From owner-freebsd-hackers Sun Dec 22 01:42:12 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA24991 for hackers-outgoing; Sun, 22 Dec 1996 01:42:12 -0800 (PST) Received: from mailnews.kub.nl (mailnews.kub.nl [137.56.0.220]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA24986; Sun, 22 Dec 1996 01:41:59 -0800 (PST) Received: from tomcat.kub.nl (slip156.kub.nl [192.87.170.156]) by mailnews.kub.nl (8.8.4/8.7.1) with ESMTP id KAA11898; Sun, 22 Dec 1996 10:41:54 +0100 (MET) Received: (from s799637@localhost) by tomcat.kub.nl (8.8.4/8.6.12) id KAA01668; Sun, 22 Dec 1996 10:41:33 +0100 (MET) Message-Id: <199612220941.KAA01668@tomcat.kub.nl> Subject: Kernel rebuild quits at param.c:82 To: hackers@freebsd.org, freebsd-stable@freebsd.org Date: Sun, 22 Dec 1996 10:41:33 +0100 (MET) From: A.H.A.M.Boer@kub.nl (Arnout Boer) Reply-To: A.H.A.M.Boer@kub.nl X-Operating-System: FreeBSD 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 Hi, With different versions of the stable tree and even with the 2.2-RELEASE tree rebuilding a kernel stops with: param.c:82 `TIMEZONE' undeclared here (not in a function) param.c:82 initializer element for `tz.tz_minutes_west' is not constant param.c:82 `DST' undeclared here (not in a function) param.c:82 initializer element for `tz.tz_dsttime' is not constant *** Error code 1 Stop. My machine is a iPentium 133 with 32 mb ram, a Adaptec 2940U controller with a couple of disks and a cdrom player, an ASUS P55T2P4c motherboard. I hope you can help me out. Arnout Boer p.s. I hope you can e-mail reactions to me or cc them cause I am not subscribed to the hackerslist momentarily ************************************************************* Arnout Boer * s799637@kub.nl * arnout@tref.nl ************************************************************* From owner-freebsd-hackers Sun Dec 22 03:01:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA28155 for hackers-outgoing; Sun, 22 Dec 1996 03:01: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 DAA28150 for ; Sun, 22 Dec 1996 03:01:52 -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 MAA10378; Sun, 22 Dec 1996 12:01:51 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA22907; Sun, 22 Dec 1996 12:01:50 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id LAA13258; Sun, 22 Dec 1996 11:56:57 +0100 (MET) From: J Wunsch Message-Id: <199612221056.LAA13258@uriah.heep.sax.de> Subject: Re: Kernel rebuild quits at param.c:82 To: A.H.A.M.Boer@kub.nl Date: Sun, 22 Dec 1996 11:56:57 +0100 (MET) Cc: hackers@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612220941.KAA01668@tomcat.kub.nl> from Arnout Boer at "Dec 22, 96 10:41:33 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 Arnout Boer wrote: > param.c:82 `TIMEZONE' undeclared here (not in a function) > param.c:82 initializer element for `tz.tz_minutes_west' is not constant > param.c:82 `DST' undeclared here (not in a function) > param.c:82 initializer element for `tz.tz_dsttime' is not constant > *** Error code 1 Your config and kernel source seem to be in heavy disagreement. The last traces of the timezone stuff have been removed from the kernel ages ago. Make sure to build your kernel from consistent sources, rebuild and reinstall config(8) first, and re-run it on you config file. -- 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 Sun Dec 22 07:51:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA08210 for hackers-outgoing; Sun, 22 Dec 1996 07:51:30 -0800 (PST) Received: from deere-bh.dx.deere.com (deere-bh.dx.deere.com [207.122.201.66]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA08204 for ; Sun, 22 Dec 1996 07:51:27 -0800 (PST) Received: (from uucp@localhost) by deere-bh.dx.deere.com (8.6.12/8.6.11) id JAA08798 for ; Sun, 22 Dec 1996 09:51:49 -0600 Received: from deere.dx.deere.com by deere-bh.dx.deere.com via smap (V1.3) id sma008791; Sun Dec 22 09:51:46 1996 Received: from 90.deere.com (dts.90.deere.com) by deere.dx.deere.com (4.1/SMI-4.0) id AA26264; Sun, 22 Dec 96 09:51:15 CST Received: from bc17684.deere.com by 90.deere.com (SMI-8.6/SMI-SVR4) id JAA27458; Sun, 22 Dec 1996 09:49:29 -0600 Message-Id: <32BD4F13.12B8@90.deere.com> Date: Sun, 22 Dec 1996 09:09:07 -0600 From: Bertrum Carroll Organization: Deere & Company X-Mailer: Mozilla 2.01Gold (Win95; I) Mime-Version: 1.0 To: hackers@FreeBSD.org Subject: How to join Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk How do I join this list? bc17684@90.deere.com From owner-freebsd-hackers Sun Dec 22 08:12:52 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA09181 for hackers-outgoing; Sun, 22 Dec 1996 08:12:52 -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 IAA09176 for ; Sun, 22 Dec 1996 08:12:49 -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 IAA17027; Sun, 22 Dec 1996 08:12:42 -0800 (PST) To: Nate Williams cc: dkelly@hiwaay.net, hackers@freebsd.org Subject: Re: Posting to multiple lists In-reply-to: Your message of "Sat, 21 Dec 1996 22:11:43 MST." <199612220511.WAA29323@rocky.mt.sri.com> Date: Sun, 22 Dec 1996 08:12:41 -0800 Message-ID: <17023.851271161@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I've been using procmail for at least 3 years and it has *always* > worked. However, Jordan has never gotten it working so I don't know > what's different between his setup and mine. Oh, I've gotten it to work - I've just never gotten it to stay working. :-) After a few days of perfect operation, the thing starts catching sig 11's and bouncing mail on me. :( Jordan From owner-freebsd-hackers Sun Dec 22 08:34:25 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA09890 for hackers-outgoing; Sun, 22 Dec 1996 08:34:25 -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 IAA09885 for ; Sun, 22 Dec 1996 08:34:22 -0800 (PST) Received: from PacBell.TelcoSucks.org (ulf@msn-42.hl-1.msn.eunet.de [194.175.90.42]) by DNS.Lamb.net (8.8.3/8.8.2) with SMTP id IAA02155; Sun, 22 Dec 1996 08:38:27 -0800 (PST) Message-Id: <3.0.32.19961222083103.006f2964@Gatekeeper-3.Lamb.net> X-Sender: ulf@Gatekeeper-3.Lamb.net X-Mailer: Windows Eudora Pro Version 3.0 Demo (32) Date: Sun, 22 Dec 1996 08:35:27 -0800 To: Bertrum Carroll , hackers@FreeBSD.org From: Ulf Zimmermann Subject: Re: How to join Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk At 09:09 AM 12/22/96 -0600, Bertrum Carroll wrote: >How do I join this list? > >bc17684@90.deere.com > > Send email to majordomo@freebsd.org. Put "help" into the message body. 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 Sun Dec 22 08:34:37 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA09915 for hackers-outgoing; Sun, 22 Dec 1996 08:34: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 IAA09906 for ; Sun, 22 Dec 1996 08:34:34 -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 LAA17088; Sun, 22 Dec 1996 11:34:32 -0500 (EST) Received: from localhost (chuckr@localhost) by ginger.eng.umd.edu (8.8.3/8.7.3) with SMTP id LAA26365; Sun, 22 Dec 1996 11:34:31 -0500 (EST) X-Authentication-Warning: ginger.eng.umd.edu: chuckr owned process doing -bs Date: Sun, 22 Dec 1996 11:34:31 -0500 (EST) From: Chuck Robey X-Sender: chuckr@ginger.eng.umd.edu To: Bertrum Carroll cc: hackers@FreeBSD.org Subject: Re: How to join In-Reply-To: <32BD4F13.12B8@90.deere.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, 22 Dec 1996, Bertrum Carroll wrote: > How do I join this list? You want to tell the list controller, which is a program called majordomo, to add you to the list. To do this, send mail to majordomo@FreeBSD.org, with a single line body: subscribe Majordomo doesn't read the subject line at all. Majordomo also has a very nice writeup available which it will mail to you if you confuse it ... just leave your .sig in place, that should do it. It will tell you how to look at other lists, and other possible commands. > > bc17684@90.deere.com > > > ----------------------------+----------------------------------------------- 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 Dec 22 08:46:40 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA10377 for hackers-outgoing; Sun, 22 Dec 1996 08:46:40 -0800 (PST) Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA10372 for ; Sun, 22 Dec 1996 08:46:37 -0800 (PST) Received: from freebie.lemis.de by diablo.ppp.de with smtp (Smail3.1.28.1 #1) id m0vbr2S-000QYYC; Sun, 22 Dec 96 17:46 MET Received: (grog@localhost) by freebie.lemis.de (8.8.4/8.6.12) id QAA00445; Sun, 22 Dec 1996 16:50:27 +0100 (MET) From: grog@lemis.de Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Message-Id: <199612221550.QAA00445@freebie.lemis.de> Subject: Re: 3com 3c589b pcmcia support? In-Reply-To: <199612210533.WAA25762@rocky.mt.sri.com> from Nate Williams at "Dec 20, 96 10:33:14 pm" To: nate@mt.sri.com (Nate Williams) Date: Sun, 22 Dec 1996 16:50:27 +0100 (MET) Cc: rmallory@sunbeam.csusb.edu, hackers@freebsd.org (FreeBSD Hackers) 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 Nate Williams writes: >> >> I have a 3c589c-TP, and the default GENERIC kernel finds it, ifconfigs >> it up, and appears to work (I get a link light on the hub at that >> point). > > Try messing with the link flags. Usually appending '-link0 link1' *OR* > 'link0 -link1' works. Specifically, "-link0 link1" selects the BNC port, and "link0 -link1" sets the UTP port. Greg From owner-freebsd-hackers Sun Dec 22 08:59:01 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA11054 for hackers-outgoing; Sun, 22 Dec 1996 08:59:01 -0800 (PST) Received: (from jmb@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA11045; Sun, 22 Dec 1996 08:58:56 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199612221658.IAA11045@freefall.freebsd.org> Subject: Re: How to join To: chuckr@glue.umd.edu (Chuck Robey) Date: Sun, 22 Dec 1996 08:58:56 -0800 (PST) Cc: bc17684@90.deere.com, hackers@FreeBSD.org In-Reply-To: from "Chuck Robey" at Dec 22, 96 11:34:31 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Chuck Robey wrote: > > On Sun, 22 Dec 1996, Bertrum Carroll wrote: > > > How do I join this list? > > You want to tell the list controller, which is a program called majordomo, > to add you to the list. To do this, send mail to majordomo@FreeBSD.org, > with a single line body: > > subscribe uhhh...the line above should read subscribe for example subscribe freebsd-hackers bc17684@90.deere.com jmb -- Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG FreeBSD--4.4BSD Unix for PC clones, source included. http://www.freebsd.org/ PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB From owner-freebsd-hackers Sun Dec 22 09:04:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA11382 for hackers-outgoing; Sun, 22 Dec 1996 09:04:20 -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 JAA11375 for ; Sun, 22 Dec 1996 09:04:18 -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 MAA17429; Sun, 22 Dec 1996 12:04:15 -0500 (EST) Received: from localhost (chuckr@localhost) by ginger.eng.umd.edu (8.8.3/8.7.3) with SMTP id MAA27311; Sun, 22 Dec 1996 12:04:15 -0500 (EST) X-Authentication-Warning: ginger.eng.umd.edu: chuckr owned process doing -bs Date: Sun, 22 Dec 1996 12:04:14 -0500 (EST) From: Chuck Robey X-Sender: chuckr@ginger.eng.umd.edu To: "Jonathan M. Bresler" cc: bc17684@90.deere.com, hackers@FreeBSD.org Subject: Re: How to join In-Reply-To: <199612221658.IAA11045@freefall.freebsd.org> 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, 22 Dec 1996, Jonathan M. Bresler wrote: > Chuck Robey wrote: > > > > On Sun, 22 Dec 1996, Bertrum Carroll wrote: > > > > > How do I join this list? > > > > You want to tell the list controller, which is a program called majordomo, > > to add you to the list. To do this, send mail to majordomo@FreeBSD.org, > > with a single line body: > > > > subscribe > > uhhh...the line above should read > > subscribe > > for example > > subscribe freebsd-hackers bc17684@90.deere.com oops .. > jmb > -- > Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG > FreeBSD--4.4BSD Unix for PC clones, source included. http://www.freebsd.org/ > PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB > ----------------------------+----------------------------------------------- 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 Dec 22 09:16:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA12190 for hackers-outgoing; Sun, 22 Dec 1996 09:16:06 -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 JAA12183 for ; Sun, 22 Dec 1996 09:16:02 -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 SAA16735 for ; Sun, 22 Dec 1996 18:16:36 +0100 (MET) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.3/8.6.9) id SAA11327 for freebsd-hackers@freefall.cdrom.com; Sun, 22 Dec 1996 18:29:03 +0100 (MET) Date: Sun, 22 Dec 1996 18:29:03 +0100 (MET) From: Christoph Kukulies Message-Id: <199612221729.SAA11327@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: /usr/share/skel - make world writes into it Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Every time I'm building a world on one of my machines it clobbers the dotfiles in /usr/share/skel which are shared in our NIS/YP environment. Each of the 10 PCs mounts /usr/share -root=0 from our NFS/NIS server. When I build world on one of the clients which happens to be a PPRO and makes world building a fun otherwise. Could this be changed in that make world leaves the existing files there untouched. Or is there another way to protect an individual setup? --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Sun Dec 22 09:39:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA13610 for hackers-outgoing; Sun, 22 Dec 1996 09:39:04 -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 JAA13605 for ; Sun, 22 Dec 1996 09:39:00 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id MAA07076; Sun, 22 Dec 1996 12:38:25 -0500 (EST) From: "John S. Dyson" Message-Id: <199612221738.MAA07076@dyson.iquest.net> Subject: Re: Kernel rebuild quits at param.c:82 To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 22 Dec 1996 12:38:25 -0500 (EST) Cc: A.H.A.M.Boer@kub.nl, hackers@freebsd.org In-Reply-To: <199612221056.LAA13258@uriah.heep.sax.de> from "J Wunsch" at Dec 22, 96 11:56:57 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 > As Arnout Boer wrote: > > > param.c:82 `TIMEZONE' undeclared here (not in a function) > > param.c:82 initializer element for `tz.tz_minutes_west' is not constant > > param.c:82 `DST' undeclared here (not in a function) > > param.c:82 initializer element for `tz.tz_dsttime' is not constant > > *** Error code 1 > > Your config and kernel source seem to be in heavy disagreement. The > last traces of the timezone stuff have been removed from the kernel > ages ago. Make sure to build your kernel from consistent sources, > rebuild and reinstall config(8) first, and re-run it on you config > file. > Once, long ago, a group of us had a disagreement that the config sources should be part of the kernel tree (which I champion.) Maybe this should be revisited -- since the config program *does* have to have intimate knowedge of and actually *does* produce kernel code (like genassym.) Mess-ups associated with bogus versions of config have a possibility of being controlled then. John From owner-freebsd-hackers Sun Dec 22 10:58:54 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA15871 for hackers-outgoing; Sun, 22 Dec 1996 10:58:54 -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 KAA15865 for ; Sun, 22 Dec 1996 10:58:50 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id TAA00122 for ; Sun, 22 Dec 1996 19:58:43 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id TAA15257 for hackers@freebsd.org; Sun, 22 Dec 1996 19:58:15 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.4/keltia-uucp-2.9) id TAA20391; Sun, 22 Dec 1996 19:50:59 +0100 (CET) Message-ID: Date: Sun, 22 Dec 1996 19:50:59 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: hackers@freebsd.org Subject: Re: Posting to multiple lists References: <199612220511.WAA29323@rocky.mt.sri.com> <17023.851271161@time.cdrom.com> X-Mailer: Mutt 0.55.04 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2837 In-Reply-To: <17023.851271161@time.cdrom.com>; from Jordan K. Hubbard on Dec 22, 1996 08:12:41 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Jordan K. Hubbard: > Oh, I've gotten it to work - I've just never gotten it to stay > working. :-) After a few days of perfect operation, the thing starts > catching sig 11's and bouncing mail on me. :( I'm sure that's because you insisted to run 3.10. 3.11pre{3,4} have *never* dumped core on me for two years of constant use. 3.11pre4 is the latest ever made and is very stable. -- 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 Dec 22 12:03:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA17643 for hackers-outgoing; Sun, 22 Dec 1996 12:03:55 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA17637 for ; Sun, 22 Dec 1996 12:03:53 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA01294; Sun, 22 Dec 1996 13:03:50 -0700 (MST) Date: Sun, 22 Dec 1996 13:03:50 -0700 (MST) Message-Id: <199612222003.NAA01294@rocky.mt.sri.com> From: Nate Williams To: Greg Lehey Cc: nate@mt.sri.com (Nate Williams), rmallory@sunbeam.csusb.edu, hackers@freebsd.org (FreeBSD Hackers) Subject: Re: 3com 3c589b pcmcia support? In-Reply-To: <199612221550.QAA00445@freebie.lemis.de> References: <199612210533.WAA25762@rocky.mt.sri.com> <199612221550.QAA00445@freebie.lemis.de> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> I have a 3c589c-TP, and the default GENERIC kernel finds it, ifconfigs > >> it up, and appears to work (I get a link light on the hub at that > >> point). > > > > Try messing with the link flags. Usually appending '-link0 link1' *OR* > > 'link0 -link1' works. > > Specifically, "-link0 link1" selects the BNC port, and "link0 -link1" > sets the UTP port. Actually, it depends on which model and what the built-in settings are. My two cards behave exactly opposite of one another with the link flags. Nate From owner-freebsd-hackers Sun Dec 22 12:13:50 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA17993 for hackers-outgoing; Sun, 22 Dec 1996 12:13:50 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA17987 for ; Sun, 22 Dec 1996 12:13:47 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA01347; Sun, 22 Dec 1996 13:12:51 -0700 (MST) Date: Sun, 22 Dec 1996 13:12:51 -0700 (MST) Message-Id: <199612222012.NAA01347@rocky.mt.sri.com> From: Nate Williams To: "John S. Dyson" Cc: joerg_wunsch@uriah.heep.sax.de, hackers@freebsd.org Subject: config(8) moved to /usr/src/sys (was Re: Kernel rebuild quits ..) In-Reply-To: <199612221738.MAA07076@dyson.iquest.net> References: <199612221056.LAA13258@uriah.heep.sax.de> <199612221738.MAA07076@dyson.iquest.net> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John S. Dyson writes: > Once, long ago, a group of us had a disagreement that the config > sources should be part of the kernel tree (which I champion.) Maybe > this should be revisited -- since the config program *does* have > to have intimate knowedge of and actually *does* produce kernel > code (like genassym.) Mess-ups associated with bogus versions of > config have a possibility of being controlled then. I'm with you John! Go for it! Nate From owner-freebsd-hackers Sun Dec 22 12:14:27 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA18044 for hackers-outgoing; Sun, 22 Dec 1996 12:14:27 -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 MAA18026 for ; Sun, 22 Dec 1996 12:14:09 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id HAA03618 for hackers@freebsd.org; Mon, 23 Dec 1996 07:13:50 +1100 (EST) From: Julian Assange Message-Id: <199612222013.HAA03618@profane.iq.org> Subject: ipretard.c selective tcp/ip queues and throughput limiters To: hackers@freebsd.org Date: Mon, 23 Dec 1996 07:13:49 +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 From owner-freebsd-hackers Sun Dec 22 14:21:23 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA22346 for hackers-outgoing; Sun, 22 Dec 1996 14:21:23 -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 OAA22339 for ; Sun, 22 Dec 1996 14:21: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 XAA28845; Sun, 22 Dec 1996 23:21:07 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA03666; Sun, 22 Dec 1996 23:21:06 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id XAA15967; Sun, 22 Dec 1996 23:12:08 +0100 (MET) From: J Wunsch Message-Id: <199612222212.XAA15967@uriah.heep.sax.de> Subject: Re: /usr/share/skel - make world writes into it To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Sun, 22 Dec 1996 23:12:08 +0100 (MET) Cc: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612221729.SAA11327@gilberto.physik.rwth-aachen.de> from Christoph Kukulies at "Dec 22, 96 06:29:03 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 Christoph Kukulies wrote: > Every time I'm building a world on one of my machines it clobbers > the dotfiles in /usr/share/skel which are shared in our NIS/YP > environment. I think we've been there before. Customized skeleton files are supposed to be created e.g. under /etc/skel/. Since you can configure adduser(8) and pw(8) to pick them up there, this should basically be no big deal, though you might run into problems sharing them across NFS. -- 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 Sun Dec 22 19:04:46 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA06811 for hackers-outgoing; Sun, 22 Dec 1996 19:04:46 -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 TAA06806 for ; Sun, 22 Dec 1996 19:04:44 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id NAA15799 for hackers@freebsd.org; Mon, 23 Dec 1996 13:34:41 +1030 (CST) From: Michael Smith Message-Id: <199612230304.NAA15799@genesis.atrad.adelaide.edu.au> Subject: what happenedto src/release/*? To: hackers@freebsd.org Date: Mon, 23 Dec 1996 13:34:40 +1030 (CST) 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 just cvsupped, and all of src/release was deleted. I understans that there's a new distribution collection, src-release, but I have that in my cvsupfile. Have I just fallen in a crack, or is there a real problem? (cvsup.au.freebsd.org, BTW.) -- ]] 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 Dec 22 19:21:43 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA07464 for hackers-outgoing; Sun, 22 Dec 1996 19:21:43 -0800 (PST) Received: from nlanr.net (oceana.sdsc.edu [132.249.40.200]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA07455 for ; Sun, 22 Dec 1996 19:21:40 -0800 (PST) Received: (from tony@localhost) by nlanr.net (8.7.3/8.7.3) id TAA20487 for hackers@freebsd.org; Sun, 22 Dec 1996 19:21:39 -0800 (PST) From: Tony Sterrett Message-Id: <199612230321.TAA20487@nlanr.net> Subject: Partition type number To: hackers@freebsd.org Date: Sun, 22 Dec 1996 19:21:39 -0800 (PST) X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Does anyone know the partition type number for win95 (dos partition)? Thanks in advance Tony From owner-freebsd-hackers Sun Dec 22 20:21:07 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA14707 for hackers-outgoing; Sun, 22 Dec 1996 20:21:07 -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 UAA14694 for ; Sun, 22 Dec 1996 20:20:41 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id PAA03748; Mon, 23 Dec 1996 15:19:42 +1100 (EST) From: Julian Assange Message-Id: <199612230419.PAA03748@profane.iq.org> Subject: Re: ipretard.c selective tcp/ip queues and throughput limiters In-Reply-To: from Daniel O'Callaghan at "Dec 23, 96 09:16:35 am" To: danny@panda.hilink.com.au (Daniel O'Callaghan) Date: Mon, 23 Dec 1996 15:19:42 +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 Written this morning. If people find it useful, I'll polish it. example: # ipfw add divert 92 tcp from any to any 80 out via ed0 # ./ipretard -v -t 1000/300 -w 2208 /* ipretard (c) 1996 Julian Assange (proff@suburbia.net) All Rights Reserved */ #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include #define MAX_IP (65535+100) #define MAX_PACKET (MAX_IP+sizeof(struct packet)-1) struct packet { struct packet *next, *prev; time_t time; int len; struct sockaddr_in in; char data[1]; }; int holdoff_write=0; int holdoffs=0; int delay_drops=0; int window_changes=0; int bytes_in=0; int bytes_out=0; int add_bytes_out=0; int packets_in=0; int packets_out=0; int packets_queued=0; int bytes_queued=0; double samples=60.0*5.0; /* 5 minute period */ double max_thru=0.0; double load_avg; time_t ti; int verbose=0; void sigalrm(int i) { if (max_thru!=0.0) { load_avg=load_avg*(1.0-1.0/samples)+add_bytes_out/samples; if (load_avg>max_thru) { holdoff_write = 1; holdoffs++; } else holdoff_write = 0; } bytes_out+=add_bytes_out; add_bytes_out=0; if (verbose) printf("in: %d/%d %d avg out: %d/%d %d avg queued: %d/%d drop: %d win_change: %d holdoffs: %d loadavg %.2f\n", bytes_in, packets_in, packets_in? bytes_in/packets_in: 0, bytes_out, packets_out, packets_out? bytes_out/packets_out: 0, bytes_queued, packets_queued, delay_drops, window_changes, holdoffs, load_avg); ti=time(NULL); #ifdef POSIX signal(SIGALRM, sigalrm); #endif alarm(1); } u_short fast_ip_gen_check(struct ip *ip) /* well, for C anyway.. */ { register u_short *u = (u_short *)ip; register int sum = 0; u_char hl = ip->ip_hl * 4; sum += *u++; sum += *u++; sum += *u++; sum += *u++; sum += *u++; u++; /* skip checksum */ sum += *u++; sum += *u++; sum += *u++; sum += *u++; if (hl != sizeof (*ip)) for (hl = (hl - sizeof (*ip)) / 2; hl--;) sum += *u++; sum = (sum >> 16) + (sum & 0xffff); /* fold carries */ return (u_short) ~sum; } u_short fast_tcp_gen_check(struct ip *ip) /* well, for C anyway.. */ { register u_short *u; register int sum = 0; u_short len = ntohs(ip->ip_len) - ip->ip_hl * 4; u_char resprot[2] = {0, IPPROTO_TCP}; u = (u_short *) &ip->ip_src; sum += *u++; sum += *u++; sum += *u++; sum += *u++; sum += *(u_short *) resprot; sum += htons(len); u = (u_short *) ((char*)ip + ip->ip_hl * 4); sum += *u++; sum += *u++; sum += *u++; sum += *u++; sum += *u++; sum += *u++; sum += *u++; sum += *u++; u++; /* skip th_sum */ sum += *u++; if (!(len -= sizeof (struct tcphdr))) goto plainhdr; for (; len > 15; len -= 16) { sum += *u++; sum += *u++; sum += *u++; sum += *u++; sum += *u++; sum += *u++; sum += *u++; sum += *u++; } for (; len > 1; len -= 2) sum += *u++; if (len == 1) sum += *(u_char *) u; plainhdr: sum = (sum >> 16) + (sum & 0xffff); /* fold carries */ len = ~sum; return len; } void usage(char *av0) { fprintf(stderr, "usage: %s [-b ring_buf_len][-d max_packet_delay][-p divert_port][-t max_throughput_per_sec/sample_period][-v][-w max_window]\n", av0); exit(1); } int main(int argc, char **argv) { int c; int fd; int div_port=92; int buf_len=256*1024; /* 256k */ struct sockaddr_in in; fd_set fdr_set, fdw_set; int max_window=0; int max_ring_delay=5; struct packet *pq_base, *pq_head=NULL, *pq_tail; while ((c=getopt(argc, argv, "b:d:p:t:vw:"))!=-1) switch(c) { case 'b': buf_len=atoi(optarg); if (buf_lendata, MAX_IP, 0, (struct sockaddr*)&pq_tail->in, &in_len))>0) { struct packet *pq; pq_tail->len=cc; pq_tail->time=ti; bytes_queued+=sizeof(struct packet)-1+cc; bytes_in+=cc; if ((pq=(char*)pq_tail+sizeof(struct packet)-1+cc)+MAX_PACKET>(char *)pq_base+buf_len) pq=pq_base; if (!pq_head) pq_head=pq_tail; if (pq_tail->prev) pq_tail->prev->next=pq_tail; pq->next=NULL; pq->prev=pq_tail; pq_tail=pq; packets_queued++; packets_in++; } } if (packets_queued && FD_ISSET(fd, &fdw_set)) { if (ti-pq_head->time > max_ring_delay) { delay_drops++; goto deqeue; } if (max_window && pq_head->len>=sizeof(struct ip)+sizeof(struct tcphdr)) { struct ip *ip=(struct ip*)pq_head->data; u_short len=ntohs(ip->ip_len); if (ip->ip_p==IPPROTO_TCP && len==pq_head->len) { struct tcphdr *tcp=(struct tcphdr*)((char*)ip+ip->ip_hl*4); if (ntohs(tcp->th_win)>max_window) { tcp->th_win=htons(max_window); tcp->th_sum=fast_tcp_gen_check(ip); window_changes++; } } } /* according to divert(4) diverts to incoming need a valid ip_sum, while outgoing diverts have their ip_sum recalculated by the ip stack */ if (pq_head->in.sin_addr.s_addr!=INADDR_ANY) { struct ip *ip=(struct ip*)pq_head->data; ip->ip_sum=fast_ip_gen_check(ip); } if (sendto(fd, pq_head->data, pq_head->len, 0, (struct sockaddr*)&pq_head->in, sizeof(pq_head->in))==pq_head->len) { packets_out++; add_bytes_out+=pq_head->len; deqeue: bytes_queued-=sizeof(struct packet)-1+pq_head->len; pq_head=pq_head->next; if (pq_head) pq_head->prev=NULL; packets_queued--; } else { switch (errno) { case EAGAIN: case ENOBUFS: continue; case EMSGSIZE: default: perror("sendto"); goto deqeue; } } } } exit(1); } From owner-freebsd-hackers Sun Dec 22 21:12:44 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA16787 for hackers-outgoing; Sun, 22 Dec 1996 21:12:44 -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 VAA16761 for ; Sun, 22 Dec 1996 21:12:39 -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 VAA15606; Sun, 22 Dec 1996 21:09:32 -0800 (PST) Date: Sun, 22 Dec 1996 21:08:34 -0800 (PST) From: Julian Elischer To: Julian Assange cc: "Daniel O'Callaghan" , hackers@freebsd.org Subject: Re: ipretard.c selective tcp/ip queues and throughput limiters In-Reply-To: <199612230419.PAA03748@profane.iq.org> 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, 23 Dec 1996, Julian Assange wrote: > > Written this morning. If people find it useful, I'll polish it. > > example: > > # ipfw add divert 92 tcp from any to any 80 out via ed0 > # ./ipretard -v -t 1000/300 -w 2208 very neat! this is the sort of thing we wrote the divert socket code for.... From owner-freebsd-hackers Sun Dec 22 22:17:09 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA20267 for hackers-outgoing; Sun, 22 Dec 1996 22:17:09 -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 WAA20249 for ; Sun, 22 Dec 1996 22:17:03 -0800 (PST) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.2/8.8.2) id RAA23698; Mon, 23 Dec 1996 17:16:50 +1100 (EST) From: David Dawes Message-Id: <199612230616.RAA23698@rf900.physics.usyd.edu.au> Subject: Re: what happenedto src/release/*? In-Reply-To: <199612230304.NAA15799@genesis.atrad.adelaide.edu.au> from Michael Smith at "Dec 23, 96 01:34:40 pm" To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Mon, 23 Dec 1996 17:16:47 +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 >I just cvsupped, and all of src/release was deleted. I understans that >there's a new distribution collection, src-release, but I have that in >my cvsupfile. > >Have I just fallen in a crack, or is there a real problem? > >(cvsup.au.freebsd.org, BTW.) I forgot to make the changes required for the removal of src/release and src/tools from the src-etc distribution. While redoing the update (for src-release), I'm getting: Server warning: Cannot open "/home/cvsup/etc/cvsup/prefixes/FreeBSD.cvs/src/rele ase/compat/compat1x.tgz.uu,v": No such file or directory Server warning: Cannot open "/home/cvsup/etc/cvsup/prefixes/FreeBSD.cvs/src/rele ase/compat/compat20.tgz.uu,v": No such file or directory Server warning: Cannot open "/home/cvsup/etc/cvsup/prefixes/FreeBSD.cvs/src/rele ase/compat/compat21.tgz.uu,v": No such file or directory Other than that, it should all be OK on cvsup.au.freebsd.org now. David From owner-freebsd-hackers Sun Dec 22 22:45:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA21396 for hackers-outgoing; Sun, 22 Dec 1996 22:45:58 -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 WAA21391 for ; Sun, 22 Dec 1996 22:45:55 -0800 (PST) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id HAA16852; Mon, 23 Dec 1996 07:04:08 +0100 From: Luigi Rizzo Message-Id: <199612230604.HAA16852@labinfo.iet.unipi.it> Subject: Re: ipretard.c selective tcp/ip queues and throughput limiters To: proff@iq.org (Julian Assange) Date: Mon, 23 Dec 1996 07:04:07 +0100 (MET) Cc: danny@panda.hilink.com.au, hackers@freebsd.org In-Reply-To: <199612230419.PAA03748@profane.iq.org> from "Julian Assange" at Dec 23, 96 03:19:23 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Written this morning. If people find it useful, I'll polish it. very useful. The only drawback is the overhead that this (and basically everything using the divert socket) has: packets move to user space and back, something you don't want to do on high-speed traffic. For a less flexible (at the moment) but much more efficient approach to this kind of problems, have a look also at my dummynet stuff (available from http://www.iet.unipi.it/~luigi). 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 Mon Dec 23 09:41:28 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA11734 for hackers-outgoing; Mon, 23 Dec 1996 09:41:28 -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 JAA11729 for ; Mon, 23 Dec 1996 09:41:25 -0800 (PST) Received: (from jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) id JAA09384; Mon, 23 Dec 1996 09:41:24 -0800 (PST) To: freebsd-hackers@freebsd.org Path: not-for-mail From: jdp@polstra.com (John Polstra) Newsgroups: polstra.freebsd.hackers Subject: Re: what happenedto src/release/*? Date: 23 Dec 1996 09:41:23 -0800 Organization: Polstra & Co., Seattle, WA Lines: 47 Distribution: local Message-ID: <59mg83$955@austin.polstra.com> References: <199612230616.RAA23698@rf900.physics.usyd.edu.au> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199612230616.RAA23698@rf900.physics.usyd.edu.au>, David Dawes wrote: > While redoing the update (for src-release), I'm getting: > > Server warning: Cannot open "/home/cvsup/etc/cvsup/prefixes/FreeBSD.cvs/src/rele > ase/compat/compat1x.tgz.uu,v": No such file or directory > Server warning: Cannot open "/home/cvsup/etc/cvsup/prefixes/FreeBSD.cvs/src/rele > ase/compat/compat20.tgz.uu,v": No such file or directory > Server warning: Cannot open "/home/cvsup/etc/cvsup/prefixes/FreeBSD.cvs/src/rele > ase/compat/compat21.tgz.uu,v": No such file or directory I think you must have been doing your update at the same time that Peter was doing this: peter 96/12/22 22:04:23 Removed: release/compat compat1x.tgz.uu compat20.tgz.uu compat21.tgz.uu Log: Ditch the tarballs (or lardballs as jkh calls them :-) Since these files will no longer have tags, the rcs files can disappear to the archives to recover the space. The server identifies the files needing updates in one thread, and does the actual updating in a second, asynchronous thread. If a file gets deleted in between these two threads, you can get messages like those above. This does not apply to the usual "cvs rm" case, where a file is moved into the Attic -- that's handled fine. It's only when a file is manually deleted from the repository -- which, of course, "never" happens. :-) About the original problem with the missing src-release collection: I'm currently testing a system that will keep the config files for all mirrors up to date and in sync with freefall automatically. (That's the motivation behind the new top-level "distrib" tree in the repository.) That will hopefully eliminate this common problem for all time. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth -- 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 Dec 23 11:56:47 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA19492 for hackers-outgoing; Mon, 23 Dec 1996 11:56:47 -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 LAA19487 for ; Mon, 23 Dec 1996 11:56:33 -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 LAA22602; Mon, 23 Dec 1996 11:49:36 -0800 (PST) Message-ID: <32BEE215.167EB0E7@whistle.com> Date: Mon, 23 Dec 1996 11:48:37 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Luigi Rizzo CC: Julian Assange , danny@panda.hilink.com.au, hackers@freebsd.org Subject: Re: ipretard.c selective tcp/ip queues and throughput limiters References: <199612230604.HAA16852@labinfo.iet.unipi.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Luigi Rizzo wrote: > > > Written this morning. If people find it useful, I'll polish it. > > very useful. The only drawback is the overhead that this (and basically > everything using the divert socket) has: packets move to user space and > back, something you don't want to do on high-speed traffic. > > For a less flexible (at the moment) but much more efficient approach to > this kind of problems, have a look also at my dummynet stuff (available > from http://www.iet.unipi.it/~luigi). but as Kieth sklower at CSRG told me.. There's got to be a way to make it possible for essoteric or unusual modules to be implimented OUT OF THE KERNEL, or they are (1) hard to prototype (2) increasing the complexity of what IS in the kernel beyond the point of debuggability :) From owner-freebsd-hackers Mon Dec 23 13:06:36 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA22718 for hackers-outgoing; Mon, 23 Dec 1996 13:06:36 -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 NAA22694 for ; Mon, 23 Dec 1996 13:06:30 -0800 (PST) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id VAA18083; Mon, 23 Dec 1996 21:24:50 +0100 From: Luigi Rizzo Message-Id: <199612232024.VAA18083@labinfo.iet.unipi.it> Subject: Re: ipretard.c selective tcp/ip queues and throughput limiters To: julian@whistle.com (Julian Elischer) Date: Mon, 23 Dec 1996 21:24:50 +0100 (MET) Cc: proff@iq.org, danny@panda.hilink.com.au, hackers@FreeBSD.ORG In-Reply-To: <32BEE215.167EB0E7@whistle.com> from "Julian Elischer" at Dec 23, 96 11:48:18 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Luigi Rizzo wrote: > > very useful. The only drawback is the overhead that this (and basically > > everything using the divert socket) has: packets move to user space and > > back, something you don't want to do on high-speed traffic. . > but as Kieth sklower at CSRG told me.. > There's got to be a way to make it possible for essoteric or unusual > modules to be implimented OUT OF THE KERNEL, or > they are > (1) hard to prototype > (2) increasing the complexity of what IS in the kernel beyond the > point of debuggability :) which is why I like very much the idea of divert sockets, tun devices and similar things, but only when used in the proper way (e.g. prototyping and/or slow speeds). 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 Mon Dec 23 16:26:05 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA01805 for hackers-outgoing; Mon, 23 Dec 1996 16:26: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 QAA01800 for ; Mon, 23 Dec 1996 16:26: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 QAA11752 for ; Mon, 23 Dec 1996 16:26:01 -0800 (PST) Date: Mon, 23 Dec 1996 16:26:01 -0800 (PST) From: Jaye Mathisen To: hackers@freebsd.org Subject: mount -o noatime unsupported in -current? 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 have noatime set in my mount flags for -current, but mount never shows it as being there. async does seem to work. BTW, does a mount -o async -u take effect immediately? From owner-freebsd-hackers Mon Dec 23 16:38:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA02145 for hackers-outgoing; Mon, 23 Dec 1996 16:38:06 -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 QAA02140 for ; Mon, 23 Dec 1996 16:38:03 -0800 (PST) Received: (from mbarkah@localhost) by hemi.com (8.8.4/8.7.3) id RAA20048 for hackers@freebsd.org; Mon, 23 Dec 1996 17:38:01 -0700 (MST) From: Ade Barkah Message-Id: <199612240038.RAA20048@hemi.com> Subject: That uucppublic directory... To: hackers@freebsd.org Date: Mon, 23 Dec 1996 17:38:01 -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 Hi there, drwxrwxrwx 2 uucp uucp 512 Dec 23 17:20 uucppublic/ Maybe the default permissions for the above should be different ? Regards, -Ade ------------------------------------------------------------------- Inet: mbarkah@hemi.com - HEMISPHERE ONLINE - ------------------------------------------------------------------- From owner-freebsd-hackers Mon Dec 23 20:04:56 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA07456 for hackers-outgoing; Mon, 23 Dec 1996 20:04:56 -0800 (PST) Received: from night.xinside.com (patrick@night.xinside.com [199.164.187.35]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA07451 for ; Mon, 23 Dec 1996 20:04:52 -0800 (PST) Received: (from patrick@localhost) by night.xinside.com (8.8.2/8.8.2) id VAA07914; Mon, 23 Dec 1996 21:01:30 -0700 (MST) Date: Mon, 23 Dec 1996 21:01:30 -0700 (MST) From: Patrick Giagnocavo Message-Id: <199612240401.VAA07914@night.xinside.com> To: hackers@freebsd.org Subject: odd problem with 2.2-Oct. SNAP + POP3 // fetchmail... Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello All, Please respond to both patrick@xinside.com and pgiag@earthlink.net if possible, in addition to the list if you wish... I am simply having the darndest time figuring out what is going on between my ISP and my Dell XPi Notebook running 2.2-961014-SNAP. I am using the iijppp (tun0 driver) package to connect to my ISP. Everything connects fine, I can surf the WWW no problem. In trying to get my email though I see the following behavior: -- I connect via POP3 using either Netscape 3.01 Gold or using the fetchmail client (latest version). -- connection is made, password accepted. Either client gets the information about how many messages there are, and the size of the first message. -- then, nothing; absolutely nothing. I can leave it alone as long as I want, but no POP mail is downloaded. No modem lights blink, no data seems to be transmitted. -- I have an ancient Mac (that I of course will not be taking on the road with me as travel back East this Christmas). It is able to download just fine. Ideas? Merry Christmas! --Patrick From owner-freebsd-hackers Mon Dec 23 22:02:49 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA10495 for hackers-outgoing; Mon, 23 Dec 1996 22:02:49 -0800 (PST) Received: from deceased.hb.north.de (deceased.hb.north.de [194.94.232.249]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id WAA10488 for ; Mon, 23 Dec 1996 22:02:46 -0800 (PST) Received: from jelal.hb.north.de by deceased.hb.north.de with uucp (Smail3.2) id m0vcPwc-0016CJC; Tue, 24 Dec 1996 07:02:30 +0100 (MET) Received: by jelal.hb.north.de (SMail-ST 0.95gcc/2.5+) id AA00055; Tue, 24 Dec 1996 07:00:14 +0100 (CET) Received: (from nox@localhost) by saturn.hb.north.de (8.7.5/8.7.3) id HAA21312; Tue, 24 Dec 1996 07:00:37 +0100 (MET) Date: Tue, 24 Dec 1996 07:00:37 +0100 (MET) From: Juergen Lock Message-Id: <199612240600.HAA21312@saturn.hb.north.de> Subject: ping o'death, variation on a theme... and less deadly things (bisdn) To: isdn@muc.ditec.de Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [Not sure why this didn't go out the first time so i'm sending it again. sorry to anyone who already saw it...] And you thoght BSD's ip is immune to those right? :) I still haven't got around tracking this down further but here is what happens: 2.1.6-stable kernel with bisdn-0.97 and bpf, start tcpdump -i ipi0 then send it a 32k ping from the other end (a dos ka9q + ispa in this case). you see the fragments coming in and then it dies, apparently having overwritten the stack trying to copy the entire(?) outgoing packet to bpf. Also the bisdntrc didnt start properly with the included start_if script, this is what i'm using now: (and its running just perfect as long as i leave bpf alone. i like it!) Index: sys-i386-isa/teles.c @@ -563,6 +563,10 @@ chan_t *chan = &sc->sc_chan[c]; caddr_t hscx = chan->hscx; + /* tel_init gets called from all over the place. We don't want an */ + /* interrupt to occur in the middle of changing these pointers */ + /* mask all interrupts */ + (*sc->put)(hscx, 0x20, 0xff); /* MASK */ if (chan->obuf) m_freem(chan->obuf); if (chan->ibuf) Index: sys-bisdn/b_isdnipi.c @@ -444,6 +444,7 @@ register struct mbuf *m1 = m; register u_char *cp = bpfbuf; + u_int left = sizeof(bpfbuf) - 4; u_int af = dst->sa_family; /* prepend the address family to bpf buffer */ @@ -455,10 +456,12 @@ { register int mlen = m1->m_len; + if (mlen > left) + mlen = left; bcopy(mtod(m1, caddr_t), cp, mlen); cp += mlen; len += mlen; - } while((m1 = m1->m_next) != NULL); + } while((m1 = m1->m_next) != NULL && left > 0); } #endif /* NBPFILTER */ Index: bisdntrc/bisdntrc.c @@ -148,7 +148,23 @@ } } +#if 1 + if((setvbuf(stdout, (char *)NULL, _IOLBF, 0)) != 0) + { + char buffer[80]; + + sprintf(buffer, "Error setting stdout to line-buffered"); + perror(buffer); + exit(1); + } + if (signal(SIGHUP, catchsig) == SIG_IGN) { + /* write(1, "signal(SIGHUP, SIG_IGN)\n", + sizeof "signal(SIGHUP, SIG_IGN)\n" - 1); */ + signal(SIGHUP, SIG_IGN); + }; +#else (void) signal(SIGHUP, catchsig); +#endif (void) signal(SIGTERM, catchsig); (void) signal(SIGKILL, catchsig); (void) signal(SIGINT, catchsig); Index: etc/start_if.ipi0 @@ -1,3 +1,4 @@ +#! /bin/sh #--------------------------------------------------------------------------- # # /etc/start_if.ipi0 - startup script for bisdn daemon @@ -10,7 +11,8 @@ # output device for fullscreen mode out_dev=/dev/ttyv6 # terminal type for fullscreen mode -out_typ=pcvt25h +#out_typ=pcvt25h +out_typ=cons25 # enable lowlevel ISDN tracing isdn_trace=YES @@ -18,10 +20,10 @@ echo '---------- enter /etc/start_if.ipi0 -----------------------------------' -if [ -f /etc/rc.ipfw ] -then - sh /etc/rc.ipfw -fi +#if [ -f /etc/rc.ipfw ] +#then +# sh /etc/rc.ipfw +#fi # start the isdn daemon if [ -x /usr/local/bin/bisdnd ] @@ -36,7 +38,8 @@ if [ -x /usr/local/bin/bisdntrc -a X${isdn_trace} = X"YES" ] then echo 'starting ISDN tracing ...' - nohup /usr/local/bin/bisdntrc -n4 -r -o/tmp/isdn.trace >/dev/null 2>&1 & + #nohup /usr/local/bin/bisdntrc -n4 -r -o/tmp/isdn.trace >/dev/null 2>&1 & + (cd /etc/bisdn; sh -c 'nohup /usr/local/bin/bisdntrc -n4 -r >>/var/log/bisdn/isdn.trace 2>&1 &') sleep 1 fi thanx + cheers, Juergen From owner-freebsd-hackers Mon Dec 23 23:51:12 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA13756 for hackers-outgoing; Mon, 23 Dec 1996 23:51:12 -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 XAA13750 for ; Mon, 23 Dec 1996 23:51:07 -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 IAA15624; Tue, 24 Dec 1996 08:50:57 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA29596; Tue, 24 Dec 1996 08:50:56 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id IAA10140; Tue, 24 Dec 1996 08:37:08 +0100 (MET) From: J Wunsch Message-Id: <199612240737.IAA10140@uriah.heep.sax.de> Subject: Re: That uucppublic directory... To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Tue, 24 Dec 1996 08:37:07 +0100 (MET) Cc: mbarkah@hemi.com (Ade Barkah) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612240038.RAA20048@hemi.com> from Ade Barkah at "Dec 23, 96 05:38:01 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 Ade Barkah wrote: > drwxrwxrwx 2 uucp uucp 512 Dec 23 17:20 uucppublic/ > > Maybe the default permissions for the above should be different ? Not if you wanna allow UUCP file transfers. That's why it is called a `pubdir' -- everybody can upload there. No, even `t' bits won't do any good, since the user who's received a file from remote should be able to delete the file there, but the way it arrived from outside, it's owned by `uucp'. Of course, if you don't need that service at all, or ar going to organize this in a different way (e.g. by arranging for a UUCP directory in the people's homedir), you can safely remove 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 Mon Dec 23 23:52:16 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA13846 for hackers-outgoing; Mon, 23 Dec 1996 23:52:16 -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 XAA13830 for ; Mon, 23 Dec 1996 23:52:13 -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 IAA15808; Tue, 24 Dec 1996 08:52:03 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA29604; Tue, 24 Dec 1996 08:52:03 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id IAA10254; Tue, 24 Dec 1996 08:48:32 +0100 (MET) From: J Wunsch Message-Id: <199612240748.IAA10254@uriah.heep.sax.de> Subject: Re: mount -o noatime unsupported in -current? To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Tue, 24 Dec 1996 08:48:32 +0100 (MET) Cc: mrcpu@cdsnet.net (Jaye Mathisen) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Jaye Mathisen at "Dec 23, 96 04:26:01 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 Jaye Mathisen wrote: > BTW, does a mount -o async -u take effect immediately? Yes, i'm using it often before rm -r'ing a large subhierarchy (and ``mount -o noasync -u'' later). -- 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 Dec 24 00:21:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA14691 for hackers-outgoing; Tue, 24 Dec 1996 00:21:19 -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 AAA14686 for ; Tue, 24 Dec 1996 00:21: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 JAA20591; Tue, 24 Dec 1996 09:20:59 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA29793; Tue, 24 Dec 1996 09:20:58 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id JAA10431; Tue, 24 Dec 1996 09:03:48 +0100 (MET) From: J Wunsch Message-Id: <199612240803.JAA10431@uriah.heep.sax.de> Subject: Re: odd problem with 2.2-Oct. SNAP + POP3 // fetchmail... To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Tue, 24 Dec 1996 09:03:48 +0100 (MET) Cc: patrick@xinside.com, pgiag@earthlink.net Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612240401.VAA07914@night.xinside.com> from Patrick Giagnocavo at "Dec 23, 96 09:01:30 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 Patrick Giagnocavo wrote: > -- connection is made, password accepted. Either client gets the > information about how many messages there are, and the size of the > first message. > > -- then, nothing; absolutely nothing. I basically mistrust Netcrap at first. Have you ever tried to use something like popclient (it's in the ports)? -- 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 Dec 24 05:55:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA21785 for hackers-outgoing; Tue, 24 Dec 1996 05:55:18 -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 FAA21778 for ; Tue, 24 Dec 1996 05:55:07 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hydrogen.nike.efn.org (8.8.3/8.8.3) with SMTP id CAA10713 for ; Tue, 24 Dec 1996 02:39:10 -0800 (PST) Date: Tue, 24 Dec 1996 02:39:09 -0800 (PST) From: John-Mark Gurney X-Sender: jmg@hydrogen Reply-To: John-Mark Gurney To: FreeBSD Hackers Subject: err: sleep(5) from telnet, after select 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.. I have a diskless machine (386/25sx 6meg ram, swap also nfs) that regularly gets this message... I notice there was a comment about this... that he (or whoever added it) doesn't like it... I just recompiled telnet to give me the errno when this happens... when it does it gives 14 == EFAULT... it only seems to happen after I've let it be for a while... any body have any suggestions? should I just remove the sleep and be gone with it? thanks for your suggesstions... 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 Tue Dec 24 06:17:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA22205 for hackers-outgoing; Tue, 24 Dec 1996 06:17:19 -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 GAA22200 for ; Tue, 24 Dec 1996 06:17:16 -0800 (PST) Received: (from greg@localhost) by nevis.oss.uswest.net (8.8.2/8.8.2) id IAA12059 for hackers@freebsd.org; Tue, 24 Dec 1996 08:16:45 -0600 (CST) From: "Greg Rowe" Message-Id: <9612240816.ZM12057@nevis.oss.uswest.net> Date: Tue, 24 Dec 1996 08:16:45 -0600 X-Mailer: Z-Mail (3.2.1 10oct95) To: hackers@freebsd.org Subject: Exabyte 8505XL Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can anyone tell me what the default density is for an Exabyte 8505XL tape drive on 2.1.5 ? I seem to be only getting around 7-8 gig on a tape using Amanda. I'm not sure if this is because I'm comressing the dumps prior to writing to tape and hardware compression can't do much more, or I'm writing to the tape at standard 8505 density. I noticed density codes have been added to the SCSI code at 2.2 for Exabytes. Do I need to upgrade my dump systems to take advantage of the Exabyte hardware compression ? Thanks. Greg From owner-freebsd-hackers Tue Dec 24 07:40:38 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA24189 for hackers-outgoing; Tue, 24 Dec 1996 07:40:38 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA24182 for ; Tue, 24 Dec 1996 07:40:35 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id QAA09193; Tue, 24 Dec 1996 16:30:27 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.8.4/8.8.2) with SMTP id OAA28156; Tue, 24 Dec 1996 14:27:35 +0100 (MET) Date: Tue, 24 Dec 1996 14:27:35 +0100 (MET) From: Andreas Klemm To: Joerg Wunsch cc: FreeBSD hackers , Jaye Mathisen Subject: Re: mount -o noatime unsupported in -current? In-Reply-To: <199612240748.IAA10254@uriah.heep.sax.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 Tue, 24 Dec 1996, J Wunsch wrote: > As Jaye Mathisen wrote: > > > BTW, does a mount -o async -u take effect immediately? > > Yes, i'm using it often before rm -r'ing a large subhierarchy (and > ``mount -o noasync -u'' later). Yes, this is a nice trick ;) Then rm -rf works like hell ;-)) It's blindly fast and very dangerous ;) -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-hackers Tue Dec 24 09:52:12 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA27836 for hackers-outgoing; Tue, 24 Dec 1996 09:52:12 -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 JAA27831 for ; Tue, 24 Dec 1996 09:52:08 -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 JAA07082 for ; Tue, 24 Dec 1996 09:50:07 -0800 (PST) Message-ID: <32C01792.41C67EA6@whistle.com> Date: Tue, 24 Dec 1996 09:49:07 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: 2.2 build broken? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just checked out the sources using RELENG_2_2 and the build stops with: ===> usr.bin/ee ===> usr.bin/env ===> usr.bin/error ===> usr.bin/expand ===> usr.bin/f2c ===> usr.bin/false ===> usr.bin/fetch cc -O -Wall -c /usr/src/usr.bin/fetch/main.c /usr/src/usr.bin/fetch/main.c: In function `ftpget': /usr/src/usr.bin/fetch/main.c:304: too few arguments to function `ftpLogin' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. # is anyone fixing this? (specifically, who's working on fetch these days)? it looks as if this file hasn't been changed in 2.2 for a while revision 1.29 date: 1996/11/14 07:36:26; author: ache; state: Exp; lines: +3 -2 Report net connection error via hstrerror(h_errno) now instead of simple fact that can't connect revision 1.26.2.2 date: 1996/11/28 08:26:14; author: phk; state: Exp; lines: +9 -4 YAMFC From owner-freebsd-hackers Tue Dec 24 11:10:33 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA29888 for hackers-outgoing; Tue, 24 Dec 1996 11:10:33 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA29883 for ; Tue, 24 Dec 1996 11:10:31 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id LAA09181; Tue, 24 Dec 1996 11:10:19 -0800 (PST) To: Julian Elischer cc: hackers@freebsd.org Subject: Re: 2.2 build broken? In-reply-to: Your message of "Tue, 24 Dec 1996 09:49:07 PST." <32C01792.41C67EA6@whistle.com> Date: Tue, 24 Dec 1996 11:10:19 -0800 Message-ID: <9177.851454619@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I just checked out the sources using RELENG_2_2 > and the build stops with: You're probably just not building right. You should have the new libftpio library installed before you rebuild fetch. Jordan From owner-freebsd-hackers Tue Dec 24 11:38:53 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA01568 for hackers-outgoing; Tue, 24 Dec 1996 11:38:53 -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 LAA01559 for ; Tue, 24 Dec 1996 11:38:48 -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 LAA08587; Tue, 24 Dec 1996 11:33:31 -0800 (PST) Message-ID: <32C02FCF.2781E494@whistle.com> Date: Tue, 24 Dec 1996 11:32:31 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: hackers@freebsd.org Subject: Re: 2.2 build broken? References: <9177.851454619@time.cdrom.com> 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 wrote: > > > I just checked out the sources using RELENG_2_2 > > and the build stops with: > > You're probably just not building right. You should have the > new libftpio library installed before you rebuild fetch. > > Jordan make bootstrap make world on a system that was made from the 2.2 branch (about 4 weeks ago) I am doing a 'make install' after which I'll try 'make' again..... From owner-freebsd-hackers Tue Dec 24 11:38:56 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA01575 for hackers-outgoing; Tue, 24 Dec 1996 11:38:56 -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 LAA01558 for ; Tue, 24 Dec 1996 11:38:48 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id UAA00407 for ; Tue, 24 Dec 1996 20:38:43 +0100 Received: (from uucp@localhost) by brasil.brainstorm.fr (8.6.12/8.6.12) with UUCP id UAA15988 for hackers@freebsd.org; Tue, 24 Dec 1996 20:38:42 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.4/keltia-uucp-2.9) id UAA08747; Tue, 24 Dec 1996 20:26:54 +0100 (CET) Message-ID: Date: Tue, 24 Dec 1996 20:26:53 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: hackers@freebsd.org Subject: Re: 2.2 build broken? References: <32C01792.41C67EA6@whistle.com> X-Mailer: Mutt 0.55.04 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2837 In-Reply-To: <32C01792.41C67EA6@whistle.com>; from Julian Elischer on Dec 24, 1996 09:49:07 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Julian Elischer: > ===> usr.bin/fetch > cc -O -Wall -c /usr/src/usr.bin/fetch/main.c > /usr/src/usr.bin/fetch/main.c: In function `ftpget': > /usr/src/usr.bin/fetch/main.c:304: too few arguments to function > `ftpLogin' I'm surprised: 452 [20:17] roberto@keltia:/tmp> cvs -d /spare/FreeBSD-current co -r RELENG_2_2 fetch cvs checkout: Updating fetch U fetch/Makefile U fetch/fetch.1 U fetch/main.c ... 456 [20:17] roberto@keltia:/tmp/fetch> ll total 22 drwxr-xr-x 2 roberto wheel 512 Dec 24 20:17 CVS/ -rw-r--r-- 1 roberto wheel 104 Jun 26 22:49 Makefile -rw-r--r-- 1 roberto wheel 3065 Sep 24 00:24 fetch.1 -rw-r--r-- 1 roberto wheel 16681 Nov 28 09:26 main.c 457 [20:17] roberto@keltia:/tmp/fetch> make Warning: Object directory not changed from original /tmp/fetch cc -O -m486 -pipe -Wall -c main.c cc -O -m486 -pipe -Wall -o fetch main.o -lftpio gzip -c fetch.1 > fetch.1.gz ... 460 [20:20] roberto@keltia:/tmp/fetch> cvs status -v main.c =================================================================== File: main.c Status: Up-to-date Working revision: 1.26.2.2 Thu Nov 28 08:26:14 1996 Repository revision: 1.26.2.2 /spare/FreeBSD-current/src/usr.bin/fetch/main.c,v Sticky Tag: RELENG_2_2 (branch: 1.26.2) Sticky Date: (none) Sticky Options: (none) You may have a pre-1.8.2.1 version of ftpio.h (before Andrey's changes that added the 6th parameter). -- 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 Dec 24 12:48:29 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA03722 for hackers-outgoing; Tue, 24 Dec 1996 12:48:29 -0800 (PST) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA03717 for ; Tue, 24 Dec 1996 12:48:27 -0800 (PST) Received: by kaori.communique.net with Microsoft Exchange (IMC 4.0.837.3) id <01BBF1A9.3A8DF710@kaori.communique.net>; Tue, 24 Dec 1996 14:46:21 -0600 Message-ID: From: Raul Zighelboim To: "'hackers@freefall.freebsd.org'" Subject: More DC21140 problems.... Date: Tue, 24 Dec 1996 14:46:20 -0600 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3 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 is what DMESG reports... de0 rev 32 int a irq 9 on pci0:11 de0: SMC 8432BA DC21140A [10-100Mb/s] pass 2.0 de0: address 00:00:c0:4b:6c:ef de0: enabling BNC/AUI port This interface is connected to a 10bT hub. This card does not hasa AUI port, only a tp port. Is there something I am missing? maybe something I can set the kernel for apart from 'device de0' ? Thanks. ------------------------ ------------------------ Raul Zighelboim Communique Inc. mailto:mango@communique.net http://www.communique.net From owner-freebsd-hackers Tue Dec 24 13:20:26 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA04941 for hackers-outgoing; Tue, 24 Dec 1996 13:20:26 -0800 (PST) Received: from rhiannon.clari.net.au (dns1.clari.net.au [203.27.85.9]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA04936 for ; Tue, 24 Dec 1996 13:20:22 -0800 (PST) Received: (from peter@localhost) by rhiannon.clari.net.au (8.7.5/8.6.12) id IAA23024; Wed, 25 Dec 1996 08:20:02 +1100 (EST) Message-ID: X-Mailer: XFMail 0.4 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 25 Dec 1996 08:19:23 +1100 (EST) Organization: ClariNET Internet Servies From: Peter Hawkins To: Julian Elischer Subject: Re: ipretard.c selective tcp/ip queues and throughput limiters Cc: Julian Assange , "Daniel O'Callaghan" , hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'd really love a copy of this! Where can I get it? Peter ---------------------------------- Peter Hawkins E-Mail: Peter Hawkins Ph: 61 3 9852 7340 ClariNET Internet Services http://www.clari.net.au ---------------------------------- From owner-freebsd-hackers Tue Dec 24 13:21:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA05005 for hackers-outgoing; Tue, 24 Dec 1996 13:21:18 -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 NAA04998 for ; Tue, 24 Dec 1996 13:21:15 -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 WAA01801 for ; Tue, 24 Dec 1996 22:21:13 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA09713 for freebsd-hackers@freebsd.org; Tue, 24 Dec 1996 22:21:13 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id WAA13246 for freebsd-hackers@freebsd.org; Tue, 24 Dec 1996 22:18:03 +0100 (MET) From: J Wunsch Message-Id: <199612242118.WAA13246@uriah.heep.sax.de> Subject: Re: mount -o noatime unsupported in -current? To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Tue, 24 Dec 1996 22:18:03 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Andreas Klemm at "Dec 24, 96 02:27:35 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 Andreas Klemm wrote: > Yes, this is a nice trick ;) Then rm -rf works like hell ;-)) > It's blindly fast and very dangerous ;) It's not that risky. In particular, if all you're doing is a large `rm' operation, fsck should always be able to repair the filesystem even in case of a catastrophic failure. -- 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 Dec 24 13:21:49 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA05081 for hackers-outgoing; Tue, 24 Dec 1996 13:21: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 NAA05074 for ; Tue, 24 Dec 1996 13:21: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 WAA01835; Tue, 24 Dec 1996 22:21:26 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA09722; Tue, 24 Dec 1996 22:21:21 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id WAA13332; Tue, 24 Dec 1996 22:20:37 +0100 (MET) From: J Wunsch Message-Id: <199612242120.WAA13332@uriah.heep.sax.de> Subject: Re: Exabyte 8505XL To: greg@uswest.net (Greg Rowe) Date: Tue, 24 Dec 1996 22:20:37 +0100 (MET) Cc: hackers@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <9612240816.ZM12057@nevis.oss.uswest.net> from Greg Rowe at "Dec 24, 96 08:16:45 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 Greg Rowe wrote: > Do I need to upgrade my dump systems to take advantage of > the Exabyte hardware compression ? Thanks. There are unfortunately multiple ways how vendors could implement the `compression on' switch. One of them is implemented as ``mt comp 1'', have you tried this? -- 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 Dec 24 13:45:51 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA05806 for hackers-outgoing; Tue, 24 Dec 1996 13:45:51 -0800 (PST) Received: from mail13.digital.com (mail13.digital.com [192.208.46.30]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA05795 for ; Tue, 24 Dec 1996 13:45:48 -0800 (PST) Received: from muggsy.lkg.dec.com by mail13.digital.com (8.7.5/UNX 1.5/1.0/WV) id QAA15980; Tue, 24 Dec 1996 16:36:47 -0500 (EST) Received: from whydos.lkg.dec.com by muggsy.lkg.dec.com (5.65/DEC-Ultrix/4.3) with SMTP id AA12835; Tue, 24 Dec 1996 16:36:44 -0500 Received: from localhost.lkg.dec.com (localhost.lkg.dec.com [127.0.0.1]) by whydos.lkg.dec.com (8.6.12/8.6.12) with SMTP id RAA26829; Tue, 24 Dec 1996 17:45:21 GMT Message-Id: <199612241745.RAA26829@whydos.lkg.dec.com> X-Authentication-Warning: whydos.lkg.dec.com: Host localhost.lkg.dec.com didn't use HELO protocol To: Raul Zighelboim Cc: "'hackers@freefall.freebsd.org'" Subject: Re: More DC21140 problems.... In-Reply-To: Your message of "Tue, 24 Dec 1996 14:46:20 CST." Date: Tue, 24 Dec 1996 17:45:20 +0000 From: Matt Thomas Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > de0 rev 32 int a irq 9 on pci0:11 > de0: SMC 8432BA DC21140A [10-100Mb/s] pass 2.0 > de0: address 00:00:c0:4b:6c:ef > de0: enabling BNC/AUI port That's due to a bug in identify_smc_nic routine. However, fixing that bug won't prove things much since you need to use autonegotiation on that board. -- Matt Thomas Internet: matt@3am-software.com 3am Software Foundry WWW URL: http://www.3am-software.com/bio/matt.html Westford, MA Disclaimer: I disavow all knowledge of this message From owner-freebsd-hackers Tue Dec 24 15:22:28 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA10142 for hackers-outgoing; Tue, 24 Dec 1996 15:22:28 -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 PAA10135 for ; Tue, 24 Dec 1996 15:22:25 -0800 (PST) Message-Id: <199612242322.PAA10135@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA114609736; Wed, 25 Dec 1996 10:22:16 +1100 From: Darren Reed Subject: Re: Exabyte 8505XL To: greg@uswest.net (Greg Rowe) Date: Wed, 25 Dec 1996 10:22:16 +1100 (EDT) Cc: hackers@freebsd.org In-Reply-To: <9612240816.ZM12057@nevis.oss.uswest.net> from "Greg Rowe" at Dec 24, 96 08:16:45 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 Greg Rowe, sie said: > > Can anyone tell me what the default density is for an Exabyte 8505XL tape > drive > on 2.1.5 ? I seem to be only getting around 7-8 gig on a tape using Amanda. > I'm > not sure if this is because I'm comressing the dumps prior to writing to tape > and hardware compression can't do much more, or I'm writing to the tape at > standard 8505 density. I noticed density codes have been added to the SCSI > code > at 2.2 for Exabytes. Do I need to upgrade my dump systems to take advantage of > the Exabyte hardware compression ? Thanks. bdsf 126 54000 6000 :2.3G", # Exabyte 8200 bdsf 126 54000 13000 :5.2G", # Exabyte 8500 (double density 112m) bdsf 126 54000 18000 :7.0G", # Exabyte 8500 (double density 160m) bdsf 126 108000 13000 :10.4G", # Exabyte 8500-Compression 112m bdsf 126 108000 18000 :14.0G", # Exabyte 8500-Compression 160m these "work" for me, but I'm not sure if they're correct or not. From owner-freebsd-hackers Tue Dec 24 17:29:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA21717 for hackers-outgoing; Tue, 24 Dec 1996 17:29:19 -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 RAA21711 for ; Tue, 24 Dec 1996 17:29:16 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id LAA21213; Wed, 25 Dec 1996 11:59:00 +1030 (CST) From: Michael Smith Message-Id: <199612250129.LAA21213@genesis.atrad.adelaide.edu.au> Subject: Re: mount -o noatime unsupported in -current? In-Reply-To: from Andreas Klemm at "Dec 24, 96 02:27:35 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Wed, 25 Dec 1996 11:58:59 +1030 (CST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@freebsd.org, mrcpu@cdsnet.net 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 Andreas Klemm stands accused of saying: > > > > Yes, i'm using it often before rm -r'ing a large subhierarchy (and > > ``mount -o noasync -u'' later). > > Yes, this is a nice trick ;) Then rm -rf works like hell ;-)) > It's blindly fast and very dangerous ;) Actually, I've crashed any number of boxes using '-o async' and have yet to lose anything substantial. We don't ship with it because fsck tends to get a bit unhappy about it, and talking a customer through a manual fsck can be a pain, but internally we use it all the time; IMHO the performance advantage for things like large CVS operations and big deletions is a fair tradeoff against the possible risk of having to restore from backup. > andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH -- ]] 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 Dec 25 07:04:52 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA13854 for hackers-outgoing; Wed, 25 Dec 1996 07:04:52 -0800 (PST) Received: from squirrel.tgsoft.com (sdts3-44.znet.com [207.167.66.44]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA13849 for ; Wed, 25 Dec 1996 07:04:49 -0800 (PST) Received: (from thompson@localhost) by squirrel.tgsoft.com (8.8.3/8.6.12) id HAA00997; Wed, 25 Dec 1996 07:12:18 -0800 (PST) Date: Wed, 25 Dec 1996 07:12:18 -0800 (PST) Message-Id: <199612251512.HAA00997@squirrel.tgsoft.com> From: mark thompson To: freebsd-hackers@freebsd.org Subject: cvsup change Reply-to: thompson@znet.com Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have been paying attention (or so i thought) to the reorganizaion of the collections, so i added: src-release release=cvs host=cvsup.freebsd.org hostbase=/home base=/u prefix=/usr/cvs delete old use-rel-suffix compress to the beginning of my cvsup file. It nicely ran through that. It nicely ran through another collection or two, then it deleted everything in src/release. I moved the request for src-release to just before ports-all, and it is now very nicely bringing src/release back. Is this the behaviour that I should expect from: CVSup client Software version: REL_14_0 Protocol version: 14.0 ? -mark From owner-freebsd-hackers Wed Dec 25 10:00:25 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA17415 for hackers-outgoing; Wed, 25 Dec 1996 10:00:25 -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 KAA17408 for ; Wed, 25 Dec 1996 10:00:23 -0800 (PST) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id SAA20184 for hackers@freebsd.org; Wed, 25 Dec 1996 18:21:07 +0100 From: Luigi Rizzo Message-Id: <199612251721.SAA20184@labinfo.iet.unipi.it> Subject: Any support for PnP ? To: hackers@freebsd.org Date: Wed, 25 Dec 1996 18:21:07 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there any support for PnP boards, in any release of FreeBSD or the other free unixes (NetBSD, Linux) ? In case the answer is negative, is there anyone interested in working on this ? I know this is a boring thing to do, but there are probably strong "marketing" motivations to add such support: More and more cards (specifically: audio and network) nowadays are soft-configurable only. This forces users to run Windows just to configure properly the boards, not to mention those cards which neet to be enabled at bootstrap. Secondly, it might not be too hard to add such a feature: we already have support for soft configuration with for the PCI boards, and the specifications for PnP seem to be available on the net. There might even be some code available, if someone has pointers I might spend some time working on this. 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 Wed Dec 25 11:24:35 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA19366 for hackers-outgoing; Wed, 25 Dec 1996 11:24:35 -0800 (PST) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA19361 for ; Wed, 25 Dec 1996 11:24:33 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.7.5/8.6.12) with SMTP id LAA02841; Wed, 25 Dec 1996 11:15:29 -0800 (PST) Message-Id: <199612251915.LAA02841@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: Host localhost [127.0.0.1] didn't use HELO protocol To: Luigi Rizzo Cc: hackers@freebsd.org Subject: Re: Any support for PnP ? Reply-To: Jason Thorpe From: Jason Thorpe Date: Wed, 25 Dec 1996 11:15:29 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 25 Dec 1996 18:21:07 +0100 (MET) Luigi Rizzo wrote: > Is there any support for PnP boards, in any release of FreeBSD or > the other free unixes (NetBSD, Linux) ? You may want to contact Christos Zoulas . He has written some very good PnP code for NetBSD. I've done a small amount of hacking on his code, and I expect it to be committed to the NetBSD master sources very soon. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-hackers Wed Dec 25 17:54:49 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA01108 for hackers-outgoing; Wed, 25 Dec 1996 17:54:49 -0800 (PST) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA01103; Wed, 25 Dec 1996 17:54:47 -0800 (PST) Received: by kaori.communique.net with Microsoft Exchange (IMC 4.0.837.3) id <01BBF29D.28C8B4D0@kaori.communique.net>; Wed, 25 Dec 1996 19:52:29 -0600 Message-ID: From: Raul Zighelboim To: "'hackers@freefall.freebsd.org'" Cc: "'questions@freefall.freebsd.org'" Subject: Help 'no buffer available'!! Date: Wed, 25 Dec 1996 19:52:28 -0600 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3 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 My poor news server is sick..... ----kiyoko:/var/log# ping akira PING akira.communique.net (204.27.65.10): 56 data bytes 64 bytes from 204.27.65.10: icmp_seq=0 ttl=255 time=0.867 ms ping: sendto: No buffer space available ping: wrote akira.communique.net 64 chars, ret=-1 ping: sendto: No buffer space available ping: wrote akira.communique.net 64 chars, ret=-1 64 bytes from 204.27.65.10: icmp_seq=3 ttl=255 time=0.708 ms ---- this is killing communications once in a while....(the message No buffer available)... we stopped runnung named on the server to preserve memory.... What can I do to resolve it on 2.1.6R (will be upgrading to 2.2b soon) My kernel details" options "CHILD_MAX=512" options "OPEN_MAX=1024" options "MAXMEM=262144" options "NMBCLUSTERS=4096" options "EXTRAVNODES=30000" <----- this is not a real option on 2.1.6 options "NBUF=4096" 3c509 and ahc controllers. I also run "/usr/sbin/sysctl -w kern.maxvnodes=30000" at boot time.... Is theresomething I am missing ? Thanks. ------------------------ ------------------------ Raul Zighelboim Communique Inc. mailto:mango@communique.net http://www.communique.net From owner-freebsd-hackers Wed Dec 25 18:20:14 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA02406 for hackers-outgoing; Wed, 25 Dec 1996 18:20:14 -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 SAA02386; Wed, 25 Dec 1996 18:20:09 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id SAA04304; Wed, 25 Dec 1996 18:18:48 -0800 (PST) Message-Id: <199612260218.SAA04304@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Raul Zighelboim cc: "'hackers@freefall.freebsd.org'" , "'questions@freefall.freebsd.org'" Subject: Re: Help 'no buffer available'!! In-reply-to: Your message of "Wed, 25 Dec 1996 19:52:28 CST." From: David Greenman Reply-To: dg@root.com Date: Wed, 25 Dec 1996 18:18:47 -0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >My kernel details" > >options "CHILD_MAX=512" >options "OPEN_MAX=1024" >options "MAXMEM=262144" >options "NMBCLUSTERS=4096" >options "EXTRAVNODES=30000" <----- this is not a real option on >2.1.6 >options "NBUF=4096" I don't know off hand what is causing your problem, but you definately don't want NBUF=4096. There is no reason for it and it will consume a tremendous amount of virtual memory in 2.1.x. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Wed Dec 25 20:34:57 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA06395 for hackers-outgoing; Wed, 25 Dec 1996 20:34:57 -0800 (PST) Received: from edison.ebicom.net (ttsai@Edison.EbiCom.net [205.218.114.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA06388 for ; Wed, 25 Dec 1996 20:34:55 -0800 (PST) Received: (from ttsai@localhost) by edison.ebicom.net From: Tim Tsai Message-Id: <199612260434.WAA19053@edison.ebicom.net> Subject: 2.1.6 kernel and pgcc To: freebsd-hackers@freebsd.org Date: Wed, 25 Dec 1996 22:34:52 -0600 (CST) Receipt-To: ttsai@pobox.com Reply-To: ttsai@pobox.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 When I tried to compile 2.1.6 kernel with pgcc, I get the following error: ../../i386/clock.c:300: inconsistent operand constraints in an `asm' ../../i386/clock.c:302: inconsistent operand constraints in an `asm' the offending code is: __asm __volatile(".byte 0xf,0x31" : "=A" (last_count)); DELAY(1000000); __asm __volatile(".byte 0xf,0x31" : "=A" (count)); any ideas? I just hard code it to my CPU speed for now. Thanks, Tim From owner-freebsd-hackers Wed Dec 25 21:02:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA07151 for hackers-outgoing; Wed, 25 Dec 1996 21:02:31 -0800 (PST) Received: from hamby1.lightside.net (hamby1.lightside.net [207.67.176.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA07142 for ; Wed, 25 Dec 1996 21:02:08 -0800 (PST) Received: from localhost (jehamby@localhost) by hamby1.lightside.net (8.8.3/8.8.2) with SMTP id VAA00218; Wed, 25 Dec 1996 21:01:06 -0800 (PST) X-Authentication-Warning: hamby1.lightside.net: jehamby owned process doing -bs Date: Wed, 25 Dec 1996 21:01:05 -0800 (PST) From: Jake Hamby X-Sender: jehamby@hamby1 Reply-To: Jake Hamby To: hackers@freebsd.org, "John S. Dyson" Subject: Update on Lite/2 merge? 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 haven't heard anything on the Lite/2 merge yet, and I've been holding off on doing a "make world". Can we get a brief heads-up on when to expect those changes and what to watch out for after they occur? Thanks! -- Jake From owner-freebsd-hackers Wed Dec 25 22:48:27 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA10342 for hackers-outgoing; Wed, 25 Dec 1996 22:48:27 -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 WAA10337 for ; Wed, 25 Dec 1996 22:48:25 -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 WAA02511 for ; Wed, 25 Dec 1996 22:49:10 -0800 (PST) Received: (qmail 5748 invoked by uid 110); 26 Dec 1996 06:48:14 -0000 Message-ID: <19961226064814.5747.qmail@suburbia.net> Subject: Re: Help 'no buffer available'!! In-Reply-To: from Raul Zighelboim at "Dec 25, 96 07:52:28 pm" To: mango@staff.communique.net (Raul Zighelboim) Date: Thu, 26 Dec 1996 17:48:14 +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 > My poor news server is sick..... > > ----kiyoko:/var/log# ping akira > PING akira.communique.net (204.27.65.10): 56 data bytes > 64 bytes from 204.27.65.10: icmp_seq=0 ttl=255 time=0.867 ms > ping: sendto: No buffer space available > ping: wrote akira.communique.net 64 chars, ret=-1 > ping: sendto: No buffer space available I often get this as well. What is the philosophy in having sendto() et al return an error, rather than block until buffer space is available? From owner-freebsd-hackers Wed Dec 25 23:13:54 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA11321 for hackers-outgoing; Wed, 25 Dec 1996 23:13:54 -0800 (PST) Received: from hamby1.lightside.net (hamby1.lightside.net [207.67.176.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA11316 for ; Wed, 25 Dec 1996 23:13:50 -0800 (PST) Received: from localhost (jehamby@localhost) by hamby1.lightside.net (8.8.3/8.8.2) with SMTP id XAA00210 for ; Wed, 25 Dec 1996 23:13:47 -0800 (PST) X-Authentication-Warning: hamby1.lightside.net: jehamby owned process doing -bs Date: Wed, 25 Dec 1996 23:13:46 -0800 (PST) From: Jake Hamby X-Sender: jehamby@hamby1 To: hackers@freebsd.org Subject: URGENT: 2.2-BETA fails for PPP to COM3! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Danger Will Robinson! It appears that changes to sysinstall since the last time I've actively used it (2.1.5) are preventing a PPP install from working on other serial ports than COM1. Here are the issues as I understand them; I'm sorry I don't have a patch: I have three serial ports, COM1 and COM2, plus COM3 at port 0x3f8 IRQ 9. The modem (an internal Zoom 28.8) is on COM3. All three serial ports are correctly probed and recorded by the kernel and sysinstall (I had to manually enable COM3 of course). The last version of sysinstall I remember using for PPP (2.1.5) manually asked which COM port to use in a separate dialog box. The latest version shows all possible SLIP and PPP combinations in a single dialog box. No matter what you choose, however, user-mode PPP always tries /dev/cuaa0. I believe this is caused by a line in the ppp.conf file: set device cuaa0 that would be generated from the devp->devname variable in network.c. I believe that somehow the COM1 device struct is being stored for the ppp0 device, and not the serial port that the user chose. I hope this is enough information for you to figure out the problem before 2.2-RELEASE, because I would consider this a quite serious flaw! I was happy with the old way that sysinstall worked, a separate dialog box asking for COM port, and I'm curious why this was changed? P.S. A user mailed me personally about this problem (but with 2.1.6 I believe) and I forwarded him to questions. He eventually was able to install, by changing his modem to COM1 (ick!). -- Jake From owner-freebsd-hackers Wed Dec 25 23:43:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA12387 for hackers-outgoing; Wed, 25 Dec 1996 23:43:41 -0800 (PST) Received: from hamby1.lightside.net (hamby1.lightside.net [207.67.176.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA12382 for ; Wed, 25 Dec 1996 23:43:37 -0800 (PST) Received: from localhost (jehamby@localhost) by hamby1.lightside.net (8.8.3/8.8.2) with SMTP id XAA00214; Wed, 25 Dec 1996 23:43:29 -0800 (PST) X-Authentication-Warning: hamby1.lightside.net: jehamby owned process doing -bs Date: Wed, 25 Dec 1996 23:43:28 -0800 (PST) From: Jake Hamby X-Sender: jehamby@hamby1 To: "Jordan K. Hubbard" cc: hackers@freebsd.org Subject: Re: URGENT: 2.2-BETA fails for PPP to COM3! In-Reply-To: <26222.851585856@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 I _did_ try with 2.2-BETA (the latest version that you posted the MD5 checksum for tonight). I also reproduced it using COM2. Check it out again. This could be a big negative publicity if not fixed since I'd guess 99% of PC owners have a mouse on COM1 and their modem on something other. You don't need to actually start a PPP, just type "show modem" at the PPP prompt, and verify that it always shows "device: cuaa0" to reproduce the bug. -- Jake On Wed, 25 Dec 1996, Jordan K. Hubbard wrote: > > Danger Will Robinson! It appears that changes to sysinstall since the > > last time I've actively used it (2.1.5) are preventing a PPP install from > > You need to try with 2.2-BETA. This is old news. > > Jordan > > From owner-freebsd-hackers Wed Dec 25 23:46:29 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA12534 for hackers-outgoing; Wed, 25 Dec 1996 23:46:29 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA12526 for ; Wed, 25 Dec 1996 23:46:25 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id XAA26299; Wed, 25 Dec 1996 23:46:21 -0800 (PST) To: Jake Hamby cc: hackers@freebsd.org Subject: Re: URGENT: 2.2-BETA fails for PPP to COM3! In-reply-to: Your message of "Wed, 25 Dec 1996 23:43:28 PST." Date: Wed, 25 Dec 1996 23:46:21 -0800 Message-ID: <26295.851586381@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I _did_ try with 2.2-BETA (the latest version that you posted the MD5 > checksum for tonight). I also reproduced it using COM2. Check it out > again. This could be a big negative publicity if not fixed since I'd OK, all you mentioned was 2.1.5 (several times) in your article, so I think I can be forgiven for thinking that you were mentioning an old problem. :-) Sounds like my last set of fixes didn't fix it at all, which is very bizarre since the com port is being passed in as /dev/cuaa where n relates to the unit number displayed in the IP devices menu. Hmmmmmm. I'll investigate further, thanks. Jordan From owner-freebsd-hackers Thu Dec 26 01:16:39 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA15237 for hackers-outgoing; Thu, 26 Dec 1996 01:16:39 -0800 (PST) Received: from ruly46.MedFac.LeidenUniv.nl (ruly46.MedFac.LeidenUniv.nl [132.229.2.46]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA15229 for ; Thu, 26 Dec 1996 01:16:36 -0800 (PST) Received: from localhost (ruly7w.MedFac.LeidenUniv.nl [132.229.2.87]) by ruly46.MedFac.LeidenUniv.nl (8.8.4/%^)) with SMTP id KAA10217 for ; Thu, 26 Dec 1996 10:16:28 +0100 (MET) Date: Thu, 26 Dec 1996 10:17:48 +0100 (MET) From: Nick Pearson X-Sender: nick@localhost To: hackers@freebsd.org Subject: Re: URGENT: 2.2-BETA fails for PPP to COM3! 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, 25 Dec 1996, Jake Hamby wrote: > I _did_ try with 2.2-BETA (the latest version that you posted the MD5 > checksum for tonight). I also reproduced it using COM2. Check it out > again. This could be a big negative publicity if not fixed since I'd > guess 99% of PC owners have a mouse on COM1 and their modem on something > other. You don't need to actually start a PPP, just type "show modem" at > the PPP prompt, and verify that it always shows "device: cuaa0" to > reproduce the bug. > > -- Jake I've seen the same on 2.2-ALPHA when installing on a friends machine. Disabling the other com ports, i.e. the ports the modem isn't on, in the boot -c editor forces ppp onto the right port. Not brilliant but workable. Nick From owner-freebsd-hackers Thu Dec 26 03:38:15 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA17868 for hackers-outgoing; Thu, 26 Dec 1996 03:38:15 -0800 (PST) Received: from rah.star-gate.com ([204.188.121.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id DAA17862 for ; Thu, 26 Dec 1996 03:38:12 -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 DAA00365; Thu, 26 Dec 1996 03:37:19 -0800 (PST) Message-Id: <199612261137.DAA00365@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Luigi Rizzo cc: hackers@freebsd.org, Sujal Patel Subject: Re: Any support for PnP ? In-reply-to: Your message of "Wed, 25 Dec 1996 18:21:07 +0100." <199612251721.SAA20184@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 26 Dec 1996 03:37:19 -0800 From: Amancio Hasty Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Sujal Patel is the guy you want to talk to . He has code to init PnP cards available for FreeBSD . Also you may want to take a look at the GUS PnP driver which inits the GUS PnP and takes its configuration paramaters from the config file. Cheers, Amancio >From The Desk Of Luigi Rizzo : > Is there any support for PnP boards, in any release of FreeBSD or > the other free unixes (NetBSD, Linux) ? > > In case the answer is negative, is there anyone interested in > working on this ? I know this is a boring thing to do, but there > are probably strong "marketing" motivations to add such support: > More and more cards (specifically: audio and network) nowadays are > soft-configurable only. This forces users to run Windows just to > configure properly the boards, not to mention those cards which > neet to be enabled at bootstrap. > > Secondly, it might not be too hard to add such a feature: we already > have support for soft configuration with for the PCI boards, and the > specifications for PnP seem to be available on the net. There might > even be some code available, if someone has pointers I might spend > some time working on this. > > 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 Thu Dec 26 03:51:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA18124 for hackers-outgoing; Thu, 26 Dec 1996 03:51:58 -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 DAA18100; Thu, 26 Dec 1996 03:51:14 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id WAA06082; Thu, 26 Dec 1996 22:50:13 +1100 (EST) From: Julian Assange Message-Id: <199612261150.WAA06082@profane.iq.org> Subject: Trouble porting scilab To: hackers@freebsd.org, ports@freebsd.org Date: Thu, 26 Dec 1996 22:50:12 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by freefall.freebsd.org id DAA18102 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm having some difficulty with porting scilab to FreeBSD. scilab contains fortran code, the symbols from which seem to negatively effect linkage between some of the C<->C symbols. For example, x_main.o is a C object and uses _SetXsciOn, which is a C symbol from the libs/X11G.a archive. If called without any fortran objects, _SetXsciOn is resolved. It makes no difference if f77(1) or cc(1) is used to link, asside from initial entry points (_main/crt0 etc). Anyone have any idea on this? f77 -O -o bin/scilex routines/default/interf.o routines/default/bidon.o routines/default/fydot.o routines/default/fjac.o routines/default/fydotd.o routines/default/ffeval.o routines/default/foptim.o routines/default/fsolvf.o routines/default/fsolvj.o routines/default/fintg.o routines/default/fschur.o routines/default/dgetx.o routines/default/dgety.o routines/default/fres.o routines/default/fadda.o routines/default/fj2.o routines/default/fsurf.o routines/default/fsurfd.o routines/default/fresd.o routines/default/fjacd.o routines/default/fcol.o routines/default/fbutn.o routines/default/mainsci.o routines/default/scimem.o routines/default/matusr.o routines/default/matus2.o routines/default/funtab.o routines/default/msgstxt.o libs/system.a libs/interf.a libs/system2.a libs/optim.a libs/integ.a libs/control.a libs/scicos.a libs/signal.a libs/poly.a libs/calelm.a libs/lapack.a libs/X11G.a libs/sparse.a libs/metanet.a libs/sun.a libs/intersci.a libs/xwindow.a libs/xsci.a libs/comm.a -L/usr/X11R6/lib -lXaw -lXmu -lXt -lXext -lSM -lICE -lX11 -ltermcap x_charproc.o: Undefined symbol `_xscion_' referenced from text segment x_charproc.o: Undefined symbol `_xscion_' referenced from text segment x_charproc.o: Undefined symbol `_xscion_' referenced from text segment x_charproc.o: Undefined symbol `_scilab_' referenced from text segment x_main.o: Undefined symbol `_SetXsciOn' referenced from text segment x_main.o: Undefined symbol `_SGDeleteWindow' referenced from data segment x_screen.o: Undefined symbol `_scilines_' referenced from text segment x_zzledt.o: Undefined symbol `_set_is_reading' referenced from text segment x_zzledt.o: Undefined symbol `_sigbas_' referenced from text segment x_zzledt.o: Undefined symbol `_get_echo_mode' referenced from text segment x_zzledt.o: Undefined symbol `_get_echo_mode' referenced from text segment x_zzledt.o: Undefined symbol `_get_echo_mode' referenced from text segment x_zzledt.o: Undefined symbol `_set_echo_mode' referenced from text segment x_zzledt.o: Undefined symbol `_set_is_reading' referenced from text segment x_zzledt.o: Undefined symbol `_sigbas_' referenced from text segment jpc_command.o: Undefined symbol `_sciquit_' referenced from text segment jpc_command.o: Undefined symbol `_sigbas_' referenced from text segment jpc_command.o: Undefined symbol `_get_is_reading' referenced from text segment jpc_command.o: Undefined symbol `_xscion_' referenced from text segment jpc_command.o: Undefined symbol `_GetDriver_' referenced from text segment jpc_command.o: Undefined symbol `_dr_' referenced from text segment jpc_command.o: Undefined symbol `_GetDriver_' referenced from text segment jpc_command.o: Undefined symbol `_dr_' referenced from text segment jpc_command.o: Undefined symbol `_dr_' referenced from text segment jpc_command.o: Undefined symbol `_DeleteSGWin' referenced from text segment jpc_inter.o: Undefined symbol `_xscion_' referenced from text segment wf_w_file.o: Undefined symbol `_write_getfile' referenced from text segment wf_w_file.o: Undefined symbol `_cancel_getfile' referenced from text segment *** Error code 1 Stop. root@profane:/p/math/scilab/work/scilab-2.2# nm libs/X11G.a |fgrep sciOn 00000000 T _SetXsciOn From owner-freebsd-hackers Thu Dec 26 04:22:52 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA18673 for hackers-outgoing; Thu, 26 Dec 1996 04:22:52 -0800 (PST) Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA18667 for ; Thu, 26 Dec 1996 04:22:49 -0800 (PST) Received: (from guido@localhost) by gvr.win.tue.nl (8.8.4/8.8.2) id PAA05541 for freebsd-hackers@freebsd.org; Tue, 24 Dec 1996 15:24:19 +0100 (MET) From: Guido van Rooij Message-Id: <199612241424.PAA05541@gvr.win.tue.nl> Subject: username lengths To: freebsd-hackers@freebsd.org Date: Tue, 24 Dec 1996 15:24:19 +0100 (MET) 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 correct way to check what the max length of usernames on a system is? Somehow I cannot find it... -Guido From owner-freebsd-hackers Thu Dec 26 05:03:56 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA19491 for hackers-outgoing; Thu, 26 Dec 1996 05:03:56 -0800 (PST) Received: from hda.hda.com (ip1-max1-fitch.ziplink.net [199.232.245.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id FAA19486 for ; Thu, 26 Dec 1996 05:03:53 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id IAA07192; Thu, 26 Dec 1996 08:00:08 -0500 From: Peter Dufault Message-Id: <199612261300.IAA07192@hda.hda.com> Subject: Re: username lengths In-Reply-To: <199612241424.PAA05541@gvr.win.tue.nl> from Guido van Rooij at "Dec 24, 96 03:24:19 pm" To: guido@gvr.win.tue.nl (Guido van Rooij) Date: Thu, 26 Dec 1996 08:00:07 -0500 (EST) Cc: freebsd-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 > What is the correct way to check what the max length of usernames on > a system is? Somehow I cannot find it... P1003.1b-1993 section B.9.1: "POSIX.1 is silent about the content of the strings containing user or group names. These could be digit strings..." and so on. I suppose this means it could be the user's uuencoded home directory. So the complete answer is that you can't have a max length; you must use getlogin() or getpwnam() and then allocate to the string length. -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-hackers Thu Dec 26 05:18:16 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA19723 for hackers-outgoing; Thu, 26 Dec 1996 05:18:16 -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 FAA19718 for ; Thu, 26 Dec 1996 05:18:12 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id IAA00868; Thu, 26 Dec 1996 08:18:06 -0500 (EST) From: "John S. Dyson" Message-Id: <199612261318.IAA00868@dyson.iquest.net> Subject: Re: Update on Lite/2 merge? To: jehamby@lightside.com Date: Thu, 26 Dec 1996 08:18:01 -0500 (EST) Cc: hackers@freebsd.org In-Reply-To: from "Jake Hamby" at Dec 25, 96 09:01:05 pm Reply-To: dyson@freebsd.org 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 > I haven't heard anything on the Lite/2 merge yet, and I've been holding > off on doing a "make world". Can we get a brief heads-up on when to > expect those changes and what to watch out for after they occur? Thanks! > I have been having personal turmoil (Christmas, etc.) It'll be coming soon. John From owner-freebsd-hackers Thu Dec 26 05:20:29 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA19847 for hackers-outgoing; Thu, 26 Dec 1996 05:20:29 -0800 (PST) Received: from rhiannon.clari.net.au (dns1.clari.net.au [203.27.85.9]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA19840 for ; Thu, 26 Dec 1996 05:20:22 -0800 (PST) Received: (from root@localhost) by rhiannon.clari.net.au (8.7.5/8.6.12) id AAA12236 for hackers@freebsd.org; Fri, 27 Dec 1996 00:21:02 +1100 (EST) Date: Fri, 27 Dec 1996 00:21:02 +1100 (EST) From: Peter Hawkins Message-Id: <199612261321.AAA12236@rhiannon.clari.net.au> To: hackers@freebsd.org Subject: Help with sb Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have been ahving terrible problems with my sb Pro 3.1 clone. My 2.1.5 kernel was compiled with: controller snd0 device sb0 at isa? port 0x220 irq 7 conflicts drq 1 vector sbintr and on booting: Dec 24 10:59:11 rhiannon /kernel: sb0 at 0x220 irq 7 drq 1 on isa Dec 24 10:59:11 rhiannon /kernel: sb0: is detected. I have the requisite devices: lrwxrwxr-x 1 root wheel 6 Dec 26 23:30 /dev/audio -> audio0 crw-rw-rw- 1 root wheel 30, 4 Dec 27 00:03 /dev/audio0 (similar for midi etc) *yet* Whenever I try and use it, the device locks up after playing for a second or two. With nas and voxware, I can start au and use auplay. A wav file will play for about a second then freeze. The server needs to be killed (SIGKILL) and restarted before it will respond again. It is the device I suspect because rplay and raplay were similar though the server locked up after only 1/2 a second of sound and is so frozen that not even a kill -9 will kill it. If I used cat > /dev/audio I'd get a second or so of noise then nothing though ^C and then catting another file gave another second of noise so the device was not hung totally. I have a prnter also on irq7 though it was switched off at the time and even killing lpd didn't help. I assume having a sb and parallel port both on 7 is pretty standard anyway so it seems unlikely this is the problem. I've been stumped for 2 months on this and to anyone who can help me and prevent me going nutty over this I extend an offer of a pint of any beer you fancy if you meet me at the Geebung Polo Club. Peter (desperately seeking an audio guru) From owner-freebsd-hackers Thu Dec 26 05:43:09 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA20431 for hackers-outgoing; Thu, 26 Dec 1996 05:43:09 -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 FAA20426 for ; Thu, 26 Dec 1996 05:43:07 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id AAA24579; Fri, 27 Dec 1996 00:12:56 +1030 (CST) From: Michael Smith Message-Id: <199612261342.AAA24579@genesis.atrad.adelaide.edu.au> Subject: Re: Help with sb In-Reply-To: <199612261321.AAA12236@rhiannon.clari.net.au> from Peter Hawkins at "Dec 27, 96 00:21:02 am" To: peter@clari.net.au (Peter Hawkins) Date: Fri, 27 Dec 1996 00:12:55 +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 Peter Hawkins stands accused of saying: > I have been ahving terrible problems with my sb Pro 3.1 clone. My 2.1.5 > kernel was compiled with: > > controller snd0 > device sb0 at isa? port 0x220 irq 7 conflicts drq 1 vector sbintr Sharing interrupts with your parallel port is a Bad Idea. > *yet* Whenever I try and use it, the device locks up after playing > for a second or two. This is characteristic of interrupt problems. Try another interrupt. > I have a prnter also on irq7 though it was switched off at the time and > even killing lpd didn't help. I assume having a sb and parallel port both > on 7 is pretty standard anyway so it seems unlikely this is the problem. It's not "standard". It's extremely evil and should not be contemplated. -- ]] 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 Dec 26 05:47:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA20518 for hackers-outgoing; Thu, 26 Dec 1996 05:47:41 -0800 (PST) Received: from rhiannon.clari.net.au (dns1.clari.net.au [203.27.85.9]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA20511 for ; Thu, 26 Dec 1996 05:47:35 -0800 (PST) Received: (from peter@localhost) by rhiannon.clari.net.au (8.7.5/8.6.12) id AAA12747; Fri, 27 Dec 1996 00:48:18 +1100 (EST) Message-ID: X-Mailer: XFMail 0.4 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <199612261342.AAA24579@genesis.atrad.adelaide.edu.au> Date: Fri, 27 Dec 1996 00:44:39 +1100 (EST) Organization: ClariNET Internet Servies From: Peter Hawkins To: Michael Smith Subject: Re: Help with sb Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Really? Hmmm ok then though since almost all sbs use "7" out of the box as do parallel ports, I should imaging the conflict would be commonplace on most PCs bought in shops? Anyway I can try moving it though the sb has the irq hardwired. I guess I could try booting w/o the parallel port. Worth a try I guess but it seems odd to me (sbs don't give you much choice on irq and parallel ports give you none right?). Peter ---------------------------------- Peter Hawkins E-Mail: Peter Hawkins Ph: 61 3 9852 7340 ClariNET Internet Services http://www.clari.net.au ---------------------------------- From owner-freebsd-hackers Thu Dec 26 06:02:11 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA20898 for hackers-outgoing; Thu, 26 Dec 1996 06:02:11 -0800 (PST) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id GAA20893 for ; Thu, 26 Dec 1996 06:02:08 -0800 (PST) Received: by kaori.communique.net with Microsoft Exchange (IMC 4.0.837.3) id <01BBF302.C20B1150@kaori.communique.net>; Thu, 26 Dec 1996 07:59:45 -0600 Message-ID: From: Raul Zighelboim To: "'proff@suburbia.net'" Cc: "'hackers@FreeBSD.ORG'" Subject: RE: Help 'no buffer available'!! Date: Thu, 26 Dec 1996 07:59:44 -0600 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3 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 have seen the server die no long after this messages pop up, I am glad I am receiving them :-) or :-( >> >> ----kiyoko:/var/log# ping akira >> PING akira.communique.net (204.27.65.10): 56 data bytes >> 64 bytes from 204.27.65.10: icmp_seq=0 ttl=255 time=0.867 ms >> ping: sendto: No buffer space available >> ping: wrote akira.communique.net 64 chars, ret=-1 >> ping: sendto: No buffer space available > >I often get this as well. What is the philosophy in having >sendto() et al return an error, rather than block until >buffer space is available? > > From owner-freebsd-hackers Thu Dec 26 06:09:14 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA21180 for hackers-outgoing; Thu, 26 Dec 1996 06:09: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 GAA21175 for ; Thu, 26 Dec 1996 06:09:12 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id AAA24628; Fri, 27 Dec 1996 00:39:05 +1030 (CST) From: Michael Smith Message-Id: <199612261409.AAA24628@genesis.atrad.adelaide.edu.au> Subject: Re: Help with sb In-Reply-To: from Peter Hawkins at "Dec 27, 96 00:44:39 am" To: peter@clari.net.au (Peter Hawkins) Date: Fri, 27 Dec 1996 00:39:04 +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 Peter Hawkins stands accused of saying: > Really? Yes. > Hmmm ok then though since almost all sbs use "7" out of the box as do > parallel ports, I should imaging the conflict would be commonplace > on most PCs bought in shops? Rule #1: PC hardware is crap. There are exceptions to this rule, but it's a good place to start when trying to find your feet. The conflict doesn't matter to DOS and DOS-derived operating systems, because they wouldn't know what to do with an interrupt if you wrapped it in 40-grit sandpaper and inserted it backwards with a jackhammer. >From FreeBSD's point of view, with a _very_ few exceptions, IRQ conflicts are not allowed because they create potentially indeterminate, undetectable, irrecoverable hardware states. The fact that you weren't using your printer port doesn't mean that the driver didn't have the vector allocated, and it doesn't mean that it wasn't driving the IRQ 7 line inactive. > Anyway I can try moving it though the sb has the irq hardwired. I guess > I could try booting w/o the parallel port. You will have to permanently disable the printer port, or shift the other card to a different IRQ. I would recommend the latter. > Worth a try I guess but it seems odd to me (sbs don't give you much choice > on irq and parallel ports give you none right?). Printer ports are generally found at IRQ 7. FreeBSD will work with them anywhere, and even with no interrupts at all (but performance will suck). Most SB cards offer several interrupts; even my nasty old SB2.0 gives me 2, 3, 5 or 7. > Peter Hawkins -- ]] 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 Dec 26 06:30:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA21639 for hackers-outgoing; Thu, 26 Dec 1996 06:30:19 -0800 (PST) Received: from rhiannon.clari.net.au (dns1.clari.net.au [203.27.85.9]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA21630 for ; Thu, 26 Dec 1996 06:30:15 -0800 (PST) Received: (from peter@localhost) by rhiannon.clari.net.au (8.7.5/8.6.12) id BAA13479; Fri, 27 Dec 1996 01:30:57 +1100 (EST) Message-ID: X-Mailer: XFMail 0.4 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <199612261409.AAA24628@genesis.atrad.adelaide.edu.au> Date: Fri, 27 Dec 1996 01:11:28 +1100 (EST) Organization: ClariNET Internet Servies From: Peter Hawkins To: Michael Smith Subject: Re: Help with sb Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Rule #1: PC hardware is crap. There are exceptions to this rule, but >it's a good place to start when trying to find your feet. You get no argumetn here. I am *not* a PC person. I use Decstations and alphas and find PC "logic" unfathomable (hence this problem) >The conflict doesn't matter to DOS and DOS-derived operating systems, >because they wouldn't know what to do with an interrupt if you wrapped >it in 40-grit sandpaper and inserted it backwards with a jackhammer. Ahh well that would explain it. It would also be a very excellent idea as a mechanism for taking retalliation out upon IBM, INTEL and MICROSOFT. >>From FreeBSD's point of view, with a _very_ few exceptions, IRQ >conflicts are not allowed because they create potentially >indeterminate, undetectable, irrecoverable hardware states. Right, makes sense. I thought there must be something "magic" about pc interrupt s as dos allows the conflict. I couldn't imagine how you could have a conflict though. >The fact that you weren't using your printer port doesn't mean that >the driver didn't have the vector allocated, and it doesn't mean that >it wasn't driving the IRQ 7 line inactive. ah - this I did not know. >> Anyway I can try moving it though the sb has the irq hardwired. I guess >> I could try booting w/o the parallel port. > >You will have to permanently disable the printer port, or shift the >other card to a different IRQ. I would recommend the latter. Sadly, just about impossible. I have a choice of 7 (hardwired to printer) and 10 (hardwired to cyclades :(. >Printer ports are generally found at IRQ 7. FreeBSD will work with them >anywhere, and even with no interrupts at all (but performance will suck). Does it take a kernel recompile to move it? I assume you do not need to jumper anything. What if I just set the printer driver into polled mode? (actually I think that's how I had it) >Most SB cards offer several interrupts; even my nasty old SB2.0 gives me >2, 3, 5 or 7. 3 = sio1 (mouse) 5 = my WD8003e (can goto 3 but that is sio1) *sigh* Peter From owner-freebsd-hackers Thu Dec 26 06:32:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA21733 for hackers-outgoing; Thu, 26 Dec 1996 06:32:06 -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 GAA21728 for ; Thu, 26 Dec 1996 06:32:03 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id BAA24677 for hackers@freebsd.org; Fri, 27 Dec 1996 01:02:01 +1030 (CST) From: Michael Smith Message-Id: <199612261432.BAA24677@genesis.atrad.adelaide.edu.au> Subject: Wavelan driver testers? To: hackers@freebsd.org Date: Fri, 27 Dec 1996 01:02:00 +1030 (CST) 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've taken Jim Binkley's Wavelan drivers (ISA cards only) for 2.1.0 and ported them to 2.2 with a few minor modifications. I'm now looking for a few interested parties to test the driver before I commit it to -current. Naturally, I'm also looking for a reviewer for this. Please let me know if you're interested in either case. Please note that the cards I used for the port are only on loan, and I'll have to return them on 11/1, so I'd like to have things tidy by then. If at all possible, I'll try to get the driver into the 'experimental' directory on the 2.2 CDROM. (Garrett; I've cc'd you on this as I seem to recall that you don't follow -hackers. My apologies if I've spammed 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 Thu Dec 26 06:59:00 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA23075 for hackers-outgoing; Thu, 26 Dec 1996 06:59:00 -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 GAA23065 for ; Thu, 26 Dec 1996 06:58:57 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hydrogen.nike.efn.org (8.8.4/8.8.4) with SMTP id GAA25878; Thu, 26 Dec 1996 06:58:44 -0800 (PST) Date: Thu, 26 Dec 1996 06:58:44 -0800 (PST) From: John-Mark Gurney X-Sender: jmg@hydrogen Reply-To: John-Mark Gurney To: Peter Hawkins cc: hackers@freebsd.org Subject: Re: Help with sb In-Reply-To: <199612261321.AAA12236@rhiannon.clari.net.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 Fri, 27 Dec 1996, Peter Hawkins wrote: > *yet* Whenever I try and use it, the device locks up after playing > for a second or two. sounds like your sound card is possibly not set to irq7.. but something else... a second of sound and then nothing more usally signifies that it isn't recieveing the irq for it... I have a SB Pro v3.1 myself... nice card... > I have a prnter also on irq7 though it was switched off at the time and > even killing lpd didn't help. I assume having a sb and parallel port both > on 7 is pretty standard anyway so it seems unlikely this is the problem. > I've been stumped for 2 months on this and to anyone who can help me > and prevent me going nutty over this I extend an offer of a pint of > any beer you fancy if you meet me at the Geebung Polo Club. well... it'll have to be about three years before I can take you up on that :)... 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 Thu Dec 26 07:40:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA24569 for hackers-outgoing; Thu, 26 Dec 1996 07:40:06 -0800 (PST) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [207.95.42.241]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA24512; Thu, 26 Dec 1996 07:39:59 -0800 (PST) Received: from dingo.its.enc.edu (dingo.its.enc.edu [207.95.222.250]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id KAA24833; Thu, 26 Dec 1996 10:35:26 -0500 (EST) Date: Thu, 26 Dec 1996 10:41:59 -0500 (EST) From: Charles Owens X-Sender: owensc@dingo.its.enc.edu Reply-To: Charles Owens To: Snob Art Genre cc: hackers@freebsd.org, questions@freebsd.org Subject: Re: multi-group file access techniques 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, 18 Dec 1996, Snob Art Genre wrote: > On Wed, 18 Dec 1996, Charles Owens wrote: > > > .../man_readable_c is a "control directory," a technique that seems > > obvious to me now but was new to me when I read of it in "Techniques for > > Simulating Multiple Group Ownership," by Doug Morris, from the October > > issue of SysAdmin magazine. > > What's a control directory? Basicly an extra directory thrown in to allow an additional type of access via the group permissions (typically). Any given directory or file can belong to just one group, which is a royal pain. The control directory provides a means to simulate multiple group ownership in a limited fashion. Back to the example from my posting (to which only you replied: grrrr...): Owner Group Mode man_readable_c eng2_member eng1 drwxr-x--- | +- man_readable eng2_member eng2 drwxrwxr-x | +- (files) eng2_member eng2 -rwxrwxr-x Here the goal is to allow one group (eng2, who also should belong to group eng1) to have read+write access and another group (eng1) to have just read access. Members of eng1 access the contents of man_readable_c via that directory's group permissions. The, eng1 members can gain read-only access to the contents of man_readable via man_readable's 'other' permission field. > > In his article, Doug Morris also speaks of a technique of using hard links > > of directories to achieve a similar effect. This technique could be used > > in tandem with the above to add more flexibility, but we all know the > > GREAT EVIL that hard linked directories are. :-) > > And why are hard-linked directories evil? > > > Thanks in advance for any and all response, I don't have a complete understanding of the technical issues, but from what other have said I've gotten the general impression that using them can often (if not always) lead to the corruption of the file system. Do a search of the hackers discussion list for the string "hard linked directories." There were quite a number of illuminating posts on this particular topic a few months ago. >From what I've gleaned from these postings, one of the biggest problems with them is the potential for creating loops in the file tree, which fsck is generally very unhappy about. If one is very careful not to create such loops _is_ it possible to safely employ hard-linked directories (and keep fsck happy) ? I can certainly see that they're very dangerous, but can they be used safely with FreeBSD? Anyone? > Ha! Bet you weren't expecting questions instead of answers. :) Hey.. why not?! Discussion is always a nice thing! :-) --- ------------------------------------------------------------------------- Charles Owens Email: owensc@enc.edu "I read somewhere to learn is to Information Technology Services remember... and I've learned that Eastern Nazarene College we've all forgot..." - King's X ------------------------------------------------------------------------- From owner-freebsd-hackers Thu Dec 26 07:48:02 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA24738 for hackers-outgoing; Thu, 26 Dec 1996 07:48:02 -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 HAA24721; Thu, 26 Dec 1996 07:47:59 -0800 (PST) Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.6.12/8.6.9) with SMTP id KAA03090; Thu, 26 Dec 1996 10:52:47 -0500 Message-Id: <3.0.32.19961226104713.00ae68a0@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Thu, 26 Dec 1996 10:47:15 -0500 To: Luigi Rizzo From: dennis Subject: Re: ipretard.c selective tcp/ip queues and throughput limiters Cc: isp@freebsd.org, 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 09:24 PM 12/23/96 +0100, you wrote: >> Luigi Rizzo wrote: > >> > very useful. The only drawback is the overhead that this (and basically >> > everything using the divert socket) has: packets move to user space and >> > back, something you don't want to do on high-speed traffic. >. >> but as Kieth sklower at CSRG told me.. >> There's got to be a way to make it possible for essoteric or unusual >> modules to be implimented OUT OF THE KERNEL, or >> they are >> (1) hard to prototype >> (2) increasing the complexity of what IS in the kernel beyond the >> point of debuggability :) > >which is why I like very much the idea of divert sockets, tun devices >and similar things, but only when used in the proper way (e.g. >prototyping and/or slow speeds). Our "soon-to-be-released" version 2.0 of ET/BWMGR does this inline, and will provide for precise, bidirectional bandwidth allocation and control by data type (ie, http, ftp, IP address, etc) and is specifically designed for high speed systems With a few rules there is no noticable overhead. It will allow ISPs and corporate administrators to control the traffic of individual workstations, networks or the entire intranet without adversly affecting the routers performance or other traffic. So you could, for example, limit ftp downloads to 512k on a T1, guarantee a specific bandwidth for outgoing http traffic or limit video traffic to 56k to guarantee bandwidth availability for other critical services. Dennis Emerging Technologies, Inc. Router cards for BSD/OS, FreeBSD and Linux Standalone Routers Bandwidth Manager http://www.etinc.com sales@etinc.com (516) 271-4525 From owner-freebsd-hackers Thu Dec 26 07:52:40 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA24886 for hackers-outgoing; Thu, 26 Dec 1996 07:52:40 -0800 (PST) Received: from rhiannon.clari.net.au (dns1.clari.net.au [203.27.85.9]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA24881 for ; Thu, 26 Dec 1996 07:52:37 -0800 (PST) Received: (from peter@localhost) by rhiannon.clari.net.au (8.7.5/8.6.12) id CAA00489; Fri, 27 Dec 1996 02:52:22 +1100 (EST) Message-ID: X-Mailer: XFMail 0.4 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 27 Dec 1996 02:51:50 +1100 (EST) Organization: ClariNET Internet Servies From: Peter Hawkins To: John-Mark Gurney Subject: Re: Help with sb Cc: John-Mark Gurney , hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John-Mark Thankyou and I've fixed it. You get a beer when you're next here. Peter > >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) > ---------------------------------- Peter Hawkins E-Mail: Peter Hawkins Ph: 61 3 9852 7340 ClariNET Internet Services http://www.clari.net.au ---------------------------------- From owner-freebsd-hackers Thu Dec 26 07:56:35 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA24995 for hackers-outgoing; Thu, 26 Dec 1996 07:56:35 -0800 (PST) Received: from rhiannon.clari.net.au (dns1.clari.net.au [203.27.85.9]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA24990 for ; Thu, 26 Dec 1996 07:56:32 -0800 (PST) Received: (from peter@localhost) by rhiannon.clari.net.au (8.7.5/8.6.12) id CAA00540; Fri, 27 Dec 1996 02:56:19 +1100 (EST) Message-ID: X-Mailer: XFMail 0.4 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <199612261342.AAA24579@genesis.atrad.adelaide.edu.au> Date: Fri, 27 Dec 1996 02:54:04 +1100 (EST) Organization: ClariNET Internet Servies From: Peter Hawkins To: Michael Smith , hackers@freebsd.org Subject: Re: Help with sb Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thankyou for those who helped. It was indeed the interrupt clash. Moving my ed1 to irq 9 via 2 freed up irq 5 for sdn0 and it works fine. For the record, it seems that dos does not use the printer's irq properly hence it is possible to steal irq 7 (according to those who helped me). In FreeBSD it is not valid to do this. Peter ---------------------------------- Peter Hawkins E-Mail: Peter Hawkins Ph: 61 3 9852 7340 ClariNET Internet Services http://www.clari.net.au ---------------------------------- From owner-freebsd-hackers Thu Dec 26 08:21:45 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA26439 for hackers-outgoing; Thu, 26 Dec 1996 08:21:45 -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 IAA26426 for ; Thu, 26 Dec 1996 08:21:38 -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 RAA11369; Thu, 26 Dec 1996 17:21:19 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id RAA12857; Thu, 26 Dec 1996 17:21:18 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id RAA20780; Thu, 26 Dec 1996 17:12:50 +0100 (MET) From: J Wunsch Message-Id: <199612261612.RAA20780@uriah.heep.sax.de> Subject: Re: Help with sb To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Thu, 26 Dec 1996 17:12:48 +0100 (MET) Cc: peter@clari.net.au (Peter Hawkins) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Peter Hawkins at "Dec 27, 96 01:11:28 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 Peter Hawkins wrote: > Does it take a kernel recompile to move it? No, you can change it by booting with -c. > jumper anything. What if I just set the printer driver into polled mode? > (actually I think that's how I had it) It will burn many CPU cycles in tight loops then. > 3 = sio1 (mouse) > 5 = my WD8003e (can goto 3 but that is sio1) Put an expansion card into the second half of an ISA slot, and use IRQ 11 or IRQ 12. If your soundcard has all the contact pads on it, you might be able to solder a wire as well. -- 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 Dec 26 08:21:51 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA26463 for hackers-outgoing; Thu, 26 Dec 1996 08:21:51 -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 IAA26446 for ; Thu, 26 Dec 1996 08:21: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 RAA11363; Thu, 26 Dec 1996 17:21:17 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id RAA12856; Thu, 26 Dec 1996 17:21:17 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id RAA16953; Thu, 26 Dec 1996 17:09:51 +0100 (MET) From: J Wunsch Message-Id: <199612261609.RAA16953@uriah.heep.sax.de> Subject: Re: Help with sb To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Thu, 26 Dec 1996 17:09:41 +0100 (MET) Cc: peter@clari.net.au Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612261409.AAA24628@genesis.atrad.adelaide.edu.au> from Michael Smith at "Dec 27, 96 00:39:04 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 Michael Smith wrote: > You will have to permanently disable the printer port, or shift the > other card to a different IRQ. I would recommend the latter. You can run the printer driver without IRQs if you've got no other option. Of course, this will make it a CPU burner. It's only been invented to support printers or cables with a broken ACK signal. > Printer ports are generally found at IRQ 7. Many of them offer the option for IRQ 5 since this used to be the `official' LPT2 IRQ before IRQ lines got scarce, so IRQ 5 later became relabelled as ``generic IRQ''. -- 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 Dec 26 08:41:12 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA26901 for hackers-outgoing; Thu, 26 Dec 1996 08:41:12 -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 IAA26896 for ; Thu, 26 Dec 1996 08:41:08 -0800 (PST) Received: (from uucp@localhost) by smtp-gw01.ny.us.ibm.net (8.6.9/8.6.9) id QAA300214 for ; Thu, 26 Dec 1996 16:41:07 GMT Message-Id: <199612261641.QAA300214@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 sman6UDM2; Thu Dec 26 16:41:00 1996 Reply-To: From: "Steve Sims" To: "Hackers" Subject: `make world` won't Date: Thu, 26 Dec 1996 11:39:59 -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 This morning, much to my surprise, `make world` barfed after cvsup'ing -CURRENT. # make update world -------------------------------------------------------------- make world started on Thu Dec 26 11:38:22 EST 1996 -------------------------------------------------------------- -------------------------------------------------------------- Making hierarchy -------------------------------------------------------------- cd /usr/src && make hierarchy cd /usr/src/etc && make distrib-dirs [blah, blah, snip] -------------------------------------------------------------- Rebuilding /usr/share/mk -------------------------------------------------------------- cd /usr/src && make mk cd /usr/src/share/mk && make install [blah, blah, snip] -------------------------------------------------------------- Cleaning up the source tree -------------------------------------------------------------- cd /usr/src && make cleandir ===> include rm -f a.out Errs errs mklog osreldate.h version vers.c ===> include/rpcsvc rm -f a.out Errs errs mklog klm_prot.h mount.h nfs_prot.h nlm_prot.h rex.h rnusers.h rquota.h rstat.h rwall.h sm_inter.h spray.h yppasswd.h yp.h ypxfrd.h ===> include/rpcsvc rm -f a.out Errs errs mklog klm_prot.h mount.h nfs_prot.h nlm_prot.h rex.h rnusers.h rquota.h rstat.h rwall.h sm_inter.h spray.h yppasswd.h yp.h ypxfrd.h ===> lib ===> lib/csu/i386 ===> lib/libc ===> lib/libcompat ===> lib/libcom_err pwd: No such file or directory *** Error code 2 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. # Doh! Any clues? I'm using Polstra's (most excellent!) cvsup 14.0 with the plain-vanilla /usr/share/examples/cvsup/standard-supfile. ...sjs... From owner-freebsd-hackers Thu Dec 26 08:52:25 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA27186 for hackers-outgoing; Thu, 26 Dec 1996 08:52:25 -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 IAA27180 for ; Thu, 26 Dec 1996 08:52:20 -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 RAA14058; Thu, 26 Dec 1996 17:50:56 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id RAA13333; Thu, 26 Dec 1996 17:50:56 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id RAA08400; Thu, 26 Dec 1996 17:29:32 +0100 (MET) From: J Wunsch Message-Id: <199612261629.RAA08400@uriah.heep.sax.de> Subject: Re: multi-group file access techniques To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Thu, 26 Dec 1996 17:29:31 +0100 (MET) Cc: ben@narcissus.ml.org, owensc@enc.edu Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Charles Owens at "Dec 26, 96 10:41:59 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 Charles Owens wrote: > >From what I've gleaned from these postings, one of the biggest problems > with them is the potential for creating loops in the file tree, which fsck > is generally very unhappy about. If one is very careful not to create Our fsck were always very unhappy about additional hardlinks to directories. > such loops _is_ it possible to safely employ hard-linked directories (and > keep fsck happy) ? I can certainly see that they're very dangerous, but > can they be used safely with FreeBSD? Anyone? Directory hardlinks are impossible in FreeBSD. They have been discontinued quite some time ago. -- 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 Dec 26 08:52:29 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA27202 for hackers-outgoing; Thu, 26 Dec 1996 08:52:29 -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 IAA27187 for ; Thu, 26 Dec 1996 08:52:25 -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 RAA14072; Thu, 26 Dec 1996 17:50:59 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id RAA13335; Thu, 26 Dec 1996 17:50:58 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id RAA09725; Thu, 26 Dec 1996 17:31:13 +0100 (MET) From: J Wunsch Message-Id: <199612261631.RAA09725@uriah.heep.sax.de> Subject: Re: Help with sb To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Thu, 26 Dec 1996 17:31:12 +0100 (MET) Cc: peter@clari.net.au (Peter Hawkins) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Peter Hawkins at "Dec 27, 96 02:54:04 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 Peter Hawkins wrote: > For the record, it seems that dos does not use the printer's irq properly > hence it is possible to steal irq 7 (according to those who helped me). DOS uses polled printing. I'm not sure about Windows versions, i assume at least NT will also use interrupt-driven printing if possible. -- 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 Dec 26 09:30:12 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA28095 for hackers-outgoing; Thu, 26 Dec 1996 09:30:12 -0800 (PST) Received: from fly.HiWAAY.net (sprice@fly.HiWAAY.net [208.147.154.56]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA28088 for ; Thu, 26 Dec 1996 09:30:11 -0800 (PST) Received: from localhost by fly.HiWAAY.net; (8.8.4/1.1.8.2/21Sep95-1003PM) id LAA13977; Thu, 26 Dec 1996 11:30:05 -0600 (CST) Date: Thu, 26 Dec 1996 11:30:05 -0600 (CST) From: Steve Price To: Steve Sims cc: Hackers Subject: Re: `make world` won't In-Reply-To: <199612261641.QAA300214@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 Thu, 26 Dec 1996, Steve Sims wrote: # This morning, much to my surprise, `make world` barfed after cvsup'ing # -CURRENT. # # ... # pwd: No such file or directory # *** Error code 2 # This problem is known and fixed. The trail of comments is in the mailing list archives. To fix the problem you need to update these two files in src/bin/sh: main.c (1.11) cd.c (1.11) Steve PS: If you can't get these files let me know and I will get them for you. # # Doh! Any clues? I'm using Polstra's (most excellent!) cvsup 14.0 with the # plain-vanilla /usr/share/examples/cvsup/standard-supfile. # # ...sjs... # From owner-freebsd-hackers Thu Dec 26 09:37:13 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA28344 for hackers-outgoing; Thu, 26 Dec 1996 09:37:13 -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 JAA28339 for ; Thu, 26 Dec 1996 09:37:10 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id EAA24737; Fri, 27 Dec 1996 04:35:19 +1100 Date: Fri, 27 Dec 1996 04:35:19 +1100 From: Bruce Evans Message-Id: <199612261735.EAA24737@godzilla.zeta.org.au> To: freebsd-hackers@freebsd.org, j@uriah.heep.sax.de Subject: Re: Help with sb Cc: peter@clari.net.au Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Does it take a kernel recompile to move it? > >No, you can change it by booting with -c. `lptcontrol -p' can be used to stop the printer generating interrupts, but there is no way to connect the sb or lpt to the interrupt if it isn't already - the first one configured grabs the interrupt vector and the error for the other not being able to allocate the vector is silently ignored. >> jumper anything. What if I just set the printer driver into polled mode? >> (actually I think that's how I had it) > >It will burn many CPU cycles in tight loops then. The driver was so braindamaged that this was required for many printers with working interrupts anyway. Joerg improved the driver, but it's not clear if the polling code is still useful since no one complains about working code :-). Bruce From owner-freebsd-hackers Thu Dec 26 10:22:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA01394 for hackers-outgoing; Thu, 26 Dec 1996 10: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 KAA01386 for ; Thu, 26 Dec 1996 10:22: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 TAA22188; Thu, 26 Dec 1996 19:21:10 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA16071; Thu, 26 Dec 1996 19:21:10 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id TAA02654; Thu, 26 Dec 1996 19:01:40 +0100 (MET) From: J Wunsch Message-Id: <199612261801.TAA02654@uriah.heep.sax.de> Subject: Re: Help with sb To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Thu, 26 Dec 1996 19:01:39 +0100 (MET) Cc: peter@clari.net.au Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612261735.EAA24737@godzilla.zeta.org.au> from Bruce Evans at "Dec 27, 96 04:35:19 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 Bruce Evans wrote: > >It will burn many CPU cycles in tight loops then. > > The driver was so braindamaged that this was required for many printers > with working interrupts anyway. Joerg improved the driver, but it's not > clear if the polling code is still useful since no one complains about > working code :-). Well, now that you mention it, indeed, it's been me... I almost forgot about this. :-) But you're right, it's quite possible that it works in interrupt mode now for all printers that generated the ACK signal at all (and for all cables that properly wire it, of course). -- 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 Dec 26 10:22:43 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA01442 for hackers-outgoing; Thu, 26 Dec 1996 10:22:43 -0800 (PST) Received: from trinity.radio-do.de (fn@trinity.Radio-do.de [193.101.164.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA01436 for ; Thu, 26 Dec 1996 10:22:37 -0800 (PST) Received: by trinity.radio-do.de (8.7.6/CLIENT-1.2.7-h) via EUnet id TAA11392; Thu, 26 Dec 1996 19:22:05 +0100 (MET) To: hackers@freebsd.org Cc: Michael Smith , Peter Hawkins Subject: Re: Help with sb References: From: Frank Nobis Date: 26 Dec 1996 19:22:05 +0100 In-Reply-To: Peter Hawkins's message of Fri, 27 Dec 1996 01:11:28 +1100 (EST) Message-ID: Lines: 39 X-Mailer: Red Gnus v0.74/XEmacs 19.14 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> "Peter" == Peter Hawkins writes: >> Printer ports are generally found at IRQ 7. FreeBSD will work >> with them anywhere, and even with no interrupts at all (but >> performance will suck). Peter> Does it take a kernel recompile to move it? I assume you do Peter> not need to jumper anything. What if I just set the printer Peter> driver into polled mode? (actually I think that's how I Peter> had it) You can boot the kernel with -c option and disable the IRQ 7 for your printer. This will work untill you install a new kernel and forget to change the kernel config file too. I am running my old deskjet without an IRQ and the performance is not that bad at all. >> Most SB cards offer several interrupts; even my nasty old SB2.0 >> gives me 2, 3, 5 or 7. Peter> 3 = sio1 (mouse) 5 = my WD8003e (can goto 3 but that is Peter> sio1) At boot time I see: Dec 9 20:35:11 trinity /kernel: lpt0 at 0x3bc-0x3c3 on isa ... Dec 9 20:35:12 trinity /kernel: sb0 at 0x220 irq 7 drq 1 on isa Dec 9 20:35:12 trinity /kernel: sb0: Dec 9 20:35:12 trinity /kernel: opl0 at 0x388 on isa Dec 9 20:35:12 trinity /kernel: opl0: Gruss Frank -- Frank Nobis Email: fn@Radio-do.de PGP AVAILABLE Landgrafenstr. 130 dg3dcn http://www.radio-do.de/~fn/ 44139 Dortmund Powered by FreeBSD Fax: +49 231 7213816 From owner-freebsd-hackers Thu Dec 26 11:37:22 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA04960 for hackers-outgoing; Thu, 26 Dec 1996 11:37:22 -0800 (PST) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [207.95.42.241]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA04954 for ; Thu, 26 Dec 1996 11:37:20 -0800 (PST) Received: from dingo.its.enc.edu (dingo.its.enc.edu [207.95.222.250]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id OAA26095; Thu, 26 Dec 1996 14:33:37 -0500 (EST) Date: Thu, 26 Dec 1996 14:40:15 -0500 (EST) From: Charles Owens X-Sender: owensc@dingo.its.enc.edu Reply-To: Charles Owens To: J Wunsch cc: FreeBSD hackers , ben@narcissus.ml.org Subject: Re: multi-group file access techniques / directory hardlinks In-Reply-To: <199612261629.RAA08400@uriah.heep.sax.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 Thu, 26 Dec 1996, J Wunsch wrote: > As Charles Owens wrote: > > > >From what I've gleaned from these postings, one of the biggest problems > > with them is the potential for creating loops in the file tree, which fsck > > is generally very unhappy about. If one is very careful not to create > > Our fsck were always very unhappy about additional hardlinks to > directories. > > > such loops _is_ it possible to safely employ hard-linked directories (and > > keep fsck happy) ? I can certainly see that they're very dangerous, but > > can they be used safely with FreeBSD? Anyone? > > Directory hardlinks are impossible in FreeBSD. They have been > discontinued quite some time ago. Uhhh... well, sort of. At least as of 2.1.6 it is still possible to use ln(1) to create directory hardlinks using an undocumented flag. This, along with some other observations suggests to me the following: 1. The file system does in fact support directory hardlinks. (This is true at least to some extent, since the '.' and '..' entries are, in fact, directory hardlinks.) 2. Certain key tools do _not_ understand directory hardlinks. The ones that I know of are fsck, rm, and rmdir. 3. The official FreeBSD stance (that I seem to be hearing) that directory hardlinks are unsupported is based on: a. the insufficient status of the tool support (previous point) - and/or - b. the fact that directory hardlinks are dangerous in the hands of the uncareful. Am I correct here? Would someone in the know provide clarification? As I stated in my original posting (on Dec 18), my goal is to come up with an optimum technique for allowing multiple groups controlled access to a file tree. (To my surprise, I had very little response to this posting, which deals with what I think is a rather interesting challenge. If you'd like me to repost, please holler). Essentially I'm trying to achieve a subset of the functionality offered by Access Control Lists as implemented in AIX et al. A recent *article in 'Sys Admin' deals with this problem. One of the two techniques suggested relies on the use of directory hardlinks, which is why I'm currently interested in the topic. Although they more or less do what I want I'm not thrilled with either of the techniques and was hoping that someone here had some other suggestions. Please see my original posting for more details. Thanks * Morris, Doug. "Techniques for Simulating Multiple Group Access," _Sys_Admin_. October 1996, page 71. --- ------------------------------------------------------------------------- Charles Owens Email: owensc@enc.edu "I read somewhere to learn is to Information Technology Services remember... and I've learned that Eastern Nazarene College we've all forgot..." - King's X ------------------------------------------------------------------------- From owner-freebsd-hackers Thu Dec 26 12:31:47 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA06294 for hackers-outgoing; Thu, 26 Dec 1996 12:31:47 -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 MAA06289 for ; Thu, 26 Dec 1996 12:31:43 -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 MAA29473; Thu, 26 Dec 1996 12:27:55 -0800 (PST) Message-ID: <32C2DF8C.167EB0E7@whistle.com> Date: Thu, 26 Dec 1996 12:26:52 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Charles Owens CC: J Wunsch , FreeBSD hackers , ben@narcissus.ml.org Subject: Re: multi-group file access techniques / directory hardlinks References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Charles Owens wrote: > 1. The file system does in fact support directory hardlinks. (This is > true at least to some extent, since the '.' and '..' entries are, > in fact, directory hardlinks.) see below. > > 2. Certain key tools do _not_ understand directory hardlinks. The ones > that I know of are fsck, rm, and rmdir. > > 3. The official FreeBSD stance (that I seem to be hearing) that > directory hardlinks are unsupported is based on: > > a. the insufficient status of the tool support (previous point) > - and/or - > b. the fact that directory hardlinks are dangerous in the > hands of the uncareful. > > Am I correct here? Would someone in the know provide clarification? the KERNEL now disallows the 'link' operation on directories. > > As I stated in my original posting (on Dec 18), my goal is to come up with > an optimum technique for allowing multiple groups controlled access to a > file tree. (To my surprise, I had very little response to this posting, > which deals with what I think is a rather interesting challenge. If you'd > like me to repost, please holler). Essentially I'm trying to achieve a > subset of the functionality offered by Access Control Lists as implemented > in AIX et al. I never saw the original posting. From owner-freebsd-hackers Thu Dec 26 12:54:25 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA06903 for hackers-outgoing; Thu, 26 Dec 1996 12:54:25 -0800 (PST) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [207.95.42.241]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA06897 for ; Thu, 26 Dec 1996 12:54:23 -0800 (PST) Received: from dingo.its.enc.edu (dingo.its.enc.edu [207.95.222.250]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id PAA26408 for ; Thu, 26 Dec 1996 15:51:03 -0500 (EST) Date: Thu, 26 Dec 1996 15:57:42 -0500 (EST) From: Charles Owens X-Sender: owensc@dingo.its.enc.edu To: hackers@freebsd.org Subject: multi-group file access techniques (repost) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Here's the original post in case you missed it. Sorry for the etiquette breach... :-) --- Charles Owens Email: owensc@enc.edu Subject: multi-group file access techniques Howdy, I'm trying to grapple with the challenge of how to allow multiple groups and users (but not everyone) to have access to a directory hierarchy. We don't have ACL's in FreeBSD, so I'm finding it a bit tricky. Below is an example of what I need to do. If you have any insights, alternate approaches, please let me know! My goal is to set up a flexible way of organizing permissions such that collections of users can share files with security where needed. An integral part of the picture is http access, so the user (or group) 'www' also needs read access (unless I run Apache as root, which I don't think I want to do). [Web access permissions (via .htaccess or access.conf) are a separate issue -- let's just limit the discussion to file system access issues]. First let's define what I mean by a "group hierarchy". Basicly, it's a collection of groups associated with a single entity, such as a department, each with a different privilege level. An example: Group Hierarchy 'Engineering' Group Name Membership eng anyone associated with department eng1 full time staff eng2 managers eng3 administrators In implementing this, member users would belong to all groups within the hierarchy down to the level appropriate for them (so a manager would belong to groups eng, eng1, and eng2). What would this look like in practice? Owner Group Mode /dept/eng root eng drwxrwx--- | +- man_only eng2_member eng2 drwxrwx--- | | | (files) | +- man_readable_c eng2_member eng1 drwxr-x--- | +- man_readable eng2_member eng2 drwxrwxr-x | (files) Here managers (members of eng, eng1 and eng2 groups) can have full access to everything. Staff (belonging to eng and eng1) have RW access to /dept/eng, but just read to /dept/eng/man_readable_c/man_readable. .../man_readable_c is a "control directory," a technique that seems obvious to me now but was new to me when I read of it in "Techniques for Simulating Multiple Group Ownership," by Doug Morris, from the October issue of SysAdmin magazine. This seems reasonably workable, but there's no provision to allow the user or group 'www' to have read access. Adding this access into the above scheme seems possible, but a bit goofy. I've achieved it below simply by making 'www' the owner of all "choke point" directories: Owner Group Mode /dept/eng_c www eng dr-xrwx--- | +- man_only www eng2 dr-xrwx--- | | | (files) | +- man_readable_c www eng1 dr-xr-x--- | +- man_readable eng2_member eng2 drwxrwxr-x | (files) This does work, but has two obvious flaws: 1. Security - the user "www" should _not_ have to own the directories 2. Ease of use - a normal user could not achieve the above configuration with normal file system commands. Certainly, though, a few setuid utilities could be written to make this possible... What other approaches exist? Comments? Critiques? In his article, Doug Morris also speaks of a technique of using hard links of directories to achieve a similar effect. This technique could be used in tandem with the above to add more flexibility, but we all know the GREAT EVIL that hard linked directories are. :-) (Morris's article forces me to ask, though, if hard linked directories are actually okay for other OS's, perhaps non-BSD ones?) Thanks in advance for any and all response, --- ------------------------------------------------------------------------- Charles Owens Email: owensc@enc.edu "I read somewhere to learn is to Information Technology Services remember... and I've learned that Eastern Nazarene College we've all forgot..." - King's X ------------------------------------------------------------------------- From owner-freebsd-hackers Thu Dec 26 13:03:51 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA07469 for hackers-outgoing; Thu, 26 Dec 1996 13:03:51 -0800 (PST) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [207.95.42.241]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA07460 for ; Thu, 26 Dec 1996 13:03:47 -0800 (PST) Received: from dingo.its.enc.edu (dingo.its.enc.edu [207.95.222.250]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id PAA26430; Thu, 26 Dec 1996 15:59:37 -0500 (EST) Date: Thu, 26 Dec 1996 16:06:16 -0500 (EST) From: Charles Owens X-Sender: owensc@dingo.its.enc.edu To: Julian Elischer cc: J Wunsch , FreeBSD hackers , ben@narcissus.ml.org Subject: Re: multi-group file access techniques / directory hardlinks In-Reply-To: <32C2DF8C.167EB0E7@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 On Thu, 26 Dec 1996, Julian Elischer wrote: > Charles Owens wrote: > > > 1. The file system does in fact support directory hardlinks. (This is > > true at least to some extent, since the '.' and '..' entries are, > > in fact, directory hardlinks.) > > see below. > > > > > 2. Certain key tools do _not_ understand directory hardlinks. The ones > > that I know of are fsck, rm, and rmdir. > > > > 3. The official FreeBSD stance (that I seem to be hearing) that > > directory hardlinks are unsupported is based on: > > > > a. the insufficient status of the tool support (previous point) > > - and/or - > > b. the fact that directory hardlinks are dangerous in the > > hands of the uncareful. > > > > Am I correct here? Would someone in the know provide clarification? > > the KERNEL now disallows the 'link' operation on directories. Ok... that's very clear, but a bit terse. :-) What I'm digging for above is an expression of the rationale for this disabling (_not_ that I disagree). I certainly can see that directory hard linking should be disabled as long as support in the basic tools (rm, rmdir, fsck) is incomplete (otherwise it's a major head-ache for the user). ...But if the tool support was made complete I'm not so sure that this kernal disabling is the way to go. Perhaps there could be a options flag in the kernal config file to force directory linking to be allowed for those who need it. > > > > > As I stated in my original posting (on Dec 18), my goal is to come up with > > an optimum technique for allowing multiple groups controlled access to a > > file tree. (To my surprise, I had very little response to this posting, > > which deals with what I think is a rather interesting challenge. If you'd > > like me to repost, please holler). Essentially I'm trying to achieve a > > subset of the functionality offered by Access Control Lists as implemented > > in AIX et al. > > I never saw the original posting. I've reposted it... --- ------------------------------------------------------------------------- Charles Owens Email: owensc@enc.edu "I read somewhere to learn is to Information Technology Services remember... and I've learned that Eastern Nazarene College we've all forgot..." - King's X ------------------------------------------------------------------------- From owner-freebsd-hackers Thu Dec 26 14:10:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA11722 for hackers-outgoing; Thu, 26 Dec 1996 14:10:41 -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 OAA11717; Thu, 26 Dec 1996 14:10:38 -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 QAA03410; Thu, 26 Dec 1996 16:10:36 -0600 (CST) Received: from localhost by solaria.sol.net (8.5/8.5) id QAA07831; Thu, 26 Dec 1996 16:10:34 -0600 From: Joe Greco Message-Id: <199612262210.QAA07831@solaria.sol.net> Subject: Re: Help 'no buffer available'!! To: dg@root.com Date: Thu, 26 Dec 96 16:10:33 CST Cc: mango@staff.communique.net, hackers@freefall.freebsd.org, questions@freefall.freebsd.org In-Reply-To: <199612260218.SAA04304@root.com> from "David Greenman" at Dec 25, 96 06:18:47 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 > >My kernel details" > > > >options "CHILD_MAX=512" > >options "OPEN_MAX=1024" > >options "MAXMEM=262144" > >options "NMBCLUSTERS=4096" > >options "EXTRAVNODES=30000" <----- this is not a real option on > >2.1.6 > >options "NBUF=4096" > > I don't know off hand what is causing your problem, but you definately > don't want NBUF=4096. There is no reason for it and it will consume a > tremendous amount of virtual memory in 2.1.x. I have noticed I get the "No buffer space" under several conditions, most of which involve "stalls" of networking stuff. An enabled de interface with nothing connected will cause this. A sl interface that got flow controlled will often get wedged in this state. Usually downing and up'ping the interface will clear the condition. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-hackers Thu Dec 26 14:17:44 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA12222 for hackers-outgoing; Thu, 26 Dec 1996 14:17:44 -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 OAA12216 for ; Thu, 26 Dec 1996 14:17:41 -0800 (PST) Received: (from jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) id OAA12528; Thu, 26 Dec 1996 14:17:30 -0800 (PST) To: freebsd-hackers@freebsd.org Path: not-for-mail From: jdp@polstra.com (John Polstra) Newsgroups: polstra.freebsd.hackers Subject: Re: cvsup change Date: 26 Dec 1996 14:17:29 -0800 Organization: Polstra & Co., Seattle, WA Lines: 68 Distribution: local Message-ID: <59uthp$c7d@austin.polstra.com> References: <199612251512.HAA00997@squirrel.tgsoft.com> Summary: Not your fault Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199612251512.HAA00997@squirrel.tgsoft.com>, mark thompson wrote: > I have been paying attention (or so i thought) to the reorganizaion of > the collections, so i added: > > src-release release=cvs host=cvsup.freebsd.org hostbase=/home base=/u prefix=/usr/cvs delete old use-rel-suffix compress > > to the beginning of my cvsup file. It nicely ran through that. It nicely > ran through another collection or two, then it deleted everything in > src/release. It's not your fault. As you know, I made my original announcement about it and then followed up with a string of 3 cascading "corrections". Every one of them was incorrect in some way. For some reason I just couldn't seem to do anything right in connection with this particular change. In my final bogus "correction", I reported that I had run a test and realized that no files were going to be deleted. I did in fact run the test, and that's what I observed. But I must have set up the test wrong, because later when I made the change on the real servers, my files got deleted just like everybody else's. Your case was even worse than most, because you happened to add src-release at the beginning of your supfile instead of at the end or in alphabetical order. That made it come before src-etc, which was the release that caused the files to be deleted. So your files didn't even get restored again until the next time you ran cvsup. You must surely be wondering how it is that I couldn't better predict the behavior of my own program! Believe it or not, deciding which files to add, update, or delete is one of the most complicated parts of the entire software package. In an effort to do what sup would do, it has to do some rather, er, strange processing. In addition, this code has to handle CVS mode and checkout mode in very different ways. Finally, there are many complications that can arise quite easily on a client machine: Missing list file ("checkouts.*") List file out of sync with the actual files Server supports newer protocol version than client Client supports newer protocol version than server Situations having to do with whether the file is in the Attic or not Situations involving the "refuse" files Well, you get the picture. I've redesigned that part of the software twice since the original release. It's been in good shape and very stable for several months now, and as a result I hardly ever look at it any more. Sometimes I get confused about what it does under the various conditions it can be subjected to. It's not a very good excuse, but at least it's an explanation. :-) > I moved the request for src-release to just before > ports-all, and it is now very nicely bringing src/release back. FWIW, now that the transient has passed, it should make no difference what order your collections are in. 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 ... ;-) 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 Thu Dec 26 14:25:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA12721 for hackers-outgoing; Thu, 26 Dec 1996 14:25:55 -0800 (PST) Received: from eac.iafrica.com (196-7-192-110.iafrica.com [196.7.192.110]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA12711 for ; Thu, 26 Dec 1996 14:25:49 -0800 (PST) Received: (from rnordier@localhost) by eac.iafrica.com (8.7.6/8.6.12) id AAA01537; Fri, 27 Dec 1996 00:19:21 +0200 (SAT) From: Robert Nordier Message-Id: <199612262219.AAA01537@eac.iafrica.com> Subject: Re: multi-group file access techniques / directory hardlinks In-Reply-To: from Charles Owens at "Dec 26, 96 04:06:16 pm" To: owensc@enc.edu (Charles Owens) Date: Fri, 27 Dec 1996 00:19:19 +0200 (SAT) Cc: julian@whistle.com, j@uriah.heep.sax.de, freebsd-hackers@freebsd.org, ben@narcissus.ml.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 Charles Owens wrote: > On Thu, 26 Dec 1996, Julian Elischer wrote: > > > Charles Owens wrote: > > > > > 1. The file system does in fact support directory hardlinks. (This is > > > true at least to some extent, since the '.' and '..' entries are, > > > in fact, directory hardlinks.) > > > > see below. > > > > > > > > 2. Certain key tools do _not_ understand directory hardlinks. The ones > > > that I know of are fsck, rm, and rmdir. > > > > > > 3. The official FreeBSD stance (that I seem to be hearing) that > > > directory hardlinks are unsupported is based on: > > > > > > a. the insufficient status of the tool support (previous point) > > > - and/or - > > > b. the fact that directory hardlinks are dangerous in the > > > hands of the uncareful. > > > > > > Am I correct here? Would someone in the know provide clarification? > > > > the KERNEL now disallows the 'link' operation on directories. > > Ok... that's very clear, but a bit terse. :-) What I'm digging for above > is an expression of the rationale for this disabling (_not_ that I > disagree). I certainly can see that directory hard linking should be > disabled as long as support in the basic tools (rm, rmdir, fsck) is > incomplete (otherwise it's a major head-ache for the user). ...But if the > tool support was made complete I'm not so sure that this kernal disabling > is the way to go. Perhaps there could be a options flag in the kernal > config file to force directory linking to be allowed for those who need > it. > > > > > > > > > As I stated in my original posting (on Dec 18), my goal is to come up with > > > an optimum technique for allowing multiple groups controlled access to a > > > file tree. (To my surprise, I had very little response to this posting, > > > which deals with what I think is a rather interesting challenge. If you'd > > > like me to repost, please holler). Essentially I'm trying to achieve a > > > subset of the functionality offered by Access Control Lists as implemented > > > in AIX et al. > > > > I never saw the original posting. > > I've reposted it... > --- > ------------------------------------------------------------------------- > Charles Owens Email: owensc@enc.edu > "I read somewhere to learn is to > Information Technology Services remember... and I've learned that > Eastern Nazarene College we've all forgot..." - King's X > ------------------------------------------------------------------------- > > -- Robert Nordier From owner-freebsd-hackers Thu Dec 26 14:28:11 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA12845 for hackers-outgoing; Thu, 26 Dec 1996 14:28:11 -0800 (PST) Received: from eac.iafrica.com (196-7-192-110.iafrica.com [196.7.192.110]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA12840 for ; Thu, 26 Dec 1996 14:28:05 -0800 (PST) Received: (from rnordier@localhost) by eac.iafrica.com (8.7.6/8.6.12) id AAA01564; Fri, 27 Dec 1996 00:22:57 +0200 (SAT) From: Robert Nordier Message-Id: <199612262222.AAA01564@eac.iafrica.com> Subject: Re: multi-group file access techniques / directory hardlinks In-Reply-To: from Charles Owens at "Dec 26, 96 04:06:16 pm" To: owensc@enc.edu (Charles Owens) Date: Fri, 27 Dec 1996 00:22:56 +0200 (SAT) Cc: julian@whistle.com, j@uriah.heep.sax.de, freebsd-hackers@freebsd.org, ben@narcissus.ml.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 [Sorry about the previous message, which got away before it was ready.] Charles Owens wrote: > On Thu, 26 Dec 1996, Julian Elischer wrote: > > > Charles Owens wrote: > > > > > 1. The file system does in fact support directory hardlinks. (This is > > > true at least to some extent, since the '.' and '..' entries are, > > > in fact, directory hardlinks.) > > > > see below. [ ... ] > > > > > > Am I correct here? Would someone in the know provide clarification? > > > > the KERNEL now disallows the 'link' operation on directories. > > Ok... that's very clear, but a bit terse. :-) What I'm digging for above > is an expression of the rationale for this disabling (_not_ that I > disagree). I certainly can see that directory hard linking should be > disabled as long as support in the basic tools (rm, rmdir, fsck) is > incomplete (otherwise it's a major head-ache for the user). ...But if the > tool support was made complete I'm not so sure that this kernal disabling > is the way to go. Perhaps there could be a options flag in the kernal > config file to force directory linking to be allowed for those who need > it. One fundamental limitation is the deadlock detection scheme in ufs_lookup, which can't handle hard links which point towards the root of the file tree. (`..' is treated as a special case.) Generalized detection of backward links would require different, and more complex, handling of LOCKPARENT cases. -- Robert Nordier From owner-freebsd-hackers Thu Dec 26 14:47:43 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA13975 for hackers-outgoing; Thu, 26 Dec 1996 14:47:43 -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 OAA13965 for ; Thu, 26 Dec 1996 14:47:39 -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 XAA21858; Thu, 26 Dec 1996 23:46:17 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA20357; Thu, 26 Dec 1996 23:46:16 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id WAA00148; Thu, 26 Dec 1996 22:41:06 +0100 (MET) From: J Wunsch Message-Id: <199612262141.WAA00148@uriah.heep.sax.de> Subject: Re: multi-group file access techniques / directory hardlinks To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Thu, 26 Dec 1996 22:41:06 +0100 (MET) Cc: owensc@enc.edu, ben@narcissus.ml.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Charles Owens at "Dec 26, 96 02:40:15 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 Charles Owens wrote: > > Directory hardlinks are impossible in FreeBSD. They have been > > discontinued quite some time ago. > > Uhhh... well, sort of. At least as of 2.1.6 it is still possible to use > ln(1) to create directory hardlinks using an undocumented flag. > 3. The official FreeBSD stance (that I seem to be hearing) that > directory hardlinks are unsupported is based on: > > a. the insufficient status of the tool support (previous point) > - and/or - > b. the fact that directory hardlinks are dangerous in the > hands of the uncareful. c. the fact that directory hardlinks have been discontinued in 2.2. 2.1.6 did indeed still support it, since this was a new feature, hence it didn't go into the 2.1.x tree. They are not only dangerous in the hands of the uncareful, but they are dangerous at all. As i wrote earlier, fsck did _always_ complain about additional hardlinks, so it was always an error to even try it. > As I stated in my original posting (on Dec 18), my goal is to come up with > an optimum technique for allowing multiple groups controlled access to a > file tree. It's probably better to concentrate on a one group per user technique, and put all the other people who are allowed mutually into secondary groups. The ugly old limits for secondary groups have just been killed (but this won't be in 2.2 yet). The experience on freefall proves that this concept is workable, although there's still a tool missing where a user can invite and de-invite others into his group. Maybe i'm missing something here, but it seems to me that those secondary groups should do what you want. David Nugent also suggested to me in private mail that he is thinking of a .db file for the group list as well, so speed issues might also go away soon. > A recent *article in 'Sys Admin' deals with this problem. One of the two > techniques suggested relies on the use of directory hardlinks, which is > why I'm currently interested in the topic. Even in systems that support them, they were only allowed for root users anyway. In order to remove such an extraneous hardlink, you had to bypass any and all validation tests in the kernel (as it is e.g. done if a directory is not empty, but you try rmdir'ing it). Finally, we aren't the first disallowing directory hardlinks. I personally know Data General's DG/UX which used to disallow this misfeature at least since 1990, Linux doesn't allow this, and i think there were even more systems. -- 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 Dec 26 14:48:21 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA14061 for hackers-outgoing; Thu, 26 Dec 1996 14:48: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 OAA14055 for ; Thu, 26 Dec 1996 14:48:17 -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 XAA21868; Thu, 26 Dec 1996 23:46:20 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA20366; Thu, 26 Dec 1996 23:46:18 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id XAA00217; Thu, 26 Dec 1996 23:13:09 +0100 (MET) From: J Wunsch Message-Id: <199612262213.XAA00217@uriah.heep.sax.de> Subject: Re: multi-group file access techniques / directory hardlinks To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Thu, 26 Dec 1996 23:13:09 +0100 (MET) Cc: owensc@enc.edu (Charles Owens), ben@narcissus.ml.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Charles Owens at "Dec 26, 96 04:06:16 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 Charles Owens wrote: > ...But if the > tool support was made complete I'm not so sure that this kernal disabling > is the way to go. You have already been overruled. The decision has been made. > Perhaps there could be a options flag in the kernal > config file to force directory linking to be allowed for those who need > it. You've got the source, you can remove the check again. It's in /sys/kern/vfs_syscalls.c. -- 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 Dec 26 15:01:50 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA15088 for hackers-outgoing; Thu, 26 Dec 1996 15:01:50 -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 PAA15072 for ; Thu, 26 Dec 1996 15:01:43 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id AAA02591 for ; Fri, 27 Dec 1996 00:01:35 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id AAA13159 for Hackers@freebsd.org; Fri, 27 Dec 1996 00:01:22 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.4/keltia-uucp-2.9) id XAA06052; Thu, 26 Dec 1996 23:44:47 +0100 (CET) Message-ID: Date: Thu, 26 Dec 1996 23:44:47 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: Hackers@freebsd.org (Hackers) Subject: Re: `make world` won't References: <199612261641.QAA300214@smtp-gw01.ny.us.ibm.net> X-Mailer: Mutt 0.55.04 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2837 In-Reply-To: <199612261641.QAA300214@smtp-gw01.ny.us.ibm.net>; from Steve Sims on Dec 26, 1996 11:39:59 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Steve Sims: > Doh! Any clues? I'm using Polstra's (most excellent!) cvsup 14.0 with the > plain-vanilla /usr/share/examples/cvsup/standard-supfile. Reinstall /bin/sh by getting the _latest_ and recompile before running "make world" again. Steve fixed it a few days ago. -- 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 Thu Dec 26 15:01:51 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA15100 for hackers-outgoing; Thu, 26 Dec 1996 15:01:51 -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 PAA15073 for ; Thu, 26 Dec 1996 15:01:43 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id AAA02594 for ; Fri, 27 Dec 1996 00:01:35 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id AAA13158 for hackers@freebsd.org; Fri, 27 Dec 1996 00:01:22 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.4/keltia-uucp-2.9) id XAA06041; Thu, 26 Dec 1996 23:40:36 +0100 (CET) Message-ID: Date: Thu, 26 Dec 1996 23:40:35 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: hackers@freebsd.org Subject: Re: multi-group file access techniques References: X-Mailer: Mutt 0.55.04 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2837 In-Reply-To: ; from Charles Owens on Dec 26, 1996 10:41:59 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Charles Owens: > keep fsck happy) ? I can certainly see that they're very dangerous, but > can they be used safely with FreeBSD? Anyone? One of the obvious problem is: what is ".." for an hard-linked directory ? -- 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 Thu Dec 26 15:06:47 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA15377 for hackers-outgoing; Thu, 26 Dec 1996 15:06:47 -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 PAA15371 for ; Thu, 26 Dec 1996 15:06:44 -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 PAA02221 for ; Thu, 26 Dec 1996 15:03:06 -0800 (PST) Message-ID: <32C303EB.41C67EA6@whistle.com> Date: Thu, 26 Dec 1996 15:02:03 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: ACLs for BSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In 1992 someone posted to the comp.unix.bsd list (I believe) a set of patches to add ACLs to arbitrary files under 386BSD. Bill Jolitz and others considered it to be of interest, however it seems to have gone from my archives. does anyone still have that tucked away? it might be worth looking at again soem time. julian From owner-freebsd-hackers Thu Dec 26 15:34:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA17264 for hackers-outgoing; Thu, 26 Dec 1996 15:34:58 -0800 (PST) Received: from trapdoor.dstc.edu.au (root@trapdoor.dstc.edu.au [130.102.176.12]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA17249 for ; Thu, 26 Dec 1996 15:34:54 -0800 (PST) Received: from foxtail.dstc.edu.au (foxtail.dstc.edu.au [130.102.176.14]) by trapdoor.dstc.edu.au (8.6.9/8.6.12) with ESMTP id JAA27951; Fri, 27 Dec 1996 09:34:36 +1000 Received: (from leonard@localhost) by foxtail.dstc.edu.au (8.6.10/8.6.10) id JAA07441; Fri, 27 Dec 1996 09:34:35 +1000 From: David Leonard Message-Id: <199612262334.JAA07441@foxtail.dstc.edu.au> Subject: Re: multi-group file access techniques (repost) To: owensc@enc.edu Date: Fri, 27 Dec 1996 09:34:35 +1000 (EST) Cc: hackers@freebsd.org Reply-To: leonard@dstc.edu.au 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 In dstc.mail.freebsd.hackers you write: > .../man_readable_c is a "control directory," a technique that seems [...] > making 'www' the owner of all "choke point" directories: okay, so this technique is emulating ACLs by concatenating the unix permissions on ancestor directories. (correct me if ive got this wrong) > In his article, Doug Morris also speaks of a technique of using hard links > of directories to achieve a similar effect. This technique could be used > in tandem with the above to add more flexibility, but we all know the > GREAT EVIL that hard linked directories are. :-) this could also be done with portalfs or nullfs? hard links can introduce inter-device cycles in the filesystem tree which many program (libraries) rely on the non-existence of. imho introducing ACLs is admitting to complexity :) The really simple solution is having billions of groups and encoding the ACL in them... a perl script should do it :) :) :) -- David Leonard Developer, DSTC The University of Queensland david.leonard@dstc.edu.au http://www.dstc.edu.au/~leonard/ "What is contemplation but laxative for the mind?" - T.A.Casady (?) From owner-freebsd-hackers Thu Dec 26 16:27:37 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA20912 for hackers-outgoing; Thu, 26 Dec 1996 16:27:37 -0800 (PST) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [207.95.42.241]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA20899 for ; Thu, 26 Dec 1996 16:27:33 -0800 (PST) Received: from dingo.its.enc.edu (dingo.its.enc.edu [207.95.222.250]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id TAA27214; Thu, 26 Dec 1996 19:23:59 -0500 (EST) Date: Thu, 26 Dec 1996 19:30:43 -0500 (EST) From: Charles Owens X-Sender: owensc@dingo.its.enc.edu Reply-To: Charles Owens To: Joerg Wunsch cc: FreeBSD hackers , ben@narcissus.ml.org Subject: Re: multi-group file access techniques / directory hardlinks In-Reply-To: <199612262141.WAA00148@uriah.heep.sax.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 Thu, 26 Dec 1996, J Wunsch wrote: > As Charles Owens wrote: > > > > Directory hardlinks are impossible in FreeBSD. They have been > > > discontinued quite some time ago. > > > > Uhhh... well, sort of. At least as of 2.1.6 it is still possible to use > > ln(1) to create directory hardlinks using an undocumented flag. > > > 3. The official FreeBSD stance (that I seem to be hearing) that > > directory hardlinks are unsupported is based on: > > > > a. the insufficient status of the tool support (previous point) > > - and/or - > > b. the fact that directory hardlinks are dangerous in the > > hands of the uncareful. > > c. the fact that directory hardlinks have been discontinued in 2.2. > > 2.1.6 did indeed still support it, since this was a new feature, hence > it didn't go into the 2.1.x tree. > > They are not only dangerous in the hands of the uncareful, but they > are dangerous at all. As i wrote earlier, fsck did _always_ complain > about additional hardlinks, so it was always an error to even try it. > > > As I stated in my original posting (on Dec 18), my goal is to come up with > > an optimum technique for allowing multiple groups controlled access to a > > file tree. > > It's probably better to concentrate on a one group per user technique, > and put all the other people who are allowed mutually into secondary > groups. The ugly old limits for secondary groups have just been > killed (but this won't be in 2.2 yet). The experience on freefall > proves that this concept is workable, although there's still a tool > missing where a user can invite and de-invite others into his group. I assume you mean the 16 groups per user limit, eh? Do you mean that in the new, post 2.2 code there's really _no_ limit to the number of secondary groups that a user can belong to? (for example, suppose every one of my thousands of users belongs to their own personal group. If I make the user 'metauser' a member of each one of these groups then there'd be no problem? ...except perhaps perfromance issues as you mention below?) Will this show up in 2.2.1 and/or 3.0? (Is it in -current now?) I need to be rolling out a solution in the next few months, but with this user membership limit going away in the near future it looks like I may want to take a more evolutionary approach. > Maybe i'm missing something here, but it seems to me that those > secondary groups should do what you want. David Nugent also suggested > to me in private mail that he is thinking of a .db file for the group > list as well, so speed issues might also go away soon. > > > A recent *article in 'Sys Admin' deals with this problem. One of the two > > techniques suggested relies on the use of directory hardlinks, which is > > why I'm currently interested in the topic. > > Even in systems that support them, they were only allowed for root > users anyway. In order to remove such an extraneous hardlink, you had > to bypass any and all validation tests in the kernel (as it is > e.g. done if a directory is not empty, but you try rmdir'ing it). > > Finally, we aren't the first disallowing directory hardlinks. I > personally know Data General's DG/UX which used to disallow this > misfeature at least since 1990, Linux doesn't allow this, and i think > there were even more systems. Sounds good to me. I never really liked the idea of hard linked directories anyway. :-) Thanks! --- ------------------------------------------------------------------------- Charles Owens Email: owensc@enc.edu "I read somewhere to learn is to Information Technology Services remember... and I've learned that Eastern Nazarene College we've all forgot..." - King's X ------------------------------------------------------------------------- From owner-freebsd-hackers Thu Dec 26 16:38:48 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA21278 for hackers-outgoing; Thu, 26 Dec 1996 16:38:48 -0800 (PST) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [207.95.42.241]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA21271 for ; Thu, 26 Dec 1996 16:38:45 -0800 (PST) Received: from dingo.its.enc.edu (dingo.its.enc.edu [207.95.222.250]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id TAA27251; Thu, 26 Dec 1996 19:35:11 -0500 (EST) Date: Thu, 26 Dec 1996 19:41:55 -0500 (EST) From: Charles Owens X-Sender: owensc@dingo.its.enc.edu To: David Leonard cc: hackers@freebsd.org Subject: Re: multi-group file access techniques (repost) In-Reply-To: <199612262334.JAA07441@foxtail.dstc.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 Fri, 27 Dec 1996, David Leonard wrote: > In dstc.mail.freebsd.hackers you write: > > > .../man_readable_c is a "control directory," a technique that seems > [...] > > making 'www' the owner of all "choke point" directories: > > okay, so this technique is emulating ACLs by concatenating the unix > permissions on ancestor directories. (correct me if ive got this wrong) Yep, that's the general idea. > > In his article, Doug Morris also speaks of a technique of using hard links > > of directories to achieve a similar effect. This technique could be used > > in tandem with the above to add more flexibility, but we all know the > > GREAT EVIL that hard linked directories are. :-) > > this could also be done with portalfs or nullfs? hard links can > introduce inter-device cycles in the filesystem tree which many > program (libraries) rely on the non-existence of. > > imho introducing ACLs is admitting to complexity :) I agree with the sentiment! > The really simple solution is having billions of groups and encoding the > ACL in them... a perl script should do it :) :) :) What exactly do you mean by 'encoding the ACL in them'. Could you flesh this out a bit... perhaps including an example? Thanks! --- ------------------------------------------------------------------------- Charles Owens Email: owensc@enc.edu "I read somewhere to learn is to Information Technology Services remember... and I've learned that Eastern Nazarene College we've all forgot..." - King's X ------------------------------------------------------------------------- From owner-freebsd-hackers Thu Dec 26 17:08:10 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA22143 for hackers-outgoing; Thu, 26 Dec 1996 17:08:10 -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 RAA22138 for ; Thu, 26 Dec 1996 17:08:06 -0800 (PST) Received: (from uucp@localhost) by nic.follonett.no (8.8.3/8.8.3) with UUCP id CAA02920; Fri, 27 Dec 1996 02:06:45 +0100 (MET) Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id BAA28187; Fri, 27 Dec 1996 01:59:04 +0100 (MET) Message-Id: <3.0.32.19961227015643.009da790@dimaga.com> X-Sender: eivind@dimaga.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Fri, 27 Dec 1996 01:56:44 +0100 To: Peter Hawkins From: Eivind Eklund Subject: Re: Help with sb 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 02:54 AM 12/27/96 +1100, you wrote: > >Thankyou for those who helped. It was indeed the interrupt clash. Moving my >ed1 to irq 9 via 2 freed up irq 5 for sdn0 and it works fine. > >For the record, it seems that dos does not use the printer's irq properly >hence it is possible to steal irq 7 (according to those who helped me). > >In FreeBSD it is not valid to do this. A very interesting question is why 'we' don't check for this and disallow it. The different drivers must know which IRQs they're using, and should be able to allocate these from a pool. If we added a priority system it might even be possible to devices that CAN poll (like the parallell port) to poll if another card/driver 'stole' it's interrupt. I'm unfortuneatly not in a position where I can implement this right now (my only FreeBSD box is running as a server for 12 people who like their files :), but perhaps some of the people thinking about addign PnP could do something? (A system used by only some drivers is still better than no system...) Eivind Eklund / perhaps@yes.no / http://maybe.yes.no/perhaps/ From owner-freebsd-hackers Thu Dec 26 19:01:43 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA26491 for hackers-outgoing; Thu, 26 Dec 1996 19:01:43 -0800 (PST) Received: from sdev.usn.blaze.net.au (sdev.usn.blaze.net.au [203.17.53.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA26486 for ; Thu, 26 Dec 1996 19:01:37 -0800 (PST) Received: (from davidn@localhost) by sdev.usn.blaze.net.au (8.8.4/8.6.9) id OAA01377; Fri, 27 Dec 1996 14:00:01 +1100 (EST) Message-ID: Date: Fri, 27 Dec 1996 14:00:01 +1100 From: davidn@sdev.usn.blaze.net.au (David Nugent) To: owensc@enc.edu (Charles Owens) Cc: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), freebsd-hackers@freebsd.org (FreeBSD hackers), ben@narcissus.ml.org Subject: Re: multi-group file access techniques / directory hardlinks References: <199612262141.WAA00148@uriah.heep.sax.de> X-Mailer: Mutt 0.54 Mime-Version: 1.0 In-Reply-To: ; from Charles Owens on Dec 26, 1996 19:30:43 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Charles Owens writes: > > It's probably better to concentrate on a one group per user technique, > > and put all the other people who are allowed mutually into secondary > > groups. The ugly old limits for secondary groups have just been > > killed (but this won't be in 2.2 yet). The experience on freefall > > proves that this concept is workable, although there's still a tool > > missing where a user can invite and de-invite others into his group. > > > I assume you mean the 16 groups per user limit, eh? No. The 200 users per group limit. > Do you mean that in the new, post 2.2 code there's really _no_ > limit to the number of secondary groups that a user can belong to? No. There is now (effectively) no limit to the number of users who can belong to any secondary group, although the number will actually be something >=65536 users since the line length is prevented from growing beyond 256K for security reasons, which is fair enough. So far, the 16 groups per user is enforced by initgroups() et al remains, but I think it a candidate for being looked at as well. It seems that this is mostly driven by the NGROUPS #define in sys/param.h NGROUPS_MAX and KERN_NGROUPS (which is 18, not 16, for some reason which I haven't looked into). Unlike the 200 limit, though, a change here will affects the kernel, not just userland code. There may not be a way of making it "unlimited" without some significant redesign which may break POSIX or other design specifications (I don't know), but afaik there's no reason that this small limit could be raised to, say, 64. But beyond a solution that involves lifting it to a ridiculously high number, whatever limit is set is going to be arbitrary. 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@freefall.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-hackers Thu Dec 26 22:11:44 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA04478 for hackers-outgoing; Thu, 26 Dec 1996 22:11:44 -0800 (PST) Received: from research.gate.nec.co.jp (research.gate.nec.co.jp [202.32.8.49]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA04473 for ; Thu, 26 Dec 1996 22:11:40 -0800 (PST) Received: from sbl-gw.sbl.cl.nec.co.jp by research.gate.nec.co.jp (8.8.3p1+2.6Wbeta9/950912) with ESMTP id PAA16608; Fri, 27 Dec 1996 15:11:37 +0900 (JST) Received: from sirius.sbl.cl.nec.co.jp by sbl-gw.sbl.cl.nec.co.jp (8.7.6+2.6Wbeta7/3.3W6) with ESMTP id PAA28229; Fri, 27 Dec 1996 15:11:36 +0900 (JST) Received: by sirius.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with UUCP id PAA06595; Fri, 27 Dec 1996 15:11:33 +0900 (JST) Date: Fri, 27 Dec 1996 15:11:33 +0900 (JST) From: Naoki Hamada Message-Id: <199612270611.PAA06595@sirius.sbl.cl.nec.co.jp> To: freebsd-hackers@FreeBSD.ORG Subject: [2.2-BETA] NFS hangup! Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, guys! This morning I encountered a sudden hangup and found out what is the case. On a NFS imported filesystem, when I execute the following sequence, the PC totally hangs up after the `mv' command. % mkdir -p tmp/tmp % mv tmp/tmp . On a UFS filesystem, a normal error occurs: mv: rename tmp/tmp to ./tmp: Directory not empty The NFS server is a SS20 which runs SunOS 4.1.4 and the PC runs FreeBSD 2.2 BETA. - nao From owner-freebsd-hackers Thu Dec 26 22:27:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA06326 for hackers-outgoing; Thu, 26 Dec 1996 22:27:20 -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 WAA06321 for ; Thu, 26 Dec 1996 22:27:17 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vdVkj-0001hq-00; Thu, 26 Dec 1996 23:26:45 -0700 To: davidn@sdev.usn.blaze.net.au (David Nugent) Subject: Re: multi-group file access techniques / directory hardlinks Cc: owensc@enc.edu (Charles Owens), joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), freebsd-hackers@freebsd.org (FreeBSD hackers), ben@narcissus.ml.org In-reply-to: Your message of "Fri, 27 Dec 1996 14:00:01 +1100." References: <199612262141.WAA00148@uriah.heep.sax.de> Date: Thu, 26 Dec 1996 23:26:45 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message David Nugent writes: : Unlike the 200 limit, though, a change here will affects the : kernel, not just userland code. There may not be a way of : making it "unlimited" without some significant redesign which : may break POSIX or other design specifications (I don't know), : but afaik there's no reason that this small limit could be raised : to, say, 64. But beyond a solution that involves lifting it to a : ridiculously high number, whatever limit is set is going to be : arbitrary. NFS v2 has hard limits in the number of groups a user may belong to, if memory serves me correctly. Warner From owner-freebsd-hackers Fri Dec 27 00:52:57 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA10850 for hackers-outgoing; Fri, 27 Dec 1996 00:52:57 -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 AAA10840 for ; Fri, 27 Dec 1996 00:52:51 -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 JAA29456 for ; Fri, 27 Dec 1996 09:52:48 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA28483 for freebsd-hackers@freebsd.org; Fri, 27 Dec 1996 09:52:46 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id JAA03329 for freebsd-hackers@freebsd.org; Fri, 27 Dec 1996 09:48:35 +0100 (MET) From: J Wunsch Message-Id: <199612270848.JAA03329@uriah.heep.sax.de> Subject: Re: multi-group file access techniques / directory hardlinks To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Fri, 27 Dec 1996 09:48:34 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from David Nugent at "Dec 27, 96 02:00:01 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 David Nugent wrote: > So far, the 16 groups per user is enforced by initgroups() et > al remains, but I think it a candidate for being looked at as > well. It seems that this is mostly driven by the NGROUPS > #define in sys/param.h NGROUPS_MAX and KERN_NGROUPS (which is > 18, not 16, for some reason which I haven't looked into). > > Unlike the 200 limit, though, a change here will affects the > kernel, not just userland code. If they are done correctly, this shouldn't be the problem. We allow for as much as you want IP alias addresses, so why not allowing for as much as you want secondary groups? Of course, you gotta be careful with obsolete or braindead protocols that hard-code some maximum. NIS and NFS seem to fit into this category... Still no justification to also limit the !NIS && !NFS 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 Fri Dec 27 01:21:49 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA11663 for hackers-outgoing; Fri, 27 Dec 1996 01:21: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 BAA11640 for ; Fri, 27 Dec 1996 01:21:44 -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 KAA02826; Fri, 27 Dec 1996 10:21:27 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA28733; Fri, 27 Dec 1996 10:21:25 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id JAA03454; Fri, 27 Dec 1996 09:56:03 +0100 (MET) From: J Wunsch Message-Id: <199612270856.JAA03454@uriah.heep.sax.de> Subject: Re: [2.2-BETA] NFS hangup! To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Fri, 27 Dec 1996 09:56:03 +0100 (MET) Cc: nao@sbl.cl.nec.co.jp (Naoki Hamada) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612270611.PAA06595@sirius.sbl.cl.nec.co.jp> from Naoki Hamada at "Dec 27, 96 03:11:33 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 Naoki Hamada wrote: > This morning I encountered a sudden hangup and found out what is the > case. On a NFS imported filesystem, when I execute the following > sequence, the PC totally hangs up after the `mv' command. > > % mkdir -p tmp/tmp > % mv tmp/tmp . I get the dreaded panic: nfs: sillyrename dir when trying this. (Both, client and server are FreeBSD.) Doesn't this ring a bell for somebody? -- 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 Dec 27 03:46:40 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA15929 for hackers-outgoing; Fri, 27 Dec 1996 03:46:40 -0800 (PST) Received: from wiley.csusb.edu (wiley.csusb.edu [139.182.2.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id DAA15924 for ; Fri, 27 Dec 1996 03:46:38 -0800 (PST) Received: (from wwong@localhost) by wiley.csusb.edu (8.8.4/8.6.11) id DAA15780; Fri, 27 Dec 1996 03:40:28 -0800 (PST) From: William Wong Message-Id: <199612271140.DAA15780@wiley.csusb.edu> Subject: Re: [2.2-BETA] NFS hangup! To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 27 Dec 1996 03:40:28 -0800 (PST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199612270856.JAA03454@uriah.heep.sax.de> from "J Wunsch" at Dec 27, 96 09:56:03 am X-Mailer: ELM [version 2.4 PL22] 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 Naoki Hamada wrote: > > > This morning I encountered a sudden hangup and found out what is the > > case. On a NFS imported filesystem, when I execute the following > > sequence, the PC totally hangs up after the `mv' command. > > > > % mkdir -p tmp/tmp > > % mv tmp/tmp . > > I get the dreaded > > panic: nfs: sillyrename dir > > when trying this. (Both, client and server are FreeBSD.) > > Doesn't this ring a bell for somebody? > > -- > 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. ;-) > > Yep, I remember hangs like that way back when I was using FreeBSD 1.1.5.1 and mounting filesystems off of some IBM RS/6000 machines running AIX 3.x. I guess these problems are pretty lengendary. :) -- William T. Wong Assistant Network Analyst Cal State University, San Bernardino Phone: (909) 880-7281 email: wwong@wiley.csusb.edu From owner-freebsd-hackers Fri Dec 27 05:12:05 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA18354 for hackers-outgoing; Fri, 27 Dec 1996 05:12:05 -0800 (PST) Received: from news.IAEhv.nl (root@news.IAEhv.nl [194.151.64.4]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id FAA18349 for ; Fri, 27 Dec 1996 05:12:02 -0800 (PST) Received: from truk.brandinnovators.com (uucp@localhost) by news.IAEhv.nl (8.6.13/1.63) with IAEhv.nl; pid 28756 on Fri, 27 Dec 1996 13:44:21 +0100; id NAA28756 efrom: hans@truk.brandinnovators.com; eto: freebsd-hackers@freebsd.org Received: by truk.brandinnovators.com (8.7.5/BI96070101) for id KAA05227; Fri, 27 Dec 1996 10:48:59 GMT Message-Id: <199612271048.KAA05227@truk.brandinnovators.com> From: hans@brandinnovators.com (Hans Zuidam) Subject: bootloader & memory test... To: freebsd-hackers@freebsd.org Date: Fri, 27 Dec 1996 10:48:59 +0000 () 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, After about a year of sig-11 plague I decided to find exactly what was wrong with the memory of my system and found a program called MemTest-86 by Chris Brady. It is the only one that's indeed reporting errors, none of the DOS based ones found anything! To narrow the search space I would like to make some modifications, but the sources use a modified version of the Linux boot loader. To make things worse apparently two different assembler syntaxes (AT&T and Intel) are used and I am not well versed (to say the least) in either. The memory test sets the CPU for flat 32 bit addressing and loads itself to address 0x100. It uses the area from 0x0 to 0xFF as it's stack. Could someone give me a hand (or pointers) to achieve the same using the FreeBSD boot loader? Thanks in advance, Hans -- H. Zuidam E-Mail: hans@brandinnovators.com Brand Innovators B.V. P-Mail: P.O. Box 1377 de Pinckart 54 5602 BJ Eindhoven, The Netherlands 5674 CC Nuenen Tel. +31 40 2631134, Fax. +31 40 2831138 From owner-freebsd-hackers Fri Dec 27 05:59:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA19526 for hackers-outgoing; Fri, 27 Dec 1996 05:59:04 -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 FAA19519 for ; Fri, 27 Dec 1996 05:59:01 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id AAA27921; Sat, 28 Dec 1996 00:28:51 +1030 (CST) From: Michael Smith Message-Id: <199612271358.AAA27921@genesis.atrad.adelaide.edu.au> Subject: Re: bootloader & memory test... In-Reply-To: <199612271048.KAA05227@truk.brandinnovators.com> from Hans Zuidam at "Dec 27, 96 10:48:59 am" To: hans@brandinnovators.com (Hans Zuidam) Date: Sat, 28 Dec 1996 00:28:50 +1030 (CST) Cc: 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 Hans Zuidam stands accused of saying: > After about a year of sig-11 plague I decided to find exactly what was > wrong with the memory of my system and found a program called MemTest-86 > by Chris Brady. It is the only one that's indeed reporting errors, none > of the DOS based ones found anything! It looks interesting, indeed. It could do with some slightly more complex tests, but it certainly looks like a good start. > The memory test sets the CPU for flat 32 bit addressing and loads itself > to address 0x100. It uses the area from 0x0 to 0xFF as it's stack. Could > someone give me a hand (or pointers) to achieve the same using the FreeBSD > boot loader? Thanks in advance, The FreeBSD bootloader is _very_ different; you would be better off sticking with the code that's there. If nobody beats me to it, I'll have a look at cutting you a new Makefile tomorrow. > H. Zuidam E-Mail: hans@brandinnovators.com -- ]] 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 Fri Dec 27 07:23:39 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA22170 for hackers-outgoing; Fri, 27 Dec 1996 07:23:39 -0800 (PST) Received: from bbs.mpcs.com (bbs.mpcs.com [204.215.226.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA22165 for ; Fri, 27 Dec 1996 07:23:31 -0800 (PST) Received: (from hgoldste@localhost) by bbs.mpcs.com (8.8.4/8.8.4/MPCS) id KAA20570; Fri, 27 Dec 1996 10:21:34 -0500 Date: Fri, 27 Dec 1996 10:21:34 -0500 From: Howard Goldstein Message-Id: <199612271521.KAA20570@bbs.mpcs.com> To: luigi@labinfo.iet.unipi.it, freebsd-hackers@freebsd.org Subject: Re: ipretard.c selective tcp/ip queues and throughput limiters In-Reply-To: <199612230604.HAA16852@labinfo.iet.unipi.it> Reply-To: hgoldste@bbs.mpcs.com Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199612230604.HAA16852@labinfo.iet.unipi.it>, you wrote: : For a less flexible (at the moment) but much more efficient approach to : this kind of problems, have a look also at my dummynet stuff (available : from http://www.iet.unipi.it/~luigi). Can anyone else hit this site? I can't -- Howard Goldstein From owner-freebsd-hackers Fri Dec 27 07:59:59 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA25120 for hackers-outgoing; Fri, 27 Dec 1996 07:59:59 -0800 (PST) Received: from main.intcomm.net (main.intcomm.Net [204.95.133.250]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA25115 for ; Fri, 27 Dec 1996 07:59:57 -0800 (PST) Received: from main.intcomm.net (main.intcomm.Net [204.95.133.250]) by main.intcomm.net (8.7.5/8.6.9) with SMTP id JAA07901 for ; Fri, 27 Dec 1996 09:59:56 -0600 (CST) Date: Fri, 27 Dec 1996 09:59:56 -0600 (CST) From: Jim Bentley To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe From owner-freebsd-hackers Fri Dec 27 08:36:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA26671 for hackers-outgoing; Fri, 27 Dec 1996 08:36:06 -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 IAA26657 for ; Fri, 27 Dec 1996 08:35:52 -0800 (PST) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id LAA21311; Fri, 27 Dec 1996 11:33:21 -0500 From: Bill Paul Message-Id: <199612271633.LAA21311@skynet.ctr.columbia.edu> Subject: Re: [2.2-BETA] NFS hangup! To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 27 Dec 1996 11:33:20 -0500 (EST) Cc: hackers@freebsd.org In-Reply-To: <199612270856.JAA03454@uriah.heep.sax.de> from "J Wunsch" at Dec 27, 96 09:56:03 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, J Wunsch had to walk into mine and say: > As Naoki Hamada wrote: > > > This morning I encountered a sudden hangup and found out what is the > > case. On a NFS imported filesystem, when I execute the following > > sequence, the PC totally hangs up after the `mv' command. > > > > % mkdir -p tmp/tmp > > % mv tmp/tmp . > > I get the dreaded > > panic: nfs: sillyrename dir > > when trying this. (Both, client and server are FreeBSD.) > > Doesn't this ring a bell for somebody? Happens for me too (SunOS 4.1.3 server, FreeBSD client). The offending code is in nfs_vnops.c: static int nfs_sillyrename(dvp, vp, cnp) struct vnode *dvp, *vp; struct componentname *cnp; { register struct sillyrename *sp; struct nfsnode *np; int error; short pid; cache_purge(dvp); np = VTONFS(vp); #ifndef DIAGNOSTIC if (vp->v_type == VDIR) panic("nfs: sillyrename dir"); #endif It's basically disallowing sillyrenames for directories. If you compile with options DIAGNOSTIC it looks like the problem is hidden; this doesn't look like the right thing to do though. With SunOS, I get: mv: tmp/tmp: rename: Directory not empty Looking at our code, it seems that the client will attempt a sillyrename in nfs_rename() if the 'destination' vnode exists is in use. The 2.1.0 code didn't do this (which I guess is a bug if you're renaming foo to bar, and foo and bar are both files, and bar exists and is still being referenced by someone). (Of course none of this crap works if you have two client machines, and a process on one host unlinks bar while a process on the other host has a reference to bar, but that's NFS for you.) The code in nfs_rename() says: /* * If the tvp exists and is in use, sillyrename it before doing the * rename of the new file over it. */ if (tvp && tvp->v_usecount > 1 && !VTONFS(tvp)->n_sillyrename && !nfs_sillyrename(tdvp, tvp, tcnp)) { vrele(tvp); tvp = NULL; } Should the test in nfs_rename() check if the 'destination' vnode is a directory and skip the sillyrename if it is? I.e.: /* * If the tvp exists and is in use, sillyrename it before doing the * rename of the new file over it. * XXX Can't sillyrename a directory. The server will catch the * error for us anyway. */ if (tvp && tvp->v_usecount > 1 && !VTONFS(tvp)->n_sillyrename && tvp->v_type != VDIR && !nfs_sillyrename(tdvp, tvp, tcnp)) { vrele(tvp); tvp = NULL; } -Bill -- ============================================================================= -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 Fri Dec 27 08:51:16 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA27404 for hackers-outgoing; Fri, 27 Dec 1996 08:51:16 -0800 (PST) Received: from geo.geoaccess.net (root@[204.244.119.126]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA27398 for ; Fri, 27 Dec 1996 08:51:14 -0800 (PST) Received: from localhost (root@localhost) by geo.geoaccess.net (8.7.5/8.7.3) with SMTP id IAA01157 for ; Fri, 27 Dec 1996 08:51:08 -0800 Date: Fri, 27 Dec 1996 08:51:08 -0800 (PST) From: root To: hackers@FreeBSD.org Subject: How to run C programs on FreeBSD Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Recently I purchased FreeBSD Release 2.1.5 and installed on my machine for developer package. I tried to run a small program hello.c to print on screen. After editing hello.c and I compile it as as: gcc -o hello hello.c hello It supposed to print: Hello World! However, the system responded: "Command not found" I checked file mode hello and it was rwxr_xr_x. It should run. Also I made a perl script to rpint "Hello world!". I set the script mode as 777 after editing. When I tried to run it, it gave me the same error message as before for c program hello. What do I have to do to run it? Would you please help me out? It would be greatly appreciated. Thank you so much. Yung, yung@geoaccess.net From owner-freebsd-hackers Fri Dec 27 09:14:39 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA28357 for hackers-outgoing; Fri, 27 Dec 1996 09:14:39 -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 JAA28348 for ; Fri, 27 Dec 1996 09:14:24 -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 LAA09643; Fri, 27 Dec 1996 11:57:17 -0800 Message-Id: <199612271957.LAA09643@interlink.ReyMoreno.net.co> To: "FreeBSD matters of Mark Huizer (xaa)" , FreeBSD Acct , FreeBSD hackers Date: Fri, 27 Dec 96 11:59:46 -0500 From: Mauricio Calderòn X-Mailer: e-mailMCI v2.3 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk -- [ From: Mauricio Calderòn * EMC.Ver #2.3 ] -- unsubscribe From owner-freebsd-hackers Fri Dec 27 09:31:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA29306 for hackers-outgoing; Fri, 27 Dec 1996 09:31:55 -0800 (PST) Received: from trinity.radio-do.de (fn@trinity.Radio-do.de [193.101.164.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA29276 for ; Fri, 27 Dec 1996 09:31:39 -0800 (PST) Received: by trinity.radio-do.de (8.7.6/CLIENT-1.2.7-h) via EUnet id SAA00727; Fri, 27 Dec 1996 18:31:29 +0100 (MET) Cc: root To: hackers@freebsd.org Subject: Re: How to run C programs on FreeBSD References: From: Frank Nobis Date: 27 Dec 1996 18:31:28 +0100 In-Reply-To: root's message of Fri, 27 Dec 1996 08:51:08 -0800 (PST) Message-ID: Lines: 24 X-Mailer: Red Gnus v0.74/XEmacs 19.14 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> "root" == root writes: root> Recently I purchased FreeBSD Release 2.1.5 and installed on root> my machine for developer package. I tried to run a small root> program hello.c to print on screen. root> After editing hello.c and I compile it as as: gcc -o hello root> hello.c hello root> It supposed to print: Hello World! root> However, the system responded: "Command not found" root> Yung, yung@geoaccess.net As we can see you are the user root. Root has per default the current directory '.' not in his path. Try './hello' Gruß Frank -- Frank Nobis Email: fn@Radio-do.de PGP AVAILABLE Landgrafenstr. 130 dg3dcn http://www.radio-do.de/~fn/ 44139 Dortmund Powered by FreeBSD Fax: +49 231 7213816 From owner-freebsd-hackers Fri Dec 27 09:51:59 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA00470 for hackers-outgoing; Fri, 27 Dec 1996 09:51: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 JAA00465 for ; Fri, 27 Dec 1996 09:51: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 SAA29162 for ; Fri, 27 Dec 1996 18:51:46 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id SAA04826 for freebsd-hackers@freebsd.org; Fri, 27 Dec 1996 18:51:45 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id SAA14090 for freebsd-hackers@freebsd.org; Fri, 27 Dec 1996 18:27:11 +0100 (MET) From: J Wunsch Message-Id: <199612271727.SAA14090@uriah.heep.sax.de> Subject: Re: How to run C programs on FreeBSD To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Fri, 27 Dec 1996 18:27:11 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from root at "Dec 27, 96 08:51:08 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 > However, the system responded: > "Command not found" (Moved to -questions) -- 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 Dec 27 11:34:43 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA04654 for hackers-outgoing; Fri, 27 Dec 1996 11:34:43 -0800 (PST) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA04648 for ; Fri, 27 Dec 1996 11:34:40 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.7.5/8.6.12) with SMTP id LAA10973; Fri, 27 Dec 1996 11:25:31 -0800 (PST) Message-Id: <199612271925.LAA10973@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: Host localhost [127.0.0.1] didn't use HELO protocol To: root Cc: hackers@freebsd.org Subject: Re: How to run C programs on FreeBSD Reply-To: Jason Thorpe From: Jason Thorpe Date: Fri, 27 Dec 1996 11:25:25 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 27 Dec 1996 08:51:08 -0800 (PST) root wrote: > However, the system responded: > "Command not found" The program isn't in your search path... either add "." to the end of your path, or invoke your program by full or relative pathname (preferred) like "./hello". Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-hackers Fri Dec 27 12:43:11 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA07174 for hackers-outgoing; Fri, 27 Dec 1996 12:43: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 MAA07168 for ; Fri, 27 Dec 1996 12:43: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 KAA00527; Fri, 27 Dec 1996 10:33:04 -0800 (PST) Message-ID: <32C4161E.41C67EA6@whistle.com> Date: Fri, 27 Dec 1996 10:31:58 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Michael Smith CC: Hans Zuidam , freebsd-hackers@freebsd.org Subject: Re: bootloader & memory test... References: <199612271358.AAA27921@genesis.atrad.adelaide.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith wrote: > > > > The memory test sets the CPU for flat 32 bit addressing and loads itself > > to address 0x100. It uses the area from 0x0 to 0xFF as it's stack. Could > > someone give me a hand (or pointers) to achieve the same using the FreeBSD > > boot loader? Thanks in advance, > > The FreeBSD bootloader is _very_ different; you would be better off > sticking with the code that's there. If nobody beats me to it, I'll > have a look at cutting you a new Makefile tomorrow. > The FreeBSD botblocks set themselves to be in a flat 32bit address space as well. They do use up more of the bottom 640K, (but you can control where they put themselves in ram at compile time) so it should be possible to add the function into one of the .s files From owner-freebsd-hackers Fri Dec 27 13:06:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA08477 for hackers-outgoing; Fri, 27 Dec 1996 13:06:41 -0800 (PST) Received: from edison.ebicom.net (ttsai@Edison.EbiCom.net [205.218.114.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA08470 for ; Fri, 27 Dec 1996 13:06:38 -0800 (PST) Received: (from ttsai@localhost) by edison.ebicom.net From: Tim Tsai Message-Id: <199612272106.PAA02820@edison.ebicom.net> Subject: catching SIGILL To: freebsd-hackers@freebsd.org Date: Fri, 27 Dec 1996 15:06:36 -0600 (CST) Receipt-To: ttsai@pobox.com Reply-To: ttsai@pobox.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 It appears that it's not possible to catch SIGILL on 2.1.6. Is that correct? I peeked at the source and the action is set to SIG_DFL each time. Just curious. I was running "crashme" and it always core dumps on SIGILL, which means that I usually can't run it for more than a dozen iterations or so. Thanks, Tim From owner-freebsd-hackers Fri Dec 27 14:31:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA11481 for hackers-outgoing; Fri, 27 Dec 1996 14:31:24 -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 OAA11475 for ; Fri, 27 Dec 1996 14:31:22 -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 OAA09469 for ; Fri, 27 Dec 1996 14:31:20 -0800 (PST) Date: Fri, 27 Dec 1996 14:31:20 -0800 (PST) From: Jaye Mathisen To: hackers@freebsd.org Subject: 2.2-beta install notes. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 2.2-BETA installed just yippee skippee on a new P6-200 with 128MB RAM, and 2940UW and Quantum 4GB disks. >From power-on to finish with squid running, was 36 minutes via FTP install. I love it. From owner-freebsd-hackers Fri Dec 27 14:36:08 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA11599 for hackers-outgoing; Fri, 27 Dec 1996 14:36:08 -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 OAA11586 for ; Fri, 27 Dec 1996 14:36:01 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id JAA30911; Sat, 28 Dec 1996 09:32:02 +1100 Date: Sat, 28 Dec 1996 09:32:02 +1100 From: Bruce Evans Message-Id: <199612272232.JAA30911@godzilla.zeta.org.au> To: freebsd-hackers@freebsd.org, ttsai@pobox.com Subject: Re: catching SIGILL Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > It appears that it's not possible to catch SIGILL on 2.1.6. Is that >correct? I peeked at the source and the action is set to SIG_DFL each >time. SIGILL can be caught just like SIGQUIT. However, if a process trashes its stack pointer so badly that a signal cannot be delivered, then FreeBSD uncatches SIGILL and kills the process with a SIGILL. Crashme apparently trashes its stack pointer very quickly. Bruce From owner-freebsd-hackers Fri Dec 27 14:44:44 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA11991 for hackers-outgoing; Fri, 27 Dec 1996 14:44:44 -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 OAA11983 for ; Fri, 27 Dec 1996 14:44:41 -0800 (PST) Received: from phaeton.Artisoft.COM by mail.crl.com with SMTP id AA14585 (5.65c/IDA-1.5 for ); Fri, 27 Dec 1996 14:44:43 -0800 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA25350; Fri, 27 Dec 1996 15:34:40 -0700 From: Terry Lambert Message-Id: <199612272234.PAA25350@phaeton.artisoft.com> Subject: Re: unlink by inodes? To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 27 Dec 1996 15:34:40 -0700 (MST) Cc: freebsd-hackers@FreeBSD.org In-Reply-To: <199612191917.UAA28344@uriah.heep.sax.de> from "J Wunsch" at Dec 19, 96 08:17:12 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 J"org writes: > As Chris Csanady wrote: > > > Yeah. :) You really should try to use the fs as it was intended > > anyway. BTW, does anyone know the status of McKusick's soft > > updates integration? I think this would make a lot of people happy.. > > Do you perchance mean `mount -o async'? No, I don't think he does. Someone at the CSRG was rumored to be working on yet another 4.4BSD release. Rumor was that it was to include the Soft Updates code from the WWW posted Appendix A to the Ganger/Patt paper on Metadata updates. The Ganger/Patt code is from SVR4 and has been "sanitized" (read: SVR4 has mostly been ripped out, and a number of coding errors have been introduced). The problem with the Ganger/Patt code (besides that fact that Matt Day, mday@elbereth.org, has already integrated it last year on top of my layering patches required to make the namespace code work on the Artisoft Windows95 IFS port of the BSD4.4 Heidemann framework) is that it is not generalized... that is, it would be hard to maintain LFS, MFS, and so on in the face of a hacked up UFS layer. I am really skeptical of any soft updates implementation that doesn't approach a file system as an event/action based system with commutative and associative properties for the event/action node relations. Doing anything less means that you could not unify the model and abstract it from a particular implementation (in this case, SVR4 UFS or BSD UFS and FFS layers). My personal opinion is that any implementation short of this would end up being a kludge that would live on in infamy, a historical wart we could never successfully kill, for ever after. I've talked to Ganger a bit on this, but he isn't very hip on graphical least-path soloutions, and so wasn't terribly interested (all his work is in SVR4 anyway, so he doesn't have to deal with layer interactions between stacking layers anyway, so for him it's a non-problem). 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 Dec 27 15:07:44 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA12819 for hackers-outgoing; Fri, 27 Dec 1996 15:07:44 -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 PAA12810 for ; Fri, 27 Dec 1996 15:07:42 -0800 (PST) Received: from phaeton.Artisoft.COM by mail.crl.com with SMTP id AA18232 (5.65c/IDA-1.5 for ); Fri, 27 Dec 1996 15:07:48 -0800 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA25406; Fri, 27 Dec 1996 15:59:28 -0700 From: Terry Lambert Message-Id: <199612272259.PAA25406@phaeton.artisoft.com> Subject: Re: MMAP() problem partially solved... To: scrappy@hub.org (Marc G. Fournier) Date: Fri, 27 Dec 1996 15:59:28 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Marc G. Fournier" at Dec 21, 96 08:28:00 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 > First off, I've sort of found the problem I was having with storing > and recovering the 'int' value from the mmap()'d region... > > Since I was doing 'sprintf(mem_loc, "%d", value);', I was attempting > to store a 5byte char into a 4byte region, so memory overruns. I've changed > things so that I'm allocating 10bytes of space instead of 'sizeof(int)' to > get around that.. > > Still curious as to whether there is something better I should be using, > mind you...something like 'mem_loc = (char *)&size;'? > > Oh well...back to the code...sorry for the disruption... *(int *)mem_lock = value; /* store int without converting it*/ value = *(int *)mem_loc; /* retrieve int without converting it*/ This assumes that mem_lock is alignerd to a 4 byte boundry. 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 Dec 27 15:15:22 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA13114 for hackers-outgoing; Fri, 27 Dec 1996 15:15: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 PAA13109 for ; Fri, 27 Dec 1996 15:15:20 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA25449; Fri, 27 Dec 1996 16:09:36 -0700 From: Terry Lambert Message-Id: <199612272309.QAA25449@phaeton.artisoft.com> Subject: Re: odd problem with 2.2-Oct. SNAP + POP3 // fetchmail... To: patrick@night.xinside.com (Patrick Giagnocavo) Date: Fri, 27 Dec 1996 16:09:36 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: <199612240401.VAA07914@night.xinside.com> from "Patrick Giagnocavo" at Dec 23, 96 09:01:30 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 > Please respond to both patrick@xinside.com and pgiag@earthlink.net if > possible, in addition to the list if you wish... > > I am simply having the darndest time figuring out what is going on > between my ISP and my Dell XPi Notebook running 2.2-961014-SNAP. I am > using the iijppp (tun0 driver) package to connect to my ISP. > Everything connects fine, I can surf the WWW no problem. > > In trying to get my email though I see the following behavior: > > -- I connect via POP3 using either Netscape 3.01 Gold or using the > fetchmail client (latest version). > > -- connection is made, password accepted. Either client gets the > information about how many messages there are, and the size of the > first message. > > -- then, nothing; absolutely nothing. I can leave it alone as long as > I want, but no POP mail is downloaded. No modem lights blink, no data > seems to be transmitted. > > -- I have an ancient Mac (that I of course will not be taking on the > road with me as travel back East this Christmas). It is able to > download just fine. > > Ideas? There is a follow-on RFC (1957) to the POP RFC (1725) which explains this problem. Basically, your POP server is not compliant. 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 Dec 27 15:15:50 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA13148 for hackers-outgoing; Fri, 27 Dec 1996 15:15: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 PAA13143 for ; Fri, 27 Dec 1996 15:15:47 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA25429; Fri, 27 Dec 1996 16:06:08 -0700 From: Terry Lambert Message-Id: <199612272306.QAA25429@phaeton.artisoft.com> Subject: Re: ipretard.c selective tcp/ip queues and throughput limiters To: julian@whistle.com (Julian Elischer) Date: Fri, 27 Dec 1996 16:06:08 -0700 (MST) Cc: luigi@labinfo.iet.unipi.it, proff@iq.org, danny@panda.hilink.com.au, hackers@FreeBSD.ORG In-Reply-To: <32BEE215.167EB0E7@whistle.com> from "Julian Elischer" at Dec 23, 96 11:48:37 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 > but as Kieth sklower at CSRG told me.. > There's got to be a way to make it possible for essoteric or unusual > modules to be implimented OUT OF THE KERNEL, or > they are > (1) hard to prototype > (2) increasing the complexity of what IS in the kernel beyond the > point of debuggability :) You must abstract both the top and bottom end of the modules sufficiently; most modules are only abstracted sufficiently at the top end. For instance, for FS's, the VFS is well defined, but the VM interface for doing actual disk I/O is not well abstracted at all. This is what I've been calling "layering problems". It is definitely a goal of mine to allow a module to be debugged in user space with a source level debugger. 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 Dec 27 15:19:54 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA13278 for hackers-outgoing; Fri, 27 Dec 1996 15:19:54 -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 PAA13273 for ; Fri, 27 Dec 1996 15:19:51 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA25462; Fri, 27 Dec 1996 16:13:05 -0700 From: Terry Lambert Message-Id: <199612272313.QAA25462@phaeton.artisoft.com> Subject: Re: mount -o noatime unsupported in -current? To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 27 Dec 1996 16:13:05 -0700 (MST) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199612242118.WAA13246@uriah.heep.sax.de> from "J Wunsch" at Dec 24, 96 10:18: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 > > Yes, this is a nice trick ;) Then rm -rf works like hell ;-)) > > It's blindly fast and very dangerous ;) > > It's not that risky. In particular, if all you're doing is a large > `rm' operation, fsck should always be able to repair the filesystem > even in case of a catastrophic failure. This is true, as long as you do *nothing* other than the large rm before remounting 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 Fri Dec 27 15:32:33 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA13600 for hackers-outgoing; Fri, 27 Dec 1996 15:32: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 PAA13593 for ; Fri, 27 Dec 1996 15:32:29 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA25506; Fri, 27 Dec 1996 16:25:47 -0700 From: Terry Lambert Message-Id: <199612272325.QAA25506@phaeton.artisoft.com> Subject: Re: Help 'no buffer available'!! To: proff@suburbia.net Date: Fri, 27 Dec 1996 16:25:47 -0700 (MST) Cc: mango@staff.communique.net, hackers@FreeBSD.ORG In-Reply-To: <19961226064814.5747.qmail@suburbia.net> from "proff@suburbia.net" at Dec 26, 96 05:48:14 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 > > My poor news server is sick..... > > > > ----kiyoko:/var/log# ping akira > > PING akira.communique.net (204.27.65.10): 56 data bytes > > 64 bytes from 204.27.65.10: icmp_seq=0 ttl=255 time=0.867 ms > > ping: sendto: No buffer space available > > ping: wrote akira.communique.net 64 chars, ret=-1 > > ping: sendto: No buffer space available > > I often get this as well. What is the philosophy in having > sendto() et al return an error, rather than block until > buffer space is available? It is my opinion that an error return of this type is *absolutely necessary* to allow applications to correctly back off in "source quench" conditions. Don't misunderstand me... I think failure to meet bandwidth commitments is an evil, evil thing, and "leaky bucket" implementations of ATM and other non-committed rate transports should be banned and thier proponents hung. The general idea is that the provider sells to more customers than he has bandwidth to support, and everyone gets screwed equally as the bandwidth is overused. However. Source quench is something we have to live with, and it is arguable that your sending application is buggy if it is not handling the condition gracefully (see Stevens for a better discussion of sendto errors and their causes...). For your particular case, look for an mbuf leak on an error condition, since I believe taking the interface down and bringing it back up is known to clear the problem. 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 Dec 27 15:39:53 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA13901 for hackers-outgoing; Fri, 27 Dec 1996 15:39: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 PAA13892 for ; Fri, 27 Dec 1996 15:39:50 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA25520; Fri, 27 Dec 1996 16:33:05 -0700 From: Terry Lambert Message-Id: <199612272333.QAA25520@phaeton.artisoft.com> Subject: Re: multi-group file access techniques To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 27 Dec 1996 16:33:05 -0700 (MST) Cc: freebsd-hackers@freebsd.org, ben@narcissus.ml.org, owensc@enc.edu In-Reply-To: <199612261629.RAA08400@uriah.heep.sax.de> from "J Wunsch" at Dec 26, 96 05:29:31 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 > > >From what I've gleaned from these postings, one of the biggest problems > > with them is the potential for creating loops in the file tree, which fsck > > is generally very unhappy about. If one is very careful not to create > > Our fsck were always very unhappy about additional hardlinks to > directories. > > > such loops _is_ it possible to safely employ hard-linked directories (and > > keep fsck happy) ? I can certainly see that they're very dangerous, but > > can they be used safely with FreeBSD? Anyone? > > Directory hardlinks are impossible in FreeBSD. They have been > discontinued quite some time ago. Directory hard links were disabled as far back as 1.1.5.1; I believe fsck can detect a cycle and ignore it (it used to be able to anyway) while issuing a warning message. Tar and most other programs aren't so lucky, and frequently their heads explode. There are a lot of good resons for *not* allowing directory har links; the best is that an ancestor pointer can be maintained in the inode at create or rename time (when the parent pointer is being fixed for the ".." entry) to allow trivial reverse traversal. This is useful for ACL and trustee-style permissions which may be reverse inherited, and which may be implemented as a stacking layer. In point of fact, it is possible to seperate the concept of an in core vnode reference from an in core inode reference so that hard links are similar in most ways to symlinks -- alias inodes, I think they are called in one implementation. Because the vnode reference and the data content reference is seperate, it's possible to determine from an open file the path used to open the file. This has a large number of useful consequences for security models which are so obvious that there is no need to go into them. Basically, hard directory link removal is a transition stage to changing the in core represenetation of directory data. 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 Dec 27 15:53:14 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA14798 for hackers-outgoing; Fri, 27 Dec 1996 15:53:14 -0800 (PST) Received: from nlanr.net (oceana.sdsc.edu [132.249.40.200]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA14789 for ; Fri, 27 Dec 1996 15:53:12 -0800 (PST) Received: (from tony@localhost) by nlanr.net (8.7.3/8.7.3) id PAA05947 for hackers@freebsd.org; Fri, 27 Dec 1996 15:53:10 -0800 (PST) From: Tony Sterrett Message-Id: <199612272353.PAA05947@nlanr.net> Subject: xx_probe() in driver To: hackers@freebsd.org Date: Fri, 27 Dec 1996 15:53:10 -0800 (PST) X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I am write a driver with xx_probe(). I understand that the xx_probe() is called at system config time. How do I let the system know I want xx_probe() called? BTW I've followed the rules for developing drivers my read routine works but my xx_probe() it not called. Thanks in Advance. Tony From owner-freebsd-hackers Fri Dec 27 15:55:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA15015 for hackers-outgoing; Fri, 27 Dec 1996 15:55:19 -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 PAA15007 for ; Fri, 27 Dec 1996 15:55:16 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA25559; Fri, 27 Dec 1996 16:49:34 -0700 From: Terry Lambert Message-Id: <199612272349.QAA25559@phaeton.artisoft.com> Subject: Re: multi-group file access techniques (repost) To: owensc@enc.edu (Charles Owens) Date: Fri, 27 Dec 1996 16:49:34 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: from "Charles Owens" at Dec 26, 96 03:57:42 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'm trying to grapple with the challenge of how to allow multiple groups > and users (but not everyone) to have access to a directory hierarchy. We > don't have ACL's in FreeBSD, so I'm finding it a bit tricky. > > Below is an example of what I need to do. If you have any insights, > alternate approaches, please let me know! 1) Modify the VOP_ADVLOCK to be veto-based 2) Modify the VOP_LOCK code to be veto based. Call a top level vn_lock to call the underlying VOP_LOCK. Move the vclean locking to the top level code. Now NULLFS will no longer crash. If you have a 2.1.5 kernel, take my patches from -current in June of 1995; they contain this fix. Using NULLFS, prototype an FS layer that sits on top of an FS using the following user name space intrusions: 1) If a file name starts with #, byte-stuff it to ## 2) Use all #... file names as names associated with a base inode number 3) Add in the stacking layer a VOP_IOCTL operation for ACL's. 4) Add subfunctions for "create/delete/add/delete/get" ACL. 5) Write a user space utility to manipulate ACL's. 6) For a file in the directory named "foo", with inode "1745", the ACL file will be named "#1745". 7) Store all ACL's in the appropriate file. I recommend a sparse file. 8) Modify the VOP's which take names and call the common lookup code to enforce your ACL's. 9) remount the FS using the new NULL-derived ACL layer onto the same mount point. When backing up, unmount the ACL layer so the backup utility can see the ACL containers as files in the underlying FS. 10) If you support reverse inheritance, modify the UFS create to store the parent directory inode in the underlying inode. Add an option to fsck (during pass 7) to set these for the first time you start using the new UFS code. You now have *real* ACL's. Otherwise, live with the "goofy" intermediate directory scheme... if you don't like it exposed in the namespace, hide it using symlinks. 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 Dec 27 15:59:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA15288 for hackers-outgoing; Fri, 27 Dec 1996 15:59:20 -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 PAA15283 for ; Fri, 27 Dec 1996 15:59:18 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA25573; Fri, 27 Dec 1996 16:54:07 -0700 From: Terry Lambert Message-Id: <199612272354.QAA25573@phaeton.artisoft.com> Subject: Re: ACLs for BSD To: julian@whistle.com (Julian Elischer) Date: Fri, 27 Dec 1996 16:54:07 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: <32C303EB.41C67EA6@whistle.com> from "Julian Elischer" at Dec 26, 96 03:02: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 > In 1992 someone posted to the comp.unix.bsd list (I believe) > a set of patches to add ACLs to arbitrary files under 386BSD. > > Bill Jolitz and others considered it to be of interest, however it > seems to have gone from my archives. > > does anyone still have that tucked away? > it might be worth looking at again soem time. I have the code. It is limited to the number of free ints in the on disk inode (which is now larger than it was under 386BSD/FreeBSD 1.x). It would not be very effective with the new FS code (a limit of 2 or so ACL's). It (obviously) also suffers from the same problems as quotas, namely it's bogus because quota should be implemented as a stacking layer anyway so they can be applied to all fs's, and so they don't care about quotafile placement. 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 Dec 27 17:55:02 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA21860 for hackers-outgoing; Fri, 27 Dec 1996 17:55:02 -0800 (PST) Received: from rhiannon.clari.net.au (dns1.clari.net.au [203.27.85.9]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA21849 for ; Fri, 27 Dec 1996 17:54:58 -0800 (PST) Received: (from root@localhost) by rhiannon.clari.net.au (8.7.5/8.6.12) id MAA29279; Sat, 28 Dec 1996 12:55:15 +1100 (EST) Date: Sat, 28 Dec 1996 12:55:15 +1100 (EST) From: Peter Hawkins Message-Id: <199612280155.MAA29279@rhiannon.clari.net.au> To: hans@brandinnovators.com Subject: memory test Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hans, I have a suspected memory fault on a key server. I'd really appreciate a copy of your diagnostic if you get it going. Better yet, submit it as the first item for a new /usr/ports/diags - desperately needed! Peter From owner-freebsd-hackers Fri Dec 27 19:03:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA23727 for hackers-outgoing; Fri, 27 Dec 1996 19:03:18 -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 TAA23720 for ; Fri, 27 Dec 1996 19:03:13 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id NAA00491; Sat, 28 Dec 1996 13:28:58 +1030 (CST) From: Michael Smith Message-Id: <199612280258.NAA00491@genesis.atrad.adelaide.edu.au> Subject: Re: bootloader & memory test... In-Reply-To: <32C4161E.41C67EA6@whistle.com> from Julian Elischer at "Dec 27, 96 10:31:58 am" To: julian@whistle.com (Julian Elischer) Date: Sat, 28 Dec 1996 13:28:57 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, hans@brandinnovators.com, 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 Julian Elischer stands accused of saying: > > The FreeBSD botblocks set themselves to be in a flat 32bit address > space as well. They do use up more of the bottom 640K, > (but you can control where they put themselves in ram at compile time) > > so it should be possible to add the function into one of the > .s files I thought the bootblocks were fill'd to overflowing? Still, the bootblock in question is full of 'bde' comments. Is there a bootloader _anywhere_ in the free Unix world that Bruce _hasn't_ been involved in? 8) -- ]] 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 Fri Dec 27 19:07:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA23974 for hackers-outgoing; Fri, 27 Dec 1996 19:07: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 TAA23947 for ; Fri, 27 Dec 1996 19:07:50 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id NAA00509; Sat, 28 Dec 1996 13:37:42 +1030 (CST) From: Michael Smith Message-Id: <199612280307.NAA00509@genesis.atrad.adelaide.edu.au> Subject: Re: xx_probe() in driver In-Reply-To: <199612272353.PAA05947@nlanr.net> from Tony Sterrett at "Dec 27, 96 03:53:10 pm" To: tony@nlanr.net (Tony Sterrett) Date: Sat, 28 Dec 1996 13:37:41 +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 Tony Sterrett stands accused of saying: > I am write a driver with xx_probe(). I understand that the > xx_probe() is called at system config time. How do I let the > system know I want xx_probe() called? BTW I've followed the > rules for developing drivers my read routine works but > my xx_probe() it not called. You need a non-static isa_driver structure called 'xxdriver', which is concatenated into a linker set at link time. Look at any other device driver for an example of this; basically yours would look like : struct isa_driver xxdriver = { xx_probe, xx_attach, "xx", 0}; (Make the 0 a 1 if your hardware is very touchy about being probed and you want a chance to go first for your nominated I/O space.) Because of this, the only non-static function in your driver should be the interrupt handler. > 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 Fri Dec 27 19:23:59 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA24599 for hackers-outgoing; Fri, 27 Dec 1996 19:23:59 -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 TAA24594 for ; Fri, 27 Dec 1996 19:23:56 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id WAA07203; Fri, 27 Dec 1996 22:19:01 -0500 (EST) From: "John S. Dyson" Message-Id: <199612280319.WAA07203@dyson.iquest.net> Subject: Re: ipretard.c selective tcp/ip queues and throughput limiters To: terry@lambert.org (Terry Lambert) Date: Fri, 27 Dec 1996 22:19:01 -0500 (EST) Cc: julian@whistle.com, luigi@labinfo.iet.unipi.it, proff@iq.org, danny@panda.hilink.com.au, hackers@freebsd.org In-Reply-To: <199612272306.QAA25429@phaeton.artisoft.com> from "Terry Lambert" at Dec 27, 96 04:06:08 pm 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 > > For instance, for FS's, the VFS is well defined, but the VM interface > for doing actual disk I/O is not well abstracted at all. > The VM code uses direct disk input when the filesystem allows it. Otherwise, the filesystems can do VOP_READ operations as in normal UFS read write operations. The vnode pageout uses VOP_WRITE operations. Refer to vnode_pager (where the VM input output operations happen.) I don't think that there are layering problems anymore (there were initially though.) Note that the filesystem can take over all paging operations now -- used to be they couldn't. John From owner-freebsd-hackers Fri Dec 27 19:59:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA25626 for hackers-outgoing; Fri, 27 Dec 1996 19:59:58 -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 TAA25621 for ; Fri, 27 Dec 1996 19:59:56 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by chai.plexuscom.com (8.8.4/8.6.12) with SMTP id XAA00822; Fri, 27 Dec 1996 23:00:57 -0500 (EST) Message-Id: <199612280400.XAA00822@chai.plexuscom.com> X-Authentication-Warning: chai.plexuscom.com: localhost [127.0.0.1] didn't use HELO protocol To: hackers@FreeBSD.ORG Cc: Terry Lambert Subject: Re: multi-group file access techniques (repost) In-reply-to: Your message of "Fri, 27 Dec 1996 16:49:34 MST." <199612272349.QAA25559@phaeton.artisoft.com> Date: Fri, 27 Dec 1996 23:00:57 -0500 From: Bakul Shah Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert writes: > Using NULLFS, prototype an FS layer that sits on top of an FS using the > following user name space intrusions: ...[`intrusions' on the ACLs via a special FS layer deleted]... > You now have *real* ACL's. Here is another idea -- perhaps more in `the spirit of Unix' (IMHO). or plan9. * Implement a group FS layer. The group-fs allows group membership related operations via the familiar file system interface. For example, # enable group-fs $ mount groupfs /system/groups # Add a new user to the wheel group $ cd /system/groups/wheel # each group has its own dir. $ ls root $ touch joe # joe must be a known user $ ls root joe # Create a new group $ cd /system/groups $ mkdir my-group # Use this new group $ cd $HOME $ chgrp my-group file1 file2 dir ... Treating groups as directories also solves the problem of who can add/delete group members (depends on the permission bits of the group dir). If a group is added as a subdir in another group dir, the first group's members are automatically members of the latter group. In this scheme a file's gid maps on to an i-number of a group dir (on the group-fs). Checking group permissions on a file `foo' is then equivalent to a lookup for an entry with ino == user's id, starting with a group dir whose vnode is derived from foo's gid. There are some obvious problems with the scheme as sketched out (afterall, I thought of this scheme only about 15 minutes back) but I believe they ought to be solvable. If you want `path-access-control' where accessability of a file is a function of the path used (I think this is what Terry calls reverse inheritance), the group-fs would need to be a bit smarter. Perhaps a validating program or a list of regular expressions can be stored in the group dir. I prefer controlling ACLs via groups in this way because a) 4 billion groups ought to be enough for a while and if you want you can put each file in a different group. b) Multiple files can share the same group memebers. In an ACL per file approach you may need to create separate lists. c) The above scheme can be used, for instance, to tighten control over exisiting collection of files by changing existing group's membership but *without* changing file inodes. d) Finer grained control over who can change group membeship etc. and yet a whole group of files can be simulteneously controlled. To make this really effective I'd also want a user-fs, to keep track of users. This would make system administration easier too! # enable user-fs $ mount userfs /system/users # add a new user $ cd /system/users $ mkdir bubba # this will automatically create files in # this new dir based on some default dir. $ ls bubba gid gecos home limits passwd shell uid ... The same sort of thing can be done with a number of other /etc files. An FS abstraction allows you to take advantage of other features available on files (such as explicit control and distribution of responsibility of who can add/delete instances of some object-type). Also, file paths map nicely to URLs! :-) Assuming, of course, all of this can be done reasonably efficiently (and if the FS API is light-weight enough). Comments? -- bakul From owner-freebsd-hackers Fri Dec 27 21:26:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA28154 for hackers-outgoing; Fri, 27 Dec 1996 21:26:24 -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 VAA28149 for ; Fri, 27 Dec 1996 21:26: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 VAA05903; Fri, 27 Dec 1996 21:19:55 -0800 (PST) Message-ID: <32C4ADBA.41C67EA6@whistle.com> Date: Fri, 27 Dec 1996 21:18:50 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Michael Smith CC: hans@brandinnovators.com, freebsd-hackers@freebsd.org Subject: Re: bootloader & memory test... References: <199612280258.NAA00491@genesis.atrad.adelaide.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith wrote: > > Julian Elischer stands accused of saying: > > > > The FreeBSD botblocks set themselves to be in a flat 32bit address > > space as well. They do use up more of the bottom 640K, > > (but you can control where they put themselves in ram at compile time) > > > > so it should be possible to add the function into one of the > > .s files > > I thought the bootblocks were fill'd to overflowing? > > Still, the bootblock in question is full of 'bde' comments. Is there > a bootloader _anywhere_ in the free Unix world that Bruce _hasn't_ been > involved in? 8) I was thinking more in line of cloning that code as a starting point fpr a stand-alone memory tester.. dd it to to a floppy and reboot for a test..:) From owner-freebsd-hackers Fri Dec 27 21:40:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA28747 for hackers-outgoing; Fri, 27 Dec 1996 21:40:58 -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 VAA28742 for ; Fri, 27 Dec 1996 21:40:56 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id QAA00707; Sat, 28 Dec 1996 16:06:43 +1030 (CST) From: Michael Smith Message-Id: <199612280536.QAA00707@genesis.atrad.adelaide.edu.au> Subject: Re: bootloader & memory test... In-Reply-To: <32C4ADBA.41C67EA6@whistle.com> from Julian Elischer at "Dec 27, 96 09:18:50 pm" To: julian@whistle.com (Julian Elischer) Date: Sat, 28 Dec 1996 16:06:42 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, hans@brandinnovators.com, 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 Julian Elischer stands accused of saying: > I was thinking more in line of cloning that code as a starting point > fpr a stand-alone memory tester.. > dd it to to a floppy and reboot for a test..:) That's what it does already. I've rewritten it almost completely with the goal of getting it into the bootloader, but the best I can do is too big : lovely:~/work/sys/i386/boot/biosboot>size mtest.o text data bss dec hex 1040 32 84 1156 484 By stripping some options it can go a little smaller, but I'm still about 200 bytes short. Any idea how easy it is to make a kernel-substitute; something else one can boot? -- ]] 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 Dec 28 00:27:11 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA03021 for hackers-outgoing; Sat, 28 Dec 1996 00:27:11 -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 AAA03013 for ; Sat, 28 Dec 1996 00:27:05 -0800 (PST) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id DAA24129; Sat, 28 Dec 1996 03:24:46 -0500 From: Bill Paul Message-Id: <199612280824.DAA24129@skynet.ctr.columbia.edu> Subject: Re: bootloader & memory test... To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Sat, 28 Dec 1996 03:24:45 -0500 (EST) Cc: julian@whistle.com, hans@brandinnovators.com, hackers@freebsd.org In-Reply-To: <199612280536.QAA00707@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Dec 28, 96 04:06:42 pm 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, Michael Smith had to walk into mine and say: > Julian Elischer stands accused of saying: > > I was thinking more in line of cloning that code as a starting point > > fpr a stand-alone memory tester.. > > dd it to to a floppy and reboot for a test..:) > > That's what it does already. I've rewritten it almost completely with > the goal of getting it into the bootloader, but the best I can do is > too big : > > lovely:~/work/sys/i386/boot/biosboot>size mtest.o > text data bss dec hex > 1040 32 84 1156 484 > > By stripping some options it can go a little smaller, but I'm still > about 200 bytes short. > > Any idea how easy it is to make a kernel-substitute; something else one > can boot? I while back I rigged up a standalone version of the bootloader which you could load instead of the kernel. Normally the kernel is loaded at address 0x00100000 in memory; I created a startup routine that would copy the boot block down from that location back to 0x00010000 (where the boot code usually executes) and then transfer control to itself at the lower address. It took me several weeks and a couple of books before I was able to wrap my brain around the concepts of global descriptor tables and real mode vs. protected mode memory model, and even then I wasn't entirely sure what the hell I was doing (debugging a standalone image ain't easy, y'know). I pulled a couple of disgusting tricks to make it work, like frobbing the start address in the a.out header of the image so that our boot loader would read it into the correct memory location (the image was actually linked at address 0; loading it at address 0 wouldn't hav worked )and rebuilding the GDT from scratch since I ended up wiping out the old GDT by overwritting the old boot code with my image. Also, I linked my image as an OMAGIC executable, which wouldn't load correctly at first because our boot loader assumes that the image it loads will always be a ZMAGIC executable. There are a couple of things you can look for: - If you hunt around for the most recent release of Mach on the net, you'll find that it includes a network boot loader that's meant to be linked as a standalone image. (It was the earlier version of this code that gave rise to our existing boot loader.) The only problem is that the Mach assembler is apparently not quite the same as ours, so even though you may get the code to compile and link on FreeBSD, it won't execute unless you tweak some stuff. - OpenBSD has (if you look hard enough) a libsa for the 386 architecture. There were some commit messages in the openbsd-commit archibe about it, which prompted me to grab a copy. It was committed to a seperate branch though, and the commit message was lost when freefall lunched one of its disks recently. I forget was the branch tag was. Basically what they did was split up the BIOS code into seperate machine dependent bits and combined it with the machine independent bits to generate a complete library. I happen to like the libsa idea since their code has support for UFS, NFS, RARP, BOOTP, bootparams, and a bunch of other things. Unfortunately, while I was able to get it to compile and load, I never did get it to boot the FreeBSD kernel (I could read it into memory, but their code doesn't have the bootinfo stuff that we do, and I lost interest when I couldn't figure out how to fake my own bootinfo struct and pass it to the kernel correctly.) -Bill -- ============================================================================= -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 Sat Dec 28 04:33:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA10892 for hackers-outgoing; Sat, 28 Dec 1996 04:33:24 -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 EAA10886 for ; Sat, 28 Dec 1996 04:32:59 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id XAA17456; Sat, 28 Dec 1996 23:29:54 +1100 Date: Sat, 28 Dec 1996 23:29:54 +1100 From: Bruce Evans Message-Id: <199612281229.XAA17456@godzilla.zeta.org.au> To: julian@whistle.com, msmith@atrad.adelaide.edu.au Subject: Re: bootloader & memory test... Cc: freebsd-hackers@freebsd.org, hans@brandinnovators.com Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >That's what it does already. I've rewritten it almost completely with >the goal of getting it into the bootloader, but the best I can do is >too big : > >lovely:~/work/sys/i386/boot/biosboot>size mtest.o >text data bss dec hex >1040 32 84 1156 484 > >By stripping some options it can go a little smaller, but I'm still >about 200 bytes short. Can't you strip 7K of code from the boot loader? There is no need to boot FreeBSD after running the memory test. Bruce From owner-freebsd-hackers Sat Dec 28 05:57:35 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA12762 for hackers-outgoing; Sat, 28 Dec 1996 05:57:35 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA12753; Sat, 28 Dec 1996 05:57:20 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id OAA04170; Sat, 28 Dec 1996 14:46:39 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.4/8.8.2) id OAA15421; Sat, 28 Dec 1996 14:34:00 +0100 (MET) Message-ID: Date: Sat, 28 Dec 1996 14:34:00 +0100 From: andreas@klemm.gtn.com (Andreas Klemm) To: se@FreeBSD.org Cc: hackers@FreeBSD.org Subject: option FAILSAFE in GENERIC and LINT a bit misleading ? X-Mailer: Mutt 0.54-PL15 Mime-Version: 1.0 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk When grepping for the keyword FAILSAFE in the kernel tree, the one and only kernel module that uses FAILSAFE is that from Stefan Esser. I had tought, that FAILSAFE for example uses the old bcopy routines for i586 machines and generally extra "sanity" in a wider area of kernel modules. Don't get me wrong, I like this idea about FAILSAFE, but currently there is a big gap between documentation in LINT and real use of this option in the kernel. I'd suggest to rename the FAILSAFE option to NCR_FAILSAFE until other modules use this FAILSAFE option as well. Now it could confuse or mislead people who really think, that it does something good about stability ... Currently it's only concerning stability in one ncr scsi controller driver. I'd suggest renaming the option to NCR_FAILSAFE and to really document in the kernel profile, what it does within the NCR driver. Here what's currently in LINT and GENERIC in -current. >From LINT: # When this is set, be extra conservative in various parts of the kernel # and choose functionality over speed (on the widest variety of systems). options FAILSAFE >From GENERIC: options FAILSAFE #Be conservative Andreas /// -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-hackers Sat Dec 28 06:26:07 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA13352 for hackers-outgoing; Sat, 28 Dec 1996 06:26:07 -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 GAA13347 for ; Sat, 28 Dec 1996 06:26:04 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id AAA01299; Sun, 29 Dec 1996 00:55:43 +1030 (CST) From: Michael Smith Message-Id: <199612281425.AAA01299@genesis.atrad.adelaide.edu.au> Subject: Re: bootloader & memory test... In-Reply-To: <199612281229.XAA17456@godzilla.zeta.org.au> from Bruce Evans at "Dec 28, 96 11:29:54 pm" To: bde@zeta.org.au (Bruce Evans) Date: Sun, 29 Dec 1996 00:55:42 +1030 (CST) Cc: julian@whistle.com, msmith@atrad.adelaide.edu.au, freebsd-hackers@freebsd.org, hans@brandinnovators.com 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 Bruce Evans stands accused of saying: > > > >By stripping some options it can go a little smaller, but I'm still > >about 200 bytes short. > > Can't you strip 7K of code from the boot loader? There is no need to > boot FreeBSD after running the memory test. That's not the object; I wanted to add it as a feature to the standard bootloader (if it could be easily done). New user : "halfway through the install I get this sig-11 message" Us : "your RAM is bad" Nu : "norton sez its ok" U : "norton is no good" Nu: "how do I test my RAM then" U: "type 'mem_test'" at the 'boot' prompt" The code as-is works fine standalone; I have no desire to reinvent the wheel. Hence the follow-on question about making it boot/run standalone. > Bruce -- ]] 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 Dec 28 10:19:11 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA19884 for hackers-outgoing; Sat, 28 Dec 1996 10:19:11 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA19875; Sat, 28 Dec 1996 10:18:57 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id KAA07432; Sat, 28 Dec 1996 10:18:51 -0800 (PST) To: andreas@klemm.gtn.com (Andreas Klemm) cc: se@FreeBSD.org, hackers@FreeBSD.org Subject: Re: option FAILSAFE in GENERIC and LINT a bit misleading ? In-reply-to: Your message of "Sat, 28 Dec 1996 14:34:00 +0100." Date: Sat, 28 Dec 1996 10:18:51 -0800 Message-ID: <7429.851797131@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I'd suggest to rename the FAILSAFE option to NCR_FAILSAFE until > other modules use this FAILSAFE option as well. I think it'd be far better just to get other modules using FAILSAFE as soon as we can. Why change something we're only going to have to change back again? Jordan From owner-freebsd-hackers Sat Dec 28 12:26:25 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA23564 for hackers-outgoing; Sat, 28 Dec 1996 12:26:25 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA23559 for ; Sat, 28 Dec 1996 12:26:22 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id VAA03202; Sat, 28 Dec 1996 21:15:39 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.4/8.8.2) id VAA09253; Sat, 28 Dec 1996 21:07:13 +0100 (MET) Message-ID: Date: Sat, 28 Dec 1996 21:07:13 +0100 From: andreas@klemm.gtn.com (Andreas Klemm) To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: hackers@freebsd.org Subject: Re: option FAILSAFE in GENERIC and LINT a bit misleading ? References: <7429.851797131@time.cdrom.com> X-Mailer: Mutt 0.54-PL15 Mime-Version: 1.0 In-Reply-To: <7429.851797131@time.cdrom.com>; from "Jordan K. Hubbard" on Dec 28, 1996 10:18:51 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard writes: > > I'd suggest to rename the FAILSAFE option to NCR_FAILSAFE until > > other modules use this FAILSAFE option as well. > > I think it'd be far better just to get other modules using FAILSAFE > as soon as we can. Why change something we're only going to have to > change back again? I think you are right, if that option actually would be used. FAILSAFE exists since months now and nobody uses it. I have very often the problem, that my FreeBSD system simply hangs. It might be a hardware failure. I don't know exactly. Today I decided to try to build a kernel using the FAILSAFE option, because I thought it might make my system running more solid. After a new kernel build I had the feeling to look at the sources, what FAILSAFE is actually doing... The 'find /usr/src/sys -type f -print | xargs grep FAILSAFE' was a bit disappointing, since only ncr.c uses it. So I came to the conclusion, that FAILSAFE and it's description in LINT and GENERIC is totally misleading, since it currently brings nothing at all. It's only used in one driver. I think FAILSAFE is a good thing, but it's description is currently totally misleading for a "end (novice) user". Therefore I'd vote for a better description in GENERIC and LINT, what FAILSAFE actually does for a 2.2 or -current system. -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-hackers Sat Dec 28 15:00:29 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA00231 for hackers-outgoing; Sat, 28 Dec 1996 15:00:29 -0800 (PST) Received: from moonpie.w8hd.org (root@moonpie.w8hd.org [198.252.159.14]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA00226 for ; Sat, 28 Dec 1996 15:00:27 -0800 (PST) Received: from moonpie.w8hd.org (kimc@moonpie.w8hd.org [198.252.159.14]) by moonpie.w8hd.org (8.8.4/8.8.2) with SMTP id SAA28444 for ; Sat, 28 Dec 1996 18:00:26 -0500 (EST) Date: Sat, 28 Dec 1996 18:00:26 -0500 (EST) From: Kim Culhan To: hackers@freebsd.org Subject: vi edit mode unstable -termcap ? 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 have had this problem here for some time, searched for the cause today and cannot find it. On two -current machines here, when using an xterm and telnet to the other machine, when using the arrow-keys to move around the screen, vi will switch to the insert mode and deposit characters into the editor. For example if I hit the down-arrow key a few times, after about 3 or 4 arrow-down, it will begin to put 'B' into the editor. Same for the other arrow keys, 'A' for up-arrow etc. On a third machine running 2.2-current from 9-15 I can telnet to it from either of the other machines and it will not do this. I can't find a difference in the termcap files, what can be causing this ? regards kim -- kimc@w8hd.org From owner-freebsd-hackers Sat Dec 28 15:11:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA00567 for hackers-outgoing; Sat, 28 Dec 1996 15:11:30 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA00559; Sat, 28 Dec 1996 15:11:23 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr2-49.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA18018 (5.67b/IDA-1.5); Sun, 29 Dec 1996 00:11:19 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.4/8.6.9) id AAA02435; Sun, 29 Dec 1996 00:11:19 +0100 (CET) Message-Id: Date: Sun, 29 Dec 1996 00:11:18 +0100 From: se@FreeBSD.org (Stefan Esser) To: andreas@klemm.gtn.com (Andreas Klemm) Cc: se@FreeBSD.org, hackers@FreeBSD.org Subject: Re: option FAILSAFE in GENERIC and LINT a bit misleading ? References: X-Mailer: Mutt 0.54-PL15 Mime-Version: 1.0 In-Reply-To: ; from Andreas Klemm on Dec 28, 1996 14:34:00 +0100 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Dec 28, andreas@klemm.gtn.com (Andreas Klemm) wrote: > I'd suggest renaming the option to NCR_FAILSAFE and to really > document in the kernel profile, what it does within the NCR > driver. Well, and I'd suggest to NOT rename it, and to hope it will find further use in other parts of the kernel. FAILSAFE was intended for install kernels, where it is more important to have the system running, than to get best performance out of it. And the documentation mentions this suggested use. I don't think it matters, whether the kernel uses it for example to select a more conservative bcopy, since it is up to the people supporting that code, to make sure it works on all systems, at least with the boot floppy kernel. They don't have to use it, if they don't see the need, but the possibility should be documented, and it is ... Regards, STefan From owner-freebsd-hackers Sat Dec 28 19:42:36 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA11557 for hackers-outgoing; Sat, 28 Dec 1996 19:42:36 -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 TAA11550 for ; Sat, 28 Dec 1996 19:42:31 -0800 (PST) Received: (from joe@localhost) by monk.via.net (8.6.11/8.6.12) id TAA08249 for hackers@freebsd.org; Sat, 28 Dec 1996 19:41:53 -0800 Date: Sat, 28 Dec 1996 19:41:53 -0800 From: Joe McGuckin Message-Id: <199612290341.TAA08249@monk.via.net> To: hackers@freebsd.org Subject: netstats for aliased interfaces? X-Sun-Charset: US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We run Apache web servers and ftp servers on FreeBSD. How hard would it be to modify the kernel to keep seperate octet counts of network devices - with aliases ethernet devices broken out by IP? -joe From owner-freebsd-hackers Sat Dec 28 20:53:38 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA13894 for hackers-outgoing; Sat, 28 Dec 1996 20:53:38 -0800 (PST) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id UAA13889 for ; Sat, 28 Dec 1996 20:53:36 -0800 (PST) Received: by agora.rdrop.com (Smail3.1.29.1 #17) id m0veDFb-0008uPC; Sat, 28 Dec 96 20:53 PST Message-Id: From: batie@agora.rdrop.com (Alan Batie) Subject: pppd & utmp To: hackers@freebsd.org Date: Sat, 28 Dec 1996 20:53:31 -0800 (PST) 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 I've installed the latest getty w/ ppp detection, and it's working great. I added some minor hacks to pppd as a result, in order to get utmp updated as well (instead of just wtmp, as it currently does). It's enabled with the "utmp" option. I'd like to add something that identifies them as being ppp users, but I'm not quite sure what the "correct" approach should be. Thoughts: 1. put "ppp" in the hostname field 2. put the hostname associated with the assigned IP address in the hostname field (this feels "most" correct, but is more work) 3. do nothing --- they're not really logging in over the network, don't corrupt the meaning of the hostname field and it's none of your business anyhow Likewise, pppd just shows up in ps as being "root" and "pppd"; you have to look at the tty then run w to see who it is. I'm thinking of having pppd modify it's arguments to show the user as argv[1], but I'm not sure how to do that safely. Do you just change the argv[1] pointer value? I suppose I could go look at sendmail or something else that does it... -- Alan Batie ______ batie@agora.rdrop.com \ / Assimilate this! +1 503 452-0960 \ / --Worf, First Contact DE 3C 29 17 C0 49 7A 27 \/ 40 A5 3C 37 4A DA 52 B9 It is my policy to avoid purchase of any products from companies which use unrequested email advertisements or telephone solicitation. From owner-freebsd-hackers Sat Dec 28 22:30:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA16320 for hackers-outgoing; Sat, 28 Dec 1996 22:30:20 -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 WAA16315 for ; Sat, 28 Dec 1996 22:30:18 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id RAA02704; Sun, 29 Dec 1996 17:00:12 +1030 (CST) From: Michael Smith Message-Id: <199612290630.RAA02704@genesis.atrad.adelaide.edu.au> Subject: Re: pppd & utmp In-Reply-To: from Alan Batie at "Dec 28, 96 08:53:31 pm" To: batie@agora.rdrop.com (Alan Batie) Date: Sun, 29 Dec 1996 17:00:11 +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 Alan Batie stands accused of saying: > > Likewise, pppd just shows up in ps as being "root" and "pppd"; you have to > look at the tty then run w to see who it is. I'm thinking of having pppd > modify it's arguments to show the user as argv[1], but I'm not sure how to > do that safely. Do you just change the argv[1] pointer value? I suppose > I could go look at sendmail or something else that does it... 'man setproctitle' > Alan Batie ______ -- ]] 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 Dec 28 23:22:59 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA17624 for hackers-outgoing; Sat, 28 Dec 1996 23:22:59 -0800 (PST) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA17619 for ; Sat, 28 Dec 1996 23:22:54 -0800 (PST) Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id SAA25381; Sun, 29 Dec 1996 18:32:47 +1100 (EST) Date: Sun, 29 Dec 1996 18:32:46 +1100 (EST) From: "Daniel O'Callaghan" To: Joe McGuckin cc: hackers@freebsd.org Subject: Re: netstats for aliased interfaces? In-Reply-To: <199612290341.TAA08249@monk.via.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 Sat, 28 Dec 1996, Joe McGuckin wrote: > We run Apache web servers and ftp servers on FreeBSD. How hard would it be > to modify the kernel to keep seperate octet counts of network devices - with > aliases ethernet devices broken out by IP? An alternative would be to use the IPFW accounting and define rules for each IP address. That way you can track bytes/service too. Danny From owner-freebsd-hackers Sat Dec 28 23:28:29 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA17734 for hackers-outgoing; Sat, 28 Dec 1996 23:28:29 -0800 (PST) Received: from xi.omniscient.com (root@cust89.max1.seattle.aa.net [205.199.141.89]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA17726 for ; Sat, 28 Dec 1996 23:28:27 -0800 (PST) Received: from localhost (smpatel@localhost [127.0.0.1]) by xi.omniscient.com (8.7.5/8.6.12) with SMTP id XAA07040; Sat, 28 Dec 1996 23:27:54 -0800 (PST) Date: Sat, 28 Dec 1996 23:27:52 -0800 (PST) From: Sujal Patel X-Sender: smpatel@xi.omniscient.com To: Amancio Hasty cc: Luigi Rizzo , hackers@freebsd.org Subject: Re: Any support for PnP ? In-Reply-To: <199612261137.DAA00365@rah.star-gate.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 Thu, 26 Dec 1996, Amancio Hasty wrote: > Sujal Patel is the guy you want to talk to . He has code to init > PnP cards available for FreeBSD . Also you may want to take a look > at the GUS PnP driver which inits the GUS PnP and takes its configuration > paramaters from the config file. The latest sources are at: http://www.freebsd.org/~smpatel/FreeBSD-ISA_PnP.README http://www.freebsd.org/~smpatel/FreeBSD-ISA_PnP_June8.tar.gz http://www.freebsd.org/~smpatel/pnpget.c http://www.freebsd.org/~smpatel/pnpget.h I haven't had much time to work on this stuff recently, I hope to get back to it soon... Sujal From owner-freebsd-hackers Sat Dec 28 23:33:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA17897 for hackers-outgoing; Sat, 28 Dec 1996 23:33:06 -0800 (PST) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA17892 for ; Sat, 28 Dec 1996 23:32:59 -0800 (PST) Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id SAA25395; Sun, 29 Dec 1996 18:42:55 +1100 (EST) Date: Sun, 29 Dec 1996 18:42:54 +1100 (EST) From: "Daniel O'Callaghan" To: Alan Batie cc: hackers@freebsd.org Subject: Re: pppd & utmp 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, 28 Dec 1996, Alan Batie wrote: > I've installed the latest getty w/ ppp detection, and it's working great. > I added some minor hacks to pppd as a result, in order to get utmp updated > as well (instead of just wtmp, as it currently does). It's enabled with > the "utmp" option. I'd like to add something that identifies them as > being ppp users, but I'm not quite sure what the "correct" approach should > be. Thoughts: > > 1. put "ppp" in the hostname field This is already done, if you use the pppd in -current. Uses a host of ":PPP". > 2. put the hostname associated with the assigned IP address in the hostname > field (this feels "most" correct, but is more work) Could be useful for debugging, when a customer rings up to say nothing works. > Likewise, pppd just shows up in ps as being "root" and "pppd"; you have to > look at the tty then run w to see who it is. I'm thinking of having pppd > modify it's arguments to show the user as argv[1], but I'm not sure how to > do that safely. Do you just change the argv[1] pointer value? I suppose > I could go look at sendmail or something else that does it... This would be really neat. Please do as Mike Smith suggests and read setproctitle(3), and then implement it. Uname and IP address would be good, and that solves whether to put the IP address into utmp. I do suggest you start by pulling -current sources and comparing them with your own. regards, Danny From owner-freebsd-hackers Sat Dec 28 23:38:26 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA18084 for hackers-outgoing; Sat, 28 Dec 1996 23:38:26 -0800 (PST) Received: from sdev.usn.blaze.net.au (sdev.usn.blaze.net.au [203.17.53.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA18078 for ; Sat, 28 Dec 1996 23:38:20 -0800 (PST) Received: (from davidn@localhost) by sdev.usn.blaze.net.au (8.8.4/8.6.9) id SAA04010; Sun, 29 Dec 1996 18:37:55 +1100 (EST) Message-ID: Date: Sun, 29 Dec 1996 18:37:55 +1100 From: davidn@sdev.usn.blaze.net.au (David Nugent) To: kimc@w8hd.org (Kim Culhan) Cc: hackers@freebsd.org Subject: Re: vi edit mode unstable -termcap ? References: X-Mailer: Mutt 0.54 Mime-Version: 1.0 In-Reply-To: ; from Kim Culhan on Dec 28, 1996 18:00:26 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Kim Culhan writes: > I have had this problem here for some time, searched for the cause today > and cannot find it. > > On two -current machines here, when using an xterm and telnet to the other > machine, when using the arrow-keys to move around the screen, vi will > switch to the insert mode and deposit characters into the editor. > > For example if I hit the down-arrow key a few times, after about > 3 or 4 arrow-down, it will begin to put 'B' into the editor. Yes, this is really VERY annoying. I have the same problem with any network connections, even across 10mb ethernet, which is just plain crazy. The workaround (and it IS only a workaround!) is to put set escapetime=10 into ~/.exrc. Could the maintainer of nvi PLEASE use a more reasonable default value for escapetime? This is problematic even editing in an xterm locally on a system running under a reasonable load. > On a third machine running 2.2-current from 9-15 I can telnet to it > from either of the other machines and it will not do this. This started with the recent vendor import of the new version of nvi. "split" disappeared too. :-( 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@freefall.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-hackers Sat Dec 28 23:46:44 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA18273 for hackers-outgoing; Sat, 28 Dec 1996 23:46:44 -0800 (PST) Received: from sdev.usn.blaze.net.au (sdev.usn.blaze.net.au [203.17.53.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA18266 for ; Sat, 28 Dec 1996 23:46:39 -0800 (PST) Received: (from davidn@localhost) by sdev.usn.blaze.net.au (8.8.4/8.6.9) id SAA04024; Sun, 29 Dec 1996 18:46:29 +1100 (EST) Message-ID: Date: Sun, 29 Dec 1996 18:46:28 +1100 From: davidn@sdev.usn.blaze.net.au (David Nugent) To: batie@agora.rdrop.com (Alan Batie) Cc: hackers@freebsd.org Subject: Re: pppd & utmp References: X-Mailer: Mutt 0.54 Mime-Version: 1.0 In-Reply-To: ; from Alan Batie on Dec 28, 1996 20:53:31 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Alan Batie writes: > I've installed the latest getty w/ ppp detection, and it's working great. > I added some minor hacks to pppd as a result, in order to get utmp updated > as well (instead of just wtmp, as it currently does). It's enabled with > the "utmp" option. I'd like to add something that identifies them as > being ppp users Hmm, I had the opposite problem with mgetty recently (which I use for other reasons - namely I need/want to monitor and initialise modems rather than use them in 'dumb' mode, which I do not trust, and I want "manual" answer rather than auto-answer). Users were shown in utmp as "ppp" and not by their correct logins. Needless to say, I found this particularly useless for accounting purposes, so I immediately disabled it. Looks like I may have overlooked an option, so thanks for the pointer. :) > 1. put "ppp" in the hostname field > 2. put the hostname associated with the assigned IP address in the hostname > field (this feels "most" correct, but is more work) Actually, that'd be the most useful imho. And, yep, having written perl code to translate utmp to a list of IP's, it is a fair amount or work. It may be easier within pppd though. > Likewise, pppd just shows up in ps as being "root" and "pppd"; you have to > look at the tty then run w to see who it is. I'm thinking of having pppd > modify it's arguments to show the user as argv[1], but I'm not sure how to > do that safely. Do you just change the argv[1] pointer value? man setproctitle(). If you do this, make it optional. Putting at least the username and IP address in there would be handy. 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@freefall.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-hackers Sat Dec 28 23:47:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA18311 for hackers-outgoing; Sat, 28 Dec 1996 23:47:41 -0800 (PST) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id XAA18306 for ; Sat, 28 Dec 1996 23:47:38 -0800 (PST) Received: by agora.rdrop.com (Smail3.1.29.1 #17) id m0veFxz-0008uHC; Sat, 28 Dec 96 23:47 PST Message-Id: From: batie@agora.rdrop.com (Alan Batie) Subject: Re: pppd & utmp To: danny@panda.hilink.com.au (Daniel O'Callaghan) Date: Sat, 28 Dec 1996 23:47:31 -0800 (PST) Cc: hackers@freebsd.org In-Reply-To: from "Daniel O'Callaghan" at Dec 29, 96 06:42:54 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 > This is already done, if you use the pppd in -current. Uses a host of > ":PPP". OK; I hadn't seen any comments about pppd so I didn't think to update that one. I'll do so and compare it. > This would be really neat. Please do as Mike Smith suggests and read > setproctitle(3), and then implement it. Yes, setproctitle does solve that problem nicely... The things they add when you aren't looking... -- Alan Batie ______ batie@agora.rdrop.com \ / Assimilate this! +1 503 452-0960 \ / --Worf, First Contact DE 3C 29 17 C0 49 7A 27 \/ 40 A5 3C 37 4A DA 52 B9 It is my policy to avoid purchase of any products from companies which use unrequested email advertisements or telephone solicitation.