From owner-freebsd-hackers Sun Jun 13 1:55:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 527F714C4B for ; Sun, 13 Jun 1999 01:55:28 -0700 (PDT) (envelope-from darius@dons.net.au) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id SAA75429 for ; Sun, 13 Jun 1999 18:25:27 +0930 (CST) (envelope-from darius@dons.net.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 13 Jun 1999 18:25:27 +0930 (CST) From: "Daniel J. O'Connor" To: freebsd-hackers@freebsd.org Subject: DHCP, arp and de0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have tried getting my system to use DHCP on my local network, but I'm having trouble. If I don't use DHCP everything works fine, but if I use DHCP I get the following messages appearing in my log file when I use ESD, and try and ping my LAN IP. Jun 13 17:35:21 guppy /kernel: arplookup 127.0.0.1 failed: could not allocate llinfo Jun 13 17:35:21 guppy /kernel: arpresolve: can't allocate llinfo for 127.0.0.1rt I notcied also that the arp table doesn't have an entry for my IP when I use DHCP. When I don't use DHCP I have a line like guppy.dons.net.au (203.31.81.9) at 0:80:ad:16:77:3e permanent [ethernet] in the arp table, but its not there when I use DHCP. I can't add it by hand either. I am running -current as of this morning (ie 12 Jun 10:30am GMT), and I have a Digital 21140 base 10/100 card. It has 2 ports, one for 10 and the other for 100 mbits (lame). Personally I suspect the driver since I've had other strangness with arp and this card when I try and change media, but I could be way off base. Any ideas? --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 2: 6:30 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 E4B2414CC7 for ; Sun, 13 Jun 1999 02:06:26 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 58927 invoked from network); 13 Jun 1999 09:06:25 -0000 Received: from shell-2.enteract.com (dscheidt@207.229.143.41) by pop3-3.enteract.com with SMTP; 13 Jun 1999 09:06:25 -0000 Received: from localhost (dscheidt@localhost) by shell-2.enteract.com (8.9.3/8.9.2) with SMTP id EAA53015; Sun, 13 Jun 1999 04:06:25 -0500 (CDT) (envelope-from dscheidt@enteract.com) X-Authentication-Warning: shell-2.enteract.com: dscheidt owned process doing -bs Date: Sun, 13 Jun 1999 04:06:25 -0500 (CDT) From: David Scheidt To: Bernd Walter Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates problem? In-Reply-To: <19990613084249.A66895@cicely8.cicely.de> 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, 13 Jun 1999, Bernd Walter wrote: > On Sat, Jun 12, 1999 at 12:13:43AM -0500, David Scheidt wrote: > > I had a 3.2 stable (from 30 May 1999)machine panic tonight, trying > > to load the oss driver, which is not too shocking. What was shocking > > was the damage done to my filesystem. The automatic fsck failed, > > with an UNEXPECTED SOFT UPDATES INCONSISTNCY. PARTIALLY ALLOCATED > > INODE I=39684. > > > What kernel-config are you using? > I have had several fs-crashes because of a to high configured maxusers. The only diffs between my config file and GENERIC are: 1. softupdates 2. no support for hardware I haven't got 3. pty is 64 I am not actually complaining about the panic; I think the oss driver is a piece of crap. I just happened to have a soundcard that they support that the FreeBSD drivers don't, and a .wav file I wanted to listen to. What does disturb me is the damage done to a pretty quiet filesystem. I wouldn't have thought that toasting a whole bunch of files that were not in use would be the normal behavior. I have seen lots of panics, but have never seen filesystem damage as bad as this. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 4:22:36 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 47E1714F97 for ; Sun, 13 Jun 1999 04:22:33 -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 NAA22388; Sun, 13 Jun 1999 13:22:30 +0200 (CEST) (envelope-from des) To: Brian Feldman Cc: hackers@FreeBSD.ORG Subject: Re: select(2) breakage References: From: Dag-Erling Smorgrav Date: 13 Jun 1999 13:22:30 +0200 In-Reply-To: Brian Feldman's message of "Sun, 13 Jun 1999 00:44:50 -0400 (EDT)" Message-ID: Lines: 29 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman writes: > Another problem that came up with this: I originally started at port 1024. > I monopolized 30000 ports (almost all consecutive, of course). When I try to > connect() a TCP socket as non-root, it fails with EAGAIN (I only tracked it > far enough down as in_pcbbind().) It seems that eventually it gives up trying > to find a port... :-/ What kind of connects are you doing? If you try to connect all your sockets to the same destination,port tuple you'll quickly run out of source ports, since there are only a little less than 4,000 ports available: des@des ~% sysctl -A | grep portrange net.inet.ip.portrange.lowfirst: 1023 net.inet.ip.portrange.lowlast: 600 net.inet.ip.portrange.first: 1024 net.inet.ip.portrange.last: 5000 net.inet.ip.portrange.hifirst: 49152 net.inet.ip.portrange.hilast: 65535 connect() normally uses the 1024-5000 range. Try the following: # sysctl -w net.inet.ip.portrange.last=40000 and see if it solves the EAGAIN problem. 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 Jun 13 7:25:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 502F914D22 for ; Sun, 13 Jun 1999 07:25:46 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (qmail 8173 invoked from network); 13 Jun 1999 14:25:44 -0000 Received: from dyson.iquest.net (198.70.144.127) by iquest3.iquest.net with SMTP; 13 Jun 1999 14:25:44 -0000 Received: (from root@localhost) by dyson.iquest.net (8.9.1/8.9.1) id JAA06530; Sun, 13 Jun 1999 09:25:38 -0500 (EST) From: "John S. Dyson" Message-Id: <199906131425.JAA06530@dyson.iquest.net> Subject: Re: problem for the VM gurus In-Reply-To: <199906130439.VAA65304@apollo.backplane.com> from Matthew Dillon at "Jun 12, 99 09:39:25 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sun, 13 Jun 1999 09:25:38 -0500 (EST) Cc: hgoldste@bbs.mpcs.com, dyson@iquest.net, freebsd-hackers@FreeBSD.ORG 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 > > * We hack a fix to deal with the mmap/write case. > > A permanent vnode locking fix is many months away because core > decided to ask Kirk to fix it, which was news to me at the time. > However, I agree with the idea of having Kirk fix VNode locking. > > But since this sort of permanent fix is months away, we really need > an interim solution to the mmap/write deadlock case. > > The easiest interim solution is to break write atomicy. That is, > unlock the vnode if the backing store of the uio being written is > (A) vnode-pager-backed and (B) not all in-core. > > This will generally fix all known deadlock situations but at the > cost of write atomicy in certain cases. We can use the same hack > that pipe code uses and only guarentee write atomicy for small > block sizes. We would do this by wiring ( and faulting, if > necessary ) the first N pages of the uio prior to locking the vnode. > > We cannot wire all the pages of the uio since the user may specify > a very large buffer - megabytes or gigabytes. > > * Stage 3: Permanent fix is committed by generally fixing vnode locks > and VFS layering. > > ... which may be 6 months if Kirk agrees to do a complete rewrite > of the vnode locking algorithms. > Regarding atomicy: Remember that you cannot assume that the mappings stay the same during almost any I/O mechanism anymore. The issue of wiring pages and assuming constant mapping has to be resolved. A careful definition of whether or not one is doing I/O to an address or I/O to a specific piece of memory. I know that this is an end condition, but it has consequences as to the effects on the design. (I suspect that a punt to do I/O to a virtual address is correct, but those change, and also disappear.) John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 8: 1:30 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 384CC14D22 for ; Sun, 13 Jun 1999 08:01:27 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id LAA26460; Sun, 13 Jun 1999 11:01:26 -0400 (EDT) Date: Sun, 13 Jun 1999 11:01:26 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.ORG Subject: Re: select(2) breakage 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 13 Jun 1999, Dag-Erling Smorgrav wrote: > Brian Feldman writes: > > Another problem that came up with this: I originally started at port 1024. > > I monopolized 30000 ports (almost all consecutive, of course). When I try to > > connect() a TCP socket as non-root, it fails with EAGAIN (I only tracked it > > far enough down as in_pcbbind().) It seems that eventually it gives up trying > > to find a port... :-/ > > What kind of connects are you doing? If you try to connect all your > sockets to the same destination,port tuple you'll quickly run out of > source ports, since there are only a little less than 4,000 ports > available: > > des@des ~% sysctl -A | grep portrange > net.inet.ip.portrange.lowfirst: 1023 > net.inet.ip.portrange.lowlast: 600 > net.inet.ip.portrange.first: 1024 > net.inet.ip.portrange.last: 5000 > net.inet.ip.portrange.hifirst: 49152 > net.inet.ip.portrange.hilast: 65535 > > connect() normally uses the 1024-5000 range. Try the following: > > # sysctl -w net.inet.ip.portrange.last=40000 > > and see if it solves the EAGAIN problem. Actually, this is the perfect explanation. I think that this should go in the FAQ. Why in the world are we limiting the ports we can use other than from 1-1023? > > 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 > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___/___/___/ " THAT'S WRONG WRONG WRONG!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 8:46:21 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 DE0FA14E07 for ; Sun, 13 Jun 1999 08:46:18 -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 RAA28184; Sun, 13 Jun 1999 17:46:15 +0200 (CEST) (envelope-from des) To: Brian Feldman Cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG Subject: Re: select(2) breakage References: From: Dag-Erling Smorgrav Date: 13 Jun 1999 17:46:13 +0200 In-Reply-To: Brian Feldman's message of "Sun, 13 Jun 1999 11:01:26 -0400 (EDT)" Message-ID: Lines: 33 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman writes: > On 13 Jun 1999, Dag-Erling Smorgrav wrote: > > connect() normally uses the 1024-5000 range. Try the following: > > > > # sysctl -w net.inet.ip.portrange.last=40000 > > > > and see if it solves the EAGAIN problem. > > Actually, this is the perfect explanation. I think that this should go in > the FAQ. Why in the world are we limiting the ports we can use other than > from 1-1023? I have no idea. The only use I've ever had for this is the predictability of FTP data port numbers, since ftpd will normally use the high range (49152-65535). Useful for designing firewalls, and if you don't like opening such a wide port range, you can whittle it down to a handful (say, one thousand) of ports with judicious use of sysctl. I couldn't find any reference to this in RFC 793, 1122, 1123, 1700 or 2577. Remind me to build a glimpse index of my RFC collection... This still doesn't explain select()'s failure to time out, although I should point out that you forgot to increase FD_SETSIZE before including , and I'm not sure your computation of highestsock is correct, since there's no guarantee that fdvec is sorted. I haven't tested your code though, I just looked over it quickly. BTW, you should check for errno == EINTR when select() returns -1. 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 Jun 13 8:59:58 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 2BD1714CA8 for ; Sun, 13 Jun 1999 08:59:55 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id LAA27328; Sun, 13 Jun 1999 11:59:55 -0400 (EDT) Date: Sun, 13 Jun 1999 11:59:55 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.ORG Subject: Re: select(2) breakage 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 13 Jun 1999, Dag-Erling Smorgrav wrote: > Brian Feldman writes: > > On 13 Jun 1999, Dag-Erling Smorgrav wrote: > > > connect() normally uses the 1024-5000 range. Try the following: > > > > > > # sysctl -w net.inet.ip.portrange.last=40000 > > > > > > and see if it solves the EAGAIN problem. > > > > Actually, this is the perfect explanation. I think that this should go in > > the FAQ. Why in the world are we limiting the ports we can use other than > > from 1-1023? > > I have no idea. The only use I've ever had for this is the > predictability of FTP data port numbers, since ftpd will normally use > the high range (49152-65535). Useful for designing firewalls, and if > you don't like opening such a wide port range, you can whittle it down > to a handful (say, one thousand) of ports with judicious use of sysctl. > > I couldn't find any reference to this in RFC 793, 1122, 1123, 1700 or > 2577. Remind me to build a glimpse index of my RFC collection... > > This still doesn't explain select()'s failure to time out, although I > should point out that you forgot to increase FD_SETSIZE before > including , and I'm not sure your computation of > highestsock is correct, since there's no guarantee that fdvec is > sorted. I haven't tested your code though, I just looked over it > quickly. I have two copies. One has FD_SETSIZE increased to 30004 and a vector size of 30000. The other has FD_SETSIZE default (1024) and a vector of 512. The guarantee of fdvec is sorted is that Unix behavior is to allocate the next available fd, so highestsock is correct. The program is correct, except I didn't have a linefeed in the select() status printing, so it DID time out successfully, but you didn't see the status report. > > BTW, you should check for errno == EINTR when select() returns -1. The perror() is the status report for select() when -1. > > 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 > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___/___/___/ " THAT'S WRONG WRONG WRONG!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 9: 0:52 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 5448314CA8 for ; Sun, 13 Jun 1999 09:00: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 SAA28506; Sun, 13 Jun 1999 18:00:48 +0200 (CEST) (envelope-from des) To: Dag-Erling Smorgrav Cc: Brian Feldman , hackers@FreeBSD.ORG Subject: Re: select(2) breakage References: From: Dag-Erling Smorgrav Date: 13 Jun 1999 18:00:48 +0200 In-Reply-To: Dag-Erling Smorgrav's message of "13 Jun 1999 17:46:13 +0200" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav writes: > This still doesn't explain select()'s failure to time out Found it! If you change: printf("no select() action"); to: fprintf(stderr, "no select() action\n"); you'll see that select() does time out. The moral of this story is to always use an unbuffered stream for logging and debugging messages. 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 Jun 13 9: 2:30 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 2D13114CA8 for ; Sun, 13 Jun 1999 09:02:27 -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 SAA28551; Sun, 13 Jun 1999 18:02:24 +0200 (CEST) (envelope-from des) To: Brian Feldman Cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG Subject: Re: select(2) breakage References: From: Dag-Erling Smorgrav Date: 13 Jun 1999 18:02:24 +0200 In-Reply-To: Brian Feldman's message of "Sun, 13 Jun 1999 11:59:55 -0400 (EDT)" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman writes: > On 13 Jun 1999, Dag-Erling Smorgrav wrote: > > BTW, you should check for errno == EINTR when select() returns -1. > The perror() is the status report for select() when -1. Yeah, but EINTR is a normal condition, so I'd ignore it silently instead of logging it. Of course, the purpose of this program is to demonstrate select() behaviour, so logging EINTR is valid. 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 Jun 13 9: 8: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 82B3C14EAC for ; Sun, 13 Jun 1999 09:07:58 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id MAA13761; Sun, 13 Jun 1999 12:06:23 -0400 (EDT) Date: Sun, 13 Jun 1999 12:06:23 -0400 (EDT) From: Chuck Robey To: Bill Huey Cc: Wes Peters , freebsd-hackers@FreeBSD.ORG Subject: Re: High syscall overhead? In-Reply-To: <199906130624.XAA03037@mag.ucsd.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 Sat, 12 Jun 1999, Bill Huey wrote: > > > The Linux philosophy has always been about simplistic cycle counting > > exercises without understand whether the data had any meaning or not. > > You've once again displayed your wholehearted participation in this > > lack of understanding of what the data points might mean to any real- > > world application. > > Well, the thing I'm talking about isn't a philosophy, because > it removed data serialization doing what I suspect is a kernel/user > space copy from doing a superficial glance of the code. > > This is one of the detected bottlenecks in the Mindcraft study that > suck copy performance by approximately 4 times. > > Another things that was included on the like bottleneck list is > the waking of all the processes in the process queue when accept() > is being called. This was termed the "Thundering Herds" problem, which > they solve using a wake-one process implementation of accept(). > > > denial" part. Or, better yet, just fuck off and get the hell off our > > list. This is NOT an appropriate forum for Linux advocacy, which seems > > to be all you can do. > > Well, so far I've heard alot of BS about Linux that isn't exactly true > and much of it seems like a bunch of artificial problems that hold > against the Linux folks. Most of it is just intentionally misrepresented > bullshit. That is totally wrong, Bill. We have a public mail archive, so if you don't like to believe me, go check our archive. YOU have been the only source of either Linux or FreeBSD bashing. We have a pretty pleasing assortment of grownups here, who have gone past the point of needing to claim "my ball is better than your ball". One of my own personal complaints about the Linux groups is that they seem to grow the kind of people who need to disparage in order to feel good. This might be because my only exposure to Linux persons is via Usenet, which is immersed in that teenage-type philosophy. I don't know of any Linux mailing lists of the order of the FreeBSD lists. We don't need that approach here, it doesn't increase knowledge, and only hurts feelings. If you follow up on this thread, please DROP all Linux/FreeBSD comparisons of that order. We all know that both Linux AND FreeBSD are fine unixes, and we don't need bashing here. This list does occaisonally have some comparisons, Linux vs. FreeBSD, but if it isn't kept strictly technical, and non-accusatory, we don't want it or need it. I have seen people in the past that were honestly surprised at the huge difference between Usenet newsgroup rules, and our FreeBSD list rules. If you actually fit in that category, maybe you should "lurk" these lists for a while, so you can see the difference, and not find yourself outside of our lists normal behaviour. > > I came on this list initially to just check was the FreeBSD community > was like, but what I've gotten since is alot of ego and hostility > toward things that aren't completely FreeBSD. That's something that > I didn't expect and reading this list has given me a particular > negative view of FreeBSD that wasn't present before. People don't like your need to compare, in order to make one group seem better or worse than another. You need to find some other way to get your point across. > > In-fighting with the current NFS maintainer and general rudeness to other > potential devs make FreeBSD's kernel people look like bunch of dorks whether > you like it or not. > > I'm also not big enough asshole ot put someone on a "kill-list" and is just > a reflection of a kind of conservative need to dehumanize other folks > so that your selfish comfort is "preserved". Profanity is also one of the things not accepted here. > > > Wes Peters Softweyr LLC > > bill > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 9:13:35 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 6561515289 for ; Sun, 13 Jun 1999 09:13:25 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.2/8.9.2) id QAA49007; Sun, 13 Jun 1999 16:13:07 +0100 (BST) (envelope-from nik) Date: Sun, 13 Jun 1999 16:13:06 +0100 From: Nik Clayton To: Bill Huey Cc: Wes Peters , freebsd-hackers@freebsd.org Subject: Re: High syscall overhead? Message-ID: <19990613161305.A47537@catkin.nothing-going-on.org> Reply-To: nik@freebsd.org References: <37633725.3BD5BECD@softweyr.com> <199906130624.XAA03037@mag.ucsd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906130624.XAA03037@mag.ucsd.edu>; from Bill Huey on Sat, Jun 12, 1999 at 11:24:11PM -0700 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ cc'd to -hackers for the archives, reply-to points back to me so that this doesn't perpetuate on the list ] On Sat, Jun 12, 1999 at 11:24:11PM -0700, Bill Huey wrote: > I came on this list initially to just check was the FreeBSD community > was like, Then you chose the wrong list. As the web pages point out, this list is for technical discussion. It's not somewhere you go to find out what the community is like. There's already too much noise on this list, and all this is doing is contributing to it. If you want to find out what the community is like then subscribe to -chat, and read and post, or subscribe to -questions, and just read. You'll get a much better idea that way. > I'm also not big enough asshole ot put someone on a "kill-list" and is just > a reflection of a kind of conservative need to dehumanize other folks > so that your selfish comfort is "preserved". Post technical content to a technical mailing list and expect to be treated with respect. Post ill advised non technical content and expect to be treated like an idiot. As I say, feel free to join -chat to see how the FreeBSD community behaves. 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 Sun Jun 13 9:23:10 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 6F8001514A for ; Sun, 13 Jun 1999 09:23:07 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id MAA27785; Sun, 13 Jun 1999 12:22:14 -0400 (EDT) Date: Sun, 13 Jun 1999 12:22:13 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Chuck Robey Cc: Bill Huey , Wes Peters , freebsd-hackers@FreeBSD.ORG Subject: Re: High syscall overhead? 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, 13 Jun 1999, Chuck Robey wrote: > On Sat, 12 Jun 1999, Bill Huey wrote: > > > Well, so far I've heard alot of BS about Linux that isn't exactly true > > and much of it seems like a bunch of artificial problems that hold > > against the Linux folks. Most of it is just intentionally misrepresented > > bullshit. > > That is totally wrong, Bill. We have a public mail archive, so if you > don't like to believe me, go check our archive. YOU have been the only > source of either Linux or FreeBSD bashing. We have a pretty pleasing > assortment of grownups here, who have gone past the point of needing to > claim "my ball is better than your ball". Exactly. Do you have references? > > One of my own personal complaints about the Linux groups is that they > seem to grow the kind of people who need to disparage in order to feel > good. This might be because my only exposure to Linux persons is via > Usenet, which is immersed in that teenage-type philosophy. I don't know > of any Linux mailing lists of the order of the FreeBSD lists. The Linux-kernel mailing list seems to be closer to -hackers. > > We don't need that approach here, it doesn't increase knowledge, > and only hurts feelings. If you follow up on this thread, please DROP > all Linux/FreeBSD comparisons of that order. We all know that both > Linux AND FreeBSD are fine unixes, and we don't need bashing here. Linux is a Unix clone, while FreeBSD is Unix. Don't confuse people with this. > > This list does occaisonally have some comparisons, Linux vs. FreeBSD, > but if it isn't kept strictly technical, and non-accusatory, we don't > want it or need it. > > I have seen people in the past that were honestly surprised at the huge > difference between Usenet newsgroup rules, and our FreeBSD list rules. > If you actually fit in that category, maybe you should "lurk" these > lists for a while, so you can see the difference, and not find yourself > outside of our lists normal behaviour. The noise to content ratio is MUCH higher on Usenet, and probably will always be. > > > > > I came on this list initially to just check was the FreeBSD community > > was like, but what I've gotten since is alot of ego and hostility > > toward things that aren't completely FreeBSD. That's something that > > I didn't expect and reading this list has given me a particular > > negative view of FreeBSD that wasn't present before. > > People don't like your need to compare, in order to make one group seem > better or worse than another. You need to find some other way to get > your point across. > > > > > In-fighting with the current NFS maintainer and general rudeness to other > > potential devs make FreeBSD's kernel people look like bunch of dorks whether > > you like it or not. Don't confuse fighting with "not sweeping issues under the carpet." > > > > I'm also not big enough asshole ot put someone on a "kill-list" and is just > > a reflection of a kind of conservative need to dehumanize other folks > > so that your selfish comfort is "preserved". > > Profanity is also one of the things not accepted here. Damn straight! Sorry, couldn't resist. Profanity isn't that unacceptable, if appropriate (sometimes it is..), but personal attacks ARE. > > > > > > Wes Peters Softweyr LLC > > > > bill > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@picnic.mat.net | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. > (301) 220-2114 | > ----------------------------+----------------------------------------------- > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___/___/___/ " THAT'S WRONG WRONG WRONG!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 10: 6:25 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 D4A5C150B5 for ; Sun, 13 Jun 1999 10:06:23 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA04284; Sun, 13 Jun 1999 10:06:20 -0700 (PDT) (envelope-from dillon) Date: Sun, 13 Jun 1999 10:06:20 -0700 (PDT) From: Matthew Dillon Message-Id: <199906131706.KAA04284@apollo.backplane.com> To: David Scheidt Cc: Bernd Walter , freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates problem? References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Sun, 13 Jun 1999, Bernd Walter wrote: : :> On Sat, Jun 12, 1999 at 12:13:43AM -0500, David Scheidt wrote: :> > I had a 3.2 stable (from 30 May 1999)machine panic tonight, trying :> > to load the oss driver, which is not too shocking. What was shocking :> > was the damage done to my filesystem. The automatic fsck failed, :> > with an UNEXPECTED SOFT UPDATES INCONSISTNCY. PARTIALLY ALLOCATED :> > INODE I=39684. :> > :> What kernel-config are you using? :> I have had several fs-crashes because of a to high configured maxusers. : :The only diffs between my config file and GENERIC are: :1. softupdates :2. no support for hardware I haven't got :3. pty is 64 : :I am not actually complaining about the panic; I think the oss :driver is a piece of crap. I just happened to have a soundcard :that they support that the FreeBSD drivers don't, and a .wav file :I wanted to listen to. What does disturb me is the damage done to :a pretty quiet filesystem. I wouldn't have thought that toasting :a whole bunch of files that were not in use would be the normal :behavior. I have seen lots of panics, but have never seen filesystem :damage as bad as this. : :David Scheidt This smells like a memory corruption problem rather then a softupdates problem. i.e. that something in the kernel overwrote random kernel memory which happened to correspond to a filesystem buffer. There was a buffer corruption bug found in VFS/BIO recently, but it was fixed prior to the 3.2 release ( it was an getnewbuf() race, fixed in 1.193.2.4 of kern/vfs_bio.c ). -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 Sun Jun 13 10:16:19 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 5F28D15197 for ; Sun, 13 Jun 1999 10:16:17 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA04387; Sun, 13 Jun 1999 10:16:15 -0700 (PDT) (envelope-from dillon) Date: Sun, 13 Jun 1999 10:16:15 -0700 (PDT) From: Matthew Dillon Message-Id: <199906131716.KAA04387@apollo.backplane.com> To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: The clean and dirty buffer list of a vnode References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :>From the source code of vtruncbuf() in file vfs_subr.c, I find out that :the code deals with the case when a buffer linked on the clean or dirty :list of a vnode can change its identity (b_xflags flag, b_vp field, or :B_DELWRI flag). For example, a buffer's B_VNCLEAN flag is cleared even if :it is found on the clean list. Or a buffer's B_DELWRI flag is cleared :even if it is found on the dirty list. This is new in FreeBSD 3.x. : :Can anyone explain to me how can this happen? : :Any help is appreciated. : :-------------------------------------------------- :Zhihui Zhang. Please visit http://www.freebsd.org :-------------------------------------------------- Ah, I know what this is.... I was confused by your description. What is going on here is that vtruncbuf() is scanning a linked list and potentially sleeping in the middle of the scan. It is possible for the current buffer in the scan to be ripped out from under the scan during the sleep and move to a different queue. So, in fact, if B_VNCLEAN is set we know that the buffer is on the clean list, and vise versa, and we use this to check whether we've been transported to a different queue during the scan. Even though the code looks messy, it works as advertised. -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 Sun Jun 13 10:37:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sdios.sea.ru (sdios.sea.ru [194.87.190.76]) by hub.freebsd.org (Postfix) with ESMTP id CC7D514C1F; Sun, 13 Jun 1999 10:37:10 -0700 (PDT) (envelope-from adm@sdios.sea.ru) Received: from sdios.sea.ru (filer.sdios.sea.ru [10.1.1.20]) by sdios.sea.ru (8.8.8/8.8.8) with ESMTP id BAA01740; Mon, 14 Jun 1999 01:42:50 +0400 (MSD) (envelope-from adm@sdios.sea.ru) Message-ID: <3763EBE7.21244F2D@sdios.sea.ru> Date: Sun, 13 Jun 1999 21:35:36 +0400 From: "Southern Branch of the P.P.Shirshov Institute of Oceanology" X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: UDP sockets Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ! I have a problem. My program creates UDP-socket and after that it tries to create UDP or TCP-socket. But last one doesn't work. TCP doesn't execute "accept" UDP doesn't execute "recvfrom" What can I do ? Answer me via e-mail:pavel@sdios.sea.ru Thank you Pavel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 10:55:46 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 81D1D1522B for ; Sun, 13 Jun 1999 10:55:43 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 25579 invoked by uid 1001); 13 Jun 1999 17:55:42 +0000 (GMT) To: green@unixhelp.org Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: High syscall overhead? From: sthaug@nethelp.no In-Reply-To: Your message of "Sun, 13 Jun 1999 12:22:13 -0400 (EDT)" 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, 13 Jun 1999 19:55:42 +0200 Message-ID: <25577.929296542@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Linux is a Unix clone, while FreeBSD is Unix. Don't confuse people with > this. I'm afraid that attitude isn't going to help Unix agains Windows... I use FreeBSD for all my systems. I still go around and tell people that Linux is one several Unix variants, and I intend to continue doing this. For an end user, the differences between for instance FreeBSD and Linux are in most cases small and rather uninteresting - and it's much more useful to point out the differences between Unix and Windows. 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 Jun 13 10:58:54 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 146E61514A; Sun, 13 Jun 1999 10:58:51 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id NAA29304; Sun, 13 Jun 1999 13:58:02 -0400 (EDT) Date: Sun, 13 Jun 1999 13:58:02 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "Southern Branch of the P.P.Shirshov Institute of Oceanology" Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: UDP sockets In-Reply-To: <3763EBE7.21244F2D@sdios.sea.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 Sun, 13 Jun 1999, Southern Branch of the P.P.Shirshov Institute of Oceanology wrote: > Hi ! > I have a problem. > My program creates UDP-socket and after that it tries to create UDP or > TCP-socket. But last one doesn't work. > TCP doesn't execute "accept" > UDP doesn't execute "recvfrom" > What can I do ? This is almost CERTAINLY programmer error. Have someone experienced look at your source. > > Answer me via e-mail:pavel@sdios.sea.ru > > Thank you > Pavel > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___/___/___/ " THAT'S WRONG WRONG WRONG!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 11: 1:37 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 3F67115254 for ; Sun, 13 Jun 1999 11:01:36 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id OAA29402; Sun, 13 Jun 1999 14:01:35 -0400 (EDT) Date: Sun, 13 Jun 1999 14:01:35 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: sthaug@nethelp.no Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: High syscall overhead? In-Reply-To: <25577.929296542@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, 13 Jun 1999 sthaug@nethelp.no wrote: > > Linux is a Unix clone, while FreeBSD is Unix. Don't confuse people with > > this. > > I'm afraid that attitude isn't going to help Unix agains Windows... > > I use FreeBSD for all my systems. I still go around and tell people that > Linux is one several Unix variants, and I intend to continue doing this. > For an end user, the differences between for instance FreeBSD and Linux > are in most cases small and rather uninteresting - and it's much more > useful to point out the differences between Unix and Windows. > And the differences between a BSD system and Linux aren't huge? Nay, sir, surely you jest. I, personally, dislike people using the wrong terminology. Linux is a relatively Unix-like and relatively POSIX-compliant system, but it's not Unix. What's wrong with calling a system by its true name? > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___/___/___/ " THAT'S WRONG WRONG WRONG!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 11:14:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from server.ghostgbtb.com (modem11.tekrab.net [208.30.20.211]) by hub.freebsd.org (Postfix) with ESMTP id 5DF091514A for ; Sun, 13 Jun 1999 11:14:10 -0700 (PDT) (envelope-from mrami@gbtb.com) Received: from localhost (mrami@localhost) by server.ghostgbtb.com (8.9.2/8.9.2) with SMTP id OAA00701 for ; Sun, 13 Jun 1999 14:14:10 -0400 (EDT) (envelope-from mrami@gbtb.com) X-Authentication-Warning: server.ghostgbtb.com: mrami owned process doing -bs Date: Sun, 13 Jun 1999 14:13:46 -0400 (EDT) From: Marc Ramirez X-Sender: mrami@server.ghostgbtb.com To: hackers@freebsd.org Subject: symlink question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry if I'm bothering you busy folk unnecessarily... If I wanted to add variant symlinks, would that just require modifications to namei, or is that way too simplistic? Thanks, Marc. -- Marc Ramirez - Owner Great Big Throbbing Brains mrami@gbtb.com http://www.gbtb.com Our brains throb, so yours won't have to! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 13:33:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 71FC314E2C for ; Sun, 13 Jun 1999 13:33:47 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id NAA26102; Sun, 13 Jun 1999 13:30:21 -0700 (PDT) Message-Id: <199906132030.NAA26102@implode.root.com> To: Matthew Dillon Cc: hgoldste@bbs.mpcs.com (Howard Goldstein), dyson@iquest.net, freebsd-hackers@FreeBSD.ORG, "John S. Dyson" Subject: Re: problem for the VM gurus In-reply-to: Your message of "Sat, 12 Jun 1999 21:39:25 PDT." <199906130439.VAA65304@apollo.backplane.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 13 Jun 1999 13:30:21 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A permanent vnode locking fix is many months away because core > decided to ask Kirk to fix it, which was news to me at the time. > However, I agree with the idea of having Kirk fix VNode locking. Actually, core did no such thing. Kirk told me a month or so ago that he intended to fix the vnode locking. Not that this is particularly important, but people shouldn't get the idea that Kirk's involvement had anything to do with core since it did not. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 14:22:47 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 CDEC314C8B for ; Sun, 13 Jun 1999 14:22:45 -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 4E59B2E20B; Sun, 13 Jun 1999 17:20:05 -0400 (EDT) Message-Id: <4.1.19990613170939.043d4320@mail.venux.net> X-Sender: mhagerty@mail.venux.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 13 Jun 1999 17:23:01 -0400 To: hackers@freebsd.org From: Matthew Hagerty Subject: 3c562/563 PCMCIA LAN+33.6 PC Card 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 purchased a 3Com EtherLink III LAN+33.6 Modem PCMCIA card only to find that FreeBSD does not yet support the 3c562 controller. There was a post a day or two ago that had this subject line: sysnewconfig990609-kld990609test8.7.patch.gz Does this patch give a 3.2-RELEASE support for the 3c562 controller? If so, is there any way I can get a boot floppy with this support so I can do a network install (I don't have a CD-ROM for my laptop). If there is no support for the 3c562, what would be a good driver for me to start with to write a driver? Also, where can one get a programmers guide to 3Com's NIC chipsets? Thanks 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 Sun Jun 13 15:11:14 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 7A0B514F20 for ; Sun, 13 Jun 1999 15:11:13 -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 PAA52608; Sun, 13 Jun 1999 15:10:54 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Brian Feldman Cc: Chuck Robey , Bill Huey , Wes Peters , freebsd-hackers@FreeBSD.ORG Subject: Re: High syscall overhead? In-reply-to: Your message of "Sun, 13 Jun 1999 12:22:13 EDT." Date: Sun, 13 Jun 1999 15:10:54 -0700 Message-ID: <52604.929311854@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not to pick on Brian, but can we end this pathetic and sorry thread already? Everybody: Just play nice with your little brother and stop poking him in the back seat - we'll get to where we're going soon and then everybody can have a milkshake if they've been good. Thank you. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 15:53:21 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 B010014CB6 for ; Sun, 13 Jun 1999 15:53: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 PAA51738; Sun, 13 Jun 1999 15:53:05 -0700 (PDT) Date: Sun, 13 Jun 1999 15:53:04 -0700 (PDT) From: Julian Elischer To: "John S. Dyson" Cc: Matthew Dillon , hgoldste@bbs.mpcs.com, dyson@iquest.net, freebsd-hackers@FreeBSD.ORG Subject: Re: problem for the VM gurus In-Reply-To: <199906131425.JAA06530@dyson.iquest.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 Sun, 13 Jun 1999, John S. Dyson wrote: > > Remember that you cannot assume that the mappings stay the same during > almost any I/O mechanism anymore. The issue of wiring pages and assuming > constant mapping has to be resolved. A careful definition of whether > or not one is doing I/O to an address or I/O to a specific piece of > memory. I know that this is an end condition, but it has consequences > as to the effects on the design. (I suspect that a punt to do I/O > to a virtual address is correct, but those change, and also disappear.) Which brings up the fact that some of us have been talking about making all IO operations refer to PHYSICAL pages at the strategy layer. Consider.... for Raw IO: read() ... user address physio() ... user pages are faulted to ensur ethey are present, then physical addreses are extracted and remapped to KV. addresses strategy.. for DMA devices (most ones we really care about) ... KV addresses are converted to PHYSICAL addresses again. If we changed the iterface so that the UIO passed from physio to the strategy routine held an array of physical addresses we could save quite a bit of work. Also, it wouldn't matter that the pages were or were not mapped, as long as they are locked in ram. For domb devices that don't do DMA, the pages would be mapped by some other special scheme. For pages coming from the buffer cache/vm system, the physical page addresses should be known already somewhere and the physical UIO addresses should be pretty trivially collected for the Strategy. This sounds like a project that could be bitten off and completed pretty quickly. 1/ redefine UIO correctly to include UIO_PHYSSPACE and an appropriate change in iovec to allow physical addresses.. (they may be differnt to virtual addresses in some architectures).. maybe define a phys_iovec[] and make the pointer in UIO a pointer to a union. (?) 2/ change drivers to be able to handle getting a UIO_PHYSSPACE request. This would require adding a routine to map such requests into KV space, for use by the dumb drivers. (all drivers still know how to handle old type requests) 3/ Change the callers at our leasure (e.g. physio, buffercache etc.) anyone have comments? I know I discussed this with the NetBSD guys (e.g. chuq, chuck and jason) and they said htay were looking at similar things. possible gotcha's: you would have to be careful about blocking when allocating teh IOVEC of physical addresses. maybe they would be allocated as part of allocating the UIO. (maybe you'd hav eot specify how many pages the UIO should hold when you allocate it to optimise the allocation. How this fit's into the proposed rewriting of the iorequest (struct buf) rewrite that's been rumbling in the background needs evaluation. julian p.s. david.. you didn't comment on Matt's subission of a plan for attacking the deadlock problem. It sounded reasonable to me but I'm only marginal in this area. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 16:23:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 7662615182 for ; Sun, 13 Jun 1999 16:23:15 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id QAA26382; Sun, 13 Jun 1999 16:21:51 -0700 (PDT) Message-Id: <199906132321.QAA26382@implode.root.com> To: Matthew Dillon Cc: dyson@iquest.net, freebsd-hackers@FreeBSD.ORG Subject: Re: problem for the VM gurus In-reply-to: Your message of "Sat, 12 Jun 1999 21:39:25 PDT." <199906130439.VAA65304@apollo.backplane.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 13 Jun 1999 16:21:51 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Interesting. It's an overlapping same-process deadlock with mmap/write. > This bug also hits NFS, though in a slightly different way, and also > occurs with mmap/write when two processes are mmap'ing two files and > write()ing the other descriptor using the map as a buffer. > > I see a three-stage solution: > > * We change the API for the VM pager *getpages() code. > > At the moment the caller busies all pages being passed to getpages() > and expects the primary page (but not any of the others) to be > returned busied. I also believe that some of the code assumes that > the page will not be unbusied at all for the duration of the > operation ( though vm_fault was hacked to handle the situation where > it might have been ). > > This API is screwing up NFS and would also make it very difficult for > general VFS deadlock avoidance to be implemented properly and for > a fix to the specific case being discussed in this thread to be > implemented properly. > > I recommend changing the API such that *ALL* passed pages are > unbusied prior to return. The caller of getpages() must then > VM lookup the page again. Always. vm_fault already does this, > in fact. We would clean up the code and document it to this effect. > > This change would allow us to immediately fix the self-referential > deadlocks and I think it would also allow me to fix a similar bug > in NFS trivially. I should point out here that the process of looking up the pages is a significant amount of the overhead of the routines involved. Although doing this for just one page is probably sufficiently in the noise as to not be a concern. > The easiest interim solution is to break write atomicy. That is, > unlock the vnode if the backing store of the uio being written is > (A) vnode-pager-backed and (B) not all in-core. Uh, I don't think you can safely do that. I thought one of the reasons for locking a vnode for writes is so that the file metadata doesn't change underneath you while the write is in progress, but perhaps I'm wrong about that. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 16:57:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from detlev.UUCP (tex-123.camalott.com [208.229.74.123]) by hub.freebsd.org (Postfix) with ESMTP id 67CBE14C56 for ; Sun, 13 Jun 1999 16:55:58 -0700 (PDT) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.3) id SAA90612; Sun, 13 Jun 1999 18:55:53 -0500 (CDT) (envelope-from joelh) To: freebsd-hackers@freebsd.org Subject: vn swapfiles deleted while in use From: Joel Ray Holveck Date: 13 Jun 1999 18:55:52 -0500 Message-ID: <86vhcr3bav.fsf@detlev.UUCP> Lines: 11 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What, to the reckoning of the resident populace, would happen if somebody were to rm a vnconfig'd swapfile while it was in use? Thanks, 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 Sun Jun 13 16:58:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from surf.iae.nl (surf.IAE.nl [194.151.66.2]) by hub.freebsd.org (Postfix) with ESMTP id C234D14C56 for ; Sun, 13 Jun 1999 16:58:29 -0700 (PDT) (envelope-from wjw@iae.nl) Received: by surf.iae.nl (Postfix, from userid 74) id 8B5C29907; Mon, 14 Jun 1999 01:58:28 +0200 (MET DST) To: mrami@gbtb.com Subject: Re: symlink question X-Newsgroups: list.freebsd.hackers In-Reply-To: Organization: Internet Access Eindhoven Cc: hackers@freebsd.org Message-Id: <19990613235828.8B5C29907@surf.iae.nl> Date: Mon, 14 Jun 1999 01:58:28 +0200 (MET DST) From: wjw@iae.nl (Willem Jan Withagen) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: > >Sorry if I'm bothering you busy folk unnecessarily... > >If I wanted to add variant symlinks, would that just require modifications >to namei, or is that way too simplistic? I've done that part with help of Mike Smith and others. I still have the changes around somewhere. it was the simpeler part of the job. The harder part is to get something to be usable to replace the variable part with. There has been some discussion on how to get information to the kernel on the variant part. And what kind of problems would go with that. I started on an excursion into sysctl to make it much more dynamic. And use the information stored in there as subsitute values for the variant-links. But since I ran out of holyday time, it has been shelved. The discussions should still be in the archives. Most probably under variant links. --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 9.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 17: 2:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from postoffice.na2k.net (B-075.NET-LYNX.COM [206.132.230.75]) by hub.freebsd.org (Postfix) with ESMTP id 52EE914EA2 for ; Sun, 13 Jun 1999 17:02:57 -0700 (PDT) (envelope-from cyouse@cybersites.com) Received: from [206.132.230.101] by postoffice.na2k.net (NTMail 4.20.0009/NU4022.00.b1f4d9e7) with ESMTP id zpeiaaaa for ; Sun, 13 Jun 1999 20:02:52 -0400 Message-ID: <003001beb5f9$9b10b480$65e684ce@sloth.yousehouse.org> From: "Chuck Youse" To: "Marc Ramirez" , Subject: Re: symlink question Date: Sun, 13 Jun 1999 20:05:23 -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 Forgive my ignorance, but what exactly is meant by a "variant link", and what might one be used for? Chuck Youse Director of Systems cyouse@cybersites.com -----Original Message----- From: Marc Ramirez To: hackers@FreeBSD.ORG Date: Sunday, June 13, 1999 1:12 PM Subject: symlink question > >Sorry if I'm bothering you busy folk unnecessarily... > >If I wanted to add variant symlinks, would that just require modifications >to namei, or is that way too simplistic? > >Thanks, >Marc. > >-- >Marc Ramirez - Owner Great Big Throbbing Brains >mrami@gbtb.com http://www.gbtb.com >Our brains throb, so yours won't have to! > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 17:10:12 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 4091A14FEE for ; Sun, 13 Jun 1999 17:10:10 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id UAA36390; Sun, 13 Jun 1999 20:10:15 -0400 (EDT) Date: Sun, 13 Jun 1999 20:10:14 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Joel Ray Holveck Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vn swapfiles deleted while in use In-Reply-To: <86vhcr3bav.fsf@detlev.UUCP> 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 13 Jun 1999, Joel Ray Holveck wrote: > What, to the reckoning of the resident populace, would happen if > somebody were to rm a vnconfig'd swapfile while it was in use? My reckoning is that the dirent would be deleted, and that's it. It would most likely go away when the system is restarted. Does it continue to work for you? > > Thanks, > 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 > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___/___/___/ " THAT'S WRONG WRONG WRONG!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 17:28:15 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 1B7CC14CD4 for ; Sun, 13 Jun 1999 17:28:11 -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 RAA53373; Sun, 13 Jun 1999 17:28:47 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: "Chuck Youse" Cc: "Marc Ramirez" , hackers@FreeBSD.ORG Subject: Variant symlinks [was Re: symlink question] In-reply-to: Your message of "Sun, 13 Jun 1999 20:05:23 EDT." <003001beb5f9$9b10b480$65e684ce@sloth.yousehouse.org> Date: Sun, 13 Jun 1999 17:28:47 -0700 Message-ID: <53369.929320127@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Forgive my ignorance, but what exactly is meant by a "variant link", and > what might one be used for? Gee, it's refreshing to see someone other than myself bringing this subject up. :) Variant symlinks, which many of us fell in love with back in our Apollo days, are essentially just symlinks with a level of variable expansion added in. E.g. back on the Apollo, you could do thinks like this: ln -s /usr/bin '/binaries/${ARCH}/bin' And have /usr/bin point to /binaries/i386/bin or /binaries/mips/bin depending on the user's $ARCH environment variable, ostensibly set by default by the shell but also user-modifiable with setenv. Many other things involving architecture, timezone or natural language neutrality are also obviously possible with this mechanism, this is just one example. The problem with doing this under FreeBSD always arises when one contemplates getting at the user's environment from the context of namei() - Apollo was able to see this problem coming and plan for it in advance, Unix did not and it's not quite so trivially contemplated here. ;) That, in turn, generally leads folks away from the environment and into a more sysctl-based (or other analogous) mechanism for setting symlink variables, that stage generally bogging down over the question of implementing user, group and system-wide variable spaces when all the VMS people jump into the discussion and make a good case for this. The current sysctl implementation assumes just one system-wide variable space. Good luck on this iteration, guys - that's all I can say. :-) It's a worthy feature, doing it truly correctly is simply hard. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 17:31:24 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 D4E0114C35 for ; Sun, 13 Jun 1999 17:31:22 -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 RAA53428; Sun, 13 Jun 1999 17:32:01 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Cc: "Chuck Youse" , "Marc Ramirez" , hackers@FreeBSD.ORG Subject: Re: Variant symlinks [was Re: symlink question] In-reply-to: Your message of "Sun, 13 Jun 1999 17:28:47 PDT." <53369.929320127@zippy.cdrom.com> Date: Sun, 13 Jun 1999 17:32:00 -0700 Message-ID: <53425.929320320@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And have /usr/bin point to /binaries/i386/bin or /binaries/mips/bin And before people jump on me, let me just clarify in advance that I was not meaning to imply that Apollo ever used the x86 architecture. They didn't. It was just an example. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 18:10:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Hydro.CAM.ORG (Hydro.CAM.ORG [198.168.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 7A06914BCD; Sun, 13 Jun 1999 18:10:31 -0700 (PDT) (envelope-from intmktg@CAM.ORG) Received: from Stratus.CAM.ORG (Stratus.CAM.ORG [198.168.100.6]) by Hydro.CAM.ORG (8.8.8/8.8.4) with ESMTP id VAA29585; Sun, 13 Jun 1999 21:10:11 -0400 (EDT) Date: Sun, 13 Jun 1999 21:10:29 -0400 (EDT) From: Marc Tardif To: freebsd-hackers@freebsd.org Cc: freebsd-questions@freebsd.org Subject: Fatal trap 12 on startup 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 While installing 2.2.8R (from a CD which I got from cheapbytes) on a 486DX2 66, w/ 16Mb RAM, I get: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA mono <16 virtual consoles, flags=0x0> > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xefc00000 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xf01eee33 > stack pointer = 0x10:0xefbffefc > frame pointer = 0x10:0xefbffefc > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pre 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 0 () > interrupt mask = net tty bio cam > panic: page fault >Automatic reboot in 15 seconds - press a key on the console to abort At this point, I tried a few options at the boot prompt, including: -cv to change any device which could be in conflict -g to try and debug -d also to debug -s just for the hell of it In all cases, I got the same message as above. I simply don't seem to have a chance to fix the problem as far as I can see. I've also searched the freebsd mailing list and handbook/faq, but couldn't find anything. Please suggest a few alternatives, I'd rather learn about this problem instead of going back to my previous release. Thanks in advance, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 13 23:59:42 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 5DEF614ED6 for ; Sun, 13 Jun 1999 23:59:40 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA06727; Sun, 13 Jun 1999 23:59:34 -0700 (PDT) (envelope-from dillon) Date: Sun, 13 Jun 1999 23:59:34 -0700 (PDT) From: Matthew Dillon Message-Id: <199906140659.XAA06727@apollo.backplane.com> To: David Greenman Cc: dyson@iquest.net, freebsd-hackers@FreeBSD.ORG Subject: Re: problem for the VM gurus References: <199906132321.QAA26382@implode.root.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> VM lookup the page again. Always. vm_fault already does this, :> in fact. We would clean up the code and document it to this effect. :> :> This change would allow us to immediately fix the self-referential :> deadlocks and I think it would also allow me to fix a similar bug :> in NFS trivially. : : I should point out here that the process of looking up the pages is a :significant amount of the overhead of the routines involved. Although :doing this for just one page is probably sufficiently in the noise as to :not be a concern. It would be for only one page and, besides, it *already* relooksup the page in vm_fault ( to see if the page was ripped out from under the caller ), so the overhead on the change would be very near zero. :> The easiest interim solution is to break write atomicy. That is, :> unlock the vnode if the backing store of the uio being written is :> (A) vnode-pager-backed and (B) not all in-core. : : Uh, I don't think you can safely do that. I thought one of the reasons :for locking a vnode for writes is so that the file metadata doesn't change :underneath you while the write is in progress, but perhaps I'm wrong about :that. : :-DG : :David Greenman The problem can be distilled into the fact that we currently hold an exclusive lock *through* a uiomove that might possibly incur read I/O due to pages not being entirely in core. The problem does *not* occur when we are blocked on meta-data I/O ( such as a BMAP operation ) since meta-data cannot be mmaped. Under current circumstances we already lose read atomicy on the source during the write(), but do not lose write() atomicy. The simple solution is to give up or downgrade the lock on the destination when blocked within the uiomove. We can pre-fault the first two pages of the uio to guarentee a minimum write atomicy I/O size. I suppose this could be extended to pre-faulting the first N pages of the uio, where N is chosen to be reasonably large - like 64K, but we could not guarentee arbitrary write atomicy because the user might decide to write a very large mmap'd buffer ( e.g. megabytes or gigabytes ) and obviously wiring that many pages just won't work. The more complex solution is to implement a separate range lock for I/O that is independant of the vnode lock. This solution would also require deadlock detection and restart handling. Atomicy would be maintained from the point of view of the processes running on the machine but not from the point of view of the physical storage. Since write atomicy is already not maintained from the point of view of the physical storage I don't think this would present a problem. Due to the complexity, however, it could not be used as an interim solution. It would have to be a permanent solution for the programming time to be worth it. Doing range-based deadlock detection and restart handling properly is not trivial. It is something that only databases usually need to do. -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 Jun 14 0: 1: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 6B4F814ED6 for ; Mon, 14 Jun 1999 00:01:28 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA06746; Mon, 14 Jun 1999 00:01:26 -0700 (PDT) (envelope-from dillon) Date: Mon, 14 Jun 1999 00:01:26 -0700 (PDT) From: Matthew Dillon Message-Id: <199906140701.AAA06746@apollo.backplane.com> To: Joel Ray Holveck Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vn swapfiles deleted while in use References: <86vhcr3bav.fsf@detlev.UUCP> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :What, to the reckoning of the resident populace, would happen if :somebody were to rm a vnconfig'd swapfile while it was in use? : :Thanks, :joelh The system still has a reference to the file, even deleted, so all you would be doing would be removing its directory entry. On the otherhand, if you *truncate* the file or unconfigure the vn node, you will blow the system up when the system tries to swap something in or out on that file. -Matt Matthew Dillon :-- :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 : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 0: 8:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cicero1.cybercity.dk (cicero1.cybercity.dk [212.242.40.4]) by hub.freebsd.org (Postfix) with ESMTP id A388314BD4 for ; Mon, 14 Jun 1999 00:08:28 -0700 (PDT) (envelope-from alex@hausse.dk) Received: from staff.cybercity.dk (staff.cybercity.dk [212.242.42.36]) by cicero1.cybercity.dk (8.8.8/8.8.7) with ESMTP id JAA29079 for ; Mon, 14 Jun 1999 09:07:00 +0200 (CEST) (envelope-from alex@hausse.dk) Received: from alexnt (nl210.cybercity.dk [212.242.42.210]) by staff.cybercity.dk (8.8.7/8.8.3) with SMTP id JAA18118 for ; Mon, 14 Jun 1999 09:06:59 +0200 (CEST) From: =?iso-8859-1?Q?Alex_Nordstr=F6m?= To: Date: Mon, 14 Jun 1999 09:04:02 +0200 Message-ID: <000001beb634$15a0d8d0$d22af2d4@cybercity.dk> 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 In-Reply-To: Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-hackers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 0:24:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id 6FB8115295 for ; Mon, 14 Jun 1999 00:24:14 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Mon, 14 Jun 1999 09:27:11 +0200 Message-ID: <55586E7391ACD211B9730000C1100276179664@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: 'Dag-Erling Smorgrav' , Brian Feldman Cc: hackers@FreeBSD.ORG Subject: RE: select(2) breakage Date: Mon, 14 Jun 1999 09:21:40 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Dag-Erling Smorgrav [SMTP:des@flood.ping.uio.no] > Sent: Sunday, June 13, 1999 6:02 PM > To: Brian Feldman > Cc: Dag-Erling Smorgrav; hackers@FreeBSD.ORG > Subject: Re: select(2) breakage > [ML] To the previous posters: the port ranges are limited so that the source sockets bound to any port do not clobber the (pseudo reserved) destination ports (e.g X server). You can still bind to a specific port in any range. This is the behavior since ages (and can be gleaned from the source; all other unices behave the same, they just don't let you adjust the ranges :) /Marino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 0:26: 9 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 8020E14A0B for ; Mon, 14 Jun 1999 00:26:07 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA06901; Mon, 14 Jun 1999 00:26:01 -0700 (PDT) (envelope-from dillon) Date: Mon, 14 Jun 1999 00:26:01 -0700 (PDT) From: Matthew Dillon Message-Id: <199906140726.AAA06901@apollo.backplane.com> To: David Greenman Cc: hgoldste@bbs.mpcs.com (Howard Goldstein), dyson@iquest.net, freebsd-hackers@FreeBSD.ORG, "John S. Dyson" Subject: Re: problem for the VM gurus References: <199906132030.NAA26102@implode.root.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> A permanent vnode locking fix is many months away because core :> decided to ask Kirk to fix it, which was news to me at the time. :> However, I agree with the idea of having Kirk fix VNode locking. : : Actually, core did no such thing. Kirk told me a month or so ago that he :intended to fix the vnode locking. Not that this is particularly important, :but people shouldn't get the idea that Kirk's involvement had anything to :do with core since it did not. : :-DG : :David Greenman Let me put it this way: You didn't bother to inform anyone else who might have reason to be interested until it came up as an offhand comment at USENIX. Perhaps you should consider not keeping such important events to yourself, eh? Frankly, I am rather miffed -- if I had known that Kirk had expressed an interest a month ago I would have been able to pool our interests earlier. Instead I've been working in a vacuum for a month because I didn't know that someone else was considering trying to solve the problem. This does not fill me with rosy feelings. -Matt Matthew Dillon :Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org :Creator of high-performance Internet servers - http://www.terasolutions.com : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 0:37:38 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 6866B15255 for ; Mon, 14 Jun 1999 00:37:36 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA07041; Mon, 14 Jun 1999 00:37:28 -0700 (PDT) (envelope-from dillon) Date: Mon, 14 Jun 1999 00:37:28 -0700 (PDT) From: Matthew Dillon Message-Id: <199906140737.AAA07041@apollo.backplane.com> To: Dan Moschuk Cc: hackers@FreeBSD.ORG Subject: Re: hundreds of sockets stuck in TIME_WAIT References: <19990609115951.A79834@trinsec.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I noticed on a very high traffic'd webserver, I have just over 4000 sockets :stuck in the TIME_WAIT state. Ideally, I want to "bend" the RFC a bit and :close the descriptor before it hits that state, or, ignore the 2MSL wait :when it enters that state. : :I take it there is no sysctl switch to trigger this, so, am I going :kernel diving? : :-Dan Just ignore them, that's what we do. They should not start to impact on performance until you hit at least 15000 sockets. -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 Jun 14 0:46:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id C9AEB14E2E for ; Mon, 14 Jun 1999 00:46:11 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Mon, 14 Jun 1999 09:49:09 +0200 Message-ID: <55586E7391ACD211B9730000C1100276179666@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: "'dyson@iquest.net'" , wes@softweyr.com Cc: crossd@cs.rpi.edu, freebsd-hackers@FreeBSD.ORG Subject: RE: High syscall overhead? Date: Mon, 14 Jun 1999 09:42:25 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: John S. Dyson [SMTP:dyson@iquest.net] > Sent: Saturday, June 12, 1999 6:58 PM > To: wes@softweyr.com > Cc: crossd@cs.rpi.edu; freebsd-hackers@FreeBSD.ORG > Subject: Re: High syscall overhead? > > Think of it like this: since alot of desktops sit in idle loops much > of the time, perhaps the Linux philosophy has been to improve such > behavior :-). > [ML] Do you remember the old anecdote about a profiled ATT unix kernel where they have found out that the kernel spends a lot of time in one loop and rewritten it in assembly--it turned out it was the IDLE loop :) /Marino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 1:28:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id 2F8F714E0D for ; Mon, 14 Jun 1999 01:28:53 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Mon, 14 Jun 1999 10:31:48 +0200 Message-ID: <55586E7391ACD211B9730000C1100276179667@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: "'Jordan K. Hubbard'" Cc: Chuck Youse , Marc Ramirez , hackers@FreeBSD.ORG Subject: RE: Variant symlinks [was Re: symlink question] Date: Mon, 14 Jun 1999 10:26:17 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Jordan K. Hubbard [SMTP:jkh@zippy.cdrom.com] > Sent: Monday, June 14, 1999 2:32 AM > Cc: Chuck Youse; Marc Ramirez; hackers@FreeBSD.ORG > Subject: Re: Variant symlinks [was Re: symlink question] > > > And have /usr/bin point to /binaries/i386/bin or /binaries/mips/bin > > And before people jump on me, let me just clarify in advance that I > was not meaning to imply that Apollo ever used the x86 architecture. > They didn't. It was just an example. :) [ML] My last Apollo (with an HP badge on it) was an MC 68040 with a whopping 16 Megs of RAM and 1 Gig of disk. It was running DomainOS, though :) Believe me, it was an improvement over MicrovaxII running Ultrix. Ah, the olden days... /Marino > - Jordan > > > 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 Jun 14 2:31:42 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 9FDE414D70 for ; Mon, 14 Jun 1999 02:31:40 -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 LAA60869; Mon, 14 Jun 1999 11:31:33 +0200 (CEST) (envelope-from des) To: Matthew Dillon Cc: Joel Ray Holveck , freebsd-hackers@FreeBSD.ORG Subject: Re: vn swapfiles deleted while in use References: <86vhcr3bav.fsf@detlev.UUCP> <199906140701.AAA06746@apollo.backplane.com> From: Dag-Erling Smorgrav Date: 14 Jun 1999 11:31:32 +0200 In-Reply-To: Matthew Dillon's message of "Mon, 14 Jun 1999 00:01:26 -0700 (PDT)" Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > On the otherhand, if you *truncate* the file or unconfigure the > vn node, you will blow the system up when the system tries > to swap something in or out on that file. Is there any possibility of adding a reference count to the vn device so it can't be unconfigured if it's still referenced? Is there any possibility of implementing a compulsory (as opposed to advisory) file locking system, so vn swapfiles can't be truncated or written to by any other process while it's in use? 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 Jun 14 2:40:22 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 9FA7714EDE for ; Mon, 14 Jun 1999 02:40:16 -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 LAA61124; Mon, 14 Jun 1999 11:39:59 +0200 (CEST) (envelope-from des) To: Matthew Dillon Cc: David Greenman , hgoldste@bbs.mpcs.com (Howard Goldstein), dyson@iquest.net, freebsd-hackers@FreeBSD.ORG, "John S. Dyson" , perhaps@yes.no Subject: Re: problem for the VM gurus References: <199906132030.NAA26102@implode.root.com> <199906140726.AAA06901@apollo.backplane.com> From: Dag-Erling Smorgrav Date: 14 Jun 1999 11:39:59 +0200 In-Reply-To: Matthew Dillon's message of "Mon, 14 Jun 1999 00:26:01 -0700 (PDT)" Message-ID: Lines: 30 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > :> A permanent vnode locking fix is many months away because core > :> decided to ask Kirk to fix it, which was news to me at the time. > :> However, I agree with the idea of having Kirk fix VNode locking. > : > : Actually, core did no such thing. Kirk told me a month or so ago that he > :intended to fix the vnode locking. Not that this is particularly important, > :but people shouldn't get the idea that Kirk's involvement had anything to > :do with core since it did not. > > Let me put it this way: You didn't bother to inform anyone else who > might have reason to be interested until it came up as an offhand > comment at USENIX. Perhaps you should consider not keeping such important > events to yourself, eh? Frankly, I am rather miffed -- if I had known > that Kirk had expressed an interest a month ago I would have been able > to pool our interests earlier. Instead I've been working in a vacuum > for a month because I didn't know that someone else was considering trying > to solve the problem. This does not fill me with rosy feelings. Eivind Eklund has also been working on this. It is my understanding that he has a working Perl version of vnode_if.sh, and is about halfway through adding invariants to the locking code to track down locking errors. He stopped working on it about a month or two ago for lack of time; I seem to recall that he had managed to get the kernel to boot and was working on panics (from violated invariants) which occurred during fsck. 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 Jun 14 3:48: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from servo.ccr.org (servo.ccr.org [198.3.0.2]) by hub.freebsd.org (Postfix) with ESMTP id 0CDC614DB1 for ; Mon, 14 Jun 1999 03:47:58 -0700 (PDT) (envelope-from mo@servo.ccr.org) Received: (from mo@localhost) by servo.ccr.org (8.9.2/8.9.2) id GAA57400 for hackers@freebsd.org; Mon, 14 Jun 1999 06:47:58 -0400 (EDT) (envelope-from mo) Date: Mon, 14 Jun 1999 06:47:58 -0400 (EDT) From: "Mike O'Dell" Message-Id: <199906141047.GAA57400@servo.ccr.org> To: hackers@freebsd.org Subject: coarse vs fine-grained locking in SMP systems Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG very fine-grain-locked systems often display convoying and are prone to priority inversion problems. coarse-grained systems exhibit all the granularity problems already described. (the first purdue dual-vax system plowed most of that ground) we published the best Unix SMP paper I've ever seen in Computing Systems - from the Amdahl guys who did an SMP version of the kernel by very clever hacks on SPLx() macros to make them spin locks and a bit of other clever trickery on the source. they could take a stock kernel and SMP everything but the device drivers essentially with a SED script. most interesting, they benchmarked it against their laboriously reworked fine-grained kernel and under heavy multiprogramming loads it performed better than the fine-grain kernel and essentially never did materially worse. and with *many* fewer man-years of hacking. it might be worth digging out that paper for a looky. sorry i don't have the citation off the top of my head, but i think the Usenix online index would have it. -mo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 5:34:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from itsdsv1.enc.edu (fw1.enc.edu [207.95.42.127]) by hub.freebsd.org (Postfix) with ESMTP id 73C3714C18 for ; Mon, 14 Jun 1999 05:34:19 -0700 (PDT) (envelope-from owensc@enc.edu) Received: from enc.edu (r2s1.r.its.enc.edu [10.100.0.21]) by itsdsv1.enc.edu (8.7.5/8.7.3) with ESMTP id IAA03903; Mon, 14 Jun 1999 08:24:37 -0400 (EDT) Message-ID: <3764F7EA.2C8AEACD@enc.edu> Date: Mon, 14 Jun 1999 08:39:06 -0400 From: Charles Owens Organization: Eastern Nazarene College X-Mailer: Mozilla 4.51 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: kernel@tdnet.com.br, hackers@freebsd.org Subject: Re: quota crash my system, how to fix it ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Unknow User said: > Quota crash my system after quotaoff followed by quotaon! > I applied a patch (kern/8137), but it did not work! > Can anybody explain how could i fix this problem. > here goes the patch i applied: [ patch deleted ] I believe the currently accepted solution is to simply never turn the quota system off and on. I've seen this conventional wisdom repeated here on this list and it certainly holds true within my experience. I enable the quota system at at boot time (with quotaon) and then never turn it off. Maybe four years back someone suggested strongly that edquota should not be used with the quota system running (I forget his exact argument). Following this advice I changed my user management scripts to call quotaoff and quotaon at the appropriate times. Doing so caused a crash and reboot a few minutes after these scripts would be run, almost every time. I went back to the previous version of my scripts and stabilty returned. YMMV, of course. -- --- ------------------------------------------------------------------------- Charles N. Owens Email: owensc@enc.edu http://www.enc.edu/~owensc Network & Systems Administrator Information Technology Services "Outside of a dog, a book is a man's Eastern Nazarene College best friend. Inside of a dog it's too dark to read." - Groucho Marx ------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 5:59:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from detlev.UUCP (tex-63.camalott.com [208.229.74.63]) by hub.freebsd.org (Postfix) with ESMTP id EFD58152DD for ; Mon, 14 Jun 1999 05:59:34 -0700 (PDT) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.3) id HAA11950; Mon, 14 Jun 1999 07:59:53 -0500 (CDT) (envelope-from joelh) To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vn swapfiles deleted while in use References: <86vhcr3bav.fsf@detlev.UUCP> <199906140701.AAA06746@apollo.backplane.com> From: Joel Ray Holveck Date: 14 Jun 1999 07:59:50 -0500 In-Reply-To: Matthew Dillon's message of "Mon, 14 Jun 1999 00:01:26 -0700 (PDT)" Message-ID: <861zff2b08.fsf@detlev.UUCP> Lines: 17 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> What, to the reckoning of the resident populace, would happen if >> somebody were to rm a vnconfig'd swapfile while it was in use? > The system still has a reference to the file, even deleted, > so all you would be doing would be removing its directory > entry. And what happens when the system is shut down? Would everything happen nicely then? Thanks, 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 Mon Jun 14 6: 6:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from star1.iwl.net (star1.iwl.net [206.136.182.130]) by hub.freebsd.org (Postfix) with ESMTP id A576E152DB for ; Mon, 14 Jun 1999 06:06:49 -0700 (PDT) (envelope-from star@iwl.net) Received: (from root@localhost) by star1.iwl.net (8.8.8/8.8.4) id IAA12874; Mon, 14 Jun 1999 08:06:14 -0500 (CDT) Date: Mon, 14 Jun 1999 08:06:14 -0500 (CDT) From: star@iwl.net Message-Id: <199906141306.IAA12874@star1.iwl.net> To: hackers@FreeBSD.ORG Subject: NAT Gateway to multiple ISPs Reply-To: star@iwl.net X-Mailer: [XMailTool v3.1.2b] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Any ideas on the following ? I am setting up a home/office network with NAT filtering gateway on a dual-NIC FreeBSD 3.2 box. No problem so far - I've set up several like this on 2.2.8 using natd. The new wrinkle is this: I need to connect to two ISPs (DSL & Cable Modem), ideally with automatic failover and load balancing when multiple internal PC's are generating internet traffic. I know that this requires running gated (or routed) to receive RIP or OSPF messages from the ISPs, and to select the best outgoing ISP's route. The key question is: while the routing program probably requires a third NIC so that each external link has its own device, how can natd handle multiple external internet interfaces. I've been searching in several directions: 1) Using "ifconfig alias" option to map the two external addresses assigned by the two ISPs into the same NIC - would seem to confuse the routing of outgoing traffic, although I have 'aliased' reliably on a fbsd web server (all in the same subnet) and have also seen multiple subnets peacefully coexist on the same physical network. 2) Somehow get natd or another NAT server to recognise two outgoing interfaces - this would also seem to confuse the functioning of the routing program. 3) Configure an internal pseudo-device (tun ?) or divert interface between natd (and the internal NIC) on the inside and gated or routed (and the two external NICS) on the outside. This way, natd and the routing program would be completely isolated and wouldn't need to know that the other existed. ISP1 - NIC1 \ gated - TUN - natd - NIC3 - internal net / device ISP2 - NIC2 The third seems the best choice, but I haven't seen any discription of this type of configuration. Any advice ? Thanks very much for your help, Andy Starratt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 6:33: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from argus.tfs.net (as1-p71.tfs.net [139.146.210.71]) by hub.freebsd.org (Postfix) with ESMTP id B6CBB15266 for ; Mon, 14 Jun 1999 06:32:56 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id IAA61298; Mon, 14 Jun 1999 08:32:38 -0500 (CDT) From: Jim Bryant Message-Id: <199906141332.IAA61298@argus.tfs.net> Subject: Re: coarse vs fine-grained locking in SMP systems In-Reply-To: <199906141047.GAA57400@servo.ccr.org> from Mike O'Dell at "Jun 14, 99 06:47:58 am" To: mo@servo.ccr.org (Mike O'Dell) Date: Mon, 14 Jun 1999 08:32:37 -0500 (CDT) Cc: freebsd-hackers@freebsd.org Reply-To: jbryant@unix.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: > very fine-grain-locked systems often display convoying and > are prone to priority inversion problems. coarse-grained > systems exhibit all the granularity problems already described. > (the first purdue dual-vax system plowed most of that ground) Was this a VAX 11/782 or a later machine? 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 Mon Jun 14 8:57:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from server.ghostgbtb.com (modem13.tekrab.net [208.30.20.213]) by hub.freebsd.org (Postfix) with ESMTP id 6D83015275 for ; Mon, 14 Jun 1999 08:57:42 -0700 (PDT) (envelope-from mrami@gbtb.com) Received: from localhost (mrami@localhost) by server.ghostgbtb.com (8.9.2/8.9.2) with SMTP id LAA02905; Mon, 14 Jun 1999 11:57:31 -0400 (EDT) (envelope-from mrami@gbtb.com) X-Authentication-Warning: server.ghostgbtb.com: mrami owned process doing -bs Date: Mon, 14 Jun 1999 11:57:31 -0400 (EDT) From: Marc Ramirez X-Sender: mrami@server.ghostgbtb.com To: Chuck Youse Cc: hackers@FreeBSD.ORG Subject: Re: symlink question In-Reply-To: <003001beb5f9$9b10b480$65e684ce@sloth.yousehouse.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, 13 Jun 1999, Chuck Youse wrote: > Forgive my ignorance, but what exactly is meant by a "variant link", and > what might one be used for? In my fantasy world, a variant symlink is kind of a way of putting a search path into a symbolic link, so that if you had an environment variable E=a:b:c, and you had a symbolic link created with ln -s /some/where/\${E}/foo bar when you execute a command like more bar/baz.txt it would look for /some/where/a/foo/bax.txt, then /some/where/b/foo/baz.txt, then /some/where/c/foo/baz.txt. It's akin to what the unionfs tries to do, but it doesn't care about creating total transparency, and it doesn't mask directories, and changes to one process's search order don't affect other process's search orders, so you don't have to do all those machinations with loopback mounts and things like that. It's much more along the lines of VMS's logicals, if yoy know of those. As for uses, in my fantasy world, I personally would be using it for system testing where I have a rather large base system which gets modified per customer. "export CUSTOMER=foo; gosystem" would be so nice... Marc. > > Chuck Youse > Director of Systems > cyouse@cybersites.com > > -----Original Message----- > From: Marc Ramirez > To: hackers@FreeBSD.ORG > Date: Sunday, June 13, 1999 1:12 PM > Subject: symlink question > > > > > >Sorry if I'm bothering you busy folk unnecessarily... > > > >If I wanted to add variant symlinks, would that just require modifications > >to namei, or is that way too simplistic? > > > >Thanks, > >Marc. > > > >-- > >Marc Ramirez - Owner Great Big Throbbing Brains > >mrami@gbtb.com http://www.gbtb.com > >Our brains throb, so yours won't have to! > > > > > > > >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 > -- Marc Ramirez - Owner Great Big Throbbing Brains mrami@gbtb.com http://www.gbtb.com Our brains throb, so yours won't have to! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 9: 3:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from server.ghostgbtb.com (modem13.tekrab.net [208.30.20.213]) by hub.freebsd.org (Postfix) with ESMTP id 2ECEA14F31 for ; Mon, 14 Jun 1999 09:03:13 -0700 (PDT) (envelope-from mrami@gbtb.com) Received: from localhost (mrami@localhost) by server.ghostgbtb.com (8.9.2/8.9.2) with SMTP id MAA02940; Mon, 14 Jun 1999 12:03:07 -0400 (EDT) (envelope-from mrami@gbtb.com) X-Authentication-Warning: server.ghostgbtb.com: mrami owned process doing -bs Date: Mon, 14 Jun 1999 12:03:07 -0400 (EDT) From: Marc Ramirez X-Sender: mrami@server.ghostgbtb.com To: "Jordan K. Hubbard" Cc: hackers@FreeBSD.ORG Subject: Re: Variant symlinks [was Re: symlink question] In-Reply-To: <53369.929320127@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 Sun, 13 Jun 1999, Jordan K. Hubbard wrote: > > Forgive my ignorance, but what exactly is meant by a "variant link", and > > what might one be used for? > > Gee, it's refreshing to see someone other than myself bringing this > subject up. :) Well, I'd like to add versioning, too, but _that's_ hard! :) Marc. -- Marc Ramirez - Owner Great Big Throbbing Brains mrami@gbtb.com http://www.gbtb.com Our brains throb, so yours won't have to! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 9: 6:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id 7763B14D7E for ; Mon, 14 Jun 1999 09:06:09 -0700 (PDT) (envelope-from roger@cs.strath.ac.uk) Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id RAA09003 Mon, 14 Jun 1999 17:06:07 +0100 (BST) Message-ID: <3765286D.167E@cs.strath.ac.uk> Date: Mon, 14 Jun 1999 17:06:06 +0100 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: hackers@freebsd.org Subject: do softupdates work on SMP -stable and -current now? 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 remember reading in the mailing lists how softupdates were unreliable on SMP 3.x and -current machines about 6-8 months ago. Is this all fixed now for SMP machines? I've been using softupdates on a uni-processor 3.2-stable machine and it works well. I wanted to try it on my two SMP machines (one has 3.2-stable, one has -current) Bye Roger -- Roger Hardiman | Telepresence Research Group roger@cs.strath.ac.uk | DMEM, University of Strathclyde tel: 0141 548 2897 | Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557 | http://telepresence.dmem.strath.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 9:13: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 D30C114BE3 for ; Mon, 14 Jun 1999 09:13:55 -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 MAA13000; Mon, 14 Jun 1999 12:12:42 -0400 (EDT) Message-Id: <199906141612.MAA13000@cs.rpi.edu> To: Roger Hardiman Cc: hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: do softupdates work on SMP -stable and -current now? In-Reply-To: Message from Roger Hardiman of "Mon, 14 Jun 1999 17:06:06 BST." <3765286D.167E@cs.strath.ac.uk> Date: Mon, 14 Jun 1999 12:12:42 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I certainly hope they are working under SMP.... I am running a 4-way Pentium-III xeon box using vinum and softupdates. so far it has been a champ. -- 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 Jun 14 9:17:45 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 0503514A12 for ; Mon, 14 Jun 1999 09:17:35 -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 QAA38235; Mon, 14 Jun 1999 16:17:28 GMT Message-ID: <37652A92.D4AD4014@tdx.co.uk> Date: Mon, 14 Jun 1999 17:15:14 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Roger Hardiman Cc: hackers@FreeBSD.ORG Subject: Re: do softupdates work on SMP -stable and -current now? References: <3765286D.167E@cs.strath.ac.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Roger Hardiman wrote: > Hi, > I remember reading in the mailing lists how softupdates > were unreliable on SMP 3.x and -current machines about 6-8 months > ago. > > Is this all fixed now for SMP machines? > > I've been using softupdates on a uni-processor 3.2-stable machine > and it works well. I wanted to try it on my two > SMP machines (one has 3.2-stable, one has -current) We have a couple of large(ish) systems (both dual P2/Pro's) running Vinum and softupdates, and I've not seen any problems... One was up until recently 3.1, there both 4.0-current now... -Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 9:22:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id 8BD1214DC7 for ; Mon, 14 Jun 1999 09:22:08 -0700 (PDT) (envelope-from roger@cs.strath.ac.uk) Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id RAA09322 Mon, 14 Jun 1999 17:22:06 +0100 (BST) Message-ID: <37652C2D.15FB@cs.strath.ac.uk> Date: Mon, 14 Jun 1999 17:22:05 +0100 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: do softupdates work on SMP -stable and -current now? References: <199906141612.MAA13000@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 Well, following up to my own post, 3 people have reported no problems with softupdates on their SMP machines. One was softupdates only 2 were softupdates and vimun together. Thanks for everyones prompt replies. Right, back to those PicoBSD commits. Bye Roger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 9:47:27 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 B3C6D14DFE for ; Mon, 14 Jun 1999 09:47:25 -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 MAA13655 for ; Mon, 14 Jun 1999 12:47:24 -0400 (EDT) Message-Id: <199906141647.MAA13655@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: 3.2-STABLE panic #17 (NFS -- additional informatio) Date: Mon, 14 Jun 1999 12:47:24 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, now that I have hopefully gotten the criticial people's attention, I will proceed with the details: 1: My test program can only reproduce this with NFSv3/UDP from a recently patched Solaris system to a FreeBSD server. I have not tested older Solaris patches, I suspect that they will not cause the panic. 2: Recent packet traces of the NFS traffic reveals that it is likely *NOT* unlink that is causing the problem. I now have 6 packet traces and all fail within a couple of packets of the NFS server responding to a create request with "ERROR: File exists" (that is TCPDUMP terminoligy). Looking through the create call, I think I can see it, but it is tough. 2a: only ever *one* "ERROR: File exists" has ever been seen per a single crash. 3: Based on #1 and #2 I can surmise that other OSs will eventually trip this, but the access pattern is sufficiently different that my test program will not do it. 4: It is not a concurancy issue as far as I can tell. I wrapped all of nfssrv_create() (or whatever it is called) in a spl_softclock(), splx() pairing and I could still cause the panic. 5: I tried compiling with "MAX_PERF" which in effect comments out the panic, this caused all access to the directory to result in (D)iskwait, with WCHAN of "inode". Effectively bringing the NFS server down, but without the advantage of having the machine come back by itself. I am still digging arround, but this is significantly above my head. It is great fun, and I wouldn't mind continuing except this is becoming a difficult issue. We have backed everything down to NFSv2, but existing mounts are difficult to get rid of. -- 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 Jun 14 9:58: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles532.castles.com [208.214.165.96]) by hub.freebsd.org (Postfix) with ESMTP id 335E515266 for ; Mon, 14 Jun 1999 09:58:02 -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 JAA03010; Mon, 14 Jun 1999 09:53:23 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199906141653.JAA03010@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "David E. Cross" Cc: freebsd-hackers@freebsd.org Subject: Re: 3.2-STABLE panic #17 (NFS -- additional informatio) In-reply-to: Your message of "Mon, 14 Jun 1999 12:47:24 EDT." <199906141647.MAA13655@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Jun 1999 09:53:23 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am still digging arround, but this is significantly above my head. It is > great fun, and I wouldn't mind continuing except this is becoming a difficult > issue. We have backed everything down to NFSv2, but existing mounts are > difficult to get rid of. It's a difficult issue no matter who you are, and you seem to be in the ideal situation; you have the ability to reproduce the problem, motivation to fix it, you appear to have enough clue to understand what's going on, and you're enjoying it. I'd have to say you're the perfect guy for the problem. And thanks for pursuing it this far already! -- \\ 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 Jun 14 11: 3: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 1FD2E1522E for ; Mon, 14 Jun 1999 11:03:30 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA11413; Mon, 14 Jun 1999 11:03:27 -0700 (PDT) (envelope-from dillon) Date: Mon, 14 Jun 1999 11:03:27 -0700 (PDT) From: Matthew Dillon Message-Id: <199906141803.LAA11413@apollo.backplane.com> To: Dag-Erling Smorgrav Cc: Joel Ray Holveck , freebsd-hackers@FreeBSD.ORG Subject: Re: vn swapfiles deleted while in use References: <86vhcr3bav.fsf@detlev.UUCP> <199906140701.AAA06746@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> vn node, you will blow the system up when the system tries :> to swap something in or out on that file. : :Is there any possibility of adding a reference count to the vn device :so it can't be unconfigured if it's still referenced? : :Is there any possibility of implementing a compulsory (as opposed to :advisory) file locking system, so vn swapfiles can't be truncated or :written to by any other process while it's in use? : :DES Sure. We could probably do the same thing we do for active binaries. It's pretty low on my list, though. -Matt Matthew Dillon :-- :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 : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 12: 0:12 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 690D514D23 for ; Mon, 14 Jun 1999 12:00: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 LAA27270; Mon, 14 Jun 1999 11:58:50 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id LAA05627; Mon, 14 Jun 1999 11:58:50 -0700 Received: from softweyr.com (dyn0.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA09168; Mon, 14 Jun 99 11:58:12 PDT Message-Id: <376550BF.CF584A8@softweyr.com> Date: Mon, 14 Jun 1999 12:58:07 -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: Chuck Youse Cc: Marc Ramirez , hackers@FreeBSD.ORG Subject: Re: symlink question References: <003001beb5f9$9b10b480$65e684ce@sloth.yousehouse.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Youse wrote: > > Forgive my ignorance, but what exactly is meant by a "variant link", and > what might one be used for? A symlink that has a variable name embedded in it. It can be quite useful at times; consider a symlink such as: /usr/local/bin/bash -> /usr/local/{karch}/bin/bash, where {karch} can be automagically expanded into i.e. i386-FreeBSD3.1 or sparc-NetBSD1.4 or hppa-hpux10. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr 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 Jun 14 12:59: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 34F4E155E9 for ; Mon, 14 Jun 1999 12:58:57 -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 PAA17232 for ; Mon, 14 Jun 1999 15:58:56 -0400 (EDT) Message-Id: <199906141958.PAA17232@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: 3.2-STABLE, panic #end. Problem found.. Date: Mon, 14 Jun 1999 15:58:56 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think I found the problem, and I have a pseudo-fix... (the machine nolonger crashes). This is a bleeding edge development, I have not had time to refine this code any. The problem is that nfs_create for NFSv3 does not release the lock for "vp" with a vput() before it exits. My crude "patch" follows (read "hacked, with an axe"). -- 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 Jun 14 13: 7:10 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 EDF4815568 for ; Mon, 14 Jun 1999 13:07:07 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from wobble.cs.rpi.edu (wobble.cs.rpi.edu [128.213.8.1]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA17424; Mon, 14 Jun 1999 16:07:03 -0400 (EDT) From: "David E. Cross" Received: (from crossd@localhost) by wobble.cs.rpi.edu (8.9.3/8.9.2) id QAA62362; Mon, 14 Jun 1999 16:07:03 -0400 (EDT) Date: Mon, 14 Jun 1999 16:07:03 -0400 (EDT) Message-Id: <199906142007.QAA62362@wobble.cs.rpi.edu> To: crossd@cs.rpi.edu, freebsd-hackers@freebsd.org, schimken@cs.rpi.edu Subject: oops, here's the patch Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG *** nfs_serv.c Tue Jun 8 15:53:11 1999 --- /cs/crossd/nfs_serv.c Mon Jun 14 16:05:45 1999 *************** *** 1343,1348 **** --- 1343,1349 ---- fhandle_t *fhp; u_quad_t frev, tempsize; u_char cverf[NFSX_V3CREATEVERF]; + int eexistdebug=0; #ifndef nolint rdev = 0; *************** *** 1380,1385 **** --- 1381,1387 ---- case NFSV3CREATE_GUARDED: if (nd.ni_vp) { error = EEXIST; + eexistdebug=1; break; } case NFSV3CREATE_UNCHECKED: *************** *** 1489,1497 **** vrele(nd.ni_startdir); zfree(namei_zone, nd.ni_cnd.cn_pnbuf); vp = nd.ni_vp; ! if (nd.ni_dvp == vp) vrele(nd.ni_dvp); ! else vput(nd.ni_dvp); VOP_ABORTOP(nd.ni_dvp, &nd.ni_cnd); if (vap->va_size != -1) { --- 1491,1499 ---- vrele(nd.ni_startdir); zfree(namei_zone, nd.ni_cnd.cn_pnbuf); vp = nd.ni_vp; ! if (nd.ni_dvp == vp) vrele(nd.ni_dvp); ! else vput(nd.ni_dvp); VOP_ABORTOP(nd.ni_dvp, &nd.ni_cnd); if (vap->va_size != -1) { *************** *** 1505,1513 **** error = VOP_SETATTR(vp, vap, cred, procp); } ! if (error) vput(vp); } } if (!error) { bzero((caddr_t)fhp, sizeof(nfh)); --- 1507,1516 ---- error = VOP_SETATTR(vp, vap, cred, procp); } ! if (error) vput(vp); } + if (eexistdebug) vput(vp); } if (!error) { bzero((caddr_t)fhp, sizeof(nfh)); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 13:53:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.249.195.3]) by hub.freebsd.org (Postfix) with ESMTP id 33B8D15168 for ; Mon, 14 Jun 1999 13:53:00 -0700 (PDT) (envelope-from paulo@nlink.com.br) Received: from localhost (paulo@localhost) by mirage.nlink.com.br (8.9.3/8.9.1) with SMTP id RAA22168 for ; Mon, 14 Jun 1999 17:52:55 -0300 (EST) Date: Mon, 14 Jun 1999 17:52:55 -0300 (EST) From: Paulo Fragoso To: freebsd-hackers@freebsd.org Subject: pppd + pam + radius (3) [getting crazy] 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, I've solved (I think) modules auth failures in pppd using PAM (compiled with -DUSE_PAM). It's work after one modification: --- ../pppd-orig/auth.c Sat Jun 20 15:02:08 1998 +++ auth.c Mon Jun 14 17:42:16 1999 @@ -867,7 +867,6 @@ */ pam_error = pam_authenticate (pamh, PAM_SILENT); if (pam_error == PAM_SUCCESS) { - pam_error = pam_acct_mgmt (pamh, PAM_SILENT); /* start a session for this user. Session closed when link ends. */ if (pam_error == PAM_SUCCESS) Now I can log in my system authenticating via radius on another machine. I'm using radiusd-cistron-1.5.4.3 but this server isn't working fine. My radlast is empty. Why is happening? What the best version of radiusd to use? Please!!!, can anyone help me? I getting crazy :-) Paulo. ------ " ... Overall we've found FreeBSD to excel in performace, stability, technical support, and of course price. Two years after discovering FreeBSD, we have yet to find a reason why we switch to anything else" -David Filo, Yahoo! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 14:13:50 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 20757153E9 for ; Mon, 14 Jun 1999 14:13:40 -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 RAA20328 for ; Mon, 14 Jun 1999 17:13:39 -0400 (EDT) Message-Id: <199906142113.RAA20328@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: umapfs... Date: Mon, 14 Jun 1999 17:13:38 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been looking at the code for UMAPfs... I am trying to understand conceptually why it is so unstable... It looks straightforward enough as simply passing the calls it receives on to the FS below it, almost like it didn't exist at all. Why does this cause problems? Isn't the only difference between a UMAP/UNION FS and a "native" FS an additional stack frame in the kernel? (As I am starting to wrap up this FS adventure, I am looking to start another:) -- 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 Jun 14 14:35:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from servo.ccr.org (servo.ccr.org [198.3.0.2]) by hub.freebsd.org (Postfix) with ESMTP id B4A15155EC for ; Mon, 14 Jun 1999 14:35:30 -0700 (PDT) (envelope-from mo@servo.ccr.org) Received: from servo.ccr.org (localhost [127.0.0.1]) by servo.ccr.org (8.9.2/8.9.2) with ESMTP id RAA58095; Mon, 14 Jun 1999 17:35:26 -0400 (EDT) (envelope-from mo@servo.ccr.org) Message-Id: <199906142135.RAA58095@servo.ccr.org> To: jbryant@unix.tfs.net Cc: freebsd-hackers@freebsd.org Subject: Re: coarse vs fine-grained locking in SMP systems In-reply-to: Your message of "Mon, 14 Jun 1999 08:32:37 CDT." <199906141332.IAA61298@argus.tfs.net> Date: Mon, 14 Jun 1999 17:35:26 -0400 From: "Mike O'Dell" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG it was on a Purdue Dual Vax 11/780 much later DEC sold the 782 which was a commercially produced version of the Purdue Dual VAX 11/780 which was built from one machine and a bunch of "spares". George Goble produced the parts list to order from DEC Spares to build your own. several got built. -mo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 16:50: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 D34B914CB4 for ; Mon, 14 Jun 1999 16:50:28 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA12993; Mon, 14 Jun 1999 16:50:26 -0700 (PDT) (envelope-from dillon) Date: Mon, 14 Jun 1999 16:50:26 -0700 (PDT) From: Matthew Dillon Message-Id: <199906142350.QAA12993@apollo.backplane.com> To: "David E. Cross" Cc: crossd@cs.rpi.edu, freebsd-hackers@FreeBSD.ORG, schimken@cs.rpi.edu Subject: Re: oops, here's the patch References: <199906142007.QAA62362@wobble.cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh man that routine is complex! I'm looking at it closely and I think you are right, except I think you may have introduced a minor bug in fixing the other bug. Here is the code and the last bit of your modification for reference: if (vap->va_size != -1) { error = nfsrv_access(vp, VWRITE, cred, (nd.ni_cnd.cn_flags & RDONLY), procp, 0); if (!error) { nqsrv_getl(vp, ND_WRITE); tempsize = vap->va_size; VATTR_NULL(vap); vap->va_size = tempsize; error = VOP_SETATTR(vp, vap, cred, procp); } if (error) vput(vp); } if (eexistdebug) vput(vp); <<<<<<<<< your addition However, if the inside of the first conditional generates an error, the vp may be vput twice. What I recommend is this for the last bit: if (vap->va_size != -1) { ... if (error) { vput(vp); vp = NULL; <<<<<<< my addition } } if (eexistdebug && vp) <<<<<<< also check vp != NULL vput(vp); It would be good if someone else could look over this routine and double-check David's find and his solution with my modification. Have we handled all the cases? David, this is a great bug find! -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 Jun 14 16:55:14 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 78E701500B for ; Mon, 14 Jun 1999 16:55:11 -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 QAA01486; Mon, 14 Jun 1999 16:54:30 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id QAA17633; Mon, 14 Jun 1999 16:54:30 -0700 Received: from softweyr.com (dyn0.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA25002; Mon, 14 Jun 99 16:54:13 PDT Message-Id: <37659624.3A6B8F9C@softweyr.com> Date: Mon, 14 Jun 1999 17:54: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: star@iwl.net Cc: hackers@FreeBSD.ORG Subject: Re: NAT Gateway to multiple ISPs References: <199906141306.IAA12874@star1.iwl.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG star@iwl.net wrote: > > Any ideas on the following ? > > I am setting up a home/office network with NAT filtering gateway > on a dual-NIC FreeBSD 3.2 box. No problem so far - I've set > up several like this on 2.2.8 using natd. > > The new wrinkle is this: I need to connect to two ISPs > (DSL & Cable Modem), ideally with automatic failover and > load balancing when multiple internal PC's are generating > internet traffic. > > I know that this requires running gated (or routed) to > receive RIP or OSPF messages from the ISPs, and to select the > best outgoing ISP's route. > > The key question is: while the routing program probably > requires a third NIC so that each external link has its own > device, how can natd handle multiple external internet > interfaces. You could certainly (and easily) do it with *two* FreeBSD boxes: +----------+ +----------+ Cable -->| Router | | Firewall | | Gated+ |<---->| natd+ |<-- internal network DSL -->| FreeBSD | | FreeBSD | +----------+ +----------+ I'm not sure it is possible to virtualize the connection between the "router" and "firewall" above. Perhaps with a clever (ab)use of the bridging code. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr 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 Jun 14 16:58:53 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 D839815026 for ; Mon, 14 Jun 1999 16:58:51 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA13101; Mon, 14 Jun 1999 16:58:49 -0700 (PDT) (envelope-from dillon) Date: Mon, 14 Jun 1999 16:58:49 -0700 (PDT) From: Matthew Dillon Message-Id: <199906142358.QAA13101@apollo.backplane.com> To: Joel Ray Holveck Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vn swapfiles deleted while in use References: <86vhcr3bav.fsf@detlev.UUCP> <199906140701.AAA06746@apollo.backplane.com> <861zff2b08.fsf@detlev.UUCP> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :>> What, to the reckoning of the resident populace, would happen if :>> somebody were to rm a vnconfig'd swapfile while it was in use? :> The system still has a reference to the file, even deleted, :> so all you would be doing would be removing its directory :> entry. : :And what happens when the system is shut down? Would everything :happen nicely then? : :Thanks, :joelh I have no idea. I seem to recall a bug report indicating that the system sometimes shutsdown unclean due to the VN mount maintaining its lock on the file. -Matt Matthew Dillon :-- :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 : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 17: 0: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id DF71915026 for ; Mon, 14 Jun 1999 16:59:56 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA64400; Tue, 15 Jun 1999 00:41:43 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA47618; Tue, 15 Jun 1999 00:40:58 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199906142340.AAA47618@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: star@iwl.net Cc: hackers@FreeBSD.ORG Subject: Re: NAT Gateway to multiple ISPs In-reply-to: Your message of "Mon, 14 Jun 1999 08:06:14 CDT." <199906141306.IAA12874@star1.iwl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Jun 1999 00:40:58 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Any ideas on the following ? > > I am setting up a home/office network with NAT filtering gateway > on a dual-NIC FreeBSD 3.2 box. No problem so far - I've set > up several like this on 2.2.8 using natd. > > The new wrinkle is this: I need to connect to two ISPs > (DSL & Cable Modem), ideally with automatic failover and > load balancing when multiple internal PC's are generating > internet traffic. > > I know that this requires running gated (or routed) to > receive RIP or OSPF messages from the ISPs, and to select the > best outgoing ISP's route. > > The key question is: while the routing program probably > requires a third NIC so that each external link has its own > device, how can natd handle multiple external internet > interfaces. [.....] > 3) Configure an internal pseudo-device (tun ?) or divert > interface between natd (and the internal NIC) on the inside > and gated or routed (and the two external NICS) on the > outside. > This way, natd and the routing program would be completely > isolated and wouldn't need to know that the other existed. > > ISP1 - NIC1 > \ > gated - TUN - natd - NIC3 - internal net > / device > ISP2 - NIC2 > > > The third seems the best choice, but I haven't seen any > discription of this type of configuration. Except of course for the working example I mailed you on June 9 and committed to src/share/examples/ppp. > Any advice ? > > Thanks very much for your help, > > Andy Starratt -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 19:18:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.cc.ncu.edu.tw (mail.cc.ncu.edu.tw [163.28.48.44]) by hub.freebsd.org (Postfix) with ESMTP id 3716F1540C for ; Mon, 14 Jun 1999 19:18:07 -0700 (PDT) (envelope-from mihs@wm28.csie.ncu.edu.tw) Received: from wm28.csie.ncu.edu.tw (root@wm27.csie.ncu.edu.tw [140.115.155.127]) by mail.cc.ncu.edu.tw (8.9.3/8.9.3/SUN/Solaris) with ESMTP id KAA13862 for ; Tue, 15 Jun 1999 10:15:24 +0800 (CST) Message-ID: <3765B7DC.E87AD77C@wm28.csie.ncu.edu.tw> Date: Tue, 15 Jun 1999 10:18:04 +0800 From: Ming-I Hsieh Organization: XLab, CSIE, NCU, Taiwan. X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Why not let "sys/stat.h" include "sys/types.h"? Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone can tell me why the ``sys/stat.h'' don't include ``sys/types''! It will cause some imcompatible between FreeBSD and some others UN*X. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 19:29:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id C5B6414E4B for ; Mon, 14 Jun 1999 19:29:22 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA13180; Tue, 15 Jun 1999 11:57:28 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3765B7DC.E87AD77C@wm28.csie.ncu.edu.tw> Date: Tue, 15 Jun 1999 11:57:28 +0930 (CST) From: "Daniel O'Connor" To: Ming-I Hsieh Subject: RE: Why not let "sys/stat.h" include "sys/types.h"? Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15-Jun-99 Ming-I Hsieh wrote: > Anyone can tell me why the ``sys/stat.h'' don't include ``sys/types''! > It will cause some imcompatible between FreeBSD and some others UN*X. Because you're supposed to know what you need when you use certain things.. As the stat(2) man page says, you need to include both and --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 19:31:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id EA6EE14E4B for ; Mon, 14 Jun 1999 19:31:35 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id MAA17201; Tue, 15 Jun 1999 12:54:47 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199906150254.MAA17201@cimlogic.com.au> Subject: Re: Matt's Commit status (was Re: 3.2-stable, panic #12) In-Reply-To: <56714.928444103@zippy.cdrom.com> from "Jordan K. Hubbard" at "Jun 3, 1999 2: 8:23 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Tue, 15 Jun 1999 12:54:47 +1000 (EST) 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 Jordan K. Hubbard wrote: > Excellent. Let's assume then that all the core folk who are there, > plus any committers who have an interest in the issue (since core has > to listen to its developers' opinions too or we can no longer honestly > claim to represent their interests), will be getting together during > the week to discuss this issue along with perhaps some general > technical discussion of your work and your future plans. It would > be a shame (not to mention stupid) to waste this opportunity. For the benefit of those of us who weren't at USENIX, can we please have a summary of what was discussed/decided? -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 21:19:36 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 A7AC314DAE for ; Mon, 14 Jun 1999 21:19:34 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 21101 invoked from network); 15 Jun 1999 04:19:34 -0000 Received: from shell-1.enteract.com (dscheidt@207.229.143.40) by pop3-3.enteract.com with SMTP; 15 Jun 1999 04:19:34 -0000 Received: from localhost (dscheidt@localhost) by shell-1.enteract.com (8.9.3/8.9.2) with SMTP id XAA86252; Mon, 14 Jun 1999 23:19:33 -0500 (CDT) (envelope-from dscheidt@enteract.com) X-Authentication-Warning: shell-1.enteract.com: dscheidt owned process doing -bs Date: Mon, 14 Jun 1999 23:19:33 -0500 (CDT) From: David Scheidt To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG, "David E. Cross" Subject: re: david cross's NFS panic fix In-Reply-To: <199906150355.UAA14268@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 Mon, 14 Jun 1999, Matthew Dillon wrote: > Ack, you may have opened up a can of worms here. I don't even think I don't think it is fair to say he opened a can of worms. He found it, but it was clearly open to begin with. He had the misfortune to stumble across it. Since he has tracked it down, it needs to be quashed, right? (note, CC's trimmed, subject changed, and redirected back into -hackers, which this has wondered out of.) 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 Jun 14 21:22:42 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 EF33414DAE for ; Mon, 14 Jun 1999 21:22:38 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA14463; Mon, 14 Jun 1999 21:22:32 -0700 (PDT) (envelope-from dillon) Date: Mon, 14 Jun 1999 21:22:32 -0700 (PDT) From: Matthew Dillon Message-Id: <199906150422.VAA14463@apollo.backplane.com> To: David Scheidt Cc: freebsd-hackers@FreeBSD.ORG, "David E. Cross" Subject: Re: re: david cross's NFS panic fix References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :On Mon, 14 Jun 1999, Matthew Dillon wrote: : :> Ack, you may have opened up a can of worms here. I don't even think : :I don't think it is fair to say he opened a can of worms. He found it, but :it was clearly open to begin with. He had the misfortune to stumble across :it. Since he has tracked it down, it needs to be quashed, right? : :(note, CC's trimmed, subject changed, and redirected back into -hackers, :which this has wondered out of.) : :David Scheidt Oh yes, it needs to be squashed. I meant that comment in a good way :-) -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 Jun 14 21:27: 2 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 310B714DAE for ; Mon, 14 Jun 1999 21:27:00 -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 AAA24303; Tue, 15 Jun 1999 00:26:41 -0400 (EDT) Message-Id: <199906150426.AAA24303@cs.rpi.edu> To: Matthew Dillon Cc: "David E. Cross" , schimken@cs.rpi.edu, freebsd-hackers@freebsd.org Subject: NFSv3 fixes... In-Reply-To: Message from Matthew Dillon of "Mon, 14 Jun 1999 20:55:14 PDT." <199906150355.UAA14268@apollo.backplane.com> Date: Tue, 15 Jun 1999 00:26:40 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry about that everyone, I 'repl'ied to the wrong message. > Ack, you may have opened up a can of worms here. I don't even think > that nfs_namei() does the right thing when it returns an error... it > doesn't look like it clears the ndp->ni_vp either in some error cases. Who, me? Open a can of worms? ;) > We are going to have to instrument the code - basically means NULLing > out ni_vp and any local vnode pointer when the vnode in question is > released so we can keep track of it and putting KASSERT()s in strategic > places. nfs_namei() in nfs/nfs_subs.c and just about all the subroutines > defined in nfs/nfs_serv.c. That was along the lines of my thoughts too... it became painfully obvious that this sort of bug could be (and probably is) everywhere in the nfs server code. I will be happy to follow your lead on this (honored one may say). I am hoping to have some time to deal with this tonight, but I did just get my CD-RW drive. We should probably take the time to document the code some more while we are at it... simple things like commenting what braces go to what would have greatly eased my trace through the code :) -- David Cross The source will be with you, always. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 21:52: 4 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 1AB9414DF6 for ; Mon, 14 Jun 1999 21:51:58 -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 WAA46178; Mon, 14 Jun 1999 22:51: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 WAA86614; Mon, 14 Jun 1999 22:51:40 -0600 (MDT) Message-Id: <199906150451.WAA86614@harmony.village.org> To: Marc Ramirez Subject: Re: Variant symlinks [was Re: symlink question] Cc: "Jordan K. Hubbard" , hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 14 Jun 1999 12:03:07 EDT." References: Date: Mon, 14 Jun 1999 22:51:40 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Marc Ramirez writes: : Well, I'd like to add versioning, too, but _that's_ hard! Versioning wouldn't be too hard to add to a filesystem. Name lookup would be impacted. The act of creating a new version would just be the creat(2) system call, or open with the O_CREAT bit set (and maybe with the O_TRUNC bit too). However, adding utilities to deal with all these new versions might take a lot of time since various versioning schemes have been implemented in userland over the years (all the foo~ or foo~3~ files from us emacs users, for example). I don't know if it would be worth it to actually do this, but it would make an interesting kernel hacking project for someone wishing to learn about the vfs layer. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 21:55:31 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 DF3F614D6F for ; Mon, 14 Jun 1999 21:55:29 -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 WAA46193; Mon, 14 Jun 1999 22:55: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 WAA86656; Mon, 14 Jun 1999 22:54:56 -0600 (MDT) Message-Id: <199906150454.WAA86656@harmony.village.org> To: Ming-I Hsieh Subject: Re: Why not let "sys/stat.h" include "sys/types.h"? Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 15 Jun 1999 10:18:04 +0800." <3765B7DC.E87AD77C@wm28.csie.ncu.edu.tw> References: <3765B7DC.E87AD77C@wm28.csie.ncu.edu.tw> Date: Mon, 14 Jun 1999 22:54:56 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3765B7DC.E87AD77C@wm28.csie.ncu.edu.tw> Ming-I Hsieh writes: : Anyone can tell me why the ``sys/stat.h'' don't include ``sys/types''! : It will cause some imcompatible between FreeBSD and some others UN*X. Because it isn't supposed to. STAT(2) FreeBSD System Calls Manual STAT(2) ... #include #include int stat(const char *path, struct stat *sb) ... I believe that posix and/or ANSI-C (now ISO-C, soon to be C9x) requires that name space polution be limited in what sys/stat.h can cause to be defined. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 22:55:51 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 2B57814DB4 for ; Mon, 14 Jun 1999 22:55:45 -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 WAA02586; Mon, 14 Jun 1999 22:57:18 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: John Birrell Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Matt's Commit status (was Re: 3.2-stable, panic #12) In-reply-to: Your message of "Tue, 15 Jun 1999 12:54:47 +1000." <199906150254.MAA17201@cimlogic.com.au> Date: Mon, 14 Jun 1999 22:57:18 -0700 Message-ID: <2582.929426238@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For the benefit of those of us who weren't at USENIX, can we please > have a summary of what was discussed/decided? Nothing was [deliberately] decided but much was discussed. As soon as one of us lands back home in some reasonable state, a summary will be posted. I've yet to do this myself and will be on the road for the rest of the week as well. :| - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 22:56:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 71A4414F11; Mon, 14 Jun 1999 22:56:39 -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 XAA46284; Mon, 14 Jun 1999 23:56:37 -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 XAA90154; Mon, 14 Jun 1999 23:56:20 -0600 (MDT) Message-Id: <199906150556.XAA90154@harmony.village.org> To: Mitsuru IWASAKI Subject: Re: apmd for FreeBSD Cc: freebsd-hackers@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Thu, 10 Jun 1999 21:55:46 +0900." <199906101257.VAA16619@tasogare.imasy.or.jp> References: <199906101257.VAA16619@tasogare.imasy.or.jp> Date: Mon, 14 Jun 1999 23:56:20 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199906101257.VAA16619@tasogare.imasy.or.jp> Mitsuru IWASAKI writes: : apmd(8): : http://home.jp.freebsd.org/~iwasaki/apm/19990610/apmd-usr.sbin.tar.gz With the patched include files, this compiles and appears to work on -current. : 3.2-RELEASE kernel patch: : http://home.jp.freebsd.org/~iwasaki/apm/19990610/apmd-sys-R320.diff.gz I've applied the patches to my -current system. I had to apply two by hand, and then it just compiled and appeared to work with no ill effects on my desktop. Good job. Now to testing on my laptop.... Warner P.S. I've put my diffs vs -current at http://www.freebsd.org/~imp/apmd-sys-current.diff.gz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 23:22:16 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 BED8114D90 for ; Mon, 14 Jun 1999 23:22:08 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id QAA21734; Tue, 15 Jun 1999 16:20:39 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xma021722; Tue, 15 Jun 99 16:20:38 +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 QAA10301; Tue, 15 Jun 1999 16:20:37 +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 QAA12397; Tue, 15 Jun 1999 16:20:37 +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 QAA03507; Tue, 15 Jun 1999 16:20:36 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199906150620.QAA03507@nymph.detir.qld.gov.au> To: "Chuck Youse" Cc: hackers@freebsd.org, "Marc Ramirez" , syssgm@detir.qld.gov.au Subject: Re: symlink question References: <003001beb5f9$9b10b480$65e684ce@sloth.yousehouse.org> In-Reply-To: <003001beb5f9$9b10b480$65e684ce@sloth.yousehouse.org> from "Chuck Youse" at "Sun, 13 Jun 1999 20:05:23 -0400" Date: Tue, 15 Jun 1999 16:20:36 +1000 From: Stephen McKay Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 13th June 1999, "Chuck Youse" wrote: >Forgive my ignorance, but what exactly is meant by a "variant link", and >what might one be used for? Abused, not used. A number of incredibly dodgy things can be done with symlinks that point here at one moment and there at another moment based on the current value of some environment variable, or other hidden system variable. I cough up a lung every time this topic is raised. Variant symlinks have caused me grief (Pyramid OSx) and never joy. I hope it fails yet again to appear in FreeBSD. Just think of the new security holes for a start. Stephen. "Oh, namei! What have they done to thee?" -- John Mackin, on seeing Apollo's variant symlinks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 23:31:59 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 A0087153DE for ; Mon, 14 Jun 1999 23:31:58 -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 XAA02747; Mon, 14 Jun 1999 23:33:24 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Stephen McKay Cc: "Chuck Youse" , hackers@FreeBSD.ORG, "Marc Ramirez" Subject: Re: symlink question In-reply-to: Your message of "Tue, 15 Jun 1999 16:20:36 +1000." <199906150620.QAA03507@nymph.detir.qld.gov.au> Date: Mon, 14 Jun 1999 23:33:24 -0700 Message-ID: <2743.929428404@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > symlinks have caused me grief (Pyramid OSx) and never joy. I hope it fails > yet again to appear in FreeBSD. Just think of the new security holes for a > start. Name one, please. You can currently point a symlink anyplace you like; whether the user has permission to *read* or execute the target of the link, however, is where the genuine system administration takes over. How the actual value is derived shouldn't make that much difference. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 14 23:57:43 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 ECD6614F0C for ; Mon, 14 Jun 1999 23:57:41 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 42244 invoked from network); 15 Jun 1999 06:57:41 -0000 Received: from shell-1.enteract.com (dscheidt@207.229.143.40) by pop3-3.enteract.com with SMTP; 15 Jun 1999 06:57:41 -0000 Received: from localhost (dscheidt@localhost) by shell-1.enteract.com (8.9.3/8.9.2) with SMTP id BAA86823; Tue, 15 Jun 1999 01:57:40 -0500 (CDT) (envelope-from dscheidt@enteract.com) X-Authentication-Warning: shell-1.enteract.com: dscheidt owned process doing -bs Date: Tue, 15 Jun 1999 01:57:40 -0500 (CDT) From: David Scheidt To: "Jordan K. Hubbard" Cc: Stephen McKay , Chuck Youse , hackers@FreeBSD.ORG, Marc Ramirez Subject: Re: symlink question In-Reply-To: <2743.929428404@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, 14 Jun 1999, Jordan K. Hubbard wrote: > > symlinks have caused me grief (Pyramid OSx) and never joy. I hope it fails > > yet again to appear in FreeBSD. Just think of the new security holes for a > > start. > > Name one, please. You can currently point a symlink anyplace you > like; whether the user has permission to *read* or execute the target > of the link, however, is where the genuine system administration takes > over. How the actual value is derived shouldn't make that much > difference. :) First try: Suppose foo depends on /usr/local/etc/foo.conf. /usr/local/etc is a link to /usr/local/${ARCH}/etc. User does export $ARCH=../../home/user, so /usr/local/etc/foo.conf is now in their home directory. Depending on how poorly written foo is written, it may be possible for the user to get foo to do things it wouldn't normally. There a bunch of these sorts of things lurking here. Clearly, navigation up the tree can't be allowed, at least for processes operating with increased privs. There are probably some other path subversion issues, or potential issues, lurking in this. This is not to say this isn't a good idea. I can think of serveral uses that would make my life easier. 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 Jun 14 23:58:34 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 1E7F115432 for ; Mon, 14 Jun 1999 23:58:27 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id QAA27108; Tue, 15 Jun 1999 16:56:38 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xmaa27096; Tue, 15 Jun 99 16:56:34 +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 QAA12595; Tue, 15 Jun 1999 16:56:34 +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 QAA14919; Tue, 15 Jun 1999 16:56:33 +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 QAA04733; Tue, 15 Jun 1999 16:56:32 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199906150656.QAA04733@nymph.detir.qld.gov.au> To: "Jordan K. Hubbard" Cc: "Chuck Youse" , hackers@FreeBSD.ORG, "Marc Ramirez" , syssgm@detir.qld.gov.au Subject: Re: symlink question References: <2743.929428404@zippy.cdrom.com> In-Reply-To: <2743.929428404@zippy.cdrom.com> from "Jordan K. Hubbard" at "Mon, 14 Jun 1999 23:33:24 -0700" Date: Tue, 15 Jun 1999 16:56:32 +1000 From: Stephen McKay Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 14th June 1999, "Jordan K. Hubbard" wrote: >> symlinks have caused me grief (Pyramid OSx) and never joy. I hope it fails >> yet again to appear in FreeBSD. Just think of the new security holes for a >> start. > >Name one, please. You can currently point a symlink anyplace you >like; whether the user has permission to *read* or execute the target >of the link, however, is where the genuine system administration takes >over. How the actual value is derived shouldn't make that much >difference. :) Yes, symlinks caused (still cause?) havoc when introduced! And with variant symlinks, you lose the ability to statically verify where things go. A safe symlink (right now) becomes a dangerous one not when the file system is changed, but when some transient variable changes. I don't like that at all. I don't want to have to think through all the consequences. You might consider this sort of shifting of the goal posts (the subtle change to the behaviour of absolutely every program) as a minor inconvenience, and acceptable in order to gain the benefits of variant links. I don't think that way, partially because I don't see them as a real benefit, with more "wow" effect than real utility. Everyone points out the /${ARCH}/bin use, but that can be done in other ways (eg just set PATH) that don't cost much (admin time or cpu time). Stephen. PS On second thoughts, I think Mackin was pointing and exclaiming at a Tektronix workstation. Did they have variant links? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 0:15:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles504.castles.com [208.214.165.68]) by hub.freebsd.org (Postfix) with ESMTP id CACC514D98 for ; Tue, 15 Jun 1999 00:15:36 -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 AAA00708 for ; Tue, 15 Jun 1999 00:12:52 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199906150712.AAA00708@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@freebsd.org Subject: ZD labs test update Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Jun 1999 00:12:51 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Straight back from Usenix, I've returned to ZD labs to continue with the benchmarking attempt we started the week before last. Just to remind everyone, this is the standard Samba-and-Apache runaround with the addition of Zeus to the mix in order to get a feel for its relative performance. The goal here is to add a FreeBSD column to the tests published in PC Week a little while back. The system configuration is as follows; - Compaq Proliant 6100 (an engineering sample) with 4x500MHz PII Xeons and 2GB of RAM. - One Seagate Cheetah for the system disk, on an Adaptec 2940U2W. - Seven Seagate Cheetahs for the data volume, managed by an Infortrend 3201U2, organised as a single RAID5 volume (this is a test requirement) and hung off another 2940U2W. - Four Intel EtherExpress Pro/100's. The RAID controller was kindly loaned by Telenet Systems, the rest of the equipment is provided by ZD labs themselves. Today's progress was greatly aided by Peter Wemm, who managed to miss his flight out last night, and was thus dragged along. This gave us a fighting chance against the Compaq system, which fought us at almost every turn. I'm sure these systems are wonderful servers, but they've got to be towards the "more painful" end of the spectrum when it comes to setting them up. We'd previously encountered problems with the Infortrend controller not at all liking the other disks we'd tried to talk to; a collection of Cheetahs with IBM and Compaq firmware simply wouldn't work. This time we had better luck with real Seagate firmware, and the array performance wasn't too shabby, giving us ~8MB/sec write performance and ~16MB/sec read performance using the dd-stone benchmark. Following established lore, it was necessary to use the secret Ctrl-A hotkey to enable Advanced mode in the Compaq setup program so that the MP table could be set to 'Full Table' mode, as well as rearrange interrupts so that nothing useful was given IRQ 9. This latter was necessary as otherwise the system was presented with around 100,000 interrupts per second, from an unknown source. This consumed about 6% CPU (according to systat) in SMP mode, and caused the peripheral with that IRQ to fail miserably. A few other minor tweaks were performed (upping the buffer cache sizing by setting NBUF to 32,000) and a set of kernels built for UP, 2-way and 4-way SMP. Thus, the ground is prepared for us to begin testing with Samba tomorrow. More news as it comes... -- \\ 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 Tue Jun 15 1:22:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (Postfix) with SMTP id B0C5614D6E for ; Tue, 15 Jun 1999 01:22:30 -0700 (PDT) (envelope-from will@ns.oeno.com) Received: (qmail 4112 invoked by uid 1001); 15 Jun 1999 08:22:29 -0000 To: mo@servo.ccr.org (Mike O'Dell) Cc: hackers@freebsd.org Subject: Re: coarse vs fine-grained locking in SMP systems References: <199906141047.GAA57400@servo.ccr.org> From: Ville-Pertti Keinonen Date: 15 Jun 1999 11:20:11 +0300 In-Reply-To: mo@servo.ccr.org's message of "14 Jun 1999 13:48:19 +0300" Message-ID: <86btehooxw.fsf@not.demophon.com> Lines: 19 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mo@servo.ccr.org (Mike O'Dell) writes: > very fine-grain-locked systems often display convoying and > are prone to priority inversion problems. coarse-grained Priority inversion problems are design flaws. Depending on the type of locks, they may not even be possible. Spin locks held for short periods of time (typical for very fine-grained systems) can't cause priority inversion because the process holding the lock can't block. > we published the best Unix SMP paper I've ever seen in Computing > Systems - from the Amdahl guys who did an SMP version of the kernel > by very clever hacks on SPLx() macros to make them spin locks and > a bit of other clever trickery on the source. they could take a stock An approach like that can't possibly be sufficient if code has been written with the assumption that only interrupt-like events or blocking calls can change things from under it. There is quite a bit of code in FreeBSD that relies on this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 1:32: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 8F73014EF4 for ; Tue, 15 Jun 1999 01:32:17 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id BAA15496; Tue, 15 Jun 1999 01:32:15 -0700 (PDT) (envelope-from dillon) Date: Tue, 15 Jun 1999 01:32:15 -0700 (PDT) From: Matthew Dillon Message-Id: <199906150832.BAA15496@apollo.backplane.com> To: "David E. Cross" Cc: schimken@cs.rpi.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: NFSv3 fixes... References: <199906150426.AAA24303@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Who, me? Open a can of worms? ;) Heh! :> We are going to have to instrument the code - basically means NULLing :> out ni_vp and any local vnode pointer when the vnode in question is :> released so we can keep track of it and putting KASSERT()s in strategic :> places. nfs_namei() in nfs/nfs_subs.c and just about all the subroutines :> defined in nfs/nfs_serv.c. : :That was along the lines of my thoughts too... it became painfully obvious :that this sort of bug could be (and probably is) everywhere in the nfs :server code. I will be happy to follow your lead on this (honored one :may say). I am hoping to have some time to deal with this tonight, but I did :just get my CD-RW drive. We should probably take the time to document the :code some more while we are at it... simple things like commenting what :braces go to what would have greatly eased my trace through the code :) : :-- :David Cross :The source will be with you, always. Well, I looked at the code some more. The bugs in nfs_namei() are easy to fix. Unfortunately, I found some truely horrendous bugs in nfs_serv.c. Sometimes 'dirp' is not properly released, there is a double-free of nd.ni_cnd.cn_pnbuf in one place, sometimes nd.ni_startdir is not always released. This is on top of the bugs you found with nd.ni_vp and nd.ni_dvp not always being properly released! The nfs_serv.c module is going to have to be seriously cleaned up, which basically means a rewrite of the more complex procedures. I think I can do it fairly easily, and comment it along the way. -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 Jun 15 2: 0:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (Postfix) with SMTP id 5989314EE5 for ; Tue, 15 Jun 1999 02:00:45 -0700 (PDT) (envelope-from will@ns.oeno.com) Received: (qmail 5007 invoked by uid 1001); 15 Jun 1999 09:00:42 -0000 To: dscheidt@enteract.com (David Scheidt) Cc: hackers@freebsd.org Subject: Re: symlink question References: <2743.929428404@zippy.cdrom.com> From: Ville-Pertti Keinonen Date: 15 Jun 1999 11:58:25 +0300 In-Reply-To: dscheidt@enteract.com's message of "15 Jun 1999 09:58:21 +0300" Message-ID: <86aeu1on66.fsf@not.demophon.com> Lines: 35 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dscheidt@enteract.com (David Scheidt) writes: > First try: Suppose foo depends on /usr/local/etc/foo.conf. > /usr/local/etc is a link to /usr/local/${ARCH}/etc. User does > export $ARCH=../../home/user, so /usr/local/etc/foo.conf is now in > their home directory. Depending on how poorly written foo is Eww, I don't like the idea of using environment variables this way. The kernel shouldn't rely on them, they are a userland thing except during execve. Environment variables aren't even visible to the kernel in the process that sets them. Variant symlinks don't need to be controlled through environment variables. If there is a specific use in mind for variant symlinks, the mechanism for configuring them should be chosen with consideration for that. (Even if variant symlinks could be environment variables, there should be ones that are based on some "hard-wired" info and system-wide variant symlinks should only use environment variables when user-modifiability is specifically desirable. Your example is obviously a case of improper use.) If there is no specific use in mind for variant symlinks, other than to have fun magic thingies around to play with that *can* be used for such-and-such, then implementing them is not a particularly good idea. For example, Lites had variant symlinks with keywords that were internally resolved to the architecture/system name or the name of the system being emulated. For Lites, this was much better than something equivalent to FreeBSD's /compat hacks, because emulated systems were "equal", and the root partition could be shared with the real system. For FreeBSD, the current approach is probably better, because emulated systems are optional exceptions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 2:37:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (Postfix) with SMTP id 54CBD14D8C for ; Tue, 15 Jun 1999 02:37:53 -0700 (PDT) (envelope-from will@ns.oeno.com) Received: (qmail 6163 invoked by uid 1001); 15 Jun 1999 09:37:52 -0000 To: dillon@apollo.backplane.com (Matthew Dillon) Cc: hackers@freebsd.org Subject: Re: oops, here's the patch References: <199906142007.QAA62362@wobble.cs.rpi.edu> <199906142350.QAA12993@apollo.backplane.com> From: Ville-Pertti Keinonen Date: 15 Jun 1999 12:35:33 +0300 In-Reply-To: dillon@apollo.backplane.com's message of "15 Jun 1999 02:50:57 +0300" Message-ID: <86909lolga.fsf@not.demophon.com> Lines: 38 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dillon@apollo.backplane.com (Matthew Dillon) writes: > However, if the inside of the first conditional generates an error, the vp > may be vput twice. What I recommend is this for the last bit: That can't happen (the attributes are straight from VATTR_NULL along that path) - if it could, the file could also be truncated... > if (vap->va_size != -1) { > ... > if (error) { > vput(vp); > vp = NULL; <<<<<<< my addition > } > } > if (eexistdebug && vp) <<<<<<< also check vp != NULL > vput(vp); > It would be good if someone else could look over this routine and > double-check David's find and his solution with my modification. Have > we handled all the cases? Yes, for that code path. Here's a simpler virtual unified diff that does the same thing as David's patch. (You don't need an 'eexistdebug' variable.) if (vap->va_size != -1) { ... - if (error) - vput(vp); } + if (error) + vput(vp); You can add a check for 'error == 0' in addition to 'vap->va_size != -1' but that shouldn't have any effect. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 3:25:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 8B52614DC8; Tue, 15 Jun 1999 03:25:15 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.2/8.8.8) id LAA73470; Tue, 15 Jun 1999 11:25:12 +0100 (BST) (envelope-from joe) Date: Tue, 15 Jun 1999 11:25:12 +0100 From: Josef Karthauser To: Roger Hardiman Cc: multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: IR Remote for AverMedia and FlyVideo Message-ID: <19990615112512.A71377@pavilion.net> References: <375FBAC9.1C071969@cs.strath.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <375FBAC9.1C071969@cs.strath.ac.uk>; from Roger Hardiman on Thu, Jun 10, 1999 at 02:16:57PM +0100 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jun 10, 1999 at 02:16:57PM +0100, Roger Hardiman wrote: > Hi, > > Several people have asked my recently about supporting the AverMedia > remote control and the FlyVideo Remote Control units for their > Bt848/Bt878 TV cards. > > Well, I finally got a reply from AverMedia and after checking on the > Linux Infra Red Controller (LIRC) web site, I found the source and specs > for > the AverMedia and FlyVideo IR modules. > > I do not have AverMedia or Flyvideo hardware, so I'm not going to look > into it, > but if owner/hackers of these cards want to knock something up for the > Bt848 driver, I'll gladly add it in along side the Hauppauge IR support > we already have. Hi Roger, I've got a phototransistor plugged into my DTR line on the serial port. Is there any working software for FreeBSD for utilising this? (I want to never lose a remote control again!) Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 4: 1: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 5186214C3B for ; Tue, 15 Jun 1999 04:00:58 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id HAA16761; Tue, 15 Jun 1999 07:00:42 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id HAA16006; Tue, 15 Jun 1999 07:00:00 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id GAA53375; Tue, 15 Jun 1999 06:59:58 -0400 (EDT) Date: Tue, 15 Jun 1999 06:59:58 -0400 (EDT) From: Thomas David Rivers Message-Id: <199906151059.GAA53375@lakes.dignus.com> To: jkh@zippy.cdrom.com, syssgm@detir.qld.gov.au Subject: Re: symlink question Cc: cyouse@cybersites.com, hackers@FreeBSD.ORG, mrami@gbtb.com In-Reply-To: <2743.929428404@zippy.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > symlinks have caused me grief (Pyramid OSx) and never joy. I hope it fails > > yet again to appear in FreeBSD. Just think of the new security holes for a > > start. > > Name one, please. You can currently point a symlink anyplace you > like; whether the user has permission to *read* or execute the target > of the link, however, is where the genuine system administration takes > over. How the actual value is derived shouldn't make that much > difference. :) > > - Jordan > My biggest problem with variant symlinks (which I've preached on before) is the following scenario: o) User A runs program P which takes advantage of a variant symlink in some fashion (either in finding P or finding some data P needs, etc...) o) User B runs program P which fails miserably. o) The sysadmin notes that the machines are the same, the symlinks are the same... then has to track down user B, and has to determine what variant symlinks P has been (perhaps even unaware to the designers of P) using and then has see what in user B's environment is causing this problem. Muliply B by several hundred... We would have problems like that on our Apollos; learning the hard way to avoid variant symlinks... just to ensure the environment was as expected. You don't have these same questions with "plain" symlinks. And, if the symlink changes, it's quite easy to see that it changed... So - I'd say that variant symlinks are like many other things, it's really easy to shoot yourself in the foot.. In my opinion variant symlinks make it too easy. Sometimes nifty things don't need to be done. I'd suggest that if they were implemented in FreeBSD - we leave the support 'off' by default, with a sysctl variable to enable them. When a user posts that his XXX/YYY/ZZZ directory has "gone away" we can ask, "are variant symlinks turned on?" and have a good first guess as to the culprit. Just my thoughts.... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 4:23:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from web105.yahoomail.com (web105.yahoomail.com [205.180.60.71]) by hub.freebsd.org (Postfix) with SMTP id 73F9814A0B for ; Tue, 15 Jun 1999 04:23:26 -0700 (PDT) (envelope-from thallgren@yahoo.com) Message-ID: <19990615112327.22753.rocketmail@web105.yahoomail.com> Received: from [131.116.188.217] by web105.yahoomail.com; Tue, 15 Jun 1999 12:23:27 BST Date: Tue, 15 Jun 1999 12:23:27 +0100 (BST) From: Tommy Hallgren Subject: Re: ZD labs test update To: Mike Smith , hackers@freebsd.org 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 --- Mike Smith wrote: > We'd previously encountered problems with the Infortrend controller not > at all liking the other disks we'd tried to talk to; a collection of > Cheetahs with IBM and Compaq firmware simply wouldn't work. This time > we had better luck with real Seagate firmware, and the array > performance wasn't too shabby, giving us ~8MB/sec write performance and > ~16MB/sec read performance using the dd-stone benchmark. Isn't 16MB/s quite bad for this kind of system? === Regards, Tommy Hallgren Briljantg. 31, SE-421 49, Göteborg Tel.: 031 - 770 5232 (Work: Telia Prosoft) Tel.: 0709 - 312 404 (GSM) Tel.: 031 - 47 65 28 (Home) _____________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 4:32:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id 1A90914D2D for ; Tue, 15 Jun 1999 04:32:31 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Tue, 15 Jun 1999 13:35:26 +0200 Message-ID: <55586E7391ACD211B9730000C110027617966C@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: 'Tommy Hallgren' , Mike Smith , hackers@freebsd.org Subject: RE: ZD labs test update Date: Tue, 15 Jun 1999 13:29:53 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Tommy Hallgren [SMTP:thallgren@yahoo.com] > Sent: Tuesday, June 15, 1999 1:23 PM > To: Mike Smith; hackers@freebsd.org > Subject: Re: ZD labs test update > > Isn't 16MB/s quite bad for this kind of system? > [ML] Figuring in the SCSI overhead, 16 MBps, where MB is 2^20B, is pretty much the limit of the fast-wide or ultra-narrow SCSI. So, it depends on the RAID and the SCSI chain. /Marino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 5: 9:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from chmls05.mediaone.net (ne.mediaone.net [24.128.1.70]) by hub.freebsd.org (Postfix) with ESMTP id EDC5614CF9 for ; Tue, 15 Jun 1999 05:09:54 -0700 (PDT) (envelope-from jim@thehousleys.net) Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.218.96.75]) by chmls05.mediaone.net (8.8.7/8.8.7) with ESMTP id IAA16266 for ; Tue, 15 Jun 1999 08:09:53 -0400 (EDT) Received: from thehousleys.net (housley@localhost [127.0.0.1]) by thehousleys.net (8.9.3/8.9.3) with ESMTP id IAA03184 for ; Tue, 15 Jun 1999 08:09:53 -0400 (EDT) (envelope-from jim@thehousleys.net) Message-ID: <37664291.C2A45247@thehousleys.net> Date: Tue, 15 Jun 1999 08:09:53 -0400 From: "James E. Housley" X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: Inactive vs. free Memory Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just for my infomation. What is the difference between "Inactive" and "Free" memory. Right now top says I have 157M Inact and 3260K Free. Jim -- James E. Housley PGP: 1024/03983B4D System Supply, Inc. 2C 3F 3A 0D A8 D8 C3 13 Pager: pagejim@notepage.com 7C F0 B5 BF 27 8B 92 FE "The box said 'Requires Windows 95, NT, or better,' so I installed FreeBSD" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 6:15: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 1F0B914C2D for ; Tue, 15 Jun 1999 06:15:28 -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 PAA11404 for ; Tue, 15 Jun 1999 15:15:25 +0200 (MET DST) Date: Tue, 15 Jun 1999 15:15:24 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: FreeBSD hackers mailing list Subject: dumpon Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've yesterday tried to get kernel dumps to work and failed (and instead just fixed the bug I was looking for :-). The manpage for dumpon seems to be out of date. Adding dump on wd0s2b to the KERNEL config file, gives me a syntax error in that line. And adding the dumpdev to rc.conf is too late as I want the machine to go pop before the filesystems are mounted RW. Any pointers on how I can switch on dumping to the swap partition (/dev/wd0s2b), to be enabled at boot time? 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 Tue Jun 15 6:26:23 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 7B5D4155D3 for ; Tue, 15 Jun 1999 06:26:19 -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 PAA36574; Tue, 15 Jun 1999 15:26:03 +0200 (CEST) (envelope-from des) To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: umapfs... References: <199906142113.RAA20328@cs.rpi.edu> From: Dag-Erling Smorgrav Date: 15 Jun 1999 15:26:03 +0200 In-Reply-To: "David E. Cross"'s message of "Mon, 14 Jun 1999 17:13:38 -0400" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David E. Cross" writes: > I have been looking at the code for UMAPfs... I am trying to understand > conceptually why it is so unstable... You're looking in the wrong place. It's unstable because of infrastructure problems which require fairly substantial amounts of work to correct. 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 Jun 15 6:31:52 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 01D3B14C2D for ; Tue, 15 Jun 1999 06:31:47 -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 JAA29864; Tue, 15 Jun 1999 09:31:23 -0400 (EDT) Message-Id: <199906151331.JAA29864@cs.rpi.edu> To: Dag-Erling Smorgrav Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: umapfs... In-Reply-To: Message from Dag-Erling Smorgrav of "15 Jun 1999 15:26:03 +0200." Date: Tue, 15 Jun 1999 09:31:23 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I have been looking at the code for UMAPfs... I am trying to understand >> conceptually why it is so unstable... > >You're looking in the wrong place. It's unstable because of >infrastructure problems which require fairly substantial amounts of >work to correct. > >DES I guess that is what I am asking... What is different between the following: int foo(void){ return 0; } and int foo_prime(void) { return foo(); } That is my interpretation of the code. It would *seem* to just pass the call off to the next FS layer as if the VFS system of the kernel had done it directly.... Conceptually I must be missing something. -- 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 Jun 15 8:21: 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 CDD831509E for ; Tue, 15 Jun 1999 08:21:00 -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 RAA39159; Tue, 15 Jun 1999 17:20:53 +0200 (CEST) (envelope-from des) To: "David E. Cross" Cc: Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: umapfs... References: <199906151331.JAA29864@cs.rpi.edu> From: Dag-Erling Smorgrav Date: 15 Jun 1999 17:20:53 +0200 In-Reply-To: "David E. Cross"'s message of "Tue, 15 Jun 1999 09:31:23 -0400" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David E. Cross" writes: > That is my interpretation of the code. It would *seem* to just pass the > call off to the next FS layer as if the VFS system of the kernel had done it > directly.... Conceptually I must be missing something. Umm, umapfs rewrites the owner/group of vnodes if I'm not mistaken. That's the whole point with it. 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 Jun 15 8:45: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id A653914A2F for ; Tue, 15 Jun 1999 08:39:49 -0700 (PDT) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id SAA33368; Tue, 15 Jun 1999 18:39:26 +0300 (EEST) (envelope-from ru) Date: Tue, 15 Jun 1999 18:39:26 +0300 From: Ruslan Ermilov To: hackers@FreeBSD.org Subject: [Call for review] init(8): new feature Message-ID: <19990615183926.A31280@relay.ucb.crimea.ua> Mail-Followup-To: hackers@FreeBSD.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=AhhlLboLdkugWU4S X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD 3.2-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Hi, hackers! While the -core is busy to review/approve this patch, I would like to know your opinion. What do you think of it? Thanks, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --AhhlLboLdkugWU4S Content-Type: message/rfc822 Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id XAA18478; Fri, 11 Jun 1999 23:41:00 +0300 (EEST) (envelope-from ru) Date: Fri, 11 Jun 1999 23:40:59 +0300 From: Ruslan Ermilov To: dg@freebsd.org, bde@freebsd.org, phk@freebsd.org, des@freebsd.org Subject: init(8): new feature request Message-ID: <19990611234059.A7733@relay.ucb.crimea.ua> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=d6Gm4EdcadzBjdND X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD 3.2-STABLE i386 --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Hi! We have a lot of PRs (5451, 9066, 10035) complaining the lack of running /etc/rc.shutdown from shutdown(8)/reboot(8). In fact, there are two ways to cleanly (with /etc/rc.shutdown) reboot the system: - send init(8) SIGINT signal; - run shutdown(8) without ``-r'' and ``-h'' switches, so it will send init(8) SIGINT signal. On the other hand, there is no easy (single-step) way to run /etc/rc.shutdown and then halt plus optionally power-off the system. The patch below (mostly from PR#5451) removes this limitation by adding two new features to init(8): - when init(8) receives SIGUSR1, it will act like in SIGINT case, but will call reboot(RB_HALT); - when init(8) receives SIGUSR2, it will act like in SIGINT case, but will call reboot(RB_HALT|RB_POWEROFF). Also, when compiled with -DCOMPAT_SYSV_INIT, it is now possible to emulate SysV's init(8) behaviour. I have tested it on my 3.2-STABLE, and it works like a charm. Very handy!!! Could you please review it? Thanks, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="init.c.patch" Index: Makefile =================================================================== RCS file: /usr/FreeBSD-CVS/src/sbin/init/Makefile,v retrieving revision 1.15 diff -u -r1.15 Makefile --- Makefile 1998/01/20 10:39:56 1.15 +++ Makefile 1999/06/11 20:14:19 @@ -6,6 +6,7 @@ BINMODE=500 INSTALLFLAGS=-fschg CFLAGS+=-DDEBUGSHELL -DSECURE -DLOGIN_CAP +CFLAGS+=-DCOMPAT_SYSV_INIT .if exists(${.CURDIR}/../../secure) && !defined(NOCRYPT) && !defined(NOSECURE) DISTRIBUTION=des Index: init.c =================================================================== RCS file: /usr/FreeBSD-CVS/src/sbin/init/init.c,v retrieving revision 1.31 diff -u -r1.31 init.c --- init.c 1998/07/22 05:45:11 1.31 +++ init.c 1999/06/11 20:28:59 @@ -132,6 +132,7 @@ #define TRUE 1 int Reboot = FALSE; +int howto = RB_AUTOBOOT; int devfs; @@ -203,9 +204,44 @@ errx(1, "%s", strerror(EPERM)); /* System V users like to reexec init. */ - if (getpid() != 1) - errx(1, "already running"); - + if (getpid() != 1) { +#ifdef COMPAT_SYSV_INIT + /* So give them what they want */ + if (argc > 1) { + if (strlen(argv[1]) == 1) { + register char state = *argv[1]; + register int sig; + + switch (state) { + case '0': /* halt + poweroff */ + sig = SIGUSR2; + break; + case '1': /* single user */ + case 's': + sig = SIGTERM; + break; + case '6': /* reboot */ + sig = SIGINT; + break; + case 'q': /* re-read /etc/ttys */ + sig = SIGHUP; + break; + case 'c': /* block further logins */ + sig = SIGTSTP; + break; + default: + goto usage; + } + kill(1, sig); + _exit(0); + } else +usage: + errx(1, "invalid level ``%s''\n" + "usage: init [016cqs]", argv[1]); + } else +#endif + errx(1, "already running"); + } /* * Note that this does NOT open a file... * Does 'init' deserve its own facility number? @@ -259,11 +295,13 @@ handle(badsys, SIGSYS, 0); handle(disaster, SIGABRT, SIGFPE, SIGILL, SIGSEGV, SIGBUS, SIGXCPU, SIGXFSZ, 0); - handle(transition_handler, SIGHUP, SIGINT, SIGTERM, SIGTSTP, 0); + handle(transition_handler, SIGHUP, SIGINT, SIGTERM, SIGTSTP, + SIGUSR1, SIGUSR2, 0); handle(alrm_handler, SIGALRM, 0); sigfillset(&mask); delset(&mask, SIGABRT, SIGFPE, SIGILL, SIGSEGV, SIGBUS, SIGSYS, - SIGXCPU, SIGXFSZ, SIGHUP, SIGINT, SIGTERM, SIGTSTP, SIGALRM, 0); + SIGXCPU, SIGXFSZ, SIGHUP, SIGINT, SIGTERM, SIGTSTP, SIGALRM, + SIGUSR1, SIGUSR2, 0); sigprocmask(SIG_SETMASK, &mask, (sigset_t *) 0); sigemptyset(&sa.sa_mask); sa.sa_flags = 0; @@ -598,7 +636,7 @@ sync(); alarm(2); pause(); - reboot(RB_AUTOBOOT); + reboot(howto); _exit(0); } @@ -1238,6 +1276,10 @@ case SIGHUP: requested_transition = clean_ttys; break; + case SIGUSR2: + howto = RB_POWEROFF; + case SIGUSR1: + howto |= RB_HALT; case SIGINT: Reboot = TRUE; case SIGTERM: --d6Gm4EdcadzBjdND-- --AhhlLboLdkugWU4S-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 8:54:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66]) by hub.freebsd.org (Postfix) with ESMTP id BEDAB14A2F for ; Tue, 15 Jun 1999 08:54:26 -0700 (PDT) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: from c62443-a.frmt1.sfba.home.com ([24.0.69.165]) by mail.rdc1.sfba.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19990615155425.QFTJ8807.mail.rdc1.sfba.home.com@c62443-a.frmt1.sfba.home.com>; Tue, 15 Jun 1999 08:54:25 -0700 Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.8.7/8.8.7) id IAA32687; Tue, 15 Jun 1999 08:54:23 -0700 To: "James E. Housley" Cc: hackers@FreeBSD.ORG Subject: Re: Inactive vs. free Memory References: <37664291.C2A45247@thehousleys.net> From: Arun Sharma Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: 15 Jun 1999 08:54:23 -0700 In-Reply-To: "James E. Housley"'s message of "Tue, 15 Jun 1999 08:09:53 -0400" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "James E. Housley" writes: > Just for my infomation. What is the difference between "Inactive" and > "Free" memory. Right now top says I have 157M Inact and 3260K Free. Inactive means the page contains valid data belonging to some file, but is not mapped into any address space. Free means, the page doesn't contain valid data. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 9: 0: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 8EB5315367 for ; Tue, 15 Jun 1999 09:00:00 -0700 (PDT) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: from c62443-a.frmt1.sfba.home.com ([24.0.69.165]) by mail.rdc1.sfba.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19990615155959.QHLF8807.mail.rdc1.sfba.home.com@c62443-a.frmt1.sfba.home.com> for ; Tue, 15 Jun 1999 08:59:59 -0700 Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.8.7/8.8.7) id IAA32700; Tue, 15 Jun 1999 08:59:59 -0700 To: hackers@FreeBSD.ORG Subject: Re: [Call for review] init(8): new feature References: <19990615183926.A31280@relay.ucb.crimea.ua> From: Arun Sharma Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: 15 Jun 1999 08:59:59 -0700 In-Reply-To: Ruslan Ermilov's message of "Tue, 15 Jun 1999 18:39:26 +0300" Message-ID: Lines: 6 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While we're on the init topic, is there any strong feeling here about BSD /etc/rc* scripts Vs SysV ? The nice thing about SysV initscripts is the ability to start and stop any service that I like. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 9: 5:23 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 27FCD155B8; Tue, 15 Jun 1999 09:05:18 -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 AA025017514; Tue, 15 Jun 1999 07:51:54 -0400 Date: Tue, 15 Jun 1999 07:51:54 -0400 (EDT) From: Bill Fumerola To: Ruslan Ermilov Cc: hackers@FreeBSD.ORG Subject: Re: [Call for review] init(8): new feature In-Reply-To: <19990615183926.A31280@relay.ucb.crimea.ua> 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, 15 Jun 1999, Ruslan Ermilov wrote: > While the -core is busy to review/approve this patch, > I would like to know your opinion. What do you think > of it? The sysv init should probably be off by default. - 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 Tue Jun 15 9:17:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 262A0152F8 for ; Tue, 15 Jun 1999 09:17:39 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.2/8.8.8) id RAA71552; Tue, 15 Jun 1999 17:17:31 +0100 (BST) (envelope-from joe) Date: Tue, 15 Jun 1999 17:17:31 +0100 From: Josef Karthauser To: Arun Sharma Cc: "James E. Housley" , hackers@FreeBSD.ORG Subject: Re: Inactive vs. free Memory Message-ID: <19990615171731.P71377@pavilion.net> References: <37664291.C2A45247@thehousleys.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Arun Sharma on Tue, Jun 15, 1999 at 08:54:23AM -0700 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 15, 1999 at 08:54:23AM -0700, Arun Sharma wrote: > "James E. Housley" writes: > > > Just for my infomation. What is the difference between "Inactive" and > > "Free" memory. Right now top says I have 157M Inact and 3260K Free. > > Inactive means the page contains valid data belonging to some file, > but is not mapped into any address space. Free means, the page doesn't > contain valid data. Thanks Arun, This has been bugging us for ages :) At last it's clear Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 9:26:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id 0820815033 for ; Tue, 15 Jun 1999 09:24:23 -0700 (PDT) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id TAA44514; Tue, 15 Jun 1999 19:21:51 +0300 (EEST) (envelope-from ru) Date: Tue, 15 Jun 1999 19:21:50 +0300 From: Ruslan Ermilov To: Bill Fumerola Cc: hackers@FreeBSD.ORG Subject: Re: [Call for review] init(8): new feature Message-ID: <19990615192150.A43041@relay.ucb.crimea.ua> Mail-Followup-To: Bill Fumerola , hackers@FreeBSD.ORG References: <19990615183926.A31280@relay.ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Bill Fumerola on Tue, Jun 15, 1999 at 07:51:54AM -0400 X-Operating-System: FreeBSD 3.2-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 15, 1999 at 07:51:54AM -0400, Bill Fumerola wrote: > On Tue, 15 Jun 1999, Ruslan Ermilov wrote: > > > While the -core is busy to review/approve this patch, > > I would like to know your opinion. What do you think > > of it? > > The sysv init should probably be off by default. > Sure, I turned it on only for test purposes, in case someone wants to try it out. -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 9:50:18 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 39C2F15135 for ; Tue, 15 Jun 1999 09:50:09 -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 JAA19226 for ; Tue, 15 Jun 1999 09:50:12 -0700 Date: Tue, 15 Jun 1999 09:50:00 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-hackers@freebsd.org Subject: NFS hangs on reads? 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 Umm, recently I've noticed for both 3.2 && 4.0 that NFS seems to get wedged on a directory that is mounted from a Solaris 2.6 (unpatched) server- but this seems to only happen if the local mount point is a directory just off of root. The scenario is, e.g.: bird:/export/home on /home bird:/space5/freebsd on /freebsd bird:/space5/freebsd/distfiles on /usr/ports/distfiles bird:/src/freebsd-current/src on /usr/src a 'ls' of /home hangs. Then a 'ls' of /home/mjacob and /usr/src hangs... the ps commands have: 31154 31830 31802 0 -18 0 360 212 nfsngt D+ p1 0:00.00 (ls) 31154 31869 1 0 -18 0 360 212 nfsngt D p2- 0:00.00 (ls) Sorry- this is a bit vague- I'll track it down further if this isn't already a known problem I'll track this more carefully. I first saw this with 3.2-stable, but it also is happening with -current as of today. A quick perusal of the nfs_node code doesn't suggest much to me. I should point out that both systems are 2xPPro SMP systems. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 9:54:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dyson.iquest.net. (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (Postfix) with ESMTP id 3DAD91518F for ; Tue, 15 Jun 1999 09:54:48 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from toor@localhost) by dyson.iquest.net. (8.9.3/8.9.3) id LAA03905; Tue, 15 Jun 1999 11:54:37 -0500 (EST) (envelope-from toor) Message-Id: <199906151654.LAA03905@dyson.iquest.net.> Subject: Re: Inactive vs. free Memory In-Reply-To: from Arun Sharma at "Jun 15, 1999 08:54:23 am" To: adsharma@home.com (Arun Sharma) Date: Tue, 15 Jun 1999 11:54:37 -0500 (EST) Cc: jim@thehousleys.net (James E. Housley), hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net 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 Arun Sharma said: > "James E. Housley" writes: > > > Just for my infomation. What is the difference between "Inactive" and > > "Free" memory. Right now top says I have 157M Inact and 3260K Free. > > Inactive means the page contains valid data belonging to some file, > but is not mapped into any address space. Free means, the page doesn't > contain valid data. > Trying to be helpful to follow up with more detail, but slightly inprecise due to the fact that there are still some generalizations: Active pages have been recently mapped into a process by the kernel, most often by virtue of a page fault. Sometimes pages are activated, but not initially mapped, and that is a policy decision. Inactive pages might or might not be mapped into a process recently, but those pages have likely been bumped from the Active list by the pageout daemon. Sometimes the system will initially inactivate a page instead of activating it for policy reasons though. Cache pages are not mapped into a process, but are left around for reuse with intact data. Cache pages are VM cached, but a slightly confusing issue is that buffer cache pages are actually wired. Cache pages are in the netherworld of being free and not-free, and can be used as BOTH empty or cache data. Free pages have no data, and might or might not be prezeroed. Wired pages are often directly used by the kernel, and are not available for involuntary reuse by the actions of the pageout daemon. One of the improvements of FreeBSD VM over the old original code is that it has an in-between form of "free" pages called "cache" pages, that are available for immediate reuse both as empty pages or containing their previous contents. This allows for policy mistakes to be buffered further than the LRU-K type algorithm used by the pageout daemon. Adding the cache queue made a significant improvement, over and above the LRU-K style scheme. (Note the FreeBSD implementation of LRU-K is particularly efficient.) -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 9:57:54 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 EB99D15243; Tue, 15 Jun 1999 09:57:51 -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 JAA19243; Tue, 15 Jun 1999 09:57:55 -0700 Date: Tue, 15 Jun 1999 09:57:44 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-hackers@FreeBSD.ORG Cc: peter@FreeBSD.ORG Subject: followup to mysefl: Re: NFS hangs on reads? 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 Closer examination shows the possible problem: Rev 1.29 added: /* * Insert the nfsnode in the hash queue for its new file handle */ for (np2 = nhpp->lh_first; np2 != 0; np2 = np2->n_hash.le_next) { if (mntp != NFSTOV(np)->v_mount || np2->n_fhsize != fhsize || bcmp((caddr_t)fhp, (caddr_t)np2->n_fhp, fhsize)) continue; vrele(vp); goto retry; } Peter- you brought this over from FreeBSD... what's up? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 10: 0: 6 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 D1D101537B; Tue, 15 Jun 1999 10:00:04 -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 JAA19258; Tue, 15 Jun 1999 09:59:59 -0700 Date: Tue, 15 Jun 1999 09:59:48 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-hackers@FreeBSD.ORG Cc: peter@FreeBSD.ORG Subject: D'oh! 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 > for (np2 = nhpp->lh_first; np2 != 0; np2 = np2->n_hash.le_next) { > if (mntp != NFSTOV(np)->v_mount || np2->n_fhsize != fhsize || > bcmp((caddr_t)fhp, (caddr_t)np2->n_fhp, fhsize)) > continue; > vrele(vp); > goto retry; > } > > > Peter- you brought this over from FreeBSD... what's up? ------------------------------------OpenBSD! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 10:29:14 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 0E89114CF7; Tue, 15 Jun 1999 10:29:12 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA19516; Tue, 15 Jun 1999 10:29:07 -0700 (PDT) (envelope-from dillon) Date: Tue, 15 Jun 1999 10:29:07 -0700 (PDT) From: Matthew Dillon Message-Id: <199906151729.KAA19516@apollo.backplane.com> To: Matthew Jacob Cc: freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: D'oh! References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> for (np2 = nhpp->lh_first; np2 != 0; np2 = np2->n_hash.le_next) { :> if (mntp != NFSTOV(np)->v_mount || np2->n_fhsize != fhsize || :> bcmp((caddr_t)fhp, (caddr_t)np2->n_fhp, fhsize)) :> continue; :> vrele(vp); :> goto retry; :> } :> :> :> Peter- you brought this over from FreeBSD... what's up? :------------------------------------OpenBSD! : The problem is that peter is not releasing the nfs_node_hash_lock when he goes to retry, creating a deadlock with himself. Peter, looks like a quick fix & commit to me, I'd say just go ahead and do it. Heh, I just realized how funny that first statement was :-) -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 Jun 15 10:30:34 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 D7A0F14C18 for ; Tue, 15 Jun 1999 10:30:30 -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 CAA00728; Wed, 16 Jun 1999 02:30:21 +0900 (JST) Date: Wed, 16 Jun 1999 02:30:21 +0900 (JST) Message-Id: <199906151730.CAA00728@afs.ntc.mita.keio.ac.jp> To: jkh@zippy.cdrom.com Cc: mark@grondar.za, hackers@FreeBSD.ORG, hosokawa@itc.keio.ac.jp Subject: PCCARD boot.flp for -current (reviewer wanted) In-Reply-To: Your message of "Thu, 3 Jun 1999 19:10:51 JST". <10710.928404651@peewee> 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 <10710.928404651@peewee> jkh@zippy.cdrom.com writes: >> 1. Put pccardd on the mfsroot floppy and add a few things to >> sysinstall (this may already be done by his patches, I haven't >> had time to check) which enable its use during installation. I've ported PC-card boot.flp to -current. Source patch can be found at http://wing-yee.ntc.keio.ac.jp/hosokawa/pccard-flp/current-diff-19990616.tar.gz and, compiled binaries (boot.flp, kern.flp, and mfsroot.flp) at http://wing-yee.ntc.keio.ac.jp/hosokawa/pccard-flp/current-binaries-19990616.tar.gz With this patch, "make PCCARD=YES boot.flp" produces PC-card boot.flp and "make boot.flp" produces normal boot.flp. To make them both automatically, more patches are required, but I think they can be committed later. Please review this patch. I want to commit these patches to -current and -stable. If there are no objection, I'll commit them. -- 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 Tue Jun 15 10:33:12 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 3B2F714C18; Tue, 15 Jun 1999 10:33:09 -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 KAA19382; Tue, 15 Jun 1999 10:33:11 -0700 Date: Tue, 15 Jun 1999 10:33:00 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: D'oh! In-Reply-To: <199906151729.KAA19516@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 > : > > The problem is that peter is not releasing the nfs_node_hash_lock > when he goes to retry, creating a deadlock with himself. > > Peter, looks like a quick fix & commit to me, I'd say just go ahead > and do it. > > Heh, I just realized how funny that first statement was :-) Yup, that's my take too.... waking up any waiters to re-contend seemed correct to do too.... Index: nfs_node.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_node.c,v retrieving revision 1.29 diff -c -r1.29 nfs_node.c *** nfs_node.c 1999/06/05 05:26:36 1.29 --- nfs_node.c 1999/06/15 17:19:49 *************** *** 167,172 **** --- 167,175 ---- bcmp((caddr_t)fhp, (caddr_t)np2->n_fhp, fhsize)) continue; vrele(vp); + if (nfs_node_hash_lock < 0) + wakeup(&nfs_node_hash_lock); + nfs_node_hash_lock = 0; goto retry; } LIST_INSERT_HEAD(nhpp, np, n_hash); If peter doesn't respond by this afternoon, I'll commit it. I've tried it on -current so far. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 10:37:22 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 9AF75153DA; Tue, 15 Jun 1999 10:37:19 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA19611; Tue, 15 Jun 1999 10:37:18 -0700 (PDT) (envelope-from dillon) Date: Tue, 15 Jun 1999 10:37:18 -0700 (PDT) From: Matthew Dillon Message-Id: <199906151737.KAA19611@apollo.backplane.com> To: Matthew Jacob Cc: freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: D'oh! References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> Heh, I just realized how funny that first statement was :-) : : :Yup, that's my take too.... waking up any waiters to re-contend seemed :correct to do too.... :... : :If peter doesn't respond by this afternoon, I'll commit it. I've tried it :on -current so far. Sounds good to me! If someone on -hackers has easy access to the OpenBSD source, it would be nice if he could check whether the OpenBSD code has the same problem and notify the OpenBSD folks if it does. -Matt Matthew Dillon :Index: nfs_node.c :... : bcmp((caddr_t)fhp, (caddr_t)np2->n_fhp, fhsize)) : continue; : vrele(vp); :+ if (nfs_node_hash_lock < 0) :+ wakeup(&nfs_node_hash_lock); :+ nfs_node_hash_lock = 0; : goto retry; : } : :-matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 10:38: 6 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 026B814CFF; Tue, 15 Jun 1999 10:38:03 -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 KAA19440; Tue, 15 Jun 1999 10:38:05 -0700 Date: Tue, 15 Jun 1999 10:37:54 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: D'oh! In-Reply-To: <199906151737.KAA19611@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 > :> > :> Heh, I just realized how funny that first statement was :-) > : > : > :Yup, that's my take too.... waking up any waiters to re-contend seemed > :correct to do too.... > :... > : > :If peter doesn't respond by this afternoon, I'll commit it. I've tried it > :on -current so far. > > Sounds good to me! If someone on -hackers has easy access to the OpenBSD > source, it would be nice if he could check whether the OpenBSD code > has the same problem and notify the OpenBSD folks if it does. > Good point. I'm a committer there too, so I'll check it and let them know... thx... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 10:50:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 702051519E; Tue, 15 Jun 1999 10:50:32 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb49.imasy.or.jp [202.227.24.177]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id CAA23758; Wed, 16 Jun 1999 02:50:29 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199906151750.CAA23758@tasogare.imasy.or.jp> To: imp@harmony.village.org Cc: iwasaki@jp.FreeBSD.org, freebsd-hackers@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: apmd for FreeBSD In-Reply-To: Your message of "Mon, 14 Jun 1999 23:56:20 -0600" <199906150556.XAA90154@harmony.village.org> References: <199906150556.XAA90154@harmony.village.org> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 16 Jun 1999 02:48:42 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 18 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks a lot for your testing. I'm preparing -current NotePC for testing this. imp> I've applied the patches to my -current system. I had to apply two by imp> hand, and then it just compiled and appeared to work with no ill imp> effects on my desktop. It should :) I heard that 3.2-RELEASE kernel patch can be applied to -STABLE (even 2.2-STABLE) with no rejects because there are few differences between them. imp> P.S. I've put my diffs vs -current at imp> http://www.freebsd.org/~imp/apmd-sys-current.diff.gz Thanks. Give my kind regards. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 11: 2:11 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 78C201507A for ; Tue, 15 Jun 1999 11:02:05 -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 10txX1-000MIq-00 for hackers@freebsd.org; Tue, 15 Jun 1999 20:01:55 +0200 From: Sheldon Hearn To: hackers@freebsd.org Subject: inetd+libwrap and wrapping UDP services Date: Tue, 15 Jun 1999 20:01:55 +0200 Message-ID: <85735.929469715@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, The patches on PR 12097 that deal with fixing inetd's handling of tcp_wrapper support do _not_ enable wrapping of UDP services. David Malone and I are busy working on a patch for doing so, but I have a question that I probably should have asked when we started. Is there any point in wrapping UDP services (identified as "dgram udp" services in inetd.conf)? Since they're all single-threaded, using the wait option, any successful connection opens up a rolling period during which any further connections will not be wrapped (hence the word rolling). So what's the point? Obviously, if there's a real need for wrapping UDP services, we'll carry on grafting. Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 11: 5:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (Postfix) with ESMTP id ECC8F153DB for ; Tue, 15 Jun 1999 11:05:12 -0700 (PDT) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id 055965B92; Tue, 15 Jun 1999 20:05:10 +0200 (MET DST) Message-ID: <19990615200510.A3803@gvr.org> Date: Tue, 15 Jun 1999 20:05:10 +0200 From: Guido van Rooij To: Sheldon Hearn , hackers@freebsd.org Subject: Re: inetd+libwrap and wrapping UDP services References: <85735.929469715@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <85735.929469715@axl.noc.iafrica.com>; from Sheldon Hearn on Tue, Jun 15, 1999 at 08:01:55PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 15, 1999 at 08:01:55PM +0200, Sheldon Hearn wrote: > > Hi folks, > > The patches on PR 12097 that deal with fixing inetd's handling of > tcp_wrapper support do _not_ enable wrapping of UDP services. David > Malone and I are busy working on a patch for doing so, but I have a > question that I probably should have asked when we started. > > Is there any point in wrapping UDP services (identified as "dgram udp" > services in inetd.conf)? Since they're all single-threaded, using the > wait option, any successful connection opens up a rolling period during > which any further connections will not be wrapped (hence the word > rolling). > And when you fix that, the wrapper stuff gets invoked for every packet... -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 11: 7:25 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 92AD8151E0 for ; Tue, 15 Jun 1999 11:07:15 -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 10txby-000MMj-00; Tue, 15 Jun 1999 20:07:02 +0200 From: Sheldon Hearn To: Guido van Rooij Cc: hackers@freebsd.org Subject: Re: inetd+libwrap and wrapping UDP services In-reply-to: Your message of "Tue, 15 Jun 1999 20:05:10 +0200." <19990615200510.A3803@gvr.org> Date: Tue, 15 Jun 1999 20:07:02 +0200 Message-ID: <85976.929470022@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 15 Jun 1999 20:05:10 +0200, Guido van Rooij wrote: > And when you fix that, the wrapper stuff gets invoked for every > packet... Even worse than I anticipated. :-) So then we just note in the manpage that only TCP-based services are wrapped? 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 Jun 15 11: 9:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (Postfix) with ESMTP id 4B584152CA; Tue, 15 Jun 1999 11:09:49 -0700 (PDT) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id C35605B98; Tue, 15 Jun 1999 20:09:47 +0200 (MET DST) Message-ID: <19990615200947.B3803@gvr.org> Date: Tue, 15 Jun 1999 20:09:47 +0200 From: Guido van Rooij To: Matthew Dillon , Matthew Jacob Cc: freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: D'oh! References: <199906151737.KAA19611@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199906151737.KAA19611@apollo.backplane.com>; from Matthew Dillon on Tue, Jun 15, 1999 at 10:37:18AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 15, 1999 at 10:37:18AM -0700, Matthew Dillon wrote: > > Sounds good to me! If someone on -hackers has easy access to the OpenBSD > source, it would be nice if he could check whether the OpenBSD code > has the same problem and notify the OpenBSD folks if it does. they dont seem to have the nfs_node_hash_lock at all. Our code in nfs_nget(): loop: for (np = nhpp->lh_first; np != 0; np = np->n_hash.le_next) { if (mntp != NFSTOV(np)->v_mount || np->n_fhsize != fhsize || bcmp((caddr_t)fhp, (caddr_t)np->n_fhp, fhsize)) continue; vp = NFSTOV(np); if (vget(vp, 1)) goto loop; *npp = np; return(0); } /* * Obtain a lock to prevent a race condition if the getnewvnode() * or MALLOC() below happens to block. */ if (nfs_node_hash_lock) { while (nfs_node_hash_lock) { nfs_node_hash_lock = -1; tsleep(&nfs_node_hash_lock, PVM, "nfsngt", 0); } nfs_node_hash_lock = 1; /* * Do the MALLOC before the getnewvnode since doing so afterward * might cause a bogus v_data pointer to get dereferenced * elsewhere if MALLOC should block. */ MALLOC(np, struct nfsnode *, sizeof *np, M_NFSNODE, M_WAITOK); error = getnewvnode(VT_NFS, mntp, nfsv2_vnodeop_p, &nvp); Their code: loop: for (np = nhpp->lh_first; np != 0; np = np->n_hash.le_next) { if (mntp != NFSTOV(np)->v_mount || np->n_fhsize != fhsize || bcmp((caddr_t)fhp, (caddr_t)np->n_fhp, fhsize)) continue; vp = NFSTOV(np); if (vget(vp, LK_EXCLUSIVE, p)) goto loop; *npp = np; return(0); } error = getnewvnode(VT_NFS, mntp, nfsv2_vnodeop_p, &nvp); if (error) { *npp = 0; return (error); } vp = nvp; MALLOC(np, struct nfsnode *, sizeof *np, M_NFSNODE, M_WAITOK); I have not checked if they have fixed this otherwise though. -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 11:10:47 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 56D4415601 for ; Tue, 15 Jun 1999 11:10:35 -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 10txfC-000MPb-00; Tue, 15 Jun 1999 20:10:22 +0200 From: Sheldon Hearn To: Guido van Rooij Cc: hackers@freebsd.org Subject: Re: inetd+libwrap and wrapping UDP services In-reply-to: Your message of "Tue, 15 Jun 1999 20:07:02 +0200." <85976.929470022@axl.noc.iafrica.com> Date: Tue, 15 Jun 1999 20:10:22 +0200 Message-ID: <86154.929470222@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 15 Jun 1999 20:07:02 +0200, Sheldon Hearn wrote: > So then we just note in the manpage that only TCP-based services are > wrapped? And don't even _think_ about telling me that the phrase "Support is provided for TCP Wrappers" doesn't say anything about UDP. ;-) 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 Jun 15 11:10:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 1983915543; Tue, 15 Jun 1999 11:10:57 -0700 (PDT) From: "Jonathan M. Bresler" To: hackers@FreeBSD.ORG Subject: PATCH for NE2000 driver--if_ed.c Message-Id: <19990615181057.1983915543@hub.freebsd.org> Date: Tue, 15 Jun 1999 11:10:57 -0700 (PDT) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG patch adds support for the Linksys 10/100 PCMCIA card if you have a NE2000 type card which is supported by if_ed.c, please apply this patch and provide feedback. it work wonderfully for me, but i have only two cards that use this driver.....there are a wide variety of cards that use the if_ed.c driver. i want to make sure of the change before committing it. *** /sys/i386/isa/if_ed.c.orig Tue Jan 2 05:33:53 1990 --- /sys/i386/isa/if_ed.c Sun Jun 6 06:59:40 1999 *************** *** 193,198 **** --- 193,200 ---- static u_long ds_crc __P((u_char *ep)); + static int ed_get_Linksys __P((struct ed_softc *)); + #if (NCARD > 0) || (NPNP > 0) #include #endif *************** *** 410,415 **** --- 412,435 ---- return (1); } + static int + ed_get_Linksys(sc) + struct ed_softc *sc; + { + u_char sum; + int i; + + for (sum = 0, i = 0x14; i < 0x1c; i++) + sum += inb(sc->nic_addr +i); + if (sum != 0xff) + return (0); + for (i = 0; i < ETHER_ADDR_LEN; i++) { + sc->arpcom.ac_enaddr[i] = inb(sc->nic_addr + 0x14 + i); + printf("%02x.", sc->arpcom.ac_enaddr[i]); + } + return (1); + } + /* * Probe and vendor-specific initialization routine for SMC/WD80x3 boards */ *************** *** 1072,1077 **** --- 1092,1098 ---- u_char romdata[16], tmp; static char test_pattern[32] = "THIS is A memory TEST pattern"; char test_buffer[32]; + int linksys = 0; sc->asic_addr = port + ED_NOVELL_ASIC_OFFSET; sc->nic_addr = port + ED_NOVELL_NIC_OFFSET; *************** *** 1141,1147 **** ed_pio_writemem(sc, test_pattern, 8192, sizeof(test_pattern)); ed_pio_readmem(sc, 8192, test_buffer, sizeof(test_pattern)); ! if (bcmp(test_pattern, test_buffer, sizeof(test_pattern))) { /* not an NE1000 - try NE2000 */ outb(sc->nic_addr + ED_P0_DCR, ED_DCR_WTS | ED_DCR_FT1 | ED_DCR_LS); --- 1162,1174 ---- ed_pio_writemem(sc, test_pattern, 8192, sizeof(test_pattern)); ed_pio_readmem(sc, 8192, test_buffer, sizeof(test_pattern)); ! linksys = ed_get_Linksys(sc); ! if (linksys) { ! outb(sc->nic_addr + ED_P0_DCR, ED_DCR_WTS | ED_DCR_FT1 | ED_DCR_LS); ! sc->isa16bit = 1; ! sc->type = ED_TYPE_NE2000; ! sc->type_str = "Linksys"; ! } else if (bcmp(test_pattern, test_buffer, sizeof(test_pattern))) { /* not an NE1000 - try NE2000 */ outb(sc->nic_addr + ED_P0_DCR, ED_DCR_WTS | ED_DCR_FT1 | ED_DCR_LS); *************** *** 1251,1269 **** * Use one xmit buffer if < 16k, two buffers otherwise (if not told * otherwise). */ ! if ((memsize < 16384) || (flags & ED_FLAGS_NO_MULTI_BUFFERING)) sc->txb_cnt = 1; else sc->txb_cnt = 2; sc->rec_page_start = sc->tx_page_start + sc->txb_cnt * ED_TXBUF_SIZE; ! sc->rec_page_stop = sc->tx_page_start + memsize / ED_PAGE_SIZE; sc->mem_ring = sc->mem_start + sc->txb_cnt * ED_PAGE_SIZE * ED_TXBUF_SIZE; ! ! ed_pio_readmem(sc, 0, romdata, 16); ! for (n = 0; n < ETHER_ADDR_LEN; n++) ! sc->arpcom.ac_enaddr[n] = romdata[n * (sc->isa16bit + 1)]; #ifdef GWETHER if (sc->arpcom.ac_enaddr[2] == 0x86) { --- 1278,1298 ---- * Use one xmit buffer if < 16k, two buffers otherwise (if not told * otherwise). */ ! if ((sc->mem_size < 16384) || (flags & ED_FLAGS_NO_MULTI_BUFFERING)) sc->txb_cnt = 1; else sc->txb_cnt = 2; sc->rec_page_start = sc->tx_page_start + sc->txb_cnt * ED_TXBUF_SIZE; ! n = sc->tx_page_start + sc->mem_size / ED_PAGE_SIZE; ! sc->rec_page_stop = (n > 0xff) ? 0xff : n; sc->mem_ring = sc->mem_start + sc->txb_cnt * ED_PAGE_SIZE * ED_TXBUF_SIZE; ! if (!linksys) { ! ed_pio_readmem(sc, 0, romdata, 16); ! for (n = 0; n < ETHER_ADDR_LEN; n++) ! sc->arpcom.ac_enaddr[n] = romdata[n * (sc->isa16bit + 1)]; ! } #ifdef GWETHER if (sc->arpcom.ac_enaddr[2] == 0x86) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 11:11:52 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 3924715709; Tue, 15 Jun 1999 11:11:46 -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 LAA19634; Tue, 15 Jun 1999 11:11:36 -0700 Date: Tue, 15 Jun 1999 11:11:24 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Guido van Rooij Cc: Matthew Dillon , freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: D'oh! In-Reply-To: <19990615200947.B3803@gvr.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 Yes, I looked at it. It's also true that we both (OpenBSD/FreeBSD) have a small memory leak too in this case. NetBSD has none of the problems. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 11:12: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (Postfix) with ESMTP id 6B39315641 for ; Tue, 15 Jun 1999 11:12:04 -0700 (PDT) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id 880845B92; Tue, 15 Jun 1999 20:12:03 +0200 (MET DST) Message-ID: <19990615201203.C3803@gvr.org> Date: Tue, 15 Jun 1999 20:12:03 +0200 From: Guido van Rooij To: Sheldon Hearn Cc: hackers@freebsd.org Subject: Re: inetd+libwrap and wrapping UDP services References: <19990615200510.A3803@gvr.org> <85976.929470022@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <85976.929470022@axl.noc.iafrica.com>; from Sheldon Hearn on Tue, Jun 15, 1999 at 08:07:02PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 15, 1999 at 08:07:02PM +0200, Sheldon Hearn wrote: > > > On Tue, 15 Jun 1999 20:05:10 +0200, Guido van Rooij wrote: > > > And when you fix that, the wrapper stuff gets invoked for every > > packet... > > Even worse than I anticipated. :-) > > So then we just note in the manpage that only TCP-based services are > wrapped? Hmmm..I would just enable the UDP stuff. It is a policy issue, so why not at least giving the functionality. I woul however note in the manpage what the consequences are for nowait UDP services. While you're at it, I'd alos mention what the consequence of the wait option is (i.e. wrapper only for the starting connection). -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 11:12:40 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 BF46B1573F; Tue, 15 Jun 1999 11:12:34 -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 MAA48220; Tue, 15 Jun 1999 12:12:32 -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 MAA93558; Tue, 15 Jun 1999 12:12:21 -0600 (MDT) Message-Id: <199906151812.MAA93558@harmony.village.org> To: Mitsuru IWASAKI Subject: Re: apmd for FreeBSD Cc: freebsd-hackers@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Wed, 16 Jun 1999 02:48:42 +0900." <199906151750.CAA23758@tasogare.imasy.or.jp> References: <199906151750.CAA23758@tasogare.imasy.or.jp> <199906150556.XAA90154@harmony.village.org> Date: Tue, 15 Jun 1999 12:12:21 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199906151750.CAA23758@tasogare.imasy.or.jp> Mitsuru IWASAKI writes: : Thanks a lot for your testing. : I'm preparing -current NotePC for testing this. You are most welcome. I'm glad that I could be of assistance. I've wanted something like this for a long time, but never found the time to implement it. : imp> P.S. I've put my diffs vs -current at : imp> http://www.freebsd.org/~imp/apmd-sys-current.diff.gz : : Thanks. Give my kind regards. No problem. I'm glad that I could be of assistance. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 11:15:23 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 33A9115647; Tue, 15 Jun 1999 11:15:20 -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 LAA19654; Tue, 15 Jun 1999 11:15:12 -0700 Date: Tue, 15 Jun 1999 11:14:59 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Guido van Rooij Cc: Matthew Dillon , freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG Subject: to be more precise... In-Reply-To: <19990615200947.B3803@gvr.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 The actual code of interest is: FreeBSD: * $Id: nfs_node.c,v 1.28.2.1 1999/06/07 00:04:05 peter Exp $ or * $Id: nfs_node.c,v 1.29 1999/06/05 05:26:36 peter Exp $ ... /* * Insert the nfsnode in the hash queue for its new file handle */ for (np2 = nhpp->lh_first; np2 != 0; np2 = np2->n_hash.le_next) { if (mntp != NFSTOV(np)->v_mount || np2->n_fhsize != fhsize || bcmp((caddr_t)fhp, (caddr_t)np2->n_fhp, fhsize)) continue; vrele(vp); goto retry; } OpenBSD: /* $OpenBSD: nfs_node.c,v 1.13 1999/04/28 09:28:17 art Exp $ */ ... /* * Insert the nfsnode in the hash queue for its new file handle */ for (np2 = nhpp->lh_first; np2 != 0; np2 = np2->n_hash.le_next) { if (vp->v_mount != NFSTOV(np2)->v_mount || fhsize != np2->n_fhsize || bcmp((caddr_t)fhp, (caddr_t)np2->n_fhp, fhsize)) continue; vrele(vp); goto retry; } For OpenBSD and FreeBSD it's a memory leak for the allocated nfsnode *np. For FreeBSD it's also the locking foop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 13:10:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.CDROM.com (unknown [155.40.64.166]) by hub.freebsd.org (Postfix) with ESMTP id 093FD14F3A; Tue, 15 Jun 1999 13:10:23 -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 NAA12531; Tue, 15 Jun 1999 13:06:41 -0700 (PDT) (envelope-from mike@dingo.CDROM.com) Message-Id: <199906152006.NAA12531@dingo.CDROM.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: Matthew Jacob , freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: D'oh! In-reply-to: Your message of "Tue, 15 Jun 1999 10:29:07 PDT." <199906151729.KAA19516@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Jun 1999 13:06:40 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem is that peter is not releasing the nfs_node_hash_lock > when he goes to retry, creating a deadlock with himself. > > Peter, looks like a quick fix & commit to me, I'd say just go ahead > and do it. Peter is sic transit mundi at the moment, having missed his original flight back from Usenix. This probably calls for another committer (eg. one of the Matts...) -- \\ 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 Tue Jun 15 13:18:10 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 CFBF515429; Tue, 15 Jun 1999 13:18:07 -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 NAA55681; Tue, 15 Jun 1999 13:17:33 -0700 (PDT) Date: Tue, 15 Jun 1999 13:17:32 -0700 (PDT) From: Julian Elischer To: Mike Smith Cc: Matthew Dillon , Matthew Jacob , freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: D'oh! In-Reply-To: <199906152006.NAA12531@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 Tue, 15 Jun 1999, Mike Smith wrote: > Peter is sic transit mundi at the moment, having missed his original > flight back from Usenix. This probably calls for another committer > (eg. one of the Matts...) Hmm, a choice of 1 out of 1 unless I missed somthing Peter is sick in transit to mundi? where's mundi? lemme see.. sounds like one of the machines at monash uni. munnari, mullet, mundi.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 13:36: 6 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 5E18714F46; Tue, 15 Jun 1999 13:35: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 GAA23099; Wed, 16 Jun 1999 06:05:54 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id GAA10794; Wed, 16 Jun 1999 06:05:56 +0930 (CST) Date: Wed, 16 Jun 1999 06:05:55 +0930 From: Greg Lehey To: garret.white@nokia.com Cc: FreeBSD Hackers Subject: Device drivers (was: looking for a reference manual) Message-ID: <19990616060554.P521@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 garret.white@nokia.com on Tue, Jun 15, 1999 at 08:51:59PM +0300 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 [moved to -hackers; this is more appropriate there] On Tuesday, 15 June 1999 at 20:51:59 +0300, garret.white@nokia.com wrote: > > Hi All! > > I'm looking to write device drivers for FreeBSD. To this end, I'm searching > for a Driver-Kernel interface reference manual for FreeBSD (ordinary BSD > should do). (You know, a reference that documents all the low-level library > calls and such.) I have one for SVR4 but I'm having trouble finding one for > BSD. Anyone know of one? There's nothing that corresponds directly to the System V DDI/DKI manual. Some (but unfortunately not all) kernel functions and structures are described in section 9 of the manual. Look at intro(9) for a start. There's also a tutorial at http://www.freebsd.org/tutorials/ddwg/ddwg.html. But you'll find that you'll have to read a lot of other driver code before you get your driver finished. 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 Tue Jun 15 13:45: 1 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 3513414F56 for ; Tue, 15 Jun 1999 13:44:58 -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 NAA57058; Tue, 15 Jun 1999 13:44:44 -0700 (PDT) Date: Tue, 15 Jun 1999 13:44:43 -0700 (PDT) From: Julian Elischer To: Greg Lehey Cc: garret.white@nokia.com, FreeBSD Hackers Subject: Re: Device drivers (was: looking for a reference manual) In-Reply-To: <19990616060554.P521@freebie.lemis.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 you can also find samples in /usr/share/examples/drivers. These may be slightly broken in 4.x On Wed, 16 Jun 1999, Greg Lehey wrote: > [moved to -hackers; this is more appropriate there] > > On Tuesday, 15 June 1999 at 20:51:59 +0300, garret.white@nokia.com wrote: > > > > Hi All! > > > > I'm looking to write device drivers for FreeBSD. To this end, I'm searching > > for a Driver-Kernel interface reference manual for FreeBSD (ordinary BSD > > should do). (You know, a reference that documents all the low-level library > > calls and such.) I have one for SVR4 but I'm having trouble finding one for > > BSD. Anyone know of one? > > There's nothing that corresponds directly to the System V DDI/DKI > manual. Some (but unfortunately not all) kernel functions and > structures are described in section 9 of the manual. Look at intro(9) > for a start. There's also a tutorial at > http://www.freebsd.org/tutorials/ddwg/ddwg.html. But you'll find that > you'll have to read a lot of other driver code before you get your > driver finished. > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 13:55:50 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 CBADB156D6; Tue, 15 Jun 1999 13:55:45 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA20771; Tue, 15 Jun 1999 13:55:42 -0700 (PDT) (envelope-from dillon) Date: Tue, 15 Jun 1999 13:55:42 -0700 (PDT) From: Matthew Dillon Message-Id: <199906152055.NAA20771@apollo.backplane.com> To: Matthew Jacob Cc: Guido van Rooij , freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Holy cow - path component freeing a mess? (was Re: D'oh!) References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is totally screwed up: The rules used to determine whether a path component buffer ( struct componentname, sys/namei.h ) is freed by a VOP routine or not are idiotic. As far as I can tell, the rule is: * if no error is returned free the path component buffer, but only if the SAVESTART flag is not set. * If an error is returned, free the path component buffer whether SAVESTART is set or not. Combine this with the callers which decide whether to set SAVESTART, and the result is an extremely fragile mess. Combine this with VOP_ABORTOP's operation ( which frees the path component if SAVESTART is not set ) and it gets even worse. Confused yet? At the very least, anyone who zfree's a path component should clear the HASBUF flag so sanity checks can be added to the code. The nfs_serv.c code is unnecessarily complex due to this junkiness. I would like to fix this in the tree and add sanity checks. -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 Jun 15 14: 3:23 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 4B16C155D3 for ; Tue, 15 Jun 1999 14:03:17 -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 RAA10075; Tue, 15 Jun 1999 17:03:37 -0400 (EDT) Message-Id: X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Tue, 15 Jun 1999 15:42:27 -0400 To: hackers@freebsd.org From: Dennis Subject: Intel 82559 Suppored? Cc: dg@root.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is the 82559 ethernet controller supported under Freebsd 3.2? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 14:10: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id DBEA3155D3 for ; Tue, 15 Jun 1999 14:09:57 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id OAA01965; Tue, 15 Jun 1999 14:09:41 -0700 (PDT) Message-Id: <199906152109.OAA01965@implode.root.com> To: Dennis Cc: hackers@freebsd.org Subject: Re: Intel 82559 Suppored? In-reply-to: Your message of "Tue, 15 Jun 1999 15:42:27 EDT." From: David Greenman Reply-To: dg@root.com Date: Tue, 15 Jun 1999 14:09:41 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Is the 82559 ethernet controller supported under Freebsd 3.2? Yes. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 14:23:37 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 BDF8414CE7; Tue, 15 Jun 1999 14:23:32 -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 OAA20120; Tue, 15 Jun 1999 14:23:30 -0700 Date: Tue, 15 Jun 1999 14:23:24 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Matthew Dillon Cc: Guido van Rooij , freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: Holy cow - path component freeing a mess? (was Re: D'oh!) In-Reply-To: <199906152055.NAA20771@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 Umm, okay.... but I'm a little confused about how the zfree I'm adding to nfs_nget falls under this. Am I being really stupid here? On Tue, 15 Jun 1999, Matthew Dillon wrote: > This is totally screwed up: The rules used to determine whether > a path component buffer ( struct componentname, sys/namei.h ) is freed > by a VOP routine or not are idiotic. > > As far as I can tell, the rule is: > > * if no error is returned free the path component buffer, but only > if the SAVESTART flag is not set. > > * If an error is returned, free the path component buffer whether > SAVESTART is set or not. > > Combine this with the callers which decide whether to set SAVESTART, > and the result is an extremely fragile mess. Combine this with > VOP_ABORTOP's operation ( which frees the path component if SAVESTART is > not set ) and it gets even worse. > > Confused yet? > > At the very least, anyone who zfree's a path component should > clear the HASBUF flag so sanity checks can be added to the code. The > nfs_serv.c code is unnecessarily complex due to this junkiness. > > I would like to fix this in the tree and add sanity checks. > > -Matt > Matthew Dillon > > > > 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 Jun 15 14:39:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 710F914C2E; Tue, 15 Jun 1999 14:39:13 -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 OAA61487; Tue, 15 Jun 1999 14:39:02 -0700 (PDT) Date: Tue, 15 Jun 1999 14:39:00 -0700 (PDT) From: Julian Elischer To: Matthew Dillon Cc: Matthew Jacob , Guido van Rooij , freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: Holy cow - path component freeing a mess? (was Re: D'oh!) In-Reply-To: <199906152055.NAA20771@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 talk to terry on this topic :-) He has a set of patches that straighten all this out julian On Tue, 15 Jun 1999, Matthew Dillon wrote: > This is totally screwed up: The rules used to determine whether > a path component buffer ( struct componentname, sys/namei.h ) is freed > by a VOP routine or not are idiotic. > > As far as I can tell, the rule is: > > * if no error is returned free the path component buffer, but only > if the SAVESTART flag is not set. > > * If an error is returned, free the path component buffer whether > SAVESTART is set or not. > > Combine this with the callers which decide whether to set SAVESTART, > and the result is an extremely fragile mess. Combine this with > VOP_ABORTOP's operation ( which frees the path component if SAVESTART is > not set ) and it gets even worse. > > Confused yet? > > At the very least, anyone who zfree's a path component should > clear the HASBUF flag so sanity checks can be added to the code. The > nfs_serv.c code is unnecessarily complex due to this junkiness. > > I would like to fix this in the tree and add sanity checks. > > -Matt > Matthew Dillon > > > > 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 Jun 15 14:47:12 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 913E414D8B; Tue, 15 Jun 1999 14:47:10 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA21028; Tue, 15 Jun 1999 14:47:07 -0700 (PDT) (envelope-from dillon) Date: Tue, 15 Jun 1999 14:47:07 -0700 (PDT) From: Matthew Dillon Message-Id: <199906152147.OAA21028@apollo.backplane.com> To: Matthew Jacob Cc: Guido van Rooij , freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: Holy cow - path component freeing a mess? (was Re: D'oh!) References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Umm, okay.... but I'm a little confused about how the zfree I'm adding to :nfs_nget falls under this. Am I being really stupid here? it's unrelated. I was starting a new thread. I have finished fixing up nfs_serv.c and am now testing it. Most of the procedures required significant adjustments to catch all the problems - mainly due to the various NFS macros in nfsm_subs.h doing 'goto nfsmout;'. -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 Jun 15 14:54: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 E57BF14D84; Tue, 15 Jun 1999 14:54:33 -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 RAA39862; Tue, 15 Jun 1999 17:54:14 -0400 (EDT) Message-Id: <199906152154.RAA39862@cs.rpi.edu> To: Matthew Dillon Cc: Matthew Jacob , Guido van Rooij , freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: Holy cow - path component freeing a mess? (was Re: D'oh!) In-Reply-To: Message from Matthew Dillon of "Tue, 15 Jun 1999 14:47:07 PDT." <199906152147.OAA21028@apollo.backplane.com> Date: Tue, 15 Jun 1999 17:54:14 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :Umm, okay.... but I'm a little confused about how the zfree I'm adding to > :nfs_nget falls under this. Am I being really stupid here? > > it's unrelated. I was starting a new thread. > > I have finished fixing up nfs_serv.c and am now testing it. Most of > the procedures required significant adjustments to catch all the > problems - mainly due to the various NFS macros in nfsm_subs.h doing > 'goto nfsmout;'. Way to go! I was hoping this would happen... it is the miracle of Open Source. I am a bit sad that I'm not doing any of the stuff now though :(, you guys are just too gosh darn quick. Seriously though... when are we likely to see this stuff hit -STABLE? I would like to to dig through your nfs_serv.c at some point before it gets commited too. There are a couple of other NFSv3 bugs that I have been tracking and I would like to see if this addresses those. -- 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 Jun 15 14:59: 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 239B9153EC; Tue, 15 Jun 1999 14:58:57 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA21113; Tue, 15 Jun 1999 14:58:55 -0700 (PDT) (envelope-from dillon) Date: Tue, 15 Jun 1999 14:58:55 -0700 (PDT) From: Matthew Dillon Message-Id: <199906152158.OAA21113@apollo.backplane.com> To: "David E. Cross" Cc: Matthew Jacob , Guido van Rooij , freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: Holy cow - path component freeing a mess? (was Re: D'oh!) References: <199906152154.RAA39862@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Way to go! I was hoping this would happen... it is the miracle of Open Source. :I am a bit sad that I'm not doing any of the stuff now though :(, you guys :are just too gosh darn quick. : :Seriously though... when are we likely to see this stuff hit -STABLE? I would :like to to dig through your nfs_serv.c at some point before it gets commited :too. There are a couple of other NFSv3 bugs that I have been tracking and I :would like to see if this addresses those. : :-- :David Cross | email: crossd@cs.rpi.edu The differences between -current and -stable for nfs_serv.c and nfs_subs.c are relatively minor. Once we've life tested the hell out of it in current, it should be easy to MFC into stable. Maybe 3 weeks total. -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 Jun 15 15: 5: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 ACB6814D84; Tue, 15 Jun 1999 15:05:55 -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 SAA39993; Tue, 15 Jun 1999 18:05:44 -0400 (EDT) Message-Id: <199906152205.SAA39993@cs.rpi.edu> To: Matthew Dillon Cc: "David E. Cross" , Matthew Jacob , Guido van Rooij , freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: Holy cow - path component freeing a mess? (was Re: D'oh!) In-Reply-To: Message from Matthew Dillon of "Tue, 15 Jun 1999 14:58:55 PDT." <199906152158.OAA21113@apollo.backplane.com> Date: Tue, 15 Jun 1999 18:05:43 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The differences between -current and -stable for nfs_serv.c and nfs_subs.c > are relatively minor. Once we've life tested the hell out of it in > current, it should be easy to MFC into stable. Maybe 3 weeks total. Hmm... that is a bit long for us... 3 weeks, 21 days at 1.7 day/panic = 0.59 Panic/Day == 21 (day) * 0.59(day/panic) [remeber to check your units ;] that's another 12 panics for us (if they keep up at the current rate). Luckily since we have backed down to NFSv2 we are a bit more stable. The only reason the server went down today is because the IDE disk decided to flake out. It was amazing, even though the OS disk was dead it still continued to serve some NFS requests (from different partitions of course :) Don't get me wrong, I agree this is the correct procedure, but I plan to roll my own nfs_serv.c untill it gets MFC-ed... and I'll be able to provide you with some real world test results of the new code on -STABLE. -- 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 Jun 15 16:22:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp4.erols.com (smtp4.erols.com [207.172.3.237]) by hub.freebsd.org (Postfix) with ESMTP id 1560114F2A for ; Tue, 15 Jun 1999 16:22:06 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (207-172-143-242.s51.as3.hgt.md.dialup.rcn.com [207.172.143.242]) by smtp4.erols.com (8.8.8/smtp-v1) with ESMTP id TAA15620; Tue, 15 Jun 1999 19:21:48 -0400 (EDT) Message-Id: <199906152321.TAA15620@smtp4.erols.com> 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: Tue, 15 Jun 1999 19:21:48 -0400 (EDT) From: John Baldwin To: "Daniel J. O'Connor" Subject: RE: DHCP, arp and de0 Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Jun-99 Daniel J. O'Connor wrote: > Hi, > I have tried getting my system to use DHCP on my local network, but I'm > having > trouble. > If I don't use DHCP everything works fine, but if I use DHCP I get the > following messages appearing in my log file when I use ESD, and try and ping > my LAN IP. > Jun 13 17:35:21 guppy /kernel: arplookup 127.0.0.1 failed: could not allocate > llinfo > Jun 13 17:35:21 guppy /kernel: arpresolve: can't allocate llinfo for > 127.0.0.1rt > > I notcied also that the arp table doesn't have an entry for my IP when I use > DHCP. When I don't use DHCP I have a line like > guppy.dons.net.au (203.31.81.9) at 0:80:ad:16:77:3e permanent [ethernet] > > in the arp table, but its not there when I use DHCP. I can't add it by hand > either. > > I am running -current as of this morning (ie 12 Jun 10:30am GMT), and I have > a > Digital 21140 base 10/100 card. It has 2 ports, one for 10 and the other for > 100 mbits (lame). Personally I suspect the driver since I've had other > strangness with arp and this card when I try and change media, but I could be > way off base. > > Any ideas? Are you using the built-in dhcp client (/sbin/dhclient)? If so, what does the output look like during boot up? What does 'ifconfig -i de0' show? Also, do you have a lease in /var/db/dhcp.leases? --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 16:23:32 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 643DE14C32; Tue, 15 Jun 1999 16:23:27 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA23668; Tue, 15 Jun 1999 16:23:25 -0700 (PDT) (envelope-from dillon) Date: Tue, 15 Jun 1999 16:23:25 -0700 (PDT) From: Matthew Dillon Message-Id: <199906152323.QAA23668@apollo.backplane.com> To: "David E. Cross" Cc: Matthew Jacob , Guido van Rooij , freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: Holy cow - path component freeing a mess? (was Re: D'oh!) References: <199906152205.SAA39993@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hmm... that is a bit long for us... 3 weeks, 21 days at 1.7 day/panic = :0.59 Panic/Day == 21 (day) * 0.59(day/panic) [remeber to check your units ;] :... :David Cross | email: crossd@cs.rpi.edu I'll have patches on my site in a few days. I just meant time till it was actually committed into -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 Tue Jun 15 16:44:21 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 B87A314C32 for ; Tue, 15 Jun 1999 16:44:17 -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 JAA10155; Wed, 16 Jun 1999 09:14:03 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199906152344.JAA10155@gizmo.internode.com.au> Subject: Re: [Call for review] init(8): new feature To: adsharma@home.com (Arun Sharma) Date: Wed, 16 Jun 1999 09:14:03 +0930 (CST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Arun Sharma" at Jun 15, 99 08:59:59 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 Arun Sharma wrote: > While we're on the init topic, is there any strong feeling here about > BSD /etc/rc* scripts Vs SysV ? The nice thing about SysV initscripts > is the ability to start and stop any service that I like. That's fine -- there are lots of ways to start and stop any service you like without involving SysV init. - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 18:29:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id B80A2151FE for ; Tue, 15 Jun 1999 18:29:48 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA06254; Wed, 16 Jun 1999 10:59:28 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199906152321.TAA15620@smtp4.erols.com> Date: Wed, 16 Jun 1999 10:59:28 +0930 (CST) From: "Daniel O'Connor" To: John Baldwin Subject: RE: DHCP, arp and de0 Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15-Jun-99 John Baldwin wrote: > Are you using the built-in dhcp client (/sbin/dhclient)? If so, what does > output look like during boot up? What does 'ifconfig -i de0' show? Also, > you have a lease in /var/db/dhcp.leases? I am using /sbin/dhclient de0 to get a lease, and the config file is empty except for comments. The output looks OK when it boots up, but I don't have an exact copy. It DOES get a lease fine, but for some reason it isn't entered into the arp table :( Err.. ifconfig -i de0 isn't legal :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 18:35:19 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 A4D6B15474; Tue, 15 Jun 1999 18:35:08 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-15-185.dialup.HiWAAY.net [216.180.15.185]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id UAA15224; Tue, 15 Jun 1999 20:35:05 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id TAA40317; Tue, 15 Jun 1999 19:47:42 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199906160047.TAA40317@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Josef Karthauser Cc: Roger Hardiman , multimedia@FreeBSD.org, hackers@FreeBSD.org, sos@FreeBSD.org From: David Kelly Subject: Re: IR Remote for AverMedia and FlyVideo In-reply-to: Message from Josef Karthauser of "Tue, 15 Jun 1999 11:25:12 BST." <19990615112512.A71377@pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Jun 1999 19:47:42 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josef Karthauser writes: > > I've got a phototransistor plugged into my DTR line on the serial > port. Is there any working software for FreeBSD for utilising this? > (I want to never lose a remote control again!) Oh My Goodness! I don't know whether to laugh or cry. Can somebody get me started with links to whatever online IR technology is out there? I am in need of a bunch of IR remote control units which can be controlled via serial port or other simple computerized means. While in the past One For All made inexpensive IR remote controls with a serial port, they changed the design about 4 years ago and refused to publish the spec. Do not know if they still include any kind of serial port in current models. Wouldn't do me any good unless I have documentation. As for "phototransistor plugged into my DTR line", this is a job for a $2 microcontroller, not a task for a multiuser multitasking OS. I *think* you can start at http://www.mcu.motsps.com/ and follow the 68HC05 family and find a reference design using a 68HC705K IR controller. It is a very simple design and does very few commands. Its not intented to be a "build to print IR controller." Only a example to get one started. The code is given for generating IR commands. The 68HC705K family features IRQ and pullups on some of its I/O pins allowing one to connect to a keyboard with zero external components. Probably would want to substitute another '05, possibly one with a serial port. Other Motorola app notes provide example code to implement UARTs in software. Also at the same site is a DOS-based 68HC05 assembler. I've been meaning to see if it runs under doscmd. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 18:39:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from maxwell.syr.edu (maxwell.syr.edu [128.230.129.5]) by hub.freebsd.org (Postfix) with ESMTP id F418615423; Tue, 15 Jun 1999 18:39:36 -0700 (PDT) (envelope-from cmsedore@maxwell.syr.edu) Received: from exchange.maxwell.syr.edu (exchange.maxwell.syr.edu [128.230.129.241]) by maxwell.syr.edu (8.9.1a/8.9.1) with ESMTP id UAA12440; Tue, 15 Jun 1999 20:17:11 GMT Received: by exchange.maxwell.syr.edu with Internet Mail Service (5.5.1960.3) id ; Tue, 15 Jun 1999 21:39:28 -0400 Message-ID: <262C3DA9BE0CD211971700A0C9B413A1CD04@exchange.maxwell.syr.edu> From: Christopher Sedore To: "'David Kelly'" , Josef Karthauser Cc: Roger Hardiman , multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG, sos@FreeBSD.ORG Subject: RE: IR Remote for AverMedia and FlyVideo Date: Tue, 15 Jun 1999 21:39:27 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I bought a one-for-all remote that I drove from FreeBSD just in the last year or two. You might try www.smarthome.com. I bought the remote, cable, and docs for how to use it for under US $100. They also have RS232 learning IR devices for $180. Expensive, but I wasn't willing to do the electronics work. -Chris > -----Original Message----- > From: David Kelly [SMTP:dkelly@HiWAAY.net] > Sent: Tuesday, June 15, 1999 8:48 PM > To: Josef Karthauser > Cc: Roger Hardiman; multimedia@FreeBSD.ORG; hackers@FreeBSD.ORG; > sos@FreeBSD.ORG > Subject: Re: IR Remote for AverMedia and FlyVideo > > Josef Karthauser writes: > > > > I've got a phototransistor plugged into my DTR line on the serial > > port. Is there any working software for FreeBSD for utilising this? > > (I want to never lose a remote control again!) > > Oh My Goodness! I don't know whether to laugh or cry. > > Can somebody get me started with links to whatever online IR > technology > is out there? I am in need of a bunch of IR remote control units which > > can be controlled via serial port or other simple computerized means. > > While in the past One For All made inexpensive IR remote controls with > > a serial port, they changed the design about 4 years ago and refused > to > publish the spec. Do not know if they still include any kind of serial > > port in current models. Wouldn't do me any good unless I have > documentation. > > As for "phototransistor plugged into my DTR line", this is a job for a > $2 microcontroller, not a task for a multiuser multitasking OS. I > *think* you can start at http://www.mcu.motsps.com/ and follow the > 68HC05 family and find a reference design using a 68HC705K IR > controller. It is a very simple design and does very few commands. Its > not intented to be a "build to print IR controller." Only a example to > get one started. The code is given for generating IR commands. The > 68HC705K family features IRQ and pullups on some of its I/O pins > allowing one to connect to a keyboard with zero external components. > Probably would want to substitute another '05, possibly one with a > serial port. > > Other Motorola app notes provide example code to implement UARTs in > software. > > Also at the same site is a DOS-based 68HC05 assembler. I've been > meaning to see if it runs under doscmd. > > -- > David Kelly N4HHE, dkelly@nospam.hiwaay.net > ===================================================================== > The human mind ordinarily operates at only ten percent of its > capacity -- the rest is overhead for the operating system. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-multimedia" 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 Jun 15 18:40:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp4.erols.com (smtp4.erols.com [207.172.3.237]) by hub.freebsd.org (Postfix) with ESMTP id 64E8C15447 for ; Tue, 15 Jun 1999 18:40:22 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (207-172-144-4.s4.as4.hgt.md.dialup.rcn.com [207.172.144.4]) by smtp4.erols.com (8.8.8/smtp-v1) with ESMTP id VAA07774; Tue, 15 Jun 1999 21:40:00 -0400 (EDT) Message-Id: <199906160140.VAA07774@smtp4.erols.com> 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: Tue, 15 Jun 1999 21:40:00 -0400 (EDT) From: John Baldwin To: "Daniel O'Connor" Subject: RE: DHCP, arp and de0 Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16-Jun-99 Daniel O'Connor wrote: > > On 15-Jun-99 John Baldwin wrote: >> Are you using the built-in dhcp client (/sbin/dhclient)? If so, what does >> output look like during boot up? What does 'ifconfig -i de0' show? Also, >> you have a lease in /var/db/dhcp.leases? > > I am using /sbin/dhclient de0 to get a lease, and the config file is empty > except for comments. The output looks OK when it boots up, but I don't have > an > exact copy. > > It DOES get a lease fine, but for some reason it isn't entered into the arp > table :( > > Err.. ifconfig -i de0 isn't legal :) Whoops.. just ifconfig de0. Have you tried using the interface? We use dhcp for a lab I help run, and 'arp -a' on the clients does not show an entry for the local de0 card they have installed, but they work fine regardless. Do you have a route for 127.0.0.1 in your route table (netstat -rn), there should be one that just points to itself so, AFAIK, it shouldn't be arp'ing for that address. --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 18:54:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by hub.freebsd.org (Postfix) with ESMTP id 5454214C0A for ; Tue, 15 Jun 1999 18:54:45 -0700 (PDT) (envelope-from justin@walker3.apple.com) Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out1.apple.com (8.8.5/8.8.5) with ESMTP id SAA12956 for ; Tue, 15 Jun 1999 18:54:43 -0700 Received: from scv2.apple.com (scv2.apple.com) by mailgate1.apple.com (mailgate1.apple.com- SMTPRS 2.0.15) with ESMTP id for ; Tue, 15 Jun 1999 18:54:42 -0700 Received: from walker3.apple.com (walker3.apple.com [17.219.24.201]) by scv2.apple.com (8.9.3/8.9.3) with ESMTP id SAA38412 for ; Tue, 15 Jun 1999 18:54:40 -0700 Received: by walker3.apple.com (8.9.1/8.9.1) id SAA00658 for freebsd-hackers@FreeBSD.ORG; Tue, 15 Jun 1999 18:54:47 -0700 (PDT) Message-Id: <199906160154.SAA00658@walker3.apple.com> To: freebsd-hackers@freebsd.org Subject: Re: RE: DHCP, arp and de0 In-Reply-To: Date: Tue, 15 Jun 1999 18:54:40 -0700 From: "Justin C. Walker" Reply-To: justin@apple.com X-Mailer: by Apple MailViewer (2.105.dev) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: John Baldwin > Date: 1999-06-15 16:23:24 -0700 > To: "Daniel J. O'Connor" > Subject: RE: DHCP, arp and de0 > Cc: freebsd-hackers@FreeBSD.ORG > In-reply-to: > X-Priority: 3 (Normal) > Delivered-to: freebsd-hackers@freebsd.org > X-Mailer: XFMail 1.3 [p0] on FreeBSD > X-Loop: FreeBSD.ORG > > > On 13-Jun-99 Daniel J. O'Connor wrote: > > Hi, > > I have tried getting my system to use DHCP on my local network, but I'm > > having > > trouble. > > If I don't use DHCP everything works fine, but if I use DHCP I get the > > following messages appearing in my log file when I use ESD, and try and ping > > my LAN IP. > > Jun 13 17:35:21 guppy /kernel: arplookup 127.0.0.1 failed: could not allocate > > llinfo > > Jun 13 17:35:21 guppy /kernel: arpresolve: can't allocate llinfo for > > 127.0.0.1rt I'm not sure this is relevant, but the loopback address should *not* be fed to ARP. That's attached to the loopback interface (lo0), and shouldn't be seen on any wire. Could be your config is seriously fouled up. Regards, Justin -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | Manager, CoreOS Networking | Men are from Earth. Apple Computer, Inc. | Women are from Earth. 2 Infinite Loop | Deal with it. Cupertino, CA 95014 | *-------------------------------------*-------------------------------* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 19:15:24 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 AAEDC152A7; Tue, 15 Jun 1999 19:15:16 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-15-185.dialup.HiWAAY.net [216.180.15.185]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id VAA05228; Tue, 15 Jun 1999 21:15:14 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id VAA41107; Tue, 15 Jun 1999 21:15:12 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199906160215.VAA41107@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Christopher Sedore Cc: multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG, sos@FreeBSD.ORG From: David Kelly Subject: Re: IR Remote for AverMedia and FlyVideo In-reply-to: Message from Christopher Sedore of "Tue, 15 Jun 1999 21:39:27 EDT." <262C3DA9BE0CD211971700A0C9B413A1CD04@exchange.maxwell.syr.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Jun 1999 21:15:11 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christopher Sedore writes: > I bought a one-for-all remote that I drove from FreeBSD just in the last > year or two. You might try www.smarthome.com. I bought the remote, > cable, and docs for how to use it for under US $100. They also have > RS232 learning IR devices for $180. Expensive, but I wasn't willing to > do the electronics work. Familiar with www.smarthome.com. Bought docs from them when the OFA-6 changed to a newer OFA-6. A problem I've always had with the OFA-6 was that I couldn't "hold a button down" over the serial port. Could only momentarily press it. Found something interesting, http://www.smarthome.com/1143.html, "IBM Home Director X10 Starter Kit." Appears to be software for programming a fancy IR/RF remote control via serial port. Then you can turn the computer off and the remote control will execute preprogramed instructions at the assigned time. $39.95. Now it doesn't really say the IR/RF remote control has the serial port but I don't see anything else. It does say you can turn the computer off after programming your events. So it has to happen outside of the computer. Guess I'm going to have to buy one to find out. On second thought it appears SmartHome is simply not picturing the Home Director controller, which is the component that connects to the PC serial port. Search for "IBM Home Director" on Yahoo! yielded lots of accurate hits. At the moment I don't see a path from the computer to an IR appliance. Maybe there is one. Maybe not. But mostly the IR/RF remote control is there to provide a cordless way for a human to do the X10 stuff. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 19:23:38 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 D7169151A2; Tue, 15 Jun 1999 19:23:36 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA24603; Tue, 15 Jun 1999 19:23:35 -0700 (PDT) (envelope-from dillon) Date: Tue, 15 Jun 1999 19:23:35 -0700 (PDT) From: Matthew Dillon Message-Id: <199906160223.TAA24603@apollo.backplane.com> To: "David E. Cross" , Matthew Jacob , Guido van Rooij , freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG, crossd@cs.rpi.edu Subject: VOP_*() routines, lookup(), and namei() leave garbage pointers on error References: <199906152205.SAA39993@cs.rpi.edu> <199906152323.QAA23668@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bleh. More fragility. VOP_*() routines, lookup(), and namei() leave garbage pointers in nameidata and returned-vnode structures when they return an error. They really ought to NULL-out those garbage pointers. It's on my list to fix. It makes it difficult for the NFS code to keep track of its state. That plus the almost total lack of state tracking for the path name component allocation state, which makes it difficult to sanity-check the zfree's. For example, if lookup() returns an error it may leave an invalid ni_dvp pointer in the nameidata. VOP_SYMLINK returns an invalid vp ( all callers of VOP_SYMLINK just ignore it, but that still doesn't make it right ), and namei() also has similar problems when it returns na error. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 19:29:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id E3C0A151A2 for ; Tue, 15 Jun 1999 19:28:53 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA06770; Wed, 16 Jun 1999 11:57:48 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199906160140.VAA07774@smtp4.erols.com> Date: Wed, 16 Jun 1999 11:57:48 +0930 (CST) From: "Daniel O'Connor" To: John Baldwin Subject: RE: DHCP, arp and de0 Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16-Jun-99 John Baldwin wrote: > Whoops.. just ifconfig de0. Have you tried using the interface? We use > for a lab I help run, and 'arp -a' on the clients does not show an entry for > the local de0 card they have installed, but they work fine regardless. Do > have a route for 127.0.0.1 in your route table (netstat -rn), there should > one that just points to itself so, AFAIK, it shouldn't be arp'ing for that > address. Well I have a netstat -nr from when it was using DHCP and when it wasn't and the only difference is the 'Refs' for 127.0.0.1 was 3 for DHCP and 2 for static. The interface works OK for somethings, but for example I can't run 'esd', and whenever I try and ping the address assigned to the ethernet card I get Jun 13 17:35:21 guppy /kernel: arplookup 127.0.0.1 failed: could not allocate llinfo Jun 13 17:35:21 guppy /kernel: arpresolve: can't allocate llinfo for 127.0.0.1rt every ping packet sent. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 19:29:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 1848D154AE for ; Tue, 15 Jun 1999 19:29:23 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA06784; Wed, 16 Jun 1999 11:58:42 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199906160154.SAA00658@walker3.apple.com> Date: Wed, 16 Jun 1999 11:58:42 +0930 (CST) From: "Daniel O'Connor" To: "Justin C. Walker" Subject: Re: RE: DHCP, arp and de0 Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16-Jun-99 Justin C. Walker wrote: > I'm not sure this is relevant, but the loopback address should > *not* be fed to ARP. That's attached to the loopback interface > (lo0), and shouldn't be seen on any wire. Could be your config is > seriously fouled up. Yes, but how :) The loopback device is configured properly etc.. Its quite strange :-/ --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 19:54:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 64D691549A for ; Tue, 15 Jun 1999 19:54:53 -0700 (PDT) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: from c62443-a.frmt1.sfba.home.com ([24.0.69.165]) by mail.rdc1.sfba.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19990616025453.XEUJ8807.mail.rdc1.sfba.home.com@c62443-a.frmt1.sfba.home.com>; Tue, 15 Jun 1999 19:54:53 -0700 Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.8.7/8.8.7) id TAA01731; Tue, 15 Jun 1999 19:54:52 -0700 To: Mark Newton Cc: hackers@FreeBSD.ORG Subject: Re: [Call for review] init(8): new feature References: <199906152344.JAA10155@gizmo.internode.com.au> From: Arun Sharma Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: 15 Jun 1999 19:54:51 -0700 In-Reply-To: Mark Newton's message of "Wed, 16 Jun 1999 09:14:03 +0930 (CST)" Message-ID: Lines: 21 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Newton writes: > Arun Sharma wrote: > > > While we're on the init topic, is there any strong feeling here about > > BSD /etc/rc* scripts Vs SysV ? The nice thing about SysV initscripts > > is the ability to start and stop any service that I like. > > That's fine -- there are lots of ways to start and stop any service you > like without involving SysV init. Like sending a signal to the process providing the service ? The problem with that approach is, the signal you send and the clean up you do is non-standard for each service and having a standard interface: /etc/rc.d/ stop|start|restart makes it standard. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 19:57:19 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 761FE15183 for ; Tue, 15 Jun 1999 19:57:15 -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 MAA10899; Wed, 16 Jun 1999 12:27:09 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199906160257.MAA10899@gizmo.internode.com.au> Subject: Re: [Call for review] init(8): new feature To: adsharma@home.com (Arun Sharma) Date: Wed, 16 Jun 1999 12:27:09 +0930 (CST) Cc: newton@internode.com.au, hackers@FreeBSD.ORG In-Reply-To: from "Arun Sharma" at Jun 15, 99 07:54:51 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 Arun Sharma wrote: > Mark Newton writes: > > Arun Sharma wrote: > > > > > While we're on the init topic, is there any strong feeling here about > > > BSD /etc/rc* scripts Vs SysV ? The nice thing about SysV initscripts > > > is the ability to start and stop any service that I like. > > That's fine -- there are lots of ways to start and stop any service you > > like without involving SysV init. > > Like sending a signal to the process providing the service ? The > problem with that approach is, the signal you send and the clean up > you do is non-standard for each service and having a standard > interface: There are lots of ways to start and stop any service you like without relying on sending a signal to a process and without involving SysV init. This topic has been canvassed so many times by so many people that I can only suggest that you run off to the archives and read about it there. - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 20: 4: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from www.crb-web.com (ns1.crb-web.com [209.70.120.131]) by hub.freebsd.org (Postfix) with SMTP id 082D115488 for ; Tue, 15 Jun 1999 20:03:58 -0700 (PDT) (envelope-from wayne@crb.crb-web.com) Received: (qmail 9485 invoked by uid 1001); 16 Jun 1999 03:05:43 -0000 Date: Tue, 15 Jun 1999 23:05:43 -0400 (EDT) From: Wayne Cuddy Reply-To: wayne@crb-web.com Cc: hackers@FreeBSD.ORG Subject: Re: [Call for review] init(8): new feature 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 They SysV way is more elegant and less error prone for bad typist. Graphical tools can be used to interface with these quite easily. It also also easy to automate installations via installation mechanisms. I don't think I agree that it is a bad idea because it is associated with SysV... On 15 Jun 1999, Arun Sharma wrote: > Date: 15 Jun 1999 19:54:51 -0700 > From: Arun Sharma > To: Mark Newton > Cc: hackers@FreeBSD.ORG > Subject: Re: [Call for review] init(8): new feature > > Mark Newton writes: > > > Arun Sharma wrote: > > > > > While we're on the init topic, is there any strong feeling here about > > > BSD /etc/rc* scripts Vs SysV ? The nice thing about SysV initscripts > > > is the ability to start and stop any service that I like. > > > > That's fine -- there are lots of ways to start and stop any service you > > like without involving SysV init. > > Like sending a signal to the process providing the service ? The > problem with that approach is, the signal you send and the clean up > you do is non-standard for each service and having a standard > interface: > > /etc/rc.d/ stop|start|restart > > makes it standard. > > -Arun > > > 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 Jun 15 20: 7: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from www.crb-web.com (ns1.crb-web.com [209.70.120.131]) by hub.freebsd.org (Postfix) with SMTP id 2513915104 for ; Tue, 15 Jun 1999 20:06:59 -0700 (PDT) (envelope-from wayne@crb.crb-web.com) Received: (qmail 9508 invoked by uid 1001); 16 Jun 1999 03:08:45 -0000 Date: Tue, 15 Jun 1999 23:08:45 -0400 (EDT) From: Wayne Cuddy Reply-To: wayne@crb-web.com To: FreeBSD Hackers List Subject: how do I install driver examples? 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 my 2.2.7 system I have this directory: /usr/share/examples/drivers This is not on my 3.2S system. I have the 3.1 4 cd set can anyone tell me what I need to install in order get the drivers extracted from my 3.1 cd? Thanks, Wayne To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 20:11:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub1.cuckoo.com (wrangler.cuckoo.com [206.109.5.194]) by hub.freebsd.org (Postfix) with SMTP id 8FF7D14CFF for ; Tue, 15 Jun 1999 20:11:35 -0700 (PDT) (envelope-from dbaker@cuckoo.com) Received: (qmail 33748 invoked by uid 200); 16 Jun 1999 03:11:34 -0000 Message-ID: <19990615221134.A33048@cuckoo.com> Date: Tue, 15 Jun 1999 22:11:34 -0500 From: Daniel Baker To: freebsd-hackers@freebsd.org Subject: Typo: sys/pci/pcisupport.c Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=x+6KMIRAuhnl3hBn X-Mailer: Mutt 0.93.2i X-PGP-Fingerprint: F3 41 B7 EE 96 92 F5 35 5E 3C 02 61 08 22 23 98 X-Operating-System: FreeBSD 3.1-STABLE i386 X-Distributed: Join the cows! http://www.distributed.net/ ]:8) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --x+6KMIRAuhnl3hBn Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable 4.0-CURRENT: sys/pci/pcisupport.c: 955: /* VIA Technologies -- vendor 0x1106 &/ 956: case 0x05861106: /* south bridge section */ 957: return ("VIA 82C586 PCI-ISA bridge"); This is cute. Moo. Daniel --=20 dbaker@cuckoo.com - Senior CuckooNet Consultant - http://www.cuckoo.com/dan= iel/ --x+6KMIRAuhnl3hBn Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: nN6eaNiNtqrdEtRP33LvP/ooQThovkte iQCVAwUBN2cH1jPZFXqiby35AQHa6AQA3FitjMK133YlbNHty4CNFQatP2MIwpnC APG4yP23x1GOoTTpccOeSWhW7aXpVulbm8w82hBLKNuWJ1X6C4VdJ6i6jAFXw235 CpSmx69Et9g3hvBiDXIE4i5N8Vm6tAxxtqcg27a+jm2cWaYNnpmPDOVM8aKfu5H4 aJGpeCZ/VKw= =SNC1 -----END PGP SIGNATURE----- --x+6KMIRAuhnl3hBn-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 20:18:38 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 9DFF814C04 for ; Tue, 15 Jun 1999 20:18:34 -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 MAA11012; Wed, 16 Jun 1999 12:48:19 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199906160318.MAA11012@gizmo.internode.com.au> Subject: Re: [Call for review] init(8): new feature To: wayne@crb-web.com Date: Wed, 16 Jun 1999 12:48:19 +0930 (CST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Wayne Cuddy" at Jun 15, 99 11:05:43 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 Wayne Cuddy wrote: > They SysV way is more elegant and less error prone for bad typist. ... and has absolutely no way of encoding interdependencies between services (or any concept of a "service" at all, other than as after-the-fact hacks). What happens to your NFS services when you do "/etc/init.d/inetsvc stop; /etc/init.d/inetsvc start" on a Sun? What *should* happen on a notebook computer when you start it without its pccard ethernet device plugged in? Should certain network services not be started at all, or should they be delayed until after PPP comes up? Isn't that a question that can only be answered by the individual service? (like, DHCP wouldn't need to start at all when PPP comes up, but your web server might need to be restarted to listen to a new IP address). > Graphical tools can be used to interface with these quite easily. ... also true for any other well-designed interface. > It also also easy to > automate installations via installation mechanisms. Also true for any other well-designed interface. SysV's mechanism is not a well-designed interface. Sure, it has its strengths, and it makes certain tasks easy, but it's not the only answer that has strengths and simplicity. > I don't think I agree > that it is a bad idea because it is associated with SysV... Neither do I; that issue hasn't been broached in this discussion to date. I think it's a bad idea because it's an intrinsically bad idea. It seems to me that every time this issue comes up people say, "We need something better than rc.local/rc.conf for boot-time configuration. SysV has certain attributes we don't have; so let's use SysV!" It's like the politician's mantra: "SOMETHING must be done! This random solution counts as `something', so let's implement this random solution." Let's not. Several people have given this matter serious thought and have come up with some excellent ideas, some of which have been implmenented as a test platform. Again I'd suggest that anyone interested in following this up consults the archives first, because the last thing we need is to have the mailing lists rehash the same ground *again* less than three months after the last time we rehashed it. [ a note to whoever it is that's replying to this message: you will no doubt delete this text in your reply, because it's stressing that you should CONSULT THE ARCHIVES. have you consulted them? if not, please, please, please exit your editor without saving your response, and consult them. thank you for your cooperation. normal service will resume shortly. ] - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 20:22:56 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 86DCB14CFF for ; Tue, 15 Jun 1999 20:22:54 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 54743 invoked from network); 16 Jun 1999 03:22:54 -0000 Received: from shell-2.enteract.com (dscheidt@207.229.143.41) by pop3-3.enteract.com with SMTP; 16 Jun 1999 03:22:54 -0000 Received: from localhost (dscheidt@localhost) by shell-2.enteract.com (8.9.3/8.9.2) with SMTP id WAA10899; Tue, 15 Jun 1999 22:22:53 -0500 (CDT) (envelope-from dscheidt@enteract.com) X-Authentication-Warning: shell-2.enteract.com: dscheidt owned process doing -bs Date: Tue, 15 Jun 1999 22:22:53 -0500 (CDT) From: David Scheidt To: Wayne Cuddy Cc: FreeBSD Hackers List Subject: Re: how do I install driver examples? 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, 15 Jun 1999, Wayne Cuddy wrote: > On my 2.2.7 system I have this directory: > /usr/share/examples/drivers > > This is not on my 3.2S system. I have the 3.1 4 cd set can anyone tell me > what I need to install in order get the drivers extracted from my 3.1 cd? They are on cdrom2. # cd /; (cd /cdrom; tar cvf - usr/share/examples/drivers ) | tar xvf - should work. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 21: 7:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (Postfix) with ESMTP id A66DA154B5 for ; Tue, 15 Jun 1999 21:07:20 -0700 (PDT) (envelope-from sanpei@sanpei.org) Received: from lavender.sanpei.org (u4161.seaple.icc.ne.jp [210.170.12.161]) by titanium.yy.ics.keio.ac.jp (8.8.8+3.0Wbeta13/3.7W) with ESMTP id NAA10403; Wed, 16 Jun 1999 13:07:07 +0900 (JST) Received: (from sanpei@localhost) by lavender.sanpei.org (8.9.3/3.7W) id NAA20129; Wed, 16 Jun 1999 13:07:07 +0900 (JST) Date: Wed, 16 Jun 1999 13:07:07 +0900 (JST) Message-Id: <199906160407.NAA20129@lavender.sanpei.org> To: adsharma@home.com Cc: newton@internode.com.au, hackers@FreeBSD.ORG, sanpei@sanpei.org Subject: Re: [Call for review] init(8): new feature In-Reply-To: Your message of "Wed, 16 Jun 1999 11:54:51 JST". From: sanpei@sanpei.org (MIHIRA Yoshiro) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG adsharma@home.com wrote: >> >> Like sending a signal to the process providing the service ? The >> problem with that approach is, the signal you send and the clean up >> you do is non-standard for each service and having a standard >> interface: >> >> /etc/rc.d/ stop|start|restart >> >> makes it standard. I think we need to use /usr/local/etc/rc.d/.sh stop|start|restart # Yes, We modify some ports to support start,stop..... MIHIRA Sanpei Yoshiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 21:10: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 21468154C7 for ; Tue, 15 Jun 1999 21:10:00 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id NAA07776; Wed, 16 Jun 1999 13:39:30 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Description: signed PGP message Content-Transfer-Encoding: 8bit Content-Type: application/pgp; format=text; x-action=sign MIME-Version: 1.0 In-Reply-To: <199906160407.NAA20129@lavender.sanpei.org> Date: Wed, 16 Jun 1999 13:39:29 +0930 (CST) From: "Daniel O'Connor" To: (MIHIRA Yoshiro) Subject: Re: [Call for review] init(8): new feature Cc: hackers@FreeBSD.ORG, newton@internode.com.au, adsharma@home.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- On 16-Jun-99 MIHIRA Yoshiro wrote: > >> /etc/rc.d/ stop|start|restart > >> makes it standard. > I think we need to use > /usr/local/etc/rc.d/.sh stop|start|restart > > # Yes, We modify some ports to support start,stop..... But there are services that come with FreeBSD (ie Bind, Sendmail, etc) that should (IMHO :) go in /etc/rc.d - --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv iQCVAwUBN2cjeVbYW/HEoF9pAQEloQP/VnHVOsUk7C1Sgkab5uuNkO81hKFUVhRz FO26/eqzDJHBI36G78Sn73YFos8+RGGlrTR3dpperfxS19DmVI/N1uyF9vNliA/q 4e4AGoxjDjJY2ekqy9g8z9J+fZ3x+wqZY7c6TYQFbV3t8kImwhy9xpJnr0+eLLAi U9cHTmkqIpY= =scez -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 15 23:49:59 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 DB5EC150DA for ; Tue, 15 Jun 1999 23:49:37 -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 AAA75076; Wed, 16 Jun 1999 00:09:27 +0100 (BST) (envelope-from nik) Date: Wed, 16 Jun 1999 00:09:27 +0100 From: Nik Clayton To: Arun Sharma Cc: hackers@FreeBSD.ORG Subject: Re: [Call for review] init(8): new feature Message-ID: <19990616000927.A74670@catkin.nothing-going-on.org> References: <19990615183926.A31280@relay.ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Arun Sharma on Tue, Jun 15, 1999 at 08:59:59AM -0700 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 15, 1999 at 08:59:59AM -0700, Arun Sharma wrote: > While we're on the init topic, is there any strong feeling here about > BSD /etc/rc* scripts Vs SysV ? Yes, lots. The last round of discussion was covered in the freebsd-arch mailing list, the archives should be enlightening. 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 Wed Jun 16 1:26: 9 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 3D66215332 for ; Wed, 16 Jun 1999 01:25:25 -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 KAA77982; Wed, 16 Jun 1999 10:25:02 +0200 (CEST) (envelope-from des) To: sanpei@sanpei.org (MIHIRA Yoshiro) Cc: adsharma@home.com, newton@internode.com.au, hackers@FreeBSD.ORG Subject: Re: [Call for review] init(8): new feature References: <199906160407.NAA20129@lavender.sanpei.org> From: Dag-Erling Smorgrav Date: 16 Jun 1999 10:25:00 +0200 In-Reply-To: sanpei@sanpei.org's message of "Wed, 16 Jun 1999 13:07:07 +0900 (JST)" Message-ID: Lines: 26 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sanpei@sanpei.org (MIHIRA Yoshiro) writes: > # Yes, We modify some ports to support start,stop..... And others to no longer support it. The Apache 1.2 port used to support it, the Apache 1.3 port doesn't. Here's a replacement: #!/bin/sh if [ ! -x /usr/local/sbin/apachectl ] ; then echo "apachectl not found" exit 1 fi case $1 in start|stop|restart) /usr/local/sbin/apachectl $1 ;; *) echo "Usage: $(basename $0) start|stop|restart" exit 1 ;; esac 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 Jun 16 1:30: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 077F314D4D for ; Wed, 16 Jun 1999 01:30: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 KAA78126; Wed, 16 Jun 1999 10:30:50 +0200 (CEST) (envelope-from des) To: David Scheidt Cc: Wayne Cuddy , FreeBSD Hackers List Subject: Re: how do I install driver examples? References: From: Dag-Erling Smorgrav Date: 16 Jun 1999 10:30:49 +0200 In-Reply-To: David Scheidt's message of "Tue, 15 Jun 1999 22:22:53 -0500 (CDT)" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Scheidt writes: > # cd /; (cd /cdrom; tar cvf - usr/share/examples/drivers ) | tar xvf - > should work. # cd /cdrom && tar cvf - usr/share/examples/drivers | tar xvf - -C / 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 Jun 16 2:38:13 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 5933215616 for ; Wed, 16 Jun 1999 02:38:10 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id LAA08753; Wed, 16 Jun 1999 11:37:56 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199906160937.LAA08753@freebsd.dk> Subject: Re: ZD labs test update In-Reply-To: <19990615112327.22753.rocketmail@web105.yahoomail.com> from Tommy Hallgren at "Jun 15, 1999 12:23:27 pm" To: thallgren@yahoo.com (Tommy Hallgren) Date: Wed, 16 Jun 1999 11:37:55 +0200 (CEST) Cc: mike@smith.net.au, 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 Tommy Hallgren wrote: > --- Mike Smith wrote: > > We'd previously encountered problems with the Infortrend controller not > > at all liking the other disks we'd tried to talk to; a collection of > > Cheetahs with IBM and Compaq firmware simply wouldn't work. This time > > we had better luck with real Seagate firmware, and the array > > performance wasn't too shabby, giving us ~8MB/sec write performance and > > ~16MB/sec read performance using the dd-stone benchmark. > > Isn't 16MB/s quite bad for this kind of system? It does compare badly to my little ATA system which does the dd-stone at ~13MB write / ~17Mb read, for a fraction of the cost :) -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 Jun 16 3:52:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id 4D64714CBB for ; Wed, 16 Jun 1999 03:52:15 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Wed, 16 Jun 1999 12:55:14 +0200 Message-ID: <55586E7391ACD211B9730000C1100276179678@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: 'Daniel Baker' , freebsd-hackers@freebsd.org Subject: RE: Typo: sys/pci/pcisupport.c Date: Wed, 16 Jun 1999 12:48:51 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Daniel Baker [SMTP:dbaker@cuckoo.com] > Sent: Wednesday, June 16, 1999 5:12 AM > To: freebsd-hackers@freebsd.org > Subject: Typo: sys/pci/pcisupport.c > > 4.0-CURRENT: sys/pci/pcisupport.c: > > 955: /* VIA Technologies -- vendor 0x1106 &/ > 956: case 0x05861106: /* south bridge section */ > 957: return ("VIA 82C586 PCI-ISA bridge"); > > This is cute. Moo. [ML] Yes. A comment-within-a-comment compiler warning would have been nice. AFAIK, gcc doesn't warn about that. /Marino > Daniel > > -- > dbaker@cuckoo.com - Senior CuckooNet Consultant - > http://www.cuckoo.com/daniel/ << File: ATT03690.ATT >> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 5:27: 8 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 41EA4156DD for ; Wed, 16 Jun 1999 05:27:04 -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 OAA11439; Wed, 16 Jun 1999 14:26:51 +0200 (MET DST) Date: Wed, 16 Jun 1999 14:26:51 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Ladavac Marino Cc: FreeBSD hackers mailing list Subject: RE: Typo: sys/pci/pcisupport.c In-Reply-To: <55586E7391ACD211B9730000C1100276179678@r-lmh-wi-100.corpnet.at> 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 > > 955: /* VIA Technologies -- vendor 0x1106 &/ > > 956: case 0x05861106: /* south bridge section */ > > 957: return ("VIA 82C586 PCI-ISA bridge"); > > > > This is cute. Moo. > [ML] Yes. A comment-within-a-comment compiler warning would > have been nice. AFAIK, gcc doesn't warn about that. It does, just no one checking. Someone needs to go and fix warnings again in CURRENT. root@elpc36:ELPC $make pcisupport.o perl5 ../../kern/makedevops.pl -h ../../kern/bus_if.m cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf ../../pci/pcisupport.c ../../pci/pcisupport.c:955: warning: `/*' within comment To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 5:29:28 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 ED3B815377 for ; Wed, 16 Jun 1999 05:29:25 -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 AA142770941; Wed, 16 Jun 1999 04:15:41 -0400 Date: Wed, 16 Jun 1999 04:15:41 -0400 (EDT) From: Bill Fumerola To: Daniel Baker Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Typo: sys/pci/pcisupport.c In-Reply-To: <19990615221134.A33048@cuckoo.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, 15 Jun 1999, Daniel Baker wrote: > 4.0-CURRENT: sys/pci/pcisupport.c: > > 955: /* VIA Technologies -- vendor 0x1106 &/ > 956: case 0x05861106: /* south bridge section */ > 957: return ("VIA 82C586 PCI-ISA bridge"); > > This is cute. Moo. Fixed. Thanks. - 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 Wed Jun 16 5:37:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id B27B1150B7 for ; Wed, 16 Jun 1999 05:37:19 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Wed, 16 Jun 1999 14:40:11 +0200 Message-ID: <55586E7391ACD211B9730000C110027617967A@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: 'Nick Hibma' , Ladavac Marino Cc: FreeBSD hackers mailing list Subject: compiler warnings (was: RE: Typo: sys/pci/pcisupport.c) Date: Wed, 16 Jun 1999 14:34:33 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Nick Hibma [SMTP:nick.hibma@jrc.it] > Sent: Wednesday, June 16, 1999 2:27 PM > To: Ladavac Marino > Cc: FreeBSD hackers mailing list > Subject: RE: Typo: sys/pci/pcisupport.c > It does, just no one checking. Someone needs to go and fix warnings > again in CURRENT. > [ML] my dearest warning is SNI CC "Computation serves no purpose". There is a story behind it: our product was shipping for hpux and was later ported to sinix. It had some instabilities during development (it was first developed for hpux, then the enhancements were ported to sinix, almost in parallel). A colleague wrote (paraphrased) pointer->pointer->object.method; where he wanted pointer->pointer->object.method(); hpux CC did not say a word. Naturally, the method had desired side effects :) /Marino > 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 Jun 16 5:43: 3 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 9350B15269 for ; Wed, 16 Jun 1999 05:42:57 -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 OAA12258; Wed, 16 Jun 1999 14:42:47 +0200 (MET DST) Date: Wed, 16 Jun 1999 14:42:47 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Ladavac Marino Cc: FreeBSD hackers mailing list Subject: Re: compiler warnings (was: RE: Typo: sys/pci/pcisupport.c) In-Reply-To: <55586E7391ACD211B9730000C110027617967A@r-lmh-wi-100.corpnet.at> 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 > pointer->pointer->object.method; > > where he wanted > > pointer->pointer->object.method(); > > hpux CC did not say a word. Naturally, the method had desired > side effects :) Port your application to see more compiler warnings. It sounds like perl -e 'use strict; ...' :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 5:51:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id BA122150B7 for ; Wed, 16 Jun 1999 05:51:30 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id IAA02867; Wed, 16 Jun 1999 08:51:57 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id IAA02094; Wed, 16 Jun 1999 08:51:25 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id IAA04314; Wed, 16 Jun 1999 08:51:25 -0400 (EDT) Date: Wed, 16 Jun 1999 08:51:25 -0400 (EDT) From: Thomas David Rivers Message-Id: <199906161251.IAA04314@lakes.dignus.com> To: mladavac@metropolitan.at, nick.hibma@jrc.it Subject: Re: compiler warnings (was: RE: Typo: sys/pci/pcisupport.c) Cc: hackers@FreeBSD.ORG In-Reply-To: <55586E7391ACD211B9730000C110027617967A@r-lmh-wi-100.corpnet.at> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > There is a story behind it: our product was shipping for hpux > and was later ported to sinix. It had some instabilities during > development (it was first developed for hpux, then the enhancements were > ported to sinix, almost in parallel). > > A colleague wrote (paraphrased) > > pointer->pointer->object.method; Some compilers will emit something like: Warning: Statement has no side effect for expressions like this (at least, the Systems/C compiler does.) > > where he wanted > > pointer->pointer->object.method(); > > hpux CC did not say a word. Naturally, the method had desired > side effects :) > > /Marino > -- rivers@dignus.com Work: (919) 676-0847 Get your mainframe (370) `C' compiler at http://www.dignus.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 9:10:10 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 57F68155B9 for ; Wed, 16 Jun 1999 09:10:07 -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 JAA22774; Wed, 16 Jun 1999 09:09:22 -0700 Date: Wed, 16 Jun 1999 09:09:04 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Soren Schmidt Cc: Tommy Hallgren , mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: ZD labs test update In-Reply-To: <199906160937.LAA08753@freebsd.dk> 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 > > > We'd previously encountered problems with the Infortrend controller not > > > at all liking the other disks we'd tried to talk to; a collection of > > > Cheetahs with IBM and Compaq firmware simply wouldn't work. This time > > > we had better luck with real Seagate firmware, and the array > > > performance wasn't too shabby, giving us ~8MB/sec write performance and > > > ~16MB/sec read performance using the dd-stone benchmark. > > > > Isn't 16MB/s quite bad for this kind of system? > > It does compare badly to my little ATA system which does the dd-stone > at ~13MB write / ~17Mb read, for a fraction of the cost :) Until there's a media defect and no AWRE (automatic write reallocate).... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 10: 3:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from osmail.onesoft.com (unknown [209.207.229.30]) by hub.freebsd.org (Postfix) with ESMTP id 6ED4714CEA for ; Wed, 16 Jun 1999 10:02:45 -0700 (PDT) (envelope-from morpheus_420@depechemode.com) X-Internal-ID: 3761293000010254 Received: from local.com (209.207.229.31) by osmail.onesoft.com (NPlex 2.0.108) for freebsd-hackers@freebsd.org; 16 Jun 1999 13:06:29 -0400 Message-ID: <3761293000010254@osmail.onesoft.com> (added by osmail.onesoft.com) From: morpheus_420@depechemode.com To: freebsd-hackers@freebsd.org Subject: help with CD-Rom Date: Wed, 16 Jun 1999 13:01:39 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yesterday I was able to mount my CD-ROM just fine. Today after a lot of kernel hacking I am not. I am fairly new at this so this may be a really easy answer. I have an entry in the "fstab" file that references my cdrom /dev/wcd0c /cdrom ro, noauto 0 0 but when I goto "mount /cdrom" I get an error that says "/dev/wcd0c: Device not configured" Any ideas as to what I am doing or have done wrong here thanks in advance -Jay ------------------------------- To get your free email account, go to: http://www.depechemodemail.com Exclusive Depeche Mode Merchandise Now Avalailable Online at http://www.depechemode.com Depeche Mode Mail is a service of Electric Artists and OneSoft. ------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 10: 4:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from osmail.onesoft.com (unknown [209.207.229.30]) by hub.freebsd.org (Postfix) with ESMTP id CAF2114CEA for ; Wed, 16 Jun 1999 10:02:53 -0700 (PDT) (envelope-from morpheus_420@depechemode.com) X-Internal-ID: 3761293000010258 Received: from local.com (209.207.229.31) by osmail.onesoft.com (NPlex 2.0.108) for freebsd-hackers@freebsd.org; 16 Jun 1999 13:06:38 -0400 Message-ID: <3761293000010258@osmail.onesoft.com> (added by osmail.onesoft.com) From: morpheus_420@depechemode.com To: freebsd-hackers@freebsd.org Subject: help with CD-Rom Date: Wed, 16 Jun 1999 13:01:47 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yesterday I was able to mount my CD-ROM just fine. Today after a lot of kernel hacking I am not. I am fairly new at this so this may be a really easy answer. I have an entry in the "fstab" file that references my cdrom /dev/wcd0c /cdrom ro, noauto 0 0 but when I goto "mount /cdrom" I get an error that says "/dev/wcd0c: Device not configured" Any ideas as to what I am doing or have done wrong here thanks in advance -Jay ------------------------------- To get your free email account, go to: http://www.depechemodemail.com Exclusive Depeche Mode Merchandise Now Avalailable Online at http://www.depechemode.com Depeche Mode Mail is a service of Electric Artists and OneSoft. ------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 11:33: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bantu.cl.msu.edu (bantu.cl.msu.edu [35.8.3.18]) by hub.freebsd.org (Postfix) with ESMTP id 80D19152B0 for ; Wed, 16 Jun 1999 11:33:03 -0700 (PDT) (envelope-from dervish@bantu.cl.msu.edu) Received: (from dervish@localhost) by bantu.cl.msu.edu (8.9.3/8.9.3) id OAA90893; Wed, 16 Jun 1999 14:29:47 -0400 (EDT) (envelope-from dervish) Date: Wed, 16 Jun 1999 14:29:47 -0400 From: bush doctor To: morpheus_420@depechemode.com Cc: freebsd-hackers@freebsd.org Subject: Re: help with CD-Rom Message-ID: <19990616142947.C90275@bantu.cl.msu.edu> References: <3761293000010258@osmail.onesoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <3761293000010258@osmail.onesoft.com>; from morpheus_420@depechemode.com on Wed, Jun 16, 1999 at 01:01:47PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT i386 X-PGP-Fingerprint: 35 95 F8 63 DA 5B 32 51 8F A9 AC 3C B4 74 F3 BA WWW-Home-Page: http://www.msu.edu/~ikhala Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Once morpheus_420@depechemode.com aka (morpheus_420@depechemode.com) said: > Yesterday I was able to mount my CD-ROM just fine. Today after > a lot of kernel hacking I am not. I am fairly new at this so > this may be a really easy answer. > I have an entry in the "fstab" file that references my cdrom > /dev/wcd0c /cdrom ro, noauto 0 0 > but when I goto "mount /cdrom" I get an error that says > "/dev/wcd0c: Device not configured" > > > Any ideas as to what I am doing or have done wrong here No ideas as to what you're doing :-) However, Check your kernel config file and make sure you have the following device wcd0 #IDE CD-ROM grep the output of dmesg and see if you had any errors referring to wcd0 Can't be any more helpful without just a wee bit more information about your system, at least the version you're running. dmesg output would've been useful here. Also this question probably should have went to -questions > > thanks in advance No problems. Also once i have an ides as to what you're doing, you'll be the first to know ... #;^) > > -Jay > > ------------------------------- > To get your free email account, go to: > http://www.depechemodemail.com > Exclusive Depeche Mode Merchandise Now Avalailable Online at > http://www.depechemode.com > Depeche Mode Mail is a service of Electric Artists and > OneSoft. > ------------------------------- > > #;^) -- So ya want ta here da roots? Dem that feels it knows it ... bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 12:13:32 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 93922152B5 for ; Wed, 16 Jun 1999 12:13:28 -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 PAA14256 for ; Wed, 16 Jun 1999 15:13:59 -0400 (EDT) Message-Id: <199906161913.PAA14256@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 16 Jun 1999 14:05:42 -0400 To: hackers@freebsd.org From: Dennis Subject: DLINK quad ethernet board Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is this board supported? Anyone using them? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 12:17:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from surf.iae.nl (surf.IAE.nl [194.151.66.2]) by hub.freebsd.org (Postfix) with ESMTP id 0301914C59 for ; Wed, 16 Jun 1999 12:17:50 -0700 (PDT) (envelope-from wjw@iae.nl) Received: by surf.iae.nl (Postfix, from userid 74) id 922609937; Wed, 16 Jun 1999 21:17:49 +0200 (MET DST) To: jkh@zippy.cdrom.com Subject: Re: Variant symlinks [was Re: symlink question] X-Newsgroups: list.freebsd.hackers In-Reply-To: <53425.929320320@zippy.cdrom.com> References: <53369.929320127@zippy.cdrom.com> Organization: Internet Access Eindhoven Cc: hackers@freebsd.org Message-Id: <19990616191749.922609937@surf.iae.nl> Date: Wed, 16 Jun 1999 21:17:49 +0200 (MET DST) From: wjw@iae.nl (Willem Jan Withagen) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <53425.929320320@zippy.cdrom.com> you write: >> And have /usr/bin point to /binaries/i386/bin or /binaries/mips/bin > >And before people jump on me, let me just clarify in advance that I >was not meaning to imply that Apollo ever used the x86 architecture. >They didn't. It was just an example. :) Well sort of. :-) It could do windoze emulation on their poor 68K boxes. But you'd have to be a very patient (or desperate) person to use that. --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 9.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 12:36:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id AFE1314EEE for ; Wed, 16 Jun 1999 12:36:26 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id PAA20151 for ; Wed, 16 Jun 1999 15:37:04 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id PAA02700 for ; Wed, 16 Jun 1999 15:36:23 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id PAA06539 for freebsd-hackers@freebsd.org; Wed, 16 Jun 1999 15:36:23 -0400 (EDT) Date: Wed, 16 Jun 1999 15:36:23 -0400 (EDT) From: Thomas David Rivers Message-Id: <199906161936.PAA06539@lakes.dignus.com> To: freebsd-hackers@freebsd.org Subject: 3.2 SL/IP Install - can't get ifconfig to work... Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't seem to be able to get 3.2 to do a SL/IP install (this is for a laptop which seems to be having PAO problems...) Turning on DEBUG in the install options, I can watch it nicely execute: ifconfig sl0 inet 10.0.0.98 10.0.0.99 netmask 255.255.255.0 but - not matter what - that always seems to fail with: ifconfig: ioctl(SIOCAIFADDR): File exists does anyone have a clue why the ioctl for the sl0 ifconfig would fail? (Perhaps the sl psuedo-device is missing from the kernel?) [I'm guessin the 'File exists' is left-over stuff in errno, as the ioctl(SIOCAIFADDR) message seems to be the result of perror().] - Thanks - - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 12:40:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 6C96914EEE; Wed, 16 Jun 1999 12:40:18 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id MAA23994; Wed, 16 Jun 1999 12:39:48 -0700 (PDT) (envelope-from Studded@gorean.org) Date: Wed, 16 Jun 1999 12:39:48 -0700 (PDT) From: Studded X-Sender: doug@dt054n86.san.rr.com To: The Tech-Admin Dude Cc: Luigi Rizzo , Dan Nelson , arikkert@surf.IAE.nl, freebsd-bugs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: timeconsuming processes on FreeBSD 3.1 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, 20 May 1999, The Tech-Admin Dude wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I could add another one, top(1) frequently does that on this machine.. > so whatever answers you get, be sure to forward them to me :). Blast from the past, but since no one gave you an answer, here is one suggestion. I used to have this problem all the time until I discovered that top obeys environment variables. So, you could put the following in /etc/login.conf (make sure to rebuild the db after editing): :setenv=TOP='-I -d5' The -I just means "don't display idle processes," the -d5 means "do 5 cycles then exit." Both are overridable from the command line. You might want to set the -d value higher so that it's more transparent to the user, but after setting this up I've never had another runaway top process. HTH, Doug -- *** Chief Operations Officer, DALnet IRC network *** 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 Wed Jun 16 12:54:25 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 43B4D150DE for ; Wed, 16 Jun 1999 12:54:18 -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 VAA05630; Wed, 16 Jun 1999 21:52:56 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199906161952.VAA05630@gratis.grondar.za> To: hosokawa@itc.keio.ac.jp (HOSOKAWA Tatsumi) Cc: jkh@zippy.cdrom.com, hackers@FreeBSD.ORG Subject: Re: PCCARD boot.flp for -current (reviewer wanted) Date: Wed, 16 Jun 1999 21:52:55 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've ported PC-card boot.flp to -current. > > Source patch can be found at > > http://wing-yee.ntc.keio.ac.jp/hosokawa/pccard-flp/current-diff-19990616.tar. gz I was offline for a while - apologies for not getting back to you. I have the new ones, and my box is busy building world with them right now. I'll commit if nobody else can/wants to... 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 Wed Jun 16 13: 5:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 50BEA14CEE for ; Wed, 16 Jun 1999 13:05:50 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id QAA23548 for ; Wed, 16 Jun 1999 16:06:24 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id QAA02747; Wed, 16 Jun 1999 16:05:42 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id QAA06745; Wed, 16 Jun 1999 16:05:41 -0400 (EDT) Date: Wed, 16 Jun 1999 16:05:41 -0400 (EDT) From: Thomas David Rivers Message-Id: <199906162005.QAA06745@lakes.dignus.com> To: freebsd-hackers@FreeBSD.ORG, rivers@dignus.com Subject: Re: 3.2 SL/IP Install - can't get ifconfig to work... In-Reply-To: <199906161936.PAA06539@lakes.dignus.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I don't seem to be able to get 3.2 to do a SL/IP > install (this is for a laptop which seems to be > having PAO problems...) > > Turning on DEBUG in the install options, I can watch > it nicely execute: > > ifconfig sl0 inet 10.0.0.98 10.0.0.99 netmask 255.255.255.0 > > but - not matter what - that always seems to fail with: > > ifconfig: ioctl(SIOCAIFADDR): File exists > > does anyone have a clue why the ioctl for the sl0 > ifconfig would fail? (Perhaps the sl psuedo-device > is missing from the kernel?) [I'm guessin the > 'File exists' is left-over stuff in errno, as the > ioctl(SIOCAIFADDR) message seems to be the result > of perror().] > > - Thanks - > - Dave Rivers - > > Just to add to my own mail... After the ifconfig "fails" (and the slattach succeeds) - it seems that SL/IP is actually working. From the server box (this is a straight-through null-modem connection) - I can ping the box I'm trying to install. Also - under the shell on VTY4 - I can mount_nfs the server's CDROM drive... so - the network is actually working... Although ifconfig has a non-zero return code. I tried doing an "ifconfig sl0 down" under the emergency shell on VTY4 - but that didn't seem to change anything; every ifconfig sl0 comes back with "ioctl(SIOCAIFADDR): File exists". I think I can hack-around in sysinstall to get past this; but, something should be done before 3.3. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 13:50:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from puma.wmin.ac.uk (puma.wmin.ac.uk [161.74.92.94]) by hub.freebsd.org (Postfix) with SMTP id 9338B14CB0 for ; Wed, 16 Jun 1999 13:50:33 -0700 (PDT) (envelope-from smaraux@seth.cpc.wmin.ac.uk) Received: from seth.cpc.wmin.ac.uk by puma.wmin.ac.uk with INTERNAL-SMTP (MMTA) with ESMTP; Wed, 16 Jun 1999 21:47:29 +0100 Received: from localhost (smaraux@localhost) by seth.cpc.wmin.ac.uk (8.9.3/8.9.3) with ESMTP id VAA70603 for ; Wed, 16 Jun 1999 21:49:57 +0100 (BST) (envelope-from smaraux@seth.cpc.wmin.ac.uk) Date: Wed, 16 Jun 1999 21:49:57 +0100 (BST) From: Sebastien Maraux To: hackers@FreeBSD.org Subject: option BOOTP_NFSROOT 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 Does anybody ever used this option? options BOOTP_NFSROOT I'd like to use it, to boot a computer from a boot disk, and start a diskless station by mounting via NFS all the file system. The problem is that I don't know how to use it. and I don't know how to make the disk boot without using MFS_ROOT? Does anyone have an idea? Can I use MFS_ROOT (for boot0 and boot1) anyway and mount everything from the network via NFS? Thanks to those who will answer. Bye Sebastien MARAUX. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 14: 0:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from medulla.hippocampus.net (medulla.hippocampus.net [204.138.241.6]) by hub.freebsd.org (Postfix) with ESMTP id D3D9D14F12 for ; Wed, 16 Jun 1999 14:00:05 -0700 (PDT) (envelope-from marc@netstor.com) Received: from localhost (marc@localhost) by medulla.hippocampus.net (8.9.2/8.9.2) with ESMTP id RAA00993; Wed, 16 Jun 1999 17:06:30 -0400 (EDT) Date: Wed, 16 Jun 1999 17:06:30 -0400 (EDT) From: Marc Nicholas X-Sender: marc@medulla.hippocampus.net To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: DLINK quad ethernet board In-Reply-To: <199906161913.PAA14256@etinc.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 At a chipset level (DEC 21143) yes...in the same way a Znyx card would work. It looks like the card also uses a DEC bridge chip too (not unussual on multi-port Ethernet cards) and FreeBSD will also cope fine with that too. HOWEVER...be aware that some BIOSes mess up the initialization of such beasties (PCI bridging and all). So, in short, it should work...but I've never tried it :-) Out of interest, how much do DLink knock these puppies out of? -marc ---------------------------------------------------------------- Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com "Fast, Expandable and Affordable Internet Caching Products" 1.877.464.4776 416.979.9000 fax: 416.979.8223 cell: 416.346.9255 On Wed, 16 Jun 1999, Dennis wrote: > > Is this board supported? Anyone using them? > > 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 Wed Jun 16 14: 6:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 1DA0214ED7 for ; Wed, 16 Jun 1999 14:06:20 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id RAA01040 for ; Wed, 16 Jun 1999 17:06:58 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id RAA02841; Wed, 16 Jun 1999 17:06:16 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id RAA07359; Wed, 16 Jun 1999 17:06:16 -0400 (EDT) Date: Wed, 16 Jun 1999 17:06:16 -0400 (EDT) From: Thomas David Rivers Message-Id: <199906162106.RAA07359@lakes.dignus.com> To: freebsd-hackers@FreeBSD.ORG, rivers@dignus.com Subject: Re: 3.2 SL/IP Install - can't get ifconfig to work... In-Reply-To: <199906162005.QAA06745@lakes.dignus.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To add more to this - tracing through in.c in the kernel, I see that when you configure an interface it eventually works its way down to rtrequest - to add a route for the new interface. I believe rtrequest() is the one returning EEXIST which is what causes ifconfig on sl0 to always complain "File exists". Now - why would rtrequest() believe there's a route already there? I made sure there was nothing in the GATEWAY and NAMESERVER field, just in case sysinstall was issuing the route somehow. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 15:41: 9 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 0402A14D7C for ; Wed, 16 Jun 1999 15:41:05 -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 XAA10797; Wed, 16 Jun 1999 23:56:04 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA04355; Wed, 16 Jun 1999 23:03:31 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199906162103.XAA04355@yedi.iaf.nl> Subject: Re: Variant symlinks [was Re: symlink question] In-Reply-To: <19990616191749.922609937@surf.iae.nl> from Willem Jan Withagen at "Jun 16, 1999 9:17:49 pm" To: wjw@iae.nl (Willem Jan Withagen) Date: Wed, 16 Jun 1999 23:03:31 +0200 (CEST) Cc: jkh@zippy.cdrom.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 Willem Jan Withagen wrote ... > In article <53425.929320320@zippy.cdrom.com> you write: > >> And have /usr/bin point to /binaries/i386/bin or /binaries/mips/bin > > > >And before people jump on me, let me just clarify in advance that I > >was not meaning to imply that Apollo ever used the x86 architecture. > >They didn't. It was just an example. :) > > Well sort of. :-) > It could do windoze emulation on their poor 68K boxes. But you'd have to be > a very patient (or desperate) person to use that. Patient... yeah. I used to run hardware simulations on a DN3000 (68020/12), with a network connected hardware modeller. Cute, at that time.. -- | / 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 Jun 16 16: 3:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.erols.com (smtp1.erols.com [207.172.3.234]) by hub.freebsd.org (Postfix) with ESMTP id 7B16714EDF for ; Wed, 16 Jun 1999 16:03:49 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (207-172-143-173.s46.as2.hgt.md.dialup.rcn.com [207.172.143.173]) by smtp1.erols.com (8.8.8/8.8.5) with ESMTP id TAA17280; Wed, 16 Jun 1999 19:03:37 -0400 (EDT) Message-Id: <199906162303.TAA17280@smtp1.erols.com> X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 16 Jun 1999 19:03:41 -0400 (EDT) From: John Baldwin To: "Daniel O'Connor" Subject: RE: DHCP, arp and de0 Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16-Jun-99 Daniel O'Connor wrote: > > On 16-Jun-99 John Baldwin wrote: >> Whoops.. just ifconfig de0. Have you tried using the interface? We use >> for a lab I help run, and 'arp -a' on the clients does not show an entry >> for >> the local de0 card they have installed, but they work fine regardless. Do >> have a route for 127.0.0.1 in your route table (netstat -rn), there should >> one that just points to itself so, AFAIK, it shouldn't be arp'ing for that >> address. > > Well I have a netstat -nr from when it was using DHCP and when it wasn't and > the only difference is the 'Refs' for 127.0.0.1 was 3 for DHCP and 2 for > static. Hmm. Here's what I have on one of our clients: # netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default xxx.xx.184.1 UGSc 2 2 de0 127.0.0.1 127.0.0.1 UH 2 10 lo0 xxx.xx.184 link#1 UC 0 0 de0 xxx.xx.184.66 127.0.0.1 UGHS 0 0 lo0 xxx.xx.184.255 ff:ff:ff:ff:ff:ff UHLWb 1 896 de0 As you can see, only 2 refs for 127.0.0.1. Note that there is a route for de0's IP: xxx.xx.184.66 to 127.0.0.1. Do you have lo0 configured properly (is lo0 in network_interfaces in /etc/rc.conf and ifconfig_lo0 in either /etc/rc.conf or /etc/defaults/rc.conf)? > The interface works OK for somethings, but for example I can't run 'esd', and > whenever I try and ping the address assigned to the ethernet card I get > Jun 13 17:35:21 guppy /kernel: arplookup 127.0.0.1 failed: could not allocate > llinfo > Jun 13 17:35:21 guppy /kernel: arpresolve: can't allocate llinfo for > 127.0.0.1rt > > every ping packet sent. Don't have esd to test with, but I can ping it's own IP fine. I'd be willing to bet, though, that esd not working is a symptom of the same problem since a client talking to a server on the same host usually uses the lo0 interface. It really sounds like your lo0 isn't configured. What version of FreeBSD are you running? --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 16: 9:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from spooky.rwwa.com (rwwa.com [198.115.177.3]) by hub.freebsd.org (Postfix) with ESMTP id 4EFE714F3D for ; Wed, 16 Jun 1999 16:09:24 -0700 (PDT) (envelope-from witr@rwwa.com) Received: from spooky.rwwa.com (localhost.rwwa.com [127.0.0.1]) by spooky.rwwa.com (8.8.7/8.8.7) with ESMTP id TAA12409; Wed, 16 Jun 1999 19:10:05 -0400 (EDT) (envelope-from witr@rwwa.com) Message-Id: <199906162310.TAA12409@spooky.rwwa.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Garance A Drosihn Cc: "Jordan K. Hubbard" , Matthew Dillon , freebsd-hackers@freebsd.org Subject: Re: Matt's Commit status (was Re: 3.2-stable, panic #12) In-reply-to: Your message of "Thu, 03 Jun 1999 18:21:11 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Jun 1999 19:10:05 -0400 From: Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG drosih@rpi.edu said: :- While others seemed too busy with "new" technology to bother with :- ugly-old-NFS problems, Matt dived in and pursued them with enough :- enthusiasm to make a real difference. In particular, lots of NFS bugs that had been there, and reported, since early 2.2 days. Bugs that made it impossible for me to agitate for FreeBSD boxes to replace the hundreds of Sun workstations at my site, cuz NFS would just fall over dead. I don't care even if Matt smells like a pig. He's a-fixin bugs, don't ye know? --------------------------------------------------------------------- Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 17: 8:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id E457F14A2F for ; Wed, 16 Jun 1999 17:08:57 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id UAA19016 for ; Wed, 16 Jun 1999 20:09:35 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id UAA03049 for ; Wed, 16 Jun 1999 20:08:54 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id UAA07982 for freebsd-hackers@freebsd.org; Wed, 16 Jun 1999 20:08:54 -0400 (EDT) Date: Wed, 16 Jun 1999 20:08:54 -0400 (EDT) From: Thomas David Rivers Message-Id: <199906170008.UAA07982@lakes.dignus.com> To: freebsd-hackers@freebsd.org Subject: More on ifconfig sl0 issue... Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well - I've added some printf()s to determine that what I suspected was correct. The route is being entered into the table twice. If looks like in_ifinit() is calling the sioctl() routine, which calls if_up(), which then adds the route. Then, in_ifinit() goes on to add another route and *poof* - the route's already there - you get EEXISTS. What's interesting about this is it only happens on my small laptop. On an older 486 I have - if_up() doesn't seem to get invokved (I'm working on finding out why.) For those interested - see /sys/netinet/in.c and /sys/net/if.c and /sys/net/if_sl.c. This is all with a 3.2-RELEASE source base. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 17:47:33 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 872F414D10 for ; Wed, 16 Jun 1999 17:47:19 -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 UAA15480; Wed, 16 Jun 1999 20:47:50 -0400 (EDT) Message-Id: <199906170047.UAA15480@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 16 Jun 1999 19:39:29 -0400 To: Marc Nicholas From: Dennis Subject: Re: DLINK quad ethernet board Cc: hackers@freebsd.org In-Reply-To: References: <199906161913.PAA14256@etinc.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 05:06 PM 6/16/99 -0400, you wrote: >At a chipset level (DEC 21143) yes...in the same way a Znyx card would >work. > >It looks like the card also uses a DEC bridge chip too (not unussual on >multi-port Ethernet cards) and FreeBSD will also cope fine with that too. > >HOWEVER...be aware that some BIOSes mess up the initialization of such >beasties (PCI bridging and all). I also notice that DLINK markets this as a "load balancing board" which "appears as a single nic to the system". I assume that their windows driver makes it look like that, but it may have a strange interface. They are apparently a lot cheaper than Zynx boards (with the same technology)....Although I havent really found any of the DLINK dealers that sell them. Dennis > >So, in short, it should work...but I've never tried it :-) > >Out of interest, how much do DLink knock these puppies out of? > > >-marc > >---------------------------------------------------------------- >Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com >"Fast, Expandable and Affordable Internet Caching Products" >1.877.464.4776 416.979.9000 fax: 416.979.8223 cell: 416.346.9255 > >On Wed, 16 Jun 1999, Dennis wrote: > >> >> Is this board supported? Anyone using them? >> >> 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 Wed Jun 16 17:57:39 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 6634115031 for ; Wed, 16 Jun 1999 17:57:26 -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 JAA17143; Thu, 17 Jun 1999 09:57:11 +0900 (JST) Date: Thu, 17 Jun 1999 09:57:11 +0900 (JST) Message-Id: <199906170057.JAA17143@afs.ntc.mita.keio.ac.jp> To: mark@grondar.za Cc: jkh@zippy.cdrom.com, hackers@FreeBSD.ORG, hosokawa@itc.keio.ac.jp Subject: Re: PCCARD boot.flp for -current (reviewer wanted) In-Reply-To: Your message of "Thu, 17 Jun 1999 04:52:55 JST". <199906161952.VAA05630@gratis.grondar.za> 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 <199906161952.VAA05630@gratis.grondar.za> mark@grondar.za writes: >> I was offline for a while - apologies for not getting back to you. >> >> I have the new ones, and my box is busy building world with them right >> now. >> >> I'll commit if nobody else can/wants to... Please note that this patch replaces all explicit irq parameter in "config" line of pccard.conf.sample with "?". I think that, in fact, most of them are not necessary if "irq" definition of pccard.conf or "-i" option of pccardd (with this patch) are set correctly. If there are cards that *really* needs irq parameter in "config" line, please let me know about them. I think "-i" option can be configured semiautomatically by using "dirty" parameters of PC-card sysinstall and /etc/rc.pccard. I'll work on this after the patch is committed. -- 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 Wed Jun 16 18:11: 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 4A8D31505E for ; Wed, 16 Jun 1999 18:10:46 -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 SAA16371; Wed, 16 Jun 1999 18:10:43 -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 SAA66976; Wed, 16 Jun 1999 18:10:42 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 16 Jun 1999 18:10:42 -0700 (PDT) Message-Id: <199906170110.SAA66976@vashon.polstra.com> To: ust@cert.siemens.de Subject: Re: m3socks and cvsup In-Reply-To: <19990608084217.A5098@alaska.cert.siemens.de> References: <19990601190941.46F9F2921C@localhost.localdomain> <199906080624.AAA03373@harmony.village.org> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990608084217.A5098@alaska.cert.siemens.de>, Udo Schweigert wrote: > I'm using it (runsocks cvsup -P m) for a year now and it works > without any problems. (Since cvsup 16 the "-P m" is not needed, so > "runsocks cvsup" should so it). Just to make sure I understand: You're using standard socks rather than m3socks, right? I believe that standard socks should work with cvsup's multiplexed mode, but I've never tried it. It would probably be necessary to add "@M3novm" to the command line, though. If standard socks works, then I want to eliminate m3socks. There are some problems with m3socks that I just found out about recently. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 18:15:46 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 4F5B415055 for ; Wed, 16 Jun 1999 18:15:35 -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 SAA02790; Wed, 16 Jun 1999 18:14:56 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id SAA14962; Wed, 16 Jun 1999 18:14:57 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA17765; Wed, 16 Jun 99 18:14:54 PDT Message-Id: <37684C0E.330B7FA0@softweyr.com> Date: Wed, 16 Jun 1999 19:14:54 -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: Thomas David Rivers Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 3.2 SL/IP Install - can't get ifconfig to work... References: <199906162106.RAA07359@lakes.dignus.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas David Rivers wrote: > > To add more to this - tracing through in.c in the kernel, > I see that when you configure an interface it eventually > works its way down to rtrequest - to add a route for > the new interface. > > I believe rtrequest() is the one returning EEXIST which is > what causes ifconfig on sl0 to always complain "File exists". > > Now - why would rtrequest() believe there's a route already > there? Probably because there is one. ;^) netstat -rn before and after the ifconfig should allow you to see what has changed. I suspect it might be your default route, but you'd have to look to be sure. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr 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 Jun 16 18:18:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 3648615055 for ; Wed, 16 Jun 1999 18:18:13 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id VAA25383; Wed, 16 Jun 1999 21:18:49 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id VAA03157; Wed, 16 Jun 1999 21:18:08 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id VAA08418; Wed, 16 Jun 1999 21:18:07 -0400 (EDT) Date: Wed, 16 Jun 1999 21:18:07 -0400 (EDT) From: Thomas David Rivers Message-Id: <199906170118.VAA08418@lakes.dignus.com> To: rivers@dignus.com, wes@softweyr.com Subject: Re: 3.2 SL/IP Install - can't get ifconfig to work... Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <37684C0E.330B7FA0@softweyr.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Thomas David Rivers wrote: > > > > To add more to this - tracing through in.c in the kernel, > > I see that when you configure an interface it eventually > > works its way down to rtrequest - to add a route for > > the new interface. > > > > I believe rtrequest() is the one returning EEXIST which is > > what causes ifconfig on sl0 to always complain "File exists". > > > > Now - why would rtrequest() believe there's a route already > > there? > > Probably because there is one. ;^) > > netstat -rn before and after the ifconfig should allow you to see > what has changed. I suspect it might be your default route, but > you'd have to look to be sure. > netstat isn't on the install mfsroot (which is was) - but I tracked this down to a kernel bug. See PR#12251. Basically, if you do the slattach _before_ the ifconfig, the ifconfig will fail because the kernel tries to add the route twice. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 18:37:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 19433152A9 for ; Wed, 16 Jun 1999 18:37:38 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id VAA46957; Wed, 16 Jun 1999 21:35:38 -0400 (EDT) Date: Wed, 16 Jun 1999 21:35:38 -0400 (EDT) From: Chuck Robey To: Robert Withrow Cc: Garance A Drosihn , "Jordan K. Hubbard" , Matthew Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: Matt's Commit status (was Re: 3.2-stable, panic #12) In-Reply-To: <199906162310.TAA12409@spooky.rwwa.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, 16 Jun 1999, Robert Withrow wrote: > > drosih@rpi.edu said: > :- While others seemed too busy with "new" technology to bother with > :- ugly-old-NFS problems, Matt dived in and pursued them with enough > :- enthusiasm to make a real difference. > > In particular, lots of NFS bugs that had been there, and reported, > since early 2.2 days. Bugs that made it impossible for me to agitate for > FreeBSD boxes to replace the hundreds of Sun workstations at my site, > cuz NFS would just fall over dead. > > I don't care even if Matt smells like a pig. He's a-fixin bugs, don't > ye know? I really can't get too excited over a bunch of folks who continually open threads that are painful, that have been explained in horrible detail, as if they have some new viewpoint. It was done for very good reasons, although we didn't ask your permissions, and it wasn't kept a secret (except maybe that no one wanted to embarrass Matt). Either go back to the mail archives and *find out* why it was done, or please do everyone involved a service and stop this. There isn't any conspiracy here, sorry! ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 18:53:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 008AA14C2B for ; Wed, 16 Jun 1999 18:53:08 -0700 (PDT) (envelope-from brooks@one-eyed-alien.net) Received: from localhost (brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) with ESMTP id SAA03949 for ; Wed, 16 Jun 1999 18:53:02 -0700 (PDT) From: brooks@one-eyed-alien.net X-Authentication-Warning: orion.ac.hmc.edu: brdavis owned process doing -bs Date: Wed, 16 Jun 1999 18:53:02 -0700 (PDT) X-Sender: brdavis@orion.ac.hmc.edu To: freebsd-hackers@freebsd.org Subject: changes to ether_output() 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, I've been doing some work which caused me to want to write a simple userland bridging/filtering program (don't ask ;-). The easy way to do it seemed to be to use BPF to read and write the packets one each side. I wrote something up in a few hundred lines of code which worked (mostly) as long as no one did much broadcast and I threw away multicast packets. After some searching I found a refrence in libnet (ports/net/libnet) which said the problem was that while BPF takes a whole packet and claims to write it to the wire, it actually ignores the source address and uses the one assigned to the card. They had an LKM which fixed the problem, but it was based on a mid-1997 version of net/if_ethersubr.c from 2.2.x and had a number of things commented out that probably shouldn't have been. I've taken the key lines from the LKM and produced a patch which adds optional support for for spoofing the source address of certain ethernet packets. It's a compile time option and is controled by a sysctl which defaults to off and doesn't work in secure mode. The patch is included below. The diff is against 3.2-STABLE as of a couple weeks ago and it looks like part of it may have to be applyed by hand on -current. Please let me know what you think. -- Brooks P.S. If someone is willing to commit this, I'll also create the appropriate LINT entry to go with it. *** net/if_ethersubr.c.orig Tue Jun 15 18:46:10 1999 --- net/if_ethersubr.c Wed Jun 16 18:21:42 1999 *************** *** 38,43 **** --- 38,44 ---- #include "opt_inet.h" #include "opt_ipx.h" #include "opt_bdg.h" + #include "opt_ether.h" #include #include *************** *** 111,116 **** --- 112,125 ---- #include #endif /* NVLAN > 0 */ + SYSCTL_NODE(_net_link, IFT_ETHER, ether, CTLFLAG_RW, 0, "Ethernet"); + + #ifdef ETHER_SPOOF_SRC + static int spoof_src = 0; + SYSCTL_INT(_net_link_ether, OID_AUTO, spoof_src, CTLFLAG_RW|CTLFLAG_SECURE, + &spoof_src, 0, "Allow Ethernet source addresses to be spoofed"); + #endif + static int ether_resolvemulti __P((struct ifnet *, struct sockaddr **, struct sockaddr *)); u_char etherbroadcastaddr[6] = { 0xff, 0xff, 0xff, 0xff, 0xff, 0xff }; *************** *** 133,138 **** --- 142,150 ---- short type; int s, error = 0; u_char edst[6]; + #ifdef ETHER_SPOOF_SRC + u_char esrc[6]; + #endif register struct mbuf *m = m0; register struct rtentry *rt; register struct ether_header *eh; *************** *** 167,172 **** --- 179,187 ---- time_second < rt->rt_rmx.rmx_expire) senderr(rt == rt0 ? EHOSTDOWN : EHOSTUNREACH); } + #ifdef ETHER_SPOOF_SRC + (void)memcpy(esrc, ac->ac_enaddr, sizeof (esrc)); + #endif hlen = ETHER_HDR_LEN; switch (dst->sa_family) { #ifdef INET *************** *** 333,338 **** --- 348,357 ---- loop_copy = -1; /* if this is for us, don't do it */ eh = (struct ether_header *)dst->sa_data; (void)memcpy(edst, eh->ether_dhost, sizeof (edst)); + #ifdef ETHER_SPOOF_SRC + if (spoof_src != 0) + (void)memcpy(esrc, eh->ether_shost, sizeof (esrc)); + #endif type = eh->ether_type; break; *************** *** 353,360 **** --- 372,383 ---- (void)memcpy(&eh->ether_type, &type, sizeof(eh->ether_type)); (void)memcpy(eh->ether_dhost, edst, sizeof (edst)); + #ifdef ETHER_SPOOF_SRC + (void)memcpy(eh->ether_shost, esrc, sizeof (esrc)); + #else (void)memcpy(eh->ether_shost, ac->ac_enaddr, sizeof(eh->ether_shost)); + #endif /* * If a simplex interface, and the packet is being sent to our *************** *** 679,686 **** sdl->sdl_alen = ifp->if_addrlen; bcopy(((struct arpcom *)ifp)->ac_enaddr, LLADDR(sdl), ifp->if_addrlen); } - - SYSCTL_NODE(_net_link, IFT_ETHER, ether, CTLFLAG_RW, 0, "Ethernet"); int ether_ioctl(ifp, command, data) --- 702,707 ---- *** conf/options.orig Fri May 21 15:45:39 1999 --- conf/options Wed Jun 16 18:19:51 1999 *************** *** 221,226 **** --- 221,227 ---- IPFILTER opt_ipfilter.h IPFILTER_LOG opt_ipfilter.h IPFILTER_LKM opt_ipfilter.h + ETHER_SPOOF_SRC opt_ether.h # ATM (HARP version) ATM_CORE opt_atm.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 20:35:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from medulla.hippocampus.net (medulla.hippocampus.net [204.138.241.6]) by hub.freebsd.org (Postfix) with ESMTP id E166514BDA for ; Wed, 16 Jun 1999 20:35:53 -0700 (PDT) (envelope-from marc@netstor.com) Received: from localhost (marc@localhost) by medulla.hippocampus.net (8.9.2/8.9.2) with ESMTP id XAA02019; Wed, 16 Jun 1999 23:42:32 -0400 (EDT) Date: Wed, 16 Jun 1999 23:42:32 -0400 (EDT) From: Marc Nicholas X-Sender: marc@medulla.hippocampus.net To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: DLINK quad ethernet board In-Reply-To: <199906170047.UAA15480@etinc.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 Load balancing will always be done at the driver level, and not in board logic...you want those separate MACs etc. :-) This is true of all the boards I'm familiar with. I'm actually trying to implement EtherChannel under FreeBSD for Znyx boards right now. -marc ---------------------------------------------------------------- Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com "Fast, Expandable and Affordable Internet Caching Products" 1.877.464.4776 416.979.9000 fax: 416.979.8223 cell: 416.346.9255 On Wed, 16 Jun 1999, Dennis wrote: > At 05:06 PM 6/16/99 -0400, you wrote: > >At a chipset level (DEC 21143) yes...in the same way a Znyx card would > >work. > > > >It looks like the card also uses a DEC bridge chip too (not unussual on > >multi-port Ethernet cards) and FreeBSD will also cope fine with that too. > > > >HOWEVER...be aware that some BIOSes mess up the initialization of such > >beasties (PCI bridging and all). > > I also notice that DLINK markets this as a "load balancing board" which > "appears as a single nic to the system". I assume that their windows driver > makes it look like that, but it may have a strange interface. > > They are apparently a lot cheaper than Zynx boards (with the same > technology)....Although I havent really found any of the DLINK dealers that > sell them. > > Dennis > > > >So, in short, it should work...but I've never tried it :-) > > > >Out of interest, how much do DLink knock these puppies out of? > > > > > >-marc > > > >---------------------------------------------------------------- > >Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com > >"Fast, Expandable and Affordable Internet Caching Products" > >1.877.464.4776 416.979.9000 fax: 416.979.8223 cell: 416.346.9255 > > > >On Wed, 16 Jun 1999, Dennis wrote: > > > >> > >> Is this board supported? Anyone using them? > >> > >> 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 16 22:34:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 212CD151D7 for ; Wed, 16 Jun 1999 22:33:16 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id FAA14875; Thu, 17 Jun 1999 05:05:19 +0200 From: Luigi Rizzo Message-Id: <199906170305.FAA14875@labinfo.iet.unipi.it> Subject: Re: changes to ether_output() To: brooks@one-eyed-alien.net Date: Thu, 17 Jun 1999 05:05:19 +0200 (MET DST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "brooks@one-eyed-alien.net" at Jun 16, 99 06:52:43 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 920 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > I've been doing some work which caused me to want to write a simple > userland bridging/filtering program (don't ask ;-). The easy way to do it ok, i won't ask, just remind you that freebsd (in 2.2.8, 3.2, 4.x) has bridging integrated with the ipfw so you can do bridging and filtering entirely in the kernel using standard tools -- you can even use the PicoBSD images from http://www.iet.unipi.it/~luigi/ip_dummynet/ for this cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) http://www.iet.unipi.it/~luigi/ngc99/ ==== First International Workshop on Networked Group Communication ==== -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 17 0:37:10 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 8722F15169 for ; Thu, 17 Jun 1999 00:37:07 -0700 (PDT) (envelope-from ust@cert.siemens.de) X-Envelope-Sender-Is: ust@cert.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 JAA14262; Thu, 17 Jun 1999 09:37:06 +0200 (MET DST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail2.siemens.de (8.9.3/8.9.3) with ESMTP id JAA23688; Thu, 17 Jun 1999 09:37:05 +0200 (MET DST) Received: from alaska.cert.siemens.de (alaska.cert.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.9.3/8.9.3/Siemens CERT [ $Revision: 1.9 ]) with ESMTP id JAA02675; Thu, 17 Jun 1999 09:38:10 +0200 (CEST) Received: (from ust@localhost) by alaska.cert.siemens.de (8.9.3/8.9.3/alaska [ $Revision: 1.2 ]) id HAA03656; Thu, 17 Jun 1999 07:38:10 GMT (envelope-from ust) Date: Thu, 17 Jun 1999 09:38:10 +0200 From: Udo Schweigert To: John Polstra Cc: hackers@FreeBSD.ORG Subject: Re: m3socks and cvsup Message-ID: <19990617092316.B3119@alaska.cert.siemens.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i X-Mailer: Mutt 0.95.5i In-Reply-To: <199906170110.SAA66976@vashon.polstra.com>; from John Polstra on Wed, Jun 16, 1999 at 06:10:42PM -0700 X-Operating-System: FreeBSD 3.2-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jun 16, 1999 at 06:10:42PM -0700, John Polstra wrote: > Udo Schweigert wrote: > > > I'm using it (runsocks cvsup -P m) for a year now and it works > > without any problems. (Since cvsup 16 the "-P m" is not needed, so > > "runsocks cvsup" should so it). > > Just to make sure I understand: You're using standard socks rather > than m3socks, right? > > I believe that standard socks should work with cvsup's multiplexed > mode, but I've never tried it. It would probably be necessary to add > "@M3novm" to the command line, though. If standard socks works, then > I want to eliminate m3socks. There are some problems with m3socks > that I just found out about recently. > Hello John, I'm not using m3socks, I use the standard socks5 from ports (current version is socks5-1.0.8). To use it (the runsocks program) with cvsup one has to build cvsup with dynamic linking (by building port net/cvsup), the precompiled package from CD-ROM and the one from net/cvsup-bin port will not work. For example I changed in /usr/local/etc/cvsup/update.sh (contained in net/cvsup-mirror port): < cvsup -1gL 1 -c ${colldir} -h ${host} supfile --- > runsocks cvsup -P m -1gL 1 -c ${colldir} -h ${host} supfile As stated before, this works since approx. one year without any problems. As I remember, I used m3socks for a short time, but when I noticed that runsocks also worked, I changed to that. Regards ------------------------------------------------------------------------------- Udo Schweigert || Voice : +49 89 636 42170 Siemens AG, Siemens CERT || Fax : +49 89 636 48000 ZT IK 3 || email : Udo.Schweigert@mchp.siemens.de D-81730 Muenchen / Germany || : ust@cert.siemens.de PGP fingerprint || 2A 53 F6 A6 30 59 64 02 6B C4 E0 73 B2 C9 6C E7 ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 17 0:43:13 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 2E39515169 for ; Thu, 17 Jun 1999 00:43:11 -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 DAA16929 for ; Thu, 17 Jun 1999 03:43:00 -0400 (EDT) Message-Id: <199906170743.DAA16929@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: vinum performance Date: Thu, 17 Jun 1999 03:43:10 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a drive that is rated at ~16 Meg/second, and indeed it delivers on the order of 15+ Meg/second. If I use Vinum to create a concatinated device of 2 such units performance drops to 2.5 Meg/sec. This seems like a drastic drop in performance. Any ideas what I am doin incorrectly? -- 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 Jun 17 1: 4:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ACC.sumy.net (ACC.sim.net.ua [62.244.20.221]) by hub.freebsd.org (Postfix) with ESMTP id DD982150F5 for ; Thu, 17 Jun 1999 01:04:20 -0700 (PDT) (envelope-from pasha@sim.net.ua) Received: from sim.net.ua (GW.sumy.net [62.244.20.220]) by ACC.sumy.net (8.9.3/8.9.3) with ESMTP id LAA23841; Thu, 17 Jun 1999 11:03:33 +0300 (EEST) Message-ID: <3768ABD4.FD515328@sim.net.ua> Date: Thu, 17 Jun 1999 11:03:32 +0300 From: Pavel Narozhniy X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: uk, ru, en MIME-Version: 1.0 To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vinum performance References: <199906170743.DAA16929@cs.rpi.edu> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David E. Cross" wrote: > > I have a drive that is rated at ~16 Meg/second, and indeed it delivers on the > order of 15+ Meg/second. If I use Vinum to create a concatinated device > of 2 such units performance drops to 2.5 Meg/sec. This seems like a > drastic drop in performance. Any ideas what I am doin incorrectly? Try to place those drives on two different SCSI controllers. -- Pavel Narozhniy nic-hdl: PN395-RIPE http://www.sumy.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 17 1:10:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id 43118150F5 for ; Thu, 17 Jun 1999 01:10:11 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id LAA28334; Thu, 17 Jun 1999 11:10:08 +0300 (EEST) Date: Thu, 17 Jun 1999 11:10:08 +0300 (EEST) From: Narvi To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vinum performance In-Reply-To: <199906170743.DAA16929@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 Thu, 17 Jun 1999, David E. Cross wrote: > I have a drive that is rated at ~16 Meg/second, and indeed it delivers on the > order of 15+ Meg/second. If I use Vinum to create a concatinated device > of 2 such units performance drops to 2.5 Meg/sec. This seems like a > drastic drop in performance. Any ideas what I am doin incorrectly? > Try changing stripe size. How big is it right now? > -- > 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 > Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 17 1:11:38 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 2B200150F5 for ; Thu, 17 Jun 1999 01:11:33 -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 RAA03673; Thu, 17 Jun 1999 17:41:31 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id RAA51596; Thu, 17 Jun 1999 17:41:38 +0930 (CST) Date: Thu, 17 Jun 1999 17:41:36 +0930 From: Greg Lehey To: Pavel Narozhniy Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: vinum performance Message-ID: <19990617174135.M9893@freebie.lemis.com> References: <199906170743.DAA16929@cs.rpi.edu> <3768ABD4.FD515328@sim.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <3768ABD4.FD515328@sim.net.ua>; from Pavel Narozhniy on Thu, Jun 17, 1999 at 11:03:32AM +0300 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 Thursday, 17 June 1999 at 11:03:32 +0300, Pavel Narozhniy wrote: > "David E. Cross" wrote: >> >> I have a drive that is rated at ~16 Meg/second, and indeed it delivers on the >> order of 15+ Meg/second. If I use Vinum to create a concatinated device >> of 2 such units performance drops to 2.5 Meg/sec. This seems like a >> drastic drop in performance. Any ideas what I am doin incorrectly? > > Try to place those drives on two different SCSI controllers. That wouldn't be the problem with a concatenated plex. 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 Thu Jun 17 1:17:59 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 D791C15724 for ; Thu, 17 Jun 1999 01:17:40 -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 RAA03685; Thu, 17 Jun 1999 17:47:41 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id RAA52025; Thu, 17 Jun 1999 17:47:47 +0930 (CST) Date: Thu, 17 Jun 1999 17:47:47 +0930 From: Greg Lehey To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vinum performance Message-ID: <19990617174746.N9893@freebie.lemis.com> References: <199906170743.DAA16929@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906170743.DAA16929@cs.rpi.edu>; from David E. Cross on Thu, Jun 17, 1999 at 03:43:10AM -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 Thursday, 17 June 1999 at 3:43:10 -0400, David E. Cross wrote: > I have a drive that is rated at ~16 Meg/second, and indeed it delivers on the > order of 15+ Meg/second. If I use Vinum to create a concatinated device > of 2 such units performance drops to 2.5 Meg/sec. This seems like a > drastic drop in performance. Indeed, if you're comparing apples with apples. > Any ideas what I am doin incorrectly? No. You haven't really given any details. Most of the performance testing I have done has been with striped plexes (which offer the potential for better performance), and I've found that in massively concurrent situations the performance is roughly what you would expect (almost n * normal disk performance, where n is the number of disks in the stripe set. I'd expect performance of a concatenated plex to be pretty close to that of the raw disk. How are you measuring performance? I'd recommend rawio (ftp://ftp.lemis.com/pub/rawio.tar.gz). 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 Thu Jun 17 1:18: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 AE6ED14CA4 for ; Thu, 17 Jun 1999 01:18:17 -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 RAA03694; Thu, 17 Jun 1999 17:48:17 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id RAA52060; Thu, 17 Jun 1999 17:48:24 +0930 (CST) Date: Thu, 17 Jun 1999 17:48:24 +0930 From: Greg Lehey To: Narvi Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: vinum performance Message-ID: <19990617174823.O9893@freebie.lemis.com> References: <199906170743.DAA16929@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Narvi on Thu, Jun 17, 1999 at 11:10:08AM +0300 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 Thursday, 17 June 1999 at 11:10:08 +0300, Narvi wrote: > > On Thu, 17 Jun 1999, David E. Cross wrote: > >> I have a drive that is rated at ~16 Meg/second, and indeed it delivers on the >> order of 15+ Meg/second. If I use Vinum to create a concatinated device >> of 2 such units performance drops to 2.5 Meg/sec. This seems like a >> drastic drop in performance. Any ideas what I am doin incorrectly? > > Try changing stripe size. How big is it right now? This was a concatenated plex. 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 Thu Jun 17 1:55: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (Postfix) with SMTP id 5BBDF150F5 for ; Thu, 17 Jun 1999 01:55:05 -0700 (PDT) (envelope-from will@ns.oeno.com) Received: (qmail 27329 invoked by uid 1001); 17 Jun 1999 08:55:04 -0000 To: crossd@cs.rpi.edu (David E. Cross) Cc: hackers@freebsd.org Subject: Re: vinum performance References: <199906170743.DAA16929@cs.rpi.edu> From: Ville-Pertti Keinonen Date: 17 Jun 1999 11:52:43 +0300 In-Reply-To: crossd@cs.rpi.edu's message of "17 Jun 1999 10:43:31 +0300" Message-ID: <86so7rqkdg.fsf@not.demophon.com> Lines: 26 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG crossd@cs.rpi.edu (David E. Cross) writes: > I have a drive that is rated at ~16 Meg/second, and indeed it delivers on the > order of 15+ Meg/second. If I use Vinum to create a concatinated device > of 2 such units performance drops to 2.5 Meg/sec. This seems like a > drastic drop in performance. Any ideas what I am doin incorrectly? You've accidentally striped subdisks on the same drive? ;--) Like Greg Lehey said, you haven't really provided enough details. The minimum info required would be: - Is this read or write performance? Many disks are shipped with write caching disabled, and write performance can be significantly worse than read performance. It shouldn't be quite *that* bad, though, I get better write performance with slower disks, write caching disabled and mirroring (with the default 3.2 vinum - which has debugging compiled in, look at the bss size...). - Are you testing through the filesystem? (How are you testing?) Maybe you're doing a dd test and accessing /dev/vinum/vol/* rather than /dev/vinum/rvol/*... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 17 2: 2:28 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 785BB150F5 for ; Thu, 17 Jun 1999 02:02:21 -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 SAA03887; Thu, 17 Jun 1999 18:32:20 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id SAA52465; Thu, 17 Jun 1999 18:32:26 +0930 (CST) Date: Thu, 17 Jun 1999 18:32:25 +0930 From: Greg Lehey To: Ville-Pertti Keinonen Cc: "David E. Cross" , hackers@FreeBSD.ORG Subject: Re: vinum performance Message-ID: <19990617183225.Q9893@freebie.lemis.com> References: <199906170743.DAA16929@cs.rpi.edu> <86so7rqkdg.fsf@not.demophon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <86so7rqkdg.fsf@not.demophon.com>; from Ville-Pertti Keinonen on Thu, Jun 17, 1999 at 11:52:43AM +0300 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 Thursday, 17 June 1999 at 11:52:43 +0300, Ville-Pertti Keinonen wrote: > > crossd@cs.rpi.edu (David E. Cross) writes: > >> I have a drive that is rated at ~16 Meg/second, and indeed it delivers on the >> order of 15+ Meg/second. If I use Vinum to create a concatinated device >> of 2 such units performance drops to 2.5 Meg/sec. This seems like a >> drastic drop in performance. Any ideas what I am doin incorrectly? > > You've accidentally striped subdisks on the same drive? ;--) > > Like Greg Lehey said, you haven't really provided enough details. He did provide one detail, though; this is a concatenated plex, not a striped one. > The minimum info required would be: > > - Is this read or write performance? That wouldn't be enough. > Many disks are shipped with write caching disabled, and write > performance can be significantly worse than read performance. Not if it works without Vinum. > - Are you testing through the filesystem? (How are you testing?) That's the real qustion. > Maybe you're doing a dd test and accessing /dev/vinum/vol/* rather > than /dev/vinum/rvol/*... That would, in fact, be faster. But we need to know what he's doing, and I suspect you're on the right track. 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 Thu Jun 17 2:15:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 7A46B152E6 for ; Thu, 17 Jun 1999 02:15:48 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 6729679; Thu, 17 Jun 1999 17:15:46 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: Matthew Dillon , Matthew Jacob , freebsd-hackers@FreeBSD.ORG Subject: Re: D'oh! In-reply-to: Your message of "Tue, 15 Jun 1999 13:06:40 MST." <199906152006.NAA12531@dingo.CDROM.com> Date: Thu, 17 Jun 1999 17:15:46 +0800 From: Peter Wemm Message-Id: <19990617091546.6729679@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > The problem is that peter is not releasing the nfs_node_hash_lock > > when he goes to retry, creating a deadlock with himself. > > > > Peter, looks like a quick fix & commit to me, I'd say just go ahead > > and do it. > > Peter is sic transit mundi at the moment, having missed his original > flight back from Usenix. This probably calls for another committer > (eg. one of the Matts...) Just as a FYI for others in future, never trust Mike's assurances that you've got plenty of time to get to the airport.. :-) Getting lost (twice!) wasn't factored into it, and I didn't have maps of either area. Oh well, at least I got a self-guided tour of Walnut Creek by night... :-) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 17 3:44:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailer.syr.edu (mailer.syr.edu [128.230.18.29]) by hub.freebsd.org (Postfix) with ESMTP id D804915337 for ; Thu, 17 Jun 1999 03:44:35 -0700 (PDT) (envelope-from cmsedore@mailbox.syr.edu) Received: from rodan.syr.edu by mailer.syr.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.DE8DCDC0@mailer.syr.edu>; Thu, 17 Jun 1999 6:44:38 -0400 Received: from localhost (cmsedore@localhost) by rodan.syr.edu (8.8.7/8.8.7) with ESMTP id GAA29879; Thu, 17 Jun 1999 06:44:33 -0400 (EDT) X-Authentication-Warning: rodan.syr.edu: cmsedore owned process doing -bs Date: Thu, 17 Jun 1999 06:44:33 -0400 (EDT) From: Christopher Sedore X-Sender: cmsedore@rodan.syr.edu To: brooks@one-eyed-alien.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: changes to ether_output() 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, 16 Jun 1999 brooks@one-eyed-alien.net wrote: > Hi, > > I've been doing some work which caused me to want to write a simple > userland bridging/filtering program (don't ask ;-). The easy way to do it > seemed to be to use BPF to read and write the packets one each side. I > wrote something up in a few hundred lines of code which worked (mostly) as > long as no one did much broadcast and I threw away multicast packets. > After some searching I found a refrence in libnet (ports/net/libnet) which > said the problem was that while BPF takes a whole packet and claims to > write it to the wire, it actually ignores the source address and uses the > one assigned to the card. They had an LKM which fixed the problem, but it > was based on a mid-1997 version of net/if_ethersubr.c from 2.2.x and had a > number of things commented out that probably shouldn't have been. > > I've taken the key lines from the LKM and produced a patch which adds > optional support for for spoofing the source address of certain ethernet > packets. It's a compile time option and is controled by a sysctl which > defaults to off and doesn't work in secure mode. The patch is included > below. The diff is against 3.2-STABLE as of a couple weeks ago and it > looks like part of it may have to be applyed by hand on -current. > > Please let me know what you think. I filed a kernel bug report about this early this year. This is a bug in the BPF implementation on FreeBSD (at least this was the consensus of those who reacted when I posted about it). If you look in the gnats pages you'll find my report and a patch to fix bpf. I don't remember the code well enough to envision what your patch does, but you might want to look over mine just to see what I did (it didn't look to me like you fixed bpf, but maybe I'm missing that). -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 17 5:52:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (Postfix) with SMTP id CEF5C15378 for ; Thu, 17 Jun 1999 05:52:32 -0700 (PDT) (envelope-from will@ns.oeno.com) Received: (qmail 4029 invoked by uid 1001); 17 Jun 1999 12:52:31 -0000 To: grog@lemis.com (Greg Lehey) Cc: hackers@freebsd.org Subject: Re: vinum performance References: <199906170743.DAA16929@cs.rpi.edu> <19990617183225.Q9893@freebie.lemis.com> From: Ville-Pertti Keinonen Date: 17 Jun 1999 15:50:10 +0300 In-Reply-To: grog@lemis.com's message of "17 Jun 1999 12:02:50 +0300" Message-ID: <86r9nbq9dp.fsf@not.demophon.com> Lines: 22 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG grog@lemis.com (Greg Lehey) writes: > > You've accidentally striped subdisks on the same drive? ;--) > > > > Like Greg Lehey said, you haven't really provided enough details. > > He did provide one detail, though; this is a concatenated plex, not a > striped one. Or he at least *thinks* it's concatenated. ;--) I didn't miss that - but given numbers that bad, it sounds like there might be some really silly mistake involved. > > Many disks are shipped with write caching disabled, and write > > performance can be significantly worse than read performance. > > Not if it works without Vinum. My thought was that he might be comparing read performance and write performance (they are often pretty close). But even so, the difference shouldn't be *that* big. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 17 10:46:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id BFCB214FC7 for ; Thu, 17 Jun 1999 10:46:31 -0700 (PDT) (envelope-from brooks@one-eyed-alien.net) Received: from localhost (brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) with ESMTP id KAA29846; Thu, 17 Jun 1999 10:46:22 -0700 (PDT) From: brooks@one-eyed-alien.net X-Authentication-Warning: orion.ac.hmc.edu: brdavis owned process doing -bs Date: Thu, 17 Jun 1999 10:46:22 -0700 (PDT) X-Sender: brdavis@orion.ac.hmc.edu To: Luigi Rizzo Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: changes to ether_output() In-Reply-To: <199906170305.FAA14875@labinfo.iet.unipi.it> 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, 17 Jun 1999, Luigi Rizzo wrote: > > I've been doing some work which caused me to want to write a simple > > userland bridging/filtering program (don't ask ;-). The easy way to do it > > ok, i won't ask, just remind you that freebsd (in 2.2.8, 3.2, 4.x) > has bridging integrated with the ipfw so you can do bridging and > filtering entirely in the kernel using standard tools -- you can even > use the PicoBSD images from http://www.iet.unipi.it/~luigi/ip_dummynet/ > for this I know, I'm using that code when my bridge isn't running. It's just that I want to keep my filtering (and packet mangling) in userland so the system doesn't panic when I do something stupid. -- Brooks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 17 11: 2: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 4D5E515137 for ; Thu, 17 Jun 1999 11:02:02 -0700 (PDT) (envelope-from brooks@one-eyed-alien.net) Received: from localhost (brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) with ESMTP id LAA01274; Thu, 17 Jun 1999 11:01:56 -0700 (PDT) From: brooks@one-eyed-alien.net X-Authentication-Warning: orion.ac.hmc.edu: brdavis owned process doing -bs Date: Thu, 17 Jun 1999 11:01:55 -0700 (PDT) X-Sender: brdavis@orion.ac.hmc.edu To: Christopher Sedore Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: changes to ether_output() 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, 17 Jun 1999, Christopher Sedore wrote: > I filed a kernel bug report about this early this year. This is a bug in > the BPF implementation on FreeBSD (at least this was the consensus of > those who reacted when I posted about it). If you look in the gnats pages > you'll find my report and a patch to fix bpf. I don't remember the code > well enough to envision what your patch does, but you might want to look > over mine just to see what I did (it didn't look to me like you fixed bpf, > but maybe I'm missing that). It looks like they should both work. The difference is that your patch changes bpf to use AF_LINK and adds handling code and mine changes the way AF_UNSPEC is implemented so that the provided ethernet header is actually used. One could argue that if you pass in an ethernet header, you should be able to expect it is acutally used. On the other hand, one could argue that unless you tell the system you want to communicate at the link layer, it shouldn't let you mess with your link layer settings. Does anyone know what the historical answer would be? -- Brooks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 17 12:37: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id 18C2A14FAC for ; Thu, 17 Jun 1999 12:37:01 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id WAA08832; Thu, 17 Jun 1999 22:36:50 +0300 (EEST) Date: Thu, 17 Jun 1999 22:36:49 +0300 (EEST) From: Narvi To: Greg Lehey Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: vinum performance In-Reply-To: <19990617174823.O9893@freebie.lemis.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, 17 Jun 1999, Greg Lehey wrote: > On Thursday, 17 June 1999 at 11:10:08 +0300, Narvi wrote: > > > > On Thu, 17 Jun 1999, David E. Cross wrote: > > > >> I have a drive that is rated at ~16 Meg/second, and indeed it delivers on the > >> order of 15+ Meg/second. If I use Vinum to create a concatinated device > >> of 2 such units performance drops to 2.5 Meg/sec. This seems like a > >> drastic drop in performance. Any ideas what I am doin incorrectly? > > > > Try changing stripe size. How big is it right now? > > This was a concatenated plex. > Do we know that for a fact? It could be concatenated by striping. And no, i am not sure he was using vinum terminology (and he didn't say plex anywhere). > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 17 13:51:32 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 C3CB7155A4 for ; Thu, 17 Jun 1999 13:51:27 -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 GAA06269; Fri, 18 Jun 1999 06:21:26 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id GAA54090; Fri, 18 Jun 1999 06:21:34 +0930 (CST) Date: Fri, 18 Jun 1999 06:21:33 +0930 From: Greg Lehey To: Narvi Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: vinum performance Message-ID: <19990618062133.S9893@freebie.lemis.com> References: <19990617174823.O9893@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Narvi on Thu, Jun 17, 1999 at 10:36:49PM +0300 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 Thursday, 17 June 1999 at 22:36:49 +0300, Narvi wrote: > > On Thu, 17 Jun 1999, Greg Lehey wrote: > >> On Thursday, 17 June 1999 at 11:10:08 +0300, Narvi wrote: >>> >>> On Thu, 17 Jun 1999, David E. Cross wrote: >>> >>>> I have a drive that is rated at ~16 Meg/second, and indeed it delivers on the >>>> order of 15+ Meg/second. If I use Vinum to create a concatinated device >>>> of 2 such units performance drops to 2.5 Meg/sec. This seems like a >>>> drastic drop in performance. Any ideas what I am doin incorrectly? >>> >>> Try changing stripe size. How big is it right now? >> >> This was a concatenated plex. > > Do we know that for a fact? I see no reason to doubt what he said. > It could be concatenated by striping. No, the organizations are concatenated, striped or RAID-5. One doesn't mean the other. > And no, i am not sure he was using vinum terminology (and he didn't > say plex anywhere). I don't know any other usage of the word "concatenated" in this connection. 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 Thu Jun 17 13:53: 5 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 ADC0E155A4 for ; Thu, 17 Jun 1999 13:52:55 -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 GAA06277; Fri, 18 Jun 1999 06:22:55 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id GAA54107; Fri, 18 Jun 1999 06:23:04 +0930 (CST) Date: Fri, 18 Jun 1999 06:23:03 +0930 From: Greg Lehey To: Ville-Pertti Keinonen Cc: hackers@freebsd.org Subject: Re: vinum performance Message-ID: <19990618062303.T9893@freebie.lemis.com> References: <199906170743.DAA16929@cs.rpi.edu> <19990617183225.Q9893@freebie.lemis.com> <86r9nbq9dp.fsf@not.demophon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <86r9nbq9dp.fsf@not.demophon.com>; from Ville-Pertti Keinonen on Thu, Jun 17, 1999 at 03:50:10PM +0300 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 Thursday, 17 June 1999 at 15:50:10 +0300, Ville-Pertti Keinonen wrote: > > grog@lemis.com (Greg Lehey) writes: > >>> You've accidentally striped subdisks on the same drive? ;--) >>> >>> Like Greg Lehey said, you haven't really provided enough details. >> >> He did provide one detail, though; this is a concatenated plex, not a >> striped one. > > Or he at least *thinks* it's concatenated. ;--) I didn't miss that - > but given numbers that bad, it sounds like there might be some really > silly mistake involved. OK, you're the second person to say that. Let's wait until he comes back with more details. >>> Many disks are shipped with write caching disabled, and write >>> performance can be significantly worse than read performance. >> >> Not if it works without Vinum. > > My thought was that he might be comparing read performance and write > performance (they are often pretty close). But even so, the > difference shouldn't be *that* big. I'm sure there's something wrong here. I'd just like to find out what it is. I don't think it's with Vinum, but I'm prepared to be proven wrong. 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 Thu Jun 17 19:14:50 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 0F29014C1A; Thu, 17 Jun 1999 19:14:44 -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 LAA07691; Fri, 18 Jun 1999 11:44:43 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA01748; Fri, 18 Jun 1999 11:44:51 +0930 (CST) Date: Fri, 18 Jun 1999 11:44:50 +0930 From: Greg Lehey To: FreeBSD current users , FreeBSD Hackers Subject: Remote serial gdb--status? Message-ID: <19990618114450.Q9893@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 I've been away from work for several weeks, and I now find that I can no longer start remote serial gdb. I am using sio0 on the debugged machine side, and sio1 on the debugging machine side. Here are the relevant dmesg outputs: panic (debugged machine): sio0: system console sio0: gdb debugging port ... sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0 sio0: type 16550A freebie (debugging machine): sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 I can communicate fine using cu, and a breakout box shows all modem signals asserte (DCD, DTR, DSR, RTS, CTS). When I go into remote debug on panic, RxD flashes, and when freebie tries to attach to panic, TxD flashes, so I'm obviously addressing the correct ports. I've checked the bit rate and configuration of the ports before going into debug, and they look right (9600 bps, cs8, -istrip, -parenb). I don't know what else to look for. Any ideas? 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 Thu Jun 17 19:49:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monk.via.net (monk.via.net [209.81.9.10]) by hub.freebsd.org (Postfix) with ESMTP id 36C48155D7 for ; Thu, 17 Jun 1999 19:49:48 -0700 (PDT) (envelope-from joe@monk.via.net) Received: (from joe@localhost) by monk.via.net (8.8.8/8.8.8) id TAA21896 for hackers@freebsd.org; Thu, 17 Jun 1999 19:49:47 -0700 (PDT) (envelope-from joe) Date: Thu, 17 Jun 1999 19:49:47 -0700 (PDT) From: Joe McGuckin Message-Id: <199906180249.TAA21896@monk.via.net> To: hackers@freebsd.org Subject: CD writer - which one to buy? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I want to make CDROMS - data and music. Which is the preferred drive? What software do I use to write filesystems to the CDROM? I also want to make some custom CD's (for listening in my car) from my largish collection of audio CD's. What software can I use to copy the audio tracks onto disk and rewrite them onto CDROM? Thanks! Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 17 21:36: 3 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 CC66714DB0 for ; Thu, 17 Jun 1999 21:36: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 VAA22527; Thu, 17 Jun 1999 21:35:59 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id VAA90484; Thu, 17 Jun 1999 21:35:59 -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: <19990617092316.B3119@alaska.cert.siemens.de> Date: Thu, 17 Jun 1999 21:35:59 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Udo Schweigert Subject: Re: m3socks and cvsup Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Udo Schweigert wrote: > I'm not using m3socks, I use the standard socks5 from ports (current > version is socks5-1.0.8). To use it (the runsocks program) with > cvsup one has to build cvsup with dynamic linking (by building port > net/cvsup), the precompiled package from CD-ROM and the one from > net/cvsup-bin port will not work. > > For example I changed in /usr/local/etc/cvsup/update.sh (contained in > net/cvsup-mirror port): > > < cvsup -1gL 1 -c ${colldir} -h ${host} supfile > --- > > runsocks cvsup -P m -1gL 1 -c ${colldir} -h ${host} supfile > > As stated before, this works since approx. one year without any problems. Thanks for the information. I was pretty sure that multiplexed mode had eliminated the need for a special socks package, but I hadn't checked it myself. I recommend adding "@M3novm" to the cvsup command line when using socks. Otherwise you might get "Bad address" errors occasionally. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 1: 1:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from saturn.ms.tlk.com (saturn.ms.tlk.com [194.97.68.6]) by hub.freebsd.org (Postfix) with ESMTP id D5F3315225 for ; Fri, 18 Jun 1999 01:01:19 -0700 (PDT) (envelope-from br@smilla.rueskamp.com) Received: from mars.ms.tlk.com (mars.ms.tlk.com [194.97.68.1]) by saturn.ms.tlk.com (Postfix) with ESMTP id A45554ECD8 for ; Fri, 18 Jun 1999 10:01:18 +0200 (CEST) Received: from smilla.rueskamp.com(really [194.97.69.109]) by mars.ms.tlk.com via sendmail with esmtp id for ; Fri, 18 Jun 1999 10:01:18 +0200 (CEST)) Received: (from br@localhost) by smilla.rueskamp.com (8.9.3/8.9.3) id KAA08569 for freebsd-hackers@freebsd.org; Fri, 18 Jun 1999 10:01:15 +0200 (CEST) (envelope-from br) From: Bodo Rueskamp Message-Id: <199906180801.KAA08569@smilla.rueskamp.com> Subject: pthread_cancel To: freebsd-hackers@freebsd.org Date: Fri, 18 Jun 1999 10:01:15 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Is anyone working on pthread_cancel? ; Bodo -- Bodo Rüskamp, br@rueskamp.com, 51°55' N 7°41' E (1) Elvis is alive. (2) Dinosaurs too. (3) The next millenium starts on January 1st 2000. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 1:14:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id C78DF14CF5 for ; Fri, 18 Jun 1999 01:14:23 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from srmail.sr.hp.com (srmail.sr.hp.com [15.4.45.14]) by palrel3.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id BAA24842 for ; Fri, 18 Jun 1999 01:14:22 -0700 (PDT) Received: from mina.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA086993661; Fri, 18 Jun 1999 01:14:21 -0700 Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id BAA29087 for ; Fri, 18 Jun 1999 01:14:21 -0700 (PDT) Message-Id: <199906180814.BAA29087@mina.sr.hp.com> To: freebsd-hackers@freebsd.org Subject: Re: vinum performance Reply-To: Darryl Okahata In-Reply-To: Your message of "Thu, 17 Jun 1999 17:47:47 +0930." Mime-Version: 1.0 (generated by tm-edit 1.1.1.1) Content-Type: text/plain; charset=US-ASCII Date: Fri, 18 Jun 1999 01:14:20 -0700 From: Darryl Okahata Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > On Thursday, 17 June 1999 at 3:43:10 -0400, David E. Cross wrote: > > I have a drive that is rated at ~16 Meg/second, and indeed it delivers on t > he > > order of 15+ Meg/second. If I use Vinum to create a concatinated device > > of 2 such units performance drops to 2.5 Meg/sec. This seems like a > > drastic drop in performance. > > Indeed, if you're comparing apples with apples. Possible marginally-related data point: with the 3.1-RELEASE vinum, and with striped drives (yes, I know the original user is using concatenated devices), I saw pretty bad write performance with the default filesystem frag size. Increasing the frag size (via newfs), increased performance substantially. -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 1:43:40 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 33B7314FCE; Fri, 18 Jun 1999 01:43:31 -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 SAA08870; Fri, 18 Jun 1999 18:13:30 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id SAA03095; Fri, 18 Jun 1999 18:13:26 +0930 (CST) Date: Fri, 18 Jun 1999 18:13:25 +0930 From: Greg Lehey To: FreeBSD Hackers , FreeBSD Questions Subject: Beware of UnixWare 7 Message-ID: <19990618181324.A2863@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 Those of you who were at Usenix may have picked up a free copy of a UnixWare 7 CD-ROM from SCO. If so, be careful when installing it. I tried installing it on a machine with two other systems installed. It failed to install (looped trying to install drivers it didn't need). When I rebooted, I found that it had overwritten the Master Boot Record (which is silly, since it knew there were two other systems on the disk), and it also rewrote the partition table: it changed the numbers of the partitions. This is particularly difficult for FreeBSD, which has the partition number explicitly in the device name. In my case, FreeBSD was on partition 2, devices /dev/rwd0s2a and /dev/rwd0s2e. It was moved to partition 3, so the device names changed to devices /dev/rwd0s3a and /dev/rwd0s3e. Since I didn't have device nodes for these devices, I was unable to remount the root file system, and I had to use the fixit floppy to rewrite the partition table. Nothing got lost, but it was a real pain. 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 Fri Jun 18 1:50:20 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 65442150B0 for ; Fri, 18 Jun 1999 01:50:15 -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 SAA08894; Fri, 18 Jun 1999 18:20:16 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id SAA03144; Fri, 18 Jun 1999 18:20:09 +0930 (CST) Date: Fri, 18 Jun 1999 18:20:06 +0930 From: Greg Lehey To: Darryl Okahata Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vinum performance Message-ID: <19990618182006.C2863@freebie.lemis.com> References: <199906180814.BAA29087@mina.sr.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906180814.BAA29087@mina.sr.hp.com>; from Darryl Okahata on Fri, Jun 18, 1999 at 01:14:20AM -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 [Format recovered--see http://www.lemis.com/email/email-format.html] On Friday, 18 June 1999 at 1:14:20 -0700, Darryl Okahata wrote: > Greg Lehey wrote: > >> On Thursday, 17 June 1999 at 3:43:10 -0400, David E. Cross wrote: >>> I have a drive that is rated at ~16 Meg/second, and indeed it >>> delivers on the order of 15+ Meg/second. If I use Vinum to create >>> a concatinated device of 2 such units performance drops to 2.5 >>> Meg/sec. This seems like a drastic drop in performance. >> >> Indeed, if you're comparing apples with apples. > > Possible marginally-related data point: with the 3.1-RELEASE vinum, > and with striped drives (yes, I know the original user is using > concatenated devices), I saw pretty bad write performance with the > default filesystem frag size. Increasing the frag size (via newfs), > increased performance substantially. That shouldn't have anything to do with it. If you see anything unusual in Vinum performance, please tell me. It's easy to come to incorrect conclusions about the cause of performance problems, and disseminating them doesn't help. Follow the links at http://www.lemis.com/vinum.html for a discussion of Vinum performance. The biggest factor influencing Vinum performance on striped plexes is the stripe size, which should be at least 256 kB. 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 Jun 18 1:57:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 8B7C114DEC; Fri, 18 Jun 1999 01:57:16 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA16934; Fri, 18 Jun 1999 08:29:10 +0200 From: Luigi Rizzo Message-Id: <199906180629.IAA16934@labinfo.iet.unipi.it> Subject: Re: Beware of UnixWare 7 To: grog@lemis.com (Greg Lehey) Date: Fri, 18 Jun 1999 08:29:10 +0200 (MET DST) Cc: hackers@FreeBSD.ORG, questions@FreeBSD.ORG In-Reply-To: <19990618181324.A2863@freebie.lemis.com> from "Greg Lehey" at Jun 18, 99 06:13:06 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1498 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Those of you who were at Usenix may have picked up a free copy of a > UnixWare 7 CD-ROM from SCO. If so, be careful when installing it. I ... > When I rebooted, I found that it had overwritten the Master Boot > Record (which is silly, since it knew there were two other systems on > the disk), and it also rewrote the partition table: it changed the > numbers of the partitions. This is particularly difficult for > FreeBSD, which has the partition number explicitly in the device name. which is not much smarter... > /dev/rwd0s2e. It was moved to partition 3, so the device names > changed to devices /dev/rwd0s3a and /dev/rwd0s3e. Since I didn't have > device nodes for these devices, I was unable to remount the root file > system, and I had to use the fixit floppy to rewrite the partition > table. Nothing got lost, but it was a real pain. hit a similar problem the other day, i think i managed to fix it withouth the floppy by mounting again the root partition on /mnt and there acting appropriately. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) http://www.iet.unipi.it/~luigi/ngc99/ ==== First International Workshop on Networked Group Communication ==== -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 2: 8: 6 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 9F54914FF9 for ; Fri, 18 Jun 1999 02:07:53 -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 SAA08946; Fri, 18 Jun 1999 18:37:51 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id SAA03216; Fri, 18 Jun 1999 18:37:33 +0930 (CST) Date: Fri, 18 Jun 1999 18:37:32 +0930 From: Greg Lehey To: Luigi Rizzo Cc: hackers@FreeBSD.ORG Subject: Re: Beware of UnixWare 7 Message-ID: <19990618183731.D2863@freebie.lemis.com> References: <19990618181324.A2863@freebie.lemis.com> <199906180629.IAA16934@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906180629.IAA16934@labinfo.iet.unipi.it>; from Luigi Rizzo on Fri, Jun 18, 1999 at 08:29:10AM +0200 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, 18 June 1999 at 8:29:10 +0200, Luigi Rizzo wrote: >> Those of you who were at Usenix may have picked up a free copy of a >> UnixWare 7 CD-ROM from SCO. If so, be careful when installing it. I > ... >> When I rebooted, I found that it had overwritten the Master Boot >> Record (which is silly, since it knew there were two other systems on >> the disk), and it also rewrote the partition table: it changed the >> numbers of the partitions. This is particularly difficult for >> FreeBSD, which has the partition number explicitly in the device name. > > which is not much smarter... > >> /dev/rwd0s2e. It was moved to partition 3, so the device names >> changed to devices /dev/rwd0s3a and /dev/rwd0s3e. Since I didn't have >> device nodes for these devices, I was unable to remount the root file >> system, and I had to use the fixit floppy to rewrite the partition >> table. Nothing got lost, but it was a real pain. > > hit a similar problem the other day, i think i managed to fix it > withouth the floppy by mounting again the root partition on /mnt > and there acting appropriately. Nice one. 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 Jun 18 2:15:34 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 8BCA514DEC; Fri, 18 Jun 1999 02:15:29 -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 SAA19399; Fri, 18 Jun 1999 18:44:50 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199906180914.SAA19399@gizmo.internode.com.au> Subject: Re: Beware of UnixWare 7 To: grog@lemis.com (Greg Lehey) Date: Fri, 18 Jun 1999 18:44:50 +0930 (CST) Cc: hackers@FreeBSD.ORG, questions@FreeBSD.ORG In-Reply-To: <19990618181324.A2863@freebie.lemis.com> from "Greg Lehey" at Jun 18, 99 06:13:25 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 Greg Lehey wrote: > Those of you who were at Usenix may have picked up a free copy of a > UnixWare 7 CD-ROM from SCO. If so, be careful when installing it. SCO has been a real pain in the bum about partition tables for as long as I can remember. Don't even try installing it anywhere other than on your normal boot disk either. I've never had any luck getting SCO OpenServer onto a secondary disk of any kind. - 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 Fri Jun 18 2:31:28 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 B0A981500D for ; Fri, 18 Jun 1999 02:31:07 -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 TAA09034; Fri, 18 Jun 1999 19:01:07 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id TAA03333; Fri, 18 Jun 1999 19:00:50 +0930 (CST) Date: Fri, 18 Jun 1999 19:00:50 +0930 From: Greg Lehey To: Mark Newton Cc: hackers@FreeBSD.ORG Subject: Re: Beware of UnixWare 7 Message-ID: <19990618190050.E2863@freebie.lemis.com> References: <19990618181324.A2863@freebie.lemis.com> <199906180914.SAA19399@gizmo.internode.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906180914.SAA19399@gizmo.internode.com.au>; from Mark Newton on Fri, Jun 18, 1999 at 06:44:50PM +0930 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, 18 June 1999 at 18:44:50 +0930, Mark Newton wrote: > Greg Lehey wrote: > >> Those of you who were at Usenix may have picked up a free copy of a >> UnixWare 7 CD-ROM from SCO. If so, be careful when installing it. > > SCO has been a real pain in the bum about partition tables for as > long as I can remember. To be fair, this is UnixWare (ex Novell, ex Univel, ex USL), not OpenDeathtrap. I always thought it a little better, but I never tried to share disks with it before. > Don't even try installing it anywhere other than on your normal boot > disk either. I've never had any luck getting SCO OpenServer onto a > secondary disk of any kind. That wouldn't surprise me. 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 Jun 18 2:31: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 D9E7315196; Fri, 18 Jun 1999 02:31:42 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id LAA31388; Fri, 18 Jun 1999 11:29:53 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199906180929.LAA31388@freebsd.dk> Subject: Re: Beware of UnixWare 7 In-Reply-To: <19990618181324.A2863@freebie.lemis.com> from Greg Lehey at "Jun 18, 1999 6:13:25 pm" To: grog@lemis.com (Greg Lehey) Date: Fri, 18 Jun 1999 11:29:53 +0200 (CEST) Cc: hackers@FreeBSD.ORG, questions@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 Greg Lehey wrote: > FreeBSD, which has the partition number explicitly in the device name. > In my case, FreeBSD was on partition 2, devices /dev/rwd0s2a and > /dev/rwd0s2e. It was moved to partition 3, so the device names > changed to devices /dev/rwd0s3a and /dev/rwd0s3e. Since I didn't have > device nodes for these devices, I was unable to remount the root file > system, and I had to use the fixit floppy to rewrite the partition > table. Nothing got lost, but it was a real pain. Thats the reason why I always use /dev/rwd0a etc, ie without the slicenumbers in it, that way it will always use the FreeBSD slice no matter what number is has gotten. Of cause that only works if you only have one FreeBSD slice, but that is most normal I guess... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 2:34:37 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 C4CCC14C9C; Fri, 18 Jun 1999 02:34:20 -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 TAA09051; Fri, 18 Jun 1999 19:03:50 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id TAA03377; Fri, 18 Jun 1999 19:03:47 +0930 (CST) Date: Fri, 18 Jun 1999 19:03:47 +0930 From: Greg Lehey To: Soren Schmidt Cc: hackers@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Beware of UnixWare 7 Message-ID: <19990618190347.G2863@freebie.lemis.com> References: <19990618181324.A2863@freebie.lemis.com> <199906180929.LAA31388@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906180929.LAA31388@freebsd.dk>; from Soren Schmidt on Fri, Jun 18, 1999 at 11:29:53AM +0200 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, 18 June 1999 at 11:29:53 +0200, Soren Schmidt wrote: > It seems Greg Lehey wrote: >> FreeBSD, which has the partition number explicitly in the device name. >> In my case, FreeBSD was on partition 2, devices /dev/rwd0s2a and >> /dev/rwd0s2e. It was moved to partition 3, so the device names >> changed to devices /dev/rwd0s3a and /dev/rwd0s3e. Since I didn't have >> device nodes for these devices, I was unable to remount the root file >> system, and I had to use the fixit floppy to rewrite the partition >> table. Nothing got lost, but it was a real pain. > > Thats the reason why I always use /dev/rwd0a etc, ie without the > slicenumbers in it, that way it will always use the FreeBSD > slice no matter what number is has gotten. Of cause that only > works if you only have one FreeBSD slice, but that is most > normal I guess... Yup, I prefer the "compatibility slice" names too. They're not as fussy as the strict slice names, and they look less System V.4-ish. 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 Fri Jun 18 2:52:26 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 0A4FE14F23 for ; Fri, 18 Jun 1999 02:52:23 -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 LAA26473 for ; Fri, 18 Jun 1999 11:52:22 +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 LAA11974; Fri, 18 Jun 1999 11:52:13 +0200 (CEST) Message-ID: <376A174B.568C53F0@pvt.net> Date: Fri, 18 Jun 1999 11:54:19 +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: freebsd-hackers@FreeBSD.ORG Subject: Re: help with CD-Rom References: <3761293000010258@osmail.onesoft.com> <19990616142947.C90275@bantu.cl.msu.edu> Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG bush doctor wrote: > > Once morpheus_420@depechemode.com aka (morpheus_420@depechemode.com) said: > > Yesterday I was able to mount my CD-ROM just fine. Today after > > a lot of kernel hacking I am not. I am fairly new at this so > > this may be a really easy answer. > > I have an entry in the "fstab" file that references my cdrom > > /dev/wcd0c /cdrom ro, noauto 0 0 > > but when I goto "mount /cdrom" I get an error that says > > "/dev/wcd0c: Device not configured" > > > > > > Any ideas as to what I am doing or have done wrong here > No ideas as to what you're doing :-) > However, > Check your kernel config file and make sure you have the following > device wcd0 #IDE CD-ROM I see an "acd0" device line in my 3.2 GENERICS config file. Could someone please explain the diffrence between wcd0 and acd0 devices? What has changed? Thanks in advance. Milon -- papezik@pvt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 2:59:25 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 CF949150AD for ; Fri, 18 Jun 1999 02:59:18 -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 TAA19585; Fri, 18 Jun 1999 19:28:03 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199906180958.TAA19585@gizmo.internode.com.au> Subject: Re: Beware of UnixWare 7 To: grog@lemis.com (Greg Lehey) Date: Fri, 18 Jun 1999 19:28:03 +0930 (CST) Cc: newton@internode.com.au, hackers@FreeBSD.ORG In-Reply-To: <19990618190050.E2863@freebie.lemis.com> from "Greg Lehey" at Jun 18, 99 07:00:50 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 Greg Lehey wrote: > On Friday, 18 June 1999 at 18:44:50 +0930, Mark Newton wrote: > > SCO has been a real pain in the bum about partition tables for as > > long as I can remember. > > To be fair, this is UnixWare You mean "UnixSwear," don't you? :-) - 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 Fri Jun 18 3: 4:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 15D4E14F23 for ; Fri, 18 Jun 1999 03:04:21 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id GAA17708; Fri, 18 Jun 1999 06:03:19 -0400 (EDT) Date: Fri, 18 Jun 1999 06:03:19 -0400 (EDT) From: Daniel Eischen Message-Id: <199906181003.GAA17708@pcnet1.pcnet.com> To: br@smilla.rueskamp.com, freebsd-hackers@FreeBSD.ORG Subject: Re: pthread_cancel Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bodo Rueskamp wrote: > Is anyone working on pthread_cancel? I've got some stale patches for it which I'll bring up to date. But to implement the POSIX cancelable functions correctly will take some hacking of libc. I can do this also, but it needs further discussion as to how it _should_ be done. See the -hackers and -current mailing list archives, and pay particular attention to Derek Seaman's posts. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 3:38:52 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 41A9D14F19 for ; Fri, 18 Jun 1999 03:38:50 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id GAA70934; Fri, 18 Jun 1999 06:38:26 -0400 (EDT) Date: Fri, 18 Jun 1999 06:38:26 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@janus.syracuse.net To: Daniel Eischen Cc: br@smilla.rueskamp.com, freebsd-hackers@FreeBSD.ORG Subject: Re: pthread_cancel In-Reply-To: <199906181003.GAA17708@pcnet1.pcnet.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, 18 Jun 1999, Daniel Eischen wrote: > Bodo Rueskamp wrote: > > Is anyone working on pthread_cancel? > > I've got some stale patches for it which I'll bring up to > date. But to implement the POSIX cancelable functions > correctly will take some hacking of libc. I can do this > also, but it needs further discussion as to how it _should_ > be done. > > See the -hackers and -current mailing list archives, and > pay particular attention to Derek Seaman's posts. Do you mean Richard? > > Dan Eischen > eischen@vigrid.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 Fri Jun 18 3:44:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 4B94414F19 for ; Fri, 18 Jun 1999 03:44:37 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id GAA19226; Fri, 18 Jun 1999 06:43:40 -0400 (EDT) Date: Fri, 18 Jun 1999 06:43:40 -0400 (EDT) From: Daniel Eischen Message-Id: <199906181043.GAA19226@pcnet1.pcnet.com> To: eischen@vigrid.com, green@unixhelp.org Subject: Re: pthread_cancel Cc: br@smilla.rueskamp.com, freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Fundakowski Feldman wrote: > > See the -hackers and -current mailing list archives, and > > pay particular attention to Derek Seaman's posts. > > Do you mean Richard? Oops. My sincere apologies to Richard Seaman (whom I actually meant - is it who or whom?). Derek is another fellow who happens to have the same last name. Sorry again, Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 5:21:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.panix.com (mail2.panix.com [166.84.0.213]) by hub.freebsd.org (Postfix) with ESMTP id 6A7FB15310; Fri, 18 Jun 1999 05:21:29 -0700 (PDT) (envelope-from tomg@nrnet.org) Received: from mailhost.nrnet.org (root@mailhost.nrnet.org [166.84.192.39]) by mail2.panix.com (8.8.8/8.8.8/PanixM1.3) with ESMTP id IAA26528; Fri, 18 Jun 1999 08:21:26 -0400 (EDT) Received: from localhost (tomg@localhost) by mailhost.nrnet.org (8.8.7/8.8.4) with SMTP id HAA11151; Fri, 18 Jun 1999 07:17:14 -0400 Date: Fri, 18 Jun 1999 07:17:14 -0400 (EDT) From: Thomas Good To: Greg Lehey Cc: FreeBSD Hackers , FreeBSD Questions Subject: Re: Beware of UnixWare 7 In-Reply-To: <19990618181324.A2863@freebie.lemis.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, 18 Jun 1999, Greg Lehey wrote: > Those of you who were at Usenix may have picked up a free copy of a > UnixWare 7 CD-ROM from SCO. If so, be careful when installing it. I > tried installing it on a machine with two other systems installed. It > failed to install (looped trying to install drivers it didn't need). > When I rebooted, I found that it had overwritten the Master Boot > Record (which is silly, since it knew there were two other systems on Greg, Now that you've recovered I can wax rhetoical (briefly ;-). I have run UnixWare since day 1 - when Novell bought it from USL. It had bad kernel code in version 1.1 - panic on every shutdown when it couldn't flush dirty pages. SCO cleaned that up but everything that used to be free on UW1.1 is now activated by a licence key and $$$. It's approx $795 to turn on anything (even netscape)... I run 2.1.2 on a production box - at least for now. (Moving to Slackware soon on this box...) The lamest implementation of Unix I've ever seen. Many conf tasks remain non-trivial as compared to BSD or Linux due to inexpertise on SCO's end...as the red Sytem Admin Handbook once stated (Neveth, Snyder et al.) SCO Unix* is `perverse'. An example of clumsiness: the sendmail.cf file that comes stock with 2.1.2 is for OpenServer hence all paths are wrong. And, for whatever reason SCO didn't see fit to build makemap so making a mailertable is tougher than it should be...on and on... I got UW 7 in the mail (kind of like America Online). It makes a lovely ashtray. (And you can rest a pint there as well!) Cheers, Tom ------- North Richmond Community Mental Health Center ------- Thomas Good MIS Coordinator Vital Signs: tomg@ { admin | q8 } .nrnet.org Phone: 718-354-5528 Fax: 718-354-5056 /* Member: Computer Professionals For Social Responsibility */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 6:11:31 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 CAA6E15314 for ; Fri, 18 Jun 1999 06:11:28 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 18 Jun 99 14:11:27 +0100 (BST) To: freebsd-hackers@freebsd.org Subject: Inetd and wrapping. X-Request-Do: Date: Fri, 18 Jun 1999 14:11:26 +0100 From: David Malone Message-ID: <9906181411.aa23134@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon and myself have been looking at the wrapping support in inetd, and I'd be interested to hear what people think on the following issues. David. Making wrapping a run time option: It seems strange to make wrapping a compile time option, when it could be a command line option, or a per service option in inetd.conf? I'd suggest that we have two command line options, one which disables wrapping all together and one which disables it for internal services. Wrapping dgram services: If our inetd wrapping is to replace tcpd we need to be able to wrap the initial connection to udp based services. The man page should make it clear that it can only check the first connection to the service, and after that the service is on its own. An interesting question is, should we try to do this in a clever fashion, or should we stick with something simple. The simple implimentation looks like: fork(); if( rejected ) exit() else provide_serivce(); The clever implimentation would look like: fork; while( rejected && !timedout ) { get new packet }; if( timedout ) exit() else provide_service(); The clever one reduces forks, but as inetd isn't the place where high performance services are provided from the extra complexity may not be worth it. Making internal services cleverer if they have forked: If an internal udp service has forked it could provide its service using a similar loop to the one for clever UDP wrapping. This would reduce the amount of forking. Is it worth the extra complexity? Trying to wrap stream/wait services: Doing this would involve being able to find the address of the next connection on a listening socket without calling accept. AFAIK this isn't possible with the normal socket interface, and isn't supported by tcpd. We should probably just say this isn't possible in the man page? Wrapping of weirder types: According to the inetd man page we support sockets of type: ``stream'', ``dgram'', ``raw'', ``rdm'', or ``seqpacket''. I (personally) have never seen any inetd services using raw, rdm or seqpacket - is it worth providing wrapping for these socket types? Adding wrapper support to "wait" daemons: Daemons that use the "wait" class can only have their first successful connection wrapped by inetd, and then they are free to accept or reject subsequent connections themselves until they exit. Usually they have a timeout (identd, talkd), or only serve one connection (tftpd, rpc.rstatd). Should we go around and try to add wrapper support into these services? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 6:30: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 9913F15378 for ; Fri, 18 Jun 1999 06:30:08 -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 10uyia-000ASm-00; Fri, 18 Jun 1999 15:30:04 +0200 From: Sheldon Hearn To: freebsd-hackers@freebsd.org Cc: David Malone Subject: Re: Inetd and wrapping. In-reply-to: Your message of "Fri, 18 Jun 1999 14:11:26 +0100." <9906181411.aa23134@salmon.maths.tcd.ie> Date: Fri, 18 Jun 1999 15:30:03 +0200 Message-ID: <40223.929712603@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Jun 1999 14:11:26 +0100, David Malone wrote: > Sheldon and myself have been looking at the wrapping support in inetd, and > I'd be interested to hear what people think on the following issues. Is the general consensus that we absolutely must have wrapper support built into inetd? What we've got right now isn't doing a fantastic job, and trying to wedge in the job tcpd did before is getting progressively uglier. :-( 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 Jun 18 6:36:21 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 7D9E615378 for ; Fri, 18 Jun 1999 06:36:18 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from bell.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 18 Jun 99 14:36:18 +0100 (BST) Date: Fri, 18 Jun 1999 14:36:17 +0100 From: David Malone To: Sheldon Hearn Cc: freebsd-hackers@freebsd.org Subject: Re: Inetd and wrapping. Message-ID: <19990618143617.A43897@bell.maths.tcd.ie> References: <9906181411.aa23134@salmon.maths.tcd.ie> <40223.929712603@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <40223.929712603@axl.noc.iafrica.com>; from Sheldon Hearn on Fri, Jun 18, 1999 at 03:30:03PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 18, 1999 at 03:30:03PM +0200, Sheldon Hearn wrote: > Is the general consensus that we absolutely must have wrapper support > built into inetd? What we've got right now isn't doing a fantastic job, > and trying to wedge in the job tcpd did before is getting progressively > uglier. :-( I think we may almost be there, and we've unearther problems with inetd that were there anyway - but not as obvious without wrapping. While the process is painful I think the end result may be OK. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 9:26:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.sb2573.ru (ns.sb2573.ru [195.133.133.118]) by hub.freebsd.org (Postfix) with ESMTP id 526B214BD0 for ; Fri, 18 Jun 1999 09:26:29 -0700 (PDT) (envelope-from ksb@sb2573.ru) Message-ID: <001601beb9a7$9e0aaf90$fbc910ac@magc-winnt.cd.ld.sb2573.ru> From: "ksb" To: Subject: Buffer overflows question Date: Fri, 18 Jun 1999 20:28:34 +0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0013_01BEB9C9.237B22B0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0013_01BEB9C9.237B22B0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Hello. Would you, please, comment the kernel message below: sio0: 478 more tty-level buffer overflows (total 478) I use FreeBSD 2.2.8; there is a modem (without hardware flow control) on /dev/cua0; I have a leased line with 38400 bps full duplex; there is PPP (user mode) tunnel to my ISP. Can you answer what are these buffers (kernel or UART 16550A) and how can I fight with these buffer overflows. Thank you. -- Malinin A. G. ------=_NextPart_000_0013_01BEB9C9.237B22B0 Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable
Hello.
 
Would you,=20 please, comment the kernel message below:
 
    sio0:=20 478 more tty-level buffer overflows (total 478)
 
I use = FreeBSD 2.2.8;=20 there is a modem (without hardware flow control)
on = /dev/cua0; I have a=20 leased line with 38400 bps full duplex;
there is = PPP (user mode)=20 tunnel to my ISP.
 
Can you = answer what are=20 these buffers (kernel or UART 16550A) and
how can I = fight with=20 these buffer overflows.
 
Thank = you.
 
--
Malinin A.=20 G.
 
------=_NextPart_000_0013_01BEB9C9.237B22B0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 9:38:37 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 0342C152B0 for ; Fri, 18 Jun 1999 09:38:29 -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 MAA05337 for ; Fri, 18 Jun 1999 12:38:40 -0400 (EDT) Message-Id: <199906181638.MAA05337@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Fri, 18 Jun 1999 11:30:54 -0400 To: hackers@freebsd.org From: Dennis Subject: Dual boot with LINUX Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can linux be booted using the freebsd boot manager? Lilo always seems to want to install itself. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 9:50: 5 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 9E3C214D9B; Fri, 18 Jun 1999 09:50:00 -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 MAA05370; Fri, 18 Jun 1999 12:44:16 -0400 (EDT) Message-Id: <199906181644.MAA05370@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Fri, 18 Jun 1999 11:36:29 -0400 To: Thomas Good , Greg Lehey From: Dennis Subject: Re: Beware of UnixWare 7 Cc: FreeBSD Hackers , FreeBSD Questions In-Reply-To: References: <19990618181324.A2863@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Many conf tasks remain non-trivial as compared to BSD or Linux due >to inexpertise on SCO's end...as the red Sytem Admin Handbook once >stated (Neveth, Snyder et al.) SCO Unix* is `perverse'. I enjoy reading the section in that book on network hardware whenever I need a good laugh. People shouldnt attempt to write about things that they so clearly know nothing about. Dennis > >An example of clumsiness: the sendmail.cf file that comes stock with >2.1.2 is for OpenServer hence all paths are wrong. And, for whatever >reason SCO didn't see fit to build makemap so making a mailertable is >tougher than it should be...on and on... > >I got UW 7 in the mail (kind of like America Online). It makes a >lovely ashtray. (And you can rest a pint there as well!) > >Cheers, >Tom > >------- North Richmond Community Mental Health Center ------- > >Thomas Good MIS Coordinator >Vital Signs: tomg@ { admin | q8 } .nrnet.org > Phone: 718-354-5528 > Fax: 718-354-5056 > >/* Member: Computer Professionals For Social Responsibility */ > > > >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 Jun 18 10:38:41 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 993B714FD1 for ; Fri, 18 Jun 1999 10:38:38 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id NAA77609 for ; Fri, 18 Jun 1999 13:38:40 -0400 (EDT) Date: Fri, 18 Jun 1999 13:38:40 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@janus.syracuse.net To: hackers@FreeBSD.org Subject: dd(1) changes (review please) Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1793103162-929727520=:75966" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1793103162-929727520=:75966 Content-Type: TEXT/PLAIN; charset=US-ASCII Would someone (being more experienced than I) review these modifications to FreeBSD (HEAD)'s bin/dd? In my changes, I've tried to convert every random "int", "u_long", etc. to the proper types ("off_t", "u_int64_t", "{,s}size_t", and keeping the ints that SHOULD be ints), which I am pretty sure I've done properly. I've also removed bogus casts, added new ones, and generally cleaned up the code into a more maintainable lump. I suppose by learning the code and doing the cleanups/fixes, I've designated myself as the maintainer of dd(1), haven't I? *grin* Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ --0-1793103162-929727520=:75966 Content-Type: APPLICATION/octet-stream; name="dd.patch.gz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="dd.patch.gz" H4sIAKODajcAA81bfVPbSNL/23yKDncJNpLBkoEAXnKbI+SOuwRyQO5ts+WS pTFWYUuKJIewm3z36+6ZkUYv5iVVT9WTqiB71N3T09PT8+uecRBOp9BfQpb6 25Mw2g6CbS+9zrZ82J7FC7F9nQphtK71+/0mbedtGsLflhE4++C4h4ODQ2cI zsHBwZplWe2CKizDw+HeobMnWX7+Gfp7L+2XYPHfn39egyz38tCHL3EYdKbj eArj8Ydu1595KWz2eqM6QSbEzUMkN2FSJ+krkuV4HkfXnWuRjyfZb3UqS1GF Ub63M85XkUHRY5anSz8HHDb8vgYdSRJ5CzHioTqDoe0OwFJPGi5S3c7CuYBu N05ECkewaVnI/6UHz47g7OO7dz0W1QmnJQl2EywT/tbrwZGiW+t3Oh2Rpl+7 jg3ry8iboNg8Bm8+j30vF5Alni9gGqeQzwQpuVyIKIdP68+zT+vrNmxyvzjs H5OzzoxA/9YbMvUIyDQ8AH+W8gBs2DjaMEcB1d5vovg2AqL0ogCeZyiTx80i STp63RFsfBpsFJ08o+aaoCiGL958ScoLP5yGIuAB1OTli2SLpgslUuOITMoS u16CbV1jfjd7k0x4OIzuC+SyqS2ziZ7Gn4W/iXhKg8162+pLyduzoaVN8/pj +trrkTWNvlt6e7AbnpBOqU9FhaKfhw2uzVLOYxBM5951Bi/AS/qvojgTec3/ nmeHEM7n4tqbly7ixwsMJrhUYuwhRY9KhRfcAXKv8/jZAEZv1lMlmj5YkV4b g9b/2xEPAEm4mT6zPZnqu1y0e7s2xiuLnnt6zZINwmgroGiAnjuAb98gXuZl A5u1UH2ynE5x5dI0ZOB7URTnMBHwm0jjdYpGOPbtTfwDm3CBOttwm4a40GgC OMD5uPYyyL0bQbEoAy8rLJBtAVwSDQuXMvx4OQ+ogzlSYb+o7a2AWy/K0e1x JQcxhDlKorB1jRqh4fyZ8G8gjuZ3UkQqrpfIDVOMTehpkyXS5xsZJGk8wYBw BzSE2zjNZ9i+xTzb+Ne0yys4Pbsav3/974pxilb2l4cshDsJRhwKNF4EzwOc R809KnuLp1OcQKO/bdA6qJ5bKLRCVTXY2pLaVEPZsU0L+G7Ef5wc6TMHA9rU nP2B2tXUVoBikAPjOSmv3cdwHBpO3lPbjPJDawUlmWpcJ65oQ/ufUmdfqrO/ Wh3/HgX8p3fpDva4y4O9e7pM7sY+rmGUvBy39lsStHctA6Qi4yWHzrKgeCC6 A6kbK+PukjKus6uU+b1YxM+MUHY8/vNlj/2htHirPcz3T7HJjstqDN1HqvGQ Y3R+0B/cXfYHd+cefzCWzcr5qdA8quM99gp39x6vKBf0yn5Nknu6VdudH0df UDb1PxwM7APs/4AeVfhFe3oVcRlgACVlIum+QCIMEjbHbL07+yYy4L7q0MCf h1lexwbcWN+1ib2BDmRjCQ/4u4kP/CY+kF1W+4LtFXjgvl41R9ltK1yglyLN aBd+EDH4JWKAVfu7Ic/Y4auCeUJdhxxq6DjKoXj+aS/FPeyYhSDeiUB8TVKR sTxMKQi2TmOEs7dhdE04cJExwI1gGWXhdYS7JKUFW2vWj0iBvZ3+hPfXXOCu sbUGKKXj9OA1JHEW5uEXAQGC0AWOM1ouJoqk495DoTpCxSZ32MMEuovlPKcv u47bk/zDx/PflPzOwN1BAWzMoWM7ZE00qrPL5kSx5C4i8VIvl9xfca3MsxjH RAB64vk3t14aZDRPCc7SJJyH+R25EwPtO7SNFkMGQ/wQkHsp+4VREPosmdF5 xiPZrqVn9TxsrVj0yNQrggh+4SDS70g2Gjo6jAwYzFi0aBaa0BFHHXwj13mO 2Ink2vCC3towKKAG0xzBx3fnZ3/h3R+9d3sTztE9pmjcLQmByKGVP5e5hRRA AkkCqS15zxCMhdchobhNWp6GGp8bWlimFv/4+PqNBlfU9JMEoWYXFQhqri6k FynFZbK5kQAhQ3Yb5hhF2DIUB88RETJSLOoAhyCz+q04Da/XgmZNgdZus6Yg W+s1Bdn6pJpCC8vw0Nk5dA+MmgLDrz2Nvnj/wRUx7fakg4SUOUTsGnLblN8A PUc6RhhhEN3MR8UG3aW9xs+9SZmXq5R+h3EOPva5rwkmyTeyH7Rm4bf0P11G /kj3PrOpTxsW3te5iJSTYnNVp/J9XTfcew0VMeKxNg6pYTkIdKQ2BOXnYpqD WCT53RY3bBf5C2vUY4t0aDFjE20ljG5YPf0lZfPoHQjbX7xgPXB2nlHyHW2M oN8nDMaw5GFZ9wvhXadM56lJbskSeElhg1HZUvSk6ixDTNlctMNwj55siLpO CfRBS7MJWCcFvk5GxZuR6ljOAlK8Pz3rEhy2CxKjuNHiI5TUcteF0jrNpYaf 1PSSKbr+jKo/bJBeaRHLKixSkfNI/jIfVoLIZh32Hi6c5L/4s195BGKeif/3 6tL6AIqc9Jc2Z05bqadshskopq1+nAaAQWyGPLjTReJ2HkYCk2RMrLNMLLiY NRNFXkTL5eBAL5cify19zsLdZ0utXfIEsVjEX0RXuYrd5k2Ga6D5uhR+esiH kEezgVWSF+sKPQf+xI9fNmDjVzgEfODaIYDfN4VaDwtdJa00cFMs6ISC5so6 YgpZB9F5lLNTzaNkYF1GRtB7anDFTfAq9aJsLms4VPLwvUwYCJC3RpnGveRK jOvu01PHNy5HZmVsq6/0cjXDKzUooNdqhOV0QV+2mBFRhi0yrbKXMwKWQ40U wHLabdGyFLvM8PdExmrI04Q67MlVlPN0kUhHxr4WX0w41srJ7BR+caSnoD7D qvU7jdeyineyuKrYVYGVVqdKekoZr46MQopKSAw51ffUfRCMsUEm5+RY1RWn 0uSXHL0pPUUc0PCzsT/H7OHR3mZs4rWVjbg1+tplZCSjB5pvqWPIOvuFSjWq 3oBCjKVWmVp69bBXPFlAq3cgaZt/SOGrPUTvx6hVG7iT8GoluAuCJrSjtjqw o7YnwboGw/DQ3T3cdUpQ93LHdhyw5IO84vQcZ5/37hGDaZ6+bdorcBYJegkO CJdXr68QiY0k4mZIliEqy/glnxF1N/0pIyE+2OHI2hsRsZGGEgFHKAL56thI FZ5k73+gnIYdlNNAP07uTNpEYKoTXfNmyPS6gUuOOK0YxtKMNbakIz9KvKZ9 gnjgooougUtqY6BxQsPMlO5EySGzU6djXbhoYJByuVjV7BxDcW5v0/sxsq0n SQa58DubtPU1Red8nEV0a2W51nElbHY1DuiotY+drWc5GnJ9pFqnAbZdXr05 PRu/PX13cnbOgQwIPcltQ9NgUhV1lRgbzscXb87P3v1H55M6HiHpT3RaYD3E qAqPBReGh75TVFDKhLMMWhxfSzzsEB7e1WuH0dO/FEyicxI6IVh4dzDzvgjE TVTnn4sFeY5aUJz0B7HIFDOVxrNlklDgJCfjHVgdAxS7hBoeWsaqNErtVfTS bXLk9E0P/V8XNHT4Budv373+y6UNb07ektXfn785Mfa44izn7Pzi5PWbckur qdGqRNOEWoOqDXdlarW7U/iI5mKkb8CnMhkpPIPTAxmbj+iwBP8t+Dy1q0qc XUzl9cmJrVCIhA698nAUE3zF3C16qokpKsINZhq90e89/ZndWe3dNbqpnN/W 7VLP0aBAJhoeqLztJVfz5EPDu5swCjJa6coP1YlU7iX0oF1VfPUWyVxUs1uj 4Ng9Hp+/RSc6Hl+enPydP5ydX118PDuWelffy9K73AWmjPvpNEG6jI2WmE7H ec+ofG+WCMdA5k3OVSwqfeexnk5VqMopdDMO9nIulGUUjPIQ/9DZH669mUiN sEYndOE8AE8iqKGs7w/3m5cq1gAhWBiZ8ImrD5lCT5HUiNHKaGRcPtCHMZS7 YUYURuPpcj5HB5BfcHtBXEUAW5/GSCy3z5GHn24Zef4r0pjHpc79pmGa5bxN 3WGeRXYIYjKB3Aj4MJp3JcW+zIQB+82gYx6jXP4HZ1iv+cYLXVGovENX+PO7 8+O/fzsefzzjT6ri3VGplnRlW2Zmav2oSMQJdBvtwKS0OhxSkI7KCRR5ZUDX iWRNKlf85ImyOsNw93iRuHv6FKkQuC1PjwGXX5xuGUaJakE4qsZfmU0r/4ti ZpfhXd+VsCEIKYf+cH55+m9U+vMyTGnXnXm5ZqXJJEBNs7YQWeZdCzo5rdSd IzjdPkdRWTL37lTNWR5FDXcP1IkMeyR6ny9GjRoayRfBqET9NqDnR7doM1sB HF1IK7+ZxTSkDivOfmtmChRgKuW04cEeHRcNDw5sZ6CDPltQo6tnamL4Bb9h 1ZXPdDQs6/dlIUWSzBmTFYFB0dhA0Wd8/PGip3cmycLh1FUlXGaVM+TT2ThD PAntKDCqaxQqxzc2Mqvaez2eaR0UHXI3lLEepcx6KQFgvapadWNtNxhffDBj Ji4Ip6A3US7P0A4dWQzA2iFkU0xRscerVX16efzXCwpcz6QHFTMmvzKiLBsq KaG8iEHHUOgink93EQLxJfQLS7fZmesr9dF+X6Ha1esPJ2qqK8X6Wv+03xVd 13oE498PyQClnrxkVmTv/SOIehg7qin8BKf6pj15pCTuvtRx1pL1zVpSx9lT U8c6wy7yGHcMh1xJsOhRnGv98VQqPLO/gLO1T8T72wN3G7ergXvoDg+HDu61 3iKEk68J/FEeTMGa9YdATMNIwJIPlWQyxadSFh08wmk1CUVbLWQuygEZ8rtE oAB9Nv17EX46m4HOVtSe6AUBnTZKSFMSJTqnWaYp3YBS1BRZDQ59CNaR9ZxW lsldTnW2JbbIyzuUFcr6vKSfe5lKDuqkhfAiezMu8MijLJXgyXLkI/pHP5ad 2/d3znSrusXgreanw4u+0xl8HTiy89oChi4tdloWvEp6zF4yfzj9cMLcrkyn Q1w6XdoUFbCjNLKnK5OYFLguWLt79FD3CnhP6cjbn1JXTiglQKWENlDNFBxR p8xPwyTHUGoaWAJGRVgrAfC9VjYIx/BH0UIpejomt8zMVJrwnOLB/A/RVYbB 0VQnafAQ7Au9B9iyBlscBJDdehPNZ1LnDWplcl2WsDpy7ekh2I8YAnpN0qC+ T3lkyBoMLWoj3YMKw3c4PWdk0Vj+xagVnq5PhyxJtlhJQe6WqVjJgkGptQ8V rFZwrOhlNZM8K+k0rIF2laXVKjnZ06RGG/fnIrrOZ20eoq9iU0wwLc7feafL RVRxEmXYupPUrcQFGB5si4O0EGtj1uU27KJoV0huI2d72Q8ZkBwU7WM/ynRI rC222mTQCeIlhjWC3DjnUBRMEUNw6olMQaAcmqqq5NIrYMBsJQwQXzEGR00o oNvrcEC3PwkStDIND133EFFiAQt2XzJ4lA8K25INFyvownLRRuNFW5QNlEyD rhx3qainXqjbJ7p6a7Rz1sKHapZq08mJpq23yxO4igBdt63JLeqjpZBacylG pjtcH623eq4YD91//vKrzR854ZNfwsmifENfinfC9eSbhjR6U5DN3SU9lu6c KNv8Rs/aSt9ZhJnfPH+QrXW/ka1P8hrF8h4xAbPsgEs4snq1ZI/PIOVD5huZ 8DPKIUR/byRPND9SfSJKUpyBaXfYgyzmXJlqrEEcbRCuQRxEuCUPwhgpJDhU taOCE8FNcS0PP/MlQM6rns+XFv4vwkEYfYrqbei9n6J1W1Xw1p9/xtefayy1 Ns0C8qJiUeSxjRoPfy6Cn/7C1Z9RMQKZxV1evTm5uFBlcqpQ0WjyFCMUj6a4 wIsyKFypY9eHbMCj553YDHXPMzXYx/B/XskPKplSKtmFcpQFOz34E6xzUF2H Q/UpW5f501MH/r0cvHkN53GjLzeEp467wWmMWO47pUr/B2NuW/Vy1a1c8/JG Yxw11335pr72yzdPWv8r2HDfcA6HO0YMcLioSY8d43wa2WuVVXUVg0tPqV3U r4qi1ESfXOt6VDrScF4fapt1L3Vfgqt0dLmlSGlsmZ/QL7LKFN/Gyb5j8M8/ aojohxplffwZlx112ZOTpW8y6/mmahI95ZJl0UgVKlXNqLyFvQnFSUJb2agh 4HGc9x5tdVKRL9PI+JmOI39w4Oi7PDQbdNWguIrHiHuRxwnk4zipVhEbZq+V w40CvTQ92VkamAZGNSmqr8xkqUv9JEe1enJywkzq6cpzJHffOOPgQ7fyl2lc 8OdJk7/Cqp5sPGsrIDXmSpXQ9OWi+84tlO0vT67aZ+3eE4wW5vsP1JozN+Rf ZzjFaQVlVHGytaC/dOXu6u3lxchslrWAI0MheYlXHo/Gfj4vdH5/dXp+fHX+ wYYXxN2rnAM+QPqDw9mRwyl/XCHLakW53zQn3cUoqms9eKV+ONbx4ygPo6Uw xhVVVI8epZ26K9cWdctYJyPv/wBguBYOHTwAAA== --0-1793103162-929727520=:75966-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 10:51:15 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 181BA150C9; Fri, 18 Jun 1999 10:51:06 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id NAA77871; Fri, 18 Jun 1999 13:50:09 -0400 (EDT) Date: Fri, 18 Jun 1999 13:50:09 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@janus.syracuse.net To: Ruslan Ermilov Cc: hackers@FreeBSD.org, cvs-committers@FreeBSD.org Subject: Re: Introduction In-Reply-To: <19990618200140.A28527@relay.ucb.crimea.ua> 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, 18 Jun 1999, Ruslan Ermilov wrote: > On Fri, Jun 18, 1999 at 12:24:16PM -0400, Brian Fundakowski Feldman wrote: > > Hello, I'm Brian Feldman, a new committer to the FreeBSD source tree! Some of > > the things I'll be working on are: > > - maintaining and improving IPFW (cleanups too, of course) > Let's join our efforts in this area! > IPFW code is very ugly... Which is basically due to it being hacked on for years without a cleanup. Now's the time (between major versions) to do this, I think. How's this: let's organize a small group to bounce ideas off eachother, first of all (I'm forwarding this to hackers to perhaps elicit a response of more people.) We should get ideas on what people think is wrong with the current implementation, what new features should be added, and where we should rearchitect. IPFW is reasonably small enough to redesign/reimplement in a few weeks (with multiple intelligent people working on it, of course =), so I think this is a worthwhile project. So Ruslan, why don't we organize a small group that will be doing this (this being the rewrite, and BTW I really want the external interface to IPFW to be backward-compatible)? We should then look through any relevant PRs and make sure to have all the info we need before undertaking this. > > I hope this is the kind of thing Jordan wanted! > > > John Birrell (IIRC). Everyone would always appreciate some introduction :) > > > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ > > green@freebsd.org _ __ ___ | _ ) __| \ > > FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | > > http://www.freebsd.org _ |___/___/___/ > > > > > > -- > Ruslan Ermilov Sysadmin and DBA of the > ru@ucb.crimea.ua United Commercial Bank, > ru@FreeBSD.org FreeBSD committer, > +380.652.247.647 Simferopol, Ukraine > > http://www.FreeBSD.org The Power To Serve > http://www.oracle.com Enabling The Information Age > > 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 Fri Jun 18 10:57: 1 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 3EE9514C9C for ; Fri, 18 Jun 1999 10:56:50 -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 10v2sk-000DMS-00 for hackers@freebsd.org; Fri, 18 Jun 1999 19:56:50 +0200 From: Sheldon Hearn To: hackers@freebsd.org Subject: Obtaining client host IP before accept() Date: Fri, 18 Jun 1999 19:56:49 +0200 Message-ID: <51363.929728609@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I found a thread in the freebsd-hackers archive from 1997 that covered my question, but the answers didn't nail it down to a "yes" or "no" satisfactorily. We could save ourselves a lot of angst in the work we're doing on inetd if we could determine the client IP address of a TCP socket before calling accept(). Alternatively, we'd love a way to accept() without acknowledging a connection, so that the connection request could be left for a child that expected to do its own socket() and bind() calls. My take on the previous thread is that this is impossible in userland. I'd appreciate it someone who knows the answer for a fact could look at the code below and answer the following question: Will the IP address of the client host ever enter buf[] if the accept() is _not_ uncommented? I don't need portability, since this is for use within the FreeBSD inetd exclusively. Thanks, Sheldon. -------- #include #include #include #include #include #include #include #include #include #include /* * Use an arbitrary port that you know isn't in use on the system. I * don't run ircd, so this is safe for me. */ #define LISTEN_PORT (6667) #define BUFSIZE (1500) int main(void) { int ctl; int peek; int i = 1; int port = LISTEN_PORT; char buf[BUFSIZE]; struct sockaddr_in server_addr; struct sockaddr_in client_addr; struct in_addr bind_address; struct msghdr msg; if ((ctl = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)) < 0) err(errno, "error creating socket"); printf("socket number %d created\n", ctl); if (setsockopt(ctl, SOL_SOCKET, SO_REUSEADDR, (char *)&i, sizeof(i))) err(errno, "error setsockopt(SO_REUSEADDR): "); if (setsockopt(ctl, SOL_SOCKET, SO_REUSEPORT, (char *)&i, sizeof(i))) err(errno, "error setsockopt(SO_REUSEPORT): "); printf("setsockopt(SO_REUSEADDR|SO_REUSEPORT) successful\n"); bind_address.s_addr = htonl(INADDR_ANY); server_addr.sin_family = AF_INET; server_addr.sin_addr = bind_address; server_addr.sin_port = htons(port); if (bind(ctl, (struct sockaddr *)&server_addr, sizeof(server_addr))) err(errno, "error (%d) bind(%lu:%d)", errno, server_addr.sin_addr.s_addr, port); printf("bound to port %d\n", port); if (listen(ctl, 0)) err(errno, "error listening: "); printf("listening...\n"); /* i = sizeof(client_addr); if (peek = accept(ctl, (struct sockaddr *)&client_addr, &i) < 0) err(errno, "accept() failed: "); printf("connection accepted from %s\n", inet_ntoa(client_addr.sin_addr)); */ msg.msg_name = (void *)&server_addr; msg.msg_namelen = sizeof(server_addr); msg.msg_iovlen = 0; msg.msg_control = (caddr_t)&buf; msg.msg_controllen = 1; while (recvmsg(ctl, &msg, MSG_PEEK) < 0) { warn("recvmsg failed: "); printf("msg_flags = %i\n", msg.msg_flags); sleep(2); } printf("recvmsg successful, wtf?\n"); close(ctl); /* close(peek); */ return(0); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 11: 5:49 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 A879914C9C for ; Fri, 18 Jun 1999 11:05:46 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id OAA78122; Fri, 18 Jun 1999 14:04:48 -0400 (EDT) Date: Fri, 18 Jun 1999 14:04:48 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@janus.syracuse.net To: Ruslan Ermilov Cc: hackers@FreeBSD.org Subject: new-IPFW (was Re: Introduction) 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 also want new-IPFW to be modular. This would mean that, for instance, DUMMYNET would be just one plug-in to IPFW. More would be created in an extensible manner, rather than the current hack to do DUMMYNET. 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 Fri Jun 18 11: 6:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from atlrel1.hp.com (atlrel1.hp.com [156.153.255.210]) by hub.freebsd.org (Postfix) with ESMTP id A598115313 for ; Fri, 18 Jun 1999 11:05:29 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from srmail.sr.hp.com (srmail.sr.hp.com [15.4.45.14]) by atlrel1.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id OAA27375; Fri, 18 Jun 1999 14:03:38 -0400 (EDT) Received: from mina.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA045749041; Fri, 18 Jun 1999 11:04:01 -0700 Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id LAA12830; Fri, 18 Jun 1999 11:04:00 -0700 (PDT) Message-Id: <199906181804.LAA12830@mina.sr.hp.com> To: Greg Lehey Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vinum performance Reply-To: Darryl Okahata In-Reply-To: Your message of "Fri, 18 Jun 1999 18:20:06 +0930." <19990618182006.C2863@freebie.lemis.com> Mime-Version: 1.0 (generated by tm-edit 1.1.1.1) Content-Type: text/plain; charset=US-ASCII Date: Fri, 18 Jun 1999 11:04:00 -0700 From: Darryl Okahata Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > On Friday, 18 June 1999 at 1:14:20 -0700, Darryl Okahata wrote: > > > Possible marginally-related data point: with the 3.1-RELEASE vinum, > > and with striped drives (yes, I know the original user is using > > concatenated devices), I saw pretty bad write performance with the > > default filesystem frag size. Increasing the frag size (via newfs), > > increased performance substantially. > > That shouldn't have anything to do with it. If you see anything > unusual in Vinum performance, please tell me. It shouldn't, perhaps, have anything to do with it, but it did. I'm simply reporting empirical results, where I kept the stripe size constant and varied the filesystem frag size. I was able to get around a 2X improvement in write speed by increasing the frag size. Why, I don't know. I do know that I saw what I saw. ;-) This was, however, using 128K stripe sizes. Perhaps there's an interaction between small stripes and frag sizes? Also, I'm still stuck using the 3.1-RELEASE vinum. I want to upgrade to something newer, but I can't do so until I manage to backup my system (and I've got a lot of files to backup). ;-( > It's easy to come to > incorrect conclusions about the cause of performance problems, and > disseminating them doesn't help. Follow the links at It's not so much of a conclusion as a data point. I'm simply reporting what I saw. Note that I am NOT saying that varying the frag size is the most significant way of improving performance. I'm sure that you're correct in your recommendations. However, I was able to significantly affect write performace simply by changing the frag size. As I've said, I don't know why, but it happened. I don't know how reproducible this is; maybe it's related to rotational latencies, the particular drive type, drive firmware, CPU speed, etc.. I don't know -- but I do know that it happened, and I'm simply reporting a data point. This is just a single data point, and we all know how dangerous it is to extrapolate from a single data point. ;-) However, if others report their findings, we may or may not find a trend. -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 11: 7:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id A8C7914C9C for ; Fri, 18 Jun 1999 11:07:39 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id LAA16203 for ; Fri, 18 Jun 1999 11:07:39 -0700 (PDT) (envelope-from Studded@gorean.org) Date: Fri, 18 Jun 1999 11:07:39 -0700 (PDT) From: Studded X-Sender: doug@dt054n86.san.rr.com To: freebsd-hackers@freebsd.org Subject: Re: Heavily loaded nfs/amd gets stuck 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 No action on this in -current for a few days, so let's try hackers. In response to some suggestions I tried raising the number of nfsiod's to 20 (the max) and increasing the sysctl cache value to 10, still no joy. I'm using amd to automount directories on sun (sol 2.6) server to my freebsd-current client machine. Details below, any help appreciated. Doug On Thu, 17 Jun 1999, Studded wrote: > > Also, should I be considering a move to -current for this box? Is > > -current stable enough right now to run a fairly heavily loaded web > > server? If the NFS in -current is going to be doing better than what's in > > -stable it will be worth a little headache to change, since our structure > > depends on it heavily. > > Well I went ahead and tried -current, and got better results, but > the same crash. With the following map: > > /defaults type:=nfs;opts:=rw,nosuid,vers=3,intr,proto=udp,noconn > * rhost:=IP${key};rfs:=/Space/${key} > > It went MUCH farther through the script (mounted about 60 out of 80 > directories) but it crashed just the same. Kernel stack trace looked like > this: > > stuff > Xresume1() > --- interrupt > bcmp() > mountnfs() > nfs_mount() > mount() > syscall() > Xint0x80syscall() Ok, another interesting development. What the script I'm running does is go through each user account on our sun servers, reads a file, then uses certain values from that file to print out conf files on the local freebsd server that's acting as an NFS client (and crashing). So it's mounting a directory, reading 250 files, mounting the next directory, reading the next 250 files, and so on for a total of 80 directories. I changed the script so that after each reading the 250 files for each directory it did a 'sleep 10' before it started again. This allowed the script to run through to completion. So, I'm still open to new things to try here. Does anyone have any suggestions? I've been looking at nfsiod, all I had started was the default 4 because I thought they would spawn more if they needed more, but apparently they don't. Would more of those help? Would turning them off altogether help? I *really* need help with this since my boss is (justifiably I think) loathe to put this box into service without a little more concrete evidence that NFS can hold up. Would it be better to send this to -hackers? Maybe file a PR? I don't mean to sound like a pest, and yes I know that we're all volunteers, etc. But after wheedling for 4 months to try freebsd I'm kind of feeling the pinch here. :-/ Thanks for any help you can provide, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 11:24: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id 75A7714D1E; Fri, 18 Jun 1999 11:22:31 -0700 (PDT) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id VAA65927; Fri, 18 Jun 1999 21:20:56 +0300 (EEST) (envelope-from ru) Date: Fri, 18 Jun 1999 21:20:55 +0300 From: Ruslan Ermilov To: Brian Fundakowski Feldman Cc: jmb@FreeBSD.org, committers@FreeBSD.org, hackers@FreeBSD.org Subject: Re: Introduction Message-ID: <19990618212055.A61311@relay.ucb.crimea.ua> Mail-Followup-To: Brian Fundakowski Feldman , jmb@FreeBSD.org, committers@FreeBSD.org, hackers@FreeBSD.org References: <19990618200140.A28527@relay.ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Brian Fundakowski Feldman on Fri, Jun 18, 1999 at 01:50:09PM -0400 X-Operating-System: FreeBSD 3.2-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 18, 1999 at 01:50:09PM -0400, Brian Fundakowski Feldman wrote: > On Fri, 18 Jun 1999, Ruslan Ermilov wrote: > > > On Fri, Jun 18, 1999 at 12:24:16PM -0400, Brian Fundakowski Feldman wrote: > > > Hello, I'm Brian Feldman, a new committer to the FreeBSD source tree! Some of > > > the things I'll be working on are: > > > - maintaining and improving IPFW (cleanups too, of course) > > Let's join our efforts in this area! > > IPFW code is very ugly... > > Which is basically due to it being hacked on for years without a cleanup. > Now's the time (between major versions) to do this, I think. How's this: > let's organize a small group to bounce ideas off eachother, first of all > (I'm forwarding this to hackers to perhaps elicit a response of more people.) > We should get ideas on what people think is wrong with the current > implementation, what new features should be added, and where we should > rearchitect. > Agreed. So, Jonathan, could you please create for us? > IPFW is reasonably small enough to redesign/reimplement in a few weeks > (with multiple intelligent people working on it, of course =), so I think > this is a worthwhile project. So Ruslan, why don't we organize a small group > that will be doing this (this being the rewrite, and BTW I really want the > external interface to IPFW to be backward-compatible)? We should then look > through any relevant PRs and make sure to have all the info we need before > undertaking this. > I've closed a number of ipfw's PRs last week, most of them were for ipfw(8). Cheers, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 11:42: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from distortion.dk (distortion.dk [195.249.147.156]) by hub.freebsd.org (Postfix) with ESMTP id 5CB1215073; Fri, 18 Jun 1999 11:41:55 -0700 (PDT) (envelope-from npp@distortion.dk) Received: from localhost (npp@localhost) by distortion.dk (8.9.1/8.9.1) with ESMTP id WAA08617; Fri, 18 Jun 1999 22:15:14 +0200 (CEST) (envelope-from npp@distortion.dk) Date: Fri, 18 Jun 1999 22:15:14 +0200 (CEST) From: Nicolai Petri To: Brian Fundakowski Feldman Cc: Ruslan Ermilov , hackers@FreeBSD.ORG, cvs-committers@FreeBSD.ORG Subject: Re: Introduction 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, 18 Jun 1999, Brian Fundakowski Feldman wrote: > On Fri, 18 Jun 1999, Ruslan Ermilov wrote: > > > Let's join our efforts in this area! > > IPFW code is very ugly... > > Which is basically due to it being hacked on for years without a cleanup. > Now's the time (between major versions) to do this, I think. How's this: > let's organize a small group to bounce ideas off eachother, first of all > (I'm forwarding this to hackers to perhaps elicit a response of more people.) > We should get ideas on what people think is wrong with the current > implementation, what new features should be added, and where we should > rearchitect. What about support for protocol verification ?? (Example : Blocking of malformed ftp commands.) Wich layer would it be logically to implement this in ? Is a userland proxy the only way ? ------------ Nicolai Petri WM-data BFC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 11:57:55 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 2661C151B9 for ; Fri, 18 Jun 1999 11:57:47 -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 LAA27344; Fri, 18 Jun 1999 11:57:42 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id LAA06106; Fri, 18 Jun 1999 11:57:42 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA11471; Fri, 18 Jun 99 11:57:41 PDT Message-Id: <376A96A4.FF22512E@softweyr.com> Date: Fri, 18 Jun 1999 12:57: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: Papezik Milon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: help with CD-Rom References: <3761293000010258@osmail.onesoft.com> <19990616142947.C90275@bantu.cl.msu.edu> <376A174B.568C53F0@pvt.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Papezik Milon wrote: > > I see an "acd0" device line in my 3.2 GENERICS config file. > > Could someone please explain the diffrence > between wcd0 and acd0 devices? > > What has changed? The name. ATAPI CD-ROMs are now called "acd". MAKEDEV will typically make wcd->acd symlinks in the /dev directory for hysterical raisins. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr 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 Jun 18 11:57:55 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 10A28151B8; Fri, 18 Jun 1999 11:57:49 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id OAA78968; Fri, 18 Jun 1999 14:56:50 -0400 (EDT) Date: Fri, 18 Jun 1999 14:56:50 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@janus.syracuse.net To: Nicolai Petri Cc: Ruslan Ermilov , hackers@FreeBSD.org, cvs-committers@FreeBSD.org Subject: Re: Introduction 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, 18 Jun 1999, Nicolai Petri wrote: > On Fri, 18 Jun 1999, Brian Fundakowski Feldman wrote: > > On Fri, 18 Jun 1999, Ruslan Ermilov wrote: > > > > > Let's join our efforts in this area! > > > IPFW code is very ugly... > > > > implementation, what new features should be added, and where we should > > rearchitect. > > What about support for protocol verification ?? (Example : Blocking of > malformed ftp commands.) I don't like the idea of implementing protocols MEANT for userland in the kernel. Doing this leads to code duplication (a LOT of it) and unnecessary complexity. This would just lead to people wanting an entire ftpd in the kernel (which wouldn't be a good idea, even after having built the parsers/state machine (or worse) into the kernel). This is entirely impractical, and without a hybrid user/kernel model impossible. > > Wich layer would it be logically to implement this in ? This should be done in the user land. > > Is a userland proxy the only way ? > > ------------ > Nicolai Petri > WM-data BFC > > > > 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 Fri Jun 18 12:12:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (Postfix) with ESMTP id 65FB515386 for ; Fri, 18 Jun 1999 12:11:51 -0700 (PDT) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id VAA23835; Fri, 18 Jun 1999 21:11:23 +0200 (CEST) Message-ID: <19990618211123.B22107@foobar.franken.de> Date: Fri, 18 Jun 1999 21:11:23 +0200 From: Harold Gutch To: Wes Peters , Papezik Milon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: help with CD-Rom References: <3761293000010258@osmail.onesoft.com> <19990616142947.C90275@bantu.cl.msu.edu> <376A174B.568C53F0@pvt.net> <376A96A4.FF22512E@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <376A96A4.FF22512E@softweyr.com>; from Wes Peters on Fri, Jun 18, 1999 at 12:57:40PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 18, 1999 at 12:57:40PM -0600, Wes Peters wrote: > > Could someone please explain the diffrence > > between wcd0 and acd0 devices? > > > > What has changed? > > The name. ATAPI CD-ROMs are now called "acd". MAKEDEV will typically > make wcd->acd symlinks in the /dev directory for hysterical raisins. ^ I understand - it will create symlinks to stop users getting hysterical as their CD-ROM isn't working anymore ;). bye, Harold -- Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 12:20:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id 8E2CA15174; Fri, 18 Jun 1999 12:19:10 -0700 (PDT) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id WAA77105; Fri, 18 Jun 1999 22:15:59 +0300 (EEST) (envelope-from ru) Date: Fri, 18 Jun 1999 22:15:58 +0300 From: Ruslan Ermilov To: ugen@xonix.com Cc: green@unixhelp.org, committers@FreeBSD.org, hackers@FreeBSD.org Subject: Re: Introduction Message-ID: <19990618221558.A71643@relay.ucb.crimea.ua> Mail-Followup-To: ugen@xonix.com, green@unixhelp.org, committers@FreeBSD.org, hackers@FreeBSD.org References: <37693FCF.608FA855@xonix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <37693FCF.608FA855@xonix.com>; from Ugen Antsilevitch on Thu, Jun 17, 1999 at 02:34:55PM -0400 X-Operating-System: FreeBSD 3.2-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jun 17, 1999 at 02:34:55PM -0400, Ugen Antsilevitch wrote: > The part that obviously interests me is IPFW - if you guys are > interested to put some effort in "real" i.e. stateful firewall > to be developed i'd love to offer any help i can. > Great! How we should proceed -- that's the question. My plan: * Clean the existing code (both userland and kernel) (10-20% done) * Re-design the ipfw's API * Port the existing functionality to the new API * Proceed with new features -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 12:46:29 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 0B14114D84; Fri, 18 Jun 1999 12:46:21 -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 MAA27989; Fri, 18 Jun 1999 12:45:44 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id MAA07634; Fri, 18 Jun 1999 12:45:45 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA13732; Fri, 18 Jun 99 12:45:43 PDT Message-Id: <376AA1E6.F529ED99@softweyr.com> Date: Fri, 18 Jun 1999 13:45:42 -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: Greg Lehey Cc: FreeBSD current users , FreeBSD Hackers Subject: Re: Remote serial gdb--status? References: <19990618114450.Q9893@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > I've been away from work for several weeks, and I now find that I can > no longer start remote serial gdb. I am using sio0 on the debugged > machine side, and sio1 on the debugging machine side. Here are the > relevant dmesg outputs: > > panic (debugged machine): > > sio0: system console > sio0: gdb debugging port > ... > sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0 > sio0: type 16550A > > freebie (debugging machine): > > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > sio1: interrupting at irq 3 > > I can communicate fine using cu, and a breakout box shows all modem > signals asserte (DCD, DTR, DSR, RTS, CTS). When I go into remote > debug on panic, RxD flashes, and when freebie tries to attach to > panic, TxD flashes, so I'm obviously addressing the correct ports. > I've checked the bit rate and configuration of the ports before going > into debug, and they look right (9600 bps, cs8, -istrip, -parenb). I > don't know what else to look for. Any ideas? I think you need flags 0x50 (instead of 0x90) on panic. From sio(4): Meaning of flags: ... 0x00010 device is potential system console 0x00020 device is forced to become system console 0x00040 device is reserved for low-level IO (e. g. for remote kernel debugging) ... -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr 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 Jun 18 13: 8: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ceia.nordier.com (m1-50-dbn.dial-up.net [196.34.155.50]) by hub.freebsd.org (Postfix) with ESMTP id CB95014F72 for ; Fri, 18 Jun 1999 13:07:56 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id WAA12447; Fri, 18 Jun 1999 22:07:18 +0200 (SAST) From: Robert Nordier Message-Id: <199906182007.WAA12447@ceia.nordier.com> Subject: Re: Dual boot with LINUX In-Reply-To: <199906181638.MAA05337@etinc.com> from Dennis at "Jun 18, 1999 11:30:54 am" To: dennis@etinc.com (Dennis) Date: Fri, 18 Jun 1999 22:07:15 +0200 (SAST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > Can linux be booted using the freebsd boot manager? Lilo always seems to > want to install itself. Provided you install Linux in a primary fdisk partition (slice 1-4), it should work OK. The RedHat default is to install to an extended fdisk partition, and we don't support booting from those. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 13:11:32 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 DB60014F8A for ; Fri, 18 Jun 1999 13:11:30 -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 QAA52485; Fri, 18 Jun 1999 16:11:02 -0400 (EDT) Message-Id: <199906182011.QAA52485@cs.rpi.edu> To: Greg Lehey Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: vinum performance In-Reply-To: Message from Greg Lehey of "Thu, 17 Jun 1999 17:47:47 +0930." <19990617174746.N9893@freebie.lemis.com> Date: Fri, 18 Jun 1999 16:11:11 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have a drive that is rated at ~16 Meg/second, and indeed it delivers on the > > order of 15+ Meg/second. If I use Vinum to create a concatinated device > > of 2 such units performance drops to 2.5 Meg/sec. This seems like a > > drastic drop in performance. > > Indeed, if you're comparing apples with apples. > > > Any ideas what I am doin incorrectly? > > No. You haven't really given any details. > > Most of the performance testing I have done has been with striped > plexes (which offer the potential for better performance), and I've > found that in massively concurrent situations the performance is > roughly what you would expect (almost n * normal disk performance, > where n is the number of disks in the stripe set. I'd expect > performance of a concatenated plex to be pretty close to that of the > raw disk. How are you measuring performance? I'd recommend rawio > (ftp://ftp.lemis.com/pub/rawio.tar.gz). Ok, I am terribly sorry I didn't provide more information. I was very tired (it has been a long week; after the NFS work the main NFS server that has been having all of the problems decided that its main OS partion was going to have a hardware failure...) Anyway, here is some more information... bash-2.03$ df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 99183 21526 69723 24% / /dev/da0s1e 2032623 1062270 807744 57% /usr /dev/da0s1f 198399 3466 179062 2% /var /dev/vinum/concat 29077993 252757 26498997 1% /mnt bash-2.03$ cd /var/tmp bash-2.03$ df -k . Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1f 198399 3466 179062 2% /var bash-2.03$ dd bs=64k if=/dev/zero of=foo count=2048 2048+0 records in 2048+0 records out 134217728 bytes transferred in 10.218804 secs (13134387 bytes/sec) bash-2.03$ cd /mnt bash-2.03$ df -k . Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/vinum/concat 29077993 252757 26498997 1% /mnt bash-2.03$ dd bs=64k if=/dev/zero of=foo count=2048 2048+0 records in 2048+0 records out 134217728 bytes transferred in 59.653922 secs (2249940 bytes/sec) bash-2.03$ vinum info Can't open history file /var/tmp/vinum_history: Permission denied (13) Can't open /dev/vinum/Control: Permission denied bash-2.03$ su - hostname# vinum info Flags: 0x80204 Total of 21 blocks malloced, total memory: 9552 Maximum allocs: 1264, malloc table at 0xc3583ad4 hostname# vinum printconfig # Vinum configuration of hostname, saved at Fri Jun 18 16:08:56 1999 drive drive1 device /dev/da0s1h drive drive2 device /dev/da1s1h volume concat plex name concat.p0 org concat vol concat sd name concat.p0.s0 drive drive1 plex concat.p0 len 27597000b driveoffset 265b plexoffset 0b sd name concat.p0.s1 drive drive2 plex concat.p0 len 32405704b driveoffset 265b plexoffset 27597000b If you need anything else it can probably be provided. Oh, this is 3.2-STABLE from last week. -- 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 Jun 18 14:19:28 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 9196A1584E for ; Fri, 18 Jun 1999 14:19:26 -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 OAA91229 for ; Fri, 18 Jun 1999 14:19:04 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 18 Jun 1999 14:19:04 -0700 (PDT) From: Doug White To: hackers@freebsd.org Subject: 3.1 panic: vm_page_unwire: invalid wire count: 0 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello .. I'm getting the following panic on a P90 running 3.1-RELEASE. This system is one of our routers and crashes every week or so. I can't find any reference if this was fixed or not. If someone's been playing in this area recently I can schedule an upgrade to 3.2 or -STABLE if it would help. The panic appears to be a problem inside of procfs, although I'm not sure it's just an innocent victim to a previous corruption. It doesn't help that the kernel can't keep time on this box; see PR 12022. I can make the core files and debugged kernel available if desired. Some time before this (in this case ~4hrs) this message is logged: /kernel: vm_page_free: freeing wired page Here is ye olde stack trace: #0 boot (howto=256) at ../../kern/kern_shutdown.c:285 285 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:285 #1 0xf012abf8 in at_shutdown (function=0xf0209c25 , arg=0x0, queue=-193525184) at ../../kern/kern_shutdown.c:446 #2 0xf01cf3f3 in vm_page_unwire (m=0xf043f594, activate=1) at ../../vm/vm_page.c:1346 #3 0xf0157851 in procfs_rwmem (curp=0xf4861ba0, p=0xf476c3c0, uio=0xf4868f40) at ../../miscfs/procfs/procfs_mem.c:256 #4 0xf0157928 in procfs_domem (curp=0xf4861ba0, p=0xf476c3c0, pfs=0xf0c1c900, uio=0xf4868f40) at ../../miscfs/procfs/procfs_mem.c:305 #5 0xf01581cf in procfs_rw (ap=0xf4868efc) at ../../miscfs/procfs/procfs_subr.c:279 #6 0xf0153de1 in vn_read (fp=0xf0bebf80, uio=0xf4868f40, cred=0xf0c15900) at vnode_if.h:303 #7 0xf0135469 in read (p=0xf4861ba0, uap=0xf4868f94) at ../../kern/sys_generic.c:121 #8 0xf01ed07b in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = -272642048, tf_esi = 4096, tf_ebp = -272644136, tf_isp = -192507932, tf_ebx = 0, tf_edx = 0, tf_ecx = -272642048, tf_eax = 3, tf_trapno = 8, tf_err = 2, tf_eip = 134548752, tf_cs = 31, tf_eflags = 659, tf_esp = -272645204, tf_ss = 39}) at ../../i386/i386/trap.c:1100 #9 0xf01e145c in Xint0x80_syscall () #10 0x804b002 in ?? () #11 0x804b2c0 in ?? () #12 0x804b30a in ?? () #13 0x8049dd7 in ?? () #14 0x8049eb9 in ?? () #15 0x8049b03 in ?? () #16 0x80480e9 in ?? () And here be the screwy part: (kgdb) frame 2 #2 0xf01cf3f3 in vm_page_unwire (m=0xf043f594, activate=1) at ../../vm/vm_page.c:1346 1346 panic("vm_page_unwire: invalid wire count: %d\n", m->wire_count); (kgdb) print *m $6 = {pageq = {tqe_next = 0x705f6d76, tqe_prev = 0x5f656761}, hashq = { tqe_next = 0x69776e75, tqe_prev = 0x203a6572}, listq = { tqe_next = 0x61766e69, tqe_prev = 0x2064696c}, object = 0x65726977, pindex = 1970234144, phys_addr = 540701806, queue = 25637, flags = 10, pc = 28022, wire_count = 28767, hold_count = 26465, act_count = 101 'e', busy = 95 '_', valid = 99 'c', dirty = 97 'a'} (kgdb) print m $7 = (struct vm_page *) 0xf0209c25 (kgdb) frame 3 #3 0xf0157851 in procfs_rwmem (curp=0xf4861ba0, p=0xf476c3c0, uio=0xf4868f40) at ../../miscfs/procfs/procfs_mem.c:256 256 vm_page_unwire(m, 1); (kgdb) print m $8 = (struct vm_page *) 0x100 Thoughts? Hints? Buttons to push? Thanks! 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 Fri Jun 18 14:37:26 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 083EE14D49 for ; Fri, 18 Jun 1999 14:37:20 -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 RAA06444; Fri, 18 Jun 1999 17:37:28 -0400 (EDT) Message-Id: <199906182137.RAA06444@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Fri, 18 Jun 1999 16:29:39 -0400 To: Robert Nordier From: Dennis Subject: Re: Dual boot with LINUX Cc: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:07 PM 6/18/99 +0200, you wrote: >Dennis wrote: > >> Can linux be booted using the freebsd boot manager? Lilo always seems to >> want to install itself. > >Provided you install Linux in a primary fdisk partition (slice 1-4), >it should work OK. The RedHat default is to install to an extended >fdisk partition, and we don't support booting from those. Well the problem with *should* is that lilo installs itself whenever you run it, and you have to run it to install a new kernel. So I was hoping to find someone that has actually done it. Dennis > >-- >Robert Nordier > > >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 Jun 18 14:47: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ceia.nordier.com (c2-34-dbn.dial-up.net [196.34.155.162]) by hub.freebsd.org (Postfix) with ESMTP id 7B79A14D66 for ; Fri, 18 Jun 1999 14:46:53 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id XAA13090; Fri, 18 Jun 1999 23:46:16 +0200 (SAST) From: Robert Nordier Message-Id: <199906182146.XAA13090@ceia.nordier.com> Subject: Re: Dual boot with LINUX In-Reply-To: <199906182137.RAA06444@etinc.com> from Dennis at "Jun 18, 1999 04:29:39 pm" To: dennis@etinc.com (Dennis) Date: Fri, 18 Jun 1999 23:46:14 +0200 (SAST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > At 10:07 PM 6/18/99 +0200, you wrote: > >Dennis wrote: > > > >> Can linux be booted using the freebsd boot manager? Lilo always seems to > >> want to install itself. > > > >Provided you install Linux in a primary fdisk partition (slice 1-4), > >it should work OK. The RedHat default is to install to an extended > >fdisk partition, and we don't support booting from those. > > Well the problem with *should* is that lilo installs itself whenever you > run it, and you have to run it to install a new kernel. So I was hoping to > find someone that has actually done it. Should just implies YMMV: I have booted Linux with the freebsd boot manager. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 14:50:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rossel.saarnet.de (rossel.saarnet.de [145.253.240.29]) by hub.freebsd.org (Postfix) with ESMTP id 4761214D52 for ; Fri, 18 Jun 1999 14:50:30 -0700 (PDT) (envelope-from doehrm@aubi.de) Received: from igate.aubi.de (root@igate.aubi.de [145.253.242.249]) by rossel.saarnet.de (8.8.8/8.8.8) with ESMTP id XAA28562 for ; Fri, 18 Jun 1999 23:15:25 +0200 (MET DST) Received: from cisco.aubi.de (soraya.aubi.de [170.56.121.252]) by igate.aubi.de (8.9.1a/8.9.1) with ESMTP id XAA02174 for ; Fri, 18 Jun 1999 23:02:14 +0200 Received: from exchange.aubi.de (EXCHANGE.aubi.de [170.56.121.91]) by cisco.aubi.de (8.9.1/8.9.1) with ESMTP id XAA11392 for ; Fri, 18 Jun 1999 23:29:24 +0200 (CEST) Received: by EXCHANGE with Internet Mail Service (5.5.2232.9) id ; Fri, 18 Jun 1999 23:08:31 +0200 Message-ID: From: =?iso-8859-1?Q?Markus_D=F6hr?= To: "'freebsd-hackers@freebsd.org'" Subject: M$ using Linux? Date: Fri, 18 Jun 1999 23:08:30 +0200 Importance: high X-Priority: 1 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What do you think about that: [root@beta ~]# nmap -vv -p119 -P0 -sT -O betanews.microsoft.com Sequence numbers: E6E23C4C E7368B4F E6E0CC8D E79B4DEC E7A43C4E E76D208A Remote operating system guess: Linux 2.1.122 - 2.1.132; 2.2.0-pre1 - = 2.2.2 OS Fingerprint: TSeq(Class=3DRI%gcd=3D1%SI=3D3A46A8) T1(Resp=3DY%DF=3DY%W=3D7F53%ACK=3DS++%Flags=3DAS%Ops=3DMENNTNW) T2(Resp=3DN) T3(Resp=3DY%DF=3DY%W=3D7F53%ACK=3DS++%Flags=3DAS%Ops=3DMENNTNW) T4(Resp=3DY%DF=3DN%W=3D0%ACK=3DO%Flags=3DR%Ops=3D) T5(Resp=3DN) T6(Resp=3DN) T7(Resp=3DN) PU(Resp=3DN) Nmap run completed -- 1 IP address (1 host up) scanned in 20 seconds and that? [root@beta ~]# telnet betanews.microsoft.com 119 Trying 207.46.180.35... Connected to betanews.msn.com. Escape character is '^]'. 200 cpmsblns02.microsoft.com InterNetNews NNRP server INN 2.2 = 21-Jan-1999 ready=20 (posting ok). INN running on NT? And the most interesting: Quoting Alan Cox from the linux-kernel developer list: someone asking: > I guess that they run windows-2000 on the beta site, and then I guess = is > that they > have stolen IP-code from Linux. Im right, yes ?! Unlikely. Judging by the window 2000 beta traces they run a BSD stack = derivative close to freebsd - and the BSD license permits such use -- Markus Doehr =20 IT Admin =20 AUBI Baubeschl=E4ge GmbH =20 Tel.: +49 6503 917 152 =20 Fax : +49 6503 917 190 =20 e-Mail: doehrm@aubi.de MD1139-RIPE =20 ************************* =20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 14:52:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id 9CA2D14D52 for ; Fri, 18 Jun 1999 14:52:29 -0700 (PDT) (envelope-from reichert@numachi.com) Received: (qmail 15491 invoked by uid 1001); 18 Jun 1999 21:52:27 -0000 Date: Fri, 18 Jun 1999 17:52:27 -0400 From: Brian Reichert To: hackers@freebsd.org Subject: Re: Dual boot with LINUX Message-ID: <19990618175227.L12143@numachi.com> References: <199906182137.RAA06444@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199906182137.RAA06444@etinc.com>; from Dennis on Fri, Jun 18, 1999 at 04:29:39PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 18, 1999 at 04:29:39PM -0400, Dennis wrote: > At 10:07 PM 6/18/99 +0200, you wrote: > >Dennis wrote: > > > >> Can linux be booted using the freebsd boot manager? Lilo always seems to > >> want to install itself. > > > >Provided you install Linux in a primary fdisk partition (slice 1-4), > >it should work OK. The RedHat default is to install to an extended > >fdisk partition, and we don't support booting from those. > > Well the problem with *should* is that lilo installs itself whenever you > run it, and you have to run it to install a new kernel. So I was hoping to > find someone that has actually done it. Just to say it: I have done it. I used BootEasy to dual-boot RH5.2 and FBSD-3.2-R. RH gets grabby, though: you have to take great pains to a) install it's root partition in a primary partition, and b) not grab the rest of the disk as a 'logical' (ha!) partition, then leave a mess of it marked as 'unused'. I installed FreeBSD first, then RedHat. With RedHat, use fdisk (rather than DiskDruid) to massage the partition table. DiskDruid _might_ work, but it thwarted me once, and I was getting impatient. I recall that I also had to use the 'Partition' utility from FBSD /stand/sysinstall to manually mark the Linux root partition as active (all of the other tools on hand would only let me set one partition as active, I wanted them all to be marked as such). This may not been neccessary, but the BootEasy manager assuredly could see the Linux partition thereafter. When you install LILO, have it do so on the boot block of the partition, not the MBR. Upon installation, LILO noticed that there was another partition, and offered to set up a label for it. I did; and now, when I bring up the Linux half, I can re-jump to the FreeBSD half. -- Brian 'you Bastard' Reichert reichert@numachi.com 37 Crystal Ave. #303 Current daytime number: (603)-434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 14:58:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from chain.freebsd.os.org.za (chain.freebsd.os.org.za [196.7.74.174]) by hub.freebsd.org (Postfix) with ESMTP id 992C214D52 for ; Fri, 18 Jun 1999 14:58:31 -0700 (PDT) (envelope-from khetan@chain.freebsd.os.org.za) X-Disclaimer: Contents of this e-mail are the writer's opinion X-Disclaimer2: and may not be quoted, re-produced or forwarded X-Disclaimer3: (in part or whole) without the author's permission. Received: from localhost (khetan@localhost) by chain.freebsd.os.org.za (8.9.3/8.9.3) with ESMTP id XAA82765; Fri, 18 Jun 1999 23:58:12 +0200 (SAST) (envelope-from khetan@chain.freebsd.os.org.za) Date: Fri, 18 Jun 1999 23:58:12 +0200 (SAST) From: Khetan Gajjar Reply-To: Khetan Gajjar To: David Malone Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Inetd and wrapping. In-Reply-To: <19990618143617.A43897@bell.maths.tcd.ie> Message-ID: X-Mobile: +27 82 9907663 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Around Today, "David Malone" wrote : DM> I think we may almost be there, and we've unearther problems with inetd DM> that were there anyway - but not as obvious without wrapping. While the DM> process is painful I think the end result may be OK. As a user, I'd say that it would certainly be nice to have TCPWrapper support in the inetd, but there's no reason why it has to explicitly be made part of inetd. The support (after the patches Sheldon brought in) now is pretty good; is there any reason why the existing functionality should be extended ? A RedHat installation I used yonks ago had TCP/Wrappers installed as is on installation, and had no integration with the inetd; it was basically inetd and the TCP/Wrappers port installed. We're already better than that right now. --- Khetan Gajjar (!kg1779) * khetan@os.org.za http://khetan.os.org.za/ * Talk/Finger khetan@khetan.os.org.za FreeBSD enthusiast * http://www2.za.freebsd.org/ Reference : <19990618143617.A43897@bell.maths.tcd.ie> Date : Jun 18, 1999, 2:36pm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 15: 0:47 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 839AD14F17 for ; Fri, 18 Jun 1999 15:00:43 -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 SAA06553; Fri, 18 Jun 1999 18:00:49 -0400 (EDT) Message-Id: <199906182200.SAA06553@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Fri, 18 Jun 1999 16:53:09 -0400 To: Markus =?iso-8859-1?Q?D=F6hr?= , "'freebsd-hackers@freebsd.org'" From: Dennis Subject: Re: M$ using Linux? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I heard that Windows-2000 IS linux :-) Dennis At 11:08 PM 6/18/99 +0200, Markus D=F6hr wrote: >What do you think about that: > >[root@beta ~]# nmap -vv -p119 -P0 -sT -O betanews.microsoft.com > > >Sequence numbers: E6E23C4C E7368B4F E6E0CC8D E79B4DEC E7A43C4E E76D208A >Remote operating system guess: Linux 2.1.122 - 2.1.132; 2.2.0-pre1 - 2.2.2 >OS Fingerprint: >TSeq(Class=3DRI%gcd=3D1%SI=3D3A46A8) >T1(Resp=3DY%DF=3DY%W=3D7F53%ACK=3DS++%Flags=3DAS%Ops=3DMENNTNW) >T2(Resp=3DN) >T3(Resp=3DY%DF=3DY%W=3D7F53%ACK=3DS++%Flags=3DAS%Ops=3DMENNTNW) >T4(Resp=3DY%DF=3DN%W=3D0%ACK=3DO%Flags=3DR%Ops=3D) >T5(Resp=3DN) >T6(Resp=3DN) >T7(Resp=3DN) >PU(Resp=3DN) >Nmap run completed -- 1 IP address (1 host up) scanned in 20 seconds > > >and that? > >[root@beta ~]# telnet betanews.microsoft.com 119 >Trying 207.46.180.35... >Connected to betanews.msn.com. >Escape character is '^]'. >200 cpmsblns02.microsoft.com InterNetNews NNRP server INN 2.2 21-Jan-1999 ready=20 >(posting ok). > >INN running on NT? > >And the most interesting: >Quoting Alan Cox from the linux-kernel developer list: > >someone asking: > >> I guess that they run windows-2000 on the beta site, and then I guess is >> that they >> have stolen IP-code from Linux. Im right, yes ?! > > >Unlikely. Judging by the window 2000 beta traces they run a BSD stack derivative >close to freebsd - and the BSD license permits such use > > > >-- >Markus Doehr =20 >IT Admin =20 >AUBI Baubeschl=E4ge GmbH =20 >Tel.: +49 6503 917 152 =20 >Fax : +49 6503 917 190 =20 >e-Mail: doehrm@aubi.de >MD1139-RIPE =20 >************************* =20 > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 16:25: 2 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 4A9C414E39; Fri, 18 Jun 1999 16:24:53 -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 IAA13988; Sat, 19 Jun 1999 08:54:45 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id IAA09530; Sat, 19 Jun 1999 08:54:44 +0930 (CST) Date: Sat, 19 Jun 1999 08:54:44 +0930 From: Greg Lehey To: Thomas Good Cc: FreeBSD Hackers , FreeBSD Questions Subject: Re: Beware of UnixWare 7 Message-ID: <19990619085444.O2863@freebie.lemis.com> References: <19990618181324.A2863@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Thomas Good on Fri, Jun 18, 1999 at 07:17:14AM -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 Friday, 18 June 1999 at 7:17:14 -0400, Thomas Good wrote: > On Fri, 18 Jun 1999, Greg Lehey wrote: > >> Those of you who were at Usenix may have picked up a free copy of a >> UnixWare 7 CD-ROM from SCO. If so, be careful when installing it. I >> tried installing it on a machine with two other systems installed. It >> failed to install (looped trying to install drivers it didn't need). >> When I rebooted, I found that it had overwritten the Master Boot >> Record (which is silly, since it knew there were two other systems on > > Now that you've recovered I can wax rhetoical (briefly ;-). > I have run UnixWare since day 1 - when Novell bought it from USL. > It had bad kernel code in version 1.1 - panic on every shutdown > when it couldn't flush dirty pages. I used it right from the beginning. The problems I recall were disappearing files and failing NFS config; the latter was crucial for the work I was doing, and the only way I found to fix it was to reinstall NFS. > SCO cleaned that up but everything that used to be free on UW1.1 is > now activated by a licence key and $$$. It's approx $795 to turn on > anything (even netscape)... I thought the licenses were free. I got the main license for free, anyway. > I run 2.1.2 on a production box - at least for now. (Moving > to Slackware soon on this box...) The lamest implementation of > Unix I've ever seen. It looks like you haven't used OpenServer. I think UnixWare is better. > Many conf tasks remain non-trivial as compared to BSD or Linux due > to inexpertise on SCO's end...as the red Sytem Admin Handbook once > stated (Neveth, Snyder et al.) SCO Unix* is `perverse'. This is Open[Server,Deathtrap], not UnixWare. A completely different system. > An example of clumsiness: the sendmail.cf file that comes stock with > 2.1.2 is for OpenServer hence all paths are wrong. And, for > whatever reason SCO didn't see fit to build makemap so making a > mailertable is tougher than it should be...on and on... Right, they have a different mailer which they prefer. But it does look clumsy, agreed. I've tried twice more to install UnixWare. It makes all the right noises, but on reboot it just hangs. I'm giving up now. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 16:39:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.panix.com (mail2.panix.com [166.84.0.213]) by hub.freebsd.org (Postfix) with ESMTP id 92C49150F0; Fri, 18 Jun 1999 16:39:33 -0700 (PDT) (envelope-from tomg@nrnet.org) Received: from mailhost.nrnet.org (tomg@mailhost.nrnet.org [166.84.192.39]) by mail2.panix.com (8.8.8/8.8.8/PanixM1.3) with ESMTP id TAA09989; Fri, 18 Jun 1999 19:39:30 -0400 (EDT) Received: from localhost (tomg@localhost) by mailhost.nrnet.org (8.8.7/8.8.4) with SMTP id SAA02235; Fri, 18 Jun 1999 18:37:48 -0400 Date: Fri, 18 Jun 1999 18:37:47 -0400 (EDT) From: Thomas Good To: Dennis Cc: Greg Lehey , FreeBSD Hackers , FreeBSD Questions Subject: Re: Beware of UnixWare 7 In-Reply-To: <199906181644.MAA05370@etinc.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, 18 Jun 1999, Dennis wrote: > > >Many conf tasks remain non-trivial as compared to BSD or Linux due > >to inexpertise on SCO's end...as the red Sytem Admin Handbook once > >stated (Neveth, Snyder et al.) SCO Unix* is `perverse'. > > I enjoy reading the section in that book on network hardware whenever I > need a good laugh. People shouldnt attempt to write about things that they > so clearly know nothing about. > > Dennis Argumentum ad hominem? Or simply ad absurdum? You won't find many SCO fans amongst those who've used more than one implementation of unix...and Novell getting out of the Unix business (and taking a beating for doing it) speaks volumes. ------- North Richmond Community Mental Health Center ------- Thomas Good MIS Coordinator Vital Signs: tomg@ { admin | q8 } .nrnet.org Phone: 718-354-5528 Fax: 718-354-5056 /* Member: Computer Professionals For Social Responsibility */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 17:11:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bytor.rush.net (bytor.rush.net [209.45.245.145]) by hub.freebsd.org (Postfix) with ESMTP id C290A14D3E for ; Fri, 18 Jun 1999 17:11:09 -0700 (PDT) (envelope-from lynch@bsdunix.net) Received: from localhost (lynch@localhost) by bytor.rush.net (8.9.3/8.9.3) with ESMTP id UAA19398 for ; Fri, 18 Jun 1999 20:11:08 -0400 (EDT) Date: Fri, 18 Jun 1999 20:11:08 -0400 (EDT) From: Pat Lynch X-Sender: lynch@bytor.rush.net To: hackers@freebsd.org Subject: SMP and Celerons... 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 Heya, sorry I tried this one on -stable and -questions and noone seems to know, and they actually go so far as to ask me how I got two celerons in a motherboard... so I ask here. I have two PPGA(Socket 370) Celeron 333A's that are on MSI6905 Dual Socket 1 adaptors... a Tyan Thunder 2 motherboard (onboard scsi, sound, etc.) I boot an SMP kernel, it gets right past autoboot... then panics the message was that it "could not find local apic"... its kinda strange because essentially with these adaptors, the celerons should be 1) SMP capable, and 2) the same as a PII, except no L2 cache I know others that ran FreeBSD SMP with celerons... anyone know if theres some kind of patch I need or modification I have to make to get either -CURRENT or -STABLE working on this machine? Right now it is running a UP kernel instead of the SMP one and runs fine. -Pat ___________________________________________________________________________ Pat Lynch lynch@rush.net lynch@bsdunix.net Systems Administrator Rush Networking ___________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 17:39:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.panix.com (mail2.panix.com [166.84.0.213]) by hub.freebsd.org (Postfix) with ESMTP id B668A151B7; Fri, 18 Jun 1999 17:39:12 -0700 (PDT) (envelope-from tomg@nrnet.org) Received: from mailhost.nrnet.org (root@mailhost.nrnet.org [166.84.192.39]) by mail2.panix.com (8.8.8/8.8.8/PanixM1.3) with ESMTP id UAA16116; Fri, 18 Jun 1999 20:39:07 -0400 (EDT) Received: from localhost (tomg@localhost) by mailhost.nrnet.org (8.8.7/8.8.4) with SMTP id TAA02510; Fri, 18 Jun 1999 19:36:06 -0400 Date: Fri, 18 Jun 1999 19:36:06 -0400 (EDT) From: Thomas Good Reply-To: Thomas Good To: Greg Lehey Cc: FreeBSD Hackers , FreeBSD Questions Subject: Re: Beware of UnixWare 7 In-Reply-To: <19990619085444.O2863@freebie.lemis.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, 19 Jun 1999, Greg Lehey wrote: > > I have run UnixWare since day 1 - when Novell bought it from USL. > > I used it right from the beginning. The problems I recall were > disappearing files and failing NFS config; the latter was crucial for > the work I was doing, and the only way I found to fix it was to > reinstall NFS. I found that with Sendmail too. They forgot about makemap, as I said. They also didn't include any m4 macros. And so on. And trying to conf UUCP over TCP is also quite a bit of fun. Installing Taylor helps there. I have a long list of things that I can do on other implementations (even Solaris) that take three times as long on UW... > > SCO cleaned that up but everything that used to be free on UW1.1 is > > now activated by a licence key and $$$. It's approx $795 to turn on > > anything (even netscape)... > > I thought the licenses were free. I got the main license for free, > anyway. Well, I can't comment on UW 7 and its licencing scheme but on 2.1.2 Netscape Fast Track expires and then demands a cash infusion. Similarly, I got DOS Merge for about 30 days before he expired. Morningstar PPP demanded a financial jumpstart before I could even fire it up. > > I run 2.1.2 on a production box - at least for now. (Moving > > to Slackware soon on this box...) The lamest implementation of > > Unix I've ever seen. > > It looks like you haven't used OpenServer. I think UnixWare is > better. Actually, I have...in one respect it is better than UW. It is one system as opposed to the soup that is UnixWare. USL, Novell and now SCO. UW is the quintessential white elephant and it shows. Maybe UW 7 is better but I stopped caring awhile back. BSD is our choice for mail servers and Slackware is my option for my PostgreSQL servers...it is very obvious to me (using Slackware since 2.3) that Patrick is ultra scrupulous about testing everything before he issues a new release. I also install BSD and *expect* that everything will work. Because it always has... > > Many conf tasks remain non-trivial as compared to BSD or Linux due > > to inexpertise on SCO's end...as the red Sytem Admin Handbook once > > stated (Neveth, Snyder et al.) SCO Unix* is `perverse'. > > This is Open[Server,Deathtrap], not UnixWare. A completely different > system. True - but SCO has a very heavy hand...as mentioned above I *almost* prefer OpenServer. I'm rather pleased that my shop will move our last database from PROGRESS on UW to PostgreSQL on Slackware 01 July 99. That will end our relationship with SCO and PROGRESS. > I've tried twice more to install UnixWare. It makes all the right > noises, but on reboot it just hangs. I'm giving up now. So you won't be wanting a subscription to SCO World for father's day, eh? Cheers, Tom ------- North Richmond Community Mental Health Center ------- Thomas Good MIS Coordinator Vital Signs: tomg@ { admin | q8 } .nrnet.org Phone: 718-354-5528 Fax: 718-354-5056 /* Member: Computer Professionals For Social Responsibility */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 18: 0:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id 03E0515129 for ; Fri, 18 Jun 1999 18:00:43 -0700 (PDT) (envelope-from jim@thehousleys.net) Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.218.96.75]) by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id VAA02877; Fri, 18 Jun 1999 21:00:41 -0400 (EDT) Received: from thehousleys.net (housley@localhost [127.0.0.1]) by thehousleys.net (8.9.3/8.9.3) with ESMTP id VAA23381; Fri, 18 Jun 1999 21:00:41 -0400 (EDT) (envelope-from jim@thehousleys.net) Message-ID: <376AEBB9.AC178064@thehousleys.net> Date: Fri, 18 Jun 1999 21:00:41 -0400 From: "James E. Housley" X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: lyncy@bsdunix.net, hackers@freebsd.org Subject: Re: SMP and Celerons... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pat Lynch wrote: > > Heya, sorry I tried this one on -stable and -questions and noone seems to > know, and they actually go so far as to ask me how I got two celerons in a > motherboard... Couple of things. freebsd-smp is probably the best list. > > I have two PPGA(Socket 370) Celeron 333A's that are on MSI6905 Dual Socket > 1 adaptors... > > a Tyan Thunder 2 motherboard (onboard scsi, sound, etc.) > > I boot an SMP kernel, it gets right past autoboot... then panics > > the message was that it "could not find local apic"... > > its kinda strange because essentially with these adaptors, the celerons > should be 1) SMP capable, and 2) the same as a PII, except no L2 cache > I have two PPGA Celereon 300A's over clocked to 450 on MSI6905 rev 1.1 boards on a ASUS P2B-D MB. The standard kernel works great for me. Is jumper J3 closed? to support Dual? I also added the following lines to my kernel. # Mandatory: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional, these are the defaults plus 1: options NCPU=2 # number of CPUs options NBUS=2 # number of busses options NAPIC=1 # number of IO APICs options NINTR=24 # number of INTs I know you said you added the top two. I added the bottom just because I don't like trusting defaults. mptable verified that they are right, but I know for SURE what is being used. Jim -- James E. Housley PGP: 1024/03983B4D System Supply, Inc. 2C 3F 3A 0D A8 D8 C3 13 Pager: pagejim@notepage.com 7C F0 B5 BF 27 8B 92 FE "The box said 'Requires Windows 95, NT, or better,' so I installed FreeBSD" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 18:30:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from firewall.reed.wattle.id.au (darren2.lnk.telstra.net [139.130.53.33]) by hub.freebsd.org (Postfix) with ESMTP id E95BD14BEF; Fri, 18 Jun 1999 18:30:18 -0700 (PDT) (envelope-from darrenr@reed.wattle.id.au) Received: (from root@localhost) by firewall.reed.wattle.id.au (8.9.1/8.8.7) id BAA20262; Sat, 19 Jun 1999 01:30:16 GMT Received: from avalon.reed.wattle.id.au(192.168.1.1) by firewall.reed.wattle.id.au via smap (V1.3) id sma020260; Sat Jun 19 01:30:06 1999 Received: from percival.reed.wattle.id.au. (percival.reed.wattle.id.au [192.168.1.5]) by avalon.reed.wattle.id.au (8.9.0.Beta3/8.9.0.Beta3) with SMTP id LAA11524; Sat, 19 Jun 1999 11:30:05 +1000 (EST) From: Darren Reed Message-Id: <199906190130.LAA11524@avalon.reed.wattle.id.au> Subject: Re: Introduction In-Reply-To: from Nicolai Petri at "Jun 18, 99 10:15:14 pm" To: npp@distortion.dk (Nicolai Petri) Date: Sat, 19 Jun 1999 11:30:04 +1000 (EST) Cc: green@unixhelp.org, ru@ucb.crimea.ua, hackers@FreeBSD.org, cvs-committers@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL37 (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 some email I received from Nicolai Petri, sie wrote: > On Fri, 18 Jun 1999, Brian Fundakowski Feldman wrote: > > On Fri, 18 Jun 1999, Ruslan Ermilov wrote: > > > > > Let's join our efforts in this area! > > > IPFW code is very ugly... > > > > Which is basically due to it being hacked on for years without a cleanup. > > Now's the time (between major versions) to do this, I think. How's this: > > let's organize a small group to bounce ideas off eachother, first of all > > (I'm forwarding this to hackers to perhaps elicit a response of more people.) > > We should get ideas on what people think is wrong with the current > > implementation, what new features should be added, and where we should > > rearchitect. > > What about support for protocol verification ?? (Example : Blocking of > malformed ftp commands.) Surely you jest... > Wich layer would it be logically to implement this in ? 5 and above. > Is a userland proxy the only way ? With a 100% reliability, yes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 18:51:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.erols.com (smtp1.erols.com [207.172.3.234]) by hub.freebsd.org (Postfix) with ESMTP id 9821114CD3 for ; Fri, 18 Jun 1999 18:51:46 -0700 (PDT) (envelope-from ugen@xonix.com) Received: from xonix.com (207-172-196-192.s192.tnt1.hck.nj.dialup.rcn.com [207.172.196.192]) by smtp1.erols.com (8.8.8/8.8.5) with ESMTP id VAA05819; Fri, 18 Jun 1999 21:49:59 -0400 (EDT) Message-ID: <3769A669.3ED8000E@xonix.com> Date: Thu, 17 Jun 1999 21:52:41 -0400 From: Ugen Antsilevitch X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Ruslan Ermilov , Brian Fundakowski Feldman , Darren Reed , Nicolai Petri , Wes Peters , Bill Fumerola Cc: hackers@FreeBSD.ORG Subject: Re: Introduction References: <37693FCF.608FA855@xonix.com> <19990618221558.A71643@relay.ucb.crimea.ua> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok...i guess i would be the wrong person for cleaning the code since i kinda responsible for the damn thing being a mess in the first place. I can try:) I however have some ideas on how to make a better API (as in more hooks to userland, which btw now after i have read an "FTP requests comment, migh even make more sence). One thing though - if we (you :) will really work on this - can we set up some tiny mailing list for IPFW ? Should we? (Or tell me if i have everyone who was interested on this e-mail "To" list and forget this request:) --Ugen Ruslan Ermilov wrote: > On Thu, Jun 17, 1999 at 02:34:55PM -0400, Ugen Antsilevitch wrote: > > The part that obviously interests me is IPFW - if you guys are > > interested to put some effort in "real" i.e. stateful firewall > > to be developed i'd love to offer any help i can. > > > Great! > > How we should proceed -- that's the question. My plan: > > * Clean the existing code (both userland and kernel) (10-20% done) > * Re-design the ipfw's API > * Port the existing functionality to the new API > * Proceed with new features > > -- > Ruslan Ermilov Sysadmin and DBA of the > ru@ucb.crimea.ua United Commercial Bank, > ru@FreeBSD.org FreeBSD committer, > +380.652.247.647 Simferopol, Ukraine > > http://www.FreeBSD.org The Power To Serve > http://www.oracle.com Enabling The Information Age > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 18:55:38 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 1C44814D1E for ; Fri, 18 Jun 1999 18:55:30 -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 VAA24912; Fri, 18 Jun 1999 21:55:51 -0400 (EDT) Date: Fri, 18 Jun 1999 20:55:50 -0500 (EST) From: Alfred Perlstein To: =?iso-8859-1?Q?Markus_D=F6hr?= Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: M$ using Linux? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Jun 1999, [iso-8859-1] Markus D=F6hr wrote: > What do you think about that: >=20 > [root@beta ~]# nmap -vv -p119 -P0 -sT -O betanews.microsoft.com >=20 > > Sequence numbers: E6E23C4C E7368B4F E6E0CC8D E79B4DEC E7A43C4E E76D208A > Remote operating system guess: Linux 2.1.122 - 2.1.132; 2.2.0-pre1 - 2.2.= 2 > OS Fingerprint: > TSeq(Class=3DRI%gcd=3D1%SI=3D3A46A8) > T1(Resp=3DY%DF=3DY%W=3D7F53%ACK=3DS++%Flags=3DAS%Ops=3DMENNTNW) > T2(Resp=3DN) > T3(Resp=3DY%DF=3DY%W=3D7F53%ACK=3DS++%Flags=3DAS%Ops=3DMENNTNW) > T4(Resp=3DY%DF=3DN%W=3D0%ACK=3DO%Flags=3DR%Ops=3D) > T5(Resp=3DN) > T6(Resp=3DN) > T7(Resp=3DN) > PU(Resp=3DN) > Nmap run completed -- 1 IP address (1 host up) scanned in 20 seconds > >=20 > and that? >=20 > [root@beta ~]# telnet betanews.microsoft.com 119 Perhaps you sent this to the wrong list, or are looking for someone to flame you? :) It's cool that Linux is being used by MS, more power to you. -Alfred (someone who knows a lot of the people on the Hotmail team) :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 19: 2:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from argus.tfs.net (host1-126.birch.net [216.212.1.126]) by hub.freebsd.org (Postfix) with ESMTP id 656D314D1E for ; Fri, 18 Jun 1999 19:02:39 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id UAA70763; Fri, 18 Jun 1999 20:25:29 -0500 (CDT) From: Jim Bryant Message-Id: <199906190125.UAA70763@argus.tfs.net> Subject: Re: SMP and Celerons... In-Reply-To: from Pat Lynch at "Jun 18, 99 08:11:08 pm" To: lynch@bsdunix.net (Pat Lynch) Date: Fri, 18 Jun 1999 20:25:28 -0500 (CDT) Cc: freebsd-hackers@freebsd.org Reply-To: jbryant@unix.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: > Heya, sorry I tried this one on -stable and -questions and noone seems to > know, and they actually go so far as to ask me how I got two celerons in a > motherboard... > > so I ask here. > > I have two PPGA(Socket 370) Celeron 333A's that are on MSI6905 Dual Socket > 1 adaptors... > > a Tyan Thunder 2 motherboard (onboard scsi, sound, etc.) there is a problem with the freebsd sound support for this board, but i am told it is being worked on [?]. > I boot an SMP kernel, it gets right past autoboot... then panics > > the message was that it "could not find local apic"... > > its kinda strange because essentially with these adaptors, the celerons > should be 1) SMP capable, and 2) the same as a PII, except no L2 cache > > I know others that ran FreeBSD SMP with celerons... anyone know if theres > some kind of patch I need or modification I have to make to get either > -CURRENT or -STABLE working on this machine? Right now it is running a UP > kernel instead of the SMP one and runs fine. strangeness. i run the same board with dual pII-333's, Tyan Thunder2, S1696DLUA. when i boot, i show two cpus and an apic. i have two theories: 1). these boards have a problem with celery. 2). you have a flaky mb. granted, i haven't heard about too many of them being flaky, but that they have an above average reliability level. but then, there is always someone that get s flake sooner or later. My experience [of about 12 days so far] is that this is a quality midrange system, as configured here, and is maybe even a tad more reliable than my workhorse p133 [which has had three spontaneous reboots in the same period, but running an older -current by a few weeks]. Unless you have some weird boards, -current currently works fine on my system [although -current is subject to overnight changes that produce catastrophic failures every now and then, always check which way the wind is blowing in the -current mailing list before doing a make installworld]. Can you borrow a couple of pII's? It would be interesting to see if the Thunder2's have a problem sith celery. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #41: Tue Jun 15 10:59:11 CDT 1999 jbryant@wahoo:/usr/src/sys/compile/WAHOO Timecounter "i8254" frequency 1192991 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x650 Stepping=0 Features=0x183fbff real memory = 268435456 (262144K bytes) avail memory = 257720320 (251680K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 . . . APIC_IO: Testing 8254 interrupt delivery APIC_IO: Broken MP table detected: 8254 is not connected to IO APIC int pin 2 APIC_IO: routing 8254 via 8259 on pin 0 . . . changing root device to da0s1a [and normal boot] 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 Fri Jun 18 19: 6:12 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 04D501515B for ; Fri, 18 Jun 1999 19:06:10 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id WAA85838; Fri, 18 Jun 1999 22:05:56 -0400 (EDT) Date: Fri, 18 Jun 1999 22:04:30 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@janus.syracuse.net To: Darren Reed Cc: Nicolai Petri , ru@ucb.crimea.ua, hackers@FreeBSD.org Subject: firewalling (Was Re: Introduction) In-Reply-To: <199906190130.LAA11524@avalon.reed.wattle.id.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 How do you feel about (after getting it fixed in -CURRENT) helping with converting ipfw(8) to just a front-end to ipf? I think it's worth discussing whether it's actually worth it to rewrite IPFW or just work on improving ipfilter. (discussion moved to -hackers) 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 Fri Jun 18 19:29:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from firewall.reed.wattle.id.au (darren2.lnk.telstra.net [139.130.53.33]) by hub.freebsd.org (Postfix) with ESMTP id 9DFDB1513E for ; Fri, 18 Jun 1999 19:29:20 -0700 (PDT) (envelope-from darrenr@reed.wattle.id.au) Received: (from root@localhost) by firewall.reed.wattle.id.au (8.9.1/8.8.7) id CAA20353; Sat, 19 Jun 1999 02:29:17 GMT Received: from avalon.reed.wattle.id.au(192.168.1.1) by firewall.reed.wattle.id.au via smap (V1.3) id sma020351; Sat Jun 19 02:28:57 1999 Received: from percival.reed.wattle.id.au. (percival.reed.wattle.id.au [192.168.1.5]) by avalon.reed.wattle.id.au (8.9.0.Beta3/8.9.0.Beta3) with SMTP id MAA11563; Sat, 19 Jun 1999 12:28:56 +1000 (EST) From: Darren Reed Message-Id: <199906190228.MAA11563@avalon.reed.wattle.id.au> Subject: Re: firewalling (Was Re: Introduction) In-Reply-To: from Brian Fundakowski Feldman at "Jun 18, 99 10:04:30 pm" To: green@unixhelp.org (Brian Fundakowski Feldman) Date: Sat, 19 Jun 1999 12:28:55 +1000 (EST) Cc: npp@distortion.dk, ru@ucb.crimea.ua, hackers@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL37 (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 some email I received from Brian Fundakowski Feldman, sie wrote: > How do you feel about (after getting it fixed in -CURRENT) helping with > converting ipfw(8) to just a front-end to ipf? I think it's worth discussing > whether it's actually worth it to rewrite IPFW or just work on improving > ipfilter. (discussion moved to -hackers) I imagine they might be fighting words to some ;) As I see it, if you added hooks for divert to ipfilter in FreeBSD and maybe added the rule number bits (I *know* there are going to be people who'd just die without it) then I can't see why you'd need ipfw. I imagine that would be a hell of a lot less work than bringing the features of ipfilter into ipfw. It'd also be one of those steps forward in compatibility between the various BSDs... Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 19:36:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monk.via.net (monk.via.net [209.81.9.10]) by hub.freebsd.org (Postfix) with ESMTP id 762471508B for ; Fri, 18 Jun 1999 19:35:29 -0700 (PDT) (envelope-from joe@monk.via.net) Received: (from joe@localhost) by monk.via.net (8.8.8/8.8.8) id TAA11773 for hackers@freebsd.org; Fri, 18 Jun 1999 19:35:26 -0700 (PDT) (envelope-from joe) From: Joe McGuckin Message-Id: <199906190235.TAA11773@monk.via.net> Date: Fri, 18 Jun 1999 19:35:26 -0700 (PDT) To: hackers@freebsd.org Subject: 802.1q vlans supported ? X-Mailer: Ishmail 1.3.1-970608-bsdi MIME-Version: 1.0 Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I notice that there are paches for Linux to implement VLANS. Do we support it? Joe Joe McGuckin ViaNet Communications 994 San Antonio Road Palo Alto, CA 94303 Phone: 650-969-2203 Cell: 650-207-0372 Fax: 650-969-2124 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 19:40: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 0256814CB6 for ; Fri, 18 Jun 1999 19:40:34 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id WAA86336; Fri, 18 Jun 1999 22:39:22 -0400 (EDT) Date: Fri, 18 Jun 1999 22:37:57 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@janus.syracuse.net To: Darren Reed Cc: npp@distortion.dk, ru@ucb.crimea.ua, hackers@FreeBSD.ORG Subject: Re: firewalling (Was Re: Introduction) In-Reply-To: <199906190228.MAA11563@avalon.reed.wattle.id.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 Sat, 19 Jun 1999, Darren Reed wrote: > In some email I received from Brian Fundakowski Feldman, sie wrote: > > How do you feel about (after getting it fixed in -CURRENT) helping with > > converting ipfw(8) to just a front-end to ipf? I think it's worth discussing > > whether it's actually worth it to rewrite IPFW or just work on improving > > ipfilter. (discussion moved to -hackers) > > I imagine they might be fighting words to some ;) As I see it, if you > added hooks for divert to ipfilter in FreeBSD and maybe added the rule > number bits (I *know* there are going to be people who'd just die without > it) then I can't see why you'd need ipfw. I imagine that would be a hell > of a lot less work than bringing the features of ipfilter into ipfw. > > It'd also be one of those steps forward in compatibility between the various > BSDs... Yes, and I know it might take some work. I'd like to have something good be the default in FreeBSD, and I feel that maybe if ipfilter can be brought to the foreground well and made backward compatible (i.e. ipfw(8) to translate (perl? /bin/sh? idunno)), it will be a winning thing. I'd of course like to add UID/GID support to ipfilter like I did to IPFW (but didn't commit). IPFW is nearing the end of its maintainable life. It needs a pretty large rewrite or full replacement pretty soon. If we can get ipfilter in src/contrib kept up-to-date and working, supplying a replacement for ipfw(8) as a front-end, I don't see why ipfilter can't be the "FreeBSD firewall." > > Darren > > > 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 Fri Jun 18 20:38:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (Postfix) with ESMTP id 16F8C14FC7; Fri, 18 Jun 1999 20:38:24 -0700 (PDT) (envelope-from kline@tera.com) Received: from athena.tera.com (athena.tera.com [207.224.230.169]) by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id UAA19892; Fri, 18 Jun 1999 20:38:09 -0700 (PDT) Received: (from kline@localhost) by athena.tera.com (8.7.5/8.7.3) id UAA08170; Fri, 18 Jun 1999 20:38:08 -0700 (PDT) Date: Fri, 18 Jun 1999 20:38:08 -0700 From: Gary Kline To: Greg Lehey Cc: Thomas Good , FreeBSD Hackers , FreeBSD Questions Subject: Re: Beware of UnixWare 7 Message-ID: <19990618203808.A8164@athena.tera.com> References: <19990618181324.A2863@freebie.lemis.com> <19990619085444.O2863@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95us In-Reply-To: <19990619085444.O2863@freebie.lemis.com>; from Greg Lehey on Sat, Jun 19, 1999 at 08:54:44AM +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jun 19, 1999 at 08:54:44AM +0930, Greg Lehey wrote: [[ ... ]] > > I've tried twice more to install UnixWare. It makes all the right > noises, but on reboot it just hangs. I'm giving up now. > Maybe you should check out Limux 6.0. I just saw it shrink-wrapped (RedHat + MacMillan[?]) at Costco. Warehouse chain. gary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 21:19: 7 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 321F214C9D; Fri, 18 Jun 1999 21:18: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 NAA14843; Sat, 19 Jun 1999 13:48:59 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA00602; Sat, 19 Jun 1999 13:49:00 +0930 (CST) Date: Sat, 19 Jun 1999 13:49:00 +0930 From: Greg Lehey To: Gary Kline Cc: Thomas Good , FreeBSD Hackers , FreeBSD Questions Subject: Re: Beware of UnixWare 7 Message-ID: <19990619134900.A430@freebie.lemis.com> References: <19990618181324.A2863@freebie.lemis.com> <19990619085444.O2863@freebie.lemis.com> <19990618203808.A8164@athena.tera.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990618203808.A8164@athena.tera.com>; from Gary Kline on Fri, Jun 18, 1999 at 08:38:08PM -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, 18 June 1999 at 20:38:08 -0700, Gary Kline wrote: > On Sat, Jun 19, 1999 at 08:54:44AM +0930, Greg Lehey wrote: > > [[ ... ]] >> >> I've tried twice more to install UnixWare. It makes all the right >> noises, but on reboot it just hangs. I'm giving up now. >> > > Maybe you should check out Limux 6.0. I just saw it shrink-wrapped > (RedHat + MacMillan[?]) at Costco. Warehouse chain. I can't use that to develop UnixWare software. In fact, I *did* install (Debian) Linux on the system, just to make sure that it wasn't some silly boot problem. I also installed NetBSD, all on the same partition (overwriting the previous ones, of course). NetBSD had the nicest install, but Debian was alright as well, though it's a pain that Linux needs one (Microsoft) partition per file system or swap. Both NetBSD and Linux installed and booted fine. They also booted from CD-ROM, while UnixWare required no fewer than 3 boot floppies, which had to be made from the CD-ROM. 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 Jun 18 23:21:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 9DA0A14CA9 for ; Fri, 18 Jun 1999 23:20:58 -0700 (PDT) (envelope-from darius@dons.net.au) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id PAA07728; Sat, 19 Jun 1999 15:50:38 +0930 (CST) (envelope-from darius@dons.net.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990619155038:5705=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: <51363.929728609@axl.noc.iafrica.com> Date: Sat, 19 Jun 1999 15:50:38 +0930 (CST) From: "Daniel J. O'Connor" To: Sheldon Hearn Subject: RE: Obtaining client host IP before accept() Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990619155038:5705=_ Content-Type: text/plain; charset=us-ascii On 18-Jun-99 Sheldon Hearn wrote: > Will the IP address of the client host ever enter buf[] if the > accept() is _not_ uncommented? > > I don't need portability, since this is for use within the FreeBSD inetd > exclusively. Well if you CAN'T do it in FreeBSD, is there an OS we can copy the API from that DOES do it? (Providing it isn't too braindamaged of course.. :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum --_=XFMail.1.3.p0.FreeBSD:990619155038:5705=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN2s2tmj0TqzKxF7VAQHMJAQAhgw2jvM31DJ7TBOOGpnwpCMwGWgaxULM +kfEh5p2KDoG4yqh147j162pCxKFshc7CNghZJsfsF/23VnXqOlvU6x839MYlKxX N0TH+IYGIwfyQ3UsNaAFArWNg4DqGKeAxAGV6VnCXFAQSTzHvd8AE73LqP9xP1xY rYMR1Oe7JDQ= =KSZ4 -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990619155038:5705=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 18 23:51:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 8D97E14CF6 for ; Fri, 18 Jun 1999 23:51:09 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id AAA28529; Sat, 19 Jun 1999 00:51:03 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <376B3DD6.17CB270D@softweyr.com> Date: Sat, 19 Jun 1999 00:51: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: Markus =?iso-8859-1?Q?D=F6hr?= Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: M$ using Linux? References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Markus Döhr wrote: > > What do you think about that: > > [root@beta ~]# nmap -vv -p119 -P0 -sT -O betanews.microsoft.com > > > Sequence numbers: E6E23C4C E7368B4F E6E0CC8D E79B4DEC E7A43C4E E76D208A > Remote operating system guess: Linux 2.1.122 - 2.1.132; 2.2.0-pre1 - 2.2.2 > OS Fingerprint: > TSeq(Class=RI%gcd=1%SI=3A46A8) > T1(Resp=Y%DF=Y%W=7F53%ACK=S++%Flags=AS%Ops=MENNTNW) > T2(Resp=N) > T3(Resp=Y%DF=Y%W=7F53%ACK=S++%Flags=AS%Ops=MENNTNW) > T4(Resp=Y%DF=N%W=0%ACK=O%Flags=R%Ops=) > T5(Resp=N) > T6(Resp=N) > T7(Resp=N) > PU(Resp=N) > Nmap run completed -- 1 IP address (1 host up) scanned in 20 seconds > > > and that? > > [root@beta ~]# telnet betanews.microsoft.com 119 > Trying 207.46.180.35... > Connected to betanews.msn.com. > Escape character is '^]'. > 200 cpmsblns02.microsoft.com InterNetNews NNRP server INN 2.2 21-Jan-1999 ready > (posting ok). > > INN running on NT? > > And the most interesting: > Quoting Alan Cox from the linux-kernel developer list: > > someone asking: > > > I guess that they run windows-2000 on the beta site, and then I guess is > > that they > > have stolen IP-code from Linux. Im right, yes ?! > > > Unlikely. Judging by the window 2000 beta traces they run a BSD stack derivative > close to freebsd - and the BSD license permits such use > If they give credit in the copyrights. I've never seen Microsloth do that. BTW, queso reports: # queso betanews.microsoft.com:119 207.46.180.35:119 * Linux 2.1.xx -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr 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 Sat Jun 19 3:35:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from saturn.ms.tlk.com (saturn.ms.tlk.com [194.97.68.6]) by hub.freebsd.org (Postfix) with ESMTP id 6698514BF5 for ; Sat, 19 Jun 1999 03:35:50 -0700 (PDT) (envelope-from br@smilla.rueskamp.com) Received: from mars.ms.tlk.com (mars.ms.tlk.com [194.97.68.1]) by saturn.ms.tlk.com (Postfix) with ESMTP id 0F00E4ECF7; Sat, 19 Jun 1999 12:35:50 +0200 (CEST) Received: from smilla.rueskamp.com(really [194.97.69.109]) by mars.ms.tlk.com via sendmail with esmtp id for ; Sat, 19 Jun 1999 12:35:49 +0200 (CEST)) Received: (from br@localhost) by smilla.rueskamp.com (8.9.3/8.9.3) id MAA24192; Sat, 19 Jun 1999 12:35:45 +0200 (CEST) (envelope-from br) From: Bodo Rueskamp Message-Id: <199906191035.MAA24192@smilla.rueskamp.com> Subject: Re: Obtaining client host IP before accept() In-Reply-To: from "Daniel J. O'Connor" at "Jun 19, 1999 03:50:38 pm" To: darius@dons.net.au (Daniel J. O'Connor) Date: Sat, 19 Jun 1999 12:35:45 +0200 (CEST) Cc: sheldonh@uunet.co.za (Sheldon Hearn), hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Will the IP address of the client host ever enter buf[] if the > > accept() is _not_ uncommented? > > I don't need portability, since this is for use within the FreeBSD inetd > > exclusively. > > Well if you CAN'T do it in FreeBSD, is there an OS we can copy the API from > that DOES do it? (Providing it isn't too braindamaged of course.. :) There is an API that can do it: System V Release 4 Streams and TLI (Transport Layer Interface). TLI is not based on systems calls doing the job. It is based on message transfer between the user and some kernel entity. Incoming calls are indicated by sending a T_CONN_IND message (connect indication) to the user process. Then the user process opens a second TLI stream (like using the socket() system call) and sends a T_CONN_CON message (connect confirmation) to the kernel entity. The TLI API is based on OSI. It doesn't provide much more functionality than BSD sockets. Two APIs for the same task isn't very useful. So you should better hack the BSD sockets to fit your needs. A similar functionality in BSD-world would be: (1) use recvfrom() instead of accept() on the socket TLI: use getmsg() to receive the T_CONN_IND (2) create a new socket using socket() TLI: use open() to open a new stream (3) accept the connection using an ioctl() TLI: send T_CONN_CON to accept the connection or (2) reject the connection using an ioctl() TLI: send T_DISCON_REQ to reject the connection Here's an overview of the TLI messages: TLI (user) TLI (kernel) BSD socket T_INFO_REQ T_INFO_ACK - T_BIND_REQ T_BIND_ACK bind() T_UNBIND_REQ - - T_OPTMGMT_REQ T_OPTMGMT_ACK setsockopt() - T_ERROR_ACK errno T_CONN_REQ T_CONN_RES connect() T_CONN_CON T_CONN_IND accept() T_DISCON_REQ - shutdown() - T_DISCON_IND errno T_ORDREL_REQ - shutdown() T_DATA_REQ - send() / sendto() / write() - T_DATA_IND recv() / recvfrom() / read() T_EXDATA_REQ - send() / sendto() - T_EXDATA_IND recv() / recvfrom() T_UNITDATA_REQ - send() / sendto() / write() - T_UNITDATA_IND recv() / recvfrom() / read() - T_UDERROR_IND recv() / recvfrom() / read() & errno ; Bodo -- Bodo Rüskamp, br@rueskamp.com, 51°55' N 7°41' E (1) Elvis is alive. (2) Dinosaurs too. (3) The next millenium starts on January 1st 2000. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 5:41:59 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 906CE14FE8; Sat, 19 Jun 1999 05:41:55 -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 OAA86085; Sat, 19 Jun 1999 14:41:26 +0200 (CEST) (envelope-from des) To: Ruslan Ermilov Cc: ugen@xonix.com, green@unixhelp.org, committers@FreeBSD.org, hackers@FreeBSD.org Subject: Re: Introduction References: <37693FCF.608FA855@xonix.com> <19990618221558.A71643@relay.ucb.crimea.ua> From: Dag-Erling Smorgrav Date: 19 Jun 1999 14:41:26 +0200 In-Reply-To: Ruslan Ermilov's message of "Fri, 18 Jun 1999 22:15:58 +0300" Message-ID: Lines: 14 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ruslan Ermilov writes: > * Clean the existing code (both userland and kernel) (10-20% done) > * Re-design the ipfw's API > * Port the existing functionality to the new API > * Proceed with new features Pretty please with sugar on top, design an API that can be extended without breaking binary compatibility. We've had too much of that for no good reason (at least once between 2.2.7 and 2.2.8, and once between 3.1 and 3.2). 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 Sat Jun 19 6: 3:15 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 84CCD14E7A; Sat, 19 Jun 1999 06:03:09 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id OAA80968; Sat, 19 Jun 1999 14:03:35 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 19 Jun 1999 14:03:34 +0100 (BST) From: Doug Rabson To: Dag-Erling Smorgrav Cc: Ruslan Ermilov , ugen@xonix.com, green@unixhelp.org, committers@freebsd.org, hackers@freebsd.org Subject: Re: Introduction 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 Jun 1999, Dag-Erling Smorgrav wrote: > Ruslan Ermilov writes: > > * Clean the existing code (both userland and kernel) (10-20% done) > > * Re-design the ipfw's API > > * Port the existing functionality to the new API > > * Proceed with new features > > Pretty please with sugar on top, design an API that can be extended > without breaking binary compatibility. We've had too much of that for > no good reason (at least once between 2.2.7 and 2.2.8, and once > between 3.1 and 3.2). As far as possible, all new apis in the kernel should be designed with a stable ABI. Its pretty simple if you follow a few simple rules: 1. Hide implementation data structures. Access all information outside the core implementation using function calls. 2. Try to avoid using complex structures in the api. Each structure in an api defines part of its ABI. Changing that structure later breaks the ABI. 3. Keep the external api as simple as possible. As a rule of thumb, try to write manpages for each function. If you can't describe the function accurately and concisely in a manpage then its too complex. -- 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 Sat Jun 19 6:53: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bytor.rush.net (bytor.rush.net [209.45.245.145]) by hub.freebsd.org (Postfix) with ESMTP id A855C14E42 for ; Sat, 19 Jun 1999 06:52:57 -0700 (PDT) (envelope-from lynch@bsdunix.net) Received: from localhost (lynch@localhost) by bytor.rush.net (8.9.3/8.9.3) with ESMTP id JAA26678; Sat, 19 Jun 1999 09:52:55 -0400 (EDT) Date: Sat, 19 Jun 1999 09:52:54 -0400 (EDT) From: Pat Lynch X-Sender: lynch@bytor.rush.net To: Jim Bryant Cc: freebsd-hackers@freebsd.org Subject: Re: SMP and Celerons... In-Reply-To: <199906190125.UAA70763@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 Actually I have a "patch" that will get sound working on this board (its working in mine right now...) but it disables support for all the other ad1848 sound cards ;) I'm actually going through to make it work for all of them now (at worst its just a couple case statements *shrug*) If you are only using sound in this on mboard, then I'll give you the diffs I have. I *can* however grab the pII's from my mboard (an exact duplicate) and swap CPU's temporarily, but I'll do it later, as I have not the inclination to do it right now. If the Thunder2 has a problem with celery, I'll know by tonight. anyway, heres the diffs I made to /usr/src/sys/i386/isa/snd/ad1848.c --- ad1848.c Sat Jun 19 05:13:13 1999 +++ ad1848.c.TYAN Sat Jun 19 05:13:32 1999 @@ -1443,7 +1443,7 @@ cs423x_probe(u_long csn, u_long vend_id) { char *s = NULL ; - u_long id = vend_id & 0xff00ffff; + u_long id = vend_id & 0xffffffff; if ( id == 0x3700630e ) s = "CS4237" ; else if ( id == 0x2500630e ) @@ -1458,6 +1458,10 @@ s = "Yamaha SA2"; else if ( id == 0x3000a865) s = "Yamaha SA3"; + else if ( id == 0x2100a865) + s = "Yamaha SA3"; + else if ( id == 0x0208a865) + s = "Yamaha SA3"; else if ( id == 0x0000a865) s = "Yamaha YMF719 OPL-SA3"; else if (vend_id == 0x8140d315) @@ -1517,7 +1521,8 @@ dev->id_alive = 16 ; /* number of io ports ? */ tmp_d = sb_op_desc ; if (vend_id==0x2000a865 || vend_id==0x3000a865 || - vend_id==0x0008a865 || vend_id==0x8140d315) { + vend_id==0x0008a865 || vend_id==0x8140d315 || + vend_id==0x2100a865 || vend_id==0x0208a865) { /* Yamaha SA2/SA3 or ENSONIQ SoundscapeVIVO ENS4081 */ dev->id_iobase = d.port[0] ; tmp_d.alt_base = d.port[1] ; @@ -1532,10 +1537,12 @@ tmp_d = mss_op_desc ; dev->id_iobase = d.port[0] -4 ; /* XXX old mss have 4 bytes before... */ tmp_d.alt_base = d.port[2]; - switch (vend_id & 0xff00ffff) { + switch (vend_id & 0xffffffff) { case 0x2000a865: /* Yamaha SA2 */ case 0x3000a865: /* Yamaha SA3 */ + case 0x2100a865: /* Yamaha SA3 */ + case 0x0208a865: /* Yamaha SA3 */ case 0x0000a865: /* Yamaha TMF719 SA3 */ dev->id_iobase = d.port[1]; tmp_d.alt_base = d.port[0]; notice the switch from the vendor id numbers, the TYAN board has 0xffffffff instead of 0xff00ffff (this is based on the patch someone posted to -current earlier this week) like I said, to make it work on all ad1848 boards is trivial, but then, I'm not really a coder, so it takes me more time to work out how I want to do it ;) and chances are, compared to others, it'll be sloppy. -Pat ___________________________________________________________________________ Pat Lynch lynch@rush.net lynch@bsdunix.net Systems Administrator Rush Networking ___________________________________________________________________________ On Fri, 18 Jun 1999, Jim Bryant wrote: > In reply: > > Heya, sorry I tried this one on -stable and -questions and noone seems to > > know, and they actually go so far as to ask me how I got two celerons in a > > motherboard... > > > > so I ask here. > > > > I have two PPGA(Socket 370) Celeron 333A's that are on MSI6905 Dual Socket > > 1 adaptors... > > > > a Tyan Thunder 2 motherboard (onboard scsi, sound, etc.) > > there is a problem with the freebsd sound support for this board, but > i am told it is being worked on [?]. > > > I boot an SMP kernel, it gets right past autoboot... then panics > > > > the message was that it "could not find local apic"... > > > > its kinda strange because essentially with these adaptors, the celerons > > should be 1) SMP capable, and 2) the same as a PII, except no L2 cache > > > > I know others that ran FreeBSD SMP with celerons... anyone know if theres > > some kind of patch I need or modification I have to make to get either > > -CURRENT or -STABLE working on this machine? Right now it is running a UP > > kernel instead of the SMP one and runs fine. > > strangeness. > > i run the same board with dual pII-333's, Tyan Thunder2, S1696DLUA. > > when i boot, i show two cpus and an apic. i have two theories: > > 1). these boards have a problem with celery. > > 2). you have a flaky mb. granted, i haven't heard about too many of > them being flaky, but that they have an above average reliability > level. but then, there is always someone that get s flake sooner or > later. > > My experience [of about 12 days so far] is that this is a quality > midrange system, as configured here, and is maybe even a tad more > reliable than my workhorse p133 [which has had three spontaneous > reboots in the same period, but running an older -current by a few > weeks]. > > Unless you have some weird boards, -current currently works fine on > my system [although -current is subject to overnight changes that > produce catastrophic failures every now and then, always check which > way the wind is blowing in the -current mailing list before doing a > make installworld]. > > Can you borrow a couple of pII's? It would be interesting to see if > the Thunder2's have a problem sith celery. > > Copyright (c) 1992-1999 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-CURRENT #41: Tue Jun 15 10:59:11 CDT 1999 > jbryant@wahoo:/usr/src/sys/compile/WAHOO > Timecounter "i8254" frequency 1192991 Hz > CPU: Pentium II/Xeon/Celeron (686-class CPU) > Origin = "GenuineIntel" Id = 0x650 Stepping=0 > Features=0x183fbff > real memory = 268435456 (262144K bytes) > avail memory = 257720320 (251680K bytes) > Programming 24 pins in IOAPIC #0 > FreeBSD/SMP: Multiprocessor motherboard > cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 > cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 > io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 > . > . > . > APIC_IO: Testing 8254 interrupt delivery > APIC_IO: Broken MP table detected: 8254 is not connected to IO APIC int pin 2 > APIC_IO: routing 8254 via 8259 on pin 0 > . > . > . > changing root device to da0s1a > [and normal boot] > > 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 Sat Jun 19 7:24:12 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 02E2C14E18; Sat, 19 Jun 1999 07:24:08 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id KAA99863; Sat, 19 Jun 1999 10:23:48 -0400 (EDT) Date: Sat, 19 Jun 1999 10:22:23 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Doug Rabson Cc: Dag-Erling Smorgrav , Ruslan Ermilov , ugen@xonix.com, hackers@FreeBSD.org, luigi@FreeBSD.org Subject: Re: Introduction 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, 19 Jun 1999, Doug Rabson wrote: > On 19 Jun 1999, Dag-Erling Smorgrav wrote: > > > Ruslan Ermilov writes: > > > * Clean the existing code (both userland and kernel) (10-20% done) > > > * Re-design the ipfw's API > > > * Port the existing functionality to the new API > > > * Proceed with new features > > > > Pretty please with sugar on top, design an API that can be extended > > without breaking binary compatibility. We've had too much of that for > > no good reason (at least once between 2.2.7 and 2.2.8, and once > > between 3.1 and 3.2). > > As far as possible, all new apis in the kernel should be designed with a > stable ABI. Its pretty simple if you follow a few simple rules: > > 1. Hide implementation data structures. Access all information > outside the core implementation using function calls. > 2. Try to avoid using complex structures in the api. Each > structure in an api defines part of its ABI. Changing that > structure later breaks the ABI. > 3. Keep the external api as simple as possible. As a rule of > thumb, try to write manpages for each function. If you can't > describe the function accurately and concisely in a manpage > then its too complex. > It might be worth (discussion of) making ipfilter the firewall of choice for 4.0. There would of course be rule conversion scripts/programs (ipfw->ipf(5)), and ipfilter would be converted to a KLD, cruft removed (I'm going to work on these), and ipfilter KLD support (currently options IPFILTER_LKM) made a non-option. It seems that our pretty proprietary ipfw is no longer a good idea. And if Luigi ported all of his stuff to ipfilter from ipfw, and I did per-[ug]id support for ipfilter (which I will), we'll definitely be ahead. Ipfilter is a win for compatibilty/ubiquity, and seems to be faster than ipfw anyway. Are there any technical arguments against ipfilter or for ipfw? Note that: political arguments do not count, a conversion method will be available for ipfw users, and we should have anything special (DummyNet, uid/gid-based filtering) ported over to ipfilter. > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > > 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 Jun 19 7:36:58 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 F082E14E18; Sat, 19 Jun 1999 07:36:52 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id PAA81197; Sat, 19 Jun 1999 15:37:26 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 19 Jun 1999 15:37:26 +0100 (BST) From: Doug Rabson To: "Brian F. Feldman" Cc: Dag-Erling Smorgrav , Ruslan Ermilov , ugen@xonix.com, hackers@FreeBSD.org, luigi@FreeBSD.org Subject: Re: Introduction 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, 19 Jun 1999, Brian F. Feldman wrote: > On Sat, 19 Jun 1999, Doug Rabson wrote: > > > On 19 Jun 1999, Dag-Erling Smorgrav wrote: > > > > > Ruslan Ermilov writes: > > > > * Clean the existing code (both userland and kernel) (10-20% done) > > > > * Re-design the ipfw's API > > > > * Port the existing functionality to the new API > > > > * Proceed with new features > > > > > > Pretty please with sugar on top, design an API that can be extended > > > without breaking binary compatibility. We've had too much of that for > > > no good reason (at least once between 2.2.7 and 2.2.8, and once > > > between 3.1 and 3.2). > > > > As far as possible, all new apis in the kernel should be designed with a > > stable ABI. Its pretty simple if you follow a few simple rules: > > > > 1. Hide implementation data structures. Access all information > > outside the core implementation using function calls. > > 2. Try to avoid using complex structures in the api. Each > > structure in an api defines part of its ABI. Changing that > > structure later breaks the ABI. > > 3. Keep the external api as simple as possible. As a rule of > > thumb, try to write manpages for each function. If you can't > > describe the function accurately and concisely in a manpage > > then its too complex. > > > > It might be worth (discussion of) making ipfilter the firewall of > choice for 4.0. There would of course be rule conversion > scripts/programs (ipfw->ipf(5)), and ipfilter would be converted to a > KLD, cruft removed (I'm going to work on these), and ipfilter KLD > support (currently options IPFILTER_LKM) made a non-option. It seems > that our pretty proprietary ipfw is no longer a good idea. > And if Luigi ported all of his stuff to ipfilter from ipfw, and I > did per-[ug]id support for ipfilter (which I will), we'll definitely > be ahead. Ipfilter is a win for compatibilty/ubiquity, and seems to be > faster than ipfw anyway. Are there any technical arguments against > ipfilter or for ipfw? Note that: political arguments do not count, a > conversion method will be available for ipfw users, and we should have > anything special (DummyNet, uid/gid-based filtering) ported over to > ipfilter. I don't have a position on ipfw vs. ipfilter. As long as no functionality is lost, I don't see any problems changing. -- 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 Sat Jun 19 7:40:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sol (cs1-gw.cs.binghamton.edu [128.226.171.72]) by hub.freebsd.org (Postfix) with SMTP id 8E9CF14E18 for ; Sat, 19 Jun 1999 07:40:52 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from localhost (zzhang@localhost) by sol (SMI-8.6/8.6.9) with SMTP id KAA03164 for ; Sat, 19 Jun 1999 10:29:08 -0400 Date: Sat, 19 Jun 1999 10:29:07 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: What does VOP_FREEBLKS() do? 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 find in the routine ffs_blkfree() there is a new statement saying: VOP_FREEBLKS(ip->i_devvp, fsbtodb(fs, bno), size); which calls spec_freeblks() in file spec_vnops.c. The routine spec_freeblks() looks simple. When D_CANFREE is set, it gets an empty buffer and call strategy routine for the buffer. Since B_READ is not set, we must call the strategy routine to write some data. But where is the data for the buffer? Why we call VOP_FREEBLKS() at the time we are going to free the blocks? BTW, this vnode operation is not listed in the man pages. Any help is appreciated. -------------------------------------------------- Zhihui Zhang. Please visit 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 Jun 19 7:52:11 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 810B014BDD; Sat, 19 Jun 1999 07:52: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 QAA89155; Sat, 19 Jun 1999 16:52:00 +0200 (CEST) (envelope-from des) To: "Brian F. Feldman" Cc: Doug Rabson , Dag-Erling Smorgrav , Ruslan Ermilov , ugen@xonix.com, hackers@FreeBSD.org, luigi@FreeBSD.org Subject: Re: Introduction References: From: Dag-Erling Smorgrav Date: 19 Jun 1999 16:51:59 +0200 In-Reply-To: "Brian F. Feldman"'s message of "Sat, 19 Jun 1999 10:22:23 -0400 (EDT)" Message-ID: Lines: 19 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Brian F. Feldman" writes: > It might be worth (discussion of) making ipfilter the firewall of > choice for 4.0. There would of course be rule conversion > scripts/programs (ipfw->ipf(5)), and ipfilter would be converted to > a KLD, cruft removed (I'm going to work on these), and ipfilter KLD > support (currently options IPFILTER_LKM) made a non-option. It seems > that our pretty proprietary ipfw is no longer a good idea. If ipfilter can to everything ipfw can (judging from ipf(5), it can) and you even manage to keep an ipfw(8) command around so those who want kan keep using the old syntax still can, then I for one have no objections. Rewriting ipfw rules to ipfilter rules on the fly should be trivial; a simple Perl script should be sufficient. 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 Sat Jun 19 7:57:41 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 851FF14BDD; Sat, 19 Jun 1999 07:57:36 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id PAA81256; Sat, 19 Jun 1999 15:58:30 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 19 Jun 1999 15:58:30 +0100 (BST) From: Doug Rabson To: Dag-Erling Smorgrav Cc: "Brian F. Feldman" , Ruslan Ermilov , ugen@xonix.com, hackers@FreeBSD.org, luigi@FreeBSD.org Subject: Re: Introduction 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 Jun 1999, Dag-Erling Smorgrav wrote: > "Brian F. Feldman" writes: > > It might be worth (discussion of) making ipfilter the firewall of > > choice for 4.0. There would of course be rule conversion > > scripts/programs (ipfw->ipf(5)), and ipfilter would be converted to > > a KLD, cruft removed (I'm going to work on these), and ipfilter KLD > > support (currently options IPFILTER_LKM) made a non-option. It seems > > that our pretty proprietary ipfw is no longer a good idea. > > If ipfilter can to everything ipfw can (judging from ipf(5), it can) > and you even manage to keep an ipfw(8) command around so those who > want kan keep using the old syntax still can, then I for one have no > objections. > > Rewriting ipfw rules to ipfilter rules on the fly should be trivial; a > simple Perl script should be sufficient. Does ipfilter support divert sockets? -- 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 Sat Jun 19 8:14:38 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 42ED814EBD; Sat, 19 Jun 1999 08:14:35 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id LAA00757; Sat, 19 Jun 1999 11:13:32 -0400 (EDT) Date: Sat, 19 Jun 1999 11:12:07 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Dag-Erling Smorgrav Cc: Doug Rabson , Ruslan Ermilov , ugen@xonix.com, hackers@FreeBSD.org, luigi@FreeBSD.org Subject: Firewalls (was Re: Introduction) 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 Jun 1999, Dag-Erling Smorgrav wrote: > "Brian F. Feldman" writes: > > It might be worth (discussion of) making ipfilter the firewall of > > choice for 4.0. There would of course be rule conversion > > scripts/programs (ipfw->ipf(5)), and ipfilter would be converted to > > a KLD, cruft removed (I'm going to work on these), and ipfilter KLD > > support (currently options IPFILTER_LKM) made a non-option. It seems > > that our pretty proprietary ipfw is no longer a good idea. > > If ipfilter can to everything ipfw can (judging from ipf(5), it can) > and you even manage to keep an ipfw(8) command around so those who > want kan keep using the old syntax still can, then I for one have no > objections. > > Rewriting ipfw rules to ipfilter rules on the fly should be trivial; a > simple Perl script should be sufficient. Not quite as trivial as you think. ipfw and ipf are completely backwards when it comes to rule order: in ipfw, the first rule matched takes effect; in ipf, the last rule matched takes effect. Plus, ipf doesn't have rule numbers (but there's similar functionailty.) If you think you can get used to them both enough to tackle this, I'll handle other things, and we can have a working replacement for crufty old ipfw. Note that Luigi's extra ipfw functionality and my extra ipfw functionality _will_ be wanted in ipf before everyone is necessarily willing to switch. I have a feeling there will be some holdouts that, even if ipfw is removed, they'll MFS (merge from stable) ipfw back just because they want to keep the old way. Ipfw could be dead for 4.0-RELEASE, as I see it now. More discussion is, however, necessary. > > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no > 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 Jun 19 8:26:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from osgroup.com (unknown [38.229.41.6]) by hub.freebsd.org (Postfix) with ESMTP id 296551517D for ; Sat, 19 Jun 1999 08:26:34 -0700 (PDT) (envelope-from stan@osgroup.com) Received: from stan166 ([38.229.41.237]) by osgroup.com (8.7.6/8.6.12) with SMTP id KAA15113 for ; Sat, 19 Jun 1999 10:15:26 -0500 Received: by localhost with Microsoft MAPI; Sat, 19 Jun 1999 10:28:13 -0500 Message-ID: <01BEBA3E.6F913AC0.stan@osgroup.com> From: Constantine Shkolny Reply-To: "stan@osgroup.com" To: "hackers@FreeBSD.ORG" Subject: ipfilter (was: RE: Introduction) Date: Sat, 19 Jun 1999 10:28:12 -0500 Organization: Ashley Laurent, Inc. X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 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 All, I'm now analyzing ipfilter in 3.2 and our goal is to port our IPSec/firewall. I'm still in the beginning of reading the code so, at this time, I can't yet tell how nice it fits our needs. I just have some concerns which I'd like the people who are going to re-design the ipfilter to hear. I wouldn't be surprised to learn that you are already thinking about this, however, it's nice to know it for certain :-) The things in the IPSec field are seemingly moving to using hardware accelerators for doing compression/encryption/authentication. This means that IP filters need to grab some of IP packets, process them on a specialized prosessor and then re-inject them into the IP packet stream. That is, the filter may decide to convert the packet, but it doesn't have it ready-to-go when it has to return. However, it may have it ready at some later time, possibly when it processes a hardware interrupt and sees that the co-processor has finished its work on the packet. Can ipfilter handle this? Thank you, Stan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 8:26:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rose.niw.com.au (app3022-2.gw.connect.com.au [203.63.119.4]) by hub.freebsd.org (Postfix) with ESMTP id 31430152E5; Sat, 19 Jun 1999 08:26:45 -0700 (PDT) (envelope-from ian@niw.com.au) Received: by rose.niw.com.au (Postfix, from userid 1000) id 8E68DA3240; Sun, 20 Jun 1999 00:56:44 +0930 (CST) Date: Sun, 20 Jun 1999 00:56:44 +0930 From: Ian West To: "Brian F. Feldman" Cc: Dag-Erling Smorgrav , Doug Rabson , Ruslan Ermilov , ugen@xonix.com, hackers@FreeBSD.org, luigi@FreeBSD.org Subject: Re: Firewalls (was Re: Introduction) Message-ID: <19990620005644.C29104@rose.niw.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Brian F. Feldman on Sat, Jun 19, 1999 at 11:12:07AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jun 19, 1999 at 11:12:07AM -0400, Brian F. Feldman wrote: > On 19 Jun 1999, Dag-Erling Smorgrav wrote: > > > "Brian F. Feldman" writes: > > > It might be worth (discussion of) making ipfilter the firewall of > > > choice for 4.0. There would of course be rule conversion > > > scripts/programs (ipfw->ipf(5)), and ipfilter would be converted to > > > a KLD, cruft removed (I'm going to work on these), and ipfilter KLD > > > support (currently options IPFILTER_LKM) made a non-option. It seems > > > that our pretty proprietary ipfw is no longer a good idea. > > > > If ipfilter can to everything ipfw can (judging from ipf(5), it can) > > and you even manage to keep an ipfw(8) command around so those who > > want kan keep using the old syntax still can, then I for one have no > > objections. > > > > Rewriting ipfw rules to ipfilter rules on the fly should be trivial; a > > simple Perl script should be sufficient. > > Not quite as trivial as you think. ipfw and ipf are completely backwards when it comes > to rule order: in ipfw, the first rule matched takes effect; in ipf, the last rule matched > takes effect. Plus, ipf doesn't have rule numbers (but there's similar functionailty.) > If you think you can get used to them both enough to tackle this, I'll handle other > things, and we can have a working replacement for crufty old ipfw. Note that Luigi's > extra ipfw functionality and my extra ipfw functionality _will_ be wanted in ipf > before everyone is necessarily willing to switch. I have a feeling there will be some > holdouts that, even if ipfw is removed, they'll MFS (merge from stable) ipfw back just > because they want to keep the old way. Ipfw could be dead for 4.0-RELEASE, as I see it > now. More discussion is, however, necessary. > > > > > DES > > -- > > Dag-Erling Smorgrav - des@flood.ping.uio.no > > > > 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 Does ip filter now support per interface filtering based on an ip address, not an interface name ? This was the limitation I encountered last time I looked at it. Ran up against a few problems getting it to run nicely with user-ppp. (Can't remember how long ago that was exactly though, it may be fixed now, if so please ignore this :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 8:29: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 E46E514EBD; Sat, 19 Jun 1999 08:29:42 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id LAA01009; Sat, 19 Jun 1999 11:29:05 -0400 (EDT) Date: Sat, 19 Jun 1999 11:27:40 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Doug Rabson Cc: Dag-Erling Smorgrav , Ruslan Ermilov , ugen@xonix.com, hackers@FreeBSD.org, luigi@FreeBSD.org Subject: Re: Introduction 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, 19 Jun 1999, Doug Rabson wrote: > On 19 Jun 1999, Dag-Erling Smorgrav wrote: > > > "Brian F. Feldman" writes: > > > It might be worth (discussion of) making ipfilter the firewall of > > > choice for 4.0. There would of course be rule conversion > > > scripts/programs (ipfw->ipf(5)), and ipfilter would be converted to > > > a KLD, cruft removed (I'm going to work on these), and ipfilter KLD > > > support (currently options IPFILTER_LKM) made a non-option. It seems > > > that our pretty proprietary ipfw is no longer a good idea. > > > > If ipfilter can to everything ipfw can (judging from ipf(5), it can) > > and you even manage to keep an ipfw(8) command around so those who > > want kan keep using the old syntax still can, then I for one have no > > objections. > > > > Rewriting ipfw rules to ipfilter rules on the fly should be trivial; a > > simple Perl script should be sufficient. > > Does ipfilter support divert sockets? It still needs: divert sockets Luigi's stuff (dummynet and bridging) my stuff > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > 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 Jun 19 8:30:58 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 C8B5315323; Sat, 19 Jun 1999 08:30:16 -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 RAA90072; Sat, 19 Jun 1999 17:30:13 +0200 (CEST) (envelope-from des) To: "Brian F. Feldman" Cc: Dag-Erling Smorgrav , Doug Rabson , Ruslan Ermilov , ugen@xonix.com, hackers@FreeBSD.org, luigi@FreeBSD.org Subject: Re: Firewalls (was Re: Introduction) References: From: Dag-Erling Smorgrav Date: 19 Jun 1999 17:30:13 +0200 In-Reply-To: "Brian F. Feldman"'s message of "Sat, 19 Jun 1999 11:12:07 -0400 (EDT)" Message-ID: Lines: 20 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Brian F. Feldman" writes: > On 19 Jun 1999, Dag-Erling Smorgrav wrote: > > Rewriting ipfw rules to ipfilter rules on the fly should be trivial; a > > simple Perl script should be sufficient. > Not quite as trivial as you think. ipfw and ipf are completely backwards when it comes > to rule order: in ipfw, the first rule matched takes effect; in ipf, the last rule matched > takes effect. Just throw in 'quick' and ipfilter behaves just like ipfw. > Note that Luigi's > extra ipfw functionality and my extra ipfw functionality _will_ be wanted in ipf > before everyone is necessarily willing to switch. Divert sockets, dummynet and credential-based filtering would be sorely missed if they weren't ported to ipfilter. 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 Sat Jun 19 9: 2: 7 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 3036A152B2 for ; Sat, 19 Jun 1999 09:02:04 -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 MAA10374 for ; Sat, 19 Jun 1999 12:02:26 -0400 (EDT) Message-Id: <199906191602.MAA10374@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 19 Jun 1999 10:54:38 -0400 To: hackers@freebsd.org From: Dennis Subject: Changing Bootmgr display Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've bog F1: FreeBSD F2: LINUX F3: FreeBSD F3 is a non-bootable file system...is there a way to get the boot manager to only display F1 and F2? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 9:43:15 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 8AE3B14F5C for ; Sat, 19 Jun 1999 09:43:11 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 19 Jun 99 17:43:10 +0100 (BST) To: Khetan Gajjar Cc: freebsd-hackers@freebsd.org Subject: Re: Inetd and wrapping. In-reply-to: Your message of "Fri, 18 Jun 1999 23:58:12 +0200." X-Request-Do: Date: Sat, 19 Jun 1999 17:43:10 +0100 From: David Malone Message-ID: <9906191743.aa07126@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The support (after the patches Sheldon brought in) now is > pretty good; is there any reason why the existing functionality should be > extended ? We should support atleast as much as tcpd did. I think the only thing we're missing now is wrapping the first connection of a udp/wait service and then inetd can do as much as tcpd could. (Wrapping of internal services is a bonus over what tcpd can do already). I'd be happy with just adding support for wrapping udp stuff and adding a command line flag which turns off wrapping to keep purists happy. I just wanted to see what the general opinion was. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 9:57: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from medulla.hippocampus.net (medulla.hippocampus.net [204.138.241.6]) by hub.freebsd.org (Postfix) with ESMTP id 6D5B314D97 for ; Sat, 19 Jun 1999 09:56:54 -0700 (PDT) (envelope-from marc@netstor.com) Received: from localhost (marc@localhost) by medulla.hippocampus.net (8.9.2/8.9.2) with ESMTP id NAA16701; Sat, 19 Jun 1999 13:03:10 -0400 (EDT) Date: Sat, 19 Jun 1999 13:03:10 -0400 (EDT) From: Marc Nicholas X-Sender: marc@medulla.hippocampus.net To: Pat Lynch Cc: hackers@FreeBSD.ORG Subject: Re: SMP and Celerons... 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 Hmmm...I always thought there was something "broke" inside Celerons to prevent SMP...maybe I'm wrong? Sure would be neat if you could run them SMP... -marc ---------------------------------------------------------------- Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com "Fast, Expandable and Affordable Internet Caching Products" 1.877.464.4776 416.979.9000 fax: 416.979.8223 cell: 416.346.9255 On Fri, 18 Jun 1999, Pat Lynch wrote: > Heya, sorry I tried this one on -stable and -questions and noone seems to > know, and they actually go so far as to ask me how I got two celerons in a > motherboard... > > so I ask here. > > I have two PPGA(Socket 370) Celeron 333A's that are on MSI6905 Dual Socket > 1 adaptors... > > a Tyan Thunder 2 motherboard (onboard scsi, sound, etc.) > > I boot an SMP kernel, it gets right past autoboot... then panics > > the message was that it "could not find local apic"... > > its kinda strange because essentially with these adaptors, the celerons > should be 1) SMP capable, and 2) the same as a PII, except no L2 cache > > I know others that ran FreeBSD SMP with celerons... anyone know if theres > some kind of patch I need or modification I have to make to get either > -CURRENT or -STABLE working on this machine? Right now it is running a UP > kernel instead of the SMP one and runs fine. > > -Pat > > ___________________________________________________________________________ > > Pat Lynch lynch@rush.net > lynch@bsdunix.net > Systems Administrator Rush Networking > ___________________________________________________________________________ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 9:59:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ceia.nordier.com (m2-31-dbn.dial-up.net [196.34.155.95]) by hub.freebsd.org (Postfix) with ESMTP id 0630614D97 for ; Sat, 19 Jun 1999 09:59:15 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id SAA01909; Sat, 19 Jun 1999 18:58:25 +0200 (SAST) From: Robert Nordier Message-Id: <199906191658.SAA01909@ceia.nordier.com> Subject: Re: Changing Bootmgr display In-Reply-To: <199906191602.MAA10374@etinc.com> from Dennis at "Jun 19, 1999 10:54:38 am" To: dennis@etinc.com (Dennis) Date: Sat, 19 Jun 1999 18:58:23 +0200 (SAST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > F1: FreeBSD > F2: LINUX > F3: FreeBSD > > F3 is a non-bootable file system...is there a way to get the boot manager > to only display F1 and F2? At the moment, no. Though you could use the following patch, which allows the slices to be individually disabled. (The B0FLAGS setting in Makefile enables slices 1 and 2; use B0FLAGS=0xf to enable all four slices.) If worthwhile, boot0cfg(8) can later be modified to set/unset the flags, rather than using a build option. Note that the patch is against boot0.s rev 1.9 committed yesterday. -- Robert Nordier --- Makefile.orig Sat Jun 19 18:48:42 1999 +++ Makefile Sat Jun 19 18:43:07 1999 @@ -8,7 +8,7 @@ M4?= m4 -B0FLAGS=0x0 +B0FLAGS=0x3 B0TICKS=0xb6 ORG= 0x600 --- boot0.s.orig Sat Jun 19 18:51:10 1999 +++ boot0.s Sat Jun 19 18:51:21 1999 @@ -71,6 +71,8 @@ movwir(partbl+0x4,_bx) # Partition table xorl %edx,%edx # Item number main.3: movbr1(_ch,-0x4,_bx_) # Zero active flag + btwr1(_dx,_FLAGS,_bp_) # Entry enabled? + jnc main.5 # No movb0r(_bx_,_al) # Load type movwir(tables,_di) # Lookup tables movb $TBL0SZ,%cl # Number of entries To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 10: 5:34 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 A380414D97 for ; Sat, 19 Jun 1999 10:05:31 -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 LAA63335; Sat, 19 Jun 1999 11:05:30 -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 LAA86038; Sat, 19 Jun 1999 11:06:07 -0600 (MDT) Message-Id: <199906191706.LAA86038@harmony.village.org> To: Dennis Subject: Re: Changing Bootmgr display Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 19 Jun 1999 10:54:38 EDT." <199906191602.MAA10374@etinc.com> References: <199906191602.MAA10374@etinc.com> Date: Sat, 19 Jun 1999 11:06:07 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199906191602.MAA10374@etinc.com> Dennis writes: : F3 is a non-bootable file system...is there a way to get the boot manager : to only display F1 and F2? More generally, I'd like my Win98 partition to be identified as Win98, not ????. Also, is there a list of partition types to ignore somehwere? My suspend partition also shows up as ????. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 10: 7: 3 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 381E414D97 for ; Sat, 19 Jun 1999 10:07: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 LAA63346; Sat, 19 Jun 1999 11:06:59 -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 LAA86070; Sat, 19 Jun 1999 11:07:36 -0600 (MDT) Message-Id: <199906191707.LAA86070@harmony.village.org> To: Marc Nicholas Subject: Re: SMP and Celerons... Cc: Pat Lynch , hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 19 Jun 1999 13:03:10 EDT." References: Date: Sat, 19 Jun 1999 11:07:36 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Marc Nicholas writes: : Hmmm...I always thought there was something "broke" inside Celerons to : prevent SMP...maybe I'm wrong? Sure would be neat if you could run them : SMP... What is "broke" about the Celerons is their cache. Without a good cache sharing, you can't get good SMP performance. While you can run a SMP Celeron machine, it won't scale as well as the PII version of the chip. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 10:31:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from argus.tfs.net (host1-126.birch.net [216.212.1.126]) by hub.freebsd.org (Postfix) with ESMTP id 103C014E77 for ; Sat, 19 Jun 1999 10:31:16 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id MAA26402; Sat, 19 Jun 1999 12:29:54 -0500 (CDT) From: Jim Bryant Message-Id: <199906191729.MAA26402@argus.tfs.net> Subject: Re: KNE40BT in freebsd only getting 45KB/sec ftp transfer to win98 machine In-Reply-To: <376B4C20.EDE2C8BF@tpgi.com.au> from Eddie Irvine at "Jun 19, 99 05:52:00 pm" To: eirvine@tpgi.com.au (Eddie Irvine) Date: Sat, 19 Jun 1999 12:29:53 -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 duplex should work fine in a 2 machine point to point without a switch. In reply: > Hi, > > Speed in what protocol? FTP? SMB? Appletalk? > > Have you checked the duplexing of cards on both > machines? Use the DOS program that came with the > ethernet cards to check. Unless your card is > connected directly to a switch, it should be > half duplex (I'm not sure on this, but that > is my understanding). > > > Jim Bryant wrote: > > > > In reply: > > > I am running FreeBSD-current and for some reason I am only > > > getting~45KB/sec > > > transfer to a computer running Windows 98. I have a Kingston > > > KNE40BTcard and I > > > can find no hardware error as to why I am only reaching those speeds. > > > Could you suggest what may be the error? > > > > > > Andrew Tamm > > > > ummmmmmm.. winblowz-98. 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 Sat Jun 19 10:53:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ceia.nordier.com (m1-11-dbn.dial-up.net [196.34.155.11]) by hub.freebsd.org (Postfix) with ESMTP id 6353D14E25 for ; Sat, 19 Jun 1999 10:53:25 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id TAA02512; Sat, 19 Jun 1999 19:52:24 +0200 (SAST) From: Robert Nordier Message-Id: <199906191752.TAA02512@ceia.nordier.com> Subject: Re: Changing Bootmgr display In-Reply-To: <199906191706.LAA86038@harmony.village.org> from Warner Losh at "Jun 19, 1999 11:06:07 am" To: imp@harmony.village.org (Warner Losh) Date: Sat, 19 Jun 1999 19:52:21 +0200 (SAST) Cc: dennis@etinc.com (Dennis), 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 Warner Losh wrote: > In message <199906191602.MAA10374@etinc.com> Dennis writes: > : F3 is a non-bootable file system...is there a way to get the boot manager > : to only display F1 and F2? > > More generally, I'd like my Win98 partition to be identified as Win98, > not ????. Also, is there a list of partition types to ignore > somehwere? My suspend partition also shows up as ????. The present boot manager is limited in size to 446 bytes, so there's just not space to provide an adequate list of known partitions. The best solution is probably to customise the sources or use a "proper" boot manager. (I see that at the FreeBSD Mall, they're offering Partition Magic and System Commander with FreeBSD.) To ignore a partition by type, see the following patch as an example (we ignore type 0x42). -- Robert Nordier --- boot0.s.orig Sat Jun 19 19:50:23 1999 +++ boot0.s Sat Jun 19 19:50:44 1999 @@ -24,7 +24,7 @@ .set PRT_OFF,0x1be # Partition table - .set TBL0SZ,0x3 # Table 0 size + .set TBL0SZ,0x4 # Table 0 size .set TBL1SZ,0xa # Table 1 size .set MAGIC,0xaa55 # Magic: bootable @@ -231,7 +231,7 @@ # Partition type tables tables: - .byte 0x0, 0x5, 0xf + .byte 0x0, 0x5, 0xf, 0x42 .byte 0x1, 0x4, 0x6, 0xb, 0xc, 0xe, 0x63, 0x83 .byte 0xa5, 0xa6 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 11: 4: 9 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 6433414BFA; Sat, 19 Jun 1999 11:03:59 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id OAA03543; Sat, 19 Jun 1999 14:03:33 -0400 (EDT) Date: Sat, 19 Jun 1999 14:02:08 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Dag-Erling Smorgrav Cc: Doug Rabson , Ruslan Ermilov , ugen@xonix.com, hackers@FreeBSD.org, luigi@FreeBSD.org Subject: Re: Firewalls (was Re: Introduction) 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 Jun 1999, Dag-Erling Smorgrav wrote: > "Brian F. Feldman" writes: > > On 19 Jun 1999, Dag-Erling Smorgrav wrote: > > > Rewriting ipfw rules to ipfilter rules on the fly should be trivial; a > > > simple Perl script should be sufficient. > > Not quite as trivial as you think. ipfw and ipf are completely backwards when it comes > > to rule order: in ipfw, the first rule matched takes effect; in ipf, the last rule matched > > takes effect. > > Just throw in 'quick' and ipfilter behaves just like ipfw. I figured that out. Come to think of it, I rather like "quick" much better than ipf's default way. > > > Note that Luigi's > > extra ipfw functionality and my extra ipfw functionality _will_ be wanted in ipf > > before everyone is necessarily willing to switch. > > Divert sockets, dummynet and credential-based filtering would be > sorely missed if they weren't ported to ipfilter. Definitely. Working on ipfilter is probably better than reinventing the wheel again. > > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no > 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 Jun 19 11:28: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp4.erols.com (smtp4.erols.com [207.172.3.237]) by hub.freebsd.org (Postfix) with ESMTP id A243714D3D for ; Sat, 19 Jun 1999 11:28:06 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (207-172-143-245.s54.as3.hgt.md.dialup.rcn.com [207.172.143.245]) by smtp4.erols.com (8.8.8/smtp-v1) with ESMTP id OAA23635; Sat, 19 Jun 1999 14:28:01 -0400 (EDT) Message-Id: <199906191828.OAA23635@smtp4.erols.com> 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: <199906191706.LAA86038@harmony.village.org> Date: Sat, 19 Jun 1999 14:26:52 -0400 (EDT) From: John Baldwin To: Warner Losh Subject: Re: Changing Bootmgr display Cc: hackers@FreeBSD.ORG, Dennis Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Jun-99 Warner Losh wrote: > In message <199906191602.MAA10374@etinc.com> Dennis writes: >: F3 is a non-bootable file system...is there a way to get the boot manager >: to only display F1 and F2? > > More generally, I'd like my Win98 partition to be identified as Win98, > not ????. Also, is there a list of partition types to ignore > somehwere? My suspend partition also shows up as ????. > > Warner Then don't use BootEasy. The OS-BS boot manager is quite nice, and the beta version (which seems very stable in my experience) even provides a nice colorful menu on boot up as well as a nice installation utility. And with that you can name each partition whatever you want, put them in any order, and optionally have a default partition to boot to. --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 11:53: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pallas.veritas.com (pallas.veritas.com [204.177.156.25]) by hub.freebsd.org (Postfix) with ESMTP id 5865314CB6 for ; Sat, 19 Jun 1999 11:53:01 -0700 (PDT) (envelope-from aaron@sigma.veritas.com) Received: from megami.veritas.com (megami.veritas.com [192.203.46.101]) by pallas.veritas.com (8.9.1a/8.9.1) with SMTP id LAA01804; Sat, 19 Jun 1999 11:53:40 -0700 (PDT) Received: from sigma.veritas.com([192.203.46.125]) (1437 bytes) by megami.veritas.com via sendmail with P:esmtp/R:smart_host/T:smtp (sender: ) id for ; Sat, 19 Jun 1999 11:52:54 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #3 built 1999-Jan-25) Received: from sigma (localhost [127.0.0.1]) by sigma.veritas.com (8.9.2/8.9.1) with ESMTP id LAA94369; Sat, 19 Jun 1999 11:52:54 -0700 (PDT) (envelope-from aaron@sigma.veritas.com) Message-Id: <199906191852.LAA94369@sigma.veritas.com> From: Aaron Smith To: John Baldwin Cc: Warner Losh , hackers@FreeBSD.ORG, Dennis Subject: Re: Changing Bootmgr display In-reply-to: Your message of "Sat, 19 Jun 1999 14:26:52 EDT." <199906191828.OAA23635@smtp4.erols.com> Date: Sat, 19 Jun 1999 11:52:54 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Jun 1999 14:26:52 EDT, John Baldwin writes: >Then don't use BootEasy. The OS-BS boot manager is quite nice, and the beta >version (which seems very stable in my experience) even provides a nice >colorful menu on boot up as well as a nice installation utility. > >And with that you can name each partition whatever you want, put them in any >order, and optionally have a default partition to boot to. LILO's an option too, right? Is no one mentioning it for some incompatibility I don't know about (I haven't used it with FreeBSD), or is the reason political? Aaron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 12:14:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.erols.com (smtp1.erols.com [207.172.3.234]) by hub.freebsd.org (Postfix) with ESMTP id 25D2514C4B for ; Sat, 19 Jun 1999 12:14:46 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (207-172-143-141.s14.as2.hgt.md.dialup.rcn.com [207.172.143.141]) by smtp1.erols.com (8.8.8/8.8.5) with ESMTP id PAA02939; Sat, 19 Jun 1999 15:14:40 -0400 (EDT) Message-Id: <199906191914.PAA02939@smtp1.erols.com> 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: <199906191852.LAA94369@sigma.veritas.com> Date: Sat, 19 Jun 1999 15:14:04 -0400 (EDT) From: John Baldwin To: Aaron Smith Subject: Re: Changing Bootmgr display Cc: Dennis , hackers@FreeBSD.ORG, Warner Losh , John Baldwin Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Jun-99 Aaron Smith wrote: > On Sat, 19 Jun 1999 14:26:52 EDT, John Baldwin writes: >>Then don't use BootEasy. The OS-BS boot manager is quite nice, and the beta >>version (which seems very stable in my experience) even provides a nice >>colorful menu on boot up as well as a nice installation utility. >> >>And with that you can name each partition whatever you want, put them in any >>order, and optionally have a default partition to boot to. > > LILO's an option too, right? Is no one mentioning it for some > incompatibility I don't know about (I haven't used it with FreeBSD), or is > the reason political? > > Aaron No, I just happen to use OS-BS in an environment of machines that dual boot NT and FreeBSD. (And my machine which dual boots '95 and FreeBSD). I don't happen to use Linux, so I don't happen to use LILO. No politics there. Also, both BootEasy and OS-BS (stable and beta versions) come on the FreeBSD CD's, so I'd reccommend those to a FreeBSD user just because they are easy to get to (no 'net surfin' required) if they have the CD's. FWIW, OS-BS is a completely OS-independent project with no affiliation with FreeBSD, it just happens to be on the CD. (AFAIK) --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 12:47:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dhcp9545042.columbus.rr.com (dhcp9545042.columbus.rr.com [24.95.45.42]) by hub.freebsd.org (Postfix) with ESMTP id 2E151150EE for ; Sat, 19 Jun 1999 12:47:33 -0700 (PDT) (envelope-from rowland@dhcp9545042.columbus.rr.com) Received: (from rowland@localhost) by dhcp9545042.columbus.rr.com (8.9.3/8.9.3) id PAA88618; Sat, 19 Jun 1999 15:45:54 -0400 (EDT) (envelope-from rowland) To: Marc Nicholas Cc: hackers@FreeBSD.ORG Subject: Re: SMP and Celerons... References: X-Face: "<|%>c@Vfv/8}+Av1z:R5sDzf!3QVer!n\,.&+&h\k1,BHAoyw8Gp10<-SqZ<*"|!U!a#xg6ls?1,Vj$m@r?uHcfB,'i:LLgtyb;~}O8v7zZThuB`X~#IE{v*"PhI]cl/>&ys(MGa%y:6~TuHFw&~|V?!9HZ_R"<}dC5D:%igP2Q6ZJex,P0M From: Shaun Rowland Date: 19 Jun 1999 15:45:54 -0400 In-Reply-To: Marc Nicholas's message of "Sat, 19 Jun 1999 13:03:10 -0400 (EDT)" Message-ID: <87k8t0c6tp.fsf@dhcp9545042.columbus.rr.com> Lines: 15 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "20 Minutes to Nikko" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Nicholas writes: > Hmmm...I always thought there was something "broke" inside Celerons to > prevent SMP...maybe I'm wrong? Sure would be neat if you could run them > SMP... > > > -marc Well there is kind of. If you have a socket 370 adapter you can un-break it. I am currently running dual Celeron 400's, and they truly fly on this box! I can assure you it works without problems. -- Shaun Rowland rowland@cis.ohio-state.edu http://www.cis.ohio-state.edu/~rowland/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 12:57:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dhcp9545042.columbus.rr.com (dhcp9545042.columbus.rr.com [24.95.45.42]) by hub.freebsd.org (Postfix) with ESMTP id 1C6381534A for ; Sat, 19 Jun 1999 12:57:07 -0700 (PDT) (envelope-from rowland@dhcp9545042.columbus.rr.com) Received: (from rowland@localhost) by dhcp9545042.columbus.rr.com (8.9.3/8.9.3) id PAA88654; Sat, 19 Jun 1999 15:55:36 -0400 (EDT) (envelope-from rowland) To: Warner Losh Cc: Marc Nicholas , Pat Lynch , hackers@FreeBSD.ORG Subject: Re: SMP and Celerons... References: <199906191707.LAA86070@harmony.village.org> X-Face: "<|%>c@Vfv/8}+Av1z:R5sDzf!3QVer!n\,.&+&h\k1,BHAoyw8Gp10<-SqZ<*"|!U!a#xg6ls?1,Vj$m@r?uHcfB,'i:LLgtyb;~}O8v7zZThuB`X~#IE{v*"PhI]cl/>&ys(MGa%y:6~TuHFw&~|V?!9HZ_R"<}dC5D:%igP2Q6ZJex,P0M From: Shaun Rowland Date: 19 Jun 1999 15:55:36 -0400 In-Reply-To: Warner Losh's message of "Sat, 19 Jun 1999 11:07:36 -0600" Message-ID: <87hfo4c6dj.fsf@dhcp9545042.columbus.rr.com> Lines: 22 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "20 Minutes to Nikko" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh writes: > In message Marc Nicholas writes: > : Hmmm...I always thought there was something "broke" inside Celerons to > : prevent SMP...maybe I'm wrong? Sure would be neat if you could run them > : SMP... > > What is "broke" about the Celerons is their cache. Without a good > cache sharing, you can't get good SMP performance. While you can run > a SMP Celeron machine, it won't scale as well as the PII version of > the chip. > > Warner Do you mean the ones that don't have cache or the ones that have 128Kb cache on the chip? Is there that big of a hit of the cache is on the chip? I have seen some benchmarks and the system I have seemed to keep up well with a dual PII 400. I don't know how well it would scale though. -- Shaun Rowland rowland@cis.ohio-state.edu http://www.cis.ohio-state.edu/~rowland/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 14: 5:28 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 A416714FF6 for ; Sat, 19 Jun 1999 14:05:24 -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 RAA11285; Sat, 19 Jun 1999 17:05:48 -0400 (EDT) Message-Id: <199906192105.RAA11285@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 19 Jun 1999 15:58:04 -0400 To: Aaron Smith From: Dennis Subject: Re: Changing Bootmgr display Cc: hackers@freebsd.org In-Reply-To: <199906191852.LAA94369@sigma.veritas.com> 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 11:52 AM 6/19/99 -0700, you wrote: >On Sat, 19 Jun 1999 14:26:52 EDT, John Baldwin writes: >>Then don't use BootEasy. The OS-BS boot manager is quite nice, and the beta >>version (which seems very stable in my experience) even provides a nice >>colorful menu on boot up as well as a nice installation utility. >> >>And with that you can name each partition whatever you want, put them in any >>order, and optionally have a default partition to boot to. > >LILO's an option too, right? Is no one mentioning it for some >incompatibility I don't know about (I haven't used it with FreeBSD), or is >the reason political? The only objection I have to lilo is that is doesnt display a menu by default and you have to specify a default (unlike the "last-used" method of freebsd), which is a pain for systems that generally have no keyboard or monitor. DB > >Aaron > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 14:38:50 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 9E6DA15313; Sat, 19 Jun 1999 14:38:43 -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 OAA09312; Sat, 19 Jun 1999 14:36:54 -0700 (PDT) Message-Id: <199906192136.OAA09312@lestat.nas.nasa.gov> To: Dag-Erling Smorgrav Cc: "Brian F. Feldman" , Doug Rabson , Ruslan Ermilov , ugen@xonix.com, hackers@FreeBSD.ORG, luigi@FreeBSD.ORG Subject: Re: Firewalls (was Re: Introduction) Reply-To: Jason Thorpe From: Jason Thorpe Date: Sat, 19 Jun 1999 14:36:53 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19 Jun 1999 17:30:13 +0200 Dag-Erling Smorgrav wrote: > Divert sockets, dummynet and credential-based filtering would be > sorely missed if they weren't ported to ipfilter. ...but if they were ported to IP Filter, then lots of other systems could use them, too. -- 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 Sat Jun 19 15: 5:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.erols.com (smtp1.erols.com [207.172.3.234]) by hub.freebsd.org (Postfix) with ESMTP id EB5E114E99 for ; Sat, 19 Jun 1999 15:05:40 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (207-172-143-148.s21.as2.hgt.md.dialup.rcn.com [207.172.143.148]) by smtp1.erols.com (8.8.8/8.8.5) with ESMTP id SAA01316; Sat, 19 Jun 1999 18:05:36 -0400 (EDT) Message-Id: <199906192205.SAA01316@smtp1.erols.com> X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 19 Jun 1999 18:05:45 -0400 (EDT) From: John Baldwin To: kbyanc@alcnet.com, freebsd-hackers@freebsd.org Subject: Joystick support for Koules... Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In an effort to make FreeBSD even more (un)productive, I added in support for FreeBSD's joystick driver to Koules, a game which can be found in the ports collection at /usr/ports/games/koules. To compile the game with this patch follow this sequence: # cd /usr/ports/games/koules # make patch # cd work/koules-1.4 # fetch http://www.cslab.vt.edu/~jobaldwi/koules-bsdjoy.tgz # mkdir temp # tar xvfzC koules-bsdjoy.tgz temp/ # patch client.c < temp/client.c.patch # patch koules.c < temp/koules.c.patch # patch koules.h < temp/koules.h.patch # patch menu.c < temp/menu.c.patch # patch xlib/init.c < temp/xlib_init.c.patch # cp temp/freebsd_joystick.h . Edit Iconfig and uncomment the '#define JOYSTICK' line, then cd back to /usr/ports/games/koules, and 'make install' as usual. One problem so far: it doesn't detect to make sure a joystick is at a port. Please send any suggestions, comments, etc. as I'd like to get this tested on more than just my box before I send it to the author as the authoritative FreeBSD joystick support. :) --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 15:19: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bytor.rush.net (bytor.rush.net [209.45.245.145]) by hub.freebsd.org (Postfix) with ESMTP id B093F15339 for ; Sat, 19 Jun 1999 15:18:52 -0700 (PDT) (envelope-from lynch@bsdunix.net) Received: from localhost (lynch@localhost) by bytor.rush.net (8.9.3/8.9.3) with ESMTP id SAA29715; Sat, 19 Jun 1999 18:18:37 -0400 (EDT) Date: Sat, 19 Jun 1999 18:18:37 -0400 (EDT) From: Pat Lynch X-Sender: lynch@bytor.rush.net To: Shaun Rowland Cc: Marc Nicholas , hackers@FreeBSD.ORG Subject: Re: SMP and Celerons... In-Reply-To: <87k8t0c6tp.fsf@dhcp9545042.columbus.rr.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 Wish that was the case for me, might just be my momboard.... ___________________________________________________________________________ Pat Lynch lynch@rush.net lynch@bsdunix.net Systems Administrator Rush Networking ___________________________________________________________________________ On 19 Jun 1999, Shaun Rowland wrote: > Marc Nicholas writes: > > > Hmmm...I always thought there was something "broke" inside Celerons to > > prevent SMP...maybe I'm wrong? Sure would be neat if you could run them > > SMP... > > > > > > -marc > > Well there is kind of. If you have a socket 370 adapter you can > un-break it. I am currently running dual Celeron 400's, and they > truly fly on this box! I can assure you it works without problems. > -- > Shaun Rowland rowland@cis.ohio-state.edu > http://www.cis.ohio-state.edu/~rowland/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 15:19:55 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 B4A1715313 for ; Sat, 19 Jun 1999 15:19:50 -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 SAA11474; Sat, 19 Jun 1999 18:20:14 -0400 (EDT) Message-Id: <199906192220.SAA11474@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 19 Jun 1999 17:12:28 -0400 To: John Baldwin From: Dennis Subject: Re: Changing Bootmgr display Cc: hackers@freebsd.org In-Reply-To: <199906192205.SAA22343@smtp4.erols.com> References: <199906192107.RAA11294@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Will it allow you to 1) specify which partitions appear on the menu (ie, eliminate non-bootables) and 2) set the partition last selected to the default/active partition? Dennis At 06:05 PM 6/19/99 -0400, you wrote: > >On 19-Jun-99 Dennis wrote: >> At 03:14 PM 6/19/99 -0400, you wrote: >>> >>>On 19-Jun-99 Aaron Smith wrote: >>>> On Sat, 19 Jun 1999 14:26:52 EDT, John Baldwin writes: >>>>>Then don't use BootEasy. The OS-BS boot manager is quite nice, and the >> beta >>>>>version (which seems very stable in my experience) even provides a nice >>>>>colorful menu on boot up as well as a nice installation utility. >>>>> >>>>>And with that you can name each partition whatever you want, put them in >> any >>>>>order, and optionally have a default partition to boot to. >>>> >>>> LILO's an option too, right? Is no one mentioning it for some >>>> incompatibility I don't know about (I haven't used it with FreeBSD), or is >>>> the reason political? >>>> >>>> Aaron >>> >>>No, I just happen to use OS-BS in an environment of machines that dual >> boot NT >>>and FreeBSD. (And my machine which dual boots '95 and FreeBSD). I don't >>>happen to use Linux, so I don't happen to use LILO. No politics there. >>> >>>Also, both BootEasy and OS-BS (stable and beta versions) come on the FreeBSD >>>CD's, so I'd reccommend those to a FreeBSD user just because they are easy to >>>get to (no 'net surfin' required) if they have the CD's. >>> >>>FWIW, OS-BS is a completely OS-independent project with no affiliation with >>>FreeBSD, it just happens to be on the CD. (AFAIK) >> >> And for those of use who dont use the CD method, where might we find it? >> Does it boot the "last used" OS or is there a specific default? > >ftp://ftp.freebsd.org/pub/FreeBSD/tools/{osbs135.exe|osbsbeta.exe} > >The osbsbeta.exe is the beta version. The stable version allows you to set >custom names for partitions, but I prefer the nice look of the beta version >myself. I'm not sure about the stable version, but the beta version allows you >to choose between having a set default or having the default be the 'last used' >OS. > >HTH. > >> Dennis > >--- > >John Baldwin -- http://members.freedomnet.com/~jbaldwin/ >PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc >"Power Users Use the Power to Serve!" - http://www.freebsd.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 15:48:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.erols.com (smtp2.erols.com [207.172.3.235]) by hub.freebsd.org (Postfix) with ESMTP id DBB941579A for ; Sat, 19 Jun 1999 15:47:47 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (207-172-143-145.s18.as2.hgt.md.dialup.rcn.com [207.172.143.145]) by smtp2.erols.com (8.8.8/8.8.5) with ESMTP id SAA25522; Sat, 19 Jun 1999 18:51:35 -0400 (EDT) Message-Id: <199906192251.SAA25522@smtp2.erols.com> 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: <199906192220.SAA11474@etinc.com> Date: Sat, 19 Jun 1999 18:47:49 -0400 (EDT) From: John Baldwin To: Dennis Subject: Re: Changing Bootmgr display Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Jun-99 Dennis wrote: > Will it allow you to > > 1) specify which partitions appear on the menu (ie, eliminate > non-bootables) and Yes. > 2) set the partition last selected to the default/active partition? Yes. > Dennis Sorry if I wasn't clear enough earlier. --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 15:55:31 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 A8C9C14A12 for ; Sat, 19 Jun 1999 15:55:14 -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 QAA63920; Sat, 19 Jun 1999 16:55:12 -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 QAA87149; Sat, 19 Jun 1999 16:55:52 -0600 (MDT) Message-Id: <199906192255.QAA87149@harmony.village.org> To: Shaun Rowland Subject: Re: SMP and Celerons... Cc: Marc Nicholas , hackers@FreeBSD.ORG In-reply-to: Your message of "19 Jun 1999 15:45:54 EDT." <87k8t0c6tp.fsf@dhcp9545042.columbus.rr.com> References: <87k8t0c6tp.fsf@dhcp9545042.columbus.rr.com> Date: Sat, 19 Jun 1999 16:55:51 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <87k8t0c6tp.fsf@dhcp9545042.columbus.rr.com> Shaun Rowland writes: : Well there is kind of. If you have a socket 370 adapter you can : un-break it. I am currently running dual Celeron 400's, and they : truly fly on this box! I can assure you it works without problems. By "broke" people mean that the celerons do not have a cache architecture that can efficiently handle SMP. So rather than getting close to a 2x (1.75) performance increase for 2 CPU, you get more like 1.5 or so due to cache coherency effects. In the MP world, this is really bad performance. It will work, but it scales poorly. I don't recall if this is due to reduce coherency functionality, or is just an artifact of cache sizes. You really want to have 1M or so of cache for CPUs in this class. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 15:57: 3 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 EB79714CFA for ; Sat, 19 Jun 1999 15:56:48 -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 QAA63928; Sat, 19 Jun 1999 16:56:46 -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 QAA87169; Sat, 19 Jun 1999 16:57:25 -0600 (MDT) Message-Id: <199906192257.QAA87169@harmony.village.org> To: Shaun Rowland Subject: Re: SMP and Celerons... Cc: Marc Nicholas , Pat Lynch , hackers@FreeBSD.ORG In-reply-to: Your message of "19 Jun 1999 15:55:36 EDT." <87hfo4c6dj.fsf@dhcp9545042.columbus.rr.com> References: <87hfo4c6dj.fsf@dhcp9545042.columbus.rr.com> <199906191707.LAA86070@harmony.village.org> Date: Sat, 19 Jun 1999 16:57:25 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <87hfo4c6dj.fsf@dhcp9545042.columbus.rr.com> Shaun Rowland writes: : Do you mean the ones that don't have cache or the ones that have 128Kb : cache on the chip? Is there that big of a hit of the cache is on the : chip? I have seen some benchmarks and the system I have seemed to : keep up well with a dual PII 400. I don't know how well it would : scale though. By broke, I mean that they don't scale well due to cache effects. I think it may just be a size thing, but it might also be a cache coherency protocol ineffeciencies as well. The articles I've seen show that for typical workloads, people with two celerons were getting in the 1.5x range, while people with PIIs were getting 1.8x or so. Warnr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 18:41: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 6FF6514D47 for ; Sat, 19 Jun 1999 18:41:36 -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 SAA97615; Sat, 19 Jun 1999 18:40:40 -0700 (PDT) Date: Sat, 19 Jun 1999 18:40:38 -0700 (PDT) From: Julian Elischer To: Brian Fundakowski Feldman Cc: Darren Reed , npp@distortion.dk, ru@ucb.crimea.ua, hackers@FreeBSD.ORG Subject: Re: firewalling (Was Re: Introduction) 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 We use IPFW to great effect in the interjet whatever we end up with had better have the same features or we can't use it.. 1/ simple to use programatic API 2/ Divert sockets are a MUST. We do a lot of our filtering in userland. 3/ The ability to branch the rules using 'skipto' (goto?) is used heavily and the goto optimisations are very important to our performance. 4/ The 'fwd' facility is also very important. 5/ Line numbers are crucial to the way we control rules in the product. 6/ the ability to log but not halt processing of a packet is also crucial. If you change the semantics of how rules interact, you could screw us. Maybe you should look at what BSDI have.. A bpf based filter for link layer, and a separate IP layer filter.. Also look at the DPF code from MIT (in the exokernel). If we are going to do a replacement we shouldn't junk ipfw for something of equivalent technology (ipf), but consider doing something like DPF which is truely revolutionary. DPF generates att addition time, Dynamically generated machine instructions for an optimal packet classifier. When you add a rule, it re-writes the machine code.. there are ports for several architectures and it's very portable. Making a tree of indivdually created DPF filters would lead to incredibly high processing rates of very complicated rules. If you are not going to go the whole hog, then better to leave things the way they are (but with some cleaning). Security mechanisms are not the things you want to futz with too much. WHile I agree that ipf is "standard in NetBSD and OpenBSD, ipfw is closer to the Linux ipfw and as such, it would be a better maketting plan to ether leave it as is or move more towards what they do or leave it much as it is.. the others are pretty irrelevant when it comes to market and especially when it comes to our share of it. After 23 years in this industry I've learned (it took a long time) that a working but not perfect feature is better than a perfect one if the perfect one has marketting drawbacks. The present system is real easy to understand and many people use it. Think REAL HARD before removing it. IPF can already beadded by those that want it. Don't screw over the project in your eagerness to do good. Having said that I know IPFW's weaknesses. Most of it comes from the fact that we are working "out of the correct layer" sometimes. I'd LOVE to see a good DPF implementation.... julian On Fri, 18 Jun 1999, Brian Fundakowski Feldman wrote: > On Sat, 19 Jun 1999, Darren Reed wrote: > > > In some email I received from Brian Fundakowski Feldman, sie wrote: > > > How do you feel about (after getting it fixed in -CURRENT) helping with > > > converting ipfw(8) to just a front-end to ipf? I think it's worth discussing > > > whether it's actually worth it to rewrite IPFW or just work on improving > > > ipfilter. (discussion moved to -hackers) > > > > I imagine they might be fighting words to some ;) As I see it, if you > > added hooks for divert to ipfilter in FreeBSD and maybe added the rule > > number bits (I *know* there are going to be people who'd just die without > > it) then I can't see why you'd need ipfw. I imagine that would be a hell > > of a lot less work than bringing the features of ipfilter into ipfw. > > > > It'd also be one of those steps forward in compatibility between the various > > BSDs... > > Yes, and I know it might take some work. I'd like to have something good be > the default in FreeBSD, and I feel that maybe if ipfilter can be brought > to the foreground well and made backward compatible (i.e. ipfw(8) to translate > (perl? /bin/sh? idunno)), it will be a winning thing. I'd of course like to > add UID/GID support to ipfilter like I did to IPFW (but didn't commit). > IPFW is nearing the end of its maintainable life. It needs a pretty large > rewrite or full replacement pretty soon. If we can get ipfilter in src/contrib > kept up-to-date and working, supplying a replacement for ipfw(8) as a front-end, > I don't see why ipfilter can't be the "FreeBSD firewall." > > > > > > Darren > > > > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 18:48:42 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 4E26614BE5; Sat, 19 Jun 1999 18:48:38 -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 SAA97735; Sat, 19 Jun 1999 18:47:23 -0700 (PDT) Date: Sat, 19 Jun 1999 18:47:22 -0700 (PDT) From: Julian Elischer To: "Brian F. Feldman" Cc: Doug Rabson , Dag-Erling Smorgrav , Ruslan Ermilov , ugen@xonix.com, hackers@FreeBSD.ORG, luigi@FreeBSD.ORG Subject: Re: Introduction 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, 19 Jun 1999, Brian F. Feldman wrote: > On Sat, 19 Jun 1999, Doug Rabson wrote: > > > On 19 Jun 1999, Dag-Erling Smorgrav wrote: > > > > > "Brian F. Feldman" writes: > > > > It might be worth (discussion of) making ipfilter the firewall of > > > > choice for 4.0. There would of course be rule conversion > > > > scripts/programs (ipfw->ipf(5)), and ipfilter would be converted to > > > > a KLD, cruft removed (I'm going to work on these), and ipfilter KLD > > > > support (currently options IPFILTER_LKM) made a non-option. It seems > > > > that our pretty proprietary ipfw is no longer a good idea. > > > > > > If ipfilter can to everything ipfw can (judging from ipf(5), it can) > > > and you even manage to keep an ipfw(8) command around so those who > > > want kan keep using the old syntax still can, then I for one have no > > > objections. > > > > > > Rewriting ipfw rules to ipfilter rules on the fly should be trivial; a > > > simple Perl script should be sufficient. > > > > Does ipfilter support divert sockets? > > It still needs: > divert sockets > Luigi's stuff (dummynet and bridging) > my stuff fwd stuff? > > > > > -- > > Doug Rabson Mail: dfr@nlsystems.com > > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > > > > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 18:52:53 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 E795514BE5; Sat, 19 Jun 1999 18:52:48 -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 SAA97843; Sat, 19 Jun 1999 18:52:24 -0700 (PDT) Date: Sat, 19 Jun 1999 18:52:23 -0700 (PDT) From: Julian Elischer To: "Brian F. Feldman" Cc: Dag-Erling Smorgrav , Doug Rabson , Ruslan Ermilov , ugen@xonix.com, hackers@FreeBSD.ORG, luigi@FreeBSD.ORG Subject: Re: Firewalls (was Re: Introduction) 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 As a contributor to ipfw, notice that I will be sticking my oar into the water when it comes to deleting it unless I'm very sure that the ipf stuff is better. Unless you're Danish you don't just get to delete bits of the tree without a lot of agreement, especially from those who are working on it.. (in this case luigi and I would both be extrememly interested). On Sat, 19 Jun 1999, Brian F. Feldman wrote: > On 19 Jun 1999, Dag-Erling Smorgrav wrote: > > > "Brian F. Feldman" writes: > > > It might be worth (discussion of) making ipfilter the firewall of > > > choice for 4.0. There would of course be rule conversion > > > scripts/programs (ipfw->ipf(5)), and ipfilter would be converted to > > > a KLD, cruft removed (I'm going to work on these), and ipfilter KLD > > > support (currently options IPFILTER_LKM) made a non-option. It seems > > > that our pretty proprietary ipfw is no longer a good idea. > > > > If ipfilter can to everything ipfw can (judging from ipf(5), it can) > > and you even manage to keep an ipfw(8) command around so those who > > want kan keep using the old syntax still can, then I for one have no > > objections. > > > > Rewriting ipfw rules to ipfilter rules on the fly should be trivial; a > > simple Perl script should be sufficient. > > Not quite as trivial as you think. ipfw and ipf are completely backwards when it comes > to rule order: in ipfw, the first rule matched takes effect; in ipf, the last rule matched > takes effect. Plus, ipf doesn't have rule numbers (but there's similar functionailty.) > If you think you can get used to them both enough to tackle this, I'll handle other > things, and we can have a working replacement for crufty old ipfw. Note that Luigi's > extra ipfw functionality and my extra ipfw functionality _will_ be wanted in ipf > before everyone is necessarily willing to switch. I have a feeling there will be some > holdouts that, even if ipfw is removed, they'll MFS (merge from stable) ipfw back just > because they want to keep the old way. Ipfw could be dead for 4.0-RELEASE, as I see it > now. More discussion is, however, necessary. > > > > > DES > > -- > > Dag-Erling Smorgrav - des@flood.ping.uio.no > > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 19: 5:56 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 C045814BE5; Sat, 19 Jun 1999 19:05:51 -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 TAA69118; Sat, 19 Jun 1999 19:06:24 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Julian Elischer Cc: "Brian F. Feldman" , Dag-Erling Smorgrav , Doug Rabson , Ruslan Ermilov , ugen@xonix.com, hackers@FreeBSD.ORG, luigi@FreeBSD.ORG Subject: Re: Firewalls (was Re: Introduction) In-reply-to: Your message of "Sat, 19 Jun 1999 18:52:23 PDT." Date: Sat, 19 Jun 1999 19:06:24 -0700 Message-ID: <69114.929844384@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > is better. Unless you're Danish you don't just get to delete bits of the s/Unless/Especially if/ :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 19 20:12: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 3869D14BF5; Sat, 19 Jun 1999 20:12:46 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id XAA11883; Sat, 19 Jun 1999 23:12:33 -0400 (EDT) Date: Sat, 19 Jun 1999 23:11:07 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Julian Elischer Cc: Doug Rabson , Dag-Erling Smorgrav , Ruslan Ermilov , ugen@xonix.com, hackers@FreeBSD.ORG, luigi@FreeBSD.ORG Subject: Re: Introduction 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 It has "fwd stuff" :) 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 Jun 19 20:15:48 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 78C6F14BF5; Sat, 19 Jun 1999 20:15:44 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id XAA11927; Sat, 19 Jun 1999 23:15:35 -0400 (EDT) Date: Sat, 19 Jun 1999 23:14:10 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Julian Elischer Cc: Dag-Erling Smorgrav , Doug Rabson , Ruslan Ermilov , ugen@xonix.com, hackers@FreeBSD.ORG, luigi@FreeBSD.ORG Subject: Re: Firewalls (was Re: Introduction) 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, 19 Jun 1999, Julian Elischer wrote: > As a contributor to ipfw, notice that I will be sticking my oar into the > water when it comes to deleting it unless I'm very sure that the ipf stuff > is better. Unless you're Danish you don't just get to delete bits of the > tree without a lot of agreement, especially from those who are working on > it.. (in this case luigi and I would both be extrememly interested). Deleting IPFW would be a _long_ time from now, if at all. What it looks like now is: 1. making ipf and ipfw equivalent in functionality 2. cleaning up both 3. MAYBE starting a brand new firewall project I wasn't planning on trying to rip something out from under anyone :) > > > On Sat, 19 Jun 1999, Brian F. Feldman wrote: > > > On 19 Jun 1999, Dag-Erling Smorgrav wrote: > > > > > "Brian F. Feldman" writes: > > > > It might be worth (discussion of) making ipfilter the firewall of > > > > choice for 4.0. There would of course be rule conversion > > > > scripts/programs (ipfw->ipf(5)), and ipfilter would be converted to > > > > a KLD, cruft removed (I'm going to work on these), and ipfilter KLD > > > > support (currently options IPFILTER_LKM) made a non-option. It seems > > > > that our pretty proprietary ipfw is no longer a good idea. > > > > > > If ipfilter can to everything ipfw can (judging from ipf(5), it can) > > > and you even manage to keep an ipfw(8) command around so those who > > > want kan keep using the old syntax still can, then I for one have no > > > objections. > > > > > > Rewriting ipfw rules to ipfilter rules on the fly should be trivial; a > > > simple Perl script should be sufficient. > > > > Not quite as trivial as you think. ipfw and ipf are completely backwards when it comes > > to rule order: in ipfw, the first rule matched takes effect; in ipf, the last rule matched > > takes effect. Plus, ipf doesn't have rule numbers (but there's similar functionailty.) > > If you think you can get used to them both enough to tackle this, I'll handle other > > things, and we can have a working replacement for crufty old ipfw. Note that Luigi's > > extra ipfw functionality and my extra ipfw functionality _will_ be wanted in ipf > > before everyone is necessarily willing to switch. I have a feeling there will be some > > holdouts that, even if ipfw is removed, they'll MFS (merge from stable) ipfw back just > > because they want to keep the old way. Ipfw could be dead for 4.0-RELEASE, as I see it > > now. More discussion is, however, necessary. > > > > > > > > DES > > > -- > > > Dag-Erling Smorgrav - des@flood.ping.uio.no > > > > > > > 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 > > > > > > 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