From owner-freebsd-current Sun Dec 8 00:34:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA01982 for current-outgoing; Sun, 8 Dec 1996 00:34:18 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA01977 for ; Sun, 8 Dec 1996 00:34:16 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id AAA01079; Sun, 8 Dec 1996 00:34:08 -0800 (PST) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@freebsd.org (FreeBSD-current users) Subject: Re: last in -current In-reply-to: Your message of "Sat, 07 Dec 1996 22:34:36 +0100." <199612072134.WAA23001@uriah.heep.sax.de> Date: Sun, 08 Dec 1996 00:34:07 -0800 Message-ID: <1075.850034047@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I think we're more headed towards a migration tool. My system ain't > fully -current again, once it is, i'm in an urgent need to write the > tool. If possible at all, i'll try to write it with some heuristics > so it can also migrate wtmp's that have trailing records written using > the new scheme. Well, like I said before, I think that a general "delta" system needs to be evolved along these lines: 1. All deltas have a consistent data format, sequence numbered, uuencoded, PGP signed and for the benefit of the migration tools (and easy sending through email). 2. Based on its type field, which would be extensible, the migration tools will know what to do with a delta once it's been decoded, verified and checked for applicability. A delta could be as simple as a unidiff for patch, it could be a perl script or other executable which is run to perform some more complex action. 3. Any time a delta procedure changes something, it or the migration tools (for simpler deltas which have built-in handlers) will have to register a "reverse delta", essentially a delta who's job it is to go back to the previous state of affairs. This means that a side-effect of applying a bunch of deltas to your system is the creation of *another* set of deltas under a common collection name (say "undo"). You could then go ask to apply the undo collection later if you wanted to undo the previous action, bringing you back to your pre-upgrade state. The migration tools should also have the concept of "destructive delta application", where deltas of that class don't cause a reverse-op to happen and are themselves deleted upon being applied, giving you one level of undo. All that was probably a lot more complex to describe than it might be to actually do. :-) Once you've done that, the creation of a "wtmp migrator" becomes pretty easy. I don't mean to come down on Joerg with a huge spec here in response to a small problem, but a haphazard collection of upgrade bits is what we have *already*, and I'm simply trying to suggest implementing a framework somewhat more flexible than what we need for just this one-time problem since it's be nice to actually implement a solution which goes farther than just a one release, throw-away for a change. :-) Jordan From owner-freebsd-current Sun Dec 8 00:53:26 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA02447 for current-outgoing; Sun, 8 Dec 1996 00:53:26 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id AAA02434 for ; Sun, 8 Dec 1996 00:53:20 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA01515 for ; Sun, 8 Dec 1996 09:53:17 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA02459 for freebsd-current@FreeBSD.org; Sun, 8 Dec 1996 09:53:16 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id JAA29083 for freebsd-current@FreeBSD.org; Sun, 8 Dec 1996 09:38:27 +0100 (MET) From: J Wunsch Message-Id: <199612080838.JAA29083@uriah.heep.sax.de> Subject: Re: mfs module -- seems to work.. To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 8 Dec 1996 09:36:41 +0100 (MET) Cc: freebsd-current@freebsd.orgccsanady@friley216.res.iastate.edu (Chris Csanady) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612072239.QAA00487@friley216.res.iastate.edu> from Chris Csanady at "Dec 7, 96 04:39:51 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 Chris Csanady wrote: > I noticed in /usr/src/lkm/Makefile that the mfs module is not build because > it is broken. I have built it and loaded it, and it seems to work fine > without any changes. I've noticed the following bogosities: . mount_mfs without previously loading the lkm causes: mount_mfs: /mnt: Operation not supported by device /kernel: pid 28996 (mount_mfs), uid 0: exited on signal 11\ (core dumped) (It's supposed to first load the lkm.) . Loading it manually, and call mount_mfs then worked. However, attempts to umount it hung (interruptible), and i had to kill off the `mfs' process manually. -- 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 Dec 8 00:58:40 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA02643 for current-outgoing; Sun, 8 Dec 1996 00:58:40 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA02638 for ; Sun, 8 Dec 1996 00:58:38 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id AAA01158; Sun, 8 Dec 1996 00:58:28 -0800 (PST) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@freebsd.org (FreeBSD-current users) Subject: Re: cvs commit: src/include utmp.h In-reply-to: Your message of "Sat, 07 Dec 1996 19:18:54 +0100." <199612071818.TAA21315@uriah.heep.sax.de> Date: Sun, 08 Dec 1996 00:58:27 -0800 Message-ID: <1154.850035507@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > another place later: while the upgrade installation will painlessly > create the new files, it will leave the old files in their stale > location. Nobody will ever notice that they are stale, well unless > somebody tries to edit them and wonders why his changes are not in > effect at all... Yes, this and a host of other unpredicatable issues will be part of every upgrade we do. If we improve our accounting so that we know what to ask the upgrade system for at all ("gimme the new bindist, man pages and the bash and tcsh packages if they're newer"), and do this framework we've just started talking about (I'm looking at CTM right now, actually, it's interesting. It lacks PGP key signatures for creating truly *trusted* deltas (and I think this is an important point) and won't invoke pieces of a delta as executables, but those features could perhaps be added. :-) > What about a `whiteboard' directory in CVS? Some place where > everybody could append his notes at the end of a file? When it's Sure, just so long as this doesn't turn into another "TODO file" fiasco. I've always liked the idea of making it easier for us to leave notes for one another, there's just this constant problem with nobody ever erasing the whiteboards. :-) I'd actually prefer to make it so easy to make your own upgrade delta (e.g. there'd be a better tool than ``pkg_create'' this time :) that people would be more inclined to just make and commit one on the spot than describe it in words which some release engineer might or might not ever do anything with.. :-) Jordan From owner-freebsd-current Sun Dec 8 01:37:07 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA03456 for current-outgoing; Sun, 8 Dec 1996 01:37:07 -0800 (PST) Received: from wgrobez1.remote.louisville.edu (wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA03449 for ; Sun, 8 Dec 1996 01:37:03 -0800 (PST) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.8.4/8.6.12) with SMTP id EAA01302 for ; Sun, 8 Dec 1996 04:36:46 -0500 (EST) Date: Sun, 8 Dec 1996 04:36:39 -0500 (EST) From: Gary Roberts To: freebsd-current@freebsd.org Subject: samba 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 wondering if anyone was planning on making an 'smbmount' for the fbsd? I use samba now to share my unix drives with win95 clients, but I can't mount my win95 shares via fbsd(unless I use smbclient, and that's like ftp). And as far as I know, there isn't a NFS server for 95. I think having a 'samba fs' and the ability to mount shared machine drives(ie: win95, winnt, wfw, etc) would be cool. Thanks Gary From owner-freebsd-current Sun Dec 8 02:39:38 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA04967 for current-outgoing; Sun, 8 Dec 1996 02:39:38 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA04962 for ; Sun, 8 Dec 1996 02:39:34 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id VAA03667; Sun, 8 Dec 1996 21:08:48 +1030 (CST) From: Michael Smith Message-Id: <199612081038.VAA03667@genesis.atrad.adelaide.edu.au> Subject: Re: samba In-Reply-To: from Gary Roberts at "Dec 8, 96 04:36:39 am" To: wangel@wgrobez1.remote.louisville.edu (Gary Roberts) Date: Sun, 8 Dec 1996 21:08:47 +1030 (CST) Cc: freebsd-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 Gary Roberts stands accused of saying: > Just wondering if anyone was planning on making an 'smbmount' for the > fbsd? I use samba now to share my unix drives with win95 clients, but I > can't mount my win95 shares via fbsd(unless I use smbclient, and that's > like ftp). And as far as I know, there isn't a NFS server for 95. Please go back and read the mailing list archives for the meat of the last N times this has come up. Searching for 'smbfs' is probably a good place to start. Look particularly for Terry's detailed rants on the topic. Basically, the core problem is that the SMB protocol doesn't provide the features necessary for the implementation of a unix filesystem. The linux smbfs is, in the tradition of Linux, a festering hack, and this isn't exclusively the fault of the implementors. > I think having a 'samba fs' and the ability to mount shared machine > drives(ie: win95, winnt, wfw, etc) would be cool. Well, what can I say? Go for it! 8) > Gary -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Sun Dec 8 05:25:47 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA08952 for current-outgoing; Sun, 8 Dec 1996 05:25:47 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id FAA08946 for ; Sun, 8 Dec 1996 05:25:43 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id OAA06240 for ; Sun, 8 Dec 1996 14:25:36 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA07139 for freebsd-current@FreeBSD.org; Sun, 8 Dec 1996 14:25:35 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id OAA23270 for freebsd-current@FreeBSD.org; Sun, 8 Dec 1996 14:11:59 +0100 (MET) From: J Wunsch Message-Id: <199612081311.OAA23270@uriah.heep.sax.de> Subject: Re: last in -current To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 8 Dec 1996 14:11:58 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <1075.850034047@time.cdrom.com> from "Jordan K. Hubbard" at "Dec 8, 96 00:34:07 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: > Well, like I said before, I think that a general "delta" system needs > to be evolved along these lines: I basically like that idea. Do you already have a more detailed imagination of the delta format (type field etc.)? > 1. All deltas have a consistent data format, sequence > numbered, uuencoded, PGP signed and for the benefit of the > migration tools (and easy sending through email). Hmmpf. Kill your government first. As long as we cannot provide PGP as a binary drop-in, this is a moot point. I see your point, but i'm afraid that all we could do by now is MD5-checking the deltas. > 3. Any time a delta procedure changes something, it or the migration > tools (for simpler deltas which have built-in handlers) will have > to register a "reverse delta", essentially a delta who's job it is > to go back to the previous state of affairs. I'm not yet convinced that this is always possible. Consider the wtmp changes. The best you could probably do is keeping the previous wtmp & Co files around in the reverse delta, but all system activity records between the upgrade and the application of the reverse delta will be lost upon applying the latter. And, the reverse delta may become _really huge_, so the upgrade procedure must offer several opportunities, like allowing to delete the latest reverse delta from the hard disk, storing the reverse delta on external media (tape, ZIP drive) without consuming much temp disk space, or even not generating the reverse delta at all for those who think they aren't interested in it. > ..., and I'm simply trying to suggest implementing a > framework somewhat more flexible than what we need for just this > one-time problem since it's be nice to actually implement a solution > which goes farther than just a one release, throw-away for a > change. :-) Yep. Now, who's going to become FreeBSD's ``upgrade meister''? Yet another vacant job position... :-) Wasn't there anybody asking for things to do recently??? -- 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 Dec 8 07:31:39 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA14507 for current-outgoing; Sun, 8 Dec 1996 07:31:39 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA14502 for ; Sun, 8 Dec 1996 07:31:35 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.7.6/8.7.3) with SMTP id KAA17300; Sun, 8 Dec 1996 10:31:23 -0500 (EST) Date: Sun, 8 Dec 1996 10:31:23 -0500 (EST) From: John Fieber To: Michael Smith cc: Gary Roberts , freebsd-current@freebsd.org Subject: Re: samba In-Reply-To: <199612081038.VAA03667@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 Sun, 8 Dec 1996, Michael Smith wrote: > Please go back and read the mailing list archives for the meat of the > last N times this has come up. Searching for 'smbfs' is probably a > good place to start. Look particularly for Terry's detailed rants on > the topic. To quote from the motd on freefall: sd3 passed away at 7:05AM PST. RIP. A replacement drive will be ordered ASAP. Lots of stuff has died with it, expect chaos for a while. The mailing list archives are among the dead. :( I just hope some backups exist. > The linux smbfs is, in the tradition of Linux, a festering hack, and > this isn't exclusively the fault of the implementors. Alas, if you rate software on two scales: elegantly engineered solution to festering hack, and useless to useful, I'd hazzard a guess that if there is any correlation, it would be positive (associate the festering hacks with higher utility). Non-programmers don't care *how* the programmer implements something, so long as it works most of the time. Evidence? Microsoft products. I rest my case. -john From owner-freebsd-current Sun Dec 8 08:09:08 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA15428 for current-outgoing; Sun, 8 Dec 1996 08:09:08 -0800 (PST) Received: from solar.tlk.com (root@solar.tlk.com [194.97.84.10]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA15418 for ; Sun, 8 Dec 1996 08:08:50 -0800 (PST) Received: by solar.tlk.com id ; Sun, 8 Dec 96 17:08 MET Message-Id: From: torstenb@solar.tlk.com (Torsten Blum) Subject: Re: last in -current In-Reply-To: <199612081311.OAA23270@uriah.heep.sax.de> from J Wunsch at "Dec 8, 96 02:11:58 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 8 Dec 1996 17:08:41 +0100 (MET) Cc: freebsd-current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL26 (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 J Wunsch wrote: > > 1. All deltas have a consistent data format, sequence > > numbered, uuencoded, PGP signed and for the benefit of the > > migration tools (and easy sending through email). > > Hmmpf. Kill your government first. As long as we cannot provide PGP > as a binary drop-in, this is a moot point. pgp uses idea, which is patented by Ascom in Switzerland. Non-private use (and they're very restrictive with this definition) is free, but for everything else you need a licence. That's the same reason why the ssh port has a switch to disable idea. -tb From owner-freebsd-current Sun Dec 8 08:46:39 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA16909 for current-outgoing; Sun, 8 Dec 1996 08:46:39 -0800 (PST) Received: from ylana.vet.purdue.edu (vet.vet.purdue.edu [128.210.96.50]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA16897 for ; Sun, 8 Dec 1996 08:46:31 -0800 (PST) Received: from ylana.vet.purdue.edu (localhost.vet.purdue.edu [127.0.0.1]) by ylana.vet.purdue.edu (8.8.3/8.7.3) with ESMTP id LAA23662 for ; Sun, 8 Dec 1996 11:24:59 -0500 (EST) Message-Id: <199612081624.LAA23662@ylana.vet.purdue.edu> X-Mailer: exmh version 1.6.9 8/22/96 To: current@FreeBSD.ORG Subject: ctm delta src-cur.2484.gz mangled? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Dec 1996 11:24:58 -0500 From: Benjamin Lewis Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, I'm having trouble applying ctm delta src-cur.2484.gz: ylana:/usr/src [143]#ctm -v -v ctms/src-cur.2484.gz Working on Expecting Global MD5 <050901836fc100ca56044c7706b85623> Reference Global MD5 <050901836fc100ca56044c7706b85623> FN: share/doc/handbook/contrib.sgml md5 mismatch. FN: share/doc/handbook/contrib.sgml edit fails. Exit(104) I know for a fact that I've never modified share/doc/handbook/contrib.sgml, but just in case there was bit-rot or something, I created a virgin src/ tree from the src-cur.2400A.gz base delta, and applied every delta to it, with the same results for #2484. Is there anything I can do about this? It looks like I can tell ctm to ignore contrib.sgml, but then I'd never be able to update that file again, right (without grabbing another base delta)? This sort of thing seems to happen every time we get close to another base delta, and in the past I've just waited for and downloaded the next base delta. However, this seems to defeat the point of deltas entirely, as I end up ftping a 40MB file every 100 deltas. Might as well just skip the deltas all together, eh? Here's the output of ctm -V 4, just in case it's useful: ylana:/usr/src [156]#ctm -V 4 ctms/src-cur.2484.gz Working on Pass1 -- Checking integrity of incoming CTM-patch <2.0> <2484> <19961207035439Z> <.> <.ctm_status> <0> <0> <644> <033bb9da025d22edfc6652084340370c> <13> <0> <0> <644> <488ebd4498a977ac9f1096f9a499f4ed> <6c8c6261294fc734c6b6a909ffcd5155> <42> <0> <0> <644> <4981450b46bbeb0346c2a13507d2ab28> <42bcdccaec390221d57e3c12af702bd4> <755> <0> <0> <644> <8748e9e48254d5fb48099abcf118eb3e> <277e4132096aa9213805a647528886b0> <209> <0> <0> <644> <1247fd3171e99fbbfdf21a03a9b12a58> <239> <0> <0> <644> <6ba3d5e778fbdc9e5203909c3333e576> <4bd20c78ef1a8f456883cf25eb583135> <157> <0> <0> <644> <6e45127ccaec8aeb8f6b969c8ea08f17> <261b55949a6dfbf25d2d6e5a83a0c0cc> <1033> <0> <0> <644> <3c696fde00ac0dd4d15938729e875b5e> <128> Expecting Global MD5 <050901836fc100ca56044c7706b85623> <050901836fc100ca56044c7706b85623> Reference Global MD5 <050901836fc100ca56044c7706b85623> Pass2 -- Checking if CTM-patch will apply <2.0> <2484> <19961207035439Z> <.> <.ctm_status> <0> <0> <644> <033bb9da025d22edfc6652084340370c> <13> <0> <0> <644> <488ebd4498a977ac9f1096f9a499f4ed> <6c8c6261294fc734c6b6a909ffcd5155> <42> <0> <0> <644> <4981450b46bbeb0346c2a13507d2ab28> <42bcdccaec390221d57e3c12af702bd4> <755> <0> <0> <644> <8748e9e48254d5fb48099abcf118eb3e> FN: share/doc/handbook/contrib.sgml md5 mismatch. <277e4132096aa9213805a647528886b0> <209> FN: share/doc/handbook/contrib.sgml edit fails. Exit(104) Thanks, -Ben -- | ". . .and Blundell is doing very well in sixth position Benjamin Lewis | . . .in fact he's lapping 2.5 seconds faster than bhlewis@purdue.edu | Blundell who is in fifth position" | -- Murray Walker From owner-freebsd-current Sun Dec 8 09:17:50 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA17906 for current-outgoing; Sun, 8 Dec 1996 09:17:50 -0800 (PST) Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA17894 for ; Sun, 8 Dec 1996 09:17:36 -0800 (PST) Received: from cantina.clinet.fi (root@cantina.clinet.fi [194.100.0.15]) by hauki.clinet.fi (8.8.2/8.6.4) with ESMTP id TAA10685; Sun, 8 Dec 1996 19:17:26 +0200 (EET) Received: (hsu@localhost) by cantina.clinet.fi (8.8.2/8.6.4) id TAA08170; Sun, 8 Dec 1996 19:17:25 +0200 (EET) Date: Sun, 8 Dec 1996 19:17:25 +0200 (EET) Message-Id: <199612081717.TAA08170@cantina.clinet.fi> From: Heikki Suonsivu To: "Jordan K. Hubbard" Cc: freebsd-current@freebsd.org In-reply-to: "Jordan K. Hubbard"'s message of 8 Dec 1996 10:46:21 +0200 Subject: Re: last in -current Organization: Clinet Ltd, Espoo, Finland References: <1075.850034047@time.cdrom.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk From: "Jordan K. Hubbard" Once you've done that, the creation of a "wtmp migrator" becomes pretty easy. Simple character formats allow modifying the format without building tools for backwards compatibility. Would require providing getwtmp and similar functions for access and would break quite a bit of programs, but might be worth it. Has posix anything to say on this? To me it seems that messing up this much just for 8 more bytes for user id seems short-sighted (solaris went to 32 in utmpx, I'm not sure about that :-). -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi mobile +358-40-5519679 work +358-9-43542270 fax -4555276 From owner-freebsd-current Sun Dec 8 11:54:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA21753 for current-outgoing; Sun, 8 Dec 1996 11:54:19 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA21748 for ; Sun, 8 Dec 1996 11:54:16 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id LAA05892; Sun, 8 Dec 1996 11:52:51 -0800 (PST) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: last in -current In-reply-to: Your message of "Sun, 08 Dec 1996 14:11:58 +0100." <199612081311.OAA23270@uriah.heep.sax.de> Date: Sun, 08 Dec 1996 11:52:51 -0800 Message-ID: <5888.850074771@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I basically like that idea. Do you already have a more detailed > imagination of the delta format (type field etc.)? Yeah, I'll write something up later on this afternoon and post it. I think there's even an old mail somewhere where I went into detail on what the headers would look like. :-) This isn't the first time this whole thing has come up, we just never seem to get beyond the discussion phase. :-( I'll see if I can do something more tangible this time. > > 1. All deltas have a consistent data format, sequence > > numbered, uuencoded, PGP signed and for the benefit of the > > migration tools (and easy sending through email). > > Hmmpf. Kill your government first. As long as we cannot provide PGP > as a binary drop-in, this is a moot point. Erm, no, it's really not. Even though pgp is something of a pain to install on both sides of the Atlantic, it's hardly an impossibility and tools like pgpmail are very popular over here, stupid government or no. Furthermore, even if the tools *ignore* the pgp signature, as they would in the case where no pgp program was found (and it would just print a short warning msg that they should install the pgp program if they want more assurance that what they're doing is legitimate), we still need to provide it for those people who really do care. That way we've also done our bit for security and if someone later ignores the warnings and gets screwed by someone putting a trojan-horsed set of upgrade patches up on a mirror FTP site somewhere (and these things are never a question of *if* so much as *when*), we can just shrug and say "you should have installed pgp, dude, we DID make provisions for this problem!" Right now, the best we can say is "uh, yeah, we don't know security from a rat's sphincter and there aren't even any provisions for verifying that the stuff came from us, sorry!" That doesn't quite sound as good, does it? :-) > I'm not yet convinced that this is always possible. Consider the wtmp > changes. The best you could probably do is keeping the previous wtmp > & Co files around in the reverse delta, but all system activity Yes, that is true, and keeping the old version of the file around (though possibly compressed) would sort of be the "last ditch" reverse delta for cases when nothing more elegant was possible. Better than nothing, as is: > records between the upgrade and the application of the reverse delta > will be lost upon applying the latter. Which at least allows you to go back to a working wtmp file, despite having lost some entries, if you decide that long usernames are a luxury you can't afford for some reason (say your favorite binary-only system accounting tool breaks, or something). It's not perfect, no, but again (as with the pgp stuff) it's a lot better than saying "no way of going backwards exists, sorry." The wtmp example doesn't perhaps lend itself as well to reverse-motion as many other types of deltas will, but I think it's still a very necessary feature, imperfections and all. > And, the reverse delta may become _really huge_, so the upgrade > procedure must offer several opportunities, like allowing to delete > the latest reverse delta from the hard disk, storing the reverse delta > on external media (tape, ZIP drive) without consuming much temp disk > space, or even not generating the reverse delta at all for those who > think they aren't interested in it. Absolutely, and these are all in the category of refinements I can see us adding in response to real-life concerns about the delta mechanism. For now, however, I think we're more likely to actually get a working framework written if we assume that disk space is cheap (and it is) and just code straight for functionality right now and use whatever resources we need to do that. There's always time to tie ribbons around it later. > Yep. Now, who's going to become FreeBSD's ``upgrade meister''? I'm willing to work with someone on specifying and coding this, but if I try to do it alone then we're also likely to wait another year for a solution. That's both a threat and a plea for help. :-) Jordan From owner-freebsd-current Sun Dec 8 13:09:51 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA23720 for current-outgoing; Sun, 8 Dec 1996 13:09:51 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA23715 for ; Sun, 8 Dec 1996 13:09:49 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA29411; Sun, 8 Dec 1996 13:48:43 -0700 From: Terry Lambert Message-Id: <199612082048.NAA29411@phaeton.artisoft.com> Subject: Re: last in -current To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sun, 8 Dec 1996 13:48:43 -0700 (MST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org In-Reply-To: <1075.850034047@time.cdrom.com> from "Jordan K. Hubbard" at Dec 8, 96 00:34:07 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 > 1. All deltas have a consistent data format, sequence > numbered, uuencoded, PGP signed and for the benefit of the > migration tools (and easy sending through email). Sounds like tacit approval of PGP technology export. FWIW. 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 Dec 8 13:17:40 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA24043 for current-outgoing; Sun, 8 Dec 1996 13:17:40 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA24038 for ; Sun, 8 Dec 1996 13:17:38 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA29428; Sun, 8 Dec 1996 13:54:47 -0700 From: Terry Lambert Message-Id: <199612082054.NAA29428@phaeton.artisoft.com> Subject: Re: last in -current To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sun, 8 Dec 1996 13:54:47 -0700 (MST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.org In-Reply-To: <5888.850074771@time.cdrom.com> from "Jordan K. Hubbard" at Dec 8, 96 11:52:51 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 > > Hmmpf. Kill your government first. As long as we cannot provide PGP > > as a binary drop-in, this is a moot point. > > Erm, no, it's really not. Even though pgp is something of a pain to > install on both sides of the Atlantic, it's hardly an impossibility > and tools like pgpmail are very popular over here, stupid government > or no. Actually, it's only not a pain on the other side of the Atlantic if the person on the other side of the Atlantic is net-connected, and willing to violate US law (yes, I know, non-US citizens should not be subject to US law; if laws counted in GDP, the US would not have a trade imbalance). It seems to me that you, as a CDROM producer, should not be willing to limit your market to "people with CDROMs AND net connections" (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 Sun Dec 8 13:43:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA25108 for current-outgoing; Sun, 8 Dec 1996 13:43:24 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA25103 for ; Sun, 8 Dec 1996 13:43:22 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA29467; Sun, 8 Dec 1996 14:19:49 -0700 From: Terry Lambert Message-Id: <199612082119.OAA29467@phaeton.artisoft.com> Subject: Re: samba To: jfieber@indiana.edu (John Fieber) Date: Sun, 8 Dec 1996 14:19:49 -0700 (MST) Cc: msmith@atrad.adelaide.edu.au, wangel@wgrobez1.remote.louisville.edu, freebsd-current@freebsd.org In-Reply-To: from "John Fieber" at Dec 8, 96 10:31:23 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 > On Sun, 8 Dec 1996, Michael Smith wrote: > > > Please go back and read the mailing list archives for the meat of the > > last N times this has come up. Searching for 'smbfs' is probably a > > good place to start. Look particularly for Terry's detailed rants on > > the topic. > > To quote from the motd on freefall: > > sd3 passed away at 7:05AM PST. RIP. A replacement drive will be > ordered ASAP. Lots of stuff has died with it, expect chaos for a > while. > > The mailing list archives are among the dead. :( > I just hope some backups exist. Well, I keep everything I post, and everything everyone says in response to one of my posts, and most discussions I find interesting, and most discussions which reveal non-obvious hardware information. So while I don't keep the majority of list traffic, I do keep some, even if I have to edit it down for content occasionally. Here are the most relevent saved pieces from the last SMBFS discussion: ========================================================================= FROM THE MOST COGENT CREDENTIAL MODEL DISCUSSION ========================================================================= | Sorry, but I can't accept "no user level security" as "good enough", | when the SMB model depends on connection credentials to impose the | will of the SMB server administrator. | | What we are arguing here is whether it is acceptable under any | circumstances to subvert the ability of the SMB administrator to | impose his will on his system. | | My answer for that is "no, it's not -- it is his box, and he is God, | what he says must go". | | You can't really balance this with the UNIX model -- that's the | whole point, that the models are not directly interoperable. | | | There are ways around this problem, and in the last set of "go-rounds" | in usenet, I even offered to work on a general soloution -- though not | solely on my own -- to the credential problem. It turns out my | correspondant was more up for arguing about why I should release | crap code instead of wanting to work on good code. I let the thread | die on that note. ========================================================================= THE USENET POSTING REFERENCED ABOVE ========================================================================= | No. I'm suggesting that the client security be implemented like the | Windows 95 password provider interface, where authenticating as a UNIX | user unlocks the users "password cache". | | Then a session manager is established as part of login, and when the | kernel SMBFS needs a password for an SMB server, it asks the session | manager for it. | | The session manager will look in the password cache, which the user can | use to establish pre-authentication information for when it is later | needed, and, if necessary and technically possible (ie: on the console | or an X sever or in a Screen session), the session manager can pop up | a user request to provide authentication information. | | The information can be stored in the cache (at the user's option: | "remember this password"), and will be passed on to the kernel to allow | it to complete the pending request (or deny it, if the authentication | information is incorrect). | | For systems that care about security of password caching, there is | always the ability to turn it off and have the session manager | query the user each time. This (like the UnixWare NUC login) | assumes that there is a covert channel to the user -- UnixWare | assumes the ability to pop up an X requester from the session | manager. | | | Since UNIX cerdentials are identical for multiple sessions, it would | be a good idea to divorce the UNIX credential from the process. This | is a necessary step in B2/B1 certification in any case; however, it | is also possible to cache at the kernel level the credential/session | pair. Thus if a user has two xterms and attempts to access the same | network resource from each of them, he or she is only interrogated once | for verification. | | This same method can be used, seperate from the user credential, to | provide directory and file level password protection in an FS stacking | layer (a B1 requirement). | | | This requires up-front session management implementation, but the | spin-off is well worth it (IMO). | | I'm willing to work on the session management interface. I believe I | am one of the few people outside of Microsoft to have successfully | build a Windows95 password provider interface module. ========================================================================= DETAILED INFORMATION ON THE CREDENTIAL MAPPING PROBLEM ========================================================================= | > Download ksmbfs from: | > ftp://samba.anu.edu.au/pub/samba/contributed/ksmbfs-0.2.4.tgz | | How do you resolve: | | 1) It's GPL'ed code | | 2) It does not allow per-user enforcement of credential mapping | | The first is not really a kicker if it's distributed as an LKM, and the | LKM is not distributed pre-loaded. Its just that you can't sell or | even give away the agregate system because of the license conflicts. | | | The second is a serious issue, since it damages the SMB server | administrators management authority to have all users from a given | UNIX box appear as as a single SMB client. This was my objection | to the SMBFS suggestions I have seen in the past. | | I did an SMBFS for FreeBSD 1.1.5.1 (so it would be a hard port, and | it is code Novell/USG claimed they owned because I was a Novell | employee when I did it on my own time before Novell bought USL). | | The credential problem is significant, and I did not solve it in | my prototype code. | | | IF FreeBSD supported attaching additional credential information to | a session (ie: it had the concept of a session manager, which it | applied to normal console logins, as well as to "screen" and "xdm" | logins), then it would be possible to implement a method of querying | the user asynchronously for the information the kernel needs to | establish a seperate connection credential for the user for a given | mount. | | For remote sessions, and for TTY's, where it is impossible to pop | up a "dialog" without potentially destroying unrecoverable screen | contents, preauthentication would be required. This basically means | adding an EAUTH error code to all pathing operations, and handling | the error return in all programs which invoke those system/library | calls. Then the applications can self-handle querying for authentication | without damaging the application context. There is also the posibility | of a Window95-style "password cache" in this scenario, the cache being | managed by the session manager, and cache unlocking forced at login time | along with standard system login. This incidently buys you the ability | to have password protected directories and files, since the missing | piece for that FS extention is the ability to query the user for | authentication data; same problem, different context. | | | But short of this, porting SMBFS directly is a bad idea, since it damages | existing security models on servers we can't do anything about because | they come from Microsoft, or AT&T, or IBM, etc., and they don't have | source code. There is no way to repair the damage, other than to note | it, and have the SMB server administrator react appropriately (which | is undefined, since the situation never arises without SMBFS rearing | its ugly head). | | If you intentionally go ahead and damage someone else's security model | by making an N:1 mapping of a resource which is, by design, expected | to be 1:1 mapped by a single user client machine, be prepared to take | a lot of heat for doing it. | | This is *exactly* the problem the NUC (NetWare UNIX Client) people at | Novell dealt with in UnixWare, NeXTStep, etc., and exactly the issue | that caused them the most grief in their 20 man year (5 engineers over | 4 years) project to solve the problem uniformly and securely. | | | My offer to help work on a session management interface (made in a | Usenet posting on SMBFS) still stands; there did not seem to be a lot | of interest in resolving the general problem, when a kludge soloution | was so close. 8-(. > > The linux smbfs is, in the tradition of Linux, a festering hack, and > > this isn't exclusively the fault of the implementors. > > Alas, if you rate software on two scales: elegantly engineered > solution to festering hack, and useless to useful, I'd hazzard a > guess that if there is any correlation, it would be positive > (associate the festering hacks with higher utility). I'd have to say that you have neglected the case where utility was a design criteria. 8-). > Non-programmers don't care *how* the programmer implements > something, so long as it works most of the time. Evidence? > Microsoft products. I rest my case. "How are you going to keep them down on the farm after they have seen Paris?" This is a case of them not having high expectations because they have never seen something which would meet high expectations. Once they have seen something like that, their expectations will have been raised. Do you think Microsoft Engineers really *wanted* to work on protected memory interfaces instead of the next API for video games? Do you think they *wanted* to give away networking or Internet Explorer instead of charging for it? They are backing down skirmish lines to retrench... not acting out of choice. CIFS (SMBFS) is to WebNFS as ActiveX Components are to JAVA Applets. 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 Dec 8 13:58:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA25657 for current-outgoing; Sun, 8 Dec 1996 13:58:19 -0800 (PST) Received: from access3.digex.net (qlAGyDS9O5WNg@access3.digex.net [205.197.245.194]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA25636; Sun, 8 Dec 1996 13:58:12 -0800 (PST) Received: from localhost (dnex@localhost) by access3.digex.net (8.8.4/8.8.4) with SMTP id QAA23185; Sun, 8 Dec 1996 16:58:06 -0500 (EST) Date: Sun, 8 Dec 1996 16:58:05 -0500 (EST) From: DNEX X-Sender: dnex@access3.digex.net To: current@freebsd.org, stable@freebsd.org Subject: IP masquerading Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does FreeBSD support IP masquerading or are there plans to implement it? TIA, Kenneth J. Dupuis Senior Consultant DNEX From owner-freebsd-current Sun Dec 8 15:32:39 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA29876 for current-outgoing; Sun, 8 Dec 1996 15:32:39 -0800 (PST) Received: from icicle.winternet.com (adm@icicle.winternet.com [198.174.169.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA29868 for ; Sun, 8 Dec 1996 15:32:36 -0800 (PST) Received: (from adm@localhost) by icicle.winternet.com (8.7.5/8.7.5) id RAA03403 for ; Sun, 8 Dec 1996 17:32:33 -0600 (CST) Posted-Date: Sun, 8 Dec 1996 17:32:33 -0600 (CST) Received: from ppp-67-42.dialup.winternet.com(204.246.67.42) by icicle.winternet.com via smap (V2.0beta) id xma003387; Sun, 8 Dec 96 17:32:21 -0600 Date: Sun, 8 Dec 1996 17:31:25 -0600 () From: Jimbo Bahooli To: freebsd-current@freebsd.org Subject: Possible solution to upgrade problems... Message-ID: X-X-Sender: moke@icicle.winternet.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I do not know if this has already been suggested, or what not but here it goes. I would suggest something like the ports section for upgrades to -RELEASE systems. That way the branch could die but relevant fixes could still be released. A possible setup would be like this, lets say 2.2-RELEASE comes out and is bundled with sendmail 8.8.10. Yet three days later there is a bug found in it. Any 2.2-RELEASE user could then go to /pub/FreeBSD/upgrades-2.2/sendmail download it, it would be similar to a port in structure, then just make it. From owner-freebsd-current Sun Dec 8 16:03:45 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA01633 for current-outgoing; Sun, 8 Dec 1996 16:03:45 -0800 (PST) Received: from wgrobez1.remote.louisville.edu (wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA01612; Sun, 8 Dec 1996 16:03:39 -0800 (PST) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.8.4/8.6.12) with SMTP id TAA04967; Sun, 8 Dec 1996 19:03:53 -0500 (EST) Date: Sun, 8 Dec 1996 19:03:52 -0500 (EST) From: Gary Roberts To: DNEX cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: IP masquerading 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, 8 Dec 1996, DNEX wrote: > Does FreeBSD support IP masquerading or are there plans to implement it? > > TIA, > > Kenneth J. Dupuis > Senior Consultant > DNEX > > Yes. It does. Charles Mott. Nice piece of software. Anyways, it's not a program like linux uses, it uses the PPP program. Check it out at: http://www.srv.net/~cmott/alias.html Real easy to install, and it works beutifully! Thanks Gary Roberts System Admin. -- Altered Reality. http://136.165.243.183 -- Main User Pages From owner-freebsd-current Sun Dec 8 16:04:07 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA01701 for current-outgoing; Sun, 8 Dec 1996 16:04:07 -0800 (PST) Received: from broon.off.connect.com.au (broon.off.connect.com.au [203.63.69.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA01691 for ; Sun, 8 Dec 1996 16:04:03 -0800 (PST) Received: from connect.com.au (ggm@localhost) by broon.off.connect.com.au with ESMTP id KAA14361 (8.7.6h/IDA-1.6 for ); Mon, 9 Dec 1996 10:03:19 +1000 (EST) X-Authentication-Warning: broon.off.connect.com.au: ggm owned process doing -bs X-Mailer: exmh version 1.6.9 8/22/96 To: freebsd-current@freebsd.org Subject: siguing into current from a random version In-reply-to: Your message of "Sun, 08 Dec 1996 17:31:25 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Dec 1996 10:03:18 +1000 Message-ID: <14360.850089798@connect.com.au> From: George Michaelson Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've come into FreeBSD after 2+ years tracking NetBSD. I'm still a bit confused about some procedures. NetBSD has a summary of CVS changes and a rolling README of current state changes similar to RLOG lines from RCS. Does FreeBSD have this kind of summary of changes under CVS? The individual CVS update reports are vital for some people, but for passive drones like me, less useful than something like a ChangeLog which is append-grown. The re-sync to current process is not clear. NetBSD ususally had an indication from known people when re-sync was vital, and irregular checkpoint tarsets existed for people who were nervous of the in-place libc.so upgrade etc etc. -George -- George Michaelson | connect.com.au pty/ltd Email: ggm@connect.com.au | c/o AAPT, Phone: +61 7 3834 9976 | level 8, the Riverside Centre, Fax: +61 7 3834 9908 | 123 Eagle St, Brisbane QLD 4000 From owner-freebsd-current Sun Dec 8 16:23:36 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA02498 for current-outgoing; Sun, 8 Dec 1996 16:23:36 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA02479 for ; Sun, 8 Dec 1996 16:23:30 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id BAA20463 for ; Mon, 9 Dec 1996 01:23:24 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA19152 for freebsd-current@FreeBSD.org; Mon, 9 Dec 1996 01:23:24 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id XAA17852 for freebsd-current@FreeBSD.org; Sun, 8 Dec 1996 23:19:16 +0100 (MET) From: J Wunsch Message-Id: <199612082219.XAA17852@uriah.heep.sax.de> Subject: Re: last in -current To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 8 Dec 1996 23:19:15 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <5888.850074771@time.cdrom.com> from "Jordan K. Hubbard" at "Dec 8, 96 11:52:51 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: > > Hmmpf. Kill your government first. As long as we cannot provide PGP > > as a binary drop-in, this is a moot point. > > Erm, no, it's really not. [...] > Furthermore, even if the tools *ignore* the pgp signature, as > they would in the case where no pgp program was found (and it would > just print a short warning msg that they should install the pgp > program if they want more assurance that what they're doing is > legitimate), we still need to provide it for those people who really > do care. Ok, this sounds reasonable. -- 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 Dec 8 17:03:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA04986 for current-outgoing; Sun, 8 Dec 1996 17:03:20 -0800 (PST) Received: from po2.glue.umd.edu (root@po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA04981 for ; Sun, 8 Dec 1996 17:03:17 -0800 (PST) Received: from downlink.eng.umd.edu (downlink.eng.umd.edu [129.2.98.182]) by po2.glue.umd.edu (8.8.3/8.7.3) with ESMTP id UAA01378; Sun, 8 Dec 1996 20:03:13 -0500 (EST) Received: from localhost (chuckr@localhost) by downlink.eng.umd.edu (8.8.3/8.7.3) with SMTP id UAA10151; Sun, 8 Dec 1996 20:03:13 -0500 (EST) X-Authentication-Warning: downlink.eng.umd.edu: chuckr owned process doing -bs Date: Sun, 8 Dec 1996 20:03:12 -0500 (EST) From: Chuck Robey X-Sender: chuckr@downlink.eng.umd.edu To: George Michaelson cc: freebsd-current@freebsd.org Subject: Re: siguing into current from a random version In-Reply-To: <14360.850089798@connect.com.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, 9 Dec 1996, George Michaelson wrote: > > > I've come into FreeBSD after 2+ years tracking NetBSD. I'm still a bit > confused about some procedures. > > NetBSD has a summary of CVS changes and a rolling README of current state > changes similar to RLOG lines from RCS. Does FreeBSD have this kind of > summary of changes under CVS? The individual CVS update reports are vital > for some people, but for passive drones like me, less useful than something > like a ChangeLog which is append-grown. > > The re-sync to current process is not clear. NetBSD ususally had an indication > from known people when re-sync was vital, and irregular checkpoint tarsets > existed for people who were nervous of the in-place libc.so upgrade etc etc. I've never tracked NetBSD, so I'm not sure, but I think maybe that CVSROOT/commitlogs, which has the commit logs broken up by top level directories, has what you're asking for, a log of all commits made. We don't explicitly make tars when things change, probably because those changes are often accompanied by a short period of some level of broken-ness, while bugs are found. Instead, we have snaps, for those who don't want to track current totally, but who want to stay reasonably close, and contribute error reports. Snaps are usually done during periods of relative stability, so maybe that's what you're asking for? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Sun Dec 8 17:10:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA05302 for current-outgoing; Sun, 8 Dec 1996 17:10:30 -0800 (PST) Received: from broon.off.connect.com.au (broon.off.connect.com.au [203.63.69.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA05296 for ; Sun, 8 Dec 1996 17:10:26 -0800 (PST) Received: from connect.com.au (ggm@localhost) by broon.off.connect.com.au with ESMTP id LAA15136 (8.7.6h/IDA-1.6); Mon, 9 Dec 1996 11:09:03 +1000 (EST) X-Authentication-Warning: broon.off.connect.com.au: ggm owned process doing -bs To: Chuck Robey cc: freebsd-current@freebsd.org Subject: Re: siguing into current from a random version In-reply-to: Your message of "Sun, 08 Dec 1996 20:03:12 EST." Date: Mon, 09 Dec 1996 11:09:03 +1000 Message-ID: <15134.850093743@connect.com.au> From: George Michaelson Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Snaps are good but the timelag between snaps and interesting state in current is bad. If you're saying that for any given SUP state you can go from the last snap to current without tripping over any non-reversable states, well and good. I don't think you're saying that :-) I suppose an assumption many neophytes like myself make is that CVS commits happen to complete sets of *tested* changes and not work in progress, so that the worst-case state is the testing (by author/cvs-changer) didn't cover for ones own particular setup and circumstances. Looks like you're saying its more fluid, and simply doing a make world on the result of a sup on current is caveat emptor. I can handle that, if there is some indication in the logs/readmes/mail to say when its known current is unrunnable. Thats kinda what the NetBSD doc/CHANGES is all about: things in there reflect coarser grain documentation than individual CVS commits. By the time its logged there, its probably 1/2 way stable. It looks to me like the best bet for a time to re-sync is the xmas holidays since the frequency of changes to CVS will be lower... -George From owner-freebsd-current Sun Dec 8 17:32:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA06168 for current-outgoing; Sun, 8 Dec 1996 17:32:18 -0800 (PST) Received: from po1.glue.umd.edu (root@po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA06163 for ; Sun, 8 Dec 1996 17:32:15 -0800 (PST) Received: from downlink.eng.umd.edu (downlink.eng.umd.edu [129.2.98.182]) by po1.glue.umd.edu (8.8.3/8.7.3) with ESMTP id UAA05778; Sun, 8 Dec 1996 20:32:07 -0500 (EST) Received: from localhost (chuckr@localhost) by downlink.eng.umd.edu (8.8.3/8.7.3) with SMTP id UAA10166; Sun, 8 Dec 1996 20:32:06 -0500 (EST) X-Authentication-Warning: downlink.eng.umd.edu: chuckr owned process doing -bs Date: Sun, 8 Dec 1996 20:32:05 -0500 (EST) From: Chuck Robey X-Sender: chuckr@downlink.eng.umd.edu To: George Michaelson cc: freebsd-current@freebsd.org Subject: Re: siguing into current from a random version In-Reply-To: <15134.850093743@connect.com.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, 9 Dec 1996, George Michaelson wrote: > > Snaps are good but the timelag between snaps and interesting state in current > is bad. If you're saying that for any given SUP state you can go from the > last snap to current without tripping over any non-reversable states, well > and good. I don't think you're saying that :-) > > I suppose an assumption many neophytes like myself make is that CVS commits > happen to complete sets of *tested* changes and not work in progress, so that > the worst-case state is the testing (by author/cvs-changer) didn't cover for > ones own particular setup and circumstances. > > Looks like you're saying its more fluid, and simply doing a make world on > the result of a sup on current is caveat emptor. It's laid out honestly in the handbook, current is NOT guaranteed buildable, and has in recent memory gone through some fairly rough periods of unbuildability. It's been fairly stable lately, but folks shouldn't assume that's a permanent thing, it's simply chance. If you can't risk outage, and you don't enjoy helping to find bugs, then you probably should avoid current. Snaps are halfway stable, but they're more in the way of beta releases, before actual releases. > I can handle that, if there is some indication in the logs/readmes/mail to > say when its known current is unrunnable. To find that out, subscribe to the commit lists, which anyone running current should absolutely do anyhow. There AREN'T announcements that say "it's stable now", but there are often announcements of the type "this'll breaks things, do this to correct it". > Thats kinda what the NetBSD doc/CHANGES is all about: things in there reflect > coarser grain documentation than individual CVS commits. By the time its > logged there, its probably 1/2 way stable. > > It looks to me like the best bet for a time to re-sync is the xmas holidays > since the frequency of changes to CVS will be lower... No. If you don't want to find bugs, don't resync to current, ever. They do come up, and there won't be apologies, that's what current is for, putting things out for test. Like I said, current is stable now, but in 6 hours, who knows? Snaps might be safer for you. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Sun Dec 8 17:43:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA06812 for current-outgoing; Sun, 8 Dec 1996 17:43:31 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA06807 for ; Sun, 8 Dec 1996 17:43:29 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id RAA04389; Sun, 8 Dec 1996 17:41:34 -0800 (PST) Message-Id: <199612090141.RAA04389@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: George Michaelson cc: Chuck Robey , freebsd-current@freebsd.org Subject: Re: siguing into current from a random version In-reply-to: Your message of "Mon, 09 Dec 1996 11:09:03 +1000." <15134.850093743@connect.com.au> From: David Greenman Reply-To: dg@root.com Date: Sun, 08 Dec 1996 17:41:34 -0800 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I suppose an assumption many neophytes like myself make is that CVS commits >happen to complete sets of *tested* changes and not work in progress, so that >the worst-case state is the testing (by author/cvs-changer) didn't cover for >ones own particular setup and circumstances. That's the ideal, but we all make mistakes. >Looks like you're saying its more fluid, and simply doing a make world on >the result of a sup on current is caveat emptor. More or less, but we do usually send out warnings about specific things that will need to be rebuilt or special build procedures that need to be followed when they are needed. >I can handle that, if there is some indication in the logs/readmes/mail to >say when its known current is unrunnable. Commits aren't supposed to be done unless the code has been tested first. There is an exception that is sometimes allowed when the code being worked on isn't part of the main-line stuff. >Thats kinda what the NetBSD doc/CHANGES is all about: things in there reflect >coarser grain documentation than individual CVS commits. By the time its >logged there, its probably 1/2 way stable. We had considered doing this at one point, but eventually decided that it was too much work to maintain and now we just make people read the commit messages...which tend to be higher quality than our counterparts (my opinion of course). >It looks to me like the best bet for a time to re-sync is the xmas holidays >since the frequency of changes to CVS will be lower... That's what you think. :-) -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Sun Dec 8 17:48:53 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA07351 for current-outgoing; Sun, 8 Dec 1996 17:48:53 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA07345 for ; Sun, 8 Dec 1996 17:48:50 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id MAA05793; Mon, 9 Dec 1996 12:18:11 +1030 (CST) From: Michael Smith Message-Id: <199612090148.MAA05793@genesis.atrad.adelaide.edu.au> Subject: Re: siguing into current from a random version In-Reply-To: <15134.850093743@connect.com.au> from George Michaelson at "Dec 9, 96 11:09:03 am" To: ggm@connect.com.au (George Michaelson) Date: Mon, 9 Dec 1996 12:18:10 +1030 (CST) Cc: chuckr@glue.umd.edu, freebsd-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 George Michaelson stands accused of saying: > > Snaps are good but the timelag between snaps and interesting state in current > is bad. If you're saying that for any given SUP state you can go from the > last snap to current without tripping over any non-reversable states, well > and good. I don't think you're saying that :-) The general rule is that you can build -CURRENT from the last -RELEASE version, and modulo short periods of brokenness in -CURRENT, this is a fairly safe assumption. The FreeBSD build is a lot more involved than the NetBSD build (as you will have noticed if you've looked at /usr/src/Makefile). Considerable care is taken to build tools that are required for the build process itself first. My current qualification process for systems involves installing an old SNAP (whatever I can get my hands on at the time 8), doing a checkout from our CVS server of the source tree and then a full 'make world'. > Looks like you're saying its more fluid, and simply doing a make world on > the result of a sup on current is caveat emptor. No, this is not the case; commits that break the tree generate enormous amounts of flamage on the -current list, and usually a correcting commit that gets in first 8) Most of the complaints on the -current list come from people with broken source trees; either as a result of sup malfunctioning, local changes, or passionate fingers. CVSup has drastically reduced the incidence of the first case. > It looks to me like the best bet for a time to re-sync is the xmas holidays > since the frequency of changes to CVS will be lower... Depending on what you want to sync _to_; if you're using CVSup (as I strongly recommend 8), grab the whole CVS tree and check out at RELENG_2_2 to get the 2.2 soon-to-be-release thread for an up-to-date-and-stable version, or go to the head for the 3.0 major-changes-impending thread. Generally large changes are announced on the -current list, which you should be reading if you're planning on tracking -current. The commit mailing lists are also worth watching if you have the time. > -George -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Sun Dec 8 18:24:51 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA10834 for current-outgoing; Sun, 8 Dec 1996 18:24:51 -0800 (PST) Received: from sed.cs.fsu.edu (sed.cs.fsu.edu [128.186.121.157]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA10789 for ; Sun, 8 Dec 1996 18:24:48 -0800 (PST) Received: by sed.cs.fsu.edu (8.8.3/56) id CAA05321; Mon, 9 Dec 1996 02:24:45 GMT From: Gang-Ryung Uh Message-Id: <199612090224.CAA05321@sed.cs.fsu.edu> Subject: w To: current@freebsd.org Date: Sun, 8 Dec 1996 21:24:44 -0500 (EST) 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 Hello, I downloaded freebsd-current at Dec 8, made world, and make kernel. Now, I have a couple of problems. First, "w" seems to be broken. Second, "kaffe" is not working... Would you tell me what I have done wrong? Thanks. Regards, Gang-Ryung Uh From owner-freebsd-current Sun Dec 8 19:58:25 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA21081 for current-outgoing; Sun, 8 Dec 1996 19:58:25 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA21072 for ; Sun, 8 Dec 1996 19:58:23 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id TAA06916; Sun, 8 Dec 1996 19:56:52 -0800 (PST) To: Terry Lambert cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org Subject: Re: last in -current In-reply-to: Your message of "Sun, 08 Dec 1996 13:48:43 MST." <199612082048.NAA29411@phaeton.artisoft.com> Date: Sun, 08 Dec 1996 19:56:52 -0800 Message-ID: <6912.850103812@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > 1. All deltas have a consistent data format, sequence > > numbered, uuencoded, PGP signed and for the benefit of the > > migration tools (and easy sending through email). > > Sounds like tacit approval of PGP technology export. FWIW. There are foreign sites from which PGP technology may be obtained. FWIW, I *do* approve of PGP technology being exported but it's also hardly necessary at this stage. Jordan From owner-freebsd-current Sun Dec 8 20:05:47 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA21884 for current-outgoing; Sun, 8 Dec 1996 20:05:47 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA21867 for ; Sun, 8 Dec 1996 20:05:45 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id UAA28226 for ; Sun, 8 Dec 1996 20:06:03 -0800 (PST) Received: (qmail 4549 invoked by uid 110); 9 Dec 1996 04:05:15 -0000 Message-ID: <19961209040514.4547.qmail@suburbia.net> Subject: Re: strange problems with recent current In-Reply-To: <199612090319.OAA12973@godzilla.zeta.org.au> from Bruce Evans at "Dec 9, 96 02:19:33 pm" To: bde@zeta.org.au (Bruce Evans) Date: Mon, 9 Dec 1996 15:05:14 +1100 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >Dec 8 02:37:59 evil /kernel: cy15: 5 more silo overflows (total 3876) > >Dec 8 02:38:00 evil /kernel: cy8: 1 more silo overflow (total 7) > >... > >This has crept in sometime during the past few days. > > On what hardware? The PCI cy driver doesn't use a "fast" interrupt > handler yet, so silo overflows are quite likely for it. E.g., updating > the keyboard LEDs takes a few msec, so a few fifos full of input may > be dropped on each port whenever you hit caps lock (the fifo fills up > in 1 msec at 115200 bps). P100/Triton mother board. 4 Triton/mb IDE drives, two scsi (ISA adaptec), average 120 procs, 72Mb swap used (striped over the 4 ide drives). This configuration hasn't changed, and I don't use the console keyboard, infact..the console keyboard has been unplugged (could this have any effect?) > >Previously cy.c > >would suffer silo overflows far more rarely (once every 10-30 seconds > >on average) and overflows quantities were never over 2 or 3. > > One per day is too many. cy15 is often going at 57.6k in both directions, the others are more sporadic typical dial-up-user traffic (at 38.4). I moved cy15 onto sio1 (on board 16550A uart) Dec 9 14:58:16 suburbia /kernel: sio1: 1 more silo overflow (total 17190) Dec 9 14:58:21 suburbia /kernel: cy0: 2 more silo overflows (total 220) Dec 9 14:58:21 suburbia /kernel: sio1: 1 more silo overflow (total 17191) Dec 9 14:58:29 suburbia /kernel: sio1: 1 more silo overflow (total 17192) Dec 9 14:58:38 suburbia /kernel: sio1: 1 more silo overflow (total 17193) (uptime 16 hours) This is actually quite a bit better than the cyclades (could just be the 12 vs 15 byte byffer) but still worse than the cyclades before the "slow down". > >Response time generally has suffered, even with a very low load. Feels > >like some kind of excessive context switching delay. > > I haven't noticed any new problems here on a lightly loaded 486/33 system. > > Bruce > Load average is typically around 0.16 Cheers, Julian. From owner-freebsd-current Sun Dec 8 20:40:29 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA25843 for current-outgoing; Sun, 8 Dec 1996 20:40:29 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA25832 for ; Sun, 8 Dec 1996 20:40:26 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id XAA21708; Sun, 8 Dec 1996 23:38:47 -0500 (EST) From: "John S. Dyson" Message-Id: <199612090438.XAA21708@dyson.iquest.net> Subject: Re: siguing into current from a random version To: dg@root.com Date: Sun, 8 Dec 1996 23:38:42 -0500 (EST) Cc: ggm@connect.com.au, chuckr@glue.umd.edu, freebsd-current@FreeBSD.ORG In-Reply-To: <199612090141.RAA04389@root.com> from "David Greenman" at Dec 8, 96 05:41:34 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 > > >It looks to me like the best bet for a time to re-sync is the xmas holidays > >since the frequency of changes to CVS will be lower... > > That's what you think. :-) > Isn't xmas time when all of us with non-FreeBSD jobs have plenty of time to write code? :-). John From owner-freebsd-current Sun Dec 8 20:54:37 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA27440 for current-outgoing; Sun, 8 Dec 1996 20:54:37 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA27424 for ; Sun, 8 Dec 1996 20:54:35 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id UAA28825 for ; Sun, 8 Dec 1996 20:54:58 -0800 (PST) Received: (qmail 5229 invoked by uid 110); 9 Dec 1996 04:54:08 -0000 Message-ID: <19961209045408.5228.qmail@suburbia.net> Subject: Re: strange problems with recent current In-Reply-To: <199612090445.UAA20757@root.com> from David Greenman at "Dec 8, 96 08:45:13 pm" To: dg@root.com Date: Mon, 9 Dec 1996 15:54:08 +1100 (EST) Cc: hackers@freebsd.org, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Bruce means: Are you using the ISA Cyclades board or the PCI Cyclades > board? > > -DG PCI From owner-freebsd-current Sun Dec 8 20:58:28 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA27987 for current-outgoing; Sun, 8 Dec 1996 20:58:28 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA27982; Sun, 8 Dec 1996 20:58:25 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id UAA21328; Sun, 8 Dec 1996 20:57:56 -0800 (PST) Message-Id: <199612090457.UAA21328@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: proff@suburbia.net cc: hackers@freebsd.org, current@freebsd.org Subject: Re: strange problems with recent current In-reply-to: Your message of "Mon, 09 Dec 1996 15:54:08 +1100." <19961209045408.5228.qmail@suburbia.net> From: David Greenman Reply-To: dg@root.com Date: Sun, 08 Dec 1996 20:57:56 -0800 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Bruce means: Are you using the ISA Cyclades board or the PCI Cyclades >> board? >> >> -DG > >PCI Okay, then you definately want to get "cytest" and change the shared memory mapping address to >1MB. That should make the accesses to the card several times faster than they are now. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Sun Dec 8 23:40:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA13640 for current-outgoing; Sun, 8 Dec 1996 23:40:19 -0800 (PST) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id XAA13633 for ; Sun, 8 Dec 1996 23:40:18 -0800 (PST) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0vX0IS-0003wtC; Sun, 8 Dec 96 23:38 PST Received: from critter.tfs.com (localhost.phk.dk [127.0.0.1]) by critter.tfs.com (8.8.2/8.8.2) with ESMTP id IAA15525; Mon, 9 Dec 1996 08:40:33 +0100 (MET) To: George Michaelson cc: Chuck Robey , freebsd-current@freebsd.org Subject: Re: siguing into current from a random version In-reply-to: Your message of "Mon, 09 Dec 1996 11:09:03 +1000." <15134.850093743@connect.com.au> Date: Mon, 09 Dec 1996 08:40:32 +0100 Message-ID: <15523.850117232@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <15134.850093743@connect.com.au>, George Michaelson writes: > >Snaps are good but the timelag between snaps and interesting state in current >is bad. If you're saying that for any given SUP state you can go from the >last snap to current without tripping over any non-reversable states, well >and good. I don't think you're saying that :-) Well, the snaps are supposed to happen about every other month or so... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-current Mon Dec 9 00:25:14 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA17236 for current-outgoing; Mon, 9 Dec 1996 00:25:14 -0800 (PST) Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA17218 for ; Mon, 9 Dec 1996 00:25:07 -0800 (PST) Received: (from root@localhost) by btp1da.phy.uni-bayreuth.de (8.8.4/8.7.3) id JAA27943; Mon, 9 Dec 1996 09:24:18 +0100 (CET) From: Werner Griessl Message-Id: <199612090824.JAA27943@btp1da.phy.uni-bayreuth.de> Subject: Re: rdump slow In-Reply-To: <199612072019.VAA22287@uriah.heep.sax.de> from J Wunsch at "Dec 7, 96 09:19:54 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 9 Dec 1996 09:24:18 +0100 (CET) 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 > As Werner Griessl wrote: > > > rdump in current is very slow, should be ~5 times faster : > > > > Wed Dec 4 09:57:01 1996 start btp1da:system_save to btp1x5:/dev/nrmt0h > > Wed Dec 4 09:57:01 1996 rewinding tape > > Wed Dec 4 09:57:07 1996 #1 rdump / ... > > > DUMP: DUMP: 21409 tape blocks on 1 volumes(s) > > > > DUMP: finished in 430 seconds, throughput 49 KBytes/sec > > ^^^^^^^^^^^^^ !!!!! > > I can't confirm this. What's your blocksize? What system is the > remote TCP peer? Is the tape streaming? > Blocksize is the default (10), remote system is a DEC-alpha 3000/600, tape is a HP-DAT 35480 with local transfer-rate ~250 kb/sec . > That's what i get here: > > j@uriah 1523% /sbin/dump 0Bbf 5000000 32 localhost:/dev/rst0 / > ... > DUMP: DUMP: 20154 tape blocks on 1 volumes(s) > DUMP: finished in 53 seconds, throughput 380 KBytes/sec > ... > j@uriah 1524% /sbin/dump 0Bbf 5000000 32 /dev/rst0 / > ... > DUMP: DUMP: 20154 tape blocks on 1 volumes(s) > DUMP: finished in 53 seconds, throughput 380 KBytes/sec > > So of course, it's been the loopback device, but as long as the > Ethernet card in question can handle 380 KB/s (which is not very > much), the limiting factor is obviously the tape here. (It's a > QIC-2.5GB w/ compression in a Tandberg drive. The 380 KB/s is a > normal rate there.) > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > From owner-freebsd-current Mon Dec 9 00:36:11 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA17935 for current-outgoing; Mon, 9 Dec 1996 00:36:11 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA17930 for ; Mon, 9 Dec 1996 00:36:07 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id AAA03275; Mon, 9 Dec 1996 00:35:33 -0800 (PST) To: Poul-Henning Kamp cc: George Michaelson , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: siguing into current from a random version In-reply-to: Your message of "Mon, 09 Dec 1996 08:40:32 +0100." <15523.850117232@critter.tfs.com> Date: Mon, 09 Dec 1996 00:35:33 -0800 Message-ID: <3271.850120533@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Well, the snaps are supposed to happen about every other month or so... Actually, I think we settled on once every 3 months. More than that and they get kind of annoying to do. :-) 3.0 probably won't see a SNAP until almost February or March, probably, the justification for that being that there's probably not going to be a heck of a lot of *difference* between 2.2-RELEASE and 3.0-current for at least another couple of months. I could be proven wrong, in which case a SNAP will be done sooner, but the degree of significant divergence to date has been small. Jordan From owner-freebsd-current Mon Dec 9 00:53:57 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA20229 for current-outgoing; Mon, 9 Dec 1996 00:53:57 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id AAA20206 for ; Mon, 9 Dec 1996 00:53:38 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA02991; Mon, 9 Dec 1996 09:53:22 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA26371; Mon, 9 Dec 1996 09:53:21 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id JAA21614; Mon, 9 Dec 1996 09:24:28 +0100 (MET) From: J Wunsch Message-Id: <199612090824.JAA21614@uriah.heep.sax.de> Subject: Re: w To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 9 Dec 1996 09:24:28 +0100 (MET) Cc: uh@sed.cs.fsu.edu (Gang-Ryung Uh) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612090224.CAA05321@sed.cs.fsu.edu> from Gang-Ryung Uh at "Dec 8, 96 09:24:44 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 Gang-Ryung Uh wrote: > I downloaded freebsd-current at Dec 8, made world, and make > kernel. Now, I have a couple of problems. First, "w" seems > to be broken. Second, "kaffe" is not working... > > Would you tell me what I have done wrong? As for the no longer working `w' command: your fault is that you haven't read the -current mailing list as you're supposed to. The utmp/wtmp structure changes have been discussed in full beauty. As for kaffe, i don't know. -- 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 Dec 9 00:55:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA20435 for current-outgoing; Mon, 9 Dec 1996 00:55:18 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id AAA20371 for ; Mon, 9 Dec 1996 00:55:15 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA03003; Mon, 9 Dec 1996 09:53:27 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA26377; Mon, 9 Dec 1996 09:53:26 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id JAA21768; Mon, 9 Dec 1996 09:47:34 +0100 (MET) From: J Wunsch Message-Id: <199612090847.JAA21768@uriah.heep.sax.de> Subject: Re: siguing into current from a random version To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 9 Dec 1996 09:47:34 +0100 (MET) Cc: ggm@connect.com.au (George Michaelson) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <15134.850093743@connect.com.au> from George Michaelson at "Dec 9, 96 11:09:03 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 George Michaelson wrote: > I can handle that, if there is some indication in the logs/readmes/mail to > say when its known current is unrunnable. Read the -current mailing list. Brokeness is being discussed there. If you fear of the breakage, the SNAPs are indeed for you (regardless of whether you take the official ones, or just build the system after checking out from CVS -- remember, unlike NetBSD, you can continously upgrade your CVS mirror to the master CVS). The SNAPs are usually taken if the current state of affairs indicate a rather painless system. They can be as close together as one month. -- 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 Dec 9 01:24:12 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA22428 for current-outgoing; Mon, 9 Dec 1996 01:24:12 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id BAA22422 for ; Mon, 9 Dec 1996 01:24:06 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA05147; Mon, 9 Dec 1996 10:23:54 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA26857; Mon, 9 Dec 1996 10:23:54 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id KAA22223; Mon, 9 Dec 1996 10:08:44 +0100 (MET) From: J Wunsch Message-Id: <199612090908.KAA22223@uriah.heep.sax.de> Subject: Re: rdump slow To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 9 Dec 1996 10:08:44 +0100 (MET) Cc: croot@btp1da.phy.uni-bayreuth.de (Werner Griessl) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612090824.JAA27943@btp1da.phy.uni-bayreuth.de> from Werner Griessl at "Dec 9, 96 09:24:18 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 Werner Griessl wrote: > > > DUMP: finished in 430 seconds, throughput 49 KBytes/sec > > > ^^^^^^^^^^^^^ !!!!! > > > > I can't confirm this. What's your blocksize? What system is the > > remote TCP peer? Is the tape streaming? > > > > Blocksize is the default (10), remote system is a DEC-alpha 3000/600, > tape is a HP-DAT 35480 with local transfer-rate ~250 kb/sec . Do you get the same slow througput when using rsh/dd for the tape? What does GNUtar's ``-f remote:/dev/ice'' yield? Does increasing the blocksize e.g. to 32 improve anything? Which throughput would you get to /dev/null on the remote machine? Questions, questions, questions. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Dec 9 02:04:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA25635 for current-outgoing; Mon, 9 Dec 1996 02:04:04 -0800 (PST) Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA25618 for ; Mon, 9 Dec 1996 02:03:53 -0800 (PST) Received: (from root@localhost) by btp1da.phy.uni-bayreuth.de (8.8.4/8.7.3) id LAA16976; Mon, 9 Dec 1996 11:03:10 +0100 (CET) From: Werner Griessl Message-Id: <199612091003.LAA16976@btp1da.phy.uni-bayreuth.de> Subject: Re: rdump slow solved In-Reply-To: <199612090908.KAA22223@uriah.heep.sax.de> from J Wunsch at "Dec 9, 96 10:08:44 am" To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 9 Dec 1996 11:03:10 +0100 (CET) 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 > As Werner Griessl wrote: > > > > > DUMP: finished in 430 seconds, throughput 49 KBytes/sec > > > > ^^^^^^^^^^^^^ !!!!! > > > > > > I can't confirm this. What's your blocksize? What system is the > > > remote TCP peer? Is the tape streaming? > > > > > > > Blocksize is the default (10), remote system is a DEC-alpha 3000/600, > > tape is a HP-DAT 35480 with local transfer-rate ~250 kb/sec . > > Do you get the same slow througput when using rsh/dd for the tape? > What does GNUtar's ``-f remote:/dev/ice'' yield? Does increasing the > blocksize e.g. to 32 improve anything? > > Which throughput would you get to /dev/null on the remote machine? > Questions, questions, questions. > Thanks for the hints, Joerg ! Changing the blocksize to 32 was the solution . Have now with "rdump 0uBbf 1000000 32 ....": DUMP: finished in 79 seconds, throughput 283 KBytes/sec ^^^^^^^^^^^^^^ Werner > -- > 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 Dec 9 05:04:37 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA02462 for current-outgoing; Mon, 9 Dec 1996 05:04:37 -0800 (PST) Received: from jalopeno.nixu.fi (jalopeno.nixu.fi [194.197.118.20]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA02457 for ; Mon, 9 Dec 1996 05:04:33 -0800 (PST) Received: (from hawk@localhost) by jalopeno.nixu.fi (8.8.3/8.8.3) id PAA01942 for freebsd-current@freebsd.org; Mon, 9 Dec 1996 15:03:58 +0200 (EET) From: Marko Lamminen Message-Id: <199612091303.PAA01942@jalopeno.nixu.fi> Subject: problems with reinstall... To: freebsd-current@freebsd.org Date: Mon, 9 Dec 1996 15:03:56 +0200 (EET) Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I recently begun keeping up with -current (once again) as I finally got my new machine that has power enough to compile world at a decent time. Everything went fine until I decided to install current to my other freebsd (old 486-66) too mounting the source and obj trees from the faster machine and doing reinstall. The machine I was upgrading was a few months old -current. First problem was that gzcat insisted that some of the manual page packages were invalid format (altough they worked on the nfs server which was already running 3.0-current) this not being very serious I installed a new kernel (which I had compiled in the faster machine but with config that was made for the 486) and rebooted the system. Reboot went fine until it was time to mount root_device writabe, mount gave a bus error and nothing I could do to mount root writable. Also trying an update on any other fs would also result in bus error and most strange was that 'man mount' also gave a bus error but for example 'man ls' worked just fine. Since the only real difference between the two machine was the kernel I first suspected it but could find no flaws in the config and am now totally clueless as what might be causing this. I would be more than happy to get any suggestion on which way to look for trouble. I even tried booting the old 2.2 kernel but that resulted in the same errors. The 486 machine has 1542 adaptec scsi and a 4 gig seagate hawk4. I'm currently booting this system with fbsdboot.exe from dos due to some exotic partition configurations but this shouldn't matter as it used to work just as same and the kernel does load corretly (or atleast seems to load corretly). Problem number two: There seems to some incompability problem with my faster machine and the curretn bootloader since if I try to boot the system normally it hangs right after loading the kernel but using fbsdboot.exe from dos the booting goes just fine. The machine is a Asus double Pentium Pro motherboard (passive mb, two pentium pro card) and I'm using on board IDE as harddisk controller. I have 64M of FPM installed. This might be due to some bios setting but disabling every bios option I could think of causing this didn't change anything. More detailed system configurations/software/bios setting are available if they are needed. (I'm at school and the machines are at home) - Marko Lamminen (hawk@nixu.fi) From owner-freebsd-current Mon Dec 9 06:04:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA04190 for current-outgoing; Mon, 9 Dec 1996 06:04:41 -0800 (PST) Received: from friley216.res.iastate.edu (friley216.res.iastate.edu [129.186.78.216]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA04185 for ; Mon, 9 Dec 1996 06:04:39 -0800 (PST) Received: from friley216.res.iastate.edu (loopback [127.0.0.1]) by friley216.res.iastate.edu (8.8.3/8.7.3) with ESMTP id IAA00305; Mon, 9 Dec 1996 08:03:27 -0600 (CST) Message-Id: <199612091403.IAA00305@friley216.res.iastate.edu> X-Mailer: exmh version 1.6.9 8/22/96 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@freebsd.org (FreeBSD-current users) Subject: Re: mfs module -- seems to work.. In-reply-to: Your message of Sun, 08 Dec 1996 09:36:41 +0100. <199612080838.JAA29083@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Dec 1996 08:03:26 -0600 From: Chris Csanady Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I've noticed the following bogosities: > >. mount_mfs without previously loading the lkm causes: > > mount_mfs: /mnt: Operation not supported by device > /kernel: pid 28996 (mount_mfs), uid 0: exited on signal 11\ > (core dumped) > > (It's supposed to first load the lkm.) Ok. I did some looking into this, and now I am really stumped. There seems to be something quite strange afoot here. :\ I have traced the problem to vfsload(). (/usr/src/lib/libc/gen/getvfsent.c:233) It would seem that the chdir() call is failing on a bad file descriptor!? Does anyone have any ideas why this might happen? How a chdir("/var/tmp") ever fail? --Chris Csanady >. Loading it manually, and call mount_mfs then worked. However, > attempts to umount it hung (interruptible), and i had to kill > off the `mfs' process manually. Ive not noticed this one.. > >-- >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 Dec 9 06:14:25 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA04777 for current-outgoing; Mon, 9 Dec 1996 06:14:25 -0800 (PST) Received: from friley216.res.iastate.edu (friley216.res.iastate.edu [129.186.78.216]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA04772 for ; Mon, 9 Dec 1996 06:14:23 -0800 (PST) Received: from friley216.res.iastate.edu (loopback [127.0.0.1]) by friley216.res.iastate.edu (8.8.3/8.7.3) with ESMTP id IAA00418; Mon, 9 Dec 1996 08:14:23 -0600 (CST) Message-Id: <199612091414.IAA00418@friley216.res.iastate.edu> X-Mailer: exmh version 1.6.9 8/22/96 cc: freebsd-current@freebsd.org, j@uriah.heep.sax.de Subject: Re: mfs module -- seems to work.. In-reply-to: Your message of Sat, 07 Dec 1996 16:39:51 -0600. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Dec 1996 08:14:22 -0600 From: Chris Csanady Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ignore my previous post please. :) I really should make it a policy not to post quite so early in the morning.. Chris From owner-freebsd-current Mon Dec 9 07:15:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA08584 for current-outgoing; Mon, 9 Dec 1996 07:15:24 -0800 (PST) Received: from utgard.hos.net (utgard.hos.net [205.238.129.45]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA08579 for ; Mon, 9 Dec 1996 07:15:21 -0800 (PST) Received: (from faulkner@localhost) by utgard.hos.net (8.8.4/8.7.3) id JAA18492; Mon, 9 Dec 1996 09:15:17 -0600 (CST) Message-ID: Date: Mon, 9 Dec 1996 09:15:17 -0600 From: faulkner@asgard.hos.net (Boyd R. Faulkner) To: current@freebsd.org Subject: wtmp X-Mailer: Mutt 0.53-export Mime-Version: 1.0 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk wtmp is broken with respect to two ports (I have found so far). ssh, which is fixed by a simple recompile, and install. wu-ftpd, which is not. I suspect there may be more but I have not found the culprit, yet. Boyd -- _____________________________________________________________________________ Boyd Faulkner "The fates lead him who will; faulkner@asgard.hos.net Him who won't, they drag." http://asgard.hos.net/~faulkner Old Roman Saying -- Source: Joseph Campbell _____________________________________________________________________________ From owner-freebsd-current Mon Dec 9 07:21:37 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA09058 for current-outgoing; Mon, 9 Dec 1996 07:21:37 -0800 (PST) Received: from utgard.hos.net (utgard.hos.net [205.238.129.45]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA09050 for ; Mon, 9 Dec 1996 07:21:33 -0800 (PST) Received: (from faulkner@localhost) by utgard.hos.net (8.8.4/8.7.3) id JAA18541; Mon, 9 Dec 1996 09:21:31 -0600 (CST) Message-ID: Date: Mon, 9 Dec 1996 09:21:31 -0600 From: faulkner@asgard.hos.net (Boyd R. Faulkner) To: current@freebsd.org Subject: wtmp and wu-ftpd X-Mailer: Mutt 0.53-export Mime-Version: 1.0 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I said that wtmp broke wu-ftpd and a simple recompile did not fix it. I was wrong. The installation point has moved since I compiled it last and I tested the wrong version. A simple recompile and install fixes it. Boyd -- _____________________________________________________________________________ Boyd Faulkner "The fates lead him who will; faulkner@asgard.hos.net Him who won't, they drag." http://asgard.hos.net/~faulkner Old Roman Saying -- Source: Joseph Campbell _____________________________________________________________________________ From owner-freebsd-current Mon Dec 9 07:41:22 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA11501 for current-outgoing; Mon, 9 Dec 1996 07:41:22 -0800 (PST) Received: from sdev.usn.blaze.net.au (sdev.usn.blaze.net.au [203.17.53.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA11495 for ; Mon, 9 Dec 1996 07:41:16 -0800 (PST) Received: (from davidn@localhost) by sdev.usn.blaze.net.au (8.8.4/8.6.9) id CAA01876; Tue, 10 Dec 1996 02:40:55 +1100 (EST) Message-ID: Date: Tue, 10 Dec 1996 02:40:54 +1100 From: davidn@sdev.usn.blaze.net.au (David Nugent) To: faulkner@asgard.hos.net (Boyd R. Faulkner) Cc: current@freebsd.org Subject: Re: wtmp References: X-Mailer: Mutt 0.50 Mime-Version: 1.0 In-Reply-To: ; from Boyd R. Faulkner on Dec 9, 1996 09:15:17 -0600 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Boyd R. Faulkner writes: > wtmp is broken with respect to two ports (I have found so far). > > ssh, which is fixed by a simple recompile, and install. > wu-ftpd, which is not. top 3.4 (a recompile fixes) XFree86's xterm (which a recompile also fixes) xdm is also probably broken, but I don't use it so haven't found out. rxvt too? screen > I suspect there may be more but I have not found the culprit, yet. A definitive list would be useful. Regards, David Nugent, Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@blaze.net.au http://www.blaze.net.au/~davidn From owner-freebsd-current Mon Dec 9 07:42:53 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA11609 for current-outgoing; Mon, 9 Dec 1996 07:42:53 -0800 (PST) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA11604 for ; Mon, 9 Dec 1996 07:42:50 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id JAA06081 for ; Mon, 9 Dec 1996 09:42:15 -0600 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma006077; Mon Dec 9 09:42:11 1996 Received: from milo.lodgenet.com (milo.lodgenet.com [204.124.121.171]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id JAA03810 for ; Mon, 9 Dec 1996 09:42:24 -0600 Received: from milo.lodgenet.com (localhost [127.0.0.1]) by milo.lodgenet.com (8.7.6/8.6.12) with ESMTP id JAA19968 for ; Mon, 9 Dec 1996 09:42:38 -0600 (CST) Message-Id: <199612091542.JAA19968@milo.lodgenet.com> X-Mailer: exmh version 1.6.9 8/22/96 To: current@FreeBSD.ORG Subject: PPP-OnDemand Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Dec 1996 09:42:38 -0600 From: John Prince Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi all.. I plan on using ppp on demand, and can not seem to get it to work without routed.. Does routed need to be running for this to work?? Thanks.. John -- ----------------------------------------------------------- John S. Prince email: johnp@lodgenet.com Manager, Systems Support voice: 605-330-1443 LodgeNet Entertainment Corp fax: 605-373-1630 ----------------------------------------------------------- From owner-freebsd-current Mon Dec 9 07:44:13 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA11733 for current-outgoing; Mon, 9 Dec 1996 07:44:13 -0800 (PST) Received: from ns.uninet.ee (ns.uninet.ee [194.204.0.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA11677 for ; Mon, 9 Dec 1996 07:43:38 -0800 (PST) Received: from localhost (taavi@localhost) by ns.uninet.ee (8.8.4/8.7.3) with SMTP id RAA11080; Mon, 9 Dec 1996 17:33:55 +0200 (EET) X-Authentication-Warning: ns.uninet.ee: taavi owned process doing -bs Date: Mon, 9 Dec 1996 17:33:55 +0200 (EET) From: Taavi Talvik To: "Boyd R. Faulkner" cc: current@freebsd.org Subject: Re: wtmp 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 Mon, 9 Dec 1996, Boyd R. Faulkner wrote: > wtmp is broken with respect to two ports (I have found so far). > > ssh, which is fixed by a simple recompile, and install. > wu-ftpd, which is not. > > I suspect there may be more but I have not found the culprit, yet. You should add xterm (xterm -ls) to list of programs broken by wtmp/utmp changes. best regards, taavi ----------------------------------------------------------- Taavi Talvik | Internet: taavi@uninet.ee AS Nosper | phone: +372 6405150 Ravala pst. 10-412 | fax: +372 6405151 EE0001, Tallinn, Estonia | From owner-freebsd-current Mon Dec 9 11:13:09 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA22731 for current-outgoing; Mon, 9 Dec 1996 11:13:09 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA22724 for ; Mon, 9 Dec 1996 11:13:06 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA01028; Mon, 9 Dec 1996 11:50:38 -0700 From: Terry Lambert Message-Id: <199612091850.LAA01028@phaeton.artisoft.com> Subject: Re: siguing into current from a random version To: dg@root.com Date: Mon, 9 Dec 1996 11:50:38 -0700 (MST) Cc: ggm@connect.com.au, chuckr@glue.umd.edu, freebsd-current@FreeBSD.ORG In-Reply-To: <199612090141.RAA04389@root.com> from "David Greenman" at Dec 8, 96 05:41:34 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 > >I suppose an assumption many neophytes like myself make is that CVS commits > >happen to complete sets of *tested* changes and not work in progress, so that > >the worst-case state is the testing (by author/cvs-changer) didn't cover for > >ones own particular setup and circumstances. > > That's the ideal, but we all make mistakes. Heh. Like checking code in without compiling the tree as it would look following the checkin... Nothing you can do about that, really, without instituting global writer locks on the tree (not that this will ever be approved). If you wanted all checkouts to result in a tree with a self-consistent state, you would have to have reader-locks so a write couldn't come in while a checkout was in progress and screw up self-consistency. Alternately, you'd make a copy of the tree 3-4 times a day with a reader-lock, and unless you were on a hot check-in run, use the copy of the tree for builds. Otherwise, you'd set reader locks for local checkouts. checkin, main tree: lock w cvs update build [ modify code on build fail, rerun build, repeat as needed ] cvs ci unlock update, main tree (or tree copy for cvssup, sup, ctm, etc.): lock r cvs update (or copy tree, whatever) unlock update, copy-of-main tree (or actual SUP client, etc.): cvs update (or copy tree, whatever) o copy-of-main tree is guaranteed buildable. Period. o main tree is guaranteed buildable if either lock has been asserted and a cvs update/build/checkin cycle has been successfully completed in the last writer lock cycle. Sure, someone could intentionally "unlock" a broken tree, but whoever did it would be signing their name in blood on the thing, for all to see. o ulockw can be used to create a "global log file" with delatas for overall changes. In addition, session tagging can be used to return tree to previous self sconsistent state for each and every checkin I know, I know: locking has been shouted down as inconvenient (even if integrated in encapsulation programs, ala): cvs lock r cvs update (or copy tree) cvs unlock (you would encapsulate by allowing only root/group write access to the archive, no one would be a member of the group, and cvs lock r would be suid root and add group access for the group to the current process on lock and take it away on unlock). Kinda like seatbelts... everyone complains about inconvenience with them, too. 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 Dec 9 11:15:21 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA22856 for current-outgoing; Mon, 9 Dec 1996 11:15:21 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA22851 for ; Mon, 9 Dec 1996 11:15:18 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA01043; Mon, 9 Dec 1996 11:54:08 -0700 From: Terry Lambert Message-Id: <199612091854.LAA01043@phaeton.artisoft.com> Subject: Re: w To: uh@sed.cs.fsu.edu (Gang-Ryung Uh) Date: Mon, 9 Dec 1996 11:54:07 -0700 (MST) Cc: current@FreeBSD.ORG In-Reply-To: <199612090224.CAA05321@sed.cs.fsu.edu> from "Gang-Ryung Uh" at Dec 8, 96 09:24:44 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 > I downloaded freebsd-current at Dec 8, made world, and make > kernel. Now, I have a couple of problems. First, "w" seems > to be broken. Second, "kaffe" is not working... > > Would you tell me what I have done wrong? > Thanks. You did not recompile all of the programs which include utmp.h. Sidebar: I really like the idea of providing a get/put interface, like the fstab stuff, for utmp/wtmp. That way we can change the shared library and the programs won't need recompiling. 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 Dec 9 11:32:15 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA23966 for current-outgoing; Mon, 9 Dec 1996 11:32:15 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA23945 for ; Mon, 9 Dec 1996 11:32:12 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA01078; Mon, 9 Dec 1996 12:09:56 -0700 From: Terry Lambert Message-Id: <199612091909.MAA01078@phaeton.artisoft.com> Subject: Re: mfs module -- seems to work.. To: ccsanady@friley216.res.iastate.edu (Chris Csanady) Date: Mon, 9 Dec 1996 12:09:56 -0700 (MST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org In-Reply-To: <199612091403.IAA00305@friley216.res.iastate.edu> from "Chris Csanady" at Dec 9, 96 08:03:26 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 > Ok. I did some looking into this, and now I am really stumped. There seems > to be something quite strange afoot here. :\ I have traced the problem to > vfsload(). (/usr/src/lib/libc/gen/getvfsent.c:233) It would seem that the > chdir() call is failing on a bad file descriptor!? Does anyone have any > ideas why this might happen? How a chdir("/var/tmp") ever fail? chdir works by doing a lookup, getting a locked vp to a dir back (and referenced as if it were opened -- see fchdir), and then putting the vp into the vp area for "current directory" in the proc struct. Then it closes the vp that was previously there. A currently directory is, in a very real sense, an open file. This is why you must gett all processes current directories out of an FS before it will unmount. A lookup picks a start point: For a non-chroot'ed process, this is the vp for /. For a chroot'ed process, this is the chroot vp from the proc struct (the current implementation of "namei/lookup" is inconsistent; the root vp should be set as the chroot vp, and the root vp should not be special cased for non-chroot'ed processes). The lookup proceeds a component at a time: lock start_point vnode dereference vfs_ops for lookup from the start_point my_locked_vnode = lookup(start_point, "var") unlock start_point start_point = my_locked_vnode dereference vfs_ops for lookup from the start_point my_locked_vnode = lookup(start_point, "tmp") temp_old_dir = current_dir current_dir = my_locked_vnode unlock temp_dir So to answer your question: It can fail if "var" does not exist in the root vnode namespace when lookup in the root FS type is called It can fail if "tmp" does not exist in the "var" vnode namespace when lookup in the "var" FS type is called In general, if the FS types change (ie: lookup() traverses a mount point), you should unmount the mount and look to make sure that the permissions on the underlying vnode(s) will let you cd into it, or ls it, or whatever. If not, you will need to chmod them. 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 Dec 9 11:39:12 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA25401 for current-outgoing; Mon, 9 Dec 1996 11:39:12 -0800 (PST) Received: from utgard.hos.net (utgard.hos.net [205.238.129.45]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA25358 for ; Mon, 9 Dec 1996 11:39:08 -0800 (PST) Received: (from faulkner@localhost) by utgard.hos.net (8.8.4/8.7.3) id NAA20617; Mon, 9 Dec 1996 13:38:21 -0600 (CST) Message-ID: Date: Mon, 9 Dec 1996 13:38:21 -0600 From: faulkner@asgard.hos.net (Boyd R. Faulkner) To: taavi@uninet.ee (Taavi Talvik) Cc: faulkner@asgard.hos.net (Boyd R. Faulkner), current@freebsd.org Subject: Re: wtmp References: X-Mailer: Mutt 0.53-export Mime-Version: 1.0 In-Reply-To: ; from Taavi Talvik on Dec 9, 1996 17:33:55 +0200 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Taavi Talvik writes: > On Mon, 9 Dec 1996, Boyd R. Faulkner wrote: > > > wtmp is broken with respect to two ports (I have found so far). > > > > ssh, which is fixed by a simple recompile, and install. > > wu-ftpd, which is not. > > > > I suspect there may be more but I have not found the culprit, yet. > > You should add xterm (xterm -ls) to list of programs broken by wtmp/utmp > changes. > Yes, xterm was the culprit. Thanks, Boyd -- _____________________________________________________________________________ Boyd Faulkner "The fates lead him who will; faulkner@asgard.hos.net Him who won't, they drag." http://asgard.hos.net/~faulkner Old Roman Saying -- Source: Joseph Campbell _____________________________________________________________________________ From owner-freebsd-current Mon Dec 9 13:00:09 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA00225 for current-outgoing; Mon, 9 Dec 1996 13:00:09 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA00116 for ; Mon, 9 Dec 1996 12:59:54 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id VAA13910 for ; Mon, 9 Dec 1996 21:59:42 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id VAA04026 for freebsd-current@FreeBSD.ORG; Mon, 9 Dec 1996 21:59:15 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.4/keltia-uucp-2.9) id VAA09570; Mon, 9 Dec 1996 21:27:46 +0100 (CET) Message-ID: Date: Mon, 9 Dec 1996 21:27:46 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@freebsd.org (FreeBSD Current Users' list) Subject: ATAPI on 2.2-ALPHA & general installation remarks X-Mailer: Mutt 0.53 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2768 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just received my brand new P6/180 at work. It has an ATAPI CD-ROM (error made by the vendor, I asked for a SCSI one). It is recognized without problem by the 2.2-ALPHA boot floppy. I've installed by FTP though because there is no CD of 2.2-ALPHA. The install went well after I fought with the 3C509 card (don't ask why I have both an fxp0 and an ep0). The fxp0 is shipped by HP but has only an 10BT connector and we use 10B2... I tumbled on the "no space left on device on /" when restarting the installation *without* newfs-ing the / partition. The machine is an HP XU with an on-board Adaptec Ultra controller. Here is dmesg output without -v. Stephan, if you want a dmesg with -v, just ask. The motherboard is a dual-PPro although I have only one processor. The PS/2 mouse is recognized without problem by XFree86 3.2.The Millenium is recognized by XFree86 too and correctly initialized. Is there some interesting options I could use for the Adaptec ? I intend to upgrade to 3.0-CURRENT in a few days when the dust of installation is a bit settled. It is fast: less than 3mn for a kernel compile (without NFS). The disks give me 7 MB/s read and 5 MB/s write. Copyright (c) 1992-1996 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2-ALPHA #2: Mon Dec 9 16:45:14 MET 1996 roberto@caerdonn.eurocontrol.fr:/src/src/sys/compile/CAERDONN Calibrating clock(s) relative to mc146818A clock ... i586 clock: 180060673 Hz, i8254 clock: 1193063 Hz CPU: Pentium Pro (180.08-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x617 Stepping=7 Features=0xfbff,MTRR,PGE,MCA,CMOV> real memory = 67108864 (65536K bytes) avail memory = 64163840 (62660K bytes) Probing for devices on PCI bus 0: chip0 rev 136 on pci0:0 pci0:1: CMD, device=0x0646, class=storage (ide) int a irq 14 [no driver assigned] ahc0 rev 0 int a irq 10 on pci0:2 ahc0: Using left over BIOS settings ahc0: aic7880 Single Channel, SCSI Id=7, 16 SCBs (ahc0:0:0): "SEAGATE ST32550N 8303" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2033MB (4165272 512 byte sectors) (ahc0:1:0): "HP 2.13GB B 50-0482 0482" type 0 fixed SCSI 2 sd1(ahc0:1:0): Direct-Access 2033MB (4165272 512 byte sectors) vga0 rev 1 int a irq 11 on pci0:11 fxp0 rev 1 int a irq 11 on pci0:12 fxp0: Ethernet address 08:00:09:dc:23:7e chip1 rev 4 on pci0:20 chip2 rev 4 on pci0:25 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2: disabled, not probed. sio3: disabled, not probed. lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x63 irq 12 on motherboard fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordy wcd0: 1377Kb/sec, 128Kb cache, audio play, 255 volume levels, ejectable tray wcd0: no disc inside, unlocked 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 5 on isa ep0: aui/utp/bnc[*BNC*] address 00:60:97:3b:29:b6 npx0 on motherboard npx0: INT 16 interface -----End of forwarded message----- -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #31: Tue Dec 3 23:52:58 CET 1996 From owner-freebsd-current Mon Dec 9 13:59:26 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA04191 for current-outgoing; Mon, 9 Dec 1996 13:59:26 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA04185 for ; Mon, 9 Dec 1996 13:59:22 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA09105; Mon, 9 Dec 1996 22:58:33 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA10852; Mon, 9 Dec 1996 22:58:32 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id WAA24099; Mon, 9 Dec 1996 22:00:41 +0100 (MET) From: J Wunsch Message-Id: <199612092100.WAA24099@uriah.heep.sax.de> Subject: Re: PPP-OnDemand To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 9 Dec 1996 22:00:41 +0100 (MET) Cc: johnp@lodgenet.com (John Prince) In-Reply-To: <199612091542.JAA19968@milo.lodgenet.com> from John Prince at "Dec 9, 96 09:42:38 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 John Prince wrote: > I plan on using ppp on demand, and can not seem to get it to work without > routed.. > Does routed need to be running for this to work?? Rather the other way 'round: a running routed used to be a show- stopper for working dial-on-demand PPP. What you need is an `add 0.0.0.0 y z' statement in ppp.conf however. -- 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 Dec 9 15:21:32 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA09175 for current-outgoing; Mon, 9 Dec 1996 15:21:32 -0800 (PST) Received: from american.com (mail.american.com [204.253.96.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA09164 for ; Mon, 9 Dec 1996 15:21:28 -0800 (PST) Received: from muir-woods.american.com (muir-woods.american.com [204.253.96.201]) by american.com (8.7.6/8.6.12) with ESMTP id SAA09455 for ; Mon, 9 Dec 1996 18:20:52 -0500 (EST) Received: (from brad@localhost) by muir-woods.american.com (8.8.3/8.6.12) id SAA15038; Mon, 9 Dec 1996 18:20:51 -0500 (EST) Date: Mon, 9 Dec 1996 18:20:51 -0500 (EST) Message-Id: <199612092320.SAA15038@muir-woods.american.com> From: Brad Parker To: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: some fixes to libc_r (RELENG_2_2) Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk [is anyone else using libc_r?] I've been trying to use libc_r on RELENG_2_2 (is there a doc anywhere which describes the tags available and what they *really* mean? I assume RELENG_2_2 is 2.2-alpha) Anyway, I found some problems building libc_r; there where some missing functions and some makefiles which were out of date. If I'm out of rev or there is a better tree please let me know. I noticed some other missing functions - I only added the ones I'm using. Also, building with libc_r is a pain as you need to use -nostlib, include /usr/lib/crt0.o at the start and "/usr/lib/libgcc.a -lc_r /usr/lib/libgcc.a" at the end. A flag to "cc" would be better. New files: *** new file: gen/readdir_r.c #include #include /* fake readdir_r using thread-safe readdir */ int readdir_r(DIR *dirp, struct dirent *entry, struct dirent **result) { struct dirent *dp; if ((dp = readdir(dirp)) == 0) return -1; *entry = *dp; *result = dp; return 0; } *** new file: uthread/uthread_attr_setdetachstate.c #include #ifdef _THREAD_SAFE #include #include "pthread_private.h" int pthread_attr_setdetachstate(pthread_attr_t *attr, int detachstate) { int ret; if (attr == NULL || *attr == NULL) { errno = EINVAL; ret = -1; } else { (*attr)->flags = ((*attr)->flags & ~(PTHREAD_DETACHED)) | (detachstate & PTHREAD_DETACHED); ret = 0; } return(ret); } #endif Diffs: *** uthread/Makefile.inc.~1~ Tue Aug 20 04:20:59 1996 --- uthread/Makefile.inc Mon Dec 9 14:08:39 1996 *************** *** 7,13 **** --- 7,19 ---- SRCS+= \ uthread_accept.c \ + uthread_attr_destroy.c \ + uthread_attr_init.c \ + uthread_attr_setcreatesuspend.c \ uthread_attr_setcreatesuspend_np.c \ + uthread_attr_setdetachstate.c \ + uthread_attr_setprio.c \ + uthread_attr_setstacksize.c \ uthread_autoinit.cc \ uthread_bind.c \ uthread_clean.c \ *** sys/Makefile.inc.~1~ Thu Aug 22 00:25:09 1996 --- sys/Makefile.inc Mon Dec 9 16:39:16 1996 *************** *** 6,12 **** # modules with non-default implementations on at least one architecture: SRCS+= Ovfork.S brk.S cerror.S exect.S fork.S pipe.S ptrace.S reboot.S \ ! sbrk.S setlogin.S sigpending.S sigprocmask.S sigreturn.S \ sigsuspend.S syscall.S __error.c # glue to provide compatibility between GCC 1.X and 2.X --- 6,12 ---- # modules with non-default implementations on at least one architecture: SRCS+= Ovfork.S brk.S cerror.S exect.S fork.S pipe.S ptrace.S reboot.S \ ! rfork.S sbrk.S setlogin.S sigpending.S sigprocmask.S sigreturn.S \ sigsuspend.S syscall.S __error.c # glue to provide compatibility between GCC 1.X and 2.X *************** *** 27,33 **** setpgid.o setpriority.o setregid.o setreuid.o setrlimit.o \ setsid.o settimeofday.o setuid.o shmsys.o stat.o statfs.o \ swapon.o symlink.o sync.o sysarch.o umask.o unlink.o \ ! unmount.o utimes.o vadvise.o __syscall.o __sysctl.o # Syscalls renamed as _thread_sys_{syscall}. THREADASM= accept.o bind.o close.o connect.o dup.o dup2.o \ --- 27,33 ---- setpgid.o setpriority.o setregid.o setreuid.o setrlimit.o \ setsid.o settimeofday.o setuid.o shmsys.o stat.o statfs.o \ swapon.o symlink.o sync.o sysarch.o umask.o unlink.o \ ! unmount.o utimes.o utrace.o vadvise.o __syscall.o __sysctl.o # Syscalls renamed as _thread_sys_{syscall}. THREADASM= accept.o bind.o close.o connect.o dup.o dup2.o \ *** gen/Makefile.inc.~1~ Sun Jan 21 19:22:18 1996 --- gen/Makefile.inc Mon Dec 9 15:24:19 1996 *************** *** 2,8 **** # $Id: Makefile.inc,v 1.1 1996/01/22 00:22:18 julian Exp $ # machine-independent gen sources ! .PATH: ${.CURDIR}/../libc/${MACHINE}/gen ${.CURDIR}/../libc/gen SRCS+= alarm.c assert.c clock.c closedir.c config.c confstr.c crypt.c \ ctermid.c daemon.c devname.c disklabel.c err.c errlst.c \ --- 2,8 ---- # $Id: Makefile.inc,v 1.1 1996/01/22 00:22:18 julian Exp $ # machine-independent gen sources ! .PATH: ${.CURDIR}/../libc/${MACHINE}/gen ${.CURDIR}/../libc/gen ${.CURDIR}/gen SRCS+= alarm.c assert.c clock.c closedir.c config.c confstr.c crypt.c \ ctermid.c daemon.c devname.c disklabel.c err.c errlst.c \ *************** *** 20,25 **** --- 20,28 ---- telldir.c termios.c time.c times.c timezone.c ttyname.c ttyslot.c \ ualarm.c uname.c unvis.c usleep.c utime.c valloc.c vis.c wait.c \ wait3.c waitpid.c + + # + SRCS+= readdir_r.c # *rand48 family, from 1.1.5 SRCS+= _rand48.c drand48.c erand48.c jrand48.c lcong48.c lrand48.c \ *** yp/Makefile.inc.~1~ Sun Jan 21 19:23:58 1996 --- yp/Makefile.inc Mon Dec 9 15:59:26 1996 *************** *** 4,8 **** # yp sources .PATH: ${.CURDIR}/../libc/yp ! SRCS+= xdryp.c yplib.c --- 4,18 ---- # yp sources .PATH: ${.CURDIR}/../libc/yp ! SRCS+= xdryp.c yp_xdr.c yplib.c ! CLEANFILES+= yp_xdr.c yp.h ! ! RPCSRC= ${.DESTDIR}/usr/include/rpcsvc/yp.x ! RPCGEN= rpcgen ! ! yp_xdr.c: ${RPCSRC} yp.h ! ${RPCGEN} -c -o ${.TARGET} ${RPCSRC} ! ! yp.h: ${RPCSRC} ! ${RPCGEN} -h -o ${.TARGET} ${RPCSRC} From owner-freebsd-current Mon Dec 9 21:51:16 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA15658 for current-outgoing; Mon, 9 Dec 1996 21:51:16 -0800 (PST) Received: from motaba.tmc.edu.tw (motaba.tmc.edu.tw [203.64.48.253]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id VAA15649 for ; Mon, 9 Dec 1996 21:51:06 -0800 (PST) From: alexj@motaba.tmc.edu.tw Received: from [203.64.48.13] by motaba.tmc.edu.tw (AIX 3.2/UCB 5.64/4.03) id AA19060; Tue, 10 Dec 1996 13:53:25 +0800 Date: Tue, 10 Dec 1996 13:53:25 +0800 Message-Id: <3.0.32.19961210135325.00de1af0@mail.tmc.edu.tw> X-Sender: alexj@mail.tmc.edu.tw (Unverified) X-Mailer: Windows Eudora Pro Version 3.0 (32) To: freebsd-current@freebsd.org Subject: Amazing to MIT Pthread-1.60b6 & Pthread built in FreeBSD-2.2-ALPHA Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====================_850254808==_" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk --=====================_850254808==_ Content-Type: text/enriched; charset="us-ascii" It surprised me so much !! I wrote a small program to test the performance of MIT PThread-1.60b6 (MIT) used in FreeBSD-2.2-ALPHA & the pthread built in FBSD-2.2-ALPHA (FBSD). I had thought that the performance of FBSD should be better than that of MIT. However, I am wrong after making this test. It's really amazing. The performance of MIT is much better than that of FBSD. Is there any problem in FreeBSD-2.2-ALPHA ? gcc pbench.c -lc_r ================================================================ FreeBSD 2.2-ALPHA built-in PTHREAD test.... Testing pthread_create() 1000 times...spending 3.228051 seconds Testing pthread_lock() 10000 times...spending 0.97357 seconds Testing pthread_yield() 10000 times...spending 12.1259162 seconds ================================================================ pgcc pbench.c ================================================================ MIT PTHREAD 1.60B6 performance test.... Testing pthread_create() 100000 times...spending 0.1063555 seconds Testing pthread_lock() 1000000 times...spending 1.168608 seconds Testing pthread_yield() 1000000 times...spending 9.333843 seconds ================================================================== The attachment is my program source code --=====================_850254808==_ Content-Type: text/plain; charset="us-ascii" Content-Disposition: attachment; filename="pbench.c" #include #include struct timeval tv1, tv2; long testTimes=100; void create_thread_test() { pthread_exit(0); } void test_pthread_create() { int count; long d_sec, d_usec, tt; pthread_t p_t; tt = testTimes / 10; printf("Testing pthread_create() %i times...", tt); gettimeofday(&tv1, NULL); for(count=0; count < tt; count++) { pthread_create(&p_t, NULL, (void*) &create_thread_test, NULL); } gettimeofday(&tv2, NULL); d_usec = tv2.tv_usec-tv1.tv_usec; d_sec = tv2.tv_sec-tv1.tv_sec; if (d_usec < 0) { d_usec = 1000000- d_usec; d_sec--; } printf("spending %i.%i seconds\n",d_sec,d_usec); } void test_pthread_lock() { int count; long d_sec, d_usec; pthread_mutex_t lock; printf("Testing pthread_lock() %i times...", testTimes); pthread_mutex_init(&lock, NULL); gettimeofday(&tv1, NULL); for(count=0; count < testTimes; count++) { pthread_mutex_lock(&lock); pthread_mutex_unlock(&lock); } gettimeofday(&tv2, NULL); d_usec = tv2.tv_usec-tv1.tv_usec; d_sec = tv2.tv_sec-tv1.tv_sec; if (d_usec < 0) { d_usec = 1000000- d_usec; d_sec--; } printf("spending %i.%i seconds\n",d_sec,d_usec); } void test_pthread_yield() { int count; long d_sec, d_usec; printf("Testing pthread_yield() %i times...", testTimes); gettimeofday(&tv1, NULL); for(count=0; count < testTimes; count++) { pthread_yield(); } gettimeofday(&tv2, NULL); d_usec = tv2.tv_usec-tv1.tv_usec; d_sec = tv2.tv_sec-tv1.tv_sec; if (d_usec < 0) { d_usec = 1000000- d_usec; d_sec--; } printf("spending %i.%i seconds\n",d_sec,d_usec); } //================================================================ main(argc, argv) int argc; char *argv[]; { int i; pthread_init(); printf("argc=%i\n", argc); for (i=0; i < argc; i++) { printf("argv[%i]=%s\n", i, argv[i]); } if (argc >=2) { testTimes = atoi(argv[1]); } //#define MIT #ifdef MIT printf("MIT PTHREAD 1.60B6 performance test....\n"); #else printf("FreeBSD 2.2-ALPHA built-in PTHREAD test....\n"); #endif test_pthread_create(); test_pthread_lock(); test_pthread_yield(); } --=====================_850254808==_ Content-Type: text/enriched; charset="us-ascii" ======================================================== = Reading this letter thorugh ffff,0000,0000Eudora Pro 3, = = You will find that the world of e-mail can also be ffff,0000,ffffco0000,0000,fffflo0000,ffff,ffffrf0000,ffff,0000ul = ======================================================== --=====================_850254808==_-- From owner-freebsd-current Mon Dec 9 22:03:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA16971 for current-outgoing; Mon, 9 Dec 1996 22:03:55 -0800 (PST) Received: from motaba.tmc.edu.tw (motaba.tmc.edu.tw [203.64.48.253]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id WAA16833 for ; Mon, 9 Dec 1996 22:02:44 -0800 (PST) From: alexj@motaba.tmc.edu.tw Received: from [203.64.48.13] by motaba.tmc.edu.tw (AIX 3.2/UCB 5.64/4.03) id AA22878; Tue, 10 Dec 1996 14:04:09 +0800 Date: Tue, 10 Dec 1996 14:04:09 +0800 Message-Id: <3.0.32.19961210140410.00ded150@mail.tmc.edu.tw> X-Sender: alexj@mail.tmc.edu.tw X-Mailer: Windows Eudora Pro Version 3.0 (32) To: freebsd-current@freebsd.org Subject: Amazing to MIT Pthread-1.60b6 & Pthread built in FreeBSD-2.2-ALPHA Mime-Version: 1.0 Content-Type: text/enriched; charset="us-ascii" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sorry, I forgot telling you from where I get the pthread-1.60b6 It's here: sipb.mit.edu:/pub/pthreads ======================================================== = Reading this letter thorugh ffff,0000,0000Eudora Pro 3, = = You will find that the world of e-mail can also be ffff,0000,ffffco0000,0000,fffflo0000,ffff,ffffrf0000,ffff,0000ul = ======================================================== From owner-freebsd-current Tue Dec 10 05:36:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA00926 for current-outgoing; Tue, 10 Dec 1996 05:36:20 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA00881; Tue, 10 Dec 1996 05:36:12 -0800 (PST) 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 EAA13262 ; Tue, 10 Dec 1996 04:20:50 -0800 (PST) From: Greg Lehey Received: from freebie.lemis.de by diablo.ppp.de with smtp (Smail3.1.28.1 #1) id m0vXR9i-000QXiC; Tue, 10 Dec 96 13:19 MET Received: (grog@localhost) by freebie.lemis.de (8.8.4/8.6.12) id LAA18102; Tue, 10 Dec 1996 11:54:06 +0100 (MET) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Message-Id: <199612101054.LAA18102@freebie.lemis.de> Subject: It works! Solved my problem wih Etherlink III on AcerNote Light To: freebsd-mobile@freebsd.org (FreeBSD mobile Mailing List) Date: Tue, 10 Dec 1996 11:54:05 +0100 (MET) Cc: FreeBSD-current@freebsd.org (FreeBSD current users) 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 For those of you who've been following my tribulations installing -current on an AcerNote Light, the good news: finally it works. I've learnt a number of things on the way, however, so I thought I'd share the story: 1. Initially, I tried installing with the 2.1.5 boot floppy. It recognized the card, but couldn't get it to work. I sent a message off, I think to -current, and got a number of replies, including "set your link0 and link1 correctly", and "you need the PAO floppy". 2. In the meantime, several things happened to muddy the waters: i. I tried the 3Com "diagnostic", which must be the worst piece of junk I have ever seen. It told me that the Ethernet card was defective--it failed every test. So I changed the Ethernet card. ii. At the same time, the hard disk on the notebook died. So I changed the notebook. iii. The handbook for the notebook suggested that the standard settings for the board (I/O 0x300, IRQ 10) wouldn't work. IRQ 10 is "reserved", so they say, though they don't say for what. They also give a map of upper memory showing nothing free at all; obviously a misprint, but another cause for uncertainty. I tried moving the board to 0x320, IRQ 11 (at least they say IRQ 11 is available), but that didn't help. It just meant that, after I could no longer run the diagnostic, I found that I had forgotten how I had last set it. iv. The new notebook and the new diagnostic still claimed that the new Ethernet card was defective. I decided that the diagnostic was defective, and sent off a mail message to 3Com asking for help. Despite their promises of a callback, it hasn't happened yet. The diagnostic appears to want to run under Windoze 95% with card services enabled. If you boot DOS from floppy, it will run, but it will fail the test. In order for it to pass the test in this mode, you need first to read the configuration, store the same configuration back, and then run the diagnostic, which will succeed. Leave the diagnostic program, restart it, and run it again, and it will fail. I can't see a means of distinguishing this behaviour from that of a board which can't keep its configuration. This kind of diagnostic is just one step removed from being completely useless. To be fair (though not necessarily generous), I didn't verify whether the diagnostic worked correctly under Windoze 95%. That would have required finishing the installation and answering all sorts of stupid questions, including serial numbers and such junk. To make matters worse, after I wiped Windoze 95% from the disk, the diagnostic would not even start. Instead, it said Can't Run Install, files missing. Make sure you have INSTALL.EXE, INST1.SAC and STRINGS.BIN in your directory (-1, 2) These files are, of course, all there, on the original, write-protected diskette. I re-created a second diskette from the backup, and I downloaded the file 3C589.EXE from your web site, but the results were the same. I'm pretty sure the real reason is that it didn't find a DOS or Windoze hard disk partition. Summary: the diagnostic software is broke, but bad. 3. I built a number of kernels with a number of different options, set up my /etc/pccard.conf as various people have suggested--all in vain. I suspect that the pccard setup is very version-sensitive. My pccardd didn't even accept the definitions that some people had put in their /etc/pccard.conf, for example. Nevertheless, things looked *very* bad. pccardd couldn't find anything which looked like PCMCIA resources (though the kernel did notice when I inserted and removed the boards). I shelved this and went away for some serious head-scratching. 4. During the head-scratching, I decided to retry the 2.1.5 vanilla boot diskette. Bingo! it found the board. Not much I could do with it, of course, but it was better than what I had had with the PAO diskette. I then attempted it with what I thought was the 2.1.5 generic kernel, only to find it was a 2.1.0-SNAP kernel dated 28 September 1995. It didn't find the board. Subsequent attempts with the generic 2.1.5 kernel showed that it didn't find the board either. Huh? Back to the boot diskette. It no longer found it, either. After power cycling, it did, and so did the generic kernel. So then I built a -current kernel without crd0 and pcic[01]. It FOund the baord. And it was able to correctly configure zp0. But I still couldn't get things to work. On closer examination, there seems to be something wrong with the routing table entry: there was no entry at all for zp0, and I couldn't find a way to put one in. In /etc/sysconfig, I did effectively: ifconfig lp0 192.109.197.159 192.109.197.137 ifconfig zp0 192.109.197.159 This had the strange effect that no entry at all for zp0 appeared in the routing table. I don't understand this: at the other end (freebie) I had an almost completely symmetrical configuration, which worked with no problems. I still don't know what happened here, but I'll take a look once I clean up the backlog that this marathon has caused. So I removed lp0 from /etc/sysconfig and rebooted. Now the routing tables looked OK, but it still didn't work. OK, I've got RG-58, what links do I need? Where's the man page for zp? Nowhere. I played around with the links and found that link1 will do the trick: it works. Not very fast, but it works. The hard disk on this machine seems to be the slowest I've every come across. ftp'ing a 67 MB file gave me a throughput of about 220 kB/s when copying to disk, about 750 kB/s when copying to /dev/null. By comparison, the same file ftp'd to (IDE) disk on freebie at 860 kB/s, and to /dev/null at 940 kB/s. The error rate might explain some of this: on freebie, netstat -in shows: Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ep0 1500 00.a0.24.37.0d.2b 3042959 1 3470819 1 0 ep0 1500 192.109.197 192.109.197.137 3042959 1 3470819 1 0 By contrast, on papillon (the notebook), I have: zp0 1500 00.60.97.40.fb.e1 221769 198 52256 3 0 zp0 1500 192.109.197 192.109.197.159 221769 198 52256 3 0 The morals of the story ----------------------- 1. We obviously need to look at the pccard stuff a lot more carefully. The documentation needs to mention this. In fact, we need documentation. I'll see what I can put together. 2. We probably need to document the vagaries of "diagnostic" programs such as the junk that 3Com supplies. You'd think 3Com would be interested, too. After all, I can't be the only person to return hardware because the accompanying software says it's defective. 3. PCMCIA is obviously a good subject for the internals book we're talking about writing. 4. It would be nice to have a general diagnostic utility for snooping around in the PC hardware to see what's there and what isn't. I'll think about writing one. If anybody has any ideas, I'd be interested to hear of them. 5. The probe routines are probably not all they should be. I'd guess that the 2.1-SNAP kernel got the board into a state where no kernel could successfully probe it, and I had to power down to get any improvement. This is partially documented in the kernel config files, but it might be an idea to make it more prominent. 6. We need man pages for all the Ethernet drivers, even if they're substantially clones. It would also be nice to have an overview of what the ifconfig flags mean for the various drivers. Greg From owner-freebsd-current Tue Dec 10 05:38:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA01160 for current-outgoing; Tue, 10 Dec 1996 05:38:18 -0800 (PST) Received: from gargoyle.bazzle.com (gargoyle.bazzle.com [206.103.246.190]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA01145 for ; Tue, 10 Dec 1996 05:38:12 -0800 (PST) Received: from gargoyle.bazzle.com (localhost [127.0.0.1]) by gargoyle.bazzle.com (8.8.3/8.6.12) with SMTP id IAA06989; Tue, 10 Dec 1996 08:37:50 -0500 (EST) Date: Tue, 10 Dec 1996 08:37:50 -0500 (EST) From: "Eric J. Chet" To: alexj@motaba.tmc.edu.tw cc: freebsd-current@FreeBSD.ORG Subject: Re: Amazing to MIT Pthread-1.60b6 & Pthread built in FreeBSD-2.2-ALPHA In-Reply-To: <3.0.32.19961210135325.00de1af0@mail.tmc.edu.tw> 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, 10 Dec 1996 alexj@motaba.tmc.edu.tw wrote: > It surprised me so much !! > > I wrote a small program to test the performance of MIT PThread-1.60b6 (MIT) used in FreeBSD-2.2-ALPHA & the pthread built in FBSD-2.2-ALPHA (FBSD). > > I had thought that the performance of FBSD should be better than that of > > MIT. However, I am wrong after making this test. > > It's really amazing. The performance of MIT is much better than that > > of FBSD. > > Is there any problem in FreeBSD-2.2-ALPHA ? > > > gcc pbench.c -lc_r > > ================================================================ > > FreeBSD 2.2-ALPHA built-in PTHREAD test.... > > Testing pthread_create() 1000 times...spending 3.228051 seconds > > Testing pthread_lock() 10000 times...spending 0.97357 seconds > > Testing pthread_yield() 10000 times...spending 12.1259162 seconds > > ================================================================ > > > pgcc pbench.c > > ================================================================ > > MIT PTHREAD 1.60B6 performance test.... > > Testing pthread_create() 100000 times...spending 0.1063555 seconds > > Testing pthread_lock() 1000000 times...spending 1.168608 seconds > > Testing pthread_yield() 1000000 times...spending 9.333843 seconds > > ================================================================== > > > The attachment is my program source code > > Hello Could you please compile both versions with either gcc or pgcc, those numbers are meaningless. Eric J. Chet - ejc@bazzle.com From owner-freebsd-current Tue Dec 10 05:50:48 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA00926 for current-outgoing; Tue, 10 Dec 1996 05:36:20 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA00881; Tue, 10 Dec 1996 05:36:12 -0800 (PST) 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 EAA13262 ; Tue, 10 Dec 1996 04:20:50 -0800 (PST) From: Greg Lehey Received: from freebie.lemis.de by diablo.ppp.de with smtp (Smail3.1.28.1 #1) id m0vXR9i-000QXiC; Tue, 10 Dec 96 13:19 MET Received: (grog@localhost) by freebie.lemis.de (8.8.4/8.6.12) id LAA18102; Tue, 10 Dec 1996 11:54:06 +0100 (MET) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Message-Id: <199612101054.LAA18102@freebie.lemis.de> Subject: It works! Solved my problem wih Etherlink III on AcerNote Light To: freebsd-mobile@freebsd.org (FreeBSD mobile Mailing List) Date: Tue, 10 Dec 1996 11:54:05 +0100 (MET) Cc: FreeBSD-current@freebsd.org (FreeBSD current users) 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 For those of you who've been following my tribulations installing -current on an AcerNote Light, the good news: finally it works. I've learnt a number of things on the way, however, so I thought I'd share the story: 1. Initially, I tried installing with the 2.1.5 boot floppy. It recognized the card, but couldn't get it to work. I sent a message off, I think to -current, and got a number of replies, including "set your link0 and link1 correctly", and "you need the PAO floppy". 2. In the meantime, several things happened to muddy the waters: i. I tried the 3Com "diagnostic", which must be the worst piece of junk I have ever seen. It told me that the Ethernet card was defective--it failed every test. So I changed the Ethernet card. ii. At the same time, the hard disk on the notebook died. So I changed the notebook. iii. The handbook for the notebook suggested that the standard settings for the board (I/O 0x300, IRQ 10) wouldn't work. IRQ 10 is "reserved", so they say, though they don't say for what. They also give a map of upper memory showing nothing free at all; obviously a misprint, but another cause for uncertainty. I tried moving the board to 0x320, IRQ 11 (at least they say IRQ 11 is available), but that didn't help. It just meant that, after I could no longer run the diagnostic, I found that I had forgotten how I had last set it. iv. The new notebook and the new diagnostic still claimed that the new Ethernet card was defective. I decided that the diagnostic was defective, and sent off a mail message to 3Com asking for help. Despite their promises of a callback, it hasn't happened yet. The diagnostic appears to want to run under Windoze 95% with card services enabled. If you boot DOS from floppy, it will run, but it will fail the test. In order for it to pass the test in this mode, you need first to read the configuration, store the same configuration back, and then run the diagnostic, which will succeed. Leave the diagnostic program, restart it, and run it again, and it will fail. I can't see a means of distinguishing this behaviour from that of a board which can't keep its configuration. This kind of diagnostic is just one step removed from being completely useless. To be fair (though not necessarily generous), I didn't verify whether the diagnostic worked correctly under Windoze 95%. That would have required finishing the installation and answering all sorts of stupid questions, including serial numbers and such junk. To make matters worse, after I wiped Windoze 95% from the disk, the diagnostic would not even start. Instead, it said Can't Run Install, files missing. Make sure you have INSTALL.EXE, INST1.SAC and STRINGS.BIN in your directory (-1, 2) These files are, of course, all there, on the original, write-protected diskette. I re-created a second diskette from the backup, and I downloaded the file 3C589.EXE from your web site, but the results were the same. I'm pretty sure the real reason is that it didn't find a DOS or Windoze hard disk partition. Summary: the diagnostic software is broke, but bad. 3. I built a number of kernels with a number of different options, set up my /etc/pccard.conf as various people have suggested--all in vain. I suspect that the pccard setup is very version-sensitive. My pccardd didn't even accept the definitions that some people had put in their /etc/pccard.conf, for example. Nevertheless, things looked *very* bad. pccardd couldn't find anything which looked like PCMCIA resources (though the kernel did notice when I inserted and removed the boards). I shelved this and went away for some serious head-scratching. 4. During the head-scratching, I decided to retry the 2.1.5 vanilla boot diskette. Bingo! it found the board. Not much I could do with it, of course, but it was better than what I had had with the PAO diskette. I then attempted it with what I thought was the 2.1.5 generic kernel, only to find it was a 2.1.0-SNAP kernel dated 28 September 1995. It didn't find the board. Subsequent attempts with the generic 2.1.5 kernel showed that it didn't find the board either. Huh? Back to the boot diskette. It no longer found it, either. After power cycling, it did, and so did the generic kernel. So then I built a -current kernel without crd0 and pcic[01]. It FOund the baord. And it was able to correctly configure zp0. But I still couldn't get things to work. On closer examination, there seems to be something wrong with the routing table entry: there was no entry at all for zp0, and I couldn't find a way to put one in. In /etc/sysconfig, I did effectively: ifconfig lp0 192.109.197.159 192.109.197.137 ifconfig zp0 192.109.197.159 This had the strange effect that no entry at all for zp0 appeared in the routing table. I don't understand this: at the other end (freebie) I had an almost completely symmetrical configuration, which worked with no problems. I still don't know what happened here, but I'll take a look once I clean up the backlog that this marathon has caused. So I removed lp0 from /etc/sysconfig and rebooted. Now the routing tables looked OK, but it still didn't work. OK, I've got RG-58, what links do I need? Where's the man page for zp? Nowhere. I played around with the links and found that link1 will do the trick: it works. Not very fast, but it works. The hard disk on this machine seems to be the slowest I've every come across. ftp'ing a 67 MB file gave me a throughput of about 220 kB/s when copying to disk, about 750 kB/s when copying to /dev/null. By comparison, the same file ftp'd to (IDE) disk on freebie at 860 kB/s, and to /dev/null at 940 kB/s. The error rate might explain some of this: on freebie, netstat -in shows: Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ep0 1500 00.a0.24.37.0d.2b 3042959 1 3470819 1 0 ep0 1500 192.109.197 192.109.197.137 3042959 1 3470819 1 0 By contrast, on papillon (the notebook), I have: zp0 1500 00.60.97.40.fb.e1 221769 198 52256 3 0 zp0 1500 192.109.197 192.109.197.159 221769 198 52256 3 0 The morals of the story ----------------------- 1. We obviously need to look at the pccard stuff a lot more carefully. The documentation needs to mention this. In fact, we need documentation. I'll see what I can put together. 2. We probably need to document the vagaries of "diagnostic" programs such as the junk that 3Com supplies. You'd think 3Com would be interested, too. After all, I can't be the only person to return hardware because the accompanying software says it's defective. 3. PCMCIA is obviously a good subject for the internals book we're talking about writing. 4. It would be nice to have a general diagnostic utility for snooping around in the PC hardware to see what's there and what isn't. I'll think about writing one. If anybody has any ideas, I'd be interested to hear of them. 5. The probe routines are probably not all they should be. I'd guess that the 2.1-SNAP kernel got the board into a state where no kernel could successfully probe it, and I had to power down to get any improvement. This is partially documented in the kernel config files, but it might be an idea to make it more prominent. 6. We need man pages for all the Ethernet drivers, even if they're substantially clones. It would also be nice to have an overview of what the ifconfig flags mean for the various drivers. Greg From owner-freebsd-current Tue Dec 10 06:05:56 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA01208 for current-outgoing; Tue, 10 Dec 1996 06:05:56 -0800 (PST) Received: from viking.ucsalf.ac.uk (viking.ucsalf.ac.uk [192.195.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id GAA01202 for ; Tue, 10 Dec 1996 06:05:47 -0800 (PST) Received: by viking.ucsalf.ac.uk (Smail3.1.29.1 #4) id m0vXSma-00037EC; Tue, 10 Dec 96 14:03 GMT Message-Id: From: mark@plato.salford.ac.uk (Mark Powell) Subject: NFS problems with 2.2-current ? To: freebsd-current@freebsd.org Date: 10 Dec 1996 14:03:36 -0000 X-Gated-To-News-By: news@ucsalf.ac.uk Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I'm running the latest 2.2-current. I like to mount src.doc.ic.ac.uk/public on my system. If I do a TCP mount df and mount always hang when trying to show# free space. Although I can 'ls' the archive and copy files from it. If I UDP mount the archive df and mount work fine, as does 'ls'. However, trying to copy any files from the archive always hangs. Any ideas? TIA -- Mark Powell - Unix Information Officer - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 745 5936 Fax: +44 161 736 3596 Email: mark@salford.ac.uk finger mark@ucsalf.ac.uk (for PGP key) Home Page From owner-freebsd-current Tue Dec 10 07:23:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA07924 for current-outgoing; Tue, 10 Dec 1996 07:23:41 -0800 (PST) Received: from jalopeno.nixu.fi (jalopeno.nixu.fi [194.197.118.20]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA07911 for ; Tue, 10 Dec 1996 07:23:37 -0800 (PST) Received: from flauta.nixu.fi (flauta.nixu.fi [194.197.118.35]) by jalopeno.nixu.fi (8.8.3/8.8.3) with ESMTP id RAA13442 for ; Tue, 10 Dec 1996 17:23:04 +0200 (EET) Date: Tue, 10 Dec 1996 17:22:49 +0200 (EET) From: Marko Lamminen Reply-To: Marko Lamminen Subject: Re: NFS problems with 2.2-current ? To: freebsd-current@freebsd.org 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 have no idea if this is related but I'll post this anyway since someone might be having same problems. Yesterday I posted about a make reinstall that had gone awry. I spent many hours debugging this a found the the most probably cause, NFS. Situation was this: I had a pentium pro which I used to compile and install a 3.0-current, everything went fine (execpt it doesn't boot from disk bootblock). After testing it a bit I decided to install 3.0-current to my other machine (an older 486) using the 'reinstall' option and NFS mounted src and obj trees. The make reinstall went _almost_ smoothly (there was trouble but as it fixed by just doing it again I suspected some older program inferring with a new) and after installing a new kernel it was time to reboot. Now there were problems, it was unable to mount root writable (mount -o update /) because mount core dumped (bus error). Various other binaries were also behaving strangly (VI coredumped if I pressed ESC). After extensive testing of the new kernel (failsafe,diagnostics,ddb,etc.etc.), I was about ready to give up but happened to take a cksum of 'mount' and realized that altough the mount was same size as the original (in the pentium pro) it had different checksum. After goin through all of the system files with md5 I had found over 500 defected files (out of 5500 total) and used rcp to copy those from the pentium pro. After that things have been working propely. I suspect that it was the NFS that had defected these files but I haven't had time to do extensive testing which I will do when get the time. Of course the problem might also be the int the harddisk but they would have to be quite subtle for the driver not to notice them and the disk has so far been quite reliable (4 gig Seagate Hawk4&1542 adaptec). I remember hearing something about nfs defecting files sometime agou but I don't quite remember what was it that caused it. - Marko From owner-freebsd-current Tue Dec 10 09:54:10 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA17731 for current-outgoing; Tue, 10 Dec 1996 09:54:10 -0800 (PST) Received: from hamby1.lightside.net (hamby1.lightside.net [207.67.176.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA17723 for ; Tue, 10 Dec 1996 09:54:06 -0800 (PST) Received: from localhost (jehamby@localhost) by hamby1.lightside.net (8.8.3/8.8.2) with SMTP id VAA00406; Sun, 8 Dec 1996 21:41:41 -0800 (PST) X-Authentication-Warning: hamby1.lightside.net: jehamby owned process doing -bs Date: Sun, 8 Dec 1996 21:41:40 -0800 (PST) From: Jake Hamby X-Sender: jehamby@hamby1 To: "Eric J. Chet" cc: alexj@motaba.tmc.edu.tw, freebsd-current@FreeBSD.ORG Subject: Re: Amazing to MIT Pthread-1.60b6 & Pthread built in FreeBSD-2.2-ALPHA 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 The "pgcc" he used was not Pentium-GCC but a wrapper around GCC to link with the pthreads library. So yes, I would assume that both tests were compiled with the same version of GCC. -- Jake On Tue, 10 Dec 1996, Eric J. Chet wrote: > On Tue, 10 Dec 1996 alexj@motaba.tmc.edu.tw wrote: > > > It surprised me so much !! > > > > I wrote a small program to test the performance of MIT PThread-1.60b6 (MIT) used in FreeBSD-2.2-ALPHA & the pthread built in FBSD-2.2-ALPHA (FBSD). > > > > I had thought that the performance of FBSD should be better than that of > > > > MIT. However, I am wrong after making this test. > > > > It's really amazing. The performance of MIT is much better than that > > > > of FBSD. > > > > Is there any problem in FreeBSD-2.2-ALPHA ? > > > > > > gcc pbench.c -lc_r > > > > ================================================================ > > > > FreeBSD 2.2-ALPHA built-in PTHREAD test.... > > > > Testing pthread_create() 1000 times...spending 3.228051 seconds > > > > Testing pthread_lock() 10000 times...spending 0.97357 seconds > > > > Testing pthread_yield() 10000 times...spending 12.1259162 seconds > > > > ================================================================ > > > > > > pgcc pbench.c > > > > ================================================================ > > > > MIT PTHREAD 1.60B6 performance test.... > > > > Testing pthread_create() 100000 times...spending 0.1063555 seconds > > > > Testing pthread_lock() 1000000 times...spending 1.168608 seconds > > > > Testing pthread_yield() 1000000 times...spending 9.333843 seconds > > > > ================================================================== > > > > > > The attachment is my program source code > > > > > > Hello > Could you please compile both versions with either gcc or pgcc, > those numbers are meaningless. > > Eric J. Chet > - ejc@bazzle.com From owner-freebsd-current Tue Dec 10 11:19:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA22968 for current-outgoing; Tue, 10 Dec 1996 11:19:06 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA22963 for ; Tue, 10 Dec 1996 11:19:02 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA04644; Tue, 10 Dec 1996 11:56:37 -0700 From: Terry Lambert Message-Id: <199612101856.LAA04644@phaeton.artisoft.com> Subject: Re: Amazing to MIT Pthread-1.60b6 & Pthread built in To: alexj@motaba.tmc.edu.tw Date: Tue, 10 Dec 1996 11:56:37 -0700 (MST) Cc: freebsd-current@freebsd.org In-Reply-To: <3.0.32.19961210135325.00de1af0@mail.tmc.edu.tw> from "alexj@motaba.tmc.edu.tw" at Dec 10, 96 01:53:25 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I wrote a small program to test the performance of MIT > PThread-1.60b6 (MIT) used in FreeBSD-2.2-ALPHA & the pthread built > in FBSD-2.2-ALPHA (FBSD). [ ... ] > gcc pbench.c -lc_r > ================================================================ > FreeBSD 2.2-ALPHA built-in PTHREAD test.... > Testing pthread_create() 1000 times...spending 3.228051 seconds [ ... ] > pgcc pbench.c > ================================================================ > MIT PTHREAD 1.60B6 performance test.... > Testing pthread_create() 100000 times...spending 0.1063555 seconds Some comments: 1) Why aren't you using gcc or pgcc for both? This is not a valid test unless everything other than the threads code itself is equal. 2) The MIT test does not appear to be using a thread safe C library; how can you expect this to work? 3) There is no obvious explanation for why your MIT iterations are 100 time your FreeBSD iterations. However, since you are apparently using statistical profiling methods, this would seem to related to thread context switch overhead being 100 times less important to the MIT numbers. This is not a valid test unless everything other than the threads code itself is equal. Statistical profiling is *very* sensitive to things like this -- that's why it is not a good method of benchmarking anything but absolutely identical environments with *exactly* one variable change (ie: comparing Linux vs. BSD with statistical methods is not valid, nor is comparing threading environments on a single OS when you change more than just the threading environment). 4) The FreeBSD lock times are better. Do you have a hypothesis why? Without an interpretation of the results of your test, the value of your test is reduced. This is because we can't look at the code and tell if there is a difference between what you intended to measure vs. what you actually did measure. This is not a defense of the FreeBSD code... but I am asking how you got from your results to the conclusions you drew because of your results; I don't see a valid logical path that leads from your results, inevitibly to your conclusions. 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 Tue Dec 10 11:27:35 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA23404 for current-outgoing; Tue, 10 Dec 1996 11:27:35 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA23397; Tue, 10 Dec 1996 11:27:30 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA04666; Tue, 10 Dec 1996 12:06:26 -0700 From: Terry Lambert Message-Id: <199612101906.MAA04666@phaeton.artisoft.com> Subject: Re: It works! Solved my problem wih Etherlink III on AcerNote Light To: grog@lemis.de (Greg Lehey) Date: Tue, 10 Dec 1996 12:06:26 -0700 (MST) Cc: freebsd-mobile@freebsd.org, FreeBSD-current@freebsd.org In-Reply-To: <199612101054.LAA18102@freebie.lemis.de> from "Greg Lehey" at Dec 10, 96 11:54:05 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > For those of you who've been following my tribulations installing > -current on an AcerNote Light, the good news: finally it works. [ ... ] > So then I built a -current kernel without crd0 and pcic[01]. It > FOund the baord. And it was able to correctly configure zp0. But > I still couldn't get things to work. On closer examination, there > seems to be something wrong with the routing table entry: there > was no entry at all for zp0, and I couldn't find a way to put one > in. In /etc/sysconfig, I did effectively: > > ifconfig lp0 192.109.197.159 192.109.197.137 > ifconfig zp0 192.109.197.159 This is incorrect. You have "named" both interfaces the same IP "name". You can't do this, it's not legal. If it works at all, it has more to do with assignment order, and the resulting bogus data in your routing table, and which bogus route is found first during a linear traversal, than anything else. Consider: I am your kernel... I have a packet for 192.109.197.158; do I send it out your parallel port or your ethernet card? > So I removed lp0 from /etc/sysconfig and rebooted. Now the > routing tables looked OK, but it still didn't work. OK, I've got > RG-58, what links do I need? Where's the man page for zp? > Nowhere. I played around with the links and found that link1 will > do the trick: it works. Not very fast, but it works. The hard > disk on this machine seems to be the slowest I've every come > across. ftp'ing a 67 MB file gave me a throughput of about 220 > kB/s when copying to disk, about 750 kB/s when copying to > /dev/null. By comparison, the same file ftp'd to (IDE) disk on > freebie at 860 kB/s, and to /dev/null at 940 kB/s. The error rate > might explain some of this: on freebie, netstat -in shows: I can't explain the error rate. Does it claim that the card is bogus at boot time? There were some rent patches for (589?) which might be applicable. The 3COM stuff is notoriously variable in their detection interface design... moreso than almost any other devices (well, except ATAPI CDROMs). 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 Tue Dec 10 12:22:39 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA26882 for current-outgoing; Tue, 10 Dec 1996 12:22:39 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA26865; Tue, 10 Dec 1996 12:22:34 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA08722; Tue, 10 Dec 1996 13:18:49 -0700 (MST) Date: Tue, 10 Dec 1996 13:18:49 -0700 (MST) Message-Id: <199612102018.NAA08722@rocky.mt.sri.com> From: Nate Williams To: Terry Lambert Cc: grog@lemis.de (Greg Lehey), freebsd-mobile@freebsd.org, FreeBSD-current@freebsd.org Subject: Re: It works! Solved my problem wih Etherlink III on AcerNote Light In-Reply-To: <199612101906.MAA04666@phaeton.artisoft.com> References: <199612101054.LAA18102@freebie.lemis.de> <199612101906.MAA04666@phaeton.artisoft.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > ifconfig lp0 192.109.197.159 192.109.197.137 > > ifconfig zp0 192.109.197.159 > > This is incorrect. Youare correct, but it is allowed on Point-Point interfaces and doesn't cause problems because of host routes. Nate From owner-freebsd-current Tue Dec 10 12:38:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA28168 for current-outgoing; Tue, 10 Dec 1996 12:38:41 -0800 (PST) Received: from inga.augusta.de (root@inga.augusta.de [193.175.23.65]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA28163 for ; Tue, 10 Dec 1996 12:38:38 -0800 (PST) Received: from rabbit by inga.augusta.de with uucp (Smail3.1.29.1 #1) id m0vXYr2-004cqiC; Tue, 10 Dec 96 21:32 MET Received: by rabbit.augusta.de (Smail3.1.29.1 #1) id m0vXYLi-000FzfC; Tue, 10 Dec 96 21:00 MET Message-Id: Date: Tue, 10 Dec 96 21:00 MET Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Organization: Privat Site running FreeBSD References: <199612081624.LAA23662@ylana.vet.purdue.edu> In-Reply-To: <199612081624.LAA23662@ylana.vet.purdue.edu> From: shanee@rabbit.augusta.de (Andreas Kohout) Subject: Re: ctm delta src-cur.2484.gz mangled? X-Original-Newsgroups: muc.lists.freebsd.current To: current@freebsd.org, blewis@vet.purdue.edu Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199612081624.LAA23662@ylana.vet.purdue.edu>, blewis@vet.purdue.edu (Benjamin Lewis) writes: > I'm having trouble applying ctm delta src-cur.2484.gz: > > ylana:/usr/src [143]#ctm -v -v ctms/src-cur.2484.gz > Working on > Expecting Global MD5 <050901836fc100ca56044c7706b85623> > Reference Global MD5 <050901836fc100ca56044c7706b85623> > FN: share/doc/handbook/contrib.sgml md5 mismatch. > FN: share/doc/handbook/contrib.sgml edit fails. > Exit(104) sorry, but here it works just well ... 1996-12-10 20:44 ctm: > FS .ctm_status 1996-12-10 20:44 ctm: > FN gnu/libexec/uucp/common_sources/policy.h 1996-12-10 20:44 ctm: > FN lib/libc/sys/setuid.2 1996-12-10 20:44 ctm: > FN share/doc/handbook/contrib.sgml 1996-12-10 20:44 ctm: > FN share/doc/ja_JP.EUC/handbook/authors.sgml 1996-12-10 20:44 ctm: > FN sys/sys/unistd.h 1996-12-10 20:44 ctm: > FN sys/vm/vm_map.c 1996-12-10 20:44 ctm: > FN sys/vm/vm_map.h 1996-12-10 20:44 ctm: All done ok 1996-12-10 20:44 ctm: Exit(0) 1996-12-10 20:44 src-cur.2484.gz applied I use ctm_rmail to apply the deltas: ctm_rmail -p /tmp -d /s-ctm -b /usr/src -l /tmp/log /s-ctm (I hope this is correct :-) If you like, I´ll send the contrib.sgml to you ... -- Greeting, Andy running FreeBSD-current --------------------------------------------------------------------------- From owner-freebsd-current Tue Dec 10 13:30:29 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA02659 for current-outgoing; Tue, 10 Dec 1996 13:30:29 -0800 (PST) Received: from relay.internode.net (mail.internode.net [198.161.228.50]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA02650 for ; Tue, 10 Dec 1996 13:30:24 -0800 (PST) Date: Tue, 10 Dec 1996 13:30:24 -0800 (PST) Received: from [198.161.228.104] by relay.internode.net (SMTPD32-3.02) id A4037D5009E; Tue, 10 Dec 1996 14:20:03 -0700 Message-Id: <1.5.4.16.19961210143123.0a0f855a@internode.net> X-Sender: drussell@internode.net X-Mailer: Windows Eudora Light Version 1.5.4 (16) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: current@freebsd.org From: Doug Russell Subject: 2.2-ALPHA Upgrade Question/Problem Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there some kind of a known bug in the 2.2-ALPHA install program (from boot.flp) which kills off the partition table when you try to upgrade? I tried it twice to verify that there was a problem. I was running 2.1.0 on two of my machines, 486quick150 and hobbes. I upgraded 486Quick150 to 2.1.5 many weeks ago, and upgraded hobbes to 2.1.6 later with no problems using the upgrade routine in sysinstall. I tried upgrading to 2.2-ALPHA on hobbes the other night, and it toasted the parition table by the time I got to disklabel to mount the existing partitions (in the upgrade process). There was nothing there to mount. I figured it was a fluke, but I re-installed 2.1.6 and tried upgrading again to be sure. It toasted the partition again, so something is a little whacky in there, especially since the routine in 2.1.6 works fine. Any ideas? Later...... From owner-freebsd-current Tue Dec 10 14:00:07 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA05254 for current-outgoing; Tue, 10 Dec 1996 14:00:07 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA05247; Tue, 10 Dec 1996 14:00:04 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA04945; Tue, 10 Dec 1996 14:38:17 -0700 From: Terry Lambert Message-Id: <199612102138.OAA04945@phaeton.artisoft.com> Subject: Re: It works! Solved my problem wih Etherlink III on AcerNote Light To: nate@mt.sri.com (Nate Williams) Date: Tue, 10 Dec 1996 14:38:17 -0700 (MST) Cc: terry@lambert.org, grog@lemis.de, freebsd-mobile@freebsd.org, FreeBSD-current@freebsd.org In-Reply-To: <199612102018.NAA08722@rocky.mt.sri.com> from "Nate Williams" at Dec 10, 96 01:18: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 > > > ifconfig lp0 192.109.197.159 192.109.197.137 > > > ifconfig zp0 192.109.197.159 > > > > This is incorrect. > > Youare correct, but it is allowed on Point-Point interfaces and doesn't > cause problems because of host routes. Hmmm... How do I tell the difference between a PPP connection that is a connection to a subnet and a PPP connection that is my connection to the Internet, such that I (as the PPP) will set up the correct host and default routes? This actually bears on the modem/ethernet combo card case, or the case of an undocked laptop with an ethernet in the docking adapter, but an IR connector otherwise: I should have a marked preference for the faster media when equivalent media are available. Windows95 RAS (Remote Access Services) has a checkbox on their properties sheet for this: First: open My computer open Dial-Up Networking right-button(properties) on a connection icon Then: click the "Server Type..." button to open the "Server Types" window click the "TCP/IP Settings..." button to open the "TCP/IP Settings" window Then: "Use default gateway on remote network" is checked: - Deletes the previous default route to the local network adapter card - Adds a default route for all network addresses *except* those for which a subnet route already exists to the Windows95 routing table (use the undocumented "ROUTE PRINT" command in a Windows95 DOS box) "Use default gateway on remote network" is not checked: - Adds a route for the subnet for the network (logical subnetting is not allowed) for the dialed target IP address In other words, if I have a local network connection, and I dial up my pop account at my ISP, then Windows95 tends to screw up the routing while the connection is up. At least it has the checkbox, though... and you *can* hack the routing table manually, if you absolutely need to (though multiple NIC point-to-point routing is not supported without a lot of hacking, running a ported routed, and doing the registry hack that differentiates WindowsNT Worstation from WindowsNT Server (only Win95 doesn't have the thread that runs once a clock tick to hack this value back like Workstation does). In any case, it seems to me that you would have to name them differently in BSD, since in BSD, the interfaces are actually route destinations. Maybe he is running routed? I'll bet that would cause the behaviour, if it's otherwise legal, like you say, to name them the same IP address. 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 Tue Dec 10 14:16:43 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA06632 for current-outgoing; Tue, 10 Dec 1996 14:16:43 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA06613; Tue, 10 Dec 1996 14:16:34 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA09166; Tue, 10 Dec 1996 15:12:49 -0700 (MST) Date: Tue, 10 Dec 1996 15:12:49 -0700 (MST) Message-Id: <199612102212.PAA09166@rocky.mt.sri.com> From: Nate Williams To: Terry Lambert Cc: nate@mt.sri.com (Nate Williams), freebsd-mobile@freebsd.org, FreeBSD-current@freebsd.org Subject: Re: It works! Solved my problem wih Etherlink III on AcerNote Light In-Reply-To: <199612102138.OAA04945@phaeton.artisoft.com> References: <199612102018.NAA08722@rocky.mt.sri.com> <199612102138.OAA04945@phaeton.artisoft.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert writes: > > > > ifconfig lp0 192.109.197.159 192.109.197.137 > > > > ifconfig zp0 192.109.197.159 > > > > > > This is incorrect. > > > > You are correct, but it is allowed on Point-Point interfaces and doesn't > > cause problems because of host routes. > > Hmmm... > > How do I tell the difference between a PPP connection that is a > connection to a subnet and a PPP connection that is my connection > to the Internet, such that I (as the PPP) will set up the correct > host and default routes? Every PPP connection is a connection to a 'network', and you will use a 'default' route to have any unknown packets sent to a machine that knows what to do with them, otherwise you rely on addresses/masks. That's why you have default routes. > This actually bears on the modem/ethernet combo card case, or the case > of an undocked laptop with an ethernet in the docking adapter, but > an IR connector otherwise: I should have a marked preference for > the faster media when equivalent media are available. Then you have a 'dual-homed' setup, which is both non-trivial to setup and non-standard. You have to have something like gateD which exchanges routing information from the 'routers' you are connected to in order to do this correctly. > Windows95 RAS (Remote Access Services) has a checkbox on their > properties sheet for this: > - Deletes the previous default route to the local > network adapter card We don't do this. > - Adds a default route for all network addresses > *except* those for which a subnet route already > exists to the Windows95 routing table (use the > undocumented "ROUTE PRINT" command in a Windows95 > DOS box) A 'default' route is a 'default' route. If you don't know what to do with a packet send it to the default route. IT doesn't add routing entries for every known route, it simply states 'if you don't have an existing routing entry, punt it to the 'default' machine. > "Use default gateway on remote network" is not checked: > > - Adds a route for the subnet for the network > (logical subnetting is not allowed) for the > dialed target IP address If you don't where to send it, drop it. No 'default' route exists. In unix, this would be: # route add default ISP.route.net OR not. (This assumes you aren't running routed which listens for default routes that are broadcast, which Win95 doesn't do.) In freeBSD you either have the defaultroute entry set in /etc/sysconfig or not, which does the above command. > In other words, if I have a local network connection, and I dial > up my pop account at my ISP, then Windows95 tends to screw up the > routing while the connection is up. It certainly shouldn't, and doesn't on any of my boxes. Nate From owner-freebsd-current Tue Dec 10 16:20:56 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA15367 for current-outgoing; Tue, 10 Dec 1996 16:20:56 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA15361; Tue, 10 Dec 1996 16:20:51 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id KAA19960; Wed, 11 Dec 1996 10:49:03 +1030 (CST) From: Michael Smith Message-Id: <199612110019.KAA19960@genesis.atrad.adelaide.edu.au> Subject: Re: It works! Solved my problem wih Etherlink III on AcerNote Light In-Reply-To: <199612101906.MAA04666@phaeton.artisoft.com> from Terry Lambert at "Dec 10, 96 12:06:26 pm" To: terry@lambert.org (Terry Lambert) Date: Wed, 11 Dec 1996 10:49:01 +1030 (CST) Cc: grog@lemis.de, freebsd-mobile@FreeBSD.ORG, FreeBSD-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 Terry Lambert stands accused of saying: > > in. In /etc/sysconfig, I did effectively: > > > > ifconfig lp0 192.109.197.159 192.109.197.137 > > ifconfig zp0 192.109.197.159 > > This is incorrect. This is perfectly legitimate. The 'lp' interface is p2p, and the routing entry is a host route for the other end of the link. > Consider: I am your kernel... I have a packet for 192.109.197.158; do > I send it out your parallel port or your ethernet card? The ethernet, obviously. > Terry Lambert -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Dec 10 17:09:14 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA18493 for current-outgoing; Tue, 10 Dec 1996 17:09:14 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA18482; Tue, 10 Dec 1996 17:09:11 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA05309; Tue, 10 Dec 1996 17:47:27 -0700 From: Terry Lambert Message-Id: <199612110047.RAA05309@phaeton.artisoft.com> Subject: Re: It works! Solved my problem wih Etherlink III on AcerNote Light To: nate@mt.sri.com (Nate Williams) Date: Tue, 10 Dec 1996 17:47:26 -0700 (MST) Cc: terry@lambert.org, nate@mt.sri.com, freebsd-mobile@freebsd.org, FreeBSD-current@freebsd.org In-Reply-To: <199612102212.PAA09166@rocky.mt.sri.com> from "Nate Williams" at Dec 10, 96 03:12: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 > > In other words, if I have a local network connection, and I dial > > up my pop account at my ISP, then Windows95 tends to screw up the > > routing while the connection is up. > > It certainly shouldn't, and doesn't on any of my boxes. Try running *any* proxy server for going from NETBEUI or IPX based winsock.dll or wsock32.dll clients to a Windows95 box running the proxy server to gate the socket calls. If the Win95 box has a local network connection and supports RAS, when a RAS connection is present, all packets will be sent to the RAS connection, even if only one client has specified a RAS port for its connection and all other clients have specified using the local network connection. You would run into this if you have a branch office connected by intermittent connection instead of dedicated line. You don't notice that it's sending all the packets to the wrong place if your test setup also has a local (real) net connection. But it is. As far as why it happens, well, Win95 does not support routing between local cards based on subnet correctly -- ie: a Win95 box is not a router. This relates to the original topic in that a Win95 box with two network interfaces "named" the same network address will act as you described -- IF you do not need it to route. Anyway, this is all very special case, and is probably more interesting to people into nomadic computing that the majority of the people on this list. I was just curious as to what would happen when it was put in this environment (in case that's what he meant when he said he had another machine with a "near identical setup" which worked... it might have been non-FreeBSD. Back to your regularly scheduled postings... 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 Dec 10 19:28:35 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA03928 for current-outgoing; Tue, 10 Dec 1996 19:28:35 -0800 (PST) Received: from ylana.vet.purdue.edu (vet.vet.purdue.edu [128.210.96.50]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA03900 for ; Tue, 10 Dec 1996 19:28:27 -0800 (PST) Received: from ylana.vet.purdue.edu (localhost.vet.purdue.edu [127.0.0.1]) by ylana.vet.purdue.edu (8.8.3/8.7.3) with ESMTP id WAA26821; Tue, 10 Dec 1996 22:28:34 -0500 (EST) Message-Id: <199612110328.WAA26821@ylana.vet.purdue.edu> X-Mailer: exmh version 1.6.9 8/22/96 To: shanee@rabbit.augusta.de (Andreas Kohout) cc: current@freebsd.org, blewis@vet.purdue.edu Subject: Re: ctm delta src-cur.2484.gz mangled? In-reply-to: Your message of "Tue, 10 Dec 1996 21:00:00 +0700." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Tue, 10 Dec 1996 22:28:33 -0500 From: Benjamin Lewis Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by freefall.freebsd.org id TAA03924 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Andy: Thank you for taking the time to reply to my message, I really appreciate it. You wrote: [deleted] > sorry, but here it works just well ... [deleted] I don't understand why it only seemed to fail on my system, but I think I've sorted it out. I ended up grabbing a new copy of contrib.sgml from ftp.freebsd.org and dropping it into my src tree. So far, things seem to be working OK. > If you like, I´ll send the contrib.sgml to you ... I really appreciate the offer. I think my src tree is back in working order, but I may take you up on it later if things fall apart again. Thanks again, -Ben -- Benjamin Lewis | "Don't let your schooling interfere bhlewis@purdue.edu | with your education." | -- Mark Twain From owner-freebsd-current Tue Dec 10 20:17:14 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA08467 for current-outgoing; Tue, 10 Dec 1996 20:17:14 -0800 (PST) Received: from hemi.com (hemi.com [204.132.158.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA08453 for ; Tue, 10 Dec 1996 20:17:11 -0800 (PST) Received: (from mbarkah@localhost) by hemi.com (8.8.4/8.7.3) id VAA03860 for freebsd-current@freebsd.org; Tue, 10 Dec 1996 21:17:04 -0700 (MST) From: Ade Barkah Message-Id: <199612110417.VAA03860@hemi.com> Subject: Sup gets access denied for bison/lex.h To: freebsd-current@freebsd.org Date: Tue, 10 Dec 1996 21:17:04 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I tried to sup -current sources today, and: SUP: Access denied to contrib/bison/lex.h (I only noticed it when "make world" failed since this file is missing.) Thanks, -Ade ------------------------------------------------------------------- Inet: mbarkah@hemi.com - HEMISPHERE ONLINE - ------------------------------------------------------------------- From owner-freebsd-current Tue Dec 10 20:50:40 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA11706 for current-outgoing; Tue, 10 Dec 1996 20:50:40 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA11701 for ; Tue, 10 Dec 1996 20:50:38 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id UAA02158; Tue, 10 Dec 1996 20:50:30 -0800 (PST) To: Doug Russell cc: current@freebsd.org Subject: Re: 2.2-ALPHA Upgrade Question/Problem In-reply-to: Your message of "Tue, 10 Dec 1996 13:30:24 PST." <1.5.4.16.19961210143123.0a0f855a@internode.net> Date: Tue, 10 Dec 1996 20:50:30 -0800 Message-ID: <2154.850279830@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Is there some kind of a known bug in the 2.2-ALPHA install program (from > boot.flp) which kills off the partition table when you try to upgrade? I > tried it twice to verify that there was a problem. No, not a known one. :-( I'll try an upgrade later on today with 2.2-almost-BETA Jordan From owner-freebsd-current Tue Dec 10 23:43:40 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA24575 for current-outgoing; Tue, 10 Dec 1996 23:43:40 -0800 (PST) Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id XAA24570 for ; Tue, 10 Dec 1996 23:43:37 -0800 (PST) From: Greg Lehey Received: from freebie.lemis.de by diablo.ppp.de with smtp (Smail3.1.28.1 #1) id m0vXjKF-000QXzC; Wed, 11 Dec 96 08:43 MET Received: (grog@localhost) by freebie.lemis.de (8.8.4/8.6.12) id IAA02737; Wed, 11 Dec 1996 08:07:54 +0100 (MET) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Message-Id: <199612110707.IAA02737@freebie.lemis.de> Subject: Re: It works! Solved my problem wih Etherlink III on AcerNote Light In-Reply-To: <199612101906.MAA04666@phaeton.artisoft.com> from Terry Lambert at "Dec 10, 96 12:06:26 pm" To: terry@lambert.org (Terry Lambert) Date: Wed, 11 Dec 1996 08:07:53 +0100 (MET) Cc: FreeBSD-current@FreeBSD.ORG (FreeBSD current users) 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 (dropping -mobile from this list--it's not really a notebook issue) Terry Lambert writes: >> For those of you who've been following my tribulations installing >> -current on an AcerNote Light, the good news: finally it works. > >> ... ] > >> So then I built a -current kernel without crd0 and pcic[01]. It >> FOund the baord. And it was able to correctly configure zp0. But >> I still couldn't get things to work. On closer examination, there >> seems to be something wrong with the routing table entry: there >> was no entry at all for zp0, and I couldn't find a way to put one >> in. In /etc/sysconfig, I did effectively: >> >> ifconfig lp0 192.109.197.159 192.109.197.137 >> ifconfig zp0 192.109.197.159 > > This is incorrect. This is correct and valid. > You have "named" both interfaces the same IP "name". No. The first interface is lp0. The second interface is zp0. They have different names, only the address is the same. That's a big difference. > You can't do this, it's not legal. You can do this, it's legal. > If it works at all, it has more to do with assignment order, and the > resulting bogus data in your routing table, and which bogus route is > found first during a linear traversal, than anything else. You've touched on the truth, and passed it by. > Consider: I am your kernel... I have a packet for 192.109.197.158; do > I send it out your parallel port or your ethernet card? In the above, it looks as if you're saying "you can't have two interfaces with the same address", but I'm not sure that's what you want to say. Maybe you want to say "you can't have two routing table entries, one of which is a subset of the other. Either way you're wrong. You look in the routing table. In the case I was talking about, there was no entry for zp0, and that's what I was complaining about. Compare page 39 of TCP/IP illustrated, volume 1. Routing does: 1. Look for the complete destination IP address in the routing table. If found, use it. In our case, this would be lp0. 2. Otherwise, look for the network ID in the routing table. If found, use it. In our case, this would be zp0, if it were there. 3. Otherwise look for a default entry. If found, use it. Otherwise 'network is unreachable'. This is done rather more elegantly than this description suggests in the function rn_match in net/radix.c. It does a single linear traversal and looks for the matching entry with the longest net mask. Having said this, you might be amused by freebie's complete interface settings: lp0: flags=8851 mtu 1500 inet 192.109.197.137 --> 192.109.197.159 netmask 0xffffff00 ep0: flags=8843 mtu 1500 inet 192.109.197.137 netmask 0xffffff00 broadcast 192.109.197.255 ether 00:a0:24:37:0d:2b ipi0: flags=811 mtu 1500 inet 192.109.197.137 --> 194.163.31.4 netmask 0xffffffc0 ipi1: flags=811 mtu 1500 inet 192.109.197.137 --> 194.64.112.1 netmask 0xffffff00 ipi2: flags=811 mtu 1500 inet 192.109.197.137 --> 194.163.31.129 netmask 0xffffffc0 ipi3: flags=811 mtu 1500 inet 192.109.197.37 --> 192.109.197.38 netmask 0xffffff00 ipi4: flags=811 mtu 1500 inet 192.109.197.148 --> 194.77.2.34 netmask 0xffffff00 ipi5: flags=811 mtu 1500 inet 192.109.197.137 --> 194.163.31.1 netmask 0xffffffc0 ipi6: flags=811 mtu 1500 inet 192.109.197.137 --> 192.129.52.242 netmask 0xffffff00 ipi9: flags=811 mtu 1500 inet 194.97.201.66 --> 194.97.201.9 netmask 0xffffff00 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 The ipi are ISDN interfaces. BTW, as I mentioned yesterday, I thought something else had gone wrong. It looks like it had. I can take both interfaces up and down, and the routing table is updated correctly. >> ftp'ing a 67 MB file gave me a throughput of about 220 >> kB/s when copying to disk, about 750 kB/s when copying to >> /dev/null. By comparison, the same file ftp'd to (IDE) disk on >> freebie at 860 kB/s, and to /dev/null at 940 kB/s. The error rate >> might explain some of this: on freebie, netstat -in shows: > > I can't explain the error rate. Does it claim that the card is bogus > at boot time? No. > There were some rent patches for (589?) which might > be applicable. This was with -current as of Tuesday. The latest cvs update was cvs-cur.2791.gz. I haven't seen any relevant patches come in since then. > The 3COM stuff is notoriously variable in their detection interface > design... moreso than almost any other devices (well, except ATAPI > CDROMs). Interesting. In the meantime I've spoken with 3com, and I'm gradually left with the impression that the detection problem is with the AcerNote PCMCIA interface, and not with the board. The other problems remain. Anyway, maybe the problems were related to my startup attempts. I've since rebooted the machine, and when I look now I see: Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll zp0 1500 00.60.97.40.fb.e1 39442 0 39038 10 0 zp0 1500 192.109.197 192.109.197.159 39442 0 39038 10 0 That looks a lot more healthy. I've noticed that the machine seems to go into some kind of power-save mode when it's closed, and that causes it to respond more slowly. Maybe the oerrs are related to that. Greg From owner-freebsd-current Tue Dec 10 23:43:53 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA24598 for current-outgoing; Tue, 10 Dec 1996 23:43:53 -0800 (PST) Received: from tahoma.cwu.edu (skynyrd@tahoma.cwu.edu [198.104.65.220]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id XAA24593 for ; Tue, 10 Dec 1996 23:43:51 -0800 (PST) Received: by tahoma.cwu.edu; id AA12494; Tue, 10 Dec 1996 23:43:45 -0800 Date: Tue, 10 Dec 1996 23:43:45 -0800 (PST) From: Chris Timmons To: FreeBSD-current@freebsd.org Subject: Re: Problems with PLIP driver? In-Reply-To: <96Dec7.103059pst.177711@crevenia.parc.xerox.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 "Well, lets keep in mind that PLIP is a disgusting thing in the first place, but as we all know, in certain circumstances that may not matter." -Poul-Henning Kamp, noted FreeBSD developer (I'm sorry - I saved this a few months ago and put it into my .plan and just couldn't help but resurrect it after a peek in the code :) -c On Sat, 7 Dec 1996, Bill Fenner wrote: > I'm wrong, it's more than just the header. I went through this in > great detail quite a while ago. Look at ppp and tun for hints, > you probably have to change the bpf_attach() call too. And I'd > move the bpf_mtap() in the output routine way up to the top, > since right now it completely misses the LINK0 case, and even > if it doesn't the output routine has already zeroed out the length > field in each mbuf in the chain. > > Fun fun. > > Bill > From owner-freebsd-current Wed Dec 11 01:07:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA27883 for current-outgoing; Wed, 11 Dec 1996 01:07:58 -0800 (PST) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA27878; Wed, 11 Dec 1996 01:07:50 -0800 (PST) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.3/8.8.3) id LAA04906; Wed, 11 Dec 1996 11:06:03 +0200 (EET) From: mika ruohotie Message-Id: <199612110906.LAA04906@shadows.aeon.net> Subject: Re: It works! Solved my problem wih Etherlink III on AcerNote Light To: nate@mt.sri.com (Nate Williams) Date: Wed, 11 Dec 1996 11:06:02 +0200 (EET) Cc: terry@lambert.org, nate@mt.sri.com, freebsd-mobile@freebsd.org, FreeBSD-current@freebsd.org In-Reply-To: <199612102212.PAA09166@rocky.mt.sri.com> from Nate Williams at "Dec 10, 96 03:12:49 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > In other words, if I have a local network connection, and I dial > > up my pop account at my ISP, then Windows95 tends to screw up the > > routing while the connection is up. > It certainly shouldn't, and doesn't on any of my boxes. hmm? it shouldnt, but does. atleast in some way. i've learned the hard way that win95 have no idea how to do things freebsd does as a "trivia" (example, configuring different interfaces totally separatedly, including the host/domain names known for the interface) but that's why this is freebsd-* and not windows95-*... =) :P that's why i run freebsd on many machines, and win95 only on one desktop at work... my home p133 have never been infected with ms-code. > Nate mickey From owner-freebsd-current Wed Dec 11 07:36:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA16872 for current-outgoing; Wed, 11 Dec 1996 07:36:31 -0800 (PST) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA16864 for ; Wed, 11 Dec 1996 07:36:27 -0800 (PST) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id PAA05620 for ; Wed, 11 Dec 1996 15:38:22 GMT Date: Wed, 11 Dec 1996 15:38:22 +0000 (GMT) From: Developer To: freebsd-current@freebsd.org Subject: Problem PS command Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk There seems to be a problem with the ps command, which doesn't occur with top or the process filing system. Sometimes ps -ax just hangs up and has to be kill -9'ed.. The problem is when it's in scripts is really messes things up. Has anyone got any ideas why this might be? Please could you reply by email. Thanks in Advance. Trefor S. From owner-freebsd-current Wed Dec 11 08:36:14 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA20521 for current-outgoing; Wed, 11 Dec 1996 08:36:14 -0800 (PST) Received: from smyrno.sol.net (smyrno.sol.net [206.55.64.117]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA20511; Wed, 11 Dec 1996 08:36:06 -0800 (PST) Received: from solaria.sol.net (solaria.sol.net [206.55.65.75]) by smyrno.sol.net (8.8.3/8.8.3) with SMTP id KAA23321; Wed, 11 Dec 1996 10:35:34 -0600 (CST) Received: from localhost by solaria.sol.net (8.5/8.5) id KAA03706; Wed, 11 Dec 1996 10:36:02 -0600 From: Joe Greco Message-Id: <199612111636.KAA03706@solaria.sol.net> Subject: mlocking an mmap'ped region? To: current@freebsd.org, dyson@freebsd.org Date: Wed, 11 Dec 96 10:35:59 CST X-Mailer: ELM [version 2.4dev PL65] MIME-Version: 1.0 Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The following does not seem to work on a 2.2-CURRENT box (built yesterday). It does seem to work on SunOS. Is it just too early to be doing programming or is there really something preventing me from doing this? Thanks, ... JG #include #include #include #include #include #include #include /* * mlock-files - read a list of files on stdin, mmap() them, mlock() them, * and then sleep forever. */ int mapper(fd) int fd; { struct stat sb; size_t size; caddr_t map; if (fstat(fd, &sb) < 0) { perror("fstat"); close(fd); return(-1); } size = (size_t)sb.st_size; if ((int)(map = mmap(NULL, size, PROT_READ, MAP_SHARED, fd, 0)) == -1) { perror("mmap"); close(fd); return(-1); } if (mlock(map, size) < 0) { perror("mlock"); fprintf(stderr, "map = %08x eof=%d\n", map, size); close(fd); return(-1); } else { fprintf(stderr, "allocated map = %08x eof=%d\n", map, size); } close(fd); return(0); } int main(int argc, char *argv[]) { int fd; char buffer[8192]; if (argc != 1) { fprintf(stderr, "usage: mlock-files\n"); exit(1); } while (! feof(stdin)) { fgets(buffer, sizeof(buffer), stdin); if (strchr(buffer, '\n')) { *strchr(buffer, '\n') = '\0'; } if (! feof(stdin)) { if ((fd = open(buffer, O_RDONLY, 0755)) < 0) { perror(buffer); } else { mapper(fd); } } } sleep(99999999); } -- ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-current Wed Dec 11 09:29:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA23513 for current-outgoing; Wed, 11 Dec 1996 09:29:19 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA23504; Wed, 11 Dec 1996 09:29:08 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id MAA03619; Wed, 11 Dec 1996 12:27:45 -0500 (EST) From: John Dyson Message-Id: <199612111727.MAA03619@dyson.iquest.net> Subject: Re: mlocking an mmap'ped region? To: jgreco@solaria.sol.net (Joe Greco) Date: Wed, 11 Dec 1996 12:27:45 -0500 (EST) Cc: current@freebsd.org, dyson@freebsd.org In-Reply-To: <199612111636.KAA03706@solaria.sol.net> from "Joe Greco" at Dec 11, 96 10:35:59 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 > The following does not seem to work on a 2.2-CURRENT box (built yesterday). > It does seem to work on SunOS. > > Is it just too early to be doing programming or is there really something > preventing me from doing this? > Yep, it is called broken code :-(. That problem was just brought to my attention yesterday. Unfortunately, someone also wants it fixed in 2.1.X :-(. I'll probably get it fixed in -current in the next day or so. Doing mlock the way that it is currently done is problematical from a couple of viewpoints, so I think it is going to need to be reworked. Basically, the original way of doing vm_map_pageable is wrong for userland pages. (BTW, I seem to remember that someone had found this problem a year or so ago, and it fell through the cracks.) John From owner-freebsd-current Wed Dec 11 10:01:21 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA25583 for current-outgoing; Wed, 11 Dec 1996 10:01:21 -0800 (PST) Received: from freebsd.netcom.com (freebsd.netcom.com [198.211.79.3]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA25578 for ; Wed, 11 Dec 1996 10:01:19 -0800 (PST) Received: by freebsd.netcom.com (8.6.12/SMI-4.1) id MAA00824; Wed, 11 Dec 1996 12:00:47 -0600 From: bugs@freebsd.netcom.com (Mark Hittinger) Message-Id: <199612111800.MAA00824@freebsd.netcom.com> Subject: Re: mlocking an mmap'ped region? (fwd) To: current@freebsd.org Date: Wed, 11 Dec 1996 12:00:47 -0600 (CST) X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > The following does not seem to work on a 2.2-CURRENT box (built yesterday). > > It does seem to work on SunOS. > > > > Is it just too early to be doing programming or is there really something > > preventing me from doing this? > > > Yep, it is called broken code :-(. That problem was just brought to my > attention yesterday. Unfortunately, someone also wants it fixed in 2.1.X :-(. > > I'll probably get it fixed in -current in the next day or so. Doing mlock > the way that it is currently done is problematical from a couple of viewpoints, > so I think it is going to need to be reworked. Basically, the original > way of doing vm_map_pageable is wrong for userland pages. Isn't this also a big problem on SMP? :-) Later Mark Hittinger Netcom/Dallas bugs@freebsd.netcom.com From owner-freebsd-current Wed Dec 11 10:01:56 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA25648 for current-outgoing; Wed, 11 Dec 1996 10:01:56 -0800 (PST) Received: from smyrno.sol.net (smyrno.sol.net [206.55.64.117]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA25621; Wed, 11 Dec 1996 10:01:49 -0800 (PST) Received: from solaria.sol.net (solaria.sol.net [206.55.65.75]) by smyrno.sol.net (8.8.3/8.8.3) with SMTP id MAA23800; Wed, 11 Dec 1996 12:01:16 -0600 (CST) Received: from localhost by solaria.sol.net (8.5/8.5) id MAA04254; Wed, 11 Dec 1996 12:01:46 -0600 From: Joe Greco Message-Id: <199612111801.MAA04254@solaria.sol.net> Subject: Re: mlocking an mmap'ped region? To: dyson@FreeBSD.ORG Date: Wed, 11 Dec 96 12:01:44 CST Cc: current@FreeBSD.ORG In-Reply-To: <199612111727.MAA03619@dyson.iquest.net> from "John Dyson" at Dec 11, 96 12:27:45 pm X-Mailer: ELM [version 2.4dev PL65] MIME-Version: 1.0 Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > The following does not seem to work on a 2.2-CURRENT box (built yesterday). > > It does seem to work on SunOS. > > > > Is it just too early to be doing programming or is there really something > > preventing me from doing this? > > Yep, it is called broken code :-(. That problem was just brought to my > attention yesterday. Unfortunately, someone also wants it fixed in 2.1.X :-(. > > I'll probably get it fixed in -current in the next day or so. Doing mlock > the way that it is currently done is problematical from a couple of viewpoints, > so I think it is going to need to be reworked. Basically, the original > way of doing vm_map_pageable is wrong for userland pages. > > (BTW, I seem to remember that someone had found this problem a year or > so ago, and it fell through the cracks.) Hi! Might have been me, actually... I like coercing the system into doing what I really want it to do by tricks such as these. :-) I have a PPro200 sitting here and I was going to do a "find /usr/src -type f -print | mlock-files" before doing a make world and see what happened. With 224MB RAM and the /usr/src only taking 160MB of disk I figured it would be lots of fun to load all my source code into RAM and then make world. In any case, thanks... I was banging my head against a wall and I had done lots of things to find my "problem", then tried it on SunOS and it worked fine. :-/ So I started snooping around the kernel source code and decided that I did not want to try to comprehend the inner workings of vm_map_pageable (I had found the "return (error == KERN_SUCCESS ? 0 : ENOMEM);" and decided I was in over my head if it was a FreeBSD thing, when I started looking at vm_map_pageable's code). ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-current Wed Dec 11 10:27:29 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA27242 for current-outgoing; Wed, 11 Dec 1996 10:27:29 -0800 (PST) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA27237 for ; Wed, 11 Dec 1996 10:27:27 -0800 (PST) Received: from Mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.2/8.8.2) with ESMTP id MAA04704 for ; Wed, 11 Dec 1996 12:27:23 -0600 (CST) Received: from Mercury.mcs.net (jonas@Mercury.mcs.com [192.160.127.80]) by Mailbox.mcs.com (8.8.2/8.8.2) with ESMTP id MAA07988; Wed, 11 Dec 1996 12:27:06 -0600 (CST) Received: (from jonas@localhost) by Mercury.mcs.net (8.8.2/8.8.2) id MAA14540; Wed, 11 Dec 1996 12:25:43 -0600 (CST) From: Lars Jonas Olsson Message-Id: <199612111825.MAA14540@Mercury.mcs.net> Subject: dga crashes current To: current@freebsd.org Date: Wed, 11 Dec 1996 12:25:43 -0600 (CST) Cc: jonas@mcs.net X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Running the X program dga that test dga mode crashes current. To repeat: Set up for remote diagnostics (COMCONSOLE) set X for 256 colors run dga hit 'q' on the keyboard You will see: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xf3488ffd fault code = supervisor write, page not present instruction pointer = 0x8:0xf01b08f3 stack pointer = 0x10:0xefbffed8 frame pointer = 0x10:0xefbffef4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 203 (dga) interrupt mask = panic: page fault syncing disks... 40 40 37 33 14 2 done Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Jonas From owner-freebsd-current Wed Dec 11 11:53:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA03947 for current-outgoing; Wed, 11 Dec 1996 11:53:55 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA03942 for ; Wed, 11 Dec 1996 11:53:51 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id OAA03843; Wed, 11 Dec 1996 14:53:40 -0500 (EST) From: John Dyson Message-Id: <199612111953.OAA03843@dyson.iquest.net> Subject: Re: mlocking an mmap'ped region? (fwd) To: bugs@freebsd.netcom.com (Mark Hittinger) Date: Wed, 11 Dec 1996 14:53:40 -0500 (EST) Cc: current@freebsd.org In-Reply-To: <199612111800.MAA00824@freebsd.netcom.com> from "Mark Hittinger" at Dec 11, 96 12:00:47 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 > > > > I'll probably get it fixed in -current in the next day or so. Doing mlock > > the way that it is currently done is problematical from a couple of viewpoints, > > so I think it is going to need to be reworked. Basically, the original > > way of doing vm_map_pageable is wrong for userland pages. > > Isn't this also a big problem on SMP? :-) > It might be, but maybe not. vm_map_pageable actually does three things, wires the pages, puts the pages into the address space (faulting them), and marks the map entry wired. I think that the way that it does them is wrong for userland, and also there are some bad consequences during fork for wired map entries. I don't think that object chains are being handled properly in the code (last time that I looked.) I haven't done enough of an analysis on what needs to be done to stake a claim on a solution. I think that there are two (high level) problems with our memory lock code. Firstly, vm_map_pageable is not right for user land, and secondly we have not concept of a process lock (but just an address space lock.) I think that we need both, and mlock doesn't do everything that people want (esp regarding new pages.) John From owner-freebsd-current Wed Dec 11 13:15:44 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA10023 for current-outgoing; Wed, 11 Dec 1996 13:15:44 -0800 (PST) Received: from relay.internode.net (mail.internode.net [198.161.228.50]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA10014 for ; Wed, 11 Dec 1996 13:15:41 -0800 (PST) Date: Wed, 11 Dec 1996 13:15:41 -0800 (PST) Received: from [198.161.228.114] by relay.internode.net (SMTPD32-3.02) id A229DB000FE; Wed, 11 Dec 1996 14:05:45 -0700 Message-Id: <1.5.4.16.19961211141631.48873478@internode.net> X-Sender: drussell@internode.net X-Mailer: Windows Eudora Light Version 1.5.4 (16) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: "Jordan K. Hubbard" From: Doug Russell Subject: Re: 2.2-ALPHA Upgrade Question/Problem Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 08:50 PM 12/10/96 -0800, Jordan K. Hubbard wrote: >> Is there some kind of a known bug in the 2.2-ALPHA install program (from >> boot.flp) which kills off the partition table when you try to upgrade? I >> tried it twice to verify that there was a problem. > >No, not a known one. :-( > >I'll try an upgrade later on today with 2.2-almost-BETA > Hopefully it works. I will be trying it again on 486Quick150, probably on the weekend, assuming my new TR-4 drive gets here tomorrow so I can back the silly thing up without using 10 QIC-80 tapes. :-) The only (partially) saving grace is that hobbes has some slightly strange hardware. The machine is an old 386/40 ISA, and it uses a GSI model 21 EIDE controller with a Western Digital 2420 drive. The controller has it's own BIOS, so it COULD be some kind of whacky thing with this particular card. It still really irks me that it worked fine upgrading to 2.1.6, and now will not work going up to 2.2-ALPHA. In any case, 486Quick150 has a newer motherboard with a generic VESA EIDE controller (it uses an old OPTI chipset for the EIDE), so I will try it on there. I will also possibly try another VESA controller from another machine (I don't remember what it is, but it's different), and maybe even try it on my server machine (much newer on board PCI EIDE controller) and see what happens if it still doesn't work. Let me know if it is magically fixed in -current so I don't waste a bunch of time trying to find something that is already fixed. I've been too low on disk space to compile a -current, but I have 3 more 1.6 gig drives coming tomorrow which should fix that problem. I did something else silly in the install program last night installing 2.2-ALPHA from scratch onto Hobbes. It sig 11'd and said "I'm Dead". but I cannot for the life of me remember what I was doing. Don't worry too much about that one, as I think I did something stupid rather than the install program. (not that it should ever die...). If I can remember what it is, or I run into it again, I'll let you know. Later...... From owner-freebsd-current Wed Dec 11 13:34:48 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA11093 for current-outgoing; Wed, 11 Dec 1996 13:34:48 -0800 (PST) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA11088 for ; Wed, 11 Dec 1996 13:34:42 -0800 (PST) Received: from Mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.2/8.8.2) with ESMTP id PAA13487 for ; Wed, 11 Dec 1996 15:34:36 -0600 (CST) Received: from Mercury.mcs.net (jonas@Mercury.mcs.com [192.160.127.80]) by Mailbox.mcs.com (8.8.2/8.8.2) with ESMTP id PAA12682; Wed, 11 Dec 1996 15:34:12 -0600 (CST) Received: (from jonas@localhost) by Mercury.mcs.net (8.8.2/8.8.2) id PAA04909; Wed, 11 Dec 1996 15:34:07 -0600 (CST) From: Lars Jonas Olsson Message-Id: <199612112134.PAA04909@Mercury.mcs.net> Subject: remote gdb To: current@freebsd.org Date: Wed, 11 Dec 1996 15:34:07 -0600 (CST) Cc: jonas@mcs.net X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm debugging dga related (mprotect) related panics in cuyrrent. I'm doing it with remote gdb like: Have options DDB in config file SMARTDEBUG config -g SMARTDEBUG make the kernel cp kernel kernel.debug strip -d kernel install kernel on machine that panics. install kernel.debug on remote machine Boot machine to be debugged with -g start gdb on other machine in directory with kernel.debug in it. amcell1# gdb kernel.debug 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) target remote /dev/cuaa1 Remote debugging using /dev/cuaa1 pmap_protect (pmap=0xf2357864, sva=135467008, eva=139661312, prot=1) at ../../i386/i386/pmap.c:1874 ../../i386/i386/pmap.c:1874: No such file or directory. (gdb) dir /amcell2/new/src/sys/compile/SMARTDEBUG Source directories searched: /amcell2/new/src/sys/compile/SMARTDEBUG:$cdir:$cwd (gdb) bt #0 pmap_protect (pmap=0xf2357864, sva=135467008, eva=139661312, prot=1) at ../../i386/i386/pmap.c:1874 #1 0xf01a396e in vm_map_protect (map=0xf2357800, start=135467008, end=139661312, new_prot=1 '\001', set_max=0) at ../../vm/vm_map.c:1201 #2 0xf01a566e in mprotect (p=0xf234a200, uap=0xefbfff94, retval=0xefbfff84) at ../../vm/vm_mmap.c:484 #3 0xf01bc72b in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 24576, tf_esi = 0, tf_ebp = -272640728, tf_isp = -272629788, tf_ebx = 0, tf_edx = -272641536, tf_ecx = -272641536, tf_eax = 74, tf_trapno = 12, tf_err = 7, tf_eip = 135115361, tf_cs = 31, tf_eflags = 642, tf_esp = -272640756, tf_ss = 39}) at ../../i386/i386/trap.c:891 #4 0xf01b4155 in Xsyscall () #5 0x1e7a in ?? () #6 0x1095 in ?? () (gdb) list 1869 if (pbits & PG_RW) { 1870 if (pbits & PG_M) { 1871 vm_offset_t sva = i386_ptob(sindex); 1872 if (pmap_track_modified(sva)) { 1873 vm_page_t m = PHYS_TO_VM_PAGE(pbits); 1874 m->dirty = VM_PAGE_BITS_ALL; 1875 } 1876 } 1877 ptbase[sindex] = pbits & ~(PG_M|PG_RW); 1878 anychanged = 1; Now how do I shutdown the system nicely? (as nicely as possible?) Jonas From owner-freebsd-current Wed Dec 11 19:43:48 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA06499 for current-outgoing; Wed, 11 Dec 1996 19:43:48 -0800 (PST) Received: from pat.idt.unit.no (0@pat.idt.unit.no [129.241.103.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA06475; Wed, 11 Dec 1996 19:43:36 -0800 (PST) Received: from idt.unit.no (tegge@ikke.idt.unit.no [129.241.111.65]) by pat.idt.unit.no (8.8.4/8.8.4) with ESMTP id EAA03905; Thu, 12 Dec 1996 04:43:26 +0100 (MET) Message-Id: <199612120343.EAA03905@pat.idt.unit.no> To: dyson@FreeBSD.ORG, dyson@dyson.iquest.net Cc: jgreco@solaria.sol.net, current@FreeBSD.ORG Subject: Re: mlocking an mmap'ped region? In-Reply-To: Your message of "Wed, 11 Dec 1996 12:27:45 -0500 (EST)" References: <199612111727.MAA03619@dyson.iquest.net> X-Mailer: Mew version 1.06 on Emacs 19.33.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 12 Dec 1996 04:43:25 +0100 From: Tor Egge Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > The following does not seem to work on a 2.2-CURRENT box (built yesterday). > > It does seem to work on SunOS. > > > > Is it just too early to be doing programming or is there really something > > preventing me from doing this? > > > Yep, it is called broken code :-(. That problem was just brought to my > attention yesterday. Unfortunately, someone also wants it fixed in 2.1.X :-(. This looks similar to PR kern/1514. There is also a fix in -current to avoid crashes after having used mlock() if the process exits without first unlocking the memory. (added in rev 1.129 of sys/i386/i386/pmap.c, and not present in the 2.2 branch) - Tor Egge From owner-freebsd-current Wed Dec 11 20:40:56 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA12939 for current-outgoing; Wed, 11 Dec 1996 20:40:56 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA12911; Wed, 11 Dec 1996 20:40:49 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id UAA13311; Wed, 11 Dec 1996 20:40:08 -0800 (PST) Message-Id: <199612120440.UAA13311@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Tor Egge cc: dyson@freebsd.org, jgreco@solaria.sol.net, current@freebsd.org Subject: Re: mlocking an mmap'ped region? In-reply-to: Your message of "Thu, 12 Dec 1996 04:43:25 +0100." <199612120343.EAA03905@pat.idt.unit.no> From: David Greenman Reply-To: dg@root.com Date: Wed, 11 Dec 1996 20:40:08 -0800 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> > The following does not seem to work on a 2.2-CURRENT box (built yesterday). >> > It does seem to work on SunOS. >> > >> > Is it just too early to be doing programming or is there really something >> > preventing me from doing this? >> > >> Yep, it is called broken code :-(. That problem was just brought to my >> attention yesterday. Unfortunately, someone also wants it fixed in 2.1.X :-(. >This looks similar to PR kern/1514. There is also a fix in -current >to avoid crashes after having used mlock() if the process exits without >first unlocking the memory. (added in rev 1.129 of sys/i386/i386/pmap.c, >and not present in the 2.2 branch) Uh, actually, it is in the 2.2 branch. See rev 1.128.2.1 of pmap.c -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Thu Dec 12 04:31:08 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA10188 for current-outgoing; Thu, 12 Dec 1996 04:31:08 -0800 (PST) Received: from mpress.com (qmailr@mpress.com [208.138.29.130]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA10123 for ; Thu, 12 Dec 1996 04:31:02 -0800 (PST) From: brian@mpress.com Received: (qmail 5695 invoked by uid 100); 12 Dec 1996 12:30:51 -0000 Message-ID: <19961212123051.5694.qmail@mpress.com> Subject: SKIP and -current To: freebsd-current@freebsd.org Date: Thu, 12 Dec 1996 04:30:50 -0800 (PST) Reply-to: brian@mpress.com X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I came accross skip (secure ip something or other) which looks pretty interesting, but is ported for 2.1.5 and 2.1.0. I hacked it into compiling under 2.2, with most of the effort going to skip_wrapper.c (the lkm stuff). Regretably, I don't know much about lkm, and while everything compiles and installs, when it tries to modload the module it reports something like /usr/bin/ld: unable to resolve _skip, or some such thing about not being able to find a reference to _skip. The module is called skipmod, with most of the references being skipmod_this or skipmod_that. Now there are two things I am wondering at this point: 1. Can anyone give me a pointer towards resolving this reference problem. I could make available the 2.1.5 and my 2.2 skip_wrapper.c and perhaps someone could point out my mistake. 2. Is there possibly some underlying differences between 2.1.5 and 2.2 which means this is really more work than it looks like? Thanks in advance. -- brian@mpress.com From owner-freebsd-current Thu Dec 12 05:33:43 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA12229 for current-outgoing; Thu, 12 Dec 1996 05:33:43 -0800 (PST) Received: from box.satech.net.au (root@box.satech.net.au [203.0.179.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA12221; Thu, 12 Dec 1996 05:33:15 -0800 (PST) Received: from matte.satech.net.au (matte.satech.net.au [203.1.91.219]) by box.satech.net.au (go-away/8.6.9) with ESMTP id AAA30712; Fri, 13 Dec 1996 00:03:37 +1030 Received: from matte.satech.net.au (localhost.satech.net.au [127.0.0.1]) by matte.satech.net.au (8.8.4/8.7.3) with SMTP id AAA00822; Fri, 13 Dec 1996 00:02:38 +1100 (EST) Message-ID: <32B0026C.15FB7483@satech.net.au> Date: Fri, 13 Dec 1996 00:02:36 +1100 From: Matthew Thyer X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Stefan Esser CC: FreeBSD CURRENT Subject: Re: Four problems that really bug me with CURRENT References: <3292F70B.41C67EA6@satech.net.au> <199611221253.NAA07064@x14.mi.uni-koeln.de> <3296F2FE.41C67EA6@satech.net.au> <199611231555.QAA18903@x14.mi.uni-koeln.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Sorry for the delay I've been very busy with a new baby and a new job. I have applied the patch but it makes no difference. The PCI bus is still only found on the second boot into FreeBSD after a hard reset (or power cycle) regardless of whether I boot into DOS 6.22 first (to activate my PnP sound card). My motherboard is a no name GA-586AP if that means anything to you. The motherboard manual is dated 1 Jan 1995 Stefan Esser wrote: > > On Nov 23, thyerm@satech.net.au (Matthew Thyer) wrote: > > My system is a Pentium 90 PCI with 16MB standard RAM, ExpertColor > > S3 Trio 64 (2 MB), Maxtor 71260 AT 1204MB 2448 cyl 10ms IDE HDD, > > PC-2000 NCR 53c810 PCI scsi controller, 2 x slow old IBM 0661371 > > 320MB disks from a RISC 6000, quad speed ATAPI CD-ROM, Creative > > Labs PnP SB16, NE2000 clone NIC, floppy disk. [snip] > Your system does not comply to the PCI spec. My only idea > now is, to have the configuration mode 1 hardcoded in your > kernel. Please apply the following patch: > > Index: /sys/i386/isa/pcibus.c > =================================================================== > RCS file: /usr/cvs/src/sys/i386/isa/pcibus.c,v > retrieving revision 1.27 > diff -C2 -r1.27 pcibus.c > *** pcibus.c 1996/10/30 22:38:55 1.27 > --- pcibus.c 1996/11/23 15:50:11 > *************** > *** 204,208 **** > pci_mechanism = 1; > pci_maxdevice = 32; > ! > outl (CONF1_ADDR_PORT, CONF1_ENABLE_CHK); > outb (CONF1_ADDR_PORT +3, 0); > --- 204,208 ---- > pci_mechanism = 1; > pci_maxdevice = 32; > ! return; > outl (CONF1_ADDR_PORT, CONF1_ENABLE_CHK); > outb (CONF1_ADDR_PORT +3, 0); > > But BEWARE: This removes support for PCI configuration mode 2 > chip sets, and may even fail on non-PCI systems. If this patch > is not sufficient to probe your PCI bus, then there might be > some chip set register, that needs to be set to a specific > value in order to enable PCI. Since I have no idea what this > value might be, I don't think I can help, then ... > > (Please let me know whether this patch works or not.) > > Complain to your vendor for delivering a non-PCI compliant > product ! > > Regards, STefan -- ======================================================================== @ Work: Matthew.Thyer@dsto.defence.gov.au @ Play: thyerm@satech.net.au ======================================================================== "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 From owner-freebsd-current Thu Dec 12 06:04:50 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA13495 for current-outgoing; Thu, 12 Dec 1996 06:04:50 -0800 (PST) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA13489 for ; Thu, 12 Dec 1996 06:04:45 -0800 (PST) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id OAA23529; Thu, 12 Dec 1996 14:05:26 GMT Date: Thu, 12 Dec 1996 14:05:26 +0000 (GMT) From: Developer To: Matthew Thyer cc: freebsd-current@freebsd.org Subject: Re: Problem PS command In-Reply-To: <32AFF445.41C67EA6@satech.net.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 Thu, 12 Dec 1996, Matthew Thyer wrote: > My ps command didn't work when I rebuilt my kernel ready to make > world. After I made world and rebooted it worked again. > > You haven't got your kernel sources more up to date than what the > system was last built with have you ? > > Recompile ps and see if it works. Ive already tried re-compiling it -- it doesn't hang all the time, just sometimes, it's weird. Thanks. Trefor S. > > There seems to be a problem with the ps command, which doesn't occur with > > top or the process filing system. Sometimes ps -ax just hangs up and has > > to be kill -9'ed.. The problem is when it's in scripts is really messes > > things up. > > > > Has anyone got any ideas why this might be? > > > > Please could you reply by email. > > > > Thanks in Advance. > > > > Trefor S. > > -- > ======================================================================== > @ Work: Matthew.Thyer@dsto.defence.gov.au @ Play: thyerm@satech.net.au > ======================================================================== > "If it is true that our Universe has a zero net value for all conserved > quantities, then it may simply be a fluctuation of the vacuum of some > larger space in which our Universe is imbedded. In answer to the > question of why it happened, I offer the modest proposal that our > Universe is simply one of those things which happen from time to time." > E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 > From owner-freebsd-current Thu Dec 12 09:55:50 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA25383 for current-outgoing; Thu, 12 Dec 1996 09:55:50 -0800 (PST) Received: from access.netaxs.com (mail@access.netaxs.com [207.8.186.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA25377 for ; Thu, 12 Dec 1996 09:55:42 -0800 (PST) Received: from unix2.netaxs.com (noyles@unix2.netaxs.com [207.8.186.4]) by access.netaxs.com (8.7.6/8.6.11) with SMTP id MAA26924 for ; Thu, 12 Dec 1996 12:55:04 -0500 (EST) Date: Thu, 12 Dec 1996 12:55:04 -0500 (EST) From: "Juan J. Noyles" cc: freebsd-current@freebsd.org Subject: Extended IDE Disk and CD In-Reply-To: <19961212123051.5694.qmail@mpress.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 Hello folks, I'm not exactly running FreeBSD yet. I spent some time reading the manual and found that the version I got just last weekend (2.1.5) is obsolete. That actually made me glad, because the book gave me the impression that I'd have some trouble installing it on my EIDE Disk and CDROM. I'm trying to find out if the current version or 3.x will allow me to use these devices. From owner-freebsd-current Thu Dec 12 11:56:28 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA01745 for current-outgoing; Thu, 12 Dec 1996 11:56:28 -0800 (PST) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA01735 for ; Thu, 12 Dec 1996 11:56:26 -0800 (PST) Received: from phaeton.Artisoft.COM by mail.crl.com with SMTP id AA06399 (5.65c/IDA-1.5 for ); Thu, 12 Dec 1996 11:56:46 -0800 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA07947; Thu, 12 Dec 1996 12:32:13 -0700 From: Terry Lambert Message-Id: <199612121932.MAA07947@phaeton.artisoft.com> Subject: Re: Extended IDE Disk and CD To: noyles@netaxs.com (Juan J. Noyles) Date: Thu, 12 Dec 1996 12:32:13 -0700 (MST) Cc: freebsd-current@freebsd.org In-Reply-To: from "Juan J. Noyles" at Dec 12, 96 12:55: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 > I'm not exactly running FreeBSD yet. I spent some time reading the manual > and found that the version I got just last weekend (2.1.5) is obsolete. > That actually made me glad, because the book gave me the impression that > I'd have some trouble installing it on my EIDE Disk and CDROM. > > I'm trying to find out if the current version or 3.x will allow me to use > these devices. The lower the version of FreeBSD, the more these deivces are required to adhere to the specification to work (most do not strictly adhere). The higher the version of FreeBSD, the more forgiving the driver is when the manufacturer goes off into the weeds. So, one question: 1) How far off into the weeds is your drive manufacturer? And one suggestion: 1) Make the floppy, boot it, and see what it says.... 2.1.5 is not as forgiving as more recent versions, but it will work with a lot of hardware. 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 Dec 12 14:30:35 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA12567 for current-outgoing; Thu, 12 Dec 1996 14:30:35 -0800 (PST) Received: from vector.jhs.no_domain (slip139-92-4-228.mu.de.ibm.net [139.92.4.228]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA12555; Thu, 12 Dec 1996 14:30:26 -0800 (PST) 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 PAA11753; Thu, 12 Dec 1996 15:08:08 +0100 (MET) Message-Id: <199612121408.PAA11753@vector.jhs.no_domain> To: Developer cc: freebsd-current@freebsd.org Subject: Re: Problem PS command From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" X-Organization: Vector Systems Ltd. X-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-ISDN: +49.89.26023276 X-Web: http://www.freebsd.org/~jhs/ In-reply-to: Your message of "Wed, 11 Dec 1996 15:38:22 GMT." Date: Thu, 12 Dec 1996 15:08:08 +0100 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Reference: > From: Developer > Subject: Re: Problem PS command > Date: Wed, 11 Dec 1996 15:38:22 +0000 (GMT) > Message-id: > > > There seems to be a problem with the ps command, which doesn't occur with > top or the process filing system. Sometimes ps -ax just hangs up and has > to be kill -9'ed.. The problem is when it's in scripts is really messes > things up. > > Has anyone got any ideas why this might be? Did you recompile world ? :-) ie make sure your kernel & ps & (from memory) libkvm all match ? Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Thu Dec 12 14:42:44 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA14157 for current-outgoing; Thu, 12 Dec 1996 14:42:44 -0800 (PST) Received: from pat.idt.unit.no (0@pat.idt.unit.no [129.241.103.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA14151 for ; Thu, 12 Dec 1996 14:42:41 -0800 (PST) Received: from idt.unit.no (tegge@ikke.idt.unit.no [129.241.111.65]) by pat.idt.unit.no (8.8.4/8.8.4) with ESMTP id XAA20650; Thu, 12 Dec 1996 23:42:10 +0100 (MET) Message-Id: <199612122242.XAA20650@pat.idt.unit.no> To: bde@zeta.org.au Cc: marcs@znep.com, roberto@keltia.freenix.fr, freebsd-current@freebsd.org Subject: Re: Patch for larger stats in vmstat -i In-Reply-To: Your message of "Mon, 25 Nov 1996 18:07:02 +1100" References: <199611250707.SAA21740@godzilla.zeta.org.au> X-Mailer: Mew version 1.06 on Emacs 19.33.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 12 Dec 1996 23:42:09 +0100 From: Tor Egge Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >If it is worthwhile to change, why not make it a few longer than that? > >Even with your patch, I can get: > > > >interrupt total rate > >clk0 irq0 295363845 99 > >rtc0 irq8 378098605 127 > >fdc0 irq6 1 0 > >wdc0 irq14 125614605 42 > >wdc1 irq15 148530817 50 > >sc0 irq1 1 0 > >sio1 irq3 20746 0 > >ed0 irq5 205705153 69 > >ep0 irq10 131130 0 > >Total 1153464903 390 > > Another billion and you'll get negative counts with a minus sign to screw > up the formatting some more. Counts should be 64-bit, but the kernel > doesn't support that yet. > > Bruce I fully agree: skarven:~$ vmstat -i interrupt total rate clk0 irq0 209765285 100 rtc0 irq8 268479013 127 pci irq11 97998111 46 pci irq9 681239849 324 fdc0 irq6 1 0 sc0 irq1 676 0 ms0 irq12 792860021 378 ms1 irq14 271147170 129 Total -1973477170 -940 - Tor Egge From owner-freebsd-current Thu Dec 12 15:27:03 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA17254 for current-outgoing; Thu, 12 Dec 1996 15:27:03 -0800 (PST) Received: from rs3.rrz.Uni-Koeln.DE (519@rs3.rrz.Uni-Koeln.DE [134.95.100.214]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA17238 for ; Thu, 12 Dec 1996 15:26:59 -0800 (PST) Received: by rs3.rrz.Uni-Koeln.DE id AA34941 (5.67b/IDA-1.5 for freebsd-current@freebsd.org); Fri, 13 Dec 1996 00:26:45 +0100 Date: Fri, 13 Dec 1996 00:26:45 +0100 (MET) From: Ralf Luettgen To: freebsd-current@freebsd.org Subject: How to calculate the tracks? (fwd) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ---------- Forwarded message ---------- Date: Thu, 12 Dec 1996 17:21:58 -0500 (EST) From: David C Niemi To: Ralf Luettgen Cc: Alain.Knaff@poboxes.com Subject: How to calculate the tracks? (fwd) Doesn't FreeBSD have support for DOS-style partition tables in its fdisk program? If so, you could define a DOS partition using fdisk and then use mkdosfs (if FreeBSD has this program, I don't remember). As for how to do it with mformat, I'd suggest you go ahead and experiment with it, unless you already have important data on a different partition on the Jaz disk. David Niemi@linux.wauug.org 703-810-5538 Reston, Virginia, USA ------ Money talks, but it is wrong half of the time. ----- ---------- Forwarded message ---------- Date: Thu, 12 Dec 1996 23:04:28 +0100 To: David.Niemi@mail.li.org Subject: How to calculate the tracks? Hi, I'm running FreeBSD with mtools 3.0. My question is, in which way I've to calculate the number of tracks by a mformat. The actual problem is to mformat a jaz disk. It has 1021 cyl, 64 heads and 32 sectors. Please could you say me, what will be the right value for the tracks option by mformat. I've make a partition on the disk wich starts at sector 32. Thank you for help by Ralf From owner-freebsd-current Thu Dec 12 16:14:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA24006 for current-outgoing; Thu, 12 Dec 1996 16:14:06 -0800 (PST) Received: from sed.cs.fsu.edu (sed.cs.fsu.edu [128.186.121.157]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA23986 for ; Thu, 12 Dec 1996 16:14:01 -0800 (PST) Received: by sed.cs.fsu.edu (8.8.3/56) id AAA25228; Fri, 13 Dec 1996 00:13:55 GMT From: Gang-Ryung Uh Message-Id: <199612130013.AAA25228@sed.cs.fsu.edu> Subject: ft To: current@freebsd.org Date: Thu, 12 Dec 1996 19:13:54 -0500 (EST) 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 Hi, Is "ft" working at current? Thanks. Regards, Gang-Ryung Uh From owner-freebsd-current Thu Dec 12 16:45:59 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA27162 for current-outgoing; Thu, 12 Dec 1996 16:45:59 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA27153 for ; Thu, 12 Dec 1996 16:45:54 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id BAA03531; Fri, 13 Dec 1996 01:45:37 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA16208; Fri, 13 Dec 1996 01:45:36 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id BAA14442; Fri, 13 Dec 1996 01:44:08 +0100 (MET) From: J Wunsch Message-Id: <199612130044.BAA14442@uriah.heep.sax.de> Subject: Re: ft To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Fri, 13 Dec 1996 01:44:08 +0100 (MET) Cc: uh@sed.cs.fsu.edu (Gang-Ryung Uh) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612130013.AAA25228@sed.cs.fsu.edu> from Gang-Ryung Uh at "Dec 12, 96 07:13:54 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 Gang-Ryung Uh wrote: > Is "ft" working at current? As poor as it always used to work. Only older drives are supported. -- 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 Thu Dec 12 16:58:26 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA27964 for current-outgoing; Thu, 12 Dec 1996 16:58:26 -0800 (PST) Received: (from jmb@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA27958; Thu, 12 Dec 1996 16:58:24 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199612130058.QAA27958@freefall.freebsd.org> Subject: Re: ft To: uh@sed.cs.fsu.edu (Gang-Ryung Uh) Date: Thu, 12 Dec 1996 16:58:24 -0800 (PST) Cc: current@FreeBSD.ORG In-Reply-To: <199612130013.AAA25228@sed.cs.fsu.edu> from "Gang-Ryung Uh" at Dec 12, 96 07:13:54 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Gang-Ryung Uh wrote: > > Hi, > > Is "ft" working at current? > Thanks. not really, use lft instead. (uuencoded lft mailed separately) jmb From owner-freebsd-current Thu Dec 12 17:20:39 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA29413 for current-outgoing; Thu, 12 Dec 1996 17:20:39 -0800 (PST) Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA29399 for ; Thu, 12 Dec 1996 17:20:33 -0800 (PST) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA29100; Fri, 13 Dec 96 02:23:05 +0100 Date: Fri, 13 Dec 96 02:23:05 +0100 Message-Id: <9612130123.AA29100@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: current@freebsd.org Subject: -current strangeness X-Mailer: Emacs Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is with a make world/system from today: $ /usr/bin/w w: /dev//jmz: No such file or directory $ who jmz ttyp1 Jan 1 01:00 :0.0 jmz Jan 1 01:00 (&-02ttyp3) Jean-Marc _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr ============================================================================= From owner-freebsd-current Thu Dec 12 18:41:52 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA05009 for current-outgoing; Thu, 12 Dec 1996 18:41:52 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA05004 for ; Thu, 12 Dec 1996 18:41:49 -0800 (PST) Received: by sovcom.kiae.su id AA12087 (5.65.kiae-1 ); Fri, 13 Dec 1996 05:21:58 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Fri, 13 Dec 96 05:21:58 +0300 Received: from localhost (nagual.ru [127.0.0.1]) by nagual.ru (8.8.4/8.8.4) with SMTP id FAA04697; Fri, 13 Dec 1996 05:21:34 +0300 (MSK) Date: Fri, 13 Dec 1996 05:21:34 +0300 (MSK) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7=2C_Andrey_Chernov?= To: FreeBSD-current , Garrett Wollman Subject: New routed drop core (sig 11) after remote rtquery 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 rebuild everything, of course. dt:/ ttyp1 1_# gdb /usr/obj/usr/src/sbin/routed/routed routed.core ... Core was generated by `routed'. Program terminated with signal 11, Segmentation fault. #0 0x3872 in input (from=0xefbfdd24, sifp=0x0, aifp=0x0, rip=0xefbfd8d4, cc=24) at /usr/src/sbin/routed/input.c:269 269 ap = find_auth(aifp); (gdb) bt #0 0x3872 in input (from=0xefbfdd24, sifp=0x0, aifp=0x0, rip=0xefbfd8d4, cc=24) at /usr/src/sbin/routed/input.c:269 #1 0x18 in ?? () #2 0x30fd in read_rip (sock=5, sifp=0x0) at /usr/src/sbin/routed/input.c:133 #3 0x570e in main (argc=0, argv=0xefbfde94) at /usr/src/sbin/routed/main.c:479 (gdb) quit -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Thu Dec 12 19:08:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA07281 for current-outgoing; Thu, 12 Dec 1996 19:08:55 -0800 (PST) Received: from veda.is (veda.is [193.4.230.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA07243 for ; Thu, 12 Dec 1996 19:08:30 -0800 (PST) Received: (from adam@localhost) by veda.is (8.8.4/8.8.2) id DAA11679 for freebsd-current@freebsd.org; Fri, 13 Dec 1996 03:07:30 GMT From: Adam David Message-Id: <199612130307.DAA11679@veda.is> Subject: setgid() semantics To: freebsd-current@freebsd.org Date: Fri, 13 Dec 1996 03:07:21 +0000 (GMT) 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 It is apparently no longer possible to use setgid() to switch between real and effective gids. Can someone please confirm this change to be intentional, or help identify the problem. (found by elm) Looks probable that this was among the recent Posix conformance changes. -- Adam David From owner-freebsd-current Thu Dec 12 19:53:46 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA11334 for current-outgoing; Thu, 12 Dec 1996 19:53:46 -0800 (PST) Received: from cathouse.vu.com (root@cathouse.vu.com [204.209.156.4]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA11316; Thu, 12 Dec 1996 19:53:41 -0800 (PST) Received: (from mike@localhost) by cathouse.vu.com (8.8.4/8.8.2) id UAA02506; Thu, 12 Dec 1996 20:55:16 -0700 (MST) Date: Thu, 12 Dec 1996 20:55:16 -0700 (MST) From: Mike Nemeth Message-Id: <199612130355.UAA02506@cathouse.vu.com> To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: want your input for a *BSD-device-driver-writing FAQ Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk as it appears that i'm not going to get any help from the *bsd "experts" in the local geographic area, i would like to solicit information on the writing of device drivers under *BSD for incorporation into a FAQ. if you have experience in writing/debugging device drivers under *BSD, particularly NetBSD 1.1, please forward any information you have found to be of use to driverfaq@cathouse.vu.com thank you! From owner-freebsd-current Thu Dec 12 22:14:27 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA22580 for current-outgoing; Thu, 12 Dec 1996 22:14:27 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA22571 for ; Thu, 12 Dec 1996 22:14:24 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id HAA13081 for ; Fri, 13 Dec 1996 07:16:05 +0100 (MET) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.3/8.6.9) id HAA04492 for freebsd-current@freefall.cdrom.com; Fri, 13 Dec 1996 07:29:05 +0100 (MET) Date: Fri, 13 Dec 1996 07:29:05 +0100 (MET) From: Christoph Kukulies Message-Id: <199612130629.HAA04492@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: wtmp Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm aware that some commands (last, w) were broken due to the wtmp changes recently but what is the way to handle this correctly on an updated machine? I deleted /var/log/wtmp and did a touch /var/log/wtmp. I still get # w 7:09AM up 48 days, 12:07, 3 users, load averages: 0.00, 0.00, 0.00 USER TTY FROM LOGIN@ IDLE WHAT &r­2ttyv2 - 01Jan70 4:07 - ttyp0 toots Thu09PM 4:07 - kuku p1 kuku-home 7:07AM - w # This is on a yesterday's -current machine. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Thu Dec 12 22:29:15 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA23584 for current-outgoing; Thu, 12 Dec 1996 22:29:15 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA23558; Thu, 12 Dec 1996 22:29:09 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.7.6/8.7.3) with SMTP id BAA08762; Fri, 13 Dec 1996 01:29:03 -0500 (EST) Date: Fri, 13 Dec 1996 01:29:03 -0500 (EST) From: John Fieber To: Mike Nemeth cc: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: want your input for a *BSD-device-driver-writing FAQ In-Reply-To: <199612130355.UAA02506@cathouse.vu.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, 12 Dec 1996, Mike Nemeth wrote: > local geographic area, i would like to solicit information on the writing of > device drivers under *BSD for incorporation into a FAQ. if you have experience If you have not already, be sure to look at http://www.freebsd.org/tutorials/ddwg/ddwg.html. That might be a good place to start. Information on writing a device driver is certainly more substantial than the FAQ was intended for. -john From owner-freebsd-current Thu Dec 12 23:00:50 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA25663 for current-outgoing; Thu, 12 Dec 1996 23:00:50 -0800 (PST) Received: from grackle.grondar.za (DU8JqcnXh+DfNzHk2Uv1ZzS2dFwpe254@grackle.grondar.za [196.7.18.131]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA25657 for ; Thu, 12 Dec 1996 23:00:39 -0800 (PST) Received: from grackle.grondar.za (XtTiv40jbychYmD8XgtXAxN27z1x6pzL@localhost [127.0.0.1]) by grackle.grondar.za (8.8.4/8.8.4) with ESMTP id IAA04156; Fri, 13 Dec 1996 08:59:27 +0200 (SAT) Message-Id: <199612130659.IAA04156@grackle.grondar.za> To: Christoph Kukulies cc: freebsd-current@freefall.freebsd.org Subject: Re: wtmp Date: Fri, 13 Dec 1996 08:59:21 +0200 From: Mark Murray Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Christoph Kukulies wrote: > > I'm aware that some commands (last, w) were broken due to the wtmp > changes recently but what is the way to handle this correctly on > an updated machine? > > I deleted /var/log/wtmp and did a touch /var/log/wtmp. I still get > > # w > 7:09AM up 48 days, 12:07, 3 users, load averages: 0.00, 0.00, 0.00 ^^^^^^^ Build a new kernel and reboot. > This is on a yesterday's -current machine. Not the kernel! M -- Mark Murray PGP key fingerprint = 80 36 6E 40 83 D6 8A 36 This .sig is umop ap!sdn. BC 06 EA 0E 7A F2 CE CE From owner-freebsd-current Thu Dec 12 23:17:15 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA26667 for current-outgoing; Thu, 12 Dec 1996 23:17:15 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA26660 for ; Thu, 12 Dec 1996 23:17:12 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id IAA13366; Fri, 13 Dec 1996 08:18:40 +0100 (MET) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.3/8.6.9) id IAA04654; Fri, 13 Dec 1996 08:31:41 +0100 (MET) From: Christoph Kukulies Message-Id: <199612130731.IAA04654@gilberto.physik.rwth-aachen.de> Subject: Re: wtmp In-Reply-To: <199612130659.IAA04156@grackle.grondar.za> from Mark Murray at "Dec 13, 96 08:59:21 am" To: mark@grondar.za (Mark Murray) Date: Fri, 13 Dec 1996 08:31:41 +0100 (MET) Cc: kuku@gilberto.physik.rwth-aachen.de, freebsd-current@freefall.freebsd.org Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Christoph Kukulies wrote: > > > > I'm aware that some commands (last, w) were broken due to the wtmp > > changes recently but what is the way to handle this correctly on > > an updated machine? > > > > I deleted /var/log/wtmp and did a touch /var/log/wtmp. I still get > > > > # w > > 7:09AM up 48 days, 12:07, 3 users, load averages: 0.00, 0.00, 0.00 > ^^^^^^^ > Build a new kernel and reboot. Ack. It was too early this morning that I sat at the computer. > > > This is on a yesterday's -current machine. > > Not the kernel! > > M > -- > Mark Murray PGP key fingerprint = 80 36 6E 40 83 D6 8A 36 > This .sig is umop ap!sdn. BC 06 EA 0E 7A F2 CE CE > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Fri Dec 13 02:14:08 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA06989 for current-outgoing; Fri, 13 Dec 1996 02:14:08 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA06984 for ; Fri, 13 Dec 1996 02:13:59 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id VAA28452; Fri, 13 Dec 1996 21:08:04 +1100 Date: Fri, 13 Dec 1996 21:08:04 +1100 From: Bruce Evans Message-Id: <199612131008.VAA28452@godzilla.zeta.org.au> To: adam@veda.is, freebsd-current@freebsd.org Subject: Re: setgid() semantics Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >It is apparently no longer possible to use setgid() to switch between real >and effective gids. Can someone please confirm this change to be intentional, >or help identify the problem. (found by elm) It was intentional to stop setuid() and setgid() switching ids as non-root. They never worked to switch ids as root. The switching version broke the BSD4.4Lite security model and programs that depended on it often didn't know enough about saved ids to be secure. >Looks probable that this was among the recent Posix conformance changes. This was a security change. Both behaviours are POSIX conformant. Gids can be switched securely using the following models: BSD4.4Lite: Use setegid() to switch between the real gid and the saved gid. (The saved gid is initially the effective gid.) Use setgid() to set all the ids to the same value. Do not use setrgid() or setregid(). These functions are just wrappers around setegid(). They never change the saved gid, and have other problems. FreeBSD-current: Use setregid() to switch gids as usual. Use setregid(uid, uid) or or setgid(uid) to set all the ids to the same value. You can also use the BSD4.4Lite model, but this is probably less portable. POSIX, as implemented in FreeBSD: If _POSIX_SAVED_IDS is not defined, you lose. If _POSIX_SAVED_IDS is defined: If the effective uid is root, you lose (you can switch to another id, but there is no way back). Otherwise, you can switch gids using setgid(). You can't drop the saved gid without execing. POSIX, with "appropriate privilege" meaning something different from being root: If _POSIX_SAVED_IDS is not defined: "appropriate privilege" can probably involve hidden state to allow switching between previously acceptable ids. It isn't clear how this state could be dropped. If _POSIX_SAVED_IDS defined: Same as if it is defined, except it is guaranteed that you can't drop the saved gid :-]. FreeBSD-previous: Use setregid() as in -current. Do not use the full BSD4.4Lite model as non-root, since setgid() does not drop the saved id. As non-root, you can also use setgid() to switch gids, but setregid() must be used to set all the gids to the same value. Bruce From owner-freebsd-current Fri Dec 13 03:41:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA10691 for current-outgoing; Fri, 13 Dec 1996 03:41:18 -0800 (PST) Received: from mail001.mediacity.com ([206.24.105.68]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id DAA10590 for ; Fri, 13 Dec 1996 03:39:55 -0800 (PST) From: brian@mediacity.com Received: (qmail-queue invoked from smtpd); 13 Dec 1996 11:39:13 -0000 Received: from home001.mediacity.com (HELO mediacity.com) (qmailr@206.24.105.66) by mail001.mediacity.com with SMTP; 13 Dec 1996 11:39:13 -0000 Received: (qmail-queue invoked by uid 100); 13 Dec 1996 11:38:40 -0000 Message-ID: <19961213113840.14700.qmail@mediacity.com> Subject: I have SKIP 1.00 working with -current To: freebsd-current@freebsd.org Date: Fri, 13 Dec 1996 03:38:40 -0800 (PST) Reply-To: brian@mediacity.com X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I managed to get SKIP 1.00 ported and working under -current. Pretty cool stuff. -- Brian Litzinger Powered by FreeBSD http[s]://www.mpress.com From owner-freebsd-current Fri Dec 13 03:46:05 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA10934 for current-outgoing; Fri, 13 Dec 1996 03:46:05 -0800 (PST) Received: from mail001.mediacity.com ([206.24.105.68]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id DAA10861 for ; Fri, 13 Dec 1996 03:44:40 -0800 (PST) From: brian@mediacity.com Received: (qmail-queue invoked from smtpd); 13 Dec 1996 11:43:59 -0000 Received: from home001.mediacity.com (HELO mediacity.com) (qmailr@206.24.105.66) by mail001.mediacity.com with SMTP; 13 Dec 1996 11:43:59 -0000 Received: (qmail-queue invoked by uid 100); 13 Dec 1996 11:43:25 -0000 Message-ID: <19961213114325.14716.qmail@mediacity.com> Subject: Ported to FreeBSD 2.2 and 3.0 To: freeskip@incog.com Date: Fri, 13 Dec 1996 03:43:25 -0800 (PST) Cc: freebsd-current@freebsd.org Reply-To: brian@mediacity.com X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've ported SKIP 1.00 to FreeBSD -current, which at the moment means it works with 3.0 and is likely to work with 2.2. I did the development under 3.0 (-current). Shall I make a set of patches available? Currently I just hacked the code to work with 3.0. Maybe I should put in '#if FreeBSD>=2.2' or some such thing around all my changes? Perhaps the -current people can tell me a good way to differentiate the version FreeBSD versions with the code. -- Brian Litzinger Powered by FreeBSD http[s]://www.mpress.com From owner-freebsd-current Fri Dec 13 04:09:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA11949 for current-outgoing; Fri, 13 Dec 1996 04:09:06 -0800 (PST) Received: from grackle.grondar.za (6aMDh1aJuW5NLbpcBDw5qLHjvrqrtvYe@grackle.grondar.za [196.7.18.131]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA11935 for ; Fri, 13 Dec 1996 04:08:55 -0800 (PST) Received: from grackle.grondar.za (OrFixLVRcxpbCjlhwtqvmEhwoYL2bSAC@localhost [127.0.0.1]) by grackle.grondar.za (8.8.4/8.8.4) with ESMTP id OAA05330; Fri, 13 Dec 1996 14:07:59 +0200 (SAT) Message-Id: <199612131207.OAA05330@grackle.grondar.za> To: brian@mediacity.com cc: freeskip@incog.com, freebsd-current@freebsd.org Subject: Re: Ported to FreeBSD 2.2 and 3.0 Date: Fri, 13 Dec 1996 14:07:58 +0200 From: Mark Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Perhaps the -current people can tell me a good way to differentiate > the version FreeBSD versions with the code. Look in /usr/share/examples/FreeBSD_version. M -- Mark Murray PGP key fingerprint = 80 36 6E 40 83 D6 8A 36 This .sig is umop ap!sdn. BC 06 EA 0E 7A F2 CE CE From owner-freebsd-current Fri Dec 13 04:20:15 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA12868 for current-outgoing; Fri, 13 Dec 1996 04:20:15 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA12845 for ; Fri, 13 Dec 1996 04:20:08 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id NAA03654; Fri, 13 Dec 1996 13:19:42 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA20925; Fri, 13 Dec 1996 10:25:10 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id JAA17212; Fri, 13 Dec 1996 09:58:54 +0100 (MET) From: J Wunsch Message-Id: <199612130858.JAA17212@uriah.heep.sax.de> Subject: Re: ft To: freebsd-current@freebsd.org (FreeBSD-current users) Date: Fri, 13 Dec 1996 09:58:54 +0100 (MET) Cc: jmb@freefall.freebsd.org (Jonathan M. Bresler) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612130058.QAA27958@freefall.freebsd.org> from "Jonathan M. Bresler" at "Dec 12, 96 04:58:24 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 Jonathan M. Bresler wrote: > > Is "ft" working at current? > > Thanks. > > not really, use lft instead. ``Not really'' is wrong, though. It works the same way it always worked. The weakest point is IMHO the driver itself, which is orphaned and seeks a maintainer. However, if `lft' works better in some respects than `ft(8)', why don't you commit it to the tree? I understand that we can't drop the old utility since both are incompatible, but nobody says we can't have two. -- 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 Dec 13 04:22:00 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA13018 for current-outgoing; Fri, 13 Dec 1996 04:22:00 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA13013 for ; Fri, 13 Dec 1996 04:21:47 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id NAA03401; Fri, 13 Dec 1996 13:18:44 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA21393; Fri, 13 Dec 1996 10:55:59 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id KAA17385; Fri, 13 Dec 1996 10:19:43 +0100 (MET) From: J Wunsch Message-Id: <199612130919.KAA17385@uriah.heep.sax.de> Subject: Re: setgid() semantics To: freebsd-current@freebsd.org (FreeBSD-current users) Date: Fri, 13 Dec 1996 10:19:43 +0100 (MET) Cc: adam@veda.is (Adam David) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612130307.DAA11679@veda.is> from Adam David at "Dec 13, 96 03:07:21 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 Adam David wrote: > It is apparently no longer possible to use setgid() to switch between real > and effective gids. Can someone please confirm this change to be intentional, > or help identify the problem. (found by elm) You should use setegid for this. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Fri Dec 13 04:26:26 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA13266 for current-outgoing; Fri, 13 Dec 1996 04:26:26 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA13209 for ; Fri, 13 Dec 1996 04:24:14 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id NAA03405; Fri, 13 Dec 1996 13:18:45 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA21417; Fri, 13 Dec 1996 10:59:48 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id KAA17406; Fri, 13 Dec 1996 10:20:26 +0100 (MET) From: J Wunsch Message-Id: <199612130920.KAA17406@uriah.heep.sax.de> Subject: Re: setgid() semantics To: freebsd-current@freebsd.org (FreeBSD-current users) Date: Fri, 13 Dec 1996 10:20:26 +0100 (MET) Cc: adam@veda.is (Adam David) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612130307.DAA11679@veda.is> from Adam David at "Dec 13, 96 03:07:21 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 Adam David wrote: > It is apparently no longer possible to use setgid() to switch between real > and effective gids. Can someone please confirm this change to be intentional, > or help identify the problem. (found by elm) ...and, you should not run your elm setgid anyway. :) -- 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 Dec 13 04:33:46 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA13633 for current-outgoing; Fri, 13 Dec 1996 04:33:46 -0800 (PST) Received: (from jmb@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA13627; Fri, 13 Dec 1996 04:33:32 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199612131233.EAA13627@freefall.freebsd.org> Subject: Re: ft To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 13 Dec 1996 04:33:32 -0800 (PST) Cc: freebsd-current@freebsd.org In-Reply-To: <199612130858.JAA17212@uriah.heep.sax.de> from "J Wunsch" at Dec 13, 96 09:58:54 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > > As Jonathan M. Bresler wrote: > > > > Is "ft" working at current? > > > Thanks. > > > > not really, use lft instead. > > ``Not really'' is wrong, though. It works the same way it always > worked. The weakest point is IMHO the driver itself, which is > orphaned and seeks a maintainer. > > However, if `lft' works better in some respects than `ft(8)', why > don't you commit it to the tree? I understand that we can't drop the > old utility since both are incompatible, but nobody says we can't have > two. no commit privs. (thought jordan does threaten from time to time) the present situaton allows me to bitch from the sidelines with having to get my clothes dirty on the field. jmb FreeBSD Postmaster and Commentator From owner-freebsd-current Fri Dec 13 04:42:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA14212 for current-outgoing; Fri, 13 Dec 1996 04:42:58 -0800 (PST) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA14206 for ; Fri, 13 Dec 1996 04:42:50 -0800 (PST) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.7.6/BSD4.4) id XAA29654 Fri, 13 Dec 1996 23:42:41 +1100 (EST) From: michael butler Message-Id: <199612131242.XAA29654@asstdc.scgt.oz.au> Subject: Re: I have SKIP 1.00 working with -current In-Reply-To: <19961213113840.14700.qmail@mediacity.com> from "brian@mediacity.com" at "Dec 13, 96 03:38:40 am" To: brian@mediacity.com Date: Fri, 13 Dec 1996 23:42:41 +1100 (EST) Cc: freebsd-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 brian@mediacity.com writes: > I managed to get SKIP 1.00 ported and working under -current. > Pretty cool stuff. Except, if I read correctly, that it presents a (not insignificant) problem if anyone tries to export it (knowingly or otherwise) from North America, michael From owner-freebsd-current Fri Dec 13 09:24:01 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA00365 for current-outgoing; Fri, 13 Dec 1996 09:24:01 -0800 (PST) Received: from innocence.interface-business.de (innocence.interface-business.de [193.101.57.202]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA00346 for ; Fri, 13 Dec 1996 09:23:48 -0800 (PST) Received: from ida.interface-business.de (ida.interface-business.de [193.101.57.203]) by innocence.interface-business.de (8.6.11/8.6.9) with SMTP id SAA00584 for ; Fri, 13 Dec 1996 18:21:05 +0100 Received: (from j@localhost) by ida.interface-business.de (8.8.2/8.7.3) id SAA00981 for freebsd-current@FreeBSD.org; Fri, 13 Dec 1996 18:25:04 +0100 (MET) From: J Wunsch Message-Id: <199612131725.SAA00981@ida.interface-business.de> Subject: Is CVS broken? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Fri, 13 Dec 1996 18:25:04 +0100 (MET) Reply-To: joerg_wunsch@interface-business.de (Joerg Wunsch) X-Phone: +49-351-31809-14 X-Fax: +49-351-3361187 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+ 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 diff --exclude CVS -u -r -I $Header:.* \$ -I $Id:.* \$ -I Revision [0-9.]* 19 ./usr.bin/compress/doc/revision.log /c/src/usr.bin/compress/doc/revision.log --- ./usr.bin/compress/doc/revision.log Fri May 27 14:30:59 1994 +++ /c/src/usr.bin/compress/doc/revision.log Tue Jun 13 00:01:33 1995 @@ -1,9 +1,9 @@ /* * $Header: /home/ncvs/src/usr.bin/compress/doc/revision.log,v 1.1.1.1 1994/05/ 27 12:30:59 rgrimes Exp $ * $Log: revision.log,v $ - * Revision 1.1.1.1 1994/05/27 12:30:59 rgrimes - * BSD 4.4 Lite Usr.bin Sources - * +# Revision 1.1.1.1 1994/05/27 12:30:59 rgrimes +# BSD 4.4 Lite Usr.bin Sources +# * Revision 4.0 85/07/30 12:50:00 joe * Removed ferror() calls in output routine on every output except first. * Prepared for release to the world. Note that the comment character has been changed from " *" to "#". I've observed a multitude of these changes when reviewing 2.2 candidate diffs. -- J"org Wunsch Unix support engineer joerg_wunsch@interface-business.de http://www.interface-business.de/~j From owner-freebsd-current Fri Dec 13 12:15:21 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA10002 for current-outgoing; Fri, 13 Dec 1996 12:15:21 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA09992 for ; Fri, 13 Dec 1996 12:15:13 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA15679; Fri, 13 Dec 1996 12:52:16 -0700 From: Terry Lambert Message-Id: <199612131952.MAA15679@phaeton.artisoft.com> Subject: Re: setgid() semantics To: bde@zeta.org.au (Bruce Evans) Date: Fri, 13 Dec 1996 12:52:16 -0700 (MST) Cc: adam@veda.is, freebsd-current@FreeBSD.ORG In-Reply-To: <199612131008.VAA28452@godzilla.zeta.org.au> from "Bruce Evans" at Dec 13, 96 09:08: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 > This was a security change. Both behaviours are POSIX conformant. > > Gids can be switched securely using the following models: > > BSD4.4Lite: > Use setegid() to switch between the real gid and the saved gid. > (The saved gid is initially the effective gid.) Use setgid() to set > all the ids to the same value. Do not use setrgid() or setregid(). > These functions are just wrappers around setegid(). They never change > the saved gid, and have other problems. > > FreeBSD-current: > Use setregid() to switch gids as usual. Use setregid(uid, uid) or > or setgid(uid) to set all the ids to the same value. You can also > use the BSD4.4Lite model, but this is probably less portable. And if you need to make the effective gid the real gid to violate security anyway (like running "enable" or "disable" on SCO to toggle logins on ports), use: system( "sh -c program"); To make the egid and gid match and be the priviledged value for "program". Ie: it doesn't make any *real* security fix. 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 Fri Dec 13 14:07:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA20807 for current-outgoing; Fri, 13 Dec 1996 14:07:30 -0800 (PST) Received: from suntan.tandem.com (suntan.tandem.com [192.216.221.8]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA20789 for ; Fri, 13 Dec 1996 14:07:27 -0800 (PST) Received: from papillon.lemis.de by suntan.tandem.com (8.6.12/suntan5.961027) id OAA27985; Fri, 13 Dec 1996 14:07:26 -0800 From: Greg Lehey Received: (grog@localhost) by papillon.lemis.de (8.8.4/8.6.12) id NAA00279; Thu, 12 Dec 1996 13:36:24 -0500 (EST) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Message-Id: <199612121836.NAA00279@papillon.lemis.de> Subject: Re: Problems with PLIP driver? In-Reply-To: <96Dec7.100955pst.177711@crevenia.parc.xerox.com> from Bill Fenner at "Dec 7, 96 10:09:50 am" To: fenner@parc.xerox.com (Bill Fenner) Date: Thu, 12 Dec 1996 13:36:23 -0500 (EST) Cc: FreeBSD-current@FreeBSD.ORG (FreeBSD current users) 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 Bill Fenner writes: > In message <199612061732.SAA02168@freebie.lemis.de> you write: >> 2. There's definitely a bug in the bpf code, causing 100% of all >> messages to be reported as invalid. I think I can find that one >> by myself. > > It's the fact that the header is supposed to be an int containing the > address family, not a short containing the ethertype. I posted this > fix a long time ago and apparently nobody ever thought it worthwhile. > I don't have the diff any more, but it's small. (And the web page's > mailing list search is broken so I can't try to find them there...) Thanks. Yes, I found that out. I have a nasty kludge that I put together because I was in a hurry. I sent it to Poul-Henning, but I intend to do something better. Greg From owner-freebsd-current Fri Dec 13 15:02:00 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA23913 for current-outgoing; Fri, 13 Dec 1996 15:02:00 -0800 (PST) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA23898 for ; Fri, 13 Dec 1996 15:01:55 -0800 (PST) Received: from pauling.salk.edu (pauling [198.202.70.108]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id PAA23065 for ; Fri, 13 Dec 1996 15:01:07 -0800 (PST) Date: Fri, 13 Dec 1996 15:00:19 -0800 (PST) From: Tom Bartol To: current@freebsd.org Subject: SMP? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Well, my new Dual 200MHz P6 machine has arrived and I'd just love to try out the FreeBSD SMP stuff. How should I proceed with installing FreeBSD on this monster? Where can I go to get the SMP version? Or is it way to soon to even attempt this? Thanks, Tom From owner-freebsd-current Fri Dec 13 16:46:49 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA28200 for current-outgoing; Fri, 13 Dec 1996 16:46:49 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA28193 for ; Fri, 13 Dec 1996 16:46:46 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA19387; Fri, 13 Dec 1996 17:23:54 -0700 From: Terry Lambert Message-Id: <199612140023.RAA19387@phaeton.artisoft.com> Subject: Re: SMP? To: bartol@salk.edu (Tom Bartol) Date: Fri, 13 Dec 1996 17:23:53 -0700 (MST) Cc: current@freebsd.org In-Reply-To: from "Tom Bartol" at Dec 13, 96 03:00: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 > Well, my new Dual 200MHz P6 machine has arrived and I'd just love to try > out the FreeBSD SMP stuff. How should I proceed with installing FreeBSD > on this monster? Where can I go to get the SMP version? Or is it way to > soon to even attempt this? http://www.freebsd.org/~fsmp http://www.freebsd.org/~fsmp/SMP http://www.freebsd.org/~fsmp/SMP/mptable/mptable.html 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 Fri Dec 13 21:00:27 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA06080 for current-outgoing; Fri, 13 Dec 1996 21:00:27 -0800 (PST) Received: from veda.is (adam@ubiq.veda.is [193.4.230.60]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA06075; Fri, 13 Dec 1996 21:00:23 -0800 (PST) Received: (from adam@localhost) by veda.is (8.8.4/8.7.3) id FAA02445; Sat, 14 Dec 1996 05:04:42 GMT From: Adam David Message-Id: <199612140504.FAA02445@veda.is> Subject: pidentd works now To: freebsd-ports@freebsd.org Date: Sat, 14 Dec 1996 05:04:37 +0000 (GMT) Cc: freebsd-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 pidentd is now working again in -current, in case anyone is still wondering about it. -- Adam David From owner-freebsd-current Sat Dec 14 01:30:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA18371 for current-outgoing; Sat, 14 Dec 1996 01:30:24 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA18324 for ; Sat, 14 Dec 1996 01:30:02 -0800 (PST) Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id BAA21611 for ; Sat, 14 Dec 1996 01:30:21 -0800 (PST) Received: (qmail 17292 invoked from network); 14 Dec 1996 08:11:05 -0000 Received: from unknown (HELO profane.iq.org) (203.4.184.215) by suburbia.net with SMTP; 14 Dec 1996 08:11:05 -0000 Received: (from root@localhost) by profane.iq.org (8.8.4/8.8.2) id LAA04569 for current@freebsd.org; Sat, 14 Dec 1996 11:45:51 +1100 (EST) Date: Sat, 14 Dec 1996 11:45:51 +1100 (EST) From: I call god Message-Id: <199612140045.LAA04569@profane.iq.org> To: current@freebsd.org Subject: 1001 steve commits Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Add delta 1.4 96.12.14.06.19.23 steve Edit src/bin/sh/mystring.c Add delta 1.5 96.12.14.06.19.24 steve Edit src/bin/sh/options.c Add delta 1.9 96.12.14.06.19.24 steve Edit src/bin/sh/options.h Add delta 1.5 96.12.14.06.19.25 steve Edit src/bin/sh/output.c Add delta 1.5 96.12.14.06.19.26 steve Edit src/bin/sh/output.h Add delta 1.4 96.12.14.06.19.26 steve Edit src/bin/sh/parser.c Add delta 1.17 96.12.14.06.19.27 steve and so on... why? From owner-freebsd-current Sat Dec 14 02:11:47 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA20686 for current-outgoing; Sat, 14 Dec 1996 02:11:47 -0800 (PST) Received: from rosie.scsn.net (scsn.net [206.25.246.12]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA20681 for ; Sat, 14 Dec 1996 02:11:44 -0800 (PST) Received: from rhiannon.scsn.net (cola33.scsn.net [206.25.247.33]) by rosie.scsn.net (post.office MTA v2.0 0813 ID# 0-13529) with ESMTP id AAA235 for ; Sat, 14 Dec 1996 05:09:16 -0500 Received: (from root@localhost) by rhiannon.scsn.net (8.8.4/8.6.12) id FAA04836 for current@FreeBSD.org; Sat, 14 Dec 1996 05:11:11 -0500 (EST) From: "Donald J. Maddox" Message-Id: <199612141011.FAA04836@rhiannon.scsn.net> Subject: Something broken in libm To: current@FreeBSD.org Date: Sat, 14 Dec 1996 05:11:10 -0500 (EST) Reply-To: dmaddox@scsn.net X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk There is definitely something broken in libm when HAVE_FPU is defined... More specifically, the problem seems to be in the __ieee754_pow() function defined in src/lib/msun/src/e_pow.c. I have not been able to nail down the exact problem, but if anyone else is interested -- You can duplicate the problem by: 1) make world with HAVE_FPU defined in /etc/make.conf 2) Build and install povray from the port. 3) cd /usr/local/lib/povray3/pov3demo/radios. 4) povray +L/usr/local/lib/povray3/include +Irad2.pov +Orad2.tga +V +X rad2.ini You will be rewarded with a core dump (FPE). Or you can build Mesa2.0 from the port, and try to execute the 'wave' demo in the 'samples' directory. You will get the same results. -- Donald J. Maddox (dmaddox@scsn.net) From owner-freebsd-current Sat Dec 14 02:26:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA21017 for current-outgoing; Sat, 14 Dec 1996 02:26:06 -0800 (PST) Received: from wiesbaden.netsurf.de (nero.wiesbaden.netsurf.de [194.163.168.140]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA21012; Sat, 14 Dec 1996 02:26:00 -0800 (PST) Received: from idefix by wiesbaden.netsurf.de with smtp (Smail3.1.28.1 #10) id m0vYsDS-001lyHC; Sat, 14 Dec 96 12:25 MET Message-ID: <32B28129.4D1C@wiesbaden.netsurf.de> Date: Sat, 14 Dec 1996 11:27:53 +0100 From: Marcus John Organization: LAMARC EDV-Schulung & Beratung GmbH X-Mailer: Mozilla 3.0 (WinNT; I) MIME-Version: 1.0 To: questions@FreeBSD.org CC: current@FreeBSD.org Subject: PPP over BISDN Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi all, is there an extension/patch to use PPP over raw(HDLC) connections set up with then BISDN 0.97 package ? Thanks marcus.john@wiesbaden.netsurf.de From owner-freebsd-current Sat Dec 14 03:26:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA22520 for current-outgoing; Sat, 14 Dec 1996 03:26:58 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id DAA22515 for ; Sat, 14 Dec 1996 03:26:54 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id WAA02738; Sat, 14 Dec 1996 22:25:06 +1100 Date: Sat, 14 Dec 1996 22:25:06 +1100 From: Bruce Evans Message-Id: <199612141125.WAA02738@godzilla.zeta.org.au> To: current@FreeBSD.org, dmaddox@scsn.net Subject: Re: Something broken in libm Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > There is definitely something broken in libm when HAVE_FPU is >defined... More specifically, the problem seems to be in the >__ieee754_pow() function defined in src/lib/msun/src/e_pow.c. I >have not been able to nail down the exact problem, but if anyone >else is interested -- Try this fix. __ieee754_pow() only uses two functions that change when HAVE_FPU is defined, __ieee754_sqrt() and scalbn(). __iee754_sqrt() is to simple to be be broken, but scalbn() left garbage on the FPU stack. --- diff -c2 s_scalbn.S~ s_scalbn.S *** s_scalbn.S~ Fri Aug 19 21:14:30 1994 --- s_scalbn.S Sat Dec 14 21:36:34 1996 *************** *** 42,44 **** --- 42,45 ---- fldl 4(%esp) fscale + fstp %st(1) ret --- It's surprising that this problem hasn't been noticed before. scalbn() is also used for log10() and remainders mod pi/2. Some packages ignore all floating point errors (see fpsetmask(3)). FPU stack overflow should not be ignored, but unfortunately there is no way to trap it without also trapping for invalid operands. When the stack overflows, pushing further operands onto it pushes NaNs instead of the operands, so nothing much can be computed. E.g., the following program termintes after 1 iteration instead of 1e6 iterations: main() { double d; /* Fill up FPU stack. */ asm("fldz"); asm("fldz"); asm("fldz"); asm("fldz"); asm("fldz"); asm("fldz"); asm("fldz"); asm("fldz"); for (d = 0; d < 1e6; ) ++d; } Bruce From owner-freebsd-current Sat Dec 14 08:05:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA10812 for current-outgoing; Sat, 14 Dec 1996 08:05:55 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA10794 for ; Sat, 14 Dec 1996 08:05:52 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.7.6/8.7.3) with SMTP id LAA14886; Sat, 14 Dec 1996 11:05:43 -0500 (EST) Date: Sat, 14 Dec 1996 11:05:42 -0500 (EST) From: John Fieber Reply-To: John Fieber To: Bruce Evans cc: current@FreeBSD.org, dmaddox@scsn.net Subject: Re: Something broken in libm In-Reply-To: <199612141125.WAA02738@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 Sat, 14 Dec 1996, Bruce Evans wrote: > Try this fix. __ieee754_pow() only uses two functions that change > when HAVE_FPU is defined, __ieee754_sqrt() and scalbn(). > __iee754_sqrt() is to simple to be be broken, but scalbn() left > garbage on the FPU stack. ... > It's surprising that this problem hasn't been noticed before. Hm... According to my mail archives, I started a discussion about povray crashing when linked with msun near the end of May 1994. At that time, no answer was found. I'll try this patch now. :) -john From owner-freebsd-current Sat Dec 14 08:15:23 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA11774 for current-outgoing; Sat, 14 Dec 1996 08:15:23 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA11764 for ; Sat, 14 Dec 1996 08:15:20 -0800 (PST) Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id IAA26923 for ; Sat, 14 Dec 1996 08:15:37 -0800 (PST) Received: (qmail 1763 invoked from network); 14 Dec 1996 16:14:33 -0000 Received: from profane.iq.org (203.4.184.222) by suburbia.net with SMTP; 14 Dec 1996 16:14:33 -0000 Received: (from root@localhost) by profane.iq.org (8.8.4/8.8.2) id TAA08317 for current@freebsd.org; Sat, 14 Dec 1996 19:48:40 +1100 (EST) Date: Sat, 14 Dec 1996 19:48:40 +1100 (EST) From: I call god Message-Id: <199612140848.TAA08317@profane.iq.org> To: current@freebsd.org Subject: in_ifaddr' undeclared (first use this function) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk root@profane:/sys/compile/SUB# make cc -c -O -pipe -m486 -pipe -malign-functions=2 -malign-loops=2 -malign-jumps=2 -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdinc -I- -I. -I../.. -I../../../include -DSPX_HACK -DEXT2FS -DPSM_NO_RESET -DFDSEEKWAIT=16 -DSC_KBD_PROBE_WORKS -DTUNE_1542 -DSAFETY -DNSWAPDEV=20 -DDEVFS -DMFS -DCD9660 -DNFS -DFFS -DIPDIVERT -DINET -DCOMPAT_43 -DI586_OPTIMIZED_BZERO -DI586_OPTIMIZED_BCOPY -DI586_FAST_BCOPY -DFAILSAFE -DKERNEL ../../netinet/if_ether.c ../../netinet/if_ether.c: In function `in_arpinput': ../../netinet/if_ether.c:453: `in_ifaddr' undeclared (first use this function) ../../netinet/if_ether.c:453: (Each undeclared identifier is reported only once ../../netinet/if_ether.c:453: for each function it appears in.) Looking at the code, this looks like a semantic typo. in_ifaddr is the struct, but it is being used as a variable name -Julian A. From owner-freebsd-current Sat Dec 14 09:57:35 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA21139 for current-outgoing; Sat, 14 Dec 1996 09:57:35 -0800 (PST) Received: from mule1.mindspring.com (mule1.mindspring.com [204.180.128.167]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA21133 for ; Sat, 14 Dec 1996 09:57:33 -0800 (PST) Received: from rlb.users.mindspring.com (user-168-121-25-139.dialup.mindspring.com [168.121.25.139]) by mule1.mindspring.com (8.8.2/8.7.3) with SMTP id RAA78372 for ; Sat, 14 Dec 1996 17:57:29 GMT Message-ID: <32B2EA88.15FB7483@mindspring.com> Date: Sat, 14 Dec 1996 12:57:28 -0500 From: Ron Bolin X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: 12-14-96 kernel compile tbl? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I tried to build today's current 12-14 via cvsup and ran across the problem below: cc -c -pipe -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-exter ns -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdinc -I- -I. -I../.. -I../../../include -DFAILSAFE -DCOMPAT_43 -DCD9660 -DNFS -DFFS -DINET -D KERNEL ../../netinet/if_ether.c ../../netinet/if_ether.c: In function `in_arpinput': ../../netinet/if_ether.c:453: `in_ifaddr' undeclared (first use this function) ../../netinet/if_ether.c:453: (Each undeclared identifier is reported only once ../../netinet/if_ether.c:453: for each function it appears in.) *** Error code 1 Stop. I installed the new includes first b4 this occured. What is the fix to reference in_ifaddr? I noticed that /usr/src/sys/netinet/in_var.h defines in_ifaddr, but is not in the include path for some reason. Thank's in advance. Ron -- **************************************************************************** Ron Bolin rlb@mindspring.com, http://www.mindspring.com/~rlb/ GSU: gs01rlb@panther.gsu.edu matrlbx@indigo4.cs.gsu.edu Home: 770-992-8877 **************************************************************************** From owner-freebsd-current Sat Dec 14 10:32:08 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA25306 for current-outgoing; Sat, 14 Dec 1996 10:32:08 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA25279 for ; Sat, 14 Dec 1996 10:32:01 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id NAA00193; Sat, 14 Dec 1996 13:31:54 -0500 (EST) From: "John S. Dyson" Message-Id: <199612141831.NAA00193@dyson.iquest.net> Subject: Re: 12-14-96 kernel compile tbl? To: rlb@mindspring.com (Ron Bolin) Date: Sat, 14 Dec 1996 13:31:54 -0500 (EST) Cc: freebsd-current@freebsd.org In-Reply-To: <32B2EA88.15FB7483@mindspring.com> from "Ron Bolin" at Dec 14, 96 12:57:28 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 > I tried to build today's current 12-14 via cvsup and ran across the > problem below: > > cc -c -pipe -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit > -Wnested-exter > ns -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdinc > -I- -I. > -I../.. -I../../../include -DFAILSAFE -DCOMPAT_43 -DCD9660 -DNFS -DFFS > -DINET -D > KERNEL ../../netinet/if_ether.c > ../../netinet/if_ether.c: In function `in_arpinput': > ../../netinet/if_ether.c:453: `in_ifaddr' undeclared (first use this > function) > ../../netinet/if_ether.c:453: (Each undeclared identifier is reported > only once > ../../netinet/if_ether.c:453: for each function it appears in.) > *** Error code 1 > I just committed a fix for it a few minutes ago!!! Thanks... John dyson@freebsd.org From owner-freebsd-current Sat Dec 14 11:49:26 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA03798 for current-outgoing; Sat, 14 Dec 1996 11:49:26 -0800 (PST) Received: from tau-ceti.isc-br.com (root@tau-ceti.isc-br.com [129.189.2.133]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA03792 for ; Sat, 14 Dec 1996 11:49:22 -0800 (PST) Received: by tau-ceti.isc-br.com (Smail3.1.28.1 #13) id m0vZ00M-0008pHC; Sat, 14 Dec 96 11:44 PST Received: (from kew@localhost) by phobos.walker.org (8.8.4/8.7.3) id LAA00878; Sat, 14 Dec 1996 11:24:49 -0800 (PST) Date: Sat, 14 Dec 1996 11:24:49 -0800 (PST) Message-Id: <199612141924.LAA00878@phobos.walker.org> From: Keith Walker To: Ron Bolin Cc: freebsd-current@freebsd.org Subject: 12-14-96 kernel compile tbl? In-Reply-To: <32B2EA88.15FB7483@mindspring.com> References: <32B2EA88.15FB7483@mindspring.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ron Bolin writes: > I tried to build today's current 12-14 via cvsup and ran across the > problem below: > > ../../netinet/if_ether.c:453: `in_ifaddr' undeclared (first use this > function) I fixed it - until the official fix comes out - with this: change line 453 of if_ether.c to: for (ia = in_ifaddrhead.tqh_first; ia; ia = ia->ia_link.tqe_next) There are examples of this in other files, and it seems that the fix works, although mine is a *quite* simple system and doesn't do very much with ethernet. I figured this out by noticing that the declaration of in_ifaddr was changed in 'in_var.h' from the old extern struct in_ifaddr *in_ifaddr; to extern TAILQ_HEAD(in_ifaddrhead, in_ifaddr) in_ifaddrhead; Hope this helps. From owner-freebsd-current Sat Dec 14 12:31:09 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA08721 for current-outgoing; Sat, 14 Dec 1996 12:31:09 -0800 (PST) Received: from irz401.inf.tu-dresden.de (irz401.inf.tu-dresden.de [141.76.1.12]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA08697 for ; Sat, 14 Dec 1996 12:31:01 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz401.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA13721 for ; Sat, 14 Dec 1996 21:30:56 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA10792 for freebsd-current@FreeBSD.org; Sat, 14 Dec 1996 21:30:56 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id VAA29404 for freebsd-current@FreeBSD.org; Sat, 14 Dec 1996 21:25:20 +0100 (MET) From: J Wunsch Message-Id: <199612142025.VAA29404@uriah.heep.sax.de> Subject: Huh?!? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 14 Dec 1996 21:25:19 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) 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 That's me on thud: joerg@thud 58% w 9:24PM up 5 days, 9:20, 1 user, load averages: 1.07, 0.82, 0.43 USER TTY FROM LOGIN@ IDLE WHAT joerg p0 EL-SEGUNDO.MT.DD 12May61 - w ^^^^^^^^^^^^^^^^ ^^^^^^^ I'm logged in from uriah.heep.sax.de (via ssh), and i didn't even exist already in May, 1961. :-)) -- 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 Sat Dec 14 12:47:26 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA10769 for current-outgoing; Sat, 14 Dec 1996 12:47:26 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA10759 for ; Sat, 14 Dec 1996 12:47:21 -0800 (PST) Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id MAA00381 for ; Sat, 14 Dec 1996 12:47:56 -0800 (PST) Received: (qmail 1008 invoked from network); 14 Dec 1996 20:47:04 -0000 Received: from profane.iq.org (203.4.184.222) by suburbia.net with SMTP; 14 Dec 1996 20:47:04 -0000 Received: (from root@localhost) by profane.iq.org (8.8.4/8.8.2) id AAA14515 for current@freebsd.org; Sun, 15 Dec 1996 00:21:15 +1100 (EST) Date: Sun, 15 Dec 1996 00:21:15 +1100 (EST) From: I call god Message-Id: <199612141321.AAA14515@profane.iq.org> To: current@freebsd.org Subject: num_eisa_slots Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk loading kernel userconfig.o: Undefined symbol `_num_eisa_slots' referenced from text segment userconfig.o: Undefined symbol `_num_eisa_slots' referenced from text segment userconfig.o: Undefined symbol `_num_eisa_slots' referenced from text segment *** Error code 1 From owner-freebsd-current Sat Dec 14 13:53:05 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA17403 for current-outgoing; Sat, 14 Dec 1996 13:53:05 -0800 (PST) Received: from irz401.inf.tu-dresden.de (irz401.inf.tu-dresden.de [141.76.1.12]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA17379 for ; Sat, 14 Dec 1996 13:52:56 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz401.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA15062; Sat, 14 Dec 1996 22:52:16 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA11834; Sat, 14 Dec 1996 22:50:59 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id WAA29699; Sat, 14 Dec 1996 22:43:46 +0100 (MET) From: J Wunsch Message-Id: <199612142143.WAA29699@uriah.heep.sax.de> Subject: Re: num_eisa_slots To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 14 Dec 1996 22:43:45 +0100 (MET) Cc: profroot@iq.org (I call god) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612141321.AAA14515@profane.iq.org> from I call god at "Dec 15, 96 00:21:15 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 I call god wrote: > loading kernel > userconfig.o: Undefined symbol `_num_eisa_slots' referenced from text segment > userconfig.o: Undefined symbol `_num_eisa_slots' referenced from text segment > userconfig.o: Undefined symbol `_num_eisa_slots' referenced from text segment > *** Error code 1 Hmpf. I should have tested not so GENERIC kernels as well, probably. <:-) ^____ the conical hat As a stop-gap measure, please add controller eisa0 to your config file temporarily. This will include eisaconf.c. A better fix is on the way... -- 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 Sat Dec 14 14:05:15 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA18727 for current-outgoing; Sat, 14 Dec 1996 14:05:15 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA18719 for ; Sat, 14 Dec 1996 14:05:11 -0800 (PST) Received: from irz401.inf.tu-dresden.de (irz401.inf.tu-dresden.de [141.76.1.12]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id OAA22881 for ; Sat, 14 Dec 1996 14:05:09 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz401.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA15095; Sat, 14 Dec 1996 23:03:46 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA12049; Sat, 14 Dec 1996 23:03:46 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id XAA29926; Sat, 14 Dec 1996 23:01:00 +0100 (MET) From: J Wunsch Message-Id: <199612142201.XAA29926@uriah.heep.sax.de> Subject: Re: num_eisa_slots To: profroot@iq.org (I call god) Date: Sat, 14 Dec 1996 23:00:59 +0100 (MET) Cc: current@freebsd.org In-Reply-To: <199612141321.AAA14515@profane.iq.org> from I call god at "Dec 15, 96 00:21:15 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 I call god wrote: > loading kernel > userconfig.o: Undefined symbol `_num_eisa_slots' referenced from text segment > userconfig.o: Undefined symbol `_num_eisa_slots' referenced from text segment > userconfig.o: Undefined symbol `_num_eisa_slots' referenced from text segment > *** Error code 1 Here's my official fix, give it a try please. cvs diff: Diffing . Index: userconfig.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/userconfig.c,v retrieving revision 1.72 diff -u -r1.72 userconfig.c --- userconfig.c 1996/12/14 18:07:17 1.72 +++ userconfig.c 1996/12/14 22:00:22 @@ -2272,7 +2272,6 @@ static int set_device_flags(CmdParm *); static int set_device_enable(CmdParm *); static int set_device_disable(CmdParm *); -static int set_num_eisa_slots(CmdParm *); static int quitfunc(CmdParm *); static int helpfunc(CmdParm *); #if defined(USERCONFIG_BOOT) @@ -2282,7 +2281,11 @@ static int lineno; /* XXX hack */ +#incldue "eisa.h" +#if NEISA > 0 extern int num_eisa_slots; +static int set_num_eisa_slots(CmdParm *); +#endif /* NEISA > 0 */ static CmdParm addr_parms[] = { { PARM_DEVSPEC, {} }, @@ -2301,16 +2304,20 @@ { -1, {} }, }; +#if NEISA > 0 static CmdParm int_arg[] = { { PARM_INT, {} }, { -1, {} }, }; +#endif /* NEISA > 0 */ static Cmd CmdList[] = { { "?", helpfunc, NULL }, /* ? (help) */ { "di", set_device_disable, dev_parms }, /* disable dev */ { "dr", set_device_drq, int_parms }, /* drq dev # */ +#if NEISA > 0 { "ei", set_num_eisa_slots, int_arg }, /* # EISA slots */ +#endif /* NEISA > 0 */ { "en", set_device_enable, dev_parms }, /* enable dev */ { "ex", quitfunc, NULL }, /* exit (quit) */ { "f", set_device_flags, int_parms }, /* flags dev mask */ @@ -2461,7 +2468,9 @@ if (lsdevtab(&isa_devtab_tty[0])) return 0; if (lsdevtab(&isa_devtab_net[0])) return 0; if (lsdevtab(&isa_devtab_null[0])) return 0; +#if NEISA > 0 printf("\nNumber of EISA slots to probe: %d\n", num_eisa_slots); +#endif /* NEISA > 0 */ return 0; } @@ -2547,6 +2556,7 @@ return 0; } +#if NEISA > 0 static int set_num_eisa_slots(CmdParm *parms) { @@ -2556,6 +2566,7 @@ num_eisa_slots = (num_slots <= 16 ? num_slots : 10); return 0; } +#endif /* NEISA > 0 */ static int quitfunc(CmdParm *parms) @@ -2577,7 +2588,9 @@ printf("flags \tSet device flags\n"); printf("enable \tEnable device\n"); printf("disable \tDisable device (will not be probed)\n"); +#if NEISA > 0 printf("eisa \t\tSet the number of EISA slots to probe\n"); +#endif /* NEISA > 0 */ printf("quit\t\t\tExit this configuration utility\n"); printf("reset\t\t\tReset CPU\n"); #ifdef VISUAL_USERCONFIG -- 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 Sat Dec 14 14:20:12 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA20589 for current-outgoing; Sat, 14 Dec 1996 14:20:12 -0800 (PST) Received: from spooky.eis.net.au (root@spooky.eis.net.au [203.12.171.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA20567 for ; Sat, 14 Dec 1996 14:20:03 -0800 (PST) Received: (from ernie@localhost) by spooky.eis.net.au (8.8.4/8.6.12) id IAA10425 for current@freebsd.org; Sun, 15 Dec 1996 08:19:49 +1000 (EST) From: Ernie Elu Message-Id: <199612142219.IAA10425@spooky.eis.net.au> Subject: SUP of current weird To: current@freebsd.org Date: Sun, 15 Dec 1996 08:19:47 +1000 (EST) 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 I noticed over the last few days that there have been a few minor bugs that stop a make world in -current so I simply run sup again to get the latest fixed the next day. However every time I run sup it seems to want to retreive most of the contrib directory again which is wastefull. Has there been major patches every day of the last week to the contrib dir that forces sup to download it again? Or is there something odd going on? It only seems to be the contrib dir the other just update changed files as normal. Any suggestions? Here is the line from my supfile. src-contrib release=current host=sup.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix - Ernie. From owner-freebsd-current Sat Dec 14 14:55:38 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA24982 for current-outgoing; Sat, 14 Dec 1996 14:55:38 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA24968 for ; Sat, 14 Dec 1996 14:55:34 -0800 (PST) Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id OAA01969 for ; Sat, 14 Dec 1996 14:56:10 -0800 (PST) Received: (qmail 7040 invoked from network); 14 Dec 1996 22:55:21 -0000 Received: from profane.iq.org (203.4.184.222) by suburbia.net with SMTP; 14 Dec 1996 22:55:21 -0000 Received: (from root@localhost) by profane.iq.org (8.8.4/8.8.2) id CAA28641 for current@freebsd.org; Sun, 15 Dec 1996 02:29:33 +1100 (EST) Date: Sun, 15 Dec 1996 02:29:33 +1100 (EST) From: I call god Message-Id: <199612141529.CAA28641@profane.iq.org> To: current@freebsd.org Subject: eisa typo Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk /* XXX hack */ #incldue "eisa.h" #if NEISA > 0 try again ;) From owner-freebsd-current Sat Dec 14 16:46:57 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA06772 for current-outgoing; Sat, 14 Dec 1996 16:46:57 -0800 (PST) Received: from profane.iq.org (profane.iq.org [203.4.184.217]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA06761 for ; Sat, 14 Dec 1996 16:46:52 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id EAA07329 for current@freebsd.org; Sun, 15 Dec 1996 04:20:06 +1100 (EST) Date: Sun, 15 Dec 1996 04:20:06 +1100 (EST) From: Julian Assange Message-Id: <199612141720.EAA07329@profane.iq.org> To: current@freebsd.org Subject: arp responses just died Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 04:17:09.442963 arp who-has 203.4.184.222 tell 203.4.184.1 04:17:10.453095 arp who-has 203.4.184.222 tell 203.4.184.1 04:17:11.614342 arp who-has 203.4.184.222 tell 203.4.184.1 proff@profane:/usr/local/home/proff$ ifconfig -au ed0: flags=8943 mtu 1500 inet 203.4.184.222 netmask 0xffffff00 broadcast 203.4.184.255 ether 00:00:c0:1d:7d:30 $ arp profane profane.iq.org (203.4.184.222) at 0:0:c0:1d:7d:30 permanent published (doesn't work dynamically either) Cheers, Julian From owner-freebsd-current Sat Dec 14 17:01:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA08366 for current-outgoing; Sat, 14 Dec 1996 17:01:41 -0800 (PST) Received: from profane.iq.org (profane.iq.org [203.4.184.217]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA08356 for ; Sat, 14 Dec 1996 17:01:28 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id EAA12242 for current@freebsd.org; Sun, 15 Dec 1996 04:35:05 +1100 (EST) Date: Sun, 15 Dec 1996 04:35:05 +1100 (EST) From: Julian Assange Message-Id: <199612141735.EAA12242@profane.iq.org> To: current@freebsd.org Subject: "/usr/src/share/man/man5/Makefile" error Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "/local2/usr/src/share/man/man5/Makefile", line 8: Unassociated shell command "fdesc.5 forward.5 fstab.5 group.5 hosts.5 link.5 kernfs.5 networks.5 passwd.5 pbm.5 phones.5 printcap.5 procfs.5 protocols.5 remote.5 resolver.5 services.5 shells.5 stab.5 sysconfig.5 types.5 utmp.5 hosts.equiv.5 hosts.lpd.5" Fatal errors encountered -- cannot continue line 8 is missing a trailing \ (line 7 rather) From owner-freebsd-current Sat Dec 14 20:32:05 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA20567 for current-outgoing; Sat, 14 Dec 1996 20:32:05 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA20558 for ; Sat, 14 Dec 1996 20:32:00 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id XAA07652 for current@freebsd.org; Sat, 14 Dec 1996 23:31:59 -0500 (EST) From: "John S. Dyson" Message-Id: <199612150431.XAA07652@dyson.iquest.net> Subject: Warning -- Lite/2 merge coming up To: current@freebsd.org Date: Sat, 14 Dec 1996 23:31:58 -0500 (EST) 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 Fair warning: I am about 2/3's way through a merge of Lite/2 with -current (Jeffery Hsu et. al. work.) By about Tue or Wed, I'll be committing the changes. It would be a good idea to assume that the system will be marginally stable until next weekend. John From owner-freebsd-current Sat Dec 14 21:32:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA23061 for current-outgoing; Sat, 14 Dec 1996 21:32:31 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA23045 for ; Sat, 14 Dec 1996 21:32:27 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id GAA28643 for ; Sun, 15 Dec 1996 06:32:20 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id GAA01093 for freebsd-current@freebsd.org; Sun, 15 Dec 1996 06:32:06 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.4/keltia-uucp-2.9) id BAA28343; Sun, 15 Dec 1996 01:33:58 +0100 (CET) Message-ID: Date: Sun, 15 Dec 1996 01:33:57 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@freebsd.org (FreeBSD-current users) Subject: Re: Huh?!? References: <199612142025.VAA29404@uriah.heep.sax.de> X-Mailer: Mutt 0.53 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2768 In-Reply-To: <199612142025.VAA29404@uriah.heep.sax.de>; from J Wunsch on Dec 14, 1996 21:25:19 +0100 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to J Wunsch: > joerg p0 EL-SEGUNDO.MT.DD 12May61 - w > ^^^^^^^^^^^^^^^^ ^^^^^^^ > > I'm logged in from uriah.heep.sax.de (via ssh), and i didn't even > exist already in May, 1961. :-)) Neither did I :-) I noticed the same problem and sent a mail to root@thud about it. Thud is post-utmp changes but even with a "converted" wtmp (look in /var/log) and a Dec. 8th make world it still show this. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #31: Tue Dec 3 23:52:58 CET 1996