From owner-freebsd-current Sun Jun 25 01:16:11 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA13413 for current-outgoing; Sun, 25 Jun 1995 01:16:11 -0700 Received: from ufrmsa1.olivetti.za (root@ufrmsa1.Olivetti.za [160.124.2.20]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id BAA13402 for ; Sun, 25 Jun 1995 01:16:00 -0700 Received: from neptune by ufrmsa1.olivetti.za with uucp (Smail3.1.29.1 #3) id m0sPqZG-000IjIC; Sun, 25 Jun 95 10:13 GMT-0200 Received: by neptune.ru.ac.za (Smail3.1.28.1 #10) id m0sPmhP-00005XC; Sun, 25 Jun 95 10:05 SAT Message-Id: Subject: Re: Crypt code summary(2). To: mark@grondar.za (Mark Murray) Date: Sun, 25 Jun 1995 10:05:47 +0200 (SAT) Cc: rgrimes@gndrsh.aac.dev.com, mark@grondar.za, paul@freebsd.org, current@freebsd.org, csgr@freebsd.org, Wollman@halloran-eldar.lcs.mit.edu, jkh@freefall.cdrom.com, gibbs@freefall.cdrom.com In-Reply-To: <199506242106.XAA04478@grumble.grondar.za> from "Mark Murray" at Jun 24, 95 11:06:39 pm From: geoff%neptune@ufrmsa1.olivetti.za Reply-To: geoff%neptune@ufrmsa1.olivetti.za X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2143 Sender: current-owner@freebsd.org Precedence: bulk Mark Murray writes : > > > > The kind folks at CSIR in South Africa who give me the Skeleton site for > > > sourcing the crypto stuff have offered their machine for just this! > > > (See mail to -hackers and bounce by me to the -current list). They are > > > offering this machine as a full-blown code maintenance (cvs, ctm etc) > > > site. > > > > I have read these, and it looks to be a reasonable site. I still need > > clarification on the legality of importing DES and crypto code from that > > site to a US site. After that is done we would need a machine running > > FreeBSD to set up the cvs/ctm/sup stuff on, heck if I am going to try > > and port that to any other platform or even try!!! > > This site is running FreeBSD (an old-ish -current). I think that we must also emphasise that we now have a group of people here in .za (Mark, the guys at the CSIR, and - believe it or not :-) :-) - myself) who are committed to getting a CVS repository site/FreeBSD archive site here in .za. As I mentioned on another thread, Mark has agreed to prick my conscience in order to get me a bit more active with FreeBSD again. With my (attempted) reentry into the FreeBSD fray I hope I can get a bit of work in in this area. I am prepared (if necessary) to make a few of trips (evenings and weekends - time permitting) to the CSIR to assist in any config work required on skeleton. (That includes getting it up to -current, work on CVS etc. and any work required to get the machine fully up to steam.) (For me to get to the CSIR is not too far - it's just a trip to Pretoria.) Other areas to look at include getting skeleton running CTM etc. Also, to reiterate a few things discussed on the phone with Mark yesterday: I fully support Mark taking on the leadership role in the work on the secure/crypt bits. With Mark at the helm on this one, I hope we should be able to get some reasonable progress. Geoff. -- Geoff Rehmet | ____ _ o /\ geoff@neptune.ru.ac.za |___ _-\_<, / /\/\ "finger -l rehmet@cs.ru.ac.za" for PGP key | (*)/'(*) /\/ / \ \ From owner-freebsd-current Sun Jun 25 02:07:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA15328 for current-outgoing; Sun, 25 Jun 1995 02:07:16 -0700 Received: from dns.netvision.net.il (root@dns.NetVision.net.il [194.90.1.5]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA15320 for ; Sun, 25 Jun 1995 02:07:13 -0700 Received: from Burka.NetVision.net.il (root@Burka.NetVision.net.il [194.90.6.15]) by dns.netvision.net.il (8.6.12/8.6.9) with ESMTP id MAA27541; Sun, 25 Jun 1995 12:07:44 +0300 Received: from gena@NetVision.net.il (Burka.NetVision.net.il [194.90.6.15]) by Burka.NetVision.net.il (8.6.11/8.6.6) with SMTP id MAA00257; Sun, 25 Jun 1995 12:20:27 +0300 Date: Sun, 25 Jun 1995 12:20:27 +0300 Message-ID: X-Face: #v>4HN>#D_"[olq9y`HqTYkLVB89Xy|3')Vs9v58JQ*u-xEJVKY`xa.}E?z0RkLI/P&;BJmi0#u=W0).-Y'J4(dw{"54NhSG|YYZG@[)(`e! >jN#L!~qI5fE-JHS+< Organization: NetVision ltd. X-Mailer: XFMail 0.2-Beta on FreeBSD From: Gennady Sorokopud To: Subject: no bell under Xinside server Cc: "Gennady B. Sorokopud" Sender: current-owner@FreeBSD.org Precedence: bulk Hello! I noticed that if i'm running Xinside X-server speaker bell does not work. (But it works perfectly with pcvt console driver) After some investigation i find out that ioctl that is responsible for "beeping" under X is missing in syscons.c . After applying the following patch things got back to normal. *** /sys/i386/isa/syscons.c.org Sun Jun 25 11:29:54 1995 --- /sys/i386/isa/syscons.c Sun Jun 25 11:30:56 1995 *************** *** 488,493 **** --- 488,501 ---- switch (cmd) { /* process console hardware related ioctl's */ + case CONS_XBELL: + if (*data) + do_bell(scp, ((int*)data)[0] & 0xffff, + ( ((int*)data)[1] & 0xffff ) * hz / 1000); + else + do_bell(scp, scp->bell_pitch, scp->bell_duration); + return 0; + case GIO_ATTR: /* get current attributes */ *(int*)data = scp->term.cur_attr; return 0; *** /sys/i386/include/console.h.org Sun Jun 25 11:31:26 1995 --- /sys/i386/include/console.h Sun Jun 25 11:32:05 1995 *************** *** 77,82 **** --- 77,83 ---- #define GIO_FONT8x16 _IOR('c', 69, fnt16_t) #define CONS_GETINFO _IOWR('c', 73, vid_info_t) #define CONS_GETVERS _IOR('c', 74, int) + #define CONS_XBELL _IOW('t', 123, int[2]) #define VT_OPENQRY _IOR('v', 1, int) #define VT_SETMODE _IOW('v', 2, vtmode_t) I'd really appreciate if someone with commit privileges could commit this patch. -------- Gennady B. Sorokopud - System programmer at NetVision Israel. E-Mail: gena@NetVision.net.il Homepage: http://www.netvision.net.il/~gena This message was sent at 06/25/95 12:09:30 by XF-Mail From owner-freebsd-current Sun Jun 25 10:56:03 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA29270 for current-outgoing; Sun, 25 Jun 1995 10:56:03 -0700 Received: from pelican.com (pelican.com [134.24.4.62]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA29263 for ; Sun, 25 Jun 1995 10:55:57 -0700 Received: from puffin.pelican.com by pelican.com with smtp (Smail3.1.28.1 #5) id m0sPvuN-000K0hC; Sun, 25 Jun 95 10:55 WET DST Received: (from pete@localhost) by puffin.pelican.com (8.6.11/8.6.9) id RAA14968; Sun, 25 Jun 1995 17:55:47 GMT Date: Sun, 25 Jun 1995 17:55:47 GMT From: Pete Carah Message-Id: <199506251755.RAA14968@puffin.pelican.com> To: bde@freefall.cdrom.com Subject: Re: cvs commit: src/sys/i386/isa sio.c In-Reply-To: <199506250451.VAA08729@freefall.cdrom.com> Cc: current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk In article <199506250451.VAA08729@freefall.cdrom.com> you write: >bde 95/06/24 21:51:02 > Modified: sys/i386/isa sio.c ..... > specified (as before). `LOSESOUTINTS' ports are ones with 0x08 set in > their config flags. Unless this flag is set, it will now take up to one > second to recover from lost output interrupts, if any. Some 8250s and > 16450s lose output interrupts. *ALL* real NS parts (prior to 1993, anyhow) lose output ints, as do the C&T ones then too. This *does* include 16550AFN and may or may not include 16550D (I can test; I just got a set). Don't know about Taiwanese ones. This is per both experience and the NS app notes (they finally admitted it in 1991...) I don't know if NS has ever published a set of mask steps and/or date codes that have/don't have this bug. Because of this, loses-out-ints should be the default and a flag set if a person *knows* that they don't have the bug; more chips have it than don't, and it breaks 'g' protocol pretty badly with a 1-second recovery. The lose-out-int case looks obscure but on a fast bidir conversation it tends to attack every few seconds. (ppp and Taylor 'i' should show it; very little else that most people do would.) My slip connection (to a Cisco term server) tends to not be truly bidirectional; I don't know why; likely has to do with interrupting the modem's compression stream. For those not in-the-know, the loses-out-ints comes about because a read of the interrupt id register resets a pending transmit interrupt whether or not it was the id that was read (read and read-error are higher priority). Some 8259 clones suffered from a similar problem; that is why AUTO_EOI often isn't a good idea. All else in this commit looks fine here; the slow of poll when nothing is open won't hurt LOSESOUTINTS ports either... (one might include open-wait in non-open since getty doesn't depend on output ints until woken up.) -- Pete From owner-freebsd-current Sun Jun 25 11:15:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA00354 for current-outgoing; Sun, 25 Jun 1995 11:15:34 -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 LAA00333 for ; Sun, 25 Jun 1995 11:15:26 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id EAA04120; Mon, 26 Jun 1995 04:10:52 +1000 Date: Mon, 26 Jun 1995 04:10:52 +1000 From: Bruce Evans Message-Id: <199506251810.EAA04120@godzilla.zeta.org.au> To: current@freebsd.org, gena@NetVision.net.il Subject: Re: no bell under Xinside server Sender: current-owner@freebsd.org Precedence: bulk >I noticed that if i'm running Xinside X-server speaker bell does not >work. >(But it works perfectly with pcvt console driver) >After some investigation i find out that ioctl that is responsible >for "beeping" under X is missing in syscons.c . It went away in revision 1.88 1995/01/12 and I think it was broken in syscons before that, so nothing should have been using it. >+ #define CONS_XBELL _IOW('t', 123, int[2]) Its name was CONSOLE_X_BELL in syscons and it still has that name in pcvt. Bruce From owner-freebsd-current Sun Jun 25 12:20:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA03482 for current-outgoing; Sun, 25 Jun 1995 12:20:36 -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 MAA03476 ; Sun, 25 Jun 1995 12:20:29 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id FAA05169; Mon, 26 Jun 1995 05:18:32 +1000 Date: Mon, 26 Jun 1995 05:18:32 +1000 From: Bruce Evans Message-Id: <199506251918.FAA05169@godzilla.zeta.org.au> To: bde@freefall.cdrom.com, pete@puffin.pelican.com Subject: Re: cvs commit: src/sys/i386/isa sio.c Cc: current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk >> specified (as before). `LOSESOUTINTS' ports are ones with 0x08 set in >> their config flags. Unless this flag is set, it will now take up to one >> second to recover from lost output interrupts, if any. Some 8250s and >> 16450s lose output interrupts. >*ALL* real NS parts (prior to 1993, anyhow) lose output ints, as do the >C&T ones then too. This *does* include 16550AFN and may or may not include I haven't seen the problem for any part later than 1988 but I don't think I have any "real NS" parts (I may have a couple of Intel ones). >Because of this, loses-out-ints should be the default and a flag set if >a person *knows* that they don't have the bug; more chips have it than >don't, and it breaks 'g' protocol pretty badly with a 1-second recovery. Try it and see. >The lose-out-int case looks obscure but on a fast bidir conversation it >tends to attack every few seconds. (ppp and Taylor 'i' should show sio uses several methods to reduce the problem so it may not occur very often. In particular, it is recovered from on the next input interrupt, so streaming protocols recover within a few character times. >it; very little else that most people do would.) My slip connection >(to a Cisco term server) tends to not be truly bidirectional; I don't >know why; likely has to do with interrupting the modem's compression >stream. I've been complaining about this for a year or two. I think it is because tcp/ip wasn't designed for bidirectional interface. My standard benchmark is: time rcp machine1:/kernel machine2:/tmp/kernel & \ time rcp machine2:/kernel machine1:/tmp/kernel & This takes about twice as long as would separate rcp's because acks get queued behind large amounts of data and arrive too late to keep the data streaming. >For those not in-the-know, the loses-out-ints comes about because a read >of the interrupt id register resets a pending transmit interrupt whether >or not it was the id that was read (read and read-error are higher >priority). Some 8259 clones suffered from a similar problem; that is >why AUTO_EOI often isn't a good idea. sio tries to avoid this problem by reading the interrupt id register as little as possible. Unfortunately it has to read it at the start of the (loop in the) interrupt handler for the COM_MULTIPORT case. Otherwise, it only reads it at the end of the (loop in the) interrupt handler. It only has to do this to handle edge triggering braindamage. Also, sio doesn't rely on the interrupt id register for anything except the end-of-interrupt condition. Output-possible is checked for directly after checking (directly) for input. This should completely fix the above bug - if a higher priority event is seen, then output will be checked for a little later (later enough for races not to be a problem). So perhaps LOSESOUTINTS is never necessary. But there may be other chip bugs. I think there is a similar problem with lost modem status interrupts. Bruce From owner-freebsd-current Sun Jun 25 12:33:21 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA04019 for current-outgoing; Sun, 25 Jun 1995 12:33:21 -0700 Received: (from phk@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA04009 ; Sun, 25 Jun 1995 12:33:20 -0700 From: Poul-Henning Kamp Message-Id: <199506251933.MAA04009@freefall.cdrom.com> Subject: Re: cvs commit: src/sys/i386/isa sio.c To: bde@zeta.org.au (Bruce Evans) Date: Sun, 25 Jun 1995 12:33:20 -0700 (PDT) Cc: bde@freefall.cdrom.com, pete@puffin.pelican.com, current@freebsd.org In-Reply-To: <199506251918.FAA05169@godzilla.zeta.org.au> from "Bruce Evans" at Jun 26, 95 05:18:32 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 751 Sender: current-owner@freebsd.org Precedence: bulk > I've been complaining about this for a year or two. I think it is because > tcp/ip wasn't designed for bidirectional interface. My standard benchmark > is: > > time rcp machine1:/kernel machine2:/tmp/kernel & \ > time rcp machine2:/kernel machine1:/tmp/kernel & > > This takes about twice as long as would separate rcp's because acks get > queued behind large amounts of data and arrive too late to keep the data > streaming. Have you tried making your tcp-windows bigger ? -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Just that: dried leaves in boiling water ? From owner-freebsd-current Sun Jun 25 12:44:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA04533 for current-outgoing; Sun, 25 Jun 1995 12:44:46 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA04526 ; Sun, 25 Jun 1995 12:44:44 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA17255; Sun, 25 Jun 1995 15:44:05 -0400 Date: Sun, 25 Jun 1995 15:44:05 -0400 From: Garrett Wollman Message-Id: <9506251944.AA17255@halloran-eldar.lcs.mit.edu> To: Mark Murray Cc: "Rodney W. Grimes" , paul@freebsd.org, current@freebsd.org, csgr@freebsd.org, Wollman@halloran-eldar.lcs.mit.edu, jkh@freefall.cdrom.com, gibbs@freefall.cdrom.com Subject: Crypt code summary(2). In-Reply-To: <199506241552.RAA03235@grumble.grondar.za> References: <199506241552.RAA03235@grumble.grondar.za> Sender: current-owner@freebsd.org Precedence: bulk < said: > 2) (Little discussion here) eay's Secure Sockets Library (SSL) to be > imported in a similar way to above. (This is how secure telnet, FTP > etc will work). I very much dislike this idea. The situation with secure Internet apps is still far too much in flux for any one solution to be adopted in the source tree; there's a good chance that it will be necessary to rip it out later. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Sun Jun 25 12:46:33 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA04763 for current-outgoing; Sun, 25 Jun 1995 12:46:33 -0700 Received: (from phk@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA04752 ; Sun, 25 Jun 1995 12:46:31 -0700 From: Poul-Henning Kamp Message-Id: <199506251946.MAA04752@freefall.cdrom.com> Subject: Re: Crypt code summary(2). To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Sun, 25 Jun 1995 12:46:31 -0700 (PDT) Cc: mark@grondar.za, rgrimes@gndrsh.aac.dev.com, paul@freebsd.org, current@freebsd.org, csgr@freebsd.org, Wollman@halloran-eldar.lcs.mit.edu, jkh@freefall.cdrom.com, gibbs@freefall.cdrom.com In-Reply-To: <9506251944.AA17255@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Jun 25, 95 03:44:05 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 817 Sender: current-owner@freebsd.org Precedence: bulk > < said: > > > 2) (Little discussion here) eay's Secure Sockets Library (SSL) to be > > imported in a similar way to above. (This is how secure telnet, FTP > > etc will work). > > I very much dislike this idea. The situation with secure Internet > apps is still far too much in flux for any one solution to be adopted > in the source tree; there's a good chance that it will be necessary to > rip it out later. Since when have we stopped taking emerging technologies in ? -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Just that: dried leaves in boiling water ? From owner-freebsd-current Sun Jun 25 13:04:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA05565 for current-outgoing; Sun, 25 Jun 1995 13:04:15 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA05549 ; Sun, 25 Jun 1995 13:03:42 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.11/8.6.9) with ESMTP id WAA02091; Sun, 25 Jun 1995 22:03:25 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.11/8.6.9) with SMTP id WAA08724; Sun, 25 Jun 1995 22:03:22 +0200 Message-Id: <199506252003.WAA08724@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: Poul-Henning Kamp cc: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman), mark@grondar.za, rgrimes@gndrsh.aac.dev.com, paul@freebsd.org, current@freebsd.org, csgr@freebsd.org, jkh@freefall.cdrom.com, gibbs@freefall.cdrom.com Subject: Re: Crypt code summary(2). Date: Sun, 25 Jun 1995 22:03:21 +0200 From: Mark Murray Sender: current-owner@freebsd.org Precedence: bulk > > < said: > > > > > 2) (Little discussion here) eay's Secure Sockets Library (SSL) to be > > > imported in a similar way to above. (This is how secure telnet, FTP > > > etc will work). > > > > I very much dislike this idea. The situation with secure Internet > > apps is still far too much in flux for any one solution to be adopted > > in the source tree; there's a good chance that it will be necessary to > > rip it out later. > > Since when have we stopped taking emerging technologies in ? You guys want to hear something frightening? Eric Young (the `eay' in SSLeay) has a friend who will make SATAN look stupid. He has, and is going to release code that will snoop passwords out of new telnet and FTP sessions. The purpose is to force the use of this (or any equivalent technology). _They_ would prefer this to be SSLeay. Well? Are we going to have something we can unleash in retaliation? Given SSLeay's licence "free for non-commercial _and_ commercial use as as long as attribution is given", I reckon we would be very foolish not to. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Sun Jun 25 13:19:18 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA05957 for current-outgoing; Sun, 25 Jun 1995 13:19:18 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA05949 for ; Sun, 25 Jun 1995 13:19:14 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA17301; Sun, 25 Jun 1995 16:18:54 -0400 Date: Sun, 25 Jun 1995 16:18:54 -0400 From: Garrett Wollman Message-Id: <9506252018.AA17301@halloran-eldar.lcs.mit.edu> To: Mark Murray Cc: current@freebsd.org Subject: Re: Crypt code summary(2). In-Reply-To: <199506252003.WAA08724@grumble.grondar.za> References: <199506252003.WAA08724@grumble.grondar.za> Sender: current-owner@freebsd.org Precedence: bulk < said: > You guys want to hear something frightening? Eric Young (the `eay' in > SSLeay) has a friend who will make SATAN look stupid. He has, and is > going to release code that will snoop passwords out of new telnet and > FTP sessions. Lots of people have such programs. There are probably several dozen running on various insecure machines throughout MITnet right now. The usual answer is Kerberized rlogin/telnet or S/Key; in our group we use both (and I've been tasked to find or create a working S/Key implementation for our Alphas under four different versions of OSF/1). > The purpose is to force the use of this (or any > equivalent technology). _They_ would prefer this to be SSLeay. /I/ would prefer it to be the Internet Authentication and Encapsulating Security payloads myself. If I ever have free time again I may write support myself (although I'd prefer to have somebody else's code). > Well? Are we going to have something we can unleash in retaliation? > Given SSLeay's licence "free for non-commercial _and_ commercial use as > as long as attribution is given", I reckon we would be very foolish not > to. It seems like a fine application of the `ports' facility. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Sun Jun 25 13:24:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA06091 for current-outgoing; Sun, 25 Jun 1995 13:24:12 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA06085 for ; Sun, 25 Jun 1995 13:24:10 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA17317; Sun, 25 Jun 1995 16:23:55 -0400 Date: Sun, 25 Jun 1995 16:23:55 -0400 From: Garrett Wollman Message-Id: <9506252023.AA17317@halloran-eldar.lcs.mit.edu> To: Bruce Evans Cc: bde@freefall.cdrom.com, pete@puffin.pelican.com, current@freebsd.org Subject: Re: cvs commit: src/sys/i386/isa sio.c In-Reply-To: <199506251918.FAA05169@godzilla.zeta.org.au> References: <199506251918.FAA05169@godzilla.zeta.org.au> Sender: current-owner@freebsd.org Precedence: bulk < said: > I've been complaining about this for a year or two. I think it is because > tcp/ip wasn't designed for bidirectional interface. My standard benchmark > is: This is simply not true. > This takes about twice as long as would separate rcp's because acks get > queued behind large amounts of data and arrive too late to keep the data > streaming. This is because you don't have priority queueing for TCP ack packets. You probably will before the end of the year. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Sun Jun 25 13:58:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA06899 for current-outgoing; Sun, 25 Jun 1995 13:58:57 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA06892 for ; Sun, 25 Jun 1995 13:58:39 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.11/8.6.9) with ESMTP id WAA02141; Sun, 25 Jun 1995 22:58:23 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.11/8.6.9) with SMTP id WAA08903; Sun, 25 Jun 1995 22:58:22 +0200 Message-Id: <199506252058.WAA08903@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: Garrett Wollman cc: Mark Murray , current@freebsd.org Subject: Re: Crypt code summary(2). Date: Sun, 25 Jun 1995 22:58:21 +0200 From: Mark Murray Sender: current-owner@freebsd.org Precedence: bulk > < said: > > > You guys want to hear something frightening? Eric Young (the `eay' in > > SSLeay) has a friend who will make SATAN look stupid. He has, and is > > going to release code that will snoop passwords out of new telnet and > > FTP sessions. > > Lots of people have such programs. There are probably several dozen > running on various insecure machines throughout MITnet right now. The > usual answer is Kerberized rlogin/telnet or S/Key; in our group we use > both (and I've been tasked to find or create a working S/Key > implementation for our Alphas under four different versions of OSF/1). Ok - these have not been released on comp.sources.misc. This piece of code I mentioned will be. Once every cracker in the world has it who knows what else will happen? > > The purpose is to force the use of this (or any > > equivalent technology). _They_ would prefer this to be SSLeay. > > /I/ would prefer it to be the Internet Authentication and > Encapsulating Security payloads myself. If I ever have free time > again I may write support myself (although I'd prefer to have somebody > else's code). Right - so there is a recognition that something is needed. The discussion now goes to `what?' I personally have not heard of the code you mention. Is it available overseas? Is it well publicised and documented? Is it well used? (These aren't meant to be jabs - I am genuinely just digging for info here) With this code we have it right now, and I have the time and inclination to port it. > It seems like a fine application of the `ports' facility. That certainly is a possibility. It is not _my_ #1 choice, though. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Sun Jun 25 14:00:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA07002 for current-outgoing; Sun, 25 Jun 1995 14:00:37 -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 OAA06996 ; Sun, 25 Jun 1995 14:00:25 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id GAA06791; Mon, 26 Jun 1995 06:56:52 +1000 Date: Mon, 26 Jun 1995 06:56:52 +1000 From: Bruce Evans Message-Id: <199506252056.GAA06791@godzilla.zeta.org.au> To: bde@zeta.org.au, phk@freefall.cdrom.com Subject: Re: cvs commit: src/sys/i386/isa sio.c Cc: bde@freefall.cdrom.com, current@freebsd.org, pete@puffin.pelican.com Sender: current-owner@freebsd.org Precedence: bulk [for slip (and ppp)] >> time rcp machine1:/kernel machine2:/tmp/kernel & \ >> time rcp machine2:/kernel machine1:/tmp/kernel & >> >> This takes about twice as long as would separate rcp's because acks get >> queued behind large amounts of data and arrive too late to keep the data >> streaming. >Have you tried making your tcp-windows bigger ? I tried a smaller tcp_sendspace/tcp_recvspace but that made the problem worse. The slowdown is (now) not nearly a factor of 2. It is from 95 seconds for rcp'ing in one direction only to 125 and 125-136 seconds (the slowdown is sometimes asymmetrical). With a tcp_sendspace/tcp_recspace of 32K instead of 16K, the slowdown is less (to 110 and 128 seconds). With large windows, transmission works OK for a while, then both sides sometimes stop sending for a second or two, then each side takes turns transmitting, then transmission works OK... With small windows, this cycle repeats more often. The problem is more obvious at lower line speeds. Bruce From owner-freebsd-current Sun Jun 25 14:08:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA07463 for current-outgoing; Sun, 25 Jun 1995 14:08:58 -0700 Received: (from phk@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA07454 ; Sun, 25 Jun 1995 14:08:56 -0700 From: Poul-Henning Kamp Message-Id: <199506252108.OAA07454@freefall.cdrom.com> Subject: Re: Crypt code summary(2). To: mark@grondar.za (Mark Murray) Date: Sun, 25 Jun 1995 14:08:55 -0700 (PDT) Cc: wollman@halloran-eldar.lcs.mit.edu, mark@grondar.za, current@freebsd.org In-Reply-To: <199506252058.WAA08903@grumble.grondar.za> from "Mark Murray" at Jun 25, 95 10:58:21 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 468 Sender: current-owner@freebsd.org Precedence: bulk > > It seems like a fine application of the `ports' facility. > > That certainly is a possibility. It is not _my_ #1 choice, though. I going to counter Garrett, and say: Put it in the main branch. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Just that: dried leaves in boiling water ? From owner-freebsd-current Sun Jun 25 14:15:42 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA07809 for current-outgoing; Sun, 25 Jun 1995 14:15:42 -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 OAA07803 ; Sun, 25 Jun 1995 14:15:33 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id HAA07096; Mon, 26 Jun 1995 07:14:27 +1000 Date: Mon, 26 Jun 1995 07:14:27 +1000 From: Bruce Evans Message-Id: <199506252114.HAA07096@godzilla.zeta.org.au> To: bde@zeta.org.au, wollman@halloran-eldar.lcs.mit.edu Subject: Re: cvs commit: src/sys/i386/isa sio.c Cc: bde@freefall.cdrom.com, current@freebsd.org, pete@puffin.pelican.com Sender: current-owner@freebsd.org Precedence: bulk >> I've been complaining about this for a year or two. I think it is because >> tcp/ip wasn't designed for bidirectional interface. My standard benchmark >> is: >This is simply not true. >> This takes about twice as long as would separate rcp's because acks get >> queued behind large amounts of data and arrive too late to keep the data >> streaming. >This is because you don't have priority queueing for TCP ack packets. >You probably will before the end of the year. Why didn't we have designed-in things yesterday? Bruce From owner-freebsd-current Sun Jun 25 14:52:38 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA08798 for current-outgoing; Sun, 25 Jun 1995 14:52:38 -0700 Received: from bigdipper.iagi.net (bigdipper.iagi.net [198.6.14.10]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA08792 for ; Sun, 25 Jun 1995 14:52:37 -0700 Received: (from adhir@localhost) by bigdipper.iagi.net (8.6.11/8.6.9) id RAA00607; Sun, 25 Jun 1995 17:52:45 -0400 Date: Sun, 25 Jun 1995 17:52:45 -0400 (EDT) From: "Alok K. Dhir" To: current@freebsd.org Subject: -stable sup tree? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk Hey all - I was wondering if there was any new info on the -stable sup target? Has this been implemented yet, and if so, where, so that I may begin SUPping it... Thanks. Alok K. Dhir Internet Access Group, Inc. adhir@iagi.net (301) 652-0484 Fax: (301) 652-0649 http://www.iagi.net From owner-freebsd-current Sun Jun 25 14:56:50 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA09099 for current-outgoing; Sun, 25 Jun 1995 14:56:50 -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 OAA09075 for ; Sun, 25 Jun 1995 14:56:43 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA26935; Sun, 25 Jun 1995 23:56:21 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA04836; Sun, 25 Jun 1995 23:56:10 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id UAA18975; Sun, 25 Jun 1995 20:24:19 +0200 From: J Wunsch Message-Id: <199506251824.UAA18975@uriah.heep.sax.de> Subject: Re: no bell under Xinside server To: bde@zeta.org.au (Bruce Evans) Date: Sun, 25 Jun 1995 20:24:18 +0200 (MET DST) Cc: current@freebsd.org, gena@NetVision.net.il In-Reply-To: <199506251810.EAA04120@godzilla.zeta.org.au> from "Bruce Evans" at Jun 26, 95 04:10:52 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: 1013 Sender: current-owner@freebsd.org Precedence: bulk As Bruce Evans wrote: > > It went away in revision 1.88 1995/01/12 and I think it was broken in > syscons before that, so nothing should have been using it. > > >+ #define CONS_XBELL _IOW('t', 123, int[2]) > > Its name was CONSOLE_X_BELL in syscons and it still has that name in pcvt. Bing! Rings a bell in me. No longer supported by newer pcvt's either. It's old compatibility cruft from pccons, and pcvt used to implement the old pccons model for X11 support in order to ease the transition. We've recently decided that it will no longer be #ifdef'ed in by default for the next pcvt release (which is to be out RSN). You should advise Xinside to use #define KDMKTONE _IO('K', 8 /*, int */) instead. It's supported by both, syscons and pcvt. It's the SVRx compatible command, so they should have the code already handy for its implementation. -- 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 Jun 25 14:58:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA09250 for current-outgoing; Sun, 25 Jun 1995 14:58:55 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA09244 for ; Sun, 25 Jun 1995 14:58:52 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA11996; Sun, 25 Jun 95 15:51:52 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506252151.AA11996@cs.weber.edu> Subject: Re: no bell under Xinside server To: gena@NetVision.net.il (Gennady Sorokopud) Date: Sun, 25 Jun 95 15:51:52 MDT Cc: current@FreeBSD.org, gena@NetVision.net.il In-Reply-To: from "Gennady Sorokopud" at Jun 25, 95 12:20:27 pm X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@FreeBSD.org Precedence: bulk > I noticed that if i'm running Xinside X-server speaker bell does not > work. > > (But it works perfectly with pcvt console driver) > > After some investigation i find out that ioctl that is responsible > for "beeping" under X is missing in syscons.c . Isn't the ioctl to set duration and frequency also missing? Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun Jun 25 15:20:22 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA10137 for current-outgoing; Sun, 25 Jun 1995 15:20:22 -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 PAA10130 for ; Sun, 25 Jun 1995 15:20:17 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id IAA08228; Mon, 26 Jun 1995 08:16:30 +1000 Date: Mon, 26 Jun 1995 08:16:30 +1000 From: Bruce Evans Message-Id: <199506252216.IAA08228@godzilla.zeta.org.au> To: peter@haywire.dialix.com Subject: Re: i386/563: isa conflict detection cannot handle ioaddr 0x0 Cc: current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk >The conflict detection code does not allow for the possibility that >a device does not have an IO address. 0 is a valid io address. I think the bug is actually that config generates address 0 instead of an out of bounds address for devices that don't have an io address. The out of bounds address should probably be -2. -1 is used for address `?'. However, Config fails to distinguish between `?' and `none' for other items, and isa.c only knows that -1 is special, so the out of bounds address should be -1 for now. Bruce From owner-freebsd-current Sun Jun 25 15:25:42 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA10330 for current-outgoing; Sun, 25 Jun 1995 15:25:42 -0700 Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA10323 for ; Sun, 25 Jun 1995 15:25:35 -0700 Received: by sequent.kiae.su id AA25456 (5.65.kiae-2 ); Mon, 26 Jun 1995 02:06:09 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Mon, 26 Jun 95 02:06:09 +0400 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id CAA00452; Mon, 26 Jun 1995 02:02:35 +0400 To: Mark Murray , Garrett Wollman Cc: current@freebsd.org References: <199506252003.WAA08724@grumble.grondar.za> <9506252018.AA17301@halloran-eldar.lcs.mit.edu> In-Reply-To: <9506252018.AA17301@halloran-eldar.lcs.mit.edu>; from Garrett Wollman at Sun, 25 Jun 1995 16:18:54 -0400 Message-Id: Organization: Olahm Ha-Yetzirah Date: Mon, 26 Jun 1995 02:02:34 +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: Re: Crypt code summary(2). Lines: 17 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 744 Sender: current-owner@freebsd.org Precedence: bulk In message <9506252018.AA17301@halloran-eldar.lcs.mit.edu> Garrett Wollman writes: >/I/ would prefer it to be the Internet Authentication and >Encapsulating Security payloads myself. If I ever have free time >again I may write support myself (although I'd prefer to have somebody >else's code). Internet Auth. require MD5 which implementation in software slow down IP approx. in two times, see latest IETF materials. SSL is speed winner here. -- 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 Sun Jun 25 15:26:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA10420 for current-outgoing; Sun, 25 Jun 1995 15:26:28 -0700 Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA10414 ; Sun, 25 Jun 1995 15:26:24 -0700 Received: by sequent.kiae.su id AA24686 (5.65.kiae-2 ); Mon, 26 Jun 1995 02:01:09 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Mon, 26 Jun 95 02:01:08 +0400 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id CAA00413; Mon, 26 Jun 1995 02:00:14 +0400 To: Mark Murray , Poul-Henning Kamp Cc: csgr@freebsd.org, current@freebsd.org, gibbs@freefall.cdrom.com, jkh@freefall.cdrom.com, paul@freebsd.org, rgrimes@gndrsh.aac.dev.com, Garrett Wollman References: <199506252003.WAA08724@grumble.grondar.za> In-Reply-To: <199506252003.WAA08724@grumble.grondar.za>; from Mark Murray at Sun, 25 Jun 1995 22:03:21 +0200 Message-Id: Organization: Olahm Ha-Yetzirah Date: Mon, 26 Jun 1995 02:00:13 +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: Re: Crypt code summary(2). Lines: 23 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 1097 Sender: current-owner@freebsd.org Precedence: bulk In message <199506252003.WAA08724@grumble.grondar.za> Mark Murray writes: >You guys want to hear something frightening? Eric Young (the `eay' in >SSLeay) has a friend who will make SATAN look stupid. He has, and is >going to release code that will snoop passwords out of new telnet and >FTP sessions. The purpose is to force the use of this (or any >equivalent technology). _They_ would prefer this to be SSLeay. It isn't surprise, such code exists long time, if you have root on any machine in the local ethernet f.e, you can set card to promisc. mode and grab all traffic that goes through your local net, including ftp/telnet passwords. In more intelligent way you can use BPF filtering for it as tcpdump does. Then small artifical intelligense to recognize passwords through incoming data... -- 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 Sun Jun 25 15:58:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA11467 for current-outgoing; Sun, 25 Jun 1995 15:58:15 -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 PAA11458 for ; Sun, 25 Jun 1995 15:58:13 -0700 Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id PAA02962; Sun, 25 Jun 1995 15:58:10 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id PAA00581; Sun, 25 Jun 1995 15:58:36 -0700 Message-Id: <199506252258.PAA00581@corbin.Root.COM> To: Garrett Wollman cc: current@freebsd.org Subject: Re: cvs commit: src/sys/i386/isa sio.c In-reply-to: Your message of "Sun, 25 Jun 95 16:23:55 EDT." <9506252023.AA17317@halloran-eldar.lcs.mit.edu> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 25 Jun 1995 15:58:35 -0700 Sender: current-owner@freebsd.org Precedence: bulk >> This takes about twice as long as would separate rcp's because acks get >> queued behind large amounts of data and arrive too late to keep the data >> streaming. > >This is because you don't have priority queueing for TCP ack packets. >You probably will before the end of the year. I'm not sure this going help a lot - most of the data gets buffered in the modem and priority queing for ACKs isn't going to help this. -DG From owner-freebsd-current Sun Jun 25 16:12:20 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA11901 for current-outgoing; Sun, 25 Jun 1995 16:12:20 -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 QAA11894 for ; Sun, 25 Jun 1995 16:12:16 -0700 Received: (from peter@localhost) by haywire.DIALix.COM (8.6.12/8.6.12/DIALix) id HAA24996; Mon, 26 Jun 1995 07:11:42 +0800 Date: Mon, 26 Jun 1995 07:11:40 +0800 (WST) From: Peter Wemm To: Bruce Evans cc: current@freebsd.org Subject: Re: i386/563: isa conflict detection cannot handle ioaddr 0x0 In-Reply-To: <199506252216.IAA08228@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk On Mon, 26 Jun 1995, Bruce Evans wrote: > > >The conflict detection code does not allow for the possibility that > >a device does not have an IO address. > > 0 is a valid io address. I think the bug is actually that config > generates address 0 instead of an out of bounds address for devices that > don't have an io address. The out of bounds address should probably be > -2. -1 is used for address `?'. However, Config fails to distinguish > between `?' and `none' for other items, and isa.c only knows that -1 is > special, so the out of bounds address should be -1 for now. > > Bruce But isn't the DMA1 controller at IO address 0x0 -> 0x1F? IMHO, that makes it just about as invalid a choice for an expansion card as one can get.. :-) Hmm. There appears to be a sort-of convention with the existing code.. if you dont specify a maddr, config sets it to zero. isa.c knows that "maddr 0" is disabled. Same goes for the irq - it appears to be set to 0 if it's not specified in the config line, and the isa code disables conflict testing. As far as I can see, there _is_ an IRQ0 in the system (at least there are vectors in isa.c), but I think it's permanently wired to a timer or something. On the other hand, drq appears to be -1 for being "not specified", to blow away my argument above. :-) My preference would be that "port ?" is different to "" (none). Indeed, I have a use for this in the slxos driver - I need a way to specify to either use a configured irq (ie: "irq 14"), or to probe for settings or use the first available (ie: "irq ?"), or to run in polled mode with no irq handlers (ie: "" (no setting)). For now, I'd plead for making the io port conflict detection consistant with the memory address conflict detection.. ie: "0" == no setting. It'll at least make the current code that's "out there" work. If somebody wants to go through and sort out "config" and isa.c and the drivers to use -2 as "no setting", that would be a "Good Thing". IMHO, making " ?" == "" is a step in the wrong direction as it is a slight loss of existing (albeit inconsistant) functionality. Cheers, -Peter From owner-freebsd-current Sun Jun 25 17:11:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA13415 for current-outgoing; Sun, 25 Jun 1995 17:11:02 -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 RAA13408 for ; Sun, 25 Jun 1995 17:10:50 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id KAA10740; Mon, 26 Jun 1995 10:09:35 +1000 Date: Mon, 26 Jun 1995 10:09:35 +1000 From: Bruce Evans Message-Id: <199506260009.KAA10740@godzilla.zeta.org.au> To: bde@zeta.org.au, peter@haywire.DIALix.COM Subject: Re: i386/563: isa conflict detection cannot handle ioaddr 0x0 Cc: current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk >> 0 is a valid io address. I think the bug is actually that config >> generates address 0 instead of an out of bounds address for devices that >> don't have an io address. The out of bounds address should probably be >But isn't the DMA1 controller at IO address 0x0 -> 0x1F? IMHO, that >makes it just about as invalid a choice for an expansion card as one can >get.. :-) The DMA registers should be in a device or something so that they get conflict-checked. Anyway, config is supposed to somewhat machine-independent and shouldn't presume anything about the address space. I think 0 is considered free mainly because it is a null pointer constant. config should also presume less about the representation of addresses. It stores memory addresses in an int and port addresses in a (char *). Addresses should be represented by u_long's or u_quad_t's. >Hmm. There appears to be a sort-of convention with the existing code.. >if you dont specify a maddr, config sets it to zero. isa.c knows that >"maddr 0" is disabled. Yes. I guess the no-maddr case got fixed because it is very common. >Same goes for the irq - it appears to be set to 0 if it's not specified >in the config line, and the isa code disables conflict testing. As far >as I can see, there _is_ an IRQ0 in the system (at least there are >vectors in isa.c), but I think it's permanently wired to a timer or >something. IRQn is actually (1 << n) so 0 is special. This is another thing that is done wrong. IRQn should be n and irq numbers -1 and -2 special. I think this is fixed in NetBSD. >On the other hand, drq appears to be -1 for being "not specified", to blow >away my argument above. :-) DRQn is n so there is no alternative to -1 being special. >My preference would be that "port ?" is different to "" (none). Indeed, Yes, that's what the -1 and -2 are for. Config, isa.c and drivers would have to be more careful about sign extension if they used u_longs like I said to above. Someone once made id_iobase a u_short and broke the `id_iobase < 0' test in lpt.c. >For now, I'd plead for making the io port conflict detection consistant >with the memory address conflict detection.. ie: "0" == no setting. >It'll at least make the current code that's "out there" work. OK. Bruce From owner-freebsd-current Sun Jun 25 21:25:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA22560 for current-outgoing; Sun, 25 Jun 1995 21:25:36 -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 VAA22552 for ; Sun, 25 Jun 1995 21:25:32 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA14513; Mon, 26 Jun 1995 06:25:07 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id GAA07646; Mon, 26 Jun 1995 06:24:58 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id AAA20224; Mon, 26 Jun 1995 00:56:20 +0200 From: J Wunsch Message-Id: <199506252256.AAA20224@uriah.heep.sax.de> Subject: Re: no bell under Xinside server To: terry@cs.weber.edu (Terry Lambert) Date: Mon, 26 Jun 1995 00:56:20 +0200 (MET DST) Cc: gena@NetVision.net.il, current@FreeBSD.org In-Reply-To: <9506252151.AA11996@cs.weber.edu> from "Terry Lambert" at Jun 25, 95 03:51:52 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: 985 Sender: current-owner@FreeBSD.org Precedence: bulk As Terry Lambert wrote: > > > I noticed that if i'm running Xinside X-server speaker bell does not > > work. > Isn't the ioctl to set duration and frequency also missing? It is there, but Xinside is using an obsoleted interface. This is the pcvt part, the syscons implementation is rather similiar. The interface itself is featured after SysV, hence the semantics are somewhat awful: case KDMKTONE: /* ring the speaker */ if(data) { int duration = *(int *)data >> 16; int pitch = *(int *)data & 0xffff; sysbeep(pitch, duration * hz / 3000); } else { sysbeep(PCVT_SYSBEEPF / 1493, hz / 4); } return 0; -- 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 Jun 25 23:12:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA27056 for current-outgoing; Sun, 25 Jun 1995 23:12:34 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA27005 ; Sun, 25 Jun 1995 23:12:05 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.11/8.6.9) with ESMTP id IAA02748; Mon, 26 Jun 1995 08:10:34 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.11/8.6.9) with SMTP id IAA11689; Mon, 26 Jun 1995 08:10:33 +0200 Message-Id: <199506260610.IAA11689@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: ache@astral.msk.su cc: Mark Murray , Poul-Henning Kamp , csgr@freebsd.org, current@freebsd.org, gibbs@freefall.cdrom.com, jkh@freefall.cdrom.com, paul@freebsd.org, rgrimes@gndrsh.aac.dev.com, Garrett Wollman Subject: Re: Crypt code summary(2). Date: Mon, 26 Jun 1995 08:10:32 +0200 From: Mark Murray Sender: current-owner@freebsd.org Precedence: bulk > >You guys want to hear something frightening? Eric Young (the `eay' in > >SSLeay) has a friend who will make SATAN look stupid. He has, and is > >going to release code that will snoop passwords out of new telnet and > >FTP sessions. The purpose is to force the use of this (or any > >equivalent technology). _They_ would prefer this to be SSLeay. > > It isn't surprise, such code exists long time, if you have > root on any machine in the local ethernet f.e, you can > set card to promisc. mode and grab all traffic that goes through > your local net, including ftp/telnet passwords. In more > intelligent way you can use BPF filtering for it as tcpdump > does. Then small artifical intelligense to recognize > passwords through incoming data... Sure. The concept has been around for a while. The point here is now this code is going to be unleashed, and every twit-not-programmer will have the tools to snoop with his FreeBSD/NetBSD/Linux box. Just like Crack - very few dictionary attacks actually happened until this one came around. Now most wise fols are running some form of shadow password. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Sun Jun 25 23:57:07 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA28645 for current-outgoing; Sun, 25 Jun 1995 23:57:07 -0700 Received: from dns.netvision.net.il (root@dns.NetVision.net.il [194.90.1.5]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA28639 for ; Sun, 25 Jun 1995 23:57:04 -0700 Received: from Burka.NetVision.net.il (root@Burka.NetVision.net.il [194.90.6.15]) by dns.netvision.net.il (8.6.12/8.6.9) with ESMTP id JAA28346; Mon, 26 Jun 1995 09:57:32 +0300 Received: from gena@NetVision.net.il (Burka.NetVision.net.il [194.90.6.15]) by Burka.NetVision.net.il (8.6.11/8.6.6) with SMTP id KAA03978; Mon, 26 Jun 1995 10:10:18 +0300 Date: Mon, 26 Jun 1995 10:10:18 +0300 In-Reply-To: <199506251824.UAA18975@uriah.heep.sax.de> Message-ID: X-Face: #v>4HN>#D_"[olq9y`HqTYkLVB89Xy|3')Vs9v58JQ*u-xEJVKY`xa.}E?z0RkLI/P&;BJmi0#u=W0).-Y'J4(dw{"54NhSG|YYZG@[)(`e! >jN#L!~qI5fE-JHS+< Organization: NetVision ltd. X-Mailer: XFMail 0.2-Beta on FreeBSD From: Gennady Sorokopud To: Joerg Wunsch , J Wunsch Subject: Re: no bell under Xinside server Cc: Bruce Evans , , Sender: current-owner@freebsd.org Precedence: bulk Hello! So what do you suggest to folks that still wants to use Xinside with syscons? Advising things to Xinside folks sounds nice but...:-) In message <199506251824.UAA18975@uriah.heep.sax.de> J Wunsch writes: >As Bruce Evans wrote: >> >> It went away in revision 1.88 1995/01/12 and I think it was broken in >> syscons before that, so nothing should have been using it. >> >> >+ #define CONS_XBELL _IOW('t', 123, int[2]) >> >> Its name was CONSOLE_X_BELL in syscons and it still has that name in pcvt. > >Bing! Rings a bell in me. > >No longer supported by newer pcvt's either. It's old compatibility >cruft from pccons, and pcvt used to implement the old pccons model for >X11 support in order to ease the transition. We've recently decided >that it will no longer be #ifdef'ed in by default for the next pcvt >release (which is to be out RSN). > >You should advise Xinside to use > >#define KDMKTONE _IO('K', 8 /*, int */) > >instead. It's supported by both, syscons and pcvt. It's the SVRx >compatible command, so they should have the code already handy for its >implementation. > >-- >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. ;-) -------- Gennady B. Sorokopud - System programmer at NetVision Israel. E-Mail: gena@NetVision.net.il Homepage: http://www.netvision.net.il/~gena This message was sent at 06/26/95 10:08:04 by XF-Mail From owner-freebsd-current Mon Jun 26 00:03:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA29006 for current-outgoing; Mon, 26 Jun 1995 00:03: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 AAA28946 for ; Mon, 26 Jun 1995 00:03:14 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA19060; Mon, 26 Jun 1995 09:03:09 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA08436; Mon, 26 Jun 1995 09:03:08 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id IAA22082; Mon, 26 Jun 1995 08:44:57 +0200 From: J Wunsch Message-Id: <199506260644.IAA22082@uriah.heep.sax.de> Subject: Re: i386/563: isa conflict detection cannot handle ioaddr 0x0 To: bde@zeta.org.au (Bruce Evans) Date: Mon, 26 Jun 1995 08:44:56 +0200 (MET DST) Cc: bde@zeta.org.au, peter@haywire.DIALix.COM, current@freebsd.org In-Reply-To: <199506260009.KAA10740@godzilla.zeta.org.au> from "Bruce Evans" at Jun 26, 95 10:09:35 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: 381 Sender: current-owner@freebsd.org Precedence: bulk As Bruce Evans wrote: > > The DMA registers should be in a device or something so that they get > conflict-checked. Same holds for `rtc0'. It's even using an IRQ, but doesn't appear anywhere in the config file, not even as a comment. -- 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 Jun 26 00:03:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA29008 for current-outgoing; Mon, 26 Jun 1995 00:03:26 -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 AAA28956 for ; Mon, 26 Jun 1995 00:03:16 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA19066; Mon, 26 Jun 1995 09:03:11 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA08442 for freebsd-current@FreeBSD.org; Mon, 26 Jun 1995 09:03:10 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id IAA22112 for freebsd-current@FreeBSD.org; Mon, 26 Jun 1995 08:48:59 +0200 From: J Wunsch Message-Id: <199506260648.IAA22112@uriah.heep.sax.de> Subject: Re: kern/562: netscape (bsdi executable) can't do a uname (fix provided) To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 26 Jun 1995 08:48:59 +0200 (MET DST) Reply-To: freebsd-current@FreeBSD.org (FreeBSD-current users) In-Reply-To: <199506251830.LAA00912@freefall.cdrom.com> from "peter@haywire.dialix.com" at Jun 25, 95 11:30:01 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: 5698 Sender: current-owner@FreeBSD.org Precedence: bulk Can any brave soul who's actually got Netscape 1.1 try this? As peter@haywire.dialix.com wrote: > > > >Number: 562 > >Category: kern > >Synopsis: netscape (bsdi executable) can't do a uname (fix provided) > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-bugs (FreeBSD bugs mailing list) > >State: open > >Class: change-request > >Submitter-Id: current-users > >Arrival-Date: Sun Jun 25 11:30:00 1995 > >Originator: Peter Wemm > >Organization: > DIALix Services > >Release: FreeBSD 2.0-BUILT-19950625 i386 > >Environment: > > FreeBSD-current > FreeBSD jhome.DIALix.COM 2.0-BUILT-19950625 FreeBSD 2.0-BUILT-19950625 #4: Sun Jun 25 22:05:25 WST 1995 pwroot@jhome.DIALix.COM:/usr/src/sys/compile/JHOME i386 > > >Description: > > Netscape 1.1N does a uname() at startup to discover the Host OS type. > This information is presented to every server that it connects to, and > is probably logged for statistics, at least on home.netscape.com. > > The problem is, that it identifies itself as (while running on FreeBSD) as > something like this: > > GET / HTTP/1.0 > User-Agent: Mozilla/1.1N (X11; I; BSD/386 uname failed) > Accept: */* > Accept: image/gif > Accept: image/x-xbitmap > Accept: image/jpeg > > This does not do much to help convince Netscape to support FreeBSD in the > future.... :-) > > After applying this patch, it identifies itself like this: (Thanks to > Gary Palmer for the idea on how to see this info) > > GET / HTTP/1.0 > User-Agent: Mozilla/1.1N (X11; I; FreeBSD 2.0-BUILT-1995060 i386) > Accept: */* > Accept: image/gif > Accept: image/x-xbitmap > Accept: image/jpeg > > (BTW: FreeBSD-current is still "2.0-built-nnnnn"????) > > Also, when starting up netscape, there is a very annoying printf > "uname() failed; can't tell what system we're running on" > > >How-To-Repeat: > > Run netscape... > > >Fix: > > Apply this patch to /usr/src/sys/kern/kern_sysctl.c and make sure > COMPAT_43 is defined (netscape is a 4.3BSD-net2 binary, so it should > have COMPAT_43 defined anyway) > > Apologies for the ugly code here.. > > -Peter > > *** kern_sysctl-dist.c Tue May 30 18:58:22 1995 > --- kern_sysctl.c Mon Jun 26 02:01:21 1995 > *************** > *** 767,772 **** > --- 767,818 ---- > #define KINFO_LOADAVG (5<<8) > #define KINFO_CLOCKRATE (6<<8) > > + /* Non-standard BSDI extension - only present on their 4.3 net-2 releases */ > + #define KINFO_BSDI_SYSINFO (101<<8) > + > + /* > + * XXX this is bloat, but I hope it's better here than on the potentially > + * limited kernel stack... -Peter > + */ > + > + struct { > + char *bsdi_machine; /* "i386" on BSD/386 */ > + char *pad0; > + long pad1; > + long pad2; > + long pad3; > + u_long pad4; > + u_long pad5; > + u_long pad6; > + > + char *bsdi_ostype; /* "BSD/386" on BSD/386 */ > + char *bsdi_osrelease; /* "1.1" on BSD/386 */ > + long pad7; > + long pad8; > + char *pad9; > + > + long pad10; > + long pad11; > + int pad12; > + long pad13; > + quad_t pad14; > + long pad15; > + > + struct timeval pad16; > + /* we dont set this, because BSDI's uname used gethostname() instead */ > + char *bsdi_hostname; /* hostname on BSD/386 */ > + > + /* the actual string data is appended here */ > + > + } bsdi_si; > + /* > + * this data is appended to the end of the bsdi_si structure during copyout. > + * The "char *" offsets are relative to the base of the bsdi_si struct. > + * This contains "FreeBSD\02.0-BUILT-nnnnnn\0i386\0", and these strings > + * should not exceed the length of the buffer here... (or else!! :-) > + */ > + char bsdi_strings[80]; /* It had better be less than this! */ > + > struct getkerninfo_args { > int op; > char *where; > *************** > *** 829,834 **** > --- 875,937 ---- > name[0] = KERN_CLOCKRATE; > error = kern_sysctl(name, 1, uap->where, &size, NULL, 0, p); > break; > + > + case KINFO_BSDI_SYSINFO: { > + /* > + * this is pretty crude, but it's just enough for uname() > + * from BSDI's 1.x libc to work. > + */ > + > + u_int needed; > + u_int left; > + char *s; > + > + bzero((char *)&bsdi_si, sizeof(bsdi_si)); > + bzero(bsdi_strings, sizeof(bsdi_strings)); > + > + s = bsdi_strings; > + > + bsdi_si.bsdi_ostype = ((char *)(s - bsdi_strings)) + sizeof(bsdi_si); > + strcpy(s, ostype); > + s += strlen(s) + 1; > + > + bsdi_si.bsdi_osrelease = ((char *)(s - bsdi_strings)) + sizeof(bsdi_si); > + strcpy(s, osrelease); > + s += strlen(s) + 1; > + > + bsdi_si.bsdi_machine = ((char *)(s - bsdi_strings)) + sizeof(bsdi_si); > + strcpy(s, machine); > + s += strlen(s) + 1; > + > + needed = sizeof(bsdi_si) + (s - bsdi_strings); > + > + if (uap->where == NULL) { > + /* process is asking how much buffer to supply.. */ > + size = needed; > + error = 0; > + break; > + } > + > + /* if too much buffer supplied, trim it down */ > + if (size > needed) > + size = needed; > + > + /* how much of the buffer is remaining */ > + left = size; > + > + if ((error = copyout((char *)&bsdi_si, uap->where, left)) != 0) > + break; > + > + /* is there any point in continuing? */ > + if (left > sizeof(bsdi_si)) > + left -= sizeof(bsdi_si); > + else > + break; > + > + error = copyout(&bsdi_strings, uap->where + sizeof(bsdi_si), > + left); > + break; > + } > > default: > return (EOPNOTSUPP); > >Audit-Trail: > >Unformatted: > > > -- 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 Jun 26 00:31:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA00291 for current-outgoing; Mon, 26 Jun 1995 00:31:47 -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 AAA00276 for ; Mon, 26 Jun 1995 00:31:39 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA22962; Mon, 26 Jun 1995 17:28:19 +1000 Date: Mon, 26 Jun 1995 17:28:19 +1000 From: Bruce Evans Message-Id: <199506260728.RAA22962@godzilla.zeta.org.au> To: gena@NetVision.net.il, j@uriah.heep.sax.de, joerg_wunsch@uriah.heep.sax.de Subject: Re: no bell under Xinside server Cc: bde@zeta.org.au, current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk >So what do you suggest to folks that still wants to use Xinside >with syscons? >Advising things to Xinside folks sounds nice but...:-) We will probably have to restore the compatibility cruft for a few months (or years :-() until everything stops using it. Bruce From owner-freebsd-current Mon Jun 26 02:10:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA03294 for current-outgoing; Mon, 26 Jun 1995 02:10:01 -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 CAA03277 ; Mon, 26 Jun 1995 02:09:57 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id CAA03201; Mon, 26 Jun 1995 02:10:10 -0700 From: "Rodney W. Grimes" Message-Id: <199506260910.CAA03201@gndrsh.aac.dev.com> Subject: Re: Crypt code summary(2). To: phk@freefall.cdrom.com (Poul-Henning Kamp) Date: Mon, 26 Jun 1995 02:10:10 -0700 (PDT) Cc: mark@grondar.za, wollman@halloran-eldar.lcs.mit.edu, current@freebsd.org In-Reply-To: <199506252108.OAA07454@freefall.cdrom.com> from "Poul-Henning Kamp" at Jun 25, 95 02:08:55 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: 1358 Sender: current-owner@freebsd.org Precedence: bulk > > > > It seems like a fine application of the `ports' facility. > > > > That certainly is a possibility. It is not _my_ #1 choice, though. > > I going to counter Garrett, and say: Put it in the main branch. I am going to counter Poul, and agree with Garrett, and give reasons for doing so. a) It is very likely to change as RFC's get done to cover this and we will more or less be forced to rip out what ever we had done to implement what is in the RFCs. b) This is cryto code and may have legal ramifications that none of us have fully evaluated (and I wouldn't consider it fully evaluated until some one has consulted with the State Department and/or an attourny (didn't we have some one once offer us free or low cost legal counsel??). c) A port collection is lets us look at how this stuff all works and intergrates without mucking around with the main source tree. It gets the code to our user base just as well, and becomes totally optional. Please don't just say things like ``I am going to counter so and so'' with out giving a good reason for the counter, it is a waste of bandwidth and argument without meat does not stand well in a battle. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Mon Jun 26 02:20:42 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA03978 for current-outgoing; Mon, 26 Jun 1995 02:20:42 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA03940 ; Mon, 26 Jun 1995 02:20:28 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.11/8.6.9) with ESMTP id LAA02946; Mon, 26 Jun 1995 11:20:12 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.11/8.6.9) with SMTP id LAA12300; Mon, 26 Jun 1995 11:20:11 +0200 Message-Id: <199506260920.LAA12300@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: "Rodney W. Grimes" cc: phk@freefall.cdrom.com (Poul-Henning Kamp), mark@grondar.za, wollman@halloran-eldar.lcs.mit.edu, current@freebsd.org Subject: Re: Crypt code summary(2). Date: Mon, 26 Jun 1995 11:20:11 +0200 From: Mark Murray Sender: current-owner@freebsd.org Precedence: bulk > I am going to counter Poul, and agree with Garrett, and give reasons > for doing so. ...and I am going to debate this too! > a) It is very likely to change as RFC's get done to cover this and > we will more or less be forced to rip out what ever we had done > to implement what is in the RFCs. The SSLeay code is already covered by RFC's. See rfc1421, rfc1422, rfc1423 and rfc1424. > b) This is cryto code and may have legal ramifications that none of > us have fully evaluated (and I wouldn't consider it fully evaluated > until some one has consulted with the State Department and/or an > attourny (didn't we have some one once offer us free or low cost > legal counsel??). Do US embassies have PR State Department folks I could ask? M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Mon Jun 26 02:40:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA04936 for current-outgoing; Mon, 26 Jun 1995 02:40:47 -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 CAA04923 for ; Mon, 26 Jun 1995 02:40:43 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id CAA03287; Mon, 26 Jun 1995 02:40:48 -0700 From: "Rodney W. Grimes" Message-Id: <199506260940.CAA03287@gndrsh.aac.dev.com> Subject: Re: -stable sup tree? To: adhir@iagi.net (Alok K. Dhir) Date: Mon, 26 Jun 1995 02:40:48 -0700 (PDT) Cc: current@freebsd.org In-Reply-To: from "Alok K. Dhir" at Jun 25, 95 05:52:45 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: 805 Sender: current-owner@freebsd.org Precedence: bulk > > > Hey all - I was wondering if there was any new info on the -stable sup > target? Has this been implemented yet, and if so, where, so that I may > begin SUPping it... Sorry, due to my work load and recent move I have not been able to get to it. The tree is there, I just need to add a few dozen lines to a shell script and create the dozen or so sup targets, test it all out and let it loose, but that takes an hour or two of my time, and I have just not had one to spare on that lately :-(. > > Thanks. > > Alok K. Dhir > Internet Access Group, Inc. > adhir@iagi.net > (301) 652-0484 Fax: (301) 652-0649 > http://www.iagi.net > > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Mon Jun 26 03:45:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA07335 for current-outgoing; Mon, 26 Jun 1995 03:45: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 DAA07328 for ; Mon, 26 Jun 1995 03:45:11 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id DAA03691; Mon, 26 Jun 1995 03:44:46 -0700 From: "Rodney W. Grimes" Message-Id: <199506261044.DAA03691@gndrsh.aac.dev.com> Subject: Re: Crypt code summary(2). To: mark@grondar.za (Mark Murray) Date: Mon, 26 Jun 1995 03:44:46 -0700 (PDT) Cc: FreeBSD-current@FreeBSD.Org (FreeBSD current) In-Reply-To: <199506260920.LAA12300@grumble.grondar.za> from "Mark Murray" at Jun 26, 95 11:20:11 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: 1196 Sender: current-owner@FreeBSD.Org Precedence: bulk [CC: trimmed, it was getting rather long :-)] > > > I am going to counter Poul, and agree with Garrett, and give reasons > > for doing so. > > ...and I am going to debate this too! > > > a) It is very likely to change as RFC's get done to cover this and > > we will more or less be forced to rip out what ever we had done > > to implement what is in the RFCs. > > The SSLeay code is already covered by RFC's. See rfc1421, rfc1422, rfc1423 > and rfc1424. Oh, I did not realize that (gee, blush, time to go read the RFC index since the last time I looked it over for what was new the RFS's where only in the 1200's or so :-(). > > b) This is cryto code and may have legal ramifications that none of > > us have fully evaluated (and I wouldn't consider it fully evaluated > > until some one has consulted with the State Department and/or an > > attourny (didn't we have some one once offer us free or low cost > > legal counsel??). > > Do US embassies have PR State Department folks I could ask? Don't know. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Mon Jun 26 04:46:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA09312 for current-outgoing; Mon, 26 Jun 1995 04:46:29 -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 EAA09306 for ; Mon, 26 Jun 1995 04:46:26 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id EAA03980; Mon, 26 Jun 1995 04:46:41 -0700 From: "Rodney W. Grimes" Message-Id: <199506261146.EAA03980@gndrsh.aac.dev.com> Subject: Re: cvs commit: src/share/FAQ/extras stable-supfile To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Mon, 26 Jun 1995 04:46:41 -0700 (PDT) Cc: FreeBSD-current@FreeBSD.Org (FreeBSD current) In-Reply-To: <199506261143.EAA03964@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Jun 26, 95 04:43:46 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: 833 Sender: current-owner@FreeBSD.Org Precedence: bulk > > > > > rgrimes 95/06/26 04:41:26 > > > > Added: share/FAQ/extras stable-supfile > > Log: > > Here is a supfile for getting the -stable bits from SUP.FreeBSD.ORG. > > And this was pulled into the RELENG_2_1_0 branch by tagging it correctly. > (cvs tag -b RELENG_2_1_0 stable-supfile) And as far as I know this is all up and working now (I have to wait for the 9:00 am run to make sure the cron job works to do the updates and supscans, but I hand tested it and am very confident it is correct). I did a quicky mini sup of just a few parts and it seems to work just fine... Now on to create a few new mailling lists (or do I hand that over to jmb???). -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Mon Jun 26 06:08:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA11683 for current-outgoing; Mon, 26 Jun 1995 06:08:58 -0700 Received: from kryten.atinc.com (kryten.atinc.com [198.138.38.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA11677 for ; Mon, 26 Jun 1995 06:08:55 -0700 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8.3) id JAA13093; Mon, 26 Jun 1995 09:00:35 -0400 Date: Mon, 26 Jun 1995 09:00:34 -0400 (EDT) From: "Jonathan M. Bresler" Subject: Re: cvs commit: src/share/FAQ/extras stable-supfile To: "Rodney W. Grimes" cc: "Rodney W. Grimes" , FreeBSD current In-Reply-To: <199506261146.EAA03980@gndrsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.Org Precedence: bulk On Mon, 26 Jun 1995, Rodney W. Grimes wrote: > > Now on to create a few new mailling lists (or do I hand that over to > jmb???). i'll take care of it ;) what's the name of the new list, and is there an initial list of subscribers and do you have an info file about the list....just a few lines to explain to people what its about. they can get this information with the majordomo 'info' command. Jonathan M. Bresler jmb@kryten.atinc.com | Analysis & Technology, Inc. | 2341 Jeff Davis Hwy play go. | Arlington, VA 22202 ride bike. hack FreeBSD.--ah the good life | 703-418-2800 x346 From owner-freebsd-current Mon Jun 26 06:54:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA13206 for current-outgoing; Mon, 26 Jun 1995 06:54:29 -0700 Received: from whisker.internet-eireann.ie (whisker.internet-eireann.ie [194.9.34.204]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA13195 ; Mon, 26 Jun 1995 06:54:19 -0700 Received: from localhost (localhost [127.0.0.1]) by whisker.internet-eireann.ie (8.6.11/8.6.9) with SMTP id OAA00986; Mon, 26 Jun 1995 14:54:57 +0100 To: Gennady Sorokopud cc: Joerg Wunsch , J Wunsch , Bruce Evans , current@freebsd.org Subject: Re: no bell under Xinside server In-reply-to: Your message of "Mon, 26 Jun 1995 10:10:18 +0300." Date: Mon, 26 Jun 1995 14:54:56 +0100 Message-ID: <984.804174896@whisker.internet-eireann.ie> From: "Jordan K. Hubbard" Sender: current-owner@freebsd.org Precedence: bulk > Hello! > > So what do you suggest to folks that still wants to use Xinside > with syscons? > > Advising things to Xinside folks sounds nice but...:-) I don't get it. This has been FIXED for awhile, for both XFree86 and Xaccel (I'm using Xaccel right now with 2.0.5 and it beeps just fine!). What release are you running, Gennady? Jordan From owner-freebsd-current Mon Jun 26 06:58:56 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA13422 for current-outgoing; Mon, 26 Jun 1995 06:58:56 -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 GAA13416 for ; Mon, 26 Jun 1995 06:58:54 -0700 Received: from borg.ess.harris.com (suw2k.ess.harris.com) by ess.harris.com (5.x/SMI-SVR4) id AA04205; Mon, 26 Jun 1995 09:58:44 -0400 Received: by borg.ess.harris.com (4.1/SMI-4.1) id AA00611; Mon, 26 Jun 95 09:56:24 EDT Date: Mon, 26 Jun 95 09:56:24 EDT From: jleppek@suw2k.ess.harris.com (James Leppek) Message-Id: <9506261356.AA00611@borg.ess.harris.com> To: freebsd-current@freebsd.org Subject: Re: Crypt code summary(2). Sender: current-owner@freebsd.org Precedence: bulk while the work in rfc1421..24 dealing with internet mail is important the arena of "general" application level internet security is quite active. As a researcher in this area there are a variety of SAMPs (security association management protocols) and KMPs (key management protocols) that are being hottly debated at every conference and standards meeting. I am hoping to use freebsd to pitch my own abstract security services(SNAPI) interface at the next technology transfer conference in august if my NEC notebooks arrive in time. The point is that there is no clear solution, or even path, at this time. The IEEE802.10 folks have been struggling to come to some consensus for years. Motorola is actively pushing there SAMP, while commercial organization like netscape and NCSA utilize niche solutions like SSL(Secured Socket Layer) and SHTTP. Even this activity was a battle and I believe the terisa activity was an attempt to get just these 2 protocols together. Remember as well that IPNG is around the corner with additional intrinisc security capabilities (if anyone figures out what to do with them :-) ) While I have been a fbsd advocate since 1993, I have not been an "active" contributor so maybe I shouldn't have a say but I feel obligated to offer an opinion which is, don't try to commit security services to the src tree yet. The ports or experimental areas are a much better home and would make it much easier to avoid stepping on those nasty US munitions laws :-) The dust will settle soon to a "few" possibilities and then a path should be chosen. Jim Leppek > From owner-freebsd-current@freefall.cdrom.com Mon Jun 26 05:18:44 1995 > X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol > To: "Rodney W. Grimes" > Cc: phk@freefall.cdrom.com (Poul-Henning Kamp), mark@grondar.za, > wollman@halloran-eldar.lcs.mit.edu, current@freebsd.org > Subject: Re: Crypt code summary(2). > Date: Mon, 26 Jun 1995 11:20:11 +0200 > From: Mark Murray > Sender: current-owner@freebsd.org > > > I am going to counter Poul, and agree with Garrett, and give reasons > > for doing so. > > ...and I am going to debate this too! > > > a) It is very likely to change as RFC's get done to cover this and > > we will more or less be forced to rip out what ever we had done > > to implement what is in the RFCs. > > The SSLeay code is already covered by RFC's. See rfc1421, rfc1422, rfc1423 > and rfc1424. > > > b) This is cryto code and may have legal ramifications that none of > > us have fully evaluated (and I wouldn't consider it fully evaluated > > until some one has consulted with the State Department and/or an > > attourny (didn't we have some one once offer us free or low cost > > legal counsel??). > > Do US embassies have PR State Department folks I could ask? > > M > > -- > Mark Murray > 46 Harvey Rd, Claremont, Cape Town 7700, South Africa > +27 21 61-3768 GMT+0200 > From owner-freebsd-current Mon Jun 26 07:33:03 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA14708 for current-outgoing; Mon, 26 Jun 1995 07:33:03 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id HAA14701 for ; Mon, 26 Jun 1995 07:33:01 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA18243; Mon, 26 Jun 1995 10:28:30 -0400 Date: Mon, 26 Jun 1995 10:28:30 -0400 From: Garrett Wollman Message-Id: <9506261428.AA18243@halloran-eldar.lcs.mit.edu> To: Bruce Evans Cc: current@freebsd.org Subject: Re: cvs commit: src/sys/i386/isa sio.c In-Reply-To: <199506252114.HAA07096@godzilla.zeta.org.au> References: <199506252114.HAA07096@godzilla.zeta.org.au> Sender: current-owner@freebsd.org Precedence: bulk < said: >> This is because you don't have priority queueing for TCP ack packets. >> You probably will before the end of the year. > Why didn't we have designed-in things yesterday? Because it's an ongoing research problem, and not susceptible to a quick hack fix. Things are just starting to move from the research environment into a commercial one. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Mon Jun 26 07:47:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA15393 for current-outgoing; Mon, 26 Jun 1995 07:47:17 -0700 Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id HAA15381 for ; Mon, 26 Jun 1995 07:47:09 -0700 Received: by sequent.kiae.su id AA04420 (5.65.kiae-2 for current@freebsd.org); Mon, 26 Jun 1995 18:36:08 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Mon, 26 Jun 95 18:36:06 +0400 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id SAA00931 for current@freebsd.org; Mon, 26 Jun 1995 18:23:22 +0400 To: current@freebsd.org Message-Id: Organization: Olahm Ha-Yetzirah Date: Mon, 26 Jun 1995 18:23:21 +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: mb_map full with GATEWAY and maxusers 64! Lines: 8 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 394 Sender: current-owner@freebsd.org Precedence: bulk Just got it in -current :-( Normal load, not many users, just few telnets, two editors... Any ideas? -- 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 Mon Jun 26 07:50:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA15583 for current-outgoing; Mon, 26 Jun 1995 07:50:19 -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 HAA15575 for ; Mon, 26 Jun 1995 07:50:13 -0700 Received: (from peter@localhost) by haywire.DIALix.COM (8.6.12/8.6.12/DIALix) id WAA16011; Mon, 26 Jun 1995 22:50:07 +0800 Date: Mon, 26 Jun 1995 22:50:06 +0800 (WST) From: Peter Wemm To: current@freebsd.org Subject: bug in Linux^H^H^H^H^HDoom Emulator Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk Thanks for committing it Soren (?? is that how you write it in 7-bit ascii?). If you compile a kernel with options DIAGNOSTIC, it running doom will cause a panic inside ufs_access - the vnode in the VOP_ACCESS call in linux_misc.c is not locked at this point. I've had a look, and based on what I saw in kern_exec.c, I suggest that the following patch *might* be in order... I dont know if it's correct and have not yet compiled a kernel to test it, so caveat emptor! kern_exec.c approximately does this: NDINIT(... FOLLOW | LOCKLEAF ...) namei(&nd). vp = nd..... [...] err = VOP_ACCESS(vp) err = VOP_OPEN(vp) VOP_UNLOCK(vp) err = vm_mmap(vp...) I added LOCKLEAF and a VOP_UNLOCK() to i386/linux/linux_misc.c - I'd appreciate knowing if it looks right or if it's going to cause the file system to get eaten.. :-) Cheers, -Peter (PS: Thanks for comitting it Soren! :-) *** linux_misc.c.dist Mon Jun 26 01:32:37 1995 --- linux_misc.c Mon Jun 26 22:38:41 1995 *************** *** 188,194 **** printf("Linux-emul(%d): uselib(%s)\n", p->p_pid, path); #endif ! NDINIT(&ni, LOOKUP, FOLLOW, UIO_SYSSPACE, path, p); if (error = namei(&ni)) return error; --- 188,194 ---- printf("Linux-emul(%d): uselib(%s)\n", p->p_pid, path); #endif ! NDINIT(&ni, LOOKUP, FOLLOW | LOCKLEAF, UIO_SYSSPACE, path, p); if (error = namei(&ni)) return error; *************** *** 215,220 **** --- 215,222 ---- if (error = VOP_OPEN(vnodep, FREAD, p->p_ucred, p)) return error; + + VOP_UNLOCK(vnodep); /* lock no longer needed */ error = vm_mmap(kernel_map, (vm_offset_t *)&a_out, 1024, VM_PROT_READ, VM_PROT_READ, 0, (caddr_t)vnodep, 0); From owner-freebsd-current Mon Jun 26 07:50:51 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA15692 for current-outgoing; Mon, 26 Jun 1995 07:50:51 -0700 Received: (from phk@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA15673 ; Mon, 26 Jun 1995 07:50:47 -0700 From: Poul-Henning Kamp Message-Id: <199506261450.HAA15673@freefall.cdrom.com> Subject: Re: Crypt code summary(2). To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Mon, 26 Jun 1995 07:50:47 -0700 (PDT) Cc: mark@grondar.za, wollman@halloran-eldar.lcs.mit.edu, current@freebsd.org In-Reply-To: <199506260910.CAA03201@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Jun 26, 95 02:10:10 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 795 Sender: current-owner@freebsd.org Precedence: bulk > > > That certainly is a possibility. It is not _my_ #1 choice, though. > > > > I going to counter Garrett, and say: Put it in the main branch. > > I am going to counter Poul, and agree with Garrett, and give reasons > for doing so. > > a) It is very likely to change as RFC's get done to cover this and > we will more or less be forced to rip out what ever we had done > to implement what is in the RFCs. SSL is implemented in NetScape. It's unlikely to change at all. I already stated my argumentes earlier. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Just that: dried leaves in boiling water ? From owner-freebsd-current Mon Jun 26 08:01:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA16409 for current-outgoing; Mon, 26 Jun 1995 08:01:14 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA16402 for ; Mon, 26 Jun 1995 08:01:12 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA18314; Mon, 26 Jun 1995 11:01:09 -0400 Date: Mon, 26 Jun 1995 11:01:09 -0400 From: Garrett Wollman Message-Id: <9506261501.AA18314@halloran-eldar.lcs.mit.edu> To: Poul-Henning Kamp Cc: current@freebsd.org Subject: Re: Crypt code summary(2). In-Reply-To: <199506261450.HAA15673@freefall.cdrom.com> References: <199506260910.CAA03201@gndrsh.aac.dev.com> <199506261450.HAA15673@freefall.cdrom.com> Sender: current-owner@freebsd.org Precedence: bulk < said: > SSL is implemented in NetScape. It's unlikely to change at all. Which makes it all the more more important that we wait to see what really ends up getting standardized. One company's proprietary software may not get implemented by other vendors. More importantly, the technology is subject to patents in the US and probably other countries where such patents are legal. I don't want to see FreeBSD dragged into even more legal difficulties than we have already had. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Mon Jun 26 08:08:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA16797 for current-outgoing; Mon, 26 Jun 1995 08:08:13 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA16791 for ; Mon, 26 Jun 1995 08:08:10 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA18338; Mon, 26 Jun 1995 11:07:10 -0400 Date: Mon, 26 Jun 1995 11:07:10 -0400 From: Garrett Wollman Message-Id: <9506261507.AA18338@halloran-eldar.lcs.mit.edu> To: Mark Murray Cc: current@freebsd.org Subject: Re: Crypt code summary(2). In-Reply-To: <199506260920.LAA12300@grumble.grondar.za> References: <199506260920.LAA12300@grumble.grondar.za> Sender: current-owner@freebsd.org Precedence: bulk < said: > The SSLeay code is already covered by RFC's. See rfc1421, rfc1422, rfc1423 > and rfc1424. Nice try. What you have quoted are the privacy-enhanced mail RFCs. This has nothing to do with creating encrypted real-time communication sessions. > Do US embassies have PR State Department folks I could ask? You would have to ask them. They might even give you an answer. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Mon Jun 26 08:08:56 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA16916 for current-outgoing; Mon, 26 Jun 1995 08:08:56 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA16907 for ; Mon, 26 Jun 1995 08:08:54 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA18341; Mon, 26 Jun 1995 11:08:46 -0400 Date: Mon, 26 Jun 1995 11:08:46 -0400 From: Garrett Wollman Message-Id: <9506261508.AA18341@halloran-eldar.lcs.mit.edu> To: davidg@root.com Cc: current@freebsd.org Subject: Re: cvs commit: src/sys/i386/isa sio.c In-Reply-To: <199506252258.PAA00581@corbin.Root.COM> References: <9506252023.AA17317@halloran-eldar.lcs.mit.edu> <199506252258.PAA00581@corbin.Root.COM> Sender: current-owner@freebsd.org Precedence: bulk < said: >> This is because you don't have priority queueing for TCP ack packets. >> You probably will before the end of the year. > I'm not sure this going help a lot - most of the data gets buffered in the > modem and priority queing for ACKs isn't going to help this. This is arguably a problem with the modems and not the machines. This sort of situation makes it impossible to offer any useful sort of quality-of-service beyond best-effort. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Mon Jun 26 08:12:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA17436 for current-outgoing; Mon, 26 Jun 1995 08:12:49 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA17427 for ; Mon, 26 Jun 1995 08:12:46 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA18349; Mon, 26 Jun 1995 11:12:05 -0400 Date: Mon, 26 Jun 1995 11:12:05 -0400 From: Garrett Wollman Message-Id: <9506261512.AA18349@halloran-eldar.lcs.mit.edu> To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka "Andrey A. Chernov, Black Mage" Cc: Mark Murray , Garrett Wollman , current@freebsd.org Subject: Re: Crypt code summary(2). In-Reply-To: References: <199506252003.WAA08724@grumble.grondar.za> <9506252018.AA17301@halloran-eldar.lcs.mit.edu> Sender: current-owner@freebsd.org Precedence: bulk < said: > Internet Auth. require MD5 which implementation in software > slow down IP approx. in two times, This is Not A Problem. 1) It is always possible to use other digital signature techniques. 2) It's OK if it's slow; it's still faster than an Ethernet, which makes it fast enough for the needs of most users. > see latest IETF materials. Not all RFCs are Standards. > SSL is speed winner here. And it's also proprietary. And it requires technology which it would be illegal for Walnut Creek to sell even within the US without getting a license from PKP. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Mon Jun 26 08:15:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA17822 for current-outgoing; Mon, 26 Jun 1995 08:15:27 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA17806 for ; Mon, 26 Jun 1995 08:15:23 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA18362; Mon, 26 Jun 1995 11:14:34 -0400 Date: Mon, 26 Jun 1995 11:14:34 -0400 From: Garrett Wollman Message-Id: <9506261514.AA18362@halloran-eldar.lcs.mit.edu> To: Mark Murray Cc: Garrett Wollman , current@freebsd.org Subject: Re: Crypt code summary(2). In-Reply-To: <199506252058.WAA08903@grumble.grondar.za> References: <199506252058.WAA08903@grumble.grondar.za> Sender: current-owner@freebsd.org Precedence: bulk < said: >> /I/ would prefer it to be the Internet Authentication and >> Encapsulating Security payloads myself. If I ever have free time >> again I may write support myself (although I'd prefer to have somebody >> else's code). > Right - so there is a recognition that something is needed. The > discussion now goes to `what?' I personally have not heard of the code > you mention. See the output of the IP Security working group. The AH and ESP were developed to be the standard (i.e., required for inclusion in every conforming implementation) mechanism for security in IPv6, and recent work in the IP Security WG has developed a way for them to be implemented under IPv4 as well. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Mon Jun 26 09:22:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA21166 for current-outgoing; Mon, 26 Jun 1995 09:22:45 -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 JAA21160 for ; Mon, 26 Jun 1995 09:22:40 -0700 Received: (from peter@localhost) by haywire.DIALix.COM (8.6.12/8.6.12/DIALix) id AAA20926; Tue, 27 Jun 1995 00:22:35 +0800 Date: Tue, 27 Jun 1995 00:22:34 +0800 (WST) From: Peter Wemm To: current@freebsd.org Subject: when is the supscan done? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk Quickie: How often and when are the cvs updates and sup scans done on sup.freebsd.org? I think somebody mentioned 9am local time at one point... Cheers, -Peter From owner-freebsd-current Mon Jun 26 09:24:11 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA21274 for current-outgoing; Mon, 26 Jun 1995 09:24:11 -0700 Received: from ns.dknet.dk (root@ns.dknet.dk [193.88.44.42]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA21267 for ; Mon, 26 Jun 1995 09:24:07 -0700 Received: from login.dknet.dk by ns.dknet.dk with SMTP id AA26881 (5.65c8/IDA-1.4.4j); Mon, 26 Jun 1995 18:15:42 +0200 Received: by login.dknet.dk (4.1/SMI-4.1DKnet00) id AA29761; Mon, 26 Jun 95 18:15:33 +0200 Message-Id: <9506261615.AA29761@login.dknet.dk> Subject: Re: bug in Linux^H^H^H^H^HDoom Emulator To: peter@haywire.DIALix.COM (Peter Wemm) Date: Mon, 26 Jun 95 18:15:33 MET DST Cc: current@freebsd.org In-Reply-To: ; from "Peter Wemm" at Jun 26, 95 10:50 pm From: sos@freebsd.org Reply-To: sos@freebsd.org X-Charset: ASCII X-Char-Esc: 29 Sender: current-owner@freebsd.org Precedence: bulk In reply to Peter Wemm who wrote: > > Thanks for committing it Soren (?? is that how you write it in 7-bit ascii?). Yep it is :-) > If you compile a kernel with options DIAGNOSTIC, it running doom will > cause a panic inside ufs_access - the vnode in the VOP_ACCESS call in > linux_misc.c is not locked at this point. Yep I've seen this too (now), I'll see waht can be done about it (your patch looks right though) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org | sos@login.dknet.dk) FreeBSD Core Team So much code to hack -- so little time From owner-freebsd-current Mon Jun 26 09:44:18 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA21891 for current-outgoing; Mon, 26 Jun 1995 09:44:18 -0700 Received: from irbs.irbs.com (irbs.com [199.182.75.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA21885 for ; Mon, 26 Jun 1995 09:44:15 -0700 Received: (from jc@localhost) by irbs.irbs.com (8.6.11/8.6.6) id MAA06473; Mon, 26 Jun 1995 12:40:26 -0400 From: John Capo Message-Id: <199506261640.MAA06473@irbs.irbs.com> Subject: Re: mb_map full with GATEWAY and maxusers 64! To: ache@astral.msk.su (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka) Date: Mon, 26 Jun 1995 12:40:25 -0400 (EDT) Cc: freebsd-current@freefall.cdrom.com (freebsd-current) In-Reply-To: from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka" at Jun 26, 95 06:23:21 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: 624 Sender: current-owner@FreeBSD.org Precedence: bulk =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka writes: > > Just got it in -current :-( > Normal load, not many users, just few telnets, two editors... > Any ideas? > -- > 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 > I have seen it with maxusers at 48 and 96 on a lightly loaded system. I switched to NMBCLUSTERS=2048 and have not seen it since. -- John Capo From owner-freebsd-current Mon Jun 26 10:00:07 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA22337 for current-outgoing; Mon, 26 Jun 1995 10:00:07 -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 KAA22331 for ; Mon, 26 Jun 1995 10:00:04 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id JAA04477; Mon, 26 Jun 1995 09:59:42 -0700 From: "Rodney W. Grimes" Message-Id: <199506261659.JAA04477@gndrsh.aac.dev.com> Subject: Re: cvs commit: src/share/FAQ/extras stable-supfile To: jmb@kryten.Atinc.COM (Jonathan M. Bresler) Date: Mon, 26 Jun 1995 09:59:42 -0700 (PDT) Cc: FreeBSD-current@FreeBSD.Org In-Reply-To: from "Jonathan M. Bresler" at Jun 26, 95 09:00:34 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: 1262 Sender: current-owner@FreeBSD.Org Precedence: bulk > > On Mon, 26 Jun 1995, Rodney W. Grimes wrote: > > > > > Now on to create a few new mailling lists (or do I hand that over to > > jmb???). > > i'll take care of it ;) > > what's the name of the new list, and is there an initial list of > subscribers and do you have an info file about the list....just a few > lines to explain to people what its about. they can get this > information with the majordomo 'info' command. It should be just one mailling lists now that I think about it, FreeBSD-stable (just like FreeBSD-current). The ``info'' should be very similiar to -current, only reworded to say this is for the -stable sup bits that we now support and this set of bits is always relative or built upon the last production ``RELEASE'' of freebsd with only critical bug fixes and such going into it. It is a step in grade between running the last release, and running -current or snap shot systems. Initial subscribes must at least be the release engineering team, which is ``jhk, davidg, rgrimes'', we all have local mail forwards on freefall so that should do it. Thank you very much, -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Mon Jun 26 10:03:51 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA22473 for current-outgoing; Mon, 26 Jun 1995 10:03:51 -0700 Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA22454 for ; Mon, 26 Jun 1995 10:03:05 -0700 Received: by sequent.kiae.su id AA18368 (5.65.kiae-2 ); Mon, 26 Jun 1995 20:52:32 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Mon, 26 Jun 95 20:52:31 +0400 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id UAA01412; Mon, 26 Jun 1995 20:47:21 +0400 To: Mark Murray , Garrett Wollman Cc: current@freebsd.org References: <199506260920.LAA12300@grumble.grondar.za> <9506261507.AA18338@halloran-eldar.lcs.mit.edu> In-Reply-To: <9506261507.AA18338@halloran-eldar.lcs.mit.edu>; from Garrett Wollman at Mon, 26 Jun 1995 11:07:10 -0400 Message-Id: Organization: Olahm Ha-Yetzirah Date: Mon, 26 Jun 1995 20:47:21 +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: Re: Crypt code summary(2). Lines: 22 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 909 Sender: current-owner@freebsd.org Precedence: bulk In message <9506261507.AA18338@halloran-eldar.lcs.mit.edu> Garrett Wollman writes: >< said: >> The SSLeay code is already covered by RFC's. See rfc1421, rfc1422, rfc1423 >> and rfc1424. >Nice try. What you have quoted are the privacy-enhanced mail RFCs. >This has nothing to do with creating encrypted real-time communication >sessions. SSL exists now in pre-RFC state until October. You can got this pre-RFC somewhere in http://www.netscape.com/ You can also look at ftp://ds.internic.net/internet-drafts/draft-hickman-netscape-ssl-01.txt -- 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 Mon Jun 26 10:05:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA22602 for current-outgoing; Mon, 26 Jun 1995 10:05:36 -0700 Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA22592 for ; Mon, 26 Jun 1995 10:05:30 -0700 Received: by sequent.kiae.su id AA18274 (5.65.kiae-2 ); Mon, 26 Jun 1995 20:51:38 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Mon, 26 Jun 95 20:51:36 +0400 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id UAA01383; Mon, 26 Jun 1995 20:42:19 +0400 To: Garrett Wollman Cc: current@freebsd.org, Mark Murray References: <199506252003.WAA08724@grumble.grondar.za> <9506252018.AA17301@halloran-eldar.lcs.mit.edu> <9506261512.AA18349@halloran-eldar.lcs.mit.edu> In-Reply-To: <9506261512.AA18349@halloran-eldar.lcs.mit.edu>; from Garrett Wollman at Mon, 26 Jun 1995 11:12:05 -0400 Message-Id: Organization: Olahm Ha-Yetzirah Date: Mon, 26 Jun 1995 20:42:18 +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: Re: Crypt code summary(2). Lines: 53 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 2331 Sender: current-owner@freebsd.org Precedence: bulk In message <9506261512.AA18349@halloran-eldar.lcs.mit.edu> Garrett Wollman writes: >< said: >> Internet Auth. require MD5 which implementation in software >> slow down IP approx. in two times, >This is Not A Problem. > 1) It is always possible to use other digital signature > techniques. > 2) It's OK if it's slow; it's still faster than an Ethernet, > which makes it fast enough for the needs of most users. Here some quote, more detailed report will be into RFC1810: MD5 is an authentication algorithm, which has been proposed as the default authentication option in IPv6. When enabled, the MD5 algorithm operates over the entire data packet, including header. This RFC addresses how fast MD5 can be implemented in software and hardware, and whether it supports currently available IP bandwidth. MD5 can be implemented in existing hardware technology at 256 Mbps, and in software at 87 Mbps. These rates cannot support current IP rates, e.g., 100 Mbps TCP and 130 Mbps UDP over ATM. If MD5 cannot support existing network bandwidth using existing technology, it will not scale as network speeds increase in the future. This RFC is intended to alert the IP community about the performance limitations of MD5, and to suggest that alternatives be considered for use in high speed IP implementations. >> SSL is speed winner here. >And it's also proprietary. And it requires technology which it would >be illegal for Walnut Creek to sell even within the US without getting >a license from PKP. 1) SSLref SSL implementation (Netscape) uses RSAREF, you don't need PKP license for it. 2) SSLay SSL implementation (from E.Y.) uses its own RSA routines, not know about license here. 3) Outside USA exists RSAEURO, which is compatible with RSAREF and made in Europe. I.e. after some shuffling, it will be legal to distribute different SSL kits in USA and Outside both. -- 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 Mon Jun 26 10:18:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA23236 for current-outgoing; Mon, 26 Jun 1995 10:18:13 -0700 Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA23228 for ; Mon, 26 Jun 1995 10:17:25 -0700 Received: by sequent.kiae.su id AA23279 (5.65.kiae-2 ); Mon, 26 Jun 1995 21:09:01 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Mon, 26 Jun 95 21:08:58 +0400 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id VAA01533; Mon, 26 Jun 1995 21:07:31 +0400 To: John Capo Cc: freebsd-current References: <199506261640.MAA06473@irbs.irbs.com> In-Reply-To: <199506261640.MAA06473@irbs.irbs.com>; from John Capo at Mon, 26 Jun 1995 12:40:25 -0400 (EDT) Message-Id: Organization: Olahm Ha-Yetzirah Date: Mon, 26 Jun 1995 21:07:30 +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: Re: mb_map full with GATEWAY and maxusers 64! Lines: 26 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 873 Sender: current-owner@FreeBSD.org Precedence: bulk In message <199506261640.MAA06473@irbs.irbs.com> John Capo writes: >=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka writes: >> >> Just got it in -current :-( >> Normal load, not many users, just few telnets, two editors... >I have seen it with maxusers at 48 and 96 on a lightly loaded system. >I switched to NMBCLUSTERS=2048 and have not seen it since. Maybe we need simple increase NMBCLUSTERS calculation as default to something like: #ifdef GATEWAY #define NMBCLUSTERS (2048 + maxusers * 16) #else #define NMBCLUSTERS (1024 + maxusers * 16) #endif Any opinions? -- 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 Mon Jun 26 10:18:50 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA23311 for current-outgoing; Mon, 26 Jun 1995 10:18:50 -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 KAA23305 for ; Mon, 26 Jun 1995 10:18:47 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id KAA04656; Mon, 26 Jun 1995 10:18:52 -0700 From: "Rodney W. Grimes" Message-Id: <199506261718.KAA04656@gndrsh.aac.dev.com> Subject: Re: when is the supscan done? To: peter@haywire.DIALix.COM (Peter Wemm) Date: Mon, 26 Jun 1995 10:18:52 -0700 (PDT) Cc: current@freebsd.org In-Reply-To: from "Peter Wemm" at Jun 27, 95 00:22:34 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: 491 Sender: current-owner@freebsd.org Precedence: bulk > > Quickie: How often and when are the cvs updates and sup scans done on > sup.freebsd.org? > > I think somebody mentioned 9am local time at one point... I mentioned 9am, and that was just because I knew that would be the next run of the job. They run at: 0 1,7,13,19 * * * root /root/bin/update_usrall -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Mon Jun 26 10:32:00 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA23834 for current-outgoing; Mon, 26 Jun 1995 10:32:00 -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 KAA23828 for ; Mon, 26 Jun 1995 10:31:56 -0700 Received: by haven.uniserve.com id <30744>; Mon, 26 Jun 1995 10:32:36 +0100 Date: Mon, 26 Jun 1995 10:32:28 -0700 (PDT) From: Tom Samplonius To: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka Andrey A. Chernov, Black Mage" cc: John Capo , freebsd-current Subject: Re: mb_map full with GATEWAY and maxusers 64! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Mon, 26 Jun 1995, =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka Andrey A. Chernov, Black Mage wrote: > >I have seen it with maxusers at 48 and 96 on a lightly loaded system. > >I switched to NMBCLUSTERS=2048 and have not seen it since. > > Maybe we need simple increase NMBCLUSTERS calculation as default to > something like: > > #ifdef GATEWAY > #define NMBCLUSTERS (2048 + maxusers * 16) > #else > #define NMBCLUSTERS (1024 + maxusers * 16) > #endif > > Any opinions? I think that is too high. Most (all?) users that reported this problem found that 2048 buffers cured it. Yet your calculcation would give these users even more buffers that would likely be unneeded. As an alternative: - document NMBCLUSTERS in LINT (as of 2.0.5R, this still wasn't mentioned) - include a explicit "options NMBCLUSTERS" line in the GENERIC kernel, with then note that "mb_map" full indicates that you've run out these buffers I would just prefer that this just be documented rather than to bury the calculation somewhere. Tom From owner-freebsd-current Mon Jun 26 10:35:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA24038 for current-outgoing; Mon, 26 Jun 1995 10:35:12 -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 KAA24032 for ; Mon, 26 Jun 1995 10:35:08 -0700 Received: (from peter@localhost) by haywire.DIALix.COM (8.6.12/8.6.12/DIALix) id BAA24750; Tue, 27 Jun 1995 01:34:51 +0800 Date: Tue, 27 Jun 1995 01:34:50 +0800 (WST) From: Peter Wemm To: "Rodney W. Grimes" cc: current@freebsd.org Subject: Re: when is the supscan done? In-Reply-To: <199506261718.KAA04656@gndrsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk On Mon, 26 Jun 1995, Rodney W. Grimes wrote: > > Quickie: How often and when are the cvs updates and sup scans done on > > sup.freebsd.org? > > > > I think somebody mentioned 9am local time at one point... > > I mentioned 9am, and that was just because I knew that would be the > next run of the job. They run at: > 0 1,7,13,19 * * * root /root/bin/update_usrall Thanks! Just as a $0.02 suggestion: I wouldn't mind seeing the results of a "cvs update -q" (or whatever) when this job is run... I'd find that a lot easier to read than the output that "sup -v" generates when run on the machine here. Perhaps others would be interested too? (Please dont hold this against the suggestion, but the NetBSD folks do it, (which I read) and I find it a convenient summary). Cheers, -Peter From owner-freebsd-current Mon Jun 26 10:41:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA24480 for current-outgoing; Mon, 26 Jun 1995 10:41:48 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA24474 for ; Mon, 26 Jun 1995 10:41:46 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA26976; Mon, 26 Jun 95 11:33:19 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506261733.AA26976@cs.weber.edu> Subject: Re: Crypt code summary(2). To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Mon, 26 Jun 95 11:33:19 MDT Cc: phk@freefall.cdrom.com, mark@grondar.za, wollman@halloran-eldar.lcs.mit.edu, current@freebsd.org In-Reply-To: <199506260910.CAA03201@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Jun 26, 95 02:10:10 am X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@freebsd.org Precedence: bulk > b) This is cryto code and may have legal ramifications that none of > us have fully evaluated (and I wouldn't consider it fully evaluated > until some one has consulted with the State Department and/or an > attourny (didn't we have some one once offer us free or low cost > legal counsel??). Yes. It was offered on the basis that it be used to form a BSD Consortium. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jun 26 10:50:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA24844 for current-outgoing; Mon, 26 Jun 1995 10:50:46 -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 KAA24838 for ; Mon, 26 Jun 1995 10:50:45 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by wc.cdrom.com (8.6.12/8.6.12) with SMTP id KAA07355 for ; Mon, 26 Jun 1995 10:50:41 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA18654; Mon, 26 Jun 1995 13:47:43 -0400 Date: Mon, 26 Jun 1995 13:47:43 -0400 From: Garrett Wollman Message-Id: <9506261747.AA18654@halloran-eldar.lcs.mit.edu> To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka "Andrey A. Chernov, Black Mage" Cc: current@freebsd.org Subject: Re: Crypt code summary(2). In-Reply-To: References: <199506260920.LAA12300@grumble.grondar.za> <9506261507.AA18338@halloran-eldar.lcs.mit.edu> Sender: current-owner@freebsd.org Precedence: bulk < said: > SSL exists now in pre-RFC state until October. NOT ALL RFCs ARE STANDARDS. INTERNET-DRAFTS ARE NOT STANDARDS. Unless Netscape gives up change control on this specification, it will never be a standard. There does not exist general agreement in the community at this point what is the best mechanism to provide end-to-end security. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Mon Jun 26 10:55:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA25249 for current-outgoing; Mon, 26 Jun 1995 10:55:47 -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 KAA25242 ; Mon, 26 Jun 1995 10:55:43 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id KAA04885; Mon, 26 Jun 1995 10:55:49 -0700 From: "Rodney W. Grimes" Message-Id: <199506261755.KAA04885@gndrsh.aac.dev.com> Subject: Re: when is the supscan done? To: peter@haywire.DIALix.COM (Peter Wemm) Date: Mon, 26 Jun 1995 10:55:49 -0700 (PDT) Cc: current@freebsd.org, jmb@freebsd.org In-Reply-To: from "Peter Wemm" at Jun 27, 95 01:34:50 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: 1280 Sender: current-owner@freebsd.org Precedence: bulk > > On Mon, 26 Jun 1995, Rodney W. Grimes wrote: > > > Quickie: How often and when are the cvs updates and sup scans done on > > > sup.freebsd.org? > > > > > > I think somebody mentioned 9am local time at one point... > > > > I mentioned 9am, and that was just because I knew that would be the > > next run of the job. They run at: > > 0 1,7,13,19 * * * root /root/bin/update_usrall > > Thanks! > > Just as a $0.02 suggestion: I wouldn't mind seeing the results of a > "cvs update -q" (or whatever) when this job is run... I'd find that a lot > easier to read than the output that "sup -v" generates when run on the > machine here. Perhaps others would be interested too? > > (Please dont hold this against the suggestion, but the NetBSD folks do > it, (which I read) and I find it a convenient summary). Easy enough, what mailling list do they send it out on?? Or do they use a seperate list (cc: to jmb to keep him aware that I might be asking for another mailling list). Right now this just goes out to the root: alias in /etc/sendmail.cf, but that can be changed pretty easily. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Mon Jun 26 10:56:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA25335 for current-outgoing; Mon, 26 Jun 1995 10:56:57 -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 KAA25329 ; Mon, 26 Jun 1995 10:56:53 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id KAA04895; Mon, 26 Jun 1995 10:57:03 -0700 From: "Rodney W. Grimes" Message-Id: <199506261757.KAA04895@gndrsh.aac.dev.com> Subject: Re: Crypt code summary(2). To: terry@cs.weber.edu (Terry Lambert) Date: Mon, 26 Jun 1995 10:57:03 -0700 (PDT) Cc: phk@freefall.cdrom.com, mark@grondar.za, wollman@halloran-eldar.lcs.mit.edu, current@freebsd.org In-Reply-To: <9506261733.AA26976@cs.weber.edu> from "Terry Lambert" at Jun 26, 95 11:33:19 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: 688 Sender: current-owner@freebsd.org Precedence: bulk > > > b) This is cryto code and may have legal ramifications that none of > > us have fully evaluated (and I wouldn't consider it fully evaluated > > until some one has consulted with the State Department and/or an > > attourny (didn't we have some one once offer us free or low cost > > legal counsel??). > > Yes. It was offered on the basis that it be used to form a BSD Consortium. Well, since you are the one who always pushes the BSD Consortium, can you tell me how the formation of it is going :-) :-) :-0 -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Mon Jun 26 11:01:40 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA25697 for current-outgoing; Mon, 26 Jun 1995 11:01:40 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA25691 for ; Mon, 26 Jun 1995 11:01:38 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA18675; Mon, 26 Jun 1995 14:00:49 -0400 Date: Mon, 26 Jun 1995 14:00:49 -0400 From: Garrett Wollman Message-Id: <9506261800.AA18675@halloran-eldar.lcs.mit.edu> To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka "Andrey A. Chernov, Black Mage" Cc: current@freebsd.org Subject: Re: Crypt code summary(2). In-Reply-To: References: <199506252003.WAA08724@grumble.grondar.za> <9506252018.AA17301@halloran-eldar.lcs.mit.edu> <9506261512.AA18349@halloran-eldar.lcs.mit.edu> Sender: current-owner@freebsd.org Precedence: bulk < said: > and in software at 87 Mbps. These rates cannot support current IP > rates, e.g., 100 Mbps TCP and 130 Mbps UDP over ATM. As I said, this is simply NOT A PROBLEM for us, and those groups that think it is a problem are free to create their own mechanism using a different authentication method. > 1) SSLref SSL implementation (Netscape) > uses RSAREF, you don't need PKP license for it. Which I would be STRONGLY opposed to having in the source tree. > 2) SSLay SSL implementation (from E.Y.) > uses its own RSA routines, not know about license here. It's not RSAREF, therefore we can't distribute it in the US without a license. (Unless distributors want to get sued; I don't.) > 3) Outside USA exists RSAEURO, which is compatible > with RSAREF and made in Europe. It's not RSAREF, therefore we can't distribute it in the US without a license. (Unless distributors want to get sued; I don't.) I don't seem to be getting through here. We have an elaborate mechanism for dealing with this sort of problem in the ports collection. The base source tree is too big as it is. You're proposing to bloat it even further to include something which belongs in ports if anywhere at all. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Mon Jun 26 11:20:00 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA26432 for current-outgoing; Mon, 26 Jun 1995 11:20:00 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA26426 for ; Mon, 26 Jun 1995 11:19:56 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA28518; Mon, 26 Jun 95 12:12:54 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506261812.AA28518@cs.weber.edu> Subject: Re: bug in Linux^H^H^H^H^HDoom Emulator To: peter@haywire.DIALix.COM (Peter Wemm) Date: Mon, 26 Jun 95 12:12:53 MDT Cc: current@freebsd.org In-Reply-To: from "Peter Wemm" at Jun 26, 95 10:50:06 pm X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@freebsd.org Precedence: bulk vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv DO NOT COMMIT THIS WITHOUT FURTHER CHANGES! ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > *** linux_misc.c.dist Mon Jun 26 01:32:37 1995 > --- linux_misc.c Mon Jun 26 22:38:41 1995 > *************** > *** 188,194 **** > printf("Linux-emul(%d): uselib(%s)\n", p->p_pid, path); > #endif > > ! NDINIT(&ni, LOOKUP, FOLLOW, UIO_SYSSPACE, path, p); > if (error = namei(&ni)) > return error; > > --- 188,194 ---- > printf("Linux-emul(%d): uselib(%s)\n", p->p_pid, path); > #endif > > ! NDINIT(&ni, LOOKUP, FOLLOW | LOCKLEAF, UIO_SYSSPACE, path, p); > if (error = namei(&ni)) > return error; > > *************** > *** 215,220 **** > --- 215,222 ---- > > if (error = VOP_OPEN(vnodep, FREAD, p->p_ucred, p)) > return error; > + > + VOP_UNLOCK(vnodep); /* lock no longer needed */ > > error = vm_mmap(kernel_map, (vm_offset_t *)&a_out, 1024, > VM_PROT_READ, VM_PROT_READ, 0, (caddr_t)vnodep, 0); At the *absolute* least: if (error = VOP_OPEN(vnodep, FREAD, p->p_ucred, p)) { VOP_UNLOCK(vnodep); /* lock no longer needed */ return error; } VOP_UNLOCK(vnodep); /* lock no longer needed */ Unfortunately, from context, I can't tell if there are other intervening error returns or not. If so, they need the same change! Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jun 26 11:21:42 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA26531 for current-outgoing; Mon, 26 Jun 1995 11:21:42 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA26524 for ; Mon, 26 Jun 1995 11:21:22 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.11/8.6.9) with ESMTP id UAA03521; Mon, 26 Jun 1995 20:20:33 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.11/8.6.9) with SMTP id UAA13634; Mon, 26 Jun 1995 20:20:32 +0200 Message-Id: <199506261820.UAA13634@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: Garrett Wollman cc: ache@astral.msk.su, current@freebsd.org Subject: Re: Crypt code summary(2). Date: Mon, 26 Jun 1995 20:20:31 +0200 From: Mark Murray Sender: current-owner@freebsd.org Precedence: bulk > > 1) SSLref SSL implementation (Netscape) > > uses RSAREF, you don't need PKP license for it. > > Which I would be STRONGLY opposed to having in the source tree. Why? You have voiced an opinion for another package (I cannot remember its name). Lets hear some argument for this. I would like _something_. > It's not RSAREF, therefore we can't distribute it in the US without a > license. (Unless distributors want to get sued; I don't.) > > > 3) Outside USA exists RSAEURO, which is compatible > > with RSAREF and made in Europe. > > It's not RSAREF, therefore we can't distribute it in the US without a > license. (Unless distributors want to get sued; I don't.) You are missing a point here. What is wrong (apart from your reservations above) of distributing RSAREF in the USA and RSAEURO elsewhere? > I don't seem to be getting through here. We have an elaborate > mechanism for dealing with this sort of problem in the ports > collection. The base source tree is too big as it is. You're > proposing to bloat it even further to include something which belongs > in ports if anywhere at all. There is a tacit agreement that some form of secure-secure-type mechanism should be in the tree. I (and a couple of others) believe this (SSLeay) is it. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Mon Jun 26 11:23:35 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA26622 for current-outgoing; Mon, 26 Jun 1995 11:23:35 -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 LAA26616 ; Mon, 26 Jun 1995 11:23:32 -0700 Received: (lix@localhost) by cs.pdx.edu (8.6.10/CATastrophe-12/23/94-P) id LAA01591; Mon, 26 Jun 1995 11:23:28 -0700 for Date: Mon, 26 Jun 1995 11:23:28 -0700 From: lix@cs.pdx.edu (xiaoyin li) Message-Id: <199506261823.LAA01591@cs.pdx.edu> To: current@freebsd.org, question@freebsd.org Subject: pine Sender: current-owner@freebsd.org Precedence: bulk I would appreciate very much if someone can tell me how to make "pine" software work on FreeBSD April SNAP system. I coped files from ftp public domain: /pub5/freebsd/FreeBSD-current/ports/mail/pine I also copied pine3.91 software from: Host: ftp.cac.washington.edu My question is how can I compile pine3.91 successfully with above files on my FreeBSD? I tried to compile pine3.91 by using "build bsd", and I got Error Code 1 message as a result. Thank you, Xiaoyin Li System Administrator PSU Bookstore Tel: 503-226-2631 Email: lix@rigel.cs.pdx.edu or: lix@bkst.pdx.edu From owner-freebsd-current Mon Jun 26 11:56:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA28390 for current-outgoing; Mon, 26 Jun 1995 11:56:13 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA28384 for ; Mon, 26 Jun 1995 11:56:11 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA28600; Mon, 26 Jun 95 12:47:47 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506261847.AA28600@cs.weber.edu> Subject: Re: Crypt code summary(2). To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Mon, 26 Jun 95 12:47:47 MDT Cc: phk@freefall.cdrom.com, mark@grondar.za, wollman@halloran-eldar.lcs.mit.edu, current@freebsd.org In-Reply-To: <199506261757.KAA04895@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Jun 26, 95 10:57:03 am X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@freebsd.org Precedence: bulk > > Yes. It was offered on the basis that it be used to form a BSD Consortium. > > Well, since you are the one who always pushes the BSD Consortium, can > you tell me how the formation of it is going :-) :-) :-0 BSDI seems uninterested because they feel they can simply dictate the future of BSD because their strong historical ties to CSRG have resulted in them being the sole recognized authorities. They also have almost total control of the BSD commercial software effort and therefore can dictate the ABI. NetBSD seems uninterested because they feel they can simply dictate the future of BSD because their porting efforts have resulted in them being uniquely suited to taking all the architectural issues into account in their source base. Their ABI compatability efforts have given them access to the commercial software on each ported platform, at least to a limited extent, and they feel they will displace the commercial OS's. FreeBSD seems uninterested because they feel they can simply dictate the future of BSD because of their technological enhancements in the area of installation, VM, and commodity hardware coverage have resulted in them being more palletable to a larger user base. They point to the number of messages in the FreeBSD news groups being larger than the twice number of messages in the NetBSD and BSD groups combined as evidence of their success. Linux seems uninterested because they feel they can simply dictate the use of Linux instead by subverting public BSD channels into Linux advocacy groups. You will be assimilated. They have a magazine. 8-|. Other than that, everyone agrees it's a good idea, but no one wants to make it their part time job, even though it could be a paid job, given that non-profit corporations still have paid employees. Sort of the same as is true for a "BSD Journal" (though given the Linux success in this area, that could go full-time easily). As for me: ideas aren't a problem; time to implement them all *is* a problem. I can think of many, many ways someone can make their own job. On the effort vs. return scale, I'm doing close to the maximum edge on the curve, and don't have much time for following much else. I make intentional exceptions for things I think will advance the state of the art in various areas, but that's more as long term investments in the future than anything else (and the only things most of you see are computer science related). Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jun 26 12:02:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA28688 for current-outgoing; Mon, 26 Jun 1995 12:02:55 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA28682 for ; Mon, 26 Jun 1995 12:02:53 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA18818; Mon, 26 Jun 1995 15:01:54 -0400 Date: Mon, 26 Jun 1995 15:01:54 -0400 From: Garrett Wollman Message-Id: <9506261901.AA18818@halloran-eldar.lcs.mit.edu> To: Mark Murray Cc: Garrett Wollman , ache@astral.msk.su, current@freebsd.org Subject: Re: Crypt code summary(2). In-Reply-To: <199506261820.UAA13634@grumble.grondar.za> References: <199506261820.UAA13634@grumble.grondar.za> Sender: current-owner@freebsd.org Precedence: bulk < said: >> Which I would be STRONGLY opposed to having in the source tree. > Why? You have voiced an opinion for another package (I cannot remember its > name). Lets hear some argument for this. I would like _something_. 1. RSAREF is free for personal or corporate use under the following conditions: o RSAREF, RSAREF applications, and services based on RSAREF applications may not be sold. o You must give RSA the source code of any free RSAREF application you plan to distribute or deploy within your company. RSA will make these applications available to the public, free of charge. 4. You must use the interface described in the RSAREF documentation. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Mon Jun 26 12:07:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA28860 for current-outgoing; Mon, 26 Jun 1995 12:07:28 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA28853 for ; Mon, 26 Jun 1995 12:07:26 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA18830; Mon, 26 Jun 1995 15:06:34 -0400 Date: Mon, 26 Jun 1995 15:06:34 -0400 From: Garrett Wollman Message-Id: <9506261906.AA18830@halloran-eldar.lcs.mit.edu> To: Mark Murray Cc: current@freebsd.org Subject: Re: Crypt code summary(2). In-Reply-To: <9506261901.AA18818@halloran-eldar.lcs.mit.edu> References: <199506261820.UAA13634@grumble.grondar.za> <9506261901.AA18818@halloran-eldar.lcs.mit.edu> Sender: current-owner@freebsd.org Precedence: bulk < o RSAREF, RSAREF applications, and services based on > RSAREF applications may not be sold. This is important! This means that: 1) RSAREF cannot become part of FreeBSD because of this clause. 2) Alternative implementations of RSA cannot become part of FreeBSD because the technology is subject to software patents in the United States and other countries. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Mon Jun 26 12:17:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA29282 for current-outgoing; Mon, 26 Jun 1995 12:17:19 -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 MAA29276 ; Mon, 26 Jun 1995 12:17:14 -0700 Received: (from peter@localhost) by haywire.DIALix.COM (8.6.12/8.6.12/DIALix) id DAA05914; Tue, 27 Jun 1995 03:17:00 +0800 Date: Tue, 27 Jun 1995 03:16:58 +0800 (WST) From: Peter Wemm To: Terry Lambert cc: current@freebsd.org, sos@freebsd.org Subject: Re: bug in Linux^H^H^H^H^HDoom Emulator In-Reply-To: <9506261812.AA28518@cs.weber.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk On Mon, 26 Jun 1995, Terry Lambert wrote: > > vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv > DO NOT COMMIT THIS WITHOUT FURTHER CHANGES! > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Seconded! :-) > > *** linux_misc.c.dist Mon Jun 26 01:32:37 1995 > > --- linux_misc.c Mon Jun 26 22:38:41 1995 > > *************** > > *** 188,194 **** > > printf("Linux-emul(%d): uselib(%s)\n", p->p_pid, path); > > #endif > > > > ! NDINIT(&ni, LOOKUP, FOLLOW, UIO_SYSSPACE, path, p); > > if (error = namei(&ni)) > > return error; > > > > --- 188,194 ---- > > printf("Linux-emul(%d): uselib(%s)\n", p->p_pid, path); > > #endif > > > > ! NDINIT(&ni, LOOKUP, FOLLOW | LOCKLEAF, UIO_SYSSPACE, path, p); > > if (error = namei(&ni)) > > return error; > > > > *************** > > *** 215,220 **** > > --- 215,222 ---- > > > > if (error = VOP_OPEN(vnodep, FREAD, p->p_ucred, p)) > > return error; > > + > > + VOP_UNLOCK(vnodep); /* lock no longer needed */ > > > > error = vm_mmap(kernel_map, (vm_offset_t *)&a_out, 1024, > > VM_PROT_READ, VM_PROT_READ, 0, (caddr_t)vnodep, 0); > > > At the *absolute* least: > > if (error = VOP_OPEN(vnodep, FREAD, p->p_ucred, p)) { > VOP_UNLOCK(vnodep); /* lock no longer needed */ > return error; > } > > VOP_UNLOCK(vnodep); /* lock no longer needed */ > > Unfortunately, from context, I can't tell if there are other intervening > error returns or not. If so, they need the same change! You are, of course, correct.. This might be more appropriate: (sorry about the unidiff - but it shows the change much more clearly) As before, please don't commit this either until it's checked! --- linux_misc.c.dist Mon Jun 26 01:32:37 1995 +++ linux_misc.c Tue Jun 27 02:54:00 1995 @@ -188,7 +188,7 @@ printf("Linux-emul(%d): uselib(%s)\n", p->p_pid, path); #endif - NDINIT(&ni, LOOKUP, FOLLOW, UIO_SYSSPACE, path, p); + NDINIT(&ni, LOOKUP, FOLLOW | LOCKLEAF, UIO_SYSSPACE, path, p); if (error = namei(&ni)) return error; @@ -196,25 +196,39 @@ if (vnodep == NULL) return ENOEXEC; - if (vnodep->v_writecount) + if (vnodep->v_writecount) { + VOP_UNLOCK(vnodep); return ETXTBSY; + } - if (error = VOP_GETATTR(vnodep, &attr, p->p_ucred, p)) - return error; + if (error = VOP_GETATTR(vnodep, &attr, p->p_ucred, p)) { + VOP_UNLOCK(vnodep); + return error; + } if ((vnodep->v_mount->mnt_flag & MNT_NOEXEC) || ((attr.va_mode & 0111) == 0) - || (attr.va_type != VREG)) + || (attr.va_type != VREG)) { + VOP_UNLOCK(vnodep); return ENOEXEC; + } - if (attr.va_size == 0) + if (attr.va_size == 0) { + VOP_UNLOCK(vnodep); return ENOEXEC; + } - if (error = VOP_ACCESS(vnodep, VEXEC, p->p_ucred, p)) + if (error = VOP_ACCESS(vnodep, VEXEC, p->p_ucred, p)) { + VOP_UNLOCK(vnodep); return error; + } - if (error = VOP_OPEN(vnodep, FREAD, p->p_ucred, p)) + if (error = VOP_OPEN(vnodep, FREAD, p->p_ucred, p)) { + VOP_UNLOCK(vnodep); return error; + } + + VOP_UNLOCK(vnodep); /* lock no longer needed */ error = vm_mmap(kernel_map, (vm_offset_t *)&a_out, 1024, VM_PROT_READ, VM_PROT_READ, 0, (caddr_t)vnodep, 0); @@ -225,7 +239,7 @@ * Is it a Linux binary ? */ if (((a_out->a_magic >> 16) & 0xff) != 0x64) - return -1; + return ENOEXEC; /* * Set file/virtual offset based on a.out variant. @@ -240,7 +254,7 @@ file_offset = 0; break; default: - return (-1); + return ENOEXEC; } vnodep->v_flag |= VTEXT; Note that I've changed two "return -1"'s to "return ENOEXEC" - is that correct? The code appears to be designed to return an errno, and -1 doesn't appear right at first glance... Next question: should those be VOP_UNLOCK's (like in kern_exec.c) or vput() or vrele()? I think it probably needs a vput() instead of the VOP_UNLOCK() for all the cases before the error return, otherwise the reference counts are going to constantly increase. I suspect that after the VOP_UNLOCK (before the vm_mmap), all error returns probably need a vrele() first to clear the reference left by namei(). Is that about right? (the patch above does not do this - that's why it should not be committed). Comments? [Now, is this version going to eat my filesystem? Or just use up all my vnodes? :-)] Thanks Terry! (And a special thanks to Soren for letting the code out for public scrutiny like this!) -Peter From owner-freebsd-current Mon Jun 26 12:23:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA29588 for current-outgoing; Mon, 26 Jun 1995 12:23:23 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA29571 for ; Mon, 26 Jun 1995 12:22:53 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.11/8.6.9) with ESMTP id VAA03631; Mon, 26 Jun 1995 21:22:36 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.11/8.6.9) with SMTP id VAA14460; Mon, 26 Jun 1995 21:22:35 +0200 Message-Id: <199506261922.VAA14460@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: Garrett Wollman cc: Mark Murray , ache@astral.msk.su, current@freebsd.org Subject: Re: Crypt code summary(2). Date: Mon, 26 Jun 1995 21:22:34 +0200 From: Mark Murray Sender: current-owner@freebsd.org Precedence: bulk > >> Which I would be STRONGLY opposed to having in the source tree. > > > Why? You have voiced an opinion for another package (I cannot remember its > > name). Lets hear some argument for this. I would like _something_. > > 1. RSAREF is free for personal or corporate use under the > following conditions: > > o RSAREF, RSAREF applications, and services based on > RSAREF applications may not be sold. Does selling a `free' operating system for the distribution costs on CDROM count as `selling'? Is FreeBSD (as opposed to the CDROM) actually `sold'? (This question could easily sink to semantics, I know. Lets try to keep it sane. GNU may not be sold either. We have GNU. (Not much, and the license makes it a bit funny, but when you need it, you need it). > o You must give RSA the source code of any free RSAREF > application you plan to distribute or deploy within > your company. RSA will make these applications > available to the public, free of charge. What is the problem here? We _want_ to do this. We are going to do it anyway. > 4. You must use the interface described in the RSAREF > documentation. For European users, this does not kill RSAEURO. It is the same interface. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Mon Jun 26 12:36:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA00154 for current-outgoing; Mon, 26 Jun 1995 12:36:04 -0700 Received: from irbs.irbs.com (irbs.com [199.182.75.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA00147 for ; Mon, 26 Jun 1995 12:36:00 -0700 Received: (from jc@localhost) by irbs.irbs.com (8.6.11/8.6.6) id PAA12035; Mon, 26 Jun 1995 15:35:37 -0400 From: John Capo Message-Id: <199506261935.PAA12035@irbs.irbs.com> Subject: Re: mb_map full with GATEWAY and maxusers 64! To: tom@uniserve.com (Tom Samplonius) Date: Mon, 26 Jun 1995 15:35:36 -0400 (EDT) Cc: freebsd-current@freefall.cdrom.com (freebsd-current) In-Reply-To: from "Tom Samplonius" at Jun 26, 95 10:32:28 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: 1717 Sender: current-owner@FreeBSD.org Precedence: bulk Tom Samplonius writes: > > > On Mon, 26 Jun 1995, =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka Andrey A. Chernov, Black Mage wrote: > > > >I have seen it with maxusers at 48 and 96 on a lightly loaded system. > > >I switched to NMBCLUSTERS=2048 and have not seen it since. > > > > Maybe we need simple increase NMBCLUSTERS calculation as default to > > something like: > > > > #ifdef GATEWAY > > #define NMBCLUSTERS (2048 + maxusers * 16) > > #else > > #define NMBCLUSTERS (1024 + maxusers * 16) > > #endif > > > > Any opinions? > > I think that is too high. Most (all?) users that reported this problem > found that 2048 buffers cured it. Yet your calculcation would give these > users even more buffers that would likely be unneeded. > > As an alternative: > > - document NMBCLUSTERS in LINT (as of 2.0.5R, this still wasn't mentioned) > - include a explicit "options NMBCLUSTERS" line in the GENERIC kernel, > with then note that "mb_map" full indicates that you've run out these buffers > > I would just prefer that this just be documented rather than to bury the > calculation somewhere. > I agree with Tom here. But, it seems to me that there is an underlying problem of some sort. Why do I have to allow for 4Megs of mbuf clusters to service some unknown transient event. Once this memory is in the mbuf map, its there forever. Is this a valid way to examine a running kernel? It appears that it is. gdb -k kernel /dev/mem (kgdb) p mbstat $4 = {m_mbufs = 0, m_clusters = 38, m_spare = 0, m_clfree = 30, m_drops = 0, m_wait = 0, m_drain = 0, m_mtypes = {0, 8, 3, 0, 23, 0, 0, 0, 8, 0 }} (kgdb) p nmbclusters $5 = 2048 (kgdb) -- John Capo From owner-freebsd-current Mon Jun 26 13:03:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA01706 for current-outgoing; Mon, 26 Jun 1995 13:03:09 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA01695 for ; Mon, 26 Jun 1995 13:03:02 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA18934; Mon, 26 Jun 1995 16:01:25 -0400 Date: Mon, 26 Jun 1995 16:01:25 -0400 From: Garrett Wollman Message-Id: <9506262001.AA18934@halloran-eldar.lcs.mit.edu> To: Mark Murray Cc: Garrett Wollman , ache@astral.msk.su, current@freebsd.org Subject: Re: Crypt code summary(2). In-Reply-To: <199506261922.VAA14460@grumble.grondar.za> References: <199506261922.VAA14460@grumble.grondar.za> Sender: current-owner@freebsd.org Precedence: bulk < said: >> o RSAREF, RSAREF applications, and services based on >> RSAREF applications may not be sold. > Does selling a `free' operating system for the distribution costs on CDROM > count as `selling'? Yes. b. The Program may not be used directly for revenue-generating purposes. You may not: (i) use the Program to provide services to others for which you are compensated in any manner; (ii) license or otherwise distribute any Application Program in any manner that generates income to you, including without limitation any income on account of license fees, royalties, maintenance fees and upgrade fees; and (iii) license or otherwise distribute any Application Program without the express written acknowledgment of the end user that the Program will not be used in connection with any revenue-generating activity of the end user. Nothing in this paragraph prohibits you from using the Program or any Application Program solely for internal purposes on the premises of a business which is engaged in revenue-generating activities. Section (iii) is the killer. > GNU may not be sold either. We have GNU. (Not much, and the license makes it > a bit funny, but when you need it, you need it). This is simply not true. Anyone is welcome to sell GNU programs, they simply have to give away the source. Walnut Creek sells GNU programs; see pages 33 and 34 of the Spring '95 catalog. [Unless you are in the free software distribution business, it is hard to develop a business plan that works with this model. Of course, that was the FSF's intention in the first place.] >> o You must give RSA the source code of any free RSAREF >> application you plan to distribute or deploy within >> your company. RSA will make these applications >> available to the public, free of charge. > What is the problem here? We _want_ to do this. We are going to do it anyway. Note the way this paragraph is written. It is not sufficient to simply make a program available so RSA can grab it; every single time you commit a modification to any client program, you (or someone in the US) must send it to RSADSI. The mrouted license is similar, but we're OK because all our changes come from the developers. >> 4. You must use the interface described in the RSAREF >> documentation. > For European users, this does not kill RSAEURO. It is the same interface. The point was that this license doesn't allow arbitrary use of the software components, as does every other piece of software in FreeBSD. It is illegal in the US to compile a program which calls the internal interfaces of RSAREF, regardless of whether you intend to distribute it or not. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Mon Jun 26 13:38:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA03516 for current-outgoing; Mon, 26 Jun 1995 13:38:12 -0700 Received: from forgery.CS.Berkeley.EDU (forgery.CS.Berkeley.EDU [128.32.33.75]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA03510 for ; Mon, 26 Jun 1995 13:38:11 -0700 Received: (from asami@localhost) by forgery.CS.Berkeley.EDU (8.6.11/8.6.9) id NAA02663; Mon, 26 Jun 1995 13:38:02 -0700 Date: Mon, 26 Jun 1995 13:38:02 -0700 Message-Id: <199506262038.NAA02663@forgery.CS.Berkeley.EDU> To: peter@haywire.DIALix.COM CC: rgrimes@gndrsh.aac.dev.com, current@freebsd.org In-reply-to: (message from Peter Wemm on Tue, 27 Jun 1995 01:34:50 +0800 (WST)) Subject: Re: when is the supscan done? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: current-owner@freebsd.org Precedence: bulk * > > I think somebody mentioned 9am local time at one point... * > * > I mentioned 9am, and that was just because I knew that would be the * > next run of the job. They run at: * > 0 1,7,13,19 * * * root /root/bin/update_usrall I'm not sure how to interpret your sentence, but if you mean the 7am one will have finished by 9am, I disagree. The 1am one usually doesn't finish until way after 3am these days. Satoshi From owner-freebsd-current Mon Jun 26 15:25:41 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA09631 for current-outgoing; Mon, 26 Jun 1995 15:25:41 -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 PAA09621 for ; Mon, 26 Jun 1995 15:25:38 -0700 Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id PAA05572; Mon, 26 Jun 1995 15:25:33 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id PAA17617; Mon, 26 Jun 1995 15:26:00 -0700 Message-Id: <199506262226.PAA17617@corbin.Root.COM> To: John Capo cc: tom@uniserve.com (Tom Samplonius), freebsd-current@freefall.cdrom.com (freebsd-current) Subject: Re: mb_map full with GATEWAY and maxusers 64! In-reply-to: Your message of "Mon, 26 Jun 95 15:35:36 EDT." <199506261935.PAA12035@irbs.irbs.com> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 26 Jun 1995 15:25:58 -0700 Sender: current-owner@FreeBSD.org Precedence: bulk >I agree with Tom here. But, it seems to me that there is an >underlying problem of some sort. Why do I have to allow for 4Megs >of mbuf clusters to service some unknown transient event. Once >this memory is in the mbuf map, its there forever. Well, the usage is a function of the number of TCP connections. If you do a "netstat" and find a whole pile of connections (even ones in a closing state), then this explains it. This can easily happen to people using HTTP. >Is this a valid way to examine a running kernel? It appears that >it is. I suppose, but "netstat -m" should provide you with enough information. -DG From owner-freebsd-current Mon Jun 26 16:37:30 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA20803 for current-outgoing; Mon, 26 Jun 1995 16:37:30 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id QAA20795 ; Mon, 26 Jun 1995 16:37:28 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA00700; Mon, 26 Jun 95 17:30:28 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506262330.AA00700@cs.weber.edu> Subject: Re: bug in Linux^H^H^H^H^HDoom Emulator To: peter@haywire.DIALix.COM (Peter Wemm) Date: Mon, 26 Jun 95 17:30:27 MDT Cc: current@freebsd.org, sos@freebsd.org In-Reply-To: from "Peter Wemm" at Jun 27, 95 03:16:58 am X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@freebsd.org Precedence: bulk > > On Mon, 26 Jun 1995, Terry Lambert wrote: > > > > vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv > > DO NOT COMMIT THIS WITHOUT FURTHER CHANGES! > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Seconded! :-) [ ... patches dealing with error returns ... ] > Note that I've changed two "return -1"'s to "return ENOEXEC" - is that > correct? The code appears to be designed to return an errno, and -1 > doesn't appear right at first glance... I can't comment without more source... you'd have to exercise the condition and see if you get what you expected as an error without a full code path. My impression is that -1 is probably correct. > Next question: should those be VOP_UNLOCK's (like in kern_exec.c) or > vput() or vrele()? OK, this whole discussion is starting to become an argument for single entry/single exit of functions. 8-). Again, without more context (like the expected lock state in/out of the locking function) I can't tell at a casual glance whether or not the the count is bumped. Actually, I expect that it is not, though that could be a problem for the SMP work. > I think it probably needs a vput() instead of the VOP_UNLOCK() for all > the cases before the error return, otherwise the reference counts are > going to constantly increase. I suspect that after the VOP_UNLOCK (before > the vm_mmap), all error returns probably need a vrele() first to clear > the reference left by namei(). Is that about right? (the patch above > does not do this - that's why it should not be committed). Ugh. Looks like someone needs to run through the VFS and UFS code and clean up entry/exit state information. The whole FS source base is looking uglier and uglier. 8-(. > Comments? [Now, is this version going to eat my filesystem? Or just use > up all my vnodes? :-)] The net effect is that the FS will not unmount after a failed reference if in fact the reference count is incremented by the lookup. Incrementing it at the lookup is the correct thing to do for SMP (in case of real or effective kernel preemption) to prevent the thing from being incorrectly discarded by one processor in the midst of use by another. The question is if this is correct for SMP or preemption safe or simply unsafe for reentry -- in which case it's not bumping the count. You need to go into the routine that returns the locked node to be sure. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jun 26 16:43:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA21420 for current-outgoing; Mon, 26 Jun 1995 16:43:46 -0700 Received: from whisker.internet-eireann.ie (whisker.internet-eireann.ie [194.9.34.204]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA21389 ; Mon, 26 Jun 1995 16:43:31 -0700 Received: from localhost (localhost [127.0.0.1]) by whisker.internet-eireann.ie (8.6.11/8.6.9) with SMTP id AAA02306; Tue, 27 Jun 1995 00:43:58 +0100 To: terry@cs.weber.edu (Terry Lambert) cc: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes), phk@freefall.cdrom.com, mark@grondar.za, wollman@halloran-eldar.lcs.mit.edu, current@freebsd.org Subject: Re: Crypt code summary(2). In-reply-to: Your message of "Mon, 26 Jun 1995 12:47:47 MDT." <9506261847.AA28600@cs.weber.edu> Date: Tue, 27 Jun 1995 00:43:57 +0100 Message-ID: <2304.804210237@whisker.internet-eireann.ie> From: "Jordan K. Hubbard" Sender: current-owner@freebsd.org Precedence: bulk > FreeBSD seems uninterested because they feel they can simply dictate > the future of BSD because of their technological enhancements in the > area of installation, VM, and commodity hardware coverage have > resulted in them being more palletable to a larger user base. They > point to the number of messages in the FreeBSD news groups being > larger than the twice number of messages in the NetBSD and BSD > groups combined as evidence of their success. > ... > Other than that, everyone agrees it's a good idea, but no one wants > to make it their part time job, even though it could be a paid job, > given that non-profit corporations still have paid employees. > ... > > As for me: ideas aren't a problem; time to implement them all *is* a > problem. I can think of many, many ways someone can make their I think you've come closer to determining the REAL reason why none of us have jumped on the bandwagon. I don't dispute that a number of us are proud of the size of our user base, but I don't think we're quite so arrogant (at least *I'm* not) as to assume that we can "dictate" anything to the BSD community at large. It all simply comes down to time. I'd like to get 2.1R out the door, write a book, do some magazine articles, go give one of the keynote speeches in Australia this August and possibly one in Japan later this summer, have a life for about 5 minutes on July 29th, etc. etc. Where in all of that am I supposed to fit in the riding of the mechanical bull that getting seriously involved in a BSD Consortium would entail? The answer is: I can't. Getting behind this effort would be a big job and a high-voltage wire to be grabbing on to, and I just don't have the time, nor does anyone else I know. It's not arrogance, it's exhaustion! So if you want to front such an organization, please feel free! But don't talk to me about how YOU are maxed out and then in the same breath imply that our own lack of willingness comes from arrogance of our position and not simply a similar level of over-committment. You're full of ideas, Terry, but you're also far too willing to sign other people up for things you're not willing to commit to yourself. Kindly stop! You're not helping things and the impression you end up giving is that of someone who likes the sound of his own voice (or typing? :-) but always has a convenient excuse when the REAL work or committment is called for. Enough with the feeble excuses! We've heard them all by now! Put up or shut up, PUH-LEEZE! :-) Thank you! Jordan From owner-freebsd-current Mon Jun 26 16:49:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA22092 for current-outgoing; Mon, 26 Jun 1995 16:49:57 -0700 Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id QAA22073 for ; Mon, 26 Jun 1995 16:49:52 -0700 Received: by sequent.kiae.su id AA25958 (5.65.kiae-2 ); Tue, 27 Jun 1995 03:48:02 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Tue, 27 Jun 95 03:48:01 +0400 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id DAA02513; Tue, 27 Jun 1995 03:39:57 +0400 To: davidg@Root.COM, John Capo Cc: freebsd-current , Tom Samplonius References: <199506262226.PAA17617@corbin.Root.COM> In-Reply-To: <199506262226.PAA17617@corbin.Root.COM>; from David Greenman at Mon, 26 Jun 1995 15:25:58 -0700 Message-Id: Organization: Olahm Ha-Yetzirah Date: Tue, 27 Jun 1995 03:39:56 +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: Re: mb_map full with GATEWAY and maxusers 64! Lines: 21 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 1042 Sender: current-owner@FreeBSD.org Precedence: bulk In message <199506262226.PAA17617@corbin.Root.COM> David Greenman writes: >>I agree with Tom here. But, it seems to me that there is an >>underlying problem of some sort. Why do I have to allow for 4Megs >>of mbuf clusters to service some unknown transient event. Once >>this memory is in the mbuf map, its there forever. > Well, the usage is a function of the number of TCP connections. If you do a >"netstat" and find a whole pile of connections (even ones in a closing state), >then this explains it. This can easily happen to people using HTTP. I wonder why it happens on my host, as I already said, user activity was very low, and I am not running HTTP/anon FTP/IRCD/NFSD or other network-consume daemons, just plain routed+named. -- 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 Mon Jun 26 18:24:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA00181 for current-outgoing; Mon, 26 Jun 1995 18:24:24 -0700 Received: from westhill.cdrom.com (westhill.cdrom.com [192.216.223.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA00173 ; Mon, 26 Jun 1995 18:24:22 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by westhill.cdrom.com (8.6.11/8.6.11) with SMTP id SAA23228 ; Mon, 26 Jun 1995 18:24:05 -0700 X-Authentication-Warning: westhill.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: "Rodney W. Grimes" cc: peter@haywire.DIALix.COM (Peter Wemm), current@freebsd.org, jmb@freebsd.org Subject: Re: when is the supscan done? In-reply-to: Your message of "Mon, 26 Jun 1995 10:55:49 PDT." <199506261755.KAA04885@gndrsh.aac.dev.com> Date: Mon, 26 Jun 1995 18:24:05 -0700 Message-ID: <23226.804216245@westhill.cdrom.com> From: Gary Palmer Sender: current-owner@freebsd.org Precedence: bulk In message <199506261755.KAA04885@gndrsh.aac.dev.com>, "Rodney W. Grimes" write s: >Right now this just goes out to the root: alias in /etc/sendmail.cf, >but that can be changed pretty easily. They also contain a lot more info than I think people want to see... (and the root alias is in /etc/aliases, not sendmail.cf :-) ) Perhaps we should split the cvs update's off somehow to enable the supscan's to still go to root? Gary From owner-freebsd-current Mon Jun 26 18:30:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA00567 for current-outgoing; Mon, 26 Jun 1995 18:30:29 -0700 Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA00561 for ; Mon, 26 Jun 1995 18:30:25 -0700 Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.11/8.6.9) id VAA02111 for freebsd-current@freebsd.org; Mon, 26 Jun 1995 21:30:05 -0400 From: A boy and his worm gear Message-Id: <199506270130.VAA02111@skynet.ctr.columbia.edu> Subject: Proposal for mountd change To: freebsd-current@freebsd.org Date: Mon, 26 Jun 1995 21:30:01 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1793 Sender: current-owner@freebsd.org Precedence: bulk Hello there: Not too long ago, somebody sent a message to the bugs list about a problem using a FreeBSD machine as a boot server for a diskless Sun client. The problem is that Suns try to directly mount their swap devices as plain files rather than mounting the filesystem containing the swap file and then getting a file handle for the swap file once the mount of the filesystem has succeeded. As it happens, mountd is designed (yes David G., the word is designed, not 'architected' -- there's no such word as 'architected') to check the mount path supplied by the client and reject anything that isn't a directory, including plain files. This makes it impossible to use FreeBSD to completely support diskless booting of SunOS 4.x machines (I'm not sure if Solaris 2.x has the same requirements). Anyway, I'd like to find a way around this. I'm wondering if it would be possible to add a run-time option to mountd to loosen the 'directories only' restriction to include plain files. This is just an idea at this point -- I haven't had the chance to test it. I'm not even certain that twisting mountd's arm is the only thing that's required. Suggestions or comments would be appreciated. I'll have a chance to test this notion sometime this coming weekend. -Bill -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~T~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Bill Paul (212) 854-6020 | System Manager Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The Møøse Illuminati: ignore it and be confused, or join it and be confusing! ~~~~~~ "Welcome to All Things BSDish! If it's not BSDish, it's crap!" ~~~~~~~ From owner-freebsd-current Mon Jun 26 18:53:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA01077 for current-outgoing; Mon, 26 Jun 1995 18:53:25 -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 SAA01057 for ; Mon, 26 Jun 1995 18:53:13 -0700 Received: by haven.uniserve.com id <30757>; Mon, 26 Jun 1995 18:53:43 +0100 Date: Mon, 26 Jun 1995 18:53:09 -0700 (PDT) From: Tom Samplonius To: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka Andrey A. Chernov, Black Mage" cc: freebsd-current Subject: Re: mb_map full with GATEWAY and maxusers 64! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Tue, 27 Jun 1995, =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka Andrey A. Chernov, Black Mage wrote: > I wonder why it happens on my host, as I already said, user activity > was very low, and I am not running HTTP/anon FTP/IRCD/NFSD or other > network-consume daemons, just plain routed+named. named can be pretty intensive. I just read a report of someone running out of mbufs running bind-4.9.3-BETA21 on a SunOS 4.1.3 system. Tom From owner-freebsd-current Mon Jun 26 19:02:33 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA01279 for current-outgoing; Mon, 26 Jun 1995 19:02:33 -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 TAA01266 for ; Mon, 26 Jun 1995 19:02:22 -0700 Received: by haven.uniserve.com id <30747>; Mon, 26 Jun 1995 19:02:51 +0100 Date: Mon, 26 Jun 1995 19:02:44 -0700 (PDT) From: Tom Samplonius To: John Capo cc: freebsd-current Subject: Re: mb_map full with GATEWAY and maxusers 64! In-Reply-To: <199506261935.PAA12035@irbs.irbs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Mon, 26 Jun 1995, John Capo wrote: > I agree with Tom here. But, it seems to me that there is an > underlying problem of some sort. Why do I have to allow for 4Megs > of mbuf clusters to service some unknown transient event. Once > this memory is in the mbuf map, its there forever. Running out mbufs doesn't kill your system. It just means that you drop a few packets. Only if it happens continuously is it a problem Tom From owner-freebsd-current Mon Jun 26 19:42:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA02890 for current-outgoing; Mon, 26 Jun 1995 19:42:04 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id TAA02883 ; Mon, 26 Jun 1995 19:42:01 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA01284; Mon, 26 Jun 95 20:35:08 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506270235.AA01284@cs.weber.edu> Subject: Re: Crypt code summary(2). To: jkh@freebsd.org (Jordan K. Hubbard) Date: Mon, 26 Jun 95 20:35:07 MDT Cc: rgrimes@gndrsh.aac.dev.com, phk@freefall.cdrom.com, mark@grondar.za, wollman@halloran-eldar.lcs.mit.edu, current@freebsd.org In-Reply-To: <2304.804210237@whisker.internet-eireann.ie> from "Jordan K. Hubbard" at Jun 27, 95 00:43:57 am X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@freebsd.org Precedence: bulk [ ... Re: Consortium ... ] > So if you want to front such an organization, please feel free! But > don't talk to me about how YOU are maxed out and then in the same > breath imply that our own lack of willingness comes from arrogance of > our position and not simply a similar level of over-committment. That's not what I implied. I implied a lack of interest, not "interest but a lack of willingness". Arrogance is another topic entirely, and the failure attributable to it is names "Merge", not "Consortium" (and no, I'm not *willing* to go down that thread again). > You're full of ideas, Terry, but you're also far too willing to sign > other people up for things you're not willing to commit to yourself. I agree with this, to an extent. I can name some examples quite close to home: the original 386BSD FAQ and patchkit, both of which I foisted off on the first willing/unsuspecting people to come along who stood a chance (IMO) of keeping it going at the right level. > Kindly stop! You're not helping things and the impression you end up > giving is that of someone who likes the sound of his own voice (or > typing? :-) I don't think that's it. I am unlikely to keep opinions to myself. > but always has a convenient excuse when the REAL work or > committment is called for. Enough with the feeble excuses! We've > heard them all by now! Put up or shut up, PUH-LEEZE! :-) Well, Rod is burning in my dual processor P90 right now (ask him if you don't believe me). Feel free to ask Jeffrey Hsu what is currently going on with him, if he's willing to comment. Feel free to ask Sean Eric Fagan what joint project we have up our sleeves, though I'd rather it not be made too public right now. I just barely finished reviewing someone else's manuscript for Prentice Hall; it was a much more time consuming job than I had expected. Naerly 6 Months of free time; expect to see the book "UNIX Internals: The New Frontiers" in bookstores soon. I highly recommend it for its comparative look at many UNIX implementations. I'm about to take my first real vacation in about two years (not that I won't stay net connected) and expect to be updating some Nucleotide Visualization software I put together for a couple of genetecists doing Human Genome Project work. I expect I'll be asked to help move over some relativistically invariant pair production simulation software I volunteered time on occasionally over the last 10-12 years (it was just recently used to locate the energy range for the carrier of the weak force). So even on vacation, I expect to stay quite busy. Meanwhile, Sean has seen one pre-release game of several, and everyone on the FreeBSD Core and XFree86 mailing lists at least had opportunity (even if they didn't exercise it) to see the first Alpha of Mimic, my Motif library clone. So I think I have "put up" quite a bit. On the other hand, places where I do only make comments, you can be sure I have some sort of code concern or another in mind. Just because I don't think something is release quality doesn't mean it's not there -- rememeber when I shipped off the pre-alpha for LKM? It had Sun copyright manual pages I was using to figure options at the end of the utility source files, and it took two months for them to be removed. On top of that, since the "console team" needed the LKM code, I rushed it in favor of other projects. Less than a week later, Novell bought USL and much of my code that was nearly ready to go (like shared libraries using Jeffrey Hsu's PIC mods to GCC and GNU asm) got delayed. Much of it to the point that it was obviated (by another shared library implementation a year later for shared libs) or obsoleted by massive and sometimes gratuitous interface changes (like my Streams implementation). I'd like to avoid providing opportunity for that kind of screwup again, thank you. Yes, I take a hundred paths at once; that doesn't mean I never reach the end of any of them. Have some frigging patience! I haven't been in a position to *do* anything, first because of Novell, and then for lack of equipment and all my free time going to book reviewing (all three of which should finally be remedied around the 10th of July). Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jun 26 20:31:20 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA04515 for current-outgoing; Mon, 26 Jun 1995 20:31:20 -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 UAA04508 for ; Mon, 26 Jun 1995 20:31:18 -0700 Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id UAA05934; Mon, 26 Jun 1995 20:31:12 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id UAA17759; Mon, 26 Jun 1995 20:31:41 -0700 Message-Id: <199506270331.UAA17759@corbin.Root.COM> To: Tom Samplonius cc: John Capo , freebsd-current Subject: Re: mb_map full with GATEWAY and maxusers 64! In-reply-to: Your message of "Mon, 26 Jun 95 19:02:44 PDT." From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 26 Jun 1995 20:31:40 -0700 Sender: current-owner@FreeBSD.org Precedence: bulk > >On Mon, 26 Jun 1995, John Capo wrote: > >> I agree with Tom here. But, it seems to me that there is an >> underlying problem of some sort. Why do I have to allow for 4Megs >> of mbuf clusters to service some unknown transient event. Once >> this memory is in the mbuf map, its there forever. > > Running out mbufs doesn't kill your system. It just means that you >drop a few packets. Only if it happens continuously is it a problem Prior to 2.0.5R, it did kill the system. -DG From owner-freebsd-current Mon Jun 26 20:37:59 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA04713 for current-outgoing; Mon, 26 Jun 1995 20:37: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 UAA04707 for ; Mon, 26 Jun 1995 20:37:56 -0700 Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id UAA05944; Mon, 26 Jun 1995 20:37:50 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id UAA17779; Mon, 26 Jun 1995 20:38:18 -0700 Message-Id: <199506270338.UAA17779@corbin.Root.COM> To: A boy and his worm gear cc: freebsd-current@freebsd.org Subject: Re: Proposal for mountd change In-reply-to: Your message of "Mon, 26 Jun 95 21:30:01 EDT." <199506270130.VAA02111@skynet.ctr.columbia.edu> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 26 Jun 1995 20:38:17 -0700 Sender: current-owner@freebsd.org Precedence: bulk >swap file once the mount of the filesystem has succeeded. As it >happens, mountd is designed (yes David G., the word is designed, >not 'architected' -- there's no such word as 'architected') to check How/why did I deserve this jab? -DG From owner-freebsd-current Mon Jun 26 21:24:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA05582 for current-outgoing; Mon, 26 Jun 1995 21:24:45 -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 VAA05576 ; Mon, 26 Jun 1995 21:24:42 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA11210; Tue, 27 Jun 1995 06:24:39 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id GAA17048; Tue, 27 Jun 1995 06:24:38 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id AAA24998; Tue, 27 Jun 1995 00:43:13 +0200 From: J Wunsch Message-Id: <199506262243.AAA24998@uriah.heep.sax.de> Subject: Re: pine To: lix@cs.pdx.edu (xiaoyin li) Date: Tue, 27 Jun 1995 00:43:13 +0200 (MET DST) Cc: current@FreeBSD.ORG, question@FreeBSD.ORG In-Reply-To: <199506261823.LAA01591@cs.pdx.edu> from "xiaoyin li" at Jun 26, 95 11:23:28 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: 804 Sender: current-owner@FreeBSD.ORG Precedence: bulk As xiaoyin li wrote: > > > > I would appreciate very much if someone can tell me how to make "pine" software > work on FreeBSD April SNAP system. > > I coped files from ftp public domain: > /pub5/freebsd/FreeBSD-current/ports/mail/pine > > I also copied pine3.91 software from: > Host: ftp.cac.washington.edu > > My question is how can I compile pine3.91 successfully with above files > on my FreeBSD? Put the pine `port' files under e.g. /usr/ports/mail/pine/. Put the pine tar.gz file (assuming it's the version as required by the Makefile) into /usr/ports/distfiles/. cd /usr/ports/mail/pine/; make should do the trick. -- 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 Jun 26 22:45:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA07390 for current-outgoing; Mon, 26 Jun 1995 22:45:36 -0700 Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA07383 for ; Mon, 26 Jun 1995 22:45:32 -0700 Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.11/8.6.9) id BAA02424; Tue, 27 Jun 1995 01:45:06 -0400 From: A boy and his worm gear Message-Id: <199506270545.BAA02424@skynet.ctr.columbia.edu> Subject: Re: Proposal for mountd change To: davidg@Root.COM Date: Tue, 27 Jun 1995 01:45:03 -0400 (EDT) Cc: freebsd-current@freebsd.org In-Reply-To: <199506270338.UAA17779@corbin.Root.COM> from "David Greenman" at Jun 26, 95 08:38:17 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1467 Sender: current-owner@freebsd.org Precedence: bulk Of all the gin joints in all the world, David Greenman had to walk into mine and say: > > >swap file once the mount of the filesystem has succeeded. As it > >happens, mountd is designed (yes David G., the word is designed, > >not 'architected' -- there's no such word as 'architected') to check > > How/why did I deserve this jab? > > -DG > It's not you I was jabbing; it's 'architected.' It stands out in my mind as a manufactured marketing term maquerading as a real word, and it's one that I heard (and read) far too many times at PC Expo last week. Now I grit my teeth whenever anyone says it. Of course, by that same token, I'm guilty of plenty of similar offenses. Even though I try to avoid it, I occasionally catch myself saying things like 'interoperability' and 'connectivity' which don't exist in the dictionary either. Maybe someday we'll have English++ where words will be able to supply their own definitions. :) -Bill -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~T~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Bill Paul (212) 854-6020 | System Manager Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The Møøse Illuminati: ignore it and be confused, or join it and be confusing! ~~~~~~ "Welcome to All Things BSDish! If it's not BSDish, it's crap!" ~~~~~~~ From owner-freebsd-current Mon Jun 26 23:25:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA09039 for current-outgoing; Mon, 26 Jun 1995 23:25:52 -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 XAA09027 ; Mon, 26 Jun 1995 23:25:47 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id XAA05754; Mon, 26 Jun 1995 23:25:50 -0700 From: "Rodney W. Grimes" Message-Id: <199506270625.XAA05754@gndrsh.aac.dev.com> Subject: Re: Crypt code summary(2). To: terry@cs.weber.edu (Terry Lambert) Date: Mon, 26 Jun 1995 23:25:50 -0700 (PDT) Cc: phk@freefall.cdrom.com, mark@grondar.za, wollman@halloran-eldar.lcs.mit.edu, current@freebsd.org In-Reply-To: <9506261847.AA28600@cs.weber.edu> from "Terry Lambert" at Jun 26, 95 12:47:47 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: 3946 Sender: current-owner@freebsd.org Precedence: bulk > > > > Yes. It was offered on the basis that it be used to form a BSD Consortium. > > > > Well, since you are the one who always pushes the BSD Consortium, can > > you tell me how the formation of it is going :-) :-) :-0 > > BSDI seems uninterested because they feel they can simply dictate > the future of BSD because their strong historical ties to CSRG have > resulted in them being the sole recognized authorities. They also > have almost total control of the BSD commercial software effort > and therefore can dictate the ABI. See all the stuff going on in FSSTND, I don't think they are in the ``dictating'' position on that one, and are already willing to bend quite far in a cooperative effort to make this thing a reality for Linux, FreeBSD and BSDI (at least, and evidently NetBSD is just going to wait for the next draft and then decide (fools, IMHO, but what ever). > NetBSD seems uninterested because they feel they can simply dictate > the future of BSD because their porting efforts have resulted in > them being uniquely suited to taking all the architectural issues > into account in their source base. Their ABI compatability efforts > have given them access to the commercial software on each ported > platform, at least to a limited extent, and they feel they will > displace the commercial OS's. I am not allowed to speek for NetBSD, so ``no comment'' :-) > > FreeBSD seems uninterested because they feel they can simply dictate > the future of BSD because of their technological enhancements in the > area of installation, VM, and commodity hardware coverage have > resulted in them being more palletable to a larger user base. They > point to the number of messages in the FreeBSD news groups being > larger than the twice number of messages in the NetBSD and BSD > groups combined as evidence of their success. I for one, as a core team member, am *very* interested in seeing an attempt to do this. Especially in lite of the recent cooperative effort that is occuring between the Linux, BSDI, and FreeBSD camps. > Linux seems uninterested because they feel they can simply dictate > the use of Linux instead by subverting public BSD channels into Linux > advocacy groups. You will be assimilated. They have a magazine. 8-|. This is hog wash and you darn well know it. They have already agreed to adopt whole sale pretty much the BSD way of doing /usr/share, and are willing to follow *BSD in the architectual indepenedence areas. > Other than that, everyone agrees it's a good idea, but no one wants > to make it their part time job, even though it could be a paid job, > given that non-profit corporations still have paid employees. I doubt very much that it could afford to pay my normal rate, but I would do this ``part time job'' for 1/2 of my normal rate if that is what it takes to get you rolling on this. > Sort of the same as is true for a "BSD Journal" (though given the > Linux success in this area, that could go full-time easily). > > As for me: ideas aren't a problem; time to implement them all *is* a > problem. I think that time is the *whole* problem, and none of what you said is much of the problem at all. > I can think of many, many ways someone can make their > own job. On the effort vs. return scale, I'm doing close to the > maximum edge on the curve, and don't have much time for following > much else. I make intentional exceptions for things I think will > advance the state of the art in various areas, but that's more as > long term investments in the future than anything else (and the only > things most of you see are computer science related). > > > Terry Lambert > terry@cs.weber.edu > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Mon Jun 26 23:55:03 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA10711 for current-outgoing; Mon, 26 Jun 1995 23:55:03 -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 XAA10702 for ; Mon, 26 Jun 1995 23:54:59 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id XAA05823; Mon, 26 Jun 1995 23:54:04 -0700 From: "Rodney W. Grimes" Message-Id: <199506270654.XAA05823@gndrsh.aac.dev.com> Subject: Re: Crypt code summary(2). To: mark@grondar.za (Mark Murray) Date: Mon, 26 Jun 1995 23:54:04 -0700 (PDT) Cc: wollman@halloran-eldar.lcs.mit.edu, mark@grondar.za, ache@astral.msk.su, current@freebsd.org In-Reply-To: <199506261922.VAA14460@grumble.grondar.za> from "Mark Murray" at Jun 26, 95 09:22:34 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: 2671 Sender: current-owner@freebsd.org Precedence: bulk > > > >> Which I would be STRONGLY opposed to having in the source tree. > > > > > Why? You have voiced an opinion for another package (I cannot remember its > > > name). Lets hear some argument for this. I would like _something_. > > > > 1. RSAREF is free for personal or corporate use under the > > following conditions: > > > > o RSAREF, RSAREF applications, and services based on > > RSAREF applications may not be sold. > > Does selling a `free' operating system for the distribution costs on CDROM > count as `selling'? Walnut Creek is selling these CDROM's high about what would be considered ``distribution costs''. They _are_ a for profit company, and do make a profit!! > Is FreeBSD (as opposed to the CDROM) actually `sold'? (This question could > easily sink to semantics, I know. Lets try to keep it sane. Yes, it is sold, some times even for more than you would ever think possible. > GNU may not be sold either. We have GNU. (Not much, and the license makes it > a bit funny, but when you need it, you need it). Nothing in the GNU license says you can't sell GNU binaries, heck RTR software makes a full time profitable business compiling and selling GNU binaries. It simply says you have to provide the sources at cost of distribution, but it says nothing about what you can make for profit from building BINARIES!!! > > o You must give RSA the source code of any free RSAREF > > application you plan to distribute or deploy within > > your company. RSA will make these applications > > available to the public, free of charge. > > What is the problem here? We _want_ to do this. We are going to do it anyway. You are *NOT* going to make RSA part of the FreeBSD source tree, no how, no way, nodda, forget it, it is way way way to much legalize involved with even touching RSA code in the USA!!!! You think the State Department and DES is a pain, wait until you see what a company that holds a patent on something you are using can do to you for screwing around with it! I don't want to put FreeBSD or Walnut Creek in that possition, nor would I want any person buying FreeBSD to be put into that possition. Do it as a port, period. Garrett is right on this one, and I am going to back him up 100%. > > > 4. You must use the interface described in the RSAREF > > documentation. > > For European users, this does not kill RSAEURO. It is the same interface. > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Tue Jun 27 00:11:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA11315 for current-outgoing; Tue, 27 Jun 1995 00:11:23 -0700 Received: from whisker.internet-eireann.ie (whisker.internet-eireann.ie [194.9.34.204]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA11292 ; Tue, 27 Jun 1995 00:11:07 -0700 Received: from localhost (localhost [127.0.0.1]) by whisker.internet-eireann.ie (8.6.11/8.6.9) with SMTP id IAA06422; Tue, 27 Jun 1995 08:11:41 +0100 To: terry@cs.weber.edu (Terry Lambert) cc: jkh@freebsd.org (Jordan K. Hubbard), rgrimes@gndrsh.aac.dev.com, phk@freefall.cdrom.com, mark@grondar.za, wollman@halloran-eldar.lcs.mit.edu, current@freebsd.org Subject: Re: Crypt code summary(2). In-reply-to: Your message of "Mon, 26 Jun 1995 20:35:07 MDT." <9506270235.AA01284@cs.weber.edu> Date: Tue, 27 Jun 1995 08:11:40 +0100 Message-ID: <6420.804237100@whisker.internet-eireann.ie> From: "Jordan K. Hubbard" Sender: current-owner@freebsd.org Precedence: bulk > That's not what I implied. I implied a lack of interest, not "interest > but a lack of willingness". That's not what your little summary of all the groups's "motivation" (or lack thereof) implied to me, but we can skip it. It's not worth arguing over, truly. > Arrogance is another topic entirely, and the failure attributable to > it is names "Merge", not "Consortium" (and no, I'm not *willing* to > go down that thread again). I'm glad of that because I'd argue that point as well.. :-) I said it many times, both during and after those proceedings: If there was any way for the parties to work together without tearing BOTH groups apart through internal strife and an inherent inability to even like each other, much less work together, then we'd have done it. Everyone on the outside was, in turn, pushing like some sort of demented Hedda Gabbler style match-maker who just couldn't believe that her pairing up of the Grand Dragon of the Klu-Klux-Klan and Whitney Houston wasn't going to work out. "But with his organizational abilities and her voice, it would be a match made in heaven!" she continued to gush. "What's a little difference in politics got to do with anything?" Arrogance really didn't enter into it, and it's really overly simplistic of you to think that it did. These are volunteers here Terry, in case you've forgotten. You can't get the Moose Lodge to meet every saturday for drinks and socialization if they all hate one another's guts. I never could figure out how everyone found this so bloody hard to understand at the time. Must have been something in the water. [And before you even think it, we didn't fail to get along simply due to being "rivals" and it wouldn't take Sigmund Freud to quickly ascertain that the two groups of people simply have SERIOUSLY divergent styles and age groupings]. > I agree with this, to an extent. I can name some examples quite close > to home: the original 386BSD FAQ and patchkit, both of which I foisted > off on the first willing/unsuspecting people to come along who stood a > chance (IMO) of keeping it going at the right level. And the three of us have never quite forgiven you for it, either.. :-) > Well, Rod is burning in my dual processor P90 right now (ask him if > you don't believe me). Oh, I don't doubt that you're thinking of jumping in, I'm just a little tired of the continued "I'm coming in soon! I am! How's the water? Cold? Should I wear the bathing cap? If I toss in a thermometer, would someone mind reading the temperature to me? Does anyone see any snapping turtles sitting on the bottom? You know, this reminds me of another water hole I used to use back during my salad days at RAND, why we used to gather 'round every Sunday and..." >From our perspective, what we get from you are multi-page missives but virtually nothing in the way of diffs. Try to see it through our eyes, Terry! It's hardly impatience when it's gone on for YEARS, and I think I can reasonably say that the burden of proof is quite fairly and squarely on you at this point. I'm not going to poison the well with undue cynicism, but I do think that some of the feelings of frustration that I and others feel is more than reasonably well founded. 3 or 6 months is one thing, but we're not talking about 3 to 6 months, are we? > Feel free to ask Jeffrey Hsu what is currently going on with him, if > he's willing to comment. I will. I know he's got an important project going, but judging by some of the other abortive projects that have come (and gone) before, I'm not exactly going to hold this up in lieu of actual, tangible progress. No slight to Jeff intended or implied, but my viewpoint is an entirely reasonable one. When he has something to share with us then I'm sure that he will. Until he does, however, I'm not going to go around telling everyone that Jeff's a god and is going to save the world tomorrow and, to his credit, Jeff doesn't appear to be doing so either! > Feel free to ask Sean Eric Fagan what joint project we have up our > sleeves, though I'd rather it not be made too public right now. See above. I'm sure you have 27 different projects up your sleeve right now. When one bears demonstrable fruit, call me! I'll be happy to send you a six pack of fine beer just for proving me wrong.. :-) > I just barely finished reviewing someone else's manuscript for > Prentice Hall; it was a much more time consuming job than I had > expected. Naerly 6 Months of free time; expect to see the book > "UNIX Internals: The New Frontiers" in bookstores soon. I highly > recommend it for its comparative look at many UNIX implementations. Well, I won't kick it out of bed. I'll keep my eyes open for it. > Meanwhile, Sean has seen one pre-release game of several, and everyone > on the FreeBSD Core and XFree86 mailing lists at least had opportunity > (even if they didn't exercise it) to see the first Alpha of Mimic, my > Motif library clone. Now c'mon, Terry. You're reaching for straws now. I did grab it and I saw that it wasn't anywhere near "there" enough for anything I'd want to use Motif for (e.g. compiling any sort of reasonably sized Motif-dependant software) so I went back to other things. Don't get me wrong, I know that everything's got to start somewhere, but you must admit that Mimic wasn't even really ALPHA by a long shot. ALPHA is a version of fully functioning software that may or may not have significant bugs and is perhaps missing some functionality around the edges. BETA is supposed to have the missing holes filled in and a few less bugs. RELEASE is supposed to have the last (known) bugs worked out and be as featureful as was planned for that release.. To release a credible Motif clone, you need to at least have fairly significant coverage of all the standard and commonly used primitives and header files, and Mimic doesn't even come close. So I'll give you full credit for a good project and a fine start, but please don't start saying silly things like "I released an ALPHA of Mimic, my Motif library clone" when both you and I know that what you REALLY did was release a snapshot of Mimic, your work-in-progress towards a Motif library clone. There's quite a difference! > On the other hand, places where I do only make comments, you can be > sure I have some sort of code concern or another in mind. Just because > I don't think something is release quality doesn't mean it's not there Not my point at all. I just want to see more concrete examples and less of "you guys could all rearchitect the frammitz and redo the glotch" sorts of postings. You seem to have this need to work in a corner and occasionally come out in a loud blare of trumpets and a cry of "follow me, men!" when it would seem far more practical to work a little more in the open light of day and let other people have a chance to actually see and PARTICIPATE in the day-to-day progress of a project. Imagine if we ran -current in such a fashion: No code was released, except perhaps once every 6 months or so when we felt like it, and all the other hackers had to go on were bits of forwarded email chit-chat between the various core team members things like "I'm rearchitecting the VM system guys! It's way cool!" "Yaaay! Go David!" and such. Everyone else would leave in disgust! Again, this is one of those hyper-obvious things that I'm having trouble figuring out why I should even have to mention it to you. Bill Jolitz did EXACTLY the same thing to us, which is perhaps why we're a little sensitive about it now. Doesn't make you any less guilty of it, mind you, but just to put things into further perspective. > I'd like to avoid providing opportunity for that kind of screwup again, > thank you. Well, one way of avoiding it would be to work openly and give people the chance to notice things like that BEFORE THEY HAPPEN! I know, I know, it's a crazy idea but it Might Just Work! :-) > Yes, I take a hundred paths at once; that doesn't mean I never reach > the end of any of them. Have some frigging patience! I haven't been Oh, I have Terry, believe me I have. But I think I also can't be blamed if that patience is wearing just a bit thin. I'm not the only one who thinks that the number and length of these delays has turned much of what you've talking about over the last 2 years into something of a running farce.. Wake up and smell the coffee! Why don't we simply agree to disgree on your methodology and whether or not you're ever going to come out of the hole to see your shadow and just wait and see? I'll agree that there's certainly no constructive effect to my flaming you to toast at this point, and if I reached some of my internal limits yesterday and went perhaps a bit too publically ballistic as a result, then I'll be the first to admit that I should probably back off and admit that even if I'm RIGHT in every single one of my assessments it really doesn't matter and I should shut up. You're not a horse who can be made to drink and I think we can all be comfortable with that conclusion.. :-) Jordan From owner-freebsd-current Tue Jun 27 01:06:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAB14641 for current-outgoing; Tue, 27 Jun 1995 01:06:06 -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 BAB14635 ; Tue, 27 Jun 1995 01:06:01 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id BAA06007; Tue, 27 Jun 1995 01:05:56 -0700 From: "Rodney W. Grimes" Message-Id: <199506270805.BAA06007@gndrsh.aac.dev.com> Subject: Re: when is the supscan done? To: gpalmer@westhill.cdrom.com (Gary Palmer) Date: Tue, 27 Jun 1995 01:05:56 -0700 (PDT) Cc: peter@haywire.DIALix.COM, current@freebsd.org, jmb@freebsd.org In-Reply-To: <23226.804216245@westhill.cdrom.com> from "Gary Palmer" at Jun 26, 95 06:24:05 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: 1186 Sender: current-owner@freebsd.org Precedence: bulk > > In message <199506261755.KAA04885@gndrsh.aac.dev.com>, "Rodney W. Grimes" write > s: > >Right now this just goes out to the root: alias in /etc/sendmail.cf, > >but that can be changed pretty easily. > > They also contain a lot more info than I think people want to see... > (and the root alias is in /etc/aliases, not sendmail.cf :-) ) > > Perhaps we should split the cvs update's off somehow to enable the > supscan's to still go to root? After my last set of hackery to /root/bin/update_usrsrc it is time for a rewrite using shell functions and while someone is at it the update should be split out and send probably to freebsd-current and to freebsd-stable respectfully. Also the long list of /usr/local/bin/supscan should be converted to a shell function and used something like this (my shell programming lessons predate functions, so syntax may be wrong here). dosupcan (supsubclass) { for i in base bin ... usrsbin; do /usr/local/bin/supscan /home ${supsubclass}${i} done } dosupscan(""); dosupscan("stable-"); -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Tue Jun 27 01:15:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA15050 for current-outgoing; Tue, 27 Jun 1995 01:15:24 -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 BAA15042 ; Tue, 27 Jun 1995 01:15:20 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id BAA06024; Tue, 27 Jun 1995 01:15:28 -0700 From: "Rodney W. Grimes" Message-Id: <199506270815.BAA06024@gndrsh.aac.dev.com> Subject: Re: Crypt code summary(2). To: terry@cs.weber.edu (Terry Lambert) Date: Tue, 27 Jun 1995 01:15:28 -0700 (PDT) Cc: jkh@freebsd.org, phk@freefall.cdrom.com, mark@grondar.za, wollman@halloran-eldar.lcs.mit.edu, current@freebsd.org In-Reply-To: <9506270235.AA01284@cs.weber.edu> from "Terry Lambert" at Jun 26, 95 08:35:07 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: 2904 Sender: current-owner@freebsd.org Precedence: bulk > > [ ... Re: Consortium ... ] > > > So if you want to front such an organization, please feel free! But > > don't talk to me about how YOU are maxed out and then in the same > > breath imply that our own lack of willingness comes from arrogance of > > our position and not simply a similar level of over-committment. > > That's not what I implied. I implied a lack of interest, not "interest > but a lack of willingness". > > Arrogance is another topic entirely, and the failure attributable to > it is names "Merge", not "Consortium" (and no, I'm not *willing* to > go down that thread again). I have talked on this issue before, but want to make one thing clear, ``Arrognace'' was not the cause of the Merge failure. And unless you are either Chris D. or Rod Grimes you don't really know all the gory details and should not make statements about what may or may not have been the cause of the merge failure. ... > > > but always has a convenient excuse when the REAL work or > > committment is called for. Enough with the feeble excuses! We've > > heard them all by now! Put up or shut up, PUH-LEEZE! :-) > > Well, Rod is burning in my dual processor P90 right now (ask him if > you don't believe me). Fact! > Feel free to ask Jeffrey Hsu what is currently going on with him, if > he's willing to comment. > > Feel free to ask Sean Eric Fagan what joint project we have up our > sleeves, though I'd rather it not be made too public right now. > > I just barely finished reviewing someone else's manuscript for > Prentice Hall; it was a much more time consuming job than I had > expected. Naerly 6 Months of free time; expect to see the book > "UNIX Internals: The New Frontiers" in bookstores soon. I highly > recommend it for its comparative look at many UNIX implementations. Way COOL!!! Now, when is the 4.4 CSRG internals book suppose to come out?? > I'm about to take my first real vacation in about two years (not that Gee, you take vacations to often. My last real vacation was some time in the 1980's, that is why you don't have enoght time :-) :-) :-) .. > > Yes, I take a hundred paths at once; that doesn't mean I never reach > the end of any of them. Have some frigging patience! I haven't been > in a position to *do* anything, first because of Novell, and then for > lack of equipment and all my free time going to book reviewing (all > three of which should finally be remedied around the 10th of July). Please hold your patience with Terry just a little bit longer, I think we are going to start seeing his real work in a more visable form some time in the very near future (I predict August based on a shipping date that has been requested as I know just when Terry comes back from Vacation :-)). -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Tue Jun 27 02:45:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA21829 for current-outgoing; Tue, 27 Jun 1995 02:45:17 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA21808 for ; Tue, 27 Jun 1995 02:45:03 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.11/8.6.9) with ESMTP id LAA04494; Tue, 27 Jun 1995 11:44:41 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.11/8.6.9) with SMTP id LAA17659; Tue, 27 Jun 1995 11:44:38 +0200 Message-Id: <199506270944.LAA17659@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: geoff@ufrmsa1.olivetti.za, Wollman@halloran-eldar.lcs.mit.edu, gibbs@freefall.cdrom.com, rgrimes@gndrsh.aac.dev.com, current@freebsd.org Subject: More crypto proposals. Date: Tue, 27 Jun 1995 11:44:37 +0200 From: Mark Murray Sender: current-owner@freebsd.org Precedence: bulk Hi Well! That last one certainly sparked off a lively debate! Who said the art of negotiation was dead? I am certainly making policy progress here, so thank you all for your input. I'm not going to rehash it all here - just the bits that need it: 1) We have been offered a machine to run the crypto CVS on. This is skeleton.mikom.csir.co.za, and is the same machine that I use as the master FTP site for the non-US crypt code. The machine is run by (I may not have the name totally right) the Computer Security Group of the Council for Scientific and Industrial Research (CSIR) in South Africa, and these blokes are committed. I think that this meets the requirement of the site not being a `fly-by-night'; they will be around for a loooong while. Geoff Rehmet has offered to set up this machine for CVS. 2) Geoff has expressed an interest in getting back into the `swing of things, and wants to work with me on the secure code. He is happy to help out, but does not want to lead the project. 3) I recognise some grave reservations that the US folk have with a lot of the crypto code I am proposing (SSLeay). I would now like to open _another_ can of worms by making this proposal: In the (distant) past, the US folks have made their own crypto libraries, and it has been up to _us_ to track _them_. If we are running a non-US crypto site, and we are not subject to US law in this regard, how would the US residents feel about us making the non-US code as _we_ like it? (Well, more or less - I am not talking free reign here, nor am I trying to start a splinter movement. I am just trying to come up with a mechanism to provide this code to many folks who want/need it.) Obviously this would be done in such a way as to _not_ make it look as though you are `co-operating', so you could not be busted, but it would fit seamlessly into [y]our code. This way, as things develop, you could track us. The way this could be done is for us to just build our `secure' so the standard targets work - obj, all, install, distribute etc. The main src/Makefile can then just use these if `secure' exists. So what changes? `our' code gets a little ahead of `yours', and there is nothing to stop you tracking _us_. Bottom line, this could still be (as Rod and Garrett point out) put into the ports distribution. I would prefer to not do this, as from communications I have had with Eric Young, I believe that some form of SSL will become ubiquitous - and after SSLeay gets posted, a floodgate will open. What say? M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Tue Jun 27 07:43:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA14908 for current-outgoing; Tue, 27 Jun 1995 07:43:19 -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 HAB14898 ; Tue, 27 Jun 1995 07:43:16 -0700 Message-Id: <199506271443.HAB14898@freefall.cdrom.com> X-Authentication-Warning: freefall.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: "Rodney W. Grimes" cc: gpalmer@westhill.cdrom.com (Gary Palmer), peter@haywire.dialix.com, current@freebsd.org, jmb@freebsd.org Subject: Re: when is the supscan done? In-reply-to: Your message of "Tue, 27 Jun 95 01:05:56 PDT." <199506270805.BAA06007@gndrsh.aac.dev.com> Date: Tue, 27 Jun 1995 07:43:15 -0700 From: "Justin T. Gibbs" Sender: current-owner@freebsd.org Precedence: bulk > >Also the long list of /usr/local/bin/supscan should be converted to a >shell function and used something like this (my shell programming >lessons predate functions, so syntax may be wrong here). > Why not something more dynamic: cd /home/sup foreach i ( * ) supscan $i /home/sup end Of course thats csh not sh, but you get the idea. >-- >Rod Grimes rgrimes@gndrsh.aac.dev.com >Accurate Automation Company Reliable computers for FreeBSD -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Jun 27 08:04:38 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA16383 for current-outgoing; Tue, 27 Jun 1995 08:04:38 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA16377 for ; Tue, 27 Jun 1995 08:04:35 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA20062; Tue, 27 Jun 1995 11:03:29 -0400 Date: Tue, 27 Jun 1995 11:03:29 -0400 From: Garrett Wollman Message-Id: <9506271503.AA20062@halloran-eldar.lcs.mit.edu> To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka "Andrey A. Chernov, Black Mage" Cc: freebsd-current Subject: Re: mb_map full with GATEWAY and maxusers 64! In-Reply-To: References: <199506262226.PAA17617@corbin.Root.COM> Sender: current-owner@FreeBSD.org Precedence: bulk < said: > I wonder why it happens on my host, as I already said, user activity > was very low, and I am not running HTTP/anon FTP/IRCD/NFSD or other > network-consume daemons, just plain routed+named. The C library's stub resolver likes to use TCP connections to talk to named (so that it can get a somewhat guaranteed indication of success or failure). If you do a lot of DNS resolution very quickly, then this can create a lot of TCP connections in TIME_WAIT state. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Tue Jun 27 08:09:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA16763 for current-outgoing; Tue, 27 Jun 1995 08:09:16 -0700 Received: from asstdc.scgt.oz.au (asstdc.scgt.oz.au [202.14.234.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA16737 for ; Tue, 27 Jun 1995 08:08:55 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id BAA08082 for current@freebsd.org; Wed, 28 Jun 1995 01:07:35 +1000 From: michael butler Message-Id: <199506271507.BAA08082@asstdc.scgt.oz.au> Subject: ipfw - addf reject = panic To: current@freebsd.org Date: Wed, 28 Jun 1995 01:07:34 +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: 305 Sender: current-owner@freebsd.org Precedence: bulk This evening I was looking to move back to kernel mode ppp and, in doing so, exploring the firewall facility ipfw once more. Sad news .. gw3:~ # ipfw addf reject all from any to harvey : : asstdc:~ # traceroute harvey .. results in a kernel panic on gw3 running current as of yesterday :-( michael From owner-freebsd-current Tue Jun 27 08:13:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA16979 for current-outgoing; Tue, 27 Jun 1995 08:13:43 -0700 Received: from westhill.cdrom.com (westhill.cdrom.com [192.216.223.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA16973 for ; Tue, 27 Jun 1995 08:13:42 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by westhill.cdrom.com (8.6.11/8.6.11) with SMTP id IAA00686 ; Tue, 27 Jun 1995 08:13:03 -0700 X-Authentication-Warning: westhill.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: michael butler cc: current@freebsd.org Subject: Re: ipfw - addf reject = panic In-reply-to: Your message of "Wed, 28 Jun 1995 01:07:34 +1000." <199506271507.BAA08082@asstdc.scgt.oz.au> Date: Tue, 27 Jun 1995 08:13:03 -0700 Message-ID: <684.804265983@westhill.cdrom.com> From: Gary Palmer Sender: current-owner@freebsd.org Precedence: bulk In message <199506271507.BAA08082@asstdc.scgt.oz.au>, michael butler writes: >This evening I was looking to move back to kernel mode ppp and, in doing so, >exploring the firewall facility ipfw once more. Sad news .. >gw3:~ # ipfw addf reject all from any to harvey >asstdc:~ # traceroute harvey > .. results in a kernel panic on gw3 running current as of yesterday :-( Really? Have you tried just `ipfw addf ldeny ...' instead to see if it's a problem with the ICMP sending code? If not, I'm in trouble... I just turned on the firewall locally - on a -current box, although I'm not using `reject'... Gary From owner-freebsd-current Tue Jun 27 08:19:44 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA17525 for current-outgoing; Tue, 27 Jun 1995 08:19:44 -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 IAA17508 for ; Tue, 27 Jun 1995 08:19:30 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id BAA08464; Wed, 28 Jun 1995 01:18:32 +1000 From: michael butler Message-Id: <199506271518.BAA08464@asstdc.scgt.oz.au> Subject: Re: ipfw - addf reject = panic To: gpalmer@westhill.cdrom.com (Gary Palmer) Date: Wed, 28 Jun 1995 01:18:31 +1000 (EST) Cc: current@freebsd.org In-Reply-To: <684.804265983@westhill.cdrom.com> from "Gary Palmer" at Jun 27, 95 08:13:03 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: 401 Sender: current-owner@freebsd.org Precedence: bulk Gary Palmer writes: > Really? Have you tried just `ipfw addf ldeny ...' instead to see if > it's a problem with the ICMP sending code? If not, I'm in trouble... I > just turned on the firewall locally - on a -current box, although I'm > not using `reject'... "ldeny" works properly .. just throws it onto the gw3's console as it should. Thanks, a workaround whilst it gets scrutinised :-) michael From owner-freebsd-current Tue Jun 27 08:52:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA19118 for current-outgoing; Tue, 27 Jun 1995 08:52:24 -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 IAA19107 for ; Tue, 27 Jun 1995 08:52:20 -0700 Received: from freebsd.netcraft.co.uk (lambda.demon.co.uk [158.152.17.124]) by who.cdrom.com (8.6.11/8.6.9) with ESMTP id IAA21707 for ; Tue, 27 Jun 1995 08:52:09 -0700 Received: (from paul@localhost) by freebsd.netcraft.co.uk (8.6.11/8.6.9) id QAA01048; Tue, 27 Jun 1995 16:39:12 +0100 From: Paul Richards Message-Id: <199506271539.QAA01048@freebsd.netcraft.co.uk> Subject: Re: ipfw - addf reject = panic To: gpalmer@westhill.cdrom.com (Gary Palmer) Date: Tue, 27 Jun 1995 16:39:11 +0100 (BST) Cc: imb@scgt.oz.au, current@freebsd.org In-Reply-To: <684.804265983@westhill.cdrom.com> from "Gary Palmer" at Jun 27, 95 08:13:03 am Reply-to: paul@freebsd.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1092 Sender: current-owner@freebsd.org Precedence: bulk In reply to Gary Palmer who said > > In message <199506271507.BAA08082@asstdc.scgt.oz.au>, michael butler writes: > >This evening I was looking to move back to kernel mode ppp and, in doing so, > >exploring the firewall facility ipfw once more. Sad news .. > > >gw3:~ # ipfw addf reject all from any to harvey > > >asstdc:~ # traceroute harvey > > > .. results in a kernel panic on gw3 running current as of yesterday :-( > > Really? Have you tried just `ipfw addf ldeny ...' instead to see if > it's a problem with the ICMP sending code? If not, I'm in trouble... I > just turned on the firewall locally - on a -current box, although I'm > not using `reject'... The ipfw code works for me fine but using user-space PPP. I suspect that it is the kernel PPP code that is falling over rather than anything else since it was flakey in 2.0 and has since been largely ignored since everyones switched. -- Paul Richards, Bluebird Computer Systems. FreeBSD core team member. Internet: paul@FreeBSD.org, http://www.freebsd.org/~paul Phone: 0370 462071 (Mobile), +44 1222 457651 (home) From owner-freebsd-current Tue Jun 27 09:11:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA19792 for current-outgoing; Tue, 27 Jun 1995 09:11:23 -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 JAA19781 ; Tue, 27 Jun 1995 09:10:59 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id CAA11019; Wed, 28 Jun 1995 02:10:41 +1000 From: michael butler Message-Id: <199506271610.CAA11019@asstdc.scgt.oz.au> Subject: Re: ipfw - addf reject = panic To: paul@freebsd.org Date: Wed, 28 Jun 1995 02:10:38 +1000 (EST) Cc: current@freebsd.org In-Reply-To: <199506271539.QAA01048@freebsd.netcraft.co.uk> from "Paul Richards" at Jun 27, 95 04:39:11 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: 495 Sender: current-owner@freebsd.org Precedence: bulk Paul Richards writes: > The ipfw code works for me fine but using user-space PPP. I suspect > that it is the kernel PPP code that is falling over rather than > anything else since it was flakey in 2.0 and has since been largely > ignored since everyones switched. Different code .. user-mode PPP has its own internal filter functions executed at context-switch intervals along with the rest of the protocol. It also currently has no facility to return ICMP unreachable indications, michael From owner-freebsd-current Tue Jun 27 09:45:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA21157 for current-outgoing; Tue, 27 Jun 1995 09:45:26 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA21149 for ; Tue, 27 Jun 1995 09:45:24 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA20239; Tue, 27 Jun 1995 12:44:55 -0400 Date: Tue, 27 Jun 1995 12:44:55 -0400 From: Garrett Wollman Message-Id: <9506271644.AA20239@halloran-eldar.lcs.mit.edu> To: Mark Murray Cc: geoff@ufrmsa1.olivetti.za, Wollman@halloran-eldar.lcs.mit.edu, gibbs@freefall.cdrom.com, rgrimes@gndrsh.aac.dev.com, current@freebsd.org Subject: More crypto proposals. In-Reply-To: <199506270944.LAA17659@grumble.grondar.za> References: <199506270944.LAA17659@grumble.grondar.za> Sender: current-owner@freebsd.org Precedence: bulk < said: > In the (distant) past, the US folks have made their own crypto libraries, > and it has been up to _us_ to track _them_. If we are running a non-US > crypto site, and we are not subject to US law in this regard, how would > the US residents feel about us making the non-US code as _we_ > like it? I don't think this is a problem, with the caveat that if anything is to got out with the label ``FreeBSD'' on it, it should get the same sort of review as anything else that is a part of the system. > Bottom line, this could still be (as Rod and Garrett point out) put > into the ports distribution. I would prefer to not do this, as from > communications I have had with Eric Young, I believe that some form of > SSL will become ubiquitous - and after SSLeay gets posted, a floodgate > will open. Regardless, I would far rather see this particular business handled by the `ports' mechanism. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Tue Jun 27 10:51:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA25794 for current-outgoing; Tue, 27 Jun 1995 10:51:49 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA25785 ; Tue, 27 Jun 1995 10:51:47 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA03188; Tue, 27 Jun 95 11:44:53 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506271744.AA03188@cs.weber.edu> Subject: Re: Crypt code summary(2). To: jkh@freebsd.org (Jordan K. Hubbard) Date: Tue, 27 Jun 95 11:44:53 MDT Cc: jkh@freebsd.org, rgrimes@gndrsh.aac.dev.com, phk@freefall.cdrom.com, mark@grondar.za, wollman@halloran-eldar.lcs.mit.edu, current@freebsd.org In-Reply-To: <6420.804237100@whisker.internet-eireann.ie> from "Jordan K. Hubbard" at Jun 27, 95 08:11:40 am X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@freebsd.org Precedence: bulk [ ... Merge crap ... ] > Arrogance really didn't enter into it, and it's really overly > simplistic of you to think that it did. These are volunteers here > Terry, in case you've forgotten. You can't get the Moose Lodge to > meet every saturday for drinks and socialization if they all hate one > another's guts. If it's a business, and the people involved are employees, you can get them together; money is a powerful motivator. All you are really saying here is that there was insufficient motivation (money or otherwise). It was not my intent to travel this road again, so I'm going to stick my fingers in my eyes and hum until we get to the rest of the message. > Oh, I don't doubt that you're thinking of jumping in, I'm just a > little tired of the continued "I'm coming in soon! I am! How's the > water? Cold? Should I wear the bathing cap? If I toss in a > thermometer, would someone mind reading the temperature to me? Does > anyone see any snapping turtles sitting on the bottom? You know, this > reminds me of another water hole I used to use back during my salad > days at RAND, why we used to gather 'round every Sunday and..." Humerous. At the end of July, I want to commit semantic changes to the mount system call, some areas of the file system code in each file system type, and all user space file system utilties. This is not "thinking of jumping in", this is a date. I need an architecture specific subdirectory (ie: shared between hosts of the same cpu type) where I can put a subdirectory containing file system utilitites usable in single user mode. If you care about seperating file system types by whether or not you can use them in single user mode, I will need another directory that serves the same function and which is also searched, assuming the file system containing it is mounted. I was thinking of /sbin/fs/ and /usr/sbin/fs/. At the same time, I want to reorganize the file system portion of the kernel source tree. Specifically, I want to rename the ufs directory to vfs. I want to move iosfs, miscfs, msdosfs, and nfs into this directory. I would also like to move the vfs specific portions of the kern/* files into the vfs directory, preferrably at the vfs/* level rather than as a subdirectory. Comments? > > Meanwhile, Sean has seen one pre-release game of several, and everyone > > on the FreeBSD Core and XFree86 mailing lists at least had opportunity > > (even if they didn't exercise it) to see the first Alpha of Mimic, my > > Motif library clone. > > Now c'mon, Terry. You're reaching for straws now. I did grab it and > I saw that it wasn't anywhere near "there" enough for anything I'd > want to use Motif for (e.g. compiling any sort of reasonably sized > Motif-dependant software) so I went back to other things. Don't get > me wrong, I know that everything's got to start somewhere, but you > must admit that Mimic wasn't even really ALPHA by a long shot. ALPHA > is a version of fully functioning software that may or may not have > significant bugs and is perhaps missing some functionality around the > edges. Excuse me. Apparently you didn't look very hard. The code was sufficient for compiling and linking any Motif program using the documented Motif 1.2.x interfaces, period. As stated in the release notes, the library itself was intentionally disabled, although it would, in fact, as it was distributed, allow you to run several O'Reilly and Young book examples. The only ftpable things that wouldn't compile were two "public domain" widgets, obviously written with Motif source in one hand and a pencil in the other, and "moxftp", which used an undocumented interface to build an XmFontList in two places because the author didn't want write his own code, and manifest constants in several others because the author was (apparently) too lazy to use (caddr_t) casts like he was supposed to for _XtInherit. > BETA is supposed to have the missing holes filled in and a few > less bugs. RELEASE is supposed to have the last (known) bugs worked > out and be as featureful as was planned for that release.. To release > a credible Motif clone, you need to at least have fairly significant > coverage of all the standard and commonly used primitives and header > files, and Mimic doesn't even come close. Nice to know that you examined it so carefully without submitting *any* feedback on it (until now, and I still don't know what sources you used so I could go, get them, and make them work). > You seem to have this need to work in a corner and occasionally come > out in a loud blare of trumpets and a cry of "follow me, men!" when it > would seem far more practical to work a little more in the open light > of day and let other people have a chance to actually see and > PARTICIPATE in the day-to-day progress of a project. I have asked for host space for several projects. I have plenty of space, but it is not net connected and is pretty damn useless for that sort of thing, you'd have to agree. FreeBSD has the luxury it has because of freefall.cdrom.com and freebsd.cdrom.com. Before that, it had the ref.tfs.com machine. Until I have the same luxury, I'll code on the hardware I have available, and if it doesn't have anonymous FTP into it like the hardware available to you, well, that's too bad. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Jun 27 11:03:07 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA26293 for current-outgoing; Tue, 27 Jun 1995 11:03:07 -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 LAA26283 ; Tue, 27 Jun 1995 11:03:04 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id LAA07070; Tue, 27 Jun 1995 11:03:14 -0700 From: "Rodney W. Grimes" Message-Id: <199506271803.LAA07070@gndrsh.aac.dev.com> Subject: Re: when is the supscan done? To: gibbs@freefall.cdrom.com (Justin T. Gibbs) Date: Tue, 27 Jun 1995 11:03:14 -0700 (PDT) Cc: FreeBSD-current@FreeBSD.Org (FreeBSD current) In-Reply-To: <199506271443.HAB14898@freefall.cdrom.com> from "Justin T. Gibbs" at Jun 27, 95 07:43:15 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: 908 Sender: current-owner@FreeBSD.Org Precedence: bulk > > > > >Also the long list of /usr/local/bin/supscan should be converted to a > >shell function and used something like this (my shell programming > >lessons predate functions, so syntax may be wrong here). > > > > Why not something more dynamic: > > cd /home/sup > foreach i ( * ) > supscan $i /home/sup > end > > Of course thats csh not sh, but you get the idea. and leaves out the fact that there are things in /home/sup that are NOT scanable sup collections. And I sure as heck don't want the cvs-* targets to have scan files, those are done on the fly! Nope, do not do this!! Use what I wrote, correcting any syntax errors, it was not so off the cuff, but a thought out replacement that does exactly what we have now in 1/10th the lines. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Tue Jun 27 11:11:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAB26507 for current-outgoing; Tue, 27 Jun 1995 11:11:19 -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 LAA26501 for ; Tue, 27 Jun 1995 11:11:15 -0700 Received: (from peter@localhost) by haywire.DIALix.COM (8.6.12/8.6.12/DIALix) id CAA26278; Wed, 28 Jun 1995 02:11:05 +0800 Date: Wed, 28 Jun 1995 02:11:02 +0800 (WST) From: Peter Wemm To: current@freebsd.org Subject: taylor-uucp mods in freebsd-current? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk Taylor-uucp 1.06 is being prepared for release, and the author has asked for any final patches.. How much has the code in FreeBSD diverged? It's hard to diff trivially because of the reorganisation of the directory tree... A grep revealed some of the FreeBSD versions are up to v1.5, and a lot are at 1.3. I had a go at it and found a lot of diffs, but most of it was buried in white-space diffs (I've just asked Ian to stip them out of his copy). Despite that, I found a couple of changes that looked like bug fixes, but it's not obvious what they were for.. Is there any chance of finding somebody CVS access who could have a rummage around the CVS logs and find out why the changes were made? Thanks, -Peter From owner-freebsd-current Tue Jun 27 11:26:18 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA27163 for current-outgoing; Tue, 27 Jun 1995 11:26:18 -0700 Received: from freebsd.netcraft.co.uk (lambda.demon.co.uk [158.152.17.124]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA27157 ; Tue, 27 Jun 1995 11:26:12 -0700 Received: (from paul@localhost) by freebsd.netcraft.co.uk (8.6.11/8.6.9) id RAA01451; Tue, 27 Jun 1995 17:40:58 +0100 From: Paul Richards Message-Id: <199506271640.RAA01451@freebsd.netcraft.co.uk> Subject: Re: ipfw - addf reject = panic To: imb@scgt.oz.au (michael butler) Date: Tue, 27 Jun 1995 17:40:58 +0100 (BST) Cc: paul@freebsd.org, current@freebsd.org In-Reply-To: <199506271610.CAA11019@asstdc.scgt.oz.au> from "michael butler" at Jun 28, 95 02:10:38 am Reply-to: paul@freebsd.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 946 Sender: current-owner@freebsd.org Precedence: bulk In reply to michael butler who said > > Paul Richards writes: > > > The ipfw code works for me fine but using user-space PPP. I suspect > > that it is the kernel PPP code that is falling over rather than > > anything else since it was flakey in 2.0 and has since been largely > > ignored since everyones switched. > > Different code .. user-mode PPP has its own internal filter functions > executed at context-switch intervals along with the rest of the protocol. > It also currently has no facility to return ICMP unreachable indications, Ehh? I'm using ipfw, the kernel firewall code, not the user-mode PPP filtering code. I think the layering is (is this right?) modem <-> user PPP <-> tun <-> IP layer <-> ipfw <-> TCP so ipfw is always common. -- Paul Richards, Bluebird Computer Systems. FreeBSD core team member. Internet: paul@FreeBSD.org, http://www.freebsd.org/~paul Phone: 0370 462071 (Mobile), +44 1222 457651 (home) From owner-freebsd-current Tue Jun 27 11:30:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA27373 for current-outgoing; Tue, 27 Jun 1995 11:30:39 -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 LAA27367 for ; Tue, 27 Jun 1995 11:30:36 -0700 Received: (from peter@localhost) by haywire.DIALix.COM (8.6.12/8.6.12/DIALix) id CAA27731; Wed, 28 Jun 1995 02:30:30 +0800 Date: Wed, 28 Jun 1995 02:30:27 +0800 (WST) From: Peter Wemm To: current@freebsd.org Subject: what version of named is in freebsd-current? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk As a followup to the last message, bind-4.9.3 is in it's possibly final form (at BETA21).. What version is in FreeBSD-current? The makefile sets VER=LOCAL-`date ....` Are there any changes in the FreeBSD version that are worthy of being submitted for "11'th hour" patches? (The FreeBSD version seems older than all of the copies I have around... - I didn't have much luck with diff - the smallest diff I got was 7,400 lines long!?! and that's _with_ --ignore-all-space and on just the "named" directory. The diff to BETA21 is 9,974 lines..) Could somebody perhaps please have a rummage around the CVS logs and see if there's anything in particular that should be submitted back to Paul Vixie? Cheers, -Peter From owner-freebsd-current Tue Jun 27 11:36:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA27673 for current-outgoing; Tue, 27 Jun 1995 11:36:27 -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 LAA27656 ; Tue, 27 Jun 1995 11:36:08 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id EAA01749; Wed, 28 Jun 1995 04:35:40 +1000 From: michael butler Message-Id: <199506271835.EAA01749@asstdc.scgt.oz.au> Subject: Re: ipfw - addf reject = panic To: paul@freebsd.org Date: Wed, 28 Jun 1995 04:35:36 +1000 (EST) Cc: current@freebsd.org In-Reply-To: <199506271640.RAA01451@freebsd.netcraft.co.uk> from "Paul Richards" at Jun 27, 95 05:40: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: 455 Sender: current-owner@freebsd.org Precedence: bulk Paul Richards writes: > Ehh? I'm using ipfw, the kernel firewall code, not the user-mode PPP > filtering code. Oh, OK .. sorry, I misunderstood. > I think the layering is (is this right?) > modem <-> user PPP <-> tun <-> IP layer <-> ipfw <-> TCP Yup .. > so ipfw is always common. .. and, having just tested it with user-mode PPP instead of kernel PPP, "ipfw addf reject .." will still panic the box it's running on. "deny" doesn't, michael From owner-freebsd-current Tue Jun 27 11:54:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA28445 for current-outgoing; Tue, 27 Jun 1995 11:54: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 LAA28436 for ; Tue, 27 Jun 1995 11:53:57 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id EAA03427 for current@freebsd.org; Wed, 28 Jun 1995 04:53:46 +1000 From: michael butler Message-Id: <199506271853.EAA03427@asstdc.scgt.oz.au> Subject: gated -> /var/run/gated.pid start-up problem To: current@freebsd.org Date: Wed, 28 Jun 1995 04:53:44 +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: 280 Sender: current-owner@freebsd.org Precedence: bulk It seems that gated (3.5a10) wants to write to /var/run/gated.pid and /var/run/gated.version but on system start-up, this fails :-(. Is the /"mount" in etc/rc for non-nfs file-systems synchronous or is gated trying to write to a file-system that isn't quite there yet ? michael From owner-freebsd-current Tue Jun 27 14:02:38 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA02892 for current-outgoing; Tue, 27 Jun 1995 14:02:38 -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 OAA02884 for ; Tue, 27 Jun 1995 14:02:32 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id HAA23286; Wed, 28 Jun 1995 07:00:32 +1000 Date: Wed, 28 Jun 1995 07:00:32 +1000 From: Bruce Evans Message-Id: <199506272100.HAA23286@godzilla.zeta.org.au> To: current@freebsd.org, peter@haywire.DIALix.COM Subject: Re: taylor-uucp mods in freebsd-current? Sender: current-owner@freebsd.org Precedence: bulk >Taylor-uucp 1.06 is being prepared for release, and the author has asked >for any final patches.. >How much has the code in FreeBSD diverged? It's hard to diff trivially >because of the reorganisation of the directory tree... A grep revealed >some of the FreeBSD versions are up to v1.5, and a lot are at 1.3. Not a lot, but it is even harder to diff trivially because there are no tags to help distinguish the Taylor diffs from our diffs. `cvs diff -c2 -r 1.1' gives 37704 lines 1058787 chars of output. Andrey usually sends changes back to the author promptly, so we are unlikely to have diverged significantly, but it's hard to tell. Bruce From owner-freebsd-current Tue Jun 27 14:30:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA03992 for current-outgoing; Tue, 27 Jun 1995 14:30:28 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA03953 ; Tue, 27 Jun 1995 14:30:04 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.11/8.6.9) with ESMTP id XAA05114; Tue, 27 Jun 1995 23:29:41 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.11/8.6.9) with SMTP id XAA22045; Tue, 27 Jun 1995 23:29:32 +0200 Message-Id: <199506272129.XAA22045@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: Garrett Wollman cc: Mark Murray , geoff@ufrmsa1.olivetti.za, gibbs@freefall.cdrom.com, rgrimes@gndrsh.aac.dev.com, current@freebsd.org Subject: Re: More crypto proposals. Date: Tue, 27 Jun 1995 23:29:32 +0200 From: Mark Murray Sender: current-owner@freebsd.org Precedence: bulk > < said: > > > In the (distant) past, the US folks have made their own crypto libraries , > > and it has been up to _us_ to track _them_. If we are running a non-US > > crypto site, and we are not subject to US law in this regard, how would > > the US residents feel about us making the non-US code as _we_ > > like it? > > I don't think this is a problem, with the caveat that if anything is > to got out with the label ``FreeBSD'' on it, it should get the same > sort of review as anything else that is a part of the system. Wonderful! I was hoping you would say this! I did _not_ want my efforts to be seen as a gung-ho go-it-alone thing. I just want a legal, moral and acceptable method of getting some decent code into FreeBSD. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Tue Jun 27 17:25:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA10837 for current-outgoing; Tue, 27 Jun 1995 17:25:39 -0700 Received: from whisker.internet-eireann.ie (whisker.internet-eireann.ie [194.9.34.204]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA10830 ; Tue, 27 Jun 1995 17:25:28 -0700 Received: from localhost (localhost [127.0.0.1]) by whisker.internet-eireann.ie (8.6.11/8.6.9) with SMTP id BAA08874; Wed, 28 Jun 1995 01:25:50 +0100 To: terry@cs.weber.edu (Terry Lambert) cc: jkh@freebsd.org (Jordan K. Hubbard), rgrimes@gndrsh.aac.dev.com, phk@freefall.cdrom.com, mark@grondar.za, wollman@halloran-eldar.lcs.mit.edu, current@freebsd.org Subject: Re: Crypt code summary(2). In-reply-to: Your message of "Tue, 27 Jun 1995 11:44:53 MDT." <9506271744.AA03188@cs.weber.edu> Date: Wed, 28 Jun 1995 01:25:50 +0100 Message-ID: <8872.804299150@whisker.internet-eireann.ie> From: "Jordan K. Hubbard" Sender: current-owner@freebsd.org Precedence: bulk > If it's a business, and the people involved are employees, you can get > them together; money is a powerful motivator. Well, perhaps we should talk about that sometime. I'm serious. This is the first time anyone has mentioned the words "money and merge" together in the same sentence to me, and while it might not make one bit of difference it does move the goal-posts enough to at least merit a few quiet discussions on the side-lines. > If you care about seperating file system types by whether or not you > can use them in single user mode, I will need another directory that > serves the same function and which is also searched, assuming the file > system containing it is mounted. It all sounds worthy of discussion, but we're in the wrong group for that. I would move any such proposals to arch@freebsd.org. > Nice to know that you examined it so carefully without submitting *any* > feedback on it (until now, and I still don't know what sources you used > so I could go, get them, and make them work). Ok, since I stuck my foot in it, why don't we start over? Tell me exactly what you'd like me to test and I'll give it a shot again with a few programs I've got (like mgdiff) to test with. If it turns out I was blind or using the wrong sources, I'll be more than happy to post a public apology to you on this list. Fair enough? > I have asked for host space for several projects. I have plenty of space, > but it is not net connected and is pretty damn useless for that sort of > thing, you'd have to agree. FreeBSD has the luxury it has because of This, again, is the first time I've heard that lack of a place to work was a sticking point for you. Why didn't you come to me before? I'd be happy to make you a place to work somewhere on one of the FreeBSD machines and I don't think that anyone else on the team would begrudge you a chance to work as out in the open as we have the benefit of being able to do. Just say the word, Terry, and we'll jump through hoops to facilitate you! I am, again, perfectly serious. Jordan From owner-freebsd-current Tue Jun 27 17:41:31 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA11339 for current-outgoing; Tue, 27 Jun 1995 17:41:31 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id RAA11333 ; Tue, 27 Jun 1995 17:41:29 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA04600; Tue, 27 Jun 95 18:34:36 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506280034.AA04600@cs.weber.edu> Subject: Re: Crypt code summary(2). To: jkh@freebsd.org (Jordan K. Hubbard) Date: Tue, 27 Jun 95 18:34:35 MDT Cc: jkh@freebsd.org, rgrimes@gndrsh.aac.dev.com, phk@freefall.cdrom.com, mark@grondar.za, wollman@halloran-eldar.lcs.mit.edu, current@freebsd.org In-Reply-To: <8872.804299150@whisker.internet-eireann.ie> from "Jordan K. Hubbard" at Jun 28, 95 01:25:50 am X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@freebsd.org Precedence: bulk > > If you care about seperating file system types by whether or not you > > can use them in single user mode, I will need another directory that > > serves the same function and which is also searched, assuming the file > > system containing it is mounted. > > It all sounds worthy of discussion, but we're in the wrong group for > that. I would move any such proposals to arch@freebsd.org. Done. Or rather, John is active in this area, and I've agreed with David to coordinate with him. > > Nice to know that you examined it so carefully without submitting *any* > > feedback on it (until now, and I still don't know what sources you used > > so I could go, get them, and make them work). > > Ok, since I stuck my foot in it, why don't we start over? Tell me > exactly what you'd like me to test and I'll give it a shot again with > a few programs I've got (like mgdiff) to test with. If it turns out I > was blind or using the wrong sources, I'll be more than happy to post > a public apology to you on this list. Fair enough? I need to know the date on the tar file you have (if you have one). If you don't, I'll need to dig up my original pruned distribution disk (or I can prune you another one). > > I have asked for host space for several projects. I have plenty of space, > > but it is not net connected and is pretty damn useless for that sort of > > thing, you'd have to agree. FreeBSD has the luxury it has because of > > This, again, is the first time I've heard that lack of a place to work > was a sticking point for you. Why didn't you come to me before? I'd > be happy to make you a place to work somewhere on one of the FreeBSD > machines and I don't think that anyone else on the team would begrudge > you a chance to work as out in the open as we have the benefit of > being able to do. Not all of the things are strictly FreeBSD related... most of them are rather general. If it's still OK, I'm taking you up on it (I get back from Utah on the 10th) semi-immediately. > Just say the word, Terry, and we'll jump through hoops to facilitate > you! I am, again, perfectly serious. 8-). Now in the center ring... throwing the frisbee after yelling "watch this" to the anticipatory crowd... Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Jun 27 17:48:21 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA11660 for current-outgoing; Tue, 27 Jun 1995 17:48:21 -0700 Received: from whisker.internet-eireann.ie (whisker.internet-eireann.ie [194.9.34.204]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA11651 ; Tue, 27 Jun 1995 17:48:07 -0700 Received: from localhost (localhost [127.0.0.1]) by whisker.internet-eireann.ie (8.6.11/8.6.9) with SMTP id BAA09056; Wed, 28 Jun 1995 01:48:34 +0100 To: terry@cs.weber.edu (Terry Lambert) cc: jkh@freebsd.org (Jordan K. Hubbard), rgrimes@gndrsh.aac.dev.com, phk@freefall.cdrom.com, mark@grondar.za, wollman@halloran-eldar.lcs.mit.edu, current@freebsd.org Subject: Re: Crypt code summary(2). In-reply-to: Your message of "Tue, 27 Jun 1995 18:34:35 MDT." <9506280034.AA04600@cs.weber.edu> Date: Wed, 28 Jun 1995 01:48:34 +0100 Message-ID: <9054.804300514@whisker.internet-eireann.ie> From: "Jordan K. Hubbard" Sender: current-owner@freebsd.org Precedence: bulk > I need to know the date on the tar file you have (if you have one). If > you don't, I'll need to dig up my original pruned distribution disk (or > I can prune you another one). I think it was on time.cdrom.com, which Gary kindly "cleaned" for me recently (it's a long story :-) and so I'm going to need it again, sorry! > Not all of the things are strictly FreeBSD related... most of them are > rather general. If it's still OK, I'm taking you up on it (I get back > from Utah on the 10th) semi-immediately. I don't see any problem with this. > 8-). Now in the center ring... throwing the frisbee after yelling > "watch this" to the anticipatory crowd... "Watch this", eh? You realize, of course, that this only insures that it's now going to bounce off your head right before you trip over your own feet and land in a comical heap, the frisbee meanwhile going on to ricochet onto the nearest roof. :-) Jordan From owner-freebsd-current Tue Jun 27 20:17:07 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA16659 for current-outgoing; Tue, 27 Jun 1995 20:17:07 -0700 Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id UAA16650 for ; Tue, 27 Jun 1995 20:17:04 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15492(2)>; Tue, 27 Jun 1995 20:16:21 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <49860>; Tue, 27 Jun 1995 20:16:11 -0700 To: roberto@blaise.ibp.fr (Ollivier Robert) cc: wollman@freefall.cdrom.com (Garrett A. Wollman), current@freebsd.org Subject: Re: traceroute with LSRR options In-reply-to: Your message of "Thu, 22 Jun 95 02:41:22 PDT." <199506220941.LAA02391@blaise.ibp.fr> Date: Tue, 27 Jun 1995 20:16:05 PDT From: Bill Fenner Message-Id: <95Jun27.201611pdt.49860@crevenia.parc.xerox.com> Sender: current-owner@freebsd.org Precedence: bulk In message <199506220941.LAA02391@blaise.ibp.fr> you write: >Speaking of traceroute, it would be nice to have the version >that support loose sorce routing, the "-g" option... I attempted to port Matt Mathis's original LSRR patches to our traceroute. It turns out that Matt's code assumes that, even if you set IP_HDRINCL, the kernel will include any options you set with IP_OPTIONS. Our rip_output, however, says: if ((inp->inp_flags & INP_HDRINCL) == 0) { ... opts = inp->inp_options; } else { ... opts = NULL; ... } Is there any reason not to allow the insertion of options with the IP_OPTIONS setsockopt(), even if the user has set IP_HDRINCL? (I know that Stevens says the convention is that if you set IP_HDRINCL then you really mean IP_HDRINCL. But I also think that if you set IP_OPTIONS then you really mean IP_OPTIONS...) Bill From owner-freebsd-current Tue Jun 27 22:52:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA22421 for current-outgoing; Tue, 27 Jun 1995 22:52:12 -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 WAA22415 ; Tue, 27 Jun 1995 22:52:09 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id WAA08478; Tue, 27 Jun 1995 22:52:17 -0700 From: "Rodney W. Grimes" Message-Id: <199506280552.WAA08478@gndrsh.aac.dev.com> Subject: Re: Paul Richards: sysconfig routed setting To: jkh@freebsd.org (Jordan K. Hubbard) Date: Tue, 27 Jun 1995 22:52:17 -0700 (PDT) Cc: FreeBSD-current@freebsd.org (FreeBSD current) In-Reply-To: <8337.804273321@whisker.internet-eireann.ie> from "Jordan K. Hubbard" at Jun 27, 95 06:15:21 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: 3402 Sender: current-owner@freebsd.org Precedence: bulk Note sure why this was just forwarded to me instead of sent to at least the -current mailling list, just because I am the one working in there does not mean these types of discussions should occur in private email.. > > I agree. Okay, so noted. > ------- Forwarded Message > > Received: from freebsd.netcraft.co.uk (lambda.demon.co.uk [158.152.17.124]) > by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA18450 > for ; Tue, 27 Jun 1995 08:35:18 -0700 > Received: (from paul@localhost) by freebsd.netcraft.co.uk (8.6.11/8.6.9) id QAA01000 for jkh@freefall.cdrom.com; Tue, 27 Jun 1995 16:35:02 +0100 > From: Paul Richards > Message-Id: <199506271535.QAA01000@freebsd.netcraft.co.uk> > Subject: sysconfig routed setting > To: jkh@freefall.cdrom.com (Jordan Hubbard) > Date: Tue, 27 Jun 1995 16:35:01 +0100 (BST) > Reply-to: paul@FreeBSD.org > X-Mailer: ELM [version 2.4 PL24] > MIME-Version: 1.0 > Content-Type: text/plain; charset=ISO-8859-1 > Content-Transfer-Encoding: 8bit > > The default value for routed should probably be NO since there are > few reasons to run a router and in those cases where you should > you'll know about it and go configure it appropriately. ``Should'' and ``probably'' are not very convincing words, your already sounding like you would go mush on this if I blew a couple of quick holes at it. Also you give very little technical reason why it should not be run. Routed does not require *any* configuration, and does very very little if anything unless rip packets are on the wires. If RIP packets are on the wires you should damn well be sure you listen to them in one way or another. I also disagree with your assertion that ``where you should you'll know about it and go configure it appropriately''. We have users out there who don't have a clue about this stuff, don't know what RIP is, don't need to know that they get there routing information from some gateway on there network, wouldn't know how to configure it if you told them it needed done. Face it, ip address with netmask and a host name go beyond some of the folks trying to install this stuff now. Perhaps if sysinstall inforced this 4 point synopsis of what you have to do to have your host understand routing: You either have to have a) a default route, b) run routed in some form (the current defaults are good) to pick up rip packets off the wire, c) gated (a non-trival thing to set up) or d) no network connection to have your system work correctly. Give those 4 conditions the best default there is to ship the system with (since you can't do the default route or gated configuration) is to have routed -q started by default. If a person sets a default route, they can disable routed. If a person sets up gated the can disable routed If a person has no network connection, well, okay, it is wrong for this one case, they could disable routed if they wanted to free the process slot and some memory. IMHO, and evidently CSRG's as well, routed -q should be the default it covers the widest cases. If I set the default to ``NO'' belive me there are going to be a lot of bug reports about people who can not get off there local network. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Jun 28 00:38:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA26852 for current-outgoing; Wed, 28 Jun 1995 00:38:34 -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 AAA26846 for ; Wed, 28 Jun 1995 00:38:30 -0700 Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au id <21245-0@bunyip.cc.uq.oz.au>; Wed, 28 Jun 1995 17:33:11 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id PAA25465 for ; Wed, 28 Jun 1995 15:52:04 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id FAA05856 for ; Wed, 28 Jun 1995 05:48:59 GMT Message-Id: <199506280548.FAA05856@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6 4/21/95 To: current@freebsd.org Subject: Typo in ip_fw.c Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Jun 1995 15:48:58 +1000 From: Stephen Hocking Sender: current-owner@freebsd.org Precedence: bulk Compiles fall over with the following - /usr/src/lkm/ipfw/../../sys/netinet/ip_fw.c: In function `ip_fw_chk': /usr/src/lkm/ipfw/../../sys/netinet/ip_fw.c:331: `return_0' undeclared (first us e this function) /usr/src/lkm/ipfw/../../sys/netinet/ip_fw.c:331: (Each undeclared identifier is reported only once /usr/src/lkm/ipfw/../../sys/netinet/ip_fw.c:331: for each function it appears in .) Fix is self-evident. Stephen I do not speak for the Worker's Compensation Board of Queensland - They don't pay me enough for that! From owner-freebsd-current Wed Jun 28 02:05:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA29461 for current-outgoing; Wed, 28 Jun 1995 02:05:29 -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 CAA29453 for ; Wed, 28 Jun 1995 02:05:25 -0700 Received: from bunyip.cc.uq.oz.au (bunyip.cc.uq.oz.au [130.102.2.1]) by wc.cdrom.com (8.6.12/8.6.12) with SMTP id CAA25871 for ; Wed, 28 Jun 1995 02:05:19 -0700 Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au id <01415-0@bunyip.cc.uq.oz.au>; Wed, 28 Jun 1995 19:03:09 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id TAA29713 for ; Wed, 28 Jun 1995 19:07:17 +1000 Received: by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id JAA07274; Wed, 28 Jun 1995 09:04:14 GMT Date: Wed, 28 Jun 1995 09:04:14 GMT From: Stephen Hocking Message-Id: <199506280904.JAA07274@netfl15a.devetir.qld.gov.au> To: current@freebsd.org Subject: More crypt stuff (fwd) Sender: current-owner@freebsd.org Precedence: bulk >Xref: pandora.devetir.qld.gov.au comp.security.misc:10184 comp.security.unix:13332 >Path: pandora.devetir.qld.gov.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!europa.chnt.gtegsc.com!ra.nrl.navy.mil!itd!metz >From: metz@itd.itd.nrl.navy.mil (Craig Metz) >Newsgroups: comp.security.unix,comp.security.misc >Subject: Announcing NRL OPIE 2.0 >Date: 27 Jun 1995 18:39:18 GMT >Organization: Information Technology Division, Naval Research Laboratory >Lines: 101 >Message-ID: <3spj8m$5um@ra.nrl.navy.mil> >NNTP-Posting-Host: itd-fddi.nrl.navy.mil Announcing NRL OPIE 2.0 ======================= We are pleased to announce the public release of the U.S. Naval Research Laboratory's One-Time Passwords in Everything (OPIE) Version 2.0 Software Distribution. OPIE provides a one-time password system for POSIX- compliant UNIX-like operating systems. The system should be secure against the passive attacks now commonplace on the Internet (see RFC 1704 for more details). The system is vulnerable to active dictionary attacks, though these are not widespread at present and can be detected through proper use of system audit software. The NRL OPIE software is derived in part from and is backwards compatible with the Bell Communications Research (Bellcore) S/Key(TM) Version 1 Software Distribution. Because Bellcore claims "S/Key" as a trademark for their software, NRL has been forced to use a different name (we picked "OPIE") for its software distribution. NRL OPIE includes the following additions/modifications to the original Bellcore S/Key(TM) Version 1 software: * Just about one-command installation for many common platforms. While we still recommend that you follow instructions and test things by hand, the more adventurous can install OPIE quickly. * A modified BSD FTP daemon that does OPIE. The small and simple BSD ftpd(8) was deliberately chosen over the wuarchive ftpd(8) because we didn't have the time needed to convince ourselves that the wuarchive ftpd(8) didn't have any security holes lurking in its many extra features. * By default, the "su" binary always gives you an OPIE challenge, even on the console. This was a hole for rlogin/telnet sessions in the original S/Key software. * MD5 support. MD5 is now the default algorithm, though MD4 is still supported by changing a parameter in the Makefile. This change was made because MD5 is widely believed to be cryptographically stronger than MD4 (see RFC 1321). * A more portable version of MD4 has been substituted for the original MD4. This should solve many of the endian problems. * Most of the system-dependencies have been moved to a new file "opie_cfg.h". * Configuration options have been moved to the Makefile. * Isolated system dependencies (e.g. BSDisms) with appropriate #ifdefs. * Revised the opiekey(1) program to simultaneously support MD4 and MD5, with the default algorithm being tunable using the MDX symbol in the Makefile. * More operating systems are supported by NRL OPIE as of Release 2, but older BSD systems that aren't close to being compliant with the POSIX standard are no longer supported. * Transition mechanisms are optional to prevent potential back doors. * On systems using the /etc/opieaccess transition mechanism, users can choose to require the use of OPIE to login to their accounts when it would otherwise be optional. * Bug fixes * Cosmetic changes * Changes to mostly conform with the draft Internet OTP standard. Tested Configurations ===================== We have tested OPIE on the following platforms: Hardware Operating System Referred to as System -------- ---------------- -------------- --------- Sun SPARCStation 20 Solaris 2.4 Solaris solaris Sun 4/300 SunOS 4.1.3 SunOS sunos Sun SPARCStation 2 4.4BSD-Encumbered 4.4BSD 44bsd 486/66 PC BSDI BSD/OS 1.1 & 2.0 BSD/OS bsdos 486/66 PC Slackware Linux 2.1 Linux linux SGI Indigo^2 IRIX 5.2 IRIX irix HP 9000/750 HP-UX 9.01 HP-UX9 hpux9 HP 9000/755 HP-UX 10.0 HP-UX10 hpux10 IBM RS/6000 550 AIX 3.2.5 AIX aix Additionally, we have received information from beta testers from which we believe OPIE to work on the following additional platforms: Hardware Operating System Referred to as System -------- ---------------- -------------- --------- 486 PC FreeBSD FreeBSD freebsd 486 PC NetBSD NetBSD netbsd Trademarks ========== S/Key is a trademark of Bell Communications Research (Bellcore). UNIX is a trademark of Unix Systems Laboratories. NRL is a trademark of the U. S. Naval Research Laboratory. OPIE is in the public domain and hence cannot be legally trademarked by anyone. Availability ============ NRL OPIE 2.0 is copyrighted but freely available. It is now available From owner-freebsd-current Wed Jun 28 04:54:42 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA03565 for current-outgoing; Wed, 28 Jun 1995 04:54:42 -0700 Received: from dataplex.net (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA03559 for ; Wed, 28 Jun 1995 04:54:39 -0700 Received: from [199.183.109.242] by dataplex.net with SMTP (MailShare 1.0b8); Wed, 28 Jun 1995 06:54:35 -0500 X-Sender: wacky@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 28 Jun 1995 06:54:37 -0500 To: FreeBSD-current@freebsd.org (FreeBSD current) From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: Sysconfig routed setting Sender: current-owner@freebsd.org Precedence: bulk rgrimes@gndrsh.aac.dev.com writes: >Perhaps if sysinstall inforced this 4 point synopsis of what you have >to do to have your host understand routing: > > You either have to have a) a default route, b) run routed in some form > (the current defaults are good) to pick up rip packets off the wire, > c) gated (a non-trival thing to set up) or d) no network connection to > have your system work correctly. > >Give those 4 conditions the best default there is to ship the system >with (since you can't do the default route or gated configuration) is >to have routed -q started by default. > >If a person sets a default route, they can disable routed. >If a person sets up gated the can disable routed >If a person has no network connection, well, okay, it is wrong >for this one case, they could disable routed if they wanted to >free the process slot and some memory. > >IMHO, and evidently CSRG's as well, routed -q should be the default >it covers the widest cases. I support Rod's viewpoint. If we want to get fancy we can test for "gated" in the netstart code and supress the starting of "routed" there. Otherwise, what does it hurt to start it? ---- Richard Wackerbarth rkw@dataplex.net From owner-freebsd-current Wed Jun 28 08:12:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA08759 for current-outgoing; Wed, 28 Jun 1995 08:12:09 -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 IAA08737 for ; Wed, 28 Jun 1995 08:11:46 -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 <55622>; Wed, 28 Jun 1995 17:11:04 +0200 Received: (from jhs@localhost) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) id DAA22883; Mon, 26 Jun 1995 03:38:07 +0200 Date: Mon, 26 Jun 1995 03:38:07 +0200 From: Julian Howard Stacey Message-Id: <199506260138.DAA22883@vector.eikon.e-technik.tu-muenchen.de> To: rgrimes@gndrsh.aac.dev.com Subject: Re: Crypt code summary(2). Cc: current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk Rod, cc current@freebsd.org Re. your: > After that is done we would need a machine running > FreeBSD to set up the cvs/ctm/sup stuff on, heck if I am going to try > and port that to any other platform or even try!!! Thank you for having considered helping set up the international FreeBSD crypt site, but please do Not do this ! It should not be created or administered by people subject to USA law. Purpose of the site is to achieve something that would be illegal if done under USA legal jurisdiction, but is perfectly legal under other jurisdictions: namely the worldwide distribution of secure encryption (presumably both what the USA currently bans, & whatever encryption software the USA may later extend the ban to). If anyone subject to USA law helps set up or administer the non USA crypt site, they will by their very presence create a conflict of interests between intrusive USA legal requirements, their chances of arrest by US Feds, & FreeBSD world requirements for cryptographic software. If no USA citizens or residents are involved in the work, the US govt will have noone to prosecute. Leave this work to a non USA citizen in South Africa or Germany etc, If they need help they can ask you or others for advice, (If they are diplomatic, they'll ask for advice on CVS in general, with no specific reference as to purpose of the intended CVS FTP & mail base) No doubt the people who have already volunteered to set up this site will appreciate private mail from people who happen to notice anything in code that might embarass US citizens with their government. I wrote that I'd deny information about our crypt sources etc, to any USA government official. You seemed to think that illegal ?. Wrong. The site is to be outside the USA to avoid USA law. We Britons, Germans & S.Africans etc outside the USA are Not subject to USA law. My non co-operation with the USA government would be totally legal. If any USA law enforcement person shows up out of USA jurisdiction to question anyone involved in the new site, we can call the police to forcibly remove USA Feds from our territory, thus USA officials cannot force us to divulge information that might prejudice our USA FreeBSD friends. No USA citizen or resident should have write access to any of the crypt areas of the international site. With no write access, the USA government cannot prosecute you for aiding & abetting, also the International site is free from the danger of having the USA govt. say to one of its residents or citizens: Either you rlogin to SA/Germany right now, & delete that crypt stuff, or we're gonna' arrest you for [whatever they choose]. Please do not create a conflict of interest by involving yourself with the set up or admin of this site, it could compromise you with the US authorities, would create a conflict of interest, & would detract from the objective of a site independent of USA jurisdiction. Ref. the Aachen site, you asked me to let kuku@ speak for himself, hopefully he will, meantime I can tell you about a year or so ago he gave several of us facilities on that machine explicitly so we could create a 2nd site. We had no intention to restrict crypt code access, rather the opposite in fact. (The work didn't get done for a variety of reasons, but it's still on my list). I'd really appreciate if you just did crypt code integration issues (where you seem to be making progress :-), and left the issue of foreign sites & international law to us, the `foreign' site owners of the rest of the planet, we have our own laws, & intrusion of USA law is offensive. The safest solution to the problem the USA government has forced on us all, is if the citizens of the rest of the world arrange their own crypt site & mail list etc, without `write access' involvement of USA citizens or residents. If a USA citizen or resident is asked to help set up or admin a non USA crypt site, please refer the invitation to the lists, for non USA citizens or residents to work on instead. Of course, if someone in SA were to ask someone in the USA to set up a strawberry fruit crop CVS database, & after he'd finished, & had trained his successor, & had his write access removed, ... if at that point the site owners suddenly changed their site usage, then used it for ... well perhaps storing computer programs or something ... well, the guy who had done the initial install for strawberries might be in the clear (though it would still be be better if he'd not done the set up). (I mention this just in case any USA regulated person feels a burning desperate desire to config a CVS system somewhere, & is 110% certain that no one else on the planet outside the USA is available for the job ;-) Julian Stacey, Germany. Recommended , Alternate From owner-freebsd-current Wed Jun 28 08:56:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA10957 for current-outgoing; Wed, 28 Jun 1995 08:56:39 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA10951 ; Wed, 28 Jun 1995 08:56:33 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA00902; Wed, 28 Jun 1995 11:56:15 -0400 Date: Wed, 28 Jun 1995 11:56:15 -0400 From: Garrett Wollman Message-Id: <9506281556.AA00902@halloran-eldar.lcs.mit.edu> To: "Rodney W. Grimes" Cc: jkh@freebsd.org (Jordan K. Hubbard), FreeBSD-current@freebsd.org (FreeBSD current) Subject: Re: Paul Richards: sysconfig routed setting In-Reply-To: <199506280552.WAA08478@gndrsh.aac.dev.com> References: <8337.804273321@whisker.internet-eireann.ie> <199506280552.WAA08478@gndrsh.aac.dev.com> Sender: current-owner@freebsd.org Precedence: bulk < said: > ``Should'' and ``probably'' are not very convincing words, Let me word this more strongly: A machine which is not directly involved in forwarding packets has no business running a routing process, PERIOD. Routing processes run on routers and routers only. > If RIP > packets are on the wires you should damn well be sure you listen to > them in one way or another. Bull****. If RIP packets are on the wires, then it's the business of the routers which are exchanging them. If RIP packets are not on the wires, then it's the business of the routers which are exchanging some other routing protocol. If you are not a router, you have no business listening to them. HOSTS DO NOT NEED ROUTING INFORMATION. > Give those 4 conditions the best default there is to ship the system > with (since you can't do the default route or gated configuration) is > to have routed -q started by default. Actually, no, the best default is to ship the system with no routes at all, and force users if the indicate they are connected to the net to designate a default router. If they don't know the number to specify, then there should be somebody else in their shop who does. (If their shop is at all sensible, it will be numbered net.sub.net.1.) We actually have (broken) code in the source tree which could be used to listen for router advertisements and suggest a default to the user, but not all routers advertise. > IMHO, and evidently CSRG's as well, routed -q should be the default > it covers the widest cases. Which is just another example of a piece of Internet technology that CSRG got completely wrong and we are just now recovering from. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Wed Jun 28 09:19:20 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA11701 for current-outgoing; Wed, 28 Jun 1995 09:19:20 -0700 Received: from intercore.com (num1sun.intercore.com [205.198.76.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA11695 ; Wed, 28 Jun 1995 09:19:18 -0700 Received: (robin@localhost) by intercore.com (8.6.9/8.6.4) id MAA06455; Wed, 28 Jun 1995 12:15:51 -0400 From: Robin Cutshaw Message-Id: <199506281615.MAA06455@intercore.com> Subject: Re: Paul Richards: sysconfig routed setting To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Wed, 28 Jun 1995 12:15:50 -0400 (EDT) Cc: rgrimes@gndrsh.aac.dev.com, jkh@freebsd.org, FreeBSD-current@freebsd.org In-Reply-To: <9506281556.AA00902@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Jun 28, 95 11:56:15 am X-Mailer: ELM [version 2.4 PL21] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 867 Sender: current-owner@freebsd.org Precedence: bulk > > < said: > > > ``Should'' and ``probably'' are not very convincing words, > > Let me word this more strongly: > > A machine which is not directly involved in forwarding packets > has no business running a routing process, PERIOD. Routing > processes run on routers and routers only. > I'm not sure that I agree with this. One of the purposes of routed -q is to allow a host to make an intelligent decision as to where to send an originated packet. I've got several routers on a network and several routers one or two networks deep so I prefer to send packets (that my host originates) to the appropriate router. You could argue that I should use a default and suffer from either slower throughput or redirects but I would argue that this is inadequate. robin From owner-freebsd-current Wed Jun 28 09:30:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA12092 for current-outgoing; Wed, 28 Jun 1995 09:30:37 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA12086 for ; Wed, 28 Jun 1995 09:30:29 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA01016; Wed, 28 Jun 1995 12:30:14 -0400 Date: Wed, 28 Jun 1995 12:30:14 -0400 From: Garrett Wollman Message-Id: <9506281630.AA01016@halloran-eldar.lcs.mit.edu> To: Robin Cutshaw Cc: FreeBSD-current@freebsd.org Subject: Re: Paul Richards: sysconfig routed setting In-Reply-To: <199506281615.MAA06455@intercore.com> References: <9506281556.AA00902@halloran-eldar.lcs.mit.edu> <199506281615.MAA06455@intercore.com> Sender: current-owner@freebsd.org Precedence: bulk < said: > I've got several routers on a network and > several routers one or two networks deep so I prefer to send packets > (that my host originates) to the appropriate router. There is a protocol for router discovery that someone (I think Paul Traina) imported an implementation of. Unfortunately, the code is not in a compilable state, and nobody appears to have touched it since it was imported. This is the right solution to your concern. > You could argue that I should use a default and suffer from either > slower throughput or redirects but I would argue that this is > inadequate. Nonetheless, it is the way the Internet architecture (second edition) was designed. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Wed Jun 28 09:56:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA12909 for current-outgoing; Wed, 28 Jun 1995 09:56: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 JAA12903 for ; Wed, 28 Jun 1995 09:56:30 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id JAA09801; Wed, 28 Jun 1995 09:53:36 -0700 From: "Rodney W. Grimes" Message-Id: <199506281653.JAA09801@gndrsh.aac.dev.com> Subject: Re: Crypt code summary(2). To: jhs@vector.eikon.e-technik.tu-muenchen.de (Julian Howard Stacey) Date: Wed, 28 Jun 1995 09:53:36 -0700 (PDT) Cc: current@freebsd.org In-Reply-To: <199506260138.DAA22883@vector.eikon.e-technik.tu-muenchen.de> from "Julian Howard Stacey" at Jun 26, 95 03:38:07 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: 5283 Sender: current-owner@freebsd.org Precedence: bulk > > > Rod, cc current@freebsd.org > > Re. your: > > > After that is done we would need a machine running > > FreeBSD to set up the cvs/ctm/sup stuff on, heck if I am going to try > > and port that to any other platform or even try!!! > > Thank you for having considered helping set up the > international FreeBSD crypt site, but please do Not do this ! > It should not be created or administered by people subject to USA law. Okay, fine by me, one less thing for me to do! > Purpose of the site is to achieve something that would be illegal if > done under USA legal jurisdiction, but is perfectly legal under other ... > > I wrote that I'd deny information about our crypt sources etc, You wrote that you suggest we ``all'' deny information, big difference between what YOU do and what you ask US to do!! > to any USA government official. You seemed to think that illegal ?. Wrong. > The site is to be outside the USA to avoid USA law. > We Britons, Germans & S.Africans etc outside the USA are Not subject to > USA law. As long as you keep your communications and actions totally outside of the USA that is true. But your suggestion that we all refuse to talk to the feds about this crypto stuff would, with reasonable high probability, land a US citizen doing that in jail. > My non co-operation with the USA government would be totally legal. Yes, yours is, mine is not. Your original statement was far to broad. > If any USA law enforcement person shows up out of USA jurisdiction to question > anyone involved in the new site, we can call the police to forcibly remove > USA Feds from our territory, thus USA officials cannot force us to divulge > information that might prejudice our USA FreeBSD friends. You will find that if the USA feds are going to try to do something out of the USA jurisdiction they would have already contacted your police and your police will probably be right there with them to take action on behalf of the USA's officiers. Have you ever heard of mutual enforcement agreements? > No USA citizen or resident should have write access to any of the crypt areas > of the international site. With no write access, the USA government cannot > prosecute you for aiding & abetting, also the International site is free from > the danger of having the USA govt. say to one of its residents or citizens: > Either you rlogin to SA/Germany right now, & delete that crypt > stuff, or we're gonna' arrest you for [whatever they choose]. > > Please do not create a conflict of interest by involving yourself with the > set up or admin of this site, it could compromise you with the US authorities, > would create a conflict of interest, & would detract from the objective of > a site independent of USA jurisdiction. Okay, fine, I am no longer involved... > Ref. the Aachen site, you asked me to let kuku@ speak for himself, hopefully > he will, meantime I can tell you about a year or so ago he gave several > of us facilities on that machine explicitly so we could create a 2nd site. And I did go over there, and set some things up, and do have write access to bits over there, and did even break a few laws doing it but cleaned up after myself. So, you might say, this machine is now tainted as I was the one who setup sup and cvs over there :-(. > We had no intention to restrict crypt code access, rather the opposite > in fact. > (The work didn't get done for a variety of reasons, but it's still on my > list). > > I'd really appreciate if you just did crypt code integration issues (where you > seem to be making progress :-), and left the issue of foreign sites & > international law to us, the `foreign' site owners of the rest of the planet, > we have our own laws, & intrusion of USA law is offensive. > > The safest solution to the problem the USA government has forced on us all, > is if the citizens of the rest of the world arrange their own crypt site & > mail list etc, without `write access' involvement of USA citizens or > residents. > If a USA citizen or resident is asked to help set up or admin a non USA crypt > site, please refer the invitation to the lists, for non > USA citizens or residents to work on instead. Under those conditions the Aachen site of kuku@ is tainted and can not be used. > > Of course, if someone in SA were to ask someone in the USA to > set up a strawberry fruit crop CVS database, & after he'd finished, & had > trained his successor, & had his write access removed, ... if at that point > the site owners suddenly changed their site usage, then used it for ... well > perhaps storing computer programs or something ... well, the guy who had done > the initial install for strawberries might be in the clear > (though it would still be be better if he'd not done the set up). > (I mention this just in case any USA regulated person feels a burning > desperate desire to config a CVS system somewhere, & is 110% certain that no > one else on the planet outside the USA is available for the job ;-) > > Julian Stacey, Germany. > Recommended , Alternate > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Jun 28 10:15:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA13722 for current-outgoing; Wed, 28 Jun 1995 10:15:25 -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 KAA13715 ; Wed, 28 Jun 1995 10:15:21 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id KAA09858; Wed, 28 Jun 1995 10:15:18 -0700 From: "Rodney W. Grimes" Message-Id: <199506281715.KAA09858@gndrsh.aac.dev.com> Subject: Re: Paul Richards: sysconfig routed setting To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Wed, 28 Jun 1995 10:15:18 -0700 (PDT) Cc: jkh@freebsd.org, FreeBSD-current@freebsd.org In-Reply-To: <9506281556.AA00902@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Jun 28, 95 11:56:15 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: 3286 Sender: current-owner@freebsd.org Precedence: bulk > > < said: > > > ``Should'' and ``probably'' are not very convincing words, > > Let me word this more strongly: > > A machine which is not directly involved in forwarding packets > has no business running a routing process, PERIOD. Routing > processes run on routers and routers only. > > > If RIP > > packets are on the wires you should damn well be sure you listen to > > them in one way or another. > > Bull****. If RIP packets are on the wires, then it's the business of > the routers which are exchanging them. If RIP packets are not on the > wires, then it's the business of the routers which are exchanging some > other routing protocol. If you are not a router, you have no business > listening to them. HOSTS DO NOT NEED ROUTING INFORMATION. HOSTS REQUIRE ROUTING INFORMATION!!! A default route is ROUTING INFORMATION. > > Give those 4 conditions the best default there is to ship the system > > with (since you can't do the default route or gated configuration) is > > to have routed -q started by default. > > Actually, no, the best default is to ship the system with no routes at > all, and force users if the indicate they are connected to the net to > designate a default router. A default router is not always the appropriate solution in a multiple routed network environment and will fail if the default router is powered down and the work load takeing over by a secondary router. Any site who gives a hoot about network reliability has back up routers, and runs RIP or other dynamic route listners on every single host. > If they don't know the number to specify, > then there should be somebody else in their shop who does. (If their > shop is at all sensible, it will be numbered net.sub.net.1.) We > actually have (broken) code in the source tree which could be used to > listen for router advertisements and suggest a default to the user, > but not all routers advertise. > > > IMHO, and evidently CSRG's as well, routed -q should be the default > > it covers the widest cases. > > Which is just another example of a piece of Internet technology that > CSRG got completely wrong and we are just now recovering from. Seems we disagree. How many large network sites have you had to administer, and how many times have you installed back up routers and networks that must meet a 7 day x 24 hour up time requirement? Have you ever been responsible for actaully deploying and makeing a 200+ node network stay alive on a day to day basis? Do all of your networks client class machines run with a ``default route'' or other static route information that would fall flat on it's face if I came in and powered down your default router and/or had to do a full network upgrade that would replace all existing routers? Been there, done that, default routes are fine for small static networks, but fall to pieces in any sizeable changing structure. You might hate routed and the RIP protocol (and I agree it is not very eligant) but it does get the job done for the a very large mass of the world. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Jun 28 10:20:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA14014 for current-outgoing; Wed, 28 Jun 1995 10:20:45 -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 KAA14008 for ; Wed, 28 Jun 1995 10:20:43 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id KAA09888; Wed, 28 Jun 1995 10:20:34 -0700 From: "Rodney W. Grimes" Message-Id: <199506281720.KAA09888@gndrsh.aac.dev.com> Subject: Re: Paul Richards: sysconfig routed setting To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Wed, 28 Jun 1995 10:20:34 -0700 (PDT) Cc: robin@intercore.com, FreeBSD-current@freebsd.org In-Reply-To: <9506281630.AA01016@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Jun 28, 95 12:30:14 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: 1231 Sender: current-owner@freebsd.org Precedence: bulk > > < said: > > > I've got several routers on a network and > > several routers one or two networks deep so I prefer to send packets > > (that my host originates) to the appropriate router. > > There is a protocol for router discovery that someone (I think Paul > Traina) imported an implementation of. Unfortunately, the code is not > in a compilable state, and nobody appears to have touched it since it > was imported. This is the right solution to your concern. Okay, great, when this works and can fully replace what routed -q does, I am all for it!! But until THEN, nothing is going to convince me that we should change the current default of routed -q. > > > You could argue that I should use a default and suffer from either > > slower throughput or redirects but I would argue that this is > > inadequate. > > Nonetheless, it is the way the Internet architecture (second edition) > was designed. And you think that CSRG screwed up??? WTF is going on, we are going backwards!!! -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Jun 28 11:35:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA17257 for current-outgoing; Wed, 28 Jun 1995 11:35:57 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA17251 ; Wed, 28 Jun 1995 11:35:53 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id MAA03494; Wed, 28 Jun 1995 12:37:45 -0600 Date: Wed, 28 Jun 1995 12:37:45 -0600 Message-Id: <199506281837.MAA03494@rocky.sri.MT.net> To: Garrett Wollman Cc: "Rodney W. Grimes" , jkh@freebsd.org (Jordan K. Hubbard), FreeBSD-current@freebsd.org (FreeBSD current) Subject: Re: Paul Richards: sysconfig routed setting In-Reply-To: <9506281556.AA00902@halloran-eldar.lcs.mit.edu> References: <8337.804273321@whisker.internet-eireann.ie> <199506280552.WAA08478@gndrsh.aac.dev.com> <9506281556.AA00902@halloran-eldar.lcs.mit.edu> Reply-To: nate@sneezy.sri.com (Nate Williams) From: nate@sneezy.sri.com (Nate Williams) Sender: current-owner@freebsd.org Precedence: bulk > If you are not a router, you have no business > listening to them. HOSTS DO NOT NEED ROUTING INFORMATION. OK, given your assertion's, HOW is machine B supposed to send data to my machine? Ethernet = SLIP/PPP * machine-A<=>machine-B<=>machine-C<*>{internet} ^ * v Nate's box I have two options, and I chose the latter since it's much easier to setup because we have other boxes also sitting off the machines in the network. 1) Have machine A arp for my IP address. 2) Have machine A declare itself a router from my IP address With your assumption, machine B does is not running any routing software, so therefore it does not know to send packets to machine A in order to get to my machine. Note, there are many machines similar to machine B in my network, and I'm not about to add static routes to every one of them to force routing to my machine. Nate From owner-freebsd-current Wed Jun 28 11:39:38 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA17452 for current-outgoing; Wed, 28 Jun 1995 11:39:38 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA17442 ; Wed, 28 Jun 1995 11:39:28 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA01339; Wed, 28 Jun 1995 14:39:20 -0400 Date: Wed, 28 Jun 1995 14:39:20 -0400 From: Garrett Wollman Message-Id: <9506281839.AA01339@halloran-eldar.lcs.mit.edu> To: nate@sneezy.sri.com (Nate Williams) Cc: Garrett Wollman , "Rodney W. Grimes" , jkh@freebsd.org (Jordan K. Hubbard), FreeBSD-current@freebsd.org (FreeBSD current) Subject: Re: Paul Richards: sysconfig routed setting In-Reply-To: <199506281837.MAA03494@rocky.sri.MT.net> References: <8337.804273321@whisker.internet-eireann.ie> <199506280552.WAA08478@gndrsh.aac.dev.com> <9506281556.AA00902@halloran-eldar.lcs.mit.edu> <199506281837.MAA03494@rocky.sri.MT.net> Sender: current-owner@freebsd.org Precedence: bulk <> If you are not a router, you have no business >> listening to them. HOSTS DO NOT NEED ROUTING INFORMATION. > OK, given your assertion's, HOW is machine B supposed to send data to > my machine? > Ethernet = > SLIP/PPP * > machine-A<=>machine-B<=>machine-C<*>{internet} > ^ > * > v > Nate's box Machine A is a router. It runs a routing protocol. > With your assumption, machine B does is not running any routing > software, so therefore it does not know to send packets to machine A in > order to get to my machine. Machine B has a default router R. R and A exchange routing protocol packets to inform each other of their locations. When machine B sends a packet for `Nate's box' to R, R sends an ICMP redirect back to B telling it that `Nate's box' should be reached by way of A, and B sends future packets directly. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Wed Jun 28 13:18:41 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA20942 for current-outgoing; Wed, 28 Jun 1995 13:18:41 -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 NAA20935 ; Wed, 28 Jun 1995 13:18:26 -0700 Received: by haven.uniserve.com id <30814>; Wed, 28 Jun 1995 13:18:42 +0100 Date: Wed, 28 Jun 1995 13:18:34 -0700 (PDT) From: Tom Samplonius To: Garrett Wollman cc: "Rodney W. Grimes" , "Jordan K. Hubbard" , FreeBSD current Subject: Re: Paul Richards: sysconfig routed setting In-Reply-To: <9506281556.AA00902@halloran-eldar.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk On Wed, 28 Jun 1995, Garrett Wollman wrote: > listening to them. HOSTS DO NOT NEED ROUTING INFORMATION. When there are multiple routers, how do you recommend that hosts be setup? Tom From owner-freebsd-current Wed Jun 28 13:31:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA21482 for current-outgoing; Wed, 28 Jun 1995 13:31:57 -0700 Received: from intercore.com (num1sun.intercore.com [205.198.76.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA21476 for ; Wed, 28 Jun 1995 13:31:55 -0700 Received: (robin@localhost) by intercore.com (8.6.9/8.6.4) id QAA07676; Wed, 28 Jun 1995 16:28:37 -0400 From: Robin Cutshaw Message-Id: <199506282028.QAA07676@intercore.com> Subject: Re: Paul Richards: sysconfig routed setting To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Wed, 28 Jun 1995 16:28:36 -0400 (EDT) Cc: freebsd-current@freebsd.org In-Reply-To: <9506281630.AA01016@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Jun 28, 95 12:30:14 pm X-Mailer: ELM [version 2.4 PL21] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1175 Sender: current-owner@freebsd.org Precedence: bulk > > < said: > > > I've got several routers on a network and > > several routers one or two networks deep so I prefer to send packets > > (that my host originates) to the appropriate router. > > There is a protocol for router discovery that someone (I think Paul > Traina) imported an implementation of. Unfortunately, the code is not > in a compilable state, and nobody appears to have touched it since it > was imported. This is the right solution to your concern. > And, unfortunately, not all routers implement this protocol (i.e. ascend). > > You could argue that I should use a default and suffer from either > > slower throughput or redirects but I would argue that this is > > inadequate. > > Nonetheless, it is the way the Internet architecture (second edition) > was designed. > The "Internet architecture"? Are you refering to a specific routing protocol (like BGP) or a biblical reference? :-) I still believe that in a high performance, production network you may want any given host, router or not, to know the best, most efficient route to it's clients/servers. robin From owner-freebsd-current Wed Jun 28 13:35:08 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA21714 for current-outgoing; Wed, 28 Jun 1995 13:35:08 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA21708 for ; Wed, 28 Jun 1995 13:35:01 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA01626; Wed, 28 Jun 1995 16:34:53 -0400 Date: Wed, 28 Jun 1995 16:34:53 -0400 From: Garrett Wollman Message-Id: <9506282034.AA01626@halloran-eldar.lcs.mit.edu> To: Robin Cutshaw Cc: freebsd-current@freebsd.org Subject: Re: Paul Richards: sysconfig routed setting In-Reply-To: <199506282028.QAA07676@intercore.com> References: <9506281630.AA01016@halloran-eldar.lcs.mit.edu> <199506282028.QAA07676@intercore.com> Sender: current-owner@freebsd.org Precedence: bulk < said: > The "Internet architecture"? Are you refering to a specific routing > protocol (like BGP) or a biblical reference? :-) It's a biblical reference. In the Internet Architecture, there are two sorts of network nodes: hosts and gateways. Gateways may run a routing protocol, forward packets, send ICMP redirects, and otherwise, well, route. Hosts may do none of these things. What the Internet pioneers called a `gateway' is what is now called a `router'. (What is now called a `gateway' was to them a `mailbridge'.) -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Wed Jun 28 16:11:59 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA26732 for current-outgoing; Wed, 28 Jun 1995 16:11: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 QAA26724 ; Wed, 28 Jun 1995 16:11: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 BAA08538 ; Thu, 29 Jun 1995 01:11:52 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id BAA00831 ; Thu, 29 Jun 1995 01:11:51 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199506282311.BAA00831@blaise.ibp.fr> Subject: Re: Paul Richards: sysconfig routed setting To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Thu, 29 Jun 1995 01:11:51 +0200 (MET DST) Cc: rgrimes@gndrsh.aac.dev.com, jkh@freebsd.org, FreeBSD-current@freebsd.org In-Reply-To: <9506281556.AA00902@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Jun 28, 95 11:56:15 am X-Operating-System: FreeBSD BUILT-19950501 ctm#617 X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 588 Sender: current-owner@freebsd.org Precedence: bulk > other routing protocol. If you are not a router, you have no business > listening to them. HOSTS DO NOT NEED ROUTING INFORMATION. I agree with Garrett on this one. You only need routed/gated if you have than one interface and you are a router. If you have a single segment you don't need a default route and if you have multiple segments and/or connections (PPP, SLIP, whatever) then you always have a router to put a defaultroute to. -- 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 Wed Jun 28 18:48:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA01944 for current-outgoing; Wed, 28 Jun 1995 18:48:58 -0700 Received: from postie.das.gov.au (postie.das.gov.au [147.211.53.231]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA01935 for ; Wed, 28 Jun 1995 18:48:54 -0700 Received: from zeus.das.gov.au by postie.das.gov.au with SMTP (1.38.193.5/16.2) id AA14831; Thu, 29 Jun 1995 11:53:35 +1000 From: Charles Smith Received: by zeus.das.gov.au (4.1) id AA03984; Thu, 29 Jun 95 11:44:45 EST Message-Id: <9506290144.AA03984@zeus.das.gov.au> Subject: Re: Boot support for Adaptec 2940 PCI Controller (fwd) To: current@FreeBSD.org Date: Thu, 29 Jun 1995 11:44:45 +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: 2674 Sender: current-owner@FreeBSD.org Precedence: bulk Any news for the patch to support 2.0 PCI Compac System with the ahc0 Driver ? Following mail tells all. regards Charles Smith Forwarded message: > From gibbs@freefall.cdrom.com Wed Jun 28 16:35:22 1995 > Message-Id: <199506280638.XAA24349@freefall.cdrom.com> > X-Authentication-Warning: freefall.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol > To: Charles Smith > Cc: gibbs@freebsd.org > Subject: Re: Boot support for Adaptec 2940 PCI Controller > In-Reply-To: Your message of "Wed, 28 Jun 95 16:10:14 +1000." > <9506280610.AA01115@zeus.das.gov.au> > Date: Tue, 27 Jun 1995 23:38:37 -0700 > From: "Justin T. Gibbs" > > >Justin, > > > >My name is Charles Smith and the Australian Government Department > >I am working in has tasked me with the installation and management of > >FreeBSD running on Pentium Based Systems for its primary Domain Name Server, > >Mail Gateway, httpd servers and nntp Servers. > > Yeah! Is amazing where you find FreeBSD these days. :) You may want to > submit an entry for our Web site's list of "Where you'll find FreeBSD". > > >We wish to use (YECH!!!) Compac PCI based Systems with the ADAPTEC 2940 > >SCSI Controller and Seagate Hawk 4 SCSI DISKS. > > > >I tried to install BSD2.0.5 and low and behold the boot disk distribution > >did not have the "ahc0" device driver. The README said that ahc0 was > >supported. Is it ? and if so how do I create an install disk that includes > >the ahc0 drivers. I have checked the system out using "-c" config option > >and the driver is definetely not there. > > Ahhhh. The problem you are seeing is not that the ahc driver is not > in the kernel, but that the Compaq is a 2.0 PCI machine and the > PCI code that was released in 2.0.5 did not properly probe the Compaq. > I'm not sure if the proposed patch for this problem has been put into > the tree yet, but I'm sure that a quick post to current@FreeBSD.org > will find you the two or three people who reported this problem and > are testing Stephan's patch to the PCI code. I'm sure one of them > will be able to provide you with a boot floppy. > > Once your up, if you do have any problems with the aic7xxx driver, don't > hesitate to drop me a note. > > Good Luck! > > > Gary > >++++++++++++++ > > > >Regards Charles Smith. > > > >P.S. Keep up the great work. The OS is UNIX as it should be!!! > > -- > Justin T. Gibbs > =========================================== > Software Developer - Walnut Creek CDROM > FreeBSD: Turning PCs into workstations > =========================================== > From owner-freebsd-current Wed Jun 28 21:22:03 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA07375 for current-outgoing; Wed, 28 Jun 1995 21:22:03 -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 VAA07365 for ; Wed, 28 Jun 1995 21:21:56 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA17170; Thu, 29 Jun 1995 06:21:53 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id GAA18355 for freebsd-current@FreeBSD.org; Thu, 29 Jun 1995 06:21:52 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id FAA04362 for freebsd-current@FreeBSD.org; Thu, 29 Jun 1995 05:44:58 +0200 From: J Wunsch Message-Id: <199506290344.FAA04362@uriah.heep.sax.de> Subject: Re: Paul Richards: sysconfig routed setting To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 29 Jun 1995 05:44:56 +0200 (MET DST) Reply-To: freebsd-current@FreeBSD.org (FreeBSD-current users) In-Reply-To: <9506281556.AA00902@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Jun 28, 95 11:56:15 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: 1831 Sender: current-owner@FreeBSD.org Precedence: bulk As Garrett Wollman wrote: > > > If RIP > > packets are on the wires you should damn well be sure you listen to > > them in one way or another. > > Bull****. If RIP packets are on the wires, then it's the business of > the routers which are exchanging them. Interesting. How do you solve the following then? (NB: The following networks are not Internet-connected, even though i'm using domain names. They form a private IP network.) tcd-dresden.de does have two machines on its local ethernet that are acting as routers. lam.tcd-dresden.de is often running PPP over ISDN to connect the network to eat-kempen.de. As long as the link is ready, it should be announced within tcd-dresden.de's ethernet, so all hosts can reach the hosts @eat-kempen.de. bonnie.tcd-dresden.de does have a modem, and occasionally people are logging in through the modem and run SLIP. As soon as somebody did this, his host route shall also be announced throughout the ethernet so he can use all hosts out of tcd-dresden.de. (It's not necessary to exchange routing information for this via lam's PPP link.) There are several hosts that could log in via SLIP, they do have a variety of IP addresses (sometimes out of the range that's normally belonging to tcd-dresden.de's class C net, but not necessarily). Right now i've been solving this running gated's on the gateways that are going to forward RIP announcements to the ethernet, and have routed -q's (listening-only routed's) on all non-gateway hosts, so they can adjust their kernel routing tables as soon as some of the external routes are being announced. Everything is working as desired. I'm curious how to solve this withouth routed's. -- 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 Wed Jun 28 21:30:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA07907 for current-outgoing; Wed, 28 Jun 1995 21:30:58 -0700 Received: from virgo.ai.net (root@virgo.ai.net [198.69.44.2]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA07901 for ; Wed, 28 Jun 1995 21:30:56 -0700 Received: from aries.ai.net (aries.ai.net [198.69.44.1]) by virgo.ai.net (8.6.11/8.6.12) with ESMTP id AAA00481; Thu, 29 Jun 1995 00:33:28 -0400 Received: (from nc@localhost) by aries.ai.net (8.6.11/8.6.12) id AAA05403; Thu, 29 Jun 1995 00:30:48 -0400 Date: Thu, 29 Jun 1995 00:30:48 -0400 (EDT) From: Network Coordinator To: FreeBSD-current users , Joerg Wunsch cc: FreeBSD-current users Subject: Re: Paul Richards: sysconfig routed setting In-Reply-To: <199506290344.FAA04362@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk > Right now i've been solving this running gated's on the gateways that > are going to forward RIP announcements to the ethernet, and have > routed -q's (listening-only routed's) on all non-gateway hosts, so > they can adjust their kernel routing tables as soon as some of the > external routes are being announced. Everything is working as > desired. > > I'm curious how to solve this withouth routed's. I would think you would solve this the way everyone else does. For packets that are local on the ethernet, send directly to that machine, if they are not, forward to one of the routers. Afterall, that's what a router is for. -Jerry. From owner-freebsd-current Thu Jun 29 00:38:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA15152 for current-outgoing; Thu, 29 Jun 1995 00:38:06 -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 AAA15146 ; Thu, 29 Jun 1995 00:38:03 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id AAA10884; Thu, 29 Jun 1995 00:34:08 -0700 From: "Rodney W. Grimes" Message-Id: <199506290734.AAA10884@gndrsh.aac.dev.com> Subject: Re: Paul Richards: sysconfig routed setting To: roberto@blaise.ibp.fr (Ollivier Robert) Date: Thu, 29 Jun 1995 00:34:08 -0700 (PDT) Cc: wollman@halloran-eldar.lcs.mit.edu, jkh@freebsd.org, FreeBSD-current@freebsd.org In-Reply-To: <199506282311.BAA00831@blaise.ibp.fr> from "Ollivier Robert" at Jun 29, 95 01:11:51 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: 1884 Sender: current-owner@freebsd.org Precedence: bulk > > > other routing protocol. If you are not a router, you have no business > > listening to them. HOSTS DO NOT NEED ROUTING INFORMATION. > > I agree with Garrett on this one. You only need routed/gated if you have > than one interface and you are a router. ^more Pretty hard to be router with out more than 1 interface :-) > If you have a single segment > you don't need a default route and if you have multiple segments and/or > connections (PPP, SLIP, whatever) then you always have a router to put > a defaultroute to. Evedintly no one has read my posting about more than one router and what happens if you use defaultroutes and the ``default'' router who would normally provide ``better'' redirects has crashed. Also some one poined out the performance side issue and all those uneeded redirects, unnessary use of a router is bad for the router as well, another thing I have first hand experince with. Nope, sorry, I have done way way to many reliable network setups and know that ``defaultroute'' is an evil ugly thing to do. Ever try to slap in a spare box at a different IP address to be the emergency router and have to go change defaultroutes on 200 hosts so you can debug the broken router but keep people up and running, can you say ``not fun!!!'. Look, this is all very simple really, routed -q works today for all most every one, and has for a very very long time. I know it is ugly, RIP sucks, it should and WILL dies. We don't have the elegant solution yet, but should some day soon. Until then just leave it alone, don't make it worse. > > -- > 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 > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Thu Jun 29 02:01:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA17994 for current-outgoing; Thu, 29 Jun 1995 02:01:02 -0700 Received: from FileServ1.MI.Uni-Koeln.DE (FileServ1.MI.Uni-Koeln.DE [134.95.212.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id CAA17978 for ; Thu, 29 Jun 1995 02:00:57 -0700 Received: by FileServ1.MI.Uni-Koeln.DE id AA05695 (5.67b/IDA-1.5 for current@freebsd.org); Thu, 29 Jun 1995 10:54:22 +0200 Message-Id: <199506290854.AA05695@FileServ1.MI.Uni-Koeln.DE> From: esser@zpr.uni-koeln.de (Stefan Esser) Date: Thu, 29 Jun 1995 10:54:21 +0200 In-Reply-To: Charles Smith "Re: Boot support for Adaptec 2940 PCI Controller (fwd)" (Jun 29, 11:44) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Charles Smith Subject: Re: Boot support for Adaptec 2940 PCI Controller (fwd) Cc: current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk On Jun 29, 11:44, Charles Smith wrote: } Subject: Re: Boot support for Adaptec 2940 PCI Controller (fwd) } Any news for the patch to support 2.0 PCI Compac System with the } ahc0 Driver ? The problem with the Compaq is not, that is a PCI 2.0 compliant systems (these are quite common), but that the Compaq was identified as using an old PCI configuration mechanism, when it in fact uses the new one ... There is modified probe code in FreeBSD-current, which has been successfully tested on Compaq Prosignea and Compaq Prolinea systems. Don't know about you environment: Can you build a kernel on another machine or using some other controller (or possible an IDE disk drive ?). There currently is no boot floppy with the new PCI probe code, but I could try to build one, if this is the only possibility to get your system installed. Regards, STefan From owner-freebsd-current Thu Jun 29 05:28:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA22658 for current-outgoing; Thu, 29 Jun 1995 05:28:12 -0700 Received: from news.rim.or.jp (news.rim.or.jp [202.255.181.3]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA22651 ; Thu, 29 Jun 1995 05:28:07 -0700 Received: (from uucp@localhost) by news.rim.or.jp (8.6.10+2.4W/3.3W-rim1.0) with UUCP id VAA17434; Thu, 29 Jun 1995 21:28:02 +0900 Received: from us.and.or.jp (localhost [127.0.0.1]) by us.and.or.jp (8.6.11/3.4W) with ESMTP id UAA00299; Thu, 29 Jun 1995 20:51:18 +0900 Message-Id: <199506291151.UAA00299@us.and.or.jp> Reply-To: sa2c@st.rim.or.jp To: se@freebsd.org cc: current@freebsd.org Subject: new PCI probe code and ASUS AP4 Date: Thu, 29 Jun 1995 20:51:17 +0900 From: NIIMI Satoshi Sender: current-owner@freebsd.org Precedence: bulk I've noticed that the new PCI probe code doesn't find a PCI bus on my ASUS PVI-486AP4 (Aries chipset). The problem is that if out(CONF1_ADDR_PORT, CONF1_ENABLE_CHK), then inl(CONF1_ADDR_PORT) is equal to CONF1_ENABLE_CHK (not CONF1_ENABLE). Here is patch that works for me. --- pcibus.c.org Thu Jun 29 13:21:19 1995 +++ pcibus.c Thu Jun 29 20:48:36 1995 @@ -164,7 +164,7 @@ result = inl (CONF1_ADDR_PORT); outl (CONF1_ADDR_PORT, oldval); - if (result == CONF1_ENABLE) { + if (result & CONF1_ENABLE) { pci_mechanism = 1; pci_maxdevice = 32; return; -- $B?78+3P;V(B / NIIMI Satoshi From owner-freebsd-current Thu Jun 29 08:26:31 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA27863 for current-outgoing; Thu, 29 Jun 1995 08:26:31 -0700 Received: from freebsd.netcraft.co.uk (lambda.demon.co.uk [158.152.17.124]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA27854 ; Thu, 29 Jun 1995 08:26:14 -0700 Received: (from paul@localhost) by freebsd.netcraft.co.uk (8.6.11/8.6.9) id QAA13229; Thu, 29 Jun 1995 16:23:38 +0100 From: Paul Richards Message-Id: <199506291523.QAA13229@freebsd.netcraft.co.uk> Subject: Re: Paul Richards: sysconfig routed setting To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Thu, 29 Jun 1995 16:23:38 +0100 (BST) Cc: nate@sneezy.sri.com, wollman@halloran-eldar.lcs.mit.edu, rgrimes@gndrsh.aac.dev.com, jkh@freebsd.org, FreeBSD-current@freebsd.org In-Reply-To: <9506281839.AA01339@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Jun 28, 95 02:39:20 pm Reply-to: paul@freebsd.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 2165 Sender: current-owner@freebsd.org Precedence: bulk In reply to Garrett Wollman who said > > < > > Ethernet = > > SLIP/PPP * > > > machine-A<=>machine-B<=>machine-C<*>{internet} > > ^ > > * > > v > > Nate's box > > > Machine A is a router. It runs a routing protocol. I'm not even sure that is necessary, since Nate's box is the only machine hanging off the slip link proxy ARP would be a better set up. Machine A proxy-ARP's Nate's address so that Nate's box appears to be on the ethernet. Nate's box will obvious have a default route to machine A and if A has appropriate netmasks for it's two interfaces it will know that packet's for Nate's box go out the slip link. It's is a router but it wouldn't be necessary to run a routing deamon on it. > > > With your assumption, machine B does is not running any routing > > software, so therefore it does not know to send packets to machine A in > > order to get to my machine. > > Machine B has a default router R. R and A exchange routing protocol > packets to inform each other of their locations. When machine B sends > a packet for `Nate's box' to R, R sends an ICMP redirect back to B > telling it that `Nate's box' should be reached by way of A, and B > sends future packets directly. If A does proxy ARP then B will send packets to A and A will forward them across the slip link without having to run a routed. This is an exception though and Garrett's description above expalins the more general case, if for example there were several boxes off the slip link to Nate's machine. We're getting off the point a bit though, which is whether routed should be enabled by default. I still think the only time it should be run is if the box has a real need to exchange RIP info with other routers and in those cases the admin will know enough to make that decision. For most boxes it's not needed. -- Paul Richards, Bluebird Computer Systems. FreeBSD core team member. Internet: paul@FreeBSD.org, http://www.freebsd.org/~paul Phone: 0370 462071 (Mobile), +44 1222 457651 (home) From owner-freebsd-current Thu Jun 29 09:16:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA29763 for current-outgoing; Thu, 29 Jun 1995 09:16:47 -0700 Received: from colin.muc.de (root@colin.muc.de [193.174.4.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA29757 for ; Thu, 29 Jun 1995 09:16:44 -0700 Received: from totum by colin.muc.de with UUCP id <25560-2>; Thu, 29 Jun 1995 18:16:17 +0200 Received: (from root@localhost) by totum.muc.de (8.6.11/8.6.9) id SAA00218; Thu, 29 Jun 1995 18:40:13 +0200 Date: Thu, 29 Jun 1995 18:40:11 +0200 From: Michael Reifenberger To: FreeBSD-Current Subject: panic: spec_badop called Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk With a current kernel, on a r/o mounted root and a r/w mounted /mnt I do: `find /dev | cpio -pdamuv /mnt` and get after some copies the panic listed above. (I know that the -a flag does not work on r/o FSs) Can anyone else reproduce this? Bye! ---- Michael Reifenberger From owner-freebsd-current Thu Jun 29 09:45:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA00409 for current-outgoing; Thu, 29 Jun 1995 09:45:55 -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 JAA00389 ; Thu, 29 Jun 1995 09:45:50 -0700 Received: (lix@localhost) by cs.pdx.edu (8.6.10/CATastrophe-12/23/94-P) id JAA20067; Thu, 29 Jun 1995 09:45:39 -0700 for Date: Thu, 29 Jun 1995 09:45:39 -0700 From: lix@cs.pdx.edu (xiaoyin li) Message-Id: <199506291645.JAA20067@cs.pdx.edu> To: current@FreeBSD.org, questions@FreeBSD.org Subject: xmosaic Sender: current-owner@FreeBSD.org Precedence: bulk I am looking for an "xmosaic" software for FreeBSD system. I would appreciate very much if someone could provide me information where I can get it from ftp public domain. Thank you, Xiaoyin Li System Administrator PSU Bookstore Tel: (503)226-2631 Email: lix@rigel.cs.pdx.edu From owner-freebsd-current Thu Jun 29 10:56:20 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA02507 for current-outgoing; Thu, 29 Jun 1995 10:56:20 -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 KAA02493 ; Thu, 29 Jun 1995 10:56:17 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id KAA11766; Thu, 29 Jun 1995 10:56:12 -0700 From: "Rodney W. Grimes" Message-Id: <199506291756.KAA11766@gndrsh.aac.dev.com> Subject: Re: Paul Richards: sysconfig routed setting To: paul@freebsd.org Date: Thu, 29 Jun 1995 10:56:12 -0700 (PDT) Cc: wollman@halloran-eldar.lcs.mit.edu, nate@sneezy.sri.com, jkh@freebsd.org, FreeBSD-current@freebsd.org In-Reply-To: <199506291523.QAA13229@freebsd.netcraft.co.uk> from "Paul Richards" at Jun 29, 95 04:23:38 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: 2190 Sender: current-owner@freebsd.org Precedence: bulk ... > > We're getting off the point a bit though, which is whether routed should > be enabled by default. I still think the only time it should be run is > if the box has a real need to exchange RIP info with other routers and in > those cases the admin will know enough to make that decision. routed -q does _not_ ``exchange RIP info'' it simply listens for it, and I will repeat again, you really should listen to your local routers passively, there may very well be more than one! Defaultroute setups are prone to default router failure with no easy back up solution. Anyone with more than 1 segment _should_ run a routing protocol on there router(s), and have all clients listen to the(se) router(s). I have put this out 4 times now, and no one has even responded to this point :-(. I like it the way I have it here, I can install boxes up the wazo and never have to set a default or static route on a one of them, just let routed -q listen to my 2 routers and the new box knows what to do, no IP address to rember to set in defaultrouter, no worry if one of my routers gets kick knocked over when I am swinging sheetrock sheets around, every one will just start using the other router. This works for my FreeBSD boxes and for my HP/Apollo boxes, and should work for any box that supports routed -q. Most _larger_ networks have more than one router per segment for this very reason. > For most boxes it's not needed. Define _most_. It is _needed_ on every box I have here, I could go do it all with defaultroutes but then I would not have my fall over router do me one single bit of good :-(. It is _needed_ on every network I have ever set up, same reasons. Perhaps you folks are willing to live with router outages, I on the other hand find most of my clients quite willing to spend the extra few thousand dollars to have the highly reliable _and_ servicable dual router setups. [Gee, it is so nice to be able to take a router down to upgrade it without having to wait until 3am when _almost_ no one is using it] -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Thu Jun 29 16:52:44 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA12591 for current-outgoing; Thu, 29 Jun 1995 16:52:44 -0700 Received: from intercore.com (num1sun.intercore.com [205.198.76.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAB12585 for ; Thu, 29 Jun 1995 16:52:41 -0700 Received: (robin@localhost) by intercore.com (8.6.9/8.6.4) id TAA06417; Thu, 29 Jun 1995 19:49:11 -0400 From: Robin Cutshaw Message-Id: <199506292349.TAA06417@intercore.com> Subject: Re: Paul Richards: sysconfig routed setting To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Thu, 29 Jun 1995 19:49:10 -0400 (EDT) Cc: freebsd-current@freebsd.org In-Reply-To: <199506291756.KAA11766@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Jun 29, 95 10:56:12 am X-Mailer: ELM [version 2.4 PL21] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 156 Sender: current-owner@freebsd.org Precedence: bulk > > I have put this out 4 times now, and no one has even responded to this > point :-(. > You're preaching to my choir. I whole-heartedly agree. robin From owner-freebsd-current Thu Jun 29 17:57:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA14068 for current-outgoing; Thu, 29 Jun 1995 17:57:19 -0700 Received: from cps201.cps.cmich.edu (archive@cps201.cps.cmich.edu [141.209.20.201]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA14062 for ; Thu, 29 Jun 1995 17:57:16 -0700 Received: (from archive@localhost) by cps201.cps.cmich.edu (8.6.9/8.6.9) id UAA11136; Thu, 29 Jun 1995 20:56:59 -0400 Date: Thu, 29 Jun 1995 20:56:59 -0400 (EDT) From: CMU Mail Archive X-Sender: archive@cps201 Reply-To: mbailey@gnu.ai.mit.edu To: A boy and his worm gear cc: freebsd-current@freebsd.org Subject: Re: Proposal for mountd change In-Reply-To: <199506270130.VAA02111@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk On Mon, 26 Jun 1995, A boy and his worm gear wrote: > This makes it impossible to use FreeBSD to completely support diskless > booting of SunOS 4.x machines (I'm not sure if Solaris 2.x has the > same requirements). Yes it does sorta ;) > > Anyway, I'd like to find a way around this. I'm wondering if it > would be possible to add a run-time option to mountd to loosen > the 'directories only' restriction to include plain files. This is > just an idea at this point -- I haven't had the chance to test it. > I'm not even certain that twisting mountd's arm is the only thing > that's required. I had this working with the old mountd code EXCEPT that the fact that FreeBSD doesn't have rpc.statd and rpc.lockd caused the Sun to cough and die in a BAD TRAP. Since the mountd code has been changed for the new NFS code there is a '-r' (I think :) that allows the mounting of a file rather than a directory. The only problem I have found so far is that the Sun's don't like this and puke mounting any of their system from the FreeBSd machine then. I am at a stage in which I can test the diskless booting of Sun's with code until it works correctly EXCEPT the problem of not have rpc.statd and rpc.lockd on the server. If anyone knows where there is source for statd and lockd for any system I am more than willing to work on the rpc code. As far as NFS goes I don't like this new nfs 3 bit that has been placed into -current it breaks some of our sun mounts around here and doesn't like to talk to the linsux client here either anymore. Thanks Matthew S. Bailey Systems Programmer Journey Communications. From owner-freebsd-current Fri Jun 30 16:50:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA24645 for current-outgoing; Fri, 30 Jun 1995 16:50:49 -0700 Received: from cyclops (xtwa2.ess.harris.com [130.41.26.161]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA24634 for ; Fri, 30 Jun 1995 16:50:41 -0700 Received: (from jleppek@localhost) by cyclops (8.6.11/8.6.9) id TAA00567; Fri, 30 Jun 1995 19:50:44 -0400 Date: Fri, 30 Jun 1995 19:50:44 -0400 From: Jim Leppek Message-Id: <199506302350.TAA00567@cyclops> To: freebsd-current@freefall.cdrom.com Subject: ppp Sender: current-owner@FreeBSD.org Precedence: bulk why does a requested IP of 0.0.0.0 get converted to 192.0.0.1 in ipcp.c line 164 ? if (icp->want_ipaddr.s_addr == 0) icp->want_ipaddr.s_addr = htonl(0xc0000001); My provider expected an IP of 0.0.0.0 to indicate a dynamic ppp connection and this "feature" did cause a bit of confusion as a ifaddr 0 0 does not really work. Thanks Jim Leppek From owner-freebsd-current Sat Jul 1 00:11:31 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA04746 for current-outgoing; Sat, 1 Jul 1995 00:11:31 -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 AAA04740 for ; Sat, 1 Jul 1995 00:11:26 -0700 Received: by haven.uniserve.com id <30804>; Sat, 1 Jul 1995 00:12:04 +0100 Date: Sat, 1 Jul 1995 00:12:04 -0700 (PDT) From: Tom Samplonius To: David Greenman cc: Garrett Wollman , current@freebsd.org Subject: Re: cvs commit: src/sys/i386/isa sio.c In-Reply-To: <199506252258.PAA00581@corbin.Root.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk On Sun, 25 Jun 1995, David Greenman wrote: > I'm not sure this going help a lot - most of the data gets buffered in the > modem and priority queing for ACKs isn't going to help this. How big are modem buffers? From my own expirences, modem buffers sizes appear to be much less than the TCP win size, which would indicate that most of data is buffered at the computer. Tom From owner-freebsd-current Sat Jul 1 03:13:05 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA11531 for current-outgoing; Sat, 1 Jul 1995 03:13:05 -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 DAA11506 for ; Sat, 1 Jul 1995 03:13:02 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA00966; Sat, 1 Jul 1995 12:12:59 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA02968; Sat, 1 Jul 1995 12:12:53 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id LAA00795; Sat, 1 Jul 1995 11:37:33 +0200 From: J Wunsch Message-Id: <199507010937.LAA00795@uriah.heep.sax.de> Subject: Re: ppp To: jleppek@harris.com (Jim Leppek) Date: Sat, 1 Jul 1995 11:37:32 +0200 (MET DST) Cc: freebsd-current@freefall.cdrom.com In-Reply-To: <199506302350.TAA00567@cyclops> from "Jim Leppek" at Jun 30, 95 07:50:44 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: 880 Sender: current-owner@FreeBSD.org Precedence: bulk As Jim Leppek wrote: > > why does a requested IP of 0.0.0.0 get converted to > 192.0.0.1 in ipcp.c line 164 ? > > > if (icp->want_ipaddr.s_addr == 0) > icp->want_ipaddr.s_addr = htonl(0xc0000001); > > > My provider expected an IP of 0.0.0.0 to indicate a dynamic ppp connection > and this "feature" did cause a bit of confusion as a ifaddr 0 0 > does not really work. 0.0.0.0 is an invalid address. It's used to access any listener on the localhost (e.g. you can telnet 0 to your own host), and to describe a default route. No idea about the 192.0.0.1 however. Dynamic PPP address assignment requires valid IP addresses, but those addresses must be negotiated by the PPP peers. This is part of the PPP protocol (AFAIK). -- 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 Sat Jul 1 04:31:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA16499 for current-outgoing; Sat, 1 Jul 1995 04:31:04 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA16468 ; Sat, 1 Jul 1995 04:30:43 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.11/8.6.9) with ESMTP id NAA10825; Sat, 1 Jul 1995 13:30:23 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.11/8.6.9) with SMTP id NAA23439; Sat, 1 Jul 1995 13:30:18 +0200 Message-Id: <199507011130.NAA23439@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: geoff@ufrmsa1.olivetti.za, Wollman@halloran-eldar.lcs.mit.edu, gibbs@freefall.cdrom.com, rgrimes@gndrsh.aac.dev.com, current@freebsd.org, announce@freebsd.org, secure@freebsd.org, jhay@mikom.csir.co.za, Renier Bezuidenhout , bertus@mikom.csir.co.za Subject: To those interested in the foreign FreeBSD secure code. Date: Sat, 01 Jul 1995 13:30:17 +0200 From: Mark Murray Sender: current-owner@freebsd.org Precedence: bulk Hi The number of people who have had something to contribute here is is GREAT! For those not in the know, there is an initiative afoot to get a South African CVS site going that will contain the cryptography code that is otherwise illegal to get out of the USA. There has already been a fair amount of discussion about the code and the site, but mail is now getting difficult to deal with. I have set up a majordomo for those who are going to _*participate*_ (even in the background) in this project. If you feel you have something to contribute, or feel the need to keep a "fatherly eye out" (Core members!), please join. As this is going to be run from a small site with limited bandwidth, I would prefer to keep the list of members limited to those actually involved or in charge, and not just use it as another mailing list. Thanks for your co-operation! To join, please send the following line: subscribe freebsd-foreign-secure [] to majordomo@grondar.za. For help, send the following line: help to majordomo@grondar.za Enjoy! M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Sat Jul 1 08:22:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA22526 for current-outgoing; Sat, 1 Jul 1995 08:22:19 -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 IAA22518 for ; Sat, 1 Jul 1995 08:22:15 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA05463; Sat, 1 Jul 1995 17:22:12 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id RAA03936 for freebsd-current@FreeBSD.org; Sat, 1 Jul 1995 17:22:12 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id RAA02130 for freebsd-current@FreeBSD.org; Sat, 1 Jul 1995 17:10:13 +0200 From: J Wunsch Message-Id: <199507011510.RAA02130@uriah.heep.sax.de> Subject: getopt(1) To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 1 Jul 1995 17:10:12 +0200 (MET DST) Reply-To: freebsd-current@FreeBSD.org (FreeBSD-current users) 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: 404 Sender: current-owner@FreeBSD.org Precedence: bulk I'm missing the getopt(1) program to get some old shell scripts working without converting them to use the modern replacement getopts(1). I've got an older implementation (by me, back from 386BSD 0.1 days) lying around, do people object against importing 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 Sat Jul 1 09:04:03 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA23479 for current-outgoing; Sat, 1 Jul 1995 09:04:03 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA23455 for ; Sat, 1 Jul 1995 09:03:48 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.11/8.6.9) with ESMTP id SAA11079; Sat, 1 Jul 1995 18:02:25 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.11/8.6.9) with SMTP id SAA21479; Sat, 1 Jul 1995 18:02:23 +0200 Message-Id: <199507011602.SAA21479@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: freebsd-current@FreeBSD.org (FreeBSD-current users), joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: getopt(1) Date: Sat, 01 Jul 1995 18:02:23 +0200 From: Mark Murray Sender: current-owner@FreeBSD.org Precedence: bulk > I'm missing the getopt(1) program to get some old shell scripts > working without converting them to use the modern replacement > getopts(1). I've got an older implementation (by me, back from 386BSD > 0.1 days) lying around, do people object against importing it? Isn't that a bit of a step backward? Importing old code to get old scripts working? Surely progress would be better served by upgrading the scripts. My 0.02R (1US$=3.6ZAR, so 0.02ZAR very little) M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Sat Jul 1 10:47:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA26827 for current-outgoing; Sat, 1 Jul 1995 10:47:57 -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 KAA26821 for ; Sat, 1 Jul 1995 10:47:54 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id KAA15354 for freebsd-current@FreeBSD.org; Sat, 1 Jul 1995 10:47:48 -0700 From: "Rodney W. Grimes" Message-Id: <199507011747.KAA15354@gndrsh.aac.dev.com> Subject: Re: getopt(1) To: freebsd-current@FreeBSD.org Date: Sat, 1 Jul 1995 10:47:47 -0700 (PDT) In-Reply-To: <199507011510.RAA02130@uriah.heep.sax.de> from "J Wunsch" at Jul 1, 95 05:10:12 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: 559 Sender: current-owner@FreeBSD.org Precedence: bulk > > I'm missing the getopt(1) program to get some old shell scripts > working without converting them to use the modern replacement > getopts(1). I've got an older implementation (by me, back from 386BSD > 0.1 days) lying around, do people object against importing it? 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! -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Sat Jul 1 11:13:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAB27515 for current-outgoing; Sat, 1 Jul 1995 11:13: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 LAA27509 for ; Sat, 1 Jul 1995 11:13:07 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA08547; Sat, 1 Jul 1995 20:13:03 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA05549 for freebsd-current@FreeBSD.org; Sat, 1 Jul 1995 20:13:02 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id UAA03360 for freebsd-current@FreeBSD.org; Sat, 1 Jul 1995 20:05:38 +0200 From: J Wunsch Message-Id: <199507011805.UAA03360@uriah.heep.sax.de> Subject: Re: getopt(1) To: freebsd-current@FreeBSD.org Date: Sat, 1 Jul 1995 20:05:37 +0200 (MET DST) Reply-To: freebsd-current@FreeBSD.org In-Reply-To: <199507011747.KAA15354@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Jul 1, 95 10:47:47 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: 676 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. -- 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 Sat Jul 1 11:31:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA27823 for current-outgoing; Sat, 1 Jul 1995 11:31:49 -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 LAA27816 for ; Sat, 1 Jul 1995 11:31:41 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id EAA04830 for current@freebsd.org; Sun, 2 Jul 1995 04:31:30 +1000 From: michael butler Message-Id: <199507011831.EAA04830@asstdc.scgt.oz.au> Subject: NFS client no longer works :-( To: current@freebsd.org Date: Sun, 2 Jul 1995 04:31:27 +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: 331 Sender: current-owner@freebsd.org Precedence: bulk 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) :-( michael From owner-freebsd-current Sat Jul 1 12:16:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA28985 for current-outgoing; Sat, 1 Jul 1995 12:16:02 -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 MAA28972 for ; Sat, 1 Jul 1995 12:15:58 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA09595; Sat, 1 Jul 1995 21:15:55 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA05903; Sat, 1 Jul 1995 21:15:54 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id VAA03913; Sat, 1 Jul 1995 21:14:16 +0200 From: J Wunsch Message-Id: <199507011914.VAA03913@uriah.heep.sax.de> Subject: Re: NFS client no longer works :-( To: imb@scgt.oz.au (michael butler) Date: Sat, 1 Jul 1995 21:14:15 +0200 (MET DST) Cc: current@FreeBSD.org In-Reply-To: <199507011831.EAA04830@asstdc.scgt.oz.au> from "michael butler" at Jul 2, 95 04:31:27 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: 2227 Sender: current-owner@FreeBSD.org Precedence: bulk As 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) Hmm, two possibilities. Either, it's the NFSv3 code, or it is my recent fix for some weird NFSv2 servers. The latter change might be reverted with: Index: nfs_subs.c =================================================================== RCS file: /usr/home/cvs/src/sys/nfs/nfs_subs.c,v retrieving revision 1.16 retrieving revision 1.15 diff -u -r1.16 -r1.15 --- 1.16 1995/06/14 06:23:38 +++ 1.15 1995/05/30 08:12:43 @@ -34,7 +34,7 @@ * SUCH DAMAGE. * * @(#)nfs_subs.c 8.3 (Berkeley) 1/4/94 - * $Id: nfs_subs.c,v 1.16 1995/06/14 06:23:38 joerg Exp $ + * $Id: nfs_subs.c,v 1.15 1995/05/30 08:12:43 rgrimes Exp $ */ /* @@ -712,26 +712,7 @@ fp = (struct nfsv2_fattr *)cp2; vtyp = nfstov_type(fp->fa_type); vmode = fxdr_unsigned(u_short, fp->fa_mode); - /* - * XXX - * - * The duplicate information returned in fa_type and fa_mode - * is an ambiguity in the NFS version 2 protocol. - * - * VREG should be taken literally as a regular file. If a - * server intents to return some type information differently - * in the upper bits of the mode field (e.g. for sockets, or - * FIFOs), NFSv2 mandates fa_type to be VNON. Anyway, we - * leave the examination of the mode bits even in the VREG - * case to avoid breakage for bogus servers, but we make sure - * that there are actually type bits set in the upper part of - * fa_mode (and failing that, trust the va_type field). - * - * NFSv3 cleared the issue, and requires fa_mode to not - * contain any type information (while also introduing sockets - * and FIFOs for fa_type). - */ - if (vtyp == VNON || (vtyp == VREG && (vmode & S_IFMT) != 0)) + if (vtyp == VNON || vtyp == VREG) vtyp = IFTOVT(vmode); if (isnq) { rdev = fxdr_unsigned(long, fp->fa_nqrdev); Please tell me if this has been the problem. -- 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 Sat Jul 1 13:57:38 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA01749 for current-outgoing; Sat, 1 Jul 1995 13:57:38 -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 NAA01743 ; Sat, 1 Jul 1995 13:57:36 -0700 Received: by duality.gnu.ai.mit.edu (8.6.12/8.6.12GNU) id QAA26175; Sat, 1 Jul 1995 16:57:30 -0400 Date: Sat, 1 Jul 1995 16:57:30 -0400 Message-Id: <199507012057.QAA26175@duality.gnu.ai.mit.edu> From: "Charles M. Hannum" To: wollman@halloran-eldar.lcs.mit.edu CC: rgrimes@gndrsh.aac.dev.com, jkh@freebsd.org, FreeBSD-current@freebsd.org In-reply-to: <9506281556.AA00902@halloran-eldar.lcs.mit.edu> (message from Garrett Wollman on Wed, 28 Jun 1995 11:56:15 -0400) Subject: Re: Paul Richards: sysconfig routed setting Sender: current-owner@freebsd.org Precedence: bulk HOSTS DO NOT NEED ROUTING INFORMATION. What would you suggest that multihomed hosts do? From owner-freebsd-current Sat Jul 1 14:33:32 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA02936 for current-outgoing; Sat, 1 Jul 1995 14:33:32 -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 OAA02912 ; Sat, 1 Jul 1995 14:33:19 -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 XAA16984 ; Sat, 1 Jul 1995 23:33:16 +0200 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id XAA13018 ; Sat, 1 Jul 1995 23:33:15 +0200 Received: (from roberto@localhost) by keltia.frmug.fr.net (8.7.Beta.7/keltia-uucp-2.2) id XAA05094 for freebsd-bugs@FreeBSD.ORG; Sat, 1 Jul 1995 23:31:31 +0200 (MET DST) From: Ollivier Robert Message-Id: <199507012131.XAA05094@keltia.frmug.fr.net> Subject: Problem with ed0 and netstat statistics To: freebsd-bugs@FreeBSD.ORG (FreeBSD Bugs' list), freebsd-current@FreeBSD.ORG Date: Sat, 1 Jul 1995 23:31:31 +0200 (MET DST) Reply-To: roberto@keltia.freenix.fr (Ollivier Robert) X-Operating-System: FreeBSD 2.0-BUILT-19950629 ctm#829 X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: current-owner@FreeBSD.ORG Precedence: bulk Hello everyone (especially David), I'm doing a backup of my laptop with rdump on my small Ethernet network (just the primary machine -- keltia -- and the laptop -- a Sparcbook named sidhe) and I'm getting an awfully high number of collisions shown by netstat. What is weird is that the tranceiver on the sparcbook doesn't show any collision... It may be related to the PR I opened a days ago (kern/540 I think) but I'd like to know where the problem may lay. 276 [23:19] roberto@keltia:ports/utils> netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ed0 1500 00.00.c0.4d.ed.08 18158 196 13643 0 2741 ed0 1500 FR-ATL-NET keltia.frmug.fr 18158 196 13643 0 2741 [...] 277 [23:19] roberto@keltia:ports/utils> netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ed0 1500 00.00.c0.4d.ed.08 18791 208 13950 0 2842 ed0 1500 FR-ATL-NET keltia.frmug.fr 18791 208 13950 0 2842 [...] 278 [23:19] roberto@keltia:ports/utils> netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ed0 1500 00.00.c0.4d.ed.08 19357 218 14237 0 2986 ed0 1500 FR-ATL-NET keltia.frmug.fr 19357 218 14237 0 2986 and now : 279 [23:23] roberto@keltia:ports/utils> netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ed0 1500 00.00.c0.4d.ed.08 38907 455 22603 1 8446 ed0 1500 FR-ATL-NET keltia.frmug.fr 38907 455 22603 1 8446 more than 5000 coll. in 4 minutes ? When you have only *2* machines on the ethernet doing almost nothing except the backup ?? And more than 200 Ierrs as well. Is there a problem in the SMC8013EP I got, in the driver or in netstat's statistics ? I'm sure that I lose thoughput though. Ideas anyone ? Relevant pieces of information : FreeBSD 2.0-BUILT-19950629 #6: Thu Jun 29 17:38:21 MET DST 1995 roberto@keltia:/src/src/sys/compile/KELTIA CPU: i486DX (486-class CPU) real memory = 33161216 (8096 pages) avail memory = 31416320 (7670 pages) [...] ed0 at 0x300-0x31f irq 10 maddr 0xcc000 msize 16384 on isa ed0: address 00:00:c0:4d:ed:08, type WD8013EP (16 bit) bpf: ed0 attached ------------------------------------------------------------ # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # $Id: GENERIC,v 1.11 1994/11/08 07:39:26 jkh Exp $ # machine "i386" cpu "I486_CPU" ident "KELTIA" maxusers 20 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options MFS #Berkeley Fast Filesystem options LFS #Berkeley Log Filesystem options PROCFS #Berkeley proc Filesystem options "COMPAT_43" #Compatible with BSD 4.3 options "SCSI_2_DEF" #hack for the mp1624 options UCONSOLE #for xconsole options "AUTO_EOI_1" options "AUTO_EOI_2" options DUMMY_NOPS options TEST_LABELLING options "COMPAT_LINUX" options SYSVSHM options SYSVSEM options SYSVMSG options "SHMMAXPGS=128" # 512 KB of sharable memory options GATEWAY options KTRACE config kernel root on sd0 swap on sd0 and sd1 and sd2 dumps on sd0 controller isa0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 controller bt0 at isa? port "IO_BT0" bio irq ? vector btintr controller scbus0 at bt0 disk sd0 at scbus0 target 0 unit 0 disk sd1 at scbus0 target 1 tape st0 at scbus0 target 5 tape st1 at scbus0 target 4 device cd0 at scbus0 target 6 controller snd0 device sb0 at isa? port 0x220 irq 5 drq 3 vector sbintr device opl0 at isa? port 0x388 device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device ed0 at isa? port 0x300 net irq 10 iomem 0xcc000 vector edintr pseudo-device loop pseudo-device ether pseudo-device log pseudo-device sl 1 pseudo-device ppp 1 pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device pty 24 pseudo-device speaker pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device disc #Discard device pseudo-device tun 1 #Enable user-level PPP see ppp(8) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. ------------------------------------------------------------ -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia 2.0-BUILT-19950629 #6: Thu Jun 29 17:38:21 MET DST 1995 From owner-freebsd-current Sat Jul 1 17:34:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA08960 for current-outgoing; Sat, 1 Jul 1995 17:34:36 -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 RAA08954 for ; Sat, 1 Jul 1995 17:34:35 -0700 Received: from borg.ess.harris.com (suw2k.ess.harris.com) by ess.harris.com (5.x/SMI-SVR4) id AA27664; Sat, 1 Jul 1995 20:34:31 -0400 Received: by borg.ess.harris.com (4.1/SMI-4.1) id AA00609; Sat, 1 Jul 95 20:32:10 EDT Date: Sat, 1 Jul 95 20:32:10 EDT From: jleppek@suw2k.ess.harris.com (James Leppek) Message-Id: <9507020032.AA00609@borg.ess.harris.com> To: freebsd-current@freefall.cdrom.com Subject: Re: ppp Sender: current-owner@FreeBSD.org Precedence: bulk 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 :-) ) I am still unclear as to the reason for the non-intuitive mapping of 0 to 192.0.0.1 Hmmmmmmm Ahh well another mystery of life, thats what sources are for :-) Jim > From owner-freebsd-current@freefall.cdrom.com Sat Jul 1 14:59:04 1995 > From: J Wunsch > Subject: Re: ppp > To: jleppek@harris.com (Jim Leppek) > Date: Sat, 1 Jul 1995 11:37:32 +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 > Sender: current-owner@FreeBSD.org > > As Jim Leppek wrote: > > > > why does a requested IP of 0.0.0.0 get converted to > > 192.0.0.1 in ipcp.c line 164 ? > > > > > > if (icp->want_ipaddr.s_addr == 0) > > icp->want_ipaddr.s_addr = htonl(0xc0000001); > > > > > > My provider expected an IP of 0.0.0.0 to indicate a dynamic ppp connection > > and this "feature" did cause a bit of confusion as a ifaddr 0 0 > > does not really work. > > 0.0.0.0 is an invalid address. It's used to access any listener on > the localhost (e.g. you can telnet 0 to your own host), and to > describe a default route. > > No idea about the 192.0.0.1 however. > > Dynamic PPP address assignment requires valid IP addresses, but those > addresses must be negotiated by the PPP peers. This is part of the > PPP protocol (AFAIK). > > -- > 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 Sat Jul 1 19:48:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA12588 for current-outgoing; Sat, 1 Jul 1995 19:48:06 -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 TAA12582 for ; Sat, 1 Jul 1995 19:48:03 -0700 Received: by duality.gnu.ai.mit.edu (8.6.12/8.6.12GNU) id WAA27132; Sat, 1 Jul 1995 22:47:57 -0400 Date: Sat, 1 Jul 1995 22:47:57 -0400 Message-Id: <199507020247.WAA27132@duality.gnu.ai.mit.edu> From: "Charles M. Hannum" To: terry@cs.weber.edu CC: rgrimes@gndrsh.aac.dev.com, phk@freefall.cdrom.com, mark@grondar.za, wollman@halloran-eldar.lcs.mit.edu, current@freebsd.org In-reply-to: <9506261847.AA28600@cs.weber.edu> (terry@cs.weber.edu) Subject: Re: Crypt code summary(2). Sender: current-owner@freebsd.org Precedence: bulk NetBSD seems uninterested because they [...] This is, of course, a severe misrepresentation. Nobody in the NetBSD `core' group has discussed plans to displace any commercial operating system (although, by 3rd party reports, this actually happened in one case). *Please* speak only for yourself, Terry. From owner-freebsd-current Sat Jul 1 21:40:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA15485 for current-outgoing; Sat, 1 Jul 1995 21:40:46 -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 VAA15467 for ; Sat, 1 Jul 1995 21:40:17 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id OAA32241; Sun, 2 Jul 1995 14:36:51 +1000 Date: Sun, 2 Jul 1995 14:36:51 +1000 From: Bruce Evans Message-Id: <199507020436.OAA32241@godzilla.zeta.org.au> To: current@freebsd.org Subject: serial ip congestion Cc: bde@zeta.org.au Sender: current-owner@freebsd.org Precedence: bulk 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 seems to be a problem with lost or delayed acks. tcpdump usually shows output something like this: 02:40:35.300351 a0.1023 > a4.cmd: . 0:1440(1440) ack 1 win 17280 [tos 0x8] 02:40:35.503441 a4.cmd > a0.1023: . ack 1440 win 15840 02:40:35.503892 a0.1023 > a4.cmd: . 1440:2880(1440) ack 1 win 17280 [tos 0x8] 02:40:35.512789 a0.1023 > a4.cmd: . 2880:4320(1440) ack 1 win 17280 [tos 0x8] 02:40:35.696198 a4.cmd > a0.1023: . ack 2880 win 15840 02:40:35.696636 a0.1023 > a4.cmd: . 4320:5760(1440) ack 1 win 17280 [tos 0x8] 02:40:35.696895 a0.1023 > a4.cmd: . 5760:7200(1440) ack 1 win 17280 [tos 0x8] 02:40:35.862330 a4.cmd > a0.1023: . ack 4320 win 15840 02:40:35.862889 a0.1023 > a4.cmd: . 7200:8640(1440) ack 1 win 17280 [tos 0x8] 02:40:35.863073 a0.1023 > a4.cmd: . 8640:9120(480) ack 1 win 17280 [tos 0x8] 02:40:36.020688 a4.cmd > a0.1023: . ack 5760 win 15840 02:40:36.021168 a0.1023 > a4.cmd: . 9120:10560(1440) ack 1 win 17280 [tos 0x8] dup acks: 02:40:36.343629 a4.cmd > a0.1023: . ack 5760 win 17280 02:40:36.390202 a4.cmd > a0.1023: . ack 5760 win 17280 long pause send again: 02:40:39.800301 a0.1023 > a4.cmd: . 5760:7200(1440) ack 1 win 17280 [tos 0x8] 02:40:39.987871 a4.cmd > a0.1023: . ack 10080 win 12960 OK now 02:40:39.988292 a0.1023 > a4.cmd: . 10080:11520(1440) ack 1 win 17280 [tos 0x8] 02:40:39.992211 a0.1023 > a4.cmd: . 11520:12960(1440) ack 1 win 17280 [tos 0x8] 02:40:39.992540 a4.cmd > a0.1023: . ack 10080 win 16416 02:40:40.289384 a4.cmd > a0.1023: . ack 12960 win 16608 02:40:40.289799 a0.1023 > a4.cmd: . 12960:14400(1440) ack 1 win 17280 [tos 0x8] 02:40:40.296508 a0.1023 > a4.cmd: . 14400:15840(1440) ack 1 win 17280 [tos 0x8] 02:40:40.296762 a0.1023 > a4.cmd: . 15840:17280(1440) ack 1 win 17280 [tos 0x8] 02:40:40.531287 a4.cmd > a0.1023: . ack 14400 win 17280 02:40:40.531670 a0.1023 > a4.cmd: . 17280:18720(1440) ack 1 win 17280 [tos 0x8] 02:40:40.722439 a4.cmd > a0.1023: . ack 15840 win 17280 02:40:40.722852 a0.1023 > a4.cmd: . 18720:20160(1440) ack 1 win 17280 [tos 0x8] 02:40:40.931900 a4.cmd > a0.1023: . ack 17280 win 17280 02:40:40.932352 a0.1023 > a4.cmd: . 20160:21600(1440) ack 1 win 17280 [tos 0x8] 02:40:41.132582 a4.cmd > a0.1023: . ack 18720 win 17280 02:40:41.133029 a0.1023 > a4.cmd: . 21600:23040(1440) ack 1 win 17280 [tos 0x8] 02:40:41.133325 a0.1023 > a4.cmd: . 23040:24480(1440) ack 1 win 17280 [tos 0x8] 02:40:41.331971 a4.cmd > a0.1023: . ack 20160 win 17280 02:40:41.332444 a0.1023 > a4.cmd: . 24480:25920(1440) ack 1 win 17280 [tos 0x8] short pause dup ack: 02:40:41.807865 a4.cmd > a0.1023: . ack 20160 win 17280 long pause send again: 02:40:44.300298 a0.1023 > a4.cmd: . 20160:21600(1440) ack 1 win 17280 [tos 0x8] --- 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 & The following variations don't help: cslip instead of ppp 2 systems sio driver on one system, cy driver on other 2 ports on each system, both pairs active mtu = mru = 16384 The following variation helps: speed 57600 (even with 4 active pairs, there are no long pauses, although there are short pauses when the disk is written to, and throughput is on 4 * 4.4K/sec). No errors were reported by the drivers or by pppstats. I noticed many bugs in the man pages: pppstats.8: The `ip' field isn't documented. The `ip' field seems to be backwards. It seems to count udp packets. `connection' is spelled `connectoin' in one place. `pppstats' should be named `pppstat' slstat.8: `slstat' calls itself `vmstat' in one place. The documented default fields are in out pack comp uncomp unknwn toss other err search miss coll but the actual default fields are in pack comp uncomp unknwn out pack comp uncomp other. There is no cross reference to `pppstats'. Bruce From owner-freebsd-current Sat Jul 1 22:55:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA17518 for current-outgoing; Sat, 1 Jul 1995 22:55: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 WAA17500 for ; Sat, 1 Jul 1995 22:55:19 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA01685; Sun, 2 Jul 1995 15:48:56 +1000 Date: Sun, 2 Jul 1995 15:48:56 +1000 From: Bruce Evans Message-Id: <199507020548.PAA01685@godzilla.zeta.org.au> To: peter@haywire.DIALix.COM, rgrimes@gndrsh.aac.dev.com Subject: Re: when is the supscan done? Cc: current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk >Just as a $0.02 suggestion: I wouldn't mind seeing the results of a >"cvs update -q" (or whatever) when this job is run... I'd find that a lot >easier to read than the output that "sup -v" generates when run on the >machine here. Perhaps others would be interested too? Use ctm and its output instead of sup. Bruce From owner-freebsd-current Sat Jul 1 23:51:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA18874 for current-outgoing; Sat, 1 Jul 1995 23:51:52 -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 XAA18855 ; Sat, 1 Jul 1995 23:51:49 -0700 Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au id <25110-0@bunyip.cc.uq.oz.au>; Sun, 2 Jul 1995 16:51:40 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id QAA12577; Sun, 2 Jul 1995 16:56:01 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id GAA01310; Sun, 2 Jul 1995 06:53:07 GMT Message-Id: <199507020653.GAA01310@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6 4/21/95 To: current@freebsd.org, scsi@freebsd.org Subject: Calling sequence for SCSI operations Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Jul 1995 16:53:07 +1000 From: Stephen Hocking Sender: current-owner@freebsd.org Precedence: bulk I'm in the process of finding out why the -current seagate.c driver does not work with Future Domain TMC-885 controllers and was wondering if anyone could tell me exactly what happens when things start up after the kernel is loaded. At the moment I'm getting a bunch of arbitration timeout and it refuses to see any of the drives. I do know, from my work with the 2.0R driver, that it can't cope with allowing disconnects. Stephen I do not speak for the Worker's Compensation Board of Queensland - They don't pay me enough for that!