From owner-freebsd-hackers Sun Jun 15 05:21:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA07749 for hackers-outgoing; Sun, 15 Jun 1997 05:21:21 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA07744 for ; Sun, 15 Jun 1997 05:21:18 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA11893 (5.67b/IDA-1.5 for FreeBSD-hackers@freebsd.org); Sun, 15 Jun 1997 14:21:47 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id OAA00995; Sun, 15 Jun 1997 14:14:46 +0200 (MET DST) From: Wilko Bulte Message-Id: <199706151214.OAA00995@yedi.iaf.nl> Subject: ISDN troubles: it now works To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list), rene@freeze.iaf.nl (Rene 'Freeze' de Vries) Date: Sun, 15 Jun 1997 14:14:46 +0200 (MET DST) 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 Hello We've finally gotten ISDN/PPP to work. There were multiple problems, including a typo in the kernel config file. But the best brain crusher was the fact that in isdnpppd the whole negotiation/setup stuff about local & remote IP addresses and the default route adding was commented out with #if 0's Which meant that after we finally got the dialling stuff working we saw a message telling us which addresses were assigned to local/remote ends of the connection. The ISP we have uses dynamic addresses. But isdnpppd never used these adresses to re-setup the link. Cute.. The stupid thing is that all options related to handling dynamic adress setup are accepted like in the 'normal' pppd. But are simply ignored. I really don't understand why this is done, because after changing the #if 0 into #if 1 the protocols worked OK. That is, you need also a small hack in the kernel: /* FALLTHROUGH */ case SIOCSIFFLAGS: x= splimp(); if(!(ifr->ifr_flags & IFF_UP)) { if(sc->sc_outstate != STATE_IDLE){ printf("bisdn: SIOCSIFFLAGS disco but fall thru\n"); #if wilko isdn_disconnect(sc->sc_appl, 0); #endif } sc->ipp_ppp_sc->sc_if.if_flags &= ~(IFF_UP|IFF_RUNNING); sc->ipp_ppp_sc->sc_npmode[NP_IP]=NPMODE_ERROR; } else { sc->ipp_ppp_sc->sc_if.if_flags |= (IFF_UP|IFF_RUNNING); sc->ipp_ppp_sc->sc_npmode[NP_IP]=NPMODE_PASS; } splx(x); break; It looks like that if you want to use the address negotiation you need to patch the above in /sys/bisdn/b_isdnipp.c If you don't the connection is broken ('disco') on every attempt to dial. Dial is ok, and then during the re-setup with the assigned addresses (I guess..) the connection is dropped. Since I'm not an expert on this stuff I appreciate knowledgable insight/ comments on why the #if 0 are there and why patch to the ioctl is needed. Thanks to all the kind people who either helped or offered help to get things working (Peter, Gary, Wolfgang, Marc). Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-hackers Sun Jun 15 05:38:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA08451 for hackers-outgoing; Sun, 15 Jun 1997 05:38:54 -0700 (PDT) Received: from piggy.mdstud.chalmers.se (root@piggy.mdstud.chalmers.se [129.16.234.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA08436 for ; Sun, 15 Jun 1997 05:38:36 -0700 (PDT) Received: from hallgren.se (ip181124.student.gu.se [130.241.181.124]) by piggy.mdstud.chalmers.se (8.8.5/8.7.3) with SMTP id OAA12566; Sun, 15 Jun 1997 14:37:08 +0200 (MET DST) Message-ID: <33A3E123.41C67EA6@mdstud.chalmers.se> Date: Sun, 15 Jun 1997 14:33:39 +0200 From: Tommy Hallgren Organization: FreeBSD X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2.1-RELEASE i386) MIME-Version: 1.0 To: "Serge A. Babkin" CC: hackers@freebsd.org Subject: Re: C optimizer bug ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Serge! Sometimes when you turn on optimizations, the compiler decides to cache some data into registers. Loops like while(!flag) {} will be mov eax, flag label: tst eax branch label  instead of label: mov eax, flag tst eax branch label Use the keyword "volatile" to force the loading the contents every time. Maybe this could be your problem? Mvh: Tommy(md6tommy@mdstud.chalmers.se) From owner-freebsd-hackers Sun Jun 15 06:10:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA09389 for hackers-outgoing; Sun, 15 Jun 1997 06:10:44 -0700 (PDT) Received: from florence.pavilion.net (mailrelay1.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA09378; Sun, 15 Jun 1997 06:10:36 -0700 (PDT) Received: (from joe@localhost) by florence.pavilion.net (8.8.5/8.8.5) id OAA24046; Sun, 15 Jun 1997 14:09:35 +0100 (BST) Message-ID: <19970615140935.59168@pavilion.net> Date: Sun, 15 Jun 1997 14:09:35 +0100 From: Josef Karthauser To: questions@freebsd.org Cc: hackers@freebsd.org Subject: help, running out of processes. :( Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Can someone please help me? We've got a web machine thta is running out of processes to the extent the it can't spawn CGI scripts anymore. This started happening when I upgraded from 2.1.7.1 to 2.2.2. The web server runs under the a non-priv user called webboss. We usually unlimit the number of processes and openfiles in a startup script that unlimits the shell before firing up 'httpd' (apache). I've created a class called 'web' in /etc/login.conf with limits of 1000 processes and 2000 files (we've got a USERS 128 in the kernel). I've attached this class to the 'webboss' user in the passwd file. We're still getting 'out of processes' errors for this user though. When this last happened a 'ps -aux | grep ^webboss | wc' showed 150 processes running for webboss, and I couldn't 'su -m weboss' from root. Does anybody know how login.conf works? It's not clear to me from the manual whether it's values act globally, or only for users that have logged in? What can I do to fix this problem. It's causing us major problems at the moment. Joe p.s. the passwd(5) man page still shows that the class field is unused. This isn't the case anymore is it? -- Josef Karthauser Technical Manager Email: joe@pavilion.net Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] From owner-freebsd-hackers Sun Jun 15 08:02:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA12783 for hackers-outgoing; Sun, 15 Jun 1997 08:02:25 -0700 (PDT) Received: from bagpuss.visint.co.uk (bagpuss.visint.co.uk [194.207.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA12778 for ; Sun, 15 Jun 1997 08:02:15 -0700 (PDT) Received: from dylan.visint.co.uk (dylan.visint.co.uk [194.207.134.180]) by bagpuss.visint.co.uk (8.7.5/8.7.3) with SMTP id QAA07754; Sun, 15 Jun 1997 16:02:00 +0100 (BST) Date: Sun, 15 Jun 1997 16:02:00 +0100 (BST) From: Stephen Roome To: Wolfgang Helbig cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Strange things afoot In-Reply-To: <199706131803.UAA10160@helbig.informatik.ba-stuttgart.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 Fri, 13 Jun 1997, Wolfgang Helbig wrote: > Hi, > > So I then go into that directory and do a make depend. After I've then > > installed all the extra bits of code it needs which mkbisdntree didn't put > > Which `extra bits of code' are you refering to? The only files that are > needed for compilation and are not installed by mkbisdntree are > /usr/sys.bisdn/i386/include/bisdn_ioctl.h > and > /usr/sys.bisdn/i386/include/bisdn_isdn.h Yup, those (and I'm not sure, but I think there were some other bisdn_*.h files as well?) but also running one of the patches completely messed up /usr/src/sys/ufs/ffs/ffs_extern.h. That's the really odd bit, because I can't find any ffs_extern references in any of the files... I think the drive might be dead, so I've found an identical machine and I'm using that now, hopefully this one will work. I'll have to wait and see. > > Instead these files are copied to /usr/include/machine which in turn is a > symbolic link to /sys/i386/include once you did a ``make world'' on your > machine. I'll leave it to do a make world on the old box, but only once I have a backup of everything. I expect it's just these cheap IDE drives that's causing this. > This is interesting, because ``make world'' is considered to be a very > good hardware tester, and your problems might be hardware caused. So if > you have about 250 Mbyte left on your /usr partition give it a try and > see what happens. I'm going to wipe the disk from the BIOS and see if that finds any errors. After that I'll leave it looping make clean and world. (to a typescript!) I'll probably also try putting a reboot in at the end of rc.local and then leaving it starting up and shutting down for a few hours =), it'll give fsck a chance and it should give it a bit of a workout =) Many Thanks for the help. Steve Roome. From owner-freebsd-hackers Sun Jun 15 08:48:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA14586 for hackers-outgoing; Sun, 15 Jun 1997 08:48:50 -0700 (PDT) Received: from helbig.informatik.ba-stuttgart.de (helbig.informatik.ba-stuttgart.de [141.31.166.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA14581 for ; Sun, 15 Jun 1997 08:48:46 -0700 (PDT) Received: (from helbig@localhost) by helbig.informatik.ba-stuttgart.de (8.8.5/8.8.5) id RAA29785; Sun, 15 Jun 1997 17:48:41 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199706151548.RAA29785@helbig.informatik.ba-stuttgart.de> Subject: Re: ISDN troubles: it now works In-Reply-To: <199706151214.OAA00995@yedi.iaf.nl> from Wilko Bulte at "Jun 15, 97 02:14:46 pm" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Sun, 15 Jun 1997 17:48:40 +0200 (MET DST) Cc: FreeBSD-hackers@FreeBSD.ORG, rene@freeze.iaf.nl X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hello > > We've finally gotten ISDN/PPP to work. There were multiple problems, > including a typo in the kernel config file. > > But the best brain crusher was the fact that in isdnpppd the whole > negotiation/setup stuff about local & remote IP addresses and the default > route adding was commented out with #if 0's > > Which meant that after we finally got the dialling stuff working we > saw a message telling us which addresses were assigned to local/remote > ends of the connection. The ISP we have uses dynamic addresses. > But isdnpppd never used these adresses to re-setup the link. Cute.. > The stupid thing is that all options related to handling dynamic > adress setup are accepted like in the 'normal' pppd. But are simply > ignored. > > I really don't understand why this is done, because after changing the > #if 0 into #if 1 the protocols worked OK. That is, you need also a > small hack in the kernel: > > /* FALLTHROUGH */ > > case SIOCSIFFLAGS: > x= splimp(); > if(!(ifr->ifr_flags & IFF_UP)) { > if(sc->sc_outstate != STATE_IDLE){ > printf("bisdn: SIOCSIFFLAGS disco but fall > thru\n"); > #if wilko > isdn_disconnect(sc->sc_appl, 0); > #endif > } > sc->ipp_ppp_sc->sc_if.if_flags &= ~(IFF_UP|IFF_RUNNING); > sc->ipp_ppp_sc->sc_npmode[NP_IP]=NPMODE_ERROR; > } else { > sc->ipp_ppp_sc->sc_if.if_flags |= (IFF_UP|IFF_RUNNING); > sc->ipp_ppp_sc->sc_npmode[NP_IP]=NPMODE_PASS; > } > splx(x); > break; > > It looks like that if you want to use the address negotiation you need > to patch the above in /sys/bisdn/b_isdnipp.c If you don't the connection > is broken ('disco') on every attempt to dial. Dial is ok, and then > during the re-setup with the assigned addresses (I guess..) the connection > is dropped. > > Since I'm not an expert on this stuff I appreciate knowledgable insight/ > comments on why the #if 0 are there and why patch to the ioctl is needed. Probably because the original patchers never believed that isdnpppd would stay around that long. It was really meant to be a quick fix to enable ppp functions in bisdn (for NetBSD). Since Dec 1st 1996 we happily received the first success message about a working isdnpppd connection from Andrew Gordon. Soon after that we had the dynamic addressing stuff working by reenabling the ifdef'ed code and applying a patch similar to the one above. On the ftp.muc.ditec.de server there are two tarballs--bisdntest and bisdntest-2. They contain all kernel files and diffs to ease bisdn(ppp) kernel modification in a -current environment. They include among others the patch above. And a cute shell script from Andreas Klemm to automate the kernel patches. AFAIK bisdntest works well for FreeBSD 2.2.1 and bisdntest-2 is o.k for FreeBSD 2.2.2. (You'll have to copy bisdn-ioctl.h and bisdn-isdn.h to /sys/i386/include before starting mkbisdnkernel on systems where there is no symlink from /usr/include/machine to /sys/i386/include) Some changes to bisdntest-2 where necessary to make it work on -current. Those changes do not add any functionality to the code, they only reflect modifications in some kernel interfaces. So I hesitate to put a bisdntest-3 on the bisdn ftp server. Glad to hear that bisdn works for you with PPP and dynamic IP adresses! Wolfgang From owner-freebsd-hackers Sun Jun 15 09:29:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA16198 for hackers-outgoing; Sun, 15 Jun 1997 09:29:47 -0700 (PDT) Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA16193 for ; Sun, 15 Jun 1997 09:29:45 -0700 (PDT) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by pahtoh.cwu.edu (8.8.5/8.8.5) with ESMTP id JAA02991; Sun, 15 Jun 1997 09:29:42 -0700 (PDT) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.5/8.8.5) with SMTP id JAA13612; Sun, 15 Jun 1997 09:29:42 -0700 (PDT) Date: Sun, 15 Jun 1997 09:29:42 -0700 (PDT) From: Chris Timmons To: "Serge A. Babkin" cc: hackers@FreeBSD.ORG Subject: Re: C optimizer bug ? In-Reply-To: <199706142204.EAA24900@hq.icb.chel.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hmmm, deja vu all over again? See the post below from Garrett; I also found a post from Thomas David Rivers who mentioned the possibility that automatic variables could have static extent when the code is compiled without optimization. TDR suggested that perhaps the questionable code was saving the address of an auto and then trying to dereference it later. Works fine until you compile with optimization and the variable is actually constructed/destructed as control flows in and out of the block in which it is defined (i.e. local extent.) caveat: I do not know exactly how gcc behaves in this regard; it just seemed like the two threads might be concerned with the same phenomenon. -Chris (from the archives...) Date: Tue, 11 Feb 1997 15:22:52 -0500 From: Garrett Wollman To: guhl@mitre.org (George Uhl) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG Subject: Fix to Interrupt/Terminate Signal causes page fault in kernel mode < I posted the following to freebsd-hackers and freebsd-bugs a couple > of days ago. I have fixed the problem, not by making any code > changes, but by compiling the kernel unoptimized! Your code is almost certainly broken. It probably has automatic variable initialization problems. -GAWollman From owner-freebsd-hackers Sun Jun 15 10:03:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA17472 for hackers-outgoing; Sun, 15 Jun 1997 10:03:36 -0700 (PDT) Received: from helbig.informatik.ba-stuttgart.de (helbig.informatik.ba-stuttgart.de [141.31.166.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA17467 for ; Sun, 15 Jun 1997 10:03:30 -0700 (PDT) Received: (from helbig@localhost) by helbig.informatik.ba-stuttgart.de (8.8.5/8.8.5) id TAA00605; Sun, 15 Jun 1997 19:03:29 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199706151703.TAA00605@helbig.informatik.ba-stuttgart.de> Subject: Re: Strange things afoot In-Reply-To: from Stephen Roome at "Jun 15, 97 04:02:00 pm" To: steve@visint.co.uk (Stephen Roome) Date: Sun, 15 Jun 1997 19:03:29 +0200 (MET DST) Cc: helbig@MX.BA-Stuttgart.De, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > > good hardware tester, and your problems might be hardware caused. So if > > you have about 250 Mbyte left on your /usr partition give it a try and > > see what happens. > > I'm going to wipe the disk from the BIOS and see if that finds any errors. > After that I'll leave it looping make clean and world. (to a typescript!) > > I'll probably also try putting a reboot in at the end of rc.local and then > leaving it starting up and shutting down for a few hours =), it'll give > fsck a chance and it should give it a bit of a workout =) How about changing the flags to fsck in /etc/rc? from `fsck -p' to `fsck -p -f'. That makes fsck check the filesystems even if they are `clean', i. e. the clean flag is set. > > Many Thanks for the help. You are welcome! Wolfgang > > Steve Roome. > > > From owner-freebsd-hackers Sun Jun 15 11:48:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA20667 for hackers-outgoing; Sun, 15 Jun 1997 11:48:52 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA20662 for ; Sun, 15 Jun 1997 11:48:50 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA16658; Sun, 15 Jun 1997 11:39:16 -0700 From: Terry Lambert Message-Id: <199706151839.LAA16658@phaeton.artisoft.com> Subject: Re: C optimizer bug ? To: babkin@hq.icb.chel.su (Serge A. Babkin) Date: Sun, 15 Jun 1997 11:39:15 -0700 (MST) Cc: jkh@time.cdrom.com, hackers@FreeBSD.ORG In-Reply-To: <199706150136.HAA07646@hq.icb.chel.su> from "Serge A. Babkin" at Jun 15, 97 07:36:45 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 > Okay, here is the description: The function scsi_done() must check > whether xs->bp is zero and then depending on it call biodone() Declare this variable volitile. You are probably suffering from overambitious ANSI register optimization, where the value being tested is loaded into a register and never reloaded (there's actually no excuse for this, given that the compiler can determine loop scoping and see from that whether or not the optimization would fail). Sun's ANSI C and othes have similar problems. Probably the success depends upon whether the value is initially zero or not. 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 Sun Jun 15 11:52:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA20811 for hackers-outgoing; Sun, 15 Jun 1997 11:52:30 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA20804 for ; Sun, 15 Jun 1997 11:52:28 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA16670; Sun, 15 Jun 1997 11:41:11 -0700 From: Terry Lambert Message-Id: <199706151841.LAA16670@phaeton.artisoft.com> Subject: Re: C optimizer bug ? To: babkin@hq.icb.chel.su (Serge A. Babkin) Date: Sun, 15 Jun 1997 11:41:11 -0700 (MST) Cc: jkh@time.cdrom.com, hackers@FreeBSD.ORG In-Reply-To: <199706150207.IAA22124@hq.icb.chel.su> from "Serge A. Babkin" at Jun 15, 97 08:07:46 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 > There is at least one useful point: should the optimizer be used for > kernel ? Indeed I got the first bad experience with optimizers > when I wrote my first driver for SCO. Now I know why SCO > does not use optimizer for kernel :-) Guessing: because SCO's programmers have similar problems with ANSI C permitted register promotion semantics and out of scope test variable modifications? 8-) 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sun Jun 15 11:59:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA20975 for hackers-outgoing; Sun, 15 Jun 1997 11:59:10 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA20967; Sun, 15 Jun 1997 11:59:08 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA16701; Sun, 15 Jun 1997 11:50:57 -0700 From: Terry Lambert Message-Id: <199706151850.LAA16701@phaeton.artisoft.com> Subject: Re: help, running out of processes. :( To: joe@pavilion.net (Josef Karthauser) Date: Sun, 15 Jun 1997 11:50:57 -0700 (MST) Cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <19970615140935.59168@pavilion.net> from "Josef Karthauser" at Jun 15, 97 02:09:35 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Can someone please help me? We've got a web machine thta is running out > of processes to the extent the it can't spawn CGI scripts anymore. This > started happening when I upgraded from 2.1.7.1 to 2.2.2. > > The web server runs under the a non-priv user called webboss. We usually > unlimit the number of processes and openfiles in a startup script that > unlimits the shell before firing up 'httpd' (apache). > > I've created a class called 'web' in /etc/login.conf with limits of 1000 > processes and 2000 files (we've got a USERS 128 in the kernel). I've attached > this class to the 'webboss' user in the passwd file. We're still getting > 'out of processes' errors for this user though. When this last happened > a 'ps -aux | grep ^webboss | wc' showed 150 processes running for webboss, > and I couldn't 'su -m weboss' from root. > > Does anybody know how login.conf works? It's not clear to me from the > manual whether it's values act globally, or only for users that have logged > in? login.conf only operates agains users whose credentials were generated through a login process (quotas are assigned at the time credentials are, when using login.conf). > What can I do to fix this problem. It's causing us major problems at > the moment. Most likely, you want to sysctl up "maxprocperuid", followed by "maxproc" in a process before forking the process that forks the server. This is (effectively) what login.conf does when you login. 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 Sun Jun 15 14:22:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA26720 for hackers-outgoing; Sun, 15 Jun 1997 14:22:30 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA26713 for ; Sun, 15 Jun 1997 14:22:28 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA32004 (5.67b/IDA-1.5 for FreeBSD-hackers@FreeBSD.ORG); Sun, 15 Jun 1997 23:22:18 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id UAA04038; Sun, 15 Jun 1997 20:53:22 +0200 (MET DST) From: Wilko Bulte Message-Id: <199706151853.UAA04038@yedi.iaf.nl> Subject: Re: ISDN troubles: it now works To: helbig@MX.BA-Stuttgart.De (Wolfgang Helbig) Date: Sun, 15 Jun 1997 20:53:22 +0200 (MET DST) Cc: FreeBSD-hackers@FreeBSD.ORG, rene@freeze.iaf.nl In-Reply-To: <199706151548.RAA29785@helbig.informatik.ba-stuttgart.de> from "Wolfgang Helbig" at Jun 15, 97 05:48:40 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Wolfgang Helbig wrote... [del] > > It looks like that if you want to use the address negotiation you need > > to patch the above in /sys/bisdn/b_isdnipp.c If you don't the connection > > is broken ('disco') on every attempt to dial. Dial is ok, and then > > during the re-setup with the assigned addresses (I guess..) the connection > > is dropped. > > > > Since I'm not an expert on this stuff I appreciate knowledgable insight/ > > comments on why the #if 0 are there and why patch to the ioctl is needed. > > Probably because the original patchers never believed that isdnpppd > would stay around that long. It was really meant to be a quick fix > to enable ppp functions in bisdn (for NetBSD). Since Dec 1st 1996 > we happily received the first success message about a working > isdnpppd connection from Andrew Gordon. Soon after that we had the > dynamic addressing stuff working by reenabling the ifdef'ed code > and applying a patch similar to the one above. Right. It seems we re-invented the same wheel here :) > On the ftp.muc.ditec.de server there are two tarballs--bisdntest > and bisdntest-2. They contain all kernel files and diffs to ease > bisdn(ppp) kernel modification in a -current environment. They Our system does not run -current, it is intended as a workhorse doing web proxying and firewalling for a small network of 6 Suns and 6 PCs. > AFAIK bisdntest works well for FreeBSD 2.2.1 and bisdntest-2 is o.k > for FreeBSD 2.2.2. (You'll have to copy bisdn-ioctl.h and Well, I think I'll stick to what I have now, there were already people anxiously awaiting for the return of the Internet link. > Glad to hear that bisdn works for you with PPP and dynamic IP adresses! Thanks. (stupid question: will this whole ISDN/ppp thing be really integrated into -current one time? So that it ends up on a release cd sometime? As noted, I'm not an expert on this stuff so I don't feel qualified to do it myself) Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-hackers Sun Jun 15 14:40:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA27375 for hackers-outgoing; Sun, 15 Jun 1997 14:40:32 -0700 (PDT) Received: from bagpuss.visint.co.uk (bagpuss.visint.co.uk [194.207.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA27368 for ; Sun, 15 Jun 1997 14:40:25 -0700 (PDT) Received: from dylan.visint.co.uk (dylan.visint.co.uk [194.207.134.180]) by bagpuss.visint.co.uk (8.7.5/8.7.3) with SMTP id WAA12203; Sun, 15 Jun 1997 22:39:48 +0100 (BST) Date: Sun, 15 Jun 1997 22:39:48 +0100 (BST) From: Stephen Roome To: Brian Somers cc: freebsd-hackers@FreeBSD.ORG Subject: Re: /var/run/natd.pid request In-Reply-To: <199706121954.UAA05858@awfulhak.demon.co.uk> 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, 12 Jun 1997, Brian Somers wrote: > > > Everything then talks fine both on the firewall machine, and from my work > > > machine across the room, for 0-3 minutes. After that, the logging on the > > > console slows to a halt, and if I try to: > A "hack" has fixed the panic in 2.2 and -current for the moment. I'm > looking at figuring out a proper fix now. I'm suffering from the same problem here, (although we get everything to route fine for usually up to about 30 seconds until it freezes up.) but we don't actually get panics, just a complete freeze. However, we're in dire need of a working version of natd here. (We're using natd 1.4, installed as one of the standard 2.2.2-RELEASE ports, with bisdn-0.97 and a Teles S0/16.3) > For the moment, you could try using ppp rather than pppd/natd. Wait > 'till natd is part of /usr/src :) (It's not going to work with isdn =( ) Anyway I need this for Monday morning (2 hours time =)), I'll try to download a newer version and pop it on, but if you can send me or point me in the right direction for the patch/hack to stop natd freezing up then I would be a happy bunny :) (Also, I if you're using isdn to connect an internal network to demon.co.uk using this setup then if there is any chance of a copy of your configuration files then please (grovel) can I have a copy - to be sure bisdn is actually set up fine as well - although I just typed this mail message over it...) Many Thanks, Steve Roome - Vision Interactive Ltd. T:(home) +44 (0) 976 241 342 / (work) +44 (0) 117 973 0597 From owner-freebsd-hackers Sun Jun 15 19:19:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA09958 for hackers-outgoing; Sun, 15 Jun 1997 19:19:03 -0700 (PDT) Received: from cyber2.servtech.com (root@cyber2.servtech.com [199.1.22.12]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA09953 for ; Sun, 15 Jun 1997 19:18:58 -0700 (PDT) Received: from nest.pr-comm.com (osprey.pr-comm.com [207.41.67.240]) by cyber2.servtech.com (8.8.5/8.8.5) with ESMTP id WAA22465; Sun, 15 Jun 1997 22:18:39 -0400 (EDT) Received: (from housley@localhost) by nest.pr-comm.com (8.8.5/8.7.3) id WAA00361; Sun, 15 Jun 1997 22:18:34 -0400 (EDT) From: "James E. Housley" Message-Id: <199706160218.WAA00361@nest.pr-comm.com> Subject: User PPP problems sometime after 2.2.0 To: hackers-digest@freebsd.org Date: Sun, 15 Jun 1997 22:18:32 -0400 (EDT) Cc: housley@pr-comm.com X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have been tracking 2.2-STABLE via CVSup and it has been a while since I compiled the updates. I did a make world and now I am haveing problems with user PPP. If I do 'ppp osprey' and then 'term' and manually dial and log in everything is fine. However, if I do 'ppp osprey' and then 'dial'. The modem dials and connects and then hangs up. I have have a log file showing both sequences, but it is very large. I turned on ALL set log entries. In the second sequence I get a Disconnected! very early in the link setup. This is a big problem. My cron jobs to get my mail don't work if the link can't be setup automaticaly. I will post all information that is helpful. Please tell me the most useful log settings and if I should edit out things such as the "time" sequences. Thanks, Jim From owner-freebsd-hackers Sun Jun 15 21:04:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA13919 for hackers-outgoing; Sun, 15 Jun 1997 21:04:35 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA13914 for ; Sun, 15 Jun 1997 21:04:33 -0700 (PDT) Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id VAA06625 for ; Sun, 15 Jun 1997 21:03:17 -0700 (PDT) Received: (babkin@localhost) by hq.icb.chel.su (8.8.3/8.6.5) id JAA24558; Mon, 16 Jun 1997 09:30:12 +0600 (ESD) From: "Serge A. Babkin" Message-Id: <199706160330.JAA24558@hq.icb.chel.su> Subject: Re: C optimizer bug ? To: terry@lambert.org (Terry Lambert) Date: Mon, 16 Jun 1997 09:30:11 +0600 (ESD) Cc: jkh@time.cdrom.com, hackers@FreeBSD.ORG In-Reply-To: <199706151839.LAA16658@phaeton.artisoft.com> from "Terry Lambert" at Jun 15, 97 11:39:15 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > Okay, here is the description: The function scsi_done() must check > > whether xs->bp is zero and then depending on it call biodone() > > Declare this variable volitile. You are probably suffering from > overambitious ANSI register optimization, where the value being > tested is loaded into a register and never reloaded (there's > actually no excuse for this, given that the compiler can determine > loop scoping and see from that whether or not the optimization > would fail). Sun's ANSI C and othes have similar problems. > > Probably the success depends upon whether the value is initially > zero or not. xs->bp does not change during the operation, it is initialized before calling the SCSI code. I tried to compile the kernel with -C -fvolatile that must declare all values accessed by pointers as volatile but this given no positive effect. I tried -fvolatile-global flag too but the kernel refuses to compile with it at all. The GCC version is 2.6.3. I'm going to study the produced code. -SB From owner-freebsd-hackers Sun Jun 15 23:21:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA17546 for hackers-outgoing; Sun, 15 Jun 1997 23:21:26 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA17527; Sun, 15 Jun 1997 23:21:21 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wdV80-0002XC-00; Sun, 15 Jun 1997 23:19:00 -0700 Date: Sun, 15 Jun 1997 23:18:59 -0700 (PDT) From: Tom Samplonius To: Terry Lambert cc: Josef Karthauser , questions@freebsd.org, hackers@freebsd.org Subject: Re: help, running out of processes. :( In-Reply-To: <199706151850.LAA16701@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 15 Jun 1997, Terry Lambert wrote: > > Can someone please help me? We've got a web machine thta is running out > > of processes to the extent the it can't spawn CGI scripts anymore. This > > started happening when I upgraded from 2.1.7.1 to 2.2.2. > > > > The web server runs under the a non-priv user called webboss. We usually > > unlimit the number of processes and openfiles in a startup script that > > unlimits the shell before firing up 'httpd' (apache). > > > > I've created a class called 'web' in /etc/login.conf with limits of 1000 > > processes and 2000 files (we've got a USERS 128 in the kernel). I've attached > > this class to the 'webboss' user in the passwd file. We're still getting > > 'out of processes' errors for this user though. When this last happened > > a 'ps -aux | grep ^webboss | wc' showed 150 processes running for webboss, > > and I couldn't 'su -m weboss' from root. > > > > Does anybody know how login.conf works? It's not clear to me from the > > manual whether it's values act globally, or only for users that have logged > > in? > > login.conf only operates agains users whose credentials were generated > through a login process (quotas are assigned at the time credentials > are, when using login.conf). Yes, a big problem for processes that leave root after binding to a privileged port. But shouldn't such processes should call setrlimit() appropriately first? ... > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > Tom From owner-freebsd-hackers Mon Jun 16 02:29:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA24594 for hackers-outgoing; Mon, 16 Jun 1997 02:29:38 -0700 (PDT) Received: from unique.usn.blaze.net.au (unique.usn.blaze.net.au [203.17.53.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA24586 for ; Mon, 16 Jun 1997 02:29:31 -0700 (PDT) Received: from unique.usn.blaze.net.au (local [127.0.0.1]) by unique.usn.blaze.net.au (8.8.5/8.8.5) with ESMTP id TAA08450 for ; Mon, 16 Jun 1997 19:29:09 +1000 (EST) Message-Id: <199706160929.TAA08450@unique.usn.blaze.net.au> To: freebsd-hackers@freebsd.org Subject: bind and aliases X-Face: (W@z~5kg?"+5?!2kHP)+l369.~a@oTl^8l87|/s8"EH?Uk~P#N+Ec~Z&@;'LL!;3?y Date: Mon, 16 Jun 1997 19:29:07 +1000 From: David Nugent Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm attempting to set up a server and seem to have a problem. I can't get the (UDP based) server running when binding to a specific address, but it does work just fine when binding to any. The executable is a BSD binary (actually, this is Id's unixded, the dedicated quake server). It has a command line option to bind to a specific address so that you can run multiple servers on the same machine using the default udp port. ktrace shows the following: 4703 unixded CALL socket(0x2,0x2,0x11) Aka, socket(PF_INET, SOCK_DGRAM, 16) [hmm, no protocol 16 defined in /etc/protocols...] 4703 unixded RET socket 6 4703 unixded CALL ioctl(0x6,FIONBIO,0xefbfd73c) 4703 unixded RET ioctl 0 4703 unixded CALL write(0x1,0x961000,0x31) 4703 unixded GIO fd 1 wrote 49 bytes "Binding to IP Interface Address of 203.17.53.241 " 4703 unixded RET write 49/0x31 Call to bind follows:- 4703 unixded CALL bind(0x6,0xefbfd740,0x10) 4703 unixded RET bind -1 errno 49 Can't assign requested address 4703 unixded CALL close(0x6) 4703 unixded RET close 0 4703 unixded CALL write(0x2,0xefbfd080,0x28) 4703 unixded GIO fd 2 wrote 40 bytes "UDP_Init: Unable to open control socket " But bind(2) failes with errno 49, which suggests that there's no interface with this address. However, even the default ip address on the ed0 interface won't work here. This is its ifconfig: ed0: flags=8843 mtu 1500 inet 203.17.53.17 netmask 0xfffffff0 broadcast 203.17.53.31 inet 203.17.53.241 netmask 0xffffffff broadcast 203.17.53.241 inet 203.17.53.242 netmask 0xffffffff broadcast 203.17.53.242 inet 203.17.53.243 netmask 0xffffffff broadcast 203.17.53.243 ether 00:00:c0:d5:a5:10 Anyone have any ideas? I first tried this under -current as of May 14th or thereabouts, but just updated to yesterday's -current and the result is the same. What's worse is that I know this works ok for tcp sockets since I've recently been using bind(2) on specific addresses in code I'm working on. Regards, David From owner-freebsd-hackers Mon Jun 16 02:30:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA24696 for hackers-outgoing; Mon, 16 Jun 1997 02:30:44 -0700 (PDT) Received: from prova.iet.unipi.it (prova1.iet.unipi.it [131.114.9.11]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA24561; Mon, 16 Jun 1997 02:28:30 -0700 (PDT) Received: (from luigi@localhost) by prova.iet.unipi.it (8.8.5/8.8.5) id LAA00577; Mon, 16 Jun 1997 11:27:25 +0200 (CEST) From: Luigi Rizzo Message-Id: <199706160927.LAA00577@prova.iet.unipi.it> Subject: rr queueing To: luigi@prova.iet.unipi.it (Luigi Rizzo) Date: Mon, 16 Jun 1997 11:27:25 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL31 (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 am sending this mail because you might be interested in the subject. You are on the Bcc list so you will not be bothered by replies from other recipients]. I have some preliminary code for implementing RR queueing and associated stuff (including bw allocation) in the bottom layers of the networking stack. When complete (although it pretty much works even now) it is meant to replace the IF_ENQUEUE/IF_DEQUEUE macros. As such, I have tried to make the code and the algorithms fast and efficient. The code includes some description on what it does and how, so if you have comments and suggestions on how to improve it or add more features, let me know. The code is at the following URL http://www.iet.unipi.it/~luigi/newifqueue.c in its current form, it compiles to a standalone program so as to check actual performance and be easily modifiable. 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 Jun 16 02:39:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA24996 for hackers-outgoing; Mon, 16 Jun 1997 02:39:07 -0700 (PDT) Received: from deathstar.ml.org (adrian@deathstar.ml.org [203.62.152.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA24969 for ; Mon, 16 Jun 1997 02:38:49 -0700 (PDT) Received: from localhost (adrian@localhost) by deathstar.ml.org (8.8.5/8.7.3) with SMTP id RAA00937 for ; Mon, 16 Jun 1997 17:40:38 +0800 Date: Mon, 16 Jun 1997 17:40:38 +0800 (WST) From: Adrian Chadd To: freebsd-hackers@freebsd.org Subject: IP tunnel between a FreeBSD box and a cisco. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi guys. Has anyone setup an IP tunnel between a FreeBSD box, and a cisco router (specifically the 4000-series router, running IOS 10.x (I don't know the exact version - its not mine :) ) ? Why? I want to do BGP between our gateway box running FreeBSD/gated, and a 4000.. but there is a 1003 in the way. Multi-hop BGP works fine, but since the 1003 doesn't know the routes itself, it blindly sends stuff to its default gateway (being some other router). Note 64k is for this link, and 64k is for another client (otherwise I would have just had the default route via the link I'm BGPing with :-) Diagram: 4000 ---64k-- ISDN --- [ 1003 ] -- ethernet -- [GATEWAY] | 64k (another client) and I want the 4000 and the gateway box to have a "tunnel" going which I can then do BGP over. Thanks, -- Adrian Chadd | "Unix doesn't stop you from doing | stupid things because that would | stop you from doing clever things" From owner-freebsd-hackers Mon Jun 16 04:30:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA29833 for hackers-outgoing; Mon, 16 Jun 1997 04:30:23 -0700 (PDT) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA29823 for ; Mon, 16 Jun 1997 04:30:19 -0700 (PDT) Message-Id: <199706161130.EAA29823@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA268110131; Mon, 16 Jun 1997 21:22:11 +1000 From: Darren Reed Subject: Re: rr queueing To: luigi@iet.unipi.it (Luigi Rizzo) Date: Mon, 16 Jun 1997 21:22:10 +1000 (EST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199706160927.LAA00577@prova.iet.unipi.it> from "Luigi Rizzo" at Jun 16, 97 11:27:25 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 Luigi Rizzo, sie said: > > I have some preliminary code for implementing RR queueing and > associated stuff (including bw allocation) in the bottom layers of > the networking stack. When complete (although it pretty much works > even now) it is meant to replace the IF_ENQUEUE/IF_DEQUEUE macros. > As such, I have tried to make the code and the algorithms fast and > efficient. The code includes some description on what it does and > how, so if you have comments and suggestions on how to improve it > or add more features, let me know. Did I miss something or... Is it faster than IF_ENQUEUE/IF_DEQUEUE ? Does it fix some mysterious problem/bug that currently exists ? Darren From owner-freebsd-hackers Mon Jun 16 06:46:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA05796 for hackers-outgoing; Mon, 16 Jun 1997 06:46:23 -0700 (PDT) Received: from mbunix.mitre.org (mbunix.mitre.org [129.83.20.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA05785 for ; Mon, 16 Jun 1997 06:46:13 -0700 (PDT) Received: from FUZZY (fuzzy.mitre.org [128.29.154.17]) by mbunix.mitre.org (8.8.5/8.8.5/mitre.0) with SMTP id JAA23936; Mon, 16 Jun 1997 09:43:27 -0400 (EDT) Date: Mon, 16 Jun 1997 09:43:27 -0400 (EDT) Received: from m15081-mac.mitre.org (128.29.114.90) by fuzzy.mitre.org with SMTP id 34029; Mon, 16 Jun 1997 09:43:26 EST X-Sender: guhl@mail90.mitre.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: babkin@hq.icb.chel.su From: guhl@mitre.org (George Uhl) Subject: Re: C optimizer bug ? cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Indeed, it was a bug in the code. >Hmmm, deja vu all over again? See the post below from Garrett; I also >found a post from Thomas David Rivers who mentioned the possibility that >automatic variables could have static extent when the code is compiled >without optimization. TDR suggested that perhaps the questionable code >was saving the address of an auto and then trying to dereference it later. >Works fine until you compile with optimization and the variable is >actually constructed/destructed as control flows in and out of the block >in which it is defined (i.e. local extent.) > Actually, it was a pointer problem. Not that the pointer referenced a bad address, but rather I used the back pointer of a linked list instead of the forward pointer. The back pointer is actually a double pointer which ultimately references the same address that the previous element's forward pointer references (that is, the current element). See the LIST macros in sys/queue.h for specifics. I can't remember why I used the back pointer in the first place, but I was just beginning to change the FreeBSD kernel to support the OSI (sigh) and X.25 protocol processing we use in our lab and I just didn't know what I was doing at the time. The strange thing about this bug, was that the code "appeared" to work when the code was unoptimized. With more exhaustive testing the bug should have manifested itself in other ways. The difficult task was isolating the bug because the part of the kernel that was crashing did not pinpoint the bug's location. I found it where I didn't expect it to be. When the obvious fails only the unobvious remains! >caveat: I do not know exactly how gcc behaves in this regard; it just >seemed like the two threads might be concerned with the same phenomenon. > >-Chris > You might want to examine your code again. >(from the archives...) > >Date: Tue, 11 Feb 1997 15:22:52 -0500 >From: Garrett Wollman >To: guhl@mitre.org (George Uhl) >Cc: freebsd-hackers@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG >Sender: owner-hackers@FreeBSD.ORG >Subject: Fix to Interrupt/Terminate Signal causes page fault in kernel >mode > >< >> I posted the following to freebsd-hackers and freebsd-bugs a couple >> of days ago. I have fixed the problem, not by making any code >> changes, but by compiling the kernel unoptimized! > >Your code is almost certainly broken. It probably has automatic >variable initialization problems. > >-GAWollman George Uhl email: phone: 703-883-7305 The MITRE Corporation 1820 Dolley Madison Blvd. McLean, VA. 22102 From owner-freebsd-hackers Mon Jun 16 06:50:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA06044 for hackers-outgoing; Mon, 16 Jun 1997 06:50:57 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id GAA06032 for ; Mon, 16 Jun 1997 06:50:52 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA07204; Mon, 16 Jun 1997 09:50:11 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 16 Jun 1997 09:50 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id OAA23833; Sun, 15 Jun 1997 14:48:01 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id OAA10921; Sun, 15 Jun 1997 14:56:04 -0400 (EDT) Date: Sun, 15 Jun 1997 14:56:04 -0400 (EDT) From: Thomas David Rivers Message-Id: <199706151856.OAA10921@lakes.water.net> To: ponds!hq.icb.chel.su!babkin, ponds!time.cdrom.com!jkh Subject: Re: C optimizer bug ? Cc: ponds!FreeBSD.ORG!hackers Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > > > I tried everything and finally decided to build the kernel > > > without the optimization. Everything started working fine! > > > So the C optimizer seems like having a bug. > > > > Without trying to reduce this down to something others can actually > > reproduce, however, this basically goes into the same category as > > UFO sightings and alien abductions. There's strong evidence that > > it _might_ happen, but with no concrete proof we can only continue > > to speculate as to whether or not they're real. :-) > > Okay, here is the description: The function scsi_done() must check > whether xs->bp is zero and then depending on it call biodone() > or wakeup(xs). Sometimes it confuses these cases and does the > wrong thing, in this case the process hangs on tsleep(...,"scsicmd") > or waiting for biodone() (I can't remember the argument of > tsleep() for biodone exactly). The probability of hangup on missing > wakeup(xs) is about 1/4. The hangups on missing biodone() are > rare. > > In case of any delays caused by printf() or tcpdump or > using a loopback Ethernet card simulator > the SCSI simulator is able to finish the operation before the > scsi_scsi_cmd() function gets control back from the SCSI > card driver and in this case it just does not sleep. The hangups > on missing biodone() still occur even with delays. > > I don't know how to reproduce this bug without all those > simulators but I think it should be possible. Hey!!! This sounds an awful lot like my "daily panic" problem - when I put printf()s around scsi_done, etc... the problem goes away. [Although, my problem isn't limited to SCSI...] Since I've demonstrated this with older and newer versions of FreeBSD, which used at least two different GCC compilers - I tend to think it's not a compiler problem... I'll bet you'll discover something else is trashing some memory. Likely overwriting memory that's in a different location when you don't optimize. That also why adding printf()s "helps" the problem; as the printf()s change the size of the stack... - Dave Rivers - > > -SB > From owner-freebsd-hackers Mon Jun 16 08:19:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA10696 for hackers-outgoing; Mon, 16 Jun 1997 08:19:25 -0700 (PDT) Received: from wafu.netgate.net (wafu.netgate.net [204.145.147.80]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA10689 for ; Mon, 16 Jun 1997 08:19:11 -0700 (PDT) Received: from chiota.signet.or.jp (INS30.tama.dtinet.or.jp [203.181.77.30]) by wafu.netgate.net (8.7.5/8.7.3) with ESMTP id HAA10719; Mon, 16 Jun 1997 07:22:46 GMT Message-Id: <199706160722.HAA10719@wafu.netgate.net> Received: from chiota.signet.or.jp (localhost.signet.or.jp [127.0.0.1]) by chiota.signet.or.jp (8.8.5/) with ESMTP id AAA00481; Tue, 17 Jun 1997 00:19:42 +0900 (JST) To: freebsd-hackers@FreeBSD.ORG Cc: shigio@wafu.netgate.net Subject: an inconvenience about macro [/usr/src/sys/sys/kernel.h] Date: Tue, 17 Jun 1997 00:19:42 +0900 From: Shigio Yamaguchi Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello hackers. I found an inconvenience in kernel source. (It is not a bug.) What do you think? --------------------------------------------------------------------------- Inconvenience about Macro --------------------------------------------------------------------------- In /usr/src/sys/kern/init_main.c, SYSINIT macro is used. It is like this. [/usr/src/sys/kern/init_main.c] SYSINIT(placeholder, SI_SUB_DUMMY,SI_ORDER_ANY, NULL, NULL) SYSINIT doesn't end with ';', because the definition already has it. [/usr/src/sys/sys/kern.h] #define SYSINIT(uniquifier, subsystem, order, func, ident) \ static struct sysinit uniquifier ## _sys_init = { \ subsystem, \ order, \ func, \ ident, \ SI_TYPE_DEFAULT \ }; \ DATA_SET(sysinit_set,uniquifier ## _sys_init); ^ | END WITH ';' But ctags(1) cannot treat this pattern. For example, in these code [/usr/src/sys/kern/init_main.c] SYSINIT(placeholder, SI_SUB_DUMMY,SI_ORDER_ANY, NULL, NULL) ... (a) ..... void main(framep) ... (b) void *framep; { ..... } ... (c) Ctags(1) assumes SYSINIT start at (a) and end at (c). As the result that main() functin is skipped. I think the definition of SYSINIT should not end with ';' and the referenced point should end with ';' like this. SYSINIT(placeholder, SI_SUB_DUMMY,SI_ORDER_ANY, NULL, NULL); By the way, in the same source file(/usr/src/sys/sys/kern.h), MAKE_SET's code is good. [/usr/src/sys/sys/kern.h] #define MAKE_SET(set, sym, type) \ static void const * const __set_##set##_sym_##sym = &sym; \ asm(".stabs \"_" #set "\", " #type ", 0, 0, _" #sym) In this macro, the first statement ends with ';' and the second (=last) statement doesn't end with ';'. It should be so. -- Shigio Yamaguchi (Freelance programmer) Mail: shigio@wafu.netgate.net, WWW: http://wafu.netgate.net/tama/ From owner-freebsd-hackers Mon Jun 16 11:05:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA19828 for hackers-outgoing; Mon, 16 Jun 1997 11:05:19 -0700 (PDT) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA19807 for ; Mon, 16 Jun 1997 11:05:08 -0700 (PDT) Received: from ct.picker.com by whqvax.picker.com with SMTP; Mon, 16 Jun 1997 14:04:05 -0400 (EDT) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA03016; Mon, 16 Jun 97 14:04:03 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id OAA14055; Mon, 16 Jun 1997 14:02:38 -0400 Message-Id: <19970616140238.32473@ct.picker.com> Date: Mon, 16 Jun 1997 14:02:38 -0400 From: Randall Hopper To: Elizabeth Ann Martin Cc: hackers@FreeBSD.ORG Subject: Re: hfs + msdos + ZIP 2.2.1-R References: <199706121932.OAA00421@ascc.artsci.wustl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <199706121932.OAA00421@ascc.artsci.wustl.edu>; from Elizabeth Ann Martin on Thu, Jun 12, 1997 at 02:32:17PM -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Elizabeth Ann Martin: |I am under the impression that the (Macintosh) hfs port + msdos LINT enable |+ SCSI Iomega ZIP (100 Mb) drive will allow me to mount either hfs- or |msdos- formatted ZIP disks on my 2.2.1-RELEASE system. | |Is this correct? Can't speak to HFS. But for MS-DOS, you're correct. I occasionally do this, though normally I'll just put a UFS on a ZIP disk for my FreeBSD storage. Randall From owner-freebsd-hackers Mon Jun 16 11:07:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA19943 for hackers-outgoing; Mon, 16 Jun 1997 11:07:00 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA19936 for ; Mon, 16 Jun 1997 11:06:57 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.5/8.7.3) with SMTP id LAA28997 for ; Mon, 16 Jun 1997 11:06:54 -0700 (PDT) Date: Mon, 16 Jun 1997 11:06:51 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: Black-hole FS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A FS where every stat() fails, every open/mkdir succeeds, and all writes dump all the data, and all reads return nothing would be really cool. And if it could be unionized on top of an NFS mounted partition, even cooler. Might be a good first project for hacking. From owner-freebsd-hackers Mon Jun 16 12:25:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA24636 for hackers-outgoing; Mon, 16 Jun 1997 12:25:46 -0700 (PDT) Received: from train.tgci.com (train.tgci.com [205.185.169.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA24627 for ; Mon, 16 Jun 1997 12:25:42 -0700 (PDT) Received: from emilyd ([206.250.85.68]) by train.tgci.com (8.6.12/8.6.9) with SMTP id MAA11250 for ; Mon, 16 Jun 1997 12:25:31 -0700 Message-Id: <199706161925.MAA11250@train.tgci.com> Comments: Authenticated sender is From: "Riley J. McIntire" To: hackers@FreeBSD.ORG Date: Mon, 16 Jun 1997 12:25:30 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: (Fwd) Re: Serious potential IMAP problem Reply-to: chaos@tgci.com Priority: normal X-mailer: Pegasus Mail for Win32 (v2.42a) Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Normally I just lurk on the hackers list, but at the risk of being flamed, thought this might generate some interest here as a possible enhancement to FreeBSD. As an impetus to this, this incomplete quote goes on to offer NT as an example of a "good operating system" in this aspect of security. Riley ------- Forwarded Message Follows ------- Date: Mon, 16 Jun 1997 10:39:31 -0700 (PDT) From: Chris Newman Subject: Re: Serious potential IMAP problem To: Mark Crispin Cc: info-cyrus@andrew.cmu.edu On Mon, 16 Jun 1997, Mark Crispin wrote: > Unfortunately, the cretins who designed UNIX thought that it would be alright > for applications to do login via the setuid() call after the application > validates the password. This, in turn, requires root to do the setuid() and > perhaps also to access the password. > > In good operating systems, there is a non-root state which equates to being > "not logged in"; it issue an unprivileged system call to log in with > authentication credentials in the call. The kernel validates the > authentication credentials and sets the process's user id on success. I concur with this analysis. Any Unix vendors out there planning on fixing this? I don't think it should be too hard to add a magic user which can setuid() to anyone but root, but has no other root privileges. > I am considering a further breakup of the UW server into two programs, one of > which is "not logged in" and the other of which is "logged in"; the idea is to > make the security-critical portion of the UW server be a very small program > that can be subject to verification techniques. I am not sure breaking them into separate programs is a good idea due to the buffer flushing problem that plagues sendmail. But having a single .c file with all the critical code separated sounds useful. > simplifying assumptions to be made. The bad news in Cyrus is that any crack > of Cyrus' security is effectively a full crack of the entire mail store; the > kernel won't/can't stop it. I encountered this problem when I was trying to figure out how to hook up a Cyrus mailstore to the PMDF MTA/backbone that Innosoft sells. PMDF has a much stricter security model then sendmail, so there's no simple way to hook the stock Cyrus "deliver" program up to PMDF due to the Cyrus privileges it requires. I had to create a "deliver" replacement. I'm not familiar with the sendmail glue to deliver, but I sure hope it either doesn't use system() to run deliver, or strips any shell meta characters after the "+" in a subaddress. > So, there are tradeoffs either way; neither is "more secure" than the other, > just "different" in how they approach the problem. Well they certainly have different security risks. UW has a small "root" window, while Cyrus has a larger "cyrus" window. Which is deemed "more secure" depends on the security policy of the site. From owner-freebsd-hackers Mon Jun 16 13:20:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA28012 for hackers-outgoing; Mon, 16 Jun 1997 13:20:35 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA28007; Mon, 16 Jun 1997 13:20:32 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA18033; Mon, 16 Jun 1997 13:10:57 -0700 From: Terry Lambert Message-Id: <199706162010.NAA18033@phaeton.artisoft.com> Subject: Re: help, running out of processes. :( To: tom@sdf.com (Tom Samplonius) Date: Mon, 16 Jun 1997 13:10:56 -0700 (MST) Cc: terry@lambert.org, joe@pavilion.net, questions@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: from "Tom Samplonius" at Jun 15, 97 11:18:59 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > login.conf only operates agains users whose credentials were generated > > through a login process (quotas are assigned at the time credentials > > are, when using login.conf). > > Yes, a big problem for processes that leave root after binding to a > privileged port. > > But shouldn't such processes should call setrlimit() appropriately > first? Good question; but it begs the question "what is a credential?". I suspect it's unreasonable to have processes started in the rc.conf file calling setrlimit() as a required action. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jun 16 13:29:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA28717 for hackers-outgoing; Mon, 16 Jun 1997 13:29:26 -0700 (PDT) Received: from phoenix.its.rpi.edu (dec@phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA28712 for ; Mon, 16 Jun 1997 13:29:21 -0700 (PDT) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.5/8.8.5) with SMTP id QAA23531 for ; Mon, 16 Jun 1997 16:30:56 -0400 (EDT) Date: Mon, 16 Jun 1997 16:30:55 -0400 (EDT) From: "David E. Cross" To: hackers@freebsd.org Subject: better version of HFS utilities for 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 I found a GPL version of an HFS package (hfsutils) that supports many more options than our current hfs package. It seems to be fairly reliable, information can be found at: http://www.mars.org/home/rob/proj/hfs -- David Cross ACS Consultant From owner-freebsd-hackers Mon Jun 16 14:25:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA02513 for hackers-outgoing; Mon, 16 Jun 1997 14:25:32 -0700 (PDT) Received: from ice.cold.org (cold.org [206.81.134.103]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA02505 for ; Mon, 16 Jun 1997 14:25:22 -0700 (PDT) Received: from localhost (brandon@localhost) by ice.cold.org (8.8.5/8.8.5) with SMTP id PAA01089; Mon, 16 Jun 1997 15:25:18 -0600 (MDT) Date: Mon, 16 Jun 1997 15:25:17 -0600 (MDT) From: Brandon Gillespie To: "Brian N. Handy" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: waiting for response from send-pr? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 12 Jun 1997, Brian N. Handy wrote: > On Thu, 12 Jun 1997, Brandon Gillespie wrote: > So the send-pr worked, it just hasn't [yet] grabbed the attention of > anyone important. Maybe it's time for you to walk the corridors of > power... How so? From owner-freebsd-hackers Mon Jun 16 14:39:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA03309 for hackers-outgoing; Mon, 16 Jun 1997 14:39:01 -0700 (PDT) Received: from friley01.res.iastate.edu (friley01.res.iastate.edu [129.186.189.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA03290 for ; Mon, 16 Jun 1997 14:38:42 -0700 (PDT) Received: (from ccsanady@localhost) by friley01.res.iastate.edu (8.8.5/8.8.5) id QAA03561 for hackers@freebsd.org; Mon, 16 Jun 1997 16:38:35 -0500 (CDT) Date: Mon, 16 Jun 1997 16:38:35 -0500 (CDT) From: Chris Csanady Message-Id: <199706162138.QAA03561@friley01.res.iastate.edu> To: hackers@freebsd.org Subject: Distributed shared memory? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Could someone please point me at whatever is available now? Thanks, Chris Csanady From owner-freebsd-hackers Mon Jun 16 15:48:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA07237 for hackers-outgoing; Mon, 16 Jun 1997 15:48:45 -0700 (PDT) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA07207 for ; Mon, 16 Jun 1997 15:48:13 -0700 (PDT) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id SAA20569; Mon, 16 Jun 1997 18:46:59 -0400 Date: Mon, 16 Jun 1997 18:46:58 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: Chris Csanady cc: hackers@FreeBSD.ORG Subject: Re: Distributed shared memory? In-Reply-To: <199706162138.QAA03561@friley01.res.iastate.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Jun 1997, Chris Csanady wrote: > Could someone please point me at whatever is available > now? I had mnfs for freebsd 2.05R, but gave up trying to track freebsd and get the needed fixes into the VM for it. But it worked and was used by several groups. ftp://ftp.sarnoff.com/pub/mnfs/freebsd/ for sources etc. www.sarnoff.com:8000 for papers, follow the metacomputing tree. also try zounds. www.sarnoff.com:8000, go down the metacomputing tree. we've used zounds for 4 applications here, all very different. Needs no kernel mods. ron From owner-freebsd-hackers Mon Jun 16 17:13:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA10376 for hackers-outgoing; Mon, 16 Jun 1997 17:13:47 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA10371 for ; Mon, 16 Jun 1997 17:13:44 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id JAA13328; Tue, 17 Jun 1997 09:43:25 +0930 (CST) From: Michael Smith Message-Id: <199706170013.JAA13328@genesis.atrad.adelaide.edu.au> Subject: Re: (Fwd) Re: Serious potential IMAP problem In-Reply-To: <199706161925.MAA11250@train.tgci.com> from "Riley J. McIntire" at "Jun 16, 97 12:25:30 pm" To: chaos@tgci.com Date: Tue, 17 Jun 1997 09:43:25 +0930 (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 Riley J. McIntire stands accused of saying: > > On Mon, 16 Jun 1997, Mark Crispin wrote: > > Unfortunately, the cretins who designed UNIX thought that it would be alright > > for applications to do login via the setuid() call after the application > > validates the password. This, in turn, requires root to do the setuid() and > > perhaps also to access the password. Oh, it's our dear little pal Mark Crispin. He's such a charmer, don't you think? > > In good operating systems, there is a non-root state which equates to being > > "not logged in"; it issue an unprivileged system call to log in with > > authentication credentials in the call. The kernel validates the > > authentication credentials and sets the process's user id on success. This in turn requires the kernel have the mechanism to access the credential store, which may equate to bundling every possible password access mechanism with the kernel; yeah, let's suck in all the Kerberos stuff, NIS, Radius, S/Key, ssh, Tacacs, SecurID, the Captain Midnight Secret Decoder Wheel algorithm, and so on. You'll note that there's no actual attempt to justify why authentication by root and subsequent sacrifice of priveledge is actually _bad_. > I concur with this analysis. Any Unix vendors out there planning on > fixing this? I don't think it should be too hard to add a magic user > which can setuid() to anyone but root, but has no other root privileges. This is stupid; with "no other priveledges", the "not-logged-in" user will not be able to access the local password store, and possibly not be able to make network transactions required to access remote password stores. > I am not sure breaking them into separate programs is a good idea due to > the buffer flushing problem that plagues sendmail. But having a single .c > file with all the critical code separated sounds useful. Alternatively, consider using the PAM framework, which is compact, open to analysis, and once analysed, every program that uses it is much simpler to analyse in itself. If PAM interests you, see the references off my homepage (http://www.smith.net.au/~mike). -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jun 16 17:58:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA12309 for hackers-outgoing; Mon, 16 Jun 1997 17:58:30 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA12297; Mon, 16 Jun 1997 17:58:19 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wdmYu-0002tH-00; Mon, 16 Jun 1997 17:55:56 -0700 Date: Mon, 16 Jun 1997 17:55:56 -0700 (PDT) From: Tom Samplonius To: Simon Shapiro cc: FreeBSD-hackers@freebsd.org, FreeBSD-SCSI@freebsd.org, "Justin T. Gibbs" Subject: Re: Announcement: New DPT RAID Controller Driver Available In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 13 Jun 1997, Simon Shapiro wrote: ... > The driver supports the PM3334{U,W,D} which is a PCI controller > sporting a 68030 processor, up to 3 SCSI ultra-wide-differential > busses. It is also available (I think) as narrow, non-ultra and > definitely single-ended. www.dpt.com says this controller has a 40mhz 68040 ?? ... > I would like you to help me in posting an announcement on the proper > FreeBSD lists and in checking it in. Anyone volunteered for the check-in yet? Has a FreeBSD 2.2.2-RELEASE boot disk been made with the DPT driver? I'm looking at a RAID solution for a freebsd server I'm building. Reliability is important (previous server had an uptime of 209 days before a flaky disk forced a reboot!). Basically, either I use the DPT controller, or a Mylex SCSI-to-SCSI controller connected to a standard PCI controller. The Mylex solution is kinda slow, but since it simply appears as a really big disk connected to your SCSI bus, it is almost guarrenteeed to work with FreeBSD. Anyone else using any kinda of RAID solution with freebsd now? Tom From owner-freebsd-hackers Mon Jun 16 18:20:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA13749 for hackers-outgoing; Mon, 16 Jun 1997 18:20:09 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA13677; Mon, 16 Jun 1997 18:19:55 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id TAA15968; Mon, 16 Jun 1997 19:19:42 -0600 (MDT) Message-Id: <199706170119.TAA15968@pluto.plutotech.com> To: Tom Samplonius cc: Simon Shapiro , FreeBSD-hackers@FreeBSD.ORG, FreeBSD-SCSI@FreeBSD.ORG, "Justin T. Gibbs" Subject: Re: Announcement: New DPT RAID Controller Driver Available In-reply-to: Your message of "Mon, 16 Jun 1997 17:55:56 PDT." Date: Mon, 16 Jun 1997 20:18:40 -0600 From: "Justin T. Gibbs" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Anyone volunteered for the check-in yet? Has a FreeBSD 2.2.2-RELEASE >boot disk been made with the DPT driver? I will be doing the final review and checkin into current and the 2.2 branch. As for a boot floppy, I'm sure that the releng22.FreeBSD.org will be able to accomodate you once the code is checked into the tree. >Tom -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hackers Mon Jun 16 18:21:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA13938 for hackers-outgoing; Mon, 16 Jun 1997 18:21:49 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA13862 for ; Mon, 16 Jun 1997 18:20:41 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AB29308; Mon, 16 Jun 1997 21:20:07 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 16 Jun 1997 21:20 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id UAA17013; Mon, 16 Jun 1997 20:49:27 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id UAA13928; Mon, 16 Jun 1997 20:57:32 -0400 (EDT) Date: Mon, 16 Jun 1997 20:57:32 -0400 (EDT) From: Thomas David Rivers Message-Id: <199706170057.UAA13928@lakes.water.net> To: ponds!FreeBSD.ORG!jmb, ponds!mep.ruhr-uni-bochum.de!roberte Subject: Re: REQ: FreeBSD in our life Cc: ponds!hub.freebsd.org!hackers Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > i did a presentation at europen.se in oct 1996 > and anonther in research triangle park in may 1997 > i can send you my sldies in tex format > will that help? > Hey!! Not to directly respond to this; but just as a note to Jonathan and anyone else. If you ever find yourself in the Research Triangle Park area; just let me know!!! I can show you around! - Dave Rivers - > i can slow tell you baout hub.freebsd.org, our mail server > > jmb > -- > Jonathan M. Bresler FreeBSD Core Team, 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 > > > Robert Eckardt wrote: > > > > Hello, > > > > next week I'm going to give a talk on FreeBSD in the UNIX SysAdms group > > at the computer center here in Bochum. > > (history, features, applications, own experience) > > > > I would like to collect some information on "real-life" boxes that > > handle some traffic (mail, www, ...) (besides ftp.cdrom.com :-). > > (Like a mail server with some (ten-)thousand mails/day) > > > date: Thu Jun 5 17:24:09 PDT 1997 > mailstats: > Statistics from Sat May 31 03:39:40 1997 > M msgsfr bytes_from msgsto bytes_to Mailer > 0 0 0K 8380 17225K prog > 1 0 0K 5014 13163K *file* > 3 35744 119220K 16307 55662K local > 6 7979 25186K 137329 304160K smtp8 > 7 0 0K 2 3K relay > ======================================== > T 43723 144406K 167032 390213K > > we average from 8 to 14 addresses per email sent > > > Also I'm interested in "not-so-standard" applications with FreeBSD. > > > > Finally, I'would like to hear about some architectural features of > > FreeBSD (also in comparison to other OSes), preferrably with some > > references (and understandable for a non-OS-designer like me :-). > From owner-freebsd-hackers Mon Jun 16 18:27:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA14374 for hackers-outgoing; Mon, 16 Jun 1997 18:27:18 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA14366 for ; Mon, 16 Jun 1997 18:27:15 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id KAA13608; Tue, 17 Jun 1997 10:55:31 +0930 (CST) From: Michael Smith Message-Id: <199706170125.KAA13608@genesis.atrad.adelaide.edu.au> Subject: Re: REQ: help from Emacs/XEmacs/Jove/Jed/... users In-Reply-To: from Chuck Robey at "Jun 14, 97 02:47:14 pm" To: chuckr@glue.umd.edu (Chuck Robey) Date: Tue, 17 Jun 1997 10:55:30 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, narvi@haldjas.folklore.ee, jkh@time.cdrom.com, token@wicx50.informatik.uni-wuerzburg.de, 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 Chuck Robey stands accused of saying: > > Bad news: pilot adds almost no extra functions, so removing pilot doesn't > gain us anything. libpico.so.1.3 still about 160K. Booger. Is there lots of fluff in the library? I find it hard to swallow that a "simple" text editor bulks 160K... > Chuck Robey | Interests include any kind of voice or data -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jun 16 19:16:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA16948 for hackers-outgoing; Mon, 16 Jun 1997 19:16:19 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA16940 for ; Mon, 16 Jun 1997 19:16:15 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id WAA02422; Mon, 16 Jun 1997 22:16:02 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id WAA03717; Mon, 16 Jun 1997 22:16:00 -0400 Date: Mon, 16 Jun 1997 22:15:45 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Michael Smith cc: narvi@haldjas.folklore.ee, jkh@time.cdrom.com, token@wicx50.informatik.uni-wuerzburg.de, freebsd-hackers@FreeBSD.ORG Subject: Re: REQ: help from Emacs/XEmacs/Jove/Jed/... users In-Reply-To: <199706170125.KAA13608@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 17 Jun 1997, Michael Smith wrote: > Chuck Robey stands accused of saying: > > > > Bad news: pilot adds almost no extra functions, so removing pilot doesn't > > gain us anything. libpico.so.1.3 still about 160K. > > Booger. Is there lots of fluff in the library? I find it hard to swallow > that a "simple" text editor bulks 160K... I thought about that, Mike. Yes, I could trim some stuff, like the file selector functionality could be limited, but then I realized that it would mean just about no chance, ever, of being able to fold in any updates from newer pine releases. Would that be acceptable? What I mean by that is that there would be major differences between the stock pico code and what I left in. If I really used a knife on it, I could slim it down. It'd STILL be better than ee (from a newuser standpoint), just about as portable as a lead anvil. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Mon Jun 16 19:16:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA16974 for hackers-outgoing; Mon, 16 Jun 1997 19:16:33 -0700 (PDT) Received: from pandora.hh.kew.com (root@kendra.ne.highway1.com [24.128.53.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA16968 for ; Mon, 16 Jun 1997 19:16:31 -0700 (PDT) Received: from fantasy-factory.net.kew.com (uucp@fantasy-factory.net.kew.com [204.96.41.103]) by pandora.hh.kew.com (8.8.5/8.8.5) with ESMTP id WAA03027; Mon, 16 Jun 1997 22:15:07 -0400 (EDT) Received: from kew-sonata.UUCP (uucp@localhost) by fantasy-factory.net.kew.com (8.8.5/8.8.5) with UUCP id WAA05987; Mon, 16 Jun 1997 22:15:05 -0400 (EDT) Received: by sonata.uucp.kew.com (UUPC/extended 1.12s); Mon, 16 Jun 1997 22:14:53 -0500 Message-ID: <33a5f31d.kew-sonata@sonata.uucp.kew.com> Date: Mon, 16 Jun 1997 22:14:48 -0500 From: "Drew Derbyshire" Organization: Kendra Electronic Wonderworks (PO Box 80144, Stoneham MA 02180) To: "Michael Smith" Cc: hackers@freebsd.org Subject: Re: (Fwd) Re: Serious potential IMAP problem Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 17 Jun 1997 09:43:25 +0930 (CST), "Michael Smith" wrote: > Oh, it's our dear little pal Mark Crispin. He's such a charmer, don't > you think? Suffice to say I did not find this comment charming. > > > In good operating systems, there is a non-root state which equates to being > > > "not logged in"; it issue an unprivileged system call to log in with > > > authentication credentials in the call. The kernel validates the > > > authentication credentials and sets the process's user id on success. > > This in turn requires the kernel have the mechanism to access the > credential store, which may equate to bundling every possible password > access mechanism with the kernel; yeah, let's suck in all the Kerberos > stuff, NIS, Radius, S/Key, ssh, Tacacs, SecurID, the Captain Midnight > Secret Decoder Wheel algorithm, and so on. This is not correct. For example, FreeBSD file systems need not be compiled into the kernel to be a system call. Likewise, IBM VM/ESA both use external file systems and external security packages with well defined API's which are routed through the kernel but run as started (daemon) tasks, which would have the required access. Likewise, numerous systems allow processes acting as "nobody" to execute commands (login, date, time, in some cases message) which in the case of a command allow the priv level to be upgraded. > You'll note that there's no actual attempt to justify why > authentication by root and subsequent sacrifice of priveledge is > actually _bad_. This is fairly clear to me -- one never wants to grant more access than is needed, because if excessive access is never gained, it cannot be abused by programming error or attack before being surrendered. It also discourages the practice for every setuid program to have direct access to the sensitive security database. > Alternatively, consider using the PAM framework, which is compact, > open to analysis, and once analysed, every program that uses it is > much simpler to analyse in itself. If PAM interests you, see the > references off my homepage (http://www.smith.net.au/~mike). As shared library(s), it still appears to encourage granting root to a program as trivial a POP3 server which only needs normal user access. This temporary root access is, to me, inherently more dangerous than taking a program from no access to the specific user id without a stop at the higher priv level. -ahd- -- Internet: ahd@kew.com Voice: 617-279-9810 "During emergency landing, replace dinner tray and bring seat to upright position. Extinguish all smoking materials . . . including the spacecraft, if possible." - Spaceman Spiff (aka Calvin) From owner-freebsd-hackers Mon Jun 16 19:18:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA17088 for hackers-outgoing; Mon, 16 Jun 1997 19:18:55 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA17078 for ; Mon, 16 Jun 1997 19:18:51 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id WAA02973; Mon, 16 Jun 1997 22:18:45 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id WAA03737; Mon, 16 Jun 1997 22:18:44 -0400 Date: Mon, 16 Jun 1997 22:18:29 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Chris Csanady cc: hackers@FreeBSD.ORG Subject: Re: Distributed shared memory? In-Reply-To: <199706162138.QAA03561@friley01.res.iastate.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Jun 1997, Chris Csanady wrote: > > Could someone please point me at whatever is available > now? Ron Minnich (I think sanoff.com, but I'm not sure( has got something of that order. I think it was called Zounds. > > Thanks, > Chris Csanady > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Mon Jun 16 19:47:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA18408 for hackers-outgoing; Mon, 16 Jun 1997 19:47:28 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA18401 for ; Mon, 16 Jun 1997 19:47:25 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA14052; Tue, 17 Jun 1997 12:16:16 +0930 (CST) From: Michael Smith Message-Id: <199706170246.MAA14052@genesis.atrad.adelaide.edu.au> Subject: Re: REQ: help from Emacs/XEmacs/Jove/Jed/... users In-Reply-To: from Chuck Robey at "Jun 16, 97 10:15:45 pm" To: chuckr@glue.umd.edu (Chuck Robey) Date: Tue, 17 Jun 1997 12:16:15 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, narvi@haldjas.folklore.ee, jkh@time.cdrom.com, token@wicx50.informatik.uni-wuerzburg.de, 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 Chuck Robey stands accused of saying: > > > > Booger. Is there lots of fluff in the library? I find it hard to swallow > > that a "simple" text editor bulks 160K... > > I thought about that, Mike. Yes, I could trim some stuff, like the file > selector functionality could be limited, but then I realized that it would > mean just about no chance, ever, of being able to fold in any updates from > newer pine releases. Would that be acceptable? I don't think so, no; it becomes another millstone that someone has to maintain. > What I mean by that is that there would be major differences between the > stock pico code and what I left in. If I really used a knife on it, I > could slim it down. It'd STILL be better than ee (from a newuser > standpoint), just about as portable as a lead anvil. Hmm, I meant more along the lines of "optional" functionality, eg. the ispell interface, etc. It sounds like the library is basically "this is what you get". *sigh* > Chuck Robey | Interests include any kind of voice or data -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jun 16 20:08:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA19385 for hackers-outgoing; Mon, 16 Jun 1997 20:08:05 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA19369 for ; Mon, 16 Jun 1997 20:07:52 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA14153; Tue, 17 Jun 1997 12:37:05 +0930 (CST) From: Michael Smith Message-Id: <199706170307.MAA14153@genesis.atrad.adelaide.edu.au> Subject: Re: (Fwd) Re: Serious potential IMAP problem In-Reply-To: <33a5f31d.kew-sonata@sonata.uucp.kew.com> from Drew Derbyshire at "Jun 16, 97 10:14:48 pm" To: ahd@kew.com (Drew Derbyshire) Date: Tue, 17 Jun 1997 12:37:05 +0930 (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 Drew Derbyshire stands accused of saying: > On Tue, 17 Jun 1997 09:43:25 +0930 (CST), "Michael Smith" wrote: > > Oh, it's our dear little pal Mark Crispin. He's such a charmer, don't > > you think? > > Suffice to say I did not find this comment charming. What? You think I should refrain from prompting the recall of previous context wrt. Mark C's opinions and behaviour? It's not like I'm accusing him of anything more than basic lack of couth. > > > > In good operating systems, there is a non-root state which equates to being > > > > "not logged in"; it issue an unprivileged system call to log in with > > > > authentication credentials in the call. The kernel validates the > > > > authentication credentials and sets the process's user id on success. > > > > This in turn requires the kernel have the mechanism to access the > > credential store, which may equate to bundling every possible password > > access mechanism with the kernel; yeah, let's suck in all the Kerberos > > stuff, NIS, Radius, S/Key, ssh, Tacacs, SecurID, the Captain Midnight > > Secret Decoder Wheel algorithm, and so on. > > This is not correct. For example, FreeBSD file systems need not be > compiled into the kernel to be a system call. Entirely apart from the syntactic nonsensicality of this statement, filesystem code must be present in the kernel image, whether placed there during the post-compile link, or subsequently via a modload operation. In either case, they occupy space in the kernel image. > Likewise, IBM VM/ESA both > use external file systems and external security packages with well > defined API's which are routed through the kernel but run as started > (daemon) tasks, which would have the required access. Aha, and now you have spread the potential security gap even wider; the realm of trust encompasses the "nobody" program, the kernel, the daemon and the communications channels between them. Now you have to special-case the handling of buffers used in these communications channels to prevent the possible leaking of credential data. I don't think this is a terribly good idea. Bill did some interesting work with process intercommunication and adding functionality that allows the processes on either end of an IPC channel to be assured of the identity of the process they are communicating with, and this could indeed be used for that sort of activity. > Likewise, numerous systems allow processes acting as "nobody" to execute > commands (login, date, time, in some cases message) which in the case of > a command allow the priv level to be upgraded. Huh? How can a "nobody" process have its privilege level upgraded by executing a command? It can potentially spawn a setuid command, but there is no advantage here at all. > > You'll note that there's no actual attempt to justify why > > authentication by root and subsequent sacrifice of priveledge is > > actually _bad_. > > This is fairly clear to me -- one never wants to grant more access than > is needed, because if excessive access is never gained, it cannot be > abused by programming error or attack before being surrendered. It also > discourages the practice for every setuid program to have direct access > to the sensitive security database. The alternative actually grants access to the "sensitive security database" to everyone. Either no privilege is required to communicate with the authentication server, which opens the system to dictionary and similar attacks, or communications with the authentication server are restricted to the "nobody" user, but normal users must be able to become the "nobody" user in order encompass transition from one user identity to another, which effectively opens the same hole. This is no worse, it's just no better, and more complicated to boot. > > Alternatively, consider using the PAM framework, which is compact, > > open to analysis, and once analysed, every program that uses it is > > much simpler to analyse in itself. If PAM interests you, see the > > references off my homepage (http://www.smith.net.au/~mike). > > As shared library(s), it still appears to encourage granting root to a > program as trivial a POP3 server which only needs normal user access. > This temporary root access is, to me, inherently more dangerous than > taking a program from no access to the specific user id without a stop > at the higher priv level. This is correct; it does not change the current model, simply makes analysing the risks presented by the model a more straightforward task. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jun 16 20:47:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA20471 for hackers-outgoing; Mon, 16 Jun 1997 20:47:37 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA20464 for ; Mon, 16 Jun 1997 20:47:34 -0700 (PDT) Received: (qmail 8999 invoked by uid 1000); 17 Jun 1997 03:47:41 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 16 Jun 1997 20:47:41 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Tom Samplonius Subject: Re: Announcement: New DPT RAID Controller Driver Available Cc: "Justin T. Gibbs" , FreeBSD-SCSI@FreeBSD.ORG, FreeBSD-hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Tom Samplonius; On 17-Jun-97 you wrote: > > On Fri, 13 Jun 1997, Simon Shapiro wrote: > > ... > > The driver supports the PM3334{U,W,D} which is a PCI controller > > sporting a 68030 processor, up to 3 SCSI ultra-wide-differential > > busses. It is also available (I think) as narrow, non-ultra and > > definitely single-ended. > > www.dpt.com says this controller has a 40mhz 68040 ?? I know it is an abomination to have a Motorola processor in a computer dominated by the holy Intel processor. But, in case you can stomach the idea for a while, it actually works well. Those of you who insist that their computer is maintained purely Intel will be glad to know that (as I am told), the next generation will have an i960 instead. > ... > > I would like you to help me in posting an announcement on the proper > > FreeBSD lists and in checking it in. > > Anyone volunteered for the check-in yet? Has a FreeBSD 2.2.2-RELEASE > boot disk been made with the DPT driver? Yes, Justin Gibbs. He has been very helpful and now even insists that the driver complies with the BSD coding standards. I am indenting and indenting... :-) > I'm looking at a RAID solution for a freebsd server I'm building. > Reliability is important (previous server had an uptime of 209 days > before > a flaky disk forced a reboot!). Basically, either I use the DPT > controller, or a Mylex SCSI-to-SCSI controller connected to a standard > PCI > controller. The Mylex solution is kinda slow, but since it simply > appears > as a really big disk connected to your SCSI bus, it is almost > guarrenteeed > to work with FreeBSD. The DPT controller is doing the same thing. Since 1982. I think you will find the support, the configuration utilities (in native mode!), the perfomance and the complete integration (You will get a beep, console output, syslog, SNMP event and a can of diet soda whacked on the head every time: a. Bus Glitch b. Fan failure in the disk enclosure c. Power supply failure d. Disk failure. If you have a spare disk plugged in, you will also get aotomatic re-build of the array. Oh, did iI mention all power supplies are redundant and all disks are hot pluggable without any software intervention? >From us (the Atlas team), you also get multi initiator support, performance monitoring, Distributed Lock Manager and Distributed I/O. ... The option for 200+ days between boots will only come later. Right now we are delivering 14 days between boots (the anticipated frequency of enhancements posted for the driver). Simon From owner-freebsd-hackers Mon Jun 16 20:56:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA20879 for hackers-outgoing; Mon, 16 Jun 1997 20:56:06 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA20874 for ; Mon, 16 Jun 1997 20:56:01 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id XAA17318; Mon, 16 Jun 1997 23:55:58 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id XAA07728; Mon, 16 Jun 1997 23:55:56 -0400 Date: Mon, 16 Jun 1997 23:55:39 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Chris Csanady cc: hackers@FreeBSD.ORG Subject: Re: Distributed shared memory? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Jun 1997, Chuck Robey wrote: > On Mon, 16 Jun 1997, Chris Csanady wrote: > > > > > Could someone please point me at whatever is available > > now? > > Ron Minnich (I think sanoff.com, but I'm not sure( has got something of > that order. I think it was called Zounds. Darn, that should have been sarnoff, not sanoff. Mr. TV. > > > > > Thanks, > > Chris Csanady > > > > > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@eng.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > (301) 220-2114 | version 3.0 current -- and great FUN! > ----------------------------+----------------------------------------------- > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Mon Jun 16 21:12:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA21451 for hackers-outgoing; Mon, 16 Jun 1997 21:12:18 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA21422; Mon, 16 Jun 1997 21:12:03 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wdpaP-0002yO-00; Mon, 16 Jun 1997 21:09:41 -0700 Date: Mon, 16 Jun 1997 21:09:41 -0700 (PDT) From: Tom Samplonius To: Simon Shapiro cc: "Justin T. Gibbs" , FreeBSD-SCSI@freebsd.org, FreeBSD-hackers@freebsd.org Subject: Re: Announcement: New DPT RAID Controller Driver Available In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Jun 1997, Simon Shapiro wrote: > Hi Tom Samplonius; On 17-Jun-97 you wrote: > > > > On Fri, 13 Jun 1997, Simon Shapiro wrote: > > > > ... > > > The driver supports the PM3334{U,W,D} which is a PCI controller > > > sporting a 68030 processor, up to 3 SCSI ultra-wide-differential > > > busses. It is also available (I think) as narrow, non-ultra and > > > definitely single-ended. > > > > www.dpt.com says this controller has a 40mhz 68040 ?? > > I know it is an abomination to have a Motorola processor in a computer > dominated by the holy Intel processor. But, in case you can stomach the > idea for a while, it actually works well. Nope, the point was making was that you say the board has a 68030, while www.dtp.com says it is a 68040. The 68040 has quite a bit more kick than a 68030. That's a good thing. The 68000 series was always a good line. Plenty of integrated devices use them. > Those of you who insist that their computer is maintained purely Intel will > be glad to know that (as I am told), the next generation will have an i960 > instead. The i960 is not necessarily better. Especially, not the gutless 20mhz version. DPT might be better off with the 68060, as long as the price is right. ... > find the support, the configuration utilities (in native mode!), the > perfomance and the complete integration (You will get a beep, console > output, syslog, SNMP event and a can of diet soda whacked on the head every > time: ... > b. Fan failure in the disk enclosure > c. Power supply failure How does this work? Do you need to buy DPT enclosures for this? I don't have a DPT enclosure :(, and it doesn't seem that DPT makes rack mount enclosures. > If you have a spare disk plugged in, you will also get aotomatic re-build > of the array. Oh, did iI mention all power supplies are redundant and all > disks are hot pluggable without any software intervention? Again these all sound like features in the hardware module? I just use standard hot-swap modules (Dataport VI). FreeBSD gets mighty confused when you pull a drive while it is running, but the modules are mighty handle for any kind of field replacement. Are power supplies a big deal these days? I've never had a good PS2 supply die, but have had 4 drives die, all in last three years. Tom From owner-freebsd-hackers Mon Jun 16 21:51:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA22950 for hackers-outgoing; Mon, 16 Jun 1997 21:51:17 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA22942 for ; Mon, 16 Jun 1997 21:51:11 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA25972; Tue, 17 Jun 1997 00:50:28 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 17 Jun 1997 00:50 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id VAA17129; Mon, 16 Jun 1997 21:02:57 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id VAA14051; Mon, 16 Jun 1997 21:11:02 -0400 (EDT) Date: Mon, 16 Jun 1997 21:11:02 -0400 (EDT) From: Thomas David Rivers Message-Id: <199706170111.VAA14051@lakes.water.net> To: ponds!FreeBSD.ORG!hackers, ponds!cdsnet.net!mrcpu Subject: Re: Hmph, just found a piece of $NEWLIB/history in the middle of , in.nnrpd. Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > Doesn't bode well for the reliability of our UFS/AHC, WRT recent reported > repeatable panics... > > If anybody wants to look at some coredumps, I have some kernel panics > (freeing free block), that it woul dbe easy to check out. > > > I'm probably sounding like a broken record at this point; but it sure does sound an awful lot like my "daily panics" problems.... I don't think it has much to do with the AHC (unless, this is a totally different problem.) - Dave Rivers - From owner-freebsd-hackers Mon Jun 16 22:43:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA24449 for hackers-outgoing; Mon, 16 Jun 1997 22:43:01 -0700 (PDT) Received: from argus.nuke.net (pm3-p39.tfs.net [206.154.183.231]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA24437 for ; Mon, 16 Jun 1997 22:42:52 -0700 (PDT) Received: (from jbryant@localhost) by argus.nuke.net (8.8.5/8.8.5) id AAA04506; Tue, 17 Jun 1997 00:42:29 -0500 (CDT) From: Jim Bryant Message-Id: <199706170542.AAA04506@argus.nuke.net> Subject: Re: Distributed shared memory? To: ccsanady@friley01.res.iastate.edu (Chris Csanady) Date: Tue, 17 Jun 1997 00:42:28 -0500 (CDT) Cc: freebsd-hackers@freebsd.org Reply-To: jbryant@tfs.net In-Reply-To: <199706162138.QAA03561@friley01.res.iastate.edu> from "Chris Csanady" at Jun 16, 97 04:38:35 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply: > Could someone please point me at whatever is available > now? are you thinking of some kind of mach-like concept? it might be more efficient to simply use an UDP... Jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" jbryant@tfs.net - KC5VDJ 2M, 70cm, KPC-3+ - kc5vdj@wv0t.#neks.ks.usa.noam From owner-freebsd-hackers Mon Jun 16 22:59:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA25006 for hackers-outgoing; Mon, 16 Jun 1997 22:59:53 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA24991 for ; Mon, 16 Jun 1997 22:59:48 -0700 (PDT) Received: (qmail 17470 invoked by uid 1000); 17 Jun 1997 05:59:42 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 16 Jun 1997 22:59:42 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Tom Samplonius Subject: Re: Announcement: New DPT RAID Controller Driver Available Cc: FreeBSD-hackers@FreeBSD.ORG, FreeBSD-SCSI@FreeBSD.ORG, "Justin T. Gibbs" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Tom Samplonius; On 17-Jun-97 you wrote: ... > Nope, the point was making was that you say the board has a 68030, > while > www.dtp.com says it is a 68040. The 68040 has quite a bit more kick than > a 68030. That's a good thing. This whole thing was atounge in cheek (foot in mouth?) and relates to some past employment experience... ... > The i960 is not necessarily better. Especially, not the gutless 20mhz > version. > > DPT might be better off with the 68060, as long as the price is right. Yes, but the logo on the chip is still wrong. Now take Mylex for example. Here is a quality, mature product that has the right high tech processor on board. Obviously the right choice. (Hint: Check out the Unholy union's benchmarks and performance braggings. Count how many DPT's are described and hoe many politically correct HBA's are listed. Now repeat once the i960 DPT's are out.) ... > How does this work? Do you need to buy DPT enclosures for this? You can. They are actually made by DEC Storage Works division. There is an upcoming SCSI standard for all this. The way it works is simple. They use several ``undefined/unused'' signals on the SCSI bus (cable) to transmit back and forth the necessary data. the DPT's simply comply with the DEC de-facto standard. We are using these enclosues in a HUGE project we are working on. It is amusing to pull a power supply, fan, disk or even a SCSI cable off while doing ls -alR or some nasty RDBMS access and listen to the siren, watch the red lights flash like mad and still have the disks operate as if nothing happened (well, a bit slower on RAID-5). > I don't have a DPT enclosure :(, and it doesn't seem that DPT makes > rack mount enclosures. Well, guess what? Call DPT, ask for Rene norton and tell her to sell you the same rack-mount she shipped me for evaluation. It is a rack mount that has 2 power supplies and 6 3.5" slots, or you can take a P/S out and put a 7th disk in. If you want, she can send you the proper terminator and instructions and then you can split the BUS into 2 busses. The only objection I hear here: a. The P/S are only available in A/C. We need -48VDC b. Both power and signal cables come off the front. this is great for service but our marketing people are complaining. We (Atlas Telecom, my employer) are building an AC-D/C version (using the DEC power supplies (3 in N+1), fans, SCSI backplane, etc. in our own box. It will have eight slots, be differential capable and allow bus daisy-chaining. It is done is cooperation with DPT and DEC so you should be able to enjoy the fruits of this effort. I have evaluated, tested and even participated in the design of more than one I/O subsystem in my short life. The StorageWorks solution is the best I have ever seen. not perfect, Just the BEST. Same goes for DPT. I have worked with them on several projects for over 15 years. Never dissapointed, except for minor things. ... > > disks are hot pluggable without any software intervention? > > Again these all sound like features in the hardware module? The hot-spare capability is a DPT feature. So it will work regardless of the disk cabinetry. Hot-plugging SCSI (especially single-ended is tricky. DPt helps out by allowing the use of 528 byte sectors. Coupled with ECC memory in the controller, they perform ECC across the SCSI bus. This cuts down (drastically) on the complaints at insert/removal. If your SCSI bus is not carefully done, you will still glitch it. I have tested some very reputable solutions and wit hthe exception of the StorageWorks, they all fail. The test is simple; Plug and unplug a drive once per minute and observe the system console. If you get tons of aborts (or the DPT beeps like mad and will not stop you have a bad disk bay. What happens is that either the power supply lines glitch and cause several drives to spin down (The DPT sees it as a multiple-drive fault and refuses to play the effected array), or it glitches some of the handshake signals and causes the bus to hang. The way DEC gets over that is with some fancy circuitry inside the disk module. the bus is totally passive (albeit interesting in design). > I just use standard hot-swap modules (Dataport VI). FreeBSD gets > mighty > confused when you pull a drive while it is running, but the modules are > mighty handle for any kind of field replacement. See above for possible causes. The DPT HBA handles all the recovery. You simply do not see any of it unless it gave up. If you WANT to address devices directly and eliminate the DPT handling (why?), there is a way to do it. The initial version of the FreeBSD driver does not support this ``feature''. > > Are power supplies a big deal these days? I've never had a good PS2 > supply die, but have had 4 drives die, all in last three years. Power supplies are funny business. We were having severe problems with a 250W PS/2 power supply handling insersions/removal of 4 drives in another disk bay. The StorageWorks does fine with one 150W P/S handling 8 drives. Has a lot to do with surge/spike/EMI handling on the OUTPUT side. Also, one may think that a $400 P/S may have some more design and quality put into it than a $35 one. Simon From owner-freebsd-hackers Tue Jun 17 00:27:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA29418 for hackers-outgoing; Tue, 17 Jun 1997 00:27:32 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA29410 for ; Tue, 17 Jun 1997 00:27:17 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA00455; Tue, 17 Jun 1997 09:25:57 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id KAA07034; Sun, 15 Jun 1997 10:31:02 +0200 (MET DST) Message-ID: <19970615103102.EG39497@uriah.heep.sax.de> Date: Sun, 15 Jun 1997 10:31:02 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: fedi@ms13.hinet.net Subject: Re: Burn CD not allowed copy References: <19970609115429.53481@oneway.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970609115429.53481@oneway.net>; from fedi@ms13.hinet.net on Jun 9, 1997 11:54:29 +0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk (Btw., it's considered impolite to post something to a newsgroup and a mailinglist or personal account without mentioning the crosspost.) As fedi@ms13.hinet.net wrote: > I want to burn CD not allowed copy, I have tried many times > but in vain. Below is part of my shell script of burncd. You cannot have your cake, and eat it. Think about it. Copying a CD-ROM means just reading it, so in order to prevent it from being copied, you need to prevent it from being read. You can do this by bending it 20 times, scratching large pieces of the gold coating off, or punching several holes into it. This would be the only imaginable copy protection, but i seriously doubt it's what you're looking for. :-) Get used to the idea that any form of ``copy protection'' is basically meaningless in the computer area, since somebody else will always find a way to work around 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 Tue Jun 17 00:28:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA29517 for hackers-outgoing; Tue, 17 Jun 1997 00:28:24 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA29511 for ; Tue, 17 Jun 1997 00:28:21 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA00483 for hackers@FreeBSD.ORG; Tue, 17 Jun 1997 09:28:19 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id KAA07045; Sun, 15 Jun 1997 10:34:40 +0200 (MET DST) Message-ID: <19970615103440.PB32135@uriah.heep.sax.de> Date: Sun, 15 Jun 1997 10:34:40 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: %i conversion in sscanf? References: <199706091452.AAA29091@genesis.atrad.adelaide.edu.au> <19970609223442.26371@keltia.freenix.fr> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970609223442.26371@keltia.freenix.fr>; from Ollivier Robert on Jun 9, 1997 22:34:42 +0200 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Ollivier Robert wrote: > Interesting: > > 244 [22:29] roberto@keltia:~> perl -e 'print 0xABCDEF45 . "\n"' > 2882400069 Hexadecimal constants are always considered unsigned. Garrett recently pointed this out for the C case, and i assume Perl is just doing it similar. Too bad that scanf is not consistent with 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 Jun 17 00:28:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA29539 for hackers-outgoing; Tue, 17 Jun 1997 00:28:29 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA29528 for ; Tue, 17 Jun 1997 00:28:26 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA00484; Tue, 17 Jun 1997 09:28:24 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id KAA07062; Sun, 15 Jun 1997 10:38:32 +0200 (MET DST) Message-ID: <19970615103831.BN11477@uriah.heep.sax.de> Date: Sun, 15 Jun 1997 10:38:31 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: luigi@iet.unipi.it (Luigi Rizzo) Subject: Re: rtprio from non-root users ? References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Luigi Rizzo on Jun 9, 1997 22:25:58 +0200 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Luigi Rizzo wrote: > I am trying to allow non-root accounts to use CD-R devices. The rtprio there is probably overly paranoid. In my original scripts, i forgot to add the rtprio to the dd part of the pipeline, and i've been using it this way for quite a long time without any problem. :) (Note that this made the rtprio basically meaningless, since it only applied to the unimportant disk-reading team process, but not to the important CD-R writing dd.) At any rate, if you insist on the rtprio, write a setuid Perl script. That's the simplest solution, and it doesn't even require any additional software (like sudo). -- 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 Jun 17 00:28:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA29583 for hackers-outgoing; Tue, 17 Jun 1997 00:28:49 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA29573 for ; Tue, 17 Jun 1997 00:28:44 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA00491 for hackers@FreeBSD.ORG; Tue, 17 Jun 1997 09:28:42 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id OAA07418; Sun, 15 Jun 1997 14:38:37 +0200 (MET DST) Message-ID: <19970615143837.DG25350@uriah.heep.sax.de> Date: Sun, 15 Jun 1997 14:38:37 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: tar hangs 2.2.x system References: <199706110614.BAA04741@dyson.iquest.net> <339E86BE.7A59@cki.ipri.kiev.ua> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <339E86BE.7A59@cki.ipri.kiev.ua>; from Ruslan Shevchenko on Jun 11, 1997 14:06:25 +0300 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Ruslan Shevchenko wrote: > > tar -cvf /dev/rfd0 somefiles > > > > Note the "raw" device. > > > > But it is a bug. > > Anybody, do send_pr No, don't. For one, it was a known bug, so the PR wouldn't probably have caused more reason for anybody at all, and now, Bruce has fixed this bug a couple of days ago. Folks, nevertheless: Buffered devices (/dev/fd0) are JUST and ONLY for mounting something (and for swapon(8)). Raw devices (/dev/rfd0) are FOR EVERYTHING ELSE. (The terms `block device' and `character device' are misnomers you should never use. Historical errors.) Sorry for shouting, but from some non-newbie like dennis, i would have expected to know this. I'm repeating this over and over again to my clients on any Unix course i'm teaching. (There are several reasons for this statement, beyond the now fixed FreeBSD bug.) -- 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 Jun 17 00:29:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA29630 for hackers-outgoing; Tue, 17 Jun 1997 00:29:20 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA29618 for ; Tue, 17 Jun 1997 00:29:12 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA00492; Tue, 17 Jun 1997 09:28:48 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id OAA07441; Sun, 15 Jun 1997 14:42:41 +0200 (MET DST) Message-ID: <19970615144241.VR25113@uriah.heep.sax.de> Date: Sun, 15 Jun 1997 14:42:41 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: handy@sag.space.lockheed.com (Brian N. Handy) Subject: Re: malloc failed? References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Brian N. Handy on Jun 11, 1997 09:21:56 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Brian N. Handy wrote: > > Also, back in 2.1, I ran into a problem where the max data size could > >not be increased greater than physical memory. I wonder if this could > >your problem too. > > Well, that's not my problem, I only have 80MB of physical memory. (I have > 240MB of swap, so I surmise that's not the problem either.) You're probably hitting the absolute hard limit. It's a compile-time option for your kernel. RTFLINT. -- 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 Jun 17 00:30:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA29731 for hackers-outgoing; Tue, 17 Jun 1997 00:30:02 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA29685 for ; Tue, 17 Jun 1997 00:29:56 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA00493; Tue, 17 Jun 1997 09:29:51 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id OAA07459; Sun, 15 Jun 1997 14:46:11 +0200 (MET DST) Message-ID: <19970615144611.AD50958@uriah.heep.sax.de> Date: Sun, 15 Jun 1997 14:46:11 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: julian@whistle.com (Julian Elischer) Subject: Re: BSD2.2 (a while ago) and ppwait state References: <339E0785.2781E494@whistle.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <339E0785.2781E494@whistle.com>; from Julian Elischer on Jun 10, 1997 19:03:49 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Julian Elischer wrote: > Does anyone know why we are seeing this on a machine > with kernels several months old? > I don't remember discussion of this.. > > basically, processes start freezing (after 6 hours) > in 'ppwait' state, which appears to be related to vfork. John's vfork optimization caused a hang in libc's (buggy) popen(3) implementation. Look into the CVS history of src/lib/libc/gen/popen.c, or bring your sys/kern/kern_fork.c to rev. 1.38 (supposedly). -- 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 Jun 17 00:32:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA29920 for hackers-outgoing; Tue, 17 Jun 1997 00:32:01 -0700 (PDT) Received: from freefall.freebsd.org (freefall.cdrom.com [204.216.27.21]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA29905 for ; Tue, 17 Jun 1997 00:31:59 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA19043 for ; Tue, 17 Jun 1997 00:31:05 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA00504; Tue, 17 Jun 1997 09:31:42 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id PAA07598; Sun, 15 Jun 1997 15:19:32 +0200 (MET DST) Message-ID: <19970615151932.ZQ32245@uriah.heep.sax.de> Date: Sun, 15 Jun 1997 15:19:32 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.com Cc: thompson@squirrel.tgsoft.com (mark thompson) Subject: Re: floppy, redux References: <19970612151521.6346.qmail@squirrel.tgsoft.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970612151521.6346.qmail@squirrel.tgsoft.com>; from mark thompson on Jun 12, 1997 15:15:21 -0000 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As mark thompson wrote: > The floppy controller/DMA unit comes in for suspicion. Unfortunately, > this started shortly after going to 2.2.1 from 2.1.7, so i also suspect > the driver. The driver hasn't changed much during the last years. I bet you're erroneously using the buffered devices, where you should use the raw ones, are you? This vastly increases the source of possible problems, by including the entire buffer cache into suspicion. -- 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 Jun 17 00:33:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA00139 for hackers-outgoing; Tue, 17 Jun 1997 00:33:11 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA00134 for ; Tue, 17 Jun 1997 00:33:07 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id RAA25623; Tue, 17 Jun 1997 17:16:04 +1000 Date: Tue, 17 Jun 1997 17:16:04 +1000 From: Bruce Evans Message-Id: <199706170716.RAA25623@godzilla.zeta.org.au> To: freebsd-hackers@FreeBSD.ORG, shigio@wafu.netgate.net Subject: Re: an inconvenience about macro [/usr/src/sys/sys/kernel.h] Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >--------------------------------------------------------------------------- >Inconvenience about Macro >--------------------------------------------------------------------------- > >In /usr/src/sys/kern/init_main.c, SYSINIT macro is used. It is like this. > > [/usr/src/sys/kern/init_main.c] > SYSINIT(placeholder, SI_SUB_DUMMY,SI_ORDER_ANY, NULL, NULL) > >SYSINIT doesn't end with ';', because the definition already has it. I like leaving off the semicolon in the macro definition like this so that a semicolon must be supplied and is valid after invocations of the macro. Most of the SYSCTL() macros have the same problem. I planned to fix this someday. >But ctags(1) cannot treat this pattern. indent(1) has the same problem. This problem is mostly avoided by following the macro invocations with an invalid semicolon (the resulting null declarations at file scope are syntax errors in ANSI C). Bruce From owner-freebsd-hackers Tue Jun 17 00:35:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA00331 for hackers-outgoing; Tue, 17 Jun 1997 00:35:48 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA00322 for ; Tue, 17 Jun 1997 00:35:44 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA00528 for freebsd-hackers@FreeBSD.ORG; Tue, 17 Jun 1997 09:35:37 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id QAA07792; Sun, 15 Jun 1997 16:02:52 +0200 (MET DST) Message-ID: <19970615160250.HK59536@uriah.heep.sax.de> Date: Sun, 15 Jun 1997 16:02:50 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Subject: Re: dump/restore with compression References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Brandon Gillespie on Jun 12, 1997 13:40:51 -0600 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Brandon Gillespie wrote: > Is there plans to integrate a compression option into dump and restore? > Does anybody USE dump/restore anymore? I've been using the Digital Unix > equivalent 'vdump' and 'vrestore' for a while now, and it has a lot more > capability than the older dump/restore (such as compression 8) ``a lot more'' is a bit of an overstatement. Apart from it being created to handle AdvFS (and thus AdvFS filesets), it has just -D (for backing up subdirectories, as opposed to entire filesystems or filesets), and -C, that are real advantages. What i didn't like is that they broke compatibility. vdump's output is incompatible with dump's. That's something they shouldn't have broken without reason. dump is compatible across machines, even if it doesn't look so at the first glance. Adding compression shouldn't be too hard. You gotta add a new flag, link libz to the binary (which will unfortunately bloat it), and you should probably store the filename inside the archive with a `.gz' appended. This way, an older restore that doesn't understand the compression flag will just restore a gzip'ed file, while a newer restore will decode the flag, and knows that it can strip the `.gz' after decompressing the file. For files that are already compressed, you simply omit the flag. It requires somebody doing it. :-) Even given Terry's vehemental vote for a block compression, i'd rather like to see it as outlined above, since it's probably the most flexible variant. Of course, i personally wouldn't use it much, but rely on the hardware compression of my tape drive. ;) -- 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 Jun 17 00:36:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA00429 for hackers-outgoing; Tue, 17 Jun 1997 00:36:41 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA00423 for ; Tue, 17 Jun 1997 00:36:38 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA00530; Tue, 17 Jun 1997 09:36:03 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id QAA07820; Sun, 15 Jun 1997 16:12:49 +0200 (MET DST) Message-ID: <19970615161247.MU44516@uriah.heep.sax.de> Date: Sun, 15 Jun 1997 16:12:47 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: john@isi.co.jp (john cooper) Subject: Re: TEAC WORM Drive Model CD-R50S.. References: <199706142346.IAA11795@ns.isi.co.jp> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706142346.IAA11795@ns.isi.co.jp>; from john cooper on Jun 15, 1997 08:46:31 +0900 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As john cooper wrote: > Anyone know for a fact if this drive will work under 2.2.1? Unless it's compatible with HP or Philips drives (both being effectively the same), it's not likely. > The TEAC website was rather content-free, specification wise. Bug them about documentation, or pick another vendor. Tell them so. -- 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 Jun 17 01:09:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA01721 for hackers-outgoing; Tue, 17 Jun 1997 01:09:42 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA01699 for ; Tue, 17 Jun 1997 01:09:37 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA00618 for FreeBSD-hackers@FreeBSD.ORG; Tue, 17 Jun 1997 10:03:50 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA12598; Mon, 16 Jun 1997 08:11:03 +0200 (MET DST) Message-ID: <19970616081103.EZ47070@uriah.heep.sax.de> Date: Mon, 16 Jun 1997 08:11:03 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: FreeBSD-hackers@FreeBSD.ORG Subject: Re: ISDN troubles: it now works References: <199706151548.RAA29785@helbig.informatik.ba-stuttgart.de> <199706151853.UAA04038@yedi.iaf.nl> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706151853.UAA04038@yedi.iaf.nl>; from Wilko Bulte on Jun 15, 1997 20:53:22 +0200 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Wilko Bulte wrote: > (stupid question: will this whole ISDN/ppp thing be really > integrated into -current one time? So that it ends up on a release > cd sometime? As noted, I'm not an expert on this stuff so I don't > feel qualified to do it myself) BISDN has currently legal problems that prevent it from releasing anything more recent than 0.97. That's why you gotta bother with a one-year old package that doesn't fit quite into FreeBSD-current. Once the legally questionable files are rewritten (which is driven by a large overhaul of the lower layers anyway, most work done by Hellmuth Michaelis), we can think about integrating it into the FreeBSD tree. The PPP stuff also needs quite some work. It seems we decided inside the BISDN developers list that it would be useful to maintain two different versions of PPP, both targeted to different people. -- 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 Jun 17 01:10:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA01867 for hackers-outgoing; Tue, 17 Jun 1997 01:10:40 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA01862 for ; Tue, 17 Jun 1997 01:10:36 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA00675; Tue, 17 Jun 1997 10:10:23 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA12695; Mon, 16 Jun 1997 08:32:58 +0200 (MET DST) Message-ID: <19970616083258.PA23683@uriah.heep.sax.de> Date: Mon, 16 Jun 1997 08:32:58 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: housley@nest.pr-comm.com (James E. Housley), brian@awfulhak.demon.co.uk Subject: Re: User PPP problems sometime after 2.2.0 References: <199706160218.WAA00361@nest.pr-comm.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706160218.WAA00361@nest.pr-comm.com>; from James E. Housley on Jun 15, 1997 22:18:32 -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As James E. Housley wrote: > I have been tracking 2.2-STABLE via CVSup and it has been a while since I > compiled the updates. I did a make world and now I am haveing problems > with user PPP. If I do 'ppp osprey' and then 'term' and manually dial > and log in everything is fine. However, if I do 'ppp osprey' and then > 'dial'. The modem dials and connects and then hangs up. I have have a > log file showing both sequences, but it is very large. I turned on ALL > set log entries. In the second sequence I get a Disconnected! very early > in the link setup. I think you've got a problem in LCP or IPCP negotiation, and since the negotiation doesn't converge for some reason, both sides decide to hangup in the end. That's what the Disconnected! comes from. It's probably the most useful level to log `LCP' (which i understand also includes IPCP). -- 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 Jun 17 01:17:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA02176 for hackers-outgoing; Tue, 17 Jun 1997 01:17:48 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA02169 for ; Tue, 17 Jun 1997 01:17:45 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA00810 for hackers@FreeBSD.ORG; Tue, 17 Jun 1997 10:17:43 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id XAA14923; Mon, 16 Jun 1997 23:05:39 +0200 (MET DST) Message-ID: <19970616230539.ZT15015@uriah.heep.sax.de> Date: Mon, 16 Jun 1997 23:05:39 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: (Fwd) Re: Serious potential IMAP problem References: <199706161925.MAA11250@train.tgci.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706161925.MAA11250@train.tgci.com>; from Riley J. McIntire on Jun 16, 1997 12:25:30 +0000 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Riley J. McIntire wrote: > Normally I just lurk on the hackers list, but at the risk of being > flamed, thought this might generate some interest here as a possible > enhancement to FreeBSD. This is probably highly inflammable material. :) I will restrict the number of my followups. > > In good operating systems, there is a non-root state which equates to being > > "not logged in"; it issue an unprivileged system call to log in with > > authentication credentials in the call. The kernel validates the > > authentication credentials and sets the process's user id on success. > > I concur with this analysis. I think this guy is simply looking through his NT view onto the world, nothing else. In NT, you gotta ``log in'' first in order to do anything. In Unix, you run a process with your credentials, and you don't need to be logged in (e.g. cron can run it on your behalf). Providing a such a metauser/-state would IMHO be just _the_ target for hacking then, since you can afterwards assume any UID, including root -- since if this state can be used to login a user, it must be able to obtain Superuser privileges (in order to log in the Superuser). Presumably, after authenticating him, but if some cracker gets a similar process that doesn't authenticate, he got root. The ``good operating system'' with its method has already been proven that the requirement to always log in first also has its problems... There are rumours that when you use their telnetd, the console user suddenly switches to the identity of the telnetting user. :-O -- 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 Jun 17 01:32:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA03011 for hackers-outgoing; Tue, 17 Jun 1997 01:32:42 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA03006 for ; Tue, 17 Jun 1997 01:32:28 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id KAA17560; Tue, 17 Jun 1997 10:03:42 +0200 From: Luigi Rizzo Message-Id: <199706170803.KAA17560@labinfo.iet.unipi.it> Subject: Re: rtprio from non-root users ? To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 17 Jun 1997 10:03:42 +0200 (MET DST) Cc: hackers@FreeBSD.ORG, luigi@iet.unipi.it In-Reply-To: <19970615103831.BN11477@uriah.heep.sax.de> from "J Wunsch" at Jun 15, 97 10:38:12 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > As Luigi Rizzo wrote: > > > I am trying to allow non-root accounts to use CD-R devices. > > The rtprio there is probably overly paranoid. In my original scripts, > i forgot to add the rtprio to the dd part of the pipeline, and i've > been using it this way for quite a long time without any problem. :) I see. On 2.2.X the rtprio commands in burncd.sh are correct :) In light of the recent discussion on disk scheduling etc. it turns out that probably the biggest danger for a correct cd burn is the fact that a process may be starved by another disk-intensive activity (although team is so aggressive that it is unlikely to become the victim of starvation). Next danger on a small-memory system is probably the fact that some of the buffers used by team (or dd ?) might get swapped out. I'd say that if we really want a safer cd write utility, we'd better write a specific program (perhaps just a few patches to "team" would suffice) which does all is needed (from rtrpio to locking buffers in memory etc.) Cheers Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Tue Jun 17 02:46:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA06093 for hackers-outgoing; Tue, 17 Jun 1997 02:46:49 -0700 (PDT) Received: from smtp1.ts.kiev.ua (viking.ts.kiev.ua [193.124.229.195]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA06078 for ; Tue, 17 Jun 1997 02:46:37 -0700 (PDT) Received: from aviion.ts.kiev.ua by smtp1.ts.kiev.ua with SMTP id MAA17767; (8.8.3/zah/2.1) Tue, 17 Jun 1997 12:34:58 +0300 (EET DST) Received: from nbki.ipri.kiev.ua by aviion.ts.kiev.ua with ESMTP id KAA02245; (8.6.11/zah/2.1) Tue, 17 Jun 1997 10:17:56 GMT Received: from cki.ipri.kiev.ua by nbki.ipri.kiev.ua with ESMTP id MAA18452; (8.6.9/zah/1.1) Tue, 17 Jun 1997 12:05:33 +0100 Received: from 194.44.146.14 (mac.ipri.kiev.ua [194.44.146.14]) by cki.ipri.kiev.ua (8.7.6/8.7.3) with SMTP id MAA00664 for ; Tue, 17 Jun 1997 12:01:32 +0300 (EET DST) Message-ID: <33A644A0.1981@cki.ipri.kiev.ua> Date: Tue, 17 Jun 1997 11:02:39 +0300 From: Ruslan Shevchenko Reply-To: rssh@cki.ipri.kiev.ua Organization: IPRI X-Mailer: Mozilla 3.01Gold (Macintosh; I; 68K) MIME-Version: 1.0 To: hackers@freebsd.org Subject: setting PATH in skeleton files Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I see phrase PATH=....... in skeleton files (i.e. in /usr/share/skel/dot.profile, the same in dot.cshrc) In generally it is bad, becouse system admininstrator can not add new directory in /etc/profile. for all users. From owner-freebsd-hackers Tue Jun 17 04:24:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA09634 for hackers-outgoing; Tue, 17 Jun 1997 04:24:27 -0700 (PDT) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA09626 for ; Tue, 17 Jun 1997 04:24:17 -0700 (PDT) Received: from p0.hai.siemens.co.at (root@firix [10.1.143.100]) by zwei.siemens.at with SMTP id NAA12647 for ; Tue, 17 Jun 1997 13:25:21 +0200 (MET DST) Received: from zerberus.hai.siemens.co.at by p0.hai.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0wdwO0-00074LC; Tue, 17 Jun 97 13:25 MET DST Received: from zerberus (localhost) by zerberus.hai.siemens.co.at (4.1/SMI-4.1) id AA22928; Tue, 17 Jun 97 13:24:15 +0200 Message-Id: <33A673DE.41C67EA6@zerberus.hai.siemens.co.at> Date: Tue, 17 Jun 1997 13:24:14 +0200 From: Helmut Wirth Organization: Siemens AG. Österreich X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 4.1.4 sun4c) Mime-Version: 1.0 To: Joerg Wunsch Cc: freebsd-hackers@FreeBSD.ORG Subject: Question to CD Writer and FreeBSD References: <19970609115429.53481@oneway.net> <19970615103102.EG39497@uriah.heep.sax.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, I have a question concerning my CD writer: I have a HP6020i writer and it works fine under W95. I would like to use it under FreeBSD. I have FreeBSD-2.2 Stable (via ctm). Last time I looked at the driver only the HP4020i had an entry. But I read messages here, that HP6020i is supported meanwhile. Is this true? Have I to do something special to use it? Any hints? Btw: Last time I looked (about a week before) at the HP Web page the specification for the HP6020i was "not yet ready". Helmut F. Wirth --------------- E-mail: hfwirth@ping.at E-mail (at work): wirth@zerberus.hai.siemens.co.at Tel. : +43-1-1707-37610 (at work) FAX : +43-1-1707-57602 (at work) From owner-freebsd-hackers Tue Jun 17 11:08:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA26801 for hackers-outgoing; Tue, 17 Jun 1997 11:08:22 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA26796 for ; Tue, 17 Jun 1997 11:08:19 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0we2dj-0003GK-00; Tue, 17 Jun 1997 11:05:59 -0700 Date: Tue, 17 Jun 1997 11:05:58 -0700 (PDT) From: Tom Samplonius To: Ruslan Shevchenko cc: hackers@freebsd.org Subject: Re: setting PATH in skeleton files In-Reply-To: <33A644A0.1981@cki.ipri.kiev.ua> 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, 17 Jun 1997, Ruslan Shevchenko wrote: > I see phrase > PATH=....... in skeleton files > (i.e. in /usr/share/skel/dot.profile, the same in dot.cshrc) > > In generally it is bad, becouse > system admininstrator can not add new directory in /etc/profile. > for all users. > > Yes, it really should go into /etc/login.conf, so it works for all shells, and not just for bash/sh Tom From owner-freebsd-hackers Tue Jun 17 11:52:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA00490 for hackers-outgoing; Tue, 17 Jun 1997 11:52:57 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA00482 for ; Tue, 17 Jun 1997 11:52:55 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA03357 (5.67b/IDA-1.5 for FreeBSD-hackers@FreeBSD.ORG); Tue, 17 Jun 1997 20:53:10 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id UAA00859; Tue, 17 Jun 1997 20:15:53 +0200 (MET DST) From: Wilko Bulte Message-Id: <199706171815.UAA00859@yedi.iaf.nl> Subject: Re: ISDN troubles: it now works To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 17 Jun 1997 20:15:53 +0200 (MET DST) Cc: FreeBSD-hackers@FreeBSD.ORG In-Reply-To: <19970616081103.EZ47070@uriah.heep.sax.de> from "J Wunsch" at Jun 16, 97 08:11:03 am X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As J Wunsch wrote... > As Wilko Bulte wrote: > > > (stupid question: will this whole ISDN/ppp thing be really > > integrated into -current one time? So that it ends up on a release > > cd sometime? As noted, I'm not an expert on this stuff so I don't > > feel qualified to do it myself) > > BISDN has currently legal problems that prevent it from releasing > anything more recent than 0.97. That's why you gotta bother with a > one-year old package that doesn't fit quite into FreeBSD-current. Right... I knew it must be something like this. Lawyers... > The PPP stuff also needs quite some work. It seems we decided inside > the BISDN developers list that it would be useful to maintain two > different versions of PPP, both targeted to different people. I would agree. I suppose there are idiosyncrasies beyond my grasp that make different code for [isdn]pppd the most practical solution. Just pick the daemon of your liking. Thanks for clarifying this. Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-hackers Tue Jun 17 11:58:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA00764 for hackers-outgoing; Tue, 17 Jun 1997 11:58:11 -0700 (PDT) Received: from tornado.cisco.com (tornado.cisco.com [171.69.104.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA00758 for ; Tue, 17 Jun 1997 11:58:08 -0700 (PDT) Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147]) by tornado.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id OAA02998 for ; Tue, 17 Jun 1997 14:56:51 -0400 (EDT) Received: from bmcgover-pc.cisco.com (localhost.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.8.5/8.8.5) with ESMTP id OAA00228 for ; Tue, 17 Jun 1997 14:57:36 -0400 (EDT) Message-Id: <199706171857.OAA00228@bmcgover-pc.cisco.com> To: hackers@freebsd.org Subject: Clists limited to 1024 bytes? Date: Tue, 17 Jun 1997 14:57:35 -0400 From: Brian McGovern Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've been tinkering around with line disciplines, and have been having problems with the bottom half of the input side. It appears that l_rint will stop passing characters up at 19200 at around 1K (or so t_rawq.cc states). Is there any way to safely increase this to around 8K, or even 16K? The reason I ask is that the board I'm working with has an 8K receive buffer, and I'd like (for the sake of efficiency), be able to move nearly a full buffer of data at once, but I seem to be limited by this number. I've taken a look at tp->t_hiwat in the termios structure, as well as c_cbmax in the clist structure, and neither seems to collate directly with this limit in to the clists. Can anyone comment, and possibly get me past this? Thanks. -Brian From owner-freebsd-hackers Tue Jun 17 12:34:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA02676 for hackers-outgoing; Tue, 17 Jun 1997 12:34:32 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA02671 for ; Tue, 17 Jun 1997 12:34:29 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA08983 for hackers@FreeBSD.ORG; Tue, 17 Jun 1997 21:34:27 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id SAA18655; Tue, 17 Jun 1997 18:50:33 +0200 (MET DST) Message-ID: <19970617185032.VJ21658@uriah.heep.sax.de> Date: Tue, 17 Jun 1997 18:50:32 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: rtprio from non-root users ? References: <19970615103831.BN11477@uriah.heep.sax.de> <199706170803.KAA17560@labinfo.iet.unipi.it> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706170803.KAA17560@labinfo.iet.unipi.it>; from Luigi Rizzo on Jun 17, 1997 10:03:42 +0200 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Luigi Rizzo wrote: > In light of the recent discussion on disk scheduling etc. it turns > out that probably the biggest danger for a correct cd burn is the > fact that a process may be starved by another disk-intensive activity > (although team is so aggressive that it is unlikely to become the > victim of starvation). Right. I've seen it starving when heavy paging was going on (from a netpbm process allocating way more than the physical memory). -- 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 Jun 17 13:18:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA04648 for hackers-outgoing; Tue, 17 Jun 1997 13:18:20 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA04633 for ; Tue, 17 Jun 1997 13:18:09 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id WAA10584 for ; Tue, 17 Jun 1997 22:18:02 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id WAA03261 for hackers@FreeBSD.ORG; Tue, 17 Jun 1997 22:17:56 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id VAA01365; Tue, 17 Jun 1997 21:38:12 +0200 (CEST) Message-ID: <19970617213812.27013@keltia.freenix.fr> Date: Tue, 17 Jun 1997 21:38:12 +0200 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: %i conversion in sscanf? References: <199706091452.AAA29091@genesis.atrad.adelaide.edu.au> <19970609223442.26371@keltia.freenix.fr> <19970615103440.PB32135@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <19970615103440.PB32135@uriah.heep.sax.de>; from J Wunsch on Sun, Jun 15, 1997 at 10:34:40AM +0200 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3385 AMD-K6 MMX @ 208 MHz Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to J Wunsch: > Hexadecimal constants are always considered unsigned. Garrett > recently pointed this out for the C case, and i assume Perl is just > doing it similar. More, all variables are floating-point ones, unless one uses "use integer;" (in post 5.003 Perl). -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #20: Fri Jun 13 00:16:13 CEST 1997 From owner-freebsd-hackers Tue Jun 17 13:22:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA05003 for hackers-outgoing; Tue, 17 Jun 1997 13:22:21 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA04998 for ; Tue, 17 Jun 1997 13:22:18 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA09570; Tue, 17 Jun 1997 22:21:46 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id VAA19374; Tue, 17 Jun 1997 21:54:50 +0200 (MET DST) Message-ID: <19970617215450.WS33139@uriah.heep.sax.de> Date: Tue, 17 Jun 1997 21:54:50 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: wirth@zerberus.hai.siemens.co.at (Helmut Wirth) Subject: Re: Question to CD Writer and FreeBSD References: <19970609115429.53481@oneway.net> <19970615103102.EG39497@uriah.heep.sax.de> <33A673DE.41C67EA6@zerberus.hai.siemens.co.at> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <33A673DE.41C67EA6@zerberus.hai.siemens.co.at>; from Helmut Wirth on Jun 17, 1997 13:24:14 +0200 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Helmut Wirth wrote: > I have a question concerning my CD writer: I have a HP6020i writer > and it works fine under W95. I would like to use it under FreeBSD. I > have FreeBSD-2.2 Stable (via ctm). Last time I looked at the driver only > the HP4020i had an entry. Don't worry. Say ``wormcontrol select HP 4020i'', and go ahead. The device detection in the kernel itself works, and the command sets are reasonably compatible. In -stable, there's still a problem that forces you to reload the medium after each use. Jean-Marc fixed this (and improved many other things) in -current. -- 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 Jun 17 13:50:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA06621 for hackers-outgoing; Tue, 17 Jun 1997 13:50:26 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA06615 for ; Tue, 17 Jun 1997 13:50:22 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA19623; Tue, 17 Jun 1997 13:41:45 -0700 From: Terry Lambert Message-Id: <199706172041.NAA19623@phaeton.artisoft.com> Subject: Re: Burn CD not allowed copy To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 17 Jun 1997 13:41:44 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG, fedi@ms13.hinet.net In-Reply-To: <19970615103102.EG39497@uriah.heep.sax.de> from "J Wunsch" at Jun 15, 97 10:31:02 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 > Get used to the idea that any form of ``copy protection'' is basically > meaningless in the computer area, since somebody else will always find > a way to work around it. If worse comes to worse, there are people who will cheerily help other people dump RAM images of already executing programs and the code preamble necessary to cause them to load and reset the registers and program counter, then resume execution. So even if you do come up with a workable copy protection scheme, people will just grab the image after it has been started and called the verification code. If you insist on copy protection, you should simply silk-screen "I am smarter than you" onto the CDROM... at least that way it will stay around when some cracker says "Oh no you're not!", unlike non-physical software claims that you are smarter than him (ie: copy protection). Of course, if you really wanted to make it inconvenient for a cracker, build a dongle. This will make it inconvenient for your users as well, but you can bask happily in the knowledge that for every user who can't use your software, neither can 10 crackers -- who would never have paid you a dime anyway, since people prevented from stealing something don't go out and buy it because they can't steal it. 8-P. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jun 17 13:52:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA06766 for hackers-outgoing; Tue, 17 Jun 1997 13:52:33 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA06758 for ; Tue, 17 Jun 1997 13:52:30 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA10070 for hackers@freebsd.org; Tue, 17 Jun 1997 22:52:29 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA19543; Tue, 17 Jun 1997 22:41:26 +0200 (MET DST) Message-ID: <19970617224125.NK30309@uriah.heep.sax.de> Date: Tue, 17 Jun 1997 22:41:25 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: bin/3837: new feature for rtprio References: <199706170740.AAA00720@hub.freebsd.org> <199706171148.HAA17808@hda.hda.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706171148.HAA17808@hda.hda.com>; from Peter Dufault on Jun 17, 1997 07:48:06 -0400 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Peter Dufault wrote: > My wish list, expanding beyond rtprio: > > 1. Compile a program out of a book using P1003.1b real time interface > with no changes. This means no get credentials calls in the program > since P1003.1b only mumbles about "appropriate privilege" without > any definition. Hmm, hmm. Now i gotta admit that i don't even have the slightest clues about P1003.1b. -- 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 Jun 17 13:53:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA06852 for hackers-outgoing; Tue, 17 Jun 1997 13:53:05 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA06839 for ; Tue, 17 Jun 1997 13:53:01 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA19632; Tue, 17 Jun 1997 13:44:29 -0700 From: Terry Lambert Message-Id: <199706172044.NAA19632@phaeton.artisoft.com> Subject: Re: dump/restore with compression To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 17 Jun 1997 13:44:29 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <19970615160250.HK59536@uriah.heep.sax.de> from "J Wunsch" at Jun 15, 97 04:02:50 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 > Even given Terry's vehemental vote for a block compression, i'd rather > like to see it as outlined above, since it's probably the most > flexible variant. Of course, i personally wouldn't use it much, but > rely on the hardware compression of my tape drive. ;) Which is, incidently, block compression so that partial recovery of archives are possible (unless you have one of the old, stupid QIC-40/80 floppy tape controller boards with the wierd compression that locks you into one hardware vendor for eternity, yet isn't manufactured any more). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jun 17 14:24:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA08568 for hackers-outgoing; Tue, 17 Jun 1997 14:24:20 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA08541 for ; Tue, 17 Jun 1997 14:24:13 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id XAA10720 for ; Tue, 17 Jun 1997 23:24:03 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id XAA04090 for freebsd-hackers@FreeBSD.ORG; Tue, 17 Jun 1997 23:23:43 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id XAA02197; Tue, 17 Jun 1997 23:23:21 +0200 (CEST) Message-ID: <19970617232321.46029@keltia.freenix.fr> Date: Tue, 17 Jun 1997 23:23:21 +0200 From: Ollivier Robert To: freebsd-hackers@FreeBSD.ORG Subject: Re: Burn CD not allowed copy References: <19970615103102.EG39497@uriah.heep.sax.de> <199706172041.NAA19623@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <199706172041.NAA19623@phaeton.artisoft.com>; from Terry Lambert on Tue, Jun 17, 1997 at 01:41:44PM -0700 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3385 AMD-K6 MMX @ 208 MHz Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Terry Lambert: > Of course, if you really wanted to make it inconvenient for a > cracker, build a dongle. This will make it inconvenient for > your users as well, but you can bask happily in the knowledge > that for every user who can't use your software, neither can 10 That's not really true, I've seen lots of software used without the dongle they were supposed to run with... So it is not a good protection now (even if it takes more work to crack a dongle). > crackers -- who would never have paid you a dime anyway, since > people prevented from stealing something don't go out and buy > it because they can't steal it. I love that sentence :-) -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #20: Fri Jun 13 00:16:13 CEST 1997 From owner-freebsd-hackers Tue Jun 17 14:35:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA09717 for hackers-outgoing; Tue, 17 Jun 1997 14:35:12 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA09712 for ; Tue, 17 Jun 1997 14:35:10 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA19688; Tue, 17 Jun 1997 14:25:24 -0700 From: Terry Lambert Message-Id: <199706172125.OAA19688@phaeton.artisoft.com> Subject: Re: (Fwd) Re: Serious potential IMAP problem To: ahd@kew.com (Drew Derbyshire) Date: Tue, 17 Jun 1997 14:25:24 -0700 (MST) Cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG In-Reply-To: <33a5f31d.kew-sonata@sonata.uucp.kew.com> from "Drew Derbyshire" at Jun 16, 97 10:14:48 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 > > Oh, it's our dear little pal Mark Crispin. He's such a charmer, don't > > you think? > > Suffice to say I did not find this comment charming. Me either. I've been having a productive dialog with Mark regarding the IMAP4rev1 (RFC2060) standard as it relates to server rather than client implementation (the standard appears to have an organizational bias discouraging server writers). There a number of other semantic nastinesses which require token stacks because of ordering issues (variant valued tags preceeding commands so that it is impossible to use alternate Lex start states to disambiguate them, and numeric values untagged responses preceeding identification tokens, etc.). Other than what I view as parser technology favoritism (the LISP model is a religious issue; he does not like Yacc/Lex generated LALR parsers), he has been quite reasonable in discussing these issues. > > > > In good operating systems, there is a non-root state which > > > > equates to being "not logged in"; it issue an unprivileged > > > > system call to log in with authentication credentials in > > > > the call. The kernel validates the authentication credentials > > > > and sets the process's user id on success. I don't like this statement, mostly because it puts a catch-22 on kernel service credentials potentially necessary for boot. Like NFS client services. It also precludes any reasonable method of obtaining priviledged credentials from a completely unpriveleged state. This seems to be a distinction of degree, not one of kind, and therefore an aritifical, puritanical requirement. This is not to say that there are not benefits to the NT security model; only that those benefits derive from implementation, not from the NT model itself. > > This in turn requires the kernel have the mechanism to access the > > credential store, which may equate to bundling every possible password > > access mechanism with the kernel; yeah, let's suck in all the Kerberos > > stuff, NIS, Radius, S/Key, ssh, Tacacs, SecurID, the Captain Midnight > > Secret Decoder Wheel algorithm, and so on. > > This is not correct. For example, FreeBSD file systems need not be > compiled into the kernel to be a system call. Likewise, IBM VM/ESA both > use external file systems and external security packages with well > defined API's which are routed through the kernel but run as started > (daemon) tasks, which would have the required access. The FS comment is a nonsequitur. I do, however, agree that the GSSAPI RFC1508 mechanisms referenced by RFC1731, and the RFC2095 improvement to the clear-text storage of the shared secret on the server are both logical FOR A SERVICE. However, I don't believe that a UNIX (or NT) kernel meets the RFC1508 definition of "application program". > Likewise, numerous systems allow processes acting as "nobody" to execute > commands (login, date, time, in some cases message) which in the case of > a command allow the priv level to be upgraded. Priviledge upgrade by an unpriviledged user is problematic. I *certainly* do *NOT* buy the NT GINA model access via "impersonate" as a very secure mechanism. In general, the MS API's are geared toward *downgrading* security for services started by a process with administrator credentials. Unlike "secure UNIX" and "VMS installed images", the NT model is a poor cousing, in that it requires initial trust (just as with the UNIX login model). > > You'll note that there's no actual attempt to justify why > > authentication by root and subsequent sacrifice of priveledge is > > actually _bad_. > > This is fairly clear to me -- one never wants to grant more access than > is needed, because if excessive access is never gained, it cannot be > abused by programming error or attack before being surrendered. It also > discourages the practice for every setuid program to have direct access > to the sensitive security database. Agreed. But NT is hardly the shining icon to hold up as the "Gold Standard" of such implementations. Clearly, the NT mservice model and external authentication replacement via GINA, in particular, was not well understood before the posting was made. The IMAP4 code from the University of Washington provides imap2/imap3 compatability, both of which require priveledged port access, and I believe the IANA target port for imap4 is also priviledged. In addition, the IMAP4 code, when compiled for NT, has no GSSAPI knowledge of the NT authentication services (via GINA), and provides only LI compliance for authentication (ie: only support for the "LOGIN " facility) on NT. Aside: I can easily crash NT with a user space program of any credential; it is not a far logical leap to me using this not to execute unintentionally erroneous code resulting in a crash, but to instead execute intentionally erroneous code to result in a security breach. The only thing preventing this at present is that I do not have the patience to wade through WinICE to determine the correct incantations. There are doubtless others in the same situation who either *do* have the patience, or who could be paid to act as if they has the patience for sufficient time to complete the task. In the limit, NT *is* crackable by any low priviledged credential with patience (or money, in lieu of patience). > > Alternatively, consider using the PAM framework, which is compact, > > open to analysis, and once analysed, every program that uses it is > > much simpler to analyse in itself. If PAM interests you, see the > > references off my homepage (http://www.smith.net.au/~mike). > > As shared library(s), it still appears to encourage granting root to a > program as trivial a POP3 server which only needs normal user access. > This temporary root access is, to me, inherently more dangerous than > taking a program from no access to the specific user id without a stop > at the higher priv level. I believe there is, implicitly, a stop at a higher level when the user traps to kernel mode for the call. Kernel mode does not even enforce page write protection against kernel services for many Intel processors. It seems to me that the original NT security assumptions are flawed in this regard, even were *all* the system call bugs found and repaired (unlikely in the lifetime of the universe, given most software developement teams' resemblance to road construction crews). 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 Tue Jun 17 14:52:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA10618 for hackers-outgoing; Tue, 17 Jun 1997 14:52:04 -0700 (PDT) Received: from nemeton.com.au (gw.nemeton.com.au [203.8.3.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA10583 for ; Tue, 17 Jun 1997 14:51:58 -0700 (PDT) Received: (qmail 26530 invoked from network); 17 Jun 1997 21:50:36 -0000 Received: from topaz.nemeton.com.au (203.8.3.18) by nemeton.com.au with SMTP; 17 Jun 1997 21:50:36 -0000 Received: (qmail 8427 invoked from network); 17 Jun 1997 21:55:06 -0000 Received: from localhost.nemeton.com.au (127.0.0.1) by localhost.nemeton.com.au with SMTP; 17 Jun 1997 21:55:06 -0000 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-hackers@freebsd.org Subject: Re: dump/restore with compression In-reply-to: <19970615160250.HK59536@uriah.heep.sax.de> Date: Wed, 18 Jun 1997 07:52:36 +1000 Message-ID: <8425.866584356@nemeton.com.au> From: Giles Lean Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 15 Jun 1997 16:02:50 +0200 J Wunsch wrote: > What i didn't like is that they broke compatibility. vdump's output > is incompatible with dump's. That's something they shouldn't have > broken without reason. dump is compatible across machines, even if it > doesn't look so at the first glance. I've never seen different OSes with compatible dump formats. Your ``at first glance'' comment intrigues me; is there something I've missed? Giles From owner-freebsd-hackers Tue Jun 17 15:30:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA12550 for hackers-outgoing; Tue, 17 Jun 1997 15:30:59 -0700 (PDT) Received: from pandora.hh.kew.com (ahd@kendra.ne.highway1.com [24.128.53.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA12545 for ; Tue, 17 Jun 1997 15:30:55 -0700 (PDT) Received: (from ahd@localhost) by pandora.hh.kew.com (8.8.5/8.8.5) id SAA07492; Tue, 17 Jun 1997 18:30:48 -0400 (EDT) Date: Tue, 17 Jun 1997 18:30:48 -0400 (EDT) From: Drew Derbyshire Message-Id: <199706172230.SAA07492@pandora.hh.kew.com> To: ahd@kew.com, terry@lambert.org Subject: Re: (Fwd) Re: Serious potential IMAP problem Cc: hackers@FreeBSD.ORG, msmith@atrad.adelaide.edu.au Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk When I don't even know some of the terms Terry used, it's time to shut up. :-) My only comment would be any references to other OS environments by _me_ would be to IBM mainframe OSes, in particular CP/67 and its off-spring, such as VM/XA. I don't do NT internals. -ahd- From owner-freebsd-hackers Tue Jun 17 15:36:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA12988 for hackers-outgoing; Tue, 17 Jun 1997 15:36:28 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA12983 for ; Tue, 17 Jun 1997 15:36:21 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 6719 invoked by uid 1001); 17 Jun 1997 22:36:15 +0000 (GMT) To: giles@nemeton.com.au Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG Subject: Re: dump/restore with compression In-Reply-To: Your message of "Wed, 18 Jun 1997 07:52:36 +1000" References: <8425.866584356@nemeton.com.au> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 18 Jun 1997 00:36:15 +0200 Message-ID: <6717.866586975@verdi.nethelp.no> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've never seen different OSes with compatible dump formats. > Your ``at first glance'' comment intrigues me; is there something I've > missed? HP-UX and SunOS, for one, had dump formats that were close enough that you could restore a HP dump on a Sun, and vice versa. (Assuming you knew what you were doing - they disagreed on the definition of block size, for instance.) Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Tue Jun 17 18:58:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA21602 for hackers-outgoing; Tue, 17 Jun 1997 18:58:38 -0700 (PDT) Received: from squirrel.tgsoft.com (squirrel.tgsoft.com [207.167.64.183]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA21593 for ; Tue, 17 Jun 1997 18:58:31 -0700 (PDT) Received: (qmail 2612 invoked by uid 128); 18 Jun 1997 01:58:04 -0000 Date: 18 Jun 1997 01:58:04 -0000 Message-ID: <19970618015804.2611.qmail@squirrel.tgsoft.com> From: mark thompson To: j@uriah.heep.sax.de CC: hackers@FreeBSD.ORG In-reply-to: "j@uriah.heep.sax.de"'s message of Sun, 15 Jun 1997 15:19:32 +0200 Subject: Re: floppy, redux Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: j@uriah.heep.sax.de (J Wunsch) Date: Sun, 15 Jun 1997 15:19:32 +0200 As mark thompson wrote: > The floppy controller/DMA unit comes in for suspicion. Unfortunately, > this started shortly after going to 2.2.1 from 2.1.7, so i also suspect > the driver. The driver hasn't changed much during the last years. I bet you're erroneously using the buffered devices, where you should use the raw ones, are you? This vastly increases the source of possible problems, by including the entire buffer cache into suspicion. Well, uhm, no. I have been using /dev/rfd0.1440 (9,3)... either with tar or with mcopy. But answering your question caused me to discover another thing. It only seems to fail when it is copying data to/from the wd0 device. I just did several copies from sd0 and /tmp (mfs), and no problems. The CPU is a IWILL P55TV with integrated fd and wd. Should i perhaps move the wd drive to the OTHER onboard controller? I assume FreeBSD would not freak over that... -mark p.s. FreeBSD 2.2.1-RELEASE #1: Sat May 31 09:13:14 PDT 1997 thompson@squirrel.tgsoft.com:/w/root/usr/src/sys/compile/MARX CPU: AMD K5 model 1 (100.23-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x511 Stepping=1 Features=0x21bf real memory = 50331648 (49152K bytes) avail memory = 47067136 (45964K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 vga0 rev 10 on pci0:17 ahc0 rev 1 int a irq 11 on pci0:18 ahc0: aic7860 Single Channel, SCSI Id=7, 3 SCBs ahc0 waiting for scsi devices to settle ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "SEAGATE ST12550N 0014" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2040MB (4178874 512 byte sectors) (ahc0:4:0): "SONY CD-ROM CDU-8003A 1.9a" type 5 removable SCSI 2 cd0(ahc0:4:0): CD-ROM cd present [332512 x 2048 byte records] vx0 <3COM 3C900 Etherlink XL PCI> rev 0 int a irq 12 on pci0:19 utp/aui/bnc[*bnc*] address 00:60:97:2d:f0:93 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <8 virtual consoles, flags=0x0> lpt0 at 0x3bc-0x3c3 irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 at 0x3e8-0x3ef irq 5 on isa sio2: type 16550A sio3: disabled, not probed. wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 1549MB (3173184 sectors), 3148 cyls, 16 heads, 63 S/T, 512 B/S fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in fd1: 1.2MB 5.25in npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 9 drq 1 on isa sb0: IP packet filtering initialized, divert enabled, unlimited logging From owner-freebsd-hackers Tue Jun 17 20:23:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA25162 for hackers-outgoing; Tue, 17 Jun 1997 20:23:46 -0700 (PDT) Received: from brickbat9.mindspring.com (brickbat9.mindspring.com [207.69.200.12]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA25154 for ; Tue, 17 Jun 1997 20:23:42 -0700 (PDT) Received: from bogus.mindspring.com (user-37kbo12.dialup.mindspring.com [207.69.224.34]) by brickbat9.mindspring.com (8.8.5/8.8.5) with SMTP id XAA10841; Tue, 17 Jun 1997 23:23:36 -0400 (EDT) Message-Id: <1.5.4.32.19970618032336.006984c4@mindspring.com> X-Sender: kpneal@mindspring.com X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 17 Jun 1997 23:23:36 -0400 To: Thomas David Rivers From: "Kevin P. Neal" Subject: Re: REQ: FreeBSD in our life Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 08:57 PM 6/16/97 -0400, Thomas David Rivers wrote: >> i did a presentation at europen.se in oct 1996 >> and anonther in research triangle park in may 1997 >> i can send you my sldies in tex format >> will that help? >> > > Hey!! Not to directly respond to this; but just as a note >to Jonathan and anyone else. > > If you ever find yourself in the Research Triangle Park area; >just let me know!!! I can show you around! > > - Dave Rivers - Yes, and I can tag along (if nobody minds). Maybe eat at the cafeteria (because it's so very nice and cheap as well) or something. -- XCOMM Kevin P. Neal, Junior, Comp. Sci. - House of Retrocomputing XCOMM mailto:kpneal@pobox.com - http://www.pobox.com/~kpn/ XCOMM kpneal@eos.ncsu.edu Spoken by Keir Finlow-Bates: XCOMM "Good grief, I've just noticed I've typed in a rant. Sorry chaps!" From owner-freebsd-hackers Tue Jun 17 21:10:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA26725 for hackers-outgoing; Tue, 17 Jun 1997 21:10:05 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA26687 for ; Tue, 17 Jun 1997 21:09:52 -0700 (PDT) Received: from awfulhak.demon.co.uk (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id EAA01797; Wed, 18 Jun 1997 04:06:48 +0100 (BST) Message-Id: <199706180306.EAA01797@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: Mark Tinguely , Stephen Roome , Robert Huff , freebsd-hackers@freebsd.org, Ari Suutari Subject: pppd/natd Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Jun 1997 04:06:48 +0100 From: Brian Somers Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've just applied a small patch that fixes the pppd/natd crash in 2.2 & -current. The patch isn't the perfect solution, but it will get things up and running for the time being. I'll continue to look into what's actually causing the garbage mbuf in the first place. If anybody *isn't* using cvsup or ctm, the patch is as follows: diff -c -r1.19 ppp_tty.c *** ppp_tty.c 1997/06/09 04:13:48 1.19 --- ppp_tty.c 1997/06/18 02:41:14 *************** *** 641,646 **** --- 641,651 ---- } s = spltty(); /* in case.. do not want netisrs to preempt us */ + + m = sc->sc_outm; + if (m && m->m_len < 0) + MFREE(m, sc->sc_outm); + idle = 0; while (CCOUNT(&tp->t_outq) < PPP_HIWAT) { /* -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Tue Jun 17 23:23:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA00923 for hackers-outgoing; Tue, 17 Jun 1997 23:23:25 -0700 (PDT) Received: from polya.blah.org (slmel12p01.ozemail.com.au [203.108.200.89]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA00913 for ; Tue, 17 Jun 1997 23:23:19 -0700 (PDT) Received: (from ada@localhost) by polya.blah.org (8.8.5/8.8.5) id QAA03038 for hackers@FreeBSD.ORG; Wed, 18 Jun 1997 16:23:11 +1000 (EST) From: Ada T Lim Message-Id: <199706180623.QAA03038@polya.blah.org> Subject: Re: hackers-digest V3 #242 In-Reply-To: <199706172053.NAA06861@hub.freebsd.org> from "owner-hackers-digest@FreeBSD.ORG" at "Jun 17, 97 01:53:07 pm" To: hackers@FreeBSD.ORG Date: Wed, 18 Jun 1997 16:23:10 +1000 (EST) X-Mailer: ELM [version 2.4ME+ PL32 (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 > > This in turn requires the kernel have the mechanism to access the > > credential store, which may equate to bundling every possible password > > access mechanism with the kernel; yeah, let's suck in all the Kerberos > > stuff, NIS, Radius, S/Key, ssh, Tacacs, SecurID, the Captain Midnight > > Secret Decoder Wheel algorithm, and so on. no it doesnt; all it needs is a reworked setuid() - setuid(id) { if(id !=0 && getuid()==trusteduser) uid = id; etc. (I know this isn't right, but hopefully you get the idea.) > > You'll note that there's no actual attempt to justify why > > authentication by root and subsequent sacrifice of priveledge is > > actually _bad_. Oh, why don't you make _every_ one of your programs setuid, and then put in a seteuid() call somewhere? because holes exist. > > Alternatively, consider using the PAM framework, which is compact, > > open to analysis, and once analysed, every program that uses it is > > much simpler to analyse in itself. If PAM interests you, see the > > references off my homepage (http://www.smith.net.au/~mike). > > As shared library(s), it still appears to encourage granting root to a > program as trivial a POP3 server which only needs normal user access. > This temporary root access is, to me, inherently more dangerous than > taking a program from no access to the specific user id without a stop > at the higher priv level. I've already been flamed by deraadt for this, so I _know_ I'm onto a good thing :) Anyhow, what would be a good way to implement 'setuid libraries'? (The idea being that all function calls to this library have an implicit setuid(0) first and a setuid() back afterwards. This would mean that things like ptyopen() etc could be used in user-programs without needing to be root. Ada From owner-freebsd-hackers Tue Jun 17 23:51:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA02074 for hackers-outgoing; Tue, 17 Jun 1997 23:51:23 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA02068 for ; Tue, 17 Jun 1997 23:51:19 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA13348 for freebsd-hackers@freebsd.org; Wed, 18 Jun 1997 08:51:00 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA21757; Wed, 18 Jun 1997 08:22:32 +0200 (MET DST) Message-ID: <19970618082232.IY44909@uriah.heep.sax.de> Date: Wed, 18 Jun 1997 08:22:32 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org Subject: Re: dump/restore with compression References: <19970615160250.HK59536@uriah.heep.sax.de> <8425.866584356@nemeton.com.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <8425.866584356@nemeton.com.au>; from Giles Lean on Jun 18, 1997 07:52:36 +1000 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Giles Lean wrote: > > What i didn't like is that they broke compatibility. vdump's output > > is incompatible with dump's. > I've never seen different OSes with compatible dump formats. Did you try it? I have no problems reading an AIX 3.2.5 dump tape on FreeBSD (for an example of something i've tried myself). AIX doesn't even have UFS, and it has a different byte-order. Also, DEC UNIX already offers (BSD) dump for their UFS, so having vdump more incompatible than necessary so both formats cannot be interchanged looks silly. -- 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 Jun 17 23:53:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA02152 for hackers-outgoing; Tue, 17 Jun 1997 23:53:47 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA02147 for ; Tue, 17 Jun 1997 23:53:42 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA13380 for hackers@FreeBSD.ORG; Wed, 18 Jun 1997 08:53:40 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA21857; Wed, 18 Jun 1997 08:47:05 +0200 (MET DST) Message-ID: <19970618084705.BK05243@uriah.heep.sax.de> Date: Wed, 18 Jun 1997 08:47:05 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: floppy, redux References: <19970618015804.2611.qmail@squirrel.tgsoft.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970618015804.2611.qmail@squirrel.tgsoft.com>; from mark thompson on Jun 18, 1997 01:58:04 -0000 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As mark thompson wrote: > I bet you're erroneously using the buffered devices, where you should > use the raw ones, are you? > Well, uhm, no. > But answering your question caused me to discover another thing. It only > seems to fail when it is copying data to/from the wd0 device. I just did > several copies from sd0 and /tmp (mfs), and no problems. Hmmmmm. > Should i perhaps move the wd drive to the OTHER onboard controller? Well, there's enough crappy hardware in the PC world, so it might be worth the while. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Wed Jun 18 00:01:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA02592 for hackers-outgoing; Wed, 18 Jun 1997 00:01:48 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA02587 for ; Wed, 18 Jun 1997 00:01:44 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id QAA20880; Wed, 18 Jun 1997 16:31:36 +0930 (CST) From: Michael Smith Message-Id: <199706180701.QAA20880@genesis.atrad.adelaide.edu.au> Subject: Re: hackers-digest V3 #242 In-Reply-To: <199706180623.QAA03038@polya.blah.org> from Ada T Lim at "Jun 18, 97 04:23:10 pm" To: ada@not-enough.bandwidth.org (Ada T Lim) Date: Wed, 18 Jun 1997 16:31:36 +0930 (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 Ada T Lim stands accused of saying: > > Anyhow, what would be a good way to implement 'setuid libraries'? > (The idea being that all function calls to this library have an > implicit setuid(0) first and a setuid() back afterwards. This discards any state that may be implicit in the user's current priviledge level though, so the library code would have to be paranoid about checking the credentials it was being run with. It's kinda sticky. > Ada -- ]] 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 Jun 18 00:33:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA03603 for hackers-outgoing; Wed, 18 Jun 1997 00:33:49 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA03598 for ; Wed, 18 Jun 1997 00:33:45 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.5/8.8.5) id JAA03544; Wed, 18 Jun 1997 09:33:10 +0200 (SAT) From: John Hay Message-Id: <199706180733.JAA03544@zibbi.mikom.csir.co.za> Subject: Re: Proposed change to struct clockinfo In-Reply-To: <19970615102528.GA34262@uriah.heep.sax.de> from J Wunsch at "Jun 15, 97 10:25:28 am" To: joerg_wunsch@uriah.heep.sax.de Date: Wed, 18 Jun 1997 09:33:09 +0200 (SAT) Cc: hackers@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL31 (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 John Hay wrote: > > > As far as I can tell only 4 other files use the clockinfo structure and > > they will work again after a recompile. They are: > > lib/libc/gmon/gmon.c > > usr.bin/time/time.c > > usr.sbin/kgmon/kgmon.c > > libexec/rpc.rstatd/rstat_proc.c > > > > I would also like to put these in the 2.2 tree after a few days. > > Since you're going to change a file in libc, this would require a > version number update. This is unacceptable for 2.2. Please clarify > in -hackers whether the already bumped minor version number would > suffice (i assume, even though strictly spoken, isn't it an interface > change to an existing library function? -- this would mandate a major > number bump, sigh). > The interface to the library function does not change. The sysctl change and lib/libc/gmon/gmon.c use that, so it will have to be recompiled to work again. So I think the minor version bump that already happened should be enough??? The other programs in the list above use the sysctl direcly and would also have to be recompiled, but I don't think that is a problem??? John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-hackers Wed Jun 18 01:33:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA05588 for hackers-outgoing; Wed, 18 Jun 1997 01:33:54 -0700 (PDT) Received: from sendero.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA05583 for ; Wed, 18 Jun 1997 01:33:50 -0700 (PDT) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.5) id BAA17598 for FreeBSD-Hackers@FreeBSD.org; Wed, 18 Jun 1997 01:33:56 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 18 Jun 1997 01:33:55 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: FreeBSD-Hackers@FreeBSD.org Subject: High Resolution Timers, How? Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi Y'all, I am in need for a precise, high resolution timer within the kernel. I need it to time certain instructions, functions, and I/O events. The best i could find is a global variable called time which claims to have a usec resolution but; Either I am exceptionally lucky and always hit it on a x000000 resolution, or it is not telling the truth. i need a timer that will increment in usec resolution or as close to it as I can get. Any help will be appreciated. Simon From owner-freebsd-hackers Wed Jun 18 01:58:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA06486 for hackers-outgoing; Wed, 18 Jun 1997 01:58:26 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA06481 for ; Wed, 18 Jun 1997 01:58:20 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id SAA21423; Wed, 18 Jun 1997 18:28:13 +0930 (CST) From: Michael Smith Message-Id: <199706180858.SAA21423@genesis.atrad.adelaide.edu.au> Subject: Re: High Resolution Timers, How? In-Reply-To: from Simon Shapiro at "Jun 18, 97 01:33:55 am" To: Shimon@i-Connect.Net (Simon Shapiro) Date: Wed, 18 Jun 1997 18:28:12 +0930 (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 Simon Shapiro stands accused of saying: > > I am in need for a precise, high resolution timer within the kernel. > I need it to time certain instructions, functions, and I/O events. microtime() > Simon -- ]] 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 Jun 18 03:31:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA09824 for hackers-outgoing; Wed, 18 Jun 1997 03:31:40 -0700 (PDT) Received: from relay1.cit.ru (relay1.cit.ru [193.125.82.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA09816 for ; Wed, 18 Jun 1997 03:31:22 -0700 (PDT) Received: from free.tula.su by relay1.cit.ru with UUCP id OAA10773; (8.8.2-MVC-141196/vak/1.9) Wed, 18 Jun 1997 14:35:14 +0400 (MSD) Received: from blik.UUCP by free.tula.su with UUCP id OAA07635; (8.8.2-MVC-141196/vak/1.9) 9b Received: by blik.samara.su id AA08627 (5.65/IDA-simtel for hackers@freebsd.org); Wed, 18 Jun 1997 16:22:27 +0500 To: hackers@freebsd.org Message-Id: Organization: Center of Information Technology From: "Igor" Date: Wed, 18 Jun 97 16:22:27 +0500 X-Mailer: BML [UNIX Beauty Mail v.1.39] Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk help what should I do to subscribe for this mailing list --- igor@blik.samara.su (Igor) From owner-freebsd-hackers Wed Jun 18 03:36:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA10129 for hackers-outgoing; Wed, 18 Jun 1997 03:36:59 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA10118 for ; Wed, 18 Jun 1997 03:36:54 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id LAA19607; Wed, 18 Jun 1997 11:59:14 +0200 From: Luigi Rizzo Message-Id: <199706180959.LAA19607@labinfo.iet.unipi.it> Subject: Re: High Resolution Timers, How? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 18 Jun 1997 11:59:14 +0200 (MET DST) Cc: Shimon@i-Connect.Net, FreeBSD-Hackers@FreeBSD.ORG In-Reply-To: <199706180858.SAA21423@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jun 18, 97 06:27:53 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Simon Shapiro stands accused of saying: > > > > I am in need for a precise, high resolution timer within the kernel. > > I need it to time certain instructions, functions, and I/O events. > > microtime() It is worth mentioning that the Pentium also has an accessible cycle counter, which can be read using the rdtsc asm instruction (or the equivalent rdtsc() function in the kernel). I don't know much about it except, but from what I have read&heard it counts CPU clock cycles, so you have to scale to the actual clock speed of your processor. See /sys/i386/include/cpufunc.h 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 Wed Jun 18 03:41:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA10294 for hackers-outgoing; Wed, 18 Jun 1997 03:41:56 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA10286 for ; Wed, 18 Jun 1997 03:41:45 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id UAA22004; Wed, 18 Jun 1997 20:08:42 +0930 (CST) From: Michael Smith Message-Id: <199706181038.UAA22004@genesis.atrad.adelaide.edu.au> Subject: Re: High Resolution Timers, How? In-Reply-To: <199706180959.LAA19607@labinfo.iet.unipi.it> from Luigi Rizzo at "Jun 18, 97 11:59:14 am" To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Wed, 18 Jun 1997 20:08:42 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, Shimon@i-Connect.Net, 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 Luigi Rizzo stands accused of saying: > > Simon Shapiro stands accused of saying: > > > > > > I am in need for a precise, high resolution timer within the kernel. > > > I need it to time certain instructions, functions, and I/O events. > > > > microtime() > > It is worth mentioning that the Pentium also has an accessible cycle > counter, which can be read using the rdtsc asm instruction (or the > equivalent rdtsc() function in the kernel). microtime() uses it. Ask Bruce if you need to know more 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 Wed Jun 18 04:24:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA11560 for hackers-outgoing; Wed, 18 Jun 1997 04:24:08 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA11553 for ; Wed, 18 Jun 1997 04:24:06 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id FAA19300; Wed, 18 Jun 1997 05:24:03 -0600 (MDT) Message-Id: <199706181124.FAA19300@pluto.plutotech.com> To: Simon Shapiro cc: FreeBSD-Hackers@FreeBSD.ORG Subject: Re: High Resolution Timers, How? In-reply-to: Your message of "Wed, 18 Jun 1997 01:33:55 PDT." Date: Wed, 18 Jun 1997 06:22:47 -0600 From: "Justin T. Gibbs" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Hi Y'all, > >I am in need for a precise, high resolution timer within the kernel. >I need it to time certain instructions, functions, and I/O events. If you only need high resolution "time of day" functionality, use microtime(). >The best i could find is a global variable called time which claims >to have a usec resolution but; Either I am exceptionally lucky and >always hit it on a x000000 resolution, or it is not telling the >truth. i need a timer that will increment in usec resolution or >as close to it as I can get. Were you looking at lbolt? -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hackers Wed Jun 18 04:45:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA12230 for hackers-outgoing; Wed, 18 Jun 1997 04:45:11 -0700 (PDT) Received: from inetfw.sonycsl.co.jp (inetfw.sonycsl.co.jp [203.137.129.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA12223 for ; Wed, 18 Jun 1997 04:45:06 -0700 (PDT) Received: from hotaka.csl.sony.co.jp (hotaka.csl.sony.co.jp [43.27.98.57]) by inetfw.sonycsl.co.jp (8.8.5/3.5W) with ESMTP id UAA17862 for ; Wed, 18 Jun 1997 20:44:59 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by hotaka.csl.sony.co.jp (8.8.4/3.3W3) with ESMTP id UAA16819 for ; Wed, 18 Jun 1997 20:44:44 +0900 (JST) Message-Id: <199706181144.UAA16819@hotaka.csl.sony.co.jp> To: FreeBSD-Hackers@FreeBSD.ORG Subject: Re: High Resolution Timers, How? In-reply-to: Your message of "Wed, 18 Jun 1997 18:28:12 +0930." <199706180858.SAA21423@genesis.atrad.adelaide.edu.au> Date: Wed, 18 Jun 1997 20:44:43 +0900 From: Kenjiro Cho Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Solaris implements gethrtime(get high resolution time) that returns a 64-bit value in nanoseconds since some arbitrary time. Its features are: - simpler and faster - higher resolution - no sec/usec conversion required - no clock adjustment (no time warp) hrtime seems to be an attractive alternative since microtime() is used mostly to measure time delta, and easily implemented by extracting part of microtime(). How about implementing gethrtime in FreeBSD? --kj --- Kenjiro Cho Sony Computer Science Laboratory Inc. From owner-freebsd-hackers Wed Jun 18 04:45:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA12246 for hackers-outgoing; Wed, 18 Jun 1997 04:45:15 -0700 (PDT) Received: from bsd.fs.bauing.th-darmstadt.de (bsd.fs.bauing.th-darmstadt.de [130.83.63.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA12222 for ; Wed, 18 Jun 1997 04:45:02 -0700 (PDT) Received: from campa.panke.de (anonymous213.ppp.cs.tu-berlin.de [130.149.17.213]) by bsd.fs.bauing.th-darmstadt.de (8.8.5/8.8.5) with ESMTP id NAA28276; Wed, 18 Jun 1997 13:44:53 +0200 (MET DST) Received: (from wosch@localhost) by campa.panke.de (8.8.5/8.6.12) id NAA00946; Wed, 18 Jun 1997 13:10:09 +0200 (MET DST) To: rssh@cki.ipri.kiev.ua Cc: hackers@FreeBSD.ORG Subject: Re: setting PATH in skeleton files References: <33A644A0.1981@cki.ipri.kiev.ua> From: Wolfram Schneider Date: 18 Jun 1997 13:10:07 +0200 In-Reply-To: Ruslan Shevchenko's message of Tue, 17 Jun 1997 11:02:39 +0300 Message-ID: Lines: 16 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ruslan Shevchenko writes: > I see phrase > PATH=....... in skeleton files > (i.e. in /usr/share/skel/dot.profile, the same in dot.cshrc) > > In generally it is bad, becouse > system admininstrator can not add new directory in /etc/profile. > for all users. /usr/share/skel/dot.* are general examples which will be override after next update/make world. As a system admin, you should copy /usr/share/skel to /etc/skel and may modify the files in /etc/skel. -- Wolfram Schneider http://www.apfel.de/~wosch/ From owner-freebsd-hackers Wed Jun 18 05:11:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA13159 for hackers-outgoing; Wed, 18 Jun 1997 05:11:00 -0700 (PDT) Received: from pandora.hh.kew.com (kendra.ne.highway1.com [24.128.53.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA13154 for ; Wed, 18 Jun 1997 05:10:56 -0700 (PDT) Received: from fantasy-factory.net.kew.com (uucp@fantasy-factory.net.kew.com [204.96.41.103]) by pandora.hh.kew.com (8.8.5/8.8.5) with ESMTP id IAA01622 for ; Wed, 18 Jun 1997 08:10:19 -0400 (EDT) Received: from kew-sonata.UUCP (uucp@localhost) by fantasy-factory.net.kew.com (8.8.5/8.8.5) with UUCP id IAA02043 for hackers@freebsd.org; Wed, 18 Jun 1997 08:10:16 -0400 (EDT) Received: by sonata.uucp.kew.com (UUPC/extended 1.12s); Tue, 17 Jun 1997 00:24:32 -0500 Message-ID: <33a61180.kew-sonata@sonata.uucp.kew.com> Date: Tue, 17 Jun 1997 00:24:32 -0500 From: "Drew Derbyshire" Organization: Kendra Electronic Wonderworks (PO Box 80144, Stoneham MA 02180) To: hackers@freebsd.org Subject: granting auth to processes Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It's not so much the shared library vs. server which concerns me, but levels of access granted. If every program didn't need full root access to change the effective user, it's not as big a problem. Consider it's the multiple levels of access needed to a set of files: User O can create or delete file Group A can read/write existing files Group B can read existing file Group C can write existing file Others have no access UFS does not allow this in a trivial fashion, because it has a finite number of permission bits. Likewise I somewhat object to a model which only has root/noroot as classes of API access, because it leads to the wrong amount of priv granted. -- Internet: ahd@kew.com Voice: 617-279-9810 "OSI: Same day service in a nano-second world." - Van Jacobson From owner-freebsd-hackers Wed Jun 18 05:51:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA14811 for hackers-outgoing; Wed, 18 Jun 1997 05:51:05 -0700 (PDT) Received: from thorin.hway.ru (flash@thorin.hway.ru [194.87.58.130]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA14800 for ; Wed, 18 Jun 1997 05:50:58 -0700 (PDT) Received: from localhost (flash@localhost) by thorin.hway.ru (8.8.5/8.8.5) with SMTP id QAA18961 for ; Wed, 18 Jun 1997 16:50:14 +0400 (MSD) Date: Wed, 18 Jun 1997 16:50:13 +0400 (MSD) From: "Alexander V. Tischenko" To: freebsd-hackers@FreeBSD.ORG Subject: RFCs and Urgent pointers Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, Anybody thought of adding the RFC style Urgent pointers to the TCP, say, as TCP level socket option ? Alexander V. Tischenko ------------------------------------------------------------------------------ Integrated Network Technologies | Tel: +7 095 978-47-37 7, Miusskaya sq., Moscow, 125047 Russia | Fax: +7 095 978-47-37 Internet: flash@hway.ru | NIC: AT55-RIPE From owner-freebsd-hackers Wed Jun 18 06:13:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA15583 for hackers-outgoing; Wed, 18 Jun 1997 06:13:45 -0700 (PDT) Received: from seagull.rtd.com (seagull.rtd.com [198.102.68.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA15574 for ; Wed, 18 Jun 1997 06:13:42 -0700 (PDT) Received: (from dgy@localhost) by seagull.rtd.com (8.8.5/8.8.5) id GAA27714; Wed, 18 Jun 1997 06:16:13 -0700 (MST) From: Don Yuniskis Message-Id: <199706181316.GAA27714@seagull.rtd.com> Subject: Re: granting auth to processes In-Reply-To: <33a61180.kew-sonata@sonata.uucp.kew.com> from Drew Derbyshire at "Jun 17, 97 00:24:32 am" To: ahd@kew.com (Drew Derbyshire) Date: Wed, 18 Jun 1997 06:16:12 -0700 (MST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 > It's not so much the shared library vs. server which concerns me, but > levels of access granted. If every program didn't need full root access > to change the effective user, it's not as big a problem. > > Consider it's the multiple levels of access needed to a set of files: > > User O can create or delete file > Group A can read/write existing files > Group B can read existing file > Group C can write existing file > Others have no access > > UFS does not allow this in a trivial fashion, because it has a finite > number of permission bits. Likewise I somewhat object to a model which > only has root/noroot as classes of API access, because it leads to the > wrong amount of priv granted. Can you spell MULTICS? --don From owner-freebsd-hackers Wed Jun 18 06:15:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA15654 for hackers-outgoing; Wed, 18 Jun 1997 06:15:51 -0700 (PDT) Received: from caipfs.rutgers.edu (root@caipfs.rutgers.edu [128.6.155.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA15647 for ; Wed, 18 Jun 1997 06:15:48 -0700 (PDT) Received: from jenolan.caipgeneral (jenolan.rutgers.edu [128.6.111.5]) by caipfs.rutgers.edu (8.8.5/8.8.5) with SMTP id JAA01980; Wed, 18 Jun 1997 09:15:46 -0400 (EDT) Received: by jenolan.caipgeneral (SMI-8.6/SMI-SVR4) id JAA06467; Wed, 18 Jun 1997 09:13:40 -0400 Date: Wed, 18 Jun 1997 09:13:40 -0400 Message-Id: <199706181313.JAA06467@jenolan.caipgeneral> From: "David S. Miller" To: flash@hway.ru CC: freebsd-hackers@FreeBSD.ORG, Eric.Schenk@dna.lth.se In-reply-to: (flash@hway.ru) Subject: Re: RFCs and Urgent pointers Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Date: Wed, 18 Jun 1997 16:50:13 +0400 (MSD) From: "Alexander V. Tischenko" Anybody thought of adding the RFC style Urgent pointers to the TCP, say, as TCP level socket option ? We've made this a sysctl() tunable under Linux, I don't think we considered the benefits of making it a socket option, that may in fact be a better approach. Comments? From owner-freebsd-hackers Wed Jun 18 06:39:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA16701 for hackers-outgoing; Wed, 18 Jun 1997 06:39:19 -0700 (PDT) Received: from thorin.hway.ru (flash@thorin.hway.ru [194.87.58.130]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA16477 for ; Wed, 18 Jun 1997 06:33:57 -0700 (PDT) Received: from localhost (flash@localhost) by thorin.hway.ru (8.8.5/8.8.5) with SMTP id RAA20626; Wed, 18 Jun 1997 17:32:16 +0400 (MSD) Date: Wed, 18 Jun 1997 17:32:16 +0400 (MSD) From: "Alexander V. Tischenko" To: "David S. Miller" cc: freebsd-hackers@FreeBSD.ORG, Eric.Schenk@dna.lth.se Subject: Re: RFCs and Urgent pointers In-Reply-To: <199706181313.JAA06467@jenolan.caipgeneral> 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 Jun 1997, David S. Miller wrote: > Date: Wed, 18 Jun 1997 16:50:13 +0400 (MSD) > From: "Alexander V. Tischenko" > > Anybody thought of adding the RFC style Urgent pointers to the TCP, > say, as TCP level socket option ? > > We've made this a sysctl() tunable under Linux, I don't think we > considered the benefits of making it a socket option, that may in fact > be a better approach. Comments? > I suppose it is better to make it an option, 'cause this way you can set it on per-socket basis from your applications. Alexander V. Tischenko ------------------------------------------------------------------------------ Integrated Network Technologies | Tel: +7 095 978-47-37 7, Miusskaya sq., Moscow, 125047 Russia | Fax: +7 095 978-47-37 Internet: flash@hway.ru | NIC: AT55-RIPE From owner-freebsd-hackers Wed Jun 18 06:52:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA17413 for hackers-outgoing; Wed, 18 Jun 1997 06:52:17 -0700 (PDT) Received: from kevin.sunshine.net (pme46.sunshine.net [204.191.205.46]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA17407 for ; Wed, 18 Jun 1997 06:52:13 -0700 (PDT) Received: from localhost (cagey@localhost) by kevin.sunshine.net (8.8.5/8.8.5) with SMTP id GAA00656; Wed, 18 Jun 1997 06:45:58 -0700 (PDT) X-Authentication-Warning: kevin.sunshine.net: cagey owned process doing -bs Date: Wed, 18 Jun 1997 06:45:53 -0700 (PDT) From: Kevin Eliuk X-Sender: cagey@kevin.sunshine.net Reply-To: Kevin Eliuk To: Igor cc: hackers@FreeBSD.ORG Subject: Re: your mail 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 Jun 1997, Igor wrote: > help > what should I do to subscribe for this mailing list > --- > igor@blik.samara.su (Igor) subscribe through majordomo@freebsd.org In message subscribe [
] -- =| Regards, =| FreeBSD ==> http://www.FreeBSD.org =| Kevin G. Eliuk =| "Free at last, free at last, ..." From owner-freebsd-hackers Wed Jun 18 07:11:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA18324 for hackers-outgoing; Wed, 18 Jun 1997 07:11:14 -0700 (PDT) Received: from florence.pavilion.net (mailrelay1.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA18319 for ; Wed, 18 Jun 1997 07:11:11 -0700 (PDT) Received: (from joe@localhost) by florence.pavilion.net (8.8.5/8.8.5) id PAA16550; Wed, 18 Jun 1997 15:10:04 +0100 (BST) Message-ID: <19970618151004.21788@pavilion.net> Date: Wed, 18 Jun 1997 15:10:04 +0100 From: Josef Karthauser To: Drew Derbyshire Cc: hackers@FreeBSD.ORG Subject: Re: granting auth to processes References: <33a61180.kew-sonata@sonata.uucp.kew.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <33a61180.kew-sonata@sonata.uucp.kew.com>; from Drew Derbyshire on Tue, Jun 17, 1997 at 12:24:32AM -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, Jun 17, 1997 at 12:24:32AM -0500, Drew Derbyshire wrote: > > Consider it's the multiple levels of access needed to a set of files: > > User O can create or delete file > Group A can read/write existing files > Group B can read existing file > Group C can write existing file > Others have no access > > UFS does not allow this in a trivial fashion, because it has a finite > number of permission bits. Likewise I somewhat object to a model which > only has root/noroot as classes of API access, because it leads to the > wrong amount of priv granted. One way around it that I've been thinking about might work. Any comments? What if we make a way of allowing groups defined in /etc/groups to contain groups as well as uids? i.e. xrwxrwx--- fred.foo filename User fred and users on group foo can read and write to this file. could /etc/group foo contain: foo:*:1000:joe,fred,'group wheel' This would allow really useful generalisations of group access. i.e. joe and fred and anyone on group wheel can read and write this file. Comments? Joe -- Josef Karthauser Technical Manager Email: joe@pavilion.net Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] From owner-freebsd-hackers Wed Jun 18 07:48:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA20223 for hackers-outgoing; Wed, 18 Jun 1997 07:48:09 -0700 (PDT) Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA19892 for ; Wed, 18 Jun 1997 07:42:51 -0700 (PDT) Received: (babkin@localhost) by hq.icb.chel.su (8.8.3/8.6.5) id UAA01513; Wed, 18 Jun 1997 20:36:03 +0600 (ESD) From: "Serge A. Babkin" Message-Id: <199706181436.UAA01513@hq.icb.chel.su> Subject: Re: C optimizer bug ? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 18 Jun 1997 20:36:03 +0600 (ESD) Cc: hackers@FreeBSD.ORG In-Reply-To: <10918.866346949@time.cdrom.com> from "Jordan K. Hubbard" at Jun 14, 97 08:55:49 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > >I was too lazy to do this but if it's going to give any effect > >I can do it. > > Well, as I said, what you've done so far will generate *no* effect, so > look at this as the only option if causing an effect is what you have > in mind. :) Okay, I have found the trouble and it was mine. The scsi_scsi_cmd() function used splbio() while awaiting the result from adapter while I used Ethernet. After adding splimp() and splnet() the races gone away. -SB From owner-freebsd-hackers Wed Jun 18 08:03:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA21059 for hackers-outgoing; Wed, 18 Jun 1997 08:03:26 -0700 (PDT) Received: from seagull.rtd.com (seagull.rtd.com [198.102.68.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA21052 for ; Wed, 18 Jun 1997 08:03:23 -0700 (PDT) Received: (from dgy@localhost) by seagull.rtd.com (8.8.5/8.8.5) id IAA01834; Wed, 18 Jun 1997 08:05:56 -0700 (MST) From: Don Yuniskis Message-Id: <199706181505.IAA01834@seagull.rtd.com> Subject: Re: granting auth to processes In-Reply-To: <19970618151004.21788@pavilion.net> from Josef Karthauser at "Jun 18, 97 03:10:04 pm" To: joe@pavilion.net (Josef Karthauser) Date: Wed, 18 Jun 1997 08:05:56 -0700 (MST) Cc: ahd@kew.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 In the words of the world-renowned author, Josef Karthauser: > On Tue, Jun 17, 1997 at 12:24:32AM -0500, Drew Derbyshire wrote: > > > > Consider it's the multiple levels of access needed to a set of files: > > > > User O can create or delete file > > Group A can read/write existing files > > Group B can read existing file > > Group C can write existing file > > Others have no access > > > > UFS does not allow this in a trivial fashion, because it has a finite > > number of permission bits. Likewise I somewhat object to a model which > > only has root/noroot as classes of API access, because it leads to the > > wrong amount of priv granted. > > One way around it that I've been thinking about might work. Any comments? > What if we make a way of allowing groups defined in /etc/groups to contain > groups as well as uids? > > i.e. > xrwxrwx--- fred.foo filename > > User fred and users on group foo can read and write to this file. > > could /etc/group foo contain: > foo:*:1000:joe,fred,'group wheel' > > This would allow really useful generalisations of group access. i.e. > joe and fred and anyone on group wheel can read and write this file. Write a perl script to expand group names from a /etc/groups.your_scheme file and recreate the /etc/groups file from this. It, however, doesn't solve the problem posed above... --don From owner-freebsd-hackers Wed Jun 18 08:10:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA21587 for hackers-outgoing; Wed, 18 Jun 1997 08:10:59 -0700 (PDT) Received: from seagull.rtd.com (seagull.rtd.com [198.102.68.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA21582 for ; Wed, 18 Jun 1997 08:10:57 -0700 (PDT) Received: (from dgy@localhost) by seagull.rtd.com (8.8.5/8.8.5) id IAA02167 for freebsd-hackers@freefall.cdrom.com; Wed, 18 Jun 1997 08:13:39 -0700 (MST) From: Don Yuniskis Message-Id: <199706181513.IAA02167@seagull.rtd.com> Subject: Opus diskettes To: freebsd-hackers@freefall.FreeBSD.org (FreeBSD hackers) Date: Wed, 18 Jun 1997 08:13:39 -0700 (MST) X-Mailer: ELM [version 2.4ME+ PL31 (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 Greetings! I know I *started* to write this but can't recall if I ever finished it -- and I don't recall seeing it on the list, so... I'm trying to chase down some man page problems in one of the ports and was going to look through the man pages for another OS I have in a box here. It's a SysV3.2 derivative from Opus Systems (runs on a 32032 coprocessor card). The files appear to be gzipped tarballs with some bogus front-end glued onto them. They are all called OPFIL (on 5" floppies). Was this a SysV-ism? Any clues as to how I can descramble them (short of reinstalling the coprocessor card, etc.)? Thx! --don From owner-freebsd-hackers Wed Jun 18 08:13:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA21759 for hackers-outgoing; Wed, 18 Jun 1997 08:13:57 -0700 (PDT) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA21741; Wed, 18 Jun 1997 08:13:52 -0700 (PDT) Received: from localhost (taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id LAA18204; Wed, 18 Jun 1997 11:13:05 -0400 (EDT) Date: Wed, 18 Jun 1997 11:13:05 -0400 (EDT) From: Brian Tao To: Simon Shapiro cc: FREEBSD-HACKERS , FREEBSD-SCSI Subject: Re: Announcement: New DPT RAID Controller Driver Available In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Jun 1997, Simon Shapiro wrote: > > I have evaluated, tested and even participated in the design of more > than one I/O subsystem in my short life. The StorageWorks solution > is the best I have ever seen. not perfect, Just the BEST. I should add that NetApp also uses the DEC StorageWorks shelves and canisters for their 2GB and 4GB configurations, and if it's good enough for them, it's good enough for me. ;-) Mounting drives inside the canisters is a little tricky at first, but you get the hang of it pretty quickly. The ones we have are plastic, so I imagine the heat dissipation isn't the best. Netapp went with a Eurologics product (metal extruded cases) for their 9GB shelves. -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't" From owner-freebsd-hackers Wed Jun 18 08:18:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA21962 for hackers-outgoing; Wed, 18 Jun 1997 08:18:02 -0700 (PDT) Received: from crowbar.aa.ans.net (crowbar.aa.ans.net [198.83.22.71]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA21957 for ; Wed, 18 Jun 1997 08:18:00 -0700 (PDT) Received: from crowbar.aa.ans.net (markd@localhost) by crowbar.aa.ans.net (8.8.5/8.8.3) with ESMTP id LAA06706; Wed, 18 Jun 1997 11:17:58 -0400 (EDT) Message-Id: <199706181517.LAA06706@crowbar.aa.ans.net> To: hackers@freebsd.org cc: markd@ans.net Subject: Support for 3Com Etherlink III Lan+33.6 Modem PC card Date: Wed, 18 Jun 1997 11:17:58 -0400 From: Mark Davisson Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can someone point me to the correct version which supports this card? It is a multiport card using drivers 3C562C/3C563C. I have version 2.1.5 which looks like it supports the Etherlink III (zp0) but I think the card I have is a new version. Thanks, From owner-freebsd-hackers Wed Jun 18 08:51:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA23420 for hackers-outgoing; Wed, 18 Jun 1997 08:51:14 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA23415 for ; Wed, 18 Jun 1997 08:51:12 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id IAA05829 for ; Wed, 18 Jun 1997 08:50:51 -0700 (PDT) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.8.4/8.8.4) with SMTP id SAA20120; Wed, 18 Jun 1997 18:39:54 +0300 (EEST) Date: Wed, 18 Jun 1997 18:39:54 +0300 (EEST) From: Narvi To: Josef Karthauser cc: Drew Derbyshire , hackers@FreeBSD.ORG Subject: Re: granting auth to processes In-Reply-To: <19970618151004.21788@pavilion.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 18 Jun 1997, Josef Karthauser wrote: > On Tue, Jun 17, 1997 at 12:24:32AM -0500, Drew Derbyshire wrote: > > > > Consider it's the multiple levels of access needed to a set of files: > > > > User O can create or delete file > > Group A can read/write existing files > > Group B can read existing file > > Group C can write existing file > > Others have no access > > > > UFS does not allow this in a trivial fashion, because it has a finite > > number of permission bits. Likewise I somewhat object to a model which > > only has root/noroot as classes of API access, because it leads to the > > wrong amount of priv granted. > > One way around it that I've been thinking about might work. Any comments? > What if we make a way of allowing groups defined in /etc/groups to contain > groups as well as uids? > > i.e. > xrwxrwx--- fred.foo filename > > User fred and users on group foo can read and write to this file. > > could /etc/group foo contain: > foo:*:1000:joe,fred,'group wheel' > Well some time ago (= this year, more than 2 months ago) an idea groped up when talking about ACL-s on the hackers was: Have something like permissionFS, fith directories as groups and files inside them as users belonging to that group. Don't treat subdirectories in any special ways (they are just groups like the parent), who can add new members to a given group depends purely on write permissions on that directory. As there is almost infinite (2^31? with only 1024 users on a system, each can have ~2M groups before running out) number of groups you have suddenly implemented ACLs without changing a single byte of existing filesystem code. The above case the permissions on the directory should be ownerx groupa rwxr-x--- and the file mode would be ownerx groupb rw-rw-r-- where: 1) People who must have read access belong to groupa 2) People who must have read and write access belong to both groupa and groupb Yes, there is the problem with ownerx creating a hard link to it in another directory. Sander PS. I did not think this out. There is no love, no good, no happiness and no future - all these are just illusions. > This would allow really useful generalisations of group access. i.e. > joe and fred and anyone on group wheel can read and write this file. > > Comments? > Joe > -- > Josef Karthauser > Technical Manager Email: joe@pavilion.net > Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] > > From owner-freebsd-hackers Wed Jun 18 09:37:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA26297 for hackers-outgoing; Wed, 18 Jun 1997 09:37:04 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA26291 for ; Wed, 18 Jun 1997 09:36:57 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA04087; Wed, 18 Jun 1997 10:36:48 -0600 (MDT) Date: Wed, 18 Jun 1997 10:36:48 -0600 (MDT) Message-Id: <199706181636.KAA04087@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mark Davisson Cc: hackers@freebsd.org Subject: Re: Support for 3Com Etherlink III Lan+33.6 Modem PC card In-Reply-To: <199706181517.LAA06706@crowbar.aa.ans.net> References: <199706181517.LAA06706@crowbar.aa.ans.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Can someone point me to the correct version which supports this card? Combo cards aren't supported at this time. Nate From owner-freebsd-hackers Wed Jun 18 09:38:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA26395 for hackers-outgoing; Wed, 18 Jun 1997 09:38:52 -0700 (PDT) Received: from smtp1.ts.kiev.ua (viking.ts.kiev.ua [193.124.229.195]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA26114 for ; Wed, 18 Jun 1997 09:34:20 -0700 (PDT) Received: from aviion.ts.kiev.ua by smtp1.ts.kiev.ua with SMTP id SAA25383; (8.8.3/zah/2.1) Wed, 18 Jun 1997 18:39:28 +0300 (EET DST) Received: from nbki.ipri.kiev.ua by aviion.ts.kiev.ua with ESMTP id QAA06183; (8.6.11/zah/2.1) Wed, 18 Jun 1997 16:34:42 GMT Received: from cki.ipri.kiev.ua by nbki.ipri.kiev.ua with ESMTP id SAA24048; (8.6.9/zah/1.1) Wed, 18 Jun 1997 18:08:56 +0100 Received: from 194.44.146.14 (mac.ipri.kiev.ua [194.44.146.14]) by cki.ipri.kiev.ua (8.7.6/8.7.3) with SMTP id SAA00397; Wed, 18 Jun 1997 18:04:51 +0300 (EET DST) Message-ID: <33A7EB47.26C6@cki.ipri.kiev.ua> Date: Wed, 18 Jun 1997 17:05:56 +0300 From: Ruslan Shevchenko Reply-To: rssh@cki.ipri.kiev.ua Organization: IPRI X-Mailer: Mozilla 3.01Gold (Macintosh; I; 68K) MIME-Version: 1.0 To: Wolfram Schneider CC: hackers@FreeBSD.ORG Subject: Re: setting PATH in skeleton files References: <33A644A0.1981@cki.ipri.kiev.ua> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Wolfram Schneider wrote: > > Ruslan Shevchenko writes: > > I see phrase > > PATH=....... in skeleton files > > (i.e. in /usr/share/skel/dot.profile, the same in dot.cshrc) > > > > In generally it is bad, becouse > > system admininstrator can not add new directory in /etc/profile. > > for all users. > > /usr/share/skel/dot.* are general examples which will be override > after next update/make world. As a system admin, you should I understand. ;) But i don't wont to modify default skeletons, It is writen to user profile by adduser, than user can patch it, if he wish. So, after erasing string PATH=, I (and not only I) will receive ecomomy of 1 operation > copy /usr/share/skel to /etc/skel and may modify the files in > /etc/skel. > > -- > Wolfram Schneider http://www.apfel.de/~wosch/ From owner-freebsd-hackers Wed Jun 18 10:00:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA27544 for hackers-outgoing; Wed, 18 Jun 1997 10:00:22 -0700 (PDT) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.96.1.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA27525; Wed, 18 Jun 1997 10:00:18 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.5/8.8.5) with SMTP id NAA02008; Wed, 18 Jun 1997 13:00:11 -0400 (EDT) Date: Wed, 18 Jun 1997 13:00:11 -0400 (EDT) From: "Matthew N. Dodd" To: Brian Tao cc: FREEBSD-HACKERS , FREEBSD-SCSI Subject: Re: Announcement: New DPT RAID Controller Driver Available 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 Jun 1997, Brian Tao wrote: > I should add that NetApp also uses the DEC StorageWorks shelves > and canisters for their 2GB and 4GB configurations, and if it's good > enough for them, it's good enough for me. ;-) Mounting drives FYI NetApp went with the DSW enclosures because DEC had a big surplus of them and gave NetApp a good deal. I've not heard too many good things about DSW. Of course there aren't too many other enclosures that do the same stuff a DSW does. Have a good one. /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ From owner-freebsd-hackers Wed Jun 18 10:18:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA28339 for hackers-outgoing; Wed, 18 Jun 1997 10:18:51 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA28334 for ; Wed, 18 Jun 1997 10:18:49 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA20980; Wed, 18 Jun 1997 10:09:19 -0700 From: Terry Lambert Message-Id: <199706181709.KAA20980@phaeton.artisoft.com> Subject: Re: granting auth to processes To: ahd@kew.com (Drew Derbyshire) Date: Wed, 18 Jun 1997 10:09:19 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <33a61180.kew-sonata@sonata.uucp.kew.com> from "Drew Derbyshire" at Jun 17, 97 00:24:32 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 [ ... he want's ACLs ... ] Why not use ACLs? Seriously, there are a number of people who have asked me questions about data-hiding and name space intrusions for projects like quota FS's, compressing FS's, and ACL FS's. I'm sure at least several of them are close to working code, if not already there. You should ask on the FS list. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jun 18 10:21:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA28462 for hackers-outgoing; Wed, 18 Jun 1997 10:21:39 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA28457 for ; Wed, 18 Jun 1997 10:21:35 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA20993; Wed, 18 Jun 1997 10:12:21 -0700 From: Terry Lambert Message-Id: <199706181712.KAA20993@phaeton.artisoft.com> Subject: Re: hackers-digest V3 #242 To: ada@not-enough.bandwidth.org (Ada T Lim) Date: Wed, 18 Jun 1997 10:12:21 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199706180623.QAA03038@polya.blah.org> from "Ada T Lim" at Jun 18, 97 04:23:10 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 > Anyhow, what would be a good way to implement 'setuid libraries'? (The idea > being that all function calls to this library have an implicit setuid(0) first > and a setuid() back afterwards. You mean "installed images". Generally a "system" priviledge level jammed in between "user" and "kernel". On an Intel, this probably means "ring 1" (kernel is "ring 0" and user is "ring 3"). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jun 18 10:28:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA28773 for hackers-outgoing; Wed, 18 Jun 1997 10:28:06 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA28707 for ; Wed, 18 Jun 1997 10:28:00 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA21035; Wed, 18 Jun 1997 10:18:37 -0700 From: Terry Lambert Message-Id: <199706181718.KAA21035@phaeton.artisoft.com> Subject: Re: Opus diskettes To: dgy@rtd.com (Don Yuniskis) Date: Wed, 18 Jun 1997 10:18:37 -0700 (MST) Cc: freebsd-hackers@freefall.FreeBSD.org In-Reply-To: <199706181513.IAA02167@seagull.rtd.com> from "Don Yuniskis" at Jun 18, 97 08:13:39 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm trying to chase down some man page problems in one of > the ports and was going to look through the man pages for another > OS I have in a box here. It's a SysV3.2 derivative from Opus > Systems (runs on a 32032 coprocessor card). The files appear > to be gzipped tarballs with some bogus front-end glued onto > them. They are all called OPFIL (on 5" floppies). > Was this a SysV-ism? Any clues as to how I can > descramble them (short of reinstalling the coprocessor card, etc.)? > Thx! dd if=/dev/floppy skip=4k conv=swab of=file_without_VTOC You may not need the "conv=swab", depending on the box you are running on. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jun 18 10:50:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA29866 for hackers-outgoing; Wed, 18 Jun 1997 10:50:50 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA29854 for ; Wed, 18 Jun 1997 10:50:47 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA00684 for ; Wed, 18 Jun 1997 10:40:35 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd000678; Wed Jun 18 17:40:26 1997 Message-ID: <33A81D49.15FB7483@whistle.com> Date: Wed, 18 Jun 1997 10:39:21 -0700 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: [Fwd: Re: AFP 2.2 Rev8] Content-Type: multipart/mixed; boundary="------------3F54BC7E1CFBAE3959E2B600" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. --------------3F54BC7E1CFBAE3959E2B600 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Someone in the FreeBSD community was talking about doing this. but I can't remember who. Anyone remember? julian --------------3F54BC7E1CFBAE3959E2B600 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Return-Path: Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id IAA26021 for ; Wed, 18 Jun 1997 08:32:09 -0700 (PDT) Received: from whistle.whistle.com(207.76.205.131), claiming to be "whistle.com" via SMTP by alpo.whistle.com, id smtpd026017; Wed Jun 18 15:32:06 1997 Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id IAA00860; Wed, 18 Jun 1997 08:32:04 -0700 (PDT) Received: from gatekeeper.whistle.com(207.76.204.2) by whistle.com via smap (V1.3) id sma000858; Wed Jun 18 08:31:46 1997 Received: (from smap@localhost) by gatekeeper.whistle.com (8.7.5/8.6.12) id IAA10889; Wed, 18 Jun 1997 08:31:46 -0700 (PDT) Received: from terminator.rs.itd.umich.edu(141.211.164.2) by gatekeeper.whistle.com via smap (V1.3) id sma010887; Wed Jun 18 08:31:26 1997 Received: from localhost by terminator.rs.itd.umich.edu (8.8.5/2.3) with SMTP id KAA22007; Wed, 18 Jun 1997 10:58:09 -0400 (EDT) Received: by terminator.rs.itd.umich.edu (bulk_mailer v1.5+); Wed, 18 Jun 1997 10:57:49 -0400 Received: by terminator.rs.itd.umich.edu (8.8.5/2.3) id KAA21943; Wed, 18 Jun 1997 10:57:48 -0400 (EDT) Received: from judgmentday.rs.itd.umich.edu by terminator.rs.itd.umich.edu (8.8.5/2.3) with ESMTP id KAA21929; Wed, 18 Jun 1997 10:57:42 -0400 (EDT) Received: by judgmentday.rs.itd.umich.edu (8.8.5/2.2) with X.500 id KAA03113; Wed, 18 Jun 1997 10:57:41 -0400 (EDT) Received: by judgmentday.rs.itd.umich.edu (8.8.5/2.2) with X.500 id KAA03066; Wed, 18 Jun 1997 10:57:34 -0400 (EDT) Received: from iglou1 by judgmentday.rs.itd.umich.edu (8.8.5/2.2) with SMTP id KAA03010; Wed, 18 Jun 1997 10:57:24 -0400 (EDT) Received: from mfreeman by iglou1 with smtp (8.7.3/8.6.12) id 0weMAi-0001AD-00; Wed, 18 Jun 1997 10:57:20 -0400 Date: Wed, 18 Jun 1997 10:57:20 -0400 (EDT) From: "Michael M. Freeman" X-Sender: mfreeman@iglou1 To: Bernard Becker cc: netatalk-admins@umich.edu Subject: Re: AFP 2.2 Rev8 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-netatalk-admins@terminator.rs.itd.umich.edu On Wed, 18 Jun 1997, Bernard Becker wrote: > Apple has recently finished beta testing AppleShare IP 5.0, our new > AppleShare file server implementation. > [BIG SNIP] > > Are there any plans from the developers and maintainers to incorporate this > new spec into netatalk? > Greetings Bernard, There are actually two "unofficial" implementations of AFP-over-TCP for netatalk. One is the "netatalk-2.0a6" distribution from Adrian Sun of washington.edu and the other is my more modest "afptcpd-0.1a3" distribution. The "netatalk-2.0a6" dist. is a major revision of 1.4b2 that incorporates AFP 2.2 (including AFP-over-TCP) into afpd. The "afptcpd" dist. is an add-on (separate daemon) to 1.4b2. Both run under Linux 2.0.x/2.1.x and SunOS 4.1.x. ARGGGG Pager just went off. To be continued...... Mike Freeman --------------3F54BC7E1CFBAE3959E2B600-- From owner-freebsd-hackers Wed Jun 18 11:00:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA00619 for hackers-outgoing; Wed, 18 Jun 1997 11:00:32 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA00614 for ; Wed, 18 Jun 1997 11:00:30 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA01116 for ; Wed, 18 Jun 1997 10:52:36 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd001110; Wed Jun 18 17:52:27 1997 Message-ID: <33A82019.FF6D5DF@whistle.com> Date: Wed, 18 Jun 1997 10:51:21 -0700 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: Adding a new feature to 2.2 series? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Whistle communications is one of the major users and maintainers of the ipfw and diversion code. (we wrote the latter and have helped maintian the former) We also have based our product around the 2.2 family of FreeBSD. We have added significant functionality to the ipfw code in -curremt but would like to have this same functionality in the version we actually use for the product. (i.e. 2.2 series) There is an interface change involved in the ipfw changes, but the command-line view remains compatible. The question is whether this is acceptable in 2.2 considering the limited use of this interface. I'd like to back-port the -current changes to 2.2. While we presently have a system that allows us to selectively use our own files instead of those coming in from freebsd.org, that does have problems in some ways and we'd rather keep such things to a minimum. If there are no objections, I'd like to merge in the changes from -current (now several weeks old) into 2.2 (actually I'd directly import our 2.2 based patches that have been in testing for several months now.) If there are violent objections please speak up now!! I'll try to address any problems that are raised.. julian. From owner-freebsd-hackers Wed Jun 18 11:05:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA00849 for hackers-outgoing; Wed, 18 Jun 1997 11:05:28 -0700 (PDT) Received: from fyeung5 (netific.vip.best.com [205.149.182.145]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA00841 for ; Wed, 18 Jun 1997 11:05:13 -0700 (PDT) Received: from fyeung8.netific.com (fyeung8 [204.238.125.8]) by fyeung5 (8.6.11/8.6.9) with SMTP id WAA11633 for ; Tue, 17 Jun 1997 22:55:42 -0700 Received: by fyeung8.netific.com (5.x/SMI-SVR4) id AA16829; Wed, 18 Jun 1997 10:55:51 -0700 Date: Wed, 18 Jun 1997 10:55:51 -0700 From: fyeung@fyeung8.netific.com (Francis Yeung) Message-Id: <9706181755.AA16829@fyeung8.netific.com> To: hackers@freebsd.org Subject: RiscBSD speed X-Sun-Charset: US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, See below. FYI. Francis ----- Begin Included Message ----- >From root@fyeung25.netific.com Tue Jun 17 23:52 PDT 1997 Date: Wed, 18 Jun 1997 00:32:01 +0100 From: Peter Teichmann To: port-arm32@NetBSD.ORG Subject: RiscBSD speed X-Posting-Agent: RISC OS Newsbase 0.59 Delivered-To: port-arm32@NetBSD.ORG Hi, some days ago I compiled lmbench for RiscBSD and got the following results. I added some other computers for comparison: L M B E N C H 1 . 0 S U M M A R Y ------------------------------------ Processor, Processes - times in microseconds -------------------------------------------- Host OS Mhz Null Null Simple /bin/sh Mmap 2-proc 8-proc Syscall Process Process Process lat ctxsw ctxsw --------- ------------- ---- ------- ------- ------- ------- ---- ------ ------ Strongarm NetBSD 1.2D 215 5 38K 59K 279K 1763 855 1276 Arm610/33 NetBSD 1.2D 31 80 25K 38K 166K 843 251 390 i586 FreeBSD 2.1-S 100 7 3K 13K 21K 173 29 35 i586 Linux 1.2.13 100 3 3K 24K 73K 84 66 83 pa-risc HP-UX A.09.01 98 13 3K 10K 20K 97 29 30 sgi IRIX5.3 5.3 198 11 3K 8K 19K 260 40 38 alpha OSF1 V3.2 189 15 5K 15K 89K 261 40 46 *Local* Communication latencies in microseconds ----------------------------------------------- Host OS Pipe UDP RPC/ TCP RPC/ UDP TCP --------- ------------- ------- ------- ------- ------- ------- Strongarm NetBSD 1.2D 1839 13888 15810 13986 14424 Arm610/33 NetBSD 1.2D 1669 14104 17791 14783 15887 i586 FreeBSD 2.1-S 115 249 408 297 510 i586 Linux 1.2.13 140 -1 806 -1 1249 pa-risc HP-UX A.09.01 169 248 759 257 805 sgi IRIX5.3 5.3 131 313 671 278 641 alpha OSF1 V3.2 198 709 1109 629 994 *Local* Communication bandwidths in megabytes/second ---------------------------------------------------- Host OS Pipe TCP File Mmap Bcopy Bcopy Mem Mem reread reread (libc) (hand) read write --------- ------------- ---- ---- ------ ------ ------ ------ ---- ----- Strongarm NetBSD 1.2D 2 3 1 4 16 2 36 23 Arm610/33 NetBSD 1.2D 2 1 1 5 10 0 13 23 i586 FreeBSD 2.1-S 18 0 29 50 41 38 65 83 i586 Linux 1.2.13 12 3 13 8 21 20 60 31 pa-risc HP-UX A.09.01 44 20 44 33 26 32 53 49 sgi IRIX5.3 5.3 34 22 32 44 32 31 69 66 alpha OSF1 V3.2 23 7 37 12 38 38 64 79 Memory latencies in nanoseconds (WARNING - may not be correct, check graphs) -------------------------------------------- Host OS Mhz L1 $ L2 $ Main mem Guesses --------- ------------- --- ---- ---- -------- ------- Strongarm NetBSD 1.2D 214 5 720 740 No L2 cache? Arm610/33 NetBSD 1.2D 31 61 551 548 No L2 cache? i586 FreeBSD 2.1-S 99 10 101 180 i586 Linux 1.2.13 99 10 222 321 pa-risc HP-UX A.09.01 98 10 10 348 No L1 cache? sgi IRIX5.3 5.3 197 10 76 1018 alpha OSF1 V3.2 188 10 53 477 You can see that memory access is not too fast, but this is because of the lame rpc main board. It is much worse that context switching, communication latencies and bandwiths are very bad compared with other systems. Sometimes the Arm610 is faster than the Strongarm, I guess this is because of cache flushing or even switching off on Strongarm. But also the Arm610 is not too fast, it is even very slow, and there is not always the cache flushed or switched off. So my question is: is this because RiscBSD is not very optimized (so this could become better some day) or is it because of some other reason? Peter Teichmann ----- End Included Message ----- From owner-freebsd-hackers Wed Jun 18 11:18:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA01486 for hackers-outgoing; Wed, 18 Jun 1997 11:18:37 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA01479 for ; Wed, 18 Jun 1997 11:18:35 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.5/8.7.3) with SMTP id LAA12886 for ; Wed, 18 Jun 1997 11:18:31 -0700 (PDT) Date: Wed, 18 Jun 1997 11:18:30 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: update question. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does update only affect UFS operations? If I have nfs set to async, will update sync it up? From owner-freebsd-hackers Wed Jun 18 11:48:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA03088 for hackers-outgoing; Wed, 18 Jun 1997 11:48:34 -0700 (PDT) Received: from ecsl.cs.sunysb.edu (sequoia.cs.sunysb.edu [130.245.14.12]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA03079 for ; Wed, 18 Jun 1997 11:48:26 -0700 (PDT) Received: (from yifeng@localhost) by ecsl.cs.sunysb.edu (8.6.12/8.6.9) id OAA15814 for freebsd-hackers@FreeBSD.org; Wed, 18 Jun 1997 14:48:15 -0400 From: Yi-feng Li Message-Id: <199706181848.OAA15814@ecsl.cs.sunysb.edu> Subject: no subject (file transmission) To: freebsd-hackers@FreeBSD.org Date: Wed, 18 Jun 1997 14:48:14 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Dear Sir, My name is Yi-Feng Li. I am a graduate student, studying in the SUNY at Stony Brook. Currently, I am doing my master project about IP Firewall on the BSD 2.1.6. To do this project, I have to modify the kernel source code. My major job is working on the /sys/netinet/ directory. According to the lack of knowledge and experience, I have getten some problems and can not solve. I hope you can help me. My problems are as followings: 1) How to get the system time and user time, used by a process, in the kernel? I have tried to use getrusage() function in the /sys/kern/kern_resource.c, but it won't work. I can not reboot the machine successfully. I bet I have done something wrong; neither this is not a good way to do it nor I do not use it currectly. 2) How to open a file and write messages into the file in the kernel? Your help will be appreciated!! Thanks!! Yi-Feng Li yifeng@ecsl.cs.sunysb.edu From owner-freebsd-hackers Wed Jun 18 11:57:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA03582 for hackers-outgoing; Wed, 18 Jun 1997 11:57:23 -0700 (PDT) Received: from phantasm.scl.ameslab.gov (phantasm.scl.ameslab.gov [147.155.142.74]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA03577 for ; Wed, 18 Jun 1997 11:57:19 -0700 (PDT) Received: (from ccsanady@localhost) by phantasm.scl.ameslab.gov (8.6.12/8.6.12) id SAA05367; Wed, 18 Jun 1997 18:57:13 GMT From: "Chris Csanady" Message-Id: <9706181357.ZM5365@phantasm.scl.ameslab.gov> Date: Wed, 18 Jun 1997 13:57:12 -0500 X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: hackers@freebsd.org Subject: Network concurrency problems!? Cc: matt@3am-software.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Some background.. I have 2 ppro200 machines running 2.2.2 with 4 back to back full duplex 100Mbps connections. (and 2 10Mbps connections to a real network.) These are all SMC 10/100 cards, using Matt's 960603 drivers. I am concurrently running NetPIPE over each of the links. It tests TCP, using a range of increasing block sizes. (info at http://www.scl.ameslab.gov/netpipe) I don't know if this is a generic problem or driver specific, but when I have 2-4 cards in a machine, I am only able to saturate one link with larger transfer sizes. With 4 cards, at approx 6k, and 16k, two of the pipes are completely starved. The last runs about 10Mbps slower. Also, there appear to be hundreds of thousands of collisions on a couple of the interfaces. (This should be impossible, correct?) Anyways, is this possibly a PCI int sharing problem, or some odd livelock situation being encountered? How exactly would I go about tracking this down? Chris Csanady From owner-freebsd-hackers Wed Jun 18 12:02:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA03775 for hackers-outgoing; Wed, 18 Jun 1997 12:02:10 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA03767 for ; Wed, 18 Jun 1997 12:02:04 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wePwl-0002xR-00; Wed, 18 Jun 1997 11:59:11 -0700 Date: Wed, 18 Jun 1997 11:59:11 -0700 (PDT) From: Tom Samplonius To: Francis Yeung cc: hackers@freebsd.org Subject: Re: RiscBSD speed In-Reply-To: <9706181755.AA16829@fyeung8.netific.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 18 Jun 1997, Francis Yeung wrote: > > > Greetings, > > See below. FYI. > > Francis > [ bunch of lmbench results for mostly obscure platforms deleted ] This was hardly relevant to the freebsd-hackers list. FreeBSD doesn't run on most of those platforms. Plus, the benchmarks were run on FreeBSD 2.1, but which 2.1? 2.1.0, 2.1.5, 2.1.6, 2.1.7? Besides 2.2 is known to benchmark (with lmbench) much faster than 2.1. Tom From owner-freebsd-hackers Wed Jun 18 12:04:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA03945 for hackers-outgoing; Wed, 18 Jun 1997 12:04:11 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA03935 for ; Wed, 18 Jun 1997 12:04:04 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id PAA01930; Wed, 18 Jun 1997 15:05:17 -0400 Date: Wed, 18 Jun 1997 15:05:16 -0400 (EDT) From: Ben Black To: Don Yuniskis cc: Drew Derbyshire , hackers@FreeBSD.ORG Subject: Re: granting auth to processes In-Reply-To: <199706181316.GAA27714@seagull.rtd.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 actually, this is a feature of any true capabilities-based system. On Wed, 18 Jun 1997, Don Yuniskis wrote: > > It's not so much the shared library vs. server which concerns me, but > > levels of access granted. If every program didn't need full root access > > to change the effective user, it's not as big a problem. > > > > Consider it's the multiple levels of access needed to a set of files: > > > > User O can create or delete file > > Group A can read/write existing files > > Group B can read existing file > > Group C can write existing file > > Others have no access > > > > UFS does not allow this in a trivial fashion, because it has a finite > > number of permission bits. Likewise I somewhat object to a model which > > only has root/noroot as classes of API access, because it leads to the > > wrong amount of priv granted. > > Can you spell MULTICS? > > --don > From owner-freebsd-hackers Wed Jun 18 12:06:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA04079 for hackers-outgoing; Wed, 18 Jun 1997 12:06:24 -0700 (PDT) Received: from numachi.numachi.com (numachi.numachi.com [198.175.254.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA04063 for ; Wed, 18 Jun 1997 12:06:16 -0700 (PDT) Received: (from reichert@localhost) by numachi.numachi.com (8.6.12/8.6.12) id PAA28190; Wed, 18 Jun 1997 15:06:06 -0400 Message-ID: <19970618150605.51823@numachi.numachi.com> Date: Wed, 18 Jun 1997 15:06:05 -0400 From: Brian Reichert To: freebsd-hackers@freebsd.org Subject: atapi CD drive wedging Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.68 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hidy-ho, folks. I've pawed through the mail archives, but didn't see any clear pointers on this one, so here goes: I have a NEC 272 CD ROM drive, that probes at boot, and works well. But I've noticed two set of symptoms: - my console gets clogged with '/kernel: wcd0: cannot read audio disc' messages. What is directing the kernel to try, when I'm not running xcdplayer, or the like? - Inevitably, I will see this after a couple of hours of using the drive: Jun 5 12:52:06 aobrien /kernel: atapi1.0: unknown phase Jun 5 12:52:06 aobrien /kernel: wcd0: i/o error, status=0, error=1 after which the drive is not accessable via software, as the incurring process blocks forwever, and cannot be KILLed. Is there a way of 'unwedging' the drive, so I can make further use of it? I suppose my biggest problem, is that this all begins a death spiral, where suddenly various processes hang, so badly that I cannot even log in remotely to straighten things out. I've been using FreeBSD for a couple of years now, and this is the first time I've had userland processes wedge a machine to the point of forcing a complete restart. Does anyone have any observations on this whole mess? Thanks for your time... -- Brian 'you Bastard' Reichert reichert@numachi.com 37 Crystal Ave. #303 Derry NH 03038-1713 USA Intel architecture: the left-hand path From owner-freebsd-hackers Wed Jun 18 12:10:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA04321 for hackers-outgoing; Wed, 18 Jun 1997 12:10:24 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA04316 for ; Wed, 18 Jun 1997 12:10:16 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id PAA01948; Wed, 18 Jun 1997 15:08:43 -0400 Date: Wed, 18 Jun 1997 15:08:43 -0400 (EDT) From: Ben Black To: Terry Lambert cc: Drew Derbyshire , hackers@FreeBSD.ORG Subject: Re: granting auth to processes In-Reply-To: <199706181709.KAA20980@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk because ACLs are generally pretty heavyweight and in my experience with NT tremendously easy to misconfigure. i am a big fan of capabilities because they are only marginally more complex than traditional UNIX permissions, while allowing arbitrary levels of access control. On Wed, 18 Jun 1997, Terry Lambert wrote: > [ ... he want's ACLs ... ] > > Why not use ACLs? > > Seriously, there are a number of people who have asked me questions > about data-hiding and name space intrusions for projects like quota > FS's, compressing FS's, and ACL FS's. I'm sure at least several of > them are close to working code, if not already there. You should > ask on the FS list. > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > From owner-freebsd-hackers Wed Jun 18 12:26:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA05301 for hackers-outgoing; Wed, 18 Jun 1997 12:26:53 -0700 (PDT) Received: from pandora.hh.kew.com (kendra.ne.highway1.com [24.128.53.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA05294 for ; Wed, 18 Jun 1997 12:26:47 -0700 (PDT) Received: (from ahd@localhost) by pandora.hh.kew.com (8.8.5/8.8.5) id PAA04006; Wed, 18 Jun 1997 15:26:15 -0400 (EDT) Date: Wed, 18 Jun 1997 15:26:15 -0400 (EDT) From: Drew Derbyshire Message-Id: <199706181926.PAA04006@pandora.hh.kew.com> To: hackers@FreeBSD.ORG, julian@whistle.com Subject: Re: Adding a new feature to 2.2 series? Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk If you're hacking the code, add a wish for the ipfw command line side, although not for 2.2.x ... Consider parsing the port and IP address fields for the contents of /etc/services, /etc/hosts and /etc/network. I find the requirement to use numerics to be extremely error prone. I presume this is currently done because NIS and DNS are not presumed to be available when ipfw is run and the stock gethostbyname, etc. would attempt to access these services. So think about it ... -ahd- From owner-freebsd-hackers Wed Jun 18 13:19:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA08822 for hackers-outgoing; Wed, 18 Jun 1997 13:19:06 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA08811 for ; Wed, 18 Jun 1997 13:18:56 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 3668 invoked by uid 1001); 18 Jun 1997 20:18:38 +0000 (GMT) To: ccsanady@scl.ameslab.gov Cc: hackers@FreeBSD.ORG, matt@3am-software.com Subject: Re: Network concurrency problems!? In-Reply-To: Your message of "Wed, 18 Jun 1997 13:57:12 -0500" References: <9706181357.ZM5365@phantasm.scl.ameslab.gov> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 18 Jun 1997 22:18:38 +0200 Message-ID: <3666.866665118@verdi.nethelp.no> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Some background.. I have 2 ppro200 machines running 2.2.2 with 4 back > to back full duplex 100Mbps connections. (and 2 10Mbps connections to > a real network.) These are all SMC 10/100 cards, using Matt's 960603 > drivers. I am concurrently running NetPIPE over each of the links. It > tests TCP, using a range of increasing block sizes. (info at > http://www.scl.ameslab.gov/netpipe) > > I don't know if this is a generic problem or driver specific, but when I > have 2-4 cards in a machine, I am only able to saturate one link with > larger transfer sizes. With 4 cards, at approx 6k, and 16k, two of the > pipes are completely starved. The last runs about 10Mbps slower. Also, > there appear to be hundreds of thousands of collisions on a couple of the > interfaces. (This should be impossible, correct?) Collisions are a sign that your interfaces are *not* running full duplex. Also, if you expect a PPro-200 to saturate 4 100 Mbps links, I think you are a wee bit optimistic. (One link, no problem.) Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Wed Jun 18 13:24:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA09272 for hackers-outgoing; Wed, 18 Jun 1997 13:24:03 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA09201 for ; Wed, 18 Jun 1997 13:23:42 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0weRCY-0002zn-00; Wed, 18 Jun 1997 13:19:34 -0700 Date: Wed, 18 Jun 1997 13:19:33 -0700 (PDT) From: Tom Samplonius To: Chris Csanady cc: hackers@freebsd.org, matt@3am-software.com Subject: Re: Network concurrency problems!? In-Reply-To: <9706181357.ZM5365@phantasm.scl.ameslab.gov> 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 Jun 1997, Chris Csanady wrote: ... > there appear to be hundreds of thousands of collisions on a couple of the > interfaces. (This should be impossible, correct?) ... Collisions on a full duplex connection? How exactly are you making these full-duplex connections between the two systems? Tom From owner-freebsd-hackers Wed Jun 18 13:35:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA09777 for hackers-outgoing; Wed, 18 Jun 1997 13:35:01 -0700 (PDT) Received: from phantasm.scl.ameslab.gov (phantasm.scl.ameslab.gov [147.155.142.74]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA09763 for ; Wed, 18 Jun 1997 13:34:58 -0700 (PDT) Received: (from ccsanady@localhost) by phantasm.scl.ameslab.gov (8.6.12/8.6.12) id UAA05453; Wed, 18 Jun 1997 20:34:50 GMT From: "Chris Csanady" Message-Id: <9706181534.ZM5451@phantasm.scl.ameslab.gov> Date: Wed, 18 Jun 1997 15:34:49 -0500 In-Reply-To: sthaug@nethelp.no "Re: Network concurrency problems!?" (Jun 18, 10:18pm) References: <9706181357.ZM5365@phantasm.scl.ameslab.gov> <3666.866665118@verdi.nethelp.no> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: sthaug@nethelp.no Subject: Re: Network concurrency problems!? 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 On Jun 18, 10:18pm, sthaug@nethelp.no wrote: > Subject: Re: Network concurrency problems!? > > Some background.. I have 2 ppro200 machines running 2.2.2 with 4 back > > to back full duplex 100Mbps connections. (and 2 10Mbps connections to > > a real network.) These are all SMC 10/100 cards, using Matt's 960603 > > drivers. I am concurrently running NetPIPE over each of the links. It > > tests TCP, using a range of increasing block sizes. (info at > > http://www.scl.ameslab.gov/netpipe) > > > > I don't know if this is a generic problem or driver specific, but when I > > have 2-4 cards in a machine, I am only able to saturate one link with > > larger transfer sizes. With 4 cards, at approx 6k, and 16k, two of the > > pipes are completely starved. The last runs about 10Mbps slower. Also, > > there appear to be hundreds of thousands of collisions on a couple of the > > interfaces. (This should be impossible, correct?) > > Collisions are a sign that your interfaces are *not* running full duplex. The cards say they are full duplex. The little light is on.. A switch also tells me the same if I plug them in. > Also, if you expect a PPro-200 to saturate 4 100 Mbps links, I think you > are a wee bit optimistic. (One link, no problem.) I don't expect it to. Although.. I am concerned that when one is saturated, no packets go through the others. This is a Bad Thing(tm).. Chris From owner-freebsd-hackers Wed Jun 18 13:51:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA10520 for hackers-outgoing; Wed, 18 Jun 1997 13:51:19 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA10510 for ; Wed, 18 Jun 1997 13:51:05 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0weRe6-00030S-00; Wed, 18 Jun 1997 13:48:02 -0700 Date: Wed, 18 Jun 1997 13:48:01 -0700 (PDT) From: Tom Samplonius To: sthaug@nethelp.no cc: ccsanady@scl.ameslab.gov, hackers@freebsd.org, matt@3am-software.com Subject: Re: Network concurrency problems!? In-Reply-To: <3666.866665118@verdi.nethelp.no> 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 Jun 1997 sthaug@nethelp.no wrote: .. > Also, if you expect a PPro-200 to saturate 4 100 Mbps links, I think you > are a wee bit optimistic. (One link, no problem.) Why? As long as the ethernet hw is fast, is should be no problem. I can run 2 FW SCSI channels saturated (2 x 20MB/s * 8 = 320mbs), and the system isn't even working too hard yet. Certainly, full-duplex connections double the total possible bandwidth (4 x 100 x 2 = 800mbs), but most servers are mainly outbound. However, I really doubt whether most ethernet adapters offload enough functions from the main CPU. The trend is to make very stupid controllers, which are slaved to the CPU for everything. > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > Tom From owner-freebsd-hackers Wed Jun 18 13:54:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA10648 for hackers-outgoing; Wed, 18 Jun 1997 13:54:27 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA10642 for ; Wed, 18 Jun 1997 13:54:16 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.5/8.7.3) id WAA04370; Wed, 18 Jun 1997 22:47:52 +0200 (MEST) From: Søren Schmidt Message-Id: <199706182047.WAA04370@sos.freebsd.dk> Subject: Re: atapi CD drive wedging In-Reply-To: <19970618150605.51823@numachi.numachi.com> from Brian Reichert at "Jun 18, 97 03:06:05 pm" To: reichert@numachi.numachi.com (Brian Reichert) Date: Wed, 18 Jun 1997 22:47:52 +0200 (MEST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Brian Reichert who wrote: > Hidy-ho, folks. > > I have a NEC 272 CD ROM drive, that probes at boot, and works well. > But I've noticed two set of symptoms: What version of FreeBSD are you using ??? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Wed Jun 18 14:12:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA11441 for hackers-outgoing; Wed, 18 Jun 1997 14:12:20 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA11363 for ; Wed, 18 Jun 1997 14:11:59 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 4915 invoked by uid 1001); 18 Jun 1997 21:11:54 +0000 (GMT) To: tom@sdf.com Cc: ccsanady@scl.ameslab.gov, hackers@FreeBSD.ORG, matt@3am-software.com Subject: Re: Network concurrency problems!? In-Reply-To: Your message of "Wed, 18 Jun 1997 13:48:01 -0700 (PDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 18 Jun 1997 23:11:54 +0200 Message-ID: <4913.866668314@verdi.nethelp.no> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Also, if you expect a PPro-200 to saturate 4 100 Mbps links, I think you > > are a wee bit optimistic. (One link, no problem.) > > Why? As long as the ethernet hw is fast, is should be no problem. It's a problem because of the resource usage of the TCP/IP stack and the driver. The FreeBSD TCP/IP stack is good, but it's not the most efficient. As far as I know, there is still an extra pass over the data to perform the TCP checksum, for instance. > I > can run 2 FW SCSI channels saturated (2 x 20MB/s * 8 = 320mbs), and the > system isn't even working too hard yet. Certainly, full-duplex > connections double the total possible bandwidth (4 x 100 x 2 = 800mbs), > but most servers are mainly outbound. > > However, I really doubt whether most ethernet adapters offload enough > functions from the main CPU. The trend is to make very stupid > controllers, which are slaved to the CPU for everything. There has been a good deal of debate on whether offloading is really the best idea for network protocol implementations. A lot of people have tried it, and a lot of people have failed. If you look at Van Jacobson't work you'll find him arguing in the opposite direction: A "stupid" (in reality: simple and efficient) controller, and a very efficient protocol stack implementation. See http://ee.lbl.gov/nrg-talks.html, in particular "Some Design Issues for High-speed Networks" and "Design Changes to the Kernel Network Architecture for 4.4BSD" Also "The Witless Interface", presented at the 1991 Gigabit Workshop. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Wed Jun 18 14:17:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA11624 for hackers-outgoing; Wed, 18 Jun 1997 14:17:11 -0700 (PDT) Received: from gwu.ericy.com (gwu.ericy.com [208.196.3.162]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA11606; Wed, 18 Jun 1997 14:17:07 -0700 (PDT) Received: (from uucp@localhost) by gwu.ericy.com (8.8.2/8.8.2) id QAA23519; Wed, 18 Jun 1997 16:12:33 -0500 (CDT) Received: from mr1.exu.ericsson.com(138.85.147.11) by gwu.ericy.com via smap (3.2) id xma023514; Wed, 18 Jun 97 16:12:27 -0500 Received: from noah.lmc.ericsson.se (noah.lmc.ericsson.se [142.133.1.1]) by mr1.exu.ericsson.se (8.7.1/NAHUB-MR1.1) with ESMTP id QAA07239; Wed, 18 Jun 1997 16:15:09 -0500 (CDT) Received: from jello.lmc.ericsson.se (jello.lmc.ericsson.se [142.133.28.34]) by noah.lmc.ericsson.se (8.8.5/8.8.5) with ESMTP id RAA16869; Wed, 18 Jun 1997 17:15:07 -0400 (EDT) Received: from localhost (lmcsato@localhost) by jello.lmc.ericsson.se (8.8.5/8.8.3) with SMTP id RAA24023; Wed, 18 Jun 1997 17:15:04 -0400 (EDT) X-Authentication-Warning: jello.lmc.ericsson.se: lmcsato owned process doing -bs Date: Wed, 18 Jun 1997 17:15:03 -0400 (EDT) From: Samy Touati To: freebsd-questions@freebsd.org cc: freebsd-hackers@freebsd.org Subject: SMC 9332BDT doesn't work on 2.2.2 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I installed fbsd 2.2.2 on a compaq with a pentium pro 180. I used a 3com 905 ethernet card which worked at 10mb but not on 100, because I wanted 100mb speed I changed the card to an SMC 9332BDT. The card is detected correctly but as soon as it's detected the card goes down (the LED goes down). I can't access the machine with this card. When detecting the card a message says: enabling the 100TX even if I it to a 10Mb link. Any ideas? Is this card supported or do I have to get a patch. Any help is appreciated. Thanks. Samy From owner-freebsd-hackers Wed Jun 18 14:19:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA11778 for hackers-outgoing; Wed, 18 Jun 1997 14:19:57 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA11751; Wed, 18 Jun 1997 14:19:51 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0weS8a-0002m7-00; Wed, 18 Jun 1997 15:19:32 -0600 To: Nate Williams Subject: Re: dump/restore with compression Cc: Brandon Gillespie , freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org In-reply-to: Your message of "Thu, 12 Jun 1997 15:40:16 MDT." <199706122140.PAA12271@rocky.mt.sri.com> References: <199706122140.PAA12271@rocky.mt.sri.com> Date: Wed, 18 Jun 1997 15:19:32 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Does anybody USE dump/restore anymore? Every night. Well, I use dump a whole lot more often than restore :-) Or at least my computer, dedicated deciple of The Church Of The Daily Backup, does. Come over sometime and see my Exabyte Shrine to this same church :-) Warner From owner-freebsd-hackers Wed Jun 18 14:45:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA13132 for hackers-outgoing; Wed, 18 Jun 1997 14:45:23 -0700 (PDT) Received: from mail.cei.net (mail.cei.net [204.117.117.29]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA12562 for ; Wed, 18 Jun 1997 14:35:00 -0700 (PDT) Received: from smtp.dancooks.com (smtp.dancooks.com [204.180.122.4]) by mail.cei.net (8.8.5/8.6.9) with SMTP id QAA03795 for ; Wed, 18 Jun 1997 16:34:34 -0500 (CDT) Received: from T2/SpoolDir by smtp.dancooks.com (Mercury 1.12); Wed, 18 Jun 97 16:33:14 -0600 Received: from SpoolDir by T2 (Mercury 1.30); 18 Jun 97 16:32:54 -0600 From: "Jason Hudgins" Organization: Dan Cook's Inc. To: hackers@freebsd.org Date: Wed, 18 Jun 1997 16:32:46 -0600 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: RSA5 Encryption Cracked.. Priority: normal X-mailer: Pegasus Mail for Windows (v2.42a) Message-ID: <11F12637A8E@smtp.dancooks.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Heya, I just thought some of you might be happy to know that the Deschall project just successfully cracked an RC5 encrypted message with a 56 bit key. The really cool thing is that it was one of the 1-2% machines that was running FreeBSD! The majority of the machines hacking away cpu cylces were running windows and solaris. They found the key after searching through only 25% of the keyspace. Even though it was really just a matter of luck, I still that it was pretty cool. Jason Jason L. Hudgins Dan Cook's Web Hacker Type Person office email: hudginsj@smtp.dancooks.com home email: jasonh@cei.net http://www.dancooks.com/~jason From owner-freebsd-hackers Wed Jun 18 15:10:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA14659 for hackers-outgoing; Wed, 18 Jun 1997 15:10:53 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA14642 for ; Wed, 18 Jun 1997 15:10:50 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id SAA05128; Wed, 18 Jun 1997 18:12:26 -0400 Date: Wed, 18 Jun 1997 18:12:24 -0400 (EDT) From: Ben Black To: Jason Hudgins cc: hackers@FreeBSD.ORG Subject: Re: RSA5 Encryption Cracked.. In-Reply-To: <11F12637A8E@smtp.dancooks.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 are you certain it was the 56-bit challenge? i don't think we went through 25% of the keyspace...and their announcement said that globally 50% of the keyspace was exhausted... On Wed, 18 Jun 1997, Jason Hudgins wrote: > Heya, > I just thought some of you might be happy to know that the > Deschall project just successfully cracked an RC5 encrypted message > with a 56 bit key. The really cool thing is that it was one of the > 1-2% machines that was running FreeBSD! The majority of the > machines hacking away cpu cylces were running windows and solaris. > They found the key after searching through only 25% of the > keyspace. Even though it was really just a matter of luck, I still > that it was pretty cool. > > Jason > > > Jason L. Hudgins > Dan Cook's Web Hacker Type Person > office email: hudginsj@smtp.dancooks.com > home email: jasonh@cei.net > http://www.dancooks.com/~jason > From owner-freebsd-hackers Wed Jun 18 15:20:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA15365 for hackers-outgoing; Wed, 18 Jun 1997 15:20:23 -0700 (PDT) Received: from mars.aros.net (mars.aros.net [207.173.16.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA15358 for ; Wed, 18 Jun 1997 15:20:20 -0700 (PDT) Received: from shell.aros.net (root@shell.aros.net [207.173.16.19]) by mars.aros.net (8.8.5/8.8.4) with ESMTP id QAA17740; Wed, 18 Jun 1997 16:12:27 -0600 (MDT) Received: from shell.aros.net (msanders@localhost.aros.net [127.0.0.1]) by shell.aros.net (8.8.5/8.8.5) with ESMTP id QAA00811; Wed, 18 Jun 1997 16:20:18 -0600 (MDT) Message-Id: <199706182220.QAA00811@shell.aros.net> X-Attribution: msanders To: "Jason Hudgins" cc: hackers@FreeBSD.ORG Subject: Re: RSA5 Encryption Cracked.. In-reply-to: Your message of "Wed, 18 Jun 1997 16:32:46 MDT." <11F12637A8E@smtp.dancooks.com> X-Mailer: MH 6.8.3 Date: Wed, 18 Jun 1997 16:20:17 -0600 From: "Michael K. Sanders" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <11F12637A8E@smtp.dancooks.com>, "Jason Hudgins" writes: > > I just thought some of you might be happy to know that the >Deschall project just successfully cracked an RC5 encrypted message >with a 56 bit key. The really cool thing is that it was one of the >1-2% machines that was running FreeBSD! The majority of the >machines hacking away cpu cylces were running windows and solaris. > They found the key after searching through only 25% of the >keyspace. Even though it was really just a matter of luck, I still >that it was pretty cool. Just to clarify, it was a 56-bit _DES_ encrypted message [1]. ...and I think it's even cooler. [1]: "Strong cryptography makes the world a safer place." From owner-freebsd-hackers Wed Jun 18 15:27:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA15836 for hackers-outgoing; Wed, 18 Jun 1997 15:27:54 -0700 (PDT) Received: from pandora.hh.kew.com (kendra.ne.highway1.com [24.128.53.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA15817; Wed, 18 Jun 1997 15:27:48 -0700 (PDT) Received: (from ahd@localhost) by pandora.hh.kew.com (8.8.5/8.8.5) id SAA04672; Wed, 18 Jun 1997 18:26:42 -0400 (EDT) Date: Wed, 18 Jun 1997 18:26:42 -0400 (EDT) From: Drew Derbyshire Message-Id: <199706182226.SAA04672@pandora.hh.kew.com> To: imp@village.org, nate@mt.sri.com Subject: Re: dump/restore with compression Cc: brandon@ice.cold.org, freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As matter of fact, just last night I made the mistake of installing the BIN dist when I was adding X11 to the system. As the system was only a week old, I had not set up backups yet (after three years of nightly tape backups under the previous OS) ... ... did you know that the BIN dist also (re)loads /etc for free? The system _will_ now backup via dump the root partition to a second drive every night -- after I tweak it tonight, I'll have incrementals for a week and weekly full backups going back a month. (I had week's worth setup before I went to bed last night.) I'll further add tape or Zip-drive later. Woe to the system that does not bow to an avatar of data recovery. -ahd- From owner-freebsd-hackers Wed Jun 18 15:58:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA17230 for hackers-outgoing; Wed, 18 Jun 1997 15:58:46 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA17217 for ; Wed, 18 Jun 1997 15:58:42 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id TAA05919; Wed, 18 Jun 1997 19:00:15 -0400 Date: Wed, 18 Jun 1997 19:00:13 -0400 (EDT) From: Ben Black To: "Michael K. Sanders" cc: Jason Hudgins , hackers@FreeBSD.ORG Subject: Re: RSA5 Encryption Cracked.. In-Reply-To: <199706182220.QAA00811@shell.aros.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 yes, i suspected it was the DES crack effort, and yes it is even cooler. this is excellent ammunition for lifting export restrictions (assuming the clinton administration doesn't shove kerrey's bill through). On Wed, 18 Jun 1997, Michael K. Sanders wrote: > In message <11F12637A8E@smtp.dancooks.com>, "Jason Hudgins" writes: > > > > I just thought some of you might be happy to know that the > >Deschall project just successfully cracked an RC5 encrypted message > >with a 56 bit key. The really cool thing is that it was one of the > >1-2% machines that was running FreeBSD! The majority of the > >machines hacking away cpu cylces were running windows and solaris. > > They found the key after searching through only 25% of the > >keyspace. Even though it was really just a matter of luck, I still > >that it was pretty cool. > > Just to clarify, it was a 56-bit _DES_ encrypted message [1]. > > ...and I think it's even cooler. > > [1]: "Strong cryptography makes the world a safer place." > From owner-freebsd-hackers Wed Jun 18 16:33:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA19093 for hackers-outgoing; Wed, 18 Jun 1997 16:33:16 -0700 (PDT) Received: from agni.nuko.com ([206.79.130.80]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA19076; Wed, 18 Jun 1997 16:33:13 -0700 (PDT) Received: (from vinay@localhost) by agni.nuko.com (8.8.5/8.7.3) id QAA20371; Wed, 18 Jun 1997 16:32:21 -0700 (PDT) From: Vinay Bannai Message-Id: <199706182332.QAA20371@agni.nuko.com> Subject: Problems with my sounblaster 16 To: freebsd-hackers@freebsd.org, freebsd-multimedia@freebsd.org Date: Wed, 18 Jun 1997 16:32:20 -0700 (PDT) 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 folks I had my soundblaster card working perfectly ok on my 2.1.5 and then I upgraded to 2.2.2 (cvsup from cvsup.freebsd.org) and it stops working. My machine Pentium Pro, 200Mhz, running 2.2.2-RELEASE with soundblaster 16 The config file has the following line for my soundcard controller snd0 device sb0 at isa? port 0x220 irq 7 conflicts drq 1 vector sbintr device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 I also made sure there are no conflicts with my lpt port (in fact I commented out the lpt support). I also disabled lpt port in my BIOS. I tried it at irq 5 also but to no avail. The sound plays intermittently (half a second at a time) and then finally freezes after a while. I get the following message in my /var/log/messages /kernel: Sound: DMA timed out - IRQ/DRQ config error? Can anyone help me out? Thanks Vinay -- Vinay Bannai E-mail: vinay@agni.nuko.com (408)-526-0280 x 275 (Work) http://agni.nuko.com/~vinay From owner-freebsd-hackers Wed Jun 18 16:42:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA19501 for hackers-outgoing; Wed, 18 Jun 1997 16:42:12 -0700 (PDT) Received: from watermarkgroup.com (lor.watermarkgroup.com [38.246.139.30]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA19495 for ; Wed, 18 Jun 1997 16:42:10 -0700 (PDT) Received: by watermarkgroup.com (4.1/SMI-4.1) id AA25334; Wed, 18 Jun 97 19:32:00 EDT Date: Wed, 18 Jun 97 19:32:00 EDT From: luoqi@watermarkgroup.com (Luoqi Chen) Message-Id: <9706182332.AA25334@watermarkgroup.com> To: yifeng@ecsl.cs.sunysb.edu Subject: Re: no subject (file transmission) Cc: hackers@FreeBSD.Org Sender: owner-hackers@FreeBSD.Org X-Loop: FreeBSD.org Precedence: bulk > 1) How to get the system time and user time, used by a process, in the kernel? > I have tried to use getrusage() function in the /sys/kern/kern_resource.c, > but it won't work. I can not reboot the machine successfully. I bet I > have done something wrong; neither this is not a good way to do it nor I do > not use it currectly. Do not call getrusage(), call calcru() instead, struct timeval utime, stime, itime; struct proc *p; ... calcru(p, &utime, &stime, &itime); ... > 2) How to open a file and write messages into the file in the kernel? To open a file, char *path; struct vnode *vp; struct nameidata nd; struct proc *p; int error; NDINIT(&nd, LOOKUP, FOLLOW, UIO_USERSPACE, path, p); error = vn_open(&nd, O_CREAT|FWRITE, 0644); if (error) { } vp = nd.ni_vp; VOP_UNLOCK(vp); keep the vp around, that's your handle to the file. To close it, error = vn_close(vp, FWRITE, p->p_ucred, p); To write to it, error = vn_rdwr(UIO_WRITE, vp, buf, len, 0, UIO_SYSSPACE, IO_APPEND|IO_UNIT, p->ucred, (int *)0, p); From owner-freebsd-hackers Wed Jun 18 16:59:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA20324 for hackers-outgoing; Wed, 18 Jun 1997 16:59:13 -0700 (PDT) Received: from merix.merix.com (merix.merix.com [198.145.172.40]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA20304 for ; Wed, 18 Jun 1997 16:59:11 -0700 (PDT) Received: from sandy.merix.com by merix.merix.com with SMTP (1.38.110.45/16.2) id AA087278985; Wed, 18 Jun 1997 17:09:45 -0700 Received: by sandy.merix.com (4.1/8.0) id AA03890; Wed, 18 Jun 97 16:55:20 PDT Date: Wed, 18 Jun 97 16:55:20 PDT Subject: Status on LS-120 drive support? To: freebsd-hackers@freebsd.org From: Troy Curtiss Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Anybody out there using those LS-120 drives yet? I think they are IDE-interfaced. Looks like they hold 120MB and can read old floppies (1.44M) too. If they are going to be supported (or going to be commercially successful), they look like a better deal than the Iomega Zip drives. Any thoughts? -Troy -- /-----------------------------------------------------------\ | Troy Curtiss, HW/SW Engineer | Email: troyc@merix.com | | Merix Corporation, CL-302 | Phone: (970) 203-6643 | | Loveland, CO 80537 | Fax : (970) 203-6610 | \-----------------------------------------------------------/ From owner-freebsd-hackers Wed Jun 18 17:35:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA22122 for hackers-outgoing; Wed, 18 Jun 1997 17:35:23 -0700 (PDT) Received: (from jmb@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA22116; Wed, 18 Jun 1997 17:35:18 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199706190035.RAA22116@hub.freebsd.org> Subject: Re: dump/restore with compression To: freebsd-hackers@freebsd.org Date: Wed, 18 Jun 1997 17:35:18 -0700 (PDT) Cc: nate@mt.sri.com, brandon@ice.cold.org, freebsd-questions@freebsd.org In-Reply-To: from "Warner Losh" at Jun 18, 97 03:19:32 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Does anybody USE dump/restore anymore? yes. elizabeth zwicky wrote a usenix paper about torture testing backup methids (dump, tar, cpio). dump was the most reliable of the group. jmb ps. dont user compression. if the data is valuable enough to backup its valuable enough to backup reliably. From owner-freebsd-hackers Wed Jun 18 18:00:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA23013 for hackers-outgoing; Wed, 18 Jun 1997 18:00:01 -0700 (PDT) Received: from pandora.hh.kew.com (kendra.ne.highway1.com [24.128.53.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA22972; Wed, 18 Jun 1997 17:59:55 -0700 (PDT) Received: (from ahd@localhost) by pandora.hh.kew.com (8.8.5/8.8.5) id UAA05638; Wed, 18 Jun 1997 20:58:43 -0400 (EDT) Date: Wed, 18 Jun 1997 20:58:43 -0400 (EDT) From: Drew Derbyshire Message-Id: <199706190058.UAA05638@pandora.hh.kew.com> To: freebsd-hackers@FreeBSD.ORG, jmb@FreeBSD.ORG Subject: Re: dump/restore with compression Cc: brandon@ice.cold.org, freebsd-questions@FreeBSD.ORG, nate@mt.sri.com Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > ps. dont use compression. if the data is valuable enough to backup > its valuable enough to backup reliably. This implies compression is not reliable. I can't say much for UNIX backups, but in general I've never had hardware or software compression screw up worse than any other hardware/software combination. I believe in compression because it encourages backups by reducing the media needed, cutting both media cost and time spent swapping volumes. Less media per megabyte up also reduces the chances of an I/O error on media, so compressed backups can be more reliable than uncompressed. Like anything to do with backups, test and then test again. -ahd- From owner-freebsd-hackers Wed Jun 18 18:00:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA23110 for hackers-outgoing; Wed, 18 Jun 1997 18:00:28 -0700 (PDT) Received: from kalypso.cybercom.net (kalypso.cybercom.net [209.21.136.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA23085; Wed, 18 Jun 1997 18:00:18 -0700 (PDT) Received: from shell1.cybercom.net (ksmm@shell1.cybercom.net [209.21.136.6]) by kalypso.cybercom.net (8.8.5/8.8.5) with ESMTP id UAA08016; Wed, 18 Jun 1997 20:09:55 -0400 (EDT) Received: from localhost (ksmm@localhost) by shell1.cybercom.net (8.8.5/8.8.5) with SMTP id UAA05401; Wed, 18 Jun 1997 20:37:01 -0400 (EDT) Date: Wed, 18 Jun 1997 20:37:01 -0400 (EDT) From: The Classiest Man Alive To: Troy Curtiss cc: freebsd-hackers@FreeBSD.ORG, chat@FreeBSD.ORG Subject: Re: Status on LS-120 drive support? (moving to chat...) 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 Jun 1997, Troy Curtiss wrote: : Anybody out there using those LS-120 drives yet? I think they : are IDE-interfaced. Looks like they hold 120MB and can read old : floppies (1.44M) too. If they are going to be supported (or going : to be commercially successful), they look like a better deal than : the Iomega Zip drives. Any thoughts? The drives look like they could be a match for the Iomega Zip (especially with 20% more storage space), but they have some catching up to do. Iomega has shipped more than one million Zip drives to date, far more than any other similar drive. The media is everywhere--computer stores, office supply stores, technical bookstores. And we all know somebody that has one, so they're well-tested and great for exchanging with friends. Remember the EZ-135? They were supposed to be technically superior to the Zip, too (35% more space, 50% faster, etc.), but weak marketing, shipping delays and reliability problems have all but made those things extinct. It's hard to overturn such a "well-established" market. But if you decide to go that route, let me know how it works out. K.S. From owner-freebsd-hackers Wed Jun 18 18:19:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA24204 for hackers-outgoing; Wed, 18 Jun 1997 18:19:47 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA24195 for ; Wed, 18 Jun 1997 18:19:43 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0weVqE-00037F-00; Wed, 18 Jun 1997 18:16:50 -0700 Date: Wed, 18 Jun 1997 18:16:49 -0700 (PDT) From: Tom Samplonius To: sthaug@nethelp.no cc: ccsanady@scl.ameslab.gov, hackers@freebsd.org, matt@3am-software.com Subject: Re: Network concurrency problems!? In-Reply-To: <4913.866668314@verdi.nethelp.no> 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 Jun 1997 sthaug@nethelp.no wrote: > > > Also, if you expect a PPro-200 to saturate 4 100 Mbps links, I think you > > > are a wee bit optimistic. (One link, no problem.) > > > > Why? As long as the ethernet hw is fast, is should be no problem. > > It's a problem because of the resource usage of the TCP/IP stack and the > driver. > > The FreeBSD TCP/IP stack is good, but it's not the most efficient. As far > as I know, there is still an extra pass over the data to perform the TCP > checksum, for instance. Would a TCP socket have more system overhead than a file on a UFS filesystem? I guess you can tess this by running dd on a mfs, and tcpblast/netpipe/ttcp on loopback? Somehow I think the socket would be faster. ... > > However, I really doubt whether most ethernet adapters offload enough > > functions from the main CPU. The trend is to make very stupid > > controllers, which are slaved to the CPU for everything. > > There has been a good deal of debate on whether offloading is really the > best idea for network protocol implementations. A lot of people have tried > it, and a lot of people have failed. If you look at Van Jacobson't work > you'll find him arguing in the opposite direction: A "stupid" (in reality: > simple and efficient) controller, and a very efficient protocol stack > implementation. Not really what I was refering to. I was thinking about controllers that minimize interupt calls, use DMA, avoid PIO, and align data transfered to the host. Tom From owner-freebsd-hackers Wed Jun 18 18:30:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA24869 for hackers-outgoing; Wed, 18 Jun 1997 18:30:05 -0700 (PDT) Received: (from jmb@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA24820; Wed, 18 Jun 1997 18:29:55 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199706190129.SAA24820@hub.freebsd.org> Subject: Re: dump/restore with compression To: ahd@kew.com (Drew Derbyshire) Date: Wed, 18 Jun 1997 18:29:55 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG, jmb@FreeBSD.ORG, brandon@ice.cold.org, freebsd-questions@FreeBSD.ORG, nate@mt.sri.com In-Reply-To: <199706190058.UAA05638@pandora.hh.kew.com> from "Drew Derbyshire" at Jun 18, 97 08:58:43 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Drew Derbyshire wrote: > > > ps. dont use compression. if the data is valuable enough to backup > > its valuable enough to backup reliably. > > This implies compression is not reliable. I can't say much for > UNIX backups, but in general I've never had hardware or software > compression screw up worse than any other hardware/software > combination. the danger with compression is that a single bit error can destory the entire backup. (note the _can_ it does not have to be this way. block compression in place of streaming compression may not fail catastrophicly. > I believe in compression because it encourages backups by reducing > the media needed, cutting both media cost and time spent swapping > volumes. Less media per megabyte up also reduces the chances of > an I/O error on media, so compressed backups can be more reliable > than uncompressed. get a tape backup device that can store everything. you dont have to do a level 0 every night ;) > > Like anything to do with backups, test and then test again. Amen brother! From owner-freebsd-hackers Wed Jun 18 18:57:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA26127 for hackers-outgoing; Wed, 18 Jun 1997 18:57:33 -0700 (PDT) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA26120 for ; Wed, 18 Jun 1997 18:57:29 -0700 (PDT) Message-Id: <199706190157.SAA26120@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA169985011; Thu, 19 Jun 1997 11:50:11 +1000 From: Darren Reed Subject: Re: Status on LS-120 drive support? To: troyc@sandy.merix.com (Troy Curtiss) Date: Thu, 19 Jun 1997 11:50:11 +1000 (EST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Troy Curtiss" at Jun 18, 97 04:55:20 pm 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 Troy Curtiss, sie said: > > Anybody out there using those LS-120 drives yet? I think they > are IDE-interfaced. Looks like they hold 120MB and can read old > floppies (1.44M) too. If they are going to be supported (or going > to be commercially successful), they look like a better deal than > the Iomega Zip drives. Any thoughts? The LS-120 has two *heads* - one for current floppies and one for the new format. It is a plug-in replacement for floppy drives apparently. It may even work without a new driver (just diff. geometry) ? From owner-freebsd-hackers Wed Jun 18 18:58:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA26206 for hackers-outgoing; Wed, 18 Jun 1997 18:58:38 -0700 (PDT) Received: from seagull.rtd.com (seagull.rtd.com [198.102.68.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA26201 for ; Wed, 18 Jun 1997 18:58:36 -0700 (PDT) Received: (from dgy@localhost) by seagull.rtd.com (8.8.5/8.8.5) id SAA09351; Wed, 18 Jun 1997 18:59:25 -0700 (MST) From: Don Yuniskis Message-Id: <199706190159.SAA09351@seagull.rtd.com> Subject: Re: Opus diskettes In-Reply-To: <199706181718.KAA21035@phaeton.artisoft.com> from Terry Lambert at "Jun 18, 97 10:18:37 am" To: terry@lambert.org (Terry Lambert) Date: Wed, 18 Jun 1997 18:59:25 -0700 (MST) Cc: dgy@rtd.com, freebsd-hackers@freefall.FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL31 (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 In the words of the world-renowned author, Terry Lambert: > > I'm trying to chase down some man page problems in one of > > the ports and was going to look through the man pages for another > > OS I have in a box here. It's a SysV3.2 derivative from Opus > > Systems (runs on a 32032 coprocessor card). The files appear > > to be gzipped tarballs with some bogus front-end glued onto > > them. They are all called OPFIL (on 5" floppies). > > Was this a SysV-ism? Any clues as to how I can > > descramble them (short of reinstalling the coprocessor card, etc.)? > > dd if=/dev/floppy skip=4k conv=swab of=file_without_VTOC Hmmm... perhaps you meant ^^ "8" since skip expects # of blocks as an argument? In either case, this doesn't cut the mustard :-( I looked through a few other OPFIL's and they *don't* appear to be compressed. For example, one contained /etc/.profile which was entirely readable. Perhaps just a tape archive with some bogus crap on the front end? file(1) sees them as "data" (BFD!) > You may not need the "conv=swab", depending on the box you are > running on. Thx! --don From owner-freebsd-hackers Wed Jun 18 18:58:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA26262 for hackers-outgoing; Wed, 18 Jun 1997 18:58:57 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA26242; Wed, 18 Jun 1997 18:58:53 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0weWRz-00038P-00; Wed, 18 Jun 1997 18:55:51 -0700 Date: Wed, 18 Jun 1997 18:55:50 -0700 (PDT) From: Tom Samplonius To: The Classiest Man Alive cc: Troy Curtiss , freebsd-hackers@freebsd.org, chat@freebsd.org Subject: Re: Status on LS-120 drive support? (moving to chat...) 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 Jun 1997, The Classiest Man Alive wrote: ... > any other similar drive. The media is everywhere--computer stores, office > supply stores, technical bookstores. And we all know somebody that has > one, so they're well-tested and great for exchanging with friends. ... Don't forget that Zip is available is a SCSI version, which makes it usable on non-intel systems like Mac, Sparc, and SGI. I don't believe that an IDE-only solution will take off for this reason. Tom From owner-freebsd-hackers Wed Jun 18 20:32:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA01605 for hackers-outgoing; Wed, 18 Jun 1997 20:32:19 -0700 (PDT) Received: from whizzo.TransSys.COM (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA01511 for ; Wed, 18 Jun 1997 20:32:02 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.TransSys.COM (8.8.5/8.7.3) with SMTP id XAA00910; Wed, 18 Jun 1997 23:31:10 -0400 (EDT) Message-Id: <199706190331.XAA00910@whizzo.TransSys.COM> X-Mailer: exmh version 2.0delta 6/3/97 To: "Alexander V. Tischenko" cc: "David S. Miller" , freebsd-hackers@FreeBSD.ORG, Eric.Schenk@dna.lth.se From: "Louis A. Mamakos" Subject: Re: RFCs and Urgent pointers References: In-reply-to: Your message of "Wed, 18 Jun 1997 17:32:16 +0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Jun 1997 23:31:09 -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Wed, 18 Jun 1997, David S. Miller wrote: > > > Date: Wed, 18 Jun 1997 16:50:13 +0400 (MSD) > > From: "Alexander V. Tischenko" > > > > Anybody thought of adding the RFC style Urgent pointers to the TCP, > > say, as TCP level socket option ? > > > > We've made this a sysctl() tunable under Linux, I don't think we > > considered the benefits of making it a socket option, that may in fact > > be a better approach. Comments? > > > I suppose it is better to make it an option, 'cause this way you can set > it on per-socket basis from your applications. TCP urgent data is how the socket out-of-band-data abstraction is realized. I don't understand what else you might "add" to TCP to do "Urgent Pointers". There ought to already be a option for "inline" out-of-band data, which I think is the default in most modern BSD-based TCPs. louie From owner-freebsd-hackers Wed Jun 18 21:22:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA04295 for hackers-outgoing; Wed, 18 Jun 1997 21:22:37 -0700 (PDT) Received: from caipfs.rutgers.edu (root@caipfs.rutgers.edu [128.6.155.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA04290 for ; Wed, 18 Jun 1997 21:22:34 -0700 (PDT) Received: from jenolan.caipgeneral (jenolan.rutgers.edu [128.6.111.5]) by caipfs.rutgers.edu (8.8.5/8.8.5) with SMTP id AAA21282; Thu, 19 Jun 1997 00:22:07 -0400 (EDT) Received: by jenolan.caipgeneral (SMI-8.6/SMI-SVR4) id AAA07058; Thu, 19 Jun 1997 00:20:01 -0400 Date: Thu, 19 Jun 1997 00:20:01 -0400 Message-Id: <199706190420.AAA07058@jenolan.caipgeneral> From: "David S. Miller" To: louie@TransSys.COM CC: flash@hway.ru, freebsd-hackers@FreeBSD.ORG, Eric.Schenk@dna.lth.se In-reply-to: <199706190331.XAA00910@whizzo.TransSys.COM> (louie@TransSys.COM) Subject: Re: RFCs and Urgent pointers Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: "Louis A. Mamakos" Date: Wed, 18 Jun 1997 23:31:09 -0400 > > Anybody thought of adding the RFC style Urgent pointers to the TCP, > > say, as TCP level socket option ? TCP urgent data is how the socket out-of-band-data abstraction is realized. I don't understand what else you might "add" to TCP to do "Urgent Pointers". There ought to already be a option for "inline" out-of-band data, which I think is the default in most modern BSD-based TCPs. The issue is not to add anything, but rather to allow, on a configurable basis, one to choose between the RFC sanctioned interpretation of where the urgent pointer "points" and the traditional one. Read the RFC for details 8-) Later, David "Sparc" Miller davem@caip.rutgers.edu From owner-freebsd-hackers Wed Jun 18 22:40:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA07675 for hackers-outgoing; Wed, 18 Jun 1997 22:40:09 -0700 (PDT) Received: from sabrina.watermarkgroup.com (ppp-2.ts-1.ptn.idt.net [169.132.64.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA07611 for ; Wed, 18 Jun 1997 22:39:56 -0700 (PDT) Received: (from luoqi@localhost) by sabrina.watermarkgroup.com (8.8.5/8.6.12) id BAA11739 for hackers@FreeBSD.Org; Thu, 19 Jun 1997 01:39:51 -0400 (EDT) Date: Thu, 19 Jun 1997 01:39:51 -0400 (EDT) From: Luoqi Chen Message-Id: <199706190539.BAA11739@sabrina.watermarkgroup.com> To: hackers@FreeBSD.Org Subject: ld -T bug Sender: owner-hackers@FreeBSD.Org X-Loop: FreeBSD.org Precedence: bulk I tried to link an executable at a start address other than the default, with dynamical binding, by passing -T flag to ld. Though I won't be able to run it with exec system call, but I could mmap it in a loader program and jump to the start address. The link was successful, but it seemed that ld had written RSS section at the wrong offset in the executable file, it was written as if the start address was still the default. So ld.so won't see them at expected location and results in a segmentation fault. This problem goes away when binding statically (e.g. building the kernel) as there is no RSS section. I have attached a fix for this problem. Could anyone commit this to the CVS tree? Thanks. Index: rrs.c =================================================================== RCS file: /fun/cvs/src/gnu/usr.bin/ld/rrs.c,v retrieving revision 1.17 diff -u -r1.17 rrs.c --- rrs.c 1996/10/01 01:22:35 1.17 +++ rrs.c 1997/06/19 05:08:25 @@ -947,7 +947,11 @@ if (rrs_section_type == RRS_NONE) return; +#if 0 pos = rrs_data_start + (N_DATOFF(outheader) - DATA_START(outheader)); +#else + pos = N_DATOFF(outheader); +#endif if (fseek(outstream, pos, SEEK_SET) != 0) err(1, "write_rrs_data: fseek"); @@ -996,7 +1000,11 @@ if (rrs_section_type == RRS_PARTIAL) return; +#if 0 pos = rrs_text_start + (N_TXTOFF(outheader) - TEXT_START(outheader)); +#else + pos = rrs_text_start + (N_TXTOFF(outheader) - text_start); +#endif if (fseek(outstream, pos, SEEK_SET) != 0) err(1, "write_rrs_text: fseek"); From owner-freebsd-hackers Wed Jun 18 22:40:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA07752 for hackers-outgoing; Wed, 18 Jun 1997 22:40:50 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA07739 for ; Wed, 18 Jun 1997 22:40:45 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA05957 for freebsd-hackers@freefall.FreeBSD.org; Wed, 18 Jun 1997 21:30:23 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id VAA23308; Wed, 18 Jun 1997 21:14:39 +0200 (MET DST) Message-ID: <19970618211439.NU46112@uriah.heep.sax.de> Date: Wed, 18 Jun 1997 21:14:39 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freefall.FreeBSD.org Subject: Re: Opus diskettes References: <199706181513.IAA02167@seagull.rtd.com> <199706181718.KAA21035@phaeton.artisoft.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de-noreply (Joerg Wunsch) In-Reply-To: <199706181718.KAA21035@phaeton.artisoft.com>; from Terry Lambert on Jun 18, 1997 10:18:37 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > dd if=/dev/floppy skip=4k conv=swab of=file_without_VTOC ^^^^^^^ This would IMHO skip 4k blocks = 2048 * 512 bytes. Is this what you want? :-) (The default bs is 512 bytes, and skip is measured in bs.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Wed Jun 18 22:43:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA07895 for hackers-outgoing; Wed, 18 Jun 1997 22:43:28 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA07890 for ; Wed, 18 Jun 1997 22:43:26 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id WAA07025; Wed, 18 Jun 1997 22:42:55 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma007023; Wed Jun 18 22:42:44 1997 Received: (from archie@localhost) by bubba.whistle.com (8.8.5/8.6.12) id WAA02606; Wed, 18 Jun 1997 22:42:44 -0700 (PDT) From: Archie Cobbs Message-Id: <199706190542.WAA02606@bubba.whistle.com> Subject: Re: Adding a new feature to 2.2 series? In-Reply-To: <199706181926.PAA04006@pandora.hh.kew.com> from Drew Derbyshire at "Jun 18, 97 03:26:15 pm" To: ahd@kew.com (Drew Derbyshire) Date: Wed, 18 Jun 1997 22:42:44 -0700 (PDT) Cc: hackers@FreeBSD.ORG, julian@whistle.com X-Mailer: ELM [version 2.4ME+ PL31 (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 > If you're hacking the code, add a wish for the ipfw command line > side, although not for 2.2.x ... > > Consider parsing the port and IP address fields for the contents > of /etc/services, /etc/hosts and /etc/network. I find the requirement > to use numerics to be extremely error prone. I presume this is > currently done because NIS and DNS are not presumed to be available > when ipfw is run and the stock gethostbyname, etc. would attempt > to access these services. DNS/NIS are not required to use /etc/services as far as I know, so that's not the reason.. I was under the impression that this was done for security reasons, i.e., if someone hacks (ie modifies) your /etc/services, they can then render your TCP and UDP packet filtering useless.. Of course, if they can do this, they can probably hack ipfw too .. I agree, at least it should be enablable via a command line option. I'll look at adding this to the patch.. shouldn't be hard. Comments? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-hackers Wed Jun 18 22:46:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA08025 for hackers-outgoing; Wed, 18 Jun 1997 22:46:04 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA08020 for ; Wed, 18 Jun 1997 22:46:01 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA06617 for hackers@FreeBSD.ORG; Wed, 18 Jun 1997 23:31:31 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id XAA23691; Wed, 18 Jun 1997 23:09:48 +0200 (MET DST) Message-ID: <19970618230948.EJ13870@uriah.heep.sax.de> Date: Wed, 18 Jun 1997 23:09:48 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: RiscBSD speed References: <9706181755.AA16829@fyeung8.netific.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Tom Samplonius on Jun 18, 1997 11:59:11 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Tom Samplonius wrote: > This was hardly relevant to the freebsd-hackers list. I normally hate off-topic postings, but i found it at least interesting (assuming also the usual grain of salt you gotta take for a microbenchmark like lmbench). > FreeBSD doesn't > run on most of those platforms. Plus, the benchmarks were run on FreeBSD > 2.1, but which 2.1? 2.1.0, 2.1.5, 2.1.6, 2.1.7? The picture mentioned 2.1-S, presumably meaning 2.1-stable. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Wed Jun 18 23:23:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA09592 for hackers-outgoing; Wed, 18 Jun 1997 23:23:55 -0700 (PDT) Received: from thorin.hway.ru (root@thorin.hway.ru [194.87.58.130]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA09535 for ; Wed, 18 Jun 1997 23:23:00 -0700 (PDT) Received: from flash.intech.hway.ru (flash.intech.hway.ru [194.87.58.132]) by thorin.hway.ru (8.8.5/8.8.5) with ESMTP id KAA28211; Thu, 19 Jun 1997 10:20:22 +0400 (MSD) Message-Id: <199706190620.KAA28211@thorin.hway.ru> From: "Alexander V. Tischenko" To: "Alexander V. Tischenko" , "Louis A. Mamakos" Cc: "David S. Miller" , , Subject: Re: RFCs and Urgent pointers Date: Thu, 19 Jun 1997 10:17:01 +0400 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From: Louis A. Mamakos > To: Alexander V. Tischenko > Cc: David S. Miller ; freebsd-hackers@FreeBSD.ORG; Eric.Schenk@dna.lth.se > Subject: Re: RFCs and Urgent pointers > Date: 19 èþíÿ 1997 ã. 7:31 > > > On Wed, 18 Jun 1997, David S. Miller wrote: > > > > > Date: Wed, 18 Jun 1997 16:50:13 +0400 (MSD) > > > From: "Alexander V. Tischenko" > > > > > > Anybody thought of adding the RFC style Urgent pointers to the TCP, > > > say, as TCP level socket option ? > > > > > > We've made this a sysctl() tunable under Linux, I don't think we > > > considered the benefits of making it a socket option, that may in fact > > > be a better approach. Comments? > > > > > I suppose it is better to make it an option, 'cause this way you can set > > it on per-socket basis from your applications. > > TCP urgent data is how the socket out-of-band-data abstraction is realized. I > don't understand what else you might "add" to TCP to do "Urgent Pointers". > There ought to already be a option for "inline" out-of-band data, which I > think is the default in most modern BSD-based TCPs. Just read RFC-1122, especially the part concerning TCP and Urgent Pointers (4.2.2.4 Urgent Pointer), you will understand what i meant. > > louie > > ---------------------------------------------------------------------------- -------------------------------------------- Alexander V. Tischenko Integrated Network Technologies AT55-RIPE From owner-freebsd-hackers Thu Jun 19 00:00:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA11604 for hackers-outgoing; Thu, 19 Jun 1997 00:00:43 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA11599 for ; Thu, 19 Jun 1997 00:00:38 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 6927 invoked by uid 1001); 19 Jun 1997 07:00:23 +0000 (GMT) To: tom@sdf.com Cc: ccsanady@scl.ameslab.gov, hackers@FreeBSD.ORG, matt@3am-software.com Subject: Re: Network concurrency problems!? In-Reply-To: Your message of "Wed, 18 Jun 1997 18:16:49 -0700 (PDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 19 Jun 1997 09:00:23 +0200 Message-ID: <6925.866703623@verdi.nethelp.no> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > There has been a good deal of debate on whether offloading is really the > > best idea for network protocol implementations. A lot of people have tried > > it, and a lot of people have failed. If you look at Van Jacobson't work > > you'll find him arguing in the opposite direction: A "stupid" (in reality: > > simple and efficient) controller, and a very efficient protocol stack > > implementation. > > Not really what I was refering to. I was thinking about controllers > that minimize interupt calls, use DMA, avoid PIO, and align data > transfered to the host. With the possible exception of the data alignment issue, which of these do you think are *not* used by the 100 Mbps cards supported by FreeBSD? (I mention the alignment issue because the DEC 21040 used to have a problem here. Not sure if the 21140 has the same problem.) Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Thu Jun 19 01:10:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA15113 for hackers-outgoing; Thu, 19 Jun 1997 01:10:55 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA15105 for ; Thu, 19 Jun 1997 01:10:52 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wecG6-0003HE-00; Thu, 19 Jun 1997 01:07:58 -0700 Date: Thu, 19 Jun 1997 01:07:58 -0700 (PDT) From: Tom Samplonius To: Joerg Wunsch cc: hackers@freebsd.org Subject: Re: RiscBSD speed In-Reply-To: <19970618230948.EJ13870@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 Wed, 18 Jun 1997, J Wunsch wrote: > > FreeBSD doesn't > > run on most of those platforms. Plus, the benchmarks were run on FreeBSD > > 2.1, but which 2.1? 2.1.0, 2.1.5, 2.1.6, 2.1.7? > > The picture mentioned 2.1-S, presumably meaning 2.1-stable. Of what vintage? Not anymore helpful... > -- > 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. ;-) > > Tom From owner-freebsd-hackers Thu Jun 19 01:19:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA15540 for hackers-outgoing; Thu, 19 Jun 1997 01:19:31 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA15535 for ; Thu, 19 Jun 1997 01:19:28 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) id EAA17008; Thu, 19 Jun 1997 04:15:02 -0400 (EDT) Message-ID: <19970619041501.32083@vinyl.quickweb.com> Date: Thu, 19 Jun 1997 04:15:01 -0400 From: Mark Mayo To: freebsd-hackers@freebsd.org Subject: make world error in RELENG_2_2 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi again. Well, after I struggled to build the latest RELENG_2_2 for so long, I decided to take the advice of the wise (who believed that my system was somehow hosed) and reinstall my system. So I dug out the 2.2.1 CD and installed - boy has sysinstall improved since the last time I installed in August '96!! Looks great. However, when I cvsup'ed the lastest RELENG_2_2 and did a make world, it still puked!!! Arggh. If you search the mail archives for "tclMtherr" you'll see that several other people have had the same problems. The problem seems to be some sort of confusion as to whether or not FreeBSD needs the math error support. I noticed that there was no Makefile, so I ran 'configure' in /usr/src/contrib/tcl/unix and it said: matherr support ... no Hmm. I'm not sure how to interpret that (which is the root of the problem here). The question is: do I need the tclMtherr routine or not? I played around with source abit, and discoverd some descrepencies with the #defines.... but it all seems to be irrelevant anyhow since after I ran the configure script and did 'make' all went well. tclMtherr compiled no problem and I'm happy again. So I guess it's a simple case of the Makefile file is missing from the distribution, and the Makefile.in isn't doing the right thing under FreeBSD. I have no idea why this isn't showing up on other peoples' systems however, since most people aren't getting this screwup. Perhaps I'm just CVS jinx'ed or something bizarre... cya, -Mark -- ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ---------------------------------------------------------------------------- University degrees are a bit like adultery: you may not want to get involved with that sort of thing, but you don't want to be thought incapable. -Sir Peter Imbert From owner-freebsd-hackers Thu Jun 19 01:22:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA15760 for hackers-outgoing; Thu, 19 Jun 1997 01:22:54 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA15754 for ; Thu, 19 Jun 1997 01:22:49 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wecRg-0003Hn-00; Thu, 19 Jun 1997 01:19:56 -0700 Date: Thu, 19 Jun 1997 01:19:55 -0700 (PDT) From: Tom Samplonius To: sthaug@nethelp.no cc: ccsanady@scl.ameslab.gov, hackers@freebsd.org, matt@3am-software.com Subject: Re: Network concurrency problems!? In-Reply-To: <6925.866703623@verdi.nethelp.no> 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, 19 Jun 1997 sthaug@nethelp.no wrote: > > > There has been a good deal of debate on whether offloading is really the > > > best idea for network protocol implementations. A lot of people have tried > > > it, and a lot of people have failed. If you look at Van Jacobson't work > > > you'll find him arguing in the opposite direction: A "stupid" (in reality: > > > simple and efficient) controller, and a very efficient protocol stack > > > implementation. > > > > Not really what I was refering to. I was thinking about controllers > > that minimize interupt calls, use DMA, avoid PIO, and align data > > transfered to the host. > > With the possible exception of the data alignment issue, which of these do > you think are *not* used by the 100 Mbps cards supported by FreeBSD? Not "think", but "know". The 3COM Fast Etherlink is only used in polled mode. Even then, the card does seem to be terribly efficient. You should read the driver, and card specs for more details, rather than bother the list. Also, DG has mentioned that the Intel Etherexpress Pro100, is faster than anything using the de driver, because the driver is simpler, due to the hardware design of the Pro100. Anyways, enough on this topic. See the list archives, and hw specs for more details. > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > Tom From owner-freebsd-hackers Thu Jun 19 01:26:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA15906 for hackers-outgoing; Thu, 19 Jun 1997 01:26:10 -0700 (PDT) Received: from burka.rdy.com (dima@burka.rdy.com [205.149.163.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA15901 for ; Thu, 19 Jun 1997 01:26:07 -0700 (PDT) Received: by burka.rdy.com id BAA19159; (8.8.5/RDY) Thu, 19 Jun 1997 01:26:06 -0700 (PDT) Message-Id: <199706190826.BAA19159@burka.rdy.com> Subject: btw To: hackers@freebsd.org Date: Thu, 19 Jun 1997 01:26:06 -0700 (PDT) X-Class: Fast Organization: HackerDome Reply-To: dima@best.net From: dima@best.net (Dima Ruban) X-Mailer: ELM [version 2.4ME+ PL31 (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 Hey guys! Why do we call /etc/rc.local by: (thats from /etc/rc) # Do traditional (but rather obsolete) rc.local file if it exists. [ -f /etc/rc.local ] && sh /etc/rc.local ^^^^ and not ". /etc/rc.local"? In current case we are not able to use any variables from /etc/rc.conf in /etc/rc.local ... (Which sucks!) If nobody has any objections, I'll commit this change. Thanks! -- dima From owner-freebsd-hackers Thu Jun 19 01:41:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA16694 for hackers-outgoing; Thu, 19 Jun 1997 01:41:05 -0700 (PDT) Received: from coconut.blueberry.co.uk ([194.70.52.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA16688 for ; Thu, 19 Jun 1997 01:41:00 -0700 (PDT) Received: (from nik@localhost) by coconut.blueberry.co.uk (8.8.5/8.8.5) id JAA19475; Thu, 19 Jun 1997 09:27:18 +0100 (BST) Message-ID: <19970619092718.07152@blueberry.co.uk> Date: Thu, 19 Jun 1997 09:27:18 +0100 From: Nik Clayton To: hackers@freebsd.org Subject: 2.1.7: YP/NIS and getservent()/getprotoent() functions Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e Organization: Blueberry New Media Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, [ Originally sent to -questions, no response, so trying -hackers ] The yp(4) manual page on my 2.1.7 system includes (under "BUGS") The getservent(3) and getprotoent(3) functions do not yet have NIS sup- port. Fortunately, these files don't need to be updated that often. Is this still true? A quick eyeball through the source in /usr/src/lib/libc/net/getservent.c shows what look like appropriate YP functions, and quick tests with my /etc/services file seem to show that the '+' token in /etc/services *is* recognised and acted upon. If someone more knowledgable than me could confirm this is the case, I'll submit patches to the appropriate documentation (since it looks like -current, based on ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src/share/man/man4/yp.4 has the same wrong information). N -- --+=[ Blueberry Hill Blueberry New Media ]=+-- --+=[ http://www.blueberry.co.uk/ 1/9 Chelsea Harbour Design Centre, ]=+-- --+=[ WebMaster@blueberry.co.uk London, England, SW10 0XE ]=+-- --+=[ Contributing to the heat death of the Universe since 1973 ]=+-- From owner-freebsd-hackers Thu Jun 19 02:08:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA17887 for hackers-outgoing; Thu, 19 Jun 1997 02:08:14 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id CAA17882 for ; Thu, 19 Jun 1997 02:08:09 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 7620 invoked by uid 1001); 19 Jun 1997 09:07:59 +0000 (GMT) To: tom@sdf.com Cc: ccsanady@scl.ameslab.gov, hackers@FreeBSD.ORG, matt@3am-software.com Subject: Re: Network concurrency problems!? In-Reply-To: Your message of "Wed, 18 Jun 1997 18:16:49 -0700 (PDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 19 Jun 1997 11:07:59 +0200 Message-ID: <7618.866711279@verdi.nethelp.no> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Would a TCP socket have more system overhead than a file on a UFS > filesystem? I guess you can tess this by running dd on a mfs, and > tcpblast/netpipe/ttcp on loopback? Somehow I think the socket would be > faster. I don't know enough about the file system to say whether this is a relevant comparison on one host. It's not a very good comparison to the Ethernet case for the simple reason that the Ethernet MTU is 1500, while the default loopback MTU is 16384. I did a couple of quick tests here on a PPro-200. With the default loopback MTU, I consistently got around 44 MByte/s (M=1048576) using ttcp. With a 1500 byte MTU, I'm down to 27 Mbyte/s - a significant difference. Using the loopback interface the packet needs to traverse both down and up the protocol stack on the same host, so this would tend to decrease performance. I don't know whether the increased performance from a large loopback MTU offsets the decreased performance from traversing the protocol stack twice. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Thu Jun 19 02:09:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA17965 for hackers-outgoing; Thu, 19 Jun 1997 02:09:26 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA17960 for ; Thu, 19 Jun 1997 02:09:22 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id SAA27236; Thu, 19 Jun 1997 18:39:13 +0930 (CST) From: Michael Smith Message-Id: <199706190909.SAA27236@genesis.atrad.adelaide.edu.au> Subject: Re: make world error in RELENG_2_2 In-Reply-To: <19970619041501.32083@vinyl.quickweb.com> from Mark Mayo at "Jun 19, 97 04:15:01 am" To: mark@quickweb.com (Mark Mayo) Date: Thu, 19 Jun 1997 18:39:13 +0930 (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 Mark Mayo stands accused of saying: > > However, when I cvsup'ed the lastest RELENG_2_2 and did a make world, it > still puked!!! Arggh. If you search the mail archives for "tclMtherr" you'll > see that several other people have had the same problems. You've still done something wrong. I am in the process of a 'make release' right now, and apart from our CVS server maching throwing a gear in the middle of the checkout it's going fine. The machine running the release, incidentally, has been doing checkout, make world cycles since last Friday evening. THERE IS NOTHING WRONG WITH 2.2. > The problem seems to be some sort of confusion as to whether or not FreeBSD > needs the math error support. I noticed that there was no Makefile, so > I ran 'configure' in /usr/src/contrib/tcl/unix and it said: > matherr support ... no The tcl build problem posted last week was someone with hosed includes (I suspect they deleted /sys for some reason). Running the 'configure' script in the Tcl directory won't do anything; nothing is built under contrib. I don't know why, or what has broken peoples' systems, but it's nothing wrong with the tree. > Mark Mayo mark@quickweb.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 Thu Jun 19 03:02:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA19862 for hackers-outgoing; Thu, 19 Jun 1997 03:02:14 -0700 (PDT) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA19856 for ; Thu, 19 Jun 1997 03:02:08 -0700 (PDT) Message-Id: <199706191002.DAA19856@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA026824090; Thu, 19 Jun 1997 19:54:51 +1000 From: Darren Reed Subject: Re: btw To: dima@best.net Date: Thu, 19 Jun 1997 19:54:50 +1000 (EST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199706190826.BAA19159@burka.rdy.com> from "Dima Ruban" at Jun 19, 97 01:26:06 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In some mail from Dima Ruban, sie said: > > Hey guys! > > Why do we call /etc/rc.local by: (thats from /etc/rc) > # Do traditional (but rather obsolete) rc.local file if it exists. > [ -f /etc/rc.local ] && sh /etc/rc.local > ^^^^ > and not ". /etc/rc.local"? does rc (sh) handle errors the same way with "sh xx" and ". xx" ? From owner-freebsd-hackers Thu Jun 19 03:25:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA20721 for hackers-outgoing; Thu, 19 Jun 1997 03:25:54 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA20713 for ; Thu, 19 Jun 1997 03:25:49 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 8183 invoked by uid 1001); 19 Jun 1997 10:25:43 +0000 (GMT) To: tom@sdf.com Cc: ccsanady@scl.ameslab.gov, hackers@FreeBSD.ORG, matt@3am-software.com Subject: Re: Network concurrency problems!? In-Reply-To: Your message of "Thu, 19 Jun 1997 01:19:55 -0700 (PDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 19 Jun 1997 12:25:42 +0200 Message-ID: <8181.866715942@verdi.nethelp.no> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > With the possible exception of the data alignment issue, which of these do > > you think are *not* used by the 100 Mbps cards supported by FreeBSD? > > Not "think", but "know". The 3COM Fast Etherlink is only used in polled > mode. Even then, the card does seem to be terribly efficient. You should > read the driver, and card specs for more details, rather than bother the > list. You're right - I shouldn't have said "the 100 Mbps cards supported by FreeBSD" - but then I didn't realize that the 3Com card was relevant at all. All the high-speed work I've seen with FreeBSD has used either the Intel Pro 100/B or a DEC 21140 based card. > Also, DG has mentioned that the Intel Etherexpress Pro100, is faster > than anything using the de driver, because the driver is simpler, due to > the hardware design of the Pro100. Yes, the Pro 100/B is measurably faster, and the driver is simpler. The speed difference is not dramatic, though, according to my own measure- ments. I can't remember seeing a direct statement that the Pro 100/B driver is simpler due to the design of the Pro 100/B. Can anybody help me here? Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Thu Jun 19 04:17:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA22285 for hackers-outgoing; Thu, 19 Jun 1997 04:17:52 -0700 (PDT) Received: from ads.genrad.co.uk ([132.223.201.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA22278 for ; Thu, 19 Jun 1997 04:17:47 -0700 (PDT) Message-Id: <199706191117.EAA22278@hub.freebsd.org> Received: from host5-99-3-2.btinternet.com [195.99.3.2] (HELO localhost) by ads.genrad.co.uk (AltaVista Mail V1.0/1.0 BL18 listener) id 0000_004a_33a9_1496_03ba; Thu, 19 Jun 1997 12:14:30 +0100 Reply-To: From: "Robert Swindells" To: CC: , Subject: Re: make world error in RELENG_2_2 Date: Thu, 19 Jun 1997 11:11:26 +0100 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 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 Michael Smith wrote: > > Mark Mayo stands accused of saying: > > > > However, when I cvsup'ed the lastest RELENG_2_2 and did a make world, it > > still puked!!! Arggh. If you search the mail archives for "tclMtherr" you'll > > see that several other people have had the same problems. > > You've still done something wrong. I am in the process of a > 'make release' right now, and apart from our CVS server maching throwing > a gear in the middle of the checkout it's going fine. > > The machine running the release, incidentally, has been doing checkout, > make world cycles since last Friday evening. > > THERE IS NOTHING WRONG WITH 2.2. > > > The problem seems to be some sort of confusion as to whether or not FreeBSD > > needs the math error support. I noticed that there was no Makefile, so > > I ran 'configure' in /usr/src/contrib/tcl/unix and it said: > > matherr support ... no > > The tcl build problem posted last week was someone with hosed includes > (I suspect they deleted /sys for some reason). Running the 'configure' > script in the Tcl directory won't do anything; nothing is built > under contrib. > > I don't know why, or what has broken peoples' systems, but it's nothing > wrong with the tree. > Try deleting the .depend files from your tree, several packages were moved from gnu to contrib between 2.2.1 and 2.2.2. I have used cvsup to update my 2.2.1 tree and needed to do this the first time I updated it. Robert Swindells ---------------------------------- Robert Swindells - GenRad Ltd. rjs@genrad.co.uk - Work rjs@fdy2.demon.co.uk - Home From owner-freebsd-hackers Thu Jun 19 04:31:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA23075 for hackers-outgoing; Thu, 19 Jun 1997 04:31:52 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA23070 for ; Thu, 19 Jun 1997 04:31:49 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with SMTP id EAA03461; Thu, 19 Jun 1997 04:33:46 -0700 (PDT) Message-Id: <199706191133.EAA03461@implode.root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: sthaug@nethelp.no cc: hackers@FreeBSD.ORG Subject: Re: Network concurrency problems!? In-reply-to: Your message of "Thu, 19 Jun 1997 12:25:42 +0200." <8181.866715942@verdi.nethelp.no> From: David Greenman Reply-To: dg@root.com Date: Thu, 19 Jun 1997 04:33:46 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I can't remember seeing a direct statement that the Pro 100/B driver is >simpler due to the design of the Pro 100/B. Can anybody help me here? I might have said that...I don't recall. In any case, it's part of the reason; the other part is that I simply was very careful about coding and spent a great deal of time optimizing the critical paths. There shouldn't be much difference in total throughput, but the Pro/100B under FreeBSD consumes much less CPU time compared to the DEC chip cards. My vauge recollection is that the interrupt time was roughly half. It's entirely possible that Matt has improved the performance of his driver since I did the tests, however. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Thu Jun 19 06:50:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA27880 for hackers-outgoing; Thu, 19 Jun 1997 06:50:19 -0700 (PDT) Received: from pandora.hh.kew.com (ahd@kendra.ne.highway1.com [24.128.53.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA27873 for ; Thu, 19 Jun 1997 06:50:16 -0700 (PDT) Received: (from ahd@localhost) by pandora.hh.kew.com (8.8.5/8.8.5) id JAA03034; Thu, 19 Jun 1997 09:50:02 -0400 (EDT) Date: Thu, 19 Jun 1997 09:50:02 -0400 (EDT) From: Drew Derbyshire Message-Id: <199706191350.JAA03034@pandora.hh.kew.com> To: ahd@kew.com, archie@whistle.com Subject: Re: Adding a new feature to 2.2 series? Cc: hackers@FreeBSD.ORG, julian@whistle.com Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From archie@whistle.com Thu Jun 19 01:44:07 1997 > > If you're hacking the code, add a wish for the ipfw command line > > side, although not for 2.2.x ... > > > > Consider parsing the port and IP address fields for the contents > > of /etc/services, /etc/hosts and /etc/network. I find the requirement > > to use numerics to be extremely error prone. I presume this is > > currently done because NIS and DNS are not presumed to be available > > when ipfw is run and the stock gethostbyname, etc. would attempt > > to access these services. > > DNS/NIS are not required to use /etc/services as far as I know, > so that's not the reason.. On SunOS and Solaris, /etc/services will definitely use NIS if you tell it to. I don't use NIS in my BSD environment, so I can't be sure. Correction, I can RTFM the 2.2.1 man page: NIS INTERACTION Access to the NIS services.byname map can be enabled by adding a single ``+'' on a line by itself in the /etc/services file. This causes the con- tents of the NIS services map to be inserted at the location where the ``+'' appears. Of course, using NIS on a true firewall strikes me as a really dumb idea, since that's fairly easy to hack compared to local system access. > I was under the impression that this was done for security reasons, > i.e., if someone hacks (ie modifies) your /etc/services, they can > then render your TCP and UDP packet filtering useless.. > > Of course, if they can do this, they can probably hack ipfw too .. Agreed. If they hack /etc/services, most attacks would kill the underlying the service anyway, since for example SMTP won't be real useful on port 1025. > I agree, at least it should be enablable via a command line option. > I'll look at adding this to the patch.. shouldn't be hard. Comments? I don't object if you wait for -current on this part, especially if it adds IP address parsing as well. -ahd- From owner-freebsd-hackers Thu Jun 19 07:21:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA29031 for hackers-outgoing; Thu, 19 Jun 1997 07:21:10 -0700 (PDT) Received: from relay1.cit.ru (relay1.cit.ru [193.125.82.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA29023 for ; Thu, 19 Jun 1997 07:21:04 -0700 (PDT) Received: from free.tula.su by relay1.cit.ru with UUCP id SAA28956; (8.8.2-MVC-141196/vak/1.9) Thu, 19 Jun 1997 18:20:12 +0400 (MSD) Received: from blik.UUCP by free.tula.su with UUCP id SAA00640; (8.8.2-MVC-141196/vak/1.9) 9b Received: by blik.samara.su id AA03186 (5.65/IDA-simtel for hackers@freebsd.org); Thu, 19 Jun 1997 19:42:00 +0500 To: hackers@freebsd.org Message-Id: Organization: Center of Information Technology From: "Igor" Date: Thu, 19 Jun 97 19:41:58 +0500 X-Mailer: BML [UNIX Beauty Mail v.1.39] Subject: debugging kernel's code Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk what are the methods of debugging kernel's code ? --- igor@blik.samara.su (Igor) From owner-freebsd-hackers Thu Jun 19 09:17:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA04242 for hackers-outgoing; Thu, 19 Jun 1997 09:17:26 -0700 (PDT) Received: from chouette.inria.fr (chouette.inria.fr [138.96.24.103]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA04236 for ; Thu, 19 Jun 1997 09:17:23 -0700 (PDT) Received: by chouette.inria.fr (8.8.5/8.7.3) id SAA26631; Thu, 19 Jun 1997 18:16:46 +0200 (MET DST) Date: Thu, 19 Jun 1997 18:16:46 +0200 (MET DST) Message-Id: <199706191616.SAA26631@chouette.inria.fr> From: Emmanuel Duros To: freebsd-hackers@freebsd.org Subject: Generic Routing Encapsulation [rfc1701] implementation Reply-to: Emmanuel.Duros@sophia.inria.fr Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I am looking for an implementation of GRE for Freebsd which would encapsulate (at least) ARP and IP datagrams. Do you know if there is any work beeing done on this protocol? If not, do you know pointers to some implementations for other OS's? I may be led to port/implement it... Emmanuel From owner-freebsd-hackers Thu Jun 19 10:04:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA05969 for hackers-outgoing; Thu, 19 Jun 1997 10:04:58 -0700 (PDT) Received: from ui-gate.utell.co.uk (root@ui-gate.utell.co.uk [194.200.4.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA05960; Thu, 19 Jun 1997 10:04:50 -0700 (PDT) Received: from utell.co.uk (shift.utell.net [97.3.0.21]) by ui-gate.utell.co.uk (8.7.6/8.7.3) with ESMTP id SAA05474; Thu, 19 Jun 1997 18:04:36 +0100 (BST) Received: (from brian@localhost) by utell.co.uk (8.8.5/8.8.5) id SAA24424; Thu, 19 Jun 1997 18:04:36 +0100 (BST) Date: Thu, 19 Jun 1997 18:04:36 +0100 (BST) Message-Id: <199706191704.SAA24424@utell.co.uk> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: brian@awfulhak.org, brian@utell.co.uk Organization: Awfulhak Ltd. References: <33956BBB.1BB@nospam.com> <5n7bk7$osi@uriah.heep.sax.de> <339863C7.1DF5@nospam.com> <5nbrkn$2h6@uriah.heep.sax.de> <339D9548.7B07@nospam.com> <5ob5e7$31j@ui-gate.utell.co.uk> From: brian@utell.co.uk (Brian Somers) Subject: Re: xperfmon++ problem (again) Newsgroups: comp.unix.bsd.freebsd.misc Cc: jmz@freebsd.org, freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [cc'd to jmz@FreeBSD.org (the XFree86 maintainer for FreeBSD)] [cc'd to freebsd-hackers@FreeBSD.org] [posted to comp.unix.bsd.freebsd.misc] In article <5ob5e7$31j@ui-gate.utell.co.uk>, brian@shift.utell.net (Brian Somers) writes: > In article <339D9548.7B07@nospam.com>, > Marvin Foster writes: >> J Wunsch wrote: >>> >>> Marvin Foster wrote: >>> >>> > Sorry. I was doing this from memory. The message was >>> > >>> > Error: Cannot perform realloc >>> >>> Well, i was checking all ``Cannot'' messages in the source, and none >>> didn't come close to what you've mentioned. >>> >>> Of course, there's a chance that it's a message from some X11 library. >>> Sorry for not being more helpful, but all i can say is that it works >>> for me (and used to work all the time). >>> >>> -- >>> 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. ;-) >> >> I did the following: >> >> [pozzo:/usr/home/mefoster] ldd /usr/X11R6/bin/xperfmon++ >> /usr/X11R6/bin/xperfmon++: >> -lXaw.6 => /usr/X11R6/lib/libXaw.so.6.1 (0x8022000) >> -lXt.6 => /usr/X11R6/lib/libXt.so.6.0 (0x8058000) >> -lXmu.6 => /usr/X11R6/lib/libXmu.so.6.0 (0x8099000) >> -lX11.6 => /usr/X11R6/lib/libX11.so.6.1 (0x80a9000) >> -lkvm.2 => /usr/lib/libkvm.so.2.0 (0x813f000) >> -lc.3 => /usr/lib/libc.so.3.0 (0x8143000) >> [pozzo:/usr/home/mefoster] >> [pozzo:/usr/home/mefoster] strings /usr/X11R6/lib/libXt.so.6.0 | grep >> realloc >> realloc >> _realloc >> [pozzo:/usr/home/mefoster] strings /usr/X11R6/lib/libXt.so.6.0 | grep >> perform >> Cannot perform %s >> [pozzo:/usr/home/mefoster] >> >> I'm sort of new to FreeBSD, and not very expert at unix debugging, but >> I will keep looking into it and submit a problem report if I find >> anything. > > Ouch. I just built XFree86-3.3, and I'm now getting this from knews. > I rebuilt knews too - no change. > > It happens just after I press the post key !!!!!! > > This is on a RELENG_2_2 machine built June 15. Even setting > /etc/malloc.conf to RAD doesn't yield any results - somethings > lying - realloc didn't fail ! I'll post any findings. > > Here goes again *cringe* Well, xc/lib/Xt/Alloc.c does the realloc (in function XtRealloc). I changed the diagnostic so that it says how much we're allocating, and it comes out as zero ! Ah ha ! shift $ cd /tmp shift $ cat >x.c < #include main() { char *x = (char *)malloc(0); printf("%p\n", x); x = (char *)realloc(x,0); printf("%p\n", x); return 0; } eof shift $ cc -o x x.c shift $ ./x 0x4030 0x0 shift $ Now this is *really* bad news AFAIK. X provides the following in FreeBSD.cf: #define Malloc0ReturnsNull NO but I don't know of any provisions for malloc returning a pointer and realloc returning NULL :( We could always do a simple patch to this file, but is this the right way to go ? -- Brian Don't _EVER_ lose your sense of humour ! From owner-freebsd-hackers Thu Jun 19 10:06:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA06033 for hackers-outgoing; Thu, 19 Jun 1997 10:06:22 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA06028 for ; Thu, 19 Jun 1997 10:06:20 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA22648; Thu, 19 Jun 1997 09:55:51 -0700 From: Terry Lambert Message-Id: <199706191655.JAA22648@phaeton.artisoft.com> Subject: Re: RiscBSD speed To: tom@sdf.com (Tom Samplonius) Date: Thu, 19 Jun 1997 09:55:51 -0700 (MST) Cc: fyeung@fyeung8.netific.com, hackers@FreeBSD.ORG In-Reply-To: from "Tom Samplonius" at Jun 18, 97 11:59:11 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 > [ bunch of lmbench results for mostly obscure platforms deleted ] > > This was hardly relevant to the freebsd-hackers list. FreeBSD doesn't > run on most of those platforms. It should. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Jun 19 10:08:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA06167 for hackers-outgoing; Thu, 19 Jun 1997 10:08:31 -0700 (PDT) Received: from sparkie.gnofn.org (sparkie.gnofn.org [206.27.168.35]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA06160 for ; Thu, 19 Jun 1997 10:08:28 -0700 (PDT) Received: from sparkie.gnofn.org (sparkie.gnofn.org [206.27.168.35]) by sparkie.gnofn.org (8.7.Beta.10/8.7.Beta.10) with SMTP id MAA26166 for ; Thu, 19 Jun 1997 12:07:50 -0500 (CDT) Date: Thu, 19 Jun 1997 12:07:48 -0500 (CDT) From: Craig Johnston To: hackers@freebsd.org Subject: sad UT_HOSTSIZE of 16 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If we're even going to store the remote hostname in utmp, in this day and age of ridiculously long hostnames, shouldn't we go for a bit more than 16 chars? 16 chars is not enough for a human to be able to figure out many entire addresses these days, much less a program. For example: ip119.harvey.la. It'd be nice to know that we were dealing with ip119.harvey.la.pub-ip. psi.net, no? 16 for display purposes might be just fine, but it'd be nice to have 255 chars or so of remote hostname stored in the utmp file. Sure, we can find out more other ways, but I think it should be in utmp. Of course the question is: what breaks? -Craig From owner-freebsd-hackers Thu Jun 19 10:10:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA06318 for hackers-outgoing; Thu, 19 Jun 1997 10:10:26 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA06311 for ; Thu, 19 Jun 1997 10:10:23 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA22674; Thu, 19 Jun 1997 10:00:38 -0700 From: Terry Lambert Message-Id: <199706191700.KAA22674@phaeton.artisoft.com> Subject: Re: update question. To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Thu, 19 Jun 1997 10:00:38 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Jaye Mathisen" at Jun 18, 97 11:18:30 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 > Does update only affect UFS operations? If I have nfs set to async, will > update sync it up? Update syncs dirty buffers for all mounted FS's. Unless NFS is mounted async (a violation of the RFC's defining the NFS protocol, for the most part), all ops will be synchronous anyway so that network outages do not leave implied state indeterminate. For example, a data file and a seperate index file which indexes records in the first file must be guaranteed colinear updating so that the database can be deterministically recovered following a client or server crash with a trasaction pending. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Jun 19 10:13:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA06536 for hackers-outgoing; Thu, 19 Jun 1997 10:13:51 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA06531 for ; Thu, 19 Jun 1997 10:13:49 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA22694; Thu, 19 Jun 1997 10:04:33 -0700 From: Terry Lambert Message-Id: <199706191704.KAA22694@phaeton.artisoft.com> Subject: Re: Opus diskettes To: joerg_wunsch@uriah.heep.sax.de-noreply Date: Thu, 19 Jun 1997 10:04:33 -0700 (MST) Cc: freebsd-hackers@freefall.FreeBSD.org In-Reply-To: <19970618211439.NU46112@uriah.heep.sax.de> from "J Wunsch" at Jun 18, 97 09:14:39 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > As Terry Lambert wrote: > > > dd if=/dev/floppy skip=4k conv=swab of=file_without_VTOC > ^^^^^^^ > > This would IMHO skip 4k blocks = 2048 * 512 bytes. Is this what you > want? :-) (The default bs is 512 bytes, and skip is measured in bs.) Sorry; the man page for dd is ambiguous: Where sizes are specified, a decimal number of bytes is expected. If the number ends with a ``b'', ``k'', ``m'' or ``w'', the number is multiplied by 512, 1024 (1K), 1048576 (1M) or the number of bytes in an integer, re- spectively. and it has been a long time since I've had to do this for an OPUS (or 3B1 or 3B2) disk. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Jun 19 10:26:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA07067 for hackers-outgoing; Thu, 19 Jun 1997 10:26:07 -0700 (PDT) Received: from ui-gate.utell.co.uk (root@ui-gate.utell.co.uk [194.200.4.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA07058; Thu, 19 Jun 1997 10:25:58 -0700 (PDT) Received: from utell.co.uk (shift.utell.net [97.3.0.21]) by ui-gate.utell.co.uk (8.7.6/8.7.3) with ESMTP id SAA05602; Thu, 19 Jun 1997 18:25:51 +0100 (BST) Received: (from brian@localhost) by utell.co.uk (8.8.5/8.8.5) id SAA00390; Thu, 19 Jun 1997 18:25:50 +0100 (BST) Date: Thu, 19 Jun 1997 18:25:50 +0100 (BST) Message-Id: <199706191725.SAA00390@utell.co.uk> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: brian@awfulhak.org, brian@utell.co.uk Organization: Awfulhak Ltd. References: <33956BBB.1BB@nospam.com> <5n7bk7$osi@uriah.heep.sax.de> <339863C7.1DF5@nospam.com> <5nbrkn$2h6@uriah.heep.sax.de> <339D9548.7B07@nospam.com> <5ob5e7$31j@ui-gate.utell.co.uk> <5obor4$58o@ui-gate.utell.co.uk> From: brian@utell.co.uk (Brian Somers) Subject: Re: xperfmon++ problem (again) Newsgroups: comp.unix.bsd.freebsd.misc Cc: jmz@freebsd.org, freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [cc'd to jmz@FreeBSD.org] [cc'd to freebsd-hackers@FreeBSD.org] [posted to comp.unix.bsd.freebsd.misc] In article <5obor4$58o@ui-gate.utell.co.uk>, brian@shift.utell.net (Brian Somers) writes: > > [cc'd to jmz@FreeBSD.org (the XFree86 maintainer for FreeBSD)] > [cc'd to freebsd-hackers@FreeBSD.org] > [posted to comp.unix.bsd.freebsd.misc] > > In article <5ob5e7$31j@ui-gate.utell.co.uk>, > brian@shift.utell.net (Brian Somers) writes: >> In article <339D9548.7B07@nospam.com>, >> Marvin Foster writes: >>> J Wunsch wrote: >>>> >>>> Marvin Foster wrote: >>>> >>>> > Sorry. I was doing this from memory. The message was >>>> > >>>> > Error: Cannot perform realloc >>>> >>>> Well, i was checking all ``Cannot'' messages in the source, and none >>>> didn't come close to what you've mentioned. >>>> >>>> Of course, there's a chance that it's a message from some X11 library. >>>> Sorry for not being more helpful, but all i can say is that it works >>>> for me (and used to work all the time). >>>> >>>> -- >>>> 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. ;-) >>> >>> I did the following: >>> >>> [pozzo:/usr/home/mefoster] ldd /usr/X11R6/bin/xperfmon++ >>> /usr/X11R6/bin/xperfmon++: >>> -lXaw.6 => /usr/X11R6/lib/libXaw.so.6.1 (0x8022000) >>> -lXt.6 => /usr/X11R6/lib/libXt.so.6.0 (0x8058000) >>> -lXmu.6 => /usr/X11R6/lib/libXmu.so.6.0 (0x8099000) >>> -lX11.6 => /usr/X11R6/lib/libX11.so.6.1 (0x80a9000) >>> -lkvm.2 => /usr/lib/libkvm.so.2.0 (0x813f000) >>> -lc.3 => /usr/lib/libc.so.3.0 (0x8143000) >>> [pozzo:/usr/home/mefoster] >>> [pozzo:/usr/home/mefoster] strings /usr/X11R6/lib/libXt.so.6.0 | grep >>> realloc >>> realloc >>> _realloc >>> [pozzo:/usr/home/mefoster] strings /usr/X11R6/lib/libXt.so.6.0 | grep >>> perform >>> Cannot perform %s >>> [pozzo:/usr/home/mefoster] >>> >>> I'm sort of new to FreeBSD, and not very expert at unix debugging, but >>> I will keep looking into it and submit a problem report if I find >>> anything. >> >> Ouch. I just built XFree86-3.3, and I'm now getting this from knews. >> I rebuilt knews too - no change. >> >> It happens just after I press the post key !!!!!! >> >> This is on a RELENG_2_2 machine built June 15. Even setting >> /etc/malloc.conf to RAD doesn't yield any results - somethings >> lying - realloc didn't fail ! I'll post any findings. >> >> Here goes again *cringe* > > Well, xc/lib/Xt/Alloc.c does the realloc (in function XtRealloc). > I changed the diagnostic so that it says how much we're allocating, > and it comes out as zero ! Ah ha ! > > shift $ cd /tmp > shift $ cat >x.c < #include > #include > main() > { > char *x = (char *)malloc(0); > printf("%p\n", x); > x = (char *)realloc(x,0); > printf("%p\n", x); > return 0; > } > eof > shift $ cc -o x x.c > shift $ ./x > 0x4030 > 0x0 > shift $ > > Now this is *really* bad news AFAIK. X provides the following in > FreeBSD.cf: > #define Malloc0ReturnsNull NO > > but I don't know of any provisions for malloc returning a pointer > and realloc returning NULL :( > > We could always do a simple patch to this file, but is this the > right way to go ? FWIW, this is the patch - it solves my knews problem, but isn't *really* the right answer :| Copy it to /usr/ports/x11/XFree86/patches/patch-af, and just "make". *** lib/Xt/Alloc.c.orig Wed May 21 16:02:17 1997 --- lib/Xt/Alloc.c Thu Jun 19 18:18:22 1997 *************** *** 139,150 **** if (!size) size = 1; #endif return(XtMalloc(size)); ! } else if ((ptr = Xrealloc(ptr, size)) == NULL ! #if MALLOC_0_RETURNS_NULL ! && size ! #endif ! ) ! _XtAllocError("realloc"); return(ptr); } --- 139,149 ---- if (!size) size = 1; #endif return(XtMalloc(size)); ! } else if ((ptr = Xrealloc(ptr, size)) == NULL && size) { ! char Msg[25]; ! sprintf(Msg, "realloc(%u)", size); ! _XtAllocError(Msg); ! } return(ptr); } -- Brian Don't _EVER_ lose your sense of humour ! From owner-freebsd-hackers Thu Jun 19 10:30:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA07256 for hackers-outgoing; Thu, 19 Jun 1997 10:30:06 -0700 (PDT) Received: from fang.cs.sunyit.edu (perlsta@fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA07250 for ; Thu, 19 Jun 1997 10:30:03 -0700 (PDT) Received: from localhost (perlsta@localhost) by fang.cs.sunyit.edu (8.7.6/8.7.3) with SMTP id NAA21095 for ; Thu, 19 Jun 1997 13:29:31 -0400 (EDT) Date: Thu, 19 Jun 1997 13:29:31 -0400 (EDT) From: Alfred Perlstein To: hackers@FreeBSD.ORG Subject: install is broken In-Reply-To: <9706181755.AA16829@fyeung8.netific.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 Since i installed 2.2.2-RELEASE the install program, when you go to add a new network interface has been all messed up. infact somehow it duplicated all the comments in the rc.conf file and now all the fields thatt come up for configuring the network interface are filled with garbage. I thought it was just me, but when i installed freebsd on a friend's computer i had the same problem. You guys might also want to make aborting a FTP transfer easier incase you connect to a REALLY SLOW site. thanks Alfred perlsta@cs.sunyit.edu From owner-freebsd-hackers Thu Jun 19 10:42:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA07817 for hackers-outgoing; Thu, 19 Jun 1997 10:42:48 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA07812 for ; Thu, 19 Jun 1997 10:42:46 -0700 (PDT) Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.8.3/8.6.9) with SMTP id NAA17187; Thu, 19 Jun 1997 13:48:16 -0400 (EDT) Message-Id: <3.0.32.19970619134051.00c926d0@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Thu, 19 Jun 1997 13:40:54 -0400 To: "Igor" , hackers@FreeBSD.ORG From: dennis Subject: Re: debugging kernel's code Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 07:41 PM 6/19/97 +0500, Igor wrote: >what are the methods of debugging kernel's code ? trace code is one. >--- > igor@blik.samara.su (Igor) > > > From owner-freebsd-hackers Thu Jun 19 10:58:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA08603 for hackers-outgoing; Thu, 19 Jun 1997 10:58:48 -0700 (PDT) Received: from sand.sentex.ca (sand.sentex.ca [206.222.77.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA08587 for ; Thu, 19 Jun 1997 10:58:42 -0700 (PDT) Received: from gravel (gravel.sentex.ca [205.211.165.210]) by sand.sentex.ca (8.8.5/8.8.3) with SMTP id OAA23592 for ; Thu, 19 Jun 1997 14:09:29 -0400 (EDT) Message-Id: <3.0.2.32.19970619140035.00a32100@sentex.net> X-Sender: mdtancsa@sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) Date: Thu, 19 Jun 1997 14:00:35 -0400 To: freebsd-hackers@FreeBSD.ORG From: Mike Tancsa Subject: Re: make world error in RELENG_2_2 In-Reply-To: <199706190909.SAA27236@genesis.atrad.adelaide.edu.au> References: <19970619041501.32083@vinyl.quickweb.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 06:39 PM 6/19/97 +0930, Michael Smith wrote: >You've still done something wrong. I am in the process of a >'make release' right now, and apart from our CVS server maching throwing >a gear in the middle of the checkout it's going fine. > >The machine running the release, incidentally, has been doing checkout, >make world cycles since last Friday evening. > >THERE IS NOTHING WRONG WITH 2.2. > >I don't know why, or what has broken peoples' systems, but it's nothing >wrong with the tree. If there is nothing wrong, why were so many people having problems all of a sudden? I would say the lack of the login.conf in /etc was a 'problem'... the changing of the /usr/include structure was also a 'problem'... Look, I am not out to bitch about FreeBSD... I think its an incredible project. But thats not to say there are some minor glitches here and there, and always room for improvment... I have been following 2.2-RELENG for a couple of months now, with almost weekly updates. I ran into problems when I skipped a few weeks. The big one being the changing of the /usr/include tree. I try and read the main lists almost religiously.. But its easy to miss a post that details a change to the tree structure.... Now, if there was a README file of some sort included with the cvsup process, detailing any manual interventions necessary in the make world process, this would help avoid situations like this. But blindling blaming the user saying there is nothing wrong doesnt help matters, nor is it correct... ---Mike ********************************************************************** Mike Tancsa (mike@sentex.net) * To do is to be -- Nietzsche Sentex Communications Corp, * To be is to do -- Sartre Cambridge, Ontario * Do be do be do -- Sinatra (http://www.sentex.net/~mdtancsa) * From owner-freebsd-hackers Thu Jun 19 11:16:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA09511 for hackers-outgoing; Thu, 19 Jun 1997 11:16:54 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA09506 for ; Thu, 19 Jun 1997 11:16:52 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.5/8.7.3) with SMTP id LAA02227 for ; Thu, 19 Jun 1997 11:16:46 -0700 (PDT) Date: Thu, 19 Jun 1997 11:16:45 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: OpenBSD Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sheesh, how many people do they have working on that thing? I was reading the 2.1 release announcement, and shaking my head... Of course, the "20 or more security fixes", w/o mentioning subsystems was amusing. (Not doubting that they were fixed, only the tossing around of unsubstantiated numbers). Anybody running FreeBSD given it a shot just to see? I have been thinking about it to see if it fixes my UFS problems that are seemingly unrepairable. From owner-freebsd-hackers Thu Jun 19 11:46:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA10751 for hackers-outgoing; Thu, 19 Jun 1997 11:46:06 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA10745 for ; Thu, 19 Jun 1997 11:46:04 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id LAA24208; Thu, 19 Jun 1997 11:45:59 -0700 (PDT) To: Alfred Perlstein cc: hackers@FreeBSD.ORG Subject: Re: install is broken In-reply-to: Your message of "Thu, 19 Jun 1997 13:29:31 EDT." Date: Thu, 19 Jun 1997 11:45:58 -0700 Message-ID: <24204.866745958@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Since i installed 2.2.2-RELEASE the install program, when you go to add > a new network interface has been all messed up. Yeah, I know, and it's now fixed in 2.2-970617-RELENG / 3.0-970617-SNAP and later releases (examples of both now being on ftp.freebsd.org). Jordan From owner-freebsd-hackers Thu Jun 19 11:46:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA10808 for hackers-outgoing; Thu, 19 Jun 1997 11:46:54 -0700 (PDT) Received: from pandora.hh.kew.com (ahd@kendra.ne.highway1.com [24.128.53.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA10803 for ; Thu, 19 Jun 1997 11:46:52 -0700 (PDT) Received: (from ahd@localhost) by pandora.hh.kew.com (8.8.5/8.8.5) id OAA03931; Thu, 19 Jun 1997 14:46:48 -0400 (EDT) Date: Thu, 19 Jun 1997 14:46:48 -0400 (EDT) From: Drew Derbyshire Message-Id: <199706191846.OAA03931@pandora.hh.kew.com> To: craig@gnofn.org, hackers@FreeBSD.ORG Subject: Re: sad UT_HOSTSIZE of 16 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From: Craig Johnston > If we're even going to store the remote hostname in utmp, in this day and > age of ridiculously long hostnames, shouldn't we go for a bit more than 16 > chars? . . . > 16 for display purposes might be just fine, but it'd be nice to > have 255 chars or so of remote hostname stored in the utmp file. > Sure, we can find out more other ways, but I think it should be > in utmp. I've been considering this. Many of the programs automatically write the dotted quad address if the name is too long -- I have some fixes to apply to make this to more standard if as threatened I get commit privs. :-) If the programs automatically put dotted quads IP addresses in when needed for length and you can assume a fast DNS, perhaps the better apporach is to add support to the various viewing programs (last, finger, etc.) to resolve the dotted quad back to the full host name. This doesn't change the data format or waste space, at the expense of additional wall clock when formatting. > Of course the question is: what breaks? Nothing, if you fix normally the data and enhance the data consumers as I describe. Unenhanced consumers still work as well. Will a printable IPv6 address fit in 16 bytes? -ahd- From owner-freebsd-hackers Thu Jun 19 12:28:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA12701 for hackers-outgoing; Thu, 19 Jun 1997 12:28:06 -0700 (PDT) Received: from gwa.ericsson.com (gwa.ericsson.com [198.215.127.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA12647; Thu, 19 Jun 1997 12:27:51 -0700 (PDT) Received: from mr1.exu.ericsson.se (mr1.exu.ericsson.com [138.85.147.11]) by gwa.ericsson.com (8.8.2/8.8.2) with ESMTP id OAA14279; Thu, 19 Jun 1997 14:27:10 -0500 (CDT) Received: from noah.lmc.ericsson.se (noah.lmc.ericsson.se [142.133.1.1]) by mr1.exu.ericsson.se (8.7.1/NAHUB-MR1.1) with ESMTP id OAA12774; Thu, 19 Jun 1997 14:27:09 -0500 (CDT) Received: from jello.lmc.ericsson.se (jello.lmc.ericsson.se [142.133.28.34]) by noah.lmc.ericsson.se (8.8.5/8.8.5) with ESMTP id PAA27086; Thu, 19 Jun 1997 15:27:06 -0400 (EDT) Received: from localhost (lmcsato@localhost) by jello.lmc.ericsson.se (8.8.5/8.8.3) with SMTP id PAA26019; Thu, 19 Jun 1997 15:27:03 -0400 (EDT) X-Authentication-Warning: jello.lmc.ericsson.se: lmcsato owned process doing -bs Date: Thu, 19 Jun 1997 15:27:03 -0400 (EDT) From: Samy Touati To: questions@freebsd.org cc: hackers@freebsd.org Subject: SMC 9332BDT Help me please... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, In the rel notes of 2.2.2 it's clear that the SMC9332 BDT should work. I installed one and it dies as soon as it gets probed by the kernel at boot time. The chipset 21140A is identified with pass 2.0 and it tries to enable the 100TX port. Is this card supported in 2.2.2 or in 3.0? Thank you very much. Samy From owner-freebsd-hackers Thu Jun 19 12:46:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA13381 for hackers-outgoing; Thu, 19 Jun 1997 12:46:07 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA13367 for ; Thu, 19 Jun 1997 12:45:52 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id PAA26618; Thu, 19 Jun 1997 15:46:57 -0400 Date: Thu, 19 Jun 1997 15:46:55 -0400 (EDT) From: Ben Black To: Jaye Mathisen cc: hackers@FreeBSD.ORG Subject: Re: OpenBSD 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 the security fixes are real. unfortunately, few people can deal with theo deraadt, so step lightly on the openbsd lists. On Thu, 19 Jun 1997, Jaye Mathisen wrote: > > > Sheesh, how many people do they have working on that thing? I was reading > the 2.1 release announcement, and shaking my head... > > Of course, the "20 or more security fixes", w/o mentioning subsystems was > amusing. (Not doubting that they were fixed, only the tossing around of > unsubstantiated numbers). > > Anybody running FreeBSD given it a shot just to see? I have been > thinking about it to see if it fixes my UFS problems that are seemingly > unrepairable. > From owner-freebsd-hackers Thu Jun 19 12:51:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA13690 for hackers-outgoing; Thu, 19 Jun 1997 12:51:37 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA13669 for ; Thu, 19 Jun 1997 12:51:19 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA17549 for freebsd-hackers@FreeBSD.ORG; Thu, 19 Jun 1997 21:51:12 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id VAA02148; Thu, 19 Jun 1997 21:24:30 +0200 (MET DST) Message-ID: <19970619212430.SW21160@uriah.heep.sax.de> Date: Thu, 19 Jun 1997 21:24:30 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Subject: Re: make world error in RELENG_2_2 References: <19970619041501.32083@vinyl.quickweb.com> <3.0.2.32.19970619140035.00a32100@sentex.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <3.0.2.32.19970619140035.00a32100@sentex.net>; from Mike Tancsa on Jun 19, 1997 14:00:35 -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Mike Tancsa wrote: > >THERE IS NOTHING WRONG WITH 2.2. > > > >I don't know why, or what has broken peoples' systems, but it's nothing > >wrong with the tree. > > If there is nothing wrong, why were so many people having problems all of a > sudden? I would say the lack of the login.conf in /etc was a 'problem'... That's something entirely different. Mike's statement was related to the build process. login.conf is related to the execution environment. Note that a newly built and installed 2.2-stable of course should create /etc/login.conf, however upgrading using `make world' is supposed to never touch files in /etc. The upgrader is always responsible for doing this manually (has always been, and will be for at least quite some time, until a contributor steps forward with a sophisticated upgrade concept). -- 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 Jun 19 12:53:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA13917 for hackers-outgoing; Thu, 19 Jun 1997 12:53:55 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA13903 for ; Thu, 19 Jun 1997 12:53:49 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA17615; Thu, 19 Jun 1997 21:53:46 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id VAA02197; Thu, 19 Jun 1997 21:37:24 +0200 (MET DST) Message-ID: <19970619213723.UP30812@uriah.heep.sax.de> Date: Thu, 19 Jun 1997 21:37:23 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: igor@blik.samara.su (Igor) Subject: Re: debugging kernel's code References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Igor on Jun 19, 1997 19:41:58 +0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Igor wrote: > what are the methods of debugging kernel's code ? There's an entire section in the FreeBSD handbook devoted to kernel debugging. Go and read it, poshaluista. -- 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 Jun 19 13:13:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA15101 for hackers-outgoing; Thu, 19 Jun 1997 13:13:41 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA15084 for ; Thu, 19 Jun 1997 13:13:30 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 11226 invoked by uid 1001); 19 Jun 1997 20:13:25 +0000 (GMT) To: lmcsato@lmc.ericsson.se Cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: SMC 9332BDT Help me please... In-Reply-To: Your message of "Thu, 19 Jun 1997 15:27:03 -0400 (EDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 19 Jun 1997 22:13:25 +0200 Message-ID: <11224.866751205@verdi.nethelp.no> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > In the rel notes of 2.2.2 it's clear that the SMC9332 BDT should work. > I installed one and it dies as soon as it gets probed by the kernel at > boot time. > The chipset 21140A is identified with pass 2.0 and it tries to enable the > 100TX port. > > Is this card supported in 2.2.2 or in 3.0? Pick up http://www.3am-software.com/de-970513.tar.gz and install it, and you'll probably have much better luck! Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Thu Jun 19 13:15:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA15232 for hackers-outgoing; Thu, 19 Jun 1997 13:15:54 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA15221 for ; Thu, 19 Jun 1997 13:15:48 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wenZX-0003bo-00; Thu, 19 Jun 1997 13:12:47 -0700 Date: Thu, 19 Jun 1997 13:12:47 -0700 (PDT) From: Tom Samplonius To: Jaye Mathisen cc: hackers@freebsd.org Subject: Re: OpenBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 19 Jun 1997, Jaye Mathisen wrote: ... > Anybody running FreeBSD given it a shot just to see? I have been > thinking about it to see if it fixes my UFS problems that are seemingly > unrepairable. UFS problem? Tom From owner-freebsd-hackers Thu Jun 19 13:34:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA16924 for hackers-outgoing; Thu, 19 Jun 1997 13:34:19 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA16912 for ; Thu, 19 Jun 1997 13:34:10 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA22936; Thu, 19 Jun 1997 13:24:25 -0700 From: Terry Lambert Message-Id: <199706192024.NAA22936@phaeton.artisoft.com> Subject: Re: Opus diskettes To: dgy@rtd.com (Don Yuniskis) Date: Thu, 19 Jun 1997 13:24:25 -0700 (MST) Cc: terry@lambert.org, dgy@rtd.com, freebsd-hackers@freefall.FreeBSD.org In-Reply-To: <199706190159.SAA09351@seagull.rtd.com> from "Don Yuniskis" at Jun 18, 97 06:59:25 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 > > dd if=/dev/floppy skip=4k conv=swab of=file_without_VTOC > > Hmmm... perhaps you meant ^^ "8" since skip expects # of blocks > as an argument? > > In either case, this doesn't cut the mustard :-( I looked through > a few other OPFIL's and they *don't* appear to be compressed. For > example, one contained /etc/.profile which was entirely readable. > > Perhaps just a tape archive with some bogus crap on the front > end? file(1) sees them as "data" (BFD!) I doubt the data is compressed as well; the statement up front was that the disks contained compressed data. The 4k is a VTOC (Volume Table Of Contents); it is the old-SRV3 "disklabel" which was a non-optional result of the "format" command. Generally, we used the disks for tar archives; however, you should also check for cpio archives (more likely; without the extra package installed, SVR3 did not have tar, only cpio, especially on OPUS and Fortune systems boxes). Worst case, they are S51K file systems. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Jun 19 13:40:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA17356 for hackers-outgoing; Thu, 19 Jun 1997 13:40:08 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA17313 for ; Thu, 19 Jun 1997 13:40:03 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id NAA24529; Thu, 19 Jun 1997 13:39:47 -0700 (PDT) To: Mike Tancsa cc: freebsd-hackers@FreeBSD.ORG Subject: Re: make world error in RELENG_2_2 In-reply-to: Your message of "Thu, 19 Jun 1997 14:00:35 EDT." <3.0.2.32.19970619140035.00a32100@sentex.net> Date: Thu, 19 Jun 1997 13:39:47 -0700 Message-ID: <24525.866752787@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > If there is nothing wrong, why were so many people having problems all of a > sudden? I would say the lack of the login.conf in /etc was a 'problem'... That was a problem. Our problem. However, in every single case that I've seen the world target falling over so far, it has been: a) A 2.2.x tree splatted on top of a previous generation src tree (and that's bad). b) A bogus cvsup file, missing some crucial section of the source code (src-all is a good target and highly recommended). c) Stale depends or includes. Also note that RELENG_2_2 recently switched from SHARED=symlinks to SHARED=copies by default. This is not a 'problem' to be fixed so much as a change to simply be cognizant of, and if you've any doubts then blow away /usr/include and start over with a make includes; in all cases, the solution is fairly simple when you think about it. Jordan From owner-freebsd-hackers Thu Jun 19 14:15:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA19764 for hackers-outgoing; Thu, 19 Jun 1997 14:15:31 -0700 (PDT) Received: from sand.sentex.ca (sand.sentex.ca [206.222.77.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA19756 for ; Thu, 19 Jun 1997 14:15:23 -0700 (PDT) Received: from gravel (gravel.sentex.ca [205.211.165.210]) by sand.sentex.ca (8.8.5/8.8.3) with SMTP id RAA04444; Thu, 19 Jun 1997 17:25:58 -0400 (EDT) Message-Id: <3.0.2.32.19970619171704.02693930@sentex.net> X-Sender: mdtancsa@sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) Date: Thu, 19 Jun 1997 17:17:04 -0400 To: "Jordan K. Hubbard" From: Mike Tancsa Subject: Re: make world error in RELENG_2_2 Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <24525.866752787@time.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 01:39 PM 6/19/97 -0700, Jordan K. Hubbard wrote: >> If there is nothing wrong, why were so many people having problems all of a >> sudden? I would say the lack of the login.conf in /etc was a 'problem'... > >That was a problem. Our problem. However, in every single case that >I've seen the world target falling over so far, it has been: > > a) A 2.2.x tree splatted on top of a previous generation src > tree (and that's bad). > > b) A bogus cvsup file, missing some crucial section of the > source code (src-all is a good target and highly recommended). > > c) Stale depends or includes. You have sort of proved my point... As I said before, I try and follow the mailling lists as closely as possbile for any caveats / changes to the cvsup process... My sup file consists of the following *default tag=RELENG_2_2 *default host=cvsup.freebsd.org *default prefix=/usr *default base=/usr *default release=cvs delete use-rel-suffix src-all src-eBones src-secure Since there is precious little docs on the make world process, I have generally assumed that make world will do everything that is necessary to, well, make world (except for /etc, which is clear why you dont want to do that)... I had to learn the hard way about deleteing /usr/include, and the stale depends issue. Again, I assumed that make world would take care of these issues (and so did other users)... Perhaps a different target name, or a change in functionality of the target world would help here... My problems of a few Saturdays ago were due to c)... >Also note that RELENG_2_2 recently switched from SHARED=symlinks >to SHARED=copies by default. This is not a 'problem' to be fixed >so much as a change to simply be cognizant of, and if you've any >doubts then blow away /usr/include and start over with a make includes; >in all cases, the solution is fairly simple when you think about it. Its simple now :-) Look, I am really hesitant to be critical about the FreeBSD project because its such an amazing OS. (I am still amazed at what is produced strickly by volunteer efforts... ) Although I would guess the majority of people dont rebuild their OS from scratch, this area seems like it could use a little more clarification in either the docs, or in an FAQ. Better yet, as part of the CVSUP process, perhaps checkout a file that contains notes on any critical changes that would effect the build process... like blow away /usr/include and rebuild first etc... Even a simple section in the handbook after the CVSUP docs about the make world process would help alot... I would volunteer, but I certainly do not consider myself an expert... ---Mike ********************************************************************** Mike Tancsa (mike@sentex.net) * To do is to be -- Nietzsche Sentex Communications Corp, * To be is to do -- Sartre Cambridge, Ontario * Do be do be do -- Sinatra (http://www.sentex.net/~mdtancsa) * From owner-freebsd-hackers Thu Jun 19 14:36:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA20772 for hackers-outgoing; Thu, 19 Jun 1997 14:36:38 -0700 (PDT) Received: from gwa.ericsson.com (gwa.ericsson.com [198.215.127.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA20754; Thu, 19 Jun 1997 14:36:26 -0700 (PDT) Received: from mr1.exu.ericsson.se (mr1.exu.ericsson.com [138.85.147.11]) by gwa.ericsson.com (8.8.2/8.8.2) with ESMTP id QAA23776; Thu, 19 Jun 1997 16:35:54 -0500 (CDT) Received: from noah.lmc.ericsson.se (noah.lmc.ericsson.se [142.133.1.1]) by mr1.exu.ericsson.se (8.7.1/NAHUB-MR1.1) with ESMTP id QAA22928; Thu, 19 Jun 1997 16:35:52 -0500 (CDT) Received: from jello.lmc.ericsson.se (jello.lmc.ericsson.se [142.133.28.34]) by noah.lmc.ericsson.se (8.8.5/8.8.5) with ESMTP id RAA03477; Thu, 19 Jun 1997 17:33:50 -0400 (EDT) Received: from localhost (lmcsato@localhost) by jello.lmc.ericsson.se (8.8.5/8.8.3) with SMTP id RAA26163; Thu, 19 Jun 1997 17:31:47 -0400 (EDT) X-Authentication-Warning: jello.lmc.ericsson.se: lmcsato owned process doing -bs Date: Thu, 19 Jun 1997 17:31:47 -0400 (EDT) From: Samy Touati To: sthaug@nethelp.no cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: SMC 9332BDT Help me please... [solved] In-Reply-To: <11224.866751205@verdi.nethelp.no> 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 took the driver and it worked well. Thank you very much. Samy On Thu, 19 Jun 1997 sthaug@nethelp.no wrote: > > In the rel notes of 2.2.2 it's clear that the SMC9332 BDT should work. > > I installed one and it dies as soon as it gets probed by the kernel at > > boot time. > > The chipset 21140A is identified with pass 2.0 and it tries to enable the > > 100TX port. > > > > Is this card supported in 2.2.2 or in 3.0? > > Pick up http://www.3am-software.com/de-970513.tar.gz and install it, > and you'll probably have much better luck! > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > From owner-freebsd-hackers Thu Jun 19 14:39:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA20892 for hackers-outgoing; Thu, 19 Jun 1997 14:39:07 -0700 (PDT) Received: from burka.rdy.com (dima@burka.rdy.com [205.149.163.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA20885 for ; Thu, 19 Jun 1997 14:39:03 -0700 (PDT) Received: by burka.rdy.com id OAA22385; (8.8.5/RDY) Thu, 19 Jun 1997 14:38:52 -0700 (PDT) Message-Id: <199706192138.OAA22385@burka.rdy.com> Subject: Re: btw In-Reply-To: <199706191002.DAA29358@flea.best.net> from Darren Reed at "Jun 19, 97 07:54:50 pm" To: avalon@coombs.anu.edu.au (Darren Reed) Date: Thu, 19 Jun 1997 14:38:52 -0700 (PDT) Cc: dima@best.net, hackers@FreeBSD.ORG X-Class: Fast Organization: HackerDome Reply-To: dima@best.net From: dima@best.net (Dima Ruban) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Darren Reed writes: > In some mail from Dima Ruban, sie said: > > > > Hey guys! > > > > Why do we call /etc/rc.local by: (thats from /etc/rc) > > # Do traditional (but rather obsolete) rc.local file if it exists. > > [ -f /etc/rc.local ] && sh /etc/rc.local > > ^^^^ > > and not ". /etc/rc.local"? > > does rc (sh) handle errors the same way with "sh xx" and ". xx" ? It doesn't realy matter. tick:/# tail -5 /etc/rc # Do traditional (but rather obsolete) rc.local file if it exists. [ -f /etc/rc.local ] && sh /etc/rc.local date exit 0 tick:/# Even if ". /etc/rc.local" will be abnormaly terminated we won't loose anything but "date" command :-) And one other thing. All rc.files that we have we run with "." and not with "sh". All but /etc/rc.local. > > -- dima From owner-freebsd-hackers Thu Jun 19 14:39:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA20958 for hackers-outgoing; Thu, 19 Jun 1997 14:39:53 -0700 (PDT) Received: from pobox.com (ott-on1-22.netcom.ca [207.181.90.86]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA20950 for ; Thu, 19 Jun 1997 14:39:49 -0700 (PDT) Received: (from brianc@localhost) by pobox.com (8.8.5/8.8.5) id RAA01531; Thu, 19 Jun 1997 17:39:00 -0400 (EDT) Message-ID: <19970619173858.39930@pobox.com> Date: Thu, 19 Jun 1997 17:38:58 -0400 From: Brian Campbell To: freebsd-hackers@FreeBSD.org Subject: fs recovery Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk What's the normal sequence of steps to recover from a corrupted filesystem? It appears the first 64-inodes are "screwy" (according to fsdb). After that, things look reasonable. I used fsdb to look at the first 150k inodes and found an expected mixture of directories and inodes. Is there an easy way to recreate my root directory and link some of these directories (presumably the ones whose parent was inode 2? how do I find that out?) into the root? Or, failing that ... I have a backup from about a week ago. Is there a tool to scan what's left of the filesystem for anything more recent? Help! ;-) From owner-freebsd-hackers Thu Jun 19 14:59:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA22187 for hackers-outgoing; Thu, 19 Jun 1997 14:59:44 -0700 (PDT) Received: from sand.sentex.ca (sand.sentex.ca [206.222.77.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA21768 for ; Thu, 19 Jun 1997 14:51:43 -0700 (PDT) Received: from gravel (gravel.sentex.ca [205.211.165.210]) by sand.sentex.ca (8.8.5/8.8.3) with SMTP id SAA04558; Thu, 19 Jun 1997 18:02:14 -0400 (EDT) Message-Id: <3.0.2.32.19970619175320.00a7d7f0@sentex.net> X-Sender: mdtancsa@sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) Date: Thu, 19 Jun 1997 17:53:20 -0400 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), freebsd-hackers@FreeBSD.ORG From: Mike Tancsa Subject: Re: make world error in RELENG_2_2 In-Reply-To: <19970619212430.SW21160@uriah.heep.sax.de> References: <3.0.2.32.19970619140035.00a32100@sentex.net> <19970619041501.32083@vinyl.quickweb.com> <3.0.2.32.19970619140035.00a32100@sentex.net> 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 6/19/97 +0200, J Wunsch wrote: >As Mike Tancsa wrote: > >> >THERE IS NOTHING WRONG WITH 2.2. >> > >> >I don't know why, or what has broken peoples' systems, but it's nothing >> >wrong with the tree. >> >> If there is nothing wrong, why were so many people having problems all of a >> sudden? I would say the lack of the login.conf in /etc was a 'problem'... > >That's something entirely different. Mike's statement was related to >the build process. I was also talking about the build process... I see the two as being related in that both demonstrate a weaker area of the FreeBSD documentation (weak relative to an OS that is otherwise most excellent)... As I said in my response to JK, I think including a file in the CVSUP that contains such info like (make world will fail unless you rebuild your /usr/include tree, or XXX no longer exists and has been replaced by YYY, so do ZZZ before doing a make world, otherwise you are in trouble...) >Note that a newly built and installed 2.2-stable of >course should create /etc/login.conf, however upgrading using `make >world' is supposed to never touch files in /etc. The upgrader is >always responsible for doing this manually (has always been, and will >be for at least quite some time, until a contributor steps forward >with a sophisticated upgrade concept). Yes, I can see why this is a desirable design... That part has always been clear... Its the kill and rebuild /usr/include and .depends that up until a few cvsups ago, I (and a few others it seems) didnt know about... It wasnt such a big issue for me, because the effected unit was just a backup server... But had it been one of my main production units, I would be a few kg's thinner. I know that the answers are almost always in the list, but sometimes finding a small kernel of info like that can be very difficult in mail archives. Hence, I see it more of an issue than people who are already aware of it. Adding a few points like the ones raised by JK to the documentation, could go a long way to avoid problems like this. ---Mike ********************************************************************** Mike Tancsa (mike@sentex.net) * To do is to be -- Nietzsche Sentex Communications Corp, * To be is to do -- Sartre Cambridge, Ontario * Do be do be do -- Sinatra (http://www.sentex.net/~mdtancsa) * From owner-freebsd-hackers Thu Jun 19 15:32:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA23917 for hackers-outgoing; Thu, 19 Jun 1997 15:32:15 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA23909 for ; Thu, 19 Jun 1997 15:32:09 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) id SAA20730; Thu, 19 Jun 1997 18:27:21 -0400 (EDT) Message-ID: <19970619182720.20258@vinyl.quickweb.com> Date: Thu, 19 Jun 1997 18:27:20 -0400 From: Mark Mayo To: Michael Smith Cc: Mark Mayo , freebsd-hackers@FreeBSD.ORG Subject: Re: make world error in RELENG_2_2 References: <19970619041501.32083@vinyl.quickweb.com> <199706190909.SAA27236@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: <199706190909.SAA27236@genesis.atrad.adelaide.edu.au>; from Michael Smith on Thu, Jun 19, 1997 at 06:39:13PM +0930 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Jun 19, 1997 at 06:39:13PM +0930, Michael Smith wrote: > Mark Mayo stands accused of saying: > > > > However, when I cvsup'ed the lastest RELENG_2_2 and did a make world, it > > still puked!!! Arggh. If you search the mail archives for "tclMtherr" you'll > > see that several other people have had the same problems. > > You've still done something wrong. I am in the process of a > 'make release' right now, and apart from our CVS server maching throwing > a gear in the middle of the checkout it's going fine. Good for you... but what have I done wrong - this is the question I'm begging to know. I started with a fresh install of 2.2.1 from CD, created a cvsup download of src-all, and did make world. There was NO /usr/obj directory before the make. I've included my CVSUP file at the end of the email incase that's where I'm screwing up. > THERE IS NOTHING WRONG WITH 2.2. There is with my 2.2 tree :-) > > The problem seems to be some sort of confusion as to whether or not FreeBSD > > needs the math error support. I noticed that there was no Makefile, so > > I ran 'configure' in /usr/src/contrib/tcl/unix and it said: > > matherr support ... no > > The tcl build problem posted last week was someone with hosed includes > (I suspect they deleted /sys for some reason). Running the 'configure' > script in the Tcl directory won't do anything; nothing is built > under contrib. I realize that. I just wanted to see if the error popped up that way. Turns out it doesn't. I ended up just doing a "make -k world" and manually building tcl afterwards. Note that I did cd /usr/src/include make make install on the second try before running make world. This *should* be updating my /usr/include , no? At any rate, this is done by 'make world' long before my tcl build problems occur with a 'make includes'. So I didn't delete /sys, and my includes aren't hosed. > I don't know why, or what has broken peoples' systems, but it's nothing > wrong with the tree. Well, whatever the case, when I cvsup down the tree "over top" of the 2.2.1 Release, I get a bad tree. This also happened before when I was cvsupp'ing down the releases from my old August '96 SNAP. I don't know why. Perhaps something to do with dependencies out of date... I did delete them all. I guess it's just weird, or maybe satan is in my computer. I'm going to play around some more and see if I can't figure this out better. I'll post if I discover anything. -Mark > > > Mark Mayo mark@quickweb.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 [[ -- ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ---------------------------------------------------------------------------- University degrees are a bit like adultery: you may not want to get involved with that sort of thing, but you don't want to be thought incapable. -Sir Peter Imbert From owner-freebsd-hackers Thu Jun 19 16:07:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA25501 for hackers-outgoing; Thu, 19 Jun 1997 16:07:21 -0700 (PDT) Received: from friley01.res.iastate.edu (friley01.res.iastate.edu [129.186.189.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA25496 for ; Thu, 19 Jun 1997 16:07:17 -0700 (PDT) Received: from friley01.res.iastate.edu (loopback [127.0.0.1]) by friley01.res.iastate.edu (8.8.5/8.8.5) with ESMTP id SAA13293; Thu, 19 Jun 1997 18:08:44 -0500 (CDT) Message-Id: <199706192308.SAA13293@friley01.res.iastate.edu> X-Mailer: exmh version 2.0gamma 1/27/96 To: dg@root.com cc: sthaug@nethelp.no, hackers@FreeBSD.ORG Subject: Re: Network concurrency problems!? In-reply-to: Your message of Thu, 19 Jun 1997 04:33:46 -0700. <199706191133.EAA03461@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Jun 1997 18:08:44 -0500 From: Chris Csanady Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>I can't remember seeing a direct statement that the Pro 100/B driver is >>simpler due to the design of the Pro 100/B. Can anybody help me here? > > I might have said that...I don't recall. In any case, it's part of the >reason; the other part is that I simply was very careful about coding and >spent a great deal of time optimizing the critical paths. There shouldn't >be much difference in total throughput, but the Pro/100B under FreeBSD >consumes much less CPU time compared to the DEC chip cards. My vauge >recollection is that the interrupt time was roughly half. It's entirely >possible that Matt has improved the performance of his driver since I >did the tests, however. For what its worth, we are seeing virtually no difference in performance between the dec and intel cards with Matt's latest driver. However, the intel card does seem to be a lot more efficent. BTW, does the intel card use DBDMA? From the driver, it looks like something similar. How about the dec? Also, this is sortof an aside, but I am writing a new driver, and was wondering about using mem mapped vs io mapped registers. How much of a difference in performance is there? Or should I just do a lot of outl()'s? (like in linux.. but its really ugly imho..) The memory/PCI busses are already a significant bottleneck, so I dont think I can afford to sacrifice too much.. Chris Csanady > >-DG > >David Greenman >Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Thu Jun 19 16:10:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA25694 for hackers-outgoing; Thu, 19 Jun 1997 16:10:11 -0700 (PDT) Received: from brie.direct.ca (brie.direct.ca [199.60.229.8]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA25682; Thu, 19 Jun 1997 16:10:04 -0700 (PDT) Received: from localhost (jaredp@localhost) by brie.direct.ca (8.8.3/8.8.0) with SMTP id QAA13004; Thu, 19 Jun 1997 16:09:57 -0700 (PDT) X-Authentication-Warning: brie.direct.ca: jaredp owned process doing -bs Date: Thu, 19 Jun 1997 16:09:56 -0700 (PDT) From: Jared Proudfoot To: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org, freebsd-hackers@freebsd.org Subject: SCSI Problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, I've been looking through the mailing list archives and I've noticed that a lot of people have been experiencing the damn SCSI problems that I have been having recently. I'm currently running FreeBSD 2.2.1-RELEASE on a P166 with 128MB RAM, an Adaptec 2940 UW controller, 2 Quantam Atlases, 1 Quantam Grand Prix and an IDE Quantum Sirocco. The machine will lock up periodically, giving SCSI drive errors. Here's the errors I've been getting, the error as reported in /var/log/messages and a copy of my dmesg output: sd1(ahc0:5:0): UNIT ATTENTION asc:29,1 retires: 4 SCB: 0x1 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x4 Queueing an Abort SCB Queueing an Abort SCB no longer in timeout messages: ------------------------------------------------------------------------- Jun 14 06:35:22 havarti /kernel: sd1(ahc0:5:0): SCB 0x0 - timed out while idle, Jun 14 06:35:22 havarti /kernel: SEQADDR == 0x8 Jun 14 06:35:22 havarti /kernel: sd1(ahc0:5:0): Queueing an Abort SCB ------------------------------------------------------------------------- dmesg: ------------------------------------------------------------------------- Copyright (c) 1992-1996 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved FreeBSD 2.2.1-RELEASE #0: Fri May 16 22:32:31 PDT 1997 jaredp@havarti:/usr/src/sys/compile/HAVARTI CPU: Pentium (167.05-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 134217728 (131072K bytes) avail memory = 127184896 (124204K bytes) Probing for devices on PCI bus 0: chip0 rev 1 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 ahc0 rev 1 int a irq 12 on pci0:10 ahc0: aic7860 Single Channel, SCSI Id=7, 3 SCBs (ahc0:3:0): "QUANTUM XP34550S LXY1" type 0 fixed SCSI 2 sd0(ahc0:3:0): Direct-Access 4341MB (8890760 512 byte sectors) sd0(ahc0:3:0): with 5899 cyls, 10 heads, and an average 150 sectors/track (ahc0:5:0): "QUANTUM XP34550S LXQ1" type 0 fixed SCSI 2 sd1(ahc0:5:0): Direct-Access 4341MB (8890760 512 byte sectors) sd1(ahc0:5:0): with 5899 cyls, 10 heads, and an average 150 sectors/track (ahc0:6:0): "QUANTUM XP34301 1071" type 0 fixed SCSI 2 sd2(ahc0:6:0): Direct-Access 4106MB (8410200 512 byte sectors) sd2(ahc0:6:0): with 4076 cyls, 20 heads, and an average 103 sectors/track vga0 rev 84 int a irq 11 on pci0:12 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 1628MB (3335472 sectors), 3309 cyls, 16 heads, 63 S/T, 512 B/S fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: utp[*UTP*] address 00:a0:24:39:7e:bb npx0 on motherboard npx0: INT 16 interface ccd0-3: Concatenated disk drivers --------------------------------------------------------------------------- I've seen lots of discussion, but not solution on the lists. Has one been found? Any help would be appreciated. Thanks in advance, Jared Proudfoot PS - Please cc: me on this discussion. I'm not currently subscribed the the mailing lists. Thanks. -- Jared Proudfoot jaredp@direct.ca Systems Engineer, Canada Internet Direct Inc. http://www.direct.ca/ Finger jproudfo@footprints.net for PGP public key. From owner-freebsd-hackers Thu Jun 19 16:14:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA25918 for hackers-outgoing; Thu, 19 Jun 1997 16:14:00 -0700 (PDT) Received: from mail2.digital.com (mail2.digital.com [204.123.2.56]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA25896 for ; Thu, 19 Jun 1997 16:13:49 -0700 (PDT) Received: from johndoe.altavista-software.com (dhcp-14.altavista-software.com [205.181.164.238]) by mail2.digital.com (8.7.5/UNX 1.5/1.0/WV) with SMTP id QAA05699; Thu, 19 Jun 1997 16:05:56 -0700 (PDT) Message-Id: <3.0.1.32.19970619190409.0075418c@ranier.altavista-software.com> X-Sender: lkgpop@ranier.altavista-software.com X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Thu, 19 Jun 1997 19:04:09 -0400 To: sthaug@nethelp.no From: Matt Thomas Subject: Re: SMC 9332BDT Help me please... Cc: hackers@FreeBSD.ORG In-Reply-To: <11224.866751205@verdi.nethelp.no> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 10:13 PM 6/19/97 +0200, sthaug@nethelp.no wrote: >> In the rel notes of 2.2.2 it's clear that the SMC9332 BDT should work. >> I installed one and it dies as soon as it gets probed by the kernel at >> boot time. >> The chipset 21140A is identified with pass 2.0 and it tries to enable the >> 100TX port. >> >> Is this card supported in 2.2.2 or in 3.0? > >Pick up http://www.3am-software.com/de-970513.tar.gz and install it, >and you'll probably have much better luck! Use de-970603.tar.gz or even de-970618.tar.gz. The first had some transmit work done and the latter has even better transmit performance. -- Matt Thomas Internet: matt@lkg.dec.com UNIX Networking WWW URL: http://ftp.digital.com/%7Ethomas/ Digital Equipment Corporation Disclaimer: This message reflects my own Littleton, MA warped views, etc. From owner-freebsd-hackers Thu Jun 19 16:18:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA26140 for hackers-outgoing; Thu, 19 Jun 1997 16:18:23 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA26135 for ; Thu, 19 Jun 1997 16:18:15 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with SMTP id QAA07656; Thu, 19 Jun 1997 16:20:15 -0700 (PDT) Message-Id: <199706192320.QAA07656@implode.root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Chris Csanady cc: sthaug@nethelp.no, hackers@FreeBSD.ORG Subject: Re: Network concurrency problems!? In-reply-to: Your message of "Thu, 19 Jun 1997 18:08:44 CDT." <199706192308.SAA13293@friley01.res.iastate.edu> From: David Greenman Reply-To: dg@root.com Date: Thu, 19 Jun 1997 16:20:15 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >BTW, does the intel card use DBDMA? From the driver, it looks like >something similar. How about the dec? What is DBDMA? >Also, this is sortof an aside, but I am writing a new driver, and was >wondering about using mem mapped vs io mapped registers. How much of >a difference in performance is there? Or should I just do a lot of outl()'s? >(like in linux.. but its really ugly imho..) > >The memory/PCI busses are already a significant bottleneck, so I dont think >I can afford to sacrifice too much.. Programmed I/O instruction on the P6 (and Pentium II) are serialized in a way that makes them extremely expensive; memory mapped PCI operations are much faster because of this. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Thu Jun 19 16:41:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA27366 for hackers-outgoing; Thu, 19 Jun 1997 16:41:20 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA27357 for ; Thu, 19 Jun 1997 16:41:14 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id JAA00235; Fri, 20 Jun 1997 09:11:04 +0930 (CST) From: Michael Smith Message-Id: <199706192341.JAA00235@genesis.atrad.adelaide.edu.au> Subject: Re: make world error in RELENG_2_2 In-Reply-To: <19970619182720.20258@vinyl.quickweb.com> from Mark Mayo at "Jun 19, 97 06:27:20 pm" To: mark@quickweb.com (Mark Mayo) Date: Fri, 20 Jun 1997 09:11:03 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, mark@quickweb.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 Mark Mayo stands accused of saying: > > I realize that. I just wanted to see if the error popped up that way. Turns > out it doesn't. I ended up just doing a "make -k world" and manually > building tcl afterwards. Note that I did > cd /usr/src/include > make > make install > > on the second try before running make world. This *should* be updating my > /usr/include , no? No. "make includes" at the top level does that. -- ]] 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 Jun 19 16:46:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA27596 for hackers-outgoing; Thu, 19 Jun 1997 16:46:55 -0700 (PDT) Received: from sand.sentex.ca (sand.sentex.ca [206.222.77.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA27583; Thu, 19 Jun 1997 16:46:48 -0700 (PDT) Received: from gravel (gravel.sentex.ca [205.211.165.210]) by sand.sentex.ca (8.8.5/8.8.3) with SMTP id TAA04913; Thu, 19 Jun 1997 19:57:23 -0400 (EDT) Message-Id: <3.0.2.32.19970619194829.00c21440@sentex.net> X-Sender: mdtancsa@sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) Date: Thu, 19 Jun 1997 19:48:29 -0400 To: Jared Proudfoot , freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG From: Mike Tancsa Subject: Re: SCSI Problems In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 04:09 PM 6/19/97 -0700, Jared Proudfoot wrote: >I'm currently running FreeBSD 2.2.1-RELEASE on a P166 with 128MB RAM, an >Adaptec 2940 UW controller, 2 Quantam Atlases, 1 Quantam Grand Prix and an >IDE Quantum Sirocco. Two things I recall a) There has been fixes to the code since 2.2.1-RELEASE b) I also recall specific discussion of Quantum drives and firmware revs... Dunno if its your modle or not thats effected. But I would be concerned far more with a) than b) Have a look at http://www.freebsd.org/handbook/handbook228.html#479 and specifically at http://www.freebsd.org/handbook/handbook240.html#498 for how to use CVSUP to get the latest version of FreeBSD... Also, you may want to check out www.dejanews.com. They archive comp.unix.bsd.free.* and the mailling list in the newsgroup muc.lists.freebsd* ---Mike ********************************************************************** Mike Tancsa (mike@sentex.net) * To do is to be -- Nietzsche Sentex Communications Corp, * To be is to do -- Sartre Cambridge, Ontario * Do be do be do -- Sinatra (http://www.sentex.net/~mdtancsa) * From owner-freebsd-hackers Thu Jun 19 17:25:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA29227 for hackers-outgoing; Thu, 19 Jun 1997 17:25:11 -0700 (PDT) Received: from seagull.rtd.com (seagull.rtd.com [198.102.68.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA29222 for ; Thu, 19 Jun 1997 17:25:09 -0700 (PDT) Received: (from dgy@localhost) by seagull.rtd.com (8.8.5/8.8.5) id RAA11881; Thu, 19 Jun 1997 17:27:22 -0700 (MST) From: Don Yuniskis Message-Id: <199706200027.RAA11881@seagull.rtd.com> Subject: Re: Opus diskettes In-Reply-To: <199706192024.NAA22936@phaeton.artisoft.com> from Terry Lambert at "Jun 19, 97 01:24:25 pm" To: terry@lambert.org (Terry Lambert) Date: Thu, 19 Jun 1997 17:27:22 -0700 (MST) Cc: dgy@rtd.com, terry@lambert.org, freebsd-hackers@freefall.FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL31 (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 In the words of the world-renowned author, Terry Lambert: > > > dd if=/dev/floppy skip=4k conv=swab of=file_without_VTOC > > > > Hmmm... perhaps you meant ^^ "8" since skip expects # of blocks > > as an argument? > > > > In either case, this doesn't cut the mustard :-( I looked through > > a few other OPFIL's and they *don't* appear to be compressed. For > > example, one contained /etc/.profile which was entirely readable. > > > > Perhaps just a tape archive with some bogus crap on the front > > end? file(1) sees them as "data" (BFD!) > > I doubt the data is compressed as well; the statement up front > was that the disks contained compressed data. The first disk I examined happened to have lots of executables on it and no real text that was obvious. > The 4k is a VTOC (Volume Table Of Contents); it is the old-SRV3 > "disklabel" which was a non-optional result of the "format" > command. This doesn't appear to be the case. I've tried stripping various amounts off of the front of the file and it's still unrecognizable as a tarball or a cpio archive. (sigh) I guess I'll have to install the d*mn coprocessor and unpack them the hard way :-( > Generally, we used the disks for tar archives; however, you should > also check for cpio archives (more likely; without the extra > package installed, SVR3 did not have tar, only cpio, especially > on OPUS and Fortune systems boxes). Yes, previous OPUS release were just cpio archives cpio -icvtdumB ... > Worst case, they are S51K file systems. Or, perhaps I'll just punt and leave the man pages broken. No one seems to be missing it... ;-) Thx! --don From owner-freebsd-hackers Thu Jun 19 17:51:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA00559 for hackers-outgoing; Thu, 19 Jun 1997 17:51:00 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA00540; Thu, 19 Jun 1997 17:50:55 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0werrr-0003js-00; Thu, 19 Jun 1997 17:47:59 -0700 Date: Thu, 19 Jun 1997 17:47:59 -0700 (PDT) From: Tom Samplonius To: Jared Proudfoot cc: freebsd-scsi@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: SCSI Problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 19 Jun 1997, Jared Proudfoot wrote: > > Greetings, > > I've been looking through the mailing list archives and I've noticed that > a lot of people have been experiencing the damn SCSI problems that I have > been having recently. > > I'm currently running FreeBSD 2.2.1-RELEASE on a P166 with 128MB RAM, an > Adaptec 2940 UW controller, 2 Quantam Atlases, 1 Quantam Grand Prix and an > IDE Quantum Sirocco. You should probably upgrade to 2.2.2 The errors, look really familar. Is sd1 the Grand Prix? Is it always sd1? I found the Grand Prix to be very unreliable. So if sd1 is the Grand Prix, and sd1 is always the cause, rip it out. Also, 2.2.2-stable is better able to handle recovery. The drive still times out, and the system will freeze for a couple for seconds, and continue on. Tom From owner-freebsd-hackers Thu Jun 19 18:18:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA01508 for hackers-outgoing; Thu, 19 Jun 1997 18:18:46 -0700 (PDT) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA01501 for ; Thu, 19 Jun 1997 18:18:42 -0700 (PDT) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id LAA08562; Fri, 20 Jun 1997 11:18:39 +1000 (EST) Message-ID: <19970620111839.40700@rf900.physics.usyd.edu.au> Date: Fri, 20 Jun 1997 11:18:39 +1000 From: David Dawes To: hackers@freebsd.org Subject: Re: xperfmon++ problem (again) References: <33956BBB.1BB@nospam.com> <5n7bk7$osi@uriah.heep.sax.de> <339863C7.1DF5@nospam.com> <5nbrkn$2h6@uriah.heep.sax.de> <339D9548.7B07@nospam.com> <5ob5e7$31j@ui-gate.utell.co.uk> <5obor4$58o@ui-gate.utell.co.uk> <199706191725.SAA00390@utell.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199706191725.SAA00390@utell.co.uk>; from Brian Somers on Thu, Jun 19, 1997 at 06:25:50PM +0100 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, Jun 19, 1997 at 06:25:50PM +0100, Brian Somers wrote: >[cc'd to jmz@FreeBSD.org] >[cc'd to freebsd-hackers@FreeBSD.org] >[posted to comp.unix.bsd.freebsd.misc] >> Now this is *really* bad news AFAIK. X provides the following in >> FreeBSD.cf: >> #define Malloc0ReturnsNull NO >> >> but I don't know of any provisions for malloc returning a pointer >> and realloc returning NULL :( >> >> We could always do a simple patch to this file, but is this the >> right way to go ? > >FWIW, this is the patch - it solves my knews problem, but isn't >*really* the right answer :| Copy it to >/usr/ports/x11/XFree86/patches/patch-af, and just "make". The right answer in my opinion is to change the definition of Malloc0ReturnsNULL back to YES in FreeBSD.cf. That won't cause any problems for the case where malloc(0) returns a non-NULL pointer. David From owner-freebsd-hackers Thu Jun 19 18:46:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA02722 for hackers-outgoing; Thu, 19 Jun 1997 18:46:00 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA02716; Thu, 19 Jun 1997 18:45:57 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id TAA01010; Thu, 19 Jun 1997 19:45:46 -0600 (MDT) Message-Id: <199706200145.TAA01010@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Jared Proudfoot cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI Problems In-reply-to: Your message of "Thu, 19 Jun 1997 16:09:56 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Jun 1997 20:44:15 -0600 From: "Justin T. Gibbs" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >The machine will lock up periodically, giving SCSI drive errors. Here's >the errors I've been getting, the error as reported in /var/log/messages >and a copy of my dmesg output: > >sd1(ahc0:5:0): UNIT ATTENTION asc:29,1 retires: 4 >SCB: 0x1 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 >From the sense table of the new SCSI code: /* DTLPWRSOMCAE */{0x29, 0x01, "Power on occurred" } It looks like you either have a bad power supply or the connector to your drive is worn or loose. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hackers Thu Jun 19 18:47:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA02809 for hackers-outgoing; Thu, 19 Jun 1997 18:47:02 -0700 (PDT) Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA02803 for ; Thu, 19 Jun 1997 18:46:59 -0700 (PDT) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by pahtoh.cwu.edu (8.8.5/8.8.5) with ESMTP id SAA01947; Thu, 19 Jun 1997 18:46:57 -0700 (PDT) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.5/8.8.5) with SMTP id SAA14734; Thu, 19 Jun 1997 18:46:56 -0700 (PDT) Date: Thu, 19 Jun 1997 18:46:56 -0700 (PDT) From: Chris Timmons To: David Dawes cc: hackers@FreeBSD.ORG Subject: Re: xperfmon++ problem (again) In-Reply-To: <19970620111839.40700@rf900.physics.usyd.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 While we're looking at FreeBSD.cf, could we add -pipe to be a default gcc option? It really has a profound effect... -Chris From owner-freebsd-hackers Thu Jun 19 18:55:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA03250 for hackers-outgoing; Thu, 19 Jun 1997 18:55:40 -0700 (PDT) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA03243 for ; Thu, 19 Jun 1997 18:55:17 -0700 (PDT) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id LAA08629; Fri, 20 Jun 1997 11:54:09 +1000 (EST) Message-ID: <19970620115409.62437@rf900.physics.usyd.edu.au> Date: Fri, 20 Jun 1997 11:54:09 +1000 From: David Dawes To: Chris Timmons Cc: hackers@FreeBSD.ORG Subject: Re: xperfmon++ problem (again) References: <19970620111839.40700@rf900.physics.usyd.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Chris Timmons on Thu, Jun 19, 1997 at 06:46:56PM -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Jun 19, 1997 at 06:46:56PM -0700, Chris Timmons wrote: > >While we're looking at FreeBSD.cf, could we add -pipe to be a default gcc >option? It really has a profound effect... You can add it to your host.def. We don't plan on adding things like this to the default .cf files. I would argue that if -pipe is a big win in all situations, it should be turned on by default in gcc itself. David From owner-freebsd-hackers Thu Jun 19 19:02:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA03464 for hackers-outgoing; Thu, 19 Jun 1997 19:02:12 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA03454 for ; Thu, 19 Jun 1997 19:02:07 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) id VAA21630; Thu, 19 Jun 1997 21:57:33 -0400 (EDT) Message-ID: <19970619215732.54070@vinyl.quickweb.com> Date: Thu, 19 Jun 1997 21:57:32 -0400 From: Mark Mayo To: Michael Smith Cc: Mark Mayo , freebsd-hackers@FreeBSD.ORG Subject: Re: make world error in RELENG_2_2 References: <19970619182720.20258@vinyl.quickweb.com> <199706192341.JAA00235@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: <199706192341.JAA00235@genesis.atrad.adelaide.edu.au>; from Michael Smith on Fri, Jun 20, 1997 at 09:11:03AM +0930 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Jun 20, 1997 at 09:11:03AM +0930, Michael Smith wrote: > Mark Mayo stands accused of saying: > > > > I realize that. I just wanted to see if the error popped up that way. Turns > > out it doesn't. I ended up just doing a "make -k world" and manually > > building tcl afterwards. Note that I did > > cd /usr/src/include > > make > > make install > > > > on the second try before running make world. This *should* be updating my > > /usr/include , no? > > No. "make includes" at the top level does that. Yeah. However, I still don't understand why my header files are screwed. Here's what I'm confused about: 'make world' fairly early in the game does a 'make includes'. Based on this I assumed that I didn't have to manually do a 'make includes' myself. Result: doing a 'make includes' while the old /usr/include still existed didn't get me a clean build. After following the advice of Jordan and Mike, I did cd /usr/include rm -rf * cd /usr/src make includes Result: cd /usr/src/include; install -C -o bin -g bin -m 444 a.out.h ar.h assert.h bitstring.h ctype.h db.h dirent.h disktab.h err.h f2c.h fnmatch.h fstab.h fts.h glob.h grp.h strhash.h histedit.h kvm.h limits.h link.h locale.h malloc.h memory.h mpool.h ndbm.h netdb.h nl_types.h nlist.h paths.h pthread.h pthread_np.h pwd.h ranlib.h regex.h regexp.h resolv.h rune.h runetype.h setjmp.h sgtty.h signal.h stab.h stddef.h stdio.h stdlib.h string.h strings.h struct.h sysexits.h tar.h time.h timers.h ttyent.h unistd.h utime.h utmp.h vis.h /usr/include cd /usr/src/include/arpa; install -C -o bin -g bin -m 444 ftp.h inet.h nameser.h telnet.h tftp.h /usr/include/arpa usage: install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop. *** Error code 1 Hmm. Seems like the install program fails when there's no existing stuff. Soooo, I grabbed a copy of /usr/include/* from an up and running 2.2.2 machine, put them in my /usr/include and then did 'make includes'. It worked. I did notice that the tcl libraries (which are my problem) were replaced (I mean the include files for the tcl libraries..). I'm hoping this is where the problem is. I also removed the depend files from the src tree: root:{126}/usr/src % find . -name "*depend*" -print ./contrib/groff/pic/depend ./contrib/libg++/libg++/src/depend ./contrib/libg++/libg++/tests/depend ./contrib/libg++/libio/depend root:{127}/usr/src % find . -name "*depend*" -delete Then I removed the entire object tree rm -rf /usr/obj/* I checked one more time with CVSUP to see that I have everthing, and I do. I'm doing to do a make world now to see if it works. I don't think that the above procedure is entirely obvious. II also shouldn't have to grab files from another machine to build my include directory. make includes should do it for me. The point of all of this is quite simple: I had a problem. I even worked out my problem (make -k world;make tcl separetly afterwards) in my own clutsy way. I wanted to see if other were having the same sort of problem so I posted to -hackers. All you did was give a frustrated "you're wrong. you must have hosed you machine. there's nothing wrong with 2.2". You then proceded to imply that such questions were asked by "incompetent" people, and suggested that any competent person would figure out how to do it. Thank yo very much. What an intelligent response. I'm not responding to your post directly, since I have no desire to get in a flame war. I almost replied and called you and ignorant, elitist asshole. But upon pondering the situation, I really don't think you are. You're just frustrated by "incompetent people". Of course, what you would call incompetent I would call "inexperienced". Fine. I'm "incompetent". I asked a question. I didn't criticise FreeBSD. I didn't even complain about it. I just wanted to find a nice solution to my problem, since my incompetent solution is just a hack. Fuck me for wanting to learn something. You see, believe it or not, I don't know as much as you about FreeBSD. I'm 21 years old, and I've only been using Unix for under 2 years. I've only been using FreeBSD for 1.5 years. I'm trying to learn as much as I can as quickly as I can, but I'm not familiar with the details of the build mechanism, and I'm not a C guru. Maybe someday I will, but for now I'm just a learner. So in the future, if it bugs you to have to deal with us newbies, just don't read our emails. That way we won't bug you, and you won't bug us. In the mean time, I've been documenting everything I learn about FreeBSD so the other newbies like myself don't have to bug your majesty. http://vinyl.quickweb.com/mark/FreeBSD I'll be adding a section entitles "What to do when make world fails", that will go throough some of the common problems that might occur during dramatic reorganizations of the source tree, and how to get around them. Thanks to Jordan and others who actually responded with suggestions. -Mark > > -- > ]] 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 [[ -- ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ---------------------------------------------------------------------------- University degrees are a bit like adultery: you may not want to get involved with that sort of thing, but you don't want to be thought incapable. -Sir Peter Imbert From owner-freebsd-hackers Thu Jun 19 19:09:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA03738 for hackers-outgoing; Thu, 19 Jun 1997 19:09:48 -0700 (PDT) Received: from sendero.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA03728; Thu, 19 Jun 1997 19:09:39 -0700 (PDT) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.5) id TAA01977; Thu, 19 Jun 1997 19:09:38 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 19 Jun 1997 19:09:38 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Brian Tao Subject: Re: Announcement: New DPT RAID Controller Driver Available Cc: FREEBSD-SCSI , FREEBSD-HACKERS Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Brian Tao; On 18-Jun-97 you wrote: > On Mon, 16 Jun 1997, Simon Shapiro wrote: > > > > I have evaluated, tested and even participated in the design of more > > than one I/O subsystem in my short life. The StorageWorks solution > > is the best I have ever seen. not perfect, Just the BEST. > > I should add that NetApp also uses the DEC StorageWorks shelves > and canisters for their 2GB and 4GB configurations, and if it's good > enough for them, it's good enough for me. ;-) Mounting drives > inside the canisters is a little tricky at first, but you get the hang > of it pretty quickly. The ones we have are plastic, so I imagine the > heat dissipation isn't the best. Netapp went with a Eurologics > product (metal extruded cases) for their 9GB shelves. You know, the canister problem is an interesting one. I was once involved in a project where we build a database server with 3,000 (no typo) drives, so canisters and packing density were somewhat important :-). An excellent mechanical engineer designed a wonderful metal system (both canisters and carriers). We had up to 30% perofrmance loss on random seeks with system. It baffled anyone until another engineer decided to test the drives on his desk, outside the box, outside the carriers - Yes, the performance was back. Turns out soft errors were masked and the rigid but ringing-resonating nature of steel and the high packing density caused drives to resonate the cabinets and cause miseeks. For other, unrelated problems, we decided to use the DEC canisters. Smug as a cat with a bird in mouth we loaded 200 drives into a cabinet, smirking and making snide remarks about the silly plastic carriers - No data loss, no perfromance loss. Asking the DEC engineers about why they choose platic, they just smiled and shrugged... Simon BTW, the little flex-circuit between the drive and the canister plug makes you think too. Simon From owner-freebsd-hackers Thu Jun 19 19:54:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA05563 for hackers-outgoing; Thu, 19 Jun 1997 19:54:41 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA05282; Thu, 19 Jun 1997 19:48:40 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id UAA05312; Thu, 19 Jun 1997 20:53:47 -0500 (EST) Date: Thu, 19 Jun 1997 20:53:46 -0500 (EST) From: John Fieber Reply-To: John Fieber To: brian@awfulhak.org, brian@utell.co.uk cc: jmz@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: realloc() quirk (was: Re: xperfmon++ problem (again)) In-Reply-To: <199706191725.SAA00390@utell.co.uk> 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, 19 Jun 1997, Brian Somers wrote: [Way to many quotes to get straight, so I won't even try.] > >>>> > Sorry. I was doing this from memory. The message was > >>>> > > >>>> > Error: Cannot perform realloc > >>>> > >>>> Well, i was checking all ``Cannot'' messages in the source, and none > >>>> didn't come close to what you've mentioned. [snip] > >>> [pozzo:/usr/home/mefoster] strings /usr/X11R6/lib/libXt.so.6.0 | grep > >>> perform > >>> Cannot perform %s [snip] > >> Ouch. I just built XFree86-3.3, and I'm now getting this from knews. > >> I rebuilt knews too - no change. > >> > >> It happens just after I press the post key !!!!!! [snip] > > Well, xc/lib/Xt/Alloc.c does the realloc (in function XtRealloc). > > I changed the diagnostic so that it says how much we're allocating, > > and it comes out as zero ! Ah ha ! [snip] > > Now this is *really* bad news AFAIK. X provides the following in > > FreeBSD.cf: > > #define Malloc0ReturnsNull NO [snip] > FWIW, this is the patch - it solves my knews problem, but isn't > *really* the right answer :| Copy it to > /usr/ports/x11/XFree86/patches/patch-af, and just "make". The problem is that malloc(0) and realloc(ptr, 0) behave differently but X assumes they behave the same. This was fixed recently in -current but phk has not (that I noticed) committed it to RELENG_2_2. However, I grabbed malloc.c from -current and re-built my 2.2.1 libc and both knews and xperfmon++ work fine. I think this is a pretty important thing to get fixed in RELENG_2_2. It might even be worthwhile to make updated copies of libc available to people who can't easily upgrade or rebuild their libc. -john From owner-freebsd-hackers Thu Jun 19 20:04:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA05992 for hackers-outgoing; Thu, 19 Jun 1997 20:04:52 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA05987; Thu, 19 Jun 1997 20:04:50 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id VAA02058; Thu, 19 Jun 1997 21:04:29 -0600 (MDT) Message-Id: <199706200304.VAA02058@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Simon Shapiro cc: Brian Tao , FREEBSD-SCSI , FREEBSD-HACKERS Subject: Re: Announcement: New DPT RAID Controller Driver Available In-reply-to: Your message of "Thu, 19 Jun 1997 19:09:38 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Jun 1997 22:02:57 -0600 From: "Justin T. Gibbs" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >An excellent mechanical engineer designed a wonderful metal system (both >canisters and carriers). We had up to 30% perofrmance loss on random >seeks with system. It baffled anyone until another engineer decided to >test the drives on his desk, outside the box, outside the carriers - >Yes, the performance was back. Turns out soft errors were masked and >the rigid but ringing-resonating nature of steel and the high packing >density caused drives to resonate the cabinets and cause miseeks. Pluto's drive sled design uses a very simple and cheap suspension design to deal with this very problem. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hackers Thu Jun 19 20:12:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA06343 for hackers-outgoing; Thu, 19 Jun 1997 20:12:03 -0700 (PDT) Received: from pcpsj.pfcs.com (g03WxVX7as3kf2FsJ89UH1IOLW0ZJp0M@harlan.fred.net [205.252.219.31]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA06316 for ; Thu, 19 Jun 1997 20:11:55 -0700 (PDT) Received: from mumps.pfcs.com (mumps.pfcs.com [192.52.69.11]) by pcpsj.pfcs.com (8.6.12/8.6.9) with SMTP id XAA05483 for ; Thu, 19 Jun 1997 23:11:45 -0400 Received: from localhost by mumps.pfcs.com with SMTP id AA16809 (5.67b/IDA-1.5 for ); Thu, 19 Jun 1997 23:11:30 -0400 To: hackers@freebsd.org Subject: "make reinstall"? Date: Thu, 19 Jun 1997 23:11:29 -0300 Message-Id: <16807.866776289@mumps.pfcs.com> From: Harlan Stenn Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have done a "make world" on a current 2.2-STABLE tree. I went to another machine (2.1-stable), and did an (effective) NFS mount of the build machine's /usr/src and /usr/obj (I used symlinks to the right places on an amd-controlled /net/ dir). I do a "make reinstall", and after cleaning up some obvious stuff (added mail to /etc/group, copied over libc.so.3.0 and /usr/bin/install), but the "make reinstall" falls over trying to install klm_prot.h in include/rpcsvc . I haven't been able to figure this one out yet. Suggestions? (And I know about login.conf, so that won't bite me when the time comes.) Thanks... H From owner-freebsd-hackers Thu Jun 19 20:24:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA06868 for hackers-outgoing; Thu, 19 Jun 1997 20:24:00 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA06850 for ; Thu, 19 Jun 1997 20:23:52 -0700 (PDT) Received: from awfulhak.demon.co.uk (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id DAA29697; Fri, 20 Jun 1997 03:17:12 +0100 (BST) Message-Id: <199706200217.DAA29697@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: David Dawes cc: hackers@FreeBSD.ORG Subject: Re: xperfmon++ problem (again) In-reply-to: Your message of "Fri, 20 Jun 1997 11:18:39 +1000." <19970620111839.40700@rf900.physics.usyd.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Jun 1997 03:17:12 +0100 From: Brian Somers Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [.....] > >FWIW, this is the patch - it solves my knews problem, but isn't > >*really* the right answer :| Copy it to > >/usr/ports/x11/XFree86/patches/patch-af, and just "make". > > The right answer in my opinion is to change the definition of > Malloc0ReturnsNULL back to YES in FreeBSD.cf. That won't cause > any problems for the case where malloc(0) returns a non-NULL pointer. Are you sure that when Malloc0ReturnsNULL is set to YES, pointer values returned from malloc(0) are freed ? Maybe there's some nasty code that says something like #if !Malloc0ReturnsNUL /* or whatever */ if (!mallocSize) free(ptr); #endif although I'd hope not ! > David From owner-freebsd-hackers Thu Jun 19 20:40:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA07839 for hackers-outgoing; Thu, 19 Jun 1997 20:40:43 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA07823 for ; Thu, 19 Jun 1997 20:40:38 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA01931; Fri, 20 Jun 1997 13:10:09 +0930 (CST) From: Michael Smith Message-Id: <199706200340.NAA01931@genesis.atrad.adelaide.edu.au> Subject: Re: make world error in RELENG_2_2 In-Reply-To: <19970619215732.54070@vinyl.quickweb.com> from Mark Mayo at "Jun 19, 97 09:57:32 pm" To: mark@quickweb.com (Mark Mayo) Date: Fri, 20 Jun 1997 13:10:09 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, mark@quickweb.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 Mark Mayo stands accused of saying: > > Yeah. However, I still don't understand why my header files are screwed. > Here's what I'm confused about: > 'make world' fairly early in the game does a 'make includes'. Based on this > I assumed that I didn't have to manually do a 'make includes' myself. > Result: doing a 'make includes' while the old /usr/include still existed > didn't get me a clean build. After following the advice of Jordan and Mike, > I did > cd /usr/include > rm -rf * > cd /usr/src > make includes > > Result: > > cd /usr/src/include; install -C -o bin -g bin -m 444 a.out.h ar.h assert.h > bitstring.h ctype.h db.h dirent.h disktab.h err.h f2c.h fnmatch.h fstab.h fts.h > glob.h grp.h strhash.h histedit.h kvm.h limits.h link.h locale.h malloc.h > memory.h mpool.h ndbm.h netdb.h nl_types.h nlist.h paths.h pthread.h > pthread_np.h pwd.h ranlib.h regex.h regexp.h resolv.h rune.h runetype.h > setjmp.h sgtty.h signal.h stab.h stddef.h stdio.h stdlib.h string.h strings.h > struct.h sysexits.h tar.h time.h timers.h ttyent.h unistd.h utime.h utmp.h > vis.h /usr/include > cd /usr/src/include/arpa; install -C -o bin -g bin -m 444 ftp.h inet.h > nameser.h telnet.h tftp.h /usr/include/arpa > usage: install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 > install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 ... > fileN directory > install -d [-g group] [-m mode] [-o owner] directory ... > *** Error code 64 > Hmm. Looks like 'make includes' doesn't do the mtree stuff first. Can you read Makefiles? Do you understand the basic idea behind them? If not, now is the time to learn. I agree that install(1) should be giving you a helpful error message, and it's not. > I'll be adding a section entitles "What to do when make world fails", that > will go throough some of the common problems that might occur during > dramatic reorganizations of the source tree, and how to get around them. Here is a checklist you might want to include somewhere near the top where impatient people will find it. This isn't my work; if the author wants to be identified I'm sure they'll stand up and say so : 1. If your CPU is overclocked, shut up and don't bother us again. 2. Make absolutely sure your entire source tree is 100% up-to-date, using CVSup or CTM. 3. If you cheated in step 2, in any way whatsoever, shut up and don't bother us again. 4. Execute these commands as root: rm -rf /usr/obj mkdir /usr/obj find /usr/src -name obj -type l | xargs rm make world 5. If you didn't type the commands in step 4 precisely as directed, shut up and don't bother us again. 6. If it still fails, wait 24 hours. Then repeat steps 1-5 again one time. 7. If you didn't wait 24 hours and then repeat steps 1-5 exactly as directed, shut up and don't bother us again. 8. If it still fails in exactly the same way as the first time, tell us about it. Ok, so they may want toning down a bit for general consumption... -- ]] 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 Jun 19 20:54:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA08634 for hackers-outgoing; Thu, 19 Jun 1997 20:54:10 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA08627 for ; Thu, 19 Jun 1997 20:54:06 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA02112; Fri, 20 Jun 1997 13:23:59 +0930 (CST) From: Michael Smith Message-Id: <199706200353.NAA02112@genesis.atrad.adelaide.edu.au> Subject: Re: "make reinstall"? In-Reply-To: <16807.866776289@mumps.pfcs.com> from Harlan Stenn at "Jun 19, 97 11:11:29 pm" To: Harlan.Stenn@pfcs.com (Harlan Stenn) Date: Fri, 20 Jun 1997 13:23:59 +0930 (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 Harlan Stenn stands accused of saying: > I have done a "make world" on a current 2.2-STABLE tree. > > I went to another machine (2.1-stable), and did an (effective) NFS mount > of the build machine's /usr/src and /usr/obj (I used symlinks to the > right places on an amd-controlled /net/ dir). > > I do a "make reinstall", and after cleaning up some obvious stuff (added > mail to /etc/group, copied over libc.so.3.0 and /usr/bin/install), but > the "make reinstall" falls over trying to install klm_prot.h in > include/rpcsvc . > > I haven't been able to figure this one out yet. > > Suggestions? Check and make sure that the directory and the file exist for starters; they're usually the two reasons reinstalls fail. Also check that the directory is a real directory, not a link to somewhere that doesn't exist anymore. I am assuming that you're just getting the "no error message" message from install... > H -- ]] 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 Jun 19 21:15:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA09233 for hackers-outgoing; Thu, 19 Jun 1997 21:15:23 -0700 (PDT) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA09224 for ; Thu, 19 Jun 1997 21:15:17 -0700 (PDT) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id OAA08955; Fri, 20 Jun 1997 14:09:10 +1000 (EST) Message-ID: <19970620140910.56164@rf900.physics.usyd.edu.au> Date: Fri, 20 Jun 1997 14:09:10 +1000 From: David Dawes To: Brian Somers Cc: hackers@FreeBSD.ORG Subject: Re: xperfmon++ problem (again) References: <19970620111839.40700@rf900.physics.usyd.edu.au> <199706200217.DAA29697@awfulhak.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199706200217.DAA29697@awfulhak.demon.co.uk>; from Brian Somers on Fri, Jun 20, 1997 at 03:17:12AM +0100 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Jun 20, 1997 at 03:17:12AM +0100, Brian Somers wrote: >[.....] >> >FWIW, this is the patch - it solves my knews problem, but isn't >> >*really* the right answer :| Copy it to >> >/usr/ports/x11/XFree86/patches/patch-af, and just "make". >> >> The right answer in my opinion is to change the definition of >> Malloc0ReturnsNULL back to YES in FreeBSD.cf. That won't cause >> any problems for the case where malloc(0) returns a non-NULL pointer. > >Are you sure that when Malloc0ReturnsNULL is set to YES, pointer >values returned from malloc(0) are freed ? Maybe there's some nasty >code that says something like > >#if !Malloc0ReturnsNUL /* or whatever */ >if (!mallocSize) > free(ptr); >#endif > >although I'd hope not ! In the core X11 code, the behaviour of free is not affected by the setting of Malloc0ReturnsNULL. For example, XtFree() is: #define Xfree(ptr) free(ptr) void XtFree(ptr) char *ptr; { if (ptr != NULL) Xfree(ptr); } David From owner-freebsd-hackers Thu Jun 19 21:53:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA10813 for hackers-outgoing; Thu, 19 Jun 1997 21:53:44 -0700 (PDT) Received: from TomQNX.tomqnx.com (root@ott-pm1-25.comnet.ca [206.75.140.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA10799 for ; Thu, 19 Jun 1997 21:53:15 -0700 (PDT) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m0wevep-000A41C; Fri, 20 Jun 1997 00:50:47 -0400 (EDT) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: Re: make world error in RELENG_2_2 In-Reply-To: <24525.866752787@time.cdrom.com> from "Jordan K. Hubbard" at "Jun 19, 97 01:39:47 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 20 Jun 1997 00:50:47 -0400 (EDT) Cc: mike@sentex.net, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (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 suspect that there IS some other problem, and it is/was with cvsup. I don't know why or how or if I contributed to it:-) I too had a screwed-up tree a few weeks ago. My tree was set up to point to my 2.2.1R cdrom using lndir and after a few cvsup runs, make world bombed. I found that if I simply removed the offending section of the tree and reran cvsup, which checked out the missing items, that problem went away. Other problems appeared later in make world. I finally blew away the entire tree and /usr/sup and started over. No further make world problems have been experienced (so far). I have also experienced Tcl/Tk problems that were definitely caused by incompatibilities between the base release version and the various versions brought in as part of the 'ports' process. There are bad problems with this, as the versions have different include files, are loaded in different locations, etc. etc. It is only a suggestion, but I think that the ports process needs the capability to specify/look for a 'minimum release version' for a dependant package, rather than an absolute. For example if a port requires Tcl-4.1 and Tcl-4.2 exists, then it should not find it necessary to load Tcl-4.1 on top of everything, but carry on using the later version. Regards, Tom > > If there is nothing wrong, why were so many people having problems all of a > > sudden? I would say the lack of the login.conf in /etc was a 'problem'... > > That was a problem. Our problem. However, in every single case that > I've seen the world target falling over so far, it has been: > > a) A 2.2.x tree splatted on top of a previous generation src > tree (and that's bad). > > b) A bogus cvsup file, missing some crucial section of the > source code (src-all is a good target and highly recommended). > > c) Stale depends or includes. > > Also note that RELENG_2_2 recently switched from SHARED=symlinks > to SHARED=copies by default. This is not a 'problem' to be fixed > so much as a change to simply be cognizant of, and if you've any > doubts then blow away /usr/include and start over with a make includes; > in all cases, the solution is fairly simple when you think about it. > > Jordan > From owner-freebsd-hackers Thu Jun 19 22:20:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA11767 for hackers-outgoing; Thu, 19 Jun 1997 22:20:58 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA11758 for ; Thu, 19 Jun 1997 22:20:50 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id HAA24492 for hackers@FreeBSD.ORG; Fri, 20 Jun 1997 07:20:47 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id HAA04940; Fri, 20 Jun 1997 07:12:10 +0200 (MET DST) Message-ID: <19970620071210.TQ58637@uriah.heep.sax.de> Date: Fri, 20 Jun 1997 07:12:10 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: xperfmon++ problem (again) References: <19970620111839.40700@rf900.physics.usyd.edu.au> <19970620115409.62437@rf900.physics.usyd.edu.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970620115409.62437@rf900.physics.usyd.edu.au>; from David Dawes on Jun 20, 1997 11:54:09 +1000 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As David Dawes wrote: > I would argue that if -pipe is a > big win in all situations, it should be turned on by default in gcc > itself. It will have a speed impact on small-memory machines. Now of course, if we could make the XFree86 templates pick up the setting for CFLAGS from /etc/make.conf ;-), but i figure that's not possible, due to the name conflict and the way the X11 templates build up their own CFLAGS. -- 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 Jun 19 22:23:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA11841 for hackers-outgoing; Thu, 19 Jun 1997 22:23:23 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA11829 for ; Thu, 19 Jun 1997 22:23:18 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id HAA24522; Fri, 20 Jun 1997 07:23:16 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id HAA04965; Fri, 20 Jun 1997 07:20:11 +0200 (MET DST) Message-ID: <19970620072011.RM43153@uriah.heep.sax.de> Date: Fri, 20 Jun 1997 07:20:11 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: brianc@pobox.com (Brian Campbell) Subject: Re: fs recovery References: <19970619173858.39930@pobox.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970619173858.39930@pobox.com>; from Brian Campbell on Jun 19, 1997 17:38:58 -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Brian Campbell wrote: > I used fsdb to look at the first 150k inodes and found an expected > mixture of directories and inodes. Is there an easy way to recreate > my root directory and link some of these directories (presumably > the ones whose parent was inode 2? how do I find that out?) into > the root? What happens if you recreate inode 2 as an (empty) root directory, and leave the rest to fsck? IMHO, it should find the orphaned members of the previous root directory, and drop them into lost+found. -- 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 Jun 19 22:27:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA12019 for hackers-outgoing; Thu, 19 Jun 1997 22:27:15 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA12013 for ; Thu, 19 Jun 1997 22:27:12 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id WAA26038; Thu, 19 Jun 1997 22:27:07 -0700 (PDT) To: Mike Tancsa cc: freebsd-hackers@FreeBSD.ORG Subject: Re: make world error in RELENG_2_2 In-reply-to: Your message of "Thu, 19 Jun 1997 17:17:04 EDT." <3.0.2.32.19970619171704.02693930@sentex.net> Date: Thu, 19 Jun 1997 22:27:07 -0700 Message-ID: <26034.866784427@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > You have sort of proved my point... As I said before, I try and follow the > mailling lists as closely as possbile for any caveats / changes to the > cvsup process... My sup file consists of the following > ... I think the real problem here is that some folks are simply unclear on the amount of "expertise" required to use /usr/src as an effective upgrade tool. You ask why we don't document the world target - but we do! /usr/src/Makefile is the documentation for the world target, and before you start laughing and figuring 'ol Jordan is copping-out here, let me just explain that for anything which requires building from sources, we *definitely assume* a very comfortable degree of knowledge in how to analyze Makefiles and see exactly what they are doing, up to and including making inferences about where the dependencies are and, if necessary, taking whatever steps are necessary to ensure that a failed build is jump-started from the right place. The world target *does* generally work, don't get me wrong, but it's also exceedingly easy to get to a point where the delta between where you are and where /usr/src would like to take you has diverged too far to allow "world" to actually work. In such cases, you need to know how to shepard the process through by hand and the Makefile truly says it all where that's concerned. I can't imagine any more effective or concise body of documentation than the build system itself to someone who knows what they're doing, and someone who doesn't know what they're doing really shouldn't be using the world target - they should be hanging back at the major release points and upgrading via binaries only. We're proud of our integrated build system and, given that it's also often the quickest way of getting a fix into a user's tree, we do sometimes tend to recommend it as a solution in situations where we really shouldn't. Building from source is NOT a generic, targeted-at-the-end-user kinda mechanism and I'm sorry if we ever lent that impression. It's not. It's for software engineering types to use, those who are more than comfortable with the idea of reading Makefiles and figuring it out, and in that sense I'd say it's probably as documented as it's ever going to be. This is also hardly the "elitist" stance some might see it as - it's just being honest about how this process works and hardly unknown in this industry. If you walked into IBM tomorrow as an engineer, for example, and were tasked with porting some large, obscure product of theirs from AIX to another UNIX variant, do you think you'd find a source tree with a carefully documented build system, all easily understandable in a ten minute study? Ha Ha. No. What you'd find instead is almost certainly something which was completely opaque to the average joe and aimed strictly at those who know how to take a build system apart in its entirety, say "aha, so THAT is what you idiots had in mind", and then adapt it to the new target system (or, as I've frequently done in such situations, do it over since the original designers had all the pan-UNIX expertise of a team of Visual Basic programmers and did it wrong for anything _but_ AIX). That's just the nature of the beast, and if anything I'd say that FreeBSD has one of the _easiest_ build systems to understand. You really have it easy, so quit whinging and start reading the Makefiles in the future, OK? :-) Jordan From owner-freebsd-hackers Thu Jun 19 22:38:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA12455 for hackers-outgoing; Thu, 19 Jun 1997 22:38:11 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA12447 for ; Thu, 19 Jun 1997 22:38:05 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wewLj-0003ru-00; Thu, 19 Jun 1997 22:35:07 -0700 Date: Thu, 19 Jun 1997 22:35:07 -0700 (PDT) From: Tom Samplonius To: Harlan Stenn cc: hackers@freebsd.org Subject: Re: "make reinstall"? In-Reply-To: <16807.866776289@mumps.pfcs.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, 19 Jun 1997, Harlan Stenn wrote: > I have done a "make world" on a current 2.2-STABLE tree. > > I went to another machine (2.1-stable), and did an (effective) NFS mount > of the build machine's /usr/src and /usr/obj (I used symlinks to the > right places on an amd-controlled /net/ dir). > > I do a "make reinstall", and after cleaning up some obvious stuff (added > mail to /etc/group, copied over libc.so.3.0 and /usr/bin/install), but > the "make reinstall" falls over trying to install klm_prot.h in > include/rpcsvc . > > I haven't been able to figure this one out yet. > > Suggestions? > > (And I know about login.conf, so that won't bite me when the time > comes.) > > Thanks... > > H > > This is bug in "make reinstall". I've run into this every time with it. >From memory, the klm_prot.h is in the wrong directory. It is either in the obj, and belongs in the src directory, or vice versa. Manually fix it, and it will work fine. I have no idea why "make world" handles this, and only "reinstall" breaks. Tom From owner-freebsd-hackers Thu Jun 19 22:39:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA12497 for hackers-outgoing; Thu, 19 Jun 1997 22:39:03 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA12489 for ; Thu, 19 Jun 1997 22:38:55 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wewMP-0003ry-00; Thu, 19 Jun 1997 22:35:49 -0700 Date: Thu, 19 Jun 1997 22:35:49 -0700 (PDT) From: Tom Samplonius To: Michael Smith cc: hackers@freebsd.org Subject: Re: "make reinstall"? In-Reply-To: <199706200353.NAA02112@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Jun 1997, Michael Smith wrote: > Harlan Stenn stands accused of saying: > > I have done a "make world" on a current 2.2-STABLE tree. > > > > I went to another machine (2.1-stable), and did an (effective) NFS mount > > of the build machine's /usr/src and /usr/obj (I used symlinks to the > > right places on an amd-controlled /net/ dir). > > > > I do a "make reinstall", and after cleaning up some obvious stuff (added > > mail to /etc/group, copied over libc.so.3.0 and /usr/bin/install), but > > the "make reinstall" falls over trying to install klm_prot.h in > > include/rpcsvc . > > > > I haven't been able to figure this one out yet. > > > > Suggestions? > > Check and make sure that the directory and the file exist for starters; > they're usually the two reasons reinstalls fail. Also check that the > directory is a real directory, not a link to somewhere that doesn't > exist anymore. > > I am assuming that you're just getting the "no error message" message from > install... > > > H > > -- > ]] 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 [[ > > Actually the above is a bug in "reinstall". Strangely "world" works fine. Tom From owner-freebsd-hackers Thu Jun 19 22:57:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA13432 for hackers-outgoing; Thu, 19 Jun 1997 22:57:14 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA13426 for ; Thu, 19 Jun 1997 22:57:12 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id WAA26163; Thu, 19 Jun 1997 22:56:59 -0700 (PDT) To: Mark Mayo cc: Michael Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: make world error in RELENG_2_2 In-reply-to: Your message of "Thu, 19 Jun 1997 18:27:20 EDT." <19970619182720.20258@vinyl.quickweb.com> Date: Thu, 19 Jun 1997 22:56:59 -0700 Message-ID: <26160.866786219@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Good for you... but what have I done wrong - this is the question I'm begging > to know. I started with a fresh install of 2.2.1 from CD, created a cvsup > download of src-all, and did make world. There was NO /usr/obj directory You didn't install /usr/src from 2.2.1, right? That would be stupid since you're just going to cvsup over it, after all. :-) > Well, whatever the case, when I cvsup down the tree "over top" of the 2.2.1 > Release, I get a bad tree. This also happened before when I was Yes, you'll almost always get a bad tree when you do that. Don't do that. Things move, you know, and when they do this practice will bite you really hard, right on the ass. Jordan From owner-freebsd-hackers Thu Jun 19 23:21:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA14490 for hackers-outgoing; Thu, 19 Jun 1997 23:21:26 -0700 (PDT) Received: from relay1.cit.ru (relay1.cit.ru [193.125.82.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA14480 for ; Thu, 19 Jun 1997 23:21:08 -0700 (PDT) Received: from free.tula.su by relay1.cit.ru with UUCP id KAA13566; (8.8.2-MVC-141196/vak/1.9) Fri, 20 Jun 1997 10:20:10 +0400 (MSD) Received: from blik.UUCP by free.tula.su with UUCP id KAA01990; (8.8.2-MVC-141196/vak/1.9) 9b Received: by blik.samara.su id AA08588 (5.65/IDA-simtel for hackers@freebsd.org); Fri, 20 Jun 1997 11:59:37 +0500 To: hackers@freebsd.org Message-Id: Organization: Center of Information Technology From: "Igor" Date: Fri, 20 Jun 97 11:59:36 +0500 X-Mailer: BML [UNIX Beauty Mail v.1.39] Subject: kernel's debugging, next Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>what are the methods of debugging kernel's code ? >trace code is one. Can I do on-line debugging (not post-mortem) kernel's code and how ? Where can I read instructions ? --- igor@blik.samara.su (Igor) From owner-freebsd-hackers Thu Jun 19 23:37:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA15396 for hackers-outgoing; Thu, 19 Jun 1997 23:37:16 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA15388 for ; Thu, 19 Jun 1997 23:37:14 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id XAA26314; Thu, 19 Jun 1997 23:37:07 -0700 (PDT) To: Harlan Stenn cc: hackers@FreeBSD.ORG Subject: Re: "make reinstall"? In-reply-to: Your message of "Thu, 19 Jun 1997 23:11:29 -0300." <16807.866776289@mumps.pfcs.com> Date: Thu, 19 Jun 1997 23:37:07 -0700 Message-ID: <26310.866788627@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I do a "make reinstall", and after cleaning up some obvious stuff (added > mail to /etc/group, copied over libc.so.3.0 and /usr/bin/install), but > the "make reinstall" falls over trying to install klm_prot.h in > include/rpcsvc . This target has never actually worked for doing what you're trying to do. :( Jordan From owner-freebsd-hackers Thu Jun 19 23:43:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA15673 for hackers-outgoing; Thu, 19 Jun 1997 23:43:21 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA15668 for ; Thu, 19 Jun 1997 23:43:19 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id XAA26362; Thu, 19 Jun 1997 23:41:50 -0700 (PDT) To: tom@tomqnx.com (Tom Torrance at home) cc: mike@sentex.net, freebsd-hackers@FreeBSD.ORG Subject: Re: make world error in RELENG_2_2 In-reply-to: Your message of "Fri, 20 Jun 1997 00:50:47 EDT." Date: Thu, 19 Jun 1997 23:41:49 -0700 Message-ID: <26359.866788909@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I suspect that there IS some other problem, and it is/was with cvsup. > I don't know why or how or if I contributed to it:-) It's not a problem with cvsup. It's a fundamental flaw in the model of trying to "upgrade" a source tree by continually: a) Changing modified bits. b) Adding new ones. c) Not deleting the old ones. It's (c) which is the killer since you will eventually confuse the bezeesus out of the build system with old bits. Do you have the "delete" option turned on in your supfile? Jordan From owner-freebsd-hackers Fri Jun 20 00:21:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA17546 for hackers-outgoing; Fri, 20 Jun 1997 00:21:45 -0700 (PDT) Received: from deathstar.ml.org (adrian@deathstar.ml.org [203.62.152.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA17538 for ; Fri, 20 Jun 1997 00:21:31 -0700 (PDT) Received: from localhost (adrian@localhost) by deathstar.ml.org (8.8.5/8.7.3) with SMTP id PAA15724 for ; Fri, 20 Jun 1997 15:23:40 +0800 Date: Fri, 20 Jun 1997 15:23:40 +0800 (WST) From: Adrian Chadd To: freebsd-hackers@freebsd.org Subject: socket redirector Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey guys. I'm writing a quick socket redirector for something. Its run out of inetd, and basically opens a socket somewhere and acts as a pipe between the two. I'm using select(), and its working fine. The only problem I'm having is that I don't know how to tell when the remote end closes the connection down, so that I can just close everything down, and quit. Any ideas on how I'd do this? Thanks, -- Adrian Chadd | "Unix doesn't stop you from doing | stupid things because that would | stop you from doing clever things" From owner-freebsd-hackers Fri Jun 20 00:24:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA17698 for hackers-outgoing; Fri, 20 Jun 1997 00:24:18 -0700 (PDT) Received: from gatekeeper.barcode.co.il (gatekeeper.barcode.co.il [192.116.93.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA17663; Fri, 20 Jun 1997 00:24:06 -0700 (PDT) Received: (from nadav@localhost) by gatekeeper.barcode.co.il (8.8.5/8.6.12) id KAA21031; Fri, 20 Jun 1997 10:23:58 +0300 (IDT) Date: Fri, 20 Jun 1997 10:23:58 +0300 (IDT) From: Nadav Eiron To: Samy Touati cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: SMC 9332BDT Help me please... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 19 Jun 1997, Samy Touati wrote: > > > Hi, > > > In the rel notes of 2.2.2 it's clear that the SMC9332 BDT should work. > I installed one and it dies as soon as it gets probed by the kernel at > boot time. > The chipset 21140A is identified with pass 2.0 and it tries to enable the > 100TX port. The newer versions of the 21140A chipset are not supported by the current driver. However, a replacement (beta quality) driver is available at: http://www.3am-software.com Most people report it to work fine with the newer cards. Also look in the hackers list archives for discussions of newer de drivers. > > Is this card supported in 2.2.2 or in 3.0? > > > Thank you very much. > > Samy > > > Nadav From owner-freebsd-hackers Fri Jun 20 01:33:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA20773 for hackers-outgoing; Fri, 20 Jun 1997 01:33:38 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA20765 for ; Fri, 20 Jun 1997 01:33:33 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id SAA03739; Fri, 20 Jun 1997 18:03:01 +0930 (CST) From: Michael Smith Message-Id: <199706200833.SAA03739@genesis.atrad.adelaide.edu.au> Subject: Re: "make reinstall"? In-Reply-To: <26310.866788627@time.cdrom.com> from "Jordan K. Hubbard" at "Jun 19, 97 11:37:07 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 20 Jun 1997 18:03:01 +0930 (CST) Cc: Harlan.Stenn@pfcs.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > I do a "make reinstall", and after cleaning up some obvious stuff (added > > mail to /etc/group, copied over libc.so.3.0 and /usr/bin/install), but > > the "make reinstall" falls over trying to install klm_prot.h in > > include/rpcsvc . > > This target has never actually worked for doing what you're trying to > do. :( It _used_ to, actually. Back before building releases was an option for me (2.0.5 days IIRC), I used to do this quite a lot. > Jordan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Fri Jun 20 01:39:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA21101 for hackers-outgoing; Fri, 20 Jun 1997 01:39:06 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA21093 for ; Fri, 20 Jun 1997 01:39:03 -0700 (PDT) Received: (qmail 7894 invoked by uid 1000); 20 Jun 1997 08:39:05 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199706200304.VAA02058@pluto.plutotech.com> Date: Fri, 20 Jun 1997 01:39:04 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: "Justin T. Gibbs" Subject: Re: Announcement: New DPT RAID Controller Driver Available Cc: FREEBSD-HACKERS , FREEBSD-SCSI , Brian Tao Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi "Justin T. Gibbs"; On 20-Jun-97 you wrote: > >An excellent mechanical engineer designed a wonderful metal system (both > >canisters and carriers). We had up to 30% perofrmance loss on random > >seeks with system. It baffled anyone until another engineer decided to > >test the drives on his desk, outside the box, outside the carriers - > >Yes, the performance was back. Turns out soft errors were masked and > >the rigid but ringing-resonating nature of steel and the high packing > >density caused drives to resonate the cabinets and cause miseeks. > > Pluto's drive sled design uses a very simple and cheap suspension design > to deal with this very problem. Proof that this problem is not unique. There are several ways of dealing with it. Worse was hanging devices on... springs! Simon From owner-freebsd-hackers Fri Jun 20 02:27:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA23649 for hackers-outgoing; Fri, 20 Jun 1997 02:27:56 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA23627; Fri, 20 Jun 1997 02:27:50 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with SMTP id CAA12213; Fri, 20 Jun 1997 02:29:50 -0700 (PDT) Message-Id: <199706200929.CAA12213@implode.root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Simon Shapiro cc: "Justin T. Gibbs" , FREEBSD-HACKERS , FREEBSD-SCSI , Brian Tao Subject: Re: Announcement: New DPT RAID Controller Driver Available In-reply-to: Your message of "Fri, 20 Jun 1997 01:39:04 PDT." From: David Greenman Reply-To: dg@root.com Date: Fri, 20 Jun 1997 02:29:50 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >Hi "Justin T. Gibbs"; On 20-Jun-97 you wrote: >> >An excellent mechanical engineer designed a wonderful metal system (both >> >canisters and carriers). We had up to 30% perofrmance loss on random >> >seeks with system. It baffled anyone until another engineer decided to >> >test the drives on his desk, outside the box, outside the carriers - >> >Yes, the performance was back. Turns out soft errors were masked and >> >the rigid but ringing-resonating nature of steel and the high packing >> >density caused drives to resonate the cabinets and cause miseeks. >> >> Pluto's drive sled design uses a very simple and cheap suspension design >> to deal with this very problem. > >Proof that this problem is not unique. There are several ways of dealing >with it. Worse was hanging devices on... springs! Before everyone throws out their metal drive enclosures in favor of plastic ones, let me say something about my experiance. Wcarchive used to lose a couple of drives a month back when they were housed in plastic enclosures. I noticed that the drives in that box ran hot, and I finally got tired of flying down to the Bay area so often to deal with it and convinced WC to replace the cabinet/enclosures with an all-steel one made by Kingston. This was about a year ago. Result: The drives run almost cold now and we haven't had a single failure in that array since. All of our drives have fairly well balanced spindles and don't vibrate all that much, and I've never seen a reported seek failure or noticed any slowness. In my opinion, the all- metal enclosure is a significant factor in the cooling of the drives and these days I wouldn't consider anything else. YMMV. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Fri Jun 20 02:49:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA24346 for hackers-outgoing; Fri, 20 Jun 1997 02:49:26 -0700 (PDT) Received: from florence.pavilion.net (mailrelay1.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA24315; Fri, 20 Jun 1997 02:49:08 -0700 (PDT) Received: (from joe@localhost) by florence.pavilion.net (8.8.5/8.8.5) id KAA28868; Fri, 20 Jun 1997 10:48:29 +0100 (BST) Message-ID: <19970620104829.34842@pavilion.net> Date: Fri, 20 Jun 1997 10:48:29 +0100 From: Josef Karthauser To: questions@freebsd.org, hackers@freebsd.org Cc: isp@freebsd.org Subject: Apache 1.1.3 and 1.2.0 problems under FBSD2.2.2 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The continuing saga of a sick web machine :( A brief history. We're running a P200pro FBSD2.2.2 machine here as a virtual web server. It currently has 130ish web servers running, each with their own IP address. Where did the problem start? I'm not sure, but it was some combination of reaching 124ish web servers, and hitting a certain number of active http connections. The web server is basically fine, until some limit gets reached and the server then just hangs, with lots of sockets still active. I've tried unlimiting the shell entirely, that we run the httpd from. I've tried adding an entry for the web user to /etc/login.conf: web:\ :path=/usr/local/news/bin /bin /sbin /usr/bin /usr/sbin:\ :cputime=infinity:\ :filesize=128M:\ :datasize-curr=64M:\ :stacksize-cur=32M:\ :coredumpsize-cur=0:\ :maxmemorysize-cur=128M:\ :memorylocked=32M:\ :maxproc=1000:\ :maxproc-cur=1000:\ :openfiles=2000:\ :openfiles-cur=2000:\ :tc=default: This has been bound to the web user in the password file: webboss:*:1011:1011:web:0:0:Web Boss:/nonexistent:/bin/false This still didn't solve the problem. (We'd find loads of sockets in FIN_WAIT_2 when the process hung.) Next stage was to recompile the kernel to raise SOMAXCONN. Here's a fragment from our config file: ----------------------------- machine "i386" cpu "I386_CPU" cpu "I486_CPU" cpu "I586_CPU" cpu "I686_CPU" ident PAVILION maxusers 256 # joe/pavilion/19970529: Our machines have 96Mb of memory options "MAXMEM=96*1024" # joe/pavilion/19970619: jungled the maximum number of connections options SOMAXCONN=1024 options INET #InterNETworking options FFS #Berkeley Fast Filesystem ----------------------------- When I arrived this morning the web server had hung again. Looking at netstat it appears to be better, in as much as there are no FIN_WAIT2's. The whole netstat is included below. The apache that we're running at the moment is 1.1.3. I've tried running 1.2.0 under the above conditions, but it wont start with more than 124 virtual hosts defined. It just complains that it can't look up the name of the main server. It sounds like it's hit a file descriptor limit, but I know that this isn't the case because: dougal# unlimit dougal# limit cputime unlimited filesize unlimited datasize 131072 kbytes stacksize 65536 kbytes coredumpsize unlimited memoryuse unlimited memorylocked unlimited maxproc 4115 openfiles 8232 Fun and games or what!! Any suggestions, other than a full frontal labotamy, would gratefully be received. Joe ------------------------------ Active Internet connections Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp 450 0 194.242.128.16.80 132.236.77.25.4902 ESTABLISHED tcp 0 2 194.242.128.16.23 194.242.128.8.54274 ESTABLISHED tcp 179 0 194.242.128.16.80 208.200.99.17.39158 CLOSE_WAIT tcp 0 0 194.242.132.36.21 195.92.128.66.2949 ESTABLISHED tcp 593 0 194.242.128.16.80 194.216.92.1.39331 ESTABLISHED tcp 448 0 194.242.128.16.80 132.236.77.25.2229 ESTABLISHED tcp 342 0 194.242.128.16.80 192.100.101.6.2769 CLOSE_WAIT tcp 190 0 194.242.128.16.80 194.238.8.2.4428 CLOSE_WAIT tcp 98 0 194.242.128.16.80 206.117.147.5.1540 CLOSE_WAIT tcp 183 0 194.242.132.94.80 158.152.68.58.1256 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1863 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1837 CLOSE_WAIT tcp 506 0 194.242.128.16.80 134.239.84.2.4479 CLOSE_WAIT tcp 183 0 194.242.132.94.80 158.152.68.58.1253 CLOSE_WAIT tcp 174 0 194.242.128.16.80 194.242.131.158.1028 ESTABLISHED tcp 256 0 194.242.132.15.80 194.170.1.141.35479 CLOSE_WAIT tcp 376 0 194.242.132.86.80 148.88.11.117.2246 CLOSE_WAIT tcp 219 0 194.242.128.16.80 194.74.164.12.53444 ESTABLISHED tcp 506 0 194.242.128.16.80 134.239.84.2.4474 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1812 CLOSE_WAIT tcp 434 0 194.242.128.16.80 134.239.84.2.4473 CLOSE_WAIT tcp 484 0 194.242.128.16.80 151.120.84.6.2817 ESTABLISHED tcp 237 0 194.242.128.16.80 195.86.14.170.4484 ESTABLISHED tcp 334 0 194.242.128.16.80 194.88.74.2.3506 CLOSE_WAIT tcp 232 0 194.242.128.16.80 202.219.149.5.1552 CLOSE_WAIT tcp 272 0 194.242.128.16.80 194.242.131.83.1030 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1786 CLOSE_WAIT tcp 219 0 194.242.128.16.80 194.74.164.12.53436 ESTABLISHED tcp 269 0 194.242.128.16.80 202.32.150.23.2872 ESTABLISHED tcp 181 0 194.242.132.73.80 209.1.12.107.44178 CLOSE_WAIT tcp 376 0 194.242.128.16.80 194.242.131.156.1837 ESTABLISHED tcp 368 0 194.242.128.16.80 207.139.25.25.1548 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1761 CLOSE_WAIT tcp 397 0 194.242.132.113.80 193.113.139.190.4681 CLOSE_WAIT tcp 259 0 194.242.132.77.80 158.152.170.36.2057 CLOSE_WAIT tcp 411 0 194.242.132.86.80 193.113.139.190.4477 CLOSE_WAIT tcp 405 0 194.242.132.86.80 193.113.139.190.4476 CLOSE_WAIT tcp 182 0 194.242.132.92.80 204.123.9.20.1689 CLOSE_WAIT tcp 386 0 194.242.128.16.80 129.194.12.50.44910 CLOSE_WAIT tcp 91 0 194.242.132.67.80 204.62.245.168.52059 CLOSE_WAIT tcp 259 0 194.242.132.77.80 158.152.170.36.2056 CLOSE_WAIT tcp 295 0 194.242.132.47.80 195.4.24.129.1232 ESTABLISHED tcp 0 0 194.242.128.16.80 194.242.128.24.1735 CLOSE_WAIT tcp 201 0 194.242.128.16.80 161.112.192.10.34007 CLOSE_WAIT tcp 240 0 194.242.132.61.80 194.152.71.133.1300 ESTABLISHED tcp 202 0 194.242.128.16.80 208.200.99.17.36367 CLOSE_WAIT tcp 201 0 194.242.128.16.80 208.200.99.17.36343 CLOSE_WAIT tcp 438 0 194.242.128.16.80 134.239.84.2.4429 CLOSE_WAIT tcp 353 0 194.242.132.47.80 195.4.24.129.1218 ESTABLISHED tcp 438 0 194.242.128.16.80 134.239.84.2.4404 CLOSE_WAIT tcp 234 0 194.242.132.12.80 193.190.194.200.2889 ESTABLISHED tcp 198 0 194.242.132.13.80 204.123.9.20.4438 CLOSE_WAIT tcp 195 0 194.242.128.16.80 208.200.99.17.36281 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1703 CLOSE_WAIT tcp 201 0 194.242.128.16.80 208.200.99.17.36271 CLOSE_WAIT tcp 90 0 194.242.128.16.80 206.249.9.2.2766 CLOSE_WAIT tcp 410 0 194.242.132.86.80 193.113.139.190.2014 CLOSE_WAIT tcp 90 0 194.242.128.16.80 206.249.9.2.2765 CLOSE_WAIT tcp 111 0 194.242.132.22.80 204.62.245.167.34399 CLOSE_WAIT tcp 410 0 194.242.132.86.80 193.113.139.190.1879 CLOSE_WAIT tcp 405 0 194.242.132.86.80 193.113.139.190.1813 CLOSE_WAIT tcp 411 0 194.242.132.86.80 193.113.139.190.1812 CLOSE_WAIT tcp 506 0 194.242.128.16.80 134.239.84.2.4371 CLOSE_WAIT tcp 236 0 194.242.132.16.80 152.163.207.135.48836 ESTABLISHED tcp 94 0 194.242.132.108.80 204.62.245.168.49494 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1678 CLOSE_WAIT tcp 458 0 194.242.128.16.80 134.239.84.2.4365 CLOSE_WAIT tcp 353 0 194.242.132.47.80 195.4.24.129.1119 ESTABLISHED tcp 257 0 194.242.132.92.80 192.195.167.3.41145 CLOSE_WAIT tcp 458 0 194.242.128.16.80 134.239.84.2.4363 CLOSE_WAIT tcp 353 0 194.242.132.47.80 195.4.24.129.1116 ESTABLISHED tcp 269 0 194.242.128.16.80 202.32.150.23.2869 CLOSE_WAIT tcp 458 0 194.242.128.16.80 134.239.84.2.4362 CLOSE_WAIT tcp 186 0 194.242.128.16.80 208.200.99.17.36063 CLOSE_WAIT tcp 293 0 194.242.132.16.80 152.163.207.135.45099 ESTABLISHED tcp 222 0 194.242.132.52.80 202.190.35.126.1144 ESTABLISHED tcp 183 0 194.242.132.94.80 158.152.68.58.1210 CLOSE_WAIT tcp 177 0 194.242.132.93.80 209.1.12.108.36299 CLOSE_WAIT tcp 221 0 194.242.132.10.80 192.71.13.14.47797 CLOSE_WAIT tcp 239 0 194.242.132.36.80 194.52.244.35.1049 ESTABLISHED tcp 505 0 194.242.128.16.80 193.63.255.1.53161 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1652 CLOSE_WAIT tcp 90 0 194.242.132.77.80 204.62.245.168.48250 CLOSE_WAIT tcp 269 0 194.242.128.16.80 202.32.150.23.2866 CLOSE_WAIT tcp 515 0 194.242.132.17.80 163.195.1.153.1522 CLOSE_WAIT tcp 199 0 194.242.128.16.80 208.200.99.17.35924 CLOSE_WAIT tcp 268 0 194.242.128.16.80 152.170.9.196.2927 CLOSE_WAIT tcp 469 0 194.242.128.16.80 134.239.84.2.4359 CLOSE_WAIT tcp 113 0 194.242.128.16.80 204.62.245.32.35501 CLOSE_WAIT tcp 93 0 194.242.128.16.80 206.14.14.180.1520 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1627 CLOSE_WAIT tcp 194 0 194.242.132.12.80 134.105.16.250.3369 CLOSE_WAIT tcp 243 0 194.242.128.16.80 195.232.30.131.2101 CLOSE_WAIT tcp 93 0 194.242.128.16.80 206.14.14.180.1409 CLOSE_WAIT tcp 190 0 194.242.128.16.80 194.238.8.2.4308 CLOSE_WAIT tcp 194 0 194.242.132.12.80 134.105.16.250.3368 CLOSE_WAIT tcp 410 0 194.242.132.86.80 193.113.139.190.2382 CLOSE_WAIT tcp 411 0 194.242.132.86.80 193.113.139.190.2358 CLOSE_WAIT tcp 405 0 194.242.132.86.80 193.113.139.190.2356 CLOSE_WAIT tcp 330 0 194.242.132.22.80 203.8.223.2.28346 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1601 CLOSE_WAIT tcp 194 0 194.242.132.12.80 134.105.16.250.3367 CLOSE_WAIT tcp 93 0 194.242.128.16.80 206.14.14.180.1190 CLOSE_WAIT tcp 194 0 194.242.132.12.80 134.105.16.250.3366 CLOSE_WAIT tcp 93 0 194.242.128.16.80 206.14.14.180.1137 CLOSE_WAIT tcp 109 0 194.242.132.24.80 206.14.154.191.53983 ESTABLISHED tcp 152 0 194.242.128.16.80 193.133.92.249.1143 CLOSE_WAIT tcp 515 0 194.242.132.17.80 163.195.1.153.1195 CLOSE_WAIT tcp 263 0 194.242.128.16.80 206.173.210.46.1214 CLOSE_WAIT tcp 194 0 194.242.132.12.80 134.105.16.250.3365 CLOSE_WAIT tcp 469 0 194.242.132.22.80 203.8.223.2.25264 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1576 CLOSE_WAIT tcp 255 0 194.242.132.101.80 193.130.245.65.2034 CLOSE_WAIT tcp 93 0 194.242.128.16.80 206.14.14.180.4936 CLOSE_WAIT tcp 152 0 194.242.128.16.80 193.133.92.249.1136 CLOSE_WAIT tcp 328 0 194.242.128.16.80 192.100.101.6.3792 CLOSE_WAIT tcp 345 0 194.242.128.16.80 194.235.21.6.2010 CLOSE_WAIT tcp 288 0 194.242.132.33.80 194.164.0.34.1116 ESTABLISHED tcp 360 0 194.242.128.16.80 192.100.101.6.3667 CLOSE_WAIT tcp 284 0 194.242.128.16.80 194.238.50.8.2472 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1544 CLOSE_WAIT tcp 248 0 194.242.128.16.80 202.158.8.41.1036 CLOSE_WAIT tcp 275 0 194.242.132.96.80 198.242.49.1.2055 CLOSE_WAIT tcp 307 0 194.242.128.16.80 163.137.8.131.2098 CLOSE_WAIT tcp 297 0 194.242.132.10.80 198.164.97.26.1416 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1519 CLOSE_WAIT tcp 98 0 194.242.128.16.80 206.117.147.5.1501 CLOSE_WAIT tcp 342 0 194.242.128.16.80 192.100.101.6.3211 CLOSE_WAIT tcp 563 0 194.242.132.92.80 192.189.54.2.52946 CLOSE_WAIT tcp 98 0 194.242.128.16.80 206.117.147.3.4743 CLOSE_WAIT tcp 464 0 194.242.132.77.80 145.228.48.120.1190 CLOSE_WAIT tcp 243 0 194.242.128.16.80 193.133.92.249.4992 CLOSE_WAIT tcp 303 0 194.242.128.16.80 193.130.252.110.2757 CLOSE_WAIT tcp 302 0 194.242.128.16.80 152.163.197.35.54381 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1493 CLOSE_WAIT tcp 94 0 194.242.132.108.80 204.62.245.168.42228 CLOSE_WAIT tcp 302 0 194.242.128.16.80 152.163.197.35.53574 CLOSE_WAIT tcp 201 0 194.242.128.16.80 161.112.192.10.34006 CLOSE_WAIT tcp 299 0 194.242.128.16.80 152.163.197.35.51812 CLOSE_WAIT tcp 469 0 194.242.132.104.80 192.189.54.2.51384 CLOSE_WAIT tcp 412 0 194.242.132.86.80 193.113.139.190.4406 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1467 CLOSE_WAIT tcp 411 0 194.242.132.86.80 193.113.139.190.4365 CLOSE_WAIT tcp 405 0 194.242.132.86.80 193.113.139.190.4362 CLOSE_WAIT tcp 271 0 194.242.128.16.80 195.212.234.226.4412 CLOSE_WAIT tcp 191 0 194.242.132.92.80 203.102.82.2.3565 CLOSE_WAIT tcp 185 0 194.242.132.59.80 209.1.12.113.36894 CLOSE_WAIT tcp 114 0 194.242.132.22.80 204.62.245.32.64282 CLOSE_WAIT tcp 301 0 194.242.128.16.80 152.163.197.35.47158 CLOSE_WAIT tcp 248 0 194.242.132.77.80 158.152.170.36.1979 CLOSE_WAIT tcp 243 0 194.242.128.16.80 193.133.92.249.4954 CLOSE_WAIT tcp 266 0 194.242.128.16.80 152.163.205.34.36163 CLOSE_WAIT tcp 395 0 194.242.128.16.80 205.138.230.67.1657 ESTABLISHED tcp 0 0 194.242.128.16.80 194.242.128.24.1435 CLOSE_WAIT tcp 301 0 194.242.128.16.80 152.163.197.35.43958 CLOSE_WAIT tcp 219 0 194.242.132.22.80 203.2.193.70.3710 CLOSE_WAIT tcp 219 0 194.242.132.22.80 203.2.193.70.3667 CLOSE_WAIT tcp 180 0 194.242.132.41.80 209.1.12.108.35039 CLOSE_WAIT tcp 477 0 194.242.128.16.80 194.222.193.246.2374 ESTABLISHED tcp 339 0 194.242.132.96.80 198.242.49.1.2380 CLOSE_WAIT tcp 307 0 194.242.128.16.80 163.137.8.131.1800 CLOSE_WAIT tcp 410 0 194.242.132.86.80 193.113.139.190.2328 CLOSE_WAIT tcp 405 0 194.242.132.86.80 193.113.139.190.2314 CLOSE_WAIT tcp 411 0 194.242.132.86.80 193.113.139.190.2312 CLOSE_WAIT tcp 479 0 194.242.132.22.80 194.222.193.246.2372 ESTABLISHED tcp 0 0 194.242.128.16.80 194.242.128.24.1410 CLOSE_WAIT tcp 479 0 194.242.132.22.80 194.222.193.246.2369 ESTABLISHED tcp 222 0 194.242.128.16.80 136.152.64.115.1168 CLOSE_WAIT tcp 387 0 194.242.132.32.80 194.242.128.144.1363 ESTABLISHED tcp 299 0 194.242.132.22.80 203.2.193.70.3421 CLOSE_WAIT tcp 348 0 194.242.128.16.80 194.242.130.162.1029 ESTABLISHED tcp 463 0 194.242.128.16.80 194.222.193.246.2367 ESTABLISHED tcp 281 0 194.242.128.16.80 152.163.205.25.3792 ESTABLISHED tcp 299 0 194.242.132.22.80 203.2.193.70.3217 CLOSE_WAIT tcp 469 0 194.242.132.104.80 192.189.54.2.47330 CLOSE_WAIT tcp 423 0 194.242.128.16.80 194.235.21.6.1994 CLOSE_WAIT tcp 267 0 194.242.128.16.80 194.151.78.79.1074 ESTABLISHED tcp 272 0 194.242.128.16.80 194.151.78.79.1072 ESTABLISHED tcp 299 0 194.242.132.22.80 203.2.193.70.3153 CLOSE_WAIT tcp 314 0 194.242.128.16.80 194.74.164.12.53345 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1384 CLOSE_WAIT tcp 247 0 194.242.128.16.80 195.232.30.131.1093 CLOSE_WAIT tcp 245 0 194.242.128.16.80 195.232.30.131.1677 CLOSE_WAIT tcp 244 0 194.242.128.16.80 195.232.30.131.1568 CLOSE_WAIT tcp 422 0 194.242.128.16.80 202.96.65.30.1996 ESTABLISHED tcp 423 0 194.242.128.16.80 194.235.21.6.1993 CLOSE_WAIT tcp 98 0 194.242.132.36.80 204.62.245.32.62339 CLOSE_WAIT tcp 309 0 194.242.128.16.80 152.163.205.34.35414 CLOSE_WAIT tcp 410 0 194.242.132.86.80 193.113.139.190.3876 CLOSE_WAIT tcp 232 0 194.242.132.28.80 194.152.162.248.1183 ESTABLISHED tcp 235 0 194.242.132.28.80 194.152.162.248.1182 ESTABLISHED tcp 201 0 194.242.128.16.80 161.112.192.10.34005 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1350 CLOSE_WAIT tcp 93 0 194.242.128.16.80 206.14.14.180.2538 CLOSE_WAIT tcp 258 0 194.242.128.16.80 130.54.61.13.1256 CLOSE_WAIT tcp 0 0 194.242.128.16.80 193.133.92.249.4784 CLOSE_WAIT tcp 0 0 194.242.128.16.80 163.137.8.131.4805 CLOSE_WAIT tcp 0 0 194.242.132.12.80 132.166.52.28.2199 CLOSE_WAIT tcp 0 0 194.242.128.16.80 193.133.96.130.2222 ESTABLISHED tcp 0 0 194.242.128.16.80 193.215.220.104.2231 ESTABLISHED tcp 0 0 194.242.128.16.80 138.25.2.20.51082 CLOSE_WAIT tcp 0 0 194.242.132.36.80 195.16.0.26.46365 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.119.231.99.1253 CLOSE_WAIT tcp 0 0 194.242.132.22.80 193.6.20.1.1088 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.30.38.200.62426 CLOSE_WAIT tcp 0 0 194.242.128.16.80 195.76.129.30.31184 CLOSE_WAIT tcp 0 0 194.242.132.66.80 163.119.254.17.1850 CLOSE_WAIT udp 0 0 194.242.128.16.3065 194.242.128.1.53 udp 0 0 194.242.128.16.2630 194.242.128.1.53 udp 0 0 194.242.128.16.2606 194.242.128.1.53 udp 0 0 194.242.128.16.2605 194.242.128.1.53 udp 0 0 194.242.128.16.2603 194.242.128.1.53 udp 0 0 194.242.128.16.2577 194.242.128.1.53 udp 0 0 194.242.128.16.2039 194.242.128.1.53 udp 0 0 194.242.128.16.2030 194.242.128.1.53 udp 0 0 194.242.128.16.2025 194.242.128.1.53 udp 0 0 194.242.128.16.2008 194.242.128.1.53 udp 0 0 194.242.128.16.1685 194.242.128.1.53 udp 0 0 194.242.128.16.1287 194.242.128.1.53 udp 0 0 194.242.128.16.1232 194.242.128.1.53 udp 0 0 194.242.128.16.1154 194.242.128.1.53 udp 0 0 194.242.128.16.4448 194.242.128.1.53 udp 0 0 194.242.128.16.4293 194.242.128.1.53 udp 0 0 194.242.128.16.4121 194.242.128.1.53 udp 0 0 194.242.128.16.3903 194.242.128.1.53 udp 0 0 194.242.128.16.1081 194.242.128.1.53 udp 0 0 194.242.128.16.3686 194.242.128.1.53 udp 0 0 194.242.128.16.2552 194.242.128.1.53 udp 0 0 194.242.128.16.2645 194.242.128.1.53 udp 0 0 194.242.128.16.1197 194.242.128.1.53 udp 0 0 194.242.128.16.4712 194.242.128.1.53 udp 0 0 194.242.128.16.3906 194.242.128.1.53 udp 0 0 194.242.128.16.3323 194.242.128.1.53 udp 0 0 194.242.128.16.2824 194.242.128.1.53 udp 0 0 194.242.128.16.4744 194.242.128.1.53 udp 0 0 194.242.128.16.3994 194.242.128.1.53 udp 0 0 194.242.128.16.2514 194.242.128.1.53 udp 0 0 194.242.128.16.2243 194.242.128.1.53 udp 0 0 194.242.128.16.3457 194.242.128.1.53 udp 0 0 194.242.128.16.1908 194.242.128.1.53 udp 0 0 194.242.128.16.1506 194.242.128.1.53 udp 0 0 194.242.128.16.4991 194.242.128.1.53 udp 0 0 194.242.128.16.4249 194.242.128.1.53 udp 0 0 194.242.128.16.1864 194.242.128.1.53 udp 0 0 194.242.128.16.1448 194.242.128.1.53 udp 0 0 194.242.128.16.3714 194.242.128.1.53 udp 0 0 194.242.128.16.3709 194.242.128.1.53 udp 0 0 194.242.128.16.3560 194.242.128.1.53 udp 0 0 194.242.128.16.3124 194.242.128.1.53 udp 0 0 194.242.128.16.2903 194.242.128.1.53 udp 0 0 194.242.128.16.1382 194.242.128.1.53 udp 0 0 194.242.128.16.1283 194.242.128.1.53 udp 0 0 194.242.128.16.4594 194.242.128.1.53 udp 0 0 194.242.128.16.2766 194.242.128.1.53 udp 0 0 194.242.128.16.1775 194.242.128.1.53 udp 0 0 194.242.128.16.4750 194.242.128.1.53 udp 0 0 194.242.128.16.4386 194.242.128.1.53 udp 0 0 194.242.128.16.2301 194.242.128.1.53 udp 0 0 194.242.128.16.1127 194.242.128.1.53 udp 0 0 194.242.128.16.2374 194.242.128.1.53 udp 0 0 194.242.128.16.1719 194.242.128.1.53 udp 0 0 194.242.128.16.3833 194.242.128.1.53 udp 0 0 194.242.128.16.3290 194.242.128.1.53 udp 0 0 194.242.128.16.2014 194.242.128.1.53 udp 0 0 194.242.128.16.1526 194.242.128.1.53 udp 0 0 194.242.128.16.3910 194.242.128.1.53 udp 0 0 194.242.128.16.1900 194.242.128.1.53 udp 0 0 194.242.128.16.1845 194.242.128.1.53 udp 0 0 194.242.128.16.4469 194.242.128.1.53 udp 0 0 194.242.128.16.3769 194.242.128.1.53 udp 0 0 194.242.128.16.3643 194.242.128.1.53 udp 0 0 194.242.128.16.3553 194.242.128.1.53 udp 0 0 194.242.128.16.2489 194.242.128.1.53 udp 0 0 194.242.128.16.4457 194.242.128.1.53 udp 0 0 194.242.128.16.2986 194.242.128.1.53 udp 0 0 194.242.128.16.2275 194.242.128.1.53 udp 0 0 194.242.128.16.2822 194.242.128.1.53 udp 0 0 194.242.128.16.1984 194.242.128.1.53 udp 0 0 194.242.128.16.1896 194.242.128.1.53 udp 0 0 194.242.128.16.3921 194.242.128.1.53 udp 0 0 194.242.128.16.2143 194.242.128.1.53 udp 0 0 194.242.128.16.1556 194.242.128.1.53 udp 0 0 194.242.128.16.1518 194.242.128.1.53 udp 0 0 194.242.128.16.4837 194.242.128.1.53 udp 0 0 194.242.128.16.3516 194.242.128.1.53 udp 0 0 194.242.128.16.4191 194.242.128.1.53 udp 0 0 194.242.128.16.2535 194.242.128.1.53 udp 0 0 194.242.128.16.1227 194.242.128.1.53 udp 0 0 194.242.128.16.4537 194.242.128.1.53 udp 0 0 194.242.128.16.3992 194.242.128.1.53 udp 0 0 194.242.128.16.3791 194.242.128.1.53 udp 0 0 194.242.128.16.3103 194.242.128.1.53 udp 0 0 194.242.128.16.2772 194.242.128.1.53 udp 0 0 194.242.128.16.1834 194.242.128.1.53 udp 0 0 194.242.128.16.1422 194.242.128.1.53 udp 0 0 194.242.128.16.3685 194.242.128.1.53 udp 0 0 194.242.128.16.3490 194.242.128.1.53 udp 0 0 194.242.128.16.3489 194.242.128.1.53 udp 0 0 194.242.128.16.2917 194.242.128.1.53 udp 0 0 194.242.128.16.2827 194.242.128.1.53 udp 0 0 194.242.128.16.2814 194.242.128.1.53 udp 0 0 194.242.128.16.1416 194.242.128.1.53 udp 0 0 194.242.128.16.1710 194.242.128.1.53 udp 0 0 194.242.128.16.1236 194.242.128.1.53 udp 0 0 194.242.128.16.1184 194.242.128.1.53 udp 0 0 194.242.128.16.4276 194.242.128.1.53 udp 0 0 194.242.128.16.3913 194.242.128.1.53 udp 0 0 194.242.128.16.3902 194.242.128.1.53 udp 0 0 194.242.128.16.3453 194.242.128.1.53 udp 0 0 194.242.128.16.2852 194.242.128.1.53 udp 0 0 194.242.128.16.2838 194.242.128.1.53 udp 0 0 194.242.128.16.2519 194.242.128.1.53 udp 0 0 194.242.128.16.2486 194.242.128.1.53 udp 0 0 194.242.128.16.1594 194.242.128.1.53 udp 0 0 194.242.128.16.1558 194.242.128.1.53 udp 0 0 194.242.128.16.1515 194.242.128.1.53 udp 0 0 194.242.128.16.1441 194.242.128.1.53 udp 0 0 194.242.128.16.1052 194.242.128.1.53 udp 0 0 194.242.128.16.4896 194.242.128.1.53 udp 0 0 194.242.128.16.4774 194.242.128.1.53 udp 0 0 194.242.128.16.4412 194.242.128.1.53 udp 0 0 194.242.128.16.4359 194.242.128.1.53 udp 0 0 194.242.128.16.3670 194.242.128.1.53 udp 0 0 194.242.128.16.1934 194.242.128.1.53 udp 0 0 194.242.128.16.1286 194.242.128.1.53 udp 0 0 194.242.128.16.1213 194.242.128.1.53 udp 0 0 194.242.128.16.2346 194.242.128.1.53 udp 0 0 194.242.128.16.2170 194.242.128.1.53 udp 0 0 194.242.128.16.2078 194.242.128.1.53 udp 0 0 194.242.128.16.1846 194.242.128.1.53 udp 0 0 194.242.128.16.1732 194.242.128.1.53 udp 0 0 194.242.128.16.1730 194.242.128.1.53 udp 0 0 194.242.128.16.1684 194.242.128.1.53 udp 0 0 194.242.128.16.1654 194.242.128.1.53 udp 0 0 194.242.128.16.1544 194.242.128.1.53 udp 0 0 194.242.128.16.1147 194.242.128.1.53 udp 0 0 194.242.128.16.4562 194.242.128.1.53 udp 0 0 194.242.128.16.3484 194.242.128.1.53 udp 0 0 194.242.128.2.53 *.* udp 0 0 194.242.128.16.123 *.* -- Josef Karthauser Technical Manager Email: joe@pavilion.net Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] From owner-freebsd-hackers Fri Jun 20 02:57:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA24720 for hackers-outgoing; Fri, 20 Jun 1997 02:57:59 -0700 (PDT) Received: from florence.pavilion.net (mailrelay1.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA24708 for ; Fri, 20 Jun 1997 02:57:54 -0700 (PDT) Received: (from joe@localhost) by florence.pavilion.net (8.8.5/8.8.5) id KAA29339; Fri, 20 Jun 1997 10:57:19 +0100 (BST) Message-ID: <19970620105719.59968@pavilion.net> Date: Fri, 20 Jun 1997 10:57:19 +0100 From: Josef Karthauser To: hackers@freebsd.org Subject: Suggested changed to sys/socket.h Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've been playing around with redefining SOMAXCONN in my kernel configuration file. It doesn't half make a lot of noise at compile time. Is there any reason why /usr/src/sys/sys/socket.h shouldn't be changed like this: *** socket.h Fri Aug 30 03:18:24 1996 --- socket-new.h Fri Jun 20 10:55:14 1997 *************** *** 249,255 **** --- 249,257 ---- /* * Maximum queue length specifiable by listen. */ + #ifndef SOMAXCONN #define SOMAXCONN 128 + #endif /*!SOMAXCONN*/ /* * Message header for recvmsg and sendmsg calls. Joe -- Josef Karthauser Technical Manager Email: joe@pavilion.net Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] From owner-freebsd-hackers Fri Jun 20 03:00:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA24906 for hackers-outgoing; Fri, 20 Jun 1997 03:00:28 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA24897 for ; Fri, 20 Jun 1997 03:00:24 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id DAA27385; Fri, 20 Jun 1997 03:00:11 -0700 (PDT) To: Michael Smith cc: Harlan.Stenn@pfcs.com, hackers@FreeBSD.ORG Subject: Re: "make reinstall"? In-reply-to: Your message of "Fri, 20 Jun 1997 18:03:01 +0930." <199706200833.SAA03739@genesis.atrad.adelaide.edu.au> Date: Fri, 20 Jun 1997 03:00:11 -0700 Message-ID: <27382.866800811@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > This target has never actually worked for doing what you're trying to > > do. :( > > It _used_ to, actually. Back before building releases was an option > for me (2.0.5 days IIRC), I used to do this quite a lot. OK, so not never then. Hardly ever. :-) Jordan From owner-freebsd-hackers Fri Jun 20 03:37:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA26231 for hackers-outgoing; Fri, 20 Jun 1997 03:37:32 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA26212; Fri, 20 Jun 1997 03:37:27 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id DAA27550; Fri, 20 Jun 1997 03:37:07 -0700 (PDT) To: dg@root.com cc: Simon Shapiro , "Justin T. Gibbs" , FREEBSD-HACKERS , FREEBSD-SCSI , Brian Tao Subject: Re: Announcement: New DPT RAID Controller Driver Available In-reply-to: Your message of "Fri, 20 Jun 1997 02:29:50 PDT." <199706200929.CAA12213@implode.root.com> Date: Fri, 20 Jun 1997 03:37:07 -0700 Message-ID: <27545.866803027@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > haven't had a single failure in that array since. All of our drives have > fairly well balanced spindles and don't vibrate all that much, and I've never > seen a reported seek failure or noticed any slowness. In my opinion, the all- Erm, I think the difference we're probably seeing with wcarchive is the fact that each drive bay doesn't hold more than 8 drives (most holding far fewer) and is independantly bolted to the rack. That probably provides pretty good vibration isolation, but undoubtedly also at a drive-to-housing cost ratio which would be unacceptable to the truly big RAID builder. I would also be suspicious of the cooling properties of a plastic drive enclosure (it seems like packing it in a mini-Igloo ice chest would be no worse to me ;-), but given a much different racking scenario, say 80 drives in a single free-standing rack, I'm more than willing to believe that vibration becomes a significant problem requiring creative solutions. If it were my fingers signing the P.O. on a true drive-array-from-hell, I'd probably favor the vendor providing the best combination of all-metal construction, air-flow, power supply quality and vibration isolation. Unless, of course, they had something like the AMES wind tunnel providing forced airflow past the drives, then I suppose the plastic sled construction wouldn't really matter much, would it? :-) Jordan From owner-freebsd-hackers Fri Jun 20 03:48:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA26693 for hackers-outgoing; Fri, 20 Jun 1997 03:48:08 -0700 (PDT) Received: from lab321.ru (anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA26622 for ; Fri, 20 Jun 1997 03:47:56 -0700 (PDT) Received: from localhost (localhost.l321.omsk.net.ru [127.0.0.1]) by lab321.ru SLMail 1.032 with SMTP id RAA04397 for ; Fri, 20 Jun 1997 17:49:47 +0700 (OSD) Date: Fri, 20 Jun 1997 17:49:46 +0700 (OSD) From: Eugeny Kuzakov To: freebsd-hackers@freebsd.org Subject: fbsd2.2.2&gcc&KDE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dear Sirs ! I am trying to compile KDE(latest verision) on FreeBSD 2.2.2 box. I have some troubles with compile kghostview.cpp, because g++ hangs... Can you help me ? Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru From owner-freebsd-hackers Fri Jun 20 05:05:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA28761 for hackers-outgoing; Fri, 20 Jun 1997 05:05:16 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA28739; Fri, 20 Jun 1997 05:05:07 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with SMTP id FAA12992; Fri, 20 Jun 1997 05:07:02 -0700 (PDT) Message-Id: <199706201207.FAA12992@implode.root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Josef Karthauser cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG, isp@FreeBSD.ORG Subject: Re: Apache 1.1.3 and 1.2.0 problems under FBSD2.2.2 In-reply-to: Your message of "Fri, 20 Jun 1997 10:48:29 BST." <19970620104829.34842@pavilion.net> From: David Greenman Reply-To: dg@root.com Date: Fri, 20 Jun 1997 05:07:02 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Any suggestions, other than a full frontal labotamy, would gratefully >be received. What do you have NMBCLUSTERS set to? A busy WWW server needs a fairly high value for that - many times the default. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Fri Jun 20 05:07:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA28877 for hackers-outgoing; Fri, 20 Jun 1997 05:07:07 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA28871 for ; Fri, 20 Jun 1997 05:07:04 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with SMTP id FAA13012; Fri, 20 Jun 1997 05:08:54 -0700 (PDT) Message-Id: <199706201208.FAA13012@implode.root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Josef Karthauser cc: hackers@FreeBSD.ORG Subject: Re: Suggested changed to sys/socket.h In-reply-to: Your message of "Fri, 20 Jun 1997 10:57:19 BST." <19970620105719.59968@pavilion.net> From: David Greenman Reply-To: dg@root.com Date: Fri, 20 Jun 1997 05:08:53 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I've been playing around with redefining SOMAXCONN in >my kernel configuration file. It doesn't half make >a lot of noise at compile time. > >Is there any reason why /usr/src/sys/sys/socket.h >shouldn't be changed like this: > >*** socket.h Fri Aug 30 03:18:24 1996 >--- socket-new.h Fri Jun 20 10:55:14 1997 >*************** >*** 249,255 **** >--- 249,257 ---- > /* > * Maximum queue length specifiable by listen. > */ >+ #ifndef SOMAXCONN > #define SOMAXCONN 128 >+ #endif /*!SOMAXCONN*/ Yes; you can also set it with the sysctl variable kern.somaxconn. The value in socket.h is only a default - the best way to tune this is in your /etc/rc.local. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Fri Jun 20 05:08:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA28979 for hackers-outgoing; Fri, 20 Jun 1997 05:08:43 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA28974 for ; Fri, 20 Jun 1997 05:08:41 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id FAA21529; Fri, 20 Jun 1997 05:07:47 -0700 (PDT) To: Eugeny Kuzakov cc: freebsd-hackers@FreeBSD.ORG Subject: Re: fbsd2.2.2&gcc&KDE In-reply-to: Your message of "Fri, 20 Jun 1997 17:49:46 +0700." Date: Fri, 20 Jun 1997 05:07:47 -0700 Message-ID: <21525.866808467@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Dear Sirs ! > > I am trying to compile KDE(latest verision) on FreeBSD 2.2.2 box. This is actually a message which should go to questions@freebsd.org, but since it's dealing with a moderately interesting topic I guess we'll let you live. This time. :) > I have some troubles with compile kghostview.cpp, because g++ hangs... > Can you help me ? Not really - I just went and grabbed the latest KDE stuff, having meant to try it eventually anyway, and while the kdesupport and kdelib stuff compiled just fine, the ghostview app compile _fell over_ rather than causing any kind of hang here: Making app in kghostview gmake[1]: Entering directory `/a/jkh/KDE/kdeapps/kghostview' c++ -O2 -Wall -I/usr/X11R6/include -I/usr/X11R6/include/X11/qt -I/usr/local/kde/include -I. -I.. -I../kfm/libkfm -DHAVE_CONFIG_H -c kghostview.cpp kghostview.cpp: In method `class QString KGhostview::print_file(class QString, int)': kghostview.cpp:1426: parse error before `(' kghostview.cpp:1426: parse error before `,' kghostview.cpp:1422: warning: unused variable `struct __sFILE * tmpfile' kghostview.cpp:1431: passing `__sFILE * (*)()' as argument 1 of `fclose(__sFILE *)' kghostview.cpp:1434: confused by earlier errors, bailing out So I have to conclude that this software, which declares itself very very early alpha and not guaranteed to actually do anything at all, is probably breaking on some stdio incompatibility here. ;) In any case, why not just comment this one app out of the Makefile and continue? Everything else seems to build just fine, and it all just comes up and works once you set your KDEFOO variables properly. Jordan From owner-freebsd-hackers Fri Jun 20 05:12:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA29117 for hackers-outgoing; Fri, 20 Jun 1997 05:12:21 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA29109; Fri, 20 Jun 1997 05:12:05 -0700 (PDT) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.8.4/8.8.4) with SMTP id PAA11086; Fri, 20 Jun 1997 15:25:22 +0300 (EEST) Date: Fri, 20 Jun 1997 15:25:21 +0300 (EEST) From: Narvi To: Nadav Eiron cc: Samy Touati , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: SMC 9332BDT Help me please... 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 [I hope anyone answering is wiser than me and deletes either -hackers or -questions from the cc: list] On Fri, 20 Jun 1997, Nadav Eiron wrote: > > > On Thu, 19 Jun 1997, Samy Touati wrote: > > > > > > > Hi, > > > > > > In the rel notes of 2.2.2 it's clear that the SMC9332 BDT should work. > > I installed one and it dies as soon as it gets probed by the kernel at > > boot time. > > The chipset 21140A is identified with pass 2.0 and it tries to enable the > > 100TX port. > > The newer versions of the 21140A chipset are not supported by the current > driver. However, a replacement (beta quality) driver is available at: > > http://www.3am-software.com > > Most people report it to work fine with the newer cards. Also look in the > hackers list archives for discussions of newer de drivers. Why are you calling it beta quality? It is at least as good as the old driver (zero problems with both around here). As for replacement - FreeBSD de driver hasn't just been resyncronised yet with the independent, multiplatform, etc. de driver. And so it lacks some features. Sander There is no love, no good, no happiness and no future - all these are just illusions. [snip] From owner-freebsd-hackers Fri Jun 20 05:36:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA00152 for hackers-outgoing; Fri, 20 Jun 1997 05:36:17 -0700 (PDT) Received: from pandora.hh.kew.com (root@kendra.ne.highway1.com [24.128.53.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA00146 for ; Fri, 20 Jun 1997 05:36:14 -0700 (PDT) Received: (from ahd@localhost) by pandora.hh.kew.com (8.8.5/8.8.5) id HAA02285; Fri, 20 Jun 1997 07:31:51 -0400 (EDT) Date: Fri, 20 Jun 1997 07:31:51 -0400 (EDT) From: Drew Derbyshire Message-Id: <199706201131.HAA02285@pandora.hh.kew.com> To: adrian@deathstar.ml.org, freebsd-hackers@FreeBSD.ORG Subject: Re: socket redirector Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From: Adrian Chadd > I'm writing a quick socket redirector for something. Its run out of inetd, > and basically opens a socket somewhere and acts as a pipe between the two. > I'm using select(), and its working fine. The only problem I'm having is > that I don't know how to tell when the remote end closes the connection > down, so that I can just close everything down, and quit. > > Any ideas on how I'd do this? Get this from the distribution: socket-1.1 create tcp socket and connect to stdin/out Note that I have loaded it but not tested it. To answer the source question, I think it's wait for the socket to go ready on read, and a zero byte read is EOD, just like a file. -ahd- From owner-freebsd-hackers Fri Jun 20 05:36:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA00176 for hackers-outgoing; Fri, 20 Jun 1997 05:36:22 -0700 (PDT) Received: from pandora.hh.kew.com (root@kendra.ne.highway1.com [24.128.53.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA00151 for ; Fri, 20 Jun 1997 05:36:16 -0700 (PDT) Received: (from ahd@localhost) by pandora.hh.kew.com (8.8.5/8.8.5) id HAA02245; Fri, 20 Jun 1997 07:23:20 -0400 (EDT) Date: Fri, 20 Jun 1997 07:23:20 -0400 (EDT) From: Drew Derbyshire Message-Id: <199706201123.HAA02245@pandora.hh.kew.com> To: jkh@time.cdrom.com, mike@sentex.net Subject: Re: make world error in RELENG_2_2 Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From: "Jordan K. Hubbard" > (or,as I've frequently done in such situations, do it over since the > original designers had all the pan-UNIX expertise of a team of Visual > Basic programmers and did it wrong for anything _but_ AIX). That's a nasty lie ... they do it wrong for AIX too. :-) (Examples on request, off-line.) -ahd- From owner-freebsd-hackers Fri Jun 20 07:02:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA04175 for hackers-outgoing; Fri, 20 Jun 1997 07:02:39 -0700 (PDT) Received: from florence.pavilion.net (mailrelay1.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA04156; Fri, 20 Jun 1997 07:02:30 -0700 (PDT) Received: (from joe@localhost) by florence.pavilion.net (8.8.5/8.8.5) id PAA14106; Fri, 20 Jun 1997 15:00:30 +0100 (BST) Message-ID: <19970620150029.55055@pavilion.net> Date: Fri, 20 Jun 1997 15:00:30 +0100 From: Josef Karthauser To: dg@root.com Cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Apache 1.1.3 and 1.2.0 problems under FBSD2.2.2 References: <19970620104829.34842@pavilion.net> <199706201207.FAA12992@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199706201207.FAA12992@implode.root.com>; from David Greenman on Fri, Jun 20, 1997 at 05:07:02AM -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Jun 20, 1997 at 05:07:02AM -0700, David Greenman wrote: > >Any suggestions, other than a full frontal labotamy, would gratefully > >be received. > > What do you have NMBCLUSTERS set to? A busy WWW server needs a fairly high > value for that - many times the default. > It appears that: NMBCLUSTERS (512 + MAXUSERS * 16) therefore NMBCLUSTERS=512 + 256*16. Can it be changed with sysctl? Joe -- Josef Karthauser Technical Manager Email: joe@pavilion.net Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] From owner-freebsd-hackers Fri Jun 20 07:30:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA05461 for hackers-outgoing; Fri, 20 Jun 1997 07:30:44 -0700 (PDT) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA05444; Fri, 20 Jun 1997 07:30:37 -0700 (PDT) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.5/8.8.5) with UUCP id IAA02329; Fri, 20 Jun 1997 08:30:25 -0600 (MDT) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id IAA17616; Fri, 20 Jun 1997 08:31:10 -0600 (MDT) Date: Fri, 20 Jun 1997 08:31:10 -0600 (MDT) From: Marc Slemko To: Josef Karthauser cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG, isp@FreeBSD.ORG Subject: Re: Apache 1.1.3 and 1.2.0 problems under FBSD2.2.2 In-Reply-To: <19970620104829.34842@pavilion.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 Please, limit your crossposting. _ONE_ mailing list is appropriate. If something is appropriate to another list, it is almost never appropriate to questions. Also it is appreciated if you don't ask a question publicly and submit it as an Apache bug at the same time. Ask it publicly first and wait to get answers. It avoids wasting limited developer time. On Fri, 20 Jun 1997, Josef Karthauser wrote: > The continuing saga of a sick web machine :( > > A brief history. We're running a P200pro FBSD2.2.2 machine here as > a virtual web server. It currently has 130ish web servers running, > each with their own IP address. > > Where did the problem start? I'm not sure, but it was some combination > of reaching 124ish web servers, and hitting a certain number of active > http connections. > > The web server is basically fine, until some limit gets reached and the > server then just hangs, with lots of sockets still active. You are running out of file descriptors. Just because you change the ulimit does _NOT_ mean you can actually use all of them. You are probably running into the FD_SETSIZE limit, which limits (among other things) the number of fds that select() can handle. It is still 255. Under 2.2, I think you should be able to just redefine FD_SETSIZE before compiling Apache to increase that. The reason that 1.1 works and 1.2 doesn't is probably because file descriptors are allocated in a different order in 1.2 for various reasons. You don't make it entirely clear, but I am assuming that just Apache is hanging, not the whole machine. -- Marc Slemko | Apache team member marcs@znep.com | marc@apache.org From owner-freebsd-hackers Fri Jun 20 08:42:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA08460 for hackers-outgoing; Fri, 20 Jun 1997 08:42:50 -0700 (PDT) Received: from merix.merix.com (merix.merix.com [198.145.172.40]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA08444 for ; Fri, 20 Jun 1997 08:42:48 -0700 (PDT) Received: from sandy.merix.com by merix.merix.com with SMTP (1.38.110.45/16.2) id AA268791994; Fri, 20 Jun 1997 08:53:14 -0700 Received: by sandy.merix.com (4.1/8.0) id AA16564; Fri, 20 Jun 97 08:38:46 PDT Date: Fri, 20 Jun 97 08:38:46 PDT Subject: USB -- How tricky will it be to support? To: freebsd-hackers@freebsd.org From: Troy Curtiss Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hackers, How tricky is USB going to be to support? Some of the mechanisms such as hot plug/unplug, auto-detection and driver allocation, addressing, and etc. don't look easy... The paradigm feels like a cross between the PC-Card stuff (for the plug/unplug) and a PCI-bus (for addressing and detection). Anybody toyed with supporting USB yet? I'm curious what angle to attack this subsystem from. Cheers, -Troy -- /-----------------------------------------------------------\ | Troy Curtiss, HW/SW Engineer | Email: troyc@merix.com | | Merix Corporation, CL-302 | Phone: (970) 203-6643 | | Loveland, CO 80537 | Fax : (970) 203-6610 | \-----------------------------------------------------------/ From owner-freebsd-hackers Fri Jun 20 08:49:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA08719 for hackers-outgoing; Fri, 20 Jun 1997 08:49:30 -0700 (PDT) Received: from mail11.digital.com (mail11.digital.com [192.208.46.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA08713 for ; Fri, 20 Jun 1997 08:49:26 -0700 (PDT) From: garyj@frt.dec.com Received: from cssmuc.frt.dec.com (cssmuc.frt.dec.com [16.186.96.161]) by mail11.digital.com (8.7.5/UNX 1.5/1.0/WV) with SMTP id LAA31361 for ; Fri, 20 Jun 1997 11:29:03 -0400 (EDT) Received: from localhost by cssmuc.frt.dec.com; (5.65v3.2/1.1.8.2/14Nov95-0232PM) id AA25614; Fri, 20 Jun 1997 17:28:59 +0200 Message-Id: <9706201528.AA25614@cssmuc.frt.dec.com> X-Mailer: exmh version 1.6.4 10/10/95 To: hackers@freebsd.org In-Reply-To: Message from "Jordan K. Hubbard" of Fri, 20 Jun 97 03:37:07 PDT. Reply-To: gjennejohn@frt.dec.com Subject: Re: Announcement: New DPT RAID Controller Driver Available Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Jun 97 17:28:59 +0200 X-Mts: smtp Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk jkh@time.cdrom.com writes: > Unless, of course, they had something like the AMES wind tunnel > providing forced airflow past the drives, then I suppose the plastic > sled construction wouldn't really matter much, would it? :-) > basically, the Storage Works thingies from DEC _do_ have a wind tunnel :) I have one of these things at home and it has 2 large fans on the back pushing (or pulling ?) air. I've seen some pretty big RAID arrays here at DEC, all made using plastic enclosures. They work good (although I have to agree with an earlier poster that those flimsy flex connections are pretty cheesy and *so* easy to ruin). --- Gary Jennejohn (work) gjennejohn@frt.dec.com (home) Gary.Jennejohn@munich.netsurf.de (play) gj@freebsd.org From owner-freebsd-hackers Fri Jun 20 09:06:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA09336 for hackers-outgoing; Fri, 20 Jun 1997 09:06:48 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA09309 for ; Fri, 20 Jun 1997 09:06:33 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wf69f-0004B5-00; Fri, 20 Jun 1997 09:03:19 -0700 Date: Fri, 20 Jun 1997 09:03:19 -0700 (PDT) From: Tom Samplonius To: Adrian Chadd cc: freebsd-hackers@freebsd.org Subject: Re: socket redirector In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Jun 1997, Adrian Chadd wrote: > Hey guys. > > I'm writing a quick socket redirector for something. Its run out of inetd, > and basically opens a socket somewhere and acts as a pipe between the two. > I'm using select(), and its working fine. The only problem I'm having is > that I don't know how to tell when the remote end closes the connection > down, so that I can just close everything down, and quit. > > Any ideas on how I'd do this? > > Thanks, > > -- > Adrian Chadd | "Unix doesn't stop you from doing > | stupid things because that would > | stop you from doing clever things" I use netcat from ports to do this, and it can tell. Tom From owner-freebsd-hackers Fri Jun 20 09:14:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA09790 for hackers-outgoing; Fri, 20 Jun 1997 09:14:16 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA09783 for ; Fri, 20 Jun 1997 09:14:12 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) id MAA25274; Fri, 20 Jun 1997 12:09:39 -0400 (EDT) Message-ID: <19970620120938.27122@vinyl.quickweb.com> Date: Fri, 20 Jun 1997 12:09:38 -0400 From: Mark Mayo To: "Jordan K. Hubbard" Cc: Tom Torrance at home , mike@sentex.net, freebsd-hackers@FreeBSD.ORG Subject: Re: make world error in RELENG_2_2 References: <26359.866788909@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: <26359.866788909@time.cdrom.com>; from Jordan K. Hubbard on Thu, Jun 19, 1997 at 11:41:49PM -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Jun 19, 1997 at 11:41:49PM -0700, Jordan K. Hubbard wrote: > > I suspect that there IS some other problem, and it is/was with cvsup. > > I don't know why or how or if I contributed to it:-) > > It's not a problem with cvsup. It's a fundamental flaw in the model > of trying to "upgrade" a source tree by continually: > > a) Changing modified bits. > b) Adding new ones. > c) Not deleting the old ones. > > It's (c) which is the killer since you will eventually confuse the > bezeesus out of the build system with old bits. Do you have the > "delete" option turned on in your supfile? I turns out this is indeed the case... after trying a thousand things to get a clean 'make world', the only thing that worked in the end was in fact nuking the entire /usr/src tree and re-cvsup'ing it. I do have "delete" specified in my supfile, but it obviously doesn't do what I thought it should :-) The only other thing that was "required" was getting a new copy of the include files for /usr/include. I assumed that cvsup did (c) above, when it doesn't. Oh well. Too bad really - since the only reasons I did install the source from the 2.2.1 CD is so I woulnd't have to wait so long for my modem to suck down the *entire* src-all tree :-) Live and learn. -Mark > > Jordan -- ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ---------------------------------------------------------------------------- University degrees are a bit like adultery: you may not want to get involved with that sort of thing, but you don't want to be thought incapable. -Sir Peter Imbert From owner-freebsd-hackers Fri Jun 20 09:36:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA11196 for hackers-outgoing; Fri, 20 Jun 1997 09:36:00 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA11190 for ; Fri, 20 Jun 1997 09:35:57 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) id MAA25377; Fri, 20 Jun 1997 12:28:57 -0400 (EDT) Message-ID: <19970620122856.35232@vinyl.quickweb.com> Date: Fri, 20 Jun 1997 12:28:56 -0400 From: Mark Mayo To: Michael Smith Cc: Mark Mayo , freebsd-hackers@FreeBSD.ORG Subject: Re: make world error in RELENG_2_2 References: <19970619215732.54070@vinyl.quickweb.com> <199706200340.NAA01931@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: <199706200340.NAA01931@genesis.atrad.adelaide.edu.au>; from Michael Smith on Fri, Jun 20, 1997 at 01:10:09PM +0930 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Jun 20, 1997 at 01:10:09PM +0930, Michael Smith wrote: > Mark Mayo stands accused of saying: > > [SNIP] > > > I'll be adding a section entitles "What to do when make world fails", that > > will go throough some of the common problems that might occur during > > dramatic reorganizations of the source tree, and how to get around them. > > Here is a checklist you might want to include somewhere near the top > where impatient people will find it. This isn't my work; if the > author wants to be identified I'm sure they'll stand up and say so : Thanks for the list. I'll add it to my checklist. Of course, using this strategy I would have waited over a month before looking at other options. But yes, in general if the make world fails, you just have to wait 24 hours and try again... Perhaps the other important steps if make world is failing are: 1) rm -rf /usr/src/* 2) CVSUP the whole tree again 3) make world And if that fails: 1) make includes 2) or FTP down the /usr/include files from a more current machine 3) make world (implied rm -r /usr/obj here...) One last thing: After I did get the new includes, everything compiled but in the install phase "install-info" for all the GNU info docs failed with an invalid option to install-info. Anyways, I'm just going to remove my whole source tree and start fresh - this seems to be the key when weird stuff starts happening. Would there be anyway for CVSUP to know when the tree is getting too mixed up and just say "Well, looks like we're gonna have to start from scratch here. Shall I continue?". That would be neat. Like I said to Jordan, the fact that the "delete" option in the cvsup file doesn't do the removal of old bits is a little misleading, and is ultimatlely what sent me down the wrong path :-) You see, in my mind, after I run cvsup, I should have the same source tree as the repository, no matter what I started from! Of course, maybe now I hold the record for the most runs of 'make world' in a 24 hour period ;-) Quite an educational experience, and now I feel far more knowledgable/comfortable about the whole build procedure. -Mark > > 1. If your CPU is overclocked, shut up and don't bother us again. > > 2. Make absolutely sure your entire source tree is 100% up-to-date, > using CVSup or CTM. > > 3. If you cheated in step 2, in any way whatsoever, shut up and > don't bother us again. > > 4. Execute these commands as root: > > rm -rf /usr/obj > mkdir /usr/obj > find /usr/src -name obj -type l | xargs rm > make world > > 5. If you didn't type the commands in step 4 precisely as directed, > shut up and don't bother us again. > > 6. If it still fails, wait 24 hours. Then repeat steps 1-5 > again one time. > > 7. If you didn't wait 24 hours and then repeat steps 1-5 exactly > as directed, shut up and don't bother us again. > > 8. If it still fails in exactly the same way as the first time, tell > us about it. > > > Ok, so they may want toning down a bit for general consumption... > > -- > ]] 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 [[ -- ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ---------------------------------------------------------------------------- University degrees are a bit like adultery: you may not want to get involved with that sort of thing, but you don't want to be thought incapable. -Sir Peter Imbert From owner-freebsd-hackers Fri Jun 20 09:49:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA12068 for hackers-outgoing; Fri, 20 Jun 1997 09:49:53 -0700 (PDT) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA12063 for ; Fri, 20 Jun 1997 09:49:51 -0700 (PDT) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.5/8.8.5) with UUCP id KAA10486 for hackers@FreeBSD.ORG; Fri, 20 Jun 1997 10:49:45 -0600 (MDT) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id KAA18322 for ; Fri, 20 Jun 1997 10:48:48 -0600 (MDT) Date: Fri, 20 Jun 1997 10:48:48 -0600 (MDT) From: Marc Slemko To: hackers@FreeBSD.ORG Subject: Re: Apache 1.1.3 and 1.2.0 problems under FBSD2.2.2 In-Reply-To: <19970620104829.34842@pavilion.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Jun 1997, Josef Karthauser wrote: > The continuing saga of a sick web machine :( > > A brief history. We're running a P200pro FBSD2.2.2 machine here as > a virtual web server. It currently has 130ish web servers running, > each with their own IP address. > > Where did the problem start? I'm not sure, but it was some combination > of reaching 124ish web servers, and hitting a certain number of active > http connections. Grr. I thought this had been fixed in FreeBSD, but I guess not. The problem here is that the FILE structure uses only a short for _file, which means it can only handle 255 fds. When Apache (or, more likely, one of the library routines it calls) tries to access a FILE structure the low fds are all taken already so it chokes. This should be fixed in FreeBSD. It is in BSDI 2.1. Haven't looked to see how many side-effects there are in increasing the size... From owner-freebsd-hackers Fri Jun 20 10:17:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA13403 for hackers-outgoing; Fri, 20 Jun 1997 10:17:33 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA13396 for ; Fri, 20 Jun 1997 10:17:24 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wf7Hy-0005mG-00; Fri, 20 Jun 1997 11:15:58 -0600 To: "Jordan K. Hubbard" Subject: Re: make world error in RELENG_2_2 Cc: Mike Tancsa , freebsd-hackers@freebsd.org In-reply-to: Your message of "Thu, 19 Jun 1997 22:27:07 PDT." <26034.866784427@time.cdrom.com> References: <26034.866784427@time.cdrom.com> Date: Fri, 20 Jun 1997 11:15:58 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <26034.866784427@time.cdrom.com> "Jordan K. Hubbard" writes: : That's just the nature of the beast, and if anything I'd say that : FreeBSD has one of the _easiest_ build systems to understand. Yes. Much nicer and generally does the right thing automatically more often than the OpenBSD system I have. And a whole lot easier than it was back in the 1.0R days when it was a real pain. Building a system on a live system is an inherantly dangerous operation. The fact that it works (or seems to) as well as it does is nothng short of unbelievable. Finally, make world isn't a complete upgrade. It doesn't do anything to your /etc files so you have to merge them by hand. Warner From owner-freebsd-hackers Fri Jun 20 10:24:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA13754 for hackers-outgoing; Fri, 20 Jun 1997 10:24:21 -0700 (PDT) Received: from friley01.res.iastate.edu (friley01.res.iastate.edu [129.186.189.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA13749 for ; Fri, 20 Jun 1997 10:24:19 -0700 (PDT) Received: from friley01.res.iastate.edu (loopback [127.0.0.1]) by friley01.res.iastate.edu (8.8.5/8.8.5) with ESMTP id MAA15908 for ; Fri, 20 Jun 1997 12:26:11 -0500 (CDT) Message-Id: <199706201726.MAA15908@friley01.res.iastate.edu> X-Mailer: exmh version 2.0gamma 1/27/96 To: hackers@freebsd.org Subject: pci_map_mem failed... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Jun 1997 12:26:11 -0500 From: Chris Csanady Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am working on an ethernet driver, but when I try to map the cards registers, I get the following.. pci_map_mem failed: device's memrange 0x6100-0x61ff is incompatible with its bridge's memrange 0x2000000-0xffffffff There seems to be some comment in German in pci.c about this case, so I was wondering if something is broken.. If not, what am I doing wrong here? Thanks, Chris Csanady From owner-freebsd-hackers Fri Jun 20 10:44:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA14633 for hackers-outgoing; Fri, 20 Jun 1997 10:44:12 -0700 (PDT) Received: from mail2.lancs.ac.uk (mail2.lancs.ac.uk [148.88.8.13]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA14628 for ; Fri, 20 Jun 1997 10:44:08 -0700 (PDT) Received: from unixc.lancs.ac.uk by mail2.lancs.ac.uk with SMTP (PP); Fri, 20 Jun 1997 18:44:02 +0100 Received: (from costa@localhost) by unixc.lancs.ac.uk (8.8.4/8.6.12) id SAA15099; Fri, 20 Jun 1997 18:43:56 +0100 (BST) Date: Fri, 20 Jun 1997 18:43:56 +0100 (BST) From: EMANUELE COSTA To: freebsd-hackers@FreeBSD.org Subject: Problems with 2.2.1 release Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, I've just downloaded the 2.2.1 release of freebsd and I've got a big problem! Whenever I try to use the boot disk it happens that while expanding or decompressing the kernel a "bad crc error" occurs and consequently the system crashes, ( it needs a cold reboot!). I tried the disk on different computers and it worked fine, so I decided to test all the various version and what I get is: 1) 2.1.7 can boot, ( no errors) 2) 2.2.1 error 3) 2.2.2 error so it seems that the kernel from version 2.2.1 is incompatible with my computer! I've bought my computer six mounth ago and it has the following characteristics: 1) acer pentium 133 mhz 2) 16 mg ram 3) pci bus type 4) bloody windows 95 ready! so I can't see why this is happening. Thanks in advance for your help, EMANUELE -- e-mail: costa@unix.lancs.ac.uk http://www.leganordsen.it/ From owner-freebsd-hackers Fri Jun 20 10:45:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA14689 for hackers-outgoing; Fri, 20 Jun 1997 10:45:22 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA14679; Fri, 20 Jun 1997 10:45:07 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-38.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA20916 (5.67b/IDA-1.5); Fri, 20 Jun 1997 19:44:56 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id TAA21304; Fri, 20 Jun 1997 19:44:56 +0200 (CEST) X-Face: " Date: Fri, 20 Jun 1997 19:44:55 +0200 From: Stefan Esser To: Troy Curtiss Cc: freebsd-hackers@FreeBSD.ORG, Stefan Esser Subject: Re: USB -- How tricky will it be to support? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Troy Curtiss on Fri, Jun 20, 1997 at 08:38:46AM -0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jun 20, Troy Curtiss wrote: > Hackers, > How tricky is USB going to be to support? Some of the mechanisms > such as hot plug/unplug, auto-detection and driver allocation, addressing, > and etc. don't look easy... The paradigm feels like a cross between the > PC-Card stuff (for the plug/unplug) and a PCI-bus (for addressing and > detection). I have looked a little at USB, and found that the most tricky part is support of isochronous devices (sound cards, modems, ...) Probing and attaching an USB chip is not hard, but USB is more like SCSI than a network driver: There are many classes of devices which all use their own command sets. We'll need a well designed "generic" layer, which has to take e.g. time synchronization of USB devices into account. In fact, there are quite detailed instructions on how a USB driver should interface to such a generic layer. I don't like the style of the code examples given in the USB UHCI (Universal Host Controller Interface) specification, but at least that a start ... :) > Anybody toyed with supporting USB yet? I'm curious what angle to > attack this subsystem from. Well, start by reading all available USB specs. Then take a look at some implementation of a USB bridge (i.e. Intel PIIX-3 or -4). Then tell us about your proposed architecture, best if you include a working prototype :) I'd be insterested to work on this, but have (too many) higher priority tasks, currently. But at least, I think we should start a discussion on how to attack USB ... Regards, STefan From owner-freebsd-hackers Fri Jun 20 11:02:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA15612 for hackers-outgoing; Fri, 20 Jun 1997 11:02:09 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA15607 for ; Fri, 20 Jun 1997 11:02:02 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id LAA12386; Fri, 20 Jun 1997 11:01:46 -0700 (PDT) Message-Id: <199706201801.LAA12386@austin.polstra.com> To: luoqi@sabrina.watermarkgroup.com Subject: Re: ld -T bug Newsgroups: polstra.freebsd.hackers In-Reply-To: <199706190539.BAA11739@sabrina.watermarkgroup.com> References: <199706190539.BAA11739@sabrina.watermarkgroup.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Date: Fri, 20 Jun 1997 11:01:46 -0700 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199706190539.BAA11739@sabrina.watermarkgroup.com>, Luoqi Chen wrote: > link was successful, but it seemed that > ld had written RSS section at the wrong offset in the executable file, > it was written as if the start address was still the default. So ld.so > won't see them at expected location and results in a segmentation fault. > This problem goes away when binding statically (e.g. building the kernel) > as there is no RSS section. > > I have attached a fix for this problem. Could anyone commit this to > the CVS tree? Thanks. This bug was already fixed in -current on May 13. The fix hasn't been merged into -2.2 yet. By the way, please always specify which version of FreeBSD you're running when you report a problem. 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 Fri Jun 20 11:40:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA17321 for hackers-outgoing; Fri, 20 Jun 1997 11:40:17 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA17313 for ; Fri, 20 Jun 1997 11:40:14 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) id OAA26287; Fri, 20 Jun 1997 14:35:42 -0400 (EDT) Message-ID: <19970620143541.17175@vinyl.quickweb.com> Date: Fri, 20 Jun 1997 14:35:41 -0400 From: Mark Mayo To: hackers@freebsd.org Subject: FreeBSD cracks DES ! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just thought I'd mention that the RSA DES challenge is over, and that the winning client was a DESCHALL machine, **** running on FreeBSD *** !! Neato. The search ended after 25% of the keyspace was searched (50% globablly). Considering the odds of that, combined with the fact that FreeBSD was collectively only cracking about 1-2% of the keys, I'd say the gods are on our side :-) -Mark -- ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ---------------------------------------------------------------------------- University degrees are a bit like adultery: you may not want to get involved with that sort of thing, but you don't want to be thought incapable. -Sir Peter Imbert From owner-freebsd-hackers Fri Jun 20 11:51:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA17890 for hackers-outgoing; Fri, 20 Jun 1997 11:51:50 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA17883 for ; Fri, 20 Jun 1997 11:51:44 -0700 (PDT) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by agora.rdrop.com (8.8.5/8.8.5) with SMTP id LAA21444 for ; Fri, 20 Jun 1997 11:51:40 -0700 (PDT) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id OAA16184; Fri, 20 Jun 1997 14:49:22 -0400 Date: Fri, 20 Jun 1997 14:49:21 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: Chris Csanady cc: hackers@FreeBSD.ORG Subject: Re: pci_map_mem failed... In-Reply-To: <199706201726.MAA15908@friley01.res.iastate.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > pci_map_mem failed: device's memrange 0x6100-0x61ff is incompatible with its > bridge's memrange 0x2000000-0xffffffff that looks like an io register range to me, not a mem register range. From owner-freebsd-hackers Fri Jun 20 12:14:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA19407 for hackers-outgoing; Fri, 20 Jun 1997 12:14:41 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA19401 for ; Fri, 20 Jun 1997 12:14:34 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id MAA12625; Fri, 20 Jun 1997 12:13:55 -0700 (PDT) Message-Id: <199706201913.MAA12625@austin.polstra.com> To: mark@quickweb.com Subject: Re: make world error in RELENG_2_2 Newsgroups: polstra.freebsd.hackers In-Reply-To: <19970620120938.27122@vinyl.quickweb.com> References: <26359.866788909@time.cdrom.com> <19970620120938.27122@vinyl.quickweb.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Date: Fri, 20 Jun 1997 12:13:55 -0700 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > It's not a problem with cvsup. It's a fundamental flaw in the model > > of trying to "upgrade" a source tree by continually: > > > > a) Changing modified bits. > > b) Adding new ones. > > c) Not deleting the old ones. > > > > It's (c) which is the killer since you will eventually confuse the > > bezeesus out of the build system with old bits. Do you have the > > "delete" option turned on in your supfile? > > I turns out this is indeed the case... > [...] > I assumed that cvsup did (c) above, when it doesn't. You're certainly not the first person to get bitten by that. CVSup in general (exception described below) has the attitude, "If I didn't create it, I'm not allowed to delete it." Believe me, users get real offended if it behaves any other way. So things work just fine if you originally created your tree using CVSup. It knows it has the authority and the responsibility to clean up files that later get moved or deleted in the master source tree. When you have an existing source tree that was created by some other means, and you "adopt" it with CVSup, things get a little bit dicier. The exception I mentioned above does its best to deal with this scenario, but it's not perfect. Here's one way to adopt a tree that should work 100% fine: 1. Start with a definite known version of the source tree. Let's say it's FreeBSD-2.2.2-RELEASE, for example. 2. To adopt the tree accurately, do one CVSup update specifying the exact release that you have. In this case, you use "tag=RELENG_2_2_2_RELEASE". The update should of course make no changes to your tree. But it will have the side-effect of allowing CVSup to feel that it "owns" all of the files. (Its ability to "feel" is one of its many advanced features. :-) 3. Now change your tag to whatever you really want, e.g., "tag=RELENG_2_2" for -2.2-stable. Do another CVSup update. Any files that should be added or deleted will be handled properly. Trouble can arise if step 2 is skipped. Then, any files in your -2.2.2 tree that no longer exist in -stable are essentially considered unknown extra files and left alone. The greater the distance between your starting revision and the one you're trying to get to, the more of a problem this becomes. (As I describe this, I am thinking that I might be able to make it do better in a future release. I am also thinking that this would be a very good topic for discussion in the non-existent CVSup FAQ. :-) One final point -- I have to agree that you were ill-used by the orginal respondent. Hastening to add that he's a highly valued member of the development team, I nevertheless have to say that perhaps he's used up his patience reserve for "make world is broken" questions and should just stop answering them for a while. -- 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 Fri Jun 20 13:07:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA21662 for hackers-outgoing; Fri, 20 Jun 1997 13:07:47 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA21655 for ; Fri, 20 Jun 1997 13:07:45 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) id QAA27118; Fri, 20 Jun 1997 16:02:37 -0400 (EDT) Message-ID: <19970620160235.20002@vinyl.quickweb.com> Date: Fri, 20 Jun 1997 16:02:35 -0400 From: Mark Mayo To: John Polstra Cc: mark@quickweb.com, hackers@freebsd.org Subject: Re: make world error in RELENG_2_2 References: <26359.866788909@time.cdrom.com> <19970620120938.27122@vinyl.quickweb.com> <199706201913.MAA12625@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: <199706201913.MAA12625@austin.polstra.com>; from John Polstra on Fri, Jun 20, 1997 at 12:13:55PM -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, Jun 20, 1997 at 12:13:55PM -0700, John Polstra wrote: > > > It's not a problem with cvsup. It's a fundamental flaw in the model > > > of trying to "upgrade" a source tree by continually: > > > > > > a) Changing modified bits. > > > b) Adding new ones. > > > c) Not deleting the old ones. > > > > > > It's (c) which is the killer since you will eventually confuse the > > > bezeesus out of the build system with old bits. Do you have the > > > "delete" option turned on in your supfile? > > > > I turns out this is indeed the case... > > [...] > > I assumed that cvsup did (c) above, when it doesn't. > > You're certainly not the first person to get bitten by that. CVSup > in general (exception described below) has the attitude, "If I > didn't create it, I'm not allowed to delete it." Believe me, users > get real offended if it behaves any other way. So things work just > fine if you originally created your tree using CVSup. It knows it > has the authority and the responsibility to clean up files that > later get moved or deleted in the master source tree. Ok. I get it. That seems reasonable - indeed, good material for the FAQ. :-) > [SNIP] > that should work 100% fine: > > 1. Start with a definite known version of the source tree. > Let's say it's FreeBSD-2.2.2-RELEASE, for example. > > 2. To adopt the tree accurately, do one CVSup update specifying the > exact release that you have. In this case, you use > "tag=RELENG_2_2_2_RELEASE". The update should of course make > no changes to your tree. But it will have the side-effect of > allowing CVSup to feel that it "owns" all of the files. (Its > ability to "feel" is one of its many advanced features. :-) > > 3. Now change your tag to whatever you really want, e.g., > "tag=RELENG_2_2" for -2.2-stable. Do another CVSup update. > Any files that should be added or deleted will be handled > properly. Excellent. I'll add this to my tutorial, I'm sure a lot of people didn't know this is how it works. > [SNIP] > for discussion in the non-existent CVSup FAQ. :-) Or even the man page. Even a quick mention that cvsup won't delete files that it doesn't "own" would be good. In general, I think a lot more could be written about the whole FreeBSD build procedure. I'll write what I can, and post to the list when I'm done for a review. -Mark > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-knowledge is always bad news." -- John Barth -- ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ---------------------------------------------------------------------------- University degrees are a bit like adultery: you may not want to get involved with that sort of thing, but you don't want to be thought incapable. -Sir Peter Imbert From owner-freebsd-hackers Fri Jun 20 13:14:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA22205 for hackers-outgoing; Fri, 20 Jun 1997 13:14:59 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA22193 for ; Fri, 20 Jun 1997 13:14:52 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA28311; Fri, 20 Jun 1997 13:06:48 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd028307; Fri Jun 20 20:06:40 1997 Message-ID: <33AAE28B.167EB0E7@whistle.com> Date: Fri, 20 Jun 1997 13:05:31 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Igor CC: hackers@FreeBSD.ORG Subject: Re: kernel's debugging, next References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Igor wrote: > > >>what are the methods of debugging kernel's code ? > > >trace code is one. > > Can I do on-line debugging (not post-mortem) kernel's code and how ? > Where can I read instructions ? > > --- > igor@blik.samara.su (Igor) look at http://www.freebsd.org/handbook/handbook265.html#591 this is relative and automatically generated, but it should be constant for a day or two. if it seems to be wrong just look it up in the handbook yourself.. http://www.freebsd.org/handbook From owner-freebsd-hackers Fri Jun 20 14:58:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA27372 for hackers-outgoing; Fri, 20 Jun 1997 14:58:09 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA27367 for ; Fri, 20 Jun 1997 14:58:07 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA24616; Fri, 20 Jun 1997 14:47:06 -0700 From: Terry Lambert Message-Id: <199706202147.OAA24616@phaeton.artisoft.com> Subject: Re: OpenBSD To: tom@sdf.com (Tom Samplonius) Date: Fri, 20 Jun 1997 14:47:06 -0700 (MST) Cc: mrcpu@cdsnet.net, hackers@FreeBSD.ORG In-Reply-To: from "Tom Samplonius" at Jun 19, 97 01:12:47 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 > > Anybody running FreeBSD given it a shot just to see? I have been > > thinking about it to see if it fixes my UFS problems that are seemingly > > unrepairable. > > UFS problem? He's talking about his "free xxx isn't" race condition errors. 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 Jun 20 15:02:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA27569 for hackers-outgoing; Fri, 20 Jun 1997 15:02:46 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA27564 for ; Fri, 20 Jun 1997 15:02:39 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA24629; Fri, 20 Jun 1997 14:51:09 -0700 From: Terry Lambert Message-Id: <199706202151.OAA24629@phaeton.artisoft.com> Subject: Re: xperfmon++ problem (again) To: dawes@xfree86.org (David Dawes) Date: Fri, 20 Jun 1997 14:51:09 -0700 (MST) Cc: skynyrd@opus.cts.cwu.edu, hackers@FreeBSD.ORG In-Reply-To: <19970620115409.62437@rf900.physics.usyd.edu.au> from "David Dawes" at Jun 20, 97 11:54:09 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 > You can add it to your host.def. We don't plan on adding things like > this to the default .cf files. It would make compiles so fast that people wouldn't bother working on nitpicky little optimiations, and then where would we be... 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 Jun 20 15:15:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA28084 for hackers-outgoing; Fri, 20 Jun 1997 15:15:40 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA28077 for ; Fri, 20 Jun 1997 15:15:36 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA24655; Fri, 20 Jun 1997 15:04:54 -0700 From: Terry Lambert Message-Id: <199706202204.PAA24655@phaeton.artisoft.com> Subject: Re: Suggested changed to sys/socket.h To: dg@root.com Date: Fri, 20 Jun 1997 15:04:53 -0700 (MST) Cc: joe@pavilion.net, hackers@FreeBSD.ORG In-Reply-To: <199706201208.FAA13012@implode.root.com> from "David Greenman" at Jun 20, 97 05:08:53 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >Is there any reason why /usr/src/sys/sys/socket.h > >shouldn't be changed like this: > > > >*** socket.h Fri Aug 30 03:18:24 1996 > >--- socket-new.h Fri Jun 20 10:55:14 1997 > >*************** > >*** 249,255 **** > >--- 249,257 ---- > > /* > > * Maximum queue length specifiable by listen. > > */ > >+ #ifndef SOMAXCONN > > #define SOMAXCONN 128 > >+ #endif /*!SOMAXCONN*/ > > Yes; you can also set it with the sysctl variable kern.somaxconn. The > value in socket.h is only a default - the best way to tune this is in your > /etc/rc.local. Not to mention that you might include socket.h otherwise, and not have the kernel config gile definition in scope at the time. Really, the value should be statrtup initialized and caches from sysctl instead of hard-coded in user programs. 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 Jun 20 15:18:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA28247 for hackers-outgoing; Fri, 20 Jun 1997 15:18:42 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA28242 for ; Fri, 20 Jun 1997 15:18:40 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id PAA15225; Fri, 20 Jun 1997 15:18:31 -0700 (PDT) Message-Id: <199706202218.PAA15225@austin.polstra.com> To: marcs@znep.com Subject: Re: Apache 1.1.3 and 1.2.0 problems under FBSD2.2.2 Newsgroups: polstra.freebsd.hackers In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Date: Fri, 20 Jun 1997 15:18:30 -0700 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , Marc Slemko wrote: > > Grr. I thought this had been fixed in FreeBSD, but I guess not. > The problem here is that the FILE structure uses only a short for > _file, which means it can only handle 255 fds. Er ... that's a mighty strange "short" you've got there, if it can only hold a number up to 255. Maybe you should upgrade to a 32-bit machine. :-) -- 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 Fri Jun 20 15:19:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA28312 for hackers-outgoing; Fri, 20 Jun 1997 15:19:30 -0700 (PDT) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA28307 for ; Fri, 20 Jun 1997 15:19:27 -0700 (PDT) Received: by kaori.Communique.Net with Internet Mail Service (5.0.1457.3) id ; Fri, 20 Jun 1997 17:18:51 -0500 Message-ID: From: Raul Zighelboim To: hackers@FreeBSD.ORG Subject: RE: SMC 9332BDT Help me please... Date: Fri, 20 Jun 1997 17:18:48 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I just finished upgrading 3 servers to the SMC newer card, using the latest drivers from http://www.3am-software.com (I think they are date June 18). The cards are performing alright on a 10baseT switch. but..... Whenever I move the cards to my 100baseTX hub, i get _verry poor_ performance. At this time, I am iyoko:~$ netstat -w 8 input (Total) output packets errs bytes packets errs bytes colls 904 0 280436 831 0 367682 32 1012 0 258319 1017 0 413742 48 if I swap the card to the 10obaseTX hub, input drops to 1/2, output drops to 1/10 of the traffic: iyoko:~$ netstat -w 8 input (Total) output packets errs bytes packets errs bytes colls 904 0 131634 374 0 54872 32 1012 0 112762 321 0 67218 48 and keeps goping down as time goes on.... Is this an effect of the driver, a broken card (3 of them) or a limitation on ???? My kernel says: de0 rev 32 int a irq 11 on pci0:14 de0: SMC 9332BDT 21140A [10-100Mb/s] pass 2.0 de0: address 00:e0:29:05:9c:c0 de0: media: 1="10baseT" 2="Full Duplex 10baseT" 3="100baseTX" 4="Full Duplex 100baseTX" and de0: enabling 100baseTX port de0: enabling 10baseT port de0: enabling 100baseTX port de0: link down: cable problem? de0: enabling 10baseT port as I move the card from one hub to the other. > -----Original Message----- > From: Narvi [SMTP:narvi@haldjas.folklore.ee] > Sent: Friday, June 20, 1997 7:25 AM > To: Nadav Eiron > Cc: Samy Touati; questions@FreeBSD.ORG; hackers@FreeBSD.ORG > Subject: Re: SMC 9332BDT Help me please... > > > [I hope anyone answering is wiser than me and deletes either -hackers > or > -questions from the cc: list] > > On Fri, 20 Jun 1997, Nadav Eiron wrote: > > > > > > > On Thu, 19 Jun 1997, Samy Touati wrote: > > > > > > > > > > > Hi, > > > > > > > > > In the rel notes of 2.2.2 it's clear that the SMC9332 BDT should > work. > > > I installed one and it dies as soon as it gets probed by the > kernel at > > > boot time. > > > The chipset 21140A is identified with pass 2.0 and it tries to > enable the > > > 100TX port. > > > > The newer versions of the 21140A chipset are not supported by the > current > > driver. However, a replacement (beta quality) driver is available > at: > > > > http://www.3am-software.com > > > > Most people report it to work fine with the newer cards. Also look > in the > > hackers list archives for discussions of newer de drivers. > > Why are you calling it beta quality? It is at least as good as the old > driver (zero problems with both around here). As for replacement - > FreeBSD > de driver hasn't just been resyncronised yet with the independent, > multiplatform, etc. de driver. And so it lacks some features. > > Sander > > There is no love, no good, no happiness and no future - > all these are just illusions. > > [snip] From owner-freebsd-hackers Fri Jun 20 15:25:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA28552 for hackers-outgoing; Fri, 20 Jun 1997 15:25:15 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA28545 for ; Fri, 20 Jun 1997 15:25:12 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id PAA15291; Fri, 20 Jun 1997 15:25:06 -0700 (PDT) Message-Id: <199706202225.PAA15291@austin.polstra.com> To: mark@quickweb.com Subject: Re: make world error in RELENG_2_2 Newsgroups: polstra.freebsd.hackers In-Reply-To: <19970620160235.20002@vinyl.quickweb.com> References: <19970620120938.27122@vinyl.quickweb.com> <199706201913.MAA12625@austin.polstra.com> <19970620160235.20002@vinyl.quickweb.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Date: Fri, 20 Jun 1997 15:25:06 -0700 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <19970620160235.20002@vinyl.quickweb.com>, Mark Mayo wrote: > > [SNIP] > > for discussion in the non-existent CVSup FAQ. :-) > > Or even the man page. Even a quick mention that cvsup won't delete > files that it doesn't "own" would be good. Well, it's always a mistake to defend your own man page, but still I'll point out that cvsup(1) does say this: In general, CVSup deletes only files which are known to the server. Extra files present in the client's tree are left alone, even in exact mode. More precisely, CVSup is willing to delete two classes of files: o Files that were previously created or updated by CVSup itself. o Checked-out versions of files which are marked as dead on the server. 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 Fri Jun 20 15:29:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA28697 for hackers-outgoing; Fri, 20 Jun 1997 15:29:17 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA28688 for ; Fri, 20 Jun 1997 15:29:11 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id PAA03483; Fri, 20 Jun 1997 15:29:42 -0700 (PDT) Message-ID: <19970620152941.01199@hydrogen.nike.efn.org> Date: Fri, 20 Jun 1997 15:29:41 -0700 From: John-Mark Gurney To: Mark Mayo Cc: hackers@FreeBSD.ORG Subject: Re: make world error in RELENG_2_2 References: <26359.866788909@time.cdrom.com> <19970620120938.27122@vinyl.quickweb.com> <199706201913.MAA12625@austin.polstra.com> <19970620160235.20002@vinyl.quickweb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <19970620160235.20002@vinyl.quickweb.com>; from Mark Mayo on Fri, Jun 20, 1997 at 04:02:35PM -0400 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mark Mayo scribbled this message on Jun 20: > On Fri, Jun 20, 1997 at 12:13:55PM -0700, John Polstra wrote: > > You're certainly not the first person to get bitten by that. CVSup > > in general (exception described below) has the attitude, "If I > > didn't create it, I'm not allowed to delete it." Believe me, users > > get real offended if it behaves any other way. So things work just > > fine if you originally created your tree using CVSup. It knows it > > has the authority and the responsibility to clean up files that > > later get moved or deleted in the master source tree. > > Ok. I get it. That seems reasonable - indeed, good material for the > FAQ. :-) hmmm... maybe also talking about how you can modify $BASEDIR/sup/modulename/checkouts.cvs to force cvsup to think it owns all the files in a tree... I remeber I had VERY similar problems, but I started with a CVS tree instead of the source tree... I probably still have the email from John Polstra about it... :) hope this helps some others too... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hackers Fri Jun 20 15:47:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA29660 for hackers-outgoing; Fri, 20 Jun 1997 15:47:44 -0700 (PDT) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA29648 for ; Fri, 20 Jun 1997 15:47:37 -0700 (PDT) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.5/8.8.5) with UUCP id QAA29934; Fri, 20 Jun 1997 16:46:29 -0600 (MDT) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id QAA20181; Fri, 20 Jun 1997 16:47:04 -0600 (MDT) Date: Fri, 20 Jun 1997 16:47:03 -0600 (MDT) From: Marc Slemko To: John Polstra cc: hackers@freebsd.org Subject: Re: Apache 1.1.3 and 1.2.0 problems under FBSD2.2.2 In-Reply-To: <199706202218.PAA15225@austin.polstra.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 Grr. Sigh, sorry... too much Solaris on my brain. I wrote short without thinking short. Thanks. Now I have to figure out the real reason it breaks. There appears to be no problems on BSD/OS. Something doesn't like having a lot of fds... On Fri, 20 Jun 1997, John Polstra wrote: > In article , > Marc Slemko wrote: > > > > Grr. I thought this had been fixed in FreeBSD, but I guess not. > > The problem here is that the FILE structure uses only a short for > > _file, which means it can only handle 255 fds. > > Er ... that's a mighty strange "short" you've got there, if it can only > hold a number up to 255. Maybe you should upgrade to a 32-bit machine. :-) > -- > 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 Fri Jun 20 15:53:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA29962 for hackers-outgoing; Fri, 20 Jun 1997 15:53:28 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA29957 for ; Fri, 20 Jun 1997 15:53:23 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 20377 invoked by uid 1001); 20 Jun 1997 22:53:13 +0000 (GMT) To: mango@staff.communique.net Cc: hackers@FreeBSD.ORG Subject: RE: SMC 9332BDT Help me please... In-Reply-To: Your message of "Fri, 20 Jun 1997 17:18:48 -0500" References: X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 21 Jun 1997 00:53:13 +0200 Message-ID: <20375.866847193@verdi.nethelp.no> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I just finished upgrading 3 servers to the SMC newer card, using the > latest drivers from http://www.3am-software.com (I think they are date > June 18). > > The cards are performing alright on a 10baseT switch. but..... > Whenever I move the cards to my 100baseTX hub, i get _verry poor_ > performance. Have you checked whether the switch believes the port to be in half or full duplex mode? Problems like these are typical symptoms of card and switch not agreeing about the duplex mode. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Fri Jun 20 16:11:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA01106 for hackers-outgoing; Fri, 20 Jun 1997 16:11:50 -0700 (PDT) Received: from lsd.relcom.eu.net (lsd.relcom.eu.net [193.124.23.23]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA01099 for ; Fri, 20 Jun 1997 16:11:45 -0700 (PDT) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.5/8.8.5) id DAA26880; Sat, 21 Jun 1997 03:11:30 +0400 (MSD) Date: Sat, 21 Jun 1997 03:11:29 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= X-Sender: ache@lsd.relcom.eu.net To: John Polstra cc: marcs@znep.com, hackers@FreeBSD.ORG Subject: Re: Apache 1.1.3 and 1.2.0 problems under FBSD2.2.2 In-Reply-To: <199706202218.PAA15225@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Jun 1997, John Polstra wrote: > In article , > Marc Slemko wrote: > > > > Grr. I thought this had been fixed in FreeBSD, but I guess not. > > The problem here is that the FILE structure uses only a short for > > _file, which means it can only handle 255 fds. > > Er ... that's a mighty strange "short" you've got there, if it can only > hold a number up to 255. Maybe you should upgrade to a 32-bit machine. :-) It more sounds like FD_SETSIZE limit. It is why I increase default FD_SETSIZE to 1024 in -current :-) -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ From owner-freebsd-hackers Fri Jun 20 16:41:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA02462 for hackers-outgoing; Fri, 20 Jun 1997 16:41:59 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA02443 for ; Fri, 20 Jun 1997 16:41:37 -0700 (PDT) Received: from awfulhak.demon.co.uk (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id XAA27009; Fri, 20 Jun 1997 23:26:44 +0100 (BST) Message-Id: <199706202226.XAA27009@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: EMANUELE COSTA cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Problems with 2.2.1 release In-reply-to: Your message of "Fri, 20 Jun 1997 18:43:56 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Jun 1997 23:26:44 +0100 From: Brian Somers Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hi, > I've just downloaded the 2.2.1 release of freebsd and I've got a > big problem! > Whenever I try to use the boot disk it happens that while > expanding or decompressing the kernel a "bad crc error" occurs and > consequently the system crashes, ( it needs a cold reboot!). > I tried the disk on different computers and it worked fine, so I > decided to test all the various version and what I get is: > > 1) 2.1.7 can boot, ( no errors) > 2) 2.2.1 error > 3) 2.2.2 error [.....] I'd try writing a 2.2.1 image on your disk 1) and a 2.1.7 image on disk 2) to make sure that it's not a media thing. Some floppy drives just refuse to read stuff formatted by others - although it's not so common these days. > EMANUELE > > -- > e-mail: costa@unix.lancs.ac.uk > http://www.leganordsen.it/ > > -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Fri Jun 20 16:44:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA02633 for hackers-outgoing; Fri, 20 Jun 1997 16:44:32 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA02617 for ; Fri, 20 Jun 1997 16:44:13 -0700 (PDT) Received: from awfulhak.demon.co.uk (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id XAA26672; Fri, 20 Jun 1997 23:14:12 +0100 (BST) Message-Id: <199706202214.XAA26672@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: "Jordan K. Hubbard" cc: tom@tomqnx.com (Tom Torrance at home), mike@sentex.net, freebsd-hackers@FreeBSD.ORG Subject: Re: make world error in RELENG_2_2 In-reply-to: Your message of "Thu, 19 Jun 1997 23:41:49 PDT." <26359.866788909@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Jun 1997 23:14:12 +0100 From: Brian Somers Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I suspect that there IS some other problem, and it is/was with cvsup. > > I don't know why or how or if I contributed to it:-) > > It's not a problem with cvsup. It's a fundamental flaw in the model > of trying to "upgrade" a source tree by continually: > > a) Changing modified bits. > b) Adding new ones. > c) Not deleting the old ones. > > It's (c) which is the killer since you will eventually confuse the > bezeesus out of the build system with old bits. Do you have the ^^^^^^^^ That's "bejeesus" (or sometimes "bejaisus"). Your spelling is terrible :) > "delete" option turned on in your supfile? > > Jordan -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Fri Jun 20 17:18:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA04096 for hackers-outgoing; Fri, 20 Jun 1997 17:18:13 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA04091 for ; Fri, 20 Jun 1997 17:18:08 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.5/8.8.5) id TAA00330; Fri, 20 Jun 1997 19:16:53 -0500 (EST) From: "John S. Dyson" Message-Id: <199706210016.TAA00330@dyson.iquest.net> Subject: Re: OpenBSD In-Reply-To: <199706202147.OAA24616@phaeton.artisoft.com> from Terry Lambert at "Jun 20, 97 02:47:06 pm" To: terry@lambert.org (Terry Lambert) Date: Fri, 20 Jun 1997 19:16:38 -0500 (EST) Cc: tom@sdf.com, mrcpu@cdsnet.net, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 > > > Anybody running FreeBSD given it a shot just to see? I have been > > > thinking about it to see if it fixes my UFS problems that are seemingly > > > unrepairable. > > > > UFS problem? > > He's talking about his "free xxx isn't" race condition errors. > I am working on the problem. I know at least a reasonable explaination. Might have it committed tonight. John From owner-freebsd-hackers Fri Jun 20 17:30:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA04626 for hackers-outgoing; Fri, 20 Jun 1997 17:30:27 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA04621 for ; Fri, 20 Jun 1997 17:30:25 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA06626 for ; Fri, 20 Jun 1997 17:30:18 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd006607; Sat Jun 21 00:30:05 1997 Message-ID: <33AB2047.3F54BC7E@whistle.com> Date: Fri, 20 Jun 1997 17:28:55 -0700 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-stable IPFW warning Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk To fix some unrecoverably broken stuff in the firewall cade it was necessary to implement the same interface through a different method. this means that the ipfw program must match the kernel. Hopefully this is the last time this will be needed. The change has been tested and is in production here at whistle. I guess other programs that hit the firewall rules (e.g. natd) might need to be recompiled for the next 2.2 release I'll make (or help with) the changes if I can track them down.. I don't like making a change like this to -stable, but I couldn't see a way around this one and it's ramifications are limited to a small audience. julian From owner-freebsd-hackers Fri Jun 20 17:33:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA04769 for hackers-outgoing; Fri, 20 Jun 1997 17:33:23 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA04764 for ; Fri, 20 Jun 1997 17:33:19 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id KAA07690; Sat, 21 Jun 1997 10:03:11 +0930 (CST) From: Michael Smith Message-Id: <199706210033.KAA07690@genesis.atrad.adelaide.edu.au> Subject: Re: USB -- How tricky will it be to support? In-Reply-To: from Troy Curtiss at "Jun 20, 97 08:38:46 am" To: troyc@sandy.merix.com (Troy Curtiss) Date: Sat, 21 Jun 1997 10:03:10 +0930 (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 Troy Curtiss stands accused of saying: > Hackers, > How tricky is USB going to be to support? >From my reading, quite. It's very heavy on the software side. > Some of the mechanisms > such as hot plug/unplug, auto-detection and driver allocation, addressing, > and etc. don't look easy... The paradigm feels like a cross between the > PC-Card stuff (for the plug/unplug) and a PCI-bus (for addressing and > detection). Yup. It needs to be developed in the context of a generalised demand-loaded/unloaded device driver model, and it'll need to make heavy use of devfs. You should have a look at Doug R.'s new ISA code as well, as providing he has the time to keep working on it, it's the best place to start. ` The generalised driver framework is the infrastrucrure required; things like USB will come "almost" (ha!) for free once it's in place. > Anybody toyed with supporting USB yet? I'm curious what angle to > attack this subsystem from. I read through several of the spec documents and decided I just didn't have the time to spend on it (and no USB hardware to try with either). If you wanted to do _something_ in the current context, I'd humbly suggest developing the various functional components in a very black-box fashion, so that you can reuse them later; concetrate on the protocol and detection code, that sort of stuff. > | Troy Curtiss, HW/SW Engineer | Email: troyc@merix.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 Jun 20 17:54:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA05782 for hackers-outgoing; Fri, 20 Jun 1997 17:54:28 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA05774 for ; Fri, 20 Jun 1997 17:54:24 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wfEOY-0004qS-00; Fri, 20 Jun 1997 17:51:14 -0700 Date: Fri, 20 Jun 1997 17:51:13 -0700 (PDT) From: Tom Samplonius To: Terry Lambert cc: mrcpu@cdsnet.net, hackers@freebsd.org Subject: Re: OpenBSD In-Reply-To: <199706202147.OAA24616@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Jun 1997, Terry Lambert wrote: > > > Anybody running FreeBSD given it a shot just to see? I have been > > > thinking about it to see if it fixes my UFS problems that are seemingly > > > unrepairable. > > > > UFS problem? > > He's talking about his "free xxx isn't" race condition errors. What exactly is it about this condition that makes it occur on some machines? I don't see it on a 16GB and a 8GB news spool here. No corruption problmes either (although it was not clear to me, whether the corruption is just a result of the panic, or just another effect of this problem). > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > Tom From owner-freebsd-hackers Fri Jun 20 18:16:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA06507 for hackers-outgoing; Fri, 20 Jun 1997 18:16:40 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA06502 for ; Fri, 20 Jun 1997 18:16:37 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id SAA02814 for hackers@freebsd.org; Fri, 20 Jun 1997 18:16:36 -0700 Date: Fri, 20 Jun 1997 18:16:36 -0700 From: Sean Eric Fagan Message-Id: <199706210116.SAA02814@kithrup.com> To: hackers@freebsd.org Subject: "Go Solo 2" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I got a complimentary copy of _Go Solo 2: The Authorized Guide to Version 2 of the Single UNIX(r) Specification_ today (one of the few perqs for being moderator of comp.std.unix). One of the nicest things about it is that it has man pages (in HTML format) for all of the library functions and commands that are required to be "UNIX." (Well, it's *supposed* to be all; I haven't done an exhaustive search yet. But it looks fairly complete. They're also there in PDF format, apparantly.) So far, it seems considerably more useful than the first version. (I'll poke around it, and post a full review on comp.std.unix soon, hopefully.) Anyway, I thought it may be useful to some people, so I thought I'd mention it. Sean. From owner-freebsd-hackers Fri Jun 20 18:33:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA07195 for hackers-outgoing; Fri, 20 Jun 1997 18:33:10 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA07189 for ; Fri, 20 Jun 1997 18:33:06 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wfF0A-0004tE-00; Fri, 20 Jun 1997 18:30:06 -0700 Date: Fri, 20 Jun 1997 18:30:06 -0700 (PDT) From: Tom Samplonius To: sthaug@nethelp.no cc: mango@staff.communique.net, hackers@freebsd.org Subject: RE: SMC 9332BDT Help me please... In-Reply-To: <20375.866847193@verdi.nethelp.no> 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, 21 Jun 1997 sthaug@nethelp.no wrote: > > I just finished upgrading 3 servers to the SMC newer card, using the > > latest drivers from http://www.3am-software.com (I think they are date > > June 18). > > > > The cards are performing alright on a 10baseT switch. but..... > > Whenever I move the cards to my 100baseTX hub, i get _verry poor_ > > performance. > > Have you checked whether the switch believes the port to be in half or > full duplex mode? Problems like these are typical symptoms of card and > switch not agreeing about the duplex mode. > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no Yes, when connected to a hub, the card MUST be set to half-duplex. Tom From owner-freebsd-hackers Sat Jun 21 00:23:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA17497 for hackers-outgoing; Sat, 21 Jun 1997 00:23:37 -0700 (PDT) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA17481 for ; Sat, 21 Jun 1997 00:23:32 -0700 (PDT) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.5/8.8.5) with UUCP id BAA27063 for hackers@freebsd.org; Sat, 21 Jun 1997 01:23:20 -0600 (MDT) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id BAA22758 for ; Sat, 21 Jun 1997 01:22:50 -0600 (MDT) Date: Sat, 21 Jun 1997 01:22:50 -0600 (MDT) From: Marc Slemko To: hackers@freebsd.org Subject: gethostbyname() and fds >255 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If I run the following program: #define FD_SETSIZE 1024 #include #include #include #include #include #include #include int main () { char s[1024]; int i; struct hostent *h; for (i = 0; i < 400; i++) { sprintf(s, "test/%d", i); if (open(s, O_RDWR|O_CREAT, 0666) == -1) err(1, "open of %s failed", s); if (!(h = gethostbyname("www.worldgate.com"))) { herror("gethostbyname failed"); exit(1); } h = gethostbyname("www.worldgate.com"); printf("%d: host = %s (%s)\n", i, inet_ntoa(*(struct in_addr *)(u_int *)h->h_addr), h->h_name); } exit(0); } On 2.2-stable from a month or so ago with ulimit -n 2048 I get: 0: host = 198.161.84.2 (valis.worldgate.com) 1: host = 198.161.84.2 (valis.worldgate.com) 2: host = 198.161.84.2 (valis.worldgate.com) 3: host = 198.161.84.2 (valis.worldgate.com) [...] 249: host = 198.161.84.2 (valis.worldgate.com) 250: host = 198.161..84.2 (valis.worldgate.com) 251: host = 198.161.84.2 (valis.worldgate.com) gethostbyname failed: Unknown host For comparison, it works fine on BSD/OS 2.1. Does it work in -current? Ideas? If I remove the gethostbyname, I can open >255 fds without problem. From owner-freebsd-hackers Sat Jun 21 01:08:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA18641 for hackers-outgoing; Sat, 21 Jun 1997 01:08:45 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA18636 for ; Sat, 21 Jun 1997 01:08:41 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id BAA28278; Sat, 21 Jun 1997 01:08:37 -0700 (PDT) To: Marc Slemko cc: hackers@FreeBSD.ORG Subject: Re: gethostbyname() and fds >255 In-reply-to: Your message of "Sat, 21 Jun 1997 01:22:50 MDT." Date: Sat, 21 Jun 1997 01:08:36 -0700 Message-ID: <28274.866880516@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > For comparison, it works fine on BSD/OS 2.1. Does it work in -current? It would appear to: 396: host = 198.161.84.2 (valis.worldgate.com) 397: host = 198.161.84.2 (valis.worldgate.com) 398: host = 198.161.84.2 (valis.worldgate.com) 399: host = 198.161.84.2 (valis.worldgate.com) root@make-> uname -a FreeBSD make.ican.net 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Mon Jun 16 13:10:14 EDT 1997 jkh@make.ican.net:/a/local/src/sys/compile/MAKE i386 It does indeed fall over on my 2.2-stable system. Jordan From owner-freebsd-hackers Sat Jun 21 01:34:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA19192 for hackers-outgoing; Sat, 21 Jun 1997 01:34:07 -0700 (PDT) Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA19152 for ; Sat, 21 Jun 1997 01:33:47 -0700 (PDT) Received: (babkin@localhost) by hq.icb.chel.su (8.8.3/8.6.5) id OAA00684; Sat, 21 Jun 1997 14:35:17 +0600 (ESD) From: "Serge A. Babkin" Message-Id: <199706210835.OAA00684@hq.icb.chel.su> Subject: Re: RSA5 Encryption Cracked.. To: black@zen.cypher.net (Ben Black) Date: Sat, 21 Jun 1997 14:35:16 +0600 (ESD) Cc: msanders@aros.net, hudginsj@smtp.dancooks.com, hackers@FreeBSD.ORG In-Reply-To: from "Ben Black" at Jun 18, 97 07:00:13 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > yes, i suspected it was the DES crack effort, and yes it is even cooler. > this is excellent ammunition for lifting export restrictions (assuming > the clinton administration doesn't shove kerrey's bill through). I have read some short article about cracking of DES. They said that there exists for about 10 years the possibility to crack DES in analythincal way (I think with enough amount of enciphered data). They recommended to use DES three times on the data to get real security. -SB > > On Wed, 18 Jun 1997, Michael K. Sanders wrote: > > > In message <11F12637A8E@smtp.dancooks.com>, "Jason Hudgins" writes: > > > > > > I just thought some of you might be happy to know that the > > >Deschall project just successfully cracked an RC5 encrypted message > > >with a 56 bit key. The really cool thing is that it was one of the > > >1-2% machines that was running FreeBSD! The majority of the > > >machines hacking away cpu cylces were running windows and solaris. > > > They found the key after searching through only 25% of the > > >keyspace. Even though it was really just a matter of luck, I still > > >that it was pretty cool. > > > > Just to clarify, it was a 56-bit _DES_ encrypted message [1]. > > > > ...and I think it's even cooler. > > > > [1]: "Strong cryptography makes the world a safer place." > > > From owner-freebsd-hackers Sat Jun 21 01:38:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA19372 for hackers-outgoing; Sat, 21 Jun 1997 01:38:12 -0700 (PDT) Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA19306 for ; Sat, 21 Jun 1997 01:35:56 -0700 (PDT) Received: (babkin@localhost) by hq.icb.chel.su (8.8.3/8.6.5) id OAA01256; Sat, 21 Jun 1997 14:38:26 +0600 (ESD) From: "Serge A. Babkin" Message-Id: <199706210838.OAA01256@hq.icb.chel.su> Subject: Re: debugging kernel's code To: igor@blik.samara.su (Igor) Date: Sat, 21 Jun 1997 14:38:25 +0600 (ESD) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Igor" at Jun 19, 97 07:41:58 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > what are the methods of debugging kernel's code ? There exists the DDB kernel debugger. I use it primarily for analysing the panics. There exisgs KGDB (Kernel GDB) too but I never tried to use it. And of course the classic method of adding printf()s is all the time with us! -SB From owner-freebsd-hackers Sat Jun 21 01:58:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA19801 for hackers-outgoing; Sat, 21 Jun 1997 01:58:31 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA19796 for ; Sat, 21 Jun 1997 01:58:27 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 23112 invoked by uid 1001); 21 Jun 1997 08:58:23 +0000 (GMT) To: jkh@time.cdrom.com Cc: marcs@znep.com, hackers@FreeBSD.ORG Subject: Re: gethostbyname() and fds >255 In-Reply-To: Your message of "Sat, 21 Jun 1997 01:08:36 -0700" References: <28274.866880516@time.cdrom.com> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 21 Jun 1997 10:58:23 +0200 Message-ID: <23110.866883503@verdi.nethelp.no> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > For comparison, it works fine on BSD/OS 2.1. Does it work in -current? > > It would appear to: > > 396: host = 198.161.84.2 (valis.worldgate.com) > 397: host = 198.161.84.2 (valis.worldgate.com) > 398: host = 198.161.84.2 (valis.worldgate.com) > 399: host = 198.161.84.2 (valis.worldgate.com) > root@make-> uname -a > FreeBSD make.ican.net 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Mon Jun 16 13:10:14 EDT 1997 jkh@make.ican.net:/a/local/src/sys/compile/MAKE i386 > > It does indeed fall over on my 2.2-stable system. The problem is in res_send(). In lib/libc/net/res_send.c line 577 in FreeBSD-current we have: if (s+1 > FD_SETSIZE) { #ifdef DEBUG if (_res.options & RES_DEBUG) fprintf(stderr, "res_send: too many files\n"); #endif res_close(); goto next_ns; } and FD_SETSIZE is statically defined as 256 in /usr/include/sys/types.h. For comparison, the following code was added between BIND-4.9.5-P1 and what will become BIND-4.9.6: if (s+1 > FD_SETSIZE) { Perror(stderr, "s+1 > FD_SETSIZE", EMFILE); res_close(); goto next_ns; } and BIND-8.1.1-T2B src/lib/resolv/res_send.c has at line 587: if (s+1 > FD_SETSIZE) { Perror(stderr, "s+1 > FD_SETSIZE", EMFILE); res_close(); goto next_ns; } Since this code was added between 4.9.5-P1 and 4.9.6, my guess is that it's an attempt to stop some sort of denial of service attack - but it looks like it may not be the best way to fix it. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Sat Jun 21 02:08:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA20128 for hackers-outgoing; Sat, 21 Jun 1997 02:08:27 -0700 (PDT) Received: from csd.cs.technion.ac.il (csd.cs.technion.ac.il [132.68.32.8]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id CAA20119 for ; Sat, 21 Jun 1997 02:08:18 -0700 (PDT) Received: from localhost (nadav@localhost) by csd.cs.technion.ac.il (8.6.11/8.6.10) with SMTP id MAA10367; Sat, 21 Jun 1997 12:07:21 +0300 X-Authentication-Warning: csd.cs.technion.ac.il: nadav owned process doing -bs Date: Sat, 21 Jun 1997 12:07:21 +0300 (IDT) From: Nadav Eiron X-Sender: nadav@csd To: Adrian Chadd cc: freebsd-hackers@FreeBSD.ORG Subject: Re: socket redirector In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Jun 1997, Adrian Chadd wrote: > Hey guys. > > I'm writing a quick socket redirector for something. Its run out of inetd, > and basically opens a socket somewhere and acts as a pipe between the two. > I'm using select(), and its working fine. The only problem I'm having is > that I don't know how to tell when the remote end closes the connection > down, so that I can just close everything down, and quit. > > Any ideas on how I'd do this? Why not just use plug-gw from the fwtk? From your description it sounds like just the thing you need. > > Thanks, > > -- > Adrian Chadd | "Unix doesn't stop you from doing > | stupid things because that would > | stop you from doing clever things" > > > Nadav From owner-freebsd-hackers Sat Jun 21 02:19:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA20457 for hackers-outgoing; Sat, 21 Jun 1997 02:19:36 -0700 (PDT) Received: from csd.cs.technion.ac.il (csd.cs.technion.ac.il [132.68.32.8]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id CAA20443 for ; Sat, 21 Jun 1997 02:19:27 -0700 (PDT) Received: from localhost (nadav@localhost) by csd.cs.technion.ac.il (8.6.11/8.6.10) with SMTP id MAA10413; Sat, 21 Jun 1997 12:15:26 +0300 X-Authentication-Warning: csd.cs.technion.ac.il: nadav owned process doing -bs Date: Sat, 21 Jun 1997 12:15:25 +0300 (IDT) From: Nadav Eiron X-Sender: nadav@csd To: gjennejohn@frt.dec.com cc: hackers@FreeBSD.ORG Subject: Re: Announcement: New DPT RAID Controller Driver Available In-Reply-To: <9706201528.AA25614@cssmuc.frt.dec.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Jun 1997 garyj@frt.dec.com wrote: > > jkh@time.cdrom.com writes: > > Unless, of course, they had something like the AMES wind tunnel > > providing forced airflow past the drives, then I suppose the plastic > > sled construction wouldn't really matter much, would it? :-) > > > > basically, the Storage Works thingies from DEC _do_ have a wind tunnel :) > I have one of these things at home and it has 2 large fans on the back > pushing (or pulling ?) air. Pulling. Wait a couple of months and you'll see the dust accumulate on the front of the drives... > > I've seen some pretty big RAID arrays here at DEC, all made using > plastic enclosures. They work good (although I have to agree with > an earlier poster that those flimsy flex connections are pretty cheesy > and *so* easy to ruin). > My previous employer had a pretty big OpenVMS cluster with giant SW800 racks (rough estimate - about 500 drives, total most 7200rpm). When filling up one of these racks, DEC recommends that you add a shelf of fans at the bottom to force some more air into it, but other than that, heat doesn't seem to be a problem. These plastic canisters seem to have great air flow. Just place your hand over the warm air outlet of one of these SW800s and feel how much heat it evacuates from the drives. > --- > Gary Jennejohn (work) gjennejohn@frt.dec.com > (home) Gary.Jennejohn@munich.netsurf.de > (play) gj@freebsd.org > > > Nadav From owner-freebsd-hackers Sat Jun 21 02:26:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA20741 for hackers-outgoing; Sat, 21 Jun 1997 02:26:30 -0700 (PDT) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA20736 for ; Sat, 21 Jun 1997 02:26:25 -0700 (PDT) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.5/8.8.5) with UUCP id DAA03471; Sat, 21 Jun 1997 03:26:18 -0600 (MDT) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id DAA23462; Sat, 21 Jun 1997 03:26:49 -0600 (MDT) Date: Sat, 21 Jun 1997 03:26:48 -0600 (MDT) From: Marc Slemko To: sthaug@nethelp.no cc: hackers@FreeBSD.ORG Subject: Re: gethostbyname() and fds >255 In-Reply-To: <23110.866883503@verdi.nethelp.no> 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, 21 Jun 1997 sthaug@nethelp.no wrote: > > > For comparison, it works fine on BSD/OS 2.1. Does it work in -current? > > > > It would appear to: > > > > 396: host = 198.161.84.2 (valis.worldgate.com) > > 397: host = 198.161.84.2 (valis.worldgate.com) > > 398: host = 198.161.84.2 (valis.worldgate.com) > > 399: host = 198.161.84.2 (valis.worldgate.com) > > root@make-> uname -a > > FreeBSD make.ican.net 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Mon Jun 16 13:10:14 EDT 1997 jkh@make.ican.net:/a/local/src/sys/compile/MAKE i386 > > > > It does indeed fall over on my 2.2-stable system. > > The problem is in res_send(). In lib/libc/net/res_send.c line 577 in > FreeBSD-current we have: Sigh. Yes, that's it. I found it an hour or so ago looking through things. For a test, rebuilding libc with FD_SETSIZE=1024 then linking it against my test program worked fine. That isn't very nice. It appears the only reason it works in -current (well, it will break at 1024 fds there...) is that FD_SETSIZE has been increased. Guess I'll have to double check what else was broken when FD_SETSIZE was increased and make a patch for 2.2 that I can point people to. My biggest concern in this is that Apache 1.2 will not work with >~255 fds used for logs without recompiling libc with a larger FD_SETSIZE. From owner-freebsd-hackers Sat Jun 21 02:31:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA20903 for hackers-outgoing; Sat, 21 Jun 1997 02:31:51 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id CAA20892 for ; Sat, 21 Jun 1997 02:31:46 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 23233 invoked by uid 1001); 21 Jun 1997 09:31:43 +0000 (GMT) To: marcs@znep.com Cc: hackers@FreeBSD.ORG Subject: Re: gethostbyname() and fds >255 In-Reply-To: Your message of "Sat, 21 Jun 1997 03:26:48 -0600 (MDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 21 Jun 1997 11:31:43 +0200 Message-ID: <23231.866885503@verdi.nethelp.no> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > The problem is in res_send(). In lib/libc/net/res_send.c line 577 in > > FreeBSD-current we have: > > Sigh. Yes, that's it. I found it an hour or so ago looking through > things. For a test, rebuilding libc with FD_SETSIZE=1024 then linking it > against my test program worked fine. Btw, I just reported it to bind-bugs@isc.org and pointed out that as a minimum a res_send() dependency on FD_SETSIZE should be documented. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Sat Jun 21 02:40:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA21217 for hackers-outgoing; Sat, 21 Jun 1997 02:40:57 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA21211 for ; Sat, 21 Jun 1997 02:40:54 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id TAA24130; Sat, 21 Jun 1997 19:38:28 +1000 Date: Sat, 21 Jun 1997 19:38:28 +1000 From: Bruce Evans Message-Id: <199706210938.TAA24130@godzilla.zeta.org.au> To: jkh@time.cdrom.com, sthaug@nethelp.no Subject: Re: gethostbyname() and fds >255 Cc: hackers@FreeBSD.ORG, marcs@znep.com Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >The problem is in res_send(). In lib/libc/net/res_send.c line 577 in >FreeBSD-current we have: > > if (s+1 > FD_SETSIZE) { >#ifdef DEBUG > if (_res.options & RES_DEBUG) > fprintf(stderr, > "res_send: too many files\n"); >#endif > res_close(); > goto next_ns; > } > >and FD_SETSIZE is statically defined as 256 in /usr/include/sys/types.h. >... FD_SETSIZE is statically defined as 1024 in -current. This just moves the problem. >Since this code was added between 4.9.5-P1 and 4.9.6, my guess is that >it's an attempt to stop some sort of denial of service attack - but it It is to prevent writing beyond the end of sdmask in in FD_SET(s, &sdmask). >looks like it may not be the best way to fix it. Library functions should not have arbitrary limits, so library code that wants to use select(2) should avoid using the official interface with statically defined fd_set's. This isn't easy, and it is only possible now that the kernel doesn't really implement the official interface. Bruce From owner-freebsd-hackers Sat Jun 21 04:20:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA25547 for hackers-outgoing; Sat, 21 Jun 1997 04:20:51 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA25542 for ; Sat, 21 Jun 1997 04:20:47 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id VAA26616; Sat, 21 Jun 1997 21:16:38 +1000 Date: Sat, 21 Jun 1997 21:16:38 +1000 From: Bruce Evans Message-Id: <199706211116.VAA26616@godzilla.zeta.org.au> To: FreeBSD-Hackers@FreeBSD.ORG, kjc@csl.sony.co.jp Subject: Re: High Resolution Timers, How? Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Solaris implements gethrtime(get high resolution time) that returns >a 64-bit value in nanoseconds since some arbitrary time. > >Its features are: > - simpler and faster > - higher resolution > - no sec/usec conversion required > - no clock adjustment (no time warp) > >hrtime seems to be an attractive alternative since microtime() is used >mostly to measure time delta, and easily implemented by extracting >part of microtime(). > >How about implementing gethrtime in FreeBSD? I'm not sure that microtime() really is used mostly to measure time deltas. I'm fairly sure that calculation of deltas is not more common than reading the time, so it wouldn't be a good tradeoff to do extra work when reading times to give binary format. A naive implementation would have to do something like mono_time.tv_sec * 1000000000LL + mono_time.tv_usec * 1000 extra, and the multiplication by 10^9 would be wasted when two times with the same tv_sec value are subtracted. A better implementation would keep a separate copy of `mono_time' in binary format. A better interface would use machine-dependent units to avoid premature scaling. Bruce From owner-freebsd-hackers Sat Jun 21 05:37:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA27525 for hackers-outgoing; Sat, 21 Jun 1997 05:37:24 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA27520 for ; Sat, 21 Jun 1997 05:37:20 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id WAA28756; Sat, 21 Jun 1997 22:35:08 +1000 Date: Sat, 21 Jun 1997 22:35:08 +1000 From: Bruce Evans Message-Id: <199706211235.WAA28756@godzilla.zeta.org.au> To: jhay@mikom.csir.co.za, joerg_wunsch@uriah.heep.sax.de Subject: Re: Proposed change to struct clockinfo Cc: hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> > As far as I can tell only 4 other files use the clockinfo structure and >> > they will work again after a recompile. They are: >> > lib/libc/gmon/gmon.c >> > usr.bin/time/time.c >> > usr.sbin/kgmon/kgmon.c >> > libexec/rpc.rstatd/rstat_proc.c >> suffice (i assume, even though strictly spoken, isn't it an interface >> change to an existing library function? -- this would mandate a major >> number bump, sigh). >> > >The interface to the library function does not change. The sysctl change >and lib/libc/gmon/gmon.c use that, so it will have to be recompiled to >work again. So I think the minor version bump that already happened >should be enough??? The other programs in the list above use the sysctl >direcly and would also have to be recompiled, but I don't think that is >a problem??? Strictly, it requires even more than a major version number bump. It breaks all programs linked to the old gmon object. To avoid breaking them, you have to implement a new sysctl to return the new struct. It's just like the non-problem with stat(2) and the problem with fcntl(2). When the size and shape of `struct stat' changed, there had to be a new syscall to prevent breakage. When the size (and shape?) of `struct flock' changed, there should have been a new syscall to prevent breakage (there wasn't). Anyway, only the static version of the gmon object in the profiling library is normally used, so changing the version number of the shared library won't help. The profiling library seems to be rarely used, and gmon has reasonable fallback code, so it is probably OK not to implement a new sysctl in this case. Bruce From owner-freebsd-hackers Sat Jun 21 05:57:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA28088 for hackers-outgoing; Sat, 21 Jun 1997 05:57:01 -0700 (PDT) Received: from squirrel.tgsoft.com (squirrel.tgsoft.com [207.167.64.183]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA28083 for ; Sat, 21 Jun 1997 05:56:58 -0700 (PDT) Received: (qmail 9970 invoked by uid 128); 21 Jun 1997 12:56:56 -0000 Date: 21 Jun 1997 12:56:56 -0000 Message-ID: <19970621125656.9969.qmail@squirrel.tgsoft.com> From: mark thompson To: avalon@coombs.anu.edu.au CC: hackers@FreeBSD.ORG In-reply-to: message from Darren Reed on Thu, 19 Jun 1997 11:50:11 +1000 (EST) Subject: Re: Status on LS-120 drive support? Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: Darren Reed Date: Thu, 19 Jun 1997 11:50:11 +1000 (EST) In some mail from Troy Curtiss, sie said: > > Anybody out there using those LS-120 drives yet? I think they > are IDE-interfaced. Looks like they hold 120MB and can read old > floppies (1.44M) too. If they are going to be supported (or going > to be commercially successful), they look like a better deal than > the Iomega Zip drives. Any thoughts? The LS-120 has two *heads* - one for current floppies and one for the new format. It is a plug-in replacement for floppy drives apparently. It may even work without a new driver (just diff. geometry) ? Sounds like a floptical. Anybody remember those? Still have one somewhere (rummage, rummage). An object lesson in "things not catching on". -mark From owner-freebsd-hackers Sat Jun 21 07:21:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA00403 for hackers-outgoing; Sat, 21 Jun 1997 07:21:12 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA00397 for ; Sat, 21 Jun 1997 07:21:06 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA12458 for hackers@FreeBSD.ORG; Sat, 21 Jun 1997 16:20:54 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id QAA10941; Sat, 21 Jun 1997 16:04:01 +0200 (MET DST) Message-ID: <19970621160401.FP36358@uriah.heep.sax.de> Date: Sat, 21 Jun 1997 16:04:01 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: pci_map_mem failed... References: <199706201726.MAA15908@friley01.res.iastate.edu> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706201726.MAA15908@friley01.res.iastate.edu>; from Chris Csanady on Jun 20, 1997 12:26:11 -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Chris Csanady wrote: > There seems to be some comment in German in pci.c about > this case, so I was wondering if something is broken.. /* ACHTUNG: Ist der Code richtig, wenn eine PCI-PCI-Bridge fuer * die PCI-Slots verwendet wird, aber die Onboard-Devices direkt * an der CPU-PCI-Bridge haengen (Siehe Compaq Prolinea Problem) ??? */ /* * Attention: is this code indeed correct when using a PCI-to-PCI * bridge for the PCI slots, where the onboard devices connect * directly to the CPU-PCI bridge (see Compaq Prolinea problem)? */ Somebody feel free to commit the translation. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jun 21 08:49:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA05598 for hackers-outgoing; Sat, 21 Jun 1997 08:49:53 -0700 (PDT) Received: from iafnl.es.iaf.nl (root@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA05580 for ; Sat, 21 Jun 1997 08:49:49 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA10015 (5.67b/IDA-1.5 for hackers@FreeBSD.ORG); Sat, 21 Jun 1997 17:22:36 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id RAA00356; Sat, 21 Jun 1997 17:09:24 +0200 (MET DST) From: Wilko Bulte Message-Id: <199706211509.RAA00356@yedi.iaf.nl> Subject: Re: Announcement: New DPT RAID Controller Driver Available To: gjennejohn@frt.dec.com Date: Sat, 21 Jun 1997 17:09:24 +0200 (MET DST) Cc: hackers@FreeBSD.ORG In-Reply-To: <9706201528.AA25614@cssmuc.frt.dec.com> from "garyj@frt.dec.com" at Jun 20, 97 05:28:59 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As garyj@frt.dec.com wrote... > jkh@time.cdrom.com writes: > > Unless, of course, they had something like the AMES wind tunnel > > providing forced airflow past the drives, then I suppose the plastic > > sled construction wouldn't really matter much, would it? :-) > > > > basically, the Storage Works thingies from DEC _do_ have a wind tunnel :) > I have one of these things at home and it has 2 large fans on the back > pushing (or pulling ?) air. Pulls air from front to rear thru the SBB (storage building block) > I've seen some pretty big RAID arrays here at DEC, all made using > plastic enclosures. They work good (although I have to agree with Metalised plastic, to keep within FCC req's > an earlier poster that those flimsy flex connections are pretty cheesy > and *so* easy to ruin). You are not supposed to get your hands on them... Newer SBBs have 'warranty void' stickers on them to keep people from opening them. If you want a really fragile flex check out a TZ8[67] DLT tape drive in an SBB. But kidding aside: you need to be careful with the flexes, but apart from that it works just fine. Wilko (aka wilko@storage.jgo.dec.com ;-) _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-hackers Sat Jun 21 10:18:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA10195 for hackers-outgoing; Sat, 21 Jun 1997 10:18:04 -0700 (PDT) Received: from super-g.inch.com (super-g.com [204.178.32.161]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA10190 for ; Sat, 21 Jun 1997 10:18:02 -0700 (PDT) Received: from localhost (spork@localhost) by super-g.inch.com (8.8.5/8.8.5) with SMTP id NAA10411; Sat, 21 Jun 1997 13:30:52 GMT Date: Sat, 21 Jun 1997 13:30:52 +0000 (GMT) From: spork X-Sender: spork@super-g.inch.com To: Jaye Mathisen cc: hackers@FreeBSD.ORG Subject: Re: OpenBSD 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 I actually have NetBSD on a MacIIX at home, and I was considering throwing OpenBSD on it for fun next time I have some spare time... Once it's up, anyone who's curious can get an account; it's on a DDS line tho, so it might be a bit painful if I'm browsing or whatnot... Charles On Thu, 19 Jun 1997, Jaye Mathisen wrote: > > > Sheesh, how many people do they have working on that thing? I was reading > the 2.1 release announcement, and shaking my head... > > Of course, the "20 or more security fixes", w/o mentioning subsystems was > amusing. (Not doubting that they were fixed, only the tossing around of > unsubstantiated numbers). > > Anybody running FreeBSD given it a shot just to see? I have been > thinking about it to see if it fixes my UFS problems that are seemingly > unrepairable. > From owner-freebsd-hackers Sat Jun 21 10:19:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA10287 for hackers-outgoing; Sat, 21 Jun 1997 10:19:50 -0700 (PDT) Received: from super-g.inch.com (super-g.com [204.178.32.161]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA10282 for ; Sat, 21 Jun 1997 10:19:47 -0700 (PDT) Received: from localhost (spork@localhost) by super-g.inch.com (8.8.5/8.8.5) with SMTP id NAA10420; Sat, 21 Jun 1997 13:32:37 GMT Date: Sat, 21 Jun 1997 13:32:37 +0000 (GMT) From: spork X-Sender: spork@super-g.inch.com To: Ben Black cc: Jaye Mathisen , hackers@FreeBSD.ORG Subject: Re: OpenBSD 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 I was trolling comp.unix.security a few times, and his attitude kind of frightened me. I appreciate that he's a hard worker, but everything turned personal on that group... Charles On Thu, 19 Jun 1997, Ben Black wrote: > the security fixes are real. unfortunately, few people can deal with > theo deraadt, so step lightly on the openbsd lists. > > On Thu, 19 Jun 1997, Jaye Mathisen wrote: > > > > > > > Sheesh, how many people do they have working on that thing? I was reading > > the 2.1 release announcement, and shaking my head... > > > > Of course, the "20 or more security fixes", w/o mentioning subsystems was > > amusing. (Not doubting that they were fixed, only the tossing around of > > unsubstantiated numbers). > > > > Anybody running FreeBSD given it a shot just to see? I have been > > thinking about it to see if it fixes my UFS problems that are seemingly > > unrepairable. > > > From owner-freebsd-hackers Sat Jun 21 10:42:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA11174 for hackers-outgoing; Sat, 21 Jun 1997 10:42:04 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA11169 for ; Sat, 21 Jun 1997 10:42:00 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA14325 (5.67b/IDA-1.5 for hackers@FreeBSD.ORG); Sat, 21 Jun 1997 19:42:06 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id TAA02164; Sat, 21 Jun 1997 19:29:31 +0200 (MET DST) From: Wilko Bulte Message-Id: <199706211729.TAA02164@yedi.iaf.nl> Subject: Re: Announcement: New DPT RAID Controller Driver Available To: nadav@cs.technion.ac.il (Nadav Eiron) Date: Sat, 21 Jun 1997 19:29:30 +0200 (MET DST) Cc: gjennejohn@frt.dec.com, hackers@FreeBSD.ORG In-Reply-To: from "Nadav Eiron" at Jun 21, 97 12:15:25 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Nadav Eiron wrote... > On Fri, 20 Jun 1997 garyj@frt.dec.com wrote: > > jkh@time.cdrom.com writes: > > > providing forced airflow past the drives, then I suppose the plastic > > > sled construction wouldn't really matter much, would it? :-) > My previous employer had a pretty big OpenVMS cluster with giant SW800 > racks (rough estimate - about 500 drives, total most 7200rpm). When > filling up one of these racks, DEC recommends that you add a shelf of fans Right, the 'fan tray' as it is called. > at the bottom to force some more air into it, but other than that, heat > doesn't seem to be a problem. These plastic canisters seem to have great > air flow. Just place your hand over the warm air outlet of one of these > SW800s and feel how much heat it evacuates from the drives. It's interesting to note that when the 7200 rpm drives were introduced also new fan models were introduced to be put on the back of the storage shelves. The idea is that one fan is allowed to fail without causing a disk meltdown. The older fans could not keep up in such a case so the newer dual speed fans are needed. In case a fan fails, the remaining fan switches to double speed. Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-hackers Sat Jun 21 10:49:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA11501 for hackers-outgoing; Sat, 21 Jun 1997 10:49:07 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA11464 for ; Sat, 21 Jun 1997 10:48:55 -0700 (PDT) Received: (qmail 11650 invoked by uid 1000); 21 Jun 1997 17:49:01 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199706200929.CAA12213@implode.root.com> Date: Sat, 21 Jun 1997 10:49:01 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: dg@root.com Subject: Re: Announcement: New DPT RAID Controller Driver Available Cc: Brian Tao , FREEBSD-SCSI , FREEBSD-HACKERS , "Justin T. Gibbs" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi David Greenman; On 20-Jun-97 you wrote: ... > Before everyone throws out their metal drive enclosures in favor of > plastic ones, let me say something about my experiance. Wcarchive used to > lose a couple of drives a month back when they were housed in plastic > enclosures. I noticed that the drives in that box ran hot, and I finally > got > tired of flying down to the Bay area so often to deal with it and > convinced > WC to replace the cabinet/enclosures with an all-steel one made by > Kingston. > This was about a year ago. Result: The drives run almost cold now and we > haven't had a single failure in that array since. All of our drives have > fairly well balanced spindles and don't vibrate all that much, and I've > never > seen a reported seek failure or noticed any slowness. In my opinion, the > all- > metal enclosure is a significant factor in the cooling of the drives and > these > days I wouldn't consider anything else. > YMMV. Before this turns into a religious war :-) IMHO; there is nothing inherently bad in platic carriers nor in metal carriers. Either technology can be either well made or poorly made. If David would have examined both the plastic carriers that failed and the metal carriers that are so successful, he would have discovered that one is allowing better air flow than the other. Should David had taped shut all the air passages in the metal carrier, it would have overheater just as nicely, unless the thing was imeresed in coold water. I brought up the platic carriers more as an anecdore to illustrate that platic is not necessarily bad, nor metal necessarily good. Good airflow, vibration isolation, quality drives, and just as important carriers rack and cabinet cooling are just as important. Simon From owner-freebsd-hackers Sat Jun 21 10:49:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA11502 for hackers-outgoing; Sat, 21 Jun 1997 10:49:08 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA11466 for ; Sat, 21 Jun 1997 10:48:56 -0700 (PDT) Received: (qmail 11652 invoked by uid 1000); 21 Jun 1997 17:49:01 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <27545.866803027@time.cdrom.com> Date: Sat, 21 Jun 1997 10:49:01 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: "Jordan K. Hubbard" Subject: Re: Announcement: New DPT RAID Controller Driver Available Cc: Brian Tao , FREEBSD-SCSI , FREEBSD-HACKERS , "Justin T. Gibbs" , dg@root.com Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi "Jordan K. Hubbard"; On 20-Jun-97 you wrote: ... > I would also be suspicious of the cooling properties of a plastic > drive enclosure (it seems like packing it in a mini-Igloo ice chest > would be no worse to me ;-), but given a much different racking > scenario, say 80 drives in a single free-standing rack, I'm more than > willing to believe that vibration becomes a significant problem > requiring creative solutions. If it were my fingers signing the P.O. > on a true drive-array-from-hell, I'd probably favor the vendor > providing the best combination of all-metal construction, air-flow, > power supply quality and vibration isolation. We needed to put 3,000 drives in an array. We ended up with 200 drives per cabinet and 15 cabinets per system. Made finding the CPU array a bit difficult :-) We snickered at the DEC solution and jibed about it a lot worse than you do :-). The DEc engineers were cool about it and kept on saying ``just try it, will you?'' ``Sure we said'' this thing will be out of here in no time. No way these things will ever work. We put a recording thermometer in every disk, in every tray, in every rack. We put the rack in an oven and cooked at 110 F for a week. Ambient + 10 said the spec, ambient + 10 it was. In all spots. All the time. Ambient + 12 with one fan off. The spec said do not phisically remove a fan for more than 2 minutes. In 5 minutes the drives overheated. Then we pulled our heaviest gun. No way a plastic carrier in plastic rack will pass EMI/RFI. Guess again. I think what happened there was that these kids at DEC, knowing nothing about system engineering, and absolutely nothing about mechanical design nor disk drives just got lucky. > Unless, of course, they had something like the AMES wind tunnel > providing forced airflow past the drives, then I suppose the plastic > sled construction wouldn't really matter much, would it? :-) Actually, of the 5-6 designs weevaluated here, the DEC solution is also the quitest. Just to trigger another round of heated and energetic discussion: Our hardware engineers computed, with great precision, that to run 6 drives, one needs at least 300W. DEC engineers obviusly skipped school that day as their P/S are only 150W each. ~No way will you be able to ever hot plug a P/S or replace a disk. Sure. I took a rack, put one power supply and SEVEN (not 6) drives in it and powered it up, booted FreeBSD, and formatted all the drives at the same time. Then I started random I/O with read-write cycle on all drives. 256 instances in all. Worked fine. Oh, BTW, the in-house design, using TWO 300W power supplies crashes EVERY TIME you unplug or plug a disk. As I said, DEC has no clue how to build a disk system. They make lousy CPU's too. Simon From owner-freebsd-hackers Sat Jun 21 10:49:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA11535 for hackers-outgoing; Sat, 21 Jun 1997 10:49:13 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA11483 for ; Sat, 21 Jun 1997 10:49:03 -0700 (PDT) Received: (qmail 11673 invoked by uid 1000); 21 Jun 1997 17:49:01 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 21 Jun 1997 10:49:01 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: FreeBSD-Hackers@FreeBSD.ORG, FreeBSD-SCSI@FreeBSD.ORG Subject: Mystery of The missing I/O - Help Solicited Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Y'all This message is for all those who are still speaking to me after daring to suggest that plasic (yuck!) disk carriers can be as good as steel ones (imagine that!) :-)) No, really, there is something serious we could be helped with: With the new DPT driver, we were plagued with occasional getting stuck. what happens is that after few minutes of operation, or after few days of operation, under varying loads, any process which goes to a certain disk would just block indefinitely. We verified that we do not miss processing any interrupt. We fixed a minor hole that causes biodone to get confused every million I/O's or so. We traced individual commands to make sure that we do not have any SCSI command which we do not return to sd.c To make these verifications we built all kinds of strange and interesting tools. Nothing helps. Oh, to confuse everyone, we can reproduce this problem only on Pentium Pros. Pentium-100's simply will not fail. We braught the load on test systems all the way up to about 120. Nothing. Next hint set; We can reliably reproduce the problem only on sendero, only when doing make release. So we though. Today we decided to try something else. We quited down ALL networking activity on the system, including disconnecting PPP. We managed to build make release flawlessly. Several times. Connect PPP and SCSI command completions seem to disappear somewhere between sd.c and the driver or higher. Disconnect PPP and all is well. Before someone tells me to shut down the software interrupts, I will be quickly to point out that I can #ifdef it out and still get the same problem. Exactly. Let me point out that the DPT can complete a SCSI READ/WRITE command in about 250 microseconds (on a cache hit). We measured, occasionally, interruptscoming as fast as 4 microseconds apart (like two consecutive cache hits). We are at our wits end to find an explanation for this. Any suggestion will be greatly appreciated. Thamx, Simon Quiz: How many SCSI commands does it take to run make release? Answer: 300,000 reads and 2.1 million writes. From owner-freebsd-hackers Sat Jun 21 11:44:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA13542 for hackers-outgoing; Sat, 21 Jun 1997 11:44:30 -0700 (PDT) Received: from online.no (pilt.online.no [193.212.1.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA13537 for ; Sat, 21 Jun 1997 11:44:24 -0700 (PDT) Received: from x (bergen1356.online.no [148.122.210.246]) by online.no (8.7.6/8.7.3) with ESMTP id UAA26600 for ; Sat, 21 Jun 1997 20:43:40 +0200 (MET DST) Message-Id: <199706211843.UAA26600@online.no> From: "Tommy Midttveit" To: Subject: Update your FreeBSD directory! Date: Sat, 21 Jun 1997 20:40:13 +0200 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 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 Hi, my name is Tommy Midttveit. I've currently downloaded FreeBSD, and was downloading XFree86. I see that you have not updated the one under the FreeBSD direcotory to the newst one, XFree 3.2. In the FreeBSD directory there was version 2.2 I think, or something like that. One more thing, is it possible to get the whole FreeBSD on a CD? With the software that you have for it? I still have a modem connection, and would earn on buying on of those... instead of downloading it all via the ftp... TM From owner-freebsd-hackers Sat Jun 21 12:17:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA14870 for hackers-outgoing; Sat, 21 Jun 1997 12:17:42 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA14861 for ; Sat, 21 Jun 1997 12:17:38 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id MAA21972; Sat, 21 Jun 1997 12:17:25 -0700 (PDT) To: "Tommy Midttveit" cc: hackers@FreeBSD.ORG Subject: Re: Update your FreeBSD directory! In-reply-to: Your message of "Sat, 21 Jun 1997 20:40:13 +0200." <199706211843.UAA26600@online.no> Date: Sat, 21 Jun 1997 12:17:25 -0700 Message-ID: <21967.866920645@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hi, my name is Tommy Midttveit. I've currently downloaded FreeBSD, and was > downloading XFree86. I see that you have not updated the one under the > FreeBSD direcotory to the newst one, XFree 3.2. In the FreeBSD directory Some of the previous releases of FreeBSD _expect_ to see XFree86 3.2. It would cause them some distress if I suddenly changed it. If you want 2.2 or 3.0 releases with XFree86 3.3 then you should investigate /pub/FreeBSD/*-970618-* on ftp.freebsd.org. > One more thing, is it possible to get the whole FreeBSD on a CD? Yep, just visit http://www.cdrom.com.. Jordan From owner-freebsd-hackers Sat Jun 21 13:12:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA17048 for hackers-outgoing; Sat, 21 Jun 1997 13:12:43 -0700 (PDT) Received: from radford.i-plus.net (root@Radford.i-Plus.net [206.99.237.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA17041 for ; Sat, 21 Jun 1997 13:12:40 -0700 (PDT) Received: from abyss.i-Plus.net (pitlord@Abyss.i-Plus.net [206.99.237.44]) by radford.i-plus.net (8.8.5/8.8.5) with SMTP id QAA00968; Sat, 21 Jun 1997 16:10:58 -0400 (EDT) Message-Id: <199706212010.QAA00968@radford.i-plus.net> X-Mailer: Microsoft Outlook Express 4.71.0544.0 From: "Troy Settle" To: "Mike Tancsa" , "Jordan K. Hubbard" Cc: Subject: Re: make world error in RELENG_2_2 Date: Sat, 21 Jun 1997 16:10:31 -0400 X-Priority: 3 X-MSMail-Priority: Normal MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-MimeOLE: Produced By Microsoft MimeOLE Engine V4.71.0544.0 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: Jordan K. Hubbard >I think the real problem here is that some folks are simply unclear on >the amount of "expertise" required to use /usr/src as an effective >upgrade tool. I would hardly call myself an expert. I tried to make world several dozen times a few weeks ago, and finally reached the point of giving up. I had posted -questions, and asked on IRC. In fact, I talked to you a bit about it, but still no go. >You ask why we don't document the world target - but we do! >/usr/src/Makefile is the documentation for the world target, and >before you start laughing and figuring 'ol Jordan is copping-out here, >let me just explain that for anything which requires building from >sources, we *definitely assume* a very comfortable degree of knowledge >in how to analyze Makefiles and see exactly what they are doing, up to >and including making inferences about where the dependencies are and, >if necessary, taking whatever steps are necessary to ensure that a >failed build is jump-started from the right place. Yes, the handbook even says to check out /usr/src/Makefile before attempting to make world. However, for beginners, it's not quite enough. After reading other posts in this thread, I have gained enough clues to finally succeed in making the world. The only problem I had, was getting /usr/include up to speed. The only way I was able to do this, was by removing it before starting. This had it's problems too. There were a few instances where I had to backtrack, and make a few directories by hand. I don't remember all of them right off, but they included: /usr/include/arpa /usr/include/g++ (and a few under that) /usr/include/readline /usr/include/rpc /usr/include/rpcsvc /usr/include/ss It wasn't anything major to deal with... just a pain 'cause I had to keep starting over. >The world target *does* generally work, don't get me wrong, but it's >also exceedingly easy to get to a point where the delta between where >you are and where /usr/src would like to take you has diverged too far >to allow "world" to actually work. In such cases, you need to know >how to shepard the process through by hand and the Makefile truly says >it all where that's concerned. I can't imagine any more effective or >concise body of documentation than the build system itself to someone >who knows what they're doing, and someone who doesn't know what >they're doing really shouldn't be using the world target - they should >be hanging back at the major release points and upgrading via binaries >only. What about those of us who want to learn about this stuff. It's not difficult once one gets a few clues. But, those clues are a little less than obvious to many of us. >We're proud of our integrated build system and, given that it's also >often the quickest way of getting a fix into a user's tree, we do >sometimes tend to recommend it as a solution in situations where we >really shouldn't. Building from source is NOT a generic, >targeted-at-the-end-user kinda mechanism and I'm sorry if we ever lent >that impression. It's not. It's for software engineering types to >use, those who are more than comfortable with the idea of reading >Makefiles and figuring it out, and in that sense I'd say it's probably >as documented as it's ever going to be. FreeBSD's integrated build system is something to be proud of. I'm sure it took years of work to develop it, and I'm sure it will continue to grow. The problem is the learning curve. Whereas those persons that have been with FreeBSD since the beginning, this is all child's play, there are even more of us that have only been with FreeBSD for a short time, and need a little help now and then. Someday, when time permits, and my coding experience has grown, I hope to become an active contributer to the FreeBSD project, but there are many things that must be learned first, and it's not an easy road when honest questions are given sarcastic or very short replies. Calling us stupid or lazy doens't help anything. Sure, I'll bet that there's people out there that would rather have everything handed to them on a silver platter. Me? I want to learn, and sometime, I'm going to need some help. A qualified answer to an honest question is the best way to help someone in my position. Sarcasm won't stop me from asking, it just pisses people off. >This is also hardly the "elitist" stance some might see it as - it's >just being honest about how this process works and hardly unknown in >this industry. If you walked into IBM tomorrow as an engineer, for >example, and were tasked with porting some large, obscure product of >theirs from AIX to another UNIX variant, do you think you'd find a >source tree with a carefully documented build system, all easily >understandable in a ten minute study? Ha Ha. No. What you'd find >instead is almost certainly something which was completely opaque to >the average joe and aimed strictly at those who know how to take a >build system apart in its entirety, say "aha, so THAT is what you >idiots had in mind", and then adapt it to the new target system (or, >as I've frequently done in such situations, do it over since the >original designers had all the pan-UNIX expertise of a team of Visual >Basic programmers and did it wrong for anything _but_ AIX). In some ways, I do see an "elitist" stance, but it's not one of total seperation. The tools and information is there for everyone to see and study. With time, anyone could learn the details of the FreeBSD build system. The problem, is getting over the first hurdle of the learning curve. Today, I finally got RELENG_2_2 to build, and a few minutes later, I used my newly found knowledge to help someone else get 3.0 to build. >That's just the nature of the beast, and if anything I'd say that >FreeBSD has one of the _easiest_ build systems to understand. >You really have it easy, so quit whinging and start reading the >Makefiles in the future, OK? :-) Yes, now that I've got a few clues, it is pretty easy stuff. Like I said above, the first hurdle of the learning curve is the hardest. Well, I've gone on enough about this. I gotta get back to upgrading and cleaning my box. It's turning into a fun ride :) -- Troy Settle Network Administrator, iPlus Internet Services http://www.i-Plus.net From owner-freebsd-hackers Sat Jun 21 13:18:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA17371 for hackers-outgoing; Sat, 21 Jun 1997 13:18:59 -0700 (PDT) Received: from peedub.gj.org (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA17339; Sat, 21 Jun 1997 13:18:48 -0700 (PDT) Received: from peedub.gj.org (localhost [127.0.0.1]) by peedub.gj.org (8.8.5/8.6.9) with ESMTP id WAA07125; Sat, 21 Jun 1997 22:18:33 GMT Message-Id: <199706212218.WAA07125@peedub.gj.org> X-Mailer: exmh version 2.0gamma 1/27/96 To: freebsd-hackers@freefall.FreeBSD.org Cc: FreeBSD-SCSI@FreeBSD.ORG Subject: Re: Mystery of The missing I/O - Help Solicited Reply-To: Gary Jennejohn In-reply-to: Your message of "Sat, 21 Jun 1997 10:49:01 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Jun 1997 22:18:32 +0000 From: Gary Jennejohn Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro writes: [snip] >Today we decided to try something else. We quited down ALL networking >activity on the system, including disconnecting PPP. We managed to build >make release flawlessly. Several times. Connect PPP and SCSI command >completions seem to disappear somewhere between sd.c and the driver or >higher. Disconnect PPP and all is well. > which PPP ? Kernel or user-land ? Seems like this should be important. --- Gary Jennejohn Home - Gary.Jennejohn@munich.netsurf.de Work - gjennejohn@frt.dec.com From owner-freebsd-hackers Sat Jun 21 14:08:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA19634 for hackers-outgoing; Sat, 21 Jun 1997 14:08:02 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA19604 for ; Sat, 21 Jun 1997 14:07:57 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wfXL5-0005jP-00; Sat, 21 Jun 1997 14:04:55 -0700 Date: Sat, 21 Jun 1997 14:04:54 -0700 (PDT) From: Tom Samplonius To: Tommy Midttveit cc: hackers@freebsd.org Subject: Re: Update your FreeBSD directory! In-Reply-To: <199706211843.UAA26600@online.no> 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, 21 Jun 1997, Tommy Midttveit wrote: > Hi, my name is Tommy Midttveit. I've currently downloaded FreeBSD, and was > downloading XFree86. I see that you have not updated the one under the > FreeBSD direcotory to the newst one, XFree 3.2. In the FreeBSD directory > there was version 2.2 I think, or something like that. > One more thing, is it possible to get the whole FreeBSD on a CD? > With the software that you have for it? I still have a modem connection, > and would earn on buying on of those... instead of downloading it all via > the ftp... > > TM This does not belong on the freebsd-hackers mailing list. Everyone one ftp.cdrom/ftp.freebsd.org is available on CD. See www.cdrom.com Tom From owner-freebsd-hackers Sat Jun 21 14:23:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA20134 for hackers-outgoing; Sat, 21 Jun 1997 14:23:59 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA20128 for ; Sat, 21 Jun 1997 14:23:56 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id RAA14413; Sat, 21 Jun 1997 17:24:13 -0400 Date: Sat, 21 Jun 1997 17:24:11 -0400 (EDT) From: Ben Black To: "Serge A. Babkin" cc: msanders@aros.net, hudginsj@smtp.dancooks.com, hackers@FreeBSD.ORG Subject: Re: RSA5 Encryption Cracked.. In-Reply-To: <199706210835.OAA00684@hq.icb.chel.su> 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 think you mean differential cryptanalysis which under certain circumstances can reduce the effective keyspace. it is not broadly applicable and is rather constrained. 3DES (triple DES) will be an actual gov't standard shortly. NSA is also releasing a new gov't encryption standard (i forget the name, starts with A...AES?) b3n On Sat, 21 Jun 1997, Serge A. Babkin wrote: > > > > yes, i suspected it was the DES crack effort, and yes it is even cooler. > > this is excellent ammunition for lifting export restrictions (assuming > > the clinton administration doesn't shove kerrey's bill through). > > I have read some short article about cracking of DES. They said that > there exists for about 10 years the possibility to crack DES in > analythincal way (I think with enough amount of enciphered data). > They recommended to use DES three times on the data to get real > security. > > -SB > > > > > On Wed, 18 Jun 1997, Michael K. Sanders wrote: > > > > > In message <11F12637A8E@smtp.dancooks.com>, "Jason Hudgins" writes: > > > > > > > > I just thought some of you might be happy to know that the > > > >Deschall project just successfully cracked an RC5 encrypted message > > > >with a 56 bit key. The really cool thing is that it was one of the > > > >1-2% machines that was running FreeBSD! The majority of the > > > >machines hacking away cpu cylces were running windows and solaris. > > > > They found the key after searching through only 25% of the > > > >keyspace. Even though it was really just a matter of luck, I still > > > >that it was pretty cool. > > > > > > Just to clarify, it was a 56-bit _DES_ encrypted message [1]. > > > > > > ...and I think it's even cooler. > > > > > > [1]: "Strong cryptography makes the world a safer place." > > > > > > From owner-freebsd-hackers Sat Jun 21 15:37:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA23534 for hackers-outgoing; Sat, 21 Jun 1997 15:37:08 -0700 (PDT) Received: from moonpie.w8hd.org (moonpie.w8hd.org [198.252.159.14]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA23529 for ; Sat, 21 Jun 1997 15:37:06 -0700 (PDT) Received: from moonpie.w8hd.org (moonpie.w8hd.org [198.252.159.14]) by moonpie.w8hd.org (8.8.5/8.8.5) with SMTP id SAA25732 for ; Sat, 21 Jun 1997 18:37:04 -0400 (EDT) Date: Sat, 21 Jun 1997 18:37:04 -0400 (EDT) From: Kim Culhan To: hackers@freebsd.org Subject: boot mgr warning - cant find boot.config ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Installed 3.0-970619-SNAP on a new disk, at boot time: F1 . . . DOS F2 . . . BSD Default: F2 Can't find file boot.config Can't find file boot.help Any info on where this is coming from is greatly appreciated. regards kim -- kimc@w8hd.org From owner-freebsd-hackers Sat Jun 21 15:41:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA23818 for hackers-outgoing; Sat, 21 Jun 1997 15:41:22 -0700 (PDT) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA23813 for ; Sat, 21 Jun 1997 15:41:20 -0700 (PDT) Received: from pf1.phil.uni-sb.de (root@pf1.phil.uni-sb.de [134.96.82.11]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA08343 for ; Sat, 21 Jun 1997 15:40:36 -0700 (PDT) Received: from relay1.UU.NET (relay1.UU.NET [192.48.96.5]) by pf1.phil.uni-sb.de (8.8.5/8.8.5/961001chris) with ESMTP id AAA27938 for ; Sun, 22 Jun 1997 00:39:06 +0200 (MET DST) Received: from ngeout01.news.aol.com by relay1.UU.NET with SMTP (peer crosschecked as: ngeout01.news.aol.com [152.163.176.244]) id QQcuyk24998; Sat, 21 Jun 1997 18:40:52 -0400 (EDT) Received: from ladder01.news.aol.com (ladder01.news-fddi.aol.com [172.16.30.168]) by ngeout01.news.aol.com (8.6.12/8.6.12) with ESMTP id SAA09734 for ; Sat, 21 Jun 1997 18:40:53 -0400 Date: Sat, 21 Jun 1997 18:40:53 -0400 To: Message-Id: <19970621224000.SAA24834@ladder01.news.aol.com> Newsgroups: saar.lists.freebsd-hackers From: thekewlguy@aol.com (TheKewlGuy) Organization: AOL http://www.aol.com Subject: READ THIS!!!!!!!!!!!!! Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk A little while back, I was browsing these newsgroups, just like you are now, and came across an article similar to this that said you could make thousands of dollars within weeks with only an initial investment of $5.00! So I thought, "Yeah, right, this must be a scam," but like most of us I was curious, so I kept reading. Anyway, it said that you send $1.00 to each of the 5 names and addresses stated in the article. You then place your own name and address in the bottom of the list at #5, and post the article in at least 200 newsgroups. (There are thousands) No catch, that was it. So after thinking it over, and talking to a few people first, I thought about trying it. I figured what have I got to lose except 5 stamps and $5.00, right? Like most of us I was a little skeptical and a little worried about the legal aspects of it all. So I checked it out with my country Post Office, and others had with US Post (1-800-725-2161) and they confirmed that it is indeed legal! Then I invested the measly $5.00............. Well GUESS WHAT!!... with in 7 days, I started getting money in the mail! I was shocked! I still figured it would end soon, and didn't give it another thought. But the money just kept coming in. In my first week, I made about $20.00 to $30.00 dollars. By the end of the second week I had made a total of over $1,000.00!!!!!! In the third week I had over $10,000.00 and it's still growing. This is now my fourth week and I have made a total of just over $42,000.00 and it's still coming in ....... It's certainly worth $5.00, and 5 stamps, I spent more than that on the lottery!! Let me tell you how this works and most importantly, Why it works....also, make sure you print a copy of this article NOW, so you can get the information off of it as you need it. The process is very simple and consists of 3 easy steps: STEP 1: Get 5 separate pieces of paper and write the following on each piece of paper "PLEASE PUT ME ON YOUR MAILING LIST." Now get 5 $1.00 bills and place ONE inside EACH of the 5 pieces of paper so the bill will not be seen through the envelope to prevent thievery. Next, place one paper in each of the 5 envelopes and seal them. You should now have 5 sealed envelopes, each with a piece of paper stating the above phrase and a $1.00 bill. What you are doing is creating a service by this. THIS IS PERFECTLY LEGAL! Mail the 5 envelopes to the following addresses: (MAKE SURE YOU MAIL $1 cash to EACH of these people or it WILL NOT WORK.....If you follow these directions carefully......you willl recieve LOTS of money....if you don't follow the directions...you will no recieve jack. YOU CAN USE A FAKE NAME FOR PRIVACY AND SECURITY REASONS....AND/OR RENT A P.O BOX AT YOUR POST OFFICE OR A MAIL SERVICE CENTER IF YOU DO NOT WANT ALL THIS CASH COMING TO YOUR HOUSE......BUT IT IS PERFECTLY FINE TO USE YOUR HOME ADDRESS.....MOST DO. #1 Tom, BDB. Via Damiano Chiesa 10 00010 Marcellina (Roma) Italy #2 H. J. Sung 1839 Keeaumoku St. Honolulu, HI 96822-3004 #3 C.Mas 1130 Greensboro Lane Box 73 Sarasota, FL 34234 #4 RED MOSQUITO P. O. Box 891329-277 Suite #180- 277 2323 Clear Lake City Blvd Houston, Texas 77289-1329 #5 Kyle Everett 2215 Topsfield Rd. South Bend, IN 46614 STEP 2: Now take the #1 name off the list that you see above, move the other names up (5 becomes 4, 4 becomes 3, etc...) and add YOUR Name as number 5 on the list. STEP 3: Change anything you need to, but try to keep this article as close to original as possible. Now, post your amended article to at least 200 newsgroups. (I think there is close to 25,000 groups) All you need is 200, but remember, the more you post, the more money you make! Don't know HOW to post in the newsgroups? Well do exactly the following: (OR YOU MAY BE ABLE TO USE THE "COPY AND PASTE" METHOD.) FOR NETSCAPE USERS: 1) Click on any newsgroup, like normal. Then click on "To News", which is in the top left corner of the newsgroup page. This will bring up a message box. 2) Fill in the SUBJECT with a flashy title, like the one I used, something to catch the eye!!! 3) Now go to the message part of the box and retype this letter exactly as it is here, with exception of your few changes. (remember to add your name to number 5 and move the rest up) 4) When your're done typing in the WHOLE letter, click on 'FILE' above the send button. Then, 'SAVE AS..' DO NOT SEND YOUR ARTICLE UNTIL YOU SAVE IT. (so you don't have to type this 200 times) 5) Now that you have saved the letter, go ahead and send your first copy! (click the 'SEND' button in the top left corner) 6) This is where you post all 200! OK, go to ANY newsgroup article and click the 'TO NEWS' button again. Type in your flashy subject in the 'SUBJECT BOX', then go to the message and place your cursor here. Now click on 'ATTACHMENT' which is right below the 'SUBJECT BOX'. Click on attach file then find your letter wherever you saved it. Click once on your file then click 'OPEN' then click 'OK'. If you did this right, you should see your filename in the 'ATTACHMENT BOX' and it will be shaded. NOW POST AWAY! FOR INTERNET EXPLORER: It's just as easy, holding down the left mouse button, highlight this entire article, then press the 'CTRL' key and 'C' key at the same time to copy this article. Then print the article for your records to have the names of those you will be sending $1.00 to. Go to the newsgroups and press 'POST AN ARTICLE' type in your flashy subject and click the large window below. Press 'CTRL' and 'V' and the article will appear in the message window. **BE SURE TO MAKE YOUR ADDRESS CHANGES TO THE 5 NAMES.** Now re-highlight the article and re-copy it so you have the changes.... then all you have to do for each newsgroup is 'CTRL' and 'V' and press 'POST'. It's that easy!! THAT'S IT! All you have to do is jump to different newsgroups and post away, after you get the hang of it, it will take about 30 seconds for each newsgroup! **REMEMBER, THE MORE NEWSGROUPS YOU POST IN, THE MORE MONEY YOU WILL MAKE!! BUT YOU HAVE TO POST A MINIMUM OF 200** **If these instructions are too complex to follow, try Forte's "Free Agent." It is freeware for noncommercial use. To download it, simply use a search utility and type "Forte Free Agent". You should be able to find it.** That's it! You will begin receiving money from around the world within days! You may eventually want to rent a P.O. Box due to the large amount of mail you receive. If you wish to stay anonymous, you can invent a name to use, as long as the postman will deliver it. **JUST MAKE SURE ALL THE ADDRESSES ARE CORRECT.** --- Now the WHY part: Out of 200 postings, say I receive only 5 replies (a very low example). So then I made $5.00 with my name at #5 on the letter. Now, each of the 5 persons who just sent me $1.00 make the MINIMUM 200 postings, each with my name at #4 and only 5 persons respond to each of the original 5, that is another $25.00 for me, now those 25 each make 200 MINIMUM posts with my name at #3 and only 5 replies each, I will bring in an additional $125.00! Now, those 125 persons turn around and post the MINIMUM 200 with my name at #2 and only receive 5 replies each, I will make an additional $626.00! OK, now here is the fun part, each of those 625 persons post a MINIMUM 200 letters with my name at #1 and they each only receive 5 replies, that just made me $3,125.00!!! With a original investment of only $5.00! AMAZING! And as I said 5 responses is actually VERY LOW! Average is probable 20 to 30! So lets put those figures at just 15 responses per person. Here is what you will make: at #5 $15.00 at #4 $225.00 at #3 $3,375.00 at #2 $50,625.00 at #1 $759,375.00 When your name is no longer on the list, you just take the latest posting in the newsgroups, and send out another $5.00 to names on the list, putting your name at number 5 again. And start posting again. The thing to remember is that thousands of people all over the world are joining the Internet and reading these articles everyday, JUST LIKE YOU are now!! So can you afford $5.00 and see if it really works?? I think so... People have said, "what if the plan is played out and no one sends you the money? So what! What are the chances of that happening when there are tons of new honest users and new honest people who are joining the Internet and newsgroups everyday and are willing to give it a try? Estimates are at 20,000 to 50,000 new users, every day, with thousands of those joining the actual Internet. Remember, play FAIRLY and HONESTLY and this will work. You just have to be honest. Make sure you print this article out RIGHT NOW, also. Try to keep a list of everyone that sends you money and always keep an eye on the newsgroups to make sure everyone is playing fairly. Remember, HONESTY IS THE BEST POLICY. You don't need to cheat the basic idea to make the money!! GOOD LUCK to all and please play fairly and reap the huge rewards from this, which is tons of extra CASH. **By the way, if you try to deceive people by posting the messages with your name in the list and not sending the money to the rest of the people already on the list, you will NOT get as much. Someone I talked to knew someone who did that and he only made about $150.00, and that's after seven or eight weeks! Then he sent the 5 $1.00 bills, people added him to their lists, and in 4-5 weeks he had over $10k. This is the fairest and most honest way I have ever seen to share the wealth of the world without costing anything but our time!!! Don't listen to the people that don't trust it and continue to say it's illegal and don't work... They are just too skeptical. You also may want to buy mailing and e-mail lists for future dollars. From owner-freebsd-hackers Sat Jun 21 16:08:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA24872 for hackers-outgoing; Sat, 21 Jun 1997 16:08:40 -0700 (PDT) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA24862 for ; Sat, 21 Jun 1997 16:08:33 -0700 (PDT) Received: from localhost (taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id TAA20262; Sat, 21 Jun 1997 19:07:52 -0400 (EDT) Date: Sat, 21 Jun 1997 19:07:52 -0400 (EDT) From: Brian Tao To: Mark Mayo cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD cracks DES ! In-Reply-To: <19970620143541.17175@vinyl.quickweb.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Jun 1997, Mark Mayo wrote: > > Just thought I'd mention that the RSA DES challenge is over, and > that the winning client was a DESCHALL machine, **** running on > FreeBSD *** !! Neato! Now let's see if a FreeBSD machine will claim the prize for the 56-bit RC5 challenge too. :) -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't" From owner-freebsd-hackers Sat Jun 21 16:11:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA25045 for hackers-outgoing; Sat, 21 Jun 1997 16:11:39 -0700 (PDT) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA25040 for ; Sat, 21 Jun 1997 16:11:35 -0700 (PDT) Received: from localhost (taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id TAA20585; Sat, 21 Jun 1997 19:10:46 -0400 (EDT) Date: Sat, 21 Jun 1997 19:10:46 -0400 (EDT) From: Brian Tao To: Marc Slemko cc: sthaug@nethelp.no, hackers@FreeBSD.ORG Subject: Re: gethostbyname() and fds >255 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, 21 Jun 1997, Marc Slemko wrote: > > Guess I'll have to double check what else was broken when FD_SETSIZE > was increased and make a patch for 2.2 that I can point people to. > My biggest concern in this is that Apache 1.2 will not work with > >~255 fds used for logs without recompiling libc with a larger > FD_SETSIZE. I believe someone just added that very problem to the Apache FAQ. You will need to rebuild libc if your FD_SETSIZE is initially set to 256 to support more than 255 virtualhosts in Apache 1.2. -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't" From owner-freebsd-hackers Sat Jun 21 16:27:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA25689 for hackers-outgoing; Sat, 21 Jun 1997 16:27:39 -0700 (PDT) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA25684 for ; Sat, 21 Jun 1997 16:27:36 -0700 (PDT) Received: from localhost (taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id TAA23264 for ; Sat, 21 Jun 1997 19:27:04 -0400 (EDT) Date: Sat, 21 Jun 1997 19:27:03 -0400 (EDT) From: Brian Tao To: FREEBSD-HACKERS Subject: "ad1848: Problems when clearing interrupt" Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At some point today, while listening to a bunch of MP3 using the mpg123 0.59i player, the sound system on my 2.2-BETA machine at home stopped working (Gravis Ultrasound MAX 512k, not the newer PnP models). The dmesg buffer was filled with: isa_dmastart: channel 1 busy ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff isa_dmastart: channel 1 busy ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff isa_dmastart: channel 1 busy ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff [etc...] Anything sound-related no longer worked (mpg123, xanim, s3mod, catting files to /dev/audio, etc.). In an effort to clear up the problem, I shut down to single user mode. All non-essential processes were apparently killed off, but I could not umount /usr/local (where mpg123 lives), even though fstat didn't show any process holding open a file descriptor on that filesystem. Re-entering multiuser mode didn't solve the sound problem either. I haven't upgraded this machine since last December (in fact it hasn't even been rebooted since early March), so I suppose I should do that anyway, but is this a known problem. If so, has it been fixed in the (presumably) newer sound drivers in 3.0-current? -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't" From owner-freebsd-hackers Sat Jun 21 16:50:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA26706 for hackers-outgoing; Sat, 21 Jun 1997 16:50:47 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA26701 for ; Sat, 21 Jun 1997 16:50:43 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA00334; Sat, 21 Jun 1997 19:50:09 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Sat, 21 Jun 1997 19:50 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id TAA29325; Sat, 21 Jun 1997 19:08:50 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id TAA26826; Sat, 21 Jun 1997 19:17:06 -0400 (EDT) Date: Sat, 21 Jun 1997 19:17:06 -0400 (EDT) From: Thomas David Rivers Message-Id: <199706212317.TAA26826@lakes.water.net> To: ponds!lakes.water.net!rivers, ponds!dyson.iquest.net!toor Subject: "free xxx isn't" problems (was Re: OpenBSD Cc: ponds!FreeBSD.ORG!hackers, ponds!cdsnet.net!mrcpu, ponds!sdf.com!tom Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk John Dyson writes: > > > > > Anybody running FreeBSD given it a shot just to see? I have been > > > > thinking about it to see if it fixes my UFS problems that are seemingly > > > > unrepairable. > > > > > > UFS problem? > > > > He's talking about his "free xxx isn't" race condition errors. > > > I am working on the problem. I know at least a reasonable explaination. > Might have it committed tonight. > > John > John - I'd be delighted to hear about what you've found, and equally thrilled to try out any changes you make... [I'm not coming off as too exurberant, am I??? :-) ] Can you describe your explanation, and possibly, point me somewhere to gather diff's, etc... - Thanks - - Dave Rivers - p.s. I missed your message of last Friday; I've been on vacation... sorry if this seems a little late... From owner-freebsd-hackers Sat Jun 21 17:07:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA27296 for hackers-outgoing; Sat, 21 Jun 1997 17:07:36 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA27288 for ; Sat, 21 Jun 1997 17:07:28 -0700 (PDT) Received: (qmail 2235 invoked by uid 1000); 22 Jun 1997 00:07:34 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199706211729.TAA02164@yedi.iaf.nl> Date: Sat, 21 Jun 1997 17:07:34 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Wilko Bulte Subject: Re: Announcement: New DPT RAID Controller Driver Available Cc: hackers@FreeBSD.ORG, gjennejohn@frt.dec.com, (Nadav Eiron) Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Wilko Bulte; On 21-Jun-97 you wrote: > As Nadav Eiron wrote... > > On Fri, 20 Jun 1997 garyj@frt.dec.com wrote: > > > > jkh@time.cdrom.com writes: > > > > providing forced airflow past the drives, then I suppose the > plastic > > > > sled construction wouldn't really matter much, would it? :-) > > > My previous employer had a pretty big OpenVMS cluster with giant SW800 > > racks (rough estimate - about 500 drives, total most 7200rpm). When > > filling up one of these racks, DEC recommends that you add a shelf of > fans > > Right, the 'fan tray' as it is called. > > > at the bottom to force some more air into it, but other than that, heat > > doesn't seem to be a problem. These plastic canisters seem to have > great > > air flow. Just place your hand over the warm air outlet of one of these > > SW800s and feel how much heat it evacuates from the drives. > > It's interesting to note that when the 7200 rpm drives were introduced > also new fan models were introduced to be put on the back of the storage > shelves. The idea is that one fan is allowed to fail without causing a > disk meltdown. The older fans could not keep up in such a case > so the newer dual speed fans are needed. In case a fan fails, the > remaining fan switches to double speed. Like I said, these hobyists at DEC really do not know the first thing about disk subsystems. Give me a good PC. Grrrrr... :-) Any idea about my network-scsi interaction? Simon From owner-freebsd-hackers Sat Jun 21 17:07:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA27323 for hackers-outgoing; Sat, 21 Jun 1997 17:07:40 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA27291 for ; Sat, 21 Jun 1997 17:07:28 -0700 (PDT) Received: (qmail 2243 invoked by uid 1000); 22 Jun 1997 00:07:34 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199706212218.WAA07125@peedub.gj.org> Date: Sat, 21 Jun 1997 17:07:34 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Gary Jennejohn Subject: Re: Mystery of The missing I/O - Help Solicited Cc: FreeBSD-SCSI@FreeBSD.ORG, freebsd-hackers@freefall.FreeBSD.org Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Gary Jennejohn; On 21-Jun-97 you wrote: > Simon Shapiro writes: > [snip] > >Today we decided to try something else. We quited down ALL networking > >activity on the system, including disconnecting PPP. We managed to > build > >make release flawlessly. Several times. Connect PPP and SCSI command > >completions seem to disappear somewhere between sd.c and the driver or > >higher. Disconnect PPP and all is well. > > > > which PPP ? Kernel or user-land ? Seems like this should be important. Kernel PPP. Source is RELENG_2_2 as of 971619. Existed earlier. We do see an occsional buffer overflow warning on the sio port where PPP is running. Baud rate is either 115,200 (ISDN 64Kb) or 230,400 (128Kb ISDN). One more thing. We get a 1-8 seconds delay in the system every now and then. It manifests itself as a complete freeze that comes suddenly and releases suddenly. It is NOT in the DPT driver. Internal to the driver, we see it as a similar delay in serving software interrupts or in return from scsi_done(). Simon From owner-freebsd-hackers Sat Jun 21 17:07:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA27324 for hackers-outgoing; Sat, 21 Jun 1997 17:07:40 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA27289 for ; Sat, 21 Jun 1997 17:07:28 -0700 (PDT) Received: (qmail 2241 invoked by uid 1000); 22 Jun 1997 00:07:34 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199706211509.RAA00356@yedi.iaf.nl> Date: Sat, 21 Jun 1997 17:07:34 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Wilko Bulte Subject: Re: Announcement: New DPT RAID Controller Driver Available Cc: hackers@FreeBSD.ORG, gjennejohn@frt.dec.com Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Wilko Bulte; On 21-Jun-97 you wrote: ... > > an earlier poster that those flimsy flex connections are pretty cheesy > > and *so* easy to ruin). > > You are not supposed to get your hands on them... Newer SBBs have > 'warranty void' stickers on them to keep people from opening them. > > If you want a really fragile flex check out a TZ8[67] DLT tape drive > in an SBB. But kidding aside: you need to be careful with the flexes, > but apart from that it works just fine. The flex circuit has a reason (other than being the ``cool'' thing to do); they eliminate connectors (improves signal quality), and allow impedience matching. The worst enemy of a SCSI bus is the impedience changes between traces, connectors, external cables, connectors, ribbon cables, backplanes, stub riboon cables, etc. etc. Simon From owner-freebsd-hackers Sat Jun 21 17:08:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA27406 for hackers-outgoing; Sat, 21 Jun 1997 17:08:01 -0700 (PDT) Received: from bsd.fs.bauing.th-darmstadt.de (bsd.fs.bauing.th-darmstadt.de [130.83.63.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA27392 for ; Sat, 21 Jun 1997 17:07:56 -0700 (PDT) Received: from campa.panke.de (anonymous218.ppp.cs.tu-berlin.de [130.149.17.218]) by bsd.fs.bauing.th-darmstadt.de (8.8.5/8.8.5) with ESMTP id CAA14211 for ; Sun, 22 Jun 1997 02:07:51 +0200 (MET DST) Received: (from wosch@localhost) by campa.panke.de (8.8.5/8.6.12) id CAA03560; Sun, 22 Jun 1997 02:04:49 +0200 (MET DST) Date: Sun, 22 Jun 1997 02:04:49 +0200 (MET DST) Message-Id: <199706220004.CAA03560@campa.panke.de> From: Wolfram Schneider To: hackers@freebsd.org Subject: vnconfig and MSDOS FS MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I made a backup of a MSDOS hard disk with dd(1) into a single 425 MB large file. Now I want mount this file with vnconfig and mount_msdos, but it will not work: # vnconfig -u /dev/vn0c # vnconfig /dev/vn0c /usr/tmp/adk # mount_msdos /dev/vn0c /mnt mount_msdos: /dev/vn0c: Invalid argument What's wrong? Does vnconfig not support MSDOS FS? -- Wolfram Schneider http://www.apfel.de/~wosch/ From owner-freebsd-hackers Sat Jun 21 17:13:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA27712 for hackers-outgoing; Sat, 21 Jun 1997 17:13:29 -0700 (PDT) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA27707 for ; Sat, 21 Jun 1997 17:13:26 -0700 (PDT) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.5/8.8.5) with UUCP id SAA19660; Sat, 21 Jun 1997 18:13:22 -0600 (MDT) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id SAA28816; Sat, 21 Jun 1997 18:14:25 -0600 (MDT) Date: Sat, 21 Jun 1997 18:14:25 -0600 (MDT) From: Marc Slemko To: Brian Tao cc: hackers@FreeBSD.ORG Subject: Re: gethostbyname() and fds >255 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, 21 Jun 1997, Brian Tao wrote: > On Sat, 21 Jun 1997, Marc Slemko wrote: > > > > Guess I'll have to double check what else was broken when FD_SETSIZE > > was increased and make a patch for 2.2 that I can point people to. > > My biggest concern in this is that Apache 1.2 will not work with > > >~255 fds used for logs without recompiling libc with a larger > > FD_SETSIZE. > > I believe someone just added that very problem to the Apache FAQ. > You will need to rebuild libc if your FD_SETSIZE is initially set to > 256 to support more than 255 virtualhosts in Apache 1.2. Yes, I know. It isn't just a coincidence that it happened right after I had a chance to track down the problem. To clarify, it is not needed to support more than 255 virtualhosts, but more than 255 file descriptors being used for other things. As long as you don't use Listen directives or seperate logfiles for each virtual host, you will have no problems with fd limits. And for anyone needing to make Apache work when it needs more than 256 file descriptors without having to recompile libc, a patch that has been tossed around for a while is current being tested in preparation for integration. It will use fcntl's F_DUPFD to leave enough low numbered fds free for use by broken library calls. Should be available somewhere sometime somehow. -- Marc Slemko | Apache team member marcs@znep.com | marc@apache.org From owner-freebsd-hackers Sat Jun 21 20:14:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA04501 for hackers-outgoing; Sat, 21 Jun 1997 20:14:49 -0700 (PDT) Received: from INDO-SERV.indosat.net.id (ns2.indosat.net.id [202.155.0.15]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA04493 for ; Sat, 21 Jun 1997 20:14:44 -0700 (PDT) Received: from default (ppp23-bdg.indosat.net.id [202.155.2.151]) by INDO-SERV.indosat.net.id (8.7.3/8.7.3) with ESMTP id KAA25082 for ; Sun, 22 Jun 1997 10:15:30 -0700 (GMT) Message-Id: <199706221715.KAA25082@INDO-SERV.indosat.net.id> From: "Adi" To: Date: Sun, 22 Jun 1997 10:06:07 +0700 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1157 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 unsubscribe boyngirl@iName.com From owner-freebsd-hackers Sat Jun 21 21:01:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA06069 for hackers-outgoing; Sat, 21 Jun 1997 21:01:40 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA06064 for ; Sat, 21 Jun 1997 21:01:32 -0700 (PDT) Received: from awfulhak.demon.co.uk (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id EAA06656; Sun, 22 Jun 1997 04:32:20 +0100 (BST) Message-Id: <199706220332.EAA06656@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: Brian Somers cc: Michael Hancock , "Lenzi, Sergio" , freebsd-hackers@FreeBSD.ORG Subject: Re: pppd & natd problem turnaround.. In-reply-to: Your message of "Tue, 10 Jun 1997 08:12:27 BST." <199706100712.IAA22720@awfulhak.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Jun 1997 04:32:20 +0100 From: Brian Somers Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > On Mon, 9 Jun 1997, Lenzi, Sergio wrote: > > > > > > Better find the real bug. m->m_len < 0 "can't happen". > > > > > > > Shure it can't happen... > > > > > > My site as both slip and ppp configured in kernel > > > > It can't happen if pppfcs ensures it doesn't. Better find the real bug > > before the workaround gets forgotten. > > I've said on the cvs list, this is top of my list now. It turned out to be a VJ compression thing. It's now fixed in 2.2 & -current. -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sat Jun 21 22:29:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA09455 for hackers-outgoing; Sat, 21 Jun 1997 22:29:32 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA09450; Sat, 21 Jun 1997 22:29:10 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id PAA21334; Sun, 22 Jun 1997 15:26:46 +1000 Date: Sun, 22 Jun 1997 15:26:46 +1000 From: Bruce Evans Message-Id: <199706220526.PAA21334@godzilla.zeta.org.au> To: hackers@FreeBSD.ORG, wosch@apfel.de Subject: Re: vnconfig and MSDOS FS Cc: joerg@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I made a backup of a MSDOS hard disk with dd(1) into >a single 425 MB large file. Now I want mount this file with vnconfig >and mount_msdos, but it will not work: > ># vnconfig -u /dev/vn0c ># vnconfig /dev/vn0c /usr/tmp/adk ># mount_msdos /dev/vn0c /mnt >mount_msdos: /dev/vn0c: Invalid argument > >What's wrong? Does vnconfig not support MSDOS FS? Hint: which slices are the DOS partition(s) on? They probably aren't on the whole disk slice. You need to enable slices using `vnconfig ... -s slices ...' (-s is documented only in the usage message and the slices option isn't documented :-(). You shouldn't use /dev/vn0c, which is the the c partition for the first FreeBSD slice, if slices are not enabled. Use the whole disk device /dev/vn0 if that is what you want. /dev/vn0c happens to work because of sloppy checking for aliases in the driver. All minors for (non-raw) vn0* devices are are aliases for each other. For images on floppies, the problem is a litter harder to fix. The MBR overlaps the boot block and the boot block normally ends with 0xAA55 which is interpreted as a signature for a valid partition table. You have to either edit the boot block to destroy the signature or run fdisk to fix the partition table. I found some bugs in mkdosfs when I tested this on a floppy-sized file system: 1) the file system is named msdos, but the program to create it is named mkdosfs. 2) mkdosfs doesn't clear all the directory entries. For a 1200K file system, it writes malloced garbage to the last 7 sectors in the directory. Bruce