From owner-freebsd-stable Sun Jul 25 4: 0:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from awfulhak.org (dynamic-99.max1-du-ws.dialnetwork.pavilion.co.uk [212.74.8.99]) by hub.freebsd.org (Postfix) with ESMTP id 8197B15186 for ; Sun, 25 Jul 1999 04:00:18 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (root@keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id LAA12999; Sun, 25 Jul 1999 11:52:44 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id LAA71084; Sun, 25 Jul 1999 11:53:12 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199907251053.LAA71084@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Carroll Kong Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NATD 3.2-Release Issues? In-reply-to: Your message of "Sun, 25 Jul 1999 01:21:32 EDT." <4.2.0.58.19990725010824.01312ce0@email.eden.rutgers.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 Jul 1999 11:53:12 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please don't send messages individually to me and then to a list. Send to both at the same time with the same message - it wastes less of peoples time. This is my answer to your personal email with the same content: : Hi, : : The ``host is down'' message just means it's getting no response from : a directly connected host. I'm not sure what the question is here. : If you're trying to send stuff via your cable-providers server, : surely this means it's not responding ? : : BTW, you're best bet is to at least cc freebsd-questions as you're : more likely to find a better answer there. > Hi guys. I have been using 3.2-Release for quite some time now as a > natd. Normally I have no problems with this setup at all. However, I just > realized, after perusing my logs, I have been getting this error. > > Jul 18 17:58:41 daemon natd[107]: failed to write packet back (Host is down) > Jul 18 17:58:41 daemon natd[107]: failed to write packet back (No route to > host) > Jul 18 17:58:45 daemon natd[107]: failed to write packet back (No route to > host) > > (I only greped for natd in this case, it naturally has the 'last message > repeated' for quite some time in between logs) > > > Normally I get this error when my 'cable' modem goes down, so it makes > sense that there is no route to host. However, as I checked the more > recent logs. > > Jul 25 00:06:07 daemon natd[107]: failed to write packet back (Host is down) > Jul 25 00:06:12 daemon last message repeated 3 times > Jul 25 00:45:30 daemon natd[107]: failed to write packet back (Host is down) > Jul 25 00:51:54 daemon last message repeated 18 times > > Now, this error is a bit different. There is no '(No route to host)' error > this time. And, I get this error yet the cable modem interface did NOT go > down. I do not think I changed anything significant, however, I did add > these kernel options around the '5th of june'. > > pseudo-device bpfilter 4 #Berkeley packet filter > > #NATD > options IPFIREWALL > options IPDIVERT > > #DUMMYNET > options IPFIREWALL_VERBOSE > options IPFIREWALL_VERBOSE_LIMIT=10 > options DUMMYNET > options NMBCLUSTERS=1024 > > #SOFTUPDATES > options SOFTUPDATES > > #NCFTPD SHARED MEM > #options SHMMAXPGS=1024 > > #SHARED MEM OPTIONS FROM LINT > options SHMALL=1025 > options "SHMMAX=(SHMMAXPGS*PAGE_SIZE+1)" > options SHMMAXPGS=1025 > options SHMMIN=2 > options SHMMNI=33 > options SHMSEG=9 > > Ok. Now, I do use dummynet, however, using ipfw show, there was no usage > on that particular "pipe". The machine has maxusers set to 128, and is a > k6-200 with 32 megs of ram, using Dec PCI nics (two of them), on an > asus97-XE, TX Chipset. I really think the issue is software based over > hardware since previous logs did not have such a "large" amount of this > natd failure to write back. (previous to the 5th of july which was the > last time I modified my new kernel file). I also run these services on top > of the standard ones, like apache13+php3 with ssl, and I added my own > loadable module, mod_fastcgi, mysqld, postgresql, ncftpd, socks5, sshd, > with the default tcp wrapper, telnetd, and ftpd. (Hm. I could eliminate > running mysqld, even I only have 32 megs of ram, my machine 'does' seem ok > with the 'load', Kudos to FreeBSD power!). > > Now, I highly doubt if I just remake world it will 'fix' anything, however, > I am ready to remake world since I am using 3.2-RELEASE. However, I was > not aware of any significant fixes done to natd code during this > time. (sorry if I missed it, by the way, is there a direct listing of > fixes that grows as we progress through stable? I know it is cumbersome > though, and we must as well just add the list in each release, but just > curious for convenience sake). > > Ok. So, are any of my options somewhat "limiting" and causing a pipe to be > full or something odd like that? Or is this a known problem and I should > consider getting my machine 'synched' with 3.2-STABLE? It has to be my > kernel setup or a 'bug' that has been squashed some how, right? > > On the side, could it be my bpf filter is not high enough? I do use dhcpd, > but I only host maybe 3 clients. (they are not always even on all the time). > > Thanks in advance, I am sure we can find a solution for this problem. > > -Carroll Kong -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 25 11:53:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from chumbly.math.missouri.edu (chumbly.math.missouri.edu [128.206.72.12]) by hub.freebsd.org (Postfix) with ESMTP id 6053614BFA for ; Sun, 25 Jul 1999 11:53:13 -0700 (PDT) (envelope-from rich@chumbly.math.missouri.edu) Received: (from rich@localhost) by chumbly.math.missouri.edu (8.9.1a/8.9.1) id NAA25780 for freebsd-stable@freebsd.org; Sun, 25 Jul 1999 13:51:52 -0500 (CDT) From: Rich Winkel Message-Id: <199907251851.NAA25780@chumbly.math.missouri.edu> Subject: make installworld 3.2R -> 3.2S fails over NFS To: freebsd-stable@freebsd.org Date: Sun, 25 Jul 1999 13:51:52 -0500 (CDT) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is from 3.2 sources cvsup'd today. The buildworld on the nfs server goes fine, the make.conf files are identical on the server and client, but make installworld on the client gives: [... lots of lines ...] ===> gnu/usr.bin/perl/perl install -c -s -o root -g wheel -m 555 perl /usr/bin /usr/bin/perl5 -> /usr/bin/perl /usr/bin/perl5.00503 -> /usr/bin/perl cd /usr/obj/usr/src/gnu/usr.bin/perl/perl/ext/B ; make -B install INSTALLPRIVLI B=/usr/libdata/perl/5.00503 INSTALLARCHLIB=/usr/libdata/perl/5.00503/mach make: don't know how to make Makefile.PL. Stop *** Error code 2 Stop. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 25 12:34:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from poboxer.pobox.com (ferg5200-1-15.cpinternet.com [208.149.16.15]) by hub.freebsd.org (Postfix) with ESMTP id 98ACC14FD0 for ; Sun, 25 Jul 1999 12:34:27 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id OAA03062; Sun, 25 Jul 1999 14:30:03 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 25 Jul 1999 14:30:03 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: stable@freebsd.org Subject: Lost console X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14235.26016.454033.194916@avalon.east> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After upgrading from 3.2 CD to 3.2-STABLE, the console disappears when the kernel boots. How can I stop this behaviour? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 25 17:13:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (Postfix) with ESMTP id 9852F14CBA for ; Sun, 25 Jul 1999 17:13:43 -0700 (PDT) (envelope-from gnb@itga.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id KAA27885; Mon, 26 Jul 1999 10:11:32 +1000 (EST) Received: from lightning.itga.com.au(192.168.71.20) via SMTP by fw.bby.com.au, id smtpd027879; Mon Jul 26 00:11:29 1999 Received: from lightning (lightning [192.168.71.20]) by lightning.itga.com.au (8.9.1a/8.9.1) with ESMTP id KAA27998; Mon, 26 Jul 1999 10:11:26 +1000 (EST) Message-Id: <199907260011.KAA27998@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: Christoph Sold Cc: FreeBSD-Stable@FreeBSD.ORG Subject: Re: FAILED make buildword (3.1-R => 3.2-S) In-reply-to: Your message of Sat, 24 Jul 1999 17:55:38 +0200. Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 26 Jul 1999 10:11:26 +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > today I fetched the fresh 3.2 stable code using cvsup, starting make > buildworld. It failed. Since I=B4m out of my depth here, maybe you coul= d = > help. You missed the HEADS UP messages posted by John Polstra on -stable on 03 = Jul? [you do follow the stable mailinglist, don't you!?] The softupdates files have moved and need new symlinks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 25 18:37:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 971D314D95 for ; Sun, 25 Jul 1999 18:37:53 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:bX7D2TOADqNo7W0jsmweLRLCGx3uFgGr@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id KAA21229; Mon, 26 Jul 1999 10:36:50 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id KAA05141; Mon, 26 Jul 1999 10:41:08 +0900 (JST) Message-Id: <199907260141.KAA05141@zodiac.mech.utsunomiya-u.ac.jp> To: alk@pobox.com Cc: stable@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Lost console In-reply-to: Your message of "Sun, 25 Jul 1999 14:30:03 EST." <14235.26016.454033.194916@avalon.east> References: <14235.26016.454033.194916@avalon.east> Date: Mon, 26 Jul 1999 10:41:07 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >After upgrading from 3.2 CD to 3.2-STABLE, the console disappears >when the kernel boots. How can I stop this behaviour? I think you should still be able to login to the system via network. Send me /var/run/dmesg.out, /boot.config, /boot/loader.rc and your kernel configuration file for examination. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 25 19: 9:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from poboxer.pobox.com (ferg5200-1-41.cpinternet.com [208.149.16.41]) by hub.freebsd.org (Postfix) with ESMTP id CF5C214E35 for ; Sun, 25 Jul 1999 19:09:14 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id VAA02005; Sun, 25 Jul 1999 21:04:09 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 25 Jul 1999 21:04:07 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: yokota@zodiac.mech.utsunomiya-u.ac.jp Cc: stable@freebsd.org Subject: Re: Lost console References: <14235.26016.454033.194916@avalon.east> <199907260141.KAA05141@zodiac.mech.utsunomiya-u.ac.jp> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14235.49122.970966.568427@avalon.east> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Kazutaka YOKOTA on Mon, 26 July: : : >After upgrading from 3.2 CD to 3.2-STABLE, the console disappears : >when the kernel boots. How can I stop this behaviour? : : I think you should still be able to login to the system via network. : Send me /var/run/dmesg.out, /boot.config, /boot/loader.rc and your : kernel configuration file for examination. (Sorry. Insufficient clarity is ever the petty hobgoblin that haunts my email. Or is it otiose purple? I forget.) What I mean to describe is that, from the time /boot/loader beings a "boot" until "Login:", no console activity is visible. If it never gets that far -- c'est perdu. Attempting to "boot -s" results in no better results: No prompt ever appears. Sometimes I can ctl-alt-del my way back to the BIOS, in order to boot a different kernel, and sometimes I can't. I'm expecting that there is a config element required in order to avoid this behaviour. Inspection of GENERIC and LINT did not make it evident, however, and a bisection search on LINT would take an absurd amount of time, hence my query. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 25 19:21:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id CF7AF14BE5 for ; Sun, 25 Jul 1999 19:21:29 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:CicCmxEHVJfVZ3qmQGw9oR+2Lt7IN0Y0@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id LAA21771; Mon, 26 Jul 1999 11:21:01 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id LAA07433; Mon, 26 Jul 1999 11:25:19 +0900 (JST) Message-Id: <199907260225.LAA07433@zodiac.mech.utsunomiya-u.ac.jp> To: alk@pobox.com Cc: stable@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Lost console In-reply-to: Your message of "Sun, 25 Jul 1999 21:04:07 EST." <14235.49122.970966.568427@avalon.east> References: <14235.26016.454033.194916@avalon.east> <199907260141.KAA05141@zodiac.mech.utsunomiya-u.ac.jp> <14235.49122.970966.568427@avalon.east> Date: Mon, 26 Jul 1999 11:25:13 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >: I think you should still be able to login to the system via network. >: Send me /var/run/dmesg.out, /boot.config, /boot/loader.rc and your >: kernel configuration file for examination. > >(Sorry. Insufficient clarity is ever the petty hobgoblin that haunts >my email. Or is it otiose purple? I forget.) > >What I mean to describe is that, from the time /boot/loader beings a >"boot" until "Login:", no console activity is visible. If it never >gets that far -- c'est perdu. Attempting to "boot -s" results in no >better results: No prompt ever appears. Sometimes I can ctl-alt-del >my way back to the BIOS, in order to boot a different kernel, and >sometimes I can't. > >I'm expecting that there is a config element required in order to >avoid this behaviour. Inspection of GENERIC and LINT did not make >it evident, however, and a bisection search on LINT would take an >absurd amount of time, hence my query. I am suspecting that somehow your system is trying to use the serial console. Please provide your /var/run/dmesg.out, /boot.config, /boot/loader.rc and your kernel configuration file. Without these info, it is extremely difficult to give you any advice. When you ever see "Login:" prompt, you should be able to login to the system. (It may take relatively a long time.) Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 26 4: 1:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.singtel-yp.com (mail.singtel-yp.com [165.21.60.44]) by hub.freebsd.org (Postfix) with SMTP id A1E8714BEE for ; Mon, 26 Jul 1999 04:01:12 -0700 (PDT) (envelope-from ktsin@mail.singtel-yp.com) Received: (qmail 15326 invoked by uid 1001); 26 Jul 1999 11:00:08 -0000 Message-ID: <19990726110008.15325.qmail@mail.singtel-yp.com> From: ktsin@mail.singtel-yp.com Subject: a patch to fix the proxy arp problem To: stable@freebsd.org Date: Mon, 26 Jul 1999 19:00:08 +0800 (SGT) Cc: jooji@neptune.oceancomputer.com 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've managed to track down the proxy arp problem in 3.2-stable. It was due to misalignment which led to wrong/corrupted destination address and netmask. In many scenarios, the wrong address and netmask would match a existing route in the routing table, prompting the kernel to reject the request to add the new route. To fix the proxy arp problem, type: fetch -o - http://www.daddylonglegs.com/arp.patch | patch -d /usr/src and then rebuild arp in /usr/src/usr.sbin/arp. kt :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 26 6:42:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from neptune.oceancomputer.com (neptune.oceancomputer.com [216.116.139.133]) by hub.freebsd.org (Postfix) with ESMTP id 7EE1B14F95 for ; Mon, 26 Jul 1999 06:42:48 -0700 (PDT) (envelope-from jooji@neptune.oceancomputer.com) Received: from localhost (jooji@localhost) by neptune.oceancomputer.com (8.9.2/8.9.2) with ESMTP id JAA22832; Mon, 26 Jul 1999 09:41:28 -0400 (EDT) Date: Mon, 26 Jul 1999 09:41:28 -0400 (EDT) From: "Jasper O'Malley" To: ktsin@mail.singtel-yp.com Cc: stable@freebsd.org Subject: Re: a patch to fix the proxy arp problem In-Reply-To: <19990726110008.15325.qmail@mail.singtel-yp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Jul 1999 ktsin@mail.singtel-yp.com wrote: > I've managed to track down the proxy arp problem in 3.2-stable. It was due to > misalignment which led to wrong/corrupted destination address and netmask. Thank you :) If you have a second, could you go over the patch briefly, and explain what it does? Is the misalignment caused by the addition of the sdl_rcf and sdl_route elements to the sockaddr_dl structure in /usr/src/sys/net/if_dl.h? Why did it work without the ROUNDUP() macro before the addition of these elements, and why don't it now? Thanks again for the patch...I can upgrade my firewall again ;) Cheers, Mick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 26 10:42:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id 57E3014EBD for ; Mon, 26 Jul 1999 10:42:11 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt011n65.san.rr.com (8.8.8/8.8.8) with ESMTP id KAA19696; Mon, 26 Jul 1999 10:41:19 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Mon, 26 Jul 1999 10:41:18 -0700 (PDT) From: Doug X-Sender: doug@dt011n65.san.rr.com To: ktsin@mail.singtel-yp.com Cc: stable@freebsd.org Subject: Re: a patch to fix the proxy arp problem In-Reply-To: <19990726110008.15325.qmail@mail.singtel-yp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Jul 1999 ktsin@mail.singtel-yp.com wrote: > I've managed to track down the proxy arp problem in 3.2-stable. It was due to > misalignment which led to wrong/corrupted destination address and netmask. > > To fix the proxy arp problem, type: > > fetch -o - http://www.daddylonglegs.com/arp.patch | patch -d /usr/src You probably want to send this in as a PR as well. Thank you for your diligence in hunting this one down. Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 26 14:13:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from hotmail.com (f261.hotmail.com [207.82.251.152]) by hub.freebsd.org (Postfix) with SMTP id 0FCB814CFB for ; Mon, 26 Jul 1999 14:13:47 -0700 (PDT) (envelope-from showboat@hotmail.com) Received: (qmail 56446 invoked by uid 0); 26 Jul 1999 21:12:15 -0000 Message-ID: <19990726211215.56445.qmail@hotmail.com> Received: from 207.202.146.16 by www.hotmail.com with HTTP; Mon, 26 Jul 1999 14:12:14 PDT X-Originating-IP: [207.202.146.16] From: "Show Boat" To: freebsd-stable@FreeBSD.ORG Subject: Re: repeated mysql oriented crashes Date: Mon, 26 Jul 1999 14:12:14 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We upgraded the uthreads as recommended, but to no avail. :( It appears that the on screen console errors (before the mandatory hard reboot) haven't been the same every time. This time (according to the TECH at our ISP) the screen was full of scrolling 'busy count' and 'pack count' errors. It was scrolling too quickly for him to make out more, but he did mention da0. I'm beginning to question the RAID system. Even though all crashes have been directly linked to mysql queries, the onscreen errors seem to always refer to da0. (running a DPT PM3334UW/2) I can't find any indications that the DPT drivers have been upgraded. I'm banging my head against a wall here. Any suggestions (other than finding a softer wall) would be really appreciated. Thanks, Jeremy >From: Ludwig Pummer >To: "Show Boat" >CC: freebsd-stable@FreeBSD.ORG >Subject: Re: repeated mysql oriented crashes >Date: Tue, 20 Jul 1999 22:13:18 -0700 > >At 06:01 PM 7/20/1999 -0700, Show Boat wrote: >>Some hunting and searching has led us to believe that we are encountering >>a driver failure and that we should bring the OS back to -stable. >> >>As I said, I haven't done this before, so I'm a little anxious. Before I >>take that step, I would be very greatful to hear some input from those who >>surely know more about this than I do. >> >>Is bringing the system back to -stable likely to correct our problem? Am >>I missing some indicator in the error above? Has someone else >>encountered similar trouble (and found a fix?) > >I don't know if bringing it to -stable would fix your driver problem. I do >remember the odd message on one of the lists regarding problems with the >DPT driver. > >However, I _do_ know that FreeBSD 3.1-Stable sometime after May 14 (that >was the last make world I did on a production server before hearing rumors >of the pthreads breakage) has broken pthreads support, meaning that if you >want to run mysql with native pthreads, it will crash. I don't know if this >has been fixed in -stable since it was last brought up in this list (end of >June/early July). A fixed pthreads library is available at >ftp://ftp.pcnet.com/users/eischen/FreeBSD/uthread.tgz , if it hasn't been >fixed in -stable yet. Your 2 options (if -stable's pthreads hasn't been >fixed yet) are to either use MIT pthreads (included with mysql) or use the >fixed pthreads tarball listed above. > >--Ludwig Pummer > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message _______________________________________________________________ Get Free Email and Do More On The Web. Visit http://www.msn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 26 18:17:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.singtel-yp.com (mail.singtel-yp.com [165.21.60.44]) by hub.freebsd.org (Postfix) with SMTP id A5DF415022 for ; Mon, 26 Jul 1999 18:17:32 -0700 (PDT) (envelope-from ktsin@mail.singtel-yp.com) Received: (qmail 23014 invoked by uid 1001); 27 Jul 1999 01:17:31 -0000 Message-ID: <19990727011731.23013.qmail@mail.singtel-yp.com> From: ktsin@mail.singtel-yp.com Subject: Re: a patch to fix the proxy arp problem To: jooji@neptune.oceancomputer.com (Jasper O'Malley) Date: Tue, 27 Jul 1999 09:17:31 +0800 (SGT) Cc: stable@freebsd.org In-Reply-To: from "Jasper O'Malley" at Jul 26, 99 09:41:28 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 26 Jul 1999 ktsin@mail.singtel-yp.com wrote: > > > I've managed to track down the proxy arp problem in 3.2-stable. It was due to > > misalignment which led to wrong/corrupted destination address and netmask. > > Thank you :) If you have a second, could you go over the patch briefly, > and explain what it does? Is the misalignment caused by the addition of > the sdl_rcf and sdl_route elements to the sockaddr_dl structure in > /usr/src/sys/net/if_dl.h? Yes. sockaddr_dl was previously 20 bytes long (multiple of 4 bytes or sizeof(long)). After the sdl_rcf and sdl_route elements were added the length increased to 54 bytes. > Why did it work without the ROUNDUP() macro > before the addition of these elements, and why don't it now? The ROUNDUP() macro is also used in /usr/src/sys/net/rtsock.c. By using the macro, rtsock.c requires the start of each sockaddr in the sockaddr list to be a multiple of 4. Arp does not adhere to this requirement when constructing or extracting the sockaddr list in the set() or get() routines. It just appends one sockaddr after another, without leaving any padding or gap when needed. I don't know if arp or changes to sockaddr_dl in if_dl.h is responsible for the breakage. Does the spec require the length of all sockaddrs to be multiples of 4 bytes? kt > > Thanks again for the patch...I can upgrade my firewall again ;) > > Cheers, > Mick > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 27 1:32:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dingo.cdrom.com (castles554.castles.com [208.214.165.118]) by hub.freebsd.org (Postfix) with ESMTP id A9B0015378 for ; Tue, 27 Jul 1999 01:32: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 BAA01383; Tue, 27 Jul 1999 01:26:46 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907270826.BAA01383@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "David Schwartz" Cc: "Mike Smith" , stable@freebsd.org Subject: Re: Tuning the system's clock In-reply-to: Your message of "Thu, 22 Jul 1999 12:40:31 PDT." <001801bed47a$0efc31a0$021d85d1@youwant.to> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Jul 1999 01:26:45 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The TSC is calibrated at boot time using the RTC; that calibration is > > inherently limited to the accuracy of the RTC. > > Exactly. The RTC is accurate to maybe 150 ppm. The other problem is that > this calibration occurs right after power up, when the system is 'cold'. > It's not going to be representative of the system's 'warm' rate either. That assumes that you don't pause the system to allow it to warm up first. 8) > For one thing, the TSC oscillator can be replaced with a high-precision > OCXO. But that won't help you if you can't tune the TSC divisor, will it? > (Of course, XNTP would be the right tool for this purpose.) Actually, I don't think you'd have any luck replacing the TSC oscillator without a lot of nasty boardwork; many applications these days are using programmable frequency synthesisers using embedded crystals in the 10-40MHz range; I've seen others using cheap NTSC colourburst crystals and even a couple using 32kHz watch crystals. > In any event, tuning the TSC divisor via sysctl causes my FreeBSD-STABLE > machine to reboot instantly. I've just found that NTP seems to work the best > when the system is already keeping pretty good time. This is definitely a bug. Have you spoken to Poul about it yet? The "instant reboot" sounds particularly unpleasant; it should be fairly straightforward to track it down though. -- \\ 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-stable" in the body of the message From owner-freebsd-stable Tue Jul 27 11:43:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from exit-gw.power.net (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id B6BA814BFF for ; Tue, 27 Jul 1999 11:43:10 -0700 (PDT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.8.8/8.8.8) with ESMTP id LAA04999 for ; Tue, 27 Jul 1999 11:41:46 -0700 (PDT) (envelope-from frank@tinker.exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.1) id LAA04083 for stable@freebsd.org; Tue, 27 Jul 1999 11:41:46 -0700 (PDT) (envelope-from frank) From: Frank Mayhar Message-Id: <199907271841.LAA04083@realtime.exit.com> Subject: Upgrading from 2.2.8 to 3.2-stable... To: stable@freebsd.org Date: Tue, 27 Jul 1999 11:41:46 -0700 (PDT) Reply-To: frank@exit.com 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I sent this to -hackers, and got very little response. Warner Losh suggest I drop back to 3.1-RELEASE and retry the upgrade. I did, and got the same result. Has anyone succeeded at this, and, if so, how? > Well, I'm having problems upgrading a system from 2.2.8 to 3.2-stable. I > checked the archives, and apparently others have run into this one as well. > Unfortunately, I couldn't find a fix for it. > > The problem is when the upgrade procedure tries to build the elf version of > libmytinfo. It generates an executable, mkcaplist, which it uses to > generate the caplist.c file. This is an elf executable, which promptly > coredumps when the makefile tries to run it. > > Now, I _know_ this library has been around for a while, and others have > successfully done a "make upgrade." My question is: What the hell am I > doing wrong? > > I'm just doing a "make upgrade" on a clean /usr/obj. It crashes when it gets > to libmytinfo. That's it. > > Any help or pointers would be greatly appreciated. Thanks. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 27 12:53:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from Hinako.AMBusiness.com (hinako.ambusiness.com [204.183.184.20]) by hub.freebsd.org (Postfix) with ESMTP id D117714C9E; Tue, 27 Jul 1999 12:53:19 -0700 (PDT) (envelope-from gdsntusr@globaldelsys.com) Received: from optimant (user-2ivebv6.dialup.mindspring.com [165.247.47.230]) by Hinako.AMBusiness.com (8.9.3/8.9.3) with SMTP id PAA01669; Tue, 27 Jul 1999 15:23:49 -0400 Message-ID: <000d01bed869$ddeec110$2bc809c0@HalbartAir.com> From: "NT Workstation User" To: , , , , Subject: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms Date: Tue, 27 Jul 1999 15:54:07 -0400 Organization: Global Delivery Systems X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am having a pecular problem trying to run SCO binaries under the iBCS emulation in Linux. I figure the problem may be related to Linux lacking the necesary functionality to support files larger than 2GB which this SCO binary supports. I was thinking of trying freeBSD with its SCO emulation support but I am uncertain whether freeBSD supports files larger than 2GB on 32bit x86 platforms. Anybody know the answer to this question. Also if only a peticular version supports it, let me know so I can get the correct version. The program that I am trying to get to run under freeBSD or Linux is the Microfocus cobol runtime. Everything else in that COBOL development package works except the actual runtime, which just happens to support large files (> 2GB) for the COBOL databases. This is why I fugure its dying under Linux, so does freeBSD on 32bit x86 platforms support files > 2GB? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 27 12:55:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from Hinako.AMBusiness.com (hinako.ambusiness.com [204.183.184.20]) by hub.freebsd.org (Postfix) with ESMTP id 0A3AD15337; Tue, 27 Jul 1999 12:55:12 -0700 (PDT) (envelope-from gdsntusr@globaldelsys.com) Received: from optimant (user-2ivebsm.dialup.mindspring.com [165.247.47.150]) by Hinako.AMBusiness.com (8.9.3/8.9.3) with SMTP id PAA01675; Tue, 27 Jul 1999 15:25:36 -0400 Message-ID: <001301bed86a$1d2e2910$2bc809c0@HalbartAir.com> From: "NT Workstation User" To: , , , , Subject: Re: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms Date: Tue, 27 Jul 1999 15:55:51 -0400 Organization: Global Delivery Systems X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I forgot, please forward a copy of any responses to my email address as I am not a member of any of these lists. ----- Original Message ----- From: NT Workstation User To: ; ; ; ; Sent: Tuesday, July 27, 1999 3:54 PM Subject: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms > I am having a pecular problem trying to run SCO binaries under the iBCS > emulation in Linux. I figure the problem may be related to Linux lacking > the necesary functionality to support files larger than 2GB which this SCO > binary supports. I was thinking of trying freeBSD with its SCO emulation > support but I am uncertain whether freeBSD supports files larger than 2GB on > 32bit x86 platforms. Anybody know the answer to this question. Also if > only a peticular version supports it, let me know so I can get the correct > version. The program that I am trying to get to run under freeBSD or Linux > is the Microfocus cobol runtime. Everything else in that COBOL development > package works except the actual runtime, which just happens to support large > files (> 2GB) for the COBOL databases. This is why I fugure its dying under > Linux, so does freeBSD on 32bit x86 platforms support files > 2GB? > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 27 13: 6: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tasam.com (tasam.com [206.161.83.22]) by hub.freebsd.org (Postfix) with ESMTP id 8300F153D1; Tue, 27 Jul 1999 13:05:39 -0700 (PDT) (envelope-from freebsd.list@bug.tasam.com) Received: from bug (209-122-238-225.s225.tnt2.lnh.md.dialup.rcn.com [209.122.238.225]) by tasam.com (8.9.3/8.9.1) with SMTP id QAA11004; Tue, 27 Jul 1999 16:05:23 -0400 (EDT) Message-ID: <009a01bed86b$601baf80$0286860a@tasam.com> From: "Joe Gleason" To: "NT Workstation User" , , , , , References: <000d01bed869$ddeec110$2bc809c0@HalbartAir.com> Subject: Re: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms Date: Tue, 27 Jul 1999 16:05:17 -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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am uncertain about the emulation issues, but I know my backup tar files often exceed 4GB on x86 systems. I have done this with versions FreeBSD 2.2.2-3.2. I have never heard it mentioned before, so I assume it works on all versions. Probably a UFS thing. Joe Gleason Tasam > I am having a pecular problem trying to run SCO binaries under the iBCS > emulation in Linux. I figure the problem may be related to Linux lacking > the necesary functionality to support files larger than 2GB which this SCO > binary supports. I was thinking of trying freeBSD with its SCO emulation > support but I am uncertain whether freeBSD supports files larger than 2GB on > 32bit x86 platforms. Anybody know the answer to this question. Also if > only a peticular version supports it, let me know so I can get the correct > version. The program that I am trying to get to run under freeBSD or Linux > is the Microfocus cobol runtime. Everything else in that COBOL development > package works except the actual runtime, which just happens to support large > files (> 2GB) for the COBOL databases. This is why I fugure its dying under > Linux, so does freeBSD on 32bit x86 platforms support files > 2GB? > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 27 13:22:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from Hinako.AMBusiness.com (hinako.ambusiness.com [204.183.184.20]) by hub.freebsd.org (Postfix) with ESMTP id 28D6114DE3; Tue, 27 Jul 1999 13:22:17 -0700 (PDT) (envelope-from gdsntusr@globaldelsys.com) Received: from optimant (user-2ivebm6.dialup.mindspring.com [165.247.46.198]) by Hinako.AMBusiness.com (8.9.3/8.9.3) with SMTP id PAA01720; Tue, 27 Jul 1999 15:52:44 -0400 Message-ID: <001901bed86d$e7b4c010$2bc809c0@HalbartAir.com> From: "NT Workstation User" To: "Joe Gleason" , , , , , References: <000d01bed869$ddeec110$2bc809c0@HalbartAir.com> <009a01bed86b$601baf80$0286860a@tasam.com> Subject: Re: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms Date: Tue, 27 Jul 1999 16:22:59 -0400 Organization: Global Delivery Systems X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ummm, I'm not sure whether tar files count. See the 2GB file limit under Linux comes from the maximum value of a 32bit signed integer. Because the file system calls use those 32bit integers a file's size is limited to 2GB, at least if you want random access. tar files generally aren't accessed in a random access fashion, instead the file is treated as a byte stream. Though I can't remember exactly, I think I created (> 2GB) tar files under Linux once too. I know SCO and other commercial OSes have addition file functions for large files which use 64bit integers to overcome this limitation. As Linux lacks this feature I am considering giving freeBSD (or any of the other BSDs) a try. Of course this leaves me wondering whether to try the pre-4.0 or the 3.2 version. ----- Original Message ----- From: Joe Gleason To: NT Workstation User ; ; ; ; ; Sent: Tuesday, July 27, 1999 4:05 PM Subject: Re: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms > I am uncertain about the emulation issues, but I know my backup tar files > often exceed 4GB on x86 systems. > I have done this with versions FreeBSD 2.2.2-3.2. I have never heard it > mentioned before, so I assume it works on all versions. Probably a UFS > thing. > > Joe Gleason > Tasam > > > I am having a pecular problem trying to run SCO binaries under the iBCS > > emulation in Linux. I figure the problem may be related to Linux lacking > > the necesary functionality to support files larger than 2GB which this SCO > > binary supports. I was thinking of trying freeBSD with its SCO emulation > > support but I am uncertain whether freeBSD supports files larger than 2GB > on > > 32bit x86 platforms. Anybody know the answer to this question. Also if > > only a peticular version supports it, let me know so I can get the correct > > version. The program that I am trying to get to run under freeBSD or > Linux > > is the Microfocus cobol runtime. Everything else in that COBOL > development > > package works except the actual runtime, which just happens to support > large > > files (> 2GB) for the COBOL databases. This is why I fugure its dying > under > > Linux, so does freeBSD on 32bit x86 platforms support files > 2GB? > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 27 13:33:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from web1.aps-services.com (adsl-209-232-134-22.dsl.scrm01.pacbell.net [209.232.134.22]) by hub.freebsd.org (Postfix) with ESMTP id BC4EE14DE3 for ; Tue, 27 Jul 1999 13:33:36 -0700 (PDT) (envelope-from david@web1.aps-services.com) Received: from dave ([192.168.0.12]) by web1.aps-services.com (8.9.1/8.8.6) with SMTP id NAA00315 for ; Tue, 27 Jul 1999 13:29:08 -0700 (PDT) Message-Id: <199907272029.NAA00315@web1.aps-services.com> From: dave@aps-services.com To: freebsd-stable@FreeBSD.ORG Date: Tue, 27 Jul 1999 13:36:05 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: rc.conf and a third ethernet device X-mailer: Pegasus Mail for Win32 (v3.01d) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I added a third nic card to my 2.2.7 box and added a line to the rc.conf file. The machine sees the card and I can ifconfig the card up. Why won't this card come up on startup? Cheers David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 27 13:42:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from support.euronet.nl (support.euronet.nl [194.134.32.134]) by hub.freebsd.org (Postfix) with ESMTP id 4335415347 for ; Tue, 27 Jul 1999 13:42:17 -0700 (PDT) (envelope-from pieterw@support.euronet.nl) Received: (from pieterw@localhost) by support.euronet.nl (8.9.1/8.9.1) id WAA17638; Tue, 27 Jul 1999 22:39:53 +0200 (CEST) (envelope-from pieterw) Date: Tue, 27 Jul 1999 22:39:53 +0200 From: Pieter Westland To: dave@aps-services.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: rc.conf and a third ethernet device Message-ID: <19990727223953.A17464@support.euronet.nl> References: <199907272029.NAA00315@web1.aps-services.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199907272029.NAA00315@web1.aps-services.com>; from dave@aps-services.com on Tue, Jul 27, 1999 at 01:36:05PM -0700 X-OS: FreeBSD support.euronet.nl 2.2.7-STABLE FreeBSD 2.2.7-STABLE X-URL: http://support.euronet.nl/~pieterw X-Editor: vim X-Organization: EuroNet * Internet Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 27, 1999 at 01:36:05PM -0700, dave@aps-services.com wrote: > I added a third nic card to my 2.2.7 box and added a line to the > rc.conf file. The machine sees the card and I can ifconfig the card up. > Why won't this card come up on startup? Did you add the device in /etc/rc.conf in the network_interfaces-line? And was also a ifconfig_interface-line added? Example (machine with two NIC's, running 3.1-RELEASE): network_interfaces="ed1 ed2 lo0" ifconfig_ed2="inet (ip-address) netmask 255.255.254.0" ifconfig_ed1="inet 192.168.50.1 netmask 255.255.255.0" Pieter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 27 13:55: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from web1.aps-services.com (adsl-209-232-134-22.dsl.scrm01.pacbell.net [209.232.134.22]) by hub.freebsd.org (Postfix) with ESMTP id 36D981523E for ; Tue, 27 Jul 1999 13:55:01 -0700 (PDT) (envelope-from david@web1.aps-services.com) Received: from dave ([192.168.0.12]) by web1.aps-services.com (8.9.1/8.8.6) with SMTP id NAA00306 for ; Tue, 27 Jul 1999 13:49:31 -0700 (PDT) Message-Id: <199907272049.NAA00306@web1.aps-services.com> From: dave@aps-services.com To: stable@freebsd.org Date: Tue, 27 Jul 1999 13:56:28 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: rc.conf and ethernet device X-mailer: Pegasus Mail for Win32 (v3.01d) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you everyone for responding so quickly. A want to apologize to Dan Riley for not posting the question with the right list. Thank you, David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 27 15: 6:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id A8B6E153B3 for ; Tue, 27 Jul 1999 15:06:42 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id AAA10989; Wed, 28 Jul 1999 00:05:07 +0200 (CEST) (envelope-from olli) Date: Wed, 28 Jul 1999 00:05:07 +0200 (CEST) From: Oliver Fromme Message-Id: <199907272205.AAA10989@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms Cc: gdsntusr@globaldelsys.com Organization: Administration Heim 3 Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG gdsntusr@globaldelsys.com wrote in list.freebsd-stable: > [...] I was thinking of trying freeBSD with its SCO emulation > support but I am uncertain whether freeBSD supports files larger than 2GB on > 32bit x86 platforms. It certainly does. olli@dao-lin-hay:/tmp> touch foobar olli@dao-lin-hay:/tmp> truncate `echo "2^43 - 1" | bc` foobar olli@dao-lin-hay:/tmp> ls -l foobar -rw-r--r-- 1 olli wheel 8796093022207 Jul 27 23:55 foobar olli@dao-lin-hay:/tmp> That's 8 Tbyte - 1. Impressive, isn't it? :) By the way, off_t (the data type used for seeking in files and other things) is 64 bits in FreeBSD, even on the 32bit i386 platform, so this is not limiting. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 27 18:53:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 5EB4215403; Tue, 27 Jul 1999 18:53:09 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.3/8.9.1) id VAA07686; Tue, 27 Jul 1999 21:50:33 -0400 (EDT) (envelope-from mi) Message-Id: <199907280150.VAA07686@misha.cisco.com> Subject: uthread_init.c: 'Cannot get stdio flags' :-( To: questions@freebsd.org, stable@freebsd.org Date: Tue, 27 Jul 1999 21:50:32 -0400 (EDT) Cc: eischen@vigrid.com, jb@cimlogic.com.au Reply-To: mi@aldan.algebra.com From: Mikhail Teterin X-Mailer: ELM [version 2.4ME+ PL60 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Under what circumstances could a panic: Fatal error 'Cannot get stdio flags' at line ? in file /usr/src/lib/libc_r/uthread/uthread_init.c (errno = ?) be triggered? We are trying to replace HylaFAX's ${PREFIX}/sbin/faxsend with our own application, which is written with threads. The app works fine if called directly -- from command line. But it dies a horrible death when actually invoked by HylaFAX's ${PREFIX}/sbin/faxq. Here is a rather short ktrace produced by replacing faxsend with a shell wrapper: 1157 ktrace RET ktrace 0 1157 ktrace CALL execve(0xbfbfdc23,0xbfbfdaec,0xbfbfdb00) 1157 ktrace NAMI "/usr/local/sbin/faxsend.bin" 1157 faxsend.bin RET execve 0 1157 faxsend.bin CALL getpid 1157 faxsend.bin RET getpid 1157/0x485 1157 faxsend.bin CALL fcntl(0,0x3,0) 1157 faxsend.bin RET fcntl -1 errno 9 Bad file descriptor 1157 faxsend.bin CALL write(0x2,0xbfbfd9ac,0x6e) 1157 faxsend.bin GIO fd 2 wrote 110 bytes "Fatal error 'Cannot get stdio flags' at line ? in file /usr/src/lib/libc_r/ut\ hread/uthread_init.c (errno = ?) " 1157 faxsend.bin RET write 110/0x6e 1157 faxsend.bin CALL setitimer(0x2,0xbfbfd968,0) 1157 faxsend.bin RET setitimer 0 1157 faxsend.bin CALL close(0xffffffff) 1157 faxsend.bin RET close -1 errno 9 Bad file descriptor 1157 faxsend.bin CALL close(0xffffffff) 1157 faxsend.bin RET close -1 errno 9 Bad file descriptor 1157 faxsend.bin PSIG SIGSEGV SIG_DFL First the thread library panics and then segfaults before our main() even gets a chance to do anything... The entire app is compiled with "-D_THREADSAFE -pthread" and linked with "-pthread -static" (tried dynamic too). The only other library -- -lm is not rebuilt with thread awareness, though. The problem is perfectly reproducible on FreeBSD 3.0-RELEASE as well as on 3.2-RELEASE... Thanks in advance for any hints. Yours sincerely, -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 27 20:24:26 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id C705614F0E; Tue, 27 Jul 1999 20:24:13 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.3/8.9.1) id NAA55212; Wed, 28 Jul 1999 13:30:57 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199907280330.NAA55212@cimlogic.com.au> Subject: Re: uthread_init.c: 'Cannot get stdio flags' :-( In-Reply-To: <199907280150.VAA07686@misha.cisco.com> from Mikhail Teterin at "Jul 27, 1999 09:50:32 pm" To: mi@aldan.algebra.com Date: Wed, 28 Jul 1999 13:30:56 +1000 (EST) Cc: questions@freebsd.org, stable@freebsd.org, eischen@vigrid.com, jb@cimlogic.com.au 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > Under what circumstances could a panic: > > Fatal error 'Cannot get stdio flags' at line ? in file > /usr/src/lib/libc_r/uthread/uthread_init.c (errno = ?) > > be triggered? > > We are trying to replace HylaFAX's ${PREFIX}/sbin/faxsend with our own > application, which is written with threads. The app works fine if called > directly -- from command line. But it dies a horrible death when > actually invoked by HylaFAX's ${PREFIX}/sbin/faxq. Here is a rather > short ktrace produced by replacing faxsend with a shell wrapper: Looks like ${PREFIX}/sbin/faxq has closed file descriptor 0 (stdin). It's legal to do that, so our thread initialisation will have to check for EBADF and not fail in that case. -- 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-stable" in the body of the message From owner-freebsd-stable Tue Jul 27 21:34:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 4027C14DC3 for ; Tue, 27 Jul 1999 21:34:21 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.3/8.9.1) id OAA55371; Wed, 28 Jul 1999 14:40:03 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199907280440.OAA55371@cimlogic.com.au> Subject: Re: uthread_init.c: 'Cannot get stdio flags' :-( In-Reply-To: <379E8126.3541FDA9@vigrid.com> from "Daniel M. Eischen" at "Jul 28, 1999 00:03:50 am" To: eischen@vigrid.com (Daniel M. Eischen) Date: Wed, 28 Jul 1999 14:40:02 +1000 (EST) Cc: jb@cimlogic.com.au, mi@aldan.algebra.com, stable@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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel M. Eischen wrote: > John Birrell wrote: > > Looks like ${PREFIX}/sbin/faxq has closed file descriptor 0 (stdin). > > It's legal to do that, so our thread initialisation will have to check > > for EBADF and not fail in that case. > > Assuming it's also legal for stdout and stderr, is this what you had > in mind (not compiled or tested)? Yes, at least as far as the initialisation goes. There is probably an issue about restoring the file descriptors on fork/exit/sigchld that I haven't thought through. [ I replied to this without looking at the sources, so what I just said may turn out to be of no consequence. I could claim that I'm so busy, but the truth is it's a sunny winter day here. 8-) ] -- 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-stable" in the body of the message From owner-freebsd-stable Tue Jul 27 23: 2:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from br3-de0.dnsmgr.net (br3-de0.dnsmgr.net [198.145.92.3]) by hub.freebsd.org (Postfix) with ESMTP id 4679E1502A; Tue, 27 Jul 1999 23:02:19 -0700 (PDT) (envelope-from hamellr@hamell.hpc1.com) Received: from heorot.hamell.hpc1.com (host74-43.iwbc.net [216.228.74.43]) by br3-de0.dnsmgr.net (8.9.3/8.9.3) with SMTP id XAA92581; Tue, 27 Jul 1999 23:12:57 -0700 (PDT) (envelope-from hamellr@hamell.hpc1.com) Date: Mon, 26 Jul 1999 15:26:24 -0700 (PDT) From: Rick Hamell To: NT Workstation User Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms In-Reply-To: <000d01bed869$ddeec110$2bc809c0@HalbartAir.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Trimmed a few CC's) > binary supports. I was thinking of trying freeBSD with its SCO emulation > support but I am uncertain whether freeBSD supports files larger than 2GB on > 32bit x86 platforms. Anybody know the answer to this question. Also if > only a peticular version supports it, let me know so I can get the correct > version. The program that I am trying to get to run under freeBSD or Linux I dimly remeber someone mentioning that they had tested 60 gig files just to make sure there was no limitation. Of course that was under 2.2.8 I think....:) Rick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 1: 7:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from exstudent3.levels.unisa.edu.au (EXSTUDENT3.Levels.UniSA.Edu.Au [130.220.22.184]) by hub.freebsd.org (Postfix) with ESMTP id 9D53914F31 for ; Wed, 28 Jul 1999 01:07:27 -0700 (PDT) (envelope-from SAYJM001@students.unisa.edu.au) Received: by EXSTUDENT3.Levels.UniSA.Edu.Au with Internet Mail Service (5.5.2232.9) id ; Wed, 28 Jul 1999 17:35:27 +0930 Message-ID: <18E0DD07CFBFD211886600A0C97250B158D611@EXSTUDENT3.Levels.UniSA.Edu.Au> From: "Sayers, Jarrod Michael - SAYJM001" To: "'freebsd-stable@FreeBSD.ORG'" Subject: Date: Wed, 28 Jul 1999 17:35:26 +0930 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 5:41:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 6CCAB15472 for ; Wed, 28 Jul 1999 05:41:50 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.3/8.9.1) id IAA08428; Wed, 28 Jul 1999 08:38:34 -0400 (EDT) (envelope-from mi) Message-Id: <199907281238.IAA08428@misha.cisco.com> Subject: Re: uthread_init.c: 'Cannot get stdio flags' :-( In-Reply-To: <379E8126.3541FDA9@vigrid.com> from "Daniel M. Eischen" at "Jul 28, 1999 00:03:50 am" To: "Daniel M. Eischen" Date: Wed, 28 Jul 1999 08:38:34 -0400 (EDT) Cc: jb@cimlogic.com.au, mi@aldan.algebra.com, stable@freebsd.org Reply-To: mi@aldan.algebra.com From: Mikhail Teterin X-Mailer: ELM [version 2.4ME+ PL60 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel M. Eischen once wrote: > John Birrell wrote: > > Mikhail Teterin wrote: > > > Under what circumstances could a panic: > > > > > > Fatal error 'Cannot get stdio flags' at line ? in file > > > /usr/src/lib/libc_r/uthread/uthread_init.c (errno = ?) > > > > > > be triggered? > > > > > > We are trying to replace HylaFAX's ${PREFIX}/sbin/faxsend with our > > > own application, which is written with threads. The app works fine > > > if called directly -- from command line. But it dies a horrible > > > death when actually invoked by HylaFAX's ${PREFIX}/sbin/faxq. Here > > > is a rather short ktrace produced by replacing faxsend with a > > > shell wrapper: > > > > Looks like ${PREFIX}/sbin/faxq has closed file descriptor 0 (stdin). > > It's legal to do that, so our thread initialisation will have to > > check for EBADF and not fail in that case. > > Assuming it's also legal for stdout and stderr, is this what you had > in mind (not compiled or tested)? Thank you very much! We will try the patch today and let you know. Yours, -mi Index: uthread_init.c =================================================================== RCS file: /opt/b/CVS/src/lib/libc_r/uthread/uthread_init.c,v retrieving revision 1.16 diff -r1.16 uthread_init.c 309,313c309,320 < if ((_thread_fd_table_init(0) != 0) || < (_thread_fd_table_init(1) != 0) || < (_thread_fd_table_init(2) != 0)) { < PANIC("Cannot initialize stdio file descriptor " < "table entries"); --- > if ((_thread_fd_table_init(0) != 0) && > (errno != EBADF)) > PANIC("Cannot initialize stdin file descriptor " > "table entry"); > else if ((_thread_fd_table_init(1) != 0) && > (errno != EBADF)) > PANIC("Cannot initialize stdout file descriptor " > "table entry"); > else if ((_thread_fd_table_init(2) != 0) && > (errno != EBADF)) > PANIC("Cannot initialize stderr file descriptor " > "table entry"); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 8:15:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 8C762154D8 for ; Wed, 28 Jul 1999 08:15:39 -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 RAA84399; Wed, 28 Jul 1999 17:15:28 +0200 (CEST) (envelope-from des) To: Gregory Bond Cc: Christoph Sold , FreeBSD-Stable@FreeBSD.ORG Subject: Re: FAILED make buildword (3.1-R => 3.2-S) References: <199907260011.KAA27998@lightning.itga.com.au> From: Dag-Erling Smorgrav Date: 28 Jul 1999 17:15:26 +0200 In-Reply-To: Gregory Bond's message of "Mon, 26 Jul 1999 10:11:26 +1000" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gregory Bond writes: > > today I fetched the fresh 3.2 stable code using cvsup, starting make > > buildworld. It failed. Since I´m out of my depth here, maybe you could > > help. > [...] > The softupdates files have moved and need new symlinks. This would only affect a kernel build, not a world build. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 8:22:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fed-ef1.frb.gov (fed.frb.gov [132.200.32.32]) by hub.freebsd.org (Postfix) with ESMTP id D576415044 for ; Wed, 28 Jul 1999 08:22:17 -0700 (PDT) (envelope-from seth@freebie.dp.ny.frb.org) Received: by fed-ef1.frb.gov; id LAA14480; Wed, 28 Jul 1999 11:22:00 -0400 (EDT) Received: from m1pmdf.frb.gov(192.168.3.38) by fed.frb.gov via smap (V4.2) id xma014099; Wed, 28 Jul 99 11:21:26 -0400 Date: Wed, 28 Jul 1999 11:21:22 -0400 (EDT) From: Seth Subject: tcpd, inetd, and hosts.[allow|deny] To: freebsd-stable@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found a problem yesterday that might have some security implications for those users using tcpd, either explicitly or through the new (post- 7/21/1999) wrapped inetd. The problem arises because the default directories for the hosts.[allow|deny] files have changed somewhere along the line, and because tcpd utilities (such as tcpdmatch and tcpdchk) have been part of the FreeBSD distribution (the Makefiles are in usr.sbin, but the source is in contrib/tcp_wrappers) since at least 3.1-R. Somewhere along the line (as far as I can tell, somewhere between 3.1-RELEASE and 3.2-STABLE of 6/20), the directories that /usr/sbin/tcpdmatch uses to check for tcpd access files changed from /usr/local/etc to /etc. However, tcpd (NOT installed as part of the distribution) uses access files in /usr/local/etc. This inconsistency means that some users who rely on /usr/sbin/tcpdmatch to check security will get false results, as modern builds (but prior to 7/21) of /usr/sbin/tcpdmatch will check /etc as opposed to /usr/local/etc. /usr/local/sbin/tcpdmatch, installed with tcpd, checks /usr/local/etc correctly. Now, part two. If you've been using /usr/local/libexec/tcpd and associated access files in /usr/local/etc, and you've recently updated (after 7/21) and are now running inetd with -w, note that this wrapped inetd expects the files to be in /etc, not /usr/local/etc (which is where your old tcpd wanted them). If you happen to use /usr/local/sbin/tcpdmatch (the one that comes in the tcpd package) instead of the included /usr/sbin/tcpdmatch, you'll get false results, as /usr/local/sbin/tcpdmatch checks access files in /usr/local/etc. I filed a bug report about this yesterday (bin/12819). I happen to feel that this is a serious problem, although that's been debated. Doesn't matter. Just be aware that the behavior has changed and that you need to be aware that your access files may need to be moved. Milestones & summary: 3.1-RELEASE: /usr/sbin/tcpdmatch confirmed to check /usr/local/etc. /usr/local/sbin/tcpdmatch, part of tcpd package, checks /usr/local/etc. -STABLE of 6/20: /usr/sbin/tcpdmatch has changed somewhere along the line. Checks /etc by default now, even though tcpd isn't integrated into the distribution and expects access files in /usr/local/etc. /usr/local/sbin/tcpdmatch continues to check /usr/local/etc. -STABLE of 7/21: inetd now wraps; expects access files in /etc. /usr/local/sbin/tcpdmatch continues to check /usr/local/etc. Sorry for the long-winded message, but I wanted to explain the issue as thoroughly as I could. Also, thanks to Sheldon and the freebsd-bugs team for following up on this pr so promptly. SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 9:24:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tornado.cisco.com (tornado.cisco.com [171.69.104.22]) by hub.freebsd.org (Postfix) with ESMTP id BA5A914BE2; Wed, 28 Jul 1999 09:24:24 -0700 (PDT) (envelope-from lawlopez@cisco.com) Received: from cisco.com (lawlopez-pc.cisco.com [171.69.206.56]) by tornado.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id MAA28905; Wed, 28 Jul 1999 12:22:47 -0400 (EDT) Message-ID: <379F2E59.FA8EA348@cisco.com> Date: Wed, 28 Jul 1999 12:22:49 -0400 From: "Lawrence D. Lopez" Organization: Cisco Systems/Network Masters/L3 Data Systems X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: mi@aldan.algebra.com Cc: questions@freebsd.org, stable@freebsd.org, eischen@vigrid.com, jb@cimlogic.com.au Subject: Re: uthread_init.c: 'Cannot get stdio flags' :-( References: <199907280157.VAA07727@misha.cisco.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh shucks, give me something hard. HylaFAX closed fd 0 before it did a fork exec. Threads require fd 0 to exist. Larry Mikhail Teterin wrote: > > Hello! > > Under what circumstances could a panic: > > Fatal error 'Cannot get stdio flags' at line ? in file > /usr/src/lib/libc_r/uthread/uthread_init.c (errno = ?) > > be triggered? > > We are trying to replace HylaFAX's ${PREFIX}/sbin/faxsend with our own > application, which is written with threads. The app works fine if called > directly -- from command line. But it dies a horrible death when > actually invoked by HylaFAX's ${PREFIX}/sbin/faxq. Here is a rather > short ktrace produced by replacing faxsend with a shell wrapper: > > 1157 ktrace RET ktrace 0 > 1157 ktrace CALL execve(0xbfbfdc23,0xbfbfdaec,0xbfbfdb00) > 1157 ktrace NAMI "/usr/local/sbin/faxsend.bin" > 1157 faxsend.bin RET execve 0 > 1157 faxsend.bin CALL getpid > 1157 faxsend.bin RET getpid 1157/0x485 > 1157 faxsend.bin CALL fcntl(0,0x3,0) > 1157 faxsend.bin RET fcntl -1 errno 9 Bad file descriptor > 1157 faxsend.bin CALL write(0x2,0xbfbfd9ac,0x6e) > 1157 faxsend.bin GIO fd 2 wrote 110 bytes > "Fatal error 'Cannot get stdio flags' at line ? in file /usr/src/lib/libc_r/ut\ > hread/uthread_init.c (errno = ?) > " > 1157 faxsend.bin RET write 110/0x6e > 1157 faxsend.bin CALL setitimer(0x2,0xbfbfd968,0) > 1157 faxsend.bin RET setitimer 0 > 1157 faxsend.bin CALL close(0xffffffff) > 1157 faxsend.bin RET close -1 errno 9 Bad file descriptor > 1157 faxsend.bin CALL close(0xffffffff) > 1157 faxsend.bin RET close -1 errno 9 Bad file descriptor > 1157 faxsend.bin PSIG SIGSEGV SIG_DFL > > First the thread library panics and then segfaults before our main() > even gets a chance to do anything... > > The entire app is compiled with "-D_THREADSAFE -pthread" and linked with > "-pthread -static" (tried dynamic too). The only other library -- -lm is > not rebuilt with thread awareness, though. > > The problem is perfectly reproducible on FreeBSD 3.0-RELEASE as well as > on 3.2-RELEASE... > > Thanks in advance for any hints. Yours sincerely, > > -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 10: 2:52 1999 Delivered-To: freebsd-stable@freebsd.org Received: from extra.gc.lviv.ua (extra.gc.lviv.ua [195.5.56.19]) by hub.freebsd.org (Postfix) with ESMTP id 6CB7014D70 for ; Wed, 28 Jul 1999 10:02:45 -0700 (PDT) (envelope-from vadim@gc.lviv.ua) Received: from gate.gc.lviv.ua (gate.gc.lviv.ua [192.168.168.18]) by extra.gc.lviv.ua (8.9.3/8.9.3) with ESMTP id UAA76476 for ; Wed, 28 Jul 1999 20:01:17 +0300 (EEST) Received: from gc.lviv.ua (intra.lviv.gc.com.ua [192.168.1.93]) by gate.gc.lviv.ua (8.9.3/8.9.3) with ESMTP id TAA20598 for ; Wed, 28 Jul 1999 19:59:54 +0300 (EEST) Message-ID: <379F3650.38C590CD@gc.lviv.ua> Date: Wed, 28 Jul 1999 19:56:48 +0300 From: Vadim Chekan Organization: Galitsky Kontrakty X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: "stable@FreeBSD.ORG" Subject: Bison update request Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello everyone! Which version of bison is there in Current? In 3.2-release it's 1.25 which is dated 1995! It's buggy. What about update to bison-1.28? Vadim Chekan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 10: 3:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by hub.freebsd.org (Postfix) with ESMTP id 0293A154C0 for ; Wed, 28 Jul 1999 10:03:27 -0700 (PDT) (envelope-from george@dblab.ece.ntua.gr) Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id UAA25422; Wed, 28 Jul 1999 20:03:02 +0300 (EEST) Received: from hawk.dbnet.ece.ntua.gr (hawk.dbnet.ece.ntua.gr [147.102.12.8]) by dblab.ece.ntua.gr (8.9.3/8.9.3) with ESMTP id UAA34140; Wed, 28 Jul 1999 20:03:01 +0300 (EEST) Received: (from george@localhost) by hawk.dbnet.ece.ntua.gr (8.9.3/8.9.2) id UAA60070; Wed, 28 Jul 1999 20:03:00 +0300 (EEST) Date: Wed, 28 Jul 1999 20:02:59 +0300 From: Yiorgos Adamopoulos To: Seth Cc: freebsd-stable@FreeBSD.ORG Subject: Re: tcpd, inetd, and hosts.[allow|deny] Message-ID: <19990728200259.A60026@dblab.ece.ntua.gr> Reply-To: adamo@dblab.ece.ntua.gr References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Seth on Wed, Jul 28, 1999 at 11:21:22AM -0400 X-Organization: Knowledge and Data Base Systems Laboratory, National Technical University of Athens, GREECE X-URL: http://home.eu.org/~adamo X-Alt-Email: adamo@ieee.org X-Work-Phone: +30-1-772-1-436 X-Work-FAX: +30-1-772-1-442 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 28, 1999 at 11:21:22AM -0400, Seth wrote: > Somewhere along the line (as far as I can tell, somewhere between > 3.1-RELEASE and 3.2-STABLE of 6/20), the directories that > /usr/sbin/tcpdmatch uses to check for tcpd access files changed from > /usr/local/etc to /etc. However, tcpd (NOT installed as part of the > distribution) uses access files in /usr/local/etc. This inconsistency > means that some users who rely on /usr/sbin/tcpdmatch to check security > will get false results, as modern builds (but prior to 7/21) of > /usr/sbin/tcpdmatch will check /etc as opposed to /usr/local/etc. > /usr/local/sbin/tcpdmatch, installed with tcpd, checks /usr/local/etc > correctly. Peculiar though it may seem, I would call this expected behaviour. Why? tcpd is installed from /usr/ports/security/tcp_wrappers right? So it uses /usr/local/etc/hosts.{allow,deny} and /usr/local/sbin/tcpdmatch is installed *with* tcpd from the ports collection. OTOH, /usr/sbin/tcpdmatch in installed on the *system* (read make World) and checks /etc/hosts.{allow,deny} since this is what the tcp_wrappers aware inetd uses (and you need a tcpdmatch to check these, right?). But if you have tcpd capability in inetd, why do you now need to explicitly install tcpd? (That is if you run the FreeBSD inetd). -- ieee.org!adamo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 10:30:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by hub.freebsd.org (Postfix) with ESMTP id 2BD4D14D70 for ; Wed, 28 Jul 1999 10:30:05 -0700 (PDT) (envelope-from george@dblab.ece.ntua.gr) Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id UAA26457; Wed, 28 Jul 1999 20:29:55 +0300 (EEST) Received: from hawk.dbnet.ece.ntua.gr (hawk.dbnet.ece.ntua.gr [147.102.12.8]) by dblab.ece.ntua.gr (8.9.3/8.9.3) with ESMTP id UAA34296; Wed, 28 Jul 1999 20:29:55 +0300 (EEST) Received: (from george@localhost) by hawk.dbnet.ece.ntua.gr (8.9.3/8.9.2) id UAA80330; Wed, 28 Jul 1999 20:29:55 +0300 (EEST) Date: Wed, 28 Jul 1999 20:29:54 +0300 From: Yiorgos Adamopoulos To: Seth Cc: Yiorgos Adamopoulos , freebsd-stable@FreeBSD.ORG Subject: Re: tcpd, inetd, and hosts.[allow|deny] Message-ID: <19990728202954.A75107@dblab.ece.ntua.gr> Reply-To: adamo@dblab.ece.ntua.gr References: <19990728200259.A60026@dblab.ece.ntua.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Seth on Wed, Jul 28, 1999 at 01:17:26PM -0400 X-Organization: Knowledge and Data Base Systems Laboratory, National Technical University of Athens, GREECE X-URL: http://home.eu.org/~adamo X-Alt-Email: adamo@ieee.org X-Work-Phone: +30-1-772-1-436 X-Work-FAX: +30-1-772-1-442 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 28, 1999 at 01:17:26PM -0400, Seth wrote: > administrative point of view. The access files must be moved from > /usr/local/etc to /etc in order for a default wrapped inetd config to > access them. Any administrator who relied on wrapping and who made the Now this is where I disagree. The default /etc/hosts.allow allows every connection. Which is OK, since if you cut-n-paste your old inetd.conf tcpd wrapped lines, inetd will execute tcpd, who (tcpd) will check /usr/local/etc/hosts.{allow,deny} which will do what the administrator expects. -- ieee.org!adamo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 10:42:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fed-ef1.frb.gov (fed.frb.gov [132.200.32.32]) by hub.freebsd.org (Postfix) with ESMTP id 0632715033 for ; Wed, 28 Jul 1999 10:42:10 -0700 (PDT) (envelope-from seth@freebie.dp.ny.frb.org) Received: by fed-ef1.frb.gov; id NAA26805; Wed, 28 Jul 1999 13:42:09 -0400 (EDT) Received: from m1pmdf.frb.gov(192.168.3.38) by fed.frb.gov via smap (V4.2) id xma026626; Wed, 28 Jul 99 13:41:57 -0400 Date: Wed, 28 Jul 1999 13:41:52 -0400 (EDT) From: Seth Subject: Re: tcpd, inetd, and hosts.[allow|deny] In-reply-to: <19990728202954.A75107@dblab.ece.ntua.gr> To: Yiorgos Adamopoulos Cc: freebsd-stable@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Jul 1999, Yiorgos Adamopoulos wrote: > On Wed, Jul 28, 1999 at 01:17:26PM -0400, Seth wrote: > > administrative point of view. The access files must be moved from > > /usr/local/etc to /etc in order for a default wrapped inetd config to > > access them. Any administrator who relied on wrapping and who made the > > Now this is where I disagree. The default /etc/hosts.allow allows every > connection. Which is OK, since if you cut-n-paste your old inetd.conf tcpd > wrapped lines, inetd will execute tcpd, who (tcpd) will check > /usr/local/etc/hosts.{allow,deny} which will do what the administrator expects. > Not sure I follow you. Assume for a moment that you've been using the tcpd package and have created a custom /usr/local/etc/hosts.deny to filter, say, ftp attempts from some domain. Ignore for the moment that the tcpdmatch that comes with FreeBSD base distributions past some point in time after 3.1-R won't check these files by default (my first original point). Your tcpd, installed as /usr/local/libexec/tcpd, works fine with your /usr/local/etc/hosts.deny. You've now made world using post-7/12 sources and decided to use this new feature -- wrapping from inetd -- as opposed to tcpd. Hey, why use an external program when inetd is more than happy to do it for you? You remove all the references to /usr/local/libexec/tcpd from your /etc/inetd.conf, and restart inetd with -w. You're now vulnerable to all the access attempts you were protecting before you converted to wrapped inetd, since the wrapped inetd looks in /etc for the access files. Since yours are still in /usr/local/etc, you're wide open until you move them. SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 10:53:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shemp.palomine.net (shemp.palomine.net [205.198.88.200]) by hub.freebsd.org (Postfix) with SMTP id 952D714C0E for ; Wed, 28 Jul 1999 10:53:15 -0700 (PDT) (envelope-from cjohnson@palomine.net) Received: (qmail 13355 invoked by uid 1000); 28 Jul 1999 17:52:05 -0000 Date: Wed, 28 Jul 1999 13:52:05 -0400 From: Chris Johnson To: Seth Cc: freebsd-stable@FreeBSD.ORG Subject: Re: tcpd, inetd, and hosts.[allow|deny] Message-ID: <19990728135205.A13283@palomine.net> References: <19990728202954.A75107@dblab.ece.ntua.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Seth on Wed, Jul 28, 1999 at 01:41:52PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 28, 1999 at 01:41:52PM -0400, Seth wrote: > > > On Wed, 28 Jul 1999, Yiorgos Adamopoulos wrote: > > > On Wed, Jul 28, 1999 at 01:17:26PM -0400, Seth wrote: > > > administrative point of view. The access files must be moved from > > > /usr/local/etc to /etc in order for a default wrapped inetd config to > > > access them. Any administrator who relied on wrapping and who made the > > > > Now this is where I disagree. The default /etc/hosts.allow allows every > > connection. Which is OK, since if you cut-n-paste your old inetd.conf tcpd > > wrapped lines, inetd will execute tcpd, who (tcpd) will check > > /usr/local/etc/hosts.{allow,deny} which will do what the administrator > > expects. > > > > Not sure I follow you. Assume for a moment that you've been using the tcpd > package and have created a custom /usr/local/etc/hosts.deny to filter, say, > ftp attempts from some domain. Ignore for the moment that the tcpdmatch that > comes with FreeBSD base distributions past some point in time after 3.1-R > won't check these files by default (my first original point). Your tcpd, > installed as /usr/local/libexec/tcpd, works fine with your > /usr/local/etc/hosts.deny. > > You've now made world using post-7/12 sources and decided to use this new > feature -- wrapping from inetd -- as opposed to tcpd. Hey, why use an > external program when inetd is more than happy to do it for you? You remove > all the references to /usr/local/libexec/tcpd from your /etc/inetd.conf, and > restart inetd with -w. But before you blindly remove all references to /usr/local/libexec/tcpd, you read the man page for the new inetd, which refers you to hosts_access(5). You read that and see that the files are now in /etc. And even if you don't read the man page, it occurs to you that since inetd is a part of the base distribution, it'd never be looking at a file in /usr/local/etc anyway. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 10:59:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id 33B0814FF1 for ; Wed, 28 Jul 1999 10:59:56 -0700 (PDT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 119Xbj-000656-00 for freebsd-stable@FreeBSD.ORG; Wed, 28 Jul 1999 13:35:11 -0400 Date: Wed, 28 Jul 1999 13:35:11 -0400 From: Peter Radcliffe To: freebsd-stable@FreeBSD.ORG Subject: Re: tcpd, inetd, and hosts.[allow|deny] Message-ID: <19990728133511.F20777@pir.net> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <19990728200259.A60026@dblab.ece.ntua.gr> <19990728202954.A75107@dblab.ece.ntua.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990728202954.A75107@dblab.ece.ntua.gr>; from Yiorgos Adamopoulos on Wed, Jul 28, 1999 at 08:29:54PM +0300 X-fish: < Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yiorgos Adamopoulos probably said: > Now this is where I disagree. The default /etc/hosts.allow allows > every connection. Which is OK, since if you cut-n-paste your old > inetd.conf tcpd wrapped lines, inetd will execute tcpd, who (tcpd) > will check /usr/local/etc/hosts.{allow,deny} which will do what the > administrator expects. Not always true. tcpd is linked dynamicly with libwrap, it depends which libwrap.so is first in the linker's search. When I went to 3.2 my older tcpd started using /etc/hosts.*. P. -- pir pir@pir.net pir@shore.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 11: 8:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fed-ef1.frb.gov (fed.frb.gov [132.200.32.32]) by hub.freebsd.org (Postfix) with ESMTP id D0A5914C3F for ; Wed, 28 Jul 1999 11:08:52 -0700 (PDT) (envelope-from seth@freebie.dp.ny.frb.org) Received: by fed-ef1.frb.gov; id OAA20851; Wed, 28 Jul 1999 14:08:00 -0400 (EDT) Received: from m1pmdf.frb.gov(192.168.3.38) by fed.frb.gov via smap (V4.2) id xma020100; Wed, 28 Jul 99 14:07:14 -0400 Date: Wed, 28 Jul 1999 14:07:11 -0400 (EDT) From: Seth Subject: Re: tcpd, inetd, and hosts.[allow|deny] In-reply-to: <19990728135205.A13283@palomine.net> To: Chris Johnson Cc: freebsd-stable@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Jul 1999, Chris Johnson wrote: > But before you blindly remove all references to /usr/local/libexec/tcpd, you > read the man page for the new inetd, which refers you to hosts_access(5). You > read that and see that the files are now in /etc. And even if you don't read > the man page, it occurs to you that since inetd is a part of the base > distribution, it'd never be looking at a file in /usr/local/etc anyway. > > Chris > Yes. *I* would do that (and did, which is why I saw the problem). This was not a "hey, you guys, you got it wrong!" message. This was a "hey, I ran across this set of inconsistencies and wanted to make sure people weren't relying on false assumptions." Two things still stand out: 1) tcpdchk and tcpdmatch were included as part of the base distribution prior to having a wrapped inetd. Their default behavior was changed before 6/20: it went from checking /usr/local/etc to /etc. This wasn't documented on the list, afaict. My CTM update did a wholesale replacement of tcpdmatch.8 on 20 April. I can't tell whether this was the change. 2) I am not suggesting that the documentation is incorrect. The documentation has been consistent throughout. IMHO, however, whenever you make a substantive change to a security feature, you should point out explicitly what else is affected. You shouldn't rely on the users to figure out that they need to read a new hosts_access manpage, especially when they're familiar with the old hosts_access manpage and nobody's told them that the files have moved. Or maybe you should. But it doesn't cost much to just throw in a paragraph titled "SIDE EFFECTS" or something to that effect whenever you do something like this, and it protects those people who are unfamiliar enough with the changes not to realize that the change is not as simple as it looks. SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 11:21: 4 1999 Delivered-To: freebsd-stable@freebsd.org Received: from voyager.fisicc-ufm.edu (ip-46-094.guate.net [200.12.46.94]) by hub.freebsd.org (Postfix) with ESMTP id 61B0614CB3 for ; Wed, 28 Jul 1999 11:20:23 -0700 (PDT) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id MAA00841; Wed, 28 Jul 1999 12:16:57 -0600 (CST) (envelope-from obonilla) Date: Wed, 28 Jul 1999 12:16:57 -0600 From: Oscar Bonilla To: Vadim Chekan Cc: "stable@FreeBSD.ORG" Subject: Re: Bison update request Message-ID: <19990728121656.C420@fisicc-ufm.edu> References: <379F3650.38C590CD@gc.lviv.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <379F3650.38C590CD@gc.lviv.ua>; from Vadim Chekan on Wed, Jul 28, 1999 at 07:56:48PM +0300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 28, 1999 at 07:56:48PM +0300, Vadim Chekan wrote: > Hello everyone! > > Which version of bison is there in Current? > In 3.2-release it's 1.25 which is dated 1995! > It's buggy. What about update to bison-1.28? > For what I've read in -current it seems bison is on its way out. better use yacc. (i might be wrong :) -Oscar -- For PGP Public Key: finger obonilla@fisicc-ufm.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 11:25:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16]) by hub.freebsd.org (Postfix) with ESMTP id 4FA7214CB3 for ; Wed, 28 Jul 1999 11:25:36 -0700 (PDT) (envelope-from dglynn@vaview5.vavu.vt.edu) Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16]) by vaview5.vavu.vt.edu (8.8.8/8.8.7) with SMTP id OAA01335 for ; Wed, 28 Jul 1999 14:25:06 -0400 (EDT) (envelope-from dglynn@vaview5.vavu.vt.edu) Date: Wed, 28 Jul 1999 14:25:05 -0400 (EDT) From: Greg Lynn To: stable@FreeBSD.ORG Subject: tty buffer overflows... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any way to fix this problem: /kernel: sio0: 233 more tty-level buffer overflows Can this be fixed by compiling in some sio flags for the buffer sizes? -Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 12:28: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fed-ef1.frb.gov (fed.frb.gov [132.200.32.32]) by hub.freebsd.org (Postfix) with ESMTP id 3CB1914CF3 for ; Wed, 28 Jul 1999 12:27:48 -0700 (PDT) (envelope-from seth@freebie.dp.ny.frb.org) Received: by fed-ef1.frb.gov; id NAA07428; Wed, 28 Jul 1999 13:18:25 -0400 (EDT) Received: from m1pmdf.frb.gov(192.168.3.38) by fed.frb.gov via smap (V4.2) id xma006935; Wed, 28 Jul 99 13:17:32 -0400 Date: Wed, 28 Jul 1999 13:17:26 -0400 (EDT) From: Seth Subject: Re: tcpd, inetd, and hosts.[allow|deny] In-reply-to: <19990728200259.A60026@dblab.ece.ntua.gr> To: Yiorgos Adamopoulos Cc: freebsd-stable@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Jul 1999, Yiorgos Adamopoulos wrote: > Peculiar though it may seem, I would call this expected behaviour. Why? > > tcpd is installed from /usr/ports/security/tcp_wrappers right? So it uses > /usr/local/etc/hosts.{allow,deny} and /usr/local/sbin/tcpdmatch is installed > *with* tcpd from the ports collection. > > OTOH, /usr/sbin/tcpdmatch in installed on the *system* (read make World) and > checks /etc/hosts.{allow,deny} since this is what the tcp_wrappers aware inetd > uses (and you need a tcpdmatch to check these, right?). > > But if you have tcpd capability in inetd, why do you now need to explicitly > install tcpd? (That is if you run the FreeBSD inetd). > The issue is one of timing. I agree that IF tcpd were part of the base install (in /usr/libexec, for example), it would make sense (and there would be no need to use the port). However, my first point was that prior to the introduction of the wrapped inetd, tcpdmatch and tcpdcheck were provided -- WITHOUT an accompanying tcpd -- in /usr/sbin. They originally checked /usr/local/etc. Sometime between 3.1-RELEASE and 6/20 -STABLE, these utilities were changed to check /etc as opposed to /usr/local/etc, and thus could not have been expected to perform any useful function prior to the inetd wrap of 7/21. What were they there for? All they did was create confusion for many reasons; primary among them was the fact that most people have /usr/sbin BEFORE /usr/local/sbin in their paths and thus were executing the wrong version of tcpdmatch... the version that wouldn't read the files that tcpd was reading. With the introduction of inetd wrapping, the /usr/sbin/tcpd* utilities serve their intended purpose, since they check /etc, which is where inetd expects the rules. My second point was that the move from a locally-installed tcpd to the wrapped inetd was not seamless from an administrative point of view. The access files must be moved from /usr/local/etc to /etc in order for a default wrapped inetd config to access them. Any administrator who relied on wrapping and who made the change to inetd to enable wrapping but did not move their rules files actually defeated his own security measures. That's a scenario that didn't get much airtime, and the point of my last post was to make people aware of the issues involved. SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 14: 5: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from alice.gba.oz.au (gba-254.tmx.com.au [203.9.155.254]) by hub.freebsd.org (Postfix) with SMTP id B14D7154EB for ; Wed, 28 Jul 1999 14:04:57 -0700 (PDT) (envelope-from gjb-freebsd@gba.oz.au) Received: (qmail 5796 invoked by uid 1001); 29 Jul 1999 07:01:29 +1000 Message-ID: <19990728210129.5795.qmail@alice.gba.oz.au> X-Posted-By: GBA-Post 1.03 20-Sep-1998 X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 Date: Thu, 29 Jul 1999 07:01:28 +1000 From: Greg Black To: freebsd-stable@FreeBSD.ORG Cc: gdsntusr@globaldelsys.com, Oliver Fromme Subject: Re: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms References: <199907272205.AAA10989@dorifer.heim3.tu-clausthal.de> In-reply-to: <199907272205.AAA10989@dorifer.heim3.tu-clausthal.de> of Wed, 28 Jul 1999 00:05:07 +0200 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fromme writes: > olli@dao-lin-hay:/tmp> touch foobar > olli@dao-lin-hay:/tmp> truncate `echo "2^43 - 1" | bc` foobar > olli@dao-lin-hay:/tmp> ls -l foobar > -rw-r--r-- 1 olli wheel 8796093022207 Jul 27 23:55 foobar > olli@dao-lin-hay:/tmp> > > That's 8 Tbyte - 1. Impressive, isn't it? :) Depends on your concept of impressive. Look at this minor variation: $ df . Filesystem 1K-blocks Used Avail Capacity Mounted on mfs:36 63503 14 58409 0% /tmp $ touch foo $ truncate `echo "2^43 - 1" | bc` foo $ ls -ls foo 32 -rw-rw---- 1 gjb wheel 8796093022207 Jul 29 06:49 foo $ df . Filesystem 1K-blocks Used Avail Capacity Mounted on mfs:36 63503 46 58377 0% /tmp I suppose you could claim that fitting a Terabyte+ size file into a 64 Mbyte file system was impressive. But since the file really only uses 32 Kbytes (as shown by the ls(1) and df(1) output), I'd call it a bit of a scam ... -- Greg Black -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 14:18:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id CA74D15544 for ; Wed, 28 Jul 1999 14:17:36 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id XAA00574 for freebsd-stable@FreeBSD.ORG; Wed, 28 Jul 1999 23:17:35 +0200 (CEST) (envelope-from olli) Date: Wed, 28 Jul 1999 23:17:35 +0200 (CEST) From: Oliver Fromme Message-Id: <199907282117.XAA00574@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms Organization: Administration Heim 3 Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Black wrote in list.freebsd-stable: > Oliver Fromme writes: > > > olli@dao-lin-hay:/tmp> touch foobar > > olli@dao-lin-hay:/tmp> truncate `echo "2^43 - 1" | bc` foobar > > olli@dao-lin-hay:/tmp> ls -l foobar > > -rw-r--r-- 1 olli wheel 8796093022207 Jul 27 23:55 foobar > > olli@dao-lin-hay:/tmp> > > > > That's 8 Tbyte - 1. Impressive, isn't it? :) > > Depends on your concept of impressive. Look at this minor > variation: > > $ df . > Filesystem 1K-blocks Used Avail Capacity Mounted on > mfs:36 63503 14 58409 0% /tmp > $ touch foo > $ truncate `echo "2^43 - 1" | bc` foo > $ ls -ls foo > 32 -rw-rw---- 1 gjb wheel 8796093022207 Jul 29 06:49 foo > $ df . > Filesystem 1K-blocks Used Avail Capacity Mounted on > mfs:36 63503 46 58377 0% /tmp > > I suppose you could claim that fitting a Terabyte+ size file > into a 64 Mbyte file system was impressive. But since the file > really only uses 32 Kbytes (as shown by the ls(1) and df(1) > output), I'd call it a bit of a scam ... Well, _of course_ it is creating a sparse file, or did you think that I've got 8 Tbyte of disk space? I wish I had. :-) I meant that the number itself is impressive, and the fact that FreeBSD does support files of that size, whether sparse or not. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 16:46:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (Postfix) with ESMTP id C58D514C3C for ; Wed, 28 Jul 1999 16:46:36 -0700 (PDT) (envelope-from gnb@itga.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id JAA03382; Thu, 29 Jul 1999 09:46:35 +1000 (EST) Received: from lightning.itga.com.au(192.168.71.20) via SMTP by fw.bby.com.au, id smtpd003377; Wed Jul 28 23:46:29 1999 Received: from lightning (lightning [192.168.71.20]) by lightning.itga.com.au (8.9.1a/8.9.1) with ESMTP id JAA05133; Thu, 29 Jul 1999 09:46:27 +1000 (EST) Message-Id: <199907282346.JAA05133@lightning.itga.com.au> From: Gregory Bond To: Dag-Erling Smorgrav Cc: Christoph Sold , FreeBSD-Stable@FreeBSD.ORG Subject: Re: FAILED make buildword (3.1-R => 3.2-S) In-reply-to: Your message of 28 Jul 1999 17:15:26 +0200. Date: Thu, 29 Jul 1999 09:46:27 +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This would only affect a kernel build, not a world build. So I would have thought, except that buildworld does the following: cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 ufs/ffs/*.h /usr/obj/usr/src/tmp/usr/include/ufs/ffs which fails is the softupdates symlinks are wrong. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 17:10:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rebel.net.au (rebel.rebel.net.au [203.20.69.66]) by hub.freebsd.org (Postfix) with ESMTP id 9CD5A154EC for ; Wed, 28 Jul 1999 17:10:15 -0700 (PDT) (envelope-from kkenn@rebel.net.au) Received: from 203.20.69.78 (dialup-8.rebel.net.au [203.20.69.78]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id JAA13227 for ; Thu, 29 Jul 1999 09:39:32 +0930 Received: (qmail 2648 invoked from network); 29 Jul 1999 00:09:23 -0000 Received: from localhost (kkenn@127.0.0.1) by localhost with SMTP; 29 Jul 1999 00:09:23 -0000 Date: Thu, 29 Jul 1999 09:39:23 +0930 (CST) From: Kris Kennaway Reply-To: kkenn@rebel.net.au To: Oscar Bonilla Cc: Vadim Chekan , "stable@FreeBSD.ORG" Subject: Re: Bison update request In-Reply-To: <19990728121656.C420@fisicc-ufm.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Jul 1999, Oscar Bonilla wrote: > > Which version of bison is there in Current? > > In 3.2-release it's 1.25 which is dated 1995! > > It's buggy. What about update to bison-1.28? > > For what I've read in -current it seems bison is on its way out. > better use yacc. > > (i might be wrong :) This was stated the other day by David O'Brien as his intention, so it may not be wise to depend on bison being in current forever. However, there's a port at /usr/ports/devel/bison which is currently at 1.27, and could be upgraded to 1.28 either by politely requesting so from the maintainer (wghicks@bellsouth.net) or by send-PRing your own patches :-) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 28 23:42:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id BF55914C38 for ; Wed, 28 Jul 1999 23:42:05 -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 IAA34914; Thu, 29 Jul 1999 08:31:11 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199907290631.IAA34914@gratis.grondar.za> To: Seth Cc: Yiorgos Adamopoulos , freebsd-stable@FreeBSD.ORG Subject: Re: tcpd, inetd, and hosts.[allow|deny] Date: Thu, 29 Jul 1999 08:31:10 +0200 From: Mark Murray Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > However, my first point was that prior to the introduction of the > wrapped inetd, tcpdmatch and tcpdcheck were provided -- WITHOUT an > accompanying tcpd -- in /usr/sbin. Wrong. When I pulled wrappers into the base system, inetd was done _at_the_ _same_time_. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 29 0:21: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from volodya.prime.net.ua (volodya.prime.net.ua [195.64.229.17]) by hub.freebsd.org (Postfix) with ESMTP id 56BCF15595 for ; Thu, 29 Jul 1999 00:20:46 -0700 (PDT) (envelope-from andyo@prime.net.ua) Received: from prime.net.ua (localhost [127.0.0.1]) by volodya.prime.net.ua (8.9.3/8.8.8) with ESMTP id KAA01052; Thu, 29 Jul 1999 10:13:14 +0300 (EEST) (envelope-from andyo@prime.net.ua) Message-ID: <379FFF08.43E46539@prime.net.ua> Date: Thu, 29 Jul 1999 10:13:13 +0300 From: "Andy V. Oleynik" Organization: M-Info X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en, ru, uk MIME-Version: 1.0 To: Greg Lynn Cc: stable@FreeBSD.ORG Subject: Re: tty buffer overflows... References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I may be wrong but it seems to me that the only way to get rid is advance CPU performance. Greg Lynn wrote: > Is there any way to fix this problem: > > /kernel: sio0: 233 more tty-level buffer overflows > > Can this be fixed by compiling in some sio > flags for the buffer sizes? > > -Greg > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- WBW Andy V. Oleynik (When U work in virtual office prime.net.ua's U have good chance to obtain system administrator virtual money ö%-) +380442448363 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 29 0:21:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from extra.gc.lviv.ua (extra.gc.lviv.ua [195.5.56.19]) by hub.freebsd.org (Postfix) with ESMTP id 434351557C for ; Thu, 29 Jul 1999 00:21:27 -0700 (PDT) (envelope-from vadim@gc.lviv.ua) Received: from gate.gc.lviv.ua (gate.gc.lviv.ua [192.168.168.18]) by extra.gc.lviv.ua (8.9.3/8.9.3) with ESMTP id KAA78514 for ; Thu, 29 Jul 1999 10:20:53 +0300 (EEST) Received: from gc.lviv.ua (intra.lviv.gc.com.ua [192.168.1.93]) by gate.gc.lviv.ua (8.9.3/8.9.3) with ESMTP id KAA71666 for ; Thu, 29 Jul 1999 10:19:28 +0300 (EEST) Message-ID: <379FFFCF.992175D0@gc.lviv.ua> Date: Thu, 29 Jul 1999 10:16:32 +0300 From: Vadim Chekan Organization: Galitsky Kontrakty X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: "stable@FreeBSD.ORG" Subject: Re: Bison update request References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Wed, 28 Jul 1999, Oscar Bonilla wrote: > > > > Which version of bison is there in Current? > > > In 3.2-release it's 1.25 which is dated 1995! > > > It's buggy. What about update to bison-1.28? > > > > For what I've read in -current it seems bison is on its way out. > > better use yacc. > > > > (i might be wrong :) > > This was stated the other day by David O'Brien as his intention, so it may > not be wise to depend on bison being in current forever. However, there's Did I miss somesing? Why Bison is bad and is there anyting better (and free)? > a port at /usr/ports/devel/bison which is currently at 1.27, and could be > upgraded to 1.28 either by politely requesting so from the maintainer > (wghicks@bellsouth.net) or by send-PRing your own patches :-) Yes, I installed this port. But I still can't understand why stable have got old and buggy bison if there's the new one without known errors. It worthed to me a lot of time to find bug in "bison.simple" template. Only then I started to looking for a recent version. Vadim Chekan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 29 3:59: 8 1999 Delivered-To: freebsd-stable@freebsd.org Received: from home2.ecore.net (home2.ecore.net [212.63.128.224]) by hub.freebsd.org (Postfix) with ESMTP id 84B7015443 for ; Thu, 29 Jul 1999 03:58:31 -0700 (PDT) (envelope-from sold@cheasy.de) Received: from kiste.cheasy.de [212.63.145.25] by home2.ecore.net with ESMTP (SMTPD32-5.04) id A3C5EF90446; Thu, 29 Jul 1999 12:58:13 +0200 Received: (from sold@localhost) by kiste.cheasy.de (8.9.2/8.9.2) id VAA05354; Wed, 28 Jul 1999 21:32:26 +0200 (CEST) (envelope-from sold) From: Christoph Sold Date: Wed, 28 Jul 1999 21:32:26 +0200 (CEST) To: freebsd-stable@FreeBSD.ORG Cc: gdsntusr@globaldelsys.com Subject: Re: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms In-Reply-To: <199907272205.AAA10989@dorifer.heim3.tu-clausthal.de> References: <199907272205.AAA10989@dorifer.heim3.tu-clausthal.de> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14239.22848.139612.71015@kiste.cheasy.de> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fromme writes: > gdsntusr@globaldelsys.com wrote in list.freebsd-stable: > > [...] I was thinking of trying freeBSD with its SCO emulation > > support but I am uncertain whether freeBSD supports files larger than 2GB on > > 32bit x86 platforms. > > It certainly does. > > olli@dao-lin-hay:/tmp> touch foobar > olli@dao-lin-hay:/tmp> truncate `echo "2^43 - 1" | bc` foobar > olli@dao-lin-hay:/tmp> ls -l foobar > -rw-r--r-- 1 olli wheel 8796093022207 Jul 27 23:55 foobar > olli@dao-lin-hay:/tmp> > > That's 8 Tbyte - 1. Impressive, isn't it? :) > > By the way, off_t (the data type used for seeking in files and > other things) is 64 bits in FreeBSD, even on the 32bit i386 > platform, so this is not limiting. This shows FreeBSD is able to create sparse files bigger than 2GB. It does not neccessarily show there are l_seek calls in the icbs emulator supporting 64k file offsets. To answer the original question, look in the sources of the SCO binary emulation for seek functions. If the offset is defined as 64 bit integer, FreeBSD SCO emulation will support random seek in files bigger than 2GB. -Christoph Sold P.S: No, I have not looked into the source. I have no idea where the SCO emulator lives in the source tree. Please correct me if I am wrong. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 29 4:38:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id CB1A714D5F for ; Thu, 29 Jul 1999 04:38:21 -0700 (PDT) (envelope-from dispatch@blackhelicopters.org) Received: (from dispatch@localhost) by blackhelicopters.org (8.8.8/8.8.8) id HAA24115; Thu, 29 Jul 1999 07:37:27 -0400 (EDT) (envelope-from dispatch) From: Dispatcher Message-Id: <199907291137.HAA24115@blackhelicopters.org> Subject: Re: Bison update request In-Reply-To: <379FFFCF.992175D0@gc.lviv.ua> from Vadim Chekan at "Jul 29, 1999 10:16:32 am" To: vadim@gc.lviv.ua (Vadim Chekan) Date: Thu, 29 Jul 1999 07:37:27 -0400 (EDT) Cc: stable@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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vadim, Bison was used to support gcc, which is the compiler used in 3.x. The version of gcc 3.2 uses is also old, so we need a matching bison. -current uses egcs. We can easily use yacc with it, with only a few changes. The motivation is: Yacc has a BSD license, while Bison has a GNU license. ==ml [Charset koi8-r unsupported, filtering to ASCII...] > > > Kris Kennaway wrote: > > > > On Wed, 28 Jul 1999, Oscar Bonilla wrote: > > > > > > Which version of bison is there in Current? > > > > In 3.2-release it's 1.25 which is dated 1995! > > > > It's buggy. What about update to bison-1.28? > > > > > > For what I've read in -current it seems bison is on its way out. > > > better use yacc. > > > > > > (i might be wrong :) > > > > This was stated the other day by David O'Brien as his intention, so it may > > not be wise to depend on bison being in current forever. However, there's > > Did I miss somesing? Why Bison is bad and is there anyting better (and > free)? > > > a port at /usr/ports/devel/bison which is currently at 1.27, and could be > > upgraded to 1.28 either by politely requesting so from the maintainer > > (wghicks@bellsouth.net) or by send-PRing your own patches :-) > > Yes, I installed this port. But I still can't understand why stable have > got old and buggy bison if there's the new one without known errors. It > worthed to me a lot of time to find bug in "bison.simple" template. Only > then I started to looking for a recent version. > > Vadim Chekan. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 29 7: 7:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fed-ef1.frb.gov (fed.frb.gov [132.200.32.32]) by hub.freebsd.org (Postfix) with ESMTP id 536D9155BD for ; Thu, 29 Jul 1999 07:07:40 -0700 (PDT) (envelope-from seth@freebie.dp.ny.frb.org) Received: by fed-ef1.frb.gov; id KAA15761; Thu, 29 Jul 1999 10:05:32 -0400 (EDT) Received: from m1pmdf.frb.gov(192.168.3.38) by fed.frb.gov via smap (V4.2) id xma015374; Thu, 29 Jul 99 10:04:59 -0400 Date: Thu, 29 Jul 1999 10:04:45 -0400 (EDT) From: Seth Subject: Re: tcpd, inetd, and hosts.[allow|deny] In-reply-to: <199907290631.IAA34914@gratis.grondar.za> To: Mark Murray Cc: Yiorgos Adamopoulos , freebsd-stable@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Then I can't explain why, on my June 11 build, I had /usr/sbin/tcpdmatch, /usr/sbin/tcpdchk, but no wrapped inetd or tcpd other than /usr/local/libexec/tcpd. Nor did I have anything in my inetd manpage indicating -W or -w support. I also had, from the tcpd install, /usr/local/sbin/tcpdmatch and /usr/local/sbin/tcpdchk. From the cvs repository, on March 14, v1.1 by markm: "Build tcp_wappers' userland. I am not building tcpd, because in a day or two, inetd will gain the necessary functionality. At that stage, I'll make wrapping the default for sendmail and portmapper as well." However, inetd didn't gain the necessary *command-line* functionality until July 21. It was there before (buggy on March 28?), but it required a rebuild of inetd with compile-time options, which were not passed by default. Thus, users who were unaware that inetd needed to be rebuilt with new options suddenly found themselves with userland tcpdchk and tcpdmatch that didn't do anything. I'd wager that most users were unaware that these two files had even migrated to userland on March 14. In any case, my 6/11 build didn't even have -w or -W in the inetd manpages. The man page updates appear to have come on June 17, v1.9., and June 22 (I'm not a CVS guru, so I can't be 100% sure). The long and short of it is this: users who built world after March 14 but before July 22, AND who didn't change inetd's Makefile to build inetd with the proper flags, wound up in a (potentially) precarious position. If you'd like, I can show you an example of a system (not mine; I've since upgraded) where this is the case. SB On Thu, 29 Jul 1999, Mark Murray wrote: > > However, my first point was that prior to the introduction of the > > wrapped inetd, tcpdmatch and tcpdcheck were provided -- WITHOUT an > > accompanying tcpd -- in /usr/sbin. > > Wrong. > > When I pulled wrappers into the base system, inetd was done _at_the_ > _same_time_. > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 29 8:16:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from extra.gc.lviv.ua (extra.gc.lviv.ua [195.5.56.19]) by hub.freebsd.org (Postfix) with ESMTP id 3941114C8F for ; Thu, 29 Jul 1999 08:16:14 -0700 (PDT) (envelope-from vadim@gc.lviv.ua) Received: from gate.gc.lviv.ua (gate.gc.lviv.ua [192.168.168.18]) by extra.gc.lviv.ua (8.9.3/8.9.3) with ESMTP id SAA80337 for ; Thu, 29 Jul 1999 18:15:28 +0300 (EEST) Received: from gc.lviv.ua (intra.lviv.gc.com.ua [192.168.1.93]) by gate.gc.lviv.ua (8.9.3/8.9.3) with ESMTP id SAA98591 for ; Thu, 29 Jul 1999 18:13:53 +0300 (EEST) Message-ID: <37A06EF6.97853AF9@gc.lviv.ua> Date: Thu, 29 Jul 1999 18:10:46 +0300 From: Vadim Chekan Organization: Galitsky Kontrakty X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 Cc: stable@FreeBSD.ORG Subject: Re: Bison update request References: <199907291137.HAA24115@blackhelicopters.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dispatcher wrote: > > Vadim, > > Bison was used to support gcc, which is the compiler used in 3.x. The > version of gcc 3.2 uses is also old, so we need a matching bison. > > -current uses egcs. We can easily use yacc with it, with only a few changes. > > The motivation is: > > Yacc has a BSD license, while Bison has a GNU license. > > ==ml Ok. This is a Big Politic. May be yacc is better, but this doesn't mean that "bad" bison in FreeBSD distribution can contain bug. Try this (I suppose bison-1.25): bison test.y && cc -c test.tab.c ===> Start test.y %{ #define YYPARSE_PARAM param %} %token T_STRING %% input: | input T_STRING ; %% ===> End test.y Can you compile this? Here's the patch: --- bison.simple.old Thu Jul 29 17:49:44 1999 +++ bison.simple.new Thu Jul 29 17:50:11 1999 @@ -150,8 +150,12 @@ /* Prevent warning if -Wstrict-prototypes. */ #ifdef __GNUC__ +#ifdef YYPARSE_PARAM +int yyparse (void *); +#else int yyparse (void); #endif +#endif ^L #if __GNUC__ > 1 /* GNU C and GNU C++ define this. */ #define __yy_memcpy(TO,FROM,COUNT) __builtin_memcpy(TO,FROM,COUNT) Shuld I applay bug-report, or this mail is enought? Vadim Chekan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 29 9:35:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 681A7150C5 for ; Thu, 29 Jul 1999 09:35:24 -0700 (PDT) (envelope-from dispatch@blackhelicopters.org) Received: (from dispatch@localhost) by blackhelicopters.org (8.8.8/8.8.8) id MAA24762; Thu, 29 Jul 1999 12:34:29 -0400 (EDT) (envelope-from dispatch) From: Dispatcher Message-Id: <199907291634.MAA24762@blackhelicopters.org> Subject: Re: Bison update request In-Reply-To: <37A06EF6.97853AF9@gc.lviv.ua> from Vadim Chekan at "Jul 29, 1999 6:10:46 pm" To: vadim@gc.lviv.ua (Vadim Chekan) Date: Thu, 29 Jul 1999 12:34:29 -0400 (EDT) Cc: stable@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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok. This is a Big Politic. Absolutely. FreeBSD has just as many politics as any other successful free software project. My advice is: apply your patch and run a "make world." If it goes all the way through, use send-pr to submit the patch. If it breaks world, well, you can track it down or search for the larger issue. Send-pr makes sure that the appropriate people see it, and the problem can be tracked properly. Simply submitting something to -stable, no matter how correct the patch or description is, lets problems become lost in the flood of other email. Best, ==ml To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 29 10:30:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 74BD314C06 for ; Thu, 29 Jul 1999 10:30:22 -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 TAA36821; Thu, 29 Jul 1999 19:29:21 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199907291729.TAA36821@gratis.grondar.za> To: Seth Cc: freebsd-stable@FreeBSD.ORG Subject: Re: tcpd, inetd, and hosts.[allow|deny] Date: Thu, 29 Jul 1999 19:29:19 +0200 From: Mark Murray Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The long and short of it is this: users who built world after March 14 > but before July 22, AND who didn't change inetd's Makefile to build inetd > with the proper flags, wound up in a (potentially) precarious position. That is what commit mail is for. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 29 10:42:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from binnacle.wantabe.com (binnacle.wantabe.com [209.16.8.14]) by hub.freebsd.org (Postfix) with ESMTP id 7C0B614D53 for ; Thu, 29 Jul 1999 10:42:40 -0700 (PDT) (envelope-from jeffrl@wantabe.com) Received: from localhost (jeffrl@localhost) by binnacle.wantabe.com (8.9.2/8.9.2) with ESMTP id MAA89234 for ; Thu, 29 Jul 1999 12:42:33 -0500 (CDT) (envelope-from jeffrl@wantabe.com) X-Authentication-Warning: binnacle.wantabe.com: jeffrl owned process doing -bs Date: Thu, 29 Jul 1999 12:42:33 -0500 (CDT) From: "Jeffrey J. Libman" To: freebsd-stable@FreeBSD.ORG Subject: re: routing over a dual t1 connection (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi. currently my connection is over a single line (isdn), using a unix box and gated with rip/rip2 protocol and what is basically static routes. i now have the opportunity to move to a t1, possibly 2 t1's. i don NOT wish at this time to multi-home my net, but to put both t1's into my upstream provider in order to get the bandwidth. i understand how routing over 2 interfaces works when you are dual homed, using an as number and bgp4, etc. how do i effect routing over 2 interfaces, when i want them to be, in effect, 1 interface, double the bandwidth? is this the "balancing" i keep seeing threads about on this list? any pointers will be appreciated. thanks in advance. cheers, jeff | |\ +------------------------------+ Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | Wantabe, Inc. |__\ +------------------------------+ jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 29 11:33:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from poboxer.pobox.com (ferg5200-1-29.cpinternet.com [208.149.16.29]) by hub.freebsd.org (Postfix) with ESMTP id DE94D15106 for ; Thu, 29 Jul 1999 11:33:49 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id NAA00498; Thu, 29 Jul 1999 13:33:28 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 29 Jul 1999 13:33:28 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: stable@freebsd.org Subject: noatime with softupdates -- superfluous? X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14240.40500.685249.77954@avalon.east> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I used to observe notable speedup for long recursive directory operations by specifying noatime in mounts. Does this really matter any more with softupdates? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 29 11:38:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 8F2601513F for ; Thu, 29 Jul 1999 11:38:33 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Thu, 29 Jul 1999 11:38:31 -0700 From: "David Schwartz" To: "Jeffrey J. Libman" , Subject: RE: routing over a dual t1 connection (fwd) Date: Thu, 29 Jul 1999 11:38:31 -0700 Message-ID: <000801bed9f1$8e8e2aa0$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The best solution I've tried, though far from the cheapest, is to get a CSU/DSU for each end that can 'fuse' the two lines and provide a single serial port at twice the speed of a single T1. If your T1 card can run at 3.088Mbps, you are set. This way, nothing has to change in your routing configuration. Every other solution I've played with has suffered from the following drawbacks: 1) Poor failover if a single line fails. 2) Grossly unequal distribution of traffic. 3) Many packets received out of order. DS > hi. currently my connection is over a single line (isdn), using a unix box > and gated with rip/rip2 protocol and what is basically static routes. > > i now have the opportunity to move to a t1, possibly 2 t1's. > > i don NOT wish at this time to multi-home my net, but to put both t1's > into my upstream provider in order to get the bandwidth. > > i understand how routing over 2 interfaces works when you are dual homed, > using an as number and bgp4, etc. > > how do i effect routing over 2 interfaces, when i want them to be, in > effect, 1 interface, double the bandwidth? is this the "balancing" i keep > seeing threads about on this list? > > any pointers will be appreciated. > > thanks in advance. > > cheers, > jeff > > | > |\ > +------------------------------+ > Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet > Services | > Wantabe, Inc. |__\ > +------------------------------+ > jeffrl@wantabe.com <-----|------> | access web cgi > ftp news mail | > (281) 493-0718 __,.-=\'`^`'~=-../__,.-= > +------------------------------+ > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 29 13:26:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fed-ef1.frb.gov (fed.frb.gov [132.200.32.32]) by hub.freebsd.org (Postfix) with ESMTP id AE53714F98 for ; Thu, 29 Jul 1999 13:26:26 -0700 (PDT) (envelope-from seth@freebie.dp.ny.frb.org) Received: by fed-ef1.frb.gov; id QAA19212; Thu, 29 Jul 1999 16:26:07 -0400 (EDT) Received: from m1pmdf.frb.gov(192.168.3.38) by fed.frb.gov via smap (V4.2) id xmaa18868; Thu, 29 Jul 99 16:25:32 -0400 Date: Thu, 29 Jul 1999 16:24:42 -0400 (EDT) From: Seth Subject: nmap 2.12/2.2b4 stops working after 7/27 build? To: freebsd-stable@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG nmap used to work with -sS -O ... after 7/27 buildworld, it fails with WARNING: Could not determine what interface to route packets through to w.x.y.z, changing ping scantype to ICMP only -e doesn't work either: I cannot figure out what source address to use for device xl1, does it even exist? QUITTING! xl1 is up and active; it's the primary interface for this box. Netmask and default routes are ok. The host to be scanned is on the local subnet. xl0 is down and unconfigured. xl0: flags=8802 mtu 1500 xl1: flags=8843 mtu 1500 Can anyone else reproduce this behavior? Thanks, SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 29 14:19:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fed-ef1.frb.gov (fed.frb.gov [132.200.32.32]) by hub.freebsd.org (Postfix) with ESMTP id 3520314CB5 for ; Thu, 29 Jul 1999 14:19:15 -0700 (PDT) (envelope-from seth@freebie.dp.ny.frb.org) Received: by fed-ef1.frb.gov; id RAA22134; Thu, 29 Jul 1999 17:17:30 -0400 (EDT) Received: from m1pmdf.frb.gov(192.168.3.38) by fed.frb.gov via smap (V4.2) id xma022066; Thu, 29 Jul 99 17:17:15 -0400 Date: Thu, 29 Jul 1999 17:17:09 -0400 (EDT) From: Seth Subject: Re: nmap 2.12/2.2b4 stops working after 7/27 build? In-reply-to: To: freebsd-stable@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry to follow up on my own post, but: bringing up xl0, configuring a bogus IP address on it, then downing it fixes the problem. So I have a workaround, but I'm still wondering what changed. My last build (before July 27th) was June 11. Things were fine until this recent build. SB On Thu, 29 Jul 1999, Seth wrote: > nmap used to work with -sS -O ... after 7/27 buildworld, it fails with > > WARNING: Could not determine what interface to route packets through to > w.x.y.z, changing ping scantype to ICMP only > > > -e doesn't work either: > > I cannot figure out what source address to use for device xl1, does it > even exist? > QUITTING! > > > xl1 is up and active; it's the primary interface for this box. Netmask > and default routes are ok. The host to be scanned is on the local subnet. > xl0 is down and unconfigured. > > xl0: flags=8802 mtu 1500 > xl1: flags=8843 mtu 1500 > > > Can anyone else reproduce this behavior? > > Thanks, > > SB > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 29 15: 8:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 6A881151F5 for ; Thu, 29 Jul 1999 15:08:31 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40331>; Fri, 30 Jul 1999 07:49:23 +1000 Date: Fri, 30 Jul 1999 08:08:18 +1000 From: Peter Jeremy Subject: Re: noatime with softupdates -- superfluous? In-reply-to: <14240.40500.685249.77954@avalon.east> To: alk@pobox.com Cc: stable@FreeBSD.ORG Message-Id: <99Jul30.074923est.40331@border.alcanet.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anthony Kimball wrote: >I used to observe notable speedup for long recursive directory >operations by specifying noatime in mounts. Does this really matter >any more with softupdates? AFAIK, atime updates are already treated as asynchronous, so switching to softupdates should have minimal impact. To put it another way, specifying noatime _will_ enhance the performance of softupdates because it removes the necessity to write the updated inode back to disk. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 29 16:20:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 650151561E for ; Thu, 29 Jul 1999 16:20:52 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from ns1.cybcon.com (wwoods@ns1.cybcon.com [216.190.188.1]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id QAA24150; Thu, 29 Jul 1999 16:20:48 -0700 (PDT) Date: Thu, 29 Jul 1999 16:20:44 -0700 (PDT) From: Bill Woods To: Seth Cc: freebsd-stable@FreeBSD.ORG Subject: Re: nmap 2.12/2.2b4 stops working after 7/27 build? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, this EXACT same thing happened to me on both my laptop and desktop systems William On Thu, 29 Jul 1999, Seth wrote: > nmap used to work with -sS -O ... after 7/27 buildworld, it fails with > > WARNING: Could not determine what interface to route packets through to > w.x.y.z, changing ping scantype to ICMP only > > > -e doesn't work either: > > I cannot figure out what source address to use for device xl1, does it > even exist? > QUITTING! > > > xl1 is up and active; it's the primary interface for this box. Netmask > and default routes are ok. The host to be scanned is on the local subnet. > xl0 is down and unconfigured. > > xl0: flags=8802 mtu 1500 > xl1: flags=8843 mtu 1500 > > > Can anyone else reproduce this behavior? > > Thanks, > > SB > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 29 20:21:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tasam.com (tasam.com [206.161.83.22]) by hub.freebsd.org (Postfix) with ESMTP id 4B09D1504F for ; Thu, 29 Jul 1999 20:21:37 -0700 (PDT) (envelope-from freebsd.list@bug.tasam.com) Received: from bug (209-122-229-157.s538.tnt6.lnh.md.dialup.rcn.com [209.122.229.157]) by tasam.com (8.9.3/8.9.1) with SMTP id XAA19242; Thu, 29 Jul 1999 23:20:23 -0400 (EDT) Message-ID: <008301beda3a$76f94ac0$0286860a@tasam.com> From: "Joe Gleason" To: "David Schwartz" , "Jeffrey J. Libman" , References: <000801bed9f1$8e8e2aa0$021d85d1@youwant.to> Subject: Re: routing over a dual t1 connection (fwd) Date: Thu, 29 Jul 1999 23:20:15 -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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I suggest getting a Cisco 2500 or 2600 series router. They can do the load balancing quite easily and 2 T1's can be attached to either. I know this is a non-freebsd solution, but I have always found that a hardware router with no drives and few moving parts is quite reliable. I know this is not where I should be peddling my wares, but I have a 2500 and a 2600 for sale. ;-) Joe Gleason Tasam > > The best solution I've tried, though far from the cheapest, is to get a > CSU/DSU for each end that can 'fuse' the two lines and provide a single > serial port at twice the speed of a single T1. If your T1 card can run at > 3.088Mbps, you are set. This way, nothing has to change in your routing > configuration. > > Every other solution I've played with has suffered from the following > drawbacks: > > 1) Poor failover if a single line fails. > > 2) Grossly unequal distribution of traffic. > > 3) Many packets received out of order. > > DS > > > hi. currently my connection is over a single line (isdn), using a unix box > > and gated with rip/rip2 protocol and what is basically static routes. > > > > i now have the opportunity to move to a t1, possibly 2 t1's. > > > > i don NOT wish at this time to multi-home my net, but to put both t1's > > into my upstream provider in order to get the bandwidth. > > > > i understand how routing over 2 interfaces works when you are dual homed, > > using an as number and bgp4, etc. > > > > how do i effect routing over 2 interfaces, when i want them to be, in > > effect, 1 interface, double the bandwidth? is this the "balancing" i keep > > seeing threads about on this list? > > > > any pointers will be appreciated. > > > > thanks in advance. > > > > cheers, > > jeff > > > > | > > |\ > > +------------------------------+ > > Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet > > Services | > > Wantabe, Inc. |__\ > > +------------------------------+ > > jeffrl@wantabe.com <-----|------> | access web cgi > > ftp news mail | > > (281) 493-0718 __,.-=\'`^`'~=-../__,.-= > > +------------------------------+ > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 29 20:54:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id A7E9415648 for ; Thu, 29 Jul 1999 20:54:09 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Thu, 29 Jul 1999 20:51:49 -0700 From: "David Schwartz" To: "Joe Gleason" , "Jeffrey J. Libman" , Subject: RE: routing over a dual t1 connection (fwd) Date: Thu, 29 Jul 1999 20:51:49 -0700 Message-ID: <000001beda3e$da10bc70$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <008301beda3a$76f94ac0$0286860a@tasam.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I suggest getting a Cisco 2500 or 2600 series router. They can > do the load > balancing quite easily and 2 T1's can be attached to either. I > know this is > a non-freebsd solution, but I have always found that a hardware > router with > no drives and few moving parts is quite reliable. I know this is > not where > I should be peddling my wares, but I have a 2500 and a 2600 for sale. ;-) > > Joe Gleason > Tasam There are several problems I have had with that type of setup: 1) The router has a problem separating inbound traffic from outbound traffic. It can start to move outbound traffic away from an interface just because its inbound traffic level is high. Or, for shared media, it can continue to route large amounts of outbound traffic to an interface, causing the inbound traffic to collide to hell. 2) While you can control the way your outbound traffic splits, you can't control the inbound traffic. If the other end isn't configured just right, your inbound traffic will be badly split and there isn't a thing you can do about it. 3) Recovery from a single link failure is often very bad. This isn't quite so bad for serial links because the router can usually discover a link failure pretty rapidly. But if it can't, if something fails at a higher level, it's very difficult to get good failover. You can try to implement failover at a higher level with IP routing protocols, but if this is a link to an ISP, they are unlikely to be willing to do this. 4) The only splits possible are even or none. You can't allow a little traffic, or just overflow traffic to take one link. This problem is worst for shared media (like Ethernet), where inbound traffic and outbound traffic can collide badly, even if both directions are well split. 5) The load is measured over too long a period of time and commitments are made to route connections over one link or another which the router can't quickly change. Dramatically varying traffic patterns are very badly split. Don't draw the wrong conclusion. I'm not saying you should never do this. Sometimes it is the best solution. But it can have some really serious drawbacks. The biggest advantages of this setup are: 1) It can be very easy to get working. 2) It doesn't cause too many out-of-order packets to be received. 3) It's fairly inexpensive, especially if you already have a Cisco router with a spare fast serial port. 4) Cisco routers are very solid and can have many months of uptime without a problem. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 29 21:30:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (Postfix) with SMTP id 0654115686 for ; Thu, 29 Jul 1999 21:30:50 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 11A4JG-0004T2-00; Thu, 29 Jul 1999 21:30:18 -0700 Date: Thu, 29 Jul 1999 21:30:14 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: David Schwartz Cc: Joe Gleason , "Jeffrey J. Libman" , freebsd-stable@FreeBSD.ORG Subject: RE: routing over a dual t1 connection (fwd) In-Reply-To: <000001beda3e$da10bc70$021d85d1@youwant.to> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Jul 1999, David Schwartz wrote: > > I suggest getting a Cisco 2500 or 2600 series router. They can > > do the load > > balancing quite easily and 2 T1's can be attached to either. I > > know this is > > a non-freebsd solution, but I have always found that a hardware > > router with > > no drives and few moving parts is quite reliable. I know this is > > not where > > I should be peddling my wares, but I have a 2500 and a 2600 for sale. ;-) > > > > Joe Gleason > > Tasam > > There are several problems I have had with that type of setup: > > 1) The router has a problem separating inbound traffic from outbound > traffic. It can start to move outbound traffic away from an interface just > because its inbound traffic level is high. Or, for shared media, it can > continue to route large amounts of outbound traffic to an interface, causing > the inbound traffic to collide to hell. No. Balancing on Cisco products is done via the routing table. If multiple routes exist to a destination, traffic is balanced. Each route has a "use" counter, and the route with the lowest "use" value is one used for the traffic. There are some other options too. > 2) While you can control the way your outbound traffic splits, you can't > control the inbound traffic. If the other end isn't configured just right, > your inbound traffic will be badly split and there isn't a thing you can do > about it. Sure, inbound traffic is up to the other end. It isn't too difficult to configure, in fact, it is really easy. > 3) Recovery from a single link failure is often very bad. This isn't quite > so bad for serial links because the router can usually discover a link > failure pretty rapidly. But if it can't, if something fails at a higher > level, it's very difficult to get good failover. You can try to implement > failover at a higher level with IP routing protocols, but if this is a link > to an ISP, they are unlikely to be willing to do this. Most links to ISP are going to be serial links, or maybe cross-over ethernet, where carrier loss is going to pretty accurate. ISPs use of routing protocols between customers is very common now. > 4) The only splits possible are even or none. You can't allow a little > traffic, or just overflow traffic to take one link. This problem is worst > for shared media (like Ethernet), where inbound traffic and outbound traffic > can collide badly, even if both directions are well split. Not all ethernet is shared, only half-duplex. The solution for that problem is obvious. Cisco has quite slow to adopt full-duplex ethernet interfaces. There is really very little available on models less than the 4500. > 5) The load is measured over too long a period of time and commitments are > made to route connections over one link or another which the router can't > quickly change. Dramatically varying traffic patterns are very badly split. Not really. > Don't draw the wrong conclusion. I'm not saying you should never do this. > Sometimes it is the best solution. But it can have some really serious > drawbacks. The biggest advantages of this setup are: > > 1) It can be very easy to get working. Funny, you just said it was tricky to get working :) > 2) It doesn't cause too many out-of-order packets to be received. > > 3) It's fairly inexpensive, especially if you already have a Cisco router > with a spare fast serial port. > > 4) Cisco routers are very solid and can have many months of uptime without > a problem. > > DS > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 29 22: 5:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail0.atl.bellsouth.net (mail0.atl.bellsouth.net [205.152.0.27]) by hub.freebsd.org (Postfix) with ESMTP id 6765214DF4 for ; Thu, 29 Jul 1999 22:05:28 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net ([216.78.101.43]) by mail0.atl.bellsouth.net (3.3.0/8.9.3) with ESMTP id BAA03870; Fri, 30 Jul 1999 01:02:07 -0400 (EDT) Received: from wghicks (wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.3/8.9.2) with ESMTP id BAA01423; Fri, 30 Jul 1999 01:05:56 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199907300505.BAA01423@bellsouth.net> To: Vadim Chekan Cc: "stable@FreeBSD.ORG" , wghicks@wghicks.bellsouth.net Subject: Re: Bison update request In-reply-to: Your message of "Thu, 29 Jul 1999 10:16:32 +0300." <379FFFCF.992175D0@gc.lviv.ua> Date: Fri, 30 Jul 1999 01:05:56 -0400 From: W Gerald Hicks Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > a port at /usr/ports/devel/bison which is currently at 1.27, and could be > upgraded to 1.28 either by politely requesting so from the maintainer > (wghicks@bellsouth.net) or by send-PRing your own patches :-) Oops! I had no idea it's been updated. And I watch too, must be recent... Off to the salt mines! :) Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 30 4:51:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kogge.Hanse.DE (kogge.hanse.de [192.76.134.17]) by hub.freebsd.org (Postfix) with ESMTP id 163E714D07 for ; Fri, 30 Jul 1999 04:51:35 -0700 (PDT) (envelope-from soenksen@planlos.hanse.de) Received: from planlos.hanse.de (uucp@localhost) by kogge.Hanse.DE (8.9.3/8.9.1) with UUCP id NAA13340 for freebsd-stable@freebsd.org; Fri, 30 Jul 1999 13:52:09 +0200 (CEST) (envelope-from soenksen@planlos.hanse.de) Received: (from soenksen@localhost) by fury.planlos.hanse.de (8.9.3/8.9.1) id NAA76665 for freebsd-stable@freebsd.org; Fri, 30 Jul 1999 13:47:12 +0200 (CEST) (envelope-from soenksen) Date: Fri, 30 Jul 1999 13:47:12 +0200 From: Sebastian Soenksen To: freebsd-stable@freebsd.org Subject: make release Message-ID: <19990730134712.A76661@fury.planlos.hanse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi i tried to do a make release today with releng_3: ===> include ===> lib ===> lib/libroken make: don't know how to make k_getpwuid.c. Stop *** Error code 2 any hints? bye -- Sebastian Soenksen ; soenksen@planlos.hanse.de ; diz@IRCNet ; pgpkey available commercial use of emailadresse not allowed ; http://www.planlos.hanse.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 30 5:43:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kogge.Hanse.DE (kogge.hanse.de [192.76.134.17]) by hub.freebsd.org (Postfix) with ESMTP id 0B8AD14FDC for ; Fri, 30 Jul 1999 05:43:12 -0700 (PDT) (envelope-from soenksen@planlos.hanse.de) Received: from planlos.hanse.de (uucp@localhost) by kogge.Hanse.DE (8.9.3/8.9.1) with UUCP id OAA14594 for freebsd-stable@freebsd.org; Fri, 30 Jul 1999 14:42:32 +0200 (CEST) (envelope-from soenksen@planlos.hanse.de) Received: (from soenksen@localhost) by fury.planlos.hanse.de (8.9.3/8.9.1) id OAA88212 for freebsd-stable@freebsd.org; Fri, 30 Jul 1999 14:38:16 +0200 (CEST) (envelope-from soenksen) Date: Fri, 30 Jul 1999 14:38:16 +0200 From: Sebastian Soenksen To: freebsd-stable@freebsd.org Subject: Re: make release Message-ID: <19990730143816.A88204@fury.planlos.hanse.de> References: <19990730134712.A76661@fury.planlos.hanse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <19990730134712.A76661@fury.planlos.hanse.de>; from Sebastian Soenksen on Fri, Jul 30, 1999 at 01:47:12PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 30, 1999 at 01:47:12PM +0200, Sebastian Soenksen wrote: > i tried to do a make release today with releng_3: > ===> include > ===> lib > ===> lib/libroken > make: don't know how to make k_getpwuid.c. Stop > *** Error code 2 sorry, my fault, i forgot to check out src-crypto :) bye -- Sebastian Soenksen ; soenksen@planlos.hanse.de ; diz@IRCNet ; pgpkey available commercial use of emailadresse not allowed ; http://www.planlos.hanse.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 30 7:47:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id E782F15166 for ; Fri, 30 Jul 1999 07:47:17 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA07083; Fri, 30 Jul 1999 23:46:37 +0900 (JST) Message-ID: <37A18BAD.2D92ECFD@newsguy.com> Date: Fri, 30 Jul 1999 20:25:33 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Shashi Joshi , stable@freebsd.org Subject: Re: 2.2.7 -> 3.2 STABLE upgrade changes root password??? References: <19990607092144.A24839@WEBSI.com> <37A0818B.A5820A42@newsguy.com> <19990729185256.A2508@Shift-F1.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Shashi Joshi wrote: > The password problem was my stupidity. I had tcsh as default shell for > root. When I rebuilt in 3.2 elf format, it didn't rebuild tcsh since it is > not part of basic system Damn, I forgot the most important question. Did you update /etc before rebooting? It *ought* to have worked, even with the old tcsh. > While I have your attention, one thing that came up. > I have a new Pentium III 450 , 378 MB 3 SCSI disk system with 3.2-stable > updated. I worked with it for 2 months all fine. I moved 2GB worth tar > files from old computer all fine. > Then since 23rd Jul, I started doing daily backups from one FS to another. > It starts around midnight. 3 times it reboot the system in the middle of > the backup process (dump/restore and tars). Then once it hung up, no auto > reboots. It had to be manually started. Then yesterday night it didn't > respond to the monitor. Today the ISP staff started it again, I am yet to > find their explanation of what thye found out. Is this a 3.2-release or -stable? This seems like a honest bug. We would like to trace that, if you could help us. Could you read the session on the handbook on kernel debugging, get a crash dump, and send us the backtrace? Also, more information is needed. From the above, it would seem that no network is involved. Can you confirm that? What is(are) the SCSI interface(s) you are using? What mount options are you using? Are you using softupdates? Is there any chance you may have run out of space/inodes/swap? Do these backups stop at random points? Are there any crashes at any other time? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Is it true that you're a millionaire's son who never worked a day in your life?" "Yeah, I guess so." "Lemme tell you, son, you ain't missed a thing." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 30 8:37: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 2339515274 for ; Fri, 30 Jul 1999 08:37:03 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Fri, 30 Jul 1999 08:35:43 -0700 From: "David Schwartz" To: "Tom" Cc: "Joe Gleason" , "Jeffrey J. Libman" , Subject: RE: routing over a dual t1 connection (fwd) Date: Fri, 30 Jul 1999 08:35:43 -0700 Message-ID: <000601bedaa1$2f5e1f80$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 1) It can be very easy to get working. > > Funny, you just said it was tricky to get working :) Tricky to get working _well_. Easy to get working. :) Adding an extra 'ip route' command takes 5 seconds. But then watching your traffic balance terribly and performance go down is the hitch. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 30 11: 5:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tasam.com (tasam.com [206.161.83.22]) by hub.freebsd.org (Postfix) with ESMTP id 50899156E7 for ; Fri, 30 Jul 1999 11:05:51 -0700 (PDT) (envelope-from freebsd.list@bug.tasam.com) Received: from bug (216-164-242-66.s320.tnt10.lnh.md.dialup.rcn.com [216.164.242.66]) by tasam.com (8.9.3/8.9.1) with SMTP id OAA14591; Fri, 30 Jul 1999 14:05:35 -0400 (EDT) Message-ID: <006801bedab6$23b107a0$0286860a@tasam.com> From: "Joe Gleason" To: "David Schwartz" , "Tom" Cc: "Jeffrey J. Libman" , References: <000601bedaa1$2f5e1f80$021d85d1@youwant.to> Subject: Re: routing over a dual t1 connection (fwd) Date: Fri, 30 Jul 1999 14:04:04 -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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > 1) It can be very easy to get working. > > > > Funny, you just said it was tricky to get working :) > > Tricky to get working _well_. Easy to get working. :) > > Adding an extra 'ip route' command takes 5 seconds. But then watching your > traffic balance terribly and performance go down is the hitch. > I have done this is a production environment, the traffic balanced perfectly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 30 11:51:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 0FDE215154 for ; Fri, 30 Jul 1999 11:51:31 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Fri, 30 Jul 1999 11:51:15 -0700 From: "David Schwartz" To: "Joe Gleason" , "Tom" Cc: "Jeffrey J. Libman" , Subject: RE: routing over a dual t1 connection (fwd) Date: Fri, 30 Jul 1999 11:51:15 -0700 Message-ID: <001601bedabc$805f0410$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <006801bedab6$23b107a0$0286860a@tasam.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > 1) It can be very easy to get working. > > > > > > Funny, you just said it was tricky to get working :) > > > > Tricky to get working _well_. Easy to get working. :) > > > > Adding an extra 'ip route' command takes 5 seconds. But then > watching your > > traffic balance terribly and performance go down is the hitch. > > I have done this is a production environment, the traffic balanced > perfectly. Then perhaps you'd care to share with us how you told the router whether it should route outbound traffic to avoid inbound traffic or not do so. Universally, the inability to control this is the largest problem that I have. Is there some 'outbound traffic avoids inbound traffic' mode that you can turn on or off? The router seems to make no distinction between shared and unshared media (bandwidth shared between inbound and outbound) and, as far as I can tell, uses an algorithm that is optimized for neither case. In addition, no single TCP connection seems to be able to use the combined bandwidth. They appear to be assigned to a single link and pretty much stay that way. This could be considered to be a feature, I suppose it depends upon your application. And if it did use both links for a single connection, large numbers of packets would be received out of order. This is because each link is considered a separate IP conduit. Techniques that bond the two links into a signle conduit do not have this problem. The decision of which link to assign a connection to seems made based upon long-term load calculations (30 _seconds_ or more), so traffic patterns that vary widely over short periods of time cannot easily be accounted for. I'd love to learn the tricks to fix this, because I'd prefer to use this solution. But I've had mediocre results every time I've tried it. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 30 12: 3:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id 61BD914CD4 for ; Fri, 30 Jul 1999 12:03:11 -0700 (PDT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 11AHvx-0005K1-00 for freebsd-stable@FreeBSD.ORG; Fri, 30 Jul 1999 15:03:09 -0400 Date: Fri, 30 Jul 1999 15:03:09 -0400 From: Peter Radcliffe To: freebsd-stable@FreeBSD.ORG Subject: Re: routing over a dual t1 connection (fwd) Message-ID: <19990730150309.G13679@pir.net> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <006801bedab6$23b107a0$0286860a@tasam.com> <001601bedabc$805f0410$021d85d1@youwant.to> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <001601bedabc$805f0410$021d85d1@youwant.to>; from David Schwartz on Fri, Jul 30, 1999 at 11:51:15AM -0700 X-fish: < Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Schwartz probably said: > > I have done this is a production environment, the traffic balanced > > perfectly. > Then perhaps you'd care to share with us how you told the > router whether it This is a) nothing to do with freebsd and b) specificly nothing to do with -stable. Would you care to take cisco discussions elsewhere, please. P. -- pir pir@pir.net pir@shore.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 30 14:37:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from binnacle.wantabe.com (binnacle.wantabe.com [209.16.8.14]) by hub.freebsd.org (Postfix) with ESMTP id 553DD1571B for ; Fri, 30 Jul 1999 14:37:20 -0700 (PDT) (envelope-from jeffrl@wantabe.com) Received: from localhost (jeffrl@localhost) by binnacle.wantabe.com (8.9.2/8.9.2) with ESMTP id QAA91421; Fri, 30 Jul 1999 16:37:04 -0500 (CDT) (envelope-from jeffrl@wantabe.com) X-Authentication-Warning: binnacle.wantabe.com: jeffrl owned process doing -bs Date: Fri, 30 Jul 1999 16:37:04 -0500 (CDT) From: "Jeffrey J. Libman" To: Peter Radcliffe Cc: freebsd-stable@FreeBSD.ORG Subject: Re: routing over a dual t1 connection (fwd) In-Reply-To: <19990730150309.G13679@pir.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG um....i did NOT want to discuss cisco routers. the original query i sent was regarding using free-bsd box as a router for 2 t1's to the same destination... i know there are folks out there relying on their unix box for a router...was hoping to learn something along these lines. cheers, jeff | |\ +------------------------------+ Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | Wantabe, Inc. |__\ +------------------------------+ jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ On Fri, 30 Jul 1999, Peter Radcliffe wrote: > David Schwartz probably said: > > > I have done this is a production environment, the traffic balanced > > > perfectly. > > > Then perhaps you'd care to share with us how you told the > > router whether it > > This is a) nothing to do with freebsd and b) specificly nothing to do > with -stable. > Would you care to take cisco discussions elsewhere, please. > > P. > > -- > pir pir@pir.net pir@shore.net pir@net.tufts.edu > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 31 2:38:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ms1.tomail.com.tw (ms1.tomail.com.tw [139.175.250.174]) by hub.freebsd.org (Postfix) with SMTP id 7C2D014CF9 for ; Sat, 31 Jul 1999 02:38:26 -0700 (PDT) (envelope-from silver@tomail.com.tw) Received: (qmail 24930 invoked from network); 31 Jul 1999 09:37:59 -0000 Received: from ms2.tomail.com.tw (HELO tomail.com.tw) (203.70.70.181) by ms1.tomail.com.tw with SMTP; 31 Jul 1999 09:37:59 -0000 Message-ID: <37A2C504.9E39301A@tomail.com.tw> Date: Sat, 31 Jul 1999 17:42:28 +0800 From: Silver CHEN X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,zh-TW MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: [Q] inetd log message wher -c/-C is specified...? Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Sir: I got these messages from syslog when I enabled the -c/-C limit of inetd. Should I worry about that? >Jul 31 17:35:06 dns inetd[19464]: /var/qmail/bin/tcp-env[19569]: exit status 0x100 It seems that everything is ok, however, this msg appearred for each incomming connection, not just some of them. The only annoying effect is that I got an very big syslog everyday. They were not there if I don't specify the -c/-C parmaters. As I did before. Thanks for your response. Regards. -- +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ | Shan-Ta CHEN E-Mail : sansil@pchome.com.tw | | Silver CHEN Tel(O) : +886-2-2773-9858-288 | | ³¯µ½¹F Tel(H) : +886-2-2914-1402 | +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 31 2:43:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ms1.tomail.com.tw (ms1.tomail.com.tw [139.175.250.174]) by hub.freebsd.org (Postfix) with SMTP id 4E9C714D6C for ; Sat, 31 Jul 1999 02:43:19 -0700 (PDT) (envelope-from silver@tomail.com.tw) Received: (qmail 26847 invoked from network); 31 Jul 1999 09:42:53 -0000 Received: from ms2.tomail.com.tw (HELO tomail.com.tw) (203.70.70.181) by ms1.tomail.com.tw with SMTP; 31 Jul 1999 09:42:53 -0000 Message-ID: <37A2C629.2EEDB8C7@tomail.com.tw> Date: Sat, 31 Jul 1999 17:47:21 +0800 From: Silver CHEN X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,zh-TW MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: Re: [Q] inetd log message wher -c/-C is specified...? References: <37A2C504.9E39301A@tomail.com.tw> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry that I forgot to tell my environ. It's a 3.2-stable box and used as internet email/www servers. yes, I use ientd/qmail to handle smtp/pop3, but I don't think it matters. -- Silver CHEN 1999/7/31 Silver CHEN wrote: > > Dear Sir: > > I got these messages from syslog when I enabled the -c/-C limit > of inetd. Should I worry about that? > > >Jul 31 17:35:06 dns inetd[19464]: /var/qmail/bin/tcp-env[19569]: exit status > 0x100 > > It seems that everything is ok, however, this msg appearred for each > incomming connection, not just some of them. The only annoying > effect is that I got an very big syslog everyday. > > They were not there if I don't specify the -c/-C parmaters. As I > did before. Thanks for your response. > > Regards. > > -- > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ > | Shan-Ta CHEN E-Mail : sansil@pchome.com.tw | > | Silver CHEN Tel(O) : +886-2-2773-9858-288 | > | ³¯µ½¹F Tel(H) : +886-2-2914-1402 | > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ | Shan-Ta CHEN E-Mail : sansil@pchome.com.tw | | Silver CHEN Tel(O) : +886-2-2773-9858-288 | | ³¯µ½¹F Tel(H) : +886-2-2914-1402 | +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 31 6:34:28 1999 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id A7CA514F17 for ; Sat, 31 Jul 1999 06:34:17 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 31 Jul 1999 14:33:51 +0100 (BST) Date: Sat, 31 Jul 1999 14:33:50 +0100 From: David Malone To: Silver CHEN Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: [Q] inetd log message wher -c/-C is specified...? Message-ID: <19990731143350.A2844@walton.maths.tcd.ie> References: <37A2C504.9E39301A@tomail.com.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <37A2C504.9E39301A@tomail.com.tw>; from Silver CHEN on Sat, Jul 31, 1999 at 05:42:28PM +0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 31, 1999 at 05:42:28PM +0800, Silver CHEN wrote: > I got these messages from syslog when I enabled the -c/-C limit > of inetd. Should I worry about that? > > >Jul 31 17:35:06 dns inetd[19464]: /var/qmail/bin/tcp-env[19569]: exit status > 0x100 Looking at the inetd, it looks like inetd only logs these messages if there is some limit on the number of children. This is probably a bug, but not a serious one. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 31 12:44:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id C9FA614C57; Sat, 31 Jul 1999 12:44:42 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA14966; Sat, 31 Jul 1999 21:42:26 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Date: Sat, 31 Jul 1999 21:42:26 +0200 Message-ID: <14964.933450146.1@critter.freebsd.dk> From: Poul-Henning Kamp Subject: Sitting inside, looking out... MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa" Content-Description: Blind Carbon Copy Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------- =_aaaaaaaaaa Content-Type: message/rfc822 Content-Description: Original Message Subject: Sitting inside, looking out... From: Poul-Henning Kamp Date: Sat, 31 Jul 1999 21:42:26 +0200 Message-ID: <14964.933450146@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Bcc: Blind Distribution List: ; MIME-Version: 1.0 We have repeatedly heard that -core's communication with the developers leaves something to be desired, so I'll venture this attempt at improving it. This email is NOT a official statement from core, it is MY PERSONAL attempt, as a core member, at improving communication between core and the developers. I will try to represent the consensus -core as faithfully as I can, but make no mistake: this is seen through my glasses. 1. Core decisions ----------------- A lot of you have been asking for -core direction and decisions on various issues, and mostly you didn't get any such thing. It seems that is the way the core team as such wants things to be. I think the best way to express it is that the core team sees itself as a supreme court, not as a governing board: We only act when all other avenues of closure have failed. Think of it as "gigamanagement" rather than "micromanagement". In general the core team doesn't make more than a handful of decisions a year (that is not counting appointing committers) and there isn't resonance in -core for changing this level of activity. So how are things decided in this project if not by -core ? Well, working code speaks loud and clear, thats for sure, but otherwise it happens exactly the way you see it: people discuss things in the mailing lists and try to reach agreement. But if you want to get a core decision on something, make sure that you send an email to core@freebsd.org with the question. You cannot expect any reaction from -core by posing the question in some random maillist. Make sure to include sufficient background and references to the subject, at least half of the core members have not heard of the discussion before. And please use a distinctive subject on your emails, "proposal for new committer" is a distinctively bad subject line, much better would be "Samuel B. Morse for committer ?" In the past -core has not been very good at even answering emails, but I have been trying to improve that by assuming a self-styled secretary function: as best I can I try to keep track of outstanding items and make sure they don't fall through the cracks. If you don't get a response from -core, nag me with an email, and I will try to make it happen. 2. Who are the committers anyway ? ---------------------------------- All the noise about Matt Dillons commit bit have generated a lot of questions about who gets to be committers, so here is a little insight into the process of appointing a committer: Generally we in core operate with three kinds of committers: Ports committers These are people who maintain one or more ports. If Asami-san wants to glue a bit on somebody, we will generally let him. Limited scope committers These are people who maintain some specific bit of the tree, typically a subsystem they are (co-)authors of. A good example is the HARP ATM stack, which Mike Spengler is taking care of (and many thanks for that Mike!) Since these people are taken on board with a explicitly stated limited scope, we are more relaxed about them than we are about the last category. People have been known to successfully sneak out from this category and into: Committers at large These are the people who persist in sending well documented PRs containing correct patches. The only way we have devised so far for ridding ourselves of this kind of annoying behaviour is to say "Here! you're a committer, now close your own PRs!" :-) For all these three categories some general rules apply, or rather if they apply the answer is a resounding "no": Flaming people and generally presenting the attitude that people who don't agree with you should leave the planet on the first available rocket (or otherwise), is the most reliable way to not pass the muster. It doesn't matter how good you are technically, if you can't work in a group, your not in this particular group. Being unresponsive to input is another good way to fall through. Some of the people are right 99.994% of the time, but nobody is right 100% of the time. If people point out to you that something you did or said isn't right, listen to them, think about it more than once, they could be right. [even Bruce has been caught on the wrong foot once, that's where I got the 99.994% figure from :-) ] Wasting peoples time. We're all here on borrowed time, most of us have jobs, families, cats, houses, you name it, things that also have legitimate claims to our time. Needlessly wasting peoples time is not welcome, in particular when it is their spare time. If you match any of these descriptions, and if you have proved that you can code or document, and have some time to spare, you'll pass the muster, no worries. And don't despair: we generally appoint a "mentor" for all new committers. The mentor is responsible for helping the new committer "learn the ropes", and generally help them get cross the threshold without getting eaten by the lions. And I hope it is all worth it for the committers, because you are certainly the biggest asset we have in the project. I'm sorry that there isn't much but the title and the rather limited fame we can offer you in return. NOTE: If somebody can find a sponsor for it, I would really like to offer an "official FreeBSD Committer sweat-shirt" to each and every single committer. Luxury cars, free vacations and suitcases filled with cash would also do. 3. The GNATS database, who handles it ? --------------------------------------- Simple: You do. Even if you are not a committer, you can help out: Find a PR, try to reproduce the problem if you can, then try to fix it if you can. If the PR contains a patch, try it out. And at the end, send a follow up to the PR with your results. A PR with a complex patch has much better chances of getting committed if the PR has a couple of follow-ups which say "works for me" than if it just sits there. 4. mac68k as a new platform ? ----------------------------- We have been contacted by Grant Stockly , who informed us that he has a almost finished port of FreeBSD to the mac68k platform. [In general I would advice that people drop the core team a note early in such an undertaking. It would be a pity if somebody else was doing the same thing and you couldn't work together just because you didn't know about each other]. The core team is very keen for more platforms, but a certain level of interest and support from users and developers is needed before we will add a platform as an official part of FreeBSD, so now is the time for those of you who have an interest in the mac68k or 68k support in general, to rally around Grant and work with him on this. Our postmaster will happily create a mailing list if you want it. That's all for now folks... Poul-Henning PS: See you all at the FreeBSD-con in October! http://www.freebsdcon.org/ -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! ------- =_aaaaaaaaaa-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message