From owner-freebsd-hackers Sun Jul 18 0:58:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 8C23614BE0 for ; Sun, 18 Jul 1999 00:58:24 -0700 (PDT) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id JAA68638; Sun, 18 Jul 1999 09:58:12 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Sun, 18 Jul 1999 09:58:12 +0200 (CEST) From: Leif Neland To: Vincent Poy Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? 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 Sat, 17 Jul 1999, Vincent Poy wrote: > Ah, you have a point there. The problem is we have so many wires, > we don't know which port goes to what on the Catalyst so we had it on > autodetect and FreeBSD does boot up with fxp0 showing 100Mbps Full Duplex. > Cisco's can show you which mac-adresses are on which port. Probably Catalyst's can too. Or have somebody pull the cable in and out of the pc, and watch for the light go on and off on the switch :-) Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 1: 3:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 4E13414BE0 for ; Sun, 18 Jul 1999 01:03:33 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 65882 invoked by uid 1001); 18 Jul 1999 08:02:53 +0000 (GMT) To: vince@venus.GAIANET.NET Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? From: sthaug@nethelp.no In-Reply-To: Your message of "Sun, 18 Jul 1999 09:58:12 +0200 (CEST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 18 Jul 1999 10:02:52 +0200 Message-ID: <65880.932284972@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Ah, you have a point there. The problem is we have so many wires, > > we don't know which port goes to what on the Catalyst so we had it on > > autodetect and FreeBSD does boot up with fxp0 showing 100Mbps Full Duplex. > > > Cisco's can show you which mac-adresses are on which port. Probably > Catalyst's can too. > > Or have somebody pull the cable in and out of the pc, and watch for the > light go on and off on the switch :-) A combination of those two would probably be useful. Then make a note of the port configuration, and *keep it updated*. This is essential for a hassle-free switched Ethernet environment. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 1: 5:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 9E49C14BE0 for ; Sun, 18 Jul 1999 01:05:11 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id BAA20868; Sun, 18 Jul 1999 01:04:53 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Sun, 18 Jul 1999 01:04:53 -0700 (PDT) From: Vincent Poy To: Leif Neland Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? 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, 18 Jul 1999, Leif Neland wrote: > On Sat, 17 Jul 1999, Vincent Poy wrote: > > > Ah, you have a point there. The problem is we have so many wires, > > we don't know which port goes to what on the Catalyst so we had it on > > autodetect and FreeBSD does boot up with fxp0 showing 100Mbps Full Duplex. > > > Cisco's can show you which mac-adresses are on which port. Probably > Catalyst's can too. The Catalyst is the name of the Switches made by Cisco. :-) I'm not sure if it shows the mac address of the cisco's port or the actual device connected to it... FastEthernet0/1 is up, line protocol is up Hardware is Fast Ethernet, address is 0090.abea.3bc1 (bia 0090.abea.3bc1) FastEthernet0/2 is up, line protocol is up Hardware is Fast Ethernet, address is 0090.abea.3bc2 (bia 0090.abea.3bc2) Seems more like the Cisco's port's arp address to me than the devices. > Or have somebody pull the cable in and out of the pc, and watch for the > light go on and off on the switch :-) That's a option too... Only problem is that can take forever. :-) Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 1:53:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 733EC14BE5 for ; Sun, 18 Jul 1999 01:53:08 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id SAA07163; Sun, 18 Jul 1999 18:23:02 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id SAA65625; Sun, 18 Jul 1999 18:23:00 +0930 (CST) From: Greg Lehey Date: Sun, 18 Jul 1999 18:23:00 +0930 To: Matthew Dillon Cc: Vincent Poy , Bill Paul , crypt0genic , hackers@FreeBSD.ORG Subject: Cable quality (was: poor ethernet performance?) Message-ID: <19990718182300.E65436@freebie.lemis.com> References: <199907170215.TAA25916@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i 2From: Greg Lehey In-Reply-To: <199907170215.TAA25916@apollo.backplane.com>; from Matthew Dillon on Fri, Jul 16, 1999 at 07:15:31PM -0700 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 16 July 1999 at 19:15:31 -0700, Matthew Dillon wrote: > : Actually, I was referring to *digital* Audio cables like those > :used for CD Transports to Digital/Analog convertors such as Kimber Kable > :would be higher grade compared to Monster Cable. You're correct about the > :bit errors though. > > Digital is digital. Either it works or it doesn't. Anything that goes over copper isn't digital, it's digital simulated on analogue. Poor quality cables *can* cause problems. But I'm sure that most of the folklore that circulates on this subject is of the same nature as the advice to use loudspeaker cables with at least 20mm**2 cross section, preferably driven by tube-based amplifiers. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 2: 1:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 4A05614F66 for ; Sun, 18 Jul 1999 02:01:18 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 66303 invoked by uid 1001); 18 Jul 1999 09:00:24 +0000 (GMT) To: vince@venus.GAIANET.NET Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? From: sthaug@nethelp.no In-Reply-To: Your message of "Sun, 18 Jul 1999 01:04:53 -0700 (PDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 18 Jul 1999 11:00:24 +0200 Message-ID: <66301.932288424@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm not sure if it shows the mac address of the cisco's port or > the actual device connected to it... > > FastEthernet0/1 is up, line protocol is up > Hardware is Fast Ethernet, address is 0090.abea.3bc1 (bia > 0090.abea.3bc1) > > FastEthernet0/2 is up, line protocol is up > Hardware is Fast Ethernet, address is 0090.abea.3bc2 (bia > 0090.abea.3bc2) > > Seems more like the Cisco's port's arp address to me than the > devices. Yes, this is the MAC address of the Catalyst port. You want show mac-address-table Please read the documentation. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 2:14:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 6004D14BF4 for ; Sun, 18 Jul 1999 02:14:17 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id CAA21289; Sun, 18 Jul 1999 02:14:11 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Sun, 18 Jul 1999 02:14:11 -0700 (PDT) From: Vincent Poy To: sthaug@nethelp.no Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? In-Reply-To: <66301.932288424@verdi.nethelp.no> 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, 18 Jul 1999 sthaug@nethelp.no wrote: > > I'm not sure if it shows the mac address of the cisco's port or > > the actual device connected to it... > > > > FastEthernet0/1 is up, line protocol is up > > Hardware is Fast Ethernet, address is 0090.abea.3bc1 (bia > > 0090.abea.3bc1) > > > > FastEthernet0/2 is up, line protocol is up > > Hardware is Fast Ethernet, address is 0090.abea.3bc2 (bia > > 0090.abea.3bc2) > > > > Seems more like the Cisco's port's arp address to me than the > > devices. > > Yes, this is the MAC address of the Catalyst port. You want > > show mac-address-table > > Please read the documentation. This is hard since the actual machines and switches are almost 6000 miles away from me and the last time I checked, it didn't come with manuals. I know my way around the Cisco routers but the switches is still a mystery... Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 2:25: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 9BC9A14BF4 for ; Sun, 18 Jul 1999 02:25:04 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 66456 invoked by uid 1001); 18 Jul 1999 09:24:40 +0000 (GMT) To: vince@venus.GAIANET.NET Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? From: sthaug@nethelp.no In-Reply-To: Your message of "Sun, 18 Jul 1999 02:14:11 -0700 (PDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 18 Jul 1999 11:24:40 +0200 Message-ID: <66454.932289880@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Please read the documentation. > > This is hard since the actual machines and switches are almost > 6000 miles away from me and the last time I checked, it didn't come with > manuals. I know my way around the Cisco routers but the switches is still > a mystery... All of the Cisco documentation is available on WWW. Use it! Start at http://www.cisco.com/, follow the "Technical documents" and then the "Documentation home page" link. The manual for your switch is available, that's where I found the "show mac-address-table" command. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 3:45:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id D82C41500F for ; Sun, 18 Jul 1999 03:45:31 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id MAA43785; Sun, 18 Jul 1999 12:45:28 +0200 (CEST) (envelope-from des) To: Alfred Perlstein Cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG Subject: Re: Determining the return address References: From: Dag-Erling Smorgrav Date: 18 Jul 1999 12:45:27 +0200 In-Reply-To: Alfred Perlstein's message of "Sat, 17 Jul 1999 16:01:50 -0500 (EST)" Message-ID: Lines: 30 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: > This looks like what you are doing is trying to grab the data on the > stack before "log" which is the return address. Yes. It actually works :) > I doubt this is > at all portable and may fail because of optimizations and ABI, such > as archs that store the return address in a register... I know - I don't expect it to be portable. > gdb and glibc have some functions to assist in runtime backtraces, > perhaps a look there may help? I found out about __builtin_return_address(0). > > BTW, is dladdr() signal-safe? > not according to the sigaction man page. OK, is there any way I can find out that I am being called from a signal handler, other than using a global variable? I want my logging functions to be signal-safe - that's why I use writev(), and I've gone to great lengths to ensure that log_makedate() (which uses localtime_r() and strftime() to build a date string) and lvformat() (a printf() clone with some additional goodies) are signal-safe. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 7:25:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 4AA8C14D94; Sun, 18 Jul 1999 07:25:07 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id QAA48708; Sun, 18 Jul 1999 16:24:49 +0200 (CEST) (envelope-from des) To: Greg Lehey Cc: Taavi Talvik , Jeroen Ruigrok/Asmodai , Mike Smith , hm@hcs.de, dfr@nlsystems.com, peter@FreeBSD.ORG, FreeBSD Hackers Subject: Re: All this and documentation too? (was: cvs commit: src/sys/isa sio.c) References: <19990622214019.B15249@daemon.ninth-circle.org> <19990623154745.D581@freebie.lemis.com> From: Dag-Erling Smorgrav Date: 18 Jul 1999 16:24:48 +0200 In-Reply-To: Greg Lehey's message of "Wed, 23 Jun 1999 15:47:45 +0930" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey writes: > mdoc.samples(7). Now tell me that that's not intuitive. It would seem mdoc.samples(7) does not teach by example :) des@des ~% man -t mdoc.samples | lpr -Plex Usage: .Rv -std sections 2 and 3 only DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 8: 0:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 2004614EC4; Sun, 18 Jul 1999 08:00:38 -0700 (PDT) From: "Jonathan M. Bresler" To: green@FreeBSD.org Cc: shocking@prth.pgs.com, hackers@FreeBSD.org In-reply-to: (green@FreeBSD.org) Subject: Re: Setting up a firewall with dynamic IPs Message-Id: <19990718150038.2004614EC4@hub.freebsd.org> Date: Sun, 18 Jul 1999 08:00:38 -0700 (PDT) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 13 Jul 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > > I was checking out the firewall setup in /etc/rc.firewall, and noticed that > > the simple example relied on a fixed IP address for the external interface. I > > don't know ahead of time what IP address is going to be allocated to me before > > I dial up. Would it be possible to specify an interface (tun0) rather than an > > IP address? > > Yes. That's what the "via" keyword is for. very late followup, but i am behind in my mail again. to deal with this issue i use the following: /etc/ppp/linkup: #!/bin/sh sh /etc/rc.firewall /etc/rc.firewall (exerpt) [snip] if [ "${firewall_type}" = "MINE" ]; then # # # tun0=`ifconfig tun0 | grep netmask | cut -f 2 -d ' ' | tail -1` ep0=`ifconfig ep0 | grep netmask | cut -f 2 -d ' '` loopback="127.0.0.0/8" net10="10.0.0.0/8" net172="172.16.0.0/12" net192="192.168.0.0/16" localnet="192.168.250.0/24" localhost="127.0.0.1" ntpdate_host="128.115.14.97" xntpd_host="204.91.99.129" preppp="10.0.0.1" # # clear all rules # $fwcmd -f flush # # prevent source address spoofing # $fwcmd add 100 deny log all from ${tun0} to any in recv tun0 [snip] this way, whenever i dialup, i get a new ip address. the new ip address is used to create the firewall rules. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 11:42:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id DA17B14DCA for ; Sun, 18 Jul 1999 11:42:30 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.8.8/8.8.8) with ESMTP id LAA06997; Sun, 18 Jul 1999 11:40:52 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37921FB4.B01C6F86@gorean.org> Date: Sun, 18 Jul 1999 11:40:52 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Tim Baird Cc: freebsd-hackers@freebsd.org Subject: Re: poor ethernet performance? References: <3.0.2.32.19990716231622.007e2100@storm.digital-rain.com> <3.0.2.32.19990717015406.0095f670@storm.digital-rain.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tim Baird wrote: > I hope everyone is benefitting by these simple facts.... *chuckle* "Simple facts.." You sound like my physics professor. I for one am benefitting very much from the discussion. I got hired at my current job as a software person, but I have a background in hardware so I try and make it into the NOC every excuse I get (promotability, don't you know). It always helps if sound like I have a vague idea what I'm talking about. :) I just made up my first ethernet cables the other day, and learned an interesting tidbit that I'm sure is beyond elementary to most of you, but may benefit someone else. What I was told is that the reason Cat 5 cable is so much more efficient is that each of the 4 pairs of wire is twisted at a different rate. This helps reduce the possibility of frequency synchronization for the EM fields the pairs create. Soaking it in, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 12: 2:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id 6D8FB14E27 for ; Sun, 18 Jul 1999 12:02:11 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.8.8/8.8.8) with ESMTP id MAA07067; Sun, 18 Jul 1999 12:01:44 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37922497.95F9521D@gorean.org> Date: Sun, 18 Jul 1999 12:01:43 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Assem Salama Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Devloper References: <37907E69.90037620@twcny.rr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Assem Salama wrote: > > I am interested in helping in the development in FreeBSD. I'm not a > hotshot programmer but I know how to program. Could someone please send > me the available projects that I can work on and some info about them? Step one, ignore all those responses to the poster who sent you the handbook page, they are trying to drag you into freebsd's latest holy war. :) Step two, that handbook page has a lot of good stuff, read it. Step three, (and I can't believe this isn't mentioned in the handbook) if there isn't anything on that page that looks interesting to you, take a look at http://www.freebsd.org/cgi/query-pr-summary.cgi and see if anything there strikes your fancy. Look first at unsassigned PR's, but if one of them that is assigned to someone looks like something you can handle and have time to work on, mail the person it's assigned to and ask them about it. Looking forward to your first patch, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 12: 3:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id C87B914E27 for ; Sun, 18 Jul 1999 12:03:06 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id PAA16627; Sun, 18 Jul 1999 15:13:04 -0400 (EDT) Date: Sun, 18 Jul 1999 14:13:02 -0500 (EST) From: Alfred Perlstein To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.ORG Subject: Re: Determining the return address 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 18 Jul 1999, Dag-Erling Smorgrav wrote: > Alfred Perlstein writes: > > This looks like what you are doing is trying to grab the data on the > > stack before "log" which is the return address. > > Yes. It actually works :) > > > I doubt this is > > at all portable and may fail because of optimizations and ABI, such > > as archs that store the return address in a register... > > I know - I don't expect it to be portable. *slap* :) > > > gdb and glibc have some functions to assist in runtime backtraces, > > perhaps a look there may help? > > I found out about __builtin_return_address(0). what is that? a function? available on freebsd? > > > > BTW, is dladdr() signal-safe? > > not according to the sigaction man page. > > OK, is there any way I can find out that I am being called from a > signal handler, other than using a global variable? I want my logging > functions to be signal-safe - that's why I use writev(), and I've gone > to great lengths to ensure that log_makedate() (which uses > localtime_r() and strftime() to build a date string) and lvformat() (a > printf() clone with some additional goodies) are signal-safe. sigaltstack() ? If oss is non-zero, the current signal stack state is returned. The ss_flags field will contain the value SS_ONSTACK if the process is cur- rently on a signal stack and SS_DISABLE if the signal stack is currently disabled. by setting an alternate signal stack i think you can check if you are in a signal using this. this may not be the best way but it seems like a viable solution. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 12:28: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 03F4914E50 for ; Sun, 18 Jul 1999 12:28:01 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id VAA55297; Sun, 18 Jul 1999 21:27:18 +0200 (CEST) (envelope-from des) To: Alfred Perlstein Cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG Subject: Re: Determining the return address References: From: Dag-Erling Smorgrav Date: 18 Jul 1999 21:27:18 +0200 In-Reply-To: Alfred Perlstein's message of "Sun, 18 Jul 1999 14:13:02 -0500 (EST)" Message-ID: Lines: 28 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: > On 18 Jul 1999, Dag-Erling Smorgrav wrote: > > Alfred Perlstein writes: > > > I doubt this is > > > at all portable and may fail because of optimizations and ABI, such > > > as archs that store the return address in a register... > > I know - I don't expect it to be portable. > *slap* :) It's #ifdef'ed so you can drop it on platforms where it doesn't work :) > > > gdb and glibc have some functions to assist in runtime backtraces, > > > perhaps a look there may help? > > I found out about __builtin_return_address(0). > what is that? a function? available on freebsd? GCC builtin function. > by setting an alternate signal stack i think you can check > if you are in a signal using this. this may not be the best way > but it seems like a viable solution. Hmm, I ended up using a global variable which I increment at the beginning of the signal handler, and decrement at the end. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 13: 4: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id BBACF14A2D for ; Sun, 18 Jul 1999 13:03:58 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id QAA25198; Sun, 18 Jul 1999 16:12:21 -0400 (EDT) Date: Sun, 18 Jul 1999 15:12:19 -0500 (EST) From: Alfred Perlstein To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.ORG Subject: Re: Determining the return address 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 18 Jul 1999, Dag-Erling Smorgrav wrote: > Alfred Perlstein writes: > > On 18 Jul 1999, Dag-Erling Smorgrav wrote: > > > Alfred Perlstein writes: > > > > I doubt this is > > > > at all portable and may fail because of optimizations and ABI, such > > > > as archs that store the return address in a register... > > > I know - I don't expect it to be portable. > > *slap* :) > > It's #ifdef'ed so you can drop it on platforms where it doesn't work :) > > > > > gdb and glibc have some functions to assist in runtime backtraces, > > > > perhaps a look there may help? > > > I found out about __builtin_return_address(0). > > what is that? a function? available on freebsd? > > GCC builtin function. > > > by setting an alternate signal stack i think you can check > > if you are in a signal using this. this may not be the best way > > but it seems like a viable solution. > > Hmm, I ended up using a global variable which I increment at the > beginning of the signal handler, and decrement at the end. As long as you make sure the code won't have multiple access that would work. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 13:34:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id C5DB714C58 for ; Sun, 18 Jul 1999 13:34:10 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id NAA09373 for ; Sun, 18 Jul 1999 13:33:32 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Sun, 18 Jul 1999 13:33:32 -0700 (PDT) From: Doug White To: hackers@freebsd.org Subject: Re: Devloper 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 Just to remind everyone where the actual logic is contained... Check out swap_pager.c line 1135 (in version $Id: vm_pageout.c,v 1.129.2.6 1999/03/18 23:28:39 julian Exp $). FreeBSD is not 100% indiscriminant. It favors procs with PID > 48 as targets. You could tune this to discriminate against procs > 1000 if you wanted; that way no startup procs would be killed. Of course, if one of those is causing the problem, then you're up a creek. :) Dag-Erling Smorgrav wrote: > > "Daniel C. Sobral" writes: > > * Dividing processes into those that ought to be killed first and > > those that ought to be killed last in low-memory situations Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | 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 Jul 18 15:42:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (Postfix) with SMTP id 3FABA14D14 for ; Sun, 18 Jul 1999 15:42:50 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 3683 invoked from network); 18 Jul 1999 22:42:50 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail.cdsnet.net with SMTP; 18 Jul 1999 22:42:50 -0000 Date: Sun, 18 Jul 1999 15:42:19 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: hackers@freebsd.org Subject: tee option on ipfw? 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 The man page says the tee option on ipfw is not yet supported. I'm wondering if that is still the case as of 3.2-stable, or if the doc is just out of date. I would like to make a copy of incoming UDP packets to a specific port for some testing. tee seems like an easy way to go. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 16: 3: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 9653E14F41 for ; Sun, 18 Jul 1999 16:02:53 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40330>; Mon, 19 Jul 1999 08:42:14 +1000 Date: Mon, 19 Jul 1999 09:00:14 +1000 From: Peter Jeremy Subject: Re: telnetd To: freebsd-hackers@FreeBSD.ORG Cc: imp@village.org Message-Id: <99Jul19.084214est.40330@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: >What purpose is served by the twisty maze of ifdefs in telnetd? Probably for portability. > I'd >like to unifdef many of them. I'm trying to track down a bug and the >twisty maze makes it very hard to follow. Comments? There's nothing stopping you unifdefing telnetd on your system. I have no opinion as to the merits (or otherwise) of leaving the ifdef's in the main code tree. If you're just trying to follow the code, try 'cc -E -C -dD'. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 16:22: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from abraham.chaosdev.org (chaosdev.org [194.17.41.8]) by hub.freebsd.org (Postfix) with ESMTP id 44F8514F01; Sun, 18 Jul 1999 16:21:56 -0700 (PDT) (envelope-from plundis@chaosdev.org) Received: from localhost (plundis@localhost) by abraham.chaosdev.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id BAA07146; Mon, 19 Jul 1999 01:21:59 +0200 Date: Mon, 19 Jul 1999 01:21:59 +0200 (CEST) From: Per Lundberg To: questions@freebsd.org Cc: hackers@freebsd.org Subject: glibc 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 Has anybody done a port of glibc to FreeBSD? (I'm not interested in opinions about how poor it is or how evil the FSF are; I'm only asking to avoid duplicate work. Thanks.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 16:44:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id EED8914D9F for ; Sun, 18 Jul 1999 16:44:47 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA38895; Sun, 18 Jul 1999 17:44:39 -0600 (MDT) (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 RAA75607; Sun, 18 Jul 1999 17:44:39 -0600 (MDT) Message-Id: <199907182344.RAA75607@harmony.village.org> To: Peter Jeremy Subject: Re: telnetd Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 19 Jul 1999 09:00:14 +1000." <99Jul19.084214est.40330@border.alcanet.com.au> References: <99Jul19.084214est.40330@border.alcanet.com.au> Date: Sun, 18 Jul 1999 17:44:39 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <99Jul19.084214est.40330@border.alcanet.com.au> Peter Jeremy writes: : There's nothing stopping you unifdefing telnetd on your system. I : have no opinion as to the merits (or otherwise) of leaving the : ifdef's in the main code tree. True, but since some of what I'm doing is making sure that there are no security implications to some of the paths, doing that would be useless, since that wouldn't be what is checked into the system. We really don't need the ifdefs for solaris, cray, etc, do we? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 17: 4: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 61A3714C7F; Sun, 18 Jul 1999 17:04:08 -0700 (PDT) From: "Jonathan M. Bresler" To: vince@venus.GAIANET.NET Cc: sthaug@nethelp.no, tim@storm.digital-rain.com, freebsd-hackers@FreeBSD.ORG In-reply-to: (message from Vincent Poy on Sat, 17 Jul 1999 16:01:40 -0700 (PDT)) Subject: Re: poor ethernet performance? Message-Id: <19990719000408.61A3714C7F@hub.freebsd.org> Date: Sun, 18 Jul 1999 17:04:08 -0700 (PDT) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I guess I forgot about the overhead. I've tested between two > FreeBSD machines using Intel Pro100+ NIC cards connected to a Cisco 2924XL > Switch Full Duplex and never seen anything close to the speeds. using netperfv2pl3 and FreeBSD 2.2.8 on 300MHz PII with fxp cards (all from memory), i routinely get TCP_STREAM to pushd 94Mbps. i use these machines for stressing every else we have at work. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 17:47:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles561.castles.com [208.214.165.125]) by hub.freebsd.org (Postfix) with ESMTP id 1101F14DCA for ; Sun, 18 Jul 1999 17:47:10 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id RAA01205; Sun, 18 Jul 1999 17:42:47 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907190042.RAA01205@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: System unique identifier..... In-reply-to: Your message of "Sun, 18 Jul 1999 01:20:32 +0900." <3790AD50.DC28CD62@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 18 Jul 1999 17:42:46 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > > The loader will, at some stage in the future, grow a persistent data > > store in which items like this can be saved. > > Doesn't /boot/[defaults/]loader.conf[.local] qualify as persistent > data storage? There is little or no chance that the loader will gain the ability to write back to filesystems. Some of them don't support it (eg. iso9660), others may not (TFTP, NFS), and the code required for some of them (especially UFS) would be problematically large. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 17:56:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8D97914F9D for ; Sun, 18 Jul 1999 17:56:30 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id RAA23336; Sun, 18 Jul 1999 17:55:24 -0700 Date: Sun, 18 Jul 1999 17:55:24 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: "Daniel C. Sobral" , freebsd-hackers@FreeBSD.ORG Subject: Re: System unique identifier..... In-Reply-To: <199907190042.RAA01205@dingo.cdrom.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 > > Mike Smith wrote: > > > > > > The loader will, at some stage in the future, grow a persistent data > > > store in which items like this can be saved. > > > > Doesn't /boot/[defaults/]loader.conf[.local] qualify as persistent > > data storage? > > There is little or no chance that the loader will gain the ability to > write back to filesystems. Some of them don't support it (eg. > iso9660), others may not (TFTP, NFS), and the code required for some of > them (especially UFS) would be problematically large. But that's okay. If the persistent storage is the loader conf files, they can be updated from single or multi-user mode. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 18:27:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id A8ED914A09 for ; Sun, 18 Jul 1999 18:27:43 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id VAA24781; Sun, 18 Jul 1999 21:27:30 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Sun, 18 Jul 1999 21:27:30 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Mike Smith Cc: "Daniel C. Sobral" , freebsd-hackers@FreeBSD.org Subject: Re: System unique identifier..... In-Reply-To: <199907190042.RAA01205@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Jul 1999, Mike Smith wrote: > > Mike Smith wrote: > > > > > > The loader will, at some stage in the future, grow a persistent data > > > store in which items like this can be saved. > > > > Doesn't /boot/[defaults/]loader.conf[.local] qualify as persistent > > data storage? > > There is little or no chance that the loader will gain the ability to > write back to filesystems. Some of them don't support it (eg. > iso9660), others may not (TFTP, NFS), and the code required for some of > them (especially UFS) would be problematically large. That's not quite true. It wouldn't be too hard to modify existant files, but writing new ones/truncating would take a lot of work. It's still not a great idea to try to use a file on the FS for storage of persistent data. Wouldn't it be possible to have the kernel itself read in persistent data (in some form such as getenv?) to be written to disk? That way, the boot loader could pass it easily, and not have to worry about storage. > > -- > \\ The mind's the standard \\ Mike Smith > \\ of the man. \\ msmith@freebsd.org > \\ -- Joseph Merrick \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ 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 Jul 18 19:23:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp11.bellglobal.com (smtp11.bellglobal.com [204.101.251.53]) by hub.freebsd.org (Postfix) with ESMTP id D8FE914E98 for ; Sun, 18 Jul 1999 19:23:32 -0700 (PDT) (envelope-from vanderh@ecf.toronto.edu) Received: from localhost.nowhere (ppp18330.on.bellglobal.com [206.172.130.10]) by smtp11.bellglobal.com (8.8.5/8.8.5) with ESMTP id WAA10830; Sun, 18 Jul 1999 22:24:44 -0400 (EDT) Received: (from tim@localhost) by localhost.nowhere (8.9.3/8.9.1) id WAA83035; Sun, 18 Jul 1999 22:22:36 -0400 (EDT) (envelope-from tim) Date: Sun, 18 Jul 1999 22:22:35 -0400 From: Tim Vanderhoek To: Warner Losh Cc: Peter Jeremy , freebsd-hackers@FreeBSD.ORG Subject: Re: telnetd Message-ID: <19990718222235.B82602@mad> References: <99Jul19.084214est.40330@border.alcanet.com.au> <199907182344.RAA75607@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199907182344.RAA75607@harmony.village.org>; from Warner Losh on Sun, Jul 18, 1999 at 05:44:39PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 18, 1999 at 05:44:39PM -0600, Warner Losh wrote: > > True, but since some of what I'm doing is making sure that there are > no security implications to some of the paths, doing that would be > useless, since that wouldn't be what is checked into the system. We > really don't need the ifdefs for solaris, cray, etc, do we? #if defined(CRAY2) && defined(UNICOS5) if (!linemode) { [...] } #endif /* defined(CRAY2) && defined(UNICOS5) */ And around that, there should probably be a #ifdef LINEMODE to boot. Please trash them. Especially the termio vs. termios ones. It's not that I'm anti-portability, it's just that we very rarely come-up with a usermode program that is worth exporting. I like this one even better, #if defined(LINEMODE) && defined(KLUDGELINEMODE) [...] if (lmodetype < KLUDGE_LINEMODE) { lmodetype = KLUDGE_LINEMODE; clientstat(TELOPT_LINEMODE, WILL, 0); send_wont(TELOPT_SGA, 1); } else if (lmodetype == NO_AUTOKLUDGE) { lmodetype = KLUDGE_OK; } #endif /* defined(LINEMODE) && defined(KLUDGELINEMODE) */ [It looks like the stupid thing is a runtime option anyways, after the #ifdefs...] In the first 90% of sys_term.c, I'm not sure I could find more than a couple sets of 25 contiguous lines that don't contain at least one #if or #endif... -- This is my .signature which gets appended to the end of my messages. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 20: 2: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 5479014D7B for ; Sun, 18 Jul 1999 20:01:54 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id MAA29191; Mon, 19 Jul 1999 12:01:44 +0900 (JST) Message-ID: <3792950D.D09F02ED@newsguy.com> Date: Mon, 19 Jul 1999 12:01:33 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: FreeBSD Hackers Subject: Re: All this and documentation too? (was: cvs commit: src/sys/isa sio.c) References: <19990622214019.B15249@daemon.ninth-circle.org> <19990623154745.D581@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [trimming CC list] Dag-Erling Smorgrav wrote: > > Greg Lehey writes: > > mdoc.samples(7). Now tell me that that's not intuitive. > > It would seem mdoc.samples(7) does not teach by example :) > > des@des ~% man -t mdoc.samples | lpr -Plex > Usage: .Rv -std sections 2 and 3 only This is a bug in man, actually. Section 7 is misc, and anything *can* go there. It's perfectly possible to have something in need of section 2/3 features that happens not to qualify as section 2 or 3. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org Everything journalists write is true, except when they write about something you know. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 20:25: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id E24A01506E; Sun, 18 Jul 1999 20:24:50 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip194.houston3.tx.pub-ip.psi.net [38.12.169.194]) by leap.innerx.net (Postfix) with ESMTP id 03699370B1; Sun, 18 Jul 1999 23:24:47 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id WAA81019; Sun, 18 Jul 1999 22:25:39 -0500 (CDT) (envelope-from chris) Date: Sun, 18 Jul 1999 22:25:38 -0500 From: Chris Costello To: Per Lundberg Cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: glibc Message-ID: <19990718222538.A80844@holly.dyndns.org> Reply-To: chris@calldei.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: ; from Per Lundberg on Mon, Jul 19, 1999 at 01:21:59AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 18, 1999, Per Lundberg wrote: > Has anybody done a port of glibc to FreeBSD? (I'm not interested in > opinions about how poor it is or how evil the FSF are; I'm only asking to > avoid duplicate work. Thanks.) Not that I know of, but what's the point? -- |Chris Costello |Programming just with goto's is like swatting flies with a sledgehammer. `------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 20:55:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 6EB811508A; Sun, 18 Jul 1999 20:54:56 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA09678; Mon, 19 Jul 1999 13:24:29 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA68638; Mon, 19 Jul 1999 13:24:28 +0930 (CST) Date: Mon, 19 Jul 1999 13:24:28 +0930 From: Greg Lehey To: Alex Povolotsky Cc: stable@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Booting from vinum? Message-ID: <19990719132427.I65436@freebie.lemis.com> References: <199907171851.WAA25204@shuttle.svib.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907171851.WAA25204@shuttle.svib.ru>; from Alex Povolotsky on Sat, Jul 17, 1999 at 10:51:17PM +0400 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 17 July 1999 at 22:51:17 +0400, Alex Povolotsky wrote: > Hello! > > Is it possible to have a root partition on vinum'ed disk and benefit from > mirroring? If yes, how do I do it? Not yet. It's on the drawing board. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 21: 0:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 4D099150C0 for ; Sun, 18 Jul 1999 20:59:59 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA09694; Mon, 19 Jul 1999 13:28:37 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA68657; Mon, 19 Jul 1999 13:28:36 +0930 (CST) Date: Mon, 19 Jul 1999 13:28:36 +0930 From: Greg Lehey To: Craig Johnston Cc: hackers@FreeBSD.ORG Subject: Re: vinum is cool. anyone bitten recently? Message-ID: <19990719132836.J65436@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Craig Johnston on Sat, Jul 17, 1999 at 03:07:12PM -0500 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 17 July 1999 at 15:07:12 -0500, Craig Johnston wrote: > Well, I'm looking into doing striping and mirroring on a new webserver > I am bringing up (3.2-stable) and I have to say, vinum looks very cool. > It took me like half an hour to get it going from first contact. > > Nice job Greg -- very straightforward. Thanks. > Now, the official status of vinum is still alpha, right? Wrong. It went out of alpha about a year ago. It's been released in 3.1 and 3.2. > But then again I know that that was (is?) the official status of > softupdates for quite some time and I have been using it with no > problems. > > So my question is, has anyone actually been bitten by vinum recently? > I'm willing to take my chances if I can at least be pretty sure that I > won't suddenly lose everything on both plexes if I am mirroring. That shouldn't happen. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 21:25:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from krdl.org.sg (rodin.krdl.org.sg [192.122.139.27]) by hub.freebsd.org (Postfix) with ESMTP id 27D1B14C93 for ; Sun, 18 Jul 1999 21:25:30 -0700 (PDT) (envelope-from vasu@krdl.org.sg) Received: from mailhost.krdl.org.sg (mailbox.krdl.org.sg [192.122.134.30]) by krdl.org.sg (8.9.3/8.9.3) with ESMTP id MAA17389; Mon, 19 Jul 1999 12:31:29 +0800 (SGT) Received: from boderek (boderek [192.122.135.157]) by mailhost.krdl.org.sg (8.9.3/8.9.3) with SMTP id MAA14807; Mon, 19 Jul 1999 12:23:48 +0800 (SGT) Date: Mon, 19 Jul 1999 12:09:03 +0800 (SGT) From: Vasudha Ramnath X-Sender: vasu@boderek To: Arun Sharma Cc: freebsd-hackers@freebsd.org Subject: Re: implementing poll() in a device driver (fwd) 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 have a test driver that returns these values from the poll() function. > > However, the application > > that called the select() is not getting an error. Instead, the select > > is returning that the particular file descriptor is, in this case, > > 'readable' ! > > Take a look at "selscan" algorithm in /usr/src/sys/kern/sys_generic.c > if you wish to learn more. > > Basically, if your driver doesn't implement the poll() functionality, > it can always return 0. This will ensure that select never wakes up > because of a file descriptor associated with your driver. > thanks for your reply. I realise that one can return 0. My point is that if the driver returns POLLERR or POLLHUP, it is not getting handled correctly in sys_generic.c... It seems to me that a positive (non-zero) return value is being interpreted as 'readiness', although there is a comment in sys_generic.c that the backend (driver) can also return POLLHUP or POLLERR. --Vasudha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 21:51:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 7B57414EAC for ; Sun, 18 Jul 1999 21:51:38 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id VAA01195; Sun, 18 Jul 1999 21:49:00 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id VAA14386; Sun, 18 Jul 1999 21:48:54 -0700 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA15253; Sun, 18 Jul 99 21:48:56 PDT Message-Id: <3792AE44.9CAC4953@softweyr.com> Date: Sun, 18 Jul 1999 22:49:08 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Alfred Perlstein Cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG Subject: Re: Determining the return address References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > On 17 Jul 1999, Dag-Erling Smorgrav wrote: > > > Is there any (evidently non-portable) way of determining a function > > instance's return address? I have an idea or two that involves the > > return address and dladdr(). The code I currently use looks like this: > > This looks like what you are doing is trying to grab the data on the > stack before "log" which is the return address. I doubt this is > at all portable and may fail because of optimizations and ABI, such > as archs that store the return address in a register... On the SPARC, FWIW, the return address is in %i7. What is difficult to determine (programmatically) is if the function is a normal or leaf function; different return sequences are used for each. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 22: 5:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wenet.net (sf3-58.ppp.wenet.net [206.15.84.58]) by hub.freebsd.org (Postfix) with ESMTP id 3A9CB14EAC for ; Sun, 18 Jul 1999 22:05:34 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by wenet.net (8.9.3/8.9.1) with ESMTP id WAA01454; Sun, 18 Jul 1999 22:05:11 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sun, 18 Jul 1999 22:05:11 -0700 (PDT) From: Alex Zepeda To: Per Lundberg Cc: hackers@FreeBSD.ORG Subject: Re: glibc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, Per Lundberg wrote: > Has anybody done a port of glibc to FreeBSD? (I'm not interested in > opinions about how poor it is or how evil the FSF are; I'm only asking to > avoid duplicate work. Thanks.) Perhaps if you explain what it is you're trying to accomplish, there might be an easier option than porting *shudder* glibc? - alex The sheep bleated twice. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 23:11:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id C068B14D2A for ; Sun, 18 Jul 1999 23:11:36 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id XAA58727; Sun, 18 Jul 1999 23:10:44 -0700 (PDT) From: Archie Cobbs Message-Id: <199907190610.XAA58727@bubba.whistle.com> Subject: Re: tee option on ipfw? In-Reply-To: from Jaye Mathisen at "Jul 18, 99 03:42:19 pm" To: mrcpu@internetcds.com (Jaye Mathisen) Date: Sun, 18 Jul 1999 23:10:44 -0700 (PDT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jaye Mathisen writes: > The man page says the tee option on ipfw is not yet supported. > > I'm wondering if that is still the case as of 3.2-stable, or if the doc is > just out of date. You are correct, it's still not implemented.. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 18 23:21:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 1C4E414E36; Sun, 18 Jul 1999 23:21:37 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id CAA00750; Mon, 19 Jul 1999 02:20:30 -0400 (EDT) Message-Id: <199907190620.CAA00750@cs.rpi.edu> To: Matthew Dillon Cc: "Brian F. Feldman" , "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: USFS (User Space File System) In-Reply-To: Message from Matthew Dillon of "Sat, 17 Jul 1999 17:33:40 PDT." <199907180033.RAA86259@apollo.backplane.com> Date: Mon, 19 Jul 1999 02:20:29 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : > :Look into the portal filesystem. This is what you want :) > : > : Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ > : green@FreeBSD.org _ __ ___ | _ ) __| \ > > Actually, it isn't quite. All the portal filesystem will allow you > to do is pass back a descriptor. It does not allow you to simulate > a filesystem. > > But something similar to what the portal filesystem does would be > cool -- maybe a real protocol to pass the VOP requests down to a > user process and get responses & data. Portal FS did give me a couple of starting points.. It looks interesting. Just for my own clarification... how would this be different than NFS (specifically local NFS)? -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 0:28: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 1C6BA14FFD; Mon, 19 Jul 1999 00:27:56 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA94470; Mon, 19 Jul 1999 00:26:25 -0700 (PDT) (envelope-from dillon) Date: Mon, 19 Jul 1999 00:26:25 -0700 (PDT) From: Matthew Dillon Message-Id: <199907190726.AAA94470@apollo.backplane.com> To: "David E. Cross" Cc: "Brian F. Feldman" , "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: USFS (User Space File System) References: <199907190620.CAA00750@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Portal FS did give me a couple of starting points.. It looks interesting. :Just for my own clarification... how would this be different than NFS :(specifically local NFS)? : :-- :David Cross | email: crossd@cs.rpi.edu :Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd NFS isn't a fun protocol to implement. I'd implement a user-level filesystem interface protocol like this: * Have a device similar to portal that a user process can open for the server interface. * Have the ability to mount the 'client side' of the device once the 'server side' has been opened by the user process. * VOP Requests through the mount point are routed to the user process and responses returned. * Device driver handles auto termination of any pending commands if the user process close()'s the server side interface. * User process uses read() and write() to read request structures and write back response structures. (Thus the user process can use select() if it wishes). The request structure can contain a data pointer & length. If the device is passing a read or write request to the user level server, it mmap's the data block into the server's address space prior to queueing the command and unmaps it after receiving the response. It would be really cool if someone were to write something like this. I don't think it would be terribly difficult except for the mmap() piece. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 0:28:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 5619E150F3 for ; Mon, 19 Jul 1999 00:28:11 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id RAA16411; Mon, 19 Jul 1999 17:27:05 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xma016397; Mon, 19 Jul 99 17:26:47 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id RAA03065; Mon, 19 Jul 1999 17:25:08 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id RAA20378; Mon, 19 Jul 1999 17:25:08 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id RAA13642; Mon, 19 Jul 1999 17:25:06 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199907190725.RAA13642@nymph.detir.qld.gov.au> To: Matthew Dillon Cc: freebsd-hackers@freebsd.org, Leif Neland , syssgm@detir.qld.gov.au Subject: Re: softupdates on root partition, no floppy References: <199907172306.QAA81618@apollo.backplane.com> In-Reply-To: <199907172306.QAA81618@apollo.backplane.com> from Matthew Dillon at "Sat, 17 Jul 1999 16:06:38 -0700" Date: Mon, 19 Jul 1999 17:25:06 +1000 From: Stephen McKay Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 17th July 1999, Matthew Dillon wrote: >:Is there any way to force softupdate on on a mounted system, or do I have to >:either move the / to another machine, or move a floppydrive to this machine? > > If you boot single-user, root will be mounted read-only and you should > be able to 'tunefs -n enable /dev/rda0a' and reboot. I gave up using soft updates on root because of the delayed delete behaviour. I kept filling up root while updating kernels. It doesn't gain you much on little used file systems anyway. So, I recommend people leave root alone. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 0:40: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from storm.digital-rain.com (storm.digital-rain.com [204.244.71.70]) by hub.freebsd.org (Postfix) with ESMTP id 5378514F03 for ; Mon, 19 Jul 1999 00:40:02 -0700 (PDT) (envelope-from tim@storm.digital-rain.com) Received: from agamemnon.melonville.net (dial-line60.digital-rain.com [204.244.94.60]) by storm.digital-rain.com (8.9.1/8.9.1) with SMTP id AAA00328; Mon, 19 Jul 1999 00:38:51 -0700 (PDT) Message-Id: <3.0.2.32.19990719003849.00981d20@storm.digital-rain.com> X-Sender: tim@storm.digital-rain.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) Date: Mon, 19 Jul 1999 00:38:49 -0700 To: Doug From: Tim Baird Subject: Re: poor ethernet performance? Cc: freebsd-hackers@freebsd.org In-Reply-To: <37921FB4.B01C6F86@gorean.org> References: <3.0.2.32.19990716231622.007e2100@storm.digital-rain.com> <3.0.2.32.19990717015406.0095f670@storm.digital-rain.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:40 AM 18/07/99 -0700, you wrote: >Tim Baird wrote: > >> I hope everyone is benefitting by these simple facts.... > > *chuckle* "Simple facts.." You sound like my physics professor. I for one >am benefitting very much from the discussion. I got hired at my current job >as a software person, but I have a background in hardware so I try and make >it into the NOC every excuse I get (promotability, don't you know). It >always helps if sound like I have a vague idea what I'm talking about. :) I'll take that as a compliment ;) > > I just made up my first ethernet cables the other day, and learned an >interesting tidbit that I'm sure is beyond elementary to most of you, but >may benefit someone else. What I was told is that the reason Cat 5 cable is >so much more efficient is that each of the 4 pairs of wire is twisted at a >different rate. This helps reduce the possibility of frequency >synchronization for the EM fields the pairs create. Your description (what you were told) here is incorrect....the number of twists in a cable had **NO** effect on the spectral content of the cunducted signal or resulting radiated/induced signal.....to do so would require the conductors to have a nonlinear conduction characteristic which they most assuredly do not (for all practical purposes). The design of the cable is such that adjacent pairs have as little effectively parallel length as possible. Obviously, the currents in the wires share the same axis, so the magnetic coupling is only reduced by the fact that interfering magnetic fields will tend to induce a common mode current in adjacent pairs...particulary since both conductors in the receiving cable pair --on average-- are exposed equally, the idea in "randomizing" the twists is to reduce the capacitive coupling as much as possible. Capacitive coupling is a more localized effect, and thrives when conductors share a common plane in close proximity...this is why capacitors are designed as two metal plates very close together..the electric field between the plates (conductors) is much higher than if they were perpendicular...or not nicely parallel. I hope this clarifies the situation :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 0:40:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from abraham.chaosdev.org (chaosdev.org [194.17.41.8]) by hub.freebsd.org (Postfix) with ESMTP id CC3E115104 for ; Mon, 19 Jul 1999 00:40:18 -0700 (PDT) (envelope-from plundis@chaosdev.org) Received: from localhost (plundis@localhost) by abraham.chaosdev.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id JAA11860; Mon, 19 Jul 1999 09:38:54 +0200 Date: Mon, 19 Jul 1999 09:38:54 +0200 (CEST) From: Per Lundberg To: Alex Zepeda Cc: hackers@FreeBSD.ORG Subject: Re: glibc 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, 18 Jul 1999, Alex Zepeda wrote: > Perhaps if you explain what it is you're trying to accomplish, there might > be an easier option than porting *shudder* glibc? I need a libc 100% compatible with glibc to make porting (from Linux) easier. And, as a side note, I think both FreeBSD and Linux would benefit of having compatible libc:s. Perhaps porting BSD libc to Linux would be easier? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 0:46:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wenet.net (tibet-58.ppp.hooked.net [206.80.9.186]) by hub.freebsd.org (Postfix) with ESMTP id DED30150D8 for ; Mon, 19 Jul 1999 00:46:10 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by wenet.net (8.9.3/8.9.1) with ESMTP id AAA01866; Mon, 19 Jul 1999 00:44:36 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Mon, 19 Jul 1999 00:44:36 -0700 (PDT) From: Alex Zepeda To: Per Lundberg Cc: hackers@FreeBSD.ORG Subject: Re: glibc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, Per Lundberg wrote: > I need a libc 100% compatible with glibc to make porting (from Linux) > easier. And, as a side note, I think both FreeBSD and Linux would benefit > of having compatible libc:s. I seriously doubt this will make porting any easier. 99% of the porting issues you'll run into, are from a.) lack of sys/types.h being included, or order of headers being included. b.) dependencies on Linux-specific ioctls or syscalls, such as clone, which are not really libc related. c.) dependencies on bugs in glibc. > Perhaps porting BSD libc to Linux would be easier? I doubt it. The glibc has been designed with portability in mind (hell, it's purported to run on Irix), FreeBSD's with security and speed. - alex What I am is what I am, What you are is what you are - Edie Brickell (ain't she profound?) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 0:48:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 2FEC51505A for ; Mon, 19 Jul 1999 00:48:32 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id AAA26781; Mon, 19 Jul 1999 00:48:06 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Mon, 19 Jul 1999 00:48:06 -0700 (PDT) From: Vincent Poy To: sthaug@nethelp.no Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? In-Reply-To: <66454.932289880@verdi.nethelp.no> 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, 18 Jul 1999 sthaug@nethelp.no wrote: > > > Please read the documentation. > > > > This is hard since the actual machines and switches are almost > > 6000 miles away from me and the last time I checked, it didn't come with > > manuals. I know my way around the Cisco routers but the switches is still > > a mystery... > > All of the Cisco documentation is available on WWW. Use it! I known it is but I was talking about the printed copy... > Start at http://www.cisco.com/, follow the "Technical documents" and > then the "Documentation home page" link. The manual for your switch is > available, that's where I found the "show mac-address-table" command. Atleast the Cisco documentation is good... The Ascend documentation sucks big time since none of the stuff in the manual matches the actual OS on the system. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 0:49:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 4C4691505A for ; Mon, 19 Jul 1999 00:49:26 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id JAA71576; Mon, 19 Jul 1999 09:48:47 +0200 (CEST) (envelope-from des) To: Wes Peters Cc: Alfred Perlstein , Dag-Erling Smorgrav , hackers@FreeBSD.ORG Subject: Re: Determining the return address References: <3792AE44.9CAC4953@softweyr.com> From: Dag-Erling Smorgrav Date: 19 Jul 1999 09:48:47 +0200 In-Reply-To: Wes Peters's message of "Sun, 18 Jul 1999 22:49:08 -0600" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters writes: > On the SPARC, FWIW, the return address is in %i7. What is difficult to > determine (programmatically) is if the function is a normal or leaf function; > different return sequences are used for each. It doesn't matter; all I need it for is to find the caller's name using dladdr(). DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 0:52:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 530131507D for ; Mon, 19 Jul 1999 00:52:13 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id JAA71620; Mon, 19 Jul 1999 09:50:16 +0200 (CEST) (envelope-from des) To: Alfred Perlstein Cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG Subject: Re: Determining the return address References: From: Dag-Erling Smorgrav Date: 19 Jul 1999 09:50:16 +0200 In-Reply-To: Alfred Perlstein's message of "Sun, 18 Jul 1999 15:12:19 -0500 (EST)" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: > On 18 Jul 1999, Dag-Erling Smorgrav wrote: > > Hmm, I ended up using a global variable which I increment at the > > beginning of the signal handler, and decrement at the end. > As long as you make sure the code won't have multiple access > that would work. Signal handlers having multiple accesses? When did you last see that happen? DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 0:52:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from abraham.chaosdev.org (chaosdev.org [194.17.41.8]) by hub.freebsd.org (Postfix) with ESMTP id 264AC150F1 for ; Mon, 19 Jul 1999 00:52:33 -0700 (PDT) (envelope-from plundis@chaosdev.org) Received: from localhost (plundis@localhost) by abraham.chaosdev.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id JAA11945; Mon, 19 Jul 1999 09:49:21 +0200 Date: Mon, 19 Jul 1999 09:49:20 +0200 (CEST) From: Per Lundberg To: Alex Zepeda Cc: hackers@FreeBSD.ORG Subject: Re: glibc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, Alex Zepeda wrote: > I seriously doubt this will make porting any easier. You think so? I experience a lot of this when I try to recompile stuff for FreeBSD (most of it are due to lack of a real getopt routine). > c.) dependencies on bugs in glibc. What bugs have you found in glibc 2.1.1? Have you reported those to the GNU folks? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 0:55:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wenet.net (tibet-58.ppp.hooked.net [206.80.9.186]) by hub.freebsd.org (Postfix) with ESMTP id 56FAB1505A for ; Mon, 19 Jul 1999 00:55:18 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by wenet.net (8.9.3/8.9.1) with ESMTP id AAA04517; Mon, 19 Jul 1999 00:55:06 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Mon, 19 Jul 1999 00:55:05 -0700 (PDT) From: Alex Zepeda To: Per Lundberg Cc: hackers@FreeBSD.ORG Subject: Re: glibc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, Per Lundberg wrote: > You think so? Yes. > I experience a lot of this when I try to recompile stuff for FreeBSD > (most of it are due to lack of a real getopt routine). *sigh* It's quite easily argued that depending on a *NON STANDARD* getopt routine is a bug. AFAIK *ONLY* glibc has the long-getopt crap, and if that's the only thing you're running into, it should be easy enough to rip out the long getopt code, and add a few proper defines and have the standard libc coexist peacefully with the GNU getopt. > > c.) dependencies on bugs in glibc. > > What bugs have you found in glibc 2.1.1? Have you reported those to the > GNU folks? I personally haven't found any, but I've seen for instance, kcalc is riddled with ifdefs and warnings about floating point precision stuff and RH 5.something due to glibc bug(s). - alex I thought felt your touch In my car, on my clutch But I guess it's just someone who felt a lot like I remember you. - Translator To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 0:59:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id C1AA71501A; Mon, 19 Jul 1999 00:59:23 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id AAA26862; Mon, 19 Jul 1999 00:57:55 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Mon, 19 Jul 1999 00:57:55 -0700 (PDT) From: Vincent Poy To: "Jonathan M. Bresler" Cc: sthaug@nethelp.no, tim@storm.digital-rain.com, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? In-Reply-To: <19990719000408.61A3714C7F@hub.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 Sun, 18 Jul 1999, Jonathan M. Bresler wrote: > > I guess I forgot about the overhead. I've tested between two > > FreeBSD machines using Intel Pro100+ NIC cards connected to a Cisco 2924XL > > Switch Full Duplex and never seen anything close to the speeds. > > using netperfv2pl3 and FreeBSD 2.2.8 on 300MHz PII with fxp > cards (all from memory), i routinely get TCP_STREAM to pushd 94Mbps. > > i use these machines for stressing every else we have at work. Hmmm, has anyone tried a full duplex test before? Since it seems like the bottleneck is really the speed of the disks.. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 1: 5:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id C5C391501A; Mon, 19 Jul 1999 01:05:36 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA10416; Mon, 19 Jul 1999 17:34:08 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id RAA72754; Mon, 19 Jul 1999 17:34:07 +0930 (CST) Date: Mon, 19 Jul 1999 17:34:07 +0930 From: Greg Lehey To: FreeBSD Hackers , FreeBSD Committers Subject: How much memory do we need to install? Message-ID: <19990719173407.C72625@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG AFAIK, the minimum memory for installation is still 5 MB, and the problems people had with 8MB machines failing to install was a bug, right? What's the current status? Greg ----- Forwarded message from Thierry Herbelot ----- > Delivered-To: freebsd-questions@freebsd.org > Date: Mon, 19 Jul 1999 09:49:01 +0200 > Reply-To: thierry.herbelot@alcatel.fr > Organization: ALCATEL CIT Nanterre > X-Mailer: Mozilla 4.5 [en] (WinNT; I) > X-Accept-Language: en > To: Ben Salem > Cc: freebsd-questions@FreeBSD.ORG > X-Loop: FreeBSD.ORG > Precedence: bulk > > You must have more than 8 Megs to install FreeBSD > > TfH > > Ben Salem wrote: >> >> Im attempting to install FreeBSD 3.2-RELEASE on a 486 8mb ram. >> >> Everything goes ok until the installation actually begins, it gets to >> chunk 1 of 106 then stops. >> >> The install seems to work fine on my other machines. >> >> I have replaced the NIC card, so I think I can rule that out. >> >> Any ideas? >> >> Thanks >> Ben Salem ----- End forwarded message ----- -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 1:18: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [196.37.91.10]) by hub.freebsd.org (Postfix) with ESMTP id 6B5B714BCC; Mon, 19 Jul 1999 01:17:34 -0700 (PDT) (envelope-from rbezuide@oskar.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.nanoteq.co.za (8.9.0/8.9.0) id KAA22986; Mon, 19 Jul 1999 10:16:47 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199907190816.KAA22986@oskar.nanoteq.co.za> Subject: Re: poor ethernet performance? In-Reply-To: from Vincent Poy at "Jul 19, 99 00:57:55 am" To: vince@venus.GAIANET.NET (Vincent Poy) Date: Mon, 19 Jul 1999 10:16:47 +0200 (SAT) Cc: jmb@hub.FreeBSD.ORG, sthaug@nethelp.no, tim@storm.digital-rain.com, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... We have previously done many network performance tests for our products running on FreeBSD ... We have found that when ever there is disk accessing involved, it is not a good idea to look at the transfer figures. We did tests with ftp and is was slow (compared to only memory generated data e.g. ttcp) 1. If you want to test the network speed ... use ttcp or something that generates the data and doesn't read it from disk. 2. When doing full-duplex and using fxp cards, stay away from X-over cables ... use a full-duplex switch etc. ... the fxp cards are not made to work with X-over cables (as far as I know - ala Intel spec) note ... only for full-duplex tests. We have done tests in full-duplex with non Intel cards (because we did not have a switch at that time :)) and with max size packets we got around 188.00 Mbps using the de0 driver. Cheers Reinier > On Sun, 18 Jul 1999, Jonathan M. Bresler wrote: > > > > I guess I forgot about the overhead. I've tested between two > > > FreeBSD machines using Intel Pro100+ NIC cards connected to a Cisco 2924XL > > > Switch Full Duplex and never seen anything close to the speeds. > > > > using netperfv2pl3 and FreeBSD 2.2.8 on 300MHz PII with fxp > > cards (all from memory), i routinely get TCP_STREAM to pushd 94Mbps. > > > > i use these machines for stressing every else we have at work. > > Hmmm, has anyone tried a full duplex test before? Since it seems > like the bottleneck is really the speed of the disks.. > > > Cheers, > Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > GaiaNet Corporation - M & C Estate / / / / | / | __] ] > Beverly Hills, California USA 90210 / / / / / |/ / | __] ] > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > > 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 Jul 19 1:42:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id B120914C7F; Mon, 19 Jul 1999 01:42:26 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id BAA27194; Mon, 19 Jul 1999 01:39:53 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Mon, 19 Jul 1999 01:39:53 -0700 (PDT) From: Vincent Poy To: Reinier Bezuidenhout Cc: jmb@hub.FreeBSD.ORG, sthaug@nethelp.no, tim@storm.digital-rain.com, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? In-Reply-To: <199907190816.KAA22986@oskar.nanoteq.co.za> 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, 19 Jul 1999, Reinier Bezuidenhout wrote: > Hi ... > > We have previously done many network performance tests for our > products running on FreeBSD ... > > We have found that when ever there is disk accessing involved, it > is not a good idea to look at the transfer figures. We did tests > with ftp and is was slow (compared to only memory generated data > e.g. ttcp) yeah, I guess all tests should be done without requiring the use of the disk. > 1. If you want to test the network speed ... use ttcp or something > that generates the data and doesn't read it from disk. ttcp works. The only problem is when I tried it in both directions, at once. the total becomes 11.xMbytes/sec total as opposed to 9.4Mbytes/sec when doing it in one direction only. > 2. When doing full-duplex and using fxp cards, stay away from X-over > cables ... use a full-duplex switch etc. ... the fxp cards are not > made to work with X-over cables (as far as I know - ala Intel spec) > note ... only for full-duplex tests. Does anyone actually use X-over cables for 100Mbps Full Duplex since 3Com said CrossOver cables are not rated for 100Mbps or something even though it's Cat5. Actually, in the older Intel docs for the Pro100B, it does say to connect using X-over cable to the switch. > We have done tests in full-duplex with non Intel cards (because we did > not have a switch at that time :)) and with max size packets we got around > 188.00 Mbps using the de0 driver. Pretty interesting. How did you do the full duplex tests? Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > On Sun, 18 Jul 1999, Jonathan M. Bresler wrote: > > > > > > I guess I forgot about the overhead. I've tested between two > > > > FreeBSD machines using Intel Pro100+ NIC cards connected to a Cisco 2924XL > > > > Switch Full Duplex and never seen anything close to the speeds. > > > > > > using netperfv2pl3 and FreeBSD 2.2.8 on 300MHz PII with fxp > > > cards (all from memory), i routinely get TCP_STREAM to pushd 94Mbps. > > > > > > i use these machines for stressing every else we have at work. > > > > Hmmm, has anyone tried a full duplex test before? Since it seems > > like the bottleneck is really the speed of the disks.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 3:24:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (Postfix) with SMTP id 33F8A14C7F for ; Mon, 19 Jul 1999 03:24:06 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 11029 invoked from network); 19 Jul 1999 10:23:55 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail.cdsnet.net with SMTP; 19 Jul 1999 10:23:55 -0000 Date: Mon, 19 Jul 1999 03:23:23 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: hackers@freebsd.org Subject: Buildworld failing from 3.1 to 3-2.stable... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a box running 3.1-stable that I wanted to update. sups fine, but the build dies in login with: ===> usr.bin/login cc -O -pipe -static -Wall -DLOGIN_ACCESS -DLOGALL -I/usr/obj/n/FreeBSD/RELENG_3/src/tmp/usr/include -c /n/FreeBSD/RELENG_3 /src/usr.bin/login/login.c /n/FreeBSD/RELENG_3/src/usr.bin/login/login.c: In function `main': /n/FreeBSD/RELENG_3/src/usr.bin/login/login.c:129: warning: argument `argv' might be clobbered by `longjmp' or `vfork' cc -O -pipe -static -Wall -DLOGIN_ACCESS -DLOGALL -I/usr/obj/n/FreeBSD/RELENG_3/src/tmp/usr/include -c /n/FreeBSD/RELENG_3 /src/usr.bin/login/login_access.c cc -O -pipe -static -Wall -DLOGIN_ACCESS -DLOGALL -I/usr/obj/n/FreeBSD/RELENG_3/src/tmp/usr/include -c /n/FreeBSD/RELENG_3 /src/usr.bin/login/login_fbtab.c cc -O -pipe -static -Wall -DLOGIN_ACCESS -DLOGALL -I/usr/obj/n/FreeBSD/RELENG_3/src/tmp/usr/include -o login login.o logi n_access.o login_fbtab.o -lutil -lcrypt -lpam /usr/obj/n/FreeBSD/RELENG_3/src/tmp/usr/lib/libpam.a(pam_static_modules.o): In function `_pam_get_static_sym': pam_static_modules.o(.text+0x179): undefined reference to `skeyaccess' pam_static_modules.o(.text+0x275): undefined reference to `rad_create_request' pam_static_modules.o(.text+0x283): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x29d): undefined reference to `rad_put_string' pam_static_modules.o(.text+0x2b2): undefined reference to `rad_put_string' pam_static_modules.o(.text+0x2dc): undefined reference to `rad_put_string' pam_static_modules.o(.text+0x2ea): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x308): undefined reference to `rad_put_attr' pam_static_modules.o(.text+0x316): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x32a): undefined reference to `rad_put_int' pam_static_modules.o(.text+0x33e): undefined reference to `rad_strerror' stdin What am I missing here? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 3:29:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id BF5B014E57; Mon, 19 Jul 1999 03:29:19 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:P+7Yw23J9pZK8o3OlAYrnoeEWRa4bJx+@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id TAA31804; Mon, 19 Jul 1999 19:28:52 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id TAA13980; Mon, 19 Jul 1999 19:33:09 +0900 (JST) Message-Id: <199907191033.TAA13980@zodiac.mech.utsunomiya-u.ac.jp> To: hackers@freebsd.org, doc@freebsd.org Cc: bde@freebsd.org, wpaul@freebsd.org, rnordier@freebsd.org, nik@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: 2nd draft: README.serial for handbook Date: Mon, 19 Jul 1999 19:33:08 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The second draft of the serial console section in the FreeBSD handbook is ready. It is available at the same URL as below. Please review and correct any technical, grammatical, or whatever errors. Thank you. Kazu >>From time to time people ask questions about the serial console. As >README.serial is buried deep inside the kernel source tree, it's almost >time to have a decent text on the serial console in our handbook. > >I am reformatting README.serial so that it can be included in our >handbook, and adding bits and pieces to clarify things. I haven't >finished it yet, but would like to have your comments now, so that we >can make it more informative and useful. > >I put up the HTML version in: > > http://www.freebsd.org/~yokota/serialconsole.html > >and the SGML version in: > > http://www.freebsd.org/~yokota/serial-console.sgml > >Please have a look and send me comments, corrections, additional >useful text, relevant pointers, etc. > >Some notes: > >- The text describes FreeBSD versions 3.0 and 3.1 or later. Version >3.0 doesn't have our new boot loader, so there is a note in the >introduction section about it. > >- Because there are many differences regarding the serial console >setup between 2.X systems and 3.X systems, I don't directly deal with >2.X systems in this text. > >- I am not a SGML expart ;-< formatting and links may be wrong. > >- Some sections are not yet finished :-) > >- The chapter number is arbitrary. When this text will be eventually >included in the handbook, I expect Nik will put it somewhere suitable >and give appropriate chapter number. > > >Thank you. > >Kazu > >PS: I don't subscribe to the doc ML. Please send mail to the hackers ML >or to me directly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 4:23:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mpp.pro-ns.net (mpp.pro-ns.net [208.200.182.72]) by hub.freebsd.org (Postfix) with ESMTP id BB4E114BD7 for ; Mon, 19 Jul 1999 04:23:34 -0700 (PDT) (envelope-from mpp@mpp.pro-ns.net) Received: (from mpp@localhost) by mpp.pro-ns.net (8.9.3/8.9.3) id GAA12394; Mon, 19 Jul 1999 06:22:04 -0500 (CDT) (envelope-from mpp) From: Mike Pritchard Message-Id: <199907191122.GAA12394@mpp.pro-ns.net> Subject: Re: All this and documentation too? (was: cvs commit: src/sys/isa sio.c) In-Reply-To: <3792950D.D09F02ED@newsguy.com> from "Daniel C. Sobral" at "Jul 19, 1999 12:01:33 pm" To: dcs@newsguy.com (Daniel C. Sobral) Date: Mon, 19 Jul 1999 06:22:04 -0500 (CDT) Cc: des@flood.ping.uio.no (Dag-Erling Smorgrav), hackers@FreeBSD.org (FreeBSD Hackers) 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 > [trimming CC list] > > Dag-Erling Smorgrav wrote: > > > > Greg Lehey writes: > > > mdoc.samples(7). Now tell me that that's not intuitive. > > > > It would seem mdoc.samples(7) does not teach by example :) > > > > des@des ~% man -t mdoc.samples | lpr -Plex > > Usage: .Rv -std sections 2 and 3 only > > This is a bug in man, actually. Section 7 is misc, and anything > *can* go there. It's perfectly possible to have something in need of > section 2/3 features that happens not to qualify as section 2 or 3. It isn't a bug in man. It is a problem with the mdoc macro package. Technically, mdoc.samples is using a *roff macro in a section that shouldn't be using that macro (the .Rv macro). I've known about this problem for quite some time, but just haven't been willing to commit the fix, since mdoc.samples(7) is the only man page that spits out this error. I do have a fixed version of the mdoc macro package that ignores this error for section 7 man pages. Since I've seen a few comments on this in the past few months, I suppose I'll break down and commit my changes. -- Mike Pritchard mpp@FreeBSD.ORG or mpp@mpp.pro-ns.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 5:45:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [196.37.91.10]) by hub.freebsd.org (Postfix) with ESMTP id 14E9E1513D; Mon, 19 Jul 1999 05:45:14 -0700 (PDT) (envelope-from rbezuide@oskar.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.nanoteq.co.za (8.9.0/8.9.0) id OAA29203; Mon, 19 Jul 1999 14:46:28 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199907191246.OAA29203@oskar.nanoteq.co.za> Subject: Re: poor ethernet performance? In-Reply-To: from Vincent Poy at "Jul 19, 99 01:39:53 am" To: vince@venus.GAIANET.NET (Vincent Poy) Date: Mon, 19 Jul 1999 14:46:28 +0200 (SAT) Cc: jmb@hub.FreeBSD.ORG, sthaug@nethelp.no, tim@storm.digital-rain.com, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi .. > > 1. If you want to test the network speed ... use ttcp or something > > that generates the data and doesn't read it from disk. > > ttcp works. The only problem is when I tried it in both > directions, at once. the total becomes 11.xMbytes/sec total as opposed to > 9.4Mbytes/sec when doing it in one direction only. If the devices are set at full-duplex then you are looking at something else ... the standard size for ttcp packets is 8k ... maybe the switch etc. that you are connected to doesn't handle fragmented packets very well. But ... what it rather seems like .. is that the devices are not in full-duplex mode .... generating a lot of collisions. After a test with transfers in both directions .. check the number of collisions with "netstat -in". If the number of collisions is not high .. - wait a moment ... are you using ttcp with tcp or udp option ... if you are using tcp (the default) then when transfering data you have acks going in both directions which could cause collisions on a full-duplex line ... try the same with the -u option for UDP. Check our setup below ... I'll explain some things there. Also check with "netstat -sn" to see if there are any other counters that increase with the full-duplex transfers. > > 2. When doing full-duplex and using fxp cards, stay away from X-over > > cables ... use a full-duplex switch etc. ... the fxp cards are not > > made to work with X-over cables (as far as I know - ala Intel spec) > > note ... only for full-duplex tests. > > Does anyone actually use X-over cables for 100Mbps Full Duplex > since 3Com said CrossOver cables are not rated for 100Mbps or something > even though it's Cat5. Actually, in the older Intel docs for the Pro100B, > it does say to connect using X-over cable to the switch. Yes ... to a switch maybe ... but not fxp to fxp ... when transfering small packets .. you get a lot of "device timeouts". > > We have done tests in full-duplex with non Intel cards (because we did > > not have a switch at that time :)) and with max size packets we got around > > 188.00 Mbps using the de0 driver. > > Pretty interesting. How did you do the full duplex tests? > I'll describe the setup briefly ... :) We had 3 machines .... two PII-400 as the generators and a PII-400 as the machine in the middle ... So we have a setup that looks like this ... --------- ---------- --------- | Gen 1 |-----------------| Router |-------------| Gen 2 | --------- ---------- --------- Now .. here is a trick ... add entries manually in the Router's tables to simulate machines on each side that "does not exist". The reason for this is that we don't want the machines on the side to be generating AND excepting packets ... we just want them to generate packets at max network rate and nothing else. We then start a ttcp on both sides to the "non existing" machines. This means the router will be forwaring packets it receives without any machines having to be there because of the entries in the routing table. (we did this because we did not have another two fast machines at that time, but we did check the packets to make sure everything goes through and are not dropped etc. - it was some time ago :) ) We start ttcp with the following command ttcp -t -s -u -p 7000 -n -l 1472 10.0.0.1 the size of 1472 generates nice 1514 size UDP packets :) We then let the test run ... and check the throughput ... We used CAT5 X-over cables ... Hopw this helps Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 5:51:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sbridge.highvoltage.com (voltage.high-voltage.com [205.243.158.175]) by hub.freebsd.org (Postfix) with SMTP id 6819214D53; Mon, 19 Jul 1999 05:51:53 -0700 (PDT) (envelope-from BMCGROARTY@high-voltage.com) Date: Mon, 19 Jul 1999 6:27 -0600 From: "Brian McGroarty" To: "Greg Lehey" , "FreeBSD Hackers" , "FreeBSD Committers" Subject: RE: How much memory do we need to install? Message-ID: <27E6CBC4F939D31186D20008C7333C82@high-voltage.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 3.2-RELEASE installs just fine on an 8 meg 386. -STABLE runs just fine. -----Original Message----- From: Greg Lehey [mailto:grog@lemis.com] Sent: Monday, July 19, 1999 2:04 AM To: Brian McGroarty; FreeBSD Hackers; FreeBSD Committers Subject: How much memory do we need to install? AFAIK, the minimum memory for installation is still 5 MB, and the problems people had with 8MB machines failing to install was a bug, right? What's the current status? Greg ----- Forwarded message from Thierry Herbelot ----- > Delivered-To: freebsd-questions@freebsd.org > Date: Mon, 19 Jul 1999 09:49:01 +0200 > Reply-To: thierry.herbelot@alcatel.fr > Organization: ALCATEL CIT Nanterre > X-Mailer: Mozilla 4.5 [en] (WinNT; I) > X-Accept-Language: en > To: Ben Salem > Cc: freebsd-questions@FreeBSD.ORG > X-Loop: FreeBSD.ORG > Precedence: bulk > > You must have more than 8 Megs to install FreeBSD > > TfH > > Ben Salem wrote: >> >> Im attempting to install FreeBSD 3.2-RELEASE on a 486 8mb ram. >> >> Everything goes ok until the installation actually begins, it gets to >> chunk 1 of 106 then stops. >> >> The install seems to work fine on my other machines. >> >> I have replaced the NIC card, so I think I can rule that out. >> >> Any ideas? >> >> Thanks >> Ben Salem ----- End forwarded message ----- -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-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 Jul 19 5:59:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from abraham.chaosdev.org (chaosdev.org [194.17.41.8]) by hub.freebsd.org (Postfix) with ESMTP id 93DB61513D for ; Mon, 19 Jul 1999 05:59:39 -0700 (PDT) (envelope-from plundis@chaosdev.org) Received: from localhost (plundis@localhost) by abraham.chaosdev.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id OAA14253; Mon, 19 Jul 1999 14:58:43 +0200 Date: Mon, 19 Jul 1999 14:58:43 +0200 (CEST) From: Per Lundberg To: Alex Zepeda Cc: hackers@FreeBSD.ORG Subject: Re: glibc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, Alex Zepeda wrote: > It's quite easily argued that depending on a *NON STANDARD* getopt routine > is a bug. I know it isn't standard. But it works well, and is used by a lot of programs. Perhaps it should have been put in another library than libc, though. Actually, I'd better suggest this to the GNU people right ahead. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 6: 8:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id 096B015161 for ; Mon, 19 Jul 1999 06:08:11 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip194.houston3.tx.pub-ip.psi.net [38.12.169.194]) by leap.innerx.net (Postfix) with ESMTP id BCB9E3708B; Mon, 19 Jul 1999 09:06:24 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id IAA15218; Mon, 19 Jul 1999 08:07:14 -0500 (CDT) (envelope-from chris) Date: Mon, 19 Jul 1999 08:07:13 -0500 From: Chris Costello To: Per Lundberg Cc: Alex Zepeda , hackers@FreeBSD.ORG Subject: Re: glibc Message-ID: <19990719080712.A15178@holly.dyndns.org> Reply-To: chris@calldei.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: ; from Per Lundberg on Mon, Jul 19, 1999 at 02:58:43PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 19, 1999, Per Lundberg wrote: > On Mon, 19 Jul 1999, Alex Zepeda wrote: > > > It's quite easily argued that depending on a *NON STANDARD* getopt routine > > is a bug. > > I know it isn't standard. But it works well, and is used by a lot of > programs. Perhaps it should have been put in another library than libc, > though. Actually, I'd better suggest this to the GNU people right ahead. What is the point of using GNU-getopt over the standard getopt other than --foo-bar flags that everyone I know hates? -- |Chris Costello |Watch out for off-by-one errors. `---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 6: 8:49 1999 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 4EED91517A for ; Mon, 19 Jul 1999 06:08:46 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id IAA01910; Mon, 19 Jul 1999 08:08:24 -0500 (CDT) Date: Mon, 19 Jul 1999 08:08:24 -0500 (CDT) From: Steve Price To: Per Lundberg Cc: Alex Zepeda , hackers@FreeBSD.ORG Subject: Re: glibc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, Per Lundberg wrote: # On Mon, 19 Jul 1999, Alex Zepeda wrote: # # > It's quite easily argued that depending on a *NON STANDARD* getopt routine # > is a bug. # # I know it isn't standard. But it works well, and is used by a lot of # programs. Perhaps it should have been put in another library than libc, # though. Actually, I'd better suggest this to the GNU people right ahead. How about gnugetopt? FreeBSD already has a port, devel/libgnugetopt, that does this. :) -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 6:20:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from abraham.chaosdev.org (chaosdev.org [194.17.41.8]) by hub.freebsd.org (Postfix) with ESMTP id A42B815171 for ; Mon, 19 Jul 1999 06:20:30 -0700 (PDT) (envelope-from plundis@chaosdev.org) Received: from localhost (plundis@localhost) by abraham.chaosdev.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id PAA14451; Mon, 19 Jul 1999 15:17:44 +0200 Date: Mon, 19 Jul 1999 15:17:44 +0200 (CEST) From: Per Lundberg To: Chris Costello Cc: hackers@FreeBSD.ORG Subject: Re: glibc In-Reply-To: <19990719080712.A15178@holly.dyndns.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, 19 Jul 1999, Chris Costello wrote: > What is the point of using GNU-getopt over the standard > getopt other than --foo-bar flags that everyone I know hates? Nothing. But I don't think they're as bad as you say, especially when you're new to a program and don't know the short options yet. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 6:20:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from abraham.chaosdev.org (chaosdev.org [194.17.41.8]) by hub.freebsd.org (Postfix) with ESMTP id 4CEEE151B9 for ; Mon, 19 Jul 1999 06:20:41 -0700 (PDT) (envelope-from plundis@chaosdev.org) Received: from localhost (plundis@localhost) by abraham.chaosdev.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id PAA14461; Mon, 19 Jul 1999 15:18:42 +0200 Date: Mon, 19 Jul 1999 15:18:41 +0200 (CEST) From: Per Lundberg To: Steve Price Cc: hackers@FreeBSD.ORG Subject: Re: glibc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, Steve Price wrote: > How about gnugetopt? FreeBSD already has a port, devel/libgnugetopt, > that does this. :) Great. I'll check this out. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 6:46:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 76DF414D37 for ; Mon, 19 Jul 1999 06:46:42 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id WAA07437; Mon, 19 Jul 1999 22:46:36 +0900 (JST) Message-ID: <37932C30.3F0CAC3C@newsguy.com> Date: Mon, 19 Jul 1999 22:46:24 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: chris@calldei.com Cc: hackers@FreeBSD.ORG Subject: Re: glibc References: <19990719080712.A15178@holly.dyndns.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Costello wrote: > > What is the point of using GNU-getopt over the standard > getopt other than --foo-bar flags that everyone I know hates? Hi, I'm Daniel. Pleased to meet you. Now you know someone who doesn't hate it. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org Everything journalists write is true, except when they write about something you know. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 6:56:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id CFB1114D04 for ; Mon, 19 Jul 1999 06:56:56 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip194.houston3.tx.pub-ip.psi.net [38.12.169.194]) by leap.innerx.net (Postfix) with ESMTP id ED4F037073; Mon, 19 Jul 1999 09:53:48 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id IAA15853; Mon, 19 Jul 1999 08:54:33 -0500 (CDT) (envelope-from chris) Date: Mon, 19 Jul 1999 08:54:32 -0500 From: Chris Costello To: "Daniel C. Sobral" Cc: hackers@FreeBSD.ORG Subject: Re: glibc Message-ID: <19990719085432.B15178@holly.dyndns.org> Reply-To: chris@calldei.com References: <19990719080712.A15178@holly.dyndns.org> <37932C30.3F0CAC3C@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <37932C30.3F0CAC3C@newsguy.com>; from Daniel C. Sobral on Mon, Jul 19, 1999 at 10:46:24PM +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 19, 1999, Daniel C. Sobral wrote: > Chris Costello wrote: > > > > What is the point of using GNU-getopt over the standard > > getopt other than --foo-bar flags that everyone I know hates? > > Hi, I'm Daniel. Pleased to meet you. Now you know someone who > doesn't hate it. Good morning, Daniel! As someone more helpful than myself in this thread has already pointed out, it seems, there is a port for the GNU getopt, known as 'libgnugetopt'. I would imagine this would help the thread's originator in porting the GNU utilities to FreeBSD. -- |Chris Costello |Hardware: The parts of a computer system that can be kicked. `------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 7:55:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from voyager.fisicc-ufm.edu (ip-46-094.guate.net [200.12.46.94]) by hub.freebsd.org (Postfix) with ESMTP id E5A4314BF6 for ; Mon, 19 Jul 1999 07:55:03 -0700 (PDT) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id MAA13707 for freebsd-hackers@FreeBSD.ORG; Fri, 16 Jul 1999 12:36:49 -0600 (CST) (envelope-from obonilla) Date: Fri, 16 Jul 1999 12:36:48 -0600 From: Oscar Bonilla To: freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD Message-ID: <19990716123648.C3049@fisicc-ufm.edu> References: <19990715200336.A15050@fisicc-ufm.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <19990715200336.A15050@fisicc-ufm.edu>; from Oscar Bonilla on Thu, Jul 15, 1999 at 08:03:36PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Following up on my own post: For LDAP to be seamlessly integrated into the system some of the libraries have to be changed. Specifically the ones dealing with /etc/passwd and user information. I've decided the best way to do this is to do what's done with NIS. Basically handle the case where the user is not available in the local databases. the idea is to have an entry in the /etc/passwd enabling LDAP lookups. the Entry would be of the form ldap:*:389:389:o=My Organization, c=BR:uid:ldap.myorg.com ^^^ ^^^^^^^^^^^^^^^^^^^^^^^ ^^^ ^^^^^^^^^^^^^^ | | | | port base dn attr LDAP Server This comes ftom a pam_ldap module I got from Pedro A M Vazquez I'll change all of the function in lib/libc/gen/getpwent.c to handle this special case. The only problem is that openldap has to be integrated on the base system for this to compile... can I safely copy it to /usr/src/contrib? How do I submit this after it's done? anyone cares about ldap :)? Regards, -Oscar On Thu, Jul 15, 1999 at 08:03:36PM -0600, Oscar Bonilla wrote: > While trying to use the pam_ldap module available from www.padl.com > I discovered the following problem. > > although the module authenticates just fine (using openldap) > the login program fails to permit logins. I traced the problem to > login.c --- the following code is from login.c > > my questions are at the bottom. > > **************************************************************************** > > > pwd = getpwnam(username); > > --------- at this point pwd == NULL due to the fact that the user > --------- does not exist on the local passwd database... see below > > /* > * if we have a valid account name, and it doesn't have a > * password, or the -f option was specified and the caller > * is root or the caller isn't changing their uid, don't > * authenticate. > */ > if (pwd != NULL) { > if (pwd->pw_uid == 0) > rootlogin = 1; > > if (fflag && (uid == (uid_t)0 || > uid == (uid_t)pwd->pw_uid)) { > /* already authenticated */ > break; > } else if (pwd->pw_passwd[0] == '\0') { > if (!rootlogin || rootok) { > /* pretend password okay */ > rval = 0; > goto ttycheck; > } > } > } > > fflag = 0; > > (void)setpriority(PRIO_PROCESS, 0, -4); > > #ifndef NO_PAM > /* > * Try to authenticate using PAM. If a PAM system error > * occurs, perhaps because of a botched configuration, > * then fall back to using traditional Unix authentication. > */ > if ((rval = auth_pam()) == -1) > > ------------- This returns PAM_SUCCESS since the pam_ldap module has > ------------- successfully identified and authenticated the user. > > #endif /* NO_PAM */ > rval = auth_traditional(); > > (void)setpriority(PRIO_PROCESS, 0, 0); > > #ifndef NO_PAM > /* > * PAM authentication may have changed "pwd" to the > * entry for the template user. Check again to see if > * this is a root login after all. > */ > if (pwd != NULL && pwd->pw_uid == 0) > rootlogin = 1; > #endif /* NO_PAM */ > > ttycheck: > /* > * If trying to log in as root without Kerberos, > * but with insecure terminal, refuse the login attempt. > */ > > ------------- This next if is the problem: pwd == NULL from above, > ------------- and the user doesn't get in. > > if (pwd && !rval) { > if (rootlogin && !rootok) > refused(NULL, "NOROOT", 0); > else /* valid password & authenticated */ > break; > } > > (void)printf("Login incorrect\n"); > failures++; > > **************************************************************************** > > 1. what would be the right way to fix this? > > 2. after the user successfully logs in he still won't have an entry > in the /etc/passwd database, so all syscalls having to do with > identifying the user will fail... how can I have these funcions get > their info from LDAP? > > I'm willing to patch and submit these programs, but would like some > feedback about the right way to integrate this. > > I checked with a friend who uses linux, and it appears linux doesn't have > this problem since they use the /etc/nsswithc.conf to tell the system > where to get info from. The nsswitch (resolver?) thing seems to > understand ldap. > > Thanks folks, > > -Oscar > > -- > For PGP Public Key: finger obonilla@fisicc-ufm.edu > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- For PGP Public Key: finger obonilla@fisicc-ufm.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 8: 8:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 3EAE215171 for ; Mon, 19 Jul 1999 08:08:08 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id LAA24870; Mon, 19 Jul 1999 11:05:06 -0400 (EDT) (envelope-from luoqi) Date: Mon, 19 Jul 1999 11:05:06 -0400 (EDT) From: Luoqi Chen Message-Id: <199907191505.LAA24870@lor.watermarkgroup.com> To: dillon@apollo.backplane.com, leifn@neland.dk Subject: Re: softupdates on root partition, no floppy Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If you boot single-user, root will be mounted read-only and you should > be able to 'tunefs -n enable /dev/rda0a' and reboot. > > -Matt > Matthew Dillon > > It's a little bit simpler than that: in single user mode, tunefs -n enable / no reboot is necessary (tunefs reloads the fs after it makes changes on disk). -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 8:27:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from btm4r4.alcatel.be (btm4r4.alcatel.be [195.207.101.110]) by hub.freebsd.org (Postfix) with ESMTP id 9A8CF14A12; Mon, 19 Jul 1999 08:27:12 -0700 (PDT) (envelope-from livensw@rc.bel.alcatel.be) Received: from btmq9s.rc.bel.alcatel.be (btmq9s.rc.bel.alcatel.be [138.203.65.182]) by btm4r4.alcatel.be (8.9.1a/8.9.1) with ESMTP id RAA02284; Mon, 19 Jul 1999 17:25:52 +0200 (MET DST) Received: from btmq9z.rc.bel.alcatel.be (btmq9z [138.203.65.192]) by btmq9s.rc.bel.alcatel.be (8.8.8+Sun/8.8.8) with ESMTP id RAA20831; Mon, 19 Jul 1999 17:28:08 +0200 (MET DST) Received: (from livensw@localhost) by btmq9z.rc.bel.alcatel.be (8.8.8+Sun/8.8.8) id RAA02111; Mon, 19 Jul 1999 17:25:46 +0200 (MET DST) Date: Mon, 19 Jul 1999 17:25:46 +0200 From: Wim Livens To: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: bug in ip_forward() ? Message-ID: <19990719172546.C1676@rc.bel.alcatel.be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I suspect a bug in IP forwarding. I'm using FreeBSD 2.2.8-RELEASE. This is our network: +------+ +------+ +------+ +------+ | |4.2 4.1| |2.1 2.2| |5.1 5.2| | |btm22t|---------|btm22q|---------|btm22r|---------|btm22u| | | | | | | | | +------+ +------+ +------+ +------+ And this is what I do: btm22t# ping 192.168.5.2 ok, it works... btm22q# route delete -net 192.168.5.0 -netmask 255.255.255.252 192.168.2.2 ok, ping stops. btm22q# route add -net 192.168.5.0 -netmask 255.255.255.252 192.168.2.2 ping doesn't work btm22t# ^C btm22t# ping 192.168.5.2 ping still doesn't work btm22t# ping 192.168.5.1 (or 192.168.2.2) this ping works and suddenly the ping to 192.168.5.2 works too ! Although: btm22t# ping 192.168.5.2 ok, it works... btm22t# ^C btm22q# route delete -net 192.168.5.0 -netmask 255.255.255.252 192.168.2.2 btm22q# route add -net 192.168.5.0 -netmask 255.255.255.252 192.168.2.2 btm22t# ping 192.168.5.2 ping works! After disabling the cache in ip_forward() (netinet/ip_input.c) i.e.: sin = (struct sockaddr_in *)&ipforward_rt.ro_dst; < if ((rt = ipforward_rt.ro_rt) == 0 || < ip->ip_dst.s_addr != sin->sin_addr.s_addr ) > if (1) { ... the problem doesn't occur! Anyone has a clue what's wrong here ? Thanks a lot, Wim. ------- What follows is just some background info. Relevant routes: btm22t: 192.168/30 198.149.4.1 UGS1c 0 0 fxp0 192.168.1/30 198.149.4.1 UGS1c 0 0 fxp0 192.168.2/30 198.149.4.1 UGS1c 0 2 fxp0 192.168.4/30 link#2 UC 0 0 192.168.4.1 0:50:8b:7:50:12 UHLW 0 139 btm22q: 192.168/30 link#2 UC 0 0 192.168.0.1 link#2 UHLW 2 11 192.168.1/30 192.168.0.1 UGS1c 0 0 fxp1 192.168.2/30 link#3 UC 0 0 192.168.2.2 0:8:c7:b3:c8:c3 UHLW 1 44 fxp2 927 192.168.3/30 192.168.0.1 UGS1c 0 0 fxp1 192.168.4/30 link#1 UC 0 0 192.168.4.2 0:50:8b:7:54:2e UHLW 1 4534 fxp0 777 192.168.5/30 192.168.2.2 UGSc 0 2 fxp2 btm22r: 192.168/30 192.168.1.1 UGS1c 0 0 fxp2 192.168.1/30 link#3 UC 0 0 192.168.1.1 link#3 UHLW 1 103 192.168.2/30 link#2 UC 0 0 192.168.2.1 0:50:8b:7:49:17 UHLW 1 145 fxp1 895 192.168.4/30 192.168.2.1 UGS1c 1 21 fxp1 192.168.5/30 link#1 UC 0 0 192.168.5.2 0:50:8b:7:54:33 UHLW 0 275355 fxp0 505 btm22u: 192.168.2/30 192.168.5.1 UGS1c 0 16 fxp1 192.168.4/30 192.168.5.1 UGS1c 0 6 fxp1 192.168.5/30 link#2 UC 0 0 192.168.5.1 0:50:8b:7:49:7d UHLW 2 0 fxp1 489 dmesg on btm22q: FreeBSD 2.2.8-RELEASE #0: Fri Jul 16 15:34:52 CEST 1999 root@btm22u.rc.bel.alcatel.be:/usr/src/sys-cvs/sys/compile/CUSTOM CPU: Pentium II (quarter-micron) (348.49-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183f9ff,,MMX,< b24>> real memory = 67108864 (65536K bytes) avail memory = 63123456 (61644K bytes) altq: major number is 96 Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0:0 chip1 rev 2 on pci0:1:0 fxp0 rev 5 int a irq 11 on pci0:13:0 fxp0: Ethernet address 00:50:8b:07:50:12 fxp1 rev 5 int a irq 11 on pci0:14:0 fxp1: Ethernet address 00:50:8b:07:4b:f6 fxp2 rev 5 int a irq 11 on pci0:15:0 fxp2: Ethernet address 00:50:8b:07:49:17 chip2 rev 3 on pci0:16:0 chip3 rev 2 on pci0:20:0 chip4 rev 1 on pci0:20:1 chip5 rev 1 int d irq 11 on pci0:20:2 chip6 rev 2 on pci0:20:3 Probing for devices on PCI bus 1: vga0 rev 1 int a irq 11 on pci1:0:0 Probing for devices on PCI bus 2: de0 rev 34 int a irq 11 on pci2:4:0 de0: ZNYX ZX34X 21140A [10-100Mb/s] pass 2.2 de0: address 00:c0:95:e0:e3:70 de1 rev 34 int a irq 11 on pci2:5:0 de1: ZNYX ZX34X 21140A [10-100Mb/s] pass 2.2 de1: address 00:c0:95:e0:e3:71 de2 rev 34 int a irq 11 on pci2:6:0 de2: ZNYX ZX34X 21140A [10-100Mb/s] pass 2.2 de2: address 00:c0:95:e0:e3:72 de3 rev 34 int a irq 11 on pci2:7:0 de3: ZNYX ZX34X 21140A [10-100Mb/s] pass 2.2 de3: address 00:c0:95:e0:e3:73 Probing for PnP devices: No Plug-n-Play devices were found Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x300 psm0 not found at 0x60 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A pcm0 not found at 0xffffffff wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 4112MB (8421840 sectors), 8912 cyls, 15 heads, 63 S/T, 512 B/S fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in ep0 not found at 0x330 ep1 not found at 0x310 ep2 not found at 0x320 npx0 on motherboard npx0: INT 16 interface IP packet filtering initialized, divert enabled, default to accept, unlimited logging de0: enabling 100baseTX port de3: autosense failed: cable problem? de1: autosense failed: cable problem? de2: autosense failed: cable problem? -- Wim Livens. Alcatel - Corporate Research Center wim.livens@alcatel.be Fr. Wellesplein 1 livensw@rc.bel.alcatel.be B-2018 Antwerpen Tel: +32 3 240 7570 Belgium. Fax: +32 3 240 9932 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 8:38:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 96D9114A12 for ; Mon, 19 Jul 1999 08:38:49 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id LAA09792; Mon, 19 Jul 1999 11:46:22 -0400 (EDT) Date: Mon, 19 Jul 1999 11:46:20 -0400 (EDT) From: Alfred Perlstein To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.ORG Subject: Re: Determining the return address 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 19 Jul 1999, Dag-Erling Smorgrav wrote: > Alfred Perlstein writes: > > On 18 Jul 1999, Dag-Erling Smorgrav wrote: > > > Hmm, I ended up using a global variable which I increment at the > > > beginning of the signal handler, and decrement at the end. > > As long as you make sure the code won't have multiple access > > that would work. > > Signal handlers having multiple accesses? When did you last see that > happen? erm, can't you point multiple signal handler entries to the same routine? can't you also make it so that signals aren't defered or blocked while another handler is executing so you may actually re-enter the handler before it's complete. specifically how you say you increment it, then decrement it, if you have multiple handlers where one can interupt another you can have the counter get jumbled. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 8:43:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 379E214A12 for ; Mon, 19 Jul 1999 08:43:17 -0700 (PDT) (envelope-from kbyanc@alcnet.com) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from kbyanc (ws-41.alcnet.com [63.69.28.41]) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with SMTP id LAA25596 for ; Mon, 19 Jul 1999 11:57:47 -0400 (EDT) From: "Kelly Yancey" To: Subject: Overcommit and calloc() Date: Mon, 19 Jul 1999 11:54:05 -0400 Message-ID: <001501bed1fe$edf66980$291c453f@kbyanc.alcnet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On the other hand, I find the discussion about the merits of overcommit > and the (albeit not always in-depth) explanations of the FreeBSD VM system > educational. It would be nice if would could just extract the small amount > of signal from this discussion and put it into documentation somewhere. > Also, it has got me thinking: does FreeBSD overcommit memory allocated by > calloc()? Seems that it would be difficult since the page would > have had to > have been touched in order be zeroed, but I was curious. > I'm afraid my question got lost amongst the see of overcommit messages. :) I was curious if calloc() was overcommitted also? Or is it more fundamental than that and the kernel always overcommits memory, which processes claim via sbrk, but which, when finally touched by the app, the kernel fills with a zero'ed page. If my scenario is correct, what affect does our malloc() algorithm have, if any...in other words, is there any way to reclaim memory which was returned to the heap via free(), but which malloc() can't sbrk back to the system? Does it matter? The scenario I think of is a process malloc()'ing a large amount of memory (which is implemented by increasing the process' address space via sbrk), then malloc()'ing another chunk of memory (again, sbrk'ing). Finally, freeing the memory allocated via the first call to malloc(). Now there is a large hole in the process' address space, which presumably will be backed by swap when in fact it is useless. I can't think of any way around that, nor can I imagine it is that great of a problem, but then again, I don't know everything :) I was curious what some of the gurus thought. Thanks, Kelly ~kbyanc@posi.net~ FreeBSD - The Power To Serve - http://www.freebsd.org/ Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 8:58: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id C660E151D5 for ; Mon, 19 Jul 1999 08:58:04 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id RAA82869; Mon, 19 Jul 1999 17:57:10 +0200 (CEST) (envelope-from des) To: Alfred Perlstein Cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG Subject: Re: Determining the return address References: From: Dag-Erling Smorgrav Date: 19 Jul 1999 17:57:09 +0200 In-Reply-To: Alfred Perlstein's message of "Mon, 19 Jul 1999 11:46:20 -0400 (EDT)" Message-ID: Lines: 18 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: > erm, can't you point multiple signal handler entries to the same > routine? can't you also make it so that signals aren't defered > or blocked while another handler is executing so you may actually > re-enter the handler before it's complete. I use good ol' signal() rather than sigaction(), so no, signals can't interrupt one another's handlers. > specifically how you say you increment it, then decrement it, > if you have multiple handlers where one can interupt another > you can have the counter get jumbled. Not if increment / decrement is atomic. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 9: 2:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 017E814CF0 for ; Mon, 19 Jul 1999 09:02:26 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA40810; Mon, 19 Jul 1999 10:01:07 -0600 (MDT) (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 KAA79785; Mon, 19 Jul 1999 10:01:06 -0600 (MDT) Message-Id: <199907191601.KAA79785@harmony.village.org> Subject: Re: glibc To: Per Lundberg , hackers@FreeBSD.ORG Date: Mon, 19 Jul 1999 10:01:06 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > (most of it are due to lack of a real getopt routine). FreeBSD does have a real, 100% posix compatible getopt. Maybe you are missing one of the numerous, non-standard Linux extentions? Gnu's getopt can be found in about a dozen different places in the FreeBSD tree. cvs, tar, etc. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 9: 4:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 586E5151D5 for ; Mon, 19 Jul 1999 09:04:11 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA40814; Mon, 19 Jul 1999 10:02:36 -0600 (MDT) (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 KAA79798; Mon, 19 Jul 1999 10:02:36 -0600 (MDT) Message-Id: <199907191602.KAA79798@harmony.village.org> To: Per Lundberg Subject: Re: glibc Cc: Alex Zepeda , hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 19 Jul 1999 14:58:43 +0200." References: Date: Mon, 19 Jul 1999 10:02:36 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Per Lundberg writes: : I know it isn't standard. But it works well, and is used by a lot of : programs. Perhaps it should have been put in another library than libc, : though. Actually, I'd better suggest this to the GNU people right ahead. There has been talking of having a libgnu.a to contain common routines like the long getopt... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 9: 4:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 90518151D5 for ; Mon, 19 Jul 1999 09:04:18 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA40821; Mon, 19 Jul 1999 10:03:03 -0600 (MDT) (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 KAA79813; Mon, 19 Jul 1999 10:03:03 -0600 (MDT) Message-Id: <199907191603.KAA79813@harmony.village.org> To: chris@calldei.com Subject: Re: glibc Cc: Per Lundberg , Alex Zepeda , hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 19 Jul 1999 08:07:13 CDT." <19990719080712.A15178@holly.dyndns.org> References: <19990719080712.A15178@holly.dyndns.org> Date: Mon, 19 Jul 1999 10:03:02 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990719080712.A15178@holly.dyndns.org> Chris Costello writes: : getopt other than --foo-bar flags that everyone I know hates? Not everyone hates them... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 9: 5:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from abraham.chaosdev.org (chaosdev.org [194.17.41.8]) by hub.freebsd.org (Postfix) with ESMTP id 86E52151EF for ; Mon, 19 Jul 1999 09:05:53 -0700 (PDT) (envelope-from plundis@chaosdev.org) Received: from localhost (plundis@localhost) by abraham.chaosdev.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id SAA15926; Mon, 19 Jul 1999 18:05:51 +0200 Date: Mon, 19 Jul 1999 18:05:50 +0200 (CEST) From: Per Lundberg To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: glibc In-Reply-To: <199907191602.KAA79798@harmony.village.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, 19 Jul 1999, Warner Losh wrote: > There has been talking of having a libgnu.a to contain common > routines like the long getopt... Yeah, I was thinking about something like that. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 9: 7:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id D6EFF151E6 for ; Mon, 19 Jul 1999 09:07:13 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id SAA83131; Mon, 19 Jul 1999 18:06:37 +0200 (CEST) (envelope-from des) To: "Kelly Yancey" Cc: Subject: Re: Overcommit and calloc() References: <001501bed1fe$edf66980$291c453f@kbyanc.alcnet.com> From: Dag-Erling Smorgrav Date: 19 Jul 1999 18:06:37 +0200 In-Reply-To: "Kelly Yancey"'s message of "Mon, 19 Jul 1999 11:54:05 -0400" Message-ID: Lines: 25 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kelly Yancey" writes: > I'm afraid my question got lost amongst the see of overcommit messages. :) > I was curious if calloc() was overcommitted also? Here's our calloc() implementation: void * calloc(num, size) size_t num; register size_t size; { register void *p; size *= num; if ( (p = malloc(size)) ) bzero(p, size); return(p); } so the answer is yes, it overcommits, but the bzero() may cause the system to run out of swap. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 9:15:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 8CE311520D for ; Mon, 19 Jul 1999 09:15:43 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id SAA83293; Mon, 19 Jul 1999 18:13:52 +0200 (CEST) (envelope-from des) To: Oscar Bonilla Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD References: <19990715200336.A15050@fisicc-ufm.edu> <19990716123648.C3049@fisicc-ufm.edu> From: Dag-Erling Smorgrav Date: 19 Jul 1999 18:13:51 +0200 In-Reply-To: Oscar Bonilla's message of "Fri, 16 Jul 1999 12:36:48 -0600" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oscar Bonilla writes: > the idea is to have an entry in the /etc/passwd enabling LDAP lookups. > the Entry would be of the form > > ldap:*:389:389:o=My Organization, c=BR:uid:ldap.myorg.com Horrible idea. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 9:17:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from voyager.fisicc-ufm.edu (ip-46-094.guate.net [200.12.46.94]) by hub.freebsd.org (Postfix) with ESMTP id C76BC151D5 for ; Mon, 19 Jul 1999 09:17:51 -0700 (PDT) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id KAA03454; Mon, 19 Jul 1999 10:17:14 -0600 (CST) (envelope-from obonilla) Date: Mon, 19 Jul 1999 10:17:13 -0600 From: Oscar Bonilla To: Dag-Erling Smorgrav Cc: Oscar Bonilla , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD Message-ID: <19990719101713.A3438@fisicc-ufm.edu> References: <19990715200336.A15050@fisicc-ufm.edu> <19990716123648.C3049@fisicc-ufm.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Dag-Erling Smorgrav on Mon, Jul 19, 1999 at 06:13:51PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 19, 1999 at 06:13:51PM +0200, Dag-Erling Smorgrav wrote: > Oscar Bonilla writes: > > the idea is to have an entry in the /etc/passwd enabling LDAP lookups. > > the Entry would be of the form > > > > ldap:*:389:389:o=My Organization, c=BR:uid:ldap.myorg.com > > Horrible idea. > suggestions? -Oscar -- For PGP Public Key: finger obonilla@fisicc-ufm.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 9:23: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 7C8F114D37 for ; Mon, 19 Jul 1999 09:23:01 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id SAA83528; Mon, 19 Jul 1999 18:22:17 +0200 (CEST) (envelope-from des) To: Oscar Bonilla Cc: Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD References: <19990715200336.A15050@fisicc-ufm.edu> <19990716123648.C3049@fisicc-ufm.edu> <19990719101713.A3438@fisicc-ufm.edu> From: Dag-Erling Smorgrav Date: 19 Jul 1999 18:22:17 +0200 In-Reply-To: Oscar Bonilla's message of "Mon, 19 Jul 1999 10:17:13 -0600" Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oscar Bonilla writes: > On Mon, Jul 19, 1999 at 06:13:51PM +0200, Dag-Erling Smorgrav wrote: > > Oscar Bonilla writes: > > > the idea is to have an entry in the /etc/passwd enabling LDAP lookups. > > > the Entry would be of the form > > > > > > ldap:*:389:389:o=My Organization, c=BR:uid:ldap.myorg.com > > Horrible idea. > suggestions? /etc/auth.conf DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 9:30:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 7AC3D151D5 for ; Mon, 19 Jul 1999 09:30:16 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id MAA08438; Mon, 19 Jul 1999 12:29:52 -0400 (EDT) Message-Id: <199907191629.MAA08438@cs.rpi.edu> To: Oscar Bonilla Cc: freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: PAM & LDAP in FreeBSD, and userfs too. In-Reply-To: Message from Oscar Bonilla of "Fri, 16 Jul 1999 12:36:48 MDT." <19990716123648.C3049@fisicc-ufm.edu> Date: Mon, 19 Jul 1999 12:29:48 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I thought now would be a good time to chime in on some of my wild schemes... The reason I am interested in 'userfs' is to enable me to write a version of 'nsd'. Those of you familiar with Irix will recognize it. For others, what it does is to present the name-space on a machine as filespace. The advantages of this is that we can greatly simplify out libc to use the file/namespace that nsd provides. For example 'getpwent()' now becomes file accesses to /ns/.local/passwd/NAME. Another advantage that this abstraction provides is that it allows transparent alterations of the databases in use, even to the extent of NOT having to restart each client that may be using a specific database. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 9:33:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id CF5071521A for ; Mon, 19 Jul 1999 09:33:36 -0700 (PDT) (envelope-from kbyanc@alcnet.com) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from kbyanc (ws-41.alcnet.com [63.69.28.41]) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with SMTP id MAA26728; Mon, 19 Jul 1999 12:47:45 -0400 (EDT) From: "Kelly Yancey" To: "Dag-Erling Smorgrav" Cc: Subject: RE: Overcommit and calloc() Date: Mon, 19 Jul 1999 12:44:03 -0400 Message-ID: <001f01bed205$e8aeecc0$291c453f@kbyanc.alcnet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ahh...but wouldn't the bzero() touch all of the memory just allocated functionally making it non-overcommit? I realize that technically it isn't the same since although calloc() would ensure the memory actually was committed (again, since the bzero() touches all the pages), if there weren't enough pages free then a random process would still be killed rather than returning null. Believe me, I'm not trying to start that war again :) I'm just pointing out that while technically it is still overcommit, it will touch the pages ensuring that the memory does in fact exist (is committed). Perhaps this is why I've always heard we should avoid calloc() because it is 'slow'? Thanks for the great feedback, I should kick myself for now digging my hands in the mud myself (I assumed it was more complicated than that :) ). Kelly ~kbyanc@posi.net~ FreeBSD - The Power To Serve - http://www.freebsd.org/ Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD > -----Original Message----- > From: Dag-Erling Smorgrav [mailto:des@flood.ping.uio.no] > Sent: Monday, July 19, 1999 12:07 PM > To: Kelly Yancey > Cc: hackers@FreeBSD.ORG > Subject: Re: Overcommit and calloc() > > > "Kelly Yancey" writes: > > I'm afraid my question got lost amongst the see of overcommit > messages. :) > > I was curious if calloc() was overcommitted also? > > Here's our calloc() implementation: > > void * > calloc(num, size) > size_t num; > register size_t size; > { > register void *p; > > size *= num; > if ( (p = malloc(size)) ) > bzero(p, size); > return(p); > } > > so the answer is yes, it overcommits, but the bzero() may cause the > system to run out of swap. > > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 9:34: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 81C241521F for ; Mon, 19 Jul 1999 09:34:03 -0700 (PDT) (envelope-from rminnich@acl.lanl.gov) Received: from tbp.acl.lanl.gov (root@tbp.acl.lanl.gov [128.165.147.10]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id KAA07264 for ; Mon, 19 Jul 1999 10:33:19 -0600 (MDT) Received: from localhost (rminnich@localhost) by tbp.acl.lanl.gov (8.8.7/8.8.8) with ESMTP id KAA27395 for ; Mon, 19 Jul 1999 10:32:56 -0600 X-Authentication-Warning: tbp.acl.lanl.gov: rminnich owned process doing -bs Date: Mon, 19 Jul 1999 10:32:56 -0600 (MDT) From: "Ronald G. Minnich" To: freebsd-hackers@FreeBSD.ORG Subject: Re: USFS (User Space File System) 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, 18 Jul 1999, Boris Popov wrote: > On Sat, 17 Jul 1999, David E. Cross wrote: > > I am looking at a project that will require a user based process to interact > > with the system as if it were a filesystem. The traditional way I have seen > > That type of file system is very useful for simple tasks. A while > ago I'm experementing with 'IPX network browser' which shows NetWare > servers as directories and allows to go down to see volumes, print queues > etc. > It would be nice if we're have something like 'userfs' (or > 'daemonfs') with unified interface and mount command like this: > > # mount_user /mydaemon /mountpoint > > so, all that I need to create a new file system is to write > 'mydaemon' program. Great idea. I liked it so much I bought the company -- er, I mean, I wrote something like this. It's private name spaces for Linux and FreeBSD (among others) and it allows you to mount things from remote file servers into your name space. There's a technical paper at www.acl.lanl.gov/~rminnich that is a brief overview. I'll get longer technical papers and such out there this week I hope. Writing servers is pretty easy, I have two reference implementations. In fact one server is a .c file plus a server library, so the actual server is quite small. Remaining task is to get a VFS for FreeBSD. The v9fs is a start but I need help getting the rest done. It's pretty easy to do though -- I was amazed at how quickly the Linux version went once I had a v9fs-like VFS for Linux. If interested let me know. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 9:41:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 3BF5014E26 for ; Mon, 19 Jul 1999 09:40:50 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id SAA83917; Mon, 19 Jul 1999 18:39:16 +0200 (CEST) (envelope-from des) To: "Kelly Yancey" Cc: "Dag-Erling Smorgrav" , Subject: Re: Overcommit and calloc() References: <001f01bed205$e8aeecc0$291c453f@kbyanc.alcnet.com> From: Dag-Erling Smorgrav Date: 19 Jul 1999 18:39:15 +0200 In-Reply-To: "Kelly Yancey"'s message of "Mon, 19 Jul 1999 12:44:03 -0400" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kelly Yancey" writes: > Ahh...but wouldn't the bzero() touch all of the memory just allocated > functionally making it non-overcommit? No. If it were an "non-overcomitting malloc", it would return NULL and set errno to ENOMEM, instead of dumping core. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 9:46:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 45DEB14E2D for ; Mon, 19 Jul 1999 09:46:40 -0700 (PDT) (envelope-from rminnich@acl.lanl.gov) Received: from tbp.acl.lanl.gov (root@tbp.acl.lanl.gov [128.165.147.10]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id KAA08004 for ; Mon, 19 Jul 1999 10:45:21 -0600 (MDT) Received: from localhost (rminnich@localhost) by tbp.acl.lanl.gov (8.8.7/8.8.8) with ESMTP id KAA27425 for ; Mon, 19 Jul 1999 10:44:58 -0600 X-Authentication-Warning: tbp.acl.lanl.gov: rminnich owned process doing -bs Date: Mon, 19 Jul 1999 10:44:58 -0600 (MDT) From: "Ronald G. Minnich" To: freebsd-hackers@FreeBSD.ORG Subject: Re: USFS (User Space File System) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, Ronald G. Minnich wrote: > Great idea. I liked it so much I bought the company -- er, I mean, I wrote > something like this. It's private name spaces for Linux and FreeBSD (among > others) and it allows you to mount things from remote file servers into > your name space. I forgot to make this clear: it's a full-fledged VFS on linux supporting things like mmap etc. It is indistinguishable to any process as being anything other than a file system -- because it is a file system. It's just that mounts into the file system are controlled by your process, not by /etc/fstab. Different groups of processes can have totally different sets of mount points. In fact one test is to have a login that does a chroot to a totally empty tree. You then mount things like /usr/bin, etc. into your private tree and at that point all programs run quite normally. If you want ou even get translucent file system behaviour for free, since the file system supports union mounts and the Plan 9 semantics are that the "top" mount is where files get created. A user can thus have read-only mounts from a server or servers somewhere, mount local disk on top, and voila: all new files are local. This would also support booting from a CDROM and running even though the local disk is either nonexistant or empty of any system files. Stacking comes for free too, of course. ron p.s. I looked at the "VOP upcall" idea but there's lots of interesting issues as regards parameters in the VOP structures being handed out to a user process and then back to the kernel. I'm not sure it's a good idea. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 9:55: 2 1999 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 0856215250 for ; Mon, 19 Jul 1999 09:54:56 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id LAA46290; Mon, 19 Jul 1999 11:54:50 -0500 (CDT) (envelope-from dan) Date: Mon, 19 Jul 1999 11:54:50 -0500 From: Dan Nelson To: Dag-Erling Smorgrav Cc: Kelly Yancey , freebsd-hackers@FreeBSD.ORG Subject: Re: Overcommit and calloc() Message-ID: <19990719115450.A45503@dan.emsphone.com> References: <001f01bed205$e8aeecc0$291c453f@kbyanc.alcnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from "Dag-Erling Smorgrav" on Mon Jul 19 18:39:15 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jul 19), Dag-Erling Smorgrav said: > "Kelly Yancey" writes: > > Ahh...but wouldn't the bzero() touch all of the memory just > > allocated functionally making it non-overcommit? > > No. If it were an "non-overcomitting malloc", it would return NULL > and set errno to ENOMEM, instead of dumping core. It should be possible to modify calloc to trap signals, then bzero. If bzero faults, you free the memory and return NULL. No, wait. You can't trap SIGKILL. How about this. mmap() some anonymous memory MAP_SHARED, fork a child to bzero it. If the child dies, unmmap and return NULL. If the child succeeds, use the memory. This memory won't be freeable with malloc(), though. -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 Mon Jul 19 10:16:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 0254914CB1; Mon, 19 Jul 1999 10:16:25 -0700 (PDT) From: "Jonathan M. Bresler" To: rbezuide@oskar.nanoteq.co.za Cc: vince@venus.GAIANET.NET, sthaug@nethelp.no, tim@storm.digital-rain.com, freebsd-hackers@FreeBSD.ORG In-reply-to: <199907190816.KAA22986@oskar.nanoteq.co.za> (message from Reinier Bezuidenhout on Mon, 19 Jul 1999 10:16:47 +0200 (SAT)) Subject: Re: poor ethernet performance? Message-Id: <19990719171625.0254914CB1@hub.freebsd.org> Date: Mon, 19 Jul 1999 10:16:25 -0700 (PDT) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We have previously done many network performance tests for our > products running on FreeBSD ... > > We have found that when ever there is disk accessing involved, it > is not a good idea to look at the transfer figures. We did tests > with ftp and is was slow (compared to only memory generated data > e.g. ttcp) > > 1. If you want to test the network speed ... use ttcp or something > that generates the data and doesn't read it from disk. > absolutely right. netperf generates its own data on the fly. it does not generate any disk activity. > 2. When doing full-duplex and using fxp cards, stay away from X-over > cables ... use a full-duplex switch etc. ... the fxp cards are not > made to work with X-over cables (as far as I know - ala Intel spec) > note ... only for full-duplex tests. hmm....i have used intel cards on a cross-over cable regularly without any problems whatsoever. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 10:18:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 0624314CB1 for ; Mon, 19 Jul 1999 10:18:23 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id NAA41144; Mon, 19 Jul 1999 13:17:30 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Mon, 19 Jul 1999 13:17:30 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Per Lundberg Cc: Alex Zepeda , hackers@FreeBSD.org Subject: Re: glibc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, Per Lundberg wrote: > On Mon, 19 Jul 1999, Alex Zepeda wrote: > > > It's quite easily argued that depending on a *NON STANDARD* getopt routine > > is a bug. > > I know it isn't standard. But it works well, and is used by a lot of > programs. Perhaps it should have been put in another library than libc, > though. Actually, I'd better suggest this to the GNU people right ahead. If you give me documentation on it, I'll implement it for the BSD libc. It would be nice to go in, perhaps as a weak symbol (to remain compatible with FreeBSD packages including their own getopt.) And don't tell me to look at the getopt long code itself. That stuff is sickening. I just want the [exact] API. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ 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 Mon Jul 19 10:24:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id E4C6C14CB1 for ; Mon, 19 Jul 1999 10:24:29 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id NAA41274; Mon, 19 Jul 1999 13:23:44 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Mon, 19 Jul 1999 13:23:43 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Warner Losh Cc: Per Lundberg , Alex Zepeda , hackers@FreeBSD.org Subject: Re: glibc In-Reply-To: <199907191602.KAA79798@harmony.village.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, 19 Jul 1999, Warner Losh wrote: > In message Per Lundberg writes: > : I know it isn't standard. But it works well, and is used by a lot of > : programs. Perhaps it should have been put in another library than libc, > : though. Actually, I'd better suggest this to the GNU people right ahead. > > There has been talking of having a libgnu.a to contain common > routines like the long getopt... How about libcompat/gnu/? > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ 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 Mon Jul 19 10:30:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from unix2.it-datacntr.louisville.edu (unix2.it-datacntr.louisville.edu [136.165.4.28]) by hub.freebsd.org (Postfix) with ESMTP id BF94215149 for ; Mon, 19 Jul 1999 10:30:30 -0700 (PDT) (envelope-from k.stevenson@louisville.edu) Received: from homer.louisville.edu (ktstev01@homer.louisville.edu [136.165.1.20]) by unix2.it-datacntr.louisville.edu (8.8.8/8.8.8) with ESMTP id NAA32610 for ; Mon, 19 Jul 1999 13:28:59 -0400 Received: (from ktstev01@localhost) by homer.louisville.edu (8.8.8/8.8.8) id NAA28665 for freebsd-hackers@freebsd.org; Mon, 19 Jul 1999 13:29:41 -0400 (EDT) Message-ID: <19990719132941.A28478@homer.louisville.edu> Date: Mon, 19 Jul 1999 13:29:41 -0400 From: Keith Stevenson To: freebsd-hackers@freebsd.org Subject: Re: PAM & LDAP in FreeBSD References: <19990715200336.A15050@fisicc-ufm.edu> <19990716123648.C3049@fisicc-ufm.edu> <19990719101713.A3438@fisicc-ufm.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Dag-Erling Smorgrav on Mon, Jul 19, 1999 at 06:22:17PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 19, 1999 at 06:22:17PM +0200, Dag-Erling Smorgrav wrote: > Oscar Bonilla writes: > > On Mon, Jul 19, 1999 at 06:13:51PM +0200, Dag-Erling Smorgrav wrote: > > > Oscar Bonilla writes: > > > > the idea is to have an entry in the /etc/passwd enabling LDAP lookups. > > > > the Entry would be of the form > > > > > > > > ldap:*:389:389:o=My Organization, c=BR:uid:ldap.myorg.com > > > Horrible idea. > > suggestions? > > /etc/auth.conf > Given that this is a PAM module, wouldn't /etc/pam.conf be more appropriate? Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.stevenson@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 10:49:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id D667415243; Mon, 19 Jul 1999 10:49:27 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id KAA23392; Mon, 19 Jul 1999 10:49:25 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA66533; Mon, 19 Jul 1999 10:49:25 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Mon, 19 Jul 1999 10:49:25 -0700 (PDT) Message-Id: <199907191749.KAA66533@vashon.polstra.com> To: green@freebsd.org Subject: Re: glibc In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Brian F. Feldman wrote: > [GNU getopt] > If you give me documentation on it, I'll implement it for the BSD libc. Note, we already have GNU getopt in the source tree in libiberty (in two different places -- binutils and gdb). It might be better just to install libiberty from one of those places. Left as an exercise for the reader: Figure out how the two differ and which one is "better". :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 10:55:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id DA3FE15287 for ; Mon, 19 Jul 1999 10:55:44 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id NAA41881; Mon, 19 Jul 1999 13:55:30 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Mon, 19 Jul 1999 13:55:30 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: John Polstra Cc: hackers@FreeBSD.org Subject: Re: glibc In-Reply-To: <199907191749.KAA66533@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, John Polstra wrote: > In article , > Brian F. Feldman wrote: > > > [GNU getopt] > > If you give me documentation on it, I'll implement it for the BSD libc. > > Note, we already have GNU getopt in the source tree in libiberty (in > two different places -- binutils and gdb). It might be better just > to install libiberty from one of those places. But it would be nice to have a free long getopt implementation. > > Left as an exercise for the reader: Figure out how the two differ > and which one is "better". :-) I'd rather hurt myself severely. Wait a second, that's exactly what I'd be doing in the first place to do what you asked! Hm.... > > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "No matter how cynical I get, I just can't keep up." -- Nora Ephron > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ 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 Mon Jul 19 10:59:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 3EA0C15318; Mon, 19 Jul 1999 10:59:25 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id KAA23440; Mon, 19 Jul 1999 10:58:08 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA66575; Mon, 19 Jul 1999 10:58:04 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 19 Jul 1999 10:58:04 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: "Brian F. Feldman" Subject: Re: glibc Cc: hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian F. Feldman wrote: > On Mon, 19 Jul 1999, John Polstra wrote: > >> Left as an exercise for the reader: Figure out how the two differ >> and which one is "better". :-) > > I'd rather hurt myself severely. Of course. That's a prerequisite for becoming a committer. :-) John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 11: 9:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mom.hooked.net (mom.hooked.net [206.80.6.10]) by hub.freebsd.org (Postfix) with ESMTP id A0F4015254 for ; Mon, 19 Jul 1999 11:09:14 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from fish.hooked.net (garbanzo@fish.hooked.net [206.80.6.48]) by mom.hooked.net (8.8.6/8.8.5) with SMTP id KAA22584; Mon, 19 Jul 1999 10:59:25 -0700 (PDT) Date: Mon, 19 Jul 1999 10:59:24 -0700 (PDT) From: Alex Zepeda To: Warner Losh Cc: chris@calldei.com, Per Lundberg , hackers@FreeBSD.ORG Subject: Re: glibc In-Reply-To: <199907191603.KAA79813@harmony.village.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, 19 Jul 1999, Warner Losh wrote: > In message <19990719080712.A15178@holly.dyndns.org> Chris Costello writes: > : getopt other than --foo-bar flags that everyone I know hates? > > Not everyone hates them... Sure, I don't hate them either... until I try and port something that depends on them. Then I get annoyed. Some sort of compatible extension should be devised, so that a small block of code could be ifdef'd to provide support for long options, and the rest would work with a standard getopt routine. - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 11:42: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id C77F414F19 for ; Mon, 19 Jul 1999 11:42:02 -0700 (PDT) (envelope-from kbyanc@alcnet.com) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from kbyanc (ws-41.alcnet.com [63.69.28.41]) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with SMTP id OAA29440; Mon, 19 Jul 1999 14:56:36 -0400 (EDT) From: "Kelly Yancey" To: "Dag-Erling Smorgrav" Cc: Subject: RE: Overcommit and calloc() Date: Mon, 19 Jul 1999 14:52:55 -0400 Message-ID: <002201bed217$e94beae0$291c453f@kbyanc.alcnet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Dag-Erling Smorgrav [mailto:des@flood.ping.uio.no] > Sent: Monday, July 19, 1999 12:39 PM > To: Kelly Yancey > Cc: Dag-Erling Smorgrav; freebsd-hackers@freebsd.org > Subject: Re: Overcommit and calloc() > > > "Kelly Yancey" writes: > > Ahh...but wouldn't the bzero() touch all of the memory just allocated > > functionally making it non-overcommit? > > No. If it were an "non-overcomitting malloc", it would return NULL and > set errno to ENOMEM, instead of dumping core. > I guess I was looking at it from the commitment of memory point-of-view. Calloc() calls malloc() to get the memory (which will overcommit); calloc() then touches every page of the memory using bzero(). The memory itself will be committed. The only aspect of non-overcommit that it doesn't do is kindly tell the process if it couldn't touch every page, instead the overcommit model kills a process to reclaim pages so the bzero() will succeed (assuming we're not the unfortunate process :) ). You are absolutely right, calloc() doesn't act like a non-overcommit calloc() would, but it does in fact commit the memory. I don't know how many programs make use of calloc() but would not a more efficient algorithm be to better integrate it with malloc() such that if there is a fragment on the heap which can be used, bzero() it and return that, otherwise, simply call sbrk() and return that (since it is already zero'ed). Currently, in the event that malloc() simply returns newly sbrk()'ed memory, we unnecessarily zero it again. And yes, if the majority of people think this is worthwhile and I'm not just complete wrong here, then I'm glad to submit the patches. Kelly ~kbyanc@posi.net~ FreeBSD - The Power To Serve - http://www.freebsd.org/ Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 11:48:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (Postfix) with ESMTP id E796814F30 for ; Mon, 19 Jul 1999 11:48:15 -0700 (PDT) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA230404906; Mon, 19 Jul 1999 10:35:06 -0400 Date: Mon, 19 Jul 1999 10:35:06 -0400 (EDT) From: Bill Fumerola To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: telnetd In-Reply-To: <199907171932.NAA64473@harmony.village.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 Sat, 17 Jul 1999, Warner Losh wrote: > What purpose is served by the twisty maze of ifdefs in telnetd? I'd > like to unifdef many of them. I'm trying to track down a bug and the > twisty maze makes it very hard to follow. Comments? There seem to be some fairly stupid ones in src/sbin too. ./dump/optr.c:#if __STDC__ ./init/init.c:#ifdef __STDC__ ./newfs/mkfs.c:#ifdef __ELF__ ./newfs/newfs.c:#if __STDC__ ./mount_ntfs/mount_ntfs.c:#if __FreeBSD_version >= 300000 [...] how likely are the above to change. (some of them will never change, considering what branch they're on.) - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@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 Jul 19 11:53:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 2D3F714F38 for ; Mon, 19 Jul 1999 11:53:13 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA00408; Mon, 19 Jul 1999 11:45:12 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907191845.LAA00408@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: mjacob@feral.com Cc: Mike Smith , "Daniel C. Sobral" , freebsd-hackers@FreeBSD.ORG Subject: Re: System unique identifier..... In-reply-to: Your message of "Sun, 18 Jul 1999 17:55:24 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Jul 1999 11:45:11 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Mike Smith wrote: > > > > > > > > The loader will, at some stage in the future, grow a persistent data > > > > store in which items like this can be saved. > > > > > > Doesn't /boot/[defaults/]loader.conf[.local] qualify as persistent > > > data storage? > > > > There is little or no chance that the loader will gain the ability to > > write back to filesystems. Some of them don't support it (eg. > > iso9660), others may not (TFTP, NFS), and the code required for some of > > them (especially UFS) would be problematically large. > > But that's okay. If the persistent storage is the loader conf files, they > can be updated from single or multi-user mode. There are cases where they need to be updated _by_the_loader_; see eg. the "nextboot" manpage for functionality that we have currently lost. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 11:54: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5C97214F38 for ; Mon, 19 Jul 1999 11:54:05 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id EAA00964; Mon, 19 Jul 1999 04:50:50 -0700 Date: Mon, 19 Jul 1999 11:51:50 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: "Daniel C. Sobral" , freebsd-hackers@FreeBSD.ORG Subject: Re: System unique identifier..... In-Reply-To: <199907191845.LAA00408@dingo.cdrom.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 > > > > Mike Smith wrote: > > > > > > > > > > The loader will, at some stage in the future, grow a persistent data > > > > > store in which items like this can be saved. > > > > > > > > Doesn't /boot/[defaults/]loader.conf[.local] qualify as persistent > > > > data storage? > > > > > > There is little or no chance that the loader will gain the ability to > > > write back to filesystems. Some of them don't support it (eg. > > > iso9660), others may not (TFTP, NFS), and the code required for some of > > > them (especially UFS) would be problematically large. > > > > But that's okay. If the persistent storage is the loader conf files, they > > can be updated from single or multi-user mode. > > There are cases where they need to be updated _by_the_loader_; see eg. > the "nextboot" manpage for functionality that we have currently lost. So much the better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 12:13: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 68C6515149 for ; Mon, 19 Jul 1999 12:13:05 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA00611; Mon, 19 Jul 1999 12:06:40 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907191906.MAA00611@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Per Lundberg Cc: Alex Zepeda , hackers@FreeBSD.ORG Subject: Re: glibc In-reply-to: Your message of "Mon, 19 Jul 1999 09:38:54 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Jul 1999 12:06:40 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 18 Jul 1999, Alex Zepeda wrote: > > > Perhaps if you explain what it is you're trying to accomplish, there might > > be an easier option than porting *shudder* glibc? > > I need a libc 100% compatible with glibc to make porting (from Linux) > easier. And, as a side note, I think both FreeBSD and Linux would benefit > of having compatible libc:s. Uh, if you are using libc correctly, there should be no porting issues at all. > Perhaps porting BSD libc to Linux would be easier? Perhaps you should just fix the applications in the first place? -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 12:13:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 0FCCB14DBC; Mon, 19 Jul 1999 12:13:05 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id MAA09158; Mon, 19 Jul 1999 12:11:09 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id MAA25244; Mon, 19 Jul 1999 12:10:57 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA20769; Mon, 19 Jul 99 12:11:02 PDT Message-Id: <37937846.55C1867E@softweyr.com> Date: Mon, 19 Jul 1999 13:11:02 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Wim Livens Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: bug in ip_forward() ? References: <19990719172546.C1676@rc.bel.alcatel.be> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wim Livens wrote: > > I suspect a bug in IP forwarding. I'm using FreeBSD 2.2.8-RELEASE. > > This is our network: > > +------+ +------+ +------+ +------+ > | |4.2 4.1| |2.1 2.2| |5.1 5.2| | > |btm22t|---------|btm22q|---------|btm22r|---------|btm22u| > | | | | | | | | > +------+ +------+ +------+ +------+ > > And this is what I do: > > btm22t# ping 192.168.5.2 > ok, it works... > btm22q# route delete -net 192.168.5.0 -netmask 255.255.255.252 192.168.2.2 > ok, ping stops. > btm22q# route add -net 192.168.5.0 -netmask 255.255.255.252 192.168.2.2 > ping doesn't work And it shouldn't, you haven't given it an appropriate route. From route(8): The other commands have the following syntax: route [-n] command [-net | -host] destination gateway where destination is the destination host or network, gateway is the next-hop intermediary via which packets should be routed. There's the important part right there: gateway is the *next-hop* intermediary via which packets should be routed. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 12:38:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 12BE314F7D for ; Mon, 19 Jul 1999 12:38:46 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA00741; Mon, 19 Jul 1999 12:31:50 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907191931.MAA00741@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Luoqi Chen Cc: dillon@apollo.backplane.com, leifn@neland.dk, hackers@FreeBSD.ORG Subject: Re: softupdates on root partition, no floppy In-reply-to: Your message of "Mon, 19 Jul 1999 11:05:06 EDT." <199907191505.LAA24870@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Jul 1999 12:31:50 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If you boot single-user, root will be mounted read-only and you should > > be able to 'tunefs -n enable /dev/rda0a' and reboot. > > > > -Matt > > Matthew Dillon > > > > > It's a little bit simpler than that: in single user mode, tunefs -n enable / > no reboot is necessary (tunefs reloads the fs after it makes changes on disk). Unfortunately it doesn't first check to see if the fs is already loaded (so the reload generates a scary error message on all the other fs'es). -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 12:39:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 28F8B15286 for ; Mon, 19 Jul 1999 12:39:14 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA00760; Mon, 19 Jul 1999 12:33:53 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907191933.MAA00760@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Oscar Bonilla Cc: Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD In-reply-to: Your message of "Mon, 19 Jul 1999 10:17:13 MDT." <19990719101713.A3438@fisicc-ufm.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Jul 1999 12:33:53 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, Jul 19, 1999 at 06:13:51PM +0200, Dag-Erling Smorgrav wrote: > > Oscar Bonilla writes: > > > the idea is to have an entry in the /etc/passwd enabling LDAP lookups. > > > the Entry would be of the form > > > > > > ldap:*:389:389:o=My Organization, c=BR:uid:ldap.myorg.com > > > > Horrible idea. > > > > suggestions? Use PAM. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 12:42:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 6C48A15286 for ; Mon, 19 Jul 1999 12:42:17 -0700 (PDT) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id VAA14708; Mon, 19 Jul 1999 21:41:11 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <012801bed21e$bafdce40$0e00a8c0@neland.dk> From: "Leif Neland" To: "Stephen McKay" Cc: References: <199907172306.QAA81618@apollo.backplane.com> <199907190725.RAA13642@nymph.detir.qld.gov.au> Subject: Sv: softupdates on root partition, no floppy Date: Mon, 19 Jul 1999 21:39:08 +0200 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 From: Stephen McKay > On Saturday, 17th July 1999, Matthew Dillon wrote: > > >:Is there any way to force softupdate on on a mounted system, or do I have to > >:either move the / to another machine, or move a floppydrive to this machine? > > > > If you boot single-user, root will be mounted read-only and you should > > be able to 'tunefs -n enable /dev/rda0a' and reboot. > > I gave up using soft updates on root because of the delayed delete > behaviour. I kept filling up root while updating kernels. It doesn't > gain you much on little used file systems anyway. So, I recommend > people leave root alone. > Well, this disk is 4G and has only one partition, containing both / and /usr, so I think I may benefit from softupdates. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 12:44:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id DC4561523C for ; Mon, 19 Jul 1999 12:44:52 -0700 (PDT) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Mon, 19 Jul 1999 20:43:48 +0100 Received: from voodoo.pandhm.co.uk (VOODOO [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id 3WRWC6WG; Mon, 19 Jul 1999 20:44:35 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 116JKk-0001WN-00; Mon, 19 Jul 1999 20:44:18 +0100 Date: Mon, 19 Jul 1999 20:44:18 +0100 To: "David E. Cross" Cc: Oscar Bonilla , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD, and userfs too. Message-Id: <19990719204417.A5796@palmerharvey.co.uk> References: <199907191629.MAA08438@cs.rpi.edu> MIME-Version: 1.0 X-Mailer: Mutt 0.95.6i In-Reply-To: <199907191629.MAA08438@cs.rpi.edu>; from David E. Cross on Mon, Jul 19, 1999 at 12:29:48PM -0400 From: Dominic Mitchell Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 19, 1999 at 12:29:48PM -0400, David E. Cross wrote: > I thought now would be a good time to chime in on some of my wild schemes... > > The reason I am interested in 'userfs' is to enable me to write a version > of 'nsd'. Those of you familiar with Irix will recognize it. For others, > what it does is to present the name-space on a machine as filespace. > The advantages of this is that we can greatly simplify out libc to use the > file/namespace that nsd provides. For example 'getpwent()' now becomes > file accesses to /ns/.local/passwd/NAME. Another advantage that this > abstraction provides is that it allows transparent alterations of the > databases in use, even to the extent of NOT having to restart each client > that may be using a specific database. Lovely. Sounds like a much better way to do the Solaris/Linux (and NetBSD?) /etc/nsswitch.conf stuff. On Solaris at least, this is implemented using masses of weird shared objects... -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator In Mountain View did Larry Wall Sedately launch a quiet plea: That DOS, the ancient system, shall On boxes pleasureless to all Run Perl though lack they C. -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 12:50: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 69A3F15239 for ; Mon, 19 Jul 1999 12:50:03 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id PAA12399; Mon, 19 Jul 1999 15:47:37 -0400 (EDT) Message-Id: <199907191947.PAA12399@cs.rpi.edu> To: Mike Smith Cc: Oscar Bonilla , Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: PAM & LDAP in FreeBSD In-Reply-To: Message from Mike Smith of "Mon, 19 Jul 1999 12:33:53 PDT." <199907191933.MAA00760@dingo.cdrom.com> Date: Mon, 19 Jul 1999 15:47:33 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > On Mon, Jul 19, 1999 at 06:13:51PM +0200, Dag-Erling Smorgrav wrote: > > > Oscar Bonilla writes: > > > > the idea is to have an entry in the /etc/passwd enabling LDAP lookups. > > > > the Entry would be of the form > > > > > > > > ldap:*:389:389:o=My Organization, c=BR:uid:ldap.myorg.com > > > > > > Horrible idea. > > > > > > > suggestions? > > Use PAM. PAM isn't going to cut it. This is outside of its realm. Things like ps, top, ls, chown, chmod, lpr, rcmd, who, w, (the list goes on) need to be able to pull 'passwd' entries from the LDAP server, and unless we PAM all of those (I think that is a very bad idea), then a person will be able to login but will be dead in the water without a UID <->Username mapping. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 12:55:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (Postfix) with ESMTP id D796415239 for ; Mon, 19 Jul 1999 12:55:55 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id MAA13308; Mon, 19 Jul 1999 12:55:19 -0700 (PDT) Message-Id: <199907191955.MAA13308@lestat.nas.nasa.gov> To: Dominic Mitchell Cc: "David E. Cross" , Oscar Bonilla , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD, and userfs too. Reply-To: Jason Thorpe From: Jason Thorpe Date: Mon, 19 Jul 1999 12:55:19 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999 20:44:18 +0100 Dominic Mitchell wrote: > Lovely. Sounds like a much better way to do the Solaris/Linux (and > NetBSD?) /etc/nsswitch.conf stuff. On Solaris at least, this is > implemented using masses of weird shared objects... The plan for NetBSD is that things will also be handled with dynamic modules, but those dynamic modules will be glued into a `nscd'[*] (if you use Solaris, you're familiar with the name :-). [*] We are planning on not having all of the problems that the Solaris nscd has, and that people often complain about. This will allow libc to simply make a call to nscd (or fallback onto traditional `files' lookup), and nscd will handle all but the `files' case. This allows system-wide caching, and puts all of the complexity in one place. Involving one or more user mode file systems seems like ... the wrong approach for a name service switch. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 12:57:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (mailbox.adm.binghamton.edu [128.226.10.60]) by hub.freebsd.org (Postfix) with ESMTP id 759E415264 for ; Mon, 19 Jul 1999 12:57:49 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from cs.binghamton.edu (agate.cs.binghamton.edu [128.226.3.45]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id PAA20368 for ; Mon, 19 Jul 1999 15:57:39 -0400 (EDT) Message-ID: <379385BE.31A9F78@cs.binghamton.edu> Date: Mon, 19 Jul 1999 16:08:30 -0400 From: Zhihui Zhang X-Mailer: Mozilla 4.06 [en] (X11; I; SunOS 5.6 sun4m) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Anything special with kmem_map and mb_map? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been wondering this for some time. There are many kernel submaps: exec_map, clean_map, etc. But if you look the code in vm_map_find(), we have to call splvm() for kmem_map and its submap mb_map, but not for other kernel submaps. So is there anything special with these two kernel submaps? Thanks for any help. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 12:58: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (Postfix) with ESMTP id 6962C15268 for ; Mon, 19 Jul 1999 12:57:59 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id MAA13340; Mon, 19 Jul 1999 12:57:31 -0700 (PDT) Message-Id: <199907191957.MAA13340@lestat.nas.nasa.gov> To: "David E. Cross" Cc: Mike Smith , Oscar Bonilla , Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD Reply-To: Jason Thorpe From: Jason Thorpe Date: Mon, 19 Jul 1999 12:57:30 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999 15:47:33 -0400 "David E. Cross" wrote: > PAM isn't going to cut it. This is outside of its realm. Things like ps, > top, ls, chown, chmod, lpr, rcmd, who, w, (the list goes on) need to be able > to pull 'passwd' entries from the LDAP server, and unless we PAM all of those > (I think that is a very bad idea), then a person will be able to login but > will be dead in the water without a UID <->Username mapping. What you want is nsswitch, a'la Solaris. nsswitch tells you what the user's name is, PAM tells you how that user is to authenticate himself. The two things are orthogonal, and nsswitch and PAM together can work quite well. Solaris, for example, has both. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 13: 3:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 05C0A15239 for ; Mon, 19 Jul 1999 13:03:05 -0700 (PDT) (envelope-from kbyanc@alcnet.com) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from kbyanc (ws-41.alcnet.com [63.69.28.41]) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with SMTP id QAA33355; Mon, 19 Jul 1999 16:18:10 -0400 (EDT) From: "Kelly Yancey" To: "Dan Nelson" Cc: Subject: RE: Overcommit and calloc() Date: Mon, 19 Jul 1999 16:14:29 -0400 Message-ID: <002501bed223$4ea86660$291c453f@kbyanc.alcnet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal In-Reply-To: <19990719115450.A45503@dan.emsphone.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Dan Nelson [mailto:dnelson@emsphone.com] > Sent: Monday, July 19, 1999 12:55 PM > To: Dag-Erling Smorgrav > Cc: Kelly Yancey; freebsd-hackers@FreeBSD.ORG > Subject: Re: Overcommit and calloc() > > > In the last episode (Jul 19), Dag-Erling Smorgrav said: > > "Kelly Yancey" writes: > > > Ahh...but wouldn't the bzero() touch all of the memory just > > > allocated functionally making it non-overcommit? > > > > No. If it were an "non-overcomitting malloc", it would return NULL > > and set errno to ENOMEM, instead of dumping core. > > It should be possible to modify calloc to trap signals, then bzero. If > bzero faults, you free the memory and return NULL. > > No, wait. You can't trap SIGKILL. How about this. mmap() some > anonymous memory MAP_SHARED, fork a child to bzero it. If the child > dies, unmmap and return NULL. If the child succeeds, use the memory. > This memory won't be freeable with malloc(), though. > Hrm. I'm not actually trying to get my system to not overcommit memory. I like overcommit. Besides, every process would have to trap SIGKILL (if you even could) to simulate a non-overcommit system because any process could be killed, not just the one requesting the memory, right? Really, I was just on an educational quest. I was curious to exactly how calloc() was implemented and what affect that had on our overcommit policy. DES was nice enough to show me that calloc() is just a malloc()+bzero() so effectively, the memory gets 'committed' because all of the pages are touched immediately after the malloc(). Whether or not a process get's shot is another matter entirely. :) I have another post on this list which begs the question: if memory given to us fro sbrk() is already zeroed, why zero it again if we don't have too.... if we make calloc() smarter, we could save come clock cycles. The real question is, how many? A quick scan (not exact) of the number of times calloc() is called yields: $ cd /usr/src $ t=0; grep -c -h -R "calloc" * | while read n; do let t+=$n; echo $t; done | tail -1 828 $ t=0; grep -c -h -R "malloc" * | while read n; do let t+=$n; echo $t; done | tail -1 11380 (of course, they each are a little high due to comments and the actual function definitions themselves; cavaet emptor) So calloc() is only used about 1/14th as often as malloc(), and considering many of those calloc() calls would still be serviced the same was a malloc() (reusing memory already on the heap and bzero()'ing it), I'm not 100% sure if the added complexity if worth the performance improvement. If it is, I'de be glad to "whip" some patches up for it (it really shouldn't be too hard). Kelly ~kbyanc@posi.net~ FreeBSD - The Power To Serve - http://www.freebsd.org/ Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 13:15:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from houston.matchlogic.com (houston.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id CE5E914D0D for ; Mon, 19 Jul 1999 13:15:12 -0700 (PDT) (envelope-from crandall@matchlogic.com) Received: by houston.matchlogic.com with Internet Mail Service (5.5.2448.0) id <3631HNPN>; Mon, 19 Jul 1999 14:14:01 -0600 Message-ID: <64003B21ECCAD11185C500805F31EC0302D75907@houston.matchlogic.com> From: Charles Randall To: freebsd-hackers@FreeBSD.ORG Subject: RE: Overcommit and calloc() Date: Mon, 19 Jul 1999 14:14:00 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Kelly Yancey [mailto:kbyanc@alcnet.com] >I have another post on this list which begs the question: if memory given >to us fro sbrk() is already zeroed, why zero it again if we don't have >too.... if we make calloc() smarter, we could save come clock cycles. Because the memory returned from malloc() might be from a previous malloc()/free() and may be dirty. Charles To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 13:19:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id A1F1814E96 for ; Mon, 19 Jul 1999 13:19:07 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA13279; Mon, 19 Jul 1999 16:18:11 -0400 (EDT) Message-Id: <199907192018.QAA13279@cs.rpi.edu> To: Jason Thorpe Cc: Dominic Mitchell , "David E. Cross" , Oscar Bonilla , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: PAM & LDAP in FreeBSD, and userfs too. In-Reply-To: Message from Jason Thorpe of "Mon, 19 Jul 1999 12:55:19 PDT." <199907191955.MAA13308@lestat.nas.nasa.gov> Date: Mon, 19 Jul 1999 16:18:06 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Lovely. Sounds like a much better way to do the Solaris/Linux (and > > NetBSD?) /etc/nsswitch.conf stuff. On Solaris at least, this is > > implemented using masses of weird shared objects... > >The plan for NetBSD is that things will also be handled with dynamic >modules, but those dynamic modules will be glued into a `nscd'[*] (if you >use Solaris, you're familiar with the name :-). > >[*] We are planning on not having all of the problems that the Solaris >nscd has, and that people often complain about. > >This will allow libc to simply make a call to nscd (or fallback onto >traditional `files' lookup), and nscd will handle all but the `files' >case. This allows system-wide caching, and puts all of the complexity >in one place. > >Involving one or more user mode file systems seems like ... the wrong >approach for a name service switch. Tomato, Tomatoe. The difference between the 2 methods is in their interaction with the database itself. You will be providing a socket-ish interface to the cache, my plan is for a filesystem interface, heck it could probably do both. I personally prefer the FS approach in dealing with both on Solaris and Irix. What Irix does well, Irix does very well. The FS method also allows more complex permission checking on access to various databases, like shadow, because the node in a directory had the added granularity of being group readable. It also gives you the flexibility of the shell, or a web-browser, to get at the data. Another idea I had considered was placing something ala 'rc.conf' into a database to allow easy distribution throughout many computers (this would obviously be configuration later in the boot process). Having a FS style interface makes it much easier for programs to get at the data in a clear, consistent manor. These are just my ramblinngs, and it seems we are quickly converging on the same basic idea with slightly different (but perhaps compatible) implementations. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 13:34:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 4B40514CC0 for ; Mon, 19 Jul 1999 13:32:36 -0700 (PDT) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id WAA26372 for ; Mon, 19 Jul 1999 22:30:50 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <014801bed225$a6527fc0$0e00a8c0@neland.dk> From: "Leif Neland" To: Subject: speed of file(1) Date: Mon, 19 Jul 1999 22:30:55 +0200 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 While trying to port amavis, the virusscanner for mail, http://aachalon.de/AMaViS/amavis-0.2.0-pre4.tar.gz ) I noticed it used the file(1) several times for each file, and it took rather long time, causing bb to report red for high CPU-load each time I collected a batch of mail. So I compared it with a Linux box: My 60MHz Pentium, FreeBSD time file /usr/home/leif/vnc-3.3.2r /usr/home/leif/vnc-3.3.2r3_unixsrc.tgz: gzip compressed data, deflated, original filename, last modified: Thu Jan 21 19:23:21 1999 real 0m1.237s user 0m0.758s sys 0m0.394s 133MHz Pentium II, Linux time file vnc-3.3.2r3_unixsrc.tgz vnc-3.3.2r3_unixsrc.tgz: gzip compressed data, deflated, original filename, last modified: Thu Jan 21 19:23:21 1999, os: Unix real 0m0.036s user 0m0.010s sys 0m0.030s While I realise 60MHz is less than 133MHz, a factor 34 in difference of real time seems suspect. The magic file is different, but almost the same size. Why is FreeBSD's file so much slower? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 13:40:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id F00BD14E63 for ; Mon, 19 Jul 1999 13:40:28 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA99539; Mon, 19 Jul 1999 13:39:54 -0700 (PDT) (envelope-from dillon) Date: Mon, 19 Jul 1999 13:39:54 -0700 (PDT) From: Matthew Dillon Message-Id: <199907192039.NAA99539@apollo.backplane.com> To: Charles Randall Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: RE: Overcommit and calloc() References: <64003B21ECCAD11185C500805F31EC0302D75907@houston.matchlogic.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :From: Kelly Yancey [mailto:kbyanc@alcnet.com] :>I have another post on this list which begs the question: if memory given :>to us fro sbrk() is already zeroed, why zero it again if we don't have :>too.... if we make calloc() smarter, we could save come clock cycles. : :Because the memory returned from malloc() might be from a previous :malloc()/free() and may be dirty. : :Charles malloc() uses madvise( ... MADV_FREE) heavily in order to reduce the number of page faults that need to be taken through the course of a program's operation. MADV_FREE is an advisory free that causes FreeBSD to mark the underlying page(s) clean and to free any associated swap backing store. The kernel avoids actually freeing the page until it needs the memory, and the process can re-dirty the page to keep it. No new page-faults occur if the kernel has not reclaimed the page at the time the process reuses it. If the kernel reclaims the page first, the kernel replaces it with zero-fill. If the process reclaims the page first, the page's previous contents (considered to be 'garbage') are retained. Thus, calloc() cannot under normal circumstances assume that the data buffer returned by malloc() is already clear. Since calloc() is not usually used to allocate large chunks of memory, this isn't a problem. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 13:43:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 92C5C15247; Mon, 19 Jul 1999 13:43:20 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id NAA31717; Mon, 19 Jul 1999 13:41:28 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Mon, 19 Jul 1999 13:41:28 -0700 (PDT) From: Vincent Poy To: Reinier Bezuidenhout Cc: jmb@hub.FreeBSD.ORG, sthaug@nethelp.no, tim@storm.digital-rain.com, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? In-Reply-To: <199907191246.OAA29203@oskar.nanoteq.co.za> 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, 19 Jul 1999, Reinier Bezuidenhout wrote: > Hi .. > > > > 1. If you want to test the network speed ... use ttcp or something > > > that generates the data and doesn't read it from disk. > > > > ttcp works. The only problem is when I tried it in both > > directions, at once. the total becomes 11.xMbytes/sec total as opposed to > > 9.4Mbytes/sec when doing it in one direction only. > > If the devices are set at full-duplex then you are looking at something > else ... the standard size for ttcp packets is 8k ... maybe the switch > etc. that you are connected to doesn't handle fragmented packets very well. Hmmm, the thing is we replaced the cables with pre-made ones that go directly from the machines to the Cisco Catalyst 2924XL switch. Ofcourse, the switch is on 10/100 Auto-negotiation. > But ... what it rather seems like .. is that the devices are not in > full-duplex mode .... generating a lot of collisions. After a test > with transfers in both directions .. check the number of collisions > with "netstat -in". If the number of collisions is not high .. - wait > a moment ... are you using ttcp with tcp or udp option ... if you are > using tcp (the default) then when transfering data you have acks going > in both directions which could cause collisions on a full-duplex line ... > try the same with the -u option for UDP. Check our setup below ... > I'll explain some things there. I was using ttcp in two separate instances, one for send and one for receive between the same two machines. I did ttcp -r -s and the other end was ttcp -s -r. > Also check with "netstat -sn" to see if there are any other counters that > increase with the full-duplex transfers. Will do that. > > > 2. When doing full-duplex and using fxp cards, stay away from X-over > > > cables ... use a full-duplex switch etc. ... the fxp cards are not > > > made to work with X-over cables (as far as I know - ala Intel spec) > > > note ... only for full-duplex tests. > > > > Does anyone actually use X-over cables for 100Mbps Full Duplex > > since 3Com said CrossOver cables are not rated for 100Mbps or something > > even though it's Cat5. Actually, in the older Intel docs for the Pro100B, > > it does say to connect using X-over cable to the switch. > > Yes ... to a switch maybe ... but not fxp to fxp ... when transfering > small packets .. you get a lot of "device timeouts". I thought from a fxp to a fxp, you will need a x-over since a straight-wire won't work. > > > We have done tests in full-duplex with non Intel cards (because we did > > > not have a switch at that time :)) and with max size packets we got around > > > 188.00 Mbps using the de0 driver. > > > > Pretty interesting. How did you do the full duplex tests? > > I'll describe the setup briefly ... :) > > We had 3 machines .... two PII-400 as the generators and a PII-400 as the > machine in the middle ... > > So we have a setup that looks like this ... > > > --------- ---------- --------- > | Gen 1 |-----------------| Router |-------------| Gen 2 | > --------- ---------- --------- > > Now .. here is a trick ... add entries manually in the Router's tables > to simulate machines on each side that "does not exist". The reason > for this is that we don't want the machines on the side to be generating > AND excepting packets ... we just want them to generate packets at max > network rate and nothing else. > > We then start a ttcp on both sides to the "non existing" machines. This > means the router will be forwaring packets it receives without any > machines having to be there because of the entries in the routing table. > (we did this because we did not have another two fast machines at that > time, but we did check the packets to make sure everything goes through > and are not dropped etc. - it was some time ago :) ) > > We start ttcp with the following command > > ttcp -t -s -u -p 7000 -n -l 1472 10.0.0.1 > > the size of 1472 generates nice 1514 size UDP packets :) > > We then let the test run ... and check the throughput ... > > We used CAT5 X-over cables ... > > Hopw this helps Ah, I guess you didn't test it on a actual network that's connected to the world and also it was a direct connection between the machines rather than through a switch that can be congested. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 13:47:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 550C5152C7 for ; Mon, 19 Jul 1999 13:47:43 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA99619; Mon, 19 Jul 1999 13:45:08 -0700 (PDT) (envelope-from dillon) Date: Mon, 19 Jul 1999 13:45:08 -0700 (PDT) From: Matthew Dillon Message-Id: <199907192045.NAA99619@apollo.backplane.com> To: "Leif Neland" Cc: Subject: Re: speed of file(1) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Check the size of the magic files on your FreeBSD and Linux boxen. file was never really designed to be efficient. FreeBSD's magic file is /usr/share/misc/magic - around 164K. -Matt : :While trying to port amavis, the virusscanner for mail, : http://aachalon.de/AMaViS/amavis-0.2.0-pre4.tar.gz ) I noticed it used the :file(1) several times for each file, and it took rather long time, causing :bb to report red for high CPU-load each time I collected a batch of mail. : :So I compared it with a Linux box: : :My 60MHz Pentium, FreeBSD : :time file /usr/home/leif/vnc-3.3.2r :/usr/home/leif/vnc-3.3.2r3_unixsrc.tgz: gzip compressed data, deflated, :original filename, last modified: Thu Jan 21 19:23:21 1999 : :real 0m1.237s :user 0m0.758s :sys 0m0.394s : :133MHz Pentium II, Linux : :time file vnc-3.3.2r3_unixsrc.tgz :vnc-3.3.2r3_unixsrc.tgz: gzip compressed data, deflated, original filename, :last modified: Thu Jan 21 19:23:21 1999, os: Unix : :real 0m0.036s :user 0m0.010s :sys 0m0.030s : :While I realise 60MHz is less than 133MHz, a factor 34 in difference of real :time seems suspect. : :The magic file is different, but almost the same size. : :Why is FreeBSD's file so much slower? : :Leif : : : : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message : Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 13:48:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 4D9CD152EB for ; Mon, 19 Jul 1999 13:48:18 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA99660; Mon, 19 Jul 1999 13:48:16 -0700 (PDT) (envelope-from dillon) Date: Mon, 19 Jul 1999 13:48:16 -0700 (PDT) From: Matthew Dillon Message-Id: <199907192048.NAA99660@apollo.backplane.com> To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Anything special with kmem_map and mb_map? References: <379385BE.31A9F78@cs.binghamton.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I have been wondering this for some time. There are many kernel :submaps: exec_map, clean_map, :etc. But if you look the code in vm_map_find(), we have to call splvm() :for kmem_map and its :submap mb_map, but not for other kernel submaps. So is there anything :special with these two :kernel submaps? : :Thanks for any help. : :-Zhihui The kmem_map and mb_map's can be modified from interrupts. The other maps cannot. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 13:58:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 2C0A814D69 for ; Mon, 19 Jul 1999 13:58:48 -0700 (PDT) (envelope-from rminnich@acl.lanl.gov) Received: from tbp.acl.lanl.gov (root@tbp.acl.lanl.gov [128.165.147.10]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id OAA17688 for ; Mon, 19 Jul 1999 14:57:35 -0600 (MDT) Received: from localhost (rminnich@localhost) by tbp.acl.lanl.gov (8.8.7/8.8.8) with ESMTP id OAA28048 for ; Mon, 19 Jul 1999 14:57:11 -0600 X-Authentication-Warning: tbp.acl.lanl.gov: rminnich owned process doing -bs Date: Mon, 19 Jul 1999 14:57:11 -0600 (MDT) From: "Ronald G. Minnich" To: hackers@freebsd.org Subject: Simple parallel debugger 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 If you have needed to monitor and control lots of processes on e.g. a cluster I have rereleased a tool for this purpose. It is called simple parallel debugger, or SPD. Please if interested go to www.acl.lanl.gov/~rminnich and follow the link under that title. I know this is a bit old but I have yet to see a counterpart elsewhere that is freely available. Comments, questions, suggestions are most welcome. Thanks ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 14:17:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id F0F1014D69 for ; Mon, 19 Jul 1999 14:17:27 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40325>; Tue, 20 Jul 1999 06:57:59 +1000 Date: Tue, 20 Jul 1999 07:16:10 +1000 From: Peter Jeremy Subject: Re: Determining the return address In-reply-to: To: hackers@FreeBSD.ORG Cc: des@flood.ping.uio.no Message-Id: <99Jul20.065759est.40325@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: >Alfred Perlstein writes: >> specifically how you say you increment it, then decrement it, >> if you have multiple handlers where one can interupt another >> you can have the counter get jumbled. > >Not if increment / decrement is atomic. Which it _isn't_ in general. The only case where it _is_ atomic is on a UP i386, where the compiler has generated an `inc' instruction (which it might not). Check out /sys/alpha/include/atomic.h or a recent (less than a week old [1]) -current version of /sys/i386/include/atomic.h for atomic code. Peter [1] It was broken prior to this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 14:18:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id CB53514EE7 for ; Mon, 19 Jul 1999 14:18:49 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id OAA01326; Mon, 19 Jul 1999 14:11:18 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907192111.OAA01326@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "David E. Cross" Cc: Mike Smith , Oscar Bonilla , Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD In-reply-to: Your message of "Mon, 19 Jul 1999 15:47:33 EDT." <199907191947.PAA12399@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Jul 1999 14:11:18 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > ldap:*:389:389:o=My Organization, c=BR:uid:ldap.myorg.com > > > > > > > > Horrible idea. > > > > > > > > > > suggestions? > > > > Use PAM. > > PAM isn't going to cut it. This is outside of its realm. Things like ps, > top, ls, chown, chmod, lpr, rcmd, who, w, (the list goes on) need to be able > to pull 'passwd' entries from the LDAP server, and unless we PAM all of those > (I think that is a very bad idea), then a person will be able to login but > will be dead in the water without a UID <->Username mapping. The Linux-PAM folks solved this with their 'libpwdb', which basically provides a transport-neutral interface to the whole uid:userdata mapping. Unfortunately, their implementation _reeks_, so nobody has touched it yet. This is, however, how I think we should be going. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 14:32: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 0C02C15284 for ; Mon, 19 Jul 1999 14:31:50 -0700 (PDT) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id XAA39858; Mon, 19 Jul 1999 23:31:38 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <02a901bed22e$25164e60$0e00a8c0@neland.dk> From: "Leif Neland" To: "Matthew Dillon" Cc: References: <199907192045.NAA99619@apollo.backplane.com> Subject: Sv: speed of file(1) Date: Mon, 19 Jul 1999 23:31:42 +0200 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 From: Matthew Dillon > Check the size of the magic files on your FreeBSD and Linux boxen. > file was never really designed to be efficient. FreeBSD's magic > file is /usr/share/misc/magic - around 164K. > > -Matt > > : > > : > :The magic file is different, but almost the same size. > : Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 15: 0:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id E35FF14D1C for ; Mon, 19 Jul 1999 15:00:08 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id OAA11907; Mon, 19 Jul 1999 14:58:43 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id OAA01788; Mon, 19 Jul 1999 14:58:29 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA29912; Mon, 19 Jul 99 14:58:40 PDT Message-Id: <37939F8E.7B9E0E16@softweyr.com> Date: Mon, 19 Jul 1999 15:58:38 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Keith Stevenson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD References: <19990715200336.A15050@fisicc-ufm.edu> <19990716123648.C3049@fisicc-ufm.edu> <19990719101713.A3438@fisicc-ufm.edu> <19990719132941.A28478@homer.louisville.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Keith Stevenson wrote: > > On Mon, Jul 19, 1999 at 06:22:17PM +0200, Dag-Erling Smorgrav wrote: > > Oscar Bonilla writes: > > > On Mon, Jul 19, 1999 at 06:13:51PM +0200, Dag-Erling Smorgrav wrote: > > > > Oscar Bonilla writes: > > > > > the idea is to have an entry in the /etc/passwd enabling LDAP lookups. > > > > > the Entry would be of the form > > > > > > > > > > ldap:*:389:389:o=My Organization, c=BR:uid:ldap.myorg.com > > > > Horrible idea. > > > suggestions? > > > > /etc/auth.conf > > > > Given that this is a PAM module, wouldn't /etc/pam.conf be more appropriate? /etc/pam.conf would be appropriate for configuring the behavior of PAM modules. /etc/auth.conf would be appropriate for configuring WHICH authentication method to use. Let's please don't confuse the two. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 15:18:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 445EE14EED for ; Mon, 19 Jul 1999 15:16:24 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.2) id WAA49982; Mon, 19 Jul 1999 22:26:00 +0100 (BST) (envelope-from nik) Date: Mon, 19 Jul 1999 22:26:00 +0100 From: Nik Clayton To: Oscar Bonilla Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD Message-ID: <19990719222600.A49715@catkin.nothing-going-on.org> References: <19990715200336.A15050@fisicc-ufm.edu> <19990716123648.C3049@fisicc-ufm.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990716123648.C3049@fisicc-ufm.edu>; from Oscar Bonilla on Fri, Jul 16, 1999 at 12:36:48PM -0600 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 16, 1999 at 12:36:48PM -0600, Oscar Bonilla wrote: > For LDAP to be seamlessly integrated into the system some of the libraries > have to be changed. Specifically the ones dealing with /etc/passwd and > user information. <...> I haven't seen him post to this thread yet, but you might want to talk to Amancio Hasty . I know he's been working with LDAP and FreeBSD. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 15:45:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 94D5F14CD5 for ; Mon, 19 Jul 1999 15:45:37 -0700 (PDT) (envelope-from howardjp@wam.umd.edu) Received: from rac9.wam.umd.edu (root@rac9.wam.umd.edu [128.8.10.149]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id SAA00818 for ; Mon, 19 Jul 1999 18:43:16 -0400 (EDT) Received: from rac9.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac9.wam.umd.edu (8.9.3/8.9.3) with SMTP id SAA08512 for ; Mon, 19 Jul 1999 18:43:16 -0400 (EDT) Received: from localhost by rac9.wam.umd.edu (8.9.3/8.9.3) with ESMTP id SAA08508 for ; Mon, 19 Jul 1999 18:43:15 -0400 (EDT) X-Authentication-Warning: rac9.wam.umd.edu: howardjp owned process doing -bs Date: Mon, 19 Jul 1999 18:43:15 -0400 (EDT) From: Jamie Howard To: freebsd-hackers@freebsd.org Subject: m68k Support in FreeBSD 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 A week or so ago there was some discussion of someone who ported FreeBSD to 68k-based Macintosh systems on EFNet. There was also a reference to a website (http://www.freebsd.org/~green/FreeBSD-68k.txt). In about two weeks I'll have a spare Macintosh IIsi and would like to have a run at FreeBSD on it. So, to the point, where can I get it? :) Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 15:53:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id E4A4E14CD5 for ; Mon, 19 Jul 1999 15:53:52 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id PAA12761; Mon, 19 Jul 1999 15:51:21 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id PAA03654; Mon, 19 Jul 1999 15:51:07 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA02593; Mon, 19 Jul 99 15:51:13 PDT Message-Id: <3793ABE0.15090E38@softweyr.com> Date: Mon, 19 Jul 1999 16:51:12 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Mike Smith Cc: "David E. Cross" , Oscar Bonilla , Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD References: <199907192111.OAA01326@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > > > > > ldap:*:389:389:o=My Organization, c=BR:uid:ldap.myorg.com > > > > > > > > > > Horrible idea. > > > > > > > > > > > > > suggestions? > > > > > > Use PAM. > > > > PAM isn't going to cut it. This is outside of its realm. Things like ps, > > top, ls, chown, chmod, lpr, rcmd, who, w, (the list goes on) need to be able > > to pull 'passwd' entries from the LDAP server, and unless we PAM all of those > > (I think that is a very bad idea), then a person will be able to login but > > will be dead in the water without a UID <->Username mapping. > > The Linux-PAM folks solved this with their 'libpwdb', which basically > provides a transport-neutral interface to the whole uid:userdata > mapping. Unfortunately, their implementation _reeks_, so nobody has > touched it yet. > > This is, however, how I think we should be going. 100% agreement here. This needs to be implemented such that the administrator configures the box to use local files, or NIS, or LDAP, or whatever as the source of username information, and both login(1) and ls(1) use the information as appropriate. For ls(1) and friends, this means implementing getpwuid(3) (and getgrgid(3)) so they "just work." The implementation details are as unimportant as ever: they have to work and be maintainable. Following prior art remains a good idea; the Solaris "name service switch" implementation is a good starting point to consider. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 15:58: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp11.bellglobal.com (smtp11.bellglobal.com [204.101.251.53]) by hub.freebsd.org (Postfix) with ESMTP id 4F5041500E for ; Mon, 19 Jul 1999 15:57:57 -0700 (PDT) (envelope-from vanderh@ecf.toronto.edu) Received: from localhost.nowhere (ppp18390.on.bellglobal.com [206.172.130.70]) by smtp11.bellglobal.com (8.8.5/8.8.5) with ESMTP id SAA23750; Mon, 19 Jul 1999 18:58:59 -0400 (EDT) Received: (from tim@localhost) by localhost.nowhere (8.9.3/8.9.1) id SAA87284; Mon, 19 Jul 1999 18:56:59 -0400 (EDT) (envelope-from tim) Date: Mon, 19 Jul 1999 18:56:58 -0400 From: Tim Vanderhoek To: Greg Lehey Cc: FreeBSD Hackers Subject: Re: How much memory do we need to install? Message-ID: <19990719185658.E87043@mad> References: <19990719173407.C72625@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19990719173407.C72625@freebie.lemis.com>; from Greg Lehey on Mon, Jul 19, 1999 at 05:34:07PM +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 19, 1999 at 05:34:07PM +0930, Greg Lehey wrote: > AFAIK, the minimum memory for installation is still 5 MB, and the > problems people had with 8MB machines failing to install was a bug, > right? What's the current status? Some people have reported that they need up to 12MB to install. -- This is my .signature which gets appended to the end of my messages. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 16:34:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 8580D14D32 for ; Mon, 19 Jul 1999 16:34:33 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id QAA13252; Mon, 19 Jul 1999 16:29:57 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id QAA05070; Mon, 19 Jul 1999 16:29:43 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA04453; Mon, 19 Jul 99 16:29:55 PDT Message-Id: <3793B4F3.1E08C41D@softweyr.com> Date: Mon, 19 Jul 1999 17:29:55 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Matthew Dillon Cc: Leif Neland , freebsd-hackers@FreeBSD.ORG Subject: Re: speed of file(1) References: <199907192045.NAA99619@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > Check the size of the magic files on your FreeBSD and Linux boxen. > file was never really designed to be efficient. FreeBSD's magic > file is /usr/share/misc/magic - around 164K. The Linux one 169350 bytes, 4891 lines. The FreeBSD 3.1 magic file is 164223 bytes, 4802 lines. > Leif Neland asked: > > :While trying to port amavis, the virusscanner for mail, > : http://aachalon.de/AMaViS/amavis-0.2.0-pre4.tar.gz ) I noticed it used the > :file(1) several times for each file, and it took rather long time, causing This begs the question "Why?" Can't the program cache the results of file(1) instead of calling it multiple times? Premature optimization is the root of all evil. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 17:53:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from 001101.zer0.org (001101.zer0.org [206.24.105.163]) by hub.freebsd.org (Postfix) with ESMTP id 0E8A414EB5 for ; Mon, 19 Jul 1999 17:53:23 -0700 (PDT) (envelope-from gsutter@001101.zer0.org) Received: (from gsutter@localhost) by 001101.zer0.org (8.9.2/8.9.2) id RAA62757 for hackers@freebsd.org; Mon, 19 Jul 1999 17:52:40 -0700 (PDT) (envelope-from gsutter) Date: Mon, 19 Jul 1999 17:52:39 -0700 From: Gregory Sutter To: hackers@freebsd.org Subject: maxfiles == maxfilesperproc ? Message-ID: <19990719175239.E45481@001101.zer0.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: Zer0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hax0rs, In sys/conf/param.c (in -STABLE), both maxfiles and maxfilesperproc are set equal to MAXFILES. This doesn't make much sense to me. It seems that maxfiles should be set to be greater than maxfilesperproc by default, so that one process can't consume all of the file descriptors. I noticed this while building a system that will be running some very large processes with many open files, so set maxfilesperproc on that box equal to MAXFILES - 512, but this metric is not appropriate for systems with small MAXUSERS (like GENERIC). So... 1. Should maxfiles be, by default, larger than maxfilesperproc? 2. If so, how much is necessary and appropriate? Regards, Greg -- Gregory S. Sutter "How do I read this file?" mailto:gsutter@pobox.com "You uudecode it." http://www.pobox.com/~gsutter/ "I I I decode it?" PGP DSS public key 0x40AE3052 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 17:59: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 6363714DE5 for ; Mon, 19 Jul 1999 17:59:01 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id RAA02591; Mon, 19 Jul 1999 17:53:41 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907200053.RAA02591@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Gregory Sutter Cc: hackers@freebsd.org Subject: Re: maxfiles == maxfilesperproc ? In-reply-to: Your message of "Mon, 19 Jul 1999 17:52:39 PDT." <19990719175239.E45481@001101.zer0.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Jul 1999 17:53:41 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > hax0rs, > > In sys/conf/param.c (in -STABLE), both maxfiles and maxfilesperproc are > set equal to MAXFILES. This doesn't make much sense to me. It seems that > maxfiles should be set to be greater than maxfilesperproc by default, so > that one process can't consume all of the file descriptors. > > I noticed this while building a system that will be running some very > large processes with many open files, so set maxfilesperproc on that box > equal to MAXFILES - 512, but this metric is not appropriate for systems > with small MAXUSERS (like GENERIC). So... > > 1. Should maxfiles be, by default, larger than maxfilesperproc? Not really; these numbers are just ultra-hard limits. You should typically use login classes and the per-process limits to enforce these controls. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 18: 0:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 1F0F315012 for ; Mon, 19 Jul 1999 18:00:17 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA17486; Mon, 19 Jul 1999 18:00:32 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Jamie Howard Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: m68k Support in FreeBSD In-reply-to: Your message of "Mon, 19 Jul 1999 18:43:15 EDT." Date: Mon, 19 Jul 1999 18:00:32 -0700 Message-ID: <17482.932432432@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > website (http://www.freebsd.org/~green/FreeBSD-68k.txt). In about two > weeks I'll have a spare Macintosh IIsi and would like to have a run at > FreeBSD on it. So, to the point, where can I get it? :) I'd say that's a question for Grant Stockly, the person mentioned in green's web-cited message. It's certainly not part of FreeBSD and whether it ever will be is a matter still subject to debate. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 18: 7:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id B5C131516A for ; Mon, 19 Jul 1999 18:07:45 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id VAA50490; Mon, 19 Jul 1999 21:07:02 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Mon, 19 Jul 1999 21:07:01 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: "Jordan K. Hubbard" Cc: Jamie Howard , freebsd-hackers@FreeBSD.org Subject: Re: m68k Support in FreeBSD In-Reply-To: <17482.932432432@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, Jordan K. Hubbard wrote: > > website (http://www.freebsd.org/~green/FreeBSD-68k.txt). In about two > > weeks I'll have a spare Macintosh IIsi and would like to have a run at > > FreeBSD on it. So, to the point, where can I get it? :) > > I'd say that's a question for Grant Stockly, the person mentioned in > green's web-cited message. It's certainly not part of FreeBSD and > whether it ever will be is a matter still subject to debate. Isn't it more a question of whether a proper cross-build system will be available within the time frame that m68ks aren't completely obsolete? > > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ 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 Mon Jul 19 18:11:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 9CD6B1518A; Mon, 19 Jul 1999 18:11:16 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA24197; Mon, 19 Jul 1999 18:10:22 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: "Brian F. Feldman" Cc: Jamie Howard , freebsd-hackers@FreeBSD.org Subject: Re: m68k Support in FreeBSD In-reply-to: Your message of "Mon, 19 Jul 1999 21:07:01 EDT." Date: Mon, 19 Jul 1999 18:10:22 -0700 Message-ID: <24193.932433022@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 19 Jul 1999, Jordan K. Hubbard wrote: > > > > website (http://www.freebsd.org/~green/FreeBSD-68k.txt). In about two > > > weeks I'll have a spare Macintosh IIsi and would like to have a run at > > > FreeBSD on it. So, to the point, where can I get it? :) > > > > I'd say that's a question for Grant Stockly, the person mentioned in > > green's web-cited message. It's certainly not part of FreeBSD and > > whether it ever will be is a matter still subject to debate. > > Isn't it more a question of whether a proper cross-build system will > be available within the time frame that m68ks aren't completely obsolete? No. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 18:18:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-out.visi.com (tele.visi.com [209.98.98.17]) by hub.freebsd.org (Postfix) with ESMTP id 192C91517D; Mon, 19 Jul 1999 18:18:30 -0700 (PDT) (envelope-from mestery@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id E623B1F88D; Mon, 19 Jul 1999 20:18:28 -0500 (CDT) Received: from localhost (mestery@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id UAA04933; Mon, 19 Jul 1999 20:18:28 -0500 (CDT) X-Authentication-Warning: isis.visi.com: mestery owned process doing -bs Date: Mon, 19 Jul 1999 20:18:28 -0500 (CDT) From: To: "Brian F. Feldman" Cc: "Jordan K. Hubbard" , Jamie Howard , freebsd-hackers@FreeBSD.ORG Subject: Re: m68k Support in FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, Brian F. Feldman wrote: > On Mon, 19 Jul 1999, Jordan K. Hubbard wrote: > > > I'd say that's a question for Grant Stockly, the person mentioned in > > green's web-cited message. It's certainly not part of FreeBSD and > > whether it ever will be is a matter still subject to debate. > > Isn't it more a question of whether a proper cross-build system will > be available within the time frame that m68ks aren't completely obsolete? > Hey wait a second! I have a wonderful HP Apollo 400 Series with a 68030 at 50MHz that is so impressive looking friends and family stare in awe at it.:) Seriously, it runs NetBSD, and is a great xterm (19" black and white monitor). I assume mac's and amigas with m68k's are just as useful. -- Kyle Mestery | StorageTek's Storage Networking Group mestery@visi.com | http://www.freebsd.org/ mestery@netwinder.org | http://www.netwinder.org/ Protect your right to privacy: www.freecrypto.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 19:12:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.click2net.com (mail.click2net.com [216.94.59.238]) by hub.freebsd.org (Postfix) with ESMTP id CA65D1524D; Mon, 19 Jul 1999 19:12:34 -0700 (PDT) (envelope-from geoff@click2net.com) Received: from click2net.com (sparrow.click2net.com [216.94.59.226]) by mail.click2net.com (8.9.1/8.9.1) with ESMTP id WAA17756; Mon, 19 Jul 1999 22:11:43 -0400 (EDT) (envelope-from geoff@click2net.com) Message-ID: <3793DAD7.67FBAC6D@click2net.com> Date: Mon, 19 Jul 1999 22:11:35 -0400 From: Geoffrey Robinson Organization: Click2net inc. X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: questions@freebsd.org, hackers@freebsd.org Subject: PAO Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NB: Please reply to me directly, I'm not on the list pertinent data: FreeBSD 3.2R on a SONY VAIO laptop, PAO3-19990605 version I just installed PAO on my SONY VAIO in hopes of getting my 3COM 3CXE589ET PCMCIA eithernet card working. When I boot the laptop with the PAO install floppies it finds the card and it works because I was able to download the PAO distributions from the FTP site through it. However when I reboot the system after the install I get the following errors. - - - Initial rc.pccard configuration: pcic-memory=0xd0000 pccardc: /dev/card0: Device not configured execute pccardd pccard-beep=2 pccardc: /dev/card0: Device not configured . Doinf initial network setup: hostname. ifconfig: interface ep0 does not exist ifconfig: interface ep0 does not exist lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 route: writing to routing socket: Network is unreachable - - - Typical startup stuff follows then syslogd pukes with the error. syslogd: syslog/udp: unknown service syslogd: child pid 107 exited with return code 1 I'm sure I've missed somthing stupid but I can see it. I can get a 3com 3c589 as listed in the release notes as a last resort. Does anybody have one of these working? thanks in advance for any help. -- Geoffrey Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 19:25:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.antisocial.net (ns1.antisocial.net [208.10.211.34]) by hub.freebsd.org (Postfix) with ESMTP id 7FA7D1511B for ; Mon, 19 Jul 1999 19:25:15 -0700 (PDT) (envelope-from modred@ns1.antisocial.net) Received: from localhost (modred@localhost) by ns1.antisocial.net (8.9.3/8.9.3) with ESMTP id VAA21002; Mon, 19 Jul 1999 21:24:44 -0500 (EST) Date: Mon, 19 Jul 1999 21:24:44 -0500 (EST) From: Modred To: Vincent Poy Cc: sthaug@nethelp.no, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? 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 Sat, 17 Jul 1999, Vincent Poy wrote: > > > By reading the man page? > > The manpage doesn't really say anything about how to use ttcp... I don't think manpage useage is -hackers-esque. > There is no ttcp binary anywhere on either my -CURRENT, > 3.2-RELEASE and 3.1-RELEASE systems. Ever hear of ports? Or is 'how to use the ports collection' suddenly -hackers material? That, and .sig files that contain more relevant bits than the sender's posts... Oh, and I'd appreciate it if you could refrain from quoting this entire message to simply say, 'Interesting'... Thanks. Later, --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 19:26:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id 31A3A1511B; Mon, 19 Jul 1999 19:26:38 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id LAA18545; Tue, 20 Jul 1999 11:26:26 +0900 (JST) Date: Tue, 20 Jul 1999 11:26:26 +0900 (JST) Message-Id: <199907200226.LAA18545@afs.ntc.mita.keio.ac.jp> To: geoff@click2net.com Cc: questions@freebsd.org, hackers@freebsd.org, hosokawa@itc.keio.ac.jp Subject: Re: PAO In-Reply-To: Your message of "Tue, 20 Jul 1999 11:11:35 JST". <3793DAD7.67FBAC6D@click2net.com> From: hosokawa@itc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3793DAD7.67FBAC6D@click2net.com> geoff@click2net.com writes: >> pertinent data: FreeBSD 3.2R on a SONY VAIO laptop, PAO3-19990605 >> version >> >> I just installed PAO on my SONY VAIO in hopes of getting my 3COM >> 3CXE589ET PCMCIA eithernet card working. When I boot the laptop with the >> PAO install floppies it finds the card and it works because I was able >> to download the PAO distributions from the FTP site through it. However >> when I reboot the system after the install I get the following errors. Maybe your kernel is still GENERIC kernel. Please try # cd / # chflags noschg kernel # cp kernel.PAO kernel # chflags schg kernel and reboot. If there's not kernel.PAO file, paobin has not successfly installed yet. -- HOSOKAWA, Tatsumi Assistant Manager Information Technology Center, Keio University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 19:36:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.antisocial.net (ns1.antisocial.net [208.10.211.34]) by hub.freebsd.org (Postfix) with ESMTP id 90E7614C90 for ; Mon, 19 Jul 1999 19:36:50 -0700 (PDT) (envelope-from modred@ns1.antisocial.net) Received: from localhost (modred@localhost) by ns1.antisocial.net (8.9.3/8.9.3) with ESMTP id VAA21043; Mon, 19 Jul 1999 21:32:32 -0500 (EST) Date: Mon, 19 Jul 1999 21:32:32 -0500 (EST) From: Modred To: Vincent Poy Cc: Leif Neland , freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? 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, 18 Jul 1999, Vincent Poy wrote: > I'm not sure if it shows the mac address of the cisco's port or > the actual device connected to it... You see the MAC of the switch's port. It's been too long since I've played on a Catalyst... but what does 'sh arp' display? Any arp -> port -> host correlations? Good luck... :) > That's a option too... Only problem is that can take forever. :-) Yeah, I've noticed the 'sync-up time' takes quite awhile on a Catalyst running 100Mbps. Later, --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 19:37:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rebel.net.au (rebel.rebel.net.au [203.20.69.66]) by hub.freebsd.org (Postfix) with ESMTP id E9C03150F0 for ; Mon, 19 Jul 1999 19:37:32 -0700 (PDT) (envelope-from kkenn@rebel.net.au) Received: from 203.20.69.74 (dialup-4.rebel.net.au [203.20.69.74]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id MAA17798 for ; Tue, 20 Jul 1999 12:05:20 +0930 Received: (qmail 9298 invoked from network); 20 Jul 1999 02:35:15 -0000 Received: from localhost (kkenn@127.0.0.1) by localhost with SMTP; 20 Jul 1999 02:35:15 -0000 Date: Tue, 20 Jul 1999 12:05:14 +0930 (CST) From: Kris Kennaway Reply-To: kkenn@rebel.net.au To: Wes Peters Cc: Keith Stevenson , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD In-Reply-To: <37939F8E.7B9E0E16@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, Wes Peters wrote: > > Given that this is a PAM module, wouldn't /etc/pam.conf be more appropriate? > > /etc/pam.conf would be appropriate for configuring the behavior of PAM > modules. /etc/auth.conf would be appropriate for configuring WHICH > authentication method to use. Let's please don't confuse the two. In my work on modularizing crypt() (which is almost ready for another alpha release) I'm using login classes in /etc/login.conf instead of system-global settings in /etc/auth.conf to decide password hash schemes. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 20:42:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 063CC14E14 for ; Mon, 19 Jul 1999 20:42:46 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA01242; Mon, 19 Jul 1999 20:42:42 -0700 (PDT) (envelope-from dillon) Date: Mon, 19 Jul 1999 20:42:42 -0700 (PDT) From: Matthew Dillon Message-Id: <199907200342.UAA01242@apollo.backplane.com> To: Wes Peters Cc: Leif Neland , freebsd-hackers@FreeBSD.ORG Subject: Re: speed of file(1) References: <199907192045.NAA99619@apollo.backplane.com> <3793B4F3.1E08C41D@softweyr.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :The Linux one 169350 bytes, 4891 lines. The FreeBSD 3.1 magic file is :164223 bytes, 4802 lines. : :> Leif Neland asked: :> :> :While trying to port amavis, the virusscanner for mail, :> : http://aachalon.de/AMaViS/amavis-0.2.0-pre4.tar.gz ) I noticed it used the :> :file(1) several times for each file, and it took rather long time, causing : :This begs the question "Why?" Can't the program cache the results of file(1) :instead of calling it multiple times? : :Premature optimization is the root of all evil. : : :-- : "Where am I, and what am I doing in this handbasket?" : :Wes Peters Softweyr LLC :http://softweyr.com/ wes@softweyr.com Someone would have to compare file sources or profile it to figure out what is causing the slowness. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 20:57: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from voyager.fisicc-ufm.edu (ip-61-037.guate.net [200.12.61.37]) by hub.freebsd.org (Postfix) with ESMTP id A652415086 for ; Mon, 19 Jul 1999 20:56:46 -0700 (PDT) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id SAA00866; Mon, 19 Jul 1999 18:00:27 -0600 (CST) (envelope-from obonilla) Date: Mon, 19 Jul 1999 18:00:26 -0600 From: Oscar Bonilla To: Wes Peters Cc: Mike Smith , "David E. Cross" , Oscar Bonilla , Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD Message-ID: <19990719180026.A830@fisicc-ufm.edu> References: <199907192111.OAA01326@dingo.cdrom.com> <3793ABE0.15090E38@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <3793ABE0.15090E38@softweyr.com>; from Wes Peters on Mon, Jul 19, 1999 at 04:51:12PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 19, 1999 at 04:51:12PM -0600, Wes Peters wrote: > The implementation details are as unimportant as ever: they have to work > and be maintainable. Following prior art remains a good idea; the Solaris > "name service switch" implementation is a good starting point to consider. > I agree. In solaris (and linux by the way) all you do is set passwd ldap files in /etc/nsswitch.conf and that's it. I had started to write the code to mess with libc to "fix" the getpwent stuff, but a better solution is to "port" the nsswitch stuff from linux (i don't have source from solaris :) Anyone more knowledgeable should give me a big hand here and point me to the right way to start this. I'm willing to do the coding but need help on the overall design. Since I need this working asap, I'm gonna hack libc so that if the file /etc/auth.conf has a line saying auth_list = ldap, it looks in /etc/ldap.conf to get the rest of the stuff (server, port, base dn, etc). At the same time, we should work towards a real solution. regards, -Oscar -- For PGP Public Key: finger obonilla@fisicc-ufm.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 21: 7:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mom.hooked.net (mom.hooked.net [206.80.6.10]) by hub.freebsd.org (Postfix) with ESMTP id D65EF14DC0; Mon, 19 Jul 1999 21:07:47 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from fish.hooked.net (garbanzo@fish.hooked.net [206.80.6.48]) by mom.hooked.net (8.8.6/8.8.5) with SMTP id TAA14379; Mon, 19 Jul 1999 19:35:20 -0700 (PDT) Date: Mon, 19 Jul 1999 19:35:19 -0700 (PDT) From: Alex Zepeda To: "Brian F. Feldman" Cc: "Jordan K. Hubbard" , Jamie Howard , freebsd-hackers@FreeBSD.ORG Subject: Re: m68k Support in FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, Brian F. Feldman wrote: > Isn't it more a question of whether a proper cross-build system will > be available within the time frame that m68ks aren't completely obsolete? Bah! An 040 or 030 powered Mac w/ MacOS makes a decent web browsing, word processing machine; it's an actually useable alternative to an e-machine. Similarlly a 386 or 486 powered FreeBSD machine can still be quite useful even as a small server (admittedly the 68k Mac hardware makes for a piss poor server.. but still). I can't see a 486 or 040 powered machine becomming entirely obsolete until X is required to buildworld. - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 21:18: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 3C9BD15086 for ; Mon, 19 Jul 1999 21:17:53 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id XAA16259; Mon, 19 Jul 1999 23:16:29 -0500 (CDT) Date: Mon, 19 Jul 1999 23:16:29 -0500 From: "Matthew D. Fuller" To: Stephen McKay Cc: Matthew Dillon , freebsd-hackers@FreeBSD.ORG, Leif Neland Subject: Re: softupdates on root partition, no floppy Message-ID: <19990719231629.G12369@futuresouth.com> References: <199907172306.QAA81618@apollo.backplane.com> <199907190725.RAA13642@nymph.detir.qld.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199907190725.RAA13642@nymph.detir.qld.gov.au>; from Stephen McKay on Mon, Jul 19, 1999 at 05:25:06PM +1000 X-OS: FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 19, 1999 at 05:25:06PM +1000, a little birdie told me that Stephen McKay remarked > > I gave up using soft updates on root because of the delayed delete > behaviour. I kept filling up root while updating kernels. It doesn't > gain you much on little used file systems anyway. So, I recommend > people leave root alone. No, don't leave it alone, make it even SLOWER than usual! /dev/da0s1a on / (local, synchronous, writes: sync 114 async 3850) Question of the day: Why do I have async writes on a sync partition? -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ FutureSouth Communications | ISPHelp ISP Consulting "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 21:25:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id 70FFA15133 for ; Mon, 19 Jul 1999 21:25:21 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 55601 invoked from network); 20 Jul 1999 04:25:17 -0000 Received: from shell-1.enteract.com (dscheidt@207.229.143.40) by pop3-3.enteract.com with SMTP; 20 Jul 1999 04:25:17 -0000 Date: Mon, 19 Jul 1999 23:25:16 -0500 (CDT) From: David Scheidt To: "Matthew D. Fuller" Cc: Stephen McKay , Matthew Dillon , freebsd-hackers@FreeBSD.ORG, Leif Neland Subject: Re: softupdates on root partition, no floppy In-Reply-To: <19990719231629.G12369@futuresouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, Matthew D. Fuller wrote: > No, don't leave it alone, make it even SLOWER than usual! > /dev/da0s1a on / (local, synchronous, writes: sync 114 async 3850) > > Question of the day: Why do I have async writes on a sync partition? Because only meta-data writes are done synchronously. Data is still done asynchronously. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 21:30: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 4670E15086 for ; Mon, 19 Jul 1999 21:29:59 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id XAA16766; Mon, 19 Jul 1999 23:27:44 -0500 (CDT) Date: Mon, 19 Jul 1999 23:27:44 -0500 From: "Matthew D. Fuller" To: David Scheidt Cc: Stephen McKay , Matthew Dillon , freebsd-hackers@FreeBSD.ORG, Leif Neland Subject: Re: softupdates on root partition, no floppy Message-ID: <19990719232744.J12369@futuresouth.com> References: <19990719231629.G12369@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from David Scheidt on Mon, Jul 19, 1999 at 11:25:16PM -0500 X-OS: FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 19, 1999 at 11:25:16PM -0500, a little birdie told me that David Scheidt remarked > On Mon, 19 Jul 1999, Matthew D. Fuller wrote: > > > > Question of the day: Why do I have async writes on a sync partition? > > Because only meta-data writes are done synchronously. Data is still done > asynchronously. Even with SYNC mounts? (Not 'default', explicit 'sync'. It takes quite noticeable amounts of time to, for instance, install kernels.) From fstab: # Device Mountpoint FStype Options Dump Pass# /dev/da0s1a / ufs rw,sync 1 1 -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ FutureSouth Communications | ISPHelp ISP Consulting "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 21:53:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wrath.cs.utah.edu (wrath.cs.utah.edu [155.99.198.100]) by hub.freebsd.org (Postfix) with ESMTP id 77D4D15144 for ; Mon, 19 Jul 1999 21:53:32 -0700 (PDT) (envelope-from danderse@cs.utah.edu) Received: from lal.cs.utah.edu (lal.cs.utah.edu [155.99.195.65]) by wrath.cs.utah.edu (8.8.8/8.8.8) with ESMTP id WAA17142; Mon, 19 Jul 1999 22:52:44 -0600 (MDT) From: David G Andersen Received: (from danderse@localhost) by lal.cs.utah.edu (8.8.8/8.8.8) id WAA15557; Mon, 19 Jul 1999 22:52:42 -0600 (MDT) Message-Id: <199907200452.WAA15557@lal.cs.utah.edu> Subject: Re: tee option on ipfw? To: mrcpu@internetcds.com (Jaye Mathisen) Date: Mon, 19 Jul 1999 22:52:42 -0600 (MDT) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Jaye Mathisen" at Jul 18, 99 03:42:19 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The 'tee' behavior can be pretty easily emulated, however. a) use bpfilter - it automatically does a copy type thing. b) Use a little divert socket program which simply does: len = recvfrom(divert_socket, packetbuf, sizeof(packetbuf), 0, (struct sockaddr *)&from, &fromlen); sendto(divert_socket, packetbuf, len, 0, (struct sockaddr *)&from, fromlen); do_whatever_stuff_you_want(); Option a will, of course, be faster, since it doesn't involve a copy to userspace before allowing the packet to continue its normal path. The tee option would do the same thing, if and when. -Dave Lo and behold, Jaye Mathisen once said: > > > > The man page says the tee option on ipfw is not yet supported. > > I'm wondering if that is still the case as of 3.2-stable, or if the doc is > just out of date. > > I would like to make a copy of incoming UDP packets to a specific port for > some testing. tee seems like an easy way to go. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- work: danderse@cs.utah.edu me: angio@pobox.com University of Utah CS Department http://www.angio.net/ "If you haul a geek up a crack, you will bloody their fingers for a day... If you teach a geek to climb, you will bloody their fingers for life." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 22:39:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by hub.freebsd.org (Postfix) with ESMTP id 381F41517E for ; Mon, 19 Jul 1999 22:39:32 -0700 (PDT) (envelope-from jwm@CSUA.Berkeley.EDU) Received: from soda.CSUA.Berkeley.EDU (localhost [127.0.0.1]) by soda.CSUA.Berkeley.EDU (8.8.8/) via ESMTP id WAA25700; Mon, 19 Jul 1999 22:36:21 -0700 (PDT) env-from (jwm@CSUA.Berkeley.EDU) Message-Id: <199907200536.WAA25700@soda.CSUA.Berkeley.EDU> To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: USFS (User Space File System) In-reply-to: Message from "David E. Cross" of "Sat, 17 Jul 1999 14:57:45 EDT." <199907171857.OAA81681@cs.rpi.edu> Date: Mon, 19 Jul 1999 22:36:21 -0700 From: John Milford Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David, Unless I am misunderstanding you, mfs does what you are describing. --John "David E. Cross" wrote: > I am looking at a project that will require a user based process to interact > with the system as if it were a filesystem. The traditional way I have seen > this done is as the system NFS mounting itself (ala AMD). I would really lik e > a more clean approach to this. What I am interested in is a 'User Space > File System' that would interact with a user process in a similiar manor > to how nfsd's do. A process would issue a mount (ok, this is different than > NFSDs), then it would make a special system call with a structure, that > call would return whenever a request was pending with the structure filled in > with the appropriate information. The user process would fulfill the request , > pack the return data into the structure and call kernel again. > > I have a number of questions on more specific ideas (like caching, inode/vnod e > interaction, etc). But I am just feeling arround for what people think > about this. Any ideas/comments? > > -- > David Cross | email: crossd@cs.rpi.edu > Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~cross d > Rensselaer Polytechnic Institute, | Ph: 518.276.2860 > Department of Computer Science | Fax: 518.276.4033 > I speak only for myself. | WinNT:Linux::Linux:FreeBSD > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 19 23:59:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from not.demophon.com (ns.demophon.com [193.65.70.13]) by hub.freebsd.org (Postfix) with ESMTP id 1A7FB15200 for ; Mon, 19 Jul 1999 23:59:15 -0700 (PDT) (envelope-from will@not.demophon.com) Received: (from will@localhost) by not.demophon.com (8.9.3/8.8.7) id JAA22179; Tue, 20 Jul 1999 09:53:24 +0300 (EEST) (envelope-from will) To: des@flood.ping.uio.no (Dag-Erling Smorgrav) Cc: hackers@freebsd.org Subject: Re: Overcommit and calloc() References: <001f01bed205$e8aeecc0$291c453f@kbyanc.alcnet.com> From: Ville-Pertti Keinonen Date: 20 Jul 1999 09:53:24 +0300 In-Reply-To: des@flood.ping.uio.no's message of "19 Jul 1999 19:41:31 +0300" Message-ID: <86zp0rizh7.fsf@not.demophon.com> Lines: 21 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG des@flood.ping.uio.no (Dag-Erling Smorgrav) writes: > "Kelly Yancey" writes: > > Ahh...but wouldn't the bzero() touch all of the memory just allocated > > functionally making it non-overcommit? > > No. If it were an "non-overcomitting malloc", it would return NULL and > set errno to ENOMEM, instead of dumping core. It won't dump core. If it isn't the biggest process, it'll simply succeed, but somebody else is killed. If it's the biggest process, it'll die with SIGKILL without dumping core. There *are* systems that kill "random" processes when swap runs out, presumably when they need to actually get pages that aren't available. FreeBSD is not one of them. Overcommit still has nothing to do with malloc. Either the *system* is overcommitted or it isn't - per-process overcommitment is irrelevant, as is the way memory has become overcommitted. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 0:17:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 20130152DE for ; Tue, 20 Jul 1999 00:17:29 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id AAA35074; Tue, 20 Jul 1999 00:16:53 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Tue, 20 Jul 1999 00:16:53 -0700 (PDT) From: Vincent Poy To: Modred Cc: sthaug@nethelp.no, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, Modred wrote: > On Sat, 17 Jul 1999, Vincent Poy wrote: > > > > > > > By reading the man page? > > > The manpage doesn't really say anything about how to use ttcp... > > I don't think manpage useage is -hackers-esque. I know. > > There is no ttcp binary anywhere on either my -CURRENT, > > 3.2-RELEASE and 3.1-RELEASE systems. > > Ever hear of ports? Or is 'how to use the ports collection' suddenly > -hackers material? That, and .sig files that contain more relevant bits > than the sender's posts... I know there is ports. But you are missing the boat. There is a ttcp manpage by default and that has nothing to do with ttcp in the ports. In fact, ttcp wasn't in the ports tree until the last few months. > Oh, and I'd appreciate it if you could refrain from quoting this entire > message to simply say, 'Interesting'... Thanks. I don't post one word replies. And if you wanted to flame, atleast learn to do it privately... Not to mention that atleast my posts were FreeBSD related, yours is like 180 degrees off-topic. > > > Later, > --mike Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 0:21:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id BA15B1507C for ; Tue, 20 Jul 1999 00:21:33 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id AAA35092; Tue, 20 Jul 1999 00:18:57 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Tue, 20 Jul 1999 00:18:57 -0700 (PDT) From: Vincent Poy To: Modred Cc: Leif Neland , freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, Modred wrote: > > I'm not sure if it shows the mac address of the cisco's port or > > the actual device connected to it... > > You see the MAC of the switch's port. It's been too long since I've > played on a Catalyst... but what does 'sh arp' display? Any arp -> port > -> host correlations? Good luck... :) Even if it did show the arp of the actual host, it's useless if it doesn't show the IP of the device connected to it since how will one know what device is what. > > That's a option too... Only problem is that can take forever. :-) > > Yeah, I've noticed the 'sync-up time' takes quite awhile on a Catalyst > running 100Mbps. It's pretty fast... Just it seems like the switch by default isn't like as secure as they say it is. People on other ports can't still sniff packets on the LAN. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 1:13:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 6DE1415248 for ; Tue, 20 Jul 1999 01:13:02 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 692 invoked by uid 1001); 20 Jul 1999 08:12:58 +0000 (GMT) To: vince@venus.GAIANET.NET Cc: modred@ns1.antisocial.net, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? From: sthaug@nethelp.no In-Reply-To: Your message of "Tue, 20 Jul 1999 00:18:57 -0700 (PDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 20 Jul 1999 10:12:58 +0200 Message-ID: <690.932458378@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You see the MAC of the switch's port. It's been too long since I've > > played on a Catalyst... but what does 'sh arp' display? Any arp -> port > > -> host correlations? Good luck... :) > > Even if it did show the arp of the actual host, it's useless if it > doesn't show the IP of the device connected to it since how will one know > what device is what. As long as the hosts are using TCP/IP to communicate, you should be able to get the IP to MAC address mapping from the ARP table of any host (or router) connected to the same segment. You may have to look at the ARP tables from several hosts (or use a broadcast ping) to get all the mappings. Isn't this rather obvious? > > Yeah, I've noticed the 'sync-up time' takes quite awhile on a Catalyst > > running 100Mbps. > > It's pretty fast... Just it seems like the switch by default isn't > like as secure as they say it is. People on other ports can't still sniff > packets on the LAN. Ciscos have a 30 second delay when you connect something to a switch port. This is given by the spanning tree protocol. If you want this to go faster, turn off the spanning tree protocol on that port (OK if you can guarantee no loops in the network from that port). Not sure what you mean by "the switch by default isn't like as secure as they say it is". A switch is a bridge, and will isolate traffic between ports. However, broadcast (and in many cases multicast) traffic will be sent on all ports. Also, if the MAC address tables on the switch fills up, any traffic from a *new* MAC address will be sent on all ports. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 1:18:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from btm4r4.alcatel.be (btm4r4.alcatel.be [195.207.101.110]) by hub.freebsd.org (Postfix) with ESMTP id 028B3151A4; Tue, 20 Jul 1999 01:18:09 -0700 (PDT) (envelope-from livensw@rc.bel.alcatel.be) Received: from btmq9s.rc.bel.alcatel.be (btmq9s.rc.bel.alcatel.be [138.203.65.182]) by btm4r4.alcatel.be (8.9.1a/8.9.1) with ESMTP id KAA06904; Tue, 20 Jul 1999 10:11:13 +0200 (MET DST) Received: from btmq9z.rc.bel.alcatel.be (btmq9z [138.203.65.192]) by btmq9s.rc.bel.alcatel.be (8.8.8+Sun/8.8.8) with ESMTP id KAA27078; Tue, 20 Jul 1999 10:13:28 +0200 (MET DST) Received: (from livensw@localhost) by btmq9z.rc.bel.alcatel.be (8.8.8+Sun/8.8.8) id KAA13057; Tue, 20 Jul 1999 10:10:57 +0200 (MET DST) Date: Tue, 20 Jul 1999 10:10:57 +0200 From: Wim Livens To: Wes Peters , freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: Re: bug in ip_forward() ? Message-ID: <19990720101057.D1676@rc.bel.alcatel.be> References: <19990719172546.C1676@rc.bel.alcatel.be> <37937846.55C1867E@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <37937846.55C1867E@softweyr.com>; from Wes Peters on Mon, Jul 19, 1999 at 01:11:02PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 19, 1999 at 01:11:02PM -0600, Wes Peters wrote: > > +------+ +------+ +------+ +------+ > > | |4.2 4.1| |2.1 2.2| |5.1 5.2| | > > |btm22t|---------|btm22q|---------|btm22r|---------|btm22u| > > | | | | | | | | > > +------+ +------+ +------+ +------+ > > > > And this is what I do: > > > > btm22t# ping 192.168.5.2 > > ok, it works... > > btm22q# route delete -net 192.168.5.0 -netmask 255.255.255.252 192.168.2.2 > > ok, ping stops. > > btm22q# route add -net 192.168.5.0 -netmask 255.255.255.252 192.168.2.2 > > ping doesn't work > > And it shouldn't, you haven't given it an appropriate route. From route(8): > > The other commands have the following syntax: > > route [-n] command [-net | -host] destination gateway > > where destination is the destination host or network, gateway is the > next-hop intermediary via which packets should be routed. > > There's the important part right there: gateway is the *next-hop* intermediary > via which packets should be routed. Note that the ping is done from btm22t while the route is deleted/added on btm22q. (I've ommited the 192.168 prefix in the addresses in the figure). Now, I think I did specify a correct next-hop, namely 192.168.2.2, which is a local destination for btm22q. Thanks anyway, I should have been more clear. Wim. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 1:51:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 0768A152B1 for ; Tue, 20 Jul 1999 01:51:07 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id BAA35550; Tue, 20 Jul 1999 01:47:15 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Tue, 20 Jul 1999 01:47:15 -0700 (PDT) From: Vincent Poy To: sthaug@nethelp.no Cc: modred@ns1.antisocial.net, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? In-Reply-To: <690.932458378@verdi.nethelp.no> 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, 20 Jul 1999 sthaug@nethelp.no wrote: > > > You see the MAC of the switch's port. It's been too long since I've > > > played on a Catalyst... but what does 'sh arp' display? Any arp -> port > > > -> host correlations? Good luck... :) > > > > Even if it did show the arp of the actual host, it's useless if it > > doesn't show the IP of the device connected to it since how will one know > > what device is what. > > As long as the hosts are using TCP/IP to communicate, you should be able > to get the IP to MAC address mapping from the ARP table of any host (or > router) connected to the same segment. You may have to look at the ARP > tables from several hosts (or use a broadcast ping) to get all the > mappings. > > Isn't this rather obvious? That would only work if the machines are on the hub but if each device is on a dedicated port on the switch of it's own, it's not supposed to see the other machines... Atleast we can't see the other machines MAC with netstat -r in FreeBSD. > > > Yeah, I've noticed the 'sync-up time' takes quite awhile on a Catalyst > > > running 100Mbps. > > > > It's pretty fast... Just it seems like the switch by default isn't > > like as secure as they say it is. People on other ports can't still sniff > > packets on the LAN. > > Ciscos have a 30 second delay when you connect something to a switch port. > This is given by the spanning tree protocol. If you want this to go faster, > turn off the spanning tree protocol on that port (OK if you can guarantee > no loops in the network from that port). I think this is true with any switch that has the STP feature. > Not sure what you mean by "the switch by default isn't like as secure as > they say it is". A switch is a bridge, and will isolate traffic between > ports. However, broadcast (and in many cases multicast) traffic will be > sent on all ports. Also, if the MAC address tables on the switch fills > up, any traffic from a *new* MAC address will be sent on all ports. No idea but it seems like the people who sold the Cisco switches atleast claimed that each port is supposed to be secure to prevent packet sniffing by people on the other ports... Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 2: 3:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id 4648F151C2 for ; Tue, 20 Jul 1999 02:03:13 -0700 (PDT) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Tue, 20 Jul 1999 10:02:14 +0100 Received: from voodoo.pandhm.co.uk (VOODOO [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id 3WRWC681; Tue, 20 Jul 1999 10:03:00 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 116VnP-000Dyx-00; Tue, 20 Jul 1999 10:02:43 +0100 Date: Tue, 20 Jul 1999 10:02:43 +0100 To: Jason Thorpe Cc: Dominic Mitchell , "David E. Cross" , Oscar Bonilla , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD, and userfs too. Message-Id: <19990720100243.B53519@palmerharvey.co.uk> References: <199907191955.MAA13308@lestat.nas.nasa.gov> MIME-Version: 1.0 X-Mailer: Mutt 0.95.6i In-Reply-To: <199907191955.MAA13308@lestat.nas.nasa.gov>; from Jason Thorpe on Mon, Jul 19, 1999 at 12:55:19PM -0700 From: Dominic Mitchell Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 19, 1999 at 12:55:19PM -0700, Jason Thorpe wrote: > On Mon, 19 Jul 1999 20:44:18 +0100 > Dominic Mitchell wrote: > > > Lovely. Sounds like a much better way to do the Solaris/Linux (and > > NetBSD?) /etc/nsswitch.conf stuff. On Solaris at least, this is > > implemented using masses of weird shared objects... > > The plan for NetBSD is that things will also be handled with dynamic > modules, but those dynamic modules will be glued into a `nscd'[*] (if you > use Solaris, you're familiar with the name :-). > > [*] We are planning on not having all of the problems that the Solaris > nscd has, and that people often complain about. > > This will allow libc to simply make a call to nscd (or fallback onto > traditional `files' lookup), and nscd will handle all but the `files' > case. This allows system-wide caching, and puts all of the complexity > in one place. How will you get around one of the major bugbears of the Solaris implementation, that is nscd serialises access to these databases? I understand that the caching will allow you to return most responses quickly, but on a busy system (web cache doing dns requests?) it might well bog down... -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator In Mountain View did Larry Wall Sedately launch a quiet plea: That DOS, the ancient system, shall On boxes pleasureless to all Run Perl though lack they C. -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 2:43:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1FB011510F for ; Tue, 20 Jul 1999 02:43:15 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id DAA43400; Tue, 20 Jul 1999 03:42:22 -0600 (MDT) (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 DAA85004; Tue, 20 Jul 1999 03:42:21 -0600 (MDT) Message-Id: <199907200942.DAA85004@harmony.village.org> To: "Leif Neland" Subject: Re: Sv: speed of file(1) Cc: "Matthew Dillon" , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 19 Jul 1999 23:31:42 +0200." <02a901bed22e$25164e60$0e00a8c0@neland.dk> References: <02a901bed22e$25164e60$0e00a8c0@neland.dk> <199907192045.NAA99619@apollo.backplane.com> Date: Tue, 20 Jul 1999 03:42:21 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe the P60 is memory starved. Thrashing would cause this huge factor of speed difference... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 2:44:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id AC9EA151C4; Tue, 20 Jul 1999 02:44:16 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id DAA43407; Tue, 20 Jul 1999 03:44:15 -0600 (MDT) (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 DAA85024; Tue, 20 Jul 1999 03:44:14 -0600 (MDT) Message-Id: <199907200944.DAA85024@harmony.village.org> To: Geoffrey Robinson Subject: Re: PAO Cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 19 Jul 1999 22:11:35 EDT." <3793DAD7.67FBAC6D@click2net.com> References: <3793DAD7.67FBAC6D@click2net.com> Date: Tue, 20 Jul 1999 03:44:14 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3793DAD7.67FBAC6D@click2net.com> Geoffrey Robinson writes: : pccardc: /dev/card0: Device not configured Rebuild your kernel with pccard 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 Jul 20 3:11:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 83087152B3 for ; Tue, 20 Jul 1999 03:11:46 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id MAA07923; Tue, 20 Jul 1999 12:10:21 +0200 (CEST) (envelope-from des) To: "Kelly Yancey" Cc: "Dag-Erling Smorgrav" , Subject: Re: Overcommit and calloc() References: <002201bed217$e94beae0$291c453f@kbyanc.alcnet.com> From: Dag-Erling Smorgrav Date: 20 Jul 1999 12:10:20 +0200 In-Reply-To: "Kelly Yancey"'s message of "Mon, 19 Jul 1999 14:52:55 -0400" Message-ID: Lines: 21 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kelly Yancey" writes: > I don't know how many programs make use of calloc() but would not a more > efficient algorithm be to better integrate it with malloc() such that if > there is a fragment on the heap which can be used, bzero() it and return > that, otherwise, simply call sbrk() and return that (since it is already > zero'ed). Currently, in the event that malloc() simply returns newly > sbrk()'ed memory, we unnecessarily zero it again. I don't see the point. I've seen very few examples of justified calloc() use. For instance, I see a lot of people use calloc() instead of malloc() when allocating strings, just to make sure they'll be terminated after a strncpy(), instead of simply setting the last character to '\0' after the strncpy(). When I allocate memory, I usually intend to put something in it. There's always the odd struct sockaddr_in which I bzero() before filling it in, but they're usually on the stack. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 3:20: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from metriclient-2.uoregon.edu (metriclient-2.uoregon.edu [128.223.172.2]) by hub.freebsd.org (Postfix) with ESMTP id 7FD0E1530A for ; Tue, 20 Jul 1999 03:19:55 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by metriclient-2.uoregon.edu (8.9.1/8.8.7) id DAA24478; Tue, 20 Jul 1999 03:19:08 -0700 (PDT) Message-ID: <19990720031908.63115@hydrogen.fircrest.net> Date: Tue, 20 Jul 1999 03:19:08 -0700 From: John-Mark Gurney To: Dag-Erling Smorgrav Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Overcommit and calloc() References: <002201bed217$e94beae0$291c453f@kbyanc.alcnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Dag-Erling Smorgrav on Tue, Jul 20, 1999 at 12:10:20PM +0200 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav scribbled this message on Jul 20: > When I allocate memory, I usually intend to put something in it. > There's always the odd struct sockaddr_in which I bzero() before > filling it in, but they're usually on the stack. and even then, I don't believe in filling sockaddr_in w/ bzero, I believe in using getsockaddr on it so that you actually get all the fields filled out properly... -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 3:46:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 25DCB152D3 for ; Tue, 20 Jul 1999 03:46:02 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id MAA08747; Tue, 20 Jul 1999 12:45:56 +0200 (CEST) (envelope-from des) To: John-Mark Gurney Cc: Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: Overcommit and calloc() References: <002201bed217$e94beae0$291c453f@kbyanc.alcnet.com> <19990720031908.63115@hydrogen.fircrest.net> From: Dag-Erling Smorgrav Date: 20 Jul 1999 12:45:56 +0200 In-Reply-To: John-Mark Gurney's message of "Tue, 20 Jul 1999 03:19:08 -0700" Message-ID: Lines: 14 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John-Mark Gurney writes: > Dag-Erling Smorgrav scribbled this message on Jul 20: > > When I allocate memory, I usually intend to put something in it. > > There's always the odd struct sockaddr_in which I bzero() before > > filling it in, but they're usually on the stack. > and even then, I don't believe in filling sockaddr_in w/ bzero, I > believe in using getsockaddr on it so that you actually get all the > fields filled out properly... See? One less reason to use bzero() / calloc() :) DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 4: 3: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tardis.patho.gen.nz (tardis.patho.gen.nz [203.97.2.226]) by hub.freebsd.org (Postfix) with ESMTP id 9B50B151AA for ; Tue, 20 Jul 1999 04:02:54 -0700 (PDT) (envelope-from jabley@tardis.patho.gen.nz) Received: (from jabley@localhost) by tardis.patho.gen.nz (8.9.3/8.9.3) id WAA16305; Tue, 20 Jul 1999 22:59:30 +1200 (NZST) Date: Tue, 20 Jul 1999 22:59:30 +1200 From: Joe Abley To: Oscar Bonilla Cc: Wes Peters , Mike Smith , "David E. Cross" , Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD Message-ID: <19990720225929.A9510@patho.gen.nz> References: <199907192111.OAA01326@dingo.cdrom.com> <3793ABE0.15090E38@softweyr.com> <19990719180026.A830@fisicc-ufm.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <19990719180026.A830@fisicc-ufm.edu>; from Oscar Bonilla on Mon, Jul 19, 1999 at 06:00:26PM -0600 X-Files: the Truth is Out There Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 19, 1999 at 06:00:26PM -0600, Oscar Bonilla wrote: > I agree. In solaris (and linux by the way) all you do is set > passwd ldap files > in /etc/nsswitch.conf > and that's it. In Solaris, it's passwd: ldap files ^ nsswitch.conf(4), SunOS 5.5.1: ... There is an entry in /etc/nsswitch.conf for each database. Typically these entries will be simple, such as "protocols: files" or "networks: files nisplus". However, when multiple sources are specified it is sometimes necessary to define precisely the circumstances under which each source will be tried. A source can return one of the following codes: Status Meaning SUCCESS Requested database entry was found UNAVAIL Source is not responding or corrupted NOTFOUND Source responded "no such entry" TRYAGAIN Source is busy, might respond to retries For each status code, two actions are possible: Action Meaning continue Try the next source in the list return Return now The complete syntax of an entry is ::= ":" [ []]* ::= "[" + "]" ::= "=" ::= "success" | "notfound" | "unavail" | "tryagain" ::= "return" | "continue" ... Actually, this message is now bordering on the useful, when all I meant to be was pedantic. I'll stop now, before I go too far; suffice to say the Solaris implementation has some other elements worthy of consideration if compatability is worth aiming for. It's maybe worth mentioning that /etc/host.conf might be a candidate for the attic if the Solaris implementation was adopted on a wholesale basis (i.e. including the "hosts:" key). Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 5:11:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hda.hda.com (hda-bicnet.bicnet.net [209.244.238.132]) by hub.freebsd.org (Postfix) with ESMTP id 8FFA014C9A for ; Tue, 20 Jul 1999 05:11:40 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id HAA19384; Tue, 20 Jul 1999 07:36:36 -0400 (EDT) From: Peter Dufault Message-Id: <199907201136.HAA19384@hda.hda.com> Subject: Re: Overcommit and calloc() In-Reply-To: <001f01bed205$e8aeecc0$291c453f@kbyanc.alcnet.com> from Kelly Yancey at "Jul 19, 99 12:44:03 pm" To: kbyanc@alcnet.com (Kelly Yancey) Date: Tue, 20 Jul 1999 07:36:35 -0400 (EDT) Cc: des@flood.ping.uio.no, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, bzero could map all memory (outside the boundaries) to a single zeroed page marked copy on write. The statistics you could gather might then point out some grossly broken programs. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 5:12:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id AB9C5152FE for ; Tue, 20 Jul 1999 05:12:00 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 116YiV-0002Wk-00; Tue, 20 Jul 1999 14:09:51 +0200 From: Sheldon Hearn To: Warner Losh Cc: Tim Vanderhoek , freebsd-hackers@FreeBSD.ORG Subject: Re: OpenBSD's strlcpy(3) and strlcat(3) In-reply-to: Your message of "Thu, 15 Jul 1999 18:40:17 CST." <199907160040.SAA01415@harmony.village.org> Date: Tue, 20 Jul 1999 14:09:51 +0200 Message-ID: <9717.932472591@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 15 Jul 1999 18:40:17 CST, Warner Losh wrote: > I can see your point. I don't know if I'll like your man pages better > or not, but I'd be willing to give them a spin. Bring on the humble pie. It really isn't practical to try to have these pages match the approach of the existing pages. The best approach would be to add a description of strlcpy() to the strcpy.3 page and a description of strlcat() to the strcat.3 page. The differences between the new functions and those whose manpages they should be described in make for more confusion than we save by including them there. So I withdraw my objection to the style of the strl*() manpages, but only because I have nothing better to offer. ;-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 6:43:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mx.globalone.ru (mx.globalone.ru [194.84.254.251]) by hub.freebsd.org (Postfix) with ESMTP id ACF51152BF for ; Tue, 20 Jul 1999 06:43:10 -0700 (PDT) (envelope-from a.voropay@globalone.ru) Received: from hq.globalone.ru (hq.globalone.ru [172.16.38.1]) by mx.globalone.ru (8.9.3/8.9.3) with ESMTP id RAA11765 for ; Tue, 20 Jul 1999 17:42:16 +0400 Received: from host205.spb.in.rosprin.ru ([172.17.13.205]) by hq.globalone.ru (Netscape Messaging Server 3.5) with SMTP id 168; Tue, 20 Jul 1999 17:42:21 +0400 Message-ID: <01ca01bed2b6$0b235ba0$cd0d11ac@host205.spb.in.rosprin.ru> Reply-To: "Alexander Voropay" From: "Alexander Voropay" To: Cc: Subject: Re: glibc Date: Tue, 20 Jul 1999 17:44:11 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Has anybody done a port of glibc to FreeBSD? (I'm not interested in >> opinions about how poor it is or how evil the FSF are; I'm only asking to >> avoid duplicate work. Thanks.) > >Perhaps if you explain what it is you're trying to accomplish, there might >be an easier option than porting *shudder* glibc? glibc has better POSIX locale and I18N / L10N support : - localedef(1) and locale(1) utilities - nl_langinfo(3) XPG-4 function - gettext built-in into glibc -- -=AV=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 6:55:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (Postfix) with ESMTP id 01839152D9 for ; Tue, 20 Jul 1999 06:55:16 -0700 (PDT) (envelope-from eT@post.com) Received: (from root@localhost) by Thingol.KryptoKom.DE (8.9.1/8.9.1) id RAA02218 for ; Tue, 20 Jul 1999 17:49:53 +0200 Received: from cirdan.kryptokom.de by KryptoWall via smtpp (Version 1.2.0) id kwa02205; Tue Jul 20 17:49:24 1999 Received: from fwd.kryptokom.de ([192.168.6.40]) by Cirdan.KryptoKom.DE (8.8.8/8.8.8) with ESMTP id QAA09213 for ; Tue, 20 Jul 1999 16:00:36 +0200 Received: from post.com (localhost [127.0.0.1]) by fwd.kryptokom.de (8.9.2/8.9.2) with ESMTP id PAA00678 for ; Tue, 20 Jul 1999 15:58:12 +0200 (CEST) (envelope-from eT@post.com) Message-ID: <37948074.E413DA52@post.com> Date: Tue, 20 Jul 1999 15:58:12 +0200 From: eT X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Hackers FreeBSD Subject: KDE on FreeBSD (missing symbols) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greets .. I decided to compile KDE-1.1.1 for my 4.0-CURRENT. After compiling all (kde-1.1 and qt-1.44) I get the following errors when startx'ing: ld-elf.so complains about not finding these symbols: __ti6QFrame __ti7QObject __ti7Qblahblahblah I pressume there is something wrong with the way I compiled qt-1.44? I spose I should be asking this question to KDE mailing lists but I reckon the FreeBSD'ers will know more about the problem. eT -- Etienne de Bruin; eT@post.com visit eT on the web: http://listen.to/eT (last update: 12 Mar 1999) "six days the universe was made, supernatural" - dc talk, supernatural. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 6:55:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from prontomail9.prontomail.com (prontomail9.prontomail.com [209.185.149.109]) by hub.freebsd.org (Postfix) with ESMTP id 32F66152D0 for ; Tue, 20 Jul 1999 06:55:25 -0700 (PDT) (envelope-from avi@imail.ru) Received: from avi (209.185.149.227) by prontomail9.prontomail.com (NPlex 2.0.123) for hackers@FreeBSD.org; Tue, 20 Jul 1999 06:51:17 -0700 From: "Andrei Iltchenko" Message-Id: <199907200651372@avi.imail.ru> Date: Tue, 20 Jul 1999 17:57:35 +0400 X-Priority: Normal Content-Type: text/plain; charset=koi8-r To: hackers@FreeBSD.org Subject: POSIX threads question X-Mailer: Web Based Pronto Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, I have written a multithreaded application. In which, I have redirected stdin, stdout and stderr to some files. Does anybody know why if I make a call to fprintf family of functions, I get nothing in the output files, until I call fflush? Thank you in advance. ------------------------------------------- Sent by InfoArt iMail http://www.infoart.ru; http://www.stars.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 7:16:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from thneed.ubergeeks.com (thneed.ubergeeks.com [206.205.41.245]) by hub.freebsd.org (Postfix) with ESMTP id 6AE7515238; Tue, 20 Jul 1999 07:16:10 -0700 (PDT) (envelope-from adrian@ubergeeks.com) Received: from localhost (adrian@localhost) by thneed.ubergeeks.com (8.9.3/8.9.3) with ESMTP id KAA02488; Tue, 20 Jul 1999 10:15:34 -0400 (EDT) (envelope-from adrian@ubergeeks.com) X-Authentication-Warning: thneed.ubergeeks.com: adrian owned process doing -bs Date: Tue, 20 Jul 1999 10:15:34 -0400 (EDT) From: Adrian Filipi-Martin Reply-To: Adrian Filipi-Martin To: "Brian F. Feldman" Cc: "Jordan K. Hubbard" , Jamie Howard , freebsd-hackers@FreeBSD.ORG Subject: Re: m68k Support in FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, Brian F. Feldman wrote: > On Mon, 19 Jul 1999, Jordan K. Hubbard wrote: > > > > website (http://www.freebsd.org/~green/FreeBSD-68k.txt). In about two > > > weeks I'll have a spare Macintosh IIsi and would like to have a run at > > > FreeBSD on it. So, to the point, where can I get it? :) > > > > I'd say that's a question for Grant Stockly, the person mentioned in > > green's web-cited message. It's certainly not part of FreeBSD and > > whether it ever will be is a matter still subject to debate. > > Isn't it more a question of whether a proper cross-build system will > be available within the time frame that m68ks aren't completely obsolete? I think it's safe to say m68k will be with us for a long, long time. Maybe not on my desktop, but it will be with us. Dont' forget about all those routers, ATM switches, palm pilots, etc. that are all m68k based. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 7:32: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from voyager.fisicc-ufm.edu (ip-46-094.guate.net [200.12.46.94]) by hub.freebsd.org (Postfix) with ESMTP id 46F8F15187 for ; Tue, 20 Jul 1999 07:31:41 -0700 (PDT) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id IAA00827; Tue, 20 Jul 1999 08:28:25 -0600 (CST) (envelope-from obonilla) Date: Tue, 20 Jul 1999 08:28:25 -0600 From: Oscar Bonilla To: Joe Abley Cc: Oscar Bonilla , Wes Peters , Mike Smith , "David E. Cross" , Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD Message-ID: <19990720082825.B793@fisicc-ufm.edu> References: <199907192111.OAA01326@dingo.cdrom.com> <3793ABE0.15090E38@softweyr.com> <19990719180026.A830@fisicc-ufm.edu> <19990720225929.A9510@patho.gen.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <19990720225929.A9510@patho.gen.nz>; from Joe Abley on Tue, Jul 20, 1999 at 10:59:30PM +1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 20, 1999 at 10:59:30PM +1200, Joe Abley wrote: > On Mon, Jul 19, 1999 at 06:00:26PM -0600, Oscar Bonilla wrote: > > I agree. In solaris (and linux by the way) all you do is set > > passwd ldap files > > in /etc/nsswitch.conf > > and that's it. > > In Solaris, it's > > passwd: ldap files > ^ > > nsswitch.conf(4), SunOS 5.5.1: > > ... > There is an entry in /etc/nsswitch.conf for each database. > Typically these entries will be simple, such as "protocols: > files" or "networks: files nisplus". However, when multiple > sources are specified it is sometimes necessary to define > precisely the circumstances under which each source will be > tried. A source can return one of the following codes: > > Status Meaning > SUCCESS Requested database entry was found > UNAVAIL Source is not responding or corrupted > NOTFOUND Source responded "no such entry" > TRYAGAIN Source is busy, might respond to > retries > > For each status code, two actions are possible: > > Action Meaning > continue Try the next source in the list > return Return now > > The complete syntax of an entry is > > ::= ":" [ []]* > ::= "[" + "]" > ::= "=" > ::= "success" | "notfound" | "unavail" | "tryagain" > ::= "return" | "continue" > ... > > Actually, this message is now bordering on the useful, when all I meant > to be was pedantic. I'll stop now, before I go too far; suffice to say > the Solaris implementation has some other elements worthy of consideration > if compatability is worth aiming for. > > It's maybe worth mentioning that /etc/host.conf might be a candidate for > the attic if the Solaris implementation was adopted on a wholesale basis > (i.e. including the "hosts:" key). > Couldn't we do this with /etc/auth.conf? What's the real purpose of this file? From the man page: "auth.conf contains various attributes important to the authentication code, most notably kerberos(5) for the time being." Isn't this what PAM is about? authentication? or does auth.conf cover the "other" part of authentication, basically the getpw* stuff? Regards, -Oscar -- For PGP Public Key: finger obonilla@fisicc-ufm.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 7:39:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 127B214FA2 for ; Tue, 20 Jul 1999 07:39:47 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id QAA25780; Tue, 20 Jul 1999 16:23:10 +0200 (MET DST) Date: Tue, 20 Jul 1999 16:23:09 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Andrei Iltchenko Cc: hackers@FreeBSD.ORG Subject: Re: POSIX threads question In-Reply-To: <199907200651372@avi.imail.ru> 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 Files are block buffered not line buffered. Switch on hot piping (sorry, don't know how to), or wait until you have written 64kb, of flush more often. Nick On Tue, 20 Jul 1999, Andrei Iltchenko wrote: > Hi there, > > I have written a multithreaded application. > In which, I have redirected stdin, stdout and stderr to some files. > > Does anybody know why if I make a call to fprintf family of functions, I get nothing in the output files, until I call fflush? > > Thank you in advance. > > ------------------------------------------- > Sent by InfoArt iMail > http://www.infoart.ru; http://www.stars.ru > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 7:45:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dns0.sports.gov.uk (dns0.sports.gov.uk [195.89.151.148]) by hub.freebsd.org (Postfix) with ESMTP id 9041C1534D for ; Tue, 20 Jul 1999 07:45:06 -0700 (PDT) (envelope-from ad@dns0.sports.gov.uk) Message-ID: <37948B77.875DF2D3@dns0.sports.gov.uk> Date: Tue, 20 Jul 1999 15:45:11 +0100 From: Andy Doran X-Accept-Language: en-GB,en,en-* MIME-Version: 1.0 Cc: Andrei Iltchenko , hackers@FreeBSD.ORG Subject: Re: POSIX threads question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG man 3 setvbuf - ad > Hi there, > > I have written a multithreaded application. > In which, I have redirected stdin, stdout and stderr to some files. > > Does anybody know why if I make a call to fprintf family of functions, I get nothing in the output files, until I call fflush? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 8:22:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 8C60A1531A for ; Tue, 20 Jul 1999 08:22:52 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id LAA29350; Tue, 20 Jul 1999 11:20:08 -0400 (EDT) Message-Id: <199907201520.LAA29350@cs.rpi.edu> To: Oscar Bonilla Cc: Joe Abley , Wes Peters , Mike Smith , "David E. Cross" , Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: PAM & LDAP in FreeBSD In-Reply-To: Message from Oscar Bonilla of "Tue, 20 Jul 1999 08:28:25 MDT." <19990720082825.B793@fisicc-ufm.edu> Date: Tue, 20 Jul 1999 11:20:02 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Couldn't we do this with /etc/auth.conf? What's the real purpose of this > file? From the man page: "auth.conf contains various attributes important to > the authentication code, most notably kerberos(5) for the time being." > Isn't this what PAM is about? authentication? or does auth.conf cover the > "other" part of authentication, basically the getpw* stuff? This is bigger than just authentication. This is about the various databases that the machine needs to keep in touch with.. hosts, passwd, ethers, services, protocols, group, etc... For example using auth.conf how would one [cleanly] instruct the system that for group information it should use NIS, for hosts, DNS, and for passwords NIS (for the passwd entry) and Kerberos (for the password). What you would have when you are done would be very similar to 'nsswitch.conf'. With the exception that even nsswitch.conf cannot do everything, you still need auth.conf (shouldn't this really be pam.conf?) to tell the system to use kerberos (or whatever) to authenticate the user. BTW: To clear up some possible misunderstanding from earlier, I am 100% in support of /etc/nsswitch.conf for FreeBSD. My "FreeNSD" ;) 'nsd' server would read /etc/nsswitch.conf for its configuration, just like the Irix version does. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 8:29:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (Postfix) with ESMTP id 3D5DE15311 for ; Tue, 20 Jul 1999 08:29:25 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-35.camalott.com [208.229.74.35]) by mail.camalott.com (8.8.7/8.8.7) with ESMTP id KAA24259 for ; Tue, 20 Jul 1999 10:32:04 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.3) id LAA00999; Thu, 15 Jul 1999 11:26:11 -0500 (CDT) (envelope-from joelh) To: Matthew Dillon Cc: Stephen Hocking-Senior Programmer PGS Tensor Perth , hackers@FreeBSD.ORG, shocking@bandicoot.prth.tensor.pgs.com Subject: Re: Setting up a firewall with dynamic IPs References: <199907140116.JAA15266@ariadne.tensor.pgs.com> <199907140206.TAA85713@apollo.backplane.com> From: Joel Ray Holveck Date: 15 Jul 1999 11:26:11 -0500 In-Reply-To: Matthew Dillon's message of "Tue, 13 Jul 1999 19:06:40 -0700 (PDT)" Message-ID: <86r9m9hobg.fsf@detlev.UUCP> Lines: 15 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Usually if a connection succeeds the firewall isn't stopping it > at all. How is nmap figuring out the service type? I assume by > making a connection and probing it. Nothing so elegant. It uses /etc/services. Most of its scans never finish opening the connection. (This is why it will normally mislabel RPC services; if in doubt, use rpcinfo.) joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 8:42:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [196.37.91.10]) by hub.freebsd.org (Postfix) with ESMTP id D1EA51534C for ; Tue, 20 Jul 1999 08:42:14 -0700 (PDT) (envelope-from rbezuide@oskar.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.nanoteq.co.za (8.9.0/8.9.0) id RAA02634 for freebsd-hackers@freebsd.org; Tue, 20 Jul 1999 17:42:33 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199907201542.RAA02634@oskar.nanoteq.co.za> Subject: if_dl.h in stable causes sendmail segmentation To: freebsd-hackers@freebsd.org Date: Tue, 20 Jul 1999 17:42:31 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... I have the following situation... A machine running a 3.2-STABLE of a few weeks ago ... When the machine booted I saw that newaliases (sendmail -bi) exited with a segmentation fault. I further inspected and found that if I do a ifconfig of a interface (fxp0 or de0) newaliases is ok, but when I do an ifconfig fxp0 delete the newaliases exits on a segmentation fault. e.g. --------------------- Amnesiac# ifconfig -au de0: flags=8843 mtu 1500 inet 196.37.91.253 netmask 0xffffff00 broadcast 196.37.91.255 ether 00:e0:29:00:e5:19 media: autoselect (10baseT/UTP) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 Amnesiac# newaliases /etc/aliases: 19 aliases, longest 10 bytes, 190 bytes total Amnesiac# ifconfig de0 delete Amnesiac# newaliases Segmentation fault Amnesiac# ifconfig de0 up Amnesiac# newaliases /etc/aliases: 19 aliases, longest 10 bytes, 190 bytes total Amnesiac# ---------------------- I then used the kernel sources from a few weeks after the 3.2-RELEASE and compiled the kernel - now everything works ok ... no segmentation fault. I eventually traced the problem down to the following header file /usr/src/sys/net/if_dl.h If I use the old header file ... no problem ... use the latest one .. sendmail crashes (and looks like gated also does this). Here is the diff jarrow# diff -c if_dl.h ../../sys.new/net/if_dl.h *** if_dl.h Tue Jul 20 16:18:54 1999 --- ../../sys.new/net/if_dl.h Thu May 27 05:06:41 1999 *************** *** 31,37 **** * SUCH DAMAGE. * * @(#)if_dl.h 8.1 (Berkeley) 6/10/93 ! * $Id: if_dl.h,v 1.6 1997/02/22 09:41:00 peter Exp $ */ #ifndef _NET_IF_DL_H_ --- 31,37 ---- * SUCH DAMAGE. * * @(#)if_dl.h 8.1 (Berkeley) 6/10/93 ! * $Id: if_dl.h,v 1.6.4.1 1999/05/27 03:06:41 julian Exp $ */ #ifndef _NET_IF_DL_H_ *************** *** 68,73 **** --- 68,75 ---- u_char sdl_slen; /* link layer selector length */ char sdl_data[12]; /* minimum work area, can be larger; contains both if name and ll address */ + u_short sdl_rcf; /* source routing control */ + u_short sdl_route[16]; /* source routing information */ }; #define LLADDR(s) ((caddr_t)((s)->sdl_data + (s)->sdl_nlen)) ---------------------- Looks like the addition of the two last entries in the structure is the problem ?? Any ideas ?? Sendmail crashes in the routine in conf.c called "load_if_names()" where it cycles through the interfaces round line 4444 if (sa->sa.sa_len > sizeof ifr->ifr_addr) the address sa->sa seems to point so where If you want any more info .. just ask :) Thanx Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 9:19:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rebel.net.au (rebel.rebel.net.au [203.20.69.66]) by hub.freebsd.org (Postfix) with ESMTP id 1BC6B1533F for ; Tue, 20 Jul 1999 09:19:17 -0700 (PDT) (envelope-from kkenn@rebel.net.au) Received: from 203.20.69.75 (dialup-5.rebel.net.au [203.20.69.75]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id BAA28237 for ; Wed, 21 Jul 1999 01:47:06 +0930 Received: (qmail 54661 invoked from network); 20 Jul 1999 16:16:56 -0000 Received: from localhost (kkenn@127.0.0.1) by localhost with SMTP; 20 Jul 1999 16:16:56 -0000 Date: Wed, 21 Jul 1999 01:46:56 +0930 (CST) From: Kris Kennaway Reply-To: kkenn@rebel.net.au To: "David E. Cross" Cc: Oscar Bonilla , Joe Abley , Wes Peters , Mike Smith , Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD In-Reply-To: <199907201520.LAA29350@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Jul 1999, David E. Cross wrote: > > Couldn't we do this with /etc/auth.conf? What's the real purpose of this > > file? From the man page: "auth.conf contains various attributes important to > > the authentication code, most notably kerberos(5) for the time being." > > Isn't this what PAM is about? authentication? or does auth.conf cover the > > "other" part of authentication, basically the getpw* stuff? > > This is bigger than just authentication. This is about the various databases > that the machine needs to keep in touch with.. hosts, passwd, ethers, services, > protocols, group, etc... For example using auth.conf how would one [cleanly] > instruct the system that for group information it should use NIS, for hosts, > DNS, and for passwords NIS (for the passwd entry) and Kerberos (for the > password). What you would have when you are done would be very similar to > 'nsswitch.conf'. With the exception that even nsswitch.conf cannot do > everything, you still need auth.conf (shouldn't this really be pam.conf?) to > tell the system to use kerberos (or whatever) to authenticate the user. It looks like we've got some good concurrent projects happening at the moment - markm and co working on PAM, the nsswitch.conf project you're talking about, and the stuff I'm working on with modularizing crypt() and supporting per-login class password hashes (I've rewritten the library since I last posted about it and expect to have my code cleaned up by tomorrow night for another snapshot). The thing to make sure is that we don't tread on each other's toes, and basically that we look for the big picture and how all these projects fit together. Kris > -- > David Cross | email: crossd@cs.rpi.edu > Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd > Rensselaer Polytechnic Institute, | Ph: 518.276.2860 > Department of Computer Science | Fax: 518.276.4033 > I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 10: 7: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.33.127]) by hub.freebsd.org (Postfix) with ESMTP id AC29B14F9A for ; Tue, 20 Jul 1999 10:07:01 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id KAA09841; Tue, 20 Jul 1999 10:06:36 -0700 (PDT) Message-Id: <199907201706.KAA09841@lestat.nas.nasa.gov> To: Dominic Mitchell Cc: "David E. Cross" , Oscar Bonilla , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD, and userfs too. Reply-To: Jason Thorpe From: Jason Thorpe Date: Tue, 20 Jul 1999 10:06:34 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Jul 1999 10:02:43 +0100 Dominic Mitchell wrote: > How will you get around one of the major bugbears of the Solaris > implementation, that is nscd serialises access to these databases? I > understand that the caching will allow you to return most responses > quickly, but on a busy system (web cache doing dns requests?) it might > well bog down... Yes, that is a known issue, and one of the things we're hoping to avoid, but just how that will be done is as-of-yet-undetermined. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 10:16:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 55F7114EAB for ; Tue, 20 Jul 1999 10:16:11 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA05685; Tue, 20 Jul 1999 10:14:44 -0700 (PDT) (envelope-from dillon) Date: Tue, 20 Jul 1999 10:14:44 -0700 (PDT) From: Matthew Dillon Message-Id: <199907201714.KAA05685@apollo.backplane.com> To: John Milford Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: USFS (User Space File System) References: <199907200536.WAA25700@soda.CSUA.Berkeley.EDU> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :David, : : Unless I am misunderstanding you, mfs does what you are :describing. : : --John No, MFS runs in supervisor mode. That mfs process that you see hanging there is just placemarking the VM space. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 10:17:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 8F91A1533F for ; Tue, 20 Jul 1999 10:17:40 -0700 (PDT) (envelope-from kbyanc@alcnet.com) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from kbyanc (ws-41.alcnet.com [63.69.28.41]) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with SMTP id NAA56392; Tue, 20 Jul 1999 13:31:54 -0400 (EDT) From: "Kelly Yancey" To: Cc: Subject: RE: Overcommit and calloc() Date: Tue, 20 Jul 1999 13:28:21 -0400 Message-ID: <005101bed2d5$433a16e0$291c453f@kbyanc.alcnet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: Charles Randall > >I have another post on this list which begs the question: if memory given > >to us from sbrk() is already zeroed, why zero it again if we don't have > >too.... if we make calloc() smarter, we could save come clock cycles. > > Because the memory returned from malloc() might be from a previous > malloc()/free() and may be dirty. > > Charles Specifically, if there are no blocks on the heap that can be re-used by malloc(), it calls sbrk() to extend the process' address space. sbrk() always returns memory that the kernel has already gone through the effort of zero'ing...why do it again? I am thinking about making calloc() more intellegent like malloc(): if it re-uses a free()'ed memory block, then it has to bzero() it (exactly like it does now), if it has to sbrk() then it can skip the bzero() step and save some clock cycles. I'm expecting that in addition of gaining clock cycles from not zeroing the memory twice, the fact that calloc() won't have to touch all newly allocated pages would reduce the amount of work by the VM system and give another little performance boost. On recent thought though, I seem to recall having read in the 4.4BSD Daemon book that having the kernel zero memory is not the preferred practice, but present because when they tried to stop many progrems dies which assumed memory was initialized to zero. If I am remembering that correctly, then, the only real concern is that one day we may want to kernel to stop zeroing pages, in which case the extra logic in calloc() would be for nought. Really the jist of the changes I'm looking to make are to use the fact that the kernel is already zeroing pages to optimize the calloc() implementation. If this ever changes, then the optimization would go away. Kelly ~kbyanc@posi.net~ FreeBSD - The Power To Serve - http://www.freebsd.org/ Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 10:19:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 38BFD14EAB for ; Tue, 20 Jul 1999 10:19:43 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA05742; Tue, 20 Jul 1999 10:19:37 -0700 (PDT) (envelope-from dillon) Date: Tue, 20 Jul 1999 10:19:37 -0700 (PDT) From: Matthew Dillon Message-Id: <199907201719.KAA05742@apollo.backplane.com> To: Warner Losh Cc: "Leif Neland" , freebsd-hackers@FreeBSD.ORG Subject: Re: Sv: speed of file(1) References: <02a901bed22e$25164e60$0e00a8c0@neland.dk> <199907192045.NAA99619@apollo.backplane.com> <199907200942.DAA85004@harmony.village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Maybe the P60 is memory starved. Thrashing would cause this huge :factor of speed difference... : :Warner No, I tested it on my 1G box - there was a very noticeable delay running 'file' on a simple text file. Something in the file program or in the data description is causing the file program to eat cpu but I'm not really interested in spending hours tracking it down. If someone wants to work on the problem, I recommend editing the magic file to home in on the cause. I did a quick 'cut magic file in half' test and the time went from 0.09 seconds to 0.01 seconds, so I believe there is something in there that is causing the problem. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 10:31:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id B6D451537D for ; Tue, 20 Jul 1999 10:31:12 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id KAA50728 for freebsd-hackers@FreeBSD.ORG; Tue, 20 Jul 1999 10:29:09 -0700 (PDT) Date: Tue, 20 Jul 1999 10:29:09 -0700 (PDT) From: David Wolfskill Message-Id: <199907201729.KAA50728@pau-amma.whistle.com> Subject: RE: Overcommit and calloc() Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <005101bed2d5$433a16e0$291c453f@kbyanc.alcnet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: "Kelly Yancey" >Date: Tue, 20 Jul 1999 13:28:21 -0400 > On recent thought though, I seem to recall having read in the 4.4BSD >Daemon book that having the kernel zero memory is not the preferred >practice, but present because when they tried to stop many progrems dies >which assumed memory was initialized to zero. If I am remembering that >correctly, then, the only real concern is that one day we may want to kernel >to stop zeroing pages, in which case the extra logic in calloc() would be >for nought. I'd *think* you'd want to ensure that lack of initializing the data didn't become a way for unintended access to data that should not have been available to the process in question. (Ugh. Too many negatives in there.) Anyway, the process merely reminded me of the ability on a system I used 28+ years ago, where a FORTRAN program could open a file for writing, but read it first... and possibly find some "interesting" information left over from a previous program.... (No, that wasn't a UNIX system, let alone FreeBSD. :-}) Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 10:37:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 6E82615347 for ; Tue, 20 Jul 1999 10:37:18 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id SAA16612; Tue, 20 Jul 1999 18:36:08 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Tue, 20 Jul 1999 18:33:19 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <005101bed2d5$433a16e0$291c453f@kbyanc.alcnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 20 Jul 1999 18:33:17 +0000 To: "Kelly Yancey" From: Bob Bishop Subject: RE: Overcommit and calloc() Cc: , Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 1:28 pm -0400 20/7/99, Kelly Yancey wrote: >[...] > On recent thought though, I seem to recall having read in the 4.4BSD >Daemon book that having the kernel zero memory is not the preferred >practice, but present because when they tried to stop many progrems dies >which assumed memory was initialized to zero. Handing out unzeroed memory is a potential security hole. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 10:54:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id BB00D14C15 for ; Tue, 20 Jul 1999 10:54:30 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA06000; Tue, 20 Jul 1999 10:53:26 -0700 (PDT) (envelope-from dillon) Date: Tue, 20 Jul 1999 10:53:26 -0700 (PDT) From: Matthew Dillon Message-Id: <199907201753.KAA06000@apollo.backplane.com> To: "Kelly Yancey" Cc: , Subject: Re: RE: Overcommit and calloc() References: <005101bed2d5$433a16e0$291c453f@kbyanc.alcnet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think this would be a waste of time. As I have said, very few large allocations use calloc(). Nearly all small allocations come off the heap. The cost of adding the complexity to calloc to avoid zeroing the data is not going to be worth the minor (and unnoticeable) improvement in performance that you reap from it. Right now malloc/calloc add new blocks to the heap in chunks and while they may know that a page is zero on allocation, once the first small bit has been removed from the heap they have no idea that the remainder is still zero. Making them knowledgeable of that will simply make the critical path more costly and probably end up in reducing your overall performance. -Matt Matthew Dillon : : Specifically, if there are no blocks on the heap that can be re-used by :malloc(), it calls sbrk() to extend the process' address space. sbrk() :always returns memory that the kernel has already gone through the effort of :zero'ing...why do it again? I am thinking about making calloc() more :intellegent like malloc(): if it re-uses a free()'ed memory block, then it :has to bzero() it (exactly like it does now), if it has to sbrk() then it :can skip the bzero() step and save some clock cycles. I'm expecting that in :addition of gaining clock cycles from not zeroing the memory twice, the fact :that calloc() won't have to touch all newly allocated pages would reduce the :amount of work by the VM system and give another little performance boost. : : On recent thought though, I seem to recall having read in the 4.4BSD :Daemon book that having the kernel zero memory is not the preferred :practice, but present because when they tried to stop many progrems dies :which assumed memory was initialized to zero. If I am remembering that :correctly, then, the only real concern is that one day we may want to kernel :to stop zeroing pages, in which case the extra logic in calloc() would be :for nought. : Really the jist of the changes I'm looking to make are to use the fact :that the kernel is already zeroing pages to optimize the calloc() :implementation. If this ever changes, then the optimization would go away. : : Kelly : ~kbyanc@posi.net~ : FreeBSD - The Power To Serve - http://www.freebsd.org/ : Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 10:56:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id B0DA8153B0 for ; Tue, 20 Jul 1999 10:56:51 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA06018; Tue, 20 Jul 1999 10:54:46 -0700 (PDT) (envelope-from dillon) Date: Tue, 20 Jul 1999 10:54:46 -0700 (PDT) From: Matthew Dillon Message-Id: <199907201754.KAA06018@apollo.backplane.com> To: Bob Bishop Cc: "Kelly Yancey" , , Subject: Re: RE: Overcommit and calloc() References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi, : :At 1:28 pm -0400 20/7/99, Kelly Yancey wrote: :>[...] :> On recent thought though, I seem to recall having read in the 4.4BSD :>Daemon book that having the kernel zero memory is not the preferred :>practice, but present because when they tried to stop many progrems dies :>which assumed memory was initialized to zero. : :Handing out unzeroed memory is a potential security hole. : :-- :Bob Bishop (0118) 977 4017 international code +44 118 :rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK It should also be noted that unless your system is entirely cpu-bound, there is no cost to the kernel to zero memory because it pre-zero's pages in its idle loop. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 11:11:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from brockman.tinet.ie (brockman.tinet.ie [159.134.237.30]) by hub.freebsd.org (Postfix) with ESMTP id 9F4E61538A for ; Tue, 20 Jul 1999 11:11:04 -0700 (PDT) (envelope-from crypt0genic@tinet.ie) Received: from p252.as2.cork1.tinet.ie ([159.134.229.252] helo=tweak.home) by brockman.tinet.ie with esmtp (Exim 2.05 #23) id 116eLS-0002cw-00 for hackers@freebsd.org; Tue, 20 Jul 1999 19:10:26 +0100 Received: (from crypt0genic@localhost) by tweak.home (8.9.3/8.9.3) id TAA01186 for hackers@freebsd.org; Tue, 20 Jul 1999 19:07:46 GMT Date: Tue, 20 Jul 1999 19:07:45 +0000 From: crypt0genic To: hackers@freebsd.org Subject: Xircomm ethernet cards.... Message-ID: <19990720190745.A1172@ecad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a Xircomm 10/100 pcmcia ethernet card for my laptop and after seraching the mailing lists it is pretty obivious that it is'nt supported. Does and one know of any new developments on this? hacks? If not can some one recommend a good card for freebsd, it would have to be 10/100 mbit and work relatively well with windows aswell as freebsd. I could possibly get my Xircomm replaced. -Emil: -- Reverse engineering, the most phun and usually the most effective way to tackle a problem or learn something new. Public PGP key: http://www.ecad.org/crypt0genic_pgp_key Website: http://www.ecad.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 11:19:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by hub.freebsd.org (Postfix) with ESMTP id 678EB14CBB for ; Tue, 20 Jul 1999 11:19:52 -0700 (PDT) (envelope-from jwm@CSUA.Berkeley.EDU) Received: from soda.CSUA.Berkeley.EDU (localhost [127.0.0.1]) by soda.CSUA.Berkeley.EDU (8.8.8/) via ESMTP id LAA19587; Tue, 20 Jul 1999 11:18:29 -0700 (PDT) env-from (jwm@CSUA.Berkeley.EDU) Message-Id: <199907201818.LAA19587@soda.CSUA.Berkeley.EDU> To: Matthew Dillon Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: USFS (User Space File System) In-reply-to: Message from Matthew Dillon of "Tue, 20 Jul 1999 10:14:44 PDT." <199907201714.KAA05685@apollo.backplane.com> Date: Tue, 20 Jul 1999 11:18:29 -0700 From: John Milford Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > No, MFS runs in supervisor mode. That mfs process that you see hanging > there is just placemarking the VM space. > > -Matt > Well, I think there is a little more to it than that. I believe it does run in supervisor mode, but the mfs process is providing not just the VM space, but the process context as well. If I remeber the code correctly, MFS runs as a single process, and requests are queued (on mfsp->buf_queue) for this process and handled there. If the queuing were done a little bit differently, this could provide a mechanism for returning requests to user space. Something along the lines of a syscall that enters the kernel and waits for work as David mentioned before. So instead of having the mfs process handle the request in supervisor mode, the syscall would return, and the request could be handled in user mode. It is a little strange, because the syscall entry and return will be handling different requests, but I believe it would work. --John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 11:31: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 4D00A152F7 for ; Tue, 20 Jul 1999 11:30:55 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA06200; Tue, 20 Jul 1999 11:30:09 -0700 (PDT) (envelope-from dillon) Date: Tue, 20 Jul 1999 11:30:09 -0700 (PDT) From: Matthew Dillon Message-Id: <199907201830.LAA06200@apollo.backplane.com> To: John Milford Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: USFS (User Space File System) References: <199907201818.LAA19587@soda.CSUA.Berkeley.EDU> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Matthew Dillon wrote: : :> :> No, MFS runs in supervisor mode. That mfs process that you see hanging :> there is just placemarking the VM space. :> :> -Matt :> : : Well, I think there is a little more to it than that. I :believe it does run in supervisor mode, but the mfs process is :providing not just the VM space, but the process context as well. :If I remeber the code correctly, MFS runs as a single process, and :requests are queued (on mfsp->buf_queue) for this process and handled there. : : If the queuing were done a little bit differently, this could :provide a mechanism for returning requests to user space. Something :along the lines of a syscall that enters the kernel and waits for work :as David mentioned before. So instead of having the mfs process handle :the request in supervisor mode, the syscall would return, and the :request could be handled in user mode. It is a little strange, :because the syscall entry and return will be handling different :requests, but I believe it would work. : : : --John This seems like an unnecessary complication to me. It would be easier to simply make it a device that you can open(), read(), and write() as I first suggested. MFS is not a good template for any of this. MFS is very, very simple and the pieces that would make a user-level device driver work are considerably more complex because they require the ability to make information available to a user process that is usually available only to the kernel. MFS makes no progress to this end, because MFS runs (more or less permanently) in supervisor mode. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 11:44:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 326C515387 for ; Tue, 20 Jul 1999 11:44:07 -0700 (PDT) (envelope-from kbyanc@alcnet.com) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from kbyanc (ws-41.alcnet.com [63.69.28.41]) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with SMTP id OAA58563; Tue, 20 Jul 1999 14:59:13 -0400 (EDT) From: "Kelly Yancey" To: "Matthew Dillon" Cc: Subject: RE: RE: Overcommit and calloc() Date: Tue, 20 Jul 1999 14:55:40 -0400 Message-ID: <005b01bed2e1$7651cee0$291c453f@kbyanc.alcnet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal In-Reply-To: <199907201753.KAA06000@apollo.backplane.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Matthew Dillon [mailto:dillon@apollo.backplane.com] > Sent: Tuesday, July 20, 1999 1:53 PM > To: Kelly Yancey > Cc: crandall@matchlogic.com; freebsd-hackers@FreeBSD.ORG > Subject: Re: RE: Overcommit and calloc() > > > I think this would be a waste of time. As I have said, very few > large allocations use calloc(). Nearly all small allocations come > off the heap. The cost of adding the complexity to calloc to avoid > zeroing the data is not going to be worth the minor (and unnoticeable) > improvement in performance that you reap from it. Right now > malloc/calloc > add new blocks to the heap in chunks and while they may know > that a page > is zero on allocation, once the first small bit has been removed from > the heap they have no idea that the remainder is still zero. > Making them > knowledgeable of that will simply make the critical path more > costly and > probably end up in reducing your overall performance. > > -Matt > Matthew Dillon > > I don't dare claim to know as much as about the system as you do, how about this: I am sure that I can at least just find a spare bit in struct pgfree (/usr/src/lib/libc/stdlib/malloc.c) in which I can store a boolean flag indicating whether or not the run is already zeroed. Then all I add in complexity is setting the flag when a run is added to the list via map_pages/extend_pgdir, and a fairly small calloc() implementation which looks much like the existing calloc() but checking specifically for a run with the bit set. malloc()'s implementation doesn't have to change a bit since it doesn't care whether it's memory is zeroed or not, so the critical path isn't affected. calloc() will then use already zero'ed pages if they are available, otherwise just take what it can get and bzero() them itself. Since there will only ever be at most a single run of pre-zero'ed pages, I'll probably keep a separate pointer directly to that struct pgfree to optimize calloc() further (which would add to the critical path, so I may reconsider). I can't actually make patches, though, until I get home. As far as your other point, you imply that because pages are be pre-zeroed during the idle loop, we are currently no worse off then if they were never zeroed at all. Which is true. But is that not to say that we wouldn't be better off by taking advantage of the work we have already done? Besides, how many of us are running things like rc5 or seti@home which prevent the idle loop from doing any work? Os it not possible that we run out of zeroed pages and then when a process calls sbrk(), the VM system has to zero the memory to give to us (which may be zeroed again by calloc())...in which case a call to calloc() results in zeroing the memory twice *while we wait*. Admittingly, calloc() isn't called nearly as often as malloc(). But malloc() is already pretty darned optimized thanks to phk, I'm just trying to extend his optimizations to include cases where calloc() could further benefit. Don't worry I'll post benchmarks before and after, with and without rc5 running in the background, along with the patches. I really appreciate all the feedback though, Kelly ~kbyanc@posi.net~ FreeBSD - The Power To Serve - http://www.freebsd.org/ Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 11:50:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (Postfix) with ESMTP id BBC7014DF6 for ; Tue, 20 Jul 1999 11:50:39 -0700 (PDT) (envelope-from kyle@stdio.com) Received: from localhost (kyle@localhost) by heathers.stdio.com (8.8.8/8.8.8) with SMTP id OAA05916; Tue, 20 Jul 1999 14:48:29 -0400 (EDT) (envelope-from kyle@heathers.stdio.com) Date: Tue, 20 Jul 1999 14:48:28 -0400 (EDT) From: Kyle McPeek To: crypt0genic Cc: hackers@FreeBSD.ORG Subject: Re: Xircomm ethernet cards.... In-Reply-To: <19990720190745.A1172@ecad.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 Hi, The Xircom CreditCard Ethernet 10/100 seems to work in -Stable only. I had to burn a 3.2-RELEASE CD to install from, then put a 3.2-STABLE kernel on my laptop from another machine using the floppy. If you can make/get a 3.2-STABLE cd then that should work just fine, it is for me anyway. kyle. On Tue, 20 Jul 1999, crypt0genic wrote: > > I have a Xircomm 10/100 pcmcia ethernet card for my laptop and after seraching the mailing lists it is pretty obivious that it is'nt supported. Does and one know of any new developments on this? hacks? > > If not can some one recommend a good card for freebsd, it would have to be 10/100 mbit and work relatively well with windows aswell as freebsd. I could possibly get my Xircomm replaced. > > -Emil: > > -- > Reverse engineering, the most phun and usually the most effective way to tackle a problem or learn something new. > Public PGP key: http://www.ecad.org/crypt0genic_pgp_key > Website: http://www.ecad.org/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 11:51:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id CD687153CE for ; Tue, 20 Jul 1999 11:50:49 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id LAA29421; Tue, 20 Jul 1999 11:49:42 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA69126; Tue, 20 Jul 1999 11:49:42 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Tue, 20 Jul 1999 11:49:42 -0700 (PDT) Message-Id: <199907201849.LAA69126@vashon.polstra.com> To: obonilla@fisicc-ufm.edu Subject: Re: PAM & LDAP in FreeBSD In-Reply-To: <19990720082825.B793@fisicc-ufm.edu> References: <199907192111.OAA01326@dingo.cdrom.com> <3793ABE0.15090E38@softweyr.com> <19990719180026.A830@fisicc-ufm.edu> <19990720225929.A9510@patho.gen.nz> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990720082825.B793@fisicc-ufm.edu>, Oscar Bonilla wrote: > Couldn't we do this with /etc/auth.conf? The plan when PAM was brought in was to eliminate auth.conf. I don't think we should be looking for new uses for it. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 11:59:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 55ECB14DF6 for ; Tue, 20 Jul 1999 11:59:12 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id OAA33489 for ; Tue, 20 Jul 1999 14:59:05 -0400 (EDT) Message-Id: <199907201859.OAA33489@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: wcs stuffs... Date: Tue, 20 Jul 1999 14:59:00 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, I am still working on it, don't despair ;) This is the case of project creep... I am now working on the 'isw*()' functions, and I have a couple of questions regarding locale support in FreeBSD. Namely, how the heck do I get access to the database? I see that the LC_* databases have all the information I want in them, but I have 0 clue on how to cleanly access the data. any pointers (esp pointers to man pages) would be greatly appreciated. Thanks :) -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 12: 4:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mom.hooked.net (mom.hooked.net [206.80.6.10]) by hub.freebsd.org (Postfix) with ESMTP id 47C1C1531A for ; Tue, 20 Jul 1999 12:04:40 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from fish.hooked.net (garbanzo@fish.hooked.net [206.80.6.48]) by mom.hooked.net (8.8.6/8.8.5) with SMTP id LAA02209; Tue, 20 Jul 1999 11:02:15 -0700 (PDT) Date: Tue, 20 Jul 1999 11:02:14 -0700 (PDT) From: Alex Zepeda To: Alexander Voropay Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: glibc In-Reply-To: <01ca01bed2b6$0b235ba0$cd0d11ac@host205.spb.in.rosprin.ru> 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, 20 Jul 1999, Alexander Voropay wrote: > glibc has better POSIX locale and I18N / L10N support : > - localedef(1) and locale(1) utilities > - nl_langinfo(3) XPG-4 function > - gettext built-in into glibc Again this is just a handful of functions, that IMO are best not put into libc. Take the dl*() functions. They're not in fbsd's libc, but they're ing glibc. Doesn't mean they're not easily available. Hell gettext *is* a port. Not every app is going to need to be internationalized, not every app *should* be penalized. If you think it'd be easier to port the whole glibc than to port a hand ful of functions, nobody is stopping you :) - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 12:10:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 2BC2E15387 for ; Tue, 20 Jul 1999 12:10:23 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA05171 for FreeBSD-hackers@freebsd.org; Tue, 20 Jul 1999 21:04:32 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id VAA03203 for FreeBSD-hackers@freebsd.org; Tue, 20 Jul 1999 21:04:35 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199907201904.VAA03203@yedi.iaf.nl> Subject: any docs on how to use bus_dma_tag_create e.a. ? To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) Date: Tue, 20 Jul 1999 21:04:35 +0200 (CEST) X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm currently trying to hack a driver together for a PCI card that uses shared memory to communicate to the host. If I'm not completely offtrack I need to use (under newbus/-current) bus_dma_tag_create, bus_dma_alloc etc to get access to the cards shared memory. I'm looking for more detailed info on the parameters these functions take. Or (I'm dreaming I guess....) a sort of architectural overview of how newbus is put together. At the moment I have: /* map shared memory of FireFly */ error = bus_dma_tag_create(NULL /*parent*/, 0 /*alignm*/, 0 /*boundary*/, BUS_SPACE_MAXADDR_32BIT /*lowaddr*/, BUS_SPACE_MAXADDR /*hiaddr*/, NULL, /*filter*/, NULL, /*filterarg*/, MAXBSIZE /*maxsize*/, 1 /*XXX*/ /*nsegments*/, 4096 /*XXX*/ /*maxsegsz*/, BUS_DMA_ALLOCNOW /*XXX*/ /*flags*/, &dma_tag); but I sincerely doubt at least part of the values.. TIA, -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 12:12:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 121FB1531A for ; Tue, 20 Jul 1999 12:12:08 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id MAA29555; Tue, 20 Jul 1999 12:12:02 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id MAA69231; Tue, 20 Jul 1999 12:12:02 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Tue, 20 Jul 1999 12:12:02 -0700 (PDT) Message-Id: <199907201912.MAA69231@vashon.polstra.com> To: rbezuide@oskar.nanoteq.co.za Subject: Re: if_dl.h in stable causes sendmail segmentation In-Reply-To: <199907201542.RAA02634@oskar.nanoteq.co.za> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199907201542.RAA02634@oskar.nanoteq.co.za>, Reinier Bezuidenhout wrote: > I have the following situation... ... [various userland SEGVs traced down to a change in if_dl.h] Just a guess: it sounds like the kind of thing that would happen if you updated your kernel without also rebuilding userland. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 12:22:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 75E7014F24 for ; Tue, 20 Jul 1999 12:22:08 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id UAA18557; Tue, 20 Jul 1999 20:21:01 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Tue, 20 Jul 1999 20:15:18 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199907201754.KAA06018@apollo.backplane.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 20 Jul 1999 20:15:17 +0000 To: Matthew Dillon From: Bob Bishop Subject: Re: RE: Overcommit and calloc() Cc: "Kelly Yancey" , , Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi again, At 10:54 am -0700 20/7/99, Matthew Dillon wrote: [...] > It should also be noted that unless your system is entirely cpu-bound, > there is no cost to the kernel to zero memory because it pre-zero's > pages in its idle loop. Thanks to distributed.net, SETI. et al, idle cycles are fast going out of fashion. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 12:53:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by hub.freebsd.org (Postfix) with ESMTP id D060B1519C for ; Tue, 20 Jul 1999 12:53:18 -0700 (PDT) (envelope-from jwm@CSUA.Berkeley.EDU) Received: from soda.CSUA.Berkeley.EDU (localhost [127.0.0.1]) by soda.CSUA.Berkeley.EDU (8.8.8/) via ESMTP id MAA14190; Tue, 20 Jul 1999 12:52:50 -0700 (PDT) env-from (jwm@CSUA.Berkeley.EDU) Message-Id: <199907201952.MAA14190@soda.CSUA.Berkeley.EDU> To: Matthew Dillon Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: USFS (User Space File System) In-reply-to: Message from Matthew Dillon of "Tue, 20 Jul 1999 11:30:09 PDT." <199907201830.LAA06200@apollo.backplane.com> Date: Tue, 20 Jul 1999 12:52:50 -0700 From: John Milford Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > This seems like an unnecessary complication to me. It would be > easier to simply make it a device that you can open(), read(), and > write() as I first suggested. > > MFS is not a good template for any of this. MFS is very, very simple > and the pieces that would make a user-level device driver work are > considerably more complex because they require the ability to make > information available to a user process that is usually available only > to the kernel. MFS makes no progress to this end, because MFS runs > (more or less permanently) in supervisor mode. > > -Matt I'll defer to you on this as I never got far enough into this project to have discovered all the complications. --John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 13: 5:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mom.hooked.net (mom.hooked.net [206.80.6.10]) by hub.freebsd.org (Postfix) with ESMTP id 5EB8A1519C for ; Tue, 20 Jul 1999 13:05:16 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from fish.hooked.net (garbanzo@fish.hooked.net [206.80.6.48]) by mom.hooked.net (8.8.6/8.8.5) with SMTP id LAA04118; Tue, 20 Jul 1999 11:05:58 -0700 (PDT) Date: Tue, 20 Jul 1999 11:05:58 -0700 (PDT) From: Alex Zepeda To: eT Cc: Hackers FreeBSD Subject: Re: KDE on FreeBSD (missing symbols) In-Reply-To: <37948074.E413DA52@post.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Jul 1999, eT wrote: > Greets .. I decided to compile KDE-1.1.1 for my 4.0-CURRENT. > After compiling all (kde-1.1 and qt-1.44) I get the following errors when > startx'ing: > > ld-elf.so complains about not finding these symbols: > __ti6QFrame > __ti7QObject > __ti7Qblahblahblah > > I pressume there is something wrong with the way I compiled qt-1.44? You've gotta choose between the lesser of two evils. First, Qt 1.44 is *not* recommended you should use Qt 1.42. Second of all, TT's support of FreeBSD sucks, the FreeBSD port of Qt sucks. TT has enabled -fno-rtti which causes problems for applications (such as KDE apps) that aren't compiled with -fno-rtti. The FreeBSD port still suffers from this, as well as depending on Mesa(?!). With whatever Qt version you're using go into the appropiate configs/freebsd-... file and remove -fno-rtti. - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 13:11:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 0230A151AD for ; Tue, 20 Jul 1999 13:11:28 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id NAA07710; Tue, 20 Jul 1999 13:58:54 -0600 (MDT) Date: Tue, 20 Jul 1999 13:58:54 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199907201958.NAA07710@narnia.plutotech.com> To: Wilko Bulte Cc: hackers@FreeBSD.org Subject: Re: any docs on how to use bus_dma_tag_create e.a. ? X-Newsgroups: pluto.freebsd.hackers In-Reply-To: <199907201904.VAA03203@yedi.iaf.nl> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199907201904.VAA03203@yedi.iaf.nl> you wrote: > I'm currently trying to hack a driver together for a PCI card that uses > shared memory to communicate to the host. > > If I'm not completely offtrack I need to use (under newbus/-current) > bus_dma_tag_create, bus_dma_alloc etc to get access to the cards shared > memory. bus_dma related stuff is only required if the device has a DMA engine you wish to use. To access the shared memory on the card (e.g. map it into the kernel's virtual address space), you will need to use the resource manager and bus space. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 13:39:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 9B77B15074 for ; Tue, 20 Jul 1999 13:39:44 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA09146; Tue, 20 Jul 1999 22:37:51 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA00801; Tue, 20 Jul 1999 22:37:47 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199907202037.WAA00801@yedi.iaf.nl> Subject: Re: any docs on how to use bus_dma_tag_create e.a. ? In-Reply-To: <199907201958.NAA07710@narnia.plutotech.com> from "Justin T. Gibbs" at "Jul 20, 1999 1:58:54 pm" To: gibbs@narnia.plutotech.com (Justin T. Gibbs) Date: Tue, 20 Jul 1999 22:37:47 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Justin T. Gibbs wrote ... > In article <199907201904.VAA03203@yedi.iaf.nl> you wrote: > > I'm currently trying to hack a driver together for a PCI card that uses > > shared memory to communicate to the host. > > > > If I'm not completely offtrack I need to use (under newbus/-current) > > bus_dma_tag_create, bus_dma_alloc etc to get access to the cards shared > > memory. > > bus_dma related stuff is only required if the device has a DMA engine > you wish to use. To access the shared memory on the card (e.g. map Eh, sorry, I was confused. It has *both* shared memory and a DMA engine. > it into the kernel's virtual address space), you will need to use > the resource manager and bus space. Do you by chance have an example (maybe in -current somewhere) of the shared memory stuff? I found some DMA stuff in ahc_pci.c: /* Allocate a dmatag for our SCB DMA maps */ /* XXX Should be a child of the PCI bus dma tag */ error = bus_dma_tag_create(/*parent*/NULL, /*alignment*/0, /*boundary*/0, /*lowaddr*/BUS_SPACE_MAXADDR_32BIT, /*highaddr*/BUS_SPACE_MAXADDR, /*filter*/NULL, /*filterarg*/NULL, /*maxsize*/MAXBSIZE, /*nsegments*/AHC_NSEG, /*maxsegsz*/AHC_MAXTRANSFER_SIZE, /*flags*/BUS_DMA_ALLOCNO but I admit it is not too clear (yet..) what all the parameters do. Most (?) drivers seem to use the older framework (can I distinguish those by COMPAT_PCI_DRIVER() ?). Thanks, Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 13:44:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from voyager.fisicc-ufm.edu (pm2a-s37.guate.net [200.12.57.176]) by hub.freebsd.org (Postfix) with ESMTP id E053415422 for ; Tue, 20 Jul 1999 13:44:35 -0700 (PDT) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id OAA00809; Tue, 20 Jul 1999 14:42:18 -0600 (CST) (envelope-from obonilla) Date: Tue, 20 Jul 1999 14:42:17 -0600 From: Oscar Bonilla To: Kris Kennaway Cc: "David E. Cross" , Oscar Bonilla , Joe Abley , Wes Peters , Mike Smith , Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD Message-ID: <19990720144217.A426@fisicc-ufm.edu> References: <199907201520.LAA29350@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Kris Kennaway on Wed, Jul 21, 1999 at 01:46:56AM +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It looks like we've got some good concurrent projects happening at the > moment - markm and co working on PAM, the nsswitch.conf project you're > talking about, and the stuff I'm working on with modularizing crypt() and > supporting per-login class password hashes (I've rewritten the library > since I last posted about it and expect to have my code cleaned up by > tomorrow night for another snapshot). > > The thing to make sure is that we don't tread on each other's toes, and > basically that we look for the big picture and how all these projects fit > together. > Ok, this is my understanding of the thing: There are two parts to the problem, first we need a way to tell the system where to get its information from (call them databases, tables or whatever). This should be done a la solaris, with /etc/nsswitch.conf telling if this is to be fetched from "files, ldap, nis, dns, etc". We need to recode all the programs that obtain this info directly from files to get it from a library (this would be nsd). And then code the library itself to get the info from /etc/nsswitch.conf Second, we need a way to authenticate the user... this is what PAM does. What would need to be done is change the pam modules to make them nsd aware (i.e. where should I get the passwd from?) or make them /etc/auth.conf aware? this is the confusing part... where does crypt fit into this? crypt would get what from /etc/login.conf? regards, -Oscar -- For PGP Public Key: finger obonilla@fisicc-ufm.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 13:50:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from voyager.fisicc-ufm.edu (pm2a-s37.guate.net [200.12.57.176]) by hub.freebsd.org (Postfix) with ESMTP id 41377154A4 for ; Tue, 20 Jul 1999 13:50:24 -0700 (PDT) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id OAA01004; Tue, 20 Jul 1999 14:49:19 -0600 (CST) (envelope-from obonilla) Date: Tue, 20 Jul 1999 14:49:19 -0600 From: Oscar Bonilla To: John Polstra Cc: obonilla@fisicc-ufm.edu, hackers@freebsd.org Subject: Re: PAM & LDAP in FreeBSD Message-ID: <19990720144919.B426@fisicc-ufm.edu> References: <199907192111.OAA01326@dingo.cdrom.com> <3793ABE0.15090E38@softweyr.com> <19990719180026.A830@fisicc-ufm.edu> <19990720225929.A9510@patho.gen.nz> <19990720082825.B793@fisicc-ufm.edu> <199907201849.LAA69126@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199907201849.LAA69126@vashon.polstra.com>; from John Polstra on Tue, Jul 20, 1999 at 11:49:42AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 20, 1999 at 11:49:42AM -0700, John Polstra wrote: > In article <19990720082825.B793@fisicc-ufm.edu>, > Oscar Bonilla wrote: > > > Couldn't we do this with /etc/auth.conf? > > The plan when PAM was brought in was to eliminate auth.conf. I don't > think we should be looking for new uses for it. > ok, so this clarifies a lot of things... let's get rid of /etc/auth.conf and go with /etc/pam.conf for the authentication and /etc/nsswitch.conf for the info on where to obtain the databases from. Regards, -Oscar -- For PGP Public Key: finger obonilla@fisicc-ufm.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 14: 9:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from narcissus.net (narcissus.net [209.73.230.146]) by hub.freebsd.org (Postfix) with ESMTP id 656AB14C3D for ; Tue, 20 Jul 1999 14:09:32 -0700 (PDT) (envelope-from ben@narcissus.net) Received: by narcissus.net (Postfix, from userid 1000) id 3C93520C; Tue, 20 Jul 1999 16:59:37 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by narcissus.net (Postfix) with SMTP id 2E231F7 for ; Tue, 20 Jul 1999 16:59:37 -0400 (EDT) Date: Tue, 20 Jul 1999 16:59:37 -0400 (EDT) From: Snob Art Genre To: hackers@freebsd.org Subject: amandad zombies (fwd) 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 there, I've been beating my head against a mysterious problem for some time now, and I'm hoping that you folks can help me out. When I run amanda, seven out of my 16 hosts don't respond. Of these, some are Solaris and some are FreeBSD 3.1-RELEASE, but it's the FreeBSD ones I'm concerned with at the moment. I'm using Amanda 2.4.1. (Note that the symptomology on the Solaris machines is different, which is why I'm posting this to -hackers.) >From my experiments with amcheck and snoop, it looks like the amandad on the affected clients is doing OK for one connection, but then the amandad process sticks around as a zombie and apparently inetd won't spawn a new one until the old one dies. The only way to get rid of the zombie that I've been able to find (besides rebooting of course) is to kill inetd. (on my backup host) bash-2.02$ amcheck -c general (on a malfunctioning client) cache2# inetd -d ADD : amanda proto=udp accept=0 max=1 user=backup group=(null) class=daemon builtin=0x0 server=/usr/local/amanda/libexec/amandad inetd: enabling amanda, fd 4 inetd: registered /usr/local/amanda/libexec/amandad on 4 inetd: someone wants amanda inetd: inetd: disabling amanda, fd 4+ closing from 4 inetd: 6692 execl /usr/local/amanda/libexec/amandad Looks fine. But that's with a freshly started inetd -- the second time I run amcheck, I get no output from inetd. Now let's look at the truss output of inetd while I do an amcheck. This is with a fresh inetd. cache2# truss -p `cat /var/run/inetd.pid` syscall (null)() returns 1 (0x1) syscall sigprocmask(0x1,0x82001) returns 0 (0x0) syscall gettimeofday(0x80580ac,0x0) returns 0 (0x0) syscall fork() returns 6717 (0x1a3d) syscall sigprocmask(0x3,0x0) returns 532481 (0x82001) syscall sigprocmask(0x1,0x82001) returns 0 (0x0) SIGNAL 20 SIGNAL 20 SIGNAL 20 syscall sigsuspend(0x0) errno 4 'Interrupted system call' syscall write(5,0xefbfda3b,1) returns 1 (0x1) syscall sigreturn(0xefbfda64) errno 4 'Interrupted system call' And here it stays ... while I do another amcheck, even. It looks like SIGCHLD is being delivered, but I don't see any wait-type syscalls. Any thoughts, anyone? -- Ben UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 14:18:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 151FE153D0 for ; Tue, 20 Jul 1999 14:18:12 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id RAA36397; Tue, 20 Jul 1999 17:15:52 -0400 (EDT) Message-Id: <199907202115.RAA36397@cs.rpi.edu> To: Snob Art Genre Cc: hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: amandad zombies (fwd) In-Reply-To: Message from Snob Art Genre of "Tue, 20 Jul 1999 16:59:37 EDT." Date: Tue, 20 Jul 1999 17:15:46 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We had a similiar problem here. We had meant to submit-pr it but forgot. In our case it was because inetd had only the amanda line in it (inetd was not responsible for any other services. Our guess was that it is an off by one error in inted somewhere, but we never traced it down further. Our work-arround was to enable a second service. Let me know if this was your problem. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 14:20:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 258E214FB2 for ; Tue, 20 Jul 1999 14:20:48 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id RAA36480 for ; Tue, 20 Jul 1999 17:20:47 -0400 (EDT) Message-Id: <199907202120.RAA36480@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: linking question... Date: Tue, 20 Jul 1999 17:20:41 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a program (part of CDE)... we will call it 'foo', "foo" has library dependancies: libtt.so, libX11.so, libXt.so, libXext.so, and libwcs.so(this last one is mine). libtt.so depends on iswalpha() and iswspace() (which are defined in libwcs.so) If I link with all of those I get an error that iswspace and iswalpha are undefined, yet: nm /usr/local/lib/libwcs.so | grep isw returns: > 00001358 T iswalpha > 000013b0 T iswprint > 00001384 T iswspace And if I change the '-lwcs' line to '/usr/local/lib/libwcs.a' it links fine. Ideas? -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 14:21:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id B1377153F0 for ; Tue, 20 Jul 1999 14:20:47 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40325>; Wed, 21 Jul 1999 07:02:06 +1000 Date: Wed, 21 Jul 1999 07:20:23 +1000 From: Peter Jeremy Subject: Re: freebsd-hackers-digest V4 #553 In-reply-to: To: hackers@FreeBSD.ORG Cc: gurney_j@efn.org Message-Id: <99Jul21.070206est.40325@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John-Mark Gurney wrote: >and even then, I don't believe in filling sockaddr_in w/ bzero, I >believe in using getsockaddr on it so that you actually get all the >fields filled out properly... % man getsockaddr No manual entry for getsockaddr % The only getsockaddr() I can find in the system is in /sys/kern/uipc_syscalls.c, which may be difficult for userland code to access :-). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 14:26:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 9717815435 for ; Tue, 20 Jul 1999 14:26:50 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id RAA72357; Tue, 20 Jul 1999 17:25:04 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Tue, 20 Jul 1999 17:25:04 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Peter Jeremy Cc: hackers@FreeBSD.org, gurney_j@efn.org Subject: Re: freebsd-hackers-digest V4 #553 In-Reply-To: <99Jul21.070206est.40325@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Jul 1999, Peter Jeremy wrote: > John-Mark Gurney wrote: > >and even then, I don't believe in filling sockaddr_in w/ bzero, I > >believe in using getsockaddr on it so that you actually get all the > >fields filled out properly... > > % man getsockaddr > No manual entry for getsockaddr > % > > The only getsockaddr() I can find in the system is in > /sys/kern/uipc_syscalls.c, which may be difficult for userland code to > access :-). I think he meant getsockname(). > > Peter > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ 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 Tue Jul 20 14:27:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from narcissus.net (narcissus.net [209.73.230.146]) by hub.freebsd.org (Postfix) with ESMTP id 8064815487 for ; Tue, 20 Jul 1999 14:27:10 -0700 (PDT) (envelope-from ben@narcissus.net) Received: by narcissus.net (Postfix, from userid 1000) id A756F21C; Tue, 20 Jul 1999 17:17:26 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by narcissus.net (Postfix) with SMTP id 9A11A210; Tue, 20 Jul 1999 17:17:26 -0400 (EDT) Date: Tue, 20 Jul 1999 17:17:26 -0400 (EDT) From: Snob Art Genre To: "David E. Cross" Cc: hackers@FreeBSD.ORG Subject: Re: amandad zombies (fwd) In-Reply-To: <199907202115.RAA36397@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Jul 1999, David E. Cross wrote: > Let me know if this was your problem. It was. Many, many thanks. I will probably send-pr this, do you have anything to add to what I posted before I do so? -- Ben "The world is conspiring in your favor." -- de la Vega To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 14:28:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 46E34153E6 for ; Tue, 20 Jul 1999 14:28:18 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id RAA36623; Tue, 20 Jul 1999 17:28:15 -0400 (EDT) Message-Id: <199907202128.RAA36623@cs.rpi.edu> To: Snob Art Genre Cc: "David E. Cross" , hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: amandad zombies (fwd) In-Reply-To: Message from Snob Art Genre of "Tue, 20 Jul 1999 17:17:26 EDT." Date: Tue, 20 Jul 1999 17:28:10 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nope, that is all that we had time to track down. We were fighting NFS panics arround the same time, stuff got lost in the shuffle :) -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 14:32: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from metriclient-2.uoregon.edu (metriclient-2.uoregon.edu [128.223.172.2]) by hub.freebsd.org (Postfix) with ESMTP id BBCF0153DA; Tue, 20 Jul 1999 14:31:52 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by metriclient-2.uoregon.edu (8.9.1/8.8.7) id OAA04868; Tue, 20 Jul 1999 14:30:08 -0700 (PDT) Message-ID: <19990720143008.26953@hydrogen.fircrest.net> Date: Tue, 20 Jul 1999 14:30:08 -0700 From: John-Mark Gurney To: "Brian F. Feldman" Cc: Peter Jeremy , hackers@FreeBSD.org Subject: Re: freebsd-hackers-digest V4 #553 References: <99Jul21.070206est.40325@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Brian F. Feldman on Tue, Jul 20, 1999 at 05:25:04PM -0400 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian F. Feldman scribbled this message on Jul 20: > On Wed, 21 Jul 1999, Peter Jeremy wrote: > > > John-Mark Gurney wrote: > > >and even then, I don't believe in filling sockaddr_in w/ bzero, I > > >believe in using getsockaddr on it so that you actually get all the > > >fields filled out properly... > > > > % man getsockaddr > > No manual entry for getsockaddr > > % > > > > The only getsockaddr() I can find in the system is in > > /sys/kern/uipc_syscalls.c, which may be difficult for userland code to > > access :-). > > I think he meant getsockname(). yes, I did mean getsockname... -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 14:40:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 8F35F14C3D for ; Tue, 20 Jul 1999 14:40:02 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA07272; Tue, 20 Jul 1999 14:38:06 -0700 (PDT) (envelope-from dillon) Date: Tue, 20 Jul 1999 14:38:06 -0700 (PDT) From: Matthew Dillon Message-Id: <199907202138.OAA07272@apollo.backplane.com> To: Bob Bishop Cc: "Kelly Yancey" , , Subject: Re: RE: Overcommit and calloc() References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi again, : :At 10:54 am -0700 20/7/99, Matthew Dillon wrote: :[...] :> It should also be noted that unless your system is entirely cpu-bound, :> there is no cost to the kernel to zero memory because it pre-zero's :> pages in its idle loop. : :Thanks to distributed.net, SETI. et al, idle cycles are fast going out of :fashion. : :-- :Bob Bishop (0118) 977 4017 international code +44 118 The overhead of running seti - the OS allowing the mintick interval to elapse when it gives seti cpu, that is - is going to be several orders of magnitude greater then any increase in performance that you get from trying to optimize calloc(). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 14:40:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 167E2153B5 for ; Tue, 20 Jul 1999 14:39:56 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id WAA75820; Tue, 20 Jul 1999 22:40:15 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 20 Jul 1999 22:40:15 +0100 (BST) From: Doug Rabson To: Alex Zepeda Cc: eT , Hackers FreeBSD Subject: Re: KDE on FreeBSD (missing symbols) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Jul 1999, Alex Zepeda wrote: > On Tue, 20 Jul 1999, eT wrote: > > > Greets .. I decided to compile KDE-1.1.1 for my 4.0-CURRENT. > > After compiling all (kde-1.1 and qt-1.44) I get the following errors when > > startx'ing: > > > > ld-elf.so complains about not finding these symbols: > > __ti6QFrame > > __ti7QObject > > __ti7Qblahblahblah > > > > I pressume there is something wrong with the way I compiled qt-1.44? > > You've gotta choose between the lesser of two evils. First, Qt 1.44 is > *not* recommended you should use Qt 1.42. Second of all, TT's support of > FreeBSD sucks, the FreeBSD port of Qt sucks. TT has enabled -fno-rtti > which causes problems for applications (such as KDE apps) that aren't > compiled with -fno-rtti. The FreeBSD port still suffers from this, as > well as depending on Mesa(?!). > > With whatever Qt version you're using go into the appropiate > configs/freebsd-... file and remove -fno-rtti. Who maintains the FreeBSD qt port? Perhaps you should fix the problems in the port and submit them as patches to the maintainer (and TT). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 14:41:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 408C714CF8 for ; Tue, 20 Jul 1999 14:41:03 -0700 (PDT) (envelope-from rminnich@acl.lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id PAA60870; Tue, 20 Jul 1999 15:40:52 -0600 (MDT) Date: Tue, 20 Jul 1999 15:40:52 -0600 From: "Ronald G. Minnich" To: John Milford Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: USFS (User Space File System) In-Reply-To: <199907200536.WAA25700@soda.CSUA.Berkeley.EDU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, John Milford wrote: > Unless I am misunderstanding you, mfs does what you are > describing. I'm pretty sure you're misunderstanding him. MFS is not even close. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 15: 1:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 3DAE314BE9 for ; Tue, 20 Jul 1999 15:01:20 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA07726; Tue, 20 Jul 1999 15:01:18 -0700 (PDT) (envelope-from dillon) Date: Tue, 20 Jul 1999 15:01:18 -0700 (PDT) From: Matthew Dillon Message-Id: <199907202201.PAA07726@apollo.backplane.com> To: "Ronald G. Minnich" Cc: John Milford , "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: USFS (User Space File System) References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Mon, 19 Jul 1999, John Milford wrote: : :> Unless I am misunderstanding you, mfs does what you are :> describing. : :I'm pretty sure you're misunderstanding him. MFS is not even close. : :ron You know, none of us are being clear :-) The basic problem is that MFS is not a filesystem device. What you say? It looks like a filesystem device to you! Well, no. MFS is actually a *block* device that UFS runs on top of. When you create an MFS filesystem you are actually creating a UFS filesystem and running all the UFS filesystem device code, except the backing store is being implemented by MFS as a dummy block device. MFS simply copies the data to and from the VM space of the mfs process. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 15:13:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 99C9C14FED for ; Tue, 20 Jul 1999 15:13:12 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id PAA00570; Tue, 20 Jul 1999 15:11:16 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id PAA69699; Tue, 20 Jul 1999 15:11:15 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990720144919.B426@fisicc-ufm.edu> Date: Tue, 20 Jul 1999 15:11:15 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Oscar Bonilla Subject: Re: PAM & LDAP in FreeBSD Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oscar Bonilla wrote: > > ok, so this clarifies a lot of things... let's get rid of /etc/auth.conf > and go with /etc/pam.conf for the authentication and /etc/nsswitch.conf > for the info on where to obtain the databases from. That seems reasonable to me. PAM actually is designed to serve four separate but related functions. We're only using the authentication function currently. For an overview of PAM, see PAM(8) in the manual pages. There is also a spec in "src/contrib/libpam/doc/specs/rfc86.0.txt". John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 15:13:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 481C2153FF for ; Tue, 20 Jul 1999 15:13:42 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40331>; Wed, 21 Jul 1999 07:54:53 +1000 Date: Wed, 21 Jul 1999 08:13:10 +1000 From: Peter Jeremy Subject: Re: speed of file(1) In-reply-to: To: hackers@FreeBSD.ORG Cc: leifn@neland.dk Message-Id: <99Jul21.075453est.40331@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Leif Neland" wrote: >My 60MHz Pentium, FreeBSD > >time file /usr/home/leif/vnc-3.3.2r >/usr/home/leif/vnc-3.3.2r3_unixsrc.tgz: gzip compressed data, deflated, >original filename, last modified: Thu Jan 21 19:23:21 1999 > >real 0m1.237s >user 0m0.758s >sys 0m0.394s I can't believe these figures. Matthew Dillon wrote: > Someone would have to compare file sources or profile it to figure out > what is causing the slowness. I can't reproduce the complaint using a 64MB PII-266 running -CURRENT - there's no evidence of lack of speed, and profiling file(1) doesn't show any anomolies. It is somewhat slower on my 8MB 386, but not unreasonably so: pc0640% time file src/Z/dhcp-2.0b1pl26.tar.gz src/Z/dhcp-2.0b1pl26.tar.gz: gzip compressed data, deflated, last modified: Thu Jan 1 10:00:00 1970, os: Unix file src/Z/dhcp-2.0b1pl26.tar.gz 1.96s user 0.83s system 98% cpu 2.823 total pc0640% Note that this is somewhat more than twice the time Leif claimed for his P-60 - and a P-60 should be more than twice the speed of a 386SX-25. Unfortunately, I can't profile it on my 386: It's running 2.x and I deleted the profiling libraries due to lack of space. It will happily run the profiled ELF file(1), but doesn't generate any timing data. Looking at ktrace with MALLOC_OPTIONS=U, it does do a lot of realloc()ing (once for every 20 active lines in .../magic) and sbrk()s to a maximum size of ~390KB - not really significant. All I can think of is that Leif has a problem with his P-60 system. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 15:38:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wenet.net (spain-38.ppp.hooked.net [206.169.228.38]) by hub.freebsd.org (Postfix) with ESMTP id 27592153DC for ; Tue, 20 Jul 1999 15:38:12 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by wenet.net (8.9.3/8.9.1) with ESMTP id PAA71826; Tue, 20 Jul 1999 15:37:27 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Tue, 20 Jul 1999 15:37:26 -0700 (PDT) From: Alex Zepeda To: Doug Rabson Cc: eT , Hackers FreeBSD Subject: Re: KDE on FreeBSD (missing symbols) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Jul 1999, Doug Rabson wrote: > > You've gotta choose between the lesser of two evils. First, Qt 1.44 is > > *not* recommended you should use Qt 1.42. Second of all, TT's support of > > FreeBSD sucks, the FreeBSD port of Qt sucks. TT has enabled -fno-rtti > > which causes problems for applications (such as KDE apps) that aren't > > compiled with -fno-rtti. The FreeBSD port still suffers from this, as > > well as depending on Mesa(?!). > > > > With whatever Qt version you're using go into the appropiate > > configs/freebsd-... file and remove -fno-rtti. > > Who maintains the FreeBSD qt port? Perhaps you should fix the problems in > the port and submit them as patches to the maintainer (and TT). I've been down that road before, and found that it was much less stressful and quite a bit easier to simply add a note to the README file included with the KDE modules; which is what I've done with the rtti issue too. - alex You wear guilt, like shackles on your feet, Like a halo in reverse - Depeche Mode To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 16: 0:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 433BF15140 for ; Tue, 20 Jul 1999 16:00:51 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id PAA27002; Tue, 20 Jul 1999 15:57:34 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id PAA10281; Tue, 20 Jul 1999 15:57:09 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA09947; Tue, 20 Jul 99 15:57:32 PDT Message-Id: <3794FEDB.B8F56C0D@softweyr.com> Date: Tue, 20 Jul 1999 16:57:31 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: linking question... References: <199907202120.RAA36480@cs.rpi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David E. Cross" wrote: > > I have a program (part of CDE)... we will call it 'foo', > > "foo" has library dependancies: libtt.so, libX11.so, libXt.so, libXext.so, and > libwcs.so(this last one is mine). > > libtt.so depends on iswalpha() and iswspace() (which are defined in libwcs.so) > > If I link with all of those I get an error that iswspace and iswalpha are > undefined, yet: nm /usr/local/lib/libwcs.so | grep isw returns: > > 00001358 T iswalpha > > 000013b0 T iswprint > > 00001384 T iswspace > > And if I change the '-lwcs' line to '/usr/local/lib/libwcs.a' it links fine. Did you remember -L/usr/local/lib so the linker will know to search for libraries there? Do you have a bogus libwcs.a in /usr/lib? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 16:34: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from valis.worldgate.ca (valis.worldgate.ca [198.161.84.2]) by hub.freebsd.org (Postfix) with ESMTP id 6FAA315408 for ; Tue, 20 Jul 1999 16:33:41 -0700 (PDT) (envelope-from skafte@worldgate.ca) Received: from worldgate.ca (skafte@diskless4.worldgate.ca [198.161.84.132]) by valis.worldgate.ca (8.9.3/8.9.1) with ESMTP id RAA62405 for ; Tue, 20 Jul 1999 17:33:22 -0600 (MDT) Message-ID: <37950744.87BD34A9@worldgate.ca> Date: Tue, 20 Jul 1999 17:33:24 -0600 From: Greg Skafte Organization: WorldGate Inc. X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: problems with the integrated tcp-wrappers. Content-Type: multipart/mixed; boundary="------------C95316B5E3515867115DE0DD" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------C95316B5E3515867115DE0DD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I've just recently switched from using the tcpwrappers port to the native tcpwrappers implemention the following config entries worked on the port but are not working with the native telnetd@xxx.yyy.84.2 ftpd rlogind@xxx.yyy.84.2 rshd@xxx.yyy.84.2 ntalkd@xxx.yyy.84.2 :\ KNOWN :\ rfc931 :\ banners /usr/local/etc/tcpd/banners.allow :\ spawn = (echo "permitted\: %s from %c" | /usr/bin/Mail -s "tcpd\: [P] %c -> %s" security)& # ssh is broken using spawn =, so don't. sshd sshdfwd-X11 : \ KNOWN \ xxx.zzz.118.0/255.255.255.0 : rfc931 It seems that the spawn is broken I've found this out by moving the banners line above the spawn. -- Email: skafte@worldgate.com Voice: +780 413 1910 Fax: +780 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) --------------C95316B5E3515867115DE0DD Content-Type: text/x-vcard; charset=us-ascii; name="skafte.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Greg Skafte Content-Disposition: attachment; filename="skafte.vcf" begin:vcard n:Skafte;Greg tel;pager:(780) 491 4791 tel;fax:(780) 421 4929 tel;work:(780) 413 1910 x-mozilla-html:FALSE url:www.worldgate.ca org:;Network Operations version:2.1 email;internet:skafte@worldgate.ca title:Operations Manager adr;quoted-printable:;;#575 Sun Life Place =0D=0A10123 99 Street;Edmonton;Alberta;T5J 3H1;Canada x-mozilla-cpt:;-2496 fn:Greg Skafte end:vcard --------------C95316B5E3515867115DE0DD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 17:25:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 6B0441503A for ; Tue, 20 Jul 1999 17:24:41 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40397>; Wed, 21 Jul 1999 10:01:28 +1000 Date: Wed, 21 Jul 1999 10:19:47 +1000 From: Peter Jeremy Subject: Proposal for new syscall to close files To: hackers@FreeBSD.ORG Message-Id: <99Jul21.100128est.40397@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's fairly common, when spawning new processes, to want to make sure all unwanted FDs are closed. Currently, the options for doing this are: 1) Use fcntl(fd, F_SETFD, FD_CLOEXEC) to set the close-on-exec flag when the file is opened/cloned. This may not be practical if the FD must remain open across some exec's, but not others. It is not possible to ensure that FDs implicitly opened within library functions have the close-on-exec flag set. It may be inefficient if there are lots of opens and few execs. 2) Explicitly close unwanted FDs in the child, before the exec(). This suffers from the usual resource tracking problems (ie it's easy to forget to close one - especially in a maze of pipe()/ dup()/dup2() calls designed to join the child's stdin/out/err to the parent). It also requires that the FD's be visible to the function - which may be difficult (the FD may be hidden within another function somewhere). 3) Close all FDs except the ones you explicitly want to keep. This is normally something like: for (i = getdtablesize(); --i > 2; ) close(i); The advantage is that you are sure you don't miss any. The disadvantage is that it requires a system call for each potentially open FD - >600 on my system - whereas maybe only 4 or 5 are actually open. In the case of option 3, you only really need to attempt to close file descriptors less then curproc->p_fd->fd_lastfile or even curproc->p_fd->fd_nfiles, but these values aren't readily accessible from userland. (And this still suffers the overhead of a userland to kernel transition for each FD). I'd therefore like to propose a new syscall that closes _all_ file descriptors associated with a process, except for those passed as 1 bits in an fd_set. The proposed API is: int cleanup_files(int nfds, const fd_set *leavefds); where nfds specifies the number of fds in *leavefds to potentially keep open (ie all fds >= nfds will be closed). The function would return the number of FDs closed. The implementation would be along the lines of: struct cleanup_files_args { int nd; fd_set *leave; }; int cleanup_files(p, uap) register struct proc *p; register struct cleanup_files_args *uap; { fd_set s_fdset; fd_set *lset; int error, nclosed = 0; u_int i, ncpbytes, nfdbits; struct filedesc *fdp = p->p_fd; struct file **fpp; char *fdfp; if (uap->nd < 0 || uap->leave = NULL) return (EINVAL); /* some daemons mught not have any file descriptors */ if (fdp == NULL) { p->p_retval[0] = 0; return (0); } if (uap->nd > fdp->fd_lastfile) uap->nd = fdp->fd_lastfile + 1; /* * Allocate just enough bits for the passed fd_set. Use the * preallocated auto buffer if possible. */ nfdbits = roundup(uap->nd, NFDBITS); ncpbytes = nfdbits / NBBY; if (ncpbytes <= sizeof s_fdset) lset = &s_fdset; else lset = malloc(ncpbytes, M_SELECT, M_WAITOK); error = copyin(uap->leave, lbits, ncpbytes); if (error != 0) goto done; fpp = fdp->fd_ofiles; fdfp = fdp->fd_ofileflags; for (i = 0; i < uap->nd; i++, fpp++, fdfp++) { if (!FD_ISSET(i, lset) && *fpp != NULL) { if (*fdfp & UF_MAPPED) (void) munmapfd(p, i); error = closef(*fpp, p); if (error != 0) goto done; nclosed++; *fpp = NULL; *fdfp = 0; if (i < fdp->fd_freefile) fdp->fd_freefile = i; } } for (; i <= fdp->fd_lastfile; i++, fpp++, fdfp++) if (*fpp != NULL) { if (*fdfp & UF_MAPPED) (void) munmapfd(p, i); error = closef(*fpp, p); if (error != 0) goto done; nclosed++; *fpp = NULL; *fdfp = 0; if (i < fdp->fd_freefile) fdp->fd_freefile = i; } } while (fdp->fd_lastfile > 0 && fdp->fd_ofiles[fdp->fd_lastfile] == NULL) fdp->fd_lastfile--; done: if (lset != &s_fdset) free(lset, M_SELECT); p->p_retval[0] = nclosed; return (error); } Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 18: 2:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from trem.cnt.org.br (trem.cnt.org.br [200.19.123.1]) by hub.freebsd.org (Postfix) with ESMTP id 438E31540B for ; Tue, 20 Jul 1999 18:02:14 -0700 (PDT) (envelope-from ormonde@aker.com.br) Received: from fire2 ([10.2.0.18]) by trem.cnt.org.br (8.8.7/8.8.7) with SMTP id VAA20413 for ; Tue, 20 Jul 1999 21:47:28 -0300 (EST) (envelope-from ormonde@aker.com.br) Message-Id: <3.0.3.32.19990720220702.006facec@cnt.org.br> X-Sender: ormonde@cnt.org.br X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.3 (32) Date: Tue, 20 Jul 1999 22:07:02 -0300 To: hackers@freebsd.org From: Rodrigo Ormonde Subject: Remoting kernel debugging with FreeBSD 3.1 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 set up two boxes connected through a serial cable in order to try the remote kernel debugging, using xxgdb. I followed the instructions as they appear in the handbook, but I found some problems: In the target host, I started the boot with the -d option. When the DDB prompt appeared I typed gdb and then s, followed by enter. The debugging host was able to take control of the target host, however the xxgdb hanged up (or better, the command prompt did not appear, but I was still able to click on the quit button, for instance). I discovered the problem ocurred when the xxgdb tried to read the source file, because when a started it without the "symbol-file kernel.debug" command, everything worked fine (but it didn't help much, for I was unable to check the symbols). The interesting point is the if a quit the xxgdb and start it again (with the debugging host still stopped) and issue the "symbol-file kernel.debug" command, xxgdb is able to read the symbols and point exactly the source code line where the kernel is stopped, but it does not read the source file. I'm then able to set a break point on some functions, but when the breakpoint is reached xxgdb hangs again (and if I quit and start it again like I just wrote, it also works). Has anybody also faced this problem ? Is there any solutions ? By the way, is it possible to debug a KLD module using remoting debugging ? Any tricks ? Please send a copy of the answers to me, I'm not on the list. Thanks in advance, -- Rodrigo de La Rocque Ormonde e-mail: ormonde@aker.com.br Aker Consultoria e Informatica LTDA - http:///www.aker.com.br --> Turn your PC into a workstation. Use FreeBSD <-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 18:49: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.antisocial.net (ns1.antisocial.net [208.10.211.34]) by hub.freebsd.org (Postfix) with ESMTP id E71FB14F54 for ; Tue, 20 Jul 1999 18:48:56 -0700 (PDT) (envelope-from modred@ns1.antisocial.net) Received: from localhost (modred@localhost) by ns1.antisocial.net (8.9.3/8.9.3) with ESMTP id UAA05760; Tue, 20 Jul 1999 20:47:33 -0500 (EST) Date: Tue, 20 Jul 1999 20:47:32 -0500 (EST) From: Modred To: Vincent Poy Cc: sthaug@nethelp.no, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Jul 1999, Vincent Poy wrote: > No idea but it seems like the people who sold the Cisco switches > atleast claimed that each port is supposed to be secure to prevent packet > sniffing by people on the other ports... Perhaps they were touting 'VLANs'? I can see seperate/many, logical networks configured across one/few physical ports via a VLAN being relatively secure (VLANs can consist of a single port, and each VLAN is it's own subnet). (Is this freebsd-net-ish?) Later, --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 18:55:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (Postfix) with ESMTP id 5796415476 for ; Tue, 20 Jul 1999 18:55:10 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-118.camalott.com [208.229.74.118]) by mail.camalott.com (8.8.7/8.8.7) with ESMTP id VAA00473; Tue, 20 Jul 1999 21:06:34 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.3) id UAA56998; Tue, 20 Jul 1999 20:54:58 -0500 (CDT) (envelope-from joelh) To: Warner Losh Cc: Per Lundberg , Alex Zepeda , hackers@FreeBSD.ORG Subject: Re: glibc References: <199907191602.KAA79798@harmony.village.org> From: Joel Ray Holveck Date: 20 Jul 1999 20:54:51 -0500 In-Reply-To: Warner Losh's message of "Mon, 19 Jul 1999 10:02:36 -0600" Message-ID: <863dyihims.fsf@detlev.UUCP> Lines: 18 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I know it isn't standard. But it works well, and is used by a lot of >> programs. Perhaps it should have been put in another library than libc, >> though. Actually, I'd better suggest this to the GNU people right ahead. > There has been talking of having a libgnu.a to contain common > routines like the long getopt... Many of these common GNU routines (including getopt_long) are in liberty. That's what it was made for. It's fallen out of maintainence, but I recall somebody making noises a month or two ago about reviving it. joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 19:22:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (mailbox.adm.binghamton.edu [128.226.10.60]) by hub.freebsd.org (Postfix) with ESMTP id 8E1A5150B5 for ; Tue, 20 Jul 1999 19:22:07 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from cs.binghamton.edu (bing241.net108.binghamton.edu [128.226.108.241]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id WAA10171 for ; Tue, 20 Jul 1999 22:22:04 -0400 (EDT) Message-ID: <37952EBF.3960E7D4@cs.binghamton.edu> Date: Tue, 20 Jul 1999 22:21:51 -0400 From: Zhihui Zhang Organization: SUNY - Binghamton X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: understanding code related to forced COW for debugger Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have tried to understand the following code in vm_map_lookup() without much success: if (fault_type & VM_PROT_OVERRIDE_WRITE) prot = entry->max_protection; else prot = entry->protection; ........ if (entry->wired_count && (fault_type & VM_PROT_WRITE) && (entry->eflags & MAP_ENTRY_COW) && (fault_typea & VM_PROT_OVERRIDE_WRITE) == 0) { RETURN(KERN_PROTECTION_FAILURE); } At first, it seems to me that if you want to write a COW page, you must have OVERRIDE_WRITE set. But later I find that when wired_count is non zero, we are actually simulating a page fault, not a real one. Anyway, I do not know how the above code (1) prevents a debugger from writing a binary code, (2) forces a COW when a debugger write other data. I also have some questions on wiring a page: (1) According to the man pages of mlock(2), a wired page can still cause protection-violation faults. But in the same vm_map_lookup(), we have the following code: if (*wired) prot = fault_type = entry->protection; and the comment says "get it for all possible accesses". As I undersand it, we wire a page by simulating a page fault (no matter whether it is kernel or user who is wiring a page). (2) Can the kernel wire a page of a user process without that user's request (by calling mlock)? Any help is appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 20: 2: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id E74EF15054 for ; Tue, 20 Jul 1999 20:02:00 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id TAA42180; Tue, 20 Jul 1999 19:59:05 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Tue, 20 Jul 1999 19:59:05 -0700 (PDT) From: Vincent Poy To: Modred Cc: sthaug@nethelp.no, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Jul 1999, Modred wrote: > On Tue, 20 Jul 1999, Vincent Poy wrote: > > > No idea but it seems like the people who sold the Cisco switches > > atleast claimed that each port is supposed to be secure to prevent packet > > sniffing by people on the other ports... > > Perhaps they were touting 'VLANs'? I can see seperate/many, logical > networks configured across one/few physical ports via a VLAN being > relatively secure (VLANs can consist of a single port, and each VLAN is > it's own subnet). VLAN could be it... > (Is this freebsd-net-ish?) Ofcourse, remember the original discussion is ethernet performance between two FreeBSD boxes. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 21:24:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 32B88151C9; Tue, 20 Jul 1999 21:24:40 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id AAA29810; Wed, 21 Jul 1999 00:26:54 -0400 From: Bill Paul Message-Id: <199907210426.AAA29810@skynet.ctr.columbia.edu> Subject: Call for testers: Adaptec AIC-6915 fast ethernet driver To: hackers@freebsd.org, hardware@freebsd.org Date: Wed, 21 Jul 1999 00:26:53 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 4495 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A driver for FreeBSD 3.x and 4.0-current is now available for testing for fast ethernet adapters based on the Adaptec AIC-6915 "Starfire" ethernet controller. This includes the following Adaptec "Duralink" models: - ANA-62011 single port 64-bit adapter - ANA-62022 dual port 64-bit adapter - ANA-62044 quad port 64-bit adapter - ANA-69011 single port 32-bit adapter - ANA-62020 single port 100baseFX These are Adaptec's replacements for its older DEC 21x4x-based multiport line of adapters. All cards support 10/100 speeds in full or half duplex. The multiport cards consist of multiple AIC-6915 chips linkec via a PCI to PCI bridge. Currently I have only tested the ANA-62022 dual port card, however all of them should work equally well. The 64-bit cards will work in a 32-bit slot on most newer machines. The Starfire supports a great many features including a 16-entry perfect RX filter, a 512-bit multicast hash table filter, a 512-bit high priority hash table, VLAN filtering, multiple RX and TX queues, and several different descriptor formats. There is also a programmable frame processor, however I haven't figured out how to use it. The FreeBSD driver uses a frame-based transmit descriptor (up to 14 packet fragments in one descriptor) and the producer/consumer queueing model with TX and RX completion descriptor queues. The perfect filter and hash filter are used for hardware multicast filtering. Support for BPF mode and promiscuous mode is also provided. The Starfire also supports TCP/IP checksum offload, however this is not yet implemented in this driver. The receive ring is programmed to have 256 descriptors. The transmit ring uses 128. This should be plenty for most server-based applications. Unfortunately, in spite of all the features in the Starfire, the chip requires receive buffers to be longword aligned, which means that received packets have to be copied in order to achieve proper payload alignemnt (which is handy on the x86 and required on the alpha). You'd think if they could go to the trouble of designing in special descriptor formats for MS-DOS and OS/2, they could handle DMAing to unaligned addresses. Oh well. This driver should work on both FreeBSD/i386 and FreeBSD/alpha. To add the driver to an existing FreeBSD 3.x system, do the following: - Download if_sf.c and if_sfreg.h from http://www.freebsd.org/~wpaul/Adaptec/3.0 and put them in /sys/pci. - Edit /sys/conf/files and add a line that says: pci/if_sf.c optional sf device-driver - Edit your kernel config file (e.g. /sys/i386/conf) and add a line that says: device sf0 - Config and compile a new kernel and boot it. To add the driver to an existing FreeBSD 4.0-current system, do one the following: - Download if_sf.c and if_sfreg.h from http://www.freebsd.org/~wpaul/Adaptec/4.0 and put them in /sys/pci. - Edit /sys/conf/files and add a line that says: pci/if_sf.c optional sf - Edit your kernel config file (e.g. /sys/i386/conf) and add a line that says: device sf0 - Config and compile a new kernel and boot it. Alternatively, if you have FreeBSD 4.0-current running on the x86 platform and don't want to recompile your kernel, you can try the following: - Download sf.ko from http://www.freebsd.org/~wpaul/Adaptec/4.0 and put it in /modules. - Edit /boot/defaults/loader.conf and add a line to the device driver modules section that says: sf_load="YES" # Adaptec PCI ethernet - Reboot The sf.ko module is compiled without BPF support. A Makefile is provided in the 4.0 directory which should allow you to recompile the module on both the x86 and alpha platforms. As usual, if you have any problems, please report them to wpaul@skynet.ctr.columbia.edu. Remember to provide lots of detailed information. Vote early and vote often. The sooner people bang on this a little, the sooner it will go into the tree. No user-servicable parts inside. Offer void where prohibited by law. Operators are standing by. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 22: 8:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id C4F571544A for ; Tue, 20 Jul 1999 22:08:12 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 116obp-00048n-00; Wed, 21 Jul 1999 07:08:01 +0200 From: Sheldon Hearn To: Greg Skafte Cc: freebsd-hackers@freebsd.org Subject: Re: problems with the integrated tcp-wrappers. In-reply-to: Your message of "Tue, 20 Jul 1999 17:33:24 CST." <37950744.87BD34A9@worldgate.ca> Date: Wed, 21 Jul 1999 07:08:01 +0200 Message-ID: <15920.932533681@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Jul 1999 17:33:24 CST, Greg Skafte wrote: > I've just recently switched from using the tcpwrappers port to the > native tcpwrappers implemention I really shouldn't be answering, since you've mailed the wrong mailing list, but I can't resist. :-) > the following config entries worked on the port but are not working with > the native "Not working" is always best defined by way of syslog messages or some other output, copied verbatim. :-) Nevertheless, I haven't tested the spawn option, so "there's a doubt setting up in my people's mind" [1]. How about this; I'll look into it in a few hours, since I might be able to tickle a bug on my own. In the meantime, you grovel through your syslog messages and see if you can spot any useful error messages. If you can, I'd appreciate private mail. Ciao, Sheldon. [1] Apologies to the Round The Horne crowd. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 22:58:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 07C3A14E7B for ; Tue, 20 Jul 1999 22:58:39 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id BAA43815; Wed, 21 Jul 1999 01:57:46 -0400 (EDT) Message-Id: <199907210557.BAA43815@cs.rpi.edu> To: Wes Peters Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: linking question... In-Reply-To: Message from Wes Peters of "Tue, 20 Jul 1999 16:57:31 MDT." <3794FEDB.B8F56C0D@softweyr.com> Date: Wed, 21 Jul 1999 01:57:40 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have a program (part of CDE)... we will call it 'foo', > > > > "foo" has library dependancies: libtt.so, libX11.so, libXt.so, libXext.so, and > > libwcs.so(this last one is mine). > > > > libtt.so depends on iswalpha() and iswspace() (which are defined in libwcs.so) > > > > If I link with all of those I get an error that iswspace and iswalpha are > > undefined, yet: nm /usr/local/lib/libwcs.so | grep isw returns: > > > 00001358 T iswalpha > > > 000013b0 T iswprint > > > 00001384 T iswspace > > > > And if I change the '-lwcs' line to '/usr/local/lib/libwcs.a' it links fine. > > Did you remember -L/usr/local/lib so the linker will know to search for > libraries there? Do you have a bogus libwcs.a in /usr/lib? The problem indeed was conflicting libraries... (in /usr/X11R6/lib).. however I did place on the line *immediately* before the -lwcs a -L/usr/local/lib, however it appeared to take the /usr/X11R6/lib (which was in a previous -L statement) version instead. Is this correct? -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 23:13:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (Postfix) with ESMTP id 3B0AB1545C for ; Tue, 20 Jul 1999 23:13:47 -0700 (PDT) (envelope-from eT@post.com) Received: (from root@localhost) by Thingol.KryptoKom.DE (8.9.1/8.9.1) id KAA08108; Wed, 21 Jul 1999 10:08:23 +0200 Received: from cirdan.kryptokom.de by KryptoWall via smtpp (Version 1.2.0) id kwa08101; Wed Jul 21 10:07:58 1999 Received: from fwd.kryptokom.de ([192.168.6.40]) by Cirdan.KryptoKom.DE (8.8.8/8.8.8) with ESMTP id IAA15704; Wed, 21 Jul 1999 08:19:13 +0200 Received: from post.com (localhost [127.0.0.1]) by fwd.kryptokom.de (8.9.2/8.9.2) with ESMTP id IAA00319; Wed, 21 Jul 1999 08:17:02 +0200 (CEST) (envelope-from eT@post.com) Message-ID: <379565DD.7E4CFEBA@post.com> Date: Wed, 21 Jul 1999 08:17:02 +0200 From: eT X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Alex Zepeda Cc: Hackers FreeBSD Subject: Re: KDE on FreeBSD (missing symbols) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda wrote: > With whatever Qt version you're using go into the appropiate > configs/freebsd-... file and remove -fno-rtti. Hi alex, thanks for the speedy response. I can't find any 'fno-rtti' to start with in the freebsd-g++-shared/static? So, I compiled it without that flag anyway. I will compile qt-1.42 and then recompile the kde sources and see what happens. Any other ideas? eT -- Etienne de Bruin; eT@post.com visit eT on the web: http://listen.to/eT (last update: 12 Mar 1999) "i'm living proof that the spirit moves" - dc talk, the truth. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 20 23:20: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wenet.net (pm3-1.ppp.wenet.net [206.15.85.1]) by hub.freebsd.org (Postfix) with ESMTP id 65BA015140 for ; Tue, 20 Jul 1999 23:19:57 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by wenet.net (8.9.3/8.9.1) with ESMTP id XAA40783; Tue, 20 Jul 1999 23:18:59 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Tue, 20 Jul 1999 23:18:59 -0700 (PDT) From: Alex Zepeda To: eT Cc: Hackers FreeBSD Subject: Re: KDE on FreeBSD (missing symbols) In-Reply-To: <379565DD.7E4CFEBA@post.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Jul 1999, eT wrote: > Hi alex, thanks for the speedy response. > > I can't find any 'fno-rtti' to start with in the > freebsd-g++-shared/static? So, I compiled it without that flag > anyway. > > I will compile qt-1.42 and then recompile the kde sources and see what > happens. > > Any other ideas? The only other thing I can think of is that for some reason your application and your libraries were compiled with different name mangling schemes, usually this indicates different compilers being used (but not always). Make sure to use the same compiler and same flags for the application and libraries. - alex You wear guilt, like shackles on your feet, Like a halo in reverse - Depeche Mode To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 0:19:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id D4BF014FBD for ; Wed, 21 Jul 1999 00:19:29 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id JAA15389 for ; Wed, 21 Jul 1999 09:19:02 +0200 (MET DST) Date: Wed, 21 Jul 1999 09:19:00 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: FreeBSD hackers mailing list Subject: Re: is dumpon/savecore broken? (fwd) 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 think that is Nick's point. You can no longer specify a dump > device in the kernel config file. > > troutmask:root[203] config TROUTMASK > config: line 41: root/dump/swap specifications obsolete > > On the other hand, you should have kernel.old or a fixit > floppy available. The problem is not having a kernel lying around, I have about five. I would like to crash the system before the filesystems get mounted read/write. /usr you can mount read only and you can put the important directories on NFS, but the root and /var are still at jeopardy. Writing the USB Zip driver is a bit of a pain this way. Nick -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 0:26:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (Postfix) with SMTP id E645F14E77 for ; Wed, 21 Jul 1999 00:26:06 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 5296 invoked from network); 21 Jul 1999 06:58:43 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail.cdsnet.net with SMTP; 21 Jul 1999 06:58:43 -0000 Date: Tue, 20 Jul 1999 23:58:09 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Modred Cc: Vincent Poy , sthaug@nethelp.no, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? 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 Perhaps I'm missing something obvious, but since switches forward packets selectively per port, I would think it would be hard to sniff packets on any port, w/o administrative access to the switch to tell it to mirror data to a different port. ie, if I'm plugged into port 1, I can't see traffic on a switch on port 2 except for broadcast traffic... On Tue, 20 Jul 1999, Modred wrote: > On Tue, 20 Jul 1999, Vincent Poy wrote: > > > No idea but it seems like the people who sold the Cisco switches > > atleast claimed that each port is supposed to be secure to prevent packet > > sniffing by people on the other ports... > > Perhaps they were touting 'VLANs'? I can see seperate/many, logical > networks configured across one/few physical ports via a VLAN being > relatively secure (VLANs can consist of a single port, and each VLAN is > it's own subnet). > > (Is this freebsd-net-ish?) > > Later, > --mike > > > > 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 Jul 21 0:28:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ics.ntts.co.jp (relay.ics.ntts.co.jp [202.32.24.35]) by hub.freebsd.org (Postfix) with ESMTP id 248D514E7B for ; Wed, 21 Jul 1999 00:28:39 -0700 (PDT) (envelope-from morita@jts.ntts.co.jp) Received: from jtsgw.jts.ntts.co.jp by relay.ics.ntts.co.jp (8.8.8/3.6W-NTTSOFT-SUR2.0) id QAA26511; Wed, 21 Jul 1999 16:26:41 +0900 (JST) Received: from enif.jts.ntts.co.jp by jtsgw.jts.ntts.co.jp (8.9.1a/3.7Wpl2-JTSGW-2.0) id QAA08239; Wed, 21 Jul 1999 16:26:13 +0900 (JST) Received: from enf by enif.jts.ntts.co.jp (8.7.6/3.4W5-3s-1.0) id QAA16321; Wed, 21 Jul 1999 16:28:57 +0900 (JST) Message-ID: <000801bed34a$b4e1f360$0f04070a@jts.ntts.co.jp> From: "morita" To: "freebsd-hackers@FreeBSD.O" , , References: <199907210603.PAA01215@lavender.yy.cs.keio.ac.jp> Subject: Re: [FreeBSD-net-jp 1746] [FYI] Adaptec AIC-6915 "Starfire" ethernet controller driver and plus question compaq presario dec ethernet controller driver Date: Wed, 21 Jul 1999 16:29:01 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" 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 $B?9ED$G$9!#(B > > These are Adaptec's replacements for its older DEC 21x4x-based multiport $B$3$N%I%i%$%P!<$OL5$/$J$k$N$G$7$g$&$+!)(B->DEC 21x4x-based no more supllyed ->DEC 21x4x-based > line of adapters. All cards support 10/100 speeds in full or half duplex. > The multiport cards consist of multiple AIC-6915 chips linkec via a PCI > to PCI bridge. Currently I have only tested the ANA-62022 dual port card, > however all of them should work equally well. The 64-bit cards will work > in a 32-bit slot on most newer machines. > $B%3%s%Q%C%/!!(BPRESARIO$B!!(B2274$B!!$K(BFreeBSD3.2$B%$%s%9%H!<%k$7$?$N$G$9$,!"(B NIC$B!'!!(BDEC 21143-based $B$H%S%G%*%+!<%I!'(BSiS5598$B$N@_Dj$,$&$^$/$$$-$^$;$s!"8=:_(B $BF0$+$7$F$k(B $BJ}$,$$$i$7$?$i65$($F$/$@$5$$!#(B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 0:29: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id A5C6915008 for ; Wed, 21 Jul 1999 00:28:53 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 116qmy-0004RC-00 for freebsd-hackers@freebsd.org; Wed, 21 Jul 1999 09:27:40 +0200 From: Sheldon Hearn To: Greg Skafte Cc: freebsd-questions@freebsd.org Subject: Re: problems with the integrated tcp-wrappers. In-reply-to: Your message of "Tue, 20 Jul 1999 17:33:24 CST." <37950744.87BD34A9@worldgate.ca> Date: Wed, 21 Jul 1999 09:27:28 +0200 Message-ID: <17051.932542048@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Hijacked from freebsd-hackers ] On Tue, 20 Jul 1999 17:33:24 CST, Greg Skafte wrote: > I've just recently switched from using the tcpwrappers port to the > native tcpwrappers implemention > > the following config entries worked on the port but are not working with > the native I've tested the spawn option using a standalone sshd daemon and both of the following two configurations work as expected (on their own, not in conjunction): sshd: ALL : \ spawn (/usr/bin/mail -s "sshd request from %h" sheldonh ; Wed, 21 Jul 1999 00:34:32 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA25177; Wed, 21 Jul 1999 00:33:31 -0700 (PDT) (envelope-from dillon) Date: Wed, 21 Jul 1999 00:33:31 -0700 (PDT) From: Matthew Dillon Message-Id: <199907210733.AAA25177@apollo.backplane.com> To: Jaye Mathisen Cc: Modred , Vincent Poy , sthaug@nethelp.no, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Perhaps I'm missing something obvious, but since switches forward packets :selectively per port, I would think it would be hard to sniff packets on :any port, w/o administrative access to the switch to tell it to mirror :data to a different port. : :ie, if I'm plugged into port 1, I can't see traffic on a switch on port 2 :except for broadcast traffic... The switch routes traffic based on its ARP cache. While you cannot easily monitor another port's traffic, you can take over its MAC address and steal its traffic. Cisco VLANs perform a different function. Remember that a logical ethernet segment is typically routed by a single network route. For example, a class C or a subnetted class C. The catalyst allows you to throw machines into different VLAN buckets which, in addition to the better security, allows you to assign separate subnets to each bucket. The switch itself doesn't care, but this can reduce global ARP traffic significantly. Catalysts can have hundreds of ports stuffed into them. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 0:47:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [196.37.91.10]) by hub.freebsd.org (Postfix) with ESMTP id 42F4915140 for ; Wed, 21 Jul 1999 00:47:33 -0700 (PDT) (envelope-from rbezuide@oskar.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.nanoteq.co.za (8.9.0/8.9.0) id JAA20088; Wed, 21 Jul 1999 09:48:34 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199907210748.JAA20088@oskar.nanoteq.co.za> Subject: Re: if_dl.h in stable causes sendmail segmentation In-Reply-To: <199907201912.MAA69231@vashon.polstra.com> from John Polstra at "Jul 20, 99 12:12:02 pm" To: jdp@polstra.com (John Polstra) Date: Wed, 21 Jul 1999 09:48:32 +0200 (SAT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... > In article <199907201542.RAA02634@oskar.nanoteq.co.za>, > Reinier Bezuidenhout wrote: > > > I have the following situation... > ... [various userland SEGVs traced down to a change in if_dl.h] The sendmail that SEGV was compiled with the kernel that causes the crash ... I did the make release myself on a machine ... :( so it is not an updated kernel error :) Thanx Reinier > > Just a guess: it sounds like the kind of thing that would happen if > you updated your kernel without also rebuilding userland. > > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "No matter how cynical I get, I just can't keep up." -- Nora Ephron > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 1: 0:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id BC30815457 for ; Wed, 21 Jul 1999 01:00:12 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id AAA43601; Wed, 21 Jul 1999 00:58:30 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Wed, 21 Jul 1999 00:58:30 -0700 (PDT) From: Vincent Poy To: Matthew Dillon Cc: Jaye Mathisen , Modred , sthaug@nethelp.no, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? In-Reply-To: <199907210733.AAA25177@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Jul 1999, Matthew Dillon wrote: > :Perhaps I'm missing something obvious, but since switches forward packets > :selectively per port, I would think it would be hard to sniff packets on > :any port, w/o administrative access to the switch to tell it to mirror > :data to a different port. > : > :ie, if I'm plugged into port 1, I can't see traffic on a switch on port 2 > :except for broadcast traffic... > > The switch routes traffic based on its ARP cache. While you cannot > easily monitor another port's traffic, you can take over its MAC address > and steal its traffic. No idea, all I know is that people on our LAN without changing MAC addresses can see all traffic going on the LAN. Even from our FreeBSD box with trafshow, we can see traffic that is destined for the global net from the modem dialups. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 1:17:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay01.indigo.ie (relay01.indigo.ie [194.125.133.225]) by hub.freebsd.org (Postfix) with SMTP id 28EA615469 for ; Wed, 21 Jul 1999 01:17:45 -0700 (PDT) (envelope-from niall@pobox.com) Received: (qmail 23938 messnum 238378 invoked from network[194.125.207.54/ts99-045.dublin.indigo.ie]); 21 Jul 1999 08:16:25 -0000 Received: from ts99-045.dublin.indigo.ie (HELO pobox.com) (194.125.207.54) by relay01.indigo.ie (qp 23938) with SMTP; 21 Jul 1999 08:16:25 -0000 Message-ID: <37959D01.D849ABED@pobox.com> Date: Wed, 21 Jul 1999 10:12:17 +0000 From: Niall Smart X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Peter Jeremy Cc: hackers@FreeBSD.ORG Subject: Re: Proposal for new syscall to close files References: <99Jul21.100128est.40397@border.alcanet.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 3) Close all FDs except the ones you explicitly want to keep. This > is normally something like: > for (i = getdtablesize(); --i > 2; ) > close(i); > The advantage is that you are sure you don't miss any. The > disadvantage is that it requires a system call for each potentially > open FD - >600 on my system - whereas maybe only 4 or 5 are > actually open. How many daemons suffer from performance problems because of this? None that I know of. I'm sorry, but this syscall seems like clutter to me. Regards, Niall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 1:23: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (Postfix) with ESMTP id 07D3215475 for ; Wed, 21 Jul 1999 01:22:10 -0700 (PDT) (envelope-from eT@post.com) Received: (from root@localhost) by Thingol.KryptoKom.DE (8.9.1/8.9.1) id MAA12331; Wed, 21 Jul 1999 12:15:30 +0200 Received: from cirdan.kryptokom.de by KryptoWall via smtpp (Version 1.2.0) id kwa12328; Wed Jul 21 12:15:18 1999 Received: from fwd.kryptokom.de ([192.168.6.40]) by Cirdan.KryptoKom.DE (8.8.8/8.8.8) with ESMTP id KAA17285; Wed, 21 Jul 1999 10:26:32 +0200 Received: from post.com (localhost [127.0.0.1]) by fwd.kryptokom.de (8.9.2/8.9.2) with ESMTP id KAA00418; Wed, 21 Jul 1999 10:24:22 +0200 (CEST) (envelope-from eT@post.com) Message-ID: <379583B5.BC150E1B@post.com> Date: Wed, 21 Jul 1999 10:24:22 +0200 From: eT X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Alex Zepeda Cc: Hackers FreeBSD Subject: Re: KDE on FreeBSD (missing symbols) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda wrote: > On Wed, 21 Jul 1999, eT wrote: > > The only other thing I can think of is that for some reason your > application and your libraries were compiled with different name mangling > schemes, usually this indicates different compilers being used (but not > always). Make sure to use the same compiler and same flags for the > application and libraries. Hi, I noticed that my ld path was using the old libqt in /usr/X11R6/lib and not the new one I have in /usr/local/qt/lib. Problem I am getting now is libstdc++ problem: ld.elf complains: libstdc++.so.3: undefined symbol __ti9exception Any Ideas? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 1:33:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id B5D1114C39 for ; Wed, 21 Jul 1999 01:33:52 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 22945 invoked by uid 1001); 21 Jul 1999 08:32:47 +0000 (GMT) To: vince@venus.GAIANET.NET Cc: dillon@apollo.backplane.com, mrcpu@internetcds.com, modred@ns1.antisocial.net, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? From: sthaug@nethelp.no In-Reply-To: Your message of "Wed, 21 Jul 1999 00:58:30 -0700 (PDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 21 Jul 1999 10:32:47 +0200 Message-ID: <22943.932545967@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No idea, all I know is that people on our LAN without changing MAC > addresses can see all traffic going on the LAN. Even from our FreeBSD box > with trafshow, we can see traffic that is destined for the global net from > the modem dialups. Then either there is a hub between your net and the switch, or the switch is badly misconfigured. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 1:36:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 43F8414C39 for ; Wed, 21 Jul 1999 01:36:10 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id BAA43746; Wed, 21 Jul 1999 01:34:00 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Wed, 21 Jul 1999 01:34:00 -0700 (PDT) From: Vincent Poy To: sthaug@nethelp.no Cc: dillon@apollo.backplane.com, mrcpu@internetcds.com, modred@ns1.antisocial.net, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? In-Reply-To: <22943.932545967@verdi.nethelp.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Jul 1999 sthaug@nethelp.no wrote: > > No idea, all I know is that people on our LAN without changing MAC > > addresses can see all traffic going on the LAN. Even from our FreeBSD box > > with trafshow, we can see traffic that is destined for the global net from > > the modem dialups. > > Then either there is a hub between your net and the switch, or the switch > is badly misconfigured. Well, the switch came out of the box and just had the default setup.... It just has a IP assigned to it... And there is no hub between the net and the switch since all the modem pools are each on their own port. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 1:42:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 103CC14C39 for ; Wed, 21 Jul 1999 01:42:20 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 23060 invoked by uid 1001); 21 Jul 1999 08:39:57 +0000 (GMT) To: vince@venus.GAIANET.NET Cc: dillon@apollo.backplane.com, mrcpu@internetcds.com, modred@ns1.antisocial.net, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? From: sthaug@nethelp.no In-Reply-To: Your message of "Wed, 21 Jul 1999 01:34:00 -0700 (PDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 21 Jul 1999 10:39:57 +0200 Message-ID: <23058.932546397@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Then either there is a hub between your net and the switch, or the switch > > is badly misconfigured. > > Well, the switch came out of the box and just had the default > setup.... It just has a IP assigned to it... And there is no hub between > the net and the switch since all the modem pools are each on their own > port. If the switch "just has the default setup" I would recommend that somebody sit down and read the manual and try to *understand* what is happening - probably also try to experiment a bit with the switch configuration. Because what you're seeing is definitely not normal. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 1:44:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (Postfix) with SMTP id E379514C39 for ; Wed, 21 Jul 1999 01:44:25 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 24262 invoked from network); 21 Jul 1999 07:44:04 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail.cdsnet.net with SMTP; 21 Jul 1999 07:44:04 -0000 Date: Wed, 21 Jul 1999 00:43:29 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Matthew Dillon Cc: Modred , Vincent Poy , sthaug@nethelp.no, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? In-Reply-To: <199907210733.AAA25177@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Jul 1999, Matthew Dillon wrote: > :Perhaps I'm missing something obvious, but since switches forward packets > :selectively per port, I would think it would be hard to sniff packets on > :any port, w/o administrative access to the switch to tell it to mirror > :data to a different port. > : > :ie, if I'm plugged into port 1, I can't see traffic on a switch on port 2 > :except for broadcast traffic... > > The switch routes traffic based on its ARP cache. While you cannot > easily monitor another port's traffic, you can take over its MAC address > and steal its traffic. Well, this is waaaay past the trivial part. It certainly seems that you would have to have a lot of information from another source to be able to do this. I guess I'll I'm saying is that if you have a switch sitting there, and you're plugged into it, you're not going to be able to just fire up tcpdump and see much more than ethernet broadcasts, and IP broadcast traffic, and of course, traffic from and to your port... At least, not w/o what appears to be mucho work. And back to your regularly scheduled -hackers... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 1:47:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id C1F2C14C39 for ; Wed, 21 Jul 1999 01:47:30 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id BAA43821; Wed, 21 Jul 1999 01:43:53 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Wed, 21 Jul 1999 01:43:53 -0700 (PDT) From: Vincent Poy To: sthaug@nethelp.no Cc: dillon@apollo.backplane.com, mrcpu@internetcds.com, modred@ns1.antisocial.net, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? In-Reply-To: <23058.932546397@verdi.nethelp.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Jul 1999 sthaug@nethelp.no wrote: > > > Then either there is a hub between your net and the switch, or the switch > > > is badly misconfigured. > > > > Well, the switch came out of the box and just had the default > > setup.... It just has a IP assigned to it... And there is no hub between > > the net and the switch since all the modem pools are each on their own > > port. > > If the switch "just has the default setup" I would recommend that > somebody sit down and read the manual and try to *understand* what is > happening - probably also try to experiment a bit with the switch > configuration. Because what you're seeing is definitely not normal. Well, the manual doesn't guarantee security either.... The only thing the switch seems to do is give dedicated bandwidth to each port but no one knows if it's a true switch since someone did mention a CableTron switch being nothing but a bundled of hub ports inside grouped together. Also, the management feature isn't suppose to affect data from being seen on all the ports. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 2: 5:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id B51B514FF5 for ; Wed, 21 Jul 1999 02:05:42 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 23528 invoked by uid 1001); 21 Jul 1999 09:03:49 +0000 (GMT) To: vince@venus.GAIANET.NET Cc: dillon@apollo.backplane.com, mrcpu@internetcds.com, modred@ns1.antisocial.net, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? From: sthaug@nethelp.no In-Reply-To: Your message of "Wed, 21 Jul 1999 01:43:53 -0700 (PDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 21 Jul 1999 11:03:49 +0200 Message-ID: <23526.932547829@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If the switch "just has the default setup" I would recommend that > > somebody sit down and read the manual and try to *understand* what is > > happening - probably also try to experiment a bit with the switch > > configuration. Because what you're seeing is definitely not normal. > > Well, the manual doesn't guarantee security either.... This is true, and was well pointed out by Jan B. Koum. But most of the time the switch will nicely isolate traffic for you. However, if you are connected to what Cisco calls a "group switch module" (on a Cisco switch, of course) you need to be aware of what this really is. A Cisco "group switch" module is in reality a number of hubs (3 or 4) on one card. All ports in the same group will see the same traffic, of course. > The only > thing the switch seems to do is give dedicated bandwidth to each port but > no one knows if it's a true switch since someone did mention a CableTron > switch being nothing but a bundled of hub ports inside grouped together. You need to make up your mind. Do you have a Cisco Catalyst switch or a Cabletron switch? Since earlier in this thread you said "we don't know which port goes to what on the Catalyst" I assumed that you were indeed using a Cisco Catalyst. Since I don't know anything about Cabletron, I'll let others speak about that. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 2:25:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id 563661547A for ; Wed, 21 Jul 1999 02:25:50 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.3/8.9.3/Kp) with ESMTP id KAA38111; Wed, 21 Jul 1999 10:22:52 +0100 (BST) Message-ID: <37959139.8CF0641F@tdx.co.uk> Date: Wed, 21 Jul 1999 10:22:01 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Vincent Poy Cc: sthaug@nethelp.no, dillon@apollo.backplane.com, mrcpu@internetcds.com, modred@ns1.antisocial.net, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vincent Poy wrote: > Well, the manual doesn't guarantee security either.... The only > thing the switch seems to do is give dedicated bandwidth to each port but > no one knows if it's a true switch since someone did mention a CableTron > switch being nothing but a bundled of hub ports inside grouped together. > Also, the management feature isn't suppose to affect data from being seen > on all the ports. Can this be moved off -hackers?, onto perhaps FreeBSD-Hubs? Or even, back to ye'olde -chat? :-) -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 2:48:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id D6B2514BEE for ; Wed, 21 Jul 1999 02:48:55 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 21 Jul 1999 10:46:22 +0100 (BST) Date: Wed, 21 Jul 1999 10:46:21 +0100 From: David Malone To: "David E. Cross" Cc: Snob Art Genre , hackers@FreeBSD.ORG Subject: Re: amandad zombies (fwd) Message-ID: <19990721104621.A7765@walton.maths.tcd.ie> References: <199907202115.RAA36397@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199907202115.RAA36397@cs.rpi.edu>; from David E. Cross on Tue, Jul 20, 1999 at 05:15:46PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 20, 1999 at 05:15:46PM -0400, David E. Cross wrote: > We had a similiar problem here. We had meant to submit-pr it but forgot. > In our case it was because inetd had only the amanda line in it (inetd was > not responsible for any other services. Our guess was that it is an off by > one error in inted somewhere, but we never traced it down further. Our > work-arround was to enable a second service. Do you remember what version of inetd you saw this problem with? I'll see if I can reproduce the problem with the most recent inetd at home - but it is possible it has been fixed. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 2:59:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from not.demophon.com (ns.demophon.com [193.65.70.13]) by hub.freebsd.org (Postfix) with ESMTP id 2BAA914E95 for ; Wed, 21 Jul 1999 02:59:33 -0700 (PDT) (envelope-from will@not.demophon.com) Received: (from will@localhost) by not.demophon.com (8.9.3/8.8.7) id MAA82753; Wed, 21 Jul 1999 12:53:04 +0300 (EEST) (envelope-from will) To: jeremyp@gsmx07.alcatel.com.au (Peter Jeremy) Cc: hackers@freebsd.org Subject: Re: speed of file(1) References: <99Jul21.075453est.40331@border.alcanet.com.au> From: Ville-Pertti Keinonen Date: 21 Jul 1999 12:53:03 +0300 In-Reply-To: jeremyp@gsmx07.alcatel.com.au's message of "21 Jul 1999 01:15:28 +0300" Message-ID: <86u2qy2utc.fsf@not.demophon.com> Lines: 37 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jeremyp@gsmx07.alcatel.com.au (Peter Jeremy) writes: > "Leif Neland" wrote: > >My 60MHz Pentium, FreeBSD > > > >time file /usr/home/leif/vnc-3.3.2r > >/usr/home/leif/vnc-3.3.2r3_unixsrc.tgz: gzip compressed data, deflated, > >original filename, last modified: Thu Jan 21 19:23:21 1999 > > > >real 0m1.237s > >user 0m0.758s > >sys 0m0.394s > I can't believe these figures. Hmm, a 200 MHz Pentium (MMX), 3.2-RELEASE, everything in cache: $ /usr/bin/time file twofish.tar.gz twofish.tar.gz: gzip compressed data, deflated, last modified: Mon Jun 15 02:40:53 1998, os: Unix 0.35 real 0.24 user 0.10 sys I'd say that considering that things are cached (cpu-bound), it's very accurately proportional to Leif's time. Variances can be accounted for by the slight implementation differences (the MMX version has a bigger L1 and better branch prediction). It's also reasonably proportional to a 400 MHz PII (0.09/0.08/0.01 running 3.2 -- 0.06/0.04/0.01 running 2.2.8, BTW). Considering the completely different core, this is also quite close to what you might expect. > I can't reproduce the complaint using a 64MB PII-266 running -CURRENT - > there's no evidence of lack of speed, and profiling file(1) doesn't > show any anomolies. What are your results, then? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 3:50:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 104FB154AC; Wed, 21 Jul 1999 03:50:33 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 2B7D81911; Wed, 21 Jul 1999 12:49:16 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 2A87949D2; Wed, 21 Jul 1999 12:49:16 +0200 (CEST) Date: Wed, 21 Jul 1999 12:49:14 +0200 (CEST) From: Andrzej Bialecki To: "Brian F. Feldman" Cc: Mike Smith , "Daniel C. Sobral" , freebsd-hackers@FreeBSD.org Subject: Re: System unique identifier..... 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, 18 Jul 1999, Brian F. Feldman wrote: > On Sun, 18 Jul 1999, Mike Smith wrote: > > > > Mike Smith wrote: > > > > > > > > The loader will, at some stage in the future, grow a persistent data > > > > store in which items like this can be saved. > > > > > > Doesn't /boot/[defaults/]loader.conf[.local] qualify as persistent > > > data storage? > > > > There is little or no chance that the loader will gain the ability to > > write back to filesystems. Some of them don't support it (eg. > > iso9660), others may not (TFTP, NFS), and the code required for some of > > them (especially UFS) would be problematically large. > > That's not quite true. It wouldn't be too hard to modify existant files, > but writing new ones/truncating would take a lot of work. It's still not > a great idea to try to use a file on the FS for storage of persistent > data. Wouldn't it be possible to have the kernel itself read in persistent > data (in some form such as getenv?) to be written to disk? That way, the > boot loader could pass it easily, and not have to worry about storage. This may sound like a heresy to you, but... Why don't use the Forth blocks for that? They were invented for that purpose. We can create the files beforehand (under normal OS operation), then from the bootloader we can read and modify them - I suppose writing to a disk block is much easier than through the filesystem layer... Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 3:52:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [195.224.76.132]) by hub.freebsd.org (Postfix) with ESMTP id 2040F1546A for ; Wed, 21 Jul 1999 03:52:05 -0700 (PDT) (envelope-from fanf@chiark.greenend.org.uk) Received: from fanf by chiark.greenend.org.uk with local (Exim 2.02 #1) id 116tyn-0006Hy-00 (Debian); Wed, 21 Jul 1999 11:52:05 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14229.42580.977708.73708@chiark.greenend.org.uk> Date: Wed, 21 Jul 1999 11:52:04 +0100 (BST) In-Reply-To: <3793ABE0.15090E38@softweyr.com> References: <199907192111.OAA01326@dingo.cdrom.com> From: Tony Finch To: hackers@freebsd.org Subject: Re: PAM & LDAP in FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote: > >The implementation details are as unimportant as ever: they have to work >and be maintainable. Following prior art remains a good idea; the Solaris >"name service switch" implementation is a good starting point to consider. What about using the IRS library from bind? Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net Winner, International Obfuscated C Code Competition 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 4:28: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 7956914DF5 for ; Wed, 21 Jul 1999 04:27:55 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40326>; Wed, 21 Jul 1999 21:06:48 +1000 Date: Wed, 21 Jul 1999 21:25:07 +1000 From: Peter Jeremy Subject: Re: speed of file(1) In-reply-to: <86u2qy2utc.fsf@not.demophon.com> To: will@iki.fi Cc: hackers@FreeBSD.ORG Message-Id: <99Jul21.210648est.40326@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ville-Pertti Keinonen wrote: >jeremyp@gsmx07.alcatel.com.au (Peter Jeremy) writes: >> I can't believe these figures. Based on the figures below, maybe I was overly hasty in this statement. The changes between 2.x and 3.x magic files have far more impact than I would have expected. >What are your results, then? All timings with everything cached (although the 386 only has 8MB which limits the cacheability). For the 2.2.5 systems, I give timings with both the 2.2.5 magic and the 4.0 magic (which is the same as 3.2-RELEASE, in /tmp). i386SX-25 running 2.2.5 (roughly as posted earlier): % /usr/bin/time file src/Z/dhcp-2.0b1pl26.tar.gz src/Z/dhcp-2.0b1pl26.tar.gz: gzip compressed data, deflated, last modified: Thu Jan 1 10:00:00 1970, os: Unix 2.82 real 1.92 user 0.84 sys % /usr/bin/time file -m /tmp/magic src/Z/dhcp-2.0b1pl26.tar.gz src/Z/dhcp-2.0b1pl26.tar.gz: gzip compressed data, deflated, last modified: Thu Jan 1 10:00:00 1970, os: Unix 4.05 real 2.67 user 1.23 sys 486DX2-50 running 2.2.5: % /usr/bin/time file src/Z/dhcp-3.0-alpha-19990423.tar.gz src/Z/dhcp-3.0-alpha-19990423.tar.gz: gzip compressed data, deflated, last modified: Thu Jan 1 10:00:00 1970, os: Unix 1.43 real 0.96 user 0.38 sys % /usr/bin/time file -m /tmp/magic src/Z/dhcp-3.0-alpha-19990423.tar.gz src/Z/dhcp-3.0-alpha-19990423.tar.gz: gzip compressed data, deflated, last modified: Thu Jan 1 10:00:00 1970, os: Unix 2.15 real 1.62 user 0.44 sys PII-266 running 4.0-CURRENT: % /usr/bin/time file src/Z/dhcp-1.4.0p6.tar.gz src/Z/dhcp-1.4.0p6.tar.gz: gzip compressed data, deflated, last modified: Wed Mar 3 20:57:52 1999, os: Unix 0.13 real 0.09 user 0.03 sys When I profile file in a slow system (like a 386 or 486), there is an obvious performance bottleneck: The problem is the memcpy() invoked from fgets(). The only solution would seem to be to mmap() magic and parse it, rather than using fgets() to read it. This bottleneck will also be far more obvious on bandwidth-starved systems (like 386SX and 486DX2/4), whereas virtually the whole thing fits into the L2 cache on my P-II. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 4:33:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id D3E111546A for ; Wed, 21 Jul 1999 04:33:25 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40325>; Wed, 21 Jul 1999 21:13:59 +1000 Date: Wed, 21 Jul 1999 21:32:22 +1000 From: Peter Jeremy Subject: Re: Proposal for new syscall to close files In-reply-to: <86so6i2t1z.fsf@not.demophon.com> To: will@iki.fi Cc: hackers@FreeBSD.ORG Message-Id: <99Jul21.211359est.40325@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ville-Pertti Keinonen wrote: >Note that there are race conditions in your code. It was intended as a first cut, rather than tested code. Note that most of it was lifted from the code for select() and fdcloseexec(). > If it ever gets >committed (I don't think it's particularly useful myself), That's 2 against, 1 (me) for. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 4:34:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from des.follo.net (des.follo.net [195.204.143.216]) by hub.freebsd.org (Postfix) with ESMTP id 5852E14DF5 for ; Wed, 21 Jul 1999 04:34:39 -0700 (PDT) (envelope-from des@des.follo.net) Received: (from des@localhost) by des.follo.net (8.9.3/8.9.3) id NAA91870; Wed, 21 Jul 1999 13:34:15 +0200 (CEST) (envelope-from des) To: hackers@freebsd.org Subject: BSDI binary compatibility Organization: Yes Interactive Visit-Us-At: http://www.yes.no/ From: Dag-Erling Smorgrav Date: 21 Jul 1999 13:34:13 +0200 Message-ID: Lines: 30 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What kinds of BSDI binaries are we supposed to be able to run? I haven't had any luck getting *any* BSDI binaries to run on my (very recent) 4.0-CURRENT box. I have a handful of BSDI binaries, some of which are identified as: des@des ~/yes/bsdi/shopsite% file wwwinstall.cgi wwwinstall.cgi: unknown pure executable des@des ~/yes/bsdi/shopsite% ./wwwinstall.cgi zsh: bus error (core dumped) ./wwwinstall.cgi others (ls and cat from BSDI 4.0): des@des ~/yes/bsdi/cmc% file ./ls ./ls: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically linked, stripped des@des ~/yes/bsdi/cmc% ./ls ELF binary type not known. Use "brandelf" to brand it. zsh: abort ./ls and finally a few static ones Chris Costello was kind enough to build for me: des@des ~/yes/bsdi/cmc/bsdi_static% file hello hello: ELF 32-bit LSB executable, Intel 80386, version 1, statically linked, not stripped des@des ~/yes/bsdi/cmc/bsdi_static% ./hello ELF binary type not known. Use "brandelf" to brand it. zsh: abort ./hello DES -- Dag-Erling Smorgrav - des@yes.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 4:54: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penrose.isocor.ie (penrose.isocor.ie [194.106.155.117]) by hub.freebsd.org (Postfix) with ESMTP id CA46914F6A for ; Wed, 21 Jul 1999 04:53:56 -0700 (PDT) (envelope-from peter.edwards@isocor.ie) Received: from isocor.ie (194.106.155.218) by penrose.isocor.ie; 21 Jul 1999 12:52:21 +0100 Message-ID: <3795B50B.EFBBEFE2@isocor.ie> Date: Wed, 21 Jul 1999 12:54:51 +0100 From: Peter Edwards Organization: ISOCOR X-Mailer: Mozilla 4.6 [en] (X11; I; SunOS 5.6 i86pc) X-Accept-Language: en MIME-Version: 1.0 To: Peter Jeremy Cc: will@iki.fi, hackers@FreeBSD.ORG Subject: Re: speed of file(1) References: <99Jul21.210648est.40326@border.alcanet.com.au> Content-Type: multipart/mixed; boundary="------------8B774876DAB92991344CB5AD" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------8B774876DAB92991344CB5AD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit A quick look at the source reveals: A MAXMAGIS constant in file.h that estimates a limit of 1000 lines in magic. (The real number is 4802) An array sized on MAXMAGIS, that is reallocated every ALLOC_INTR lines of magic once MAXMAGIS is exceeded. The patch updates MAXMAGIS to 5000 (give a bit of room to grow) And makes ALLOC_INCR a variable that is bigger, and doubles every time it is used, to attenuate the problem if there ever ends up being 10000 entries in magic. Results on a 90Mhz Pentium: new verson time ./file ./file ./file: FreeBSD/i386 compact demand paged dynamically linked executable not stripped 0.14 real 0.11 user 0.02 sys old verson: ./file: FreeBSD/i386 compact demand paged dynamically linked executable not stripped 0.79 real 0.60 user 0.16 sys -- Peter. Peter Jeremy wrote: > > Ville-Pertti Keinonen wrote: > >jeremyp@gsmx07.alcatel.com.au (Peter Jeremy) writes: > >> I can't believe these figures. > > Based on the figures below, maybe I was overly hasty in this statement. > The changes between 2.x and 3.x magic files have far more impact than > I would have expected. > > >What are your results, then? > > All timings with everything cached (although the 386 only has 8MB > which limits the cacheability). For the 2.2.5 systems, I give timings > with both the 2.2.5 magic and the 4.0 magic (which is the same as > 3.2-RELEASE, in /tmp). > > i386SX-25 running 2.2.5 (roughly as posted earlier): > % /usr/bin/time file src/Z/dhcp-2.0b1pl26.tar.gz > src/Z/dhcp-2.0b1pl26.tar.gz: gzip compressed data, deflated, last modified: Thu Jan 1 10:00:00 1970, os: Unix > 2.82 real 1.92 user 0.84 sys > % /usr/bin/time file -m /tmp/magic src/Z/dhcp-2.0b1pl26.tar.gz > src/Z/dhcp-2.0b1pl26.tar.gz: gzip compressed data, deflated, last modified: Thu Jan 1 10:00:00 1970, os: Unix > 4.05 real 2.67 user 1.23 sys > > 486DX2-50 running 2.2.5: > % /usr/bin/time file src/Z/dhcp-3.0-alpha-19990423.tar.gz > src/Z/dhcp-3.0-alpha-19990423.tar.gz: gzip compressed data, deflated, last modified: Thu Jan 1 10:00:00 1970, os: Unix > 1.43 real 0.96 user 0.38 sys > % /usr/bin/time file -m /tmp/magic src/Z/dhcp-3.0-alpha-19990423.tar.gz > src/Z/dhcp-3.0-alpha-19990423.tar.gz: gzip compressed data, deflated, last modified: Thu Jan 1 10:00:00 1970, os: Unix > 2.15 real 1.62 user 0.44 sys > > PII-266 running 4.0-CURRENT: > % /usr/bin/time file src/Z/dhcp-1.4.0p6.tar.gz > src/Z/dhcp-1.4.0p6.tar.gz: gzip compressed data, deflated, last modified: Wed Mar 3 20:57:52 1999, os: Unix > 0.13 real 0.09 user 0.03 sys > > When I profile file in a slow system (like a 386 or 486), there is an > obvious performance bottleneck: The problem is the memcpy() invoked > from fgets(). The only solution would seem to be to mmap() magic > and parse it, rather than using fgets() to read it. This bottleneck > will also be far more obvious on bandwidth-starved systems (like > 386SX and 486DX2/4), whereas virtually the whole thing fits into the > L2 cache on my P-II. > > Peter > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message --------------8B774876DAB92991344CB5AD Content-Type: text/plain; charset=us-ascii; name="file.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="file.patch" Common subdirectories: file/Magdir and file.new/Magdir diff -c file/apprentice.c file.new/apprentice.c *** file/apprentice.c Wed Jan 28 07:36:21 1998 --- file.new/apprentice.c Wed Jul 21 12:35:21 1999 *************** *** 50,55 **** --- 50,56 ---- static void eatsize __P((char **)); static int maxmagic = 0; + static int alloc_incr = 256; static int apprentice_1 __P((char *, int)); *************** *** 180,188 **** struct magic *m; char *t, *s; - #define ALLOC_INCR 20 if (nd+1 >= maxmagic){ ! maxmagic += ALLOC_INCR; if ((magic = (struct magic *) realloc(magic, sizeof(struct magic) * maxmagic)) == NULL) { --- 181,188 ---- struct magic *m; char *t, *s; if (nd+1 >= maxmagic){ ! maxmagic += alloc_incr; if ((magic = (struct magic *) realloc(magic, sizeof(struct magic) * maxmagic)) == NULL) { *************** *** 192,198 **** else exit(1); } ! memset(&magic[*ndx], 0, sizeof(struct magic) * ALLOC_INCR); } m = &magic[*ndx]; m->flag = 0; --- 192,199 ---- else exit(1); } ! memset(&magic[*ndx], 0, sizeof(struct magic) * alloc_incr); ! alloc_incr *= 2; } m = &magic[*ndx]; m->flag = 0; diff -c file/file.h file.new/file.h *** file/file.h Wed Jul 21 12:37:00 1999 --- file.new/file.h Wed Jul 21 12:35:40 1999 *************** *** 35,41 **** #ifndef HOWMANY # define HOWMANY 8192 /* how much of the file to look at */ #endif ! #define MAXMAGIS 1000 /* max entries in /etc/magic */ #define MAXDESC 50 /* max leng of text description */ #define MAXstring 32 /* max leng of "string" types */ --- 35,41 ---- #ifndef HOWMANY # define HOWMANY 8192 /* how much of the file to look at */ #endif ! #define MAXMAGIS 5000 /* max entries in /etc/magic */ #define MAXDESC 50 /* max leng of text description */ #define MAXstring 32 /* max leng of "string" types */ --------------8B774876DAB92991344CB5AD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 5:15:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id 1312814F76 for ; Wed, 21 Jul 1999 05:15:26 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip232.houston3.tx.pub-ip.psi.net [38.12.169.232]) by leap.innerx.net (Postfix) with ESMTP id C6C51370B4; Wed, 21 Jul 1999 08:15:01 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id HAA01858; Wed, 21 Jul 1999 07:16:24 -0500 (CDT) (envelope-from chris) Date: Wed, 21 Jul 1999 07:16:19 -0500 From: Chris Costello To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.ORG Subject: Re: BSDI binary compatibility Message-ID: <19990721071619.D935@holly.dyndns.org> Reply-To: chris@calldei.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: ; from Dag-Erling Smorgrav on Wed, Jul 21, 1999 at 01:34:13PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 21, 1999, Dag-Erling Smorgrav wrote: > and finally a few static ones Chris Costello was kind enough to build > for me: > > des@des ~/yes/bsdi/cmc/bsdi_static% file hello > hello: ELF 32-bit LSB executable, Intel 80386, version 1, statically linked, not stripped > des@des ~/yes/bsdi/cmc/bsdi_static% ./hello > ELF binary type not known. Use "brandelf" to brand it. > zsh: abort ./hello FYI, I built them under 4.0.1 (if that matters). $ gcc -v gcc version 2.7.2.1 $ ld -v GNU ld version 2.8.1 (with BFD 2.8.1) $ as -v GNU assembler version 2.8.1 (bsd/os), using BFD version 2.8.1 > DES > -- > Dag-Erling Smorgrav - des@yes.no > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- |Chris Costello |A bug in the code is worth two in the documentation. `---------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 6:10:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penrose.isocor.ie (penrose.isocor.ie [194.106.155.117]) by hub.freebsd.org (Postfix) with ESMTP id EB0EC14E2F for ; Wed, 21 Jul 1999 06:10:20 -0700 (PDT) (envelope-from peter.edwards@isocor.ie) Received: from isocor.ie (194.106.155.218) by penrose.isocor.ie; 21 Jul 1999 14:07:32 +0100 Message-ID: <3795C6AB.DE19FCB8@isocor.ie> Date: Wed, 21 Jul 1999 14:10:03 +0100 From: Peter Edwards Organization: ISOCOR X-Mailer: Mozilla 4.6 [en] (X11; I; SunOS 5.6 i86pc) X-Accept-Language: en MIME-Version: 1.0 To: Snob Art Genre , freebsd-hackers@freebsd.org Subject: Re: amandad zombies (fwd) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sounds like (the already fixed) http://www.freebsd.org/cgi/query-pr.cgi?pr=10468 Snob Art Genre wrote: > I will probably send-pr this, do you have anything to add to what I > posted before I do so? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 6:59:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id E6AF314E5E for ; Wed, 21 Jul 1999 06:59:13 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id KAA00687; Wed, 21 Jul 1999 10:00:04 -0400 From: Bill Paul Message-Id: <199907211400.KAA00687@skynet.ctr.columbia.edu> Subject: Re: [FreeBSD-net-jp 1746] [FYI] Adaptec AIC-6915 "Starfire" ethernet controller driver and plus question compaq presario dec et To: morita@jts.ntts.co.jp (morita) Date: Wed, 21 Jul 1999 10:00:03 -0400 (EDT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <000801bed34a$b4e1f360$0f04070a@jts.ntts.co.jp> from "morita" at Jul 21, 99 04:29:01 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1547 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, morita had to walk into mine and say: > $B?9ED$G$9!#(B > > > > These are Adaptec's replacements for its older DEC 21x4x-based multiport > > $B$3$N%I%i%$%P!<$OL5$/$J$k$N$G$7$g$&$+!)(B->DEC 21x4x-based > no more supllyed ->DEC 21x4x-based Sorry, but I'm just a dumb american: I can't read this. > > line of adapters. All cards support 10/100 speeds in full or half duplex. > > The multiport cards consist of multiple AIC-6915 chips linkec via a PCI > > to PCI bridge. Currently I have only tested the ANA-62022 dual port card, > > however all of them should work equally well. The 64-bit cards will work > > in a 32-bit slot on most newer machines. > > > > $B%3%s%Q%C%/!!(BPRESARIO$B!!(B2274$B!!$K(BFreeBSD3.2$B%$%s%9%H!<%k$7$?$N$G$9$,!"(B > NIC$B!'!!(BDEC 21143-based $B$H%S%G%*%+!<%I!'(BSiS5598$B$N@_Dj$,$&$^$/$$$-$^$;$s!"8=:_(B > $BF0$+$7$F$k(B > $BJ}$,$$$i$7$?$i65$($F$/$@$5$$!#(B I can't read this either. :( -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 7:28: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 553AF14DB1 for ; Wed, 21 Jul 1999 07:27:53 -0700 (PDT) (envelope-from kbyanc@alcnet.com) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from kbyanc (ws-41.alcnet.com [63.69.28.41]) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with SMTP id KAA78151; Wed, 21 Jul 1999 10:42:40 -0400 (EDT) From: "Kelly Yancey" To: "Peter Jeremy" Cc: Subject: Date: Wed, 21 Jul 1999 10:39:11 -0400 Message-ID: <002601bed386$cbc33940$291c453f@kbyanc.alcnet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: Peter Jeremy > > "Leif Neland" wrote: > >My 60MHz Pentium, FreeBSD > > > >time file /usr/home/leif/vnc-3.3.2r > >/usr/home/leif/vnc-3.3.2r3_unixsrc.tgz: gzip compressed data, deflated, > >original filename, last modified: Thu Jan 21 19:23:21 1999 > > > >real 0m1.237s > >user 0m0.758s > >sys 0m0.394s > > I can't believe these figures. > > Matthew Dillon wrote: > > Someone would have to compare file sources or profile it to figure > > out what is causing the slowness. > > I can't reproduce the complaint using a 64MB PII-266 running -CURRENT - > there's no evidence of lack of speed, and profiling file(1) doesn't > show any anomolies. > > It is somewhat slower on my 8MB 386, but not unreasonably so: > pc0640% time file src/Z/dhcp-2.0b1pl26.tar.gz > src/Z/dhcp-2.0b1pl26.tar.gz: gzip compressed data, deflated, last > modified: Thu Jan 1 10:00:00 1970, os: Unix > file src/Z/dhcp-2.0b1pl26.tar.gz 1.96s user 0.83s system 98% cpu 2.823 > total > pc0640% > > Note that this is somewhat more than twice the time Leif claimed for > his P-60 - and a P-60 should be more than twice the speed of a > 386SX-25. > > Unfortunately, I can't profile it on my 386: It's running 2.x and I > deleted the profiling libraries due to lack of space. It will happily > run the profiled ELF file(1), but doesn't generate any timing data. > > Looking at ktrace with MALLOC_OPTIONS=U, it does do a lot of > realloc()ing (once for every 20 active lines in .../magic) and sbrk()s > to a maximum size of ~390KB - not really significant. > > All I can think of is that Leif has a problem with his P-60 system. Alright, I'll bite this too: First of all, we are all making the same benchmark? For example, the first time I run: $ time file pm_3.5.3_BSDOS_2.0.tar.Z pm_3.5.3_BSDOS_2.0.tar.Z: compress'd data 16 bits real 0m0.162s user 0m1.086s sys 0m0.060s I get much higher times than when I issue the same a command a second (or more) time: $ time file pm_3.5.3_BSDOS_2.0.tar.Z pm_3.5.3_BSDOS_2.0.tar.Z: compress'd data 16 bits real 0m0.144s user 0m0.090s sys 0m0.053s Presumably the difference come from the first invokation loading all the pages from the magic file into cache which gives the lower numbers on subsequent invokations. I just wanted to make sure before we start pointing fingers. Secondly, to compare with linux (as the original poster did): On FreeBSD 3.2-STABLE from May 18th: $ /usr/bin/time -l file radius_2.0.1_BSDOS_2.0.tar radius_2.0.1_BSDOS_2.0.tar: tar archive 0.14 real 0.09 user 0.04 sys 1140 maximum resident set size 20 average shared memory size 593 average unshared data size 135 average unshared stack size 1411 page reclaims 0 page faults 0 swaps 0 block input operations 0 block output operations 0 messages sent 0 messages received 0 signals received 0 voluntary context switches 2 involuntary context switches And from a RedHat Linux 5.2 (kernel 2.0.36) machine configured with identical hardware (albeit different other processes running at the same time): $ /usr/bin/time -v file radius_2.0.1_Linux_2.0.tar radius_2.0.1_Linux_2.0.tar: tar archive Command being timed: "file radius_2.0.1_Linux_2.0.tar" User time (seconds): 0.03 System time (seconds): 0.00 Percent of CPU this job got: 90% Elapsed (wall clock) time (h:mm:ss or m:ss): 0:00.03 Average shared text size (kbytes): 0 Average unshared data size (kbytes): 0 Average stack size (kbytes): 0 Average total size (kbytes): 0 Maximum resident set size (kbytes): 0 Average resident set size (kbytes): 0 Major (requiring I/O) page faults: 89 Minor (reclaiming a frame) page faults: 169 Voluntary context switches: 0 Involuntary context switches: 0 Swaps: 0 File system inputs: 0 File system outputs: 0 Socket messages sent: 0 Socket messages received: 0 Signals delivered: 0 Page size (bytes): 4096 Exit status: 0 $ /usr/bin/time --portability file radius_2.0.1_Linux_2.0.tar radius_2.0.1_Linux_2.0.tar: tar archive real 0.03 user 0.03 sys 0.01 I find the linux numbers fairly inconsistent between invokations (ie the CPU % fluctuating between 0% and 500%...on a uniprocessor system). The number of faults fluctuated between 2 and about 200 for both "major" and "minor" faults. My favorite is that it reports the process used 0k of memory. :) I can only figure that linux isn't collecting those stats (who really needs to know that anyway :> ) I verified that the inaccurate numbers aren't because of the shortness of the process by using a script to invoke file 100 times...the times were about 100x the values shown, as were the faults, but everything listed as 0 above was still 0. Just FYI: The linux system reports: Mem: 386320K av, 379568K used, 6752K free, 41140K shrd, 5440K buff Swap: 72256K av, 76K used, 72180K free 362108K cached The FreeBSD system reports: Mem: 64M Active, 262M Inact, 31M Wired, 14M Cache, 5222K Buf, 5736K Free Swap: 768M Total, 768M Free I really can't make heads or tails out of all of this, but I'm hoping that I've provided some information to people who could use it. Kelly ~kbyanc@posi.net~ FreeBSD - The Power To Serve - http://www.freebsd.org/ Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 7:57:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id B163B1557F for ; Wed, 21 Jul 1999 07:57:24 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA02076; Wed, 21 Jul 1999 23:56:40 +0900 (JST) Message-ID: <3795DF9B.E11B0F29@newsguy.com> Date: Wed, 21 Jul 1999 23:56:27 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Solaris and Swap Space Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One more technical follow-up. Solaris uses swap files. These can be either regular files or "slice" device files. I couldn't find any comments defining the _exact_ range of possible files, the above are what the documentation uses as example. The swap spaces are defined by a tuple of , which defines the exact position inside the file where the swap is located. Finally, the "swap -s" command, which I used to determine whether the thing overcommits or not, reports *total* memory. The man page explicitly refers to the main memory as a "swap space" for the purpose of "swap -s". Thus, Solaris does, indeed, use a RAM+SWAP model. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Your usefulness to my realm ended the day you made it off Hustaing alive." -- Sun Tzu Liao to his ex-finacee, Isis Marik To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 8: 3:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id C6EED154B5 for ; Wed, 21 Jul 1999 08:03:28 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id LAA91427; Wed, 21 Jul 1999 11:01:42 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Wed, 21 Jul 1999 11:01:41 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.org Subject: Re: BSDI binary compatibility 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 21 Jul 1999, Dag-Erling Smorgrav wrote: > What kinds of BSDI binaries are we supposed to be able to run? I > haven't had any luck getting *any* BSDI binaries to run on my (very > recent) 4.0-CURRENT box. I have a handful of BSDI binaries, some of > which are identified as: > > des@des ~/yes/bsdi/shopsite% file wwwinstall.cgi > wwwinstall.cgi: unknown pure executable > des@des ~/yes/bsdi/shopsite% ./wwwinstall.cgi > zsh: bus error (core dumped) ./wwwinstall.cgi I Have some too, as such: {"/home/green/ast/bin"}$ file ksh ksh: BSD/OS i386 compact demand paged executable not stripped {"/home/green/ast/bin"}$ ./ksh -c 'echo "Hello!"' Hello! > > others (ls and cat from BSDI 4.0): > > des@des ~/yes/bsdi/cmc% file ./ls > ./ls: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically linked, stripped > des@des ~/yes/bsdi/cmc% ./ls > ELF binary type not known. Use "brandelf" to brand it. > zsh: abort ./ls > > and finally a few static ones Chris Costello was kind enough to build > for me: > > des@des ~/yes/bsdi/cmc/bsdi_static% file hello > hello: ELF 32-bit LSB executable, Intel 80386, version 1, statically linked, not stripped > des@des ~/yes/bsdi/cmc/bsdi_static% ./hello > ELF binary type not known. Use "brandelf" to brand it. > zsh: abort ./hello We aren't compatible with BSD/OS ELF in emulation. We've been compatible with their a.out for years, but that's it. It's possible that if you brandelf them to be of type "FreeBSD", they will work. > > DES > -- > Dag-Erling Smorgrav - des@yes.no > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ 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 Wed Jul 21 8:30:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mc-qout4.whowhere.com (mc-qout4.whowhere.com [209.185.123.18]) by hub.freebsd.org (Postfix) with SMTP id 8127B14D56 for ; Wed, 21 Jul 1999 08:30:45 -0700 (PDT) (envelope-from jeffhdz@my-deja.com) Received: from Unknown/Local ([?.?.?.?]) by my-deja.com; Wed Jul 21 08:30:38 1999 To: freebsd-hackers@freebsd.org Date: Wed, 21 Jul 1999 08:30:38 -0700 From: "Jeff Hagendaz" Message-ID: Mime-Version: 1.0 Cc: X-Sent-Mail: off Reply-To: X-Mailer: MailCity Service Subject: polling in device driver X-Sender-Ip: 216.103.85.57 Organization: My Deja Email (http://www.my-deja.com:80) Content-Type: text/plain; charset=us-ascii Content-Length: 590 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am reading a Linux device driver. At some point it polls a device to check if it is ready. The timeout is set to 5 second. It uses the system jiffies to count the time: u32 time_out = jiffies + 5 * HZ; for (;;) { /* code to check if dev is ready */ ........ if (ready) break; if (intr_count == 0) schedule(); if (jiffies > time_out) return ERROR; } How do I implement such polling in FreeBSD? Thanks. --Jeff --== Sent via Deja.com http://www.deja.com/ ==-- Share what you know. Learn what you don't. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 8:34:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id A619E14D56 for ; Wed, 21 Jul 1999 08:34:28 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA28960; Wed, 21 Jul 1999 08:32:11 -0700 (PDT) (envelope-from dillon) Date: Wed, 21 Jul 1999 08:32:11 -0700 (PDT) From: Matthew Dillon Message-Id: <199907211532.IAA28960@apollo.backplane.com> To: Wes Peters Cc: Jaye Mathisen , Modred , Vincent Poy , sthaug@nethelp.no, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? References: <199907210733.AAA25177@apollo.backplane.com> <3795DD5E.2F71FBFB@softweyr.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Unmanaged layer 2 switches do that, but the "intelligent" layer 3 switches :certainly don't. Layer 3 switches can be configured to consider 2 physically :adjacent ports to be on completely different networks; they will not even :share broadcast traffic. If you shop carefully, you can even buy switches :where you can configure VLANs based on user authentication, any given :physical port can join a VLAN based on a user login program rather than :port number or MAC or IP address. : :Wes Peters Softweyr LLC :http://softweyr.com/ wes@softweyr.com I would *never* *ever* configure a switch with dynamic VLANs. Not even if my life depended on it. It would be impossible to track down problems. It's hard enough keeping the network topology straight with statically configured VLANs. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 8:35:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 18A07154C9 for ; Wed, 21 Jul 1999 08:35:56 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA28994; Wed, 21 Jul 1999 08:35:24 -0700 (PDT) (envelope-from dillon) Date: Wed, 21 Jul 1999 08:35:24 -0700 (PDT) From: Matthew Dillon Message-Id: <199907211535.IAA28994@apollo.backplane.com> To: Peter Edwards Cc: Peter Jeremy , will@iki.fi, hackers@FreeBSD.ORG Subject: Re: speed of file(1) References: <99Jul21.210648est.40326@border.alcanet.com.au> <3795B50B.EFBBEFE2@isocor.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nice rundown of the problem! I presume someone is going to commit this... -Matt Matthew Dillon :*** file/apprentice.c Wed Jan 28 07:36:21 1998 :--- file.new/apprentice.c Wed Jul 21 12:35:21 1999 :*************** :*** 50,55 **** :--- 50,56 ---- : static void eatsize __P((char **)); : : static int maxmagic = 0; :... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 8:36:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from houston.matchlogic.com (houston.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id 55219154CE for ; Wed, 21 Jul 1999 08:36:21 -0700 (PDT) (envelope-from crandall@matchlogic.com) Received: by houston.matchlogic.com with Internet Mail Service (5.5.2448.0) id ; Wed, 21 Jul 1999 09:36:17 -0600 Message-ID: <64003B21ECCAD11185C500805F31EC0302D7598C@houston.matchlogic.com> From: Charles Randall To: hackers@FreeBSD.ORG Subject: RE: speed of file(1) Date: Wed, 21 Jul 1999 09:36:16 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When this gets committed, can it be applied to both the 3.x and 4.x trees? Thanks, Charles -----Original Message----- From: Peter Edwards [mailto:peter.edwards@isocor.ie] Sent: Wednesday, July 21, 1999 5:55 AM To: Peter Jeremy Cc: will@iki.fi; hackers@FreeBSD.ORG Subject: Re: speed of file(1) A quick look at the source reveals: A MAXMAGIS constant in file.h that estimates a limit of 1000 lines in magic. (The real number is 4802) An array sized on MAXMAGIS, that is reallocated every ALLOC_INTR lines of magic once MAXMAGIS is exceeded. The patch updates MAXMAGIS to 5000 (give a bit of room to grow) And makes ALLOC_INCR a variable that is bigger, and doubles every time it is used, to attenuate the problem if there ever ends up being 10000 entries in magic. Results on a 90Mhz Pentium: new verson time ./file ./file ./file: FreeBSD/i386 compact demand paged dynamically linked executable not stripped 0.14 real 0.11 user 0.02 sys old verson: ./file: FreeBSD/i386 compact demand paged dynamically linked executable not stripped 0.79 real 0.60 user 0.16 sys -- Peter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 8:55: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from voyager.fisicc-ufm.edu (ip-46-094.guate.net [200.12.46.94]) by hub.freebsd.org (Postfix) with ESMTP id AA8AE14E60 for ; Wed, 21 Jul 1999 08:54:19 -0700 (PDT) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id JAA01758; Wed, 21 Jul 1999 09:47:11 -0600 (CST) (envelope-from obonilla) Date: Wed, 21 Jul 1999 09:47:11 -0600 From: Oscar Bonilla To: Kris Kennaway Cc: "David E. Cross" , Oscar Bonilla , Joe Abley , Wes Peters , Mike Smith , Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD Message-ID: <19990721094711.C1520@fisicc-ufm.edu> References: <199907201520.LAA29350@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Kris Kennaway on Wed, Jul 21, 1999 at 01:46:56AM +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 21, 1999 at 01:46:56AM +0930, Kris Kennaway wrote: > It looks like we've got some good concurrent projects happening at the > moment - markm and co working on PAM, the nsswitch.conf project you're > talking about, and the stuff I'm working on with modularizing crypt() and > supporting per-login class password hashes (I've rewritten the library > since I last posted about it and expect to have my code cleaned up by > tomorrow night for another snapshot). > > The thing to make sure is that we don't tread on each other's toes, and > basically that we look for the big picture and how all these projects fit > together. Ok, here goes my understanding of how things should be, please correct me if i'm wrong. There are three parts to the problem: 1. Where do we get the databases from? I mean, where do we get passwd, group, hosts, ethers, etc from. This should be handled by a name service switch a la solaris. Basically we want to be able to tell the system for each individual database where to get the stuff from. We can add entries for each database in the system. 2. How to authorize the user? I mean, what sort of authentication should we use to decide if the user should be allowed in. This should be handled by PAM. 3. What password hash should we use when we have the username and the password hash? This should be handled by the new modularized crypt. Do we want to be able to tell the system where to get its pam.conf and login.conf from? This would mean having a pam.conf and login.conf entry in nsswitch.conf. Can we make a list of stuff that needs to be done to make this possible? Something like a tasklist would be good. a) design and implement a name service switch. b) make libc aware of the name service switch. c) ??? then we should detail each step... Regards, -Oscar -- For PGP Public Key: finger obonilla@fisicc-ufm.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 9: 5:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id C935214DB1 for ; Wed, 21 Jul 1999 09:05:49 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA17700; Thu, 22 Jul 1999 01:01:11 +0900 (JST) Message-ID: <3795EEB9.1A21EEA@newsguy.com> Date: Thu, 22 Jul 1999 01:00:57 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Oscar Bonilla Cc: Kris Kennaway , "David E. Cross" , Joe Abley , Wes Peters , Mike Smith , Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD References: <199907201520.LAA29350@cs.rpi.edu> <19990721094711.C1520@fisicc-ufm.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oscar Bonilla wrote: > > There are three parts to the problem: > > 1. Where do we get the databases from? I mean, where do we get passwd, group, > hosts, ethers, etc from. > > This should be handled by a name service switch a la solaris. Basically > we want to be able to tell the system for each individual database where > to get the stuff from. We can add entries for each database in the system. I perceive here an unfair biasing toward nss. Someone mentioned defining where to get the passwords from based on the login class. This is a very interesting option, that doesn't seem to be well served by nss. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Your usefulness to my realm ended the day you made it off Hustaing alive." -- Sun Tzu Liao to his ex-finacee, Isis Marik To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 9: 6:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id DF169154FB for ; Wed, 21 Jul 1999 09:06:29 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id KAA03304; Wed, 21 Jul 1999 10:03:14 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199907211603.KAA03304@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Wilko Bulte Cc: gibbs@plutotech.com (Justin T. Gibbs), hackers@FreeBSD.ORG Subject: Re: any docs on how to use bus_dma_tag_create e.a. ? In-reply-to: Your message of "Tue, 20 Jul 1999 22:37:47 +0200." <199907202037.WAA00801@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Jul 1999 10:03:14 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> bus_dma related stuff is only required if the device has a DMA engine >> you wish to use. To access the shared memory on the card (e.g. map > >Eh, sorry, I was confused. It has *both* shared memory and a DMA engine. > >> it into the kernel's virtual address space), you will need to use >> the resource manager and bus space. > >Do you by chance have an example (maybe in -current somewhere) of the >shared memory stuff? I found some DMA stuff in ahc_pci.c: > > /* Allocate a dmatag for our SCB DMA maps */ > /* XXX Should be a child of the PCI bus dma tag */ > error = bus_dma_tag_create(/*parent*/NULL, A parent tag would indicate the restrictions of any parent bridge between the device you are talking to and CPU memory. We haven't modified the new bus code yet to pass through this information, so just leave it NULL for now. /*alignment*/1, Any alignment constraints on the target memory region of a DMA specified in bytes. If the allocation must be 32bit aligned, you would specify 4. > /*boundary*/0, Any boundary constraints on the target memory region of a DMA, for instance if the DMA cannot cross a 64k boundary, you would set this to 64K. > /*lowaddr*/BUS_SPACE_MAXADDR_32BIT, > /*highaddr*/BUS_SPACE_MAXADDR, low and high address of the region that the DMA engine cannot access. > /*filter*/NULL, /*filterarg*/NULL, If the device's DMA constraints cannot be specified with a single region, you must specify a region that encompasses all such regions and specify a filter function to provide a finer level of control. > /*maxsize*/MAXBSIZE, Maximum DMA transfer size. > /*nsegments*/AHC_NSEG, Maximum number of discontinuities in the mapped region. > /*maxsegsz*/AHC_MAXTRANSFER_SIZE, Maximum size of a segment. maxsize <= nsegments * maxsegsz. > /*flags*/BUS_DMA_ALLOCNOW Allocate all necessary resources to handle a single mapping for this tag at the time the tag is created. >Most (?) drivers seem to use the older framework (can I distinguish >those by COMPAT_PCI_DRIVER() ?). You should use the new API if possible. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 9: 6:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 10C2614DB1 for ; Wed, 21 Jul 1999 09:06:39 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id JAA04465; Wed, 21 Jul 1999 09:04:15 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA71266; Wed, 21 Jul 1999 09:04:14 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 21 Jul 1999 09:04:14 -0700 (PDT) Message-Id: <199907211604.JAA71266@vashon.polstra.com> To: crossd@cs.rpi.edu Subject: Re: linking question... In-Reply-To: <199907210557.BAA43815@cs.rpi.edu> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199907210557.BAA43815@cs.rpi.edu>, David E. Cross wrote: > > The problem indeed was conflicting libraries... (in /usr/X11R6/lib).. however > I did place on the line *immediately* before the -lwcs a -L/usr/local/lib, > however it appeared to take the /usr/X11R6/lib (which was in a previous -L > statement) version instead. Is this correct? Yes, it's correct. The -L options can appear anywhere relative to the -l options -- even after them -- and it doesn't make any difference. The relative ordering among the -L options with respect to *each other* is all ld cares about. That's been the traditional behavior on every Unix system I've ever used that supported -L at all. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 9:14:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from voyager.fisicc-ufm.edu (ip-46-094.guate.net [200.12.46.94]) by hub.freebsd.org (Postfix) with ESMTP id 92A9C154DA for ; Wed, 21 Jul 1999 09:13:39 -0700 (PDT) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id KAA03151; Wed, 21 Jul 1999 10:06:53 -0600 (CST) (envelope-from obonilla) Date: Wed, 21 Jul 1999 10:06:53 -0600 From: Oscar Bonilla To: "Daniel C. Sobral" Cc: Oscar Bonilla , Kris Kennaway , "David E. Cross" , Joe Abley , Wes Peters , Mike Smith , Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD Message-ID: <19990721100653.D1520@fisicc-ufm.edu> References: <199907201520.LAA29350@cs.rpi.edu> <19990721094711.C1520@fisicc-ufm.edu> <3795EEB9.1A21EEA@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <3795EEB9.1A21EEA@newsguy.com>; from Daniel C. Sobral on Thu, Jul 22, 1999 at 01:00:57AM +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 22, 1999 at 01:00:57AM +0900, Daniel C. Sobral wrote: > Oscar Bonilla wrote: >> >> There are three parts to the problem: >> >> 1. Where do we get the databases from? I mean, where do we get passwd, group, >> hosts, ethers, etc from. >> >> This should be handled by a name service switch a la solaris. Basically >> we want to be able to tell the system for each individual database where >> to get the stuff from. We can add entries for each database in the system. > > I perceive here an unfair biasing toward nss. Someone mentioned > defining where to get the passwords from based on the login class. > This is a very interesting option, that doesn't seem to be well > served by nss. > I was actually talking about the "other" entries. usename:uid:gid:gecos:home:shell where does PAM fit in the schema you talk about? would we need to make PAM login.conf aware then? Where do we get login.conf from? from nsswitch.conf? Regards, -Oscar -- For PGP Public Key: finger obonilla@fisicc-ufm.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 9:17:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id B3C4F154E3 for ; Wed, 21 Jul 1999 09:17:21 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 116z36-00062c-00 for hackers@freebsd.org; Wed, 21 Jul 1999 18:16:52 +0200 From: Sheldon Hearn To: hackers@freebsd.org Subject: MLINKS for select(2) FD_* macros Date: Wed, 21 Jul 1999 18:16:52 +0200 Message-ID: <23225.932573812@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, Would it be inappropriate to add select.2 MLINKS for FD_SET, FD_CLR, FD_ISSET and FD_ZERO? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 9:18:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ezln23.earthbroadcasting.com (ezln23.thedial.com [207.135.131.130]) by hub.freebsd.org (Postfix) with ESMTP id A4925154DA for ; Wed, 21 Jul 1999 09:18:49 -0700 (PDT) (envelope-from chris@thedial.com) Received: from thedial.com (localhost.earthbroadcasting.com [127.0.0.1]) by ezln23.earthbroadcasting.com (8.9.3/8.9.3) with ESMTP id KAA25133; Wed, 21 Jul 1999 10:17:44 -0600 (MDT) (envelope-from chris@thedial.com) Message-ID: <3795F2A8.8D2E62AC@thedial.com> Date: Wed, 21 Jul 1999 10:17:44 -0600 From: Christopher Taylor X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-questions@feebsd.org Subject: xmms port broken Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yesterday, I updated my ports tree with cvsup...I then attempted to make the audio/xmms port and received the following error... [root@ezln23 xmms]# make ===> Extracting for xmms-0.9.1 >> Checksum OK for xmms-0.9.1.tar.gz. ===> xmms-0.9.1 depends on executable: libtool - found ===> xmms-0.9.1 depends on shared library: gtk12.2 - not found ===> Verifying install for gtk12.2 in /usr/ports/x11-toolkits/gtk12 ===> Returning to build of xmms-0.9.1 Error: shared library "gtk12.2" does not exist *** Error code 1 gtk12.2 _does_ exist on my system... after symlinking gtk-config and glib-config to gtk12-config and glib12-config, resectively, I was able to compile xmms by hand. However, it still gives me the same error if I try and install the xmms port. A side note...xmms plays audio fine, but the player is slow to respond to mouse clicks... --Chris -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Christopher Taylor Technical Director Earth Broadcasting Corporation (EBC) 415 East 200 South Salt Lake City, Utah 84111 phone: (801) 322-3949 cell: (801) 541-8287 email: chris@thedial.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 9:26:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay01.indigo.ie (relay01.indigo.ie [194.125.133.225]) by hub.freebsd.org (Postfix) with SMTP id 8694615585 for ; Wed, 21 Jul 1999 09:26:47 -0700 (PDT) (envelope-from niall@pobox.com) Received: (qmail 707 messnum 238427 invoked from network[194.125.205.162/ts08-035.dublin.indigo.ie]); 21 Jul 1999 16:26:46 -0000 Received: from ts08-035.dublin.indigo.ie (HELO pobox.com) (194.125.205.162) by relay01.indigo.ie (qp 707) with SMTP; 21 Jul 1999 16:26:46 -0000 Message-ID: <37960FEF.E6DBD6C0@pobox.com> Date: Wed, 21 Jul 1999 18:22:39 +0000 From: Niall Smart X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Oscar Bonilla Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD References: <199907201520.LAA29350@cs.rpi.edu> <19990721094711.C1520@fisicc-ufm.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ CC list nuked ] > Ok, here goes my understanding of how things should be, please correct me > if i'm wrong. > > There are three parts to the problem: > > 1. Where do we get the databases from? I mean, where do we get passwd, group, > hosts, ethers, etc from. > > This should be handled by a name service switch a la solaris. Basically > we want to be able to tell the system for each individual database where > to get the stuff from. We can add entries for each database in the system. Not so much as "where do we get the databases from" as "which databases hold data for this particular service". For example DNS can store information for the hosts service (i.e. nameserver service) but could also store crytographic keys which could be used for as host keys for ssh for example. The service has a standard API (gethostbyname() for example, or getpwnam()) which can search through multiple disparate database types. (I may be mixing my terminology up here, it may be more conventional to say "which services support this database", where the database might be a load of struct pw for example, but hopefully its clear I mean) Each particular database type might have its own configuration file. Taking the "hosts" service for example, the configuration file for the DNS database is /etc/resolv.conf and there is no configuration for the files database (which uses /etc/hosts) > 2. How to authorize the user? I mean, what sort of authentication should we > use to decide if the user should be allowed in. > > This should be handled by PAM. Yes, although login programs would require that a) getpwnam returns non-NULL and b) pam_authenticate returns PAM_SUCCESS. > 3. What password hash should we use when we have the username and the > password hash? > > This should be handled by the new modularized crypt. This is a function of the pam_unix module, a PAM module can use smartcards, retina scanners, body odour detectors etc etc, so it may not use password hashes at all. Each PAM module may have its own configuration file to tell it which serial port the smartcard reader is on for example. Regards, Niall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 9:27:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rebel.net.au (rebel.rebel.net.au [203.20.69.66]) by hub.freebsd.org (Postfix) with ESMTP id 4B239154F4 for ; Wed, 21 Jul 1999 09:27:29 -0700 (PDT) (envelope-from kkenn@rebel.net.au) Received: from 203.20.69.79 (dialup-9.rebel.net.au [203.20.69.79]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id BAA11312 for ; Thu, 22 Jul 1999 01:57:21 +0930 Received: (qmail 8564 invoked from network); 21 Jul 1999 16:27:25 -0000 Received: from localhost (kkenn@127.0.0.1) by localhost with SMTP; 21 Jul 1999 16:27:25 -0000 Date: Thu, 22 Jul 1999 01:57:22 +0930 (CST) From: Kris Kennaway Reply-To: kkenn@rebel.net.au To: Christopher Taylor Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: xmms port broken In-Reply-To: <3795F2A8.8D2E62AC@thedial.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Jul 1999, Christopher Taylor wrote: > Date: Wed, 21 Jul 1999 10:17:44 -0600 > From: Christopher Taylor > To: freebsd-hackers@FreeBSD.ORG, freebsd-questions@feebsd.org > Subject: xmms port broken You guessed wrong on both mailing lists. Problems with freebsd ports go to freebsd-ports ;-) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 9:33:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id C0123154F4 for ; Wed, 21 Jul 1999 09:33:34 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 116zJ3-00065t-00; Wed, 21 Jul 1999 18:33:21 +0200 From: Sheldon Hearn To: Poul-Henning Kamp Cc: freebsd-hackers@freebsd.org Subject: Re: cvs commit: src/usr.sbin/inetd inetd.c In-reply-to: Your message of "Wed, 21 Jul 1999 18:15:09 +0200." <25763.932573709@critter.freebsd.dk> Date: Wed, 21 Jul 1999 18:33:21 +0200 Message-ID: <23428.932574801@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Hi-jacked from cvs-committers and cvs-all] On Wed, 21 Jul 1999 18:15:09 +0200, Poul-Henning Kamp wrote: > There is another one you may want to look at, I have not figured it > out yet: > > I try to start a ntpd from /etc/rc.local this way: > > nohup /usr/local/bin/ntpd -d -d > /usr/ntp/x.ntpd 2>&1 & > >and it invariably ends up dead in a few seconds with: > Jul 17 12:26:39 bogon ntpd[248]: ntpd exiting on signal 1 Can nohup really prevent processes from trapping SIGHUP? I thought it just set the SIGUP handler to discard and hoped for the best. Xntpd in the base system explicitly requests its graceful termination function, called finish(), be loaded as the SIGHUP handler. What is it you'd like? 1) nohup should prevent processes from trapping SIGHUP. 2) xntpd should reconfigure on SIGHUP. 3) xntpd is getting a SIGHUP and you're not sure where from. 4) xntpd is different from the port's ntpd in some way that should change. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 9:39: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id F07A1154FF for ; Wed, 21 Jul 1999 09:38:52 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA29468; Wed, 21 Jul 1999 09:37:18 -0700 (PDT) (envelope-from dillon) Date: Wed, 21 Jul 1999 09:37:18 -0700 (PDT) From: Matthew Dillon Message-Id: <199907211637.JAA29468@apollo.backplane.com> To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: understanding code related to forced COW for debugger References: <37952EBF.3960E7D4@cs.binghamton.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I have tried to understand the following code in vm_map_lookup() without :much success: : : if (fault_type & VM_PROT_OVERRIDE_WRITE) : prot = entry->max_protection; : else : prot = entry->protection; : ........ : : if (entry->wired_count && (fault_type & VM_PROT_WRITE) && : (entry->eflags & MAP_ENTRY_COW) && : (fault_typea & VM_PROT_OVERRIDE_WRITE) == 0) { : RETURN(KERN_PROTECTION_FAILURE); : } : :At first, it seems to me that if you want to write a COW page, you must :have OVERRIDE_WRITE set. The VM_PROT_OVERRIDE_WRITE flag is only used for user-wired pages, so it does not effect 'normal' page handling. Look carefully at the vm_fault() code (vm/vm_fault.c line 212), that lookup only occurs with VM_PROT_OVERRIDE_WRITE set if the normal lookup fails and the user has wired the page. So if a normal lookup fails and this is a user-wired page, we try the lookup again with VM_PROT_OVERRIDE_WRITE, presumably to handle a faked copy-on-write fault for the debugger. This results in the following: First, we temporarily increase the protections to make the page *appear* writeable. Note: only 'appear' writeable, not actually be writeable. if (fault_type & VM_PROT_OVERRIDE_WRITE) prot = entry->max_protection; else prot = entry->protection; Next we strip off only the fault bits that we care about. Note that we have already adjusted 'prot' based on the VM_PROT_OVERRIDE_WRITE flag so 'prot' is probably writeable. We will thus fall through this conditional: fault_type &= (VM_PROT_READ|VM_PROT_WRITE|VM_PROT_EXECUTE); if ((fault_type & prot) != fault_type) { RETURN(KERN_PROTECTION_FAILURE); } If this is part of a user wire and we have a write fault and the page is copy-on-write, *AND* VM_PROT_OVERRIDE_WRITE was not set, we return a failure. This is, in fact, the failure that is returned when the vm_fault code initially attempts to do the lookup before vm_fault falls through and makes a second attempt with VM_PROT_OVERRIDE_WRITE. if (entry->wired_count && (fault_type & VM_PROT_WRITE) && (entry->eflags & MAP_ENTRY_COW) && (fault_typea & VM_PROT_OVERRIDE_WRITE) == 0) { RETURN(KERN_PROTECTION_FAILURE); } Now that we've gotten past this code we revert the protection bits if the page is a user-wire, because it was because the page was a user wire (indirectly, anyway) that the protections were increased in the first place. We lose the entry->max_protection and revert back to entry->protection. Essentially, we make the page (probably) read-only again. *wired = (entry->wired_count != 0); if (*wired) prot = fault_type = entry->protection; ... but we've already gotten past the conditionals that can cause a failure to be returned, so the code that follows will *still* do the copy-on-write for the debugger. :But later I find that when wired_count is non zero, we are actually :simulating a page fault, not a real one. :Anyway, I do not know how the above code (1) prevents a debugger from :writing a binary code, (2) forces :a COW when a debugger write other data. : :I also have some questions on wiring a page: : :(1) According to the man pages of mlock(2), a wired page can still :cause protection-violation faults. :But in the same vm_map_lookup(), we have the following code: : : if (*wired) : prot = fault_type = entry->protection; : :and the comment says "get it for all possible accesses". As I undersand :it, we wire a page by simulating :a page fault (no matter whether it is kernel or user who is wiring a :page). I'm pretty sure this piece is simply reverting the mess that the copy-on-write stuff does for the debugger. entry->protection is what we normally want to use. The debugger copy-on-write junk is there so the debugger can modify a program's TEXT area but the program itself *cannot* modify its own TEXT area. It's a big mess and I don't fully understand how the structures are faked up to handle the case. :(2) Can the kernel wire a page of a user process without that user's :request (by calling mlock)? : :Any help is appreciated. Yes. The kernel can wire a page. It usually busies the page for the duration, however, so vm_fault will block on the page and then retry without actually noticing that the page has been wired. I'm probably not entirely correct here, John may be able to say more about it. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 9:40:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id C2C6E15547; Wed, 21 Jul 1999 09:39:13 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 116zO4-00067V-00; Wed, 21 Jul 1999 18:38:32 +0200 From: Sheldon Hearn To: Christopher Taylor Cc: ports@freebsd.org Subject: Re: xmms port broken Date: Wed, 21 Jul 1999 18:38:05 +0200 Message-ID: <23518.932575085@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Hijacked from freebsd-hackers and freebsd-questions] Hi Chris, You've cross-posted this message to two inappropriate lists. The freebsd-ports mailing list is what you really wanted. A copy of this message (with your original question intact) has been sent to that list on your behalf. Ciao, Sheldon. ------- Forwarded Message Message-ID: <3795F2A8.8D2E62AC@thedial.com> Date: Wed, 21 Jul 1999 10:17:44 -0600 From: Christopher Taylor To: freebsd-hackers@FreeBSD.ORG, freebsd-questions@feebsd.org Subject: xmms port broken Yesterday, I updated my ports tree with cvsup...I then attempted to make the audio/xmms port and received the following error... [root@ezln23 xmms]# make ===> Extracting for xmms-0.9.1 >> Checksum OK for xmms-0.9.1.tar.gz. ===> xmms-0.9.1 depends on executable: libtool - found ===> xmms-0.9.1 depends on shared library: gtk12.2 - not found ===> Verifying install for gtk12.2 in /usr/ports/x11-toolkits/gtk12 ===> Returning to build of xmms-0.9.1 Error: shared library "gtk12.2" does not exist *** Error code 1 gtk12.2 _does_ exist on my system... after symlinking gtk-config and glib-config to gtk12-config and glib12-config, resectively, I was able to compile xmms by hand. However, it still gives me the same error if I try and install the xmms port. A side note...xmms plays audio fine, but the player is slow to respond to mouse clicks... - --Chris - -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Christopher Taylor Technical Director Earth Broadcasting Corporation (EBC) 415 East 200 South Salt Lake City, Utah 84111 phone: (801) 322-3949 cell: (801) 541-8287 email: chris@thedial.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message ------- End of Forwarded Message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 9:45:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 5291B154D7 for ; Wed, 21 Jul 1999 09:45:12 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA25903; Wed, 21 Jul 1999 18:42:46 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Sheldon Hearn Cc: freebsd-hackers@freebsd.org Subject: Re: cvs commit: src/usr.sbin/inetd inetd.c In-reply-to: Your message of "Wed, 21 Jul 1999 18:33:21 +0200." <23428.932574801@axl.noc.iafrica.com> Date: Wed, 21 Jul 1999 18:42:45 +0200 Message-ID: <25901.932575365@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The point was who the heck sends the SIGHUP and why ? Poul-Henning In message <23428.932574801@axl.noc.iafrica.com>, Sheldon Hearn writes: > >[Hi-jacked from cvs-committers and cvs-all] > >On Wed, 21 Jul 1999 18:15:09 +0200, Poul-Henning Kamp wrote: > >> There is another one you may want to look at, I have not figured it >> out yet: >> >> I try to start a ntpd from /etc/rc.local this way: >> >> nohup /usr/local/bin/ntpd -d -d > /usr/ntp/x.ntpd 2>&1 & >> >>and it invariably ends up dead in a few seconds with: > >> Jul 17 12:26:39 bogon ntpd[248]: ntpd exiting on signal 1 > >Can nohup really prevent processes from trapping SIGHUP? I thought it >just set the SIGUP handler to discard and hoped for the best. > >Xntpd in the base system explicitly requests its graceful termination >function, called finish(), be loaded as the SIGHUP handler. > >What is it you'd like? > > 1) nohup should prevent processes from trapping SIGHUP. > 2) xntpd should reconfigure on SIGHUP. > 3) xntpd is getting a SIGHUP and you're not sure where from. > 4) xntpd is different from the port's ntpd in some way that > should change. > >Ciao, >Sheldon. > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 9:57:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 852BA15528 for ; Wed, 21 Jul 1999 09:57:38 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id CAA29303; Thu, 22 Jul 1999 02:54:57 +1000 Date: Thu, 22 Jul 1999 02:54:57 +1000 From: Bruce Evans Message-Id: <199907211654.CAA29303@godzilla.zeta.org.au> To: phk@critter.freebsd.dk, sheldonh@uunet.co.za Subject: Re: cvs commit: src/usr.sbin/inetd inetd.c Cc: freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Can nohup really prevent processes from trapping SIGHUP? I thought it >just set the SIGUP handler to discard and hoped for the best. It's normally a bug to catch ignored signals. Daomons that reread config files when they receive a signal may be counterexamples. OTOH, they probably shouldn't be started with some signals ignored unless ignoring those signals is really wanted. >Xntpd in the base system explicitly requests its graceful termination >function, called finish(), be loaded as the SIGHUP handler. This seems to be just a bug. finish() is used for SIGHUP, SIGINT, SIGQUIT and SIGTERM. finish() just finishes (actually it has undefined behaviour since it calls exit()), so nothing except undefined behaviour is lost by ignoring these signals. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 9:59:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from voyager.fisicc-ufm.edu (ip-46-094.guate.net [200.12.46.94]) by hub.freebsd.org (Postfix) with ESMTP id 233281557D for ; Wed, 21 Jul 1999 09:58:30 -0700 (PDT) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id KAA26826; Wed, 21 Jul 1999 10:57:24 -0600 (CST) (envelope-from obonilla) Date: Wed, 21 Jul 1999 10:57:24 -0600 From: Oscar Bonilla To: Niall Smart Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD Message-ID: <19990721105724.F1520@fisicc-ufm.edu> References: <199907201520.LAA29350@cs.rpi.edu> <19990721094711.C1520@fisicc-ufm.edu> <37960FEF.E6DBD6C0@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <37960FEF.E6DBD6C0@pobox.com>; from Niall Smart on Wed, Jul 21, 1999 at 06:22:39PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 21, 1999 at 06:22:39PM +0000, Niall Smart wrote: > [ CC list nuked ] good! :) >> Ok, here goes my understanding of how things should be, please correct me >> if i'm wrong. >> >> There are three parts to the problem: >> >> 1. Where do we get the databases from? I mean, where do we get passwd, group, >> hosts, ethers, etc from. >> >> This should be handled by a name service switch a la solaris. Basically >> we want to be able to tell the system for each individual database where >> to get the stuff from. We can add entries for each database in the system. > > Not so much as "where do we get the databases from" as "which databases > hold data for this particular service". For example DNS can store > information for the hosts service (i.e. nameserver service) but could > also > store crytographic keys which could be used for as host keys for ssh for > example. The service has a standard API (gethostbyname() for example, > or > getpwnam()) which can search through multiple disparate database types. > > (I may be mixing my terminology up here, it may be more conventional > to say "which services support this database", where the database > might be a load of struct pw for example, but hopefully its clear I > mean) > > Each particular database type might have its own configuration file. > Taking the "hosts" service for example, the configuration file for > the DNS database is /etc/resolv.conf and there is no configuration > for the files database (which uses /etc/hosts) Agreed. How would the sysadmin configure the stuff? I mean, our design should be flexible enough to allow for the kind of stuff you're talking about. I personally would like to be able to configure everything in the system the following way: $ cat /etc/nsswitch.conf passwd= ldap files hosts= dns files group= ldap files traditional service = where db to get it from here passwd means stuff that's in struct passwd hosts meand hostname to IP mapping, and so on. $ cat /etc/ldap.conf host= ldap.fisicc-ufm.edu basedn= ou=staff, dc=fisicc-ufm, dc=edu username= uid passwd= userPassword uid= userId gid= groupId home= userHome shell= defaultShell this would be all the ldap configuration stuff, for instance, how to map the struct passwd entries to the ldap records. $ cat /etc/resolv.conf usual dns configuration stuff so we would end up having a singe configuration file (nsswitch.conf) telling the system where to get the info from and then individual configuration files telling the system how to configure each individual service. now... would we want to be able to pull this individual configuration files from a certain service? could I have /etc/resolv.conf pulled from ldap for example? > >> 2. How to authorize the user? I mean, what sort of authentication should we >> use to decide if the user should be allowed in. >> >> This should be handled by PAM. > > Yes, although login programs would require that a) getpwnam returns > non-NULL and b) pam_authenticate returns PAM_SUCCESS. > this is what started the thread. I installed a pam_ldap module only to find out that login wouldn't let the user in because getpwnam returned NULL (not found on /etc/passwd). I then asked: "what would happen if login were to succeed, but once the user has logged in he/she doesn't have a username to uid mapping?" >> 3. What password hash should we use when we have the username and the >> password hash? >> >> This should be handled by the new modularized crypt. > > This is a function of the pam_unix module, a PAM module can > use smartcards, retina scanners, body odour detectors etc etc, > so it may not use password hashes at all. Each PAM module may > have its own configuration file to tell it which serial port the > smartcard reader is on for example. I don't see where the modularized crypt would fit in then... i totally agree that pam has this capability i was just trying to fit in the crypt stuff people have been working on. do I make sense? Regards, -Oscar -- For PGP Public Key: finger obonilla@fisicc-ufm.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 10:18:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 039E414CC0 for ; Wed, 21 Jul 1999 10:18:18 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id KAA46894; Wed, 21 Jul 1999 10:14:51 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Wed, 21 Jul 1999 10:14:51 -0700 (PDT) From: Vincent Poy To: Wes Peters Cc: Matthew Dillon , Jaye Mathisen , Modred , sthaug@nethelp.no, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? In-Reply-To: <3795DD5E.2F71FBFB@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Jul 1999, Wes Peters wrote: > Matthew Dillon wrote: > > > > :Perhaps I'm missing something obvious, but since switches forward packets > > :selectively per port, I would think it would be hard to sniff packets on > > :any port, w/o administrative access to the switch to tell it to mirror > > :data to a different port. > > : > > :ie, if I'm plugged into port 1, I can't see traffic on a switch on port 2 > > :except for broadcast traffic... > > > > The switch routes traffic based on its ARP cache. While you cannot > > easily monitor another port's traffic, you can take over its MAC address > > and steal its traffic. > > Unmanaged layer 2 switches do that, but the "intelligent" layer 3 switches > certainly don't. Layer 3 switches can be configured to consider 2 physically > adjacent ports to be on completely different networks; they will not even > share broadcast traffic. If you shop carefully, you can even buy switches > where you can configure VLANs based on user authentication, any given > physical port can join a VLAN based on a user login program rather than > port number or MAC or IP address. Speaking about Layer 2 and layer 3. Does the Cisco Catalyst 2924XL and the HP ProCurve 2424M and 4000M switches fall under Layer 3 or just layer 2? Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 10:25:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 565FB15515 for ; Wed, 21 Jul 1999 10:25:53 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-1-42.ucdavis.edu [169.237.16.42]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA45760 for ; Wed, 21 Jul 1999 10:25:40 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id KAA09013 for hackers@freebsd.org; Wed, 21 Jul 1999 10:25:38 -0700 (PDT) (envelope-from obrien) Date: Wed, 21 Jul 1999 10:25:34 -0700 From: "David O'Brien" To: hackers@freebsd.org Subject: Will FreeBSD ever see native IPv6 ?? Message-ID: <19990721102534.A8848@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So is FreeBSD *EVER* going to see native IPv6 ?? I attended a talk by a group of Intrusion Detection researchers. They were basing their research on FreeBSD because they needed divert sockets and found FreeBSD worked perfectly for this in this respect. However, once they needed IPv6 and IPsec guess what happened??? They moved to Linux and now have such a time investment in their custom kernel hacks FreeBSD will never be an option for them again. NetBSD and OpenBSD get more and more coverage from IPv6/IPsec capabilities every day. FreeBSD has lost considerable ground if we want to be a platform of choice for network and security researchers. Now ever LSOF has IPv6 support for NetBSD and OpenBSD... ----- Forwarded message from Vic Abell ----- Date: Wed, 21 Jul 1999 10:53:51 -0500 Subject: 64 bit lsof for Solaris 7; IPv6 support for {Net,Open}BSD IPv6 Support for {Net,Open}BSD ============================== ..snip.. An lsof 4.45 pre-release distribution of the NetBSD and OpenBSD sources with the IPv6 updates is available at: ..snip.. ----- End forwarded message ----- -- -- David (obrien@NUXI.com -or- obrien@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 Jul 21 11: 3: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from unix2.it-datacntr.louisville.edu (unix2.it-datacntr.louisville.edu [136.165.4.28]) by hub.freebsd.org (Postfix) with ESMTP id 204051514E for ; Wed, 21 Jul 1999 11:02:50 -0700 (PDT) (envelope-from k.stevenson@louisville.edu) Received: from homer.louisville.edu (ktstev01@homer.louisville.edu [136.165.1.20]) by unix2.it-datacntr.louisville.edu (8.8.8/8.8.8) with ESMTP id NAA50144 for ; Wed, 21 Jul 1999 13:59:56 -0400 Received: (from ktstev01@localhost) by homer.louisville.edu (8.8.8/8.8.8) id OAA29279 for freebsd-hackers@freebsd.org; Wed, 21 Jul 1999 14:00:37 -0400 (EDT) Message-ID: <19990721140036.A26960@homer.louisville.edu> Date: Wed, 21 Jul 1999 14:00:36 -0400 From: Keith Stevenson To: freebsd-hackers@freebsd.org Subject: Re: PAM & LDAP in FreeBSD References: <199907201520.LAA29350@cs.rpi.edu> <19990721094711.C1520@fisicc-ufm.edu> <37960FEF.E6DBD6C0@pobox.com> <19990721105724.F1520@fisicc-ufm.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990721105724.F1520@fisicc-ufm.edu>; from Oscar Bonilla on Wed, Jul 21, 1999 at 10:57:24AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 21, 1999 at 10:57:24AM -0600, Oscar Bonilla wrote: > > I don't see where the modularized crypt would fit in then... > i totally agree that pam has this capability i was just trying to fit > in the crypt stuff people have been working on. (Mark Murray: jump in here if I get this wrong) The way I understand it, a PAM module (pam_unix?) would need to be able to look at the password hash and figure out which of the crypt functions to call. Ideally, the PAM configuration would be able to specify which crypt functions are valid for the system. That said, one of the very attractive features of specifying the crypt function in the login class is the ability to assign different crypt algorithms on a user by user basis. Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.stevenson@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 11:41:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id D1AE014D00 for ; Wed, 21 Jul 1999 11:41:42 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id LAA05382 for ; Wed, 21 Jul 1999 11:40:31 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199907211840.LAA05382@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: Base Kerberos 5 support? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Jul 1999 11:40:31 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy , I noticed this : http://www.microsoft.com/Windows/server/Deploy/security/MitKerb.asp Microsoft claims that they are going to be compatible with MIT Kerberos 5 or so the story goes 8) I noticed that the based kerberized tools in FreeBSD are for Kerberos IV... I installed Kerberos 5 port on my system and it appears to work except in multi-homed server: I get replay dispatch errors ... My work around was simply to start moving my network services to a a box which I don't use often and it has a single interface which is okay and right for internal network services such as kerberos . Cheers -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 11:55:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from jane.lfn.org (dean.charbonnet.net [209.16.92.8]) by hub.freebsd.org (Postfix) with SMTP id 40E8F14FFC for ; Wed, 21 Jul 1999 11:55:10 -0700 (PDT) (envelope-from caj@lfn.org) Received: (qmail 2777 invoked by uid 100); 21 Jul 1999 18:55:05 -0000 Date: Wed, 21 Jul 1999 13:55:05 -0500 (CDT) From: Craig Johnston To: Jaye Mathisen Cc: Modred , Vincent Poy , sthaug@nethelp.no, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Jul 1999, Jaye Mathisen wrote: > > Perhaps I'm missing something obvious, but since switches forward packets > selectively per port, I would think it would be hard to sniff packets on > any port, w/o administrative access to the switch to tell it to mirror > data to a different port. You can definitely do it with ARP games. I was playing with this and I ran into an interesting phenomena -- perhaps someone more familiar with the workings of switches could explain. What I was doing was having one machine send out bogus ARPs to all the machines on the network except the victim, telling them the victim was at a nonexistent MAC address. The switch would broadcast packets for this MAC address because it didn't know where it was. I would then rewrite the MAC address in the ethernet header and put the packet back on the wire so the victim would get it. Interesting part was, not only did traffic for my bogus MAC get broadcast, apparently so did ALL traffic. !! This brought the 100Mbit switch to its knees. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 11:56:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (mailbox.adm.binghamton.edu [128.226.10.60]) by hub.freebsd.org (Postfix) with ESMTP id 41A5F14FFC for ; Wed, 21 Jul 1999 11:56:30 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from cs.binghamton.edu (agate.cs.binghamton.edu [128.226.3.45]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id OAA20659; Wed, 21 Jul 1999 14:55:51 -0400 (EDT) Message-ID: <37961A44.D41467ED@cs.binghamton.edu> Date: Wed, 21 Jul 1999 15:06:44 -0400 From: Zhihui Zhang X-Mailer: Mozilla 4.06 [en] (X11; I; SunOS 5.6 sun4m) MIME-Version: 1.0 To: Matthew Dillon Cc: freebsd-hackers@freebsd.org Subject: Re: understanding code related to forced COW for debugger Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Jul 1999, Matthew Dillon wrote: > > The VM_PROT_OVERRIDE_WRITE flag is only used for user-wired pages, so > it does not effect 'normal' page handling. Look carefully at the > vm_fault() code (vm/vm_fault.c line 212), that lookup only occurs > with VM_PROT_OVERRIDE_WRITE set if the normal lookup fails and the > user has wired the page. > > So if a normal lookup fails and this is a user-wired page, we try > the lookup again with VM_PROT_OVERRIDE_WRITE, presumably to handle > a faked copy-on-write fault for the debugger. This results in the > following: > > First, we temporarily increase the protections to make the page *appear* > writeable. Note: only 'appear' writeable, not actually be writeable. > > if (fault_type & VM_PROT_OVERRIDE_WRITE) > prot = entry->max_protection; > else > prot = entry->protection; To allow a debugger to write TEXT area of a program, the max_protection field must be set to include VM_PROT_WRITE by the loader. Am I right? > *wired = (entry->wired_count != 0); > if (*wired) > prot = fault_type = entry->protection; > > I'm pretty sure this piece is simply reverting the mess that the > copy-on-write stuff does for the debugger. entry->protection is what > we normally want to use. Since mlock(2) is used by user, these make sense to me. Both vm_fault_wire() and vm_fault_user_wire() have non-zero wired_count of the related map entry before calling vm_fault(). This is done by their caller vm_map_pageable() and vm_map_user_pageable(). Since you are talking about user wiring case, so for the kernel wiring case, the above code should prevent any further fault on the page after this simulated one. Therefore, a kernel-wired page will never cause protection-violation faults, while a user-wired page can, as said on the man pages of mlock(2). Since mlock(2) is used by user, these make sense to me. Thanks for your response. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 12: 1:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id E76E515540 for ; Wed, 21 Jul 1999 12:01:11 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA30513; Wed, 21 Jul 1999 11:59:11 -0700 (PDT) (envelope-from dillon) Date: Wed, 21 Jul 1999 11:59:11 -0700 (PDT) From: Matthew Dillon Message-Id: <199907211859.LAA30513@apollo.backplane.com> To: Amancio Hasty Cc: hackers@FreeBSD.ORG Subject: Re: Base Kerberos 5 support? References: <199907211840.LAA05382@rah.star-gate.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Howdy , : :I noticed this : : :http://www.microsoft.com/Windows/server/Deploy/security/MitKerb.asp : :Microsoft claims that they are going to be compatible with MIT Kerberos 5 :or so the story goes 8) : :I noticed that the based kerberized tools in FreeBSD are for Kerberos IV... : :I installed Kerberos 5 port on my system and it appears to work except :in multi-homed server: I get replay dispatch errors ... : :My work around was simply to start moving my network services to a :a box which I don't use often and it has a single interface which is okay :and right for internal network services such as kerberos . : : Cheers : Amancio Hasty Kerberos 5 is currently a port, /usr/ports/security/krb5. I would love to see krb 5 made part of the standard distribution. BEST has been using it for several years now with no problems and I believe that it is a whole lot easier to administrate then krb 4. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 12: 8:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 9DE9F15540 for ; Wed, 21 Jul 1999 12:08:34 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id VAA52963; Wed, 21 Jul 1999 21:08:28 +0200 (CEST) (envelope-from des) To: Snob Art Genre Cc: hackers@FreeBSD.ORG Subject: Re: amandad zombies (fwd) References: From: Dag-Erling Smorgrav Date: 21 Jul 1999 21:08:27 +0200 In-Reply-To: Snob Art Genre's message of "Tue, 20 Jul 1999 16:59:37 -0400 (EDT)" Message-ID: Lines: 14 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Snob Art Genre writes: > I've been beating my head against a mysterious problem for some > time now, and I'm hoping that you folks can help me out. When I run > amanda, seven out of my 16 hosts don't respond. Of these, some are > Solaris and some are FreeBSD 3.1-RELEASE, but it's the FreeBSD ones I'm > concerned with at the moment. I'm using Amanda 2.4.1. (Note that the > symptomology on the Solaris machines is different, which is why I'm > posting this to -hackers.) This was fixed in revision 1.49 of src/usr.sbin/inetd.c (1999/05/11). DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 12:14:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 9B9FC1518F for ; Wed, 21 Jul 1999 12:14:28 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id VAA53109; Wed, 21 Jul 1999 21:14:27 +0200 (CEST) (envelope-from des) To: hackers@freebsd.org Subject: UDMA problems on ALI chipsets From: Dag-Erling Smorgrav Date: 21 Jul 1999 21:14:27 +0200 Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anybody working on getting UltraDMA to work on ALI chipsets? I have a scratch box with that chipset and an UDMA disks and can test patches and perform minor debugging if anyone needs me to. ide_pci0: irq 0 at device 15.0 on pci0 DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 12:33:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id BE11614C1B for ; Wed, 21 Jul 1999 12:33:39 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id VAA49911; Wed, 21 Jul 1999 21:32:35 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199907211932.VAA49911@freebsd.dk> Subject: Re: UDMA problems on ALI chipsets In-Reply-To: from Dag-Erling Smorgrav at "Jul 21, 1999 9:14:27 pm" To: des@flood.ping.uio.no (Dag-Erling Smorgrav) Date: Wed, 21 Jul 1999 21:32:35 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Dag-Erling Smorgrav wrote: > Is anybody working on getting UltraDMA to work on ALI chipsets? I have > a scratch box with that chipset and an UDMA disks and can test patches > and perform minor debugging if anyone needs me to. > > ide_pci0: irq 0 at device 15.0 on pci0 Use the ata driver, it has support for the aladdin chipset, and it works... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 12:35:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 83AA314C1B; Wed, 21 Jul 1999 12:35:27 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id MAA56024; Wed, 21 Jul 1999 12:16:22 -0700 (PDT) Date: Wed, 21 Jul 1999 12:16:22 -0700 (PDT) From: Julian Elischer To: obrien@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Re: Will FreeBSD ever see native IPv6 ?? In-Reply-To: <19990721102534.A8848@dragon.nuxi.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 FreeBSD will have native IPV6 within a matter of weeks at this stage.. the code is being readied as we speak. see www.kame.net . 3 sets of developers for FreeBSD IPV6 have merged their efforts and the result of this should be available by the end of summer (Northern). (which isn't far away now..) On Wed, 21 Jul 1999, David O'Brien wrote: > So is FreeBSD *EVER* going to see native IPv6 ?? > I attended a talk by a group of Intrusion Detection researchers. They > were basing their research on FreeBSD because they needed divert > sockets and found FreeBSD worked perfectly for this in this respect. > However, once they needed IPv6 and IPsec guess what happened??? They > moved to Linux and now have such a time investment in their custom kernel > hacks FreeBSD will never be an option for them again. > > NetBSD and OpenBSD get more and more coverage from IPv6/IPsec > capabilities every day. FreeBSD has lost considerable ground if we want > to be a platform of choice for network and security researchers. > > Now ever LSOF has IPv6 support for NetBSD and OpenBSD... > > > ----- Forwarded message from Vic Abell ----- > Date: Wed, 21 Jul 1999 10:53:51 -0500 > Subject: 64 bit lsof for Solaris 7; IPv6 support for {Net,Open}BSD > > > IPv6 Support for {Net,Open}BSD > ============================== > ..snip.. > > An lsof 4.45 pre-release distribution of the NetBSD and OpenBSD > sources with the IPv6 updates is available at: > > ..snip.. > > ----- End forwarded message ----- > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > > > 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 Jul 21 12:41:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 098C514C4C for ; Wed, 21 Jul 1999 12:41:23 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA10306; Wed, 21 Jul 1999 21:30:39 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id VAA04796; Wed, 21 Jul 1999 21:22:34 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199907211922.VAA04796@yedi.iaf.nl> Subject: Re: any docs on how to use bus_dma_tag_create e.a. ? In-Reply-To: <199907211603.KAA03304@caspian.plutotech.com> from "Justin T. Gibbs" at "Jul 21, 1999 10: 3:14 am" To: gibbs@caspian.plutotech.com (Justin T. Gibbs) Date: Wed, 21 Jul 1999 21:22:34 +0200 (CEST) Cc: gibbs@plutotech.com, hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Justin T. Gibbs wrote ... Excellent help, thanks. Some more questions inserted below. > >shared memory stuff? I found some DMA stuff in ahc_pci.c: > > > > /* Allocate a dmatag for our SCB DMA maps */ > > /* XXX Should be a child of the PCI bus dma tag */ > > error = bus_dma_tag_create(/*parent*/NULL, > > A parent tag would indicate the restrictions of any parent bridge between > the device you are talking to and CPU memory. We haven't modified the > new bus code yet to pass through this information, so just leave it NULL > for now. > /*alignment*/1, > > Any alignment constraints on the target memory region of a DMA specified in > bytes. If the allocation must be 32bit aligned, you would specify 4. > > > /*boundary*/0, > > Any boundary constraints on the target memory region of a DMA, for instance > if the DMA cannot cross a 64k boundary, you would set this to 64K. > > > /*lowaddr*/BUS_SPACE_MAXADDR_32BIT, > > /*highaddr*/BUS_SPACE_MAXADDR, > > low and high address of the region that the DMA engine cannot access. Meaning e.g. the 16Mbyte barrier that ISA DMA has? For PCI this would be a 4Gb range(?). > > /*filter*/NULL, /*filterarg*/NULL, > > If the device's DMA constraints cannot be specified with a single region, > you must specify a region that encompasses all such regions and specify > a filter function to provide a finer level of control. > > > /*maxsize*/MAXBSIZE, > > Maximum DMA transfer size. > > > /*nsegments*/AHC_NSEG, > > Maximum number of discontinuities in the mapped region. Eh.. ? > > /*maxsegsz*/AHC_MAXTRANSFER_SIZE, > > Maximum size of a segment. maxsize <= nsegments * maxsegsz. Eh.. ? > > /*flags*/BUS_DMA_ALLOCNOW > > Allocate all necessary resources to handle a single mapping for this tag > at the time the tag is created. > > >Most (?) drivers seem to use the older framework (can I distinguish > >those by COMPAT_PCI_DRIVER() ?). > > You should use the new API if possible. That is what I'm planning to do. The amount of sample code in the various drivers is rather limited as most drivers use the old code. So I hope you don't mind me asking some more questions, Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 12:47: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 3426214C4C for ; Wed, 21 Jul 1999 12:47:00 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id PAA57713 for ; Wed, 21 Jul 1999 15:45:20 -0400 (EDT) Message-Id: <199907211945.PAA57713@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: UDMA broken in -CURRENT/-STABLE? Date: Wed, 21 Jul 1999 15:45:20 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I updated a system to -CURRENT last night and got a panic with alot of messages about UDMA failing (I don't have the exact messages, I can get them if need be). I backed down the wdc0/wdc1 controller flags from 0xa0ffa0ff to 0x0 and everything is happy. I figured its -CURRENT, and that is to be expected. I updated another system to -STABLE as of earlier today, and I got the same thing... *eeak*. again backing down from 0xa0ffa0ff to 0x0 works like a champ. The messages came right after init(8) started, and before any of the filesystems were mounted r/w (it happened most during the fsck). I hope someone else has seen this (sorry I am so skimpy on the details, I will be able to provide more soonish.) uname -a: FreeBSD phoenix.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #0: Wed Jul 21 15:17:27 EDT 1999 root@phoenix.cs.rpi.edu:/usr/src/sys/compile/PHOENIX i386 dmesg: [...] ide_pci0: rev 0x00 on pci0.7.1 [...] -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 13: 1:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id C60AB14C1F for ; Wed, 21 Jul 1999 13:01:15 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id MAA59122; Wed, 21 Jul 1999 12:59:53 -0700 (PDT) Date: Wed, 21 Jul 1999 12:59:52 -0700 (PDT) From: Julian Elischer To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: UDMA broken in -CURRENT/-STABLE? In-Reply-To: <199907211945.PAA57713@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was in the UDMA code yesterday.... (but mostly in the CYRIX code... (changes elsewhere should have been mostly cosmetic). can you get the exact error message? julian On Wed, 21 Jul 1999, David E. Cross wrote: > I updated a system to -CURRENT last night and got a panic with alot of > messages about UDMA failing (I don't have the exact messages, I can get > them if need be). I backed down the wdc0/wdc1 controller flags from > 0xa0ffa0ff to 0x0 and everything is happy. I figured its -CURRENT, and that > is to be expected. > > I updated another system to -STABLE as of earlier today, and I got the same > thing... *eeak*. again backing down from 0xa0ffa0ff to 0x0 works like a > champ. > > The messages came right after init(8) started, and before any of the > filesystems were mounted r/w (it happened most during the fsck). > > I hope someone else has seen this (sorry I am so skimpy on the details, I > will be able to provide more soonish.) > > uname -a: > FreeBSD phoenix.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #0: Wed Jul 21 15:17:27 EDT 1999 root@phoenix.cs.rpi.edu:/usr/src/sys/compile/PHOENIX i386 > > dmesg: > [...] > ide_pci0: rev 0x00 on pci0.7.1 > [...] > > -- > David Cross | email: crossd@cs.rpi.edu > Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd > Rensselaer Polytechnic Institute, | Ph: 518.276.2860 > Department of Computer Science | Fax: 518.276.4033 > I speak only for myself. | WinNT:Linux::Linux:FreeBSD > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 14:21:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 4C1E415551 for ; Wed, 21 Jul 1999 14:21:19 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id RAA59170; Wed, 21 Jul 1999 17:21:07 -0400 (EDT) Message-Id: <199907212121.RAA59170@cs.rpi.edu> To: Julian Elischer Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!! In-Reply-To: Message from Julian Elischer of "Wed, 21 Jul 1999 12:59:52 PDT." Date: Wed, 21 Jul 1999 17:21:07 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was in the UDMA code yesterday.... > (but mostly in the CYRIX code... (changes elsewhere should have been > mostly cosmetic). > > > can you get the exact error message? > > julian I got it..., I happened to be working on something else at the time and I let it sit unattended for awhile.. it ate my disk partition rather badly. Here is the error I see: wd0: DMA failure, DMA status 5 Thank goodness I tested this -STABLE on my desk machine before I was going to place it on the home directory server for the department... -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 14:34:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with SMTP id 1482714D77 for ; Wed, 21 Jul 1999 14:33:58 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40331>; Thu, 22 Jul 1999 07:13:50 +1000 Date: Thu, 22 Jul 1999 07:32:15 +1000 From: Peter Jeremy Subject: Re: speed of file(1) In-reply-to: <3795B50B.EFBBEFE2@isocor.ie> To: hackers@FreeBSD.ORG Message-Id: <99Jul22.071350est.40331@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: > Looking at ktrace with MALLOC_OPTIONS=U, it does do a lot of > realloc()ing (once for every 20 active lines in .../magic) and sbrk()s > to a maximum size of ~390KB - not really significant. and in a later message: > When I profile file in a slow system (like a 386 or 486), there is an > obvious performance bottleneck: The problem is the memcpy() invoked > from fgets(). Peter Edwards wrote: >A MAXMAGIS constant in file.h that estimates a limit of 1000 lines in >magic. (The real number is 4802) > >An array sized on MAXMAGIS, that is reallocated every ALLOC_INTR lines >of magic once MAXMAGIS is exceeded. That'll teach me to rely on the output from gprof. I thought that gprof's claim (repeated by me) that the apprentice_1() -> fgets() -> memcpy() chain was taking all the time looked dubious, but it was consistent across several systems (and it was late at night for me). (Anyone want to adapt the profiling code so that it correctly apportions time between callers, rather than just using number of calls?) My earlier statement about lots of realloc's, together with the (accurate) datapoint that memcpy() was very slow should have led me to Peter Edwards fix. It also explains why the 3.2/4.x magic file (which has only about 20% more lines) takes 50% longer to start up (continually reallocing to increase an array size is O(N^2)). Congratulations to Peter Edwards. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 15:10:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (Postfix) with ESMTP id 67AE514D6B for ; Wed, 21 Jul 1999 15:10:33 -0700 (PDT) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by shale.csir.co.za (8.9.3/8.9.3) id AAA99089; Thu, 22 Jul 1999 00:08:19 +0200 (SAT) (envelope-from reg) Date: Thu, 22 Jul 1999 00:08:18 +0200 From: Jeremy Lea To: "David E. Cross" Cc: Julian Elischer , freebsd-hackers@FreeBSD.ORG Subject: Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!! Message-ID: <19990722000818.A11593@shale.csir.co.za> References: <199907212121.RAA59170@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907212121.RAA59170@cs.rpi.edu>; from David E. Cross on Wed, Jul 21, 1999 at 05:21:07PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Wed, Jul 21, 1999 at 05:21:07PM -0400, David E. Cross wrote: > > I was in the UDMA code yesterday.... > > (but mostly in the CYRIX code... (changes elsewhere should have been > > mostly cosmetic). > > > > > > can you get the exact error message? > > > > julian > > I got it..., I happened to be working on something else at the time > and I let it sit unattended for awhile.. it ate my disk partition rather > badly. > > Here is the error I see: > wd0: DMA failure, DMA status 5 > > Thank goodness I tested this -STABLE on my desk machine before I was going to > place it on the home directory server for the department... Same error here, from 18h old -CURRENT. Asus TX97 MB and Quantum Fireball SE (4.3GB). Thankfully my disk seems ok (I didn't write anything to that disk with the bad kernel). My last kernel was from 5 July, so I can't narrow the gap any. I tried a kernel with 0x80ff flags, and it wouldn't see my keyboard (although I did a quick rebuild, so that might be pilot error.) Regards, -Jeremy -- | "I could be anything I wanted to, but one things true --+-- Never gonna be as big as Jesus, never gonna hold the world in my hand | Never gonna be as big as Jesus, never gonna build a promised land | But that's, that's all right, OK with me..." -Audio Adrenaline To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 15:13:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 3DEE915570 for ; Wed, 21 Jul 1999 15:13:11 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id PAA70595; Wed, 21 Jul 1999 15:12:43 -0700 (PDT) Date: Wed, 21 Jul 1999 15:12:42 -0700 (PDT) From: Julian Elischer To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!! In-Reply-To: <199907212121.RAA59170@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG this looks like a hardware failure.. On Wed, 21 Jul 1999, David E. Cross wrote: > > I was in the UDMA code yesterday.... > > (but mostly in the CYRIX code... (changes elsewhere should have been > > mostly cosmetic). > > > > > > can you get the exact error message? > > > > julian > > I got it..., I happened to be working on something else at the time > and I let it sit unattended for awhile.. it ate my disk partition rather > badly. > > Here is the error I see: > wd0: DMA failure, DMA status 5 > > Thank goodness I tested this -STABLE on my desk machine before I was going to > place it on the home directory server for the department... > > -- > David Cross | email: crossd@cs.rpi.edu > Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd > Rensselaer Polytechnic Institute, | Ph: 518.276.2860 > Department of Computer Science | Fax: 518.276.4033 > I speak only for myself. | WinNT:Linux::Linux:FreeBSD > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 15:19: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id D9E0F14E75 for ; Wed, 21 Jul 1999 15:19:01 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id PAA70738; Wed, 21 Jul 1999 15:15:26 -0700 (PDT) Date: Wed, 21 Jul 1999 15:15:26 -0700 (PDT) From: Julian Elischer To: Jeremy Lea Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!! In-Reply-To: <19990722000818.A11593@shale.csir.co.za> 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 try a -current but only reverting pci/ide_pci.c you can use the CVS web interface to fetch various versions... julian On Thu, 22 Jul 1999, Jeremy Lea wrote: > Hi, > > On Wed, Jul 21, 1999 at 05:21:07PM -0400, David E. Cross wrote: > > > I was in the UDMA code yesterday.... > > > (but mostly in the CYRIX code... (changes elsewhere should have been > > > mostly cosmetic). > > > > > > > > > can you get the exact error message? > > > > > > julian > > > > I got it..., I happened to be working on something else at the time > > and I let it sit unattended for awhile.. it ate my disk partition rather > > badly. > > > > Here is the error I see: > > wd0: DMA failure, DMA status 5 > > > > Thank goodness I tested this -STABLE on my desk machine before I was going to > > place it on the home directory server for the department... > > Same error here, from 18h old -CURRENT. Asus TX97 MB and Quantum > Fireball SE (4.3GB). Thankfully my disk seems ok (I didn't write > anything to that disk with the bad kernel). > > My last kernel was from 5 July, so I can't narrow the gap any. I tried > a kernel with 0x80ff flags, and it wouldn't see my keyboard (although I > did a quick rebuild, so that might be pilot error.) > > Regards, > -Jeremy > > -- > | "I could be anything I wanted to, but one things true > --+-- Never gonna be as big as Jesus, never gonna hold the world in my hand > | Never gonna be as big as Jesus, never gonna build a promised land > | But that's, that's all right, OK with me..." -Audio Adrenaline > > > 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 Jul 21 15:56:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 3981A1523F for ; Wed, 21 Jul 1999 15:56:24 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id PAA11384; Wed, 21 Jul 1999 15:53:26 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id PAA17097; Wed, 21 Jul 1999 15:52:47 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA18368; Wed, 21 Jul 99 15:53:16 PDT Message-Id: <37964F5C.3FECA244@softweyr.com> Date: Wed, 21 Jul 1999 16:53:16 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Matthew Dillon Cc: Peter Edwards , Peter Jeremy , will@iki.fi, hackers@FreeBSD.ORG Subject: Re: speed of file(1) References: <99Jul21.210648est.40326@border.alcanet.com.au> <3795B50B.EFBBEFE2@isocor.ie> <199907211535.IAA28994@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > Nice rundown of the problem! > > I presume someone is going to commit this... > > -Matt > Matthew Dillon > > > :*** file/apprentice.c Wed Jan 28 07:36:21 1998 > :--- file.new/apprentice.c Wed Jul 21 12:35:21 1999 > :*************** > :*** 50,55 **** > :--- 50,56 ---- > : static void eatsize __P((char **)); > : > : static int maxmagic = 0; > :... I will, if nobody else has. Are there any other committers following this thread? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 16: 6:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (Postfix) with ESMTP id 48EC214DA3 for ; Wed, 21 Jul 1999 16:06:33 -0700 (PDT) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by shale.csir.co.za (8.9.3/8.9.3) id BAA46737; Thu, 22 Jul 1999 01:03:01 +0200 (SAT) (envelope-from reg) Date: Thu, 22 Jul 1999 01:03:01 +0200 From: Jeremy Lea To: Julian Elischer Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!! Message-ID: <19990722010300.B11593@shale.csir.co.za> References: <19990722000818.A11593@shale.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Julian Elischer on Wed, Jul 21, 1999 at 03:15:26PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Wed, Jul 21, 1999 at 03:15:26PM -0700, Julian Elischer wrote: > try a -current but only reverting pci/ide_pci.c It'll have to wait for 18 hours or so... I'm moving the machine from -CURRENT to 3.2-RELEASE then -STABLE, so once my CDs are written and I can get da0 out then I'll play with the disk again... I only wanted a new network driver. Maybe revert -STABLE anyway if there's signs of smoke? > you can use the CVS web interface to fetch various versions... Never run current without a CVS repository is probably better advice. Regards, -Jeremy -- | "I could be anything I wanted to, but one things true --+-- Never gonna be as big as Jesus, never gonna hold the world in my hand | Never gonna be as big as Jesus, never gonna build a promised land | But that's, that's all right, OK with me..." -Audio Adrenaline To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 16:16:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 8E16F14E38 for ; Wed, 21 Jul 1999 16:16:15 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id QAA11587; Wed, 21 Jul 1999 16:14:08 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id QAA17689; Wed, 21 Jul 1999 16:13:27 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA19413; Wed, 21 Jul 99 16:14:02 PDT Message-Id: <37965439.D5FDA8B3@softweyr.com> Date: Wed, 21 Jul 1999 17:14:01 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Matthew Dillon Cc: Peter Edwards , Peter Jeremy , will@iki.fi, hackers@FreeBSD.ORG Subject: Re: speed of file(1) References: <99Jul21.210648est.40326@border.alcanet.com.au> <3795B50B.EFBBEFE2@isocor.ie> <199907211535.IAA28994@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > Nice rundown of the problem! > > I presume someone is going to commit this... OK, I've got it on freefall, ready to roll, and building on my 3.2-STABLE system here. I'll commit it as soon as *I've* seen it work, if somebody doesn't beat me to the punch. ;^) Thanks for the patch, Peter. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 17: 2:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id A346814E44; Wed, 21 Jul 1999 17:02:38 -0700 (PDT) From: "Jonathan M. Bresler" To: modred@ns1.antisocial.net Cc: vince@venus.GAIANET.NET, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG In-reply-to: (message from Modred on Mon, 19 Jul 1999 21:32:32 -0500 (EST)) Subject: Re: poor ethernet performance? Message-Id: <19990722000238.A346814E44@hub.freebsd.org> Date: Wed, 21 Jul 1999 17:02:38 -0700 (PDT) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > That's a option too... Only problem is that can take forever. :-) > > Yeah, I've noticed the 'sync-up time' takes quite awhile on a Catalyst > running 100Mbps. > that is due to the spanning tree algorithm being run. takes about 30 seconds. you can disable this with "spantree portfast" applied to the port. be careful. ;) jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 17:19: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (Postfix) with SMTP id 0CCC814C33 for ; Wed, 21 Jul 1999 17:18:44 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 29333 invoked from network); 22 Jul 1999 00:18:30 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail.cdsnet.net with SMTP; 22 Jul 1999 00:18:30 -0000 Date: Wed, 21 Jul 1999 17:17:54 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: hackers@freebsd.org Subject: What good Xeon boards are people using? 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 Need to build a good fast single processor server running FreeBSD 3.2. Uptime far more important than absolute maximum speed. However, pricing dell/compaq, etc, seems on the high side. What good boards are people using in the trenches? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 17:28: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 58B5E14CA1 for ; Wed, 21 Jul 1999 17:27:51 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id RAA49622 for ; Wed, 21 Jul 1999 17:26:01 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Wed, 21 Jul 1999 17:26:01 -0700 (PDT) From: Vincent Poy To: hackers@FreeBSD.ORG Subject: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings everyone, What are the current good motherboards for FreeBSD for the pentium II and III? I know on the Pentium, it was the ASUS board but for the PII/PIII, is the Abit the better board? Also, I was wondering what is the fastest Celeron chip that can be overclocked to run at 100Mhz FSB? Does it matter if it's Slot 1 or PPGA based? Thanks. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 17:30:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id E693F1552D; Wed, 21 Jul 1999 17:30:00 -0700 (PDT) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Thu, 22 Jul 1999 01:29:55 +0100 Received: from voodoo.pandhm.co.uk (VOODOO [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id PJ2VDTKL; Thu, 22 Jul 1999 01:29:58 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 1176k3-0000VN-00; Thu, 22 Jul 1999 01:29:43 +0100 Date: Thu, 22 Jul 1999 01:29:43 +0100 To: Julian Elischer Cc: obrien@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Will FreeBSD ever see native IPv6 ?? Message-Id: <19990722012943.A1876@palmerharvey.co.uk> References: <19990721102534.A8848@dragon.nuxi.com> MIME-Version: 1.0 X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Julian Elischer on Wed, Jul 21, 1999 at 12:16:22PM -0700 From: Dominic Mitchell Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 21, 1999 at 12:16:22PM -0700, Julian Elischer wrote: > > FreeBSD will have native IPV6 within a matter of weeks at this stage.. > the code is being readied as we speak. see www.kame.net . 3 sets of > developers for FreeBSD IPV6 have merged their efforts and the result of > this should be available by the end of summer (Northern). (which isn't > far away now..) Wicked. I can't wait to exercise our firewall's IPsec capabilities... Congratulations to all parties involved, and good luck with the final mile! -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator In Mountain View did Larry Wall Sedately launch a quiet plea: That DOS, the ancient system, shall On boxes pleasureless to all Run Perl though lack they C. -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 17:31:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 9946A14CA1; Wed, 21 Jul 1999 17:31:12 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA24213; Thu, 22 Jul 1999 10:00:50 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA51287; Thu, 22 Jul 1999 10:00:45 +0930 (CST) Date: Thu, 22 Jul 1999 10:00:45 +0930 From: Greg Lehey To: Jeff Hagendaz Cc: FreeBSD Hackers Subject: Re: polling in device driver Message-ID: <19990722100045.I84734@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Jeff Hagendaz on Wed, Jul 21, 1999 at 04:20:48PM -0700 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [returning to -hackers] On Wednesday, 21 July 1999 at 16:20:48 -0700, Jeff Hagendaz wrote: > Hi, > > I asked this in -hackers, but didn't get an answer. > Guess it is too simple to quanlify into -hackers, > I am moving it here. Your help is highly appreciated. No, -hackers is the right place. Just because you don't get an answer doesn't mean that you posted in the wrong place :-) > I am reading a Linux device driver. At some point it > polls a device to check if it is ready. The timeout > is set to 5 second. It uses the system jiffies to > count the time: > > u32 time_out = jiffies + 5 * HZ; > for (;;) { > /* code to check if dev is ready */ > ........ > if (ready) break; > if (intr_count == 0) schedule(); > if (jiffies > time_out) return ERROR; > } > > How do I implement such polling in FreeBSD? Thanks. If at all possible, you don't. If it's in the bottom half, you don't. You should try to find a better way to find when the device is ready: the driver appears to be counting interrupts, so you can probably tsleep for 5 seconds and wakeup from the lower half when you get an interrupt. It's difficult to give an example from the code you show. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 17:40:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.antisocial.net (ns1.antisocial.net [208.10.211.34]) by hub.freebsd.org (Postfix) with ESMTP id 4416515534 for ; Wed, 21 Jul 1999 17:40:38 -0700 (PDT) (envelope-from modred@ns1.antisocial.net) Received: from localhost (modred@localhost) by ns1.antisocial.net (8.9.3/8.9.3) with ESMTP id TAA16055; Wed, 21 Jul 1999 19:36:30 -0500 (EST) Date: Wed, 21 Jul 1999 19:36:30 -0500 (EST) From: Modred To: Vincent Poy Cc: Wes Peters , Matthew Dillon , Jaye Mathisen , sthaug@nethelp.no, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? 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 Wed, 21 Jul 1999, Vincent Poy wrote: > Speaking about Layer 2 and layer 3. Does the Cisco Catalyst > 2924XL and the HP ProCurve 2424M and 4000M switches fall under Layer 3 or > just layer 2? Cisco, yes... HP, no clue (perhaps you could check their website). 2900XL Architecture Notes: http://www.cisco.com/warp/public/cc/cisco/mkt/switch/cat/2900xl \ /tech/malbu_wp.htmhttp://www.cisco.com/warp/public/cc/cisco/mkt/ \ switch/cat/2900xl/tech/malbu_wp.htm 2900XL Management Guide: http://www.cisco.com/univercd/cc/td/doc/product/lan/c2900xl/ \ 29_35sa6/index.htm IOW, RTFM. Later, --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 17:41:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 51EE615573 for ; Wed, 21 Jul 1999 17:41:38 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id RAA17743; Wed, 21 Jul 1999 17:39:44 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Wed, 21 Jul 1999 17:39:44 -0700 Date: Wed, 21 Jul 1999 17:39:44 -0700 (PDT) From: Kip Macy X-Sender: kip@luna To: Vincent Poy Cc: hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: vince@venus.GAIANET.NET,hackers@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My employer has gone through numerous motherboards, we have found the ASUS P2B (now the P2B-F) to be rock solid for Pentium II usage. On Wed, 21 Jul 1999, Vincent Poy wrote: > Greetings everyone, > > What are the current good motherboards for FreeBSD for the pentium > II and III? I know on the Pentium, it was the ASUS board but for the > PII/PIII, is the Abit the better board? Also, I was wondering what is the > fastest Celeron chip that can be overclocked to run at 100Mhz FSB? Does > it matter if it's Slot 1 or PPGA based? Thanks. > > > Cheers, > Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > GaiaNet Corporation - M & C Estate / / / / | / | __] ] > Beverly Hills, California USA 90210 / / / / / |/ / | __] ] > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > > 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 Jul 21 17:44:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 4156714BE6 for ; Wed, 21 Jul 1999 17:44:33 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id RAA49753; Wed, 21 Jul 1999 17:43:46 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Wed, 21 Jul 1999 17:43:46 -0700 (PDT) From: Vincent Poy To: Kip Macy Cc: hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Jul 1999, Kip Macy wrote: Hmmm, we're using the ABIT BH-6 but that's all because we got the board for free so we can't complain... Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > My employer has gone through numerous motherboards, we have found the ASUS > P2B (now the P2B-F) to be rock solid for Pentium II usage. > > > On Wed, 21 Jul 1999, Vincent Poy wrote: > > > Greetings everyone, > > > > What are the current good motherboards for FreeBSD for the pentium > > II and III? I know on the Pentium, it was the ASUS board but for the > > PII/PIII, is the Abit the better board? Also, I was wondering what is the > > fastest Celeron chip that can be overclocked to run at 100Mhz FSB? Does > > it matter if it's Slot 1 or PPGA based? Thanks. > > > > > > Cheers, > > Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ > > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > > GaiaNet Corporation - M & C Estate / / / / | / | __] ] > > Beverly Hills, California USA 90210 / / / / / |/ / | __] ] > > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > > > > > > 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 Jul 21 17:45:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 4AD4214BE6 for ; Wed, 21 Jul 1999 17:45:46 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id RAA49740; Wed, 21 Jul 1999 17:43:03 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Wed, 21 Jul 1999 17:43:03 -0700 (PDT) From: Vincent Poy To: Modred Cc: Wes Peters , Matthew Dillon , Jaye Mathisen , sthaug@nethelp.no, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? 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 Wed, 21 Jul 1999, Modred wrote: > On Wed, 21 Jul 1999, Vincent Poy wrote: > > > Speaking about Layer 2 and layer 3. Does the Cisco Catalyst > > 2924XL and the HP ProCurve 2424M and 4000M switches fall under Layer 3 or > > just layer 2? > > Cisco, yes... HP, no clue (perhaps you could check their website). > > 2900XL Architecture Notes: > > http://www.cisco.com/warp/public/cc/cisco/mkt/switch/cat/2900xl \ > /tech/malbu_wp.htmhttp://www.cisco.com/warp/public/cc/cisco/mkt/ \ > switch/cat/2900xl/tech/malbu_wp.htm > > 2900XL Management Guide: > > http://www.cisco.com/univercd/cc/td/doc/product/lan/c2900xl/ \ > 29_35sa6/index.htm > > IOW, RTFM. I did, it gets interesting though since if it was a true Level 3 switch, it sure seems to perform more like a Level 2. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 17:56: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (Postfix) with SMTP id 8989E14CF7 for ; Wed, 21 Jul 1999 17:55:59 -0700 (PDT) (envelope-from vev@michvhf.com) Received: (qmail 17560 invoked by uid 1001); 22 Jul 1999 00:54:53 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 21 Jul 1999 20:54:53 -0400 (EDT) X-Face: *0^4Iw) To: freebsd-hardware@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: 1373 sound chip Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I sent this to multimedia about a week ago and didn't get a response so I'm trying it here [hackers & hardware] (with minor mods): I'm setting up a new machine that has onboard sound in the form of an ES1373 Creative (Ensoniq, probably). Visual config shows an unknown device as ES0 and pcm0 doesn't find anything (tried various forms in the kernel config for that one, the last one was/is: device pcm0 Is there any driver for this chip? Under windows it uses the SoundBlaster AudioPCI 64V driver. So far I haven't found any specs on Creative's or Ensoniq's website. Can someone shed some light on possibly adapting the pcm driver to this chip (like how to ID, etc.) ? Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 17:58:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from intranet.com.mx (intranet.com.mx [200.33.246.7]) by hub.freebsd.org (Postfix) with ESMTP id DAB9914C41 for ; Wed, 21 Jul 1999 17:58:55 -0700 (PDT) (envelope-from jbiquez@icsmx.com) Received: from mipcrin.intranet.com.mx (200.33.246.4) by intranet.com.mx with SMTP (Eudora Internet Mail Server 2.2); Wed, 21 Jul 1999 19:33:12 -0500 Message-Id: <3.0.6.32.19990721193432.00a34ec0@intranet.com.mx> X-Sender: jbiquez@intranet.com.mx X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 21 Jul 1999 19:34:32 -0500 To: Vincent Poy From: Jorge Biquez Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's Cc: hackers@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I hope this helps. I'm running version 3.1 on ASUS Pentium III double processor. Just a Rocket! No problems at all on the installation all the SCSI ports were recognized....my entire machine cost me 2000 USD...similar one of a famous brabd...at least 6,000 JB At 05:26 PM 21/07/99 -0700, you wrote: >Greetings everyone, > > What are the current good motherboards for FreeBSD for the pentium >II and III? I know on the Pentium, it was the ASUS board but for the >PII/PIII, is the Abit the better board? Also, I was wondering what is the >fastest Celeron chip that can be overclocked to run at 100Mhz FSB? Does >it matter if it's Slot 1 or PPGA based? Thanks. > > >Cheers, >Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ >Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] >GaiaNet Corporation - M & C Estate / / / / | / | __] ] >Beverly Hills, California USA 90210 / / / / / |/ / | __] ] >HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > >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 Jul 21 18:26:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 3D13314FE1 for ; Wed, 21 Jul 1999 18:26:32 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id VAA15717; Wed, 21 Jul 1999 21:23:53 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA14896; Wed, 21 Jul 1999 21:23:23 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id VAA32548; Wed, 21 Jul 1999 21:23:23 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199907220123.VAA32548@bb01f39.unx.sas.com> Subject: Re: Proposal for new syscall to close files In-Reply-To: From Peter Jeremy at "Jul 21, 1999 10:19:47 am" To: jeremyp@gsmx07.alcatel.com.au (Peter Jeremy) Date: Wed, 21 Jul 1999 21:23:23 -0400 (EDT) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I like this approach. I have a number of often spawned daemon processes that could benefit from this. One of the last process we debugged where we had unwanted open filedescriptors was in programs invoked by the cvs loginfo script. For naming convention considerations, I might suggest 'closeall' or 'closefdset' or something similar... at least have 'close' in name... :-) Good Work, John > It's fairly common, when spawning new processes, to want to make sure > all unwanted FDs are closed. Currently, the options for doing this are: > > 1) Use fcntl(fd, F_SETFD, FD_CLOEXEC) to set the close-on-exec flag > when the file is opened/cloned. This may not be practical if the > FD must remain open across some exec's, but not others. It is not > possible to ensure that FDs implicitly opened within library > functions have the close-on-exec flag set. It may be inefficient if > there are lots of opens and few execs. > > 2) Explicitly close unwanted FDs in the child, before the exec(). > This suffers from the usual resource tracking problems (ie it's > easy to forget to close one - especially in a maze of pipe()/ > dup()/dup2() calls designed to join the child's stdin/out/err > to the parent). It also requires that the FD's be visible to the > function - which may be difficult (the FD may be hidden within > another function somewhere). > > 3) Close all FDs except the ones you explicitly want to keep. This > is normally something like: > for (i = getdtablesize(); --i > 2; ) > close(i); > The advantage is that you are sure you don't miss any. The > disadvantage is that it requires a system call for each potentially > open FD - >600 on my system - whereas maybe only 4 or 5 are > actually open. > > In the case of option 3, you only really need to attempt to close file > descriptors less then curproc->p_fd->fd_lastfile or even > curproc->p_fd->fd_nfiles, but these values aren't readily accessible > from userland. (And this still suffers the overhead of a userland > to kernel transition for each FD). > > I'd therefore like to propose a new syscall that closes _all_ file > descriptors associated with a process, except for those passed as > 1 bits in an fd_set. The proposed API is: > > int cleanup_files(int nfds, const fd_set *leavefds); > > where nfds specifies the number of fds in *leavefds to potentially > keep open (ie all fds >= nfds will be closed). > > The function would return the number of FDs closed. > > The implementation would be along the lines of: > > struct cleanup_files_args { > int nd; > fd_set *leave; > }; > > int > cleanup_files(p, uap) > register struct proc *p; > register struct cleanup_files_args *uap; > { > fd_set s_fdset; > fd_set *lset; > int error, nclosed = 0; > u_int i, ncpbytes, nfdbits; > struct filedesc *fdp = p->p_fd; > struct file **fpp; > char *fdfp; > > if (uap->nd < 0 || uap->leave = NULL) > return (EINVAL); > > /* some daemons mught not have any file descriptors */ > if (fdp == NULL) { > p->p_retval[0] = 0; > return (0); > } > > if (uap->nd > fdp->fd_lastfile) > uap->nd = fdp->fd_lastfile + 1; > > /* > * Allocate just enough bits for the passed fd_set. Use the > * preallocated auto buffer if possible. > */ > nfdbits = roundup(uap->nd, NFDBITS); > ncpbytes = nfdbits / NBBY; > if (ncpbytes <= sizeof s_fdset) > lset = &s_fdset; > else > lset = malloc(ncpbytes, M_SELECT, M_WAITOK); > > error = copyin(uap->leave, lbits, ncpbytes); > if (error != 0) > goto done; > > fpp = fdp->fd_ofiles; > fdfp = fdp->fd_ofileflags; > for (i = 0; i < uap->nd; i++, fpp++, fdfp++) { > if (!FD_ISSET(i, lset) && *fpp != NULL) { > if (*fdfp & UF_MAPPED) > (void) munmapfd(p, i); > error = closef(*fpp, p); > if (error != 0) > goto done; > nclosed++; > *fpp = NULL; > *fdfp = 0; > if (i < fdp->fd_freefile) > fdp->fd_freefile = i; > } > } > > for (; i <= fdp->fd_lastfile; i++, fpp++, fdfp++) > if (*fpp != NULL) { > if (*fdfp & UF_MAPPED) > (void) munmapfd(p, i); > error = closef(*fpp, p); > if (error != 0) > goto done; > nclosed++; > *fpp = NULL; > *fdfp = 0; > if (i < fdp->fd_freefile) > fdp->fd_freefile = i; > } > } > > while (fdp->fd_lastfile > 0 && fdp->fd_ofiles[fdp->fd_lastfile] == NULL) > fdp->fd_lastfile--; > > done: > if (lset != &s_fdset) > free(lset, M_SELECT); > > p->p_retval[0] = nclosed; > return (error); > } > > > Peter > > > 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 Jul 21 18:47:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 4F4C314C33 for ; Wed, 21 Jul 1999 18:47:19 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id SAA13039; Wed, 21 Jul 1999 18:40:36 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id SAA01413; Wed, 21 Jul 1999 18:39:57 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA27386; Wed, 21 Jul 99 18:40:30 PDT Message-Id: <3796768E.24997AD7@softweyr.com> Date: Wed, 21 Jul 1999 19:40:30 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Vincent Poy Cc: Modred , Matthew Dillon , Jaye Mathisen , sthaug@nethelp.no, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vincent Poy wrote: > > On Wed, 21 Jul 1999, Modred wrote: > > > On Wed, 21 Jul 1999, Vincent Poy wrote: > > > > > Speaking about Layer 2 and layer 3. Does the Cisco Catalyst > > > 2924XL and the HP ProCurve 2424M and 4000M switches fall under Layer 3 or > > > just layer 2? > > > > Cisco, yes... HP, no clue (perhaps you could check their website). > > > > IOW, RTFM. Wouldn't that be RTFW? ;^) > I did, it gets interesting though since if it was a true Level 3 > switch, it sure seems to perform more like a Level 2. Wait'll you see IP routing at 12,000,000 packets per second. ;^) Layer 3 switches are not inherently slower than Layer 2, if they're built right. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 19: 6: 2 1999 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 53AA21553E for ; Wed, 21 Jul 1999 19:05:59 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) 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.2) with ESMTP id VAA84067; Wed, 21 Jul 1999 21:04:43 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Wed, 21 Jul 1999 21:04:42 -0500 (CDT) From: Chris Dillon To: Kip Macy Cc: Vincent Poy , hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Jul 1999, Kip Macy wrote: > My employer has gone through numerous motherboards, we have found the ASUS > P2B (now the P2B-F) to be rock solid for Pentium II usage. This is probably more appropriate for -hardware or even just -chat.. but anyway, I'll second that recommendation. I've found the ASUS P2B series to be very solid. I've also used many ATrend BX boards for Winblows95 boxes (simply because they were cheaper than the ASUS boards), and haven't had a bit of trouble with them. YMMV. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 19:10:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 2E51415551 for ; Wed, 21 Jul 1999 19:10:26 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40336>; Thu, 22 Jul 1999 11:51:50 +1000 Date: Thu, 22 Jul 1999 12:10:12 +1000 From: Peter Jeremy Subject: Re: Proposal for new syscall to close files In-reply-to: <199907220123.VAA32548@bb01f39.unx.sas.com> To: jwd@unx.sas.com Cc: freebsd-hackers@FreeBSD.ORG Message-Id: <99Jul22.115150est.40336@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "John W. DeBoskey" wrote: > I like this approach. I have a number of often spawned daemon >processes that could benefit from this. I don't suppose that you have any statistics showing that the for (i = 3; i < getdtablesize(); i++) close(i); approach would be too slow? > For naming convention considerations, I might suggest 'closeall' >or 'closefdset' or something similar... at least have 'close' in >name... :-) I'm not really keen on the name either - but I couldn't think of anything better. `closeall' isn't really descriptive since it doesn't close all the FDs. `closefdset' suggests (to me, anyway) the opposite behaviour: ie closing the FDs specified in the passed fd_set, instead of closing everything else. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 19:33:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wenet.net (sf3-88.ppp.wenet.net [206.15.84.88]) by hub.freebsd.org (Postfix) with ESMTP id A6DD215551 for ; Wed, 21 Jul 1999 19:33:51 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by wenet.net (8.9.3/8.9.1) with ESMTP id TAA00607; Wed, 21 Jul 1999 19:33:29 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Wed, 21 Jul 1999 19:33:29 -0700 (PDT) From: Alex Zepeda To: eT Cc: Hackers FreeBSD Subject: Re: KDE on FreeBSD (missing symbols) In-Reply-To: <379583B5.BC150E1B@post.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Jul 1999, eT wrote: > Hi, I noticed that my ld path was using the old libqt in /usr/X11R6/lib and not the new > one I have in /usr/local/qt/lib. That would do it too :^) > Problem I am getting now is libstdc++ problem: ld.elf complains: > > libstdc++.so.3: undefined symbol __ti9exception You're compiling something without exceptions (-fno-exceptions). Check again Qt, kdelibs, kdebase. And possibly if you built world recently, check the CFLAGS and CXXFLAGS that were used to build world too. - alex You wear guilt, like shackles on your feet, Like a halo in reverse - Depeche Mode To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 22:15:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 36C9A14CAB for ; Wed, 21 Jul 1999 22:15:49 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA78923; Wed, 21 Jul 1999 22:15:49 -0700 (PDT) (envelope-from dillon) Date: Wed, 21 Jul 1999 22:15:49 -0700 (PDT) From: Matthew Dillon Message-Id: <199907220515.WAA78923@apollo.backplane.com> To: freebsd-hackers@freebsd.org Subject: Anyone know how to dim and SGI flat panel? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is the 1600x1024 one that comes w/ the Number-9 graphics card. It has no dimmer control for the backlight but, apparently, there is a way to do it from a control panel in windows. The question is: Is there a way to do it from FreeBSD? I've got it up and running just dandy - except it's so bright it's burning holes in my eyes at night :-( Anyone who has one of these things know how its done? Thanks! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 22:47: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles520.castles.com [208.214.165.84]) by hub.freebsd.org (Postfix) with ESMTP id 9B2A014FBF for ; Wed, 21 Jul 1999 22:46:57 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id WAA00744; Wed, 21 Jul 1999 22:42:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907220542.WAA00744@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: freebsd-hackers@freebsd.org Subject: Re: Anyone know how to dim and SGI flat panel? In-reply-to: Your message of "Wed, 21 Jul 1999 22:15:49 PDT." <199907220515.WAA78923@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Jul 1999 22:42:34 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is the 1600x1024 one that comes w/ the Number-9 graphics card. > It has no dimmer control for the backlight but, apparently, there > is a way to do it from a control panel in windows. > > The question is: Is there a way to do it from FreeBSD? I've got it > up and running just dandy - except it's so bright it's burning holes > in my eyes at night :-( > > Anyone who has one of these things know how its done? I'd bet it's done using DPMS. See if the XFree86 4.x code can tell you anything about the monitor's capabilities. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 23:27: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles520.castles.com [208.214.165.84]) by hub.freebsd.org (Postfix) with ESMTP id C676C14BF4; Wed, 21 Jul 1999 23:26:54 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA00979; Wed, 21 Jul 1999 23:22:04 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907220622.XAA00979@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki Cc: "Brian F. Feldman" , "Daniel C. Sobral" , freebsd-hackers@FreeBSD.org Subject: Re: System unique identifier..... In-reply-to: Your message of "Wed, 21 Jul 1999 12:49:14 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Jul 1999 23:22:04 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > That's not quite true. It wouldn't be too hard to modify existant files, > > but writing new ones/truncating would take a lot of work. It's still not > > a great idea to try to use a file on the FS for storage of persistent > > data. Wouldn't it be possible to have the kernel itself read in persistent > > data (in some form such as getenv?) to be written to disk? That way, the > > boot loader could pass it easily, and not have to worry about storage. > > This may sound like a heresy to you, but... Why don't use the Forth blocks > for that? For what? Saving parametric data? That was always the plan, but the last thing I think anyone wants to do is rewrite the ffs code in Forth. > They were invented for that purpose. We can create the files > beforehand (under normal OS operation), then from the bootloader we can > read and modify them - I suppose writing to a disk block is much easier > than through the filesystem layer... Yes, that's what we've always discussed as being the most likely course of action. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 21 23:44:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from argus.tfs.net (host1-216.birch.net [216.212.1.216]) by hub.freebsd.org (Postfix) with ESMTP id 51FCB14D46 for ; Wed, 21 Jul 1999 23:44:45 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id BAA27461; Thu, 22 Jul 1999 01:43:40 -0500 (CDT) From: Jim Bryant Message-Id: <199907220643.BAA27461@argus.tfs.net> Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's In-Reply-To: from Chris Dillon at "Jul 21, 99 09:04:42 pm" To: cdillon@wolves.k12.mo.us (Chris Dillon) Date: Thu, 22 Jul 1999 01:43:40 -0500 (CDT) Cc: freebsd-hackers@freebsd.org Reply-To: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > On Wed, 21 Jul 1999, Kip Macy wrote: > > > My employer has gone through numerous motherboards, we have found the ASUS > > P2B (now the P2B-F) to be rock solid for Pentium II usage. > > This is probably more appropriate for -hardware or even just -chat.. > but anyway, I'll second that recommendation. I've found the ASUS P2B > series to be very solid. I've also used many ATrend BX boards for > Winblows95 boxes (simply because they were cheaper than the ASUS > boards), and haven't had a bit of trouble with them. YMMV. > > > -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net > FreeBSD: The fastest and most stable server OS on the planet. > For Intel x86 and Alpha architectures (SPARC under development). > ( http://www.freebsd.org ) > > "One should admire Windows users. It takes a great deal of > courage to trust Windows with your data." don't leave out the tyan thunder2 and thunder100 boards. the only problem i even know of with the thunder2 is the sound chip still isn't recognized, and the id codes pnp returns on the sound chip may differ from board to board [others claim it works for them, but not here]. i have heard of no problems with the thunder100 board. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 0:28:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id CB4F714D8B for ; Thu, 22 Jul 1999 00:28:41 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA79662; Thu, 22 Jul 1999 00:27:12 -0700 (PDT) (envelope-from dillon) Date: Thu, 22 Jul 1999 00:27:12 -0700 (PDT) From: Matthew Dillon Message-Id: <199907220727.AAA79662@apollo.backplane.com> To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: Anyone know how to dim and SGI flat panel? References: <199907220542.WAA00744@dingo.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :I'd bet it's done using DPMS. See if the XFree86 4.x code can tell you :anything about the monitor's capabilities. It's up? Very cool, they actually put the prerelease up 2 days ago! 47MB download, yummy! DGA is going to be sooooo cool. Unfortunately it looks like the DPMS stuff is still a bit primitive. Shoot. I'll check it out, though. The 3.3.3 I128 driver (that's the number 9 card) does not appear to support DPMS at all. SGI's site has a whitepaper on the flatpanel but it's a bit spare on control protocols. They do say something about an I2C bus but I dunno whether that is what DPMS uses or not. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 0:56:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from musashi.et.bocholt.fh-ge.de (reserve.et.bocholt.fh-gelsenkirchen.de [193.175.197.95]) by hub.freebsd.org (Postfix) with ESMTP id 3BDB514F43 for ; Thu, 22 Jul 1999 00:56:19 -0700 (PDT) (envelope-from hank@musashi.et.bocholt.fh-ge.de) Received: from localhost (localhost [127.0.0.1]) by musashi.et.bocholt.fh-ge.de (8.9.3/8.9.3) with ESMTP id JAA02355; Thu, 22 Jul 1999 09:55:05 +0200 (CEST) (envelope-from hank@musashi.et.bocholt.fh-ge.de) Message-Id: <199907220755.JAA02355@musashi.et.bocholt.fh-ge.de> To: Bill Paul Cc: morita@jts.ntts.co.jp (morita), freebsd-hackers@FreeBSD.ORG Subject: Re: [FreeBSD-net-jp 1746] [FYI] Adaptec AIC-6915 "Starfire" ethernet controller driver and plus question compaq presario dec et In-reply-to: Your message of "Wed, 21 Jul 1999 10:00:03 EDT." <199907211400.KAA00687@skynet.ctr.columbia.edu> Date: Thu, 22 Jul 1999 09:55:05 +0200 From: Dirk GOUDERS Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG o.k., Bill, I'll try to translate it for you: > > $B?9ED$G$9!#(B My name is Morita. > > > > > > These are Adaptec's replacements for its older DEC 21x4x-based multiport > > > > $B$3$N%I%i%$%P!<$OL5$/$J$k$N$G$7$g$&$+!)(B->DEC 21x4x-based > > no more supllyed ->DEC 21x4x-based Are these drivers lost? (Maybe in the meaning of no more supported.) > > Sorry, but I'm just a dumb american: I can't read this. > > > > line of adapters. All cards support 10/100 speeds in full or half duplex . > > > The multiport cards consist of multiple AIC-6915 chips linkec via a PCI > > > to PCI bridge. Currently I have only tested the ANA-62022 dual port card , > > > however all of them should work equally well. The 64-bit cards will work > > > in a 32-bit slot on most newer machines. > > > > > > > $B%3%s%Q%C%/!!(BPRESARIO$B!!(B2274$B!!$K(BFreeBSD3.2$B%$%s%9%H!<%k$7$?$N$G$9$,!"(B > > NIC$B!'!!(BDEC 21143-based $B$H%S%G%*%+!<%I!'(BSiS5598$B$N@_Dj$,$&$^$/$$$-$^$;$s!"8=:_(B > > $BF0$+$7$F$k(B > > $BJ}$,$$$i$7$?$i65$($F$/$@$5$$!#(B I installed FreeBSD 3.2 on a Compaq PRESARIO 2274 but my DEC 21143-based NIC and SiS5598 video card do not work well (maybe at all). Can you please tell me, how to get them work? > > I can't read this either. :( I guess, I understood the question, but I cannot answer it. Can you? Dirk > > -Bill > > -- > ============================================================================ = > -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu > Work: wpaul@ctr.columbia.edu | Center for Telecommunications Researc h > Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City > ============================================================================ = > "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" > ============================================================================ = > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-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 Jul 22 1:21:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.etrust.ru (serv.etrust.ru [195.2.84.114]) by hub.freebsd.org (Postfix) with ESMTP id 0D93C14E28 for ; Thu, 22 Jul 1999 01:21:33 -0700 (PDT) (envelope-from osa@etrust.ru) Received: from ns.etrust.ru (ns.etrust.ru [195.2.84.114]) by ns.etrust.ru (8.9.1/8.9.1) with ESMTP id MAA01022; Thu, 22 Jul 1999 12:17:09 +0400 (MSD) (envelope-from osa@etrust.ru) Date: Thu, 22 Jul 1999 12:17:07 +0400 (MSD) From: =?KOI8-R?B?88XSx8XKIO/Tz8vJzg==?= To: Vincent Poy Cc: hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Jul 1999, Vincent Poy wrote: > Greetings everyone, > > What are the current good motherboards for FreeBSD for the pentium > II and III? I know on the Pentium, it was the ASUS board but for the > PII/PIII, is the Abit the better board? Also, I was wondering what is the > fastest Celeron chip that can be overclocked to run at 100Mhz FSB? Does > it matter if it's Slot 1 or PPGA based? Thanks. My home box based Abit BX6 rev.2.0 Slot1 & i use PPGA Celeron-300A with Socket370->Slot1 bridge overclocked to 450 (100x4.5) with Pelitier element. This motherboard support PII/PIII. More overclockers says: Abit better then Asus. I think it right. All works fine. Rgdz, Sergey Osokin aka oZZ, osa@etrust.ru http://www.freebsd.org.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 1:24:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 7503214D3C; Thu, 22 Jul 1999 01:24:47 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id KAA11656; Thu, 22 Jul 1999 10:22:30 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199907220822.KAA11656@zibbi.mikom.csir.co.za> Subject: Re: Will FreeBSD ever see native IPv6 ?? In-Reply-To: from Julian Elischer at "Jul 21, 1999 12:16:22 pm" To: julian@whistle.com (Julian Elischer) Date: Thu, 22 Jul 1999 10:22:30 +0200 (SAT) Cc: obrien@FreeBSD.ORG, 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 Are you just teasing or are you serious? I searched through their site (again), but except for being mentioned in their TODO for the past few months, I can't find anything that indicates that they or anyone else is working on it. They may be, but it isn't visible anywhere where I have looked. It would be nice if there was some place to follow their progress, because I'm also one of the people that would like to see IPv6 integrated into FreeBSD. John -- John Hay -- John.Hay@mikom.csir.co.za > > FreeBSD will have native IPV6 within a matter of weeks at this stage.. > the code is being readied as we speak. see www.kame.net . 3 sets of > developers for FreeBSD IPV6 have merged their efforts and the result of > this should be available by the end of summer (Northern). (which isn't > far away now..) > > On Wed, 21 Jul 1999, David O'Brien wrote: > > > So is FreeBSD *EVER* going to see native IPv6 ?? > > I attended a talk by a group of Intrusion Detection researchers. They > > were basing their research on FreeBSD because they needed divert > > sockets and found FreeBSD worked perfectly for this in this respect. > > However, once they needed IPv6 and IPsec guess what happened??? They > > moved to Linux and now have such a time investment in their custom kernel > > hacks FreeBSD will never be an option for them again. > > > > NetBSD and OpenBSD get more and more coverage from IPv6/IPsec > > capabilities every day. FreeBSD has lost considerable ground if we want > > to be a platform of choice for network and security researchers. > > > > Now ever LSOF has IPv6 support for NetBSD and OpenBSD... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 1:30: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 40CAE14D0E for ; Thu, 22 Jul 1999 01:29:50 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA72425; Thu, 22 Jul 1999 09:31:27 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Thu, 22 Jul 1999 09:31:26 +0100 (BST) From: Doug Rabson To: Matthew Dillon Cc: Mike Smith , freebsd-hackers@freebsd.org Subject: Re: Anyone know how to dim and SGI flat panel? In-Reply-To: <199907220727.AAA79662@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Jul 1999, Matthew Dillon wrote: > > : > :I'd bet it's done using DPMS. See if the XFree86 4.x code can tell you > :anything about the monitor's capabilities. > > It's up? Very cool, they actually put the prerelease up 2 days ago! > 47MB download, yummy! DGA is going to be sooooo cool. > > Unfortunately it looks like the DPMS stuff is still a bit primitive. > Shoot. I'll check it out, though. The 3.3.3 I128 driver (that's > the number 9 card) does not appear to support DPMS at all. > > SGI's site has a whitepaper on the flatpanel but it's a bit spare on > control protocols. They do say something about an I2C bus but I dunno > whether that is what DPMS uses or not. XFree86 has an i2c driver in it for talking to monitors so it sounds as if it should see it. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 1:30:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 4C332155CB for ; Thu, 22 Jul 1999 01:30:52 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id BAA52163; Thu, 22 Jul 1999 01:29:43 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Thu, 22 Jul 1999 01:29:43 -0700 (PDT) From: Vincent Poy To: =?KOI8-R?B?88XSx8XKIO/Tz8vJzg==?= Cc: hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Jul 1999, [KOI8-R] óĊÒÇĊÊ ïÓÏËÉÎ wrote: > On Wed, 21 Jul 1999, Vincent Poy wrote: > > > Greetings everyone, > > > > What are the current good motherboards for FreeBSD for the pentium > > II and III? I know on the Pentium, it was the ASUS board but for the > > PII/PIII, is the Abit the better board? Also, I was wondering what is the > > fastest Celeron chip that can be overclocked to run at 100Mhz FSB? Does > > it matter if it's Slot 1 or PPGA based? Thanks. > > My home box based Abit BX6 rev.2.0 Slot1 & i use PPGA Celeron-300A with > Socket370->Slot1 bridge overclocked to 450 (100x4.5) with Pelitier > element. This motherboard support PII/PIII. > More overclockers says: Abit better then Asus. I think it right. > All works fine. Pretty interesting... The Pelitier element is pretty expensive I think... It seems like I've seen more Abit than ASUS Boards when it's a FreeBSD box. We have a 266 running at 400 (100x4) but I don't know which Pentium II would it be the closest to since this is a cacheless chip. It has 384 megs of ram and one thing I can't figure out is that the machine will sometimes pause for a few seconds when I type a command... Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 1:55:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from des.follo.net (des.follo.net [195.204.143.216]) by hub.freebsd.org (Postfix) with ESMTP id 18875155A0; Thu, 22 Jul 1999 01:55:12 -0700 (PDT) (envelope-from des@des.follo.net) Received: (from des@localhost) by des.follo.net (8.9.3/8.9.3) id KAA94340; Thu, 22 Jul 1999 10:53:14 +0200 (CEST) (envelope-from des) To: hackers@freebsd.org, bde@freebsd.org Subject: IDE breakage Organization: Yes Interactive Visit-Us-At: http://www.yes.no/ From: Dag-Erling Smorgrav Date: 22 Jul 1999 10:53:14 +0200 Message-ID: Lines: 262 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm experiencing serious problems with DMA (even normal DMA, not UDMA) on recent versions of -STABLE. Here's an excerpt from messages; kernel #3 is a recent -STABLE (yesterday's sources), while kernel #2 is 3.2-RELEASE. The config file for both is identical. Jul 22 10:19:35 xxx /kernel.old: Copyright (c) 1992-1999 FreeBSD Inc. Jul 22 10:19:35 xxx /kernel.old: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jul 22 10:19:35 xxx /kernel.old: The Regents of the University of California. All rights reserved. Jul 22 10:19:35 xxx /kernel.old: FreeBSD 3.2-STABLE #3: Wed Jul 21 16:21:55 CEST 1999 Jul 22 10:19:35 xxx /kernel.old: root@xxx.xxxxx.xx:/usr/src/sys/compile/XXXXX Jul 22 10:19:35 xxx /kernel.old: Timecounter "i8254" frequency 1193182 Hz Jul 22 10:19:35 xxx /kernel.old: Timecounter "TSC" frequency 348205681 Hz Jul 22 10:19:35 xxx /kernel.old: CPU: Pentium II/Xeon/Celeron (348.21-MHz 686-class CPU) Jul 22 10:19:35 xxx /kernel.old: Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Jul 22 10:19:35 xxx /kernel.old: Features=0x183f9ff Jul 22 10:19:35 xxx /kernel.old: real memory = 134217728 (131072K bytes) Jul 22 10:19:35 xxx /kernel.old: avail memory = 127774720 (124780K bytes) Jul 22 10:19:35 xxx /kernel.old: Preloaded elf kernel "kernel" at 0xc023c000. Jul 22 10:19:35 xxx /kernel.old: Probing for devices on PCI bus 0: Jul 22 10:19:35 xxx /kernel.old: chip0: rev 0x02 on pci0.0.0 Jul 22 10:19:35 xxx /kernel.old: chip1: rev 0x02 on pci0.1.0 Jul 22 10:19:35 xxx /kernel.old: xl0: <3Com 3c905-TX Fast Etherlink XL> rev 0x00 int a irq 11 on pci0.13.0 Jul 22 10:19:35 xxx /kernel.old: xl0: Ethernet address: 00:60:08:e8:6b:1d Jul 22 10:19:35 xxx /kernel.old: xl0: autoneg complete, link status good (full-duplex, 100Mbps) Jul 22 10:19:35 xxx /kernel.old: chip2: rev 0x02 on pci0.20.0 Jul 22 10:19:35 xxx /kernel.old: ide_pci0: rev 0x01 on pci0.20.1 Jul 22 10:19:35 xxx /kernel.old: chip3: rev 0x02 on pci0.20.3 Jul 22 10:19:35 xxx /kernel.old: Probing for devices on PCI bus 1: Jul 22 10:19:35 xxx /kernel.old: vga0: rev 0x5c int a irq 11 on pci1.0.0 Jul 22 10:19:35 xxx /kernel.old: Probing for PnP devices: Jul 22 10:19:35 xxx /kernel.old: Probing for devices on the ISA bus: Jul 22 10:19:35 xxx /kernel.old: sc0 on isa Jul 22 10:19:35 xxx /kernel.old: sc0: VGA color <16 virtual consoles, flags=0x0> Jul 22 10:19:35 xxx /kernel.old: atkbdc0 at 0x60-0x6f on motherboard Jul 22 10:19:35 xxx /kernel.old: atkbd0 irq 1 on isa Jul 22 10:19:35 xxx /kernel.old: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Jul 22 10:19:35 xxx /kernel.old: fdc0: FIFO enabled, 8 bytes threshold Jul 22 10:19:35 xxx /kernel.old: fd0: 1.44MB 3.5in Jul 22 10:19:35 xxx /kernel.old: wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa Jul 22 10:19:35 xxx /kernel.old: wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 Jul 22 10:19:35 xxx /kernel.old: wd0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S Jul 22 10:19:35 xxx /kernel.old: wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa Jul 22 10:19:35 xxx /kernel.old: wdc1: unit 0 (atapi): , removable, accel, dma, iordis Jul 22 10:19:35 xxx /kernel.old: acd0: drive speed 1723KB/sec, 256KB cache Jul 22 10:19:35 xxx /kernel.old: acd0: supported read types: CD-R, CD-RW, CD-DA Jul 22 10:19:35 xxx /kernel.old: acd0: Audio: play, 16 volume levels Jul 22 10:19:35 xxx /kernel.old: acd0: Mechanism: ejectable tray Jul 22 10:19:35 xxx /kernel.old: acd0: Medium: no/blank disc inside, unlocked Jul 22 10:19:35 xxx /kernel.old: npx0 on motherboard Jul 22 10:19:35 xxx /kernel.old: npx0: INT 16 interface Jul 22 10:19:35 xxx /kernel.old: vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa Jul 22 10:19:35 xxx /kernel.old: IP packet filtering initialized, divert disabled, rule-based forwarding disabled, unlimited logging Jul 22 10:19:35 xxx /kernel.old: DUMMYNET initialized (990504) Jul 22 10:19:35 xxx /kernel.old: changing root device to wd0s1a Jul 22 10:19:35 xxx /kernel.old: wd0: DMA failure, DMA status 5 Jul 22 10:19:35 xxx last message repeated 11 times Jul 22 10:19:35 xxx /kernel.old: Copyright (c) 1992-1999 FreeBSD Inc. Jul 22 10:19:35 xxx /kernel.old: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jul 22 10:19:35 xxx /kernel.old: The Regents of the University of California. All rights reserved. Jul 22 10:19:35 xxx /kernel.old: FreeBSD 3.2-RELEASE #2: Mon Jul 12 20:41:42 CEST 1999 Jul 22 10:19:35 xxx /kernel.old: root@xxx.xxxxx.xx:/usr/src/sys/compile/XXXXX Jul 22 10:19:35 xxx /kernel.old: Timecounter "i8254" frequency 1193182 Hz Jul 22 10:19:35 xxx /kernel.old: Timecounter "TSC" frequency 348205021 Hz Jul 22 10:19:35 xxx /kernel.old: CPU: Pentium II/Xeon/Celeron (348.21-MHz 686-class CPU) Jul 22 10:19:35 xxx /kernel.old: Origin = "GenuineIntel" Id = 0x652 Stepping=2 Jul 22 10:19:35 xxx /kernel.old: Features=0x183f9ff> Jul 22 10:19:35 xxx /kernel.old: real memory = 134217728 (131072K bytes) Jul 22 10:19:35 xxx /kernel.old: avail memory = 127832064 (124836K bytes) Jul 22 10:19:35 xxx /kernel.old: Preloaded elf kernel "kernel.old" at 0xc023a000. Jul 22 10:19:35 xxx /kernel.old: Probing for devices on PCI bus 0: Jul 22 10:19:35 xxx /kernel.old: chip0: rev 0x02 on pci0.0.0 Jul 22 10:19:35 xxx /kernel.old: chip1: rev 0x02 on pci0.1.0 Jul 22 10:19:35 xxx /kernel.old: xl0: <3Com 3c905-TX Fast Etherlink XL> rev 0x00 int a irq 11 on pci0.13.0 Jul 22 10:19:35 xxx /kernel.old: xl0: Ethernet address: 00:60:08:e8:6b:1d Jul 22 10:19:35 xxx /kernel.old: xl0: autoneg complete, link status good (full-duplex, 100Mbps) Jul 22 10:19:35 xxx /kernel.old: chip2: rev 0x02 on pci0.20.0 Jul 22 10:19:35 xxx /kernel.old: ide_pci0: rev 0x01 on pci0.20.1 Jul 22 10:19:35 xxx /kernel.old: chip3: rev 0x02 on pci0.20.3 Jul 22 10:19:35 xxx /kernel.old: Probing for devices on PCI bus 1: Jul 22 10:19:35 xxx /kernel.old: vga0: rev 0x5c int a irq 11 on pci1.0.0 Jul 22 10:19:35 xxx /kernel.old: Probing for PnP devices: Jul 22 10:19:35 xxx /kernel.old: Probing for devices on the ISA bus: Jul 22 10:19:35 xxx /kernel.old: sc0 on isa Jul 22 10:19:35 xxx /kernel.old: sc0: VGA color <16 virtual consoles, flags=0x0> Jul 22 10:19:35 xxx /kernel.old: atkbdc0 at 0x60-0x6f on motherboard Jul 22 10:19:35 xxx /kernel.old: atkbd0 irq 1 on isa Jul 22 10:19:35 xxx /kernel.old: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Jul 22 10:19:35 xxx /kernel.old: fdc0: FIFO enabled, 8 bytes threshold Jul 22 10:19:35 xxx /kernel.old: fd0: 1.44MB 3.5in Jul 22 10:19:35 xxx /kernel.old: wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa Jul 22 10:19:35 xxx /kernel.old: wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 Jul 22 10:19:35 xxx /kernel.old: wd0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S Jul 22 10:19:35 xxx /kernel.old: wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa Jul 22 10:19:35 xxx /kernel.old: wdc1: unit 0 (atapi): , removable, accel, dma, iordis Jul 22 10:19:35 xxx /kernel.old: acd0: drive speed 1723KB/sec, 256KB cache Jul 22 10:19:35 xxx /kernel.old: acd0: supported read types: CD-R, CD-RW, CD-DA Jul 22 10:19:35 xxx /kernel.old: acd0: Audio: play, 16 volume levels Jul 22 10:19:35 xxx /kernel.old: acd0: Mechanism: ejectable tray Jul 22 10:19:35 xxx /kernel.old: acd0: Medium: no/blank disc inside, unlocked Jul 22 10:19:35 xxx /kernel.old: npx0 on motherboard Jul 22 10:19:35 xxx /kernel.old: npx0: INT 16 interface Jul 22 10:19:35 xxx /kernel.old: vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa Jul 22 10:19:35 xxx /kernel.old: IP packet filtering initialized, divert disabled, rule-based forwarding disabled, unlimited logging Jul 22 10:19:35 xxx /kernel.old: DUMMYNET initialized (990504) Jul 22 10:19:35 xxx /kernel.old: changing root device to wd0s1a Jul 22 10:19:36 xxx savecore: no core dump Jul 22 10:19:36 xxx named[132]: starting. named 8.1.2 Wed Jul 21 15:47:47 CEST 1999 root@xxx.xxxxx.xx:/usr/obj/usr/src/usr.sbin/named Jul 22 10:19:36 xxx named[133]: Ready to answer queries. Jul 22 10:19:37 xxx xntpd[138]: xntpd version=3.4e (beta multicast); Wed Jul 21 15:48:21 CEST 1999 (1) Jul 22 10:19:37 xxx xntpd[138]: tickadj = 5, tick = 10000, tvu_maxslew = 495 Jul 22 10:19:37 xxx xntpd[138]: using xntpd phase-lock loop Jul 22 10:21:24 xxx su: des to root on /dev/ttyp0 root@xxx /# strings -n 3 /kernel | grep '^___' ___# ___# Kernel configuration for XXXXX servers. ___# ___ ___machine "i386" ___cpu "I586_CPU" ___cpu "I686_CPU" ___ident XXXXX ___maxusers 256 ___ ___# General options ___options "COMPAT_43" ___options KTRACE ___options SYSVSHM ___options SYSVMSG ___options SYSVSEM ___options INCLUDE_CONFIG_FILE ___options USERCONFIG ___options VISUAL_USERCONFIG ___ ___config kernel root on wd0 ___ ___# Buses ___controller isa0 ___controller pnp0 ___controller pci0 ___ ___device npx0 at isa? port IO_NPX irq 13 ___ ___# File system ___options FFS ___options FFS_ROOT ___options MFS ___options MFS_ROOT ___options PROCFS ___options SOFTUPDATES ___ ___controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 ___disk fd0 at fdc0 drive 0 ___controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xa0ffa0ff ___disk wd0 at wdc0 drive 0 ___disk wd1 at wdc0 drive 1 ___controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xa0ffa0ff ___disk wd2 at wdc1 drive 0 ___disk wd3 at wdc1 drive 1 ___options ATAPI ___options ATAPI_STATIC ___device acd0 ___pseudo-device vn 2 ___ ___# Networking ___options INET ___options IPFIREWALL ___options IPFIREWALL_VERBOSE ___options DUMMYNET ___options NMBCLUSTERS=8192 ___device fxp0 ___device xl0 ___pseudo-device ether ___pseudo-device loop 2 ___pseudo-device bpfilter 4 ___pseudo-device pty 64 ___ ___# Console ___controller atkbdc0 at isa? port IO_KBD tty ___device atkbd0 at isa? tty irq 1 ___device vga0 at isa? port ? conflicts ___device sc0 at isa? tty ___options "MSGBUF_SIZE=40960" ___ ___ root@xxx /# strings -n 3 /kernel.old | grep '^___' ___# ___# Kernel configuration for XXXXX servers. ___# ___ ___machine "i386" ___cpu "I586_CPU" ___cpu "I686_CPU" ___ident XXXXX ___maxusers 256 ___ ___# General options ___options "COMPAT_43" ___options KTRACE ___options SYSVSHM ___options SYSVMSG ___options SYSVSEM ___options INCLUDE_CONFIG_FILE ___options USERCONFIG ___options VISUAL_USERCONFIG ___ ___config kernel root on wd0 ___ ___# Buses ___controller isa0 ___controller pnp0 ___controller pci0 ___ ___device npx0 at isa? port IO_NPX irq 13 ___ ___# File system ___options FFS ___options FFS_ROOT ___options MFS ___options MFS_ROOT ___options PROCFS ___options SOFTUPDATES ___ ___controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 ___disk fd0 at fdc0 drive 0 ___controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xa0ffa0ff ___disk wd0 at wdc0 drive 0 ___disk wd1 at wdc0 drive 1 ___controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xa0ffa0ff ___disk wd2 at wdc1 drive 0 ___disk wd3 at wdc1 drive 1 ___options ATAPI ___options ATAPI_STATIC ___device acd0 ___pseudo-device vn 2 ___ ___# Networking ___options INET ___options IPFIREWALL ___options IPFIREWALL_VERBOSE ___options DUMMYNET ___options NMBCLUSTERS=8192 ___device fxp0 ___device xl0 ___pseudo-device ether ___pseudo-device loop 2 ___pseudo-device bpfilter 4 ___pseudo-device pty 64 ___ ___# Console ___controller atkbdc0 at isa? port IO_KBD tty ___device atkbd0 at isa? tty irq 1 ___device vga0 at isa? port ? conflicts ___device sc0 at isa? tty ___options "MSGBUF_SIZE=40960" ___ ___ DES -- Dag-Erling Smorgrav - des@yes.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 2:13:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 21890155F1; Thu, 22 Jul 1999 02:13:25 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 1CDD81912; Thu, 22 Jul 1999 11:13:00 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 1BCD149FC; Thu, 22 Jul 1999 11:13:00 +0200 (CEST) Date: Thu, 22 Jul 1999 11:13:00 +0200 (CEST) From: Andrzej Bialecki To: Mike Smith Cc: "Brian F. Feldman" , "Daniel C. Sobral" , freebsd-hackers@FreeBSD.org Subject: Re: System unique identifier..... In-Reply-To: <199907220622.XAA00979@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Jul 1999, Mike Smith wrote: > > > That's not quite true. It wouldn't be too hard to modify existant files, > > > but writing new ones/truncating would take a lot of work. It's still not > > > a great idea to try to use a file on the FS for storage of persistent > > > data. Wouldn't it be possible to have the kernel itself read in persistent > > > data (in some form such as getenv?) to be written to disk? That way, the > > > boot loader could pass it easily, and not have to worry about storage. > > > > This may sound like a heresy to you, but... Why don't use the Forth blocks > > for that? > > For what? Saving parametric data? That was always the plan, but the > last thing I think anyone wants to do is rewrite the ffs code in Forth. Ugh.. No, of course not. The former, i.e. saving parameters. I'm still sane, you know... :-) Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 2:34:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from des.follo.net (des.follo.net [195.204.143.216]) by hub.freebsd.org (Postfix) with ESMTP id D67B814F21; Thu, 22 Jul 1999 02:34:11 -0700 (PDT) (envelope-from des@des.follo.net) Received: (from des@localhost) by des.follo.net (8.9.3/8.9.3) id LAA94447; Thu, 22 Jul 1999 11:33:44 +0200 (CEST) (envelope-from des) To: Dag-Erling Smorgrav Cc: hackers@freebsd.org, bde@freebsd.org Subject: Re: IDE breakage References: Organization: Yes Interactive Visit-Us-At: http://www.yes.no/ From: Dag-Erling Smorgrav Date: 22 Jul 1999 11:33:44 +0200 In-Reply-To: Dag-Erling Smorgrav's message of "22 Jul 1999 10:53:14 +0200" Message-ID: Lines: 82 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav writes: > I'm experiencing serious problems with DMA (even normal DMA, not UDMA) > on recent versions of -STABLE. Here's an excerpt from messages; kernel > #3 is a recent -STABLE (yesterday's sources), while kernel #2 is > 3.2-RELEASE. The config file for both is identical. A brand new kernel (from the same sources and config, but built in a clean build directory) produces the following: Jul 22 11:29:17 irc /kernel: Copyright (c) 1992-1999 FreeBSD Inc. Jul 22 11:29:17 irc /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jul 22 11:29:17 irc /kernel: The Regents of the University of California. All rights reserved. Jul 22 11:29:17 irc /kernel: FreeBSD 3.2-STABLE #0: Thu Jul 22 10:54:31 CEST 1999 Jul 22 11:29:17 irc /kernel: root@xxx.xxxxx.xx:/usr/src/sys/compile/XXXXX Jul 22 11:29:17 irc /kernel: Timecounter "i8254" frequency 1193182 Hz Jul 22 11:29:17 irc /kernel: Timecounter "TSC" frequency 348204679 Hz Jul 22 11:29:17 irc /kernel: CPU: Pentium II/Xeon/Celeron (348.20-MHz 686-class CPU) Jul 22 11:29:17 irc /kernel: Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Jul 22 11:29:17 irc /kernel: Features=0x183f9ff Jul 22 11:29:17 irc /kernel: real memory = 134217728 (131072K bytes) Jul 22 11:29:17 irc /kernel: avail memory = 127774720 (124780K bytes) Jul 22 11:29:17 irc /kernel: Preloaded elf kernel "kernel" at 0xc023c000. Jul 22 11:29:17 irc /kernel: Probing for devices on PCI bus 0: Jul 22 11:29:17 irc /kernel: chip0: rev 0x02 on pci0.0.0 Jul 22 11:29:17 irc /kernel: chip1: rev 0x02 on pci0.1.0 Jul 22 11:29:17 irc /kernel: xl0: <3Com 3c905-TX Fast Etherlink XL> rev 0x00 int a irq 11 on pci0.13.0 Jul 22 11:29:17 irc /kernel: xl0: Ethernet address: 00:60:08:e8:6b:1d Jul 22 11:29:17 irc /kernel: xl0: autoneg complete, link status good (full-duplex, 100Mbps) Jul 22 11:29:17 irc /kernel: chip2: rev 0x02 on pci0.20.0 Jul 22 11:29:17 irc /kernel: ide_pci0: rev 0x01 on pci0.20.1 Jul 22 11:29:17 irc /kernel: chip3: rev 0x02 on pci0.20.3 Jul 22 11:29:17 irc /kernel: Probing for devices on PCI bus 1: Jul 22 11:29:17 irc /kernel: vga0: rev 0x5c int a irq 11 on pci1.0.0 Jul 22 11:29:17 irc /kernel: Probing for PnP devices: Jul 22 11:29:17 irc /kernel: Probing for devices on the ISA bus: Jul 22 11:29:17 irc /kernel: sc0 on isa Jul 22 11:29:17 irc /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Jul 22 11:29:17 irc /kernel: atkbdc0 at 0x60-0x6f on motherboard Jul 22 11:29:17 irc /kernel: atkbd0 irq 1 on isa Jul 22 11:29:17 irc /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Jul 22 11:29:17 irc /kernel: fdc0: FIFO enabled, 8 bytes threshold Jul 22 11:29:17 irc /kernel: fd0: 1.44MB 3.5in Jul 22 11:29:17 irc /kernel: wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa Jul 22 11:29:17 irc /kernel: wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 Jul 22 11:29:17 irc /kernel: wd0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S Jul 22 11:29:17 irc /kernel: wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa Jul 22 11:29:17 irc /kernel: wdc1: unit 0 (atapi): , removable, accel, dma, iordis Jul 22 11:29:17 irc /kernel: acd0: drive speed 1723KB/sec, 256KB cache Jul 22 11:29:17 irc /kernel: acd0: supported read types: CD-R, CD-RW, CD-DA Jul 22 11:29:17 irc /kernel: acd0: Audio: play, 16 volume levels Jul 22 11:29:17 irc /kernel: acd0: Mechanism: ejectable tray Jul 22 11:29:17 irc /kernel: acd0: Medium: no/blank disc inside, unlocked Jul 22 11:29:17 irc /kernel: npx0 on motherboard Jul 22 11:29:17 irc /kernel: npx0: INT 16 interface Jul 22 11:29:17 irc /kernel: vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa Jul 22 11:29:17 irc /kernel: IP packet filtering initialized, divert disabled, rule-based forwarding disabled, unlimited logging Jul 22 11:29:17 irc /kernel: DUMMYNET initialized (990504) Jul 22 11:29:17 irc /kernel: changing root device to wd0s1a Jul 22 11:29:17 irc /kernel: wd0: DMA failure, DMA status 5 Jul 22 11:29:17 irc last message repeated 17 times Jul 22 11:29:17 irc /kernel: wd0: DMA failure, DMA status 7 Jul 22 11:29:17 irc /kernel: Jul 22 11:29:17 irc /kernel: Jul 22 11:29:17 irc /kernel: Fatal trap 12: page fault while in kernel mode Jul 22 11:29:17 irc /kernel: fault virtual address = 0x44 Jul 22 11:29:17 irc /kernel: fault code = supervisor read, page not present Jul 22 11:29:17 irc /kernel: instruction pointer = 0x8:0xc01813ca Jul 22 11:29:17 irc /kernel: stack pointer = 0x10:0xc9599b84 Jul 22 11:29:17 irc /kernel: frame pointer = 0x10:0xc9599bf4 Jul 22 11:29:17 irc /kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Jul 22 11:29:17 irc /kernel: = DPL 0, pres 1, def32 1, gran 1 Jul 22 11:29:17 irc /kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jul 22 11:29:17 irc /kernel: current process = 5 (sh) Jul 22 11:29:17 irc /kernel: interrupt mask = Jul 22 11:29:17 irc /kernel: trap number = 12 Jul 22 11:29:17 irc /kernel: panic: page fault Jul 22 11:29:17 irc /kernel: Jul 22 11:29:17 irc /kernel: DES -- Dag-Erling Smorgrav - des@yes.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 2:56:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 12E2C14FBF for ; Thu, 22 Jul 1999 02:55:26 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id QAA67161; Thu, 22 Jul 1999 16:52:02 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Thu, 22 Jul 1999 16:52:02 +0700 (NSS) From: Max Khon To: Oscar Bonilla Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD In-Reply-To: <19990716123648.C3049@fisicc-ufm.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Fri, 16 Jul 1999, Oscar Bonilla wrote: > Following up on my own post: > > For LDAP to be seamlessly integrated into the system some of the libraries > have to be changed. Specifically the ones dealing with /etc/passwd and > user information. > > I've decided the best way to do this is to do what's done with NIS. > Basically handle the case where the user is not available in the local > databases. > > the idea is to have an entry in the /etc/passwd enabling LDAP lookups. > the Entry would be of the form > > ldap:*:389:389:o=My Organization, c=BR:uid:ldap.myorg.com > ^^^ ^^^^^^^^^^^^^^^^^^^^^^^ ^^^ ^^^^^^^^^^^^^^ > | | | | > port base dn attr LDAP Server > > This comes ftom a pam_ldap module I got from Pedro A M Vazquez > > > I'll change all of the function in lib/libc/gen/getpwent.c to handle this > special case. > > The only problem is that openldap has to be integrated on the base system > for this to compile... can I safely copy it to /usr/src/contrib? > > How do I submit this after it's done? anyone cares about ldap :)? aargh. looks horrible to me. better try to implement NSS /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 3: 9: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id E351514DE1 for ; Thu, 22 Jul 1999 03:08:05 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id QAA67302; Thu, 22 Jul 1999 16:59:59 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Thu, 22 Jul 1999 16:59:59 +0700 (NSS) From: Max Khon To: Dominic Mitchell Cc: "David E. Cross" , Oscar Bonilla , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD, and userfs too. In-Reply-To: <19990719204417.A5796@palmerharvey.co.uk> 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, there! On Mon, 19 Jul 1999, Dominic Mitchell wrote: > On Mon, Jul 19, 1999 at 12:29:48PM -0400, David E. Cross wrote: > > I thought now would be a good time to chime in on some of my wild schemes... > > > > The reason I am interested in 'userfs' is to enable me to write a version > > of 'nsd'. [...] > Lovely. Sounds like a much better way to do the Solaris/Linux (and > NetBSD?) /etc/nsswitch.conf stuff. On Solaris at least, this is > implemented using masses of weird shared objects... PAM is also "using masses of weird shared objects" but nevertheless it's quite usable /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 3:15:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 4287514DE1 for ; Thu, 22 Jul 1999 03:15:08 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id MAA11249 for ; Thu, 22 Jul 1999 12:15:05 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma011246; Thu, 22 Jul 99 12:15:05 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with SMTP id MAA22652 for ; Thu, 22 Jul 1999 12:15:04 +0200 (MET DST) Received: (qmail 14237 invoked by uid 666); 22 Jul 1999 10:15:26 -0000 Date: Thu, 22 Jul 1999 12:15:26 +0200 From: Jos Backus To: Dag-Erling Smorgrav Cc: hackers@freebsd.org Subject: Re: IDE breakage Message-ID: <19990722121526.B422@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Dag-Erling Smorgrav on Thu, Jul 22, 1999 at 11:33:44AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fwiw, I sometimes (mostly after a warm reboot) see: mmm dd hh:mm:ss hal /kernel: ata1: unwanted interrupt 1 status = ff immediately followed by a similar Fatal trap 12: page fault while in kernel mode. Last time, the current process was swapper. Next time it happens I'll write down the details. Power-cycling works around the problem. A kernel built on July 7th does not exhibit this behavior afaIct. -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 3:17:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id 10DA9155D3 for ; Thu, 22 Jul 1999 03:17:49 -0700 (PDT) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Thu, 22 Jul 1999 11:16:19 +0100 Received: from voodoo.pandhm.co.uk (VOODOO [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id PJ2VDTSD; Thu, 22 Jul 1999 11:16:20 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 117FtW-000Cs0-00; Thu, 22 Jul 1999 11:16:06 +0100 Date: Thu, 22 Jul 1999 11:16:06 +0100 To: Max Khon Cc: Dominic Mitchell , "David E. Cross" , Oscar Bonilla , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD, and userfs too. Message-Id: <19990722111605.C49393@palmerharvey.co.uk> References: <19990719204417.A5796@palmerharvey.co.uk> MIME-Version: 1.0 X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Max Khon on Thu, Jul 22, 1999 at 04:59:59PM +0700 From: Dominic Mitchell Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 22, 1999 at 04:59:59PM +0700, Max Khon wrote: > On Mon, 19 Jul 1999, Dominic Mitchell wrote: > > Lovely. Sounds like a much better way to do the Solaris/Linux (and > > NetBSD?) /etc/nsswitch.conf stuff. On Solaris at least, this is > > implemented using masses of weird shared objects... > > PAM is also "using masses of weird shared objects" but nevertheless it's > quite usable By statically linked binaries? -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator In Mountain View did Larry Wall Sedately launch a quiet plea: That DOS, the ancient system, shall On boxes pleasureless to all Run Perl though lack they C. -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 3:20:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id B8B7814D43 for ; Thu, 22 Jul 1999 03:19:56 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id RAA67669 for ; Thu, 22 Jul 1999 17:19:09 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Thu, 22 Jul 1999 17:19:09 +0700 (NSS) From: Max Khon To: freebsd-hackers@freebsd.org Subject: NSS project 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, there! So what is the "official" status of NSS impl.? Are there any takers? /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 3:26:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id CDAD014C35 for ; Thu, 22 Jul 1999 03:26:01 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id RAA67431; Thu, 22 Jul 1999 17:08:06 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Thu, 22 Jul 1999 17:08:06 +0700 (NSS) From: Max Khon To: "Daniel C. Sobral" Cc: Oscar Bonilla , Kris Kennaway , "David E. Cross" , Joe Abley , Wes Peters , Mike Smith , Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD In-Reply-To: <3795EEB9.1A21EEA@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Thu, 22 Jul 1999, Daniel C. Sobral wrote: > I perceive here an unfair biasing toward nss. Someone mentioned > defining where to get the passwords from based on the login class. > This is a very interesting option, that doesn't seem to be well > served by nss. there is already nss_ldap module for NSS to get all the stuff from LDAP that's why NSS is better (for me) than other solutions /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 3:32:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 39A3714C35 for ; Thu, 22 Jul 1999 03:32:03 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id RAA67619; Thu, 22 Jul 1999 17:17:01 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Thu, 22 Jul 1999 17:17:01 +0700 (NSS) From: Max Khon To: Oscar Bonilla Cc: Kris Kennaway , "David E. Cross" , Joe Abley , Wes Peters , Mike Smith , Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD In-Reply-To: <19990720144217.A426@fisicc-ufm.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Tue, 20 Jul 1999, Oscar Bonilla wrote: > > It looks like we've got some good concurrent projects happening at the > > moment - markm and co working on PAM, the nsswitch.conf project you're > > talking about, and the stuff I'm working on with modularizing crypt() and > > supporting per-login class password hashes (I've rewritten the library > > since I last posted about it and expect to have my code cleaned up by > > tomorrow night for another snapshot). > > > > The thing to make sure is that we don't tread on each other's toes, and > > basically that we look for the big picture and how all these projects fit > > together. > > > > Ok, this is my understanding of the thing: > > There are two parts to the problem, first we need a way to tell the > system where to get its information from (call them databases, tables > or whatever). This should be done a la solaris, with > /etc/nsswitch.conf telling if this is to be fetched from "files, ldap, > nis, dns, etc". > > We need to recode all the programs that obtain this info directly from > files to get it from a library (this would be nsd). And then code the > library itself to get the info from /etc/nsswitch.conf You misunderstand the main goal of NSS -- you need not recode anything -- NSS substitutes getxxxbyzzz libc functions > Second, we need a way to authenticate the user... this is what PAM does. > What would need to be done is change the pam modules to make them > nsd aware (i.e. where should I get the passwd from?) or make them > /etc/auth.conf aware? this is the confusing part... > > where does crypt fit into this? crypt would get what from /etc/login.conf? go to http://www.padl.com and read about LDAP + NSS and PAM deployment schemes /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 3:38: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id C9F5514CC4 for ; Thu, 22 Jul 1999 03:37:53 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id RAA67485; Thu, 22 Jul 1999 17:11:45 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Thu, 22 Jul 1999 17:11:45 +0700 (NSS) From: Max Khon To: Oscar Bonilla Cc: Wes Peters , Mike Smith , "David E. Cross" , Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD In-Reply-To: <19990719180026.A830@fisicc-ufm.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Mon, 19 Jul 1999, Oscar Bonilla wrote: > On Mon, Jul 19, 1999 at 04:51:12PM -0600, Wes Peters wrote: > > The implementation details are as unimportant as ever: they have to work > > and be maintainable. Following prior art remains a good idea; the Solaris > > "name service switch" implementation is a good starting point to consider. > > > > I agree. In solaris (and linux by the way) all you do is set > passwd ldap files > in /etc/nsswitch.conf > and that's it. > > I had started to write the code to mess with libc to "fix" the getpwent stuff, > but a better solution is to "port" the nsswitch stuff from linux (i don't have > source from solaris :) glibc NSS impl. is GPL-poisoned and the author of that impl. (sorry, do not even remember his name) does not want to distribute it under BSD-style copyright. better try to port NetBSD impl. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 4:26:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id B2E2414CE9 for ; Thu, 22 Jul 1999 04:26:34 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 46715 invoked by uid 1001); 22 Jul 1999 11:25:42 +0000 (GMT) To: des@yes.no Cc: hackers@freebsd.org, bde@freebsd.org, julian@whistle.com Subject: Re: IDE breakage From: sthaug@nethelp.no In-Reply-To: Your message of "22 Jul 1999 10:53:14 +0200" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 22 Jul 1999 13:25:42 +0200 Message-ID: <46713.932642742@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm experiencing serious problems with DMA (even normal DMA, not UDMA) > on recent versions of -STABLE. Here's an excerpt from messages; kernel > #3 is a recent -STABLE (yesterday's sources), while kernel #2 is > 3.2-RELEASE. The config file for both is identical. I can confirm problems with DMA from IDE disks in -STABLE. The problems seem to have been introduced in $Id: ide_pci.c,v 1.28.2.1 1999/07/20 22:58:20 julian Exp $ And the effect for me is that the system stops in singleuser mode, with a "DMA failure" message. This is on a 440BX/PII-350 system. Reverting to 1.28 (from 17. January 1999) fixes the problems. Please back out 1.28.2.1, at least in -STABLE. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 5:45:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sbridge.highvoltage.com (voltage.high-voltage.com [205.243.158.175]) by hub.freebsd.org (Postfix) with SMTP id 72AF914C0B; Thu, 22 Jul 1999 05:45:23 -0700 (PDT) (envelope-from BMCGROARTY@high-voltage.com) Date: Thu, 22 Jul 1999 7:07 -0600 From: "Brian McGroarty" To: "Vince Vielhaber" , "freebsd-hardware" , "hackers" Subject: RE: 1373 sound chip 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 There's a patch for the 1371 floating around that seems to work for the 1373 as well. Search the archive of FreeBSD-questions for "1371". Last I saw, the search page was still confused - you need to put "1371" in the web search field at the top, but still click the mailing list search button down below. -----Original Message----- From: Vince Vielhaber [mailto:vev@michvhf.com] Sent: Wednesday, July 21, 1999 6:54 PM To: Brian McGroarty; freebsd-hardware; hackers Subject: 1373 sound chip I sent this to multimedia about a week ago and didn't get a response so I'm trying it here [hackers & hardware] (with minor mods): I'm setting up a new machine that has onboard sound in the form of an ES1373 Creative (Ensoniq, probably). Visual config shows an unknown device as ES0 and pcm0 doesn't find anything (tried various forms in the kernel config for that one, the last one was/is: device pcm0 Is there any driver for this chip? Under windows it uses the SoundBlaster AudioPCI 64V driver. So far I haven't found any specs on Creative's or Ensoniq's website. Can someone shed some light on possibly adapting the pcm driver to this chip (like how to ID, etc.) ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 5:52:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id 74E8F14C0B; Thu, 22 Jul 1999 05:52:05 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.95]) by smtp05.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA6FCE; Thu, 22 Jul 1999 14:51:29 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id OAA00892; Thu, 22 Jul 1999 14:24:45 +0200 (CEST) (envelope-from asmodai) Date: Thu, 22 Jul 1999 14:24:45 +0200 From: Jeroen Ruigrok/Asmodai To: John Hay Cc: Julian Elischer , obrien@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Will FreeBSD ever see native IPv6 ?? Message-ID: <19990722142445.B814@daemon.ninth-circle.org> References: <199907220822.KAA11656@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <199907220822.KAA11656@zibbi.mikom.csir.co.za>; from John Hay on Thu, Jul 22, 1999 at 10:22:30AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * John Hay (jhay@mikom.csir.co.za) [990722 11:55]: > Are you just teasing or are you serious? Well, according to what was discussed earlier he is serious. But from prolonged exposure to the kame lists I (think I) know that the FreeBSD ipv6 stuff is only available for 3.x and below. > I searched through their site (again), but except for being mentioned > in their TODO for the past few months, I can't find anything that > indicates that they or anyone else is working on it. They may be, but > it isn't visible anywhere where I have looked. It would be nice if > there was some place to follow their progress, because I'm also one > of the people that would like to see IPv6 integrated into FreeBSD. At the moment I am busy merging ipv6 from the 3.x kit into CURRENT, but I have to see how to spread my time because I am also doing work on OVCS, the PDP and some other projects. *bwerk* days are much too short... If anyone else is having some spare time and willing to mess with the kame 3.x kit cvsup stuff and CURRENT alongside me, please drop a mail. 'gards, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 6:17:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 5F85B15691 for ; Thu, 22 Jul 1999 06:17:07 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id WAA22058; Thu, 22 Jul 1999 22:14:49 +0900 (JST) To: Jeroen Ruigrok/Asmodai Cc: hackers@FreeBSD.ORG In-reply-to: asmodai's message of Thu, 22 Jul 1999 14:24:45 +0200. <19990722142445.B814@daemon.ninth-circle.org> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: Will FreeBSD ever see native IPv6 ?? From: itojun@iijlab.net Date: Thu, 22 Jul 1999 22:14:49 +0900 Message-ID: <22056.932649289@coconut.itojun.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Are you just teasing or are you serious? >Well, according to what was discussed earlier he is serious. But from >prolonged exposure to the kame lists I (think I) know that the FreeBSD ipv6 >stuff is only available for 3.x and below. We (KAME) are using 3.2-RELEASE and 2.2.8-RELEASE because we can't base our IPv6 development on top of moving target. FreeBSD 3.x-STABLE and 4.x are moving target (which moves very quickly) and are unusable as base version for us - if we need to chase two moving things (IPv6 and FreeBSD) we are doomed. There has been NRL/INRIA/KAME integration work going on (basically to avoid "4 BSDs and 3 IPv6 = 12 choices" nightmare by making one IPv6 stack). There are, mainly, some (or too many) management issues there. We will be resolving management issues issue very soon, hopefully by next week. There's incomplete "unified" codebase there, which is not very ready for public consumption. Anyway please hold till the managment issue is resolved, I believe I can give you a good news. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 6:28:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from charon.npc.net (charon.finall.com [199.15.61.3]) by hub.freebsd.org (Postfix) with ESMTP id 47FAF14DD0 for ; Thu, 22 Jul 1999 06:28:37 -0700 (PDT) (envelope-from mjung@npc.net) Received: from exchange.finall.com (exchange-gw.finall.com [10.0.158.37]) by charon.npc.net (8.9.1/8.8.8) with SMTP id JAA08563 for ; Thu, 22 Jul 1999 09:25:51 -0400 (EDT) (envelope-from mjung@npc.net) Received: by exchange.finall.com with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.996.62) id <01BED424.D643EEC0@exchange.finall.com>; Thu, 22 Jul 1999 09:30:29 -0400 Message-ID: From: "Jung, Michael" To: "'freebsd-hackers@freebsd.org'" Subject: > arpresolve: can't allocate llinfo for 255.255.255.0rt Date: Thu, 22 Jul 1999 09:30:28 -0400 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.996.62 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 started getting these messages in the daily security output..... > arpresolve: can't allocate llinfo for 255.255.255.0rt > arpresolve: can't allocate llinfo for 255.255.255.0rt > arpresolve: can't allocate llinfo for 255.255.255.0rt > arpresolve: can't allocate llinfo for 255.255.255.0rt > arpresolve: can't allocate llinfo for 255.255.255.0rt > arpresolve: can't allocate llinfo for 255.255.255.0rt > arpresolve: can't allocate llinfo for 255.255.255.0rt Upon inspection of the routing table I see this (mikej@hobbs) /usr/home/mikej$netstat -r Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default c5500-rsm-vlan10 UGSc 8 51872 tl0 localhost localhost UH 0 0 lo0 129.2.1/24 link#2 UC 0 0 de0 199.15/16 link#1 UC 0 0 tl0 199.15.32 c5500-rsm-vlan10 UGSc 0 0 tl0 => 199.15.32&0xc70f22 255.255.255.0 UGSc 0 185 tl0 c5500-rsm-vlan10 0:e0:34:a1:84:0 UHLW 5 0 tl0 1198 calvin 0:80:5f:cb:de:16 UHLW 1 22152 tl0 67 Can anyone explain how or where the "199.15.32&0xc70f22" entry could have come from? I've been unable to remove it and don't have a window to reload the server for several days. Thanks-- Michael Jung (502) 315-2457 Voice Senior Network Specialist (502) 315-2815 Facsimile National Processing Company, Inc. mjung@npc.net 1231 Durrett Lane MJ548 Louisville, KY 40285 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 6:40:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles546.castles.com [208.214.165.110]) by hub.freebsd.org (Postfix) with ESMTP id 64306151F1 for ; Thu, 22 Jul 1999 06:40:38 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA01414; Thu, 22 Jul 1999 00:28:01 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907220728.AAA01414@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: Mike Smith , freebsd-hackers@freebsd.org Subject: Re: Anyone know how to dim and SGI flat panel? In-reply-to: Your message of "Thu, 22 Jul 1999 00:27:12 PDT." <199907220727.AAA79662@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Jul 1999 00:28:00 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > :I'd bet it's done using DPMS. See if the XFree86 4.x code can tell you > :anything about the monitor's capabilities. > > It's up? Very cool, they actually put the prerelease up 2 days ago! > 47MB download, yummy! DGA is going to be sooooo cool. > > Unfortunately it looks like the DPMS stuff is still a bit primitive. > Shoot. I'll check it out, though. The 3.3.3 I128 driver (that's > the number 9 card) does not appear to support DPMS at all. > > SGI's site has a whitepaper on the flatpanel but it's a bit spare on > control protocols. They do say something about an I2C bus but I dunno > whether that is what DPMS uses or not. That is how I believe that DMPS communications are transported to the display. Unfortunately, the DPMS specification is a VESA-proprietary document so you will have to either join the XFree86 project or sponsor FreeBSD as a VESA member (that would be nice 8). -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 6:50:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rebel.net.au (rebel.rebel.net.au [203.20.69.66]) by hub.freebsd.org (Postfix) with ESMTP id 6CE3A15227 for ; Thu, 22 Jul 1999 06:50:18 -0700 (PDT) (envelope-from kkenn@rebel.net.au) Received: from 203.20.69.80 (dialup-10.rebel.net.au [203.20.69.80]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id XAA25188 for ; Thu, 22 Jul 1999 23:19:16 +0930 Received: (qmail 27811 invoked from network); 22 Jul 1999 13:49:36 -0000 Received: from localhost (kkenn@127.0.0.1) by localhost with SMTP; 22 Jul 1999 13:49:36 -0000 Date: Thu, 22 Jul 1999 23:19:35 +0930 (CST) From: Kris Kennaway Reply-To: kkenn@rebel.net.au To: freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD, and userfs too. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Jul 1999, Dominic Mitchell wrote: > > PAM is also "using masses of weird shared objects" but nevertheless it's > > quite usable > > By statically linked binaries? This is also an issue for a modularized libcrypt(). Peter Wemm suggested having the library fork and exec a static helper binary module and communicate via a pipe. So essentially you'd have two files for each module, one which is a shared library and loaded via dlopen() and one which is the same code with a small amount of wrapper (main() etc) to make it into a standalone binary. Solaris seem to be deprecating static libraries; you cannot have a fully static libc and they have to resort to keeping (a copy of) libdl (and presumably the run-time linker) under /etc so it's available on the root partition. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 6:52:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 547441522C for ; Thu, 22 Jul 1999 06:52:53 -0700 (PDT) (envelope-from kbyanc@alcnet.com) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from kbyanc (ws-41.alcnet.com [63.69.28.41]) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with SMTP id KAA11856; Thu, 22 Jul 1999 10:08:02 -0400 (EDT) From: "Kelly Yancey" To: Cc: Subject: Re: UDMA broken in -CURRENT/-STABLE? Date: Thu, 22 Jul 1999 10:04:30 -0400 Message-ID: <003a01bed44b$1dfce020$291c453f@kbyanc.alcnet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I updated a system to -CURRENT last night and got a panic with alot of > messages about UDMA failing (I don't have the exact messages, I can get > them if need be). I backed down the wdc0/wdc1 controller flags from > 0xa0ffa0ff to 0x0 and everything is happy. I figured its -CURRENT, and that > is to be expected. > > I updated another system to -STABLE as of earlier today, and I got the same > thing... *eeak*. again backing down from 0xa0ffa0ff to 0x0 works like a > champ. > > The messages came right after init(8) started, and before any of the > filesystems were mounted r/w (it happened most during the fsck). > > I hope someone else has seen this (sorry I am so skimpy on the details, I > will be able to provide more soonish.) > > uname -a: > FreeBSD phoenix.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #0: Wed Jul 21 15:17:27 EDT 1999 root@phoenix.cs.rpi.edu:/usr/src/sys/compile/PHOENIX i386 > > dmesg: > [...] > ide_pci0: rev 0x00 on pci0.7.1 > [...] I've seen the exact same problem on -stable builds since the 20th (I don't know how much further back it went than that). I'm not in front of my computer right now, but the errors were all DMA errors (status as I recall). I have a PIIX4 controller. I played around with it a bit and found that simply turning of the DMA hint in the flags cleared the problems (my flags went from f0fff0ff to d0ffd0ff I believe). Actually, once I accidentilly left the flags with DMA enabled on only 1 drive and only received DMA errons on that single drive. I don't know if this is related, but my atapi CD (Acer 40x) still reports DMA (apparently not affected by the wdc flags), but won't play audio CDs from most CD apps (apparently the ones which use the CDIOCPLAYWMF ioctl to play audio). This has been going on for longer, but I don't know if it was maybe a precursor to the UDMA bug? Kelly ~kbyanc@posi.net~ FreeBSD - The Power To Serve - http://www.freebsd.org/ Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 6:54: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.go2france.com (go2france.com [209.51.193.70]) by hub.freebsd.org (Postfix) with SMTP id AD7FC1522C for ; Thu, 22 Jul 1999 06:54:01 -0700 (PDT) (envelope-from lconrad@Go2France.com) Received: from superviseur [62.161.63.210] by mail.go2france.com with ESMTP (SMTPD32-4.03) id ADE91A0342; Thu, 22 Jul 1999 08:26:17 EDT Message-Id: <4.2.0.56.19990722155323.020b1a50@go2france.com> X-Sender: lconrad@go2france.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta) Date: Thu, 22 Jul 1999 15:53:34 +0200 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: FreeBSD: the stealth OS? 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 Cool with the geeks beecause it's "unknown". http://www.msnbc.com/news/292376.asp Len To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 7: 0:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rebel.net.au (rebel.rebel.net.au [203.20.69.66]) by hub.freebsd.org (Postfix) with ESMTP id 10CDC14D44 for ; Thu, 22 Jul 1999 07:00:13 -0700 (PDT) (envelope-from kkenn@rebel.net.au) Received: from 203.20.69.80 (dialup-10.rebel.net.au [203.20.69.80]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id XAA25266 for ; Thu, 22 Jul 1999 23:28:05 +0930 Received: (qmail 32904 invoked from network); 22 Jul 1999 13:58:19 -0000 Received: from localhost (kkenn@127.0.0.1) by localhost with SMTP; 22 Jul 1999 13:58:19 -0000 Date: Thu, 22 Jul 1999 23:28:19 +0930 (CST) From: Kris Kennaway Reply-To: kkenn@rebel.net.au To: "Daniel C. Sobral" Cc: hackers@freebsd.org Subject: Re: PAM & LDAP in FreeBSD In-Reply-To: <3795EEB9.1A21EEA@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Jul 1999, Daniel C. Sobral wrote: > Oscar Bonilla wrote: > > > > There are three parts to the problem: > > > > 1. Where do we get the databases from? I mean, where do we get passwd, group, > > hosts, ethers, etc from. > > > > This should be handled by a name service switch a la solaris. Basically > > we want to be able to tell the system for each individual database where > > to get the stuff from. We can add entries for each database in the system. > > I perceive here an unfair biasing toward nss. Someone mentioned > defining where to get the passwords from based on the login class. Not quite, if you're talking about me - I use login.conf to tell passwd(1) what hash algorithm to use for new account passwords. login.conf isn't applicable for where to get passwords from; you need to already know the user name (and presumably the entire struct passwd) to know what login class they're in. What does make sense is to be able to configure where getpwent() and friends go to get the struct passwd in the first place; whether from /etc/[s]pwd.db, a LDAP server, etc. This could either be done by teaching getpwent() how to interface with more and more backends, or by a config file which (effectively) swaps between entirely different getpwent() functions (one which talks to spwd.db, one which talks LDAP, etc). This is the nsswitch.conf route. Kris > This is a very interesting option, that doesn't seem to be well > served by nss. > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 7: 6:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 5EA821522C for ; Thu, 22 Jul 1999 07:06:13 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id KAA73113 for ; Thu, 22 Jul 1999 10:06:04 -0400 (EDT) Message-Id: <199907221406.KAA73113@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: Filesystem question... Date: Thu, 22 Jul 1999 10:06:04 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since I am planning on writing userfs in order to impliment 'nsd' (and some other ideas I have hatching too :). I need to know how filesystem accesses work. Can they be queued up, and responded to out of order? For example... I have a request come in (via the filesystem), that request is going to take awhile, so I thread off a handler. Now another filesystem request comes in, will that be delivered to me, or will that block waiting for the previous request to be honored first? -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 7: 6:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rebel.net.au (rebel.rebel.net.au [203.20.69.66]) by hub.freebsd.org (Postfix) with ESMTP id 12F7D15019 for ; Thu, 22 Jul 1999 07:06:03 -0700 (PDT) (envelope-from kkenn@rebel.net.au) Received: from 203.20.69.80 (dialup-10.rebel.net.au [203.20.69.80]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id XAA25321 for ; Thu, 22 Jul 1999 23:35:24 +0930 Received: (qmail 33237 invoked from network); 22 Jul 1999 14:04:35 -0000 Received: from localhost (kkenn@127.0.0.1) by localhost with SMTP; 22 Jul 1999 14:04:35 -0000 Date: Thu, 22 Jul 1999 23:34:35 +0930 (CST) From: Kris Kennaway Reply-To: kkenn@rebel.net.au To: Oscar Bonilla Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD In-Reply-To: <19990721094711.C1520@fisicc-ufm.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Jul 1999, Oscar Bonilla wrote: > Ok, here goes my understanding of how things should be, please correct me > if i'm wrong. > > There are three parts to the problem: > > 1. Where do we get the databases from? I mean, where do we get passwd, group, > hosts, ethers, etc from. > > This should be handled by a name service switch a la solaris. Basically > we want to be able to tell the system for each individual database where > to get the stuff from. We can add entries for each database in the system. > > 2. How to authorize the user? I mean, what sort of authentication should we > use to decide if the user should be allowed in. > > This should be handled by PAM. PAM also does other functions; session management, password management, etc. > > 3. What password hash should we use when we have the username and the > password hash? > > This should be handled by the new modularized crypt. > > Do we want to be able to tell the system where to get its pam.conf and > login.conf from? This would mean having a pam.conf and login.conf entry > in nsswitch.conf. Hmm. I don't know that this much would be useful. > Can we make a list of stuff that needs to be done to make this possible? > Something like a tasklist would be good. > > a) design and implement a name service switch. > b) make libc aware of the name service switch. > c) ??? I think we should look at what NetBSD is doing and join with their efforts. There's no sense in reinventing the wheel. I'm just running my libcrypt through a make world to make sure it's okay - once it's done I'll post the new source code snapshot for comment and testing. Kris > -Oscar > > -- > For PGP Public Key: finger obonilla@fisicc-ufm.edu > ------------------------------------------------------------------------------ The Feynman Problem-Solving Algorithm: (1) Write down the problem (2) Think real hard (3) Write down the answer ------------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 7:10: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id CDC0414D61 for ; Thu, 22 Jul 1999 07:09:58 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id IAA01489; Thu, 22 Jul 1999 08:07:53 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199907221407.IAA01489@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Wilko Bulte Cc: gibbs@plutotech.com (Justin T. Gibbs), hackers@FreeBSD.ORG Subject: Re: any docs on how to use bus_dma_tag_create e.a. ? In-reply-to: Your message of "Wed, 21 Jul 1999 21:22:34 +0200." <199907211922.VAA04796@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Jul 1999 08:07:53 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > /*lowaddr*/BUS_SPACE_MAXADDR_32BIT, >> > /*highaddr*/BUS_SPACE_MAXADDR, >> >> low and high address of the region that the DMA engine cannot access. > >Meaning e.g. the 16Mbyte barrier that ISA DMA has? >For PCI this would be a 4Gb range(?). The range could be much larger than 4GB. Remember this is a range the device *cannot* access, not a range it can access. So, the beginning of the range for an ISA device would be BUS_SPACE_MAXADDR_24BIT and the hight address would be BUS_SPACE_MAXADDR. Depending on the platform or configuration of the machine, the high address could be larger than a 32bit quantity. >> > /*maxsize*/MAXBSIZE, >> >> Maximum DMA transfer size. >> >> > /*nsegments*/AHC_NSEG, >> >> Maximum number of discontinuities in the mapped region. > >Eh.. ? > >> > /*maxsegsz*/AHC_MAXTRANSFER_SIZE, >> >> Maximum size of a segment. maxsize <= nsegments * maxsegsz. > >Eh.. ? Many DMA engines have S/G capability and so can perform a single DMA that spans multiple segments of "bus space contiguous" data. By setting these parameters, the bus_dmamap_load function can determine how best to map your transfer into bus space and will return to you an array of segments to program into your DMA hardware. >> You should use the new API if possible. > >That is what I'm planning to do. The amount of sample code in the various >drivers is rather limited as most drivers use the old code. It seems that its mostly confined to the SCSI code, but hopefully that will change over time. >So I hope you don't mind me asking some more questions, Not a problem. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 7:40:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from student-mailhub.dcu.ie (ns.dcu.ie [136.206.1.3]) by hub.freebsd.org (Postfix) with ESMTP id B4BE414CDF for ; Thu, 22 Jul 1999 07:40:36 -0700 (PDT) (envelope-from pooka@redbrick.dcu.ie) Received: from mother.redbrick.dcu.ie (postfix@Mother.RedBrick.DCU.IE [136.206.15.2]) by student-mailhub.dcu.ie (8.9.3/8.9.3/893-FD) with ESMTP id PAA32322 for ; Thu, 22 Jul 1999 15:37:39 +0100 (BST) Received: by mother.redbrick.dcu.ie (Postfix, from userid 2033) id EF19E4387B; Thu, 22 Jul 1999 15:39:17 +0100 (BST) Date: Thu, 22 Jul 1999 15:39:17 +0100 To: freebsd-hackers@FreeBSD.ORG Subject: Re: Filesystem question... Message-ID: <19990722153917.E18381@mother.RedBrick.DCU.IE> References: <199907221406.KAA73113@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199907221406.KAA73113@cs.rpi.edu>; from David E. Cross on Thu, Jul 22, 1999 at 10:06:04AM -0400 Organization: My Own Private Hideyhole, Inc. From: pooka@redbrick.dcu.ie (Tiny Non Cats) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 22, 1999 at 10:06:04AM -0400 David E. Cross said: > Since I am planning on writing userfs in order to impliment 'nsd' (and > This may be completely useless, because I've not been following what you want to do with 'nsd', but you may find http://www.cs.columbia.edu/~ezk/research/security/index.html interesting. It's a description of 'WrapFS', written by Erik Zadok. It's a stackable filesystem template written as a kernel module, and can be extended to do all sorts of stuff with relative ease, apparently. Cian -- What think ye of Christ? Whose son is he? Will you, like Peter, boldly say: "Who?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 8: 4:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id 7597B15203 for ; Thu, 22 Jul 1999 08:04:21 -0700 (PDT) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Thu, 22 Jul 1999 16:03:51 +0100 Received: from voodoo.pandhm.co.uk (VOODOO [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id PJ2VDT7N; Thu, 22 Jul 1999 16:03:52 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 117KNm-000DAv-00; Thu, 22 Jul 1999 16:03:38 +0100 Date: Thu, 22 Jul 1999 16:03:38 +0100 To: Kris Kennaway Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD, and userfs too. Message-Id: <19990722160337.D50365@palmerharvey.co.uk> References: MIME-Version: 1.0 X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Kris Kennaway on Thu, Jul 22, 1999 at 11:19:35PM +0930 From: Dominic Mitchell Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 22, 1999 at 11:19:35PM +0930, Kris Kennaway wrote: > On Thu, 22 Jul 1999, Dominic Mitchell wrote: > > > > PAM is also "using masses of weird shared objects" but nevertheless it's > > > quite usable > > > > By statically linked binaries? > > This is also an issue for a modularized libcrypt(). Peter Wemm suggested > having the library fork and exec a static helper binary module and > communicate via a pipe. So essentially you'd have two files for each > module, one which is a shared library and loaded via dlopen() and one > which is the same code with a small amount of wrapper (main() etc) to make > it into a standalone binary. This is starting to get icky. This is also where the earlier idea of a userspace filesystem would probably fare better, in terms of both performance and simplicity. > Solaris seem to be deprecating static libraries; you cannot have a fully > static libc and they have to resort to keeping (a copy of) libdl (and > presumably the run-time linker) under /etc so it's available on the root > partition. Solaris hasn't supported static linking for some time. If you have a look at Casper Dik's FAQ, it goes into more detail. They do keep stuff on the root partition: admin# ls -l /etc/lib total 644 -rwxr-xr-x 1 bin bin 155060 Jul 1 1998 ld.so.1* -rwxr-xr-x 1 bin bin 4284 Jul 1 1998 libdl.so.1* -rwxr-xr-x 1 bin bin 25468 Jul 16 1997 nss_files.so.1* lrwxrwxrwx 1 root root 17 Sep 14 1998 pam_authen.so -> ./pam_authen.so.1* -rwxr-xr-x 1 root sys 14516 Jul 16 1997 pam_authen.so.1* lrwxrwxrwx 1 root root 16 Sep 14 1998 pam_entry.so -> ./pam_entry.so.1* -rwxr-xr-x 1 root sys 11540 Jul 16 1997 pam_entry.so.1* lrwxrwxrwx 1 root root 17 Sep 14 1998 pam_extern.so -> ./pam_extern.so.1* -rwxr-xr-x 1 root sys 11044 Jul 16 1997 pam_extern.so.1* lrwxrwxrwx 1 root root 16 Sep 14 1998 pam_pwmgt.so -> ./pam_pwmgt.so.1* -rwxr-xr-x 1 root sys 85764 Jul 16 1997 pam_pwmgt.so.1* lrwxrwxrwx 1 root root 18 Sep 14 1998 pam_session.so -> ./pam_session.so.1* -rwxr-xr-x 1 root sys 4748 Jul 16 1997 pam_session.so.1* -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator In Mountain View did Larry Wall Sedately launch a quiet plea: That DOS, the ancient system, shall On boxes pleasureless to all Run Perl though lack they C. -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 8:10:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.logx.com (mail.logx.com [206.162.23.33]) by hub.freebsd.org (Postfix) with SMTP id B085D1527A for ; Thu, 22 Jul 1999 08:09:59 -0700 (PDT) (envelope-from jir@logx.com) Received: (qmail 16598 invoked from network); 22 Jul 1999 15:09:34 -0000 Received: from p84b628.sng4.ap.so-net.ne.jp (HELO mebius2) (210.132.182.40) by pop3.logx.com with SMTP; 22 Jul 1999 15:09:34 -0000 Message-ID: <022001bed454$6564d180$0101a8c0@aladdin.jp> From: =?iso-2022-jp?B?amlyIBskQiRHJDkkJiQmGyhC?= To: , , References: <199907220143.KAA11513@rynex.d1.uxd.fc.nec.co.jp> Subject: =?iso-2022-jp?B?UmU6IFtGcmVlQlNELXVzZXJzLWpwIDQ0MzA0XSBkZTAgaXMgYXZhaWxh?= =?iso-2022-jp?B?YmxlIG9yIG5vdD8gKHJlOikbJEIhIRsoQnVzaW5nGyRCISEbKEJuaWMg?= =?iso-2022-jp?B?ZGUwGyRCISEbKEJvGyRCI2YhIRsoQiBwZWFwbGUgbXVjaCBpbiBqYQ==?= =?iso-2022-jp?B?cGFu?= Date: Fri, 23 Jul 1999 00:07:00 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ji $B$G$9!#(B > > $B9b66$G$9!#(B takahashi san > > > $BF0$+$J$+$C$?4D6-(B no move envilonment > $B!&(B10base$B$N%P%+(BHUB > $B!&@\B3Aj $B!&(Bifconfig$B$G(Bmedia$B$r;XDj$7$F$b(B "de0: link down: cable problem?" $B$,$G(B $B$9!#(B > good move envilonment > $BF0$$$?4D6-(B > $B!&(B10/100$B$N%G%e%"%k%9%T!<%I(BHUB(Autonegotiation$BM-(B) > $B!&@\B3Aj $B!&(Bifconfig$B$G(Bmedia$B$OFC$K;XDj$;$:(B question 10/100$B$N%G%e%"%k%9%T!<%I(BHUB(Autonegotiation$BM-(B) $B$G$J$/!"#1#0$N>l9g$O$I$&$9$l$P$$$$$N$G$7$g$&$+!)(B kernel$B!!(Bconfig$B!!$H$+!)(B $B$=$l$H$b(B, $B$=$l$O$$$8$i$:$G$9$+!)(B how config Kernel config? > > $B$I$&$bF0$$$?4D6-$N(B Autonegotiation$BM-(B $B$,$/$; $B2a5n$N(Busers-jp$B$d(Bnet-jp$B$J$I$N%a!<%k$r(B21143$B$G8!:w$7$F$b$d$O$j(B > $B%a%G%#%"$N;XDj$r$9$k$HF0$$$?J}$,B?$$$h$&$G$9!#(B > # 21143$B$N(Bdata sheet$B@N$O(BDEC$B$N(BWeb site$B$K$"$C$?$N$K$J$/$J$C$F$k(B... > # $B$@$l$+;}$C$F$J$$$+$J$!(B($B$\$=(B > > --- > Daisuke Takahashi / $b$7$+$7$F2K$G$9$+!) > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 8:12:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mgate08.so-net.ne.jp (mgate08.so-net.ne.jp [210.132.247.49]) by hub.freebsd.org (Postfix) with ESMTP id 2696A15212 for ; Thu, 22 Jul 1999 08:12:23 -0700 (PDT) (envelope-from aladdin@kb3.so-net.ne.jp) Received: from mail.kb3.so-net.ne.jp (mail.kb3.so-net.ne.jp [210.132.247.109]) by mgate08.so-net.ne.jp (8.8.8+3.0Wbeta9/3.6W99070912) with ESMTP id AAA25755; Fri, 23 Jul 1999 00:09:03 +0900 (JST) Received: from mebius2 (p84b628.sng4.ap.so-net.ne.jp [210.132.182.40]) by mail.kb3.so-net.ne.jp (8.8.8+3.0Wbeta9/3.7W99040113) with SMTP id AAA23227; Fri, 23 Jul 1999 00:09:01 +0900 (JST) Message-ID: <021d01bed454$521371e0$0101a8c0@aladdin.jp> From: "aladdin" To: "net" , , "Bill Paul" References: <199907211400.KAA00687@skynet.ctr.columbia.edu> Subject: Re: [FreeBSD-net-jp 1746] [FYI] Adaptec AIC-6915 "Starfire" ethernet controller driver and plus question compaq presario dec et and * trancelate for english Date: Thu, 22 Jul 1999 23:56:43 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG heloo all ----- Original Message ----- From: Bill Paul To: morita Cc: Sent: Wednesday, July 21, 1999 11:00 PM Subject: Re: [FreeBSD-net-jp 1746] [FYI] Adaptec AIC-6915 "Starfire" ethernet controller driver and plus question compaq presario dec et > Of all the gin joints in all the towns in all the world, morita had to > walk into mine and say: > > > $B?9ED$G$9!#(B > > > > > > These are Adaptec's replacements for its older DEC 21x4x-based multiport > > japanses 1 .> > $B$3$N%I%i%$%P!<$OL5$/$J$k$N$G$7$g$&$+!)(B->DEC 21x4x-based english 1 . > > no more supllyed ->DEC 21x4x-based is it true? japanses 1=english 1 . > Sorry, but I'm just a dumb american: I can't read this. > > > > line of adapters. All cards support 10/100 speeds in full or half duplex. > > > The multiport cards consist of multiple AIC-6915 chips linkec via a PCI > > > to PCI bridge. Currently I have only tested the ANA-62022 dual port card, > > > however all of them should work equally well. The 64-bit cards will work > > > in a 32-bit slot on most newer machines. > > > > > english 2 > > $B%3%s%Q%C%/!!(BPRESARIO$B!!(B2274$B!!$K(BFreeBSD3.2$B%$%s%9%H!<%k$7(B $B$?$N$G$9$,!"(B japanese 2 he install of? FreeBSD3.2 to conpaq PRESARIO$B!!(B2274$B!!(B english 3 > > > NIC$B!'!!(BDEC 21143-based $B$H%S%G%*%+!<%I!'(BSiS5598$B$N@_Dj(B $B$,$&$^$/$$$-$^$;$s!"8=:_(B japanese 3 NIC$B!'!!(BDEC 21143-based video chip is SiS5598 is not good condition now > > $BF0$+$7$F$k(B > > $BJ}$,$$$i$7$?$i65$($F$/$@$5$$!#(B english 4 > tell him how install > > I can't read this either. :( > > -Bill > > -- > ===================================================================== ======== > -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu > Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research > Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City > ===================================================================== ======== > "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" > ===================================================================== ======== > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-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 Jul 22 8:23:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id A94B014CC1 for ; Thu, 22 Jul 1999 08:23:52 -0700 (PDT) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Thu, 22 Jul 1999 16:22:26 +0100 Received: from voodoo.pandhm.co.uk (VOODOO [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id PJ2VDT83; Thu, 22 Jul 1999 16:22:27 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 117Kfl-000DBb-00; Thu, 22 Jul 1999 16:22:13 +0100 Date: Thu, 22 Jul 1999 16:22:13 +0100 To: "Jung, Michael" Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: > arpresolve: can't allocate llinfo for 255.255.255.0rt Message-Id: <19990722162213.E50365@palmerharvey.co.uk> References: MIME-Version: 1.0 X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Jung, Michael on Thu, Jul 22, 1999 at 09:30:28AM -0400 From: Dominic Mitchell Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 22, 1999 at 09:30:28AM -0400, Jung, Michael wrote: > I started getting these messages in the daily security output..... > > > arpresolve: can't allocate llinfo for 255.255.255.0rt > > arpresolve: can't allocate llinfo for 255.255.255.0rt > > arpresolve: can't allocate llinfo for 255.255.255.0rt > > arpresolve: can't allocate llinfo for 255.255.255.0rt > > arpresolve: can't allocate llinfo for 255.255.255.0rt > > arpresolve: can't allocate llinfo for 255.255.255.0rt > > arpresolve: can't allocate llinfo for 255.255.255.0rt I get those after a long run of nmap on our /16 network. At this point, I just kill nmap and the problem goes away. I didn't bother looking into the routing table though. Maybe it's time to see what the PC support monkeys have plugged into my network again. :-) -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator In Mountain View did Larry Wall Sedately launch a quiet plea: That DOS, the ancient system, shall On boxes pleasureless to all Run Perl though lack they C. -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 8:29:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from thneed.ubergeeks.com (thneed.ubergeeks.com [206.205.41.245]) by hub.freebsd.org (Postfix) with ESMTP id 9322114CC1 for ; Thu, 22 Jul 1999 08:29:26 -0700 (PDT) (envelope-from adrian@ubergeeks.com) Received: from localhost (adrian@localhost) by thneed.ubergeeks.com (8.9.3/8.9.3) with ESMTP id LAA02703; Thu, 22 Jul 1999 11:26:57 -0400 (EDT) (envelope-from adrian@ubergeeks.com) X-Authentication-Warning: thneed.ubergeeks.com: adrian owned process doing -bs Date: Thu, 22 Jul 1999 11:26:57 -0400 (EDT) From: Adrian Filipi-Martin Reply-To: Adrian Filipi-Martin To: Vincent Poy Cc: hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Jul 1999, Vincent Poy wrote: > Greetings everyone, > > What are the current good motherboards for FreeBSD for the pentium > II and III? I know on the Pentium, it was the ASUS board but for the > PII/PIII, is the Abit the better board? Also, I was wondering what is the > fastest Celeron chip that can be overclocked to run at 100Mhz FSB? Does > it matter if it's Slot 1 or PPGA based? Thanks. I know a lot of people like the ASUS P2B boards, but I've noticed a tendency for the systems to reset occasionally when plugging in a keyboard. I've seen this with both FreeBSD and NT, so I'm considering it a property of the board. I've had great results with the Tyan 1836DLUAN/Thunder 100's. I've got several boxes with 1GB of RAM and dual 450's humming along. For comparison one system with less memory and a SuperMicro board but identical system software has had a couple of wierd spontaneous reboots over the last few months. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 8:36:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rebel.net.au (rebel.rebel.net.au [203.20.69.66]) by hub.freebsd.org (Postfix) with ESMTP id 752DD151FF for ; Thu, 22 Jul 1999 08:36:29 -0700 (PDT) (envelope-from kkenn@rebel.net.au) Received: from 203.20.69.80 (dialup-10.rebel.net.au [203.20.69.80]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id BAA26282 for ; Fri, 23 Jul 1999 01:06:02 +0930 Received: (qmail 59402 invoked from network); 22 Jul 1999 15:36:02 -0000 Received: from localhost (kkenn@127.0.0.1) by localhost with SMTP; 22 Jul 1999 15:36:02 -0000 Date: Fri, 23 Jul 1999 01:06:00 +0930 (CST) From: Kris Kennaway Reply-To: kkenn@rebel.net.au To: Dominic Mitchell Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD, and userfs too. In-Reply-To: <19990722160337.D50365@palmerharvey.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Jul 1999, Dominic Mitchell wrote: > This is starting to get icky. This is also where the earlier idea of a > userspace filesystem would probably fare better, in terms of both > performance and simplicity. Maybe I don't get how this userspace filesystem is going to be set out (for the case of the nss stuff), but I don't see this. Kris ------------------------------------------------------------------------------ The Feynman Problem-Solving Algorithm: (1) Write down the problem (2) Think real hard (3) Write down the answer ------------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 8:53:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id CE44814D08 for ; Thu, 22 Jul 1999 08:53:05 -0700 (PDT) (envelope-from rminnich@acl.lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id JAA61246; Thu, 22 Jul 1999 09:50:37 -0600 (MDT) Date: Thu, 22 Jul 1999 09:50:37 -0600 From: "Ronald G. Minnich" To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Filesystem question... In-Reply-To: <199907221406.KAA73113@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One last thing: if you're writing userfs you might want to look at www.inter-mezzo.org ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 9:13:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from donhm.calcasieu.com (tcnet00-54.austin.texas.net [209.99.42.243]) by hub.freebsd.org (Postfix) with ESMTP id 95F7514D2D for ; Thu, 22 Jul 1999 09:12:54 -0700 (PDT) (envelope-from dread@texas.net) Received: from donhm.calcasieu.com (localhost.calcasieu.com [127.0.0.1]) by donhm.calcasieu.com (8.8.8/8.8.8) with ESMTP id LAA19258; Thu, 22 Jul 1999 11:10:37 -0500 (CDT) (envelope-from dread@texas.net) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3.0.6.32.19990721193432.00a34ec0@intranet.com.mx> Date: Thu, 22 Jul 1999 11:10:36 -0500 (CDT) From: Don Read To: Vincent Poy Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU' Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Jul-99 Jorge Biquez wrote: > I hope this helps. > I'm running version 3.1 on ASUS Pentium III double processor. Just a Rocket! > No problems at all on the installation all the SCSI ports were > recognized.... my entire machine cost me 2000 USD...similar one of a famous > brabd...at least 6,000 > > JB the ASUS boards PII/350M 128M, 3c905B, dual SCSI (1 on board + 1 Adaptec 2940B), Seagate ST39173W, Toshiba CD on IDE (had a spare HP DAT-24 tape drive) $3400 compared to a certain BigBlue box at $8000+ monitor FreeBSD 2.2.8, MySQL 3.22. been running without a hiccup since Feb. Regards, --- Don Read dread@calcasieu.com EDP Manager dread@texas.net Calcasieu Lumber Co. Austin TX -- But I'm in good company, sendmail has kicked a great many butts in the past To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 9:46:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 7553C14C20; Thu, 22 Jul 1999 09:46:41 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id MAA02834; Thu, 22 Jul 1999 12:47:06 -0400 From: Bill Paul Message-Id: <199907221647.MAA02834@skynet.ctr.columbia.edu> Subject: Update on Adaptec AIC-6915 "starfire" driver To: hackers@freebsd.org, hardware@freebsd.org Date: Thu, 22 Jul 1999 12:47:04 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2873 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't received any feedback yet on the Adaptec "Starfire" driver, however I made a few updates that people should know about: - I created a version of the driver for FreeBSD 2.2.x. You can find it at http://www.freebsd.org/~wpaul/Adaptec/2.2. Note: while I have verified that this code compiles, I have not been able to test it. There should not be any problems, but as always, Murphy's Law applies. - I found a bug today which is that sf_stats_update() required splimp() protection. I use the indirect register access method which is done in two stages: first you set the indirect address register to the register offset that you want to play with, then you access it via the indirect data register. However sf_stats_update() was interruptible which means that it was possible for the interrupt handler to run in between the first and second stages, which caused the stats updater to modify incorrect register locations. This bug would manifest itself in the form of watchdog timeouts and the 'collisions' counter sometimes reporting wildly incorrect values. I corrected this problem and updated the driver sources for each FreeBSD version (including 2.2.x) and recompiled the KLD module for FreeBSD 4.0-current. - The pre-compiled KLD module for FreeBSD 4.0-current now includes BPF support, since I have been told that there stubs that should allow BPF-enabled drivers to work even if BPF support isn't compiled into the kernel. - I added a README at http://www.freebsd.org/~wpaul/Adaptec which explains how to install the driver on FreeBSD 2.2.x, 3.x and 4.0. Also, a quick note about the Adaptec cards. I said previously that the Duralink adapters were Adaptec's replacement for their older DEC tulip-based cards. Adaptec still sells multiport adapters based on the 21x4x chip, however I believe they use the 21143 now since Intel discontinued production of the 21140 and supplies are drying up. It is possible that Adaptec may stop production on the older cards though now that they have their own high performance chipset. The Duralink cards may also be preferable in some cases since they are 64-bit PCI devices. Anyway: I would appreciate it if people could test the driver and get back to me with some feedback. I hope to merge this into the -current branch soon. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 9:47:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 1B06114CA0 for ; Thu, 22 Jul 1999 09:47:07 -0700 (PDT) (envelope-from rminnich@acl.lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id KAA147499 for ; Thu, 22 Jul 1999 10:46:55 -0600 (MDT) Date: Thu, 22 Jul 1999 10:46:55 -0600 From: "Ronald G. Minnich" To: freebsd-hackers@FreeBSD.ORG Subject: Re: Filesystem question... In-Reply-To: <19990722153917.E18381@mother.RedBrick.DCU.IE> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG what if you're not root, and you want to add your own file system to your file system name space? It seems a lot of these systems assume root access, which seems unrealistic to me. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 9:53:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 5B2931551C for ; Thu, 22 Jul 1999 09:52:56 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA83543; Thu, 22 Jul 1999 09:51:38 -0700 (PDT) (envelope-from dillon) Date: Thu, 22 Jul 1999 09:51:38 -0700 (PDT) From: Matthew Dillon Message-Id: <199907221651.JAA83543@apollo.backplane.com> To: Len Conrad Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD: the stealth OS? References: <4.2.0.56.19990722155323.020b1a50@go2france.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Cool with the geeks beecause it's "unknown". : :http://www.msnbc.com/news/292376.asp : :Len I love the quote by Matthew Fuller at the end: "There's a lot of things that Linux is 'better' at, and a lot of things FreeBSD is 'better' at, and a lot of those things can easily fluctuate on a daily or weekly basis," said Fuller, who maintains a Linux vs BSD Web page. "Thus, any definitive narrow statement that can be made is usually obsolete before anyone hears it.". Perfect! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 9:53:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rebel.net.au (rebel.rebel.net.au [203.20.69.66]) by hub.freebsd.org (Postfix) with ESMTP id 9012114C20 for ; Thu, 22 Jul 1999 09:53:51 -0700 (PDT) (envelope-from kkenn@rebel.net.au) Received: from 203.20.69.80 (dialup-10.rebel.net.au [203.20.69.80]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id CAA27079 for ; Fri, 23 Jul 1999 02:23:35 +0930 Received: (qmail 10413 invoked from network); 22 Jul 1999 16:53:41 -0000 Received: from localhost (kkenn@127.0.0.1) by localhost with SMTP; 22 Jul 1999 16:53:41 -0000 Date: Fri, 23 Jul 1999 02:23:39 +0930 (CST) From: Kris Kennaway Reply-To: kkenn@rebel.net.au To: "Ronald G. Minnich" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Filesystem question... 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 Thu, 22 Jul 1999, Ronald G. Minnich wrote: > what if you're not root, and you want to add your own file system to your > file system name space? It seems a lot of these systems assume root > access, which seems unrealistic to me. Well, if you're running it as a kernel module then obviously you need root permissions to load it. If it's running as a userland process, then there's no reason why you can't run it as a user. mount presumably wouldn't care as long as you had access rights to the underlying objects (mountpoint + stacking layer process). Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 9:58:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from yoshi.iq.org (yoshi.iq.org [203.4.184.224]) by hub.freebsd.org (Postfix) with ESMTP id 1B5A314CA2 for ; Thu, 22 Jul 1999 09:58:27 -0700 (PDT) (envelope-from proff@yoshi.iq.org) Received: (from proff@localhost) by yoshi.iq.org (8.8.8/8.8.8) id CAA01041; Fri, 23 Jul 1999 02:54:42 +1000 (EST) Date: Fri, 23 Jul 1999 02:54:42 +1000 (EST) Message-Id: <199907221654.CAA01041@yoshi.iq.org> From: Julian Assange To: hackers@freebsd.org Subject: Looking for (commercial?) bandwith on NetBSD/FreeBSD machines Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm involved in a linguistic analysis project which requires reasonable quantities of bandwidth. Due to duopolistic price-fixing, and volume-charing obtaining this bandwith in Australia is a very expensive proposition indeed (US$0.13/Mb!). I'm trying to find a co-hosting (or equivalent) solution, preferably on NetBSD or FreeBSD machines, although this is not essential and I could always provide the machine. Bandwidth usage would be about 4-10Gb/day incoming during the next few months. I also have sizeable disk requirements, which could be forfilled by 2-4x 17GB ATA/IDE -- unfortunately the equivalent in scsi is a little out of my budget. Suggestions? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 9:59:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 451E515374 for ; Thu, 22 Jul 1999 09:59:18 -0700 (PDT) (envelope-from rminnich@acl.lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id KAA129262 for ; Thu, 22 Jul 1999 10:59:18 -0600 (MDT) Date: Thu, 22 Jul 1999 10:59:18 -0600 From: "Ronald G. Minnich" To: freebsd-hackers@FreeBSD.ORG Subject: Re: Filesystem question... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Jul 1999, Kris Kennaway wrote: > Well, if you're running it as a kernel module then obviously you need root > permissions to load it. If it's running as a userland process, then > there's no reason why you can't run it as a user. mount presumably > wouldn't care as long as you had access rights to the underlying objects > (mountpoint + stacking layer process). well, you'll have to tell me more. (i have to get my freebsd source tree back :-) ) Are you saying that as an ordinary user I can mount something on top of /tmp, for example? Is the suser() check still in the mount system call? ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 10:19:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2334214CAA for ; Thu, 22 Jul 1999 10:19:00 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA50778; Thu, 22 Jul 1999 11:18:58 -0600 (MDT) (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 LAA09342; Thu, 22 Jul 1999 11:19:13 -0600 (MDT) Message-Id: <199907221719.LAA09342@harmony.village.org> To: Bill Paul Subject: Re: [FreeBSD-net-jp 1746] [FYI] Adaptec AIC-6915 "Starfire" ethernet controller driver and plus question compaq presario dec et Cc: morita@jts.ntts.co.jp (morita), freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 21 Jul 1999 10:00:03 EDT." <199907211400.KAA00687@skynet.ctr.columbia.edu> References: <199907211400.KAA00687@skynet.ctr.columbia.edu> Date: Thu, 22 Jul 1999 11:19:13 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [[ Warning, you'll need something which can display Kanji to be able to read what I've written. I'm using mule and netscape. I've tried to make the non-Japanese parts separate enough that if you only understand English and have only english viewing programs, you can safely ignore the strange sequences of characters resembling TECO progragms and/or line noise. ]] In message <199907211400.KAA00687@skynet.ctr.columbia.edu> Bill Paul writes: : Sorry, but I'm just a dumb american: I can't read this. $B?=$7Lu$4$6$$$^$9!#;d$OJF9q?M$G$9!#FI$_$^$;$s!#(B (which translates, if I've gotten the Japanese correct, as "I'm very sorry. I'm an american. I cannot read this.") >$B%3%s%Q%C%/!!(BPRESARIO$B!!(B2274$B!!$K(BFreeBSD3.2$B%$%s%9%H!<%k$7$?$N$G$9$,!"(B > NIC$B!'!!(BDEC 21143-based $B$H%S%G%*%+!<%I!'(BSiS5598$B$N@_Dj$,$&$^$/$$$-$^$;$s!"8=:_(B >$BF0$+$7$F$k(B >$BJ}$,$$$i$7$?$i65$($F$/$@$5$$!#(B Using Netscape and http://www.dgs.monash.edu.au/cgi-bin/cgiwrap/jwb/wwwjdic?9T (and my little knowledge of Japanese grammar) I believe that this says something along the lines of: Compaq PRESARIO 2274 with FreeBSD 3.2 installed, but NIC: DEC 21143-based and Video Card: SiS5598 which won't [attach]. In the current [system], can you please instruct me how [to make it work]. The text in [] is guessed based on context, I didn't look up the words in hiragana that I didn't already know, or for which the literal translation didn't make sense. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 10:28:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rebel.net.au (rebel.rebel.net.au [203.20.69.66]) by hub.freebsd.org (Postfix) with ESMTP id 4352614C02 for ; Thu, 22 Jul 1999 10:28:49 -0700 (PDT) (envelope-from kkenn@rebel.net.au) Received: from 203.20.69.80 (dialup-10.rebel.net.au [203.20.69.80]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id CAA26933 for ; Fri, 23 Jul 1999 02:05:55 +0930 Received: (qmail 91625 invoked from network); 22 Jul 1999 16:35:52 -0000 Received: from localhost (kkenn@127.0.0.1) by localhost with SMTP; 22 Jul 1999 16:35:52 -0000 Date: Fri, 23 Jul 1999 02:05:49 +0930 (CST) From: Kris Kennaway Reply-To: kkenn@rebel.net.au To: Tiny Non Cats Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Filesystem question... In-Reply-To: <19990722153917.E18381@mother.RedBrick.DCU.IE> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Jul 1999, Tiny Non Cats wrote: > On Thu, Jul 22, 1999 at 10:06:04AM -0400 David E. Cross said: > > Since I am planning on writing userfs in order to impliment 'nsd' (and > > > This may be completely useless, because I've not been following what you want > to do with 'nsd', but you may find > > http://www.cs.columbia.edu/~ezk/research/security/index.html > > interesting. It's a description of 'WrapFS', written by Erik Zadok. It's a > stackable filesystem template written as a kernel module, and can be extended to > do all sorts of stuff with relative ease, apparently. Cool. It's amazing what pops up on these lists sometimes! *sigh* If only I had some free time before starting my PhD :-( Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 10:34: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 4A84914CAA for ; Thu, 22 Jul 1999 10:34:05 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA84040; Thu, 22 Jul 1999 10:32:50 -0700 (PDT) (envelope-from dillon) Date: Thu, 22 Jul 1999 10:32:50 -0700 (PDT) From: Matthew Dillon Message-Id: <199907221732.KAA84040@apollo.backplane.com> To: Doug Rabson Cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: Anyone know how to dim and SGI flat panel? References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :XFree86 has an i2c driver in it for talking to monitors so it sounds as if :it should see it. : :-- :Doug Rabson Mail: dfr@nlsystems.com :Nonlinear Systems Ltd. Phone: +44 181 442 9037 : :... : :That is how I believe that DMPS communications are transported to the :display. Unfortunately, the DPMS specification is a VESA-proprietary :document so you will have to either join the XFree86 project or sponsor :FreeBSD as a VESA member (that would be nice 8). : :-- :\\ The mind's the standard \\ Mike Smith Ahhh. Interesting. Ah, the XFree ftp finished. Hmm. the DPMS stuff looks promising but I don't see an I128 port yet. Shoot. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 10:36:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (Postfix) with SMTP id 3F3CA1528B for ; Thu, 22 Jul 1999 10:36:13 -0700 (PDT) (envelope-from vev@michvhf.com) Received: (qmail 19429 invoked by uid 1001); 22 Jul 1999 17:35:26 -0000 Date: Thu, 22 Jul 1999 13:35:26 -0400 (EDT) From: Vince Vielhaber To: Brian McGroarty Cc: freebsd-hardware , hackers Subject: RE: 1373 sound chip 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 Thu, 22 Jul 1999, Brian McGroarty wrote: > There's a patch for the 1371 floating around that seems to work for the 1373 > as well. > > Search the archive of FreeBSD-questions for "1371". > > Last I saw, the search page was still confused - you need to put "1371" in > the web search field at the top, but still click the mailing list search > button down below. Found it and applied the patch. Still no go. The 1373 is IDing as a 1371 from BIOS, but FreeBSD doesn't see it at all. Looking at the other messages, I see some folks using 'device pcm0 at nexus?' but they're also running -current. I tried that under 3.2 and after it told me that pcm0 is only good with ISA it seg-faulted and blew core. There was also mention of another patch from Joachim Kuebart for PCI, but no mention where to find it. Vince. > > > > -----Original Message----- > From: Vince Vielhaber [mailto:vev@michvhf.com] > Sent: Wednesday, July 21, 1999 6:54 PM > To: Brian McGroarty; freebsd-hardware; hackers > Subject: 1373 sound chip > > I sent this to multimedia about a week ago and didn't get a response > so I'm trying it here [hackers & hardware] (with minor mods): > > > I'm setting up a new machine that has onboard sound in the form of an > ES1373 Creative (Ensoniq, probably). Visual config shows an unknown > device as ES0 and pcm0 doesn't find anything (tried various forms in > the kernel config for that one, the last one was/is: > > device pcm0 > > Is there any driver for this chip? Under windows it uses the SoundBlaster > AudioPCI 64V driver. So far I haven't found any specs on Creative's or > Ensoniq's website. Can someone shed some light on possibly adapting the > pcm driver to this chip (like how to ID, etc.) ? > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 11:49:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 24FD114E66; Thu, 22 Jul 1999 11:49:16 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id LAA22301; Thu, 22 Jul 1999 11:47:48 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id LAA15722; Thu, 22 Jul 1999 11:47:00 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA15623; Thu, 22 Jul 99 11:47:43 PDT Message-Id: <3797674F.71098FA7@softweyr.com> Date: Thu, 22 Jul 1999 12:47:43 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Matthew Dillon Cc: Len Conrad , freebsd-hackers@FreeBSD.ORG, freebsd-advocates@freebsd.org Subject: Re: FreeBSD: the stealth OS? References: <4.2.0.56.19990722155323.020b1a50@go2france.com> <199907221651.JAA83543@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > :Cool with the geeks beecause it's "unknown". > : > :http://www.msnbc.com/news/292376.asp > : > :Len > > I love the quote by Matthew Fuller at the end: > > "There's a lot of things that Linux is 'better' at, and a > lot of things FreeBSD is 'better' at, and a lot of those > things can easily fluctuate on a daily or weekly basis," > said Fuller, who maintains a Linux vs BSD Web page. > "Thus, any definitive narrow statement that can be made > is usually obsolete before anyone hears it.". I guess he didn't manage to get in touch with Terry. We spoke at length on Tuesday; I'm astonished how fast this came out. The writer was a DefCon for the first time; that was the first time HE had heard of BSD, and was relatively astonished to discover what a large and thriving community it is. I'd like to point out a quote from the March Daemon's Advocate at this point: ...the BSD community is just about reaching the size to be noted by the popular computing press, at least in the USA, and that what little they know of us is good. We must strive to keep this positive viewpoint. We're just finally starting to get our OWN press, where WE are the lead item and compared to Linux, rather than the other way around. This is helped by the fact that, as you can see in the MSNBC article, BSD users rarely claim that BSD is the solution to every problem on the planet, but rather just a good tool to solve problems that are commonly encountered. I am dissappointed he didn't include my plug for companies embedding BSD in products, though. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@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 Jul 22 12: 8:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1x.pvt.net (ns.pvt.net [194.149.105.18]) by hub.freebsd.org (Postfix) with ESMTP id AAE7314D82 for ; Thu, 22 Jul 1999 12:08:15 -0700 (PDT) (envelope-from papezik@pvt.net) Received: from mail1.pvt.net (news.pvtnet.cz [194.149.101.166]) by ns1x.pvt.net (8.9.3/8.9.3) with ESMTP id VAA10498 for ; Thu, 22 Jul 1999 21:08:11 +0200 Received: from pvt.net (papezik.pvt.net [194.149.103.213]) by mail1.pvt.net (8.9.3/8.9.3) with ESMTP id VAA19584; Thu, 22 Jul 1999 21:08:06 +0200 (CEST) Message-ID: <37976C03.A4A797A7@pvt.net> Date: Thu, 22 Jul 1999 21:07:47 +0200 From: Papezik Milon X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: cs, cz, sk, en MIME-Version: 1.0 To: hackers@freebsd.org Subject: Squid - a bug in src/sys/kern/uipc_socket.c Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, please don't kill me if it's "well known issue": I've found that there is a report on Squid site, which describes a problem with FreeBSD IPC and includes suggested fix. I verified that this suggested fix is not included in 3.2-RELEASE. I wonder, if it is really a bug, as I cannot find it in PR database. Could someone please comment on this report/bug/suggested fix and if/when the fix could/will be submited? original URL: http://squid.nlanr.net/Squid/FAQ/FAQ-14.html#ss14.2 Thanks in advance, Milon -- papezik@pvt.net ------------ bug report and suggested fix --------- mbuf size We noticed an odd thing with some of Squid's interprocess communication. Often, output from the dnsserver processes would NOT be read in one chunk. With full debugging, it looks like this: 1998/04/02 15:18:48| comm_select: FD 46 ready for reading 1998/04/02 15:18:48| ipcache_dnsHandleRead: Result from DNS ID 2 (100 bytes) 1998/04/02 15:18:48| ipcache_dnsHandleRead: Incomplete reply ....other processing occurs... 1998/04/02 15:18:48| comm_select: FD 46 ready for reading 1998/04/02 15:18:48| ipcache_dnsHandleRead: Result from DNS ID 2 (9 bytes) 1998/04/02 15:18:48| ipcache_parsebuffer: parsing: $name www.karup.com $h_name www.karup.inter.net $h_len 4 $ipcount 2 38.15.68.128 38.15.67.128 $ttl 2348 $end Interestingly, it is very common to get only 100 bytes on the first read. When two read() calls are required, this adds additional latency to the overall request. On our caches running Digital Unix, the median dnsserver response time was measured at 0.01 seconds. On our FreeBSD cache, however, the median latency was 0.10 seconds. Here is a simple patch to fix the bug: =================================================================== RCS file: /home/ncvs/src/sys/kern/uipc_socket.c,v retrieving revision 1.40 retrieving revision 1.41 diff -p -u -r1.40 -r1.41 --- src/sys/kern/uipc_socket.c 1998/05/15 20:11:30 1.40 +++ /home/ncvs/src/sys/kern/uipc_socket.c 1998/07/06 19:27:14 1.41 @@ -31,7 +31,7 @@ * SUCH DAMAGE. * * @(#)uipc_socket.c 8.3 (Berkeley) 4/15/94 - * $Id: FAQ.sgml,v 1.75 1999/07/06 16:07:36 wessels Exp $ + * $Id: FAQ.sgml,v 1.75 1999/07/06 16:07:36 wessels Exp $ */ #include @@ -491,6 +491,7 @@ restart: mlen = MCLBYTES; len = min(min(mlen, resid), space); } else { + atomic = 1; nopages: len = min(min(mlen, resid), space); /* Another technique which may help, but does not fix the bug, is to increase the kernel's mbuf size. The default is 128 bytes. The MSIZE symbol is defined in /usr/include/machine/param.h. However, to change it we added this line to our kernel configuration file: options MSIZE="256" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 12:30:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id E3D4514DA1 for ; Thu, 22 Jul 1999 12:30:06 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id OAA11857 for hackers@freebsd.org; Thu, 22 Jul 1999 14:30:13 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <199907221930.OAA11857@celery.dragondata.com> Subject: rtprio and fifo's To: hackers@freebsd.org Date: Thu, 22 Jul 1999 14:30:13 -0500 (CDT) 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 know the evils associated with using rtprio, but I have a real real-time application that needs to service data very quickly when it is needed from a piece of hardware. This daemon reads from a special device. The driver's read handler puts it to sleep, and wakes it back up when an interrupt comes in. Other processes communicate with this daemon using fifo's. (They send it packetized commands, and every once in a while through the loop it checks the fifo for data). According to my Stevens book here, fifo and pipe writes are guaranteed to be atomic, as long as the write is less than PIPE_BUF. (which is 512 bytes here). Unless I'm using rtprio, this is true. Apparently I'm somehow stealing execution away from the child processes during their write() in the middle of it. Occasionally, when I should be reading 192 bytes in from the fifo, i'll do one read of 89 bytes, and another of 103. This wasn't hard to code around, I just kept a buffer, and only processed it when I had a complete packet. However, about once every 6-8 hours, the daemon will get stuck in 'sbwait', and no amount of kicking it will make it wake back up. If I don't use rtprio, this doesn't happen, but the process becomes too slow to work. Has anyone run into this before, or does anyone have any suggestions on how I might fix this? I may try SYSV style message queues next, if I"m not able to fix the fifo problem. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 12:48:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id BF6EC156E9 for ; Thu, 22 Jul 1999 12:48:14 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id OAA20918; Thu, 22 Jul 1999 14:48:09 -0500 (CDT) Date: Thu, 22 Jul 1999 14:48:09 -0500 From: "Matthew D. Fuller" To: Matthew Dillon Cc: Len Conrad , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD: the stealth OS? Message-ID: <19990722144808.J12369@futuresouth.com> References: <4.2.0.56.19990722155323.020b1a50@go2france.com> <199907221651.JAA83543@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199907221651.JAA83543@apollo.backplane.com>; from Matthew Dillon on Thu, Jul 22, 1999 at 09:51:38AM -0700 X-OS: FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 22, 1999 at 09:51:38AM -0700, a little birdie told me that Matthew Dillon remarked > > I love the quote by Matthew Fuller at the end: > > "There's a lot of things that Linux is 'better' at, and a > lot of things FreeBSD is 'better' at, and a lot of those > things can easily fluctuate on a daily or weekly basis," > said Fuller, who maintains a Linux vs BSD Web page. > "Thus, any definitive narrow statement that can be made > is usually obsolete before anyone hears it.". > > Perfect! Thank you, my fans! Please leave your monetary contributions in the hat on your way out ;> -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ FutureSouth Communications | ISPHelp ISP Consulting "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 12:49:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id B1DD915793; Thu, 22 Jul 1999 12:49:31 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id MAA08065; Thu, 22 Jul 1999 12:49:23 -0700 (PDT) Date: Thu, 22 Jul 1999 12:49:22 -0700 (PDT) From: Julian Elischer To: sthaug@nethelp.no Cc: des@yes.no, hackers@freebsd.org, bde@freebsd.org Subject: Re: IDE breakage In-Reply-To: <46713.932642742@verdi.nethelp.no> 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 My fault I accidentally replaced a PAGE_MASK with a PAGE_SIZE. the resulting bug only changes teh behaviour on unaligned pages which are only possible on the raw device. (e.g. fsck) the Cyrix 5530 we used to test has a bug where we cannot do unalligned transfers by DMA anyhow, so we never hit this bug.. fixed in -current .... will be fixxed in -stable when I reintroduce the patch... julian On Thu, 22 Jul 1999 sthaug@nethelp.no wrote: > > I'm experiencing serious problems with DMA (even normal DMA, not UDMA) > > on recent versions of -STABLE. Here's an excerpt from messages; kernel > > #3 is a recent -STABLE (yesterday's sources), while kernel #2 is > > 3.2-RELEASE. The config file for both is identical. > > I can confirm problems with DMA from IDE disks in -STABLE. The problems > seem to have been introduced in > > $Id: ide_pci.c,v 1.28.2.1 1999/07/20 22:58:20 julian Exp $ > > And the effect for me is that the system stops in singleuser mode, with > a "DMA failure" message. This is on a 440BX/PII-350 system. > > Reverting to 1.28 (from 17. January 1999) fixes the problems. > > Please back out 1.28.2.1, at least in -STABLE. > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > > 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 Jul 22 13: 6: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from behemoth.lehub.com (behemoth.lehub.com [209.24.238.69]) by hub.freebsd.org (Postfix) with ESMTP id BB20114EC2 for ; Thu, 22 Jul 1999 13:05:56 -0700 (PDT) (envelope-from shibumi@lehub.com) Received: from miranda.lehub.com (miranda.lehub.com [209.24.238.77]) by behemoth.lehub.com (8.9.3/8.9.3) with ESMTP id MAA07364 for ; Wed, 21 Jul 1999 12:45:24 -0700 (PDT) (envelope-from shibumi@lehub.com) Received: from localhost (localhost [127.0.0.1]) by miranda.lehub.com (8.9.3/8.9.3) with ESMTP id MAA00781 for ; Wed, 21 Jul 1999 12:44:29 -0700 (PDT) (envelope-from shibumi@lehub.com) Message-Id: <199907211944.MAA00781@miranda.lehub.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@FreeBSD.ORG Subject: Re: poor ethernet performance? In-reply-to: Your message of "Wed, 21 Jul 1999 00:33:31 PDT." <199907210733.AAA25177@apollo.backplane.com> Reply-To: shibumi@lehub.com X-Disclaimer: Unless otherwise noted below, this is not a policy statement X-Url: http://www.shockwave.org/~shibumi Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Jul 1999 12:44:29 -0700 From: "Kenton A. Hoover" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You can hijack the MAC address after the CAM table (not ARP cache) times out for the switches. However, you can't just listen to their traffic unless you're on a span port (and span ports don't always work correctly). VLANing has a number of goals, of which you are listing only one. Another is to permit any net to appear on any switch within the switch fabric. VLANs are usually used in a form that spans multiple switches, not just using VLANs on a single switch. At an installation I put together in India, we used VLANs to allow us to better use IP addresses in a strange physical layout. When we were building out our New Site Architecture at Cisco in San Jose, we used VLANs to cut down the number of routing components necessary and further to take advantage of Layer 3 short-cutting in a number of spots around the buildings. On Wed, 21 Jul 1999 00:33:31 PDT, Sendmail channeled Matthew Dillon saying: > The switch routes traffic based on its ARP cache. While you cannot > easily monitor another port's traffic, you can take over its MAC address > and steal its traffic. > > Cisco VLANs perform a different function. Remember that a logical ethern et > segment is typically routed by a single network route. For example, > a class C or a subnetted class C. The catalyst allows you to throw > machines into different VLAN buckets which, in addition to the better > security, allows you to assign separate subnets to each bucket. The > switch itself doesn't care, but this can reduce global ARP traffic > significantly. Catalysts can have hundreds of ports stuffed into them. (ex-of Cisco Systems) | Kenton A. Hoover | shibumi@marchordie.org | | Private Citizen | | | San Francisco, California | | |===================== http://www.shockwave.org/~shibumi ====================| | A non-vegetarian anti-abortionist is a contradiction in terms. | | -- Phyllis Schlafly | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 13:25:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 3027814E11; Thu, 22 Jul 1999 13:25:34 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id NAA09256; Thu, 22 Jul 1999 13:24:37 -0700 (PDT) Date: Thu, 22 Jul 1999 13:24:36 -0700 (PDT) From: Julian Elischer To: John Hay Cc: obrien@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Will FreeBSD ever see native IPv6 ?? In-Reply-To: <199907220822.KAA11656@zibbi.mikom.csir.co.za> 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 they ARE doing it, but they haven't got the merged TCP stack quite right they are not publically anouncing anything till it works... On Thu, 22 Jul 1999, John Hay wrote: > Are you just teasing or are you serious? > > I searched through their site (again), but except for being mentioned > in their TODO for the past few months, I can't find anything that > indicates that they or anyone else is working on it. They may be, but > it isn't visible anywhere where I have looked. It would be nice if > there was some place to follow their progress, because I'm also one > of the people that would like to see IPv6 integrated into FreeBSD. > > John > -- > John Hay -- John.Hay@mikom.csir.co.za > > > > > FreeBSD will have native IPV6 within a matter of weeks at this stage.. > > the code is being readied as we speak. see www.kame.net . 3 sets of > > developers for FreeBSD IPV6 have merged their efforts and the result of > > this should be available by the end of summer (Northern). (which isn't > > far away now..) > > > > On Wed, 21 Jul 1999, David O'Brien wrote: > > > > > So is FreeBSD *EVER* going to see native IPv6 ?? > > > I attended a talk by a group of Intrusion Detection researchers. They > > > were basing their research on FreeBSD because they needed divert > > > sockets and found FreeBSD worked perfectly for this in this respect. > > > However, once they needed IPv6 and IPsec guess what happened??? They > > > moved to Linux and now have such a time investment in their custom kernel > > > hacks FreeBSD will never be an option for them again. > > > > > > NetBSD and OpenBSD get more and more coverage from IPv6/IPsec > > > capabilities every day. FreeBSD has lost considerable ground if we want > > > to be a platform of choice for network and security researchers. > > > > > > Now ever LSOF has IPv6 support for NetBSD and OpenBSD... > > > > > 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 Jul 22 13:25:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 35F71155E8 for ; Thu, 22 Jul 1999 13:25:41 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 57421 invoked by uid 1001); 22 Jul 1999 20:24:57 +0000 (GMT) To: freebsd-hackers@freebsd.org, freebsd-smp@freebsd.org Subject: rndcontrol and SMP From: sthaug@nethelp.no X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 22 Jul 1999 22:24:57 +0200 Message-ID: <57419.932675097@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG rndcontrol doesn't work very well for SMP systems. I have a system here with IRQs 16 and 18 for Ethernet and SCSI: fxp0: rev 0x05 int a irq 18 on pci0.10.0 ahc0: rev 0x00 int a irq 16 on pci0.12.0 and I'd like to use these with rndcontrol. However, the ioctl chokes on IRQ >= 16. From i386/i386/mem.c: /* * XXX the data is 16-bit due to a historical botch, so we use * magic 16's instead of ICU_LEN and can't support 24 interrupts * under SMP. */ intr = *(int16_t *)data; if (cmd != MEM_RETURNIRQ && (intr < 0 || intr >= 16)) return (EINVAL); What is needed to make this support a more sensible number of IRQs? Also, rndcontrol naturally returns an error message, which could have been better: rndcontrol: rndcontrol: Invalid argument rndcontrol uses warn() with argv[0] as the argument - but warn() is documented to always print the program name. So it gets doubled. Below is a patch against 3.2-STABLE to make it slightly more intelligent, so we get an error message like this instead: rndcontrol: setting irq 16: Invalid argument Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- *** rndcontrol.c.orig Mon Oct 13 13:08:47 1997 --- rndcontrol.c Thu Jul 22 22:06:52 1999 *************** *** 76,82 **** printf("%s: setting irq %d\n", argv[0], irq); result = ioctl(fd, MEM_SETIRQ, (char *)&irq); if (result == -1) { ! warn("%s", argv[0]); return (1); } break; --- 76,82 ---- printf("%s: setting irq %d\n", argv[0], irq); result = ioctl(fd, MEM_SETIRQ, (char *)&irq); if (result == -1) { ! warn("setting irq %d", irq); return (1); } break; *************** *** 86,92 **** printf("%s: clearing irq %d\n", argv[0], irq); result = ioctl(fd, MEM_CLEARIRQ, (char *)&irq); if (result == -1) { ! warn("%s", argv[0]); return (1); } break; --- 86,92 ---- printf("%s: clearing irq %d\n", argv[0], irq); result = ioctl(fd, MEM_CLEARIRQ, (char *)&irq); if (result == -1) { ! warn("clearing irq %d", irq); return (1); } break; *************** *** 98,104 **** if (verbose) { result = ioctl(fd, MEM_RETURNIRQ, (char *)&irq); if (result == -1) { ! warn("%s", argv[0]); return (1); } printf("%s: interrupts in use:", argv[0]); --- 98,104 ---- if (verbose) { result = ioctl(fd, MEM_RETURNIRQ, (char *)&irq); if (result == -1) { ! warn(""); return (1); } printf("%s: interrupts in use:", argv[0]); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 13:47:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 38D8D14A13 for ; Thu, 22 Jul 1999 13:47:19 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id NAA10053; Thu, 22 Jul 1999 13:45:33 -0700 (PDT) Date: Thu, 22 Jul 1999 13:45:33 -0700 (PDT) From: Julian Elischer To: Peter Jeremy Cc: jwd@unx.sas.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Proposal for new syscall to close files In-Reply-To: <99Jul22.115150est.40336@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am not sure I see a need for this syscall... julian On Thu, 22 Jul 1999, Peter Jeremy wrote: > "John W. DeBoskey" wrote: > > I like this approach. I have a number of often spawned daemon > >processes that could benefit from this. > I don't suppose that you have any statistics showing that the > for (i = 3; i < getdtablesize(); i++) close(i); > approach would be too slow? > > > For naming convention considerations, I might suggest 'closeall' > >or 'closefdset' or something similar... at least have 'close' in > >name... :-) > > I'm not really keen on the name either - but I couldn't think of > anything better. `closeall' isn't really descriptive since it doesn't > close all the FDs. `closefdset' suggests (to me, anyway) the opposite > behaviour: ie closing the FDs specified in the passed fd_set, instead > of closing everything else. > > Peter > > > 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 Jul 22 13:53:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from melete.ch.intel.com (melete.ch.intel.com [143.182.246.25]) by hub.freebsd.org (Postfix) with ESMTP id 5474C14C4F for ; Thu, 22 Jul 1999 13:53:17 -0700 (PDT) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by melete.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id NAA10818 for ; Thu, 22 Jul 1999 13:52:34 -0700 (MST) Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.8 1999/04/16 15:25:49 steved Exp steved $) with ESMTP id NAA06165 for ; Thu, 22 Jul 1999 13:52:33 -0700 (MST) X-Envelope-To: X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id QAA05818; Thu, 22 Jul 1999 16:52:34 -0400 (EDT) From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14231.33937.454645.22076@hip186.ch.intel.com> Date: Thu, 22 Jul 1999 13:52:33 -0700 (MST) To: freebsd-hackers@freebsd.org Subject: SURVEY: Sound cards that work under FreeBSD X-Mailer: VM 6.72 under Emacs 19.34.1 X-Euphoria: http://www.webnl.com/senff/leppard_start.html Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I'm working with Nik Clayton to update FAQ 3.15 to give a more comprehensive list of sound cards known to work with FreeBSD. That's why I'm sending out this template to this list. Please take the time to fill it out with information regarding your sound card so that we can compile a better list for posterity. I will do my best to keep the list current as FreeBSD evolves (please send to me or cc: me along with the list--it'll be easier to filter responses than grabbing them out of -hackers-digest :). Please be as specific about makes, models, chipsets, etc. as you can. The author of the first mail received regarding a specific sound card will be listed as the contributor of that information (unless he/she does not want his/her e-mail address listed :). Please note also that I would like information about sound cards that do NOT work (as of yet) under FreeBSD if anyone has experience with them. Hopefully, this will go well and we will be able to branch out into other pieces of supported/non-supported hardware in the future. Thank you. Survey: ------- 1) The sound card make and model/chipset. Please be as specific as you can with board rev numbers if possible. Please include wether the card is ISA or PCI. 2) FreeBSD version(s) it was tested with. List *all* versions of FreeBSD for which you can verify that the sound card does/doesn't work (don't include -BETA or -SNAP releases but dates on -STABLE and -CURRENT branches are welcome). 3) Appropriate lines from your kernel config file / PNP setup. i.e. what did you have to do to get this card working? Did you need patches not committed to a particular branch (if so URLs would be welcome)? Do you use OSS drivers instead? 4) Sample dmesg output for properly configured device. Show the world what boot messages relate to the device after properly configured. 5) Miscellaneous notes. State anything "not obvious" to the casual FreeBSD user. Good examples might be, "volume is 0 by default, use mixer(1) to adjust at boot time," or "sh MAKEDEV snd1 for the 1st device, not snd0." 6) Is it OK to publish your e-mail address / name as the contributor of this information? You may type in an anti-spam version of your e-mail address below if you would like that option instead. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds CEG, CCE, Next Generation Flows, HLA | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 13:58:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id C990714E6C for ; Thu, 22 Jul 1999 13:58:35 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA87639; Thu, 22 Jul 1999 13:56:42 -0700 (PDT) (envelope-from dillon) Date: Thu, 22 Jul 1999 13:56:42 -0700 (PDT) From: Matthew Dillon Message-Id: <199907222056.NAA87639@apollo.backplane.com> To: Papezik Milon Cc: hackers@FreeBSD.ORG Subject: Re: Squid - a bug in src/sys/kern/uipc_socket.c References: <37976C03.A4A797A7@pvt.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This isn't really a bug since this is a TCP connection. TCP makes no guarentees that atomic writes will show up as atomic reads, and the squid code shouldn't be making that assumption. On the otherhand, the proposed fix appears to be an excellent performance optimization. It is basically only turning 'atomic' on for relatively small writes, which should be a win for a receiver whether over a localhost connection or a real network. I can't imagine that it would cause a performance loss in any other situation -- it might result in a slightly smaller-then-full-sized TCP packet occassionally in a stream but that's about it. I think committing this would be beneficial. Would someone w/ commit privs care to review and then commit this bit? -Matt Matthew Dillon :Hi, : :please don't kill me if it's "well known issue": : :I've found that there is a report on Squid site, which :describes a problem with FreeBSD IPC and includes suggested fix. :I verified that this suggested fix is not included in 3.2-RELEASE. : :I wonder, if it is really a bug, as I cannot find it in PR database. : :Could someone please comment on this report/bug/suggested fix :and if/when the fix could/will be submited? : :original URL: :http://squid.nlanr.net/Squid/FAQ/FAQ-14.html#ss14.2 : : Thanks in advance, : Milon :-- :papezik@pvt.net : : :------------ bug report and suggested fix --------- :mbuf size : :We noticed an odd thing with some of Squid's interprocess communication. :Often, output from the dnsserver processes would NOT be read in one :chunk. With full debugging, it looks like this: : :1998/04/02 15:18:48| comm_select: FD 46 ready for reading :1998/04/02 15:18:48| ipcache_dnsHandleRead: Result from DNS ID 2 (100 :bytes) :1998/04/02 15:18:48| ipcache_dnsHandleRead: Incomplete reply :....other processing occurs... :1998/04/02 15:18:48| comm_select: FD 46 ready for reading :1998/04/02 15:18:48| ipcache_dnsHandleRead: Result from DNS ID 2 (9 :bytes) :1998/04/02 15:18:48| ipcache_parsebuffer: parsing: :$name www.karup.com :$h_name www.karup.inter.net :$h_len 4 :$ipcount 2 :38.15.68.128 :38.15.67.128 :$ttl 2348 :$end : :Interestingly, it is very common to get only 100 bytes on the first :read. When two read() calls are required, this adds additional latency :to the overall request. On our caches running Digital Unix, the median :dnsserver response time was measured at 0.01 seconds. On our FreeBSD :cache, however, the median latency was 0.10 seconds. : :Here is a simple patch to fix the bug: : :=================================================================== :RCS file: /home/ncvs/src/sys/kern/uipc_socket.c,v :retrieving revision 1.40 :retrieving revision 1.41 :diff -p -u -r1.40 -r1.41 :--- src/sys/kern/uipc_socket.c 1998/05/15 20:11:30 1.40 :+++ /home/ncvs/src/sys/kern/uipc_socket.c 1998/07/06 19:27:14 :1.41 :@@ -31,7 +31,7 @@ : * SUCH DAMAGE. : * : * @(#)uipc_socket.c 8.3 (Berkeley) 4/15/94 :- * $Id: FAQ.sgml,v 1.75 1999/07/06 16:07:36 wessels Exp $ :+ * $Id: FAQ.sgml,v 1.75 1999/07/06 16:07:36 wessels Exp $ : */ : : #include :@@ -491,6 +491,7 @@ restart: : mlen = MCLBYTES; : len = min(min(mlen, resid), space); : } else { :+ atomic = 1; : nopages: : len = min(min(mlen, resid), space); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 14:12:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 54EB614C10 for ; Thu, 22 Jul 1999 14:12:21 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA87754; Thu, 22 Jul 1999 14:09:32 -0700 (PDT) (envelope-from dillon) Date: Thu, 22 Jul 1999 14:09:32 -0700 (PDT) From: Matthew Dillon Message-Id: <199907222109.OAA87754@apollo.backplane.com> To: "John W. DeBoskey" Cc: jeremyp@gsmx07.alcatel.com.au (Peter Jeremy), freebsd-hackers@FreeBSD.ORG Subject: Re: Proposal for new syscall to close files References: <199907220123.VAA32548@bb01f39.unx.sas.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi, : : I like this approach. I have a number of often spawned daemon :processes that could benefit from this. One of the last process :we debugged where we had unwanted open filedescriptors was in :programs invoked by the cvs loginfo script. : : For naming convention considerations, I might suggest 'closeall' :or 'closefdset' or something similar... at least have 'close' in :name... :-) Well, when I weight the benefit of the savings in overhead for a single syscall verses a close() loop, and when I weigh the seriousness of introducing a syscall that would not be portable to other operating systems, and if I also take into account the work required to deal with descriptors after forking a daemon.... well, I don't think that adding a new syscall would be worth the relatively minor benefit nor do I think the improvement in performance would be noticeable. The benefit isn't great enough to warrent a new syscall in my view. I've written a number of forking daemons, most noteable my web server and my Diablo news transit system. I just don't think the reduced overhead would be noticeable over simply calling close(), and I didn't have any problems keeping track of which file descriptors to close in Diablo (and there could be 100+ descriptors). Keep in mind that after a fork these descriptors have a ref count > 1, meaning that the close() syscall is almost free. If you assume 5uS/close you are still talking quite a bit less then a millisecond to close a hundred descriptors. And that's pretty much the worst case I can think of. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 14:46:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id E51C714F29 for ; Thu, 22 Jul 1999 14:46:05 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id XAA05535 for hackers@FreeBSD.ORG; Thu, 22 Jul 1999 23:44:27 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id AAF1D884A; Thu, 22 Jul 1999 23:35:49 +0200 (CEST) (envelope-from roberto) Date: Thu, 22 Jul 1999 23:35:49 +0200 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: Will FreeBSD ever see native IPv6 ?? Message-ID: <19990722233549.A48954@keltia.freenix.fr> Mail-Followup-To: hackers@FreeBSD.ORG References: <199907220822.KAA11656@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i In-Reply-To: <199907220822.KAA11656@zibbi.mikom.csir.co.za>; from John Hay on Thu, Jul 22, 1999 at 10:22:30AM +0200 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5468 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to John Hay: > in their TODO for the past few months, I can't find anything that > indicates that they or anyone else is working on it. They may be, but I assure you they're working on it. Problem is they also have day jobs and some part of integration is complicated by export controls (the NRL code is more advanced IPsec-wise than our japanese friends). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #72: Mon Jul 12 08:26:43 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 14:56:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from users.anet-stl.com (users.anet-stl.com [209.145.150.20]) by hub.freebsd.org (Postfix) with ESMTP id 6101114F29 for ; Thu, 22 Jul 1999 14:56:46 -0700 (PDT) (envelope-from doogie@anet-stl.com) Received: from x ([209.145.151.138]) by users.anet-stl.com (8.9.3/8.8.5) with SMTP id QAA90574; Thu, 22 Jul 1999 16:53:06 -0500 (CDT) From: "Jason Young" To: "Matthew Dillon" , "Papezik Milon" Cc: Subject: RE: Squid - a bug in src/sys/kern/uipc_socket.c Date: Thu, 22 Jul 1999 16:43:31 -0500 Message-ID: <000501bed48b$3de34600$8a9791d1@y> 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 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal In-Reply-To: <199907222056.NAA87639@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's been committed before, and broke many things (X and CVSup come to mind). I have it compiled in locally on a few machines but it's definitely not suitable for general distribution until a solution is found that doesn't break applications. Jason Young accessUS Chief Network Engineer > -----Original Message----- > From: owner-freebsd-hackers@FreeBSD.ORG > [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of > Matthew Dillon > Sent: Thursday, July 22, 1999 3:57 PM > To: Papezik Milon > Cc: hackers@FreeBSD.ORG > Subject: Re: Squid - a bug in src/sys/kern/uipc_socket.c > > > This isn't really a bug since this is a TCP connection. > TCP makes > no guarentees that atomic writes will show up as atomic > reads, and > the squid code shouldn't be making that assumption. > > On the otherhand, the proposed fix appears to be an > excellent performance > optimization. It is basically only turning 'atomic' on > for relatively > small writes, which should be a win for a receiver > whether over a > localhost connection or a real network. I can't > imagine that it would > cause a performance loss in any other situation -- it > might result in > a slightly smaller-then-full-sized TCP packet > occassionally in a stream > but that's about it. > > I think committing this would be beneficial. Would > someone w/ commit > privs care to review and then commit this bit? > > -Matt > Matthew Dillon > > > :Hi, > : > :please don't kill me if it's "well known issue": > : > :I've found that there is a report on Squid site, which > :describes a problem with FreeBSD IPC and includes suggested fix. > :I verified that this suggested fix is not included in 3.2-RELEASE. > : > :I wonder, if it is really a bug, as I cannot find it in PR > database. > : > :Could someone please comment on this report/bug/suggested fix > :and if/when the fix could/will be submited? > : > :original URL: > :http://squid.nlanr.net/Squid/FAQ/FAQ-14.html#ss14.2 > : > : Thanks in advance, > : Milon > :-- > :papezik@pvt.net > : > : > :------------ bug report and suggested fix --------- > :mbuf size > : > :We noticed an odd thing with some of Squid's interprocess > communication. > :Often, output from the dnsserver processes would NOT be read in one > :chunk. With full debugging, it looks like this: > : > :1998/04/02 15:18:48| comm_select: FD 46 ready for reading > :1998/04/02 15:18:48| ipcache_dnsHandleRead: Result from > DNS ID 2 (100 > :bytes) > :1998/04/02 15:18:48| ipcache_dnsHandleRead: Incomplete reply > :....other processing occurs... > :1998/04/02 15:18:48| comm_select: FD 46 ready for reading > :1998/04/02 15:18:48| ipcache_dnsHandleRead: Result from DNS ID 2 (9 > :bytes) > :1998/04/02 15:18:48| ipcache_parsebuffer: parsing: > :$name www.karup.com > :$h_name www.karup.inter.net > :$h_len 4 > :$ipcount 2 > :38.15.68.128 > :38.15.67.128 > :$ttl 2348 > :$end > : > :Interestingly, it is very common to get only 100 bytes on the first > :read. When two read() calls are required, this adds > additional latency > :to the overall request. On our caches running Digital > Unix, the median > :dnsserver response time was measured at 0.01 seconds. On > our FreeBSD > :cache, however, the median latency was 0.10 seconds. > : > :Here is a simple patch to fix the bug: > : > :=================================================================== > :RCS file: /home/ncvs/src/sys/kern/uipc_socket.c,v > :retrieving revision 1.40 > :retrieving revision 1.41 > :diff -p -u -r1.40 -r1.41 > :--- src/sys/kern/uipc_socket.c 1998/05/15 20:11:30 1.40 > :+++ /home/ncvs/src/sys/kern/uipc_socket.c 1998/07/06 > 19:27:14 > :1.41 > :@@ -31,7 +31,7 @@ > : * SUCH DAMAGE. > : * > : * @(#)uipc_socket.c 8.3 (Berkeley) 4/15/94 > :- * $Id: FAQ.sgml,v 1.75 1999/07/06 16:07:36 wessels Exp $ > :+ * $Id: FAQ.sgml,v 1.75 1999/07/06 16:07:36 wessels Exp $ > : */ > : > : #include > :@@ -491,6 +491,7 @@ restart: > : mlen = MCLBYTES; > : len = min(min(mlen, resid), space); > : } else { > :+ atomic = 1; > : nopages: > : len = min(min(mlen, resid), space); > > > > 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 Jul 22 14:59:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 0B70015616 for ; Thu, 22 Jul 1999 14:59:00 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.2) id VAA32173 for hackers@freebsd.org; Thu, 22 Jul 1999 21:19:47 +0100 (BST) (envelope-from nik) Date: Thu, 22 Jul 1999 21:19:46 +0100 From: Nik Clayton To: hackers@freebsd.org Subject: InterMezzo: Project for kernel/FS hackers Message-ID: <19990722211946.A31641@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi chaps, Not entirely sure which list to post this too, so I figured that -hackers was probably most appropriate. Has anyone had the chance to look at InterMezzo, website at http://www.inter-mezzo.org/ It's main claim to fame is that it allows disconnected operation. For example, you could have a server export a home directory to a laptop, then unplug the laptop from the network, and go and edit/add/delete files from the home directory stored on the laptop. When the laptop is then plugged back in to the network, the filesystem automatically (as far as possible) integrates the changes). Coda (which already has a FreeBSD port) also does this, as well as a few other things. However, Coda is much more heavyweight than InterMezzo, and therefore easier to understand -- in particular, Coda seems to have (according to one of the Coda developers) a marked preference for exporting whole filesystems, InterMezzo allows you to export individual directory trees. Anyway, if any aspiring kernel hackers are looking for a project, that might be a fun one. The only implementation at the moment is for Linux. Cheers, N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 14:59:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (Postfix) with SMTP id 6B517155F6 for ; Thu, 22 Jul 1999 14:59:21 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 18061 invoked from network); 22 Jul 1999 21:59:14 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail.cdsnet.net with SMTP; 22 Jul 1999 21:59:14 -0000 Date: Thu, 22 Jul 1999 14:58:36 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Jason Young Cc: Matthew Dillon , Papezik Milon , hackers@FreeBSD.ORG Subject: RE: Squid - a bug in src/sys/kern/uipc_socket.c In-Reply-To: <000501bed48b$3de34600$8a9791d1@y> 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 Maybe it could be made a sysctl knob... On Thu, 22 Jul 1999, Jason Young wrote: > > It's been committed before, and broke many things (X and CVSup come to > mind). I have it compiled in locally on a few machines but it's > definitely not suitable for general distribution until a solution is > found that doesn't break applications. > > Jason Young > accessUS Chief Network Engineer > > > > -----Original Message----- > > From: owner-freebsd-hackers@FreeBSD.ORG > > [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of > > Matthew Dillon > > Sent: Thursday, July 22, 1999 3:57 PM > > To: Papezik Milon > > Cc: hackers@FreeBSD.ORG > > Subject: Re: Squid - a bug in src/sys/kern/uipc_socket.c > > > > > > This isn't really a bug since this is a TCP connection. > > TCP makes > > no guarentees that atomic writes will show up as atomic > > reads, and > > the squid code shouldn't be making that assumption. > > > > On the otherhand, the proposed fix appears to be an > > excellent performance > > optimization. It is basically only turning 'atomic' on > > for relatively > > small writes, which should be a win for a receiver > > whether over a > > localhost connection or a real network. I can't > > imagine that it would > > cause a performance loss in any other situation -- it > > might result in > > a slightly smaller-then-full-sized TCP packet > > occassionally in a stream > > but that's about it. > > > > I think committing this would be beneficial. Would > > someone w/ commit > > privs care to review and then commit this bit? > > > > -Matt > > Matthew Dillon > > > > > > :Hi, > > : > > :please don't kill me if it's "well known issue": > > : > > :I've found that there is a report on Squid site, which > > :describes a problem with FreeBSD IPC and includes suggested fix. > > :I verified that this suggested fix is not included in 3.2-RELEASE. > > : > > :I wonder, if it is really a bug, as I cannot find it in PR > > database. > > : > > :Could someone please comment on this report/bug/suggested fix > > :and if/when the fix could/will be submited? > > : > > :original URL: > > :http://squid.nlanr.net/Squid/FAQ/FAQ-14.html#ss14.2 > > : > > : Thanks in advance, > > : Milon > > :-- > > :papezik@pvt.net > > : > > : > > :------------ bug report and suggested fix --------- > > :mbuf size > > : > > :We noticed an odd thing with some of Squid's interprocess > > communication. > > :Often, output from the dnsserver processes would NOT be read in one > > :chunk. With full debugging, it looks like this: > > : > > :1998/04/02 15:18:48| comm_select: FD 46 ready for reading > > :1998/04/02 15:18:48| ipcache_dnsHandleRead: Result from > > DNS ID 2 (100 > > :bytes) > > :1998/04/02 15:18:48| ipcache_dnsHandleRead: Incomplete reply > > :....other processing occurs... > > :1998/04/02 15:18:48| comm_select: FD 46 ready for reading > > :1998/04/02 15:18:48| ipcache_dnsHandleRead: Result from DNS ID 2 (9 > > :bytes) > > :1998/04/02 15:18:48| ipcache_parsebuffer: parsing: > > :$name www.karup.com > > :$h_name www.karup.inter.net > > :$h_len 4 > > :$ipcount 2 > > :38.15.68.128 > > :38.15.67.128 > > :$ttl 2348 > > :$end > > : > > :Interestingly, it is very common to get only 100 bytes on the first > > :read. When two read() calls are required, this adds > > additional latency > > :to the overall request. On our caches running Digital > > Unix, the median > > :dnsserver response time was measured at 0.01 seconds. On > > our FreeBSD > > :cache, however, the median latency was 0.10 seconds. > > : > > :Here is a simple patch to fix the bug: > > : > > :=================================================================== > > :RCS file: /home/ncvs/src/sys/kern/uipc_socket.c,v > > :retrieving revision 1.40 > > :retrieving revision 1.41 > > :diff -p -u -r1.40 -r1.41 > > :--- src/sys/kern/uipc_socket.c 1998/05/15 20:11:30 1.40 > > :+++ /home/ncvs/src/sys/kern/uipc_socket.c 1998/07/06 > > 19:27:14 > > :1.41 > > :@@ -31,7 +31,7 @@ > > : * SUCH DAMAGE. > > : * > > : * @(#)uipc_socket.c 8.3 (Berkeley) 4/15/94 > > :- * $Id: FAQ.sgml,v 1.75 1999/07/06 16:07:36 wessels Exp $ > > :+ * $Id: FAQ.sgml,v 1.75 1999/07/06 16:07:36 wessels Exp $ > > : */ > > : > > : #include > > :@@ -491,6 +491,7 @@ restart: > > : mlen = MCLBYTES; > > : len = min(min(mlen, resid), space); > > : } else { > > :+ atomic = 1; > > : nopages: > > : len = min(min(mlen, resid), space); > > > > > > > > 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 Thu Jul 22 15: 1:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 9978C15600 for ; Thu, 22 Jul 1999 15:01:37 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA88061; Thu, 22 Jul 1999 15:00:34 -0700 (PDT) (envelope-from dillon) Date: Thu, 22 Jul 1999 15:00:34 -0700 (PDT) From: Matthew Dillon Message-Id: <199907222200.PAA88061@apollo.backplane.com> To: "Jason Young" Cc: "Papezik Milon" , Subject: Re: RE: Squid - a bug in src/sys/kern/uipc_socket.c References: <000501bed48b$3de34600$8a9791d1@y> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :It's been committed before, and broke many things (X and CVSup come to :mind). I have it compiled in locally on a few machines but it's :definitely not suitable for general distribution until a solution is :found that doesn't break applications. : :Jason Young :accessUS Chief Network Engineer Hmm.. it doesn't look like anyone tracked down why it was breaking applications after it was backed out the fist time - July last year looking at the CVS logs. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 15:10:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id D9FCF14F29 for ; Thu, 22 Jul 1999 15:10:25 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA88151; Thu, 22 Jul 1999 15:10:25 -0700 (PDT) (envelope-from dillon) Date: Thu, 22 Jul 1999 15:10:25 -0700 (PDT) From: Matthew Dillon Message-Id: <199907222210.PAA88151@apollo.backplane.com> To: "Jason Young" , "Papezik Milon" , Subject: Re: RE: Squid - a bug in src/sys/kern/uipc_socket.c References: <000501bed48b$3de34600$8a9791d1@y> <199907222200.PAA88061@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ::It's been committed before, and broke many things (X and CVSup come to ::mind). I have it compiled in locally on a few machines but it's ::definitely not suitable for general distribution until a solution is ::found that doesn't break applications. :: ::Jason Young ::accessUS Chief Network Engineer : : Hmm.. it doesn't look like anyone tracked down why it was breaking : applications after it was backed out the fist time - July last year : looking at the CVS logs. : : -Matt Looking at the code more closely, a failure can occur if the amount of data is larger then so->so_snd.sb_hiwat. This situation looks like it can occur if the socket buffer fills up (the sender is faster then the receiver). The solution would be to have a slightly more involved patch. Have a 'tryatomic' variable which is set based on this particular situation and then use it to mean 'atomic' in those cases where no error would occur. I am going to try to reproduce the failure with the original patch and will work up a new patch that fixes it if it winds up being what I think it will be. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 15:38:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id D71E21561F for ; Thu, 22 Jul 1999 15:38:35 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id SAA81150 for ; Thu, 22 Jul 1999 18:37:12 -0400 (EDT) Message-Id: <199907222237.SAA81150@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: mbuf leakage in NFSv3 writes, possbile? Date: Thu, 22 Jul 1999 18:37:12 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have 2 NFS servers. One is primarily read-only, the other read-write, they service the same clients (the read-only services more). They are (were) of the same build. I have a problem on the read/write server where it chews through mbuf clusters (it goes through about 3k in a day). Especially late at night the machine is not busy. And now it is also not busy, yet every minute or so it goes through a few mbuf clusters. The rate is about 108 minutes for 300 clusters. Does it sound reasonable that there is a mbuf leak in the NFS code somewhere? -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 15:45:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id B0C301563B for ; Thu, 22 Jul 1999 15:45:54 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA05097; Thu, 22 Jul 1999 15:44:07 -0700 (PDT) (envelope-from dillon) Date: Thu, 22 Jul 1999 15:44:07 -0700 (PDT) From: Matthew Dillon Message-Id: <199907222244.PAA05097@apollo.backplane.com> To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf leakage in NFSv3 writes, possbile? References: <199907222237.SAA81150@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I have 2 NFS servers. One is primarily read-only, the other read-write, they :service the same clients (the read-only services more). They are (were) of :the same build. I have a problem on the read/write server where it chews :through mbuf clusters (it goes through about 3k in a day). Especially late :at night the machine is not busy. And now it is also not busy, yet every :minute or so it goes through a few mbuf clusters. The rate is about 108 :minutes for 300 clusters. Does it sound reasonable that there is a mbuf leak :in the NFS code somewhere? : :-- :David Cross | email: crossd@cs.rpi.edu The server side caches mbuf chains to hold replies to NFS requests. This is done because it is quite common for requests to be repeated. The question is whether you are simply seeing the effect of this caching, or whether you have an actual mbuf leak. Does the mbuf usage / memory usage stabilize after a while or do you actually run out? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 15:46:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id BFFA6156B2 for ; Thu, 22 Jul 1999 15:46:52 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (crossd@void.cs.rpi.edu [128.213.8.27]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id SAA81283; Thu, 22 Jul 1999 18:46:11 -0400 (EDT) Message-Id: <199907222246.SAA81283@cs.rpi.edu> To: Matthew Dillon Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: mbuf leakage in NFSv3 writes, possbile? In-Reply-To: Message from Matthew Dillon of "Thu, 22 Jul 1999 15:44:07 PDT." <199907222244.PAA05097@apollo.backplane.com> Date: Thu, 22 Jul 1999 18:46:17 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I just -STABLED the server to see if it fixed it, but I was certainly running out. the server had only 3000-ish mbuf chains, and it would go through them all in a day. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 15:47:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id B1F1A15646 for ; Thu, 22 Jul 1999 15:47:18 -0700 (PDT) (envelope-from rminnich@acl.lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id QAA150144 for ; Thu, 22 Jul 1999 16:47:15 -0600 (MDT) Date: Thu, 22 Jul 1999 16:47:15 -0600 From: "Ronald G. Minnich" To: hackers@FreeBSD.ORG Subject: Re: InterMezzo: Project for kernel/FS hackers In-Reply-To: <19990722211946.A31641@catkin.nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm working with intermezzo now. It's interesting. Note that the VFS is quite simple, and defines a simple kernel-user channel which maps VFS ops to requests on an IPC channel. The possibilities are endless ... A freebsd port would be nice. Maybe you could use v9fs as a starting point. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 15:54:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 122A114BD2 for ; Thu, 22 Jul 1999 15:54:16 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id PAA57579; Thu, 22 Jul 1999 15:50:26 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Thu, 22 Jul 1999 15:50:26 -0700 (PDT) From: Vincent Poy To: Adrian Filipi-Martin Cc: hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Jul 1999, Adrian Filipi-Martin wrote: > On Wed, 21 Jul 1999, Vincent Poy wrote: > > > Greetings everyone, > > > > What are the current good motherboards for FreeBSD for the pentium > > II and III? I know on the Pentium, it was the ASUS board but for the > > PII/PIII, is the Abit the better board? Also, I was wondering what is the > > fastest Celeron chip that can be overclocked to run at 100Mhz FSB? Does > > it matter if it's Slot 1 or PPGA based? Thanks. > > I know a lot of people like the ASUS P2B boards, but I've noticed a > tendency for the systems to reset occasionally when plugging in a keyboard. > I've seen this with both FreeBSD and NT, so I'm considering it a property > of the board. I haven't seen anyone use a ASUS PII board but it seems like everyone is using ABIT boards for some reason for FreeBSD. I have a ASUS XP55T2P4 w/P233MMX on it and 128 megs of ram and while it works fine in FreeBSD... It seems to act weird in Windows95. I have some EIDE Mode 3 and mode 2 drives in the system and with the BIOS setting of PIO mode Auto, it works fine until I added the Maxtor Mode 4 HDD. This is when defining everything as auto would start up win95 half way and say things are corrupted so I had to manually set it to mode 3, 3, 2, 2 before things worked. And then the funny thing is that even with the 400Watt PC Power & Cooling Power Supply, in Win95, at certain times, when I click on something, it's like the machine did a hard reset.... Seems like the board works better with FreeBSD than Win95. > I've had great results with the Tyan 1836DLUAN/Thunder 100's. > I've got several boxes with 1GB of RAM and dual 450's humming along. For > comparison one system with less memory and a SuperMicro board but identical > system software has had a couple of wierd spontaneous reboots over the last > few months. Cool... Is 1GB of ram really needed? We used to run a 64 meg system then 128 meg and then 384 meg, it doesn't seem to do much even for a heavily loaded ISP Server. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 15:54:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 1714714DC6; Thu, 22 Jul 1999 15:54:37 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id PAA25787; Thu, 22 Jul 1999 15:52:20 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id PAA25289; Thu, 22 Jul 1999 15:51:30 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA28453; Thu, 22 Jul 99 15:52:17 PDT Message-Id: <3797A0A0.E8D8BE71@softweyr.com> Date: Thu, 22 Jul 1999 16:52:16 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Julian Elischer Cc: sthaug@nethelp.no, des@yes.no, hackers@FreeBSD.ORG, bde@FreeBSD.ORG Subject: Re: IDE breakage References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > > My fault > > I accidentally replaced a PAGE_MASK with a PAGE_SIZE. > the resulting bug only changes teh behaviour on unaligned pages > which are only possible on the raw device. > (e.g. fsck) > > the Cyrix 5530 we used to test has a bug where we cannot do unalligned > transfers by DMA anyhow, so we never hit this bug.. > > fixed in -current .... > will be fixxed in -stable when I reintroduce the patch... Bad Programmer! No doughnuts! ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@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 Jul 22 16:18:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id E481F14F5A for ; Thu, 22 Jul 1999 16:18:22 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA17973; Thu, 22 Jul 1999 16:18:19 -0700 (PDT) (envelope-from dillon) Date: Thu, 22 Jul 1999 16:18:19 -0700 (PDT) From: Matthew Dillon Message-Id: <199907222318.QAA17973@apollo.backplane.com> To: "Jason Young" , "Papezik Milon" , Subject: New patch fpr uipc_socket.c (was Squid - a bug in src/sys/kern/uipc_socket.c) References: <000501bed48b$3de34600$8a9791d1@y> <199907222200.PAA88061@apollo.backplane.com> <199907222210.PAA88151@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe this will solve the previously reported problems. With the original patch if I set net.inet.tcp.sendspace=63 and tried to run xterm from that machine to my local workstation, I got an X error. If I set sendspace=31 the xterm process just locked up and did nothing until I ^C'd it. machine A machine B w/modified kernel w/unmodified kernel (sysctl's on this machine) xterm run on A --> display is on B With this patch I can set net.inet.tcp.sendspace to anything (63, 31, 1, whatever I want) and the xterm will still run. And yes, the xterm is amazingly slow when I set net.inet.tcp.sendspace to 1 :-) This patch is relative to -CURRENT but should also work with -STABLE. -Matt Index: uipc_socket.c =================================================================== RCS file: /home/ncvs/src/sys/kern/uipc_socket.c,v retrieving revision 1.60 diff -u -r1.60 uipc_socket.c --- uipc_socket.c 1999/06/17 23:54:47 1.60 +++ uipc_socket.c 1999/07/22 23:08:38 @@ -413,7 +413,8 @@ register struct mbuf *m; register long space, len, resid; int clen = 0, error, s, dontroute, mlen; - int atomic = sosendallatonce(so) || top; + int atomic = sosendallatonce(so) || top; /* required atomicy */ + int try_atomic = atomic; /* requested atomicy */ if (uio) resid = uio->uio_resid; @@ -518,6 +519,7 @@ mlen = MCLBYTES; len = min(min(mlen, resid), space); } else { + try_atomic = 1; /* try to optimize */ nopages: len = min(min(mlen, resid), space); /* @@ -541,7 +543,7 @@ top->m_flags |= M_EOR; break; } - } while (space > 0 && atomic); + } while (space > 0 && try_atomic); if (dontroute) so->so_options |= SO_DONTROUTE; s = splnet(); /* XXX */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 17:55:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id B983E14E88 for ; Thu, 22 Jul 1999 17:55:24 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt011n65.san.rr.com (8.8.8/8.8.8) with ESMTP id RAA19171; Thu, 22 Jul 1999 17:55:19 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Thu, 22 Jul 1999 17:55:19 -0700 (PDT) From: Doug X-Sender: doug@dt011n65.san.rr.com To: Vincent Poy Cc: hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Jul 1999, Vincent Poy wrote: > Greetings everyone, > > What are the current good motherboards for FreeBSD for the pentium > II and III? I know on the Pentium, it was the ASUS board but for the > PII/PIII, is the Abit the better board? Also, I was wondering what is the > fastest Celeron chip that can be overclocked to run at 100Mhz FSB? Does > it matter if it's Slot 1 or PPGA based? Thanks. At work we're having good results with an Intel N440BX motherboard. It's a dual cpu board, running 2 PIII 500's like a champ. It also has the ability to redirect all console output (like boot/bios messages, etc.) to a serial console. It comes with a built in Etherexpress Pro 100+ as well. I have an Asus P2B at home that I've run my Celeron 300A overclocked to 450 since the first of the year with no problems (and BIG fans). HTH, Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 18:12:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rebel.net.au (rebel.rebel.net.au [203.20.69.66]) by hub.freebsd.org (Postfix) with ESMTP id 1C04214C57 for ; Thu, 22 Jul 1999 18:12:15 -0700 (PDT) (envelope-from kkenn@rebel.net.au) Received: from 203.20.69.79 (dialup-9.rebel.net.au [203.20.69.79]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id KAA00136 for ; Fri, 23 Jul 1999 10:41:25 +0930 Received: (qmail 41837 invoked from network); 23 Jul 1999 01:11:41 -0000 Received: from localhost (kkenn@127.0.0.1) by localhost with SMTP; 23 Jul 1999 01:11:41 -0000 Date: Fri, 23 Jul 1999 10:41:40 +0930 (CST) From: Kris Kennaway Reply-To: kkenn@rebel.net.au To: "Ronald G. Minnich" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Filesystem question... 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 Thu, 22 Jul 1999, Ronald G. Minnich wrote: > On Fri, 23 Jul 1999, Kris Kennaway wrote: > > Well, if you're running it as a kernel module then obviously you need root > > permissions to load it. If it's running as a userland process, then > > there's no reason why you can't run it as a user. mount presumably > > wouldn't care as long as you had access rights to the underlying objects > > (mountpoint + stacking layer process). > > well, you'll have to tell me more. (i have to get my freebsd source tree > back :-) ) > > Are you saying that as an ordinary user I can mount something on top of > /tmp, for example? If the vfs.usermount sysctl is 1, and you have appropriate access to the thing you're trying to mount (block device, etc). > Is the suser() check still in the mount system call? From vfs_syscalls.c: if (usermount == 0 && (error = suser(p))) return (error); usermount is tuned by the vfs.usermount sysctl and defaults to 0. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 18:18:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 582AB14C57 for ; Thu, 22 Jul 1999 18:18:43 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id SAA58506; Thu, 22 Jul 1999 18:14:47 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Thu, 22 Jul 1999 18:14:47 -0700 (PDT) From: Vincent Poy To: Doug Cc: hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Jul 1999, Doug wrote: > On Wed, 21 Jul 1999, Vincent Poy wrote: > > > Greetings everyone, > > > > What are the current good motherboards for FreeBSD for the pentium > > II and III? I know on the Pentium, it was the ASUS board but for the > > PII/PIII, is the Abit the better board? Also, I was wondering what is the > > fastest Celeron chip that can be overclocked to run at 100Mhz FSB? Does > > it matter if it's Slot 1 or PPGA based? Thanks. > > At work we're having good results with an Intel N440BX > motherboard. It's a dual cpu board, running 2 PIII 500's like a champ. It > also has the ability to redirect all console output (like boot/bios > messages, etc.) to a serial console. It comes with a built in Etherexpress > Pro 100+ as well. Cool... I thought the Intel motherboards weren't that good compared to other brands.. > I have an Asus P2B at home that I've run my Celeron 300A > overclocked to 450 since the first of the year with no problems (and BIG > fans). Hmmm, what kinda fans did you use and where can one get those? Is the 300A overclocked as fast as a regular PII 450Mhz? Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 18:19:34 1999 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 B53BD14C57 for ; Thu, 22 Jul 1999 18:19:30 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-117-224.bellatlantic.net [151.198.117.224]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id VAA18623; Thu, 22 Jul 1999 21:19:22 -0400 (EDT) Message-ID: <3797C3CD.A1F5D24B@bellatlantic.net> Date: Thu, 22 Jul 1999 21:22:21 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-980222-SNAP i386) MIME-Version: 1.0 To: "Daniel C. Sobral" , hackers@freebsd.org Subject: Re: Proposed substitution for ACLs References: <3787FB9D.3CDF0839@bellatlantic.net> <37882150.87A93451@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel C. Sobral wrote: > > Sergey Babkin wrote: > > > > I want to propose a simple substitution for ACLs. No, here > > is no patch yet but I'm ready and willing to do it. The reason > > why I want to discuss it first is that this is a Political Thing. > > And if the Core Team decides that it's a Bad Thing, I suppose > > it will never get commited to the system. Because of this I > > would like to see some encouraging signs from the Core Team > > before implementing it. > > Do whatever you want: as a fs layer. Speaking about the fs layers, can you please advise me on the current state of nullfs ? Is it working now ? I have checked GNATS about this and did not quite understood whether the results of a lengthly discussion in there on this subject were ever committed. On the other hand, I'm not sure whether implementing it as an FS layer is a good idea. It is certainly possible to do by snooping at the getattr/setattr calls but IMHO it will mean completely bypassing the VOP_ACCESS of the underlying filesystem what may be not good. On the other hand the changes to ufs_assess() seem to be quite small and cover all the UFS type filesystems, such as FFS and EXT2FS. Of course yet another option is to create one more fs type with all the operations in the filesystem switch the same as for FFS except for ufs_access(). What would be your recommendation ? Thanks! Here is the proposed patch (made against 3.2). If it will be considered OK I'll write some man page and LINT kernel entry too. I'm not sure whether the sysctl sub-node vfs.ufs is really neccessary but it seems to be logical. -------------------------- cut here ----------------------------- *** /sys/ufs/ufs/ufs_vnops.c 1999/07/15 14:50:53 1.1 --- /sys/ufs/ufs/ufs_vnops.c 1999/07/22 18:16:28 *************** *** 57,62 **** --- 57,63 ---- #include #include #include + #include #include #include *************** *** 104,109 **** --- 105,128 ---- static int ufsspec_read __P((struct vop_read_args *)); static int ufsspec_write __P((struct vop_write_args *)); + #ifdef ENABLE_UFS_COMMONID + /* + * Sysctl variables to control the unified user and + * group ID space. + * commonid is the lowest ID from which the common UID/GID space starts + * MINCOMMONID is the minimal value, if commonid is lower then the + * common ID space is disabled + */ + + #define MINCOMMONID 100 + + SYSCTL_NODE(_vfs, OID_AUTO, ufs, CTLFLAG_RW, 0, "Local Unix-type filesystems"); + static int commonid=0; + SYSCTL_INT(_vfs_ufs, OID_AUTO, commonid, CTLFLAG_RW, &commonid, 0, + "Lowest ID for the common GID/UID space"); + + #endif + union _qcvt { int64_t qcvt; int32_t val[2]; *************** *** 339,344 **** --- 360,382 ---- mask |= S_IWUSR; return ((ip->i_mode & mask) == mask ? 0 : EACCES); } + + #ifdef ENABLE_UFS_COMMONID + /* if the common UID/GID is enabled check the groups against the file UID */ + if (commonid >= MINCOMMONID && ip->i_uid >= commonid) { + for (i = 0, gp = cred->cr_groups; i < cred->cr_ngroups; + i++, gp++) + if (ip->i_uid == *gp) { + if (mode & VEXEC) + mask |= S_IXUSR; + if (mode & VREAD) + mask |= S_IRUSR; + if (mode & VWRITE) + mask |= S_IWUSR; + return ((ip->i_mode & mask) == mask ? 0 : EACCES); + } + } + #endif /* Otherwise, check the groups. */ for (i = 0, gp = cred->cr_groups; i < cred->cr_ngroups; i++, gp++) --------------------------- cut here ------------------------------------ -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 19:54:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from thneed.ubergeeks.com (thneed.ubergeeks.com [206.205.41.245]) by hub.freebsd.org (Postfix) with ESMTP id 28A7A1552A for ; Thu, 22 Jul 1999 19:54:53 -0700 (PDT) (envelope-from adrian@ubergeeks.com) Received: from localhost (adrian@localhost) by thneed.ubergeeks.com (8.9.3/8.9.3) with ESMTP id WAA03258; Thu, 22 Jul 1999 22:53:19 -0400 (EDT) (envelope-from adrian@ubergeeks.com) X-Authentication-Warning: thneed.ubergeeks.com: adrian owned process doing -bs Date: Thu, 22 Jul 1999 22:53:19 -0400 (EDT) From: Adrian Filipi-Martin Reply-To: Adrian Filipi-Martin To: Vincent Poy Cc: hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Jul 1999, Vincent Poy wrote: > On Thu, 22 Jul 1999, Adrian Filipi-Martin wrote: > > > I've had great results with the Tyan 1836DLUAN/Thunder 100's. > > I've got several boxes with 1GB of RAM and dual 450's humming along. For > > comparison one system with less memory and a SuperMicro board but identical > > system software has had a couple of wierd spontaneous reboots over the last > > few months. > > Cool... Is 1GB of ram really needed? We used to run a 64 meg > system then 128 meg and then 384 meg, it doesn't seem to do much even for > a heavily loaded ISP Server. Not really. The customer whose box this is chose this much memory because his previous server was a 256MB UltraSparc that was swamped all the time with a load of 6 to 7. The real problem was poor CGI programming. I made them fix them. Now it toodles along with ridiculously low loads. All the websites and the mysql db fit in core. ;-) Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 20:13:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wenet.net (pm3-43.ppp.wenet.net [206.15.85.43]) by hub.freebsd.org (Postfix) with ESMTP id 3FB9F1501B for ; Thu, 22 Jul 1999 20:13:21 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by wenet.net (8.9.3/8.9.1) with ESMTP id UAA00656; Thu, 22 Jul 1999 20:13:09 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Thu, 22 Jul 1999 20:13:09 -0700 (PDT) From: Alex Zepeda To: Adrian Filipi-Martin Cc: Vincent Poy , hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Jul 1999, Adrian Filipi-Martin wrote: > I know a lot of people like the ASUS P2B boards, but I've noticed a > tendency for the systems to reset occasionally when plugging in a keyboard. > I've seen this with both FreeBSD and NT, so I'm considering it a property > of the board. If this is a PS/2 style keyboard, don't plug and unplug them when the host is powered up. The PS/2 style stuf seems to be very sensitive to that sort of thing. If it was a USB keyboard doing that... then that would be odd. - alex You wear guilt, like shackles on your feet, Like a halo in reverse - Depeche Mode To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 23: 0: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 0879914DAA for ; Thu, 22 Jul 1999 23:00:04 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id WAA12518; Thu, 22 Jul 1999 22:58:59 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id WAA75688; Thu, 22 Jul 1999 22:58:59 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 22 Jul 1999 22:58:59 -0700 (PDT) Message-Id: <199907230558.WAA75688@vashon.polstra.com> To: Dom.Mitchell@palmerharvey.co.uk Subject: Re: PAM & LDAP in FreeBSD, and userfs too. In-Reply-To: <19990722111605.C49393@palmerharvey.co.uk> References: <19990719204417.A5796@palmerharvey.co.uk> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990722111605.C49393@palmerharvey.co.uk>, Dominic Mitchell wrote: > On Thu, Jul 22, 1999 at 04:59:59PM +0700, Max Khon wrote: > > > > PAM is also "using masses of weird shared objects" but nevertheless it's > > quite usable > > By statically linked binaries? Our PAM implementation works for static binaries too. See the sources for the gory details. Basically it creates a library that includes all the possible modules, and selects the right one at runtime. There's some linker set magic involved. Concerning "masses of weird shared objects," you'd really better get used to it. It was the wave of the future 10 years ago. It's not going away. Dynamic linking provides flexibility and modularity that you just can't get from static linking. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 23: 5:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from argus.tfs.net (host1-216.birch.net [216.212.1.216]) by hub.freebsd.org (Postfix) with ESMTP id 8D91D14DAA for ; Thu, 22 Jul 1999 23:05:18 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id BAA30812 for freebsd-hackers@freebsd.org; Fri, 23 Jul 1999 01:02:03 -0500 (CDT) From: Jim Bryant Message-Id: <199907230602.BAA30812@argus.tfs.net> Subject: usb keyboard setup -or- HELP! To: freebsd-hackers@freebsd.org Date: Fri, 23 Jul 1999 01:02:03 -0500 (CDT) Reply-To: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, i'm running 4.0-current on a dual p2-333 box. i run X, and am looking for help in setting up a usb keyboard for use with FreeBSD/Xfree86. if anyone has this running, i could use the help in setting it up. also, this keyboard has a ps2 mouse connector. does the mouse get recognized as a usb mouse? jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 22 23:42:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id 695C814F8F for ; Thu, 22 Jul 1999 23:42:50 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.8.8/8.8.8) with ESMTP id XAA21217; Thu, 22 Jul 1999 23:42:04 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37980EBC.C38668E1@gorean.org> Date: Thu, 22 Jul 1999 23:42:04 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: "David E. Cross" Cc: Matthew Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf leakage in NFSv3 writes, possbile? References: <199907222246.SAA81283@cs.rpi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David E. Cross" wrote: > > Well, I just -STABLED the server to see if it fixed it, but I was certainly > running out. the server had only 3000-ish mbuf chains, and it would go through > them all in a day. Well, have you tried increasing the number of available mbufs and see if you reach a point of stability? Assuming you have enough physical ram you could do 15k mbufs on -Stable without a problem. Check LINT for the nmbclusters option if you need help with it. Good luck, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 0: 4:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rebel.net.au (rebel.rebel.net.au [203.20.69.66]) by hub.freebsd.org (Postfix) with ESMTP id A3357156A4 for ; Fri, 23 Jul 1999 00:04:04 -0700 (PDT) (envelope-from kkenn@rebel.net.au) Received: from 203.20.69.80 (dialup-10.rebel.net.au [203.20.69.80]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id QAA07048 for ; Fri, 23 Jul 1999 16:30:12 +0930 Received: (qmail 50831 invoked from network); 23 Jul 1999 07:00:23 -0000 Received: from localhost (kkenn@127.0.0.1) by localhost with SMTP; 23 Jul 1999 07:00:23 -0000 Date: Fri, 23 Jul 1999 16:30:23 +0930 (CST) From: Kris Kennaway Reply-To: kkenn@rebel.net.au To: John Polstra Cc: Dom.Mitchell@palmerharvey.co.uk, hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD, and userfs too. In-Reply-To: <199907230558.WAA75688@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Jul 1999, John Polstra wrote: > > On Thu, Jul 22, 1999 at 04:59:59PM +0700, Max Khon wrote: > > > > > > PAM is also "using masses of weird shared objects" but nevertheless it's > > > quite usable > > > > By statically linked binaries? > > Our PAM implementation works for static binaries too. See the > sources for the gory details. Basically it creates a library that > includes all the possible modules, and selects the right one at > runtime. There's some linker set magic involved. This means you can't add in a new module without recompiling the static library, correct? That seems to defeat the purpose of PAM being modular for the static case :-( Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 0:14:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from musashi.et.bocholt.fh-ge.de (reserve.et.bocholt.fh-gelsenkirchen.de [193.175.197.95]) by hub.freebsd.org (Postfix) with ESMTP id CE92914CB7 for ; Fri, 23 Jul 1999 00:14:27 -0700 (PDT) (envelope-from hank@musashi.et.bocholt.fh-ge.de) Received: from localhost (localhost [127.0.0.1]) by musashi.et.bocholt.fh-ge.de (8.9.3/8.9.3) with ESMTP id JAA04436; Fri, 23 Jul 1999 09:10:24 +0200 (CEST) (envelope-from hank@musashi.et.bocholt.fh-ge.de) Message-Id: <199907230710.JAA04436@musashi.et.bocholt.fh-ge.de> To: John Reynolds~ Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SURVEY: Sound cards that work under FreeBSD In-reply-to: Your message of "Thu, 22 Jul 1999 13:52:33 PDT." <14231.33937.454645.22076@hip186.ch.intel.com> Date: Fri, 23 Jul 1999 09:10:24 +0200 From: Dirk GOUDERS Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's the information about the sound card I am working with: > 1) The sound card make and model/chipset. Please be as specific as you can with > board rev numbers if possible. Please include wether the card is ISA or PCI. My sound card is a SBPCI128 by Creative Labs. > 2) FreeBSD version(s) it was tested with. List *all* versions of FreeBSD for > which you can verify that the sound card does/doesn't work (don't include > -BETA or -SNAP releases but dates on -STABLE and -CURRENT branches are > welcome). I only used the card with FreeBSD 3.2 > 3) Appropriate lines from your kernel config file / PNP setup. i.e. what did > you have to do to get this card working? Did you need patches not committed > to a particular branch (if so URLs would be welcome)? Do you use OSS drivers > instead? The only line I had to add to my kernel config file was: device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0 (This causes a message "pcm0 not found" to appear at boot time but just ignoring it seems to be o.k. - allthough I would prefer not to see it, at all.) > 4) Sample dmesg output for properly configured device. Show the world what > boot messages relate to the device after properly configured. These are the messages that appear previous to the message "pcm0 not found": es1: rev 0x01 int a irq 5 on pci0.9.0 pcm1: using I/O space register mapping at 0xe400 > 5) Miscellaneous notes. State anything "not obvious" to the casual FreeBSD > user. Good examples might be, "volume is 0 by default, use mixer(1) to > adjust at boot time," or "sh MAKEDEV snd1 for the 1st device, not snd0." I had to build the audio device snd1: # cd /dev # sh MKDEV snd1 and to use the mixer to set the volume to another value than 0. I use the following script /usr/local/etc/rc.d/mixer.sh at boot time: #!/bin/sh /usr/sbin/mixer vol 60:60 pcm 60:60 cd 60:60 > 6) Is it OK to publish your e-mail address / name as the contributor of this > information? You may type in an anti-spam version of your e-mail address > below if you would like that option instead. Well, I guess, I should not be listed as the contributor, because I catched these information out of the mailing lists and would prefer the original poster to appear as the contributor. Cheers, Dirk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 0:35: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 8509D14CCB for ; Fri, 23 Jul 1999 00:35:03 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id JAA14423; Fri, 23 Jul 1999 09:34:28 +0200 (MET DST) Date: Fri, 23 Jul 1999 09:34:27 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: "Matthew D. Fuller" Cc: Matthew Dillon , Len Conrad , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD: the stealth OS? In-Reply-To: <19990722144808.J12369@futuresouth.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 > > "There's a lot of things that Linux is 'better' at, and a > > lot of things FreeBSD is 'better' at, and a lot of those > > things can easily fluctuate on a daily or weekly basis," > > said Fuller, who maintains a Linux vs BSD Web page. > > "Thus, any definitive narrow statement that can be made > > is usually obsolete before anyone hears it.". > > > > Perfect! > > Thank you, my fans! Please leave your monetary contributions in the hat > on your way out ;> Where is the hat? I saw Julian running off with it a couple of e-mails ago. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 1: 2:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 0421A14D21 for ; Fri, 23 Jul 1999 01:02:33 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id BAA60459; Fri, 23 Jul 1999 01:00:38 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Fri, 23 Jul 1999 01:00:38 -0700 (PDT) From: Vincent Poy To: Adrian Filipi-Martin Cc: hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Jul 1999, Adrian Filipi-Martin wrote: > > On Thu, 22 Jul 1999, Adrian Filipi-Martin wrote: > > > > > I've had great results with the Tyan 1836DLUAN/Thunder 100's. > > > I've got several boxes with 1GB of RAM and dual 450's humming along. For > > > comparison one system with less memory and a SuperMicro board but identical > > > system software has had a couple of wierd spontaneous reboots over the last > > > few months. > > > > Cool... Is 1GB of ram really needed? We used to run a 64 meg > > system then 128 meg and then 384 meg, it doesn't seem to do much even for > > a heavily loaded ISP Server. > > Not really. The customer whose box this is chose this much memory > because his previous server was a 256MB UltraSparc that was swamped all the > time with a load of 6 to 7. > > The real problem was poor CGI programming. I made them fix them. > Now it toodles along with ridiculously low loads. All the websites and the > mysql db fit in core. ;-) That's true too.... Seems like FreeBSD can handle a real high load without problems... Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 1:22:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id F00B914BE1 for ; Fri, 23 Jul 1999 01:22:48 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id JAA15148; Fri, 23 Jul 1999 09:53:31 +0200 (MET DST) Date: Fri, 23 Jul 1999 09:53:30 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: jbryant@tfs.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: usb keyboard setup -or- HELP! In-Reply-To: <199907230602.BAA30812@argus.tfs.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 Check out the ukbd man page man 4 ukbd It should give you all the information you need. The PS/2 connector should be recognised by the ums driver and it should give you a mouse that you can attach as described in the ums man page. Let me know if this does not work for you, so we can improve the man pages. Thanks. Nick On Fri, 23 Jul 1999, Jim Bryant wrote: > hi, i'm running 4.0-current on a dual p2-333 box. i run X, and am > looking for help in setting up a usb keyboard for use with > FreeBSD/Xfree86. > > if anyone has this running, i could use the help in setting it up. > > also, this keyboard has a ps2 mouse connector. does the mouse get > recognized as a usb mouse? > > jim > -- > All opinions expressed are mine, if you | "I will not be pushed, stamped, > think otherwise, then go jump into turbid | briefed, debriefed, indexed, or > radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" > ------------------------------------------------------------------------------ > Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw > voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant > ------------------------------------------------------------------------------ > HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 1:51:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 5A98D14E9D for ; Fri, 23 Jul 1999 01:51:26 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.79]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAD4A16; Fri, 23 Jul 1999 10:51:25 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id KAA09317; Fri, 23 Jul 1999 10:39:43 +0200 (CEST) (envelope-from asmodai) Date: Fri, 23 Jul 1999 10:39:42 +0200 From: Jeroen Ruigrok/Asmodai To: itojun@iijlab.net Cc: hackers@FreeBSD.ORG Subject: Re: Will FreeBSD ever see native IPv6 ?? Message-ID: <19990723103942.C9276@daemon.ninth-circle.org> References: <19990722142445.B814@daemon.ninth-circle.org> <22056.932649289@coconut.itojun.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <22056.932649289@coconut.itojun.org>; from itojun@iijlab.net on Thu, Jul 22, 1999 at 10:14:49PM +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * itojun@iijlab.net (itojun@iijlab.net) [990722 16:17]: > > >> Are you just teasing or are you serious? > >Well, according to what was discussed earlier he is serious. But from > >prolonged exposure to the kame lists I (think I) know that the FreeBSD ipv6 > >stuff is only available for 3.x and below. > > We (KAME) are using 3.2-RELEASE and 2.2.8-RELEASE because we can't > base our IPv6 development on top of moving target. > FreeBSD 3.x-STABLE and 4.x are moving target (which moves very quickly) > and are unusable as base version for us - if we need to chase two > moving things (IPv6 and FreeBSD) we are doomed. Problem being is that the 2.2.x branch has been declared obsolete and dead by the Project. If serious development work is being done CURRENT has always been the targetted platform. But let's not nitpick about decissions make months earlier. However, 3.2-STABLE isn't that fast moving forward, and I doubt, based on earlier discussions about touching the 3.x branch, that Jordan will allow IPv6 to be entered into the 3.x branch (however TPTB may judge otherwise). So 4.x seems like the only alternative left... And I am still working on that =) > There has been NRL/INRIA/KAME integration work going on (basically > to avoid "4 BSDs and 3 IPv6 = 12 choices" nightmare by making one > IPv6 stack). There are, mainly, some (or too many) management > issues there. We will be resolving management issues issue very soon, > hopefully by next week. That's good new ITOJUN-san, but I hope you can understand that after seeing OpenBSD deploy IPv6 and NetBSD-CURRENT getting the IPv6 code merged by you, that FreeBSD (read the userbase/developers) is anxious to also incorporate this. > There's incomplete "unified" codebase there, which is not very > ready for public consumption. Anyway please hold till the managment > issue is resolved, I believe I can give you a good news. Let me ask one question: if a few of us got the 3.x kit of kame up to 4.x level and it got all commited would it make the `merged' stack easier to integrate into CURRENT or does the stack-project prefer to use a clean codebase? I myself think the first, which allows our driver writers time to adjust to IPv6 changes, get a lot of still-present bugs out and basically restabilize the system before the next IPv6 changes. Not to mention allow people to test/work with IPv6 already. I would love to hear your reactions to the above, kind regards, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 2:16:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id 8EFD9156F9 for ; Fri, 23 Jul 1999 02:16:22 -0700 (PDT) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Fri, 23 Jul 1999 10:04:21 +0100 Received: from voodoo.pandhm.co.uk (VOODOO [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id PJ2VD4LJ; Fri, 23 Jul 1999 10:04:22 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 117bFR-000Pld-00; Fri, 23 Jul 1999 10:04:09 +0100 Date: Fri, 23 Jul 1999 10:04:09 +0100 To: John Polstra Cc: Dom.Mitchell@palmerharvey.co.uk, hackers@freebsd.org Subject: Re: PAM & LDAP in FreeBSD, and userfs too. Message-Id: <19990723100408.D98688@palmerharvey.co.uk> References: <19990719204417.A5796@palmerharvey.co.uk> <19990722111605.C49393@palmerharvey.co.uk> <199907230558.WAA75688@vashon.polstra.com> MIME-Version: 1.0 X-Mailer: Mutt 0.95.6i In-Reply-To: <199907230558.WAA75688@vashon.polstra.com>; from John Polstra on Thu, Jul 22, 1999 at 10:58:59PM -0700 From: Dominic Mitchell Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 22, 1999 at 10:58:59PM -0700, John Polstra wrote: > In article <19990722111605.C49393@palmerharvey.co.uk>, > Dominic Mitchell wrote: > > On Thu, Jul 22, 1999 at 04:59:59PM +0700, Max Khon wrote: > > > > > > PAM is also "using masses of weird shared objects" but nevertheless it's > > > quite usable > > > > By statically linked binaries? > > Our PAM implementation works for static binaries too. See the > sources for the gory details. Basically it creates a library that > includes all the possible modules, and selects the right one at > runtime. There's some linker set magic involved. Ooh! Cunning! > Concerning "masses of weird shared objects," you'd really better get > used to it. It was the wave of the future 10 years ago. It's not > going away. Dynamic linking provides flexibility and modularity that > you just can't get from static linking. Very right. I didn't say it was a bad thing, just confused me for a while when I first saw it... However, I still (personally) prefer the idea of a filesystem interface... -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator In Mountain View did Larry Wall Sedately launch a quiet plea: That DOS, the ancient system, shall On boxes pleasureless to all Run Perl though lack they C. -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 3: 1:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 2AB7414F88 for ; Fri, 23 Jul 1999 03:01:46 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id TAA09130; Fri, 23 Jul 1999 19:01:41 +0900 (JST) To: Jeroen Ruigrok/Asmodai Cc: hackers@FreeBSD.ORG In-reply-to: asmodai's message of Fri, 23 Jul 1999 10:39:42 +0200. <19990723103942.C9276@daemon.ninth-circle.org> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: Will FreeBSD ever see native IPv6 ?? From: itojun@iijlab.net Date: Fri, 23 Jul 1999 19:01:41 +0900 Message-ID: <9128.932724101@coconut.itojun.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> We (KAME) are using 3.2-RELEASE and 2.2.8-RELEASE because we can't >> base our IPv6 development on top of moving target. >> FreeBSD 3.x-STABLE and 4.x are moving target (which moves very quickly) >> and are unusable as base version for us - if we need to chase two >> moving things (IPv6 and FreeBSD) we are doomed. >Problem being is that the 2.2.x branch has been declared obsolete and dead >by the Project. >If serious development work is being done CURRENT has always been the >targetted platform. But let's not nitpick about decissions make months >earlier. >However, 3.2-STABLE isn't that fast moving forward, and I doubt, based on >earlier discussions about touching the 3.x branch, that Jordan will allow >IPv6 to be entered into the 3.x branch (however TPTB may judge otherwise). >So 4.x seems like the only alternative left... I can't tell KAME users like: "Oh, if you would like to apply KAME diffs you'll need to fetch FreeBSD 4.x of June 1st". KAME needs to stick to x.y-RELEASE either, KAME have no choice anyways. >And I am still working on that =) Thanks for the effort! >> There has been NRL/INRIA/KAME integration work going on (basically >> to avoid "4 BSDs and 3 IPv6 = 12 choices" nightmare by making one >> IPv6 stack). There are, mainly, some (or too many) management >> issues there. We will be resolving management issues issue very soon, >> hopefully by next week. >That's good new ITOJUN-san, but I hope you can understand that after seeing >OpenBSD deploy IPv6 and NetBSD-CURRENT getting the IPv6 code merged by you, >that FreeBSD (read the userbase/developers) is anxious to also incorporate >this. I talked with core@freebsd.org several times about IPv6/IPsec integration, and the reaction was that: FreeBSD can wait till unified-ipv6 is made available, since: - IPv6 is not that urgent task and - it will be messy if FreeBSD integrates KAME first, then switch to unified-ipv6. (making a big change twice for IPv6 is questionable route) So we are in the current situation. (or maybe I was not pushing hard enough) NetBSD merged in KAME code last month, because NetBSD will have feature freeze for 1.5 soon and needed IPv6 code earlier than that. If I miss 1.5, it will not be able to be merged until 1.6 (planned to be sometime late 2000, I heard). NetBSD will be switching to unified codebase whenever it is made available (so NetBSD decided to make a big change twice). >> There's incomplete "unified" codebase there, which is not very >> ready for public consumption. Anyway please hold till the managment >> issue is resolved, I believe I can give you a good news. >Let me ask one question: if a few of us got the 3.x kit of kame up to 4.x >level and it got all commited would it make the `merged' stack easier to >integrate into CURRENT or does the stack-project prefer to use a clean >codebase? I myself think the first, which allows our driver writers time >to adjust to IPv6 changes, get a lot of still-present bugs out and basically >restabilize the system before the next IPv6 changes. Not to mention allow >people to test/work with IPv6 already. Here's my question: how much patch rejection you saw when you tried to apply KAME/FreeBSD32 patch onto 4.0? Were there many of these, or very few? If they are very few, and core@freebsd is okay, I think KAME can be merged into 4.0 tree first, then FreeBSD can switch from KAME to unified whenever it becomes ready (just like NetBSD does). Hopefully KAME and unified-ipv6 will not be that different, except for dual-stack tcp part (KAME code used separate tcp4/tcp6 for a long time, due to maintenance and stability reasons. The way unified code does dual-stack tcp is different from what KAME does). Userland part can be reused without trouble. There are, however, several drawbacks in doing that: - Now we have multiple KAME/FreeBSD[34] repository, one is in KAME site and one is in freefall.freebsd.org. Synchronizing those tree is a big problem. KAME already have problems synchronizing code between platforms we support, the merge will increase the problem. - Manpower issues. We need to continue providing KAME/FreeBSD32 anyways, for people who wants more stable IPv6/IPsec systems. We can't just tell everybody to switch to 4.0 and chase FreeBSD-current. - We need some more FreeBSD commit privs for other KAME guys. (this is a easy part) - again, two big changes for IPv6? Impacts on IPv4 stability? itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 3:47:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id EFE0514ED4 for ; Fri, 23 Jul 1999 03:47:20 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id GAA03535; Fri, 23 Jul 1999 06:45:36 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Fri, 23 Jul 1999 06:45:35 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Nik Clayton Cc: hackers@freebsd.org Subject: Re: InterMezzo: Project for kernel/FS hackers In-Reply-To: <19990722211946.A31641@catkin.nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Jul 1999, Nik Clayton wrote: > Hi chaps, > > Not entirely sure which list to post this too, so I figured that -hackers > was probably most appropriate. > > Has anyone had the chance to look at InterMezzo, website at > > http://www.inter-mezzo.org/ > > It's main claim to fame is that it allows disconnected operation. For > example, you could have a server export a home directory to a laptop, > then unplug the laptop from the network, and go and edit/add/delete files > from the home directory stored on the laptop. When the laptop is then > plugged back in to the network, the filesystem automatically (as far > as possible) integrates the changes). > > Coda (which already has a FreeBSD port) also does this, as well as a few > other things. However, Coda is much more heavyweight than InterMezzo, > and therefore easier to understand -- in particular, Coda seems to have > (according to one of the Coda developers) a marked preference for > exporting whole filesystems, InterMezzo allows you to export individual > directory trees. > > Anyway, if any aspiring kernel hackers are looking for a project, that > might be a fun one. The only implementation at the moment is for Linux. > > Cheers, What I'd actually like to see is a port of Inter-mezzo to use the Arla kernel module, which is far more portable/etc, and is also under a BSD license (both Coda and Inter-mezzo are under GPL). I have worked a fair amount with the Arla module to build some user-land file system code, but have no experience with Inter-mezzo. I do have experience with the Coda module, and can say they are quite similar (although the Arla code seems more thread-aware and RPC-like). I have hopes that we can integrate the Arla module into the base FreeBSD distribution, as OpenBSD has done, as it is looking quite stable and makes userfs programming a lot easier. OpenBSD has also integrated the Arla userland support for AFS, which might also be nice to integrate into the base distribution at some point, but is perhaps less useful than integrating the kernel module as the userland code can easily be made a package. As to your comments on Coda: Coda requires custom storage on the server, and cannot export a regular file system. I'm not sure how Inter-Mezzo handles these things: they might require the storage of log/version information on the server somewhere to aid in reintegrating disconnected changes, but again I don't know all that much about it. What I do know is that Coda desperately requires simplification and a fresh code base, so it seems like a step forwards. :-) Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Computing Laboratory at Cambridge University Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 3:48:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 4EEF014ED4 for ; Fri, 23 Jul 1999 03:48:11 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id MAA25914; Fri, 23 Jul 1999 12:17:45 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id LAA01383; Fri, 23 Jul 1999 11:50:01 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199907230950.LAA01383@yedi.iaf.nl> Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's In-Reply-To: from Alex Zepeda at "Jul 22, 1999 8:13: 9 pm" To: garbanzo@hooked.net (Alex Zepeda) Date: Fri, 23 Jul 1999 11:50:01 +0200 (CEST) Cc: adrian@ubergeeks.com, vince@venus.GAIANET.NET, hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Alex Zepeda wrote ... > On Thu, 22 Jul 1999, Adrian Filipi-Martin wrote: > > > I know a lot of people like the ASUS P2B boards, but I've noticed a > > tendency for the systems to reset occasionally when plugging in a keyboard. > > I've seen this with both FreeBSD and NT, so I'm considering it a property > > of the board. > > If this is a PS/2 style keyboard, don't plug and unplug them when the host > is powered up. The PS/2 style stuf seems to be very sensitive to that PS/2 or DIN plug, does not matter. [Un]plugging keyboards is a bad idea on a live system. I've seen keyboard fuses (on the mainboard) blown etc And that would be the most benificial of the possible breakage you can get yourself into. Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 3:54:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 9F95914ED4 for ; Fri, 23 Jul 1999 03:54:39 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id GAA03560; Fri, 23 Jul 1999 06:54:26 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Fri, 23 Jul 1999 06:54:26 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: hackers@freebsd.org Cc: pham@andrew.cmu.edu Subject: Paper: Kernel-Supported Speculative Process Execution for Transparent File System Prefetching 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 ---------- Title Kernel-Supported Speculative Process Execution for Transparent File System Prefetching CMU 15-712 Software Systems Authors Ted Pham and Robert Watson Date May 7, 1999 Abstract This paper explores the feasibility of an operating system kernel performing speculative execution of user processes during system idle time to generate file system prefetches. We discuss the implementation, and how the use of existing FreeBSD kernel primitives may be leveraged to provide this through minimal modifications to the underlying operating system. We evaluate the effectiveness of the technique, and improvements that would allow us to realize the potential performance increase. URL http://www.watson.org/~robert/15-712/project/ ---------- We're still continuing work on this, and have not had a chance to do a full evaluation or wring all of the bugs out. However, I thought people might be interested in taking a look. Our source code will be available in a month or so once we've had a chance to fix a few more things up. This work is based on a paper by F Chang, "Automatic I/O Hint Generation through Speculative Execution", which appeared in Proceedings of the 3rd Symposium on Operating Systems Design and Implementation, February 1999. The basic idea was to generate file system prefetches based on a speculative thread that executed the code ahead of time, and tried to guess what reads would occur. They did this by performing a binary modification to the base program to create and maintain the thread. We wondered if it would not be more efficient and general to implement this in the OS kernel, and did so based on 4.0-CURRENT of FreeBSD (around May). What they had and what we did not have was RAID disk arrays to run their code against: they had far disk bandwidth than we did, although presumably around the same latency. The paper is not great, as it was largely written extremely early in the morning, but I think it gets across the design goals and intent. Once we've revamped the code a little and gotten it to work a bit better, presumably a published paper will turn up somewhere. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Computing Laboratory at Cambridge University Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 5:29:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 24D4014E73; Fri, 23 Jul 1999 05:29:00 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 117eRz-000Ap3-00; Fri, 23 Jul 1999 14:29:19 +0200 From: Sheldon Hearn To: Andre Albsmeier Cc: Brian Feldman , hackers@freebsd.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.h In-reply-to: Your message of "Fri, 23 Jul 1999 11:28:12 +0200." <19990723112812.A3847@internal> Date: Fri, 23 Jul 1999 14:29:19 +0200 Message-ID: <41604.932732959@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Hijacked from cvs-committers and cvs-all] On Fri, 23 Jul 1999 11:28:12 +0200, Andre Albsmeier wrote: > I observed some kind of denial of service on -STABLE: I was > playing with the new nmap and did a 'nmap -sU printfix'. > inetd was running as "inetd -l" and started sucking all the > CPU time even the nmap had been terminated long ago. What does "sucking all the CPU time" mean? Does it mean that other programs were suffering, or does it mean that it was the only significant user of CPU and so showed up at close to 100% CPU usage? I suspect that the latter is true. > /var/log/messages file showed zillions of the following lines > being added continously: Well, you did ask for them (inetd -l). :-) > Jul 23 11:21:28 printfix inetd[1743]: time from [...] > Jul 23 11:21:28 printfix inetd[1743]: daytime from [...] Usually syslog will give you "last message repeated X times". Unfortunately, the alternation of the messages makes this impossible. David Malone had a few ideas on "clever" handling of UDP. While what he suggests might help reduce the number of messages you receive under legitimate use, it won't help against DoS, since the sender of packets can simply randomize the origin addresses. > Maybe you got an idea... I know exactly why you see what you see when you do what you do. All I can say is "don't do that", because I can't think of a why to cater for what you're doing in a sensible fashion. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 5:53: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 2C3001503B; Fri, 23 Jul 1999 05:52:58 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from bell.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 23 Jul 1999 13:50:46 +0100 (BST) Date: Fri, 23 Jul 1999 13:50:45 +0100 From: David Malone To: Sheldon Hearn Cc: Andre Albsmeier , Brian Feldman , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c inetd. Message-ID: <19990723135045.A71302@bell.maths.tcd.ie> References: <19990723112812.A3847@internal> <41604.932732959@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <41604.932732959@axl.noc.iafrica.com>; from Sheldon Hearn on Fri, Jul 23, 1999 at 02:29:19PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 23, 1999 at 02:29:19PM +0200, Sheldon Hearn wrote: > Well, you did ask for them (inetd -l). :-) > > > Jul 23 11:21:28 printfix inetd[1743]: time from [...] > > Jul 23 11:21:28 printfix inetd[1743]: daytime from [...] > > Usually syslog will give you "last message repeated X times". > Unfortunately, the alternation of the messages makes this impossible. You could turn on wrapping and log them at a level at which syslog will ignore them. I'm not sure how much this would help with inetd chewing CPU time, but... David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 5:53:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 82DF11503B; Fri, 23 Jul 1999 05:53:10 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 117eoU-000Atl-00; Fri, 23 Jul 1999 14:52:34 +0200 From: Sheldon Hearn To: David Malone Cc: Andre Albsmeier , Brian Feldman , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c inetd. In-reply-to: Your message of "Fri, 23 Jul 1999 13:50:45 +0100." <19990723135045.A71302@bell.maths.tcd.ie> Date: Fri, 23 Jul 1999 14:52:34 +0200 Message-ID: <41896.932734354@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Jul 1999 13:50:45 +0100, David Malone wrote: > You could turn on wrapping and log them at a level at which > syslog will ignore them. I'm not sure how much this would help > with inetd chewing CPU time, but... If, indeed, inetd is really "chewing CPU time". Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 6: 6: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 11E0F15709 for ; Fri, 23 Jul 1999 06:06:05 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id PAA01947 for ; Fri, 23 Jul 1999 15:06:04 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id PAA02713 for ; Fri, 23 Jul 1999 15:06:03 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.9.3/8.9.3) id PAA50738 for ; Fri, 23 Jul 1999 15:06:04 +0200 (CEST) Date: Fri, 23 Jul 1999 15:06:02 +0200 From: Andre Albsmeier To: Sheldon Hearn Cc: Andre Albsmeier , Brian Feldman , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.h Message-ID: <19990723150602.B10047@internal> References: <19990723112812.A3847@internal> <41604.932732959@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <41604.932732959@axl.noc.iafrica.com>; from Sheldon Hearn on Fri, Jul 23, 1999 at 02:29:19PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23-Jul-1999 at 14:29:19 +0200, Sheldon Hearn wrote: > > [Hijacked from cvs-committers and cvs-all] > > On Fri, 23 Jul 1999 11:28:12 +0200, Andre Albsmeier wrote: > > > I observed some kind of denial of service on -STABLE: I was > > playing with the new nmap and did a 'nmap -sU printfix'. > > inetd was running as "inetd -l" and started sucking all the > > CPU time even the nmap had been terminated long ago. > > What does "sucking all the CPU time" mean? Does it mean that other > programs were suffering, or does it mean that it was the only > significant user of CPU and so showed up at close to 100% CPU usage? > > I suspect that the latter is true. It's only nearly 50% because syslogd gets most of the other half :-) But when inetd is run without -l it get 100%. > > /var/log/messages file showed zillions of the following lines > > being added continously: > > Well, you did ask for them (inetd -l). :-) > > > Jul 23 11:21:28 printfix inetd[1743]: time from [...] > > Jul 23 11:21:28 printfix inetd[1743]: daytime from [...] > > Usually syslog will give you "last message repeated X times". > Unfortunately, the alternation of the messages makes this impossible. > > David Malone had a few ideas on "clever" handling of UDP. While what > he suggests might help reduce the number of messages you receive under > legitimate use, it won't help against DoS, since the sender of packets > can simply randomize the origin addresses. > > > Maybe you got an idea... > > I know exactly why you see what you see when you do what you do. All I > can say is "don't do that", because I can't think of a why to cater for > what you're doing in a sensible fashion. I think, I didn't describe the problem clearly so I will try again :-) 1. I run 'nmap -sU printfix' on the 192.168.17.100 machine. 2. After nmap has finished it shows me the open ports. 3. We wait , e.g. 1 minute 4. inetd, which runs with -l, continues logging to syslogd and never stops. Here is a top snapshot taken one minute later: last pid: 4040; load averages: 0.96, 0.56, 0.29 up 0+06:19:27 14:56:00 36 processes: 2 running, 34 sleeping CPU states: 54.3% user, 0.0% nice, 41.9% system, 3.9% interrupt, 0.0% idle Mem: 8500K Active, 37M Inact, 12M Wired, 3428K Cache, 7592K Buf, 532K Free Swap: 49M Total, 49M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 3748 root 58 0 956K 704K RUN 0:20 44.97% 44.97% inetd 122 root 2 0 848K 576K select 3:10 36.47% 36.47% syslogd 127 root 2 0 1588K 1228K select 0:05 0.00% 0.00% named 200 root 2 0 876K 524K select 0:02 0.00% 0.00% lpd 132 root 2 -52 1236K 732K select 0:02 0.00% 0.00% xntpd In case we start inetd without -l, it doesn't log to syslogd anymore and therefore consumes all the CPU for itself: last pid: 4397; load averages: 1.59, 1.10, 0.55 up 0+06:22:14 14:58:47 111 processes: 2 running, 109 sleeping CPU states: 61.2% user, 0.0% nice, 38.0% system, 0.8% interrupt, 0.0% idle Mem: 10M Active, 30M Inact, 14M Wired, 3776K Cache, 7592K Buf, 3688K Free Swap: 49M Total, 49M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 4043 root 104 0 956K 740K RUN 1:33 97.66% 97.61% inetd 122 root 2 0 848K 576K select 3:16 0.00% 0.00% syslogd 127 root 2 0 1588K 1228K select 0:05 0.00% 0.00% named Remember that nmap has finished already a long time ago. I think, inetd is stuck in some loop which can be terminated only by killing and restarting it. -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 6:11:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 7F9951571A; Fri, 23 Jul 1999 06:10:56 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 117f4a-000Awu-00; Fri, 23 Jul 1999 15:09:12 +0200 From: Sheldon Hearn To: Andre Albsmeier Cc: Brian Feldman , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.h In-reply-to: Your message of "Fri, 23 Jul 1999 15:06:02 +0200." <19990723150602.B10047@internal> Date: Fri, 23 Jul 1999 15:09:12 +0200 Message-ID: <42091.932735352@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Jul 1999 15:06:02 +0200, Andre Albsmeier wrote: > But when inetd is run without -l it get 100%. Are you avoiding my question on purpose? :-) > On Fri, 23-Jul-1999 at 14:29:19 +0200, Sheldon Hearn wrote: > > > What does "sucking all the CPU time" mean? Does it mean that other > > programs were suffering, or does it mean that it was the only > > significant user of CPU and so showed up at close to 100% CPU usage? I don't care how the usage is split over syslog and inetd. What I want to know is whether their combined usage of the CPU causes a serious problem for other CPU-bound processes. After all, you _have_ asked the inetd+syslog pair to do a lot of work. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 6:11:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from thoth.mch.sni.de (thoth.mch.sni.de [192.35.17.2]) by hub.freebsd.org (Postfix) with ESMTP id 3F1211571E for ; Fri, 23 Jul 1999 06:11:12 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer thoth.mch.sni.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.mch.sni.de (8.9.3/8.9.3) with ESMTP id PAA29004 for ; Fri, 23 Jul 1999 15:08:59 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id PAA03554 for ; Fri, 23 Jul 1999 15:08:57 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.9.3/8.9.3) id PAA50789 for ; Fri, 23 Jul 1999 15:08:58 +0200 (CEST) Date: Fri, 23 Jul 1999 15:08:56 +0200 From: Andre Albsmeier To: David Malone Cc: Sheldon Hearn , Andre Albsmeier , hackers@freebsd.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c inetd. Message-ID: <19990723150856.C10047@internal> References: <19990723112812.A3847@internal> <41604.932732959@axl.noc.iafrica.com> <19990723135045.A71302@bell.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <19990723135045.A71302@bell.maths.tcd.ie>; from David Malone on Fri, Jul 23, 1999 at 01:50:45PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23-Jul-1999 at 13:50:45 +0100, David Malone wrote: > On Fri, Jul 23, 1999 at 02:29:19PM +0200, Sheldon Hearn wrote: > > > Well, you did ask for them (inetd -l). :-) > > > > > Jul 23 11:21:28 printfix inetd[1743]: time from [...] > > > Jul 23 11:21:28 printfix inetd[1743]: daytime from [...] > > > > Usually syslog will give you "last message repeated X times". > > Unfortunately, the alternation of the messages makes this impossible. > > You could turn on wrapping and log them at a level at which > syslog will ignore them. I'm not sure how much this would help > with inetd chewing CPU time, but... I think, I expressed myself wrong. Not the logging appears problematic but the fact that inetd seems to be stuck in an endless loop even long time after the nmap has finished. -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 6:17:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 75F4215720; Fri, 23 Jul 1999 06:17:49 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id PAA10266; Fri, 23 Jul 1999 15:16:15 +0200 (CEST) (envelope-from des) To: Sheldon Hearn Cc: Andre Albsmeier , Brian Feldman , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.h References: <41604.932732959@axl.noc.iafrica.com> From: Dag-Erling Smorgrav Date: 23 Jul 1999 15:16:14 +0200 In-Reply-To: Sheldon Hearn's message of "Fri, 23 Jul 1999 14:29:19 +0200" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn writes: > I know exactly why you see what you see when you do what you do. All I > can say is "don't do that", because I can't think of a why to cater for > what you're doing in a sensible fashion. I think you're jumping to conclusions. What I'd like to see is a tcpdump log of the UDP scan ('tcpdump -i ed0 udp or icmp'). Yes, I know it's going to be huge. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 6:18: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id BA76215717; Fri, 23 Jul 1999 06:17:54 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 23 Jul 1999 14:16:20 +0100 (BST) Date: Fri, 23 Jul 1999 14:16:19 +0100 From: David Malone To: Andre Albsmeier Cc: Sheldon Hearn , Brian Feldman , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c inetd. Message-ID: <19990723141619.A11312@walton.maths.tcd.ie> References: <19990723112812.A3847@internal> <41604.932732959@axl.noc.iafrica.com> <19990723150602.B10047@internal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <19990723150602.B10047@internal>; from Andre Albsmeier on Fri, Jul 23, 1999 at 03:06:02PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 23, 1999 at 03:06:02PM +0200, Andre Albsmeier wrote: > It's only nearly 50% because syslogd gets most of the other half :-) > > But when inetd is run without -l it get 100%. Interesting - does it still answer requests during this time? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 6:18:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 1FFB21577D for ; Fri, 23 Jul 1999 06:18:35 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.14]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id PAA07196 for ; Fri, 23 Jul 1999 15:18:33 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail2.siemens.de (8.9.3/8.9.3) with ESMTP id PAA06697 for ; Fri, 23 Jul 1999 15:18:32 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.9.3/8.9.3) id PAA50896 for ; Fri, 23 Jul 1999 15:18:33 +0200 (CEST) Date: Fri, 23 Jul 1999 15:18:31 +0200 From: Andre Albsmeier To: Sheldon Hearn Cc: Andre Albsmeier , Brian Feldman , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.h Message-ID: <19990723151831.D10047@internal> References: <19990723150602.B10047@internal> <42091.932735352@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <42091.932735352@axl.noc.iafrica.com>; from Sheldon Hearn on Fri, Jul 23, 1999 at 03:09:12PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23-Jul-1999 at 15:09:12 +0200, Sheldon Hearn wrote: > > > On Fri, 23 Jul 1999 15:06:02 +0200, Andre Albsmeier wrote: > > > But when inetd is run without -l it get 100%. > > Are you avoiding my question on purpose? :-) Sorry. The machine wasn't stressed by other programs so it was "the only significant user of CPU and so showed up at close to 100% CPU usage". But when I logged into it to kill and restart inetd the machine was responding very slow. > > On Fri, 23-Jul-1999 at 14:29:19 +0200, Sheldon Hearn wrote: > > > > > What does "sucking all the CPU time" mean? Does it mean that other > > > programs were suffering, or does it mean that it was the only > > > significant user of CPU and so showed up at close to 100% CPU usage? > > I don't care how the usage is split over syslog and inetd. What I want > to know is whether their combined usage of the CPU causes a serious > problem for other CPU-bound processes. Yes. > > After all, you _have_ asked the inetd+syslog pair to do a lot of work. Why? I start nmap, it scans the ports and inetd has for sure a lot of logging work to do. But at some time, the scan is finished but inetd continues to consume CPU time endlessly. Maybe I am just confused and this behaviour is normal ... -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 6:26: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 303CA14FE4 for ; Fri, 23 Jul 1999 06:25:57 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id PAA09755 for ; Fri, 23 Jul 1999 15:25:36 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id PAA08496 for ; Fri, 23 Jul 1999 15:25:34 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.9.3/8.9.3) id PAA50951 for ; Fri, 23 Jul 1999 15:25:35 +0200 (CEST) Date: Fri, 23 Jul 1999 15:25:31 +0200 From: Andre Albsmeier To: David Malone Cc: Andre Albsmeier , Sheldon Hearn , Brian Feldman , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c inetd. Message-ID: <19990723152531.E10047@internal> References: <19990723112812.A3847@internal> <41604.932732959@axl.noc.iafrica.com> <19990723150602.B10047@internal> <19990723141619.A11312@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <19990723141619.A11312@walton.maths.tcd.ie>; from David Malone on Fri, Jul 23, 1999 at 02:16:19PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23-Jul-1999 at 14:16:19 +0100, David Malone wrote: > On Fri, Jul 23, 1999 at 03:06:02PM +0200, Andre Albsmeier wrote: > > > It's only nearly 50% because syslogd gets most of the other half :-) > > > > But when inetd is run without -l it get 100%. > > Interesting - does it still answer requests during this time? Yes. I can still log in via the network and kill and restart inetd. Just found another syslog message (I didn't see it before because it disappeared in all the loge messages): Jul 23 15:20:51 printfix inetd[5323]: chargen/udp server failing (looping), service terminated -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 6:28:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id CC54514CC6; Fri, 23 Jul 1999 06:28:14 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 117fLx-000B0k-00; Fri, 23 Jul 1999 15:27:09 +0200 From: Sheldon Hearn To: David Malone Cc: Andre Albsmeier , Brian Feldman , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c inetd. In-reply-to: Your message of "Fri, 23 Jul 1999 14:16:19 +0100." <19990723141619.A11312@walton.maths.tcd.ie> Date: Fri, 23 Jul 1999 15:27:09 +0200 Message-ID: <42329.932736429@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Jul 1999 14:16:19 +0100, David Malone wrote: > > But when inetd is run without -l it get 100%. > > Interesting - does it still answer requests during this time? Yeah. What we really need to know is how many packets inetd actually received. The manpage excerpt that DES showed us indicates that nmap doesn't stop sending packets immediately unless it gets an ICMP message back. We know that inetd doesn't send ICMP messages back. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 6:36:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 5244114F34 for ; Fri, 23 Jul 1999 06:36:31 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.14]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id PAA13292 for ; Fri, 23 Jul 1999 15:34:19 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail2.siemens.de (8.9.3/8.9.3) with ESMTP id PAA12773 for ; Fri, 23 Jul 1999 15:34:17 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.9.3/8.9.3) id PAA51088 for ; Fri, 23 Jul 1999 15:34:18 +0200 (CEST) Date: Fri, 23 Jul 1999 15:34:16 +0200 From: Andre Albsmeier To: Dag-Erling Smorgrav Cc: Sheldon Hearn , Andre Albsmeier , Brian Feldman , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.h Message-ID: <19990723153416.F10047@internal> References: <41604.932732959@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: ; from Dag-Erling Smorgrav on Fri, Jul 23, 1999 at 03:16:14PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23-Jul-1999 at 15:16:14 +0200, Dag-Erling Smorgrav wrote: > Sheldon Hearn writes: > > I know exactly why you see what you see when you do what you do. All I > > can say is "don't do that", because I can't think of a why to cater for > > what you're doing in a sensible fashion. > > I think you're jumping to conclusions. What I'd like to see is a > tcpdump log of the UDP scan ('tcpdump -i ed0 udp or icmp'). Yes, I > know it's going to be huge. Comes in private email. It's about 130KB after which tcpdump crashed with: zsh: 5741 segmentation fault tcpdump -i fxp0 150 udp or icmp But when I restart tcpdump again (while inetd still is going wild) it is quiet. -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 6:36:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 92D8A15728; Fri, 23 Jul 1999 06:36:53 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id PAA10740; Fri, 23 Jul 1999 15:35:49 +0200 (CEST) (envelope-from des) To: Andre Albsmeier Cc: Dag-Erling Smorgrav , Sheldon Hearn , Brian Feldman , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.h References: <41604.932732959@axl.noc.iafrica.com> <19990723153416.F10047@internal> From: Dag-Erling Smorgrav Date: 23 Jul 1999 15:35:48 +0200 In-Reply-To: Andre Albsmeier's message of "Fri, 23 Jul 1999 15:34:16 +0200" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andre Albsmeier writes: > Comes in private email. It's about 130KB after which tcpdump crashed with: > > zsh: 5741 segmentation fault tcpdump -i fxp0 150 udp or icmp Weird. Very weird. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 6:55:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from thoth.mch.sni.de (thoth.mch.sni.de [192.35.17.2]) by hub.freebsd.org (Postfix) with ESMTP id 3124714D7D for ; Fri, 23 Jul 1999 06:55:07 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer thoth.mch.sni.de) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.14]) by thoth.mch.sni.de (8.9.3/8.9.3) with ESMTP id PAA04952 for ; Fri, 23 Jul 1999 15:53:51 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail2.siemens.de (8.9.3/8.9.3) with ESMTP id PAA21339 for ; Fri, 23 Jul 1999 15:53:48 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.9.3/8.9.3) id PAA51393 for ; Fri, 23 Jul 1999 15:53:49 +0200 (CEST) Date: Fri, 23 Jul 1999 15:53:48 +0200 From: Andre Albsmeier To: Dag-Erling Smorgrav Cc: Andre Albsmeier , Sheldon Hearn , Brian Feldman , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.h Message-ID: <19990723155348.J10047@internal> References: <41604.932732959@axl.noc.iafrica.com> <19990723153416.F10047@internal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: ; from Dag-Erling Smorgrav on Fri, Jul 23, 1999 at 03:35:48PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23-Jul-1999 at 15:35:48 +0200, Dag-Erling Smorgrav wrote: > Andre Albsmeier writes: > > Comes in private email. It's about 130KB after which tcpdump crashed with: > > > > zsh: 5741 segmentation fault tcpdump -i fxp0 150 udp or icmp > > Weird. Very weird. Just to overcome speculations :-) I just tested it on another machine with the same result. If have tested it now between all 3 machines in each direction. Same result. It should be reproducible very easily by running "nmap -sU target_machine" where target_machine has the internal inetd services enabled. I attach my inetd.conf in case it might be interesting (nothing special in it): # $Id: inetd.conf,v 1.33.2.1 1999/07/21 19:28:25 sheldonh Exp $ # # Internet server configuration database # # @(#)inetd.conf 5.4 (Berkeley) 6/30/90 # ftp stream tcp nowait root /usr/libexec/ftpd ftpd telnet stream tcp nowait root /usr/libexec/telnetd telnetd shell stream tcp nowait root /usr/libexec/rshd rshd login stream tcp nowait root /usr/libexec/rlogind rlogind finger stream tcp nowait/3/10 nobody /usr/libexec/fingerd fingerd #exec stream tcp nowait root /usr/libexec/rexecd rexecd #uucpd stream tcp nowait root /usr/libexec/uucpd uucpd #nntp stream tcp nowait usenet /usr/libexec/nntpd nntpd # run comsat as root to be able to print partial mailbox contents w/ biff, # or use the safer tty:tty to just print that new mail has been received. #comsat dgram udp wait tty:tty /usr/libexec/comsat comsat ntalk dgram udp wait tty:tty /usr/libexec/ntalkd ntalkd #tftp dgram udp wait nobody /usr/libexec/tftpd tftpd /tftpboot #bootps dgram udp wait root /usr/libexec/bootpd bootpd # # "Small servers" -- used to be standard on, but we're more conservative # about things due to Internet security concerns. Only turn on what you # need. # daytime stream tcp nowait root internal daytime dgram udp wait root internal time stream tcp nowait root internal time dgram udp wait root internal echo stream tcp nowait root internal echo dgram udp wait root internal discard stream tcp nowait root internal discard dgram udp wait root internal chargen stream tcp nowait root internal chargen dgram udp wait root internal # # Kerberos authenticated services # #klogin stream tcp nowait root /usr/libexec/rlogind rlogind -k #eklogin stream tcp nowait root /usr/libexec/rlogind rlogind -k -x #kshell stream tcp nowait root /usr/libexec/rshd rshd -k #kip stream tcp nowait root /usr/libexec/kipd kipd # # CVS servers - for master CVS repositories only! # #cvspserver stream tcp nowait root /usr/bin/cvs cvs pserver #cvs stream tcp nowait root /usr/bin/cvs cvs kserver # # RPC based services (you MUST have portmapper running to use these) # rstatd/1-3 dgram rpc/udp wait root /usr/libexec/rpc.rstatd rpc.rstatd rusersd/1-2 dgram rpc/udp wait root /usr/libexec/rpc.rusersd rpc.rusersd walld/1 dgram rpc/udp wait root /usr/libexec/rpc.rwalld rpc.rwalld #pcnfsd/1-2 dgram rpc/udp wait root /usr/libexec/rpc.pcnfsd rpc.pcnfsd #rquotad/1 dgram rpc/udp wait root /usr/libexec/rpc.rquotad rpc.rquotad sprayd/1 dgram rpc/udp wait root /usr/libexec/rpc.sprayd rpc.sprayd # # example entry for the optional pop3 server # #pop3 stream tcp nowait root /usr/local/libexec/popper popper # # example entry for the optional imap4 server # #imap4 stream tcp nowait root /usr/local/libexec/imapd imapd # # Return error for all "ident" requests # #auth stream tcp nowait root internal # # example entry for the optional ident server # auth stream tcp wait kmem:kmem /usr/local/sbin/identd identd -w -t120 # # example entry for the optional qmail MTA # #smtp stream tcp nowait qmaild /var/qmail/bin/tcp-env tcp-env /var/qmail/bin/qmail-smtpd # # Enable the following two entries to enable samba startup from inetd # (from the Samba documentation). # #netbios-ssn stream tcp nowait root /usr/local/sbin/smbd smbd #netbios-ns dgram udp wait root /usr/local/sbin/nmbd nmbd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 7: 0:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 2E2D31570B; Fri, 23 Jul 1999 07:00:38 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id PAA11272; Fri, 23 Jul 1999 15:57:19 +0200 (CEST) (envelope-from des) To: Andre Albsmeier Cc: Dag-Erling Smorgrav , Sheldon Hearn , Brian Feldman , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.h References: <41604.932732959@axl.noc.iafrica.com> <19990723153416.F10047@internal> <19990723155348.J10047@internal> From: Dag-Erling Smorgrav Date: 23 Jul 1999 15:57:19 +0200 In-Reply-To: Andre Albsmeier's message of "Fri, 23 Jul 1999 15:53:48 +0200" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andre Albsmeier writes: > Just to overcome speculations :-) I just tested it on another machine > with the same result. If have tested it now between all 3 machines in > each direction. Same result. Weird. I'm unable to reproduce it; my test box responds to UDP queries but does not log them (though it logs TCP queries). I'll update to the latest inetd and try again. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 7:18:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 8144D14D3B; Fri, 23 Jul 1999 07:18:33 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 23 Jul 1999 15:14:40 +0100 (BST) Date: Fri, 23 Jul 1999 15:14:40 +0100 From: David Malone To: Dag-Erling Smorgrav Cc: Andre Albsmeier , Sheldon Hearn , Brian Feldman , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c inetd. Message-ID: <19990723151440.A14016@walton.maths.tcd.ie> References: <41604.932732959@axl.noc.iafrica.com> <19990723153416.F10047@internal> <19990723155348.J10047@internal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Dag-Erling Smorgrav on Fri, Jul 23, 1999 at 03:57:19PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 23, 1999 at 03:57:19PM +0200, Dag-Erling Smorgrav wrote: > Andre Albsmeier writes: > > Just to overcome speculations :-) I just tested it on another machine > > with the same result. If have tested it now between all 3 machines in > > each direction. Same result. > > Weird. I'm unable to reproduce it; my test box responds to UDP queries > but does not log them (though it logs TCP queries). I'll update to the > latest inetd and try again. I can reproduce it using version 1.63, ktracing shows: 3052 inetd CALL sigprocmask(0x1,0x82001) 3052 inetd RET sigprocmask 0 3052 inetd CALL sigprocmask(0x3,0) 3052 inetd RET sigprocmask 532481/0x82001 3052 inetd CALL gettimeofday(0xbfbfd5e4,0) 3052 inetd RET gettimeofday 0 3052 inetd CALL write(0xc,0xbfbfd60c,0x1a) 3052 inetd RET write -1 errno 39 Destination address required 3052 inetd CALL select(0x14,0xbfbfd750,0,0,0) 3052 inetd RET select 2 3052 inetd CALL sigprocmask(0x1,0x82001) 3052 inetd RET sigprocmask 0 3052 inetd CALL sigprocmask(0x3,0) 3052 inetd RET sigprocmask 532481/0x82001 3052 inetd CALL gettimeofday(0xbfbfd6f4,0) 3052 inetd RET gettimeofday 0 3052 inetd CALL write(0xe,0xbfbfd708,0x4) 3052 inetd RET write -1 errno 39 Destination address required 3052 inetd CALL sigprocmask(0x1,0x82001) 3052 inetd RET sigprocmask 0 3052 inetd CALL sigprocmask(0x3,0) 3052 inetd RET sigprocmask 532481/0x82001 It also seems to leave several hung processes around which are serveing disgard and echo. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 7:37:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from thneed.ubergeeks.com (thneed.ubergeeks.com [206.205.41.245]) by hub.freebsd.org (Postfix) with ESMTP id B710314CDE for ; Fri, 23 Jul 1999 07:37:30 -0700 (PDT) (envelope-from adrian@ubergeeks.com) Received: from localhost (adrian@localhost) by thneed.ubergeeks.com (8.9.3/8.9.3) with ESMTP id KAA04108; Fri, 23 Jul 1999 10:35:32 -0400 (EDT) (envelope-from adrian@ubergeeks.com) X-Authentication-Warning: thneed.ubergeeks.com: adrian owned process doing -bs Date: Fri, 23 Jul 1999 10:35:32 -0400 (EDT) From: Adrian Filipi-Martin Reply-To: Adrian Filipi-Martin To: Alex Zepeda Cc: Vincent Poy , hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Jul 1999, Alex Zepeda wrote: > On Thu, 22 Jul 1999, Adrian Filipi-Martin wrote: > > > I know a lot of people like the ASUS P2B boards, but I've noticed a > > tendency for the systems to reset occasionally when plugging in a keyboard. > > I've seen this with both FreeBSD and NT, so I'm considering it a property > > of the board. > > If this is a PS/2 style keyboard, don't plug and unplug them when the host > is powered up. The PS/2 style stuf seems to be very sensitive to that > sort of thing. If it was a USB keyboard doing that... then that would be > odd. Yes, it is a PS/2 keyboard, but these are the only MB's that I have run into this problem with other than some AIX boxes years ago that would blow a fuse when disconnecting the keyboard from a running system. This isn't that big a problem. I only have keyboard installed while building the systems. Thereafter they are serial console only. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 7:39:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from thneed.ubergeeks.com (thneed.ubergeeks.com [206.205.41.245]) by hub.freebsd.org (Postfix) with ESMTP id 1B1B314D48 for ; Fri, 23 Jul 1999 07:39:36 -0700 (PDT) (envelope-from adrian@ubergeeks.com) Received: from localhost (adrian@localhost) by thneed.ubergeeks.com (8.9.3/8.9.3) with ESMTP id KAA04112; Fri, 23 Jul 1999 10:39:03 -0400 (EDT) (envelope-from adrian@ubergeeks.com) X-Authentication-Warning: thneed.ubergeeks.com: adrian owned process doing -bs Date: Fri, 23 Jul 1999 10:39:03 -0400 (EDT) From: Adrian Filipi-Martin Reply-To: Adrian Filipi-Martin To: Vincent Poy Cc: hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Jul 1999, Vincent Poy wrote: > On Thu, 22 Jul 1999, Adrian Filipi-Martin wrote: > > > > On Thu, 22 Jul 1999, Adrian Filipi-Martin wrote: > > > > > > > I've had great results with the Tyan 1836DLUAN/Thunder 100's. > > > > I've got several boxes with 1GB of RAM and dual 450's humming along. For > > > > comparison one system with less memory and a SuperMicro board but identical > > > > system software has had a couple of wierd spontaneous reboots over the last > > > > few months. > > > > > > Cool... Is 1GB of ram really needed? We used to run a 64 meg > > > system then 128 meg and then 384 meg, it doesn't seem to do much even for > > > a heavily loaded ISP Server. > > > > Not really. The customer whose box this is chose this much memory > > because his previous server was a 256MB UltraSparc that was swamped all the > > time with a load of 6 to 7. > > > > The real problem was poor CGI programming. I made them fix them. > > Now it toodles along with ridiculously low loads. All the websites and the > > mysql db fit in core. ;-) > > That's true too.... Seems like FreeBSD can handle a real high load > without problems... If you can believe it they drove the system load up to 114 with their horrible Perl CGI's. Ammazingly, I could type "sudo apachectl stop" and wait 30 seconds or so for it to run. 114 and I didn't need to reboot the system. I was pleasantly surprised. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 7:55:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from omega.honk.org (cpu1120.adsl.bellglobal.com [207.236.110.101]) by hub.freebsd.org (Postfix) with ESMTP id 6414B14D48 for ; Fri, 23 Jul 1999 07:55:20 -0700 (PDT) (envelope-from awillis@omega.honk.org) Received: from omega.honk.org (omega.honk.org [192.168.2.3]) by omega.honk.org (8.9.2/8.9.2) with ESMTP id KAA71840 for ; Fri, 23 Jul 1999 10:54:52 GMT (envelope-from awillis@omega.honk.org) Date: Fri, 23 Jul 1999 10:54:52 +0000 (GMT) From: Andrew Willis To: freebsd-hackers@freebsd.org Subject: boot problems 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 Perhaps someone can help me with this...I just bought a new computer. (2) pII 400 chips (1) Intel 1440GX (Dual CPU PIII) motherboard (2) 256 MB SDRAM (1) Mylex Raid 960 model 150 adapter (3) Quantum Atlas IV 9.1 GB Ultra2 SCSI (1) CDROM 40x (1) Floppy 1.44 (1) Server case with redundant power supply I wanted to install FreeBSD as a web server, but every time i try and boot off the first install disk kern.flp 3.2-RELEASE, the machine halts with a hex dump. The machine has an onboard scsi (Adaptec AIC-7896). OpenBSD 2.5 and FreeBSD 2.2.8 will boot, but they dont recognize the disk controller. I was told FreeBSD supports the Mylex raid. Someone please help me with this...I have tried two different floppies as well. Im using dd if=kern.flp of=/dev/fd0 on a sun ultra 5 to make the disk image. Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 8:32:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 1E72314C4A for ; Fri, 23 Jul 1999 08:32:12 -0700 (PDT) (envelope-from rminnich@acl.lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id JAA187142 for ; Fri, 23 Jul 1999 09:30:54 -0600 (MDT) Date: Fri, 23 Jul 1999 09:30:54 -0600 From: "Ronald G. Minnich" To: freebsd-hackers@FreeBSD.ORG Subject: Re: Filesystem question... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Jul 1999, Kris Kennaway wrote: > On Thu, 22 Jul 1999, Ronald G. Minnich wrote: > > Are you saying that as an ordinary user I can mount something on top of > > /tmp, for example? > If the vfs.usermount sysctl is 1, and you have appropriate access to the > thing you're trying to mount (block device, etc). OK, so let's say it is 1. Let's say I have "appropriate access" to /tmp. I mount my own fs on /tmp. I now have read/write access to everything anyone writes to /tmp. Or, let's say I don't have "appropriate access" to /tmp. Pick some other place. I mount my file system there for my files. Now everyone who wants can look for these user mounts and walk them at will. My private stuff is quite public. User mounts are neat. But user mounts that modify the global name space of the machine are not neat. User mounts should be part of a private name space. But thanks for the note. I just now realized that if I add a private name space to v9fs (which is easy), and then turn on user mounts, user processes can have private name spaces on freebsd! thanks ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 8:34: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 2632414E73 for ; Fri, 23 Jul 1999 08:34:06 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id IAA71666; Fri, 23 Jul 1999 08:33:53 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: itojun@iijlab.net Cc: Jeroen Ruigrok/Asmodai , hackers@FreeBSD.ORG Subject: Re: Will FreeBSD ever see native IPv6 ?? In-reply-to: Your message of "Fri, 23 Jul 1999 19:01:41 +0900." <9128.932724101@coconut.itojun.org> Date: Fri, 23 Jul 1999 08:33:53 -0700 Message-ID: <71662.932744033@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > FreeBSD can wait till unified-ipv6 is made available, since: > - IPv6 is not that urgent task and > - it will be messy if FreeBSD integrates KAME first, > then switch to unified-ipv6. Both of these remain true. I certainly see and understand the "marketing value" of having an early IPv6 implementation, but I don't see this as mainstream interest so much as interest on the part of various researchers and early-adopters, all of which can go to the KAME site and grab the patches to 3.2-stable if they want to play now, today. If we haven't done a good enough job of making that clear and are suffering from defections to other *BSDs because of this, then we just need to get the word out better. :-) It's not like nothing is available at all, simply not "officially" and officially we have an obligation to pick the best, most technically correct route, something which I believe we have already done. Two merges sounds like a nightmare, and we're not suffering from NetBSD's release constraints here. :) > - We need some more FreeBSD commit privs for other KAME guys. > (this is a easy part) Yes, this is certainly the easy part. As always, just let us know if there's anything we can do. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 8:38:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 7B8B215119; Fri, 23 Jul 1999 08:38:36 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 23 Jul 1999 16:37:21 +0100 (BST) Date: Fri, 23 Jul 1999 16:37:20 +0100 From: David Malone To: Dag-Erling Smorgrav Cc: Andre Albsmeier , Sheldon Hearn , Brian Feldman , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.h Message-ID: <19990723163720.A15697@walton.maths.tcd.ie> References: <41604.932732959@axl.noc.iafrica.com> <19990723153416.F10047@internal> <19990723155348.J10047@internal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Dag-Erling Smorgrav on Fri, Jul 23, 1999 at 03:57:19PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've found the problem - it looks like a bug in the code for matching internal service names to /etc/service names. The code says: if ((bi->bi_socktype == sep->se_socktype && strcmp(bi->bi_service, sep->se_service) == 0) || matchservent(bi->bi_service, sep->se_service, sep->se_proto)) It should probably say: if (bi->bi_socktype == sep->se_socktype && ((strcmp(bi->bi_service, sep->se_service) == 0) || matchservent(bi->bi_service, sep->se_service, sep->se_proto))) It was running the tcp service instead of the udp service. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 9: 7: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 22C8114CAB for ; Fri, 23 Jul 1999 09:07:00 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA25958; Fri, 23 Jul 1999 09:06:01 -0700 (PDT) (envelope-from dillon) Date: Fri, 23 Jul 1999 09:06:01 -0700 (PDT) From: Matthew Dillon Message-Id: <199907231606.JAA25958@apollo.backplane.com> To: Doug Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf leakage in NFSv3 writes, possbile? References: <199907222246.SAA81283@cs.rpi.edu> <37980EBC.C38668E1@gorean.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :"David E. Cross" wrote: :> :> Well, I just -STABLED the server to see if it fixed it, but I was certainly :> running out. the server had only 3000-ish mbuf chains, and it would go through :> them all in a day. : : Well, have you tried increasing the number of available mbufs and see if :you reach a point of stability? Assuming you have enough physical ram you :could do 15k mbufs on -Stable without a problem. Check LINT for the :nmbclusters option if you need help with it. : :Good luck, : :Doug Well, the cache shouldn't eat up *that* many mbufs! The problem is likely to be real. There is a good chance the leakage is in nfs_serv.c, which I fixed for -current. I do not think those changes have been backported to -STABLE. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 9: 8: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 746BA15734 for ; Fri, 23 Jul 1999 09:08:01 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA25968; Fri, 23 Jul 1999 09:06:40 -0700 (PDT) (envelope-from dillon) Date: Fri, 23 Jul 1999 09:06:40 -0700 (PDT) From: Matthew Dillon Message-Id: <199907231606.JAA25968@apollo.backplane.com> To: Nick Hibma Cc: "Matthew D. Fuller" , Len Conrad , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD: the stealth OS? References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : > > lot of things FreeBSD is 'better' at, and a lot of those : > > things can easily fluctuate on a daily or weekly basis," : > > said Fuller, who maintains a Linux vs BSD Web page. : > > "Thus, any definitive narrow statement that can be made : > > is usually obsolete before anyone hears it.". : > > : > > Perfect! : > : > Thank you, my fans! Please leave your monetary contributions in the hat : > on your way out ;> : :Where is the hat? I saw Julian running off with it a couple of e-mails :ago. : :Nick Do I get a discount for having the same first name? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 9:14: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 8458D14D70 for ; Fri, 23 Jul 1999 09:13:54 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 23 Jul 1999 17:13:09 +0100 (BST) Date: Fri, 23 Jul 1999 17:13:08 +0100 From: David Malone To: Matthew Dillon Cc: Doug , "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf leakage in NFSv3 writes, possbile? Message-ID: <19990723171308.A16508@walton.maths.tcd.ie> References: <199907222246.SAA81283@cs.rpi.edu> <37980EBC.C38668E1@gorean.org> <199907231606.JAA25958@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199907231606.JAA25958@apollo.backplane.com>; from Matthew Dillon on Fri, Jul 23, 1999 at 09:06:01AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 23, 1999 at 09:06:01AM -0700, Matthew Dillon wrote: > There is a good chance the leakage is in nfs_serv.c, which I fixed for > -current. > > I do not think those changes have been backported to -STABLE. julian 1999/06/30 15:05:20 PDT Modified files: (Branch: RELENG_3) sys/nfs nfs_serv.c nfs_subs.c nfs_syscalls.c nfsm_subs.h Log: MFC: Bring in NFS cleanups by Matt. . . . David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 9:34:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 4B9E71504D for ; Fri, 23 Jul 1999 09:34:46 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA26194; Fri, 23 Jul 1999 09:34:36 -0700 (PDT) (envelope-from dillon) Date: Fri, 23 Jul 1999 09:34:36 -0700 (PDT) From: Matthew Dillon Message-Id: <199907231634.JAA26194@apollo.backplane.com> To: David Malone Cc: Doug , "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf leakage in NFSv3 writes, possbile? References: <199907222246.SAA81283@cs.rpi.edu> <37980EBC.C38668E1@gorean.org> <199907231606.JAA25958@apollo.backplane.com> <19990723171308.A16508@walton.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> I do not think those changes have been backported to -STABLE. : :julian 1999/06/30 15:05:20 PDT : : Modified files: (Branch: RELENG_3) : sys/nfs nfs_serv.c nfs_subs.c nfs_syscalls.c : nfsm_subs.h : Log: : MFC: Bring in NFS cleanups by Matt. :. : David. Whup! So much for that idea! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 10:40:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from omega.honk.org (cpu1120.adsl.bellglobal.com [207.236.110.101]) by hub.freebsd.org (Postfix) with ESMTP id 87E8614DCF for ; Fri, 23 Jul 1999 10:40:24 -0700 (PDT) (envelope-from awillis@omega.honk.org) Received: from omega.honk.org (omega.honk.org [192.168.2.3]) by omega.honk.org (8.9.2/8.9.2) with ESMTP id NAA73446 for ; Fri, 23 Jul 1999 13:43:28 GMT (envelope-from awillis@omega.honk.org) Date: Fri, 23 Jul 1999 13:43:28 +0000 (GMT) From: Andrew Willis To: freebsd-hackers@freebsd.org Subject: boot problems (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After the System Halted error, i get another error message. "DAC960: system BIOS fatal Error - INT 15H function 87H Copy extended Memory ) failed." ---------- Forwarded message ---------- Date: Fri, 23 Jul 1999 10:54:52 +0000 (GMT) From: Andrew Willis To: freebsd-hackers@freebsd.org Subject: boot problems Perhaps someone can help me with this...I just bought a new computer. (2) pII 400 chips (1) Intel 1440GX (Dual CPU PIII) motherboard (2) 256 MB SDRAM (1) Mylex Raid 960 model 150 adapter (3) Quantum Atlas IV 9.1 GB Ultra2 SCSI (1) CDROM 40x (1) Floppy 1.44 (1) Server case with redundant power supply I wanted to install FreeBSD as a web server, but every time i try and boot off the first install disk kern.flp 3.2-RELEASE, the machine halts with a hex dump. The machine has an onboard scsi (Adaptec AIC-7896). OpenBSD 2.5 and FreeBSD 2.2.8 will boot, but they dont recognize the disk controller. I was told FreeBSD supports the Mylex raid. Someone please help me with this...I have tried two different floppies as well. Im using dd if=kern.flp of=/dev/fd0 on a sun ultra 5 to make the disk image. Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 10:48: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 20C2A14C0A for ; Fri, 23 Jul 1999 10:48:00 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id NAA94297; Fri, 23 Jul 1999 13:47:47 -0400 (EDT) Message-Id: <199907231747.NAA94297@cs.rpi.edu> To: Matthew Dillon Cc: David Malone , Doug , "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: mbuf leakage in NFSv3 writes, possbile? In-Reply-To: Message from Matthew Dillon of "Fri, 23 Jul 1999 09:34:36 PDT." <199907231634.JAA26194@apollo.backplane.com> Date: Fri, 23 Jul 1999 13:47:45 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, here are some real stats.... "w" is the read-only machine, it services everything that "s" (the read-write machine) does... in fact it services more. *w crossd $ strings -a /kernel | grep \^___maxusers ___maxusers 96 *w crossd $ uname -a FreeBSD w.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #1: Tue Jun 29 09:36:32 EDT 1999 root@w.cs.rpi.edu:/usr/src/sys/compile/WOBBLE i386 *w crossd $ uptime 1:43PM up 24 days, 2:08, 3 users, load averages: 0.00, 0.00, 0.00 *w crossd $ netstat -m 106/2688 mbufs in use: 85 mbufs allocated to data 21 mbufs allocated to packet headers 64/426/2048 mbuf clusters in use (current/peak/max) 1188 Kbytes allocated to network (11% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines *s crossd $ uname -a FreeBSD s.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #0: Thu Jul 22 18:12:21 EDT 1999 root@phoenix.cs.rpi.edu:/usr/src/sys/compile/STAGGER i386 *s crossd $ strings -a /kernel | grep \^___maxusers ___maxusers 512 *s crossd $ uptime 1:43PM up 19:23, 2 users, load averages: 0.02, 0.01, 0.00 *s crossd $ netstat -m 3629/4096 mbufs in use: 3621 mbufs allocated to data 8 mbufs allocated to packet headers 3550/3660/8704 mbuf clusters in use (current/peak/max) 7832 Kbytes allocated to network (96% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 10:54:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 6545814C04 for ; Fri, 23 Jul 1999 10:54:00 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id KAA15626; Fri, 23 Jul 1999 10:52:19 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA76627; Fri, 23 Jul 1999 10:52:17 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 23 Jul 1999 10:52:17 -0700 (PDT) Message-Id: <199907231752.KAA76627@vashon.polstra.com> To: dcs@newsguy.com Subject: Re: Proposed substitution for ACLs In-Reply-To: <37882150.87A93451@newsguy.com> References: <3787FB9D.3CDF0839@bellatlantic.net> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <37882150.87A93451@newsguy.com>, Daniel C. Sobral wrote: > > Do whatever you want: as a fs layer. That would be good advice, if FS layers worked. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 10:57:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 672F314BF9 for ; Fri, 23 Jul 1999 10:57:27 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA26775; Fri, 23 Jul 1999 10:55:28 -0700 (PDT) (envelope-from dillon) Date: Fri, 23 Jul 1999 10:55:28 -0700 (PDT) From: Matthew Dillon Message-Id: <199907231755.KAA26775@apollo.backplane.com> To: John Polstra Cc: dcs@newsguy.com, hackers@FreeBSD.ORG Subject: Re: Proposed substitution for ACLs References: <3787FB9D.3CDF0839@bellatlantic.net> <199907231752.KAA76627@vashon.polstra.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In article <37882150.87A93451@newsguy.com>, :Daniel C. Sobral wrote: :> :> Do whatever you want: as a fs layer. : :That would be good advice, if FS layers worked. : :John :-- : John Polstra jdp@polstra.com : John D. Polstra & Co., Inc. Seattle, Washington USA Maybe the best thing to do is to wait until FS layers are fixed later this year. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 11: 0:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 326EA14BF9 for ; Fri, 23 Jul 1999 11:00:24 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA54066; Fri, 23 Jul 1999 11:59:13 -0600 (MDT) (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 LAA20011; Fri, 23 Jul 1999 11:59:34 -0600 (MDT) Message-Id: <199907231759.LAA20011@harmony.village.org> To: Dirk GOUDERS Subject: Re: SURVEY: Sound cards that work under FreeBSD Cc: John Reynolds~ , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 23 Jul 1999 09:10:24 +0200." <199907230710.JAA04436@musashi.et.bocholt.fh-ge.de> References: <199907230710.JAA04436@musashi.et.bocholt.fh-ge.de> Date: Fri, 23 Jul 1999 11:59:34 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199907230710.JAA04436@musashi.et.bocholt.fh-ge.de> Dirk GOUDERS writes: : My sound card is a SBPCI128 by Creative Labs. Nice card... I have one too. Plays mp3 well :-). Also plays video sound well and xgalaga works with sound!... NOTE: The SBPC64 doesn't work without an external patch... Be careful. : I only used the card with FreeBSD 3.2 I've used mine on -CURRENT for about 9 months or so, but part of that time I had to get the driver from somewhere else. : The only line I had to add to my kernel config file was: : : device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0 : : (This causes a message "pcm0 not found" to appear at boot time but : just ignoring it seems to be o.k. - allthough I would prefer : not to see it, at all.) device pcm0 does the trick for me. I think that will work in 3.2. -current fixes the problem with psm0 not found. : I had to build the audio device snd1: : : # cd /dev : # sh MKDEV snd1 When you upgrade to 4.0 or -current, you'll have to undo that stuff... : and to use the mixer to set the volume to another value than 0. : I use the following script /usr/local/etc/rc.d/mixer.sh at boot time: : : #!/bin/sh : /usr/sbin/mixer vol 60:60 pcm 60:60 cd 60:60 Cool. I've always brought up xmixer to do this.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 11:24:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 275D214BF9 for ; Fri, 23 Jul 1999 11:24:49 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id LAA05492; Fri, 23 Jul 1999 11:21:53 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id LAA21528; Fri, 23 Jul 1999 11:20:54 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA23194; Fri, 23 Jul 99 11:21:40 PDT Message-Id: <3798B2B4.9BB398AE@softweyr.com> Date: Fri, 23 Jul 1999 12:21:40 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Matthew Dillon Cc: Nick Hibma , "Matthew D. Fuller" , Len Conrad , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD: the stealth OS? References: <199907231606.JAA25968@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > : > > lot of things FreeBSD is 'better' at, and a lot of those > : > > things can easily fluctuate on a daily or weekly basis," > : > > said Fuller, who maintains a Linux vs BSD Web page. > : > > "Thus, any definitive narrow statement that can be made > : > > is usually obsolete before anyone hears it.". > : > > > : > > Perfect! > : > > : > Thank you, my fans! Please leave your monetary contributions in the hat > : > on your way out ;> > : > :Where is the hat? I saw Julian running off with it a couple of e-mails > :ago. He was going to cut off the point and use it as a funnel into his BSD Toy fund. Or was that the wrong hat (or the wrong Julian?) > Do I get a discount for having the same first name? Nope, you get charged double for attempting to share in the Matt-light. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 14:29:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id EE40014E53 for ; Fri, 23 Jul 1999 14:29:11 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id RAA17158; Fri, 23 Jul 1999 17:26:41 -0400 (EDT) Message-Id: <199907232126.RAA17158@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Fri, 23 Jul 1999 16:21:04 -0400 To: Adrian Filipi-Martin , Alex Zepeda From: Dennis Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's Cc: hackers@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:35 AM 7/23/99 -0400, Adrian Filipi-Martin wrote: >On Thu, 22 Jul 1999, Alex Zepeda wrote: > >> On Thu, 22 Jul 1999, Adrian Filipi-Martin wrote: >> >> > I know a lot of people like the ASUS P2B boards, but I've noticed a >> > tendency for the systems to reset occasionally when plugging in a keyboard. >> > I've seen this with both FreeBSD and NT, so I'm considering it a property >> > of the board. >> >> If this is a PS/2 style keyboard, don't plug and unplug them when the host >> is powered up. The PS/2 style stuf seems to be very sensitive to that >> sort of thing. If it was a USB keyboard doing that... then that would be >> odd. > > Yes, it is a PS/2 keyboard, but these are the only MB's that I have >run into this problem with other than some AIX boxes years ago that would >blow a fuse when disconnecting the keyboard from a running system. > > This isn't that big a problem. I only have keyboard installed >while building the systems. Thereafter they are serial console only. I've seen it on an SBC (with a KB connector on board). it IS a problem if they want to do maintanence without bringing down the system. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 14:41:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from vip.consys.com (VIP.ConSys.COM [209.141.107.6]) by hub.freebsd.org (Postfix) with ESMTP id BEB9B15051 for ; Fri, 23 Jul 1999 14:40:52 -0700 (PDT) (envelope-from rcarter@pinyon.org) Received: (from pinyon@localhost) by vip.consys.com (8.9.3/8.9.1) id OAA01710; Fri, 23 Jul 1999 14:38:08 -0700 (MST) Date: Fri, 23 Jul 1999 14:38:08 -0700 (MST) From: "Russell L. Carter" Message-Id: <199907232138.OAA01710@vip.consys.com> To: adrian@ubergeeks.com, dennis@etinc.com, garbanzo@hooked.net Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's Cc: hackers@FreeBSD.ORG In-Reply-To: <199907232126.RAA17158@etinc.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG |At 10:35 AM 7/23/99 -0400, Adrian Filipi-Martin wrote: |>On Thu, 22 Jul 1999, Alex Zepeda wrote: |> |>> On Thu, 22 Jul 1999, Adrian Filipi-Martin wrote: |>> |>> > I know a lot of people like the ASUS P2B boards, but I've noticed a |>> > tendency for the systems to reset occasionally when plugging in a |keyboard. |>> > I've seen this with both FreeBSD and NT, so I'm considering it a property |>> > of the board. |>> |>> If this is a PS/2 style keyboard, don't plug and unplug them when the host |>> is powered up. The PS/2 style stuf seems to be very sensitive to that |>> sort of thing. If it was a USB keyboard doing that... then that would be |>> odd. |> |> Yes, it is a PS/2 keyboard, but these are the only MB's that I have |>run into this problem with other than some AIX boxes years ago that would |>blow a fuse when disconnecting the keyboard from a running system. |> |> This isn't that big a problem. I only have keyboard installed |>while building the systems. Thereafter they are serial console only. | |I've seen it on an SBC (with a KB connector on board). it IS a problem if |they want to do maintanence without bringing down the system. I fried two P6 ASUS motherboards this way, sorta along these lines, "hmm, keyboard seems to be dead, maybe try it in this machine" Russell | |Dennis | | |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 Jul 23 14:53: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from redbox.venux.net (redbox.venux.net [216.47.238.10]) by hub.freebsd.org (Postfix) with ESMTP id CB9311508D for ; Fri, 23 Jul 1999 14:53:05 -0700 (PDT) (envelope-from matthew@venux.net) Received: from thunder (net177138.hcv.com [209.153.177.138]) by redbox.venux.net (Postfix) with SMTP for id BF40E2E20B; Fri, 23 Jul 1999 17:52:41 -0400 (EDT) Message-Id: <4.1.19990723173616.009fb3e0@mail.venux.net> X-Sender: mhagerty@mail.venux.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 23 Jul 1999 17:51:25 -0400 To: freebsd-hackers@freebsd.org From: Matthew Hagerty Subject: Missing ld.so in 3.2? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I have a 3.2 install from CD-ROM and I am trying to run a commerical program, i.e. I don't have the source, and it is giving me the following error: [Fri Jul 23 16:47:48 1999] [error] [client 216.47.238.65] malformed header from script. Bad header=Couldn't open /usr/libexec/ld.so This is an error in the applications error log. I looked on my 3.1 box and there is a file /usr/libexec/ld.so but on my 3.2 box the file does not exist. Should it? Does the company of the software have to recompile for 3.2? Any insight would be greatly appreciated. Thank you, Matthew Hagerty To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 14:54:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 16E3615051 for ; Fri, 23 Jul 1999 14:54:08 -0700 (PDT) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id QAA18364; Fri, 23 Jul 1999 16:54:02 -0500 (CDT) Date: Fri, 23 Jul 1999 16:54:02 -0500 From: Tim Tsai To: "Russell L. Carter" Cc: hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's Message-ID: <19990723165402.A18229@futuresouth.com> References: <199907232126.RAA17158@etinc.com> <199907232138.OAA01710@vip.consys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199907232138.OAA01710@vip.consys.com>; from Russell L. Carter on Fri, Jul 23, 1999 at 02:38:08PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I fried two P6 ASUS motherboards this way, sorta along these lines, > "hmm, keyboard seems to be dead, maybe try it in this machine" We did the same thing on two Asus P6 MB as well! We replaced the fuse near the keyboard and both motherboards are working perfectly now. Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 15:10:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id AC09215677 for ; Fri, 23 Jul 1999 15:10:02 -0700 (PDT) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (Postfix) with ESMTP id 8B4F829A; Sat, 24 Jul 1999 02:07:33 +0400 (MSD) Date: Sat, 24 Jul 1999 02:07:33 +0400 (MSD) From: Osokin Sergey To: Matthew Hagerty Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Missing ld.so in 3.2? In-Reply-To: <4.1.19990723173616.009fb3e0@mail.venux.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 Fri, 23 Jul 1999, Matthew Hagerty wrote: > Greetings, > > I have a 3.2 install from CD-ROM and I am trying to run a commerical > program, i.e. I don't have the source, and it is giving me the following error: > > [Fri Jul 23 16:47:48 1999] [error] [client 216.47.238.65] malformed header from > script. Bad header=Couldn't open /usr/libexec/ld.so > > This is an error in the applications error log. I looked on my 3.1 box and > there is a file /usr/libexec/ld.so but on my 3.2 box the file does not > exist. Should it? Does the company of the software have to recompile for > 3.2? Any insight would be greatly appreciated. > > Thank you, > Matthew Hagerty > I think u must read following: http://www.freebsd.org/releases/3.2R/errata.html Rgdz, Osokin Sergey aka oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 16:35: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id CEEE11576C for ; Fri, 23 Jul 1999 16:35:00 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id QAA01283; Fri, 23 Jul 1999 16:30:25 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907232330.QAA01283@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Hagerty Cc: freebsd-hackers@freebsd.org Subject: Re: Missing ld.so in 3.2? In-reply-to: Your message of "Fri, 23 Jul 1999 17:51:25 EDT." <4.1.19990723173616.009fb3e0@mail.venux.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 23 Jul 1999 16:30:25 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Install the compat22 dist; you have an old a.out binary there. > Greetings, > > I have a 3.2 install from CD-ROM and I am trying to run a commerical > program, i.e. I don't have the source, and it is giving me the following error: > > [Fri Jul 23 16:47:48 1999] [error] [client 216.47.238.65] malformed header from > script. Bad header=Couldn't open /usr/libexec/ld.so > > This is an error in the applications error log. I looked on my 3.1 box and > there is a file /usr/libexec/ld.so but on my 3.2 box the file does not > exist. Should it? Does the company of the software have to recompile for > 3.2? Any insight would be greatly appreciated. > > Thank you, > Matthew Hagerty > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 16:41:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id ECF8C14F11 for ; Fri, 23 Jul 1999 16:41:44 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA28389; Fri, 23 Jul 1999 16:40:00 -0700 (PDT) (envelope-from dillon) Date: Fri, 23 Jul 1999 16:40:00 -0700 (PDT) From: Matthew Dillon Message-Id: <199907232340.QAA28389@apollo.backplane.com> To: Mike Smith Cc: Matthew Hagerty , freebsd-hackers@FreeBSD.ORG Subject: Re: Missing ld.so in 3.2? References: <199907232330.QAA01283@dingo.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Install the compat22 dist; you have an old a.out binary there. : :> Greetings, :> :> I have a 3.2 install from CD-ROM and I am trying to run a commerical :> program, i.e. I don't have the source, and it is giving me the following error: :> :> [Fri Jul 23 16:47:48 1999] [error] [client 216.47.238.65] malformed header from :> script. Bad header=Couldn't open /usr/libexec/ld.so :... Btw, the netscape4.5.us port needs this too, along with half a dozen libraries in /usr/lib/aout/. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 16:49:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id D8C2014F11 for ; Fri, 23 Jul 1999 16:49:37 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA28517; Fri, 23 Jul 1999 16:49:37 -0700 (PDT) (envelope-from dillon) Date: Fri, 23 Jul 1999 16:49:37 -0700 (PDT) From: Matthew Dillon Message-Id: <199907232349.QAA28517@apollo.backplane.com> To: Subject: New patch fpr uipc_socket.c - any objections? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Object now or forever hold your peace! Patch included again for reference. -Matt Matthew Dillon Index: uipc_socket.c =================================================================== RCS file: /home/ncvs/src/sys/kern/uipc_socket.c,v retrieving revision 1.60 diff -u -r1.60 uipc_socket.c --- uipc_socket.c 1999/06/17 23:54:47 1.60 +++ uipc_socket.c 1999/07/22 23:08:38 @@ -413,7 +413,8 @@ register struct mbuf *m; register long space, len, resid; int clen = 0, error, s, dontroute, mlen; - int atomic = sosendallatonce(so) || top; + int atomic = sosendallatonce(so) || top; /* required atomicy */ + int try_atomic = atomic; /* requested atomicy */ if (uio) resid = uio->uio_resid; @@ -518,6 +519,7 @@ mlen = MCLBYTES; len = min(min(mlen, resid), space); } else { + try_atomic = 1; /* try to optimize */ nopages: len = min(min(mlen, resid), space); /* @@ -541,7 +543,7 @@ top->m_flags |= M_EOR; break; } - } while (space > 0 && atomic); + } while (space > 0 && try_atomic); if (dontroute) so->so_options |= SO_DONTROUTE; s = splnet(); /* XXX */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 17:17:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 65E851576B for ; Fri, 23 Jul 1999 17:17:27 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA30153; Fri, 23 Jul 1999 17:14:55 -0700 (PDT) (envelope-from dillon) Date: Fri, 23 Jul 1999 17:14:55 -0700 (PDT) From: Matthew Dillon Message-Id: <199907240014.RAA30153@apollo.backplane.com> To: "David E. Cross" Cc: David Malone , Doug , "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: mbuf leakage in NFSv3 writes, possbile? References: <199907231747.NAA94297@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd say that there is a definite leak somewhere. The question is where. I'll run some buildworld tests w/ the latest current to see if I can cause mbufs to leak. I suspect that the problem may be related to a specific situation, though, such as a particular type of FS op failure. Unfortunately, I do not have any -stable machines setup at the moment that I can use for NFS testing. You could try backing out the nfs_serv.c and related patches from your -stable source to see if that fixes this particular problem. If it does then we will know where to look. -Matt Matthew Dillon :Ok, here are some real stats.... : :"w" is the read-only machine, it services everything that "s" (the :read-write machine) does... in fact it services more. : :*w crossd $ strings -a /kernel | grep \^___maxusers :___maxusers 96 :*w crossd $ uname -a :FreeBSD w.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #1: Tue Jun 29 09:36:32 EDT 1999 root@w.cs.rpi.edu:/usr/src/sys/compile/WOBBLE i386 :*w crossd $ uptime : 1:43PM up 24 days, 2:08, 3 users, load averages: 0.00, 0.00, 0.00 :*w crossd $ netstat -m :106/2688 mbufs in use: : 85 mbufs allocated to data : 21 mbufs allocated to packet headers :64/426/2048 mbuf clusters in use (current/peak/max) :1188 Kbytes allocated to network (11% in use) :0 requests for memory denied :0 requests for memory delayed :0 calls to protocol drain routines : :*s crossd $ uname -a :FreeBSD s.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #0: Thu Jul 22 18:12:21 EDT 1999 root@phoenix.cs.rpi.edu:/usr/src/sys/compile/STAGGER i386 :*s crossd $ strings -a /kernel | grep \^___maxusers :___maxusers 512 :*s crossd $ uptime : 1:43PM up 19:23, 2 users, load averages: 0.02, 0.01, 0.00 :*s crossd $ netstat -m :3629/4096 mbufs in use: : 3621 mbufs allocated to data : 8 mbufs allocated to packet headers :3550/3660/8704 mbuf clusters in use (current/peak/max) :7832 Kbytes allocated to network (96% in use) :0 requests for memory denied :0 requests for memory delayed :0 calls to protocol drain routines : :-- :David Cross | email: crossd@cs.rpi.edu :Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd :Rensselaer Polytechnic Institute, | Ph: 518.276.2860 :Department of Computer Science | Fax: 518.276.4033 :I speak only for myself. | WinNT:Linux::Linux:FreeBSD : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 17:33: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 4F40C14F89 for ; Fri, 23 Jul 1999 17:32:56 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id UAA02766; Fri, 23 Jul 1999 20:32:07 -0400 (EDT) Message-Id: <199907240032.UAA02766@cs.rpi.edu> To: Matthew Dillon Cc: "David E. Cross" , David Malone , Doug , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: mbuf leakage in NFSv3 writes, possbile? In-Reply-To: Message from Matthew Dillon of "Fri, 23 Jul 1999 17:14:55 PDT." <199907240014.RAA30153@apollo.backplane.com> Date: Fri, 23 Jul 1999 20:32:07 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, backing out now is not really an option... But given my past history with NFS, and knowledge of this site I think I have a fair idea where the leak is... I think it is in the nfsv3 "commit" handler. Why do I think this? Simple, this problem started when a user started running a large job on out origin 2k, prior to that our server had been up for 30-ish days sans any problems, since his start it requires a boot-a-day (mbuf clusters are up to 8k). Also supporting this is the fact that the clusters are used at a fairly constant rate. Now (following that hunch), I did a tcpdump against that host for tcp traffic, and noticed a fairly steady stream of "commit" NFS traffic. I realize none of this is a smoking gun, but that is where my "hunch" lies. How is mbuf cluster cleanyup done? If I knew I might have a shot in heck at locating this problem. BTW: updated netstat -m for the machine: 4855/5344 mbufs in use: 4848 mbufs allocated to data 7 mbufs allocated to packet headers 4774/4850/8704 mbuf clusters in use (current/peak/max) 10368 Kbytes allocated to network (97% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines That's alot of buffer ;) -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 18:43:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id DC0C015760; Fri, 23 Jul 1999 18:43:24 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from lithium.scientia.demon.co.uk ([192.168.1.2] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.02 #1) id 117hjB-0003vb-00; Fri, 23 Jul 1999 16:59:17 +0100 (envelope-from ben@lithium.scientia.demon.co.uk) Received: from lithium.scientia.demon.co.uk (ident=ben) by lithium.scientia.demon.co.uk with local (Exim 3.02 #1) id 117hjB-0000lA-00; Fri, 23 Jul 1999 16:59:17 +0100 (envelope-from ben@lithium.scientia.demon.co.uk) Date: Fri, 23 Jul 1999 16:59:17 +0100 From: Ben Smithurst To: sthaug@nethelp.no Cc: freebsd-hackers@freebsd.org, freebsd-smp@freebsd.org Subject: Re: rndcontrol and SMP Message-ID: <19990723165917.A2862@lithium.scientia.demon.co.uk> References: <57419.932675097@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <57419.932675097@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sthaug@nethelp.no wrote: > ! warn(""); That should (probably) be `warn(NULL);', otherwise you'd get something like `rndcontrol: : error' rather than the (probably) desired `rndcontrol: error'. (Or so my simple test showed, at least...) -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 21: 6:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 9086814D41 for ; Fri, 23 Jul 1999 21:06:14 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id AAA04539 for ; Sat, 24 Jul 1999 00:05:20 -0400 (EDT) Message-Id: <199907240405.AAA04539@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: mbuf leakage Date: Sat, 24 Jul 1999 00:05:18 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, it doesn't appear to be commit() :(. Any-who, is there a way I can get a look at the raw mbuf/mbuf-clusters? I have a feeling that seeing the data in them would speak volumes of information. Preferably a way to see them without DDB/panic would be ideal. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 21:43:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id BF4F614FA6; Fri, 23 Jul 1999 21:43:50 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA14734; Sat, 24 Jul 1999 14:43:09 +1000 Date: Sat, 24 Jul 1999 14:43:09 +1000 From: Bruce Evans Message-Id: <199907240443.OAA14734@godzilla.zeta.org.au> To: freebsd-hackers@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG, sthaug@nethelp.no Subject: Re: rndcontrol and SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > /* > * XXX the data is 16-bit due to a historical botch, so we use > * magic 16's instead of ICU_LEN and can't support 24 interrupts > * under SMP. > */ > intr = *(int16_t *)data; > if (cmd != MEM_RETURNIRQ && (intr < 0 || intr >= 16)) > return (EINVAL); > >What is needed to make this support a more sensible number of IRQs? Mainly changing the ioctl and its clients (rndcontrol only?) to supply more bits. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 22:12:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 2859114FA6 for ; Fri, 23 Jul 1999 22:12:30 -0700 (PDT) (envelope-from jkoshy@FreeBSD.org) Received: (from jkoshy@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id WAA19120; Fri, 23 Jul 1999 22:12:29 -0700 (PDT) (envelope-from jkoshy@FreeBSD.org) Date: Fri, 23 Jul 1999 22:12:29 -0700 (PDT) From: Message-Id: <199907240512.WAA19120@freefall.freebsd.org> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@freebsd.org Cc: Subject: deny ktrace without read permissions? Mime-Version: 1.0 Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG PR bin/3546 asks that `ktrace(1)' not be allowed on files that do not have read permissions for the user attempting to execute them. The intent of this change is to prevent a user from seeing how an executable with '--x--x--x' perms works by ktrace'ing its execution. My question to the -hackers is: is this a useful semantic? Would it break anything if added? A patch to "/sys/kern/kern_exec.c" that adds this functionality is attached for those who would like to play with the change. Regards, Koshy Index: /sys/kern/kern_exec.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_exec.c,v retrieving revision 1.99 diff -u -r1.99 kern_exec.c --- kern_exec.c 1999/04/27 11:15:55 1.99 +++ kern_exec.c 1999/07/24 10:35:09 @@ -26,6 +26,8 @@ * $Id: kern_exec.c,v 1.99 1999/04/27 11:15:55 phk Exp $ */ +#include "opt_ktrace.h" + #include #include #include @@ -48,6 +50,9 @@ #include #include #include +#ifdef KTRACE +#include +#endif #include #include @@ -650,6 +655,7 @@ struct vnode *vp = imgp->vp; struct vattr *attr = imgp->attr; int error; + int mode; /* Get file attributes */ error = VOP_GETATTR(vp, attr, p->p_ucred, p); @@ -677,9 +683,14 @@ return (ENOEXEC); /* - * Check for execute permission to file based on current credentials. + * Check for execute permission to file based on current credentials. */ - error = VOP_ACCESS(vp, VEXEC, p->p_ucred, p); + mode = VEXEC; +#ifdef KTRACE + if (p->p_traceflag & KTRFAC_MASK) + mode |= VREAD; +#endif + error = VOP_ACCESS(vp, mode, p->p_ucred, p); if (error) return (error); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 22:35: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id DD1A214BCE; Fri, 23 Jul 1999 22:34:58 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA07454; Sat, 24 Jul 1999 15:02:57 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA46533; Sat, 24 Jul 1999 15:02:56 +0930 (CST) Date: Sat, 24 Jul 1999 15:02:55 +0930 From: Greg Lehey To: jkoshy@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: deny ktrace without read permissions? Message-ID: <19990724150255.S84734@freebie.lemis.com> References: <199907240512.WAA19120@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907240512.WAA19120@freefall.freebsd.org>; from jkoshy@FreeBSD.ORG on Fri, Jul 23, 1999 at 10:12:29PM -0700 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 23 July 1999 at 22:12:29 -0700, jkoshy@FreeBSD.ORG wrote: > > > PR bin/3546 asks that `ktrace(1)' not be allowed on files that do not have > read permissions for the user attempting to execute them. > > The intent of this change is to prevent a user from seeing how an > executable with '--x--x--x' perms works by ktrace'ing its execution. > > My question to the -hackers is: is this a useful semantic? Yes, I think so. > Would it break anything if added? Not that I can think of. But that doesn't mean anything. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 23 23:56: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 342AA14E53 for ; Fri, 23 Jul 1999 23:56:01 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id CAA05968 for ; Sat, 24 Jul 1999 02:55:47 -0400 (EDT) Message-Id: <199907240655.CAA05968@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: mbuf leak found... for real this time. Date: Sat, 24 Jul 1999 02:55:45 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found it... our favorite function... nfsrv_create()!!! :) The problem was/is a create of an already existing file (with O_EXCL|O_CREATE, I would bet, but I don't have anyway to tell) returns *nothing* to the sender. The last time I had this problem it was because nfsrv_create() was not clearing error before its return (signalling to the caller that there was a more severe error and the packet should not be responded to. I have looked through the code, and arround line 1759 there should be a "goto nfsmreply0". Clearly we need to set error to 0 before we depart from this function with this kind of condition, I am just not sure the 'correct' way to do it. Any-who, I am not able to reproduce this reliably since the OS (all OS's I have tried, including the troubled machine) issue a getattr() to see if the file exists as a first stage, not even attempting the create call for the first try. This looks like a race condition waiting for us to loose it. As another aside... I really do think that on returning with an error condition, it may be a good idea to free those mbuf/mbuf-clusters. I cannot see a reason to keep them lying arround. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 0: 1:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 6D33C14C16 for ; Sat, 24 Jul 1999 00:01:39 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id CAA05998; Sat, 24 Jul 1999 02:59:58 -0400 (EDT) Message-Id: <199907240659.CAA05998@cs.rpi.edu> To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: mbuf leak found... for real this time. In-Reply-To: Message from "David E. Cross" of "Sat, 24 Jul 1999 02:55:45 EDT." <199907240655.CAA05968@cs.rpi.edu> Date: Sat, 24 Jul 1999 02:59:55 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG PS: I was down to only 3k mbuf-clusters free on the server, so I 'rm'-ed the troublesome file and the create went through and no more mbuf-leaking. On the downside, I cannot reproduce this problem any longer with any reliability. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 1:56:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id CCBE514F4A; Sat, 24 Jul 1999 01:56:39 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.212]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAB28EF; Sat, 24 Jul 1999 10:54:41 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id KAA20448; Sat, 24 Jul 1999 10:51:27 +0200 (CEST) (envelope-from asmodai) Date: Sat, 24 Jul 1999 10:51:27 +0200 From: Jeroen Ruigrok/Asmodai To: David Malone Cc: Dag-Erling Smorgrav , Andre Albsmeier , Sheldon Hearn , Brian Feldman , hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.h Message-ID: <19990724105127.D20171@daemon.ninth-circle.org> References: <41604.932732959@axl.noc.iafrica.com> <19990723153416.F10047@internal> <19990723155348.J10047@internal> <19990723163720.A15697@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <19990723163720.A15697@walton.maths.tcd.ie>; from David Malone on Fri, Jul 23, 1999 at 04:37:20PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * David Malone (dwmalone@maths.tcd.ie) [990723 18:41]: > if ((bi->bi_socktype == sep->se_socktype && > strcmp(bi->bi_service, sep->se_service) == 0) || > matchservent(bi->bi_service, sep->se_service, > sep->se_proto)) > > It should probably say: > > if (bi->bi_socktype == sep->se_socktype && > ((strcmp(bi->bi_service, sep->se_service) == 0) || > matchservent(bi->bi_service, sep->se_service, > sep->se_proto))) Holymoley, detect the braces-quiz. Those braces which changed are hard to spot, but prolly mean the world in this case.... -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 6: 5:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 6216814D4B for ; Sat, 24 Jul 1999 06:05:28 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 1181W9-000EoD-00 for hackers@freebsd.org; Sat, 24 Jul 1999 15:07:09 +0200 From: Sheldon Hearn To: hackers@freebsd.org Subject: Mentioning RFC numbers in /etc/services Date: Sat, 24 Jul 1999 15:07:09 +0200 Message-ID: <56928.932821629@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I plan to mention in the comments for each service in /etc/services, the latest RFC describing the service. I also plan to mention in the manpage for services(5) the e-mail address to which requests for "How do I get the RFCs" should be sent. If anyone is worried that I'll get RFC numbers wrong, I'm happy to pass my diffs by him. I intend to do this next week-end, so let me know before then if you'd like to see what I'll be doing beforehand. Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 6:15:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 2EF3A14F75 for ; Sat, 24 Jul 1999 06:15:28 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id PAA16516 for freebsd-hackers@FreeBSD.ORG; Sat, 24 Jul 1999 15:12:46 +0200 (CEST) (envelope-from olli) Date: Sat, 24 Jul 1999 15:12:46 +0200 (CEST) From: Oliver Fromme Message-Id: <199907241312.PAA16516@dorifer.heim3.tu-clausthal.de> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Filesystem question... Organization: Administration Heim 3 Reply-To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ronald G. Minnich wrote in list.freebsd-hackers: > On Fri, 23 Jul 1999, Kris Kennaway wrote: > > On Thu, 22 Jul 1999, Ronald G. Minnich wrote: > > > Are you saying that as an ordinary user I can mount something on top of > > > /tmp, for example? > > If the vfs.usermount sysctl is 1, and you have appropriate access to the > > thing you're trying to mount (block device, etc). > > OK, so let's say it is 1. Let's say I have "appropriate access" to /tmp. I > mount my own fs on /tmp. I now have read/write access to everything anyone > writes to /tmp. Not possible. You have to _own_ the mount point (which is usually not the case for /tmp). > Or, let's say I don't have "appropriate access" to /tmp. Pick some other > place. I mount my file system there for my files. Now everyone who wants > can look for these user mounts and walk them at will. My private stuff is > quite public. You own it, so you can set the permission appropriately, so nobody else can access it if you don't want that. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 6:26:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id 0742B14F75 for ; Sat, 24 Jul 1999 06:26:20 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip231.houston3.tx.pub-ip.psi.net [38.12.169.231]) by leap.innerx.net (Postfix) with ESMTP id 8961637091; Sat, 24 Jul 1999 09:24:49 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id IAA40429; Sat, 24 Jul 1999 08:25:56 -0500 (CDT) (envelope-from chris) Date: Sat, 24 Jul 1999 08:25:55 -0500 From: Chris Costello To: Sheldon Hearn Cc: hackers@FreeBSD.ORG Subject: Re: Mentioning RFC numbers in /etc/services Message-ID: <19990724082555.A40344@holly.dyndns.org> Reply-To: chris@calldei.com References: <56928.932821629@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <56928.932821629@axl.noc.iafrica.com>; from Sheldon Hearn on Sat, Jul 24, 1999 at 03:07:09PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 24, 1999, Sheldon Hearn wrote: > > Hi folks, > > I plan to mention in the comments for each service in /etc/services, the > latest RFC describing the service. I also plan to mention in the manpage > for services(5) the e-mail address to which requests for "How do I get > the RFCs" should be sent. > > If anyone is worried that I'll get RFC numbers wrong, I'm happy to pass > my diffs by him. I intend to do this next week-end, so let me know > before then if you'd like to see what I'll be doing beforehand. Are you going to be listing all the RFCs that apply? For example, DNS is 1033, 1034, and 1035, and NNTP is 0850 and 0977. -- |Chris Costello |Never trust a computer you can't lift. - Stan Masor `---------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 6:47:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id F2CFB14D40; Sat, 24 Jul 1999 06:47:21 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id PAA58793; Sat, 24 Jul 1999 15:46:26 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199907241346.PAA58793@gratis.grondar.za> To: Bruce Evans Cc: freebsd-hackers@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG, sthaug@nethelp.no Subject: Re: rndcontrol and SMP Date: Sat, 24 Jul 1999 15:46:25 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >What is needed to make this support a more sensible number of IRQs? > > Mainly changing the ioctl and its clients (rndcontrol only?) to supply > more bits. I am currently rewriting /dev/random (and rndcontrol). 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 Sat Jul 24 7:11:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 715BD14D53 for ; Sat, 24 Jul 1999 07:11:28 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id QAA58993; Sat, 24 Jul 1999 16:09:28 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199907241409.QAA58993@gratis.grondar.za> To: Matthew Dillon Cc: Amancio Hasty , hackers@FreeBSD.ORG Subject: Re: Base Kerberos 5 support? Date: Sat, 24 Jul 1999 16:09:27 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I would love to see krb 5 made part of the standard distribution. BEST > has been using it for several years now with no problems and I believe > that it is a whole lot easier to administrate then krb 4. I have Heimdal commit-ready (this has been the case for a year). I am waiting for it to be more compatible with MITK5. 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 Sat Jul 24 7:19:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id E5A2414D4B for ; Sat, 24 Jul 1999 07:19:42 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id QAA59106; Sat, 24 Jul 1999 16:17:51 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199907241417.QAA59106@gratis.grondar.za> To: Keith Stevenson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD Date: Sat, 24 Jul 1999 16:17:50 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth "Keith Stevenson": > (Mark Murray: jump in here if I get this wrong) > > The way I understand it, a PAM module (pam_unix?) would need to be able to > look at the password hash and figure out which of the crypt functions to > call. Ideally, the PAM configuration would be able to specify which crypt > functions are valid for the system. I'm sure this could be done. I'm not sure that it is PAM's job. I'll look at it. > That said, one of the very attractive features of specifying the crypt > function in the login class is the ability to assign different crypt > algorithms on a user by user basis. ...or group... 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 Sat Jul 24 7:58:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id EAE3E150C4 for ; Sat, 24 Jul 1999 07:58:27 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA25192; Sat, 24 Jul 1999 23:57:32 +0900 (JST) Message-ID: <37981F93.54C40B75@newsguy.com> Date: Fri, 23 Jul 1999 16:53:55 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Adrian Filipi-Martin Cc: Vincent Poy , hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Adrian Filipi-Martin wrote: > > > Cool... Is 1GB of ram really needed? We used to run a 64 meg > > system then 128 meg and then 384 meg, it doesn't seem to do much even for > > a heavily loaded ISP Server. > > Not really. The customer whose box this is chose this much memory > because his previous server was a 256MB UltraSparc that was swamped all the > time with a load of 6 to 7. Alas, since Solaris doesn't overcommit... :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Your usefulness to my realm ended the day you made it off Hustaing alive." -- Sun Tzu Liao to his ex-finacee, Isis Marik To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 8:28:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rebel.net.au (rebel.rebel.net.au [203.20.69.66]) by hub.freebsd.org (Postfix) with ESMTP id D0DC214DD7 for ; Sat, 24 Jul 1999 08:28:17 -0700 (PDT) (envelope-from kkenn@rebel.net.au) Received: from 203.20.69.78 (dialup-8.rebel.net.au [203.20.69.78]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id AAA25764 for ; Sun, 25 Jul 1999 00:57:02 +0930 Received: (qmail 49866 invoked from network); 24 Jul 1999 15:26:29 -0000 Received: from localhost (kkenn@127.0.0.1) by localhost with SMTP; 24 Jul 1999 15:26:29 -0000 Date: Sun, 25 Jul 1999 00:56:28 +0930 (CST) From: Kris Kennaway Reply-To: kkenn@rebel.net.au To: Mark Murray Cc: Bruce Evans , freebsd-hackers@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG, sthaug@nethelp.no Subject: Re: rndcontrol and SMP In-Reply-To: <199907241346.PAA58793@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Jul 1999, Mark Murray wrote: > > >What is needed to make this support a more sensible number of IRQs? > > > > Mainly changing the ioctl and its clients (rndcontrol only?) to supply > > more bits. > > I am currently rewriting /dev/random (and rndcontrol). When you say rewriting, do you mean syncing with the version of the code in Linux (1.04, instead of our 0.95) or actually rewriting? If the latter, I'm curious as to what your aims are. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 9: 9:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id B139B150DB; Sat, 24 Jul 1999 09:09:30 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id SAA59761; Sat, 24 Jul 1999 18:07:36 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199907241607.SAA59761@gratis.grondar.za> To: kkenn@rebel.net.au Cc: Bruce Evans , freebsd-hackers@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG, sthaug@nethelp.no Subject: Re: rndcontrol and SMP Date: Sat, 24 Jul 1999 18:07:36 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When you say rewriting, do you mean syncing with the version of the code > in Linux (1.04, instead of our 0.95) or actually rewriting? If the latter, > I'm curious as to what your aims are. I want to implement Bruce Schneier's Yarrow. 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 Sat Jul 24 9:13:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rebel.net.au (rebel.rebel.net.au [203.20.69.66]) by hub.freebsd.org (Postfix) with ESMTP id 7AE4C150E6 for ; Sat, 24 Jul 1999 09:13:12 -0700 (PDT) (envelope-from kkenn@rebel.net.au) Received: from 203.20.69.78 (dialup-8.rebel.net.au [203.20.69.78]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id BAA26319 for ; Sun, 25 Jul 1999 01:42:55 +0930 Received: (qmail 68327 invoked from network); 24 Jul 1999 16:12:22 -0000 Received: from localhost (kkenn@127.0.0.1) by localhost with SMTP; 24 Jul 1999 16:12:22 -0000 Date: Sun, 25 Jul 1999 01:42:22 +0930 (CST) From: Kris Kennaway Reply-To: kkenn@rebel.net.au To: Mark Murray Cc: Bruce Evans , freebsd-hackers@FreeBSD.ORG, sthaug@nethelp.no Subject: Re: rndcontrol and SMP In-Reply-To: <199907241607.SAA59761@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Jul 1999, Mark Murray wrote: > > When you say rewriting, do you mean syncing with the version of the code > > in Linux (1.04, instead of our 0.95) or actually rewriting? If the latter, > > I'm curious as to what your aims are. > > I want to implement Bruce Schneier's Yarrow. Ah - I had this idea as well, but hadn't looked into it further. Updating the /dev/random code to 1.04 is probably compatible with this goal to a large extent. Kris > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org > ------------------------------------------------------------------------------ The Feynman Problem-Solving Algorithm: (1) Write down the problem (2) Think real hard (3) Write down the answer ------------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 9:40:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id ADDC014D59 for ; Sat, 24 Jul 1999 09:40:35 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA35403; Sat, 24 Jul 1999 09:38:47 -0700 (PDT) (envelope-from dillon) Date: Sat, 24 Jul 1999 09:38:47 -0700 (PDT) From: Matthew Dillon Message-Id: <199907241638.JAA35403@apollo.backplane.com> To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf leak found... for real this time. References: <199907240655.CAA05968@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I found it... our favorite function... nfsrv_create()!!! :) Yeee Haw! :The problem was/is a create of an already existing file (with O_EXCL|O_CREATE, :I would bet, but I don't have anyway to tell) returns *nothing* to the sender. :The last time I had this problem it was because nfsrv_create() was not clearing :error before its return (signalling to the caller that there was a more :severe error and the packet should not be responded to. I have looked :through the code, and arround line 1759 there should be a :"goto nfsmreply0". Clearly we need to set error to 0 before we depart from :this function with this kind of condition, I am just not sure the :'correct' way to do it. Hmmm. Interesting. An EEXIST error occuring at that point for an NFSV3 mount will execute the correct nfsm_reply(), but since it is NFSV3 the nfsm_reply() macro will not jump to a return(0) ... when it finishes constructing the reply it falls through instead. In this case I believe the nfsm_reply() call on line 1761 is correct, but that we are failing to clear the error afterwords and this is resulting in a non-zero return(). Thus the reply packet is being properly formatted but not being transmitted. I think all we need to do is set error = 0 for the NFSV3 case after the nfsm_srvwcc_data() call. See the enclosed patch. We definitely do not want to call nfsm_reply(0), because we already correctly call nfsm_reply() on line 1761 (in STABLE). I really appreciate the effort you've put into tracking down these problems, Dave! You are virtually the only one who has enough of a mix of NFS clients to truely test the server-side code. The only testing I can do is between FreeBSD boxes! In anycase, please try the enclosed patch. The patch, if correct, should be applied to all branches. And if there is anyone else up on NFS I would appreciate a review of the patch! Remember that nfsm_reply() deals with errors differently between NFSv2 and NFSv3. -Matt Matthew Dillon :Any-who, I am not able to reproduce this reliably since the OS (all OS's I :have tried, including the troubled machine) issue a getattr() to see if the :file exists as a first stage, not even attempting the create call for the :first try. This looks like a race condition waiting for us to loose it. : :As another aside... I really do think that on returning with an error :condition, it may be a good idea to free those mbuf/mbuf-clusters. I cannot :see a reason to keep them lying arround. : :-- :David Cross | email: crossd@cs.rpi.edu Index: nfs_serv.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_serv.c,v retrieving revision 1.72.2.2 diff -u -r1.72.2.2 nfs_serv.c --- nfs_serv.c 1999/06/30 22:05:14 1.72.2.2 +++ nfs_serv.c 1999/07/24 16:31:48 @@ -1765,6 +1765,7 @@ nfsm_srvpostop_attr(0, vap); } nfsm_srvwcc_data(dirfor_ret, &dirfor, diraft_ret, &diraft); + error = 0; } else { nfsm_srvfhtom(fhp, v3); nfsm_build(fp, struct nfs_fattr *, NFSX_V2FATTR); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 10:13:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 516991513D for ; Sat, 24 Jul 1999 10:13:43 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id NAA75111; Sat, 24 Jul 1999 13:13:33 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Sat, 24 Jul 1999 13:13:33 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Sheldon Hearn Cc: hackers@FreeBSD.org Subject: Re: Mentioning RFC numbers in /etc/services In-Reply-To: <56928.932821629@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Jul 1999, Sheldon Hearn wrote: > > Hi folks, > > I plan to mention in the comments for each service in /etc/services, the > latest RFC describing the service. I also plan to mention in the manpage > for services(5) the e-mail address to which requests for "How do I get > the RFCs" should be sent. > > If anyone is worried that I'll get RFC numbers wrong, I'm happy to pass > my diffs by him. I intend to do this next week-end, so let me know > before then if you'd like to see what I'll be doing beforehand. I'd check, if I were you, if any of the other BSDs have done this already, to greatly simplify the task. > > Thanks, > Sheldon. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ 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 Sat Jul 24 10:23:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from snafu.adept.org (adsl-63-193-112-19.dsl.snfc21.pacbell.net [63.193.112.19]) by hub.freebsd.org (Postfix) with ESMTP id 6096815163 for ; Sat, 24 Jul 1999 10:23:55 -0700 (PDT) (envelope-from mike@snafu.adept.org) Received: from localhost (mike@localhost) by snafu.adept.org (8.9.3/8.9.3) with ESMTP id KAA02778; Sat, 24 Jul 1999 10:20:52 -0700 (PDT) Date: Sat, 24 Jul 1999 10:20:52 -0700 (PDT) From: Mike Hoskins To: "Daniel C. Sobral" Cc: Adrian Filipi-Martin , Vincent Poy , hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's In-Reply-To: <37981F93.54C40B75@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Jul 1999, Daniel C. Sobral wrote: > > Not really. The customer whose box this is chose this much memory > > because his previous server was a 256MB UltraSparc that was swamped all the > > time with a load of 6 to 7. > Alas, since Solaris doesn't overcommit... :-) This isn't a comment meant to contribute to the overcommit holy war (opinion mode: I think FreeBSD should overcommit, or at worst have a sysctl and default to overcommit - admins who don't want overcommit can then hang themselves), but we have to be a wee bit careful when throwing load averages around... I've seen FreeBSD boxes virtually unuseable with 3-4 loads, and Solaris boxes still chugging away at 5+... Perhaps 'load average' is being calculated a wee bit differently. -- Mike Hoskins To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 10:24:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 8B050151EF; Sat, 24 Jul 1999 10:24:40 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA27908; Sat, 24 Jul 1999 11:24:40 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA13835; Sat, 24 Jul 1999 11:24:39 -0600 Date: Sat, 24 Jul 1999 11:24:39 -0600 Message-Id: <199907241724.LAA13835@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: jkoshy@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: deny ktrace without read permissions? In-Reply-To: <199907240512.WAA19120@freefall.freebsd.org> References: <199907240512.WAA19120@freefall.freebsd.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > PR bin/3546 asks that `ktrace(1)' not be allowed on files that do not have > read permissions for the user attempting to execute them. > > The intent of this change is to prevent a user from seeing how an > executable with '--x--x--x' perms works by ktrace'ing its execution. > > My question to the -hackers is: is this a useful semantic? Would it break > anything if added? If we make kernel auditing based upon KTRACE (which may or may not happen), this is not a useful change since we need to be able to 'audit' system calls regardless of whether or not KTRACE is used. If this kind of addition is done, then it'll have to be removed since system auditing must occur and be essentially 'independant' of what options are used. If adding auditing has a negative effect on the successful completion of a system call, then it's not going to be used. (There are certain things that can't be avoided, such as additional CPU/memory use, but it should not effect whether or not the syscall is completed.) Also, I believe that KTRACE should be allowed since security through obscurity isn't a good reason to avoid letting the user see the syscall. If security is an issue, KTRACE shouldn't be in the system kernel. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 10:30:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 72C46151BA for ; Sat, 24 Jul 1999 10:30:20 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id CAA13363; Sun, 25 Jul 1999 02:29:46 +0900 (JST) Message-ID: <3799F7F6.CD75490F@newsguy.com> Date: Sun, 25 Jul 1999 02:29:26 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Mike Hoskins Cc: Adrian Filipi-Martin , Vincent Poy , hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Hoskins wrote: > > This isn't a comment meant to contribute to the overcommit holy war > (opinion mode: I think FreeBSD should overcommit, or at worst have a > sysctl and default to overcommit - admins who don't want overcommit can > then hang themselves), but we have to be a wee bit careful when throwing > load averages around... > > I've seen FreeBSD boxes virtually unuseable with 3-4 loads, and Solaris > boxes still chugging away at 5+... Perhaps 'load average' is being > calculated a wee bit differently. I think that would rather be a function of the memory footprint of the workload. The message said memory was increased because Solaris was overloaded with _swapping_. The load itself isn't really of much importance in this case. Since Solaris does not overcommit, it needs (much) more memory than FreeBSD would. Thus, changing to FreeBSD and upgrading the memory at the same time is sure likely to give the impressive results described. Solaris is not a bad operating system. It's just misguided. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Your usefulness to my realm ended the day you made it off Hustaing alive." -- Sun Tzu Liao to his ex-finacee, Isis Marik To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 12:10:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 8120315216 for ; Sat, 24 Jul 1999 12:10:41 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id MAA74055; Sat, 24 Jul 1999 12:10:18 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Sat, 24 Jul 1999 12:10:18 -0700 (PDT) From: Vincent Poy To: Mike Hoskins Cc: "Daniel C. Sobral" , Adrian Filipi-Martin , hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Jul 1999, Mike Hoskins wrote: > On Fri, 23 Jul 1999, Daniel C. Sobral wrote: > > > > Not really. The customer whose box this is chose this much memory > > > because his previous server was a 256MB UltraSparc that was swamped all the > > > time with a load of 6 to 7. > > Alas, since Solaris doesn't overcommit... :-) > > This isn't a comment meant to contribute to the overcommit holy war > (opinion mode: I think FreeBSD should overcommit, or at worst have a > sysctl and default to overcommit - admins who don't want overcommit can > then hang themselves), but we have to be a wee bit careful when throwing > load averages around... > > I've seen FreeBSD boxes virtually unuseable with 3-4 loads, and Solaris > boxes still chugging away at 5+... Perhaps 'load average' is being > calculated a wee bit differently. Speaking about loads, I have a question that I can't figure out... On one of our systems which is a Pentium II 400 with the ABIT BH6 with 384 megs of RAM. Just for reference, the previous was a AMD K6-233 on a ASUS P55T2P4 with 64 Megs of RAM. It seems like whether there is a heavy load or light load, at times, when typing just w in the shell or any command or even in pine, the FreeBSD OS would just hang for like 30 seconds or so... It isn't a network issue either because I can jump around in my screen windows but just commands don't work like in real time. There is this long delay. Anyone have any ideas what can be causing this? Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 12:37:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 24B1B14BDD for ; Sat, 24 Jul 1999 12:37:35 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id PAA13884; Sat, 24 Jul 1999 15:35:50 -0400 (EDT) Message-Id: <199907241935.PAA13884@cs.rpi.edu> To: Matthew Dillon Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: mbuf leak found... for real this time. In-Reply-To: Message from Matthew Dillon of "Sat, 24 Jul 1999 09:38:47 PDT." <199907241638.JAA35403@apollo.backplane.com> Date: Sat, 24 Jul 1999 15:35:50 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmmm. Interesting. An EEXIST error occuring at that point for an > NFSV3 mount will execute the correct nfsm_reply(), but since it is > NFSV3 the nfsm_reply() macro will not jump to a return(0) ... when > it finishes constructing the reply it falls through instead. > > In this case I believe the nfsm_reply() call on line 1761 is correct, > but that we are failing to clear the error afterwords and this is > resulting in a non-zero return(). Thus the reply packet is being > properly formatted but not being transmitted. > > I think all we need to do is set error = 0 for the NFSV3 case after > the nfsm_srvwcc_data() call. See the enclosed patch. We definitely > do not want to call nfsm_reply(0), because we already correctly call > nfsm_reply() on line 1761 (in STABLE). > > I really appreciate the effort you've put into tracking down these > problems, Dave! You are virtually the only one who has enough of a > mix of NFS clients to truely test the server-side code. The only > testing I can do is between FreeBSD boxes! > > In anycase, please try the enclosed patch. The patch, if correct, > should be applied to all branches. > > And if there is anyone else up on NFS I would appreciate a review of > the patch! Remember that nfsm_reply() deals with errors differently > between NFSv2 and NFSv3. Yes, I concur with your patch whole-heartedly. Apparently last night I was too-tired, and not intoxicated enough to understand the nfs_serv.c code :) I alas will not be able to test it. The machine is up and stable with 3k mbufs in reserve.. maybe later :) As an aside, what about getting rid of that mbuf leak if a nfs-service routine returns with error!=0? -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 14: 9: 3 1999 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 5850A15103 for ; Sat, 24 Jul 1999 14:08:52 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-117-43.bellatlantic.net [151.198.117.43]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id RAA10545; Sat, 24 Jul 1999 17:08:15 -0400 (EDT) Message-ID: <379A2BF4.278805D7@bellatlantic.net> Date: Sat, 24 Jul 1999 17:11:16 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-980222-SNAP i386) MIME-Version: 1.0 To: "Daniel C. Sobral" Cc: Mike Hoskins , Adrian Filipi-Martin , Vincent Poy , hackers@FreeBSD.ORG Subject: Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's References: <3799F7F6.CD75490F@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel C. Sobral wrote: > > Mike Hoskins wrote: > > > > This isn't a comment meant to contribute to the overcommit holy war > > (opinion mode: I think FreeBSD should overcommit, or at worst have a > > sysctl and default to overcommit - admins who don't want overcommit can > > then hang themselves), but we have to be a wee bit careful when throwing > > load averages around... > > > > I've seen FreeBSD boxes virtually unuseable with 3-4 loads, and Solaris > > boxes still chugging away at 5+... Perhaps 'load average' is being > > calculated a wee bit differently. > > I think that would rather be a function of the memory footprint of > the workload. The message said memory was increased because Solaris > was overloaded with _swapping_. The load itself isn't really of much > importance in this case. I think there is some confusion. In case of swapping the workload (A.K.A. CPU run queue length) will be _low_. Intensive swapping/paging means overloaded I/O subsystem and underloaded CPU. If the CPU has high load then the paging does not make a big problem, it just happens in "background" and does not really affect the system performance limited by the CPU bottleneck. Well, it may also favor the CPU-intensive application and limit the I/O-intensive applications if the filesystems and swap areas are on the same disks. (Yes, I have seen both cases in the real life). > Since Solaris does not overcommit, it needs (much) more memory than > FreeBSD would. Thus, changing to FreeBSD and upgrading the memory at It does not. It needs more swap space configured but not the physical memory. And at the current disk prices a 9G SCSI disk configured for swap would cost under $300, so the difference is not _that_ big. > Solaris is not a bad operating system. It's just misguided. :-) It's just terrible from the systems administration standpoint :-) -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 14:22: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id A385114FC4 for ; Sat, 24 Jul 1999 14:21:59 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 1189F7-000F5y-00; Sat, 24 Jul 1999 23:22:05 +0200 From: Sheldon Hearn To: chris@calldei.com Cc: hackers@FreeBSD.ORG Subject: Re: Mentioning RFC numbers in /etc/services In-reply-to: Your message of "Sat, 24 Jul 1999 08:25:55 EST." <19990724082555.A40344@holly.dyndns.org> Date: Sat, 24 Jul 1999 23:22:05 +0200 Message-ID: <58029.932851325@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Jul 1999 08:25:55 EST, Chris Costello wrote: > Are you going to be listing all the RFCs that apply? For > example, DNS is 1033, 1034, and 1035, and NNTP is 0850 and 0977. I doubt I'll be listing obsoleted RFCs. :-) I'll do the best I can. Send me private mail if you'd like to see what that is. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 16:42:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (Postfix) with ESMTP id C2A5C14D45 for ; Sat, 24 Jul 1999 16:42:23 -0700 (PDT) (envelope-from arg@arg1.demon.co.uk) Received: from localhost (arg@localhost) by arg1.demon.co.uk (8.8.8/8.8.8) with SMTP id AAA06726 for ; Sun, 25 Jul 1999 00:41:53 +0100 (BST) (envelope-from arg@arg1.demon.co.uk) Date: Sun, 25 Jul 1999 00:41:52 +0100 (BST) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: hackers@freebsd.org Subject: Linear buffers in VESA screen modes Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a plan for how to access the linear framebuffer in VESA video modes? So far as I can tell, the current[1] VESA code doesn't support enabling the linear framebuffer access at all, even though "vidcontrol -i mode" is happy to tell you the details of the buffers that you can't get access to! [1] actually, I'm working in -stable, but at a quick glance the -current code is the same in this area. I have used the following hack to make it work for my purposes: % cvs diff -c vesa.c Index: vesa.c =================================================================== RCS file: /repository/src/sys/i386/isa/vesa.c,v retrieving revision 1.15.2.5 diff -c -r1.15.2.5 vesa.c *** vesa.c 1999/04/16 15:58:21 1.15.2.5 --- vesa.c 1999/07/24 23:26:21 *************** *** 777,783 **** } #endif /* 0 */ ! if (vesa_bios_set_mode(mode)) return 1; #if VESA_DEBUG > 0 --- 777,784 ---- } #endif /* 0 */ ! /* If mode has a linear buffer, enable use of it */ ! if (vesa_bios_set_mode(info.vi_buffer ? (mode | 0x4000) : mode)) return 1; #if VESA_DEBUG > 0 This currently does the right thing (at least on my hardware) because all the modes that syscons supports for character I/O don't have a linear mapping and hence those modes get set for windowed access as before. However, it's probably not the proper solution. The application for which I need this is to support capture from the bktr driver onto the screen (ie. so that you can watch TV without X). With the above hack and a small (100-line) program it works very nicely - far tidier than installing X just for this purpose on some embedded systems where I need this capability. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 17:22:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 9854314F30 for ; Sat, 24 Jul 1999 17:22:30 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:OU9h1BGBcVLOxocaQFpchzbJ31pAUGlf@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id JAA19682; Sun, 25 Jul 1999 09:20:59 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id JAA08083; Sun, 25 Jul 1999 09:25:17 +0900 (JST) Message-Id: <199907250025.JAA08083@zodiac.mech.utsunomiya-u.ac.jp> To: Andrew Gordon Cc: hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Linear buffers in VESA screen modes In-reply-to: Your message of "Sun, 25 Jul 1999 00:41:52 +0100." References: Date: Sun, 25 Jul 1999 09:25:16 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Is there a plan for how to access the linear framebuffer in VESA video >modes? So far as I can tell, the current[1] VESA code doesn't support >enabling the linear framebuffer access at all, even though "vidcontrol -i >mode" is happy to tell you the details of the buffers that you can't get >access to! > >[1] actually, I'm working in -stable, but at a quick glance the -current >code is the same in this area. Actually -CURRENT sets up the linear framebuffer if available. >I have used the following hack to make it work for my purposes: [...] The vesa module in -CURRENT does basically the same as your patch. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 19:38:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id EB27714BF1 for ; Sat, 24 Jul 1999 19:38:38 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id MAA21069; Sun, 25 Jul 1999 12:07:42 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199907250237.MAA21069@gizmo.internode.com.au> Subject: Re: Filesystem question... To: rminnich@acl.lanl.gov (Ronald G. Minnich) Date: Sun, 25 Jul 1999 12:07:42 +0930 (CST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Ronald G. Minnich" at Jul 23, 99 09:30:54 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ronald G. Minnich wrote: > On Fri, 23 Jul 1999, Kris Kennaway wrote: > > On Thu, 22 Jul 1999, Ronald G. Minnich wrote: > > > Are you saying that as an ordinary user I can mount something on top of > > > /tmp, for example? > > If the vfs.usermount sysctl is 1, and you have appropriate access to the > > thing you're trying to mount (block device, etc). > > OK, so let's say it is 1. Let's say I have "appropriate access" to /tmp. I > mount my own fs on /tmp. I now have read/write access to everything anyone > writes to /tmp. "Appropriate access" includes the idea that you need to own the mountpoint directory. If you have a system that's so badly run that arbitrary users own /tmp, then I'd say user mounts are the least of your problems :-) > Or, let's say I don't have "appropriate access" to /tmp. Pick some other > place. I mount my file system there for my files. Now everyone who wants > can look for these user mounts and walk them at will. My private stuff is > quite public. Correct (unless you want your private stuff to be private, and chmod your mountpoint's parent directory accordingly). > But thanks for the note. I just now realized that if I add a private name > space to v9fs (which is easy), and then turn on user mounts, user > processes can have private name spaces on freebsd! I can't wait to see the security problems that causes when setuid executables assume that they only need to be worrying about one filesystem namespace. :-) - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 24 21:56:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 6BA1714BCE for ; Sat, 24 Jul 1999 21:56:29 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id AAA88251; Sun, 25 Jul 1999 00:53:06 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Sun, 25 Jul 1999 00:53:05 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Mark Newton Cc: "Ronald G. Minnich" , freebsd-hackers@FreeBSD.org Subject: Re: Filesystem question... In-Reply-To: <199907250237.MAA21069@gizmo.internode.com.au> 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, 25 Jul 1999, Mark Newton wrote: > Ronald G. Minnich wrote: > > > > But thanks for the note. I just now realized that if I add a private name > > space to v9fs (which is easy), and then turn on user mounts, user > > processes can have private name spaces on freebsd! > > I can't wait to see the security problems that causes when setuid executables > assume that they only need to be worrying about one filesystem namespace. > :-) There shouldn't be any problems if mount enabled the flags for nosuid/nodev etc. if suser(p) != 0. > > - mark > > > ---- > Mark Newton Email: newton@internode.com.au (W) > Network Engineer Email: newton@atdot.dotat.org (H) > Internode Systems Pty Ltd Desk: +61-8-82232999 > "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ 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 Sat Jul 24 22:14:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 7A9B514BFF for ; Sat, 24 Jul 1999 22:14:14 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id OAA26986; Sun, 25 Jul 1999 14:12:35 +0900 (JST) Message-ID: <379A9CAE.F697F68C@newsguy.com> Date: Sun, 25 Jul 1999 14:12:14 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Mark Newton Cc: "Ronald G. Minnich" , freebsd-hackers@FreeBSD.ORG Subject: Re: Filesystem question... References: <199907250237.MAA21069@gizmo.internode.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Newton wrote: > > > But thanks for the note. I just now realized that if I add a private name > > space to v9fs (which is easy), and then turn on user mounts, user > > processes can have private name spaces on freebsd! > > I can't wait to see the security problems that causes when setuid executables > assume that they only need to be worrying about one filesystem namespace. > :-) Yeah... it would be interesting to have a user-fs in which all executables where automatically chown to root, and setuid. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Your usefulness to my realm ended the day you made it off Hustaing alive." -- Sun Tzu Liao to his ex-finacee, Isis Marik To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message