From owner-freebsd-current Sun Oct 6 02:16:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA27670 for current-outgoing; Sun, 6 Oct 1996 02:16:46 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA27657; Sun, 6 Oct 1996 02:16:43 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id LAA17077; Sun, 6 Oct 1996 11:00:56 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.7.6/8.7.3) with SMTP id KAA14292; Sun, 6 Oct 1996 10:55:42 +0200 (MET DST) Date: Sun, 6 Oct 1996 10:55:42 +0200 (MET DST) From: Andreas Klemm To: SysAdmin cc: Mark Mayo , freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Java,Netscape, & AccelX In-Reply-To: Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 5 Oct 1996, SysAdmin wrote: > It's starting to sound more and more like it is an AcceleratedX problem! About a month ago I heard from ELSA support - who sell the commercial accelerated X Server for their Winner 2000 PRO/X cards for Solaris 2.5 x86 - that the accelerated X server has problems with Java Console and such .... On Solaris x86 the accelerated X Server has even another major disadvantage ... it doesn't support display postscript ... So you aren't able to start things like the answerbook, pageview and such important things ;-) __ andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Sun Oct 6 04:34:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA10240 for current-outgoing; Sun, 6 Oct 1996 04:34:45 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA10232 for ; Sun, 6 Oct 1996 04:34:39 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id VAA25153; Sun, 6 Oct 1996 21:32:19 +1000 Date: Sun, 6 Oct 1996 21:32:19 +1000 From: Bruce Evans Message-Id: <199610061132.VAA25153@godzilla.zeta.org.au> To: bde@zeta.org.au, michaelh@cet.co.jp Subject: Re: secure level diffs to kern_mib.c, LINT Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >What changes would be necessary to *guarantee* that the system increments >securelevel to 1, *before* any deamons are started? Set the securelevel to 1 in the kernel or use sysctl to set it before starting any daemons :-), e.g. by booting with -s or setting it near the start of /etc/rc. Setting it to 0 in the kernel doesn't do this - then /etc/rc is run in single-user mode at securelevel 0, as it must to write to disks, and daemons are started at securelevel 0 and any disk writing permissions that they gain live across changes to securelevel. >I'm less concerned with putting securelevel=2 in rc, because this is just >locking another deadbolt and isn't as critical as the transition from 0 to >1. Actually, securelevel 1 is normally so insecure that it shouldn't be used. It essentially only provides write protection of /dev/mem and /dev/kmem. The write protection on mounted disks is worthless becauses there are lots of aliases. Even plain BSD has a whole disk partition, and FreeBSD has lots of slices and SCSI control devices. Perhaps this can be worked around by deleting the aliases. Bruce From owner-freebsd-current Sun Oct 6 06:51:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA16694 for current-outgoing; Sun, 6 Oct 1996 06:51:05 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA16689 for ; Sun, 6 Oct 1996 06:51:02 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id PAA15080 for ; Sun, 6 Oct 1996 15:51:01 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA12099 for freebsd-current@FreeBSD.org; Sun, 6 Oct 1996 15:51:00 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id PAA07635 for freebsd-current@FreeBSD.org; Sun, 6 Oct 1996 15:44:22 +0200 (MET DST) From: J Wunsch Message-Id: <199610061344.PAA07635@uriah.heep.sax.de> Subject: Re: secure level diffs to kern_mib.c, LINT To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 6 Oct 1996 15:44:22 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Michael Hancock at "Oct 6, 96 12:41:00 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Michael Hancock wrote: > FreeBSD defaults securelevel to -1, use the following diffs if you prefer > normal bsd operations or want a choice. Man init(8) for details. > + #ifdef SECURE_MODE > + int securelevel; > + #else > int securelevel = -1; > + #endif The question is not to make this simple modification to the sources. However, it has been argued that all the other 4.4BSD descendants use option `INSECURE' for this, so even though the name is somewhat misleading, we should perhaps better pick up this one instead. We still need a backdoor for the X server in order to be able to default to `secure' mode, at least for workstations. -- 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-current Sun Oct 6 06:52:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA16787 for current-outgoing; Sun, 6 Oct 1996 06:52:35 -0700 (PDT) Received: from buffnet4.buffnet.net (root@buffnet4.buffnet.net [205.246.19.13]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA16765; Sun, 6 Oct 1996 06:52:28 -0700 (PDT) Received: from buffnet1.buffnet.net (mmdf@buffnet1.buffnet.net [205.246.19.10]) by buffnet4.buffnet.net (8.6.12/8.6.9) with SMTP id IAA06306; Sun, 6 Oct 1996 08:54:22 GMT Received: from buffnet7.buffnet.net by buffnet1.buffnet.net id aa16814; 6 Oct 96 9:57 EDT Date: Sun, 6 Oct 1996 09:57:52 -0400 (EDT) From: Stephen Hovey To: "Marc G. Fournier" cc: current@freebsd.org, questions@freebsd.org Subject: Re: yp_first error on WWW virtual domains... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ive never been able to get numbers from 2 class C's to work together - I take it it stops working soon as you add a 204.101.125 The problem here is your default route is no longer in the same subnet. On Sat, 5 Oct 1996, Marc G. Fournier wrote: > > Hi... > > I'm attempting to combine IP aliasing and HTTP virtual domains > on my 2.2-Current box, and am failing miserably... > > I've got my ed0 device setup so that it is aliased for: > > 205.150.102.[51-62] > 204.101.125.[200-211] > > As soon as I try to enable a 13th Web server, I start getting: > > yp_first: clnt_call: RPC: Timed out > > And if I go back down to 12, its all fine. > > I'm thinking that there is either a setting I should be > increasing in the kernel, or it has something to do with the IP aliasing... > > Anyone have experience with this? > > Thanks... > > Marc G. Fournier scrappy@ki.net > Systems Administrator @ ki.net scrappy@freebsd.org > > From owner-freebsd-current Sun Oct 6 06:57:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA16978 for current-outgoing; Sun, 6 Oct 1996 06:57:54 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA16962 for ; Sun, 6 Oct 1996 06:57:50 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id PAA15084; Sun, 6 Oct 1996 15:51:05 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA12100; Sun, 6 Oct 1996 15:51:02 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id PAA07672; Sun, 6 Oct 1996 15:49:00 +0200 (MET DST) From: J Wunsch Message-Id: <199610061349.PAA07672@uriah.heep.sax.de> Subject: Re: Java,Netscape, & AccelX To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 6 Oct 1996 15:49:00 +0200 (MET DST) Cc: andrew@why.whine.com, flaq@synwork.com, mark@hi-fi.com, jehamby@lightside.com (Jake Hamby) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Jake Hamby at "Oct 5, 96 09:03:31 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Jake Hamby wrote: > Note: If Java applets fail to display. Type this as root: > cd /usr/X11R6/lib/X11/fonts/misc > /usr/X11R6/bin/mkfontdir > chmod 444 fonts.dir > And then exit and restart your X server. > > I tried that, and lo and behold, it worked! It seems that Netscape needs > particular font aliases that for some reason XFree86 didn't define > properly. mkfontdir doesn't define anything new unless someone has installed new fonts before. In the latter case however, the someone who has been installing them is also responsible for running mkfontdir afterwards. Aliases are kept in fonts.alias anyway, and are not affected by mkfontdir at all. All of this is kinda moot for people running font servers. (You gotta reload the fontserver after installing the fonts.) -- 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-current Sun Oct 6 07:35:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA21741 for current-outgoing; Sun, 6 Oct 1996 07:35:59 -0700 (PDT) Received: from synwork.com (root@synwork.com [199.3.234.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA21720; Sun, 6 Oct 1996 07:35:51 -0700 (PDT) Received: from localhost (flaq@localhost) by synwork.com (8.7.5/8.6.12) with SMTP id JAA01771; Sun, 6 Oct 1996 09:35:09 -0500 (CDT) Date: Sun, 6 Oct 1996 09:35:09 -0500 (CDT) From: SysAdmin To: Stephen Hovey cc: "Marc G. Fournier" , current@FreeBSD.org, questions@FreeBSD.org Subject: Re: yp_first error on WWW virtual domains... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I had a similar problem. I was trying to add a second subnet from a different network to ed0. My problem was routing...couldn't get it to work no matter what I tried. I ended up having to add ed1 to my system and assign one subnet per interface and all was well. Mike On Sun, 6 Oct 1996, Stephen Hovey wrote: --> -->Ive never been able to get numbers from 2 class C's to work together - I -->take it it stops working soon as you add a 204.101.125 --> -->The problem here is your default route is no longer in the same subnet. --> -->On Sat, 5 Oct 1996, Marc G. Fournier wrote: --> -->> -->> Hi... -->> -->> I'm attempting to combine IP aliasing and HTTP virtual domains -->> on my 2.2-Current box, and am failing miserably... -->> -->> I've got my ed0 device setup so that it is aliased for: -->> -->> 205.150.102.[51-62] -->> 204.101.125.[200-211] -->> -->> As soon as I try to enable a 13th Web server, I start getting: -->> -->> yp_first: clnt_call: RPC: Timed out -->> -->> And if I go back down to 12, its all fine. -->> -->> I'm thinking that there is either a setting I should be -->> increasing in the kernel, or it has something to do with the IP aliasing... -->> -->> Anyone have experience with this? -->> -->> Thanks... -->> -->> Marc G. Fournier scrappy@ki.net -->> Systems Administrator @ ki.net scrappy@freebsd.org -->> -->> --> --> ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ Syn-Work Media, Inc. | WWW Development & Hosting | Life Safety http://www.synwork.com | Systems Integration | CCTV mike@synwork.com | Voice/Data/Fiber | Access Control Flaq on IRC | Dukane Distributor | BICSI/RCDD :|:|:|: Powered By FreeBSD :|:|:|: Turning PC's Into Workstations ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ From owner-freebsd-current Sun Oct 6 07:52:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA22665 for current-outgoing; Sun, 6 Oct 1996 07:52:09 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA22657 for ; Sun, 6 Oct 1996 07:52:05 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id QAA16246 for ; Sun, 6 Oct 1996 16:52:03 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA13924 for freebsd-current@FreeBSD.org; Sun, 6 Oct 1996 16:52:02 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id QAA08151 for freebsd-current@FreeBSD.org; Sun, 6 Oct 1996 16:20:36 +0200 (MET DST) From: J Wunsch Message-Id: <199610061420.QAA08151@uriah.heep.sax.de> Subject: Re: secure level diffs to kern_mib.c, LINT To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 6 Oct 1996 16:20:36 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199610061132.VAA25153@godzilla.zeta.org.au> from Bruce Evans at "Oct 6, 96 09:32:19 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > Actually, securelevel 1 is normally so insecure that it shouldn't be used. > It essentially only provides write protection of /dev/mem and /dev/kmem. > The write protection on mounted disks is worthless becauses there are > lots of aliases. Even plain BSD has a whole disk partition, and FreeBSD > has lots of slices and SCSI control devices. The SCSI control devices should deny their service if securelevel is ``secure enough''. -- 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-current Sun Oct 6 08:30:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA24596 for current-outgoing; Sun, 6 Oct 1996 08:30:45 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA24588 for ; Sun, 6 Oct 1996 08:30:41 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id BAA30921; Mon, 7 Oct 1996 01:27:28 +1000 Date: Mon, 7 Oct 1996 01:27:28 +1000 From: Bruce Evans Message-Id: <199610061527.BAA30921@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, j@uriah.heep.sax.de Subject: Re: secure level diffs to kern_mib.c, LINT Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> The write protection on mounted disks is worthless becauses there are >> lots of aliases. Even plain BSD has a whole disk partition, and FreeBSD >> has lots of slices and SCSI control devices. > >The SCSI control devices should deny their service if securelevel is >``secure enough''. They already deny service if they are opened at securelevel 2, since they are disk devices, and disk devices can't be opened for writing at securelevel 2, and they require write permission for all ioctls. Bruce From owner-freebsd-current Sun Oct 6 10:21:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA00842 for current-outgoing; Sun, 6 Oct 1996 10:21:32 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA00837; Sun, 6 Oct 1996 10:21:28 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id KAA19048; Sun, 6 Oct 1996 10:19:34 -0700 (PDT) Message-Id: <199610061719.KAA19048@austin.polstra.com> To: Mark Mayo Cc: freebsd-questions@freebsd.org, freebsd-current@freebsd.org Subject: Re: Java,Netscape, & AccelX In-reply-to: Date: Sun, 06 Oct 1996 10:19:33 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Well, I'm sure it is some sort of problem with AcceleratedX - but > I'm also quite sure they won't give me any support considering I'm > running a 2.2 SNAP.... I think you should try them. They were pretty reasonable about support the last time I dealt with them. 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-current Sun Oct 6 10:22:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA00958 for current-outgoing; Sun, 6 Oct 1996 10:22:02 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA00916 for ; Sun, 6 Oct 1996 10:21:51 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id TAA19153 for ; Sun, 6 Oct 1996 19:21:47 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA18753 for freebsd-current@FreeBSD.org; Sun, 6 Oct 1996 19:21:47 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id SAA08758 for freebsd-current@FreeBSD.org; Sun, 6 Oct 1996 18:51:46 +0200 (MET DST) From: J Wunsch Message-Id: <199610061651.SAA08758@uriah.heep.sax.de> Subject: Re: secure level diffs to kern_mib.c, LINT To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 6 Oct 1996 18:51:46 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199610061527.BAA30921@godzilla.zeta.org.au> from Bruce Evans at "Oct 7, 96 01:27:28 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > >The SCSI control devices should deny their service if securelevel is > >``secure enough''. > > They already deny service if they are opened at securelevel 2, since > they are disk devices, and disk devices can't be opened for writing at > securelevel 2, and they require write permission for all ioctls. Not all SCSI control devices are disk devices. However, all of them are able to cause the same degree of damage to a SCSI bus (basically), so all of them must fall under the same restrictions. -- 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-current Sun Oct 6 10:32:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA01611 for current-outgoing; Sun, 6 Oct 1996 10:32:41 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA01603; Sun, 6 Oct 1996 10:32:37 -0700 (PDT) Received: from spirit.ki.net (root@spirit.ki.net [205.150.102.51]) by quagmire.ki.net (8.7.5/8.7.5) with ESMTP id NAA04942; Sun, 6 Oct 1996 13:32:38 -0400 (EDT) Received: from localhost (scrappy@localhost) by spirit.ki.net (8.7.5/8.7.3) with SMTP id NAA21069; Sun, 6 Oct 1996 13:32:33 -0400 (EDT) X-Authentication-Warning: spirit.ki.net: scrappy owned process doing -bs Date: Sun, 6 Oct 1996 13:32:28 -0400 (EDT) From: "Marc G. Fournier" To: Stephen Hovey cc: current@freebsd.org, questions@freebsd.org Subject: Re: yp_first error on WWW virtual domains... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 6 Oct 1996, Stephen Hovey wrote: > > Ive never been able to get numbers from 2 class C's to work together - I > take it it stops working soon as you add a 204.101.125 > > The problem here is your default route is no longer in the same subnet. > I hate to admit it...but my problem was file descriptors :( As soon as I did a unlimit before running httpd, all 11x2 virtual servers worked fine... > On Sat, 5 Oct 1996, Marc G. Fournier wrote: > > > > > Hi... > > > > I'm attempting to combine IP aliasing and HTTP virtual domains > > on my 2.2-Current box, and am failing miserably... > > > > I've got my ed0 device setup so that it is aliased for: > > > > 205.150.102.[51-62] > > 204.101.125.[200-211] > > > > As soon as I try to enable a 13th Web server, I start getting: > > > > yp_first: clnt_call: RPC: Timed out > > > > And if I go back down to 12, its all fine. > > > > I'm thinking that there is either a setting I should be > > increasing in the kernel, or it has something to do with the IP aliasing... > > > > Anyone have experience with this? > > > > Thanks... > > > > Marc G. Fournier scrappy@ki.net > > Systems Administrator @ ki.net scrappy@freebsd.org > > > > > Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Sun Oct 6 11:27:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA03470 for current-outgoing; Sun, 6 Oct 1996 11:27:15 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA03465 for ; Sun, 6 Oct 1996 11:27:13 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65v3.2/1.1.8.2/19Aug95-0530PM) id AA22366; Sun, 6 Oct 1996 14:27:12 -0400 Date: Sun, 6 Oct 1996 14:27:12 -0400 From: Garrett Wollman Message-Id: <9610061827.AA22366@halloran-eldar.lcs.mit.edu> To: current@freebsd.org Subject: secure level diffs to kern_mib.c, LINT In-Reply-To: References: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: > FreeBSD defaults securelevel to -1, use the following diffs if you prefer > normal bsd operations or want a choice. Man init(8) for details. I am strongly opposed to this patch, for reasons I have stated in this list in the past few days. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Sun Oct 6 11:45:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA04264 for current-outgoing; Sun, 6 Oct 1996 11:45:20 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA04258; Sun, 6 Oct 1996 11:45:13 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65v3.2/1.1.8.2/19Aug95-0530PM) id AA31522; Sun, 6 Oct 1996 14:45:07 -0400 Date: Sun, 6 Oct 1996 14:45:07 -0400 From: Garrett Wollman Message-Id: <9610061845.AA31522@halloran-eldar.lcs.mit.edu> To: Wolfram Schneider Cc: current@freebsd.org Subject: cvs commit: src/usr.bin/find extern.h find.1 find.h function.c option.c In-Reply-To: <199610061526.RAA02342@campa.panke.de> References: <199610041254.FAA16501@freefall.freebsd.org> <199610061526.RAA02342@campa.panke.de> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: > Peter Wemm writes: >> peter 96/10/04 05:54:09 >> >> Modified: usr.bin/find extern.h find.1 find.h function.c option.c > BTW, find(1) use fts_open(3), but does not call fts_close(3). > Same problem for chown(8)/chgrp(1) and du(1). Yeah, so? find is not some long-running daemon where it matters that resources be released immediately. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Sun Oct 6 13:07:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07562 for current-outgoing; Sun, 6 Oct 1996 13:07:29 -0700 (PDT) Received: from earth.gaianet.net (vince@earth.gaianet.net [206.171.98.28]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA07557 for ; Sun, 6 Oct 1996 13:07:26 -0700 (PDT) Received: from localhost (vince@localhost) by earth.gaianet.net (8.7.5/8.6.12) with SMTP id NAA25762 for ; Sun, 6 Oct 1996 13:07:13 -0700 (PDT) Date: Sun, 6 Oct 1996 13:07:13 -0700 (PDT) From: -Vince- To: current@freebsd.org Subject: contrib in -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings everyone, Does anyone know what contrib is used for in -current and is it required for a make world? Thanks. Vince GaiaNet Corporation - Unix Network System Admin From owner-freebsd-current Sun Oct 6 13:34:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA09353 for current-outgoing; Sun, 6 Oct 1996 13:34:20 -0700 (PDT) Received: from po1.glue.umd.edu (po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA09316 for ; Sun, 6 Oct 1996 13:34:17 -0700 (PDT) Received: from gilligan.eng.umd.edu (gilligan.eng.umd.edu [129.2.103.21]) by po1.glue.umd.edu (8.8.Gamma.0/8.7.3) with ESMTP id QAA17435; Sun, 6 Oct 1996 16:34:08 -0400 (EDT) Received: from localhost (chuckr@localhost) by gilligan.eng.umd.edu (8.7.5/8.7.3) with SMTP id QAA12523; Sun, 6 Oct 1996 16:34:08 -0400 (EDT) X-Authentication-Warning: gilligan.eng.umd.edu: chuckr owned process doing -bs Date: Sun, 6 Oct 1996 16:34:07 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@gilligan.eng.umd.edu To: -Vince- cc: current@freebsd.org Subject: Re: contrib in -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 6 Oct 1996, -Vince- wrote: > Greetings everyone, > > Does anyone know what contrib is used for in -current and is it > required for a make world? Thanks. Several large packages that were not written with BSD in mind have had their sources relocated to contrib, where they are supposedly being kept relatively free of patches, on the theory that this will make upgrading those packages simpler, when new updates are brought in. Mostly you'll find stuff that's already been part of current for a while, but there are already some new additions there. One good example is groff, which used to be part of /usr/src/gnu/usr.bin. A year from now, we'll probably know more, to see if this method really has made things simpler or not. I like it so far. > > Vince > GaiaNet Corporation - Unix Network System Admin > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Sun Oct 6 14:20:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA11680 for current-outgoing; Sun, 6 Oct 1996 14:20:23 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA11675 for ; Sun, 6 Oct 1996 14:20:19 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id HAA04241; Mon, 7 Oct 1996 07:12:27 +1000 Date: Mon, 7 Oct 1996 07:12:27 +1000 From: Bruce Evans Message-Id: <199610062112.HAA04241@godzilla.zeta.org.au> To: freebsd-current@freebsd.org, j@uriah.heep.sax.de Subject: Re: secure level diffs to kern_mib.c, LINT Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> They already deny service if they are opened at securelevel 2, since >> they are disk devices, and disk devices can't be opened for writing at >> securelevel 2, and they require write permission for all ioctls. > >Not all SCSI control devices are disk devices. However, all of them >are able to cause the same degree of damage to a SCSI bus (basically), >so all of them must fall under the same restrictions. I think they are all disk devices. Disk devices are by definition those that return nonzero for isdisk(). The control devices have the same major number as devices that really are disks, so they are classified as disks. SCSI cd devices cannot be opened for writing at securelevel 2 although they can't be written to anyway. However, there may be some interesting ioctls that can be done if the devices are open for writing. Bruce From owner-freebsd-current Sun Oct 6 16:04:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA18358 for current-outgoing; Sun, 6 Oct 1996 16:04:46 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA18352 for ; Sun, 6 Oct 1996 16:04:44 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id QAA10920; Sun, 6 Oct 1996 16:04:42 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id QAA11881 for ; Sun, 6 Oct 1996 16:04:33 -0700 (PDT) Message-Id: <199610062304.QAA11881@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: freebsd-current@freebsd.org Subject: Relative performance figures, FYI... Date: Sun, 06 Oct 1996 16:04:32 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Here's another batch of PPro figures. Now that I finally have three "Real Machines", I can try playing around with FreeBSD a little more. Anyway... FYI... I finally got a working Pentium Pro motherboard and CPU. I had been having some problems with a SuperMicro motherboard. I don't know if it was the motherboard or CPU. On Friday I received an Asus motherboard and 200MHz CPU to replace the faulty ones. It worked perfectly. And here are some relative performance figures: AMD 5x86 133MHz, NICE Super-EISA 486 motherboard, 24MB 60ns RAM, 512K L2 writeback cache, BusLogic BT747s EISA SCSI controller (on a 2GB Barracuda and a 1GB Hawk SCSI drives): Make world(*): ~6 hours, depending on various factors. Intel Pentium 120MHz (**), Asus P/I-P55TP4N (Triton-1) motherboard, 64MB 60ns EDO RAM, 512K L2 pipeline-burst cache, BusLogic BT956c PCI SCSI controller (same drives as above): Make world(*): 3 hours, 10 minutes, totally clean (no pre-built man pages, dependencies, etc.). Intel Pentium Pro 200MHz, Asus P/I-P6NP5 (Natoma) motherboard, 64MB 60ns EDO RAM, 256K L2 P6 cache, BusLogic BT956c PCI SCSI controller (same drives as above): Make world(*): 1 hour, 21 minutes, totally clean (same as above). Wow. A complete clean build of my very bloated kernel (including make clean, config, make depend, make) takes a little over fifteen minutes on my P5/120, and just over seven minutes on my P6/200. Wow. * - My own custom "make world" script that does things in a specific order, and does a few things redundantly. Building the NetBSD-1.2 sources. ** - I have tested it at both 100MHz (33/66MHz bus), and at 120MHz (30/60MHz bus) (20% faster CPU, 10% slower bus). It is just barely faster at 120MHz than at 100MHz, for all the tests I ran, in spite of the slower bus. However, the difference is so small that I can conclude (for my use anyway), that a 150MHz Pentium would be slower than a 133MHz (12.8% faster CPU, 10% slower bus), and a 180MHz Pentium would definitely be slower than a 166MHz (8.4% faster CPU, 10% slower bus). ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-current Sun Oct 6 17:59:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA23181 for current-outgoing; Sun, 6 Oct 1996 17:59:36 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA23175; Sun, 6 Oct 1996 17:59:32 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA13128; Sun, 6 Oct 1996 17:56:37 -0700 From: Terry Lambert Message-Id: <199610070056.RAA13128@phaeton.artisoft.com> Subject: Re: I plan to change random() for -current (was Re: rand() and random()) To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Date: Sun, 6 Oct 1996 17:56:37 -0700 (MST) Cc: terry@lambert.org, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@freebsd.org, current@freebsd.org In-Reply-To: <199610052204.CAA07197@nagual.ru> from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Oct 6, 96 02:04:17 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > There is a historical dependence of much physics code on the > > repeatability of identical seeding for the linear congruential > > generator as a "randomness" base for repeatable Monte Carlo based > > testing of relativistically invariant P-P, N-P, and N-N pair production > > collisions. > > The fix _not_ breaks repeatability of identical seeding. Repeatability means identical results compared to historical values for the same interface. > > If you *do* change the random algorithms, then you should *leave the > > rand48() code along*. I can not stress this enough. You will damage > > repeatability of experiments for which source code is unavailable, and > > only the results remain. > > I don't understand your statement well, random() already have different > implementations in different OSes. If you mean that previous FreeBSD > dynamic-linked binaries can produce different results, yes, it is > any upgrade cost. Make static binaries if source code is unavailable. Random is not random. Random is pseudo-random. I think what is being forgotton is that pseudo-randomness is useful because of its repeatability in many, many circumstances. > Depending on predictable system function results which claimed to > be 'random' is bad idea in general (and mans/docs/standards > not declare such possibility too). They only say that "this function > [not all possible versions of this function] > gives the same sequence for the same seed". Real practice when > rand() and random() functions changes between different OSes > and inside one OS too confirms it. I remember that Unix v6 rand() > was different with what we have currently, so we must return > to Unix v6 variant according to your logic. The code in question is from the Berkeley Physics package, in FORTRAN, for generation of relativitically invariant pair production events. I would be happy if you would keep BSD compatability, since BSD UNIX is where the code was written to run. The point is not repeatability, per se. It is that the event stream will be identical for a given set of N events for a given physics. The intent of doing this is to ensure that there is no statistical variance introduced by the period of the generator. The particular code in question uses the 48 bit linear congruential method. However, it is reasonable to presume that similar code exists for any given interface dependency. The point is that in 15 years, I can rerun the same event set with a different physics, and get the same event data which I then use the physics I am testing to constrain allowable events. It is statistically *important* to know how many events, out of 100 million events, are disallowed by a given constraint. As an example, a recent run of the code with a set of "Dion" physics constraints checked some laboratory experiments dealing with identifying the energy range of the carrier of the weak force to three decimal places. This gives the theoretical model a very high probability of being a correct model (as it happens, the same model predicted the W particle more than 8 years before it was experimentally discovered). For any pseudo-random generator, code is equally likely to depend on the "pseudo" as it is to depend on the "random". Any change to either bears a great deal of consideration. I personally have optics code that depends on the pseudo-randomness of the generator to create point origin vectors for testing theoretical chromatic aberration, and correcting aberration in real optical systems with CCD collectors. Among other things, it's used to remove aberration effects from the lens correction package when processing raw Hubble telescope data to look for extrasolar planets. In point of fact, you are suggesting "correcting" a "problem" because you want a different (not better) random distribution than what you currently get. I respectfully suggest that you should consider packing around your own random number generator with the code that needs the different distribution, rather than munging the existing code. Historical behaviour of pseudo-random library services is a topic requiring a *lot* of care before changes are introduced. I really haven't seen what I would consider enough thought or discussion to merit a change. As always: my opinions. 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-current Sun Oct 6 18:10:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA23775 for current-outgoing; Sun, 6 Oct 1996 18:10:23 -0700 (PDT) Received: from earth.gaianet.net (vince@earth.gaianet.net [206.171.98.28]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA23763 for ; Sun, 6 Oct 1996 18:10:13 -0700 (PDT) Received: from localhost (vince@localhost) by earth.gaianet.net (8.7.5/8.6.12) with SMTP id SAA06991 for ; Sun, 6 Oct 1996 18:10:05 -0700 (PDT) Date: Sun, 6 Oct 1996 18:10:05 -0700 (PDT) From: -Vince- To: current@FreeBSD.ORG Subject: sup update times Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Greetings everyone, Does anyone know what times during both PDT and PST does sup.FreeBSD.ORG get updated for the -current and SMP tree? and how much delay is sup4.FreeBSD.ORG in the update from sup.FreeBSD.ORG? Thanks. Cheers, -Vince- vince@earth.gaianet.net - GaiaNet Unix Networking System Admin From owner-freebsd-current Mon Oct 7 01:22:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA23415 for current-outgoing; Mon, 7 Oct 1996 01:22:18 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA23389 for ; Mon, 7 Oct 1996 01:22:07 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA11341 for ; Mon, 7 Oct 1996 10:21:14 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA02688 for freebsd-current@FreeBSD.org; Mon, 7 Oct 1996 10:21:14 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id KAA13768 for freebsd-current@FreeBSD.org; Mon, 7 Oct 1996 10:08:08 +0200 (MET DST) From: J Wunsch Message-Id: <199610070808.KAA13768@uriah.heep.sax.de> Subject: Re: secure level diffs to kern_mib.c, LINT To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 7 Oct 1996 10:08:08 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199610062112.HAA04241@godzilla.zeta.org.au> from Bruce Evans at "Oct 7, 96 07:12:27 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > >Not all SCSI control devices are disk devices. > I think they are all disk devices. Disk devices are by definition > those that return nonzero for isdisk(). The control devices have the > same major number as devices that really are disks, so they are > classified as disks. Also /dev/uk0.ctl, /dev/pt0.ctl? -- 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-current Mon Oct 7 02:11:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA27178 for current-outgoing; Mon, 7 Oct 1996 02:11:19 -0700 (PDT) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA27170; Mon, 7 Oct 1996 02:11:14 -0700 (PDT) Received: from grumble.grondar.za (mark@localhost.grondar.za [127.0.0.1]) by grumble.grondar.za (8.7.6/8.7.3) with ESMTP id LAA18921; Mon, 7 Oct 1996 11:11:06 +0200 (SAT) Message-Id: <199610070911.LAA18921@grumble.grondar.za> To: gibbs@freebsd.org cc: current@freebsd.org Subject: Adaptec AHA2940 Ultra Date: Mon, 07 Oct 1996 11:11:06 +0200 From: Mark Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi A colleague at work has just got an AHA2940UA. At boot time the message is (abbreviated) PCI0:9 Adaptec device=6178 int a irq 10 [No driver assigned] Have you any experience with this card? If I just patch the source to treat it as a 2940 or 2940U do I have a reasonable chance of success? M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Mon Oct 7 02:28:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA27791 for current-outgoing; Mon, 7 Oct 1996 02:28:50 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA27784 for ; Mon, 7 Oct 1996 02:28:46 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id JAA14300; Mon, 7 Oct 1996 09:28:38 GMT Date: Mon, 7 Oct 1996 18:28:38 +0900 (JST) From: Michael Hancock To: Garrett Wollman cc: current@FreeBSD.org Subject: Re: secure level diffs to kern_mib.c, LINT In-Reply-To: <9610061827.AA22366@halloran-eldar.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 6 Oct 1996, Garrett Wollman wrote: > < said: > > > FreeBSD defaults securelevel to -1, use the following diffs if you prefer > > normal bsd operations or want a choice. Man init(8) for details. > > I am strongly opposed to this patch, for reasons I have stated in this > list in the past few days. This security level stuff had an ambiguous design and a flawed implementation. It was ambiguous, but reasonable because it didn't depend on an command randomly placed in the rc scripts. By encouraging the use of sysctl -w in the rc scripts you're downgrading the design to the level of the flawed implementation. It seems we're worse off then before. "It's broken, let's break it more." I can just see it now, Joe security wizard fixes init and the secure level stuff and and says, "Ok, all you guys that followed the stupid advice of putting sysctl -w kern.securelevel in rc, rc.local, or some other random place, you can take those out now." Wouldn't it be better to encourage a better design and implementation; than to encourage the use of flawed work-arounds just because the implementation lets you? Design interfaces they way they should work, if the implementation doesn't work as designed, then write a good CAVEAT section in the man pages so somebody can fix them with the least disruption to the community's configurations. At least create an opportunity for improvement. Regards, Mike Hancock From owner-freebsd-current Mon Oct 7 02:45:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA28535 for current-outgoing; Mon, 7 Oct 1996 02:45:13 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA28527 for ; Mon, 7 Oct 1996 02:45:10 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id TAA24670; Mon, 7 Oct 1996 19:42:12 +1000 Date: Mon, 7 Oct 1996 19:42:12 +1000 From: Bruce Evans Message-Id: <199610070942.TAA24670@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, j@uriah.heep.sax.de Subject: Re: secure level diffs to kern_mib.c, LINT Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> >Not all SCSI control devices are disk devices. > >> I think they are all disk devices. Disk devices are by definition >> those that return nonzero for isdisk(). The control devices have the >> same major number as devices that really are disks, so they are >> classified as disks. > >Also /dev/uk0.ctl, /dev/pt0.ctl? Ah, you just found a bug in isdisk(). isdisk() should be named something like is_a_disklike_potential_security_hole(), since it is only used for the securelevel checks in spec_vnops.c and not for anything directly to do with disks. Also missing but listed in majors.i386: ccd, ch, sctarg, ssc, su. ccd is certainly for disks. ccd is is also missing from devices.i386. devices.i386 is only used by config for determining the device numbers of the devices in the "root on xxx" and "dumps on xxx" statements. It cleaims to only be used for swap devices. Please fix some of these bogons. Bruce From owner-freebsd-current Mon Oct 7 02:46:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA28589 for current-outgoing; Mon, 7 Oct 1996 02:46:40 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA28575 for ; Mon, 7 Oct 1996 02:46:33 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id CAA02628 for ; Mon, 7 Oct 1996 02:46:20 -0700 (PDT) To: current@freebsd.org Subject: 2.2-961006-SNAP - to CD or not to CD, that is the question. Date: Mon, 07 Oct 1996 02:46:20 -0700 Message-ID: <2626.844681580@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm currently copying this snapshot to ftp.freebsd.org (where it is NOT readable yet - that will come after the 70+MB of stuff has finally crossed my poor, overloaded ISDN line) and I'm just wondering whether or not people would like to see this released on CD or wait for the next SNAP in a couple of months. Given that it's only been 2 months since the last one, some folks might not want their SNAP subscriptions activated so soon. I can also do it as a "reorder upgrade" - once Walnut Creek CDROM runs out of stock with the current 2.2-960801-SNAPs (which they will easily do in another 2 weeks or so) I can simply have the reorder done with the new snap but NOT process it as another subscription. Only new subscribers or people buying the one-off CD will get the new edition, the subscribers being lined up for the next one. Whatever people want is what I'll do. I got a little bit of flack for releasing the 0801 CD so soon after the 0627 SNAP, and I don't want people to feel like WC is just shipping these things whenever they need a few bucks - it's not that way at all, and they just press whatever I ask them to press. So I'll leave it up to you, the subscribers, to tell me what you'd like: Do you want to see 2.2-960801-SNAP as the next subscription CD, the next replacement CD (e.g. a reorder) or not on CD at all and just a "network snap?" I'm also sure that many of the people who yelled last time won't actually see this message in time and I'll get yelled at anyway, but at least I'll be able to say that I *did* call for a vote first and was merely following the will of the people. :-) In case it makes the decision any easier, here's a quick summary of the new features in 2.2-961006-SNAP. For a fuller description, you'll have to wait until the bits have copied over and I've made an official announcement: --------------------- What's new: Support for HP PC Lan+ cards (model numbers: 27247B and 27252A) Update to gcc 2.7.2.1 & add support for weak symbols. Many things moved/brought into /usr/src/contrib, updating and cleaning up the source tree accordingly. Support for compiled-in shared library ld paths. Update sgmlfmt to `instant'. Protection against the widely reported SYN attack. Many changes to UserConfig (boot -c): Now displays PCI devices. Can be preloaded with commands by saying something like: printf "USERCONFIG\ndis aha0\ndis aic0" | \ dd of=/dev/rfd0 seek=1 bs=512 count=1 conv=sync Now launched by default (in boot.flp) unless overridden with user commands (see above). ------------ I'm sure there's also much I forgot, and if you spot a feature I should have mentioned here then please let me know ASAP and I'll add it to the RELNOTES.TXT file, preferably before the announcement goes out. Thanks!! Jordan From owner-freebsd-current Mon Oct 7 02:50:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA28792 for current-outgoing; Mon, 7 Oct 1996 02:50:12 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA28784 for ; Mon, 7 Oct 1996 02:50:08 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id JAA14430; Mon, 7 Oct 1996 09:49:17 GMT Date: Mon, 7 Oct 1996 18:49:17 +0900 (JST) From: Michael Hancock To: Bruce Evans cc: current@freebsd.org Subject: Re: secure level diffs to kern_mib.c, LINT In-Reply-To: <199610061132.VAA25153@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 6 Oct 1996, Bruce Evans wrote: > Actually, securelevel 1 is normally so insecure that it shouldn't be used. > It essentially only provides write protection of /dev/mem and /dev/kmem. Isn't write protection of /dev/mem /dev/kmem a good enough reason for use? > The write protection on mounted disks is worthless becauses there are > lots of aliases. Even plain BSD has a whole disk partition, and FreeBSD So facilitate improvements, don't hinder it. > has lots of slices and SCSI control devices. Perhaps this can be worked > around by deleting the aliases. Like this. Regards, Mike Hancock From owner-freebsd-current Mon Oct 7 03:12:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA01268 for current-outgoing; Mon, 7 Oct 1996 03:12:26 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA01241 for ; Mon, 7 Oct 1996 03:12:18 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id DAA05488; Mon, 7 Oct 1996 03:10:29 -0700 (PDT) To: Michael Hancock cc: Bruce Evans , current@freebsd.org Subject: Re: secure level diffs to kern_mib.c, LINT In-reply-to: Your message of "Mon, 07 Oct 1996 18:49:17 +0900." Date: Mon, 07 Oct 1996 03:10:27 -0700 Message-ID: <5486.844683027@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Sun, 6 Oct 1996, Bruce Evans wrote: > > > Actually, securelevel 1 is normally so insecure that it shouldn't be used. > > It essentially only provides write protection of /dev/mem and /dev/kmem. > > Isn't write protection of /dev/mem /dev/kmem a good enough reason for use? Not generally - think about having to install kernels or do make worlds single-user. I don't know of *anyone* who does make worlds while single-user, it simply takes the machine down for too long when it could still be doing useful work during the build - I usually have a make world running on my box *two or three times a day* and I don't even notice it while I do my other work. I don't see what the big deal about adding a sysctl line to /etc/rc is here, I really don't. > So facilitate improvements, don't hinder it. Sometimes "giving in to gratuitous nit-picking" is also confused with "facilitating improvements." :-) Jordan From owner-freebsd-current Mon Oct 7 03:28:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA04393 for current-outgoing; Mon, 7 Oct 1996 03:28:05 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA04275 for ; Mon, 7 Oct 1996 03:27:35 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.7.6/8.7.3) id MAA11134; Mon, 7 Oct 1996 12:27:18 +0200 (SAT) From: John Hay Message-Id: <199610071027.MAA11134@zibbi.mikom.csir.co.za> Subject: Re: Adaptec AHA2940 Ultra In-Reply-To: <199610070911.LAA18921@grumble.grondar.za> from Mark Murray at "Oct 7, 96 11:11:06 am" To: mark@grondar.za (Mark Murray) Date: Mon, 7 Oct 1996 12:27:18 +0200 (SAT) Cc: current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL24 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Hi > > A colleague at work has just got an AHA2940UA. At boot time > the message is (abbreviated) > > PCI0:9 Adaptec device=6178 int a irq 10 [No driver assigned] > > Have you any experience with this card? If I just patch the source > to treat it as a 2940 or 2940U do I have a reasonable chance of > success? > I made a few changes a while ago to make it work, but I think I saw Justin committing support for it during the weekend. One problem I had with the card (and my patches) was that when I did a reboot the Adaptec BIOS did not see the disks anymore. It might have been my patches, but some people suggested that it might be a firmware problem. John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-current Mon Oct 7 03:43:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA06422 for current-outgoing; Mon, 7 Oct 1996 03:43:27 -0700 (PDT) Received: from lassie.eunet.fi (lassie.eunet.fi [192.26.119.7]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA06406 for ; Mon, 7 Oct 1996 03:43:20 -0700 (PDT) Received: from marathon.tekla.fi by lassie.eunet.fi with SMTP id AA02823 (5.67a/IDA-1.5 for ); Mon, 7 Oct 1996 12:43:09 +0200 Received: from poveri.tekla.fi by marathon.tekla.fi (5.65/20-jun-90) id AA23327; Mon, 7 Oct 1996 12:43:07 +0200 From: sja@tekla.fi (Sakari Jalovaara) Received: by poveri.tekla.fi; (5.65v3.2/1.1.8.2/20Aug96-0557PM) id AA10431; Mon, 7 Oct 1996 13:43:07 +0300 Date: Mon, 7 Oct 1996 13:43:07 +0300 Message-Id: <9610071043.AA10431@poveri.tekla.fi> To: current@FreeBSD.org Subject: Re: compiling -current with -Dlint Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> >> Id strings should be declared as const and possibly as __unused, and >> possibly in a macro so that the details can be changed. >> > >I have been able to get rid of the offending warning without >-Dlint by using a declaration like: > > static char const sccsid[] = "..."; How about hacking the C compiler so it doesn't emit unused variable warnings about static variables called "sccsid" or "rcsid"? It's a two-line change. ++sja From owner-freebsd-current Mon Oct 7 04:00:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA08223 for current-outgoing; Mon, 7 Oct 1996 04:00:53 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA08148 for ; Mon, 7 Oct 1996 04:00:07 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id UAA26363; Mon, 7 Oct 1996 20:49:28 +1000 Date: Mon, 7 Oct 1996 20:49:28 +1000 From: Bruce Evans Message-Id: <199610071049.UAA26363@godzilla.zeta.org.au> To: bde@zeta.org.au, michaelh@cet.co.jp Subject: Re: secure level diffs to kern_mib.c, LINT Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Actually, securelevel 1 is normally so insecure that it shouldn't be used. >> It essentially only provides write protection of /dev/mem and /dev/kmem. > >Isn't write protection of /dev/mem /dev/kmem a good enough reason for use? No, it gives a false sense of security. Start with securelevel 2, where there are fewer bugs and the bugs are easier to fix. Bruce From owner-freebsd-current Mon Oct 7 04:42:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA18488 for current-outgoing; Mon, 7 Oct 1996 04:42:59 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA18476 for ; Mon, 7 Oct 1996 04:42:56 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id LAA15073; Mon, 7 Oct 1996 11:33:21 GMT Date: Mon, 7 Oct 1996 20:33:20 +0900 (JST) From: Michael Hancock To: Bruce Evans cc: current@freebsd.org Subject: Re: secure level diffs to kern_mib.c, LINT In-Reply-To: <199610071049.UAA26363@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 7 Oct 1996, Bruce Evans wrote: > >> Actually, securelevel 1 is normally so insecure that it shouldn't be used. > >> It essentially only provides write protection of /dev/mem and /dev/kmem. > > > >Isn't write protection of /dev/mem /dev/kmem a good enough reason for use? > > No, it gives a false sense of security. Start with securelevel 2, where Put this in the man pages with explanations for people who want a shade of grey instead of just black and white. If they decide to use it, they're responsible for their choice not you. Regards, Mike From owner-freebsd-current Mon Oct 7 04:52:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA20166 for current-outgoing; Mon, 7 Oct 1996 04:52:21 -0700 (PDT) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA20122 for ; Mon, 7 Oct 1996 04:52:03 -0700 (PDT) Received: from grumble.grondar.za (mark@localhost.grondar.za [127.0.0.1]) by grumble.grondar.za (8.7.6/8.7.3) with ESMTP id NAA19290; Mon, 7 Oct 1996 13:51:32 +0200 (SAT) Message-Id: <199610071151.NAA19290@grumble.grondar.za> To: John Hay cc: current@freebsd.org Subject: Re: Adaptec AHA2940 Ultra Date: Mon, 07 Oct 1996 13:51:32 +0200 From: Mark Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks! I found this 20mins ago! M John Hay wrote: > > A colleague at work has just got an AHA2940UA. At boot time > > the message is (abbreviated) > > > > PCI0:9 Adaptec device=6178 int a irq 10 [No driver assigned] > > > > Have you any experience with this card? If I just patch the source > > to treat it as a 2940 or 2940U do I have a reasonable chance of > > success? > > > > I made a few changes a while ago to make it work, but I think I saw > Justin committing support for it during the weekend. One problem I > had with the card (and my patches) was that when I did a reboot the > Adaptec BIOS did not see the disks anymore. It might have been my > patches, but some people suggested that it might be a firmware > problem. > > John > -- > John Hay -- John.Hay@mikom.csir.co.za -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Mon Oct 7 07:02:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA28199 for current-outgoing; Mon, 7 Oct 1996 07:02:54 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA28191; Mon, 7 Oct 1996 07:02:50 -0700 (PDT) Message-Id: <199610071402.HAA28191@freefall.freebsd.org> To: Mark Murray cc: gibbs@freebsd.org, current@freebsd.org Subject: Re: Adaptec AHA2940 Ultra In-reply-to: Your message of "Mon, 07 Oct 1996 11:11:06 +0200." <199610070911.LAA18921@grumble.grondar.za> Date: Mon, 07 Oct 1996 07:02:49 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Hi > >A colleague at work has just got an AHA2940UA. At boot time >the message is (abbreviated) > >PCI0:9 Adaptec device=6178 int a irq 10 [No driver assigned] > >Have you any experience with this card? If I just patch the source >to treat it as a 2940 or 2940U do I have a reasonable chance of >success? I added support for this card this weekend. > >M >-- >Mark Murray >46 Harvey Rd, Claremont, Cape Town 7700, South Africa >+27 21 61-3768 GMT+0200 >Finger mark@grondar.za for PGP key -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Mon Oct 7 10:14:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA11761 for current-outgoing; Mon, 7 Oct 1996 10:14:06 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-26.ut.nl.ibm.net [139.92.42.26]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA11752 for ; Mon, 7 Oct 1996 10:14:00 -0700 (PDT) Received: (from jhs@localhost) by vector.jhs.no_domain (8.7.5/8.6.9) id QAA22945; Mon, 7 Oct 1996 16:21:02 +0100 (MET) Date: Mon, 7 Oct 1996 16:21:02 +0100 (MET) Message-Id: <199610071521.QAA22945@vector.jhs.no_domain> To: current@freebsd.org Subject: Out of mbuf clusters - increase maxusers! From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Mailer: EXMH 1.6.7, PGP available X-Address: Holz Strasse 27d, 80469 Munich, Germany X-Phone: +49.89.268616 X-Fax: +49.89.2608126 X-Web: http://www.freebsd.org/~jhs/ Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Could a kernel guru perhaps extend the console message in /sys/vm/vm_kern.c: 319 ? /kernel: Out of mbuf clusters - increase maxusers! to be a little more informative ? Maybe to something like: /kernel: Performance Warning: Out of mbuf clusters - increase maxusers ! Or /kernel: Process Aborted: Out of mbuf clusters - increase maxusers ! Even when one looks in src/ to see if this message is merely a warning or an error, it's not immediately obvious, & not all FreeBSD systems have /usr/src/sys on line, so leaving sys admins with a suspicion something may have broken or aborted somewhere, but no certainty. Julian --- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Mon Oct 7 10:15:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA11833 for current-outgoing; Mon, 7 Oct 1996 10:15:02 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-26.ut.nl.ibm.net [139.92.42.26]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA11821 for ; Mon, 7 Oct 1996 10:14:55 -0700 (PDT) Received: (from jhs@localhost) by vector.jhs.no_domain (8.7.5/8.6.9) id KAA16083; Mon, 7 Oct 1996 10:48:50 +0100 (MET) Date: Mon, 7 Oct 1996 10:48:50 +0100 (MET) Message-Id: <199610070948.KAA16083@vector.jhs.no_domain> To: current@freebsd.org Subject: tunefs.8c -o lacks syntax for keywords space and time From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Mailer: EXMH 1.6.7, PGP available X-Address: Holz Strasse 27d, 80469 Munich, Germany X-Phone: +49.89.268616 X-Fax: +49.89.2608126 X-Web: http://www.freebsd.org/~jhs/ Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Current /usr/src/*/tunefs/tunefs.8c appears to be a bit damaged ... The syntax : -o space is not specified in the manual. On very-current: cd /usr/src/*/tunefs ; nroff -man *.8 | more one gets: -o optimize_preference The file system can either try to minimize the time spent allo- cating blocks, or it can attempt to minimize the space fragmenta- tion on the disk. Optimization for space has much higher overhead for file writes. The kernel normally changes the preference au- tomatically as the percent fragmentation changes on the file sys- tem. Notice the keywords space & time are not in bold or anything ? doesnt appear documented anywhere what optimize_preference should be ? (I just happen to remember space & time as keywords from the past). This syntax is accepted though: tunefs -m 0 /dev/rsd2s2a tunefs: minimum percentage of free space changes from 8% to 0% tunefs: should optimize for space with minfree < 8% tunefs -o space /dev/rsd2s2a tunefs: optimization preference changes from time to space Admittedly my binary is a couple of weeks old, ditto my groff macros, but my /usr/src/*/tunefs/tunefs.8c is within 12 hours of current (as of writing). Maybe someone current could take a look ? Julian --- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Mon Oct 7 10:36:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA12945 for current-outgoing; Mon, 7 Oct 1996 10:36:56 -0700 (PDT) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA12936; Mon, 7 Oct 1996 10:36:49 -0700 (PDT) Received: by sovcom.kiae.su id AA07011 (5.65.kiae-1 ); Mon, 7 Oct 1996 20:22:03 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Mon, 7 Oct 96 20:22:03 +0300 Received: (from ache@localhost) by nagual.ru (8.7.6/8.7.3) id VAA01227; Mon, 7 Oct 1996 21:20:33 +0400 (MSD) Message-Id: <199610071720.VAA01227@nagual.ru> Subject: Re: I plan to change random() for -current (was Re: rand() and random()) In-Reply-To: <199610070056.RAA13128@phaeton.artisoft.com> from "Terry Lambert" at "Oct 6, 96 05:56:37 pm" To: terry@lambert.org (Terry Lambert) Date: Mon, 7 Oct 1996 21:20:32 +0400 (MSD) Cc: terry@lambert.org, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org, current@FreeBSD.org, bde@zeta.org.au (Bruce Evans) From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast 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-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > There is a historical dependence of much physics code on the > > > repeatability of identical seeding for the linear congruential > > > generator as a "randomness" base for repeatable Monte Carlo based > > > testing of relativistically invariant P-P, N-P, and N-N pair production > > > collisions. > > > > The fix _not_ breaks repeatability of identical seeding. > > Repeatability means identical results compared to historical values > for the same interface. We must follow standards and not some bad programmer practice. The fix I mean confirm standards. The thing you want not described in any standard and no more that bad programmer assumption. > The code in question is from the Berkeley Physics package, in FORTRAN, > for generation of relativitically invariant pair production events. > > I would be happy if you would keep BSD compatability, since BSD UNIX is > where the code was written to run. I suspect (I'll try to check it in near time) that BSD random() change its formulae in BSD lifetime. > The particular code in question uses the 48 bit linear congruential > method. However, it is reasonable to presume that similar code exists > for any given interface dependency. rand48 family is different thing which I not plan to touch. > you want a different (not better) random distribution than what you > currently get. I don't change random distribution at all with this fix, please look at it more carefully. I change only initial seeding behaviour. > I respectfully suggest that you should consider packing around your > own random number generator with the code that needs the different > distribution, rather than munging the existing code. Historical > behaviour of pseudo-random library services is a topic requiring a > *lot* of care before changes are introduced. I really haven't seen > what I would consider enough thought or discussion to merit a change. > > As always: my opinions. Well, it sounds like "golden code" syndrome.... We already do this thing before and I don't see your complaints. I mean Bruce's fixes to math library precision f.e. All math calculations which uses affected function will produce different results! All physic experiments becomes not-repeatable! Etc. And you keep silence it that case I don't understand why. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Mon Oct 7 10:49:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA13636 for current-outgoing; Mon, 7 Oct 1996 10:49:47 -0700 (PDT) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA13631; Mon, 7 Oct 1996 10:49:38 -0700 (PDT) Received: by sovcom.kiae.su id AA13864 (5.65.kiae-1 ); Mon, 7 Oct 1996 20:42:30 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Mon, 7 Oct 96 20:42:30 +0300 Received: (from ache@localhost) by nagual.ru (8.7.6/8.7.3) id VAA01397; Mon, 7 Oct 1996 21:41:20 +0400 (MSD) Message-Id: <199610071741.VAA01397@nagual.ru> Subject: random() fix explanation to avoid misunderstanding To: hackers@freebsd.org (FreeBSD-hackers List), current@freebsd.org (FreeBSD-current) Date: Mon, 7 Oct 1996 21:41:19 +0400 (MSD) From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At this moment I saw several own people misinterpretation of the fix like "make random generator better" or "change random distribution", etc. Here the correct answer: the fix NOT change random generator, it change SEEDING bug. Due to this bug given states algorithm is useless! I.e. it isn't needed at all to have initstate()/setstate() things with initial weak seeding formulae, because it breaks all following calculations. Netscape story is some sort of analogy: poor random number generator there make useless following good SSL algorithm. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Mon Oct 7 11:17:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA15438 for current-outgoing; Mon, 7 Oct 1996 11:17:14 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA15433; Mon, 7 Oct 1996 11:17:12 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA14432; Mon, 7 Oct 1996 11:10:44 -0700 From: Terry Lambert Message-Id: <199610071810.LAA14432@phaeton.artisoft.com> Subject: Re: I plan to change random() for -current (was Re: rand() and random()) To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Date: Mon, 7 Oct 1996 11:10:44 -0700 (MST) Cc: terry@lambert.org, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org, current@FreeBSD.org, bde@zeta.org.au In-Reply-To: <199610071720.VAA01227@nagual.ru> from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Oct 7, 96 09:20:32 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Repeatability means identical results compared to historical values > > for the same interface. > > We must follow standards and not some bad programmer practice. > The fix I mean confirm standards. The thing you want not described > in any standard and no more that bad programmer assumption. Bullshit. It says right in the man page that it is a pseudo-random number generator, and there is an interface for setting the seed value. I have every right to expect the thing to produce repeatable values over time. > I suspect (I'll try to check it in near time) that BSD random() > change its formulae in BSD lifetime. Not without notification it hasn't, and not without publicaton of the prevous algorithm. For a long time, the Berkeley code had an integrer overflow based random generator included with the package. It was found to be unreliable because of differences in number of bits. > > The particular code in question uses the 48 bit linear congruential > > method. However, it is reasonable to presume that similar code exists > > for any given interface dependency. > > rand48 family is different thing which I not plan to touch. That is not the point. The point is that there is a random function that is documented as being pseudo-random and which has a settable seed value, and neither you nor I can believably claim that the random number generator is not depended upon in this way for someone's important work. Work a hell of a lot more important than satisfying some programmer's idea of correct aesthetics. > > you want a different (not better) random distribution than what you > > currently get. > > I don't change random distribution at all with this fix, please > look at it more carefully. I change only initial seeding behaviour. If I call srandom with the same values I have historically called it with, will I get the same results I have hostorically gotten? If so, I withdraw my objection; if not I maintain and reaffirm it. > Well, it sounds like "golden code" syndrome.... It *is* "golden code syndrome". That doesn't make it any less of a valid argument. > We already do this thing before and I don't see your complaints. > I mean Bruce's fixes to math library precision f.e. > All math calculations which uses affected function will produce > different results! All physic experiments becomes not-repeatable! > Etc. And you keep silence it that case I don't understand why. As I said, comparison is impossible. Luckily, the experiments have been run on Sun Hardware, and the FreeBSD hardware was only used for the FORTRAN to C conversion process, and not for real results. If you want FreeBSD to be trusted for this kind of work, you must correct your process and assumptions. Much of the NetBSD math lib work results in a cleanup of many of these issues, and is portable to FreeBSD. Using the NetBSD code and the Sun libm code, the results were identical to those obtained on the Sun (for a single comparison, anyway) and the Sun's results identical to those obtained on the CDC and Cray systems at Los Alamos and on the KL-10/KL-11 based DEC 10 and 20 systems on which the code has also been run. It *is* "golden code syndrome". Where we seem to disagree is in deciding if this is a bad thing or not. Unless you are a mathematical programmer, you are unlikely to be able to aprehend the consequences of even a trivial change away from mathematical standards will have. There are verifiable standards of correctness, and each standard dictates issues of precision to which one can trust the code. Obviously, differences after the significant digits can be ignored for comparison -- and are, in fact, stripped from results as the "noise" that they are. I suggest strict adherence to standards -- mathematical standards, not ANSI or ISO C standards -- with regard to maintaining precision and historical implementation, as required to ensure repeatability and trust. 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-current Mon Oct 7 11:21:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA15667 for current-outgoing; Mon, 7 Oct 1996 11:21:23 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA15653 for ; Mon, 7 Oct 1996 11:21:10 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA05181 for ; Mon, 7 Oct 1996 20:21:04 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA13565 for freebsd-current@FreeBSD.org; Mon, 7 Oct 1996 20:21:04 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id UAA15280 for freebsd-current@FreeBSD.org; Mon, 7 Oct 1996 20:05:48 +0200 (MET DST) From: J Wunsch Message-Id: <199610071805.UAA15280@uriah.heep.sax.de> Subject: Re: secure level diffs to kern_mib.c, LINT To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 7 Oct 1996 20:05:48 +0200 (MET DST) In-Reply-To: <5486.844683027@time.cdrom.com> from "Jordan K. Hubbard" at "Oct 7, 96 03:10:27 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: > Not generally - think about having to install kernels or do make > worlds single-user. Development machines will generally not want to run in `secure' mode at all. Servers or other mission-critical machines will generally not want to serve as development machines (for an OS development). That is, time.cdrom.com's config file would have the ``options INSECURE'' line in it, but wcarchive.cdrom.com's config file would not. -- 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-current Mon Oct 7 11:23:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA15755 for current-outgoing; Mon, 7 Oct 1996 11:23:25 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA15743 for ; Mon, 7 Oct 1996 11:23:20 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id OAA29978 for ; Mon, 7 Oct 1996 14:23:18 -0400 (EDT) Date: Mon, 7 Oct 1996 14:23:18 -0400 (EDT) From: Brian Tao To: FREEBSD-CURRENT-L Subject: "Invalid hostname" as a hostname? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I noticed today that the output from `w', `who' and `last' show the string "invalid hostname" where the hostname/IP address would normally appear. As far as I can tell, the affected people are coming in from a host whose IP address is known in our DNS (this machine is behind a firewall, thus the RFC1918 addresses). What's invalid about "jazz.montreal.ican.net" as a hostname vs. "freedom.montreal.ican.net"? % w 1:45PM up 5 days, 1:11, 53 users, load averages: 3.55, 4.24, 3.68 USER TTY FROM LOGIN@ IDLE WHAT phil p0 10.1.1.80 1:05PM 25 ssh shine q p1 slurp 1:10PM 12 slogin trepan (ssh) q p2 slurp 1:18PM 3 slogin zap (ssh) g2 p3 fall:0.0 1:42PM - ssh crunch batsy p5 groovy.io.org Thu06PM 9 ssh zot jcolvin p7 mosey:0.0 8:29AM 1:11 ssh mail.ican.net rpbird pa roger.io.org 10:48AM 1 ssh -l roger ican.net batsy pb groovy.io.org Wed01PM 1:15 -tcsh (tcsh) khaber pc trip:0.0 7:39AM 7 ssh trepan jean pd stumble:0.0 9:16AM 44 ssh trepan q pe stagger:0.0 10:13AM 2:21 -csh (tcsh) taob pf cabal.io.org Sat07PM - w g2 pg fall:0.0 9:23AM 26 ssh io.org batsy pi groovy.io.org Wed01PM 9 ssh zot khaber pj trip:0.0 7:40AM 25 ssh shine g2 pn fall:0.0 9:23AM 3:48 ssh crunch jazzman po invalid hostname 9:40AM 1:01 /usr/local/bin/ssh mail g2 pp fall:0.0 11:18AM 2:01 ssh -l jake shine g2 pq fall:0.0 9:23AM 2:41 ssh trepan.io.org boobie pr boobie 11:21AM 2:13 /usr/local/bin/ssh -l bobbi ican.net q ps slurp 11:25AM - slogin wave (ssh) g2 pt fall:0.0 12:16PM 11 ssh trepan boobie pv boobie 11:32AM 48 /usr/local/bin/ssh -l cathy trepan maddox q1 duppy.montreal.i 8:37AM 10 /usr/local/bin/./ssh crunch maddox q2 duppy.montreal.i 8:39AM 10 /usr/local/bin/./ssh -l stephane shine boobie q3 boobie 11:34AM 1:57 /usr/local/bin/ssh -l cathy empress maddox q4 duppy.montreal.i 8:46AM - /usr/local/bin/./ssh mail.ican.net jcolvin q5 nap.io.org 9:08AM 4:36 irc jc nap.io.org (irc-2.8.16beta) g2 q6 fall:0.0 11:34AM 13 ssh zap boobie q7 boobie 11:34AM 2:09 /usr/local/bin/ssh -l boobie trepan jcolvin q8 mosey:0.0 8:09AM 35 ssh shine jcolvin qa mosey:0.0 8:09AM 35 ssh crunch jcolvin qb mosey:0.0 8:09AM 1:03 ssh trepan jcolvin qc mosey:0.0 8:09AM 1:04 ssh trepan syick qd syick Fri04PM 5 /usr/local/bin/ssh -l syick trepan jcolvin qe mosey:0.0 9:08AM 4:36 ssh nap.io.org boobie qf boobie 11:50AM 1:54 /usr/local/bin/ssh -l cathy shine jazzman qg invalid hostname 11:36AM 42 /usr/local/bin/ssh shine phil qh 10.1.1.80 12:40PM 22 ssh mail.ican.net batsy qi groovy.io.org 12:24PM 53 ssh zap phil qj 10.1.1.80 12:48PM 21 ssh ican.net khaber Pl trip:0:S.0 7:40AM 49 ssh trepan khaber Pm trip:0:S.1 7:41AM 10 ssh crunch bigmac Qo freedom.montreal 8:30AM 30 ssh shine bigmac Qp freedom.montreal 8:36AM 1:15 ssh mail.ican.net bigmac Qq freedom.montreal 8:37AM 5:08 -usr/local/bin/tcsh bigmac Qr freedom.montreal 8:37AM 2:03 ssh trepan bigmac Qs freedom.montreal 8:37AM 30 ssh crunch twiggy Qt invalid hostname 11:08AM 1:01 /usr/local/bin/ssh shine twiggy Qu invalid hostname 11:22AM 45 /usr/local/bin/ssh crunch twiggy Qv invalid hostname 11:22AM - /usr/local/bin/ssh mail twiggy R0 invalid hostname 11:26AM 8 /usr/local/bin/ssh trepan twiggy R1 invalid hostname 11:26AM 8 /usr/local/bin/ssh trepan % last jazzman jazzman ttyqg invalid hostname Mon Oct 7 11:36 still logged in jazzman ttypo invalid hostname Mon Oct 7 09:40 still logged in jazzman ttypr invalid hostname Fri Oct 4 22:26 - 23:57 (01:30) jazzman ttypa 10.2.120.26 Fri Oct 4 21:07 - 21:09 (00:01) jazzman ttypv 10.2.120.26 Fri Oct 4 16:42 - 21:23 (04:41) jazzman ttyq2 invalid hostname Fri Oct 4 16:26 - 21:23 (04:57) jazzman ttyq1 invalid hostname Thu Oct 3 09:05 - 15:57 (06:51) jazzman ttypp invalid hostname Thu Oct 3 08:16 - 15:56 (07:40) jazzman ttyq4 10.2.120.26 Wed Oct 2 18:31 - 23:58 (05:27) jazzman ttyp3 10.2.120.26 Wed Oct 2 16:59 - 23:58 (06:59) jazzman ttyp3 10.2.120.26 Wed Oct 2 16:10 - 16:56 (00:46) jazzman ttyph 10.2.120.26 Wed Oct 2 16:06 - 16:56 (00:49) wtmp begins Tue Oct 1 17:01 % fgrep jazzman /var/log/messages Oct 2 16:06:48 nap login: login from 10.2.120.26 as jazzman Oct 2 16:10:02 nap login: login from 10.2.120.26 as jazzman Oct 2 16:59:03 nap login: login from 10.2.120.26 as jazzman Oct 2 18:31:24 nap login: login from 10.2.120.26 as jazzman Oct 3 08:16:05 nap login: login from jazz.montreal.ican.net as jazzman Oct 3 09:05:20 nap login: login from jazz.montreal.ican.net as jazzman Oct 4 16:26:36 nap login: login from jazz.montreal.ican.net as jazzman Oct 4 22:26:41 nap login: login from jazz.montreal.ican.net as jazzman Oct 7 09:40:01 nap login: login from jazz.montreal.ican.net as jazzman Oct 7 11:36:44 nap login: login from jazz.montreal.ican.net as jazzman -- Brian Tao (BT300, taob@io.org, taob@ican.net) Senior Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't" From owner-freebsd-current Mon Oct 7 11:30:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA16164 for current-outgoing; Mon, 7 Oct 1996 11:30:49 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA16158; Mon, 7 Oct 1996 11:30:47 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA14499; Mon, 7 Oct 1996 11:27:36 -0700 From: Terry Lambert Message-Id: <199610071827.LAA14499@phaeton.artisoft.com> Subject: Re: random() fix explanation to avoid misunderstanding To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Date: Mon, 7 Oct 1996 11:27:36 -0700 (MST) Cc: hackers@FreeBSD.org, current@FreeBSD.org In-Reply-To: <199610071741.VAA01397@nagual.ru> from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Oct 7, 96 09:41:19 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > At this moment I saw several own people misinterpretation of the fix like > "make random generator better" or "change random distribution", etc. > > Here the correct answer: the fix NOT change random generator, it > change SEEDING bug. Due to this bug given states algorithm is > useless! I.e. it isn't needed at all to have initstate()/setstate() > things with initial weak seeding formulae, because it breaks all > following calculations. > > Netscape story is some sort of analogy: poor random number generator > there make useless following good SSL algorithm. I understand that you are improving the "random" while at the same time damaging the "pseudo". I further understand that since the (non-mathematically precise) standard does not specify the "pseudo", that you feel yourself justified in making this change, since you view the platform as a platform providing ANSI and ISO standards compliant interfaces, not necessarily mathematically or computationally useful interfaces. However, I *strongly* urge you to make the fact of this change as obvious (and reversible) as you possibly can. I can not stress strongly enough that this type of change, if done casually, *seriously* impacts the utility of the platform for *real* uses, rather than simply Computer Science uses. Computer systems are more than just toys for the people who build them. There is a vast difference between cryptographic suitability, which relies on large number theory, and suitability for use in Monte Carlo based algorithms for test data generation, which relies more on the fact of repeatable pseudo-randomness than it does on achieving a cryptographically "good" point distribution. 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-current Mon Oct 7 11:31:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA16250 for current-outgoing; Mon, 7 Oct 1996 11:31:19 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA16219; Mon, 7 Oct 1996 11:31:13 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65v3.2/1.1.8.2/19Aug95-0530PM) id AA06015; Mon, 7 Oct 1996 14:29:49 -0400 Date: Mon, 7 Oct 1996 14:29:49 -0400 From: Garrett Wollman Message-Id: <9610071829.AA06015@halloran-eldar.lcs.mit.edu> To: Terry Lambert Cc: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=), joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org, current@FreeBSD.org, bde@zeta.org.au Subject: Re: I plan to change random() for -current (was Re: rand() and random()) In-Reply-To: <199610071810.LAA14432@phaeton.artisoft.com> References: <199610071720.VAA01227@nagual.ru> <199610071810.LAA14432@phaeton.artisoft.com> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk < said: >> Well, it sounds like "golden code" syndrome.... > It *is* "golden code syndrome". > That doesn't make it any less of a valid argument. I would say it's more like Terry bitching like he usually does about somebody making a piece of code act like it's supposed to on the grounds that someone, somewhere actually depends on the bugs in it. I for one am quite sick of your whining. Around here we call that attitude ``UNIX Hacker bug #78''. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Mon Oct 7 11:36:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA16734 for current-outgoing; Mon, 7 Oct 1996 11:36:34 -0700 (PDT) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA16728; Mon, 7 Oct 1996 11:36:32 -0700 (PDT) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA17544; Mon, 7 Oct 1996 11:23:20 -0700 Date: Mon, 7 Oct 1996 11:23:20 -0700 (PDT) From: "Brian N. Handy" To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= Cc: Terry Lambert , joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org, current@FreeBSD.org, Bruce Evans Subject: Re: I plan to change random() for -current (was Re: rand() and random()) In-Reply-To: <199610071720.VAA01227@nagual.ru> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hey all, I'm trying to stay on top of this thread and follow all the theories, and I'll throw in my two cents -- It's important to recall Andrey wanted to change random() originally in part because the Gimp folks (and probably others) complain that our random() is really too non-random(). I've done a fair amount of fiddling with random number generators in my time, and I think it's safe to say there's no way it's going to get improved to the point where the numerical folks are happy. Jordan hit this one squarely on the head. Hence most of them use their own random number generator. I don't know anyone that depends on the routine that comes with the system. That's almost scary. There's been one suggestion to write another random number generator and not changing the old one. I don't think that's going to fix anything, since in general the software driving this change (GIMP et al) is all going to have to have small ugly hacks in them to support it. It would be nicer if our random() just worked. So, following in this line of reasoning, I support fixing random(). Regards, Brian From owner-freebsd-current Mon Oct 7 11:57:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA18143 for current-outgoing; Mon, 7 Oct 1996 11:57:18 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA18134; Mon, 7 Oct 1996 11:57:12 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA14614; Mon, 7 Oct 1996 11:50:43 -0700 From: Terry Lambert Message-Id: <199610071850.LAA14614@phaeton.artisoft.com> Subject: Re: I plan to change random() for -current (was Re: rand() and random()) To: wollman@lcs.mit.edu (Garrett Wollman) Date: Mon, 7 Oct 1996 11:50:42 -0700 (MST) Cc: terry@lambert.org, ache@nagual.ru, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org, current@FreeBSD.org, bde@zeta.org.au In-Reply-To: <9610071829.AA06015@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Oct 7, 96 02:29:49 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-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > >> Well, it sounds like "golden code" syndrome.... > > > It *is* "golden code syndrome". > > > That doesn't make it any less of a valid argument. > > I would say it's more like Terry bitching like he usually does about > somebody making a piece of code act like it's supposed to on the > grounds that someone, somewhere actually depends on the bugs in it. > I for one am quite sick of your whining. > > Around here we call that attitude ``UNIX Hacker bug #78''. With respect, Garrett, I'm the one who usually bitches about code *not* actinlg "like it's supposed to". I'm probably most famous for complaining about the BSD 4.4-Lite VFS code, as integrated by CSRG, not acting like John Heidemann's thesis (the design document) dictates it should act. However, I will argue against change when the historical behaviour is "important". I will note for the record that most of the refusal to adopt SVR4 conventions, like the init level abstraction, are a result of inertia: general support for historical BSD'isms, without regard to technical merit. Here we have an issue where the technical merit is relative: it depends on if you depends on the "random" behaviour" or if you depends on the "pseudo" behaviour. This is the main ideological debate. Again, with respect, "act like it's supposed to" is relative in this case. Unlike the VFS code, where CSRG has provably damaged the implementation -- demonstrable by even a cursory examination of the design document it purports to implement -- and which you have actively prevented me from correcting. This is not simply "Terry bitching". 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-current Mon Oct 7 12:08:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA19047 for current-outgoing; Mon, 7 Oct 1996 12:08:25 -0700 (PDT) Received: from mole.mole.org (marmot.mole.org [204.216.57.191]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA19037; Mon, 7 Oct 1996 12:08:22 -0700 (PDT) Received: (from mail@localhost) by mole.mole.org (8.6.12/8.6.12) id TAA22688; Mon, 7 Oct 1996 19:03:00 GMT Received: from meerkat.mole.org(206.197.192.110) by mole.mole.org via smap (V1.3) id sma022686; Mon Oct 7 19:02:55 1996 Received: (from mrm@localhost) by meerkat.mole.org (8.6.11/8.6.9) id MAA10966; Mon, 7 Oct 1996 12:02:34 -0700 Date: Mon, 7 Oct 1996 12:02:34 -0700 From: "M.R.Murphy" Message-Id: <199610071902.MAA10966@meerkat.mole.org> To: terry@lambert.org, wollman@lcs.mit.edu Subject: Re: I plan to change random() for -current (was Re: rand() and random()) Cc: ache@nagual.ru, bde@zeta.org.au, current@FreeBSD.org, freebsd-hackers@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > That doesn't make it any less of a valid argument. > > I would say it's more like Terry bitching like he usually does about > somebody making a piece of code act like it's supposed to on the > grounds that someone, somewhere actually depends on the bugs in it. > I for one am quite sick of your whining. > > Around here we call that attitude ``UNIX Hacker bug #78''. Is anyone else fed up with ad hominum attacks? I replied in private mail that I depend upon the current behavior of the rand48 family of functions for thermal motion studies and studies of systems of hard-shell ions. The work isn't important; it's just something I like to do and that I'm interested in. If the functions change, I can use the old ones if I need to and if I understand what I'm doing. It's my problem. I really am tired of attacks, though. Play nice, eh? -- Mike Murphy mrm@Mole.ORG +1 619 598 5874 Better is the enemy of Good From owner-freebsd-current Mon Oct 7 12:35:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA20941 for current-outgoing; Mon, 7 Oct 1996 12:35:17 -0700 (PDT) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA20936; Mon, 7 Oct 1996 12:35:13 -0700 (PDT) Received: by sovcom.kiae.su id AA18748 (5.65.kiae-1 ); Mon, 7 Oct 1996 22:27:26 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Mon, 7 Oct 96 22:27:26 +0300 Received: (from ache@localhost) by nagual.ru (8.7.6/8.7.3) id XAA04826; Mon, 7 Oct 1996 23:26:04 +0400 (MSD) Message-Id: <199610071926.XAA04826@nagual.ru> Subject: Re: I plan to change random() for -current (was Re: rand() and random()) In-Reply-To: <199610071810.LAA14432@phaeton.artisoft.com> from "Terry Lambert" at "Oct 7, 96 11:10:44 am" To: terry@lambert.org (Terry Lambert) Date: Mon, 7 Oct 1996 23:26:04 +0400 (MSD) Cc: terry@lambert.org, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org, current@FreeBSD.org, bde@zeta.org.au From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast 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-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Unless you are a mathematical programmer, you are unlikely to be > able to aprehend the consequences of even a trivial change away from > mathematical standards will have. There are verifiable standards > of correctness, and each standard dictates issues of precision to > which one can trust the code. Obviously, differences after the > significant digits can be ignored for comparison -- and are, in fact, > stripped from results as the "noise" that they are. FYI, I am applied mathematic, B.S. degree. > I suggest strict adherence to standards -- mathematical standards, > not ANSI or ISO C standards -- with regard to maintaining precision > and historical implementation, as required to ensure repeatability > and trust. Current random() code is joke from mathematical point of view (but not from ANSI/ISO standards). It is why it needs fixing. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Mon Oct 7 12:44:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA21567 for current-outgoing; Mon, 7 Oct 1996 12:44:08 -0700 (PDT) Received: from pcpsj.pfcs.com (harlan.fred.net [205.252.219.31]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA21520; Mon, 7 Oct 1996 12:44:01 -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 PAA12262; Mon, 7 Oct 1996 15:43:52 -0400 Received: from localhost by mumps.pfcs.com with SMTP id AA08063 (5.67b/IDA-1.5); Mon, 7 Oct 1996 15:43:51 -0400 To: hackers@freebsd.org, current@freebsd.org Subject: Re: random() fix explanation to avoid misunderstanding In-Reply-To: Terry's message of "Mon, 07 Oct 1996 11:27:36 PDT." <199610071827.LAA14499@phaeton.artisoft.com> Date: Mon, 07 Oct 1996 15:43:50 -0300 Message-Id: <8061.844717430@mumps.pfcs.com> From: Harlan Stenn Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry is right when he talk about needing to keep the PSEUDO-random code "golden". Jordan is right when he says that if you want repeatable results, it's best to carry your pseudo-random number code with you. If folks are going to change random.c anyway, I'd ask that either the old code be moved to a "compat" library, and/or find a way to have a per-process switch that provides a way to choose which version of the generator you're getting. H From owner-freebsd-current Mon Oct 7 13:06:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA23182 for current-outgoing; Mon, 7 Oct 1996 13:06:03 -0700 (PDT) Received: from sequent.kiae.su (sequent.kiae.su [193.125.152.6]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA23164; Mon, 7 Oct 1996 13:05:42 -0700 (PDT) Received: by sequent.kiae.su id AA23612 (5.65.kiae-2 ); Mon, 7 Oct 1996 23:38:18 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Mon, 7 Oct 96 23:38:17 +0400 Received: (from ache@localhost) by nagual.ru (8.7.6/8.7.3) id XAA04969; Mon, 7 Oct 1996 23:37:18 +0400 (MSD) Message-Id: <199610071937.XAA04969@nagual.ru> Subject: Re: I plan to change random() for -current (was Re: rand() and random()) In-Reply-To: <199610071850.LAA14614@phaeton.artisoft.com> from "Terry Lambert" at "Oct 7, 96 11:50:42 am" To: terry@lambert.org (Terry Lambert) Date: Mon, 7 Oct 1996 23:37:18 +0400 (MSD) Cc: wollman@lcs.mit.edu, terry@lambert.org, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org, current@FreeBSD.org, bde@zeta.org.au From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast 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-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Here we have an issue where the technical merit is relative: it depends > on if you depends on the "random" behaviour" or if you depends on the > "pseudo" behaviour. This is the main ideological debate. Your "pseudo" idea is technically wrong. Standard says that ([...] my comments) "THIS function [NOT all possible old and future implementations of this function] produce the same sequence for same seed". -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Mon Oct 7 13:08:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA23478 for current-outgoing; Mon, 7 Oct 1996 13:08:27 -0700 (PDT) Received: from sequent.kiae.su (sequent.kiae.su [193.125.152.6]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA23460; Mon, 7 Oct 1996 13:08:18 -0700 (PDT) Received: by sequent.kiae.su id AA23576 (5.65.kiae-2 ); Mon, 7 Oct 1996 23:38:12 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Mon, 7 Oct 96 23:38:07 +0400 Received: (from ache@localhost) by nagual.ru (8.7.6/8.7.3) id XAA04957; Mon, 7 Oct 1996 23:33:11 +0400 (MSD) Message-Id: <199610071933.XAA04957@nagual.ru> Subject: Re: I plan to change random() for -current (was Re: rand() and random()) In-Reply-To: <199610071902.MAA10966@meerkat.mole.org> from "M.R.Murphy" at "Oct 7, 96 12:02:34 pm" To: mrm@Mole.ORG (M.R.Murphy) Date: Mon, 7 Oct 1996 23:33:11 +0400 (MSD) Cc: terry@lambert.org, wollman@lcs.mit.edu, bde@zeta.org.au, current@FreeBSD.org, freebsd-hackers@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast 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-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I replied in private mail that I depend upon the current behavior > of the rand48 family of functions for thermal motion studies and > studies of systems of hard-shell ions. The work isn't important; > it's just something I like to do and that I'm interested in. If > the functions change, I can use the old ones if I need to and if > I understand what I'm doing. It's my problem. I NOT PLAN TO TOUCH rand48 CODE! -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Mon Oct 7 13:51:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA27427 for current-outgoing; Mon, 7 Oct 1996 13:51:24 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA27412; Mon, 7 Oct 1996 13:51:17 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA14959; Mon, 7 Oct 1996 13:47:25 -0700 From: Terry Lambert Message-Id: <199610072047.NAA14959@phaeton.artisoft.com> Subject: Re: I plan to change random() for -current (was Re: rand() and random()) To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Date: Mon, 7 Oct 1996 13:47:25 -0700 (MST) Cc: terry@lambert.org, wollman@lcs.mit.edu, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org, current@FreeBSD.org, bde@zeta.org.au In-Reply-To: <199610071937.XAA04969@nagual.ru> from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Oct 7, 96 11:37:18 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-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Here we have an issue where the technical merit is relative: it depends > > on if you depends on the "random" behaviour" or if you depends on the > > "pseudo" behaviour. This is the main ideological debate. > > Your "pseudo" idea is technically wrong. > Standard says that ([...] my comments) > "THIS function [NOT all possible > old and future implementations of this function] produce the > same sequence for same seed". I think you are having a semantics misunderstanding of the declarative English "this". The "this" on the manual page refers to implementation, not interface. 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-current Mon Oct 7 13:51:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA27428 for current-outgoing; Mon, 7 Oct 1996 13:51:25 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA27413; Mon, 7 Oct 1996 13:51:17 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA14940; Mon, 7 Oct 1996 13:44:15 -0700 From: Terry Lambert Message-Id: <199610072044.NAA14940@phaeton.artisoft.com> Subject: Re: I plan to change random() for -current (was Re: rand() and random()) To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Date: Mon, 7 Oct 1996 13:44:14 -0700 (MST) Cc: terry@lambert.org, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org, current@FreeBSD.org, bde@zeta.org.au In-Reply-To: <199610071926.XAA04826@nagual.ru> from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Oct 7, 96 11:26:04 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Unless you are a mathematical programmer, you are unlikely to be > > able to aprehend the consequences of even a trivial change away from > > mathematical standards will have. There are verifiable standards > > of correctness, and each standard dictates issues of precision to > > which one can trust the code. Obviously, differences after the > > significant digits can be ignored for comparison -- and are, in fact, > > stripped from results as the "noise" that they are. > > FYI, I am applied mathematic, B.S. degree. And I triple majored in high energy physics, applied mathematics, and computer science. This isn't a pissing contest. I would not be happy with *me* changing the interfaces for the same reasons I am not happy with *you* doing so. I can't trust me to be perfect any more than I can trust you to be perfect. > > I suggest strict adherence to standards -- mathematical standards, > > not ANSI or ISO C standards -- with regard to maintaining precision > > and historical implementation, as required to ensure repeatability > > and trust. > > Current random() code is joke from mathematical point of view (but not from > ANSI/ISO standards). It is why it needs fixing. All pseudo-random algoritms are cryptographically weak (as others have already pointed out). The only justification I've seen so far is the GIMP code, and it's a weak justification (you want me to carry around my own random generator, therefore I want the GIMP people to do the same). You haven't responded to the "heavily document and provide a compatability interface" compromise suggestion... how do you feel about that? It needs more work done to implement it, but it lets you achieve your goal without undue burden. See Jordan's last message... 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-current Mon Oct 7 14:00:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA28260 for current-outgoing; Mon, 7 Oct 1996 14:00:48 -0700 (PDT) Received: from citrine.cyberstation.net (hannibal@citrine.cyberstation.net [205.167.0.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA28250; Mon, 7 Oct 1996 14:00:42 -0700 (PDT) Received: from localhost (hannibal@localhost) by citrine.cyberstation.net (8.6.12/8.6.12) with SMTP id PAA11204; Mon, 7 Oct 1996 15:58:33 -0500 Date: Mon, 7 Oct 1996 15:58:33 -0500 (CDT) From: Dan Walters To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= cc: Terry Lambert , joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org, current@FreeBSD.org, bde@zeta.org.au Subject: Re: I plan to change random() for -current (was Re: rand() and random()) In-Reply-To: <199610071926.XAA04826@nagual.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I havn't played with weak symbols any, so this may not be possible. But couldn't we just make srandom() in libc weak, and make a librandom or something to that effect to override it? That way all programs that don't require the compatibility only need an extra link flag for a better distribution. Just a thought. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Dan Walters hannibal@cyberstation.net =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D On Mon, 7 Oct 1996, [KOI8-R] =E1=CE=C4=D2=C5=CA =FE=C5=D2=CE=CF=D7 wrote: > > Unless you are a mathematical programmer, you are unlikely to be > > able to aprehend the consequences of even a trivial change away from > > mathematical standards will have. There are verifiable standards > > of correctness, and each standard dictates issues of precision to > > which one can trust the code. Obviously, differences after the > > significant digits can be ignored for comparison -- and are, in fact, > > stripped from results as the "noise" that they are. >=20 > FYI, I am applied mathematic, B.S. degree. >=20 > > I suggest strict adherence to standards -- mathematical standards, > > not ANSI or ISO C standards -- with regard to maintaining precision > > and historical implementation, as required to ensure repeatability > > and trust. >=20 > Current random() code is joke from mathematical point of view (but not fr= om > ANSI/ISO standards). It is why it needs fixing. >=20 > --=20 > Andrey A. Chernov > > http://www.nagual.ru/~ache/ >=20 From owner-freebsd-current Mon Oct 7 14:19:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA29704 for current-outgoing; Mon, 7 Oct 1996 14:19:52 -0700 (PDT) Received: from sequent.kiae.su (sequent.kiae.su [193.125.152.6]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA29690; Mon, 7 Oct 1996 14:19:45 -0700 (PDT) Received: by sequent.kiae.su id AA29277 (5.65.kiae-2 ); Tue, 8 Oct 1996 01:05:29 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Tue, 8 Oct 96 01:05:26 +0400 Received: (from ache@localhost) by nagual.ru (8.7.6/8.7.3) id BAA00680; Tue, 8 Oct 1996 01:04:59 +0400 (MSD) Message-Id: <199610072104.BAA00680@nagual.ru> Subject: Re: I plan to change random() for -current (was Re: rand() and random()) In-Reply-To: <199610072044.NAA14940@phaeton.artisoft.com> from "Terry Lambert" at "Oct 7, 96 01:44:14 pm" To: terry@lambert.org (Terry Lambert) Date: Tue, 8 Oct 1996 01:04:58 +0400 (MSD) Cc: terry@lambert.org, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org, current@FreeBSD.org, bde@zeta.org.au From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast 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-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Current random() code is joke from mathematical point of view (but not from > > ANSI/ISO standards). It is why it needs fixing. > > All pseudo-random algoritms are cryptographically weak (as others have > already pointed out). The only justification I've seen so far is the > GIMP code, and it's a weak justification (you want me to carry around > my own random generator, therefore I want the GIMP people to do the same). I tired to repeat that I not consider possible weakness of random() at this point and do not attempt to make it better cryptographically or make it better random distributed. I only try to make seeding idea meaningful, because current implementation makes seeding practically useless. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Mon Oct 7 14:38:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA01458 for current-outgoing; Mon, 7 Oct 1996 14:38:54 -0700 (PDT) Received: from answerman.mindspring.com (answerman.mindspring.com [204.180.128.8]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA01452; Mon, 7 Oct 1996 14:38:48 -0700 (PDT) Received: from bogus.mindspring.com (borg.mindspring.com [204.180.128.14]) by answerman.mindspring.com (8.7.5/8.7.3) with SMTP id RAA27297; Mon, 7 Oct 1996 17:36:41 -0400 (EDT) Message-Id: <1.5.4.32.19961007213642.006c157c@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: Mon, 07 Oct 1996 17:36:42 -0400 To: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) From: "Kevin P. Neal" Subject: Re: I plan to change random() for -current (was Re: rand() and random()) Cc: terry@lambert.org (Terry Lambert), joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org, current@FreeBSD.org, bde@zeta.org.au Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk At 11:26 PM 10/7/96 +0400, Andrey A. Chernov wrote: >> Unless you are a mathematical programmer, you are unlikely to be >> able to aprehend the consequences of even a trivial change away from >> mathematical standards will have. There are verifiable standards >> of correctness, and each standard dictates issues of precision to >> which one can trust the code. Obviously, differences after the >> significant digits can be ignored for comparison -- and are, in fact, >> stripped from results as the "noise" that they are. > >FYI, I am applied mathematic, B.S. degree. > >> I suggest strict adherence to standards -- mathematical standards, >> not ANSI or ISO C standards -- with regard to maintaining precision >> and historical implementation, as required to ensure repeatability >> and trust. > >Current random() code is joke from mathematical point of view (but not from >ANSI/ISO standards). It is why it needs fixing. Wait. I feel like I'm missing something here. The pseudo-random calls are documented. They have been for a long time. They give repeatable results, cross platform, from the desk machine to the supercomputer. Physics experiments, for example, rely on the results being predictable and repeatable. Some number of people (small or large, depending on your point of view) have programs to do, for example, physics experiments. These things take *way* too long to run, and produce *way* too much raw data, so in effect the experiments are not re-runable. You keep a couple of graphs to store the results. The proposed change would break all of the above. No extremely serious need to change the system has been shown, but an extremely serious need to *NOT* change the system has been shown. An alternate system has been suggested, that would give numbers that were more random, and still not break anything. (/dev/random?) Is that about the gist of it? And how much hardware isn't supported yet, while this argument about changing something minor goes on? How many features does, for example, Linux have, while a debate about pseudo-random numbers go on? What did I miss? -- XCOMM Kevin P. Neal, Sophomore, Comp. Sci. \ kpneal@pobox.com XCOMM "Corrected!" -- Old Amiga tips file \ kpneal@eos.ncsu.edu XCOMM Visit the House of Retrocomputing: / Perm. Email: XCOMM http://www.pobox.com/~kpn/ / kevinneal@bix.com From owner-freebsd-current Mon Oct 7 16:18:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA07847 for current-outgoing; Mon, 7 Oct 1996 16:18:45 -0700 (PDT) Received: from nora.pcug.co.uk (Nora.PCUG.CO.UK [192.68.174.71]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA07837 for ; Mon, 7 Oct 1996 16:18:41 -0700 (PDT) Received: from helen.pcug.co.uk by nora.pcug.co.uk id aa26058; 8 Oct 96 0:17 BST Received: from said.org by helen.pcug.co.uk with UUCP (Exim 0.55 #4) id E0vAOvg-0001Qh-00; Tue, 8 Oct 1996 00:17:44 +0100 X-Rmail-Warning: at helen.pcug.co.uk (ibmpcug), said.org (home) gave fake domain "home.said.org" in envelope Received: (from jake@localhost) by home.said.org (8.7.6/8.7.3) id AAA05817 for current@freebsd.org; Tue, 8 Oct 1996 00:11:52 +0100 (BST) From: Jake Dias Message-Id: <199610072311.AAA05817@home.said.org> Subject: 3Com PCI 3c590 Defective Message. ENOUGH! To: current@freebsd.org Date: Tue, 8 Oct 1996 00:11:50 +0100 (BST) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, Re: vx0 driver Looking thru the mailling-list archives on www.freebsd.org I see that many people have asked about the possibly spurious error message which claims that virtually all PCI 3c590 cards are defective. Someone suggested that only a small number of early cards _really_ had this problem so the test can be removed and further that really the test is wrong anyway. This message still appears in -current for my 3c590. I would like some kind soul to help determine whether I really have a defective ROM version or whether someone with commit perms could/should simply remove that test. What's the deal with 3c590's? Thanks and regards, Jake Dias From owner-freebsd-current Mon Oct 7 16:40:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA09174 for current-outgoing; Mon, 7 Oct 1996 16:40:37 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA09122; Mon, 7 Oct 1996 16:40:25 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id JAA12712; Tue, 8 Oct 1996 09:37:50 +1000 Date: Tue, 8 Oct 1996 09:37:50 +1000 From: Bruce Evans Message-Id: <199610072337.JAA12712@godzilla.zeta.org.au> To: ache@nagual.ru, kpneal@pobox.com Subject: Re: I plan to change random() for -current (was Re: rand() and random()) Cc: bde@zeta.org.au, current@FreeBSD.org, freebsd-hackers@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de, terry@lambert.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >>Current random() code is joke from mathematical point of view (but not from >>ANSI/ISO standards). It is why it needs fixing. > >Wait. I feel like I'm missing something here. > >The pseudo-random calls are documented. They have been for a long time. > >They give repeatable results, cross platform, from the desk machine to the >supercomputer. Nope, they give results that vary across platforms and across time. 16-bit systems can't even represent the values returned by BSD rand(). >And how much hardware isn't supported yet, while this argument about >changing something minor goes on? How many features does, for example, Linux >have, while a debate about pseudo-random numbers go on? Linux has features such as a completely different, non-broken version of rand(). Bruce From owner-freebsd-current Mon Oct 7 16:59:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA10746 for current-outgoing; Mon, 7 Oct 1996 16:59:23 -0700 (PDT) Received: from jack.colorado.edu (jack.Colorado.EDU [128.138.149.29]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA10713 for ; Mon, 7 Oct 1996 16:59:16 -0700 (PDT) Received: from jack (localhost [127.0.0.1]) by jack.colorado.edu (8.7.6/8.7.3/CNS-4.0p) with SMTP id RAA20550; Mon, 7 Oct 1996 17:58:56 -0600 (MDT) Message-ID: <32599940.74B5@Colorado.EDU> Date: Mon, 07 Oct 1996 17:58:56 -0600 From: "Mark O'Lear" Organization: University of Colorado X-Mailer: Mozilla 3.0Gold (X11; I; SunOS 5.4 sun4m) MIME-Version: 1.0 To: Joerg Wunsch CC: FreeBSD-current users , andrew@why.whine.com, flaq@synwork.com, mark@hi-fi.com, Jake Hamby Subject: Re: Java,Netscape, & AccelX References: <199610061349.PAA07672@uriah.heep.sax.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > > As Jake Hamby wrote: > > > Note: If Java applets fail to display. Type this as root: > > cd /usr/X11R6/lib/X11/fonts/misc > > /usr/X11R6/bin/mkfontdir > > chmod 444 fonts.dir > > And then exit and restart your X server. > > > > I tried that, and lo and behold, it worked! It seems that Netscape needs > > particular font aliases that for some reason XFree86 didn't define > > properly. > > mkfontdir doesn't define anything new unless someone has installed new > fonts before. In the latter case however, the someone who has been > installing them is also responsible for running mkfontdir afterwards. > > Aliases are kept in fonts.alias anyway, and are not affected by > mkfontdir at all. > > All of this is kinda moot for people running font servers. (You gotta > reload the fontserver after installing the fonts.) > > -- > 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. ;-) The file /usr/X11R6/lib/X11/fonts/misc/fonts.dir is definately messed up in at least one of the XF86312[DEFGS] distributions. The /usr/X11R6/lib/X11/fonts/misc/fonts.dir file that is messed up has the following definitions, but no fonts (there may be other differences, but this is what I noticed): heb6x13.pcf.Z -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-8 heb8x13.pcf.Z -misc-fixed-medium-r-normal--13-120-75-75-c-80-iso8859-8 hanglg16.pcf.Z -daewoo-gothic-medium-r-normal--16-120-100-100-c-160-ksc5601.1987-0 hanglm16.pcf.Z -daewoo-mincho-medium-r-normal--16-120-100-100-c-160-ksc5601.1987-0 jiskan24.pcf.Z -jis-fixed-medium-r-normal--24-230-75-75-c-240-jisx0208.1983-0 hanglm24.pcf.Z -daewoo-mincho-medium-r-normal--24-170-100-100-c-240-ksc5601.1987-0 jiskan16.pcf.Z -jis-fixed-medium-r-normal--16-150-75-75-c-160-jisx0208.1983-0 k14.pcf.Z -misc-fixed-medium-r-normal--14-130-75-75-c-140-jisx0208.1983-0 gb16st.pcf.Z -isas-song ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0 gb24st.pcf.Z -isas-song ti-medium-r-normal--24-240-72-72-c-240-gb2312.1980-0 gb16fs.pcf.Z -isas-fangsong ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0 So if you can find heb6x13.pcf.Z in the file /usr/X11R6/lib/X11/fonts/misc/fonts.dir, but do not have the file /usr/X11R6/lib/X11/fonts/misc/heb6x13.pcf.Z, my guess is that java will not work for you (just a generalization, I don't actually know which font mapping is the culpret). My java was "broken" until I did the above mkfontdir sequence. You don't actually need to restart your X server though, just type 'xset fp rehash'. -- Mark O'Lear \ e-mail: Mark.Olear@Colorado.EDU University of Colorado \ phone: (303) 492-3798 Telecomm. Svcs. (CB 313) \ fax: (303) 492-5105 Boulder, CO 80309 \ From owner-freebsd-current Mon Oct 7 17:21:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA12199 for current-outgoing; Mon, 7 Oct 1996 17:21:21 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA12193 for ; Mon, 7 Oct 1996 17:21:19 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id AAA19344 for ; Tue, 8 Oct 1996 00:21:17 GMT Date: Tue, 8 Oct 1996 09:21:16 +0900 (JST) From: Michael Hancock To: current@FreeBSD.org Subject: bpatch (was Re: secure level diffs to kern_mib.c, LINT) In-Reply-To: <199610071049.UAA26363@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk What's the history of bpatch? Did we ever have one? Mike Hancock --------------- BPATCH(1) BSD Reference Manual BPATCH(1) NAME bpatch - patches a.out files, including kernel and /dev/kmem SYNOPSIS bpatch [-bcwls] [-r] [-N namelist] [-M memfile] location [value] DESCRIPTION The bpatch utility is a quick hack that allows patching of values in a.out(5) format files, including kernel or /dev/kmem for the running ker- nel. location is a symbol name, or a decimal/hex/octal number. value is the value to be stored, according to the type options. The type options specify the value type to be written: -b Specify value type as 'byte as number' -c Specify value type as 'byte as character' -w Specify value type as 'short/u_short' -l Specify value type as 'long/u_long' -s Specify value type as 'string' The -r option indicates that the running kernel is being patched rather than a.out. The -N namelist option can be used to specify the name of the kernel namelist file to be used. The -M memfile option can be used to specify the name of the memory file to be used, this implies -r. From owner-freebsd-current Mon Oct 7 18:27:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA17265 for current-outgoing; Mon, 7 Oct 1996 18:27:30 -0700 (PDT) Received: from alpo.whistle.com (s204m38.isp.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA17239; Mon, 7 Oct 1996 18:27:18 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.5/8.7.3) with SMTP id SAA22149; Mon, 7 Oct 1996 18:23:08 -0700 (PDT) Message-ID: <3259AC88.2781E494@whistle.com> Date: Mon, 07 Oct 1996 18:21:12 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: "Brian N. Handy" CC: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= , Terry Lambert , joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org, current@FreeBSD.org, Bruce Evans Subject: Re: I plan to change random() for -current (was Re: rand() and random()) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Brian N. Handy wrote: > > Hey all, > > I'm trying to stay on top of this thread and follow all the theories, and > So, following in this line of reasoning, I support fixing random(). > Brian me too. I'd like to see an option to use /dev/random too (link with -lreallyrandom) From owner-freebsd-current Mon Oct 7 18:47:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA18884 for current-outgoing; Mon, 7 Oct 1996 18:47:55 -0700 (PDT) Received: from night.primate.wisc.edu (night.primate.wisc.edu [144.92.43.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA18872 for ; Mon, 7 Oct 1996 18:47:50 -0700 (PDT) Received: by night.primate.wisc.edu; id UAA24313; 8.6.10/41.8; Mon, 7 Oct 1996 20:47:38 -0500 Message-Id: <199610080147.UAA24313@night.primate.wisc.edu> Date: Mon, 7 Oct 1996 20:47:38 -0500 From: dubois@primate.wisc.edu (Paul DuBois) To: jake@said.org (Jake Dias) Cc: current@freebsd.org Subject: Re: 3Com PCI 3c590 Defective Message. ENOUGH! In-Reply-To: <199610072311.AAA05817@home.said.org>; from Jake Dias on Oct 8, 1996 00:11:50 +0100 References: <199610072311.AAA05817@home.said.org> X-Mailer: Mutt 0.46 Mime-Version: 1.0 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jake Dias writes: > What's the deal with 3c590's? Good question. There seem to be a million questions about them here, and on the NetBSD lists. I noticed someone asking about them on the Plan 9 list this morning. Makes me really glad I have one. (On the motherboard; can't remove it :-( ) -- Paul DuBois dubois@primate.wisc.edu Home page: http://www.primate.wisc.edu/people/dubois Software: http://www.primate.wisc.edu/software From owner-freebsd-current Mon Oct 7 19:17:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA21569 for current-outgoing; Mon, 7 Oct 1996 19:17:13 -0700 (PDT) Received: from alpo.whistle.com (s204m38.isp.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA21562 for ; Mon, 7 Oct 1996 19:17:09 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.5/8.7.3) with SMTP id TAA22814 for ; Mon, 7 Oct 1996 19:15:54 -0700 (PDT) Message-ID: <3259B8E6.41C67EA6@whistle.com> Date: Mon, 07 Oct 1996 19:13:58 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: Netatalk.. anyone tried the new release? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does anyone hae any success/failure stories with teh new release? it seems to work here, but I'd like to here from anyone who has tried it with positive or negative feedback.... julian From owner-freebsd-current Mon Oct 7 19:35:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA23397 for current-outgoing; Mon, 7 Oct 1996 19:35:37 -0700 (PDT) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA23340; Mon, 7 Oct 1996 19:35:01 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.7.6/8.7.3) with SMTP id WAA03085; Mon, 7 Oct 1996 22:32:51 -0400 (EDT) Message-Id: <199610080232.WAA03085@whizzo.transsys.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Terry Lambert cc: wollman@lcs.mit.edu (Garrett Wollman), ache@nagual.ru, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org, current@FreeBSD.org, bde@zeta.org.au From: "Louis A. Mamakos" Subject: Re: I plan to change random() for -current (was Re: rand() and random()) References: <199610071850.LAA14614@phaeton.artisoft.com> In-reply-to: Your message of "Mon, 07 Oct 1996 11:50:42 PDT." <199610071850.LAA14614@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain Date: Mon, 07 Oct 1996 22:32:51 -0400 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I have to agree with Terry here about "fixing" rand()/srand(). For better or worse, there are expections on the implementation of these functions in a standard C libarary. For instance, in a recent Internet Draft of a protocol specification for multicast routing protocol (draft-ietf-idmr-pim-sm-spec-05.txt): > 3.7 Hash Function > > The hash function is used by all routers within a domain, to map > a group to one of the C-RPs from the RP-Set. For a particular > group, G, the hash function uses only those C-RPs whose Group- > prefix covers G. The algorithm takes as input the group address, > and the addresses of the Candidate RPs, and gives as output one > RP address to be used. > > The protocol requires that all routers hash to the same RP > within a domain (except for transients). The following hash > function must be used in each router: > > > 1 For each candidate RP address Ci in the Candidate-RP- > Set, whose Group-prefix covers G, compute a value: > Value(G,M,Ci) = > 1103515245 ((1103515245 (G&M)+12345) XOR Ci)+ 12345 mod 2^31 > where M is a hash-mask included in RP-Set messages. > This hash-mask allows a small number of > consecutive groups (e.g., 4) to always hash to the same RP. > For instance, hierarchically-encoded data can be sent on > consecutive group addresses to get the same delay and > fate-sharing characteristics. > > In standard C, this corresponds to: > > srand(G & M); > srand(rand() ^ Ci); > value = rand(); > > 2 The candidate with the highest resulting value is then > chosen as the RP for that group, and its identity and hash > value are stored with the entry created. > > Ties between C-RPs having the same hash value, are broken > in advantage of the highest address. > > The hash function algorithm is invoked by a DR, upon reception > of a packet, or IGMP Host-Membership-Report, for a group, for > which the DR has no entry. It is invoked by any router that has > (*,*,RP) state when a packet is received for which there is no > corresponding (S,G) or (*,G) entry. Furthermore, the hash > function is invoked by all routers upon receiving a Join/Prune > message with WC-bit set. I'm not defending the use here, but if we can avoid breaking assumptions and having an "incompatible" implementation, we ought to. If it looks like a duck, and walks like a duck, it should quack like one too. Louis Mamakos From owner-freebsd-current Mon Oct 7 20:23:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA27158 for current-outgoing; Mon, 7 Oct 1996 20:23:27 -0700 (PDT) Received: from terd.triskelion.com (root@danj.port.net [207.38.236.113]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA27152 for ; Mon, 7 Oct 1996 20:23:23 -0700 (PDT) Received: from fnur.triskelion.com (fnur.triskelion.com [180.200.1.3]) by terd.triskelion.com (8.7.5/8.6.12) with SMTP id XAA00836 for ; Mon, 7 Oct 1996 23:18:01 -0400 (EDT) Message-ID: <3259C7E9.41C67EA6@netcom.com> Date: Mon, 07 Oct 1996 23:18:01 -0400 From: Dan Janowski Organization: Triskelion Systems, Inc. X-Mailer: Mozilla 2.01 (X11; I; FreeBSD 2.1.0-RELEASE i386) MIME-Version: 1.0 To: current@freebsd.org Subject: Best mail for threaded majordomo reading? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What are you guys using? I am using netscape mail which does threading and mbox-es nicely, but it has some annoying deficiencies. What is a good way of auto-processing all the mail into separate mbox-es, i.e. put list mail somewhere different than "regular" mail? Thanks, Dan -- danj@netcom.com Dan Janowski Triskelion Systems, Inc. Bronx, NY From owner-freebsd-current Mon Oct 7 21:31:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA05340 for current-outgoing; Mon, 7 Oct 1996 21:31:54 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA05324 for ; Mon, 7 Oct 1996 21:31:47 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA01285; Mon, 7 Oct 1996 22:30:59 -0600 (MDT) Date: Mon, 7 Oct 1996 22:30:59 -0600 (MDT) Message-Id: <199610080430.WAA01285@rocky.mt.sri.com> From: Nate Williams To: Dan Janowski Cc: current@freebsd.org Subject: Re: Best mail for threaded majordomo reading? In-Reply-To: <3259C7E9.41C67EA6@netcom.com> References: <3259C7E9.41C67EA6@netcom.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > What are you guys using? I am using netscape > mail which does threading and mbox-es nicely, but > it has some annoying deficiencies. I use XEmacs + VM, which works very well for me. > What is a > good way of auto-processing all the mail into > separate mbox-es, i.e. put list mail somewhere > different than "regular" mail? The port of procmail works great. Both VM and procmail work together well, although you need to make sure you dump your email into the spool folder and *NOT* the read folders. Nate From owner-freebsd-current Mon Oct 7 23:12:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA19016 for current-outgoing; Mon, 7 Oct 1996 23:12:35 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA19006 for ; Mon, 7 Oct 1996 23:12:32 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id IAA02125 for ; Tue, 8 Oct 1996 08:11:59 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id IAA07484 for current@FreeBSD.org; Tue, 8 Oct 1996 08:12:13 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.0/keltia-uucp-2.9) id HAA15379; Tue, 8 Oct 1996 07:39:53 +0200 (MET DST) Message-Id: <199610080539.HAA15379@keltia.freenix.fr> Date: Tue, 8 Oct 1996 07:39:53 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: current@FreeBSD.org Subject: Re: Best mail for threaded majordomo reading? In-Reply-To: <3259C7E9.41C67EA6@netcom.com>; from Dan Janowski on Oct 7, 1996 23:18:01 -0400 References: <3259C7E9.41C67EA6@netcom.com> X-Mailer: Mutt 0.46-n Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-CURRENT ctm#2522 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk According to Dan Janowski: > What are you guys using? I am using netscape > mail which does threading and mbox-es nicely, but > it has some annoying deficiencies. What is a > good way of auto-processing all the mail into > separate mbox-es, i.e. put list mail somewhere > different than "regular" mail? Don't look any further: 1. procmail (see /usr/ports/mail/procmail) will dispatch your mail in various mailboxes (I can send you privately my procmail entries for the FreeBSD lists) ; 2. Mutt[1] will enable you to real mail with threads (as I do) nicely. It has very good PGP and MIME support. It is not an X11 program though. [1] -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #23: Sun Sep 29 14:56:23 MET DST 1996 From owner-freebsd-current Mon Oct 7 23:15:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA19459 for current-outgoing; Mon, 7 Oct 1996 23:15:18 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA19408; Mon, 7 Oct 1996 23:15:08 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id IAA03073; Tue, 8 Oct 1996 08:14:14 +0200 (MET DST) To: "M.R.Murphy" cc: terry@lambert.org, wollman@lcs.mit.edu, ache@nagual.ru, bde@zeta.org.au, current@FreeBSD.org, freebsd-hackers@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de Subject: Re: I plan to change random() for -current (was Re: rand() and random()) In-reply-to: Your message of "Mon, 07 Oct 1996 12:02:34 PDT." <199610071902.MAA10966@meerkat.mole.org> Date: Tue, 08 Oct 1996 08:14:14 +0200 Message-ID: <3071.844755254@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <199610071902.MAA10966@meerkat.mole.org>, "M.R.Murphy" writes: >Is anyone else fed up with ad hominum attacks? yes. But I'm also tired of Terry blowing things WAY out of proportion. Nobody has even thought about tinkering with rand48. Nobody needing serious random numbers uses rand(). -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Mon Oct 7 23:35:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA22445 for current-outgoing; Mon, 7 Oct 1996 23:35:54 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA22428 for ; Mon, 7 Oct 1996 23:35:50 -0700 (PDT) Received: from spirit.ki.net (root@spirit.ki.net [205.150.102.51]) by quagmire.ki.net (8.7.5/8.7.5) with ESMTP id CAA18516 for ; Tue, 8 Oct 1996 02:35:53 -0400 (EDT) Received: from localhost (scrappy@localhost) by spirit.ki.net (8.7.5/8.7.3) with SMTP id CAA18284 for ; Tue, 8 Oct 1996 02:35:45 -0400 (EDT) X-Authentication-Warning: spirit.ki.net: scrappy owned process doing -bs Date: Tue, 8 Oct 1996 02:35:40 -0400 (EDT) From: "Marc G. Fournier" To: current@freebsd.org Subject: make fails on libg++ Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Morning... I've tried just about everything that Icna think of, including re-sup'ng in the source code and I can't seem to get past libg++ :( I'm going to keep plugging away at it, hoping I'll stumble across something i've missed...but if anyone knows the solution to this one, I'm all ears...thanks in advance... ===> libg++ building shared g++ library (version 4.0) String.so: Definition of symbol `_NPOS' (multiply defined) String.so: Size element definition of symbol `_NPOS' (multiply defined) Regex.so: Definition of symbol `_NPOS' (multiply defined) Regex.so: Size element definition of symbol `_NPOS' (multiply defined) Fix.so: Definition of symbol `_NPOS' (multiply defined) Fix.so: Size element definition of symbol `_NPOS' (multiply defined) BitString.so: Definition of symbol `_NPOS' (multiply defined) BitString.so: Size element definition of symbol `_NPOS' (multiply defined) BitSet.so: Definition of symbol `_NPOS' (multiply defined) BitSet.so: Size element definition of symbol `_NPOS' (multiply defined) Obstack.so: Definition of symbol `_NPOS' (multiply defined) Obstack.so: Size element definition of symbol `_NPOS' (multiply defined) Integer.so: Definition of symbol `_NPOS' (multiply defined) Integer.so: Size element definition of symbol `_NPOS' (multiply defined) AllocRing.so: Definition of symbol `_NPOS' (multiply defined) AllocRing.so: Size element definition of symbol `_NPOS' (multiply defined) *** Error code 1 Stop. *** Error code 1 Stop. Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Tue Oct 8 00:23:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA01576 for current-outgoing; Tue, 8 Oct 1996 00:23:33 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA01520; Tue, 8 Oct 1996 00:23:16 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id RAA26125; Tue, 8 Oct 1996 17:12:06 +1000 Date: Tue, 8 Oct 1996 17:12:06 +1000 From: Bruce Evans Message-Id: <199610080712.RAA26125@godzilla.zeta.org.au> To: mrm@Mole.ORG, phk@critter.tfs.com Subject: Re: I plan to change random() for -current (was Re: rand() and random()) Cc: ache@nagual.ru, bde@zeta.org.au, current@FreeBSD.org, freebsd-hackers@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de, terry@lambert.org, wollman@lcs.mit.edu Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Nobody has even thought about tinkering with rand48. Well, I have thought of checking if it is related to the old BSD rand48 :-). rand48 isn't in BSD4.4Lite or BSDI. FreeBSD has a contributed version. Bruce From owner-freebsd-current Tue Oct 8 00:55:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA05677 for current-outgoing; Tue, 8 Oct 1996 00:55:56 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA05669 for ; Tue, 8 Oct 1996 00:55:54 -0700 (PDT) Received: from irz301.inf.tu-dresden.de by mail.crl.com with SMTP id AA23615 (5.65c/IDA-1.5 for ); Tue, 8 Oct 1996 00:56:48 -0700 Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA28816 for ; Tue, 8 Oct 1996 09:53:16 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA23373 for freebsd-current@FreeBSD.org; Tue, 8 Oct 1996 09:53:16 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id JAA19647 for freebsd-current@FreeBSD.org; Tue, 8 Oct 1996 09:46:07 +0200 (MET DST) From: J Wunsch Message-Id: <199610080746.JAA19647@uriah.heep.sax.de> Subject: Re: Java,Netscape, & AccelX To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 8 Oct 1996 09:46:07 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <32599940.74B5@Colorado.EDU> from Mark O'Lear at "Oct 7, 96 05:58:56 pm" X-Phone: +49-351-2012 669 X-Pgp-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Mark O'Lear wrote: > The file /usr/X11R6/lib/X11/fonts/misc/fonts.dir is definately > messed up in at least one of the XF86312[DEFGS] distributions. > The /usr/X11R6/lib/X11/fonts/misc/fonts.dir file that is messed > up has the following definitions, but no fonts (there may be other > differences, but this is what I noticed): > > heb6x13.pcf.Z > -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-8 > heb8x13.pcf.Z -misc-fixed-medium-r-normal--13-120-75-75-c-80-iso8859-8 > hanglg16.pcf.Z Ah, i realize what's your problem: you haven't installed all the fonts that come with the distribution (some large fonts have been broken out). So yes, this is a reason where the installation script should always finally run a `mkfontdir' there. Jordan? (The distribution itself cannot fix this, since it is not known beforehand which font packages the user is going to install.) -- 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-current Tue Oct 8 00:58:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA06034 for current-outgoing; Tue, 8 Oct 1996 00:58:48 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA06026 for ; Tue, 8 Oct 1996 00:58:43 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA28812; Tue, 8 Oct 1996 09:53:13 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA23372; Tue, 8 Oct 1996 09:53:13 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id JAA19626; Tue, 8 Oct 1996 09:43:27 +0200 (MET DST) From: J Wunsch Message-Id: <199610080743.JAA19626@uriah.heep.sax.de> Subject: Re: 3Com PCI 3c590 Defective Message. ENOUGH! To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 8 Oct 1996 09:43:27 +0200 (MET DST) Cc: jake@said.org (Jake Dias) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199610072311.AAA05817@home.said.org> from Jake Dias at "Oct 8, 96 00:11:50 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Jake Dias wrote: > Someone suggested that only a small number of early cards _really_ had this > problem so the test can be removed and further that really the test is > wrong anyway. No, it should not go away. 3Com explicitly requests all driver writers to issue a message of this kind if they detect the broken adapter, since there's no usable software workaround. However, somebody should fix the test so that only broken cards actually emit the message. ;-) -- 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-current Tue Oct 8 00:59:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA06138 for current-outgoing; Tue, 8 Oct 1996 00:59:30 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA06131 for ; Tue, 8 Oct 1996 00:59:29 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id AAA07824 for ; Tue, 8 Oct 1996 00:59:27 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA28807 for ; Tue, 8 Oct 1996 09:53:12 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA23371 for freebsd-current@FreeBSD.org; Tue, 8 Oct 1996 09:53:11 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id JAA19572 for freebsd-current@FreeBSD.org; Tue, 8 Oct 1996 09:40:10 +0200 (MET DST) From: J Wunsch Message-Id: <199610080740.JAA19572@uriah.heep.sax.de> Subject: Re: bpatch (was Re: secure level diffs to kern_mib.c, LINT) To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 8 Oct 1996 09:40:10 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Michael Hancock at "Oct 8, 96 09:21:16 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Michael Hancock wrote: > What's the history of bpatch? Did we ever have one? There's already another bpatch in the ports. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Oct 8 01:04:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA06811 for current-outgoing; Tue, 8 Oct 1996 01:04:00 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA06773; Tue, 8 Oct 1996 01:03:51 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id RAA27388; Tue, 8 Oct 1996 17:56:32 +1000 Date: Tue, 8 Oct 1996 17:56:32 +1000 From: Bruce Evans Message-Id: <199610080756.RAA27388@godzilla.zeta.org.au> To: louie@TransSys.COM, terry@lambert.org Subject: Re: I plan to change random() for -current (was Re: rand() and random()) Cc: ache@nagual.ru, bde@zeta.org.au, current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, joerg_wunsch@uriah.heep.sax.de, wollman@lcs.mit.edu Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I have to agree with Terry here about "fixing" rand()/srand(). For >better or worse, there are expections on the implementation of these >functions in a standard C libarary. For instance, in a recent >Internet Draft of a protocol specification for multicast routing >protocol (draft-ietf-idmr-pim-sm-spec-05.txt): >> 3.7 Hash Function >>.... >> 1 For each candidate RP address Ci in the Candidate-RP- >> Set, whose Group-prefix covers G, compute a value: >> Value(G,M,Ci) = >> 1103515245 ((1103515245 (G&M)+12345) XOR Ci)+ 12345 mod 2^31 If you want exactly that, use your own routine. Apparently a quality hash function isn't required. >> In standard C, this corresponds to: ^^^^^^^^^^ the usual (low quality) BSD implementation of the Standard C library functions srand() and rand() >> >> srand(G & M); >> srand(rand() ^ Ci); >> value = rand(); Bruce From owner-freebsd-current Tue Oct 8 02:09:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA10955 for current-outgoing; Tue, 8 Oct 1996 02:09:47 -0700 (PDT) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA10946 for ; Tue, 8 Oct 1996 02:09:41 -0700 (PDT) Received: by sovcom.kiae.su id AA12489 (5.65.kiae-1 for current@freebsd.org); Tue, 8 Oct 1996 12:08:03 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Tue, 8 Oct 96 12:08:02 +0300 Received: (from ache@localhost) by nagual.ru (8.7.6/8.7.3) id NAA00842 for current@freebsd.org; Tue, 8 Oct 1996 13:06:00 +0400 (MSD) Message-Id: <199610080906.NAA00842@nagual.ru> Subject: Round #2 random() fix for review To: current@freebsd.org (FreeBSD-current) Date: Tue, 8 Oct 1996 13:05:59 +0400 (MSD) From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk *** random.c.orig Sat Oct 5 20:41:57 1996 --- random.c Tue Oct 8 12:08:24 1996 *************** *** 122,128 **** /* * Initially, everything is set up as if from: * ! * initstate(1, &randtbl, 128); * * Note that this initialization takes advantage of the fact that srandom() * advances the front and rear pointers 10*rand_deg times, and hence the --- 122,128 ---- /* * Initially, everything is set up as if from: * ! * initstate(1, randtbl, 128); * * Note that this initialization takes advantage of the fact that srandom() * advances the front and rear pointers 10*rand_deg times, and hence the *************** *** 135,146 **** static long randtbl[DEG_3 + 1] = { TYPE_3, 0x9a319039, 0x32d9c024, 0x9b663182, 0x5da1f342, 0xde3b81e0, 0xdf0a6fb5, 0xf103bc02, 0x48f340fb, 0x7449e56b, 0xbeb1dbb0, 0xab5c5918, 0x946554fd, 0x8c2e680f, 0xeb3d799f, 0xb11ee0b7, 0x2d436b86, 0xda672e2a, 0x1588ca88, 0xe369735d, 0x904f35f7, 0xd7158fd6, 0x6fa6f051, 0x616e6b96, 0xac94efdc, 0x36413f93, 0xc622c298, 0xf5a42ab8, 0x8a88d77b, 0xf5ad9d0e, 0x8999220b, ! 0x27fb47b9, }; /* --- 135,157 ---- static long randtbl[DEG_3 + 1] = { TYPE_3, + #ifndef USE_WEAK_SEEDING + 0x991539b1, 0x16a5bce3, 0x6774a4cd, 0x3e01511e, 0x4e508aaa, 0x61048c05, + 0xf5500617, 0x846b7115, 0x6a19892c, 0x896a97af, 0xdb48f936, 0x14898454, + 0x37ffd106, 0xb58bff9c, 0x59e17104, 0xcf918a49, 0x09378c83, 0x52c7a471, + 0x8d293ea9, 0x1f4fc301, 0xc3db71be, 0x39b44e1c, 0xf8a44ef9, 0x4c8b80b1, + 0x19edc328, 0x87bf4bdd, 0xc9b240e5, 0xe9ee4b1b, 0x4382aee7, 0x535b6b41, + 0xf3bec5da + #else /* USE_WEAK_SEEDING */ + /* Historic implementation compatibility */ + /* The random sequences do not vary much with the seed */ 0x9a319039, 0x32d9c024, 0x9b663182, 0x5da1f342, 0xde3b81e0, 0xdf0a6fb5, 0xf103bc02, 0x48f340fb, 0x7449e56b, 0xbeb1dbb0, 0xab5c5918, 0x946554fd, 0x8c2e680f, 0xeb3d799f, 0xb11ee0b7, 0x2d436b86, 0xda672e2a, 0x1588ca88, 0xe369735d, 0x904f35f7, 0xd7158fd6, 0x6fa6f051, 0x616e6b96, 0xac94efdc, 0x36413f93, 0xc622c298, 0xf5a42ab8, 0x8a88d77b, 0xf5ad9d0e, 0x8999220b, ! 0x27fb47b9 ! #endif /* USE_WEAK_SEEDING */ }; /* *************** *** 176,181 **** --- 187,221 ---- static int rand_sep = SEP_3; static long *end_ptr = &randtbl[DEG_3 + 1]; + static inline long good_rand __P((long)); + + static inline long good_rand (x) + register long x; + { + #ifndef USE_WEAK_SEEDING + /* + * Compute x = (7^5 * x) mod (2^31 - 1) + * wihout overflowing 31 bits: + * (2^31 - 1) = 127773 * (7^5) + 2836 + * From "Random number generators: good ones are hard to find", + * Park and Miller, Communications of the ACM, vol. 31, no. 10, + * October 1988, p. 1195. + */ + register long hi, lo; + + hi = x / 127773; + lo = x % 127773; + x = 16807 * lo - 2836 * hi; + if (x <= 0) + x += 0x7fffffff; + return (x); + #else /* USE_WEAK_SEEDING */ + /* Historic implementation compatibility */ + /* The random sequences do not vary much with the seed */ + return (1103515245 * x + 12345); + #endif /* USE_WEAK_SEEDING */ + } + /* * srandom: * *************** *** 192,206 **** srandom(x) unsigned int x; { ! register int i, j; if (rand_type == TYPE_0) state[0] = x; else { - j = 1; state[0] = x; for (i = 1; i < rand_deg; i++) ! state[i] = 1103515245 * state[i - 1] + 12345; fptr = &state[rand_sep]; rptr = &state[0]; for (i = 0; i < 10 * rand_deg; i++) --- 232,245 ---- srandom(x) unsigned int x; { ! register int i; if (rand_type == TYPE_0) state[0] = x; else { state[0] = x; for (i = 1; i < rand_deg; i++) ! state[i] = good_rand(state[i - 1]); fptr = &state[rand_sep]; rptr = &state[0]; for (i = 0; i < 10 * rand_deg; i++) *************** *** 349,355 **** long i; if (rand_type == TYPE_0) ! i = state[0] = (state[0] * 1103515245 + 12345) & 0x7fffffff; else { *fptr += *rptr; i = (*fptr >> 1) & 0x7fffffff; /* chucking least random bit */ --- 388,394 ---- long i; if (rand_type == TYPE_0) ! i = state[0] = good_rand(state[0]) & 0x7fffffff; else { *fptr += *rptr; i = (*fptr >> 1) & 0x7fffffff; /* chucking least random bit */ *** random.3.orig Tue Oct 8 12:49:59 1996 --- random.3 Tue Oct 8 12:58:48 1996 *************** *** 82,96 **** will produce a random binary value. .Pp ! Unlike ! .Xr srand , ! .Fn srandom ! does not return the old seed; the reason for this is that the amount of ! state information used is much more than a single word. (Two other ! routines are provided to deal with restarting/changing random ! number generators). Like .Xr rand 3 , - however, .Fn random will by default produce a sequence of numbers that can be duplicated by calling --- 82,89 ---- will produce a random binary value. .Pp ! Like .Xr rand 3 , .Fn random will by default produce a sequence of numbers that can be duplicated by calling *************** *** 161,171 **** detects that the state information has been garbled, error messages are printed on the standard error output. .Sh SEE ALSO ! .Xr rand 3 .Sh HISTORY These functions appeared in .Bx 4.2 . .Sh BUGS About 2/3 the speed of .Xr rand 3 . --- 154,171 ---- detects that the state information has been garbled, error messages are printed on the standard error output. .Sh SEE ALSO ! .Xr rand 3 , ! .Xr srand 3 .Sh HISTORY These functions appeared in .Bx 4.2 . .Sh BUGS + .Pp About 2/3 the speed of .Xr rand 3 . + .Pp + Original implementation changed to fix seeding weakness problem: + the random sequences do not vary much with the seed. Now + better pseudo-random number generator used for initial state + calculation. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Tue Oct 8 02:36:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA12196 for current-outgoing; Tue, 8 Oct 1996 02:36:13 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA12039; Tue, 8 Oct 1996 02:32:04 -0700 (PDT) Received: (from narvi@localhost) by haldjas.folklore.ee (8.7.5/8.6.12) id MAA12042; Tue, 8 Oct 1996 12:26:45 +0300 (EET DST) Date: Tue, 8 Oct 1996 12:26:44 +0300 (EET DST) From: Narvi To: Harlan Stenn cc: hackers@freebsd.org, current@freebsd.org Subject: Re: random() fix explanation to avoid misunderstanding In-Reply-To: <8061.844717430@mumps.pfcs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 7 Oct 1996, Harlan Stenn wrote: > Terry is right when he talk about needing to keep the PSEUDO-random code > "golden". > > Jordan is right when he says that if you want repeatable results, it's > best to carry your pseudo-random number code with you. > > If folks are going to change random.c anyway, I'd ask that either the > old code be moved to a "compat" library, and/or find a way to have a > per-process switch that provides a way to choose which version of the > generator you're getting. Wouldn't just an environment variable (USE_OLD_RANDOM) do the job? Most people will not have it defined. For those who will need it, define it in the manual page for random. Yes - it does increase the code size (=bloats it) but is there any other way - as noted already, majority does not (or does not in some time in the near future) need the old code. The minority could just have it set in .login? Sander > > H > From owner-freebsd-current Tue Oct 8 03:01:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA14575 for current-outgoing; Tue, 8 Oct 1996 03:01:15 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA14560; Tue, 8 Oct 1996 03:01:06 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id KAA13700; Tue, 8 Oct 1996 10:58:23 +0100 Date: Tue, 8 Oct 1996 10:58:22 +0100 (BST) From: Doug Rabson To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= cc: Terry Lambert , joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org, current@FreeBSD.org, bde@zeta.org.au Subject: Re: I plan to change random() for -current (was Re: rand() and random()) In-Reply-To: <199610072104.BAA00680@nagual.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 8 Oct 1996, [KOI8-R] =E1=CE=C4=D2=C5=CA =FE=C5=D2=CE=CF=D7 wrote: > > > Current random() code is joke from mathematical point of view (but no= t from > > > ANSI/ISO standards). It is why it needs fixing. > >=20 > > All pseudo-random algoritms are cryptographically weak (as others have > > already pointed out). The only justification I've seen so far is the > > GIMP code, and it's a weak justification (you want me to carry around > > my own random generator, therefore I want the GIMP people to do the sam= e). >=20 > I tired to repeat that I not consider possible weakness of random() at th= is > point and do not attempt to make it better cryptographically or make > it better random distributed. I only try to make seeding idea meaningful, > because current implementation makes seeding practically useless. This whole discussion is pointless and tiring to read. If you really care about seeding random() with repeatable values, use initstate(). It is probably trivial to figure out a set of values to give to initstate() for any value which you are currently giving to srandom(). Since the proposed change will *not* affect random() at all, you will get the exact same requence of numbers. -- Doug Rabson, Microsoft RenderMorphics Ltd.=09Mail: dfr@render.com =09=09=09=09=09=09Phone: +44 171 734 3761 =09=09=09=09=09=09FAX: +44 171 734 6426 From owner-freebsd-current Tue Oct 8 03:33:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA17224 for current-outgoing; Tue, 8 Oct 1996 03:33:13 -0700 (PDT) Received: from pillar.elsevier.co.uk (root@pillar.elsevier.co.uk [193.131.222.35]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA17216 for ; Tue, 8 Oct 1996 03:33:06 -0700 (PDT) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by pillar.elsevier.co.uk (8.8.0/8.8.0) with ESMTP id LAA16830 for ; Tue, 8 Oct 1996 11:30:19 +0100 (BST) Received: from cadair.elsevier.co.uk by snowdon.elsevier.co.uk with SMTP (PP); Tue, 8 Oct 1996 11:32:31 +0100 Received: from tees.elsevier.co.uk (tees.elsevier.co.uk [193.131.197.60]) by cadair.elsevier.co.uk (8.8.0/8.8.0) with ESMTP id LAA15305; Tue, 8 Oct 1996 11:32:25 +0100 (BST) Received: (from dpr@localhost) by tees.elsevier.co.uk (8.8.0/8.8.0) id LAA06144; Tue, 8 Oct 1996 11:31:28 +0100 (BST) To: Jake Hamby Cc: current@FreeBSD.org Subject: Re: Wow, CVSup is cool! References: From: Paul Richards Date: 08 Oct 1996 11:31:27 +0100 In-Reply-To: Jake Hamby's message of Fri, 4 Oct 1996 13:50:53 -0700 (PDT) Message-ID: <57ohidg328.fsf@tees.elsevier.co.uk> Lines: 35 X-Mailer: Gnus v5.3/Emacs 19.30 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jake Hamby writes: > > After complaining about some problems I had with sup4.freebsd.org (it > repeatedly fetched large chunks of contrib even though nothing, other than > the datestamp, had changed!), I decided to try out CVSup, even though it > involves installing the 5MB Modula-3 package first. I was _very_ > impressed! My favorite features: I switched from sup to ctm some time ago and ctm is more appropriate for my modem link but last night, after a mail gateway disaster, I was forced to grab some ctm deltas by hand and it occured to me that a supscan of the deltas directory would be usefull so that when something does get badly spammed in your delta directory (assuming you archive them all which I do) then you can run sup as a one off to repair/retrieve missing delta files. It would mean having a slightly different structure to the delta directory layout in that when a new base delta is started it should be in in a separate directory. Otherwise, running sup across the whole lot would download all the base deltas that wouldn't be needed. My desire for this is that I needed to go out and got caught up trying to determine which deltas were missing and getting odd files one at a time. I really wanted some mechanism that I could just leave running while I was out that knew to grab the missing/damaged files. Sup was actually quite good at that function and as a one off recovery mechanism would still be useful. Anyone else think this would be useful? -- Paul Richards. Originative Solutions Ltd. (Netcraft Ltd. contractor) Elsevier Science TIS online journal project. Email: p.richards@elsevier.co.uk Phone: 0370 462071 (Mobile), +44 (0)1865 843155 From owner-freebsd-current Tue Oct 8 04:20:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA19930 for current-outgoing; Tue, 8 Oct 1996 04:20:37 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA19921; Tue, 8 Oct 1996 04:20:33 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id NAA04297; Tue, 8 Oct 1996 13:20:02 +0200 (MET DST) To: Paul Richards cc: Jake Hamby , current@FreeBSD.org Subject: Re: Wow, CVSup is cool! In-reply-to: Your message of "08 Oct 1996 11:31:27 BST." <57ohidg328.fsf@tees.elsevier.co.uk> Date: Tue, 08 Oct 1996 13:20:01 +0200 Message-ID: <4295.844773601@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <57ohidg328.fsf@tees.elsevier.co.uk>, Paul Richards writes: >I switched from sup to ctm some time ago and ctm is more appropriate >for my modem link but last night, after a mail gateway disaster, I was This is what I do: #!/bin/sh set -e cd /home/ncvs set `cat .ctm_status` old=foo this=$2 while [ $old != $2 ] do next=`expr $this + 1` ( cd /tmp && fetch -q ftp://freebsd.org/pub/CTM/cvs-cur/cvs-cur.${next}.gz) if [ -f /tmp/cvs-cur.*${next}.gz ] ; then ctm -v /tmp/cvs-cur.*${next}.gz mv /tmp/cvs-cur.*${next}.gz /home/CTM old=$this set `cat .ctm_status` this=$2 else break fi done -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Tue Oct 8 04:37:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA20672 for current-outgoing; Tue, 8 Oct 1996 04:37:09 -0700 (PDT) Received: from eel.dataplex.net (eel.dataplex.net [208.2.87.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA20665 for ; Tue, 8 Oct 1996 04:37:06 -0700 (PDT) Received: from [208.2.87.4] (cod [208.2.87.4]) by eel.dataplex.net (8.7.5/8.7.3) with ESMTP id GAA08613; Tue, 8 Oct 1996 06:35:38 -0500 (CDT) X-Sender: rkw@eel.dataplex.net Message-Id: In-Reply-To: <57ohidg328.fsf@tees.elsevier.co.uk> References: Jake Hamby's message of Fri, 4 Oct 1996 13:50:53 -0700 (PDT) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 8 Oct 1996 06:34:23 -0500 To: Paul Richards From: Richard Wackerbarth Subject: Re: Wow, CVSup is cool! Cc: current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >My desire for this is that I needed to go out and got caught up trying >to determine which deltas were missing and getting odd files one at a >time. I really wanted some mechanism that I could just leave running >while I was out that knew to grab the missing/damaged files. Sup was >actually quite good at that function and as a one off recovery >mechanism would still be useful. > >Anyone else think this would be useful? Since this is an infrequent use, it is not worthwhile to support it with a mechanism as heavy as sup. I suggest that you use "mirror" for this. By setting the appropriate include/exclude rules, you get just the files that you want. In my own case, I do not get every base delta. It is "cheaper" for me to simply keep a few more files to carry me back to an earlier delta. What I would like to see is coordination between the sup disptibutions and the ctm distributions so that you can seamlessly use sup to "fix" a tree and ctm to routinely update it, or vise versa. From owner-freebsd-current Tue Oct 8 05:35:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA23022 for current-outgoing; Tue, 8 Oct 1996 05:35:41 -0700 (PDT) Received: from nol.net (root@dazed.nol.net [206.126.32.101]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA23017 for ; Tue, 8 Oct 1996 05:35:39 -0700 (PDT) Received: from dazed.nol.net (blh@dazed.nol.net [206.126.32.101]) by nol.net (8.8.0/NOL - 8.*) with SMTP id HAA03473 for ; Tue, 8 Oct 1996 07:35:33 -0500 (CDT) X-AUTH: NOLNET SENDMAIL AUTH Date: Tue, 8 Oct 1996 07:35:32 -0500 (CDT) From: "Brett L. Hawn" To: current@freebsd.org Subject: ok, look folks Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've asked nicely, I've sent some 30-40 messages to the majordomo server and the owner of the list. Now... I'm going to try one more 'nice' method before I just get overly pissed off and find my own way to do it: SOMEONE TAKE ME OFF THE *&^%ING LISTS I subscribed to -current, -hackers, and -questions some time ago, and it was fun.. but right now I don't have time for it and majordomo being the piece of crap it is now says I'm not on the lists.. but yet I get some 40+ emails a day from them.. go figure. All I ask is that someone get me off the *&^%ing lists, I've emailed majordomo-owner, owner-majordomo, root@freebsd.org, and admin@freebsd.org, now I'm tired. [-] Brett L. Hawn (blh@nol.net) [-] [-] Networks On-Line - Houston, Texas [-] [-] 713-467-7100 [-] From owner-freebsd-current Tue Oct 8 06:27:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA26285 for current-outgoing; Tue, 8 Oct 1996 06:27:26 -0700 (PDT) Received: from central.picker.com (central.picker.com [144.54.31.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA26279 for ; Tue, 8 Oct 1996 06:27:24 -0700 (PDT) Received: from ct.picker.com by central.picker.com with smtp (Smail3.1.28.1 #3) id m0vAc44-0004sXC; Tue, 8 Oct 96 09:19 EDT Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA21288; Tue, 8 Oct 96 09:17:19 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id JAA29803; Tue, 8 Oct 1996 09:10:59 -0400 From: rhh@ct.picker.com (Randall Hopper) Message-Id: <199610081310.JAA29803@elmer.ct.picker.com> Subject: Re: Best mail for threaded majordomo reading? To: current@freebsd.org Date: Tue, 8 Oct 1996 09:10:59 -0400 (EDT) Reply-To: rhh@ct.picker.com Organization: Picker International, CT Division X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ollivier Robert: |According to Dan Janowski: |> What are you guys using? I am using netscape |> mail which does threading and mbox-es nicely, but |> it has some annoying deficiencies. What is a |> good way of auto-processing all the mail into |> separate mbox-es, i.e. put list mail somewhere |> different than "regular" mail? | |Don't look any further: | |1. procmail (see /usr/ports/mail/procmail) will dispatch your mail in | various mailboxes (I can send you privately my procmail entries for the | FreeBSD lists) ; | |2. Mutt[1] will enable you to real mail with threads (as I do) nicely. It | has very good PGP and MIME support. | It is not an X11 program though. To throw my 2 cents in... I'm using ELM's filter instead of procmail. Much nicer filter file syntax, through procmails is more flexible. procmail is more stable as well -- will probably convert over to that when we upgrade out mail machine here. Using ELM to read threaded mail. Just change the sort order to By Subject whenever I pull up one of my freebsd mail folders (e.g =fbsdcurr.ml.new), but it works fine. Will eventually convert to mutt -- lots of nice features (color highlighting, better MIME attachments, better PGP support, etc.). Was somewhat unstable though when I tried it a few weeks back, but its coming along fast. Randall Hopper rhh@ct.picker.com From owner-freebsd-current Tue Oct 8 06:54:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA27515 for current-outgoing; Tue, 8 Oct 1996 06:54:59 -0700 (PDT) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA27509; Tue, 8 Oct 1996 06:54:57 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199610081354.GAA27509@freefall.freebsd.org> Subject: Re: ok, look folks To: blh@nol.net (Brett L. Hawn) Date: Tue, 8 Oct 1996 06:54:57 -0700 (PDT) Cc: current@freebsd.org In-Reply-To: from "Brett L. Hawn" at Oct 8, 96 07:35:32 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk i have unsubscribed you from the FreeBSD mailing lists Brett L. Hawn wrote: > > I've asked nicely, I've sent some 30-40 messages to the majordomo server and > the owner of the list. Now... I'm going to try one more 'nice' method before why didnt you send mail to the postmaster? thats the easiest way of resolving mail problems that you cant not fix yourself. > I just get overly pissed off and find my own way to do it: > > SOMEONE TAKE ME OFF THE *&^%ING LISTS you are subscribed as blh@dazed.nol.net blh@nol.net != blh@dazed.nol.net had you sent a request using the correcty address you would not have had a problem. echo "unsubscribe freebsd-questions" | mail majordomo@freebsd.org what could have been simpler? > I subscribed to -current, -hackers, and -questions some time ago, and it was > fun.. but right now I don't have time for it and majordomo being the piece > of crap it is now says I'm not on the lists.. but yet I get some 40+ emails > a day from them.. go figure. All I ask is that someone get me off the > *&^%ing lists, I've emailed majordomo-owner, owner-majordomo, > root@freebsd.org, and admin@freebsd.org, now I'm tired. > > > [-] Brett L. Hawn (blh@nol.net) [-] > [-] Networks On-Line - Houston, Texas [-] > [-] 713-467-7100 [-] jmb -- Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG FreeBSD--4.4BSD Unix for PC clones, source included. http://www.freebsd.org/ PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB From owner-freebsd-current Tue Oct 8 07:22:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA28706 for current-outgoing; Tue, 8 Oct 1996 07:22:25 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA28699 for ; Tue, 8 Oct 1996 07:22:22 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65v3.2/1.1.8.2/19Aug95-0530PM) id AA13255; Tue, 8 Oct 1996 10:22:20 -0400 Date: Tue, 8 Oct 1996 10:22:20 -0400 From: Garrett Wollman Message-Id: <9610081422.AA13255@halloran-eldar.lcs.mit.edu> To: "Brett L. Hawn" Cc: current@freebsd.org Subject: ok, look folks In-Reply-To: References: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: > I've asked nicely, I've sent some 30-40 messages to the majordomo server and > the owner of the list. Now... I'm going to try one more 'nice' method before > I just get overly pissed off and find my own way to do it: > SOMEONE TAKE ME OFF THE *&^%ING LISTS If you were as polite when you made your request of the administrators, it's no wonder... -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Tue Oct 8 07:26:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA28945 for current-outgoing; Tue, 8 Oct 1996 07:26:30 -0700 (PDT) Received: from night.primate.wisc.edu (night.primate.wisc.edu [144.92.43.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA28938 for ; Tue, 8 Oct 1996 07:26:26 -0700 (PDT) Received: by night.primate.wisc.edu; id JAA29922; 8.6.10/41.8; Tue, 8 Oct 1996 09:26:29 -0500 Message-Id: <199610081426.JAA29922@night.primate.wisc.edu> Date: Tue, 8 Oct 1996 09:26:29 -0500 From: dubois@primate.wisc.edu (Paul DuBois) To: freebsd-current@freebsd.org (FreeBSD-current users) Subject: Re: 3Com PCI 3c590 Defective Message. ENOUGH! In-Reply-To: <199610080743.JAA19626@uriah.heep.sax.de>; from J Wunsch on Oct 8, 1996 09:43:27 +0200 References: <199610072311.AAA05817@home.said.org> <199610080743.JAA19626@uriah.heep.sax.de> X-Mailer: Mutt 0.46 Mime-Version: 1.0 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch writes: > As Jake Dias wrote: > > > Someone suggested that only a small number of early cards _really_ had this > > problem so the test can be removed and further that really the test is > > wrong anyway. > > No, it should not go away. 3Com explicitly requests all driver > writers to issue a message of this kind if they detect the broken > adapter, since there's no usable software workaround. > > However, somebody should fix the test so that only broken cards > actually emit the message. ;-) Possibly also so that the printf in the driver prints a real value instead of "%D" :-) -- Paul DuBois dubois@primate.wisc.edu Home page: http://www.primate.wisc.edu/people/dubois Software: http://www.primate.wisc.edu/software From owner-freebsd-current Tue Oct 8 09:27:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA05536 for current-outgoing; Tue, 8 Oct 1996 09:27:34 -0700 (PDT) Received: from saguaro.flyingfox.com (saguaro.flyingfox.com [204.188.109.253]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA05528 for ; Tue, 8 Oct 1996 09:27:31 -0700 (PDT) Received: (from jas@localhost) by saguaro.flyingfox.com (8.6.12/8.6.10) id JAA24825; Tue, 8 Oct 1996 09:25:27 -0700 Date: Tue, 8 Oct 1996 09:25:27 -0700 From: Jim Shankland Message-Id: <199610081625.JAA24825@saguaro.flyingfox.com> To: jmb@freefall.freebsd.org Subject: Re: ok, look folks Cc: blh@nol.net, current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > you are subscribed as blh@dazed.nol.net > blh@nol.net != blh@dazed.nol.net > had you sent a request using the correcty address > you would not have had a problem. True enough, but sometimes people don't *know* what they subscribed as. Not everyone is all that knowledgable about mail systems, or in control of the mail system they're using. Higher quality sendmails put the RCPT value in a header line, like this: Received: (from smap@localhost) by saguaro.flyingfox.com (8.6.12/8.6.10) id GAA24614 for ; Tue, 8 Oct 1996 06:08:06 -0700 Note the "for "; that's who is subscribed, and that is who would need to unsubscribe (in my case). So, 3 tips for those wishing to unsubscribe from a mailing list: (1) Look for a line like the one above, that lists the stated recipient of the mail. (2) Try to get help from you local postmaster or mail guru first; the mailing list maintainer is probably an overworked, underpaid volunteer. (3) Be polite. Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-current Tue Oct 8 10:10:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA07623 for current-outgoing; Tue, 8 Oct 1996 10:10:34 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA07618 for ; Tue, 8 Oct 1996 10:10:31 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.7.6/8.7.3) id NAA00777 for freebsd-current@freebsd.org; Tue, 8 Oct 1996 13:10:27 -0400 (EDT) From: Charles Henrich Message-Id: <199610081710.NAA00777@crh.cl.msu.edu> Subject: 961006-SNAP comments To: freebsd-current@freebsd.org Date: Tue, 8 Oct 1996 13:10:27 -0400 (EDT) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The forced visual config on install is a horrible thing. Forced config is a bad idea, especially when its not neccesary for most and confuses lots of people. Secondly forcing me into the visual mode instead of command line was just tedium. The installation process froze my keyboard (Flipping between alt-f1 alt-f2) about half way through the install, after it completed it popped my back to the main console and unlocked the keyboard. The install refused to update my /etc/ files because a piece of the installation failed. That doesnt really make a whole lot of since, especially as the piece that failed was compat21. There was nothing I could figure out to do to get it to go back and write out the /etc files. Other than that, seems to be working as well os 0801.. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-current Tue Oct 8 10:29:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA08636 for current-outgoing; Tue, 8 Oct 1996 10:29:19 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA08631 for ; Tue, 8 Oct 1996 10:29:17 -0700 (PDT) Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id KAA08582 for ; Tue, 8 Oct 1996 10:25:44 -0700 (PDT) Received: by diablo.ppp.de (Smail3.1.28.1 #1) id m0vAffL-000Qp1C; Tue, 8 Oct 96 18:09 MET Received: from [193.141.161.123] (monster.pong.ppp.de [193.141.161.123]) by pong.PPP.DE (8.7.5/8.6.12) with ESMTP id IAA18376; Tue, 8 Oct 1996 08:58:32 +0200 (MET DST) Message-Id: In-Reply-To: <3259B8E6.41C67EA6@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 8 Oct 1996 08:58:28 +0200 To: Julian Elischer , current@freebsd.org From: Stefan Bethke Subject: Re: Netatalk.. anyone tried the new release? Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 19:13 Uhr -0700 07.10.1996, Julian Elischer wrote: >Does anyone hae any success/failure stories with teh new release? >it seems to work here, but I'd like to here from anyone who has >tried it with positive or negative feedback.... Somewhat off, but whatever: in comp.unix.bsd.freebsd.misc, you said some days ago, it would be easy to back-port the AppleTalk kernel parts to 2.1.5-R. I tried (patching net/{if_ethersubr.c,if_loop.c,netisr.c} and copying netatalk from -current). netatalk-1.3.3 compiles, but atalkd isn't able to run (haven't looked further why). netatalk 1.4b1 doesn't compile on 2.1.5-R (errors in compiling afpd, something with getquota()). I'll try again when I'm finally delving into -current. -- Stefan Bethke Hamburg, Germany From owner-freebsd-current Tue Oct 8 10:44:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA09563 for current-outgoing; Tue, 8 Oct 1996 10:44:01 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA09545 for ; Tue, 8 Oct 1996 10:43:56 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id SAA01094; Tue, 8 Oct 1996 18:15:14 +0100 From: Luigi Rizzo Message-Id: <199610081715.SAA01094@labinfo.iet.unipi.it> Subject: Re: 961006-SNAP comments To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Tue, 8 Oct 1996 18:15:14 +0100 (MET) Cc: freebsd-current@freebsd.org In-Reply-To: <199610081710.NAA00777@crh.cl.msu.edu> from "Charles Henrich" at Oct 8, 96 01:10:08 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The forced visual config on install is a horrible thing. Forced config is a > bad idea, especially when its not neccesary for most and confuses lots of > people. Secondly forcing me into the visual mode instead of command line was > just tedium. Let me disagree on this. I am fond of command line interfaces too, but you have to consider that most people (probably less expert than you) think differently. I also believe forced config is usual. The only thing I miss is probably a one-keystroke quit (Skip ?) option which does not require you to confirm things if nothing has changed (Hint hint...). > The install refused to update my /etc/ files because a piece of the > installation failed. That doesnt really make a whole lot of since, especially > as the piece that failed was compat21. There was nothing I could figure out to > do to get it to go back and write out the /etc files. Agreed. This is a problem in that it leaves the install process halfway through. It is probably more sensible to update etc files in any case. I also experienced difficulties in writing the boot manager (booteasy) on my 2GB drive. I followed the standard procedure as usual (did it twice) with no effect. Apparently, though, I can write a working bootmanager with the "Write" option in the "Partition" menu. Finally, a note on the computation of "default" partitions. It looks like computations are based on memory size rather than on disk space. I have tried to install on a 2GB disk and with 8MB ram, resulting in 28MB of swap. I'd probably make it compute a larger swap area if the FreeBSD slice is big enough. Say, 5..10% of the slice ? 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-current Tue Oct 8 10:47:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA09939 for current-outgoing; Tue, 8 Oct 1996 10:47:52 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA09918; Tue, 8 Oct 1996 10:47:46 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA16537; Tue, 8 Oct 1996 10:42:50 -0700 From: Terry Lambert Message-Id: <199610081742.KAA16537@phaeton.artisoft.com> Subject: Re: I plan to change random() for -current (was Re: rand() and random()) To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Tue, 8 Oct 1996 10:42:49 -0700 (MST) Cc: mrm@Mole.ORG, terry@lambert.org, wollman@lcs.mit.edu, ache@nagual.ru, bde@zeta.org.au, current@FreeBSD.org, freebsd-hackers@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de In-Reply-To: <3071.844755254@critter.tfs.com> from "Poul-Henning Kamp" at Oct 8, 96 08:14:14 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-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > But I'm also tired of Terry blowing things WAY out of proportion. I didn't blow it out of proportion. If you had taken my initial arguments at face value and just backed off from doing a change until you had better data, I would never have made a second posting on the subject. I certainly couldn't have argued with better data, if you had had it -- but you didn't. > Nobody has even thought about tinkering with rand48. You know damn well that it's the principle, not the specific function; just because most of the work cited uses the rand48 family of functions in no way excuses the change. > Nobody needing serious random numbers uses rand(). What about the multicast routing draft, which uses the function for its hash, and therefore expects it to be implemented identically across all platforms? 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-current Tue Oct 8 10:58:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA10865 for current-outgoing; Tue, 8 Oct 1996 10:58:49 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA10846 for ; Tue, 8 Oct 1996 10:58:39 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id TAA05763 for ; Tue, 8 Oct 1996 19:57:58 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id TAA15688 for current@freebsd.org; Tue, 8 Oct 1996 19:58:06 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.0/keltia-uucp-2.9) id TAA17254; Tue, 8 Oct 1996 19:40:58 +0200 (MET DST) Message-Id: <199610081740.TAA17254@keltia.freenix.fr> Date: Tue, 8 Oct 1996 19:40:57 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: current@freebsd.org Subject: Re: Best mail for threaded majordomo reading? In-Reply-To: <199610081310.JAA29803@elmer.ct.picker.com>; from Randall Hopper on Oct 8, 1996 09:10:59 -0400 References: <199610081310.JAA29803@elmer.ct.picker.com> X-Mailer: Mutt 0.46-n Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-CURRENT ctm#2522 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Randall Hopper: > I'm using ELM's filter instead of procmail. Much nicer filter file syntax, > through procmails is more flexible. procmail is more stable as well -- > will probably convert over to that when we upgrade out mail machine here. Please note that filter is not supported anymore by the Elm team. Elm 2.5 (if it ever comes out) will not have it. > Will eventually convert to mutt -- lots of nice features (color > highlighting, better MIME attachments, better PGP support, etc.). Was > somewhat unstable though when I tried it a few weeks back, but its coming > along fast. Randall Hopper rhh@ct.picker.com 0.46 + a set of patches is quite stable (some things are still broken and it is a very moving target). -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr Mutt patch collection: From owner-freebsd-current Tue Oct 8 11:01:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA11201 for current-outgoing; Tue, 8 Oct 1996 11:01:02 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA11189 for ; Tue, 8 Oct 1996 11:00:59 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65v3.2/1.1.8.2/19Aug95-0530PM) id AA14627; Tue, 8 Oct 1996 13:59:40 -0400 Date: Tue, 8 Oct 1996 13:59:40 -0400 From: Garrett Wollman Message-Id: <9610081759.AA14627@halloran-eldar.lcs.mit.edu> To: Terry Lambert Cc: current@FreeBSD.org Subject: Re: I plan to change random() for -current (was Re: rand() and random()) In-Reply-To: <199610081742.KAA16537@phaeton.artisoft.com> References: <3071.844755254@critter.tfs.com> <199610081742.KAA16537@phaeton.artisoft.com> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk < said: >> Nobody needing serious random numbers uses rand(). > What about the multicast routing draft, which uses the function for > its hash, and therefore expects it to be implemented identically > across all platforms? It's broken and will be fixed in the next version of that document. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Tue Oct 8 11:03:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA11412 for current-outgoing; Tue, 8 Oct 1996 11:03:13 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA11403 for ; Tue, 8 Oct 1996 11:03:09 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65v3.2/1.1.8.2/19Aug95-0530PM) id AA20747; Tue, 8 Oct 1996 14:02:05 -0400 Date: Tue, 8 Oct 1996 14:02:05 -0400 From: Garrett Wollman Message-Id: <9610081802.AA20747@halloran-eldar.lcs.mit.edu> To: Luigi Rizzo Cc: henrich@crh.cl.msu.edu (Charles Henrich), freebsd-current@freebsd.org Subject: Re: 961006-SNAP comments In-Reply-To: <199610081715.SAA01094@labinfo.iet.unipi.it> References: <199610081710.NAA00777@crh.cl.msu.edu> <199610081715.SAA01094@labinfo.iet.unipi.it> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: > Finally, a note on the computation of "default" partitions. It looks like > computations are based on memory size rather than on disk space. I have > tried to install on a 2GB disk and with 8MB ram, resulting in 28MB of > swap. I'd probably make it compute a larger swap area if the FreeBSD > slice is big enough. Say, 5..10% of the slice ? When I first wrote the code to do that, it just automatically took twice the size of physical memory. Different people have different needs for swap, so it's difficult to make a choice that will please both people with 8M machines and those with 64M machines. (I have 40M in my machine, and the only reason it has as much swap as it does is so that I can get crash dumps; in normal operation it never pages anything out to swap.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Tue Oct 8 11:22:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA12938 for current-outgoing; Tue, 8 Oct 1996 11:22:51 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA12933 for ; Tue, 8 Oct 1996 11:22:49 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id LAA19021; Tue, 8 Oct 1996 11:22:08 -0700 (PDT) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: Java,Netscape, & AccelX In-reply-to: Your message of "Tue, 08 Oct 1996 09:46:07 +0200." <199610080746.JAA19647@uriah.heep.sax.de> Date: Tue, 08 Oct 1996 11:22:08 -0700 Message-ID: <19019.844798928@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > So yes, this is a reason where the installation script should always > finally run a `mkfontdir' there. Jordan? Actually, this should be part of XF86config since FreeBSD isn't the only OS which could potentially suffer from this problem. Rich? :-) Jordan From owner-freebsd-current Tue Oct 8 11:36:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA13807 for current-outgoing; Tue, 8 Oct 1996 11:36:51 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA13780; Tue, 8 Oct 1996 11:36:38 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id UAA00782; Tue, 8 Oct 1996 20:35:58 +0200 (MET DST) To: Terry Lambert cc: mrm@Mole.ORG, wollman@lcs.mit.edu, ache@nagual.ru, bde@zeta.org.au, current@FreeBSD.org, freebsd-hackers@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de Subject: Re: I plan to change random() for -current (was Re: rand() and random()) In-reply-to: Your message of "Tue, 08 Oct 1996 10:42:49 PDT." <199610081742.KAA16537@phaeton.artisoft.com> Date: Tue, 08 Oct 1996 20:35:57 +0200 Message-ID: <780.844799757@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <199610081742.KAA16537@phaeton.artisoft.com>, Terry Lambert writes: >> Nobody needing serious random numbers uses rand(). > >What about the multicast routing draft, which uses the function for >its hash, and therefore expects it to be implemented identically >across all platforms? So they're using it for a hash function ? sounds like a more suitable use that as a (pseudo-)random generator. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Tue Oct 8 11:48:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA14884 for current-outgoing; Tue, 8 Oct 1996 11:48:54 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA14846; Tue, 8 Oct 1996 11:48:45 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA16666; Tue, 8 Oct 1996 11:44:29 -0700 From: Terry Lambert Message-Id: <199610081844.LAA16666@phaeton.artisoft.com> Subject: Re: I plan to change random() for -current (was Re: rand() and random()) To: bde@zeta.org.au (Bruce Evans) Date: Tue, 8 Oct 1996 11:44:28 -0700 (MST) Cc: mrm@Mole.ORG, phk@critter.tfs.com, ache@nagual.ru, bde@zeta.org.au, current@FreeBSD.org, freebsd-hackers@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de, terry@lambert.org, wollman@lcs.mit.edu In-Reply-To: <199610080712.RAA26125@godzilla.zeta.org.au> from "Bruce Evans" at Oct 8, 96 05:12:06 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-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > >Nobody has even thought about tinkering with rand48. > > Well, I have thought of checking if it is related to the old BSD > rand48 :-). rand48 isn't in BSD4.4Lite or BSDI. FreeBSD has a > contributed version. I have the original usenet posting. It is identical in function, and was tested for compatability at boundry conditions. I also have additions to the FORTRAN library for a lot of the missing math functionality that I can dig out if necessary -- I'd need to update my ftoc/f77 code though, so I'm reluctant. 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-current Tue Oct 8 13:24:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA22210 for current-outgoing; Tue, 8 Oct 1996 13:24:53 -0700 (PDT) Received: from imperial.ece.uci.edu (imperial.ece.uci.edu [128.200.9.67]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA22186 for ; Tue, 8 Oct 1996 13:24:48 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by imperial.ece.uci.edu (8.7.5/8.6.12) with SMTP id NAA11993 for ; Tue, 8 Oct 1996 13:24:33 -0700 (PDT) Message-Id: <199610082024.NAA11993@imperial.ece.uci.edu> X-Authentication-Warning: imperial.ece.uci.edu: Host localhost [127.0.0.1] didn't use HELO protocol To: current@freebsd.org Subject: bugs with syn and mountd in latest snap Date: Tue, 08 Oct 1996 13:24:32 -0700 From: Steven Wallace Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk mountd -d Getting export list. Got line /usr gondor localhost imperial.ece.uci.edu Making new ep fs=0x404,0x1 send 40 continuous SYN packets to say, port 79, and voila! panic! System crashes inside tcp_input(). Bug obviously related to the SYN protection code added. Please let me know when these bugs are fixed. Steven From owner-freebsd-current Tue Oct 8 13:43:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA24231 for current-outgoing; Tue, 8 Oct 1996 13:43:35 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA24204 for ; Tue, 8 Oct 1996 13:43:28 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id VAA01431; Tue, 8 Oct 1996 21:15:23 +0100 From: Luigi Rizzo Message-Id: <199610082015.VAA01431@labinfo.iet.unipi.it> Subject: Re: 961006-SNAP comments To: wollman@lcs.mit.edu (Garrett Wollman) Date: Tue, 8 Oct 1996 21:15:22 +0100 (MET) Cc: henrich@crh.cl.msu.edu, freebsd-current@freebsd.org In-Reply-To: <9610081802.AA20747@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Oct 8, 96 02:01:46 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Finally, a note on the computation of "default" partitions. It looks like > > computations are based on memory size rather than on disk space. I have ... > When I first wrote the code to do that, it just automatically took > twice the size of physical memory. Different people have different > needs for swap, so it's difficult to make a choice that will please > both people with 8M machines and those with 64M machines. (I have 40M It was a very good choice back in the days when affordable disks were around 200MB and were almost completely taken by the OS+user files, so saving disk space was important. But now disks have grown 8-10 times in capacity, and we weren't as good as other to make newer releases of the os take up all the available space. So, dedicating a small fraction of the slice or 2xRAM, whatever is larger, to swap space as a default should go unnoticed by people with large disks, and they will have less risks of running out of swap. I can only speak for myself, but quite often I do installations on a small dedicated system to avoid troubles, and then move the disk to its final place (almost all of our systems use IDE disks mounted on a removable frame; probably more convenient than a laptop, for home<-->office use). 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-current Tue Oct 8 14:38:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA29592 for current-outgoing; Tue, 8 Oct 1996 14:38:31 -0700 (PDT) Received: from freenet.hamilton.on.ca (main.freenet.hamilton.on.ca [199.212.94.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA29578 for ; Tue, 8 Oct 1996 14:38:25 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (james.freenet.hamilton.on.ca [199.212.94.66]) by freenet.hamilton.on.ca (8.7.5/8.7.3) with ESMTP id RAA25196; Tue, 8 Oct 1996 17:38:28 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.7.5/8.7.3) with SMTP id RAA14922; Tue, 8 Oct 1996 17:40:16 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Tue, 8 Oct 1996 17:40:15 -0400 (EDT) From: Tim Vanderhoek To: Charles Henrich cc: freebsd-current@freebsd.org Subject: Re: 961006-SNAP comments In-Reply-To: <199610081710.NAA00777@crh.cl.msu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 8 Oct 1996, Charles Henrich wrote: > The forced visual config on install is a horrible thing. Forced config is a > bad idea, especially when its not neccesary for most and confuses lots of > people. Secondly forcing me into the visual mode instead of command line was > just tedium. I think what is dangerous is the suggestion to the user that they remove all devices which they don't have. I think it should be reworded to say "know you don't have", to prevent removal of something important ("syscons video driver? What's that? I have a DayTek moniter, not a Syscons." (Incidentally, removing the syscons driver causes a sig12, page fault while in kernel mode when one continues booting)). -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk From owner-freebsd-current Tue Oct 8 14:52:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA01801 for current-outgoing; Tue, 8 Oct 1996 14:52:30 -0700 (PDT) Received: from alpo.whistle.com (s204m38.isp.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA01787 for ; Tue, 8 Oct 1996 14:52:27 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.5/8.7.3) with SMTP id OAA05810; Tue, 8 Oct 1996 14:51:38 -0700 (PDT) Message-ID: <325ACC75.446B9B3D@whistle.com> Date: Tue, 08 Oct 1996 14:49:41 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Stefan Bethke CC: current@freebsd.org Subject: Re: Netatalk.. anyone tried the new release? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Stefan Bethke wrote: > > At 19:13 Uhr -0700 07.10.1996, Julian Elischer wrote: > >Does anyone hae any success/failure stories with teh new release? > >it seems to work here, but I'd like to here from anyone who has > >tried it with positive or negative feedback.... > > Somewhat off, but whatever: in comp.unix.bsd.freebsd.misc, you said some > days ago, it would be easy to back-port the AppleTalk kernel parts to > 2.1.5-R. I tried (patching net/{if_ethersubr.c,if_loop.c,netisr.c} and > copying netatalk from -current). > > netatalk-1.3.3 compiles, but atalkd isn't able to run (haven't looked > further why). netatalk 1.4b1 doesn't compile on 2.1.5-R (errors in > compiling afpd, something with getquota()). (just comment out all the quota stuff :) the patch in control.c in atalkd in 1.4 was based on the sam epatch on 1.3.3 and allowed atalkd to run by default.. it does run if you supply a conf file, even without the patch as that code isn't run in that case. > > I'll try again when I'm finally delving into -current. > I recommend current anyhow.... > -- > Stefan Bethke > Hamburg, Germany I assume you have the FreeBSD patches for 1.3.3? the kernel code we have came from the 2.1 port of 1.3.3 I ported it to 2.2 and checked it in.. From owner-freebsd-current Tue Oct 8 15:21:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA05589 for current-outgoing; Tue, 8 Oct 1996 15:21:48 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA05563 for ; Tue, 8 Oct 1996 15:21:42 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA02688; Wed, 9 Oct 1996 00:21:16 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA09387; Wed, 9 Oct 1996 00:21:16 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id AAA22171; Wed, 9 Oct 1996 00:18:56 +0200 (MET DST) From: J Wunsch Message-Id: <199610082218.AAA22171@uriah.heep.sax.de> Subject: Re: Java,Netscape, & AccelX To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 9 Oct 1996 00:18:55 +0200 (MET DST) Cc: XFree86-beta@XFree86.Org (XFree86 beta test list) Reply-To: XFree86-beta@XFree86.Org (XFree86 beta test list) In-Reply-To: <19019.844798928@time.cdrom.com> from "Jordan K. Hubbard" at "Oct 8, 96 11:22:08 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: (Sorry for the blatant crosspost. Background: Netcrap recommends people to run a `mkfontdir' in .../lib/X11/fonts/misc/ if they experience segfaults, and it turns out that the actual problem is that the fonts.dir in the XFree86 distribution mismatches with the actually installed fonts if somebody didn't install all the font packages.) > > So yes, this is a reason where the installation script should always > > finally run a `mkfontdir' there. Jordan? > > Actually, this should be part of XF86config since FreeBSD isn't > the only OS which could potentially suffer from this problem. > Rich? :-) Hmm, XF86Config? I thought this was only for creating the config file in /etc. Anyway, i'll move it into the XFree86 beta list then... -- 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-current Tue Oct 8 15:29:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA06873 for current-outgoing; Tue, 8 Oct 1996 15:29:11 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA06858 for ; Tue, 8 Oct 1996 15:29:04 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id HAA11662; Wed, 9 Oct 1996 07:58:35 +0930 From: Michael Smith Message-Id: <199610082228.HAA11662@genesis.atrad.adelaide.edu.au> Subject: Re: 961006-SNAP comments To: hoek@freenet.hamilton.on.ca (Tim Vanderhoek) Date: Wed, 9 Oct 1996 07:58:34 +0930 (CST) Cc: henrich@crh.cl.msu.edu, freebsd-current@freebsd.org In-Reply-To: from "Tim Vanderhoek" at Oct 8, 96 05:40:15 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Tim Vanderhoek stands accused of saying: > > (Incidentally, removing the syscons driver causes a sig12, page fault > while in kernel mode when one continues booting)). You can blame(?) Bruce for that; he insisted on being able to have both syscons and pcvt in the same kernel so it had to be possible to disable them. I don't like it for exactly the reason you've noted. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Oct 8 16:13:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA12544 for current-outgoing; Tue, 8 Oct 1996 16:13:40 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-6.ut.nl.ibm.net [139.92.42.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA12516; Tue, 8 Oct 1996 16:13:23 -0700 (PDT) Received: from vector.jhs.no_domain (localhost [127.0.0.1]) by vector.jhs.no_domain (8.7.5/8.6.9) with ESMTP id XAA05780; Tue, 8 Oct 1996 23:53:01 +0100 (MET) Message-Id: <199610082253.XAA05780@vector.jhs.no_domain> To: Dan Janowski cc: current@freebsd.org Subject: Re: Best mail for threaded majordomo reading? From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Mailer: EXMH 1.6.7, PGP available X-Address: Holz Strasse 27d, 80469 Munich, Germany X-Phone: +49.89.268616 X-Fax: +49.89.2608126 X-Web: http://www.freebsd.org/~jhs/ In-reply-to: Your message of "Mon, 07 Oct 1996 23:18:01 -0400." <3259C7E9.41C67EA6@netcom.com> Date: Tue, 08 Oct 1996 23:53:00 +0100 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Reference: > From: Dan Janowski > > What are you guys using? I am using netscape > mail which does threading and mbox-es nicely, but > it has some annoying deficiencies. I use [not yet in ports/mail/ ] /exmh http://www.freebsd.org/~jhs/src/bsd/fixes/FreeBSD/ports/generic/mail/exmh/ Other speak well of other ports/mail things such as pine etc, best discuss that on ports@, not current@ :-) > What is a > good way of auto-processing all the mail into > separate mbox-es, i.e. put list mail somewhere > different than "regular" mail? I use ports/mail/procmail, you can see my control file syntax to sort a load of mostly freebsd lists at: http://www.freebsd.org/~jhs/dots/.procmailrc Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Tue Oct 8 16:42:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA16933 for current-outgoing; Tue, 8 Oct 1996 16:42:42 -0700 (PDT) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA16926 for ; Tue, 8 Oct 1996 16:42:39 -0700 (PDT) Received: from campa.panke.de (anonymous231.ppp.cs.tu-berlin.de [130.149.17.231]) by mail.cs.tu-berlin.de (8.6.13/8.6.12) with ESMTP id BAA06657; Wed, 9 Oct 1996 01:41:03 +0200 Received: (from wosch@localhost) by campa.panke.de (8.6.12/8.6.12) id WAA06329; Tue, 8 Oct 1996 22:21:48 +0200 Date: Tue, 8 Oct 1996 22:21:48 +0200 From: Wolfram Schneider Message-Id: <199610082021.WAA06329@campa.panke.de> To: Steve Price CC: current@freebsd.org Subject: .depend Reply-to: Wolfram Schneider MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I think we should add an enviroment variable (e.g. DEPENDFILE) to make(1) for `.depend'. mkdep -f foo support different depend files. --Wolfram Schneider From owner-freebsd-current Tue Oct 8 17:47:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA20254 for current-outgoing; Tue, 8 Oct 1996 17:47:30 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA20249 for ; Tue, 8 Oct 1996 17:47:27 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id AAA28871; Wed, 9 Oct 1996 00:47:10 GMT Date: Wed, 9 Oct 1996 09:47:10 +0900 (JST) From: Michael Hancock To: Joerg Wunsch cc: FreeBSD-current users Subject: Re: bpatch (was Re: secure level diffs to kern_mib.c, LINT) In-Reply-To: <199610080740.JAA19572@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 8 Oct 1996, J Wunsch wrote: > As Michael Hancock wrote: > > > What's the history of bpatch? Did we ever have one? > > There's already another bpatch in the ports. Yes, it was in editors. I guess it needs to be called something else. The bpatch in BSDI would allow you to do this... bpatch securelevel 1 Regards, Mike Hancock From owner-freebsd-current Tue Oct 8 17:58:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA20849 for current-outgoing; Tue, 8 Oct 1996 17:58:03 -0700 (PDT) Received: from eel.dataplex.net (eel.dataplex.net [208.2.87.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA20839; Tue, 8 Oct 1996 17:57:58 -0700 (PDT) Received: from [208.2.87.4] (cod [208.2.87.4]) by eel.dataplex.net (8.7.5/8.7.3) with ESMTP id TAA00265; Tue, 8 Oct 1996 19:57:55 -0500 (CDT) X-Sender: rkw@eel.dataplex.net Message-Id: In-Reply-To: <199610082021.WAA06329@campa.panke.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 8 Oct 1996 19:56:01 -0500 To: Wolfram Schneider From: Richard Wackerbarth Subject: Re: .depend Cc: Steve Price , current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >I think we should add an enviroment variable (e.g. DEPENDFILE) to >make(1) for `.depend'. mkdep -f foo support different depend files. Why change "make"? You can always include the depend file from the makefile. From owner-freebsd-current Tue Oct 8 18:21:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA22969 for current-outgoing; Tue, 8 Oct 1996 18:21:19 -0700 (PDT) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [204.214.4.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA22960; Tue, 8 Oct 1996 18:21:15 -0700 (PDT) Received: from bonsai.hiwaay.net by fly.HiWAAY.net; (8.7.5/1.1.8.2/21Sep95-1003PM) id UAA15340; Tue, 8 Oct 1996 20:15:26 -0500 (CDT) Message-ID: <325AFCAC.538FFB68@hiwaay.net> Date: Tue, 08 Oct 1996 20:15:24 -0500 From: Steve Price Reply-To: steve@FreeBSD.org X-Mailer: Mozilla 2.02 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Wolfram Schneider CC: current@FreeBSD.org Subject: Re: .depend References: <199610082021.WAA06329@campa.panke.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Wolfram Schneider wrote: > > I think we should add an enviroment variable (e.g. DEPENDFILE) to > make(1) for `.depend'. mkdep -f foo support different depend files. > > --Wolfram Schneider I don't know exactly what you are trying to do, but you can put something like this in your Makefile: .if exists(${DEPENDFILE}) .include <${DEPENDFILE}> .endif This alleviates the need to augment make(1). Does this help? If not, please give me a specific example of what you are trying to do and I will see what I can do to help. :) Steve From owner-freebsd-current Tue Oct 8 21:28:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA04095 for current-outgoing; Tue, 8 Oct 1996 21:28:48 -0700 (PDT) Received: from research.gate.nec.co.jp (research.gate.nec.co.jp [202.32.8.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA04090 for ; Tue, 8 Oct 1996 21:28:44 -0700 (PDT) Received: from sbl-gw.sbl.cl.nec.co.jp by research.gate.nec.co.jp (8.7.6+2.6Wbeta7/950912) with ESMTP id NAA18758; Wed, 9 Oct 1996 13:27:07 +0900 (JST) Received: from sirius.sbl.cl.nec.co.jp by sbl-gw.sbl.cl.nec.co.jp (8.7.6+2.6Wbeta7/3.3W6) with ESMTP id NAA03859; Wed, 9 Oct 1996 13:26:51 +0900 (JST) Received: by sirius.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with UUCP id NAA20434; Wed, 9 Oct 1996 13:26:51 +0900 (JST) Date: Wed, 9 Oct 1996 13:26:51 +0900 (JST) From: Naoki Hamada Message-Id: <199610090426.NAA20434@sirius.sbl.cl.nec.co.jp> To: imb@asstdc.com.au CC: current@freebsd.org Subject: 3c589b + ep driver Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk michael wrote: >The following patch seems to work for me .. I'd appreciate comments from >others whether it helps or not. Note that I am not in favour of adding more >loops which cannot be guaranteed to terminate so this patch is experimental >only, I found that the ep driver does not properly handle commands which take time more than a I/O cycle. What about the following patch? (This patch is 961006-SNAP based. Still applicable to the current, I hope.) -nao diff -ur ep.orig/if_ep.c ep/if_ep.c --- ep.orig/if_ep.c Wed Oct 9 13:04:24 1996 +++ ep/if_ep.c Wed Oct 9 13:02:07 1996 @@ -728,7 +728,6 @@ */ s = splimp(); - while (inw(BASE + EP_STATUS) & S_COMMAND_IN_PROGRESS); GO_WINDOW(0); outw(BASE + EP_COMMAND, STOP_TRANSCEIVER); @@ -749,7 +748,9 @@ outb(BASE + EP_W2_ADDR_0 + i, sc->arpcom.ac_enaddr[i]); outw(BASE + EP_COMMAND, RX_RESET); + EP_BUSY_WAIT; outw(BASE + EP_COMMAND, TX_RESET); + EP_BUSY_WAIT; /* Window 1 is operating window */ GO_WINDOW(1); @@ -1082,6 +1083,7 @@ if (status & TXS_SUCCES_INTR_REQ); else if (status & (TXS_UNDERRUN | TXS_JABBER | TXS_MAX_COLLISION)) { outw(BASE + EP_COMMAND, TX_RESET); + EP_BUSY_WAIT; if (status & TXS_UNDERRUN) { if (sc->tx_rate > 1) { sc->tx_rate--; /* Actually in steps of 1/64 */ @@ -1289,6 +1291,7 @@ } all_pkt: outw(BASE + EP_COMMAND, RX_DISCARD_TOP_PACK); + EP_BUSY_WAIT; /* * recompute average packet's length, the factor used is 1/8 to go down * and 1/32 to go up @@ -1333,7 +1336,6 @@ #ifdef EP_LOCAL_STATS sc->rx_bpf_disc++; #endif - while (inw(BASE + EP_STATUS) & S_COMMAND_IN_PROGRESS); outw(BASE + EP_COMMAND, SET_RX_EARLY_THRESH | delta); return; } @@ -1346,12 +1348,12 @@ if (!sc->mb[sc->next_mb]) epmbuffill((caddr_t) sc, 0); sc->top = 0; - while (inw(BASE + EP_STATUS) & S_COMMAND_IN_PROGRESS); outw(BASE + EP_COMMAND, SET_RX_EARLY_THRESH | delta); return; out: outw(BASE + EP_COMMAND, RX_DISCARD_TOP_PACK); + EP_BUSY_WAIT; if (sc->top) { m_freem(sc->top); sc->top = 0; @@ -1364,7 +1366,6 @@ delta = MIN_RX_EARLY_THRESHF; ep_fset(F_RX_FIRST); ep_frst(F_RX_TRAILER); - while (inw(BASE + EP_STATUS) & S_COMMAND_IN_PROGRESS); outw(BASE + EP_COMMAND, SET_RX_EARLY_THRESH | (sc->rx_early_thresh = delta)); } @@ -1529,11 +1530,13 @@ outw(BASE + EP_COMMAND, RX_DISABLE); outw(BASE + EP_COMMAND, RX_DISCARD_TOP_PACK); - while (inw(BASE + EP_STATUS) & S_COMMAND_IN_PROGRESS); + EP_BUSY_WAIT; outw(BASE + EP_COMMAND, TX_DISABLE); outw(BASE + EP_COMMAND, STOP_TRANSCEIVER); outw(BASE + EP_COMMAND, RX_RESET); + EP_BUSY_WAIT; outw(BASE + EP_COMMAND, TX_RESET); + EP_BUSY_WAIT; outw(BASE + EP_COMMAND, C_INTR_LATCH); outw(BASE + EP_COMMAND, SET_RD_0_MASK); outw(BASE + EP_COMMAND, SET_INTR_MASK); diff -ur ep.orig/if_epreg.h ep/if_epreg.h --- ep.orig/if_epreg.h Wed Oct 9 13:04:24 1996 +++ ep/if_epreg.h Wed Oct 9 10:10:53 1996 @@ -142,6 +142,7 @@ */ #define is_eeprom_busy(b) (inw((b)+EP_W0_EEPROM_COMMAND)&EEPROM_BUSY) #define GO_WINDOW(x) outw(BASE+EP_COMMAND, WINDOW_SELECT|(x)) +#define EP_BUSY_WAIT while (inw(BASE + EP_STATUS) & S_COMMAND_IN_PROGRESS); /************************************************************************** * * From owner-freebsd-current Tue Oct 8 21:29:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA04137 for current-outgoing; Tue, 8 Oct 1996 21:29:45 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA04132; Tue, 8 Oct 1996 21:29:42 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id FAA02243; Wed, 9 Oct 1996 05:02:06 +0100 From: Luigi Rizzo Message-Id: <199610090402.FAA02243@labinfo.iet.unipi.it> Subject: More 961006-SNAP comments To: freebsd-current@freebsd.org Date: Wed, 9 Oct 1996 05:02:06 +0100 (MET) Cc: jkh@freebsd.org X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A few more comments on the latest snap. 1. I tried to build a new kernel, and the build produces a ton of warnings about unused parameters, signed/unsigned comparisons, and other things. Maybe it's just more verbosity than in the past, but all these warnings are not pleasant (that is, I would not like to get all of them from a CD distribution!) 2. I copied parts of the distribution on a local partition and completed the install at a later time. The progress line reports a speed of ~30 KB/s (and even lower when there is a kernel build going on). I can't figure out why it is so slow, even if the disk heads are jumping back and forth between source and destination, I would expect buffered reads before gunzipping the archive, isn't it ? As a reference, extracting from the net, on the same disk (but a different machine) was running at 300-400 KB/s according to the progress line. 3. there is a "locate.pl" file in /sys/pci. leftover from something ? 4. since there is a nice mouse support in text mode now (and I am enjoying it more and more) it could be the case to try to exploit it in the installation process. Don't know how hard would it be to integrate it into the current code. 5. In the install menu, when I try to select "Media" to select a different FTP server, it does not allow me to do so. I have to choose a different media, obtain a partial success (e.g. specify NFS, or file system, but not CDROM because it detects that there isn't one) and then change again to FTP. >From what I have seen this far, there appears not to be functional problems in the code, but perhaps some "youth" problems in the install code. Maybe it's worth waiting the next snap before putting things on a CD ? 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-current Tue Oct 8 21:39:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA04762 for current-outgoing; Tue, 8 Oct 1996 21:39:44 -0700 (PDT) Received: from terd.triskelion.com (root@danj.port.net [207.38.236.113]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA04757 for ; Tue, 8 Oct 1996 21:39:41 -0700 (PDT) Received: from fnur.triskelion.com (fnur.triskelion.com [180.200.1.3]) by terd.triskelion.com (8.7.5/8.6.12) with SMTP id AAA00372 for ; Wed, 9 Oct 1996 00:33:58 -0400 (EDT) Message-ID: <325B2B36.41C67EA6@netcom.com> Date: Wed, 09 Oct 1996 00:33:58 -0400 From: Dan Janowski Organization: Triskelion Systems, Inc. X-Mailer: Mozilla 2.01 (X11; I; FreeBSD 2.1.0-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.org Subject: Re: ok, look folks References: <199610081625.JAA24825@saguaro.flyingfox.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk (4) Save those useful and, apparently, ignored messages from majordomo when you subscribe. (Even make a mail-box file to keep them in) ++ We should add a little banner at the top of those majordomo "welcome" messages: KEEP THIS MESSAGE!!!!! YOU WILL NEED IT WHEN YOU'VE GOTTEN SICK OF THE E-MAIL TRAFFIC AND THEN TRY TO UNSUBSCRIBE IN A PANIC, FORGETTING HOW TO DO IT AND GETTING PISSED OFF ABOUT IT. ++ Nothing personal intended; it got me once. But that was Linux lists (you want to talk about traffic), and that was a long time ago. Dan -- danj@netcom.com Dan Janowski Triskelion Systems, Inc. Bronx, NY From owner-freebsd-current Tue Oct 8 22:01:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA05918 for current-outgoing; Tue, 8 Oct 1996 22:01:20 -0700 (PDT) Received: from terd.triskelion.com (root@danj.port.net [207.38.236.113]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA05911 for ; Tue, 8 Oct 1996 22:01:16 -0700 (PDT) Received: from fnur.triskelion.com (fnur.triskelion.com [180.200.1.3]) by terd.triskelion.com (8.7.5/8.6.12) with SMTP id AAA00395 for ; Wed, 9 Oct 1996 00:55:48 -0400 (EDT) Message-ID: <325B3053.167EB0E7@netcom.com> Date: Wed, 09 Oct 1996 00:55:47 -0400 From: Dan Janowski Organization: Triskelion Systems, Inc. X-Mailer: Mozilla 2.01 (X11; I; FreeBSD 2.1.0-RELEASE i386) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: 961006-SNAP comments References: <199610082015.VAA01431@labinfo.iet.unipi.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ notes on swap calculations ...] Swap is an inverse function to system memory, isn't it? Based on some "assumptions" we could have a formula: R = physical ram T = total memory size "useful" for a: minimal system, X system, developer system Sm = Minimum amount of swap no matter how much RAM one has SM = (what is the maximum supported swap size?) Maximum "useful" swap quantity D = Disk size Dp = "Normal" percentage of disk to consume for swap DpM = Maximum percentage of disk space to be consumed (for small disks) --- Calculate --- swap = max( ( T - R ), (D * Dp) ) swap = min( swap, (D * DpM) ) swap = max( max( swap, Sm ), SM) We could do something similar with var partitions (all those logs...). Dan -- danj@netcom.com Dan Janowski Triskelion Systems, Inc. Bronx, NY From owner-freebsd-current Tue Oct 8 22:23:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA06992 for current-outgoing; Tue, 8 Oct 1996 22:23:59 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA06947 for ; Tue, 8 Oct 1996 22:23:21 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id OAA13667; Wed, 9 Oct 1996 14:53:06 +0930 From: Michael Smith Message-Id: <199610090523.OAA13667@genesis.atrad.adelaide.edu.au> Subject: Re: 961006-SNAP comments To: danj@netcom.com (Dan Janowski) Date: Wed, 9 Oct 1996 14:53:05 +0930 (CST) Cc: freebsd-current@freebsd.org In-Reply-To: <325B3053.167EB0E7@netcom.com> from "Dan Janowski" at Oct 9, 96 00:55:47 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dan Janowski stands accused of saying: > > Based on some "assumptions" we could have a formula: > > R = physical ram > > T = total memory size "useful" for a: minimal system, X system, > developer system ... > --- Calculate --- > swap = max( ( T - R ), (D * Dp) ) This is (I believe) invalid; you always need swap to back your RAM with. > Dan Janowski -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Oct 8 22:38:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA08197 for current-outgoing; Tue, 8 Oct 1996 22:38:35 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA08192 for ; Tue, 8 Oct 1996 22:38:34 -0700 (PDT) Received: from localhost (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with SMTP id WAA02328 for ; Tue, 8 Oct 1996 22:39:35 -0700 Date: Tue, 8 Oct 1996 22:39:34 -0700 (PDT) From: Veggy Vinny To: current@FreeBSD.ORG Subject: -current kernel = SNAP Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Greetings, I just compiled a kernel with the -current src tree and the kernel says 2.2SNAP: root@earth [10:36pm][/usr/local] >> uname -a FreeBSD earth.GAIANET.NET 2.2-961004-SNAP FreeBSD 2.2-961004-SNAP #0: Tue Oct 8 21:15:40 PDT 1996 vince@earth.gaianet.net:/usr/src/sys-UP/compile/EARTH i386 root@earth [10:36pm][/usr/local] >> Is this correct for a -current kernel? Vince From owner-freebsd-current Wed Oct 9 00:08:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA22707 for current-outgoing; Wed, 9 Oct 1996 00:08:00 -0700 (PDT) Received: from uno.sat.t.u-tokyo.ac.jp (uno.sat.t.u-tokyo.ac.jp [133.11.70.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA22386; Wed, 9 Oct 1996 00:06:36 -0700 (PDT) Received: by uno.sat.t.u-tokyo.ac.jp (8.7.3+2.6Wbeta5/8.7.3) with ESMTP id QAA15440; Wed, 9 Oct 1996 16:06:19 +0900 (JST) To: freebsd-bugs@freebsd.org Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: NFS from Solaris Server X-Mailer: Mew version 1.06 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 09 Oct 1996 16:06:19 +0900 Message-ID: <15438.844844779@sat.t.u-tokyo.ac.jp> From: Hidetoshi Shimokawa Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, >Is Hosed, on 2.1.0 NFS will write to a sun server at a whopping 100K/sec over >ethernet, but it goes along happily just slowly. >On 2.2-961006-SNAP we also write to NFS at a whopping 100K/sec, however in 8MB >increments we write out at 600K/sec (apparently into some memory buffer??) at >which point the buffer fills, all NFS operations are locked out on the system >until the buffer is drained. This takes an eternity. How do I undo this >buffering mechanism or make it a tunable? I'm also not satisfied with NFS performance of FreeBSD-current. It seems that 2.1.5 is rather faster than current. >Also an interesting note, a SGI to the SUN writes at 900K/sec via NFS with no >problems. The SGI is apparently doing: > > NFS v3 Proc 6, Proc 7 (Data) > >The FreeBSD box does: > > NFS v2 Proc 8 (Data) > or > NFS v3 Proc 7 (Data) > >Both are horrendously slow. Im going to attempt to figure out what the hell >Proc 6 is (everything I see says read, which doesnt make alot of sense). In >any case Im not much of a kernel hacker, so any assistance or someone with a >solution, please raise your hand! :) I am looking into this problem since yesterday, adding some debuging code into kernel. The following is some results around this. The system is, PentiumPro 100M Ether Sun Ultra Wide SCSI FreeBSD-current <--------------> Solaris 2.5 --------- Disk NFSv2 client NFSv2 server 6MB/s(iozone) and I mesured performance by iozone. With the default setting (with 4 nfsiods), I can get only 300KB/s. - With NFSv3, I got around 500KB-600KB. - SS20 <-> Sun Ultra gets around 800KB/s.) 1) A faster client(pentium class) gets less performance than a slower client(486 class). 2) After I killed all async daemon (nfsiod), I got 400KB/s, this seems funny :-). 3) By added some debugging code, I found that the performance reduction happens when the nfsiods are all busy and the buffer is marked as B_DELWRI(delayed write) in nfs_asyncio() (/sys/nfs/nfs_bio.c). This explains 1). 4) I changed the code so that nfs_asyncio returns with EIO before marks B_DELWRI, then I got 800-900KB/s. I think this algorithm is essentially same as 2.1.5 or BSDI 2.1. 5) It is interesting that the change above doesn't improve v3 performance. 6) I don't know how delayed write scheme is efficient, but at this point, it is a bottleneck. It is because, after a nfsbiod starts processiong the delayed write buffer in nfssvc_iod() (nfs_syscalls.c), other nfsbiods stop its work. I confirmed by debugging code in kernel, but it can be also easily observed by % iozone & sleep 2; cat /proc/"nfsiod's pid"/status nfsiod 15057 1 15056 0 -1,-1 noflags 844842823,10788 0,0 0,78906 sbwait 0 0 0,0,0,5,2,3,4,20,31 nfsiod 15058 1 15056 0 -1,-1 noflags 844842823,10874 0,0 0,30899 nfsrcvlk 0 0 0,0,0,5,2,3,4,20,31 nfsiod 15059 1 15056 0 -1,-1 noflags 844842823,10939 0,0 0,3486 nfsrcvlk 0 0 0,0,0,5,2,3,4,20,31 nfsiod 15060 1 15056 0 -1,-1 noflags 844842823,11001 0,0 0,1694 nfsrcvlk 0 0 0,0,0,5,2,3,4,20,31 nfsiod 15061 1 15056 0 -1,-1 noflags 844842823,11061 0,0 0,1395 nfsrcvlk 0 0 0,0,0,5,2,3,4,20,31 nfsiod 15062 1 15056 0 -1,-1 noflags 844842823,11119 0,0 0,1601 nfsrcvlk 0 0 0,0,0,5,2,3,4,20,31 nfsiod 15063 1 15056 0 -1,-1 noflags 844842823,11176 0,0 0,1339 nfsrcvlk 0 0 0,0,0,5,2,3,4,20,31 nfsiod 15064 1 15056 0 -1,-1 noflags 844842823,11233 0,0 0,1277 nfsrcvlk 0 0 0,0,0,5,2,3,4,20,31 All nfsiods except one are locked at nfs_rcvlock (nfs_socket.c) for long time. By tcpdump, server did reply but nfsiod can not process it for locking. I'm not familiar with NFS and kernel programming but it seems that current code has locking problem. I don't know how to fix it, please help, NFS and kernel experts! (Isn't it needed to be non-interruptable for the code between nfs_send and nfs_rcvlock in nfs_request() and nfs_reply()?) I also like to know why NFSv3 client is so slow. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: finger -l simokawa@sat.t.u-tokyo.ac.jp From owner-freebsd-current Wed Oct 9 00:27:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA28012 for current-outgoing; Wed, 9 Oct 1996 00:27:50 -0700 (PDT) Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA28005 for ; Wed, 9 Oct 1996 00:27:48 -0700 (PDT) Received: from newport.ece.uci.edu by meter.eng.uci.edu (8.7.6) id AAA01255; Wed, 9 Oct 1996 00:27:45 -0700 (PDT) Received: from localhost by newport.ece.uci.edu (8.7.4) id AAA05826; Wed, 9 Oct 1996 00:27:44 -0700 (PDT) Message-Id: <199610090727.AAA05826@newport.ece.uci.edu> To: current@freebsd.org Subject: Re: bugs with syn and mountd in latest snap In-reply-to: Your message of "Tue, 08 Oct 1996 13:24:32 PDT." <199610082024.NAA11993@imperial.ece.uci.edu> Date: Wed, 09 Oct 1996 00:27:43 -0700 From: Steven Wallace Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk mountd is actually okay, although my problem was that the loopback lo0 interface did not get started up at boot time. The reason was that the gethostname reslover, I have "domain ece.uci.edu" in /etc/resolv.conf. That should search ece.uci.edu then uci.edu, as the man page says and 2.1.5R did. However, it now only searches ece.uci.edu. Did someone change the behavior and if so, why? As a result, localhost.uci.edu was not being found and the lo0 interface not ifconfiged. Is mountd suppose to hang if loopback not up? Why? Steven From owner-freebsd-current Wed Oct 9 00:40:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA00693 for current-outgoing; Wed, 9 Oct 1996 00:40:45 -0700 (PDT) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA00686 for ; Wed, 9 Oct 1996 00:40:41 -0700 (PDT) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.6.11/8.6.9) id RAA20191; Wed, 9 Oct 1996 17:40:22 +1000 From: David Dawes Message-Id: <199610090740.RAA20191@rf900.physics.usyd.edu.au> Subject: Re: Java,Netscape, & AccelX To: XFree86-beta@XFree86.Org Date: Wed, 9 Oct 1996 17:40:22 +1000 (EST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199610082218.AAA22171@uriah.heep.sax.de> from "J Wunsch" at Oct 9, 96 00:18:55 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >(Sorry for the blatant crosspost. Background: Netcrap recommends >people to run a `mkfontdir' in .../lib/X11/fonts/misc/ if they >experience segfaults, and it turns out that the actual problem is that >the fonts.dir in the XFree86 distribution mismatches with the actually >installed fonts if somebody didn't install all the font packages.) > >> > So yes, this is a reason where the installation script should always >> > finally run a `mkfontdir' there. Jordan? >> >> Actually, this should be part of XF86config since FreeBSD isn't >> the only OS which could potentially suffer from this problem. >> Rich? :-) > >Hmm, XF86Config? I thought this was only for creating the config file >in /etc. Anyway, i'll move it into the XFree86 beta list then... This is part of the postinst.sh script in recent XFree86 beta releases. If that isn't sufficient, then perhaps we should stop splitting the misc fonts into two parts. David From owner-freebsd-current Wed Oct 9 00:51:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA01387 for current-outgoing; Wed, 9 Oct 1996 00:51:53 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA01371 for ; Wed, 9 Oct 1996 00:51:44 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA20836; Wed, 9 Oct 1996 09:51:16 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA16355; Wed, 9 Oct 1996 09:51:15 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id JAA25102; Wed, 9 Oct 1996 09:29:19 +0200 (MET DST) From: J Wunsch Message-Id: <199610090729.JAA25102@uriah.heep.sax.de> Subject: Re: 961006-SNAP comments To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 9 Oct 1996 09:29:19 +0200 (MET DST) Cc: danj@netcom.com Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199610090523.OAA13667@genesis.atrad.adelaide.edu.au> from Michael Smith at "Oct 9, 96 02:53:05 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Michael Smith wrote: > > --- Calculate --- > > swap = max( ( T - R ), (D * Dp) ) > > This is (I believe) invalid; you always need swap to back your RAM with. Not technically (we've got ``lazy swap''), but in practice, yes, you should have more swap than RAM. -- 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-current Wed Oct 9 01:46:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA05687 for current-outgoing; Wed, 9 Oct 1996 01:46:54 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA05652 for ; Wed, 9 Oct 1996 01:46:27 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id SAA03927; Wed, 9 Oct 1996 18:42:18 +1000 Date: Wed, 9 Oct 1996 18:42:18 +1000 From: Bruce Evans Message-Id: <199610090842.SAA03927@godzilla.zeta.org.au> To: hoek@freenet.hamilton.on.ca, msmith@atrad.adelaide.edu.au Subject: Re: 961006-SNAP comments Cc: freebsd-current@FreeBSD.org, henrich@crh.cl.msu.edu Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> (Incidentally, removing the syscons driver causes a sig12, page fault >> while in kernel mode when one continues booting)). Oops, switching from sc0/pcvt to a serial console is currently broken. When the highest priority console device is disabled (or a higher priority one is disabled) the next highest priority one is supposed to take over. If all console devices are disabled, you are supposed to get what you asked for - no console device. Only a few devices support consoles (this is a bug). Their priorities are: syscons pcvt sio0 >You can blame(?) Bruce for that; he insisted on being able to have both >syscons and pcvt in the same kernel so it had to be possible to disable >them. I don't like it for exactly the reason you've noted. It should be possible to disable any driver. It is possible to disable any isa driver. Bruce From owner-freebsd-current Wed Oct 9 01:58:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA06597 for current-outgoing; Wed, 9 Oct 1996 01:58:02 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA06588 for ; Wed, 9 Oct 1996 01:57:58 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id IAA02007; Wed, 9 Oct 1996 08:57:54 GMT Date: Wed, 9 Oct 1996 17:57:53 +0900 (JST) From: Michael Hancock To: Steven Wallace cc: current@freebsd.org Subject: Re: bugs with syn and mountd in latest snap In-Reply-To: <199610090727.AAA05826@newport.ece.uci.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Oct 1996, Steven Wallace wrote: > mountd is actually okay, although my problem was that the > loopback lo0 interface did not get started up at boot time. > > The reason was that the gethostname reslover, I have > "domain ece.uci.edu" in /etc/resolv.conf. That should search ece.uci.edu > then uci.edu, as the man page says and 2.1.5R did. However, > it now only searches ece.uci.edu. Did someone change the behavior > and if so, why? Look for 'domain searching' at www.isc.org, the caretakers of bind. Though the documents there are relevant, I think our resolv is different from the one in the bind distribution. Have you tried putting the FQDN for localhost in the hosts file? Or maybe you should put in A records in your SOAs for localhost. localhost A 127.0.0.1 Regards, Mike Hancock From owner-freebsd-current Wed Oct 9 03:05:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA11222 for current-outgoing; Wed, 9 Oct 1996 03:05:05 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA11212 for ; Wed, 9 Oct 1996 03:05:01 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id DAA21078; Wed, 9 Oct 1996 03:04:56 -0700 (PDT) To: Jim Shankland cc: jmb@freefall.freebsd.org, blh@nol.net, current@freebsd.org Subject: Re: ok, look folks In-reply-to: Your message of "Tue, 08 Oct 1996 09:25:27 PDT." <199610081625.JAA24825@saguaro.flyingfox.com> Date: Wed, 09 Oct 1996 03:04:56 -0700 Message-ID: <21075.844855496@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > True enough, but sometimes people don't *know* what they > subscribed as. Not everyone is all that knowledgable about > mail systems, or in control of the mail system they're using. No problem. 1. Send email to majordomo@freebsd.org saying "help". 2. It sends you back a list of commands. 3. You notice that one of those commands allows you to receive a copy of all the users on a list. 4. You figure out which one you are and you send the deletion request. I'm sorry, but this is an open and shut case of someone who found it easier to yell and scream than do his homework. Not the best of first impressions, and certainly one which will stick with me for awhile. Fortunately for Jim, it's also unlikely that anyone will ever ask me for a reference. Jordan From owner-freebsd-current Wed Oct 9 03:10:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA11533 for current-outgoing; Wed, 9 Oct 1996 03:10:16 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA11527 for ; Wed, 9 Oct 1996 03:10:14 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id DAA21101; Wed, 9 Oct 1996 03:10:12 -0700 (PDT) To: Charles Henrich cc: freebsd-current@freebsd.org Subject: Re: 961006-SNAP comments In-reply-to: Your message of "Tue, 08 Oct 1996 13:10:27 EDT." <199610081710.NAA00777@crh.cl.msu.edu> Date: Wed, 09 Oct 1996 03:10:12 -0700 Message-ID: <21098.844855812@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The forced visual config on install is a horrible thing. Forced config is a I think this will be a matter of opinion, and you may rest assured that I won't do anything to change it until I've collected a reasonable amount of feedback on it. If it's predominantly negative, then I'll certianly nuke it. Another thing that occurred to me about an hour after I released the boot floppy was that detecting "Q" or "ESC" as special values for the "any" key in intro and assume an immediate quit would probably be a good idea. Would that make you any happier? For the rest of the users who just aren't RTFM'ing and setting their hardware up properly (sending a message to us which then gets 5 replies all saying "Boot -c!"), I think this feature is just plain mandatory. It's not like I set your on-disk kernel up like this either, it only happens once. You must have a very low capacity for tedium. :-) > The installation process froze my keyboard (Flipping between alt-f1 alt-f2) > about half way through the install, after it completed it popped my back to t he > main console and unlocked the keyboard. Hmm, sounds like one for Soren. > The install refused to update my /etc/ files because a piece of the > installation failed. That doesnt really make a whole lot of since, especial ly > as the piece that failed was compat21. There was nothing I could figure out Yeah, I changed the policy on touching /etc to be a bit more paranoid, and it looks like I'm checking more failure cases than I should be. I'll fix it, thanks. Jordan From owner-freebsd-current Wed Oct 9 03:16:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA11949 for current-outgoing; Wed, 9 Oct 1996 03:16:10 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA11902; Wed, 9 Oct 1996 03:15:51 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id KAA16977; Wed, 9 Oct 1996 10:32:14 +0100 Date: Wed, 9 Oct 1996 10:32:13 +0100 (BST) From: Doug Rabson To: Hidetoshi Shimokawa cc: freebsd-bugs@freebsd.org, freebsd-current@freebsd.org Subject: Re: NFS from Solaris Server In-Reply-To: <15438.844844779@sat.t.u-tokyo.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [hackers removed from Cc list] On Wed, 9 Oct 1996, Hidetoshi Shimokawa wrote: > [snip] > > I am looking into this problem since yesterday, adding some debuging > code into kernel. The following is some results around this. > > The system is, > > PentiumPro 100M Ether Sun Ultra Wide SCSI > FreeBSD-current <--------------> Solaris 2.5 --------- Disk > NFSv2 client NFSv2 server 6MB/s(iozone) > > and I mesured performance by iozone. > With the default setting (with 4 nfsiods), I can get only 300KB/s. > - With NFSv3, I got around 500KB-600KB. > - SS20 <-> Sun Ultra gets around 800KB/s.) > > 1) A faster client(pentium class) gets less performance than a slower > client(486 class). > > 2) After I killed all async daemon (nfsiod), I got 400KB/s, this seems > funny :-). > > 3) By added some debugging code, I found that the performance > reduction happens when the nfsiods are all busy and the buffer > is marked as B_DELWRI(delayed write) in nfs_asyncio() (/sys/nfs/nfs_bio.c). > This explains 1). > > 4) I changed the code so that nfs_asyncio returns with EIO before > marks B_DELWRI, then I got 800-900KB/s. > I think this algorithm is essentially same as 2.1.5 or BSDI 2.1. > > 5) It is interesting that the change above doesn't improve v3 performance. > > 6) I don't know how delayed write scheme is efficient, but at this > point, it is a bottleneck. It is because, after a nfsbiod starts > processiong the delayed write buffer in nfssvc_iod() (nfs_syscalls.c), > other nfsbiods stop its work. I confirmed by debugging code in > kernel, but it can be also easily observed by I was just looking at the code and returning EIO from nfs_asyncio would work. The effect it would have is to perform the rpc synchronously in the context of the writer instead of asynchronously in the context of one of the iods. If the server was able to avoid the 'write to stable storage' requirement of NFSv2 (either because of NVRAM or because it is cheating) then this would not be too inefficient. I am not sure why the delayed write handling would lock out the other iods. Maybe it is caused by the loop in nfssvc_iod which tries to flush out all the delayed write buffers in the vnode. It may be that the writing process is adding buffers at the same rate as the iod is writing them and the race is locking out the other iods. It might be worth experimenting with this code to limit the number of buffers it processes with the loop. > > % iozone & sleep 2; cat /proc/"nfsiod's pid"/status > > nfsiod 15057 1 15056 0 -1,-1 noflags 844842823,10788 0,0 0,78906 sbwait 0 0 0,0,0,5,2,3,4,20,31 > nfsiod 15058 1 15056 0 -1,-1 noflags 844842823,10874 0,0 0,30899 nfsrcvlk 0 0 0,0,0,5,2,3,4,20,31 > nfsiod 15059 1 15056 0 -1,-1 noflags 844842823,10939 0,0 0,3486 nfsrcvlk 0 0 0,0,0,5,2,3,4,20,31 > nfsiod 15060 1 15056 0 -1,-1 noflags 844842823,11001 0,0 0,1694 nfsrcvlk 0 0 0,0,0,5,2,3,4,20,31 > nfsiod 15061 1 15056 0 -1,-1 noflags 844842823,11061 0,0 0,1395 nfsrcvlk 0 0 0,0,0,5,2,3,4,20,31 > nfsiod 15062 1 15056 0 -1,-1 noflags 844842823,11119 0,0 0,1601 nfsrcvlk 0 0 0,0,0,5,2,3,4,20,31 > nfsiod 15063 1 15056 0 -1,-1 noflags 844842823,11176 0,0 0,1339 nfsrcvlk 0 0 0,0,0,5,2,3,4,20,31 > nfsiod 15064 1 15056 0 -1,-1 noflags 844842823,11233 0,0 0,1277 nfsrcvlk 0 0 0,0,0,5,2,3,4,20,31 > > All nfsiods except one are locked at nfs_rcvlock (nfs_socket.c) for long time. > By tcpdump, server did reply but nfsiod can not process it for locking. > I'm not familiar with NFS and kernel programming but > it seems that current code has locking problem. > > I don't know how to fix it, please help, NFS and kernel experts! > > (Isn't it needed to be non-interruptable for the code between nfs_send and > nfs_rcvlock in nfs_request() and nfs_reply()?) > > I also like to know why NFSv3 client is so slow. NFSv3 in current has a bug where uncommitted unstably written buffers can later be rewritten to the server synchronously. This patch fixes this bug as well as improving the code which sends commit rpcs to the server to reduce the number of rpcs needed. It also marks buffers of uncommitted data so that they can be cluster-committed automatically by the bio system. Index: nfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_bio.c,v retrieving revision 1.25 diff -u -r1.25 nfs_bio.c --- nfs_bio.c 1996/09/19 18:20:54 1.25 +++ nfs_bio.c 1996/10/09 09:10:07 @@ -905,9 +905,11 @@ iomode = NFSV3WRITE_FILESYNC; bp->b_flags |= B_WRITEINPROG; error = nfs_writerpc(vp, uiop, cr, &iomode, &must_commit); - if (!error && iomode == NFSV3WRITE_UNSTABLE) + if (!error && iomode == NFSV3WRITE_UNSTABLE) { bp->b_flags |= B_NEEDCOMMIT; - else + if (bp->b_dirtyoff == 0 && bp->b_dirtyend == bp->b_bufsize) + bp->b_flags |= B_CLUSTEROK; + } else bp->b_flags &= ~B_NEEDCOMMIT; bp->b_flags &= ~B_WRITEINPROG; Index: nfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_vnops.c,v retrieving revision 1.35 diff -u -r1.35 nfs_vnops.c --- nfs_vnops.c 1996/09/19 18:21:01 1.35 +++ nfs_vnops.c 1996/10/09 09:10:15 @@ -1210,7 +1210,10 @@ tsiz -= len; } nfsmout: - *iomode = committed; + if (vp->v_mount->mnt_flag & MNT_ASYNC) + *iomode = NFSV3WRITE_FILESYNC; + else + *iomode = committed; if (error) uiop->uio_resid = tsiz; return (error); @@ -2607,6 +2610,9 @@ int error = 0, wccflag = NFSV3_WCCRATTR; struct mbuf *mreq, *mrep, *md, *mb, *mb2; +#ifdef NFS_DEBUG + printf("nfs_commit(%x, %d, %d, %x, %x)\n", vp, (int) offset, cnt, cred, procp); +#endif if ((nmp->nm_flag & NFSMNT_HASWRITEVERF) == 0) return (0); nfsstats.rpccnt[NFSPROC_COMMIT]++; @@ -2757,13 +2763,14 @@ struct nfsmount *nmp = VFSTONFS(vp->v_mount); int s, error = 0, slptimeo = 0, slpflag = 0, retv, bvecpos; int passone = 1; - u_quad_t off = (u_quad_t)-1, endoff = 0, toff; + u_quad_t off, endoff, toff; struct ucred* wcred = NULL; -#ifndef NFS_COMMITBVECSIZ -#define NFS_COMMITBVECSIZ 20 -#endif - struct buf *bvec[NFS_COMMITBVECSIZ]; + struct buf **bvec = NULL; + int bvecsize = 0, bveccount; +#ifdef NFS_DEBUG + printf("nfs_flush(%x, %x, %d, %x, %d)\n", vp, cred, waitfor, p, commit); +#endif if (nmp->nm_flag & NFSMNT_INT) slpflag = PCATCH; if (!commit) @@ -2776,12 +2783,41 @@ * job. */ again: + off = (u_quad_t)-1; + endoff = 0; bvecpos = 0; if (NFS_ISV3(vp) && commit) { s = splbio(); + /* + * Count up how many buffers waiting for a commit. + */ + bveccount = 0; + for (bp = vp->v_dirtyblkhd.lh_first; bp; bp = nbp) { + nbp = bp->b_vnbufs.le_next; + if ((bp->b_flags & (B_BUSY | B_DELWRI | B_NEEDCOMMIT)) + == (B_DELWRI | B_NEEDCOMMIT)) + bveccount++; + } + /* + * Allocate space to remember the list of bufs to commit. It is + * important to use M_NOWAIT here to avoid a race with nfs_write. + * If we can't get memory (for whatever reason), we will end up + * committing the buffers one-by-one in the loop below. + */ + if (bveccount > bvecsize) { + if (bvec != NULL) + free(bvec, M_TEMP); + bvec = (struct buf **) + malloc(bveccount * sizeof(struct buf *), + M_TEMP, M_NOWAIT); + if (bvec == NULL) + bvecsize = 0; + else + bvecsize = bveccount; + } for (bp = vp->v_dirtyblkhd.lh_first; bp; bp = nbp) { nbp = bp->b_vnbufs.le_next; - if (bvecpos >= NFS_COMMITBVECSIZ) + if (bvecpos >= bvecsize) break; if ((bp->b_flags & (B_BUSY | B_DELWRI | B_NEEDCOMMIT)) != (B_DELWRI | B_NEEDCOMMIT)) @@ -2822,10 +2858,14 @@ * one call for all of them, otherwise commit each one * separately. */ - if (wcred != NOCRED) + if (wcred != NOCRED) { +#ifdef NFS_DEBUG +printf("nfs_flush: calling nfs_commit(%x, %d, %d, %x, %x)\n", + vp, (int) off, (int) (endoff - off), wcred, p); +#endif retv = nfs_commit(vp, off, (int)(endoff - off), wcred, p); - else { + } else { retv = 0; for (i = 0; i < bvecpos; i++) { off_t off, size; @@ -2879,8 +2919,10 @@ "nfsfsync", slptimeo); splx(s); if (error) { - if (nfs_sigintr(nmp, (struct nfsreq *)0, p)) - return (EINTR); + if (nfs_sigintr(nmp, (struct nfsreq *)0, p)) { + error = EINTR; + goto done; + } if (slpflag == PCATCH) { slpflag = 0; slptimeo = 2 * hz; @@ -2892,6 +2934,9 @@ panic("nfs_fsync: not dirty"); if ((passone || !commit) && (bp->b_flags & B_NEEDCOMMIT)) continue; +#ifdef NFS_DEBUG +printf("nfs_flush: writing bp=%x, bp->b_flags=%x\n", bp, bp->b_flags); +#endif bremfree(bp); if (passone || !commit) bp->b_flags |= (B_BUSY|B_ASYNC); @@ -2912,8 +2957,10 @@ error = tsleep((caddr_t)&vp->v_numoutput, slpflag | (PRIBIO + 1), "nfsfsync", slptimeo); if (error) { - if (nfs_sigintr(nmp, (struct nfsreq *)0, p)) - return (EINTR); + if (nfs_sigintr(nmp, (struct nfsreq *)0, p)) { + error = EINTR; + goto done; + } if (slpflag == PCATCH) { slpflag = 0; slptimeo = 2 * hz; @@ -2928,6 +2975,9 @@ error = np->n_error; np->n_flag &= ~NWRITEERR; } +done: + if (bvec) + free(bvec, M_TEMP); return (error); } @@ -3129,8 +3179,9 @@ * an actual write will have to be scheduled via. VOP_STRATEGY(). * If B_WRITEINPROG is already set, then push it with a write anyhow. */ - if (oldflags & (B_NEEDCOMMIT | B_WRITEINPROG) == B_NEEDCOMMIT) { + if ((oldflags & (B_NEEDCOMMIT | B_WRITEINPROG)) == B_NEEDCOMMIT) { off = ((u_quad_t)bp->b_blkno) * DEV_BSIZE + bp->b_dirtyoff; + vfs_busy_pages(bp, 1); bp->b_flags |= B_WRITEINPROG; retv = nfs_commit(bp->b_vp, off, bp->b_dirtyend-bp->b_dirtyoff, bp->b_wcred, bp->b_proc); @@ -3139,8 +3190,10 @@ bp->b_dirtyoff = bp->b_dirtyend = 0; bp->b_flags &= ~B_NEEDCOMMIT; biodone(bp); - } else if (retv == NFSERR_STALEWRITEVERF) + } else if (retv == NFSERR_STALEWRITEVERF) { nfs_clearcommit(bp->b_vp->v_mount); + vfs_unbusy_pages(bp); + } } if (retv) { if (force) -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 734 3761 FAX: +44 171 734 6426 From owner-freebsd-current Wed Oct 9 03:49:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA14876 for current-outgoing; Wed, 9 Oct 1996 03:49:44 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA14869 for ; Wed, 9 Oct 1996 03:49:39 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id DAA21401; Wed, 9 Oct 1996 03:49:38 -0700 (PDT) To: Steven Wallace cc: current@freebsd.org Subject: Re: bugs with syn and mountd in latest snap In-reply-to: Your message of "Tue, 08 Oct 1996 13:24:32 PDT." <199610082024.NAA11993@imperial.ece.uci.edu> Date: Wed, 09 Oct 1996 03:49:38 -0700 Message-ID: <21399.844858178@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Please let me know when these bugs are fixed. You'll have to watch the mailing lists, like everyone else. We don't operate a reminder service here. :-) Jordan From owner-freebsd-current Wed Oct 9 04:04:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA16121 for current-outgoing; Wed, 9 Oct 1996 04:04:32 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA16111 for ; Wed, 9 Oct 1996 04:04:27 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id EAA21521; Wed, 9 Oct 1996 04:04:22 -0700 (PDT) To: Tim Vanderhoek cc: Charles Henrich , freebsd-current@freebsd.org Subject: Re: 961006-SNAP comments In-reply-to: Your message of "Tue, 08 Oct 1996 17:40:15 EDT." Date: Wed, 09 Oct 1996 04:04:22 -0700 Message-ID: <21519.844859062@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > all devices which they don't have. I think it should be reworded to say > "know you don't have", to prevent removal of something important ("syscons I think that's a reasonable point - I'll do this. Jordan From owner-freebsd-current Wed Oct 9 04:26:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA18049 for current-outgoing; Wed, 9 Oct 1996 04:26:24 -0700 (PDT) Received: from pillar.elsevier.co.uk (root@pillar.elsevier.co.uk [193.131.222.35]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA18040 for ; Wed, 9 Oct 1996 04:26:22 -0700 (PDT) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by pillar.elsevier.co.uk (8.8.0/8.8.0) with ESMTP id MAA21821 for ; Wed, 9 Oct 1996 12:23:38 +0100 (BST) Received: from cadair.elsevier.co.uk by snowdon.elsevier.co.uk with SMTP (PP); Wed, 9 Oct 1996 12:25:32 +0100 Received: from tees.elsevier.co.uk (tees.elsevier.co.uk [193.131.197.60]) by cadair.elsevier.co.uk (8.8.0/8.8.0) with ESMTP id MAA16071; Wed, 9 Oct 1996 12:25:26 +0100 (BST) Received: (from dpr@localhost) by tees.elsevier.co.uk (8.8.0/8.8.0) id MAA06265; Wed, 9 Oct 1996 12:24:29 +0100 (BST) To: Dan Janowski Cc: current@freebsd.org Subject: Re: Best mail for threaded majordomo reading? References: <3259C7E9.41C67EA6@netcom.com> From: Paul Richards Date: 09 Oct 1996 12:24:28 +0100 In-Reply-To: Dan Janowski's message of Mon, 07 Oct 1996 23:18:01 -0400 Message-ID: <57lodgfkib.fsf@tees.elsevier.co.uk> Lines: 49 X-Mailer: Gnus v5.3/Emacs 19.30 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dan Janowski writes: > What are you guys using? I am using netscape > mail which does threading and mbox-es nicely, but > it has some annoying deficiencies. What is a > good way of auto-processing all the mail into > separate mbox-es, i.e. put list mail somewhere > different than "regular" mail? Well, I re-subscribed to *all* the FreeBSD lists a few months ago after a lengthy break and the first thing I did was evaluate mail readers so it was feasible to stay subscribed. The solution I'd recommend *VERY* strongly is Emacs/Gnus. It has lots of features useful for reading these lists: 1) It's a news reader that has a mail interface so you can filter incoming mail into what look like newsgroups (this is not the same as piping mail into news since these are not real newsgroups). You can choose from a number of backend drivers for mail storage, I use nnml format for incoming mail and nnfolder format for long term archiving. "nnml" looks like a news spool, "nnfolder" is just like a normal mail folder so I can use elm etc on it. You can filter the separate mailing lists into individual groups or merge them into common groups or you can do the selection on subject or author or something else. Very flexible and totally configurable. 2) It removes duplicate postings from multiple mailing lists so I only ever see one copy of a posting, this is *really* nice :-) 3) You can do ranking on subjects so things you're interested have more prominence. 4) It does expiry (just like news) so if I don't read questions for a few days they just go away :-) Personal mail doesn't have expiry enabled but the big, general lists have aggressive expiry, again all very flexible and configurable. I wouldn't survive the massive mail load without gnus, given that I'm a serious vi advocate and consider Emacs to be a resource devouring beast you can appreciate that it must be pretty good for me to have switched to an Emacs based solution :-) -- Paul Richards. Originative Solutions Ltd. (Netcraft Ltd. contractor) Elsevier Science TIS online journal project. Email: p.richards@elsevier.co.uk Phone: 0370 462071 (Mobile), +44 (0)1865 843155 From owner-freebsd-current Wed Oct 9 04:26:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA18061 for current-outgoing; Wed, 9 Oct 1996 04:26:27 -0700 (PDT) Received: from bourbon.sfc.wide.ad.jp (root@bourbon.sfc.wide.ad.jp [133.4.30.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA18046 for ; Wed, 9 Oct 1996 04:26:23 -0700 (PDT) Received: from bourbon (max@localhost [127.0.0.1]) by bourbon.sfc.wide.ad.jp (8.7.6/3.4W409/27/96) with ESMTP id UAA00310; Wed, 9 Oct 1996 20:26:21 +0900 (JST) Message-Id: <199610091126.UAA00310@bourbon.sfc.wide.ad.jp> To: freebsd-current@freebsd.org Cc: max@wide.ad.jp Subject: ldconfig problem From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= X-Mailer: Mew version 1.06 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 09 Oct 1996 20:26:21 +0900 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I found strange behavior of ldconfig, (or it might be ld.so, or whatever.) I'm running FreeBSD-current as of CTM delta up to src-cur.2287 applied. The problem is that it looks like ldconfig isn't properly updating the cache. I have kaffe and m3 ports installed on my system. And after I do (or /etc/rc does): ldconfig /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib /usr/local/lib/m3/FreeBSD2 executing kaffe causes bus error and dumps core. However, if I only do: ldconfig /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib then, execution of kaffe goes ok. Could anyone look into this problem? Or please let me know if anyone found something wrong with what I'm doing. Thanks. ----------------------------------------------------------------------- Masafumi NAKANE, Keio Univ., Dept. of Environmental Information E-Mail : max@wide.ad.jp / max@FreeBSD.ORG [URL] : http://www.sfc.wide.ad.jp/~max/ From owner-freebsd-current Wed Oct 9 04:37:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA18825 for current-outgoing; Wed, 9 Oct 1996 04:37:00 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA18820; Wed, 9 Oct 1996 04:36:57 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id EAA21793; Wed, 9 Oct 1996 04:35:46 -0700 (PDT) To: Luigi Rizzo cc: freebsd-current@freebsd.org, jkh@freebsd.org Subject: Re: More 961006-SNAP comments In-reply-to: Your message of "Wed, 09 Oct 1996 05:02:06 BST." <199610090402.FAA02243@labinfo.iet.unipi.it> Date: Wed, 09 Oct 1996 04:35:46 -0700 Message-ID: <21791.844860946@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 1. I tried to build a new kernel, and the build produces a ton of > warnings about unused parameters, signed/unsigned comparisons, and You should read this list - all of this is old and musty news at this point and previously discussed to death. :-) > 2. I copied parts of the distribution on a local partition and completed > the install at a later time. The progress line reports a speed of > ~30 KB/s (and even lower when there is a kernel build going on). > I can't figure out why it is so slow, even if the disk heads are Hmmm. Me neither! > 3. there is a "locate.pl" file in /sys/pci. leftover from something ? Evidently it's in the tree for some reason. > 4. since there is a nice mouse support in text mode now (and I am > enjoying it more and more) it could be the case to try to exploit > it in the installation process. Don't know how hard would it be to > integrate it into the current code. Very. Forget it. :-) If you're up to hacking libdialog, that's great, but don't look at me. It's too crufty in there. > 5. In the install menu, when I try to select "Media" to select a > different FTP server, it does not allow me to do so. I have to Yeah, I just figured out a better way of doing this too so that you get more what you'd expect. Will fix. > From what I have seen this far, there appears not to be functional > problems in the code, but perhaps some "youth" problems in the install > code. Maybe it's worth waiting the next snap before putting things on a > CD ? I think so, actually, especially as I'd *really like* to get the userconfig saving stuff working. The network snaps I don't feel too guilty about re-rolling every other week since the whole concept is supposed to be about testing, not conserving network bandwidth. :-) Jordan From owner-freebsd-current Wed Oct 9 05:30:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA21476 for current-outgoing; Wed, 9 Oct 1996 05:30:22 -0700 (PDT) Received: from nol.net (root@dazed.nol.net [206.126.32.101]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA21470 for ; Wed, 9 Oct 1996 05:30:20 -0700 (PDT) Received: from dazed.nol.net (blh@dazed.nol.net [206.126.32.101]) by nol.net (8.8.0/NOL - 8.*) with SMTP id HAA27672; Wed, 9 Oct 1996 07:29:30 -0500 (CDT) X-AUTH: NOLNET SENDMAIL AUTH Date: Wed, 9 Oct 1996 07:29:29 -0500 (CDT) From: "Brett L. Hawn" To: "Jordan K. Hubbard" cc: Jim Shankland , jmb@freefall.freebsd.org, current@freebsd.org Subject: Re: ok, look folks In-Reply-To: <21075.844855496@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've run majordomo before, I hack sendmail here at the office, I think I know what I'm doing. However WHENN I subscribed, I did so as blh@nol.net, NOT blh@dazed.nol.net, so yes.. I got a little frustrated with the fact that majordomo in its infinit crappiness, changed my subscribe address and made it a nightmare to unsubscribe. I think you know very little about me, and even less about what you're talking about. I was pleasant and nice for almost 3 months before I got pissed off enough to yell at the list. I sent email to majordomo-owner, root, admin, postmaster, and about a dozen other addresses asking to be removed, nicely, it got me nowhere. You will now however note, that I'm not on the list anymore, sometimes it just takes being an asshole to get things done *shrug*. On Wed, 9 Oct 1996, Jordan K. Hubbard wrote: > > > True enough, but sometimes people don't *know* what they > > subscribed as. Not everyone is all that knowledgable about > > mail systems, or in control of the mail system they're using. > > No problem. > > 1. Send email to majordomo@freebsd.org saying "help". > 2. It sends you back a list of commands. > 3. You notice that one of those commands allows you to receive a copy > of all the users on a list. > 4. You figure out which one you are and you send the deletion request. > > I'm sorry, but this is an open and shut case of someone who found it > easier to yell and scream than do his homework. Not the best of first > impressions, and certainly one which will stick with me for awhile. > Fortunately for Jim, it's also unlikely that anyone will ever ask me > for a reference. > > Jordan > [-] Brett L. Hawn (blh@nol.net) [-] [-] Networks On-Line - Houston, Texas [-] [-] 713-467-7100 [-] From owner-freebsd-current Wed Oct 9 05:55:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA22645 for current-outgoing; Wed, 9 Oct 1996 05:55:29 -0700 (PDT) Received: from vanuata (vanuata.dcs.gla.ac.uk [130.209.240.50]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA22639 for ; Wed, 9 Oct 1996 05:55:24 -0700 (PDT) Message-Id: <199610091255.FAA22639@freefall.freebsd.org> Received: from solander by vanuata with SMTP (MMTA); Wed, 9 Oct 1996 13:54:44 +0100 To: "Brett L. Hawn" cc: "Jordan K. Hubbard" , Jim Shankland , jmb@freefall.freebsd.org, current@freebsd.org Subject: Re: ok, look folks In-reply-to: Your message of "Wed, 09 Oct 1996 07:29:29 CDT." Date: Wed, 09 Oct 1996 13:54:38 +0100 From: Simon Marlow Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I've run majordomo before, I hack sendmail here at the office, I think I > know what I'm doing. However WHENN I subscribed, I did so as blh@nol.net, > NOT blh@dazed.nol.net, so yes.. I got a little frustrated with the fact that > majordomo in its infinit crappiness, changed my subscribe address and made > it a nightmare to unsubscribe. It's fairly easy to forge some mail from your original email address to get yourself off these lists. I've had to do it several times. Perhaps we should put it in the FAQ :) Cheers, Simon -- Simon Marlow simonm@dcs.gla.ac.uk Research Assistant http://www.dcs.gla.ac.uk/~simonm/ finger for PGP public key From owner-freebsd-current Wed Oct 9 06:01:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA22997 for current-outgoing; Wed, 9 Oct 1996 06:01:56 -0700 (PDT) Received: from po2.glue.umd.edu (po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA22991 for ; Wed, 9 Oct 1996 06:01:54 -0700 (PDT) Received: from skipper.eng.umd.edu (skipper.eng.umd.edu [129.2.103.24]) by po2.glue.umd.edu (8.8.0/8.7.3) with ESMTP id JAA29262; Wed, 9 Oct 1996 09:01:50 -0400 (EDT) Received: from localhost (chuckr@localhost) by skipper.eng.umd.edu (8.7.5/8.7.3) with SMTP id JAA19092; Wed, 9 Oct 1996 09:01:49 -0400 (EDT) X-Authentication-Warning: skipper.eng.umd.edu: chuckr owned process doing -bs Date: Wed, 9 Oct 1996 09:01:49 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@skipper.eng.umd.edu To: "Jordan K. Hubbard" cc: Jim Shankland , jmb@freefall.freebsd.org, blh@nol.net, current@freebsd.org Subject: Re: ok, look folks In-Reply-To: <21075.844855496@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Oct 1996, Jordan K. Hubbard wrote: > > True enough, but sometimes people don't *know* what they > > subscribed as. Not everyone is all that knowledgable about > > mail systems, or in control of the mail system they're using. I've personally handled at least a half dozen cases like this in the last year. If they're even minimally gracious, it's no problem. Having a tantrum on the mailing list is not really great behaviour. > > No problem. > > 1. Send email to majordomo@freebsd.org saying "help". > 2. It sends you back a list of commands. > 3. You notice that one of those commands allows you to receive a copy > of all the users on a list. > 4. You figure out which one you are and you send the deletion request. > > I'm sorry, but this is an open and shut case of someone who found it > easier to yell and scream than do his homework. Not the best of first > impressions, and certainly one which will stick with me for awhile. > Fortunately for Jim, it's also unlikely that anyone will ever ask me > for a reference. > > Jordan > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Wed Oct 9 06:07:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA23227 for current-outgoing; Wed, 9 Oct 1996 06:07:09 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA23222 for ; Wed, 9 Oct 1996 06:07:07 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.7.6/8.7.3) id JAA05163; Wed, 9 Oct 1996 09:06:58 -0400 (EDT) From: Charles Henrich Message-Id: <199610091306.JAA05163@crh.cl.msu.edu> Subject: Re: 961006-SNAP comments To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 9 Oct 1996 09:06:58 -0400 (EDT) Cc: hoek@freenet.hamilton.on.ca, freebsd-current@freebsd.org In-Reply-To: <21519.844859062@time.cdrom.com> from "Jordan K. Hubbard" at "Oct 9, 96 04:04:22 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > all devices which they don't have. I think it should be reworded to say > > "know you don't have", to prevent removal of something important ("syscons > > I think that's a reasonable point - I'll do this. Why are we forcing people who probably have no clue to go mucking with the device table? I've done hundreds of FreeBSD installs and the generic kernel has always booted just peachy with me. It seems that dumping people into a fairly unfriendly (granted much better than command line) device editor as the first thing they do is definatly not a good idea! -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-current Wed Oct 9 06:30:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA24553 for current-outgoing; Wed, 9 Oct 1996 06:30:51 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA24546 for ; Wed, 9 Oct 1996 06:30:48 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.7.6/8.7.3) id JAA05706; Wed, 9 Oct 1996 09:30:44 -0400 (EDT) From: Charles Henrich Message-Id: <199610091330.JAA05706@crh.cl.msu.edu> Subject: Re: 961006-SNAP comments To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 9 Oct 1996 09:30:44 -0400 (EDT) Cc: freebsd-current@freebsd.org In-Reply-To: <21098.844855812@time.cdrom.com> from "Jordan K. Hubbard" at "Oct 9, 96 03:10:12 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Another thing that occurred to me about an hour after I released the > boot floppy was that detecting "Q" or "ESC" as special values for the > "any" key in intro and assume an immediate quit would probably be a > good idea. Would that make you any happier? > > For the rest of the users who just aren't RTFM'ing and setting their > hardware up properly (sending a message to us which then gets 5 > replies all saying "Boot -c!"), I think this feature is just plain > mandatory. It's not like I set your on-disk kernel up like this > either, it only happens once. You must have a very low capacity for > tedium. :-) Im concerned about the average user who has no idea what that device table is, or what to do with it. They could easily break things, and I would wager that in the general case, the default settings are quite appropriate. How many problems will be generated by people disabling the wrong things, or stumbling around inside the editor just mucking things up because they dont know what they are doing? The tedium piece comes from the fact that I do *alot* of FreeBSD installs, if the forced config must stay, a Q would be great. (I still however think forcing a config will cause more problems than not). If we force a config it has to be brain damaged, i.e: Do you have an Adaptec 2940 SCSI Controller (Yes/No) Do you have an NE2000 Compatable Ethernet Card (Yes/No) Yes: What IRQ is this card located at? What IOMEM Address does this card use? etc.. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-current Wed Oct 9 06:55:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA25866 for current-outgoing; Wed, 9 Oct 1996 06:55:28 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA25860 for ; Wed, 9 Oct 1996 06:55:24 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id GAA23005; Wed, 9 Oct 1996 06:55:10 -0700 (PDT) Message-Id: <199610091355.GAA23005@austin.polstra.com> To: max@wide.ad.jp Cc: freebsd-current@freebsd.org Subject: Re: ldconfig problem In-reply-to: <199610091126.UAA00310@bourbon.sfc.wide.ad.jp> Date: Wed, 09 Oct 1996 06:55:09 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I have kaffe and m3 ports installed on my system. And after I do (or > /etc/rc does): > > ldconfig /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib > /usr/local/lib/m3/FreeBSD2 > > executing kaffe causes bus error and dumps core. > > However, if I only do: > > ldconfig /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib > > then, execution of kaffe goes ok. Please run "ldd" on the kaffe executable in both the failing and successful situations, and let us know what it prints out. 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-current Wed Oct 9 07:09:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA26291 for current-outgoing; Wed, 9 Oct 1996 07:09:01 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA26282 for ; Wed, 9 Oct 1996 07:08:58 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id JAA16882; Wed, 9 Oct 1996 09:06:44 -0500 From: Joe Greco Message-Id: <199610091406.JAA16882@brasil.moneng.mei.com> Subject: Re: 961006-SNAP comments To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Wed, 9 Oct 1996 09:06:44 -0500 (CDT) Cc: jkh@time.cdrom.com, hoek@freenet.hamilton.on.ca, freebsd-current@FreeBSD.org In-Reply-To: <199610091306.JAA05163@crh.cl.msu.edu> from "Charles Henrich" at Oct 9, 96 09:06:58 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > all devices which they don't have. I think it should be reworded to say > > > "know you don't have", to prevent removal of something important ("syscons > > > > I think that's a reasonable point - I'll do this. > > Why are we forcing people who probably have no clue to go mucking with the > device table? I've done hundreds of FreeBSD installs and the generic kernel > has always booted just peachy with me. It seems that dumping people into a > fairly unfriendly (granted much better than command line) device editor as the > first thing they do is definatly not a good idea! Maybe "boot -c" should invoke the visual configuration rather than the command line configuration utility... but it should not be entered by default. Just a thought as I haven't seen this SNAP. It just seems more intuitive to me. ... JG From owner-freebsd-current Wed Oct 9 07:17:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA26789 for current-outgoing; Wed, 9 Oct 1996 07:17:25 -0700 (PDT) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA26782; Wed, 9 Oct 1996 07:17:22 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199610091417.HAA26782@freefall.freebsd.org> Subject: Re: ok, look folks To: blh@nol.net (Brett L. Hawn) Date: Wed, 9 Oct 1996 07:17:21 -0700 (PDT) Cc: jkh@time.cdrom.com, jas@flyingfox.COM, current@freebsd.org In-Reply-To: from "Brett L. Hawn" at Oct 9, 96 07:29:29 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Brett L. Hawn wrote: > > I've run majordomo before, I hack sendmail here at the office, I think I > know what I'm doing. However WHENN I subscribed, I did so as blh@nol.net, > NOT blh@dazed.nol.net, so yes.. I got a little frustrated with the fact that the logs disagree with you. May 04 08:28:06 freefall.freebsd.org majordomo[10962] {"" } s ubscribe freebsd-questions "" May 04 08:28:12 freefall.freebsd.org majordomo[10962] {"" } s ubscribe freebsd-hackers "" May 04 08:28:17 freefall.freebsd.org majordomo[10962] {"" } s ubscribe freebsd-current "" before critisizing majordomo, you should check your own statements. > majordomo in its infinit crappiness, changed my subscribe address and made > it a nightmare to unsubscribe. I think you know very little about me, and > even less about what you're talking about. I was pleasant and nice for > almost 3 months before I got pissed off enough to yell at the list. I sent > email to majordomo-owner, root, admin, postmaster, and about a dozen other i may be mistaken, but i *NEVER* received mail from you asking to be removed. or asking for help. you send mail to majorodmo several times asking for help, for instance Sep 02 12:10:38 freefall.freebsd.org majordomo[7590] {"Brett L. Hawn" } help Sep 02 12:20:19 freefall.freebsd.org majordomo[8050] {"Brett L. Hawn" } help but you either did not receive, hte help message, do not understand it, or did not act on it. > addresses asking to be removed, nicely, it got me nowhere. You will now > however note, that I'm not on the list anymore, sometimes it just takes > being an asshole to get things done *shrug*. now please drop this thread. you have embarassed yourself enough in public. jmb -- Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG FreeBSD--4.4BSD Unix for PC clones, source included. http://www.freebsd.org/ PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB From owner-freebsd-current Wed Oct 9 07:48:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA28504 for current-outgoing; Wed, 9 Oct 1996 07:48:29 -0700 (PDT) Received: from bourbon.sfc.wide.ad.jp (root@bourbon.sfc.wide.ad.jp [133.4.30.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA28498 for ; Wed, 9 Oct 1996 07:48:26 -0700 (PDT) Received: from bourbon (max@localhost [127.0.0.1]) by bourbon.sfc.wide.ad.jp (8.7.6/3.4W409/27/96) with ESMTP id XAA01502; Wed, 9 Oct 1996 23:48:10 +0900 (JST) Message-Id: <199610091448.XAA01502@bourbon.sfc.wide.ad.jp> To: jdp@polstra.com Cc: max@wide.ad.jp, freebsd-current@freebsd.org Subject: Re: ldconfig problem From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= In-Reply-To: Your message of "Wed, 09 Oct 1996 06:55:09 -0700" References: <199610091355.GAA23005@austin.polstra.com> X-Mailer: Mew version 1.06 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 09 Oct 1996 23:48:10 +0900 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk jdp> Please run "ldd" on the kaffe executable in both the failing jdp> and successful situations, and let us know what it prints jdp> out. Ok, here it is. Successful one: /usr/local/bin/kaffe: -lkaffe_vm.0 => /usr/local/lib/libkaffe_vm.so.0.5 (0x801d000) -lm.2 => /usr/lib/libm.so.2.0 (0x803e000) -lc.3 => /usr/lib/libc.so.3.0 (0x8055000) Unsuccessful one: /usr/local/bin/kaffe: -lkaffe_vm.0 => /usr/local/lib/libkaffe_vm.so.0.5 (0x801e000) -lm.2 => /usr/lib/libm.so.2.0 (0x803f000) -lc.3 => /usr/lib/libc.so.3.0 (0x8056000) If needed, I also did ldd -v on the kaffe executable, but it's more than 800 lines, so I don't include it here unless someone needs it. Thanks. Max From owner-freebsd-current Wed Oct 9 07:54:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA28841 for current-outgoing; Wed, 9 Oct 1996 07:54:55 -0700 (PDT) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA28824; Wed, 9 Oct 1996 07:54:39 -0700 (PDT) Received: from campa.panke.de (anonymous231.ppp.cs.tu-berlin.de [130.149.17.231]) by mail.cs.tu-berlin.de (8.6.13/8.6.12) with ESMTP id QAA07531; Wed, 9 Oct 1996 16:28:33 +0200 Received: (from wosch@localhost) by campa.panke.de (8.6.12/8.6.12) id PAA01354; Wed, 9 Oct 1996 15:12:55 +0200 Date: Wed, 9 Oct 1996 15:12:55 +0200 From: Wolfram Schneider Message-Id: <199610091312.PAA01354@campa.panke.de> To: Richard Wackerbarth Cc: Wolfram Schneider , Steve Price , current@freebsd.org Subject: Re: .depend In-Reply-To: References: <199610082021.WAA06329@campa.panke.de> Reply-to: Wolfram Schneider MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Richard Wackerbarth writes: >>I think we should add an enviroment variable (e.g. DEPENDFILE) to >>make(1) for `.depend'. mkdep -f foo support different depend files. > >Why change "make"? Because .depend is wired in make(1). There is no way to stop make(1) to read .depend if exists. There is no way to use an other depend file, e.g. `.depend.i486' or `.depend.hostname'. Example $ mkdep $ mkdep -f .depend.debug -DDEBUG $ mkdep -f .depend.i386 -Di386 You can now include .depend.debug in ./Makefile, but make(1) also read .depend because it exists. Wolfram From owner-freebsd-current Wed Oct 9 08:12:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA00476 for current-outgoing; Wed, 9 Oct 1996 08:12:49 -0700 (PDT) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [204.214.4.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA00312; Wed, 9 Oct 1996 08:11:22 -0700 (PDT) Received: from bonsai.hiwaay.net by fly.HiWAAY.net; (8.7.5/1.1.8.2/21Sep95-1003PM) id KAA15145; Wed, 9 Oct 1996 10:11:13 -0500 (CDT) Message-ID: <325BC094.1F74CF80@hiwaay.net> Date: Wed, 09 Oct 1996 10:11:16 -0500 From: Steve Price X-Mailer: Mozilla 2.02 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Wolfram Schneider CC: current@freebsd.org Subject: Re: .depend References: <199610082021.WAA06329@campa.panke.de> <199610091312.PAA01354@campa.panke.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Wolfram Schneider wrote: > > Richard Wackerbarth writes: > >>I think we should add an enviroment variable (e.g. DEPENDFILE) to > >>make(1) for `.depend'. mkdep -f foo support different depend files. > > > >Why change "make"? > > Because .depend is wired in make(1). There is no way > to stop make(1) to read .depend if exists. There is no way > to use an other depend file, e.g. `.depend.i486' or > `.depend.hostname'. > > Example > $ mkdep > $ mkdep -f .depend.debug -DDEBUG > $ mkdep -f .depend.i386 -Di386 > > You can now include .depend.debug in ./Makefile, but make(1) also > read .depend because it exists. > > Wolfram Then the best thing would be to take the hard-coded value of .depend out of make and put a rule in one of the *.mk files. IMHO including .depend as a rule in make is not good. make should be a generic tool that can be used in any environment for doing everything from writing books to writing software. Adding another hard-coded rule/value in make(1) makes it even more biased in the build/maintenance of software programs. I would be happy (if there are no strong objections) to remove the rule from make and put it in one of the *.mk files, but I really don't think always including .depend* files from within make are the best answer for a generic build tool. Just my opinion, Steve From owner-freebsd-current Wed Oct 9 08:18:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA00872 for current-outgoing; Wed, 9 Oct 1996 08:18:23 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA00864 for ; Wed, 9 Oct 1996 08:18:20 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.7.6/8.7.3) id LAA06388; Wed, 9 Oct 1996 11:18:19 -0400 (EDT) Date: Wed, 9 Oct 1996 11:18:19 -0400 (EDT) From: Charles Henrich Message-Id: <199610091518.LAA06388@crh.cl.msu.edu> To: danj@netcom.com, freebsd-current@freebsd.org Subject: Re: 961006-SNAP comments Newsgroups: lists.freebsd.current References: <53fcif$t17@msunews.cl.msu.edu> X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In lists.freebsd.current you write: > --- Calculate --- > swap = max( ( T - R ), (D * Dp) ) > swap = min( swap, (D * DpM) ) > swap = max( max( swap, Sm ), SM) Just my two cents, I always run swap a 2.5-3x ram size. Saved me many a time when running netscape and other bloated pig apps. > We could do something similar with var partitions (all those logs...). You know, I've never understood this. On my systems I *hate* having multiple partitions. I have / period. It allows the logs to grow if necessary, tmp to grow if neccesary etc. Now, I understand why you would break /tmp out (as I do on systems I dont run, but it doesnt make a whole lot of sense for a single user environment), but why /var? With newsyslog doing clean log rotations, var doesnt ever grow unduly large, and in the case when you really want more disk, you can expand it up to the size of your disk. Same argument for /usr, doesnt make a whole lot of sense, except for arcane disk problems where you would more readily nuke an active partition than one not so active. In my many years of unix computing I've never seen that occur. -Crh -- Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-current Wed Oct 9 08:33:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA02439 for current-outgoing; Wed, 9 Oct 1996 08:33:55 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA02427 for ; Wed, 9 Oct 1996 08:33:51 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id IAA23308; Wed, 9 Oct 1996 08:33:19 -0700 (PDT) Message-Id: <199610091533.IAA23308@austin.polstra.com> To: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= cc: freebsd-current@freebsd.org Subject: Re: ldconfig problem In-reply-to: Your message of "Wed, 09 Oct 1996 23:48:10 +0900." <199610091448.XAA01502@bourbon.sfc.wide.ad.jp> Date: Wed, 09 Oct 1996 08:33:18 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Successful one: > > /usr/local/bin/kaffe: > -lkaffe_vm.0 => /usr/local/lib/libkaffe_vm.so.0.5 (0x801d000) > -lm.2 => /usr/lib/libm.so.2.0 (0x803e000) > -lc.3 => /usr/lib/libc.so.3.0 (0x8055000) > > > > Unsuccessful one: > > /usr/local/bin/kaffe: > -lkaffe_vm.0 => /usr/local/lib/libkaffe_vm.so.0.5 (0x801e000) > -lm.2 => /usr/lib/libm.so.2.0 (0x803f000) > -lc.3 => /usr/lib/libc.so.3.0 (0x8056000) Hmm, these both look OK. The shared libraries in the second case are mapped one page higher than in the first case, but that doesn't indicate a problem. Before mapping any shared libraries, the dynamic linker maps the entire "/var/run/ld.so.hints" file into memory. In the second case, that file is probably one page larger than in the first case, because it has the extra libraries from "/usr/local/lib/m3/FreeBSD2" in it. Does kaffe use dlopen(), or LD_PRELOAD, or any other unusual features of the dynamic linker? Can you examine the core file with a debugger and try to figure out what it's doing when it dies? 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-current Wed Oct 9 08:36:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA02710 for current-outgoing; Wed, 9 Oct 1996 08:36:29 -0700 (PDT) Received: from eel.dataplex.net (eel.dataplex.net [208.2.87.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA02702; Wed, 9 Oct 1996 08:36:26 -0700 (PDT) Received: from [208.2.87.4] (cod [208.2.87.4]) by eel.dataplex.net (8.7.5/8.7.3) with ESMTP id KAA29142; Wed, 9 Oct 1996 10:36:23 -0500 (CDT) X-Sender: rkw@eel.dataplex.net Message-Id: In-Reply-To: <199610091312.PAA01354@campa.panke.de> References: <199610082021.WAA06329@campa.panke.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 9 Oct 1996 10:34:03 -0500 To: Wolfram Schneider From: Richard Wackerbarth Subject: Re: .depend Cc: Steve Price , current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Richard Wackerbarth writes: >>>I think we should add an enviroment variable (e.g. DEPENDFILE) to >>>make(1) for `.depend'. mkdep -f foo support different depend files. >> >>Why change "make"? > >Because .depend is wired in make(1). There is no way >to stop make(1) to read .depend if exists. There is no way >to use an other depend file, e.g. `.depend.i486' or >`.depend.hostname'. > >Example >$ mkdep >$ mkdep -f .depend.debug -DDEBUG >$ mkdep -f .depend.i386 -Di386 > >You can now include .depend.debug in ./Makefile, but make(1) also >read .depend because it exists. In general, including ".depend" would not break anything. ".depend.debug" would simply make it redundant. If this is not the case, you probably should not generate it in the first place. You also could pass the name of the desired depend file from the command line. However, IMHO, this is not really the proper usage. The .depend files are derived from the sources under the direction of the command line flags. The resulting objects should be placed in differect directories. The .depend file that corresponds to that set of objects should be placed in the directory with the objects rather than in the sources. IMHO, this entire discussion results from a fundamental error in the methodology of building multiple versions from a single set of sources. Rather than "kluge" something else into "make" so you can "get by", we should fix the methodology. From owner-freebsd-current Wed Oct 9 09:28:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA06654 for current-outgoing; Wed, 9 Oct 1996 09:28:50 -0700 (PDT) Received: from saguaro.flyingfox.com (saguaro.flyingfox.com [204.188.109.253]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA06643 for ; Wed, 9 Oct 1996 09:28:47 -0700 (PDT) Received: (from jas@localhost) by saguaro.flyingfox.com (8.6.12/8.6.10) id JAA26076; Wed, 9 Oct 1996 09:26:41 -0700 Date: Wed, 9 Oct 1996 09:26:41 -0700 From: Jim Shankland Message-Id: <199610091626.JAA26076@saguaro.flyingfox.com> To: jas@flyingfox.COM, jkh@time.cdrom.com Subject: Re: ok, look folks Cc: blh@nol.net, current@freebsd.org, jmb@freefall.freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Jordan K. Hubbard" writes: > I'm sorry, but this is an open and shut case of someone who > found it easier to yell and scream than do his homework. Not > the best of first impressions, and certainly one which will > stick with me for awhile. Fortunately for Jim, it's also > unlikely that anyone will ever ask me for a reference. I want to make it clear that *I'm* not the guy who yelled and screamed and didn't do his homework. I am knowledgable about mail systems, I'm not trying to unsubscribe from this list, I'd know how to unsubscribe if I wanted to, I yell and scream *much* less often that the average guy, and I usually do my homework. I just pointed out that some people don't know *how* to do their homework, or don't even know that there's homework to do, and mentioned a (hopefully) useful tip for those who are in this boat. But just to be on the safe side, I still won't list you as a reference, Jordan :-). Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-current Wed Oct 9 09:30:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA06869 for current-outgoing; Wed, 9 Oct 1996 09:30:29 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA05973 for ; Wed, 9 Oct 1996 09:21:23 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id RAA17739; Wed, 9 Oct 1996 17:15:05 +0100 Date: Wed, 9 Oct 1996 17:15:04 +0100 (BST) From: Doug Rabson To: John Polstra cc: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= , freebsd-current@freebsd.org Subject: Re: ldconfig problem In-Reply-To: <199610091533.IAA23308@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Oct 1996, John Polstra wrote: > > Successful one: > > > > /usr/local/bin/kaffe: > > -lkaffe_vm.0 => /usr/local/lib/libkaffe_vm.so.0.5 (0x801d000) > > -lm.2 => /usr/lib/libm.so.2.0 (0x803e000) > > -lc.3 => /usr/lib/libc.so.3.0 (0x8055000) > > > > > > > > Unsuccessful one: > > > > /usr/local/bin/kaffe: > > -lkaffe_vm.0 => /usr/local/lib/libkaffe_vm.so.0.5 (0x801e000) > > -lm.2 => /usr/lib/libm.so.2.0 (0x803f000) > > -lc.3 => /usr/lib/libc.so.3.0 (0x8056000) > > Hmm, these both look OK. The shared libraries in the second case are > mapped one page higher than in the first case, but that doesn't indicate > a problem. Before mapping any shared libraries, the dynamic linker maps > the entire "/var/run/ld.so.hints" file into memory. In the second case, > that file is probably one page larger than in the first case, because it > has the extra libraries from "/usr/local/lib/m3/FreeBSD2" in it. > > Does kaffe use dlopen(), or LD_PRELOAD, or any other unusual features > of the dynamic linker? I think kaffe uses dlopen to load shared library implementations of native Java classes. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 734 3761 FAX: +44 171 734 6426 From owner-freebsd-current Wed Oct 9 09:49:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA08657 for current-outgoing; Wed, 9 Oct 1996 09:49:45 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA08650 for ; Wed, 9 Oct 1996 09:49:43 -0700 (PDT) Received: from alpha.Xerox.COM by mail.crl.com with SMTP id AA26481 (5.65c/IDA-1.5 for ); Wed, 9 Oct 1996 09:50:34 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <16473(2)>; Wed, 9 Oct 1996 09:41:06 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177476>; Wed, 9 Oct 1996 09:40:59 -0700 To: Steven Wallace Cc: current@freebsd.org Subject: Re: bugs with syn and mountd in latest snap In-Reply-To: Your message of "Wed, 09 Oct 96 00:27:43 PDT." <199610090727.AAA05826@newport.ece.uci.edu> Date: Wed, 9 Oct 1996 09:40:58 PDT From: Bill Fenner Message-Id: <96Oct9.094059pdt.177476@crevenia.parc.xerox.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199610090727.AAA05826@newport.ece.uci.edu> you write: >"domain ece.uci.edu" in /etc/resolv.conf. That should search ece.uci.edu >then uci.edu, as the man page says and 2.1.5R did. The man pages somehow managed to not get updated when the new resolver got imported. You could check /usr/src/contrib/bind/man/resolver.5 . Bill From owner-freebsd-current Wed Oct 9 10:17:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA10927 for current-outgoing; Wed, 9 Oct 1996 10:17:54 -0700 (PDT) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA10922 for ; Wed, 9 Oct 1996 10:17:52 -0700 (PDT) Received: from pauling.salk.edu (pauling [198.202.70.108]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id KAA24618; Wed, 9 Oct 1996 10:12:46 -0700 (PDT) Date: Wed, 9 Oct 1996 10:12:48 -0700 (PDT) From: Tom Bartol To: Charles Henrich cc: "Jordan K. Hubbard" , hoek@freenet.hamilton.on.ca, freebsd-current@freebsd.org Subject: Re: 961006-SNAP comments In-Reply-To: <199610091306.JAA05163@crh.cl.msu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Oct 1996, Charles Henrich wrote: > > > all devices which they don't have. I think it should be reworded to say > > > "know you don't have", to prevent removal of something important ("syscons > > > > I think that's a reasonable point - I'll do this. > > Why are we forcing people who probably have no clue to go mucking with the > device table? I've done hundreds of FreeBSD installs and the generic kernel > has always booted just peachy with me. It seems that dumping people into a > fairly unfriendly (granted much better than command line) device editor as the > first thing they do is definatly not a good idea! > > -Crh > > Charles Henrich Michigan State University henrich@msu.edu > > http://pilot.msu.edu/~henrich How about having two different boot floppies -- one which does the plain vanilla GENERIC thing and one for experts which defaults to the config editor. That way everyone is happy and if you run into a machine with a cantankerous set of hardware you can reboot with the "expert" boot floppy. One disadvantage of this is that it violates the elegant simplicity of FreeBSD's "all for one and one for all" boot floppy philosophy. So on this note, if there could be a convenient and friendly way to inform users at boot time that they can, if need be, access a boot config editor by hitting some key on the keyboard without cramming the editor down the throats of others who may be confused by the editor or don't need to use the editor then, just perhaps, everyone will still be happy and the "one disk is all you need" constraint will be satisfied as well!! Just a few pseudo-random thoughts (determining whether my random seeding algorithm is adequate is left as an exercise for the reader) ;-) Tom From owner-freebsd-current Wed Oct 9 10:28:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA12136 for current-outgoing; Wed, 9 Oct 1996 10:28:21 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA12130 for ; Wed, 9 Oct 1996 10:28:15 -0700 (PDT) Received: from localhost (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with SMTP id KAA07396 for ; Wed, 9 Oct 1996 10:29:16 -0700 Date: Wed, 9 Oct 1996 10:29:15 -0700 (PDT) From: Veggy Vinny To: current@FreeBSD.ORG Subject: /usr/bin/install in -current broken Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It seems the /usr/bin/install in the latest -current is broken and doesn't know what -c is... root@earth [10:25am][/usr/ports/sysutils/top] >> make install Checksums OK. ===> Installing for top-3.4 ===> Warning: your umask is "0002". If this is not desired, set it to an appropriate value and install this port again by ``make reinstall''. install -c -o root -m 2755 -g kmem top /usr/local/bin install: unknown option -c install -c top.1 /usr/local/man/man1/top.1 install: unknown option -c strip /usr/local/bin/top gzip -9nf /usr/local/man/man1/top.1 /usr/local/man/man1/top.1: No such file or directory *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. root@earth [10:26am][/usr/ports/sysutils/top] >> Vince From owner-freebsd-current Wed Oct 9 10:33:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA12373 for current-outgoing; Wed, 9 Oct 1996 10:33:01 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-160.ut.nl.ibm.net [139.92.42.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA12362 for ; Wed, 9 Oct 1996 10:32:52 -0700 (PDT) Received: (from jhs@localhost) by vector.jhs.no_domain (8.7.5/8.6.9) id OAA14284; Wed, 9 Oct 1996 14:39:56 +0100 (MET) Date: Wed, 9 Oct 1996 14:39:56 +0100 (MET) Message-Id: <199610091339.OAA14284@vector.jhs.no_domain> To: current@freebsd.org Subject: ___main in /usr/lib/libgcc.a From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Mailer: EXMH 1.6.7, PGP available X-Address: Holz Strasse 27d, 80469 Munich, Germany X-Phone: +49.89.268616 X-Fax: +49.89.2608126 X-Web: http://www.freebsd.org/~jhs/ Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Upgrading a system from a ~3 week old current to real current, I've experienced a shrinkage of /usr/lib/libgcc.a from 15K to 6K & ___main is now missing, so nothing compiled (till I copied an old libgcc.a). Trying to rebuild libgcc.a on very current: pwd /usr/src/gnu/usr.bin/cc/libgcc make /usr/obj/usr/src/gnu/usr.bin/cc/libgcc/../cc/cc -B/usr/obj/usr/src/gnu/usr.bin/cc/libgcc/../cc1/ -B/usr/obj/usr/src/gnu/usr.bin/cc/libgcc/../cpp/ -c -O2 -m486 -pipe -DFREEBSD_AOUT -I/usr/src/gnu/usr.bin/cc/libgcc/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/libgcc/../../../../contrib/gcc/config -DFREEBSD_NATIVE -DDEFAULT_TARGET_VERSION=\"2.7.2.1\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/libgcc/../cc_tools -DL_muldi3 -o _muldi3.o /usr/src/gnu/usr.bin/cc/libgcc/../../../../contrib/gcc/libgcc2.c /usr/src/gnu/usr.bin/cc/libgcc/../../../../contrib/gcc/libgcc2.c:82: unknown machine mode `word_type' cc: file path prefix `/usr/obj/usr/src/gnu/usr.bin/cc/libgcc/../cpp/' never used Is compiler work still in progress ? should I wait a few days to allow for changes pending ? or investigate how to force my libgcc.a to make in 15K full mode ? Julian --- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Wed Oct 9 10:48:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA15169 for current-outgoing; Wed, 9 Oct 1996 10:48:57 -0700 (PDT) Received: from copernicus.iafrica.com (root@copernicus.iafrica.com [196.31.1.15]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA15153 for ; Wed, 9 Oct 1996 10:48:49 -0700 (PDT) Received: from localhost (khetan@localhost [127.0.0.1]) by copernicus.iafrica.com (8.7.6/8.6.12) with SMTP id TAA07067; Wed, 9 Oct 1996 19:48:13 +0200 (SAT) Date: Wed, 9 Oct 1996 19:47:53 +0200 (SAT) From: Khetan Gajjar To: Charles Henrich cc: freebsd-current@freebsd.org Subject: Re: 961006-SNAP comments In-Reply-To: <199610091330.JAA05706@crh.cl.msu.edu> Message-ID: X-URL: http://www.iafrica.com/~khetan/ X-Alternate-Address: khetan@uunet.co.za X-Alternate-Address2: kg@iafrica.com X-Alternate-Address3: gjjkhe01@sonnenberg.uct.ac.za X-Alternate-Address4: khetan@chain.iafrica.com X-Comment: Telkom sucks huge! X-IRC-nick: chain MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Oct 1996, Charles Henrich wrote: >If we force a config it has to be brain damaged, i.e: > Do you have an Adaptec 2940 SCSI Controller (Yes/No) > Do you have an NE2000 Compatable Ethernet Card (Yes/No) > Yes: What IRQ is this card located at? > What IOMEM Address does this card use? You mean like a Linux kernel ? I've seen those. Quite nice, but I like mucking around in vi with my kernel. --- Khetan Gajjar [ http://www.iafrica.com/~khetan] I'm a FreeBSD User! [ http://www.freebsd.org] UUNet Internet Africa [0800-030-002 & help@iafrica.com] From owner-freebsd-current Wed Oct 9 11:18:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA17590 for current-outgoing; Wed, 9 Oct 1996 11:18:02 -0700 (PDT) Received: from al.imforei.apana.org.au (pjchilds@al.imforei.apana.org.au [202.12.89.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA17524 for ; Wed, 9 Oct 1996 11:17:25 -0700 (PDT) Received: (from pjchilds@localhost) by al.imforei.apana.org.au (8.8.0/8.7.3) id DAA19101; Thu, 10 Oct 1996 03:46:44 +0930 (CST) Date: Thu, 10 Oct 1996 03:46:44 +0930 (CST) From: Peter Childs Message-Id: <199610091816.DAA19101@al.imforei.apana.org.au> To: jgreco@brasil.moneng.mei.com (Joe Greco), freebsd-current@freebsd.org Subject: Re: 961006-SNAP comments X-Newsreader: TIN [version 1.2 PL2] Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199610091406.JAA16882@brasil.moneng.mei.com> you wrote: : > has always booted just peachy with me. It seems that dumping people into a : > fairly unfriendly (granted much better than command line) device editor as : Maybe "boot -c" should invoke the visual configuration rather than the : command line configuration utility... but it should not be entered by : default. As far as I can see it does dump into "visual". My two cents is that people that find this confusing aren't really the sort of people that are going to find FreeBSD very sweet. Peter -- Peter Childs --- http://www.imforei.apana.org.au/~pjchilds Finger pjchilds@al.imforei.apana.org.au for public PGP key Drag me, drop me, treat me like an object! From owner-freebsd-current Wed Oct 9 11:20:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA17848 for current-outgoing; Wed, 9 Oct 1996 11:20:29 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA17839 for ; Wed, 9 Oct 1996 11:20:26 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id LAA22717; Wed, 9 Oct 1996 11:20:25 -0700 (PDT) To: Charles Henrich cc: freebsd-current@freebsd.org Subject: Re: 961006-SNAP comments In-reply-to: Your message of "Wed, 09 Oct 1996 09:30:44 EDT." <199610091330.JAA05706@crh.cl.msu.edu> Date: Wed, 09 Oct 1996 11:20:25 -0700 Message-ID: <22715.844885225@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > in the general case, the default settings are quite appropriate. How many > problems will be generated by people disabling the wrong things, or stumbling > around inside the editor just mucking things up because they dont know what > they are doing? I don't know, why don't we let users test it and find out! That's the whole purpose of these snapshots, after all! :-) > If we force a config it has to be brain damaged, i.e: > > Do you have an Adaptec 2940 SCSI Controller (Yes/No) > Do you have an NE2000 Compatable Ethernet Card (Yes/No) > Yes: What IRQ is this card located at? > What IOMEM Address does this card use? Yes, that has, in fact, always been my intention - using the visual userconfig by default is just a temporary measure and a "driven" userconfig is on my TODO list, where a hierarchy of questions is organized into a tree (ever play that earliest of computer guessing games called "animals?"). It wouldn't be so tedious as to query you for every card at the top level, but would ask you instead for broad catagories ("Do you have a network adaptor? Is it PCI, EISA or PCI? ISA? OK, then out of the above list, which one is it?"). That's why we added two options for USERCONFIG and VISUAL_USERCONFIG recently - I want to be able to compile in alternate userconfigs (though I think I'll just make this driven userconfig feature a command off the existing one, so I can also compile BOTH into the boot.flp kernel). Jordan From owner-freebsd-current Wed Oct 9 11:47:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA20537 for current-outgoing; Wed, 9 Oct 1996 11:47:11 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA20526 for ; Wed, 9 Oct 1996 11:47:09 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id LAA22953; Wed, 9 Oct 1996 11:47:07 -0700 (PDT) To: Jim Shankland cc: blh@nol.net, current@freebsd.org, jmb@freefall.freebsd.org Subject: Re: ok, look folks In-reply-to: Your message of "Wed, 09 Oct 1996 09:26:41 PDT." <199610091626.JAA26076@saguaro.flyingfox.com> Date: Wed, 09 Oct 1996 11:47:07 -0700 Message-ID: <22951.844886827@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I want to make it clear that *I'm* not the guy who yelled and > screamed and didn't do his homework. I am knowledgable about Sorry, entirely wrong attribution, sorry! :-( Apologies to Jim. Jordan From owner-freebsd-current Wed Oct 9 11:50:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA20937 for current-outgoing; Wed, 9 Oct 1996 11:50:45 -0700 (PDT) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA20928 for ; Wed, 9 Oct 1996 11:50:39 -0700 (PDT) Received: from campa.panke.de (anonymous215.ppp.cs.tu-berlin.de [130.149.17.215]) by mail.cs.tu-berlin.de (8.6.13/8.6.12) with ESMTP id UAA17603; Wed, 9 Oct 1996 20:39:33 +0200 Received: (from wosch@localhost) by campa.panke.de (8.6.12/8.6.12) id UAA02034; Wed, 9 Oct 1996 20:30:05 +0200 Date: Wed, 9 Oct 1996 20:30:05 +0200 From: Wolfram Schneider Message-Id: <199610091830.UAA02034@campa.panke.de> To: Steve Price Cc: current@freebsd.org Subject: Re: .depend In-Reply-To: <325BC094.1F74CF80@hiwaay.net> References: <199610082021.WAA06329@campa.panke.de> <199610091312.PAA01354@campa.panke.de> <325BC094.1F74CF80@hiwaay.net> Reply-to: Wolfram Schneider MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Steve Price writes: >Then the best thing would be to take the hard-coded value of >.depend out of make and put a rule in one of the *.mk files. Yes. Wolfram From owner-freebsd-current Wed Oct 9 11:55:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA21431 for current-outgoing; Wed, 9 Oct 1996 11:55:43 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA21408 for ; Wed, 9 Oct 1996 11:55:33 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.5/8.7.3) with SMTP id LAA17827; Wed, 9 Oct 1996 11:52:11 -0700 (PDT) Message-ID: <325BF3E5.41C67EA6@whistle.com> Date: Wed, 09 Oct 1996 11:50:13 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Charles Henrich CC: danj@netcom.com, freebsd-current@freebsd.org Subject: Re: 961006-SNAP comments References: <53fcif$t17@msunews.cl.msu.edu> <199610091518.LAA06388@crh.cl.msu.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Charles Henrich wrote: > > > user environment), but why /var? With newsyslog doing clean log rotations, var > theoretically to help run / as a readonly partition on NFS systems or such and have the 'variable' files on their own partition. julian From owner-freebsd-current Wed Oct 9 12:21:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA23516 for current-outgoing; Wed, 9 Oct 1996 12:21:51 -0700 (PDT) Received: (from hsu@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA23506 for current; Wed, 9 Oct 1996 12:21:49 -0700 (PDT) Date: Wed, 9 Oct 1996 12:21:49 -0700 (PDT) From: Jeffrey Hsu Message-Id: <199610091921.MAA23506@freefall.freebsd.org> To: current Subject: dlsym broken in -current Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Here's a program which shows the problem: #include #include int f() { } main() { void *handle; void *faddr; printf("function f at 0x%x\n", f); if (!(handle = dlopen(NULL, 1))) { fprintf(stderr, "dlopen failed: %s\n", dlerror()); exit(1); } if (faddr = dlsym(NULL, "_f")) { fprintf(stderr, "dlsym failed: %s\n", dlerror()); } printf("faddr retrieved as 0x%x\n", faddr); } From owner-freebsd-current Wed Oct 9 12:25:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA23880 for current-outgoing; Wed, 9 Oct 1996 12:25:37 -0700 (PDT) Received: from white.dogwood.com (root@white.dogwood.com [140.174.96.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA23875 for ; Wed, 9 Oct 1996 12:25:35 -0700 (PDT) Received: (from dave@localhost) by white.dogwood.com (8.8.0/8.8.0) id MAA03274 ; Wed, 9 Oct 1996 12:25:20 -0700 (PDT) From: Dave Cornejo Message-Id: <199610091925.MAA03274@white.dogwood.com> Subject: Re: /usr/bin/install in -current broken In-Reply-To: from "Veggy Vinny" at "Oct 9, 96 10:29:15 am" X-ELM-OSV: (Our standard violations) no-mime=1; no-hdr-encoding=1 To: richardc@CSUA.Berkeley.EDU (Veggy Vinny) Date: Wed, 9 Oct 1996 12:25:20 -0700 (PDT) Cc: current@FreeBSD.org Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Veggy Vinny wrote: > It seems the /usr/bin/install in the latest -current is broken and > doesn't know what -c is... > > root@earth [10:25am][/usr/ports/sysutils/top] >> make install > Checksums OK. > ===> Installing for top-3.4 There is an 'install' script in the top source directory - I remove it before trying 'make install' -- Dave Cornejo - Dogwood Media, Fremont, California From owner-freebsd-current Wed Oct 9 12:27:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA24090 for current-outgoing; Wed, 9 Oct 1996 12:27:36 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA24080 for ; Wed, 9 Oct 1996 12:27:31 -0700 (PDT) Received: from localhost (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with SMTP id MAA21053; Wed, 9 Oct 1996 12:28:24 -0700 Date: Wed, 9 Oct 1996 12:28:22 -0700 (PDT) From: Veggy Vinny To: Dave Cornejo cc: current@FreeBSD.org Subject: Re: /usr/bin/install in -current broken In-Reply-To: <199610091925.MAA03274@white.dogwood.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Oct 1996, Dave Cornejo wrote: > Veggy Vinny wrote: > > It seems the /usr/bin/install in the latest -current is broken and > > doesn't know what -c is... > > > > root@earth [10:25am][/usr/ports/sysutils/top] >> make install > > Checksums OK. > > ===> Installing for top-3.4 > > There is an 'install' script in the top source directory - I remove it > before trying 'make install' It's actually the top port not -current since I just saw my make world do install -c and it didn't complain.... Cheers, -Vince- GaiaNet Corporation Unix Networking Operations From owner-freebsd-current Wed Oct 9 12:30:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA24385 for current-outgoing; Wed, 9 Oct 1996 12:30:55 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA24380 for ; Wed, 9 Oct 1996 12:30:52 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id OAA17850; Wed, 9 Oct 1996 14:28:07 -0500 From: Joe Greco Message-Id: <199610091928.OAA17850@brasil.moneng.mei.com> Subject: Re: 961006-SNAP comments To: bartol@salk.edu (Tom Bartol) Date: Wed, 9 Oct 1996 14:28:06 -0500 (CDT) Cc: henrich@crh.cl.msu.edu, jkh@time.cdrom.com, hoek@freenet.hamilton.on.ca, freebsd-current@freebsd.org In-Reply-To: from "Tom Bartol" at Oct 9, 96 10:12:48 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > How about having two different boot floppies -- one which does the plain > vanilla GENERIC thing and one for experts which defaults to the config > editor. That way everyone is happy and if you run into a machine with a > cantankerous set of hardware you can reboot with the "expert" boot floppy. Comment: the "experts" will generally be smart enough to boot with "-c" if needed so there is little reason to have a floppy for them. (I don't quite qualify because I forget -c about 50% of the time when I need it, but I certainly don't blame the install process). I think the real question is whether or not the configuration behavior is appropriate for a novice user. FWIW, I like the one floppy thing too. ... JG From owner-freebsd-current Wed Oct 9 12:42:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA25465 for current-outgoing; Wed, 9 Oct 1996 12:42:43 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA25454 for ; Wed, 9 Oct 1996 12:42:38 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id OAA17882; Wed, 9 Oct 1996 14:40:30 -0500 From: Joe Greco Message-Id: <199610091940.OAA17882@brasil.moneng.mei.com> Subject: Re: 961006-SNAP comments To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Wed, 9 Oct 1996 14:40:29 -0500 (CDT) Cc: danj@netcom.com, freebsd-current@freebsd.org In-Reply-To: <199610091518.LAA06388@crh.cl.msu.edu> from "Charles Henrich" at Oct 9, 96 11:18:19 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > In lists.freebsd.current you write: > > > --- Calculate --- > > swap = max( ( T - R ), (D * Dp) ) > > > swap = min( swap, (D * DpM) ) > > > swap = max( max( swap, Sm ), SM) > > Just my two cents, I always run swap a 2.5-3x ram size. Saved me many a time > when running netscape and other bloated pig apps. > > > We could do something similar with var partitions (all those logs...). > > You know, I've never understood this. On my systems I *hate* having multiple > partitions. I have / period. It allows the logs to grow if necessary, tmp to > grow if neccesary etc. Now, I understand why you would break /tmp out (as I do > on systems I dont run, but it doesnt make a whole lot of sense for a single > user environment), but why /var? With newsyslog doing clean log rotations, var 1) It's nice to be able to do "df" and see which region of the system is eating more capacity than you expected (searching through a whole system to find out your /var/cron/log got out of hand is silly, or some wanker lpd'd a large binary file a hundred times). 2) It limits the problem to one particular part of the system, potentially leaving other areas of the system with sufficient space to run - and space for you to use to fix the problem. 3) Some people do like to put filesystems on alternate disks. > doesnt ever grow unduly large, and in the case when you really want more disk, > you can expand it up to the size of your disk. Same argument for /usr, doesnt > make a whole lot of sense, except for arcane disk problems where you would more > readily nuke an active partition than one not so active. In my many years of > unix computing I've never seen that occur. Me, I just do it because I like having sameness and uniformity among all my systems. My real machines have / swap /usr /usr/local /var /var/spool /usr/src /usr/X11R6 all as separate partitions. Even the most minimal machine has / swap /usr /var (and almost always /usr/local too) around here - and that's only if it is tight on disk. Call it... "preference". ... JG From owner-freebsd-current Wed Oct 9 12:47:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA25902 for current-outgoing; Wed, 9 Oct 1996 12:47:22 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA25860 for ; Wed, 9 Oct 1996 12:47:13 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id MAA28529; Wed, 9 Oct 1996 12:43:36 -0700 (PDT) Message-Id: <199610091943.MAA28529@austin.polstra.com> To: Doug Rabson cc: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= , freebsd-current@freebsd.org Subject: Re: ldconfig problem In-reply-to: Your message of "Wed, 09 Oct 1996 17:15:04 BST." Date: Wed, 09 Oct 1996 12:43:36 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Does kaffe use dlopen(), or LD_PRELOAD, or any other unusual features > > of the dynamic linker? > > I think kaffe uses dlopen to load shared library implementations of > native Java classes. Hrm. Masafumi, could you please put your system into the failing state, and then send me your "/var/run/ld.so.hints" file (uuencoded)? I will take a look at it, and see if I can find anything wrong. 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-current Wed Oct 9 12:49:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA26250 for current-outgoing; Wed, 9 Oct 1996 12:49:20 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA26244 for ; Wed, 9 Oct 1996 12:49:13 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA11505; Wed, 9 Oct 1996 13:49:10 -0600 (MDT) Date: Wed, 9 Oct 1996 13:49:10 -0600 (MDT) Message-Id: <199610091949.NAA11505@rocky.mt.sri.com> From: Nate Williams To: current@freebsd.org Subject: SIO problems Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk OK, I *really* think something is funky with the serial drivers in 2.1.5. I'm getting really good results most of the time, but the # of overflows I'm seeing concerns me. HW: 486/66 - 16MB memory Aha1542B - running at 'slow' transfer rates (3.3MB/sec or 5MB/sec, whichever is the slowest, I can't remember). multi-I/O card - Slot 0 has a 16450 and is connected to my mouse - Slot 1 has a TRUE-BLUE 16550AFN and is connected to a USR Sporster 28.8K running SLIP at 115K /etc/rc.serial is running modem() on slot 1, but is modified to 115200 baud since that's what I'm running the modem at. I'm running slattach at 115200 baud. The machine seems to have problems when uses as a Remote-CVS server, which hits both the network connection and the disks hard, but I've also gotten overflows when I was away on business in the middle of the day, when *NO* significant traffic was on the line. Background: I've been running this box for years at high-speeds with no problems, but as soon as I upgraded to 2.1.5 I started seeing problems. Bruce fixed a bug that supposedly allowed overflows to go un-noticed in the past, but are now recognized, so that's what I assumed. However, I started seeing lots of serial overflows. I even ran a program Bruce provided to check the latency of my system under heavy load, but I was well under the 'problem' mark. Snippets from a boot: sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A I uncommented the 'change FIFO level' code since it happens rarely to see if helps, with the following results: sio1: 1 more silo overflow (total 1) sio1: reduced fifo trigger level to 8 sio1: 1 more silo overflow (total 2) sio1: reduced fifo trigger level to 4 sio1: 1 more silo overflow (total 3) sio1: reduced fifo trigger level to 1 sio1: 1 more silo overflow (total 4) sio1: reduced fifo trigger level to 4 Obviously the dynamic code doesn't work quite as good as it should since it changed the level from 1 -> 4, but in any case I'm getting overflows and I really shouldn't be. The box has been up 9 days with this. I have a 486/66 box on the other end running 3 full-time connections that gets beat up even more than my box and it has no problem, although it's an IDE system that never touches it's disk. I'm really confused as to why I'm seeing these errors, so if anyone can shed light on it I'd appreciate it. Nate From owner-freebsd-current Wed Oct 9 13:04:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA27378 for current-outgoing; Wed, 9 Oct 1996 13:04:49 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA27373 for ; Wed, 9 Oct 1996 13:04:46 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id NAA23267; Wed, 9 Oct 1996 13:04:34 -0700 (PDT) To: Nate Williams cc: current@freebsd.org Subject: Re: SIO problems In-reply-to: Your message of "Wed, 09 Oct 1996 13:49:10 MDT." <199610091949.NAA11505@rocky.mt.sri.com> Date: Wed, 09 Oct 1996 13:04:34 -0700 Message-ID: <23265.844891474@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > OK, I *really* think something is funky with the serial drivers in > 2.1.5. I'm getting really good results most of the time, but the # of > overflows I'm seeing concerns me. Strange - my ISDN gateway box (which just uses at TA at 115.2Kb, so there's a lot of traffic) is a 2.1.5 box and it's worked just fine ever since the upgrade - no overflows at all with my 16550A UART. Jordan From owner-freebsd-current Wed Oct 9 13:06:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA27480 for current-outgoing; Wed, 9 Oct 1996 13:06:08 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA27473 for ; Wed, 9 Oct 1996 13:06:04 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.6/8.6.6) with ESMTP id OAA22589; Wed, 9 Oct 1996 14:03:43 -0600 (MDT) Message-Id: <199610092003.OAA22589@rover.village.org> To: Veggy Vinny Subject: Re: /usr/bin/install in -current broken Cc: current@FreeBSD.org In-reply-to: Your message of "Wed, 09 Oct 1996 10:29:15 PDT." References: Date: Wed, 09 Oct 1996 14:03:42 -0600 From: Warner Losh Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message Veggy Vinny writes: : It seems the /usr/bin/install in the latest -current is broken and : doesn't know what -c is... Might I suggest that you have '.' in your path before /usr/bin and that top also has a install program that is being grabbed first? The error message for things that /usr/bin/install doesn't understand looks more like: /usr/bin/isntall -Z install: illegal option -- Z 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 ... Warner From owner-freebsd-current Wed Oct 9 13:06:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA27542 for current-outgoing; Wed, 9 Oct 1996 13:06:49 -0700 (PDT) Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA27518 for ; Wed, 9 Oct 1996 13:06:32 -0700 (PDT) Received: from grumble.grondar.za (mark@localhost.grondar.za [127.0.0.1]) by grumble.grondar.za (8.7.6/8.7.3) with ESMTP id WAA07171; Wed, 9 Oct 1996 22:04:12 +0200 (SAT) Message-Id: <199610092004.WAA07171@grumble.grondar.za> To: Veggy Vinny cc: Dave Cornejo , current@FreeBSD.org Subject: Re: /usr/bin/install in -current broken Date: Wed, 09 Oct 1996 22:04:11 +0200 From: Mark Murray Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Veggy Vinny wrote: > On Wed, 9 Oct 1996, Dave Cornejo wrote: > > Veggy Vinny wrote: > > > It seems the /usr/bin/install in the latest -current is broken and > > > doesn't know what -c is... > > > > > > root@earth [10:25am][/usr/ports/sysutils/top] >> make install > > > Checksums OK. > > > ===> Installing for top-3.4 > > > > There is an 'install' script in the top source directory - I remove it > > before trying 'make install' > > It's actually the top port not -current since I just saw my make > world do install -c and it didn't complain.... You obviously have "." in your path, and you're doing this as root. You almost certainly have the "." early in your path, too. It is a BAAAAD idea for root to have "." in their path. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Wed Oct 9 13:09:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA27767 for current-outgoing; Wed, 9 Oct 1996 13:09:20 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA27758 for ; Wed, 9 Oct 1996 13:09:16 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id OAA11630; Wed, 9 Oct 1996 14:07:51 -0600 (MDT) Date: Wed, 9 Oct 1996 14:07:51 -0600 (MDT) Message-Id: <199610092007.OAA11630@rocky.mt.sri.com> From: Nate Williams To: "Jordan K. Hubbard" Cc: Nate Williams , current@freebsd.org Subject: Re: SIO problems In-Reply-To: <23265.844891474@time.cdrom.com> References: <199610091949.NAA11505@rocky.mt.sri.com> <23265.844891474@time.cdrom.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard writes: > > OK, I *really* think something is funky with the serial drivers in > > 2.1.5. I'm getting really good results most of the time, but the # of > > overflows I'm seeing concerns me. > > Strange - my ISDN gateway box (which just uses at TA at 115.2Kb, so > there's a lot of traffic) is a 2.1.5 box and it's worked just fine > ever since the upgrade - no overflows at all with my 16550A UART. Is your ISDN gateway box doing *anything* but route packets? My gateway box was running a 28.8K modem link to the net (it's got a 56K Frame line now) so whenever I downloaded at home it took a huge hit w/out problems. But, it doesn't do anything but route packets so it never has a problem since it's the *only* thing running on the computer. It's hard to get overflows when the only processing the computer does are serial/network interrupts. :) Nate From owner-freebsd-current Wed Oct 9 13:13:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA28039 for current-outgoing; Wed, 9 Oct 1996 13:13:13 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA28024 for ; Wed, 9 Oct 1996 13:13:09 -0700 (PDT) Received: from localhost (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with SMTP id NAA25529; Wed, 9 Oct 1996 13:13:05 -0700 Date: Wed, 9 Oct 1996 13:13:04 -0700 (PDT) From: Veggy Vinny To: Mark Murray cc: Dave Cornejo , current@FreeBSD.org Subject: Re: /usr/bin/install in -current broken In-Reply-To: <199610092004.WAA07171@grumble.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Oct 1996, Mark Murray wrote: > You obviously have "." in your path, and you're doing this as root. > You almost certainly have the "." early in your path, too. > It is a BAAAAD idea for root to have "." in their path. Thanks for pointing it out.... I forgot to check that. So it was using the wrong install I guess when I was make install'ng the top port. Cheers, -Vince- GaiaNet Corporation Unix Networking Operations From owner-freebsd-current Wed Oct 9 13:15:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA28190 for current-outgoing; Wed, 9 Oct 1996 13:15:06 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA28172; Wed, 9 Oct 1996 13:15:01 -0700 (PDT) Message-Id: <199610092015.NAA28172@freefall.freebsd.org> To: Nate Williams cc: current@freebsd.org Subject: Re: SIO problems In-reply-to: Your message of "Wed, 09 Oct 1996 13:49:10 MDT." <199610091949.NAA11505@rocky.mt.sri.com> Date: Wed, 09 Oct 1996 13:15:00 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I thought this was a problem with the VM system sitting at splhigh() too much. I used to get these a long time ago, but they vanished after Bruce and John talked about this issue and something was done about it. I have no idea if those changes ever went back into the -stable branch or 2.1.5R. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Wed Oct 9 13:16:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA28492 for current-outgoing; Wed, 9 Oct 1996 13:16:55 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA28484 for ; Wed, 9 Oct 1996 13:16:52 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id UAA04138; Wed, 9 Oct 1996 20:48:43 +0100 From: Luigi Rizzo Message-Id: <199610091948.UAA04138@labinfo.iet.unipi.it> Subject: Re: 961006-SNAP comments To: julian@whistle.com (Julian Elischer) Date: Wed, 9 Oct 1996 20:48:43 +0100 (MET) Cc: henrich@crh.cl.msu.edu, danj@netcom.com, freebsd-current@freebsd.org In-Reply-To: <325BF3E5.41C67EA6@whistle.com> from "Julian Elischer" at Oct 9, 96 11:49:54 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Charles Henrich wrote: > > > > user environment), but why /var? With newsyslog doing clean log rotations, var > > > theoretically to help run / as a readonly partition > on NFS systems or such and > have the 'variable' files on their own partition. just theoretically, since a lot of machine dependant stuff is in /etc. 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-current Wed Oct 9 13:19:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA28678 for current-outgoing; Wed, 9 Oct 1996 13:19:44 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA28670 for ; Wed, 9 Oct 1996 13:19:38 -0700 (PDT) Received: from localhost (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with SMTP id NAA25679; Wed, 9 Oct 1996 13:14:56 -0700 Date: Wed, 9 Oct 1996 13:14:54 -0700 (PDT) From: Veggy Vinny To: Warner Losh cc: current@FreeBSD.org Subject: Re: /usr/bin/install in -current broken In-Reply-To: <199610092003.OAA22589@rover.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Oct 1996, Warner Losh wrote: > In message Veggy Vinny writes: > : It seems the /usr/bin/install in the latest -current is broken and > : doesn't know what -c is... > > Might I suggest that you have '.' in your path before /usr/bin and > that top also has a install program that is being grabbed first? The > error message for things that /usr/bin/install doesn't understand > looks more like: Actually, you're right and thanks for pointing it out so how do I tell which install the make install wants? Cheers, -Vince- GaiaNet Corporation Unix Networking Operations From owner-freebsd-current Wed Oct 9 13:25:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA29322 for current-outgoing; Wed, 9 Oct 1996 13:25:52 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA29311 for ; Wed, 9 Oct 1996 13:25:44 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.6/8.6.6) with ESMTP id OAA22765; Wed, 9 Oct 1996 14:24:44 -0600 (MDT) Message-Id: <199610092024.OAA22765@rover.village.org> To: Veggy Vinny Subject: Re: /usr/bin/install in -current broken Cc: current@FreeBSD.org In-reply-to: Your message of "Wed, 09 Oct 1996 13:14:54 PDT." References: Date: Wed, 09 Oct 1996 14:24:44 -0600 From: Warner Losh Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message Veggy Vinny writes: : Actually, you're right and thanks for pointing it out so how do I : tell which install the make install wants? It almost always wants /usr/bin/install :-) It generally uses the first 'install' program in your path. You might want to move '.' to be the last component in your path, since that fixes this and other problems building many of the ports or other random software off the net. You especially don't want to have it in root's path, since that can lead to trojans and such. BTW, your message nearly gave me heart failure, since I was the last person to touch install... :-) Warner From owner-freebsd-current Wed Oct 9 13:26:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA29354 for current-outgoing; Wed, 9 Oct 1996 13:26:08 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA29349 for ; Wed, 9 Oct 1996 13:26:06 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id NAA23349; Wed, 9 Oct 1996 13:17:13 -0700 (PDT) To: Nate Williams cc: current@freebsd.org Subject: Re: SIO problems In-reply-to: Your message of "Wed, 09 Oct 1996 14:07:51 MDT." <199610092007.OAA11630@rocky.mt.sri.com> Date: Wed, 09 Oct 1996 13:17:13 -0700 Message-ID: <23347.844892233@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Is your ISDN gateway box doing *anything* but route packets? My gateway Yep, it also builds my internal 2.1-stable snapshots and numerous 2.1.5 builds back when that was going on - not a hiccough. Jordan From owner-freebsd-current Wed Oct 9 13:33:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA00156 for current-outgoing; Wed, 9 Oct 1996 13:33:14 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA00145 for ; Wed, 9 Oct 1996 13:33:09 -0700 (PDT) Received: from localhost (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with SMTP id NAA27813; Wed, 9 Oct 1996 13:33:25 -0700 Date: Wed, 9 Oct 1996 13:33:24 -0700 (PDT) From: Veggy Vinny To: Warner Losh cc: current@FreeBSD.org Subject: Re: /usr/bin/install in -current broken In-Reply-To: <199610092024.OAA22765@rover.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Oct 1996, Warner Losh wrote: > : Actually, you're right and thanks for pointing it out so how do I > : tell which install the make install wants? > > It almost always wants /usr/bin/install :-) It generally uses the > first 'install' program in your path. You might want to move '.' to > be the last component in your path, since that fixes this and other > problems building many of the ports or other random software off the > net. You especially don't want to have it in root's path, since that > can lead to trojans and such. Hmmm, is moving the '.' to the last component in the path still a security risk? I guess you are right that I don't want to have it in root's path but I guess as the last component it should be okay since no one can name something with the same name and have me run it... =) > BTW, your message nearly gave me heart failure, since I was the last > person to touch install... :-) Sorry about that, I thought it was the install but then later I saw my make world just did fine with install so it couldn't be... It used to be that when install failed for a port, I just rebuild the install and it would work. =) Cheers, -Vince- GaiaNet Corporation Unix Networking Operations From owner-freebsd-current Wed Oct 9 13:33:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA00280 for current-outgoing; Wed, 9 Oct 1996 13:33:55 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA00265 for ; Wed, 9 Oct 1996 13:33:48 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id OAA11757; Wed, 9 Oct 1996 14:33:19 -0600 (MDT) Date: Wed, 9 Oct 1996 14:33:19 -0600 (MDT) Message-Id: <199610092033.OAA11757@rocky.mt.sri.com> From: Nate Williams To: "Jordan K. Hubbard" Cc: Nate Williams , current@freebsd.org Subject: Re: SIO problems In-Reply-To: <23347.844892233@time.cdrom.com> References: <199610092007.OAA11630@rocky.mt.sri.com> <23347.844892233@time.cdrom.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard writes: > > Is your ISDN gateway box doing *anything* but route packets? My gateway > > Yep, it also builds my internal 2.1-stable snapshots and numerous 2.1.5 > builds back when that was going on - not a hiccough. Is is a SCSI system? From owner-freebsd-current Wed Oct 9 13:42:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA01635 for current-outgoing; Wed, 9 Oct 1996 13:42:47 -0700 (PDT) Received: from grex.cyberspace.org (grex.cyberspace.org [152.160.30.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA01608; Wed, 9 Oct 1996 13:42:39 -0700 (PDT) Received: from localhost (entropy@localhost) by grex.cyberspace.org (8.6.13/8.6.12) with SMTP id QAA16453; Wed, 9 Oct 1996 16:36:34 -0400 Date: Wed, 9 Oct 1996 16:36:30 -0400 (EDT) From: chaos and disorder To: Julian Elischer cc: "Brian N. Handy" , =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= , Terry Lambert , joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org, current@FreeBSD.org, Bruce Evans Subject: Re: I plan to change random() for -current (was Re: rand() and random()) In-Reply-To: <3259AC88.2781E494@whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe freebsd-hackers From owner-freebsd-current Wed Oct 9 13:46:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA02194 for current-outgoing; Wed, 9 Oct 1996 13:46:26 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA02173 for ; Wed, 9 Oct 1996 13:46:17 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA18678; Wed, 9 Oct 1996 13:41:11 -0700 From: Terry Lambert Message-Id: <199610092041.NAA18678@phaeton.artisoft.com> Subject: Re: ok, look folks To: danj@netcom.com (Dan Janowski) Date: Wed, 9 Oct 1996 13:41:11 -0700 (MST) Cc: current@FreeBSD.org In-Reply-To: <325B2B36.41C67EA6@netcom.com> from "Dan Janowski" at Oct 9, 96 00:33:58 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-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > (4) Save those useful and, apparently, ignored messages from > majordomo when you subscribe. (Even make a mail-box > file to keep them in) > > > ++ We should add a little banner at the top of those > majordomo "welcome" messages: > > > KEEP THIS MESSAGE!!!!! > > YOU WILL NEED IT WHEN YOU'VE GOTTEN > SICK OF THE E-MAIL TRAFFIC AND THEN TRY > TO UNSUBSCRIBE IN A PANIC, FORGETTING > HOW TO DO IT AND GETTING PISSED OFF ABOUT IT. > > ++ > > Nothing personal intended; it got me once. But that > was Linux lists (you want to talk about traffic), and > that was a long time ago. I suggested this before, and I'll suggest it again: Each list whould have a monthly "FAQ" posting that goes out automatically; it would include "how to unsubscribe". Depending on overhead, it could even be "personalized", telling the person how to unsubscribe and from which address they'd have to do it. 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-current Wed Oct 9 13:56:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA03309 for current-outgoing; Wed, 9 Oct 1996 13:56:43 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA03300; Wed, 9 Oct 1996 13:56:38 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA18730; Wed, 9 Oct 1996 13:52:17 -0700 From: Terry Lambert Message-Id: <199610092052.NAA18730@phaeton.artisoft.com> Subject: Re: .depend To: rkw@dataplex.net (Richard Wackerbarth) Date: Wed, 9 Oct 1996 13:52:17 -0700 (MST) Cc: wosch@freebsd.org, steve@freefall.freebsd.org, current@freebsd.org In-Reply-To: from "Richard Wackerbarth" at Oct 9, 96 10:34:03 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > IMHO, this entire discussion results from a fundamental error in the > methodology of building multiple versions from a single set of sources. > Rather than "kluge" something else into "make" so you can "get by", we > should fix the methodology. What happens when I want to build several different machine architectures from the same NFS mounted sources instead of placing 3 times the SUP load on one of the severs to get thrre times the trees on three times the local diskk space used? Building multiple versions from a single set of sources is a requirement, IMO. 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-current Wed Oct 9 14:05:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA04273 for current-outgoing; Wed, 9 Oct 1996 14:05:58 -0700 (PDT) Received: from po2.glue.umd.edu (po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA04264 for ; Wed, 9 Oct 1996 14:05:55 -0700 (PDT) Received: from thurston.eng.umd.edu (thurston.eng.umd.edu [129.2.103.25]) by po2.glue.umd.edu (8.8.0/8.7.3) with ESMTP id RAA00022; Wed, 9 Oct 1996 17:05:48 -0400 (EDT) Received: from localhost (chuckr@localhost) by thurston.eng.umd.edu (8.7.5/8.7.3) with SMTP id RAA08430; Wed, 9 Oct 1996 17:05:46 -0400 (EDT) X-Authentication-Warning: thurston.eng.umd.edu: chuckr owned process doing -bs Date: Wed, 9 Oct 1996 17:05:46 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@thurston.eng.umd.edu To: Simon Marlow cc: "Brett L. Hawn" , "Jordan K. Hubbard" , Jim Shankland , jmb@freefall.freebsd.org, current@FreeBSD.org Subject: Re: ok, look folks In-Reply-To: <199610091255.FAA22639@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Oct 1996, Simon Marlow wrote: > > > I've run majordomo before, I hack sendmail here at the office, I think I > > know what I'm doing. However WHENN I subscribed, I did so as blh@nol.net, > > NOT blh@dazed.nol.net, so yes.. I got a little frustrated with the fact that > > majordomo in its infinit crappiness, changed my subscribe address and made > > it a nightmare to unsubscribe. > > It's fairly easy to forge some mail from your original email address > to get yourself off these lists. I've had to do it several times. > Perhaps we should put it in the FAQ :) I don't think so, Simon. The folks I've helped have all had the same problem: they are signed up under a slightly different name. They all have various reasons for it, and they've all been real nice when I explained it to them. All I ever had to do was mail majordomo for the list of users of the list they wanted off of, then find an address that looked close, and show it to them. They then happily thank me, and unsubscribe themselves. The problem is not one of inability, it's that they don't understand how the mechanism could possibly fail, and they get frustrated. Telling them how to forge mail won't help anything. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Wed Oct 9 14:09:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA04572 for current-outgoing; Wed, 9 Oct 1996 14:09:30 -0700 (PDT) Received: from eel.dataplex.net (eel.dataplex.net [208.2.87.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA04562 for ; Wed, 9 Oct 1996 14:09:26 -0700 (PDT) Received: from [208.2.87.4] (cod [208.2.87.4]) by eel.dataplex.net (8.7.5/8.7.3) with ESMTP id QAA20241; Wed, 9 Oct 1996 16:08:02 -0500 (CDT) X-Sender: rkw@eel.dataplex.net Message-Id: In-Reply-To: <199610092052.NAA18730@phaeton.artisoft.com> References: from "Richard Wackerbarth" at Oct 9, 96 10:34:03 am Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 9 Oct 1996 16:03:27 -0500 To: Terry Lambert From: Richard Wackerbarth Subject: Re: .depend Cc: steve@freefall.freebsd.org, current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry says: >Building multiple versions from a single set of sources is a requirement, >IMO. I totally agree. What I was trying to say is that the "error" is in the way people have going about it. The source directory should not have any files that change with the compile time options. Those files should be placed in their individual directories. From owner-freebsd-current Wed Oct 9 14:41:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA07905 for current-outgoing; Wed, 9 Oct 1996 14:41:25 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA07846 for ; Wed, 9 Oct 1996 14:41:19 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id HAA24870; Thu, 10 Oct 1996 07:40:08 +1000 Date: Thu, 10 Oct 1996 07:40:08 +1000 From: Bruce Evans Message-Id: <199610092140.HAA24870@godzilla.zeta.org.au> To: current@FreeBSD.org, nate@mt.sri.com Subject: Re: SIO problems Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Background: > I've been running this box for years at high-speeds with no problems, >but as soon as I upgraded to 2.1.5 I started seeing problems. Bruce The only significant difference between the 2.1.0 and 2.1.5 sio's is that unconfigured ports aren't initialized. Bruce From owner-freebsd-current Wed Oct 9 14:46:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA08689 for current-outgoing; Wed, 9 Oct 1996 14:46:11 -0700 (PDT) Received: from bourbon.sfc.wide.ad.jp (root@bourbon.sfc.wide.ad.jp [133.4.30.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA08666 for ; Wed, 9 Oct 1996 14:46:06 -0700 (PDT) Received: from bourbon (max@localhost [127.0.0.1]) by bourbon.sfc.wide.ad.jp (8.7.6/3.4W409/27/96) with ESMTP id GAA04189; Thu, 10 Oct 1996 06:45:41 +0900 (JST) Message-Id: <199610092145.GAA04189@bourbon.sfc.wide.ad.jp> To: jdp@polstra.com Cc: max@wide.ad.jp, freebsd-current@freebsd.org Subject: Re: ldconfig problem From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= In-Reply-To: Your message of "Wed, 09 Oct 1996 08:33:18 -0700" References: <199610091533.IAA23308@austin.polstra.com> X-Mailer: Mew version 1.06 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 10 Oct 1996 06:45:41 +0900 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk jdp> Hmm, these both look OK. The shared libraries in the second jdp> case are mapped one page higher than in the first case, but jdp> that doesn't indicate a problem. Before mapping any shared jdp> libraries, the dynamic linker maps the entire jdp> "/var/run/ld.so.hints" file into memory. In the second case, jdp> that file is probably one page larger than in the first case, jdp> because it has the extra libraries from jdp> "/usr/local/lib/m3/FreeBSD2" in it. jdp> Does kaffe use dlopen(), or LD_PRELOAD, or any other unusual jdp> features of the dynamic linker? I'm not really sure about this. But, it looks it uses dlopen as several files contain the string ``dlopen''. jdp> Can you examine the core file with a debugger and try to jdp> figure out what it's doing when it dies? Guess what! Things are getting worse. (At least it seems to me that way.) I started up gdb and and did ``help set'' to find out some stuff. Gdb gave me the first page of the help screen as usual, but as I hit return key to go onto the next page, it died on signal 3 with following message after showing the second page: gdb internal error: Memory corruption Quit (core dumped) This error is not affected by ld.so.hints change. It happens regardless of whether kaffe runs or not. So, I guess now we have to do some investigation on gdb.... ;_) Do you think having CFLAGS=-O -pipe -m486 in /etc/make.conf coud be causing these errors? After I discovered gdb's error, I rebuilt /usr/src/gnu/usr.bin/{gdb,ld} with -O and -m486 removed from /etc/make.conf, but things don't change. Should I do make world without those flags and try again? Max From owner-freebsd-current Wed Oct 9 14:48:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09095 for current-outgoing; Wed, 9 Oct 1996 14:48:03 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA09055 for ; Wed, 9 Oct 1996 14:47:55 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA12339; Wed, 9 Oct 1996 15:42:05 -0600 (MDT) Date: Wed, 9 Oct 1996 15:42:05 -0600 (MDT) Message-Id: <199610092142.PAA12339@rocky.mt.sri.com> From: Nate Williams To: Bruce Evans Cc: current@freebsd.org, nate@mt.sri.com Subject: Re: SIO problems In-Reply-To: <199610092140.HAA24870@godzilla.zeta.org.au> References: <199610092140.HAA24870@godzilla.zeta.org.au> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I've been running this box for years at high-speeds with no problems, > >but as soon as I upgraded to 2.1.5 I started seeing problems. Bruce > > The only significant difference between the 2.1.0 and 2.1.5 sio's is > that unconfigured ports aren't initialized. I jumped from 2.0 -> 2.1.5. :( Nate From owner-freebsd-current Wed Oct 9 14:49:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09253 for current-outgoing; Wed, 9 Oct 1996 14:49:16 -0700 (PDT) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA09243 for ; Wed, 9 Oct 1996 14:49:11 -0700 (PDT) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA10630; Wed, 9 Oct 1996 14:49:10 -0700 Date: Wed, 9 Oct 1996 14:49:09 -0700 (PDT) From: "Brian N. Handy" To: current@FreeBSD.org Subject: Re: SIO problems In-Reply-To: <23265.844891474@time.cdrom.com> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > [SIO overflow problems from Nate] Jordan: >Strange - my ISDN gateway box (which just uses at TA at 115.2Kb, so >there's a lot of traffic) is a 2.1.5 box and it's worked just fine >ever since the upgrade - no overflows at all with my 16550A UART. My PC's back at school (running unspecified 16450's on the mouse port) get these all the time, and my 6-month-old rgrimes P-133 has gotten these fairly routinely in the past. I haven't payed attention since the 960801 snap, though. Not sure where I stand right now. Brian From owner-freebsd-current Wed Oct 9 14:51:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09471 for current-outgoing; Wed, 9 Oct 1996 14:51:02 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA09456 for ; Wed, 9 Oct 1996 14:50:57 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id HAA25087; Thu, 10 Oct 1996 07:48:45 +1000 Date: Thu, 10 Oct 1996 07:48:45 +1000 From: Bruce Evans Message-Id: <199610092148.HAA25087@godzilla.zeta.org.au> To: gibbs@freefall.freebsd.org, nate@mt.sri.com Subject: Re: SIO problems Cc: current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >I thought this was a problem with the VM system sitting at splhigh() >too much. I used to get these a long time ago, but they vanished It can't be that, because splhigh() doesn't mask "fast" interrupts. BTW, there is a problem with the PCI interrupt demultiplexor not supporting "fast" interrupts. I tried running the cy driver with "slow" interrupts (a one line change to delate the line that sets RI_FAST). The (12 byte) fifo was overrun by a factor of about 4 for every syscons vt switch (because busy waiting is used to set the LEDs and the LEDs are set at spltty()). Bruce From owner-freebsd-current Wed Oct 9 15:04:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA10967 for current-outgoing; Wed, 9 Oct 1996 15:04:40 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA10944; Wed, 9 Oct 1996 15:04:34 -0700 (PDT) Message-Id: <199610092204.PAA10944@freefall.freebsd.org> To: Bruce Evans cc: nate@mt.sri.com, current@FreeBSD.org Subject: Re: SIO problems In-reply-to: Your message of "Thu, 10 Oct 1996 07:48:45 +1000." <199610092148.HAA25087@godzilla.zeta.org.au> Date: Wed, 09 Oct 1996 15:04:33 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >>I thought this was a problem with the VM system sitting at splhigh() >>too much. I used to get these a long time ago, but they vanished > >It can't be that, because splhigh() doesn't mask "fast" interrupts. > >BTW, there is a problem with the PCI interrupt demultiplexor not >supporting "fast" interrupts. I tried running the cy driver with >"slow" interrupts (a one line change to delate the line that sets >RI_FAST). The (12 byte) fifo was overrun by a factor of about 4 >for every syscons vt switch (because busy waiting is used to set >the LEDs and the LEDs are set at spltty()). Feel free to fix them then. You can also merge the interrupt registration code for all bus types too. 8-) > >Bruce -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Wed Oct 9 15:11:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA11536 for current-outgoing; Wed, 9 Oct 1996 15:11:13 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [193.91.212.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA11527 for ; Wed, 9 Oct 1996 15:11:05 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 7188 invoked by uid 1001); 9 Oct 1996 22:10:46 +0000 (GMT) To: luigi@labinfo.iet.unipi.it Cc: julian@whistle.com, henrich@crh.cl.msu.edu, danj@netcom.com, freebsd-current@FreeBSD.org Subject: Re: 961006-SNAP comments In-Reply-To: Your message of "Wed, 9 Oct 1996 20:48:43 +0100 (MET)" References: <199610091948.UAA04138@labinfo.iet.unipi.it> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 10 Oct 1996 00:10:46 +0200 Message-ID: <7186.844899046@verdi.nethelp.no> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > user environment), but why /var? With newsyslog doing clean log rotations, var > > > > > theoretically to help run / as a readonly partition > > on NFS systems or such and > > have the 'variable' files on their own partition. > > just theoretically, since a lot of machine dependant stuff is in /etc. I'd actually like to do a readonly /, and it looks to me like it should be possible: 1. Symlink those few variable files that are left, e.g. /etc/ntp.drift and /etc/ssh_random_seed into /var/run. 2. Use DEVFS for the devices. Any reason why this wouldn't work? Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-current Wed Oct 9 15:26:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA13070 for current-outgoing; Wed, 9 Oct 1996 15:26:37 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA13057 for ; Wed, 9 Oct 1996 15:26:33 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id PAA23805; Wed, 9 Oct 1996 15:25:45 -0700 (PDT) To: Nate Williams cc: current@freebsd.org Subject: Re: SIO problems In-reply-to: Your message of "Wed, 09 Oct 1996 14:33:19 MDT." <199610092033.OAA11757@rocky.mt.sri.com> Date: Wed, 09 Oct 1996 15:25:45 -0700 Message-ID: <23803.844899945@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Jordan K. Hubbard writes: > > > Is your ISDN gateway box doing *anything* but route packets? My gateway > > > > Yep, it also builds my internal 2.1-stable snapshots and numerous 2.1.5 > > builds back when that was going on - not a hiccough. > > Is is a SCSI system? Need you ask? :-) Yes, it is a SCSI system. You will never hear me refer to IDE in any context unless I'm talking about someone *else's* box. :-) Jordan From owner-freebsd-current Wed Oct 9 15:31:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA13448 for current-outgoing; Wed, 9 Oct 1996 15:31:18 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA13436 for ; Wed, 9 Oct 1996 15:31:13 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.7.6/8.7.3) with SMTP id RAA04860; Wed, 9 Oct 1996 17:30:36 -0500 (EST) Date: Wed, 9 Oct 1996 17:30:35 -0500 (EST) From: John Fieber To: Charles Henrich cc: "Jordan K. Hubbard" , hoek@freenet.hamilton.on.ca, freebsd-current@FreeBSD.org Subject: Re: 961006-SNAP comments In-Reply-To: <199610091306.JAA05163@crh.cl.msu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Oct 1996, Charles Henrich wrote: > Why are we forcing people who probably have no clue to go mucking with the > device table? Because this marvelous PC architecture we have often requires it. Except for people who use only the hardware and software that came installed on there machine, just about every PC user will at some point confront IRQs and the like, or they will pay someone else to. If we try and hide the issue, a fair number of people will reach a dead end and give up before they get started. This snapshot represent a first approach at confronting the issue directly. I'll agree that it needs to be refined, but considering we can't change the PC architecture, its the best direction to go. Don't be so anxious to throw out the idea just because its new and doesn't solve a problem you have. -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ From owner-freebsd-current Wed Oct 9 15:35:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA13835 for current-outgoing; Wed, 9 Oct 1996 15:35:13 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA13802 for ; Wed, 9 Oct 1996 15:35:04 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.5/8.7.3) with SMTP id PAA20151; Wed, 9 Oct 1996 15:30:30 -0700 (PDT) Message-ID: <325C2710.167EB0E7@whistle.com> Date: Wed, 09 Oct 1996 15:28:32 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: sthaug@nethelp.no CC: luigi@labinfo.iet.unipi.it, henrich@crh.cl.msu.edu, danj@netcom.com, freebsd-current@FreeBSD.org Subject: Re: 961006-SNAP comments References: <199610091948.UAA04138@labinfo.iet.unipi.it> <7186.844899046@verdi.nethelp.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk sthaug@nethelp.no wrote: > > > > > user environment), but why /var? With newsyslog doing clean log rotations, var > > > > > > > theoretically to help run / as a readonly partition > > > on NFS systems or such and > > > have the 'variable' files on their own partition. > > > > just theoretically, since a lot of machine dependant stuff is in /etc. > > I'd actually like to do a readonly /, and it looks to me like it > should be possible: > > 1. Symlink those few variable files that are left, e.g. /etc/ntp.drift > and /etc/ssh_random_seed into /var/run. > > 2. Use DEVFS for the devices. > > Any reason why this wouldn't work? > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no I've done this we throw the writable files in a writable partition and use symlinks.. vipw fails as it replaces the symlinks but otherwise it seems to work. devfs is the key, but you need to mount it from init. pester phk for teh right spot to do it.. From owner-freebsd-current Wed Oct 9 15:38:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA14112 for current-outgoing; Wed, 9 Oct 1996 15:38:06 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-183.ut.nl.ibm.net [139.92.42.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA14090 for ; Wed, 9 Oct 1996 15:37:56 -0700 (PDT) Received: (from jhs@localhost) by vector.jhs.no_domain (8.7.5/8.6.9) id XAA04561; Wed, 9 Oct 1996 23:28:36 +0100 (MET) Date: Wed, 9 Oct 1996 23:28:36 +0100 (MET) Message-Id: <199610092228.XAA04561@vector.jhs.no_domain> To: current@freebsd.org Subject: libgcc.a ___main From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Mailer: EXMH 1.6.7, PGP available X-Address: Holz Strasse 27d, 80469 Munich, Germany X-Phone: +49.89.268616 X-Fax: +49.89.2608126 X-Web: http://www.freebsd.org/~jhs/ Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk To Current@ Please ignore my question regarding ___main missing from libgcc.a (solved). (Sorry I can't assert the same subject, haven't got the post back yet.) Julian --- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Wed Oct 9 16:07:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA16410 for current-outgoing; Wed, 9 Oct 1996 16:07:56 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA16394 for ; Wed, 9 Oct 1996 16:07:40 -0700 (PDT) Received: from localhost (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with SMTP id QAA15651 for ; Wed, 9 Oct 1996 16:08:41 -0700 Date: Wed, 9 Oct 1996 16:08:39 -0700 (PDT) From: Veggy Vinny To: current@FreeBSD.ORG Subject: Good Job guys Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just wanted to say thanks for the new speed improvements you've made in the latest -current.... I was amazed to see the machine complete booting within 2 minutes! It used to take almost 10 minutes with all the networking and stuff. Anyways, is the uname -a for the -current kernel supposed to say SNAP-100496? Cheers, -Vince- GaiaNet Corporation Unix Networking Operations From owner-freebsd-current Wed Oct 9 16:44:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA19084 for current-outgoing; Wed, 9 Oct 1996 16:44:38 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA19075 for ; Wed, 9 Oct 1996 16:44:35 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.0/8.8.Beta.3) with SMTP id SAA04441 for ; Wed, 9 Oct 1996 18:44:34 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.15) id ; Wed, 9 Oct 96 18:43 CDT Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.Beta.6/8.8.Beta.3) id SAA12190 for current@freebsd.org; Wed, 9 Oct 1996 18:40:27 -0500 (CDT) From: Karl Denninger Message-Id: <199610092340.SAA12190@Jupiter.Mcs.Net> Subject: Kaboom! To: current@freebsd.org Date: Wed, 9 Oct 1996 18:40:27 -0500 (CDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We're getting a lot of these -- about once every two hours... Copyright 1994 Free Software Foundation, Inc...(no debugging symbols found)... IdlePTD 218000 current pcb at 1efdc8 panic: page fault #0 0xf0113933 in boot () (kgdb) where #0 0xf0113933 in boot () #1 0xf0113bf2 in panic () #2 0xf01bd17a in trap_fatal () #3 0xf01bcc68 in trap_pfault () #4 0xf01bc94f in trap () #5 0xf01b1fc1 in calltrap () #6 0xf01446ce in ip_input () #7 0xf0144744 in ipintr () #8 0xf01b32dd in swi_net_next () #9 0x2b900 in ?? () #10 0xc108 in ?? () #11 0xbc21 in ?? () #12 0xc2fd in ?? () #13 0x1bcd in ?? () #14 0x2f75 in ?? () #15 0x3b8a in ?? () #16 0x107e in ?? () This is consistent -- the kernel is 961004-SNAP. Ideas? Is this related to the changes made recently in the ip routines to counteract SYN floods? -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-current Wed Oct 9 16:57:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA20068 for current-outgoing; Wed, 9 Oct 1996 16:57:48 -0700 (PDT) Received: from bunyip.cc.uq.oz.au (daemon@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA20061 for ; Wed, 9 Oct 1996 16:57:44 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.oz.au (8.7.6/8.7.3) id JAA19880 for current@freebsd.org; Thu, 10 Oct 1996 09:57:41 +1000 Received: from pandora.devetir.qld.gov.au by ogre.devetir.qld.gov.au (8.7.5/DEVETIR-E0.3a) with ESMTP id KAA06986 for ; Thu, 10 Oct 1996 10:02:20 +1000 (EST) Received: from netfl15a.devetir.qld.gov.au (netfl15a.devetir.qld.gov.au [167.123.24.12]) by pandora.devetir.qld.gov.au (8.6.10/8.6.12) with ESMTP id JAA23114 for ; Thu, 10 Oct 1996 09:59:36 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id AAA15495 for ; Thu, 10 Oct 1996 00:00:29 GMT Message-Id: <199610100000.AAA15495@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6.5 12/11/95 To: current@freebsd.org Subject: Small buglet in atapi LKM code X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Oct 1996 10:00:29 +1000 From: Stephen Hocking Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ===> atapi cc -O2 -m486 -pipe -nostdinc -I. -DATAPI_MODULE -DKERNEL -DACTUALLY_LKM_NOT_KER NEL -I/usr/src/lkm/atapi/../../sys -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Winline -Wpointer-arith -c /usr/src/lkm/atapi/../../sys/i386/isa/atapi.c In file included from /usr/src/lkm/atapi/../../sys/i386/isa/atapi.c:118: machine/clock.h:12: opt_cpu.h: No such file or directory *** Error code 1 Stop. *** Error code 1 Stop. -- The views expressed above are not those of the Worker's Compensation Board of Queensland, Australia. From owner-freebsd-current Wed Oct 9 17:08:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA20951 for current-outgoing; Wed, 9 Oct 1996 17:08:52 -0700 (PDT) Received: (from hsu@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA20944 for current; Wed, 9 Oct 1996 17:08:50 -0700 (PDT) Date: Wed, 9 Oct 1996 17:08:50 -0700 (PDT) From: Jeffrey Hsu Message-Id: <199610100008.RAA20944@freefall.freebsd.org> To: current Subject: Re: dlsym broken in -current Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Okay, as has been pointed out to me, the test program I hastily sent out, but did not run to completion because it core-dumps on my -current system, had a minor logic bug with the return value of dlsym which was unrelated to the problem at hand. Here's a simpler test program: #include #include main() { void *addr; if (!(addr = dlsym(NULL, "_main"))) { fprintf(stderr, "dlsym failed: %s\n", dlerror()); } printf("addr retrieved as 0x%x\n", addr); } From owner-freebsd-current Wed Oct 9 17:15:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA21638 for current-outgoing; Wed, 9 Oct 1996 17:15:44 -0700 (PDT) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA21630 for ; Wed, 9 Oct 1996 17:15:41 -0700 (PDT) Received: from pauling.salk.edu (pauling [198.202.70.108]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id RAA29027 for ; Wed, 9 Oct 1996 17:15:41 -0700 (PDT) Date: Wed, 9 Oct 1996 17:15:42 -0700 (PDT) From: Tom Bartol To: current@freebsd.org Subject: NFS weirdness in -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Try this: At the same time as doing a: dd if=/dev/zero of=ick bs=8192 count=1024 to an NFS mounted directory in one xterm do an: ls from within the same NFS mounted directory in another xterm. What happens is the ls hangs until the dd finishes. I don't think this the correct behavior and it certainly is not the behavior I saw under 2.1.0R. Anybody have a clue here? Otherwise, -current is shaping up nicely -- it's squeezing another 15% speed-up out my Monte Carlo simulator (which, BTW, uses my own, portable 48 bit generator adapted from Knuth, and which can run in parallel on SMP etc...). Thanx, Tom From owner-freebsd-current Wed Oct 9 18:06:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA25861 for current-outgoing; Wed, 9 Oct 1996 18:06:59 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA25852; Wed, 9 Oct 1996 18:06:55 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id KAA16289; Thu, 10 Oct 1996 10:36:23 +0930 From: Michael Smith Message-Id: <199610100106.KAA16289@genesis.atrad.adelaide.edu.au> Subject: Re: .depend To: wosch@freebsd.org Date: Thu, 10 Oct 1996 10:36:22 +0930 (CST) Cc: rkw@dataplex.net, steve@freefall.freebsd.org, current@freebsd.org In-Reply-To: <199610091312.PAA01354@campa.panke.de> from "Wolfram Schneider" at Oct 9, 96 03:12:55 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Wolfram Schneider stands accused of saying: > > > >Why change "make"? > > Because .depend is wired in make(1). There is no way > to stop make(1) to read .depend if exists. There is no way > to use an other depend file, e.g. `.depend.i486' or > `.depend.hostname'. > > Example > $ mkdep > $ mkdep -f .depend.debug -DDEBUG > $ mkdep -f .depend.i386 -Di386 > > You can now include .depend.debug in ./Makefile, but make(1) also > read .depend because it exists. Irrelevant. .depend is in the object directory, and you're not going to use the same object directory for more than one target. > Wolfram -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Oct 9 18:27:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA27375 for current-outgoing; Wed, 9 Oct 1996 18:27:04 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA27315 for ; Wed, 9 Oct 1996 18:26:47 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id KAA16358; Thu, 10 Oct 1996 10:55:40 +0930 From: Michael Smith Message-Id: <199610100125.KAA16358@genesis.atrad.adelaide.edu.au> Subject: Re: /usr/bin/install in -current broken To: richardc@CSUA.Berkeley.EDU (Veggy Vinny) Date: Thu, 10 Oct 1996 10:55:39 +0930 (CST) Cc: imp@village.org, current@FreeBSD.org In-Reply-To: from "Veggy Vinny" at Oct 9, 96 01:14:54 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Veggy Vinny stands accused of saying: > > > > Might I suggest that you have '.' in your path before /usr/bin and > > that top also has a install program that is being grabbed first? The > > error message for things that /usr/bin/install doesn't understand > > looks more like: > > Actually, you're right and thanks for pointing it out so how do I > tell which install the make install wants? It wants the one in /usr/bin. Take '.' out of your path. (Sheesh, and you wonder why your local hackers have such an easy time getting root on your systems. Gawd.) > -Vince- GaiaNet Corporation Unix Networking Operations -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Oct 9 18:29:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA27650 for current-outgoing; Wed, 9 Oct 1996 18:29:01 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA27644 for ; Wed, 9 Oct 1996 18:28:58 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id KAA16373; Thu, 10 Oct 1996 10:58:45 +0930 From: Michael Smith Message-Id: <199610100128.KAA16373@genesis.atrad.adelaide.edu.au> Subject: Re: /usr/bin/install in -current broken To: richardc@CSUA.Berkeley.EDU (Veggy Vinny) Date: Thu, 10 Oct 1996 10:58:44 +0930 (CST) Cc: imp@village.org, current@freebsd.org In-Reply-To: from "Veggy Vinny" at Oct 9, 96 01:33:24 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Veggy Vinny stands accused of saying: > > Hmmm, is moving the '.' to the last component in the path still a > security risk? I guess you are right that I don't want to have it in > root's path but I guess as the last component it should be okay since no > one can name something with the same name and have me run it... =) How long is it since you typo'ed a command as root? 'xs' instead of 'cd', 'la' or ';s' instead of 'ls', or 'mroe' or 'dirt' (if you're an ex-DOS/VMSer) or whatever. Don't do it. Only put trusted directories on your path as root. > -Vince- GaiaNet Corporation Unix Networking Operations -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Oct 9 18:34:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA27898 for current-outgoing; Wed, 9 Oct 1996 18:34:19 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA27893 for ; Wed, 9 Oct 1996 18:34:16 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id SAA00378; Wed, 9 Oct 1996 18:34:06 -0700 (PDT) Message-Id: <199610100134.SAA00378@austin.polstra.com> To: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= cc: freebsd-current@freebsd.org Subject: Re: ldconfig problem In-reply-to: Your message of "Thu, 10 Oct 1996 06:45:41 +0900." <199610092145.GAA04189@bourbon.sfc.wide.ad.jp> Date: Wed, 09 Oct 1996 18:34:06 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Guess what! Things are getting worse. (At least it seems to me that > way.) I started up gdb and and did ``help set'' to find out some > stuff. Gdb gave me the first page of the help screen as usual, but as > I hit return key to go onto the next page, it died on signal 3 with > following message after showing the second page: > > gdb internal error: Memory corruption > Quit (core dumped) > > This error is not affected by ld.so.hints change. It happens > regardless of whether kaffe runs or not. So, I guess now we have to > do some investigation on gdb.... ;_) Gdb does that on my -current system too. I last updated the system a few days ago, on October 5. I copied the -current libc.so.3.0 onto my -stable system, and then executed the -current gdb from there. So that was using the dynamic linker and ld.so.hints from -stable, and the gdb, crt0.o and libc from -current. It still got the same error. I have a feeling that this particular problem is unrelated to the dynamic linker. It's just a feeling, though. I'm not sure yet. 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-current Wed Oct 9 18:43:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA28293 for current-outgoing; Wed, 9 Oct 1996 18:43:42 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA28288 for ; Wed, 9 Oct 1996 18:43:38 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA16437 for current@freebsd.org; Thu, 10 Oct 1996 11:13:31 +0930 From: Michael Smith Message-Id: <199610100143.LAA16437@genesis.atrad.adelaide.edu.au> Subject: 'dead' binary stays 'dead'? To: current@freebsd.org Date: Thu, 10 Oct 1996 11:13:30 +0930 (CST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Howdy people; (particularly VM people) I have a system here that was behaving a little oddly. Overnight it's been running some software that regularly exec's 'ls' to examine the contents of a directory (maybe every 20 seconds or so).(1) At some point, 'ls' died with a sig11. Rerunning 'ls' caused an immediate sig11 again. I tried to build another 'ls' so that I could look at the cores, but no luck 8( If it's at all enlightening, I ran the newly-built 'ls', and it worked (no surprises there); however now the 'old' ls works fine too. So I suspect that this has something to do with the 'sticky text' code not being asked to explicitly forget about programs that have been killed by signals. I'm aware that this is perhaps a difficult one to resolve tidily, but I think my scenario may have been : - ls loads, a memory error of some sort occurs. - ls runs, is killed due to memory error. - ls is rerun, old text is used, is killed again courtesy of memory error. Obviously, machines with serious memory errors deserve to loose infinitely, but this box doesn't fall into that category. It's survived numerous 'make world' cycles faultlessly, and stands up all day to the excessive pounding that the physics geeks here subject it to. Comments? Refutations? Merciless laughter? -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Oct 9 18:45:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA28406 for current-outgoing; Wed, 9 Oct 1996 18:45:58 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA28400; Wed, 9 Oct 1996 18:45:54 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA16453; Thu, 10 Oct 1996 11:14:29 +0930 From: Michael Smith Message-Id: <199610100144.LAA16453@genesis.atrad.adelaide.edu.au> Subject: Re: .depend To: terry@lambert.org (Terry Lambert) Date: Thu, 10 Oct 1996 11:14:29 +0930 (CST) Cc: rkw@dataplex.net, wosch@freebsd.org, steve@freefall.freebsd.org, current@freebsd.org In-Reply-To: <199610092052.NAA18730@phaeton.artisoft.com> from "Terry Lambert" at Oct 9, 96 01:52:17 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert stands accused of saying: > > > IMHO, this entire discussion results from a fundamental error in the > > methodology of building multiple versions from a single set of sources. > > Rather than "kluge" something else into "make" so you can "get by", we > > should fix the methodology. > > What happens when I want to build several different machine architectures > from the same NFS mounted sources instead of placing 3 times the SUP > load on one of the severs to get thrre times the trees on three times > the local diskk space used? .depend is in the object directory. Unless you're a total loser, you _will_ have seperate object directories, right? > Terry Lambert -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Oct 9 19:01:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA29204 for current-outgoing; Wed, 9 Oct 1996 19:01:43 -0700 (PDT) Received: from prozac.neuron.net (prozac.neuron.net [165.254.1.213]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA29195; Wed, 9 Oct 1996 19:01:38 -0700 (PDT) Received: (from amir@localhost) by prozac.neuron.net (8.7.5/8.6.12) id WAA29721; Wed, 9 Oct 1996 22:09:32 -0400 (EDT) From: "Amir Y. Rosenblatt" Message-Id: <199610100209.WAA29721@prozac.neuron.net> Subject: Re: Java,Netscape, & AccelX In-Reply-To: from Mark Mayo at "Oct 5, 96 03:26:13 pm" To: mark@hi-fi.com (Mark Mayo) Date: Wed, 9 Oct 1996 22:09:31 -0400 (EDT) Cc: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm guessing it's some sort of clash between libc.so and the AccelX server > -- am I correct in assuming this? > > Someone please tell me they've solver this problem and that I'm not a > random incident with no hope... I'm contacting Xinside as well, but I > believe they only support up to v2.1R. I'm using Netscape 3.0 with -current (from source as of the late august), a Number Nine Imagine 128 video card, and Accelerated X and seem to have no problem with applets. I just went to Sun's sample applets (http://java.sun.com:80/applets/applets.html) and they're working fine. Have yet to have any problems with Accelerated X. -Amir From owner-freebsd-current Wed Oct 9 19:36:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA02415 for current-outgoing; Wed, 9 Oct 1996 19:36:54 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA02396 for ; Wed, 9 Oct 1996 19:36:51 -0700 (PDT) Received: from localhost (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with SMTP id TAA06791 for ; Wed, 9 Oct 1996 19:37:53 -0700 Date: Wed, 9 Oct 1996 19:37:51 -0700 (PDT) From: Veggy Vinny To: current@FreeBSD.ORG Subject: latest -current fails Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk make world produces the following: ===> gnu/usr.bin/cvs ===> gnu/usr.bin/cvs/lib ".depend", line 85: Need an operator Fatal errors encountered -- cannot continue *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. root@earth [7:34pm][/usr/src] >> Vince From owner-freebsd-current Wed Oct 9 19:39:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA02641 for current-outgoing; Wed, 9 Oct 1996 19:39:27 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA02632 for ; Wed, 9 Oct 1996 19:39:23 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id VAA09727; Wed, 9 Oct 1996 21:38:53 -0500 (EST) From: "John S. Dyson" Message-Id: <199610100238.VAA09727@dyson.iquest.net> Subject: Re: 'dead' binary stays 'dead'? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 9 Oct 1996 21:38:53 -0500 (EST) Cc: current@FreeBSD.org In-Reply-To: <199610100143.LAA16437@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Oct 10, 96 11:13:30 am Reply-To: dyson@FreeBSD.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Obviously, machines with serious memory errors deserve to loose > infinitely, but this box doesn't fall into that category. It's > survived numerous 'make world' cycles faultlessly, and stands up all > day to the excessive pounding that the physics geeks here subject it > to. > > Comments? Refutations? Merciless laughter? > You are describing a problem that I know *can* happen, but I don't know why. In essence, once you have a copy of a programs .text, .data in memory, it will continue to be cached until the memory is reclaimed. If any part of that image gets modified, then it will stay modified. If you remove the file that has it's in-memory image broken, that brokenness will go away. However, if you try to copy the file like: cp ls ls.new, it is likely that ls.new will also be broken because the same image that is executed is also in the buffer cache (the cache and the image are pretty much one in the same.) The best way to make the problem go-away is to fill memory and cause the broken binary to disappear. Now, the complicated part is why it happened. I just don't know why... Are you using NFS? Are you using the most recent -current (snap)?... You know the typical questions :-). John From owner-freebsd-current Wed Oct 9 19:57:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA04156 for current-outgoing; Wed, 9 Oct 1996 19:57:24 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA04146; Wed, 9 Oct 1996 19:57:16 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id MAA16615; Thu, 10 Oct 1996 12:27:05 +0930 From: Michael Smith Message-Id: <199610100257.MAA16615@genesis.atrad.adelaide.edu.au> Subject: Re: 'dead' binary stays 'dead'? To: dyson@FreeBSD.org Date: Thu, 10 Oct 1996 12:27:05 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, current@FreeBSD.org In-Reply-To: <199610100238.VAA09727@dyson.iquest.net> from "John S. Dyson" at Oct 9, 96 09:38:53 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk John S. Dyson stands accused of saying: > > You are describing a problem that I know *can* happen, but I don't know > why. In essence, once you have a copy of a programs .text, .data in > memory, it will continue to be cached until the memory is reclaimed. > If any part of that image gets modified, then it will stay modified. ... but if these pages are the text and data, they're read-only, correct? ie. the only modification possible is via hardware error? > If you remove the file that has it's in-memory image broken, that > brokenness will go away. However, if you try to copy the > file like: cp ls ls.new, it is likely that ls.new will also be broken > because the same image that is executed is also in the buffer cache > (the cache and the image are pretty much one in the same.) The > best way to make the problem go-away is to fill memory and cause the > broken binary to disappear. Now, the complicated part is why it happened. The relevant part of the 'going away' incident looked like this : $ ls $ cp -r /usr/src/bin/ls . $ cd ls $ CFLAGS=-g; make $ gdb ls ../ls.core $ ./ls $ ls So I guess it's possible that the memory was reclaimed while I was rebuilding a new 'ls'. > Are you using NFS? Are you using the most recent -current (snap)?... > You know the typical questions :-). Sorry 8) NFS client only (but not on any of the filesystems being used), supped at about the same time as the latest SNAP. > John -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Oct 9 20:56:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA07327 for current-outgoing; Wed, 9 Oct 1996 20:56:14 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA07322; Wed, 9 Oct 1996 20:56:09 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id WAA11855; Wed, 9 Oct 1996 22:54:13 -0500 (EST) From: "John S. Dyson" Message-Id: <199610100354.WAA11855@dyson.iquest.net> Subject: Re: 'dead' binary stays 'dead'? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 9 Oct 1996 22:54:13 -0500 (EST) Cc: dyson@FreeBSD.org, msmith@atrad.adelaide.edu.au, current@FreeBSD.org In-Reply-To: <199610100257.MAA16615@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Oct 10, 96 12:27:05 pm Reply-To: dyson@FreeBSD.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > John S. Dyson stands accused of saying: > > > > You are describing a problem that I know *can* happen, but I don't know > > why. In essence, once you have a copy of a programs .text, .data in > > memory, it will continue to be cached until the memory is reclaimed. > > If any part of that image gets modified, then it will stay modified. > > ... but if these pages are the text and data, they're read-only, correct? > ie. the only modification possible is via hardware error? > Or software bug :-). (Memory stomp could cause it, or an incorrect mapping update in the VM code.) > > The relevant part of the 'going away' incident looked like this : > > $ ls > > $ cp -r /usr/src/bin/ls . > $ cd ls > $ CFLAGS=-g; make > $ gdb ls ../ls.core > > $ ./ls > > $ ls > > > So I guess it's possible that the memory was reclaimed while I was rebuilding > a new 'ls'. > Probably. > > > Are you using NFS? Are you using the most recent -current (snap)?... > > You know the typical questions :-). > > Sorry 8) NFS client only (but not on any of the filesystems being used), > supped at about the same time as the latest SNAP. > We all need to keep an eye on the problem... This is the first time that I have heard of it -- but doesn't mean that it isn't there :-)... John From owner-freebsd-current Wed Oct 9 21:04:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA07738 for current-outgoing; Wed, 9 Oct 1996 21:04:27 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA07728; Wed, 9 Oct 1996 21:04:21 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id VAA01047; Wed, 9 Oct 1996 21:04:19 -0700 (PDT) Message-Id: <199610100404.VAA01047@austin.polstra.com> To: Jeffrey Hsu Cc: current@freefall.freebsd.org, max@wide.ad.jp Date: Wed, 09 Oct 1996 21:04:19 -0700 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thanks for the test program. I found the problem in the dynamic linker. It's this new code in dlsym(): static void * __dlsym(fd, sym) void *fd; char *sym; { struct so_map *smp = (struct so_map *)fd, *src_map = NULL; struct nzlist *np; long addr; /* * Restrict search to passed map if dlopen()ed. */ if (LM_PRIVATE(smp)->spd_flags & RTLD_DL) src_map = smp; The code doesn't take into account the fact that "smp" can be NULL. I will commit a fix ASAP. This could also (hopefully) be the cause of the core dumps that Masafumi reported from running kaffe. 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-current Wed Oct 9 21:35:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA11917 for current-outgoing; Wed, 9 Oct 1996 21:35:57 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA11865; Wed, 9 Oct 1996 21:35:48 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id OAA17545; Thu, 10 Oct 1996 14:05:40 +0930 From: Michael Smith Message-Id: <199610100435.OAA17545@genesis.atrad.adelaide.edu.au> Subject: Re: 'dead' binary stays 'dead'? To: dyson@FreeBSD.org Date: Thu, 10 Oct 1996 14:05:39 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, current@FreeBSD.org In-Reply-To: <199610100354.WAA11855@dyson.iquest.net> from "John S. Dyson" at Oct 9, 96 10:54:13 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk John S. Dyson stands accused of saying: > > > > ... but if these pages are the text and data, they're read-only, correct? > > ie. the only modification possible is via hardware error? > > > Or software bug :-). (Memory stomp could cause it, or an incorrect > mapping update in the VM code.) Argh. Not what I wanted to know 8( > We all need to keep an eye on the problem... This is the first time that > I have heard of it -- but doesn't mean that it isn't there :-)... Would it be possible to have the memory reclaimed immediately if the program is killed by an unhandled signal? Generally speaking one wouldn't expect that would be a situation one would optimise for, and it would perhaps improve robustness in cases such as this... > John -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Oct 9 21:53:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA14454 for current-outgoing; Wed, 9 Oct 1996 21:53:02 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA14447; Wed, 9 Oct 1996 21:52:52 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id XAA08260; Wed, 9 Oct 1996 23:46:11 -0500 (EST) From: "John S. Dyson" Message-Id: <199610100446.XAA08260@dyson.iquest.net> Subject: Re: 'dead' binary stays 'dead'? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 9 Oct 1996 23:46:11 -0500 (EST) Cc: dyson@FreeBSD.org, msmith@atrad.adelaide.edu.au, current@FreeBSD.org In-Reply-To: <199610100435.OAA17545@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Oct 10, 96 02:05:39 pm Reply-To: dyson@FreeBSD.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Argh. Not what I wanted to know 8( > I do get bad news once in a while also. Note that it CAN be hardware, but could be an errant driver, VM system, anywhere in the kernel. > > > We all need to keep an eye on the problem... This is the first time that > > I have heard of it -- but doesn't mean that it isn't there :-)... > > Would it be possible to have the memory reclaimed immediately if the program > is killed by an unhandled signal? Generally speaking one wouldn't expect > that would be a situation one would optimise for, and it would perhaps > improve robustness in cases such as this... > That is actually an interesting idea!!! John From owner-freebsd-current Wed Oct 9 22:10:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA17968 for current-outgoing; Wed, 9 Oct 1996 22:10:14 -0700 (PDT) Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA17961 for ; Wed, 9 Oct 1996 22:10:11 -0700 (PDT) Received: by diablo.ppp.de (Smail3.1.28.1 #1) id m0vBDNL-000Qn8C; Thu, 10 Oct 96 06:09 MET Received: from [193.141.161.123] (monster.pong.ppp.de [193.141.161.123]) by pong.PPP.DE (8.7.5/8.6.12) with ESMTP id XAA20192; Wed, 9 Oct 1996 23:41:24 +0200 (MET DST) Message-Id: In-Reply-To: <325ACC75.446B9B3D@whistle.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 9 Oct 1996 23:40:59 +0200 To: Julian Elischer From: Stefan Bethke Subject: Re: Netatalk.. anyone tried the new release? Cc: current@freebsd.org, netatalk-admins@umich.edu Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 14:49 Uhr -0700 08.10.1996, Julian Elischer wrote: >Stefan Bethke wrote: >> netatalk-1.3.3 compiles, but atalkd isn't able to run (haven't looked >> further why). netatalk 1.4b1 doesn't compile on 2.1.5-R (errors in >> compiling afpd, something with getquota()). >(just comment out all the quota stuff :) > >the patch in control.c in atalkd in 1.4 was based on the sam epatch on >1.3.3 >and allowed atalkd to run by default.. >it does run >if you supply a conf file, even without the patch >as that code isn't run in that case. I supplied a conf file ("ed0 -phase 2"), but atalkd didn't get the zone list from our seed router. Most interestingly, the original patches applied to 2.1.0-R work on our production system, which I wanted to up to 2.1.5-R; I think I wait a little with that :-( >I assume you have the FreeBSD patches for 1.3.3? > >the kernel code we have came from the 2.1 port of 1.3.3 >I ported it to 2.2 and checked it in.. I'll look at it when I have more time. The kernel patches for 2.1.0 are definitly buggy (as far as I can tell), 'cause they have no means of receiving or sending packets from/to a machine in the startup range (see Inside AppleTalk, pp.4-8, "Node address aquisition on extended networks"). Also (maybe because of that), atalkd doesn't work on an extended network (ethernet) without a seed router, that is, a network running constantly in the startup range. Currently, you need a seed router to use netatalk; running netatalk as a seed router does not suffice, because Macs try to get network information from the seed router, sending a broadcast GetNetInfo with source address in the startup range (or the last known network address, which also doesn't work with standard 4.4 routing). This seems to be true for at least Linux also. Stefan (Please note the cross-post to netatalk-admins, hopefully we two are not the only ones interdested in getting netatalk to work completely on FreeBSD.) -- Stefan Bethke Hamburg, Germany From owner-freebsd-current Wed Oct 9 22:46:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA20944 for current-outgoing; Wed, 9 Oct 1996 22:46:19 -0700 (PDT) Received: from bourbon.sfc.wide.ad.jp (root@bourbon.sfc.wide.ad.jp [133.4.30.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA20937; Wed, 9 Oct 1996 22:46:15 -0700 (PDT) Received: from bourbon (max@localhost [127.0.0.1]) by bourbon.sfc.wide.ad.jp (8.7.6/3.4W409/27/96) with ESMTP id OAA09234; Thu, 10 Oct 1996 14:45:59 +0900 (JST) Message-Id: <199610100545.OAA09234@bourbon.sfc.wide.ad.jp> To: jdp@polstra.com Cc: hsu@freefall.freebsd.org, current@freefall.freebsd.org, max@wide.ad.jp From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= In-Reply-To: Your message of "Wed, 09 Oct 1996 21:04:19 -0700" References: <199610100404.VAA01047@austin.polstra.com> X-Mailer: Mew version 1.06 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 10 Oct 1996 14:45:59 +0900 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk jdp> This could also (hopefully) be the cause of the core dumps jdp> that Masafumi reported from running kaffe. I hate to tell you but it didn't solve the problem. The situation seems to me exactly the same as before. Max. From owner-freebsd-current Wed Oct 9 23:03:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA22210 for current-outgoing; Wed, 9 Oct 1996 23:03:47 -0700 (PDT) Received: (from hsu@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA22199; Wed, 9 Oct 1996 23:03:44 -0700 (PDT) Date: Wed, 9 Oct 1996 23:03:44 -0700 (PDT) From: Jeffrey Hsu Message-Id: <199610100603.XAA22199@freefall.freebsd.org> To: jdp@polstra.com Cc: current Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I hate to tell you but it didn't solve the problem. It does, however, solve my problem with the JDK coredumping w/ -current. I think it should also fix Jake Hamby's reported problem trying to run the JDK w/ -current. Thanks, John. From owner-freebsd-current Wed Oct 9 23:04:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA22310 for current-outgoing; Wed, 9 Oct 1996 23:04:05 -0700 (PDT) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA22272 for ; Wed, 9 Oct 1996 23:04:01 -0700 (PDT) Received: from grumble.grondar.za (mark@localhost.grondar.za [127.0.0.1]) by grumble.grondar.za (8.7.6/8.7.3) with ESMTP id IAA12278; Thu, 10 Oct 1996 08:03:29 +0200 (SAT) Message-Id: <199610100603.IAA12278@grumble.grondar.za> To: Veggy Vinny cc: Warner Losh , current@FreeBSD.org Subject: Re: /usr/bin/install in -current broken Date: Thu, 10 Oct 1996 08:03:29 +0200 From: Mark Murray Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Veggy Vinny wrote: > Hmmm, is moving the '.' to the last component in the path still a > security risk? I guess you are right that I don't want to have it in > root's path but I guess as the last component it should be okay since no > one can name something with the same name and have me run it... =) Of course. Al someon has to do is name a script/trojan/whatever as anything that is commonly mistyped to get you. How often do you type (for instance) l s-al for ls -al fin or fnid for find etc? This leaves (in these cases) l, fin an fnid open for an attacker. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Wed Oct 9 23:42:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA23819 for current-outgoing; Wed, 9 Oct 1996 23:42:14 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA23814 for ; Wed, 9 Oct 1996 23:42:05 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id QAA08305; Thu, 10 Oct 1996 16:37:40 +1000 Date: Thu, 10 Oct 1996 16:37:40 +1000 From: Bruce Evans Message-Id: <199610100637.QAA08305@godzilla.zeta.org.au> To: luigi@labinfo.iet.unipi.it, sthaug@nethelp.no Subject: Re: 961006-SNAP comments Cc: danj@netcom.com, freebsd-current@FreeBSD.org, henrich@crh.cl.msu.edu, julian@whistle.com Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >2. Use DEVFS for the devices. > >Any reason why this wouldn't work? Yes, devfs is too broken to use. E.g., anyone can chmod and chown anything in it. Bruce From owner-freebsd-current Thu Oct 10 00:45:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA26608 for current-outgoing; Thu, 10 Oct 1996 00:45:10 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA26602 for ; Thu, 10 Oct 1996 00:45:08 -0700 (PDT) Received: from localhost (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with SMTP id AAA25705; Thu, 10 Oct 1996 00:45:52 -0700 Date: Thu, 10 Oct 1996 00:45:51 -0700 (PDT) From: Veggy Vinny To: Mark Murray cc: Warner Losh , current@FreeBSD.org Subject: Re: /usr/bin/install in -current broken In-Reply-To: <199610100603.IAA12278@grumble.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 10 Oct 1996, Mark Murray wrote: > Veggy Vinny wrote: > > Hmmm, is moving the '.' to the last component in the path still a > > security risk? I guess you are right that I don't want to have it in > > root's path but I guess as the last component it should be okay since no > > one can name something with the same name and have me run it... =) > > Of course. Al someon has to do is name a script/trojan/whatever > as anything that is commonly mistyped to get you. > > How often do you type (for instance) > > l s-al for ls -al > fin or fnid for find > etc? Not that often... > This leaves (in these cases) l, fin an fnid open for an attacker. It seems like on our machines, they don't hack by logging in to the machine but I don't know what they did to put a program in a port and then they telnet to it to get root shell without even logging in... Cheers, -Vince- GaiaNet Corporation Unix Networking Operation From owner-freebsd-current Thu Oct 10 01:07:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA27861 for current-outgoing; Thu, 10 Oct 1996 01:07:20 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA27818 for ; Thu, 10 Oct 1996 01:06:54 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA05492; Thu, 10 Oct 1996 08:36:03 +0100 From: Luigi Rizzo Message-Id: <199610100736.IAA05492@labinfo.iet.unipi.it> Subject: Re: 961006-SNAP comments To: sthaug@nethelp.no Date: Thu, 10 Oct 1996 08:36:03 +0100 (MET) Cc: julian@whistle.com, henrich@crh.cl.msu.edu, danj@netcom.com, freebsd-current@FreeBSD.org In-Reply-To: <7186.844899046@verdi.nethelp.no> from "sthaug@nethelp.no" at Oct 10, 96 00:10:27 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > theoretically to help run / as a readonly partition > > > on NFS systems or such and > > > have the 'variable' files on their own partition. > > > > just theoretically, since a lot of machine dependant stuff is in /etc. > > I'd actually like to do a readonly /, and it looks to me like it > should be possible: > > 1. Symlink those few variable files that are left, e.g. /etc/ntp.drift > and /etc/ssh_random_seed into /var/run. have done this for a long time, a shared readonly root for diskless machines. /var is in a MFS partition. It works well, but it's a pain at every release to move files and create symlinks and modify /etc/rc to mount and init /var before trying to access files. And, as someone noticed, vipw does not like much this kind of settings. [I know I should be less lazy and write some script which does the work for me. :( ] > 2. Use DEVFS for the devices. Don't know about devfs, the way I do it now is to build a tar archive with all the stuff that goes into the writable /var partition, and extract it at boot time. This includes /var/dev which is pointed to from /dev. 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-current Thu Oct 10 01:28:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA29461 for current-outgoing; Thu, 10 Oct 1996 01:28:47 -0700 (PDT) Received: from nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA29455 for ; Thu, 10 Oct 1996 01:28:42 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by nike.efn.org (8.7.5/8.7.3) with SMTP id BAA11386 for ; Thu, 10 Oct 1996 01:28:35 -0700 (PDT) Date: Thu, 10 Oct 1996 01:28:31 -0700 (PDT) From: John-Mark Gurney X-Sender: jmg@nike Reply-To: John-Mark Gurney To: freebsd-current@freebsd.org Subject: libz in current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am helping a friend install a 0801 system... (this was before the 1006 snap was released)... and as it is pretty current ;).. I've been using the ports and packages from current... is there a reason for uping the shared lib version of libz? the one I have from the package of old 2.1.5 or there abouts is something like 1.3 I think.. is there any difference? also... why is the default for shared libs 2.0? I'm thinking it's that freebsd is in it's 2.x series... but then libz's shared lib version should of been over written... thanks for your comments... ttyl... John-Mark gurney_j@efn.org http://resnet.uoregon.edu/~gurney_j/ Modem/FAX: (541) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix) From owner-freebsd-current Thu Oct 10 02:15:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA02791 for current-outgoing; Thu, 10 Oct 1996 02:15:34 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA02783 for ; Thu, 10 Oct 1996 02:15:26 -0700 (PDT) Received: (from pallenby@localhost) by zibbi.mikom.csir.co.za (8.7.6/8.7.3) id LAA17791 for current@freebsd.org; Thu, 10 Oct 1996 11:15:20 +0200 (SAT) From: Paul Allenby Message-Id: <199610100915.LAA17791@zibbi.mikom.csir.co.za> Subject: Re: 961006-SNAP comments To: current@freebsd.org Date: Thu, 10 Oct 1996 11:15:19 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL24 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all! When I installed the 961006-SNAP and was in the config editor, I tried to set the irq of the ed0 device to -1 as I was not sure of the cards interrupt. It appears that only the values 1...15 are accepted ( '?' didn't work either.) Is this what was intended? Paul P.Allenby, Mikomtek, CSIR, South Africa. From owner-freebsd-current Thu Oct 10 02:53:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA05280 for current-outgoing; Thu, 10 Oct 1996 02:53:43 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA05266 for ; Thu, 10 Oct 1996 02:53:38 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id TAA18669; Thu, 10 Oct 1996 19:22:33 +0930 From: Michael Smith Message-Id: <199610100952.TAA18669@genesis.atrad.adelaide.edu.au> Subject: Re: 961006-SNAP comments To: pallenby@mikom.csir.co.za (Paul Allenby) Date: Thu, 10 Oct 1996 19:22:32 +0930 (CST) Cc: current@freebsd.org In-Reply-To: <199610100915.LAA17791@zibbi.mikom.csir.co.za> from "Paul Allenby" at Oct 10, 96 11:15:19 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Paul Allenby stands accused of saying: > > When I installed the 961006-SNAP and was in the config editor, > I tried to set the irq of the ed0 device to -1 as I was not > sure of the cards interrupt. It appears that only the values > 1...15 are accepted ( '?' didn't work either.) > Is this what was intended? If you mean the visual mode, yes. The 'ed' driver needs a legal IRQ value except in a few exceptional cases. Most drivers that know how to detect the IRQ of their hardware don't allow the value to be changed at all. > Paul -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Thu Oct 10 02:57:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA05585 for current-outgoing; Thu, 10 Oct 1996 02:57:29 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA05579 for ; Thu, 10 Oct 1996 02:57:27 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id CAA11986 for ; Thu, 10 Oct 1996 02:54:48 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id KAA20508; Thu, 10 Oct 1996 10:51:24 +0100 Date: Thu, 10 Oct 1996 10:51:23 +0100 (BST) From: Doug Rabson To: Tom Bartol cc: current@freebsd.org, Hidetoshi Shimokawa Subject: Re: NFS weirdness in -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Oct 1996, Tom Bartol wrote: > > Try this: > > At the same time as doing a: > > dd if=/dev/zero of=ick bs=8192 count=1024 > > to an NFS mounted directory in one xterm do an: > > ls > > from within the same NFS mounted directory in another xterm. What happens > is the ls hangs until the dd finishes. I don't think this the correct > behavior and it certainly is not the behavior I saw under 2.1.0R. Anybody > have a clue here? This sounds as if it might be related to a problem which came up yesterday. Hidetoshi Shimokawa was working on a patch which might fix this. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 734 3761 FAX: +44 171 734 6426 From owner-freebsd-current Thu Oct 10 05:26:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA16062 for current-outgoing; Thu, 10 Oct 1996 05:26:09 -0700 (PDT) Received: from mail12.digital.com (mail12.digital.com [192.208.46.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA16050 for ; Thu, 10 Oct 1996 05:26:06 -0700 (PDT) From: garyj@frt.dec.com Received: from cssmuc.frt.dec.com by mail12.digital.com (8.7.5/UNX 1.2/1.0/WV) id IAA30322; Thu, 10 Oct 1996 08:25:53 -0400 (EDT) Received: from localhost by cssmuc.frt.dec.com; (5.65v3.2/1.1.8.2/14Nov95-0232PM) id AA26207; Thu, 10 Oct 1996 14:25:40 +0200 Message-Id: <9610101225.AA26207@cssmuc.frt.dec.com> X-Mailer: exmh version 1.6.4 10/10/95 To: current@freebsd.org In-Reply-To: Message from John Polstra of Wed, 09 Oct 96 18:34:06 PDT. Reply-To: gjennejohn@frt.dec.com Subject: Re: ldconfig problem Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Oct 96 14:25:40 +0200 X-Mts: smtp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk jdp@polstra.com writes: [snip] > > gdb internal error: Memory corruption > > Quit (core dumped) > > > > This error is not affected by ld.so.hints change. It happens > > regardless of whether kaffe runs or not. So, I guess now we have to > > do some investigation on gdb.... ;_) > > Gdb does that on my -current system too. I last updated the system a > few days ago, on October 5. > > I copied the -current libc.so.3.0 onto my -stable system, and then > executed the -current gdb from there. So that was using the dynamic > linker and ld.so.hints from -stable, and the gdb, crt0.o and libc from > -current. It still got the same error. > > I have a feeling that this particular problem is unrelated to the > dynamic linker. It's just a feeling, though. I'm not sure yet. > I'm running a -current kernel from Oct 8 and have been using gdb a lot lately (I'm making mods to it) and have not seen one problem with it. Well, no problem which isn't related to my changes, anyway :) The user-land stuff is older than my kernel, though. That may explain the difference. --- Gary Jennejohn (work) gjennejohn@frt.dec.com (home) Gary.Jennejohn@munich.netsurf.de (play) gj@freebsd.org From owner-freebsd-current Thu Oct 10 05:28:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA16190 for current-outgoing; Thu, 10 Oct 1996 05:28:40 -0700 (PDT) Received: from GPO.iol.ie (GPO.iol.ie [194.125.2.239]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA16175 for ; Thu, 10 Oct 1996 05:28:33 -0700 (PDT) Received: from dialup-007.dublin.iol.ie (dialup-007.dublin.iol.ie [194.125.60.7]) by GPO.iol.ie Sendmail(v8.7.6) with SMTP id NAA26651 for ; Thu, 10 Oct 1996 13:28:05 +0100 (BST) From: derm@iol.ie (Dermot McNally) To: freebsd-current@freebsd.org Subject: Re: 961006-SNAP comments Date: Thu, 10 Oct 1996 12:26:43 GMT Organization: My House Message-ID: <325ee710.5836828@mail.iol.ie> References: In-Reply-To: X-Mailer: Forte Agent .99f/32.299 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Oct 1996 10:12:48 -0700 (PDT), you wrote: >FreeBSD's "all for one and one for all" boot floppy philosophy. So on >this note, if there could be a convenient and friendly way to inform = users >at boot time that they can, if need be, access a boot config editor by >hitting some key on the keyboard without cramming the editor down the >throats of others who may be confused by the editor or don't need to use >the editor then, just perhaps, everyone will still be happy and the "one >disk is all you need" constraint will be satisfied as well!!=20 Alternatively, why not launch the visual config program but have a prominent option highlighted by default along the lines of "Press Enter = to continue boot process". That way nobody forgets to go into config mode, everyone gets to find out it's there (a major help, IMHO) and nobody has trouble getting out of it and continuing with (hopefully) sensible defaults. Dermot -------------------------------------------------------------------- Dermot McNally derm@iol.ie http://www.iol.ie/~derm/ =46YI Consultants, specialising in the Internet & other networking Phone: +353-1-8252074 Mobile: +353-87-439998 "He wasn't just a train-spotter, but a train-talker, a far more dangerous condition" --Bill Bryson From owner-freebsd-current Thu Oct 10 05:43:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA16677 for current-outgoing; Thu, 10 Oct 1996 05:43:49 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA16672 for ; Thu, 10 Oct 1996 05:43:47 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id FAA14699; Thu, 10 Oct 1996 05:43:33 -0700 (PDT) To: derm@iol.ie (Dermot McNally) cc: freebsd-current@freebsd.org Subject: Re: 961006-SNAP comments In-reply-to: Your message of "Thu, 10 Oct 1996 12:26:43 GMT." <325ee710.5836828@mail.iol.ie> Date: Thu, 10 Oct 1996 05:43:33 -0700 Message-ID: <14696.844951413@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Alternatively, why not launch the visual config program but have a > prominent option highlighted by default along the lines of "Press Enter = > to > continue boot process". That way nobody forgets to go into config mode, There's an idea - a little two item menu, basically. I need to write quick-and-dirty "menus" for userconfig soon anyway, so perhaps this could fall out of that. Jordan From owner-freebsd-current Thu Oct 10 06:12:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA17980 for current-outgoing; Thu, 10 Oct 1996 06:12:36 -0700 (PDT) Received: from vanuata (vanuata.dcs.gla.ac.uk [130.209.240.50]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA17888 for ; Thu, 10 Oct 1996 06:11:07 -0700 (PDT) Message-Id: <199610101311.GAA17888@freefall.freebsd.org> Received: from solander by vanuata with SMTP (MMTA); Thu, 10 Oct 1996 14:07:01 +0100 To: Chuck Robey cc: current@FreeBSD.org Subject: Re: ok, look folks In-reply-to: Your message of "Wed, 09 Oct 1996 17:05:46 EDT." Date: Thu, 10 Oct 1996 14:06:46 +0100 From: Simon Marlow Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Chuck Robey writes: > [...] All I ever had to do was mail majordomo for the > list of users of the list they wanted off of, then find an address that > looked close, and show it to them. They then happily thank me, and > unsubscribe themselves. [...] It's not always that simple: for instance, my email address changed a few years ago from simonm@dcs.glasgow.ac.uk to simonm@dcs.gla.ac.uk, and it was impossible to send mail that appeared to come from the original address. Hence I was stuck on several mailing lists with no way to unsubscribe. > Telling them how to forge mail won't help anything. You're absolutely right, and my message was intended to be slightly tongue-in-cheek. Sorry for the confusion. Cheers, Simon -- Simon Marlow simonm@dcs.gla.ac.uk Research Assistant http://www.dcs.gla.ac.uk/~simonm/ finger for PGP public key From owner-freebsd-current Thu Oct 10 07:04:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA20218 for current-outgoing; Thu, 10 Oct 1996 07:04:12 -0700 (PDT) Received: from watson.grauel.com (watson.grauel.com [199.233.104.36]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA20212 for ; Thu, 10 Oct 1996 07:04:07 -0700 (PDT) Received: from sparcmill.grauel.com (sparcmill.grauel.com [199.233.104.34]) by watson.grauel.com (8.7.6/8.7.3) with SMTP id JAA08135; Thu, 10 Oct 1996 09:12:59 -0500 (EST) Received: by sparcmill.grauel.com (SMI-8.6/SMI-SVR4) id JAA00429; Thu, 10 Oct 1996 09:04:31 -0500 Date: Thu, 10 Oct 1996 09:04:31 -0500 Message-Id: <199610101404.JAA00429@sparcmill.grauel.com> From: Richard J Kuhns To: Michael Smith Cc: current@FreeBSD.org Subject: 'dead' binary stays 'dead'? In-Reply-To: <199610100143.LAA16437@genesis.atrad.adelaide.edu.au> References: <199610100143.LAA16437@genesis.atrad.adelaide.edu.au> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith writes: > > Howdy people; (particularly VM people) > > I have a system here that was behaving a little oddly. Overnight it's been > running some software that regularly exec's 'ls' to examine the contents > of a directory (maybe every 20 seconds or so).(1) > > At some point, 'ls' died with a sig11. Rerunning 'ls' caused an immediate > sig11 again. I tried to build another 'ls' so that I could look at the > cores, but no luck 8( > > If it's at all enlightening, I ran the newly-built 'ls', and it worked > (no surprises there); however now the 'old' ls works fine too. > > So I suspect that this has something to do with the 'sticky text' code not > being asked to explicitly forget about programs that have been killed by > signals. I'm aware that this is perhaps a difficult one to resolve > tidily, but I think my scenario may have been : > > - ls loads, a memory error of some sort occurs. > - ls runs, is killed due to memory error. > - ls is rerun, old text is used, is killed again courtesy of memory error. > > Obviously, machines with serious memory errors deserve to loose > infinitely, but this box doesn't fall into that category. It's > survived numerous 'make world' cycles faultlessly, and stands up all > day to the excessive pounding that the physics geeks here subject it > to. > > Comments? Refutations? Merciless laughter? > I'll comment. I just started a `make world' 2 days ago (10/8), which ran just fine (as usual) until it hit one of the gnu libraries during the `make all' phase, where cc1 died with a signal 11. I changed to that directory, did a `make clean', changed back to /usr/src, and restarted with a `make all'. It picked up where it left off, and worked ok for about 2 more minutes, after which it died again. I tried this cycle several more times, and got 3 more sig 11s, 1 sig 6, and one complaint from gcc/cc1 about a "bad INSN". I rebooted, and started the `make all' again -- it finished with no more problems. cc1 didn't _stay_ dead, but it certainly didn't live long after the first occurence of the problem. ASUS motherboard, 120 MH Pentium, 64MB RAM, Buslogic 946c, 2 Barracudas. The `make world' was done on an otherwise idle system, at the console (I wasn't even running X). For what it's worth... -- Richard Kuhns rjk@grauel.com PO Box 6249 Tel: (317)477-6000 \ 100 Sawmill Road x319 Lafayette, IN 47903 (800)489-4891 / From owner-freebsd-current Thu Oct 10 08:22:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA23992 for current-outgoing; Thu, 10 Oct 1996 08:22:37 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA23981; Thu, 10 Oct 1996 08:22:32 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA15718; Thu, 10 Oct 1996 09:21:53 -0600 (MDT) Date: Thu, 10 Oct 1996 09:21:53 -0600 (MDT) Message-Id: <199610101521.JAA15718@rocky.mt.sri.com> From: Nate Williams To: Jeffrey Hsu Cc: jdp@polstra.com, current@freefall.freebsd.org Subject: Fixed JDK kit In-Reply-To: <199610100603.XAA22199@freefall.freebsd.org> References: <199610100603.XAA22199@freefall.freebsd.org> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jeffrey Hsu writes: > > I hate to tell you but it didn't solve the problem. > > It does, however, solve my problem with the JDK coredumping w/ > -current. I think it should also fix Jake Hamby's reported > problem trying to run the JDK w/ -current. Thanks, John. Yes, thanks John and Jeffrey for doing this. I just started trying to figure out why java didn't work on a newer current system yesterday so I upgraded the bits to yesterday's code and it still didn't work. Based on this email I upgraded ld.so and everything started working again. Yay! Nate From owner-freebsd-current Thu Oct 10 08:43:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA25785 for current-outgoing; Thu, 10 Oct 1996 08:43:25 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA25780 for ; Thu, 10 Oct 1996 08:43:22 -0700 (PDT) Received: from localhost (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with SMTP id IAA13758 for ; Thu, 10 Oct 1996 08:44:24 -0700 Date: Thu, 10 Oct 1996 08:44:23 -0700 (PDT) From: Veggy Vinny To: current@FreeBSD.ORG Subject: make world fails in -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk a make world still fails in -current, just to confirm this... I deleted the entire /usr/src tree and resupped and this is what still happens: ===> gnu/usr.bin/cvs/lib ".depend", line 85: Need an operator Fatal errors encountered -- cannot continue *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. root@earth [8:39am][/usr/src] >> Vince From owner-freebsd-current Thu Oct 10 09:25:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA28941 for current-outgoing; Thu, 10 Oct 1996 09:25:00 -0700 (PDT) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA28931 for ; Thu, 10 Oct 1996 09:24:51 -0700 (PDT) Received: from grumble.grondar.za (mark@localhost.grondar.za [127.0.0.1]) by grumble.grondar.za (8.7.6/8.7.3) with ESMTP id SAA14242; Thu, 10 Oct 1996 18:24:05 +0200 (SAT) Message-Id: <199610101624.SAA14242@grumble.grondar.za> To: Veggy Vinny cc: current@FreeBSD.ORG Subject: Re: make world fails in -current Date: Thu, 10 Oct 1996 18:24:03 +0200 From: Mark Murray Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Veggy Vinny wrote: > a make world still fails in -current, just to confirm this... I > deleted the entire /usr/src tree and resupped and this is what still > happens: > > ===> gnu/usr.bin/cvs/lib > ".depend", line 85: Need an operator Delete the .depend file in your obj/.....cvs/lib dir, then make depend again. That file may be corrupt. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Thu Oct 10 09:25:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA29032 for current-outgoing; Thu, 10 Oct 1996 09:25:54 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA29026 for ; Thu, 10 Oct 1996 09:25:50 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA15921; Thu, 10 Oct 1996 10:25:15 -0600 (MDT) Date: Thu, 10 Oct 1996 10:25:15 -0600 (MDT) Message-Id: <199610101625.KAA15921@rocky.mt.sri.com> From: Nate Williams To: Veggy Vinny Cc: current@freebsd.org Subject: Re: make world fails in -current In-Reply-To: References: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Veggy Vinny writes: > a make world still fails in -current, just to confirm this... I > deleted the entire /usr/src tree and resupped and this is what still > happens: > > ===> gnu/usr.bin/cvs/lib > ".depend", line 85: Need an operator > Fatal errors encountered -- cannot continue > *** Error code 1 I suspect you have a left-over .depend file in the obj directory. Do a 'make cleandir' and try again. Nate From owner-freebsd-current Thu Oct 10 09:31:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA29464 for current-outgoing; Thu, 10 Oct 1996 09:31:21 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA29457 for ; Thu, 10 Oct 1996 09:31:15 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id SAA09138 for ; Thu, 10 Oct 1996 18:30:33 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id SAA10691 for freebsd-current@freebsd.org; Thu, 10 Oct 1996 18:30:25 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.0/keltia-uucp-2.9) id SAA25754; Thu, 10 Oct 1996 18:16:46 +0200 (MET DST) Message-Id: <199610101616.SAA25754@keltia.freenix.fr> Date: Thu, 10 Oct 1996 18:16:45 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@freebsd.org Subject: Re: 961006-SNAP comments In-Reply-To: <7186.844899046@verdi.nethelp.no>; from sthaug@nethelp.no on Oct 10, 1996 00:10:46 +0200 References: <199610091948.UAA04138@labinfo.iet.unipi.it> <7186.844899046@verdi.nethelp.no> X-Mailer: Mutt 0.47.09 Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-CURRENT ctm#2522 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to sthaug@nethelp.no: > 1. Symlink those few variable files that are left, e.g. /etc/ntp.drift > and /etc/ssh_random_seed into /var/run. You don't want ssh_random_seed to end up in /var/run as it would not be kept across reboots... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #23: Sun Sep 29 14:56:23 MET DST 1996 From owner-freebsd-current Thu Oct 10 09:38:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA00169 for current-outgoing; Thu, 10 Oct 1996 09:38:28 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA00161 for ; Thu, 10 Oct 1996 09:38:25 -0700 (PDT) Received: from localhost (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with SMTP id JAA17516; Thu, 10 Oct 1996 09:38:35 -0700 Date: Thu, 10 Oct 1996 09:38:34 -0700 (PDT) From: Veggy Vinny To: Mark Murray cc: current@FreeBSD.ORG Subject: Re: make world fails in -current In-Reply-To: <199610101624.SAA14242@grumble.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 10 Oct 1996, Mark Murray wrote: > Veggy Vinny wrote: > > a make world still fails in -current, just to confirm this... I > > deleted the entire /usr/src tree and resupped and this is what still > > happens: > > > > ===> gnu/usr.bin/cvs/lib > > ".depend", line 85: Need an operator > > Delete the .depend file in your obj/.....cvs/lib dir, then make depend > again. That file may be corrupt. The problem is there is no .depend file in my obj/ since this is what I tried: root@earth [8:39am][/usr/src] >> ls -agl /usr/obj/gnu/usr.bin/cvs/lib total 32 drwxrwxr-x 2 root bin 512 Oct 7 15:21 . drwxrwxr-x 9 root bin 512 May 13 19:29 .. -rwxrwxr-x 1 root bin 1161 May 13 23:36 error.o -rwxrwxr-x 1 root bin 5549 May 13 23:36 filesubr.o -rwxrwxr-x 1 root bin 2451 May 13 23:36 hash.o -rwxrwxr-x 1 root bin 1893 May 13 23:36 myndbm.o -rwxrwxr-x 1 root bin 4668 May 13 23:36 run.o -rwxrwxr-x 1 root bin 801 May 13 23:36 save-cwd.o -rwxrwxr-x 1 root bin 2310 May 13 23:36 subr.o -rwxrwxr-x 1 root bin 235 May 13 23:36 version.o root@earth [9:36am][/usr/src] >> Vince From owner-freebsd-current Thu Oct 10 09:42:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA00521 for current-outgoing; Thu, 10 Oct 1996 09:42:32 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA00508 for ; Thu, 10 Oct 1996 09:42:26 -0700 (PDT) Received: from localhost (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with SMTP id JAA17896; Thu, 10 Oct 1996 09:43:12 -0700 Date: Thu, 10 Oct 1996 09:43:11 -0700 (PDT) From: Veggy Vinny To: Nate Williams cc: current@freebsd.org Subject: Re: make world fails in -current In-Reply-To: <199610101625.KAA15921@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 10 Oct 1996, Nate Williams wrote: > Veggy Vinny writes: > > a make world still fails in -current, just to confirm this... I > > deleted the entire /usr/src tree and resupped and this is what still > > happens: > > > > ===> gnu/usr.bin/cvs/lib > > ".depend", line 85: Need an operator > > Fatal errors encountered -- cannot continue > > *** Error code 1 > > I suspect you have a left-over .depend file in the obj directory. Do a > 'make cleandir' and try again. Actually, I thought it was that yesterday but just to be sure... root@earth [9:40am][/usr/src/gnu/usr.bin/cvs] >> make cleandir ===> lib ".depend", line 85: Need an operator Fatal errors encountered -- cannot continue *** Error code 1 Stop. root@earth [9:40am][/usr/src/gnu/usr.bin/cvs] >> ls -agl /usr/obj/gnu/usr.bin/cvs/lib total 32 drwxrwxr-x 2 root bin 512 Oct 7 15:21 . drwxrwxr-x 9 root bin 512 May 13 19:29 .. -rwxrwxr-x 1 root bin 1161 May 13 23:36 error.o -rwxrwxr-x 1 root bin 5549 May 13 23:36 filesubr.o -rwxrwxr-x 1 root bin 2451 May 13 23:36 hash.o -rwxrwxr-x 1 root bin 1893 May 13 23:36 myndbm.o -rwxrwxr-x 1 root bin 4668 May 13 23:36 run.o -rwxrwxr-x 1 root bin 801 May 13 23:36 save-cwd.o -rwxrwxr-x 1 root bin 2310 May 13 23:36 subr.o -rwxrwxr-x 1 root bin 235 May 13 23:36 version.o root@earth [9:41am][/usr/src/gnu/usr.bin/cvs] >> Vince GaiaNet Corporation - Unix Networking Operations From owner-freebsd-current Thu Oct 10 09:54:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA01643 for current-outgoing; Thu, 10 Oct 1996 09:54:50 -0700 (PDT) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA01636 for ; Thu, 10 Oct 1996 09:54:48 -0700 (PDT) Received: from pauling.salk.edu (pauling [198.202.70.108]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id JAA06616; Thu, 10 Oct 1996 09:54:41 -0700 (PDT) Date: Thu, 10 Oct 1996 09:54:39 -0700 (PDT) From: Tom Bartol To: Doug Rabson cc: current@FreeBSD.ORG, Hidetoshi Shimokawa Subject: Re: NFS weirdness in -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 10 Oct 1996, Doug Rabson wrote: > On Wed, 9 Oct 1996, Tom Bartol wrote: > > > > > Try this: > > > > At the same time as doing a: > > > > dd if=/dev/zero of=ick bs=8192 count=1024 > > > > to an NFS mounted directory in one xterm do an: > > > > ls > > > > from within the same NFS mounted directory in another xterm. What happens > > is the ls hangs until the dd finishes. I don't think this the correct > > behavior and it certainly is not the behavior I saw under 2.1.0R. Anybody > > have a clue here? > > This sounds as if it might be related to a problem which came up > yesterday. Hidetoshi Shimokawa was working on a patch which might fix > this. > > -- > Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com > Phone: +44 171 734 3761 > FAX: +44 171 734 6426 Yes, it does sound like that problem now that you point it out. Hidetoshi, is there anything I can do to help out? Thanks, Tom From owner-freebsd-current Thu Oct 10 10:00:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA02092 for current-outgoing; Thu, 10 Oct 1996 10:00:18 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA02084 for ; Thu, 10 Oct 1996 10:00:16 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA16119; Thu, 10 Oct 1996 10:59:59 -0600 (MDT) Date: Thu, 10 Oct 1996 10:59:59 -0600 (MDT) Message-Id: <199610101659.KAA16119@rocky.mt.sri.com> From: Nate Williams To: Veggy Vinny Cc: Nate Williams , current@freebsd.org Subject: Re: make world fails in -current In-Reply-To: References: <199610101625.KAA15921@rocky.mt.sri.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Veggy Vinny writes: > > > a make world still fails in -current, just to confirm this... I > > > deleted the entire /usr/src tree and resupped and this is what still > > > happens: > > > > > > ===> gnu/usr.bin/cvs/lib > > > ".depend", line 85: Need an operator > > > Fatal errors encountered -- cannot continue > > > *** Error code 1 > > > > I suspect you have a left-over .depend file in the obj directory. Do a > > 'make cleandir' and try again. > > Actually, I thought it was that yesterday but just to be sure... > > root@earth [9:40am][/usr/src/gnu/usr.bin/cvs] >> make cleandir > ===> lib > ".depend", line 85: Need an operator > Fatal errors encountered -- cannot continue > *** Error code 1 # cd /usr/obj; # rm -rf * # find /usr/src -name obj -print | xargs rm -rf Nate From owner-freebsd-current Thu Oct 10 10:02:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA02319 for current-outgoing; Thu, 10 Oct 1996 10:02:12 -0700 (PDT) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA02312 for ; Thu, 10 Oct 1996 10:02:10 -0700 (PDT) Received: from pauling.salk.edu (pauling [198.202.70.108]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id KAA06688; Thu, 10 Oct 1996 10:01:28 -0700 (PDT) Date: Thu, 10 Oct 1996 10:01:26 -0700 (PDT) From: Tom Bartol To: Dermot McNally cc: freebsd-current@FreeBSD.org Subject: Re: 961006-SNAP comments In-Reply-To: <325ee710.5836828@mail.iol.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 10 Oct 1996, Dermot McNally wrote: > > Alternatively, why not launch the visual config program but have a > prominent option highlighted by default along the lines of "Press Enter to > continue boot process". That way nobody forgets to go into config mode, > everyone gets to find out it's there (a major help, IMHO) and nobody has > trouble getting out of it and continuing with (hopefully) sensible > defaults. > Yes! That's the ticket! Tom From owner-freebsd-current Thu Oct 10 10:11:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA03075 for current-outgoing; Thu, 10 Oct 1996 10:11:02 -0700 (PDT) Received: from uno.sat.t.u-tokyo.ac.jp (uno.sat.t.u-tokyo.ac.jp [133.11.70.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA03068 for ; Thu, 10 Oct 1996 10:10:57 -0700 (PDT) Received: by uno.sat.t.u-tokyo.ac.jp (8.7.3+2.6Wbeta5/8.7.3) with ESMTP id CAA09766; Fri, 11 Oct 1996 02:04:47 +0900 (JST) To: bartol@salk.edu Cc: dfr@render.com, current@FreeBSD.ORG Subject: Re: NFS weirdness in -current In-Reply-To: Your message of "Thu, 10 Oct 1996 09:54:39 -0700 (PDT)" References: X-Mailer: Mew version 1.06 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 11 Oct 1996 02:04:47 +0900 Message-ID: <9764.844967087@sat.t.u-tokyo.ac.jp> From: Hidetoshi Shimokawa Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk bartol> Yes, it does sound like that problem now that you point it out. bartol> bartol> Hidetoshi, is there anything I can do to help out? I already made a patch and send it to freebsd-lite2 list. (I guess you can find it by mailing list archive search, keyword is "Delayed write patch".) Doug will commit it to -current tomorrow(it may depends on time zone :-). If you cannot wait it, I will send you the patch. Please try the patch. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: finger -l simokawa@sat.t.u-tokyo.ac.jp From owner-freebsd-current Thu Oct 10 10:45:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA05464 for current-outgoing; Thu, 10 Oct 1996 10:45:16 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA05454; Thu, 10 Oct 1996 10:45:14 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA20319; Thu, 10 Oct 1996 10:39:46 -0700 From: Terry Lambert Message-Id: <199610101739.KAA20319@phaeton.artisoft.com> Subject: Re: .depend To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Thu, 10 Oct 1996 10:39:46 -0700 (MST) Cc: terry@lambert.org, rkw@dataplex.net, wosch@freebsd.org, steve@freefall.freebsd.org, current@freebsd.org In-Reply-To: <199610100144.LAA16453@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Oct 10, 96 11:14:29 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > IMHO, this entire discussion results from a fundamental error in the > > > methodology of building multiple versions from a single set of sources. > > > Rather than "kluge" something else into "make" so you can "get by", we > > > should fix the methodology. > > > > What happens when I want to build several different machine architectures > > from the same NFS mounted sources instead of placing 3 times the SUP > > load on one of the severs to get thrre times the trees on three times > > the local diskk space used? > > .depend is in the object directory. Unless you're a total loser, you > _will_ have seperate object directories, right? That ".depends". If I not a total loser doing a port to a new architecture, I won't have local disk drivers and I'll be running over NFS to a remote object directory. Typically, I find I have just enough space on a given build machine for the foreign object directory -- in the local object directory (funny how that works out). So for supporting multiple machine architectures, especially for build and install testing on a 100M SCSI ZIP drive that you cart around from box to box, expect me to use the same object directory on my build host. 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-current Thu Oct 10 10:48:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA05676 for current-outgoing; Thu, 10 Oct 1996 10:48:20 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA05667 for ; Thu, 10 Oct 1996 10:48:17 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id KAA05145; Thu, 10 Oct 1996 10:48:06 -0700 (PDT) Message-Id: <199610101748.KAA05145@austin.polstra.com> To: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= cc: current@freefall.freebsd.org In-reply-to: Your message of "Thu, 10 Oct 1996 14:45:59 +0900." <199610100545.OAA09234@bourbon.sfc.wide.ad.jp> Date: Thu, 10 Oct 1996 10:48:06 -0700 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > jdp> This could also (hopefully) be the cause of the core dumps > jdp> that Masafumi reported from running kaffe. > > I hate to tell you but it didn't solve the problem. The > situation seems to me exactly the same as before. Yes, I looked at kaffe, and it doesn't do the kind of thing that exposed the bug that Jeffrey discovered. I looked at the ld.so.hints file you sent me, and it looks OK to me. I am still interested in helping to solve this problem, but it seems doubtful that I can make it fail here on my machine. If you have time, please do the following: * Build a version of kaffe with debugging ("-g") information. * Put your system into the failing state, and run kaffe under the debugger. (Hopefully, gdb will work well enough to get the information I need.) When kaffe dies, print out a stack backtrace (command "where"), and also the registers ("info registers"). * Try to determine whether the program died inside the dynamic linker. Look at the program counter value (register eip). If it is greater than 0x08000000, but less than the address of the first shared library as reported by "ldd kaffe", then it is probably in the dynamic linker. If it is not in the dynamic linker, then you might as well skip the remaining steps, because they won't be useful. * If the program died in the dynamic linker, then I will need a sorted namelist from your installed version of the dynamic linker. Of course, your installed version is stripped, so you can't get a namelist from it. :-( But hopefully, the unstripped version still exists on your system, in "/usr/obj/usr/src/gnu/usr.bin/ld/rtld/ld.so". Run "nm -an" on that file, and send me the output. * I need one more piece of information, so that I can figure out where in your address space the dynamic linker was loaded. Start up the debugger on kaffe again, but before you run the program, set breakpoints at "dlopen" and "dlsym". ("b dlopen", "b dlsym"). Now run the program, and hope that it hits a breakpoint before it dies. Give the "si" command repeatedly, until the address jumps to something greater than 0x08000000. (It should require only a few repetitions.) Send me the address. If you are able to get all that information, it should help a lot to diagnose the problem. Thanks, 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-current Thu Oct 10 12:01:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA09268 for current-outgoing; Thu, 10 Oct 1996 12:01:23 -0700 (PDT) Received: from mail.tky007.tth.expo96.ad.jp (root@tky007.tth.expo96.ad.jp [133.246.32.58]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA09263 for ; Thu, 10 Oct 1996 12:01:19 -0700 (PDT) Received: from tky007.tth.expo96.ad.jp (masafumi@localhost [127.0.0.1]) by mail.tky007.tth.expo96.ad.jp (8.7.6/3.4W4-SMTP) with ESMTP id DAA27224; Fri, 11 Oct 1996 03:59:47 +0900 (JST) Message-Id: <199610101859.DAA27224@mail.tky007.tth.expo96.ad.jp> To: jdp@polstra.com Cc: max@wide.ad.jp, current@freefall.freebsd.org From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= In-Reply-To: Your message of "Thu, 10 Oct 1996 10:48:06 -0700" References: <199610101748.KAA05145@austin.polstra.com> X-Mailer: Mew version 1.06 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 11 Oct 1996 03:59:45 +0900 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, Thanks John for precise description. However, it seems gdb is doing no good. ---------------------------------------------------------------------- gdb /usr/local/bin/kaffe GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.13 (i386-unknown-freebsd), Copyright 1994 Free Software Foundation, Inc... (gdb) run Starting program: /usr/local/bin/kaffe Program terminated with signal SIGBUS, Bus error. The program no longer exists. You can't do that without a process to debug (gdb) info registers The program has no registers now. (gdb) where No stack. (gdb) quit ---------------------------------------------------------------------- If I'm doing anything wrong, please let me know. (I use gdb only occasionally.) Although I have no idea if these would give you any interesting info, I also tried some other things. 1. Set a breakpoint at main() and ran the program: It died even before entering main(). 2. Ktrace'd the execution: I don't know which peace of info can be useful, but I found that the program dies after mmap call which occurs several steps after reading and mmapping libc.so.3.0. Please let me know if there is anything I can do to solve this problem. (I sure wish I were knowledgeable enough to hack things away myself.) Max From owner-freebsd-current Thu Oct 10 12:33:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA10641 for current-outgoing; Thu, 10 Oct 1996 12:33:45 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA10635 for ; Thu, 10 Oct 1996 12:33:43 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id MAA05744; Thu, 10 Oct 1996 12:33:16 -0700 (PDT) Message-Id: <199610101933.MAA05744@austin.polstra.com> To: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= cc: current@freefall.freebsd.org In-reply-to: Your message of "Fri, 11 Oct 1996 03:59:45 +0900." <199610101859.DAA27224@mail.tky007.tth.expo96.ad.jp> Date: Thu, 10 Oct 1996 12:33:16 -0700 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Thanks John for precise description. However, it seems gdb is > doing no good. Oh joy. :-( > Please let me know if there is anything I can do to solve this > problem. Thanks. If you can help me a little, I'll try to reproduce the problem here. I assume I need to install the "kaffe" and "jdk" ports. Beyond that, could you send me a test case and a description of exactly what I have to do to run it? Also, please send me the output of "printenv" on your system. Maybe if I use your ld.so.hints file (eek!) I can get it to fail here. 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-current Thu Oct 10 12:40:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA11067 for current-outgoing; Thu, 10 Oct 1996 12:40:28 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA11051; Thu, 10 Oct 1996 12:40:24 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.0/8.8.Beta.3) with SMTP id OAA18382; Thu, 10 Oct 1996 14:40:23 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.15) id ; Thu, 10 Oct 96 14:40 CDT Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.Beta.6/8.8.Beta.3) id OAA10151; Thu, 10 Oct 1996 14:40:22 -0500 (CDT) From: Karl Denninger Message-Id: <199610101940.OAA10151@Jupiter.Mcs.Net> Subject: Crash in -current (from the current SNAP) To: hackers@freebsd.org, current@freebsd.org Date: Thu, 10 Oct 1996 14:40:21 -0500 (CDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk #0 boot (howto=260) at ../../kern/kern_shutdown.c:237 #1 0xf0113bf2 in panic (fmt=0xf01bc6af "page fault") at ../../kern/kern_shutdown.c:361 #2 0xf01bd20a in trap_fatal (frame=0xf01e3d0c) at ../../i386/i386/trap.c:741 #3 0xf01bccf8 in trap_pfault (frame=0xf01e3d0c, usermode=0) at ../../i386/i386/trap.c:652 #4 0xf01bc9df in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = -216777728, tf_ebp = -266453672, tf_isp = -266453708, tf_ebx = -215471872, tf_edx = 0, tf_ecx = -218725632, tf_eax = -216503296, tf_trapno = 12, tf_err = 0, tf_eip = -267181782, tf_cs = 8, tf_eflags = 66118, tf_esp = 0, tf_ss = -215471872}) at ../../i386/i386/trap.c:311 #5 0xf01b2051 in calltrap () #6 0xf0198fc8 in ffs_sync (mp=0xf2f9bc00, waitfor=2, cred=0xf1f5f880, p=0xf0208e74) at ../../ufs/ffs/ffs_vfsops.c:817 #7 0xf01335cb in sync (p=0xf0208e74, uap=0x0, retval=0x0) at ../../kern/vfs_syscalls.c:357 #8 0xf011380d in boot (howto=256) at ../../kern/kern_shutdown.c:181 #9 0xf0113bf2 in panic (fmt=0xf01bc6af "page fault") at ../../kern/kern_shutdown.c:361 #10 0xf01bd20a in trap_fatal (frame=0xf01e3e90) at ../../i386/i386/trap.c:741 #11 0xf01bccf8 in trap_pfault (frame=0xf01e3e90, usermode=0) at ../../i386/i386/trap.c:652 ---Type to continue, or q to quit--- #12 0xf01bc9df in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -227006164, tf_esi = -215122688, tf_ebp = -266453184, tf_isp = -266453320, tf_ebx = -211072256, tf_edx = 1073610751, tf_ecx = 0, tf_eax = 201893069, tf_trapno = 12, tf_err = 2, tf_eip = -267093275, tf_cs = 8, tf_eflags = 66050, tf_esp = 44, tf_ss = 20}) at ../../i386/i386/trap.c:311 #13 0xf01b2051 in calltrap () #14 0xf01447b2 in ip_input (m=0xf2782900) at ../../netinet/ip_input.c:508 #15 0xf0144828 in ipintr () at ../../netinet/ip_input.c:529 #16 0xf01b336d in swi_net_next () #17 0xf0125827 in pffasttimo (arg=0x0) at ../../kern/uipc_domain.c:234 #18 0xf010afd4 in softclock () at ../../kern/kern_clock.c:665 Oh oh.... ip_input, at line 529, is this: /* * Switch out to protocol's input routine. */ ipstat.ips_delivered++; >>>> (*inetsw[ip_protox[ip->ip_p]].pr_input)(m, hlen); return; What's going on here? These are somewhat frequent. The address being passed to ip_input looks ok (it appears to be in kernel space).... Given that it is a timeout call that is generating this, why do I think this has something to do with the anti-syn patches? Did anyone check the spl() levels in those changes to make sure that the structures aren't getting mangled during processing? -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-current Thu Oct 10 12:56:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA11795 for current-outgoing; Thu, 10 Oct 1996 12:56:01 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA11772 for ; Thu, 10 Oct 1996 12:55:55 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA16866; Thu, 10 Oct 1996 13:55:07 -0600 (MDT) Date: Thu, 10 Oct 1996 13:55:07 -0600 (MDT) Message-Id: <199610101955.NAA16866@rocky.mt.sri.com> From: Nate Williams To: John Polstra Cc: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= , current@freefall.freebsd.org In-Reply-To: <199610101933.MAA05744@austin.polstra.com> References: <199610101859.DAA27224@mail.tky007.tth.expo96.ad.jp> <199610101933.MAA05744@austin.polstra.com> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Thanks John for precise description. However, it seems gdb is > > doing no good. > > Oh joy. :-( I *suspect* a screwed up LD_LIBRARY_PATH. > > Please let me know if there is anything I can do to solve this > > problem. > > Thanks. If you can help me a little, I'll try to reproduce the > problem here. I assume I need to install the "kaffe" and "jdk" > ports. I just did because I could, and it works fine for me. I was getting weird errors when I had a screwed up CLASSPATH and/or LD_LIBRARY_PATH, so I suspect those. Nate From owner-freebsd-current Thu Oct 10 13:13:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA12728 for current-outgoing; Thu, 10 Oct 1996 13:13:44 -0700 (PDT) Received: from eddie.cis.uoguelph.ca (eddie.cis.uoguelph.ca [131.104.48.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA12711; Thu, 10 Oct 1996 13:13:27 -0700 (PDT) Received: (from josh@localhost) by eddie.cis.uoguelph.ca (8.7.6/8.7.3) id QAA06291; Thu, 10 Oct 1996 16:11:39 -0400 (EDT) From: Josh Tiefenbach Message-Id: <199610102011.QAA06291@eddie.cis.uoguelph.ca> Subject: Problems with bootparamd To: current@freebsd.org Date: Thu, 10 Oct 1996 16:11:39 -0400 (EDT) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I've been having some problems recently trying to get a Sun 3/50 booting off of a -current machine. The Sun was previously booting off of a Linux box fine, and since I'm recycling the config files, I'm led to believe that it may be a -current problem. Symptoms: rarpd and tftpd seem to be working fine. The sun finds its kernel, dl's it, starts reporting the devices found, and then hangs briefly after reporting the bw2 card. then the following message pops up: No bootparam server responding, still trying whoami: pmap_rmtcall status 0x5 which kinda doesnt make sense, cause it found the bootparam server earlier (from server logs) Oct 10 15:58:29 eddie bootparamd: whoami got question for 131.104.48.118 Oct 10 15:58:29 eddie bootparamd: This is host carlsberg.cis.uoguelph.ca Oct 10 15:58:29 eddie bootparamd: Returning carlsberg 131.104.48.34 Oct 10 15:58:30 eddie bootparamd: getfile got question for "carlsberg" and file "root" Oct 10 15:58:30 eddie bootparamd: returning server:eddie.cis.uoguelph.ca path:/usr/export/Xkernel.sun3 address: 131.104.48.34 I'm using the sun kernel/bootfile from the Linux-XKernel v2.0 package. Server: FreeBSD eddie.cis.uoguelph.ca 2.2-CURRENT FreeBSD 2.2-CURRENT #0: Sat Sep 21 11:15:10 EDT 1996 josh@eddie.cis.uoguelph.ca:/usr/src-current/sys/compile/EDDIE i386 Also, the booting process seems to generate: Oct 10 15:58:43 eddie routed[47]: punt RTM_ADD without gateway A grep of the mailing lists seems to indicate that other people seem to be having this problem, but I was unable to find a solution in there. Any suggestions? josh -- Josh Tiefenbach | "I am a yapping dog with mean little teeth. President, | I am as often as wrong as you, as often as Society for Computing | co-opted as you, as often sophomoric as you. and Information Science. | But I maintain. As do you." University of Guelph | -- Harlan Ellison mailto:josh@eddie.cis.uoguelph.ca Web: http://eddie.cis.uoguelph.ca/~josh From owner-freebsd-current Thu Oct 10 13:14:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA12803 for current-outgoing; Thu, 10 Oct 1996 13:14:54 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA12794 for ; Thu, 10 Oct 1996 13:14:48 -0700 (PDT) Received: from localhost (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with SMTP id NAA09352; Thu, 10 Oct 1996 13:15:34 -0700 Date: Thu, 10 Oct 1996 13:15:32 -0700 (PDT) From: Veggy Vinny To: Nate Williams cc: current@freebsd.org Subject: Re: make world fails in -current In-Reply-To: <199610101659.KAA16119@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 10 Oct 1996, Nate Williams wrote: > > root@earth [9:40am][/usr/src/gnu/usr.bin/cvs] >> make cleandir > > ===> lib > > ".depend", line 85: Need an operator > > Fatal errors encountered -- cannot continue > > *** Error code 1 > > # cd /usr/obj; > # rm -rf * > # find /usr/src -name obj -print | xargs rm -rf Thanks, this seems to have fixed it... =) Cheers, -Vince- GaiaNet Corporation Unix Networking Operations From owner-freebsd-current Thu Oct 10 13:29:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA13605 for current-outgoing; Thu, 10 Oct 1996 13:29:36 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA13595 for ; Thu, 10 Oct 1996 13:29:29 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.5/8.7.3) with SMTP id NAA01230; Thu, 10 Oct 1996 13:24:54 -0700 (PDT) Message-ID: <325D5B1D.41C67EA6@whistle.com> Date: Thu, 10 Oct 1996 13:22:53 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Bruce Evans CC: luigi@labinfo.iet.unipi.it, sthaug@nethelp.no, danj@netcom.com, freebsd-current@FreeBSD.org, henrich@crh.cl.msu.edu Subject: Re: 961006-SNAP comments References: <199610100637.QAA08305@godzilla.zeta.org.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Bruce Evans wrote: > > >2. Use DEVFS for the devices. > > > >Any reason why this wouldn't work? > > Yes, devfs is too broken to use. E.g., anyone can chmod and chown > anything in it. > > Bruce first I've heard of this.. I'll fix it asap. people keep saying it's broken but don't tell me about it.. From owner-freebsd-current Thu Oct 10 13:43:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA14446 for current-outgoing; Thu, 10 Oct 1996 13:43:58 -0700 (PDT) Received: from noc.msc.edu (noc.msc.edu [137.66.12.254]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA14438 for ; Thu, 10 Oct 1996 13:43:53 -0700 (PDT) Received: from uc.msc.edu by noc.msc.edu (5.65/MSC/v3.0.1(920324)) id AA19848; Thu, 10 Oct 96 15:43:01 -0500 Received: from fergus-17.dialup.prtel.com by uc.msc.edu (5.65/MSC/v3.0z(901212)) id AA02456; Thu, 10 Oct 96 15:42:59 -0500 Received: (from alk@localhost) by compound.Think.COM (8.7.6/8.7.3) id PAA24554; Thu, 10 Oct 1996 15:42:56 -0500 (CDT) Date: Thu, 10 Oct 1996 15:42:56 -0500 (CDT) From: Tony Kimball Message-Id: <199610102042.PAA24554@compound.Think.COM> To: current@freebsd.org Subject: muldi3.c Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I wonder about this redundancy. ; diff ./lib/libc/quad/muldi3.c ./sys/libkern/muldi3.c diff ./lib/libc/quad/muldi3.c ./sys/libkern/muldi3.c 35a36,37 > * > * $Id: muldi3.c,v 1.3 1995/05/30 08:06:41 rgrimes Exp $ 37,40d38 < < #if defined(LIBC_SCCS) && !defined(lint) < static char sccsid[] = "@(#)muldi3.c 8.1 (Berkeley) 6/4/93"; < #endif /* LIBC_SCCS and not lint */ From owner-freebsd-current Thu Oct 10 14:13:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA15890 for current-outgoing; Thu, 10 Oct 1996 14:13:08 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA15868; Thu, 10 Oct 1996 14:12:56 -0700 (PDT) Received: from alpha.Xerox.COM by mail.crl.com with SMTP id AA24434 (5.65c/IDA-1.5); Thu, 10 Oct 1996 14:13:16 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15993(3)>; Thu, 10 Oct 1996 14:09:40 PDT Received: by crevenia.parc.xerox.com id <177476>; Thu, 10 Oct 1996 14:09:32 -0700 From: Bill Fenner To: current@freebsd.org, hackers@freebsd.org, karl@mcs.net Subject: Re: Crash in -current (from the current SNAP) Message-Id: <96Oct10.140932pdt.177476@crevenia.parc.xerox.com> Date: Thu, 10 Oct 1996 14:09:31 PDT Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>> (*inetsw[ip_protox[ip->ip_p]].pr_input)(m, hlen); >What's going on here? Either ip_protox[ip->ip_p] is out of range (should be 1..7 or 8 depending on if what options you have in your kernel), or inetsw[ip_protox[ip->ip_p]].pr_input is. >Given that it is a timeout call that is generating this, why do I think >this has something to do with the anti-syn patches? Nope, this is a software interrupt causing IP to service its input queue. Bill From owner-freebsd-current Thu Oct 10 14:18:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA16293 for current-outgoing; Thu, 10 Oct 1996 14:18:47 -0700 (PDT) Received: from Octopussy (Octopussy.MI.Uni-Koeln.DE [134.95.212.20]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA16275; Thu, 10 Oct 1996 14:18:40 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-48.slip.Uni-Koeln.DE) by Octopussy with SMTP id AA09409 (5.67b/IDA-1.5); Thu, 10 Oct 1996 22:42:15 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.6/8.6.9) id WAA25353; Thu, 10 Oct 1996 22:41:30 +0200 (MET DST) Date: Thu, 10 Oct 1996 22:41:30 +0200 (MET DST) Message-Id: <199610102041.WAA25353@x14.mi.uni-koeln.de> From: Stefan Esser To: Luigi Rizzo Cc: freebsd-current@freebsd.org, jkh@freebsd.org Subject: Re: More 961006-SNAP comments In-Reply-To: <199610090402.FAA02243@labinfo.iet.unipi.it> References: <199610090402.FAA02243@labinfo.iet.unipi.it> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Luigi Rizzo writes: > A few more comments on the latest snap. > > 3. there is a "locate.pl" file in /sys/pci. leftover from something ? No. But just only useful in that directory. If you call it with some hex value, it will tell you how many DWORDs after some label this offset was in the NCR SCRIPTS program. /sys/pci > ./locate.pl 8c8 87c: msg_wdtr 8c8: msg_wdtr + 19 Just to save me some line counting ... :) (It has to be available on the system where the problem occured, since my sources might be different already. And since it needs to read "ncr.c" anyway, I decided to have it in the source directory. Its only a few lines of Perl code, anyway ...) Regards, STefan From owner-freebsd-current Thu Oct 10 14:24:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA16888 for current-outgoing; Thu, 10 Oct 1996 14:24:52 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA16857; Thu, 10 Oct 1996 14:24:27 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id OAA27457; Thu, 10 Oct 1996 14:24:00 -0700 (PDT) Message-Id: <199610102124.OAA27457@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Bill Fenner cc: current@freebsd.org, hackers@freebsd.org, karl@mcs.net Subject: Re: Crash in -current (from the current SNAP) In-reply-to: Your message of "Thu, 10 Oct 1996 14:09:31 PDT." <96Oct10.140932pdt.177476@crevenia.parc.xerox.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 10 Oct 1996 14:24:00 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> (*inetsw[ip_protox[ip->ip_p]].pr_input)(m, hlen); > >>What's going on here? > >Either ip_protox[ip->ip_p] is out of range (should be 1..7 or 8 >depending on if what options you have in your kernel), or >inetsw[ip_protox[ip->ip_p]].pr_input is. gdb isn't decoding the stack correctly. The real failure is inside the pr_input routine (probably tcp_input) somewhere. >>Given that it is a timeout call that is generating this, why do I think >>this has something to do with the anti-syn patches? > >Nope, this is a software interrupt causing IP to service its input >queue. ...which if the input queue contains SYNs could cause the queue to overrun. Right? Or am I missing something? -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Thu Oct 10 14:34:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA17533 for current-outgoing; Thu, 10 Oct 1996 14:34:09 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA17484; Thu, 10 Oct 1996 14:32:32 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.0/8.8.Beta.3) with SMTP id QAA24074; Thu, 10 Oct 1996 16:31:55 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.15) id ; Thu, 10 Oct 96 16:31 CDT Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.Beta.6/8.8.Beta.3) id QAA13145; Thu, 10 Oct 1996 16:31:51 -0500 (CDT) From: Karl Denninger Message-Id: <199610102131.QAA13145@Jupiter.Mcs.Net> Subject: Re: Crash in -current (from the current SNAP) To: fenner@parc.xerox.com (Bill Fenner) Date: Thu, 10 Oct 1996 16:31:51 -0500 (CDT) Cc: current@freebsd.org, hackers@freebsd.org, karl@Mcs.Net In-Reply-To: <96Oct10.140932pdt.177476@crevenia.parc.xerox.com> from "Bill Fenner" at Oct 10, 96 02:09:31 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > >>>> (*inetsw[ip_protox[ip->ip_p]].pr_input)(m, hlen); > > >What's going on here? > > Either ip_protox[ip->ip_p] is out of range (should be 1..7 or 8 > depending on if what options you have in your kernel), or > inetsw[ip_protox[ip->ip_p]].pr_input is. > > >Given that it is a timeout call that is generating this, why do I think > >this has something to do with the anti-syn patches? > > Nope, this is a software interrupt causing IP to service its input > queue. > > Bill > (kgdb) (kgdb) select-frame 14 (kgdb) print ip_protox[ip->ip_p] $1 = 2 '\002' That's "INET", if I'm reading the headers correctly. (kgdb) print inetsw[ip_protox[ip->ip_p]].pr_input $2 = (void (*)()) 0xf01477ec Hmmmm.... The address looks to be valid as well... -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-current Thu Oct 10 14:39:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA17886 for current-outgoing; Thu, 10 Oct 1996 14:39:44 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA17865; Thu, 10 Oct 1996 14:39:37 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.0/8.8.Beta.3) with SMTP id QAA24682; Thu, 10 Oct 1996 16:39:30 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.15) id ; Thu, 10 Oct 96 16:39 CDT Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.Beta.6/8.8.Beta.3) id QAA13465; Thu, 10 Oct 1996 16:39:27 -0500 (CDT) From: Karl Denninger Message-Id: <199610102139.QAA13465@Jupiter.Mcs.Net> Subject: Re: Crash in -current (from the current SNAP) To: dg@root.com Date: Thu, 10 Oct 1996 16:39:27 -0500 (CDT) Cc: fenner@parc.xerox.com, current@freebsd.org, hackers@freebsd.org, karl@Mcs.Net In-Reply-To: <199610102124.OAA27457@root.com> from "David Greenman" at Oct 10, 96 02:24:00 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >>>>> (*inetsw[ip_protox[ip->ip_p]].pr_input)(m, hlen); > > > >>What's going on here? > > > >Either ip_protox[ip->ip_p] is out of range (should be 1..7 or 8 > >depending on if what options you have in your kernel), or > >inetsw[ip_protox[ip->ip_p]].pr_input is. > > gdb isn't decoding the stack correctly. The real failure is inside the > pr_input routine (probably tcp_input) somewhere. Yuck. Without a failure address this is going to be a BITCH to find. The decode on the parameters passed (the switch path taken) look valid. This leads me to believe that something's trashed, perhaps in the PCBs, and is leading to a bad indirect reference. > >>Given that it is a timeout call that is generating this, why do I think > >>this has something to do with the anti-syn patches? > > > >Nope, this is a software interrupt causing IP to service its input > >queue. > > ...which if the input queue contains SYNs could cause the queue to overrun. > Right? Or am I missing something? I don't think you are. This started when the SYN attack code was added to the system. Its fairly consistent and shows up with a frequency of every few hours. I have good core dumps here if anyone wants to track this down. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-current Thu Oct 10 14:41:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA18167 for current-outgoing; Thu, 10 Oct 1996 14:41:27 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA18157; Thu, 10 Oct 1996 14:41:11 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15484(5)>; Thu, 10 Oct 1996 14:40:34 PDT Received: by crevenia.parc.xerox.com id <177476>; Thu, 10 Oct 1996 14:40:23 -0700 From: Bill Fenner To: fenner@parc.xerox.com, karl@mcs.net Subject: Re: Crash in -current (from the current SNAP) Cc: current@freebsd.org, hackers@freebsd.org Message-Id: <96Oct10.144023pdt.177476@crevenia.parc.xerox.com> Date: Thu, 10 Oct 1996 14:40:12 PDT Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >(kgdb) >(kgdb) select-frame 14 >(kgdb) print ip_protox[ip->ip_p] >$1 = 2 '\002' > >That's "INET", if I'm reading the headers correctly. No, it's "TCP" (ip_protox[] is an offset into the inetsw[], and inetsw[2] is TCP). >(kgdb) print inetsw[ip_protox[ip->ip_p]].pr_input >$2 = (void (*)()) 0xf01477ec Looks fine. Perhaps the trap didn't actually happen in ip_input? Try "select-frame 12" and then "frame frame->tf_ebp frame->tf_eip", which should tell you where the crash really happened. Bill From owner-freebsd-current Thu Oct 10 14:44:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA18317 for current-outgoing; Thu, 10 Oct 1996 14:44:03 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA18284; Thu, 10 Oct 1996 14:43:58 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.0/8.8.Beta.3) with SMTP id QAA24912; Thu, 10 Oct 1996 16:43:32 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.15) id ; Thu, 10 Oct 96 16:43 CDT Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.Beta.6/8.8.Beta.3) id QAA13666; Thu, 10 Oct 1996 16:43:30 -0500 (CDT) From: Karl Denninger Message-Id: <199610102143.QAA13666@Jupiter.Mcs.Net> Subject: Re: Crash in -current (from the current SNAP) To: fenner@parc.xerox.com (Bill Fenner) Date: Thu, 10 Oct 1996 16:43:30 -0500 (CDT) Cc: fenner@parc.xerox.com, karl@Mcs.Net, current@freebsd.org, hackers@freebsd.org In-Reply-To: <96Oct10.144023pdt.177476@crevenia.parc.xerox.com> from "Bill Fenner" at Oct 10, 96 02:40:12 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > >(kgdb) > >(kgdb) select-frame 14 > >(kgdb) print ip_protox[ip->ip_p] > >$1 = 2 '\002' > > > >That's "INET", if I'm reading the headers correctly. > > No, it's "TCP" (ip_protox[] is an offset into the inetsw[], and inetsw[2] > is TCP). > > >(kgdb) print inetsw[ip_protox[ip->ip_p]].pr_input > >$2 = (void (*)()) 0xf01477ec > > Looks fine. Perhaps the trap didn't actually happen in ip_input? > Try "select-frame 12" and then "frame frame->tf_ebp frame->tf_eip", > which should tell you where the crash really happened. > > Bill Oh oh.... (kgdb) select-frame 12 (kgdb) frame frame->tf_ebp frame->tf_eip #0 0xf0147ae5 in tcp_input (m=0xf2782900, iphlen=20) at ../../netinet/tcp_input.c:438 ../../netinet/tcp_input.c:438: No such file or directory. Which is.... inp = (struct inpcb *)so->so_pcb; >>>>>>> inp->inp_laddr = ti->ti_dst; inp->inp_lport = ti->ti_dport; in_pcbrehash(inp); Right in the middle of the "dropsocket" area. Me smells a problem with the SYN flood patch. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-current Thu Oct 10 14:46:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA18617 for current-outgoing; Thu, 10 Oct 1996 14:46:37 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA18593; Thu, 10 Oct 1996 14:46:27 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id OAA27531; Thu, 10 Oct 1996 14:46:24 -0700 (PDT) Message-Id: <199610102146.OAA27531@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Karl Denninger cc: fenner@parc.xerox.com, current@freebsd.org, hackers@freebsd.org Subject: Re: Crash in -current (from the current SNAP) In-reply-to: Your message of "Thu, 10 Oct 1996 16:39:27 CDT." <199610102139.QAA13465@Jupiter.Mcs.Net> From: David Greenman Reply-To: dg@root.com Date: Thu, 10 Oct 1996 14:46:24 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Yuck. Without a failure address this is going to be a BITCH to find. ... >I have good core dumps here if anyone wants to track this down. Do a "tail -100 vmcore.0 | strings | more" and look for the original trap message. Then use the IP along with sorted nm /kernel output to find the routine that it failed in and the offset. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Thu Oct 10 15:06:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA19744 for current-outgoing; Thu, 10 Oct 1996 15:06:24 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA19725; Thu, 10 Oct 1996 15:05:55 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15734(7)>; Thu, 10 Oct 1996 15:01:58 PDT Received: by crevenia.parc.xerox.com id <177476>; Thu, 10 Oct 1996 15:01:40 -0700 From: Bill Fenner To: fenner@parc.xerox.com, karl@mcs.net Subject: Re: Crash in -current (from the current SNAP) Cc: current@freebsd.org, hackers@freebsd.org, pst@jnx.com Message-Id: <96Oct10.150140pdt.177476@crevenia.parc.xerox.com> Date: Thu, 10 Oct 1996 15:01:25 PDT Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Me smells a problem with the SYN flood patch. Yup. Looks to me like tcp_drop() freed the tcpcb/inpcb, but then tcp_input() wants to use the tcpcb/inpcb. I suspect that an OK patch might be to turn the code around line 420 of tcp_input.c into if (so2) { tcp_drop(sototcpcb(so2), ETIMEDOUT); tcp_attach(so2); /* attach a new pcb */ } else goto drop; Bill From owner-freebsd-current Thu Oct 10 15:10:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA20194 for current-outgoing; Thu, 10 Oct 1996 15:10:44 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA20178; Thu, 10 Oct 1996 15:10:17 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <16121(5)>; Thu, 10 Oct 1996 15:07:35 PDT Received: by crevenia.parc.xerox.com id <177476>; Thu, 10 Oct 1996 15:07:29 -0700 From: Bill Fenner To: fenner@parc.xerox.com, karl@mcs.net Subject: Re: Crash in -current (from the current SNAP) Cc: current@freebsd.org, hackers@freebsd.org, pst@jnx.com Message-Id: <96Oct10.150729pdt.177476@crevenia.parc.xerox.com> Date: Thu, 10 Oct 1996 15:07:17 PDT Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of course, tcp_attach() is static so can't be called from tcp_input(). Either we need to call (*so2->so_proto->pr_usrreqs->pru_attach)(so2), or we need to sofree(so2) and then do another so2=sonewconn(so, 0). (or make tcp_attach() not static). Bill From owner-freebsd-current Thu Oct 10 15:10:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA20213 for current-outgoing; Thu, 10 Oct 1996 15:10:50 -0700 (PDT) Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA20180 for ; Thu, 10 Oct 1996 15:10:22 -0700 (PDT) Received: by diablo.ppp.de (Smail3.1.28.1 #1) id m0vBTI7-000QWWC; Thu, 10 Oct 96 23:09 MET Received: from [193.141.161.123] (monster.pong.ppp.de [193.141.161.123]) by pong.PPP.DE (8.7.5/8.6.12) with ESMTP id AAA21568; Fri, 11 Oct 1996 00:01:20 +0200 (MET DST) Message-Id: In-Reply-To: References: <199610091306.JAA05163@crh.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 11 Oct 1996 00:00:45 +0200 To: John Fieber , Charles Henrich From: Stefan Bethke Subject: Re: 961006-SNAP comments Cc: "Jordan K. Hubbard" , hoek@freenet.hamilton.on.ca, freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 17:30 Uhr -0500 09.10.1996, John Fieber wrote: >On Wed, 9 Oct 1996, Charles Henrich wrote: > >> Why are we forcing people who probably have no clue to go mucking with the >> device table? > >Because this marvelous PC architecture we have often requires it. >Except for people who use only the hardware and software that >came installed on there machine, just about every PC user will at >some point confront IRQs and the like, or they will pay someone >else to. > >If we try and hide the issue, a fair number of people will reach >a dead end and give up before they get started. [...] considering we can't >change the PC architecture, its the best direction to go. Well, the few times I had to install '95 or NT (not that I would suggest '95 being an OS or anything), it detected the hardware (SMC Ultra, NE2000 clones) without problems (the other cards were PCI). Also I've been told that '95 typically detects hardware quite nicely (I'm not talking PnP or PCI). I now have installed both 2.1.0 and 2.1.5 a few times, and I think better automatic probes would be helpful for people "who probably have no clue". Personally, i prefer -c and building a kernel immediatly anyway. Stefan P.S. if only the visual editor would support pcvt correctly... -- Stefan Bethke Hamburg, Germany From owner-freebsd-current Thu Oct 10 15:11:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA20255 for current-outgoing; Thu, 10 Oct 1996 15:11:01 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA20244; Thu, 10 Oct 1996 15:10:57 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.0/8.8.Beta.3) with SMTP id RAA26225; Thu, 10 Oct 1996 17:10:00 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.15) id ; Thu, 10 Oct 96 17:09 CDT Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.Beta.6/8.8.Beta.3) id RAA14435; Thu, 10 Oct 1996 17:09:58 -0500 (CDT) From: Karl Denninger Message-Id: <199610102209.RAA14435@Jupiter.Mcs.Net> Subject: Re: Crash in -current (from the current SNAP) To: fenner@parc.xerox.com (Bill Fenner) Date: Thu, 10 Oct 1996 17:09:57 -0500 (CDT) Cc: fenner@parc.xerox.com, karl@Mcs.Net, current@freebsd.org, hackers@freebsd.org In-Reply-To: <96Oct10.144023pdt.177476@crevenia.parc.xerox.com> from "Bill Fenner" at Oct 10, 96 02:40:12 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > >(kgdb) > >(kgdb) select-frame 14 > >(kgdb) print ip_protox[ip->ip_p] > >$1 = 2 '\002' > > > >That's "INET", if I'm reading the headers correctly. > > No, it's "TCP" (ip_protox[] is an offset into the inetsw[], and inetsw[2] > is TCP). > > >(kgdb) print inetsw[ip_protox[ip->ip_p]].pr_input > >$2 = (void (*)()) 0xf01477ec > > Looks fine. Perhaps the trap didn't actually happen in ip_input? > Try "select-frame 12" and then "frame frame->tf_ebp frame->tf_eip", > which should tell you where the crash really happened. > > Bill > Oh, one more thing to add from that section of code... so2 = sonewconn(so, 0); if (so2 == 0) { tcpstat.tcps_listendrop++; so2 = sodropablereq(so); if (so2) tcp_drop(sototcpcb(so2), ETIMEDOUT); else goto drop; } so = so2; /* * This is ugly, but .... * * Mark socket as temporary until we're * committed to keeping it. The code at * ``drop'' and ``dropwithreset'' check the * flag dropsocket to see if the temporary * socket created here should be discarded. * We mark the socket as discardable until * we're committed to it below in TCPS_LISTEN. */ dropsocket++; inp = (struct inpcb *)so->so_pcb; >>>>>> inp->inp_laddr = ti->ti_dst; inp->inp_lport = ti->ti_dport; in_pcbrehash(inp); The crash is at ">>>>>>" The problem is right here: (kgdb) print so->so_pcb $7 = 0x0 Ouch. Needless to say, trying to write to page zero will blow up! :-) Now how did so->so_pcb end up being zero is the real question? -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-current Thu Oct 10 16:08:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA23501 for current-outgoing; Thu, 10 Oct 1996 16:08:17 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA23496 for ; Thu, 10 Oct 1996 16:08:14 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id QAA00370; Thu, 10 Oct 1996 16:06:11 -0700 (PDT) Message-Id: <199610102306.QAA00370@austin.polstra.com> To: nate@mt.sri.com Cc: max@wide.ad.jp, current@freefall.freebsd.org Subject: Re: kaffe problems In-reply-to: <199610101955.NAA16866@rocky.mt.sri.com> Date: Thu, 10 Oct 1996 16:06:11 -0700 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I changed the subject to something reasonable, since I inadvertently got the thread going with a subject of "none". Nate wrote: > > Thanks. If you can help me a little, I'll try to reproduce the > > problem here. I assume I need to install the "kaffe" and "jdk" > > ports. > > I just did because I could, and it works fine for me. I was getting > weird errors when I had a screwed up CLASSPATH and/or LD_LIBRARY_PATH, > so I suspect those. I installed the "jdk" and "kaffe" ports, and tried the HelloWorldApp that came with kaffe. It worked OK here. Then I installed Max's ld.so.hints file, and it still worked OK. I did have problems at first. As Nate said, it was caused by errors in my environment. The DESCR file from the kaffe port says to set CLASSPATH to ".:/usr/local/share/kaffe/classes.zip". However, that is wrong, because it disagrees with the check in the Makefile, and with the location where the jdk port actually puts the classes.zip file. (To fix it, change "kaffe" to "java".) Also, LD_LIBRARY_PATH _must_ be set to include "/usr/local/lib", even if you've already run ldconfig on that directory. Both of these must be exported into the environment, of course. If they don't appear in the output of "printenv" then they're not exported. Gdb worked OK for me, except that it did get an error when I entered the "help set" command. The version from ports/devel/gdb didn't exhibit that problem. I don't know what is going on with Max's system. It is hard for me to see how the presence or absence of /usr/local/lib/m3/FreeBSD2 in the ldconfig command line could make any difference to kaffe. Max's output from "ldd" indicates that no libraries are being taken from there, anyway. I also don't understand the behavior of his gdb. Maybe he's got a hardware problem. Maybe he's got a corrupted libc.so.3.0. I went over the recent changes to the dynamic linker and to ldconfig again. I still don't see any new problems. I've about run out of ideas, until Max or somebody else can get more information about what is happening when kaffe fails. 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-current Thu Oct 10 16:34:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA25093 for current-outgoing; Thu, 10 Oct 1996 16:34:23 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA25079 for ; Thu, 10 Oct 1996 16:34:18 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id JAA20383; Fri, 11 Oct 1996 09:03:08 +0930 From: Michael Smith Message-Id: <199610102333.JAA20383@genesis.atrad.adelaide.edu.au> Subject: Re: make world fails in -current To: richardc@CSUA.Berkeley.EDU (Veggy Vinny) Date: Fri, 11 Oct 1996 09:03:07 +0930 (CST) Cc: nate@mt.sri.com, current@freebsd.org In-Reply-To: from "Veggy Vinny" at Oct 10, 96 01:15:32 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Veggy Vinny stands accused of saying: > > > > ===> lib > > > ".depend", line 85: Need an operator > > > Fatal errors encountered -- cannot continue > > > *** Error code 1 > > > > # cd /usr/obj; > > # rm -rf * > > # find /usr/src -name obj -print | xargs rm -rf > > Thanks, this seems to have fixed it... =) Then may I suggest unsetting NOCLEAN or NOCLEANDIR so that 'make world' will do this automatically? The Mt. Erebus crater-minimisation fund will be eternally grateful. > -Vince- GaiaNet Corporation Unix Networking Operations -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Thu Oct 10 16:47:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA25999 for current-outgoing; Thu, 10 Oct 1996 16:47:23 -0700 (PDT) Received: from mail.tky007.tth.expo96.ad.jp (tky007.tth.expo96.ad.jp [133.246.32.58]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA25992 for ; Thu, 10 Oct 1996 16:47:16 -0700 (PDT) Received: from tky007.tth.expo96.ad.jp (masafumi@localhost [127.0.0.1]) by mail.tky007.tth.expo96.ad.jp (8.7.6/3.4W4-SMTP) with ESMTP id IAA28098; Fri, 11 Oct 1996 08:44:55 +0900 (JST) Message-Id: <199610102344.IAA28098@mail.tky007.tth.expo96.ad.jp> To: jdp@polstra.com Cc: nate@mt.sri.com, max@wide.ad.jp, current@freefall.freebsd.org Subject: Re: kaffe problems From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= In-Reply-To: Your message of "Thu, 10 Oct 1996 16:06:11 -0700" References: <199610102306.QAA00370@austin.polstra.com> X-Mailer: Mew version 1.06 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 11 Oct 1996 08:44:54 +0900 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thanks folks for taking time on this problem. I decided to re-fetch the kaffe and jdk distributions and reinstall the ports of them, and I did. It made me believe that jdk previously installed on my system was somehow broken in the first place. ;_) >> I just did because I could, and it works fine for me. I was >> getting weird errors when I had a screwed up CLASSPATH and/or >> LD_LIBRARY_PATH, so I suspect those. And stupidly enough, LD_LIBRARY_PATH was another problem causing this. After all, kaffe starts running!! jdp> Also, LD_LIBRARY_PATH _must_ be set to include jdp> "/usr/local/lib", even if you've already run ldconfig on that jdp> directory. This, I have been misunderstanding. I had strong belief that LD_LIBRARY_PATH is unnecessary as long as you execute ldconfig properly. The Makefile of kaffe port does ldconfig after the installation and that made my belief even stronger. ;_) jdp> Gdb worked OK for me, except that it did get an error when I jdp> entered the "help set" command. The version from jdp> ports/devel/gdb didn't exhibit that problem. Now gdb works for me, too except for the "help set" problem. jdp> Maybe he's got a hardware problem. Maybe he's got a jdp> corrupted libc.so.3.0. Oh, right, actually I rebuilt libc.so.3.0, too before reinstalling kaffe and jdk ports, so this may be true. Anyway, the problem was caused mainly by my mistake and misunderstand. I'm awfully sorry for making you put much effort on this and spare time on this. I will request the kaffe port's maintainer to improve the DESCR file to avoid another stupid guy like myself running into the same kind of problem as I had and asking you folks the same questions. Again, I really appreciate you for helping me out. Thanks a lot. ----------------------------------------------------------------------- Masafumi NAKANE, Keio Univ., Dept. of Environmental Information E-Mail : max@wide.ad.jp / max@FreeBSD.ORG [URL] : http://www.sfc.wide.ad.jp/~max/ From owner-freebsd-current Thu Oct 10 16:50:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA26269 for current-outgoing; Thu, 10 Oct 1996 16:50:45 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA26259; Thu, 10 Oct 1996 16:50:37 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.0/8.8.Beta.3) with SMTP id SAA00444; Thu, 10 Oct 1996 18:47:10 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.15) id ; Thu, 10 Oct 96 18:47 CDT Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.Beta.6/8.8.Beta.3) id SAA16950; Thu, 10 Oct 1996 18:47:05 -0500 (CDT) From: Karl Denninger Message-Id: <199610102347.SAA16950@Jupiter.Mcs.Net> Subject: Crash in -current (and fix) - plus NEW issue! To: fenner@parc.xerox.com (Bill Fenner) Date: Thu, 10 Oct 1996 18:47:04 -0500 (CDT) Cc: fenner@parc.xerox.com, karl@Mcs.Net, current@freebsd.org, hackers@freebsd.org, pst@jnx.com In-Reply-To: <96Oct10.150729pdt.177476@crevenia.parc.xerox.com> from "Bill Fenner" at Oct 10, 96 03:07:17 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Of course, tcp_attach() is static so can't be called from tcp_input(). > Either we need to call (*so2->so_proto->pr_usrreqs->pru_attach)(so2), > or we need to sofree(so2) and then do another so2=sonewconn(so, 0). > (or make tcp_attach() not static). > > Bill > >From what I can see of the code the following fragment looked safe: sofree(so2); so2=sonewconn(so, 0); So I inserted that in the appropriate place... We'll see what happens; I'm running that test kernel now on the machine which was blowing up. Since the time to crash is variable, I probably won't know for a day or so if it fixes the problem -- if it does, I'll send in a "send-pr" for the commit with a code diff. On to other things: Has anyone seen THIS oddity? Environment: 2.2-current NFS client BSDI NFS server SOMETIMES, a "pwd" to a mounted directory will fail. If it does, OTHER directories on the same disk (mount point) also may fail -- but NOT all of them. Order is important; ie: if one user fails, another always does, but if the second does, the first may or may not (!) This shows up most frequently either in the shell (complaints at login time, although the directory contents are accessible) or in FTP ("pwd" command returns a failure). It comes and goes without obvious reason or intervention, and when its "gone" everything works as expected. Anyone else seen this? This one is really, really strange! The disks are mounted "rw,bg,intr,nodev,nosuid". Again, this is new in recent -CURRENTs (since about 8/20), and does NOT appear to happen for directories permitted as 755 (which should be readable by anyone anyway). If we can fix *this* one, and the crash fix works, then I think we have a stable build here which we could roll out. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-current Thu Oct 10 17:13:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA27930 for current-outgoing; Thu, 10 Oct 1996 17:13:52 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA27914; Thu, 10 Oct 1996 17:13:13 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15129(7)>; Thu, 10 Oct 1996 17:12:36 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177476>; Thu, 10 Oct 1996 17:12:24 -0700 To: Karl Denninger cc: fenner@parc.xerox.com (Bill Fenner), current@freebsd.org, hackers@freebsd.org, pst@jnx.com Subject: Re: Crash in -current (and fix) - plus NEW issue! In-reply-to: Your message of "Thu, 10 Oct 96 16:47:04 PDT." <199610102347.SAA16950@Jupiter.Mcs.Net> Date: Thu, 10 Oct 1996 17:12:20 PDT From: Bill Fenner Message-Id: <96Oct10.171224pdt.177476@crevenia.parc.xerox.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199610102347.SAA16950@Jupiter.Mcs.Net> you write: >>From what I can see of the code the following fragment looked safe: > >sofree(so2); >so2=sonewconn(so, 0); I think this will leave the socket on the incomplete connections queue. tcp_drop() already tries to free the socket, but sofree() refuses since so_flags has SS_NOFDREF set. This means that it will still take up a queue slot even though that's exactly what we're trying to avoid. I think my suggested fix is: if (so2) { so2->so_flags &= ~SS_NOFDREF; tcp_drop(sototcpcb(so2), ETIMEDOUT); so2 = sonewconn(so, 0); if (so2 == 0) /* can't happen? */ goto drop; } else goto drop; Turning off SS_NOFDREF will let tcp_drop free the socket, and you check to make absolutely sure that sonewconn() gave you something. >So I inserted that in the appropriate place... We'll see what happens; I'm >running that test kernel now on the machine which was blowing up. I think it'll still blow up; since sofree() doesn't actually free the socket (or remove it from the lists), the so2=sonewconn(so,0) will fail and if you don't check the result you'll die later. Bill From owner-freebsd-current Thu Oct 10 17:41:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA29754 for current-outgoing; Thu, 10 Oct 1996 17:41:10 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA29747; Thu, 10 Oct 1996 17:41:04 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.0/8.8.Beta.3) with SMTP id TAA03039; Thu, 10 Oct 1996 19:40:52 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.15) id ; Thu, 10 Oct 96 19:40 CDT Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.Beta.6/8.8.Beta.3) id TAA18402; Thu, 10 Oct 1996 19:40:50 -0500 (CDT) From: Karl Denninger Message-Id: <199610110040.TAA18402@Jupiter.Mcs.Net> Subject: Re: Crash in -current (and fix) - plus NEW issue! To: fenner@parc.xerox.com (Bill Fenner) Date: Thu, 10 Oct 1996 19:40:50 -0500 (CDT) Cc: karl@Mcs.Net, fenner@parc.xerox.com, current@freebsd.org, hackers@freebsd.org, pst@jnx.com In-Reply-To: <96Oct10.171224pdt.177476@crevenia.parc.xerox.com> from "Bill Fenner" at Oct 10, 96 05:12:20 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > In message <199610102347.SAA16950@Jupiter.Mcs.Net> you write: > >>From what I can see of the code the following fragment looked safe: > > > >sofree(so2); > >so2=sonewconn(so, 0); > > I think this will leave the socket on the incomplete connections queue. > tcp_drop() already tries to free the socket, but sofree() refuses since > so_flags has SS_NOFDREF set. This means that it will still take up > a queue slot even though that's exactly what we're trying to avoid. > > I think my suggested fix is: > > if (so2) { > so2->so_flags &= ~SS_NOFDREF; > tcp_drop(sototcpcb(so2), ETIMEDOUT); > so2 = sonewconn(so, 0); > if (so2 == 0) /* can't happen? */ > goto drop; > } else > goto drop; > > Turning off SS_NOFDREF will let tcp_drop free the socket, and you check > to make absolutely sure that sonewconn() gave you something. This blows up because the compiler claims that "so2->so_flags" is not a member (the flag word isn't there?) > >So I inserted that in the appropriate place... We'll see what happens; I'm > >running that test kernel now on the machine which was blowing up. > > I think it'll still blow up; since sofree() doesn't actually free the > socket (or remove it from the lists), the so2=sonewconn(so,0) will fail > and if you don't check the result you'll die later. > > Bill I'll have to look at this more closely. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-current Thu Oct 10 18:37:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA03721 for current-outgoing; Thu, 10 Oct 1996 18:37:17 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA03707 for ; Thu, 10 Oct 1996 18:37:12 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA20907; Fri, 11 Oct 1996 11:07:01 +0930 From: Michael Smith Message-Id: <199610110137.LAA20907@genesis.atrad.adelaide.edu.au> Subject: Re: 'dead' binary stays 'dead'? To: rjk@sparcmill.grauel.com (Richard J Kuhns) Date: Fri, 11 Oct 1996 11:07:00 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, current@FreeBSD.org In-Reply-To: <199610101404.JAA00429@sparcmill.grauel.com> from "Richard J Kuhns" at Oct 10, 96 09:04:31 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Richard J Kuhns stands accused of saying: > > I'll comment. I just started a `make world' 2 days ago (10/8), which ran > just fine (as usual) until it hit one of the gnu libraries during the `make > all' phase, where cc1 died with a signal 11. I changed to that directory, > did a `make clean', changed back to /usr/src, and restarted with a `make > all'. It picked up where it left off, and worked ok for about 2 more > minutes, after which it died again. I tried this cycle several more times, > and got 3 more sig 11s, 1 sig 6, and one complaint from gcc/cc1 about a > "bad INSN". This _sounds_ like a memory problem; certainly the symptoms of my particular case were 100% consistent, but then again gcc is a much more complex animal... > Richard Kuhns rjk@grauel.com -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Thu Oct 10 18:55:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA05124 for current-outgoing; Thu, 10 Oct 1996 18:55:08 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA05111; Thu, 10 Oct 1996 18:54:54 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14480(5)>; Thu, 10 Oct 1996 18:54:17 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177476>; Thu, 10 Oct 1996 18:54:00 -0700 To: Karl Denninger cc: fenner@parc.xerox.com (Bill Fenner), current@freebsd.org, hackers@freebsd.org, pst@jnx.com Subject: Re: Crash in -current (and fix) - plus NEW issue! In-reply-to: Your message of "Thu, 10 Oct 96 17:40:50 PDT." <199610110040.TAA18402@Jupiter.Mcs.Net> Date: Thu, 10 Oct 1996 18:53:45 PDT From: Bill Fenner Message-Id: <96Oct10.185400pdt.177476@crevenia.parc.xerox.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199610110040.TAA18402@Jupiter.Mcs.Net> you write: >> so2->so_flags &= ~SS_NOFDREF; ^^^^^ state. Brain-o, after staring at this code too long my mind turns to mush. Bill From owner-freebsd-current Thu Oct 10 18:58:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA05464 for current-outgoing; Thu, 10 Oct 1996 18:58:24 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA05456; Thu, 10 Oct 1996 18:58:20 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.0/8.8.Beta.3) with SMTP id UAA06427; Thu, 10 Oct 1996 20:57:44 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.15) id ; Thu, 10 Oct 96 20:57 CDT Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.Beta.6/8.8.Beta.3) id UAA20371; Thu, 10 Oct 1996 20:57:41 -0500 (CDT) From: Karl Denninger Message-Id: <199610110157.UAA20371@Jupiter.Mcs.Net> Subject: Re: Crash in -current (and fix) - plus NEW issue! To: fenner@parc.xerox.com (Bill Fenner) Date: Thu, 10 Oct 1996 20:57:41 -0500 (CDT) Cc: karl@Mcs.Net, fenner@parc.xerox.com, current@freebsd.org, hackers@freebsd.org, pst@jnx.com In-Reply-To: <96Oct10.185400pdt.177476@crevenia.parc.xerox.com> from "Bill Fenner" at Oct 10, 96 06:53:45 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > In message <199610110040.TAA18402@Jupiter.Mcs.Net> you write: > >> so2->so_flags &= ~SS_NOFDREF; > ^^^^^ state. > > Brain-o, after staring at this code too long my mind turns to mush. > > Bill > I'll give that a shot... -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-current Thu Oct 10 19:02:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA05839 for current-outgoing; Thu, 10 Oct 1996 19:02:11 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA05832 for ; Thu, 10 Oct 1996 19:02:07 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id SAA13237 for ; Thu, 10 Oct 1996 18:59:56 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA21094; Fri, 11 Oct 1996 11:27:00 +0930 From: Michael Smith Message-Id: <199610110157.LAA21094@genesis.atrad.adelaide.edu.au> Subject: Re: 961006-SNAP comments To: stefan@pong.ppp.de (Stefan Bethke) Date: Fri, 11 Oct 1996 11:26:59 +0930 (CST) Cc: jfieber@indiana.edu, henrich@crh.cl.msu.edu, jkh@time.cdrom.com, hoek@freenet.hamilton.on.ca, freebsd-current@FreeBSD.org In-Reply-To: from "Stefan Bethke" at Oct 11, 96 00:00:45 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Stefan Bethke stands accused of saying: > > Well, the few times I had to install '95 or NT (not that I would suggest > '95 being an OS or anything), it detected the hardware (SMC Ultra, NE2000 > clones) without problems (the other cards were PCI). Also I've been told > that '95 typically detects hardware quite nicely (I'm not talking PnP or > PCI). > > I now have installed both 2.1.0 and 2.1.5 a few times, and I think better > automatic probes would be helpful for people "who probably have no clue". You're quite welcome to write one. You do realise that the "if the disk light stops blinking you should turn the machine off and on again" thing is largely there because the sort of brutal probing necessary to find an NE2000 is just the sort of thing that totally screws other devices (eg. SCSI controllers etc.). > P.S. if only the visual editor would support pcvt correctly... What makes you say it doesn't? And if it doesn't, where's the pr explaining the problem? How can we fix something if nobody will tell us that it's broken? > Stefan Bethke -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Thu Oct 10 20:10:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA09906 for current-outgoing; Thu, 10 Oct 1996 20:10:47 -0700 (PDT) Received: from po1.glue.umd.edu (po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA09901 for ; Thu, 10 Oct 1996 20:10:42 -0700 (PDT) Received: from downlink.eng.umd.edu (downlink.eng.umd.edu [129.2.98.182]) by po1.glue.umd.edu (8.8.0/8.7.3) with ESMTP id XAA03111; Thu, 10 Oct 1996 23:10:37 -0400 (EDT) Received: from localhost (chuckr@localhost) by downlink.eng.umd.edu (8.7.5/8.7.3) with SMTP id XAA10270; Thu, 10 Oct 1996 23:10:36 -0400 (EDT) X-Authentication-Warning: downlink.eng.umd.edu: chuckr owned process doing -bs Date: Thu, 10 Oct 1996 23:10:36 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@downlink.eng.umd.edu To: Michael Smith cc: Veggy Vinny , nate@mt.sri.com, current@FreeBSD.ORG Subject: Re: make world fails in -current In-Reply-To: <199610102333.JAA20383@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 11 Oct 1996, Michael Smith wrote: > Veggy Vinny stands accused of saying: > > > > > > ===> lib > > > > ".depend", line 85: Need an operator > > > > Fatal errors encountered -- cannot continue > > > > *** Error code 1 > > > > > > # cd /usr/obj; > > > # rm -rf * > > > # find /usr/src -name obj -print | xargs rm -rf > > > > Thanks, this seems to have fixed it... =) > > Then may I suggest unsetting NOCLEAN or NOCLEANDIR so that 'make > world' will do this automatically? > > The Mt. Erebus crater-minimisation fund will be eternally grateful. You realize that wouldn't help him? He had trash files in his regular /usr/src, not his /usr/obj. Unless I'M full of trash ... (it happens). > > > -Vince- GaiaNet Corporation Unix Networking Operations > > -- > ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ > ]] Genesis Software genesis@atrad.adelaide.edu.au [[ > ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ > ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ > ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Thu Oct 10 21:08:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA13490 for current-outgoing; Thu, 10 Oct 1996 21:08:02 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA13462; Thu, 10 Oct 1996 21:07:55 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.0/8.8.Beta.3) with SMTP id XAA11153; Thu, 10 Oct 1996 23:05:16 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.15) id ; Thu, 10 Oct 96 23:05 CDT Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.Beta.6/8.8.Beta.3) id XAA23331; Thu, 10 Oct 1996 23:05:13 -0500 (CDT) From: Karl Denninger Message-Id: <199610110405.XAA23331@Jupiter.Mcs.Net> Subject: Re: Crash in -current (and fix) - plus NEW issue! To: fenner@parc.xerox.com (Bill Fenner) Date: Thu, 10 Oct 1996 23:05:13 -0500 (CDT) Cc: karl@Mcs.Net, fenner@parc.xerox.com, current@freebsd.org, hackers@freebsd.org, pst@jnx.com In-Reply-To: <96Oct10.171224pdt.177476@crevenia.parc.xerox.com> from "Bill Fenner" at Oct 10, 96 05:12:20 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > In message <199610102347.SAA16950@Jupiter.Mcs.Net> you write: > >>From what I can see of the code the following fragment looked safe: > > > >sofree(so2); > >so2=sonewconn(so, 0); > > I think this will leave the socket on the incomplete connections queue. > tcp_drop() already tries to free the socket, but sofree() refuses since > so_flags has SS_NOFDREF set. This means that it will still take up > a queue slot even though that's exactly what we're trying to avoid. > > I think my suggested fix is: > > if (so2) { > so2->so_flags &= ~SS_NOFDREF; > tcp_drop(sototcpcb(so2), ETIMEDOUT); > so2 = sonewconn(so, 0); > if (so2 == 0) /* can't happen? */ > goto drop; > } else > goto drop; > > Turning off SS_NOFDREF will let tcp_drop free the socket, and you check > to make absolutely sure that sonewconn() gave you something. > > >So I inserted that in the appropriate place... We'll see what happens; I'm > >running that test kernel now on the machine which was blowing up. > > I think it'll still blow up; since sofree() doesn't actually free the > socket (or remove it from the lists), the so2=sonewconn(so,0) will fail > and if you don't check the result you'll die later. > > Bill This doesn't work. I just got another panic, and this one is from legit data inbound but with another null dereference in the same place. I did NOT get a panic for several hours with the other patch (sofree(so2)) in there; I'm going to go back to THAT kernel and see if it is stable. I don't expect it will be, after what you sent, but heh, right now I've got nothing to lose :-) This problem is not fixed. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-current Thu Oct 10 21:59:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA16804 for current-outgoing; Thu, 10 Oct 1996 21:59:08 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA16799 for ; Thu, 10 Oct 1996 21:58:59 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id VAA01796; Thu, 10 Oct 1996 21:58:22 -0700 (PDT) Message-Id: <199610110458.VAA01796@austin.polstra.com> To: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= cc: nate@mt.sri.com, current@freefall.freebsd.org Subject: Re: kaffe problems In-reply-to: Your message of "Fri, 11 Oct 1996 08:44:54 +0900." <199610102344.IAA28098@mail.tky007.tth.expo96.ad.jp> Date: Thu, 10 Oct 1996 21:58:22 -0700 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Thanks folks for taking time on this problem. ... > Anyway, the problem was caused mainly by my mistake and misunderstand. > I'm awfully sorry for making you put much effort on this and spare time > on this. Max, I don't think you need to feel bad about this. Based on the symptoms you observed, it would be natural to think that something was wrong with ldconfig or the dynamic linker. All the more so since some extensive changes were made to both of them very recently. And, kaffe uses dlopen() and dlsym(), which exercise parts of the dynamic linker that are very rarely used. I drew the same (wrong) conclusion as you. You did a good job of stating the problem and of answering the questions that we asked. The reason it took so much time to solve this was that it was a very baffling problem! Nobody blames you for that. > I had strong belief that LD_LIBRARY_PATH is unnecessary as long as > you execute ldconfig properly. Yes, you are right about that, as far as the dynamic linker is concerned. Unfortunately, kaffe itself examines LD_LIBRARY_PATH directly, and does something with it. That is unusual. > The Makefile of kaffe port does ldconfig after the > installation and that made my belief even stronger. ;_) Yup! > jdp> Maybe he's got a hardware problem. Maybe he's got a > jdp> corrupted libc.so.3.0. > > Oh, right, actually I rebuilt libc.so.3.0, too before reinstalling > kaffe and jdk ports, so this may be true. Yes, maybe that was the problem. Something was seriously hosed in your system, anyway. I'm glad it's working OK again. 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-current Thu Oct 10 22:09:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA17489 for current-outgoing; Thu, 10 Oct 1996 22:09:25 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA17484 for ; Thu, 10 Oct 1996 22:09:23 -0700 (PDT) Received: from localhost (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with SMTP id WAA25928; Thu, 10 Oct 1996 22:07:23 -0700 Date: Thu, 10 Oct 1996 22:07:21 -0700 (PDT) From: Veggy Vinny To: Chuck Robey cc: Michael Smith , nate@mt.sri.com, current@FreeBSD.ORG Subject: Re: make world fails in -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 10 Oct 1996, Chuck Robey wrote: > > > > > ===> lib > > > > > ".depend", line 85: Need an operator > > > > > Fatal errors encountered -- cannot continue > > > > > *** Error code 1 > > > > > > Thanks, this seems to have fixed it... =) > > > > Then may I suggest unsetting NOCLEAN or NOCLEANDIR so that 'make > > world' will do this automatically? I never had NOCLEAN or NOCLEANDIR set in the first place since make world by default is supposed to do the make clean.... I deleted everything in /usr/src and resupped the entire src tree and the same thing happened... There was also no .depend file in the src or the obj directory for the cvs lib. > > The Mt. Erebus crater-minimisation fund will be eternally grateful. > > You realize that wouldn't help him? He had trash files in his regular > /usr/src, not his /usr/obj. Unless I'M full of trash ... (it happens). Yeah, I don't know what happened... All I know was I was doing the make world over a telnet connection.... GaiaNet is 900 miles away and the connection lagged so much, it cut me off so when I tried to do make world, it just break there even after deleting everything and resupping... Guess the /usr/obj directory has something that wasn't deleted causing it to break while there was no .depend file in sight... -Vince- GaiaNet Corporation Unix Networking Operations From owner-freebsd-current Thu Oct 10 22:11:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA17628 for current-outgoing; Thu, 10 Oct 1996 22:11:05 -0700 (PDT) Received: from dfw-ix9.ix.netcom.com (dfw-ix9.ix.netcom.com [206.214.98.9]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA17604; Thu, 10 Oct 1996 22:10:54 -0700 (PDT) Received: from tensbum (col-oh1-08.ix.netcom.com [199.183.200.40]) by dfw-ix9.ix.netcom.com (8.6.13/8.6.12) with SMTP id WAA14770; Thu, 10 Oct 1996 22:10:22 -0700 Message-Id: <3.0b35.32.19961011011020.00b6c70c@ix.netcom.com> X-Sender: tensbum@ix.netcom.com X-Mailer: Windows Eudora Pro Version 3.0b35 (32) Date: Fri, 11 Oct 1996 01:10:22 -0400 To: freebsd-questions@FreeBSD.ORG From: "Michael P. Deslippe" Subject: Error 22 Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am trying for the first time to set up FreeBSD (it's also my first UNIX installation). I am trying a small (USER) install on a second IDE harddrive on my system. I have created a small DOS partition (80Mb), created a DOS directory called FreeBSD, and filled it with /bin /docs /dict /manpages files and directories from the FTP server (Micro Center was out of the CD and I'm in a hurry). I booted off the floppy and ran the novice install - after a few dry runs (mostly because I wasn't paying attention), I got it to run all the way up to COMMIT. During the process of trying to create the file system, it bombs out and gives an error that says: error mounting /dev/wd2s2 on /dos: invalid argument (22) wd2s2 is the name of the DOS partition What do I need to do? I'm loading 2.1.5-Release If God's your co-pilot, switch seats! ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Michael P. Deslippe | People who can view their environment and not The Christian Advisor | see intelligent design, can't be regarded Galloway, Ohio | intelligently! ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ God will not forgive your sins in Heaven, for He already forgave them at the cross! From owner-freebsd-current Thu Oct 10 23:28:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA21286 for current-outgoing; Thu, 10 Oct 1996 23:28:18 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA21188 for ; Thu, 10 Oct 1996 23:26:07 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id XAA05687; Thu, 10 Oct 1996 23:25:11 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id WAA13341; Thu, 10 Oct 1996 22:05:17 -0700 (PDT) Message-Id: <199610110505.WAA13341@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Richard J Kuhns cc: Michael Smith , current@freebsd.org Subject: Re: 'dead' binary stays 'dead'? In-reply-to: Your message of Thu, 10 Oct 96 09:04:31 -0500. <199610101404.JAA00429@sparcmill.grauel.com> Date: Thu, 10 Oct 1996 22:03:56 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I'll comment. I just started a `make world' 2 days ago (10/8), which ran >just fine (as usual) until it hit one of the gnu libraries during the `make >all' phase, where cc1 died with a signal 11. I changed to that directory, >did a `make clean', changed back to /usr/src, and restarted with a `make >all'. It picked up where it left off, and worked ok for about 2 more >minutes, after which it died again. I tried this cycle several more times, >and got 3 more sig 11s, 1 sig 6, and one complaint from gcc/cc1 about a >"bad INSN". I'll comment, although it doesn't totally apply, because I've only done this on NetBSD-current (I have never run FreeBSD-current, and I have never had reason to do a make world on the 2.1.0 and 2.1.5 systems I've run), which doesn't have John's VM work. I usually see these kinds of problems when I have bad RAM, or the cache or RAM timings are too aggresive. If this is a new problem, with hardware that hasn't been changed in awhile, however, this may not be your problem. >ASUS motherboard, 120 MH Pentium, 64MB RAM, Buslogic 946c, 2 Barracudas. >The `make world' was done on an otherwise idle system, at the console (I >wasn't even running X). This is the exact hardware one of my NetBSD machines is (well, it had a BT956c and/or an Adaptec 2940UW, depending on when it was run, and the drives were different... OK, almost exact...). I've also spent lots of time tweaking on my AMD 5x86/133 (formerly AMD 486DX2/80), EISA bus machine. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-current Fri Oct 11 00:05:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA23730 for current-outgoing; Fri, 11 Oct 1996 00:05:02 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA23690; Fri, 11 Oct 1996 00:04:38 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id QAA24052; Fri, 11 Oct 1996 16:33:42 +0930 From: Michael Smith Message-Id: <199610110703.QAA24052@genesis.atrad.adelaide.edu.au> Subject: Re: Error 22 To: tensbum@ix.netcom.com (Michael P. Deslippe) Date: Fri, 11 Oct 1996 16:33:41 +0930 (CST) Cc: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: <3.0b35.32.19961011011020.00b6c70c@ix.netcom.com> from "Michael P. Deslippe" at Oct 11, 96 01:10:22 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Firstly, please don't send installation questions to the -current or -stable lists. We don't care about your problems; take them elsewhere. Now, because I feel that I shouldn't flame you without offering some semblance of substance : Michael P. Deslippe stands accused of saying: > > installation). I am trying a small (USER) install on a second IDE > harddrive on my system. I have created a small DOS partition (80Mb), ... > > error mounting /dev/wd2s2 on /dos: invalid argument (22) > > wd2s2 is the name of the DOS partition wd2 is the _third_ IDE disk. wd0 is the first, wd1 is the second. > Michael P. Deslippe | People who can view their environment and not -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Fri Oct 11 01:19:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA27143 for current-outgoing; Fri, 11 Oct 1996 01:19:28 -0700 (PDT) Received: from covina.lightside.com (covina.lightside.com [207.67.176.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA27112; Fri, 11 Oct 1996 01:19:23 -0700 (PDT) Received: from localhost (jehamby@localhost) by covina.lightside.com (8.8.0/8.8.0) with SMTP id BAA10056; Fri, 11 Oct 1996 01:19:17 -0700 (PDT) Date: Fri, 11 Oct 1996 01:19:12 -0700 (PDT) From: Jake Hamby To: sos@freebsd.org cc: current@freebsd.org Subject: Bug with moused and XFree86 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was very interested to discover the recent addition of moused to FreeBSD-current. GPM was always a nifty program to have for Linux, and it's great to see that FreeBSD now provides the same functionality (with a nifty arrow cursor, no less!). However, I've noticed two strange bugs affecting XFree86 (I've consistently reproduced them with 3.1.2-S as well as the 3.1.2-G beta) when moused is running. With twm as the window manager, when I click on the title-bar, the "four-corner arrow" stays active AFTER I release the mouse button, UNTIL I move the mouse (it _should_ change back to the regular arrow immediately after releasing the button). When fvwm95 is the window manager (which defaults to click-to-focus, not focus-follows-mouse), a different bug occurs. When I click to activate a new window, any characters I type are ignored, until I move the mouse (as little as one pixel), then all the characters I've typed display. I'm running FreeBSD-current with a Microsoft-compatible serial mouse on COM1. "vidcontrol -m off" was in effect during these tests, but the moused was running (started by /etc/rc.i386). I believe these are two symptoms of the same problem. My uneducated guess (and don't even _think_ I have time to look at the source code right now :-) is that moused is filtering XFree86's access to the mouse device and somehow certain events (in this case mouse-down) block it until another mouse movement is received. I don't ever remember having troubles like this with Linux and GPM, so I'm guessing that moused, not XFree86, can be patched to fix these problems. Thanks! -- Jake From owner-freebsd-current Fri Oct 11 01:30:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA28099 for current-outgoing; Fri, 11 Oct 1996 01:30:08 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA27888 for ; Fri, 11 Oct 1996 01:27:30 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA17746 for ; Fri, 11 Oct 1996 10:26:03 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA09608 for freebsd-current@FreeBSD.org; Fri, 11 Oct 1996 10:26:03 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id JAA04373 for freebsd-current@FreeBSD.org; Fri, 11 Oct 1996 09:45:57 +0200 (MET DST) From: J Wunsch Message-Id: <199610110745.JAA04373@uriah.heep.sax.de> Subject: Re: Good Job guys To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Fri, 11 Oct 1996 09:45:57 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Veggy Vinny at "Oct 9, 96 04:08:39 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Veggy Vinny wrote: > networking and stuff. Anyways, is the uname -a for the -current kernel > supposed to say SNAP-100496? Nope, 2.2-CURRENT. Your /sys/conf/newvers.sh is hosed. Here's the variable assignments from my version: TYPE="FreeBSD" REVISION="2.2" BRANCH="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-current Fri Oct 11 02:21:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA02451 for current-outgoing; Fri, 11 Oct 1996 02:21:14 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA02442; Fri, 11 Oct 1996 02:20:59 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id LAA14775; Fri, 11 Oct 1996 11:20:44 +0200 Message-Id: <199610110920.LAA14775@ra.dkuug.dk> Subject: Re: Bug with moused and XFree86 To: jehamby@lightside.com (Jake Hamby) Date: Fri, 11 Oct 1996 11:20:44 +0200 (MET DST) Cc: sos@FreeBSD.org, current@FreeBSD.org In-Reply-To: from "Jake Hamby" at Oct 11, 96 01:19:12 am From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Jake Hamby who wrote: > > However, I've noticed two strange bugs affecting XFree86 (I've > consistently reproduced them with 3.1.2-S as well as the 3.1.2-G beta) > when moused is running. With twm as the window manager, when I click on > the title-bar, the "four-corner arrow" stays active AFTER I release the > mouse button, UNTIL I move the mouse (it _should_ change back to the > regular arrow immediately after releasing the button). > > When fvwm95 is the window manager (which defaults to click-to-focus, not > focus-follows-mouse), a different bug occurs. When I click to activate a > new window, any characters I type are ignored, until I move the mouse (as > little as one pixel), then all the characters I've typed display. > > I'm running FreeBSD-current with a Microsoft-compatible serial mouse on > COM1. "vidcontrol -m off" was in effect during these tests, but the > moused was running (started by /etc/rc.i386). How -current ?? Have you created the /dev/sysmouse & /dev/consolectl devices?? Have you enabled the emulate 3 button in moused ?? Have you enabled the emulate 3 button in XFree86 ?? What mouse device does XFree86 use ?? What mouse type does XFree86 use ?? I see none of the problems here, but then I use a real 3 button mouse and Xaccel.. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Fri Oct 11 02:35:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA03269 for current-outgoing; Fri, 11 Oct 1996 02:35:33 -0700 (PDT) Received: from mail11.digital.com (mail11.digital.com [192.208.46.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA03254 for ; Fri, 11 Oct 1996 02:35:29 -0700 (PDT) From: garyj@frt.dec.com Received: from cssmuc.frt.dec.com by mail11.digital.com (8.7.5/UNX 1.2/1.0/WV) id FAA04488; Fri, 11 Oct 1996 05:35:06 -0400 (EDT) Received: from localhost by cssmuc.frt.dec.com; (5.65v3.2/1.1.8.2/14Nov95-0232PM) id AA32112; Fri, 11 Oct 1996 11:34:55 +0200 Message-Id: <9610110934.AA32112@cssmuc.frt.dec.com> X-Mailer: exmh version 1.6.4 10/10/95 To: current@freebsd.org In-Reply-To: Message from Karl Denninger of Thu, 10 Oct 96 16:39:27 CDT. Reply-To: gjennejohn@frt.dec.com Subject: Re: Crash in -current (from the current SNAP) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Oct 96 11:34:54 +0200 X-Mts: smtp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk karl@mcs.net writes: > > >>>>> (*inetsw[ip_protox[ip->ip_p]].pr_input)(m, hlen); > > > > > >>What's going on here? > > > > > >Either ip_protox[ip->ip_p] is out of range (should be 1..7 or 8 > > >depending on if what options you have in your kernel), or > > >inetsw[ip_protox[ip->ip_p]].pr_input is. > > [snip] I don't knwo whether this will help, but I saw the same thing when I upgraded my kernel using the latest sources on Wednesday (except it was udp, not tcp). The problems went away after I re-made the LKMs. The crash was being caused by an NFS access from a client. Since then I haven't had any more crashes. --- Gary Jennejohn (work) gjennejohn@frt.dec.com (home) Gary.Jennejohn@munich.netsurf.de (play) gj@freebsd.org From owner-freebsd-current Fri Oct 11 03:22:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA05778 for current-outgoing; Fri, 11 Oct 1996 03:22:53 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA05771 for ; Fri, 11 Oct 1996 03:22:41 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id LAA23946; Fri, 11 Oct 1996 11:16:12 +0100 Date: Fri, 11 Oct 1996 11:16:12 +0100 (BST) From: Doug Rabson To: Hidetoshi Shimokawa cc: bartol@salk.edu, current@FreeBSD.ORG Subject: Re: NFS weirdness in -current In-Reply-To: <9764.844967087@sat.t.u-tokyo.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 11 Oct 1996, Hidetoshi Shimokawa wrote: > bartol> Yes, it does sound like that problem now that you point it out. > bartol> > bartol> Hidetoshi, is there anything I can do to help out? > > I already made a patch and send it to freebsd-lite2 list. > (I guess you can find it by mailing list archive search, > keyword is "Delayed write patch".) > > Doug will commit it to -current tomorrow(it may depends on time zone :-). > If you cannot wait it, I will send you the patch. > > Please try the patch. I just committed the fix. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 734 3761 FAX: +44 171 734 6426 From owner-freebsd-current Fri Oct 11 03:31:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA06381 for current-outgoing; Fri, 11 Oct 1996 03:31:26 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA06181 for ; Fri, 11 Oct 1996 03:28:10 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id LAA23986; Fri, 11 Oct 1996 11:27:15 +0100 Date: Fri, 11 Oct 1996 11:27:15 +0100 (BST) From: Doug Rabson Reply-To: Doug Rabson To: John Polstra cc: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= , current@freefall.freebsd.org Subject: Re: your mail In-Reply-To: <199610101748.KAA05145@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 10 Oct 1996, John Polstra wrote: > [snip] > > * If the program died in the dynamic linker, then I will need a > sorted namelist from your installed version of the dynamic linker. Of > course, your installed version is stripped, so you can't get a namelist > from it. :-( But hopefully, the unstripped version still exists on your > system, in "/usr/obj/usr/src/gnu/usr.bin/ld/rtld/ld.so". Run "nm -an" > on that file, and send me the output. Note: it is possible to use gdb on the dynamic linker. I have done this and it is safe. Just go to /usr/src/gnu/usr.bin/ld/rtld and type 'make DEBUG_FLAGS=-g clean all install'. I also used to use a debug crt0.o which allowed me to single step into ld.so. The only thing I wasn't able to debug was the startup sequence; you can only debug calls to dlopen etc. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 734 3761 FAX: +44 171 734 6426 From owner-freebsd-current Fri Oct 11 05:08:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA11465 for current-outgoing; Fri, 11 Oct 1996 05:08:53 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA11459 for ; Fri, 11 Oct 1996 05:08:47 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id WAA24073; Fri, 11 Oct 1996 22:00:59 +1000 Date: Fri, 11 Oct 1996 22:00:59 +1000 From: Bruce Evans Message-Id: <199610111200.WAA24073@godzilla.zeta.org.au> To: alk@Think.COM, current@freebsd.org Subject: Re: muldi3.c Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I wonder about this redundancy. > >; diff ./lib/libc/quad/muldi3.c ./sys/libkern/muldi3.c >diff ./lib/libc/quad/muldi3.c ./sys/libkern/muldi3.c >35a36,37 >> * >> * $Id: muldi3.c,v 1.3 1995/05/30 08:06:41 rgrimes Exp $ >37,40d38 >< >< #if defined(LIBC_SCCS) && !defined(lint) >< static char sccsid[] = "@(#)muldi3.c 8.1 (Berkeley) 6/4/93"; >< #endif /* LIBC_SCCS and not lint */ libkern is supposed to be built from libc by copying, or perhaps by symlinking (see libc/Makefile). Under cvs, symlinks don't work and cvs Ids get out of sync. The sccsids aren't changed by cvs, but were nuked when Ids were added to the kernel. We could compile muldi3.c directly out of libc/quad using .PATH. However, muldi3.c isn't used for the i386, and I broke this possibility for the quad functions that are used by changing "quad.h" to (this was required for compiling with -I- to get unambiguous paths). Bruce From owner-freebsd-current Fri Oct 11 05:56:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA13615 for current-outgoing; Fri, 11 Oct 1996 05:56:05 -0700 (PDT) Received: from unix.guru.org (kmitch@phantasma.bevc.blacksburg.va.us [198.82.200.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA13549 for ; Fri, 11 Oct 1996 05:55:53 -0700 (PDT) Received: (from kmitch@localhost) by unix.guru.org (8.7.6/8.7.3) id IAA02387 for current@freebsd.org; Fri, 11 Oct 1996 08:55:05 -0400 (EDT) From: Keith Mitchell Message-Id: <199610111255.IAA02387@unix.guru.org> Subject: Weirdness in current To: current@freebsd.org Date: Fri, 11 Oct 1996 08:55:05 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am running current (10-10) and have noticed the following weirdnesses. These also existed in the 09-25 version. I have a C++ program I wrote, and it works fine as long as you don't try to redirect the output. Doing so, causes it to core dump. Compiling the same program on a 2.1.0R system works fine though. The second weirdness manifests it self with the wwwcount cgi script that many people use for a web counter. On my web page (www.guru.org) I have three counters in a frame (time, date, and counter). When I run netscape local on my machine to view it (3.0/3.01b1) most of the time I get one of the counters and a bunch or garbage. If I view it by running netscape on another machine (2.1.0R or Digital Unix 4.0) it looks fine. Anyone have any ideas??? From owner-freebsd-current Fri Oct 11 06:46:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA16030 for current-outgoing; Fri, 11 Oct 1996 06:46:42 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA16025 for ; Fri, 11 Oct 1996 06:46:40 -0700 (PDT) Received: from alpha.jpunix.com (root@alpha.jpunix.com [199.3.234.18]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id GAA14384 for ; Fri, 11 Oct 1996 06:46:36 -0700 (PDT) Received: (from perry@localhost) by alpha.jpunix.com (8.7.5/8.7.5) id IAA00523 for freebsd-current@freebsd.org; Fri, 11 Oct 1996 08:44:22 -0500 (CDT) Date: Fri, 11 Oct 1996 08:44:20 -0500 (CDT) From: "John A. Perry" To: freebsd-current@freebsd.org Subject: Alternate SUP sites? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Are there any alternate SUP sites? I've been trying to get to sup.freebsd.org and have had either no connects or timeouts. John Perry KG5RG perry@alpha.jpunix.com PGP-encrypted e-mail welcome! WWW - http://www.jpunix.com PGP 2.62 key for perry@jpunix.com is on the keyservers. From owner-freebsd-current Fri Oct 11 07:29:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA18691 for current-outgoing; Fri, 11 Oct 1996 07:29:53 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA18685 for ; Fri, 11 Oct 1996 07:29:51 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id HAA01081; Fri, 11 Oct 1996 07:29:09 -0700 (PDT) To: "John A. Perry" Cc: current@freebsd.org Subject: Re: Alternate SUP sites? In-reply-to: Your message of "Fri, 11 Oct 1996 08:44:20 CDT." Date: Fri, 11 Oct 1996 07:29:08 -0700 Message-ID: <1079.845044148@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Are there any alternate SUP sites? I've been trying to get to > sup.freebsd.org and have had either no connects or timeouts. It appears that they've all disappeared, one by one. :-( Any new sup site volunteers? Jordan From owner-freebsd-current Fri Oct 11 07:38:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA19509 for current-outgoing; Fri, 11 Oct 1996 07:38:26 -0700 (PDT) Received: from bmccane.uit.net ([208.129.189.48]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA19493; Fri, 11 Oct 1996 07:38:18 -0700 (PDT) Received: (from root@localhost) by bmccane.uit.net (8.7.6/8.7.3) id JAA01225; Fri, 11 Oct 1996 09:38:04 -0500 (CDT) Date: Fri, 11 Oct 1996 09:38:03 -0500 (CDT) From: Wm Brian McCane To: Julian Elischer cc: current@freefall.freebsd.org Subject: Re: HELP!! kernel deadlock found.. In-Reply-To: <199610030539.WAA02269@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 2 Oct 1996, Julian Elischer wrote: > > Take the following 3 processes: > > proc N, with a lock on file / (inode 2) > wchan of that inode, waitstring of "ufslk2" > is waiting for inode for /mnt in the root filesystem (inode M) > > proc N+1 with a lock on the inode M (/mnt in root filesystem) > is waiting for inode for / (inode 2) in the mounted filesystem /mnt > it is showing "uihget" as a waitstring. > > proc N+2 with a lock on inode 2 of the mnt filesystem (/ of that filesystem) > is waiting for the inode for / and is showing "ufslk2" as a waitstring. > > It is my suspicion that process N+2 may be trying to unmount /mnt. > > Unfortunatly though I have the system stopped in gdb > I don't know how to examine the stacktrace of arbitrary > processes so I can't say how those 3 processes got where > they are. All other processes on the system > that need to access the filesystem are locked in "ufslk2" > > e.g. any new logins go there immediatly. :( > > if anyone knows how to examine an arbitrary process stacktrace > I'd like to hear about it....... > > I'll leave the system frozen in this state, > and I can arange to get other people with internet access > to be able to run gdb and examine whatever they want.. > > David? > Terry? > John? > any takers? > > I'd love to be able to see what those 3 stack traces show..... > > > julian > I am seeing a strange "lockup" on my system as well. After running for an unspecified length of time, I will see that 'innd' is in ufslk2. After it does this, the 'df' command gets stuck in vfsbsy, down in vfs_subr.c. The only way to fix this problem is to reboot the system, which I can do from the root account no problem. Another "interesting" side effect, is that any files which are written after this time end up 0 bytes long after the 'fsck' on system reboot. I discovered this when I rebuilt and installed a new kernel one time 8(. brian From owner-freebsd-current Fri Oct 11 08:23:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA22208 for current-outgoing; Fri, 11 Oct 1996 08:23:49 -0700 (PDT) Received: from news.IAEhv.nl (root@news.IAEhv.nl [194.151.64.4]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA22202 for ; Fri, 11 Oct 1996 08:23:42 -0700 (PDT) Received: from LOCAL (uucp@localhost) by news.IAEhv.nl (8.6.13/1.63) with IAEhv.nl; pid 25014 on Fri, 11 Oct 1996 17:08:03 +0200; id RAA25014 efrom: marc@nietzsche.bowtie.nl; eto: current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by nietzsche.bowtie.nl (8.7.5/8.7.3) with ESMTP id RAA14750 for ; Fri, 11 Oct 1996 17:05:19 +0200 (MET DST) Message-Id: <199610111505.RAA14750@nietzsche.bowtie.nl> X-Mailer: exmh version 1.6.7 5/3/96 To: current@freebsd.org Subject: Solid server don't work Content-Transfer-Encoding: quoted-printable Date: Fri, 11 Oct 1996 17:05:18 +0200 From: Marc van Kempen Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I just tried to get solid server (a database engine) for Linux to work on 2.2-SNAP-960801. When I run solinst (or any of the = supplied binaries.) it just exits after having created a funny directory, ie '=F8=D6=BF=EF' (I hope this translates well through mail). Url: http://www.solidtech.com ftp: ftp://ftp.solidtech.com/pub/demos/2.1/ss21lux.zip Here is a ktrace dump of running solinst: 14521 ktrace RET ktrace 0 14521 ktrace CALL mmap(0,0x1000,0x3,0x1002,0xffffffff,0,0,0) 14521 ktrace RET mmap 134324224/0x801a000 14521 ktrace CALL break(0x5000) 14521 ktrace RET break 0 14521 ktrace CALL break(0x6000) 14521 ktrace RET break 0 14521 ktrace CALL execve(0xefbfd1dc,0xefbfd63c,0xefbfd644) 14521 ktrace NAMI "/bin/solinst" 14521 ktrace RET execve -1 errno 2 No such file or directory 14521 ktrace CALL execve(0xefbfd1dc,0xefbfd63c,0xefbfd644) 14521 ktrace NAMI "/usr/bin/solinst" 14521 ktrace RET execve -1 errno 2 No such file or directory 14521 ktrace CALL execve(0xefbfd1dc,0xefbfd63c,0xefbfd644) 14521 ktrace NAMI "/usr2/local/bin/solinst" 14521 ktrace RET execve -1 errno 2 No such file or directory 14521 ktrace CALL execve(0xefbfd1dc,0xefbfd63c,0xefbfd644) 14521 ktrace NAMI "/usr2/X11R6/bin/solinst" 14521 ktrace RET execve -1 errno 2 No such file or directory 14521 ktrace CALL execve(0xefbfd1dc,0xefbfd63c,0xefbfd644) 14521 ktrace NAMI "/usr/games/solinst" 14521 ktrace RET execve -1 errno 2 No such file or directory 14521 ktrace CALL execve(0xefbfd1dc,0xefbfd63c,0xefbfd644) 14521 ktrace NAMI "/usr2/local/X11/bin/solinst" 14521 ktrace RET execve -1 errno 2 No such file or directory 14521 ktrace CALL execve(0xefbfd1dc,0xefbfd63c,0xefbfd644) 14521 ktrace NAMI "/usr2/local/mh/bin/solinst" 14521 ktrace RET execve -1 errno 2 No such file or directory 14521 ktrace CALL execve(0xefbfd1dc,0xefbfd63c,0xefbfd644) 14521 ktrace NAMI "/usr/local/pbmplus/bin/solinst" 14521 ktrace RET execve -1 errno 2 No such file or directory 14521 ktrace CALL execve(0xefbfd1dc,0xefbfd63c,0xefbfd644) 14521 ktrace NAMI "/usr/local/games/bin/solinst" 14521 ktrace RET execve -1 errno 2 No such file or directory 14521 ktrace CALL execve(0xefbfd1dc,0xefbfd63c,0xefbfd644) 14521 ktrace NAMI "/usr/local/postgres95/bin/solinst" 14521 ktrace RET execve -1 errno 2 No such file or directory 14521 ktrace CALL execve(0xefbfd1dc,0xefbfd63c,0xefbfd644) 14521 ktrace NAMI "/usr/local/java/bin/solinst" 14521 ktrace RET execve -1 errno 2 No such file or directory 14521 ktrace CALL execve(0xefbfd1dc,0xefbfd63c,0xefbfd644) 14521 ktrace NAMI "/usr3/teTeX/bin/solinst" 14521 ktrace RET execve -1 errno 2 No such file or directory 14521 ktrace CALL execve(0xefbfd1dc,0xefbfd63c,0xefbfd644) 14521 ktrace NAMI "/home/marc/bin/solinst" 14521 ktrace RET execve -1 errno 2 No such file or directory 14521 ktrace CALL execve(0xefbfd1dc,0xefbfd63c,0xefbfd644) 14521 ktrace NAMI "./solinst" 14521 solinst RET execve 0 14521 solinst CALL mkdir(0xefbfd5cc,0xefbfd5d4) 14521 solinst NAMI "=F8=D6=BF=EF" 14521 solinst RET mkdir 0 14521 solinst CALL ktrace(0xefbfd5cc,0xefbfd5d4,0xefbfd6f8,0) 14521 solinst RET ktrace -1 errno 21 Is a directory 14521 solinst CALL ktrace(0xefbfcd38,0x8024c2c,0x3000,0xefbfcd4c) 14521 solinst RET ktrace -1 errno 2 No such file or directory 14521 solinst CALL ktrace(0xefbfcc6c,0x8024c2c,0x3000,0xefbfcc80) 14521 solinst RET ktrace -1 errno 2 No such file or directory 14521 solinst CALL old.sigvec(0xefbfbc0c,0x80233b5,0x1) 14521 solinst RET old.sigvec -1 errno 22 Invalid argument 14521 solinst CALL ktrace(0xefbfbbbc,0x8024c2c,0x3000,0xefbfbbd0) 14521 solinst RET ktrace -1 errno 2 No such file or directory 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL write(0xefbfbc78,0x80233fe,0x1) 14521 solinst RET write -1 errno 9 Bad file descriptor 14521 solinst CALL exit(0xefbfcce0) I hope this means something to someone. = Does anyone have a solution, short from nagging them about support for FreeBSD, which I already did :) Regards, Marc. ---------------------------------------------------- Marc van Kempen BowTie Technology = Email: marc@bowtie.nl WWW & Databases tel. +31 40 2 43 20 65 = fax. +31 40 2 44 21 86 http://www.bowtie.nl ---------------------------------------------------- From owner-freebsd-current Fri Oct 11 08:30:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA22611 for current-outgoing; Fri, 11 Oct 1996 08:30:38 -0700 (PDT) Received: from walkabout.asstdc.com.au (imb@walkabout.asstdc.com.au [202.12.127.73]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA22594 for ; Fri, 11 Oct 1996 08:30:30 -0700 (PDT) Received: (from imb@localhost) by walkabout.asstdc.com.au (8.7.6/BSD4.4) id BAA00199 Sat, 12 Oct 1996 01:29:39 +1000 (EST) From: michael butler Message-Id: <199610111529.BAA00199@walkabout.asstdc.com.au> Subject: Re: 3c589b + ep driver To: nao@sbl.cl.nec.co.jp (Naoki Hamada) Date: Sat, 12 Oct 1996 01:29:39 +1000 (EST) Cc: current@freebsd.org In-Reply-To: <199610090426.NAA20434@sirius.sbl.cl.nec.co.jp> from Naoki Hamada at "Oct 9, 96 01:26:51 pm" X-Comment: Phone 0419-240-180, International +61-419-240-180 X-Comment: finger imb@asstdc.com.au for PGP public key 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I found that the ep driver does not properly handle commands which > take time more than a I/O cycle. What about the following patch? (This > patch is 961006-SNAP based. Still applicable to the current, I hope.) In your patch, you've moved some of the spin-loops to a position immediately after the command which requires the wait. Since there is often some code that is run between it and the next time we need to talk to the card, it's more efficient to do those calculations first and then wait for the card to become ready - it may actually be ready by then and we've constructively used the time we would have otherwise have spent waiting for it. In this case it doesn't change things very much because the delays are relatively short but, as a matter of efficiency, I tend to do this. I do find it confusing, however, if the spin-loop doesn't have an associated comment to document which command (possibly more than a screenful before) necessitated the wait so there's probably a balance in there somewhere .. > @@ -1289,6 +1291,7 @@ > } > all_pkt: > outw(BASE + EP_COMMAND, RX_DISCARD_TOP_PACK); > + EP_BUSY_WAIT; > /* > * recompute average packet's length, the factor used is 1/8 to go down > * and 1/32 to go up Unfortunately, my particular 589b wants the wait before the discard command else it drops link-OK and goes off into the never-never .. still trying to find out why :-( michael From owner-freebsd-current Fri Oct 11 10:16:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA12747 for current-outgoing; Fri, 11 Oct 1996 10:16:11 -0700 (PDT) Received: from red.jnx.com (red.jnx.com [208.197.169.254]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA12733; Fri, 11 Oct 1996 10:16:06 -0700 (PDT) Received: (from root@localhost) by red.jnx.com (8.7.6/8.7.3) id KAA04306; Fri, 11 Oct 1996 10:15:11 -0700 (PDT) Date: Fri, 11 Oct 1996 10:15:11 -0700 (PDT) From: Paul Traina Message-Id: <199610111715.KAA04306@red.jnx.com> To: current@freebsd.org Subject: recent kernel panics in the vm system Cc: dyson@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John, Have you received reports of kernel instability in -current as of Oct 10th? I'm seeing a number of panics, and they all started in the last 2 days. Paul p.s. What would you like for me to debug? From owner-freebsd-current Fri Oct 11 10:52:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA14294 for current-outgoing; Fri, 11 Oct 1996 10:52:31 -0700 (PDT) Received: from dyson.iquest.net ([198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA14289; Fri, 11 Oct 1996 10:52:27 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id MAA03838; Fri, 11 Oct 1996 12:51:35 -0500 (EST) From: John Dyson Message-Id: <199610111751.MAA03838@dyson.iquest.net> Subject: Re: recent kernel panics in the vm system To: pst@jnx.com (Paul Traina) Date: Fri, 11 Oct 1996 12:51:35 -0500 (EST) Cc: current@FreeBSD.org, dyson@FreeBSD.org In-Reply-To: <199610111715.KAA04306@red.jnx.com> from "Paul Traina" at Oct 11, 96 10:15:11 am Reply-To: dyson@FreeBSD.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > John, > Have you received reports of kernel instability in -current as of Oct 10th? > I'm seeing a number of panics, and they all started in the last 2 days. > The only problem that is severe that I know of (right now -- might have forgotten though) is the PCB hashing thing. I would love to see a traceback so we can narrow things down. The VM code itself should be fairly stable, but a bit slow for low level benchmarks. John From owner-freebsd-current Fri Oct 11 10:57:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA14485 for current-outgoing; Fri, 11 Oct 1996 10:57:19 -0700 (PDT) Received: from red.jnx.com (red.jnx.com [208.197.169.254]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA14464; Fri, 11 Oct 1996 10:56:30 -0700 (PDT) Received: from base.jnx.com (base.jnx.com [208.197.169.238]) by red.jnx.com (8.7.6/8.7.3) with ESMTP id KAA00818; Fri, 11 Oct 1996 10:55:51 -0700 (PDT) Received: from base.jnx.com (localhost.jnx.com [127.0.0.1]) by base.jnx.com (8.7.6/8.7.3) with ESMTP id KAA01433; Fri, 11 Oct 1996 10:55:50 -0700 (PDT) Message-Id: <199610111755.KAA01433@base.jnx.com> To: dyson@FreeBSD.org cc: current@FreeBSD.org Subject: Re: recent kernel panics in the vm system In-reply-to: Your message of "Fri, 11 Oct 1996 12:51:35 CDT." <199610111751.MAA03838@dyson.iquest.net> Date: Fri, 11 Oct 1996 10:55:50 -0700 From: Paul Traina Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I found at least two bugs in my recent tcp/socket changes, but those don't seem to be the cause of my recent crashes. I wasn't aware there was any unstability with the PCB hashing, I'll look there next, thanks. Paul From: John Dyson Subject: Re: recent kernel panics in the vm system > > John, > Have you received reports of kernel instability in -current as of Oct 10th? > I'm seeing a number of panics, and they all started in the last 2 days. > The only problem that is severe that I know of (right now -- might have forgotten though) is the PCB hashing thing. I would love to see a traceback so we can narrow things down. The VM code itself should be fairly stable, but a bit slow for low level benchmarks. John From owner-freebsd-current Fri Oct 11 10:59:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA14596 for current-outgoing; Fri, 11 Oct 1996 10:59:55 -0700 (PDT) Received: from peedub.gj.org (newpc.muc.ditec.de [194.120.126.33]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA14584 for ; Fri, 11 Oct 1996 10:59:34 -0700 (PDT) Received: from peedub.gj.org (localhost [127.0.0.1]) by peedub.gj.org (8.7.6/8.6.9) with ESMTP id TAA05925 for ; Fri, 11 Oct 1996 19:57:24 GMT Message-Id: <199610111957.TAA05925@peedub.gj.org> X-Mailer: exmh version 1.6.7 5/3/96 To: freebsd-current@freebsd.org Subject: invalid return value from sysctl_kern_proc ? From: Gary Jennejohn Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Oct 1996 19:57:23 +0000 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk here's a fragment of code fom sysctl_kern_proc (/sys/kern/kern_proc.c) if (oidp->oid_number == KERN_PROC_PID) { if (namelen != 1) return (EINVAL); p = pfind((pid_t)name[0]); if (!p) return (0); ^^^^^^ shouldn't that be ESRCH ? I ask because sysctl isn't returning an error when I try to get the proc struct for a non-existent process. Seems to me that it should. -------- Gary Jennejohn Home - Gary.Jennejohn@munich.netsurf.de Work - gjennejohn@frt.dec.com From owner-freebsd-current Fri Oct 11 11:01:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA14767 for current-outgoing; Fri, 11 Oct 1996 11:01:42 -0700 (PDT) Received: from dyson.iquest.net ([198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA14759; Fri, 11 Oct 1996 11:01:38 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id NAA03860; Fri, 11 Oct 1996 13:01:19 -0500 (EST) From: John Dyson Message-Id: <199610111801.NAA03860@dyson.iquest.net> Subject: Re: recent kernel panics in the vm system To: pst@jnx.com (Paul Traina) Date: Fri, 11 Oct 1996 13:01:19 -0500 (EST) Cc: dyson@FreeBSD.org, current@FreeBSD.org In-Reply-To: <199610111755.KAA01433@base.jnx.com> from "Paul Traina" at Oct 11, 96 10:55:50 am Reply-To: dyson@FreeBSD.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > I found at least two bugs in my recent tcp/socket changes, but those don't > seem to be the cause of my recent crashes. I wasn't aware there was any > unstability with the PCB hashing, I'll look there next, thanks. > Excuse me!!! I didn't mean PCB hashing, I meant the SYN flood thing... Sorry!!!! John From owner-freebsd-current Fri Oct 11 11:09:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA15093 for current-outgoing; Fri, 11 Oct 1996 11:09:49 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA15087; Fri, 11 Oct 1996 11:09:46 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id LAA29261; Fri, 11 Oct 1996 11:09:37 -0700 (PDT) Message-Id: <199610111809.LAA29261@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Paul Traina cc: dyson@FreeBSD.org, current@FreeBSD.org Subject: Re: recent kernel panics in the vm system In-reply-to: Your message of "Fri, 11 Oct 1996 10:55:50 PDT." <199610111755.KAA01433@base.jnx.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 11 Oct 1996 11:09:37 -0700 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >I found at least two bugs in my recent tcp/socket changes, but those don't >seem to be the cause of my recent crashes. I wasn't aware there was any >unstability with the PCB hashing, I'll look there next, thanks. > >Paul > > From: John Dyson > Subject: Re: recent kernel panics in the vm system > > > > John, > > Have you received reports of kernel instability in -current as of Oct 10th? > > I'm seeing a number of panics, and they all started in the last 2 days. > > > The only problem that is severe that I know of (right now -- might have > forgotten though) is the PCB hashing thing. I would love to see a > traceback so we can narrow things down. The VM code itself should be > fairly stable, but a bit slow for low level benchmarks. John is a bit confused, I think. There is nothing wrong with the PCB hashing as far as I'm aware. The problem is with the SYN-flood drop code dereferencing a NULL. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Fri Oct 11 11:11:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA15182 for current-outgoing; Fri, 11 Oct 1996 11:11:36 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA15174; Fri, 11 Oct 1996 11:11:34 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id LAA02199; Fri, 11 Oct 1996 11:11:32 -0700 (PDT) To: dyson@FreeBSD.org cc: pst@jnx.com (Paul Traina), current@FreeBSD.org Subject: Re: recent kernel panics in the vm system In-reply-to: Your message of "Fri, 11 Oct 1996 12:51:35 CDT." <199610111751.MAA03838@dyson.iquest.net> Date: Fri, 11 Oct 1996 11:11:32 -0700 Message-ID: <2197.845057492@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I thought that everyone was complaining that Paul's SYN wait fixes had hosed the show, or are we talking about something else? FWIW, my system is now crashing too, but without any crash dumps being left behind for debugging. :( Jordan From owner-freebsd-current Fri Oct 11 11:33:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA16472 for current-outgoing; Fri, 11 Oct 1996 11:33:15 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA16467; Fri, 11 Oct 1996 11:33:13 -0700 (PDT) Received: from red.jnx.com (red.jnx.com [208.197.169.254]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id LAA14886 ; Fri, 11 Oct 1996 11:33:05 -0700 (PDT) Received: from base.jnx.com (base.jnx.com [208.197.169.238]) by red.jnx.com (8.7.6/8.7.3) with ESMTP id LAA03584; Fri, 11 Oct 1996 11:31:07 -0700 (PDT) Received: from base.jnx.com (localhost.jnx.com [127.0.0.1]) by base.jnx.com (8.7.6/8.7.3) with ESMTP id LAA00346; Fri, 11 Oct 1996 11:31:07 -0700 (PDT) Message-Id: <199610111831.LAA00346@base.jnx.com> To: dyson@FreeBSD.org cc: current@FreeBSD.org Subject: Re: recent kernel panics in the vm system In-reply-to: Your message of "Fri, 11 Oct 1996 13:01:19 CDT." <199610111801.NAA03860@dyson.iquest.net> Date: Fri, 11 Oct 1996 11:31:07 -0700 From: Paul Traina Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk OK, good. Thanks. From: John Dyson Subject: Re: recent kernel panics in the vm system > > I found at least two bugs in my recent tcp/socket changes, but those don't > seem to be the cause of my recent crashes. I wasn't aware there was any > unstability with the PCB hashing, I'll look there next, thanks. > Excuse me!!! I didn't mean PCB hashing, I meant the SYN flood thing... Sorry!!!! John From owner-freebsd-current Fri Oct 11 11:35:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA16746 for current-outgoing; Fri, 11 Oct 1996 11:35:54 -0700 (PDT) Received: from red.jnx.com (red.jnx.com [208.197.169.254]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA16450; Fri, 11 Oct 1996 11:32:10 -0700 (PDT) Received: from base.jnx.com (base.jnx.com [208.197.169.238]) by red.jnx.com (8.7.6/8.7.3) with ESMTP id LAA03588; Fri, 11 Oct 1996 11:31:37 -0700 (PDT) Received: from base.jnx.com (localhost.jnx.com [127.0.0.1]) by base.jnx.com (8.7.6/8.7.3) with ESMTP id LAA00370; Fri, 11 Oct 1996 11:31:37 -0700 (PDT) Message-Id: <199610111831.LAA00370@base.jnx.com> To: dg@root.com cc: dyson@FreeBSD.org, current@FreeBSD.org Subject: Re: recent kernel panics in the vm system In-reply-to: Your message of "Fri, 11 Oct 1996 11:09:37 PDT." <199610111809.LAA29261@root.com> Date: Fri, 11 Oct 1996 11:31:37 -0700 From: Paul Traina Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Right, I screwed the pooch with a last-microsecond change in the code. :-( Sigh. I'm committing fixes in a few minutes. From: David Greenman Subject: Re: recent kernel panics in the vm system >I found at least two bugs in my recent tcp/socket changes, but those don't >seem to be the cause of my recent crashes. I wasn't aware there was any >unstability with the PCB hashing, I'll look there next, thanks. > >Paul > > From: John Dyson > Subject: Re: recent kernel panics in the vm system > > > > John, > > Have you received reports of kernel instability in -current as of Oct 10 >>th? > > I'm seeing a number of panics, and they all started in the last 2 days. > > > The only problem that is severe that I know of (right now -- might have > forgotten though) is the PCB hashing thing. I would love to see a > traceback so we can narrow things down. The VM code itself should be > fairly stable, but a bit slow for low level benchmarks. John is a bit confused, I think. There is nothing wrong with the PCB hashing as far as I'm aware. The problem is with the SYN-flood drop code dereferencing a NULL. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Fri Oct 11 11:37:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA16886 for current-outgoing; Fri, 11 Oct 1996 11:37:13 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA16868; Fri, 11 Oct 1996 11:36:58 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id UAA00409; Fri, 11 Oct 1996 20:36:14 +0200 (MET DST) To: Gary Jennejohn cc: freebsd-current@freebsd.org Subject: Re: invalid return value from sysctl_kern_proc ? In-reply-to: Your message of "Fri, 11 Oct 1996 19:57:23 -0000." <199610111957.TAA05925@peedub.gj.org> Date: Fri, 11 Oct 1996 20:36:14 +0200 Message-ID: <407.845058974@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199610111957.TAA05925@peedub.gj.org>, Gary Jennejohn writes: >here's a fragment of code fom sysctl_kern_proc (/sys/kern/kern_proc.c) > > if (oidp->oid_number == KERN_PROC_PID) { > if (namelen != 1) > return (EINVAL); > p = pfind((pid_t)name[0]); > if (!p) > return (0); > ^^^^^^ shouldn't that be ESRCH ? > >I ask because sysctl isn't returning an error when I try to get the proc >struct for a non-existent process. Seems to me that it should. Well, it does, you don't get any data back. sysctl doesn't return error for things in the data domain it handles, only errors about the handling. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Fri Oct 11 11:40:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA17096 for current-outgoing; Fri, 11 Oct 1996 11:40:05 -0700 (PDT) Received: from red.jnx.com (red.jnx.com [208.197.169.254]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA17018; Fri, 11 Oct 1996 11:39:59 -0700 (PDT) Received: from base.jnx.com (base.jnx.com [208.197.169.238]) by red.jnx.com (8.7.6/8.7.3) with ESMTP id LAA03876; Fri, 11 Oct 1996 11:39:18 -0700 (PDT) Received: from base.jnx.com (localhost.jnx.com [127.0.0.1]) by base.jnx.com (8.7.6/8.7.3) with ESMTP id LAA00439; Fri, 11 Oct 1996 11:39:17 -0700 (PDT) Message-Id: <199610111839.LAA00439@base.jnx.com> To: Bill Fenner cc: bde@freebsd.org, dg@root.com, olah@freebsd.org, wollman@freebsd.org, current@freebsd.org Subject: Re: Partial review of SYN attack patch In-reply-to: Your message of "Thu, 10 Oct 1996 17:01:13 PDT." <96Oct10.170123pdt.177476@crevenia.parc.xerox.com> Date: Fri, 11 Oct 1996 11:39:17 -0700 From: Paul Traina Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The recent crashes were because of a typo in my code, sorry, at the last second I optimized out something I shouldn't have. The idea was to call tcp_drop() and then recreate a new socket, rather than reuse the old one. When I cleaned up the code to go to dropablereq() in socket, I fat-fingered the call to create a new connection. sodropablereq() has a 1/n chance of returning null so that the "new" connection is a canidate for dropable requests too. This code was extensively tested under -current and a similar patch was tested under 2.1.5, but at the last second, I restructured things, which is why this happened. Big regrets, fix on the way. Paul From: Bill Fenner Subject: Partial review of SYN attack patch Karl Denninger's crashes seem to be occurring because of a bug in the SYN attack patch in rev 1.52 of tcp_input.c: so2 = sonewconn(so, 0); if (so2 == 0) { tcpstat.tcps_listendrop++; so2 = sodropablereq(so); if (so2) tcp_drop(sototcpcb(so2), ETIMEDOUT); else goto drop; } so = so2; /* * This is ugly, but .... * * Mark socket as temporary until we're * committed to keeping it. The code at * ``drop'' and ``dropwithreset'' check the * flag dropsocket to see if the temporary * socket created here should be discarded. * We mark the socket as discardable until * we're committed to it below in TCPS_LISTEN. */ dropsocket++; inp = (struct inpcb *)so->so_pcb; inp->inp_laddr = ti->ti_dst; inp->inp_lport = ti->ti_dport; in_pcbrehash(inp); tcp_drop: - Sets the socket errno - Frees the pcb - Frees the inpcb (which doesn't free the socket because of SS_NOFDREF) But the code goes on to use the socket and quickly deferences the NULL inpcb. This code should probably be either if (so2) { tcp_drop(sototcpcb(so2), ETIMEDOUT); tcp_attach(so2); } else goto drop; or if (so2) { so2->so_flags &= ~SS_NOFDREF; tcp_drop(sototcpcb(so2), ETIMEDOUT); so2 = sonewconn(so, 0); if (so2 == 0) /* can't happen? */ goto drop; } else goto drop; The first has the disadvantage that tcp_attach is static in a different file, but has the advantage of being able to reuse the socket. The second has the disadvantage of destroying and recreating the socket. A third option might actually be if (so2 == 0) goto drop; After all, we're just about to update inp->inp_laddr and inp->inp_lport, and if in_pcbrehash(inp) can handle inp's laddr and lport changing (as opposed to being new) then this is probably the best option. Of course, there's probably more to it than that, perhaps flags got set in the tcpcb by the previous SYN, or there might have been data included, so it's probably not possible to reuse the tcpcb like this. It looks like the original code was trying to reuse the socket so2, without realizing that tcp_drop -> tcp_close calls in_pcbdetach? Did anyone actually test this code under attack? It seems like if sodropablereq() returns a socket, then this code has no chance of not dereferencing NULL. Bill From owner-freebsd-current Fri Oct 11 14:05:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA25401 for current-outgoing; Fri, 11 Oct 1996 14:05:41 -0700 (PDT) Received: from peedub.gj.org (newpc.muc.ditec.de [194.120.126.33]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA25392 for ; Fri, 11 Oct 1996 14:05:34 -0700 (PDT) Received: from peedub.gj.org (localhost [127.0.0.1]) by peedub.gj.org (8.7.6/8.6.9) with ESMTP id XAA06498; Fri, 11 Oct 1996 23:04:20 GMT Message-Id: <199610112304.XAA06498@peedub.gj.org> X-Mailer: exmh version 1.6.7 5/3/96 To: Poul-Henning Kamp cc: freebsd-current@freebsd.org Subject: Re: invalid return value from sysctl_kern_proc ? Reply-To: Gary Jennejohn In-reply-to: Your message of "Fri, 11 Oct 1996 20:36:14 +0200." <407.845058974@critter.tfs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Oct 1996 23:04:19 +0000 From: Gary Jennejohn Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp writes: >In message <199610111957.TAA05925@peedub.gj.org>, Gary Jennejohn writes: [cruft deleted] >>I ask because sysctl isn't returning an error when I try to get the proc >>struct for a non-existent process. Seems to me that it should. > >Well, it does, you don't get any data back. > >sysctl doesn't return error for things in the data domain it handles, >only errors about the handling. > thanks alot, Poul-Henning ! this means that this code from kvm_getprocs in libkvm is wrong. if (size % sizeof(struct kinfo_proc) != 0) { _kvm_err(kd, kd->program, "proc size mismatch (%d total, %d chunks)", size, sizeof(struct kinfo_proc)); return (0); } sysctl will set size = 0 if it can't find the requested data. This should probably read if (!size || size % sizeof(struct kinfo_proc) != 0) { ^^^^^^^ I used the code from libkvm, which didn't work as I expected it to. --- Gary Jennejohn Home - Gary.Jennejohn@munich.netsurf.de Work - gjennejohn@frt.dec.com From owner-freebsd-current Fri Oct 11 14:16:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA25945 for current-outgoing; Fri, 11 Oct 1996 14:16:32 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA25940 for ; Fri, 11 Oct 1996 14:16:29 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id OAA29959; Fri, 11 Oct 1996 14:16:17 -0700 (PDT) Message-Id: <199610112116.OAA29959@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Gary Jennejohn cc: Poul-Henning Kamp , freebsd-current@FreeBSD.org Subject: Re: invalid return value from sysctl_kern_proc ? In-reply-to: Your message of "Fri, 11 Oct 1996 23:04:19 -0000." <199610112304.XAA06498@peedub.gj.org> From: David Greenman Reply-To: dg@root.com Date: Fri, 11 Oct 1996 14:16:17 -0700 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Poul-Henning Kamp writes: >>In message <199610111957.TAA05925@peedub.gj.org>, Gary Jennejohn writes: >[cruft deleted] >>>I ask because sysctl isn't returning an error when I try to get the proc >>>struct for a non-existent process. Seems to me that it should. >> >>Well, it does, you don't get any data back. >> >>sysctl doesn't return error for things in the data domain it handles, >>only errors about the handling. >> > >thanks alot, Poul-Henning ! > >this means that this code from kvm_getprocs in libkvm is wrong. > > if (size % sizeof(struct kinfo_proc) != 0) { > _kvm_err(kd, kd->program, > "proc size mismatch (%d total, %d chunks)", > size, sizeof(struct kinfo_proc)); > return (0); > } > >sysctl will set size = 0 if it can't find the requested data. This should >probably read > > if (!size || size % sizeof(struct kinfo_proc) != 0) { > ^^^^^^^ > >I used the code from libkvm, which didn't work as I expected it to. Um, well, if one were going to change it, one wouldn't want the error message to be the same in both cases. It probably also shouldn't be fatal since that will cause ps(8) to break most of the time on busy machines. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Fri Oct 11 14:30:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA26733 for current-outgoing; Fri, 11 Oct 1996 14:30:25 -0700 (PDT) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA26716 for ; Fri, 11 Oct 1996 14:30:18 -0700 (PDT) Received: (from uucp@localhost) by frmug.org (8.6.8/8.6.9) with UUCP id XAA05133 for current@FreeBSD.org; Fri, 11 Oct 1996 23:30:06 +0200 Received: from localhost (localhost [127.0.0.1]) by xp11.frmug.org (8.7.6/8.7.3/xp11-uucp-1.1) with ESMTP id VAA01615 for ; Fri, 11 Oct 1996 21:05:38 +0200 (MET DST) Message-Id: <199610111905.VAA01615@xp11.frmug.org> To: current@FreeBSD.org Subject: gcc's bug. please comment Date: Fri, 11 Oct 1996 21:05:36 +0200 From: "Philippe Charnier" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hello, A friend found a bug in gcc-2.7.2.1. The following program fails on i386 architecture (both FreeBSD and solaris-x86) and works as expected on sparc (both sunos and solaris2.5.1) and on hp (hp-ux9.07). As I'm not on the gcc-bug list, please comment before I report the bug. This afternoon I sent a bug report to Sun but it was before trying on FreeBSD. The output should be `1 2' but it is `2 1' on i386 computers. Here is the code: ----------mypb2.c----------------- #include #include main() { FILE *fic; int a[2][50], i = 0; fic=fopen("mypb2.csv","r"); fscanf(fic, "%d;%d", &a[1][i++], &a[1][i++]); i = 0; while (i < 2) printf("%d ", a[1][i++]); printf("\n"); fclose(fic); } ---------------------------------- ---------------mypb2.csv---------- 1;2 ---------------------------------- For those that do not have a solaris-2.5 box to test on, here is the assembly output of the compiler. .file "mypb2.c" .version "01.01" gcc2_compiled.: .section .rodata .LC0: .string "r" .LC1: .string "mypb2.csv" .LC2: .string "%d;%d" .LC3: .string "%d " .LC4: .string "\n" .text .align 4 .globl main .type main,@function main: pushl %ebp movl %esp,%ebp subl $408,%esp movl $0,-408(%ebp) pushl $.LC0 pushl $.LC1 call fopen addl $8,%esp movl %eax,%eax movl %eax,-4(%ebp) leal -404(%ebp),%eax movl -408(%ebp),%edx movl %edx,%ecx leal 0(,%ecx,4),%edx leal 200(%edx),%ecx addl %ecx,%eax pushl %eax incl -408(%ebp) leal -404(%ebp),%eax movl -408(%ebp),%edx movl %edx,%ecx leal 0(,%ecx,4),%edx leal 200(%edx),%ecx addl %ecx,%eax pushl %eax incl -408(%ebp) pushl $.LC2 movl -4(%ebp),%eax pushl %eax call fscanf addl $16,%esp movl $0,-408(%ebp) .L2: cmpl $1,-408(%ebp) jle .L4 jmp .L3 .align 4 .L4: movl -408(%ebp),%eax movl -204(%ebp,%eax,4),%edx pushl %edx incl -408(%ebp) pushl $.LC3 call printf addl $8,%esp jmp .L2 .align 4 .L3: pushl $.LC4 call printf addl $4,%esp movl -4(%ebp),%eax pushl %eax call fclose addl $4,%esp .L1: leave ret .Lfe1: .size main,.Lfe1-main .ident "GCC: (GNU) 2.7.2.1" ------ ------ Philippe Charnier charnier@lirmm.fr (smtp) charnier@xp11.frmug.org (uucp) ``a PC not running FreeBSD is like a venusian with no tentacles'' ------------------------------------------------------------------------ From owner-freebsd-current Fri Oct 11 14:35:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA27021 for current-outgoing; Fri, 11 Oct 1996 14:35:11 -0700 (PDT) Received: from noc.msc.edu (noc.msc.edu [137.66.12.254]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA27006 for ; Fri, 11 Oct 1996 14:35:04 -0700 (PDT) Received: from uc.msc.edu by noc.msc.edu (5.65/MSC/v3.0.1(920324)) id AA24711; Fri, 11 Oct 96 16:32:50 -0500 Received: from fergus-17.dialup.prtel.com by uc.msc.edu (5.65/MSC/v3.0z(901212)) id AA09227; Fri, 11 Oct 96 01:36:28 -0500 Received: (from alk@localhost) by compound.Think.COM (8.7.6/8.7.3) id BAA08922; Fri, 11 Oct 1996 01:36:23 -0500 (CDT) Date: Fri, 11 Oct 1996 01:36:23 -0500 (CDT) From: Tony Kimball Message-Id: <199610110636.BAA08922@compound.Think.COM> To: rkw@dataplex.net Cc: current@freebsd.org Subject: Re: .depend Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Quoth Richard Wackerbarth on Tue, 8 October: : Why change "make"? Because it sucks? (Sorry, couldn't resist.) From owner-freebsd-current Fri Oct 11 15:11:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA29397 for current-outgoing; Fri, 11 Oct 1996 15:11:38 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA29387 for ; Fri, 11 Oct 1996 15:11:33 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.6/8.7.3) with SMTP id PAA03455; Fri, 11 Oct 1996 15:08:48 -0700 (PDT) Message-ID: <325EC4F5.167EB0E7@whistle.com> Date: Fri, 11 Oct 1996 15:06:45 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Philippe Charnier CC: current@FreeBSD.org Subject: Re: gcc's bug. please comment References: <199610111905.VAA01615@xp11.frmug.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Philippe Charnier wrote: > > Hello, > > A friend found a bug in gcc-2.7.2.1. The following program fails on > i386 architecture (both FreeBSD and solaris-x86) and works as expected > on sparc (both sunos and solaris2.5.1) and on hp (hp-ux9.07). As I'm > not on the gcc-bug list, please comment before I report the bug. This > afternoon I sent a bug report to Sun but it was before trying on > FreeBSD. > > The output should be `1 2' but it is `2 1' on i386 computers. > Here is the code: This is not a bug. the C standard specifically does not define the order of evaluation in arguments to a function. for eas of programming, they are usually eveluated from right to left, (giving 2 1) but sometimes they are evaluated left to right. arguments to a function are NOT THE SAME as a coma separated list of statements, which are DEFINED to evaluate from left to right. Thus is is not goo dC to do operations on function arguments that have side-effects as the order of evaluation can vary. > fic=fopen("mypb2.csv","r"); > fscanf(fic, "%d;%d", &a[1][i++], &a[1][i++]); this will assign a[1][1] before filling out a[1][0] The reasoning was that by the time this became a noticed problem there were already too many machines doing it each way. julian From owner-freebsd-current Fri Oct 11 17:15:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA08555 for current-outgoing; Fri, 11 Oct 1996 17:15:59 -0700 (PDT) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA08550 for ; Fri, 11 Oct 1996 17:15:57 -0700 (PDT) Received: from pauling.salk.edu (pauling [198.202.70.108]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id RAA23290; Fri, 11 Oct 1996 17:15:28 -0700 (PDT) Date: Fri, 11 Oct 1996 17:15:31 -0700 (PDT) From: Tom Bartol To: Hidetoshi Shimokawa cc: dfr@render.com, current@FreeBSD.ORG Subject: Re: NFS weirdness in -current In-Reply-To: <9764.844967087@sat.t.u-tokyo.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 11 Oct 1996, Hidetoshi Shimokawa wrote: > bartol> Yes, it does sound like that problem now that you point it out. > bartol> > bartol> Hidetoshi, is there anything I can do to help out? > > I already made a patch and send it to freebsd-lite2 list. > (I guess you can find it by mailing list archive search, > keyword is "Delayed write patch".) > > Doug will commit it to -current tomorrow(it may depends on time zone :-). > If you cannot wait it, I will send you the patch. > > Please try the patch. > > /\ Hidetoshi Shimokawa > \/ simokawa@sat.t.u-tokyo.ac.jp > PGP public key: finger -l simokawa@sat.t.u-tokyo.ac.jp > Hi, Sorry for the delay in getting back you on trying this patch. I see that the patch has already been committed, great! Here are my results: 1) the patch fixes the anomalous behavior -- nfs operations no longer block other nfs operations when they shouldn't. 2) with vfs.nfs.dwrite=1, nfs reads go at 400KBps and nfs writes go at 600KBps! Not too shabby! During a write of a file called "ick", do an "ls -al ick" in another xterm shows the file's size increasing in large chunky, and infrequent increments. 3) with vfs.nfs.dwrite=0, nfs reads go at 250KBps and nfs writes go at 250KBps. "ls -al ick" shows the file's size increasing smoothly over time. 4) with 2.2-960801-SNAP we got 600KBps reads and 300KBps writes so a few things have changed in -current. "ls -al ick" shows file's size increasing somewhat smoothly, sort of half-way between behavior described in 2 and 3 above. In the tests above we NFS mounted a filesystem served by an Auspex NS200 running Auspex kernel 1.8M1Z1 (a SunOS 4.1.4 variant). We were reading or writing a 10MB file over a dedicated switched 10BT ethernet connection to the Auspex. Hope this helps, Tom From owner-freebsd-current Fri Oct 11 19:14:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA14996 for current-outgoing; Fri, 11 Oct 1996 19:14:39 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA14989; Fri, 11 Oct 1996 19:14:34 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.0/8.8.Beta.3) with SMTP id VAA27942; Fri, 11 Oct 1996 21:14:25 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.15) id ; Fri, 11 Oct 96 21:14 CDT Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.Beta.6/8.8.Beta.3) id VAA01365; Fri, 11 Oct 1996 21:14:24 -0500 (CDT) From: Karl Denninger Message-Id: <199610120214.VAA01365@Jupiter.Mcs.Net> Subject: Re: recent kernel panics in the vm system To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 11 Oct 1996 21:14:23 -0500 (CDT) Cc: dyson@FreeBSD.ORG, pst@jnx.com, current@FreeBSD.ORG In-Reply-To: <2197.845057492@time.cdrom.com> from "Jordan K. Hubbard" at Oct 11, 96 11:11:32 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I thought that everyone was complaining that Paul's SYN wait fixes > had hosed the show, or are we talking about something else? FWIW, > my system is now crashing too, but without any crash dumps being > left behind for debugging. :( > > Jordan > We have two issues here: 1) The SYN fixes did hose the show. We have a prelim patch in which APPEARS to be working (despite an analysis that it shouldn't); no crashes in 30 hours attributable to it (there was one, but this wasn't the cause). I understand a REAL fix has been committed and should be in tonight's SUPper. 2) We have another extant problem with NFS in -current. This one is REALLY odd. What happens is that directories become inaccessible and "pwd" fails (ie: ftpd cannot determine the current directory). The problem comes and goes without reboot or other prodding that we are able to determine. The second problem we have no good, hard evidence of a fix for. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-current Fri Oct 11 20:20:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA19892 for current-outgoing; Fri, 11 Oct 1996 20:20:19 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA19883 for ; Fri, 11 Oct 1996 20:20:14 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id MAA03815; Sat, 12 Oct 1996 12:50:03 +0930 From: Michael Smith Message-Id: <199610120320.MAA03815@genesis.atrad.adelaide.edu.au> Subject: Re: gcc's bug. please comment To: charnier@xp11.frmug.org (Philippe Charnier) Date: Sat, 12 Oct 1996 12:50:02 +0930 (CST) Cc: current@FreeBSD.org In-Reply-To: <199610111905.VAA01615@xp11.frmug.org> from "Philippe Charnier" at Oct 11, 96 09:05:36 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Philippe Charnier stands accused of saying: > > A friend found a bug in gcc-2.7.2.1. The following program fails on > i386 architecture (both FreeBSD and solaris-x86) and works as expected > on sparc (both sunos and solaris2.5.1) and on hp (hp-ux9.07). As I'm > not on the gcc-bug list, please comment before I report the bug. This > afternoon I sent a bug report to Sun but it was before trying on > FreeBSD. > > The output should be `1 2' but it is `2 1' on i386 computers. > Here is the code: > > ----------mypb2.c----------------- > #include > #include > > main() > { FILE *fic; > int a[2][50], i = 0; > > fic=fopen("mypb2.csv","r"); > fscanf(fic, "%d;%d", &a[1][i++], &a[1][i++]); Arguments to C functions are usually stacked right-to-left (this is the only way to make functions with variable numbers of arguments work sensibly)(1). Thus, the args to fscanf are evaluated right-to-left, and thus your code is working as one might expect. I would imagine that the Sun and HP compilers calculate the a indices before stacking them for the call, and thus evaluate left-to-right. To me, this implies pedantic metrics-and-clockwatching compiler design, or possibly one or more large customers with large legacy codebases which depend upon code like the snippet above. The C standard _explicitly_ forbids you from making any assumptions about the order of evaluation of function arguments, so the bug is yours. (1) Yes, I know there are other ways of doing it. No, none of them work sensibly. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Fri Oct 11 21:07:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA22557 for current-outgoing; Fri, 11 Oct 1996 21:07:50 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA22551 for ; Fri, 11 Oct 1996 21:07:44 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id VAA10254; Fri, 11 Oct 1996 21:05:44 -0700 (PDT) Message-Id: <199610120405.VAA10254@austin.polstra.com> To: jkh@time.cdrom.com Cc: perry@alpha.jpunix.com, current@FreeBSD.org Subject: Re: Alternate SUP sites? In-reply-to: <1079.845044148@time.cdrom.com> Date: Fri, 11 Oct 1996 21:05:44 -0700 From: John Polstra Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > It appears that they've all disappeared, one by one. :-( Sup3.freebsd.org == cvsup2.freebsd.org == burka.rdy.com is still running, as far as I know. 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-current Fri Oct 11 21:47:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA25073 for current-outgoing; Fri, 11 Oct 1996 21:47:47 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA25068 for ; Fri, 11 Oct 1996 21:47:45 -0700 (PDT) Received: from localhost (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with SMTP id VAA06508; Fri, 11 Oct 1996 21:45:02 -0700 Date: Fri, 11 Oct 1996 21:45:00 -0700 (PDT) From: Veggy Vinny To: Joerg Wunsch cc: FreeBSD-current users Subject: Re: Good Job guys In-Reply-To: <199610110745.JAA04373@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 11 Oct 1996, J Wunsch wrote: > As Veggy Vinny wrote: > > > networking and stuff. Anyways, is the uname -a for the -current kernel > > supposed to say SNAP-100496? > > Nope, 2.2-CURRENT. Your /sys/conf/newvers.sh is hosed. Here's the > variable assignments from my version: > > TYPE="FreeBSD" > REVISION="2.2" > BRANCH="CURRENT" I checked that and it had the same thing as yours..... Somehow I would think it's hosed if it was just the -current kernel but it also did the same thing in the SMP kernel.... Oh well, I'll see what the next kernel says. Vince From owner-freebsd-current Fri Oct 11 23:20:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA01305 for current-outgoing; Fri, 11 Oct 1996 23:20:15 -0700 (PDT) Received: from red.jnx.com (red.jnx.com [208.197.169.254]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA01299; Fri, 11 Oct 1996 23:20:13 -0700 (PDT) Received: from base.jnx.com (base.jnx.com [208.197.169.238]) by red.jnx.com (8.7.6/8.7.3) with ESMTP id XAA04154; Fri, 11 Oct 1996 23:19:42 -0700 (PDT) Received: from base.jnx.com (localhost.jnx.com [127.0.0.1]) by base.jnx.com (8.7.6/8.7.3) with ESMTP id XAA01007; Fri, 11 Oct 1996 23:19:41 -0700 (PDT) Message-Id: <199610120619.XAA01007@base.jnx.com> To: Karl Denninger cc: jkh@time.cdrom.com (Jordan K. Hubbard), dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: recent kernel panics in the vm system In-reply-to: Your message of "Fri, 11 Oct 1996 21:14:23 CDT." <199610120214.VAA01365@Jupiter.Mcs.Net> Date: Fri, 11 Oct 1996 23:19:41 -0700 From: Paul Traina Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Karl, are you using LKM's? I changed the size of the socket structure recently. From: Karl Denninger Subject: Re: recent kernel panics in the vm system > > I thought that everyone was complaining that Paul's SYN wait fixes > had hosed the show, or are we talking about something else? FWIW, > my system is now crashing too, but without any crash dumps being > left behind for debugging. :( > > Jordan > We have two issues here: 1) The SYN fixes did hose the show. We have a prelim patch in which APPEARS to be working (despite an analysis that it shouldn't); no crashes in 30 hours attributable to it (there was one, but this wasn't the cause). I understand a REAL fix has been committed and should be in tonight's SUPper. 2) We have another extant problem with NFS in -current. This one is REALLY odd. What happens is that directories become inaccessible and "pwd" fails (ie: ftpd cannot determine the current directory). The problem comes and goes without reboot or other prodding that we are able to determine. The second problem we have no good, hard evidence of a fix for. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.ne >>t/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-current Sat Oct 12 01:16:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA09389 for current-outgoing; Sat, 12 Oct 1996 01:16:36 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA09382; Sat, 12 Oct 1996 01:16:30 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id KAA03182; Sat, 12 Oct 1996 10:15:54 +0200 (MET DST) To: Gary Jennejohn cc: freebsd-current@FreeBSD.org Subject: Re: invalid return value from sysctl_kern_proc ? In-reply-to: Your message of "Fri, 11 Oct 1996 23:04:19 -0000." <199610112304.XAA06498@peedub.gj.org> Date: Sat, 12 Oct 1996 10:15:54 +0200 Message-ID: <3180.845108154@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <199610112304.XAA06498@peedub.gj.org>, Gary Jennejohn writes: >Poul-Henning Kamp writes: >>In message <199610111957.TAA05925@peedub.gj.org>, Gary Jennejohn writes: >[cruft deleted] >>>I ask because sysctl isn't returning an error when I try to get the proc >>>struct for a non-existent process. Seems to me that it should. >> >>Well, it does, you don't get any data back. >> >>sysctl doesn't return error for things in the data domain it handles, >>only errors about the handling. >> > >thanks alot, Poul-Henning ! > >this means that this code from kvm_getprocs in libkvm is wrong. > > if (size % sizeof(struct kinfo_proc) != 0) { > _kvm_err(kd, kd->program, > "proc size mismatch (%d total, %d chunks)", > size, sizeof(struct kinfo_proc)); > return (0); > } > >sysctl will set size = 0 if it can't find the requested data. This should >probably read > > if (!size || size % sizeof(struct kinfo_proc) != 0) { > ^^^^^^^ > >I used the code from libkvm, which didn't work as I expected it to. No, that would be wrong. You would get the "proc size mismatch" message then for the case of "process not found" that would be wrong. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Sat Oct 12 01:22:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA09756 for current-outgoing; Sat, 12 Oct 1996 01:22:34 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA09744; Sat, 12 Oct 1996 01:22:28 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id KAA03205; Sat, 12 Oct 1996 10:21:37 +0200 (MET DST) To: "Philippe Charnier" cc: current@FreeBSD.org Subject: Re: gcc's bug. please comment In-reply-to: Your message of "Fri, 11 Oct 1996 21:05:36 +0200." <199610111905.VAA01615@xp11.frmug.org> Date: Sat, 12 Oct 1996 10:21:36 +0200 Message-ID: <3203.845108496@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <199610111905.VAA01615@xp11.frmug.org>, "Philippe Charnier" writes: >Hello, > >A friend found a bug in gcc-2.7.2.1. The following program fails on >i386 architecture (both FreeBSD and solaris-x86) and works as expected >on sparc (both sunos and solaris2.5.1) and on hp (hp-ux9.07). As I'm >not on the gcc-bug list, please comment before I report the bug. This >afternoon I sent a bug report to Sun but it was before trying on >FreeBSD. > >The output should be `1 2' but it is `2 1' on i386 computers. >Here is the code: > >----------mypb2.c----------------- >#include >#include > >main() >{ FILE *fic; > int a[2][50], i = 0; > > fic=fopen("mypb2.csv","r"); > fscanf(fic, "%d;%d", &a[1][i++], &a[1][i++]); The order in which the i++'s get evaluated is not defined by the apocryphical writings, thus the behavior of this line is likely to depend on the parameter passing convention of the CPU. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Sat Oct 12 08:45:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA06193 for current-outgoing; Sat, 12 Oct 1996 08:45:46 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA06188 for ; Sat, 12 Oct 1996 08:45:43 -0700 (PDT) Received: from magigimmix.xs4all.nl by mail.crl.com with SMTP id AA06070 (5.65c/IDA-1.5 for ); Sat, 12 Oct 1996 08:46:25 -0700 Received: from asterix.xs4all.nl (asterix.xs4all.nl [194.109.6.11]) by magigimmix.xs4all.nl (8.7.5/XS4ALL) with ESMTP id RAA10091 for ; Sat, 12 Oct 1996 17:44:25 +0200 (MET DST) Received: from plm.xs4all.nl (uucp@localhost) by asterix.xs4all.nl (8.7.5/8.7.2) with UUCP id RAA13384 for freebsd-current@FreeBSD.ORG; Sat, 12 Oct 1996 17:38:02 +0200 (MET DST) Received: (from plm@localhost) by plm.xs4all.nl (8.7.5/8.7.3) id IAA26074; Sat, 12 Oct 1996 08:09:45 +0200 To: freebsd-current@FreeBSD.ORG Subject: Re: gcc's bug. please comment References: <8720f4pvel.fsf@totally-fudged-out-message-id> From: Peter Mutsaers Date: 12 Oct 1996 08:09:45 +0200 In-Reply-To: "Philippe Charnier"'s message of Fri, 11 Oct 1996 21:05:36 +0200 Message-Id: <87d8yon26u.fsf@plm.xs4all.nl> Lines: 24 X-Mailer: Gnus v5.2.39/Emacs 19.34 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> On Fri, 11 Oct 1996 21:05:36 +0200, "Philippe Charnier" >> said: PC> The output should be `1 2' but it is `2 1' on i386 computers. PC> Here is the code: PC> - ----------mypb2.c----------------- PC> #include PC> #include PC> main() PC> { FILE *fic; PC> int a[2][50], i = 0; PC> fic=fopen("mypb2.csv","r"); PC> fscanf(fic, "%d;%d", &a[1][i++], &a[1][i++]); You must never use a pre/post increment operator twice in one expression. The order of evaluation of function parameters is undefined, thus the answer is undefined. It is not a bug. -- Peter Mutsaers | Abcoude (Utrecht), | Trust is a good quality plm@xs4all.nl | the Netherlands | for other people to have From owner-freebsd-current Sat Oct 12 11:38:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA18135 for current-outgoing; Sat, 12 Oct 1996 11:38:30 -0700 (PDT) Received: from mail.tky007.tth.expo96.ad.jp (root@tky007.tth.expo96.ad.jp [133.246.32.58]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA18008 for ; Sat, 12 Oct 1996 11:35:49 -0700 (PDT) Received: from tky007.tth.expo96.ad.jp (masafumi@localhost [127.0.0.1]) by mail.tky007.tth.expo96.ad.jp (8.7.6/3.4W4-SMTP) with ESMTP id DAA18858; Sun, 13 Oct 1996 03:33:41 +0900 (JST) Message-Id: <199610121833.DAA18858@mail.tky007.tth.expo96.ad.jp> To: freebsd-current@freebsd.org Cc: max@wide.ad.jp Subject: IIJ-PPP patch, please review From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= X-Mailer: Mew version 1.06 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Sun_Oct_13_03:30:22_1996)--" Date: Sun, 13 Oct 1996 03:33:41 +0900 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ----Next_Part(Sun_Oct_13_03:30:22_1996)-- Content-Type: Text/Plain; charset=us-ascii Hi, Recently I found a nice modification to IIJ-PPP by Hideo NORO . With this patch applied, the auto mode (dial-on-demand mode) of IIJ-PPP doesn't require any dummy packet to be sent before the link is established. So, it's like true dial-on-demand. The features added/modified by this patch are: 1. Added two options, ``syn'' and ``finrst'' , as the packet filtering options to be specified in the ppp.conf file. These are for TCP's syn packet and fin/rst packet respectively. 2. When executed in automatic mode and netmask of the source (or local) address given in the set ifaddr is less than 32, followings are performed. If these conditions are not met, normal operations are done (just as with the non-modified version of IIJ-PPP). 2.1 For 4~5 seconds after the link is established (an address is assigned to the tunnel device), PPP changes the source IP address in the IP header to the assigned address if it differs from the assigned address and re-calculate the IP checksum. 2.2 Re-calculate the checksum for TCP and UDP packets. 2.3 Change the address of the tunnel device to 0.0.0.0 upon disconnection of the line. The patch was originally made to work with IIJ-PPP included in the FreeBSD 2.1.5R, and I modified it to work with the PPP in FreeBSD-current. I tested the modified version and it seems running fine. Could someone review this? If things are ok, the author of this patch and I would like to merge this patch into FreeBSD-current. Thanks. Max ----Next_Part(Sun_Oct_13_03:30:22_1996)-- Content-Type: Text/Plain; charset=us-ascii Index: ppp/filter.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/ppp/filter.c,v retrieving revision 1.6 diff -u -r1.6 filter.c --- filter.c 1996/01/10 21:27:43 1.6 +++ filter.c 1996/10/12 17:30:31 @@ -238,13 +238,23 @@ if (argc == 0) return(1); } - if (argc == 1) { - if (STREQ(*argv, "estab")) { - filterdata.opt.estab = 1; + if (argc >= 1 && STREQ(*argv, "estab")) { + filterdata.opt.estab = 1; + argc -= 1; argv += 1; + if (argc == 0) + return(1); + } + if (argc >= 1 && STREQ(*argv, "syn")) { + filterdata.opt.syn = 1; + argc -= 1; argv += 1; + if (argc == 0) + return(1); + } + if (argc >= 1 && STREQ(*argv, "finrst")) { + filterdata.opt.finrst = 1; + /* argc -= 1; argv += 1; */ + if (argc == 0) return(1); - } - printf("estab is expected: %s\n", *argv); - return(0); } if (argc > 0) printf("bad src/dst port syntax: %s\n", *argv); @@ -359,6 +369,8 @@ printf("src: %s (%d)\n", opname[fp->opt.srcop], fp->opt.srcport); printf("dst: %s (%d)\n", opname[fp->opt.dstop], fp->opt.dstport); printf("estab: %d\n", fp->opt.estab); + printf("syn: %d\n", fp->opt.syn); + printf("finrst: %d\n", fp->opt.finrst); #endif if (val) @@ -448,6 +460,10 @@ printf(" dst %s %d", opname[fp->opt.dstop], fp->opt.dstport); if (fp->opt.estab) printf(" estab"); + if (fp->opt.syn) + printf(" syn"); + if (fp->opt.finrst) + printf(" finrst"); } printf("\n"); Index: ppp/filter.h =================================================================== RCS file: /home/ncvs/src/usr.sbin/ppp/filter.h,v retrieving revision 1.4 diff -u -r1.4 filter.h --- filter.h 1996/01/11 17:48:43 1.4 +++ filter.h 1996/10/12 17:30:31 @@ -65,6 +65,8 @@ short dstop; u_short dstport; int estab; + int syn; + int finrst; } opt; }; Index: ppp/ip.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/ppp/ip.c,v retrieving revision 1.9 diff -u -r1.9 ip.c --- ip.c 1996/05/11 20:48:25 1.9 +++ ip.c 1996/10/12 17:30:31 @@ -120,7 +120,7 @@ int direction; { struct filterent *fp = Filters[direction]; - int gotinfo, cproto, estab, n; + int gotinfo, cproto, estab, syn, finrst, n; struct tcphdr *th; struct udphdr *uh; struct icmp *ih; @@ -128,7 +128,7 @@ u_short sport, dport; if (fp->action) { - cproto = gotinfo = estab = 0; + cproto = gotinfo = estab = syn = finrst = 0; sport = dport = 0; for (n = 0; n < MAXFILTERS; n++) { if (fp->action) { @@ -149,17 +149,19 @@ switch (pip->ip_p) { case IPPROTO_ICMP: cproto = P_ICMP; ih = (struct icmp *)ptop; - sport = ih->icmp_type; estab = 1; + sport = ih->icmp_type; estab = syn = finrst = 1; break; case IPPROTO_UDP: cproto = P_UDP; uh = (struct udphdr *)ptop; sport = ntohs(uh->uh_sport); dport = ntohs(uh->uh_dport); - estab = 1; + estab = syn = finrst = 1; break; case IPPROTO_TCP: cproto = P_TCP; th = (struct tcphdr *)ptop; sport = ntohs(th->th_sport); dport = ntohs(th->th_dport); estab = (th->th_flags & TH_ACK); + syn = (th->th_flags & TH_SYN); + finrst = (th->th_flags & (TH_FIN | TH_RST)); #ifdef DEBUG if (estab == 0) logprintf("flag = %02x, sport = %d, dport = %d\n", th->th_flags, sport, dport); @@ -170,8 +172,8 @@ } gotinfo = 1; #ifdef DEBUG -logprintf("dir = %d, proto = %d, srcop = %d, dstop = %d, estab = %d\n", -direction, cproto, fp->opt.srcop, fp->opt.dstop, estab); +logprintf("dir = %d, proto = %d, srcop = %d, dstop = %d, estab = %d, syn = %d, finrst = %d\n", +direction, cproto, fp->opt.srcop, fp->opt.dstop, estab, syn, finrst); #endif } #ifdef DEBUG @@ -186,7 +188,11 @@ (fp->opt.dstop == OP_NONE || PortMatch(fp->opt.dstop, dport, fp->opt.dstport)) && - (fp->opt.estab == 0 || estab)) { + (fp->opt.estab == 0 || estab) + && + (fp->opt.syn == 0 || syn) + && + (fp->opt.finrst == 0 || finrst)) { return(fp->action); } } Index: ppp/main.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/ppp/main.c,v retrieving revision 1.22 diff -u -r1.22 main.c --- main.c 1996/10/12 16:20:32 1.22 +++ main.c 1996/10/12 17:30:31 @@ -35,6 +35,10 @@ #include #include #include +#include +#include +#include +#include #include "modem.h" #include "os.h" #include "hdlc.h" @@ -626,22 +630,144 @@ } } +inline +void +RecalcProtoCksum(buf) + u_char *buf; +{ + static u_short *bp; + static union { + struct tcphdr *th; + struct udphdr *uh; + } ph; + static u_char savec, *savecp; + static u_int hlen, plen, changes; + /* recalculate checksum in protocol specific header if needed */ + switch(((struct ip *)buf)->ip_p){ + case IPPROTO_UDP: + bp = (u_short *)buf; + bp += 2 * ((struct ip *)buf)->ip_hl; + ph.uh = (struct udphdr *)bp; + /* bp/ph.uh points to udp header */ + ph.uh->uh_sum = 0; + hlen = ntohs(((struct ip *)buf)->ip_len); + savecp = buf + hlen; + savec = *savecp; + *savecp = (u_char)0; + plen = (hlen -= 4 * ((struct ip *)buf)->ip_hl); + changes = 0; + hlen++; + hlen /= 2; + for(; hlen > 0; hlen--) + changes += *bp++; + *savecp = savec; + /* calculate pseudo UDP header */ + /* source address */ + bp = (u_short *)&(((struct ip *)buf)->ip_src); + changes += *bp++; + changes += *bp++; + /* destination address */ + changes += *bp++; + changes += *bp; + /* protocol */ + changes += htons(IPPROTO_UDP); /* protocol */ + /* UDP length */ + changes += htons(plen); + changes = (changes & 0xffff) + (changes >> 16); + changes = (changes & 0xffff) + (changes >> 16); + ph.uh->uh_sum = (~changes & 0xffff); + LogPrintf(LOG_TCPIP, "UDP check sum is recalculated\n"); + break; + case IPPROTO_TCP: + bp = (u_short *)buf; + bp += 2 * ((struct ip *)buf)->ip_hl; + ph.th = (struct tcphdr *)bp; + /* bp/ph.th points to tcp header */ + ph.th->th_sum = 0; + hlen = ntohs(((struct ip *)buf)->ip_len); + savecp = buf + hlen; + savec = *savecp; + *savecp = (u_char)0; + plen = (hlen -= 4 * ((struct ip *)buf)->ip_hl); + changes = 0; + hlen++; + hlen /= 2; + for(; hlen > 0; hlen--) + changes += *bp++; + *savecp = savec; + /* calculate pseudo TCP header */ + /* source address */ + bp = (u_short *)&(((struct ip *)buf)->ip_src); + changes += *bp++; + changes += *bp++; + /* destination address */ + changes += *bp++; + changes += *bp; + /* protocol */ + changes += htons(IPPROTO_TCP); /* protocol */ + /* TCP length */ + changes += htons(plen); + changes = (changes & 0xffff) + (changes >> 16); + changes = (changes & 0xffff) + (changes >> 16); + ph.th->th_sum = (~changes & 0xffff); + LogPrintf(LOG_TCPIP, "TCP check sum is recalculated\n"); + break; + default: /* IPPROTO_ICMP */ + } +} +void +ChangeSrcIPAddress(buf, addr) + u_char *buf; + struct in_addr addr; +{ + static u_int changes; + static u_int hlen; + static u_short *bp; + static char msgbuff[100]; /* for debugging message */ + /* if buf has correct IP address, assume it has correct IP checksum */ + if(((struct ip *)buf)->ip_src.s_addr != addr.s_addr){ + if(loglevel & (1 << LOG_TCPIP)) /* for spped up when logging is disabled */ + sprintf(msgbuff, "%s", inet_ntoa(((struct ip *)buf)->ip_src)); + ((struct ip *)buf)->ip_src = addr; + ((struct ip *)buf)->ip_sum = 0; + /* recalculating checksum in IP header */ + bp = (u_short *)buf; + changes = 0; + /* IP header length is (hlen * 2) bytes */ + for(hlen = 2 * ((struct ip *)buf)->ip_hl; hlen > 0; hlen--) + changes += *bp++; + changes = (changes & 0xffff) + (changes >> 16); + changes = (changes & 0xffff) + (changes >> 16); + ((struct ip *)buf)->ip_sum = (~changes & 0xffff); + if(loglevel & (1 << LOG_TCPIP)) /* for spped up when logging is disabled */ + LogPrintf(LOG_TCPIP, "Src address changed: %s ---> %s\n", + msgbuff, + inet_ntoa(((struct ip *)buf)->ip_src)); + } + /* but protocol specific checksum may or may not correct */ + RecalcProtoCksum(buf); +} static void DoLoop() { fd_set rfds, wfds, efds; int pri, i, n, wfd; + int tsavelen = 0; struct sockaddr_in hisaddr; struct timeval timeout, *tp; int ssize = sizeof(hisaddr); u_char *cp; - u_char rbuff[MAX_MRU]; + u_char rbuff[MAX_MRU], tbuff[MAX_MRU]; int dial_up; int tries; int qlen; pid_t pgroup; + time_t ttimer = (time_t)0; /* expiration timer for tun device */ + struct in_addr oldmyaddr; + int recalc; /* recalculates checksum */ + recalc = (mode & MODE_AUTO) && (DefMyAddress.width < 32); pgroup = getpgrp(); if (mode & MODE_DIRECT) { @@ -693,6 +819,7 @@ if (VarDialTries && tries >= VarDialTries) { dial_up = FALSE; tries = 0; + tsavelen = 0; } } } @@ -726,7 +853,7 @@ #endif /* If there are aren't many packets queued, look for some more. */ - if (qlen < 20) + if (qlen < 20 && !tsavelen) FD_SET(tun_in, &rfds); if (netfd > -1) { @@ -848,6 +975,19 @@ } } + if (tsavelen && isOsLinkup()){ + /* check & reassign source IP address */ + if(recalc) + ChangeSrcIPAddress(tbuff, getCurMyAddr()); + pri = PacketCheck(tbuff, tsavelen, FL_OUT); + if (pri >= 0){ + IpEnqueue(pri, tbuff, tsavelen); + } + tsavelen = 0; + ttimer = time(NULL) + (time_t)5; /* src IP address check expires in 5 secs */ + continue; + } + if (FD_ISSET(tun_in, &rfds)) { /* something to read from tun */ n = read(tun_in, rbuff, sizeof(rbuff)); if (n < 0) { @@ -859,16 +999,31 @@ * device until IPCP is opened. */ if (LcpFsm.state <= ST_CLOSED && (mode & MODE_AUTO)) { - pri = PacketCheck(rbuff, n, FL_DIAL); + pri = PacketCheck(rbuff, n, FL_DIAL); /* 1st time */ if (pri >= 0) { - IpEnqueue(pri, rbuff, n); + oldmyaddr = DefMyAddress.ipaddr; /* getCurMyAddr(); */ + /* IpEnqueue(pri, rbuff, n); */ + bcopy(rbuff, tbuff, tsavelen = n); dial_up = TRUE; /* XXX */ } continue; } pri = PacketCheck(rbuff, n, FL_OUT); - if (pri >= 0) + if (pri >= 0){ + if(recalc){ /* when ttimer is set, recalc is always TRUE */ + if(ttimer){ + if(ttimer > time(NULL)){ + /* check & reassign source IP address */ + ChangeSrcIPAddress(rbuff, getCurMyAddr()); + }else{ + ttimer = (time_t)0; + } + }else{ + RecalcProtoCksum(rbuff); + } + } IpEnqueue(pri, rbuff, n); + } } } logprintf("job done.\n"); Index: ppp/os.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/ppp/os.c,v retrieving revision 1.7 diff -u -r1.7 os.c --- os.c 1996/06/03 21:35:21 1.7 +++ os.c 1996/10/12 17:30:31 @@ -42,7 +42,7 @@ static struct ifaliasreq ifra; static struct ifreq ifrq; -static struct in_addr oldmine, oldhis; +static struct in_addr oldmine, oldhis, oldmask; static int linkup; #ifdef bsdi @@ -137,6 +137,7 @@ sin->sin_len = sizeof(*sin); if (changeaddr) { + oldmask.s_addr = mask; /* * Interface already exists. Just change the address. */ @@ -200,12 +201,17 @@ OsLinkdown() { char *s; + struct in_addr zeroaddr; if (linkup) { s = (char *)inet_ntoa(peer_addr); LogPrintf(LOG_LINK_BIT|LOG_LCP_BIT, "OsLinkdown: %s\n", s); if (!(mode & MODE_AUTO)) DeleteIfRoutes(0); + if((mode & MODE_AUTO) && (DefMyAddress.width < 32)){ + zeroaddr.s_addr = 0; + OsSetIpaddress(zeroaddr, oldhis, oldmask); + } linkup = 0; } } @@ -348,6 +354,16 @@ { } +int +isOsLinkup() +{ + return linkup; +} +struct in_addr +getCurMyAddr() +{ + return oldmine; +} void OsAddOutOctets(cnt) int cnt; Index: ppp/os.h =================================================================== RCS file: /home/ncvs/src/usr.sbin/ppp/os.h,v retrieving revision 1.3 diff -u -r1.3 os.h --- os.h 1996/01/10 21:27:57 1.3 +++ os.h 1996/10/12 17:30:32 @@ -34,4 +34,6 @@ void DeleteIfRoutes __P((int)); void OsAddInOctets __P((int cnt)); void OsAddOutOctets __P((int cnt)); +int isOsLinkup __P((void)); +struct in_addr getCurMyAddr __P((void)); #endif ----Next_Part(Sun_Oct_13_03:30:22_1996)---- From owner-freebsd-current Sat Oct 12 12:46:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA23876 for current-outgoing; Sat, 12 Oct 1996 12:46:45 -0700 (PDT) Received: from alpha.jpunix.com (root@alpha.jpunix.com [199.3.234.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA23864 for ; Sat, 12 Oct 1996 12:46:41 -0700 (PDT) Received: (from perry@localhost) by alpha.jpunix.com (8.7.5/8.7.5) id OAA11629 for freebsd-current@freebsd.org; Sat, 12 Oct 1996 14:45:46 -0500 (CDT) Date: Sat, 12 Oct 1996 14:45:44 -0500 (CDT) From: "John A. Perry" To: freebsd-current@freebsd.org Subject: Can't make current! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello everyone, I'm trying to upgrade from FreeBSD 2.1.5 off of the CD to current as of Sat. morn. (Oct. 12). The "make world" is failing with the following messages. The beginning of the problem is where "make world" wants to: cd /usr/src/gnu/lib/libstdc++ && make beforeinstall install -C -o bin -g bin -m 444 /usr/local/src/gnu/lib/libstdc++/_G_config.h /usr/local/src/gnu/lib/libstdc++/../../../contrib/libg++/libstdc++/cassert [stuff deleted] and ending in an error: install: /usr/local/src/gnu/lib/libstdc++/../../../contrib/libg++/libstdc++/cassert: No such file or directory *** Error code 71 What is cassert? Do I need it? Ho wcome I don't have it? What do I need to do? Please advise. John Perry KG5RG perry@alpha.jpunix.com PGP-encrypted e-mail welcome! WWW - http://www.jpunix.com PGP 2.62 key for perry@jpunix.com is on the keyservers. From owner-freebsd-current Sat Oct 12 15:06:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA03468 for current-outgoing; Sat, 12 Oct 1996 15:06:45 -0700 (PDT) Received: from inga.augusta.de (root@inga.augusta.de [193.175.23.65]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA03336 for ; Sat, 12 Oct 1996 15:04:32 -0700 (PDT) Received: from rabbit by inga.augusta.de with uucp (Smail3.1.29.1 #1) id m0vCC5m-004cs8C; Sat, 12 Oct 96 23:59 MET DST Received: by rabbit.augusta.de (Smail3.1.29.1 #1) id m0vBm2Q-000ANRC; Fri, 11 Oct 96 20:10 MET DST Message-Id: Date: Fri, 11 Oct 96 20:10 MET DST X-Newsreader: knews 0.9.6 Organization: Privat Site running FreeBSD References: From: shanee@rabbit.augusta.de (Andreas Kohout) Subject: ps axl | grep X-Original-Newsgroups: muc.lists.freebsd.current To: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, bug or feature? (sorry about long lines, but it is neccessary) Iīm running current, build Sep 22 ... I try to find out how much memory fvwm2 use. So I do a rabbit:/home/shanee> ps -ax | grep fvwm 16388 ?? S 0:02.00 fvwm 16413 ?? S 0:00.05 /usr/X11R6/lib/X11/fvwm/FvwmAuto 8 4 .fvwmrc 0 8 500 16414 ?? I 0:00.14 /usr/X11R6/lib/X11/fvwm/FvwmButtons 12 4 .fvwmrc 0 8 16417 ?? S 0:00.22 /usr/X11R6/lib/X11/fvwm/FvwmPager 14 4 .fvwmrc 0 8 0 2 but I canīt see the right field and I tried rabbit:/home/shanee> ps -axl | grep fvwm 1000 16388 16265 0 2 0 472 1048 select S ?? 0:02.01 fvwm funny ... but I thought FvwmAuto ect. must need memory. So I resize my xterm window to 120 columns and tried again rabbit:/home/shanee> ps -axl | grep fvwm 1000 16388 16265 0 2 0 472 1040 select S ?? 0:02.04 fvwm 1000 16413 16388 0 2 0 144 492 select S ?? 0:00.05 /usr/X11R6/lib/X11/fvwm/FvwmA 1000 16414 16388 0 2 0 244 764 select S ?? 0:00.14 /usr/X11R6/lib/X11/fvwm/FvwmB 1000 16417 16388 0 2 0 212 788 select S ?? 0:00.22 /usr/X11R6/lib/X11/fvwm/FvwmP I tried it with TERM=[vt51,vt100,vt220,xterm] and on a pcvt. Same problem ... Than I resized my window to 45 columns and get rabbit:/home/shanee> ps -axl | grep fvwm 1000 16388 16265 0 2 0 472 1040 selec t S ?? 0:02.46 fvwm and rabbit:/home/shanee> ps -ax | grep fvwm 16388 ?? S 0:02.47 fvwm Is this normal? Or must I send a send-pr? -- Greeting, Andy running FreeBSD-current --------------------------------------------------------------------------- From owner-freebsd-current Sat Oct 12 15:15:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA03977 for current-outgoing; Sat, 12 Oct 1996 15:15:49 -0700 (PDT) Received: from citrine.cyberstation.net (hannibal@citrine.cyberstation.net [205.167.0.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA03951 for ; Sat, 12 Oct 1996 15:15:14 -0700 (PDT) Received: from localhost (hannibal@localhost) by citrine.cyberstation.net (8.6.12/8.6.12) with SMTP id RAA08812; Sat, 12 Oct 1996 17:15:07 -0500 Date: Sat, 12 Oct 1996 17:15:06 -0500 (CDT) From: Dan Walters To: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= cc: freebsd-current@FreeBSD.ORG Subject: Re: IIJ-PPP patch, please review In-Reply-To: <199610121833.DAA18858@mail.tky007.tth.expo96.ad.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk BTW, the filters don't allow anything like "set ifilter 0 permit tcp estab", because the function that parses the rules for tcp/udp doesn't let the estab get through... Just need to delete about 3 lines at the top. ====================================================================== Dan Walters hannibal@cyberstation.net ====================================================================== On Sun, 13 Oct 1996, Masafumi NAKANE/[ISO-2022-JP] $BCf:,2mJ8(B wrote: > Hi, > > Recently I found a nice modification to IIJ-PPP by Hideo NORO > . With this patch applied, the auto mode > (dial-on-demand mode) of IIJ-PPP doesn't require any dummy packet to > be sent before the link is established. So, it's like true > dial-on-demand. > > The features added/modified by this patch are: > > 1. Added two options, ``syn'' and ``finrst'' , as the packet > filtering options to be specified in the ppp.conf file. These are for > TCP's syn packet and fin/rst packet respectively. > > 2. When executed in automatic mode and netmask of the source (or > local) address given in the set ifaddr is less than 32, followings are > performed. If these conditions are not met, normal operations are > done (just as with the non-modified version of IIJ-PPP). > > 2.1 For 4~5 seconds after the link is established (an address is > assigned to the tunnel device), PPP changes the source IP address in > the IP header to the assigned address if it differs from the assigned > address and re-calculate the IP checksum. > > 2.2 Re-calculate the checksum for TCP and UDP packets. > > 2.3 Change the address of the tunnel device to 0.0.0.0 upon > disconnection of the line. > > > The patch was originally made to work with IIJ-PPP included in the > FreeBSD 2.1.5R, and I modified it to work with the PPP in > FreeBSD-current. > > I tested the modified version and it seems running fine. > > Could someone review this? If things are ok, the author of this patch > and I would like to merge this patch into FreeBSD-current. > > Thanks. > > Max > From owner-freebsd-current Sat Oct 12 17:44:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA17472 for current-outgoing; Sat, 12 Oct 1996 17:44:45 -0700 (PDT) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA17464 for ; Sat, 12 Oct 1996 17:44:42 -0700 (PDT) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.7.6/BSD4.4) id KAA09569 Sun, 13 Oct 1996 10:44:20 +1000 (EST) From: michael butler Message-Id: <199610130044.KAA09569@asstdc.scgt.oz.au> Subject: Re: ps axl | grep In-Reply-To: from Andreas Kohout at "Oct 11, 96 08:10:00 pm" To: shanee@rabbit.augusta.de (Andreas Kohout) Date: Sun, 13 Oct 1996 10:44:20 +1000 (EST) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Andreas Kohout writes: > bug or feature? [ .. ] > funny ... but I thought FvwmAuto ect. must need memory. So I resize my > xterm window to 120 columns and tried again feature .. man ps(1) .. specifically the '-w' option .. 'ps axlww' will do what you want, michael From owner-freebsd-current Sat Oct 12 18:43:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA21831 for current-outgoing; Sat, 12 Oct 1996 18:43:33 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA21826 for ; Sat, 12 Oct 1996 18:43:30 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id SAA02166 for ; Sat, 12 Oct 1996 18:43:17 -0700 (PDT) Message-Id: <199610130143.SAA02166@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: current@freebsd.org Subject: Support for PCI Cyclades Cyclom-Y serial adapter From: David Greenman Reply-To: dg@root.com Date: Sat, 12 Oct 1996 18:43:17 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just committed to CVS the changes necessary to support the PCI version of the Cyclades Cyclom-Y serial adapters. Included with these changes is also support for multiple controllers and support for the 32-Y. In order to facilitate the changes, it was necessary to expand the device naming convention. The new naming scheme is ttyc[0-v][0-v] and cuac[0-v][0-v], where the first [0-v] is the controller and the second [0-v] is the unit on the controller. This is the same convention used on other multiport serial adapters such as the Digiboard. If you are currently using the Cyclades serial adapter, you should re-make your /dev entries and remove the old ones. The new MAKEDEV creates devices for all 32 units on a controller...just say "MAKEDEV ttyc0 cuac0", for instance, to create all of the units for controller 0. Be sure to also make the appropriate changes in /etc/. I've done a reasonable amount of testing locally, but it's always possible that I may have overlooked something. Please let me know if you experiance any problems. Thanks. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project