From owner-freebsd-hackers Sun Jan 5 04:10:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA25965 for hackers-outgoing; Sun, 5 Jan 1997 04:10:18 -0800 (PST) Received: from terminator.informatik.ba-stuttgart.de (terminator.informatik.ba-stuttgart.de [141.31.1.21]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA25874 for ; Sun, 5 Jan 1997 04:08:48 -0800 (PST) Received: from helbig.informatik.ba-stuttgart.de (max66-2.informatik.ba-stuttgart.de [141.31.66.2]) by terminator.informatik.ba-stuttgart.de (8.7.6/8.7.3) with ESMTP id MAA06902 for ; Sun, 5 Jan 1997 12:06:58 +0100 Received: (from wh@localhost) by helbig.informatik.ba-stuttgart.de (8.8.4/8.8.4) id MAA21689 for hackers@FreeBSD.ORG; Sun, 5 Jan 1997 12:49:58 +0100 (MET) From: Wolfgang Helbig Message-Id: <199701051149.MAA21689@helbig.informatik.ba-stuttgart.de> Subject: Workaround for CMD640B flaw To: hackers@FreeBSD.ORG Date: Sun, 5 Jan 1997 12:49:57 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, I attached a new disk two the secondary IDE channel as master. The primary channel is used by another disk and an ATAPI-CDROM, both working fine with FreeBSD 2.1.0 and 2.1.5 and -current. Disklabeling and creating the filesystem on the new disk worked fine. But when I started to copy files the system frooze. With the help of FreeBSD-questions I found out, that the cause is the CMD640B-IDE controller, that by design cannot control both channels concurrently. What needs to be done (and apparently is done in Linux) is to serialize the use of the two channels (that is wdc0 and wdc1) I tried a little changing the wd-driver but to no result. Since the CMD640B is used on a lot of motherboards, I think we need a workaround for this chip. May be there is an easy way to serialize? Any tips or help would be appreciated, since this is the first time I meet the kernel source! thanks, Wolfgang Helbig From owner-freebsd-hackers Sun Jan 5 05:30:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA29317 for hackers-outgoing; Sun, 5 Jan 1997 05:30:12 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA29278 for ; Sun, 5 Jan 1997 05:29:56 -0800 (PST) Message-Id: <199701051329.FAA29278@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA110270894; Mon, 6 Jan 1997 00:28:14 +1100 From: Darren Reed Subject: Re: file locking / firewalling based on uid/gid To: proff@iq.org (Julian Assange) Date: Mon, 6 Jan 1997 00:28:14 +1100 (EDT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199701022334.KAA16149@profane.iq.org> from "Julian Assange" at Jan 3, 97 10:34:34 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In some mail from Julian Assange, sie said: > > In some mail from Julian Assange, sie said: > > [...] > > > # ipfw add pass tcp from any to any established gid inetd > > > # ipfw add padd tcp from any to any 21,79 setup in gid inetd > > > > I don't think that is a good way (or the right place) to do access control > > for TCP/IP. Firstly, on a gateway, not all TCP packets are likely to have > > a gid (or for there to be one which is "findable") and secondly, where > > the current hooks are, you will cause two tcpb lookups to occur for the > > same packet. > > Bypassed these limitations by hooking input firewall checks into > the individual proto_sw routines just after the tcbp hash lookups. > Requires two scans of the firewall rule-set for inbound host packets, > but this has almost no overhead, because the first scan doesn't do > the checks of the second and vica-versa. The ipfw rule-set flows > sequentially without jumps, permitting this optimisation to work. Maybe, but the scan is still O(N) where N is the size of the list, not O(n) (where n is the applicable rules). Actually, I think it is a bad idea to have both types on the same list as the output of an ACL listing is confusing due to the "skipping". Making two separate lists solves both of these problems. > Output checks were unified by comparison, requiring only the passing > of (the new) socket credential information into ip_output(), where > it is passed onto the regular fw hook. Hmmmmm. Makes me think of SEoS which gives you user/group level access control on all system calls on Unix. Having said that, I think that access control via the system call (rather than sticking hooks into the kernel at strange places) is much neater. (To me, filtering based on UID implies you're doing things at a higher level than normal packet filtering and should be a separate beast rather than coming up with kludges to extend ipfw. Heck, there are many more and different checks you can make, for a start...). Darren From owner-freebsd-hackers Sun Jan 5 05:31:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA29369 for hackers-outgoing; Sun, 5 Jan 1997 05:31:45 -0800 (PST) Received: (from jmb@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA29361; Sun, 5 Jan 1997 05:31:41 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199701051331.FAA29361@freefall.freebsd.org> Subject: Re: Usenix FreeBSD BoF when? To: obrien@antares.aero.org (Mike O'Brien) Date: Sun, 5 Jan 1997 05:31:41 -0800 (PST) Cc: julian@whistle.com, hackers@freefall.freebsd.org, chat@freefall.freebsd.org In-Reply-To: <199701050450.UAA20001@antares.aero.org> from "Mike O'Brien" at Jan 4, 97 08:50:20 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mike O'Brien wrote: > > > no form to set one up over the web ;( > > has to be done at the registration desk > > I did that, when I was doing USENIX things. Very hungry commercial > outfits were trying to schedule BoFs months in advance which amounted > to no more than live infomercials for their products. I was revulsed > and insisted that BoFs be scheduled only at the conference, to > preserve some semblance of spontaneity. I borrowed the BoF idea > from DECUS, where it amounts to meetings organized by people around > topics too new to have been scheduled into the regular program... > many regularly scheduled daytime DECUS sessions are (or were) really just > BoFs of long standing. > > I did this long before the IETF and its BoFs were a going concern, ditto > Uniforum. > > Frankly given the alternative I'm real happy with things as they are > now. given the history, it is a very good thing! thanks, will we be see you at usenix? jmb From owner-freebsd-hackers Sun Jan 5 09:37:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA07369 for hackers-outgoing; Sun, 5 Jan 1997 09:37:16 -0800 (PST) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA07364 for ; Sun, 5 Jan 1997 09:37:13 -0800 (PST) Received: from dbws.etinc.com (dbws.etinc.com [204.141.95.130]) by etinc.com (8.6.12/8.6.9) with SMTP id MAA18126; Sun, 5 Jan 1997 12:41:42 -0500 Message-Id: <3.0.32.19970105125150.00687428@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 05 Jan 1997 12:51:52 -0500 To: Darren Reed From: dennis Subject: Re: file locking / firewalling based on uid/gid Cc: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 12:28 AM 1/6/97 +1100, you wrote: >In some mail from Julian Assange, sie said: >> > In some mail from Julian Assange, sie said: >> > [...] >> > > # ipfw add pass tcp from any to any established gid inetd >> > > # ipfw add padd tcp from any to any 21,79 setup in gid inetd >> > >> > I don't think that is a good way (or the right place) to do access control >> > for TCP/IP. Firstly, on a gateway, not all TCP packets are likely to have >> > a gid (or for there to be one which is "findable") and secondly, where >> > the current hooks are, you will cause two tcpb lookups to occur for the >> > same packet. >> >> Bypassed these limitations by hooking input firewall checks into >> the individual proto_sw routines just after the tcbp hash lookups. >> Requires two scans of the firewall rule-set for inbound host packets, >> but this has almost no overhead, because the first scan doesn't do >> the checks of the second and vica-versa. The ipfw rule-set flows >> sequentially without jumps, permitting this optimisation to work. > >Maybe, but the scan is still O(N) where N is the size of the list, not >O(n) (where n is the applicable rules). > >Actually, I think it is a bad idea to have both types on the same list >as the output of an ACL listing is confusing due to the "skipping". > >Making two separate lists solves both of these problems. > >> Output checks were unified by comparison, requiring only the passing >> of (the new) socket credential information into ip_output(), where >> it is passed onto the regular fw hook. > >Hmmmmm. Makes me think of SEoS which gives you user/group level access >control on all system calls on Unix. Having said that, I think that >access control via the system call (rather than sticking hooks into the >kernel at strange places) is much neater. > >(To me, filtering based on UID implies you're doing things at a higher > level than normal packet filtering and should be a separate beast rather > than coming up with kludges to extend ipfw. Heck, there are many more > and different checks you can make, for a start...). I agree. It seems that firewalling and "authentication" are getting entwined... which is not a "bad" thing as long as there is no penalty to pay by one or the other. We've recently combined our bandwidth management, queue prioritization and filtering functons, but made it a single-pass function to eliminate the performance penalty. Dennis From owner-freebsd-hackers Sun Jan 5 09:49:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA07701 for hackers-outgoing; Sun, 5 Jan 1997 09:49:39 -0800 (PST) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA07696 for ; Sun, 5 Jan 1997 09:49:36 -0800 (PST) Received: from dbws.etinc.com (dbws.etinc.com [204.141.95.130]) by etinc.com (8.6.12/8.6.9) with SMTP id MAA18191 for ; Sun, 5 Jan 1997 12:54:16 -0500 Message-Id: <3.0.32.19970105130424.0068f454@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 05 Jan 1997 13:04:26 -0500 To: hackers@freebsd.org From: dennis Subject: Re: New Networking framework for BSD Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 01:00 PM 1/5/97 +1100, you wrote: >In some mail from Julian Elischer, sie said: >> >> Darren, see my mail drirectly to you... >> you appear to have commented without reading the doc yet.. >> I'm not trying to replace anything. Just make a framework for such >> services as frame relay and ATM, at the LINK level. > >Yes, I read it briefly first but wrote that with an empty mind... > >Looks like the claytons STREAMS. How is it different to STREAMS (by design) ? Yeah really. STREAMS is a great academic product...but a monster in real world implementation. Not to mention a pig. Anyone care to guess why the 'BSD unices blow the doors off system V performance-wise? An issue to consider is that you dont need a new framework...virtual interfaces solve the problem without changing anything...with a new framework you are likely to break compatibility with routing daemons (like gated)...which would render the effort worthless in the big picture. Dennis ---------------------------------------------------------------------------- -------- Emerging Technologies, Inc. http://www.etinc.com 56k, T1, Frac-T3 Adapters for 'BSD and LINUX. ET/BWMGR Bandwidth Allocation and Firewall Tool Bandwidth Allocation/Limiting Routers From owner-freebsd-hackers Sun Jan 5 10:40:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA09485 for hackers-outgoing; Sun, 5 Jan 1997 10:40:25 -0800 (PST) Received: from kodiak.ucla.edu (kodiak.ucla.edu [164.67.128.11]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA09480 for ; Sun, 5 Jan 1997 10:40:23 -0800 (PST) Received: from elm.cns.ucla.edu (elm.cns.ucla.edu [164.67.222.20]) by kodiak.ucla.edu (8.8.4/8.6.9) with SMTP id SAA26588 for ; Sun, 5 Jan 1997 18:40:00 GMT From: Scott Burris To: freebsd-hackers@freebsd.org Subject: 2.2-BETA hangs after a few minutes Message-ID: Date: Sun, 5 Jan 1997 10:39:38 -0800 () Priority: NORMAL X-Mailer: Simeon for Win32 Version 4.0.9 X-Authentication: none MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk To follow up my own message, I compiled the exact same kernel configuration from 2.2-ALPHA and it works perfectly on this system. So something bad has happened between ALPHA and BETA. Guess it's time to start diff-ing the kernel source trees to see what's changed :-( Scott > I've updated several of my FreeBSD systems at home with 2.2-BETA. One, > a generic Triton chipset motherboard works just fine. The other, a > Pentium system with the Opti chipset which connects the PCI bus to the > VLB (instead of the other way around :-() now hangs solid after being up > for anywhere between 10 and 30 minutes. No panics, no nothing, the > system just appears to be completely dead. I compiled a new kernel with > the debugger, but when the system hangs, I can't force it into the > debugger. This system used to run the August 2.2 SNAP without problems > and I have reverted back to that kernel. > > I'm happy to look into this further, but can anyone make a suggestion > about how to debug a system that doesn't even panic? > > Scott > > ---------------------- > Scott Burris > UCLA Campus Telecomunications and Network Services > scott@cns.ucla.edu > > ---------------------- Scott Burris UCLA Campus Telecommunications and Network Services scott@cns.ucla.edu From owner-freebsd-hackers Sun Jan 5 12:32:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA12980 for hackers-outgoing; Sun, 5 Jan 1997 12:32:41 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA12975 for ; Sun, 5 Jan 1997 12:32:39 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id PAA03705; Sun, 5 Jan 1997 15:32:35 -0500 (EST) From: Charles Henrich Message-Id: <199701052032.PAA03705@crh.cl.msu.edu> Subject: Re: more than 32 disks? To: dg@root.com Date: Sun, 5 Jan 1997 15:32:35 -0500 (EST) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199701030329.TAA18783@root.com> from David Greenman at "Jan 2, 97 07:29:46 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > unit number. This means that one will have to make driver changes to go > beyond 32 units. :-( I noticed this pop up in relation to CD changers as well. I have a suggestion, perhaps I'll even get a moment to write it (assuming people think this is a good idea). During boot phase when DEVFS is probing around making devices, change the format of the minor number to just be 11 bits for type, and then 21 bits as an offset into a dynamically built kernel table (4 bytes/entry). This gives us 2097152 different device possibilities.. Still a limit (I hate limits) but far better than what we have today! -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Sun Jan 5 12:54:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA14025 for hackers-outgoing; Sun, 5 Jan 1997 12:54:29 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA14000; Sun, 5 Jan 1997 12:54:22 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id MAA10977; Sun, 5 Jan 1997 12:54:17 -0800 (PST) To: "Jonathan M. Bresler" cc: julian@whistle.com (Julian Elischer), hackers@freefall.freebsd.org, chat@freefall.freebsd.org Subject: Re: Usenix FreeBSD BoF when? In-reply-to: Your message of "Sat, 04 Jan 1997 19:52:46 PST." <199701050352.TAA10598@freefall.freebsd.org> Date: Sun, 05 Jan 1997 12:54:16 -0800 Message-ID: <10974.852497656@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Actually, I'm going to schedule it for 8pm on Wednesday. I just plain don't want to do it on Thursday. :) Jordan > Julian Elischer wrote: > > > > Jonathan M. Bresler wrote: > > > > > > the BoF (birds of a feather) page at usenix.org > > > http://www.usenix.org/ana97/bofs.html > > > does not list a FreeBSD BoF! > > > > > > shall we schedule one? > > > 8pm wednsesday or 8pm thursday look good ;) > > > > > > jmb > > > > I was just about to post about this! > > > > sounds a good time to me! > > > David O'Brien (sp?) wants 8pm thursday, so let's go with that, no? > no form to set one up over the web ;( > has to be done at the registration desk > first one to arrive gets the honors! > jmb From owner-freebsd-hackers Sun Jan 5 12:59:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA14393 for hackers-outgoing; Sun, 5 Jan 1997 12:59:53 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA14388 for ; Sun, 5 Jan 1997 12:59:49 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id PAA04010 for freebsd-hackers@freebsd.org; Sun, 5 Jan 1997 15:59:48 -0500 (EST) From: Charles Henrich Message-Id: <199701052059.PAA04010@crh.cl.msu.edu> Subject: A cool xterm? To: freebsd-hackers@freebsd.org Date: Sun, 5 Jan 1997 15:59:48 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone out there ever found a nice terminal window, something like Dec's mterm, or ssh for windows, or even better, NeXT's terminal? Xterm is peachy, except the scrollback just sucks :) -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Sun Jan 5 13:38:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA15775 for hackers-outgoing; Sun, 5 Jan 1997 13:38:11 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA15770 for ; Sun, 5 Jan 1997 13:38:07 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vh0Gc-0002vs-00; Sun, 5 Jan 1997 14:38:06 -0700 To: hackers@freebsd.org Subject: Got a strange one... Date: Sun, 05 Jan 1997 14:38:06 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there a way to enable bpf on only one interface of a system? I have a secure net and an insecure net with a machine sitting on both. There is no routing between the two at this time (eg gateway is set to 0). I have a need to sniff packets on my insecure net (err, ummm, rarpd has this need) and I was wondering if there would be some way to only enable bpf on the ed1 interface, while leaving it disabled on the ed0 interface. Thanks a bunch for any help that you might be able to render... Warner From owner-freebsd-hackers Sun Jan 5 14:46:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA18238 for hackers-outgoing; Sun, 5 Jan 1997 14:46:49 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA18233 for ; Sun, 5 Jan 1997 14:46:44 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id XAA02094 for ; Sun, 5 Jan 1997 23:46:40 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id XAA28862 for freebsd-hackers@FreeBSD.ORG; Sun, 5 Jan 1997 23:46:23 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.4/keltia-uucp-2.9) id XAA07787; Sun, 5 Jan 1997 23:45:26 +0100 (CET) Message-ID: Date: Sun, 5 Jan 1997 23:45:25 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-hackers@FreeBSD.ORG (FreeBSD Hackers' list) Subject: ld with -R weirdness X-Mailer: Mutt 0.55.15 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2837 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm the maintainer of the Perl5 hints file for freebsd and I tried to compile it with a shared libperl.so. I use -Wl,-R to gcc in order to give the linker to put the shared lib directory inside the executable. In suidperl case, the command line given to gcc (then ld) is the following: cc -L/usr/local/lib -Wl,-R,/usr/local/lib/perl5/i386-freebsd/5.00319/CORE -o suidperl perlmain.o sperl.o lib/auto/DynaLoader/DynaLoader.a libperl.so.3.19 `cat ext.libs` -lm -lc -lcrypt The problem is that afterward, ld.so is NOT able to find libperl.so.3.19... 608 [23:40] roberto@keltia:/build/perl5.003_10> ( cd lib ; ldd ../suidperl) ../suidperl: libperl.so.3.19 (0x0) -lm.2 => /usr/lib/libm.so.2.0 (0x8025000) -lc.3 => /usr/lib/libc.so.3.0 (0x803c000) -lcrypt.2 => /usr/lib/libcrypt.so.2.0 (0x80ad000) Even WITH LD_LIBRARY_PATH defined... 612 [23:44] roberto@keltia:/build/perl5.003_19> echo $LD_LIBRARY_PATH /work/build/perl5.003_19 When I patch the Makefile to have cc -L/usr/local/lib -Wl,-R,/usr/local/lib/perl5/i386-freebsd/5.00319/CORE -o suidperl perlmain.o sperl.o lib/auto/DynaLoader/DynaLoader.a -lperl `cat ext.libs` -lm -lc -lcrypt It works ! Looking inside the suidperl executable, I find the following weird strings: o/usr/local/lib/perl5/i386-freebsd/5.00319/CORE libperl.so.3.19 crypt Where does the 'o' before the path come from ? -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #33: Sat Dec 21 12:57:17 CET 1996 From owner-freebsd-hackers Sun Jan 5 14:56:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA18708 for hackers-outgoing; Sun, 5 Jan 1997 14:56:18 -0800 (PST) Received: from moog.kwest.com.au (root@moog.kwest.com.au [203.58.18.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA18690 for ; Sun, 5 Jan 1997 14:56:13 -0800 (PST) Received: (from cactoid@localhost) by moog.kwest.com.au (8.8.3/8.7.3) id JAA01183; Mon, 6 Jan 1997 09:56:06 +1100 (EST) Message-ID: X-Mailer: XFMail 1.0 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <199701052059.PAA04010@crh.cl.msu.edu> Date: Mon, 06 Jan 1997 09:46:24 +1100 (EST) Organization: Kwest Internetworks From: cactoid To: Charles Henrich Subject: RE: A cool xterm? Cc: freebsd-hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi.. I use "ansi_xterm", which is available from; /pub/Linux/X11/xutils/terms/ansi-xterm-R6.tgz (Yes it compiles just fine on FreeBSD) ..and inside that archive is a font called vga.pcf. A combination of these two make a really nice looking terminal. I have a customised .Xdefaults as well, here is the relevant bits: ! AnsiXTerm ansi_xterm*title: moog console ansi_xterm*font: vga ansi_xterm*iconName: nxterm ansi_xterm*reverseVideo: true ansi_xterm*scrollBar: true ansi_xterm*visualBell: true ansi_xterm*geometry: 80x32 ansi_xterm*saveLines: 256 ansi_xterm.vt100.background: Black ansi_xterm.vt100.foreground: LightGray !Eye saving pastel colors *VT100*color1: #ff4867 *VT100*color2: #77f0a0 *VT100*color3: #ffff90 *VT100*color4: #00a0b0 *VT100*color5: #fe80b0 *VT100*color6: #80c0ff Oh, btw - i also use neXtaw widgets, instead of plain old Athena. These can be downleeched from http://www.inf.ufrgs.br/~kojima/tkstep.html. If you need any help finding anything, just let me know. Remember to read the docs with ansi_xterm and add the define needed to get ansi colours. On 05-Jan-97 Charles Henrich wrote: >Has anyone out there ever found a nice terminal window, something like Dec's >mterm, or ssh for windows, or even better, NeXT's terminal? Xterm is peachy, >except the scrollback just sucks :) -- cactoid. /\/-> http://www.kwest.com.au /\/-> cactoid@kwest.com.au From owner-freebsd-hackers Sun Jan 5 16:28:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA25171 for hackers-outgoing; Sun, 5 Jan 1997 16:28:48 -0800 (PST) Received: from bios-nt.sunbeach.net (SUNBEACH.NET [205.214.199.134]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA25166 for ; Sun, 5 Jan 1997 16:28:32 -0800 (PST) Received: from bios-nt.sunbeach.net by bios-nt.sunbeach.net (NTMail 3.02.11) with ESMTP id ja089163 for ; Sun, 5 Jan 1997 15:45:33 -0400 Date: Sun, 5 Jan 1997 15:45:45 -0400 (AST) From: "Sean Batson (Sunbeach)" X-Sender: seanb012@bsdi.net To: hackers@freebsd.org Subject: Year 2000 time change(Format support) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is FreeBSD ready for the year 2000 time change and what are the effects if the support for this format isn't implemented asap with the OS? Sean Batson (Sunbeach) From owner-freebsd-hackers Sun Jan 5 16:59:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA26416 for hackers-outgoing; Sun, 5 Jan 1997 16:59:08 -0800 (PST) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA26411 for ; Sun, 5 Jan 1997 16:59:06 -0800 (PST) Received: (from jmacd@localhost) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) id QAA27318 for freebsd-hackers@freebsd.org; Sun, 5 Jan 1997 16:59:03 -0800 (PST) Date: Sun, 5 Jan 1997 16:59:03 -0800 (PST) From: Josh MacDonald Message-Id: <199701060059.QAA27318@paris.CS.Berkeley.EDU> To: freebsd-hackers@freebsd.org Subject: demangling cplusplus names in ld output Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I can't remember if FreeBSD's ld ever did demangle cpluplus names in its output, but I took a look in the source directory today and saw an extremenly old version of cplus-dem.c that was not even being linked with the ld sources and probably wouldn't do much good if it did. I certainly find it desirable, does anyone else? I've made the neccesary modifications. It involves wrapping a function call around the symbol->name field of each output statement, one small new function, and linking in the file cplus-dem.c from the gcc sources. Another approach requiring fewer modifications would be to fork a c++filt and pipe the output. I am willing to make either of these modifications (I'd have to go over my current sources with a little more scrutiny to make sure I didn't break it). -josh From owner-freebsd-hackers Sun Jan 5 17:09:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA26874 for hackers-outgoing; Sun, 5 Jan 1997 17:09:53 -0800 (PST) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA26869 for ; Sun, 5 Jan 1997 17:09:50 -0800 (PST) Received: from misery.sdf.com [204.244.213.33] by misery.sdf.com with smtp (Exim 1.59 #1) id 0vh3Zs-0005ua-00; Sun, 5 Jan 1997 17:10:12 -0800 Date: Sun, 5 Jan 1997 17:10:12 -0800 (PST) From: Tom Samplonius To: "Sean Batson (Sunbeach)" cc: hackers@freebsd.org Subject: Re: Year 2000 time change(Format support) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 5 Jan 1997, Sean Batson (Sunbeach) wrote: > Is FreeBSD ready for the year 2000 time change and > what are the effects if the support for this format > isn't implemented asap with the OS? > > Sean Batson > (Sunbeach) This doesn't belong on hackers@freebsd.org, but on questions@freebsd.org UNIX is mostly immune. Specific applications may not be. This really isn't an os issue at all. Tom From owner-freebsd-hackers Sun Jan 5 17:25:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA27593 for hackers-outgoing; Sun, 5 Jan 1997 17:25:28 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA27585 for ; Sun, 5 Jan 1997 17:25:25 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vh3oB-0003HW-00; Sun, 5 Jan 1997 18:24:59 -0700 To: "Sean Batson (Sunbeach)" Subject: Re: Year 2000 time change(Format support) Cc: hackers@freebsd.org In-reply-to: Your message of "Sun, 05 Jan 1997 15:45:45 -0400." References: Date: Sun, 05 Jan 1997 18:24:59 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message "Sean Batson (Sunbeach)" writes: : Is FreeBSD ready for the year 2000 time change and : what are the effects if the support for this format : isn't implemented asap with the OS? Yr2k is a noop for most unix systems, including FreeBSD. Warner From owner-freebsd-hackers Sun Jan 5 17:28:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA27788 for hackers-outgoing; Sun, 5 Jan 1997 17:28:04 -0800 (PST) Received: from hemi.com (hemi.com [204.132.158.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA27781 for ; Sun, 5 Jan 1997 17:28:02 -0800 (PST) Received: (from mbarkah@localhost) by hemi.com (8.8.4/8.7.3) id SAA09224; Sun, 5 Jan 1997 18:27:42 -0700 (MST) From: Ade Barkah Message-Id: <199701060127.SAA09224@hemi.com> Subject: Re: Year 2000 time change(Format support) To: tom@sdf.com (Tom Samplonius) Date: Sun, 5 Jan 1997 18:27:41 -0700 (MST) Cc: seanb012@sunbeach.net, hackers@freebsd.org In-Reply-To: from Tom Samplonius at "Jan 5, 97 05:10:12 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Tom Samplonius wrote: > > > Is FreeBSD ready for the year 2000 time change and > > what are the effects if the support for this format > > isn't implemented asap with the OS? ... > > (Sunbeach) > > UNIX is mostly immune. Specific applications may not be. This really > isn't an os issue at all. How about the year 2038 problem, then ? =-) I believe time_t overflows then. -Ade ------------------------------------------------------------------- Inet: mbarkah@hemi.com - HEMISPHERE ONLINE - ------------------------------------------------------------------- From owner-freebsd-hackers Sun Jan 5 17:42:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA28593 for hackers-outgoing; Sun, 5 Jan 1997 17:42:19 -0800 (PST) Received: from po1.glue.umd.edu (root@po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA28588 for ; Sun, 5 Jan 1997 17:42:17 -0800 (PST) Received: from ginger.eng.umd.edu (ginger.eng.umd.edu [129.2.103.20]) by po1.glue.umd.edu (8.8.3/8.7.3) with ESMTP id UAA27161; Sun, 5 Jan 1997 20:42:14 -0500 (EST) Received: from localhost (chuckr@localhost) by ginger.eng.umd.edu (8.8.3/8.7.3) with SMTP id UAA09379; Sun, 5 Jan 1997 20:42:13 -0500 (EST) X-Authentication-Warning: ginger.eng.umd.edu: chuckr owned process doing -bs Date: Sun, 5 Jan 1997 20:42:13 -0500 (EST) From: Chuck Robey X-Sender: chuckr@ginger.eng.umd.edu To: Josh MacDonald cc: freebsd-hackers@FreeBSD.org Subject: Re: demangling cplusplus names in ld output In-Reply-To: <199701060059.QAA27318@paris.CS.Berkeley.EDU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 5 Jan 1997, Josh MacDonald wrote: > > I can't remember if FreeBSD's ld ever did demangle cpluplus names > in its output, but I took a look in the source directory today and > saw an extremenly old version of cplus-dem.c that was not even > being linked with the ld sources and probably wouldn't do much good > if it did. > > I certainly find it desirable, does anyone else? I've made the > neccesary modifications. It involves wrapping a function call > around the symbol->name field of each output statement, one small > new function, and linking in the file cplus-dem.c from the gcc > sources. > > Another approach requiring fewer modifications would be to fork a > c++filt and pipe the output. > > I am willing to make either of these modifications (I'd have to go > over my current sources with a little more scrutiny to make sure > I didn't break it). Peter Wemm set up c++filt on it's own, it's already part of current. > > -josh > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sun Jan 5 18:05:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA29730 for hackers-outgoing; Sun, 5 Jan 1997 18:05:50 -0800 (PST) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA29725 for ; Sun, 5 Jan 1997 18:05:47 -0800 (PST) Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) with ESMTP id SAA27504; Sun, 5 Jan 1997 18:05:44 -0800 (PST) From: Josh MacDonald Message-Id: <199701060205.SAA27504@paris.CS.Berkeley.EDU> To: Chuck Robey cc: freebsd-hackers@freebsd.org Subject: Re: demangling cplusplus names in ld output In-reply-to: Your message of "Sun, 05 Jan 1997 20:42:13 EST." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <27497.852516340.1@paris.CS.Berkeley.EDU> Date: Sun, 05 Jan 1997 18:05:41 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Its not a question of whether c++filt is installed or not, its that when I link something, either I make every gcc link line pipe stderr to c++filt or I read mangled names when it tells me I have an undefined symbol. I'd rather see: /tmp/cc0004681.o: Undefined symbol `basic_string >::_(void)' referenced from text segment than: /tmp/cc0004601.o: Undefined symbol `___t12basic_string2ZiZt18string_char_traits1Zi' referenced from text segment > > Peter Wemm set up c++filt on it's own, it's already part of current. > > > > > -josh > > > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@eng.umd.edu | communications topic, C programming, and Unix. > 9120 Edmonston Ct #302 | > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > (301) 220-2114 | version 3.0 current -- and great FUN! > ----------------------------+----------------------------------------------- > From owner-freebsd-hackers Sun Jan 5 18:15:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA00196 for hackers-outgoing; Sun, 5 Jan 1997 18:15:11 -0800 (PST) Received: from po2.glue.umd.edu (root@po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA00190 for ; Sun, 5 Jan 1997 18:15:08 -0800 (PST) Received: from ginger.eng.umd.edu (ginger.eng.umd.edu [129.2.103.20]) by po2.glue.umd.edu (8.8.3/8.7.3) with ESMTP id VAA17911; Sun, 5 Jan 1997 21:15:06 -0500 (EST) Received: from localhost (chuckr@localhost) by ginger.eng.umd.edu (8.8.3/8.7.3) with SMTP id VAA09383; Sun, 5 Jan 1997 21:15:05 -0500 (EST) X-Authentication-Warning: ginger.eng.umd.edu: chuckr owned process doing -bs Date: Sun, 5 Jan 1997 21:15:05 -0500 (EST) From: Chuck Robey X-Sender: chuckr@ginger.eng.umd.edu To: Josh MacDonald cc: freebsd-hackers@freebsd.org Subject: Re: demangling cplusplus names in ld output In-Reply-To: <199701060205.SAA27504@paris.CS.Berkeley.EDU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 5 Jan 1997, Josh MacDonald wrote: > Its not a question of whether c++filt is installed or not, its that > when I link something, either I make every gcc link line pipe stderr to > c++filt or I read mangled names when it tells me I have an undefined > symbol. > > I'd rather see: > > /tmp/cc0004681.o: Undefined symbol `basic_string >::_(void)' referenced from text segment > > than: > > /tmp/cc0004601.o: Undefined symbol `___t12basic_string2ZiZt18string_char_traits1Zi' referenced from text segment Yeah, I understand, I use c++filt, but I don't understand what you're asking for ... we have it in the system, you can already pipe your error messages through it. It _seems_ to me that we have what you're asking for, so could you enlighten me on what's missing? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sun Jan 5 18:41:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA01596 for hackers-outgoing; Sun, 5 Jan 1997 18:41:31 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA01590 for ; Sun, 5 Jan 1997 18:41:28 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id NAA28087; Mon, 6 Jan 1997 13:11:12 +1030 (CST) From: Michael Smith Message-Id: <199701060241.NAA28087@genesis.atrad.adelaide.edu.au> Subject: Re: Ints (fwd) In-Reply-To: <199701031328.OAA14921@freebie.lemis.de> from Greg Lehey at "Jan 3, 97 02:28:06 pm" To: grog@lemis.de Date: Mon, 6 Jan 1997 13:11:11 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greg Lehey stands accused of saying: > > > > Just about every other multi-card bus ever invented uses daisy-chained > > interrupts or slot interrupts or some other manifestation of a sensible > > scheme. But not ISA. YOU CANNOT SHARE INTERRUPTS SAFELY ON ISA. > > Well, I don't know if I consider daisy-chaining sensible either. But That depends on whether you like being able to reorder the priority of interrupts in your system by shuffling cards around. Still, it allows interrupts to be shared, functionally. > the biggest problem with interrupt sharing on ISA used to be the > brain-dead circuitry of the UART board, not the bus nor the UART > itself. The circuits I have show that the interrupt output of the > UART goes to the *input* of an LS125 tri-state buffer, which then goes > via a DIP switch to the IRQ3*/IRQ4* lines. The enable input (active > low) of the LS125 gate is driven by OUT2*, which is effectively the > "interrupt enable" bit of the modem control register. > > The problem with this is that the gate drives the IRQ line at all > times, which isn't what tri-state is all about. The correct thing The IRQ lines were never specified as tri-state; see my other mail with references to Solari. The use of the 125 and the OUT2* signal mean that if the UART doesn't have interrupts enabled, another device can use the IRQ line. This is sensible design, given the context. > > ... but the inputs to the 8259 are _edge_triggered_. If another > > device is holding the line asserted, that doesn't count for a new > > interrupt. It also means that another edge can't occur. So not only > > is the second interrupt lost, but every interrupt after that is lost > > as well. > > I thought the interrupt was just a pulse. It certainly was on the > 8251. It works like this (Bruce, if you can be bothered, please correct me if I get this wrong) : 1) Device asserts IRQ signal. 2) 8259 detects edge, interrupts CPU 3) CPU performs interrupt acknowledge cycle, 8259 latches interrupt inputs. 4) CPU reads 8259, determines interrupting device 5) Interrupt handler manipulates peripheral, clears IRQ signal. The reason for the latching in step 3) is that the time between 2) and 3) can be arbitrarily large (if the CPU has interrupts off, for example), and another, higher-priority interrupt may come along in the meantime. If the input goes away between 2) and 3), you get a spurious interrupt (the 8259 reports it as IRQ 7). If the input never goes away, there's no way for another edge to occur, so 2) never happens. > Greg -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Jan 5 18:43:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA01665 for hackers-outgoing; Sun, 5 Jan 1997 18:43:47 -0800 (PST) Received: from gamma.pair.com (gamma.pair.com [207.86.128.13]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA01660 for ; Sun, 5 Jan 1997 18:43:43 -0800 (PST) Received: from [207.104.16.55] (ppp-207-104-16-55.snrf01.pacbell.net [207.104.16.55]) by gamma.pair.com (8.8.4/8.6.12) with SMTP id VAA08408; Sun, 5 Jan 1997 21:43:01 -0500 (EST) X-Envelope-To: hackers@FreeBSD.ORG X-Sender: erich@mail.powerwareintl.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 5 Jan 1997 18:52:14 -0800 To: Ade Barkah , tom@sdf.com (Tom Samplonius) From: erich@powerwareintl.com (Eric Harley) Subject: Re: Year 2000 time change(Format support) Cc: seanb012@sunbeach.net, hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 6:27 PM 1/5/97, Ade Barkah wrote: >Tom Samplonius wrote: >> >> > Is FreeBSD ready for the year 2000 time change and >> > what are the effects if the support for this format >> > isn't implemented asap with the OS? ... >> > (Sunbeach) >> >> UNIX is mostly immune. Specific applications may not be. This really >> isn't an os issue at all. > >How about the year 2038 problem, then ? =-) I believe time_t >overflows then. > AHHH!!!!! THE BIT BUCKETS GOING TO BLOW!! Eric +-------------------------------------------------------------+ |Eric Harley, VP Information Systems & CIO | |Powerware International | |http://www.powerwareintl.com/ | | | |Email: eric.harley@powerwareintl.com | |Web: http://www.powerwareintl.com/staff/erich/ | |PGP: http://www.powerwareintl.com/staff/erich/pgp.html | +-------------------------------------------------------------+ From owner-freebsd-hackers Sun Jan 5 19:57:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA05156 for hackers-outgoing; Sun, 5 Jan 1997 19:57:00 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA05149 for ; Sun, 5 Jan 1997 19:56:57 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id TAA12368; Sun, 5 Jan 1997 19:56:47 -0800 (PST) To: Chuck Robey cc: Josh MacDonald , freebsd-hackers@FreeBSD.org Subject: Re: demangling cplusplus names in ld output In-reply-to: Your message of "Sun, 05 Jan 1997 20:42:13 EST." Date: Sun, 05 Jan 1997 19:56:47 -0800 Message-ID: <12364.852523007@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Peter Wemm set up c++filt on it's own, it's already part of current. I think he knows that, Chuck. :-) If you'll just read his message again, you'll see that he lists forking and piping to c++filt as an option for solving the problem of ld symbol demangling (which I think you may have missed as the objective here). In otherwords, instead of this: jkh@time-> cc fump.cc -o fump /var/tmp/cc0123471.o: Undefined symbol `___8iostreami' referenced from text segment You'd get this: jkh@time-> cc fump.cc -o fump /var/tmp/cc0123471.o: Undefined symbol `iostream::iostream(int)' referenced from text segment See? :-) Jordan From owner-freebsd-hackers Sun Jan 5 20:07:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA05591 for hackers-outgoing; Sun, 5 Jan 1997 20:07:07 -0800 (PST) Received: from po1.glue.umd.edu (root@po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA05584 for ; Sun, 5 Jan 1997 20:07:03 -0800 (PST) Received: from ginger.eng.umd.edu (ginger.eng.umd.edu [129.2.103.20]) by po1.glue.umd.edu (8.8.3/8.7.3) with ESMTP id XAA29282; Sun, 5 Jan 1997 23:07:00 -0500 (EST) Received: from localhost (chuckr@localhost) by ginger.eng.umd.edu (8.8.3/8.7.3) with SMTP id XAA09407; Sun, 5 Jan 1997 23:06:59 -0500 (EST) X-Authentication-Warning: ginger.eng.umd.edu: chuckr owned process doing -bs Date: Sun, 5 Jan 1997 23:06:59 -0500 (EST) From: Chuck Robey X-Sender: chuckr@ginger.eng.umd.edu To: "Jordan K. Hubbard" cc: Josh MacDonald , freebsd-hackers@FreeBSD.org Subject: Re: demangling cplusplus names in ld output In-Reply-To: <12364.852523007@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 5 Jan 1997, Jordan K. Hubbard wrote: > > Peter Wemm set up c++filt on it's own, it's already part of current. > > I think he knows that, Chuck. :-) > > If you'll just read his message again, you'll see that he lists forking > and piping to c++filt as an option for solving the problem of ld symbol > demangling (which I think you may have missed as the objective here). > In otherwords, instead of this: > > jkh@time-> cc fump.cc -o fump > /var/tmp/cc0123471.o: Undefined symbol `___8iostreami' referenced from text segment > > You'd get this: > > jkh@time-> cc fump.cc -o fump > /var/tmp/cc0123471.o: Undefined symbol `iostream::iostream(int)' referenced from text segment That's what he said. You mean, I guess, having it happen automatically? Having ld invoke c++filt on it's output .... oh, I guess I'm used to piping it, didn't realize he was asking to have it happen automatically. Sorry, misunderstood. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sun Jan 5 20:43:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA06714 for hackers-outgoing; Sun, 5 Jan 1997 20:43:28 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA06708 for ; Sun, 5 Jan 1997 20:43:18 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id PAA27615; Mon, 6 Jan 1997 15:39:13 +1100 Date: Mon, 6 Jan 1997 15:39:13 +1100 From: Bruce Evans Message-Id: <199701060439.PAA27615@godzilla.zeta.org.au> To: grog@lemis.de, msmith@atrad.adelaide.edu.au Subject: Re: Ints (fwd) Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> The problem with this is that the gate drives the IRQ line at all >> times, which isn't what tri-state is all about. The correct thing > >The IRQ lines were never specified as tri-state; see my other mail with >references to Solari. The use of the 125 and the OUT2* signal mean >that if the UART doesn't have interrupts enabled, another device can >use the IRQ line. This is sensible design, given the context. Just about every optional device does it similarly. It looks like there has to be a third state to me (when the device isn't driving the IRQ line). One interesting side effect is that when the last device disconnects from an IRQ line, the line usually floats high, and the edge for this causes an interrupt. Thus "disabling" interrupts using the tri-state control usually causes an interrupt. >> I thought the interrupt was just a pulse. It certainly was on the >> 8251. Not for an 8250, or any device suitable for driving sensible (level triggered) interrupts directly. >It works like this (Bruce, if you can be bothered, please correct me if I >get this wrong) : > > 1) Device asserts IRQ signal. > 2) 8259 detects edge, interrupts CPU > 3) CPU performs interrupt acknowledge cycle, 8259 latches interrupt > inputs. > 4) CPU reads 8259, determines interrupting device > 5) Interrupt handler manipulates peripheral, clears IRQ signal. >The reason for the latching in step 3) is that the time between 2) and 3) >can be arbitrarily large (if the CPU has interrupts off, for example), and >another, higher-priority interrupt may come along in the meantime. But latching in step 3) doesn't help here. >If the input goes away between 2) and 3), you get a spurious interrupt (the >8259 reports it as IRQ 7). If the input never goes away, there's no >way for another edge to occur, so 2) never happens. No, the spurious interrupt is only generated if the interrupt goes away during the interrupt ack cycle. Interrupts that go up and down while they are masked have no effect (unless you watch them). Bruce From owner-freebsd-hackers Sun Jan 5 21:26:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA07963 for hackers-outgoing; Sun, 5 Jan 1997 21:26:06 -0800 (PST) Received: (from jmb@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA07957; Sun, 5 Jan 1997 21:26:01 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199701060526.VAA07957@freefall.freebsd.org> Subject: Re: Usenix FreeBSD BoF when? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sun, 5 Jan 1997 21:26:00 -0800 (PST) Cc: julian@whistle.com, hackers@freefall.freebsd.org, chat@freefall.freebsd.org In-Reply-To: <10974.852497656@time.cdrom.com> from "Jordan K. Hubbard" at Jan 5, 97 12:54:16 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk i wish that you had responeded earlier. i scheduled the bof for 8pm thursday when i arrived at usenix (sunday night 7pm localtime). fel free to reschedule ;) when you arrive. jmb jordan K. Hubbard wrote: > > Actually, I'm going to schedule it for 8pm on Wednesday. I just plain > don't want to do it on Thursday. :) > > Jordan > > > Julian Elischer wrote: > > > > > > Jonathan M. Bresler wrote: > > > > > > > > the BoF (birds of a feather) page at usenix.org > > > > http://www.usenix.org/ana97/bofs.html > > > > does not list a FreeBSD BoF! > > > > > > > > shall we schedule one? > > > > 8pm wednsesday or 8pm thursday look good ;) > > > > > > > > jmb > > > > > > I was just about to post about this! > > > > > > sounds a good time to me! > > > > > David O'Brien (sp?) wants 8pm thursday, so let's go with that, no? > > no form to set one up over the web ;( > > has to be done at the registration desk > > first one to arrive gets the honors! > > jmb > > From owner-freebsd-hackers Sun Jan 5 21:49:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA08933 for hackers-outgoing; Sun, 5 Jan 1997 21:49:14 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA08928 for ; Sun, 5 Jan 1997 21:49:11 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id QAA29246; Mon, 6 Jan 1997 16:18:22 +1030 (CST) From: Michael Smith Message-Id: <199701060548.QAA29246@genesis.atrad.adelaide.edu.au> Subject: Re: pib comments. In-Reply-To: <280.852383838@time.cdrom.com> from "Jordan K. Hubbard" at "Jan 4, 97 05:17:18 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 6 Jan 1997 16:18:21 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, mrcpu@cdsnet.net, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > ... In a modern GUI kinda environment, you'd have a button > for "show installation trees" and all the ports would suddenly jump > into columns, grouped by destination hierarchy, or if you clicked on > "Highlight -> LEGAL", all the tainted ones would show up in red. > > I defy you to provide that level of functionality without keeping a > cache. :-) I suggest that the Makefiles are a cache already (just a bad one 8), so the matter is one of degree, not principle. 8) I can just hear them screaming now; but it's OK, I put off redoing the whole ports mechanism in Tcl in favour of working on the FCF 8) > Jordan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Jan 5 22:07:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA10099 for hackers-outgoing; Sun, 5 Jan 1997 22:07:36 -0800 (PST) Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA09826 for ; Sun, 5 Jan 1997 22:03:51 -0800 (PST) Received: (babkin@localhost) by hq.icb.chel.su (8.8.3/8.6.5) id KAA08968; Mon, 6 Jan 1997 10:56:36 +0500 (ESK) From: "Serge A. Babkin" Message-Id: <199701060556.KAA08968@hq.icb.chel.su> Subject: Re: Year 2000 time change(Format support) To: mbarkah@hemi.com (Ade Barkah) Date: Mon, 6 Jan 1997 10:56:35 +0500 (ESK) Cc: tom@sdf.com, seanb012@sunbeach.net, hackers@freebsd.org In-Reply-To: <199701060127.SAA09224@hemi.com> from "Ade Barkah" at Jan 5, 97 06:27:41 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > How about the year 2038 problem, then ? =-) I believe time_t > overflows then. I believe there will be no 32-bit computers anymore then :-) -SB From owner-freebsd-hackers Sun Jan 5 22:45:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA13970 for hackers-outgoing; Sun, 5 Jan 1997 22:45:07 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA13962 for ; Sun, 5 Jan 1997 22:45:04 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id WAA12972; Sun, 5 Jan 1997 22:44:51 -0800 (PST) To: Michael Smith cc: mrcpu@cdsnet.net, hackers@FreeBSD.ORG Subject: Re: pib comments. In-reply-to: Your message of "Mon, 06 Jan 1997 16:18:21 +1030." <199701060548.QAA29246@genesis.atrad.adelaide.edu.au> Date: Sun, 05 Jan 1997 22:44:51 -0800 Message-ID: <12969.852533091@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I suggest that the Makefiles are a cache already (just a bad one 8), so > the matter is one of degree, not principle. 8) Isn't that's sort of like saying "the haystack is the storage area for the needle, so the difficulty in finding it is simply a matter of degree, not principle." :-) Jordan From owner-freebsd-hackers Sun Jan 5 22:59:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA14546 for hackers-outgoing; Sun, 5 Jan 1997 22:59:42 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA14494 for ; Sun, 5 Jan 1997 22:59:34 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id RAA32628; Mon, 6 Jan 1997 17:52:43 +1100 Date: Mon, 6 Jan 1997 17:52:43 +1100 From: Bruce Evans Message-Id: <199701060652.RAA32628@godzilla.zeta.org.au> To: babkin@hq.icb.chel.su, mbarkah@hemi.com Subject: Re: Year 2000 time change(Format support) Cc: hackers@FreeBSD.org, seanb012@sunbeach.net, tom@sdf.com Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> How about the year 2038 problem, then ? =-) I believe time_t >> overflows then. > >I believe there will be no 32-bit computers anymore then :-) I believe there are no 31-bit computers ever :-). Bruce From owner-freebsd-hackers Sun Jan 5 23:19:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA15824 for hackers-outgoing; Sun, 5 Jan 1997 23:19:02 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id XAA15819 for ; Sun, 5 Jan 1997 23:18:59 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vh9KL-0004U0-00; Mon, 6 Jan 1997 00:18:33 -0700 To: Ade Barkah Subject: Re: Year 2000 time change(Format support) Cc: tom@sdf.com (Tom Samplonius), seanb012@sunbeach.net, hackers@freebsd.org In-reply-to: Your message of "Sun, 05 Jan 1997 18:27:41 MST." <199701060127.SAA09224@hemi.com> References: <199701060127.SAA09224@hemi.com> Date: Mon, 06 Jan 1997 00:18:33 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199701060127.SAA09224@hemi.com> Ade Barkah writes: : How about the year 2038 problem, then ? =-) I believe time_t : overflows then. Only if we're all still running 32 bit hardware, or with a 32 bit time_t :-) Warner From owner-freebsd-hackers Sun Jan 5 23:47:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA17302 for hackers-outgoing; Sun, 5 Jan 1997 23:47:48 -0800 (PST) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA17296 for ; Sun, 5 Jan 1997 23:47:44 -0800 (PST) Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) with ESMTP id XAA28029 for ; Sun, 5 Jan 1997 23:47:42 -0800 (PST) From: Josh MacDonald Message-Id: <199701060747.XAA28029@paris.CS.Berkeley.EDU> To: freebsd-hackers@freebsd.org Subject: Re: demangling cplusplus names in ld output In-reply-to: Your message of "Sun, 05 Jan 1997 23:06:59 EST." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <28022.852536860.1@paris.CS.Berkeley.EDU> Date: Sun, 05 Jan 1997 23:47:41 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In any case, there is an unused file /usr/src/gnu/usr.bin/ld/cplus-dem.c which is an old and out of date version of the file /usr/src/contrib/gcc/cplus-dem.c. I assume, since the out of date demangling code is in the ld directory, and I might even recall it in the past, that there used to be this type of support. Can anyone fill me in? -josh On Sun, 5 Jan 1997, Jordan K. Hubbard wrote: > In otherwords, instead of this: > > jkh@time-> cc fump.cc -o fump > /var/tmp/cc0123471.o: Undefined symbol `___8iostreami' referenced from text segment > > You'd get this: > > jkh@time-> cc fump.cc -o fump > /var/tmp/cc0123471.o: Undefined symbol `iostream::iostream(int)' referenced from text segment From owner-freebsd-hackers Mon Jan 6 00:15:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA18526 for hackers-outgoing; Mon, 6 Jan 1997 00:15:14 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA18521 for ; Mon, 6 Jan 1997 00:15:09 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id SAA00493; Mon, 6 Jan 1997 18:44:58 +1030 (CST) From: Michael Smith Message-Id: <199701060814.SAA00493@genesis.atrad.adelaide.edu.au> Subject: Re: pib comments. In-Reply-To: <12969.852533091@time.cdrom.com> from "Jordan K. Hubbard" at "Jan 5, 97 10:44:51 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 6 Jan 1997 18:44:57 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, mrcpu@cdsnet.net, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > I suggest that the Makefiles are a cache already (just a bad one 8), so > > the matter is one of degree, not principle. 8) > > Isn't that's sort of like saying "the haystack is the storage area for > the needle, so the difficulty in finding it is simply a matter of > degree, not principle." :-) Yup, you got it. You could perhaps say that at the moment, with the hay all piled up, the needle is practically impossible to find. With a little reorganisation though (buldoze the hay flat), finding the needle (with a suitable magnet) would be relatively trivial. > Jordan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jan 6 01:29:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA22468 for hackers-outgoing; Mon, 6 Jan 1997 01:29:38 -0800 (PST) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id BAA22459 for ; Mon, 6 Jan 1997 01:29:35 -0800 (PST) Received: from ant.us.dell.com (ant.us.dell.com [198.64.66.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id DAA13399; Mon, 6 Jan 1997 03:28:09 -0600 Message-Id: <3.0.1.32.19970106032347.0067e4ac@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com (Unverified) X-Mailer: Windows Eudora Light Version 3.0.1 beta 4 (32) Date: Mon, 06 Jan 1997 03:28:09 -0600 To: Bruce Evans , grog@lemis.de, msmith@atrad.adelaide.edu.au From: Tony Overfield Subject: Re: Ints (fwd) Cc: hackers@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >One interesting side effect is that when the last device >disconnects from an IRQ line, the line usually floats high, and the >edge for this causes an interrupt. Thus "disabling" interrupts using >the tri-state control usually causes an interrupt. True, though on a "PC compatible" system, the IRQ _always_ goes high when not driven because there is always a pull-up resistor. >>> I thought the interrupt was just a pulse. It certainly was on the >>> 8251. > >Not for an 8250, or any device suitable for driving sensible (level >triggered) interrupts directly. There is a scheme for sharing ISA edge-triggered interrupts that involves pulsing. It works by declaring that the IRQ will remain high (by pull-up, not driven) until a device wants interrupt service. At that time the device pulses the IRQ low for 100-200 ns and then releases it again to cause the rising edge. Eventually, the interrupt occurs, and the interrupt service routine(s) must then check all the registered devices to see which one(s) caused the interrupt. Because the IRQ is pulled high by the pull-up resistor, spurious interrupts won't be generated. This may seem peculiar, but I've seen it in operation. >> 1) Device asserts IRQ signal. >> 2) 8259 detects edge, interrupts CPU >> 3) CPU performs interrupt acknowledge cycle, 8259 latches interrupt >> inputs. >> 4) CPU reads 8259, determines interrupting device >> 5) Interrupt handler manipulates peripheral, clears IRQ signal. >> >>If the input goes away between 2) and 3), you get a spurious interrupt (the >>8259 reports it as IRQ 7). If the input never goes away, there's no >>way for another edge to occur, so 2) never happens. > >No, the spurious interrupt is only generated if the interrupt goes away >during the interrupt ack cycle. Right, the CPU must recognize the CPU INTR signal and begin processing the interrupt before it can become spurious. A spurious interrupt results if an int-ack cycle occurs but the 8259 does not find an unmasked IRQ that is at a high level. Removing an IRQ before the 8259 sees its level during the int-ack usually causes an IRQ 7 (or always does, if the bouncing IRQ was a small one). But, as you may already know, you can also get a spurious IRQ 15 by removing an upper IRQ at just the right time (guess: during the 8259 IRQ scan, after the primary 8259 sees the cascade, but before the secondary 8259 sees the upper IRQ.) But the spurious interrupt is still usually IRQ 7, since the susceptible timing window is a little larger. It's larger because the IRQ could go away any time after the CPU recognizes the interrupt (before the int-ack even begins), but before the 8259 later scans for the (now missing) IRQ. Also, for whatever reasons, if the CPU were to wrongly see an asserted CPU INTR signal when the 8259 wasn't requesting it, a spurious IRQ 7 would result. Tony From owner-freebsd-hackers Mon Jan 6 01:39:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA23182 for hackers-outgoing; Mon, 6 Jan 1997 01:39:52 -0800 (PST) Received: from deputy.pavilion.co.uk (deputy.pavilion.co.uk [194.242.128.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA23177 for ; Mon, 6 Jan 1997 01:39:48 -0800 (PST) Received: from c493.tgb.toyota.co.uk (tgb-isd.demon.co.uk [194.222.88.26]) by deputy.pavilion.co.uk (8.7/8.7) with SMTP id JAA24767; Mon, 6 Jan 1997 09:38:30 GMT Date: Mon, 6 Jan 1997 09:38:30 GMT Message-Id: <199701060938.JAA24767@deputy.pavilion.co.uk> X-Sender: aledm@mailhost.pavilion.co.uk (Unverified) X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Jaye Mathisen , hackers@freebsd.org From: Aled Morris Subject: Re: Any good reason to run portmap on a non NFS'd/RPC'd machine? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 14:55 02/01/97 -0800, Jaye Mathisen wrote: >I'm not using YP or any of that stuff. If not, then it seems like >something that would be good to turn into a sysconfig variable. Nor do I - I usually rename "portmap" so it doesn't get found by RC. I would support the proposal for a sysconfig variable (although to avoid beginner's problems, there should probably be some logic in RC to override "portmap=NO" if YP, NFS or any other good stuff is enabled.) Aled -- telephone +44 973 207987 O- From owner-freebsd-hackers Mon Jan 6 01:48:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA23680 for hackers-outgoing; Mon, 6 Jan 1997 01:48:55 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA23675 for ; Mon, 6 Jan 1997 01:48:51 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id KAA17076 for ; Mon, 6 Jan 1997 10:50:54 +0100 (MET) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.3/8.6.9) id LAA00833 for freebsd-hackers@freefall.cdrom.com; Mon, 6 Jan 1997 11:04:12 +0100 (MET) Date: Mon, 6 Jan 1997 11:04:12 +0100 (MET) From: Christoph Kukulies Message-Id: <199701061004.LAA00833@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: Lignux - RMS article (pointer fyi) Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just for those being interested in GPL Copyright issues: http://www.ssc.com/lj/issue30/rms.html contains an article of Richard Stallman on the issue of Linux and GNU (GPL). --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Mon Jan 6 04:06:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA01232 for hackers-outgoing; Mon, 6 Jan 1997 04:06:05 -0800 (PST) Received: from sundial.sundial.net (root@sundial.sundial.net [204.181.150.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA01194; Mon, 6 Jan 1997 04:05:55 -0800 (PST) Received: from pbsj.com (pbsj.com [204.181.150.140]) by sundial.sundial.net (8.8.3/8.6.5) with SMTP id HAA19109; Mon, 6 Jan 1997 07:05:51 -0500 (EST) Received: from ORLANDO-Message_Server by pbsj.com with Novell_GroupWise; Mon, 06 Jan 1997 07:06:25 -0500 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Mon, 06 Jan 1997 07:10:53 -0500 From: Frank Hahnel To: freebsd-hackers@freebsd.org, freebsd-hardware@@freebsd.org, freebsd-questions@freebsd.org Subject: Unsubscribe Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe freebsd-questions fjhahnel@pbsj.com unsubscribe freebsd-hardware fjhahnel@pbsj.com From owner-freebsd-hackers Mon Jan 6 06:30:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA07717 for hackers-outgoing; Mon, 6 Jan 1997 06:30:22 -0800 (PST) Received: from border.com (borderware.com [199.71.190.98]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA07702 for ; Mon, 6 Jan 1997 06:30:19 -0800 (PST) Received: by janus.border.com id <30786-1>; Mon, 6 Jan 1997 09:29:22 -0500 Date: Mon, 6 Jan 1997 09:30:03 -0500 From: jerry@border.com (Jerry Kendall) To: Message-Id: <97Jan6.092922est.30786-1@janus.border.com> Content-Type: text Apparently-To: freebsd-hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey people, Anyone using the 3COM Fast Etherlink 3C595 T4 Parallel Tasking 10/100BASE-T4 PCI network adapter ??? If so, any problems ??? What source files do I need? etc.... -- Jerry Kendall | Senior Systems Developer, BorderWare Firewall Server jerry@border.com | Secure Computing Canada Ltd. +1 416 813 2052 (Tel) | 100 University Avenue. Suite 700 +1 416 813 2001 (Fax) | Toronto, Ontario M5J 1V6 CANADA From owner-freebsd-hackers Mon Jan 6 06:44:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA08295 for hackers-outgoing; Mon, 6 Jan 1997 06:44:17 -0800 (PST) Received: from pardal ([200.255.244.56]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id GAA08289 for ; Mon, 6 Jan 1997 06:44:10 -0800 (PST) Received: from paulo (paulo [200.1.1.51]) by pardal (8.6.12/8.6.9) with SMTP id MAA28639 for ; Mon, 6 Jan 1997 12:48:04 -0200 Message-ID: <32D0F453.2781E494@sul.com.br> Date: Mon, 06 Jan 1997 12:47:15 +0000 From: Paulo Cesar Pereira de Andrade Organization: FiscoData X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.1.0-RELEASE i386) MIME-Version: 1.0 To: FreeBSD hackers Subject: sig-11 plague Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Another day i read a message saying the phrase *sig-11 plague*, and i thought i was having the same problem. Two weeks ago i upgrade from my 386 to an amd 5x86, and after a hard time to get FreeBSD installed *manually*, (i was receiveing messages like: *tar: child returned code 1* *gzip: not in compressed format*), i restarted working on a xpaint like program that i am writing on my free time. But cc1 was frequentely receiving a sig 11, sometimes a sig 6, and this is the better case when it failed, i get .o files that did not link because were corrupt. I resolved the problem in the BIOS setup, i disabled the external cache, and now cc1 does not fail. After that, i was browsing the handbook, and read the section 21.1.1.4, where there are a description of PCI. I am not a hardware expert, and i also dont know what pci i have, but if it is a Mercury, i have done the correct work-around. Im using FreeBSD 2.1.0. I have now a doubt: is this a feature of pci or is a todo in FreeBSD (perhaps a done, since im using 2.1.0) or is i that have a not good hardware or another thing ? []s. Paulo. From owner-freebsd-hackers Mon Jan 6 07:48:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA12464 for hackers-outgoing; Mon, 6 Jan 1997 07:48:56 -0800 (PST) Received: (from jmb@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA12457; Mon, 6 Jan 1997 07:48:53 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199701061548.HAA12457@freefall.freebsd.org> Subject: Re: Usenix FreeBSD BoF when? To: jmb@freefall.freebsd.org (Jonathan M. Bresler) Date: Mon, 6 Jan 1997 07:48:53 -0800 (PST) Cc: obrien@antares.aero.org, julian@whistle.com, hackers@freefall.freebsd.org, chat@freefall.freebsd.org In-Reply-To: <199701051331.FAA29361@freefall.freebsd.org> from "Jonathan M. Bresler" at Jan 5, 97 05:31:41 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The FreeBSD BoF has been changed to 8pm Wednesday and will take place in Salons 3 and 4 (seating for 100 people so come early) jmb From owner-freebsd-hackers Mon Jan 6 08:06:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA13437 for hackers-outgoing; Mon, 6 Jan 1997 08:06:50 -0800 (PST) Received: from anacreon.sol.net (anacreon.sol.net [206.55.64.116]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA13431 for ; Mon, 6 Jan 1997 08:06:46 -0800 (PST) Received: from solaria.sol.net (solaria.sol.net [206.55.65.75]) by anacreon.sol.net (8.6.12/8.6.12) with ESMTP id KAA05456; Mon, 6 Jan 1997 10:06:41 -0600 Received: from localhost by solaria.sol.net (8.5/8.5) id KAA26670; Mon, 6 Jan 1997 10:06:40 -0600 From: Joe Greco Message-Id: <199701061606.KAA26670@solaria.sol.net> Subject: Re: Any good reason to run portmap on a non NFS'd/RPC'd To: aledm@routers.co.uk (Aled Morris) Date: Mon, 6 Jan 97 10:06:38 CST Cc: mrcpu@cdsnet.net, hackers@freebsd.org In-Reply-To: <199701060938.JAA24767@deputy.pavilion.co.uk> from "Aled Morris" at Jan 6, 97 09:38:30 am X-Mailer: ELM [version 2.4dev PL65] MIME-Version: 1.0 Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > At 14:55 02/01/97 -0800, Jaye Mathisen wrote: > >I'm not using YP or any of that stuff. If not, then it seems like > >something that would be good to turn into a sysconfig variable. > > Nor do I - I usually rename "portmap" so it doesn't get found by RC. > > I would support the proposal for a sysconfig variable (although to avoid > beginner's problems, there should probably be some logic in RC to > override "portmap=NO" if YP, NFS or any other good stuff is enabled.) How about a "portmap=AUTO"? If set, it enables portmap is YP/NFS/etc are enabled. If "NO", it yells during startup that you are broken, if YP/NFS/etc are enabled. If "YES", well, obvious :-) Just a thought. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-hackers Mon Jan 6 08:53:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA15708 for hackers-outgoing; Mon, 6 Jan 1997 08:53:15 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA15690; Mon, 6 Jan 1997 08:53:11 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id IAA02764; Mon, 6 Jan 1997 08:52:20 -0800 (PST) Message-Id: <199701061652.IAA02764@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: "Jonathan M. Bresler" cc: obrien@antares.aero.org, julian@whistle.com, hackers@freefall.freebsd.org, chat@freefall.freebsd.org Subject: Re: Usenix FreeBSD BoF when? In-reply-to: Your message of "Mon, 06 Jan 1997 07:48:53 PST." <199701061548.HAA12457@freefall.freebsd.org> From: David Greenman Reply-To: dg@root.com Date: Mon, 06 Jan 1997 08:52:20 -0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >The FreeBSD BoF has been changed to > > 8pm Wednesday > >and will take place in Salons 3 and 4 (seating for 100 people so come early) This probably won't be big enough. It was standing room only at the last one, and we probably could have seated at least 150 people. I'm expecting things to be even larger with a need for at least 200 seats. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Jan 6 09:20:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA16833 for hackers-outgoing; Mon, 6 Jan 1997 09:20:01 -0800 (PST) Received: from jump.net (serv1-2.jump.net [204.238.120.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA16779; Mon, 6 Jan 1997 09:19:55 -0800 (PST) Received: by jump.net (8.8.4/BERK-6.8.11) id LAA24277; Mon, 6 Jan 1997 11:19:38 -0600 (CST) Date: Mon, 6 Jan 1997 11:19:37 -0600 (CST) From: Lee Crites To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org cc: Lee Crites Subject: Anyone in the Round Rock/Austin Texas area??? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'd like/need some help with a few things on my FreeBSD box. Who out there is in the Round Rock, Texas and/or Austin, Texas area that would be willing to help out? Lee Crites (Please respond privately -- that way no more bandwidth is wasted on this) From owner-freebsd-hackers Mon Jan 6 09:47:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA18450 for hackers-outgoing; Mon, 6 Jan 1997 09:47:48 -0800 (PST) Received: from mailhub.aros.net (mailhub.aros.net [207.173.16.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA18445 for ; Mon, 6 Jan 1997 09:47:42 -0800 (PST) Received: from terra.aros.net (terra.aros.net [207.173.16.10]) by mailhub.aros.net (8.7.6/Unknown) with ESMTP id KAA28085 for ; Mon, 6 Jan 1997 10:47:35 -0700 (MST) Received: (from angio@localhost) by terra.aros.net (8.7.6/8.6.12) id KAA04137 for hackers@freebsd.org; Mon, 6 Jan 1997 10:42:35 -0700 From: Dave Andersen Message-Id: <199701061742.KAA04137@terra.aros.net> Subject: NFS sillyrenamedir To: hackers@freebsd.org Date: Mon, 6 Jan 1997 10:42:34 -0700 (MST) X-Mailer: ELM [version 2.4 PL25 PGP2] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As was pointed out earlier, the NFS system in -2.2 is still subject to kernel panics when someone: mkdir tmp ; mkdir tmp/tmp cd tmp mv tmp .. This panic is caused by the line in nfs_vnops.c: #ifndef DIAGNOSTIC if (vp->v_type == VDIR) panic("nfs: sillyrename dir"); #endif I'm not very familiar with the FS code in FreeBSD. Is there an easy fix for this (e.g. just skipping the panic code), or does it require a more substantial change? (Or is someone already working on this that I missed?) -Dave -- angio@aros.net Complete virtual hosting and business-oriented system administration Internet services. (WWW, FTP, email) http://www.aros.net/ http://www.aros.net/about/virtual "There are only two industries that refer to their customers as 'users'." From owner-freebsd-hackers Mon Jan 6 10:19:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA19986 for hackers-outgoing; Mon, 6 Jan 1997 10:19:34 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA19885 for ; Mon, 6 Jan 1997 10:19:11 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA12190; Mon, 6 Jan 1997 11:06:50 -0700 From: Terry Lambert Message-Id: <199701061806.LAA12190@phaeton.artisoft.com> Subject: Re: ipretard.c selective tcp/ip queues and throughput limiters To: avalon@coombs.anu.edu.au (Darren Reed) Date: Mon, 6 Jan 1997 11:06:50 -0700 (MST) Cc: terry@lambert.org, avalon@coombs.anu.edu.au, julian@whistle.com, luigi@labinfo.iet.unipi.it, proff@iq.org, danny@panda.hilink.com.au, hackers@FreeBSD.ORG In-Reply-To: <199701021045.CAA27880@freefall.freebsd.org> from "Darren Reed" at Jan 2, 97 09:42:04 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > However, some simple functions such as malloc() are *much* different when > compiled for kernel vs user. > > You can't compile a routine in user-space that uses mbufs without doing > some extra work. Then you have to deal with spl's that don't exist, etc. > > And so on. Yes, that's just developement environment glue. It's trivial to hack such code from a working kernel... The main problem is object import/export interfaces, and allocation triggers for the shadow objects. It can be done. I'm more interested in doing FS stacking layer work in user space, which doesn't require most of the effort making everything you might want to do work in user space. > I was thinking about this the other day and wondered how easy would it be > to make the kernel compile as a user process ? I've wondered this several times now... basically, I'd like to run a source debugged kernel on an auxillary CPU on my SMP box. But to do that will require religiously abstracting the HAL for interrupt handling and page handling and similar functions where the target CPU might conflict access with my master CPU... *Actually*... I'd like to run a source debug on a 3 CPU SMP system from the 4th CPU of the box... It's a nice dream. 8-). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 10:20:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA20087 for hackers-outgoing; Mon, 6 Jan 1997 10:20:15 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA20039 for ; Mon, 6 Jan 1997 10:20:01 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA12205; Mon, 6 Jan 1997 11:10:33 -0700 From: Terry Lambert Message-Id: <199701061810.LAA12205@phaeton.artisoft.com> Subject: Re: Shutdown tip To: seanb012@sunbeach.net (Sean Batson) Date: Mon, 6 Jan 1997 11:10:33 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: <32C87FC1.41C67EA6@sunbeach.net> from "Sean Batson" at Dec 30, 96 10:51:45 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The next time you guys are about to shutdown try this: > > shutdown -h now;exit > > the above command should be done once all of the users > are logged off. The end results would always be this: > > syncing ...disk > press anykey to reboot. > no buffers to rewrite to the filesystem. > > Just do an ordernary shutdown -h now, you'll get the > usual syncing ..3 4 disk ,... > > How if someone where modify the code for the shutdown > command to do a root user logout then fork or spawn > the rest of the code for the shutdown thus avoiding > the site of the buffer related numbers each time on > a shutdown. The problem is in the use of a non-"/" current directory actig as an open file reference for the processes that are still live. The correct thing to do is to orderly shutdown the processes. You would probably ss the same (correct) behaviour if you forced a shutdown to occur only in "/" (like SVR4 does) and modified the root/chroot fd code to always exist in the process instead of conditionally existing, and then simplifying the namei() code to unconditionally reference the process value. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 10:44:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA21072 for hackers-outgoing; Mon, 6 Jan 1997 10:44:56 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA21067 for ; Mon, 6 Jan 1997 10:44:53 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA12254; Mon, 6 Jan 1997 11:35:05 -0700 From: Terry Lambert Message-Id: <199701061835.LAA12254@phaeton.artisoft.com> Subject: Re: cvs commit: src/usr.bin/vi Makefile To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 6 Jan 1997 11:35:05 -0700 (MST) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199612311239.NAA24824@uriah.heep.sax.de> from "J Wunsch" at Dec 31, 96 01:39:24 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I think, most people will end up with the full set of binaries anyway. > Only people with 100 MB or smaller disks will think about the bloat. > At a time where you can't even buy a disk smaller than 1 GB, we should > probably not waste too much energy in too much splitting. The IBM systems sold for ~$400 as nonames in Computer Shopper come with 60MB drives. They are interesting for running FreeBSD because: o They have barely enough memory to do it o They have IR interfaces o They have cheap GPS add-ons A small box with small memory (power requirements) is good for lots of things, especially with an IR interface. As an example, I have a close relative whi has suffered from ischemia in the region of the Hypothalamus/pons. As a result, there is an impairment of the short-to-long-term memory commit mechanism. This makes it difficult to remember things, such as "when do I take my medication?". By carrying around a PDA-level device (ie: ~60M drive) with an IR link, they can be reminded of ">BEEP< ...take the blue pill now" type things. The IR link lets them get a schedule download of "to do today" items when they bring the PDA home (">BEEP< ...plug in the PDA for recharging and schedule download -- it's time for bed"). Scheduled things like ">BEEP< ...time to do laundry", etc.. A small power consumption system with high capability and single application fault tolerance (ie: not Windows 95, DOS, or other non-protected mode OS) is the difference between a functional person and someone who needs to be warehoused in a nursing home. There is significant benefit to a small "minimal system" that fits in a small amount of storage and still has room for a few applications. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 10:59:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA21675 for hackers-outgoing; Mon, 6 Jan 1997 10:59:28 -0800 (PST) Received: from border.com (borderware.com [199.71.190.98]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA21670 for ; Mon, 6 Jan 1997 10:59:24 -0800 (PST) Received: by janus.border.com id <30786-2>; Mon, 6 Jan 1997 13:58:32 -0500 Message-Id: <97Jan6.135832est.30786-2@janus.border.com> X-Mailer: exmh version 1.6.7 5/3/96 To: jerry@border.com (Jerry Kendall) cc: freebsd-hackers@freebsd.org In-reply-to: Your message of "Mon, 06 Jan 1997 09:30:03 EST." <97Jan6.092922est.30786-1@janus.border.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 6 Jan 1997 13:59:15 -0500 From: Jerry Kendall Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Buy the way, I orgot to mention, in FreeBSD 2.1.5 or 2.1.6 setups. I noticed that the vx0 ethernet driver is for the 3C595 but nothing mentions the 3COM Fast Etherlink 3C595 T4. > Hey people, > Anyone using the 3COM Fast Etherlink 3C595 T4 > Parallel Tasking 10/100BASE-T4 PCI network adapter ??? > > If so, any problems ??? > What source files do I need? > etc.... > -- Jerry Kendall | Senior Systems Developer, BorderWare Firewall Server jerry@border.com | Secure Computing Canada Ltd. +1 416 813 2052 (Tel) | 100 University Avenue. Suite 700 +1 416 813 2001 (Fax) | Toronto, Ontario M5J 1V6 CANADA From owner-freebsd-hackers Mon Jan 6 11:43:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA23637 for hackers-outgoing; Mon, 6 Jan 1997 11:43:33 -0800 (PST) Received: from smtp-gw01.ny.us.ibm.net (smtp-gw01.ny.us.ibm.net [165.87.194.252]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA23628 for ; Mon, 6 Jan 1997 11:43:28 -0800 (PST) Received: (from uucp@localhost) by smtp-gw01.ny.us.ibm.net (8.6.9/8.6.9) id TAA84776 for ; Mon, 6 Jan 1997 19:43:25 GMT Message-Id: <199701061943.TAA84776@smtp-gw01.ny.us.ibm.net> Received: from slip166-72-229-67.va.us.ibm.net(166.72.229.67) by smtp-gw01.ny.us.ibm.net via smap (V1.3mjr) id smaonMCKs; Mon Jan 6 19:42:11 1997 Reply-To: From: "Steve Sims" To: "Hackers" Subject: ed0 boot [p]roms Date: Mon, 6 Jan 1997 14:40:42 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Who's the resident expert on boot ROMs for ed devices? I'm thinking about building a diskless / floppy-less machine and have no earthly idea how to proceed. I haven't done diskless in years, since we ran a secure net off of a Novell server. That was painless, but the cards (with ROMs) ran about $300 back then. I figure that with all these el-cheapo NE-2000 clones floating around, somebody ought to have an idea on how to burn or where to buy an appropriate bootp/tftp-able ROM for 'em. Any takers? ...sjs.. From owner-freebsd-hackers Mon Jan 6 12:01:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA24291 for hackers-outgoing; Mon, 6 Jan 1997 12:01:58 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA24277 for ; Mon, 6 Jan 1997 12:01:55 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id MAA16298 for ; Mon, 6 Jan 1997 12:02:34 -0800 (PST) Received: (qmail 16169 invoked by uid 110); 6 Jan 1997 20:01:16 -0000 Message-ID: <19970106200116.16168.qmail@suburbia.net> Subject: new firewall code [uid/gid/bind() etc] To: hackers@freebsd.org, security@freebsd.org Date: Tue, 7 Jan 1997 07:01:16 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I tried posting the patches but, at 55k, it seems majordumbo has (silently) rejected them. You may find them at: ftp://suburbia.net/tmp/ipfw.diff My "socket credentials" patches allow you to: punch wormholes, or restrict access to the IPPORT_RESERVED space, or restrict access to bind() altogether based on: (a) uid (b) gid (including secondary groups) (c) port (d) protocol (e) interface And more importantly: Restrict access to packets being sent/received on any socket based on: (a) the packet (per normal ipfw rules) (b) uid (c) gid (including secondary groups) The former permits constructs like: /* let uid sendmail bind to port 25 */ # ipfw add accept wormhole on tcp from any 25 to any uid sendmail bind /* only let inetd bind - we presume inetd still needs to run as root for uid switching when forking off clients */ # addgroup inetd # chgrp inetd /usr/sbin/inetd # chmod 2700 /usr/sbin/inetd # killall inetd # ipfw add accept all from any to any bind gid inetd uid root # /* default policy is to deny bind */ /* keep those without security clearance out of secret network */ # ipfw add accept all from any to any via ed0 gid secret # ipfw add deny all from any to any via ed0 gid any Loging has also been enhanced: # ipfw add 60000 accept log all from any to any bind /* example of named starting up */ ipfw: 5000 Allow TCP 0.0.0.0:53 0.0.0.0:0 uid 67 gid 0 pid 1280 bind ipfw: 5000 Allow UDP 203.4.184.222:53 0.0.0.0:0 via ed0 uid 67 gid 0 pid 1280 bind ipfw: 5000 Allow UDP 203.4.184.217:53 0.0.0.0:0 via ppp0 uid 67 gid 0 pid 1280 bind ipfw: 5000 Allow UDP 127.0.0.1:53 0.0.0.0:0 via lo0 uid 67 gid 0 pid 1280 bind ipfw: 5000 Allow UDP 0.0.0.0:53 0.0.0.0:0 uid 67 gid 0 pid 1280 bind Cheers, Julian From owner-freebsd-hackers Mon Jan 6 12:34:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA26119 for hackers-outgoing; Mon, 6 Jan 1997 12:34:45 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA26114 for ; Mon, 6 Jan 1997 12:34:43 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA12384; Mon, 6 Jan 1997 13:25:05 -0700 From: Terry Lambert Message-Id: <199701062025.NAA12384@phaeton.artisoft.com> Subject: Re: make(1) substitution question... To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Mon, 6 Jan 1997 13:25:05 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: <199701020121.LAA14651@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jan 2, 97 11:51:15 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Can anyone suggest a way of making this DWIM without involving the shell? > > FOO= test > BAR= FOO BAR= $(FOO) > > target: > echo ${${BAR}} echo $(BAR) ? Otherwise, you need to invoke "eval" (techincally, you wouldn't be invoking the shell, but the implementation whould actually invoke it anyway...). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 12:37:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA26286 for hackers-outgoing; Mon, 6 Jan 1997 12:37:03 -0800 (PST) Received: from anacreon.sol.net (anacreon.sol.net [206.55.64.116]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA26281 for ; Mon, 6 Jan 1997 12:37:00 -0800 (PST) Received: from solaria.sol.net (solaria.sol.net [206.55.65.75]) by anacreon.sol.net (8.6.12/8.6.12) with ESMTP id OAA07278; Mon, 6 Jan 1997 14:36:52 -0600 Received: from localhost by solaria.sol.net (8.5/8.5) id OAA29610; Mon, 6 Jan 1997 14:36:50 -0600 From: Joe Greco Message-Id: <199701062036.OAA29610@solaria.sol.net> Subject: Re: MMAP Troubles (Joerg?) To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Mon, 6 Jan 97 14:36:48 CST Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG, henrich@crh.cl.msu.edu In-Reply-To: <199701041258.XAA23533@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jan 4, 97 11:28:35 pm X-Mailer: ELM [version 2.4dev PL65] MIME-Version: 1.0 Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Slightly older news (but I suspect still current) was that INN is > faster on FreeBSD _without_ mmap, due to caching etc. Remember that Back when I played with MMAP (2.0-2.1.5R), it did not seem to make a major difference. Given a reasonable news server, I don't think that active update time is going to be the big concern, in any case. You're much more worried about the history and spool access times. > you will want to mount your spool disks async and noatime too. Search > for anything that Joe Greco has posted about news machines; he appears > to know his stuff pretty well. I don't know if it's wise to mount async. I am doing it on my new pet box, newsfeeds.sol.net, and I have seen peaks of 44 articles per second (INN1.5, FreeBSD 2.2C, disks async, PPro200, 192MB RAM) compared to newspump.sol.net's record of 16 (INN1.4UNOFF4, FreeBSD 2.1.5R, disks sync, P133, 256MB RAM). But I am a little paranoid that a crash may not come right back. :-) File deletions are so quick, they blow my socks off. ;-) ... JG From owner-freebsd-hackers Mon Jan 6 12:52:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA27177 for hackers-outgoing; Mon, 6 Jan 1997 12:52:41 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA27169 for ; Mon, 6 Jan 1997 12:52:35 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA16011 for ; Mon, 6 Jan 1997 21:52:32 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA03972 for hackers@FreeBSD.ORG; Mon, 6 Jan 1997 21:52:32 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id VAA04987; Mon, 6 Jan 1997 21:35:40 +0100 (MET) Message-ID: Date: Mon, 6 Jan 1997 21:35:40 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: Any good reason to run portmap on a non NFS'd/RPC'd References: <199701060938.JAA24767@deputy.pavilion.co.uk> <199701061606.KAA26670@solaria.sol.net> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701061606.KAA26670@solaria.sol.net>; from Joe Greco on Jan 6, 1997 10:06:38 -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Joe Greco wrote: > How about a "portmap=AUTO"? > > If set, it enables portmap is YP/NFS/etc are enabled. > > If "NO", it yells during startup that you are broken, if YP/NFS/etc are > enabled. > > If "YES", well, obvious :-) Your message must have been corrupted, can you resend it? (The appended diff for your proposal must have gone lost. :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Jan 6 12:59:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA27673 for hackers-outgoing; Mon, 6 Jan 1997 12:59:56 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA27658 for ; Mon, 6 Jan 1997 12:59:52 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA12457; Mon, 6 Jan 1997 13:48:59 -0700 From: Terry Lambert Message-Id: <199701062048.NAA12457@phaeton.artisoft.com> Subject: Re: New motherboard breaks tape drive To: andreas@klemm.gtn.com (Andreas Klemm) Date: Mon, 6 Jan 1997 13:48:59 -0700 (MST) Cc: jfieber@indiana.edu, hackers@freebsd.org In-Reply-To: from "Andreas Klemm" at Jan 2, 97 04:06:36 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > options BOUNCE_BUFFERS #include support for DMA bounce buffers > > You only need this option when using SCSI DMA controllers like the > AHA 1542B, which only could address 16 MB address space and only in > the case when having more than 16MB of system memory. > > It might be the case, that this bounce buffering brings your system's > performance down. No. The BOUNCE_BUFFERS option is to force the use of bounce buffers even in the case that you don't need bounce buffers. For ISA bus master controllers, the use of bounce buffers is automatic and *can not be turned off* if you have more than 16M of memory. The case where you need bounce buffers, but the machine does not detect the fact is limited to NiCE EISA motherboards with the HiNT chipset, which (in violation of the EISA standard) do not decode the upper address lines for EISA bus master controllers, AND you have more than 16M. Because the HiNT chipset was so terrible, NiCE went under and was sold off several times, so there are several vendors with HiNT chipset systems. As far as I know, the HiNT chipset is only present in a few older EISA or EISA/ISA systems. Typically, you will not need to enable the option, ever. FreeBSD should really auto-detect this problem by: 1) allocate a buffer in physical memory below 16M such that another buffer can be allocated in the physical memory above 16M such that a decode wrap could be detected. Ie: if you have 24M, then you will need to allocate a buffer in the first 8M, and then in the 8M above 16M. 2) allocate the other buffer above 16M. 3) Do a read into the lower buffer from a given disk sector (sector 0 is good) 4) XOR the lower buffer with some value 5) copy the lower buffer to the higher buffer 6) Do a read into the higher buffer from the same disk sector 7) Note whether the upper or lower buffer changes; if the lower buffer changes, then the chipset is broken (ie: it is a HiNT chipset or one of the manufacturers who bought out and relabelled NiCE) 8) Turn on bouncing unconditionally if you have a bogus chipset Note: There are similar, but vastly more complicated, algorithms necessary to detect a bad Cyrix (TI mask) processor, which does not do a cache invalidate/update as a result of bus master DMA modifying data which is cached, and there are similar problems with VLB machines and machines with the Saturn I/Mercury I Intel chipsets, and for 3 or more PCI bus masters for all Mercury/Saturn/Neptune chipsets of any vintage... Another problem is that some VLB cards are detected as if they were EISA cards. EISA will always do the cache update (unless the chipset is bogus... see above), but VLB slots will not generate the cache update request unless the VLB card is in a master slot. So a real detect would seperate these drivers into distinct "VLB" and "EISA" (the case in point are Adaptec VLB controllers that export an EISA identification because they use the same chipset on the card) and would also need to BINVD the crap out of everything after turning off processor specific caches in order to be sure that what's seen is not just a good cache image of bad data (step #7 may show no buffer change at all in that case). Fixing everything in software is possible, but would need a lot of work to detect the difference between a DMA range wrap error, a cache bug, and a cache error. For instance, some processors, like Cyrix, do not honor the non-cacheable bit like they should, so you should turn caching off, or do a BINVD after a DMA has completed. For others, simply marking all bounce buffer buffers as non-cacheable would suffice. To do any of these detects, however, would require some hard entry points into all bus master DMA drivers for use by the detection routines. [ ... ] > But I think BOUNCE_BUFFERS might be the real culprit... BOUNCE_BUFFERS is probably *not* the culprit; it *could* result in a slowdown in *certain* very special circumstances. The ones he described are not them, however. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 13:03:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA27944 for hackers-outgoing; Mon, 6 Jan 1997 13:03:40 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA27939 for ; Mon, 6 Jan 1997 13:03:38 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.7.6/8.7.3) with SMTP id NAA18628; Mon, 6 Jan 1997 13:03:19 -0800 (PST) Date: Mon, 6 Jan 1997 13:03:17 -0800 (PST) From: Jaye Mathisen To: Michael Smith cc: hackers@freebsd.org Subject: Re: pib comments. In-Reply-To: <199701040417.OAA22838@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 4 Jan 1997, Michael Smith wrote: > > I'm losing faith in TCL/TK stuff. Nice idea conceptually, but painfully > > slow. > > I suggest that you push the turbo button on your P6 phallus and > perhaps try talking to the _author_ before you slam his work > publically, or at the very least ask the ports group, who have been You'll note that I didn't slam your work specifically, in fact, I said it was a great concept. You'll also note that it was a comment, and not a statement that "The author is completely braindamaged, and should be taken out and shot". So in a nutshell, relax. Perhaps it is my config, while I find it possible that it is something with Accelerated-X, it seems odd that it only shows up in tk stuff, and nothing else. My frustration with TCL/TK was related to performance in general, not your app. I've tried TKdesk, and it crawls, and zircon runs like a dog as well. The common thread being my machine, and tcl/tk apps. However, I don't see any other performance problems with my box and Motif apps, I get great mpeg frame-rates, everything else works very snappy so I was quick to point the finger at TCL/TK, which may actually be incorrect. From owner-freebsd-hackers Mon Jan 6 13:11:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA28600 for hackers-outgoing; Mon, 6 Jan 1997 13:11:52 -0800 (PST) Received: from deliverator.io.com (deliverator.io.com [199.170.88.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA28592 for ; Mon, 6 Jan 1997 13:11:49 -0800 (PST) Received: from bermuda.io.com (sszabo@bermuda.io.com [199.170.88.7]) by deliverator.io.com (8.8.4/8.8.4) with ESMTP id OAA15346 for ; Mon, 6 Jan 1997 14:22:38 -0600 (CST) Received: from localhost (sszabo@localhost) by bermuda.io.com (8.8.4/8.8.4) with SMTP id OAA11707 for ; Mon, 6 Jan 1997 14:22:36 -0600 (CST) X-Authentication-Warning: bermuda.io.com: sszabo owned process doing -bs Date: Mon, 6 Jan 1997 14:22:36 -0600 (CST) From: Stephan Szabo To: freebsd-hackers@freebsd.org Subject: Question about ypbind Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We have been attempting to install NIS on a FreeBSD 2.1.5R system and have run into a problem with ypbind. When it is run, it dies on a SIGSEGV. Going through gdb a bit gave us the following: Program received signal SIGSEGV, Segmentation fault. rpc_received (dom=0xefbfd538 "\025:\006\b\207\002", raddrp=0xefbfd528, force=0) at ypbind.c:773 773 switch(ypdb->dom_default) { (gdb) bt #0 rpc_received (dom=0xefbfd538 "\025:\006\b\207\002", raddrp=0xefbfd528, force=0) at ypbind.c:773 #1 0x20d1 in handle_children (ypdb=0xa080) at ypbind.c:537 #2 0x1f9d in main (argc=1, argv=0xefbfddc8) at ypbind.c:490 The first parameter to rpc_received seems like random noise, and doesn't match any entry in the ypbindlist, which appears to cause the actual crash. We were wondering if there was a known reason/fix for this, or what the best way to handle this problem would be. Thank you for your time. Stephan Szabo From owner-freebsd-hackers Mon Jan 6 13:15:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA28970 for hackers-outgoing; Mon, 6 Jan 1997 13:15:41 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA28963 for ; Mon, 6 Jan 1997 13:15:39 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id QAA05316; Mon, 6 Jan 1997 16:13:37 -0500 (EST) From: Charles Henrich Message-Id: <199701062113.QAA05316@crh.cl.msu.edu> Subject: Re: MMAP Troubles (Joerg?) To: jgreco@solaria.sol.net (Joe Greco) Date: Mon, 6 Jan 1997 16:13:36 -0500 (EST) Cc: msmith@atrad.adelaide.edu.au, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199701062036.OAA29610@solaria.sol.net> from Joe Greco at "Jan 6, 97 02:36:48 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I don't know if it's wise to mount async. I am doing it on my new pet > box, newsfeeds.sol.net, and I have seen peaks of 44 articles per second > (INN1.5, FreeBSD 2.2C, disks async, PPro200, 192MB RAM) compared to > newspump.sol.net's record of 16 (INN1.4UNOFF4, FreeBSD 2.1.5R, disks > sync, P133, 256MB RAM). But I am a little paranoid that a crash may > not come right back. :-) > > File deletions are so quick, they blow my socks off. I was seeing 4MB/sec deletions during an expire last night.. Expiring took 20 minutes, I was happy :) Granted it wasnt a full newsspool, only about 6GB, but still :) -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Mon Jan 6 13:18:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA29179 for hackers-outgoing; Mon, 6 Jan 1997 13:18:48 -0800 (PST) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA29174 for ; Mon, 6 Jan 1997 13:18:42 -0800 (PST) Received: by iafnl.es.iaf.nl with UUCP id AA31946 (5.67b/IDA-1.5 for hackers@freebsd.org); Mon, 6 Jan 1997 22:16:27 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.7.5/8.6.12) id UAA00776; Mon, 6 Jan 1997 20:38:45 +0100 (MET) From: Wilko Bulte Message-Id: <199701061938.UAA00776@yedi.iaf.nl> Subject: Re: Year 2000 time change(Format support) To: bde@zeta.org.au (Bruce Evans) Date: Mon, 6 Jan 1997 20:38:44 +0100 (MET) Cc: babkin@hq.icb.chel.su, mbarkah@hemi.com, hackers@freebsd.org, seanb012@sunbeach.net, tom@sdf.com In-Reply-To: <199701060652.RAA32628@godzilla.zeta.org.au> from "Bruce Evans" at Jan 6, 97 05:52:43 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote... > > >> How about the year 2038 problem, then ? =-) I believe time_t > >> overflows then. > > > >I believe there will be no 32-bit computers anymore then :-) > > I believe there are no 31-bit computers ever :-). > > Bruce But there were 36 bits ones out there ;-) Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-hackers Mon Jan 6 13:19:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA29245 for hackers-outgoing; Mon, 6 Jan 1997 13:19:23 -0800 (PST) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA29231 for ; Mon, 6 Jan 1997 13:19:20 -0800 (PST) Received: from misery.sdf.com [204.244.213.33] by misery.sdf.com with smtp (Exim 1.59 #1) id 0vhMSv-0001JN-00; Mon, 6 Jan 1997 13:20:17 -0800 Date: Mon, 6 Jan 1997 13:20:17 -0800 (PST) From: Tom Samplonius To: hackers@freebsd.org Subject: ncr 810 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk How many concurrent commands can the ncr drive + a NCR 810 controller handle? I know the ahc driver can handle 255 active commands, but only with scb paging turned on. Tom From owner-freebsd-hackers Mon Jan 6 13:23:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA29514 for hackers-outgoing; Mon, 6 Jan 1997 13:23:07 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA29506 for ; Mon, 6 Jan 1997 13:23:01 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA16799; Mon, 6 Jan 1997 22:22:54 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA04462; Mon, 6 Jan 1997 22:22:53 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id VAA05079; Mon, 6 Jan 1997 21:58:53 +0100 (MET) Message-ID: Date: Mon, 6 Jan 1997 21:58:53 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: fisco.dev@sul.com.br (Paulo Cesar Pereira de Andrade) Cc: freebsd-hackers@freebsd.org (FreeBSD hackers) Subject: Re: sig-11 plague References: <32D0F453.2781E494@sul.com.br> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <32D0F453.2781E494@sul.com.br>; from Paulo Cesar Pereira de Andrade on Jan 6, 1997 12:47:15 +0000 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Paulo Cesar Pereira de Andrade wrote: (sig 11 plague) > I resolved the problem in the BIOS setup, i disabled the external > cache, and now cc1 does not fail. ... > I have now a doubt: is this a feature of pci or is a todo in > FreeBSD (perhaps a done, since im using 2.1.0) or is i that have a not > good hardware or another thing ? It's bad hardware, very clearly in your case (since turning off the external cache worked). You don't describe your disk controller, but if it's a SCSI busmaster controller, it might help to enable the external cache but operate it in `write-through' mode. This doesn't lose much performance (unlike turning it off totally). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Jan 6 13:36:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA00724 for hackers-outgoing; Mon, 6 Jan 1997 13:36:25 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA00715 for ; Mon, 6 Jan 1997 13:36:21 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA12572; Mon, 6 Jan 1997 14:26:58 -0700 From: Terry Lambert Message-Id: <199701062126.OAA12572@phaeton.artisoft.com> Subject: Re: divert code not thread/smp compatible To: proff@iq.org (Julian Assange) Date: Mon, 6 Jan 1997 14:26:58 -0700 (MST) Cc: archie@whistle.com, hackers@FreeBSD.ORG In-Reply-To: <199701022007.HAA12208@profane.iq.org> from "Julian Assange" at Jan 3, 97 07:07:31 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Well, I looked at threading/locking issues in netinet/* generally and > have come to view the chances of seeing more than one thread in anything > close to the bsd44 inet code is zero. The whole thing is locked by > a few fat, totally non-granular splnet()s. This is true for one CPU. However, both CPU's do not need to be at the same SPL level. Neither do both CPU's have to sequentially process interrupts through a single queue in symmetric I/O mode. Locking needs to be on data object, not on subsystem entry... though during push-down (the process of increasing the granularity of kernel concurrency for multiple processors) if the interfaces are sufficiently abstract (ie: call down, no violation of layering), then a single global entrancy lock *could* be used per subsystem. Actually, this was my take on the "correct" way to do the pushdown through the system call trap layer for FS's. Interrupts (like network interrupts) are another way of entering the kernel, as are exceptions (real or page faults). If you look at each of these as seperate mechanisms for entering kernel space, then you can lock them (assuming a hierarchical locking system to prevent starvation/deadly-embrace deadlocks using computation of transitive closure over the hierarchy for deadlock avoidance) as if they were seperate things. As far as handling the code that runs at int time, the most effective method is to virtualize as much of the interrupt as you can so that long delay operations block kernel threads instead of processors (leaving CPU's as schedulable resources which can be applied against ready-to-run lists). Thus you would have a bottom end handler that would get the bus conflict out of the way as quickly as possible, and then queue the rest of the operation to be completed *not* in interrupt mode. Both NT and SVR4 ES/MP do this. Topologically, there is no difference between SMP and kernel threading issues in this regard... the only exception is inter-CPU cache synchronization events on locking (and non-synchronizing versions of this type of locking are already being discussed). > While we are on the subjects of locking, I notice a distinct lack > of atomic test-and-set or test-and-inc instructions for struct > usage counts (which are instead relying on non-atomic C). Is there > such an existing kernel macro that does: > > int > tas(slock_t *m) > { > slock_t res; > __asm__("xchgb %0,%1":"=q" (res),"=m" (*m):"0" (0x1)); > return(res); > } There is, but it's unreliable in an SMP case, and has a potential race in a DMA case within a concurrency (top/bottom interrupt handler) optimized UP multithreaded kernel... mostly because of the lock area being potentially paged if it doesn't apply to a locked-in-core subsystem. Actually, it's not the locks themselves, but the cache lines you have to worry about. In general, the P5 and above will update their instruction and data cache internally, but this has to work for 386's and 486's, too... (Van Gilluwe, _The Undocumented PC_, "determining L1 and instruction cache depth"). An IPI based mechanism, which (as a side effect of the MP spec and vagries of IPI delivery guarantess because Intel was not specific enough about implementation) lineralizes mutex (semaphore) access has been discussed on the SMP list (and is probably in the archives for that list). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 13:39:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA01048 for hackers-outgoing; Mon, 6 Jan 1997 13:39:22 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA01033 for ; Mon, 6 Jan 1997 13:39:14 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA12582; Mon, 6 Jan 1997 14:29:49 -0700 From: Terry Lambert Message-Id: <199701062129.OAA12582@phaeton.artisoft.com> Subject: Re: ft < 50kb/s ?? To: mark@putte.seeware.DIALix.oz.au (Mark Hannon) Date: Mon, 6 Jan 1997 14:29:49 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Mark Hannon" at Jan 2, 97 08:28:59 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have been a user of the ft tape driver for a number of years. Over > time I have swapped my tape drive between different motherboards and > controllers. The drive has served me well (especially with the lft > utility instead of the standard ft driver) in general, however in > the current configuration it is dead slow - It just took me 12 hours > to back up 200m of data, according to the manufacturers notes it > should be able to do 1Mbit/second, which is around 30minutes. > > What can I be doing wrong? I have moved the tape driver over to a > 486-100 motherboard with onboard floppy-disk controller. > > I have now also moved the drive over to another machine and floppy > controller, exactly the same results. I have yet to check the > drives performance under DOS. It is possible that the other machines has non-NS floppy controller chips. A number of these have FIFO's and can be significantly faster with tapes as a result (even though we can't safely detect the things). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 13:39:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA01062 for hackers-outgoing; Mon, 6 Jan 1997 13:39:23 -0800 (PST) Received: from cold.org (cold.org [206.81.134.103]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA01037; Mon, 6 Jan 1997 13:39:17 -0800 (PST) Received: from localhost (brandon@localhost) by cold.org (8.8.3/8.8.3) with SMTP id OAA23722; Mon, 6 Jan 1997 14:39:20 -0700 (MST) Date: Mon, 6 Jan 1997 14:39:20 -0700 (MST) From: Brandon Gillespie To: security@freebsd.org, hackers@freebsd.org Subject: FreeBSD as a cleanwall Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does anybody have a configuration for packet filtering through a FreeBSD router to run a cleanwall? Basically to keep all addresses of a specific IP set (say a class C) on the right sides. I.e. only set addresses of that set leave the network and don't allow any addresses of that set onto the network? I'm mulling through the docs now, but figured to look here for any possible pointers, as this seems like it would be a common enough operation.. -Brandon Gillespie From owner-freebsd-hackers Mon Jan 6 13:52:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA02386 for hackers-outgoing; Mon, 6 Jan 1997 13:52:49 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA02380 for ; Mon, 6 Jan 1997 13:52:46 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA17508; Mon, 6 Jan 1997 22:51:25 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA04864; Mon, 6 Jan 1997 22:51:24 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id WAA05222; Mon, 6 Jan 1997 22:26:21 +0100 (MET) Message-ID: Date: Mon, 6 Jan 1997 22:26:21 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: angio@aros.net (Dave Andersen) Cc: hackers@freebsd.org Subject: Re: NFS sillyrenamedir References: <199701061742.KAA04137@terra.aros.net> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701061742.KAA04137@terra.aros.net>; from Dave Andersen on Jan 6, 1997 10:42:34 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Dave Andersen wrote: > #ifndef DIAGNOSTIC > if (vp->v_type == VDIR) > panic("nfs: sillyrename dir"); > #endif > > I'm not very familiar with the FS code in FreeBSD. Is there > an easy fix for this ... revision 1.39 date: 1996/12/31 07:10:19; author: wpaul; state: Exp; lines: +3 -2 Fix (properly, I hope) 'panic: sillyrename dir' crash that can happen if you do: % cd /nfsdir % mkdir -p foo/foo % mv foo/foo . See, it's already done. :) Send the beer to Bill Paul... -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Jan 6 13:53:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA02410 for hackers-outgoing; Mon, 6 Jan 1997 13:53:02 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA02365 for ; Mon, 6 Jan 1997 13:52:29 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA17522; Mon, 6 Jan 1997 22:51:32 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA04873; Mon, 6 Jan 1997 22:51:32 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id WAA05259; Mon, 6 Jan 1997 22:36:43 +0100 (MET) Message-ID: Date: Mon, 6 Jan 1997 22:36:43 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: SimsS@IBM.Net Cc: Hackers@freebsd.org (Hackers) Subject: Re: ed0 boot [p]roms References: <199701061943.TAA84776@smtp-gw01.ny.us.ibm.net> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701061943.TAA84776@smtp-gw01.ny.us.ibm.net>; from Steve Sims on Jan 6, 1997 14:40:42 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Steve Sims wrote: > I figure that with all these el-cheapo NE-2000 clones floating around, > somebody ought to have an idea on how to burn or where to buy an appropriate > bootp/tftp-able ROM for 'em. cd /sys/i386/boot/netboot vi Makefile # there are a few options make (&& find someone to burn you the EPROM) My scratchbox can do netbooting fine, with a WD8003 card. There's also a handbook section about diskless booting, i think it also covers the server side. It was fairly painless for me to get the environment running from that description. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Jan 6 13:54:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA02513 for hackers-outgoing; Mon, 6 Jan 1997 13:54:04 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA02504 for ; Mon, 6 Jan 1997 13:53:55 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA12639; Mon, 6 Jan 1997 14:44:16 -0700 From: Terry Lambert Message-Id: <199701062144.OAA12639@phaeton.artisoft.com> Subject: Re: New Networking framework for BSD To: dennis@etinc.com (dennis) Date: Mon, 6 Jan 1997 14:44:16 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: <3.0.32.19970105130424.0068f454@etinc.com> from "dennis" at Jan 5, 97 01:04:26 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> Darren, see my mail drirectly to you... > >> you appear to have commented without reading the doc yet.. > >> I'm not trying to replace anything. Just make a framework for such > >> services as frame relay and ATM, at the LINK level. > > > >Yes, I read it briefly first but wrote that with an empty mind... > > > >Looks like the claytons STREAMS. How is it different to STREAMS (by > design) ? > > Yeah really. STREAMS is a great academic product...but a monster in real > world implementation. Not to mention a pig. Anyone care to guess why the > 'BSD unices blow the doors off system V performance-wise? Because "runstreams" is only called at system call entry, exit, and a couple other stregic times, and it is required to be called for every layer traversal in getmsg/putmsg across a stack boundry. In experimental implementations where the stack was run to completion at interrupt level, streams was no more bulky or slow than the BSD equivalents. In addition, a number of experiments have been done to implement "multiheaded stacks"... that is, a single monolithic stack that exports heads for ICMP, IP, UDP, and TCP, such that multiple traversals are not required following the initial putmsg at interrupt time. The problem with streams is when it is able to run, and the granularity at which it runs. When you look at streams implementations, I would suggest you look at the IBM AIX adaption of the Mentat Streams system. They were able to resolve the latency issues (which are the issues to which you are referring, in a sideways manner) by running the streams implementation as a kernel thread, such that stack data runs to completion, without the peristaltic slowdowns of running to copletion at interrupt level, and without the Karnot map reduction required for the multiheaded implementation. Only in kernels which are not thread reeentrant, for which kernel threading is unavailable, or which use high granularity locking on CPU reentrancy (effectively ASMP for interrupt and exception handling) have problems with streams latency... and that's not the direction FreeBSD is headed in (apparently, from reading the SMP list). > An issue to consider is that you dont need a new framework...virtual > interfaces solve the problem without changing anything... I really disagree with this... virtual interfaces cross protection domains, and that's a problem... as much of a problem as moving the network stack to user space (as some have suggested in research projects trying to address these issues). The advantage of the stremas (or xkernel framework, from the University of Arizona up the street from me) is that they do *not* cross protection domains. > with a new > framework you are likely to break compatibility with routing daemons > (like gated)...which would render the effort worthless in the big picture. I agree with this; however, since I haven't read Julian's paper yet, I will reserve comment; for all I know, it looks so much like streams I will wonder what I am complaining about if I say too much. 8-). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 13:55:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA02619 for hackers-outgoing; Mon, 6 Jan 1997 13:55:02 -0800 (PST) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA02601 for ; Mon, 6 Jan 1997 13:54:53 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hydrogen.nike.efn.org (8.8.4/8.8.4) with SMTP id NAA03638; Mon, 6 Jan 1997 13:54:29 -0800 (PST) Date: Mon, 6 Jan 1997 13:54:26 -0800 (PST) From: John-Mark Gurney Reply-To: John-Mark Gurney To: Steve Sims cc: Hackers Subject: Re: ed0 boot [p]roms In-Reply-To: <199701061943.TAA84776@smtp-gw01.ny.us.ibm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 6 Jan 1997, Steve Sims wrote: > I figure that with all these el-cheapo NE-2000 clones floating around, > somebody ought to have an idea on how to burn or where to buy an appropriate > bootp/tftp-able ROM for 'em. well.. first check out the handbook in section 13.3... diskless operation... that should get you started.. then look at /usr/src/sys/i386/boot/netboot for rom images you can burn... I have yet to burn a rom.. but I am using a com version of the ns8390 and it wors great... hope this helps... ttyl.. John-Mark gurney_j@efn.org http://resnet.uoregon.edu/~gurney_j/ Modem/FAX: (541) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix) From owner-freebsd-hackers Mon Jan 6 14:04:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA03247 for hackers-outgoing; Mon, 6 Jan 1997 14:04:24 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA03238 for ; Mon, 6 Jan 1997 14:04:20 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA12695; Mon, 6 Jan 1997 14:54:12 -0700 From: Terry Lambert Message-Id: <199701062154.OAA12695@phaeton.artisoft.com> Subject: Re: more than 32 disks? To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Mon, 6 Jan 1997 14:54:12 -0700 (MST) Cc: dg@root.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199701030439.XAA21021@crh.cl.msu.edu> from "Charles Henrich" at Jan 2, 97 11:39:32 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > with an sd3 problem yet. :-) It looks like there are only 5 bits for the > > unit number. This means that one will have to make driver changes to go > > beyond 32 units. :-( > > *sigh* I absolutely hate fixed fields :( *grumble*. So whats the generic > solution besides encoding data into the minor number? Encode a table offset > into the minor number and make the table dynamic? DEVFS. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 14:09:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA03643 for hackers-outgoing; Mon, 6 Jan 1997 14:09:55 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA03638 for ; Mon, 6 Jan 1997 14:09:53 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA12685; Mon, 6 Jan 1997 14:52:52 -0700 From: Terry Lambert Message-Id: <199701062152.OAA12685@phaeton.artisoft.com> Subject: Re: file locking / firewalling based on uid/gid To: proff@iq.org (Julian Assange) Date: Mon, 6 Jan 1997 14:52:52 -0700 (MST) Cc: avalon@coombs.anu.edu.au, hackers@FreeBSD.org In-Reply-To: <199701022334.KAA16149@profane.iq.org> from "Julian Assange" at Jan 3, 97 10:34:34 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > sockfs anyone ? > > I'm all for the everything-is-a-file and the file-system name space > philosophy of Unix, which has unfortunately been badly corroded over > the years. See VSTa or plan9 for how file system name spaced should > be managed. Bleah. 8-p String processing in the kernel is a dumb idea... especially if the only reason for doing it is because you can agree to standardize words, but can't agree to standardize numeric indices for words. I would rather not carry all of those strings around, thank you. Maybe we could do something idiotic, like MD5 the words as part of the compile process, leaving a 32 bit value unlikely to repeat based different words, then MD5 the words on the way in and pass around the MD5 values instead. Then for value parameters, we could reinvent DCL CLD's. Bletch. 8~(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 14:11:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA03764 for hackers-outgoing; Mon, 6 Jan 1997 14:11:30 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA03744 for ; Mon, 6 Jan 1997 14:11:10 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA12717; Mon, 6 Jan 1997 15:01:30 -0700 From: Terry Lambert Message-Id: <199701062201.PAA12717@phaeton.artisoft.com> Subject: Re: more than 32 disks? To: peter@taronga.com (Peter da Silva) Date: Mon, 6 Jan 1997 15:01:30 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: <199701031302.HAA07824@bonkers.taronga.com> from "Peter da Silva" at Jan 3, 97 07:02:49 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> with an sd3 problem yet. :-) It looks like there are only 5 bits for the > >> unit number. This means that one will have to make driver changes to go > >> beyond 32 units. :-( > > >*sigh* I absolutely hate fixed fields :( *grumble*. So whats the generic > >solution besides encoding data into the minor number? Encode a table offset > >into the minor number and make the table dynamic? > > Use a wider minor number, a wider portion of the minor number for unit, > decrease the number of bits used for things other than unit, use multiple > major numbers, or use another encoding than major/minor numbers for device > files (via devfs). > > Some aspects of the System V kernel build model, where the major numbers > can be easily reassigned and the same file is used to drive the building > of the kernel and the files in /dev, are really handy. Of course devfs > makes it a point moot... The major number is the index in the cdevsw/bdevsw; the major number should go away (though devfs, unfortunately, carrys one around). It should die because cdevsw/bdevsw should die. The minor number is a unit index for the device driver; the minor number should go away, since the instance records which the device operates against should be referenced via the data pointer in the vnode for the device (which itself references a common driver data structure (though devfs, unfortunately, carrys around minor numbers, too). It should die because the unit records are context which can be provided by an allocated instead of a statically indexed unit context value for a given driver. So the point is not only moot, the context in which the point was being made is also moot (or should be... screw backward compatability with bogus old drivers -- update them to register with devfs if they are useful). Same argument applies to having permanent attributes set by chmod/chgrp/chown by reflecting static data into a real file system anywhere... if you want to change the values, do it in the config file when you define the device in the first place, and have it built into the registration record for the device instead of kludging it up. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 14:13:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA03977 for hackers-outgoing; Mon, 6 Jan 1997 14:13:34 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA03963 for ; Mon, 6 Jan 1997 14:13:29 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA12726; Mon, 6 Jan 1997 15:03:52 -0700 From: Terry Lambert Message-Id: <199701062203.PAA12726@phaeton.artisoft.com> Subject: Re: more than 32 disks? To: dufault@hda.com (Peter Dufault) Date: Mon, 6 Jan 1997 15:03:52 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199701031410.JAA24455@hda.hda.com> from "Peter Dufault" at Jan 3, 97 09:10:43 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > A related question: are there issues (regarding booting, etc) with > removing all partition/slice/ file system code from the different > device drivers and having a single "dk" device that gets wired to > the other block devices? Essentially have the base device be a > trusting client of a dk device that handles all that stuff. I have suggested a hierarchy of devices, based on device type, instance, and partitioning in the past. There is no inhernet reason (except unwarranted love of the past) that this could not be implemented. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 14:21:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA04559 for hackers-outgoing; Mon, 6 Jan 1997 14:21:12 -0800 (PST) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA04553 for ; Mon, 6 Jan 1997 14:21:05 -0800 (PST) Received: from misery.sdf.com [204.244.213.33] by misery.sdf.com with smtp (Exim 1.59 #1) id 0vhNP6-0001Ud-00; Mon, 6 Jan 1997 14:20:25 -0800 Date: Mon, 6 Jan 1997 14:20:24 -0800 (PST) From: Tom Samplonius To: Stephan Szabo cc: freebsd-hackers@freebsd.org Subject: Re: Question about ypbind In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 6 Jan 1997, Stephan Szabo wrote: > > We have been attempting to install NIS on a FreeBSD 2.1.5R system > and have run into a problem with ypbind. When it is run, it dies on a > SIGSEGV. Going through gdb a bit gave us the following: > Program received signal SIGSEGV, Segmentation fault. > > rpc_received (dom=0xefbfd538 "\025:\006\b\207\002", raddrp=0xefbfd528, > force=0) at ypbind.c:773 > 773 switch(ypdb->dom_default) { > (gdb) bt > #0 rpc_received (dom=0xefbfd538 "\025:\006\b\207\002", > raddrp=0xefbfd528, force=0) at ypbind.c:773 > #1 0x20d1 in handle_children (ypdb=0xa080) at ypbind.c:537 > #2 0x1f9d in main (argc=1, argv=0xefbfddc8) at ypbind.c:490 > > > The first parameter to rpc_received seems like random noise, and doesn't > match any entry in the ypbindlist, which appears to cause the actual > crash. > We were wondering if there was a known reason/fix for this, or what the > best way to handle this problem would be. > > Thank you for your time. > > Stephan Szabo > > > > Works fine for me. What params are you running ypbind with? What kind of server is ypbind binding too (or trying to bind to)? Tom From owner-freebsd-hackers Mon Jan 6 14:21:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA04600 for hackers-outgoing; Mon, 6 Jan 1997 14:21:39 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA04589 for ; Mon, 6 Jan 1997 14:21:35 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA12748; Mon, 6 Jan 1997 15:11:56 -0700 From: Terry Lambert Message-Id: <199701062211.PAA12748@phaeton.artisoft.com> Subject: Re: file locking / firewalling based on uid/gid To: dennis@etinc.com (dennis) Date: Mon, 6 Jan 1997 15:11:56 -0700 (MST) Cc: avalon@coombs.anu.edu.au, hackers@freebsd.org In-Reply-To: <3.0.32.19970105125150.00687428@etinc.com> from "dennis" at Jan 5, 97 12:51:52 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >(To me, filtering based on UID implies you're doing things at a higher > > level than normal packet filtering and should be a separate beast rather > > than coming up with kludges to extend ipfw. Heck, there are many more > > and different checks you can make, for a start...). > > I agree. It seems that firewalling and "authentication" are getting > entwined... > which is not a "bad" thing as long as there is no penalty to pay by one or > the other. We've recently combined our bandwidth management, queue > prioritization and filtering functons, but made it a single-pass function to > eliminate the performance penalty. We must seperate credential instances from process group instances and attach them to session instances instead. Each credential for a given machine can have only a single session instance, with a potential of N process group instances sharing a pointer to the session instance. A setuid/setgid operation would establish a new session instance (if a session for the new credential were not present on the system) and decrement the reference count for the previous credential. When the reference count gose to 0, the session is destroyed. We need session instanced to implement "password caches" for non-BSD originated credentials associated with an identity instanced by a session. For instance, for use in NetWare or SMB file systems. We have the potential for "auto" session management, with a session manager registration mechanism for a given process group, to allow for credential query by the kernel if a mechanism for a covert channel to the user exists (ie: ask for the user's SMB password using an X-based dialog for a process group running under XDM, etc.). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 14:26:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA04992 for hackers-outgoing; Mon, 6 Jan 1997 14:26:39 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA04986 for ; Mon, 6 Jan 1997 14:26:37 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.7.6/8.7.3) with SMTP id OAA29602 for ; Mon, 6 Jan 1997 14:26:30 -0800 (PST) Date: Mon, 6 Jan 1997 14:26:28 -0800 (PST) From: Jaye Mathisen To: hackers@freebsd.org Subject: noatime, one more time, the last time. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk # uname -a FreeBSD news.cdsnet.net 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Mon Dec 30 10:32:21 PST 1996 root@news.cdsnet.net:/usr/src/sys/compile/NEWS i386 # mount -p /dev/sd0a / ufs rw 1 1 /dev/sd0s1f /usr ufs rw 1 1 procfs /proc procfs rw 0 0 /dev/ccd0c /news ufs rw,nosuid 1 1 # mount -o noatime -u /news # mount -p /dev/sd0a / ufs rw 1 1 /dev/sd0s1f /usr ufs rw 1 1 procfs /proc procfs rw 0 0 /dev/ccd0c /news ufs rw 1 1 So WTF did the noatime go? I see people all the time talking about using async (which works), and noatime on their newsservers, but they must be using a different reality than me, because noatime never seems to show up. Entirely possible that it's actually doing it, and the mount -p just can't display it, but I'd sure be curious. From owner-freebsd-hackers Mon Jan 6 14:32:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA05504 for hackers-outgoing; Mon, 6 Jan 1997 14:32:28 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA05497 for ; Mon, 6 Jan 1997 14:32:24 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA12770; Mon, 6 Jan 1997 15:23:19 -0700 From: Terry Lambert Message-Id: <199701062223.PAA12770@phaeton.artisoft.com> Subject: Re: device driver initialization To: julian@whistle.com (Julian Elischer) Date: Mon, 6 Jan 1997 15:23:19 -0700 (MST) Cc: erich@lodgenet.com, hackers@freebsd.org In-Reply-To: <32CD529D.167EB0E7@whistle.com> from "Julian Elischer" at Jan 3, 97 10:40:29 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > It looks like most of the ISA drivers now days have a frag like: > > > > SYSINIT(foo,SI_SUB_DRIVERS,SI_ORDER_MIDDLE+CDEV_MAJOR,foo_drvinit,NULL) [ ... ] > > Is there any reason that this can't be absorbed in the attach function, > > somewhere around where the devfs stuff is done? What's the reason for > > adding yet another entry point during re-boot. Isn't probe/attach enough? > > The addition of a devsw entry is done ONCE PER DRIVER > > the probe/attach is done ONCE PER INSTANCE > > so the usages are slightly different. > > other than that, yes it could be done.... > remember also that the eventual aim is to make drivers LKMable > in which case the SYSINIT part would be done by the LKM installation. > > It was easier to add this to every driver in a 'boilerplate' manner > (in fact I used a combination of scripts and manual editing > to add it), than to add more specialist code to each attach routine.. In addition, it is likely that a future version of the symbol agregation code for LKM's will seperate preagregated data from post-agregated data in the kernel following the link. To put this in English: o You have an object module for a driver o You link it statically, it's a static driver o You load it as an LKM, it's an LKM driver o The object code is identical in both cases This would let third parties distribute boot-critical drivers for various controllers. For instance, some poor schuck could sign NDA with Adaptec and supply a binary-only 3940 RAID-II driver so that the rest of us didn't have to sign NDA or have source to link his code in. If the 3940 was our boot device, we could build a kernel with it preloaded (assuming we don't load all our disk drivers as LKM's using VM86-based INT 13 drivers for boot by that time anyway). Same issues apply to ethernet drivers, and so on, which might want to be statically linked into the default kernel, but dynamically loaded by netboot (for example). In effect, we want to destroy the distinction between LKM's and regular drivers. For weenies who need that "extra burst of speed" that you supposedly get with non-PIC'ed objects, they can recompile from sources. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 14:45:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA06437 for hackers-outgoing; Mon, 6 Jan 1997 14:45:00 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA06427 for ; Mon, 6 Jan 1997 14:44:50 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA12791; Mon, 6 Jan 1997 15:35:13 -0700 From: Terry Lambert Message-Id: <199701062235.PAA12791@phaeton.artisoft.com> Subject: Re: MMAP Troubles (Joerg?) To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 6 Jan 1997 15:35:12 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG, henrich@crh.cl.msu.edu In-Reply-To: from "J Wunsch" at Jan 4, 97 11:43:34 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I have an oppourtunity for the MMAP person (Appears to be Joerg by > > the .c, but cant tell for sure :) > > Certainly not me, rather John Dyson. But doesn't matter. > > > Anyway, I have a big beefy pentium pro system here for use as news > > that im going to roll out in a few weeks. INN w/ MMAP causes the > > NULL trashed active file, interested in working on the problem with > > a system at your beck and call? > > IIRC, the last word on INN w/ mmap() was that INN uses mmap() against > the specs in that it tries to shorten (or extend) the file while it's > being mmap()'ed. This only incidentally works on SysV's. > > All this is hearsay, so maybe John or somebody else will tell you more > exactly. Rather, it "doen't fail on non-unified cache machines"... basically because a fault causes a copy (remember bmap()?) and the backing store for the mapped region is one type of cache and the backing store for the vnode is another... It "fails" on FreeBSD because when the file is extended, a partial page is generated, but since the mapping can only go in jumps of full pages, the difference between the previous end of file and the next page boundry is now screwed beyond recognition. This is especially the case if it was using a frag for the last partial page (the use of an 8 bit 512 byte bitmap for partial pages has been discussed; however, this is not a generic soloution; for instance, a 68040 machine with an 8k page size and a 512 byte disk block size would show the errors again when a 512k on an odd 1K boundry were added to the mappable region). Part of the "fix" is to provide a mechanism for device/offset instead of vnode/offset caching, then use the device/offset for mmap instead of referencing the buffers out of the vnode. Alternately, the extention operation must change the mapping, expanding the in core buffer from the prvious fragmentary validity to the page boundry. Ideally, we could pass a "-1" or "0" or som othe magic number in to indicate that the mapping should be dynamically expanded, if possible. Of course INN doesn't use it this way... This has really been discussed to death... INN's assumptions are invalid; for historical compatability, BSD should probably validate the assumptions by going through the extra motions on a file extend, but it currently does not do so. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 14:48:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA06689 for hackers-outgoing; Mon, 6 Jan 1997 14:48:11 -0800 (PST) Received: from antares.aero.org (antares.aero.org [130.221.192.46]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA06680; Mon, 6 Jan 1997 14:48:08 -0800 (PST) Received: from anpiel.aero.org (anpiel.aero.org [130.221.196.66]) by antares.aero.org (8.8.4/8.7.3) with SMTP id OAA07915; Mon, 6 Jan 1997 14:47:34 -0800 (PST) Message-Id: <199701062247.OAA07915@antares.aero.org> To: "Jonathan M. Bresler" Cc: obrien@antares.aero.org (Mike O'Brien), julian@whistle.com, hackers@freefall.freebsd.org, chat@freefall.freebsd.org Subject: Re: Usenix FreeBSD BoF when? In-Reply-To: Your message of "Sun, 05 Jan 1997 05:31:41 PST." <199701051331.FAA29361@freefall.freebsd.org> Date: Mon, 06 Jan 1997 14:47:24 -0800 From: "Mike O'Brien" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > thanks, will we be see you at usenix? Yep, I'll be there from Tuesday evening on. From owner-freebsd-hackers Mon Jan 6 14:51:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA06970 for hackers-outgoing; Mon, 6 Jan 1997 14:51:33 -0800 (PST) Received: from haywire.DIALix.COM (news@haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA06964 for ; Mon, 6 Jan 1997 14:51:27 -0800 (PST) Received: (from news@localhost) by haywire.DIALix.COM (8.8.4/8.8.2) id GAA11814 for freebsd-hackers@freebsd.org; Tue, 7 Jan 1997 06:51:14 +0800 (WST) X-Authentication-Warning: haywire.DIALix.COM: news set sender to usenet-request@haywire.dialix.com using -f Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-hackers@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-hackers@freebsd.org Date: 6 Jan 1997 22:51:12 GMT From: peter@spinner.DIALix.COM (Peter Wemm) Message-ID: <5arvl0$kov$1@haywire.DIALix.COM> Organization: DIALix Services, Perth, Australia. References: <199612251512.HAA00997@squirrel.tgsoft.com> Subject: Re: cvsup change Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <59uthp$c7d@austin.polstra.com>, jdp@polstra.com (John Polstra) writes: > I'm sorry for all the hassle. I'm going to think long and hard before > making this kind of change to the collections again. Hmm ... maybe I > could trick Peter into doing it next time ... ;-) Hmm........ :-) > John Cheers, -Peter From owner-freebsd-hackers Mon Jan 6 14:53:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA07119 for hackers-outgoing; Mon, 6 Jan 1997 14:53:35 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA07112 for ; Mon, 6 Jan 1997 14:53:29 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA12827; Mon, 6 Jan 1997 15:43:21 -0700 From: Terry Lambert Message-Id: <199701062243.PAA12827@phaeton.artisoft.com> Subject: Re: more than 32 disks? To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Mon, 6 Jan 1997 15:43:20 -0700 (MST) Cc: dg@root.com, freebsd-hackers@freebsd.org In-Reply-To: <199701052032.PAA03705@crh.cl.msu.edu> from "Charles Henrich" at Jan 5, 97 03:32:35 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > unit number. This means that one will have to make driver changes to go > > beyond 32 units. :-( > > I noticed this pop up in relation to CD changers as well. I have a suggestion, > perhaps I'll even get a moment to write it (assuming people think this is a > good idea). During boot phase when DEVFS is probing around making devices, > change the format of the minor number to just be 11 bits for type, and then 21 > bits as an offset into a dynamically built kernel table (4 bytes/entry). This > gives us 2097152 different device possibilities.. Still a limit (I hate limits) > but far better than what we have today! Get rid of major and minor numbers entirely. They are unnecessary. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 14:54:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA07217 for hackers-outgoing; Mon, 6 Jan 1997 14:54:03 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA07201 for ; Mon, 6 Jan 1997 14:53:58 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA12818; Mon, 6 Jan 1997 15:41:45 -0700 From: Terry Lambert Message-Id: <199701062241.PAA12818@phaeton.artisoft.com> Subject: Re: Year 2000 time change(Format support) To: babkin@hq.icb.chel.su (Serge A. Babkin) Date: Mon, 6 Jan 1997 15:41:45 -0700 (MST) Cc: mbarkah@hemi.com, tom@sdf.com, seanb012@sunbeach.net, hackers@freebsd.org In-Reply-To: <199701060556.KAA08968@hq.icb.chel.su> from "Serge A. Babkin" at Jan 6, 97 10:56:35 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > How about the year 2038 problem, then ? =-) I believe time_t > > overflows then. > > I believe there will be no 32-bit computers anymore then :-) But all the 64 and 128 bit computers will still have to support V86 for Microsoft OS's for people who want to run copies of "Great Plains Accounting" dating from March of 1987... Luckily, we don't implement Microsoft OS's... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 14:54:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA07248 for hackers-outgoing; Mon, 6 Jan 1997 14:54:09 -0800 (PST) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA07235 for ; Mon, 6 Jan 1997 14:54:07 -0800 (PST) Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.6.12/8.6.9) with SMTP id RAA27893; Mon, 6 Jan 1997 17:57:43 -0500 Message-Id: <3.0.32.19970106175249.00a7c100@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 06 Jan 1997 17:52:51 -0500 To: Terry Lambert From: dennis Subject: Re: New Networking framework for BSD Cc: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk T. Lambert writes... >> An issue to consider is that you dont need a new framework...virtual >> interfaces solve the problem without changing anything... > >I really disagree with this... virtual interfaces cross protection >domains, and that's a problem... as much of a problem as moving the >network stack to user space (as some have suggested in research >projects trying to address these issues). I dont know what you're talking about here...perhaps your concept of virtual interfaces is not the same as our implementation. There are no such problems, or should there be, if done properly. dennis From owner-freebsd-hackers Mon Jan 6 14:57:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA07584 for hackers-outgoing; Mon, 6 Jan 1997 14:57:20 -0800 (PST) Received: from offensive.communica.com.au (offensive-eth1.adl.communica.com.au [192.82.222.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA07575 for ; Mon, 6 Jan 1997 14:57:14 -0800 (PST) Received: from communica.com.au (frenzy.communica.com.au [192.82.222.65]) by offensive.communica.com.au (8.7.6/8.7.3) with SMTP id JAA12041; Tue, 7 Jan 1997 09:27:13 +1030 (CST) Received: by communica.com.au (4.1/SMI-4.1) id AA28821; Tue, 7 Jan 97 09:24:04 CDT From: brawley@communica.com.au (Ivan Brawley) Message-Id: <9701062254.AA28821@communica.com.au> Subject: Re: Year 2000 time change(Format support) To: imp@village.org (Warner Losh) Date: Tue, 7 Jan 1997 09:24:04 +1030 (CST) Cc: hackers@freebsd.org In-Reply-To: from "Warner Losh" at Jan 6, 97 00:18:33 am X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > : How about the year 2038 problem, then ? =-) I believe time_t > : overflows then. > Only if we're all still running 32 bit hardware, or with a 32 bit > time_t :-) Its solely if we are using a 31bit time_t. (its a signed long). Make it an unsigned long and we get another 68 (or there abouts) years. Make it a 64bit number (yeah, will need to add extra code to handle the maths) and be set for quite a while... But then again, why use 00:00:00 1-Jan-1970 as the epoch. Its only used for hysterical (historical, these words are usually inter-changeable :-) reasons. ivan. From owner-freebsd-hackers Mon Jan 6 14:58:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA07692 for hackers-outgoing; Mon, 6 Jan 1997 14:58:15 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA07680 for ; Mon, 6 Jan 1997 14:58:10 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA12840; Mon, 6 Jan 1997 15:47:20 -0700 From: Terry Lambert Message-Id: <199701062247.PAA12840@phaeton.artisoft.com> Subject: Re: pib comments. To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 6 Jan 1997 15:47:20 -0700 (MST) Cc: msmith@atrad.adelaide.edu.au, mrcpu@cdsnet.net, hackers@freebsd.org In-Reply-To: <12969.852533091@time.cdrom.com> from "Jordan K. Hubbard" at Jan 5, 97 10:44:51 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I suggest that the Makefiles are a cache already (just a bad one 8), so > > the matter is one of degree, not principle. 8) > > Isn't that's sort of like saying "the haystack is the storage area for > the needle, so the difficulty in finding it is simply a matter of > degree, not principle." :-) Knowing there is a needle in the first place lets you decide to go get the auto-wrecker-crane electro magnet and squash the small problem with a large sledge-hammer. Just move the haystack outside first, or all the nails in your barn won't be in your barn any more. ;-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 14:58:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA07747 for hackers-outgoing; Mon, 6 Jan 1997 14:58:31 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA07735 for ; Mon, 6 Jan 1997 14:58:28 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id OAA19143 for ; Mon, 6 Jan 1997 14:59:19 -0800 (PST) Received: (qmail 23281 invoked by uid 110); 6 Jan 1997 22:57:57 -0000 Message-ID: <19970106225757.23279.qmail@suburbia.net> Subject: make world without -DYP In-Reply-To: from J Wunsch at "Jan 6, 97 09:35:40 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 7 Jan 1997 09:57:57 +1100 (EST) Cc: hackers@freebsd.org, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Last time I attempted to build world without YP, it failed in a number of places. Asside from the security issues, YP adds significant bloat to a varity of system libraries for those who do not need it (which must be the majority of FreeBSD users). > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > From owner-freebsd-hackers Mon Jan 6 15:01:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA08026 for hackers-outgoing; Mon, 6 Jan 1997 15:01:20 -0800 (PST) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA07997 for ; Mon, 6 Jan 1997 15:00:55 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr2-44.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA12802 (5.67b/IDA-1.5 for ); Mon, 6 Jan 1997 23:59:19 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.4/8.6.9) id XAA04895; Mon, 6 Jan 1997 23:59:06 +0100 (CET) Message-Id: Date: Mon, 6 Jan 1997 23:57:45 +0100 From: se@freebsd.org (Stefan Esser) To: tom@sdf.com (Tom Samplonius) Cc: hackers@freebsd.org Subject: Re: ncr 810 References: X-Mailer: Mutt 0.55-PL15 Mime-Version: 1.0 In-Reply-To: ; from Tom Samplonius on Jan 6, 1997 13:20:17 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Jan 6, tom@sdf.com (Tom Samplonius) wrote: > > How many concurrent commands can the ncr drive + a NCR 810 controller > handle? > > I know the ahc driver can handle 255 active commands, but only with scb > paging turned on. There is no controller limit on the number of active commands. The NCR keeps all variables in system DRAM (some variants have 4KB RAM on the controller chip, and can address it transparently, but the NCR driver does not yet take advantage of this feature). But remember that multiple active commands always cause some additional overhead. There are data structures, that have to be searched for a matching element, sometimes, and the NCR driver tries to keep them as simple as possible (for example to allow for simultanous accesses from the host CPU and the NCR without need for mutexes). I chose 4 tags per device as the default, and think that 8 give slightly better performance, but add more system overhead than I'm willing to pay. Others think differently, and suggest that a higher number of tags may be of advantage in multiple reader situations. The NCR driver checks every outstanding command for completion on each interrupt. This simplifies the driver (the NCR does only request a polling sweep from the CPU, instead of adding the ID of the completed request to some Queue), and is advantagous overall, I think. There is some memory required per command, too, BTW. A few hundred bytes per command (for the scatter/gather table, for example). With many simultanous commands, you may need tens to hundreds of KB for those tables ... Why do you need that many simultanous active commands ? Regards, STefan From owner-freebsd-hackers Mon Jan 6 15:03:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA08125 for hackers-outgoing; Mon, 6 Jan 1997 15:03:39 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA08120 for ; Mon, 6 Jan 1997 15:03:31 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA12858; Mon, 6 Jan 1997 15:53:12 -0700 From: Terry Lambert Message-Id: <199701062253.PAA12858@phaeton.artisoft.com> Subject: Re: sig-11 plague To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 6 Jan 1997 15:53:12 -0700 (MST) Cc: fisco.dev@sul.com.br, freebsd-hackers@freebsd.org In-Reply-To: from "J Wunsch" at Jan 6, 97 09:58:53 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > As Paulo Cesar Pereira de Andrade wrote: > > (sig 11 plague) > > > I resolved the problem in the BIOS setup, i disabled the external > > cache, and now cc1 does not fail. ... > > > I have now a doubt: is this a feature of pci or is a todo in > > FreeBSD (perhaps a done, since im using 2.1.0) or is i that have a not > > good hardware or another thing ? > > It's bad hardware, very clearly in your case (since turning off the > external cache worked). You don't describe your disk controller, but > if it's a SCSI busmaster controller, it might help to enable the > external cache but operate it in `write-through' mode. This doesn't > lose much performance (unlike turning it off totally). Alternately, if it's a VLB controller, move it to the outside slot, since you must put bus mastering VLB devices in "master" slots ("slave" slots do not do cache updates). Probably we could give you a better answer if you would tell us your hardware (like Joerg suggested). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 15:05:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA08337 for hackers-outgoing; Mon, 6 Jan 1997 15:05:49 -0800 (PST) Received: from sumatra.americantv.com (sumatra.americantv.com [199.184.181.250]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA08326 for ; Mon, 6 Jan 1997 15:05:45 -0800 (PST) Received: from right.PCS (right.pcs. [148.105.10.31]) by sumatra.americantv.com (8.7.6/8.7.3) with ESMTP id RAA11581; Mon, 6 Jan 1997 17:00:17 -0600 (CST) Received: (jlemon@localhost) by right.PCS (8.6.13/8.6.4) id XAA10197; Mon, 6 Jan 1997 23:04:06 GMT Message-Id: <199701062304.XAA10197@right.PCS> Date: Mon, 6 Jan 1997 17:04:06 -0600 From: jlemon@americantv.com (Jonathan Lemon) To: terry@lambert.org (Terry Lambert) Cc: andreas@klemm.gtn.com (Andreas Klemm), jfieber@indiana.edu, hackers@freebsd.org Subject: Re: New motherboard breaks tape drive References: <199701062048.NAA12457@phaeton.artisoft.com> X-Mailer: Mutt 0.48.1 Mime-Version: 1.0 In-Reply-To: <199701062048.NAA12457@phaeton.artisoft.com>; from Terry Lambert on Jan 6, 1997 13:48:59 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Because the HiNT chipset was so terrible, NiCE went under and was > sold off several times, so there are several vendors with HiNT > chipset systems. As far as I know, the HiNT chipset is only > present in a few older EISA or EISA/ISA systems. Heh. When I bought my EISA machine about 4 years back, I was worried that their motherboard wouldn't be able to cache any memory above 16M. So I called them up and asked them how many address lines they had going to their tag cache - nobody in their tech department could even answer my question. So I finally had them fax over the damned schematics and looked at them myself. Incompetents, sigh. (Yes, they only had 24 address lines, and I wanted to put in 32M back then). -- Jonathan From owner-freebsd-hackers Mon Jan 6 15:27:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA09618 for hackers-outgoing; Mon, 6 Jan 1997 15:27:07 -0800 (PST) Received: from hemi.com (hemi.com [204.132.158.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA09613 for ; Mon, 6 Jan 1997 15:27:03 -0800 (PST) Received: (from mbarkah@localhost) by hemi.com (8.8.4/8.7.3) id QAA19442; Mon, 6 Jan 1997 16:26:47 -0700 (MST) From: Ade Barkah Message-Id: <199701062326.QAA19442@hemi.com> Subject: Re: pib comments. To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Mon, 6 Jan 1997 16:26:46 -0700 (MST) Cc: msmith@atrad.adelaide.edu.au, hackers@freebsd.org In-Reply-To: from Jaye Mathisen at "Jan 6, 97 01:03:17 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jaye Mathisen wrote: > My frustration with TCL/TK was related to performance in general, > not your app. I've tried TKdesk, and it crawls, and zircon runs > like a dog as well. The common thread being my machine, and tcl/tk > apps. Well, TCL is generally pretty slow. It was supposed to be just a control/glue language, but somehow people are now writing huge code entirely in tcl+tk, instead of doing most of the work in something like C. During the "Great TCL Debate" =-) (circa 1994) Tom Christiansen offered the following comparison: [1000 iterations of factorial(20)] C 0.230u 0.040s 0:00.34 79.4% 0+206k x= 1.0 scheme 2.170u 0.130s 0:02.81 81.8% 0+659k x= 9.4 perl5 2.800u 0.110s 0:02.95 98.6% 0+616k x= 12.2 python 4.710u 0.120s 0:05.18 93.2% 0+504k x= 20.5 perl4 9.820u 0.180s 0:10.61 94.2% 0+825k x= 42.7 tcl 26.950u 0.080s 0:28.43 95.0% 0+459k x=117.17 sh don't ask :-) That x=117.17 is an eye opener. Of course one might think Tom used an example that favors Perl. =-) Here's selected entries from Jean-Jacques Girardot's benchmark posted to USENET back then: [Fibonacci function, useful for measuring interpretive languages] CPU Time Elapsed Time C Ratio C 6.2u 0:08 1.0 GLisp 76.6u 1:19 12.4 Smalltalk 306.5u 5:19 49.4 SIOD 371.0u 14:41 59.8 XSCHEME 492.2u 8:20 79.4 Python 1627.4u 27:55 262.5 Tcl 3478.0u 1:00:27 561.0 Anyway, pretty interesting numbers; they're not conclusive, of course, but imho one gets a feel for TCL's relative speed. Regards, -Ade ------------------------------------------------------------------- Inet: mbarkah@hemi.com - HEMISPHERE ONLINE - ------------------------------------------------------------------- From owner-freebsd-hackers Mon Jan 6 15:45:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA10892 for hackers-outgoing; Mon, 6 Jan 1997 15:45:58 -0800 (PST) Received: from anacreon.sol.net (anacreon.sol.net [206.55.64.116]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA10869; Mon, 6 Jan 1997 15:45:50 -0800 (PST) Received: from solaria.sol.net (solaria.sol.net [206.55.65.75]) by anacreon.sol.net (8.6.12/8.6.12) with ESMTP id RAA01178; Mon, 6 Jan 1997 17:45:49 -0600 Received: from localhost by solaria.sol.net (8.5/8.5) id RAA02007; Mon, 6 Jan 1997 17:45:46 -0600 From: Joe Greco Message-Id: <199701062345.RAA02007@solaria.sol.net> Subject: Re: FreeBSD as a cleanwall To: brandon@cold.org (Brandon Gillespie) Date: Mon, 6 Jan 97 17:45:44 CST Cc: security@freebsd.org, hackers@freebsd.org In-Reply-To: from "Brandon Gillespie" at Jan 6, 97 02:39:20 pm X-Mailer: ELM [version 2.4dev PL65] MIME-Version: 1.0 Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Does anybody have a configuration for packet filtering through a FreeBSD > router to run a cleanwall? Basically to keep all addresses of a specific > IP set (say a class C) on the right sides. I.e. only set addresses of > that set leave the network and don't allow any addresses of that set onto > the network? I'm mulling through the docs now, but figured to look here > for any possible pointers, as this seems like it would be a common enough > operation.. It's called "via" :-) You want something like this. This is designed to run on a gateway router. You have a P2P circuit between you and ISP ("Internet"), and your gateway is on an ethernet. Not that that's required, but just to explain this particular setup. ---- --------- -------------- ISP|<----------->|Gateway|--------|Internal Net| ---- --------- -------------- ^^^ ^^^ ^^^ LINK_IFC GATEWAY_IFC ADDRESS_BLOCK 204.95.219.2 206.55.64.1 206.55.64.0/25 On Gateway, do the following: ipfw f echo "Installing Firewall" # # ----- IP Bad Address Prevention Section ----- # Block RFC1597 "Private Internets" (inbound) ipfw addf deny all from 10.0.0.0/8 to 0/0 via ${LINK_IFC} ipfw addf deny all from 172.16.0.0/12 to 0/0 via ${LINK_IFC} ipfw addf deny all from 192.168.0.0/16 to 0/0 via ${LINK_IFC} # Block other "Shouldn't Exist" Internets (inbound) ipfw addf deny all from 127.0.0.0/8 to 0/0 via ${LINK_IFC} ipfw addf deny all from 0.0.0.0/8 to 0/0 via ${LINK_IFC} # Block RFC1597 "Private Internets" as Source Address (outbound) ipfw addf deny all from 10.0.0.0/8 to 0/0 via ${GATEWAY_IFC} ipfw addf deny all from 172.16.0.0/12 to 0/0 via ${GATEWAY_IFC} ipfw addf deny all from 192.168.0.0/16 to 0/0 via ${GATEWAY_IFC} # Block RFC1597 "Private Internets" as Destination Address (outbound) ipfw addf deny all from 0/0 to 10.0.0.0/8 via ${GATEWAY_IFC} ipfw addf deny all from 0/0 to 172.16.0.0/12 via ${GATEWAY_IFC} ipfw addf deny all from 0/0 to 192.168.0.0/16 via ${GATEWAY_IFC} # Block other "Shouldn't Exist" Internets as Source Address (outbound) ipfw addf deny all from 0/0 to 127.0.0.0/8 via ${GATEWAY_IFC} ipfw addf deny all from 0/0 to 0.0.0.0/8 via ${GATEWAY_IFC} # Block other "Shouldn't Exist" Internets as Destination Address (outbound) ipfw addf deny all from 127.0.0.0/8 to 0/0 via ${GATEWAY_IFC} ipfw addf deny all from 0.0.0.0/8 to 0/0 via ${GATEWAY_IFC} # # ----- IP Spoofing Prevention Section ----- # Block inbound pkts from addresses "on" my net (inbound) # (add as many lines as needed) ipfw addf deny all from ${ADDRESS_BLOCK} to 0/0 via ${LINK_IFC} # # Disallow all Source Addresses (outbound) ipfw addf deny all from 0/0 to 0/0 via ${GATEWAY_IFC} # Only allow outbound pkts from addresses "on" my net (outbound) # (add as many lines as needed) ipfw addf accept all from ${ADDRESS_BLOCK} to 0/0 via ${GATEWAY_IFC} # # Disallow all Destination Addresses (inbound) ipfw addf deny all from 0/0 to 0/0 via ${LINK_IFC} # Only allow inbound pkts to addresses "on" my net (inbound) # (add as many lines as needed) ipfw addf accept all from 0/0 to ${LINK_IFC} via ${LINK_IFC} ipfw addf accept all from 0/0 to ${ADDRESS_BLOCK} via ${LINK_IFC} # This was clearly designed for use on a low speed (SLIP) router, there are lots of optimizations. I wrote it for clarity. I also wrote it under 2.1.0R, so there may be some syntax differences. This will do a pretty thorough job of preventing bogus addresses; it is certainly a good starting point for a "cleanwall" :-) The comments were what I had in the file. If any of it is unclear after inspection, let me know and I will try to clarify. The router itself is mildly trusted to DTRT, by the way, and there are some minor holes. In particular, it is possible for a remote host to send packets with a source address of ${LINK_IFC} which could be fixed by ipfw addf deny all from ${LINK_IFC} to 0/0 via ${LINK_IFC} Some folks will say that this is the long way of doing this. They are right. But it was meant to potentially deal with multiple interfaces... ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-hackers Mon Jan 6 15:48:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA11088 for hackers-outgoing; Mon, 6 Jan 1997 15:48:31 -0800 (PST) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA11073 for ; Mon, 6 Jan 1997 15:48:24 -0800 (PST) Received: from austin.polstra.com by mail.crl.com with SMTP id AA01911 (5.65c/IDA-1.5 for ); Mon, 6 Jan 1997 15:48:18 -0800 Received: (from jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) id PAA10672; Mon, 6 Jan 1997 15:45:34 -0800 (PST) To: freebsd-hackers@freebsd.org Path: not-for-mail From: jdp@polstra.com (John Polstra) Newsgroups: polstra.freebsd.hackers Subject: Re: ld with -R weirdness Date: 6 Jan 1997 15:45:33 -0800 Organization: Polstra & Co., Seattle, WA Lines: 59 Distribution: local Message-Id: <5as2qt$add@austin.polstra.com> References: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , Ollivier Robert wrote: > In suidperl case, the command line given to gcc (then ld) is the following: > > cc -L/usr/local/lib -Wl,-R,/usr/local/lib/perl5/i386-freebsd/5.00319/CORE > -o suidperl perlmain.o sperl.o lib/auto/DynaLoader/DynaLoader.a > libperl.so.3.19 `cat ext.libs` -lm -lc -lcrypt > > The problem is that afterward, ld.so is NOT able to find libperl.so.3.19... > > 608 [23:40] roberto@keltia:/build/perl5.003_10> ( cd lib ; ldd ../suidperl) > ../suidperl: > libperl.so.3.19 (0x0) > -lm.2 => /usr/lib/libm.so.2.0 (0x8025000) > -lc.3 => /usr/lib/libc.so.3.0 (0x803c000) > -lcrypt.2 => /usr/lib/libcrypt.so.2.0 (0x80ad000) > > Even WITH LD_LIBRARY_PATH defined... For security reasons, LD_LIBRARY_PATH is ignored for setuid and setgid programs. > When I patch the Makefile to have > > cc -L/usr/local/lib -Wl,-R,/usr/local/lib/perl5/i386-freebsd/5.00319/CORE > -o suidperl perlmain.o sperl.o lib/auto/DynaLoader/DynaLoader.a > -lperl `cat ext.libs` -lm -lc -lcrypt > > It works ! If you specify the library name explicitly ("libperl.so.3.19"), it is recorded as a direct reference to that particular file, and no searching is done. Directories are searched only if you specify the library generically ("-lperl"). > Looking inside the suidperl executable, I find the following weird strings: > > o/usr/local/lib/perl5/i386-freebsd/5.00319/CORE > libperl.so.3.19 > crypt > > Where does the 'o' before the path come from ? This is not anything to worry about. The string begins with the "/" character. The byte before the string happens to contain a value which is the same as the ASCII for "o". Every byte contains _some_ value, and there is a reasonably high probability that any given byte will contain the ASCII code for a printable character. I should mention one other thing. If LD(1) is to be believed, there should be no space between ld's "-R" option and the "record-library-search-path" that follows it. (Just like the "-L" option.) You probably should remove the "," after "-Wl,-R". John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Mon Jan 6 15:53:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA11547 for hackers-outgoing; Mon, 6 Jan 1997 15:53:15 -0800 (PST) Received: from gatekeeper.fsl.noaa.gov (gatekeeper.fsl.noaa.gov [137.75.131.181]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA11536 for ; Mon, 6 Jan 1997 15:53:13 -0800 (PST) Received: from cardinal.fsl.noaa.gov (daemon@cardinal.fsl.noaa.gov [137.75.60.101]) by gatekeeper.fsl.noaa.gov (8.7.5/8.7.3) with ESMTP id XAA00848; Mon, 6 Jan 1997 23:53:06 GMT Received: from auk.fsl.noaa.gov by cardinal.fsl.noaa.gov with SMTP (1.40.112.3/16.2) id AA098334781; Mon, 6 Jan 1997 23:53:01 GMT Message-Id: <32D190C1.490E@fsl.noaa.gov> Date: Mon, 06 Jan 1997 16:54:41 -0700 From: Sean Kelly Organization: CIRA/NOAA X-Mailer: Mozilla 3.0Gold (X11; I; HP-UX B.10.10 9000/725) Mime-Version: 1.0 To: Ade Barkah Cc: Jaye Mathisen , msmith@atrad.adelaide.edu.au, hackers@freebsd.org Subject: Re: pib comments. References: <199701062326.QAA19442@hemi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ade Barkah wrote: > Well, TCL is generally pretty slow. It was supposed to be just > a control/glue language, but somehow people are now writing huge > code entirely in tcl+tk, ... Exactly. As a glue language, I haven't found anything easier to integrate. Of course, the counter-argument is that if you give people enough power in the language, they'll do things they weren't intended to do. You can still shoot your feet off in C, C++, Perl, and even Tcl. It's also sublime as a macro language for an application. For the National Weather Service, we have a feature that lets forecasters write macros to process the forecaster text database (you know, the local forecast stuff you actually want to see on the Weather Channel). The macro language is just Tcl, which is simple and crippled enough to not let them get into too much trouble. ;-) > Anyway, pretty interesting numbers; they're not conclusive, of > course, but imho one gets a feel for TCL's relative speed. Tcl 8.0 (available in alpha right now) includes an on-the-fly bytecode compiler. It oughta close the gap a bit! :-) -- Sean Kelly NOAA Forecast Systems Laboratory kelly@fsl.noaa.gov Boulder Colorado USA http://www-sdd.fsl.noaa.gov/~kelly/ From owner-freebsd-hackers Mon Jan 6 16:05:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA12820 for hackers-outgoing; Mon, 6 Jan 1997 16:05:49 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA12804; Mon, 6 Jan 1997 16:05:44 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id QAA01779; Mon, 6 Jan 1997 16:04:47 -0800 (PST) To: proff@suburbia.net cc: hackers@freebsd.org, security@freebsd.org Subject: Re: new firewall code [uid/gid/bind() etc] In-reply-to: Your message of "Tue, 07 Jan 1997 07:01:16 +1100." <19970106200116.16168.qmail@suburbia.net> Date: Mon, 06 Jan 1997 16:04:46 -0800 Message-ID: <1775.852595486@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I tried posting the patches but, at 55k, it seems majordumbo has > (silently) rejected them. You may find them at: Argh! This is not the way to do it - use send-pr(1) please! Jordan From owner-freebsd-hackers Mon Jan 6 16:26:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA15137 for hackers-outgoing; Mon, 6 Jan 1997 16:26:59 -0800 (PST) Received: from inf.enst.fr (j2FxukWKEoviVLMwf7mMpQD0SP4wxpZn@inf.enst.fr [137.194.2.81]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA15132 for ; Mon, 6 Jan 1997 16:26:56 -0800 (PST) Received: from nikopol.enst.fr (nikopol.enst.fr [137.194.168.105]) by inf.enst.fr (8.8.3/8.8.4) with ESMTP id BAA10666; Tue, 7 Jan 1997 01:26:49 +0100 (MET) Received: (from fenyo@localhost) by nikopol.enst.fr (8.8.3/8.8.2) id BAA07153; Tue, 7 Jan 1997 01:26:44 +0100 (MET) To: Cc: "Hackers" X-WWW: http://home.eowyn.fr.eu.org/~fenyo/documents/axel.html X-PGP-Key: finger alex@eowyn.fr.eu.org X-NIC-Handle: AF713 X-Whois: whois -h whois.internic.net fenyo X-Pager: 06-04-30-75-94 (for emergency only) Organization: Ecole Nationale Superieure des Telecommunications de Paris Subject: Re: ed0 boot [p]roms References: <199701061943.TAA84776@smtp-gw01.ny.us.ibm.net> From: fenyo@inf.enst.fr (Alex Fenyo (eowyn)) Date: 07 Jan 1997 01:26:42 +0100 In-Reply-To: "Steve Sims"'s message of Mon, 6 Jan 1997 14:40:42 -0500 Message-ID: Lines: 34 X-Mailer: Red Gnus v0.50/XEmacs 19.14 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Steve Sims" writes: > Who's the resident expert on boot ROMs for ed devices? I'm thinking about > building a diskless / floppy-less machine and have no earthly idea how to > proceed. > ... Using an ed ethernet device, I encountered a little problem with the options offered by the Makefile to build the rom. The Makefile says : # NS8390 Options: # -DINCLUDE_WD - Include Western Digital/SMC support # -DINCLUDE_NE - Include NE1000/NE2000 support # -DINCLUDE_3COM - Include 3c503 support I think it should say that it's not a good idea to use them all at the same time, to generate a rom with the three devices support. Suppose you compile with those three options, and you are using a NE1000/NE2000 card. Then, the problem is that eth_probe() (in ns8390.c) will first try to see if there is a WD compatible card; it's not this kind of card, so it continues, trying to see if there is a 3Com card. Again, it's not this kind of card, but instead of trying to continue with the next card type (NE1000/NE2000, the good one), the portion of code included when using -DINCLUDE_3COM executes a 'return 0', saying no ethernet card was found, and finally, the boot process fails. The problem appears only when using a NE1000/NE2000 card and having made the rom with the -DINCLUDE_3COM option. Alexandre Fenyo ps: modifying ns8390.c to do the right things doesn't seem to be very complicated. From owner-freebsd-hackers Mon Jan 6 16:34:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA15667 for hackers-outgoing; Mon, 6 Jan 1997 16:34:26 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA15662 for ; Mon, 6 Jan 1997 16:34:21 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id LAA06069; Tue, 7 Jan 1997 11:04:05 +1030 (CST) From: Michael Smith Message-Id: <199701070034.LAA06069@genesis.atrad.adelaide.edu.au> Subject: Re: ed0 boot [p]roms In-Reply-To: <199701061943.TAA84776@smtp-gw01.ny.us.ibm.net> from Steve Sims at "Jan 6, 97 02:40:42 pm" To: SimsS@IBM.Net Date: Tue, 7 Jan 1997 11:04:04 +1030 (CST) Cc: Hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Steve Sims stands accused of saying: > > I haven't done diskless in years, since we ran a secure net off of a Novell > server. That was painless, but the cards (with ROMs) ran about $300 back > then. > > I figure that with all these el-cheapo NE-2000 clones floating around, > somebody ought to have an idea on how to burn or where to buy an appropriate > bootp/tftp-able ROM for 'em. Buy your el-cheapo NE2000-with-bootrom-socket, go to /sys/i386/boot/netboot, edit the Makefile to suit and build yourself an image. Then get someone to make as many copies of the bootrom as you need. > ...sjs.. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jan 6 16:39:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA16073 for hackers-outgoing; Mon, 6 Jan 1997 16:39:04 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA16053; Mon, 6 Jan 1997 16:38:58 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id QAA20411; Mon, 6 Jan 1997 16:33:19 -0800 (PST) Message-ID: <32D19981.15FB7483@whistle.com> Date: Mon, 06 Jan 1997 16:32:01 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: "Mike O'Brien" CC: "Jonathan M. Bresler" , hackers@freefall.freebsd.org, chat@freefall.freebsd.org Subject: Re: Usenix FreeBSD BoF when? References: <199701062247.OAA07915@antares.aero.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mike O'Brien wrote: > > > thanks, will we be see you at usenix? > > Yep, I'll be there from Tuesday evening on. As will I (armed with job descriptions to post :) From owner-freebsd-hackers Mon Jan 6 16:55:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA16776 for hackers-outgoing; Mon, 6 Jan 1997 16:55:57 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA16771 for ; Mon, 6 Jan 1997 16:55:55 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id QAA02141; Mon, 6 Jan 1997 16:55:04 -0800 (PST) To: Ade Barkah cc: mrcpu@cdsnet.net (Jaye Mathisen), msmith@atrad.adelaide.edu.au, hackers@freebsd.org Subject: Re: pib comments. In-reply-to: Your message of "Mon, 06 Jan 1997 16:26:46 MST." <199701062326.QAA19442@hemi.com> Date: Mon, 06 Jan 1997 16:55:04 -0800 Message-ID: <2136.852598504@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > [1000 iterations of factorial(20)] > ... > [Fibonacci function, useful for measuring interpretive languages] > > Anyway, pretty interesting numbers; they're not conclusive, of > course, but imho one gets a feel for TCL's relative speed. Well, "sort of." The problem with both these benchmarks is that they're repetitive numerical calculations, something which TCL is not only most definitely not-good at, it's something it wasn't even *designed* to do. The expression handling in TCL is all done in string form, with conversion to and from integers or floats happening as needed by `expr'. This is a hideously slow process, and one is expected to use it only infrequently to calculate intermediate results or window sizes and such. TCL is, as you said in your first paragraph, a scripting language for extending or customizing application behavior. If people are using it to calculate factorials, they're using it for the wrong things, and for these tests to have been truly fair (to "the TCL way") they should have just shown the C numbers for TCL with a little tossed in for function call overhead (say +.01 for TCL) since any right-minded TCL programmer would have taken the C versions of the Factorial or Fibonacci series calculations and stuck a TCL wrapper around them before they would have even *considered* what Tom and Jean-Jacques have done here. :-) Jordan From owner-freebsd-hackers Mon Jan 6 16:57:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA16874 for hackers-outgoing; Mon, 6 Jan 1997 16:57:32 -0800 (PST) Received: from mailhub.aros.net (mailhub.aros.net [207.173.16.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA16866 for ; Mon, 6 Jan 1997 16:57:28 -0800 (PST) Received: from fluffy.aros.net (fluffy.aros.net [207.173.16.2]) by mailhub.aros.net (8.7.6/Unknown) with ESMTP id RAA04280; Mon, 6 Jan 1997 17:57:14 -0700 (MST) Received: from fluffy.aros.net (localhost [127.0.0.1]) by fluffy.aros.net (8.8.4/8.6.12) with ESMTP id RAA21385; Mon, 6 Jan 1997 17:57:11 -0700 (MST) Message-Id: <199701070057.RAA21385@fluffy.aros.net> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: angio@aros.net (Dave Andersen), hackers@freebsd.org Subject: Re: NFS sillyrenamedir In-reply-to: Your message of "Mon, 06 Jan 1997 22:26:21 +0100." Date: Mon, 06 Jan 1997 17:57:11 -0700 From: Dave Andersen Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Joerg Wunsch stated: > revision 1.39 > date: 1996/12/31 07:10:19; author: wpaul; state: Exp; lines: +3 -2 > Fix (properly, I hope) 'panic: sillyrename dir' crash that can happen > if you do: > > % cd /nfsdir > % mkdir -p foo/foo > % mv foo/foo . > > See, it's already done. :) Send the beer to Bill Paul... Ahhh, thank you - many beers owed. I didn't think to check under -current. (This is more of an issue for -current, but is someone planning on letting this one migrate its way in to 2.2? Or did I just lose track of a CTM somewhere?) -Dave From owner-freebsd-hackers Mon Jan 6 17:08:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA17329 for hackers-outgoing; Mon, 6 Jan 1997 17:08:26 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA17322 for ; Mon, 6 Jan 1997 17:08:22 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id LAA06345; Tue, 7 Jan 1997 11:36:25 +1030 (CST) From: Michael Smith Message-Id: <199701070106.LAA06345@genesis.atrad.adelaide.edu.au> Subject: Re: pib comments. In-Reply-To: <2136.852598504@time.cdrom.com> from "Jordan K. Hubbard" at "Jan 6, 97 04:55:04 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 7 Jan 1997 11:36:25 +1030 (CST) Cc: mbarkah@hemi.com, mrcpu@cdsnet.net, msmith@atrad.adelaide.edu.au, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > The problem with both these benchmarks is that they're repetitive > numerical calculations, something which TCL is not only most > definitely not-good at, it's something it wasn't even *designed* to > do. Spot on. I'd like to see some benchmarks biassed towards Tcl for a change, say, associative array lookup, or on-the-fly code generation, or any of the things that are actually useful in a glue language. Tcl8 and the bytecoder actually cheats fairly outrageously in that it uses an optimised internal representation for variables, and translates the representation as required, so once you have a variable with a known numeric type, it's much faster. With the bytecoder and various other things, it appears to run 3-5x faster on the small tests I've done. > ... since any > right-minded TCL programmer would have taken the C versions of the > Factorial or Fibonacci series calculations and stuck a TCL wrapper > around them before they would have even *considered* what Tom and > Jean-Jacques have done here. :-) Yup. Revolting. But "when all you have is a hammer..." > Jordan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jan 6 17:12:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA17575 for hackers-outgoing; Mon, 6 Jan 1997 17:12:30 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA17561 for ; Mon, 6 Jan 1997 17:12:23 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id RAA00285; Mon, 6 Jan 1997 17:11:30 -0800 (PST) To: Michael Smith cc: mbarkah@hemi.com, mrcpu@cdsnet.net, hackers@freebsd.org Subject: Re: pib comments. In-reply-to: Your message of "Tue, 07 Jan 1997 11:36:25 +1030." <199701070106.LAA06345@genesis.atrad.adelaide.edu.au> Date: Mon, 06 Jan 1997 17:11:30 -0800 Message-ID: <281.852599490@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Yup. Revolting. But "when all you have is a hammer..." I think this is more a case of: "When the only tool you know how to use is a hammer, you'll use the first screwdriver you come across for pounding nails." :-) From owner-freebsd-hackers Mon Jan 6 17:14:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA17767 for hackers-outgoing; Mon, 6 Jan 1997 17:14:00 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA17719; Mon, 6 Jan 1997 17:13:52 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id RAA00315; Mon, 6 Jan 1997 17:12:22 -0800 (PST) To: Julian Elischer cc: "Mike O'Brien" , "Jonathan M. Bresler" , hackers@freefall.freebsd.org, chat@freefall.freebsd.org Subject: Re: Usenix FreeBSD BoF when? In-reply-to: Your message of "Mon, 06 Jan 1997 16:32:01 PST." <32D19981.15FB7483@whistle.com> Date: Mon, 06 Jan 1997 17:12:22 -0800 Message-ID: <312.852599542@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > As will I (armed with job descriptions to post :) And a follow-up presentation for "DEVFS, one year later." perhaps? :-) :-) Jordan From owner-freebsd-hackers Mon Jan 6 17:19:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA18300 for hackers-outgoing; Mon, 6 Jan 1997 17:19:51 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA18278; Mon, 6 Jan 1997 17:19:04 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id SAA13211; Mon, 6 Jan 1997 18:09:18 -0700 From: Terry Lambert Message-Id: <199701070109.SAA13211@phaeton.artisoft.com> Subject: Re: Usenix FreeBSD BoF when? To: dg@root.com Date: Mon, 6 Jan 1997 18:09:18 -0700 (MST) Cc: jmb@freefall.freebsd.org, obrien@antares.aero.org, julian@whistle.com, hackers@freefall.freebsd.org, chat@freefall.freebsd.org In-Reply-To: <199701061652.IAA02764@root.com> from "David Greenman" at Jan 6, 97 08:52:20 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >and will take place in Salons 3 and 4 (seating for 100 people so come early) > > This probably won't be big enough. It was standing room only at the last > one, and we probably could have seated at least 150 people. I'm expecting > things to be even larger with a need for at least 200 seats. Invite the press... at least Bootle and Pournelle (Bootle will be thre; I don't know about Pournelle). That high an attendance of a "spontaneous" get-together is likely to merit a mention in their column... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 17:27:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA18663 for hackers-outgoing; Mon, 6 Jan 1997 17:27:08 -0800 (PST) Received: from antares.aero.org (antares.aero.org [130.221.192.46]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA18644; Mon, 6 Jan 1997 17:27:04 -0800 (PST) Received: from anpiel.aero.org (anpiel.aero.org [130.221.196.66]) by antares.aero.org (8.8.4/8.7.3) with SMTP id RAA09813; Mon, 6 Jan 1997 17:26:26 -0800 (PST) Message-Id: <199701070126.RAA09813@antares.aero.org> To: "Jordan K. Hubbard" Cc: Julian Elischer , "Mike O'Brien" , "Jonathan M. Bresler" , hackers@freefall.freebsd.org, chat@freefall.freebsd.org Subject: Apropos of nothing other than cool toys In-Reply-To: Your message of "Mon, 06 Jan 1997 17:12:22 PST." <312.852599542@time.cdrom.com> Date: Mon, 06 Jan 1997 17:26:16 -0800 From: "Mike O'Brien" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mr. Protocol (aka me, although I'll deny it) was loaned a MessagePad 2000 (the new Newton) for evaluation. I'll have it at the conference if anyone wants to sneak a look. Most cogent comment I've heard, and I believe it: if the original Newton had worked this well, we'd all own one by now. Mike O'Brien From owner-freebsd-hackers Mon Jan 6 17:31:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA19026 for hackers-outgoing; Mon, 6 Jan 1997 17:31:12 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA18996; Mon, 6 Jan 1997 17:30:58 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id RAA00438; Mon, 6 Jan 1997 17:29:29 -0800 (PST) To: "Mike O'Brien" cc: Julian Elischer , "Jonathan M. Bresler" , hackers@freefall.freebsd.org, chat@freefall.freebsd.org Subject: Re: Apropos of nothing other than cool toys In-reply-to: Your message of "Mon, 06 Jan 1997 17:26:16 PST." <199701070126.RAA09813@antares.aero.org> Date: Mon, 06 Jan 1997 17:29:28 -0800 Message-ID: <435.852600568@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Mr. Protocol (aka me, although I'll deny it) was loaned a MessagePad We've known you were Mr Protocol for years now, Mike - your secret is probably the worst-kept one in the universe. :-) > 2000 (the new Newton) for evaluation. I'll have it at the conference > if anyone wants to sneak a look. Most cogent comment I've heard, and > I believe it: if the original Newton had worked this well, we'd all > own one by now. I saw them at COMDEX and heard similar accolades from one of the evangelists, but didn't get close enough to play with one myself. I'll take you up on that. :-) Jordan From owner-freebsd-hackers Mon Jan 6 17:37:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA19423 for hackers-outgoing; Mon, 6 Jan 1997 17:37:53 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA19416 for ; Mon, 6 Jan 1997 17:37:46 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id MAA06601; Tue, 7 Jan 1997 12:07:20 +1030 (CST) From: Michael Smith Message-Id: <199701070137.MAA06601@genesis.atrad.adelaide.edu.au> Subject: Re: pib comments. In-Reply-To: from Jaye Mathisen at "Jan 6, 97 01:03:17 pm" To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Tue, 7 Jan 1997 12:07:19 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jaye Mathisen stands accused of saying: > > You'll note that I didn't slam your work specifically, in fact, I said it > was a great concept. You'll also note that it was a comment, and not a > statement that "The author is completely braindamaged, and should be taken > out and shot". So in a nutshell, relax. Hmm; perhaps I was annoyed at the inference that because Tcl/Tk was basically crap that I must have rocks in my head to use it and that therefore it could only be of use to Lusers. I'm _still_ narked that you didn't ask me personally, first, whether it was supposed to perform like a dog. > Perhaps it is my config, while I find it possible that it is something > with Accelerated-X, it seems odd that it only shows up in tk stuff, and > nothing else. It annoyed me no end too, but I was a little on the overbusy side to chase it at the time. I can confirm that it doesn't appear to happen with the 2.x Accel-X server, and Patrick G. at Xinside was obviously very keen to get it resolved; you might want to talk directly with him and see if there's something they can do for you. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jan 6 17:49:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA20242 for hackers-outgoing; Mon, 6 Jan 1997 17:49:57 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA20224; Mon, 6 Jan 1997 17:49:52 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id RAA04511; Mon, 6 Jan 1997 17:47:37 -0800 (PST) Message-Id: <199701070147.RAA04511@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Terry Lambert cc: hackers@freefall.freebsd.org, chat@freefall.freebsd.org Subject: Re: Usenix FreeBSD BoF when? In-reply-to: Your message of "Mon, 06 Jan 1997 18:09:18 MST." <199701070109.SAA13211@phaeton.artisoft.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 06 Jan 1997 17:47:37 -0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> >and will take place in Salons 3 and 4 (seating for 100 people so come early) >> >> This probably won't be big enough. It was standing room only at the last >> one, and we probably could have seated at least 150 people. I'm expecting >> things to be even larger with a need for at least 200 seats. > >Invite the press... at least Bootle and Pournelle (Bootle will be thre; >I don't know about Pournelle). That high an attendance of a "spontaneous" >get-together is likely to merit a mention in their column... Oh, I doubt it. The Linux BOF last year had more than 500 in attendance. They had their BOF in The Grand Ballroom...I was thinking last year that we should have done the same thing. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Jan 6 17:57:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA20840 for hackers-outgoing; Mon, 6 Jan 1997 17:57:18 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA20817; Mon, 6 Jan 1997 17:57:08 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id SAA13380; Mon, 6 Jan 1997 18:47:29 -0700 From: Terry Lambert Message-Id: <199701070147.SAA13380@phaeton.artisoft.com> Subject: Re: Usenix FreeBSD BoF when? To: dg@root.com Date: Mon, 6 Jan 1997 18:47:29 -0700 (MST) Cc: terry@lambert.org, hackers@freefall.freebsd.org, chat@freefall.freebsd.org In-Reply-To: <199701070147.RAA04511@root.com> from "David Greenman" at Jan 6, 97 05:47:37 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> This probably won't be big enough. It was standing room only at the last > >> one, and we probably could have seated at least 150 people. I'm expecting > >> things to be even larger with a need for at least 200 seats. > > > >Invite the press... at least Bootle and Pournelle (Bootle will be thre; > >I don't know about Pournelle). That high an attendance of a "spontaneous" > >get-together is likely to merit a mention in their column... > > Oh, I doubt it. The Linux BOF last year had more than 500 in attendance. > They had their BOF in The Grand Ballroom...I was thinking last year that we > should have done the same thing. I meant "an obviously larger than expected number of people" at such an event where the press people were in attendance... they probably weren't at the Linux event (or the Linux event *did* get mention. Better to look like you have more people interested than you expected than to look like you have less... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 6 18:02:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA21057 for hackers-outgoing; Mon, 6 Jan 1997 18:02:28 -0800 (PST) Received: from profane.iq.org (profane.iq.org [203.4.184.217]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA21051 for ; Mon, 6 Jan 1997 18:02:14 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id NAA01908 for hackers@freebsd.org; Tue, 7 Jan 1997 13:01:01 +1100 (EST) From: Julian Assange Message-Id: <199701070201.NAA01908@profane.iq.org> Subject: envfs and /usr/share/skel/* stupidity To: hackers@freebsd.org Date: Tue, 7 Jan 1997 13:01:01 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk dot.cshrc, dot.login and dot.profile are brain-dead. they set PATH, TERM VI, MANPATH and a number of other enviromental variables, as well as umask and various mail stuff. NONE of these should be set by default. it totally destroys the concept of central management, and the TERM case breaks remote logins. dot.* should not do anything, and should merely be provided for as a (commented out!) template. Everything here should be moved into /etc/profile /etc/csh.cshrc etc. Personally, use a psuedo "envfs" /etc/env which contains system defaults for PATH, MANPATH, INFOPATH, EDITOR, PAGER etc. /etc/profile, /etc/rc (etc) then does: if cd /etc/env then for n in * do read v<$n eval $n=$v done cd - fi and in my dot.profile if cd $HOME/env then for n in * do read v<$n eval $n=$v done cd - fi which gives the user their own "envfs". Note that because eval is used, it is possible to have "`cat /etc/nntpserver`" etc, as the entry for NNTPSERVER -Julian From owner-freebsd-hackers Mon Jan 6 18:10:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA21492 for hackers-outgoing; Mon, 6 Jan 1997 18:10:36 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA21487 for ; Mon, 6 Jan 1997 18:10:32 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vhQyx-0006lU-00; Mon, 6 Jan 1997 19:09:39 -0700 To: "Jordan K. Hubbard" Subject: Re: pib comments. Cc: Michael Smith , mbarkah@hemi.com, mrcpu@cdsnet.net, hackers@freebsd.org In-reply-to: Your message of "Mon, 06 Jan 1997 17:11:30 PST." <281.852599490@time.cdrom.com> References: <281.852599490@time.cdrom.com> Date: Mon, 06 Jan 1997 19:09:39 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <281.852599490@time.cdrom.com> "Jordan K. Hubbard" writes: : "When the only tool you know how to use is a hammer, you'll : use the first screwdriver you come across for pounding nails." "Back when I was a youngster, we had to use hammers as a torque wrench, and let me tell you, they worked a damn sight better than these new-fangled things you call torque wrenches today. Sure it was hard to use, but you had to know what you were doing or you'd blow everything up." Warner From owner-freebsd-hackers Mon Jan 6 19:15:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA24341 for hackers-outgoing; Mon, 6 Jan 1997 19:15:21 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA24336 for ; Mon, 6 Jan 1997 19:15:14 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id NAA07327; Tue, 7 Jan 1997 13:43:52 +1030 (CST) From: Michael Smith Message-Id: <199701070313.NAA07327@genesis.atrad.adelaide.edu.au> Subject: Re: Ints (fwd) In-Reply-To: <3.0.1.32.19970106032347.0067e4ac@bugs.us.dell.com> from Tony Overfield at "Jan 6, 97 03:28:09 am" To: tony@dell.com (Tony Overfield) Date: Tue, 7 Jan 1997 13:43:51 +1030 (CST) Cc: bde@zeta.org.au, grog@lemis.de, msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tony Overfield stands accused of saying: > > There is a scheme for sharing ISA edge-triggered interrupts that > involves pulsing. It works by declaring that the IRQ will remain > high (by pull-up, not driven) until a device wants interrupt service. > At that time the device pulses the IRQ low for 100-200 ns and then > releases it again to cause the rising edge. Eventually, the interrupt > occurs, and the interrupt service routine(s) must then check all the > registered devices to see which one(s) caused the interrupt. Because > the IRQ is pulled high by the pull-up resistor, spurious interrupts > won't be generated. This may seem peculiar, but I've seen it in > operation. It's highly suboptimal; with the specified 2.2K pullup and assuming 60pf of line capacitance (conservative) you get a risetime of over 130nsec (hey, got the right number of zeroes this time 8), which is grossly out of spec for any logic family on the market these days. An edge that slow can actually cause serious problems if it has any noise on it. > Tony -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jan 6 19:20:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA24546 for hackers-outgoing; Mon, 6 Jan 1997 19:20:39 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id TAA24540 for ; Mon, 6 Jan 1997 19:20:36 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA20604; Mon, 6 Jan 1997 22:20:03 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 6 Jan 1997 22:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id VAA00944; Mon, 6 Jan 1997 21:26:58 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id VAA00934; Mon, 6 Jan 1997 21:30:10 -0500 (EST) Date: Mon, 6 Jan 1997 21:30:10 -0500 (EST) From: Thomas David Rivers Message-Id: <199701070230.VAA00934@lakes.water.net> To: terry@lambert.org, ponds!atrad.adelaide.edu.au!msmith Subject: Re: make(1) substitution question... Cc: ponds!freebsd.org!hackers Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk terry@lambert.org writes: > > > > Can anyone suggest a way of making this DWIM without involving the shell? > > > > FOO= test > > BAR= FOO > BAR= $(FOO) You have to be careful here. Different make implementations will evaluate $(FOO) at different times; which can produce different results. That is, is $(FOO) evaluated when make stumbles across the "BAR= $(FOO)", or is $(FOO) evaluated in a lazy fashion, when make stumbles into $(BAR)... - Dave Rivers - From owner-freebsd-hackers Mon Jan 6 22:32:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA01718 for hackers-outgoing; Mon, 6 Jan 1997 22:32:24 -0800 (PST) Received: from marvin.mmedia.com (root@marvin.mmedia.com [199.240.226.118]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA01713 for ; Mon, 6 Jan 1997 22:32:19 -0800 (PST) Received: (from joed@localhost) by marvin.mmedia.com (8.8.4/8.8.2) id AAA12120; Tue, 7 Jan 1997 00:32:12 -0600 (CST) Message-ID: Date: Tue, 7 Jan 1997 00:32:11 -0600 From: joed@ksu.edu (Joe Diehl) To: hackers@freebsd.org Subject: adduser script X-Mailer: Mutt 0.55 Mime-Version: 1.0 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, Many moons ago there was discussion on -hackers about the perl adduser script and what to do with it. What every happened with that discussion, and/or is there any perl work that needs to be done on it? --- Joe Diehl KSU Dept. of Telecommunications From owner-freebsd-hackers Mon Jan 6 23:12:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA03059 for hackers-outgoing; Mon, 6 Jan 1997 23:12:48 -0800 (PST) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id XAA03054 for ; Mon, 6 Jan 1997 23:12:44 -0800 (PST) Received: from misery.sdf.com [204.244.213.33] by misery.sdf.com with smtp (Exim 1.59 #1) id 0vhViC-0000oj-00; Mon, 6 Jan 1997 23:12:40 -0800 Date: Mon, 6 Jan 1997 23:12:40 -0800 (PST) From: Tom Samplonius To: Joe Diehl cc: hackers@freebsd.org Subject: Re: adduser script In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 7 Jan 1997, Joe Diehl wrote: > Greetings, > > Many moons ago there was discussion on -hackers about the perl adduser > script and what to do with it. What every happened with that discussion, > and/or is there any perl work that needs to be done on it? Perhaps you're not aware that an adduser script has been part of FreeBSD since release 2.1.5 (maybe even 2.1?). > --- > Joe Diehl > KSU Dept. of Telecommunications > > > Tom From owner-freebsd-hackers Mon Jan 6 23:55:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA04726 for hackers-outgoing; Mon, 6 Jan 1997 23:55:32 -0800 (PST) Received: from marvin.mmedia.com (root@marvin.mmedia.com [199.240.226.118]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA04721 for ; Mon, 6 Jan 1997 23:55:27 -0800 (PST) Received: (from joed@localhost) by marvin.mmedia.com (8.8.4/8.8.2) id BAA12359; Tue, 7 Jan 1997 01:55:13 -0600 (CST) Message-ID: Date: Tue, 7 Jan 1997 01:55:12 -0600 From: joed@ksu.edu (Joe Diehl) To: tom@sdf.com (Tom Samplonius) Cc: hackers@freebsd.org Subject: Re: adduser script References: X-Mailer: Mutt 0.55 Mime-Version: 1.0 In-Reply-To: ; from Tom Samplonius on Jan 6, 1997 23:12:40 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Tom Samplonius writes: > > On Tue, 7 Jan 1997, Joe Diehl wrote: > > > Greetings, > > > > Many moons ago there was discussion on -hackers about the perl adduser > > script and what to do with it. What every happened with that discussion, > > and/or is there any perl work that needs to be done on it? > > Perhaps you're not aware that an adduser script has been part of FreeBSD > since release 2.1.5 (maybe even 2.1?). > Yes, the script has existed at least since 2.0.5-ALPHA (which is the first version that could handle LBA translations)... I believe the conversation consisted more of the lines that the script needing modifying in some way, but the general perl knowledge pool was relatively thin. I'm not sure, it's been a while since that conversation took place and my memory is fairly hazy. --- Joe Diehl KSU Dept. of Telecommunications From owner-freebsd-hackers Tue Jan 7 00:08:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA05394 for hackers-outgoing; Tue, 7 Jan 1997 00:08:01 -0800 (PST) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA05367; Tue, 7 Jan 1997 00:07:58 -0800 (PST) Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) with ESMTP id AAA00649; Tue, 7 Jan 1997 00:07:57 -0800 (PST) From: Josh MacDonald Message-Id: <199701070807.AAA00649@paris.CS.Berkeley.EDU> To: freebsd-ports@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: installing info files MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <642.852624474.1@paris.CS.Berkeley.EDU> Date: Tue, 07 Jan 1997 00:07:55 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I apologize if this has already been discussed, I just resubscribed after unsubscribing for finals. GNU texinfo-3.9 was released sometime in November. In addition to some long-awaited bug-fixes, it introduces the install-info program, which finally makes it easy to install info files into the dir file, usually /usr/local/info/dir or /usr/share/info/dir. I use info a lot and like to have my dir file up to date, but notice that many of the packages in ports do not install the info files. Does anyone think it would be nice for the package tools and bsd.port.mk to be more aware of info files? There are two new texinfo commands called @dircategory and @direntry which are used by the author of the info file to tell install-info what nodes to link into the dir file and what category to install them in. For example, I added: @dircategory Version Control @direntry * PRCS: (prcs). The Project Revision Control System. @end direntry to the texinfo file for PRCS. When I run install-info, it adds a label "Version Control" if it doesn't exist and the node PRCS if it doesn't exist. What I propose is to remove /usr/src/gnu/usr.bin/texinfo and place the latest version in /usr/src/contrib/texinfo. This will likely involve upgrading some of the info files scattered throughout the tree because for some reason makeinfo doesn't understand old formats (makeinfo in the tree is pretty old, if I try to make world with the current version of makeinfo it fails in several places because the new version of makeinfo pukes on the texinfo files in the source tree). Then, add support to pkg_add and friends and bsd.port.mk, I'll do the work, how's this sound? -josh From owner-freebsd-hackers Tue Jan 7 00:16:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA05929 for hackers-outgoing; Tue, 7 Jan 1997 00:16:20 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id AAA05910 for ; Tue, 7 Jan 1997 00:16:14 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA06789; Tue, 7 Jan 1997 09:14:50 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA12506; Tue, 7 Jan 1997 09:14:50 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id JAA08244; Tue, 7 Jan 1997 09:13:13 +0100 (MET) Message-ID: Date: Tue, 7 Jan 1997 09:13:13 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Cc: angio@aros.net (Dave Andersen) Subject: Re: NFS sillyrenamedir References: <199701070057.RAA21385@fluffy.aros.net> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701070057.RAA21385@fluffy.aros.net>; from Dave Andersen on Jan 6, 1997 17:57:11 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Dave Andersen wrote: > (This is more of an issue for -current, but is someone planning on letting > this one migrate its way in to 2.2? Or did I just lose track of a CTM > somewhere?) It's marked for inclusion into 2.2, so yes, it will be there. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jan 7 01:01:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA07860 for hackers-outgoing; Tue, 7 Jan 1997 01:01:12 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA07854; Tue, 7 Jan 1997 01:01:08 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id TAA10109; Tue, 7 Jan 1997 19:31:01 +1030 (CST) From: Michael Smith Message-Id: <199701070901.TAA10109@genesis.atrad.adelaide.edu.au> Subject: Re: installing info files In-Reply-To: <199701070807.AAA00649@paris.CS.Berkeley.EDU> from Josh MacDonald at "Jan 7, 97 00:07:55 am" To: jmacd@CS.Berkeley.EDU (Josh MacDonald) Date: Tue, 7 Jan 1997 19:31:00 +1030 (CST) Cc: freebsd-ports@freebsd.org, freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Josh MacDonald stands accused of saying: > I apologize if this has already been discussed, I just resubscribed It hasn't. > I use info a lot and like to have my dir file up to date, but notice that > many of the packages in ports do not install the info files. Does anyone > think it would be nice for the package tools and bsd.port.mk to be more > aware of info files? Yes! > What I propose is to remove /usr/src/gnu/usr.bin/texinfo and place > the latest version in /usr/src/contrib/texinfo... Then, add support > to pkg_add and friends and bsd.port.mk, I'll do the work, how's this > sound? Great; please do it! > -josh -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Jan 7 01:27:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA09248 for hackers-outgoing; Tue, 7 Jan 1997 01:27:00 -0800 (PST) Received: from dfw-ix9.ix.netcom.com (dfw-ix9.ix.netcom.com [206.214.98.9]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id BAA09241; Tue, 7 Jan 1997 01:26:58 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (wck-ca14-58.ix.netcom.com [207.92.174.122]) by dfw-ix9.ix.netcom.com (8.6.13/8.6.12) with ESMTP id BAA10948; Tue, 7 Jan 1997 01:25:38 -0800 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.4/8.6.9) id BAA03038; Tue, 7 Jan 1997 01:22:38 -0800 (PST) Date: Tue, 7 Jan 1997 01:22:38 -0800 (PST) Message-Id: <199701070922.BAA03038@silvia.HIP.Berkeley.EDU> To: jmacd@cs.berkeley.edu CC: freebsd-ports@freebsd.org, freebsd-hackers@freebsd.org In-reply-to: <199701070807.AAA00649@paris.CS.Berkeley.EDU> (message from Josh MacDonald on Tue, 07 Jan 1997 00:07:55 -0800) Subject: Re: installing info files From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * For example, I added: * * @dircategory Version Control * @direntry * * PRCS: (prcs). The Project Revision Control System. * @end direntry * * to the texinfo file for PRCS. When I run install-info, it adds a label * "Version Control" if it doesn't exist and the node PRCS if it doesn't * exist. This sounds great. * tree). Then, add support to pkg_add and friends and bsd.port.mk, * I'll do the work, how's this sound? What exactly does bsd.port.mk/pkg_add have to do here? What is the usage of install-info? Satoshi From owner-freebsd-hackers Tue Jan 7 01:39:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA10138 for hackers-outgoing; Tue, 7 Jan 1997 01:39:41 -0800 (PST) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA10117; Tue, 7 Jan 1997 01:39:33 -0800 (PST) Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) with ESMTP id BAA00852; Tue, 7 Jan 1997 01:39:26 -0800 (PST) From: Josh MacDonald Message-Id: <199701070939.BAA00852@paris.CS.Berkeley.EDU> To: freebsd-hackers@freebsd.org, freebsd-ports@freebsd.org Subject: upgrading texinfo MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <845.852629963.1@paris.CS.Berkeley.EDU> Date: Tue, 07 Jan 1997 01:39:24 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The old texinfo sources in the tree installed programs named 'texindex' and 'makedoc'. The first is a tool which is only useful for generating .dvi files from .texi files and shouldn't see much use without the texi2dvi script which wasn't being installed. I don't see much reason to install this, since tex isn't in the source tree. The same goes for 'texi2dvi', it won't see much use without tex installed either, and anyone who installs tex is likely to get another copy of these utilities anyway. The program 'makedoc' appears to be a doc-string generator for emacs and is in /usr/bin right now but has no man page, its not even in the current version and I don't see anything using this or the above utilities in the source tree. I propose to delete the old texinfo sources, put new sources in the contrib directory, change how /usr/share/info/dir is installed (using install-info) and the bsd.info.mk rules, and only install info, makeinfo, and instal-info into /usr/bin. Again, I'll do the work (I'm partly done, in fact). After that, to pursue my original goal, bsd.port.mk needs work to encourage the installation of info files correctly (using install-info). Comments? -josh From owner-freebsd-hackers Tue Jan 7 02:18:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA12324 for hackers-outgoing; Tue, 7 Jan 1997 02:18:35 -0800 (PST) Received: from thelab.hub.org (hal-ns1-02.netcom.ca [207.181.94.66]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA12317 for ; Tue, 7 Jan 1997 02:18:30 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.4/8.8.2) with SMTP id GAA03896 for ; Tue, 7 Jan 1997 06:18:20 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 7 Jan 1997 06:18:20 -0400 (AST) From: The Hermit Hacker To: hackers@freebsd.org Subject: mmap() updates...how often? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... Not quite sure how to word this one, but how often does an mmap() region get updated, in so far as client processes seeing the data that the server process writes to it? The reason I'm asking is that I have a program that is using mmap() to pass frames from a central server to client processes. The central server is writing, on average, 20frames/sec to the mmap()'d region, and after each write, it sets a counter, also mmap()'d, that the client uses as, more or less, a position indicator. The problem is that the client seems only to see every 20th frame, as far as the indicator is concerned. I would expect some "skippage" between client reads (ie. server wrote 2 frames before the client got a chance to check the indicator again), but it seems to be *very* consistent at 20... Does this make sense? I thought about making use of msync() right after writing each frame, but looking at the man page (if I'm reading it right) seems to indicate that this would just write the data from memory to the disk file...and since I'm closing the disk file after memory mapping it, don't believe this is appropriate... Not being quite sure of what other data I can provide, does anyone have any suggestions on what I'm seeing? Since its memory mapped, I would have made the assumption that changes to the data would be seen instantaneously by the client, but either I'm missing something in my code (staring at it too long does that) or I'm once more missing something with mmap() Thanks... From owner-freebsd-hackers Tue Jan 7 02:35:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA13060 for hackers-outgoing; Tue, 7 Jan 1997 02:35:08 -0800 (PST) Received: from dfw-ix4.ix.netcom.com (dfw-ix4.ix.netcom.com [206.214.98.4]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA13038; Tue, 7 Jan 1997 02:35:02 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (wck-ca14-58.ix.netcom.com [207.92.174.122]) by dfw-ix4.ix.netcom.com (8.6.13/8.6.12) with ESMTP id CAA18227; Tue, 7 Jan 1997 02:34:23 -0800 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.4/8.6.9) id CAA03389; Tue, 7 Jan 1997 02:34:05 -0800 (PST) Date: Tue, 7 Jan 1997 02:34:05 -0800 (PST) Message-Id: <199701071034.CAA03389@silvia.HIP.Berkeley.EDU> To: jmacd@CS.Berkeley.EDU CC: freebsd-hackers@freebsd.org, freebsd-ports@freebsd.org In-reply-to: <199701070939.BAA00852@paris.CS.Berkeley.EDU> (message from Josh MacDonald on Tue, 07 Jan 1997 01:39:24 -0800) Subject: Re: upgrading texinfo From: asami@CS.Berkeley.EDU (Satoshi Asami) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * After that, to pursue my original goal, bsd.port.mk needs work * to encourage the installation of info files correctly (using * install-info). That's all nice and fine, but I still don't exactly understand what bsd.port.mk has to do with this. Shouldn't ports' Makefiles be patched to use install-info? Satoshi From owner-freebsd-hackers Tue Jan 7 02:41:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA13978 for hackers-outgoing; Tue, 7 Jan 1997 02:41:04 -0800 (PST) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA13951; Tue, 7 Jan 1997 02:40:57 -0800 (PST) Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) with ESMTP id CAA00973; Tue, 7 Jan 1997 02:40:49 -0800 (PST) From: Josh MacDonald Message-Id: <199701071040.CAA00973@paris.CS.Berkeley.EDU> To: asami@cs.berkeley.edu (Satoshi Asami) cc: freebsd-hackers@freebsd.org, freebsd-ports@freebsd.org Subject: Re: upgrading texinfo In-reply-to: Your message of "Tue, 07 Jan 1997 02:34:05 PST." <199701071034.CAA03389@silvia.HIP.Berkeley.EDU> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <966.852633646.1@paris.CS.Berkeley.EDU> Date: Tue, 07 Jan 1997 02:40:47 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > * After that, to pursue my original goal, bsd.port.mk needs work > * to encourage the installation of info files correctly (using > * install-info). > > That's all nice and fine, but I still don't exactly understand what > bsd.port.mk has to do with this. Shouldn't ports' Makefiles be > patched to use install-info? Yeah, I assumed some sort of default rule could be defined in bsd.port.mk, up to you. It should also be set up so that packages use @exec and @unexec to install info files. I guess this too falls on the package maintainer. Unless I'm wrong, this seems like a shortcoming of the pkg_create utility. -josh From owner-freebsd-hackers Tue Jan 7 02:50:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA14760 for hackers-outgoing; Tue, 7 Jan 1997 02:50:04 -0800 (PST) Received: from dfw-ix12.ix.netcom.com (dfw-ix12.ix.netcom.com [206.214.98.12]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA14717; Tue, 7 Jan 1997 02:49:57 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (wck-ca14-58.ix.netcom.com [207.92.174.122]) by dfw-ix12.ix.netcom.com (8.6.13/8.6.12) with ESMTP id CAA24657; Tue, 7 Jan 1997 02:49:11 -0800 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.4/8.6.9) id CAA03643; Tue, 7 Jan 1997 02:48:42 -0800 (PST) Date: Tue, 7 Jan 1997 02:48:42 -0800 (PST) Message-Id: <199701071048.CAA03643@silvia.HIP.Berkeley.EDU> To: jmacd@CS.Berkeley.EDU CC: freebsd-hackers@freebsd.org, freebsd-ports@freebsd.org In-reply-to: <199701071040.CAA00973@paris.CS.Berkeley.EDU> (message from Josh MacDonald on Tue, 07 Jan 1997 02:40:47 -0800) Subject: Re: upgrading texinfo From: asami@CS.Berkeley.EDU (Satoshi Asami) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * Yeah, I assumed some sort of default rule could be defined in * bsd.port.mk, up to you. It should also be set up so that packages * use @exec and @unexec to install info files. I guess this too * falls on the package maintainer. Unless I'm wrong, this seems * like a shortcoming of the pkg_create utility. Just tell me how to call install-info and we can discuss the solutions. Satoshi From owner-freebsd-hackers Tue Jan 7 03:07:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA15513 for hackers-outgoing; Tue, 7 Jan 1997 03:07:58 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id DAA15508; Tue, 7 Jan 1997 03:07:56 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id DAA25323; Tue, 7 Jan 1997 03:07:52 -0800 (PST) To: Josh MacDonald cc: freebsd-ports@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: installing info files In-reply-to: Your message of "Tue, 07 Jan 1997 00:07:55 PST." <199701070807.AAA00649@paris.CS.Berkeley.EDU> Date: Tue, 07 Jan 1997 03:07:52 -0800 Message-ID: <25320.852635272@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk That sounds great, and long overdue! It's worth it for the auto-Dir file updating alone. Jordan > I apologize if this has already been discussed, I just resubscribed > after unsubscribing for finals. GNU texinfo-3.9 was released sometime > in November. In addition to some long-awaited bug-fixes, it introduces > the install-info program, which finally makes it easy to install info > files into the dir file, usually /usr/local/info/dir or /usr/share/info/dir. > > I use info a lot and like to have my dir file up to date, but notice that > many of the packages in ports do not install the info files. Does anyone > think it would be nice for the package tools and bsd.port.mk to be more > aware of info files? > > There are two new texinfo commands called @dircategory and @direntry > which are used by the author of the info file to tell install-info what > nodes to link into the dir file and what category to install them in. > > For example, I added: > > @dircategory Version Control > @direntry > * PRCS: (prcs). The Project Revision Control System. > @end direntry > > to the texinfo file for PRCS. When I run install-info, it adds a label > "Version Control" if it doesn't exist and the node PRCS if it doesn't > exist. > > What I propose is to remove /usr/src/gnu/usr.bin/texinfo and place > the latest version in /usr/src/contrib/texinfo. This will likely > involve upgrading some of the info files scattered throughout the > tree because for some reason makeinfo doesn't understand old formats > (makeinfo in the tree is pretty old, if I try to make world with > the current version of makeinfo it fails in several places because > the new version of makeinfo pukes on the texinfo files in the source > tree). Then, add support to pkg_add and friends and bsd.port.mk, > I'll do the work, how's this sound? > > -josh From owner-freebsd-hackers Tue Jan 7 03:13:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA15764 for hackers-outgoing; Tue, 7 Jan 1997 03:13:50 -0800 (PST) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id DAA15747; Tue, 7 Jan 1997 03:13:44 -0800 (PST) Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) with ESMTP id DAA01100; Tue, 7 Jan 1997 03:13:41 -0800 (PST) From: Josh MacDonald Message-Id: <199701071113.DAA01100@paris.CS.Berkeley.EDU> To: asami@cs.berkeley.edu (Satoshi Asami) cc: freebsd-hackers@freebsd.org, freebsd-ports@freebsd.org Subject: Re: upgrading texinfo In-reply-to: Your message of "Tue, 07 Jan 1997 02:48:42 PST." <199701071048.CAA03643@silvia.HIP.Berkeley.EDU> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1093.852635617.1@paris.CS.Berkeley.EDU> Date: Tue, 07 Jan 1997 03:13:39 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > * Yeah, I assumed some sort of default rule could be defined in > * bsd.port.mk, up to you. It should also be set up so that packages > * use @exec and @unexec to install info files. I guess this too > * falls on the package maintainer. Unless I'm wrong, this seems > * like a shortcoming of the pkg_create utility. > > Just tell me how to call install-info and we can discuss the > solutions. briefly: install-info [--delete] info-file dir-file either adds or with --delete removes the entries for info-file from dir-file. if the info file is not properly equiped (it must have the extra commands I mentioned in previous mail) install-info will exit with non-zero status and print install-info: no info dir entry in `file.info' a lot of packages will not have the extra data yet, but its easy to add and I think it would be worth doing it just to have a ports tree that installs info-files correctly. you either modify the texinfo source or the info file itself, either will do. -josh From owner-freebsd-hackers Tue Jan 7 03:40:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA16863 for hackers-outgoing; Tue, 7 Jan 1997 03:40:03 -0800 (PST) Received: from dfw-ix2.ix.netcom.com (dfw-ix2.ix.netcom.com [206.214.98.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id DAA16799; Tue, 7 Jan 1997 03:39:57 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (wck-ca14-58.ix.netcom.com [207.92.174.122]) by dfw-ix2.ix.netcom.com (8.6.13/8.6.12) with ESMTP id DAA27848; Tue, 7 Jan 1997 03:38:54 -0800 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.4/8.6.9) id DAA04094; Tue, 7 Jan 1997 03:38:20 -0800 (PST) Date: Tue, 7 Jan 1997 03:38:20 -0800 (PST) Message-Id: <199701071138.DAA04094@silvia.HIP.Berkeley.EDU> To: jmacd@CS.Berkeley.EDU CC: freebsd-hackers@freebsd.org, freebsd-ports@freebsd.org In-reply-to: <199701071113.DAA01100@paris.CS.Berkeley.EDU> (message from Josh MacDonald on Tue, 07 Jan 1997 03:13:39 -0800) Subject: Re: upgrading texinfo From: asami@CS.Berkeley.EDU (Satoshi Asami) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * install-info [--delete] info-file dir-file * * either adds or with --delete removes the entries for info-file from * dir-file. Ok. Then, we can either (1) add a post-install: target, doing the above, as well as an @exec/@unexec install-info line in pkg/PLIST, or (2) add pkg/INSTALL and pkg/DEINSTALL that do the above, and call pkg/INSTALL from the post-install: target, or (3) add new variables, say, "INFOFILE" and "INFODIR" (defaults to ${PREFIX}/info/dir), and call install-info from bsd.port.mk. However, we haven't implemented on-the-fly PLIST generation (did anyone try the patch I sent out a few days ago?), so with (3), we still need to do something with pkg/* files to make pkg_add happy. * a lot of packages will not have the extra data yet, but its easy to add * and I think it would be worth doing it just to have a ports tree * that installs info-files correctly. you either modify the texinfo * source or the info file itself, either will do. I would think those mods should be patches to texinfo source, the info files are generated during build. (Of course we can do some mv/cat magic in post-build but that seems gross....) Satoshi From owner-freebsd-hackers Tue Jan 7 03:57:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA17598 for hackers-outgoing; Tue, 7 Jan 1997 03:57:07 -0800 (PST) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id DAA17575; Tue, 7 Jan 1997 03:57:02 -0800 (PST) Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) with ESMTP id DAA01200; Tue, 7 Jan 1997 03:56:58 -0800 (PST) From: Josh MacDonald Message-Id: <199701071156.DAA01200@paris.CS.Berkeley.EDU> To: asami@cs.berkeley.edu (Satoshi Asami) cc: freebsd-hackers@freebsd.org, freebsd-ports@freebsd.org Subject: Re: upgrading texinfo In-reply-to: Your message of "Tue, 07 Jan 1997 03:38:20 PST." <199701071138.DAA04094@silvia.HIP.Berkeley.EDU> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1193.852638213.1@paris.CS.Berkeley.EDU> Date: Tue, 07 Jan 1997 03:56:55 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I would think those mods should be patches to texinfo source, the info > files are generated during build. (Of course we can do some mv/cat > magic in post-build but that seems gross....) Actually, I've been looking into this and it seems that its possible to have it default sensibly. In fact, the program's not too smart, but I'll fix it, its a good cause. -josh From owner-freebsd-hackers Tue Jan 7 04:19:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA18517 for hackers-outgoing; Tue, 7 Jan 1997 04:19:39 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA18512; Tue, 7 Jan 1997 04:19:37 -0800 (PST) Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.RWTH-Aachen.DE [134.130.90.6]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id EAA11833 ; Tue, 7 Jan 1997 04:19:35 -0800 (PST) Received: (from thomas@localhost) by ghpc6.ihf.rwth-aachen.de (8.6.12/8.6.9) id NAA07221; Tue, 7 Jan 1997 13:14:12 +0100 From: Thomas Gellekum Message-Id: <199701071214.NAA07221@ghpc6.ihf.rwth-aachen.de> Subject: Re: upgrading texinfo To: jmacd@cs.berkeley.edu (Josh MacDonald) Date: Tue, 7 Jan 1997 13:14:11 +0100 (MET) Cc: asami@cs.berkeley.edu, freebsd-hackers@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG In-Reply-To: <199701071113.DAA01100@paris.CS.Berkeley.EDU> from Josh MacDonald at "Jan 7, 97 03:13:39 am" Organization: Institut f. Hochfrequenztechnik, RWTH Aachen X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Josh MacDonald wrote: > briefly: > > install-info [--delete] info-file dir-file > > either adds or with --delete removes the entries for info-file from > dir-file. Add a variable, like $INFO, similar to MAN?. `INFO=prcs.info' would trigger install-info to be run on /usr/local/info/dir. I hope install-info only needs the master info file? tg From owner-freebsd-hackers Tue Jan 7 04:48:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA20169 for hackers-outgoing; Tue, 7 Jan 1997 04:48:04 -0800 (PST) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA20134 for ; Tue, 7 Jan 1997 04:48:01 -0800 (PST) Received: from hda.hda.com (ip48-max1-fitch.ziplink.net) by mail.crl.com with SMTP id AA19610 (5.65c/IDA-1.5 for ); Tue, 7 Jan 1997 04:47:56 -0800 Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id HAA02180; Tue, 7 Jan 1997 07:41:07 -0500 From: Peter Dufault Message-Id: <199701071241.HAA02180@hda.hda.com> Subject: Re: mmap() updates...how often? In-Reply-To: from The Hermit Hacker at "Jan 7, 97 06:18:20 am" To: scrappy@hub.org (The Hermit Hacker) Date: Tue, 7 Jan 1997 07:41:06 -0500 (EST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Not quite sure how to word this one, but how often does > an mmap() region get updated, in so far as client processes seeing > the data that the server process writes to it? > > The reason I'm asking is that I have a program that is using > mmap() to pass frames from a central server to client processes. The > central server is writing, on average, 20frames/sec to the mmap()'d > region, and after each write, it sets a counter, also mmap()'d, that > the client uses as, more or less, a position indicator. I do something similar, running a simulation that puts a simulation frame in a shared region and then writes a token to a simulation pipeline to synchronize the stages of the pipeline. I don't use msync() and haven't had any funny problems. One difference may be that my entire pipeline is synchronized (each stage passes the token along until it comes back to the originator) since there is ordering in the stages. I'm sure you're using MAP_SHARED. -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-hackers Tue Jan 7 04:49:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA20271 for hackers-outgoing; Tue, 7 Jan 1997 04:49:27 -0800 (PST) Received: from hda.hda.com (ip48-max1-fitch.ziplink.net [199.232.245.48]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA20266 for ; Tue, 7 Jan 1997 04:49:24 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id HAA02203; Tue, 7 Jan 1997 07:45:15 -0500 From: Peter Dufault Message-Id: <199701071245.HAA02203@hda.hda.com> Subject: Re: mmap() updates...how often? In-Reply-To: from The Hermit Hacker at "Jan 7, 97 06:18:20 am" To: scrappy@hub.org (The Hermit Hacker) Date: Tue, 7 Jan 1997 07:45:14 -0500 (EST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Hi... > > Not quite sure how to word this one, but how often does > an mmap() region get updated, in so far as client processes seeing > the data that the server process writes to it? (You see 20 frames pass before the client process runs) Duh. Ignore my previous message - I should read carefully before writing. You're seeing the scheduling granularity. The originator process is running for twenty frames before its slice is taken away. You need to do something to let those clients run, or better, give the SMP folk a workout. See my last message about passing a token around to ensure everyone runs. -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-hackers Tue Jan 7 06:04:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA23217 for hackers-outgoing; Tue, 7 Jan 1997 06:04:13 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA23205 for ; Tue, 7 Jan 1997 06:04:03 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id JAA05460; Tue, 7 Jan 1997 09:03:32 -0500 (EST) From: "John S. Dyson" Message-Id: <199701071403.JAA05460@dyson.iquest.net> Subject: Re: mmap() updates...how often? To: dufault@hda.com (Peter Dufault) Date: Tue, 7 Jan 1997 09:03:32 -0500 (EST) Cc: scrappy@hub.org, hackers@FreeBSD.ORG In-Reply-To: <199701071241.HAA02180@hda.hda.com> from "Peter Dufault" at Jan 7, 97 07:41:06 am X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Not quite sure how to word this one, but how often does > > an mmap() region get updated, in so far as client processes seeing > > the data that the server process writes to it? > > > > The reason I'm asking is that I have a program that is using > > mmap() to pass frames from a central server to client processes. The > > central server is writing, on average, 20frames/sec to the mmap()'d > > region, and after each write, it sets a counter, also mmap()'d, that > > the client uses as, more or less, a position indicator. > > I do something similar, running a simulation that puts a simulation > frame in a shared region and then writes a token to a simulation > pipeline to synchronize the stages of the pipeline. I don't use > msync() and haven't had any funny problems. One difference may be > that my entire pipeline is synchronized (each stage passes the > token along until it comes back to the originator) since there is > ordering in the stages. > > I'm sure you're using MAP_SHARED. > I would think that the problem is that you have a process dumping data into the mmapped region? And another looking at it? I think that you need to wake-up the consumer process for every frame (somehow -- perhaps with sending a message through a pipe or SYSVSEM???) If you don't do that, then you'll simply be dependent on the process scheduler -- and that can do almost ANYTHING to you. John From owner-freebsd-hackers Tue Jan 7 06:14:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA23514 for hackers-outgoing; Tue, 7 Jan 1997 06:14:53 -0800 (PST) Received: from nimbus.superior.net (root@nimbus.superior.net [206.153.96.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA23509 for ; Tue, 7 Jan 1997 06:14:51 -0800 (PST) Received: (from exidor@localhost) by nimbus.superior.net (8.7.6/8.7.5) id JAA18773; Tue, 7 Jan 1997 09:14:32 -0500 (EST) Message-Id: <199701071414.JAA18773@nimbus.superior.net> Date: Tue, 7 Jan 1997 09:14:32 -0500 From: exidor@superior.net (Christopher Masto) To: joed@ksu.edu (Joe Diehl) Cc: tom@sdf.com (Tom Samplonius), hackers@FreeBSD.ORG Subject: Re: adduser script References: X-Mailer: Mutt 0.48.1 Mime-Version: 1.0 In-Reply-To: ; from Joe Diehl on Jan 7, 1997 01:55:12 -0600 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Joe Diehl writes: > > > Many moons ago there was discussion on -hackers about the perl adduser > > > script and what to do with it. What every happened with that discussion, > > > and/or is there any perl work that needs to be done on it? > > Yes, the script has existed at least since 2.0.5-ALPHA (which is the first > version that could handle LBA translations)... I believe the conversation > consisted more of the lines that the script needing modifying in some way, > but the general perl knowledge pool was relatively thin. I'm not sure, it's > been a while since that conversation took place and my memory is fairly hazy. I would be interested in seeing a standalone version of something similar to the 2.2 /stand/sysinstall's "User Maintenance". Of course, it would have a few changes. I meant to work on this myself, but I don't forsee having much time for it. -- Christopher Masto . . . . Superior Net Support: support@superior.net chris@masto.com . . . . . Masto Consulting: info@masto.com On Poultry Inspectors, little-known importance of: The crime bill passed by the Senate would reinstate the Federal death penalty for certain violent crimes: assassinating the President; hijacking an airliner; and murdering a government poultry inspector. - Knight Ridder News Service dispatch. From owner-freebsd-hackers Tue Jan 7 08:29:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA28493 for hackers-outgoing; Tue, 7 Jan 1997 08:29:43 -0800 (PST) Received: from interlink.ReyMoreno.net.co ([205.218.236.10]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA28415; Tue, 7 Jan 1997 08:29:27 -0800 (PST) Received: from [205.218.237.166] (windows.reymoreno.net.co [205.218.237.166]) by interlink.ReyMoreno.net.co (8.6.11/8.6.9) with SMTP id LAA18963; Tue, 7 Jan 1997 11:28:51 -0800 Message-Id: <199701071928.LAA18963@interlink.ReyMoreno.net.co> To: "Mike O'Brien" , "Jonathan M. Bresler" Subject: Re: Usenix FreeBSD BoF when? Date: Tue, 07 Jan 97 11:32:12 -0500 From: Mauricio Calderòn X-Mailer: e-mailMCI v2.3 CC: "Mike O'Brien" , Julian Elischer , "hackers@freefall.freebsd.org" , "chat@freefall.freebsd.org" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk -- [ From: Mauricio Calderòn * EMC.Ver #2.3 ] -- Unsubscribe someone please. I have tried unsubscribe with majordomo but I´m still receiving messages. Rgds, Mauricio Calderon -------- REPLY, Original message follows -------- Date: Monday, 06-Jan-97 02:47 PM From: Mike O'Brien \ Internet: (obrien@antares.aero.org) To: Jonathan M. Bresler \ Internet: (jmb@freefall.freebsd.org) cc: Mike O'Brien \ Internet: (obrien@antares.aero.org) cc: Julian Elischer \ Internet: (julian@whistle.com) cc: hackers@freefall.freebsd.org \ Internet: (hackers@freefall.freebsd.org) cc: chat@freefall.freebsd.org \ Internet: (chat@freefall.freebsd.org) Subject: Re: Usenix FreeBSD BoF when? > thanks, will we be see you at usenix? Yep, I'll be there from Tuesday evening on. -------- REPLY, End of original message -------- From owner-freebsd-hackers Tue Jan 7 09:33:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA00694 for hackers-outgoing; Tue, 7 Jan 1997 09:33:18 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA00687 for ; Tue, 7 Jan 1997 09:33:14 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id SAA01164; Tue, 7 Jan 1997 18:32:36 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id SAA13030; Tue, 7 Jan 1997 18:32:07 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.4/keltia-uucp-2.9) id HAA13205; Tue, 7 Jan 1997 07:02:23 +0100 (CET) Message-ID: Date: Tue, 7 Jan 1997 07:02:23 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: jdp@polstra.com (John Polstra) Cc: hackers@freebsd.org Subject: Re: ld with -R weirdness References: <199701062345.PAA10680@austin.polstra.com> X-Mailer: Mutt 0.55.15 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2837 In-Reply-To: <199701062345.PAA10680@austin.polstra.com>; from John Polstra on Jan 6, 1997 15:45:34 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to John Polstra: > For security reasons, LD_LIBRARY_PATH is ignored for setuid and setgid > programs. Except that when I'm testing this, the program is not yet installed and still belongs to me: -rwxr-xr-x 1 roberto staff 51047 Jan 7 01:53 suidperl* so it should respect LD_LIBRARY_PATH. > If you specify the library name explicitly ("libperl.so.3.19"), it is > recorded as a direct reference to that particular file, and no searching > is done. Directories are searched only if you specify the library > generically ("-lperl"). It is recorded in a wrong way IMHO Shared object dependencies: -llibperl.so.3.19 version 0.0 -lm version 2.0 -lc version 3.0 -lcrypt version 2.0 Even if it were recorded as libperl.so.3.19, it should be able to find it with LD_LIBRARY_PATH no ? > I should mention one other thing. If LD(1) is to be believed, there > should be no space between ld's "-R" option and the > "record-library-search-path" that follows it. (Just like the "-L" > option.) You probably should remove the "," after "-Wl,-R". It seems to work the same way with and without the ','. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #33: Sat Dec 21 12:57:17 CET 1996 From owner-freebsd-hackers Tue Jan 7 09:50:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA01502 for hackers-outgoing; Tue, 7 Jan 1997 09:50:32 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA01489 for ; Tue, 7 Jan 1997 09:50:25 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.7.6/8.7.3) with SMTP id JAA27674; Tue, 7 Jan 1997 09:40:21 -0800 (PST) Date: Tue, 7 Jan 1997 09:40:18 -0800 (PST) From: Jaye Mathisen To: Terry Lambert cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@freebsd.org, henrich@crh.cl.msu.edu Subject: INN redux... Re: MMAP Troubles (Joerg?) In-Reply-To: <199701062235.PAA12791@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As I was a whiner about this problem several months ago, let me step in now by saying that INN 1.5.1 with the MSYNC stuff that was added in, has been running just peachy under FreeBSD-current (3.0), with MMAP enabled. I have had none of the problems that I had before under I think 2.1. Methinks (and other comments bear this out), that the addition of the MSYNC code seems to fix the problem. Perhaps the possibility for the condition still exists, but it doesn't seem to be happening on a moderately busy server. From owner-freebsd-hackers Tue Jan 7 10:00:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA01904 for hackers-outgoing; Tue, 7 Jan 1997 10:00:55 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA01899 for ; Tue, 7 Jan 1997 10:00:53 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) with ESMTP id KAA16413; Tue, 7 Jan 1997 10:00:06 -0800 (PST) Message-Id: <199701071800.KAA16413@austin.polstra.com> To: roberto@keltia.freenix.fr (Ollivier Robert) cc: hackers@freebsd.org Subject: Re: ld with -R weirdness In-reply-to: Your message of "Tue, 07 Jan 1997 07:02:23 +0100." References: <199701062345.PAA10680@austin.polstra.com> Date: Tue, 07 Jan 1997 10:00:06 -0800 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > For security reasons, LD_LIBRARY_PATH is ignored for setuid and setgid > > programs. > > Except that when I'm testing this, the program is not yet installed and > still belongs to me: OK, in that case LD_LIBRARY_PATH is not the problem. The problem is that you specified the library as "libperl.so.3.19" instead of "-lperl". > > If you specify the library name explicitly ("libperl.so.3.19"), it is > > recorded as a direct reference to that particular file, and no searching > > is done. Directories are searched only if you specify the library > > generically ("-lperl"). > > It is recorded in a wrong way IMHO > > Shared object dependencies: > -llibperl.so.3.19 version 0.0 > -lm version 2.0 > -lc version 3.0 > -lcrypt version 2.0 It is recorded correctly, but "ldd -v" is printing it out incorrectly. That is a bug in ldd. I'll fix it as soon as I have time. To help me remember, it might be a good idea to send a PR about it. > Even if it were recorded as libperl.so.3.19, it should be able to > find it with LD_LIBRARY_PATH no ? No. The linker distinguishes between libraries specified as "-lxxx" and libraries specified as file names. Each shared object dependency has a flag "sod_library" that is set only if the library was specified as "-lxxx". (See LINK(5) and "/usr/include/link.h".) The search rules are used only for those libraries. The others are interpreted as pathnames. If you want the dynamic linker to search for a library, you must specify it as "-lxxx". > > I should mention one other thing. If LD(1) is to be believed, there > > should be no space between ld's "-R" option and the > > "record-library-search-path" that follows it. (Just like the "-L" > > option.) You probably should remove the "," after "-Wl,-R". > > It seems to work the same way with and without the ','. Yes, but it you use it contrary to the manual page, there is no guarantee it will still work next week, or even tomorrow. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Tue Jan 7 10:10:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA02312 for hackers-outgoing; Tue, 7 Jan 1997 10:10:14 -0800 (PST) Received: from deliverator.io.com (deliverator.io.com [199.170.88.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA02307 for ; Tue, 7 Jan 1997 10:10:11 -0800 (PST) Received: from bermuda.io.com (sszabo@bermuda.io.com [199.170.88.7]) by deliverator.io.com (8.8.4/8.8.4) with ESMTP id LAA29622; Tue, 7 Jan 1997 11:26:13 -0600 (CST) Received: from localhost (sszabo@localhost) by bermuda.io.com (8.8.4/8.8.4) with SMTP id LAA02357; Tue, 7 Jan 1997 11:26:09 -0600 (CST) X-Authentication-Warning: bermuda.io.com: sszabo owned process doing -bs Date: Tue, 7 Jan 1997 11:26:09 -0600 (CST) From: Stephan Szabo To: Tom Samplonius cc: freebsd-hackers@freebsd.org Subject: Re: Question about ypbind In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 6 Jan 1997, Tom Samplonius wrote: > > On Mon, 6 Jan 1997, Stephan Szabo wrote: > > > > > We have been attempting to install NIS on a FreeBSD 2.1.5R system > > and have run into a problem with ypbind. When it is run, it dies on a > > SIGSEGV. Going through gdb a bit gave us the following: > > Program received signal SIGSEGV, Segmentation fault. > > [rest left off for brevity] > > Works fine for me. > > What params are you running ypbind with? What kind of server is ypbind > binding too (or trying to bind to)? Originally we were running ypbind -s, and then ypbind with no parameters to see if that would work. The server is another FreeBSD 2.1.5R system. The strange thing was that it had worked for a little while, and then stopped working, but no changes were made to our knowledge to the configuration of either machine. Stephan Szabo From owner-freebsd-hackers Tue Jan 7 10:56:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA04475 for hackers-outgoing; Tue, 7 Jan 1997 10:56:20 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA04470 for ; Tue, 7 Jan 1997 10:56:18 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id NAA11433; Tue, 7 Jan 1997 13:52:18 -0500 (EST) From: Charles Henrich Message-Id: <199701071852.NAA11433@crh.cl.msu.edu> Subject: Re: INN redux... Re: MMAP Troubles (Joerg?) To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Tue, 7 Jan 1997 13:52:18 -0500 (EST) Cc: terry@lambert.org, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@freebsd.org In-Reply-To: from Jaye Mathisen at "Jan 7, 97 09:40:18 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > As I was a whiner about this problem several months ago, let me step in > now by saying that INN 1.5.1 with the MSYNC stuff that was added in, has > been running just peachy under FreeBSD-current (3.0), with MMAP enabled. > > I have had none of the problems that I had before under I think 2.1. > > Methinks (and other comments bear this out), that the addition of the > MSYNC code seems to fix the problem. > > Perhaps the possibility for the condition still exists, but it doesn't > seem to be happening on a moderately busy server. I've been running with msync on a 2.2-BETA system thats been not too busy and the problem hasnt reoccured. I'll let everyone know if it does when I go into large production with this sytem. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Tue Jan 7 11:15:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA05298 for hackers-outgoing; Tue, 7 Jan 1997 11:15:01 -0800 (PST) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA05283 for ; Tue, 7 Jan 1997 11:14:46 -0800 (PST) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id TAA07646 for hackers@freebsd.org; Tue, 7 Jan 1997 19:31:16 +0100 From: Luigi Rizzo Message-Id: <199701071831.TAA07646@labinfo.iet.unipi.it> Subject: FEC techniques and a C implementation To: hackers@freebsd.org Date: Tue, 7 Jan 1997 19:31:16 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If someone is interested, I have written a C implementation of an erasure code which I believe to be reasonably flexible and efficient for use within TCP/UDP/IP-based protocols. Typical encoding/decoding speeds on a Pentium133 are in the 1..10 MB/s range depending on the actual parameters. This encoding can be used both to reduce the experienced loss rate on unicast/multicast communications, or to build reliable multicast applications (e.g. multi-FTP, parallel download of software, etc.) A brief description with pointers to the source code (very short) and a draft paper describing the implementation, its performance and possible applications is available at the following URL: http://www.iet.unipi.it/~luigi/fec.html Comments suggestions and bug reports are welcome. Also, suggestions for useful applications related to FreeBSD or its distribution are sought. Cheers Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Tue Jan 7 12:19:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA08837 for hackers-outgoing; Tue, 7 Jan 1997 12:19:10 -0800 (PST) Received: from sunbeam.csusb.edu (sunbeam.csusb.edu [139.182.10.13]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA08832 for ; Tue, 7 Jan 1997 12:19:07 -0800 (PST) Received: (from rmallory@localhost) by sunbeam.csusb.edu (8.8.4/8.7.3) id MAA01688; Tue, 7 Jan 1997 12:18:50 -0800 (PST) From: Rob Mallory Message-Id: <199701072018.MAA01688@sunbeam.csusb.edu> Subject: Re: Usenix FreeBSD BoF when? To: julian@whistle.com (Julian Elischer) Date: Tue, 7 Jan 1997 12:18:49 -0800 (PST) Cc: hackers@freefall.freebsd.org In-Reply-To: <32D19981.15FB7483@whistle.com> from "Julian Elischer" at Jan 6, 97 04:32:01 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Mike O'Brien wrote: > > > > > thanks, will we be see you at usenix? > > > > Yep, I'll be there from Tuesday evening on. > Julian then replied: > As will I (armed with job descriptions to post :) > Oooooo... Yuk! Are you still working for the Evil Bill Gates?? -- rob@Qualcomm.com now thats a place to work...;) From owner-freebsd-hackers Tue Jan 7 12:38:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA10060 for hackers-outgoing; Tue, 7 Jan 1997 12:38:07 -0800 (PST) Received: from sunbeam.csusb.edu (sunbeam.csusb.edu [139.182.10.13]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA09860 for ; Tue, 7 Jan 1997 12:34:49 -0800 (PST) Received: (from rmallory@localhost) by sunbeam.csusb.edu (8.8.4/8.7.3) id MAA01722 for hackers@Freebsd.org; Tue, 7 Jan 1997 12:34:27 -0800 (PST) From: Rob Mallory Message-Id: <199701072034.MAA01722@sunbeam.csusb.edu> Subject: Coda-4.01 filesystem To: hackers@Freebsd.org Date: Tue, 7 Jan 1997 12:34:27 -0800 (PST) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@Freebsd.org X-Loop: FreeBSD.org Precedence: bulk I noticed there was a newly tagged "release?" of coda under /afs/cs.cmu.edu/project/coda-nbsd-port. I recommisioned a 2GB drive and installed netbsd-currnet in another attempt to get this thing running. I'll have to spend another week with it..:( My goal is to get it ported to freebsd, but it looks as there is much more work to port to freebsd as there is at getting it running on netbsd... Has anyone been following the coda-filesystem development?? Anyone done any work importing it into FreeBSD? Does anyone care? If you are not aware of its features, search for the coda- web-page at cs.cmu.edu; Coda is afs-v2 taken a couple steps further, with disconnected filesystem operations for mobile computing... If you don't have access to AFS, I can upload a 16M tarball.. -Rob Mallory From owner-freebsd-hackers Tue Jan 7 13:01:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA11215 for hackers-outgoing; Tue, 7 Jan 1997 13:01:59 -0800 (PST) Received: from profane.iq.org (profane.iq.org [203.4.184.217]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA11209 for ; Tue, 7 Jan 1997 13:01:36 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id IAA00552 for hackers@freebsd.org; Wed, 8 Jan 1997 08:00:27 +1100 (EST) From: Julian Assange Message-Id: <199701072100.IAA00552@profane.iq.org> Subject: Re: ipfws To: hackers@freebsd.org Date: Wed, 8 Jan 1997 08:00:27 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Avalon, I did think about the domain issues before implimenting socket credentials. The bind() wormholing is really only weakly coupled, but the socket credential routines are tightly coupled, and so they must be if you want to get the degree of control and efficiency out of them that I have. I considered a scheme that used only the information from socket() bind() and connect(), but rejected it because its lack of fine control and ability to eliminate covert channels in connectionless, broadcast, multicast, routing, icmp, raw sockets etc without eliminating that form of communication entirely. In terms of grammer, I agree that perhaps the bind() list could be viewed as a seperate, given its non use of the destination address/port. On the other hand the grammers are close enough that I'm not so sure it is wise to seperate them entirely. Perhaps a change from "accept" to "bind", a lexical trigger that the "to" keyword and argument is not required. In anyevent, if you port ipfilter to -current, I promise to port socket and bind credentials to ipfilter. Cheers, Julian. From owner-freebsd-hackers Tue Jan 7 14:03:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA14271 for hackers-outgoing; Tue, 7 Jan 1997 14:03:39 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA14266 for ; Tue, 7 Jan 1997 14:03:36 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id OAA09855 for ; Tue, 7 Jan 1997 14:04:15 -0800 (PST) Received: (qmail 5822 invoked by uid 110); 7 Jan 1997 22:03:00 -0000 Message-ID: <19970107220300.5821.qmail@suburbia.net> Subject: Re: w problem In-Reply-To: from Andreas Kohout at "Jan 7, 97 08:43:00 pm" To: shanee@rabbit.augusta.de (Andreas Kohout) Date: Wed, 8 Jan 1997 09:03:00 +1100 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > 7:04PM up 1:10, 2 users, load averages: 0.50, 0.58, 0.58 > > USER TTY FROM LOGIN@ IDLE WHAT > > sos v0 - 5:55PM 1:09 xinit /u1/home/sos/.xinitrc > > ÝÏ2ttyp1 - 01Jan70 1:09 - > > I have had the same problem, but after recompile of rxvt it works again ... Was this utmp change entirely necessary? From now on, xf86 has to produce two versions of its binary distribution, pre and post utmp mangle. It seems to me that a little more discussion could have gone into this. From owner-freebsd-hackers Tue Jan 7 14:43:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA16741 for hackers-outgoing; Tue, 7 Jan 1997 14:43:09 -0800 (PST) Received: from profane.iq.org (profane.iq.org [203.4.184.217]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA16727 for ; Tue, 7 Jan 1997 14:42:45 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id JAA17826 for hackers@freebsd.org; Wed, 8 Jan 1997 09:41:31 +1100 (EST) From: Julian Assange Message-Id: <199701072241.JAA17826@profane.iq.org> Subject: #include file xref philosophy To: hackers@freebsd.org Date: Wed, 8 Jan 1997 09:41:30 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What is the -current philosophy on intra #include file dependencies? Is there any reason for not following the posix line and having include files resolve all their own dependencies? I'm talking about things like needing the code that includes it, include before hand. Appart from portability issues, which I am increasingly encountering, I find the idea that user developed .c code must magically "know" what each /usr/include/* file needs and in what order very ugly and ecapsulation breaking. Moving towards self-resolving is of course backwards compatible. Can we agree to do this for /usr/include/*? Cheers, Julian. From owner-freebsd-hackers Tue Jan 7 14:52:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA17473 for hackers-outgoing; Tue, 7 Jan 1997 14:52:46 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA17425 for ; Tue, 7 Jan 1997 14:52:22 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA26883; Tue, 7 Jan 1997 23:51:16 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA00287; Tue, 7 Jan 1997 23:51:16 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id XAA10387; Tue, 7 Jan 1997 23:28:13 +0100 (MET) Message-ID: Date: Tue, 7 Jan 1997 23:28:13 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: mrcpu@cdsnet.net (Jaye Mathisen) Cc: hackers@FreeBSD.ORG Subject: Re: noatime, one more time, the last time. References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Jaye Mathisen on Jan 6, 1997 14:26:28 -0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jaye Mathisen wrote: > So WTF did the noatime go? Maybe it's ccd-related? uriah # mount -u -o noatime /tmp uriah # mount ... /dev/sd1h on /tmp (local, noatime) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jan 7 14:59:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA18074 for hackers-outgoing; Tue, 7 Jan 1997 14:59:47 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA17702 for ; Tue, 7 Jan 1997 14:57:06 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA26907; Tue, 7 Jan 1997 23:51:43 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA00293; Tue, 7 Jan 1997 23:51:43 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id XAA10425; Tue, 7 Jan 1997 23:44:28 +0100 (MET) Message-ID: Date: Tue, 7 Jan 1997 23:44:28 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: jdp@polstra.com (John Polstra) Cc: hackers@freebsd.org Subject: Re: ld with -R weirdness References: <199701062345.PAA10680@austin.polstra.com> <199701071800.KAA16413@austin.polstra.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701071800.KAA16413@austin.polstra.com>; from John Polstra on Jan 7, 1997 10:00:06 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As John Polstra wrote: > > > I should mention one other thing. If LD(1) is to be believed, there > > > should be no space between ld's "-R" option and the > > > "record-library-search-path" that follows it. > > It seems to work the same way with and without the ','. > > Yes, but it you use it contrary to the manual page, there is no > guarantee it will still work next week, or even tomorrow. General Posix rules mandate the space between an option and the option arguments. However, applications are requested (or even required) to tolerate a missing space in this position. The `classic' SysV C compilers and linkers that required -Ifoo and -Lbar without an intervening space (as well as our mkdep, and maybe some other tools) are not Posix-conformant. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jan 7 15:04:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA18864 for hackers-outgoing; Tue, 7 Jan 1997 15:04:53 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA18848 for ; Tue, 7 Jan 1997 15:04:47 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id PAA10755 for ; Tue, 7 Jan 1997 15:05:34 -0800 (PST) Received: (qmail 6677 invoked by uid 110); 7 Jan 1997 23:04:06 -0000 Message-ID: <19970107230406.6676.qmail@suburbia.net> Subject: Re: FreeBSD as a cleanwall In-Reply-To: <199701072210.AAA13560@katiska.clinet.fi> from Heikki Suonsivu at "Jan 8, 97 00:10:32 am" To: hsu@clinet.fi (Heikki Suonsivu) Date: Wed, 8 Jan 1997 10:04:06 +1100 (EST) Cc: hackers@freebsd.org, security@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Is there anything which ipfw does but bpf does not, other than better > performance ? > > How much more bpf consumes cpu than ipfw, per packet filtered, per rule ? > > -- > Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi > mobile +358-40-5519679 work +358-9-43542270 fax -4555276 > The two are not really compariable. If I was going to write a packet filtering system from scratch, I'd take most of Darren's code and add: query optimisation and grammer from libpcap fast masking from RMON my socket credential code Bpf primarily exists to cut down kernel<->user space talk, and I don't think it is useful elsewhere, except as a slow portable low-level substrate. Some RMON (one?) system(s) have support for bpf code, but except for ip/tcp options and quantitative decisions, fast masks work very well. Cheers, Julian From owner-freebsd-hackers Tue Jan 7 15:14:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA20146 for hackers-outgoing; Tue, 7 Jan 1997 15:14:07 -0800 (PST) Received: from csla.csl.sri.com (csla.csl.sri.com [192.12.33.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA20137 for ; Tue, 7 Jan 1997 15:14:01 -0800 (PST) Received: from impulse.csl.sri.com (impulse.csl.sri.com [130.107.15.11]) by csla.csl.sri.com (8.7.3/8.7.3) with ESMTP id PAA20910 for ; Tue, 7 Jan 1997 15:10:51 -0800 (PST) Received: from impulse.csl.sri.com (localhost [127.0.0.1]) by impulse.csl.sri.com (8.7.3/8.7.3) with ESMTP id PAA26734 for ; Tue, 7 Jan 1997 15:12:44 -0800 (PST) Message-Id: <199701072312.PAA26734@impulse.csl.sri.com> To: hackers@freebsd.org Subject: Re: New motherboard breaks tape drive In-reply-to: Your message of "Mon, 06 Jan 1997 17:04:06 CST." <199701062304.XAA10197@right.PCS> Date: Tue, 07 Jan 1997 15:12:39 -0800 From: Fred Gilham Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jonathan Lemon writes: ---------------------------------------- Heh. When I bought my EISA machine about 4 years back, I was worried that their motherboard wouldn't be able to cache any memory above 16M. So I called them up and asked them how many address lines they had going to their tag cache - nobody in their tech department could even answer my question. So I finally had them fax over the damned schematics and looked at them myself. Incompetents, sigh. (Yes, they only had 24 address lines, and I wanted to put in 32M back then). ---------------------------------------- I went through something like this. I have an EISA/VLB motherboard; I think it's a NICE motherboard but it has a SiS chipset. I tried to upgrade it from 16 to 32M. FreeBSD crashed every time, fairly quickly, with or without cache turned on. Windows 95 seemed to run OK, so at first I thought it was one of those `FreeBSD works the memory system harder' kind of problems---until I purposely tried loading lots of applications at the same time under Windows 95, whereupon I finally got it to crash there too. (In the meantime I discovered that Windows 95 slows down on a per-application-loaded basis, even if the applications are not doing anything.) Sometimes it gave memory parity errors but sometimes it just locked up. I finally got a running system by turning off parity checks on memory. It's been solid ever since, though I shudder to think what will happen if the memory fails. -Fred Gilham gilham@csl.sri.com From owner-freebsd-hackers Tue Jan 7 15:22:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA21362 for hackers-outgoing; Tue, 7 Jan 1997 15:22:55 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA21343 for ; Tue, 7 Jan 1997 15:22:50 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA28323; Wed, 8 Jan 1997 00:21:22 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA00612; Wed, 8 Jan 1997 00:21:21 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id AAA10524; Wed, 8 Jan 1997 00:12:48 +0100 (MET) Message-ID: Date: Wed, 8 Jan 1997 00:12:47 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: exidor@superior.net (Christopher Masto) Subject: Re: adduser script References: <199701071414.JAA18773@nimbus.superior.net> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701071414.JAA18773@nimbus.superior.net>; from Christopher Masto on Jan 7, 1997 09:14:32 -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Christopher Masto wrote: > I would be interested in seeing a standalone version of something similar > to the 2.2 /stand/sysinstall's "User Maintenance". Of course, it would > have a few changes. I meant to work on this myself, but I don't forsee > having much time for it. I also thought of extending this menu eventually. Right now, you should be able to run /stand/sysinstall -addGroup or -addUser. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jan 7 15:47:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA24714 for hackers-outgoing; Tue, 7 Jan 1997 15:47:54 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA24693 for ; Tue, 7 Jan 1997 15:47:46 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id KAA11935; Wed, 8 Jan 1997 10:16:35 +1030 (CST) From: Michael Smith Message-Id: <199701072346.KAA11935@genesis.atrad.adelaide.edu.au> Subject: Re: w problem In-Reply-To: <19970107220300.5821.qmail@suburbia.net> from "proff@suburbia.net" at "Jan 8, 97 09:03:00 am" To: proff@suburbia.net Date: Wed, 8 Jan 1997 10:16:34 +1030 (CST) Cc: shanee@rabbit.augusta.de, hackers@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk proff@suburbia.net stands accused of saying: > > Was this utmp change entirely necessary? From now on, xf86 has to produce two > versions of its binary distribution, pre and post utmp mangle. No, they produce a single version linked against libutil. > It seems to me that a little more discussion could have gone into this. More than the 18 months or so that have already ensued? You've got to be kidding. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Jan 7 16:16:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA27321 for hackers-outgoing; Tue, 7 Jan 1997 16:16:58 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA27315 for ; Tue, 7 Jan 1997 16:16:55 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA15234; Tue, 7 Jan 1997 17:06:47 -0700 From: Terry Lambert Message-Id: <199701080006.RAA15234@phaeton.artisoft.com> Subject: Re: mmap() updates...how often? To: scrappy@hub.org (The Hermit Hacker) Date: Tue, 7 Jan 1997 17:06:47 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "The Hermit Hacker" at Jan 7, 97 06:18:20 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Not quite sure how to word this one, but how often does > an mmap() region get updated, in so far as client processes seeing > the data that the server process writes to it? If it's MAP_SHARED, then it is updated instantaneously... that is, it's the same physical memory mapped into both processes. > The reason I'm asking is that I have a program that is using > mmap() to pass frames from a central server to client processes. The > central server is writing, on average, 20frames/sec to the mmap()'d > region, and after each write, it sets a counter, also mmap()'d, that > the client uses as, more or less, a position indicator. > > The problem is that the client seems only to see every 20th > frame, as far as the indicator is concerned. I would expect some > "skippage" between client reads (ie. server wrote 2 frames before > the client got a chance to check the indicator again), but it seems > to be *very* consistent at 20... You need to notify the client when the data is available, and not reuse the region until the client has used it. The context switch rate for a compute intensive task is 100HZ or once every 10ms. Most likely, the client isn't getting a chance to run, and the server is monopolizing the CPU. > Not being quite sure of what other data I can provide, does > anyone have any suggestions on what I'm seeing? Since its memory > mapped, I would have made the assumption that changes to the data > would be seen instantaneously by the client, but either I'm missing > something in my code (staring at it too long does that) or I'm once > more missing something with mmap() How are you making sure that the server does not reuse the memory region before the client displays it? If the client is an X client, are you using "XSync( Xdisplay);" to make sure the X servr is not "optimizing" away your screen updates? Other than those, no guesses... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jan 7 16:21:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA27696 for hackers-outgoing; Tue, 7 Jan 1997 16:21:41 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA27663 for ; Tue, 7 Jan 1997 16:21:30 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id BAA01878 for ; Wed, 8 Jan 1997 01:21:22 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA02626 for hackers@freebsd.org; Wed, 8 Jan 1997 01:21:21 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id BAA10901; Wed, 8 Jan 1997 01:19:11 +0100 (MET) Message-ID: Date: Wed, 8 Jan 1997 01:19:11 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: #include file xref philosophy References: <199701072241.JAA17826@profane.iq.org> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701072241.JAA17826@profane.iq.org>; from Julian Assange on Jan 8, 1997 09:41:30 +1100 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Julian Assange wrote: > What is the -current philosophy on intra #include file dependencies? > > Is there any reason for not following the posix line and having > include files resolve all their own dependencies? I'm talking about > things like needing the code that includes it, include > before hand. IIRC, Bruce once mentioned that Posix allows it to require the inclusion of (xor another which i eventually forgot) before other things. Either way, the corresponding man pages should at least mention the required include files, so your complaint about ``magical knowledge'' would not be true. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jan 7 16:23:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA27867 for hackers-outgoing; Tue, 7 Jan 1997 16:23:22 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA27858 for ; Tue, 7 Jan 1997 16:23:14 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) with ESMTP id QAA19852 for ; Tue, 7 Jan 1997 16:23:13 -0800 (PST) Message-Id: <199701080023.QAA19852@austin.polstra.com> To: freebsd-hackers@freebsd.org Subject: CVSup 14.1 is now available Date: Tue, 07 Jan 1997 16:23:12 -0800 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Announcing CVSup 14.1 --------------------- Release 14.1 of CVSup, the CVS-aware network distribution system, is now available. Where to Get CVSup ------------------ CVSup is free software. It is available from the following FTP sites: ftp://freefall.freebsd.org/pub/CVSup/ ftp://ftp.polstra.com/pub/FreeBSD/CVSup/ (slow; avoid if possible) Full sources as well as FreeBSD binaries are available: cvsup-bin-14.1.tar.gz FreeBSD static binaries for the client cvsupd-bin-14.1.tar.gz FreeBSD static binaries for the server cvsup-14.1.tar.gz Sources ** The MD5 signatures for these files are: MD5 (cvsup-bin-14.1.tar.gz) = b06efe8be163f127f5103968f0545067 MD5 (cvsupd-bin-14.1.tar.gz) = 6c822e77db2d8b9179d8c6d4c281acea MD5 (cvsup-14.1.tar.gz) = e131ef39f1cfb5807d9f488b0b3b0691 An updated port will appear in the FreeBSD ports and packages collections soon: Port: ftp://ftp.freebsd.org/pub/FreeBSD/ports-current/net/cvsup/ Package: ftp://ftp.freebsd.org/pub/FreeBSD/packages-current/net/cvsup-14.1.tgz ftp://ftp.freebsd.org/pub/FreeBSD/packages-2.2/net/cvsup-14.1.tgz The FreeBSD package now depends only on the "modula-3-lib" package, a subset of the Modula-3 installation consisting of only the shared libraries. Because of this, you can now install and use the "cvsup" package in a reasonable amount of disk space. The package is much smaller than the statically linked binary distribution, so updates to new versions of CVSup should be more convenient now. The package is the recommended distribution for binary-only users. The static binary distributions may be phased out soon. If you want SOCKS support, you must also install the "modula-3-socks" port or package: Port: ftp://ftp.freebsd.org/pub/FreeBSD/ports-current/lang/modula-3-socks/ Package: ftp://ftp.freebsd.org/pub/FreeBSD/packages-current/lang/modula-3-socks-1.0.tgz ftp://ftp.freebsd.org/pub/FreeBSD/packages-2.2/lang/modula-3-socks-1.0.tgz SOCKS is supported only under FreeBSD, and only with dynamically linked executables. The static binary distributions do not support SOCKS. ** If you wish to build CVSup from the sources, be sure to read the discussion further on in this announcement. Compatibility with Previous Releases ------------------------------------ This release is fully backward-compatible with release 14.0. There are a couple of very minor compatibility issues which could affect a few users upgrading from a release prior to 14.0. Clients: The default for the "base" directory has changed from "/usr" to "/usr/local/etc/cvsup". Practically everybody specifies the base explicitly in their supfiles, so this change will have no impact for most people. If you have been using the default value, you will need to add a line "*default base=/home" to your supfile, or specify "-b /home" on the cvsup command line. Servers: The "hostbase" is no longer taken from the client's supfile. It is now controlled on the server host. On the FreeBSD project, "hostbase=/home" was always used in the past. People operating servers will need to specify "-b /home" on the cvsupd command line to get the same effect. Alternatively, move your server configuration files from "/home" to the new default location, "/usr/local/etc/cvsup". (As before, most of the configuration files appear under a subdirectory named "sup".) What Has Changed Since the Previous Release? -------------------------------------------- For both the client and the server, there is now a "-c collDir" command line option for overriding the name of the subdirectory where the collection information is maintained. The name used to be hard-wired to "sup", and that is still the default. If the client's prefix directory for a collection doesn't exist, it is no longer a fatal error. A warning is produced and the offending collection is skipped, but the others are still processed normally. If the prefix is a symbolic link pointing to "SKIP", the warning is suppressed. Fixed a server problem that caused certain pathological updates in checkout mode to take damned near forever. Fixed a problem that caused fixups to be performed for certain RCS files that were corrupted to begin with. The files had incorrect dates on some revisions, because they had been hacked up by hand. That caused the client to write out the delta texts in the wrong order. Since there was a way to work around this dubious situation, I implemented it. Changed the logic surrounding the time stamp comparisons between files on the client and files on the server, eliminating a miniscule possibility of missed updates. Now, the system can detect it if a file happens to have been modified independently on both the client and the server at exactly the same time. The file is recognized as possibly needing an update, even though its time stamp is the same on the client and the server. Fixed the client's lock file handling ("-l" option) so that the lock remains held during the intervals between retries. Formerly, the lock was released during those intervals, rendering it fairly useless for avoiding multiple stacked up processes from cron jobs. Added a check to make sure it is possible to get the client host's own IP address before starting up the GUI. Formerly, misconfigured hosts (e.g., incorrect host name) would result in a baffling "IP.FatalError" message. Changed the priorities for syslog messages from the server so that messages associated with individual client connections are logged at "info" level rather than "notice". For simple syslog.conf setups, that takes these mostly informational messages out of /var/log/messages, where they caused a lot of clutter. The logging still isn't perfect, as a few more serious messages now also come out at "info" level. Nevertheless, the new situation is an improvement. Added a new "-k" command line option for the client, intended for debugging. This option causes the bad temporary files to be saved for files requiring fixups due to incorrect edits. The fixups are still performed, regardless. Further improved the server's handling of corrupted RCS files. In virtually all circumstances, the server should now be able to issue warnings for corrupted RCS files and carry on with the remaining updates. Beefed up the semantic checking of RCS files, to detect some more pernicious kinds of corruption. Added a "norsync" option which can be specified in the server's "releases" files. It allows the server to disable the use of the rsync algorithm for selected collections and releases. This is beneficial for CVS repositories, where CVSup's "append" updates work better and more efficiently than the rsync algorithm. Added additional server checks of the filenames received from the client, to ensure that the server cannot be spoofed into delivering files from outside its collections. What Is CVSup? -------------- CVSup is a software package for distributing and updating collections of files across a network. CVSup is specifically tailored to distributing CVS repositories. By taking advantage of the special properties of the files contained in CVS repositories, CVSup is able to perform updates much faster than traditional systems. It is especially valuable for people with slow Internet connections. CVSup parses and understands the RCS files making up a CVS repository. When updates occur, CVSup extracts new deltas directly from the RCS files on the server and edits them into the client's RCS files. Likewise, CVSup notes the addition of new symbolic tags to the files on the server and sends only the new tags to the client. CVSup is able to merge new deltas and tags from the server with deltas and tags added locally on the client machine. This makes it possible for the client to check local modifications into his repository without their being obliterated by subsequent updates from the server. Note: Although this feature is fully implemented in CVSup, it will probably not be practical to use it until some small changes have been made to CVS. In addition to distributing the RCS files themselves, CVSup is able to distribute specific checked-out versions. The client can specify a symbolic tag, a date, or both and CVSup will extract the appropriate versions from the server's CVS repository. Checked-out versions do not need to be stored on the server since CVSup can extract any version directly from the CVS repository. If the client has an existing checked-out tree, CVSup will apply the appropriate edits to update the tree or transform it into the requested version. Only the differences between the existing version and the desired version are sent across the network. To update non-RCS files, CVSup uses the highly efficient rsync algorithm, developed by Andrew Tridgell and Paul Mackerras. CVSup uses lightweight processes (threads) to implement a streaming protocol across the network. This completely eliminates the delays associated with the lock-step, request-reply form of communication used by many existing protocols, such as sup and NNTP. Information is transferred at the full available speed of the network in both directions at once. Network latency and server response delays are rendered practically irrelevant. CVSup uses the "zlib" compression package to optionally compress all communications. This provides an additional 65-75% compression, on top of the diff-based compression already built into CVSup. For efficiency, all processing is built into the CVSup package itself. Neither the client nor the server executes any other programs. For further information about how CVSup works, see the "Blurb" document in the CVSup distribution. Using CVSup to Maintain FreeBSD Sources --------------------------------------- CVSup servers are currently running at the following FreeBSD mirror sites: USA: cvsup.freebsd.org cvsup2.freebsd.org cvsup4.freebsd.org Argentina: cvsup.ar.freebsd.org Australia: cvsup.au.freebsd.org Germany: cvsup.de.freebsd.org Japan: cvsup.jp.freebsd.org Netherlands: cvsup.nl.freebsd.org South Africa: cvsup.za.freebsd.org Taiwan: sup.tw.freebsd.org Additional servers are planned to come on-line soon. Using CVSup, you can easily receive or update any of the standard FreeBSD source releases, namely, "cvs", "current", and "stable". The manual page for cvsup(1) describes how to do that. For more detailed instructions, see the FreeBSD Handbook, section 17.2: http://www.freebsd.org/handbook/ Building CVSup from the Sources ------------------------------- CVSup is written in Modula-3, a modern, compiled, object-oriented language. Modula-3 integrates threads, exceptions, and garbage collection, providing an ideal vehicle for this sort of application. Without Modula-3, CVSup would almost certainly not exist today. If you wish to build CVSup from the sources, you will first need to install the free Modula-3 compiler and runtime libraries from DEC SRC. A port is available in the FreeBSD ports collection, in "lang/modula-3". The corresponding package is, of course, available in the packages collection. You will also need version 1.0.4 or later of the "zlib" library. In FreeBSD-2.1.6 and later releases, this library has been incorporated into the system sources, in "src/lib/libz". Prior to that, a FreeBSD port was available in "devel/libz" of the FreeBSD ports collection. For other sources of this library, see the "Install" file. Do not try to use versions earlier than 1.0.4. You will also need Poul-Henning Kamp's "libmd" library. It is a standard library on FreeBSD systems. Portability Issues ------------------ I intend for CVSup to be portable to most POSIX systems. The present release has only been tested under FreeBSD versions 2.1 and later. Primarily because of packaging problems, this release of CVSup probably won't build out-of-the-box on other systems. Among other things, it relies on Poul-Henning Kamp's "libmd" encapsulation of the MD5 subroutines. The library itself is quite portable, but its Makefiles are BSD-specific. There are probably some other FreeBSD-specific things in CVSup that have not been found yet. Anybody who succeeds in porting CVSup to other systems is encouraged to send his changes to . As long as the changes are reasonably palatable, they will be incorporated into future CVSup releases. CVSup uses several POSIX-specific functions which may make it more of an effort to port the package to non-POSIX systems such as Win32. These functions include mmap, fork, syslog, stat, and chmod, among others. Status of this Release ---------------------- CVSup has seen heavy use and has been quite stable for months. Like all software, though, it is not perfect. Please be prepared to find bugs -- without a doubt, there are some. Please report bugs to . -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Tue Jan 7 16:24:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA27949 for hackers-outgoing; Tue, 7 Jan 1997 16:24:15 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA27907 for ; Tue, 7 Jan 1997 16:23:35 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id BAA01870; Wed, 8 Jan 1997 01:21:20 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA02625; Wed, 8 Jan 1997 01:21:19 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id BAA10873; Wed, 8 Jan 1997 01:15:19 +0100 (MET) Message-ID: Date: Wed, 8 Jan 1997 01:15:19 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.org Cc: proff@suburbia.net Subject: Re: w problem References: <19970107220300.5821.qmail@suburbia.net> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970107220300.5821.qmail@suburbia.net>; from proff@suburbia.net on Jan 8, 1997 09:03:00 +1100 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As proff@suburbia.net wrote: > Was this utmp change entirely necessary? Yes. It was long overdue. > From now on, xf86 has to produce two > versions of its binary distribution, pre and post utmp mangle. No. There are other possible fixes, they have been discussed, and they will eventually be implemented before FreeBSD 3.0 is released. (Concentrating all the handling in libutil, basically.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jan 7 16:26:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA28140 for hackers-outgoing; Tue, 7 Jan 1997 16:26:49 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA28134 for ; Tue, 7 Jan 1997 16:26:45 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA15256; Tue, 7 Jan 1997 17:16:29 -0700 From: Terry Lambert Message-Id: <199701080016.RAA15256@phaeton.artisoft.com> Subject: Re: New motherboard breaks tape drive To: gilham@csl.sri.com (Fred Gilham) Date: Tue, 7 Jan 1997 17:16:29 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: <199701072312.PAA26734@impulse.csl.sri.com> from "Fred Gilham" at Jan 7, 97 03:12:39 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I went through something like this. I have an EISA/VLB motherboard; I > think it's a NICE motherboard but it has a SiS chipset. I tried to > upgrade it from 16 to 32M. FreeBSD crashed every time, fairly > quickly, with or without cache turned on. Windows 95 seemed to run > OK, I believe you will find that your Windows95 is not run bus mastering DMA for its disk drivers, but doing programmed I/O (a cute name to avoid the words "buzz loop on a status register using the main processor") for your particular disk controller. The problem with the motherboard is only evident with EISA bus master devices and driver written to run them in bus mastering mode. You should go back to 16M, compile the kernel with bounce buffers enabled, and reinstall the other 16M. > I finally got a running system by turning off parity checks on memory. > It's been solid ever since, though I shudder to think what will happen > if the memory fails. This is a seperate problem. Most likely, you are running with the board jumpered for too few wait states and are using 70ns or slower memory. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jan 7 16:47:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA29113 for hackers-outgoing; Tue, 7 Jan 1997 16:47:31 -0800 (PST) Received: from thelab.hub.org (hal-ns3-21.netcom.ca [207.181.94.149]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA29107 for ; Tue, 7 Jan 1997 16:47:27 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.4/8.8.2) with SMTP id UAA06262; Tue, 7 Jan 1997 20:45:50 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 7 Jan 1997 20:45:50 -0400 (AST) From: The Hermit Hacker To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: mmap() updates...how often? In-Reply-To: <199701080006.RAA15234@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 7 Jan 1997, Terry Lambert wrote: > If it's MAP_SHARED, then it is updated instantaneously... that is, > it's the same physical memory mapped into both processes. > Okay, that is how its MAP'd...so that isn't my problem... > The context switch rate for a compute intensive task is 100HZ or > once every 10ms. Most likely, the client isn't getting a chance to > run, and the server is monopolizing the CPU. > This sounds reasonable... > > Not being quite sure of what other data I can provide, does > > anyone have any suggestions on what I'm seeing? Since its memory > > mapped, I would have made the assumption that changes to the data > > would be seen instantaneously by the client, but either I'm missing > > something in my code (staring at it too long does that) or I'm once > > more missing something with mmap() > > How are you making sure that the server does not reuse the memory > region before the client displays it? > This is currently the problem I'm looking at fixing... I'm going through the various "solutions" addressed in "Advanced Programming in the Unix Environment" by Stevens, but so far haven't found something that "sounds" reasonable. Its a one->many setup, with many being anywhere from 1 to 1000, at any one time. Semaphores, from what little I understand of them, won't cut it, because I'll have to go through hoops to make sure that each of the clients gets registered with the server, and then de-registered once they go away. Unfortunately, my understanding of them is *very* weak until I've actually programmed them (chicken before egg dilemna *sigh*)... The one thing I was thinking of was to create a socket-based ctl channel. So, when the server has written the frame to memory, it loops through the client sockets, sending it a control message. Then, once that is done, it can go to the next frame. The problem with that is that the server is currently able to write 20+frames/sec to the MMAP'd region...what sort of slowdown can I expect if I have 1000 open sockets that each have to have that control data written to, sequentially? Oh well... I'm still looking for solutions, so if anyone has a path that they think I should research further (ie. am I mistake about semaphores?), please let me know...am all ears... > If the client is an X client, are you using "XSync( Xdisplay);" to > make sure the X servr is not "optimizing" away your screen updates? > No, not using X at all... From owner-freebsd-hackers Tue Jan 7 17:01:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA29848 for hackers-outgoing; Tue, 7 Jan 1997 17:01:05 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA29837 for ; Tue, 7 Jan 1997 17:01:02 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.7.6/8.7.3) with SMTP id QAA21702; Tue, 7 Jan 1997 16:56:17 -0800 (PST) Date: Tue, 7 Jan 1997 16:56:16 -0800 (PST) From: Jaye Mathisen To: Joerg Wunsch cc: hackers@FreeBSD.ORG Subject: Re: noatime, one more time, the last time. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk No, it appears to be mount -p related... As in somehow the -p option doesn't pick up the noatime option. I never tried mount by itself, being in the habit of running mount -p for whatever reason. On Tue, 7 Jan 1997, J Wunsch wrote: > As Jaye Mathisen wrote: > > > So WTF did the noatime go? > > Maybe it's ccd-related? > > uriah # mount -u -o noatime /tmp > uriah # mount > ... > /dev/sd1h on /tmp (local, noatime) > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > From owner-freebsd-hackers Tue Jan 7 17:22:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA01191 for hackers-outgoing; Tue, 7 Jan 1997 17:22:04 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA01168 for ; Tue, 7 Jan 1997 17:21:48 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id CAA04675 for ; Wed, 8 Jan 1997 02:21:39 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id CAA03605 for hackers@FreeBSD.ORG; Wed, 8 Jan 1997 02:21:39 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id CAA11403; Wed, 8 Jan 1997 02:20:54 +0100 (MET) Message-ID: Date: Wed, 8 Jan 1997 02:20:54 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: noatime, one more time, the last time. References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Jaye Mathisen on Jan 7, 1997 16:56:16 -0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jaye Mathisen wrote: > No, it appears to be mount -p related... As in somehow the -p option noatime is simply missing there. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jan 7 17:42:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA03471 for hackers-outgoing; Tue, 7 Jan 1997 17:42:41 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA03433 for ; Tue, 7 Jan 1997 17:42:29 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id MAA12519; Wed, 8 Jan 1997 12:36:31 +1100 Date: Wed, 8 Jan 1997 12:36:31 +1100 From: Bruce Evans Message-Id: <199701080136.MAA12519@godzilla.zeta.org.au> To: hackers@freebsd.org, proff@iq.org Subject: Re: #include file xref philosophy Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >What is the -current philosophy on intra #include file dependencies? My philosophy is: - all headers should be self-sufficient - this should be implemented without including any standard headers - this shall be implemented without any namespace pollution - applications shouldn't assume any more than standards specify >Is there any reason for not following the posix line and having >include files resolve all their own dependencies? I'm talking about That's not the ANSI C line. POSIX.1 requires to be included before including any other POSIX header. >things like needing the code that includes it, include > before hand. In particular, before including . ( used to be self-sufficient in FreeBSD, but a merge from Lite2 made it depend on for u_int_*_t. >Appart from portability issues, which I am increasingly encountering, >I find the idea that user developed .c code must magically "know" >what each /usr/include/* file needs and in what order very ugly >and ecapsulation breaking. The ordering problems are mainly caused by some headers being more self-sufficent than others, with this being implemented in a bad way by including other headers. You can then satisfy magic unknown prerequisites by including an even more more magic list of other headers. Bruce From owner-freebsd-hackers Tue Jan 7 17:47:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA04089 for hackers-outgoing; Tue, 7 Jan 1997 17:47:10 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA04073 for ; Tue, 7 Jan 1997 17:47:02 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id RAA13373 for ; Tue, 7 Jan 1997 17:47:49 -0800 (PST) Received: (qmail 14403 invoked by uid 110); 8 Jan 1997 01:46:39 -0000 Message-ID: <19970108014639.14401.qmail@suburbia.net> Subject: Re: mmap() updates...how often? In-Reply-To: from The Hermit Hacker at "Jan 7, 97 08:45:50 pm" To: scrappy@hub.org (The Hermit Hacker) Date: Wed, 8 Jan 1997 12:46:39 +1100 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > is done, it can go to the next frame. The problem with that is that the > server is currently able to write 20+frames/sec to the MMAP'd region...what > sort of slowdown can I expect if I have 1000 open sockets that each have to > have that control data written to, sequentially? Why not just put them all in the same process group, and send the process group a SIGUSR1 when new data is ready in the mmaped region? This will both inform the processes and wake them up at the same time. Further, if you make your handler just inc a volatile variable, then your main routine can work out how many frames its missed. Cheers, Julian. From owner-freebsd-hackers Tue Jan 7 18:20:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA05890 for hackers-outgoing; Tue, 7 Jan 1997 18:20:56 -0800 (PST) Received: from haywire.DIALix.COM (news@haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA05883 for ; Tue, 7 Jan 1997 18:20:51 -0800 (PST) Received: (from news@localhost) by haywire.DIALix.COM (8.8.4/8.8.2) id KAA10663 for freebsd-hackers@freebsd.org; Wed, 8 Jan 1997 10:20:37 +0800 (WST) X-Authentication-Warning: haywire.DIALix.COM: news set sender to usenet-request@haywire.dialix.com using -f Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-hackers@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-hackers@freebsd.org Date: 8 Jan 1997 02:20:36 GMT From: peter@spinner.DIALix.COM (Peter Wemm) Message-ID: <5av09k$67a$1@haywire.DIALix.COM> Organization: DIALix Services, Perth, Australia. References: <199701072241.JAA17826@profane.iq.org> Subject: Re: #include file xref philosophy Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , j@uriah.heep.sax.de (J Wunsch) writes: > As Julian Assange wrote: > >> What is the -current philosophy on intra #include file dependencies? >> >> Is there any reason for not following the posix line and having >> include files resolve all their own dependencies? I'm talking about >> things like needing the code that includes it, include >> before hand. > > IIRC, Bruce once mentioned that Posix allows it to require the > inclusion of (xor another which i > eventually forgot) before other things. > > Either way, the corresponding man pages should at least mention the > required include files, so your complaint about ``magical knowledge'' > would not be true. As I understand it, POSIX allows for a system to require to be a prerequisite for other include files, Bruce knows more about more than I do. However, the SVIDIII, X/Open XPG (4+), Spec 1170, Single-Unix spec, and the whatever-it-is-called-this-month line of standards apparently require the standard headers to be self sufficient. I believe NetBSD/OpenBSD/Linux comply with this, I remember NetBSD committing the missing includes some time back. Cheers, -Peter From owner-freebsd-hackers Tue Jan 7 18:44:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA07359 for hackers-outgoing; Tue, 7 Jan 1997 18:44:57 -0800 (PST) Received: from nexgen.HiWAAY.net (max12-90.HiWAAY.net [208.147.148.90]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA07354 for ; Tue, 7 Jan 1997 18:44:53 -0800 (PST) Received: from nexgen.HiWAAY.net (localhost [127.0.0.1]) by nexgen.HiWAAY.net (8.7.6/8.7.3) with ESMTP id VAA21756; Mon, 6 Jan 1997 21:02:34 -0600 (CST) Message-Id: <199701070302.VAA21756@nexgen.HiWAAY.net> X-Mailer: exmh version 1.6.9 8/22/96 To: Paulo Cesar Pereira de Andrade cc: FreeBSD hackers From: dkelly@hiwaay.net Subject: Re: sig-11 plague In-reply-to: Message from Paulo Cesar Pereira de Andrade of "Mon, 06 Jan 1997 12:47:15 GMT." <32D0F453.2781E494@sul.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Jan 1997 21:02:33 -0600 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Another day i read a message saying the phrase *sig-11 plague*, > and i thought i was having the same problem. Two weeks ago i upgrade > from my 386 to an amd 5x86, and after a hard time to get FreeBSD > installed *manually*, [snip] > I resolved the problem in the BIOS setup, i disabled the external > cache, and now cc1 does not fail. I too have an AMD 5x86 with similar problems. Go check and see if you recognize your MB. Mine positively will not work with both "write-back cache" and an Adaptec 2940. Well, actually it does work, but only if you are using the fake cache soldered on the MB. It breaks with real cache (custom "SIMM" just for this MB), but works again when the BIOS is set to "write thru cache". I expected lots of entertainment with this $99 MB/CPU/fan, and got it. External cache was $17 more. If I get bored and feel like crashing (some more), I'll see if the VL slot on this MB works as a bus master. Currently the system has been up 18 days and no crashes since I figured out the cache thing. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. From owner-freebsd-hackers Tue Jan 7 19:18:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA09158 for hackers-outgoing; Tue, 7 Jan 1997 19:18:14 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA09127; Tue, 7 Jan 1997 19:18:07 -0800 (PST) Message-Id: <199701080318.TAA09127@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA024833424; Wed, 8 Jan 1997 14:17:04 +1100 From: Darren Reed Subject: Re: FreeBSD as a cleanwall To: proff@suburbia.net Date: Wed, 8 Jan 1997 14:17:04 +1100 (EDT) Cc: hsu@clinet.fi, hackers@FreeBSD.org, security@FreeBSD.org In-Reply-To: <19970107230406.6676.qmail@suburbia.net> from "proff@suburbia.net" at Jan 8, 97 10:04:06 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In some mail from proff@suburbia.net, sie said: [..] > fast masking from RMON > my socket credential code > > Bpf primarily exists to cut down kernel<->user space talk, and I > don't think it is useful elsewhere, except as a slow portable > low-level substrate. Some RMON (one?) system(s) have support for > bpf code, but except for ip/tcp options and quantitative decisions, > fast masks work very well. What's "fast masking" ? Darren From owner-freebsd-hackers Tue Jan 7 19:30:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA09720 for hackers-outgoing; Tue, 7 Jan 1997 19:30:56 -0800 (PST) Received: from monk.via.net (monk.via.net [140.174.204.10]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id TAA09713 for ; Tue, 7 Jan 1997 19:30:54 -0800 (PST) Received: (from joe@localhost) by monk.via.net (8.6.11/8.6.12) id TAA00628 for hackers@freebsd.org; Tue, 7 Jan 1997 19:30:13 -0800 Date: Tue, 7 Jan 1997 19:30:13 -0800 From: Joe McGuckin Message-Id: <199701080330.TAA00628@monk.via.net> To: hackers@freebsd.org Subject: Booting problem with 2.1.6 X-Sun-Charset: US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just installed 2.1.6 off the net onto a PC w- SCSI drives only. My problem is that when I reboot, I get the standard disk selection prompt: Default F1: Then it times out and I get Default F? Nothing I do will convince it to boot from the disk. Is there an easy way to fix this? Also has anyone else noticed that HP drives won't work? joe From owner-freebsd-hackers Tue Jan 7 19:45:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA10379 for hackers-outgoing; Tue, 7 Jan 1997 19:45:19 -0800 (PST) Received: from cold.org (cold.org [206.81.134.103]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA10374 for ; Tue, 7 Jan 1997 19:45:14 -0800 (PST) Received: from localhost (brandon@localhost) by cold.org (8.8.3/8.8.3) with SMTP id UAA26699 for ; Tue, 7 Jan 1997 20:45:17 -0700 (MST) Date: Tue, 7 Jan 1997 20:45:17 -0700 (MST) From: Brandon Gillespie To: freebsd-hackers@freebsd.org Subject: Selective Port Control (was Re: sendmail running non-root SUCCESS!) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 7 Jan 1997, Jimbo Bahooli wrote: > 6. edit /etc/sendmail.cf to bind to a port above the 1024 line. example: > > O DaemonPortOptions=Port=2025 > > 7. edit /etc/inetd.conf to redirect to port 2025 using netcat. example: I'm not sure how feasable it is, but one thing that would make securing some network services EXTREMELY easier would be to be able to dynamically configure port permissions, rather than to globally restrict them to 'root' Perhaps something like /etc/port.access which is formated as the 'port' (either an integer or service name) followed by some sort of access specifier, such as the common group.user, examples: smtp daemon.mail nntp newsman.news 480 special.group http webman.www etc.. Just a thought, but it'd not only help in securing things from running as root but it'd make it a lot easier to customize daemons privately, amoung many others. The security factor alone would seem to be a win. Off the bat I would think most services would run as other users if this were available.. -Brandon Gillespie From owner-freebsd-hackers Tue Jan 7 21:15:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA13158 for hackers-outgoing; Tue, 7 Jan 1997 21:15:22 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA13152 for ; Tue, 7 Jan 1997 21:15:15 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id PAA13834; Wed, 8 Jan 1997 15:44:57 +1030 (CST) From: Michael Smith Message-Id: <199701080514.PAA13834@genesis.atrad.adelaide.edu.au> Subject: Re: kernel bootp stuff In-Reply-To: <199701031411.PAA05212@labinfo.iet.unipi.it> from Luigi Rizzo at "Jan 3, 97 03:11:21 pm" To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Wed, 8 Jan 1997 15:44:56 +1030 (CST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Luigi Rizzo stands accused of saying: > > as it should) and mountd (which does not allow mounting files, but > only directries; this is fixed in 3.0 -current) This works in 2.2 as well; it's necessary for netbooting NetBSD and SunOS machines at least. > Before wasting too much time trying to cleanup the code for general > use, is there any of the committers interested in adding it to the > distributions (post 2.2) ? It's just a couple of new files and very > short modifications to 4-5 files mainly to instruct config to deal > with the new option properly. Sounds interesting; if nobody else takes it up, and you can provide me with the stuff ready-to-go along with manpages, I'll happily drop it in. > Luigi Rizzo | Dip. di Ingegneria dell'Informazione -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Wed Jan 8 02:04:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA24567 for hackers-outgoing; Wed, 8 Jan 1997 02:04:22 -0800 (PST) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA24562 for ; Wed, 8 Jan 1997 02:04:18 -0800 (PST) Received: by pcnet1.pcnet.com (4.1/SMI-4.1) id AA29695; Wed, 8 Jan 97 04:58:46 EST Date: Wed, 8 Jan 97 04:58:46 EST From: eischen@vigrid.com (Daniel Eischen) Message-Id: <9701080958.AA29695@pcnet1.pcnet.com> To: hackers@FreeBSD.ORG, joe@via.net Subject: Re: Booting problem with 2.1.6 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I just installed 2.1.6 off the net onto a PC w- SCSI drives only. > > My problem is that when I reboot, I get the standard disk selection prompt: > > Default F1: > > Then it times out and I get > > Default F? > > Nothing I do will convince it to boot from the disk. Is there an >easy way to fix this? > >Also has anyone else noticed that HP drives won't work? This probably belongs on -questions. When you installed FreeBSD was there a pre-existing DOS partition on the drive (in which you were installing)? It sounds like a geometry problem. Creating a small DOS partition on the destination drive will allow FreeBSD to pick up the correct geometries. During the partition and labeling process, you can then delete the DOS partition if you don't want it. Dan Eischen eischen@pcnet.com From owner-freebsd-hackers Wed Jan 8 02:17:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA25160 for hackers-outgoing; Wed, 8 Jan 1997 02:17:10 -0800 (PST) Received: from hda.hda.com (ip31-max1-fitch.ziplink.net [199.232.245.31]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA25146 for ; Wed, 8 Jan 1997 02:17:06 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id FAA03591; Wed, 8 Jan 1997 05:12:31 -0500 From: Peter Dufault Message-Id: <199701081012.FAA03591@hda.hda.com> Subject: Re: #include file xref philosophy In-Reply-To: <199701080136.MAA12519@godzilla.zeta.org.au> from Bruce Evans at "Jan 8, 97 12:36:31 pm" To: bde@zeta.org.au (Bruce Evans) Date: Wed, 8 Jan 1997 05:12:30 -0500 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >Is there any reason for not following the posix line and having > >include files resolve all their own dependencies? I'm talking about > > That's not the ANSI C line. POSIX.1 requires to be > included before including any other POSIX header. How about "POSIX.1 sometimes requires that be included before including some POSIX headers". They sprinkle size_t all over the place so that old programs don't break. Annex C has a summary of what types are defined in each header: mqueue.h mqd_t semaphore.h sem_t signal.h sig_atomic_t sigset_t siginfo_t stddef.h ptrdiff_t size_t wchar_t stdio.h fpos_t size_t FILE stdlib.h div_t ldiv_t size_t wchar_t string.h size_t times.h clock_t sys/types.h dev_t ino_t nlink_t pid_t ssize_t gid_t mode_t off_t size_t uid_t termios.h cc_t speed_t tcflag_t time.h clockid_t size_t time_t clock_t timer_t So size_t is defined by stddef.h, stdio.h, stdlib.h, string.h, sys/types.h, and time.h while off_t is only in sys/types.h. (This is P1003.1b-1993) -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-hackers Wed Jan 8 02:22:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA25405 for hackers-outgoing; Wed, 8 Jan 1997 02:22:49 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA25400 for ; Wed, 8 Jan 1997 02:22:45 -0800 (PST) Message-Id: <199701081022.CAA25400@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA138718950; Wed, 8 Jan 1997 21:22:30 +1100 From: Darren Reed Subject: Re: Year 2000 time change(Format support) To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Wed, 8 Jan 1997 21:22:29 +1100 (EDT) Cc: hackers@freebsd.org In-Reply-To: <199701061938.UAA00776@yedi.iaf.nl> from "Wilko Bulte" at Jan 6, 97 08:38:44 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Are there any cases where software calculates a year that is in the range 0-99 and then adds that to 1900 ? Or any that displays 19%d ? (I'm just inquiring about bins that are shipped with the os) darren From owner-freebsd-hackers Wed Jan 8 03:28:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA28557 for hackers-outgoing; Wed, 8 Jan 1997 03:28:09 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id DAA28534 for ; Wed, 8 Jan 1997 03:27:57 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id WAA32757; Wed, 8 Jan 1997 22:20:50 +1100 Date: Wed, 8 Jan 1997 22:20:50 +1100 From: Bruce Evans Message-Id: <199701081120.WAA32757@godzilla.zeta.org.au> To: bde@zeta.org.au, dufault@hda.com Subject: Re: #include file xref philosophy Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >Is there any reason for not following the posix line and having >> >include files resolve all their own dependencies? I'm talking about >> >> That's not the ANSI C line. POSIX.1 requires to be >> included before including any other POSIX header. > >How about "POSIX.1 sometimes requires that >be included before including some POSIX headers". They sprinkle >size_t all over the place so that old programs don't break. I'm only familiar with POSIX.1-1990. size_t is required to be declared by many ANSI C headers and this must be done (at least in the pure ANSI C case) without including (which doesn't exist in ANSI C). >Annex C has a summary of what types are defined in each header: > >mqueue.h mqd_t >semaphore.h sem_t These headers aren't in POSIX.1-1990 (or FreeBSD). >signal.h sig_atomic_t sigset_t siginfo_t sig_atomic_t is in ANSI C, sigset_t is in POSIX.1-1990, and siginfo_t is new (and not in FreeBSD). >stddef.h ptrdiff_t size_t wchar_t >stdio.h fpos_t size_t FILE >stdlib.h div_t ldiv_t size_t wchar_t >string.h size_t >times.h clock_t Same as in ANSI C. >sys/types.h dev_t ino_t nlink_t pid_t ssize_t gid_t mode_t off_t size_t uid_t >termios.h cc_t speed_t tcflag_t Same as in POSIX.1-1990. >time.h clockid_t size_t time_t clock_t timer_t size_t, time_t and clock_t are in ANSI C. clockid_t and timer_t are new (and not in FreeBSD). >So size_t is defined by stddef.h, stdio.h, stdlib.h, string.h, sys/types.h, >and time.h while off_t is only in sys/types.h. Same as in ANSI C and POSIX.1-1990. >(This is P1003.1b-1993) POSIX.1 reserves all names ending in _t if any POSIX.1 header is included. Thus an implementation may include if doesn't have any namespace pollution. However, an application that depends on this is unportable. Bruce From owner-freebsd-hackers Wed Jan 8 04:16:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA01222 for hackers-outgoing; Wed, 8 Jan 1997 04:16:14 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA01217 for ; Wed, 8 Jan 1997 04:16:11 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id EAA21905 for ; Wed, 8 Jan 1997 04:16:54 -0800 (PST) Received: (qmail 5418 invoked by uid 110); 8 Jan 1997 12:15:29 -0000 Message-ID: <19970108121529.5416.qmail@suburbia.net> Subject: Re: #include file xref philosophy In-Reply-To: <199701081012.FAA03591@hda.hda.com> from Peter Dufault at "Jan 8, 97 05:12:30 am" To: dufault@hda.com (Peter Dufault) Date: Wed, 8 Jan 1997 23:15:29 +1100 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > >Is there any reason for not following the posix line and having > > >include files resolve all their own dependencies? I'm talking about > > > > That's not the ANSI C line. POSIX.1 requires to be > > included before including any other POSIX header. > > How about "POSIX.1 sometimes requires that > be included before including some POSIX headers". They sprinkle > size_t all over the place so that old programs don't break. > Frankly it is painful. Include files should not break their encapsulation. include/netinet/*.h are frightful. As a bunch of other things when -DKERNEL is on. Next time you are writing/modifying an include file, please keep this in mind. Not having an include file resolve its own dependencies saves you nothing, but an open(), during CPP. I don't care if possix says its sometimes ok. Posix is wrong. I just had to manually edit and recompile 100 .c files in the last two ports I did - ports that compiled without problem on 6 other platforms, because of #include stupidity. Someone replied to me 'the magic is in the man page' - well when the magic is in everyone elses man page and CPP understands how to parse nroff and -ms macros I'll believe you. This says is to say nothing of future compatibility issues. What if no longer needs . Do we restrospectively change the worlds manpages? Cheers, Julian From owner-freebsd-hackers Wed Jan 8 04:32:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA02306 for hackers-outgoing; Wed, 8 Jan 1997 04:32:03 -0800 (PST) Received: from hda.hda.com (ip30-max1-fitch.ziplink.net [199.232.245.30]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA02293 for ; Wed, 8 Jan 1997 04:31:57 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id HAA03877; Wed, 8 Jan 1997 07:26:29 -0500 From: Peter Dufault Message-Id: <199701081226.HAA03877@hda.hda.com> Subject: Re: #include file xref philosophy In-Reply-To: <19970108121529.5416.qmail@suburbia.net> from "proff@suburbia.net" at "Jan 8, 97 11:15:29 pm" To: proff@suburbia.net Date: Wed, 8 Jan 1997 07:26:28 -0500 (EST) Cc: dufault@hda.com, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > How about "POSIX.1 sometimes requires that > > be included before including some POSIX headers". They sprinkle > > size_t all over the place so that old programs don't break. > > > > Frankly it is painful... Just to make it clear: I think headers should stand alone and include anything they need. Above I'm saying that POSIX isn't as clear as Bruce was. So IMHO: 1. Yes, headers should include all prerequisites; 2. For portability, our man pages should match what POSIX says, even if we don't require it. For example, lseek needs both and but our man page says . (I hope that the POSIX tests don't do things such as include only unistd.h and verify that something referencing off_t fails.) -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-hackers Wed Jan 8 04:38:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA02577 for hackers-outgoing; Wed, 8 Jan 1997 04:38:50 -0800 (PST) Received: from mail.MCESTATE.COM (vince@mail.MCESTATE.COM [206.171.98.50]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA02572 for ; Wed, 8 Jan 1997 04:38:48 -0800 (PST) Received: from localhost (vince@localhost) by mail.MCESTATE.COM (8.8.3/8.8.3) with SMTP id EAA01762 for ; Wed, 8 Jan 1997 04:38:28 -0800 (PST) Date: Wed, 8 Jan 1997 04:38:18 -0800 (PST) From: Vincent Poy To: hackers@FreeBSD.ORG Subject: 2.1.6R kernel compile problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk We're having a problem with two of three machines that if we specified options pty 256 from pty 16, the machine will just keep rebooting over and over again right after npx0 in the device list, it says panic: double fault This happens where normally it identifies the swap device I think. Any ideas? It works fine at pty 16. All devices (ptys) have been configured as well as /etc/ttys updated. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET Unix Networking Operations GaiaNet Corporation - M & C Estate Beverly Hills, California USA 90210 From owner-freebsd-hackers Wed Jan 8 05:09:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA04003 for hackers-outgoing; Wed, 8 Jan 1997 05:09:32 -0800 (PST) Received: from smtp-gw01.ny.us.ibm.net (smtp-gw01.ny.us.ibm.net [165.87.194.252]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id FAA03998 for ; Wed, 8 Jan 1997 05:09:30 -0800 (PST) Received: (from uucp@localhost) by smtp-gw01.ny.us.ibm.net (8.6.9/8.6.9) id NAA198420; Wed, 8 Jan 1997 13:09:29 GMT Message-Id: <199701081309.NAA198420@smtp-gw01.ny.us.ibm.net> Received: from slip166-72-229-168.va.us.ibm.net(166.72.229.168) by smtp-gw01.ny.us.ibm.net via smap (V1.3mjr) id smaOrYCrx; Wed Jan 8 13:09:19 1997 Reply-To: From: "Steve Sims" To: "Hackers" Cc: Subject: Bounce Buffers and CCD Date: Wed, 8 Jan 1997 08:07:39 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_01BBFD3B.03CA2DA0" Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_01BBFD3B.03CA2DA0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I've had a bounty of problems getting `ccd` to work with my Adaptech 1542-CF. Under 2.2-mumble the symptoms were the dreaded: vm_bounce_alloc: b_bufsize(0x80) < b_count(0x200) !! panic: vm_bounce_alloc error. Worked fine with only 16 Meg installed, I assumed that this "might" have been fixed in -CURRENT, sup'd that, rebuilt everything. Still no go. So I turned to the archives to see if this was FAQ and stumbled across the attached message (patch included). I figured that I had nothing to lose, so I 'patch < /tmp/foo', rebuilt kernel, reboot - SUCCESS! (Thanks, John!) Question: Is there any reason that this one-liner has not been folded in to -CURRENT, -STABLE, and kin? Related point: I believe it was Terry Lambert that stated in previous messages (words to the effect) that "option BOUNCE_BUFFERS" is not *strictly* needed; that this functionality is automatically enabled on ISA systems with >16Meg and that including "options BOUNCE_BUFFERS" in late-model kernel configs only serves to *force* BOUNCE_BUFFERS on ISA systems with =< 16Meg. I don't concur. Removing "options BOUNCE_BUFFERS" on a 32Meg system will page-fault-panic a booting box as quickly as anything else I've ever tried! (Terry, I hope I haven't quoted you out of context, but I'm here to tell ya': BOUNCE-BUFFERS is a MANDATORY option for >16M systems, at least on 3.0-CURRENT with my mo-bo having PCI, ISA and VESA!) ...sjs... ------=_NextPart_000_01BBFD3B.03CA2DA0 Content-Type: application/octet-stream; name="ccd_pat.txt" Content-Transfer-Encoding: quoted-printable Content-Description: ccd_pat (Text Document) Content-Disposition: attachment; filename="ccd_pat.txt" Date: Fri, 6 Sep 1996 22:50:07 -0500 (EST) From: "John S. Dyson" To: gordon@drogon.net (Gordon Henderson) Cc: questions@freebsd.org, scsi@freebsd.org Sender: owner-questions@freebsd.org Subject: Re: CCD Setup woes ... (Kernel Panic) >=20 > I'm tring to get a CCD going as an experiment and it's causing the = kernel > to panic.=20 >=20 Yep, there is a problem with CCD using the FreeBSD bounce scheme. Of = course, it is only noticed on ISA systems. >=20 > which resulted in a kernel panic. The message is: >=20 > vm_bounce_alloc: b_bufsize(0x80) < b_count(0x200) !! > panic: vm_bounce_alloc >=20 b_bufsize is not being setup correctly in ccd (I think). > > followed by the usual syncing disks bit. The number in the b_bufsize() = > varies from crash to crash. >=20 > Am I doing anything obviously wrong? >=20 No. Hope the following works for you!!! If it does, let me know so that I can commit it. Try this patch to ccd relative to -current (the equiv patch might work for -stable), I haven't tested this though: Index: ccd.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /local/home/ncvs/src/sys/dev/ccd/ccd.c,v retrieving revision 1.16 diff -C5 -r1.16 ccd.c *** ccd.c 1996/07/24 23:45:24 1.16 --- ccd.c 1996/09/07 03:46:27 *************** *** 909,918 **** --- 909,920 ---- else cbp->cb_buf.b_bcount =3D dbtob(cs->sc_ileave - cboff); if (cbp->cb_buf.b_bcount > bcount) cbp->cb_buf.b_bcount =3D bcount; =20 + cbp->cb_buf.b_bufsize =3D cbp->cb_buf.b_bcount; +=20 /* * context for ccdiodone */ cbp->cb_obp =3D bp; cbp->cb_unit =3D cs - ccd_softc; ------------------------------------------------------------------------ www@freebsd.org ------=_NextPart_000_01BBFD3B.03CA2DA0-- From owner-freebsd-hackers Wed Jan 8 06:11:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA06525 for hackers-outgoing; Wed, 8 Jan 1997 06:11:15 -0800 (PST) Received: from pardal (root@[200.255.244.56]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id GAA06491 for ; Wed, 8 Jan 1997 06:11:01 -0800 (PST) Received: from paulo (paulo [200.1.1.51]) by pardal (8.6.12/8.6.9) with SMTP id MAA01049 for ; Wed, 8 Jan 1997 12:14:06 -0200 Message-ID: <32D38F9D.41C67EA6@sul.com.br> Date: Wed, 08 Jan 1997 12:14:21 +0000 From: Paulo Cesar Pereira de Andrade Organization: FiscoData X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.1.0-RELEASE i386) MIME-Version: 1.0 To: FreeBSD hackers Subject: sig-11 plague Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have surfed the net looking for info and tried other possibilities to try to resolve my problem. And, to avoid looking lyke I was crying to you my bad luck, i did not told you all the problems, because I was thinking that was not the cause: I buyed a S3 Trio64 video card, and I also have a Trident 9440 that cames with the computer. The Trident only works with X32, but is too slower than the S3, so I was only using the S3, but the problem was that all time I was wanting to run X, I first runned SuperProbe, to see how much memory it tells me the video card has; if SuperProbe says I have 4096Kb or it says I have 2048Kb, I know that X will not run properly, but if it says I have 1024Kb, then I can do a: startx -- -bpp 16 else I do a: xinit /usr/X11R6/bin/xterm -- /usr/X11R6/bin/XF86_VGA16 Thinking the problem was with de video card (it is also unusable under w95, most times), i went to the computer store where i buyed the computer, and changed the old card by a new one. At night, back to home, I put the video card on the computer, started FreeBSD and run SuperProbe, it told me 1024Kb, *very good*. Then i powered down the computer and installed my NEC ide-cdrom, that was on the 386 -- oh, i did not say? the cdrom was not working whith the 5x86, but works very well with the 386. Powered up again the system, i did a: cat /cdrom/dists/bin.?? | tar zxvf - -C /usr/test and i got no erros. I then, in the BIOS setup reenabled the external cache and restarted FreeBSD, repeated the command and I did get no errors, oh! its amazing, all things are working, im happy, -- then i started X and it was running good, then I untarred another file and I get a error from gzip (oh no) repeated the command and get no errors; ok, i think it is the bios cache, disabled it and restarted FreeBSD, but now, SuperProbe all the time says me the video card has 4096Kb of memory (I told X in XF86Config, but this does not help). The Trident video card does not fail, at least int the few times i experienced it, so, i will again to the computer store and i will negotiate whith them another kind (supported by X) of video card, because i am thinking it is the problem. Ok, after all, i yet have my 386 with an amazing 670Kb custom kernel and a low resource configuration system that is very confiable/stable to play. Thanks in advance for any help/comment. Paulo. And here is some info: ------------- Main Board Info: DX-9500 Universal PCI, VESA, ISA 5x86/486 System Board ------------- BIOS Info: +---------------------------------------------------------------------+ | AMIBIOS Configuration (C) 1985-1994, American Megatrends Inc, | +---------------------------------------+-----------------------------+ | Main Processor : Amd 5x86 | Base Memory Size : 640KB | | Numeric Processor : Built-In | Ext. Memory Size : 15360KB | | Floppy Drive A: : 1.44 MB 3 1/2" | Display Type : VGA/EGA | | Floppy Drive B: : None | Serial Port(s) : 3F8,2F8 | | AMIBIOS Date : 10/10/94 | Parallel Port(s) : 378 | +---------------------------------------+-----------------------------+ | Hard Disk(s) Cyl Hd Sec Size LBA 32Bit Block PIO | | Mode Mode Mode Mode | | Primary Master: C: 3244 16 63 1597MB On Off Off 4 | +---------------------------------------------------------------------+ 133 MHz CPU Clock ------------- # dmesg FreeBSD 2.1.0-RELEASE #0: Thu Nov 16 10:47:14 1995 jkh@westhill.cdrom.com:/usr/src/sys/compile/GENERIC CPU: i486DX (486-class CPU) Origin = "AuthenticAMD" Id = 0x4f4 real memory = 16777216 (16384K bytes) avail memory = 14733312 (14388K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0: disabled, not probed. ed1: disabled, not probed. sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2: disabled, not probed. sio3: disabled, not probed. lpt0: disabled, not probed. lpt1: disabled, not probed. lpt2: disabled, not probed. mse0: disabled, not probed. fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 1596MB (3269952 sectors), 3244 cyls, 16 heads, 63 S/T, 512 B/S wdc1: disabled, not probed. bt0: disabled, not probed. uha0: disabled, not probed. ahc1: disabled, not probed. ahb0: disabled, not probed. aha0: disabled, not probed. aic0: disabled, not probed. nca0: disabled, not probed. nca1: disabled, not probed. sea0: disabled, not probed. wt0: disabled, not probed. mcd0: disabled, not probed. mcd1: disabled, not probed. matcdc0: disabled, not probed. scd0: disabled, not probed. ie0: disabled, not probed. ep0: disabled, not probed. ix0: disabled, not probed. le0: disabled, not probed. lnc0: disabled, not probed. lnc1: disabled, not probed. ze0: disabled, not probed. zp0: disabled, not probed. npx0 on motherboard npx0: INT 16 interface Probing for devices on the PCI bus: vga0 rev 0 int a irq 12 on pci0:14 pci0:16: UMC, device=0x8881, class=bridge (host) [no driver assigned] pci0:18: UMC, device=0x886a, class=bridge (isa) [no driver assigned] From owner-freebsd-hackers Wed Jan 8 06:30:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA07410 for hackers-outgoing; Wed, 8 Jan 1997 06:30:25 -0800 (PST) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id GAA07405 for ; Wed, 8 Jan 1997 06:30:21 -0800 (PST) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id JAA24300; Wed, 8 Jan 1997 09:28:35 -0500 From: Bill Paul Message-Id: <199701081428.JAA24300@skynet.ctr.columbia.edu> Subject: Re: Question about ypbind To: sszabo@io.com (Stephan Szabo) Date: Wed, 8 Jan 1997 09:28:34 -0500 (EST) Cc: hackers@freebsd.org In-Reply-To: from "Stephan Szabo" at Jan 7, 97 11:26:09 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the towns in all the world, Stephan Szabo had to walk into mine and say: > > > We have been attempting to install NIS on a FreeBSD 2.1.5R system > > > and have run into a problem with ypbind. When it is run, it dies on a > > > SIGSEGV. Going through gdb a bit gave us the following: > > > Program received signal SIGSEGV, Segmentation fault. > > > [rest left off for brevity] > > > > Works fine for me. > > > > What params are you running ypbind with? What kind of server is ypbind > > binding too (or trying to bind to)? > > Originally we were running ypbind -s, and then ypbind with no parameters > to see if that would work. > The server is another FreeBSD 2.1.5R system. > > The strange thing was that it had worked for a little while, and then > stopped working, but no changes were made to our knowledge to the > configuration of either machine. > > Stephan Szabo Probably something did change, but you don't think it's related. This is often the case. ("Naw, changing the netmask on the ethernet interface couldn't _possibly_ affect anything.") You have to describe your system a little better. What is your domain name? How many domains are there? Are you using virtual interfaces? Is your system multi-homed? Do you have other clients that work correctly? Does the server correctly bind to itself? Don't stop there: ask yourself more questions about your own system and answer them for me. Chances are that along the way you may discover thr problem. -Bill, who hates it when people don't give enough details -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= From owner-freebsd-hackers Wed Jan 8 06:41:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA07861 for hackers-outgoing; Wed, 8 Jan 1997 06:41:25 -0800 (PST) Received: from gatekeeper.ctron.com (ctron.com [134.141.197.25]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id GAA07854 for ; Wed, 8 Jan 1997 06:41:22 -0800 (PST) Received: (from news@localhost) by gatekeeper.ctron.com (8.6.12/8.6.9) id JAA29378 for ; Wed, 8 Jan 1997 09:41:15 -0500 Received: from stealth.ctron.com(134.141.5.107) by gatekeeper via smap (V1.3mjr) id sma029349; Wed Jan 8 09:40:41 1997 Received: from thoth.ctron.com by stealth.ctron.com (4.1/SMI-4.1) id AA27552; Wed, 8 Jan 97 09:46:39 EST Received: from thoth (localhost [127.0.0.1]) by thoth.ctron.com (8.6.12/8.6.12) with SMTP id JAA16616 for ; Wed, 8 Jan 1997 09:42:31 -0500 Message-Id: <32D3B256.3AFC@ctron.com> Date: Wed, 08 Jan 1997 09:42:30 -0500 From: Alexander Seth Jones Organization: Cabletron Systems, Inc. X-Mailer: Mozilla 3.0Gold (X11; I; SunOS 5.4 sun4m) Mime-Version: 1.0 To: hackers@freefall.freebsd.org Subject: setting modem characteristics Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, Where do I set stop bits and data bits for my modem? I found where to set parity and flow control, but haven't been able to find anything for these other two. Are they to be done through stty? -- Alex Jones | ajones@ctron.com Cabletron Systems, Inc. Durham, NH USA 03824 From owner-freebsd-hackers Wed Jan 8 08:10:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA12347 for hackers-outgoing; Wed, 8 Jan 1997 08:10:59 -0800 (PST) Received: from interlink.ReyMoreno.net.co ([205.218.236.10]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA12323; Wed, 8 Jan 1997 08:10:51 -0800 (PST) Received: from [205.218.237.166] (windows.reymoreno.net.co [205.218.237.166]) by interlink.ReyMoreno.net.co (8.6.11/8.6.9) with SMTP id LAA28163; Wed, 8 Jan 1997 11:11:46 -0800 Message-Id: <199701081911.LAA28163@interlink.ReyMoreno.net.co> To: FreeBSD hackers , "freebsd-questions@freebsd.org" Subject: Unsubscribe Date: Wed, 08 Jan 97 11:15:12 -0500 From: Mauricio Calderòn X-Mailer: E-Mail Connection v3.1a Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk -- [ From: Mauricio Calderòn * EMC.Ver #3.1a ] -- unsubscribe freebsd-questions unsubscribe freebsd-hardware From owner-freebsd-hackers Wed Jan 8 08:43:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA15821 for hackers-outgoing; Wed, 8 Jan 1997 08:43:23 -0800 (PST) Received: from nt-server.nteatel.net ([207.101.8.250]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA15815 for ; Wed, 8 Jan 1997 08:43:14 -0800 (PST) Received: from [207.101.0.87] by nt-server.nteatel.net (NTMail 3.02.07) with ESMTP id oa081914 for ; Wed, 8 Jan 1997 10:42:14 -0600 Message-Id: <3.0.32.19970108104240.00d0a080@hawkewerks.com> X-Sender: hawke@hawkewerks.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 08 Jan 1997 10:42:41 -0600 To: freebsd-hackers@freebsd.org From: HawkeWerks Multimedia Subject: FreeBSD as an ISDN Router Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've got a small network of 5 pc's. One of which is a 486/100 with 32 mb ram and FreeBSD. I would like to put a Motorola Bitsurfer ISDN TA in it, and use this box as a router to the internet for the other boxes. All the other Machines are Windoze 95, and NT, and I would like to have them talk to the Internet through the 486. Any suggestions? Is this possible? TIA Lloyd From owner-freebsd-hackers Wed Jan 8 08:45:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA16039 for hackers-outgoing; Wed, 8 Jan 1997 08:45:56 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA16030 for ; Wed, 8 Jan 1997 08:45:53 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA16433; Wed, 8 Jan 1997 09:34:13 -0700 From: Terry Lambert Message-Id: <199701081634.JAA16433@phaeton.artisoft.com> Subject: Re: #include file xref philosophy To: proff@suburbia.net Date: Wed, 8 Jan 1997 09:34:12 -0700 (MST) Cc: dufault@hda.com, hackers@FreeBSD.ORG In-Reply-To: <19970108121529.5416.qmail@suburbia.net> from "proff@suburbia.net" at Jan 8, 97 11:15:29 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Frankly it is painful. Include files should not break their encapsulation. > include/netinet/*.h are frightful. As a bunch of other things when > -DKERNEL is on. Next time you are writing/modifying an include file, please > keep this in mind. Not having an include file resolve its own dependencies > saves you nothing, but an open(), during CPP. I don't care if possix > says its sometimes ok. Posix is wrong. I agree. POSIX screws up in a number of places. Mandating update times for the getdents() interface (or mandating the getdents interface at all for that matter) is another example. Lack of a definite interface for setting file size up or down (ftruncate/fcntl-based) is yet another. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jan 8 08:46:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA16129 for hackers-outgoing; Wed, 8 Jan 1997 08:46:54 -0800 (PST) Received: from inf.enst.fr (inf.enst.fr [137.194.2.81]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA16120 for ; Wed, 8 Jan 1997 08:46:49 -0800 (PST) Received: from nikopol.enst.fr (nikopol.enst.fr [137.194.168.105]) by inf.enst.fr (8.8.3/8.8.4) with ESMTP id RAA08225; Wed, 8 Jan 1997 17:46:10 +0100 (MET) Received: (from fenyo@localhost) by nikopol.enst.fr (8.8.3/8.8.2) id RAA12918; Wed, 8 Jan 1997 17:46:01 +0100 (MET) To: Alexander Seth Jones Cc: hackers@freefall.freebsd.org X-WWW: http://home.eowyn.fr.eu.org/~fenyo/documents/axel.html X-PGP-Key: finger alex@eowyn.fr.eu.org X-NIC-Handle: AF713 X-Whois: whois -h whois.internic.net fenyo X-Pager: 06-04-30-75-94 (for emergency only) Organization: Ecole Nationale Superieure des Telecommunications de Paris Subject: Re: setting modem characteristics References: <32D3B256.3AFC@ctron.com> From: fenyo@inf.enst.fr (Alex Fenyo (eowyn)) Date: 08 Jan 1997 17:46:00 +0100 In-Reply-To: Alexander Seth Jones's message of Wed, 08 Jan 1997 09:42:30 -0500 Message-ID: Lines: 23 X-Mailer: Red Gnus v0.50/XEmacs 19.14 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Alexander Seth Jones writes: > Where do I set stop bits and data bits for my modem? I found where to > set parity and flow control, but haven't been able to find anything for > these other two. > > Are they to be done through stty? Yes, 'man stty' says : cstopb (-cstopb) Use two (one) stop bits per character. cs5 cs6 cs7 cs8 Select character size, if possible. for instance, try : stty cs8 -cstopb < /dev/cuaa0 The modem will automatically detect those settings when you enter the first AT command. Alexandre Fenyo From owner-freebsd-hackers Wed Jan 8 08:47:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA16197 for hackers-outgoing; Wed, 8 Jan 1997 08:47:33 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA16186 for ; Wed, 8 Jan 1997 08:47:30 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA16445; Wed, 8 Jan 1997 09:36:15 -0700 From: Terry Lambert Message-Id: <199701081636.JAA16445@phaeton.artisoft.com> Subject: Re: #include file xref philosophy To: dufault@hda.com (Peter Dufault) Date: Wed, 8 Jan 1997 09:36:15 -0700 (MST) Cc: proff@suburbia.net, dufault@hda.com, hackers@FreeBSD.org In-Reply-To: <199701081226.HAA03877@hda.hda.com> from "Peter Dufault" at Jan 8, 97 07:26:28 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > (I hope that the POSIX tests don't do things such as include only > unistd.h and verify that something referencing off_t fails.) I believe they can't. Since off_t (a nice particular example, BTW) is defined to be an atomic type, the type may in fact be literal off_t and remain technically compliant with the standard. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jan 8 08:48:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA16293 for hackers-outgoing; Wed, 8 Jan 1997 08:48:23 -0800 (PST) Received: from nt-server.nteatel.net ([207.101.8.250]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA16282 for ; Wed, 8 Jan 1997 08:48:19 -0800 (PST) Received: from [207.101.0.87] by nt-server.nteatel.net (NTMail 3.02.07) with ESMTP id pa081915 for ; Wed, 8 Jan 1997 10:47:38 -0600 Message-Id: <3.0.32.19970108104805.00d6de50@hawkewerks.com> X-Sender: hawke@hawkewerks.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 08 Jan 1997 10:48:06 -0600 To: freebsd-hackers@freebsd.org From: HawkeWerks Multimedia Subject: FreeBSD as an ISDN Router ***Additional Info*** Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A few things I probably should have mentioned earlier. The routing will be over PPP, with Dynamic IP's. (I'll just use the 192.0.2.*) subnet for the internal routing) The box is currently running 2.1.5-RELEASE. Thanks Lloyd From owner-freebsd-hackers Wed Jan 8 08:55:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA16802 for hackers-outgoing; Wed, 8 Jan 1997 08:55:08 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA16719 for ; Wed, 8 Jan 1997 08:53:28 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA16463; Wed, 8 Jan 1997 09:43:32 -0700 From: Terry Lambert Message-Id: <199701081643.JAA16463@phaeton.artisoft.com> Subject: Re: Bounce Buffers and CCD To: SimsS@IBM.Net Date: Wed, 8 Jan 1997 09:43:32 -0700 (MST) Cc: Hackers@FreeBSD.ORG, toor@dyson.iquest.net In-Reply-To: <199701081309.NAA198420@smtp-gw01.ny.us.ibm.net> from "Steve Sims" at Jan 8, 97 08:07:39 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Related point: I believe it was Terry Lambert that stated in previous > messages (words to the effect) that "option BOUNCE_BUFFERS" is not *strictly* > needed; that this functionality is automatically enabled on ISA systems with > >16Meg and that including "options BOUNCE_BUFFERS" in late-model kernel > configs only serves to *force* BOUNCE_BUFFERS on ISA systems with =< 16Meg. > I don't concur. Removing "options BOUNCE_BUFFERS" on a 32Meg system will > page-fault-panic a booting box as quickly as anything else I've ever tried! > (Terry, I hope I haven't quoted you out of context, but I'm here to tell ya': > BOUNCE-BUFFERS is a MANDATORY option for >16M systems, at least on > 3.0-CURRENT with my mo-bo having PCI, ISA and VESA!) Then it's not required AND it's broken. 8-(. Bounce conditions are supposed to be autodetected. What controller are you using? (PCI/VESA/ISA?) How many address lines are propagated, if PCI/VESA? (24/32?) It may be that your motherboard is broken... literally, the config BOUNCE_BUFFERS option is defined as turning on bouncing in conditions where it is not supposed to be required according to the hardware specifications for the busses involved. If you are using an ISA bus mastering DMA controller, it's supposed to be handled. If you are using nything else, it's supposed to be unnecessary; if you find it necessary for non-ISA hardware, your motherboard is not standards compliant and you should contact the manufacturer (and send mail with make/model/revision to the hardware list maintainers for a "don't anyone else buy one of these" note). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jan 8 09:16:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA18215 for hackers-outgoing; Wed, 8 Jan 1997 09:16:22 -0800 (PST) Received: from nevis.oss.uswest.net (nevis.oss.uswest.net [204.147.85.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA18125 for ; Wed, 8 Jan 1997 09:15:46 -0800 (PST) Received: (from greg@localhost) by nevis.oss.uswest.net (8.8.2/8.8.2) id LAA12696 for hackers@freebsd.org; Wed, 8 Jan 1997 11:15:10 -0600 (CST) From: "Greg Rowe" Message-Id: <9701081115.ZM12694@nevis.oss.uswest.net> Date: Wed, 8 Jan 1997 11:15:10 -0600 X-Mailer: Z-Mail (3.2.1 10oct95) To: hackers@freebsd.org Subject: 2.2 BETA Upgrade Problem Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone seen a problem with 2.2 BETA upgrade procedure using NFS ? If I do an upgrade using NFS, as soon as it gets to the point of installing the distributions, it immediately comes back with a "Couldn't extract the following distributions" (all distributions are listed) error. The debug screen shows that the device was mounted to /dist but ls'ing /dist gives a "Stale NFS file handle" error. If I create another directory(while still in the install shell) and try doing the mount again, the mount command completes with no error but again ls'ing produces the "Stale NFS file handle" error. I've tried upgrading two different systems, from two different NFS servers with the same results. Both NFS servers contain the 2.1.6 Release directory and that upgrade works fine. I can upgrade another system if you need me to test anything. Thanks. Greg Rowe -- Greg Rowe | U S West - Interact Services | INTERNET greg@uswest.net 111 Washington Ave. South | Fax: (612) 672-8537 Minneapolis, MN USA 55401 | Voice: (612) 672-8535 Never trust an operating system you don't have source for.... From owner-freebsd-hackers Wed Jan 8 09:32:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA19031 for hackers-outgoing; Wed, 8 Jan 1997 09:32:24 -0800 (PST) Received: from gatekeeper.fsl.noaa.gov (gatekeeper.fsl.noaa.gov [137.75.131.181]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA19026 for ; Wed, 8 Jan 1997 09:32:22 -0800 (PST) Received: from cardinal.fsl.noaa.gov (daemon@cardinal.fsl.noaa.gov [137.75.60.101]) by gatekeeper.fsl.noaa.gov (8.7.5/8.7.3) with ESMTP id RAA12025; Wed, 8 Jan 1997 17:32:20 GMT Received: from auk.fsl.noaa.gov by cardinal.fsl.noaa.gov with SMTP (1.40.112.3/16.2) id AA290284740; Wed, 8 Jan 1997 17:32:20 GMT Message-Id: <32D3DA8F.A59@fsl.noaa.gov> Date: Wed, 08 Jan 1997 10:34:07 -0700 From: Sean Kelly Organization: CIRA/NOAA X-Mailer: Mozilla 3.0Gold (X11; I; HP-UX B.10.10 9000/725) Mime-Version: 1.0 To: Greg Rowe Cc: hackers@FreeBSD.ORG Subject: Re: 2.2 BETA Upgrade Problem References: <9701081115.ZM12694@nevis.oss.uswest.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Greg Rowe wrote: > Has anyone seen a problem with 2.2 BETA upgrade procedure using NFS ? If I do > an upgrade using NFS, as soon as it gets to the point of installing the > distributions, it immediately comes back with a "Couldn't extract the following > distributions" (all distributions are listed) error. Yes, I've seen the exact same thing last night. (Sorry, haven't made the pr yet.) This was from a local FreeBSD 2.1.5 NFS server. The machine I was upgrading could mount the 2.2-BETA directories successfully, but the floppy boot couldn't. > If I create another directory(while still in the install shell) > and try doing the mount again, the mount command completes with no error but > again ls'ing produces the "Stale NFS file handle" error. Yep, I got the same thing. Also, if you type "mount" and list what's mounted, the two NFS mounts show up with garbage characters: !*@ on /dist sj7($!* on /mnt I had to resort to moving the 2.2-BETA sources into the anonymous ftp user's directory and using the FTP install option. Luckily, that worked. (Until it came time to restore my /etc directory. More garbage characters appeared but recovering the files by hand worked.) -- Sean Kelly NOAA Forecast Systems Laboratory kelly@fsl.noaa.gov Boulder Colorado USA http://www-sdd.fsl.noaa.gov/~kelly/ From owner-freebsd-hackers Wed Jan 8 09:56:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA20229 for hackers-outgoing; Wed, 8 Jan 1997 09:56:31 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA20224 for ; Wed, 8 Jan 1997 09:56:29 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vi2EU-00030G-00; Wed, 8 Jan 1997 10:56:10 -0700 To: Darren Reed Subject: Re: Year 2000 time change(Format support) Cc: wilko@yedi.iaf.nl (Wilko Bulte), hackers@freebsd.org In-reply-to: Your message of "Wed, 08 Jan 1997 21:22:29 +1100." <199701081022.CAA25400@freefall.freebsd.org> References: <199701081022.CAA25400@freefall.freebsd.org> Date: Wed, 08 Jan 1997 10:56:10 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199701081022.CAA25400@freefall.freebsd.org> Darren Reed writes: : Are there any cases where software calculates a year that is in the range : 0-99 and then adds that to 1900 ? There are many places where years are displayed as tm_yr + 1900, but that is the right thing to do (since tm_yr isn't in the range 0..99). : Or any that displays 19%d ? Likely. I keep seeing such things. A quick grep of the source tree will tell the anser to that :-). Warner From owner-freebsd-hackers Wed Jan 8 10:22:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA21531 for hackers-outgoing; Wed, 8 Jan 1997 10:22:52 -0800 (PST) Received: from ravenock.cybercity.dk (ravenock.cybercity.dk [194.16.57.32]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA21526 for ; Wed, 8 Jan 1997 10:22:46 -0800 (PST) Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.4/8.7.3) id TAA00483; Wed, 8 Jan 1997 19:24:21 +0100 (MET) Message-Id: <199701081824.TAA00483@ravenock.cybercity.dk> Subject: Re: FreeBSD as an ISDN Router In-Reply-To: <3.0.32.19970108104240.00d0a080@hawkewerks.com> from HawkeWerks Multimedia at "Jan 8, 97 10:42:41 am" To: hawke@hawkewerks.com (HawkeWerks Multimedia) Date: Wed, 8 Jan 1997 19:24:21 +0100 (MET) Cc: freebsd-hackers@freebsd.org From: sos@freebsd.org Reply-to: sos@freebsd.org X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply to HawkeWerks Multimedia who wrote: > I've got a small network of 5 pc's. One of which is a 486/100 with 32 mb > ram and FreeBSD. I would like to put a Motorola Bitsurfer ISDN TA in it, > and use this box as a router to the internet for the other boxes. All the > other Machines are Windoze 95, and NT, and I would like to have them talk > to the Internet through the 486. Any suggestions? Is this possible? Does it all the time :), except that I use a Stollman TA+PPP device... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Wed Jan 8 10:29:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA21989 for hackers-outgoing; Wed, 8 Jan 1997 10:29:46 -0800 (PST) Received: from smtp-gw01.ny.us.ibm.net (smtp-gw01.ny.us.ibm.net [165.87.194.252]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA21983 for ; Wed, 8 Jan 1997 10:29:39 -0800 (PST) Received: (from uucp@localhost) by smtp-gw01.ny.us.ibm.net (8.6.9/8.6.9) id SAA207537; Wed, 8 Jan 1997 18:28:10 GMT Message-Id: <199701081828.SAA207537@smtp-gw01.ny.us.ibm.net> Received: from slip166-72-229-200.va.us.ibm.net(166.72.229.200) by smtp-gw01.ny.us.ibm.net via smap (V1.3mjr) id smaJhcCkR; Wed Jan 8 18:27:55 1997 Reply-To: From: "Steve Sims" To: "Terry Lambert" Cc: Subject: Re: Bounce Buffers and CCD Date: Wed, 8 Jan 1997 13:27:23 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From: Terry Lambert >> (Terry, I hope I haven't quoted you out of context, but I'm here to tell >> ya': BOUNCE-BUFFERS is a MANDATORY option for >16M systems, at least on >> 3.0-CURRENT with my mo-bo having PCI, ISA and VESA!) > > Then it's not required AND it's broken. 8-(. > > Bounce conditions are supposed to be autodetected. Would that it were true.... > What controller are you using? (PCI/VESA/ISA?) Plain-vanilla ISA flavor Adaptec 1542-CF, Firmware 2.02 (IIRC), defaults all around: 0x330, IRQ:11 DRQ:5 > How many address lines are propagated, if PCI/VESA? (24/32?) Beats me. How can I find out? (Not that I'm sure it matters, being an ISA-centric failure. > It may be that your motherboard is broken... literally, the config > BOUNCE_BUFFERS option is defined as turning on bouncing in conditions > where it is not supposed to be required according to the hardware > specifications for the busses involved. It may be the motherboard loses. It's pretty old; no-name P-5/90. I've got a Mach-32 card in a PCI slot, everything else is ISA; ports, SCSI. If we need more granularity to determine why this board fails, I'll pop it out and decipher the silk screening. Say the word. > If you are using an ISA bus mastering DMA controller, it's supposed > to be handled. If you are using nything else, it's supposed to be > unnecessary; if you find it necessary for non-ISA hardware, your > motherboard is not standards compliant and you should contact the > manufacturer (and send mail with make/model/revision to the hardware > list maintainers for a "don't anyone else buy one of these" note). "Supposed" being the operative term here... ;-) ...sjs... From owner-freebsd-hackers Wed Jan 8 10:34:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA22241 for hackers-outgoing; Wed, 8 Jan 1997 10:34:55 -0800 (PST) Received: from mailhub.aros.net (mailhub.aros.net [207.173.16.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA22219 for ; Wed, 8 Jan 1997 10:33:51 -0800 (PST) Received: from fluffy.aros.net (fluffy.aros.net [207.173.16.2]) by mailhub.aros.net (8.8.4/Unknown) with ESMTP id LAA03913; Wed, 8 Jan 1997 11:33:23 -0700 (MST) Received: from fluffy.aros.net (localhost [127.0.0.1]) by fluffy.aros.net (8.8.4/8.6.12) with ESMTP id LAA08250; Wed, 8 Jan 1997 11:33:21 -0700 (MST) Message-Id: <199701081833.LAA08250@fluffy.aros.net> To: Sean Kelly cc: Greg Rowe , hackers@FreeBSD.org Subject: Re: 2.2 BETA Upgrade Problem In-reply-to: Your message of "Wed, 08 Jan 1997 10:34:07 MST." <32D3DA8F.A59@fsl.noaa.gov> Date: Wed, 08 Jan 1997 11:33:21 -0700 From: Dave Andersen Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > an upgrade using NFS, as soon as it gets to the point of installing the > > distributions, it immediately comes back with a "Couldn't extract the following > > distributions" (all distributions are listed) error. > > Yes, I've seen the exact same thing last night. (Sorry, haven't made > the pr yet.) We encountered it also. I did a send-pr on part of it - the fact that the system reboots after telling you it couldn't load the bin distribution and doesn't give you a chance to select a different install type - but I assumed the NFS mount was something I was goofing up. > This was from a local FreeBSD 2.1.5 NFS server. The machine I was > upgrading could mount the 2.2-BETA directories successfully, but the > floppy boot couldn't. It also failed from a local FreeBSD 2.2-BETA NFS server. It later worked properly from the same server via anonymous FTP. > I had to resort to moving the 2.2-BETA sources into the anonymous ftp > user's directory and using the FTP install option. Luckily, that > worked. (Until it came time to restore my /etc directory. More garbage > characters appeared but recovering the files by hand worked.) This happened here, but only on the machine which we unsuccessfully attempted to upgrade via NFS. The other 2.2-BETA upgrades went perfectly - the garbaged etc storage directory seems to be an artifact of trying to upgrade via NFS. -Dave Andersen From owner-freebsd-hackers Wed Jan 8 10:53:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA22922 for hackers-outgoing; Wed, 8 Jan 1997 10:53:03 -0800 (PST) Received: from smtp-gw01.ny.us.ibm.net (smtp-gw01.ny.us.ibm.net [165.87.194.252]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA22914 for ; Wed, 8 Jan 1997 10:52:59 -0800 (PST) Received: (from uucp@localhost) by smtp-gw01.ny.us.ibm.net (8.6.9/8.6.9) id SAA87614; Wed, 8 Jan 1997 18:52:51 GMT Message-Id: <199701081852.SAA87614@smtp-gw01.ny.us.ibm.net> Received: from slip166-72-229-154.va.us.ibm.net(166.72.229.154) by smtp-gw01.ny.us.ibm.net via smap (V1.3mjr) id smaSjUDe7; Wed Jan 8 18:52:43 1997 Reply-To: From: "Steve Sims" To: , "HawkeWerks Multimedia" Subject: Re: FreeBSD as an ISDN Router Date: Wed, 8 Jan 1997 13:52:39 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If (as I recall) the BitSurfr is, from FreeBSD's perspective, an AT-command-set compatible "modem" on an arbitrary serial port, then ppp (with the new '-alias' switch in (I hope) the latest 2.2 is the way to go. I gateway a LAN, through a FreeBSD "router" to the Internet. It should "just work". ...sjs... ---------- > From: HawkeWerks Multimedia > To: freebsd-hackers@freebsd.org > Subject: FreeBSD as an ISDN Router > Date: Wednesday, January 08, 1997 11:42 AM > > I've got a small network of 5 pc's. One of which is a 486/100 with 32 mb > ram and FreeBSD. I would like to put a Motorola Bitsurfer ISDN TA in it, > and use this box as a router to the internet for the other boxes. All the > other Machines are Windoze 95, and NT, and I would like to have them talk > to the Internet through the 486. Any suggestions? Is this possible? > > TIA > Lloyd > From owner-freebsd-hackers Wed Jan 8 10:53:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA22980 for hackers-outgoing; Wed, 8 Jan 1997 10:53:37 -0800 (PST) Received: from po1.glue.umd.edu (root@po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA22971 for ; Wed, 8 Jan 1997 10:53:32 -0800 (PST) Received: from uplink.eng.umd.edu (uplink.eng.umd.edu [129.2.98.181]) by po1.glue.umd.edu (8.8.3/8.7.3) with ESMTP id NAA08000; Wed, 8 Jan 1997 13:53:29 -0500 (EST) Received: from localhost (chuckr@localhost) by uplink.eng.umd.edu (8.8.3/8.7.3) with SMTP id NAA08099; Wed, 8 Jan 1997 13:53:28 -0500 (EST) X-Authentication-Warning: uplink.eng.umd.edu: chuckr owned process doing -bs Date: Wed, 8 Jan 1997 13:53:28 -0500 (EST) From: Chuck Robey X-Sender: chuckr@uplink.eng.umd.edu To: Greg Rowe cc: hackers@FreeBSD.ORG Subject: Re: 2.2 BETA Upgrade Problem In-Reply-To: <9701081115.ZM12694@nevis.oss.uswest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 8 Jan 1997, Greg Rowe wrote: > Has anyone seen a problem with 2.2 BETA upgrade procedure using NFS ? If I do > an upgrade using NFS, as soon as it gets to the point of installing the > distributions, it immediately comes back with a "Couldn't extract the following > distributions" (all distributions are listed) error. The debug screen shows > that the device was mounted to /dist but ls'ing /dist gives a "Stale NFS file > handle" error. If I create another directory(while still in the install shell) > and try doing the mount again, the mount command completes with no error but > again ls'ing produces the "Stale NFS file handle" error. > > I've tried upgrading two different systems, from two different NFS servers > with the same results. Both NFS servers contain the 2.1.6 Release directory and > that upgrade works fine. I can upgrade another system if you need me to test > anything. Thanks. I just used nfs to load my new machine from an existing one. Didn't have to go out of my little 2 machine net, but it worked line a charm. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Wed Jan 8 11:21:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA24141 for hackers-outgoing; Wed, 8 Jan 1997 11:21:12 -0800 (PST) Received: from nic.follonett.no (nic.follonett.no [194.198.43.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA24133 for ; Wed, 8 Jan 1997 11:21:09 -0800 (PST) Received: (from uucp@localhost) by nic.follonett.no (8.8.3/8.8.3) with UUCP id UAA13959; Wed, 8 Jan 1997 20:19:52 +0100 (MET) Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id UAA26550; Wed, 8 Jan 1997 20:19:08 +0100 (MET) Message-Id: <3.0.32.19970108202141.009be270@dimaga.com> X-Sender: eivind@dimaga.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 08 Jan 1997 20:21:42 +0100 To: HawkeWerks Multimedia From: Eivind Eklund Subject: Re: FreeBSD as an ISDN Router Cc: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 10:48 AM 1/8/97 -0600, you wrote: >I've got a small network of 5 pc's. One of which is a 486/100 with 32 mb >ram and FreeBSD. I would like to put a Motorola Bitsurfer ISDN TA in it, >and use this box as a router to the internet for the other boxes. All the >other Machines are Windoze 95, and NT, and I would like to have them talk >to the Internet through the 486. Any suggestions? Is this possible? Defineatly the routing; I don't know about the ISDN card. Tell me if it work well for you; I'm switching to ISDN in a couple of weeks. >The routing will be over PPP, with Dynamic IP's. (I'll just use the >192.0.2.*) subnet for the internal routing) I'm presently doing just that (modem instead of ISDN, but this shouldn't make a difference), using PPP+pktAlias 1.6. This is available from http://www.srv.net/~cmott/alias.html >From this base, I've upgraded the base PPP version to 2.1.6 with security patches. (Patches similar to the official ones, but done by yours truly.) The upgrade was simple - all changes were to different files. In addition, I've got a new version of alias.c from Charles Mott, the author. It fix a problem with FTP from the machine running PPP+pktAlias to other machines on the PPP-side subnet. (Ie, it didn't affect the 192.0.0.x-net at all, but with a dynamic IP of eg 194.198.43.149 I couldn't FTP to 194.198.43.25) PPP+pktAlias handle reverse protocols for FTP only; there are no support for eg IRC. (IRC work, but you cannot use DCC to send files) Apart from PPP+pktAlias I have two things worh mentioning - Apache 1.1.1 running as a webproxy, and firewalling to disallow connections from the rest of the world to the server when connected via PPP. The Apache webproxy work fine for http, and badly for FTP. I've just turned proxy off for FTP, and let each machine do that themselves. My firewalling script has some kludges because I want to talk to my ISP, and I want to route from the 192.* to the world. I get a dynamic IP in the upper half of 194.198.43.x, and I trust the lower half (local to the ISP, good security). The script follows; it was was written two days ago, and might still be buggy. I had to change it just today to allow FTP from the 192.0.0.x-boxes... ## Clear the old setup ipfw flush ## Allow everything within the 192 local network (will also allow the ## proxied stuff) ipfw add allow ip from 192.0.0.0/24 to any ipfw add allow ip from any to 192.0.0.0/24 ## Allow to 194.198.43.0-127 (machines at Follonett; this range do NOT ## include the dynamic IP of this box) ipfw add allow ip from any to 194.198.43.0/25 ipfw add allow ip from 194.198.43.0/25 to any ## Set up for our dynamic IP address, in the upper half of ## 194.198.43.* (ie, 194.198.43.128-255) # Generic connections outbound allowed ipfw add allow tcp from any to 194.198.43.128/25 1024-65535 # Connections within the dynamic IPs disallowed ipfw add reject all from 194.198.43.128/25 to 194.198.43.128/25 # Generic connections outwards allowed ipfw add allow all from 194.198.43.128/25 to any # Allow DNS and NTP. ipfw add allow udp from any 53,123 to 194.198.43.128/25 53,123 # Reject all unspecified UDP ipfw add reject udp from any to 194.198.43.128/25 1-65535 # Reject all privileged ports ipfw add reject tcp from any to 194.198.43.128/25 1-1024 # Reject X11 control ports ipfw add reject tcp from any to 194.198.43.128/25 6000-6063 # Allow FTP connects (somewhat insecure, but very convenient) ipfw add allow tcp from any 20 to 194.198.43.128/25 1024-65535 ## Allow all ICMP (for ping) ipfw add allow icmp from any to any ## Allow traceroute ipfw add allow udp from any 33434-33534 to any 33434-33534 ## Done I run this from /etc/netstart - and your kernel must be compiled with options IPFIREWALL for this to work. You'll probably want options IPFIREWALL_VERBOSE too, to be able to log what trigger what rules. >The box is currently running 2.1.5-RELEASE. My box is running 2.1.6 (compiled over parts of 2.1.5 over an initial 2.1.0 :) Well, hope that helped. Feel free to ask if anything is unclear. BTW: If anybody feel like commenting on how I should change the firewall-script, please do. Eivind Eklund / perhaps@yes.no / http://maybe.yes.no/perhaps/ From owner-freebsd-hackers Wed Jan 8 11:34:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA24666 for hackers-outgoing; Wed, 8 Jan 1997 11:34:15 -0800 (PST) Received: from guardian.fortress.org (fortress.org [199.84.158.128]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA24656 for ; Wed, 8 Jan 1997 11:34:10 -0800 (PST) Received: (from andrew@localhost) by guardian.fortress.org (8.7.6/8.6.12) id OAA15132; Wed, 8 Jan 1997 14:34:08 -0500 (EST) Date: Wed, 8 Jan 1997 14:34:06 -0500 (EST) From: Andrew Webster Reply-To: andrew@pubnix.net To: HawkeWerks Multimedia cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD as an ISDN Router ***Additional Info*** In-Reply-To: <3.0.32.19970108104805.00d6de50@hawkewerks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 8 Jan 1997, HawkeWerks Multimedia wrote: > A few things I probably should have mentioned earlier. > > The routing will be over PPP, with Dynamic IP's. (I'll just use the > 192.0.2.*) subnet for the internal routing) > > The box is currently running 2.1.5-RELEASE. Have you considered using RFC 1579 compliant non-routable internal addresses "just in case": 10.0.0.0 - 10.255.255.255 172.16.0.0 - 172.31.255.255 198.168.0.0 - 198.168.255.255 Regards, Andrew Webster andrew@pubnix.net PubNIX Montreal Connected to the world Branche au monde P.O. Box 147 Cote Saint Luc, Quebec H4V 2Y3 tel 514.990.5911 http://www.pubnix.net fax 514.990.9443 From owner-freebsd-hackers Wed Jan 8 11:38:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA24939 for hackers-outgoing; Wed, 8 Jan 1997 11:38:00 -0800 (PST) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA24934 for ; Wed, 8 Jan 1997 11:37:58 -0800 (PST) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id OAA01255; Wed, 8 Jan 1997 14:37:26 -0500 Date: Wed, 8 Jan 1997 14:37:26 -0500 (EST) From: "Ron G. Minnich" X-Sender: rminnich@terra To: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD as an ISDN Router In-Reply-To: <199701081852.SAA87614@smtp-gw01.ny.us.ibm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Last time the bitsurfr came up on this last it was to describe all the problems with it. Has motorola fixed them? thanks ron Ron Minnich |"Failure is not an option" -- Gene Kranz rminnich@sarnoff.com | -- except, of course, on Microsoft products (609)-734-3120 | ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html From owner-freebsd-hackers Wed Jan 8 11:54:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA25659 for hackers-outgoing; Wed, 8 Jan 1997 11:54:53 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA25635 for ; Wed, 8 Jan 1997 11:54:48 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA16809; Wed, 8 Jan 1997 12:44:32 -0700 From: Terry Lambert Message-Id: <199701081944.MAA16809@phaeton.artisoft.com> Subject: Re: Bounce Buffers and CCD To: SimsS@IBM.Net Date: Wed, 8 Jan 1997 12:44:32 -0700 (MST) Cc: terry@lambert.org, Hackers@FreeBSD.ORG In-Reply-To: <199701081828.SAA207537@smtp-gw01.ny.us.ibm.net> from "Steve Sims" at Jan 8, 97 01:27:23 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> (Terry, I hope I haven't quoted you out of context, but I'm here to tell > >> ya': BOUNCE-BUFFERS is a MANDATORY option for >16M systems, at least on > >> 3.0-CURRENT with my mo-bo having PCI, ISA and VESA!) > > > > Then it's not required AND it's broken. 8-(. > > > > Bounce conditions are supposed to be autodetected. > > Would that it were true.... > > > What controller are you using? (PCI/VESA/ISA?) > > Plain-vanilla ISA flavor Adaptec 1542-CF, Firmware 2.02 (IIRC), defaults all > around: 0x330, IRQ:11 DRQ:5 Bounce buffers should be implied by the 1542 driver, automagically. If they are not, then the driver is broken; I would guess "recently". > > How many address lines are propagated, if PCI/VESA? (24/32?) > > Beats me. How can I find out? (Not that I'm sure it matters, being an > ISA-centric failure. It's not PCI/VESA, so it's 24 (standard for ISA). Means the DMA target has to be in the low 16M, and if it isn't it needs to be "bounced". This is determined by knowing that it's an AHA1542 driver (ISA DMA bus master) and comparing the address to see if it's above 16M. > > If you are using an ISA bus mastering DMA controller, it's supposed > > to be handled. If you are using nything else, it's supposed to be > > unnecessary; if you find it necessary for non-ISA hardware, your > > motherboard is not standards compliant and you should contact the > > manufacturer (and send mail with make/model/revision to the hardware > > list maintainers for a "don't anyone else buy one of these" note). > > "Supposed" being the operative term here... ;-) "Is handled as far as I know for non-broken hardware that meets the bus specifications as ratified as accepted standards". In other words, making NiCE HiNT chipset machines work is out of scope (but possible -- see previous postings for this subject). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jan 8 12:32:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA27683 for hackers-outgoing; Wed, 8 Jan 1997 12:32:14 -0800 (PST) Received: from home.winc.com (root@home.winc.com [204.178.182.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA27678 for ; Wed, 8 Jan 1997 12:32:11 -0800 (PST) Received: from phoenix.aristar.com (slip125.winc.com [204.178.182.125]) by home.winc.com (8.8.4/8.8.4) with SMTP id PAA10015; Wed, 8 Jan 1997 15:32:08 -0500 Message-ID: <32D40441.41C67EA6@aristar.com> Date: Wed, 08 Jan 1997 15:32:01 -0500 From: "Matthew A. Gessner" Organization: Aristar, Inc. X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.1.0-RELEASE i386) MIME-Version: 1.0 To: hackers Subject: ppp -direct problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, all, I'm running 2.1.0, and the man page for ppp isn't real clear on how to set up a direct link. Here's what I have so far: I can login and start the ppplogin script that's suggested, but I have several questions I need answered: #1: if my "remote" machine is 10.0.0.123 and my "host" is 10.0.0.3 how do I a) set up tun0 (or do I use tun1 since I have a modem)? b) set up the 'ifaddr' in ppp.secret and ppp.conf I'd appreciate the help of someone who's already done this. Thanks! -- Matthew Gessner, Computer Scientist, Aristar, Inc. 302 N. Cleveland-Massillon Rd. Akron, OH 44333 Voice (330) 668-2267, Fax (330) 668-2961 From owner-freebsd-hackers Wed Jan 8 12:42:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA28251 for hackers-outgoing; Wed, 8 Jan 1997 12:42:56 -0800 (PST) Received: from smtp-gw01.ny.us.ibm.net (smtp-gw01.ny.us.ibm.net [165.87.194.252]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA28237 for ; Wed, 8 Jan 1997 12:42:51 -0800 (PST) Received: (from uucp@localhost) by smtp-gw01.ny.us.ibm.net (8.6.9/8.6.9) id UAA123445; Wed, 8 Jan 1997 20:41:33 GMT Message-Id: <199701082041.UAA123445@smtp-gw01.ny.us.ibm.net> Received: from slip166-72-229-214.va.us.ibm.net(166.72.229.214) by smtp-gw01.ny.us.ibm.net via smap (V1.3mjr) id smaAO4DM2; Wed Jan 8 20:41:16 1997 Reply-To: From: "Steve Sims" To: "Terry Lambert" Cc: , Subject: Re: Bounce Buffers and CCD Date: Wed, 8 Jan 1997 15:27:44 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From: Terry Lambert > > >> (Terry, I hope I haven't quoted you out of context, but I'm here to tell > > >> ya': BOUNCE-BUFFERS is a MANDATORY option for >16M systems, at least on > > >> 3.0-CURRENT with my mo-bo having PCI, ISA and VESA!) > > > > > > Then it's not required AND it's broken. 8-(. > > > > > > Bounce conditions are supposed to be autodetected. > > > > Would that it were true.... > > > Bounce buffers should be implied by the 1542 driver, automagically. If > they are not, then the driver is broken; I would guess "recently". Settled: The driver looks to be broken. I'll sup -CURRENT and see if it's been magically fixed, if not, how to proceed with tracking this down; who's the keeper of the 1542 code? > It's not PCI/VESA, so it's 24 (standard for ISA). Means the DMA target > has to be in the low 16M, and if it isn't it needs to be "bounced". > This is determined by knowing that it's an AHA1542 driver (ISA DMA > bus master) and comparing the address to see if it's above 16M. > > > "Supposed" being the operative term here... ;-) > > "Is handled as far as I know for non-broken hardware that meets the > bus specifications as ratified as accepted standards". > > In other words, making NiCE HiNT chipset machines work is out of scope > (but possible -- see previous postings for this subject). I shudder at the recollection of *that* brain-damaged chipset! ...sjs... From owner-freebsd-hackers Wed Jan 8 12:54:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA28664 for hackers-outgoing; Wed, 8 Jan 1997 12:54:38 -0800 (PST) Received: from perki0.connect.com.au (perki0.connect.com.au [192.189.54.85]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA28659 for ; Wed, 8 Jan 1997 12:54:35 -0800 (PST) Received: (from Unemeton@localhost) by perki0.connect.com.au id HAA09434 (8.7.6h/IDA-1.6); Thu, 9 Jan 1997 07:54:32 +1100 (EST) X-Authentication-Warning: perki0.connect.com.au: Unemeton set sender to giles@nemeton.com.au using -f >Received: from localhost.nemeton.com.au (localhost.nemeton.com.au [127.0.0.1]) by nemeton.com.au (8.8.4/8.8.4) with SMTP id HAA26798; Thu, 9 Jan 1997 07:46:48 +1100 (EST) Message-Id: <199701082046.HAA26798@nemeton.com.au> To: Darren Reed cc: hackers@freebsd.org Subject: Re: Year 2000 time change(Format support) In-reply-to: <199701081022.CAA25400@freefall.freebsd.org> Date: Thu, 09 Jan 1997 07:46:48 +1100 From: Giles Lean Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 8 Jan 1997 21:22:29 +1100 (EDT) Darren Reed wrote: > Are there any cases where software calculates a year that is in the range > 0-99 and then adds that to 1900 ? Probably. I would worry too about software (like query-pr --sql) which takes perfectly good four digit dates and strips the leading two digits. While not in itself a problem, it makes using the output harder, particularly if you want to sort it. > Or any that displays 19%d ? Looks like it; see below. (I haven't really followed these up.) I would't worry too much about sccs2rcs.csh -- it isn't safe to use anyway. That RCS doesn't look safe is concerning -- we probably need to fix this. ./src/contrib/cvs/contrib/sccs2rcs.csh: set date = `sccs prs -r$rev $file | grep "^D " | awk '{printf("19%s %s", $3, $4); exit}'` ./src/gnu/usr.bin/rcs/lib/rcstime.c: "19%.*s/%.2s/%.2s %.2s:%.2s:%s" ./src/usr.bin/yacc/test/ftp.tab.c: "19%02d%02d%02d%02d%02d%02d", ./src/usr.bin/yacc/test/ftp.y: "19%02d%02d%02d%02d%02d%02d", ./src/usr.sbin/xntpd/parse/clk_trimtsip.c: printf("sv6+ software: %d.%d (19%d/%d/%d)\n", Giles From owner-freebsd-hackers Wed Jan 8 13:31:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA00711 for hackers-outgoing; Wed, 8 Jan 1997 13:31:45 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA00702 for ; Wed, 8 Jan 1997 13:31:41 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id NAA00917; Wed, 8 Jan 1997 13:31:37 -0800 (PST) To: HawkeWerks Multimedia cc: freebsd-hackers@FreeBSD.org Subject: Re: FreeBSD as an ISDN Router In-reply-to: Your message of "Wed, 08 Jan 1997 10:42:41 CST." <3.0.32.19970108104240.00d0a080@hawkewerks.com> Date: Wed, 08 Jan 1997 13:31:36 -0800 Message-ID: <913.852759096@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I've got a small network of 5 pc's. One of which is a 486/100 with 32 mb > ram and FreeBSD. I would like to put a Motorola Bitsurfer ISDN TA in it, > and use this box as a router to the internet for the other boxes. All the > other Machines are Windoze 95, and NT, and I would like to have them talk > to the Internet through the 486. Any suggestions? Is this possible? Depends on whether those other boxes have real IP addresses. If they do, no sweat at all. If they don't, then you will have to use the 2.2-BETA or later ppp program, which support IP aliasing. Unfortunately, the Motorola Bitsurfer is a festering piece-o-shit(tm) and you'd do very well to stay away from it or anything else from Motorola's communications products division. Cisco has also been doing quite a bit of testing with their stuff, and the unanimous decision seems to be "buy a modem or TA from Moto and you will lose." I use the ADTRAN ISDN TA and I've been 100% happy with it. The next generation ADTRAN stuff looks even better, and they have always been VERY receptive to requests. I spent about an hour talking to them at COMDEX and went away quite impressed that they actually understood the ISDN market and seemed to even know what they were doing. My visit to the Motorola booth only left me with the impression that they have a fine marketing department. :-) Jordan From owner-freebsd-hackers Wed Jan 8 13:33:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA00838 for hackers-outgoing; Wed, 8 Jan 1997 13:33:59 -0800 (PST) Received: from ns2.harborcom.net (root@ns2.harborcom.net [206.158.4.4]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA00833 for ; Wed, 8 Jan 1997 13:33:57 -0800 (PST) Received: from swoosh.dunn.org (swoosh.dunn.org [206.158.7.243]) by ns2.harborcom.net (8.8.4/8.8.4) with SMTP id QAA09153; Wed, 8 Jan 1997 16:33:38 -0500 (EST) Date: Wed, 8 Jan 1997 16:31:06 -0500 () From: Bradley Dunn To: andrew@pubnix.net cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD as an ISDN Router ***Additional Info*** In-Reply-To: Message-ID: X-X-Sender: bradley@harborcom.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 8 Jan 1997, Andrew Webster wrote: > Have you considered using RFC 1579 compliant non-routable internal > addresses "just in case": > 10.0.0.0 - 10.255.255.255 > 172.16.0.0 - 172.31.255.255 > 198.168.0.0 - 198.168.255.255 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 192.168.0.0 - 192.168.255.255. RFC 1918 is the most recent RFC covering this. -BD From owner-freebsd-hackers Wed Jan 8 13:34:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA00880 for hackers-outgoing; Wed, 8 Jan 1997 13:34:05 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA00857 for ; Wed, 8 Jan 1997 13:34:02 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id NAA00932; Wed, 8 Jan 1997 13:33:43 -0800 (PST) To: "Greg Rowe" cc: hackers@freebsd.org Subject: Re: 2.2 BETA Upgrade Problem In-reply-to: Your message of "Wed, 08 Jan 1997 11:15:10 CST." <9701081115.ZM12694@nevis.oss.uswest.net> Date: Wed, 08 Jan 1997 13:33:42 -0800 Message-ID: <928.852759222@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is weird, and I will look into it when I get back home. I tested the FTP upgrade and NFS installation procedures during my shake-out period, but I can't say that I tested an NFS upgrade. They should be the same, and there's no difference between the way "upgrade" uses the media and the way that the standard install uses it, so this is quite odd. Jordan > Has anyone seen a problem with 2.2 BETA upgrade procedure using NFS ? If I d o > an upgrade using NFS, as soon as it gets to the point of installing the > distributions, it immediately comes back with a "Couldn't extract the followi ng > distributions" (all distributions are listed) error. The debug screen shows > that the device was mounted to /dist but ls'ing /dist gives a "Stale NFS fil e > handle" error. If I create another directory(while still in the install shell ) > and try doing the mount again, the mount command completes with no error but > again ls'ing produces the "Stale NFS file handle" error. > > I've tried upgrading two different systems, from two different NFS servers > with the same results. Both NFS servers contain the 2.1.6 Release directory a nd > that upgrade works fine. I can upgrade another system if you need me to test > anything. Thanks. > > Greg Rowe > > -- > Greg Rowe | > U S West - Interact Services | INTERNET greg@uswest.net > 111 Washington Ave. South | Fax: (612) 672-8537 > Minneapolis, MN USA 55401 | Voice: (612) 672-8535 > > Never trust an operating system you don't have source for.... > From owner-freebsd-hackers Wed Jan 8 13:49:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA01730 for hackers-outgoing; Wed, 8 Jan 1997 13:49:07 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA01724 for ; Wed, 8 Jan 1997 13:49:04 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id NAA01029; Wed, 8 Jan 1997 13:49:00 -0800 (PST) To: "Ron G. Minnich" cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD as an ISDN Router In-reply-to: Your message of "Wed, 08 Jan 1997 14:37:26 EST." Date: Wed, 08 Jan 1997 13:48:59 -0800 Message-ID: <1025.852760139@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk yes, but for each problem they fixed, they added 2 more. :-) Seriously, avoid this unit like a case of ebola virus. > Last time the bitsurfr came up on this last it was to describe all the > problems with it. Has motorola fixed them? > thanks > ron > > Ron Minnich |"Failure is not an option" -- Gene Kranz > rminnich@sarnoff.com | -- except, of course, on Microsoft products > (609)-734-3120 | > ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html > > From owner-freebsd-hackers Wed Jan 8 13:53:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA02012 for hackers-outgoing; Wed, 8 Jan 1997 13:53:31 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA02001 for ; Wed, 8 Jan 1997 13:53:27 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA05082 for ; Wed, 8 Jan 1997 22:51:52 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA22605 for hackers@freebsd.org; Wed, 8 Jan 1997 22:51:52 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id WAA14740; Wed, 8 Jan 1997 22:35:36 +0100 (MET) Message-ID: Date: Wed, 8 Jan 1997 22:35:36 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: #include file xref philosophy References: <199701081012.FAA03591@hda.hda.com> <19970108121529.5416.qmail@suburbia.net> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970108121529.5416.qmail@suburbia.net>; from proff@suburbia.net on Jan 8, 1997 23:15:29 +1100 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As proff@suburbia.net wrote: > include/netinet/*.h are frightful. As a bunch of other things when > -DKERNEL is on. I don't have an argument against self-contained include files. However a note of warning: you are _never_ (really: never) supposed to compile any userland utility with -DKERNEL. (I think it should be renamed into _KERNE, so it's in the reserved namespaceL.) > Someone replied to me 'the magic is in the man page' This was only done in response to your claim that one must ``magically know'' what to include. Don't rip something off its context, and later reuse it as it seems it fits best for your argumentation purposes. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Wed Jan 8 14:22:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA03823 for hackers-outgoing; Wed, 8 Jan 1997 14:22:21 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA03811 for ; Wed, 8 Jan 1997 14:22:16 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA05836 for ; Wed, 8 Jan 1997 23:22:11 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA23252 for hackers@FreeBSD.ORG; Wed, 8 Jan 1997 23:22:11 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id XAA14816; Wed, 8 Jan 1997 23:00:21 +0100 (MET) Message-ID: Date: Wed, 8 Jan 1997 23:00:20 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: 2.2 BETA Upgrade Problem References: <9701081115.ZM12694@nevis.oss.uswest.net> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Chuck Robey on Jan 8, 1997 13:53:28 -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Chuck Robey wrote: > I just used nfs to load my new machine from an existing one. Didn't > have to go out of my little 2 machine net, but it worked line a > charm. Most of my 2.2-release-cycle tests have been installed over NFS, too. However, in my case the server is running FreeBSD-almost-current, not 2.1.something. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Wed Jan 8 14:22:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA03867 for hackers-outgoing; Wed, 8 Jan 1997 14:22:59 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA03862 for ; Wed, 8 Jan 1997 14:22:55 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA05856; Wed, 8 Jan 1997 23:22:23 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA23267; Wed, 8 Jan 1997 23:22:23 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id XAA14874; Wed, 8 Jan 1997 23:13:24 +0100 (MET) Message-ID: Date: Wed, 8 Jan 1997 23:13:24 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: mgessner@aristar.com (Matthew A. Gessner) Cc: hackers@freebsd.org (hackers) Subject: Re: ppp -direct problems References: <32D40441.41C67EA6@aristar.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <32D40441.41C67EA6@aristar.com>; from Matthew A. Gessner on Jan 8, 1997 15:32:01 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Matthew A. Gessner wrote: > #1: if my "remote" machine is 10.0.0.123 and my "host" is 10.0.0.3 how > do I > > a) set up tun0 (or do I use tun1 since I have a modem)? You don't -- PPP will do this for you. > b) set up the 'ifaddr' in ppp.secret and ppp.conf Not in ppp.secret, but in ppp.conf: set ifaddr 10.0.0.3 10.0.0.123 Note the leading space. I think you are also allowed to specify address ranges by appending a ``/'', so both PPPs can negotiate the address. One extreme of this is: set ifaddr 0.0.0.0/0 10.0.0.123 Your own address can become anything then, while you insist of a particular remote address. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Wed Jan 8 14:31:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA04352 for hackers-outgoing; Wed, 8 Jan 1997 14:31:19 -0800 (PST) Received: from horst.bfd.com (horst.bfd.com [204.160.242.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA04343 for ; Wed, 8 Jan 1997 14:31:16 -0800 (PST) Received: from harlie (bastion.bfd.com [204.160.242.14]) by horst.bfd.com (8.7.6/8.7.3) with SMTP id OAA14632; Wed, 8 Jan 1997 14:30:53 -0800 (PST) Date: Wed, 8 Jan 1997 14:30:53 -0800 (PST) From: "Eric J. Schwertfeger" X-Sender: ejs@harlie To: "Jordan K. Hubbard" cc: "Ron G. Minnich" , freebsd-hackers@freebsd.org Subject: Re: FreeBSD as an ISDN Router In-Reply-To: <1025.852760139@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 8 Jan 1997, Jordan K. Hubbard wrote: > yes, but for each problem they fixed, they added 2 more. :-) > > Seriously, avoid this unit like a case of ebola virus. > > > Last time the bitsurfr came up on this last it was to describe all the > > problems with it. Has motorola fixed them? > > thanks > > ron What's the best low-cost way to connect two FreeBSD boxes, then? I'm considering asking my supervisor for a perk rather than a pay raise, in the form of upgrading my 28.8 dedicated link to the office to an ISDN line, with a FreeBSD box on both ends. It'd cost me $500/month to get that from an ISP, but they can afford the bandwidth, so it would be purely a matter of line cost ($40 a month on each end plus hardware). Not that I really need more bandwidth at home, but who doesn't want it? Naturally, if the cost is $700+ on each end for ISDN routers, it isn't going to happen. Of course, at 115K async, it would only be a 50% improvement over 64K, so I'd like to find a way to use all the bandwidth as well, which the Bitsurfer pro will only do with a sync interface. From owner-freebsd-hackers Wed Jan 8 14:33:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA04528 for hackers-outgoing; Wed, 8 Jan 1997 14:33:18 -0800 (PST) Received: from po2.glue.umd.edu (root@po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA04523 for ; Wed, 8 Jan 1997 14:33:15 -0800 (PST) Received: from uplink.eng.umd.edu (uplink.eng.umd.edu [129.2.98.181]) by po2.glue.umd.edu (8.8.3/8.7.3) with ESMTP id RAA27590; Wed, 8 Jan 1997 17:33:13 -0500 (EST) Received: from localhost (chuckr@localhost) by uplink.eng.umd.edu (8.8.3/8.7.3) with SMTP id RAA08649; Wed, 8 Jan 1997 17:33:12 -0500 (EST) X-Authentication-Warning: uplink.eng.umd.edu: chuckr owned process doing -bs Date: Wed, 8 Jan 1997 17:33:11 -0500 (EST) From: Chuck Robey X-Sender: chuckr@uplink.eng.umd.edu To: andrew@pubnix.net cc: HawkeWerks Multimedia , freebsd-hackers@freebsd.org Subject: Re: FreeBSD as an ISDN Router ***Additional Info*** In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 8 Jan 1997, Andrew Webster wrote: > On Wed, 8 Jan 1997, HawkeWerks Multimedia wrote: > > > A few things I probably should have mentioned earlier. > > > > The routing will be over PPP, with Dynamic IP's. (I'll just use the > > 192.0.2.*) subnet for the internal routing) > > > > The box is currently running 2.1.5-RELEASE. > > Have you considered using RFC 1579 compliant non-routable internal > addresses "just in case": > 10.0.0.0 - 10.255.255.255 > 172.16.0.0 - 172.31.255.255 > 198.168.0.0 - 198.168.255.255 Excuse me, isn't that last one 192, not 198? > > Regards, > > Andrew Webster andrew@pubnix.net > PubNIX Montreal Connected to the world Branche au monde > P.O. Box 147 Cote Saint Luc, Quebec H4V 2Y3 > tel 514.990.5911 http://www.pubnix.net fax 514.990.9443 > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Wed Jan 8 14:46:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA05120 for hackers-outgoing; Wed, 8 Jan 1997 14:46:49 -0800 (PST) Received: from guardian.fortress.org (fortress.org [199.84.158.128]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA05107 for ; Wed, 8 Jan 1997 14:46:40 -0800 (PST) Received: (from andrew@localhost) by guardian.fortress.org (8.7.6/8.6.12) id RAA15562; Wed, 8 Jan 1997 17:46:03 -0500 (EST) Date: Wed, 8 Jan 1997 17:46:03 -0500 (EST) From: Andrew Webster Reply-To: andrew@pubnix.net To: Chuck Robey cc: HawkeWerks Multimedia , freebsd-hackers@freebsd.org Subject: Re: FreeBSD as an ISDN Router ***Additional Info*** In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 8 Jan 1997, Chuck Robey wrote: > On Wed, 8 Jan 1997, Andrew Webster wrote: > > > On Wed, 8 Jan 1997, HawkeWerks Multimedia wrote: > > > > > A few things I probably should have mentioned earlier. > > > > > > The routing will be over PPP, with Dynamic IP's. (I'll just use the > > > 192.0.2.*) subnet for the internal routing) > > > > > > The box is currently running 2.1.5-RELEASE. > > > > Have you considered using RFC 1579 compliant non-routable internal > > addresses "just in case": > > 10.0.0.0 - 10.255.255.255 > > 172.16.0.0 - 172.31.255.255 > > 198.168.0.0 - 198.168.255.255 > > Excuse me, isn't that last one 192, not 198? DOH! So much for typos! I've got stuff running here on 198.168, so I'm used to typing it... Andrew Webster andrew@pubnix.net PubNIX Montreal Connected to the world Branche au monde P.O. Box 147 Cote Saint Luc, Quebec H4V 2Y3 tel 514.990.5911 http://www.pubnix.net fax 514.990.9443 From owner-freebsd-hackers Wed Jan 8 14:54:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA05617 for hackers-outgoing; Wed, 8 Jan 1997 14:54:12 -0800 (PST) Received: from sumatra.americantv.com (sumatra.americantv.com [199.184.181.250]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA05609 for ; Wed, 8 Jan 1997 14:54:06 -0800 (PST) Received: from right.PCS (right.pcs. [148.105.10.31]) by sumatra.americantv.com (8.7.6/8.7.3) with ESMTP id QAA19043; Wed, 8 Jan 1997 16:50:34 -0600 (CST) Received: (jlemon@localhost) by right.PCS (8.6.13/8.6.4) id WAA02939; Wed, 8 Jan 1997 22:53:04 GMT Message-ID: Date: Wed, 8 Jan 1997 16:53:03 -0600 From: jlemon@americantv.com (Jonathan Lemon) To: jkh@time.cdrom.com ("Jordan K. Hubbard") Cc: hawke@hawkewerks.com (HawkeWerks Multimedia), freebsd-hackers@freebsd.org Subject: Re: FreeBSD as an ISDN Router References: <3.0.32.19970108104240.00d0a080@hawkewerks.com> <913.852759096@time.cdrom.com> X-Mailer: Mutt 0.56e Mime-Version: 1.0 In-Reply-To: <913.852759096@time.cdrom.com>; from "Jordan K. Hubbard" on Jan 8, 1997 13:31:36 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Jordan K. Hubbard" writes: > Unfortunately, the Motorola Bitsurfer is a festering piece-o-shit(tm) > and you'd do very well to stay away from it or anything else from > Motorola's communications products division. Cisco has also been > doing quite a bit of testing with their stuff, and the unanimous > decision seems to be "buy a modem or TA from Moto and you will lose." That's not quite fair. I have no opinion on the ISDN stuff, having never used it, but the Motorola Power modems are pretty good. Now, if you want to sling mud at modems, probably nothing is more deserving of the "piece-o-shit" label than the USR's Sportster line. -- Jonathan From owner-freebsd-hackers Wed Jan 8 15:02:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA06261 for hackers-outgoing; Wed, 8 Jan 1997 15:02:39 -0800 (PST) Received: from guardian.fortress.org (fortress.org [199.84.158.128]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA06256 for ; Wed, 8 Jan 1997 15:02:33 -0800 (PST) Received: (from andrew@localhost) by guardian.fortress.org (8.7.6/8.6.12) id RAA15562; Wed, 8 Jan 1997 17:46:03 -0500 (EST) Date: Wed, 8 Jan 1997 17:46:03 -0500 (EST) From: Andrew Webster Reply-To: andrew@pubnix.net To: Chuck Robey cc: HawkeWerks Multimedia , freebsd-hackers@freebsd.org Subject: Re: FreeBSD as an ISDN Router ***Additional Info*** In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 8 Jan 1997, Chuck Robey wrote: > On Wed, 8 Jan 1997, Andrew Webster wrote: > > > On Wed, 8 Jan 1997, HawkeWerks Multimedia wrote: > > > > > A few things I probably should have mentioned earlier. > > > > > > The routing will be over PPP, with Dynamic IP's. (I'll just use the > > > 192.0.2.*) subnet for the internal routing) > > > > > > The box is currently running 2.1.5-RELEASE. > > > > Have you considered using RFC 1579 compliant non-routable internal > > addresses "just in case": > > 10.0.0.0 - 10.255.255.255 > > 172.16.0.0 - 172.31.255.255 > > 198.168.0.0 - 198.168.255.255 > > Excuse me, isn't that last one 192, not 198? DOH! So much for typos! I've got stuff running here on 198.168, so I'm used to typing it... Andrew Webster andrew@pubnix.net PubNIX Montreal Connected to the world Branche au monde P.O. Box 147 Cote Saint Luc, Quebec H4V 2Y3 tel 514.990.5911 http://www.pubnix.net fax 514.990.9443 From owner-freebsd-hackers Wed Jan 8 15:19:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA07432 for hackers-outgoing; Wed, 8 Jan 1997 15:19:36 -0800 (PST) Received: from plains.nodak.edu (tinguely@plains.NoDak.edu [134.129.111.64]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA07411 for ; Wed, 8 Jan 1997 15:19:30 -0800 (PST) Received: (from tinguely@localhost) by plains.nodak.edu (8.8.3/8.8.3) id RAA28628 for freebsd-hackers@freebsd.org; Wed, 8 Jan 1997 17:19:27 -0600 (CST) Date: Wed, 8 Jan 1997 17:19:27 -0600 (CST) From: Mark Tinguely Message-Id: <199701082319.RAA28628@plains.nodak.edu> To: freebsd-hackers@freebsd.org Subject: FYI: P6 configure (from news) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk taken from news: ------------- From: Andrew Vanderstock Subject: P6 PCI enabler (Was: Re: 3D MUCH FASTER THAN MATROX) Date: Wed, 08 Jan 1997 21:21:50 +1100 Organization: St Vincent's Hospital, Melbourne Message-ID: <32D3753E.25EE@greebo.svhm.org.au> I'm working on a P6 "enabler" which will enable write combining and setup the fastest possible MTTR setup for unixes pretty much automatically. It will also have a "danger! danger!" PCI write posting option for the Orion and will automatically enable PCI write posting for all 440FX Natoma's. It will be for free unixes (Linux first, others when they test it out :-) and source will be provided. SMP support will probably be a 1.1 revision, as all processors have to run the same MTRR config and I don't have a SMP machine to test it with. These options boosted my throughput on my HP VT6/150 with the duff Orion >from 5.8 MB/s to 56 MB/s using SciTech's display doctor under Win95, and moved my xbench scores for my Millennium to within 70% of a 200 MHz Natoma PPro (I'm not going to mention xbench figures, as the driver has not been released, and the scores may go down after we finish getting all the bugs out - suffice to say that we have done good in this version :-). I'm hoping by correctly setting write back, write posting and setting the "holes" up correctly, I might get even closer. Natomas are capable of 92 MB/s to the PCI bus, about 12 MB/s more than the fastest Triton revision to date. This enabler, yet to be titled, is not part of Xfree86, and you can read all about in a few weeks in http://www.x86.com (when I've finished the enabler and written the article). [deleted] From owner-freebsd-hackers Wed Jan 8 15:22:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA07729 for hackers-outgoing; Wed, 8 Jan 1997 15:22:53 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA07720 for ; Wed, 8 Jan 1997 15:22:47 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA17253; Wed, 8 Jan 1997 16:10:11 -0700 From: Terry Lambert Message-Id: <199701082310.QAA17253@phaeton.artisoft.com> Subject: Re: FreeBSD as an ISDN Router To: jlemon@americantv.com (Jonathan Lemon) Date: Wed, 8 Jan 1997 16:10:11 -0700 (MST) Cc: jkh@time.cdrom.com, hawke@hawkewerks.com, freebsd-hackers@freebsd.org In-Reply-To: from "Jonathan Lemon" at Jan 8, 97 04:53:03 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > "Jordan K. Hubbard" writes: > > Unfortunately, the Motorola Bitsurfer is a festering piece-o-shit(tm) > > and you'd do very well to stay away from it or anything else from > > Motorola's communications products division. Cisco has also been > > doing quite a bit of testing with their stuff, and the unanimous > > decision seems to be "buy a modem or TA from Moto and you will lose." > > That's not quite fair. I have no opinion on the ISDN stuff, having never > used it, but the Motorola Power modems are pretty good. Now, if you want > to sling mud at modems, probably nothing is more deserving of the > "piece-o-shit" label than the USR's Sportster line. The Sportster 14.4 FAXmodem (I believe) is theonly one affected, and it's only a problem if you talk to Rockwell chipset modems on the other end. US Robotics has a fix (firmware) for it anyway. The Motorola modem problems don't all have easy fixes. Don't get me wrong; I'm a big fan of Motorola, normally, but the Bitsurfer is known to be a problem in all its incarnations so far; the Sportster, on the other hand, is a problem in a single incarnation, and has a fix available... it's no worse than some Seagate and Connor SCSI drives and tagged command queueing. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jan 8 15:24:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA07821 for hackers-outgoing; Wed, 8 Jan 1997 15:24:02 -0800 (PST) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA07807 for ; Wed, 8 Jan 1997 15:23:58 -0800 (PST) Received: from ct.picker.com by whqvax.picker.com with SMTP; Wed, 8 Jan 1997 18:22:57 -0500 (EST) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA23289; Wed, 8 Jan 97 18:22:54 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id SAA23636; Wed, 8 Jan 1997 18:21:30 -0500 Message-Id: Date: Wed, 8 Jan 1997 18:21:30 -0500 From: rhh@ct.picker.com (Randall Hopper) To: henrich@crh.cl.msu.edu (Charles Henrich) Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: A cool xterm? References: <199701052059.PAA04010@crh.cl.msu.edu> X-Mailer: Mutt 0.56 Mime-Version: 1.0 In-Reply-To: <199701052059.PAA04010@crh.cl.msu.edu>; from Charles Henrich on Jan 5, 1997 15:59:48 -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Charles Henrich: |Has anyone out there ever found a nice terminal window, something like Dec's |mterm, or ssh for windows, or even better, NeXT's terminal? Xterm is peachy, |except the scrollback just sucks :) Rebuilt the color_xterm port linking with Xaw3d instead of Xaw, and the scrollbar's much better. Like the menus better too. ...with these resources: *scrollBar: true *VT100.scrollbar.background: gray40 *SimpleMenu*Cursor: hand2 *SimpleMenu*background: gray40 *SimpleMenu*foreground: yellow *SimpleMenu*borderWidth: 2 *SimpleMenu*borderColor: #c0c0c0 *SimpleMenu*vertSpace: 0 *VT100*color0: black *VT100*color1: red3 *VT100*color2: green3 *VT100*color3: yellow3 *VT100*color4: blue3 *VT100*color5: magenta3 *VT100*color6: cyan3 *VT100*color7: gray90 Randall Hopper From owner-freebsd-hackers Wed Jan 8 15:29:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA08079 for hackers-outgoing; Wed, 8 Jan 1997 15:29:40 -0800 (PST) Received: from sumatra.americantv.com (sumatra.americantv.com [199.184.181.250]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA08069 for ; Wed, 8 Jan 1997 15:29:34 -0800 (PST) Received: from right.PCS (right.pcs. [148.105.10.31]) by sumatra.americantv.com (8.7.6/8.7.3) with ESMTP id RAA19148; Wed, 8 Jan 1997 17:26:30 -0600 (CST) Received: (jlemon@localhost) by right.PCS (8.6.13/8.6.4) id XAA10838; Wed, 8 Jan 1997 23:28:59 GMT Message-ID: Date: Wed, 8 Jan 1997 17:28:58 -0600 From: jlemon@americantv.com (Jonathan Lemon) To: terry@lambert.org (Terry Lambert) Cc: jkh@time.cdrom.com, hawke@hawkewerks.com, freebsd-hackers@freebsd.org Subject: Re: FreeBSD as an ISDN Router References: <199701082310.QAA17253@phaeton.artisoft.com> X-Mailer: Mutt 0.56e Mime-Version: 1.0 In-Reply-To: <199701082310.QAA17253@phaeton.artisoft.com>; from Terry Lambert on Jan 8, 1997 16:10:11 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert writes: > > "Jordan K. Hubbard" writes: > > > Unfortunately, the Motorola Bitsurfer is a festering piece-o-shit(tm) > > > and you'd do very well to stay away from it or anything else from > > > Motorola's communications products division. Cisco has also been > > > doing quite a bit of testing with their stuff, and the unanimous > > > decision seems to be "buy a modem or TA from Moto and you will lose." > > > > That's not quite fair. I have no opinion on the ISDN stuff, having never > > used it, but the Motorola Power modems are pretty good. Now, if you want > > to sling mud at modems, probably nothing is more deserving of the > > "piece-o-shit" label than the USR's Sportster line. > > The Sportster 14.4 FAXmodem (I believe) is theonly one affected, and > it's only a problem if you talk to Rockwell chipset modems on the > other end. The 28.8k, 33.6k, and PCMCIA modems also have problems. And while USR now has fixes for most of them, the companay also spent an inordinate amount of time denying that there was a problem in the first place. (Go visit comp.dcom.modems for any length of time). Most of the Motorola modems are also flash-upgradable, and Motorola has made firmware upgrades available pretty quickly in the past. (cf: firmware upgrades for Power series) Not that this has anything to do with the Bitsurfer, so I'll shut up now. -- Jonathan From owner-freebsd-hackers Wed Jan 8 15:31:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA08245 for hackers-outgoing; Wed, 8 Jan 1997 15:31:24 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA08234 for ; Wed, 8 Jan 1997 15:31:19 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id SAA03442; Wed, 8 Jan 1997 18:31:17 -0500 (EST) From: Charles Henrich Message-Id: <199701082331.SAA03442@crh.cl.msu.edu> Subject: Re: A cool xterm? To: rhh@ct.picker.com (Randall Hopper) Date: Wed, 8 Jan 1997 18:31:17 -0500 (EST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from Randall Hopper at "Jan 8, 97 06:21:30 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Charles Henrich: > |Has anyone out there ever found a nice terminal window, something like Dec's > |mterm, or ssh for windows, or even better, NeXT's terminal? Xterm is peachy > |except the scrollback just sucks :) > > Rebuilt the color_xterm port linking with Xaw3d instead of Xaw, and the > scrollbar's much better. Like the menus better too. ...with these resources: Its not the scrollbar that annoys me, its the scrollback functionality (e.g. clear screen should write the contents of the current screen into the scrollback, not just erase em!) -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Wed Jan 8 15:42:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA09091 for hackers-outgoing; Wed, 8 Jan 1997 15:42:18 -0800 (PST) Received: from wong.rogerswave.ca (a17b32.rogerswave.ca [204.92.17.32]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA09058 for ; Wed, 8 Jan 1997 15:42:11 -0800 (PST) Received: (from wong@localhost) by wong.rogerswave.ca (8.7.5/8.7.3) id SAA00356; Wed, 8 Jan 1997 18:42:07 -0500 (EST) Date: Wed, 8 Jan 1997 18:42:07 -0500 (EST) From: Ken Wong X-Sender: wong@wong.rogerswave.ca Reply-To: wong@rogerswave.ca To: proff@suburbia.net cc: hackers@FreeBSD.ORG Subject: Re: mmap() updates...how often? In-Reply-To: <19970108014639.14401.qmail@suburbia.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 8 Jan 1997 proff@suburbia.net wrote: > > Why not just put them all in the same process group, and send the process > group a SIGUSR1 when new data is ready in the mmaped region? > Is Signal delivery quaranteed in FreeBSD? I mean if 2 or more signals are sent to a process at the same time. does it quene up the signals? Ken From owner-freebsd-hackers Wed Jan 8 16:20:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA12945 for hackers-outgoing; Wed, 8 Jan 1997 16:20:22 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA12939 for ; Wed, 8 Jan 1997 16:20:20 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id QAA02361 for ; Wed, 8 Jan 1997 16:21:06 -0800 (PST) Received: (qmail 25946 invoked by uid 110); 9 Jan 1997 00:19:45 -0000 Message-ID: <19970109001944.25945.qmail@suburbia.net> Subject: Re: potential for panic In-Reply-To: from Michael Hancock at "Jan 9, 97 08:57:31 am" To: michaelh@cet.co.jp (Michael Hancock) Date: Thu, 9 Jan 1997 11:19:44 +1100 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Wed, 1 Jan 1997, Poul-Henning Kamp wrote: > > > > > TAILQ_REMOVE and STAILQ_REMOVE would panic with a zero dereference > > if you tried to remove something not on the queue. > > > > Wouldn't it make sense to avoid that, or would the overhead be considered > > prohibitive ? #ifdef DIAGNOSTIC check #endif is what it needs -Julian From owner-freebsd-hackers Wed Jan 8 16:43:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA14118 for hackers-outgoing; Wed, 8 Jan 1997 16:43:11 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA14113 for ; Wed, 8 Jan 1997 16:43:07 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id LAA22928; Thu, 9 Jan 1997 11:12:40 +1030 (CST) From: Michael Smith Message-Id: <199701090042.LAA22928@genesis.atrad.adelaide.edu.au> Subject: Re: Year 2000 time change(Format support) In-Reply-To: <199701081022.CAA25400@freefall.freebsd.org> from Darren Reed at "Jan 8, 97 09:22:29 pm" To: avalon@coombs.anu.edu.au (Darren Reed) Date: Thu, 9 Jan 1997 11:12:39 +1030 (CST) Cc: wilko@yedi.iaf.nl, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Darren Reed stands accused of saying: > > Are there any cases where software calculates a year that is in the range > 0-99 and then adds that to 1900 ? > > Or any that displays 19%d ? Why would you? Anyone with half a brain is just going to use strftime(). > darren -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Wed Jan 8 16:54:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA14591 for hackers-outgoing; Wed, 8 Jan 1997 16:54:37 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA14585 for ; Wed, 8 Jan 1997 16:54:32 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA17405; Wed, 8 Jan 1997 17:42:48 -0700 From: Terry Lambert Message-Id: <199701090042.RAA17405@phaeton.artisoft.com> Subject: Re: mmap() updates...how often? To: wong@rogerswave.ca Date: Wed, 8 Jan 1997 17:42:47 -0700 (MST) Cc: proff@suburbia.net, hackers@freebsd.org In-Reply-To: from "Ken Wong" at Jan 8, 97 06:42:07 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Wed, 8 Jan 1997 proff@suburbia.net wrote: > > > > > Why not just put them all in the same process group, and send the process > > group a SIGUSR1 when new data is ready in the mmaped region? > > > Is Signal delivery quaranteed in FreeBSD? I mean if 2 or more signals > are sent to a process at the same time. does it quene up the signals? One signal: raise condition Two signals: rais condition for first, queue second behind mask (assume it doesn't come in during race window before masking) Three signals: You are SOL. Signals are persistent conditions, not events; to use EE jargon, they are level triggered, not edge triggered. In point of fact, no signal system compliant with currently ratified POSIX standards will queue signals for delivery in FIFO (or any other, for that matter) order. Search for "POSIX +reliable +signals" on the AltaVista search site for information on POSIX standards currently in committee for event style signal queueing. Most likely you are trying to notify a process of multiple events, and you are trying to use a non-event interface (signals) to do it. Don't. Solve the problem some other way (UNIX domain sockets, pipes, message queues, counting semaphores, etc. ...there are literally dozens of alternatives). The only thing signals are barely useful for is one shot conditions (like sending HUPCL to all processes in a process group for on-to-off DCD transition on a tty line, something that can happen only once in the lifetime of the session) and for one of many events (like sending SIGCHLD when a child process dies, after which you are expected to reap as many children as you can because the signal for subsequent processes could be lost). In the second case, the processing of the signal is not as important as its mere existance: you should set a volatile flag and do your processing in your main loop -- *NOT* in the signal handler -- to close any potential race window on delivery/unmask. See the init, xdm, and inetd code for sample implementations. of "one of many". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jan 8 20:31:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA27900 for hackers-outgoing; Wed, 8 Jan 1997 20:31:21 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id UAA27891 for ; Wed, 8 Jan 1997 20:31:17 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0viC8r-0004AG-00; Wed, 8 Jan 1997 21:31:01 -0700 To: andrew@pubnix.net Subject: Re: FreeBSD as an ISDN Router ***Additional Info*** Cc: HawkeWerks Multimedia , freebsd-hackers@freebsd.org In-reply-to: Your message of "Wed, 08 Jan 1997 14:34:06 EST." References: Date: Wed, 08 Jan 1997 21:31:00 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Andrew Webster writes: : > 192.0.2.*) subnet for the internal routing) : Have you considered using RFC 1579 compliant non-routable internal : addresses "just in case": 192.0.2.* has for a very long time been officially the test network.... Just look in the assigned numbers :-). Warner From owner-freebsd-hackers Wed Jan 8 20:35:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA28263 for hackers-outgoing; Wed, 8 Jan 1997 20:35:57 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA28257 for ; Wed, 8 Jan 1997 20:35:55 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id XAA06374 for freebsd-hackers@freebsd.org; Wed, 8 Jan 1997 23:35:51 -0500 (EST) From: Charles Henrich Message-Id: <199701090435.XAA06374@crh.cl.msu.edu> Subject: is time() valid in kernel? To: freebsd-hackers@freebsd.org Date: Wed, 8 Jan 1997 23:35:51 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I want to have the kernel time how long sync() takes in the vfs_update() routine, is it legit to throw in a standard call to gettimeofday() or is there a cooler (e.g. macro) that will give me the time so I can find out how long this sucker is taking? Why: I want to experiment changing how frequently update() runs on a busy newserver, and see what the time differences are. I have a gut-feeling that changing it from 30 seconds to 300 or more seconds wont significantly increase the sync() time, but as I'm now doing it 1/10th as often I get a large performance win.. [This system is attached to a UPS that notifies FreeBSD when the power drops which starts doing sync's and after a few minutes shuts down] -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Wed Jan 8 20:38:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA28402 for hackers-outgoing; Wed, 8 Jan 1997 20:38:27 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id UAA28397 for ; Wed, 8 Jan 1997 20:38:24 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0viCEE-0004AT-00; Wed, 8 Jan 1997 21:36:34 -0700 To: Terry Lambert Subject: Re: mmap() updates...how often? Cc: wong@rogerswave.ca, proff@suburbia.net, hackers@freebsd.org In-reply-to: Your message of "Wed, 08 Jan 1997 17:42:47 MST." <199701090042.RAA17405@phaeton.artisoft.com> References: <199701090042.RAA17405@phaeton.artisoft.com> Date: Wed, 08 Jan 1997 21:36:34 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The normal way that I've seen this sort of signalling done in the past is a pipe and a single byte write... Much more reliable than signals, but likely a little slower. Warner From owner-freebsd-hackers Wed Jan 8 21:02:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA00293 for hackers-outgoing; Wed, 8 Jan 1997 21:02:26 -0800 (PST) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA00276 for ; Wed, 8 Jan 1997 21:02:23 -0800 (PST) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.3/8.7.3) with SMTP id AAA08448; Thu, 9 Jan 1997 00:02:15 -0500 (EST) Message-Id: <199701090502.AAA08448@whizzo.transsys.com> X-Mailer: exmh version 2.0alpha 12/3/96 To: Charles Henrich cc: freebsd-hackers@freebsd.org From: "Louis A. Mamakos" Subject: Re: is time() valid in kernel? References: <199701090435.XAA06374@crh.cl.msu.edu> In-reply-to: Your message of "Wed, 08 Jan 1997 23:35:51 EST." <199701090435.XAA06374@crh.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Jan 1997 00:02:15 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I think that you want to use microtime() to capture the current time whilst timestamping events in the kernel. There's some code that I submitted a while ago which timestamps messages queued to UDP sockets based on a socket option; take a look at /sys/netinet/udp_usrreq.c for the code. louie From owner-freebsd-hackers Wed Jan 8 21:04:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA00717 for hackers-outgoing; Wed, 8 Jan 1997 21:04:36 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA00700 for ; Wed, 8 Jan 1997 21:04:33 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id AAA06512; Thu, 9 Jan 1997 00:04:26 -0500 (EST) From: Charles Henrich Message-Id: <199701090504.AAA06512@crh.cl.msu.edu> Subject: Re: is time() valid in kernel? To: louie@TransSys.COM (Louis A. Mamakos) Date: Thu, 9 Jan 1997 00:04:25 -0500 (EST) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199701090502.AAA08448@whizzo.transsys.com> from "Louis A. Mamakos" at "Jan 9, 97 00:02:15 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I think that you want to use microtime() to capture the current time > whilst timestamping events in the kernel. There's some code that I > submitted a while ago which timestamps messages queued to UDP sockets > based on a socket option; take a look at /sys/netinet/udp_usrreq.c > for the code. Cool, thanks much! -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Wed Jan 8 21:20:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA03112 for hackers-outgoing; Wed, 8 Jan 1997 21:20:39 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id VAA03098 for ; Wed, 8 Jan 1997 21:20:36 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA20610; Thu, 9 Jan 1997 00:20:03 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Thu, 9 Jan 1997 00:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id WAA17542; Wed, 8 Jan 1997 22:15:30 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id WAA05201; Wed, 8 Jan 1997 22:18:48 -0500 (EST) Date: Wed, 8 Jan 1997 22:18:48 -0500 (EST) From: Thomas David Rivers Message-Id: <199701090318.WAA05201@lakes.water.net> To: chuckr@glue.umd.edu, ponds!uswest.net!greg Subject: Re: 2.2 BETA Upgrade Problem Cc: ponds!FreeBSD.ORG!hackers Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Chuck Robey writes: > On Wed, 8 Jan 1997, Greg Rowe wrote: > .... description of problem installing 2.2-BETA upgrade over NFS ... > > > I just used nfs to load my new machine from an existing one. Didn't have > to go out of my little 2 machine net, but it worked line a charm. > I'll have to chime in here with another data point. I installed the 2.2-BETA using NFS, and that was SL/IP - not even ethernet. However - the difference is that I did a full install; from scratch. I didn't do an upgrade of an existing system. I believe Greg's problem was with an upgrade... - Dave Rivers - From owner-freebsd-hackers Thu Jan 9 00:02:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA14905 for hackers-outgoing; Thu, 9 Jan 1997 00:02:09 -0800 (PST) Received: from casparc.ppp.net (casparc.ppp.net [194.64.12.35]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id AAA14898 for ; Thu, 9 Jan 1997 00:02:05 -0800 (PST) Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0viFR4-000IEdC; Thu, 9 Jan 97 09:02 MET Received: by ernie.kts.org (Smail3.1.29.1 #5) id m0viEmd-00001XC; Thu, 9 Jan 97 08:20 MET Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: random number kernel call ? To: freebsd-hackers@freebsd.org Date: Thu, 9 Jan 1997 08:20:15 +0100 (MET) Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I need 7bit and 16bit random numbers in a driver - does the kernel provide such a (documented) service ? hellmuth -- hellmuth michaelis hm@kts.org hamburg, europe From owner-freebsd-hackers Thu Jan 9 00:32:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA15618 for hackers-outgoing; Thu, 9 Jan 1997 00:32:16 -0800 (PST) Received: from monk.via.net (monk.via.net [140.174.204.10]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id AAA15612 for ; Thu, 9 Jan 1997 00:32:14 -0800 (PST) Received: (from joe@localhost) by monk.via.net (8.6.11/8.6.12) id AAA04364 for freebsd-hackers@freebsd.org; Thu, 9 Jan 1997 00:31:32 -0800 Date: Thu, 9 Jan 1997 00:31:32 -0800 From: Joe McGuckin Message-Id: <199701090831.AAA04364@monk.via.net> To: freebsd-hackers@freebsd.org Subject: CCD questions (news server) X-Sun-Charset: US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just switched over our news machine from a tired old Sun SS2 (with Weitek upgrade) to a 133Mhz pentium with 12G of Barracudas ccd'd together, I arbitrarily set the interleave to 64. Is there a good method to derive the optimal interleave factor? I'm using a flags value of zero. How can I expect flag values of CCDF_SWAP and CCDF_UNIFORM to affect performance? My initial experiences are very positive. The machine seems to process articles about three to five times faster than the Sun with a load factor that never goes above .45 (so far, only one of our incoming feeds has switched over to the new machine). I'm very impressed. Especially if you consider that no performance tuning of the system or INN has been done yet. I'm not using MMAP yet because there seems to be some question as to how well it works for INN. Has anyone ever put together multiple machine 'news farms'? I'd like to find out what's been done so far. -joe From owner-freebsd-hackers Thu Jan 9 00:56:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA16363 for hackers-outgoing; Thu, 9 Jan 1997 00:56:16 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA16358 for ; Thu, 9 Jan 1997 00:56:14 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id AAA02384; Thu, 9 Jan 1997 00:56:06 -0800 (PST) To: "Eric J. Schwertfeger" cc: "Ron G. Minnich" , freebsd-hackers@freebsd.org Subject: Re: FreeBSD as an ISDN Router In-reply-to: Your message of "Wed, 08 Jan 1997 14:30:53 PST." Date: Thu, 09 Jan 1997 00:56:06 -0800 Message-ID: <2380.852800166@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > What's the best low-cost way to connect two FreeBSD boxes, then? I'm > considering asking my supervisor for a perk rather than a pay raise, in Buy a pair of ADTRAN TAs, the low-cost one (whatever the L1-Express turned into - my particular model isn't made anymore) doesn't run much more than $340 I think. I haven't checked prices lately, and it's easily possible that they've gone to less than this. Jordan From owner-freebsd-hackers Thu Jan 9 01:01:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA16690 for hackers-outgoing; Thu, 9 Jan 1997 01:01:30 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA16684 for ; Thu, 9 Jan 1997 01:01:26 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id BAA02406; Thu, 9 Jan 1997 01:01:16 -0800 (PST) To: jlemon@americantv.com (Jonathan Lemon) cc: hawke@hawkewerks.com (HawkeWerks Multimedia), freebsd-hackers@freebsd.org Subject: Re: FreeBSD as an ISDN Router In-reply-to: Your message of "Wed, 08 Jan 1997 16:53:03 CST." Date: Thu, 09 Jan 1997 01:01:16 -0800 Message-ID: <2402.852800476@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > That's not quite fair. I have no opinion on the ISDN stuff, having never > used it, but the Motorola Power modems are pretty good. Now, if you want Hmmmm. Take a look at their AT command set reference, see some of the perversions they made to it. Now try their new dialing command. Notice how it locks you into pulse dial until you power cycle the unit. Try turning down the volume on your speaker with the documented commands for this. Try it on a noisy line. Trust me, this modem has problems. :-) > to sling mud at modems, probably nothing is more deserving of the > "piece-o-shit" label than the USR's Sportster line. Naw, I couldn't say that about the sportster. "Flaming piece-o-shit" would, I think, be more accurate given their old habit of bursting into open flames if you stacked two on top of eachother. :-) I wouldn't recommend the USRs either, though I have to admit that I use quite a few of them at Walnut Creek CDROM (they're cheap and hardly ever ignite with the new power transformer design). I suppose if you want a nice modem, you have to buy a Fujitsu or a Zyxel, but how many stores do you know that carry those? Exactly. :-( Jordan From owner-freebsd-hackers Thu Jan 9 01:18:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA17690 for hackers-outgoing; Thu, 9 Jan 1997 01:18:00 -0800 (PST) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA17676 for ; Thu, 9 Jan 1997 01:17:57 -0800 (PST) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.6/8.7.3) with ESMTP id BAA00336; Thu, 9 Jan 1997 01:17:49 -0800 (PST) Message-Id: <199701090917.BAA00336@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: "Eric J. Schwertfeger" cc: "Jordan K. Hubbard" , "Ron G. Minnich" , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD as an ISDN Router In-reply-to: Your message of "Wed, 08 Jan 1997 14:30:53 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Jan 1997 01:17:48 -0800 From: Amancio Hasty Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of "Eric J. Schwertfeger" : > > > On Wed, 8 Jan 1997, Jordan K. Hubbard wrote: > > Naturally, if the cost is $700+ on each end for ISDN routers, it isn't > going to happen. Of course, at 115K async, it would only be a 50% > improvement over 64K, so I'd like to find a way to use all the bandwidth > as well, which the Bitsurfer pro will only do with a sync interface. Well, I have an Ascend Pipeline 50 which didn't like mbone traffic however after I upgraded to their latest software rev level is now working okay. My router is used to crash anything upstream that bear the name Ascend and then finally it would nuke itself -- all with mbone traffic naturally 8) After a year or so Ascend has fixed all my problems and I happy with my setup -- I just want mo' bandwith 8) The good thing about the ascend is that I didn't have to write a driver for the router and it is somewhat supported -- I suspect their support is a lot better nowdays. Now the small issue of support,the need not write a driver , plus OS independent interface is a *big* plus . Now someone ought to really concentrate on providing a driver for a popular ISDN card here in the US -- specially, if the driver / card can support, data on one channel, voice/fax on the other or data on both channels -- in other words flexible for the SOHO market. Perhaps, someone in the linux group has a solution which we can port --- I wouldn't be shy about such effort if I was doing the work and not getting paid for it 8) Regards, Amancio From owner-freebsd-hackers Thu Jan 9 02:08:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA20623 for hackers-outgoing; Thu, 9 Jan 1997 02:08:58 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA20608 for ; Thu, 9 Jan 1997 02:08:55 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.7.6/8.7.3) with SMTP id CAA09275 for ; Thu, 9 Jan 1997 02:08:54 -0800 (PST) Date: Thu, 9 Jan 1997 02:08:54 -0800 (PST) From: Jaye Mathisen To: hackers@freebsd.org Subject: 2.2-BETA install report, minor problems. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 1) Configuring local time zone results in a "copied" message after copying the file which seems a little redundant give that you just selected what you wanted to do, it asked to confirm it, and then tells you that it did it. Time consuming. 2) The box I was installing on had BSD/OS installed on it. For whatever reason, Custom -> Options -> Labels would *not* result in an installable disk. The newfs of the /usr partition would fail with invalid block numbers and such. In fact, it decided my 1 GB Conner disk was a 2 GB disk, and merrily went through all the config stuff, up until the newfs, which failed trying to write past the end of media. I tried everything I could think of. fdisk shows totally bizarre numbers for the partition table, and the only way I could get the damn thing to install properly was to low-level format the disk from my Adaptec controller. (BTW, this was on a P100, 2 Conner 1GB disks, 2 conner 4GB disks). After that, the install worked fine. However, even now, When I run disklabel auto on the 4GB disks, it fails with all kinds of errors about end-of-media stuff. Low level format cleaned it right up, but it seems unnecessary. From owner-freebsd-hackers Thu Jan 9 02:27:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA21543 for hackers-outgoing; Thu, 9 Jan 1997 02:27:34 -0800 (PST) Received: from plato.salford.ac.uk (plato.salford.ac.uk [146.87.1.3]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA21516 for ; Thu, 9 Jan 1997 02:27:26 -0800 (PST) Received: (qmail 18989 invoked by uid 141); 9 Jan 1997 10:27:22 -0000 Date: Thu, 9 Jan 1997 10:27:22 +0000 (GMT) From: Mark Powell To: Lindsay Computer Systems cc: freebsd-hackers@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: Can the P/I-P55T2P4 be overclocked? In other words does it support 75 and 83MHz bus speeds? In-Reply-To: <199701081734.LAA18011@jump.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 8 Jan 1997, Lindsay Computer Systems wrote: > On 8 Jan 1997 17:08:23 -0000, mark@plato.salford.ac.uk wrote: > >>The ATX (XP55T2P4) Revision 3.0 does NOT have 75Mhz or 83Mhz settings. > >>The P55T2P4-S has the third jumper soldered over to preclude 75Mhz or > >>83Mhz. settings. > >Rick, are you saying that the only board that supports 75 and 83 is > >the plain T2P4 rev. >= 3.0? I was going to get a T2P4S for the SCSI, > >but will get a seperate 2940UW if necessary to get the 75MHz bus speed. > > Correct, only the plain P55T2P4 rev. 3.0/3.1 have everything needed to do 75 & 83Mhz, > but I seriously doubt that a heavily loaded 2940 will perform well above 33Mhz PCI bus > speeds.... Why's that? Also, what d'you mean by "well"? > The SC-200 and the SC-875 stand a much better chance of running well at higher PCI > bus speeds when drives are attached that fully use their capabilities. Not too sure on the quality of the FreeBSD drivers for the NCR though. And I don't think the NCR 53c875 is supported at all, just 810 & 825 :( Suppose, I could just use narrow drives instead of the wides I currently have? Hmmm, I really wanted to overclock a Cyrix 6x86 P166+ to a P200+, and this seemed to be the way to do it from other's expericence. Do you have any idea whether the DFI G586VPS Pro (using VLSI Lunx chipset) or the or the MTech R534 (http://www.mtiusa.com/r534.htm), using the Sis5571 chipset which I think I read somewhere "allows the PCI bus to be locked at 32MHz [sic?] whatever the external clock speed", would be better for this purpose? > Rick Lindsay, Lindsay Computer Systems, http://www.jump.net/~lcs/ > Voice: 512-719-5257, Austin, Texas Sorry for all the questions, Rick, but you do seem to know your stuff :) Cheers. Mark Powell - Unix Information Officer - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 745 5936 Fax: +44 161 736 3596 Email: mark@salford.ac.uk finger mark@ucsalf.ac.uk (for PGP key) Home Page From owner-freebsd-hackers Thu Jan 9 03:29:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA23951 for hackers-outgoing; Thu, 9 Jan 1997 03:29:03 -0800 (PST) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id DAA23940 for ; Thu, 9 Jan 1997 03:28:51 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr2-37.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA29314 (5.67b/IDA-1.5 for ); Thu, 9 Jan 1997 12:28:14 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.4/8.6.9) id MAA06104; Thu, 9 Jan 1997 12:27:29 +0100 (CET) Message-Id: Date: Thu, 9 Jan 1997 12:26:09 +0100 From: se@freebsd.org (Stefan Esser) To: tinguely@plains.nodak.edu (Mark Tinguely) Cc: freebsd-hackers@freebsd.org Subject: Re: FYI: P6 configure (from news) References: <199701082319.RAA28628@plains.nodak.edu> X-Mailer: Mutt 0.55-PL15 Mime-Version: 1.0 In-Reply-To: <199701082319.RAA28628@plains.nodak.edu>; from Mark Tinguely on Jan 8, 1997 17:19:27 -0600 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Jan 8, tinguely@plains.nodak.edu (Mark Tinguely) wrote: > taken from news: > ------------- > > From: Andrew Vanderstock > Subject: P6 PCI enabler (Was: Re: 3D MUCH FASTER THAN MATROX) > Date: Wed, 08 Jan 1997 21:21:50 +1100 > Organization: St Vincent's Hospital, Melbourne > Message-ID: <32D3753E.25EE@greebo.svhm.org.au> > > I'm working on a P6 "enabler" which will enable write combining and > setup the fastest possible MTTR setup for unixes pretty much > automatically. It will also have a "danger! danger!" PCI write posting > option for the Orion and will automatically enable PCI write posting for > all 440FX Natoma's. It will be for free unixes (Linux first, others when > they test it out :-) and source will be provided. SMP support will > probably be a 1.1 revision, as all processors have to run the same MTRR > config and I don't have a SMP machine to test it with. I will look at the code when it is released, and will integrate it into the FreeBSD PCI code ... Regards, STefan From owner-freebsd-hackers Thu Jan 9 05:52:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA29972 for hackers-outgoing; Thu, 9 Jan 1997 05:52:38 -0800 (PST) Received: from nevis.oss.uswest.net (nevis.oss.uswest.net [204.147.85.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA29967 for ; Thu, 9 Jan 1997 05:52:36 -0800 (PST) Received: (from greg@localhost) by nevis.oss.uswest.net (8.8.2/8.8.2) id HAA21108; Thu, 9 Jan 1997 07:47:56 -0600 (CST) From: "Greg Rowe" Message-Id: <9701090747.ZM21106@nevis.oss.uswest.net> Date: Thu, 9 Jan 1997 07:47:55 -0600 In-Reply-To: j@uriah.heep.sax.de (J Wunsch) "Re: 2.2 BETA Upgrade Problem" (Jan 8, 11:00pm) References: <9701081115.ZM12694@nevis.oss.uswest.net> X-Mailer: Z-Mail (3.2.1 10oct95) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), hackers@FreeBSD.ORG Subject: Re: 2.2 BETA Upgrade Problem Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I tried from a 2.1.5 and a 2.1.6 system. I'll try from a 2.2 system today and let you know. Greg On Jan 8, 11:00pm, J Wunsch wrote: > Subject: Re: 2.2 BETA Upgrade Problem > As Chuck Robey wrote: > > > I just used nfs to load my new machine from an existing one. Didn't > > have to go out of my little 2 machine net, but it worked line a > > charm. > > Most of my 2.2-release-cycle tests have been installed over NFS, too. > However, in my case the server is running FreeBSD-almost-current, not > 2.1.something. > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) >-- End of excerpt from J Wunsch -- Greg Rowe | U S West - Interact Services | INTERNET greg@uswest.net 111 Washington Ave. South | Fax: (612) 672-8537 Minneapolis, MN USA 55401 | Voice: (612) 672-8535 Never trust an operating system you don't have source for.... From owner-freebsd-hackers Thu Jan 9 09:20:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA10876 for hackers-outgoing; Thu, 9 Jan 1997 09:20:38 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA10871 for ; Thu, 9 Jan 1997 09:20:34 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA08528; Thu, 9 Jan 1997 12:20:02 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Thu, 9 Jan 1997 12:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id IAA29054; Thu, 9 Jan 1997 08:13:17 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id IAA06260; Thu, 9 Jan 1997 08:16:36 -0500 (EST) Date: Thu, 9 Jan 1997 08:16:36 -0500 (EST) From: Thomas David Rivers Message-Id: <199701091316.IAA06260@lakes.water.net> To: ponds!idt.ntnu.no!Arne.Juul, ponds!lakes.water.net!rivers Subject: Mail problems (who's tacking on ucbvax.Berkely.EDU?) Cc: ponds!freefall.cdrom.com!freebsd-hackers Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > There seems to be something wrong with your mail gateway > setup. Here's what the addresses looks like in the end: > > From: Thomas David Rivers > To: chuckr@glue.umd.edu, ponds!uswest.net!greg@ucbvax.Berkeley.EDU > Cc: ponds!FreeBSD.ORG!hackers@ucbvax.Berkeley.EDU > > Now I guess the first couple are OK, but why doesn't it do the > right thing with the rest of the addresses? They really should > have been "greg@uswest.net" and "hackers@FreeBSD.ORG", it seems. > > ucbvax.Berkeley.EDU doesn't even exist, so they can't possibly > work in their current form. > You're right! I noticed that as well... But, it's not coming from me. I'm simply replying. (That is, I don't have ucbvax.Berkeley.EDU anywhere in my sendmail or related files.) Here's the header I got for the message to which I replied.... you'll see the ucbvax.Berkeley.EDU there. I'd say it was someone along this path that put the gratuitous ucbvax.Berkely.EDU in there. I'd bet it's an older sendmail.cf; built from one of the example m4 macro files, that does this for UUCP traffic.... maybe "mail.webspan.net". I'm posting this to "hackers" as well - maybe someone else has seen this oddity and we can triangulate to determine what's going on. [Terry - have you seen it?] - Dave Rivers - From dg-rtp!freefall.freebsd.org!owner-freebsd-hackers@ponds.water.net Thu Jan 9 06:20:21 1997 Received: from ponds.water.net (ponds [10.0.0.1]) by lakes.water.net (8.7.5/8.6.9) with ESMTP id GAA05912 for ; Thu, 9 Jan 1997 06:20:20 -0500 (EST) Received: from dg-rtp.UUCP (uucp@localhost) by ponds.water.net (8.7.5/8.7.3) with UUCP id GAA27342 for rivers; Thu, 9 Jan 1997 06:16:58 -0500 (EST) Received: from mail.webspan.net by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA23273; Thu, 9 Jan 1997 00:53:57 -0500 Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.18]) by mail.webspan.net (8.7.5/8.7.3) with ESMTP id AAA13031; Thu, 9 Jan 1997 00:48:31 -0500 (EST) Received: from localhost (daemon@localhost) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id VAA03132; Wed, 8 Jan 1997 21:20:44 -0800 (PST) Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA03112 for hackers-outgoing; Wed, 8 Jan 1997 21:20:39 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id VAA03098 for ; Wed, 8 Jan 1997 21:20:36 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA20610; Thu, 9 Jan 1997 00:20:03 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Thu, 9 Jan 1997 00:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id WAA17542; Wed, 8 Jan 1997 22:15:30 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id WAA05201; Wed, 8 Jan 1997 22:18:48 -0500 (EST) Date: Wed, 8 Jan 1997 22:18:48 -0500 (EST) From: Thomas David Rivers Message-Id: <199701090318.WAA05201@lakes.water.net> To: chuckr@glue.umd.edu, ponds!uswest.net!greg@ucbvax.Berkeley.EDU Subject: Re: 2.2 BETA Upgrade Problem Cc: ponds!FreeBSD.ORG!hackers@ucbvax.Berkeley.EDU Content-Type: text Sender: dg-rtp!FreeBSD.ORG!owner-hackers@ponds.water.net X-Loop: FreeBSD.org Precedence: bulk Status: R From owner-freebsd-hackers Thu Jan 9 12:15:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA19301 for hackers-outgoing; Thu, 9 Jan 1997 12:15:05 -0800 (PST) Received: from smyrno.sol.net (smyrno.sol.net [206.55.64.117]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA19296 for ; Thu, 9 Jan 1997 12:15:02 -0800 (PST) Received: from solaria.sol.net (solaria.sol.net [206.55.65.75]) by smyrno.sol.net (8.8.3/8.8.3) with SMTP id OAA18632; Thu, 9 Jan 1997 14:15:00 -0600 (CST) Received: from localhost by solaria.sol.net (8.5/8.5) id OAA07665; Thu, 9 Jan 1997 14:14:58 -0600 From: Joe Greco Message-Id: <199701092014.OAA07665@solaria.sol.net> Subject: Re: CCD questions (news server) To: joe@via.net (Joe McGuckin) Date: Thu, 9 Jan 97 14:14:57 CST Cc: freebsd-hackers@freebsd.org In-Reply-To: <199701090831.AAA04364@monk.via.net> from "Joe McGuckin" at Jan 9, 97 00:31:32 am X-Mailer: ELM [version 2.4dev PL65] MIME-Version: 1.0 Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I just switched over our news machine from a tired old Sun SS2 (with Weitek > upgrade) to a 133Mhz pentium with 12G of Barracudas ccd'd together, > > I arbitrarily set the interleave to 64. Is there a good method to derive > the optimal interleave factor? Yes - search the hackers mailing list archive for usenet, news, ccd, interleave, etc. and you will find one of my several essays on the subject. You are killing your performance with such a low number. > I'm using a flags value of zero. How can I expect flag values of CCDF_SWAP > and CCDF_UNIFORM to affect performance? Don't know. > My initial experiences are very positive. The machine seems to process articles > about three to five times faster than the Sun with a load factor that never > goes above .45 (so far, only one of our incoming feeds has switched over to the > new machine). > > I'm very impressed. Especially if you consider that no performance tuning of > the system or INN has been done yet. I'm not using MMAP yet because there > seems to be some question as to how well it works for INN. > > Has anyone ever put together multiple machine 'news farms'? I'd like to > find out what's been done so far. I am running a pair of feeder machines here, 'newspump.sol.net' and the brand new 'newsfeeds.sol.net'. newspump is a P133/256MB/3 SCSI/17 drive box, newsfeeds is a PPro200/256MB/5 SCSI/24 drive box. Between the two of them, they handle 22 peer feeds and LOTS of news. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-hackers Thu Jan 9 12:31:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA20023 for hackers-outgoing; Thu, 9 Jan 1997 12:31:43 -0800 (PST) Received: from hemi.com (hemi.com [204.132.158.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA20016 for ; Thu, 9 Jan 1997 12:31:40 -0800 (PST) Received: (from mbarkah@localhost) by hemi.com (8.8.4/8.7.3) id NAA04587 for freebsd-hackers@freebsd.org; Thu, 9 Jan 1997 13:31:39 -0700 (MST) From: Ade Barkah Message-Id: <199701092031.NAA04587@hemi.com> Subject: Help! fatal trap 12, and problem with coredump To: freebsd-hackers@freebsd.org Date: Thu, 9 Jan 1997 13:31:38 -0700 (MST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm getting these regularly now (FreeBSD 2.1.6.1): | Fatal trap 12: page fault while in kernel mode | fault virtual address = 0xb4a1956b | fault code = supervisor write, page not present | instruction pointer = 0x8:0xf014afb2 | code segment = base 0x0, limit 0xfffff, type 0x1b | = DPL 0, ... | processor eflags = interrupt enabled, resume, IOPL=0 | current process = 18896 (finger) | interrupt mask = | kernel: type 12 trap. code = 0 | stopped at _tcp_connect0x3e: mov $0xc,0xc483ffff(%ecx) nm /kernel gives f014af74 T _tcp_connect. I suspect bad RAM. Any ideas ? Would I see this if the RAM is too slow ? (They are 70ns, so they should be fine.) Now, I haven't seen any kind of coredump from this machine. Invoking panic manually from DDB gets me: | aha0: DMA beyond end of ISA: 0x10000... (I'm sure it means 16mb). I have an Adaptec 1542CF and 64mb RAM. I do have: options BOUNCE_BUFFERS in the kernel. Another machine with a 1542CF and 64mb similarly does not produce core dumps. I'd really appreciate any help or comments! Thanks, -Ade ------------------------------------------------------------------- Inet: mbarkah@hemi.com - HEMISPHERE ONLINE - ------------------------------------------------------------------- From owner-freebsd-hackers Thu Jan 9 13:10:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA21724 for hackers-outgoing; Thu, 9 Jan 1997 13:10:53 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA21719 for ; Thu, 9 Jan 1997 13:10:49 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA14833; Thu, 9 Jan 1997 22:09:09 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id VAA19679; Thu, 9 Jan 1997 21:43:15 +0100 (MET) Message-ID: Date: Thu, 9 Jan 1997 21:43:15 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: mrcpu@cdsnet.net (Jaye Mathisen) Cc: hackers@freebsd.org Subject: Re: 2.2-BETA install report, minor problems. References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Jaye Mathisen on Jan 9, 1997 02:08:54 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Jaye Mathisen wrote: > 1) Configuring local time zone results in a "copied" message after > copying the file which seems a little redundant give that you just > selected what you wanted to do, it asked to confirm it, and then tells you > that it did it. Time consuming. Remember that tzsetup is a standalone program normally. The `copied' message is to make it clear that /etc/localtime is indeed a separate copy now, so e.g. it won't be updated next time your /usr/share files are renewed. This is the default. The opposite is to create a symlink into /usr/share/zoneinfo/. tzsetup will do this if the existing /etc/localtime happened to be a symlink already, and will announce it then. > 2) The box I was installing on had BSD/OS installed on it. For whatever BSD/OS uses a totally `weird' bootstrap if used in dedicated mode (withouth an fdisk table). This is something like our `dangerously dedicated' mode, and BSDi should probably warn about its dangers as well. You just felt it... > I tried everything I could think of. fdisk shows totally bizarre > numbers for the partition table, and the only way I could get the damn > thing to install properly was to low-level format the disk from my Adaptec > controller. No. I think a simple dd if=/dev/zero of=/dev/rsd0 count=100 should have done it as well. (Substitute the actual device for rsd0 if BSD/OS has a different one, i don't know.) The same procedure is needed to reuse a `dangerously dedicated' FreeBSD disk e.g. for a MicroSoft system. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Thu Jan 9 13:50:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA23471 for hackers-outgoing; Thu, 9 Jan 1997 13:50:47 -0800 (PST) Received: from thelab.hub.org (hal-ns1-28.netcom.ca [207.181.94.92]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA23464 for ; Thu, 9 Jan 1997 13:50:43 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.4/8.8.2) with SMTP id RAA09039; Thu, 9 Jan 1997 17:49:06 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 9 Jan 1997 17:49:05 -0400 (AST) From: The Hermit Hacker To: Joe Greco cc: Joe McGuckin , freebsd-hackers@freebsd.org Subject: Re: CCD questions (news server) In-Reply-To: <199701092014.OAA07665@solaria.sol.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 9 Jan 1997, Joe Greco wrote: > > I just switched over our news machine from a tired old Sun SS2 (with Weitek > > upgrade) to a 133Mhz pentium with 12G of Barracudas ccd'd together, > > > > I arbitrarily set the interleave to 64. Is there a good method to derive > > the optimal interleave factor? > > Yes - search the hackers mailing list archive for usenet, news, ccd, > interleave, etc. and you will find one of my several essays on the subject. > > You are killing your performance with such a low number. > Now I'm curious, what interleave are you using? I don't assume its possible to *change* the interleave once the device is created, is it? I'm running even lower (32), since...well...I didn't know better :( Should maybe add a note to the man page that states a recommended value for a news server, or something like that? :) From owner-freebsd-hackers Thu Jan 9 13:53:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA23582 for hackers-outgoing; Thu, 9 Jan 1997 13:53:20 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA23575 for ; Thu, 9 Jan 1997 13:53:00 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA15455; Thu, 9 Jan 1997 22:52:55 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id WAA19881; Thu, 9 Jan 1997 22:36:20 +0100 (MET) Message-ID: Date: Thu, 9 Jan 1997 22:36:20 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org Cc: ponds!rivers@dg-rtp.dg.com (Thomas David Rivers) Subject: Re: Mail problems (who's tacking on ucbvax.Berkely.EDU?) X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 Message-ID: Date: Thu, 9 Jan 1997 22:05:53 +0100 X-Mailer: Mutt 0.55-PL10 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701091316.IAA06260@lakes.water.net>; from Thomas David Rivers on Jan 9, 1997 08:16:36 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Thomas David Rivers wrote: > I'd say it was someone along this path that put the gratuitous > ucbvax.Berkely.EDU in there. I'd bet it's an older sendmail.cf; > built from one of the example m4 macro files, that does this for > UUCP traffic.... maybe "mail.webspan.net". I wouldn't be too surprised if it were DG-RTP. DG/UX used to ship with a fairly ancient sendmail, back in the days when i've been working with it. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Thu Jan 9 13:53:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA23622 for hackers-outgoing; Thu, 9 Jan 1997 13:53:30 -0800 (PST) Received: from thelab.hub.org (hal-ns1-28.netcom.ca [207.181.94.92]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA23599 for ; Thu, 9 Jan 1997 13:53:26 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.4/8.8.2) with SMTP id RAA09330 for ; Thu, 9 Jan 1997 17:53:23 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 9 Jan 1997 17:53:22 -0400 (AST) From: The Hermit Hacker To: hackers@freebsd.org Subject: mount w/ noatime option Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... With all the talk about the noatime option, I figured I'd see what happens if I used mount from -current (3.0) on my 2.2 machine, since /usr/include/sys/mount.h defines MNT_NOATIME... It worked, but I'm wondering if this is "A Bad Thing"...like, I know that if I were to try to move some binaries from 3.0 to 2.2, I'd be asking for problems, due to struct incompatibilities (w comes to mind)...am I risking the same thing with mount, or should I be safe? Thanks... From owner-freebsd-hackers Thu Jan 9 14:01:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA24111 for hackers-outgoing; Thu, 9 Jan 1997 14:01:36 -0800 (PST) Received: from inf.enst.fr (snZ9Ci7pu3VTFv5sywgcppVFdNBMmVlG@inf.enst.fr [137.194.2.81]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA24105 for ; Thu, 9 Jan 1997 14:01:30 -0800 (PST) Received: from nikopol.enst.fr (nikopol.enst.fr [137.194.168.105]) by inf.enst.fr (8.8.4/8.8.4) with ESMTP id XAA16752; Thu, 9 Jan 1997 23:01:09 +0100 (MET) Received: (from fenyo@localhost) by nikopol.enst.fr (8.8.3/8.8.2) id XAA16757; Thu, 9 Jan 1997 23:01:05 +0100 (MET) Date: Thu, 9 Jan 1997 23:01:05 +0100 (MET) Message-Id: <199701092201.XAA16757@nikopol.enst.fr> From: "Alex Fenyo (eowyn)" To: freebsd-hackers@freebsd.org Subject: bug in code for booting over the net X-WWW: http://home.eowyn.fr.eu.org/~fenyo/documents/axel.html X-PGP-Key: finger alex@eowyn.fr.eu.org X-NIC-Handle: AF713 X-Whois: whois -h whois.internic.net fenyo X-Pager: 06-04-30-75-94 (for emergency only) Organization: Ecole Nationale Superieure des Telecommunications de Paris Reply-to: fenyo@inf.enst.fr Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I was unable to boot over ethernet because of code in /src/sys/i386/boot/netboot/start2.S In this file, _get_diskinfo is a function used to get informations about drives. To do this, it makes call to BIOS INT 13h. The parameter (drive number) is put in %dl : ------------------------------------------------------------ movb 0x8(%ebp), %dl /* diskinfo(drive #) */ call _prot_to_real /* enter real mode */ movb $0x8, %ah /* ask for disk info */ sti int $0x13 cli ------------------------------------------------------------ But the call to INT 13h never returns, on my PC. I think it's because the function _prot_to_real modifies %dl. Indeed, when I invert the two first lines, the PC boots over the net; the following code works fine : ------------------------------------------------------------ call _prot_to_real /* enter real mode */ movb 0x8(%ebp), %dl /* diskinfo(drive #) */ movb $0x8, %ah /* ask for disk info */ sti int $0x13 cli ------------------------------------------------------------ BUT looking at _prot_to_real, I can't find any reason why %dl would be modified : ------------------------------------------------------------ /************************************************************************** PROT_TO_REAL - Go from Protected Mode to REAL Mode **************************************************************************/ .globl _prot_to_real _prot_to_real: pop %eax sub $RELOC,%eax /* Adjust return address */ push %eax sub $RELOC,%esp /* Adjust stack pointer */ ljmp $REAL_MODE_SEG, $1f /* jump to a 16 bit segment */ 1: /* clear the PE bit of CR0 */ mov %cr0, %eax opsize andl $0!CR0_PE, %eax mov %eax, %cr0 /* make intersegment jmp to flush the processor pipeline * and reload CS register */ opsize ljmp $(RELOC)>>4, $2f-RELOC 2: /* we are in real mode now * set up the real mode segment registers : DS, SS, ES */ mov %cs, %ax mov %ax, %ds mov %ax, %es mov %ax, %ss sti opsize ret ------------------------------------------------------------ Could anybody explain to me this strange behavior ? Alexandre Fenyo From owner-freebsd-hackers Thu Jan 9 15:05:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA27071 for hackers-outgoing; Thu, 9 Jan 1997 15:05:34 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA27066 for ; Thu, 9 Jan 1997 15:05:31 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id PAA04580; Thu, 9 Jan 1997 15:04:47 -0800 (PST) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: mrcpu@cdsnet.net (Jaye Mathisen), hackers@freebsd.org Subject: Re: 2.2-BETA install report, minor problems. In-reply-to: Your message of "Thu, 09 Jan 1997 21:43:15 +0100." Date: Thu, 09 Jan 1997 15:04:47 -0800 Message-ID: <4576.852851087@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Remember that tzsetup is a standalone program normally. The `copied' > message is to make it clear that /etc/localtime is indeed a separate > copy now, so e.g. it won't be updated next time your /usr/share files > are renewed. This is the default. The opposite is to create a > symlink into /usr/share/zoneinfo/. tzsetup will do this if the > existing /etc/localtime happened to be a symlink already, and will > announce it then. Nonetheless, I don't think it should do this in the case where it's run from init (sysinstall) or possibly when there's no existing file there at all, e.g. the first time (I like that better). I agree that the extra message is just noise and it irked me when I first encountered the change myself. Jordan > > > 2) The box I was installing on had BSD/OS installed on it. For whatever > > BSD/OS uses a totally `weird' bootstrap if used in dedicated mode > (withouth an fdisk table). This is something like our `dangerously > dedicated' mode, and BSDi should probably warn about its dangers as > well. You just felt it... > > > I tried everything I could think of. fdisk shows totally bizarre > > numbers for the partition table, and the only way I could get the damn > > thing to install properly was to low-level format the disk from my Adaptec > > controller. > > No. I think a simple dd if=/dev/zero of=/dev/rsd0 count=100 should > have done it as well. (Substitute the actual device for rsd0 if > BSD/OS has a different one, i don't know.) The same procedure is > needed to reuse a `dangerously dedicated' FreeBSD disk e.g. for a > MicroSoft system. > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Thu Jan 9 16:50:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA02860 for hackers-outgoing; Thu, 9 Jan 1997 16:50:52 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA02852 for ; Thu, 9 Jan 1997 16:50:50 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.4/8.7.3) with SMTP id QAA23154 for ; Thu, 9 Jan 1997 16:50:49 -0800 (PST) Date: Thu, 9 Jan 1997 16:50:49 -0800 (PST) From: Jaye Mathisen To: hackers@freebsd.org Subject: CCD mirroring... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does CCD when using the mirroring option satisfy the read from the disk that's closest to the data? or does it just always read from the first disk, with the second disk being a backup? The latter seems to be the case, but I'm not positive. From owner-freebsd-hackers Thu Jan 9 16:54:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA03117 for hackers-outgoing; Thu, 9 Jan 1997 16:54:38 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA03108 for ; Thu, 9 Jan 1997 16:54:34 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.4/8.7.3) with SMTP id QAA23680; Thu, 9 Jan 1997 16:54:07 -0800 (PST) Date: Thu, 9 Jan 1997 16:54:07 -0800 (PST) From: Jaye Mathisen To: Joerg Wunsch cc: hackers@freebsd.org Subject: Re: 2.2-BETA install report, minor problems. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 9 Jan 1997, J Wunsch wrote: > > 2) The box I was installing on had BSD/OS installed on it. For whatever > > BSD/OS uses a totally `weird' bootstrap if used in dedicated mode > (withouth an fdisk table). This is something like our `dangerously > dedicated' mode, and BSDi should probably warn about its dangers as > well. You just felt it... I submit that if I'm selecting that FreeBSD use the entire disk, and I insiste that it use the entire disk this way, and "Yes, I don't want to be compatible with any type of OS co-existence", that then the exhibited behaviour is a bug. Maybe freebsd needs to zero the disklabel or something itself. I know Alpha's under Digital UNIX had a -z option to disklabel to zero it out. There should be a way to zero out the partition table as well. BSD/OS does warn about the dangers, but since I'm not co-existing, I'm replacing, then I think our stuff should be able to handle it. From owner-freebsd-hackers Thu Jan 9 17:40:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA05543 for hackers-outgoing; Thu, 9 Jan 1997 17:40:41 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA05537 for ; Thu, 9 Jan 1997 17:40:39 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id MAA29894; Fri, 10 Jan 1997 12:10:22 +1030 (CST) From: Michael Smith Message-Id: <199701100140.MAA29894@genesis.atrad.adelaide.edu.au> Subject: Re: CCD mirroring... In-Reply-To: from Jaye Mathisen at "Jan 9, 97 04:50:49 pm" To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Fri, 10 Jan 1997 12:10:21 +1030 (CST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jaye Mathisen stands accused of saying: > > Does CCD when using the mirroring option satisfy the read from the disk > that's closest to the data? or does it just always read from the first > disk, with the second disk being a backup? There's no useful way to work out "where" a disk is at, so it's not possible to operate in the first mode you describe. > The latter seems to be the case, but I'm not positive. It is. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Thu Jan 9 18:17:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA06986 for hackers-outgoing; Thu, 9 Jan 1997 18:17:50 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA06978 for ; Thu, 9 Jan 1997 18:17:44 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id TAA19116; Thu, 9 Jan 1997 19:05:45 -0700 From: Terry Lambert Message-Id: <199701100205.TAA19116@phaeton.artisoft.com> Subject: Re: 2.2-BETA install report, minor problems. To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Thu, 9 Jan 1997 19:05:44 -0700 (MST) Cc: joerg_wunsch@uriah.heep.sax.de, hackers@FreeBSD.org In-Reply-To: from "Jaye Mathisen" at Jan 9, 97 04:54:07 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > BSD/OS uses a totally `weird' bootstrap if used in dedicated mode > > (withouth an fdisk table). This is something like our `dangerously > > dedicated' mode, and BSDi should probably warn about its dangers as > > well. You just felt it... > > > I submit that if I'm selecting that FreeBSD use the entire disk, and I > insiste that it use the entire disk this way, and "Yes, I don't want to be > compatible with any type of OS co-existence", that then the exhibited > behaviour is a bug. > > Maybe freebsd needs to zero the disklabel or something itself. I know > Alpha's under Digital UNIX had a -z option to disklabel to zero it out. > There should be a way to zero out the partition table as well. > > BSD/OS does warn about the dangers, but since I'm not co-existing, I'm > replacing, then I think our stuff should be able to handle it. The question is not whether we can handle it. The question is whether the Copmaq DeskPro/E can handle it, since its POST code bootstrap checks the boot sector for "validity" (in the DOS'est sense of the word). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Jan 9 18:18:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA07078 for hackers-outgoing; Thu, 9 Jan 1997 18:18:46 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA07067 for ; Thu, 9 Jan 1997 18:18:42 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id TAA19125; Thu, 9 Jan 1997 19:07:07 -0700 From: Terry Lambert Message-Id: <199701100207.TAA19125@phaeton.artisoft.com> Subject: Re: CCD mirroring... To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Thu, 9 Jan 1997 19:07:07 -0700 (MST) Cc: mrcpu@cdsnet.net, hackers@freebsd.org In-Reply-To: <199701100140.MAA29894@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jan 10, 97 12:10:21 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Jaye Mathisen stands accused of saying: > > > > Does CCD when using the mirroring option satisfy the read from the disk > > that's closest to the data? or does it just always read from the first > > disk, with the second disk being a backup? > > There's no useful way to work out "where" a disk is at, so it's not > possible to operate in the first mode you describe. > > > The latter seems to be the case, but I'm not positive. > > It is. Contact Rod Grimes; I believe he was playing with "spindle sync", which would let you "know". At the very least, it should interleave requests between disks (I know, not much of a win for the TCQ-enabled among us). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Jan 9 20:39:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA13435 for hackers-outgoing; Thu, 9 Jan 1997 20:39:59 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA13430 for ; Thu, 9 Jan 1997 20:39:57 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id UAA00147 for ; Thu, 9 Jan 1997 20:40:51 -0800 (PST) Received: (qmail 302 invoked by uid 110); 10 Jan 1997 04:39:40 -0000 Message-ID: <19970110043940.301.qmail@suburbia.net> Subject: ipv6 To: hackers@freebsd.org Date: Fri, 10 Jan 1997 15:39:40 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is anyone actively working on intergrating the nrl code? Cheers, Julian. From owner-freebsd-hackers Thu Jan 9 21:22:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA18473 for hackers-outgoing; Thu, 9 Jan 1997 21:22:09 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA18468 for ; Thu, 9 Jan 1997 21:22:07 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id VAA01099 for ; Thu, 9 Jan 1997 21:22:49 -0800 (PST) Received: (qmail 5326 invoked by uid 110); 10 Jan 1997 05:21:14 -0000 Message-ID: <19970110052114.5325.qmail@suburbia.net> Subject: distfile diffs? To: hackers@freebsd.org Date: Fri, 10 Jan 1997 16:21:14 +1100 (EST) Cc: electron@suburbia.net (Ido Banks) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I wonder whether the ports/cvsup could not be slightly modified to handle the fetching of diffs from one distfile version to another? For example the last three tar.gz versions of pine 3.xx were approximately 4000k a peice, while the diffs of the same were considerably less. The same goes for cvsup itself, and the modular-3 distribution (the entirety of which I've pulled across at least twice in order to satisfy cvsup's dependencies). For security and code-review reasons it would also be nice to have diffs for distfile version changes, rather than just yanking over the whole tree. Given that freefall sees copies of all distfiles (except for the occasional distribution restriction), it may as well be producing diffs from one version to the other. Whether this is done by placing unexploded tar balls under cvs control and letting cvsup or cvs rdiff do the work, or merely by generating diffs each time a new distfile tarball comes in from the old tarball and grabbing them with fetch(1) is an implementation issue. If the diffs are applied as part of the make process, and one presumes the port's object code make dependencies are valid, and the work dir has not yet been cleaned, re-compilation should be minimised. Cheers, Julian. From owner-freebsd-hackers Thu Jan 9 22:46:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA22787 for hackers-outgoing; Thu, 9 Jan 1997 22:46:21 -0800 (PST) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA22780 for ; Thu, 9 Jan 1997 22:46:18 -0800 (PST) Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) with ESMTP id WAA07104 for ; Thu, 9 Jan 1997 22:46:16 -0800 (PST) From: Josh MacDonald Message-Id: <199701100646.WAA07104@paris.CS.Berkeley.EDU> To: freebsd-hackers@freebsd.org Subject: texinfo changes ready MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7095.852878771.1@paris.CS.Berkeley.EDU> Date: Thu, 09 Jan 1997 22:46:13 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm ready to commit the texinfo upgrade I described a few days ago. I've never commit such a large set of changes, so before I do I'll describe the changes; please tell me if this is okay. 1. In the directory gnu/usr.bin/texinfo, remove the file "Makefile.inc" and directories "info-files", "makedoc", "misc", and "texindex". 2. texinfo sources will now go in the contrib directory, so most of the files in the "info", "makeinfo", and "doc" get removed. 3. Add new Makefiles to each remaining subdirectory and new subdirectories "libtxi" and "install-info". 4. Import the original sources post-configured and patched into gnu/texinfo. That's the complete set of changes to the texinfo installation. Now comes the set of changes that replaces the old method of installing the /usr/share/info/dir file. 5. Modify share/mk/bsd.info.mk so that the building of info files uses install-info to add each file to the dir file. No pre-built dir file is located anywhere in the source tree, only an empty template share/info/dir-tmpl which is copied to share/info/dir when building begins. 6. Now info files in the source tree which are already annotated with the information required by install-info will install themselves correctly into share/info/dir the rest of the files (most of them) will require additional modifications to their respective Makefiles. 7. For info files in package P not containing the annotations, the Makefile previously reading. INFO= foo bar Is modified to read: INFOSECTION= "P Documentation" INFOENTRY_foo= "* foo: (foo). Documentation for the `foo' command." INFOENTRY_bar= "* bar: (bar). Documentation for the `bar' command." The Makefile is otherwise unmodified. After building, the dir file will contain: P Documentation * foo: (foo). Documentaiton for the `foo' command. * bar: (bar). Documentation for the `bar' command. The directory share/info is given an install rule to install the dir file. Please tell me if these modifications are okay. -josh From owner-freebsd-hackers Thu Jan 9 23:35:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA26412 for hackers-outgoing; Thu, 9 Jan 1997 23:35:54 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA26398 for ; Thu, 9 Jan 1997 23:35:47 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id RAA18329; Fri, 10 Jan 1997 17:36:15 +1100 Date: Fri, 10 Jan 1997 17:36:15 +1100 From: Bruce Evans Message-Id: <199701100636.RAA18329@godzilla.zeta.org.au> To: fenyo@inf.enst.fr, freebsd-hackers@FreeBSD.ORG Subject: Re: bug in code for booting over the net Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I was unable to boot over ethernet because of code in >/src/sys/i386/boot/netboot/start2.S > >In this file, _get_diskinfo is a function used to get informations >about drives. To do this, it makes call to BIOS INT 13h. >The parameter (drive number) is put in %dl : >------------------------------------------------------------ > movb 0x8(%ebp), %dl /* diskinfo(drive #) */ > call _prot_to_real /* enter real mode */ > movb $0x8, %ah /* ask for disk info */ > sti > int $0x13 > cli >------------------------------------------------------------ > >But the call to INT 13h never returns, on my PC. get_diskinfo() was buggy in revision 1.3 of start2.S. It did not preserve %edi. This is fixed in revision 1.4 and in FreeBSD-2.2. prot_to_real() is buggy in all versions of start2.S. It does not set the segment limits of the real mode descriptors to 64K-1. Some BIOSes are sensitive to this. This is fixed in prot_to_real() in biosboot/asm.S. >I think it's because the function _prot_to_real modifies %dl. It doesn't seem to have that bug :-). >Indeed, when I invert the two first lines, the PC boots over >the net; the following code works fine : >------------------------------------------------------------ > call _prot_to_real /* enter real mode */ > movb 0x8(%ebp), %dl /* diskinfo(drive #) */ > movb $0x8, %ah /* ask for disk info */ > sti > int $0x13 > cli >------------------------------------------------------------ Moving the code is wrong because gas doesn't completely understand 16-bit mode (especially when it isn't told that the mode changed), and `(%ebp)' is one of the things it doesn't understand. `movb 0x8(%ebp), %dl' for 32-bit (protected) mode actually turns into `movb 0x8(%di), %dl' when it is executed in 16-bit (real) mode! I guess this works by giving a completely invalid value for %dl so that the BIOS aborts before it runs into the other bugs. >BUT looking at _prot_to_real, I can't find any reason why %dl >would be modified : Right. Bruce From owner-freebsd-hackers Fri Jan 10 00:38:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA29653 for hackers-outgoing; Fri, 10 Jan 1997 00:38:55 -0800 (PST) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA29648 for ; Fri, 10 Jan 1997 00:38:53 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.2/8.6.12) with SMTP id AAA00262 for ; Fri, 10 Jan 1997 00:38:52 -0800 (PST) Date: Fri, 10 Jan 1997 00:38:52 -0800 (PST) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: hackers@freebsd.org Subject: ncr probe FAILS on 2.2-BETA_A! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello! I'm attempting to install 2.2-BETA_A on a SiS Pentium 100 system, and the ncr startup locks the system up just after ncr0 waiting for devices to settle This machine works perfectly with 2.2-ALPHA. I've booted -c and reduced the devices to the bare necessities with no change. System Specifics: Sis 54P chipset, Pentium 100 CPU, 32MB RAM NCR 53c815 SCSI controller w/ SDMS 3.0 BIOS Connected devices: Plextor 4PlexPLus CDROM Sony CDU-76S CDROM NE2000 network card ATI Mach64 video Probe from 2.2-ALPHA follows: ncr0 rev 3 int a irq 11 on pci0:13 ncr0 waiting for scsi devices to settle <-- 2.2-BETA stops here (ncr0:3:0): "PLEXTOR CD-ROM PX-4XCE 1.00" type 5 removable SCSI 2 cd0(ncr0:3:0): CD-ROM cd0(ncr0:3:0): FAST SCSI-2 175ns (6 Mb/sec) offset 8. cd present [263729 x 2048 byte records] (ncr0:4:0): "SONY CD-ROM CDU-76S 1.1c" type 5 removable SCSI 2 cd1(ncr0:4:0): CD-ROM cd1(ncr0:4:0): 200ns (5 Mb/sec) offset 8. cd1(ncr0:4:0): UNIT ATTENTION asc:28,0 cd1(ncr0:4:0): Not ready to ready transition, medium may have changed cd present [400000 x 2048 byte records] The SCSI devices to receive the bus reset, as the lights on the CDROMs light up, but that's all. The floppy drive light is stuck on and the keyboard LEDs don't function when the lockup occurs. There were no changes to the system configuration between shutting down 2.2-ALPHA and booting the BETA floppy. Sorry for taking so long to report this; today is the only time I've had to try plugging in BETA. Boot -v and other information available by request. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-hackers Fri Jan 10 01:01:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA00920 for hackers-outgoing; Fri, 10 Jan 1997 01:01:28 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id BAA00915 for ; Fri, 10 Jan 1997 01:01:21 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA24600 for hackers@FreeBSD.ORG; Fri, 10 Jan 1997 09:58:41 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id JAA22586; Fri, 10 Jan 1997 09:35:36 +0100 (MET) Message-ID: Date: Fri, 10 Jan 1997 09:35:35 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: mount w/ noatime option References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from The Hermit Hacker on Jan 9, 1997 17:53:22 -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As The Hermit Hacker wrote: > With all the talk about the noatime option, I figured I'd see > what happens if I used mount from -current (3.0) on my 2.2 machine, > since /usr/include/sys/mount.h defines MNT_NOATIME... > > It worked, but I'm wondering if this is "A Bad Thing"...like, It's not a Bad Thing per se, but i think it violates Posix. You normally probably would like to keep the atime record, so you can e.g. wipe out files from tmp areas nobody ever had a look at since several days. You don't win much by not bumping the atime, except in some situations like a newsserver -- but there, you win a lot. That's why the option is there. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Fri Jan 10 02:02:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA03805 for hackers-outgoing; Fri, 10 Jan 1997 02:02:47 -0800 (PST) Received: from thelab.hub.org (hal-ns1-24.netcom.ca [207.181.94.88]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA03799 for ; Fri, 10 Jan 1997 02:02:41 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.4/8.8.2) with SMTP id GAA13769; Fri, 10 Jan 1997 06:01:17 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 10 Jan 1997 06:01:17 -0400 (AST) From: The Hermit Hacker To: Joerg Wunsch cc: hackers@freebsd.org Subject: Re: mount w/ noatime option In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 10 Jan 1997, J Wunsch wrote: > As The Hermit Hacker wrote: > > > With all the talk about the noatime option, I figured I'd see > > what happens if I used mount from -current (3.0) on my 2.2 machine, > > since /usr/include/sys/mount.h defines MNT_NOATIME... > > > > It worked, but I'm wondering if this is "A Bad Thing"...like, > > It's not a Bad Thing per se, but i think it violates Posix. You > normally probably would like to keep the atime record, so you can > e.g. wipe out files from tmp areas nobody ever had a look at since > several days. You don't win much by not bumping the atime, except in > some situations like a newsserver -- but there, you win a lot. That's > why the option is there. > Oops, sorry...misworded the question :( I'm using the noatime option on my news server, but what I was worried about was taking the binary from a3.0 machine and using on a 2.2 machine, but everything so far seems right... From owner-freebsd-hackers Fri Jan 10 02:59:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA05593 for hackers-outgoing; Fri, 10 Jan 1997 02:59:16 -0800 (PST) Received: from thelab.hub.org (hal-ns1-24.netcom.ca [207.181.94.88]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA05587 for ; Fri, 10 Jan 1997 02:59:12 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.4/8.8.2) with SMTP id GAA15378 for ; Fri, 10 Jan 1997 06:59:09 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 10 Jan 1997 06:59:08 -0400 (AST) From: The Hermit Hacker To: hackers@freebsd.org Subject: mount -o async on a news servre Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hiya... Exactly *how* dangerous is setting a file system to async? In my case, I'm braving it on a news server, just the ccd device that contains both the news admin and spool directories. The drive is local to the system. My understanding of asynchronous I/O is that it doesn't wait for an acknowledgement from the system before going to the next write (only, its a very basic understanding?), so I'm curiuos as how it would handle writting the history file itself? The only risk that I can see is that if the system crashes, I'll have (might have) a corrupted file system, but is that my only risk? ie. if I turned on async for a period of time (long enough for a backlog from one system to catch up?) and then turned it back off again, would that be reasonably safe? BTW...what exactly does fastfs do? My understanding is that this is basically what it does, turns the file system to be async vs sync... Thanks... From owner-freebsd-hackers Fri Jan 10 04:08:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA08187 for hackers-outgoing; Fri, 10 Jan 1997 04:08:34 -0800 (PST) Received: from ui-gate.utell.co.uk ([194.200.4.253]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA08180 for ; Fri, 10 Jan 1997 04:08:27 -0800 (PST) Received: from dibble.utell.net (dibble2.utell.net [97.3.0.1]) by ui-gate.utell.co.uk (8.7.6/8.7.3) with ESMTP id MAA10949; Fri, 10 Jan 1997 12:02:10 GMT Message-Id: <199701101202.MAA10949@ui-gate.utell.co.uk> From: "Brian Somers" To: Cc: , Subject: (wide) DHCP negotiation using the REQUEST_IPADDR option Date: Fri, 10 Jan 1997 12:02:01 -0100 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_01BBFEEE.16772840" Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_01BBFEEE.16772840 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I seem to have found a problem with dhcp-1.3beta when DHCP'ing for a windows 95 box (I have little experience, so I don't know if it's just win95). Under windows 95, the dhcp request is sent with the REQUEST_IPADDR option set. Dhcps will try to select an IP address based on the CID before the requested IP, calling select_wcid() from request() in server/dhcps.c. If it finds a match, *and* it has a REQUEST_IPADDR option (reqip.s_addr) that differs from the entry found (res->ip_addr->s_addr), it returns(-1) - not replying to the request. If however, a NAK is returned, the client (win95) will do another dhcp request without the REQUEST_IPADDR option set..... voila IP address altered. I'm not sure about the original logic behind returning -1 above. If anyone's interested in reproducing this, make sure that you delete the arp entry on the server box while the win95 box is shut down..... I wasted a lot of time here ! The (trivial) patch is attached. Note, the freebsd port does not affect this (nor do I know if patches have been submitted for freebsd), although line numbers are probably different. Brian Don't __EVER__ lose your sense of humour ------=_NextPart_000_01BBFEEE.16772840 Content-Type: application/octet-stream; name="dhcps.c.patch" Content-Transfer-Encoding: 7bit Content-Description: dhcps.c.patch (PATCH File) Content-Disposition: attachment; filename="dhcps.c.patch" *** dhcps.c.orig Fri Jan 10 11:45:26 1997 --- dhcps.c Fri Jan 10 11:48:57 1997 *************** *** 1586,1594 **** res = NULL; res = select_wcid(DHCPREQUEST, &cid, curr_epoch); ! if (res != NULL && res->ip_addr != NULL && ! res->ip_addr->s_addr == reqip.s_addr) ! goto ack; else if (reqforme == 1) goto nak; else --- 1586,1596 ---- res = NULL; res = select_wcid(DHCPREQUEST, &cid, curr_epoch); ! if (res != NULL && res->ip_addr != NULL) ! if (res->ip_addr->s_addr == reqip.s_addr) ! goto ack; ! else ! goto nak; else if (reqforme == 1) goto nak; else ------=_NextPart_000_01BBFEEE.16772840-- From owner-freebsd-hackers Fri Jan 10 05:32:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA11252 for hackers-outgoing; Fri, 10 Jan 1997 05:32:09 -0800 (PST) Received: from terminator.informatik.ba-stuttgart.de (terminator.informatik.ba-stuttgart.de [141.31.1.21]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA11196 for ; Fri, 10 Jan 1997 05:30:20 -0800 (PST) Received: from helbig.informatik.ba-stuttgart.de (helbig.informatik.ba-stuttgart.de [141.31.166.22]) by terminator.informatik.ba-stuttgart.de (8.7.6/8.7.3) with ESMTP id NAA09079; Fri, 10 Jan 1997 13:29:29 +0100 Received: (from wh@localhost) by helbig.informatik.ba-stuttgart.de (8.8.4/8.8.4) id OAA00302; Fri, 10 Jan 1997 14:29:59 +0100 (MET) From: Wolfgang Helbig Message-Id: <199701101329.OAA00302@helbig.informatik.ba-stuttgart.de> Subject: Re: mount -o async on a news servre To: scrappy@hub.org (The Hermit Hacker) Date: Fri, 10 Jan 1997 14:29:58 +0100 (MET) Cc: hackers@freebsd.org In-Reply-To: from The Hermit Hacker at "Jan 10, 97 06:59:08 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hiya... > > Exactly *how* dangerous is setting a file system to async? I don't know *exactly* but I mount my /usr all the time async. Yesterday I had a system crash, (the system froze during "make world") but it recovered fine. After it I did another "make world" and this was the first one that succeeded. So mounting async does not seem to dangerous. AFAIK the async option turns off writing every directory change to disk immediately. That means directories will be treated like regular files in this respect, i. e. changes will get to disk during the next sync() call or when the corresponding buffer in the buffer cache is needed for another disk i/o. The update(4) process does a sync every 30 min. From owner-freebsd-hackers Fri Jan 10 05:36:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA11480 for hackers-outgoing; Fri, 10 Jan 1997 05:36:33 -0800 (PST) Received: from smtp-gw01.ny.us.ibm.net (smtp-gw01.ny.us.ibm.net [165.87.194.252]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id FAA11475 for ; Fri, 10 Jan 1997 05:36:31 -0800 (PST) Received: (from uucp@localhost) by smtp-gw01.ny.us.ibm.net (8.6.9/8.6.9) id NAA140969; Fri, 10 Jan 1997 13:35:09 GMT Message-Id: <199701101335.NAA140969@smtp-gw01.ny.us.ibm.net> Received: from slip166-72-229-80.va.us.ibm.net(166.72.229.80) by smtp-gw01.ny.us.ibm.net via smap (V1.3mjr) id smaEIsDmb; Fri Jan 10 13:35:02 1997 Reply-To: From: "Steve Sims" To: "The Hermit Hacker" , "Joe Greco" Cc: "Joe McGuckin" , Subject: Re: CCD questions (news server) Date: Fri, 10 Jan 1997 08:34:14 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The Hermit Hacker writes: > > > I arbitrarily set the interleave to 64. Is there a good method to derive > > > the optimal interleave factor? > > > > You are killing your performance with such a low number. > > > Now I'm curious, what interleave are you using? I don't assume its > possible to *change* the interleave once the device is created, is it? I'm > running even lower (32), since...well...I didn't know better :( > > Should maybe add a note to the man page that states a recommended > value for a news server, or something like that? :) > For what it's worth, I've been playing (in the strictest sense of the word, not actually *knowing anything* about ccd ;-) with CCD and various interleave values. Empirically (using `iozone`) I've decided that performance appears to "balance peak" (i.e.: best tradeoff between optimized read and optimized write speeds) when the interleave value specified will *not quite* fill the on-drive cache. So, with a farm of el-cheapo antique drives w/128K on-drive cache, I used an interleave of 240. Tweaking the interleave value higher bumps up the write performance but reading suffers. Moving the interleave downward didn't significantly help reading or writing performance. (Although some settings caused the array to lose, big time!) N.B.: This is in a plain-vanilla 4-drive, one controller, ccd configuration: No mirroring, no CCDF_SWAP or CCDF_UNIFORM flags. I'd have to play some to benchmark these. I briefly tested a configuration with dual Seagate 12550N's, one with 512K and one with 1M (!) on-drive cache and the result was similar; performance "balanced" best with an interleave of around 1000 (which is just under the size of the smaller cache). YMMV, I learned a "lot" by just playing with the values and newfs'ing. ...sjs... From owner-freebsd-hackers Fri Jan 10 05:42:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA11633 for hackers-outgoing; Fri, 10 Jan 1997 05:42:01 -0800 (PST) Received: from frig.mt.cs.keio.ac.jp (frig.mt.cs.keio.ac.jp [131.113.32.7]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id FAA11627 for ; Fri, 10 Jan 1997 05:41:59 -0800 (PST) Received: (from hosokawa@localhost) by frig.mt.cs.keio.ac.jp (8.6.12+2.4W/3.4Wbeta3) id WAA13105; Fri, 10 Jan 1997 22:41:55 +0900 Date: Fri, 10 Jan 1997 22:41:55 +0900 Message-Id: <199701101341.WAA13105@frig.mt.cs.keio.ac.jp> To: hackers@freebsd.org Subject: Why 2.2 tzsetup does't make /etc/wall_cmos_clock? From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.18PL3] 1994-08/01(Mon) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I remember that tzsetup of 2.1.x made /etc/wall_cmos_clock when I specified "CMOS clock == localtime", but 2.2 tzsetup does not make this file. Is this a "feature"? or a bug?, and is there another way to create /etc/wall_cmos_clock from sysinstall? Thanks. -- HOSOKAWA, Tatsumi E-mail: hosokawa@mt.cs.keio.ac.jp WWW homepage: http://www.mt.cs.keio.ac.jp/person/hosokawa.html Department of Computer Science, Keio University, Yokohama, Japan From owner-freebsd-hackers Fri Jan 10 06:52:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA14002 for hackers-outgoing; Fri, 10 Jan 1997 06:52:53 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA13989 for ; Fri, 10 Jan 1997 06:52:26 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id PAA09702 for ; Fri, 10 Jan 1997 15:53:11 +0100 (MET) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.3/8.6.9) id PAA11626 for freebsd-hackers@freefall.cdrom.com; Fri, 10 Jan 1997 15:50:56 +0100 (MET) Date: Fri, 10 Jan 1997 15:50:56 +0100 (MET) From: Christoph Kukulies Message-Id: <199701101450.PAA11626@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: mail to me disturbed Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk If anyone had sent mail to me in the past 12 hours I will likely have lost it. So please resend. We still may not have fully recovered from a power outage this morning and there may be problems also with ftp.de.freebsd.org sup.de.freebsd.org cvsup.de.freebsd.org --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Fri Jan 10 07:20:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA15337 for hackers-outgoing; Fri, 10 Jan 1997 07:20:34 -0800 (PST) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA15332 for ; Fri, 10 Jan 1997 07:20:32 -0800 (PST) Received: from Mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.2/8.8.2-biteme) with ESMTP id JAA26079; Fri, 10 Jan 1997 09:20:15 -0600 (CST) Received: from Jupiter.Mcs.Net (karl@Jupiter.mcs.net [192.160.127.88]) by Mailbox.mcs.com (8.8.2/8.8.2) with ESMTP id JAA25073; Fri, 10 Jan 1997 09:20:13 -0600 (CST) Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.4/8.8.2) id JAA20582; Fri, 10 Jan 1997 09:20:12 -0600 (CST) From: Karl Denninger Message-Id: <199701101520.JAA20582@Jupiter.Mcs.Net> Subject: Re: mount -o async on a news servre To: scrappy@hub.org (The Hermit Hacker) Date: Fri, 10 Jan 1997 09:20:12 -0600 (CST) Cc: hackers@freebsd.org In-Reply-To: from "The Hermit Hacker" at Jan 10, 97 06:59:08 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hiya... > > Exactly *how* dangerous is setting a file system to async? Quite. > In my case, I'm braving it on a news server, just the ccd > device that contains both the news admin and spool directories. The > drive is local to the system. > > My understanding of asynchronous I/O is that it doesn't wait > for an acknowledgement from the system before going to the next > write (only, its a very basic understanding?), so I'm curiuos as how > it would handle writting the history file itself? If you crash the superblock and its backup copies may not be properly written. If this is corrupted in the wrong sorts of ways, your root inode can end up unallocated -- the consequence of this is that the entire filesystem is destroyed. fsck is designed to fix filesystem inconsistencies. Running async increases the severity of those inconsistencies. If you have the update(1) job disabled as well, the superblock could be *hours* out of date. For this reason disabling update(1) makes this trick even more dangerous. Basically, when you write or create a file the superblock has to be updated along with the on-disk copy of the inodes involved. If you turn on async you're allowing these writes (which are normally synchronous with the create or open call) to be asynchronous -- that is, done later. The problem is that if/when you crash they might not have been done at all! The consequence is that the file(s) in question may be lost. Since DIRECTORY creates and updates are just file operations at the kernel level, this can also apply to *directories*. If it hits the root directory of the disk volume you're badly screwed (instead of slightly screwed :-). This information is known as the filesystem "metadata" (its not the actual file data, but the indices which allow you to get to the data itself). > The only risk that I can see is that if the system crashes, > I'll have (might have) a corrupted file system, but is that my only > risk? ie. if I turned on async for a period of time (long enough for > a backlog from one system to catch up?) and then turned it back off > again, would that be reasonably safe? Yes. > BTW...what exactly does fastfs do? My understanding is that > this is basically what it does, turns the file system to be async vs > sync... I believe so, yes. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | 99 Analog numbers, 77 ISDN, Web servers $75/mo Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal From owner-freebsd-hackers Fri Jan 10 08:08:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA17509 for hackers-outgoing; Fri, 10 Jan 1997 08:08:15 -0800 (PST) Received: from csla.csl.sri.com (csla.csl.sri.com [192.12.33.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA17504 for ; Fri, 10 Jan 1997 08:08:13 -0800 (PST) Received: from impulse.csl.sri.com (impulse.csl.sri.com [130.107.15.11]) by csla.csl.sri.com (8.7.3/8.7.3) with ESMTP id IAA12903 for ; Fri, 10 Jan 1997 08:05:07 -0800 (PST) Received: from impulse.csl.sri.com (localhost [127.0.0.1]) by impulse.csl.sri.com (8.7.3/8.7.3) with ESMTP id IAA03133 for ; Fri, 10 Jan 1997 08:06:58 -0800 (PST) Message-Id: <199701101606.IAA03133@impulse.csl.sri.com> To: freebsd-hackers@freebsd.org Subject: Re: A cool xterm? In-reply-to: Your message of "Wed, 08 Jan 1997 18:21:30 EST." Date: Fri, 10 Jan 1997 08:06:53 -0800 From: Fred Gilham Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Randal Hopper wrote: ---------------------------------------- Charles Henrich: |Has anyone out there ever found a nice terminal window, something |like Dec's mterm, or ssh for windows, or even better, NeXT's |terminal? Xterm is peachy, except the scrollback just sucks :) Rebuilt the color_xterm port linking with Xaw3d instead of Xaw, and the scrollbar's much better. Like the menus better too. ...with these resources: ---------------------------------------- I'm wondering what this means. Is it that people don't like the fact that the scrollbar works the way it does? Or is it that they don't like the way it looks? What exactly is wrong with the scrollbar? To put my own oar in the water, I'll say that the original Athena scrollbar is the only scrollbar I've seen with a decent user interface. Once you get used to it, anything else is harder to use. I hope there's always a scrollbar around with the Athena user interface. -Fred Gilham gilham@csl.sri.com From owner-freebsd-hackers Fri Jan 10 08:11:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA17641 for hackers-outgoing; Fri, 10 Jan 1997 08:11:37 -0800 (PST) Received: from smyrno.sol.net (smyrno.sol.net [206.55.64.117]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA17636 for ; Fri, 10 Jan 1997 08:11:35 -0800 (PST) Received: from solaria.sol.net (solaria.sol.net [206.55.65.75]) by smyrno.sol.net (8.8.3/8.8.3) with SMTP id KAA25307; Fri, 10 Jan 1997 10:11:28 -0600 (CST) Received: from localhost by solaria.sol.net (8.5/8.5) id KAA17513; Fri, 10 Jan 1997 10:11:26 -0600 From: Joe Greco Message-Id: <199701101611.KAA17513@solaria.sol.net> Subject: Re: CCD questions (news server) To: SimsS@IBM.Net Date: Fri, 10 Jan 97 10:11:23 CST Cc: scrappy@hub.org, joe@via.net, freebsd-hackers@freebsd.org In-Reply-To: <199701101335.NAA140969@smtp-gw01.ny.us.ibm.net> from "Steve Sims" at Jan 10, 97 08:34:14 am X-Mailer: ELM [version 2.4dev PL65] MIME-Version: 1.0 Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > For what it's worth, I've been playing (in the strictest sense of the word, > not actually *knowing anything* about ccd ;-) with CCD and various interleave > values. > > Empirically (using `iozone`) I've decided that performance appears to > "balance peak" (i.e.: best tradeoff between optimized read and optimized > write speeds) when the interleave value specified will *not quite* fill the > on-drive cache. > > So, with a farm of el-cheapo antique drives w/128K on-drive cache, I used an > interleave of 240. > > Tweaking the interleave value higher bumps up the write performance but > reading suffers. Moving the interleave downward didn't significantly help > reading or writing performance. (Although some settings caused the array to > lose, big time!) > > N.B.: This is in a plain-vanilla 4-drive, one controller, ccd configuration: > No mirroring, no CCDF_SWAP or CCDF_UNIFORM flags. I'd have to play some to > benchmark these. > > I briefly tested a configuration with dual Seagate 12550N's, one with 512K > and one with 1M (!) on-drive cache and the result was similar; performance > "balanced" best with an interleave of around 1000 (which is just under the > size of the smaller cache). > > YMMV, I learned a "lot" by just playing with the values and newfs'ing. This is all well and fine if you are interested in bandwidth out to your drives. If you want to be able to write a 100MB file as quickly as possible - great! But in Usenet news, you don't CARE about that as the average transfer size is pretty small, and therefore "pretty short", and going twice as fast results in "half of pretty short" time to do an operation. What you REALLY want is to let each drive do different operations. Let's say you have a big news box and 100 readers, and they are all pounding on six disks. If you use a small interleave, what will happen is that several drives will be involved with each individual reader access. Let's pretend that the number is three... three drives have to move their heads to do a single access for a single reader. You still have three drives free so another reader can also be accessing an article. So if you have 100 requests, you need 50 units of time to satisfy those requests. Now let's say you do it my way. The odds switch and favor a single drive being able to complete a file access for a single reader. That means that there are five drives available, so five other clients can be getting their articles off of other drives. So if you have 100 requests, you need about 16 units of time to satisfy those requests. In my book, if it takes less time to satisfy the same number of requests, it is a win :-) You don't give a damn about bandwidth. It is useless for a news spool. You want concurrency. You get that with large stripe sizes. Please read the mailing list archives for my long dissertations on this very subject! ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-hackers Fri Jan 10 09:19:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA21834 for hackers-outgoing; Fri, 10 Jan 1997 09:19:11 -0800 (PST) Received: from earth.infinetconsulting.com (earth.infinetconsulting.com [207.23.43.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA21825 for ; Fri, 10 Jan 1997 09:19:03 -0800 (PST) Received: (from lenc@localhost) by earth.infinetconsulting.com (8.6.12/8.6.12) id JAA27678; Fri, 10 Jan 1997 09:32:27 -0800 Date: Fri, 10 Jan 1997 09:32:27 -0800 (PST) From: Leonard Chua To: freebsd-hackers@freebsd.org Subject: pppd and the login option Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi. I've been working on setting up a ppp dialup server. I've gotten it to work with PAP via pap-secrets, and I'm now experimenting with it doing PAP authentication through the system password database (by the 'login' option). I've found that pppd keeps dying at login verification. On going through the source code, I've managed to pinpoint the problem to the crypt() call in login(): (file auth.c somewhere about line 500:) epasswd = (char *) crypt(passwd, pw->pw_passwd); if (strcmp(epasswd, pw->pw_passwd)) { syslog(LOG_WARNING,"FAILED crypt validation."); return (UPAP_AUTHNAK); } It core dumps with a segmentation fault at the crypt() call. To make sure that crypt() is not at fault, I made a similar copy of the login function in a separate test file, and it works there. I can put up the test file if anyone likes to take a look. Anyone have any ideas? The mailing lists show quite a few people with problems with the login option. Maybe this is the reason. Thanks. Len. PS> why do I want to use the system database? Simple - I don't like having a unencrypted password file anywhere (even if it's supposedly group and world unreadable). From owner-freebsd-hackers Fri Jan 10 09:26:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA22082 for hackers-outgoing; Fri, 10 Jan 1997 09:26:17 -0800 (PST) Received: from earth.infinetconsulting.com (earth.infinetconsulting.com [207.23.43.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA22077; Fri, 10 Jan 1997 09:26:15 -0800 (PST) Received: (from lenc@localhost) by earth.infinetconsulting.com (8.6.12/8.6.12) id JAA27713; Fri, 10 Jan 1997 09:39:37 -0800 Date: Fri, 10 Jan 1997 09:39:37 -0800 (PST) From: Leonard Chua To: John-Mark Gurney cc: freebsd-hackers@freebsd.org, freebsd-isp@freebsd.org Subject: Re: pppd and the login option In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > well... could you inform us to what version of FreeBSD your running? (and > ident of /usr/sbin/pppd would be nice too...) I'm running pppd with the > login option (plus a few local hacks) and it's running fine... I never > have seen pppd seg fault there.... of course that's because I haven't seen > it seg fault :)... It's kernel pppd 2.1 pl2 and FreeBSD 2.1.0 using gcc 2.6.3 > plus it's also very hard for your users to change there password :) > ttyl.. It's still in consideration, but I wouldn't want to give them a login shell. I would prefer to use a secured web page for them to change their passwords. Len. From owner-freebsd-hackers Fri Jan 10 09:49:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA23081 for hackers-outgoing; Fri, 10 Jan 1997 09:49:29 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA22958 for ; Fri, 10 Jan 1997 09:46:53 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id SAA12333; Fri, 10 Jan 1997 18:48:35 +0100 (MET) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.3/8.6.9) id SAA01138; Fri, 10 Jan 1997 18:46:31 +0100 (MET) From: Christoph Kukulies Message-Id: <199701101746.SAA01138@gilberto.physik.rwth-aachen.de> Subject: Re: A cool xterm? In-Reply-To: <199701101606.IAA03133@impulse.csl.sri.com> from Fred Gilham at "Jan 10, 97 08:06:53 am" To: gilham@csl.sri.com (Fred Gilham) Date: Fri, 10 Jan 1997 18:46:31 +0100 (MET) Cc: freebsd-hackers@freebsd.org Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > Randal Hopper wrote: > ---------------------------------------- > Charles Henrich: > |Has anyone out there ever found a nice terminal window, something > |like Dec's mterm, or ssh for windows, or even better, NeXT's > |terminal? Xterm is peachy, except the scrollback just sucks :) > > Rebuilt the color_xterm port linking with Xaw3d instead of Xaw, and the > scrollbar's much better. Like the menus better too. ...with these resources: > ---------------------------------------- I put the resources Randal posted into my .Xdefaults and the following funny happens: (I rebuilt color_xterm with all Xaw refs changed to Xaw3d in the Makefile) Running fvwm95-2 my color_xterms that pop up initially (by .xinitrc - I'm using startx) have 3D-effect scrollbars and shaded edged pop up menues but with dithered gray shades rather than the colored shades. Only newly created color_xterms (launched from the tool bar) show the correct colors and solid colored shades. I event put the resources into .Xresources - no change. Any ideas? > > I'm wondering what this means. Is it that people don't like the fact > that the scrollbar works the way it does? Or is it that they don't > like the way it looks? What exactly is wrong with the scrollbar? > > To put my own oar in the water, I'll say that the original Athena > scrollbar is the only scrollbar I've seen with a decent user > interface. Once you get used to it, anything else is harder to use. > I hope there's always a scrollbar around with the Athena user > interface. > > -Fred Gilham gilham@csl.sri.com > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Fri Jan 10 10:35:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA24969 for hackers-outgoing; Fri, 10 Jan 1997 10:35:52 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA24955 for ; Fri, 10 Jan 1997 10:35:41 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <18901(6)>; Fri, 10 Jan 1997 10:34:34 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177476>; Fri, 10 Jan 1997 10:32:52 -0800 To: Josh MacDonald cc: freebsd-hackers@freebsd.org Subject: Re: texinfo changes ready In-reply-to: Your message of "Thu, 09 Jan 97 22:46:13 PST." <199701100646.WAA07104@paris.CS.Berkeley.EDU> Date: Fri, 10 Jan 1997 10:32:47 PST From: Bill Fenner Message-Id: <97Jan10.103252pst.177476@crevenia.parc.xerox.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199701100646.WAA07104@paris.CS.Berkeley.EDU> you write: >4. Import the original sources post-configured and patched into > gnu/texinfo. You should import the original tar file into src/contrib/texinfo, then apply any needed patches and commit them on the HEAD. Having the original source on the vendor branch makes merging new versions much easier. You should also create a BSD-style makefile in src/gnu/usr.bin/texinfo derived from the makefile that configure creates. Bill From owner-freebsd-hackers Fri Jan 10 10:45:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA25334 for hackers-outgoing; Fri, 10 Jan 1997 10:45:11 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA25329 for ; Fri, 10 Jan 1997 10:45:08 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id NAA19882; Fri, 10 Jan 1997 13:44:56 -0500 (EST) Date: Fri, 10 Jan 1997 13:44:56 -0500 (EST) From: Charles Henrich Message-Id: <199701101844.NAA19882@crh.cl.msu.edu> To: wh@mx.ba-stuttgart.de, freebsd-hackers@freebsd.org Subject: Re: mount -o async on a news servre Newsgroups: lists.freebsd.hackers References: <5b5htc$ppf@msunews.cl.msu.edu> X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In lists.freebsd.hackers you write: >The update(4) process does a sync every 30 min. Every 30 seconds by default, but its tunable with sysctl.. -Crh -- Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Fri Jan 10 11:24:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA27082 for hackers-outgoing; Fri, 10 Jan 1997 11:24:32 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA27004 for ; Fri, 10 Jan 1997 11:23:58 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA06449; Fri, 10 Jan 1997 20:23:29 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id UAA23913; Fri, 10 Jan 1997 20:19:23 +0100 (MET) Message-ID: Date: Fri, 10 Jan 1997 20:19:23 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: jmacd@CS.Berkeley.EDU (Josh MacDonald) Cc: freebsd-hackers@freebsd.org Subject: Re: texinfo changes ready References: <199701100646.WAA07104@paris.CS.Berkeley.EDU> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701100646.WAA07104@paris.CS.Berkeley.EDU>; from Josh MacDonald on Jan 9, 1997 22:46:13 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Josh MacDonald wrote: > 4. Import the original sources post-configured and patched into > gnu/texinfo. Better, import them into src/contrib/texinfo, and make the Makefiles under src/gnu/texinfo reference the original files. Files you wish to override can still be put under src/gnu/texinfo, of course. You could have a look at src/usr.bin/vi for an example of something that references files from `contrib'. The rationale behind this is that it eases merging new vendor versions, since the FreeBSD changes are largely divorced from the vendor sources. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Fri Jan 10 12:18:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA29824 for hackers-outgoing; Fri, 10 Jan 1997 12:18:33 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA29814 for ; Fri, 10 Jan 1997 12:18:30 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA20414; Fri, 10 Jan 1997 13:06:51 -0700 From: Terry Lambert Message-Id: <199701102006.NAA20414@phaeton.artisoft.com> Subject: Re: mount -o async on a news servre To: scrappy@hub.org (The Hermit Hacker) Date: Fri, 10 Jan 1997 13:06:51 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: from "The Hermit Hacker" at Jan 10, 97 06:59:08 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk More information that you probably want; on the other hand, this is the first time I've laid out explicit examples of failure cases in anything but the broadest terms (I've always felt they should be blatantly obvious to anyone who has looked at the problem enough that they were willing to post comments; unfortunately, not enough people have that much self control). > Exactly *how* dangerous is setting a file system to async? Depends on how much you will miss the data if it disappears. For passive news servers, not very. For those which you post users articles to, when you rebuild the FS, you will get the articles which have propagated already, but your users articles for the propagation delay period (times a 1.5 probability vector) could be lost. So Bob posts something, your server crashes before it is propagated, and Bob's article is now lost. If you provide posting services, this denial of service may in fact annoy some people. It would annoy me, if it happened. For a regular FS, it is nearly too dangerous to contemplate, unless you can guarantee that the only time your system will go down is when you shut it down on purpose (ie: you have a UPS, adequate environmental controls for the room the machine lives in, etc.). Effectively, then, you are engaging in a risk/reward analysis. > In my case, I'm braving it on a news server, just the ccd > device that contains both the news admin and spool directories. The > drive is local to the system. > > My understanding of asynchronous I/O is that it doesn't wait > for an acknowledgement from the system before going to the next > write (only, its a very basic understanding?), so I'm curiuos as how > it would handle writting the history file itself? The write returns before it is committed to stable storage. If you have a failure in this situation, then you will lose some (random) number of writes. Because UFS/FFS/EXT2FS are not logging or journalling (note: I did not say "not log structured"; structuring is irrelevent for this discussion), this means that you have: o The state that you wanted the FS in o The state the FS is actually in o An unknown number of intermediate states between the two File system repair utilities (like fsck) take an FS from: o The state the FS is actually in To: o A state wherein the FS is internally consistent Because of Godel's Theorem, you can't guarantee that: o A state wherein the FS is internally consistent Is equal to: o The state that you wanted the FS in If you have async on. Because once the number of unknown intermediate states exceeds 2, the intended target state of an inconsistent state is no longer determinite. There are multiple potential paths to consistency, (2^(number of pending async operations - 1), in fact), but only one of them is correct. If you had 11 writes outstanding at the time of the crash, you would have only a 1 out of 1024 chance of doing the write thing... less than 1/10th of 1% change of getting the FS corrected to where it's supposed to be instead of only geting the FS cortrected to the point where it's simply "usable". Consider the example of a database engaged in a two state commit. The procedure it will follow to change a record is: --- BEGIN TRANSACTION --- 1. Read the index record for the data record to change into memory 2. Read the data record to change into memory 3. Modify the data record in memory 4. Obtain exclusive access to an unused data record 5. Write the modified data record from memory into the unused data record on disk --- COMMIT STAGE 1 COMPLETED --- 6. Modify the index record in memory 7. Write the modified index record to disk --- COMMIT STAGE 2 COMPLETED --- --- END TRANSACTION --- (A logging or journalling FS would write transaction records and keep the writes pending; it is a much simpler implementation, since no disk data would change until the transaction was ended, and the writes would be guaranteed to be ordered). Now understand that the async writes do not guarantee ordering. That is their nature. This means that it is possible that the index record could be written before the data record. If that happens, and the machine crashes, you have a valid (but incorrect) data record (whatever was there before) pointed to by a valid index record, and a valid (but orphaned) data record not pointed to by anyone. Questions: o How do I back the index record transaction out so that the index record points to the orphaned record? o How do I *know* that it wasn't the data record getting written before the index record, and that I shouldn't be advincing the index record instead of backing it up, to run the trasaction to completion? o Will they ever find poor Aunt Nell, lying at the edge of town in a ditch? ...tune in tomorrow... The problem, of course, is that there is *implied* state generated by the program. Short of implementing a transaction tracking system (like NetWare TTS, or, to be more UNIX-like, USL Tuxedo), you can't arbitrarily wind and unwind state. The INN history file would probably need to be rebuilt after each crash (if that were even possible) to ensure that it was in a good state. > The only risk that I can see is that if the system crashes, > I'll have (might have) a corrupted file system, but is that my only > risk? ie. if I turned on async for a period of time (long enough for > a backlog from one system to catch up?) and then turned it back off > again, would that be reasonably safe? It wouldn't matter; it would reduce the duration of your exposure to the time it was on, but it wouldn't eliminate the exposure entirely, or reduce it overall. The problem still boils down to whether you can deterministically put the FS in the state that it would have been had the system not crashed. Effectively, this means ordering the writes. There are a number of ways to do this: o Order them explicitly by not doing async writes. This is what the non-async FFS/EXT2FS implements; it is the most simple method, easiest to implement, and reduces the concurrency the most. It is the worst way to implement a good thing. o Order them explicitly by doing async writes to stable cache. This requires specialized hardware and is not a generic soloution. Sun's PrestoServe hardware does this; so do Auspex NFS servers. You would be hard put to find PC controllers even capable of this, let alone drivers that could handle it. The BIO subsystem would require significant changes to be able to put stable commit incursions up to the point an FS could choose between a stable commit to cache, a stable commit to disk, and an unstable commit to disk (a necessary optimization for non-metadata data originating locally instead of as the result of a network transaction). This is an OK, if very expensive, way to implement a good thing. o Order them implicitly by time and idempotence. This is what Delayed Ordered Writes (DOW -- a USL patented technology) does. Basically, I can do unordered writes as much as I want for "unimportant" things, but when I need to do writes involving FS structure, then I commit all outstanding I/O's (drain them to the disk). In SVR4.2 ES/MP (UnixWare 2.x), this results in a 60% increase in throughput to the disk, even in the Uniprocessor case. This is a patented, and therefore unusable in a public project, way of implementing a good thing. o Order them implicitly by graph relation; this may or may not include time relationships, if they happen to be members of the graph hierarchy. This is what Soft Updates (from the Ganger/Patt paper) does. Basically, I can do writes in any order, and when I have a write that depends on another write being committed before it is, I insert a queue synchronization so that associative and commutative transformation on the graph node relationships won't cross the synchronization boundries. This results in speeds approaching 5% of memory speeds (until cache limits impose disk latency slowdowns). In fact, this method tends to result in faster code than simple async writes because of increased locality seperating metadata and non-metadata operations. It is the best way (so far) to implement a good thing. Obviously, I would use soft updates if I could. But in no case would I run for a long time with async; if you want more speed, you should be willing to pay for it in code, and not kludge things in such a way that you could potentially lose data. It is the difference between doing the right thing the right way and the right thing the wrong way. > BTW...what exactly does fastfs do? My understanding is that > this is basically what it does, turns the file system to be async vs > sync... Yes; this is exactly what it does; there is a minor difference in the gathering of directory operations (there is an #ifdef'ed DEBUG sysctl() variable for directory ordering which is also affected; I really don't know why the directory ordering was ommitted in the standard sync case; I believe it is an error in the UFS implementation... Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Jan 10 12:25:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA00390 for hackers-outgoing; Fri, 10 Jan 1997 12:25:46 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA00384 for ; Fri, 10 Jan 1997 12:25:43 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA20438; Fri, 10 Jan 1997 13:14:39 -0700 From: Terry Lambert Message-Id: <199701102014.NAA20438@phaeton.artisoft.com> Subject: Re: A cool xterm? To: gilham@csl.sri.com (Fred Gilham) Date: Fri, 10 Jan 1997 13:14:39 -0700 (MST) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199701101606.IAA03133@impulse.csl.sri.com> from "Fred Gilham" at Jan 10, 97 08:06:53 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Rebuilt the color_xterm port linking with Xaw3d instead of Xaw, and the > scrollbar's much better. Like the menus better too. ...with these resources: > ---------------------------------------- > > I'm wondering what this means. Is it that people don't like the fact > that the scrollbar works the way it does? Or is it that they don't > like the way it looks? What exactly is wrong with the scrollbar? It's ugly, it fails the page up/down in the thumb area, it does not have a single-step up/down button, and it takes too many buttons on your mouse to make it work efficiently. Other than that, there's no problem with it. > To put my own oar in the water, I'll say that the original Athena > scrollbar is the only scrollbar I've seen with a decent user > interface. Once you get used to it, anything else is harder to use. > I hope there's always a scrollbar around with the Athena user > interface. NextStep has the increment up/down adjacent to each other; that is a big, big win in my book; I don't have to move the mouse pointer across nearly as much realestate to change direction if I overshoot by one line while scrolling. I think the riginal complaint was that cleared screens did not get added as complete units to the scrollback buffer of xterm. Consider the cursor addressing application which paints many areas of the screen prior to the screen being "accepted" for processing; this is both the "block mode" terminal processing model, and more recently, the modal dialog processing model. In addition, there is no way to distinguish screens in the scrollback, even if they were added, because there is no framing in the scrollback buffer itself. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Jan 10 12:25:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA00411 for hackers-outgoing; Fri, 10 Jan 1997 12:25:51 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA00402 for ; Fri, 10 Jan 1997 12:25:48 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA07220; Fri, 10 Jan 1997 21:24:58 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id VAA24150; Fri, 10 Jan 1997 21:12:42 +0100 (MET) Message-ID: Date: Fri, 10 Jan 1997 21:12:42 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi) Cc: hackers@freebsd.org Subject: Re: Why 2.2 tzsetup does't make /etc/wall_cmos_clock? References: <199701101341.WAA13105@frig.mt.cs.keio.ac.jp> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701101341.WAA13105@frig.mt.cs.keio.ac.jp>; from HOSOKAWA Tatsumi on Jan 10, 1997 22:41:55 +0900 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As HOSOKAWA Tatsumi wrote: > I remember that tzsetup of 2.1.x made /etc/wall_cmos_clock when I > specified "CMOS clock == localtime", but 2.2 tzsetup does not make > this file. > > Is this a "feature"? or a bug?, It seems to be slipped off when Garrett removed the (fairly silly) previous ``What's your CMOS set to?'' handling. > and is there another way to create > /etc/wall_cmos_clock from sysinstall? Not yet, except from the Emergency Holographic Shell. ;) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Fri Jan 10 12:29:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA00699 for hackers-outgoing; Fri, 10 Jan 1997 12:29:37 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA00691 for ; Fri, 10 Jan 1997 12:29:35 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA20456; Fri, 10 Jan 1997 13:17:36 -0700 From: Terry Lambert Message-Id: <199701102017.NAA20456@phaeton.artisoft.com> Subject: Re: mount -o async on a news servre To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Fri, 10 Jan 1997 13:17:36 -0700 (MST) Cc: wh@mx.ba-stuttgart.de, freebsd-hackers@freebsd.org In-Reply-To: <199701101844.NAA19882@crh.cl.msu.edu> from "Charles Henrich" at Jan 10, 97 01:44:56 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > In lists.freebsd.hackers you write: > > >The update(4) process does a sync every 30 min. > > Every 30 seconds by default, but its tunable with sysctl.. Due to two cooperating coding errors, setting this value higher will increase the time between when you unmount removable media and the time you can successfully eject the media (in case you were wondering about the delay on ejecting clean JAZ disks...). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Jan 10 12:59:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA02185 for hackers-outgoing; Fri, 10 Jan 1997 12:59:37 -0800 (PST) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA02179 for ; Fri, 10 Jan 1997 12:59:34 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr2-43.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA01661 (5.67b/IDA-1.5 for ); Fri, 10 Jan 1997 21:59:30 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.4/8.6.9) id VAA04628; Fri, 10 Jan 1997 21:58:46 +0100 (CET) Message-Id: Date: Fri, 10 Jan 1997 21:57:25 +0100 From: se@freebsd.org (Stefan Esser) To: dwhite@resnet.uoregon.edu (Doug White) Cc: hackers@freebsd.org Subject: Re: ncr probe FAILS on 2.2-BETA_A! References: X-Mailer: Mutt 0.55-PL15 Mime-Version: 1.0 In-Reply-To: ; from Doug White on Jan 10, 1997 00:38:52 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Jan 10, dwhite@gdi.uoregon.edu (Doug White) wrote: > Hello! > > I'm attempting to install 2.2-BETA_A on a SiS Pentium 100 system, and the > ncr startup locks the system up just after > > ncr0 waiting for devices to settle > > This machine works perfectly with 2.2-ALPHA. I've booted -c and reduced > the devices to the bare necessities with no change. Hmm, the NCR driver changes between ALPHA and BETA are quite simple, and mostly stylistic ... > ncr0 rev 3 int a irq 11 on pci0:13 > ncr0 waiting for scsi devices to settle <-- 2.2-BETA stops here > (ncr0:3:0): "PLEXTOR CD-ROM PX-4XCE 1.00" type 5 removable SCSI 2 > The SCSI devices to receive the bus reset, as the lights on the CDROMs > light up, but that's all. The floppy drive light is stuck on and the > keyboard LEDs don't function when the lockup occurs. I expect this to be a problem with your chip set ... Perhaps you want to try booting with PCI options (write buffers, PCI burst mode) disabled. > There were no changes to the system configuration between shutting down > 2.2-ALPHA and booting the BETA floppy. > > Sorry for taking so long to report this; today is the only time I've had > to try plugging in BETA. > > Boot -v and other information available by request. Please try the applied patch. If it doesn't work, then send boot -v messages. If you have access to the CVS tree, you may want to use the driver from 2.2-ALPHA. I can send you a context diff, if you prefer that ... Regards, STefan From owner-freebsd-hackers Fri Jan 10 12:59:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA02204 for hackers-outgoing; Fri, 10 Jan 1997 12:59:40 -0800 (PST) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA02175 for ; Fri, 10 Jan 1997 12:59:32 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr2-43.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA01657 (5.67b/IDA-1.5 for ); Fri, 10 Jan 1997 21:59:23 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.4/8.6.9) id VAA04651; Fri, 10 Jan 1997 21:59:19 +0100 (CET) Message-Id: Date: Fri, 10 Jan 1997 21:59:19 +0100 From: se@freebsd.org (Stefan Esser) To: dwhite@resnet.uoregon.edu (Doug White) Cc: hackers@freebsd.org Subject: Re: ncr probe FAILS on 2.2-BETA_A! References: X-Mailer: Mutt 0.55-PL15 Mime-Version: 1.0 In-Reply-To: ; from Doug White on Jan 10, 1997 00:38:52 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, I forgot to include the context diff ... Here it comes: Index: ncr.c =================================================================== RCS file: /usr/cvs/src/sys/pci/ncr.c,v retrieving revision 1.82.2.5 retrieving revision 1.82 diff -C2 -r1.82.2.5 -r1.82 *** ncr.c 1997/01/06 21:12:40 1.82.2.5 --- ncr.c 1996/10/14 10:09:52 1.82 *************** *** 4419,4426 **** */ ! burstlen = 0xc0; /* XXX 53c875 needs code change to */ ! /* be able to use larger bursts */ ! OUTB (nc_istat, 0x00 ); /* Remove Reset, abort ... */ OUTB (nc_scntl0, 0xca ); /* full arb., ena parity, par->ATN */ OUTB (nc_scntl1, 0x00 ); /* odd parity, and remove CRST!! */ --- 4416,4429 ---- */ ! #ifndef __NetBSD__ ! if (pci_max_burst_len < 4) { ! static u_char tbl[4]={0,0,0x40,0x80}; ! burstlen = tbl[pci_max_burst_len]; ! } else burstlen = 0xc0; ! #else /* !__NetBSD__ */ ! burstlen = 0xc0; ! #endif /* __NetBSD__ */ ! OUTB (nc_istat, 0 ); /* Remove Reset, abort ... */ OUTB (nc_scntl0, 0xca ); /* full arb., ena parity, par->ATN */ OUTB (nc_scntl1, 0x00 ); /* odd parity, and remove CRST!! */ From owner-freebsd-hackers Fri Jan 10 13:07:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA03010 for hackers-outgoing; Fri, 10 Jan 1997 13:07:48 -0800 (PST) Received: from home.winc.com (mgessner@home.winc.com [204.178.182.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA02986 for ; Fri, 10 Jan 1997 13:07:28 -0800 (PST) Received: (from mgessner@localhost) by home.winc.com (8.8.4/8.8.4) id QAA23987 for hackers@freebsd.org; Fri, 10 Jan 1997 16:05:56 -0500 Message-Id: <199701102105.QAA23987@home.winc.com> Subject: bind(2): address already in use -- how to fix? To: hackers@freebsd.org (FreeBSD Hackers) Date: Fri, 10 Jan 1997 16:05:55 -0500 (EST) From: mgessner@aristar.com Organization: Aristar Software Development, Inc. Reply-To: mgessner@aristar.com X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, all, I'm doing some what I think to be VERY straightforward server code. I call socket(), bind(), listen() and then accept(). I am binding to a constant port number, so that my clients will always know where to connect. If the descriptor returned by accept() is valid, I call fork, close the original descriptor returned by socket(), and then start my processing in the child. In the child, I use read(2) and write(2) to communicate, and when all done, call close(2) on the new socket to close the connection, and then call exit(). I have a SIG_CHLD handler set up, so that I can watch the termination. Now something funny happens: in sig_chld, I get reported to me several pids that WERE NOT the result of a fork() call by the server. Why is this? Also, when I terminate my program when a child has not closed its socket because the client has crashed, if I try to restart my server I get the error message: "Address already in use" I do have a SIG_INT handler defined, and in it, I check the child pid value (0 or non-zero). If it's zero, I close the child's socket, else I close the parent's socket. I'm pretty confused about this whole problem. It doesn't seem to me that this should be so difficult, and the syntax for setting these sockets for client/server access are pretty well known. I do have a copy of Stevens' Unix Network Programming that I'm using, but that doesn't seem to help too much. This problem causes me to have to reboot my machine, which is very undesirable. Can someone please shed some light on this? I've attached a copy of my source. Thanks in advance. Matt Gessner #include #include #include #include #include #include #include #include #include #include #define K 1024 char *pkgdir; /* spit out a list of all the files in the pkgdir via sockfd */ void pkglist (int sockfd) { FILE *p; char buf[32 * K], name[32]; sprintf (buf, "ls %s", pkgdir); p = popen (buf, "r"); strcpy (buf, "["); while (! feof (p)) { fscanf (p, "%s\n", name); strcat (buf, "\""); strcat (buf, name); strcat (buf, "\","); } strcat (buf, "]\n"); writec (sockfd, buf, strlen (buf), 3); } /* return a text file 'pkgname' in pkgdir. via sockfd */ void pkggett (int sockfd, const char *pkgname) { int f; char fbuf[128], c; int len, w = 0; sprintf (fbuf, "%s/%s", pkgdir, pkgname); if ((f = open (fbuf, O_RDONLY)) > 0) { while ((len = read (f, (void *) fbuf, 128)) > 0) { w = write (sockfd, fbuf, len); } c = 3; write (sockfd, &c, 1); close (f); } else { fprintf (stderr, "error opening %s\n", fbuf); } } /* return a binary file 'pkgname' via sockfd */ void pkgget (int sockfd, const char *pkgname) { int f; char fbuf[128], c; int len, w = 0; sprintf (fbuf, "%s/%s", pkgdir, pkgname); if ((f = open (fbuf, O_RDONLY)) > 0) { while ((len = read (f, (void *) fbuf, 128)) > 0) { w = write (sockfd, fbuf, len); } close (f); } else { fprintf (stderr, "error opening %s\n", fbuf); } } /* the main child command loop. accepts commands via sockfd and sends the appropriate response. */ void pkgsrv (int sockfd) { char cmd[64]; int done = 0, len; while (! done) { if ((len = readc (sockfd, cmd, sizeof cmd, 3)) > 0) { fprintf (stderr, "my pid is %d\n", getpid()); fprintf (stderr, "command is %s\n", cmd); if (strncasecmp (cmd, "list", 4) == 0) { pkglist(sockfd); } else if (strncasecmp (cmd, "gett ", 5) == 0) { pkggett (sockfd, (char *) &cmd[5]); } else if (strncasecmp (cmd, "get ", 4) == 0) { fprintf (stderr, "sending package %s\n", &cmd[4]); pkgget (sockfd, (char *) &cmd[4]); fprintf (stderr, "sent package %s\n", &cmd[4]); } else if (strncasecmp (cmd, "quit", 4) == 0) { done = 1; } else { fprintf (stderr, "received unrecognized command: %s\n", cmd); } } else { done = 1; } } } int sockfd, newsockfd, childpid; void sig_int () { fprintf (stderr, "terminating on SIGINT\n"); if (childpid != 0) { close (sockfd); } else { close (newsockfd); } exit (-1); } void sig_chld () { int pid, status; /* sometimes this returns a pid which was not created via the fork() below */ while ((pid = wait3 (&status, WNOHANG, (struct rusage *) 0)) > 0) fprintf (stderr, "child %d terminating, status = %08x\n", pid, status); } void main (int argc, char *argv[]) { int clilen; struct sockaddr_in serv_addr, cli_addr; if (argc == 2) { signal (SIGINT, sig_int); signal (SIGCHLD, sig_chld); /* set the pkgdir pointer */ pkgdir = argv[1]; /* Get a socket. */ if ((sockfd = socket (AF_INET, SOCK_STREAM, 0)) < 0) { err_sys ("socket error"); } /* bind the socket to a named port */ bzero ((char *) &serv_addr, sizeof serv_addr); serv_addr.sin_family = AF_INET; serv_addr.sin_addr.s_addr = INADDR_ANY; serv_addr.sin_port = htons (54321); if (bind (sockfd, (struct sockaddr *) &serv_addr, sizeof serv_addr) < 0) { err_sys ("bind error"); } /* listen for requests for connection on the socket */ listen (sockfd, 5); for ( ; ; ) { /* accept a connection request */ fprintf (stderr, "Waiting for connection on port %d\n", htons (serv_addr.sin_port)); clilen = sizeof cli_addr; newsockfd = accept (sockfd, (struct sockaddr *) &cli_addr, &clilen); fprintf (stderr, "connection established with %s on port %d\n", inet_ntoa (cli_addr.sin_addr), htons (cli_addr.sin_port)); if (newsockfd < 0) { err_sys ("accept error"); } if ((childpid = fork()) < 0) { err_sys ("fork error"); } else if (childpid == 0) { close (sockfd); pkgsrv (newsockfd); close (newsockfd); fprintf (stderr, "closing connection with %s on port %d\n", inet_ntoa (cli_addr.sin_addr), htons (cli_addr.sin_port)); exit (0); } else { fprintf (stderr, "spawned child process %d\n", childpid); close (newsockfd); } } } else { fprintf (stderr, "usage: %s pkgdir\n", argv[0]); exit (1); } } -- Matthew Gessner , Computer Scientist Aristar, Inc. 302 N. Cleveland-Massillon Rd. Akron, OH 44333 (330) 668-2267, (330) 668-2961 FAX From owner-freebsd-hackers Fri Jan 10 13:59:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA05590 for hackers-outgoing; Fri, 10 Jan 1997 13:59:10 -0800 (PST) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA05566 for ; Fri, 10 Jan 1997 13:58:30 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr2-43.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA01751 (5.67b/IDA-1.5 for ); Fri, 10 Jan 1997 22:58:24 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.4/8.6.9) id WAA06411; Fri, 10 Jan 1997 22:58:16 +0100 (CET) Message-Id: Date: Fri, 10 Jan 1997 22:58:16 +0100 From: se@freebsd.org (Stefan Esser) To: scott@cns.ucla.edu (Scott Burris) Cc: freebsd-hackers@freebsd.org Subject: Re: 2.2-BETA hangs after a few minutes References: X-Mailer: Mutt 0.55-PL15 Mime-Version: 1.0 In-Reply-To: ; from Scott Burris on Jan 5, 1997 10:39:38 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Jan 5, scott@cns.ucla.edu (Scott Burris) wrote: > > To follow up my own message, I compiled the exact same kernel > configuration from 2.2-ALPHA and it works perfectly on this system. > So something bad has happened between ALPHA and BETA. Guess it's > time to start diff-ing the kernel source trees to see what's changed > :-( Please send verbose boot messages (enter "-v" at the Boot: prompt). Regards, STefan From owner-freebsd-hackers Fri Jan 10 14:01:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA05725 for hackers-outgoing; Fri, 10 Jan 1997 14:01:10 -0800 (PST) Received: from sumatra.americantv.com (sumatra.americantv.com [199.184.181.250]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA05716 for ; Fri, 10 Jan 1997 14:01:01 -0800 (PST) Received: from right.PCS (right.pcs. [148.105.10.31]) by sumatra.americantv.com (8.7.6/8.7.3) with ESMTP id PAA25851; Fri, 10 Jan 1997 15:59:23 -0600 (CST) Received: (jlemon@localhost) by right.PCS (8.6.13/8.6.4) id WAA12979; Fri, 10 Jan 1997 22:00:36 GMT Message-ID: Date: Fri, 10 Jan 1997 16:00:35 -0600 From: jlemon@americantv.com (Jonathan Lemon) To: terry@lambert.org (Terry Lambert) Cc: gilham@csl.sri.com (Fred Gilham), freebsd-hackers@freebsd.org Subject: Re: A cool xterm? References: <199701101606.IAA03133@impulse.csl.sri.com> <199701102014.NAA20438@phaeton.artisoft.com> X-Mailer: Mutt 0.56e Mime-Version: 1.0 In-Reply-To: <199701102014.NAA20438@phaeton.artisoft.com>; from Terry Lambert on Jan 10, 1997 13:14:39 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert writes: > > Rebuilt the color_xterm port linking with Xaw3d instead of Xaw, and the > > scrollbar's much better. Like the menus better too. ...with these resources: > > ---------------------------------------- > > > > I'm wondering what this means. Is it that people don't like the fact > > that the scrollbar works the way it does? Or is it that they don't > > like the way it looks? What exactly is wrong with the scrollbar? > > It's ugly, it fails the page up/down in the thumb area, it does not > have a single-step up/down button, and it takes too many buttons > on your mouse to make it work efficiently. > > Other than that, there's no problem with it. It's just ugly. (I do like the NeXT scrollbars too). As for usage, I just use the following in my XTerm resource file; it's faster than trying to get the mouse onto the right scrollbar area: *VT100.translations: #override \ CtrlPrior: scroll-back(1,halfpage)\n\ CtrlNext: scroll-forw(1,halfpage)\n\ CtrlInsert: scroll-back(1,line)\n\ CtrlDelete: scroll-forw(1,line) -- Jonathan From owner-freebsd-hackers Fri Jan 10 14:07:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA05956 for hackers-outgoing; Fri, 10 Jan 1997 14:07:02 -0800 (PST) Received: from sumatra.americantv.com (sumatra.americantv.com [199.184.181.250]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA05949 for ; Fri, 10 Jan 1997 14:06:56 -0800 (PST) Received: from right.PCS (right.pcs. [148.105.10.31]) by sumatra.americantv.com (8.7.6/8.7.3) with ESMTP id QAA25875; Fri, 10 Jan 1997 16:05:24 -0600 (CST) Received: (jlemon@localhost) by right.PCS (8.6.13/8.6.4) id WAA14513; Fri, 10 Jan 1997 22:06:37 GMT Message-ID: Date: Fri, 10 Jan 1997 16:06:36 -0600 From: jlemon@americantv.com (Jonathan Lemon) To: terry@lambert.org (Terry Lambert) Cc: scrappy@hub.org (The Hermit Hacker), hackers@freebsd.org Subject: Re: mount -o async on a news servre References: <199701102006.NAA20414@phaeton.artisoft.com> X-Mailer: Mutt 0.56e Mime-Version: 1.0 In-Reply-To: <199701102006.NAA20414@phaeton.artisoft.com>; from Terry Lambert on Jan 10, 1997 13:06:51 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert writes: > Effectively, this means ordering the writes. There are a number > of ways to do this: > > o Order them explicitly by doing async writes to stable > cache. This requires specialized hardware and is not a > generic soloution. Sun's PrestoServe hardware does this; > so do Auspex NFS servers. You would be hard put to find PC > controllers even capable of this, let alone drivers that > could handle it. The BIO subsystem would require significant > changes to be able to put stable commit incursions up to > the point an FS could choose between a stable commit to > cache, a stable commit to disk, and an unstable commit to disk > (a necessary optimization for non-metadata data originating > locally instead of as the result of a network transaction). > This is an OK, if very expensive, way to implement a good thing. Another possibility is illustrated in a recent ASPLOS paper on robustness in the face of operating system crashes. IIRC, their system (Petal?) has the entire DRAM on a battery backup, and after a crash/reboot, a diagnostic utility goes through memory and writes out any pending data buffers. I'm not convinced that this would really increase reliability; most problems are usually hardware/power supply based; not OS crashes. -- Jonathan From owner-freebsd-hackers Fri Jan 10 14:12:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA06191 for hackers-outgoing; Fri, 10 Jan 1997 14:12:04 -0800 (PST) Received: from chai.plexuscom.com (chai.plexuscom.com [207.87.46.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA06174 for ; Fri, 10 Jan 1997 14:11:58 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by chai.plexuscom.com (8.8.4/8.6.12) with SMTP id RAA13433; Fri, 10 Jan 1997 17:11:57 -0500 (EST) Message-Id: <199701102211.RAA13433@chai.plexuscom.com> X-Authentication-Warning: chai.plexuscom.com: localhost [127.0.0.1] didn't use HELO protocol To: Terry Lambert Cc: gilham@csl.sri.com (Fred Gilham), freebsd-hackers@freebsd.org Subject: Re: A cool xterm? In-reply-to: Your message of "Fri, 10 Jan 1997 13:14:39 MST." <199701102014.NAA20438@phaeton.artisoft.com> Date: Fri, 10 Jan 1997 17:11:57 -0500 From: Bakul Shah Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > NextStep has the increment up/down adjacent to each other; that is a > big, big win in my book; I don't have to move the mouse pointer > across nearly as much realestate to change direction if I overshoot > by one line while scrolling. In the scrollbar used in `ups' (the debugger), the distance you drag the cursor determines the *velocity* of scrolling: move the cursor *anywhere* in the scrollbar window; press the left button and drag the cursor up or down. The farther you drag it, the faster the window scrolls. When you get close to the target, you can drag back towards the original position and scrolling can be slowed down to a crawl. If you overshoot, move past the original position to scroll in the opposite direction. This is much like a single dial for fast forward/reverse button on some VCRs. Very handy. A similar scheme for selecting text would be nice. > I think the riginal complaint was that cleared screens did not get added > as complete units to the scrollback buffer of xterm. Yeah, this would be better but can be somewhat confusing. Perhaps a thin horizontal line should separate screens cleared this way. Also, there should be a way to dump lines to a file (on command) as well as increase/decrease line buffer size. From owner-freebsd-hackers Fri Jan 10 14:29:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA06704 for hackers-outgoing; Fri, 10 Jan 1997 14:29:59 -0800 (PST) Received: from sumatra.americantv.com (sumatra.americantv.com [199.184.181.250]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA06699 for ; Fri, 10 Jan 1997 14:29:53 -0800 (PST) Received: from right.PCS (right.pcs. [148.105.10.31]) by sumatra.americantv.com (8.7.6/8.7.3) with ESMTP id QAA25952; Fri, 10 Jan 1997 16:28:28 -0600 (CST) Received: (jlemon@localhost) by right.PCS (8.6.13/8.6.4) id WAA21204; Fri, 10 Jan 1997 22:29:40 GMT Message-ID: Date: Fri, 10 Jan 1997 16:29:39 -0600 From: jlemon@americantv.com (Jonathan Lemon) To: mgessner@aristar.com Cc: hackers@freebsd.org (FreeBSD Hackers) Subject: Re: bind(2): address already in use -- how to fix? References: <199701102105.QAA23987@home.winc.com> X-Mailer: Mutt 0.56e Mime-Version: 1.0 In-Reply-To: <199701102105.QAA23987@home.winc.com>; from mgessner@aristar.com on Jan 10, 1997 16:05:55 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk mgessner@aristar.com writes: > in sig_chld, I get reported to me several pids that WERE NOT > the result of a fork() call by the server. Why is this? Most probably, they are the pids of the processes that you have spawned with popen(). popen() does an implicit fork/exec. > "Address already in use" You need to set SO_REUSEADDR in order to re-use the socket. See your copy of Stevens. -- Jonathan From owner-freebsd-hackers Fri Jan 10 14:52:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA07585 for hackers-outgoing; Fri, 10 Jan 1997 14:52:57 -0800 (PST) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA07575; Fri, 10 Jan 1997 14:52:09 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.2/8.6.12) with SMTP id OAA01067; Fri, 10 Jan 1997 14:52:08 -0800 (PST) Date: Fri, 10 Jan 1997 14:52:08 -0800 (PST) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Stefan Esser cc: hackers@freebsd.org Subject: Re: ncr probe FAILS on 2.2-BETA_A! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 10 Jan 1997, Stefan Esser wrote: > > I'm attempting to install 2.2-BETA_A on a SiS Pentium 100 system, and the > > ncr startup locks the system up just after > > > > ncr0 waiting for devices to settle > > > > This machine works perfectly with 2.2-ALPHA. I've booted -c and reduced > > the devices to the bare necessities with no change. > > Hmm, the NCR driver changes between ALPHA and BETA are > quite simple, and mostly stylistic ... > > > ncr0 rev 3 int a irq 11 on pci0:13 > > ncr0 waiting for scsi devices to settle <-- 2.2-BETA stops here > > (ncr0:3:0): "PLEXTOR CD-ROM PX-4XCE 1.00" type 5 removable SCSI 2 > > > The SCSI devices to receive the bus reset, as the lights on the CDROMs > > light up, but that's all. The floppy drive light is stuck on and the > > keyboard LEDs don't function when the lockup occurs. > > I expect this to be a problem with your chip set ... > > Perhaps you want to try booting with PCI options (write > buffers, PCI burst mode) disabled. I can try that. There is one thing I did change and that was I upgraded the CPU from a 90 to a 133, but the motherboard only does 100MHz, so it's running underclocked at the moment. I'll try fidding with the chipset options. > > > There were no changes to the system configuration between shutting down > > 2.2-ALPHA and booting the BETA floppy. > > > > Sorry for taking so long to report this; today is the only time I've had > > to try plugging in BETA. > > > > Boot -v and other information available by request. > > Please try the applied patch. If it doesn't work, then > send boot -v messages. If you have access to the CVS > tree, you may want to use the driver from 2.2-ALPHA. I > can send you a context diff, if you prefer that ... Unfortunately, this is on the boot.flp and I'm not at all set up to rebuild the system....:( Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-hackers Fri Jan 10 15:03:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA08133 for hackers-outgoing; Fri, 10 Jan 1997 15:03:43 -0800 (PST) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA08109; Fri, 10 Jan 1997 15:03:24 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr2-42.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA02059 (5.67b/IDA-1.5); Fri, 10 Jan 1997 23:59:33 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.4/8.6.9) id XAA06721; Fri, 10 Jan 1997 23:59:29 +0100 (CET) Message-Id: Date: Fri, 10 Jan 1997 23:59:29 +0100 From: se@freebsd.org (Stefan Esser) To: dwhite@resnet.uoregon.edu (Doug White) Cc: se@freebsd.org (Stefan Esser), hackers@freebsd.org Subject: Re: ncr probe FAILS on 2.2-BETA_A! References: X-Mailer: Mutt 0.55-PL15 Mime-Version: 1.0 In-Reply-To: ; from Doug White on Jan 10, 1997 14:52:08 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Jan 10, dwhite@gdi.uoregon.edu (Doug White) wrote: > On Fri, 10 Jan 1997, Stefan Esser wrote: > > Perhaps you want to try booting with PCI options (write > > buffers, PCI burst mode) disabled. > > I can try that. There is one thing I did change and that was I upgraded > the CPU from a 90 to a 133, but the motherboard only does 100MHz, so it's > running underclocked at the moment. Hmmm, that might cause problems, anyway. Could you check with the old CPU, whether the problem still exists ? > > Please try the applied patch. If it doesn't work, then > > send boot -v messages. If you have access to the CVS > > tree, you may want to use the driver from 2.2-ALPHA. I > > can send you a context diff, if you prefer that ... > > Unfortunately, this is on the boot.flp and I'm not at all set up to > rebuild the system....:( Ok, I understand this. But send verbose boot messages from FreeBSD-ALPHA, at least. I need to know your system configuration, or I won't know, whether any part that I modified between ALPHA and BETA might be the culprit ... Regards, STefan From owner-freebsd-hackers Fri Jan 10 15:59:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA10390 for hackers-outgoing; Fri, 10 Jan 1997 15:59:05 -0800 (PST) Received: from mail.inforamp.net (Mail.InfoRamp.Net [204.191.136.66]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA10382 for ; Fri, 10 Jan 1997 15:59:01 -0800 (PST) Received: from FRANK.A (ts33-03.tor.iSTAR.ca [204.191.140.63]) by mail.inforamp.net (8.7.3/8.7) with SMTP id SAA01347 for ; Fri, 10 Jan 1997 18:52:48 -0500 (EST) Date: Fri, 10 Jan 1997 18:52:48 -0500 (EST) Message-Id: <199701102352.SAA01347@mail.inforamp.net> X-Sender: avenger@inforamp.net X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: hackers@freebsd.org From: "Frank.A" Subject: Modem Setup Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am wondering how to go about seting up my modem to dial up and make a PPP connection with an ISP. I have a USR 33.6 Internal and at boot up it picks up on com 2 (sio1) I have been trying to use minicom to dial up but when I type minicom I get the message can not open /dev/modem. file missing I do not know exactly what to do. Can anyone help me setup my modem to make a PPP connection to an ISP. Cheers, Frank.A From owner-freebsd-hackers Fri Jan 10 18:05:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA18593 for hackers-outgoing; Fri, 10 Jan 1997 18:05:29 -0800 (PST) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA18583 for ; Fri, 10 Jan 1997 18:05:24 -0800 (PST) Received: (from uucp@localhost) by frmug.org (8.8.2/8.8.2/frmug-1.3) with UUCP id DAA13002 for hackers@FreeBSD.org; Sat, 11 Jan 1997 03:05:18 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by xp11.frmug.org (8.8.4/8.7.3/xp11-uucp-1.1) with ESMTP id DAA29018 for ; Sat, 11 Jan 1997 03:02:10 +0100 (CET) Message-Id: <199701110202.DAA29018@xp11.frmug.org> To: hackers@FreeBSD.org Subject: number of lines in a file, given its size Date: Sat, 11 Jan 1997 03:02:10 +0100 From: "Philippe Charnier" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hello, In line 115 in /usr/src/lib/libc/gen/getusershell.c: shells = calloc((unsigned)statb.st_size / 3, sizeof (char *)); ^^^^^^^^^^^^^^^^^ Isn't this a suspicious approximation of the number of lines in /etc/shells (just put `/' in it for example of an invalid entry). ------ ------ Philippe Charnier charnier@lirmm.fr (smtp) charnier@xp11.frmug.org (uucp) ``a PC not running FreeBSD is like a venusian with no tentacles'' ------------------------------------------------------------------------ From owner-freebsd-hackers Fri Jan 10 18:05:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA18626 for hackers-outgoing; Fri, 10 Jan 1997 18:05:47 -0800 (PST) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA18621 for ; Fri, 10 Jan 1997 18:05:43 -0800 (PST) Received: (from uucp@localhost) by frmug.org (8.8.2/8.8.2/frmug-1.3) with UUCP id DAA13007 for hackers@FreeBSD.org; Sat, 11 Jan 1997 03:05:40 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by xp11.frmug.org (8.8.4/8.7.3/xp11-uucp-1.1) with ESMTP id CAA28453 for ; Sat, 11 Jan 1997 02:42:12 +0100 (CET) Message-Id: <199701110142.CAA28453@xp11.frmug.org> To: hackers@FreeBSD.org Subject: unused variable in su Date: Sat, 11 Jan 1997 02:42:11 +0100 From: "Philippe Charnier" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hello, In /usr/src/usr.bin/su/su.c, I get: line 101: char shellbuf[MAXPATHLEN]; line 171: shell = strcpy(shellbuf, pwd->pw_shell); Shellbuf is not referenced elsewhere, is there any reason not to remove shellbuf (and adjust line 171), or is there a side effect I don't see? ------ ------ Philippe Charnier charnier@lirmm.fr (smtp) charnier@xp11.frmug.org (uucp) ``a PC not running FreeBSD is like a venusian with no tentacles'' ------------------------------------------------------------------------ From owner-freebsd-hackers Fri Jan 10 18:53:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA21606 for hackers-outgoing; Fri, 10 Jan 1997 18:53:04 -0800 (PST) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA21601; Fri, 10 Jan 1997 18:53:00 -0800 (PST) Received: (from jmacd@localhost) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) id SAA08942; Fri, 10 Jan 1997 18:52:53 -0800 (PST) Date: Fri, 10 Jan 1997 18:52:53 -0800 (PST) From: Josh MacDonald Message-Id: <199701110252.SAA08942@paris.CS.Berkeley.EDU> To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: recent texinfo commits Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The changes to the source tree involving new installation mechanism and the new texinfo version are finished. Over the next hour or so I'll be fixing the various places in the source tree where stuff won't compile because of the new rules. I don't know how to make things automatically bootstrap themselves. You'll need to have gnu/usr.bin/texinfo/install-info installed before make install will work. -josh From owner-freebsd-hackers Fri Jan 10 19:08:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA22408 for hackers-outgoing; Fri, 10 Jan 1997 19:08:09 -0800 (PST) Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA22403 for ; Fri, 10 Jan 1997 19:08:03 -0800 (PST) Received: (from davidn@localhost) by labs.usn.blaze.net.au (8.8.4/8.8.4) id OAA03332; Sat, 11 Jan 1997 14:07:37 +1100 (EST) Message-ID: Date: Sat, 11 Jan 1997 14:07:36 +1100 From: davidn@unique.usn.blaze.net.au (David Nugent) To: charnier@xp11.frmug.org ("Philippe Charnier") Cc: hackers@FreeBSD.org Subject: Re: unused variable in su References: <199701110142.CAA28453@xp11.frmug.org> X-Mailer: Mutt 0.56 Mime-Version: 1.0 In-Reply-To: <199701110142.CAA28453@xp11.frmug.org>; from "Philippe Charnier" on Jan 11, 1997 02:42:11 +0100 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk "Philippe Charnier" writes: > In /usr/src/usr.bin/su/su.c, I get: > line 101: char shellbuf[MAXPATHLEN]; > line 171: shell = strcpy(shellbuf, pwd->pw_shell); > > Shellbuf is not referenced elsewhere, is there any reason not to > remove shellbuf (and adjust line 171), or is there a side effect I don't > see? Yes, there certainly is a side-effect. You can't leave it pointing to pwd->pw_dir, since that points to an internal libc buffer which may be overwritten by a call to any getpw*() function. Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-hackers Fri Jan 10 19:43:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA24369 for hackers-outgoing; Fri, 10 Jan 1997 19:43:46 -0800 (PST) Received: from mailgate ([202.159.65.166]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id TAA24338; Fri, 10 Jan 1997 19:43:25 -0800 (PST) Received: from bandung.wasantara.net.id (bandung.wasantara.net.id [202.159.69.35]) by mailgate (8.6.11/8.6.9) with ESMTP id KAA00164; Sat, 11 Jan 1997 10:28:57 +0700 Date: Sat, 11 Jan 1997 10:28:57 +0700 Received: from BANDUNG/SpoolDir by bandung.wasantara.net.id (Mercury 1.21); 11 Jan 97 11:35:15 GMT+0700 Received: from SpoolDir by BANDUNG (Mercury 1.21); 11 Jan 97 11:34:34 GMT+0700 Received: from shuttle.wasantara.net.id by bandung.wasantara.net.id (Mercury 1.21); 11 Jan 97 11:34:25 GMT+0700 X-Sender: eka@werty.wasantara.net.id (Unverified) X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-hackers@freebsd.org From: Eka Kelana Subject: bug in setsockopt()... ? Cc: freebsd-questions@freebsd.org Message-ID: <1CA927E5D71@bandung.wasantara.net.id> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I wonder if there is anyone here ever experience a bug in setsockopt(). I did this when I found the bug: ...skipped if ((fd = socket(AF_INET, SOCK_STREAM, 0)) < 0) err("socket"); mes("socket"); #if defined(SO_SNDBUF) || defined(SO_RCVBUF) if (sockbufsize) { if (trans) { if (setsockopt(fd, SOL_SOCKET, SO_SNDBUF, (char*) &sockbufsize,sizeof(sockbufsize)) < 0) err("setsockopt: sndbuf"); mes("sndbuf"); } else { if (setsockopt(fd, SOL_SOCKET, SO_RCVBUF, &sockbufsize, sizeof sockbufsize) < 0) err("setsockopt: rcvbuf"); mes("rcvbuf"); } } #endif ...skipped optlen = sizeof(sockbufsize); if (getsockopt(fd, SOL_SOCKET, SO_SNDBUF, (char *) &sockbufsize, &optlen) < 0) err("getsockopt"); printf("socket send buff before connect: %d\n", sockbufsize); if(connect(fd, &sinhim, sizeof(sinhim) ) < 0) err("connect"); mes("connect"); optlen = sizeof(sockbufsize); if (getsockopt(fd, SOL_SOCKET, SO_SNDBUF, (char *) &sockbufsize, &optlen) < 0) err("getsockopt"); printf("socket buff size after connect: %d\n", sockbufsize); The two getsockopt() above produced different value of socket buffer size. When I didn't try to change the socket buffer size and used the default value instead, the first getsockopt() would produce 16384 bytes. I think this is the correct value, since FreeBSD set the default value for socket buffer size to 16384 bytes. But the second getsockopt() would produce 17280 bytes. I couldn't find any reasonable explanation of this behaviour, but I think it is a bug in FreeBSD networking code. I even couldn't set the socket buffer size to another value. It still shows 17280 bytes. And another crosscheck using tcpdump still shows a receive window of 17280 which means that the receive buffer is set to 17280. I need a reasonable explanation around this problem. Is there anyone here who is able to give such explanation to me ? -Eka Kelana- STTTelkom From owner-freebsd-hackers Fri Jan 10 19:49:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA24618 for hackers-outgoing; Fri, 10 Jan 1997 19:49:41 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA24613 for ; Fri, 10 Jan 1997 19:49:39 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.4/8.8.4) with SMTP id WAA14912; Fri, 10 Jan 1997 22:49:36 -0500 (EST) Date: Fri, 10 Jan 1997 22:49:36 -0500 (EST) From: John Fieber To: Fred Gilham cc: freebsd-hackers@freebsd.org Subject: Re: A cool xterm? In-Reply-To: <199701101606.IAA03133@impulse.csl.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 10 Jan 1997, Fred Gilham wrote: > I'm wondering what this means. Is it that people don't like the fact > that the scrollbar works the way it does? Or is it that they don't > like the way it looks? What exactly is wrong with the scrollbar? Its ugly, but it does give you a reasonably accurate representation of the view and the total size of the scrollable area. Unfortunately, everything else about it is a complete user interface disaster. It starts off with a *complete* disconnect between manipulation affordances and actual manipulation methods and goes downhill from there. The fact that to this day, people re-implement the same behavior in new products completely baffles me. I've been using the things for years and I still fumble and curse when I have to use them. -john From owner-freebsd-hackers Fri Jan 10 20:56:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA27120 for hackers-outgoing; Fri, 10 Jan 1997 20:56:31 -0800 (PST) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA27115 for ; Fri, 10 Jan 1997 20:56:28 -0800 (PST) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.3/8.7.3) with SMTP id XAA01378; Fri, 10 Jan 1997 23:54:31 -0500 (EST) Message-Id: <199701110454.XAA01378@whizzo.transsys.com> X-Mailer: exmh version 2.0alpha 12/3/96 To: Bakul Shah cc: Terry Lambert , gilham@csl.sri.com (Fred Gilham), freebsd-hackers@freebsd.org From: "Louis A. Mamakos" Subject: Re: A cool xterm? References: <199701102211.RAA13433@chai.plexuscom.com> In-reply-to: Your message of "Fri, 10 Jan 1997 17:11:57 EST." <199701102211.RAA13433@chai.plexuscom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Jan 1997 23:54:31 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > In the scrollbar used in `ups' (the debugger), the distance you drag > the cursor determines the *velocity* of scrolling: move the cursor > *anywhere* in the scrollbar window; press the left button and drag > the cursor up or down. The farther you drag it, the faster the > window scrolls. When you get close to the target, you can drag back > towards the original position and scrolling can be slowed down to a > crawl. If you overshoot, move past the original position to scroll > in the opposite direction. This is much like a single dial for fast > forward/reverse button on some VCRs. Very handy. But.. The way the NeXTSTEP scrollbars work, this isn't necessary. The size of the "knob" in the scroll bar is proportional to the total size of scrollable region. If you want to be in a particular part of the file, you simply grab the knob and drag it to where you want it to be. You can move up/down a line by pressing the buttons, or up/down a page by clicking the select (left) button in the scroll bar above or below the button. There are other modifications which can be done by holding the ALT key down, but few applications use them. Personally, I find the mouse button usage incredibly hard to use with the Athena widgets compared to the much simpler implementation that the NeXTSTEP ScrollView gives you. Heck, for the years I used NeXTSTEP every day, I never missed not having to screw around with an .Xdefaults file. I don't need that many ways to configure a UI with bad taste :-) Seriously, one of the thinks I loved about the Stuart terminal emulator on NeXTSTEP is that the scrollback buffer was essentially infinite (or could be if you wanted). It "did the right thing" when the screen was cleared and other cursor positioning stuff happened. Funny, I can't exactly explain what "the right thing" is now, all I know is that xterm and rxvt don't manage to do it, sigh. We could learn a lot from the UI design those guys came up with. My two-bit deep monochrome display on my NeXT pizza box machine still manages to look better than the technocolor, 24 bit deep X11 display.. Sorry for the digression into window system UI design.. louie > A similar scheme for selecting text would be nice. > > > I think the riginal complaint was that cleared screens did not get added > > as complete units to the scrollback buffer of xterm. > > Yeah, this would be better but can be somewhat confusing. Perhaps > a thin horizontal line should separate screens cleared this way. > > Also, there should be a way to dump lines to a file (on command) as > well as increase/decrease line buffer size. From owner-freebsd-hackers Fri Jan 10 21:02:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA27253 for hackers-outgoing; Fri, 10 Jan 1997 21:02:46 -0800 (PST) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA27246; Fri, 10 Jan 1997 21:02:38 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.2/8.6.12) with SMTP id UAA00257; Fri, 10 Jan 1997 20:56:12 -0800 (PST) Date: Fri, 10 Jan 1997 20:56:11 -0800 (PST) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Stefan Esser cc: hackers@freebsd.org Subject: Re: ncr probe FAILS on 2.2-BETA_A! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 10 Jan 1997, Stefan Esser wrote: > > > Perhaps you want to try booting with PCI options (write > > > buffers, PCI burst mode) disabled. > > > > I can try that. There is one thing I did change and that was I upgraded > > the CPU from a 90 to a 133, but the motherboard only does 100MHz, so it's > > running underclocked at the moment. > > Hmmm, that might cause problems, anyway. > Could you check with the old CPU, whether > the problem still exists ? Tried it with the burst and post mode disabled and the P90, no dice. > > > Please try the applied patch. If it doesn't work, then > > > send boot -v messages. If you have access to the CVS > > > tree, you may want to use the driver from 2.2-ALPHA. I > > > can send you a context diff, if you prefer that ... > > > > Unfortunately, this is on the boot.flp and I'm not at all set up to > > rebuild the system....:( > > Ok, I understand this. But send verbose boot > messages from FreeBSD-ALPHA, at least. I need > to know your system configuration, or I won't > know, whether any part that I modified between > ALPHA and BETA might be the culprit ... boot -v output for -ALPHA follows. This SiS board's bridge chips probe up a whole bunch so it doesn't show the whole boot sequence in the syslog, I'll paste on the basics above it. Let me know if you need anything else. Jan 10 00:25:42 gdi /kernel.GUS: FreeBSD 2.2-ALPHA #0: Wed Dec 11 14:08:40 PST 1996 Jan 10 00:25:43 gdi /kernel.GUS: dwhite@gdi.uoregon.edu:/usr/src/sys/compile/GDI Jan 10 00:25:43 gdi /kernel.GUS: Calibrating clock(s) relative to mc146818A clock ... i586 clock: 100006457 Hz, i8254 clock: 1193655 Hz Jan 10 00:25:43 gdi /kernel.GUS: CPU: Pentium (99.97-MHz 586-class CPU) Jan 10 00:25:43 gdi /kernel.GUS: Origin = "GenuineIntel" Id = 0x52c Stepping=12 Jan 10 00:25:43 gdi /kernel.GUS: Features=0x1bf Jan 10 00:25:43 gdi /kernel.GUS: real memory = 33554432 (32768K bytes) Jan 10 00:25:43 gdi /kernel.GUS: avail memory = 30416896 (29704K bytes) Jan 10 00:25:43 gdi /kernel.GUS: Probing for devices on PCI bus 0: Jan 10 00:25:43 gdi /kernel.GUS: chip0 rev 57 on pci0:0:0 Jan 10 00:25:43 gdi /kernel.GUS: chip1 rev 57 int a irq 60 on pci0:0:1 Jan 10 00:25:43 gdi /kernel.GUS: chip2 rev 57 int b irq 60 on pci0:0:2 Jan 10 00:25:43 gdi /kernel.GUS: chip3 rev 57 int c irq 60 on pci0:0:3 - visual boot info starts here - Jan 10 20:14:14 gdi /kernel.GUS: Jan 10 20:14:14 gdi /kernel.GUS: mapreg[18] type=0 addr=80000310 size=7ffffcf0. Jan 10 20:14:14 gdi /kernel.GUS: mapreg[1c] type=4 addr=80000310 size=7ffffcf0. Jan 10 20:14:14 gdi /kernel.GUS: mapreg[20] type=0 addr=80000320 size=7ffffce0. Jan 10 20:14:14 gdi /kernel.GUS: mapreg[24] type=4 addr=80000320 size=7ffffce0. Jan 10 20:14:14 gdi /kernel.GUS: chip4 rev 57 int d irq 60 on pci0:0:4 Jan 10 20:14:14 gdi /kernel.GUS: mapreg[10] type=0 addr=80000410 size=7ffffbf0. Jan 10 20:14:14 gdi /kernel.GUS: mapreg[14] type=4 addr=80000410 size=7ffffbf0. Jan 10 20:14:15 gdi /kernel.GUS: mapreg[18] type=0 addr=80000410 size=7ffffbf0. Jan 10 20:14:15 gdi /kernel.GUS: mapreg[1c] type=4 addr=80000410 size=7ffffbf0. Jan 10 20:14:15 gdi /kernel.GUS: mapreg[20] type=0 addr=80000420 size=7ffffbe0. Jan 10 20:14:15 gdi /kernel.GUS: mapreg[24] type=4 addr=80000420 size=7ffffbe0. Jan 10 20:14:15 gdi /kernel.GUS: chip5 rev 57 int e irq 60 on pci0:0:5 Jan 10 20:14:15 gdi /kernel.GUS: mapreg[10] type=0 addr=80000510 size=7ffffaf0. Jan 10 20:14:15 gdi /kernel.GUS: mapreg[14] type=4 addr=80000510 size=7ffffaf0. Jan 10 20:14:15 gdi /kernel.GUS: mapreg[18] type=0 addr=80000510 size=7ffffaf0. Jan 10 20:14:15 gdi /kernel.GUS: mapreg[1c] type=4 addr=80000510 size=7ffffaf0. Jan 10 20:14:15 gdi /kernel.GUS: mapreg[20] type=0 addr=80000520 size=7ffffae0. Jan 10 20:14:15 gdi /kernel.GUS: mapreg[24] type=4 addr=80000520 size=7ffffae0. Jan 10 20:14:15 gdi /kernel.GUS: chip6 rev 57 int f irq 60 on pci0:0:6 Jan 10 20:14:15 gdi /kernel.GUS: mapreg[10] type=0 addr=80000610 size=7ffff9f0. Jan 10 20:14:15 gdi /kernel.GUS: mapreg[14] type=4 addr=80000610 size=7ffff9f0. Jan 10 20:14:15 gdi /kernel.GUS: mapreg[18] type=0 addr=80000610 size=7ffff9f0. Jan 10 20:14:15 gdi /kernel.GUS: mapreg[1c] type=4 addr=80000610 size=7ffff9f0. Jan 10 20:14:15 gdi /kernel.GUS: mapreg[20] type=0 addr=80000620 size=7ffff9e0. Jan 10 20:14:15 gdi /kernel.GUS: mapreg[24] type=4 addr=80000620 size=7ffff9e0. Jan 10 20:14:15 gdi /kernel.GUS: chip7 rev 57 int g irq 60 on pci0:0:7 Jan 10 20:14:15 gdi /kernel.GUS: mapreg[10] type=0 addr=80000710 size=7ffff8f0. Jan 10 20:14:15 gdi /kernel.GUS: mapreg[14] type=4 addr=80000710 size=7ffff8f0. Jan 10 20:14:15 gdi /kernel.GUS: mapreg[18] type=0 addr=80000710 size=7ffff8f0. Jan 10 20:14:15 gdi /kernel.GUS: mapreg[1c] type=4 addr=80000710 size=7ffff8f0. Jan 10 20:14:16 gdi /kernel.GUS: mapreg[20] type=0 addr=80000720 size=7ffff8e0. Jan 10 20:14:16 gdi /kernel.GUS: mapreg[24] type=4 addr=80000720 size=7ffff8e0. Jan 10 20:14:16 gdi /kernel.GUS: chip8 rev 0 on pci0:1 Jan 10 20:14:16 gdi /kernel.GUS: pci0:12: CMD, device=0x0640, class=storage (ide) int a irq 14 [no driver assigned] Jan 10 20:14:16 gdi /kernel.GUS: ncr0 rev 3 int a irq 11 on pci0:13 Jan 10 20:14:16 gdi /kernel.GUS: mapreg[10] type=1 addr=00004000 size=0100. Jan 10 20:14:16 gdi /kernel.GUS: mapreg[14] type=0 addr=81000000 size=0100. Jan 10 20:14:16 gdi /kernel.GUS: reg20: virtual=0xf5ff7000 physical=0x81000000 size=0x100 Jan 10 20:14:16 gdi /kernel.GUS: ncr0: restart (scsi reset). Jan 10 20:14:16 gdi /kernel.GUS: ncr0 scanning for targets 0..6 (V2 pl23 95/09/07) Jan 10 20:14:16 gdi /kernel.GUS: ncr0 waiting for scsi devices to settle Jan 10 20:14:16 gdi /kernel.GUS: (ncr0:3:0): "PLEXTOR CD-ROM PX-4XCE 1.00" type 5 removable SCSI 2 Jan 10 20:14:16 gdi /kernel.GUS: cd0(ncr0:3:0): CD-ROM Jan 10 20:14:16 gdi /kernel.GUS: cd0(ncr0:3:0): FAST SCSI-2 175ns (6 Mb/sec) offset 8. Jan 10 20:14:16 gdi /kernel.GUS: cd present [268501 x 2048 byte records] Jan 10 20:14:16 gdi /kernel.GUS: (ncr0:4:0): "SONY CD-ROM CDU-76S 1.1c" type 5 removable SCSI 2 Jan 10 20:14:16 gdi /kernel.GUS: cd1(ncr0:4:0): CD-ROM Jan 10 20:14:16 gdi /kernel.GUS: cd1(ncr0:4:0): 200ns (5 Mb/sec) offset 8. Jan 10 20:14:16 gdi /kernel.GUS: Jan 10 20:14:16 gdi /kernel.GUS: cd1(ncr0:4:0): UNIT ATTENTION asc:28,0 Jan 10 20:14:16 gdi /kernel.GUS: cd1(ncr0:4:0): Not ready to ready transition, medium may have changed Jan 10 20:14:16 gdi /kernel.GUS: cd present [400000 x 2048 byte records] Jan 10 20:14:17 gdi /kernel.GUS: vga0 rev 3 on pci0:15 Jan 10 20:14:17 gdi /kernel.GUS: mapreg[10] type=0 addr=80000000 size=1000000. Jan 10 20:14:17 gdi /kernel.GUS: pci0: uses 16733440 bytes of memory from 80000000 upto ffffffff. Jan 10 20:14:17 gdi /kernel.GUS: pci0: uses 256 bytes of I/O space from 4000 upto 40ff. Jan 10 20:14:17 gdi /kernel.GUS: Probing for devices on the ISA bus: Jan 10 20:14:17 gdi /kernel.GUS: sc0 at 0x60-0x6f irq 1 on motherboard Jan 10 20:14:17 gdi /kernel.GUS: sc0: VGA color <16 virtual consoles, flags=0x0> Jan 10 20:14:17 gdi /kernel.GUS: ed0 at 0x300-0x31f irq 10 on isa Jan 10 20:14:17 gdi /kernel.GUS: ed0: address 00:c0:d1:08:08:17, type NE2000 (16 bit) Jan 10 20:14:17 gdi /kernel.GUS: bpf: ed0 attached Jan 10 20:14:17 gdi /kernel.GUS: sio0 at 0x3f8-0x3ff irq 4 on isa Jan 10 20:14:17 gdi /kernel.GUS: sio0: type 16550A Jan 10 20:14:17 gdi /kernel.GUS: sio1 at 0x2f8-0x2ff irq 3 on isa Jan 10 20:14:17 gdi /kernel.GUS: sio1: type 16550A Jan 10 20:14:17 gdi /kernel.GUS: lpt1 at 0x278-0x27f on isa Jan 10 20:14:17 gdi /kernel.GUS: qcam0 at 0x378 irq 7 flags 0x1 on isa Jan 10 20:14:17 gdi /kernel.GUS: qcam0: unidirectional parallel port Jan 10 20:14:17 gdi /kernel.GUS: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Jan 10 20:14:17 gdi /kernel.GUS: fdc0: NEC 72065B Jan 10 20:14:17 gdi /kernel.GUS: fd0: 1.44MB 3.5in Jan 10 20:14:17 gdi /kernel.GUS: wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa Jan 10 20:14:17 gdi /kernel.GUS: wdc0: unit 0 (wd0): , multi-block-16 Jan 10 20:14:18 gdi /kernel.GUS: wd0: 1033MB (2116800 sectors), 2100 cyls, 16 heads, 63 S/T, 512 B/S Jan 10 20:14:18 gdi /kernel.GUS: wdc0: unit 1 (wd1): , multi-block-8 Jan 10 20:14:18 gdi /kernel.GUS: wd1: 514MB (1054368 sectors), 1046 cyls, 16 heads, 63 S/T, 512 B/S Jan 10 20:14:18 gdi /kernel.GUS: wdc1 not found at 0x170 Jan 10 20:14:18 gdi /kernel.GUS: npx0 on motherboard Jan 10 20:14:18 gdi /kernel.GUS: npx0: INT 16 interface Jan 10 20:14:18 gdi /kernel.GUS: Checking for GUS Plug-n-Play ... Jan 10 20:14:18 gdi /kernel.GUS: Board Vendor ID: GRV0001 Board Serial Number: ffffffff Jan 10 20:14:18 gdi /kernel.GUS: gus0 at 0x240 irq 12 drq 1 flags 0x3 on isa Jan 10 20:14:18 gdi /kernel.GUS: GUS PNP (CS4231)> at 0x34c dma 3,1 Jan 10 20:14:18 gdi /kernel.GUS: Gravis PNP (1024k)> at 0x240 irq 12 dma 1,3 Jan 10 20:14:18 gdi /kernel.GUS: Jan 10 20:14:18 gdi /kernel.GUS: imasks: bio c0004840, tty c003049a, net c003049a Jan 10 20:14:18 gdi /kernel.GUS: Device configuration finished. Jan 10 20:14:18 gdi /kernel.GUS: Considering FFS root f/s. Jan 10 20:14:18 gdi /kernel.GUS: changing root device to wd0a Jan 10 20:14:18 gdi /kernel.GUS: configure() finished. Jan 10 20:14:18 gdi /kernel.GUS: bpf: tun0 attached Jan 10 20:14:19 gdi /kernel.GUS: bpf: sl0 attached Jan 10 20:14:19 gdi /kernel.GUS: bpf: lo0 attached Jan 10 20:14:19 gdi /kernel.GUS: wd0s1: type 0xa5, start 63, end = 2108735, size 2108673 : OK Jan 10 20:14:19 gdi /kernel.GUS: wd0s3: type 0xa, start 2108736, end = 2112767, size 4032 : OK Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-hackers Fri Jan 10 21:47:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA00449 for hackers-outgoing; Fri, 10 Jan 1997 21:47:48 -0800 (PST) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA00443; Fri, 10 Jan 1997 21:47:45 -0800 (PST) Received: (from jmacd@localhost) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) id VAA09224; Fri, 10 Jan 1997 21:47:41 -0800 (PST) Date: Fri, 10 Jan 1997 21:47:41 -0800 (PST) From: Josh MacDonald Message-Id: <199701110547.VAA09224@paris.CS.Berkeley.EDU> To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: texinfo commits done Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk To my knowledge, everything should build properly now. Let me know if something breaks. -josh From owner-freebsd-hackers Fri Jan 10 22:15:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA01648 for hackers-outgoing; Fri, 10 Jan 1997 22:15:56 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA01641 for ; Fri, 10 Jan 1997 22:15:53 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id BAA02660; Sat, 11 Jan 1997 01:15:52 -0500 (EST) Date: Sat, 11 Jan 1997 01:15:52 -0500 (EST) From: Charles Henrich Message-Id: <199701110615.BAA02660@crh.cl.msu.edu> To: louie@TransSys.COM, freebsd-hackers@freebsd.org Subject: Re: A cool xterm? Newsgroups: lists.freebsd.hackers References: <5b79dl$2b8e@msunews.cl.msu.edu> X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In lists.freebsd.hackers you write: >Seriously, one of the thinks I loved about the Stuart terminal emulator >on NeXTSTEP is that the scrollback buffer was essentially infinite (or >could be if you wanted). It "did the right thing" when the screen was >cleared and other cursor positioning stuff happened. Funny, I can't >exactly explain what "the right thing" is now, all I know is that xterm >and rxvt don't manage to do it, sigh. God knows I would give alot for the NeXT terminal emulator, I know people who still use nextstep just for that reason! -Crh -- Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Fri Jan 10 22:16:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA01711 for hackers-outgoing; Fri, 10 Jan 1997 22:16:15 -0800 (PST) Received: from atlantis.nconnect.net (root@atlantis.nconnect.net [206.54.227.6]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA01706; Fri, 10 Jan 1997 22:16:13 -0800 (PST) Received: from arabian.astrolab.org (dial234.nconnect.net [206.54.227.234]) by atlantis.nconnect.net (8.8.4/8.7.3) with SMTP id AAA27849; Sat, 11 Jan 1997 00:11:59 -0600 (CST) Message-ID: <32D72FE5.446B9B3D@nconnect.net> Date: Sat, 11 Jan 1997 00:15:01 -0600 From: Randy DuCharme X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-SMP i386) MIME-Version: 1.0 To: Josh MacDonald CC: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: texinfo commits done References: <199701110547.VAA09224@paris.CS.Berkeley.EDU> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Josh MacDonald wrote: > > To my knowledge, everything should build properly now. Let me know > if something breaks. > > -josh Mine breaks .... gzip -c as-all.info > as-all.info.gz install -c -s -o bin -g bin -m 555 as /usr/bin ===> doc install-info --defsection="Programming & development tools." -- defentry="* AS: (as-all). The GNU Assembler manual." as-all.info //usr/share/info/ ins nfo: not found *** code 127 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. From owner-freebsd-hackers Fri Jan 10 22:21:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA02067 for hackers-outgoing; Fri, 10 Jan 1997 22:21:47 -0800 (PST) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA02062; Fri, 10 Jan 1997 22:21:45 -0800 (PST) Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) with ESMTP id WAA09412; Fri, 10 Jan 1997 22:21:40 -0800 (PST) From: Josh MacDonald Message-Id: <199701110621.WAA09412@paris.CS.Berkeley.EDU> To: Randy DuCharme cc: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: texinfo commits done In-reply-to: Your message of "Sat, 11 Jan 1997 00:15:01 CST." <32D72FE5.446B9B3D@nconnect.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9405.852963694.1@paris.CS.Berkeley.EDU> Date: Fri, 10 Jan 1997 22:21:35 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In order, you need to: (cd /usr/src/share/info; make beforeinstall) (cd /usr/src/share/mk; make install) (cd /usr/src/gnu/usr.bin/texinfo; make all install) And then you should be able to make install from any of the documentation directories I just modified. I said at least most of this in previous mail. -josh > Josh MacDonald wrote: > > > > To my knowledge, everything should build properly now. Let me know > > if something breaks. > > > > -josh > > > Mine breaks .... > > gzip -c as-all.info > as-all.info.gz > install -c -s -o bin -g bin -m 555 as /usr/bin > ===> doc > install-info --defsection="Programming & development tools." -- > defentry="* AS: > (as-all). The GNU Assembler manual." as-all.info > //usr/share/info/ > ins nfo: not found > *** code 127 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > From owner-freebsd-hackers Fri Jan 10 23:31:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA04702 for hackers-outgoing; Fri, 10 Jan 1997 23:31:56 -0800 (PST) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA04697 for ; Fri, 10 Jan 1997 23:31:53 -0800 (PST) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.3/CET-v2.1) with SMTP id HAA12712; Sat, 11 Jan 1997 07:31:44 GMT Date: Sat, 11 Jan 1997 16:31:44 +0900 (JST) From: Michael Hancock To: Leonard Chua cc: freebsd-hackers@freebsd.org Subject: Re: pppd and the login option In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 10 Jan 1997, Leonard Chua wrote: > PS> why do I want to use the system database? Simple - I don't like > having a unencrypted password file anywhere (even if it's supposedly > group and world unreadable). It's a trade off with having a clear text file with passwords or having clear text go over the wire when considering CHAP vs. PAP w/ the system database. Mike Hancock From owner-freebsd-hackers Sat Jan 11 00:26:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA06025 for hackers-outgoing; Sat, 11 Jan 1997 00:26:08 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA06020 for ; Sat, 11 Jan 1997 00:26:06 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id SAA07725; Sat, 11 Jan 1997 18:54:08 +1030 (CST) From: Michael Smith Message-Id: <199701110824.SAA07725@genesis.atrad.adelaide.edu.au> Subject: Re: mount -o async on a news servre In-Reply-To: from Jonathan Lemon at "Jan 10, 97 04:06:36 pm" To: jlemon@americantv.com (Jonathan Lemon) Date: Sat, 11 Jan 1997 18:54:07 +1030 (CST) Cc: terry@lambert.org, scrappy@hub.org, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jonathan Lemon stands accused of saying: > > Another possibility is illustrated in a recent ASPLOS paper on robustness > in the face of operating system crashes. IIRC, their system (Petal?) has > the entire DRAM on a battery backup, and after a crash/reboot, a diagnostic > utility goes through memory and writes out any pending data buffers. FreeBSD for the NCR Tower! Yes! Yes! An excellent trick to play on the junior sysadmin on one of these systems; walk up to it, pull the wall plug, let it spin down and plug it back in. An excellent trick for the senior sysadmin to play on you; "oh, by the way, I borrowed that battery out of that unit for my motorbike...". > Jonathan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Jan 11 00:34:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA06267 for hackers-outgoing; Sat, 11 Jan 1997 00:34:51 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA06262 for ; Sat, 11 Jan 1997 00:34:49 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id TAA07745; Sat, 11 Jan 1997 19:04:37 +1030 (CST) From: Michael Smith Message-Id: <199701110834.TAA07745@genesis.atrad.adelaide.edu.au> Subject: Re: unused variable in su In-Reply-To: <199701110142.CAA28453@xp11.frmug.org> from Philippe Charnier at "Jan 11, 97 02:42:11 am" To: charnier@xp11.frmug.org (Philippe Charnier) Date: Sat, 11 Jan 1997 19:04:36 +1030 (CST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Philippe Charnier stands accused of saying: > Hello, > > In /usr/src/usr.bin/su/su.c, I get: > line 101: char shellbuf[MAXPATHLEN]; > line 171: shell = strcpy(shellbuf, pwd->pw_shell); > > Shellbuf is not referenced elsewhere, is there any reason not to > remove shellbuf (and adjust line 171), or is there a side effect I don't > see? pwd is recycled later, and shell is potentially reset later, so this is the 'correct' way to do it. Don't change it. > Philippe Charnier charnier@lirmm.fr (smtp) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Jan 11 00:43:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA06458 for hackers-outgoing; Sat, 11 Jan 1997 00:43:50 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA06453; Sat, 11 Jan 1997 00:43:45 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id TAA07768; Sat, 11 Jan 1997 19:13:39 +1030 (CST) From: Michael Smith Message-Id: <199701110843.TAA07768@genesis.atrad.adelaide.edu.au> Subject: Re: recent texinfo commits In-Reply-To: <199701110252.SAA08942@paris.CS.Berkeley.EDU> from Josh MacDonald at "Jan 10, 97 06:52:53 pm" To: jmacd@CS.Berkeley.EDU (Josh MacDonald) Date: Sat, 11 Jan 1997 19:13:38 +1030 (CST) Cc: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Josh MacDonald stands accused of saying: > > The changes to the source tree involving new installation mechanism > and the new texinfo version are finished. Over the next hour or so > I'll be fixing the various places in the source tree where stuff won't > compile because of the new rules. I don't know how to make things > automatically bootstrap themselves. You'll need to have > gnu/usr.bin/texinfo/install-info installed before make install will work. Go Josh! Note that if you have tools that need to be built before the tree itself can build, have a look at the 'bootstrap' target in the toplevel makefile, specifically the 'build-tools' target right at the end. > -josh -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Jan 11 02:04:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA08776 for hackers-outgoing; Sat, 11 Jan 1997 02:04:00 -0800 (PST) Received: from earth.infinetconsulting.com (earth.infinetconsulting.com [207.23.43.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA08766 for ; Sat, 11 Jan 1997 02:03:54 -0800 (PST) Received: (from lenc@localhost) by earth.infinetconsulting.com (8.6.12/8.6.12) id CAA29394; Sat, 11 Jan 1997 02:17:23 -0800 Date: Sat, 11 Jan 1997 02:17:22 -0800 (PST) From: Leonard Chua To: Michael Hancock cc: freebsd-hackers@freebsd.org Subject: Re: pppd and the login option In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 11 Jan 1997, Michael Hancock wrote: > It's a trade off with having a clear text file with passwords or having > clear text go over the wire when considering CHAP vs. PAP w/ the system > database. > True. My assumption, however, is that the PAP clear text goes over the TCP/IP between the dialup client, via the modem, to my dialup server. There should be no reason for such packets to ever enter the rest of the internet. A TCP/IP guru might confirm/deny this. Len. From owner-freebsd-hackers Sat Jan 11 02:08:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA08926 for hackers-outgoing; Sat, 11 Jan 1997 02:08:22 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA08921; Sat, 11 Jan 1997 02:08:18 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id CAA10933; Sat, 11 Jan 1997 02:08:11 -0800 (PST) To: Josh MacDonald cc: Randy DuCharme , freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: texinfo commits done In-reply-to: Your message of "Fri, 10 Jan 1997 22:21:35 PST." <199701110621.WAA09412@paris.CS.Berkeley.EDU> Date: Sat, 11 Jan 1997 02:08:11 -0800 Message-ID: <10929.852977291@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Add dependencies to the lib-tools or build-tools targets as necessary, please. See how the world rule in /usr/src/Makefile bootstraps itself and see if you can make these texinfo changes DTRT. Thanks! Jordan > In order, you need to: > > (cd /usr/src/share/info; make beforeinstall) > (cd /usr/src/share/mk; make install) > (cd /usr/src/gnu/usr.bin/texinfo; make all install) > > And then you should be able to make install from any of the > documentation directories I just modified. I said at least > most of this in previous mail. > > -josh > > > Josh MacDonald wrote: > > > > > > To my knowledge, everything should build properly now. Let me know > > > if something breaks. > > > > > > -josh > > > > > > Mine breaks .... > > > > gzip -c as-all.info > as-all.info.gz > > install -c -s -o bin -g bin -m 555 as /usr/bin > > ===> doc > > install-info --defsection="Programming & development tools." -- > > defentry="* AS: > > (as-all). The GNU Assembler manual." as-all.info > > //usr/share/info/ > > ins nfo: not found > > *** code 127 > > > > Stop. > > *** Error code 1 > > > > Stop. > > *** Error code 1 > > > > Stop. > > *** Error code 1 > > > > Stop. > > From owner-freebsd-hackers Sat Jan 11 03:51:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA12274 for hackers-outgoing; Sat, 11 Jan 1997 03:51:42 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id DAA12254 for ; Sat, 11 Jan 1997 03:51:22 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA21510 for hackers@FreeBSD.ORG; Sat, 11 Jan 1997 12:51:19 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id MAA29608; Sat, 11 Jan 1997 12:40:50 +0100 (MET) Message-ID: Date: Sat, 11 Jan 1997 12:40:50 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG (FreeBSD Hackers) Subject: Re: bind(2): address already in use -- how to fix? References: <199701102105.QAA23987@home.winc.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Jonathan Lemon on Jan 10, 1997 16:29:39 -0600 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jonathan Lemon wrote: > > "Address already in use" > > You need to set SO_REUSEADDR in order to re-use the socket. See your copy > of Stevens. Btw., does a proper shutdown(2) also suffice? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jan 11 03:52:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA12356 for hackers-outgoing; Sat, 11 Jan 1997 03:52:01 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id DAA12333 for ; Sat, 11 Jan 1997 03:51:54 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA21516 for freebsd-hackers@freebsd.org; Sat, 11 Jan 1997 12:51:46 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id MAA29588; Sat, 11 Jan 1997 12:33:19 +0100 (MET) Message-ID: Date: Sat, 11 Jan 1997 12:33:19 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org Subject: Re: mount -o async on a news servre References: <199701101844.NAA19882@crh.cl.msu.edu> <199701102017.NAA20456@phaeton.artisoft.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701102017.NAA20456@phaeton.artisoft.com>; from Terry Lambert on Jan 10, 1997 13:17:36 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > > Every 30 seconds by default, but its tunable with sysctl.. > > Due to two cooperating coding errors, setting this value higher > will increase the time between when you unmount removable media > and the time you can successfully eject the media (in case you > were wondering about the delay on ejecting clean JAZ disks...). Huh? You mean, after a successful umount, i could not eject a removable medium? I've never seen this, and i'm occasionally using a MO drive. Not only that i could remove it after umounting, my `od' driver even runs with the option to spin down the cartridge after closing, so i would `hear' if the drive were still open. Please, quote the coding errors, instead of only throwing claims. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jan 11 04:25:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA15835 for hackers-outgoing; Sat, 11 Jan 1997 04:25:04 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA15772 for ; Sat, 11 Jan 1997 04:24:56 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA21924 for hackers@freebsd.org; Sat, 11 Jan 1997 13:24:46 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id NAA29742; Sat, 11 Jan 1997 13:14:24 +0100 (MET) Message-ID: Date: Sat, 11 Jan 1997 13:14:24 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: unused variable in su References: <199701110142.CAA28453@xp11.frmug.org> <199701110834.TAA07745@genesis.atrad.adelaide.edu.au> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701110834.TAA07745@genesis.atrad.adelaide.edu.au>; from Michael Smith on Jan 11, 1997 19:04:36 +1030 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Michael Smith wrote: > > line 101: char shellbuf[MAXPATHLEN]; > > line 171: shell = strcpy(shellbuf, pwd->pw_shell); > > > > Shellbuf is not referenced elsewhere, is there any reason not to > > remove shellbuf (and adjust line 171), or is there a side effect I don't > > see? > > pwd is recycled later, and shell is potentially reset later, so > this is the 'correct' way to do it. Don't change it. Still, it's fairly obfuscated code. It could be better worded: if (asme) if (pwd->pw_shell && *pwd->pw_shell) { (void)strcpy(shellbuf, pwd->pw_shell); shell = shellbuf; } else { shell = _PATH_BSHELL; iscsh = NO; } This would be less confusing for compilers and human readers. Btw., shouldn't it better be a strncpy() anyway? Sure, /etc/shells is at the mercy of the sysadmin, but he isn't unfailable. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jan 11 04:25:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA15856 for hackers-outgoing; Sat, 11 Jan 1997 04:25:18 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA15850 for ; Sat, 11 Jan 1997 04:25:13 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA21940 for hackers@FreeBSD.org; Sat, 11 Jan 1997 13:25:09 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id NAA29765; Sat, 11 Jan 1997 13:20:23 +0100 (MET) Message-ID: Date: Sat, 11 Jan 1997 13:20:23 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.org Subject: Re: number of lines in a file, given its size References: <199701110202.DAA29018@xp11.frmug.org> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701110202.DAA29018@xp11.frmug.org>; from Philippe Charnier on Jan 11, 1997 03:02:10 +0100 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Philippe Charnier wrote: > In line 115 in /usr/src/lib/libc/gen/getusershell.c: > > shells = calloc((unsigned)statb.st_size / 3, sizeof (char *)); > ^^^^^^^^^^^^^^^^^ > Isn't this a suspicious approximation of the number of lines in /etc/shells > (just put `/' in it for example of an invalid entry). You are certainly right, but i think that's a moot point basically. It requires you at least the following file in order to break: /bin/sh /bin/csh / / / / (Note, no comments allowed.) Of course, this file is entirely bogus anyway, and even adding a single character after the slash keeps it in balance with that assumption. Anyway, we appreciate your PR containing the correct fix. :-) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jan 11 06:51:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA19599 for hackers-outgoing; Sat, 11 Jan 1997 06:51:29 -0800 (PST) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA19589 for ; Sat, 11 Jan 1997 06:51:25 -0800 (PST) Received: from awfulhak.demon.co.uk (localhost.coverform.lan [127.0.0.1]) by awfulhak.demon.co.uk (8.8.4/8.7.3) with ESMTP id OAA13796; Sat, 11 Jan 1997 14:30:44 GMT Message-Id: <199701111430.OAA13796@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: "Frank.A" cc: hackers@freebsd.org Subject: Re: Modem Setup In-reply-to: Your message of "Fri, 10 Jan 1997 18:52:48 EST." <199701102352.SAA01347@mail.inforamp.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Jan 1997 14:30:44 +0000 From: Brian Somers Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I am wondering how to go about seting up my modem to dial up and make a PPP > connection with an ISP. > > I have a USR 33.6 Internal and at boot up it picks up on com 2 (sio1) > > I have been trying to use minicom to dial up but when I type minicom I get > the message can not open /dev/modem. file missing > I'd suggest trying user-level ppp (aka iijppp) - the program's actually called 'ppp'. There are lots of examples in /etc/ppp and it does the dialing for you too. -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sat Jan 11 07:05:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA20133 for hackers-outgoing; Sat, 11 Jan 1997 07:05:52 -0800 (PST) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA20127 for ; Sat, 11 Jan 1997 07:05:47 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hydrogen.nike.efn.org (8.8.4/8.8.4) with SMTP id HAA04176; Sat, 11 Jan 1997 07:05:36 -0800 (PST) Date: Sat, 11 Jan 1997 07:05:35 -0800 (PST) From: John-Mark Gurney Reply-To: John-Mark Gurney To: Leonard Chua cc: Michael Hancock , freebsd-hackers@freebsd.org Subject: Re: pppd and the login option In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 11 Jan 1997, Leonard Chua wrote: > On Sat, 11 Jan 1997, Michael Hancock wrote: > > > It's a trade off with having a clear text file with passwords or having > > clear text go over the wire when considering CHAP vs. PAP w/ the system > > database. > > > True. My assumption, however, is that the PAP clear text goes over > the TCP/IP between the dialup client, via the modem, to my dialup server. > There should be no reason for such packets to ever enter the rest of > the internet. A TCP/IP guru might confirm/deny this. the way ppp works is that if has a top level lcp.. this controls how the link can comunicate... then it goes into authentication stage... after that is successful (i.e. pap password).. then it goes into the network phase in which it will try to initiate the different layers for network traffic... such as ipcp which tcp/ip uses... so the authentication isn't sent in tcp/ip packets... hope this helps.. :) ttyl.. John-Mark gurney_j@efn.org http://resnet.uoregon.edu/~gurney_j/ Modem/FAX: (541) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix) From owner-freebsd-hackers Sat Jan 11 08:19:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA22495 for hackers-outgoing; Sat, 11 Jan 1997 08:19:35 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA22483 for ; Sat, 11 Jan 1997 08:19:30 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id RAA02011 for ; Sat, 11 Jan 1997 17:21:45 +0100 (MET) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.3/8.6.9) id RAA07885 for freebsd-hackers@freefall.cdrom.com; Sat, 11 Jan 1997 17:20:04 +0100 (MET) Date: Sat, 11 Jan 1997 17:20:04 +0100 (MET) From: Christoph Kukulies Message-Id: <199701111620.RAA07885@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: Xaccel leaks? Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On one of my machines (some older 2.2-current) - where one user has the habit of leaving many X apps like ghostview/gs standing on for days - top is showing that Xaccel is now at 11M SIZE (9000K RES). swapinfo shows 37% of 44M swap. What could I do about it? Approach Xinside? Rebuild ghostview with another malloc lib? Run XFree86? In that machine we have a Matrox Millenium 4MB and XFree86 support was a bit sparse until recently. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Sat Jan 11 09:25:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA24738 for hackers-outgoing; Sat, 11 Jan 1997 09:25:56 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA24733 for ; Sat, 11 Jan 1997 09:25:54 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.4/8.8.4) with SMTP id MAA00304 for ; Sat, 11 Jan 1997 12:25:53 -0500 (EST) Date: Sat, 11 Jan 1997 12:25:53 -0500 (EST) From: John Fieber To: hackers@freebsd.org Subject: Mounting devfs on /dev Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm running RELENG_2_2 and after twiddling the sound driver to do the Right Thing for defs (which I'll submit for review), I'd like to try running devfs as /dev. Soooo, what is the current wizdom on how/when to mount it? -john From owner-freebsd-hackers Sat Jan 11 09:44:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA25715 for hackers-outgoing; Sat, 11 Jan 1997 09:44:43 -0800 (PST) Received: from kodiak.ucla.edu (kodiak.ucla.edu [164.67.128.11]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA25704; Sat, 11 Jan 1997 09:44:13 -0800 (PST) Received: from elm.cns.ucla.edu (elm.cns.ucla.edu [164.67.222.20]) by kodiak.ucla.edu (8.8.4/8.6.9) with SMTP id RAA21818; Sat, 11 Jan 1997 17:44:10 GMT From: Scott Burris To: Stefan Esser cc: freebsd-hackers@freebsd.org Subject: Re: 2.2-BETA hangs after a few minutes Message-ID: Date: Sat, 11 Jan 1997 09:44:09 -0800 () Priority: NORMAL X-Mailer: Simeon for Win32 Version 4.0.9 X-Authentication: none MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 10 Jan 1997 22:58:16 +0100 Stefan Esser wrote: > On Jan 5, scott@cns.ucla.edu (Scott Burris) wrote: > > > > To follow up my own message, I compiled the exact same kernel > > configuration from 2.2-ALPHA and it works perfectly on this system. > > So something bad has happened between ALPHA and BETA. Guess it's > > time to start diff-ing the kernel source trees to see what's changed > > :-( > > Please send verbose boot messages > (enter "-v" at the Boot: prompt). > Here they are. FYI, I brought up another machine running 2.2 BETA (a 486 EISA box) with no problems. So it's just this specific hardware. FreeBSD 2.2-BETA_A #0: Tue Dec 31 12:26:09 PST 1996 scott@elm.cns.ucla.edu:/usr/src/sys/compile/TEAK Calibrating clock(s) relative to mc146818A clock ... i586 clock: 90042054 Hz, i8254 clock: 1193166 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency CLK_USE_I586_CALIBRATION not specified - using old calibration method CPU: Pentium (90.04-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x521 Stepping=1 Features=0x1bf real memory = 50331648 (49152K bytes) avail memory = 46395392 (45308K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: MDA/hercules <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:b4:3a:50, type WD8013EPC (16 bit) bpf: ed0 attached ed1 not probed due to maddr conflict with ed0 at 0xd8000 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A : ESP sio1 not found at 0x2f8 lpt0 at 0x3bc-0x3c3 irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface bpf: lp0 attached fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in fd1: 1.2MB 5.25in wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): < TEKRAM DC-6X0X IDE cacheing controller>, 32-bit wd0: 2067MB (4233600 sectors), 4200 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): < TEKRAM DC-6X0X IDE cacheing controller>, 32-bit wd1: 1551MB (3177216 sectors), 3152 cyls, 16 heads, 63 S/T, 512 B/S bt0: Bt44xC/ 0-(32bit) bus bt0: reading board settings, busmastering, int=15 bt0: version 4.21, sync, parity, 32 mbxs, 32 ccbs bt0: targ 0 sync rate=10.00MB/s(100ns), offset=15 bt0: targ 1 sync rate=10.00MB/s(100ns), offset=15 bt0: targ 4 sync rate= 4.54MB/s(220ns), offset=08 bt0: targ 5 sync rate= 5.00MB/s(200ns), offset=15 bt0: Using Strict Round robin scheme bt0 at 0x330 irq 15 on isa (bt0:0:0): "QUANTUM XP34301 1051" type 0 fixed SCSI 2 sd0(bt0:0:0): Direct-Access 4106MB (8410200 512 byte sectors) sd0(bt0:0:0): with 4076 cyls, 20 heads, and an average 103 sectors/track (bt0:1:0): "QUANTUM XP34301 1051" type 0 fixed SCSI 2 sd1(bt0:1:0): Direct-Access 4106MB (8410200 512 byte sectors) sd1(bt0:1:0): with 4076 cyls, 20 heads, and an average 103 sectors/track (bt0:4:0): "LMS LD320 1.14" type 7 removable SCSI 2 od0(bt0:4:0): Optical od not present od0(bt0:4:0): with approximate 0 cyls, 0 heads, and 0 sectors/track (bt0:5:0): "PIONEER CD-ROM DRM-604X 2403" type 5 removable SCSI 2 cd0(bt0:5:0): CD-ROM can't get the size (bt0:5:1): "PIONEER CD-ROM DRM-604X 2403" type 5 removable SCSI 2 cd1(bt0:5:1): CD-ROM can't get the size (bt0:5:2): "PIONEER CD-ROM DRM-604X 2403" type 5 removable SCSI 2 cd2(bt0:5:2): CD-ROM can't get the size (bt0:5:3): "PIONEER CD-ROM DRM-604X 2403" type 5 removable SCSI 2 cd3(bt0:5:3): CD-ROM can't get the size (bt0:5:4): "PIONEER CD-ROM DRM-604X 2403" type 5 removable SCSI 2 cd4(bt0:5:4): CD-ROM can't get the size (bt0:5:5): "PIONEER CD-ROM DRM-604X 2403" type 5 removable SCSI 2 cd5(bt0:5:5): CD-ROM can't get the size wt0 not found at 0x300 mcd0 not found at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 npx0 on motherboard npx0: INT 16 interface imasks: bio c000c040, tty c0030092, net c0020020 BIOS Geometries: 0:03fe0f3f 0..1022=1023 cylinders, 0..15=16 heads, 1..63=63 sectors 1:03fe0f3f 0..1022=1023 cylinders, 0..15=16 heads, 1..63=63 sectors 0 accounted for Device configuration finished. Considering FFS root f/s. configure() finished. bpf: tun0 attached bpf: lo0 attached bpf: ds0 attached ccd0-3: Concatenated disk drivers wd0s1: type 0xa5, start 63, end = 4233599, size 4233537 : OK wd1s1: type 0xa5, start 63, end = 3177215, size 3177153 : OK sd0s1: type 0xa5, start 1, end = 8410199, size 8410199 : OK sd1s1: type 0xa5, start 1, end = 8410199, size 8410199 : OK sd0s1: type 0xa5, start 1, end = 8410199, size 8410199 : OK sd1s1: type 0xa5, start 1, end = 8410199, size 8410199 : OK Scott ---------------------- Scott Burris UCLA Campus Telecommunications and Network Services scott@cns.ucla.edu From owner-freebsd-hackers Sat Jan 11 10:03:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA26539 for hackers-outgoing; Sat, 11 Jan 1997 10:03:35 -0800 (PST) Received: from moonpie.w8hd.org (qmailr@moonpie.w8hd.org [198.252.159.14]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA26534 for ; Sat, 11 Jan 1997 10:03:32 -0800 (PST) Received: (qmail 20165 invoked by uid 1000); 11 Jan 1997 18:02:57 -0000 Date: 11 Jan 1997 13:02:57 -0500 Date: Sat, 11 Jan 1997 13:02:56 -0500 (EST) From: Kim Culhan To: Christoph Kukulies cc: freebsd-hackers@freefall.freebsd.org Subject: Re: Xaccel leaks? In-Reply-To: <199701111620.RAA07885@gilberto.physik.rwth-aachen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 11 Jan 1997, Christoph Kukulies wrote: > > On one of my machines (some older 2.2-current) - where one user has the habit of > leaving many X apps like ghostview/gs standing on for days - top is showing > that Xaccel is now at 11M SIZE (9000K RES). swapinfo shows 37% of 44M swap. > > What could I do about it? Approach Xinside? Rebuild ghostview with another > malloc lib? Run XFree86? > > In that machine we have a Matrox Millenium 4MB and XFree86 support was a bit > sparse until recently. This machine is a Pentium 100 running 3.0-current and Xinside's v2.1 X server, and has a Millenium 4MB and 32MB main memory. Top shows Xaccel is now at 7.92M SIZE (7156K RES) swapinfo shows 38% of 131072M swap. This is running the CDE with vic, vat, wb and sdr plus a few 'dtterms' What would be reasonable to expect? regards --kim kimc@w8hd.org From owner-freebsd-hackers Sat Jan 11 10:18:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA27124 for hackers-outgoing; Sat, 11 Jan 1997 10:18:41 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA27119 for ; Sat, 11 Jan 1997 10:18:39 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.4/8.8.4) with SMTP id NAA00625 for ; Sat, 11 Jan 1997 13:18:38 -0500 (EST) Date: Sat, 11 Jan 1997 13:18:38 -0500 (EST) From: John Fieber To: hackers@freebsd.org Subject: default permission for audio devices Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk For devfs, do are there particular opinions of ideal default permissions and ownership? Current default is 660 and root.games. -john From owner-freebsd-hackers Sat Jan 11 10:20:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA27233 for hackers-outgoing; Sat, 11 Jan 1997 10:20:12 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA27227 for ; Sat, 11 Jan 1997 10:20:09 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id TAA03213; Sat, 11 Jan 1997 19:22:26 +0100 (MET) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.3/8.6.9) id TAA08255; Sat, 11 Jan 1997 19:20:47 +0100 (MET) From: Christoph Kukulies Message-Id: <199701111820.TAA08255@gilberto.physik.rwth-aachen.de> Subject: Re: Xaccel leaks? In-Reply-To: from Kim Culhan at "Jan 11, 97 01:02:56 pm" To: kimc@w8hd.org (Kim Culhan) Date: Sat, 11 Jan 1997 19:20:46 +0100 (MET) Cc: kuku@gilberto.physik.rwth-aachen.de, freebsd-hackers@freefall.freebsd.org Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > On Sat, 11 Jan 1997, Christoph Kukulies wrote: > > > > > On one of my machines (some older 2.2-current) - where one user has the habit of > > leaving many X apps like ghostview/gs standing on for days - top is showing > > that Xaccel is now at 11M SIZE (9000K RES). swapinfo shows 37% of 44M swap. > > > > What could I do about it? Approach Xinside? Rebuild ghostview with another > > malloc lib? Run XFree86? > > > > In that machine we have a Matrox Millenium 4MB and XFree86 support was a bit > > sparse until recently. > > This machine is a Pentium 100 running 3.0-current and Xinside's v2.1 X > server, and has a Millenium 4MB and 32MB main memory. > > Top shows Xaccel is now at 7.92M SIZE (7156K RES) swapinfo shows > 38% of 131072M swap. 131 GB swap is a lot :-) > > This is running the CDE with vic, vat, wb and sdr plus a few 'dtterms' > > What would be reasonable to expect? The problem with the machine was that it often ran out of swap space - OK, 44 MB swap isn't much but is has 32MB memory and for a single user with a couple of color_xterms this should suffice. Since that happened I'm logging tops output to a file every five minutes watching it from time to time. > > regards > --kim > > kimc@w8hd.org > > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Sat Jan 11 11:14:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA29527 for hackers-outgoing; Sat, 11 Jan 1997 11:14:57 -0800 (PST) Received: from DNS.Lamb.net (root@DNS.Lamb.net [207.90.181.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA29522 for ; Sat, 11 Jan 1997 11:14:54 -0800 (PST) Received: from PacBell.TelcoSucks.org (ulf@PacBell.TelcoSucks.org [207.90.181.5]) by DNS.Lamb.net (8.8.4/8.8.2) with SMTP id LAA00623; Sat, 11 Jan 1997 11:25:37 -0800 (PST) Message-Id: <3.0.32.19970111111533.00a7ac8c@Gatekeeper-3.Lamb.net> X-Sender: ulf@Gatekeeper-3.Lamb.net X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sat, 11 Jan 1997 11:15:34 -0800 To: Christoph Kukulies , kimc@w8hd.org (Kim Culhan) From: Ulf Zimmermann Subject: Re: Xaccel leaks? Cc: kuku@gilberto.physik.rwth-aachen.de, freebsd-hackers@freefall.freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have here a 2.1.5R machine with Xaccel and a Matrox Millenium 2MB. The X is now up for about 5 days and Xaccel is at 7432K RES size (1024x768 in 256 resolution). It grows a bit more over the time, but mostly if I use Netscrap more. Ulf. At 07:20 PM 1/11/97 +0100, Christoph Kukulies wrote: >> >> >> On Sat, 11 Jan 1997, Christoph Kukulies wrote: >> >> > >> > On one of my machines (some older 2.2-current) - where one user has the habit of >> > leaving many X apps like ghostview/gs standing on for days - top is showing >> > that Xaccel is now at 11M SIZE (9000K RES). swapinfo shows 37% of 44M swap. >> > >> > What could I do about it? Approach Xinside? Rebuild ghostview with another >> > malloc lib? Run XFree86? >> > >> > In that machine we have a Matrox Millenium 4MB and XFree86 support was a bit >> > sparse until recently. >> >> This machine is a Pentium 100 running 3.0-current and Xinside's v2.1 X >> server, and has a Millenium 4MB and 32MB main memory. >> >> Top shows Xaccel is now at 7.92M SIZE (7156K RES) swapinfo shows >> 38% of 131072M swap. > >131 GB swap is a lot :-) > >> >> This is running the CDE with vic, vat, wb and sdr plus a few 'dtterms' >> >> What would be reasonable to expect? > >The problem with the machine was that it often ran out of swap space - >OK, 44 MB swap isn't much but is has 32MB memory and for a single user >with a couple of color_xterms this should suffice. > >Since that happened I'm logging tops output to a file every five minutes >watching it from time to time. > > >> >> regards >> --kim >> >> kimc@w8hd.org >> >> >> > >--Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > > ----------------------------------------------------------- Alameda Networks, Inc. | Ulf Zimmermann (ulf@Alameda.net) 1525 Pacific Avenue | Phone: (510)769-2936 Alameda, CA 94501 | Fax : (510)521-5073 From owner-freebsd-hackers Sat Jan 11 11:29:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA00368 for hackers-outgoing; Sat, 11 Jan 1997 11:29:45 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA00362 for ; Sat, 11 Jan 1997 11:29:41 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA01391 for hackers@freebsd.org; Sat, 11 Jan 1997 20:29:39 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id UAA01413; Sat, 11 Jan 1997 20:10:07 +0100 (MET) Message-ID: Date: Sat, 11 Jan 1997 20:10:07 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: default permission for audio devices References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from John Fieber on Jan 11, 1997 13:18:38 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As John Fieber wrote: > For devfs, do are there particular opinions of ideal default > permissions and ownership? Current default is 660 and > root.games. I think DEVFS should create all devices 0600 root:wheel. It's bogus for the kernel to hard-code user or group names. Everything else should be handled at rc(8) time, which is also where the beloved persistency will come into the game. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jan 11 11:30:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA00433 for hackers-outgoing; Sat, 11 Jan 1997 11:30:33 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA00417 for ; Sat, 11 Jan 1997 11:30:20 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA01397; Sat, 11 Jan 1997 20:29:48 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id UAA01427; Sat, 11 Jan 1997 20:12:03 +0100 (MET) Message-ID: Date: Sat, 11 Jan 1997 20:12:03 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: jfieber@indiana.edu (John Fieber) Cc: hackers@FreeBSD.ORG Subject: Re: Mounting devfs on /dev References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from John Fieber on Jan 11, 1997 12:25:53 -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As John Fieber wrote: > I'm running RELENG_2_2 and after twiddling the sound driver to do > the Right Thing for defs (which I'll submit for review), I'd like > to try running devfs as /dev. > > Soooo, what is the current wizdom on how/when to mount it? options DEVFS_ROOT This will pass -r to init(8), which in turn causes it to mount DEVFS. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jan 11 11:50:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA01607 for hackers-outgoing; Sat, 11 Jan 1997 11:50:40 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA01602 for ; Sat, 11 Jan 1997 11:50:35 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA24005; Sat, 11 Jan 1997 12:39:07 -0700 From: Terry Lambert Message-Id: <199701111939.MAA24005@phaeton.artisoft.com> Subject: Re: unused variable in su To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 11 Jan 1997 12:39:07 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: from "J Wunsch" at Jan 11, 97 01:14:24 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Still, it's fairly obfuscated code. It could be better worded: > > if (asme) > if (pwd->pw_shell && *pwd->pw_shell) { > (void)strcpy(shellbuf, pwd->pw_shell); > shell = shellbuf; > } else { > shell = _PATH_BSHELL; > iscsh = NO; > } > > This would be less confusing for compilers and human readers. Human readers are expected to have familiarity with the return values of standard library routines. Explicitly void casting strcpy indicates it has a return value which is being ignored, for no good reason. > Btw., shouldn't it better be a strncpy() anyway? Sure, /etc/shells is > at the mercy of the sysadmin, but he isn't unfailable. Personally, I'd use strdup() istead of an auto buffer to allocate the buffer at whatever size is necessary... ie: get rid of shellbuf entirely and replace: shell = strcpy(shellbuf, pwd->pw_shell); with: shell = strdup( pwd->pw_shell); But, hey, that's me, using strdup() for what it was intended to do. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Jan 11 11:54:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA01774 for hackers-outgoing; Sat, 11 Jan 1997 11:54:27 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA01768 for ; Sat, 11 Jan 1997 11:54:24 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA24017; Sat, 11 Jan 1997 12:40:52 -0700 From: Terry Lambert Message-Id: <199701111940.MAA24017@phaeton.artisoft.com> Subject: Re: number of lines in a file, given its size To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 11 Jan 1997 12:40:52 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: from "J Wunsch" at Jan 11, 97 01:20:23 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > In line 115 in /usr/src/lib/libc/gen/getusershell.c: > > > > shells = calloc((unsigned)statb.st_size / 3, sizeof (char *)); > > ^^^^^^^^^^^^^^^^^ > > Isn't this a suspicious approximation of the number of lines in /etc/shells > > (just put `/' in it for example of an invalid entry). > > You are certainly right, but i think that's a moot point basically. > It requires you at least the following file in order to break: strdup() to the rescue! ... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Jan 11 12:00:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA02364 for hackers-outgoing; Sat, 11 Jan 1997 12:00:46 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA02356 for ; Sat, 11 Jan 1997 12:00:40 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA24041; Sat, 11 Jan 1997 12:47:49 -0700 From: Terry Lambert Message-Id: <199701111947.MAA24041@phaeton.artisoft.com> Subject: Re: mount -o async on a news servre To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Sat, 11 Jan 1997 12:47:49 -0700 (MST) Cc: jlemon@americantv.com, terry@lambert.org, scrappy@hub.org, hackers@freebsd.org In-Reply-To: <199701110824.SAA07725@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jan 11, 97 06:54:07 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > FreeBSD for the NCR Tower! Yes! Yes! I was thinking about this a while ago. A Tower32 wouldn't be that hard (given the NetBSD HP300 port), but a Tower16 would be a bugger... unfortunately, the only NCR hardware I know is lying around somewhere is a Tower16. Maybe we should abstract the VM dependencies and services provided from a dependency on a full PMMU? Then you could port to the Tower16, the Tandy 6000, and the 80286, if you wanted. ...Just a bizarre thought... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Jan 11 12:04:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA02683 for hackers-outgoing; Sat, 11 Jan 1997 12:04:14 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA02675 for ; Sat, 11 Jan 1997 12:04:10 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA24055; Sat, 11 Jan 1997 12:52:34 -0700 From: Terry Lambert Message-Id: <199701111952.MAA24055@phaeton.artisoft.com> Subject: Re: mount -o async on a news servre To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 11 Jan 1997 12:52:34 -0700 (MST) Cc: freebsd-hackers@freebsd.org In-Reply-To: from "J Wunsch" at Jan 11, 97 12:33:19 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Every 30 seconds by default, but its tunable with sysctl.. > > > > Due to two cooperating coding errors, setting this value higher > > will increase the time between when you unmount removable media > > and the time you can successfully eject the media (in case you > > were wondering about the delay on ejecting clean JAZ disks...). > > Huh? You mean, after a successful umount, i could not eject a > removable medium? I've never seen this, and i'm occasionally using a > MO drive. Not only that i could remove it after umounting, my `od' > driver even runs with the option to spin down the cartridge after > closing, so i would `hear' if the drive were still open. > > Please, quote the coding errors, instead of only throwing claims. The buffers for the device are not decommitted until the next vclean run, since the freed vnodes with buffers attached are still in the cache. Perhaps "coding errors" was too strong; "antiquated design decisions which did not consider the maximum possible number of future usages to which the code might later be put" is probably more apt. Maybe it could be most simply stated as "there are two places where the code authors failed to look into the future". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Jan 11 12:08:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA02957 for hackers-outgoing; Sat, 11 Jan 1997 12:08:17 -0800 (PST) Received: from gatekeeper.ray.com (gatekeeper.ray.com [138.125.162.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA02952 for ; Sat, 11 Jan 1997 12:08:15 -0800 (PST) From: Gregory_D_Moncreaff@ccmail.ed.ray.com Received: (mailer@localhost) by gatekeeper.ray.com (8.7.5/8.7.3) id PAA18251 for ; Sat, 11 Jan 1997 15:08:38 -0500 Received: from zeus.ed.ray.com by gatekeeper.ray.com; Sat Jan 11 15:05:53 1997 Received: from ccmail.ed.ray.com by ZEUS.ED.RAY.COM (PMDF V4.2-10 #4335) id <01IE3AF7WI5C0000GN@ZEUS.ED.RAY.COM>; Sat, 11 Jan 1997 15:08:07 EST Date: Sat, 11 Jan 1997 14:58 -0500 (EST) Subject: Can you install and run FreeBSD on a Iomega Jaz cartridge? To: hackers@freebsd.org Message-id: <01IE3AF7X1G20000GN@ZEUS.ED.RAY.COM> MIME-version: 1.0 Content-transfer-encoding: 7BIT Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can you install and run FreeBSD on a Iomega Jaz cartridge? I was thinking that you might want to have a swap partition on a local disk, but could all the ufs partitions be on the Jaz? that way you could load the operating system-de-jour cartridge [dos, win95, winnt, linux, freebsd, ...] and let the boot manager on the physical boot disk find it... thanks, g From owner-freebsd-hackers Sat Jan 11 12:16:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA03460 for hackers-outgoing; Sat, 11 Jan 1997 12:16:28 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA03455 for ; Sat, 11 Jan 1997 12:16:26 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.4/8.8.4) with SMTP id PAA00384; Sat, 11 Jan 1997 15:15:49 -0500 (EST) Date: Sat, 11 Jan 1997 15:15:47 -0500 (EST) From: John Fieber To: Joerg Wunsch cc: hackers@FreeBSD.ORG Subject: Re: Mounting devfs on /dev In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 11 Jan 1997, J Wunsch wrote: > As John Fieber wrote: > > > I'm running RELENG_2_2 and after twiddling the sound driver to do > > the Right Thing for defs (which I'll submit for review), I'd like > > to try running devfs as /dev. > > > > Soooo, what is the current wizdom on how/when to mount it? > > options DEVFS_ROOT > > This will pass -r to init(8), which in turn causes it to mount DEVFS. So far so good. Now, what does: panic: ffs_mountroot: can't set up bdevvp for root mean? Thanks, -john From owner-freebsd-hackers Sat Jan 11 13:14:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA06354 for hackers-outgoing; Sat, 11 Jan 1997 13:14:52 -0800 (PST) Received: from DNS.Lamb.net (root@DNS.Lamb.net [207.90.181.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA06345 for ; Sat, 11 Jan 1997 13:14:48 -0800 (PST) Received: from PacBell.TelcoSucks.org (ulf@PacBell.TelcoSucks.org [207.90.181.5]) by DNS.Lamb.net (8.8.4/8.8.2) with SMTP id NAA00869 for ; Sat, 11 Jan 1997 13:26:24 -0800 (PST) Message-Id: <3.0.32.19970111131618.00a3aed4@Gatekeeper-3.Lamb.net> X-Sender: ulf@Gatekeeper-3.Lamb.net X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sat, 11 Jan 1997 13:16:18 -0800 To: hackers@freebsd.org From: Ulf Zimmermann Subject: XFree86 broken on ftp.cdrom.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just wanted to download it and the /pub/XFree86/3.2/binaries/FreeBSD-2.2 are pointing all back to itself. XF8632bin.tgz is the only file I can see there. As FreeBSD-current is a link to 2.2 it doesn't work either. Ulf. ----------------------------------------------------------- Alameda Networks, Inc. | Ulf Zimmermann (ulf@Alameda.net) 1525 Pacific Avenue | Phone: (510)769-2936 Alameda, CA 94501 | Fax : (510)521-5073 From owner-freebsd-hackers Sat Jan 11 13:14:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA06367 for hackers-outgoing; Sat, 11 Jan 1997 13:14:57 -0800 (PST) Received: from whale.gu.kiev.ua (whale.gu.net [194.93.190.4]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA06346 for ; Sat, 11 Jan 1997 13:14:48 -0800 (PST) Received: from trifork.gu.net (trifork.gu.net [194.93.190.194]) by whale.gu.kiev.ua (8.7.5/8.7.3) with SMTP id XAA24960; Sat, 11 Jan 1997 23:12:59 +0200 Date: Sun, 12 Jan 1997 02:17:05 +0200 (EET) From: Andrew Stesin To: Terry Lambert cc: The Hermit Hacker , hackers@freebsd.org Subject: Re: mount -o async on a news servre In-Reply-To: <199701102006.NAA20414@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dear Terry, thanks a lot for your explicit analysis! Every time reading your messages I learn much, it's a great gift. Now just a few minor additions, sorry. On Fri, 10 Jan 1997, Terry Lambert wrote: > > Exactly *how* dangerous is setting a file system to async? > > Depends on how much you will miss the data if it disappears. For > passive news servers, not very. It depends. After such a failure you'll loose sync between your actual newsspool and all the databases carried by INN or CNews; => rebuild of history and active will be needed to recover consistency of the entire news system => terrific amount of time will be lost doing this each time, even on a small (1Gb) news spool. On the other hand, I assume that crash will result only in article lossage from spool, no other consequenses; so if you'll tolerate the fact that your history and active databases do carry information about several hundreds of lost articles -- your'e (probably) Ok. [...] > was there before) pointed to by a valid index record, and a valid (but > orphaned) data record not pointed to by anyone. ... in the case of news this means "an article in spool which isn't in the history+active", right? It's also bad. [...] > The INN history file would probably need to be rebuilt after each crash God save me! as I told earlier. :-) Just for now I consider that "noatime" mount option is the best balance between reliability and performance on FreeBSD, right? Best regards, Andrew Stesin nic-hdl: ST73-RIPE From owner-freebsd-hackers Sat Jan 11 14:01:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA08658 for hackers-outgoing; Sat, 11 Jan 1997 14:01:19 -0800 (PST) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA08650 for ; Sat, 11 Jan 1997 14:01:15 -0800 (PST) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.2/8.8.2) id JAA29226; Sun, 12 Jan 1997 09:01:05 +1100 (EST) From: David Dawes Message-Id: <199701112201.JAA29226@rf900.physics.usyd.edu.au> Subject: Re: XFree86 broken on ftp.cdrom.com In-Reply-To: <3.0.32.19970111131618.00a3aed4@Gatekeeper-3.Lamb.net> from Ulf Zimmermann at "Jan 11, 97 01:16:18 pm" To: ulf@Lamb.net (Ulf Zimmermann) Date: Sun, 12 Jan 1997 09:01:05 +1100 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I just wanted to download it and the /pub/XFree86/3.2/binaries/FreeBSD-2.2 >are pointing all back to itself. XF8632bin.tgz is the only file I can see >there. >As FreeBSD-current is a link to 2.2 it doesn't work either. It looks like a mirroring problem. FreeBSD-2.2 and FreeBSD-current recently became separate directories on ftp.xfree86.org. David From owner-freebsd-hackers Sat Jan 11 14:04:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA08832 for hackers-outgoing; Sat, 11 Jan 1997 14:04:19 -0800 (PST) Received: from DNS.Lamb.net (root@DNS.Lamb.net [207.90.181.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA08827 for ; Sat, 11 Jan 1997 14:04:16 -0800 (PST) Received: from PacBell.TelcoSucks.org (ulf@PacBell.TelcoSucks.org [207.90.181.5]) by DNS.Lamb.net (8.8.4/8.8.2) with SMTP id OAA00952; Sat, 11 Jan 1997 14:15:36 -0800 (PST) Message-Id: <3.0.32.19970111140529.009e145c@Gatekeeper-3.Lamb.net> X-Sender: ulf@Gatekeeper-3.Lamb.net X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sat, 11 Jan 1997 14:05:30 -0800 To: David Dawes , ulf@Lamb.net (Ulf Zimmermann) From: Ulf Zimmermann Subject: Re: XFree86 broken on ftp.cdrom.com Cc: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am right now downloading it from xfree86.org directly and have a fast link to cdrom.com (175kB/sec). I can upload it, if you want. Ulf. At 09:01 AM 1/12/97 +1100, David Dawes wrote: >>I just wanted to download it and the /pub/XFree86/3.2/binaries/FreeBSD-2.2 >>are pointing all back to itself. XF8632bin.tgz is the only file I can see >>there. >>As FreeBSD-current is a link to 2.2 it doesn't work either. > >It looks like a mirroring problem. FreeBSD-2.2 and FreeBSD-current >recently became separate directories on ftp.xfree86.org. > >David > > ----------------------------------------------------------- Alameda Networks, Inc. | Ulf Zimmermann (ulf@Alameda.net) 1525 Pacific Avenue | Phone: (510)769-2936 Alameda, CA 94501 | Fax : (510)521-5073 From owner-freebsd-hackers Sat Jan 11 14:11:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA09335 for hackers-outgoing; Sat, 11 Jan 1997 14:11:58 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA09326 for ; Sat, 11 Jan 1997 14:11:52 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA24261; Sat, 11 Jan 1997 14:59:31 -0700 From: Terry Lambert Message-Id: <199701112159.OAA24261@phaeton.artisoft.com> Subject: Re: mount -o async on a news servre To: stesin@gu.net (Andrew Stesin) Date: Sat, 11 Jan 1997 14:59:31 -0700 (MST) Cc: terry@lambert.org, scrappy@hub.org, hackers@freebsd.org In-Reply-To: from "Andrew Stesin" at Jan 12, 97 02:17:05 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > The INN history file would probably need to be rebuilt after each crash > > God save me! as I told earlier. :-) > > Just for now I consider that "noatime" mount option > is the best balance between reliability and performance > on FreeBSD, right? Probably; considering that you don't have make dependencies. It *may* result in some articles being prematurely expired following a crash; not a real problem. The "access time" option is mostly security related, and for data migration to an archive ...neither one of these should be a big problem on a news server. There is some confusion, I think, between "shall be marked for update" vs. "shall be updated" vs. "shall have updates committed to stable storage" when people try to interpret POSIX. I think most of the wins you get from noatime could come without the sacrifices if "shall be updated" was interpreted to mean something other than committing the date stamps to stable storage (a sync write in the current code, each time a directory or file is accessed). Barring hacking on the code, "noatime" is a good compromise soloution for using the existing code without modifiecation. If I were running a big site, I would be tempted to run a reading host and a *seperate* posting host. A reading host would be, by definition, a passive news spool with no locally generated data; I'd run the FS for the news spool in async mode. Using a seperate server for posting, I could run the posting host with atime and sync... so my users postings would not be lost because of a crash. Depending on how the client software operates, you might have to run a request forwarder (ie: the posting host may have to pretend to be a full nntp server to let your users read from the same host, but it would forward all nntp read requests to the passive news spool, while satisfying write requests locally. Articles posted by users would be spooled to the reading host as "just another feed". In event of a crash, the lost data can be recovered from all feed hosts... including the posting host. If the news had not been propagated priior to the crash, it would still be propagated after recover. Ideally, a near future version of FreeBSD will have soft updates, and you will no longer get better speed from running async (soft updates give you speed equal to async and reliability equal to sync). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Jan 11 14:51:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA11569 for hackers-outgoing; Sat, 11 Jan 1997 14:51:32 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA11549 for ; Sat, 11 Jan 1997 14:51:28 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA05469 for hackers@freebsd.org; Sat, 11 Jan 1997 23:51:26 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id XAA02105; Sat, 11 Jan 1997 23:48:54 +0100 (MET) Message-ID: Date: Sat, 11 Jan 1997 23:48:54 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: number of lines in a file, given its size References: <199701111940.MAA24017@phaeton.artisoft.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701111940.MAA24017@phaeton.artisoft.com>; from Terry Lambert on Jan 11, 1997 12:40:52 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > > You are certainly right, but i think that's a moot point basically. > > It requires you at least the following file in order to break: > > strdup() to the rescue! ... Failed. Try again. UTSL first. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jan 11 15:21:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA12974 for hackers-outgoing; Sat, 11 Jan 1997 15:21:54 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA12939 for ; Sat, 11 Jan 1997 15:20:49 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA05880 for freebsd-hackers@freebsd.org; Sun, 12 Jan 1997 00:20:32 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id XAA02241; Sat, 11 Jan 1997 23:52:41 +0100 (MET) Message-ID: Date: Sat, 11 Jan 1997 23:52:41 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org Subject: Re: mount -o async on a news servre References: <199701111952.MAA24055@phaeton.artisoft.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701111952.MAA24055@phaeton.artisoft.com>; from Terry Lambert on Jan 11, 1997 12:52:34 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > > Huh? You mean, after a successful umount, i could not eject a > > removable medium? I've never seen this, and i'm occasionally using a > > MO drive. Not only that i could remove it after umounting, my `od' > > driver even runs with the option to spin down the cartridge after > > closing, so i would `hear' if the drive were still open. > The buffers for the device are not decommitted until the next vclean > run, ... Perhaps they are not _guaranteed_ to be decommitted until the next vclean run? No, i don't think so. umount(8) waits until all buffers are clear, which often can take a tremendous amount of time on a MO medium. Once umount(8) returns, the medium spins down immediately, which basically means odclose() has been called. This proves your theory wrong. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jan 11 15:24:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA13115 for hackers-outgoing; Sat, 11 Jan 1997 15:24:49 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA13103 for ; Sat, 11 Jan 1997 15:24:40 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA05888; Sun, 12 Jan 1997 00:22:41 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id AAA02741; Sun, 12 Jan 1997 00:20:15 +0100 (MET) Message-ID: Date: Sun, 12 Jan 1997 00:20:14 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: jfieber@indiana.edu (John Fieber) Cc: hackers@FreeBSD.ORG Subject: Re: Mounting devfs on /dev References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from John Fieber on Jan 11, 1997 15:15:47 -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As John Fieber wrote: > > options DEVFS_ROOT > > > > This will pass -r to init(8), which in turn causes it to mount DEVFS. > > So far so good. Now, what does: > > panic: ffs_mountroot: can't set up bdevvp for root Are you sure everything has been built correctly? Just for grins, i've rebuilt the kernel on my scratchbox (this time the diskless one, it was simpler for me). It worked out of the box. j@uncle 53% uname -a FreeBSD uncle 3.0-CURRENT FreeBSD 3.0-CURRENT #9: Sun Jan 12 00:00:11 MET 1997 j@uriah.heep.sax.de:/usr/diskless/uncle-root/sys-cur/compile/UNCLE i386 j@uncle 54% /sbin/mount 192.168.0.1:/usr/diskless/uncle-root on / devfs on /dev (local, noexec, read-only) uriah:/usr on /usr (read-only) uriah:/home on /home mfs:20 on /tmp (asynchronous, local) procfs on /proc (local, read-only) j@uncle 55% ls /dev /dev: bpf0% fd0.820# log@ rfd0.1480% rvn4% ttyp2% ttyvb% console% fd0a# lpctl0% rfd0.1720% rvn5% ttyp3% ttyvc% cuaa0% fd0b# lpt0% rfd0.720% rvn6% ttyp4% ttyvd% cuaa1% fd0c# mem% rfd0.800% rvn7% ttyp5% ttyve% cuaia0% fd0d# null% rfd0.820% speaker% ttyp6% ttyvf% cuaia1% fd0e# ptyp0% rfd0a% stderr% ttyp7% urandom% cuala0% fd0f# ptyp1% rfd0b% stdin% ttyv0% vn0# cuala1% fd0g# ptyp2% rfd0c% stdout% ttyv1% vn1# drum% fd0h# ptyp3% rfd0d% tty% ttyv2% vn2# fd/ gsc0% ptyp4% rfd0e% ttyd0% ttyv3% vn3# fd0# gsc0d% ptyp5% rfd0f% ttyd1% ttyv4% vn4# fd0.1200# gsc0p% ptyp6% rfd0g% ttyid0% ttyv5% vn5# fd0.1440# gsc0pd% ptyp7% rfd0h% ttyid1% ttyv6% vn6# fd0.1480# io% random% rvn0% ttyld0% ttyv7% vn7# fd0.1720# klog% rfd0% rvn1% ttyld1% ttyv8% zero% fd0.720# kmem% rfd0.1200% rvn2% ttyp0% ttyv9% fd0.800# lkm% rfd0.1440% rvn3% ttyp1% ttyva% That /dev looks fairly tidied up, doesn't it? :-) Btw., i just notice that ft0 is missing, and: bpf: ppp0 attached bpf: ppp1 attached bpf: lo0 attached ...bpf1 and bpf2 seems to be missing, too. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jan 11 15:31:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA13578 for hackers-outgoing; Sat, 11 Jan 1997 15:31:25 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA13573 for ; Sat, 11 Jan 1997 15:31:21 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.4/8.8.4) with SMTP id SAA00872; Sat, 11 Jan 1997 18:31:05 -0500 (EST) Date: Sat, 11 Jan 1997 18:31:04 -0500 (EST) From: John Fieber To: Joerg Wunsch cc: hackers@FreeBSD.ORG Subject: Re: Mounting devfs on /dev In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 12 Jan 1997, J Wunsch wrote: > As John Fieber wrote: > > Are you sure everything has been built correctly? > > Just for grins, i've rebuilt the kernel on my scratchbox (this time > the diskless one, it was simpler for me). It worked out of the box. > > j@uncle 53% uname -a > FreeBSD uncle 3.0-CURRENT FreeBSD 3.0-CURRENT #9: Sun Jan 12 00:00:11 MET 1997 j@uriah.heep.sax.de:/usr/diskless/uncle-root/sys-cur/compile/UNCLE i386 ^^^^^^^^^^^ Hmm... might there be some devfs related changes in current that are not in RELENG_2_2 (as of several days ago)? Any other required kernel config options besides DEVFS and DEVFS_ROOT? My current kernel config: machine "i386" cpu "I486_CPU" cpu "I586_CPU" ident FALLOUT maxusers 15 options CHILD_MAX=128 options OPEN_MAX=128 options "COMPAT_43" options USER_LDT options SYSVSHM #SYSV shared memory options SYSVSEM #SYSV semaphores options SYSVMSG #SYSV messages options KTRACE #Kernel syscall tracing options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options INET #InterNETworking options NETATALK #AppleTalk options FFS #Berkeley Fast Filesystem options DEVFS options DEVFS_ROOT config kernel root on sd0 # ISA Bus controller isa0 options "AUTO_EOI_1" options "AUTO_EOI_2" # PCI Bus controller pci0 # Floppy disk controller controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 # SCSI Controller and devices controller ncr0 controller scbus0 at ncr0 #controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr #controller scbus1 at aha0 device sd0 device st0 device cd0 options SCSI_DELAY=10 #Be pessimistic about Joe SCSI device #options SCSIDEBUG # Syscons console driver (SCO compatible) device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Math processor device npx0 at isa? port "IO_NPX" irq 13 vector npxintr # Serial ports device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr # Parallel ports device lpt0 at isa? port? tty irq 7 vector lptintr # Ethernet device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr # Sound card controller snd0 device sb0 at isa? port 0x220 irq 10 drq 1 vector sbintr device sbxvi0 at isa? drq 6 device sbmidi0 at isa? port 0x300 device opl0 at isa? port 0x388 # Pseudo devices pseudo-device loop # loopback device pseudo-device ether # core ethernet code pseudo-device log # system logging pseudo-device pty 32 # pseudo terminals pseudo-device speaker # PC speaker interface pseudo-device gzip # Exec gzipped a.out's pseudo-device vn # vnode driver (turns a file into a device) pseudo-device bpfilter 4 # Berkeley packet filter device From owner-freebsd-hackers Sat Jan 11 16:23:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA18130 for hackers-outgoing; Sat, 11 Jan 1997 16:23:19 -0800 (PST) Received: from mail.bb.cc.wa.us ([208.8.136.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA18118 for ; Sat, 11 Jan 1997 16:23:15 -0800 (PST) Received: (from chris@localhost) by mail.bb.cc.wa.us (8.8.3/8.8.3) id QAA00793; Sat, 11 Jan 1997 16:19:46 GMT Date: Sat, 11 Jan 1997 16:19:46 +0000 () From: Chris Coleman To: hackers@freebsd.org Subject: IPFILTER Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Im setting up ipfilter to work on my system and I have it installed. But i need help configuring the rules so that it will actually work. I have two cards in the FBSD box. fxp0 and vx0 fpx0 is 208.8.136.10 vx0 is 10.16.14.1 i have a client on 10.16.14.100 and i want it to be translated to a 208.8.136.10 address so that it can go out. how do i do this? thanks chris coleman From owner-freebsd-hackers Sat Jan 11 16:25:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA18315 for hackers-outgoing; Sat, 11 Jan 1997 16:25:42 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA18308 for ; Sat, 11 Jan 1997 16:25:39 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <16157(6)>; Sat, 11 Jan 1997 16:25:05 PST Received: by crevenia.parc.xerox.com id <177476>; Sat, 11 Jan 1997 16:24:52 -0800 From: Bill Fenner To: jfieber@indiana.edu, joerg_wunsch@uriah.heep.sax.de Subject: Re: Mounting devfs on /dev Cc: hackers@freebsd.org Message-Id: <97Jan11.162452pst.177476@crevenia.parc.xerox.com> Date: Sat, 11 Jan 1997 16:24:43 PST Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >bpf: ppp0 attached >bpf: ppp1 attached >bpf: lo0 attached > >...bpf1 and bpf2 seems to be missing, too. The "bpf: ... attached" messages just mean that that interface has registered itself with bpf, not that bpf has that number of minor devices. bpf just has the number of minors that are configured in your kernel configuration. (So if you have "pseudo-device bpfilter 3" then bpf1 and bpf2 are missing...) Bill From owner-freebsd-hackers Sat Jan 11 16:47:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA20713 for hackers-outgoing; Sat, 11 Jan 1997 16:47:03 -0800 (PST) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA20707 for ; Sat, 11 Jan 1997 16:47:00 -0800 (PST) Received: from ct.picker.com by whqvax.picker.com with SMTP; Sat, 11 Jan 1997 19:45:45 -0500 (EST) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA19084; Sat, 11 Jan 97 19:45:38 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id TAA15467; Sat, 11 Jan 1997 19:44:09 -0500 Message-Id: Date: Sat, 11 Jan 1997 19:44:08 -0500 From: rhh@ct.picker.com (Randall Hopper) To: terry@lambert.org (Terry Lambert) Cc: jlemon@americantv.com (Jonathan Lemon), freebsd-hackers@freebsd.org Subject: USR Sportster Problems (was Re: FreeBSD as an ISDN Router) References: <199701082310.QAA17253@phaeton.artisoft.com> X-Mailer: Mutt 0.56 Mime-Version: 1.0 In-Reply-To: <199701082310.QAA17253@phaeton.artisoft.com>; from Terry Lambert on Jan 8, 1997 16:10:11 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert: |jlemon@americantv.com (Jonathan Lemon) |> used it, but the Motorola Power modems are pretty good. Now, if you want |> to sling mud at modems, probably nothing is more deserving of the |> "piece-o-shit" label than the USR's Sportster line. | |The Sportster 14.4 FAXmodem (I believe) is theonly one affected, and |it's only a problem if you talk to Rockwell chipset modems on the |other end. There are a few more with the 28.8/33.6s. E.g.: http://www.carabelli.com/lore/usrincident.html http://www.usr.com/home/online/trblshot/13015.htm Randall Hopper From owner-freebsd-hackers Sat Jan 11 16:57:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA21229 for hackers-outgoing; Sat, 11 Jan 1997 16:57:45 -0800 (PST) Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA21224 for ; Sat, 11 Jan 1997 16:57:38 -0800 (PST) Received: (from davidn@localhost) by labs.usn.blaze.net.au (8.8.4/8.8.4) id WAA00807; Sat, 11 Jan 1997 22:57:11 +1100 (EST) Message-ID: Date: Sat, 11 Jan 1997 11:57:10 +0000 From: davidn@unique.usn.blaze.net.au (David Nugent) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: jfieber@indiana.edu (John Fieber), hackers@FreeBSD.ORG Subject: Re: Mounting devfs on /dev References: X-Mailer: Mutt 0.56 Mime-Version: 1.0 In-Reply-To: ; from J Wunsch on Jan 12, 1997 00:20:14 +0100 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch writes: > As John Fieber wrote: > > > > options DEVFS_ROOT > > > > > > This will pass -r to init(8), which in turn causes it to mount DEVFS. > > > > So far so good. Now, what does: > > > > panic: ffs_mountroot: can't set up bdevvp for root > > Are you sure everything has been built correctly? FWIW, it happens here too. It seems that devfs does not (yet) create the device nodes for hard disks correctly. It may be related to having the FreeBSD slice on a separate partition (in my case it was sd1s2). I've recently built a new root on sd0 using sd0x devices and not sd0xsNx, so I will give it another try when I next do a kernel build. > j@uncle 55% ls /dev > /dev: > bpf0% fd0.820# log@ rfd0.1480% rvn4% ttyp2% ttyvb% > console% fd0a# lpctl0% rfd0.1720% rvn5% ttyp3% ttyvc% > cuaa0% fd0b# lpt0% rfd0.720% rvn6% ttyp4% ttyvd% > cuaa1% fd0c# mem% rfd0.800% rvn7% ttyp5% ttyve% > cuaia0% fd0d# null% rfd0.820% speaker% ttyp6% ttyvf% > cuaia1% fd0e# ptyp0% rfd0a% stderr% ttyp7% urandom% > cuala0% fd0f# ptyp1% rfd0b% stdin% ttyv0% vn0# > cuala1% fd0g# ptyp2% rfd0c% stdout% ttyv1% vn1# > drum% fd0h# ptyp3% rfd0d% tty% ttyv2% vn2# > fd/ gsc0% ptyp4% rfd0e% ttyd0% ttyv3% vn3# > fd0# gsc0d% ptyp5% rfd0f% ttyd1% ttyv4% vn4# > fd0.1200# gsc0p% ptyp6% rfd0g% ttyid0% ttyv5% vn5# > fd0.1440# gsc0pd% ptyp7% rfd0h% ttyid1% ttyv6% vn6# > fd0.1480# io% random% rvn0% ttyld0% ttyv7% vn7# > fd0.1720# klog% rfd0% rvn1% ttyld1% ttyv8% zero% > fd0.720# kmem% rfd0.1200% rvn2% ttyp0% ttyv9% > fd0.800# lkm% rfd0.1440% rvn3% ttyp1% ttyva% > > That /dev looks fairly tidied up, doesn't it? :-) Sure does. > Btw., i just notice that ft0 is missing, and: > > bpf: ppp0 attached > bpf: ppp1 attached > bpf: lo0 attached > > ...bpf1 and bpf2 seems to be missing, too. And where are the hard disk devices? :-) DEVFS_ROOT works great for netboots though. Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-hackers Sat Jan 11 17:12:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA21797 for hackers-outgoing; Sat, 11 Jan 1997 17:12:53 -0800 (PST) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA21789 for ; Sat, 11 Jan 1997 17:12:50 -0800 (PST) Received: from ct.picker.com by whqvax.picker.com with SMTP; Sat, 11 Jan 1997 20:11:41 -0500 (EST) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA19366; Sat, 11 Jan 97 20:11:40 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id UAA15508; Sat, 11 Jan 1997 20:10:04 -0500 Message-Id: Date: Sat, 11 Jan 1997 20:10:03 -0500 From: rhh@ct.picker.com (Randall Hopper) To: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies) Cc: freebsd-hackers@FreeBSD.org Subject: Re: A cool xterm? References: <199701101606.IAA03133@impulse.csl.sri.com> <199701101746.SAA01138@gilberto.physik.rwth-aachen.de> X-Mailer: Mutt 0.56 Mime-Version: 1.0 In-Reply-To: <199701101746.SAA01138@gilberto.physik.rwth-aachen.de>; from Christoph Kukulies on Jan 10, 1997 18:46:31 +0100 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Christoph Kukulies: |Running fvwm95-2 my color_xterms that pop up initially (by .xinitrc - I'm |using startx) have 3D-effect scrollbars and shaded edged pop up menues |but with dithered gray shades rather than the colored shades. | |Only newly created color_xterms (launched from the tool bar) show the |correct colors and solid colored shades. I event put the resources |into .Xresources - no change. Any ideas? It sounds like the resources aren't getting xrdbed soon enough (for the .Xdefaults/.Xresources case), or your XAPPLRESDIR/XUSERFILESEARCHPATH isn't getting set soon enough (for the Color_xterm/XTerm app-default file case). To cover both cases, flip these lines into the top of your .xinitrc, before your invocation of fvwm95-2 and before invocation of your color_xterms (if you're invoking them here and not in the .fvwm2rc95 file). Tweak XAPPLRESDIR to where you keep your local class resource files (e.g. XTerm/Color_xterm). XAPPLRESDIR=$HOME/cfg/app-defaults; export XAPPLRESDIR userresources=$HOME/.Xresources if [ -f $userresources ]; then xrdb -merge $userresources fi Randall Hopper From owner-freebsd-hackers Sat Jan 11 17:23:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA22312 for hackers-outgoing; Sat, 11 Jan 1997 17:23:22 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA22304 for ; Sat, 11 Jan 1997 17:23:20 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.4/8.8.4) with SMTP id UAA01206; Sat, 11 Jan 1997 20:22:35 -0500 (EST) Date: Sat, 11 Jan 1997 20:22:35 -0500 (EST) From: John Fieber To: David Nugent cc: Joerg Wunsch , hackers@FreeBSD.ORG Subject: Re: Mounting devfs on /dev In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 11 Jan 1997, David Nugent wrote: > J Wunsch writes: > > As John Fieber wrote: > > > panic: ffs_mountroot: can't set up bdevvp for root > > Are you sure everything has been built correctly? > > FWIW, it happens here too. It seems that devfs does not (yet) > create the device nodes for hard disks correctly. It may be > related to having the FreeBSD slice on a separate partition > (in my case it was sd1s2). I've recently built a new root > on sd0 using sd0x devices and not sd0xsNx, so I will give it > another try when I next do a kernel build. FWIW, When I boot on a kernel with DEVFS, but without DEVFS_ROOT, then mount devfs, the all the disk entries show up correctly. Booting on a DEVFS_ROOT kernel still panics though. -john From owner-freebsd-hackers Sat Jan 11 17:53:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA23640 for hackers-outgoing; Sat, 11 Jan 1997 17:53:00 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA23632 for ; Sat, 11 Jan 1997 17:52:55 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id CAA08865; Sun, 12 Jan 1997 02:51:57 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id CAA07238; Sun, 12 Jan 1997 02:42:15 +0100 (MET) Message-ID: Date: Sun, 12 Jan 1997 02:42:14 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: jfieber@indiana.edu (John Fieber) Cc: hackers@FreeBSD.ORG, bde@zeta.org.au (Bruce Evans) Subject: Re: Mounting devfs on /dev References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from John Fieber on Jan 11, 1997 18:31:04 -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As John Fieber wrote: > Hmm... might there be some devfs related changes in current that > are not in RELENG_2_2 (as of several days ago)? Any other > required kernel config options besides DEVFS and DEVFS_ROOT? My Ha!, no, it fails for me either. It only worked on the diskless machine. The partition nodes for the disk are not being created. Only /dev/sd0, /dev/rsd0, and /dev/rsd0.ctl are there, nothing more. Maybe Bruce can give a hint here? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jan 11 17:55:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA23795 for hackers-outgoing; Sat, 11 Jan 1997 17:55:48 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA23780 for ; Sat, 11 Jan 1997 17:55:43 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id CAA08893; Sun, 12 Jan 1997 02:55:04 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id CAA07371; Sun, 12 Jan 1997 02:51:36 +0100 (MET) Message-ID: Date: Sun, 12 Jan 1997 02:51:36 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: davidn@unique.usn.blaze.net.au (David Nugent) Cc: jfieber@indiana.edu (John Fieber), hackers@FreeBSD.ORG Subject: Re: Mounting devfs on /dev References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from David Nugent on Jan 11, 1997 11:57:10 +0000 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As David Nugent wrote: > > ...bpf1 and bpf2 seems to be missing, too. > > And where are the hard disk devices? :-) There was no harddisk. > DEVFS_ROOT works great for netboots though. Yep, that's it! :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jan 11 17:59:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA24001 for hackers-outgoing; Sat, 11 Jan 1997 17:59:10 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA23991 for ; Sat, 11 Jan 1997 17:59:05 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id MAA09841; Sun, 12 Jan 1997 12:28:47 +1030 (CST) From: Michael Smith Message-Id: <199701120158.MAA09841@genesis.atrad.adelaide.edu.au> Subject: Re: Xaccel leaks? In-Reply-To: <199701111620.RAA07885@gilberto.physik.rwth-aachen.de> from Christoph Kukulies at "Jan 11, 97 05:20:04 pm" To: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies) Date: Sun, 12 Jan 1997 12:28:46 +1030 (CST) Cc: freebsd-hackers@freefall.freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Christoph Kukulies stands accused of saying: > > On one of my machines (some older 2.2-current) - where one user has the habit of > leaving many X apps like ghostview/gs standing on for days - top is showing > that Xaccel is now at 11M SIZE (9000K RES). swapinfo shows 37% of 44M swap. > > What could I do about it? Approach Xinside? Rebuild ghostview with another > malloc lib? Run XFree86? Ignore it. An 11M X server (especially if it's running on a 24-bit display) is nothing unusual. Likewise, 44M of swap is really inadequate for that sort of machine. > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Jan 11 18:10:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA24479 for hackers-outgoing; Sat, 11 Jan 1997 18:10:10 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA24474 for ; Sat, 11 Jan 1997 18:10:07 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id VAA09833; Sat, 11 Jan 1997 21:09:57 -0500 (EST) Date: Sat, 11 Jan 1997 21:09:57 -0500 (EST) From: Charles Henrich Message-Id: <199701120209.VAA09833@crh.cl.msu.edu> To: terry@lambert.org, freebsd-hackers@freebsd.org Subject: Re: mount -o async on a news servre Newsgroups: lists.freebsd.hackers References: <5b94ac$2863@msunews.cl.msu.edu> X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In lists.freebsd.hackers you write: >If I were running a big site, I would be tempted to run a reading >host and a *seperate* posting host. >A reading host would be, by definition, a passive news spool with no >locally generated data; I'd run the FS for the news spool in async mode. >Using a seperate server for posting, I could run the posting host >with atime and sync... so my users postings would not be lost because >of a crash. That would be (mostly) useless. News servers spend (as a percentage of time) very little time writing, and massive amounts of time reading. Unless im mistaken, with noatime set, meta data is almost never created, and even then only updated in the case of the scheduled sync() call. Since this can also be pushed back to happen fairly infrequently (I run every 300 seconds, on advice from Joe, and scientific [heh] exploration by myself) it doesnt effect the news spool hardly at all. From my (admittedly almost nonexistant) knowledge of the FS, the only remaining metadata updating going on is on directory creation, which only happens at new newsgroup time (almost never relativly speaking). For performance reasons you would tend to break apart the standard "USER newsreader/poster" operation and "newsfeed" operations, both of which are read/write, both of which have many times the reads as writes. In other words, if you run as suggested back a few lines, there performance loss of running async should be damn close to zero.. -Crh -- Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Sat Jan 11 18:16:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA24717 for hackers-outgoing; Sat, 11 Jan 1997 18:16:25 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA24711 for ; Sat, 11 Jan 1997 18:16:22 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id SAA21682; Sat, 11 Jan 1997 18:12:08 -0800 (PST) Message-ID: <32D8482B.6201DD56@whistle.com> Date: Sat, 11 Jan 1997 18:10:51 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Joerg Wunsch CC: John Fieber , hackers@FreeBSD.ORG Subject: Re: Mounting devfs on /dev References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > 192.168.0.1:/usr/diskless/uncle-root on / > devfs on /dev (local, noexec, read-only) ah that may be the problem... I don't know that this works when the ROOT device is on the local disk.. From owner-freebsd-hackers Sat Jan 11 18:19:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA24806 for hackers-outgoing; Sat, 11 Jan 1997 18:19:02 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA24801 for ; Sat, 11 Jan 1997 18:18:58 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id MAA09886; Sun, 12 Jan 1997 12:47:50 +1030 (CST) From: Michael Smith Message-Id: <199701120217.MAA09886@genesis.atrad.adelaide.edu.au> Subject: Re: unused variable in su In-Reply-To: <199701111939.MAA24005@phaeton.artisoft.com> from Terry Lambert at "Jan 11, 97 12:39:07 pm" To: terry@lambert.org (Terry Lambert) Date: Sun, 12 Jan 1997 12:47:49 +1030 (CST) Cc: joerg_wunsch@uriah.heep.sax.de, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert stands accused of saying: > > Personally, I'd use strdup() istead of an auto buffer to allocate > the buffer at whatever size is necessary... ie: get rid of shellbuf > entirely and replace: > > shell = strcpy(shellbuf, pwd->pw_shell); > with: > shell = strdup( pwd->pw_shell); > > But, hey, that's me, using strdup() for what it was intended to do. You could, however, try reading the code in question, and note that shell is potentially reassigned several times. You would either have to record whether it was pointing at a strdup'd string as opposed to the statically-assigned cpp constant, or you could unconditionally strdup every time and always free it before reassigning. Personally, I think that the original code is the most readable alternative. > Terry Lambert -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Jan 11 18:22:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA24992 for hackers-outgoing; Sat, 11 Jan 1997 18:22:10 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA24987 for ; Sat, 11 Jan 1997 18:22:07 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id DAA09187 for hackers@FreeBSD.ORG; Sun, 12 Jan 1997 03:22:05 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id CAA07495; Sun, 12 Jan 1997 02:56:41 +0100 (MET) Message-ID: Date: Sun, 12 Jan 1997 02:56:41 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: Mounting devfs on /dev References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from John Fieber on Jan 11, 1997 20:22:35 -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As John Fieber wrote: > FWIW, When I boot on a kernel with DEVFS, but without DEVFS_ROOT, > then mount devfs, the all the disk entries show up correctly. Of course. IIRC, Bruce once wrote that the partitions and slices in DEVFS are only initialized after the first open() of that disk. Bummer. That not only prevents DEVFS_ROOT from working, it also defeats the idea to handle the dreaded DEVFS `persistancy' from a script run by the rc(8) shell. :( -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jan 11 18:22:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA25016 for hackers-outgoing; Sat, 11 Jan 1997 18:22:22 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA25009 for ; Sat, 11 Jan 1997 18:22:18 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id DAA09188 for hackers@FreeBSD.org; Sun, 12 Jan 1997 03:22:10 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id CAA07504; Sun, 12 Jan 1997 02:57:30 +0100 (MET) Message-ID: Date: Sun, 12 Jan 1997 02:57:30 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.org Subject: Re: Mounting devfs on /dev References: <97Jan11.162452pst.177476@crevenia.parc.xerox.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <97Jan11.162452pst.177476@crevenia.parc.xerox.com>; from Bill Fenner on Jan 11, 1997 16:24:43 -0700 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Bill Fenner wrote: > >bpf: ppp0 attached > >bpf: ppp1 attached > >bpf: lo0 attached > > > >...bpf1 and bpf2 seems to be missing, too. > > The "bpf: ... attached" messages just mean that that interface has > registered itself with bpf, not that bpf has that number of minor > devices. Ah, yep. That explains it. This machine has only one bpf actually, thanks, Bill! -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jan 11 18:23:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA25075 for hackers-outgoing; Sat, 11 Jan 1997 18:23:55 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA25070 for ; Sat, 11 Jan 1997 18:23:51 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id MAA09898; Sun, 12 Jan 1997 12:53:45 +1030 (CST) From: Michael Smith Message-Id: <199701120223.MAA09898@genesis.atrad.adelaide.edu.au> Subject: Re: Can you install and run FreeBSD on a Iomega Jaz cartridge? In-Reply-To: <01IE3AF7X1G20000GN@ZEUS.ED.RAY.COM> from "Gregory_D_Moncreaff@ccmail.ed.ray.com" at "Jan 11, 97 02:58:00 pm" To: Gregory_D_Moncreaff@ccmail.ed.ray.com Date: Sun, 12 Jan 1997 12:53:44 +1030 (CST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Gregory_D_Moncreaff@ccmail.ed.ray.com stands accused of saying: > Can you install and run FreeBSD on a Iomega Jaz cartridge? With a few caveats, yes. > I was thinking that you might want to have a swap partition on > a local disk, but could all the ufs partitions be on the Jaz? You could swap on the Jaz as well; they perform quite well. > that way you could load the operating system-de-jour cartridge > [dos, win95, winnt, linux, freebsd, ...] > and let the boot manager on the physical boot disk find it... This is where you may have problems; many BIOSsen don't consider the Jaz to be a 'bootable' device, because it reports itself as being a removable. With FreBSD at least, you could put the kernel and the 'fbsdboot.exe' program on a DOS partition and boot that, which will then happily talk to the Jaz. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Jan 11 18:53:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA26587 for hackers-outgoing; Sat, 11 Jan 1997 18:53:05 -0800 (PST) Received: from echonyc.com (echonyc.com [198.67.15.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA26581 for ; Sat, 11 Jan 1997 18:53:00 -0800 (PST) Received: (from benedict@localhost) by echonyc.com (8.8.4/8.8.3) id VAA02375; Sat, 11 Jan 1997 21:52:57 -0500 (EST) Date: Sat, 11 Jan 1997 21:52:56 -0500 (EST) From: Snob Art Genre To: "Frank.A" cc: hackers@freebsd.org Subject: Re: Modem Setup In-Reply-To: <199701102352.SAA01347@mail.inforamp.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 10 Jan 1997, Frank.A wrote: > I am wondering how to go about seting up my modem to dial up and make a PPP > connection with an ISP. This belongs on -questions, not -hackers. > I have a USR 33.6 Internal and at boot up it picks up on com 2 (sio1) > > I have been trying to use minicom to dial up but when I type minicom I get > the message can not open /dev/modem. file missing # cd /dev # ln -s cuaa1 modem In English, that's: change directories to /dev, then create a symbolic link from /dev/modem to /dev/cuaa1. > I do not know exactly what to do. > > Can anyone help me setup my modem to make a PPP connection to an ISP. That's a different issue, perhaps someone more familiar with PPP can help you out. Good luck, and welcome to the FreeBSD fold. > Cheers, > > Frank.A > > Ben From owner-freebsd-hackers Sat Jan 11 19:43:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA28486 for hackers-outgoing; Sat, 11 Jan 1997 19:43:24 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA28463 for ; Sat, 11 Jan 1997 19:42:00 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id TAA23648; Sat, 11 Jan 1997 19:39:03 -0800 (PST) Message-Id: <199701120339.TAA23648@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: proff@suburbia.net cc: hackers@freebsd.org Subject: Re: ipv6 In-reply-to: Your message of "Fri, 10 Jan 1997 15:39:40 +1100." <19970110043940.301.qmail@suburbia.net> From: David Greenman Reply-To: dg@root.com Date: Sat, 11 Jan 1997 19:39:03 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Is anyone actively working on intergrating the nrl code? No, not in its current form. All of the IPv6 implementations fall short, and I doubt that any significant work will occur to merge the good parts of them until after the socket API is standardized. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sat Jan 11 19:52:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA28789 for hackers-outgoing; Sat, 11 Jan 1997 19:52:11 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA28783 for ; Sat, 11 Jan 1997 19:52:06 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id TAA22721; Sat, 11 Jan 1997 19:49:40 -0800 (PST) Message-ID: <32D85F07.52BFA1D7@whistle.com> Date: Sat, 11 Jan 1997 19:48:23 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: John Fieber CC: hackers@freebsd.org Subject: Re: sound driver/devfs change References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John Fieber wrote: > > On Sat, 11 Jan 1997, Julian Elischer wrote: > > > I noticed that you're writing all the tokens to the same place, > > so you can't delete those devices as you've lost their tokens.. > > ...Ah, well, as I said, kernel hacking is rather out of my area, > but I do enjoy learning new things. I think I'm a little over my > head already but haven't drowned quite yet. :) > > Anyway, storing them shouldn't be too difficult; in fact a slight > variation on the original version would do it: use dev->id_unit > instead of unit for the array index. But, what events would > precipitate the removal of an entry? Would there a `snddetach' > companion to sndattach somewhere? well theoretically, unlinking the driver (when we support that) or removing a pc-card device. just because we can't do that yet doesn't mean we shouldn't do "the right thing". > > -john From owner-freebsd-hackers Sat Jan 11 20:10:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA29746 for hackers-outgoing; Sat, 11 Jan 1997 20:10:15 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA29741 for ; Sat, 11 Jan 1997 20:10:13 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id UAA16879; Sat, 11 Jan 1997 20:10:08 -0800 (PST) To: John Fieber cc: hackers@freebsd.org Subject: Re: default permission for audio devices In-reply-to: Your message of "Sat, 11 Jan 1997 13:18:38 EST." Date: Sat, 11 Jan 1997 20:10:08 -0800 Message-ID: <16876.853042208@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk For audio devices, that sounds fairly reasonable, I guess. Depends on whether you think any user should be able to use the sound card or not, I suppose. :-) Jordan From owner-freebsd-hackers Sat Jan 11 20:14:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA29943 for hackers-outgoing; Sat, 11 Jan 1997 20:14:47 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA29938 for ; Sat, 11 Jan 1997 20:14:44 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id UAA16906; Sat, 11 Jan 1997 20:14:30 -0800 (PST) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: hackers@freebsd.org Subject: Re: default permission for audio devices In-reply-to: Your message of "Sat, 11 Jan 1997 20:10:07 +0100." Date: Sat, 11 Jan 1997 20:14:30 -0800 Message-ID: <16902.853042470@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I think DEVFS should create all devices 0600 root:wheel. It's bogus > for the kernel to hard-code user or group names. Everything else > should be handled at rc(8) time, which is also where the beloved > persistency will come into the game. Hmmm. Actually, ignore what I said earlier about group games - I agree with Joerg. :-) Jordan From owner-freebsd-hackers Sat Jan 11 20:18:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA00196 for hackers-outgoing; Sat, 11 Jan 1997 20:18:04 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA00191 for ; Sat, 11 Jan 1997 20:17:59 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id UAA16935; Sat, 11 Jan 1997 20:16:16 -0800 (PST) To: Terry Lambert cc: msmith@atrad.adelaide.edu.au (Michael Smith), jlemon@americantv.com, scrappy@hub.org, hackers@freebsd.org Subject: Re: mount -o async on a news servre In-reply-to: Your message of "Sat, 11 Jan 1997 12:47:49 MST." <199701111947.MAA24041@phaeton.artisoft.com> Date: Sat, 11 Jan 1997 20:16:16 -0800 Message-ID: <16932.853042576@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > ...Just a bizarre thought... Ya took the words right outta my mouth! ;-) Jordan From owner-freebsd-hackers Sat Jan 11 20:28:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA00947 for hackers-outgoing; Sat, 11 Jan 1997 20:28:00 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA00936 for ; Sat, 11 Jan 1997 20:27:58 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.4/8.8.4) with SMTP id XAA00314; Sat, 11 Jan 1997 23:27:56 -0500 (EST) Date: Sat, 11 Jan 1997 23:27:56 -0500 (EST) From: John Fieber To: Julian Elischer cc: hackers@freebsd.org Subject: sound driver/devfs change, round 2 In-Reply-To: <32D85F07.52BFA1D7@whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Okay, I've learn a bit in the last couple hours and the patches below, like the last ones, do work with my soundblaster 16. They now store the devfs tokens and theoretically handle multiple cards. To avoid further confusion with the unusual use of `unit' in the sndattach funcion, I've renamed the old unit variable to voxunit, and the current unit variable is what you expect it to be (dev->id_unit).. I've also changed the default ownership and permission to root.wheel and 0600, respectively, assuming that the "correct" settings will be applied in a startup script. Next question, currently there are unnumbered aliases for unit zero, eg audio -> audio0. Should that also be left to a startup script? -john *** soundcard.c.orig Fri Jan 10 22:56:00 1997 --- soundcard.c Sat Jan 11 23:22:35 1997 *************** *** 323,342 **** sndattach (struct isa_device *dev) { int unit; static int midi_initialized = 0; static int seq_initialized = 0; unsigned long mem_start = 0xefffffffUL; struct address_info hw_config; ! unit = driver_to_voxunit(dev->id_driver); hw_config.io_base = dev->id_iobase; hw_config.irq = ipri_to_irq (dev->id_irq); hw_config.dma = dev->id_drq; hw_config.dma_read = dev->id_flags; /* misuse the flags field for read dma*/ ! if(!unit) return FALSE; ! if (!sndtable_init_card (unit, &hw_config)) { printf (" "); return FALSE; --- 323,345 ---- sndattach (struct isa_device *dev) { int unit; + int minor; + int voxunit; static int midi_initialized = 0; static int seq_initialized = 0; unsigned long mem_start = 0xefffffffUL; struct address_info hw_config; ! unit = dev->id_unit; ! voxunit = driver_to_voxunit(dev->id_driver); hw_config.io_base = dev->id_iobase; hw_config.irq = ipri_to_irq (dev->id_irq); hw_config.dma = dev->id_drq; hw_config.dma_read = dev->id_flags; /* misuse the flags field for read dma*/ ! if(!voxunit) return FALSE; ! if (!sndtable_init_card (voxunit, &hw_config)) { printf (" "); return FALSE; *************** *** 382,435 **** #endif #ifdef DEVFS - /* XXX */ /* find out where to store the tokens.. */ /* XXX */ /* should only create devices if that card has them */ #define SND_UID 0 ! #define SND_GID 13 ! snd_devfs_token[unit]= ! devfs_add_devswf(&snd_cdevsw, (unit << 4)+SND_DEV_CTL, DV_CHR, ! SND_UID, SND_GID, 0660, "mixer%d", unit); #ifndef EXCLUDE_SEQUENCER ! snd_devfs_token[unit]= ! devfs_add_devswf(&snd_cdevsw, (unit << 4)+SND_DEV_SEQ, DV_CHR, ! SND_UID, SND_GID, 0660, "sequencer%d", unit); ! snd_devfs_token[unit]= ! devfs_add_devswf(&snd_cdevsw, (unit << 4)+SND_DEV_SEQ2, DV_CHR, ! SND_UID, SND_GID, 0660, "music%d", unit); #endif #ifndef EXCLUDE_MIDI ! snd_devfs_token[unit]= ! devfs_add_devswf(&snd_cdevsw, (unit << 4)+SND_DEV_MIDIN, ! DV_CHR, SND_UID, SND_GID, 0660, "midi%d", ! unit); #endif #ifndef EXCLUDE_AUDIO ! snd_devfs_token[unit]= ! devfs_add_devswf(&snd_cdevsw, (unit << 4)+SND_DEV_DSP, DV_CHR, ! SND_UID, SND_GID, 0660, "dsp%d", unit); ! snd_devfs_token[unit]= ! devfs_add_devswf(&snd_cdevsw, (unit << 4)+SND_DEV_AUDIO, ! DV_CHR, SND_UID, SND_GID, 0660, "audio%d", ! unit); ! snd_devfs_token[unit]= ! devfs_add_devswf(&snd_cdevsw, (unit << 4)+SND_DEV_DSP16, ! DV_CHR, SND_UID, SND_GID, 0660, "dspW%d", ! unit); ! #endif ! ! snd_devfs_token[unit]= ! devfs_add_devswf(&snd_cdevsw, (unit << 4)+SND_DEV_SNDPROC, ! DV_CHR, SND_UID, SND_GID, 0660, "pss%d", ! unit); ! ! if ( ! sndstat_devfs_token) { ! sndstat_devfs_token = ! devfs_add_devswf(&snd_cdevsw, 6, DV_CHR, SND_UID, SND_GID, ! 0660, "sndstat"); } #endif /* DEVFS */ return TRUE; --- 385,485 ---- #endif #ifdef DEVFS /* XXX */ /* should only create devices if that card has them */ #define SND_UID 0 ! #define SND_GID 0 ! if ( ! sndstat_devfs_token) ! { ! sndstat_devfs_token = ! devfs_add_devswf(&snd_cdevsw, SND_DEV_STATUS, DV_CHR, SND_UID, ! SND_GID, 0600, "sndstat"); ! } ! ! minor = (unit << 4)+SND_DEV_CTL; ! if ( ! snd_devfs_token[minor]) ! { ! snd_devfs_token[minor] = ! devfs_add_devswf(&snd_cdevsw, minor, DV_CHR, SND_UID, ! SND_GID, 0600, "mixer%d", unit); ! if (unit == 0) ! devfs_link(snd_devfs_token[minor], "mixer"); ! } #ifndef EXCLUDE_SEQUENCER ! minor = (unit << 4)+SND_DEV_SEQ; ! if ( ! snd_devfs_token[minor]) ! { ! snd_devfs_token[minor] = ! devfs_add_devswf(&snd_cdevsw, minor, DV_CHR, SND_UID, ! SND_GID, 0600, "sequencer%d", unit); ! if (unit == 0) ! devfs_link(snd_devfs_token[minor], "sequencer"); ! } ! ! minor = (unit << 4)+SND_DEV_SEQ2; ! if ( ! snd_devfs_token[minor]) ! { ! snd_devfs_token[minor] = ! devfs_add_devswf(&snd_cdevsw, minor, DV_CHR, SND_UID, ! SND_GID, 0600, "music%d", unit); ! if (unit == 0) ! devfs_link(snd_devfs_token[minor], "music"); ! } #endif #ifndef EXCLUDE_MIDI ! minor = (unit << 4)+SND_DEV_MIDIN; ! if ( ! snd_devfs_token[minor]) ! { ! snd_devfs_token[minor] = ! devfs_add_devswf(&snd_cdevsw, minor, DV_CHR, SND_UID, ! SND_GID, 0600, "midi%d", unit); ! if (unit == 0) ! devfs_link(snd_devfs_token[minor], "midi"); ! } #endif #ifndef EXCLUDE_AUDIO ! minor = (unit << 4)+SND_DEV_DSP; ! if ( ! snd_devfs_token[minor]) ! { ! snd_devfs_token[minor] = ! devfs_add_devswf(&snd_cdevsw, minor, DV_CHR, SND_UID, ! SND_GID, 0600, "dsp%d", unit); ! if (unit == 0) ! devfs_link(snd_devfs_token[minor], "dsp"); ! } ! ! minor = (unit << 4)+SND_DEV_AUDIO; ! if ( ! snd_devfs_token[minor]) ! { ! snd_devfs_token[minor] = ! devfs_add_devswf(&snd_cdevsw, minor, DV_CHR, SND_UID, ! SND_GID, 0600, "audio%d", unit); ! if (unit == 0) ! devfs_link(snd_devfs_token[minor], "audio"); ! } ! ! minor = (unit << 4)+SND_DEV_DSP16; ! if ( ! snd_devfs_token[minor]) ! { ! snd_devfs_token[minor] = ! devfs_add_devswf(&snd_cdevsw, minor, DV_CHR, SND_UID, ! SND_GID, 0600, "dspW%d", unit); ! if (unit == 0) ! devfs_link(snd_devfs_token[minor], "dspW"); ! } ! #endif ! ! minor = (unit << 4)+SND_DEV_SNDPROC; ! if ( ! snd_devfs_token[minor]) ! { ! snd_devfs_token[minor] = ! devfs_add_devswf(&snd_cdevsw, minor, DV_CHR, SND_UID, ! SND_GID, 0600, "pss%d", unit); ! if (unit == 0) ! devfs_link(snd_devfs_token[minor], "pss"); } #endif /* DEVFS */ return TRUE; From owner-freebsd-hackers Sat Jan 11 20:37:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA01296 for hackers-outgoing; Sat, 11 Jan 1997 20:37:29 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA01291 for ; Sat, 11 Jan 1997 20:37:27 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id UAA17009; Sat, 11 Jan 1997 20:37:23 -0800 (PST) To: Ulf Zimmermann cc: hackers@freebsd.org Subject: Re: XFree86 broken on ftp.cdrom.com In-reply-to: Your message of "Sat, 11 Jan 1997 13:16:18 PST." <3.0.32.19970111131618.00a3aed4@Gatekeeper-3.Lamb.net> Date: Sat, 11 Jan 1997 20:37:22 -0800 Message-ID: <17004.853043842@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I just wanted to download it and the /pub/XFree86/3.2/binaries/FreeBSD-2.2 > are pointing all back to itself. XF8632bin.tgz is the only file I can see > there. > As FreeBSD-current is a link to 2.2 it doesn't work either. Yow, looks like somebody had a little accident in there! :-) I wonder who pulled that one off. Ah well, no biggie. I'm mirroring it over again from ftp.xfree86.org. Thanks! Jordan From owner-freebsd-hackers Sat Jan 11 20:42:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA01512 for hackers-outgoing; Sat, 11 Jan 1997 20:42:09 -0800 (PST) Received: from DNS.Lamb.net (root@DNS.Lamb.net [207.90.181.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA01507 for ; Sat, 11 Jan 1997 20:42:07 -0800 (PST) Received: from PacBell.TelcoSucks.org (ulf@PacBell.TelcoSucks.org [207.90.181.5]) by DNS.Lamb.net (8.8.4/8.8.2) with SMTP id UAA01783; Sat, 11 Jan 1997 20:53:52 -0800 (PST) Message-Id: <3.0.32.19970111204338.00ae2964@Gatekeeper-3.Lamb.net> X-Sender: ulf@Gatekeeper-3.Lamb.net X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sat, 11 Jan 1997 20:43:39 -0800 To: "Jordan K. Hubbard" , Ulf Zimmermann From: Ulf Zimmermann Subject: Re: XFree86 broken on ftp.cdrom.com Cc: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It was Xfree86.org. The other mirrors are broken too. You can get from me faster, I think, if you want. Ulf. At 08:37 PM 1/11/97 -0800, Jordan K. Hubbard wrote: >> I just wanted to download it and the /pub/XFree86/3.2/binaries/FreeBSD-2.2 >> are pointing all back to itself. XF8632bin.tgz is the only file I can see >> there. >> As FreeBSD-current is a link to 2.2 it doesn't work either. > >Yow, looks like somebody had a little accident in there! :-) >I wonder who pulled that one off. Ah well, no biggie. I'm >mirroring it over again from ftp.xfree86.org. Thanks! > > Jordan > > ----------------------------------------------------------- Alameda Networks, Inc. | Ulf Zimmermann (ulf@Alameda.net) 1525 Pacific Avenue | Phone: (510)769-2936 Alameda, CA 94501 | Fax : (510)521-5073 From owner-freebsd-hackers Sat Jan 11 21:10:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA02935 for hackers-outgoing; Sat, 11 Jan 1997 21:10:30 -0800 (PST) Received: from echonyc.com (echonyc.com [198.67.15.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA02912 for ; Sat, 11 Jan 1997 21:10:26 -0800 (PST) Received: (from benedict@localhost) by echonyc.com (8.8.4/8.8.3) id AAA28438; Sun, 12 Jan 1997 00:10:15 -0500 (EST) Date: Sun, 12 Jan 1997 00:10:15 -0500 (EST) From: Snob Art Genre To: Bakul Shah cc: Terry Lambert , Fred Gilham , freebsd-hackers@freebsd.org Subject: Re: A cool xterm? In-Reply-To: <199701102211.RAA13433@chai.plexuscom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 10 Jan 1997, Bakul Shah wrote: > > Also, there should be a way to dump lines to a file (on command) as > well as increase/decrease line buffer size. > The option "-sl n" sets the scrollback buffer to n lines. Ben From owner-freebsd-hackers Sat Jan 11 21:12:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA03264 for hackers-outgoing; Sat, 11 Jan 1997 21:12:02 -0800 (PST) Received: from echonyc.com (echonyc.com [198.67.15.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA03241 for ; Sat, 11 Jan 1997 21:11:57 -0800 (PST) Received: (from benedict@localhost) by echonyc.com (8.8.4/8.8.3) id AAA28185; Sun, 12 Jan 1997 00:08:27 -0500 (EST) Date: Sun, 12 Jan 1997 00:08:27 -0500 (EST) From: Snob Art Genre To: Terry Lambert cc: Fred Gilham , freebsd-hackers@freebsd.org Subject: Re: A cool xterm? In-Reply-To: <199701102014.NAA20438@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 10 Jan 1997, Terry Lambert wrote: > It's ugly, it fails the page up/down in the thumb area, it does not > have a single-step up/down button, and it takes too many buttons > on your mouse to make it work efficiently. > > Other than that, there's no problem with it. It would also be very nice if I could use a key or combination of keys to turn scrollbar mode on, use the arrows to scroll up and down, and hit another key to go back to the active window. Does anyone know if this is currently possible, or if not, how I can set it up? Signed, one who hates switching from keyboard to mouse and back. (P.S. Keyboard-based cut and paste would be a real win too.) > > Regards, > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > Ben From owner-freebsd-hackers Sat Jan 11 22:32:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA12798 for hackers-outgoing; Sat, 11 Jan 1997 22:32:33 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA12791 for ; Sat, 11 Jan 1997 22:32:28 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id RAA28317; Sun, 12 Jan 1997 17:29:03 +1100 Date: Sun, 12 Jan 1997 17:29:03 +1100 From: Bruce Evans Message-Id: <199701120629.RAA28317@godzilla.zeta.org.au> To: jfieber@indiana.edu, julian@whistle.com Subject: Re: sound driver/devfs change, round 2 Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Next question, currently there are unnumbered aliases for unit >zero, eg audio -> audio0. Should that also be left to a startup >script? Probably. The aliases are only for confus^H^H^Hvenience. If you keep them, then they should have tokens. > #ifdef DEVFS > /* XXX */ /* should only create devices if that card has them */ > #define SND_UID 0 >! #define SND_GID 0 These 0's are still magic. They should be spelled as UID_ROOT and GID_WHEEL. Bruce From owner-freebsd-hackers Sat Jan 11 23:14:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA13958 for hackers-outgoing; Sat, 11 Jan 1997 23:14:00 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA13941 for ; Sat, 11 Jan 1997 23:13:52 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id SAA29440; Sun, 12 Jan 1997 18:07:37 +1100 Date: Sun, 12 Jan 1997 18:07:37 +1100 From: Bruce Evans Message-Id: <199701120707.SAA29440@godzilla.zeta.org.au> To: j@uriah.heep.sax.de, jfieber@indiana.edu Subject: Re: Mounting devfs on /dev Cc: bde@zeta.org.au, hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >The partition nodes for the disk are not being created. Only >/dev/sd0, /dev/rsd0, and /dev/rsd0.ctl are there, nothing more. They aren't created until the disk is opened. mountroot() should open the root device without looking it up. Other disks can easily be opened in /etc/rc using something `disklabel /dev/null'. Bruce From owner-freebsd-hackers Sat Jan 11 23:16:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA14062 for hackers-outgoing; Sat, 11 Jan 1997 23:16:46 -0800 (PST) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA14051 for ; Sat, 11 Jan 1997 23:16:40 -0800 (PST) Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) with ESMTP id XAA12014; Sat, 11 Jan 1997 23:16:25 -0800 (PST) From: Josh MacDonald Message-Id: <199701120716.XAA12014@paris.CS.Berkeley.EDU> To: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= Cc: freebsd-hackers@freebsd.org Subject: Re: Recent bsd.info.mk commit breaks SRCDIR, please merge properly! In-reply-to: Your message of "Sat, 11 Jan 1997 18:35:20 +0300." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <12007.853053358.1@paris.CS.Berkeley.EDU> Date: Sat, 11 Jan 1997 23:16:01 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Could you please clarify? -josh > Joshua, among SRCDIR method brokennes, you broke INFO* macros usage too. > Don't do blind commits, please! > I expect this things will be restored. > > -- > Andrey A. Chernov > > http://www.nagual.ru/~ache/ > From owner-freebsd-hackers Sat Jan 11 23:26:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA14386 for hackers-outgoing; Sat, 11 Jan 1997 23:26:21 -0800 (PST) Received: from agni.nuko.com ([207.82.229.31]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA14369; Sat, 11 Jan 1997 23:26:17 -0800 (PST) Received: (from vinay@localhost) by agni.nuko.com (8.7.5/8.6.12) id XAA09359; Sat, 11 Jan 1997 23:26:02 -0800 (PST) From: Vinay Kumar Message-Id: <199701120726.XAA09359@agni.nuko.com> Subject: Help with Soundblaster card To: freebsd-hackers@freebsd.org, freebsd-multimedia@freebsd.org Date: Sat, 11 Jan 1997 23:26:02 -0800 (PST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi folks, I am trying to set up the Mbone tools on my freebsd machine and am having trouble getting my soundcard to work (I know I should get Gravis, but I can't right now!!). I am running 2.1.5, Pentium 120Mhz, 32Mb ram. Here is the description of my sound card from the dmesg command: sb0 at 0x220 irq 7 drq 1 on isa sb0: sbxvi0 at 0x0 drq 5 on isa sbxvo0: sbmidi0 at 0x330 on isa After the system comes up, I can cat audio files (au type) to /dev/audio and it plays for a second or so and then hangs. I can ctrl-c and cat again, but only for a second. Seems like a buffer problem. I don't know where to start looking. Any help would be appreciated... Thanks Vinay -- Vinay Bannai E-mail: vinay@agni.nuko.com (408)-526-0280 x 275 (Work) http://agni.nuko.com/~vinay From owner-freebsd-hackers Sat Jan 11 23:35:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA14786 for hackers-outgoing; Sat, 11 Jan 1997 23:35:55 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA14779 for ; Sat, 11 Jan 1997 23:35:48 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id SAA30033; Sun, 12 Jan 1997 18:33:23 +1100 Date: Sun, 12 Jan 1997 18:33:23 +1100 From: Bruce Evans Message-Id: <199701120733.SAA30033@godzilla.zeta.org.au> To: bde@zeta.org.au, j@uriah.heep.sax.de, jfieber@indiana.edu Subject: Re: Mounting devfs on /dev Cc: hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>The partition nodes for the disk are not being created. Only >>/dev/sd0, /dev/rsd0, and /dev/rsd0.ctl are there, nothing more. I wrote: >They aren't created until the disk is opened. mountroot() should >open the root device without looking it up. Other disks can easily >be opened in /etc/rc using something `disklabel /dev/null'. Oops, they seem to be broken now for a non-root devfs. The partitions on my zip disk /dev/sd1 aren't created when /dev/sd1 is looked at in various ways, and unmounting devfs hangs all disk i/o after a while. (At first only the unmount process seemed to be hung - ps was able to run and should the process hanging on vgone. Now ps in ddb show that many processes are hanging on ufslk2. I thought that this problem was fixed.) Bruce