From owner-freebsd-current Sun Jul 2 00:29:30 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA19532 for current-outgoing; Sun, 2 Jul 1995 00:29:30 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA19523 for ; Sun, 2 Jul 1995 00:29:28 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id AAA15969 for freebsd-current@FreeBSD.org; Sun, 2 Jul 1995 00:29:18 -0700 From: "Rodney W. Grimes" Message-Id: <199507020729.AAA15969@gndrsh.aac.dev.com> Subject: Re: getopt(1) To: freebsd-current@FreeBSD.org Date: Sun, 2 Jul 1995 00:29:18 -0700 (PDT) In-Reply-To: <199507011805.UAA03360@uriah.heep.sax.de> from "J Wunsch" at Jul 1, 95 08:05:37 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1059 Sender: current-owner@FreeBSD.org Precedence: bulk > > As Rodney W. Grimes wrote: > > > > Yes I object, please convert you old scripts to be portable and > > use getopts(1) so you don't have to keep hauling getopt(1) around! > > Well, i'd accept your objection, but i've just been noticing that i > wasn't really clear: it's not for _my_ sake -- i know how to convert > the scripts (at least after RTFMing). But getopt(1) used to be part > of the system for a rather long time, and i'm under the impression > that we're missing it since it has been part of the `tainted' sources > from the original BSD. It was missing in FreeBSD 1.x and people winned that they didn't want to convert. It went missing again when we went to 4.4BSD lite, and this time it should probably stay missing folks have had 2 years to convert there scripts and if we don't break them once and for all they will never get converted. getopt was not part of the tainted code. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Sun Jul 2 00:36:38 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA20018 for current-outgoing; Sun, 2 Jul 1995 00:36:38 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA20011 for ; Sun, 2 Jul 1995 00:36:32 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA20997; Sun, 2 Jul 1995 09:36:30 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA09906; Sun, 2 Jul 1995 09:36:29 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id JAA03111; Sun, 2 Jul 1995 09:12:51 +0200 From: J Wunsch Message-Id: <199507020712.JAA03111@uriah.heep.sax.de> Subject: Re: ppp To: jleppek@suw2k.ess.harris.com (James Leppek) Date: Sun, 2 Jul 1995 09:12:50 +0200 (MET DST) Cc: freebsd-current@freefall.cdrom.com In-Reply-To: <9507020032.AA00609@borg.ess.harris.com> from "James Leppek" at Jul 1, 95 08:32:10 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 913 Sender: current-owner@FreeBSD.org Precedence: bulk As James Leppek wrote: > > I suspect the fact that 0.0.0.0 was invalid is why my provider chose it. > This allows them to detect that someone must be provided an IP > (although I would not mind if they would give me a permanent IP :-) ) Perhaps he has been refering to the _PPP_ setup. I've been playing with PPP for the first time yesterday when installing 2.0.5 on my notebook (and i've been impressed about the easyness! :). I think your provider wants you to use 0.0.0.0/0 as your initial adress, meaning ``any IP address is acceptible'' (the trailing /0 means ``I insist on 0 bits of this address to be used.'') But this is only the initial address to the IPCP layer, the actual IP address will be negotiated, and the kernel will only see the correct address. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Jul 2 07:27:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA28102 for current-outgoing; Sun, 2 Jul 1995 07:27:06 -0700 Received: from cyclops (xtwa7.ess.harris.com [130.41.26.166]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA28081 for ; Sun, 2 Jul 1995 07:26:57 -0700 Received: (from jleppek@localhost) by cyclops (8.6.11/8.6.9) id KAA00305; Sun, 2 Jul 1995 10:26:59 -0400 Date: Sun, 2 Jul 1995 10:26:59 -0400 From: Jim Leppek Message-Id: <199507021426.KAA00305@cyclops> To: joerg_wunsch@uriah.heep.sax.de CC: freebsd-current@freefall.cdrom.com In-reply-to: <199507020712.JAA03111@uriah.heep.sax.de> (message from J Wunsch on Sun, 2 Jul 1995 09:12:50 +0200 (MET DST)) Subject: Re: ppp Sender: current-owner@FreeBSD.org Precedence: bulk Yes, my provider wants to see 0.0.0.0 during the initial negotiation phase however thats the problem. A 0.0.0.0 address gets converted to 192.0.0.1 within the ppp even if you set ifaddr 0 0. This occurs in ipcp.c around line 164 per my earlier mail message. It is this forced ( and hidden ) conversion that I question. When I set my initial address to 0.0.0.0 I expect ppp to use it. I definitely like the new ppp and have stopped using my old pppd scripts by this conversion of 0.0.0.0 is a definite gotcha IMHO. I removed the questionable src lines and rebuilt ppp so all is well for me but for anyone not comfortable with tweeking sources or tracking ip negotiation bugs I suspect it would have taken a bit of time. Jim Leppek From: J Wunsch Date: Sun, 2 Jul 1995 09:12:50 +0200 (MET DST) Cc: freebsd-current@freefall.cdrom.com Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 913 As James Leppek wrote: > > I suspect the fact that 0.0.0.0 was invalid is why my provider chose it. > This allows them to detect that someone must be provided an IP > (although I would not mind if they would give me a permanent IP :-) ) Perhaps he has been refering to the _PPP_ setup. I've been playing with PPP for the first time yesterday when installing 2.0.5 on my notebook (and i've been impressed about the easyness! :). I think your provider wants you to use 0.0.0.0/0 as your initial adress, meaning ``any IP address is acceptible'' (the trailing /0 means ``I insist on 0 bits of this address to be used.'') But this is only the initial address to the IPCP layer, the actual IP address will be negotiated, and the kernel will only see the correct address. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Jul 2 08:24:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA01223 for current-outgoing; Sun, 2 Jul 1995 08:24:58 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA01194 for ; Sun, 2 Jul 1995 08:24:30 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id BAA16708; Mon, 3 Jul 1995 01:19:59 +1000 Date: Mon, 3 Jul 1995 01:19:59 +1000 From: Bruce Evans Message-Id: <199507021519.BAA16708@godzilla.zeta.org.au> To: hsu@clinet.fi Subject: Re: kern/579: sio: RS_IBUFSIZE 256 too small Cc: current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk >>Synopsis: sio: RS_IBUFSIZE at 256 bytes serial lines loose data (PPP) > A 486-40 with 6 16550 ports and 4 ethernets (3 active) > A 386-16 with 1 16550 ports and 1 ethernet (just a PPP router) >>Description: > Both these machines report "interrupt-level buffer overflow":s > very frequently on a leased line running at 38400, badly dropping > IP performance. This is because you don't use crtscts and something or other delays softclock() by more than (RB_IBUFSIZE - ceil(38400/10/100.0) = 217 character times, i.e., for more than 5.5 clock interrupts. Hardware interrupts and all other software interrupts have priority over softclock(), so any solid block of hardware or net interrupts would do this. I would be surprised if ethernet interrupts on the 386/16 didn't do it. > On 386-16 I also saw several spontaneous reboots when loading the > PPP link. Another problem. I saw a spontaneous reboot today when I did something silly involving pppd and tcpdump. The system normally just panics when tcpdump is killed after pppd is killed. >>How-To-Repeat: > It seems that this bites only me, even though it does this on two > quite different configurations. In addition the 486 machine has I think you said that 1.1.5 doesn't have the problem. I can't explain how it could work better. -current should work a little better because ordinary timeouts are no longer used. Hardware interrupts still block siopoll() but soft net interrupts don't. >>Fix: > > I changed RS_IBUFSIZE from 256 to 4096, and the problem disappeared. > It might be that a smaller amount would be sufficient (I don't mind > 8k memory waste per line in this case). But it is apparent that > 256 bytes seems not sufficient for slow or loaded machines. >sio.c: >< #define RS_IBUFSIZE 256 >-- >> #define RS_IBUFSIZE 4096 This breaks crtscts unless you make TTYHOG 16 times as large to match. The watermark RB_I_HIGH_WATER = (TTYHOG - 2 * RB_IBUFSIZE) must be significantly larger than 0. TTYHOG must to be larger than 2 * RB_IBUFSIZE even without crtscts. Bruce From owner-freebsd-current Sun Jul 2 09:09:07 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA03927 for current-outgoing; Sun, 2 Jul 1995 09:09:07 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA03919 for ; Sun, 2 Jul 1995 09:09:00 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id CAA17781 for current@freebsd.org; Mon, 3 Jul 1995 02:04:02 +1000 Date: Mon, 3 Jul 1995 02:04:02 +1000 From: Bruce Evans Message-Id: <199507021604.CAA17781@godzilla.zeta.org.au> To: current@freebsd.org Subject: Re: serial ip congestion Sender: current-owner@freebsd.org Precedence: bulk I wrote: >The system seems to be unable to handle more than one active line at 115200 >bps. With 2 lines at 11500 bps, each line takes turns transmitting. There >... >Configuration: > -current > all on one system > my new cy driver > 8 ports on connected in pairs, 2 pairs active > default mtu (1500) > speed 115200 bps > test: rcp /kernel a4:/tmp/k4 & rcp /kernel a5:/tmp/k5 & >... >No errors were reported by the drivers or by pppstats. I noticed many Nevermind. It was just ordinary silo overruns, broken error reporting, and poor error recovery. The cy driver didn't report silo overruns and pppstats doesn't report `if_ierrors', only `sls_errorin'. netstat reports the errors. Bruce From owner-freebsd-current Sun Jul 2 09:44:59 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA04698 for current-outgoing; Sun, 2 Jul 1995 09:44:59 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA04692 for ; Sun, 2 Jul 1995 09:44:57 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id SAA19743 ; Sun, 2 Jul 1995 18:44:55 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id SAA15473 ; Sun, 2 Jul 1995 18:44:54 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199507021644.SAA15473@blaise.ibp.fr> Subject: Re: ppp To: jleppek@harris.com (Jim Leppek) Date: Sun, 2 Jul 1995 18:44:53 +0200 (MET DST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@freefall.cdrom.com In-Reply-To: <199507021426.KAA00305@cyclops> from "Jim Leppek" at Jul 2, 95 10:26:59 am X-Operating-System: FreeBSD BUILT-19950501 ctm#617 X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 463 Sender: current-owner@FreeBSD.org Precedence: bulk > I definitely like the new ppp and have stopped using my old pppd > scripts by this conversion of 0.0.0.0 is a definite gotcha IMHO. Every PPP I've seen uses 0.0.0.0 to say : "Hey, gimme an address" so I vote for removing the hidden conversion. 192.0.0.1 is no less "illegal" than 0.0.0.0 but anyone uses 0.0.0.0. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.0-BUILT-19950503 #3: Wed May 3 19:53:04 MET DST 1995 From owner-freebsd-current Sun Jul 2 09:51:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA04996 for current-outgoing; Sun, 2 Jul 1995 09:51:48 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA04989 for ; Sun, 2 Jul 1995 09:51:45 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA00932; Sun, 2 Jul 1995 18:51:42 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id SAA12889; Sun, 2 Jul 1995 18:51:41 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id SAA00415; Sun, 2 Jul 1995 18:50:14 +0200 From: J Wunsch Message-Id: <199507021650.SAA00415@uriah.heep.sax.de> Subject: Re: ppp To: jleppek@harris.com (Jim Leppek) Date: Sun, 2 Jul 1995 18:50:14 +0200 (MET DST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@freefall.cdrom.com In-Reply-To: <199507021426.KAA00305@cyclops> from "Jim Leppek" at Jul 2, 95 10:26:59 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 862 Sender: current-owner@FreeBSD.org Precedence: bulk As Jim Leppek wrote: > > > Yes, my provider wants to see 0.0.0.0 during the initial negotiation > phase however thats the problem. A 0.0.0.0 address gets converted to > 192.0.0.1 within the ppp even if you set ifaddr 0 0. > This occurs in ipcp.c around line 164 per my earlier mail message. > It is this forced ( and hidden ) conversion that I question. > When I set my initial address to 0.0.0.0 I expect ppp to use it. Sorry, i've got confused. I've been in the belief that it happened later, but it's apparently been during the IPCP phase. Ok. Btw., i don't know about the kernel-ppp, but couldn't you give any address as long as you're specifying the /0 (i.e., don't insist on getting a particular address)? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Jul 2 12:00:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA06985 for current-outgoing; Sun, 2 Jul 1995 12:00:46 -0700 Received: from pelican.com (pelican.com [134.24.4.62]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA06976 for ; Sun, 2 Jul 1995 12:00:43 -0700 Received: from puffin.pelican.com by pelican.com with smtp (Smail3.1.28.1 #5) id m0sSUFt-000K0qC; Sun, 2 Jul 95 12:00 WET DST Received: (from pete@localhost) by puffin.pelican.com (8.6.11/8.6.9) id TAA26156; Sun, 2 Jul 1995 19:00:32 GMT Date: Sun, 2 Jul 1995 19:00:32 GMT From: Pete Carah Message-Id: <199507021900.TAA26156@puffin.pelican.com> To: current@freebsd.org Subject: Re: Paul Richards: sysconfig routed setting In-Reply-To: <199507012057.QAA26175@duality.gnu.ai.mit.edu> Sender: current-owner@freebsd.org Precedence: bulk In article <199507012057.QAA26175@duality.gnu.ai.mit.edu> you write: > HOSTS DO NOT NEED ROUTING INFORMATION. >What would you suggest that multihomed hosts do? He admits that *they* need routing information; what he doesn't consider is that all hosts on any network with more than one router needs routing information too, even though the host isn't multihomed. Rather that there is "an elegant" solution coming up. However, since it isn't there yet and routed is, we're kind of stuck :-( It *is* important with multihomed hosts on networks where more than one host is multihomed on the same networks (I have a network like that in a video shop where we have parallel enet and FDDI networks connecting about half of the hosts) that routed is started with -q on all hosts except for the router (or maybe *one* of the multihomed fileservers). In our case there is no need for routing FDDI packets to/from the ethernet because all the hosts are on the enet; if more than one routed is started without -q it can induce routing loops in this situation. (the SGI default is without -q; at least we did *that* right). We will be converting to a switched enet with the fddi only for fileservers; that will require routed -q on all hosts and non -q *only* on the switch box (or whoever routes; it may end up one (or more if the enet connections end up on different nets) of the fileservers again instead of the enet switch.) -- Pete From owner-freebsd-current Sun Jul 2 12:21:11 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA07481 for current-outgoing; Sun, 2 Jul 1995 12:21:11 -0700 Received: from pelican.com (pelican.com [134.24.4.62]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA07474 for ; Sun, 2 Jul 1995 12:21:07 -0700 Received: from puffin.pelican.com by pelican.com with smtp (Smail3.1.28.1 #5) id m0sSUZi-000K0qC; Sun, 2 Jul 95 12:21 WET DST Received: (from pete@localhost) by puffin.pelican.com (8.6.11/8.6.9) id TAA26200; Sun, 2 Jul 1995 19:21:02 GMT Date: Sun, 2 Jul 1995 19:21:02 GMT From: Pete Carah Message-Id: <199507021921.TAA26200@puffin.pelican.com> To: bde@zeta.org.au Subject: Re: kern/579: sio: RS_IBUFSIZE 256 too small In-Reply-To: <199507021519.BAA16708@godzilla.zeta.org.au> Cc: current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk In article <199507021519.BAA16708@godzilla.zeta.org.au> you write: >>>Synopsis: sio: RS_IBUFSIZE at 256 bytes serial lines loose data (PPP) >> A 486-40 with 6 16550 ports and 4 ethernets (3 active) >> A 386-16 with 1 16550 ports and 1 ethernet (just a PPP router) >>>Description: >> Both these machines report "interrupt-level buffer overflow":s >> very frequently on a leased line running at 38400, badly dropping >> IP performance. >This is because you don't use crtscts and something or other delays >softclock() by more than (RB_IBUFSIZE - ceil(38400/10/100.0) = 217 >character times, i.e., for more than 5.5 clock interrupts. Hardware >interrupts and all other software interrupts have priority over >softclock(), so any solid block of hardware or net interrupts would do >this. I would be surprised if ethernet interrupts on the 386/16 didn't >do it. WRONG. It shows up on raw ports where I KNOW that crtscts is in use *AND WORKS* in cooked mode *in the same connection*. The *ONLY* cure for this (so far) is to increase ttyhog to whatever your protocol's window size is; this works fine, and since no chars are ever dropped in this situation once ttyhog is icreased, I suspect that interrupt latency is *not* a problem. I know we've been over this a lot in the past; something *has* to be wrong in the driver, but I don't know what it is; apparently rts isn't being dropped when it should be, but only in raw mode. ............ >> On 386-16 I also saw several spontaneous reboots when loading the >> PPP link. > >Another problem. I saw a spontaneous reboot today when I did something >silly involving pppd and tcpdump. The system normally just panics when >tcpdump is killed after pppd is killed. Is this the old route delete bug? Must be independent of ttyhog and such. I have seen a few bpf commits recently to deal with tcpdump on down interfaces. Don't know if they fix anything since I don't use bpf particularly. >> I changed RS_IBUFSIZE from 256 to 4096, and the problem disappeared. >> It might be that a smaller amount would be sufficient (I don't mind >> 8k memory waste per line in this case). But it is apparent that >> 256 bytes seems not sufficient for slow or loaded machines. ..... >>sio.c: >>< #define RS_IBUFSIZE 256 >>-- >>> #define RS_IBUFSIZE 4096 > >This breaks crtscts unless you make TTYHOG 16 times as large to match. >The watermark RB_I_HIGH_WATER = (TTYHOG - 2 * RB_IBUFSIZE) must be >significantly larger than 0. TTYHOG must to be larger than 2 * RB_IBUFSIZE >even without crtscts. I make this problem go away just by increasing ttyhog without touching ibufsize; this is why I don't think there is any interrupt latency problem; ttyhog "fixes" process-dispatch latencies instead. -- Pete From owner-freebsd-current Sun Jul 2 12:24:08 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA07635 for current-outgoing; Sun, 2 Jul 1995 12:24:08 -0700 Received: from duality.gnu.ai.mit.edu (!#$%^&*!#$%^&*!#$%^&*!#$%^&*!#$%^&*!#$%^&*!#$%^&*!#$%^&*!#$%^&*!#$%^&*!#$%^&*!#$%^&*@duality.gnu.ai.mit.edu [18.43.0.236]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA07629 for ; Sun, 2 Jul 1995 12:24:07 -0700 Received: by duality.gnu.ai.mit.edu (8.6.12/8.6.12GNU) id PAA22366; Sun, 2 Jul 1995 15:23:49 -0400 Date: Sun, 2 Jul 1995 15:23:49 -0400 Message-Id: <199507021923.PAA22366@duality.gnu.ai.mit.edu> From: "Charles M. Hannum" To: pete@puffin.pelican.com CC: current@freebsd.org In-reply-to: <199507021900.TAA26156@puffin.pelican.com> (message from Pete Carah on Sun, 2 Jul 1995 19:00:32 GMT) Subject: Re: Paul Richards: sysconfig routed setting Sender: current-owner@freebsd.org Precedence: bulk In article <199507012057.QAA26175@duality.gnu.ai.mit.edu> you write: > HOSTS DO NOT NEED ROUTING INFORMATION. >What would you suggest that multihomed hosts do? He admits that *they* need routing information; what he doesn't consider is that all hosts on any network with more than one router needs routing information too, even though the host isn't multihomed. I disagree. First of all, he said that only `gateways' need routing information, and multi-homed hosts are not (necessarily) gateways. Secondly, it *is* plausible for single-homed hosts to rely on multiple routers negotiating shortest paths and sending redirects -- provided that there is a router discovery protocol so you don't get screwed when one router goes down. However, this still leaves multi-homed hosts with inefficient and possibly incorrect routing. From owner-freebsd-current Sun Jul 2 19:24:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA16334 for current-outgoing; Sun, 2 Jul 1995 19:24:43 -0700 Received: from haywire.DIALix.COM (root@haywire.DIALix.COM [192.203.228.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA16324 for ; Sun, 2 Jul 1995 19:24:35 -0700 Received: (from peter@localhost) by haywire.DIALix.COM (8.6.12/8.6.12/DIALix) id KAA10456; Mon, 3 Jul 1995 10:04:12 +0800 Date: Mon, 3 Jul 1995 10:04:11 +0800 (WST) From: Peter Wemm To: current@freebsd.org Subject: comments on my favourite hack to traceroute? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk This is my favourite hack to traceroute to rationalize the number of digits printed in the rtt stats.. The standard one prints three numbers after the decimal point, and when you're up in the thousands of milliseconds (try going from australia to the depths of europe some time.. :-), then the numbers are a bit of overkill. It makes the display look very messy. I made a change to cause traceroute to only show a limited number of significant digits.. ie: before after 0.123 ms 0.123 ms 6.233 ms 6.233 ms 25.231 ms 25.23 ms 121.345 ms 121 ms (I chose not to put in any decimals if > 100.0) 2323.543 ms 2323 ms This stops screen wrap arounds for while crossing most of the MCI and Sprint backbones, and what's left of the ANS backbone. Is this kind of thing useful to people? This is what it looks like over a local ethernet: traceroute to haywire.DIALix.COM (192.203.228.65), 30 hops max, 40 byte packets 1 haywire (192.203.228.65) 3.053 ms 2.393 ms 2.227 ms and this is what it looks like after crossing a few modems and ISDN links: traceroute to freefall.cdrom.com (192.216.222.4), 30 hops max, 40 byte packets 1 gecko.DIALix.oz.au (192.203.228.3) 155 ms 147 ms 125 ms 2 frontdoor (192.203.228.4) 132 ms 157 ms 127 ms 3 doormat1 (192.203.228.241) 161 ms 190 ms 162 ms 4 national.gw.au (139.130.85.1) 228 ms 272 ms 250 ms 5 usa.gw.au (139.130.240.2) 269 ms 254 ms 217 ms 6 border4-hssi1-0.SanFrancisco.mci.net (204.70.35.5) 481 ms 420 ms 420 ms 7 core-fddi-1.SanFrancisco.mci.net (204.70.3.161) 401 ms * 447 ms 8 border1-fddi0-0.SanFrancisco.mci.net (204.70.2.162) 491 ms * 478 ms 9 barrnet.SanFrancisco.mci.net (204.70.32.6) 420 ms 433 ms * 10 * su-b.barrnet.net (192.31.48.201) 522 ms 1172 ms 11 ucbnew.barrnet.net (131.119.2.2) 507 ms 461 ms 444 ms 12 ucb2.barrnet.net (131.119.253.3) 492 ms 422 ms 495 ms 13 cdrom.barrnet.net (131.119.70.134) 545 ms 487 ms 519 ms 14 freefall.cdrom.com (192.216.222.4) 534 ms 605 ms 535 ms Opinions? -Peter *** traceroute.c.dist Thu May 25 01:44:04 1995 --- traceroute.c Mon Jul 3 09:44:39 1995 *************** *** 306,312 **** struct hostent *hp; struct protoent *pe; struct sockaddr_in from, *to; ! int ch, i, on, probe, seq, tos, ttl; on = 1; seq = tos = 0; --- 306,313 ---- struct hostent *hp; struct protoent *pe; struct sockaddr_in from, *to; ! int ch, i, on, probe, seq, tos, ttl, p; ! double dt; on = 1; seq = tos = 0; *************** *** 507,513 **** --- 508,531 ---- print(packet, cc, &from); lastaddr = from.sin_addr.s_addr; } + + #if !defined(MESSY) + /* + * This quick hack is to try and rationalize the number of significant + * digits in the output. If you have a hop 2000ms away, it's not a lot of + * use knowing +/- 1 ms, let alone +/- 0.001 ms.... -Peter + */ + dt = deltaT(&t1, &t2); + if (dt >= 100.0) + p = 0; + else if (dt >= 10.0) + p = 2; + else + p = 3; + Printf(" %.*f ms", p, dt); + #else Printf(" %.3f ms", deltaT(&t1, &t2)); + #endif switch(i - 1) { case ICMP_UNREACH_PORT: #ifndef ARCHAIC From owner-freebsd-current Sun Jul 2 21:09:33 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA19464 for current-outgoing; Sun, 2 Jul 1995 21:09:33 -0700 Received: from silver.sms.fi (silver.sms.fi [194.111.122.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA19458 for ; Sun, 2 Jul 1995 21:09:31 -0700 Received: (from pete@localhost) by silver.sms.fi (8.6.11/8.6.9) id HAA22719; Mon, 3 Jul 1995 07:09:02 +0300 Date: Mon, 3 Jul 1995 07:09:02 +0300 Message-Id: <199507030409.HAA22719@silver.sms.fi> From: Petri Helenius To: Peter Wemm Cc: current@freebsd.org Subject: comments on my favourite hack to traceroute? In-Reply-To: References: Sender: current-owner@freebsd.org Precedence: bulk Peter Wemm writes: > I made a change to cause traceroute to only show a limited number of > significant digits.. > This stops screen wrap arounds for while crossing most of the MCI and > Sprint backbones, and what's left of the ANS backbone. > > Is this kind of thing useful to people? > I find this definetly useful and I think this should also be integrated to the "original" traceroute. Pete From owner-freebsd-current Sun Jul 2 22:48:18 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA21014 for current-outgoing; Sun, 2 Jul 1995 22:48:18 -0700 Received: from bunyip.cc.uq.oz.au (bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id WAA21008 for ; Sun, 2 Jul 1995 22:48:06 -0700 Received: from s1.elec.uq.edu.au by bunyip.cc.uq.oz.au with SMTP (PP); Mon, 3 Jul 1995 15:47:41 +1000 Received: from s4.elec.uq.edu.au by s1.elec.uq.edu.au (4.0/SMI-4.0) id AA03757; Mon, 3 Jul 95 15:35:48 EST From: clary@elec.uq.oz.au (Clary Harridge) Message-Id: <9507030536.AA03757@s1.elec.uq.edu.au> Subject: netscape causing reboot of diskless clients To: freebsd-current@freebsd.org Date: Mon, 3 Jul 1995 15:46:42 +1000 (EST) X-Mailer: ELM [version 2.4 PL22] Content-Type: text Content-Length: 462 Sender: current-owner@freebsd.org Precedence: bulk I find that since upgrading to FreeBSD 2.0-BUILT-19950615, diskless clients running XFree86-3.1, reboot when netscape is started. If I change the DISPLAY from :0.0 to RemoteDisplay:0.0 I can run netscape OK. Is anyone aware of problems which might cause these reboots? -- regards Dept. of Electrical Engineering, Clary Harridge University of Queensland, QLD, Australia, 4072 Phone: +61-7-365-3636 Fax: +61-7-365-4999 INTERNET: clary@elec.uq.edu.au From owner-freebsd-current Sun Jul 2 23:53:21 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA21941 for current-outgoing; Sun, 2 Jul 1995 23:53:21 -0700 Received: from clinet.fi (root@clinet.fi [193.64.6.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA21933 for ; Sun, 2 Jul 1995 23:53:11 -0700 Received: from katiska.clinet.fi (root@katiska.clinet.fi [193.64.6.3]) by clinet.fi (8.6.10/8.6.4) with ESMTP id JAA09078 for ; Mon, 3 Jul 1995 09:52:46 +0300 From: Heikki Suonsivu Received: (hsu@localhost) by katiska.clinet.fi (8.6.11/8.6.4) id JAA00240; Mon, 3 Jul 1995 09:52:46 +0300 Date: Mon, 3 Jul 1995 09:52:46 +0300 Message-Id: <199507030652.JAA00240@katiska.clinet.fi> To: freebsd-current@freefall.cdrom.com Subject: Re: kern/579: sio: RS_IBUFSIZE 256 too small Organization: Clinet Ltd, Espoo, Finland Sender: current-owner@FreeBSD.org Precedence: bulk In article <199507021921.TAA26200@puffin.pelican.com> Pete Carah writes: >> Both these machines report "interrupt-level buffer overflow":s >> very frequently on a leased line running at 38400, badly dropping ... >This is because you don't use crtscts and something or other delays On many async leased lines there is no hardware flow control, all you get through is two data wires. Even if there was, if you stop receiving because internal rs buffer overflows, you are idling the fixed-speed link, thus it should only done if the machine really can't cope with all the data (but it certainly does cope in this case). After pushing the input buffer to 4k I got a significant performance improvement and no more loss of data. My workaround is apparently wrong, it works as I don't need and don't have rts/cts flow control, but clearly something needs to be done to sio in this respect. 256 bytes seems overly tight to me, moving data in pieces this small is waste of cpu. Does it need to do a context switch or interrupt for each time it loads the 256 byte buffer to a tty buffer? >> On 386-16 I also saw several spontaneous reboots when loading the >> PPP link. Is this the old route delete bug? Must be independent of ttyhog and such. I have seen a few bpf commits recently to deal with tcpdump on down interfaces. Don't know if they fix anything since I don't use bpf particularly. I have bpf enabled in kernel but I haven't used tcpdump on the interface (at the time it reboots). The kernels are recent (2.0.5R and up). -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN From owner-freebsd-current Mon Jul 3 00:52:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA22952 for current-outgoing; Mon, 3 Jul 1995 00:52:37 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA22929 for ; Mon, 3 Jul 1995 00:52:12 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA18600; Mon, 3 Jul 1995 09:52:07 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA19491 for freebsd-current@FreeBSD.org; Mon, 3 Jul 1995 09:52:06 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id IAA03062 for freebsd-current@FreeBSD.org; Mon, 3 Jul 1995 08:45:38 +0200 From: J Wunsch Message-Id: <199507030645.IAA03062@uriah.heep.sax.de> Subject: Re: comments on my favourite hack to traceroute? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 3 Jul 1995 08:45:38 +0200 (MET DST) Reply-To: freebsd-current@FreeBSD.org (FreeBSD-current users) In-Reply-To: from "Peter Wemm" at Jul 3, 95 10:04:11 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 474 Sender: current-owner@FreeBSD.org Precedence: bulk As Peter Wemm wrote: > > I made a change to cause traceroute to only show a limited number of > significant digits.. > ie: > before after > 0.123 ms 0.123 ms > 6.233 ms 6.233 ms > 25.231 ms 25.23 ms > 121.345 ms 121 ms (I chose not to put in any decimals if > 100.0) > 2323.543 ms 2323 ms > Opinions? Makes sense for me. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Jul 3 01:39:40 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA24257 for current-outgoing; Mon, 3 Jul 1995 01:39:40 -0700 Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA24251 for ; Mon, 3 Jul 1995 01:39:28 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id SAA08352 for current@freebsd.org; Mon, 3 Jul 1995 18:38:51 +1000 From: michael butler Message-Id: <199507030838.SAA08352@asstdc.scgt.oz.au> Subject: spontaneous reboots ? To: current@freebsd.org Date: Mon, 3 Jul 1995 18:38:49 +1000 (EST) X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 411 Sender: current-owner@freebsd.org Precedence: bulk Just like those "fail-safe" circuits, I have a pair of machines which, when I power up one of them, causes the other, adjacent to it and running -current, to panic with a "trap 12: page not present" :-(. The machine running -current is running gated where the machine just powered up (2.0.5R) is running "routed -q" so that doesn't seem to be it. Any thoughts as to how I can track this one down ? michael From owner-freebsd-current Mon Jul 3 01:55:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA24860 for current-outgoing; Mon, 3 Jul 1995 01:55:23 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA24853 for ; Mon, 3 Jul 1995 01:55:20 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id SAA13156; Mon, 3 Jul 1995 18:29:36 +0930 From: Michael Smith Message-Id: <199507030859.SAA13156@genesis.atrad.adelaide.edu.au> Subject: Re: spontaneous reboots ? To: imb@scgt.oz.au (michael butler) Date: Mon, 3 Jul 1995 18:29:35 +0930 (CST) Cc: current@freebsd.org In-Reply-To: <199507030838.SAA08352@asstdc.scgt.oz.au> from "michael butler" at Jul 3, 95 06:38:49 pm Content-Type: text Content-Length: 909 Sender: current-owner@freebsd.org Precedence: bulk michael butler stands accused of saying: > > Just like those "fail-safe" circuits, I have a pair of machines which, when > I power up one of them, causes the other, adjacent to it and running > -current, to panic with a "trap 12: page not present" :-(. At the instant that you power it up, or during the boot process? If the former, you have power problems; if the latter, no idea 8) > Any thoughts as to how I can track this one down ? tcpdump on a third system would help if you suspect network interference. > michael -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" - Terry Lambert [[ From owner-freebsd-current Mon Jul 3 02:46:42 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA27362 for current-outgoing; Mon, 3 Jul 1995 02:46:42 -0700 Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA27349 for ; Mon, 3 Jul 1995 02:46:29 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id TAA12138; Mon, 3 Jul 1995 19:44:48 +1000 From: michael butler Message-Id: <199507030944.TAA12138@asstdc.scgt.oz.au> Subject: Re: spontaneous reboots ? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Mon, 3 Jul 1995 19:44:46 +1000 (EST) Cc: current@freebsd.org In-Reply-To: <199507030859.SAA13156@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jul 3, 95 06:29:35 pm X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 587 Sender: current-owner@freebsd.org Precedence: bulk Michael Smith writes: > > Just like those "fail-safe" circuits, I have a pair of machines which, > > when I power up one of them, causes the other, adjacent to it and > > running -current, to panic with a "trap 12: page not present" :-(. > At the instant that you power it up, or during the boot process? During the boot process shortly after the network card is initialised, although I'm not sure precisely when as they share one display. > tcpdump on a third system would help if you suspect network interference. On a busy ethernet, that's going to be difficult :-( michael From owner-freebsd-current Mon Jul 3 03:04:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA27868 for current-outgoing; Mon, 3 Jul 1995 03:04:14 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA27862 for ; Mon, 3 Jul 1995 03:04:09 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id DAA18112; Mon, 3 Jul 1995 03:02:02 -0700 From: "Rodney W. Grimes" Message-Id: <199507031002.DAA18112@gndrsh.aac.dev.com> Subject: Re: spontaneous reboots ? To: imb@scgt.oz.au (michael butler) Date: Mon, 3 Jul 1995 03:02:02 -0700 (PDT) Cc: msmith@atrad.adelaide.edu.au, current@freebsd.org In-Reply-To: <199507030944.TAA12138@asstdc.scgt.oz.au> from "michael butler" at Jul 3, 95 07:44:46 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 840 Sender: current-owner@freebsd.org Precedence: bulk > > Michael Smith writes: > > > > Just like those "fail-safe" circuits, I have a pair of machines which, > > > when I power up one of them, causes the other, adjacent to it and > > > running -current, to panic with a "trap 12: page not present" :-(. > > > At the instant that you power it up, or during the boot process? > > During the boot process shortly after the network card is initialised, > although I'm not sure precisely when as they share one display. > > > tcpdump on a third system would help if you suspect network interference. > > On a busy ethernet, that's going to be difficult :-( Not really, have tcpdump filter on the MAC address of the problem machine. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Mon Jul 3 03:16:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA00551 for current-outgoing; Mon, 3 Jul 1995 03:16:29 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA00315 for ; Mon, 3 Jul 1995 03:16:10 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id UAA13294; Mon, 3 Jul 1995 20:12:39 +1000 Date: Mon, 3 Jul 1995 20:12:39 +1000 From: Bruce Evans Message-Id: <199507031012.UAA13294@godzilla.zeta.org.au> To: current@freebsd.org, imb@scgt.oz.au Subject: Re: spontaneous reboots ? Sender: current-owner@freebsd.org Precedence: bulk >Just like those "fail-safe" circuits, I have a pair of machines which, when >I power up one of them, causes the other, adjacent to it and running >-current, to panic with a "trap 12: page not present" :-(. >... >Any thoughts as to how I can track this one down ? First read kernel-debug.FAQ. Bruce From owner-freebsd-current Mon Jul 3 03:40:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA01065 for current-outgoing; Mon, 3 Jul 1995 03:40:13 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA01055 for ; Mon, 3 Jul 1995 03:40:02 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id UAA14048; Mon, 3 Jul 1995 20:38:27 +1000 Date: Mon, 3 Jul 1995 20:38:27 +1000 From: Bruce Evans Message-Id: <199507031038.UAA14048@godzilla.zeta.org.au> To: freebsd-current@freefall.cdrom.com, hsu@clinet.fi Subject: Re: kern/579: sio: RS_IBUFSIZE 256 too small Sender: current-owner@FreeBSD.org Precedence: bulk >My workaround is apparently wrong, it works as I don't need and don't have >rts/cts flow control, but clearly something needs to be done to sio in this >respect. 256 bytes seems overly tight to me, moving data in pieces this >small is waste of cpu. Does it need to do a context switch or interrupt >for each time it loads the 256 byte buffer to a tty buffer? Only a software interrupt. Since the driver has to handle a hardware interrupt for every 1 or 14 characters, and a software interrupt has less overhead than a hardware interrupt (at least for FreeBSD on i386's), 256 bytes is plenty bug enough. The normal amount is actually only 115.2 bytes at 115200 bps or 1.2 bytes at 1200 bps (the multi-level interrupt handler certainly isn't more efficient at 1200 bps!). 256 was chosen as big enough to handle 115200 bps when the interrupt-level buffer is transferred every clock tick. Transferring it less often would give an unacceptable latency for non-streaming protocols. 128 would have been too close to 115.2. I thought that softclock() interrupts were never delayed as long as 1 clock tick except on grossly overloaded systems. But they sometimes are. Bruce From owner-freebsd-current Mon Jul 3 04:19:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA01650 for current-outgoing; Mon, 3 Jul 1995 04:19:14 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA01644 for ; Mon, 3 Jul 1995 04:19:05 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id VAA15005; Mon, 3 Jul 1995 21:16:02 +1000 Date: Mon, 3 Jul 1995 21:16:02 +1000 From: Bruce Evans Message-Id: <199507031116.VAA15005@godzilla.zeta.org.au> To: bde@zeta.org.au, pete@puffin.pelican.com Subject: Re: kern/579: sio: RS_IBUFSIZE 256 too small Cc: current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk >>> Both these machines report "interrupt-level buffer overflow":s ^^^^^^^^^^^^^^^ >>> very frequently on a leased line running at 38400, badly dropping >>> IP performance. >>This is because you don't use crtscts and something or other delays >>softclock() by more than (RB_IBUFSIZE - ceil(38400/10/100.0) = 217 >>character times, i.e., for more than 5.5 clock interrupts. Hardware >>interrupts and all other software interrupts have priority over >>softclock(), so any solid block of hardware or net interrupts would do >>this. I would be surprised if ethernet interrupts on the 386/16 didn't >>do it. >WRONG. It shows up on raw ports where I KNOW that crtscts is in use >*AND WORKS* in cooked mode *in the same connection*. I thought your problem was tty-level buffer overflows. >I know we've been over this a lot in the past; something *has* to be >wrong in the driver, but I don't know what it is; apparently rts isn't >being dropped when it should be, but only in raw mode. It is dropped in different code in raw mode, but the raw mode code has essentially no changes from 1.1.5 where it apparantly worked. The cooked mode code has different watermarks from 1.1.5 (high = TTYHOG/2 which happens to equal the raw mode high watermark and the 1.1.5 value iff TTYHOG has the default value of 1024, low = TTYHOG / 5 was high * 7 / 8 in 1.1.5) but anything with tty.low < driver.high && tty.low < tty.high should work. Bruce From owner-freebsd-current Mon Jul 3 04:30:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA01800 for current-outgoing; Mon, 3 Jul 1995 04:30:25 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id EAA01792 ; Mon, 3 Jul 1995 04:30:15 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA07361; Mon, 3 Jul 1995 13:25:21 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA21251; Mon, 3 Jul 1995 13:24:47 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id LAA03564; Mon, 3 Jul 1995 11:08:53 +0200 From: J Wunsch Message-Id: <199507030908.LAA03564@uriah.heep.sax.de> Subject: Re: /etc/rc and "rm -f /var/spool/lock/*" To: Harlan.Stenn@pfcs.com (Harlan Stenn) Date: Mon, 3 Jul 1995 11:08:53 +0200 (MET DST) Cc: freebsd-current@FreeBSD.org (FreeBSD-current users), core@FreeBSD.org Reply-To: freebsd-current@FreeBSD.org (FreeBSD-current users) In-Reply-To: <27450.804752338@mumps.pfcs.com> from "Harlan Stenn" at Jul 3, 95 02:18:58 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 965 Sender: current-owner@FreeBSD.org Precedence: bulk [Moved to -current, no need to discuss this in -core.] As Harlan Stenn wrote: > > I am starting a "ppp -auto" from /etc/netstart. > > Assuming this is a reasonable thing for folks to do, the "rm -f > /var/spool/lock/*" in /etc/rc is "too late". Since I get spontaneous > reboots with "ppp -auto whatever" anyway, sometimes an "old" lock file > remains. I moved the "rm -f /var/spool/lock/*" to before the call to > rc.serial. Basically means that iijppp is broken in this respect. Clients are encouraged to examine an existing lock file to see if it's a stale lock (by trying to send a signal to the process). It's safe for them to remove the lock file if the process holding the lock disappeared. Lock files suck. They should not be used at all, and the only client that really needs them right now is mgetty. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Jul 3 05:03:18 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA02609 for current-outgoing; Mon, 3 Jul 1995 05:03:18 -0700 Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA02601 for ; Mon, 3 Jul 1995 05:03:10 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id WAA18182; Mon, 3 Jul 1995 22:01:37 +1000 From: michael butler Message-Id: <199507031201.WAA18182@asstdc.scgt.oz.au> Subject: Re: spontaneous reboots ? To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Mon, 3 Jul 1995 22:01:36 +1000 (EST) Cc: current@freebsd.org In-Reply-To: <199507031002.DAA18112@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Jul 3, 95 03:02:02 am X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 375 Sender: current-owner@freebsd.org Precedence: bulk Rodney W. Grimes writes: > Not really, have tcpdump filter on the MAC address of the problem machine. It's in the ipfw code .. the packet that causes the panic is addressed to a machine which is inaccessible by virtue of an "ipfw policy deny". I don't see it from the other machinery on this ether because they're "secure" and permitted to traverse that gateway, michael From owner-freebsd-current Mon Jul 3 05:11:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA02869 for current-outgoing; Mon, 3 Jul 1995 05:11:55 -0700 Received: from ess.harris.com (su15a.ess.harris.com [130.41.1.251]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id FAA02863 for ; Mon, 3 Jul 1995 05:11:54 -0700 Received: from borg.ess.harris.com (suw2k.ess.harris.com) by ess.harris.com (5.x/SMI-SVR4) id AA07870; Mon, 3 Jul 1995 08:11:50 -0400 Received: by borg.ess.harris.com (4.1/SMI-4.1) id AA01365; Mon, 3 Jul 95 08:09:29 EDT Date: Mon, 3 Jul 95 08:09:29 EDT From: jleppek@suw2k.ess.harris.com (James Leppek) Message-Id: <9507031209.AA01365@borg.ess.harris.com> To: joerg_wunsch@uriah.heep.sax.de Subject: Re: ppp Cc: freebsd-current@freefall.cdrom.com Sender: current-owner@FreeBSD.org Precedence: bulk The "fix" is to remove the lines that override the users request to set the address to 0. I think the flexibility provided by ppp is important to support the variety of users. To say it is a providers fault because they want to use a particular address to indicate that the user is requesting an IP seems harsh. This is espicially true if some of their clients have assigned IP address's and other are asking for one from the "pool". I do not think the this hidden conversion is proper if the user has set their initial ip to 0.0.0.0 with a set ifaddr, they must mean it :-) What is the "value added" to changing it to some other arbitrary value? I would think it appropriate if someone would commit this or better yet remove the offending lines from ppp/ipcp.c. *** ipcp.c Tue May 30 07:21:55 1995 --- ipcp.c.fixed Sat Jul 1 08:35:24 1995 *************** *** 160,167 **** --- 160,171 ---- icp->want_ipaddr.s_addr = DefMyAddress.ipaddr.s_addr; icp->his_ipaddr.s_addr = DefHisAddress.ipaddr.s_addr; } + + /* if (icp->want_ipaddr.s_addr == 0) icp->want_ipaddr.s_addr = htonl(0xc0000001); + */ + if (Enabled(ConfVjcomp)) icp->want_compproto = (PROTO_VJCOMP << 16) | ((MAX_STATES - 1) << 8); else I know I keep bringing this up but it just doesn't seem right. In the kernel pppd an IP of 0 just causes the "accept_local" flag to get set, which seems appropriate. If no one agrees, oh well, I will keep changing my copy after each sup which is what "having the sources" is all about I suppose :-) Jim Leppek > From j@uriah.heep.sax.de Mon Jul 3 03:51:35 1995 > From: J Wunsch > Subject: Re: ppp > To: jleppek@suw2k.ess.harris.com (James Leppek) > Date: Mon, 3 Jul 1995 09:10:23 +0200 (MET DST) > Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) > X-Phone: +49-351-2012 669 > X-Mailer: ELM [version 2.4 PL23] > Mime-Version: 1.0 > Content-Type> : > text/plain> ; > charset=ISO-8859-1> > Content-Transfer-Encoding: 8bit > > As James Leppek wrote: > > > > the problem is that some providers are willing to accept valid addresses > > and skip negotiation, so if you give anything other than 0.0.0.0 they > > reply ok and let you have it :-( > > This is their fault. They are not supposed to allow any address... > > > I do not know if the kernel-ppp does the same thing but I think it > > is a bug if it does. > > If you can come up with a (tested) fix, please submit it. > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ > Never trust an operating system you don't have sources for. ;-) > From owner-freebsd-current Mon Jul 3 07:16:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA07050 for current-outgoing; Mon, 3 Jul 1995 07:16:57 -0700 Received: from specgw.spec.co.jp (specgw.spec.co.jp [202.32.13.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA07025 for ; Mon, 3 Jul 1995 07:16:09 -0700 Received: from localhost (uucp@localhost) by specgw.spec.co.jp (8.6.5/3.3Wb-SPEC) with UUCP id WAA17127; Mon, 3 Jul 1995 22:58:05 +0900 Received: by tama.spec.co.jp (8.6.11/6.4J.5) id CAA00773; Mon, 3 Jul 1995 02:35:11 +0900 From: Atsushi Murai Message-Id: <199507021735.CAA00773@tama.spec.co.jp> Subject: Re: ppp To: jleppek@harris.com (Jim Leppek) Date: Mon, 3 Jul 1995 02:35:11 +0900 (JST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@freefall.cdrom.com, tony-o@iij.ad.jp (Toshiharu Ohno) In-Reply-To: <199507021426.KAA00305@cyclops> from "Jim Leppek" at Jul 2, 95 10:26:59 am Reply-To: amurai@spec.co.jp X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1430 Sender: current-owner@FreeBSD.org Precedence: bulk > > Yes, my provider wants to see 0.0.0.0 during the initial negotiation > phase however thats the problem. A 0.0.0.0 address gets converted to > 192.0.0.1 within the ppp even if you set ifaddr 0 0. > This occurs in ipcp.c around line 164 per my earlier mail message. > It is this forced ( and hidden ) conversion that I question. > When I set my initial address to 0.0.0.0 I expect ppp to use it. > > I definitely like the new ppp and have stopped using my old pppd > scripts by this conversion of 0.0.0.0 is a definite gotcha IMHO. User process ppp has a dial on demand function, too. And it's should assume a valid ip address for trapping a outgoing packet. After dailing and connecting your ISP, it may negotiate and get a new ip address. In this situation, trigger packet will be lost due to old ip address without any bad effect to peer - using "192.0.0.1". But other mode, they don't do need a such a tric. > I removed the questionable src lines and rebuilt ppp so all > is well for me but for anyone not comfortable with tweeking sources > or tracking ip negotiation bugs I suspect it would have taken > a bit of time. So I will recomended we should confirm and make sure what's a right things ;-) > Jim Leppek Atsushi. P.S. I will CC: this to auther. -- Atsushi Murai Internet: amurai@spec.co.jp System Planning and Engineering Co,.Ltd. Voice : +81-33833-5341 From owner-freebsd-current Mon Jul 3 07:20:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA07200 for current-outgoing; Mon, 3 Jul 1995 07:20:52 -0700 Received: from tserv.lodgenet.com (root@dial7.iw.net [204.157.148.56]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA07116 for ; Mon, 3 Jul 1995 07:19:25 -0700 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by tserv.lodgenet.com (8.6.12/8.6.12) with ESMTP id JAA21868; Mon, 3 Jul 1995 09:20:11 -0500 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.6.11/8.6.9) with SMTP id JAA10131; Mon, 3 Jul 1995 09:19:57 -0500 Message-Id: <199507031419.JAA10131@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6 4/21/95 To: clary@elec.uq.oz.au (Clary Harridge) cc: freebsd-current@freebsd.org Subject: Re: netscape causing reboot of diskless clients In-reply-to: Your message of "Mon, 03 Jul 1995 15:46:42 +1000." <9507030536.AA03757@s1.elec.uq.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Jul 1995 09:19:56 -0500 From: "Eric L. Hernes" Sender: current-owner@freebsd.org Precedence: bulk > I find that since upgrading to FreeBSD 2.0-BUILT-19950615, > diskless clients running XFree86-3.1, reboot when netscape is started. > > If I change the DISPLAY from :0.0 to RemoteDisplay:0.0 I can run netscape OK. What kind of machine/os is running the NFS server? I've seen similar problems with SCO being the server. I suspect that other SYSV (non R4) implementations will be similar. It seems that SCO's nfs won't allow fbsd to make named sockets. The X-server tries to make some unix-domain sockets in /tmp which clients will use to connect when using display :0.0. If the display is set to `hostname`:0.0, the clients will use inet-domain sockets, and things will work. I came up with two possible work arounds. 1) a small mfs for /tmp/.X11-unix (if ram is plentiful) 2) a ufs image and the vnode driver. > > Is anyone aware of problems which might cause these reboots? > -- > regards Dept. of Electrical Engineering, > Clary Harridge University of Queensland, QLD, Australia, 4072 > Phone: +61-7-365-3636 Fax: +61-7-365-4999 > INTERNET: clary@elec.uq.edu.au > eric. -- erich@lodgenet.com erich@rrnet.com From owner-freebsd-current Mon Jul 3 08:29:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA09578 for current-outgoing; Mon, 3 Jul 1995 08:29:39 -0700 Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA09567 for ; Mon, 3 Jul 1995 08:29:24 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id BAA02503 for current@freebsd.org; Tue, 4 Jul 1995 01:29:14 +1000 From: michael butler Message-Id: <199507031529.BAA02503@asstdc.scgt.oz.au> Subject: Re: spontaneous reboots ? To: current@freebsd.org Date: Tue, 4 Jul 1995 01:29:13 +1000 (EST) In-Reply-To: <199507031201.WAA18182@asstdc.scgt.oz.au> from "michael butler" at Jul 3, 95 10:01:36 pm X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 571 Sender: current-owner@freebsd.org Precedence: bulk I wrote: > It's in the ipfw code .. In ip_fw.c at about line 300: > bad_packet: > if (f) { > /* > * Do not ICMP reply to icmp > * packets....:) > */ > if (f_prt==IP_FW_F_ICMP) > goto return_0; *** NOTE "m" is still uninitialised here *** > /* > * Reply to packets rejected > * by entry with this flag > * set only. > */ > if (!(f->fw_flg&IP_FW_F_ICMPRPL)) > goto return_0; *** and here *** > m = dtom(ip); : : > return_0: > m_freem(m); > return 0; > good_packet: > return 1; > } .. but we try m_freem(m) anyway ? michael From owner-freebsd-current Mon Jul 3 08:48:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA10225 for current-outgoing; Mon, 3 Jul 1995 08:48:34 -0700 Received: from ess.harris.com (su15a.ess.harris.com [130.41.1.251]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA10212 for ; Mon, 3 Jul 1995 08:48:32 -0700 Received: from borg.ess.harris.com (suw2k.ess.harris.com) by ess.harris.com (5.x/SMI-SVR4) id AA09712; Mon, 3 Jul 1995 11:48:25 -0400 Received: by borg.ess.harris.com (4.1/SMI-4.1) id AA01586; Mon, 3 Jul 95 11:46:04 EDT Date: Mon, 3 Jul 95 11:46:04 EDT From: jleppek@suw2k.ess.harris.com (James Leppek) Message-Id: <9507031546.AA01586@borg.ess.harris.com> To: amurai@spec.co.jp Subject: Re: ppp Cc: freebsd-current@freefall.cdrom.com Sender: current-owner@FreeBSD.org Precedence: bulk I understand your concern about demand dial but I do not see it as a problem. PPP can assume ie. trap on any address it wants as that is a "local" issue but it should use the value set by ifaddr for negotiation because that involves another party. Suppose the provider accepted the 192.0.0.1 address and arp'd it (mine did). How does the provider know that for freebsd machines the magic "I want an IP" address is 192.0.0.1 Some providers offer both rotory and fixed IP service we just can't tell them to change for fbsd. I have tried it did not work :-) If this is an issue for demand dial maybe an option could be put in to skip the "non-intuitive" behavior for that. something like: if( demand dial && (myaddr == 0.0.0.0)) map 0.0.0.0. to 192.0.0.1 its a step in the right direction Jim Leppek > From amurai@spec.co.jp Mon Jul 3 10:07:03 1995 > From: Atsushi Murai > Subject: Re: ppp > To: jleppek@harris.com (Jim Leppek) > Date: Mon, 3 Jul 1995 02:35:11 +0900 (JST) > Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@freefall.cdrom.com, > tony-o@iij.ad.jp (Toshiharu Ohno) > Reply-To: amurai@spec.co.jp > X-Mailer: ELM [version 2.4 PL23] > Content-Type> : > text> > > > > > Yes, my provider wants to see 0.0.0.0 during the initial negotiation > > phase however thats the problem. A 0.0.0.0 address gets converted to > > 192.0.0.1 within the ppp even if you set ifaddr 0 0. > > This occurs in ipcp.c around line 164 per my earlier mail message. > > It is this forced ( and hidden ) conversion that I question. > > When I set my initial address to 0.0.0.0 I expect ppp to use it. > > > > I definitely like the new ppp and have stopped using my old pppd > > scripts by this conversion of 0.0.0.0 is a definite gotcha IMHO. > > User process ppp has a dial on demand function, too. And it's should > assume a valid ip address for trapping a outgoing packet. After > dailing and connecting your ISP, it may negotiate and get a new ip > address. In this situation, trigger packet will be lost due to old ip > address without any bad effect to peer - using "192.0.0.1". But other > mode, they don't do need a such a tric. > > > I removed the questionable src lines and rebuilt ppp so all > > is well for me but for anyone not comfortable with tweeking sources > > or tracking ip negotiation bugs I suspect it would have taken > > a bit of time. > > So I will recomended we should confirm and make sure what's a right > things ;-) > > > Jim Leppek > > Atsushi. > > P.S. I will CC: this to auther. > -- > Atsushi Murai Internet: amurai@spec.co.jp > System Planning and Engineering Co,.Ltd. Voice : +81-33833-5341 > From owner-freebsd-current Mon Jul 3 08:52:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA10471 for current-outgoing; Mon, 3 Jul 1995 08:52:02 -0700 Received: from wc.cdrom.com (wc.cdrom.com [192.216.223.37]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA10465 for ; Mon, 3 Jul 1995 08:52:01 -0700 Received: from id.slip.bcm.tmc.edu (root@[128.249.248.67]) by wc.cdrom.com (8.6.12/8.6.12) with ESMTP id IAA29632 for ; Mon, 3 Jul 1995 08:51:55 -0700 Received: (from rich@localhost) by id.slip.bcm.tmc.edu (8.6.11/8.6.9) id KAA02622; Mon, 3 Jul 1995 10:50:40 -0500 Date: Mon, 3 Jul 1995 10:50:40 -0500 From: Rich Murphey Message-Id: <199507031550.KAA02622@id.slip.bcm.tmc.edu> To: freebsd-current@freebsd.org In-reply-to: <199507030908.LAA03564@uriah.heep.sax.de> (message from J Wunsch on Mon, 3 Jul 1995 11:08:53 +0200 (MET DST)) Subject: Re: /etc/rc and "rm -f /var/spool/lock/*" Reply-to: rich@lamprey.utmb.edu Sender: current-owner@freebsd.org Precedence: bulk |From: J Wunsch |Basically means that iijppp is broken in this respect. Clients are |encouraged to examine an existing lock file to see if it's a stale |lock (by trying to send a signal to the process). It's safe for them |to remove the lock file if the process holding the lock disappeared. | |Lock files suck. They should not be used at all, and the only client |that really needs them right now is mgetty. What if you wanted to run outgoing hylafax and outgoing 'ppp -auto' on the same port. From owner-freebsd-current Mon Jul 3 09:11:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA11304 for current-outgoing; Mon, 3 Jul 1995 09:11:13 -0700 Received: from mpp.com (mpp.Minn.Net [204.157.201.242]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA11298 for ; Mon, 3 Jul 1995 09:11:11 -0700 Received: (from mpp@localhost) by mpp.com (8.6.11/8.6.9) id LAA00793; Mon, 3 Jul 1995 11:10:46 -0500 From: Mike Pritchard Message-Id: <199507031610.LAA00793@mpp.com> Subject: Re: spontaneous reboots ? To: imb@scgt.oz.au (michael butler) Date: Mon, 3 Jul 1995 11:10:45 -0500 (CDT) Cc: current@freebsd.org In-Reply-To: <199507031529.BAA02503@asstdc.scgt.oz.au> from "michael butler" at Jul 4, 95 01:29:13 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 897 Sender: current-owner@freebsd.org Precedence: bulk I just filed a PR (with a patch) on this very problem just last night. It is PR kern/585. I saw panics, and not spontaneous reboots. > I wrote: > > > It's in the ipfw code .. > > In ip_fw.c at about line 300: > > > bad_packet: > > if (f) { > > /* > > * Do not ICMP reply to icmp > > * packets....:) > > */ > > if (f_prt==IP_FW_F_ICMP) > > goto return_0; > > *** NOTE "m" is still uninitialised here *** > > > /* > > * Reply to packets rejected > > * by entry with this flag > > * set only. > > */ > > if (!(f->fw_flg&IP_FW_F_ICMPRPL)) > > goto return_0; > > *** and here *** > > > m = dtom(ip); > > : > : > > > return_0: > > m_freem(m); > > return 0; > > good_packet: > > return 1; > > } > > .. but we try m_freem(m) anyway ? > > michael -- Mike Pritchard mpp@legarto.minn.net "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-current Mon Jul 3 10:02:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA13781 for current-outgoing; Mon, 3 Jul 1995 10:02:58 -0700 Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA13773 for ; Mon, 3 Jul 1995 10:02:55 -0700 Received: by haven.uniserve.com id <30829>; Mon, 3 Jul 1995 10:03:26 +0100 Date: Mon, 3 Jul 1995 10:03:15 -0700 (PDT) From: Tom Samplonius To: James Leppek cc: amurai@spec.co.jp, freebsd-current@freefall.cdrom.com Subject: Re: ppp In-Reply-To: <9507031546.AA01586@borg.ess.harris.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Mon, 3 Jul 1995, James Leppek wrote: > Suppose the provider accepted the 192.0.0.1 address and arp'd > it (mine did). How does the provider know that for freebsd machines the magic You should tell your provider to fix his broken equipment. For example, using the IP of a nameserver or a mailhost would really mess things up. This gets real ugly when the PPP server is broadcasting routes to gateway routers. A large ISP in the US had similar equipment, and some joker decided to use 1.0.0.1 as an IP address, that route was actually broadcast out onto some major backbones so that you could actually traceroute to 1.0.0.1 from outside systems. > "I want an IP" address is 192.0.0.1 > Some providers offer both rotory and fixed IP service we just can't tell > them to change for fbsd. I have tried it did not work :-) What is supposed to happen, is that the PPP server should _tell_ your system what address to use. There is no need to use a "magic" IP address to signal this, as the PPP protocol has full address negotiation capability. I've setup a PPP server that can do both static and dynamic assignment with no requirement for magic IP's. Tom From owner-freebsd-current Mon Jul 3 10:33:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA15645 for current-outgoing; Mon, 3 Jul 1995 10:33:48 -0700 Received: from wc.cdrom.com (wc.cdrom.com [192.216.223.37]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA15637 for ; Mon, 3 Jul 1995 10:33:47 -0700 Received: from pcpsj.pfcs.com (harlan.clark.net [168.143.10.179]) by wc.cdrom.com (8.6.12/8.6.12) with ESMTP id KAA00670 for ; Mon, 3 Jul 1995 10:33:41 -0700 Received: from mumps.pfcs.com (mumps.pfcs.com [192.52.69.11]) by pcpsj.pfcs.com (8.6.11/8.6.9) with SMTP id NAA00300; Mon, 3 Jul 1995 13:30:12 -0400 Received: from localhost by mumps.pfcs.com with SMTP id AA28476 (5.67b/IDA-1.5); Mon, 3 Jul 1995 13:30:28 -0400 To: freebsd-current@FreeBSD.org (FreeBSD-current users), joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: Harlan.Stenn@pfcs.com (Harlan Stenn) Subject: Re: /etc/rc and "rm -f /var/spool/lock/*" In-Reply-To: J Wunsch's (j@uriah.heep.sax.de) message dated Mon, 03 Jul 1995 11:08:53. <199507030908.LAA03564@uriah.heep.sax.de> Date: Mon, 03 Jul 1995 13:30:28 -0300 Message-Id: <28474.804792628@mumps.pfcs.com> From: Harlan Stenn Sender: current-owner@FreeBSD.org Precedence: bulk I suspect the real solution, then, will be to file ijppp. The problem is that when I start up "ppp -auto", it will almost always come up with the same PID as the one from the previous boot, so if the lock file stuck around it will mostlikely have the *same* PID in there, and will then quietly loop until the lock file goes away! This problem happens to me a lot because ijppp frequently terminates, and if I restart ppp the machine will reboot the instant "something" happens on the link. Perhaps it's a nameserver call, perhaps it's simply an IP packet that wants to be handled by the PPP link - I can't tell; no panic is generated so I don't get a core file. H From owner-freebsd-current Mon Jul 3 11:00:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA17948 for current-outgoing; Mon, 3 Jul 1995 11:00:12 -0700 Received: from ess.harris.com (su15a.ess.harris.com [130.41.1.251]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA17940 for ; Mon, 3 Jul 1995 11:00:11 -0700 Received: from borg.ess.harris.com (suw2k.ess.harris.com) by ess.harris.com (5.x/SMI-SVR4) id AA11150; Mon, 3 Jul 1995 14:00:05 -0400 Received: by borg.ess.harris.com (4.1/SMI-4.1) id AA01662; Mon, 3 Jul 95 13:57:44 EDT Date: Mon, 3 Jul 95 13:57:44 EDT From: jleppek@suw2k.ess.harris.com (James Leppek) Message-Id: <9507031757.AA01662@borg.ess.harris.com> To: tom@uniserve.com Subject: Re: ppp Cc: freebsd-current@freefall.cdrom.com Sender: current-owner@FreeBSD.org Precedence: bulk How did you configure your netblazer(what they have) to do this? was it configured to assert a particular IP based on password like most? As I indicated, I asked that they should certainly refused IP's they do not have authority over as a minimum, but I have no "real" ability to do anything. I also love to constantly hear "the windows and linux users do not have a problem" AAARRRRGGGG I think this thread is loosing focus so let me try to get it back on track :-) what is magic about 192.0.0.1? should ppp map a users configuration request to some arbitrary alternate IP. Set ifaddr is there for a purpose and even gives "ifaddr 0 0" in an example. I know that ppp supports negotiation, the real issue is the remapping without considerable justification. This is simply not intuitive. PPP supports negotiation but I do not believe the standard says what IP's are reserved or negotiable. All we are doing is overriding a user configuration, which is the opposite of what the config file is for! Atsushi sent me a long example of a negotiation session thats starts with set ifaddr 0 0 and a negotiation phase that starts with 192.0.0.1 !!!! If he wanted 192.0.0.1 he should have entered set ifaddr 192.0.0.1 0 This is the EXPECTED behavior while the assumption that the provider knows that 192.0.0.1 is "wrong" is not. I do not know how to make the point much clearer. This is not a ppp negotiation discussion, that works. This is not a "ISP ppp is broken" discussion, they conform to the standard although not in an EXPECTED fashion. They are not filtering/refusing some IP address's, although they refuse an invalid one, which is the expected behavior. If they would have accepted 0.0.0.0 then I would say they are broken. This is a discussion about EXPECTED behavior. If I configure my ppp to start negotiating with 0.0.0.0 why would I expect to see that become 192.0.0.1?????? IF this doesn't make it clear from a users point, I guess I will have to give up :-) I yield the thread... Thanks Jim Leppek > From tom@haven.uniserve.com Mon Jul 3 13:00:34 1995 > Date: Mon, 3 Jul 1995 10:03:15 -0700 (PDT) > Sender: Tom Samplonius > From: Tom Samplonius > To: James Leppek > Cc: amurai@spec.co.jp, freebsd-current@freefall.cdrom.com > Subject: Re: ppp > Mime-Version: 1.0 > Content-Type> : > TEXT/PLAIN> ; > charset=US-ASCII> > > > On Mon, 3 Jul 1995, James Leppek wrote: > > > Suppose the provider accepted the 192.0.0.1 address and arp'd > > it (mine did). How does the provider know that for freebsd machines the magic > > You should tell your provider to fix his broken equipment. For > example, using the IP of a nameserver or a mailhost would really mess > things up. > > This gets real ugly when the PPP server is broadcasting routes to gateway > routers. A large ISP in the US had similar equipment, and some joker > decided to use 1.0.0.1 as an IP address, that route was actually > broadcast out onto some major backbones so that you could actually > traceroute to 1.0.0.1 from outside systems. > > > "I want an IP" address is 192.0.0.1 > > Some providers offer both rotory and fixed IP service we just can't tell > > them to change for fbsd. I have tried it did not work :-) > > What is supposed to happen, is that the PPP server should _tell_ your > system what address to use. There is no need to use a "magic" IP address > to signal this, as the PPP protocol has full address negotiation > capability. I've setup a PPP server that can do both static and dynamic > assignment with no requirement for magic IP's. > > Tom > From owner-freebsd-current Mon Jul 3 12:40:38 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA22251 for current-outgoing; Mon, 3 Jul 1995 12:40:38 -0700 Received: from wc.cdrom.com (wc.cdrom.com [192.216.223.37]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA22232 ; Mon, 3 Jul 1995 12:40:36 -0700 Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by wc.cdrom.com (8.6.12/8.6.12) with ESMTP id MAA01414 ; Mon, 3 Jul 1995 12:40:32 -0700 Received: from cs.pdx.edu (cs.pdx.edu [131.252.20.183]) by mail.barrnet.net (8.6.10/MAIL-RELAY-LEN) with ESMTP id MAA11667; Mon, 3 Jul 1995 12:38:38 -0700 Received: (lix@localhost) by cs.pdx.edu (8.6.10/CATastrophe-12/23/94-P) id MAA06715; Mon, 3 Jul 1995 12:24:49 -0700 for Date: Mon, 3 Jul 1995 12:24:49 -0700 From: lix@cs.pdx.edu (xiaoyin li) Message-Id: <199507031924.MAA06715@cs.pdx.edu> To: current@freebsd.org, questions@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk I have installed netscape from ftp.netscape.com site on my FreeBSD with 04/95 SNAPSHOT and X11R6. However, I got the following error messages at my first try. I would apprecite very much if someone could give me a direction how to fix this probelm. ------------------------------------------------------------------------------------- books:/usr/X11R6/lib/X11 307 # netscape books:/usr/X11R6/lib/X11 308 # netscape: uname() failed; can't tell what system we're running on netscape: locale `C' not supported. Xlib: connection to ":0.0" refused by server Xlib: Client is not authorized to connect to Server Error: Can't open display: :0.0 books:/usr/X11R6/lib/X11 308 # ------------------------------------------------------------------------------------- Xiaoyin Li System Administrator PSU Bookstore Tel: (503)226-2631 Fax: (503)725-3800 Email: lix@rigel.cs.pdx.edu From owner-freebsd-current Mon Jul 3 13:13:53 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA22805 for current-outgoing; Mon, 3 Jul 1995 13:13:53 -0700 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA22794 for ; Mon, 3 Jul 1995 13:13:51 -0700 Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by who.cdrom.com (8.6.11/8.6.11) with ESMTP id NAA01300 for ; Mon, 3 Jul 1995 13:13:35 -0700 Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by mail.barrnet.net (8.6.10/MAIL-RELAY-LEN) with ESMTP id MAA11631 for ; Mon, 3 Jul 1995 12:35:32 -0700 Received: by haven.uniserve.com id <30869>; Mon, 3 Jul 1995 12:33:13 +0100 Date: Mon, 3 Jul 1995 12:32:31 -0700 (PDT) From: Tom Samplonius To: James Leppek cc: freebsd-current@freefall.cdrom.com Subject: Re: ppp In-Reply-To: <9507031757.AA01662@borg.ess.harris.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Mon, 3 Jul 1995, James Leppek wrote: > How did you configure your netblazer(what they have) to do this? IMO, Netblazer's don't make a very good PPP server. I don't believe that dynamic IP assignment out of an address pool is possible with the 2.3 software. You can get different systems with proper PPP negotiation for much less. > was it configured to assert a particular IP based on password like most? > As I indicated, I asked that they should certainly refused IP's they > do not have authority over as a minimum, but I have no "real" > ability to do anything. I also love to constantly hear "the windows > and linux users do not have a problem" AAARRRRGGGG If you need to convince them that there is problem, see if the their mail server(s) is on the same subnet as the Netblazer and use that IP address. This will convince them quite quickly. > what is magic about 192.0.0.1? should ppp map a users configuration > request to some arbitrary alternate IP. Set ifaddr is there for > a purpose and even gives "ifaddr 0 0" in an example. Nothing is special about 192.0.0.1. No magic remapping should actually be taking place. Tom From owner-freebsd-current Mon Jul 3 18:44:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA03396 for current-outgoing; Mon, 3 Jul 1995 18:44:09 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA03375 ; Mon, 3 Jul 1995 18:44:04 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id LAA14517; Tue, 4 Jul 1995 11:19:08 +0930 From: Michael Smith Message-Id: <199507040149.LAA14517@genesis.atrad.adelaide.edu.au> Subject: Re: your mail To: lix@cs.pdx.edu (xiaoyin li) Date: Tue, 4 Jul 1995 11:19:03 +0930 (CST) Cc: current@freebsd.org, questions@freebsd.org In-Reply-To: <199507031924.MAA06715@cs.pdx.edu> from "xiaoyin li" at Jul 3, 95 12:24:49 pm Content-Type: text Content-Length: 1567 Sender: current-owner@freebsd.org Precedence: bulk xiaoyin li stands accused of saying: > I have installed netscape from ftp.netscape.com site on my FreeBSD > with 04/95 SNAPSHOT and X11R6. However, I got the following error > messages at my first try. I would apprecite very much if someone > could give me a direction how to fix this probelm. > > ------------------------------------------------------------------------------------- > books:/usr/X11R6/lib/X11 307 # netscape You're running as root. Bad idea. > books:/usr/X11R6/lib/X11 308 # > netscape: uname() failed; can't tell what system we're running on This is arguably a netscape bug. > netscape: locale `C' not supported. You haven't read the netscape documentation about setting the XNLSPATH environment variable. > Xlib: connection to ":0.0" refused by server > Xlib: Client is not authorized to connect to Server > Error: Can't open display: :0.0 You're root, but not logged in as root. If you're using startx or xinit, you'll have to ask someone else. If you're using xdm, add to root's .cshrc file : setenv XAUTHORITY ~$LOGNAME/.Xauthority Don't listen to anyone who says that you should use xhost; it's out of date and a security risk. > Xiaoyin Li -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" - Terry Lambert [[ From owner-freebsd-current Mon Jul 3 19:05:50 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA04233 for current-outgoing; Mon, 3 Jul 1995 19:05:50 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA04227 for ; Mon, 3 Jul 1995 19:05:48 -0700 Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id TAA05413; Mon, 3 Jul 1995 19:05:35 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id TAA05964; Mon, 3 Jul 1995 19:06:11 -0700 Message-Id: <199507040206.TAA05964@corbin.Root.COM> To: Peter Wemm cc: current@freebsd.org Subject: Re: comments on my favourite hack to traceroute? In-reply-to: Your message of "Mon, 03 Jul 95 10:04:11 +0800." From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 03 Jul 1995 19:06:11 -0700 Sender: current-owner@freebsd.org Precedence: bulk >This is my favourite hack to traceroute to rationalize the number of >digits printed in the rtt stats.. >The standard one prints three numbers after the decimal point, and when >you're up in the thousands of milliseconds (try going from australia to >the depths of europe some time.. :-), then the numbers are a bit of >overkill. It makes the display look very messy. > >I made a change to cause traceroute to only show a limited number of >significant digits.. That's similar to what the code did originally. I changed it because it incorrectly represents the precision and I find it a lot more difficult to read with varying numbers of decimal digits. I'm personally more interested in accuracy than I am in formatting. Besides, IMO, the solution to lines being too long has always been to use a larger window. :-) >From the CVS log: revision 1.2 date: 1994/08/29 17:45:43; author: davidg; state: Exp; lines: +1 -1 Changed output formatting to correctly represent the precision - it's not cool to truncate trailing zeros.. -DG From owner-freebsd-current Mon Jul 3 19:22:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA04617 for current-outgoing; Mon, 3 Jul 1995 19:22:48 -0700 Received: from haywire.DIALix.COM (peter@haywire.DIALix.COM [192.203.228.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA04608 for ; Mon, 3 Jul 1995 19:22:40 -0700 Received: (from peter@localhost) by haywire.DIALix.COM (8.6.12/8.6.12/DIALix) id KAA17484; Tue, 4 Jul 1995 10:22:05 +0800 Date: Tue, 4 Jul 1995 10:22:04 +0800 (WST) From: Peter Wemm To: David Greenman cc: current@freebsd.org Subject: Re: comments on my favourite hack to traceroute? In-Reply-To: <199507040206.TAA05964@corbin.Root.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk On Mon, 3 Jul 1995, David Greenman wrote: > > >This is my favourite hack to traceroute to rationalize the number of > >digits printed in the rtt stats.. > >The standard one prints three numbers after the decimal point, and when > >you're up in the thousands of milliseconds (try going from australia to > >the depths of europe some time.. :-), then the numbers are a bit of > >overkill. It makes the display look very messy. > > > >I made a change to cause traceroute to only show a limited number of > >significant digits.. > > That's similar to what the code did originally. I changed it because it > incorrectly represents the precision and I find it a lot more difficult to > read with varying numbers of decimal digits. I'm personally more interested > in accuracy than I am in formatting. Besides, IMO, the solution to lines being > too long has always been to use a larger window. :-) Yes, you're right.. The original code was broken - it would trim off trailing zeros, even if they were significant. The code I suggested would still print "1.000 ms", so it'd be easy to read while testing RTT's on ethernets and local-ish links. But "3000.001 ms" is ridiculous... When you're doing a traceroute over a links like that, you're hardly worried about +/- 100 ms.. I still think my way is better.. (of course.. :-) Also, bear in mind that it isn't always practical to resize the window on a physical terminal... > -DG > Cheers, -Peter From owner-freebsd-current Mon Jul 3 19:27:59 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA04739 for current-outgoing; Mon, 3 Jul 1995 19:27:59 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA04733 for ; Mon, 3 Jul 1995 19:27:56 -0700 Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id TAA05456; Mon, 3 Jul 1995 19:27:44 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id TAA06055; Mon, 3 Jul 1995 19:28:20 -0700 Message-Id: <199507040228.TAA06055@corbin.Root.COM> To: Peter Wemm cc: current@freebsd.org Subject: Re: comments on my favourite hack to traceroute? In-reply-to: Your message of "Tue, 04 Jul 95 10:22:04 +0800." From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 03 Jul 1995 19:28:20 -0700 Sender: current-owner@freebsd.org Precedence: bulk >Also, bear in mind that it isn't always practical to resize the window on >a physical terminal... Hey... blow-torch, some masking tape and a little superglue does it for me! :-) -DG From owner-freebsd-current Mon Jul 3 19:44:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA05288 for current-outgoing; Mon, 3 Jul 1995 19:44:39 -0700 Received: from bunyip.cc.uq.oz.au (bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id TAA05259 for ; Mon, 3 Jul 1995 19:43:09 -0700 Received: from s1.elec.uq.edu.au by bunyip.cc.uq.oz.au with SMTP (PP); Tue, 4 Jul 1995 12:42:08 +1000 Received: from s4.elec.uq.edu.au by s1.elec.uq.edu.au (4.0/SMI-4.0) id AA06315; Tue, 4 Jul 95 12:30:12 EST From: clary@elec.uq.oz.au (Clary Harridge) Message-Id: <9507040230.AA06315@s1.elec.uq.edu.au> Subject: Re: netscape causing reboot of diskless clients To: erich@jake.lodgenet.com (Eric L. Hernes) Date: Tue, 4 Jul 1995 12:41:07 +1000 (EST) Cc: freebsd-current@freebsd.org In-Reply-To: <199507031419.JAA10131@jake.lodgenet.com> from "Eric L. Hernes" at Jul 3, 95 09:19:56 am X-Mailer: ELM [version 2.4 PL22] Content-Type: text Content-Length: 1264 Sender: current-owner@freebsd.org Precedence: bulk Thanks for your reply Eric! > > > I find that since upgrading to FreeBSD 2.0-BUILT-19950615, > > diskless clients running XFree86-3.1, reboot when netscape is started. This also happens with other X clients > > > > If I change the DISPLAY from :0.0 to RemoteDisplay:0.0 I can run netscape OK. > > What kind of machine/os is running the NFS server? I've seen similar > problems with SCO being the server. I suspect that other SYSV (non R4) > implementations will be similar. The NFS server is a 486 running FreeBSD 2.0-BUILT-19950616 > > It seems that SCO's nfs won't allow fbsd to make named sockets. The X-server > tries to make some unix-domain sockets in /tmp which clients will use to > connect when using display :0.0. If the display is set to `hostname`:0.0, > the clients will use inet-domain sockets, and things will work. Even when I setenv DISPLAY `hostname`:0.0 the system reboots. > > I came up with two possible work arounds. > > 1) a small mfs for /tmp/.X11-unix (if ram is plentiful) How do you do this? Via fstab or /etc/rc? What parameters? -- regards Dept. of Electrical Engineering, Clary Harridge University of Queensland, QLD, Australia, 4072 Phone: +61-7-365-3636 Fax: +61-7-365-4999 INTERNET: clary@elec.uq.edu.au From owner-freebsd-current Mon Jul 3 19:47:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA05360 for current-outgoing; Mon, 3 Jul 1995 19:47:34 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA05354 for ; Mon, 3 Jul 1995 19:47:30 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id TAA00617; Mon, 3 Jul 1995 19:47:13 -0700 From: "Rodney W. Grimes" Message-Id: <199507040247.TAA00617@gndrsh.aac.dev.com> Subject: Re: comments on my favourite hack to traceroute? To: davidg@Root.COM Date: Mon, 3 Jul 1995 19:47:13 -0700 (PDT) Cc: peter@haywire.dialix.com, current@freebsd.org In-Reply-To: <199507040228.TAA06055@corbin.Root.COM> from "David Greenman" at Jul 3, 95 07:28:20 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 480 Sender: current-owner@freebsd.org Precedence: bulk > > >Also, bear in mind that it isn't always practical to resize the window on > >a physical terminal... > > Hey... blow-torch, some masking tape and a little superglue does it for me! > > :-) Too much work, when I go to resize one of those I only want to resize it one way, to zero, right into the trash can! :-) -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Mon Jul 3 20:00:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA06347 for current-outgoing; Mon, 3 Jul 1995 20:00:19 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA06340 for ; Mon, 3 Jul 1995 20:00:17 -0700 Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id UAA05526; Mon, 3 Jul 1995 20:00:04 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id UAA06139; Mon, 3 Jul 1995 20:00:40 -0700 Message-Id: <199507040300.UAA06139@corbin.Root.COM> To: jleppek@suw2k.ess.harris.com (James Leppek) cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@freefall.cdrom.com Subject: Re: ppp In-reply-to: Your message of "Mon, 03 Jul 95 08:09:29 EDT." <9507031209.AA01365@borg.ess.harris.com> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 03 Jul 1995 20:00:39 -0700 Sender: current-owner@FreeBSD.org Precedence: bulk >I would think it appropriate if someone would commit this >or better yet remove the offending lines from ppp/ipcp.c. I agree that I can find no reason to do this conversion. I've killed the lines and committed the change. -DG From owner-freebsd-current Mon Jul 3 21:28:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA11182 for current-outgoing; Mon, 3 Jul 1995 21:28:25 -0700 Received: from kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA11176 for ; Mon, 3 Jul 1995 21:28:23 -0700 Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by kitten.mcs.com (8.6.10/8.6.9) with SMTP id XAA15333; Mon, 3 Jul 1995 23:24:21 -0500 Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Mon, 3 Jul 95 21:41 CDT Received: by venus.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Mon, 3 Jul 95 21:41 CDT Message-Id: Subject: Re: ppp To: tom@uniserve.com (Tom Samplonius) Date: Mon, 3 Jul 1995 21:41:32 -0500 (CDT) From: "Karl Denninger, MCSNet" Cc: jleppek@suw2k.ess.harris.com, freebsd-current@freefall.cdrom.com In-Reply-To: from "Tom Samplonius" at Jul 3, 95 12:32:31 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1878 Sender: current-owner@FreeBSD.org Precedence: bulk > On Mon, 3 Jul 1995, James Leppek wrote: > > > How did you configure your netblazer(what they have) to do this? > > IMO, Netblazer's don't make a very good PPP server. I don't believe > that dynamic IP assignment out of an address pool is possible with the 2.3 > software. You can get different systems with proper PPP negotiation for > much less. You be nuts. Netblazers certainly do proper PPP negotiation. They can also, if you know what you're doing, handle FIXED ADDRESS PPP accounts in a multi-POP environment. I have used them for more than three years now. For flexibility, NOTHING touches them at this point in time. > > was it configured to assert a particular IP based on password like most? > > As I indicated, I asked that they should certainly refused IP's they > > do not have authority over as a minimum, but I have no "real" > > ability to do anything. I also love to constantly hear "the windows > > and linux users do not have a problem" AAARRRRGGGG > > If you need to convince them that there is problem, see if the their mail > server(s) is on the same subnet as the Netblazer and use that IP address. > This will convince them quite quickly. > > > what is magic about 192.0.0.1? should ppp map a users configuration > > request to some arbitrary alternate IP. Set ifaddr is there for > > a purpose and even gives "ifaddr 0 0" in an example. > > Nothing is special about 192.0.0.1. No magic remapping should actually > be taking place. > > Tom -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity Modem: [+1 312 248-0900] | (shell, PPP, SLIP, leased) in Chicagoland Voice: [+1 312 248-8649] | 7 Chicagoland POPs, ISDN, 28.8, much more Fax: [+1 312 248-9865] | Email to "info@mcs.net" WWW: http://www.mcs.net ISDN - Get it here TODAY! | Home of Chicago's only FULL AP Clarinet feed! From owner-freebsd-current Tue Jul 4 04:32:18 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA22686 for current-outgoing; Tue, 4 Jul 1995 04:32:18 -0700 Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA22675 for ; Tue, 4 Jul 1995 04:32:09 -0700 Received: (from dfr@localhost) by minnow.render.com (8.6.9/8.6.9) id MAA12739; Tue, 4 Jul 1995 12:32:18 +0100 Date: Tue, 4 Jul 1995 12:32:17 +0100 (BST) From: Doug Rabson To: michael butler cc: current@freebsd.org Subject: Re: NFS client no longer works :-( In-Reply-To: <199507011831.EAA04830@asstdc.scgt.oz.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk On Sun, 2 Jul 1995, michael butler wrote: > gw3:~ # mount asstdc:/usr/src /mnt > gw3:~ # ls /mnt > ls: /mnt: Stale NFS file handle > gw3:~ # umount /mnt > umount: P: No such file or directory > gw3:~ # mount > /dev/wd0a on / (NFS exported, local) > /dev/wd0e on /usr (NFS exported, local) > : > : > P on /mnt > > .. as of yesterday's sup (June 30th) :-( You have probably just upgraded to NFSv3 :-). For NFS clients, you must at least rebuild mount_nfs. You should also rebuild mountd nfsd nfsiod fstat, nfsstat, showmount, amd and pstat. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-current Tue Jul 4 06:49:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA25393 for current-outgoing; Tue, 4 Jul 1995 06:49:29 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id GAA25384 for ; Tue, 4 Jul 1995 06:49:12 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA10084; Tue, 4 Jul 1995 15:49:05 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA07288 for freebsd-current@FreeBSD.org; Tue, 4 Jul 1995 15:49:05 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id OAA00756 for freebsd-current@FreeBSD.org; Tue, 4 Jul 1995 14:11:55 +0200 From: J Wunsch Message-Id: <199507041211.OAA00756@uriah.heep.sax.de> Subject: Re: /etc/rc and "rm -f /var/spool/lock/*" To: freebsd-current@FreeBSD.org Date: Tue, 4 Jul 1995 14:11:55 +0200 (MET DST) Reply-To: freebsd-current@FreeBSD.org In-Reply-To: <28474.804792628@mumps.pfcs.com> from "Harlan Stenn" at Jul 3, 95 01:30:28 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 411 Sender: current-owner@FreeBSD.org Precedence: bulk As Harlan Stenn wrote: > > I suspect the real solution, then, will be to file ijppp. > > The problem is that when I start up "ppp -auto", it will almost always > come up with the same PID as the one from the previous boot, so if the Interesting race condition. :( -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Jul 4 06:50:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA25440 for current-outgoing; Tue, 4 Jul 1995 06:50:09 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id GAA25387 for ; Tue, 4 Jul 1995 06:49:27 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA10095; Tue, 4 Jul 1995 15:49:18 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA07301 for current@FreeBSD.org; Tue, 4 Jul 1995 15:49:17 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id OAA00884 for current@FreeBSD.org; Tue, 4 Jul 1995 14:28:09 +0200 From: J Wunsch Message-Id: <199507041228.OAA00884@uriah.heep.sax.de> Subject: Re: comments on my favourite hack to traceroute? To: current@FreeBSD.org Date: Tue, 4 Jul 1995 14:28:08 +0200 (MET DST) Reply-To: current@FreeBSD.org In-Reply-To: <199507040206.TAA05964@corbin.Root.COM> from "David Greenman" at Jul 3, 95 07:06:11 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 334 Sender: current-owner@FreeBSD.org Precedence: bulk As David Greenman wrote: > > ... Besides, IMO, the solution to lines being > too long has always been to use a larger window. :-) Provocative question: how do you do this with syscons? :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Jul 4 06:50:31 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA25475 for current-outgoing; Tue, 4 Jul 1995 06:50:31 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id GAA25468 for ; Tue, 4 Jul 1995 06:50:26 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA10069; Tue, 4 Jul 1995 15:48:56 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA07283 for freebsd-current@FreeBSD.org; Tue, 4 Jul 1995 15:48:55 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id OAA00739 for freebsd-current@FreeBSD.org; Tue, 4 Jul 1995 14:10:13 +0200 From: J Wunsch Message-Id: <199507041210.OAA00739@uriah.heep.sax.de> Subject: Re: /etc/rc and "rm -f /var/spool/lock/*" To: freebsd-current@FreeBSD.org Date: Tue, 4 Jul 1995 14:10:13 +0200 (MET DST) Reply-To: freebsd-current@FreeBSD.org In-Reply-To: <199507031550.KAA02622@id.slip.bcm.tmc.edu> from "Rich Murphey" at Jul 3, 95 10:50:40 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 771 Sender: current-owner@FreeBSD.org Precedence: bulk As Rich Murphey wrote: > > |Lock files suck. They should not be used at all, and the only client > |that really needs them right now is mgetty. > > What if you wanted to run outgoing hylafax and outgoing > 'ppp -auto' on the same port. Open the callout device with O_EXCL. The lock files are only for those programs that need to open callout devices where they should use callin devices. mgetty (or vgetty) are examples of programs that need to do it, since they wish to watch modem messages before the carrier is established. Regular getty uses the dialin device, where the open() blocks until the carrier is detected. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Jul 4 07:37:54 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA26580 for current-outgoing; Tue, 4 Jul 1995 07:37:54 -0700 Received: from wc.cdrom.com (wc.cdrom.com [192.216.223.37]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA26574 for ; Tue, 4 Jul 1995 07:37:52 -0700 Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by wc.cdrom.com (8.6.12/8.6.12) with ESMTP id HAA09545 for ; Tue, 4 Jul 1995 07:37:43 -0700 Received: (from dfr@localhost) by minnow.render.com (8.6.9/8.6.9) id PAA13281; Tue, 4 Jul 1995 15:35:15 +0100 Date: Tue, 4 Jul 1995 15:35:14 +0100 (BST) From: Doug Rabson To: freebsd-current@freebsd.org, Joerg Wunsch cc: freebsd-current@freebsd.org Subject: Re: /etc/rc and "rm -f /var/spool/lock/*" In-Reply-To: <199507041211.OAA00756@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk On Tue, 4 Jul 1995, J Wunsch wrote: > As Harlan Stenn wrote: > > > > I suspect the real solution, then, will be to file ijppp. > > > > The problem is that when I start up "ppp -auto", it will almost always > > come up with the same PID as the one from the previous boot, so if the > > Interesting race condition. :( Easy to test for though: lockpid = pid from file; if (lockpid == getpid() || !process_exists(lockpid)) stale lock file; else line is locked; -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-current Tue Jul 4 15:21:11 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA10871 for current-outgoing; Tue, 4 Jul 1995 15:21:11 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA10859 for ; Tue, 4 Jul 1995 15:21:10 -0700 Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id PAA06815; Tue, 4 Jul 1995 15:20:11 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id PAA02142; Tue, 4 Jul 1995 15:20:54 -0700 Message-Id: <199507042220.PAA02142@corbin.Root.COM> To: current@freebsd.org, joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: comments on my favourite hack to traceroute? In-reply-to: Your message of "Tue, 04 Jul 95 14:28:08 +0200." <199507041228.OAA00884@uriah.heep.sax.de> From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 04 Jul 1995 15:20:53 -0700 Sender: current-owner@freebsd.org Precedence: bulk >As David Greenman wrote: >> >> ... Besides, IMO, the solution to lines being >> too long has always been to use a larger window. :-) > >Provocative question: how do you do this with syscons? :) Run X on one of the VT's. :-) -DG From owner-freebsd-current Tue Jul 4 20:29:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA00212 for current-outgoing; Tue, 4 Jul 1995 20:29:04 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id UAA00190 ; Tue, 4 Jul 1995 20:28:59 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: current@freebsd.org cc: core@freebsd.org Subject: I'm rolling a SNAP on Friday. Date: Tue, 04 Jul 1995 20:28:58 -0700 Message-ID: <185.804914938@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@freebsd.org Precedence: bulk Just a general warning for those who want to roll any critical bug fixes into the tree first. Jordan From owner-freebsd-current Wed Jul 5 00:11:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA06009 for current-outgoing; Wed, 5 Jul 1995 00:11:13 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA05998 ; Wed, 5 Jul 1995 00:11:10 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id AAA02070; Wed, 5 Jul 1995 00:11:29 -0700 From: "Rodney W. Grimes" Message-Id: <199507050711.AAA02070@gndrsh.aac.dev.com> Subject: Re: I'm rolling a SNAP on Friday. To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Wed, 5 Jul 1995 00:11:29 -0700 (PDT) Cc: current@freebsd.org, core@freebsd.org In-Reply-To: <185.804914938@freefall.cdrom.com> from "Jordan K. Hubbard" at Jul 4, 95 08:28:58 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 482 Sender: current-owner@freebsd.org Precedence: bulk > > Just a general warning for those who want to roll any critical bug > fixes into the tree first. I will get your stuff pulled from the end of RELENG_2_0_5 into RELENG_2_1_0 some time tomarrow. I will also get my /etc/{rc*,sysconfig} stuff rolled in a few revisions back from where I am now (last good stable version)). -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Jul 5 00:59:53 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA09435 for current-outgoing; Wed, 5 Jul 1995 00:59:53 -0700 Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA09322 for ; Wed, 5 Jul 1995 00:58:00 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id RAA24350; Wed, 5 Jul 1995 17:57:06 +1000 From: michael butler Message-Id: <199507050757.RAA24350@asstdc.scgt.oz.au> Subject: Re: I'm rolling a SNAP on Friday. To: current@freebsd.org Date: Wed, 5 Jul 1995 17:57:04 +1000 (EST) Cc: jkh@freefall.cdrom.com (Jordan K. Hubbard) In-Reply-To: <185.804914938@freefall.cdrom.com> from "Jordan K. Hubbard" at Jul 4, 95 08:28:58 pm X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1815 Sender: current-owner@freebsd.org Precedence: bulk Jordan K. Hubbard writes: > Just a general warning for those who want to roll any critical bug > fixes into the tree first. Could someone please have another look at /sys/net/ip_fw.c. After the update (sup) as at July 4th 19:40 (UTC + 10), I'm still seeing a machine that panics and reboots when given packets to be refused :-( This is my script to add the rules .. #!/bin/sh # empty the rulesets ipfw f f # make localhost reachable ipfw addf accept all from any to 127.0.0.0/8 ipfw addf accept all from 127.0.0.0/8 to any # make multicast reachable for gated ipfw addf accept all from any to 224.0.0.0/8 ipfw addf accept all from 224.0.0.0/8 to any # two reachable servers at SCG ipfw addf accept all from any to 202.14.234.61 ipfw addf accept all from 202.14.234.61 to any ipfw addf accept all from any to 202.14.234.49 ipfw addf accept all from 202.14.234.49 to any # local primary net ipfw addf accept all from 202.14.234.65 to any ipfw addf accept all from any to 202.14.234.65 ipfw addf accept all from 202.14.234.69 to any ipfw addf accept all from any to 202.14.234.69 # local ppp dial-ins # ipfw addf accept all from 202.14.234.144/28 to any # ipfw addf accept all from any to 202.14.234.144/28 # local secondary net ipfw addf accept all from 202.12.127.67 to any ipfw addf accept all from any to 202.12.127.67 ipfw addf accept all from 202.12.127.65 to any ipfw addf accept all from any to 202.12.127.65 # icmp unreach to all not permitted as above - default case ipfw addf reject all from any to any # just in case something else falls through ipfw pol d exit 0 .. and a "ping 202.14.234.51" will panic it immediately .. I'm beginning to wonder if it's my machine. The "downlinks" on the other side of it are getting tired of it so I can't do too much more testing for a little while :-( michael From owner-freebsd-current Wed Jul 5 03:59:53 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA18038 for current-outgoing; Wed, 5 Jul 1995 03:59:53 -0700 Received: from disperse.demon.co.uk (disperse.demon.co.uk [158.152.1.77]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id DAA18028 ; Wed, 5 Jul 1995 03:59:47 -0700 Received: from post.demon.co.uk by disperse.demon.co.uk id aa23442; 5 Jul 95 11:41 +0100 Received: from bagpuss.demon.co.uk by post.demon.co.uk id aa23738; 5 Jul 95 11:41 +0100 Received: (karl@localhost) by bagpuss.demon.co.uk (3.1/3.1) id KAA08086; Wed, 5 Jul 1995 10:01:59 +0100 From: Karl Strickland Message-Id: <199507050901.KAA08086@bagpuss.demon.co.uk> Subject: Re: your mail To: Michael Smith Date: Wed, 5 Jul 1995 10:01:59 +0100 (BST) Cc: lix@cs.pdx.edu, current@freebsd.org, questions@freebsd.org In-Reply-To: <199507040149.LAA14517@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jul 4, 95 11:19:03 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 699 Sender: current-owner@freebsd.org Precedence: bulk > Don't listen to anyone who says that you should use xhost; it's out of > date and a security risk. Just to clarify - are you saying that xhost based security does not perform the function it is supposed to (ie only allow clients from certain hosts to connect to the server)? Or are you saying that the above does not provide adequate security when there is more than one user on a given machine? Cheers, Karl -- ------------------------------------------+----------------------------------- Mailed using ELM on FreeBSD | Karl Strickland PGP 2.3a Public Key Available. | Internet: karl@bagpuss.demon.co.uk | From owner-freebsd-current Wed Jul 5 05:54:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA22373 for current-outgoing; Wed, 5 Jul 1995 05:54:37 -0700 Received: from tserv.lodgenet.com (lodgenet@vie1.rrnet.com [198.81.198.10]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA22358 for ; Wed, 5 Jul 1995 05:53:11 -0700 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by tserv.lodgenet.com (8.6.12/8.6.12) with ESMTP id HAA27195; Wed, 5 Jul 1995 07:54:03 -0500 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.6.11/8.6.9) with SMTP id HAA24112; Wed, 5 Jul 1995 07:53:45 -0500 Message-Id: <199507051253.HAA24112@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6 4/21/95 To: clary@elec.uq.oz.au (Clary Harridge) cc: freebsd-current@freebsd.org Subject: Re: netscape causing reboot of diskless clients In-reply-to: Your message of "Tue, 04 Jul 1995 12:41:07 +1000." <9507040230.AA06315@s1.elec.uq.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Jul 1995 07:53:44 -0500 From: "Eric L. Hernes" Sender: current-owner@freebsd.org Precedence: bulk > > > > 1) a small mfs for /tmp/.X11-unix (if ram is plentiful) > How do you do this? Via fstab or /etc/rc? What parameters? > I have the following line in /etc/fstab /dev/null /tmp mfs rw,-s4000,-Tfd360 0 0 This makes an mfs for all of /tmp, beware if you're gonna do any heavy compiling and/or make use of /tmp. More correct would be to use /tmp/.X11-unix instead of /tmp for the mount point. I can't remember if /tmp gets rm -rf'ed on bootup, in which case you'll need to add something like [ -d /tmp/.X11-unix ] || mkdir /tmp/.X11-unix before the `mount -a' in /etc/rc some people use instead of /dev/null, if you do this, your mfs is the same size as your swap partition, and you don't need the -Tfd360. If you use /dev/null, you'll get warnings about calculated sectors per cylinder etc, but it seems to work. > > -- > regards Dept. of Electrical Engineering, > Clary Harridge University of Queensland, QLD, Australia, 4072 > Phone: +61-7-365-3636 Fax: +61-7-365-4999 > INTERNET: clary@elec.uq.edu.au > eric. -- erich@lodgenet.com erich@rrnet.com From owner-freebsd-current Wed Jul 5 11:14:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA29898 for current-outgoing; Wed, 5 Jul 1995 11:14:28 -0700 Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA29885 ; Wed, 5 Jul 1995 11:14:26 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by mail.barrnet.net (8.6.10/MAIL-RELAY-LEN) with ESMTP id KAA20832; Wed, 5 Jul 1995 10:28:20 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id DAA17916; Thu, 6 Jul 1995 03:00:19 +0930 From: Michael Smith Message-Id: <199507051730.DAA17916@genesis.atrad.adelaide.edu.au> Subject: Re: your mail To: karl@bagpuss.demon.co.uk (Karl Strickland) Date: Thu, 6 Jul 1995 03:00:18 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, lix@cs.pdx.edu, current@freebsd.org, questions@freebsd.org In-Reply-To: <199507050901.KAA08086@bagpuss.demon.co.uk> from "Karl Strickland" at Jul 5, 95 10:01:59 am Content-Type: text Content-Length: 1319 Sender: current-owner@freebsd.org Precedence: bulk Karl Strickland stands accused of saying: > > > Don't listen to anyone who says that you should use xhost; it's out of > > date and a security risk. My apologies for not being clearer; I was on a slow link, and typing the extra was too much like hard work 8) My intention was to ward off the inevitable "use xhost +" advice, which is a great way to make yourself vulnerable. > Just to clarify - are you saying that xhost based security does not perform > the function it is supposed to (ie only allow clients from certain hosts > to connect to the server)? Or are you saying that the above does not provide > adequate security when there is more than one user on a given machine? As far as I am aware, xhost performs its intended function, however it's intended function leaves certain windows of vulnerability, as you point out above. As such, I don't recommend it, particularly when Xauthority is so easily implemented. > Karl -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" - Terry Lambert [[ From owner-freebsd-current Wed Jul 5 16:39:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA11788 for current-outgoing; Wed, 5 Jul 1995 16:39:26 -0700 Received: from s5.elec.uq.edu.au (root@s5.elec.uq.edu.au [130.102.96.5]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA11782 for ; Wed, 5 Jul 1995 16:39:24 -0700 Received: (from clary@localhost) by s5.elec.uq.edu.au (8.6.11/8.6.9) id JAA24602 for freebsd-current@freebsd.org; Thu, 6 Jul 1995 09:39:22 +1000 From: Clary Harridge Message-Id: <199507052339.JAA24602@s5.elec.uq.edu.au> Subject: diskless NFS swap no longer works To: freebsd-current@freebsd.org Date: Thu, 6 Jul 1995 09:39:21 +1000 (EST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 613 Sender: current-owner@freebsd.org Precedence: bulk After an upgrade to current dated Jun 15. I find that my diskless systems no longer work. On the diskless client, which boots up OK, if I run something which requires pageing to the NFS swap partition, the diskless client reboots. Martin Renters advised me that, the NFS subsystem was upgraded to NFSv3, so this may be the problem. I would be interested to know if anyone has built and run a recent diskless system. -- regards Dept. of Electrical Engineering, Clary Harridge University of Queensland, QLD, Australia, 4072 Phone: +61-7-365-3636 Fax: +61-7-365-4999 INTERNET: clary@elec.uq.edu.au From owner-freebsd-current Wed Jul 5 17:07:41 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA12729 for current-outgoing; Wed, 5 Jul 1995 17:07:41 -0700 Received: from cs.pdx.edu (lix@cs.pdx.edu [131.252.20.183]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA12723 ; Wed, 5 Jul 1995 17:07:40 -0700 Received: (lix@localhost) by cs.pdx.edu (8.6.10/CATastrophe-12/23/94-P) id RAA27504; Wed, 5 Jul 1995 17:07:23 -0700 for Date: Wed, 5 Jul 1995 17:07:23 -0700 From: lix@cs.pdx.edu (xiaoyin li) Message-Id: <199507060007.RAA27504@cs.pdx.edu> To: current@freebsd.org, lix@cs.pdx.edu, quetions@freebsd.org Subject: netscape Sender: current-owner@freebsd.org Precedence: bulk I am able to access Netscape from my FreeBSD (04/95 SNAPSHOT & R11-6) machine with your people nice help. But I still have some problems. 1. When I invoke netscape, I get a bunch of warning messages as following before Netscape menu poped up. From owner-freebsd-current Wed Jul 5 18:12:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA14798 for current-outgoing; Wed, 5 Jul 1995 18:12:57 -0700 Received: from vax.cs.pitt.edu (vax.cs.pitt.edu [136.142.79.5]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA14786 for ; Wed, 5 Jul 1995 18:12:54 -0700 Received: from w2xo.pgh.pa.us by vax.cs.pitt.edu (8.6.10/1.14) for ; id VAA04645; Wed, 5 Jul 1995 21:13:10 -0400 Received: by w2xo.pgh.pa.us (8.6.10/1.34) id VAA02683; Wed, 5 Jul 1995 21:10:42 -0400 Date: Wed, 5 Jul 1995 21:10:42 -0400 From: durham@w2xo.pgh.pa.us (James C. Durham) Message-Id: <199507060110.VAA02683@w2xo.pgh.pa.us> To: freebsd-current@freebsd.org Subject: While you're at it!... Sender: current-owner@freebsd.org Precedence: bulk Hi, I'm the guy who was installing 2.0.5 ALPHA from floppies. I finally got around to installing 2.0.5 RELEASE and found a couple more little tweeks that need to be done... When it installs the root floppy, it apparently wants to see a 2nd root floppy. If you just shove in the bin floppy, it figures it out, but it could be confusing to some folks. Also, it would be great to include somewhere a warning that the root floppy must be left gzipped. (Whooops...). And...(finally).. the floppy sets for this distribution have to live in a *subdirectory* on the floppy..ie; bin/bin.aa . This is probably an oversight, since the earlier versions didn't work this way. I forget who's working on the install script, but thought this might get read and tweeked for the SNAP. -Jim Durham From owner-freebsd-current Wed Jul 5 18:26:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA15175 for current-outgoing; Wed, 5 Jul 1995 18:26:46 -0700 Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA15169 for ; Wed, 5 Jul 1995 18:26:41 -0700 Received: by haven.uniserve.com id <30757>; Wed, 5 Jul 1995 18:28:04 +0100 Date: Wed, 5 Jul 1995 18:27:53 -0700 (PDT) From: Tom Samplonius To: "James C. Durham" cc: freebsd-current@freebsd.org Subject: Re: While you're at it!... In-Reply-To: <199507060110.VAA02683@w2xo.pgh.pa.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk On Wed, 5 Jul 1995, James C. Durham wrote: > Also, it would be great to include somewhere a warning that the root > floppy must be left gzipped. (Whooops...). As I recall, none of images had *.gz suffixs, so why would anyone try to ungzip them? Tom From owner-freebsd-current Wed Jul 5 18:33:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA15473 for current-outgoing; Wed, 5 Jul 1995 18:33:27 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA15466 for ; Wed, 5 Jul 1995 18:33:19 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id LAA21203; Thu, 6 Jul 1995 11:28:28 +1000 Date: Thu, 6 Jul 1995 11:28:28 +1000 From: Bruce Evans Message-Id: <199507060128.LAA21203@godzilla.zeta.org.au> To: hohmuth@inf.tu-dresden.de Subject: Re: bin/594: "mkdir -p some/path/" fails to create last path component when path has trailing slash Cc: current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk > "mkdir -p some/path/" fails to create last path component when > path has trailing slash Note that ordinary mkdir(1) and mkdir(2) also fail to create "foo/" although POSIX specifies that paths to directories may have an optional trailing slash. I had this fixed in 1.1.5. There is an old PR about it. mkdir -p "foo/" has the additional bug that it exits with status 0 after failing to create "foo/". Bruce From owner-freebsd-current Wed Jul 5 18:48:30 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA15956 for current-outgoing; Wed, 5 Jul 1995 18:48:30 -0700 Received: from prosun.first.gmd.de (prosun.first.gmd.de [192.35.150.136]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA15950 for ; Wed, 5 Jul 1995 18:48:25 -0700 Received: from freebsd.first.gmd.de by prosun.first.gmd.de (4.1/SMI-4.1) id AA11407; Thu, 6 Jul 95 03:48:16 +0200 Received: by freebsd.first.gmd.de (EAA02333); Thu, 6 Jul 1995 04:52:14 +0200 From: Gerd Truschinski Message-Id: <199507060252.EAA02333@freebsd.first.gmd.de> Subject: A new utility To: freebsd-current@freebsd.org Date: Thu, 6 Jul 1995 04:52:13 +0159 (MET DST) X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1954 Sender: current-owner@freebsd.org Precedence: bulk Hi there, what about a new utility: the 'guru' ? A collections of 'fortunes' designed for the FreeBSD environment. BACKGROUND: About two month ago I saw that ATS (one of the core team) used the command 'script'. That was the thing I am missing the last eleven years. But I didn't see an advertisement anywhere. And from the man page I saw that ' The script command appeared in 3.0BSD'. There was the solution, but I didn't recognice it. The other example is the command 'ls -lrt' to see files and their age. I.e do YOU use the 'rt'-flag often? If you know this examples, you use them. But there is more in FreeBSD that most people didn't recognice. SOLUTION: A 'fortune'-like database with little hints from people who had just discovered a new feature of FreeBSD. Or even know about it several years. That means: Nothing you invoke in your .logout, like 'fortune'!r Something you invoke in you .login. Then you could play a little bit with this feature. OTHER HINTS: In FreeBSD there is a base set of commands and there are the packages. The problem is: DID YOU NEED THEM? And WHY?? Normaly there are small hints in the 'xxx/pkg/DESCR'-file. But noone tell you why you need i.e. 'gmake'. We have 'make'. What make 'gmake' superior to 'make'. Only a small hint will suffice. So, all of this packages need a better description. One, which shows you the advantages of this tools. And may it be only one samm point they get. Tell the other people where to get this point!!! THE GERMAN WAY: we nedd a maintainer of all the stuff.... Ok, I collect all things that people send me with the 'Subject:guru'. If it will be to much: I cry as loud as I can! So; start sending your samll hints. /gT/, also maintainer of the crossgcc mailing list -- Gerd Truschinski | Yes, this is the sort of scenario I gt@freebsd.first.gmd.de | think up to amuse myself in the evenings. emma@cs.tu-berlin.de | -- with confirmation from Larisa From owner-freebsd-current Thu Jul 6 00:47:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA09219 for current-outgoing; Thu, 6 Jul 1995 00:47:48 -0700 Received: from eikon.regent.e-technik.tu-muenchen.de (root@eikon.regent.e-technik.tu-muenchen.de [129.187.42.3]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA09213 ; Thu, 6 Jul 1995 00:47:33 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de ([129.187.142.36]) by eikon.regent.e-technik.tu-muenchen.de with SMTP id <55357>; Thu, 6 Jul 1995 09:46:38 +0200 Received: from localhost (localhost [127.0.0.1]) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) with SMTP id OAA01902; Wed, 5 Jul 1995 14:57:32 +0200 Message-Id: <199507051257.OAA01902@vector.eikon.e-technik.tu-muenchen.de> X-Authentication-Warning: vector.eikon.e-technik.tu-muenchen.de: Host localhost didn't use HELO protocol To: freebsd-current@freebsd.org (FreeBSD-current users), joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: Harlan.Stenn@pfcs.com (Harlan Stenn), core@freebsd.org Subject: Re: /etc/rc and "rm -f /var/spool/lock/*" In-reply-to: Your message of "Mon, 03 Jul 1995 11:08:53 +0200." <199507030908.LAA03564@uriah.heep.sax.de> Date: Wed, 5 Jul 1995 14:57:31 +0200 From: "Julian Stacey " Sender: current-owner@freebsd.org Precedence: bulk > From: J Wunsch > Lock files suck. They should not be used at all, and the only client > that really needs them right now is mgetty. My /var/spool/fax/etc/config.ttyd1 (for hylafax) has: UUCPLockDir /var/spool/lock # jhs added this after seeing where kermit created a lock. I haven't got round to checking if I need it. Julian S jhs@freefall From owner-freebsd-current Thu Jul 6 10:04:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA23356 for current-outgoing; Thu, 6 Jul 1995 10:04:02 -0700 Received: from crash.ops.neosoft.com (root@crash.ops.NeoSoft.COM [198.64.212.50]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA23347 ; Thu, 6 Jul 1995 10:04:00 -0700 Received: (from smace@localhost) by crash.ops.neosoft.com (8.6.11/8.6.10) id MAA00328; Thu, 6 Jul 1995 12:02:37 -0500 From: Scott Mace Message-Id: <199507061702.MAA00328@crash.ops.neosoft.com> Subject: if_ep driver To: hackers@freebsd.org, current@freebsd.org Date: Thu, 6 Jul 1995 12:02:36 -0500 (CDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 79 Sender: current-owner@freebsd.org Precedence: bulk Is anyone working on integrating the NetBSD 3com drivers into FreeBSD? Scott From owner-freebsd-current Thu Jul 6 10:27:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA24144 for current-outgoing; Thu, 6 Jul 1995 10:27:01 -0700 Received: from crash.ops.neosoft.com (root@crash.ops.NeoSoft.COM [198.64.212.50]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA24138 ; Thu, 6 Jul 1995 10:27:00 -0700 Received: (from smace@localhost) by crash.ops.neosoft.com (8.6.11/8.6.10) id MAA00423; Thu, 6 Jul 1995 12:25:36 -0500 From: Scott Mace Message-Id: <199507061725.MAA00423@crash.ops.neosoft.com> Subject: Re: if_ep driver To: smace@crash.ops.neosoft.com (Scott Mace) Date: Thu, 6 Jul 1995 12:25:36 -0500 (CDT) Cc: hackers@freebsd.org, current@freebsd.org In-Reply-To: <199507061702.MAA00328@crash.ops.neosoft.com> from "Scott Mace" at Jul 6, 95 12:02:36 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 181 Sender: current-owner@freebsd.org Precedence: bulk Also, on a side note, does anyone have any info for programming the RX filter on 3c509's for multicast? I currently have mine hacked to just receive ALL multicast packets. Scott From owner-freebsd-current Thu Jul 6 13:56:11 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA02700 for current-outgoing; Thu, 6 Jul 1995 13:56:11 -0700 Received: from eikon.regent.e-technik.tu-muenchen.de (root@eikon.regent.e-technik.tu-muenchen.de [129.187.42.3]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA02690 for ; Thu, 6 Jul 1995 13:56:08 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de ([129.187.142.36]) by eikon.regent.e-technik.tu-muenchen.de with SMTP id <55300>; Thu, 6 Jul 1995 22:55:51 +0200 Received: (from jhs@localhost) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) id WAA00855 for current@freebsd.org; Thu, 6 Jul 1995 22:55:08 +0200 Date: Thu, 6 Jul 1995 22:55:08 +0200 From: Julian Howard Stacey Message-Id: <199507062055.WAA00855@vector.eikon.e-technik.tu-muenchen.de> To: current@freebsd.org Subject: cd /usr/ports ; make -i fetch Sender: current-owner@freebsd.org Precedence: bulk Just to say "Thanks" to whoever (Satoshi etc I think ) made cd /usr/ports ; make -i fetch possible. I reccomend it to others, it keeps your modem nice & busy, while doing other interactive things, thus ensuring you squeeze maximum value out of your phone connection (& associated telecom bill). Julian S From owner-freebsd-current Thu Jul 6 17:22:53 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA10066 for current-outgoing; Thu, 6 Jul 1995 17:22:53 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id RAA10060 for ; Thu, 6 Jul 1995 17:22:50 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA08197; Fri, 7 Jul 1995 02:22:48 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id CAA13121 for freebsd-current@freebsd.org; Fri, 7 Jul 1995 02:22:47 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id PAA10254 for freebsd-current@freebsd.org; Thu, 6 Jul 1995 15:21:02 +0200 From: J Wunsch Message-Id: <199507061321.PAA10254@uriah.heep.sax.de> Subject: Re: /etc/rc and "rm -f /var/spool/lock/*" To: freebsd-current@freebsd.org Date: Thu, 6 Jul 1995 15:21:02 +0200 (MET DST) Reply-To: freebsd-current@freebsd.org In-Reply-To: <199507051257.OAA01902@vector.eikon.e-technik.tu-muenchen.de> from "Julian Stacey" at Jul 5, 95 02:57:31 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 995 Sender: current-owner@freebsd.org Precedence: bulk As Julian Stacey wrote: > > > > From: J Wunsch > > Lock files suck. They should not be used at all, and the only client > > that really needs them right now is mgetty. > > My /var/spool/fax/etc/config.ttyd1 (for hylafax) has: > UUCPLockDir /var/spool/lock # jhs added this after seeing where kermit created a lock. > I haven't got round to checking if I need it. If it's outgoing-only, it isn't needed. If it's also able to receive incoming fax messages, i guess you're going to use mgetty anyway. mgetty needs the lock files, since it cannot use the dialin port (it has to watch modem messages even while the modem is in the `not connected' state). The only way around would be to unblock the open() on a dialin port already on the `ring indicator' line instead of the `data carrier detect', as Terry once proposed. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Jul 6 22:03:05 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA16900 for current-outgoing; Thu, 6 Jul 1995 22:03:05 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA16889 for ; Thu, 6 Jul 1995 22:02:53 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA05751; Fri, 7 Jul 1995 15:01:15 +1000 Date: Fri, 7 Jul 1995 15:01:15 +1000 From: Bruce Evans Message-Id: <199507070501.PAA05751@godzilla.zeta.org.au> To: gordon@sneaky.lonestar.org Subject: Re: i386/596: \ and \ conflict with _POSIX_SOURCE Cc: current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk >>Synopsis: and conflict with _POSIX_SOURCE >>How-To-Repeat: > Compile the following 3-line program (cc -c x.c): > # define _POSIX_SOURCE > # include > # include > and get a flood of error messages starting with complaints > about rune_t (a typedef apparently not defined). > however, this works: > # define _POSIX_SOURCE > # include > # include Oops. They also work individually, so they should work in any order if they are idempotent. They aren't idempotent. bases its decision to declare rune_t (and wchar_t) on the undefined'ness of _BSD_WCHAR_T_, but uses _BSD_WCHAR_T_ to control only wchar_t if either _POSIX_SOURCE or _ANSI_SOURCE is defined. Fix: there should be a separate guard _BSD_RUNE_T_ for rune_t. rune_t should not be declared if _POSIX_SOURCE is defined and only the above headers are included, but this is a different bug. The separate guard is required to make the following work: #define _POSIX_SOURCE #include #include #include Bruce From owner-freebsd-current Thu Jul 6 22:23:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA17591 for current-outgoing; Thu, 6 Jul 1995 22:23:43 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA17583 for ; Thu, 6 Jul 1995 22:23:07 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA06214 for freebsd-current@freebsd.org; Fri, 7 Jul 1995 15:21:13 +1000 Date: Fri, 7 Jul 1995 15:21:13 +1000 From: Bruce Evans Message-Id: <199507070521.PAA06214@godzilla.zeta.org.au> To: freebsd-current@freebsd.org Subject: Re: /etc/rc and "rm -f /var/spool/lock/*" Sender: current-owner@freebsd.org Precedence: bulk >> My /var/spool/fax/etc/config.ttyd1 (for hylafax) has: >> UUCPLockDir /var/spool/lock # jhs added this after seeing where kermit created a lock. >> I haven't got round to checking if I need it. >If it's outgoing-only, it isn't needed. If it's also able to receive >incoming fax messages, i guess you're going to use mgetty anyway. >mgetty needs the lock files, since it cannot use the dialin port (it >has to watch modem messages even while the modem is in the `not >connected' state). Er, mgetty is supposed to be used on the dialin port. It does everything necessary to listen to the modem: open the port with O_NONBLOCK; set CLOCAL; clear O_NONBLOCK; listen to modem; then when connection is detected: clear CLOCAL; read and write to the connection. The last step apparently suffers from a race under FreeBSD-2.0: sometimes the connection is detected (according to the modem's messages) a long time (several tenths of a second) before carrier rises, and the connection isn't fully established before it is used. read() and write() terminate prematurely (as if the connection were closed) in FreeBSD-2.0. mgetty should probably worry more about the race because the semantics of read/write to a non-established connection (that must have been partially opened using O_NONBLOCK etc.) aren't clearly defined The problem was fixed in 1.1.5 by DTRT (blocking) for read/write to non-established connections. Bruce From owner-freebsd-current Fri Jul 7 05:53:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA11658 for current-outgoing; Fri, 7 Jul 1995 05:53:27 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA11651 for ; Fri, 7 Jul 1995 05:53:25 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id FAA05852; Fri, 7 Jul 1995 05:52:50 -0700 Date: Fri, 7 Jul 1995 05:52:50 -0700 Message-Id: <199507071252.FAA05852@silvia.HIP.Berkeley.EDU> To: jhs@vector.eikon.e-technik.tu-muenchen.de CC: current@freebsd.org In-reply-to: <199507062055.WAA00855@vector.eikon.e-technik.tu-muenchen.de> (message from Julian Howard Stacey on Thu, 6 Jul 1995 22:55:08 +0200) Subject: Re: cd /usr/ports ; make -i fetch From: asami@cs.berkeley.edu (Satoshi Asami) Sender: current-owner@freebsd.org Precedence: bulk * Just to say "Thanks" to whoever (Satoshi etc I think ) That was done by Paul's request, so say thanks to him too.... :) * made * cd /usr/ports ; make -i fetch * possible. * I reccomend it to others, it keeps your modem nice & busy, while doing * other interactive things, thus ensuring you squeeze maximum value out of * your phone connection (& associated telecom bill). Also don't forget Jordan's "make fetch-list" command, especially useful if your FreeBSD machine is not IP connected. Satoshi From owner-freebsd-current Fri Jul 7 06:48:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA13129 for current-outgoing; Fri, 7 Jul 1995 06:48:06 -0700 Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA13121 for ; Fri, 7 Jul 1995 06:47:44 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id XAA02850 for current@freebsd.org; Fri, 7 Jul 1995 23:47:18 +1000 From: michael butler Message-Id: <199507071347.XAA02850@asstdc.scgt.oz.au> Subject: wrong alias selection ? To: current@freebsd.org Date: Fri, 7 Jul 1995 23:47:17 +1000 (EST) X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 563 Sender: current-owner@freebsd.org Precedence: bulk Has anything changed in the selection of addresses with which to respond to queries such as traceroute .. asstdc:~ % /usr/sbin/traceroute percy traceroute to percy.scgt.oz.au (202.14.234.61), 30 hops max, 40 byte packets 1 sarah.asstdc.com.au (202.12.127.65) 2.461 ms 1.714 ms 1.597 ms 2 percy (202.14.234.61) 198.035 ms 187.850 ms 177.563 ms asstdc has a single address of 202.14.234.65, sarah is an "ifconfig ed0 .. alias" for gw3.scgt.oz.au at 202.14.234.69 This did not happen prior to 2.0.5, but I can't say precisely when it changed, michael From owner-freebsd-current Fri Jul 7 17:12:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA00718 for current-outgoing; Fri, 7 Jul 1995 17:12:24 -0700 Received: from deep-thought.demos.su (root@deep-thought.demos.su [192.91.186.133]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA00712 for ; Fri, 7 Jul 1995 17:12:19 -0700 Received: by deep-thought.demos.su id EAA03735; (8.6.11/D) Sat, 8 Jul 1995 04:12:01 +0400 To: current@freebsd.org Message-ID: Organization: DEMOS Date: Sat, 8 Jul 1995 04:12:00 +0400 (MSD) X-Mailer: Mail/@ [v2.38 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka "Andrey A. Chernov, Black Mage" X-Class: Fast Subject: When ports-emulators SUP target will be available? Lines: 5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 293 Sender: current-owner@freebsd.org Precedence: bulk -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Fri Jul 7 21:43:50 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA18192 for current-outgoing; Fri, 7 Jul 1995 21:43:50 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA18060 for ; Fri, 7 Jul 1995 21:43:38 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id OAA14323 for freebsd-current@freebsd.org; Sat, 8 Jul 1995 14:39:07 +1000 Date: Sat, 8 Jul 1995 14:39:07 +1000 From: Bruce Evans Message-Id: <199507080439.OAA14323@godzilla.zeta.org.au> To: freebsd-current@freebsd.org Subject: Re: /etc/rc and "rm -f /var/spool/lock/*" Sender: current-owner@freebsd.org Precedence: bulk >> |Lock files suck. They should not be used at all, and the only client >> |that really needs them right now is mgetty. >> >> What if you wanted to run outgoing hylafax and outgoing >> 'ppp -auto' on the same port. >Open the callout device with O_EXCL. Erm, O_EXCL is useless for locking devices in FreeBSD. POSIX specifies the behaviour for open() with both O_CREAT and O_EXCL set. This behaviour is useless for locking of devices (it only works of the file doesn't already exist, and non-existent files aren't devices). The behaviour is implementation-defined if only O_EXCL is set. In FreeBSD, the behaviour is to ignore O_EXCL. FreeBSD provides the TIOCEXCL ioctl. This is not so good in theory (open() + ioctl() isn't atomic, so the locking can at best be advisory) and is worse in practice (the ioctl always succeeds and no advise is given about prior locking; also, the locking doesn't apply to root). Bruce From owner-freebsd-current Sat Jul 8 00:47:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA08970 for current-outgoing; Sat, 8 Jul 1995 00:47:15 -0700 Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA08744 for ; Sat, 8 Jul 1995 00:46:56 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id RAA17990; Sat, 8 Jul 1995 17:45:45 +1000 From: michael butler Message-Id: <199507080745.RAA17990@asstdc.scgt.oz.au> Subject: Re: bin/594: "mkdir -p some/path/" fails to create last path component when path has trailing slash To: bde@zeta.org.au (Bruce Evans) Date: Sat, 8 Jul 1995 17:45:43 +1000 (EST) Cc: current@freebsd.org In-Reply-To: <199507060128.LAA21203@godzilla.zeta.org.au> from "Bruce Evans" at Jul 6, 95 11:28:28 am X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 477 Sender: current-owner@freebsd.org Precedence: bulk Bruce Evans writes: > > "mkdir -p some/path/" fails to create last path component when > > path has trailing slash > Note that ordinary mkdir(1) and mkdir(2) also fail to create "foo/" > although POSIX specifies that paths to directories may have an optional > trailing slash. I had this fixed in 1.1.5. There is an old PR about it. The problem is more widespread .. "rmdir foo/" fails and complains of "foo is a directory" (!) and "rm -rf foo/" does likewise, michael From owner-freebsd-current Sat Jul 8 01:28:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA26461 for current-outgoing; Sat, 8 Jul 1995 01:28:43 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA26420 for ; Sat, 8 Jul 1995 01:28:32 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id SAA22164; Sat, 8 Jul 1995 18:23:14 +1000 Date: Sat, 8 Jul 1995 18:23:14 +1000 From: Bruce Evans Message-Id: <199507080823.SAA22164@godzilla.zeta.org.au> To: bde@zeta.org.au, imb@scgt.oz.au Subject: Re: bin/594: "mkdir -p some/path/" fails to create last path component when path has trailing slash Cc: current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk >> > "mkdir -p some/path/" fails to create last path component when >> > path has trailing slash > >> Note that ordinary mkdir(1) and mkdir(2) also fail to create "foo/" >> although POSIX specifies that paths to directories may have an optional >> trailing slash. I had this fixed in 1.1.5. There is an old PR about it. >The problem is more widespread .. "rmdir foo/" fails and complains of "foo >is a directory" (!) and "rm -rf foo/" does likewise, Yes, the handling of trailing slashes is broken in all cases. "foo/" sometimes means "foo/." but sometimes it is rejected without even looking at the type of the file "foo". E.g., `touch /etc/passwd/' says that /etc/passwd/ is a directory! Bruce From owner-freebsd-current Sat Jul 8 15:56:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA08472 for current-outgoing; Sat, 8 Jul 1995 15:56:47 -0700 Received: from haywire.DIALix.COM (root@haywire.DIALix.COM [192.203.228.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA08435 for ; Sat, 8 Jul 1995 15:56:43 -0700 Received: (from news@localhost) by haywire.DIALix.COM (8.6.12/8.6.12/DIALix) id GAA16167 for freebsd-current@freebsd.org; Sun, 9 Jul 1995 06:13:49 +0800 Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-current@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-current@freebsd.org Date: 9 Jul 1995 06:13:27 +0800 From: peter@haywire.dialix.com (Peter Wemm) Message-ID: <3tmvu7$fo7$1@haywire.DIALix.COM> Organization: DIALix Services, Perth, Australia. Subject: Version numbers of the different branches? Sender: current-owner@freebsd.org Precedence: bulk One thing that's bugged me for a while now, is that FreeBSD-current announces itself as "2.0-xxxxxx", even though it's actually working towards being FreeBSD-2.2 Not that it's a really big issue, but I wouldn't mind it being consistant somehow. How about making it either "2.2-BUILT-xxxxxx" or "2.X-BUILT-xxxxx" or even "2.X-CURRENT-xxxxxx". Of course, this means the newvers.sh file is going to have to be branched into 2.0.5, 2.1 and -current.. Cheers, -Peter From owner-freebsd-current Sat Jul 8 16:05:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA13368 for current-outgoing; Sat, 8 Jul 1995 16:05:15 -0700 Received: from haywire.DIALix.COM (peter@haywire.DIALix.COM [192.203.228.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA13331 for ; Sat, 8 Jul 1995 16:05:12 -0700 Received: (from peter@localhost) by haywire.DIALix.COM (8.6.12/8.6.12/DIALix) id HAA20161; Sun, 9 Jul 1995 07:05:05 +0800 Date: Sun, 9 Jul 1995 07:05:01 +0800 (WST) From: Peter Wemm To: current@freebsd.org Subject: Comments? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk When you do a make to build the source from scratch, send-pr isn't rebuilt to include the new build-date, because send-pr is built once, and the there are no dependencies to cause it to be remade when the RELEASE variable changes. How does this look for a suggested change? I know, it depends on the user's path, but that can be fixed.. This is a suggestion of a possible style of change only.. -Peter (PS: There is a "RELEASE!= uname -rsm" at the top of the Makefile) Index: Makefile =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/send-pr/Makefile,v retrieving revision 1.6 diff -u -r1.6 Makefile --- 1.6 1995/01/16 17:49:20 +++ Makefile 1995/07/08 22:57:20 @@ -13,11 +13,10 @@ send-pr: send-pr.sh Makefile sed -e 's,@DATADIR@,/etc,g' \ - -e 's/@DEFAULT_RELEASE@/$(RELEASE)/g' \ -e 's/^SUBMITTER=.*/SUBMITTER=$(SUBMITTERS)/' \ ${.ALLSRC:N*Makefile} > ${.TARGET} -send-pr.el: send-pr-el.in Makefile +send-pr.el: send-pr-el.in Makefile /usr/bin/uname sed -e 's,@DATADIR@,/etc,g' \ -e 's/@DEFAULT_RELEASE@/$(RELEASE)/g' \ -e 's/"unknown"/"$(SUBMITTERS)"/g' \ Index: send-pr.sh =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/send-pr/send-pr.sh,v retrieving revision 1.5 diff -u -r1.5 send-pr.sh --- 1.5 1994/11/10 02:34:54 +++ send-pr.sh 1995/07/08 22:57:55 @@ -40,7 +40,7 @@ [ ! -d $DATADIR/gnats -a -d "$GCC_EXEC_PREFIX" ] && DATADIR=@DATADIR@ # The default release for this host. -DEFAULT_RELEASE="@DEFAULT_RELEASE@" +DEFAULT_RELEASE="`uname -rsm`" # The default organization. DEFAULT_ORGANIZATION= From owner-freebsd-current Sat Jul 8 17:58:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAB13301 for current-outgoing; Sat, 8 Jul 1995 17:58:52 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA13293 for ; Sat, 8 Jul 1995 17:58:24 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id KAA14573; Sun, 9 Jul 1995 10:55:08 +1000 Date: Sun, 9 Jul 1995 10:55:08 +1000 From: Bruce Evans Message-Id: <199507090055.KAA14573@godzilla.zeta.org.au> To: current@freebsd.org, peter@haywire.DIALix.COM Subject: Re: Comments? Sender: current-owner@freebsd.org Precedence: bulk >How does this look for a suggested change? I know, it depends on the >user's path, but that can be fixed.. This is a suggestion of a possible >style of change only.. Fine for the uname change, but we usually don't make things dependent on Makefiles - everything potentially depends on its Makefiles (and on all included Makefiles) are included but we don't want everything to be recompiled when Makefiles are changed. Bruce