From owner-freebsd-current Sun Oct 13 07:22:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA14609 for current-outgoing; Sun, 13 Oct 1996 07:22:27 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA14602 for ; Sun, 13 Oct 1996 07:22:23 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id QAA00382 for ; Sun, 13 Oct 1996 16:21:55 +0200 (MET DST) To: current@freebsd.org Subject: make -j# Reply-to: phk@freebsd.org Date: Sun, 13 Oct 1996 16:21:53 +0200 Message-ID: <380.845216513@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Now that we have the possibility, I guess I should mention that most compiles go a couple of percent faster if you use the parallel feature of make(1). Try using: make -j3 for your kernel makes. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Sun Oct 13 07:46:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA17470 for current-outgoing; Sun, 13 Oct 1996 07:46:34 -0700 (PDT) Received: from sequent.kiae.su (sequent.kiae.su [193.125.152.6]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA17461 for ; Sun, 13 Oct 1996 07:46:29 -0700 (PDT) Received: by sequent.kiae.su id AA02754 (5.65.kiae-2 for current@freebsd.org); Sun, 13 Oct 1996 18:45:43 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Sun, 13 Oct 96 18:45:43 +0400 Received: (from ache@localhost) by nagual.ru (8.7.6/8.7.3) id SAA00830 for current@freebsd.org; Sun, 13 Oct 1996 18:33:50 +0400 (MSD) Message-Id: <199610131433.SAA00830@nagual.ru> Subject: Please fix CVSup collection To: current@freebsd.org (FreeBSD-current) Date: Sun, 13 Oct 1996 18:33:49 +0400 (MSD) From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL28 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >From todays CVSup log: ... Add delta 1.39 96.10.10.23.16.50 jdp Checkout src/lib/libmd/.depend ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ please remove this file Edit src/sbin/init/init.8 ... -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Sun Oct 13 08:34:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA21167 for current-outgoing; Sun, 13 Oct 1996 08:34:51 -0700 (PDT) Received: from unix.guru.org (phantasma.bevc.blacksburg.va.us [198.82.200.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA21151 for ; Sun, 13 Oct 1996 08:34:40 -0700 (PDT) Received: (from kmitch@localhost) by unix.guru.org (8.7.5/8.7.3) id LAA13406 for current@freebsd.org; Sun, 13 Oct 1996 11:34:30 -0400 (EDT) From: Keith Mitchell Message-Id: <199610131534.LAA13406@unix.guru.org> Subject: Re: Weirdness in current In-Reply-To: from kmitch at "Oct 11, 96 08:55:05 am" To: current@freebsd.org Date: Sun, 13 Oct 1996 11:34:30 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I am running current (10-10) and have noticed the following weirdnesses. These > also existed in the 09-25 version. > > I have a C++ program I wrote, and it works fine as long as you don't try to > redirect the output. Doing so, causes it to core dump. Compiling the > same program on a 2.1.0R system works fine though. I have a little more insight on this one. It appears that the same libraries are not getting linked in on current as on stable (2.1.0 or 2.1.5). For some reason the math library is getting linked in on stable even though I don't tell it to and my program doesn't use it directly. Current doesn't link in the math library. If I manually tell it to link in the math library everything works fine. I don't have a clue why its doing this on I/O redirection. Anyway here are the ldd outputs in hope that someone will be able to find out what the problem is: -stable: -lm.2 => /usr/lib/libm.so.2.0 (0x802f000) -lc.2 => /usr/lib/libc.so.2.2 (0x8054000) -current: -ltermcap.2 => /usr/lib/libtermcap.so.2.1 (0x8097000) -lcurses.2 => /usr/lib/libcurses.so.2.0 (0x808b000) -lcompat.2 => /usr/lib/libcompat.so.2.0 (0x80a8000) -lg++.3 => /usr/lib/libg++.so.3.0 (0x8021000) -lc.3 => /usr/lib/libc.so.3.0 (0x80ac000) > The second weirdness manifests it self with the wwwcount cgi script that > many people use for a web counter. On my web page (www.guru.org) I have > three counters in a frame (time, date, and counter). When I run netscape > local on my machine to view it (3.0/3.01b1) most of the time I get one of > the counters and a bunch or garbage. If I view it by running netscape > on another machine (2.1.0R or Digital Unix 4.0) it looks fine. Still no clue on this one though. Anyone else experience weird netscape problems on -current? It still does this on a 09/01 level of current. From owner-freebsd-current Sun Oct 13 08:50:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA21852 for current-outgoing; Sun, 13 Oct 1996 08:50:43 -0700 (PDT) Received: from mail.tky007.tth.expo96.ad.jp (root@tky007.tth.expo96.ad.jp [133.246.32.58]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA21795 for ; Sun, 13 Oct 1996 08:49:14 -0700 (PDT) Received: from tky007.tth.expo96.ad.jp (masafumi@localhost [127.0.0.1]) by mail.tky007.tth.expo96.ad.jp (8.7.6/3.4W4-SMTP) with ESMTP id AAA23791; Mon, 14 Oct 1996 00:47:42 +0900 (JST) Message-Id: <199610131547.AAA23791@mail.tky007.tth.expo96.ad.jp> To: hannibal@cyberstation.net Cc: max@wide.ad.jp, freebsd-current@FreeBSD.ORG Subject: Re: IIJ-PPP patch, please review From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= In-Reply-To: Your message of "Sat, 12 Oct 1996 17:15:06 -0500 (CDT)" References: X-Mailer: Mew version 1.06 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 14 Oct 1996 00:47:40 +0900 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Dan> BTW, the filters don't allow anything like "set ifilter 0 Dan> permit tcp estab", because the function that parses the rules Dan> for tcp/udp doesn't let the estab get through... Just need Dan> to delete about 3 lines at the top. Ok, this has been fixed. Thanks. Does anyone see any other problem with this modification? If not, I'd like to commit this change. ----------------------------------------------------------------------- Masafumi NAKANE, Keio Univ., Dept. of Environmental Information E-Mail : max@wide.ad.jp / max@FreeBSD.ORG [URL] : http://www.sfc.wide.ad.jp/~max/ From owner-freebsd-current Sun Oct 13 10:06:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA25284 for current-outgoing; Sun, 13 Oct 1996 10:06:26 -0700 (PDT) Received: from dyson.iquest.net ([198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA25274 for ; Sun, 13 Oct 1996 10:06:22 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id MAA01213 for current@freebsd.org; Sun, 13 Oct 1996 12:06:14 -0500 (EST) From: "John S. Dyson" Message-Id: <199610131706.MAA01213@dyson.iquest.net> Subject: Please test -current!!! To: current@freebsd.org Date: Sun, 13 Oct 1996 12:06:14 -0500 (EST) 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 Hi y'all: Jordan is going to cut another -snap (to fix some bogosities). I made some commits that were a little less careful than I would have right before a snap... Be evil and agressive towards -current to flush out any bugs that might have popped up (esp. VM system!!!) I think it is okay, but let's test just in case. John From owner-freebsd-current Sun Oct 13 11:37:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA29921 for current-outgoing; Sun, 13 Oct 1996 11:37:39 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA29916 for ; Sun, 13 Oct 1996 11:37:36 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.0/8.8.Beta.3) with SMTP id NAA18572 for ; Sun, 13 Oct 1996 13:37:35 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.15) id ; Sun, 13 Oct 96 13:37 CDT Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.Beta.6/8.8.Beta.3) id NAA25616 for current@freebsd.org; Sun, 13 Oct 1996 13:37:34 -0500 (CDT) From: Karl Denninger Message-Id: <199610131837.NAA25616@Jupiter.Mcs.Net> Subject: Patch which I installed for the SYN-flood related crashes To: current@freebsd.org Date: Sun, 13 Oct 1996 13:37:34 -0500 (CDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Note that we have now been running with this for almost 2 full days. No panics. The fix we are using is as follows: ~line 416 in tcp_input.c: if (so2 == 0) { tcpstat.tcps_listendrop++; so2 = sodropablereq(so); if (so2) { sofree(so2); /* Free Socket */ so2 = sonewconn(so, 0); if (!so2) /* Can't happen? */ goto drop; } else { goto drop; } } This appears to have no bad side effects (no mbufs being stuck, no memory leaks which we can discern, etc.) And it DOES appear to fix the problem. We're going to grab the new committed stuff and compare it -- I understand another fix was committed in the last few days - but the fix above definitely appears to be effective. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-current Sun Oct 13 15:14:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA08513 for current-outgoing; Sun, 13 Oct 1996 15:14:33 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA08507 for ; Sun, 13 Oct 1996 15:14:20 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id SAA16975; Sun, 13 Oct 1996 18:14:01 -0400 (EDT) Date: Sun, 13 Oct 1996 18:14:01 -0400 (EDT) From: Brian Tao To: Michael Smith cc: jkh@time.cdrom.com, FREEBSD-CURRENT-L Subject: Re: 961006-SNAP comments In-Reply-To: <199610110157.LAA21094@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 11 Oct 1996, Michael Smith wrote: > > What makes you say it doesn't? And if it doesn't, where's the pr > explaining the problem? How can we fix something if nobody will tell > us that it's broken? I'm pretty sure I submitted one eons ago when visual config first appeared and I noticed that the pcvt arrow keys don't work. Of course, that was also one of the first pr's I sent, so I may have totally mucked it up. ;-) I haven't tried visual config with a 2.2 snapshot yet though. If the problem is still there, I'll resubmit the pr. -- Brian Tao (BT300, taob@io.org, taob@ican.net) Senior Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't" From owner-freebsd-current Sun Oct 13 15:29:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA09150 for current-outgoing; Sun, 13 Oct 1996 15:29:15 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA09137 for ; Sun, 13 Oct 1996 15:29:09 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.0/8.8.Beta.3) with SMTP id RAA23545 for ; Sun, 13 Oct 1996 17:29:08 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.15) id ; Sun, 13 Oct 96 17:29 CDT Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.Beta.6/8.8.Beta.3) id RAA01131 for current@freebsd.org; Sun, 13 Oct 1996 17:29:07 -0500 (CDT) From: Karl Denninger Message-Id: <199610132229.RAA01131@Jupiter.Mcs.Net> Subject: More on the disappearing directory problem To: current@freebsd.org Date: Sun, 13 Oct 1996 17:29:07 -0500 (CDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Environment: Mounted directory via NFS, -CURRENT load. Ftp into the machine using a normal login, and do a "pwd". You sometimes get back a "permission denied" status. With the actual error logged, you get this: 230 User trebor logged in. Remote system type is UNIX. Using binary mode to transfer files. ftp> pwd 550 Permission denied (2). ftp> quit 221 Goodbye. Errno = 2, which is "ENOENT", or the directory DISAPPEARED! (This is being returned by the "getcwd" system call) However, if you then do an "ls -la", you DO see the directory and its contents. This is the only remaining open problem in the -CURRENT tree that we have. Anyone have any ideas on this? -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-current Sun Oct 13 17:09:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA12761 for current-outgoing; Sun, 13 Oct 1996 17:09:16 -0700 (PDT) Received: from haywire.DIALix.COM (haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA12756 for ; Sun, 13 Oct 1996 17:09:11 -0700 (PDT) Received: (from news@localhost) by haywire.DIALix.COM (8.7.6/8.7.3) id IAA05660 for freebsd-current@freebsd.org; Mon, 14 Oct 1996 08:09:01 +0800 (WST) Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-current@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-current@freebsd.org Date: 14 Oct 1996 00:09:01 GMT From: peter@spinner.DIALix.COM (Peter Wemm) Message-ID: <53s0at$358$1@haywire.DIALix.COM> Organization: DIALix Services, Perth, Australia. References: <380.845216513@critter.tfs.com> Subject: Re: make -j# Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <380.845216513@critter.tfs.com>, phk@critter.tfs.com (Poul-Henning Kamp) writes: > > Now that we have the possibility, I guess I should mention that most > compiles go a couple of percent faster if you use the parallel > feature of make(1). > > Try using: > make -j3 > for your kernel makes. I find that using -pipe is a better overall option for a single-cpu compile. When I set in /etc/make.conf: CFLAGS= -O -pipe COPTFLAGS= -O -pipe .. I find that a simple 'make' is faster than any setting of -j# .. This is probably more dependent on the machine in question than anything, including things like cache speed, ram speed, disk speed and architecture (ie: scsi vs. ide etc). I found that the job-complete polling was too chunky though, It seemed that make was taking up to half a second to start a new job after the last one had finished. Dropping one of the select timeout parameters from 500000 usec to 50000 usec made a lot of difference, but it still wasn't quite as quick as simply -pipe. However, on the smp kernel it certainly is nice! :-) Cheers, -Peter From owner-freebsd-current Sun Oct 13 17:43:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA14481 for current-outgoing; Sun, 13 Oct 1996 17:43:12 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA14475 for ; Sun, 13 Oct 1996 17:43:10 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id RAA07619; Sun, 13 Oct 1996 17:42:48 -0700 (PDT) Message-Id: <199610140042.RAA07619@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Karl Denninger cc: current@freebsd.org Subject: Re: More on the disappearing directory problem In-reply-to: Your message of "Sun, 13 Oct 1996 17:29:07 CDT." <199610132229.RAA01131@Jupiter.Mcs.Net> From: David Greenman Reply-To: dg@root.com Date: Sun, 13 Oct 1996 17:42:48 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Errno = 2, which is "ENOENT", or the directory DISAPPEARED! (This is being >returned by the "getcwd" system call) > >However, if you then do an "ls -la", you DO see the directory and its >contents. > >This is the only remaining open problem in the -CURRENT tree that we have. > >Anyone have any ideas on this? Just a thought... Look at the permissions of the underlying mount point for the NFS directory and make sure that it doesn't restrict any access. I recall that there was some sort of bug with NFS that the wrong inode is looked at sometimes at the mount point. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Sun Oct 13 17:46:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA14669 for current-outgoing; Sun, 13 Oct 1996 17:46:39 -0700 (PDT) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA14663; Sun, 13 Oct 1996 17:46:38 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199610140046.RAA14663@freefall.freebsd.org> Subject: Re: make -j# To: peter@spinner.DIALix.COM (Peter Wemm) Date: Sun, 13 Oct 1996 17:46:37 -0700 (PDT) Cc: freebsd-current@freebsd.org In-Reply-To: <53s0at$358$1@haywire.DIALix.COM> from "Peter Wemm" at Oct 14, 96 00:09:01 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Peter Wemm wrote: > > I find that using -pipe is a better overall option for a single-cpu compile. > When I set in /etc/make.conf: > CFLAGS= -O -pipe > COPTFLAGS= -O -pipe > .. I find that a simple 'make' is faster than any setting of -j# .. > > This is probably more dependent on the machine in question than anything, > including things like cache speed, ram speed, disk speed and architecture > (ie: scsi vs. ide etc). > > I found that the job-complete polling was too chunky though, It seemed that > make was taking up to half a second to start a new job after the last one > had finished. Dropping one of the select timeout parameters from 500000 > usec to 50000 usec made a lot of difference, but it still wasn't quite as > quick as simply -pipe. > > However, on the smp kernel it certainly is nice! :-) Peter, how much faster is make work on an smp box than on the same box running only one processor? how much of a boost are we getting at this point? if i had a multiprocessor box, i would know without asking ;( jmb From owner-freebsd-current Sun Oct 13 18:23:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA16078 for current-outgoing; Sun, 13 Oct 1996 18:23:21 -0700 (PDT) Received: from spinner.DIALix.COM (root@spinner.DIALix.COM [192.203.228.67]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA16070 for ; Sun, 13 Oct 1996 18:23:17 -0700 (PDT) Received: from spinner.DIALix.COM (peter@localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.8.0/8.8.0) with ESMTP id JAA03430; Mon, 14 Oct 1996 09:23:06 +0800 (WST) Message-Id: <199610140123.JAA03430@spinner.DIALix.COM> X-Mailer: exmh version 1.6.9 8/22/96 To: "Jonathan M. Bresler" cc: freebsd-current@freebsd.org Subject: Re: make -j# In-reply-to: Your message of "Sun, 13 Oct 1996 17:46:37 MST." <199610140046.RAA14663@freefall.freebsd.org> Date: Mon, 14 Oct 1996 09:23:05 +0800 From: Peter Wemm Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Jonathan M. Bresler" wrote: > Peter Wemm wrote: > > > > I find that using -pipe is a better overall option for a single-cpu compile [..] > > However, on the smp kernel it -j# certainly is nice! :-) > > Peter, > how much faster is make work on an smp box than on the > same box running only one processor? how much of a boost > are we getting at this point? > > if i had a multiprocessor box, i would know without asking ;( > jmb I knew I'd be getting questions like this if I mentioned smp.. :-) The machine I have here is somewhat crippled. It's a old neptune pciset based board which has the interesting requirement that if you turn on writeback on the cpu cache, it apparently needs to be turned off on the L2 cache or you get nasty coherency problems (which I certainly saw with L2 writeback enabled, certain "locked" bus-cycles were getting lost, not good when it's holding the kernel mutex updates). As well, it's certainly not known to be a particularly fast motherboard anyway. I suspect having both cpu's hammering the busses is one of the main causes of the slowdown. Within the kernel, we also have the additional problem that the process selection does not count for the benefit of the local cpu cache, and it seems more often than not that with multiple processes running, they bounce backwards and forwards between the cpus, thrashing the L1 cache each time. As a result, with a single "make" thread with SMP active on this slow box, there's an overall slowdown (about 80% normal speed from memory, I've not tested the relative speeds for a while). However, running 'make -j4' on this dual processor machine runs at about 1.8 to 1.9 times faster than the single threaded make, which puts it at about 1.5 times normal speed. Remember, this is work-in-progress stuff and we've not put a lot of effort into performance yet.. Most of the work has going into the basic "getting it working" stuff. Cheers, -Peter From owner-freebsd-current Sun Oct 13 18:43:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA16992 for current-outgoing; Sun, 13 Oct 1996 18:43:41 -0700 (PDT) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA16986 for ; Sun, 13 Oct 1996 18:43:37 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.7.5/8.7.3) id DAA19170; Mon, 14 Oct 1996 03:51:30 +0200 (MET DST) From: Mikael Karpberg Message-Id: <199610140151.DAA19170@ocean.campus.luth.se> Subject: Re: 961006-SNAP comments To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Mon, 14 Oct 1996 03:51:28 +0200 (MET DST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199610110157.LAA21094@genesis.atrad.adelaide.edu.au> from Michael Smith at "Oct 11, 96 11:26:59 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk According to Michael Smith: > Stefan Bethke stands accused of saying: > > > > Well, the few times I had to install '95 or NT (not that I would suggest > > '95 being an OS or anything), it detected the hardware (SMC Ultra, NE2000 > > clones) without problems (the other cards were PCI). Also I've been told > > that '95 typically detects hardware quite nicely (I'm not talking PnP or > > PCI). > > > > I now have installed both 2.1.0 and 2.1.5 a few times, and I think better > > automatic probes would be helpful for people "who probably have no clue". > > You're quite welcome to write one. You do realise that the "if the disk > light stops blinking you should turn the machine off and on again" thing > is largely there because the sort of brutal probing necessary to find an > NE2000 is just the sort of thing that totally screws other devices (eg. > SCSI controllers etc.). (No, sorry. I can't help write this. Not right now, at least. Anyway...) Ok, so some are, but it does work for a lot of devices, no? So at least we could probe the "nice" devices, and set as much up automagically as possible maybe? And on the issue of dropping straight into the userconfig... After any possible autoprobing (of the kind what will not screw anything up), give a small menu, looking something like: ----- Before the installation continues, FreeBSD will have to know what kind of hardware you are using. Please choose the way you would like to get your system set up: 0. Help --> 1. Continue with generic boot (Recommended) 2. Automatic probing for special hardware 3. Manual configuration 4. Expert configuration ----- Help would explain a bit more why we need this information anyway (in a newbie language way) and what each choice means, in more detail. "1" speaks for itself... "2" would (after pretty much the same "warning, if the computer hangs, reset it" warning as win95 has) do a major probing thing, trying to find out what the system contained, pretty much like win95 does. "3" could be a "20 questions" thing, with yes/no answers, as others suggested earlier. "4" kick the user into "visual mode" If you want your good old non visual, boot with -c. If you want the normal generic boot, just hit return. Also... There have been a "load preconfigured setup" or something like that for a while in the setup (haven't tried the two latest SNAPs at all, yet, sorry) and it just strikes me as pretty silly no to have a "save" if you have a "load". Would be nice to be able to save instead of commiting when using the custom setup. Then you set everything up, try, fail for some reason like your ethernet card being on the wrong interupt, you just boot with -c, set it, and reload the configuration. Would be nice. I guess the same thing goes for the userconfig load feature I read about, but have yet to experience. I'm going to give the new SNAP a shot soon, I hope... /Mikael From owner-freebsd-current Sun Oct 13 19:32:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA19173 for current-outgoing; Sun, 13 Oct 1996 19:32:51 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA19167 for ; Sun, 13 Oct 1996 19:32:48 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id TAA27048; Sun, 13 Oct 1996 19:32:14 -0700 (PDT) To: Mikael Karpberg cc: msmith@atrad.adelaide.edu.au (Michael Smith), freebsd-current@FreeBSD.org Subject: Re: 961006-SNAP comments In-reply-to: Your message of "Mon, 14 Oct 1996 03:51:28 +0200." <199610140151.DAA19170@ocean.campus.luth.se> Date: Sun, 13 Oct 1996 19:32:14 -0700 Message-ID: <27046.845260334@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Before the installation continues, FreeBSD will have to know what kind > of hardware you are using. Please choose the way you would like to get > your system set up: > > 0. Help > --> 1. Continue with generic boot (Recommended) > 2. Automatic probing for special hardware > 3. Manual configuration > 4. Expert configuration Grab the current boot floppy from ftp://whisker.cdrom.com/pub/2.2-961012-SNAP and let me know if this is closer to what you'd like to see. > "2" would (after pretty much the same "warning, if the computer hangs, > reset it" warning as win95 has) do a major probing thing, trying to > find out what the system contained, pretty much like win95 does. Heh. That's a LOT easier to describe than to implement, so unless you've got some amazing diffs to offer me, consider that a "long term to never" feature ;-). > Also... There have been a "load preconfigured setup" or something like > that for a while in the setup (haven't tried the two latest SNAPs at all, > yet, sorry) and it just strikes me as pretty silly no to have a "save" Erm, save _what_? To the new kernel? Check out the new boot floppy. Jordan From owner-freebsd-current Sun Oct 13 20:05:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA21048 for current-outgoing; Sun, 13 Oct 1996 20:05:16 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA21042 for ; Sun, 13 Oct 1996 20:05:13 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.0/8.8.Beta.3) with SMTP id WAA01648; Sun, 13 Oct 1996 22:05:09 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.15) id ; Sun, 13 Oct 96 22:05 CDT Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.Beta.6/8.8.Beta.3) id WAA07187; Sun, 13 Oct 1996 22:05:06 -0500 (CDT) From: Karl Denninger Message-Id: <199610140305.WAA07187@Jupiter.Mcs.Net> Subject: Re: More on the disappearing directory problem To: dg@root.com Date: Sun, 13 Oct 1996 22:05:06 -0500 (CDT) Cc: karl@Mcs.Net, current@freebsd.org In-Reply-To: <199610140042.RAA07619@root.com> from "David Greenman" at Oct 13, 96 05:42:48 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > >Errno = 2, which is "ENOENT", or the directory DISAPPEARED! (This is being > >returned by the "getcwd" system call) > > > >However, if you then do an "ls -la", you DO see the directory and its > >contents. > > > >This is the only remaining open problem in the -CURRENT tree that we have. > > > >Anyone have any ideas on this? > > Just a thought... Look at the permissions of the underlying mount point for > the NFS directory and make sure that it doesn't restrict any access. I recall > that there was some sort of bug with NFS that the wrong inode is looked at > sometimes at the mount point. > > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project Already thought of that and check it -- not the problem. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-current Sun Oct 13 20:55:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA23433 for current-outgoing; Sun, 13 Oct 1996 20:55:55 -0700 (PDT) Received: from friley216.res.iastate.edu (friley216.res.iastate.edu [129.186.78.216]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA23421 for ; Sun, 13 Oct 1996 20:55:49 -0700 (PDT) Received: from friley216.res.iastate.edu (loopback [127.0.0.1]) by friley216.res.iastate.edu (8.7.6/8.7.3) with ESMTP id WAA03987; Sun, 13 Oct 1996 22:52:04 -0500 (CDT) Message-Id: <199610140352.WAA03987@friley216.res.iastate.edu> To: "Jonathan M. Bresler" Cc: freebsd-current@freebsd.org Subject: Re: make -j# In-reply-to: Your message of Sun, 13 Oct 1996 17:46:37 -0700. <199610140046.RAA14663@freefall.freebsd.org> Date: Sun, 13 Oct 1996 22:52:04 -0500 From: "Chris Csanady" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Peter Wemm wrote: >> >> I find that using -pipe is a better overall option for a single-cpu compile. >> When I set in /etc/make.conf: >> CFLAGS= -O -pipe >> COPTFLAGS= -O -pipe >> .. I find that a simple 'make' is faster than any setting of -j# .. >> >> This is probably more dependent on the machine in question than anything, >> including things like cache speed, ram speed, disk speed and architecture >> (ie: scsi vs. ide etc). >> >> I found that the job-complete polling was too chunky though, It seemed that >> make was taking up to half a second to start a new job after the last one >> had finished. Dropping one of the select timeout parameters from 500000 >> usec to 50000 usec made a lot of difference, but it still wasn't quite as >> quick as simply -pipe. >> >> However, on the smp kernel it certainly is nice! :-) > >Peter, > how much faster is make work on an smp box than on the > same box running only one processor? how much of a boost > are we getting at this point? FWIW, these are the respective times on my box. I only bother because its such a pleasure to see progress. :) Chris Csanady make -O2 -pipe -j3 528.404u 74.618s 5:39.12 177.8% 483+723k 1232+2119io 169pf+0w make -O2 -pipe 560.248u 65.277s 10:27.07 99.7% 482+717k 850+652io 68pf+0w > > if i had a multiprocessor box, i would know without asking ;( >jmb From owner-freebsd-current Sun Oct 13 23:04:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA29267 for current-outgoing; Sun, 13 Oct 1996 23:04:43 -0700 (PDT) Received: from irz201.inf.tu-dresden.de (irz201.inf.tu-dresden.de [141.76.1.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA29239 for ; Sun, 13 Oct 1996 23:04:30 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz201.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id HAA01148 for ; Mon, 14 Oct 1996 07:58:38 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id HAA00653 for freebsd-current@FreeBSD.org; Mon, 14 Oct 1996 07:58:37 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.6/8.6.9) id LAA00320 for freebsd-current@FreeBSD.org; Sun, 13 Oct 1996 11:45:12 +0200 (MET DST) From: J Wunsch Message-Id: <199610130945.LAA00320@uriah.heep.sax.de> Subject: Message buffer oddity To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 13 Oct 1996 11:45:12 +0200 (MET DST) 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=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi all, after upgrading to -current last night, i've seen the strange behaviour of the kernel message buffer below. The only modification i've made is Index: /sys/sys/msgbuf.h =================================================================== RCS file: /home/cvs/src/sys/sys/msgbuf.h,v retrieving revision 1.6 diff -u -u -r1.6 msgbuf.h --- msgbuf.h 1995/08/07 07:58:23 1.6 +++ msgbuf.h 1996/08/17 20:35:16 @@ -37,7 +37,7 @@ #ifndef _SYS_MSGBUF_H_ #define _SYS_MSGBUF_H_ -#define MSG_BSIZE (4096 - 3 * sizeof(unsigned int)) +#define MSG_BSIZE (2 * 4096 - 3 * sizeof(unsigned int)) struct msgbuf { #define MSG_MAGIC 0x063061 unsigned int msg_magic; i.e., the message buffer is increased to (what i think) two pages. Now, the device probe gave me: (ncr0:3:0): "SONY SMO-C501-09 KG 2.13" type 0 removable SCSI 1 od0(ncr0:3:0): Optical 281MB (576999 512 byte sectors) od0(ncr0:3:0): with approximate 18612 cyls, 1 heads, and 31 sectors/track (ncr0:4:0): "TANDBEHi all, after upgrading to -current last night, i've seen the strange behaviour of the kernel message buffer below. The only modification i've made is Index: /sys/sys/msgbuf.h =================================================================== As you can see, the mail i'm just typing goes to the kernel message buffer! (Right after booting, there has been junk in this area.) Normally, this should have been: Oct 13 03:11:31 uriah /kernel: (ncr0:4:0): "TANDBERG TDC 4222 =07:" type 1 removable SCSI 2 Oct 13 03:11:31 uriah /kernel: st0(ncr0:4:0): Sequential-Access Oct 13 03:11:31 uriah /kernel: st0(ncr0:4:0): asynchronous. Oct 13 03:11:31 uriah /kernel: density code 0x0, 512-byte blocks, write-enabled Oct 13 03:11:31 uriah /kernel: Probing for devices on the ISA bus: Oct 13 03:11:31 uriah /kernel: vt0 at 0x60-0x6f irq 1 on motherboard Oct 13 03:11:31 uriah /kernel: vt0: unkown s3, 80 col, color, 8 scr, mf2-kbd, [R3.20-b24] etc. The syslog has registered everything up to the "TANDBE . Right now, dmesg shows me: od0(ncr0:3:0): Optical 281MB (576999 512 byte sectors) od0(ncr0:3:0): with approximate 18612 cyls, 1 heads, and 31 sectors/track (ncr0:4:0): "TANDBEl獦^D So the tail of the message buffer is overwritten again and again, at an odd address (*msgbufp + 6905). Is this due to me extending it beyond 4 KB? (The kernel has been recompiled from scratch, and i used to run previous kernels with this modification without problems.) I gonna reboot now again, and see whether this will happen again. Of course, i have to send the mail before... -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Oct 13 23:06:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA29371 for current-outgoing; Sun, 13 Oct 1996 23:06:28 -0700 (PDT) Received: from irz201.inf.tu-dresden.de (irz201.inf.tu-dresden.de [141.76.1.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA29333 for ; Sun, 13 Oct 1996 23:05:38 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz201.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA01299 for ; Mon, 14 Oct 1996 08:02:38 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA00819 for freebsd-current@FreeBSD.org; Mon, 14 Oct 1996 08:02:37 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.6/8.6.9) id LAA00330 for freebsd-current@FreeBSD.org; Sun, 13 Oct 1996 11:47:32 +0200 (MET DST) From: J Wunsch Message-Id: <199610130947.LAA00330@uriah.heep.sax.de> Subject: panic: update: rofs mod To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 13 Oct 1996 11:47:32 +0200 (MET DST) 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 How comes this? I booted the system, but remembered that i wanted to boot with -v, so i hit ^\ quickly during the rc startup. Thus, i've quit the mount command, but a `reboot' gave me: fs = / panic: update: rofs mod How comes that the root fs is being modified before the mount system call that updated its status to r/w completed? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Oct 13 23:16:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA00455 for current-outgoing; Sun, 13 Oct 1996 23:16:49 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA00450 for ; Sun, 13 Oct 1996 23:16:47 -0700 (PDT) Received: from irz201.inf.tu-dresden.de by mail.crl.com with SMTP id AA21314 (5.65c/IDA-1.5 for ); Sun, 13 Oct 1996 23:15:53 -0700 Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz201.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA01370 for ; Mon, 14 Oct 1996 08:04:37 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA00897 for freebsd-current@FreeBSD.org; Mon, 14 Oct 1996 08:04:36 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.6/8.6.9) id MAA00309 for freebsd-current@FreeBSD.org; Sun, 13 Oct 1996 12:16:03 +0200 (MET DST) From: J Wunsch Message-Id: <199610131016.MAA00309@uriah.heep.sax.de> Subject: Re: Message buffer oddity To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 13 Oct 1996 12:16:02 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from j at "Oct 13, 96 11:45:12 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=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Followup after rebooting: > I gonna reboot now again, and see whether this will happen again. Of > course, i have to send the mail before... It's still there. I can fully reproduce it by booting with -v (so to produce large probe output), and even without -v, it happens a few bytes later. I recompiled a kernel from scratch, with reverted to the original version. It's less obvious now, but every now and then, i also get something like: Device sd1a: name slot allocat%4O\^A%Dc\^A\^ETO\^A\^EdO\^A\^E\M^Ts\^A\^ED\M^W\^A\^ET{\^A\^EdO\^A\^EtK\^A\^E\^DO\^AG\M^T\^N\^A\^E\M^T_\^A\^Et+\^A\^E$\M^@\^A\^ED,\^A\^ET,\^A\^Ety\^A\^E\^DJ\^A\^E$B\^A\^Edf\^A\^Etn\^A\^Ed\M^B\^A\^Etr\^A\^E\^Ds\^A\^E\^TS\^A\^E4\M^_\^A\^E\M^Dk\^A\^E\M^Tk\^A\^E$\M^[\^A\^E4k\^A\^ED3\^A\^ET\M^_\^A\^Ed\^?\^A\^Et\^?\^A\^E\^D\M^@\^A\^E\^T8\^A\^E$D\^A\^E4D\^A\^Ed\M^H\^A\^Et\240\^A\^E\M^D\M^D\^A\^E\M^T\M^D\^A\^E$\M^D\^A\^E4\M^D\^A\^EDl\^A\^ETl\^A\^Edl\^A\^Etl\^A\^E\^Dm\^A\^E\^Ta\^A\^E$m\^A\^E4m\^A\^EDm\^AGT1Gt\M^]G4]GdqGtYG\M^DYG$-ion failed (E=17) Device rsd1a: name slot allocation failed (E=17) You notice that there's just junk inmidst a word, while the word itself is intact. The amount of junk varies between inocations of `dmesg', sometimes everything looks ok. I've also noticed that syslogd takes a huge amount of time to start with allot of rattling on the disk after my upgrade to -current. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Oct 13 23:30:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA01619 for current-outgoing; Sun, 13 Oct 1996 23:30:31 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA01612 for ; Sun, 13 Oct 1996 23:30:28 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id GAA08168; Mon, 14 Oct 1996 06:30:23 GMT Date: Mon, 14 Oct 1996 15:30:22 +0900 (JST) From: Michael Hancock To: Karl Denninger cc: current@FreeBSD.org Subject: Re: More on the disappearing directory problem In-Reply-To: <199610132229.RAA01131@Jupiter.Mcs.Net> 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, 13 Oct 1996, Karl Denninger wrote: > Errno = 2, which is "ENOENT", or the directory DISAPPEARED! (This is being > returned by the "getcwd" system call) > > However, if you then do an "ls -la", you DO see the directory and its > contents. Do you see the directory with plain ls? There is a significant difference when you need to get attributes. Regards, Mike Hancock From owner-freebsd-current Mon Oct 14 00:04:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA04683 for current-outgoing; Mon, 14 Oct 1996 00:04:11 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA04676 for ; Mon, 14 Oct 1996 00:04:05 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id QAA21439; Mon, 14 Oct 1996 16:58:48 +1000 Date: Mon, 14 Oct 1996 16:58:48 +1000 From: Bruce Evans Message-Id: <199610140658.QAA21439@godzilla.zeta.org.au> To: freebsd-current@freebsd.org, peter@spinner.DIALix.COM Subject: Re: make -j# Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >COPTFLAGS= -O -pipe >.. I find that a simple 'make' is faster than any setting of -j# .. > >This is probably more dependent on the machine in question than anything, >including things like cache speed, ram speed, disk speed and architecture >(ie: scsi vs. ide etc). -j3 added to -pipe slows things down slightly on a 32MB system with a slow disk here. System time is > 20% larger. The slowdown is larger for `make -j3 2>foo' because -jN botches stderr. Steve Price is fixing this. Bruce From owner-freebsd-current Mon Oct 14 00:29:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA06471 for current-outgoing; Mon, 14 Oct 1996 00:29:14 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA06455 for ; Mon, 14 Oct 1996 00:28:57 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA01079; Mon, 14 Oct 1996 09:23:42 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA04671; Mon, 14 Oct 1996 09:23:40 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.6/8.6.9) id JAA03461; Mon, 14 Oct 1996 09:13:20 +0200 (MET DST) From: J Wunsch Message-Id: <199610140713.JAA03461@uriah.heep.sax.de> Subject: Re: Can't make current! To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 14 Oct 1996 09:13:20 +0200 (MET DST) Cc: perry@alpha.jpunix.com (John A. Perry) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "John A. Perry" at "Oct 12, 96 02:45: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 John A. Perry wrote: > I'm trying to upgrade from FreeBSD 2.1.5 off of the CD to current > as of Sat. morn. (Oct. 12). The "make world" is failing with the following > messages. The beginning of the problem is where "make world" wants to: > > cd /usr/src/gnu/lib/libstdc++ && make beforeinstall > install -C -o bin -g bin -m 444 > /usr/local/src/gnu/lib/libstdc++/_G_config.h > /usr/local/src/gnu/lib/libstdc++/../../../contrib/libg++/libstdc++/cassert > > [stuff deleted] > > and ending in an error: > > install: > /usr/local/src/gnu/lib/libstdc++/../../../contrib/libg++/libstdc++/cassert: I've also went through an upgrade to -current by the weekend. Well, it sometimes helps you much to run your first make as `make -k', install the tools once they are ready, and then rerun `make' to build the stuff that didn't make it in the first pass. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Oct 14 01:14:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA10283 for current-outgoing; Mon, 14 Oct 1996 01:14:03 -0700 (PDT) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA10234 for ; Mon, 14 Oct 1996 01:13:12 -0700 (PDT) Received: from sol1.gud.siemens.co.at (root@[10.1.143.100]) by zwei.siemens.at (8.7.5/8.7.3) with SMTP id KAA04205 for ; Mon, 14 Oct 1996 10:11:11 +0200 (MET DST) Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0vCi8U-000211C; Mon, 14 Oct 96 10:12 MET DST Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37) id AA158850742; Mon, 14 Oct 1996 10:12:22 +0200 From: "Hr.Ladavac" Message-Id: <199610140812.AA158850742@ws2301.gud.siemens.co.at> Subject: Re: gcc's bug. please comment To: charnier@xp11.frmug.org (Philippe Charnier) Date: Mon, 14 Oct 1996 10:12:22 +0200 (MESZ) Cc: current@FreeBSD.org In-Reply-To: <199610111905.VAA01615@xp11.frmug.org> from "Philippe Charnier" at Oct 11, 96 09:05:36 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk E-mail message from Philippe Charnier contained: > > Hello, > > A friend found a bug in gcc-2.7.2.1. The following program fails on > i386 architecture (both FreeBSD and solaris-x86) and works as expected > on sparc (both sunos and solaris2.5.1) and on hp (hp-ux9.07). As I'm > not on the gcc-bug list, please comment before I report the bug. This > afternoon I sent a bug report to Sun but it was before trying on > FreeBSD. > > The output should be `1 2' but it is `2 1' on i386 computers. > Here is the code: > > ----------mypb2.c----------------- > #include > #include > > main() > { FILE *fic; > int a[2][50], i = 0; > > fic=fopen("mypb2.csv","r"); > fscanf(fic, "%d;%d", &a[1][i++], &a[1][i++]); ^^^ ^^^ Undefined Behaviour; see comp.lang.c FAQ > i = 0; > while (i < 2) printf("%d ", a[1][i++]); > printf("\n"); > fclose(fic); > } Since you just invoked undefined behavior of the C compiler you should count yourself happy that your disks weren't wiped off clean. Specifically, comma in the argument list *is*not*a*sequence*point* and you cannot tell what the value of i is going to be in those two references. The compiler is free to optimize it the way it likes it. As a matter of fact, you cannot tell what should i be even after this line. What you wrote is just another instance of the well-known: i = i++; /Marino From owner-freebsd-current Mon Oct 14 07:10:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA29194 for current-outgoing; Mon, 14 Oct 1996 07:10:15 -0700 (PDT) Received: from Octopussy (Octopussy.MI.Uni-Koeln.DE [134.95.212.20]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA29043; Mon, 14 Oct 1996 07:07:54 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-13.slip.Uni-Koeln.DE) by Octopussy with SMTP id AA20223 (5.67b/IDA-1.5); Mon, 14 Oct 1996 16:07:24 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.6/8.6.9) id QAA00744; Mon, 14 Oct 1996 16:07:25 +0200 (MET DST) Message-Id: <199610141407.QAA00744@x14.mi.uni-koeln.de> Date: Mon, 14 Oct 1996 16:07:25 +0200 From: se@zpr.uni-koeln.de (Stefan Esser) To: asami@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: kern/1782: ncr driver thinks all drives are created asynchronous In-Reply-To: <199610130108.SAA01054@baloon.mimi.com>; from asami@freebsd.org on Oct 12, 1996 18:08:41 -0700 References: <199610130108.SAA01054@baloon.mimi.com> X-Mailer: Mutt 0.45 Mime-Version: 1.0 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk asami@freebsd.org writes: > > >Number: 1782 > >Category: kern > >Synopsis: ncr driver thinks all drives are created asynchronous Sorry for the inconvenience! (And thanks for reporting this.) I've been very busy recently, but tried to get support for the various 53c875 based cards into -current before the next SNAP CD-ROM gets cut. Seems there are now many really different NCR cards, and the driver has to tell them appart, or it can't support their sync transfer modes ... :( Vendors don't currently support the Subvendor/device ID, that was introduced in PCI 2.1, and I have to identify the cards by other means. I hope that everything is working correctly again, by now. Regards, STefan From owner-freebsd-current Mon Oct 14 08:11:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA02690 for current-outgoing; Mon, 14 Oct 1996 08:11:47 -0700 (PDT) Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [193.124.36.33]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA02665 for ; Mon, 14 Oct 1996 08:11:25 -0700 (PDT) Received: from itfs.UUCP (uucp@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) with UUCP id VAA01876 for current@freebsd.org; Mon, 14 Oct 1996 21:10:19 +0600 Received: by itfs.nsk.su; Mon, 14 Oct 96 22:07:40 +0700 (NST) Received: (from daemon@localhost) by news.itfs.nsk.su (8.7.5/8.6.12) id VAA22059; Mon, 14 Oct 1996 21:51:13 +0700 (NSD) From: "Nickolay N. Dudorov" To: current@freebsd.org Subject: sgttyb vs. termios in current (?) Date: 14 Oct 1996 14:51:11 GMT Message-ID: <53tk0v$hse@news.itfs.nsk.su> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk After installation of 961006-SNAP on one of my systems I've made a kernel without COMPAT_43 option and discover that 'rlogin' echo-ed my password ;-( Investigations of sources shows that some programs still used (now obsoleted ?) sgtty headers and functions. The main "home" of such programs is 'src/games'. There are: atc, backgammon, hack, larn, rain, rogue, snake, tetris, trek, worms. Personaly I have no interest in rewriting any of this toward termios (never have used any of them on FreeBSD ;). 'src/usr.sbin' have some number of such programs also. Stuff in 'xntpd/clockstuff' and 'pcvt/vttest' seems unused in FreeBSD. 'pcvt/fontedit' looks suspicious - it tests #ifdef BSD (and uses sgttyb) before testing #if defined(__FreeBSD__). 'watch' unconditionally use sgttyb only (due to author's absence ?). In 'src/usr.bin' there is one unused(?) file in 'ee' (ee/doc/new_curse.c). 'src/usr.bin/talk/io.c' gives wanderfull example of sgttyb use: ioctl(0, FIONREAD, (struct sgttyb *) &nb); where nb is int ;-) (so the text in inner parens can/must be deleted). The two programs which I have interest in are 'rlogin' and 'lock'. Both of them was patched to use 'termios' in OpenBSD (may be in NetBSD also, but is there (anon)CVS acces to NetBSD-current ?). I've made patches for FreeBSD-current based on OpenBSD versions of rlogin and lock. If it is desirable, I can send-pr them. There is small problem with 'rlogin' - OpenBSD version discard 'litout' mode from terminal settings and options parsing, but not from options list and 'usage' message. In my patch I just ignore 'L' option, but accept it (to avoid man page rewriting ;-). Another question with 'lock' sources in FreeBSD was rised by: s[0] = NULL; assignment (with 'char s[BUFSIZ]' declaration). Corresponding line in OpenBSD looks like: s[0] = '\0'; This is not a real 'bug' and I've not touch it in my patch, but in current form it is not correct (and must be rewritten to, say: s[0] = 0; to save 3 bytes * miriads of disks with FreeBSD sources ;-) N. Dudorov From owner-freebsd-current Mon Oct 14 08:37:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA04349 for current-outgoing; Mon, 14 Oct 1996 08:37:45 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA04342 for ; Mon, 14 Oct 1996 08:37:42 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.0/8.8.Beta.3) with SMTP id KAA22358; Mon, 14 Oct 1996 10:37:33 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.15) id ; Mon, 14 Oct 96 10:37 CDT Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.Beta.6/8.8.Beta.3) id KAA02831; Mon, 14 Oct 1996 10:37:31 -0500 (CDT) From: Karl Denninger Message-Id: <199610141537.KAA02831@Jupiter.Mcs.Net> Subject: Re: More on the disappearing directory problem To: michaelh@cet.co.jp (Michael Hancock) Date: Mon, 14 Oct 1996 10:37:31 -0500 (CDT) Cc: karl@Mcs.Net, current@FreeBSD.org In-Reply-To: from "Michael Hancock" at Oct 14, 96 03:30:22 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > On Sun, 13 Oct 1996, Karl Denninger wrote: > > > Errno = 2, which is "ENOENT", or the directory DISAPPEARED! (This is being > > returned by the "getcwd" system call) > > > > However, if you then do an "ls -la", you DO see the directory and its > > contents. > > Do you see the directory with plain ls? There is a significant > difference when you need to get attributes. > > Regards, > > > Mike Hancock Yes, including the parent (..). That's what really gets me -- finding this one so far as proved to be a royal bitch. Its the only remaining problem in the -current tree that prevents us from rolling it as a production release. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-current Mon Oct 14 11:02:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA13912 for current-outgoing; Mon, 14 Oct 1996 11:02:20 -0700 (PDT) Received: from innocence.interface-business.de (ino-old.interface-business.de [193.101.57.101]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA13907 for ; Mon, 14 Oct 1996 11:02:14 -0700 (PDT) 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 TAA06669 for ; Mon, 14 Oct 1996 19:01:12 +0100 Received: (from j@localhost) by ida.interface-business.de (8.7.5/8.7.3) id UAA05968 for freebsd-current@FreeBSD.org; Mon, 14 Oct 1996 20:05:00 +0200 (MET DST) From: J Wunsch Message-Id: <199610141805.UAA05968@ida.interface-business.de> Subject: c++filt problem To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 14 Oct 1996 20:05:00 +0200 (MET DST) 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 ===> gnu/usr.bin/cc/c++filt Warning: Object directory not changed from original /usr/src/gnu/usr.bin/cc/c++filt echo "int xxy_us_dummy;" >tmp-dum.c /usr/src/gnu/usr.bin/cc/c++filt/../cc/cc -B/usr/src/gnu/usr.bin/cc/c++filt/../cc1/ -B/usr/src/gnu/usr.bin/cc/c++filt/../cpp/ -S tmp-dum.c /usr/src/gnu/usr.bin/cc/c++filt/../cc/cc: not found *** Error code 1 Stop. (I forgot to `make obj' before. It should IMHO work nevertheless. After running `make obj', it went on.) -- J"org Wunsch Unix support engineer joerg_wunsch@interface-business.de http://www.interface-business.de/~j From owner-freebsd-current Mon Oct 14 15:18:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA29708 for current-outgoing; Mon, 14 Oct 1996 15:18:58 -0700 (PDT) Received: from sdev.usn.blaze.net.au (sdev.usn.blaze.net.au [203.17.53.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA29685; Mon, 14 Oct 1996 15:18:36 -0700 (PDT) Received: from localhost (davidn@localhost) by sdev.usn.blaze.net.au (8.7.6/8.6.9) with SMTP id IAA13002; Tue, 15 Oct 1996 08:17:43 +1000 (EST) Date: Tue, 15 Oct 1996 08:17:42 +1000 (EST) From: David Nugent Reply-To: davidn@blaze.net.au To: sos@FreeBSD.ORG cc: Jake Hamby , current@FreeBSD.ORG Subject: Re: Bug with moused and XFree86 In-Reply-To: <199610110920.LAA14775@ra.dkuug.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 11 Oct 1996 sos@FreeBSD.ORG wrote: >> However, I've noticed two strange bugs affecting XFree86 (I've >> consistently reproduced them with 3.1.2-S as well as the 3.1.2-G beta) >> when moused is running. With twm as the window manager, when I click on >> the title-bar, the "four-corner arrow" stays active AFTER I release the >> mouse button, UNTIL I move the mouse (it _should_ change back to the >> regular arrow immediately after releasing the button). >> >> When fvwm95 is the window manager (which defaults to click-to-focus, not >> focus-follows-mouse), a different bug occurs. When I click to activate a >> new window, any characters I type are ignored, until I move the mouse (as >> little as one pixel), then all the characters I've typed display. >> >> I'm running FreeBSD-current with a Microsoft-compatible serial mouse on >> COM1. "vidcontrol -m off" was in effect during these tests, but the >> moused was running (started by /etc/rc.i386). FWIW, I've noticed similar things, using fvwm2. When the cursor changes, say, between an I-bar and an arrow (moving onto the title bar), the cursor is likely (but not always) to jump to an unexpected position on the screen. Clicking on title bars will do something similar. The effect is more noticable if you attempt to move windows arround. Killing moused causes the problem to simply vanish. >How -current ?? 961004-SNAP is what the kernel reports, or perhaps a day or two later - only a week or so old max. XFree is 3.1.2G >Have you created the /dev/sysmouse & /dev/consolectl devices?? Yes. >Have you enabled the emulate 3 button in moused ?? No. >Have you enabled the emulate 3 button in XFree86 ?? No. >What mouse device does XFree86 use ?? /dev/cuaa0 >What mouse type does XFree86 use ?? mouse systems. moused -p /dev/cuaa0 -t mousesystems. >I see none of the problems here, but then I use a real 3 button >mouse and Xaccel.. This is a 3 button mouse also, but with switching from microsoft and mouse systems mode available (but no middle button in microsoft mode, so I tend not to use it that way). Incidently, is there a software interface to moused available to applications? Regards, David Nugent, Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-791-9547 Data/BBS +61-3-792-3507 3:632/348@fidonet davidn@blaze.net.au http://www.blaze.net.au/~davidn From owner-freebsd-current Mon Oct 14 15:39:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA01883 for current-outgoing; Mon, 14 Oct 1996 15:39:33 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA01876 for ; Mon, 14 Oct 1996 15:39:29 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.6/8.7.3) with SMTP id PAA04543 for ; Mon, 14 Oct 1996 15:37:37 -0700 (PDT) Message-ID: <3262C032.2F1CF0FB@whistle.com> Date: Mon, 14 Oct 1996 15:35:30 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: non-console mode.. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I need to make the system run with it's console disabled.. in other words.. the device exists, bu tut acts as if there is no console Basically the way I 've been thinking about doing this is to have a "console mute" variable that mutes teh console IO before it get's to the physical devices. The aim is to have it be enabled 1/ by a sysctl action from a running process. 2/ by setting a boot flag (or failing to set one) thoughts: There are already several boot options regarding the console and I don't want to add too much more there.. my question: Would I be justified in adding a "RB_MUTE" flag? existing flags that might imply "NO_MUTE" might be: #define RB_ASKNAME 0x001 /* ask for file name to reboot from */ has to ask from somewhere #define RB_SINGLE 0x002 /* reboot to single user only */ where is the shell going to run? #define RB_KDB 0x040 /* give control to kernel debugger */ ddb need the console.. but gdb-remote is better without #define RB_CONFIG 0x400 /* invoke user configuration routing */ The config needs to run on something #define RB_VERBOSE 0x800 /* print all potentially useful info */ If the user wants to see it they might want a console.. #define RB_SERIAL 0x1000 /* user serial port as console */ well the user SAID he wanted a console.. I would rather set a new flag so that existing code runs as usual by default.. so I suggest RB_MUTE to indicate that the console device is MUTED. if anyone has violent objections, I'd like to hear of them before I start work on this thanks. julian p.s. yes there are good reasons for doing this :) From owner-freebsd-current Mon Oct 14 15:52:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA03078 for current-outgoing; Mon, 14 Oct 1996 15:52:49 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA03068; Mon, 14 Oct 1996 15:52:45 -0700 (PDT) Message-Id: <199610142252.PAA03068@freefall.freebsd.org> To: davidn@blaze.net.au cc: sos@FreeBSD.org, Jake Hamby , current@FreeBSD.org Subject: Re: Bug with moused and XFree86 In-reply-to: Your message of "Tue, 15 Oct 1996 08:17:42 +1000." Date: Mon, 14 Oct 1996 15:52:45 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >>What mouse device does XFree86 use ?? > >/dev/cuaa0 It should be using /dev/sysmouse -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Mon Oct 14 17:26:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA08525 for current-outgoing; Mon, 14 Oct 1996 17:26:57 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA08513; Mon, 14 Oct 1996 17:26:55 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id RAA22136 ; Mon, 14 Oct 1996 17:26:53 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.6.12/8.6.12) with SMTP id RAA02343; Mon, 14 Oct 1996 17:25:06 -0700 Date: Mon, 14 Oct 1996 17:25:05 -0700 (PDT) From: Jaye Mathisen To: current@freebsd.org cc: hackers@freebsd.org Subject: -current stable again? 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 held off on upgrading because of the recent problems reported by Karl and others, but -current seems suspiciously quiet after Saturday. Is it safe to use? From owner-freebsd-current Mon Oct 14 17:38:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA09594 for current-outgoing; Mon, 14 Oct 1996 17:38:58 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA09588; Mon, 14 Oct 1996 17:38:55 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id RAA20634; Mon, 14 Oct 1996 17:38:35 -0700 (PDT) To: "Justin T. Gibbs" cc: davidn@blaze.net.au, sos@FreeBSD.org, Jake Hamby , current@FreeBSD.org Subject: Re: Bug with moused and XFree86 In-reply-to: Your message of "Mon, 14 Oct 1996 15:52:45 PDT." <199610142252.PAA03068@freefall.freebsd.org> Date: Mon, 14 Oct 1996 17:38:35 -0700 Message-ID: <20632.845339915@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk /dev/sysmouse? The installer links it to /dev/mouse, actually. Jordan > >>What mouse device does XFree86 use ?? > > > >/dev/cuaa0 > > It should be using /dev/sysmouse > > -- > Justin T. Gibbs > =========================================== > FreeBSD: Turning PCs into workstations > =========================================== From owner-freebsd-current Mon Oct 14 18:28:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA12452 for current-outgoing; Mon, 14 Oct 1996 18:28:12 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA12417; Mon, 14 Oct 1996 18:28:06 -0700 (PDT) Message-Id: <199610150128.SAA12417@freefall.freebsd.org> To: "Jordan K. Hubbard" cc: davidn@blaze.net.au, sos@FreeBSD.org, Jake Hamby , current@FreeBSD.org Subject: Re: Bug with moused and XFree86 In-reply-to: Your message of "Mon, 14 Oct 1996 17:38:35 PDT." <20632.845339915@time.cdrom.com> Date: Mon, 14 Oct 1996 18:28:05 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >/dev/sysmouse? > >The installer links it to /dev/mouse, actually. > > Jordan /dev/sysmouse, /dev/mouse linked to /dev/sysmouse, same difference. The point is to be using the device managed by moused, not the hardware device. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Mon Oct 14 18:54:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA14106 for current-outgoing; Mon, 14 Oct 1996 18:54:55 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA14101 for ; Mon, 14 Oct 1996 18:54:52 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id BAA00464; Tue, 15 Oct 1996 01:54:45 GMT Date: Tue, 15 Oct 1996 10:54:45 +0900 (JST) From: Michael Hancock Reply-To: Michael Hancock To: Karl Denninger cc: current@FreeBSD.org Subject: Re: More on the disappearing directory problem In-Reply-To: <199610141537.KAA02831@Jupiter.Mcs.Net> 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, 14 Oct 1996, Karl Denninger wrote: > > > Errno = 2, which is "ENOENT", or the directory DISAPPEARED! (This is being > > > returned by the "getcwd" system call) > > > Are you in the mount directory or in a subdirectory? If you're in a mount directory does it work in a subdirectory? Regards, Mike Hancock From owner-freebsd-current Mon Oct 14 20:17:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA20730 for current-outgoing; Mon, 14 Oct 1996 20:17:53 -0700 (PDT) Received: from wgrobez1.remote.louisville.edu (root@wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA20711; Mon, 14 Oct 1996 20:17:33 -0700 (PDT) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.6/8.6.12) with SMTP id XAA12967; Mon, 14 Oct 1996 23:16:44 -0400 (EDT) Date: Mon, 14 Oct 1996 23:16:40 -0400 (EDT) From: Gary Roberts To: Jaye Mathisen cc: current@freebsd.org, hackers@freebsd.org Subject: Re: -current stable again? 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, 14 Oct 1996, Jaye Mathisen wrote: > > > I have held off on upgrading because of the recent problems reported by > Karl and others, but -current seems suspiciously quiet after Saturday. Is > it safe to use? > > I tried updating pppd to pppd2.3b or whatever, but it broke my kernel tree. I ended up running a sup to update, everything seems ok, however I did recieve alot of Warning messages from gcc while compiling a new kernel. Gary Roberts System Admin. -- Altered Reality. http://136.165.243.183 -- Main User Pages From owner-freebsd-current Mon Oct 14 23:35:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA04852 for current-outgoing; Mon, 14 Oct 1996 23:35:49 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA04845 for ; Mon, 14 Oct 1996 23:35:46 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id IAA08564; Tue, 15 Oct 1996 08:16:10 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.7.6/8.7.3) with SMTP id IAA00530; Tue, 15 Oct 1996 08:13:35 +0200 (MET DST) Date: Tue, 15 Oct 1996 08:13:35 +0200 (MET DST) From: Andreas Klemm To: Gary Roberts cc: Jaye Mathisen , current@FreeBSD.org Subject: Re: -current stable again? In-Reply-To: Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 14 Oct 1996, Gary Roberts wrote: > On Mon, 14 Oct 1996, Jaye Mathisen wrote: > > > > > > > I have held off on upgrading because of the recent problems reported by > > Karl and others, but -current seems suspiciously quiet after Saturday. Is > > it safe to use? > > > > > I tried updating pppd to pppd2.3b or whatever, but it broke my kernel > tree. I ended up running a sup to update, everything seems ok, however I > did recieve alot of Warning messages from gcc while compiling a new > kernel. That's gcc 2.7.2.1 .... Remove the Warning -W... ;-) BTW, I removed 'hackers' from the Cc:, because it's a topic for -current. -current people always read -hackers .... Andreas /// __ andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Mon Oct 14 23:49:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA05780 for current-outgoing; Mon, 14 Oct 1996 23:49:48 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA05773; Mon, 14 Oct 1996 23:49:44 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id IAA12312; Tue, 15 Oct 1996 08:44:52 +0200 Message-Id: <199610150644.IAA12312@ra.dkuug.dk> Subject: Re: Bug with moused and XFree86 To: davidn@blaze.net.au Date: Tue, 15 Oct 1996 08:44:52 +0200 (MET DST) Cc: sos@FreeBSD.ORG, jehamby@lightside.com, current@FreeBSD.ORG In-Reply-To: from "David Nugent" at Oct 15, 96 08:17:42 am From: sos@FreeBSD.ORG Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to David Nugent who wrote: > > (moving onto the title bar), the cursor is likely (but not > always) to jump to an unexpected position on the screen. > Clicking on title bars will do something similar. The effect is > more noticable if you attempt to move windows arround. Killing > moused causes the problem to simply vanish. > > >How -current ?? > > 961004-SNAP is what the kernel reports, or perhaps a day or two > later - only a week or so old max. > > XFree is 3.1.2G OK. > >Have you created the /dev/sysmouse & /dev/consolectl devices?? > > Yes. OK: > >Have you enabled the emulate 3 button in moused ?? > > No. OK. > >Have you enabled the emulate 3 button in XFree86 ?? > > No. OK. > > >What mouse device does XFree86 use ?? > > /dev/cuaa0 BUMMER! by doing this X and moused competes for the mouse! You should use /dev/sysmouse in X. > > This is a 3 button mouse also, but with switching from microsoft > and mouse systems mode available (but no middle button in > microsoft mode, so I tend not to use it that way). > > Incidently, is there a software interface to moused available to > applications? Yes, there currently only is the ioctl interface that syscons provides which can report mouseactions via a userdefined signal, but that will change sometime in the future when I get a little more time finishing my little pet project. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Mon Oct 14 23:50:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA05828 for current-outgoing; Mon, 14 Oct 1996 23:50:26 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA05823 for ; Mon, 14 Oct 1996 23:50:23 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id IAA12357; Tue, 15 Oct 1996 08:50:12 +0200 Message-Id: <199610150650.IAA12357@ra.dkuug.dk> Subject: Re: non-console mode.. To: julian@whistle.com (Julian Elischer) Date: Tue, 15 Oct 1996 08:50:12 +0200 (MET DST) Cc: current@freebsd.org In-Reply-To: <3262C032.2F1CF0FB@whistle.com> from "Julian Elischer" at Oct 14, 96 03:35:30 pm From: sos@freebsd.org Reply-to: sos@freebsd.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply to Julian Elischer who wrote: > > I need to make the system run with it's console disabled.. > in other words.. > the device exists, bu tut acts as if there is no console > > if anyone has violent objections, I'd like to hear of them before > I start work on this Maybe. > p.s. yes there are good reasons for doing this :) Such as ?? ???? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Tue Oct 15 00:17:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA07070 for current-outgoing; Tue, 15 Oct 1996 00:17:28 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA07064 for ; Tue, 15 Oct 1996 00:17:21 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id AAA22380 for ; Tue, 15 Oct 1996 00:17:10 -0700 (PDT) To: current@freebsd.org Subject: 2.2-961014-SNAP now up for FTP at ftp.freebsd.org Date: Tue, 15 Oct 1996 00:17:01 -0700 Message-ID: <22373.845363821@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Yes, it's only been 4 days since the last SNAP, but that last SNAP had a few major problems with it which made it unsuitable for general use. This SNAP should fix all the major show-stopper bugs and a number of more minor ones. As always, please use send-pr(1) or http://www.freebsd.org/send-pr.html to submit bug reports or comments on this SNAP. Jordan --- What's New, from the release notes: 0. What's new since 2.2-961006-SNAP? ------------------------------------ 11th-hour bug in SYN attack protection code fixed [showstopper]. Support for Cyclades Cyclom-Y (multi-port async serial) PCI adaptors as well as multiple controllers and the 32-Y (if you are currently using the Cyclades serial adapter, you should re-make your /dev entries and remove the old ones). /usr/src/contrib now part of src dist selection (doh!) [showstopper]. You need only change your kernel settings *once* now, on initial startup from the floppy. They will be preserved on the subsequently installed kernel. 0. What's new since 2.2-960801-SNAP? ------------------------------------ Support for HP PC Lan+ cards (model numbers: 27247B and 27252A) Update to gcc 2.7.2.1 & add support for weak symbols. Many things moved/brought into /usr/src/contrib, updating and cleaning up the source tree accordingly. Support for compiled-in shared library ld paths. Update sgmlfmt to `instant'. Protection against the widely reported SYN attack. From owner-freebsd-current Tue Oct 15 00:28:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA07758 for current-outgoing; Tue, 15 Oct 1996 00:28:51 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA07750; Tue, 15 Oct 1996 00:28:47 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id QAA20679; Tue, 15 Oct 1996 16:58:22 +0930 From: Michael Smith Message-Id: <199610150728.QAA20679@genesis.atrad.adelaide.edu.au> Subject: Re: Bug with moused and XFree86nd To: davidn@blaze.net.au Date: Tue, 15 Oct 1996 16:58:22 +0930 (CST) Cc: sos@freebsd.org, jehamby@lightside.com, current@freebsd.org In-Reply-To: from "David Nugent" at Oct 15, 96 08:17:42 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Nugent stands accused of saying: > > Incidently, is there a software interface to moused available to > applications? Not as such; what sort of interface are you looking for? > David Nugent, Unique Computing Pty Ltd - Melbourne, Australia -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Oct 15 01:19:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA12038 for current-outgoing; Tue, 15 Oct 1996 01:19:28 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA12030; Tue, 15 Oct 1996 01:19:24 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id RAA21035; Tue, 15 Oct 1996 17:49:21 +0930 From: Michael Smith Message-Id: <199610150819.RAA21035@genesis.atrad.adelaide.edu.au> Subject: Re: non-console mode.. To: sos@FreeBSD.org Date: Tue, 15 Oct 1996 17:49:20 +0930 (CST) Cc: julian@whistle.com, current@FreeBSD.org In-Reply-To: <199610150650.IAA12357@ra.dkuug.dk> from "sos@FreeBSD.org" at Oct 15, 96 08:50:12 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk sos@FreeBSD.org stands accused of saying: > > In reply to Julian Elischer who wrote: > > > > I need to make the system run with it's console disabled.. > > in other words.. > > the device exists, bu tut acts as if there is no console > > > > if anyone has violent objections, I'd like to hear of them before > > I start work on this > > Maybe. There's no need for either work or violent objections - the 'no console' case is already supported. Look at i386/i386/cons.c. > > p.s. yes there are good reasons for doing this :) > > Such as ?? ???? The box his employers make that doesn't have a console? > Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Oct 15 01:26:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA12863 for current-outgoing; Tue, 15 Oct 1996 01:26:35 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA12856 for ; Tue, 15 Oct 1996 01:26:31 -0700 (PDT) Received: from localhost (scrappy@localhost) by quagmire.ki.net (8.7.5/8.7.5) with SMTP id EAA04150 for ; Tue, 15 Oct 1996 04:26:28 -0400 (EDT) Date: Tue, 15 Oct 1996 04:26:27 -0400 (EDT) From: "Marc G. Fournier" To: current@freebsd.org Subject: make -j3 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... Just to see what would happen on my machine (everyone else was doing it...and no bridge analogies, eh? *grin*)...I tried doing a 'make -j3' for a compile... according to 'time', with -pipe, it came out faster in user/system time and, what I'm assuming, in actual time. What I'm curious about is what exactly does this do? According to the man page, it basically does 'parrellel makes', correct? But if I watch the make process, it doesn't look like more then one file is being compiled at a time...so, on a single CPU system, what does it do to produce a benefit? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Tue Oct 15 01:48:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA14891 for current-outgoing; Tue, 15 Oct 1996 01:48:55 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA14886 for ; Tue, 15 Oct 1996 01:48:50 -0700 (PDT) Received: from localhost (scrappy@localhost) by quagmire.ki.net (8.7.5/8.7.5) with SMTP id EAA05737 for ; Tue, 15 Oct 1996 04:48:54 -0400 (EDT) Date: Tue, 15 Oct 1996 04:48:53 -0400 (EDT) From: "Marc G. Fournier" To: current@freebsd.org Subject: make -j3...ignore last 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... Ignore my last...I wasn't testing out the -j3 on a large enough case...just started it on the kernel and switched back to watching top, and now can see what it does... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Tue Oct 15 02:20:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA18373 for current-outgoing; Tue, 15 Oct 1996 02:20:43 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA18368; Tue, 15 Oct 1996 02:20:38 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id LAA13315; Tue, 15 Oct 1996 11:20:28 +0200 Message-Id: <199610150920.LAA13315@ra.dkuug.dk> Subject: Re: non-console mode.. To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Tue, 15 Oct 1996 11:20:28 +0200 (MET DST) Cc: sos@FreeBSD.org, julian@whistle.com, current@FreeBSD.org In-Reply-To: <199610150819.RAA21035@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Oct 15, 96 05:49:20 pm From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Michael Smith who wrote: > > There's no need for either work or violent objections - the 'no console' > case is already supported. Look at i386/i386/cons.c. > > > > p.s. yes there are good reasons for doing this :) > > > > Such as ?? ???? > > The box his employers make that doesn't have a console? I'm sure I can be talked into makeing a consoledriver for their little LCD display :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Tue Oct 15 02:55:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA20824 for current-outgoing; Tue, 15 Oct 1996 02:55:28 -0700 (PDT) Received: from bunyip.cc.uq.oz.au (daemon@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA20818 for ; Tue, 15 Oct 1996 02:55:23 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.oz.au (8.7.6/8.7.3) id TAA21789 for current@freebsd.org; Tue, 15 Oct 1996 19:55:17 +1000 Received: from pandora.devetir.qld.gov.au by ogre.devetir.qld.gov.au (8.7.5/DEVETIR-E0.3a) with ESMTP id SAA29295 for ; Tue, 15 Oct 1996 18:19:43 +1000 (EST) Received: from netfl15a.devetir.qld.gov.au (netfl15a.devetir.qld.gov.au [167.123.24.12]) by pandora.devetir.qld.gov.au (8.6.10/8.6.12) with ESMTP id SAA01494 for ; Tue, 15 Oct 1996 18:16:12 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id IAA00229 for ; Tue, 15 Oct 1996 08:17:47 GMT Message-Id: <199610150817.IAA00229@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6.5 12/11/95 To: current@freebsd.org Subject: Small compilation problem in -current X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Oct 1996 18:17:47 +1000 From: Stephen Hocking Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ===> sendmail ===> sendmail/src cc -O2 -m486 -pipe -I/usr/src/usr.sbin/sendmail/src -DNEWDB -DNIS -o sendmail alias.o arpadate.o clock.o collect.o conf.o convtime.o daemon.o deliver.o domai n.o envelope.o err.o headers.o macro.o main.o map.o mci.o mime.o parseaddr.o que ue.o readcf.o recipient.o savemail.o srvrsmtp.o stab.o stats.o sysexits.o trace. o udb.o usersmtp.o util.o version.o -lutil conf.o: Undefined symbol `_nis_map_open' referenced from text segment conf.o: Undefined symbol `_nis_map_lookup' referenced from text segment *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. -- The views expressed above are not those of the Worker's Compensation Board of Queensland, Australia. From owner-freebsd-current Tue Oct 15 03:35:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA24024 for current-outgoing; Tue, 15 Oct 1996 03:35:50 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA24017 for ; Tue, 15 Oct 1996 03:35:46 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id UAA22090; Tue, 15 Oct 1996 20:05:39 +0930 From: Michael Smith Message-Id: <199610151035.UAA22090@genesis.atrad.adelaide.edu.au> Subject: Re: Small compilation problem in -current To: sysseh@devetir.qld.gov.au (Stephen Hocking) Date: Tue, 15 Oct 1996 20:05:39 +0930 (CST) Cc: current@FreeBSD.ORG In-Reply-To: <199610150817.IAA00229@netfl15a.devetir.qld.gov.au> from "Stephen Hocking" at Oct 15, 96 06:17:47 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Stephen Hocking stands accused of saying: > > ===> sendmail > ===> sendmail/src > cc -O2 -m486 -pipe -I/usr/src/usr.sbin/sendmail/src -DNEWDB -DNIS -o > sendmail > alias.o arpadate.o clock.o collect.o conf.o convtime.o daemon.o deliver.o > domai > n.o envelope.o err.o headers.o macro.o main.o map.o mci.o mime.o parseaddr.o > que > ue.o readcf.o recipient.o savemail.o srvrsmtp.o stab.o stats.o sysexits.o > trace. > o udb.o usersmtp.o util.o version.o -lutil > conf.o: Undefined symbol `_nis_map_open' referenced from text segment > conf.o: Undefined symbol `_nis_map_lookup' referenced from text segment > *** Error code 1 Just breezed past it here (fresh sup this afternoon); I suspect you have lib breakage. You _are_ building properly, aren't you? 8) -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Oct 15 04:33:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA29165 for current-outgoing; Tue, 15 Oct 1996 04:33:42 -0700 (PDT) Received: from sdev.usn.blaze.net.au (sdev.usn.blaze.net.au [203.17.53.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA29128; Tue, 15 Oct 1996 04:33:28 -0700 (PDT) Received: from localhost (davidn@localhost) by sdev.usn.blaze.net.au (8.7.6/8.6.9) with SMTP id VAA23574; Tue, 15 Oct 1996 21:32:14 +1000 (EST) Date: Tue, 15 Oct 1996 21:32:13 +1000 (EST) From: David Nugent Reply-To: davidn@blaze.net.au To: "Justin T. Gibbs" cc: sos@FreeBSD.org, Jake Hamby , current@FreeBSD.org Subject: Re: Bug with moused and XFree86 In-Reply-To: <199610142252.PAA03068@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 14 Oct 1996, Justin T. Gibbs wrote: >>>What mouse device does XFree86 use ?? >> >>/dev/cuaa0 > >It should be using /dev/sysmouse I get no mouse movement at all when using /dev/sysmouse. crw------- 1 root wheel 12, 255 Oct 15 07:48 /dev/consolectl crw------- 1 root wheel 12, 128 Oct 15 21:30 /dev/sysmouse How can I get it to work? David Nugent, Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-791-9547 Data/BBS +61-3-792-3507 3:632/348@fidonet davidn@blaze.net.au http://www.blaze.net.au/~davidn From owner-freebsd-current Tue Oct 15 04:41:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA29966 for current-outgoing; Tue, 15 Oct 1996 04:41:46 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA29951; Tue, 15 Oct 1996 04:41:43 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id NAA14019; Tue, 15 Oct 1996 13:41:13 +0200 Message-Id: <199610151141.NAA14019@ra.dkuug.dk> Subject: Re: Bug with moused and XFree86 To: davidn@blaze.net.au Date: Tue, 15 Oct 1996 13:41:12 +0200 (MET DST) Cc: gibbs@freefall.freebsd.org, sos@FreeBSD.org, jehamby@lightside.com, current@FreeBSD.org In-Reply-To: from "David Nugent" at Oct 15, 96 09:32:13 pm From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to David Nugent who wrote: > > On Mon, 14 Oct 1996, Justin T. Gibbs wrote: > > >>>What mouse device does XFree86 use ?? > >> > >>/dev/cuaa0 > > > >It should be using /dev/sysmouse > > I get no mouse movement at all when using /dev/sysmouse. > > crw------- 1 root wheel 12, 255 Oct 15 07:48 /dev/consolectl > crw------- 1 root wheel 12, 128 Oct 15 21:30 /dev/sysmouse > > How can I get it to work? Have you started moused with the right mousetype & port ?? Have you set Xfre mouse to /dev/sysmouse type mousesystems ?? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Tue Oct 15 05:09:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA02357 for current-outgoing; Tue, 15 Oct 1996 05:09:10 -0700 (PDT) Received: from sdev.usn.blaze.net.au (sdev.usn.blaze.net.au [203.17.53.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA02269; Tue, 15 Oct 1996 05:08:11 -0700 (PDT) Received: from localhost (davidn@localhost) by sdev.usn.blaze.net.au (8.7.6/8.6.9) with SMTP id WAA23734; Tue, 15 Oct 1996 22:07:09 +1000 (EST) Date: Tue, 15 Oct 1996 22:07:09 +1000 (EST) From: David Nugent Reply-To: davidn@blaze.net.au To: sos@FreeBSD.org cc: gibbs@freefall.freebsd.org, jehamby@lightside.com, current@FreeBSD.org Subject: Re: Bug with moused and XFree86 In-Reply-To: <199610151141.NAA14019@ra.dkuug.dk> 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, 15 Oct 1996 sos@FreeBSD.org wrote: >Have you started moused with the right mousetype & port ?? >Have you set Xfre mouse to /dev/sysmouse type mousesystems ?? Ahh . Right. So I point moused at /dev/cuaa0, and everything that uses it at /dev/sysmouse? Ok, that makes sense. Sorry for the trouble (actually, it took me a bit to work out /dev/sysmouse as it was until I thought to look in MAKEDEV from -current rather than the one I had installed which mentioned nothing). Lacking man page for moused didn't help. :) Thanks for the pointers. From owner-freebsd-current Tue Oct 15 07:29:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA11973 for current-outgoing; Tue, 15 Oct 1996 07:29:24 -0700 (PDT) Received: from onyx.interactive.net (ritz@onyx.interactive.net [208.192.224.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA11968 for ; Tue, 15 Oct 1996 07:29:22 -0700 (PDT) Received: (from ritz@localhost) by onyx.interactive.net (8.7.5/8.7.3) id KAA09364 for freebsd-current@freebsd.org; Tue, 15 Oct 1996 10:29:21 -0400 (EDT) From: Chris Mauritz Message-Id: <199610151429.KAA09364@onyx.interactive.net> Subject: SUBSCRIBE To: freebsd-current@freebsd.org Date: Tue, 15 Oct 1996 10:29:20 -0400 (EDT) X-Mailer: ELM [version 2.4 PL25] 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 SUBSCRIBE -- Christopher Mauritz | For info on internet access: ritz@interactive.net | finger/mail info@interactive.net OR IBS Interactive, Inc. | http://www.interactive.net/ From owner-freebsd-current Tue Oct 15 09:13:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA16605 for current-outgoing; Tue, 15 Oct 1996 09:13:23 -0700 (PDT) Received: from inga.augusta.de (root@inga.augusta.de [193.175.23.65]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA16596 for ; Tue, 15 Oct 1996 09:13:12 -0700 (PDT) Received: from rabbit by inga.augusta.de with uucp (Smail3.1.29.1 #1) id m0vDBwN-004copC; Tue, 15 Oct 96 18:01 MET DST Received: by rabbit.augusta.de (Smail3.1.29.1 #1) id m0vCXjU-000A9KC; Sun, 13 Oct 96 23:06 MET DST Message-Id: Date: Sun, 13 Oct 96 23:06 MET DST X-Newsreader: knews 0.9.6 Organization: Privat Site running FreeBSD References: <199610130044.KAA09569@asstdc.scgt.oz.au> From: shanee@rabbit.augusta.de (Andreas Kohout) Subject: Re: ps axl | grep X-Original-Newsgroups: muc.lists.freebsd.current In-Reply-To: <199610130044.KAA09569@asstdc.scgt.oz.au> To: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199610130044.KAA09569@asstdc.scgt.oz.au>, imb@scgt.oz.au (michael butler) writes: > > bug or feature? > > feature .. man ps(1) .. specifically the '-w' option .. 'ps axlww' will do > what you want, Thanks to you and all others ... -- Greeting, Andy running FreeBSD-current --------------------------------------------------------------------------- From owner-freebsd-current Tue Oct 15 10:24:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA22061 for current-outgoing; Tue, 15 Oct 1996 10:24:16 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA22053 for ; Tue, 15 Oct 1996 10:24:12 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id SAA00195 for ; Tue, 15 Oct 1996 18:34:32 +0200 (MET DST) To: current@freebsd.org Subject: device driver open/close inconsistency Reply-to: phk@freebsd.org Date: Tue, 15 Oct 1996 18:34:31 +0200 Message-ID: <193.845397271@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Why do we call a device-driver->open() on all opens, but only ->close() once on the last close ? -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Tue Oct 15 12:29:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02458 for current-outgoing; Tue, 15 Oct 1996 12:29:15 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA02453; Tue, 15 Oct 1996 12:29:12 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.6/8.7.3) with SMTP id MAA00334; Tue, 15 Oct 1996 12:27:42 -0700 (PDT) Message-ID: <3263E52F.59E2B600@whistle.com> Date: Tue, 15 Oct 1996 12:25:35 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: phk@freebsd.org CC: current@freebsd.org Subject: Re: device driver open/close inconsistency References: <193.845397271@critter.tfs.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp wrote: > > Why do we call a device-driver->open() on all opens, but only ->close() > once on the last close ? > > -- > Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. > http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. > whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. > Future will arrive by its own means, progress not so. history? the call on last close semantic has been a part of Unx for a long time and takes into account that FORK'd processes would call it twice and have only called the open once..... From owner-freebsd-current Tue Oct 15 12:30:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02582 for current-outgoing; Tue, 15 Oct 1996 12:30:29 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA02576; Tue, 15 Oct 1996 12:30:25 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA00828; Tue, 15 Oct 1996 12:29:54 -0700 (PDT) Received: from crab.whistle.com(207.76.205.112) by whistle.com via smap (V1.3) id sma000824; Tue Oct 15 12:29:48 1996 Received: (from ambrisko@localhost) by crab.whistle.com (8.7.6/8.6.12) id MAA13270; Tue, 15 Oct 1996 12:29:15 -0700 (PDT) From: Doug Ambrisko Message-Id: <199610151929.MAA13270@crab.whistle.com> Subject: Re: non-console mode.. In-Reply-To: <199610150920.LAA13315@ra.dkuug.dk> from "sos@freebsd.org" at "Oct 15, 96 11:20:28 am" To: sos@freebsd.org Date: Tue, 15 Oct 1996 12:29:15 -0700 (PDT) Cc: msmith@atrad.adelaide.edu.au, julian@whistle.com, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk sos@freebsd.org writes: | In reply to Michael Smith who wrote: | > | > There's no need for either work or violent objections - the 'no console' | > case is already supported. Look at i386/i386/cons.c. | > | > > > p.s. yes there are good reasons for doing this :) | > > | > > Such as ?? ???? | > | > The box his employers make that doesn't have a console? | | I'm sure I can be talked into makeing a consoledriver for their | little LCD display :) Actually nothing is needed to do that ... as I found out by a programming mistake. It was a bit strange seeing BSD boot messages on the LCD. The only catch is trying to enter in text on the keypad! Doug A. From owner-freebsd-current Tue Oct 15 13:26:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA05997 for current-outgoing; Tue, 15 Oct 1996 13:26:25 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA05990 for ; Tue, 15 Oct 1996 13:26:19 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id GAA21446; Wed, 16 Oct 1996 06:22:23 +1000 Date: Wed, 16 Oct 1996 06:22:23 +1000 From: Bruce Evans Message-Id: <199610152022.GAA21446@godzilla.zeta.org.au> To: current@freebsd.org, phk@critter.tfs.com Subject: Re: device driver open/close inconsistency Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Why do we call a device-driver->open() on all opens, but only ->close() >once on the last close ? Because it's easier to count references in vfs than in hundreds of drivers. The device close function would also need to be called on all dup()s and implicit dup()s for fork()s to give it a chance of counting references. There is also an extra reference for controlling terminals. There are also complications for /dev/tty. Unfortunately, it's hard to count references properly in vfs too: Bug 1: the reference count is incremented before calling the device open function, so processes sleeping in open are effectively counted as successful opens. Suppose there is a process sleeping in open and another process opens the device, does some ioctls to mess up the device state, and closes the device. Then it is necessary to call the device close function to clean up and kick the process sleeping in open, but the device close function is never called because the reference count is always >= 1. I believe this is (mis)handled in some versions of **ix by not allowing processes to sleep in open when another open of the same device to complete. This causes other problems. O_NONBLOCK is per-open, so I think it is wrong to let a !O_NOBLOCK open succeed in the presences of the blocking condition just because another process has done a successful open using O_NOBLOCK. Bug 2: It is difficult to get rid of controlling terminals. In 4.4Lite, exiting was the only way. Thus device close functions for controlliing terminals were never called until exit. In 4.4Lite2 and most versions of FreeBSD-2.x, the controlling terminal can be changed using TIOCSCTTY. Bruce From owner-freebsd-current Tue Oct 15 13:30:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA06277 for current-outgoing; Tue, 15 Oct 1996 13:30:23 -0700 (PDT) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA06268; Tue, 15 Oct 1996 13:30:19 -0700 (PDT) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id PAA03162; Tue, 15 Oct 1996 15:24:20 -0500 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma003149; Tue Oct 15 15:24:10 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id PAA18876; Tue, 15 Oct 1996 15:24:18 -0500 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.7.6/8.6.12) with ESMTP id PAA14536; Tue, 15 Oct 1996 15:23:51 -0500 (CDT) Message-Id: <199610152023.PAA14536@jake.lodgenet.com> X-Mailer: exmh version 1.6.9 8/22/96 To: phk@freebsd.org cc: current@freebsd.org Subject: Re: device driver open/close inconsistency In-reply-to: Your message of "Tue, 15 Oct 1996 18:34:31 +0200." <193.845397271@critter.tfs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Oct 1996 15:23:50 -0500 From: "Eric L. Hernes" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp writes: > >Why do we call a device-driver->open() on all opens, but only ->close() >once on the last close ? > That's a good one. Near as I can tell it's been that way since the epoch ;-) The only hint of an explanation I can find is in _Writing Device Drivers: Tutorial and Reference_; Burke, et al. Sect 3.5.2 that says: The `open' interface is called every time that any user initiates an action that invokes the `open' system call. The `close' interface, however, is called only when the last user initiates an action that closes the device. The reason for this difference is to allow the driver to take some special action when there is no work left to perform. I'd say that's a pretty weak explanation though. You could do the same (and more) with a simple semaphore or reference count. >-- >Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. >http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. >whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc >. >Future will arrive by its own means, progress not so. > eric. From owner-freebsd-current Tue Oct 15 13:52:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07847 for current-outgoing; Tue, 15 Oct 1996 13:52:20 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA07840 for ; Tue, 15 Oct 1996 13:52:16 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA11150 for ; Tue, 15 Oct 1996 22:51:14 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA15388 for freebsd-current@FreeBSD.org; Tue, 15 Oct 1996 22:51:14 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.6/8.6.9) id WAA13617 for freebsd-current@FreeBSD.org; Tue, 15 Oct 1996 22:44:02 +0200 (MET DST) From: J Wunsch Message-Id: <199610152044.WAA13617@uriah.heep.sax.de> Subject: Re: device driver open/close inconsistency To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 15 Oct 1996 22:44:02 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <193.845397271@critter.tfs.com> from Poul-Henning Kamp at "Oct 15, 96 06:34:31 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Poul-Henning Kamp wrote: > Why do we call a device-driver->open() on all opens, but only ->close() > once on the last close ? You can open it multiple times (it stays open meanwhile), but only close it once. Certainly, it's mostly history. It made the console code (not the syscons/pcvt/sio stuff, just the real console) rather hard. Some people might still remember the ``syscons freezes during the nightly syslogd restart'' syndrome... Julian's comment regarding forks is certainly also part of the game. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Oct 15 14:28:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09736 for current-outgoing; Tue, 15 Oct 1996 14:28:00 -0700 (PDT) Received: from rosie.scsn.net (scsn.net [206.25.246.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA09717 for ; Tue, 15 Oct 1996 14:27:42 -0700 (PDT) Received: from rhiannon.scsn.net (cola60.scsn.net [206.25.247.60]) by rosie.scsn.net (post.office MTA v2.0 0813 ID# 0-13529) with ESMTP id AAA208; Tue, 15 Oct 1996 17:26:27 -0400 Received: (from root@localhost) by rhiannon.scsn.net (8.7.6/8.6.12) id RAA00691; Tue, 15 Oct 1996 17:27:38 -0400 (EDT) From: "Donald J. Maddox" Message-Id: <199610152127.RAA00691@rhiannon.scsn.net> Subject: Re: Bug with moused and XFree86 In-Reply-To: <199610150128.SAA12417@freefall.freebsd.org> from "Justin T. Gibbs" at "Oct 14, 96 06:28:05 pm" To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Tue, 15 Oct 1996 17:27:38 -0400 (EDT) Cc: current@FreeBSD.org 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 > >/dev/sysmouse? > > > >The installer links it to /dev/mouse, actually. > > > > Jordan > > /dev/sysmouse, /dev/mouse linked to /dev/sysmouse, same difference. > The point is to be using the device managed by moused, not the hardware > device. > > -- > Justin T. Gibbs > =========================================== > FreeBSD: Turning PCs into workstations > =========================================== I must be missing something here... I normally use /dev/cuaa0 for my 'mouseman' type mouse. After reading this thread, I tried using /dev/sysmouse instead, but then I don't get any mouse events at all. Neither moused nor X see the mouse, and 'cat < /dev/sysmouse' while moving the mouse shows nothing. However, all of the above work just fine with /dev/cuaa0... What am I doing wrong? -- Donald J. Maddox (dmaddox@scsn.net) From owner-freebsd-current Tue Oct 15 14:41:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA10573 for current-outgoing; Tue, 15 Oct 1996 14:41:42 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA10562; Tue, 15 Oct 1996 14:41:38 -0700 (PDT) Message-Id: <199610152141.OAA10562@freefall.freebsd.org> To: dmaddox@scsn.net cc: current@FreeBSD.org Subject: Re: Bug with moused and XFree86 In-reply-to: Your message of "Tue, 15 Oct 1996 17:27:38 EDT." <199610152127.RAA00691@rhiannon.scsn.net> Date: Tue, 15 Oct 1996 14:41:38 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I must be missing something here... I normally use /dev/cuaa0 for >my 'mouseman' type mouse. After reading this thread, I tried using >/dev/sysmouse instead, but then I don't get any mouse events at all. >Neither moused nor X see the mouse, and 'cat < /dev/sysmouse' while >moving the mouse shows nothing. However, all of the above work just >fine with /dev/cuaa0... > > What am I doing wrong? You should be running moused on /dev/cuaa0 telling it you have a 'mouseman' mouse. You should then tell X that you have a mouse systems mouse on /dev/sysmouse. Having both moused and X using the same device is bound for trouble since you don't know which of them will get each event. >-- > > > Donald J. Maddox > (dmaddox@scsn.net) > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Oct 15 14:52:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA11343 for current-outgoing; Tue, 15 Oct 1996 14:52:54 -0700 (PDT) Received: from rosie.scsn.net (scsn.net [206.25.246.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA11328 for ; Tue, 15 Oct 1996 14:52:44 -0700 (PDT) Received: from rhiannon.scsn.net (cola60.scsn.net [206.25.247.60]) by rosie.scsn.net (post.office MTA v2.0 0813 ID# 0-13529) with ESMTP id AAA139; Tue, 15 Oct 1996 17:51:56 -0400 Received: (from root@localhost) by rhiannon.scsn.net (8.7.6/8.6.12) id RAA00793; Tue, 15 Oct 1996 17:53:07 -0400 (EDT) From: "Donald J. Maddox" Message-Id: <199610152153.RAA00793@rhiannon.scsn.net> Subject: Re: Bug with moused and XFree86 In-Reply-To: <199610152141.OAA10562@freefall.freebsd.org> from "Justin T. Gibbs" at "Oct 15, 96 02:41:38 pm" To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Tue, 15 Oct 1996 17:53:06 -0400 (EDT) Cc: current@FreeBSD.org 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 > > I must be missing something here... I normally use /dev/cuaa0 for > >my 'mouseman' type mouse. After reading this thread, I tried using > >/dev/sysmouse instead, but then I don't get any mouse events at all. > >Neither moused nor X see the mouse, and 'cat < /dev/sysmouse' while > >moving the mouse shows nothing. However, all of the above work just > >fine with /dev/cuaa0... > > > > What am I doing wrong? > > You should be running moused on /dev/cuaa0 telling it you have a > 'mouseman' mouse. You should then tell X that you have a mouse systems > mouse on /dev/sysmouse. Having both moused and X using the same > device is bound for trouble since you don't know which of them will > get each event. > Okay, now I see! :-) Thanks for the help... I have been avoiding using moused at all, since it was clearly fighting with X over the pointer. Now I'll finally be able to use both! > -- > Justin T. Gibbs > =========================================== > FreeBSD: Turning PCs into workstations > =========================================== > -- Donald J. Maddox (dmaddox@scsn.net) From owner-freebsd-current Tue Oct 15 14:55:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA11545 for current-outgoing; Tue, 15 Oct 1996 14:55:43 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA11540 for ; Tue, 15 Oct 1996 14:55:38 -0700 (PDT) Received: from localhost (scrappy@localhost) by quagmire.ki.net (8.7.5/8.7.5) with SMTP id RAA19804 for ; Tue, 15 Oct 1996 17:55:50 -0400 (EDT) Date: Tue, 15 Oct 1996 17:55:49 -0400 (EDT) From: "Marc G. Fournier" To: current@freebsd.org Subject: make -j# under 2.2-CURRENT... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... I decided to play around with this -j# option with make to compile the kernel, and found that -j2 and -j3 are worse then no -j at all: no -j: 1189.676u 105.610s 24:38.83 -j2: 1214.136u 121.934s 24:37.94 -j3: 1232.782u 127.352s 25:46.48 This is on a 486DX4-100 with 32Meg of RAM, using the same kernel sources each time... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Tue Oct 15 15:50:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA14440 for current-outgoing; Tue, 15 Oct 1996 15:50:37 -0700 (PDT) Received: from rosie.scsn.net (scsn.net [206.25.246.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA14418 for ; Tue, 15 Oct 1996 15:50:20 -0700 (PDT) Received: from rhiannon.scsn.net (cola79.scsn.net [206.25.247.79]) by rosie.scsn.net (post.office MTA v2.0 0813 ID# 0-13529) with ESMTP id AAA190; Tue, 15 Oct 1996 18:49:24 -0400 Received: (from root@localhost) by rhiannon.scsn.net (8.7.6/8.6.12) id SAA00373; Tue, 15 Oct 1996 18:50:34 -0400 (EDT) From: "Donald J. Maddox" Message-Id: <199610152250.SAA00373@rhiannon.scsn.net> Subject: Re: Bug with moused and XFree86 In-Reply-To: <199610152153.RAA00793@rhiannon.scsn.net> from "Donald J. Maddox" at "Oct 15, 96 05:53:06 pm" To: dmaddox@scsn.net Date: Tue, 15 Oct 1996 18:50:33 -0400 (EDT) Cc: current@FreeBSD.org 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 > > You should be running moused on /dev/cuaa0 telling it you have a > > 'mouseman' mouse. You should then tell X that you have a mouse systems > > mouse on /dev/sysmouse. Having both moused and X using the same > > device is bound for trouble since you don't know which of them will > > get each event. > > > > Okay, now I see! :-) Thanks for the help... I have been avoiding > using moused at all, since it was clearly fighting with X over the > pointer. Now I'll finally be able to use both! > Forgive me for replying to my own message, but it looks like I spoke too soon... Following your (Jason's) advice above, moused works ok, but... When I start the Xserver, the pointer appears at the center of the screen, as always. The first time I move the mouse, however, the pointer goes to the upper left corner of the screen and pretty much stays there. It moves when I move the mouse, but it pretty much stays locked up in that corner. In short, X is now getting mouse events, but obviously the wrong ones. Again, my mouse works fine when /dev/mouse is a link to /dev/cuaa0, I just cannot use X and moused concurrently. For clarity, here is the situation: From /etc/XF86Config: ----------------------------------------------------------------- Section "Pointer" Protocol "MouseMan" Device "/dev/mouse" ----------------------------------------------------------------- From /etc/sysconfig: ----------------------------------------------------------------- # Set to # {microsoft|mousesystems|mmseries|logitech|busmouse|mouseman|ps/2|mmhittab} # to activate system mouse cursor support (or NO for none) # Use 'vidcontrol -m on' command to activate it on particular screen mousedtype=mouseman ############## Next block activated only if mousetype != NO ################ # Set to your mouse port (required) # Use real device here, because /dev/mouse usually linked with /dev/sysmouse mousedport=/dev/cuaa0 # Moused options: # -s: 9600 baud mouse # -c: enable ChordMiddle # see moused usage info for complete options list mousedflags="" ------------------------------------------------------------------- From /dev: #ls -l /dev/sysmouse crw------- 1 root wheel 12, 128 Oct 15 18:19 /dev/sysmouse # ls -l /dev/consolectl crw------- 1 root wheel 12, 255 Oct 15 17:18 /dev/consolectl (/dev/mouse is a symbolic link to /dev/sysmouse) -------------------------------------------------------------------- What's wrong here? -- Donald J. Maddox (dmaddox@scsn.net) From owner-freebsd-current Tue Oct 15 15:52:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA14571 for current-outgoing; Tue, 15 Oct 1996 15:52:54 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA14563; Tue, 15 Oct 1996 15:52:51 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.6/8.7.3) with SMTP id PAA03416; Tue, 15 Oct 1996 15:49:40 -0700 (PDT) Message-ID: <32641484.41C67EA6@whistle.com> Date: Tue, 15 Oct 1996 15:47:32 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Michael Smith CC: sos@freebsd.org, current@freebsd.org Subject: Re: non-console mode.. References: <199610150819.RAA21035@genesis.atrad.adelaide.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith wrote: > > sos@FreeBSD.org stands accused of saying: > > > > In reply to Julian Elischer who wrote: > > > > > > I need to make the system run with it's console disabled.. > > > in other words.. > > > the device exists, bu tut acts as if there is no console > > > > > > if anyone has violent objections, I'd like to hear of them before > > > I start work on this > > > > Maybe. > > There's no need for either work or violent objections - the 'no console' > case is already supported. Look at i386/i386/cons.c. I'm very familiar with that.. In actual fact if you had no console, the system would crash. I committed a patch to fix that. but that is not what I want.. What I want to add (I have working code) is the ability to have a console-able device exist, but have that device enabled/disabled from acting as a console another way of thinking of it would be to "Mute" the console device. output still goes to dmesg and syslog, but not out to the physical device (e.g. sio0) which can then be used for other things. for debugging, the 'switch' can be thrown and teh console reactivated. but by default, it's not on. > > > > p.s. yes there are good reasons for doing this :) > > > > Such as ?? ???? not wasting a serial port on a console whne you have a better use for it...? From owner-freebsd-current Tue Oct 15 15:56:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA14770 for current-outgoing; Tue, 15 Oct 1996 15:56:40 -0700 (PDT) Received: from rosie.scsn.net (scsn.net [206.25.246.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA14762 for ; Tue, 15 Oct 1996 15:56:38 -0700 (PDT) Received: from rhiannon.scsn.net (cola79.scsn.net [206.25.247.79]) by rosie.scsn.net (post.office MTA v2.0 0813 ID# 0-13529) with ESMTP id AAA61; Tue, 15 Oct 1996 18:55:43 -0400 Received: (from root@localhost) by rhiannon.scsn.net (8.7.6/8.6.12) id SAA00399; Tue, 15 Oct 1996 18:56:54 -0400 (EDT) From: "Donald J. Maddox" Message-Id: <199610152256.SAA00399@rhiannon.scsn.net> Subject: Re: Bug with moused and XFree86 In-Reply-To: <199610152153.RAA00793@rhiannon.scsn.net> from "Donald J. Maddox" at "Oct 15, 96 05:53:06 pm" To: dmaddox@scsn.net Date: Tue, 15 Oct 1996 18:56:53 -0400 (EDT) Cc: current@FreeBSD.org 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 > > You should be running moused on /dev/cuaa0 telling it you have a > > 'mouseman' mouse. You should then tell X that you have a mouse systems > > mouse on /dev/sysmouse. Having both moused and X using the same > > device is bound for trouble since you don't know which of them will > > get each event. > > > > Okay, now I see! :-) Thanks for the help... I have been avoiding > using moused at all, since it was clearly fighting with X over the > pointer. Now I'll finally be able to use both! Forgive me for replying to my own message, but it looks like I spoke too soon... Following your (Jason's) advice above, moused works ok, but... When I start the Xserver, the pointer appears at the center of the screen, as always. The first time I move the mouse, however, the pointer goes to the upper left corner of the screen and pretty much stays there. It moves when I move the mouse, but it pretty much stays locked up in that corner. In short, X is now getting mouse events, but obviously the wrong ones. Again, my mouse works fine when /dev/mouse is a link to /dev/cuaa0, I just cannot use X and moused concurrently. For clarity, here is the situation: From /etc/XF86Config: ----------------------------------------------------------------- Section "Pointer" Protocol "MouseMan" Device "/dev/mouse" ----------------------------------------------------------------- From /etc/sysconfig: ----------------------------------------------------------------- # Set to # {microsoft|mousesystems|mmseries|logitech|busmouse|mouseman|ps/2|mmhittab} # to activate system mouse cursor support (or NO for none) # Use 'vidcontrol -m on' command to activate it on particular screen mousedtype=mouseman ############## Next block activated only if mousetype != NO ################ # Set to your mouse port (required) # Use real device here, because /dev/mouse usually linked with /dev/sysmouse mousedport=/dev/cuaa0 # Moused options: # -s: 9600 baud mouse # -c: enable ChordMiddle # see moused usage info for complete options list mousedflags="" ------------------------------------------------------------------- From /dev: #ls -l /dev/sysmouse crw------- 1 root wheel 12, 128 Oct 15 18:19 /dev/sysmouse # ls -l /dev/consolectl crw------- 1 root wheel 12, 255 Oct 15 17:18 /dev/consolectl (/dev/mouse is a symbolic link to /dev/sysmouse) -------------------------------------------------------------------- What's wrong here? -- Donald J. Maddox (dmaddox@scsn.net) From owner-freebsd-current Tue Oct 15 16:00:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA14975 for current-outgoing; Tue, 15 Oct 1996 16:00:06 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA14965; Tue, 15 Oct 1996 16:00:03 -0700 (PDT) Message-Id: <199610152300.QAA14965@freefall.freebsd.org> To: dmaddox@scsn.net cc: current@FreeBSD.org Subject: Re: Bug with moused and XFree86 In-reply-to: Your message of "Tue, 15 Oct 1996 18:50:33 EDT." <199610152250.SAA00373@rhiannon.scsn.net> Date: Tue, 15 Oct 1996 16:00:02 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > From /etc/XF86Config: >----------------------------------------------------------------- > Section "Pointer" > Protocol "MouseMan" > Device "/dev/mouse" >----------------------------------------------------------------- > What's wrong here? This should say "MouseSystems". Moused makes all mice look like MouseSystems mice. > >-- > > > Donald J. Maddox > (dmaddox@scsn.net) > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Oct 15 16:24:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA16255 for current-outgoing; Tue, 15 Oct 1996 16:24:55 -0700 (PDT) Received: from rosie.scsn.net (scsn.net [206.25.246.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA16245 for ; Tue, 15 Oct 1996 16:24:50 -0700 (PDT) Received: from rhiannon.scsn.net (cola79.scsn.net [206.25.247.79]) by rosie.scsn.net (post.office MTA v2.0 0813 ID# 0-13529) with ESMTP id AAA86; Tue, 15 Oct 1996 19:23:42 -0400 Received: (from root@localhost) by rhiannon.scsn.net (8.7.6/8.6.12) id TAA00547; Tue, 15 Oct 1996 19:24:52 -0400 (EDT) From: "Donald J. Maddox" Message-Id: <199610152324.TAA00547@rhiannon.scsn.net> Subject: Re: Bug with moused and XFree86 In-Reply-To: <199610152300.QAA14965@freefall.freebsd.org> from "Justin T. Gibbs" at "Oct 15, 96 04:00:02 pm" To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Tue, 15 Oct 1996 19:24:51 -0400 (EDT) Cc: current@FreeBSD.org 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 > > From /etc/XF86Config: > >----------------------------------------------------------------- > > Section "Pointer" > > Protocol "MouseMan" > > Device "/dev/mouse" > >----------------------------------------------------------------- > > What's wrong here? > > This should say "MouseSystems". Moused makes all mice look like > MouseSystems mice. > Ok, that did the trick! Thanks for all the help, Jason. BTW... Why is there no manpage for moused? Is there anywhere (other than the syscons source, of course) where this is documented? If not, I don't think this is the last time we will see bandwidth wasted on this... -- Donald J. Maddox (dmaddox@scsn.net) From owner-freebsd-current Tue Oct 15 16:40:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA18038 for current-outgoing; Tue, 15 Oct 1996 16:40:21 -0700 (PDT) Received: from red.jnx.com (red.jnx.com [208.197.169.254]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA18029; Tue, 15 Oct 1996 16:40:14 -0700 (PDT) Received: from red.jnx.com (localhost.jnx.com [127.0.0.1]) by red.jnx.com (8.7.6/8.7.3) with ESMTP id QAA20545; Tue, 15 Oct 1996 16:39:39 -0700 (PDT) Message-Id: <199610152339.QAA20545@red.jnx.com> To: dyson@freebsd.org cc: current@freebsd.org Subject: vm deallocate crash (look familiar?) Date: Tue, 15 Oct 1996 16:39:39 -0700 From: Paul Traina Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Here's the latest crash, I've got kernel compiled with -g and core file available if interested. This is -current as of yesterday midmorning. Paul _Debugger(f0118016) at _Debugger+0x36 _panic(f01bf5dd,f5bade10,0,f1668800,efbffefc) at _panic+0x5a _vm_object_deallocate(f1669d00) at _vm_object_deallocate+0x22 _vm_map_delete(f1668800,0,efbfe000,f1668800,f1662e00) at _vm_map_delete+0x1c9 _vm_map_remove(f1668800,0,efbfe000,f1668864,0,efbfe000) at _vm_map_remove+0x76 _exit1(f1662e00,8a,f1662e00,f56b9128,efbfff8c) at _exit1+0x113 _sigexit(f1662e00,a,c,f1662e00,efbfffbc) at _sigexit+0x80 _postsig(a) at _postsig+0x8e _trap(27,27,fffffffd,24f00,efbfdab8) at _trap+0x4bc calltrap() at calltrap+0x15 --- trap 12, eip = 0x803de20, ebp = 0xefbfdab8 --- db> panic panic: from debugger dumping to dev 401, offset 87216 ... [ preserving 0x2aa78 bytes of kernel symbol table ] BIOS basemem (639K) != RTC basemem (640K), setting to BIOS value 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-CURRENT #0: Mon Oct 14 14:03:26 PDT 1996 pst@red.jnx.com:/a/src/sys/compile/JNX.debug Calibrating clock(s) relative to mc146818A clock... i586 clock: 132955552 Hz, i8254 clock: 1193193 Hz CPU: Pentium (132.95-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30203904 (29496K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 2 on pci0:7:0 chip2 rev 2 on pci0:7:1 ahc0 rev 3 int a irq 10 on pci0:13 ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs (ahc0:0:0): "QUANTUM FIREBALL1280S 630C" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 1222MB (2503872 512 byte sectors) (ahc0:4:0): "SONY CD-ROM CD/dev/rsd0s2f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) /dev/rsd0s2f: BLK(S) MISSING IN BIT MAPS (SALVAGED) /dev/rsd0s2f: SUMMARY INFORMATION BAD (SALVAGED) /dev/rsd0s2f: CLEAN FLAG NOT SET IN SUPERBLOCK (FIXED) /dev/rsd0s2f: 41341 files, 359889 used, 519430 free (5686 frags, 64218 blocks, 0.6% fragmentation) /dev/rsd0s2e: CLEAN FLAG NOT SET IN SUPERBLOCK (FIXED) /dev/rsd0s2e: 140 files, 990 used, 28737 free (113 frags, 3578 blocks, 0.4% fragmentation) de0: flags=8843 mtu 1500 inet 208.197.169.238 netmask 0xffffff00 broadcast 208.197.169.255 ether 00:00:c0:bf:0d:dc lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 add net 224.0.0.0: gateway 208.197.169.238 starting routing daemon: routed. clearing /tmp checking for core dump...savecore: reboot after panic: vm_object_deallocate: object deallocated too many times savecore: system went down at Tue Oct 15 14:58:27 1996 savecore: /var/crash/bounds: No such file or directory savecore: writing core to /var/crash/vmcore.0 32768K 31744K 30720K 29696K 28672K 27648K 26624K 25600K 24576K 23552K 22528K 21504K 20480K 19456K 18432K 17408K 16384K 15360K 14336K 13312K 12288K 11264K 10240K 9216K 8192K 7168K 6144K 5120K 4096K 3072K 2048K 1024Ksavecore: writing kernel to /var/crash/kernel.0 recording kernel -c changes starting system daemons: syslogd. starting network daemons: tickadj ntpdate portmap ypbind mountd nfsd nfsiod amd inetd. setting ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib standard daemons: cron printer sendmail. enabling FreeBSD/i386 options:. configuring syscons:. . Local package startup: sshd xdm zhm. starting local daemons:. From owner-freebsd-current Tue Oct 15 18:11:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA23489 for current-outgoing; Tue, 15 Oct 1996 18:11:33 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA23484 for ; Tue, 15 Oct 1996 18:11:30 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id TAA08069; Tue, 15 Oct 1996 19:11:26 -0600 (MDT) Date: Tue, 15 Oct 1996 19:11:26 -0600 (MDT) Message-Id: <199610160111.TAA08069@rocky.mt.sri.com> From: Nate Williams To: current@freebsd.org Subject: BSDI 3.0 feature list Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a bit off-topic, but I find it ironic that BSDI 3.0 contains almost everything FreeBSD -current had (or stuff we've had for quite a while now). We're only missing some of the 'built-in' WWW stuff which can be gotten as aftermarket add-ons for FreeBSD, or their 'work-in-progress' stuff which NetBSD already provides. ------- From: Doug Urner To: bsdi-users@bsdi.com Subject: BSD/OS 3.0 New Features and Improvements Date: Tue, 15 Oct 1996 17:19:22 -0700 We've got our next release, 3.0, pretty well ironed out and beta testing is under way. We expect to be shipping to customers by the end of the year. When 3.0 ships all customers with current support contracts and those who purchased 2.1 within the last 60 days will receive the 3.0 release at no charge. This might be a good time to think about renewing that lapsed support contract :-) The 3.0 CD-ROM will include a number of third party packages, some demos and some fully functional versions. We're still ironing out the details, when this is complete I'll send the info to the list. Anyway, here's the short list of what's in 3.0. There may be a few changes as beta feedback comes back, but this should be pretty close. If you don't see the feature that you were hoping for now would be a great time to tell us. Planning for the 3.1 release is underway and now is when we can really use the input. Doug - -- Douglas L. Urner, dlu@bsdi.com - --8<----------------------------------------------------------------- o System Administration: Web-based system administration interface: modular, script-driven, new components easily added NIS client support New "getty daemon" manages modems, simplifies PPP dial-out o Upgrade to 4.4BSD-Lite2 o Network Services: Squid caching web proxy Improved virtual hosting (Telnet, FTP in addition to HTTP) Fully integrated RADIUS support Kerberos support now integrated, available to international customers (encryption, including rlogin/telnet, still separate) IPX gateway with five client seats SNMP tools (scotty, tkined, tknm) o Network: Improved defenses against denial of service attacks Kernel level packet filter Further TCP performance improvements TCP path MTU discovery PPP enhancements: - PAP and CHAP authentication support - Multi-link PPP Tunnel driver Improved statistics o Filesystem Support: Filesystem clean flag, no check needed after clean shutdown Long file name support for MS-DOS filesystem o Hardware Support: SCSI enhancements: - Fast and Wide SCSI support on all capable host adapters - Tagged queuing - Generic device interface, simplifies support of devices like scanners Striped/concatenated disk partitions Simplified configuration of network interfaces Dynamically-loadable keyboard map New and/or updated drivers: - BusLogic Flashpoint SCSI host adapters - DEC, SMC 10/100 MB Ethernet support - DPT - Intel EtherExpress Pro/100B - Quick-Cam - SDL N2pci - Stallion serial multi-port driver PCMCIA and power management support o Programming Support: Java Development Kit (JDK) ported to BSD/OS POSIX Threads Support Thread Safe C Library GDB version 4.16 Electric Fence 2.0.5 malloc() Debugger Latest Perl, tk, tcl read()/write() and mmap() now coherent o Work In Progress: While we're at it, here is a short run down of some of the work in progress for future releases. Both the SPARC and PowerPC ports are well underway. Both ports are targeted at the "embedded" systems market. If you're interested in using either of these ports in an "embedded" product please contact Randy Brem, VP of Embedded Systems Sales, at +1 408.842.9020. On the MP front we have a "giant lock" kernel running on dual Pentiums in our lab. MP development is one of the main priorities for the next year. Development of an NFS lock manager is also a high priority. I'm sure you'll let me know what else needs to be on the list :-) ------- end ------- From owner-freebsd-current Tue Oct 15 18:24:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA24112 for current-outgoing; Tue, 15 Oct 1996 18:24:45 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA24107; Tue, 15 Oct 1996 18:24:42 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id KAA27554; Wed, 16 Oct 1996 10:54:33 +0930 From: Michael Smith Message-Id: <199610160124.KAA27554@genesis.atrad.adelaide.edu.au> Subject: Re: non-console mode.. To: julian@whistle.com (Julian Elischer) Date: Wed, 16 Oct 1996 10:54:33 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, sos@freebsd.org, current@freebsd.org In-Reply-To: <32641484.41C67EA6@whistle.com> from "Julian Elischer" at Oct 15, 96 03:47:32 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Julian Elischer stands accused of saying: > > > > There's no need for either work or violent objections - the 'no console' > > case is already supported. Look at i386/i386/cons.c. > > I'm very familiar with that.. > > In actual fact if you had no console, the system would crash. > I committed a patch to fix that. > but that is not what I want.. > What I want to add (I have working code) is the ability to > have a console-able device exist, but have that device > enabled/disabled from acting as a console So use the null console entry, and then the 'xconsole' technique for grabbing it to an fd. (TIOCCONS). -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Oct 15 18:34:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA24542 for current-outgoing; Tue, 15 Oct 1996 18:34:51 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA24533 for ; Tue, 15 Oct 1996 18:34:48 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA27630; Wed, 16 Oct 1996 11:04:12 +0930 From: Michael Smith Message-Id: <199610160134.LAA27630@genesis.atrad.adelaide.edu.au> Subject: Re: Bug with moused and XFree86 To: dmaddox@scsn.net Date: Wed, 16 Oct 1996 11:04:11 +0930 (CST) Cc: gibbs@freefall.freebsd.org, current@FreeBSD.org In-Reply-To: <199610152324.TAA00547@rhiannon.scsn.net> from "Donald J. Maddox" at Oct 15, 96 07:24:51 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Donald J. Maddox stands accused of saying: > > Ok, that did the trick! Thanks for all the help, Jason. > BTW... Why is there no manpage for moused? Is there anywhere > (other than the syscons source, of course) where this is > documented? If not, I don't think this is the last time we > will see bandwidth wasted on this... As the original author of moused (no complaints please), I hereby delegate the authoring of the moused manpage, herafter to be referred to as moused.1, to Donald J. Maddox. Donald, please contact Soren and me when you have a planned release date for this important piece of documentation. > Donald J. Maddox 8) -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Oct 15 18:54:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA25521 for current-outgoing; Tue, 15 Oct 1996 18:54:45 -0700 (PDT) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA25515; Tue, 15 Oct 1996 18:54:44 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199610160154.SAA25515@freefall.freebsd.org> Subject: Re: BSDI 3.0 feature list To: nate@mt.sri.com (Nate Williams) Date: Tue, 15 Oct 1996 18:54:44 -0700 (PDT) Cc: current@freebsd.org In-Reply-To: <199610160111.TAA08069@rocky.mt.sri.com> from "Nate Williams" at Oct 15, 96 07:11:26 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Nate Williams wrote: > > This is a bit off-topic, but I find it ironic that BSDI 3.0 contains > almost everything FreeBSD -current had (or stuff we've had for quite a > while now). We're only missing some of the 'built-in' WWW stuff which > can be gotten as aftermarket add-ons for FreeBSD, or their > 'work-in-progress' stuff which NetBSD already provides. hmm....a remarkable amount of overlap in the list. jmb > 4.4BSD-Lite2 > Fully integrated RADIUS support > Kerberos support now integrated, available to international customers > (encryption, including rlogin/telnet, still separate) > IPX gateway with five client seats > Improved defenses against denial of service attacks > Kernel level packet filter > Further TCP performance improvements > Tunnel driver > Filesystem clean flag, no check needed after clean shutdown > - Fast and Wide SCSI support on all capable host adapters > - Tagged queuing > Striped/concatenated disk partitions > PCMCIA and power management support > Java Development Kit (JDK) ported to BSD/OS > POSIX Threads Support > Thread Safe C Library From owner-freebsd-current Tue Oct 15 20:19:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA02410 for current-outgoing; Tue, 15 Oct 1996 20:19:00 -0700 (PDT) Received: from rosie.scsn.net (scsn.net [206.25.246.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA02401 for ; Tue, 15 Oct 1996 20:18:49 -0700 (PDT) Received: from rhiannon.scsn.net (cola58.scsn.net [206.25.247.58]) by rosie.scsn.net (post.office MTA v2.0 0813 ID# 0-13529) with ESMTP id AAA200; Tue, 15 Oct 1996 23:18:07 -0400 Received: (from root@localhost) by rhiannon.scsn.net (8.7.6/8.6.12) id XAA00322; Tue, 15 Oct 1996 23:19:11 -0400 (EDT) From: "Donald J. Maddox" Message-Id: <199610160319.XAA00322@rhiannon.scsn.net> Subject: Re: Bug with moused and XFree86 In-Reply-To: <199610160134.LAA27630@genesis.atrad.adelaide.edu.au> from Michael Smith at "Oct 16, 96 11:04:11 am" To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Tue, 15 Oct 1996 23:19:10 -0400 (EDT) Cc: current@FreeBSD.org 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 > Donald J. Maddox stands accused of saying: > > > > Ok, that did the trick! Thanks for all the help, Jason. > > BTW... Why is there no manpage for moused? Is there anywhere > > As the original author of moused (no complaints please), I hereby delegate > the authoring of the moused manpage, herafter to be referred to as > moused.1, to Donald J. Maddox. > > Donald, please contact Soren and me when you have a planned release date > for this important piece of documentation. > Well, the thread leading up to this message should demonstrate that that would be a pretty poorly-informed manpage, indeed. :-) In all seriousness, though, if you took my question as some kind of "demand" for a manpage, then you read far more into it than I wrote. I ask "why is there no manpage?" because I cannot, offhand, think of any other binary on my FreeBSD machine that *doesn't* have a manpage. I cannot find a reference to moused in either the FAQ or the handbook, either. I believe that this inconsistency justifies my curiousity. I state "this lack of documentation will lead to more wasted bandwidth" because that is a self-evident fact. I appreciate the effort that you put into writing moused. I do not feel that you are in any way *obligated* to document your work. > 8) > > -- > ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ > ]] Genesis Software genesis@atrad.adelaide.edu.au [[ > ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ > ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ > ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ -- Donald J. Maddox (dmaddox@scsn.net) From owner-freebsd-current Tue Oct 15 21:14:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA05035 for current-outgoing; Tue, 15 Oct 1996 21:14:53 -0700 (PDT) Received: from bunyip.cc.uq.oz.au (daemon@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA05015 for ; Tue, 15 Oct 1996 21:14:47 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.oz.au (8.7.6/8.7.3) id OAA29194; Wed, 16 Oct 1996 14:14:36 +1000 Received: from pandora.devetir.qld.gov.au by ogre.devetir.qld.gov.au (8.7.5/DEVETIR-E0.3a) with ESMTP id OAA20860; Wed, 16 Oct 1996 14:20:10 +1000 (EST) Received: from netfl15a.devetir.qld.gov.au (netfl15a.devetir.qld.gov.au [167.123.24.12]) by pandora.devetir.qld.gov.au (8.6.10/8.6.12) with ESMTP id OAA02909; Wed, 16 Oct 1996 14:16:31 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id EAA07913; Wed, 16 Oct 1996 04:18:09 GMT Message-Id: <199610160418.EAA07913@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6.5 12/11/95 To: Michael Smith cc: current@freebsd.org Subject: Re: Small compilation problem in -current In-reply-to: Your message of "Tue, 15 Oct 1996 20:05:39 +0930." <199610151035.UAA22090@genesis.atrad.adelaide.edu.au> X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Oct 1996 14:18:07 +1000 From: Stephen Hocking Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Stephen Hocking stands accused of saying: [Sendmail oopsie clipped] > > Just breezed past it here (fresh sup this afternoon); I suspect you > have lib breakage. You _are_ building properly, aren't you? 8) > I was making the includes, the libs and then most. Just did a make world and it has cleared up. Don't know precisely what it was... Stephen -- The views expressed above are not those of the Worker's Compensation Board of Queensland, Australia. From owner-freebsd-current Tue Oct 15 21:20:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA05439 for current-outgoing; Tue, 15 Oct 1996 21:20:08 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA05364 for ; Tue, 15 Oct 1996 21:20:01 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id NAA29725; Wed, 16 Oct 1996 13:49:54 +0930 From: Michael Smith Message-Id: <199610160419.NAA29725@genesis.atrad.adelaide.edu.au> Subject: Re: Small compilation problem in -current To: sysseh@devetir.qld.gov.au (Stephen Hocking) Date: Wed, 16 Oct 1996 13:49:54 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, current@freebsd.org In-Reply-To: <199610160418.EAA07913@netfl15a.devetir.qld.gov.au> from "Stephen Hocking" at Oct 16, 96 02:18:07 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Stephen Hocking stands accused of saying: > > I was making the includes, the libs and then most. Just did a make world and > it has cleared up. Don't know precisely what it was... 'make world' now does 'make bootstrap', which may be relevant. > Stephen -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Oct 15 21:21:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA05527 for current-outgoing; Tue, 15 Oct 1996 21:21:10 -0700 (PDT) Received: from po2.glue.umd.edu (po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA05512 for ; Tue, 15 Oct 1996 21:21:05 -0700 (PDT) Received: from baud.eng.umd.edu (baud.eng.umd.edu [129.2.98.183]) by po2.glue.umd.edu (8.8.0/8.7.3) with ESMTP id AAA07982; Wed, 16 Oct 1996 00:21:02 -0400 (EDT) Received: from localhost (chuckr@localhost) by baud.eng.umd.edu (8.7.5/8.7.3) with SMTP id AAA00842; Wed, 16 Oct 1996 00:21:01 -0400 (EDT) X-Authentication-Warning: baud.eng.umd.edu: chuckr owned process doing -bs Date: Wed, 16 Oct 1996 00:20:57 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@baud.eng.umd.edu To: Rich Murphey cc: asami@FreeBSD.org, torstenb@FreeBSD.org, ports@FreeBSD.org, FreeBSD current Subject: Re: xpm static library In-Reply-To: <199610160414.XAA25640@richc.isdn.bcm.tmc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 15 Oct 1996, Rich Murphey wrote: > |From: Chuck Robey > |> |Just let me jump in here a moment. All that stuff is controlled by > |> |FreeBSD.cf, which we really ought to get some chance to tweak, you know. > |> |Before it becomes a regular part of a distribution is the right time to > |> |consider it. > |> | > |> |One possibility is to ask that a site.def file be sited in OUR > |> |/usr/share/mk directory, so we could get our own meathooks on part of the > |> |config. > |> > |> Yep, FreeBSD.cf would be the ideal place to '#define > |> ForceNormalLib YES' specificly for FreeBSD. Would that > |> fix it? Rich > | > |Yes and no. It won't fix it as long as the location of that file is > |defined to be inside the XFree86 distribution, where our cvs can't touch > |it. Would be kinda nice if either that file or site def (which is > |currently in /usr/X11R6/lib/X11config and totally _empty_) were sited > |somewhere accessible to our tree. > > Hmm.. like /etc? That particular location is used for > other things like XF86Config, so there's a precedent of > sorts. And since it's already used for a similar > purpose by other OSes as well there's a chance it would > be less surprising to them. > > |Personally, I would want some chance to mess with the contents of that > |file by giving verbal input to XFree86 members, but not have that inside > |our tree. I would have the site.def in our tree somewhere, where it being > |empty or missing wouldn't kill things. > > There's no reason you couldn't search /etc first for > site.def and /usr/X11R6/lib/X11/config last. Would > that help? Rich Well, that satisfies me, sort of. It doesn't give me direct control over it, but that's probably all to the good. I think at this point it's time to get the suggestion reviewed, by a different audience than ports. The point is to give ports some direct control over how X11 ports are built and stored. I'm going to copy this to current, and listen to the howls. > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Tue Oct 15 21:36:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA06866 for current-outgoing; Tue, 15 Oct 1996 21:36:09 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA06842 for ; Tue, 15 Oct 1996 21:36:03 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id EAA10942; Wed, 16 Oct 1996 04:35:49 GMT Date: Wed, 16 Oct 1996 13:35:49 +0900 (JST) From: Michael Hancock To: Nate Williams cc: current@FreeBSD.org Subject: Re: BSDI 3.0 feature list In-Reply-To: <199610160111.TAA08069@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 15 Oct 1996, Nate Williams wrote: > This is a bit off-topic, but I find it ironic that BSDI 3.0 contains > almost everything FreeBSD -current had (or stuff we've had for quite a What's ironic about it? Their contributor pool isn't as large as FreeBSD's. Mike Hancock From owner-freebsd-current Tue Oct 15 22:02:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA08508 for current-outgoing; Tue, 15 Oct 1996 22:02:23 -0700 (PDT) Received: from dyson.iquest.net ([198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA08499 for ; Tue, 15 Oct 1996 22:02:19 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id AAA00379; Wed, 16 Oct 1996 00:01:39 -0500 (EST) From: "John S. Dyson" Message-Id: <199610160501.AAA00379@dyson.iquest.net> Subject: Need help testing this maybe NFS fix To: pst@jnx.com, joerg_wunsch@uriah.heep.sax.de, jdp@polstra.com, current@freebsd.org Date: Wed, 16 Oct 1996 00:01:39 -0500 (EST) Cc: karl@mcs.net 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 During the rundown of forcibly dismounted NFS filesystems, there is some sloppyness in the handling of the VM objects associated with the files on the filesystems. Included with this message is a patch file that fixes that problem, and also improves the swapping algorithm by making processes that have been waken up from a sleep and who are swapped out eligible immediately for being swapped in. The main reason for this mailing is to get some feedback on a perspective NFS fix, and the swapping fix is only a side-effect of my current tree... Please let me know as soon as you can the positive or negative outcomes of running with this code... Thanks!!! John Index: kern/kern_synch.c =================================================================== RCS file: /local/home/ncvs/src/sys/kern/kern_synch.c,v retrieving revision 1.25 diff -r1.25 kern_synch.c 463a464 > p->p_flag |= P_SWAPINREQ; 508a510 > p->p_flag |= P_SWAPINREQ; 627c629,630 < if ((p->p_flag & P_INMEM) == 0) --- > if ((p->p_flag & P_INMEM) == 0) { > p->p_flag |= P_SWAPINREQ; 628a632 > } Index: kern/vfs_subr.c =================================================================== RCS file: /local/home/ncvs/src/sys/kern/vfs_subr.c,v retrieving revision 1.61 diff -r1.61 vfs_subr.c 982c982,983 < if ((vp->v_usecount == 1) && vp->v_object) { --- > if (vp->v_object && (vp->v_object->flags & OBJ_VFS_REF)) { > vm_object_reference(vp->v_object); 983a985,986 > vp->v_object->flags &= ~OBJ_VFS_REF; > vm_object_deallocate(vp->v_object); 993a997 > 1151a1156,1160 > > if (vp->v_object) { > vp->v_object->flags |= OBJ_VNODE_GONE; > } > Index: sys/proc.h =================================================================== RCS file: /local/home/ncvs/src/sys/sys/proc.h,v retrieving revision 1.29 diff -r1.29 proc.h 217a218 > #define P_SWAPINREQ 0x80000 /* Swapin request due to wakeup */ Index: vm/vm_glue.c =================================================================== RCS file: /local/home/ncvs/src/sys/vm/vm_glue.c,v retrieving revision 1.54 diff -r1.54 vm_glue.c 322c322,325 < pri = p->p_swtime + p->p_slptime - p->p_nice * 8; --- > pri = p->p_swtime + p->p_slptime; > if ((p->p_flag & P_SWAPINREQ) == 0) { > pri -= p->p_nice * 8; > } 337c340 < * Nothing to do, back to sleep --- > * Nothing to do, back to sleep. 342a346,347 > p->p_flag &= ~P_SWAPINREQ; > Index: vm/vm_object.h =================================================================== RCS file: /local/home/ncvs/src/sys/vm/vm_object.h,v retrieving revision 1.31 diff -r1.31 vm_object.h 135a136 > #define OBJ_VNODE_GONE 0x0800 /* vnode is gone */ Index: vm/vnode_pager.c =================================================================== RCS file: /local/home/ncvs/src/sys/vm/vnode_pager.c,v retrieving revision 1.64 diff -r1.64 vnode_pager.c 616a617,618 > if (object->flags & OBJ_VNODE_GONE) > return VM_PAGER_ERROR; 859a862,865 > > if (object->flags & OBJ_VNODE_GONE) > return VM_PAGER_ERROR; > From owner-freebsd-current Tue Oct 15 22:12:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA09000 for current-outgoing; Tue, 15 Oct 1996 22:12:31 -0700 (PDT) Received: from phoenix.csie.nctu.edu.tw (phoenix.csie.nctu.edu.tw [140.113.17.171]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA08993 for ; Tue, 15 Oct 1996 22:12:28 -0700 (PDT) Received: from FreeBSD.csie.NCTU.edu.tw (freebsd.csie.nctu.edu.tw [140.113.235.250]) by phoenix.csie.nctu.edu.tw (8.7.5/8.7.5) with ESMTP id NAA17616 for ; Wed, 16 Oct 1996 13:09:40 +0800 (CST) Received: (from jdli@localhost) by FreeBSD.csie.NCTU.edu.tw (8.7.6/8.7.3) id NAA19045 for freebsd-current@freebsd.org; Wed, 16 Oct 1996 13:11:07 +0800 (CST) From: Jian-Da Li Message-Id: <199610160511.NAA19045@FreeBSD.csie.NCTU.edu.tw> Subject: mbuf full problem To: freebsd-current@freebsd.org Date: Wed, 16 Oct 1996 13:11:06 +0800 (CST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi : Our FreeBSD server is running 2.2-961006-SNAP with the latest current kernel, and there is a serious problem about mbuf useage (since long ago). I found that whenever the mbuf clusters useage reached (or over) the limit defined by NMBCLUSTERS, it seems will never decrease. The mbuf full problem is usually caused by too many mirror processes running, or the search engine updating it's gathered database. The mbuf useage is normally around 800 on this server, but when too-many-mirrors are running or search engine is gathering, it will increase to 1200 (current kernel limit) even to 1800 (old kernel limit). And it will cause network almost down except ping. I tried to kill those processes, but the mbuf useage just keep staying around 1200 (was 1800) no matter how many network-related processess I killed. I have to reboot the machine to solve this problem. Now I increase NMBCLUSTERS back to 1800 to make the bad thing happen slower, but I don't think it's the right way to go. Is it a mbuf-leaking ? Which information else can I provide ? Any idea ? ====== netstat -m, maxuser=48, DRAM=32MB ====== 1430 mbufs in use: 1366 mbufs allocated to data 29 mbufs allocated to packet headers 23 mbufs allocated to protocol control blocks 12 mbufs allocated to socket names and addresses 1280/1280 mbuf clusters in use 2738 Kbytes allocated to network (100% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines =============================================== Thanks for your help. -- 李 建 達 (Jian-Da Li) 交 大 資 工 E-Mail : http://www.csie.nctu.edu.tw/~jdli From owner-freebsd-current Tue Oct 15 22:14:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA09120 for current-outgoing; Tue, 15 Oct 1996 22:14:58 -0700 (PDT) Received: from dfw-ix5.ix.netcom.com (dfw-ix5.ix.netcom.com [206.214.98.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA09108 for ; Tue, 15 Oct 1996 22:14:56 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca9-50.ix.netcom.com [207.93.143.114]) by dfw-ix5.ix.netcom.com (8.6.13/8.6.12) with ESMTP id WAA29444; Tue, 15 Oct 1996 22:13:48 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.6/8.6.9) id WAA19389; Tue, 15 Oct 1996 22:13:45 -0700 (PDT) Date: Tue, 15 Oct 1996 22:13:45 -0700 (PDT) Message-Id: <199610160513.WAA19389@silvia.HIP.Berkeley.EDU> To: chuckr@glue.umd.edu CC: rich@rich.isdn.bcm.tmc.edu, torstenb@FreeBSD.org, ports@FreeBSD.org, freebsd-current@freefall.FreeBSD.org In-reply-to: (message from Chuck Robey on Wed, 16 Oct 1996 00:20:57 -0400 (EDT)) Subject: Re: xpm static library From: asami@FreeBSD.org (Satoshi Asami) Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk * > There's no reason you couldn't search /etc first for * > site.def and /usr/X11R6/lib/X11/config last. Would * > that help? Rich * * Well, that satisfies me, sort of. It doesn't give me direct control over * it, but that's probably all to the good. I think at this point it's time * to get the suggestion reviewed, by a different audience than ports. * * The point is to give ports some direct control over how X11 ports are * built and stored. I'm going to copy this to current, and listen to the * howls. By the way, I think Chuck is talking about host.def. site.def is not empty. Satoshi From owner-freebsd-current Tue Oct 15 22:31:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA10176 for current-outgoing; Tue, 15 Oct 1996 22:31:41 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA10168 for ; Tue, 15 Oct 1996 22:31:39 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id XAA09204; Tue, 15 Oct 1996 23:31:32 -0600 (MDT) Date: Tue, 15 Oct 1996 23:31:32 -0600 (MDT) Message-Id: <199610160531.XAA09204@rocky.mt.sri.com> From: Nate Williams To: Michael Hancock Cc: Nate Williams , current@freebsd.org Subject: Re: BSDI 3.0 feature list In-Reply-To: References: <199610160111.TAA08069@rocky.mt.sri.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > This is a bit off-topic, but I find it ironic that BSDI 3.0 contains > > almost everything FreeBSD -current had (or stuff we've had for quite a > > What's ironic about it? Their contributor pool isn't as large as > FreeBSD's. I think you're mistaken. Almost every one of BSDi/3.0 'features' are kernel features, and the # of kernel hackers in FreeBSD is about the same as in BSDi. It's certainly a lot less than in something like NetBSD, but it seems most of them spend all their time just trying to keep their's kernel working (or get it working :) rather than doing lots of new features. Nate From owner-freebsd-current Tue Oct 15 23:02:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA12256 for current-outgoing; Tue, 15 Oct 1996 23:02:29 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA12248 for ; Tue, 15 Oct 1996 23:02:25 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id GAA11641; Wed, 16 Oct 1996 06:02:19 GMT Date: Wed, 16 Oct 1996 15:02:19 +0900 (JST) From: Michael Hancock To: Nate Williams cc: current@freebsd.org Subject: Re: BSDI 3.0 feature list In-Reply-To: <199610160531.XAA09204@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 15 Oct 1996, Nate Williams wrote: > > > This is a bit off-topic, but I find it ironic that BSDI 3.0 contains > > > almost everything FreeBSD -current had (or stuff we've had for quite a > > > > What's ironic about it? Their contributor pool isn't as large as > > FreeBSD's. > > I think you're mistaken. Almost every one of BSDi/3.0 'features' are > kernel features, and the # of kernel hackers in FreeBSD is about the > same as in BSDi. It's certainly a lot less than in something like > NetBSD, but it seems most of them spend all their time just trying to > keep their's kernel working (or get it working :) rather than doing lots > of new features. Erm. I didn't look at it that way. One thing to consider is that they initially had the CSRG VM guy, but not the FS/VM guy. Maybe they waffled on what to do for a while. I wonder what approach they used to make (read/write/mmap) coherent? This could make for an interesting comparison. Regards, Mike From owner-freebsd-current Wed Oct 16 07:12:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA04441 for current-outgoing; Wed, 16 Oct 1996 07:12:33 -0700 (PDT) Received: from dyson.iquest.net ([198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA04432 for ; Wed, 16 Oct 1996 07:12:26 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id JAA03363 for current@freebsd.org; Wed, 16 Oct 1996 09:12:24 -0500 (EST) From: "John S. Dyson" Message-Id: <199610161412.JAA03363@dyson.iquest.net> Subject: How is the NFS forcible dismount patch running? To: current@freebsd.org Date: Wed, 16 Oct 1996 09:12:24 -0500 (EST) 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 Hopefully the AMD (automounter) problems are pretty much gone? John From owner-freebsd-current Wed Oct 16 07:38:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA06017 for current-outgoing; Wed, 16 Oct 1996 07:38:12 -0700 (PDT) Received: from dyson.iquest.net ([198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA06009; Wed, 16 Oct 1996 07:38:07 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id JAA03426; Wed, 16 Oct 1996 09:38:05 -0500 (EST) From: John Dyson Message-Id: <199610161438.JAA03426@dyson.iquest.net> Subject: Re: How is the NFS forcible dismount patch running? To: dyson@freebsd.org Date: Wed, 16 Oct 1996 09:38:05 -0500 (EST) Cc: current@freebsd.org In-Reply-To: <199610161412.JAA03363@dyson.iquest.net> from "John S. Dyson" at Oct 16, 96 09:12:24 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 > Hopefully the AMD (automounter) problems are pretty much gone? > It was too early for me to be coherent when I asked the question :-). What I meant was that last night, I fixed a problem with the rundown of vnode that manifested itself as a problem with forcible NFS unmounts... Does NFS look more stable now? is a better way of asking the question :-). John From owner-freebsd-current Wed Oct 16 07:48:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA06418 for current-outgoing; Wed, 16 Oct 1996 07:48:31 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA06378 for ; Wed, 16 Oct 1996 07:47:59 -0700 (PDT) Received: (from narvi@localhost) by haldjas.folklore.ee (8.7.5/8.6.12) id RAA11566; Wed, 16 Oct 1996 17:44:31 +0300 (EET DST) Date: Wed, 16 Oct 1996 17:44:31 +0300 (EET DST) From: Narvi To: Michael Hancock cc: Nate Williams , current@FreeBSD.org Subject: Re: BSDI 3.0 feature list In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 16 Oct 1996, Michael Hancock wrote: > On Tue, 15 Oct 1996, Nate Williams wrote: > > > This is a bit off-topic, but I find it ironic that BSDI 3.0 contains > > almost everything FreeBSD -current had (or stuff we've had for quite a > > What's ironic about it? Their contributor pool isn't as large as > FreeBSD's. Still they have got Lite2, Web based configuration (Ok it was raised once here too, but it din't have any wind for flying) and long filenames for DOS. It's all that occured to me at the first glance. Maybe there is more, maybe not. Sander > > Mike Hancock > From owner-freebsd-current Wed Oct 16 07:58:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA06973 for current-outgoing; Wed, 16 Oct 1996 07:58:10 -0700 (PDT) Received: from miller.cs.uwm.edu (miller.cs.uwm.edu [129.89.139.22]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA06968 for ; Wed, 16 Oct 1996 07:58:03 -0700 (PDT) Received: (from james@localhost) by miller.cs.uwm.edu (8.7.6/8.7.3) id JAA04430 for current@freebsd.org; Wed, 16 Oct 1996 09:58:00 -0500 (CDT) Date: Wed, 16 Oct 1996 09:58:00 -0500 (CDT) From: Jim Lowe Message-Id: <199610161458.JAA04430@miller.cs.uwm.edu> To: current@freebsd.org Subject: Devfs update time Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk When using the devfs filesystem, the times for the inode don't get updated. I beleive atime, ctime, and mtime need to be enabled for things in the devfs. The following example illustrates the problem: % touch `tty` touch: /dev/ttyp0: Inappropriate file type or format -Jim From owner-freebsd-current Wed Oct 16 09:31:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA12911 for current-outgoing; Wed, 16 Oct 1996 09:31:47 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA12887 for ; Wed, 16 Oct 1996 09:31:39 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id CAA25066 for current@freebsd.org; Thu, 17 Oct 1996 02:27:03 +1000 Date: Thu, 17 Oct 1996 02:27:03 +1000 From: Bruce Evans Message-Id: <199610161627.CAA25066@godzilla.zeta.org.au> To: current@freebsd.org Subject: scsi drives left locked by shutdown Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I use a zip drive for "/" and swap on a test machine. Shutdown doesn't close the swap device, so scsi_prevent() isn't called to unlock the drive, so a hard reset is required to eject disks. Bruce From owner-freebsd-current Wed Oct 16 09:40:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA13703 for current-outgoing; Wed, 16 Oct 1996 09:40:43 -0700 (PDT) Received: from GPO.iol.ie (GPO.iol.ie [194.125.2.239]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA13685 for ; Wed, 16 Oct 1996 09:40:36 -0700 (PDT) Received: from dialup-057.dublin.iol.ie (dialup-057.dublin.iol.ie [194.125.60.57]) by GPO.iol.ie Sendmail(v8.7.6) with SMTP id RAA11616; Wed, 16 Oct 1996 17:40:09 +0100 (BST) From: derm@iol.ie (Dermot McNally) To: "Justin T. Gibbs" Cc: current@FreeBSD.org Subject: Re: Bug with moused and XFree86 Date: Wed, 16 Oct 1996 16:38:40 GMT Organization: My House Message-ID: <3266af08.1754502@mail.indigo.ie> References: <199610152300.QAA14965@freefall.freebsd.org> In-Reply-To: <199610152300.QAA14965@freefall.freebsd.org> X-Mailer: Forte Agent .99f/32.299 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 15 Oct 1996 16:00:02 -0700, "Justin T. Gibbs" wrote: >> From /etc/XF86Config: >>----------------------------------------------------------------- >> Section "Pointer" >> Protocol "MouseMan" >> Device "/dev/mouse" >>----------------------------------------------------------------- >> What's wrong here? > >This should say "MouseSystems". Moused makes all mice look like >MouseSystems mice. One thought here - is it still possible to switch on Emulate-3-buttons in XF86Config with this setup? There doesn't seem to be any way to make moused do this. Dermot ----------------------------------------------------------- Dermot McNally, derm@iol.ie "OK, one last time. These are _small_, but the ones out there are _far = away_. _Small_........ _Far Away_." Father Ted. From owner-freebsd-current Wed Oct 16 10:01:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA15647 for current-outgoing; Wed, 16 Oct 1996 10:01:21 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA15635 for ; Wed, 16 Oct 1996 10:01:11 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id CAA25825; Thu, 17 Oct 1996 02:59:26 +1000 Date: Thu, 17 Oct 1996 02:59:26 +1000 From: Bruce Evans Message-Id: <199610161659.CAA25825@godzilla.zeta.org.au> To: current@FreeBSD.org, james@miller.cs.uwm.edu Subject: Re: Devfs update time Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >When using the devfs filesystem, the times for the inode don't >get updated. I beleive atime, ctime, and mtime need to be >enabled for things in the devfs. > >The following example illustrates the problem: > % touch `tty` > touch: /dev/ttyp0: Inappropriate file type or format There are several problems: utimes() (which is used by `touch') doesn't work, i/o timestamps don't work, and inode change timestamps (e.g. for link and unlink) don't work. The enclosed patch is supposed to fix utimes(). The utimes(path, NULL) case is broken by an earlier check for (cred->cr_uid != file_node->uid). Write permission is supposed to be sufficient in this case. Hmm, the suser() check seems to be too early here, as it is in ufs where this patch was mostly copied from. I think the VA_UTIMES_NULL check should be before the suser() check. Bruce diff -c2 devfs_vnops.c~ devfs_vnops.c *** devfs_vnops.c~ Sun Oct 13 04:40:25 1996 --- devfs_vnops.c Sun Oct 13 04:41:45 1996 *************** *** 603,606 **** --- 600,604 ---- int error = 0; dn_p file_node; + struct timeval tv; if (error = devfs_vntodn(vp,&file_node)) *************** *** 617,622 **** (vap->va_rdev != VNOVAL) || (vap->va_bytes != VNOVAL) || ! (vap->va_gen != VNOVAL) || ! (vap->va_atime.tv_sec != VNOVAL)) { return EINVAL; --- 615,619 ---- (vap->va_rdev != VNOVAL) || (vap->va_bytes != VNOVAL) || ! (vap->va_gen != VNOVAL)) { return EINVAL; *************** *** 632,648 **** return error; /*XXX (?) */ } - if (vap->va_atime.tv_sec != VNOVAL) - { - file_node->atime = vap->va_atime; - } ! if (vap->va_mtime.tv_sec != VNOVAL) ! { file_node->mtime = vap->va_mtime; ! } ! ! if (vap->va_ctime.tv_sec != VNOVAL) ! { ! file_node->ctime = vap->va_ctime; } --- 629,646 ---- return error; /*XXX (?) */ } ! if (vap->va_atime.tv_sec != VNOVAL || vap->va_mtime.tv_sec != VNOVAL) { ! if (vp->v_mount->mnt_flag & MNT_RDONLY) ! return (EROFS); ! if (cred->cr_uid != file_node->uid && ! (error = suser(cred, &p->p_acflag)) && ! ((vap->va_vaflags & VA_UTIMES_NULL) == 0 || ! (error = VOP_ACCESS(vp, VWRITE, cred, p)))) ! return (error); ! file_node->atime = vap->va_atime; file_node->mtime = vap->va_mtime; ! microtime(&tv); ! TIMEVAL_TO_TIMESPEC(&tv, &file_node->ctime); ! return (0); } From owner-freebsd-current Wed Oct 16 11:21:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA23225 for current-outgoing; Wed, 16 Oct 1996 11:21:07 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA23217 for ; Wed, 16 Oct 1996 11:21:04 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.6/8.7.3) with SMTP id LAA02220; Wed, 16 Oct 1996 11:18:32 -0700 (PDT) Message-ID: <32652678.41C67EA6@whistle.com> Date: Wed, 16 Oct 1996 11:16:24 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Jim Lowe CC: current@FreeBSD.org Subject: Re: Devfs update time References: <199610161458.JAA04430@miller.cs.uwm.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jim Lowe wrote: hopefully fixed..... > > When using the devfs filesystem, the times for the inode don't > get updated. I beleive atime, ctime, and mtime need to be > enabled for things in the devfs. > > The following example illustrates the problem: > % touch `tty` > touch: /dev/ttyp0: Inappropriate file type or format > > -Jim From owner-freebsd-current Wed Oct 16 11:23:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA23469 for current-outgoing; Wed, 16 Oct 1996 11:23:12 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA23454 for ; Wed, 16 Oct 1996 11:23:06 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.6/8.7.3) with SMTP id LAA02244; Wed, 16 Oct 1996 11:20:18 -0700 (PDT) Message-ID: <326526E2.167EB0E7@whistle.com> Date: Wed, 16 Oct 1996 11:18:10 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Bruce Evans CC: current@freebsd.org Subject: Re: scsi drives left locked by shutdown References: <199610161627.CAA25066@godzilla.zeta.org.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bruce Evans wrote: > > I use a zip drive for "/" and swap on a test machine. Shutdown doesn't > close the swap device, so scsi_prevent() isn't called to unlock the drive, > so a hard reset is required to eject disks. > > Bruce maybe a use for the at_shutdown() call? At one stage in the Berkeley BSD 4.4 course there was discussion of adding "shutdown" entries to cdevsw entries.. From owner-freebsd-current Wed Oct 16 11:50:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA25088 for current-outgoing; Wed, 16 Oct 1996 11:50:31 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA25083 for ; Wed, 16 Oct 1996 11:50:29 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA03445; Wed, 16 Oct 1996 11:49:21 -0700 From: Terry Lambert Message-Id: <199610161849.LAA03445@phaeton.artisoft.com> Subject: Re: scsi drives left locked by shutdown To: julian@whistle.com (Julian Elischer) Date: Wed, 16 Oct 1996 11:49:21 -0700 (MST) Cc: bde@zeta.org.au, current@FreeBSD.org In-Reply-To: <326526E2.167EB0E7@whistle.com> from "Julian Elischer" at Oct 16, 96 11:18:10 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 > > I use a zip drive for "/" and swap on a test machine. Shutdown doesn't > > close the swap device, so scsi_prevent() isn't called to unlock the drive, > > so a hard reset is required to eject disks. > > maybe a use for the at_shutdown() call? > At one stage in the Berkeley BSD 4.4 course there was discussion > of adding "shutdown" entries to cdevsw entries.. I second the motion of adding "detach" routines... it's very necessary for rundown on pluggable hardware (which, by definition, is also unpluggable). The driver needs to be able to "rundown" at any time. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Oct 16 12:07:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA26197 for current-outgoing; Wed, 16 Oct 1996 12:07:56 -0700 (PDT) Received: from phoenix.csie.nctu.edu.tw (root@phoenix.csie.nctu.edu.tw [140.113.17.171]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA26189 for ; Wed, 16 Oct 1996 12:07:48 -0700 (PDT) Received: from FreeBSD.csie.NCTU.edu.tw (freebsd.csie.nctu.edu.tw [140.113.235.250]) by phoenix.csie.nctu.edu.tw (8.7.5/8.7.5) with ESMTP id DAA15465 for ; Thu, 17 Oct 1996 03:05:26 +0800 (CST) Received: (from jdli@localhost) by FreeBSD.csie.NCTU.edu.tw (8.7.6/8.7.3) id DAA02490 for freebsd-current@freebsd.org; Thu, 17 Oct 1996 03:06:50 +0800 (CST) Date: Thu, 17 Oct 1996 03:06:50 +0800 (CST) From: Jian-Da Li Message-Id: <199610161906.DAA02490@FreeBSD.csie.NCTU.edu.tw> To: freebsd-current@freebsd.org Subject: Re: Need help testing this maybe NFS fix X-Newsreader: TIN [UNIX 1.3 950824BETA+ANSI+COLOR PL6] Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 您在 <541r6t$ilm@FreeBSD.csie.NCTU.edu.tw> 文章內提到: : The main reason for this mailing is to get some feedback : on a perspective NFS fix, and the swapping fix is only a : side-effect of my current tree... Please let me know as : soon as you can the positive or negative outcomes of running : with this code... This patch is required on our heavy-loaded server to avoid hourly crash using 2.2-961014-SNAP. :( It was very stable running 2.2-960801-SNAP, and with this patch, it seems to be stable again. (up 3+ hours) Thanks. -- 李 建 達 (Jian-Da Li) 交 大 資 工 E-Mail : http://www.csie.nctu.edu.tw/~jdli From owner-freebsd-current Wed Oct 16 12:10:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA26457 for current-outgoing; Wed, 16 Oct 1996 12:10:41 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA26449 for ; Wed, 16 Oct 1996 12:10:37 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65v3.2/1.1.8.2/19Aug95-0530PM) id AA09028; Wed, 16 Oct 1996 15:09:11 -0400 Date: Wed, 16 Oct 1996 15:09:11 -0400 From: Garrett Wollman Message-Id: <9610161909.AA09028@halloran-eldar.lcs.mit.edu> To: Terry Lambert Cc: julian@whistle.com (Julian Elischer), bde@zeta.org.au, current@FreeBSD.org Subject: Re: scsi drives left locked by shutdown In-Reply-To: <199610161849.LAA03445@phaeton.artisoft.com> References: <326526E2.167EB0E7@whistle.com> <199610161849.LAA03445@phaeton.artisoft.com> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk < said: >> maybe a use for the at_shutdown() call? >> At one stage in the Berkeley BSD 4.4 course there was discussion >> of adding "shutdown" entries to cdevsw entries.. > I second the motion of adding "detach" routines... it's very necessary > for rundown on pluggable hardware (which, by definition, is also > unpluggable). The driver needs to be able to "rundown" at any time. This was, of course, one of the principal features of devconf, which Poul-Henning ripped out some months ago without so much as a by-your-leave and has yet to even discuss a replacement for. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Wed Oct 16 12:16:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA27157 for current-outgoing; Wed, 16 Oct 1996 12:16:55 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA27148 for ; Wed, 16 Oct 1996 12:16:50 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id FAA29051; Thu, 17 Oct 1996 05:15:37 +1000 Date: Thu, 17 Oct 1996 05:15:37 +1000 From: Bruce Evans Message-Id: <199610161915.FAA29051@godzilla.zeta.org.au> To: bde@zeta.org.au, julian@whistle.com Subject: Re: scsi drives left locked by shutdown Cc: current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> I use a zip drive for "/" and swap on a test machine. Shutdown doesn't >> close the swap device, so scsi_prevent() isn't called to unlock the drive, >maybe a use for the at_shutdown() call? Also swapoff(2). Bruce From owner-freebsd-current Wed Oct 16 12:26:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA28032 for current-outgoing; Wed, 16 Oct 1996 12:26:26 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA28024; Wed, 16 Oct 1996 12:26:24 -0700 (PDT) Message-Id: <199610161926.MAA28024@freefall.freebsd.org> To: Terry Lambert cc: julian@whistle.com (Julian Elischer), bde@zeta.org.au, current@FreeBSD.org Subject: Re: scsi drives left locked by shutdown In-reply-to: Your message of "Wed, 16 Oct 1996 11:49:21 PDT." <199610161849.LAA03445@phaeton.artisoft.com> Date: Wed, 16 Oct 1996 12:26:23 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> > I use a zip drive for "/" and swap on a test machine. Shutdown doesn't >> > close the swap device, so scsi_prevent() isn't called to unlock the drive, >> > so a hard reset is required to eject disks. >> >> maybe a use for the at_shutdown() call? >> At one stage in the Berkeley BSD 4.4 course there was discussion >> of adding "shutdown" entries to cdevsw entries.. > >I second the motion of adding "detach" routines... it's very necessary >for rundown on pluggable hardware (which, by definition, is also >unpluggable). The driver needs to be able to "rundown" at any time. > > > Terry Lambert > terry@lambert.org >--- >Any opinions in this posting are my own and not those of my present >or previous employers. Although detach routines might be useful for other reasons, I see the bug here as the swap device is never closed and that it should be. This doesn't require another device entry point to fix. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Wed Oct 16 13:19:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA02196 for current-outgoing; Wed, 16 Oct 1996 13:19:47 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA02184; Wed, 16 Oct 1996 13:19:39 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id WAA00575; Wed, 16 Oct 1996 22:18:49 +0200 (MET DST) To: Garrett Wollman cc: Terry Lambert , julian@whistle.com (Julian Elischer), bde@zeta.org.au, current@FreeBSD.org Subject: Re: scsi drives left locked by shutdown In-reply-to: Your message of "Wed, 16 Oct 1996 15:09:11 EDT." <9610161909.AA09028@halloran-eldar.lcs.mit.edu> Date: Wed, 16 Oct 1996 22:18:48 +0200 Message-ID: <573.845497128@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <9610161909.AA09028@halloran-eldar.lcs.mit.edu>, Garrett Wollman wri >> I second the motion of adding "detach" routines... it's very necessary >> for rundown on pluggable hardware (which, by definition, is also >> unpluggable). The driver needs to be able to "rundown" at any time. > >This was, of course, one of the principal features of devconf, which >Poul-Henning ripped out some months ago without so much as a >by-your-leave and has yet to even discuss a replacement for. May I respectfully remind you that you never heeded the calls from hackers & core alike to finish the bloddy thing for over a one year period of time. Your one-month deadline for coming up with either a finished implementation or a bit of documentation about the intentions was gracefully extended to more than 6 months before devconf was taken out behind the barn and shot. I have sent you my preliminary comments on your document about a replacement, and that is more than 3 times longer than anything you have ever sent me on similar occasions. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Wed Oct 16 13:30:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA03001 for current-outgoing; Wed, 16 Oct 1996 13:30:19 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA02987 for ; Wed, 16 Oct 1996 13:30:13 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65v3.2/1.1.8.2/19Aug95-0530PM) id AA03123; Wed, 16 Oct 1996 16:30:01 -0400 Date: Wed, 16 Oct 1996 16:30:01 -0400 From: Garrett Wollman Message-Id: <9610162030.AA03123@halloran-eldar.lcs.mit.edu> To: Poul-Henning Kamp Cc: current@FreeBSD.org Subject: Re: scsi drives left locked by shutdown In-Reply-To: <573.845497128@critter.tfs.com> References: <9610161909.AA09028@halloran-eldar.lcs.mit.edu> <573.845497128@critter.tfs.com> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk < said: > Your one-month deadline for coming up with either a finished > implementation or a bit of documentation about the intentions > was gracefully extended to more than 6 months before devconf > was taken out behind the barn and shot. And what have you done to replace it? You should have bloody well LEFT IT ALONE until you had written the replacement. (You certainly haven't demonstrated that it somehow was never useful or necessary.) > I have sent you my preliminary comments on your document about > a replacement You sent me one comment, about it being too complex for you. You have not sent me a single USEFUL reply, and so far as I can tell, nobody else has even bothered to look at it. (For the record, that was: .) This is not, by the way, a ``document about a replacement'', it's a document describing what problem such a replacement needs to solve. Having been burned once, I have no intention of actually /writing/ that replacement; I'll stick to my networking and leave device configuration up to you and Justin. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Wed Oct 16 13:40:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA03962 for current-outgoing; Wed, 16 Oct 1996 13:40:45 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA03952 for ; Wed, 16 Oct 1996 13:40:41 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id WAA00910 for ; Wed, 16 Oct 1996 22:39:51 +0200 (MET DST) To: current@freebsd.org Subject: ISDN code removal, final warning. Reply-to: phk@freebsd.org Date: Wed, 16 Oct 1996 22:39:50 +0200 Message-ID: <908.845498390@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As we have discussed earlier, the ISDN code currently in the FreeBSD source tree doesn't really cut it, so this is the final warning before we remove it. Expect to see it disappear in the next week or so. ISDN users are kindly urged to get in touch with the "bisdn" gang. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Wed Oct 16 13:46:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA04342 for current-outgoing; Wed, 16 Oct 1996 13:46:51 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA04334; Wed, 16 Oct 1996 13:46:45 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id WAA00930; Wed, 16 Oct 1996 22:45:57 +0200 (MET DST) To: Garrett Wollman cc: current@FreeBSD.org Subject: Re: scsi drives left locked by shutdown In-reply-to: Your message of "Wed, 16 Oct 1996 16:30:01 EDT." <9610162030.AA03123@halloran-eldar.lcs.mit.edu> Date: Wed, 16 Oct 1996 22:45:57 +0200 Message-ID: <928.845498757@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <9610162030.AA03123@halloran-eldar.lcs.mit.edu>, Garrett Wollman wri tes: >< >said: > >> Your one-month deadline for coming up with either a finished >> implementation or a bit of documentation about the intentions >> was gracefully extended to more than 6 months before devconf >> was taken out behind the barn and shot. > >And what have you done to replace it? You should have bloody well >LEFT IT ALONE until you had written the replacement. (You certainly >haven't demonstrated that it somehow was never useful or necessary.) I have talked with various people about the problem (who all agreed to the removal btw) and we have some good ideas, and we will probably find a good solution when we have time. In the meantime your code doesn't prevent people from thinking about it and toying with it, and it doesn't infect all our kernel sources with a bunch of unreadable code. I'm about to zap the isdn stuff for exactly the same reason. People sit there looking at it, expecting it to evolve and it's dead. >> I have sent you my preliminary comments on your document about >> a replacement > >You sent me one comment, about it being too complex for you. Well that was more than 3 times longer than your standard reply: "NO!!!!" (I'm sorry if I got it wrong, I'm not sure if you use 3 or 4 '!'s) >You have >not sent me a single USEFUL reply, and so far as I can tell, nobody >else has even bothered to look at it. Well, we're more alike than I thought then. >I have no intention of actually /writing/ >that replacement; I'll stick to my networking and leave device >configuration up to you and Justin. A wise decision that will undoubtedly help our networking code. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Wed Oct 16 14:07:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA05814 for current-outgoing; Wed, 16 Oct 1996 14:07:39 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA05809 for ; Wed, 16 Oct 1996 14:07:36 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id OAA09572; Wed, 16 Oct 1996 14:07:24 -0700 (PDT) Message-Id: <199610162107.OAA09572@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Poul-Henning Kamp cc: Garrett Wollman , current@FreeBSD.org Subject: Re: scsi drives left locked by shutdown In-reply-to: Your message of "Wed, 16 Oct 1996 22:45:57 +0200." <928.845498757@critter.tfs.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 16 Oct 1996 14:07:24 -0700 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >>I have no intention of actually /writing/ >>that replacement; I'll stick to my networking and leave device >>configuration up to you and Justin. > >A wise decision that will undoubtedly help our networking code. My goodness. Did everyone wake up on the wrong side of the bed this morning or something? Considering the attitudes, I'd say that folks woke up on the floor! -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Wed Oct 16 14:53:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09359 for current-outgoing; Wed, 16 Oct 1996 14:53:35 -0700 (PDT) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA09347 for ; Wed, 16 Oct 1996 14:53:31 -0700 (PDT) Received: from pauling.salk.edu (pauling [198.202.70.108]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id OAA20579 for ; Wed, 16 Oct 1996 14:53:22 -0700 (PDT) Date: Wed, 16 Oct 1996 14:53:31 -0700 (PDT) From: Tom Bartol To: current@FreeBSD.org Subject: wdc0 and wdc1 "not found" in -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi all, Just SUPped from sup3 and made the latest -current yesterday afternoon (Oct 15) on top of a 960801-SNAP system. I remade the kernel and rebooted. All seems well except that I can longer mount /dev/wcd0c. Further investigation of /var/log/messages revealed: Oct 16 13:33:39 pauling /kernel: wdc0 not found at 0x1f0 Oct 16 13:33:39 pauling /kernel: wdc1 not found at 0x170 Whereas with -current circa Oct 9 I got: Oct 10 23:14:57 pauling /kernel: wdc0 not found at 0x1f0 Oct 10 23:14:57 pauling /kernel: wdc1 at 0x170-0x177 irq 15 on isa Oct 10 23:14:57 pauling /kernel: wdc1: unit 0 (atapi): , removable, intr, iordis Oct 10 12:30:19 pauling /kernel: wcd0: 689Kb/sec, 128Kb cache, audio play, 255 volume levels, ejectable tray Any clues as to what's gone wrong? Tom From owner-freebsd-current Wed Oct 16 17:03:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA16962 for current-outgoing; Wed, 16 Oct 1996 17:03:10 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA16957 for ; Wed, 16 Oct 1996 17:03:06 -0700 (PDT) Received: from localhost (scrappy@localhost) by quagmire.ki.net (8.7.5/8.7.5) with SMTP id UAA01551 for ; Wed, 16 Oct 1996 20:03:04 -0400 (EDT) Date: Wed, 16 Oct 1996 20:03:02 -0400 (EDT) From: "Marc G. Fournier" To: current@freebsd.org Subject: system hangs with current kernel...? 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... This is getting slightly annoying, so I figured I'd bring it to the list... Has anyone noticed a recent problem with the -current kernel that is causing system hangs? I've seen the reports going through about panics in the NFS area and whatnot, but nothing in particular dealing with actually hangs... I'm running -current as of about Sunday night, and this morning the system locked up completely as if it was a SCSI bus hang...something I haven't experienced in *many* months on that machine. It did it last night too, and I recompiled a kernel with debugging enabled, but, of course, if it doesn't panic, it doesn't dump core :( Thanks... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Wed Oct 16 18:51:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA22186 for current-outgoing; Wed, 16 Oct 1996 18:51:14 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA22181 for ; Wed, 16 Oct 1996 18:51:11 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA09617; Thu, 17 Oct 1996 11:21:01 +0930 From: Michael Smith Message-Id: <199610170151.LAA09617@genesis.atrad.adelaide.edu.au> Subject: Re: system hangs with current kernel...? To: scrappy@ki.net (Marc G. Fournier) Date: Thu, 17 Oct 1996 11:21:00 +0930 (CST) Cc: current@freebsd.org In-Reply-To: from "Marc G. Fournier" at Oct 16, 96 08:03:02 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier stands accused of saying: > > Has anyone noticed a recent problem with the -current kernel > that is causing system hangs? I've seen the reports going through > about panics in the NFS area and whatnot, but nothing in particular > dealing with actually hangs... No. Make sure you've rebuilt your LKMs; there were changes there a little while back. > Marc G. Fournier scrappy@ki.net -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Oct 16 18:56:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA22520 for current-outgoing; Wed, 16 Oct 1996 18:56:19 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA22515 for ; Wed, 16 Oct 1996 18:56:17 -0700 (PDT) Received: from localhost (scrappy@localhost) by quagmire.ki.net (8.7.5/8.7.5) with SMTP id VAA04269; Wed, 16 Oct 1996 21:55:57 -0400 (EDT) Date: Wed, 16 Oct 1996 21:55:56 -0400 (EDT) From: "Marc G. Fournier" To: Michael Smith cc: current@freebsd.org Subject: Re: system hangs with current kernel...? In-Reply-To: <199610170151.LAA09617@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 Thu, 17 Oct 1996, Michael Smith wrote: > Marc G. Fournier stands accused of saying: > > > > Has anyone noticed a recent problem with the -current kernel > > that is causing system hangs? I've seen the reports going through > > about panics in the NFS area and whatnot, but nothing in particular > > dealing with actually hangs... > > No. Make sure you've rebuilt your LKMs; there were changes there a little > while back. > Okay...re-rebuilding that...thanks... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Wed Oct 16 19:04:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA23030 for current-outgoing; Wed, 16 Oct 1996 19:04:25 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA23024 for ; Wed, 16 Oct 1996 19:04:19 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA09715; Thu, 17 Oct 1996 11:32:27 +0930 From: Michael Smith Message-Id: <199610170202.LAA09715@genesis.atrad.adelaide.edu.au> Subject: Re: scsi drives left locked by shutdown To: wollman@lcs.mit.edu (Garrett Wollman) Date: Thu, 17 Oct 1996 11:32:26 +0930 (CST) Cc: terry@lambert.org, julian@whistle.com, bde@zeta.org.au, current@FreeBSD.org In-Reply-To: <9610161909.AA09028@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Oct 16, 96 03:09:11 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Garrett Wollman stands accused of saying: > > > I second the motion of adding "detach" routines... it's very necessary > > for rundown on pluggable hardware (which, by definition, is also > > unpluggable). The driver needs to be able to "rundown" at any time. > > This was, of course, one of the principal features of devconf, which > Poul-Henning ripped out some months ago without so much as a > by-your-leave and has yet to even discuss a replacement for. Er. Having been through the device-driver authoring process a couple of times now, this is new to me. In all my research, I don't believe I ever turned up any documentation on devconf, or any inkling that it actually achieved anything other than as a somewhat complex backend to 'lsdev'. I certainly don't recall seeing anything that implied that it supported drivers 'going away', nor any indication that it fitted in with the other major 'transient device' model (PCCARD). If it had been your pet project on which you were spending lots of time, I would sympathise with your ire; as it is I'm just surprised. > -GAWollman -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Oct 16 19:07:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA23155 for current-outgoing; Wed, 16 Oct 1996 19:07:32 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA23138 for ; Wed, 16 Oct 1996 19:07:26 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA09780; Thu, 17 Oct 1996 11:36:51 +0930 From: Michael Smith Message-Id: <199610170206.LAA09780@genesis.atrad.adelaide.edu.au> Subject: Re: Bug with moused and XFree86 To: derm@iol.ie (Dermot McNally) Date: Thu, 17 Oct 1996 11:36:50 +0930 (CST) Cc: gibbs@freefall.freebsd.org, current@FreeBSD.org In-Reply-To: <3266af08.1754502@mail.indigo.ie> from "Dermot McNally" at Oct 16, 96 04:38:40 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Dermot McNally stands accused of saying: > > > >This should say "MouseSystems". Moused makes all mice look like > >MouseSystems mice. > > One thought here - is it still possible to switch on Emulate-3-buttons in > XF86Config with this setup? There doesn't seem to be any way to make > moused do this. If I remember correctly, the 3-button emulation is performed at a higher level in XF86 than the protocol-decoding module which made it into moused. Presuming that the server will not reject the emulation request because it's handling a 3-button mouse type, I would guess it should work OK. How about you try it and let us know if it works? > Dermot -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Oct 16 19:31:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA24671 for current-outgoing; Wed, 16 Oct 1996 19:31:26 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA24660 for ; Wed, 16 Oct 1996 19:31:14 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.6.12/8.6.12) with SMTP id TAA11255; Wed, 16 Oct 1996 19:30:53 -0700 Date: Wed, 16 Oct 1996 19:30:45 -0700 (PDT) From: Jaye Mathisen To: Nate Williams cc: Michael Hancock , current@FreeBSD.org Subject: Re: BSDI 3.0 feature list In-Reply-To: <199610160531.XAA09204@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Speaking as both a BSD/OS and FreeBSD user, I would find the following suspect: > I think you're mistaken. Almost every one of BSDi/3.0 'features' are > kernel features, and the # of kernel hackers in FreeBSD is about the > same as in BSDi. It's certainly a lot less than in something like > NetBSD, but it seems most of them spend all their time just trying to > keep their's kernel working (or get it working :) rather than doing lots > of new features. BSD/OS has made other significant improvements as well, and in fact, as I recall, has thrown a few bits back to the *BSD community as well. My fundamental issue with BSD/OS has always been driver support, where they support all kinds of weird serial cards, but couldn't find the vim/vigor to actually support a 2940W in Wide mode. Or heck, through 2 releases, Adaptec 29XX's at all. They seem to have kind of dropped by the wayside in terms of just about everything else though. Did the SPARC port ever appear? Their install is probably on a par with FreeBSD's now, I did a 2.1 install a couple of months ago, and other than a reversed test for the SMC de driver 10/100 mode, it was nice and clean. But if you want to pay for the support, there's nothing wrong with it. (As long as you realize that your upgrade contract consists of maybe 1 new release/year). From owner-freebsd-current Wed Oct 16 20:30:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA29098 for current-outgoing; Wed, 16 Oct 1996 20:30:50 -0700 (PDT) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA29092 for ; Wed, 16 Oct 1996 20:30:46 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.7.6/8.7.3) with SMTP id XAA22011; Wed, 16 Oct 1996 23:30:20 -0400 (EDT) Message-Id: <199610170330.XAA22011@whizzo.transsys.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Michael Smith cc: derm@iol.ie (Dermot McNally), gibbs@freefall.freebsd.org, current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Bug with moused and XFree86 References: <199610170206.LAA09780@genesis.atrad.adelaide.edu.au> In-reply-to: Your message of "Thu, 17 Oct 1996 11:36:50 +0930." <199610170206.LAA09780@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Oct 1996 23:30:20 -0400 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Funny, I was just hacking some new code into moused to support the Glidepoint trackpad, and I recall seeing a -c option to enable "ChordMiddle" for the two button Microsoft and Logitech MouseMan/Trackman pointing devices. Wouldn't this do what Dermot wanted? louie > Dermot McNally stands accused of saying: > > > > > >This should say "MouseSystems". Moused makes all mice look like > > >MouseSystems mice. > > > > One thought here - is it still possible to switch on Emulate-3-buttons in > > XF86Config with this setup? There doesn't seem to be any way to make > > moused do this. > > If I remember correctly, the 3-button emulation is performed at a > higher level in XF86 than the protocol-decoding module which made it > into moused. Presuming that the server will not reject the emulation > request because it's handling a 3-button mouse type, I would guess it > should work OK. > > How about you try it and let us know if it works? > > > Dermot > > -- > ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ > ]] Genesis Software genesis@atrad.adelaide.edu.au [[ > ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ > ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ > ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Oct 16 21:30:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA02291 for current-outgoing; Wed, 16 Oct 1996 21:30:15 -0700 (PDT) Received: from unix.guru.org (kmitch@unix.guru.org [198.82.200.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA02286 for ; Wed, 16 Oct 1996 21:30:11 -0700 (PDT) Received: (from kmitch@localhost) by unix.guru.org (8.7.6/8.7.3) id AAA01023 for current@freebsd.org; Thu, 17 Oct 1996 00:30:07 -0400 (EDT) From: Keith Mitchell Message-Id: <199610170430.AAA01023@unix.guru.org> Subject: Re: Weirdness in current In-Reply-To: from kmitch at "Oct 13, 96 11:34:30 am" To: kmitch@unix.guru.org (kmitch) Date: Thu, 17 Oct 1996 00:29:54 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I have a C++ program I wrote, and it works fine as long as you don't try to > > redirect the output. Doing so, causes it to core dump. Compiling the > > same program on a 2.1.0R system works fine though. > > I have a little more insight on this one. It appears that the same libraries > are not getting linked in on current as on stable (2.1.0 or 2.1.5). For > some reason the math library is getting linked in on stable even though > I don't tell it to and my program doesn't use it directly. Current doesn't > link in the math library. If I manually tell it to link in the math > library everything works fine. I don't have a clue why its doing this > on I/O redirection. Anyway here are the ldd outputs in hope that someone > will be able to find out what the problem is: Ok. Here's an update. I just did a make world from a 10-16 current. The dynamic linking now appears to work correctly using the math library by default. Anyone know why this is even necessary? It still fails when linking the program statically through the -Xlinker -Bstatic option. Thanks. From owner-freebsd-current Wed Oct 16 21:47:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA03240 for current-outgoing; Wed, 16 Oct 1996 21:47:48 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au ([129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA03232 for ; Wed, 16 Oct 1996 21:47:40 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id OAA11903; Thu, 17 Oct 1996 14:17:04 +0930 From: Michael Smith Message-Id: <199610170447.OAA11903@genesis.atrad.adelaide.edu.au> Subject: Re: Bug with moused and XFree86 To: louie@TransSys.COM (Louis A. Mamakos) Date: Thu, 17 Oct 1996 14:17:04 +0930 (CST) Cc: current@freebsd.org In-Reply-To: <199610170330.XAA22011@whizzo.transsys.com> from "Louis A. Mamakos" at Oct 16, 96 11:30:20 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Louis A. Mamakos stands accused of saying: > > Funny, I was just hacking some new code into moused to support the Glidepoint > trackpad, and I recall seeing a -c option to enable "ChordMiddle" for > the two button Microsoft and Logitech MouseMan/Trackman pointing devices. > > Wouldn't this do what Dermot wanted? No. "ChordMiddle" and "Emulate3Buttons" are significantly different. > louie -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Oct 16 22:33:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA06506 for current-outgoing; Wed, 16 Oct 1996 22:33:43 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA06500 for ; Wed, 16 Oct 1996 22:33:41 -0700 (PDT) Received: from spirit.ki.net (root@spirit.ki.net [205.150.102.51]) by quagmire.ki.net (8.7.5/8.7.5) with ESMTP id BAA03158 for ; Thu, 17 Oct 1996 01:33:43 -0400 (EDT) Received: from localhost (scrappy@localhost) by spirit.ki.net (8.7.5/8.7.3) with SMTP id BAA19516 for ; Thu, 17 Oct 1996 01:33:41 -0400 (EDT) X-Authentication-Warning: spirit.ki.net: scrappy owned process doing -bs Date: Thu, 17 Oct 1996 01:33:39 -0400 (EDT) From: "Marc G. Fournier" To: current@freebsd.org Subject: make re-makes for no apparent reason... 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... I know that generally you are supposed to do: make cleandir;make depend;make when rebuilding the source tree, and generally I do, but tonight I wanted to make sure that I had completed my compile of /usr/src/lib (ie. my recent crashes hadn't happened part way through). So, I just did a 'cd /usr/src/lib;make', but its recompiling everything from scratch again, as if the existing .o files don't already exist, but, as an ls shows, the libraries have already been built: quagmire# ls -lt libc* -rw-r--r-- 1 root wheel 621162 Oct 3 21:02 libc_pic.a -rwxr-xr-x 1 root wheel 433958 Oct 3 21:02 libc.so.3.0 -rw-r--r-- 1 root wheel 624072 Oct 3 20:35 libc_p.a -rw-r--r-- 1 root wheel 539202 Oct 3 20:03 libc.a Some of the files its trying to rebuild again are: quagmire# ls -l gen/getpass.c -rw-r--r-- 1 root wheel 4010 Jul 12 16:49 gen/getpass.c Which, other then the one it did recompile, was already compiled: quagmire# ls -lt getpass* -rwxr-xr-x 1 root wheel 1513 Oct 17 01:23 getpass.o -rw-r--r-- 1 root wheel 1644 Oct 3 21:03 getpass.3.gz -rwxr-xr-x 1 root wheel 1919 Oct 3 20:43 getpass.so -rwxr-xr-x 1 root wheel 1911 Oct 3 20:19 getpass.po So, gen/getpass.c (as one example), hasn't changed since Jul 12th, and was initially compiled on Oct 3rd...why does it feel that it has to compile it again? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Thu Oct 17 00:53:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA13127 for current-outgoing; Thu, 17 Oct 1996 00:53:02 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA13122 for ; Thu, 17 Oct 1996 00:53:00 -0700 (PDT) Received: from localhost (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with SMTP id AAA16588 for ; Thu, 17 Oct 1996 00:54:04 -0700 Date: Thu, 17 Oct 1996 00:54:03 -0700 (PDT) From: Veggy Vinny To: current@FreeBSD.ORG Subject: -current build fail Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Greetings everyone, A latest make world produced the following: lib/libc/rpc/rpc_callmsg.c /usr/src/lib/libc/rpc/svc.c /usr/src/lib/libc/rpc/svc_auth.c /usr/src/lib/libc/rpc/svc_auth_unix.c /usr/src/lib/libc/rpc/svc_raw.c /usr/src/lib/libc/rpc/svc_run.c /usr/src/lib/libc/rpc/svc_simple.c /usr/src/lib/libc/rpc/svc_tcp.c /usr/src/lib/libc/rpc/svc_udp.c /usr/src/lib/libc/xdr/xdr.c /usr/src/lib/libc/xdr/xdr_array.c /usr/src/lib/libc/xdr/xdr_float.c /usr/src/lib/libc/xdr/xdr_mem.c /usr/src/lib/libc/xdr/xdr_rec.c /usr/src/lib/libc/xdr/xdr_reference.c /usr/src/lib/libc/xdr/xdr_stdio.c /usr/src/lib/libc/yp/xdryp.c yp_xdr.c /usr/src/lib/libc/yp/yplib.c /usr/src/lib/libc/i386/sys/i386_get_ldt.c /usr/src/lib/libc/i386/sys/i386_set_ldt.c /usr/src/lib/libc/net/ns_addr.c:42: netns/ns.h: No such file or directory /usr/src/lib/libc/net/ns_ntoa.c:39: netns/ns.h: No such file or directory mkdep: compile failed. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. root@earth [12:37am][/usr/src] >> Anyone have any ideas? Vince From owner-freebsd-current Thu Oct 17 01:32:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA15815 for current-outgoing; Thu, 17 Oct 1996 01:32:10 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA15776 for ; Thu, 17 Oct 1996 01:32:06 -0700 (PDT) Received: from spirit.ki.net (root@spirit.ki.net [205.150.102.51]) by quagmire.ki.net (8.7.5/8.7.5) with ESMTP id EAA06781 for ; Thu, 17 Oct 1996 04:32:15 -0400 (EDT) Received: from localhost (scrappy@localhost) by spirit.ki.net (8.7.5/8.7.3) with SMTP id EAA05418 for ; Thu, 17 Oct 1996 04:32:08 -0400 (EDT) X-Authentication-Warning: spirit.ki.net: scrappy owned process doing -bs Date: Thu, 17 Oct 1996 04:32:02 -0400 (EDT) From: "Marc G. Fournier" To: current@freebsd.org Subject: Iozone: local vs nfs drives 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... I was trying to prove a point in news tonight between using an nfs mounted drive vs a local drive for a news server (one of the gentleman doesn't seem to believe there is a difference). My argument involved using iozone to show the throughput differences between nfs/local r/w's, and the results I got don't look right: this is my nfs mounted drive (133k/s and 382k/s): IOZONE performance measurements: 133152 bytes/second for writing the file 382386 bytes/second for reading the file vs local drive (1.78M/s and 938k/s): IOZONE performance measurements: 1784080 bytes/second for writing the file 938585 bytes/second for reading the file They look right in so far that I would expect the local file system to be faster then the remote...but I would also have expected that reading the local file would be faster the writing it, as was reflected in the nfs-mounted file system... Both systems are running 2.2-Current, same kernels, about 3 days old... I've tried varying the size of file iozone uses, up to a 30Meg file, and the results seem to be quite consistent: IOZONE performance measurements: 1984490 bytes/second for writing the file 1117239 bytes/second for reading the file Why would reading the file be half as fast as writing it? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Thu Oct 17 02:46:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA20151 for current-outgoing; Thu, 17 Oct 1996 02:46:43 -0700 (PDT) Received: from aoife.indigo.ie (aoife.indigo.ie [194.125.133.9]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA20145 for ; Thu, 17 Oct 1996 02:46:39 -0700 (PDT) Received: from ts07-08.dublin.indigo.ie (ts07-08.dublin.indigo.ie [194.125.148.133]) by aoife.indigo.ie (8.7.5/8.7.5) with SMTP id KAA22015; Thu, 17 Oct 1996 10:46:50 +0100 (BST) From: derm@iol.ie (Dermot McNally) To: "Louis A. Mamakos" Cc: current@FreeBSD.ORG Subject: Re: Bug with moused and XFree86 Date: Thu, 17 Oct 1996 09:44:46 GMT Organization: My House Message-ID: <3267ff1f.469588@mail.iol.ie> References: <199610170206.LAA09780@genesis.atrad.adelaide.edu.au> <199610170330.XAA22011@whizzo.transsys.com> In-Reply-To: <199610170330.XAA22011@whizzo.transsys.com> X-Mailer: Forte Agent .99f/32.299 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 16 Oct 1996 23:30:20 -0400, "Louis A. Mamakos" = wrote: >Funny, I was just hacking some new code into moused to support the = Glidepoint >trackpad, and I recall seeing a -c option to enable "ChordMiddle" for >the two button Microsoft and Logitech MouseMan/Trackman pointing = devices.=20 > >Wouldn't this do what Dermot wanted? I don't think so. I thought that ChordMiddle was more or less the = reverse - for enabling a _real_ third button on mice that had them. Dermot ----------------------------------------------------------- Dermot McNally, derm@iol.ie "OK, one last time. These are _small_, but the ones out there are _far = away_. _Small_........ _Far Away_." Father Ted. From owner-freebsd-current Thu Oct 17 02:46:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA20167 for current-outgoing; Thu, 17 Oct 1996 02:46:48 -0700 (PDT) Received: from aoife.indigo.ie (aoife.indigo.ie [194.125.133.9]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA20162 for ; Thu, 17 Oct 1996 02:46:45 -0700 (PDT) Received: from ts07-08.dublin.indigo.ie (ts07-08.dublin.indigo.ie [194.125.148.133]) by aoife.indigo.ie (8.7.5/8.7.5) with SMTP id KAA22010; Thu, 17 Oct 1996 10:46:48 +0100 (BST) From: derm@iol.ie (Dermot McNally) To: Michael Smith Cc: current@FreeBSD.org Subject: Re: Bug with moused and XFree86 Date: Thu, 17 Oct 1996 09:44:44 GMT Organization: My House Message-ID: <3266fed0.391430@mail.iol.ie> References: <199610170206.LAA09780@genesis.atrad.adelaide.edu.au> In-Reply-To: <199610170206.LAA09780@genesis.atrad.adelaide.edu.au> X-Mailer: Forte Agent .99f/32.299 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 17 Oct 1996 11:36:50 +0930 (CST), Michael Smith wrote: >If I remember correctly, the 3-button emulation is performed at a >higher level in XF86 than the protocol-decoding module which made it >into moused. Presuming that the server will not reject the emulation >request because it's handling a 3-button mouse type, I would guess it >should work OK. > >How about you try it and let us know if it works? I will, but I need to update to the latest SNAP first (I'm not current). Dermot ----------------------------------------------------------- Dermot McNally, derm@iol.ie "OK, one last time. These are _small_, but the ones out there are _far = away_. _Small_........ _Far Away_." Father Ted. From owner-freebsd-current Thu Oct 17 02:58:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA20616 for current-outgoing; Thu, 17 Oct 1996 02:58:37 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA20611 for ; Thu, 17 Oct 1996 02:58:34 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.6.12/8.6.12) with SMTP id CAA19951; Thu, 17 Oct 1996 02:58:21 -0700 Date: Thu, 17 Oct 1996 02:58:20 -0700 (PDT) From: Jaye Mathisen To: "Marc G. Fournier" cc: current@FreeBSD.org Subject: Re: Iozone: local vs nfs drives 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 would be interested in the answer to this, I see the same behaviour on a 2940/Quantum Atlas combo, although the numbers are quite a bit higher. :) In any case, given specifically the issue of news, where most activity is reading, this is disturbing. > vs local drive (1.78M/s and 938k/s): > IOZONE performance measurements: > 1784080 bytes/second for writing the file > 938585 bytes/second for reading the file > > From owner-freebsd-current Thu Oct 17 02:59:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA20678 for current-outgoing; Thu, 17 Oct 1996 02:59:05 -0700 (PDT) Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA20666 for ; Thu, 17 Oct 1996 02:59:02 -0700 (PDT) Received: from allegro.lemis.de by diablo.ppp.de with smtp (Smail3.1.28.1 #1) id m0vDoSH-000Qo5C; Thu, 17 Oct 96 10:09 MET From: grog@lemis.de (Greg Lehey) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Received: (grog@localhost) by allegro.lemis.de (8.6.9/8.6.9) id LAA01037; Thu, 17 Oct 1996 11:08:12 +0200 Message-Id: <199610170908.LAA01037@allegro.lemis.de> Subject: Re: ok, look folks To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 17 Oct 1996 11:08:12 +0200 (MET DST) Cc: FreeBSD-current@freebsd.org (FreeBSD current users) In-Reply-To: <21075.844855496@time.cdrom.com> from "Jordan K. Hubbard" at Oct 9, 96 03:04:56 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard writes: > >> True enough, but sometimes people don't *know* what they >> subscribed as. Not everyone is all that knowledgable about >> mail systems, or in control of the mail system they're using. > > No problem. > > 1. Send email to majordomo@freebsd.org saying "help". > 2. It sends you back a list of commands. > 3. You notice that one of those commands allows you to receive a copy > of all the users on a list. > 4. You figure out which one you are and you send the deletion request. > > I'm sorry, but this is an open and shut case of someone who found it > easier to yell and scream than do his homework. Well, I think I'm not completely stupid, and I've done some thinking about this problem, but this was the first indication I had that majordomo would give you a list of the subscribers, or that that is a possible way to get yourself off the list. To judge by the other messages on the list, I'm not alone, so you can't call it an open and shut case. But the idea's good, and I'll add it to the weekly message I sent to -questions. > Not the best of first impressions, and certainly one which will > stick with me for awhile. Never seen anybody flame before? To be fair to whoever the original flamer was (are you really going to carry his name around with you?), after the nth time, you can get really upset. It wasn't nice of him to carry on flaming once people had helped him, though. Greg From owner-freebsd-current Thu Oct 17 02:59:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA20712 for current-outgoing; Thu, 17 Oct 1996 02:59:32 -0700 (PDT) Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA20706; Thu, 17 Oct 1996 02:59:27 -0700 (PDT) Received: from allegro.lemis.de by diablo.ppp.de with smtp (Smail3.1.28.1 #1) id m0vDoSJ-000QoFC; Thu, 17 Oct 96 10:09 MET From: grog@lemis.de (Greg Lehey) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Received: (grog@localhost) by allegro.lemis.de (8.6.9/8.6.9) id LAA01018; Thu, 17 Oct 1996 11:03:04 +0200 Message-Id: <199610170903.LAA01018@allegro.lemis.de> Subject: Re: ok, look folks To: terry@lambert.org (Terry Lambert) Date: Thu, 17 Oct 1996 11:03:03 +0200 (MET DST) Cc: FreeBSD-current@freebsd.org (FreeBSD current users), chat@freebsd.org (FreeBSD Chat) In-Reply-To: <199610092041.NAA18678@phaeton.artisoft.com> from "Terry Lambert" at Oct 9, 96 01:41:11 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert writes: > >> (4) Save those useful and, apparently, ignored messages from >> majordomo when you subscribe. (Even make a mail-box >> file to keep them in) > > I suggested this before, and I'll suggest it again: > > Each list whould have a monthly "FAQ" posting that goes out automatically; > it would include "how to unsubscribe". Good idea. I think I'll do it. In fact, I've done it, about 2 weeks ago, on -questions ("How to get best results from FreeBSD-questions"; maybe I should change the subject line"). I've certainly learnt some stuff from this exchange, though, and Monday's version should be different again. Comments welcome. Greg From owner-freebsd-current Thu Oct 17 07:00:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA01560 for current-outgoing; Thu, 17 Oct 1996 07:00:03 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA01496 for ; Thu, 17 Oct 1996 06:59:55 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id HAA17511; Thu, 17 Oct 1996 07:59:08 -0600 (MDT) Date: Thu, 17 Oct 1996 07:59:08 -0600 (MDT) Message-Id: <199610171359.HAA17511@rocky.mt.sri.com> From: Nate Williams To: Keith Mitchell CC: current@freebsd.org Subject: Re: Weirdness in current In-Reply-To: <199610170430.AAA01023@unix.guru.org> References: <199610170430.AAA01023@unix.guru.org> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>> I have a C++ program I wrote, and it works fine as long as you don't try to >>> redirect the output. Doing so, causes it to core dump. Compiling the >>> same program on a 2.1.0R system works fine though. >> >> I have a little more insight on this one. It appears that the same libraries >> are not getting linked in on current as on stable (2.1.0 or 2.1.5). Note, gcc and libg++ have changed in -current vs. stable. >> For >> some reason the math library is getting linked in on stable even though >> I don't tell it to and my program doesn't use it directly. I don't know why. I just looked, and it's not being forced to... > Ok. Here's an update. I just did a make world from a 10-16 current. > The dynamic linking now appears to work correctly using the math library > by default. Are you saying the math library is brought in even if you don't explicitly ask for it? > Anyone know why this is even necessary? It still fails when > linking the program statically through the -Xlinker -Bstatic option. Note, there are known oustanding bugs (that will probably never get fixed with the current a.out toolchain) w/regards to different behavior in the linker when doing static/dynamic linking. I'm not sure if this is what you are seeing, but it does exist and is known about. The linker does *NOT* link the program the preference of the command line when mixing static/shared libraries, but instead 'preferes' shared libraries over their static counter-parts. Nate From owner-freebsd-current Thu Oct 17 07:32:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA03706 for current-outgoing; Thu, 17 Oct 1996 07:32:04 -0700 (PDT) Received: from unix.guru.org (kmitch@unix.guru.org [198.82.200.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA03677 for ; Thu, 17 Oct 1996 07:31:59 -0700 (PDT) Received: (from kmitch@localhost) by unix.guru.org (8.7.6/8.7.3) id KAA10456; Thu, 17 Oct 1996 10:31:50 -0400 (EDT) From: Keith Mitchell Message-Id: <199610171431.KAA10456@unix.guru.org> Subject: Re: Weirdness in current In-Reply-To: <199610171359.HAA17511@rocky.mt.sri.com> from Nate Williams at "Oct 17, 96 07:59:08 am" To: nate@mt.sri.com (Nate Williams) Date: Thu, 17 Oct 1996 10:31:50 -0400 (EDT) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Ok. Here's an update. I just did a make world from a 10-16 current. > > The dynamic linking now appears to work correctly using the math library > > by default. > > Are you saying the math library is brought in even if you don't > explicitly ask for it? Yes. It did that in 2.10R, 2.15R, -stable, and now again in -current. I have no idea why though. The program doesn't use any of the functions in the math library directly. And, without the math library the program core dumps (but ONLY on output redirection ;-<>). With the math library compiled in it works fine. > > Anyone know why this is even necessary? It still fails when > > linking the program statically through the -Xlinker -Bstatic option. > > Note, there are known oustanding bugs (that will probably never get > fixed with the current a.out toolchain) w/regards to different behavior > in the linker when doing static/dynamic linking. I'm not sure if this > is what you are seeing, but it does exist and is known about. > > The linker does *NOT* link the program the preference of the command > line when mixing static/shared libraries, but instead 'preferes' shared > libraries over their static counter-parts. Well, what I think is happening is that the static linking is not bringing in the math library like the dynamic one now does (see above). An ldd shows that the program is entirely static, but the program core dumps on output redirection, so I am inclined to believe it is not getting the math library. I wasn't trying to mix libraries either. I wanted to make it entirely static. NOTE: -current as of 10/9 did not bring in the math library by default. -current as of 09/01 behaved the same way (gcc 2.6.3). Also, If I make a "hello world" program and compile it with cc I get just the c library. If I compile it with c++, I get the c, math, and the stdc++ libraries. (This is as of 10/16 anyways). Thanks From owner-freebsd-current Thu Oct 17 09:14:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA09275 for current-outgoing; Thu, 17 Oct 1996 09:14:24 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA09269 for ; Thu, 17 Oct 1996 09:14:17 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA18147; Thu, 17 Oct 1996 10:13:59 -0600 (MDT) Date: Thu, 17 Oct 1996 10:13:59 -0600 (MDT) Message-Id: <199610171613.KAA18147@rocky.mt.sri.com> From: Nate Williams To: Keith Mitchell Cc: nate@mt.sri.com (Nate Williams), current@freebsd.org Subject: Re: Weirdness in current In-Reply-To: <199610171431.KAA10456@unix.guru.org> References: <199610171359.HAA17511@rocky.mt.sri.com> <199610171431.KAA10456@unix.guru.org> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Are you saying the math library is brought in even if you don't > > explicitly ask for it? > > Yes. It did that in 2.10R, 2.15R, -stable, and now again in -current. I don't see that on my -stable box, but it definitely happens in -current. It's done automatically in -current by the c++ driver on line 551 of /usr/src/contrib/cc/cp/g++.c. *RANT MODE ON* Did I mention that I *HATE* the new contrib scheme? It makes trying to debug programs a nightmare since the code is scattered everywhere across contrib, so a simply grep doesn't work very well. *RANT MODE OFF* In any case, the math library is linked into into *ALL* binaries, so 'static' vs 'shared' shouldn't make any difference. > I have no idea why though. The program doesn't use any of the > functions in the math library directly. And, without the math library > the program core dumps (but ONLY on output redirection ;-<>). With > the math library compiled in it works fine. It's linked into the static version, so why adding it again makes any difference is a mystery to me. An easy way to see what's happening is to use the '-v' flag to the compiler. EX: % setenv CC "cc -v" > Well, what I think is happening is that the static linking is not bringing > in the math library like the dynamic one now does (see above). Nope. At least, not on my system. > NOTE: -current as of 10/9 did not bring in the math library by > default. The file hasn't changed, so I don't see how it would not. > -current as of 09/01 behaved the same way (gcc 2.6.3). Right. Older versions of gcc didn't explicitly link in the math library. I don't know why it's being done, but the GCC folks hopefully have some reason (or it's a bug). > Also, If I make > a "hello world" program and compile it with cc I get just the c library. If > I compile it with c++, I get the c, math, and the stdc++ libraries. (This is > as of 10/16 anyways). Right. This is on purpose, since apparently the stdc++ libraries are necessary for almost *any* C++ program you write. Even the hello world program (using streams) won't link w/out stdc++. The math library thing is a mystery though.... Nate From owner-freebsd-current Thu Oct 17 09:22:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA09700 for current-outgoing; Thu, 17 Oct 1996 09:22:52 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA09695 for ; Thu, 17 Oct 1996 09:22:45 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id CAA01871; Fri, 18 Oct 1996 02:16:15 +1000 Date: Fri, 18 Oct 1996 02:16:15 +1000 From: Bruce Evans Message-Id: <199610171616.CAA01871@godzilla.zeta.org.au> To: kmitch@unix.guru.org, nate@mt.sri.com Subject: Re: Weirdness in current Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> > Ok. Here's an update. I just did a make world from a 10-16 current. >> > The dynamic linking now appears to work correctly using the math library >> > by default. >> >> Are you saying the math library is brought in even if you don't >> explicitly ask for it? > >Yes. It did that in 2.10R, 2.15R, -stable, and now again in -current. I >have no idea why though. The program doesn't use any of the functions in >the math library directly. And, without the math library the program Then it must use it indirectly :-). libstdc++ references a lot of math functions. This is handled by always linking libm for normal invocations of c++ (look at the c++ -v output). libg++ used to be linked to some other libraries, but isn't any more. This seems to be a bug. re_match_2 is undefined in libg++.a. It is defined in libgnuregex, which doesn't seem to be linked automatically. >Well, what I think is happening is that the static linking is not bringing >in the math library like the dynamic one now does (see above). An ldd shows c++ -v -static shows libm being brought in in much the same way as for non-static linking. It should work. Bruce From owner-freebsd-current Thu Oct 17 09:32:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA10309 for current-outgoing; Thu, 17 Oct 1996 09:32:01 -0700 (PDT) Received: from unix.guru.org (kmitch@unix.guru.org [198.82.200.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA10299 for ; Thu, 17 Oct 1996 09:31:49 -0700 (PDT) Received: (from kmitch@localhost) by unix.guru.org (8.7.6/8.7.3) id MAA17823; Thu, 17 Oct 1996 12:31:22 -0400 (EDT) From: Keith Mitchell Message-Id: <199610171631.MAA17823@unix.guru.org> Subject: Re: Weirdness in current In-Reply-To: <199610171613.KAA18147@rocky.mt.sri.com> from Nate Williams at "Oct 17, 96 10:13:59 am" To: nate@mt.sri.com (Nate Williams) Date: Thu, 17 Oct 1996 12:31:22 -0400 (EDT) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Are you saying the math library is brought in even if you don't > > > explicitly ask for it? > > > > Yes. It did that in 2.10R, 2.15R, -stable, and now again in -current. > > I don't see that on my -stable box, but it definitely happens in > -current. > > It's done automatically in -current by the c++ driver on line 551 of > /usr/src/contrib/cc/cp/g++.c. > I verfied that it was bringing in the math library in the static and the dynamic one, but the program core dumps in the static one much like it did before it compiled in the math library. I find it especially strange that it *ONLY* core dumps on output redirection. Interactive use of the program works fine. From owner-freebsd-current Thu Oct 17 09:32:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA10405 for current-outgoing; Thu, 17 Oct 1996 09:32:40 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA10397 for ; Thu, 17 Oct 1996 09:32:35 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA18263; Thu, 17 Oct 1996 10:32:25 -0600 (MDT) Date: Thu, 17 Oct 1996 10:32:25 -0600 (MDT) Message-Id: <199610171632.KAA18263@rocky.mt.sri.com> From: Nate Williams To: Keith Mitchell Cc: nate@mt.sri.com (Nate Williams), current@freebsd.org Subject: Re: Weirdness in current In-Reply-To: <199610171631.MAA17823@unix.guru.org> References: <199610171613.KAA18147@rocky.mt.sri.com> <199610171631.MAA17823@unix.guru.org> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Keith Mitchell writes: > > > > Are you saying the math library is brought in even if you don't > > > > explicitly ask for it? > > > > > > Yes. It did that in 2.10R, 2.15R, -stable, and now again in -current. > > > > I don't see that on my -stable box, but it definitely happens in > > -current. > > > > It's done automatically in -current by the c++ driver on line 551 of > > /usr/src/contrib/cc/cp/g++.c. > > I verfied that it was bringing in the math library in the static and the > dynamic one, but the program core dumps in the static one much like it did > before it compiled in the math library. I find it especially > strange that it *ONLY* core dumps on output redirection. Interactive use of > the program works fine. Where is it dumping core? From owner-freebsd-current Thu Oct 17 09:33:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA10464 for current-outgoing; Thu, 17 Oct 1996 09:33:22 -0700 (PDT) Received: from unix.guru.org (kmitch@unix.guru.org [198.82.200.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA10455 for ; Thu, 17 Oct 1996 09:33:15 -0700 (PDT) Received: (from kmitch@localhost) by unix.guru.org (8.7.6/8.7.3) id MAA17938; Thu, 17 Oct 1996 12:33:01 -0400 (EDT) From: Keith Mitchell Message-Id: <199610171633.MAA17938@unix.guru.org> Subject: Re: Weirdness in current In-Reply-To: <199610171616.CAA01871@godzilla.zeta.org.au> from Bruce Evans at "Oct 18, 96 02:16:15 am" To: bde@zeta.org.au (Bruce Evans) Date: Thu, 17 Oct 1996 12:33:01 -0400 (EDT) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> > Ok. Here's an update. I just did a make world from a 10-16 current. > >> > The dynamic linking now appears to work correctly using the math library > >> > by default. > >> > >> Are you saying the math library is brought in even if you don't > >> explicitly ask for it? > > > >Yes. It did that in 2.10R, 2.15R, -stable, and now again in -current. I > >have no idea why though. The program doesn't use any of the functions in > >the math library directly. And, without the math library the program > > Then it must use it indirectly :-). libstdc++ references a lot of math > functions. This is handled by always linking libm for normal invocations > of c++ (look at the c++ -v output). Forgive me, I am somewhat naive when it comes to the interworkings of the linker, but if it needed the library and didn't get it would it not just have unresolved references and not compile? From owner-freebsd-current Thu Oct 17 09:36:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA10774 for current-outgoing; Thu, 17 Oct 1996 09:36:30 -0700 (PDT) Received: from tatooine.vader.org (tatooine.vader.org [194.159.100.200]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA10767 for ; Thu, 17 Oct 1996 09:36:26 -0700 (PDT) Received: (from chris@localhost) by tatooine.vader.org (8.8.0/8.8.0) id RAA01857; Thu, 17 Oct 1996 17:35:57 +0100 (BST) From: Chris Dabrowski Message-Id: <199610171635.RAA01857@tatooine.vader.org> Subject: Re: system hangs with current kernel...? In-Reply-To: from "Marc G. Fournier" at "Oct 16, 96 08:03:02 pm" To: scrappy@ki.net (Marc G. Fournier) Date: Thu, 17 Oct 1996 17:35:57 +0100 (BST) Cc: current@FreeBSD.org Reply-To: chris@vader.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 In a previous message, Marc G. Fournier wrote: > > This is getting slightly annoying, so I figured I'd bring it to > the list... > > Has anyone noticed a recent problem with the -current kernel > that is causing system hangs? I've seen the reports going through > about panics in the NFS area and whatnot, but nothing in particular > dealing with actually hangs... > > I'm running -current as of about Sunday night, and this morning > the system locked up completely as if it was a SCSI bus hang...something > I haven't experienced in *many* months on that machine. It did it last > night too, and I recompiled a kernel with debugging enabled, but, of course, > if it doesn't panic, it doesn't dump core :( > Yes, it happens to me too. However, I've noticed one strange phenomenon. Before the system hangs completely, connections to port 119 (INN 1.4unoff4) timeout whilst other services (21, 25, etc) are unaffected. Maybe it's because INN uses the disk intensively and hence hammers the SCSI code more. I'm not much of a hacker myself but are there any tests or info that I can provide to help? chris@tatooine.vader.org:/home/chris $ uname -a FreeBSD tatooine.vader.org 2.2-CURRENT FreeBSD 2.2-CURRENT #0: Wed Oct 16 23:57:37 BST 1996 chris@tatooine.vader.org:/usr/src/sys/compile/TATOOINE i386 Pentium 100 48Mb RAM Adaptec 2940 PCI HP 2Gb Hard Drive 4.4x CD-ROM Chris -- Chris Dabrowski chris@vader.org From owner-freebsd-current Thu Oct 17 10:10:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA12898 for current-outgoing; Thu, 17 Oct 1996 10:10:50 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA12867 for ; Thu, 17 Oct 1996 10:10:33 -0700 (PDT) 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 SAA08837 for ; Thu, 17 Oct 1996 18:10:33 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id SAA00887 for freebsd-current@freefall.cdrom.com; Thu, 17 Oct 1996 18:15:50 +0100 Date: Thu, 17 Oct 1996 18:15:50 +0100 From: Christoph Kukulies Message-Id: <199610171715.SAA00887@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: 1014 SNAP fixit broken Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I boot the 1014-SNAP boot.flp, choose Fixit and after the fixit floppy has been inserted it escapes to a shell. Typing ls or df results in a core dump and an unusable fixit system. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Thu Oct 17 10:11:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA12961 for current-outgoing; Thu, 17 Oct 1996 10:11:09 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA12952 for ; Thu, 17 Oct 1996 10:11:07 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id RAA25591; Thu, 17 Oct 1996 17:10:53 GMT Date: Fri, 18 Oct 1996 02:10:53 +0900 (JST) From: Michael Hancock To: Jaye Mathisen cc: "Marc G. Fournier" , current@freebsd.org Subject: Re: Iozone: local vs nfs drives In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 17 Oct 1996, Jaye Mathisen wrote: > > > I would be interested in the answer to this, I see the same behaviour on > a 2940/Quantum Atlas combo, although the numbers are quite a bit higher. > :) > > In any case, given specifically the issue of news, where most activity is > reading, this is disturbing. IOZONE isn't the benchmark to use to determine news performance. FFS and the file buffering used aren't optimized for reading large files. Regards, Mike Hancock From owner-freebsd-current Thu Oct 17 10:31:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA14760 for current-outgoing; Thu, 17 Oct 1996 10:31:55 -0700 (PDT) Received: from covina.lightside.com (covina.lightside.com [207.67.176.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA14755 for ; Thu, 17 Oct 1996 10:31:52 -0700 (PDT) Received: from localhost (jehamby@localhost) by covina.lightside.com (8.8.0/8.8.0) with SMTP id KAA00030; Thu, 17 Oct 1996 10:31:33 -0700 (PDT) Date: Thu, 17 Oct 1996 10:31:31 -0700 (PDT) From: Jake Hamby To: Jaye Mathisen cc: "Marc G. Fournier" , current@freebsd.org Subject: Re: Iozone: local vs nfs drives In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 17 Oct 1996, Jaye Mathisen wrote: > > > I would be interested in the answer to this, I see the same behaviour on > a 2940/Quantum Atlas combo, although the numbers are quite a bit higher. > :) > > In any case, given specifically the issue of news, where most activity is > reading, this is disturbing. > > > vs local drive (1.78M/s and 938k/s): > > IOZONE performance measurements: > > 1784080 bytes/second for writing the file > > 938585 bytes/second for reading the file I'm not a filesystem expert, but the results sound normal to me. Writing is _often_ faster than reading on modern operating systems and hard drives that I've used. Both the OS and the hard drive cache the data as it's being written and are therefore able to stream it out to the disk as fast as possible. However, for reads, the program has to request the data, _then_ the hard drive has to fetch it, _then_ it has to move from the buffer cache into your program, while your program is waiting, and can't submit the next request. So whereas with writes you are pushing the data out to disk and the write buffering works in your favor, with reads you are pulling data from the disk and there is extra latency while your program is captive waiting for the request. At least that's how I would explain the situation. Can any FS hackers confirm/reject my hypothesis? -- Jake From owner-freebsd-current Thu Oct 17 11:03:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA17286 for current-outgoing; Thu, 17 Oct 1996 11:03:49 -0700 (PDT) Received: from unix.guru.org (kmitch@unix.guru.org [198.82.200.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA17275 for ; Thu, 17 Oct 1996 11:03:43 -0700 (PDT) Received: (from kmitch@localhost) by unix.guru.org (8.7.6/8.7.3) id OAA23823; Thu, 17 Oct 1996 14:03:12 -0400 (EDT) From: Keith Mitchell Message-Id: <199610171803.OAA23823@unix.guru.org> Subject: Re: Weirdness in current In-Reply-To: <199610171632.KAA18263@rocky.mt.sri.com> from Nate Williams at "Oct 17, 96 10:32:25 am" To: nate@mt.sri.com (Nate Williams) Date: Thu, 17 Oct 1996 14:03:12 -0400 (EDT) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Where is it dumping core? > I checked my program again and did find a small bug in it that would cause it to reference an array out of bounds. Its amazing that compiling in the math library would fix this and the dynamic/static executable made a difference. ;-) And at that only on output redirection. Go Figure. ;->> Keith From owner-freebsd-current Thu Oct 17 11:03:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA17307 for current-outgoing; Thu, 17 Oct 1996 11:03:56 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA17298 for ; Thu, 17 Oct 1996 11:03:51 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id TAA28764 for ; Thu, 17 Oct 1996 19:02:48 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id UAA06681 for current@freebsd.org; Thu, 17 Oct 1996 20:02:02 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.0/keltia-uucp-2.9) id TAA16521; Thu, 17 Oct 1996 19:28:52 +0200 (MET DST) Message-Id: <199610171728.TAA16521@keltia.freenix.fr> Date: Thu, 17 Oct 1996 19:28:52 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: current@freebsd.org Subject: Re: make re-makes for no apparent reason... In-Reply-To: ; from Marc G. Fournier on Oct 17, 1996 01:33:39 -0400 References: X-Mailer: Mutt 0.47.13 Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-CURRENT ctm#2584 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Marc G. Fournier: > So, gen/getpass.c (as one example), hasn't changed since > Jul 12th, and was initially compiled on Oct 3rd...why does it > feel that it has to compile it again? Change in an #include file for example. That's what .depend is for... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #25: Tue Oct 15 21:13:57 MET DST 1996 From owner-freebsd-current Thu Oct 17 11:05:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA17440 for current-outgoing; Thu, 17 Oct 1996 11:05:28 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA17430 for ; Thu, 17 Oct 1996 11:05:24 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA19142; Thu, 17 Oct 1996 12:05:15 -0600 (MDT) Date: Thu, 17 Oct 1996 12:05:15 -0600 (MDT) Message-Id: <199610171805.MAA19142@rocky.mt.sri.com> From: Nate Williams To: Keith Mitchell Cc: nate@mt.sri.com (Nate Williams), current@freebsd.org Subject: Re: Weirdness in current In-Reply-To: <199610171803.OAA23823@unix.guru.org> References: <199610171632.KAA18263@rocky.mt.sri.com> <199610171803.OAA23823@unix.guru.org> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Where is it dumping core? > > I checked my program again and did find a small bug in it that would cause > it to reference an array out of bounds. Its amazing that compiling in the > math library would fix this and the dynamic/static executable made a > difference. ;-) And at that only on output redirection. Go Figure. ;->> Stack corruption bugs are a *bugger* to find. The program has a completely different 'memory' allocation setup when used static vs. shared libraries due to mmap() usage in the shlib loader. In any case, we're glad everything's working now. :) Nate From owner-freebsd-current Thu Oct 17 11:40:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA20111 for current-outgoing; Thu, 17 Oct 1996 11:40:52 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA20067; Thu, 17 Oct 1996 11:40:27 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id UAA04107; Thu, 17 Oct 1996 20:39:12 +0200 (MET DST) To: Nate Williams cc: Keith Mitchell , current@freebsd.org Subject: Re: Weirdness in current In-reply-to: Your message of "Thu, 17 Oct 1996 12:05:15 MDT." <199610171805.MAA19142@rocky.mt.sri.com> Date: Thu, 17 Oct 1996 20:39:12 +0200 Message-ID: <4105.845577552@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199610171805.MAA19142@rocky.mt.sri.com>, Nate Williams writes: >> > Where is it dumping core? >> >> I checked my program again and did find a small bug in it that would cause >> it to reference an array out of bounds. Its amazing that compiling in the >> math library would fix this and the dynamic/static executable made a >> difference. ;-) And at that only on output redirection. Go Figure. ;->> > >Stack corruption bugs are a *bugger* to find. The program has a >completely different 'memory' allocation setup when used static >vs. shared libraries due to mmap() usage in the shlib loader. > >In any case, we're glad everything's working now. :) I don't know of any reliable & simple way to catch that kind of bug. I once made a gross hack on a Pyramid, such that checksum of the stack was made at every function call and record written to file at the return recording match/nomatch. Crude but it worked :-) -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Thu Oct 17 11:46:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA20773 for current-outgoing; Thu, 17 Oct 1996 11:46:12 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA20766 for ; Thu, 17 Oct 1996 11:46:06 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA19565; Thu, 17 Oct 1996 12:45:44 -0600 (MDT) Date: Thu, 17 Oct 1996 12:45:44 -0600 (MDT) Message-Id: <199610171845.MAA19565@rocky.mt.sri.com> From: Nate Williams To: Poul-Henning Kamp Cc: Nate Williams , current@freebsd.org Subject: Re: Weirdness in current In-Reply-To: <4105.845577552@critter.tfs.com> References: <199610171805.MAA19142@rocky.mt.sri.com> <4105.845577552@critter.tfs.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >Stack corruption bugs are a *bugger* to find. > > I don't know of any reliable & simple way to catch that kind of bug. Port your software to SunOS/Slolaris and run Purify on it. :) > I once made a gross hack on a Pyramid, such that checksum of the stack > was made at every function call and record written to file at the > return recording match/nomatch. This is basically what Purify does.. Nate From owner-freebsd-current Thu Oct 17 12:04:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA22145 for current-outgoing; Thu, 17 Oct 1996 12:04:43 -0700 (PDT) Received: from noc.msc.edu (noc.msc.edu [137.66.12.254]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA22140 for ; Thu, 17 Oct 1996 12:04:40 -0700 (PDT) Received: from uc.msc.edu by noc.msc.edu (5.65/MSC/v3.0.1(920324)) id AA03913; Thu, 17 Oct 96 14:04:34 -0500 Received: from fergus-2.dialup.prtel.com by uc.msc.edu (5.65/MSC/v3.0z(901212)) id AA29454; Thu, 17 Oct 96 14:04:31 -0500 Received: (from alk@localhost) by compound.Think.COM (8.7.6/8.7.3) id OAA08777; Thu, 17 Oct 1996 14:04:31 -0500 (CDT) Date: Thu, 17 Oct 1996 14:04:31 -0500 (CDT) From: Tony Kimball Message-Id: <199610171904.OAA08777@compound.Think.COM> To: current@freebsd.org Subject: cvs-cur 2592 build fail in usr.sbin/tcpdump/tcpdump Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk cvs-cur 2592 ; make depend /usr/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-udp.c:51: nfsv2.h: No such file or directory mkdep: compile failed. Something like this will fix it, although I'm sure it's not conventional: Index: Makefile =================================================================== RCS file: /proj/repository/FreeBSD/src/usr.sbin/tcpdump/tcpdump/Makefile,v retrieving revision 1.14 diff -r1.14 Makefile 24c24 < CFLAGS+= -I${TCPDUMP_DISTDIR}/lbl --- > CFLAGS+= -I${TCPDUMP_DISTDIR}/lbl -I${.CURDIR}/../../../sys/nfs From owner-freebsd-current Thu Oct 17 12:07:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA22233 for current-outgoing; Thu, 17 Oct 1996 12:07:16 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA22226 for ; Thu, 17 Oct 1996 12:07:14 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA06333; Thu, 17 Oct 1996 12:04:10 -0700 From: Terry Lambert Message-Id: <199610171904.MAA06333@phaeton.artisoft.com> Subject: Re: Iozone: local vs nfs drives To: jehamby@lightside.com (Jake Hamby) Date: Thu, 17 Oct 1996 12:04:10 -0700 (MST) Cc: mrcpu@cdsnet.net, scrappy@ki.net, current@freebsd.org In-Reply-To: from "Jake Hamby" at Oct 17, 96 10:31:31 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > vs local drive (1.78M/s and 938k/s): > > > IOZONE performance measurements: > > > 1784080 bytes/second for writing the file > > > 938585 bytes/second for reading the file > > I'm not a filesystem expert, but the results sound normal to me. Writing > is _often_ faster than reading on modern operating systems and hard > drives that I've used. Both the OS and the hard drive cache the data as > it's being written and are therefore able to stream it out to the disk as > fast as possible. However, for reads, the program has to request the > data, _then_ the hard drive has to fetch it, _then_ it has to move from > the buffer cache into your program, while your program is waiting, and > can't submit the next request. > > So whereas with writes you are pushing the data out to disk and the write > buffering works in your favor, with reads you are pulling data from the > disk and there is extra latency while your program is captive waiting for > the request. At least that's how I would explain the situation. > > Can any FS hackers confirm/reject my hypothesis? When you do a write not aligned on a block boundry offset into the file, the file is paged in (read), modified, and written out. In other words, expect writes to: 1) cost as much as a read, and then some 2) cost more proportional to the write block size relative to the page size I would personally epxect writes to be slower than reads. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Thu Oct 17 12:18:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA22973 for current-outgoing; Thu, 17 Oct 1996 12:18:49 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA22968 for ; Thu, 17 Oct 1996 12:18:46 -0700 (PDT) Received: from spirit.ki.net (root@spirit.ki.net [205.150.102.51]) by quagmire.ki.net (8.7.5/8.7.5) with ESMTP id PAA13118; Thu, 17 Oct 1996 15:18:46 -0400 (EDT) Received: from localhost (scrappy@localhost) by spirit.ki.net (8.7.5/8.7.3) with SMTP id PAA10535; Thu, 17 Oct 1996 15:18:41 -0400 (EDT) X-Authentication-Warning: spirit.ki.net: scrappy owned process doing -bs Date: Thu, 17 Oct 1996 15:18:37 -0400 (EDT) From: "Marc G. Fournier" To: Michael Hancock cc: Jaye Mathisen , current@freebsd.org Subject: Re: Iozone: local vs nfs drives 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 Fri, 18 Oct 1996, Michael Hancock wrote: > On Thu, 17 Oct 1996, Jaye Mathisen wrote: > > > > > > > I would be interested in the answer to this, I see the same behaviour on > > a 2940/Quantum Atlas combo, although the numbers are quite a bit higher. > > :) > > > > In any case, given specifically the issue of news, where most activity is > > reading, this is disturbing. > > IOZONE isn't the benchmark to use to determine news performance. > Actually, both my IOZONE tests were done on "non-news" drives... they were done on /usr, on relatively dead systems.. Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Thu Oct 17 12:22:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA23266 for current-outgoing; Thu, 17 Oct 1996 12:22:36 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA23247; Thu, 17 Oct 1996 12:22:15 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id VAA04245; Thu, 17 Oct 1996 21:21:11 +0200 (MET DST) To: Nate Williams cc: current@FreeBSD.org Subject: Re: Weirdness in current In-reply-to: Your message of "Thu, 17 Oct 1996 12:45:44 MDT." <199610171845.MAA19565@rocky.mt.sri.com> Date: Thu, 17 Oct 1996 21:21:11 +0200 Message-ID: <4243.845580071@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <199610171845.MAA19565@rocky.mt.sri.com>, Nate Williams writes: >> >Stack corruption bugs are a *bugger* to find. >> >> I don't know of any reliable & simple way to catch that kind of bug. > >Port your software to SunOS/Slolaris and run Purify on it. :) > >> I once made a gross hack on a Pyramid, such that checksum of the stack >> was made at every function call and record written to file at the >> return recording match/nomatch. > >This is basically what Purify does.. I said "simple" what Purify does can hardly be called "simple" :-) -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Thu Oct 17 12:59:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA25490 for current-outgoing; Thu, 17 Oct 1996 12:59:23 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA25485; Thu, 17 Oct 1996 12:59:19 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA20119; Thu, 17 Oct 1996 13:58:38 -0600 (MDT) Date: Thu, 17 Oct 1996 13:58:38 -0600 (MDT) Message-Id: <199610171958.NAA20119@rocky.mt.sri.com> From: Nate Williams To: dyson@freebsd.org Cc: current@freebsd.org Subject: Re: How is the NFS forcible dismount patch running? In-Reply-To: <199610161412.JAA03363@dyson.iquest.net> References: <199610161412.JAA03363@dyson.iquest.net> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John S. Dyson writes: > Hopefully the AMD (automounter) problems are pretty much gone? I didn't get time to update my box to -current until this morning, and with the patch in place here are my results. Setup: client : P75/24MB -current as of late last night options: rw,soft,intr,bg,noauto server : Ultra Sparc Slolaris 2.5 Test: client # cd /nfs client # tar cf - /dev/null . & client # tar cf /dev/null . & client # tar: read error at byte 0, reading 1024 bytes, in file tmp/ssh/ssh-1.2.12/servconf.h : Interrupted system call Even so, it ran to completion after a couple hours. :) (The exported FS takes up most of a 4GB disk). Nate From owner-freebsd-current Thu Oct 17 13:11:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA26200 for current-outgoing; Thu, 17 Oct 1996 13:11:20 -0700 (PDT) Received: from ratatosk.algonet.se (mail.algonet.se [194.213.74.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA26190 for ; Thu, 17 Oct 1996 13:11:13 -0700 (PDT) Received: from (johang@bengt.algonet.se [194.213.74.14]) by ratatosk.algonet.se (8.7.4/hdw.1.0) with SMTP id WAA16753 for ; Thu, 17 Oct 1996 22:11:31 +0200 (MET DST) Message-Id: <199610172011.WAA16753@ratatosk.algonet.se> Comments: Authenticated sender is From: "Johan Granlund" To: freebsd-current@FreeBSD.org Date: Thu, 17 Oct 1996 22:04:37 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Pro 100B driver working? Priority: normal X-mailer: Pegasus Mail for Win32 (v2.42a) Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi After that one of my 3c509 cards went pof, i bought 2 Intel Pro 100B Ethercards. Both cards seems to work when using the testsoftware that came with the cards, including using a echoserver. The problem is that i cant get anything from it on the FreeBSD box. Arp gets a new entry, but not even ping gets thru. Every other minute i get a timeoutmessage. Any ideas? The printerport is on IRQ5 Intel Endevour motherboard ---------------------------------------------------------------------- Oct 17 20:13:11 phoenix /kernel: fxp0 rev 1 int a irq 7 on pci0:16 Oct 17 20:13:11 phoenix /kernel: mapreg[10] type=0 addr=fffbe000 size=1000. Oct 17 20:13:11 phoenix /kernel: mapreg[14] type=1 addr=0000ff80 size=0020. Oct 17 20:13:11 phoenix /kernel: mapreg[18] type=0 addr=ffe00000 size=100000. Oct 17 20:13:11 phoenix /kernel: reg16: virtual=0xf4879000 physical=0xfffbe000 size=0x1000 Oct 17 20:13:11 phoenix /kernel: fxp0: Ethernet address 00:a0:c9:22:e3:89 Oct 17 20:13:11 phoenix /kernel: bpf: fxp0 attached ---------------------------------------------------------------------- Oct 17 20:15:26 phoenix /kernel: fxp0: device timeout ___________________________________________________________ Internet: Johang@Algonet.se I don't even speak for myself From owner-freebsd-current Thu Oct 17 13:54:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA29069 for current-outgoing; Thu, 17 Oct 1996 13:54:53 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA29062 for ; Thu, 17 Oct 1996 13:54:48 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id NAA17871; Thu, 17 Oct 1996 13:54:41 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id NAA12845; Thu, 17 Oct 1996 13:54:31 -0700 (PDT) Message-Id: <199610172054.NAA12845@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Marc G. Fournier" cc: Michael Hancock , Jaye Mathisen , current@freebsd.org Subject: Re: Iozone: local vs nfs drives In-reply-to: Your message of Thu, 17 Oct 96 15:18:37 -0400. Date: Thu, 17 Oct 1996 13:54:31 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Fri, 18 Oct 1996, Michael Hancock wrote: >> On Thu, 17 Oct 1996, Jaye Mathisen wrote: >> > I would be interested in the answer to this, I see the same behaviour on >> > a 2940/Quantum Atlas combo, although the numbers are quite a bit higher. >> > In any case, given specifically the issue of news, where most activity is >> > reading, this is disturbing. >> IOZONE isn't the benchmark to use to determine news performance. > Actually, both my IOZONE tests were done on "non-news" drives... >they were done on /usr, on relatively dead systems.. Did you have tagged-command queuing enabled? According to my tests, that will make a BIG difference, if you have decent drives. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-current Thu Oct 17 13:59:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA29291 for current-outgoing; Thu, 17 Oct 1996 13:59:00 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA29282 for ; Thu, 17 Oct 1996 13:58:55 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id NAA18026; Thu, 17 Oct 1996 13:58:57 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id NAA12875; Thu, 17 Oct 1996 13:58:44 -0700 (PDT) Message-Id: <199610172058.NAA12875@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Keith Mitchell cc: nate@mt.sri.com (Nate Williams), current@freebsd.org Subject: Re: Weirdness in current In-reply-to: Your message of Thu, 17 Oct 96 14:03:12 -0400. <199610171803.OAA23823@unix.guru.org> Date: Thu, 17 Oct 1996 13:58:44 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Where is it dumping core? >I checked my program again and did find a small bug in it that would cause >it to reference an array out of bounds. Its amazing that compiling in the >math library would fix this and the dynamic/static executable made a >difference. ;-) And at that only on output redirection. Go Figure. ;->> Not necessarily. Compiling in the math library may have given you just enough extra allocated memory somewhere that you were writing into valid memory, even if it was out of your stack bounds. Lacking the math library may have made that particular area of memory non-allocated. Asserts are a developer's best friend. Assert! Assert! Assert! ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-current Thu Oct 17 14:00:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA29436 for current-outgoing; Thu, 17 Oct 1996 14:00:16 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA29422 for ; Thu, 17 Oct 1996 14:00:09 -0700 (PDT) Received: from spirit.ki.net (root@spirit.ki.net [205.150.102.51]) by quagmire.ki.net (8.7.5/8.7.5) with ESMTP id RAA19601; Thu, 17 Oct 1996 17:00:16 -0400 (EDT) Received: from localhost (scrappy@localhost) by spirit.ki.net (8.7.5/8.7.3) with SMTP id RAA27320; Thu, 17 Oct 1996 17:00:09 -0400 (EDT) X-Authentication-Warning: spirit.ki.net: scrappy owned process doing -bs Date: Thu, 17 Oct 1996 17:00:06 -0400 (EDT) From: "Marc G. Fournier" To: "Michael L. VanLoon -- HeadCandy.com" cc: Michael Hancock , Jaye Mathisen , current@freebsd.org Subject: Re: Iozone: local vs nfs drives In-Reply-To: <199610172054.NAA12845@MindBender.serv.net> 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, 17 Oct 1996, Michael L. VanLoon -- HeadCandy.com wrote: > > >On Fri, 18 Oct 1996, Michael Hancock wrote: > > >> On Thu, 17 Oct 1996, Jaye Mathisen wrote: > > >> > I would be interested in the answer to this, I see the same behaviour on > >> > a 2940/Quantum Atlas combo, although the numbers are quite a bit higher. > >> > In any case, given specifically the issue of news, where most activity is > >> > reading, this is disturbing. > > >> IOZONE isn't the benchmark to use to determine news performance. > > > Actually, both my IOZONE tests were done on "non-news" drives... > >they were done on /usr, on relatively dead systems.. > > Did you have tagged-command queuing enabled? According to my tests, > that will make a BIG difference, if you have decent drives. > I don't know...I haven't enabled it manually, so I would assume not. How do I check/enable it? Any caveats I should worry about? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Thu Oct 17 14:01:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA29562 for current-outgoing; Thu, 17 Oct 1996 14:01:51 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA29554 for ; Thu, 17 Oct 1996 14:01:47 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id OAA18138; Thu, 17 Oct 1996 14:01:38 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id OAA12933; Thu, 17 Oct 1996 14:01:28 -0700 (PDT) Message-Id: <199610172101.OAA12933@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Michael Hancock cc: Jaye Mathisen , "Marc G. Fournier" , current@freebsd.org Subject: Re: Iozone: local vs nfs drives In-reply-to: Your message of Fri, 18 Oct 96 02:10:53 +0900. Date: Thu, 17 Oct 1996 14:01:27 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Thu, 17 Oct 1996, Jaye Mathisen wrote: >> I would be interested in the answer to this, I see the same behaviour on >> a 2940/Quantum Atlas combo, although the numbers are quite a bit higher. >> In any case, given specifically the issue of news, where most activity is >> reading, this is disturbing. >IOZONE isn't the benchmark to use to determine news performance. >FFS and the file buffering used aren't optimized for reading large files. To elaborate, iozone reads and writes one large file. News reads and writes lots of little files all over the place. Even bonnie is a poor approximation for news. At least bonnie does a lot more that read and write a buffer. But it still works in one large file. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-current Thu Oct 17 14:28:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA01318 for current-outgoing; Thu, 17 Oct 1996 14:28:33 -0700 (PDT) Received: from itchy.mindspring.com (itchy.mindspring.com [204.180.128.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA01230 for ; Thu, 17 Oct 1996 14:27:56 -0700 (PDT) Received: from rlb.users.mindspring.com (user-168-121-25-139.dialup.mindspring.com [168.121.25.139]) by itchy.mindspring.com (8.7.5/8.7.3) with SMTP id RAA01726 for ; Thu, 17 Oct 1996 17:27:32 -0400 (EDT) Message-ID: <3266A4D7.2781E494@mindspring.com> Date: Thu, 17 Oct 1996 17:27:51 -0400 From: Ron Bolin X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: Latest Current Building Boot and Fixit Floppies. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In building the floppies from the latest current I get the following errorout of /usr/src/release/floppies (cd /usr/src/sbin/mount_nfs && make depend && make mount_nfs.o getmntopts.o) `mount_nfs.o' is up to date. `getmntopts.o' is up to date. cc -O -DCRUNCHED_BINARY -c crunch.c cc -static -o crunch crunch.o sh.lo find.lo pwd.lo ft.lo ppp.lo sysinstall.lo ne wfs.lo gzip.lo cpio.lo bad144.lo fsck.lo ifconfig.lo route.lo slattach.lo mount_ nfs.lo -ll -ledit -lutil -lkvm -lmd -ldialog -lncurses -lmytinfo -L/usr/src/rele ase/libdisk/obj -ldisk -lipx ppp.lo: Undefined symbol `_crypt' referenced from text segment *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 All other source built just fine, I even built and installed eBones and secure. It seems that the call to _crypt used in some part of the floppy build uses _crypt, bu I have only _des_crypt defined in any libs. The libcrypt.a is linked to libdescrypt.a. Any comments? -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 Thu Oct 17 14:50:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA02557 for current-outgoing; Thu, 17 Oct 1996 14:50:55 -0700 (PDT) Received: from aravis.oliverdesign.com (oliverdesign.com.oliverdesign.com [205.179.167.60]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA02550 for ; Thu, 17 Oct 1996 14:50:51 -0700 (PDT) Received: from tom.oliverdesign.com (tom.oliverdesign.com [205.179.167.58]) by aravis.oliverdesign.com (8.7.5/8.7.3) with SMTP id OAA08032 for ; Thu, 17 Oct 1996 14:50:39 GMT Message-Id: <3.0b33.32.19961017145012.00691f58@oliverdesign.com> X-Sender: tom@oliverdesign.com X-Mailer: Windows Eudora Pro Version 3.0b33 (32) Date: Thu, 17 Oct 1996 14:50:12 -0700 To: current@FreeBSD.org From: "Thomas B. Fox" Subject: help compiling current 'make world' Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, My first attempt at doing a make world failed. Following is the resulting error messages. I would appreciate someone's assistance. ===> gnu/usr.bin/groff/devX100 "Makefile", line 6: Could not find /usr/src/gnu/usr.bin/groff/devX100/../../../. ./contrib/groff/devX100/Makefile.sub Fatal errors encountered -- cannot continue *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Thomas B. Fox - tom@oliverdesign.com - Webmaster and MIS - Oliver Design, Inc. - 5 Victor Sq. - Scotts Valley, CA 95066 From owner-freebsd-current Thu Oct 17 16:05:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA07425 for current-outgoing; Thu, 17 Oct 1996 16:05:19 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA07409 for ; Thu, 17 Oct 1996 16:05:02 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id BAA04817 for ; Fri, 18 Oct 1996 01:04:17 +0200 (MET DST) To: current@freebsd.org Subject: vasprintf in the kernel ? Reply-to: phk@freebsd.org Date: Fri, 18 Oct 1996 01:04:17 +0200 Message-ID: <4815.845593457@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It seems to me that several pieces of code, devfs included would actually benefit from this, comments ? -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Thu Oct 17 16:46:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA10118 for current-outgoing; Thu, 17 Oct 1996 16:46:47 -0700 (PDT) Received: from sunrise.cs.berkeley.edu (root@sunrise.CS.Berkeley.EDU [128.32.38.121]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA10079 for ; Thu, 17 Oct 1996 16:46:40 -0700 (PDT) Received: (from asami@localhost) by sunrise.cs.berkeley.edu (8.7.5/8.6.12) id QAA13043; Thu, 17 Oct 1996 16:40:04 -0700 (PDT) Date: Thu, 17 Oct 1996 16:40:04 -0700 (PDT) Message-Id: <199610172340.QAA13043@sunrise.cs.berkeley.edu> To: michaelv@MindBender.serv.net CC: scrappy@ki.net, michaelh@cet.co.jp, mrcpu@cdsnet.net, current@freebsd.org In-reply-to: <199610172054.NAA12845@MindBender.serv.net> (michaelv@MindBender.serv.net) Subject: Re: Iozone: local vs nfs drives From: asami@freebsd.org (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * Did you have tagged-command queuing enabled? According to my tests, * that will make a BIG difference, if you have decent drives. I haven't seen tagged-queueing make much difference for reads. These are the kind of numbers we've seen before (off the top of my head): w/o tag with tag W R W R Quantum Atlas 6 7 6 7 Seagate 'Cuda 4 6 6 7 Fast-Wide disks on Adaptec 2940UW. Satoshi From owner-freebsd-current Thu Oct 17 16:48:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA10230 for current-outgoing; Thu, 17 Oct 1996 16:48:27 -0700 (PDT) Received: from llama.bazzle.com ([206.103.246.161]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA10214 for ; Thu, 17 Oct 1996 16:48:12 -0700 (PDT) Received: (from dob@localhost) by llama.bazzle.com (8.7.6/8.6.12) id TAA00312 for freebsd-current@freebsd.org; Thu, 17 Oct 1996 19:46:47 -0400 (EDT) Date: Thu, 17 Oct 1996 19:46:47 -0400 (EDT) From: "Dan O'Brien" Message-Id: <199610172346.TAA00312@llama.bazzle.com> To: freebsd-current@freebsd.org Subject: CVSUP warning on -current Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I supped tonight (during dinner no less) and got the following CVSUP warning. Is this important? Server warning: Cannot open "/home/ncvs/ports/security/ssh/patches/patch-ad,v": Permission denied Thanks, Dan O'Brien Columbus, OH From owner-freebsd-current Thu Oct 17 18:44:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA15914 for current-outgoing; Thu, 17 Oct 1996 18:44:23 -0700 (PDT) Received: from clam.niwa.cri.nz (clam.niwa.cri.nz [131.203.56.8]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA15909 for ; Thu, 17 Oct 1996 18:44:19 -0700 (PDT) Received: from frc.niwa.cri.nz (frc.niwa.cri.nz [131.203.59.1]) by clam.niwa.cri.nz (8.8.0/8.8.0) with ESMTP id OAA02667; Fri, 18 Oct 1996 14:46:23 +1300 (NZDT) Received: from alf.niwa.cri.nz (alf.niwa.cri.nz [131.203.58.14]) by frc.niwa.cri.nz (8.8.0/8.8.0) with SMTP id BAA19638; Fri, 18 Oct 1996 01:47:17 GMT Date: Fri, 18 Oct 1996 14:45:08 +1300 (NZDT) From: Wayne Knowles X-Sender: wdk@alf.niwa.cri.nz To: "Marc G. Fournier" cc: current@freebsd.org Subject: Re: make re-makes for no apparent reason... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 17 Oct 1996, Marc G. Fournier wrote: > > Hi... > > I know that generally you are supposed to do: > > make cleandir;make depend;make > > when rebuilding the source tree, and generally I do, but > tonight I wanted to make sure that I had completed my compile > of /usr/src/lib (ie. my recent crashes hadn't happened part way > through). > > So, I just did a 'cd /usr/src/lib;make', but its recompiling > everything from scratch again, as if the existing .o files don't already > exist, but, as an ls shows, the libraries have already been built: Something like this happens to me when I use tcsh and have a symbolic link as /usr/src. If your shell sets PWD (like tcsh) then you may have to 'unsetenv PWD' to stop make following the wrong path into /usr/obj I haven't spent much time with this problem, I just worked out what I had to do to work around the problem. If anybody has a more permanent suggestion to avoiding the problem, I would be very grateful. Wayne -- _____ Wayne Knowles Title : Systems Programmer / o \/ NIWA Fisheries Research Usenet: w.knowles@niwa.cri.nz \/ v /\ PO. Box 14-901, Kilbirnie `---' Wellington, NEW ZEALAND From owner-freebsd-current Thu Oct 17 18:58:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA16443 for current-outgoing; Thu, 17 Oct 1996 18:58:35 -0700 (PDT) Received: from gargoyle.bazzle.com ([206.103.246.190]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA16438 for ; Thu, 17 Oct 1996 18:58:29 -0700 (PDT) Received: from gargoyle.bazzle.com (localhost [127.0.0.1]) by gargoyle.bazzle.com (8.7.6/8.6.12) with SMTP id VAA24263; Thu, 17 Oct 1996 21:58:06 -0400 (EDT) Date: Thu, 17 Oct 1996 21:58:06 -0400 (EDT) From: "Eric J. Chet" To: "Dan O'Brien" cc: freebsd-current@freebsd.org Subject: Re: CVSUP warning on -current In-Reply-To: <199610172346.TAA00312@llama.bazzle.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, 17 Oct 1996, Dan O'Brien wrote: > I supped tonight (during dinner no less) and got the following CVSUP > warning. Is this important? > > Server warning: Cannot open "/home/ncvs/ports/security/ssh/patches/patch-ad,v": Permission denied > > > Thanks, > > Dan O'Brien > Columbus, OH > Hello I supped tonight at sup.961017.1750 and did not get that message. I used cvsup.freebsd.org Peace Eric J. Chet - ejc@bazzle.com From owner-freebsd-current Thu Oct 17 19:20:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA17485 for current-outgoing; Thu, 17 Oct 1996 19:20:42 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA17474; Thu, 17 Oct 1996 19:20:30 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id TAA25454; Thu, 17 Oct 1996 19:20:14 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id TAA14144; Thu, 17 Oct 1996 19:19:57 -0700 (PDT) Message-Id: <199610180219.TAA14144@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: asami@freebsd.org (Satoshi Asami) cc: scrappy@ki.net, michaelh@cet.co.jp, mrcpu@cdsnet.net, current@freebsd.org Subject: Re: Iozone: local vs nfs drives In-reply-to: Your message of Thu, 17 Oct 96 16:40:04 -0700. <199610172340.QAA13043@sunrise.cs.berkeley.edu> Date: Thu, 17 Oct 1996 19:19:46 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > * Did you have tagged-command queuing enabled? According to my tests, > * that will make a BIG difference, if you have decent drives. >I haven't seen tagged-queueing make much difference for reads. These >are the kind of numbers we've seen before (off the top of my head): > w/o tag with tag > W R W R >Quantum Atlas 6 7 6 7 >Seagate 'Cuda 4 6 6 7 OK, you're right. And, my tests were with a Barracuda (2GB, about 45% full), as well. Still, it DID make a big difference for writes. Also, this was under NetBSD, but the results should be very similar: W R BT956c (no TCQ) 1.5 6.1 2940UW (no TCQ) 1.5 5.0 2940UW (TCQ) 4.5 6.4 (On a Pentium 120MHz, 64MB EDO RAM, NetBSD 1.2, narrow 2GB Seagate Barracuda.) ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-current Thu Oct 17 19:25:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA17765 for current-outgoing; Thu, 17 Oct 1996 19:25:36 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA17757; Thu, 17 Oct 1996 19:25:33 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id CAA29727; Fri, 18 Oct 1996 02:25:31 GMT Date: Fri, 18 Oct 1996 11:25:31 +0900 (JST) From: Michael Hancock To: Satoshi Asami cc: current@freebsd.org Subject: Re: Iozone: local vs nfs drives In-Reply-To: <199610172340.QAA13043@sunrise.cs.berkeley.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 17 Oct 1996, Satoshi Asami wrote: > * Did you have tagged-command queuing enabled? According to my tests, > * that will make a BIG difference, if you have decent drives. > > I haven't seen tagged-queueing make much difference for reads. These > are the kind of numbers we've seen before (off the top of my head): > > w/o tag with tag > W R W R > Quantum Atlas 6 7 6 7 > Seagate 'Cuda 4 6 6 7 I guess we haven't addressed the original question though. It's strange, even if you consider the cache wiping effects. Our rotational delay defaults to zero doesn't it? Regards, Mike Hancock From owner-freebsd-current Thu Oct 17 19:27:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA17862 for current-outgoing; Thu, 17 Oct 1996 19:27:42 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA17857 for ; Thu, 17 Oct 1996 19:27:27 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id TAA25629; Thu, 17 Oct 1996 19:27:24 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id TAA14184; Thu, 17 Oct 1996 19:27:09 -0700 (PDT) Message-Id: <199610180227.TAA14184@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Marc G. Fournier" cc: Michael Hancock , Jaye Mathisen , current@freebsd.org Subject: Re: Iozone: local vs nfs drives In-reply-to: Your message of Thu, 17 Oct 96 17:00:06 -0400. Date: Thu, 17 Oct 1996 19:27:09 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Did you have tagged-command queuing enabled? According to my tests, >> that will make a BIG difference, if you have decent drives. > I don't know...I haven't enabled it manually, so I would assume >not. > How do I check/enable it? Any caveats I should worry about? Put "options AHC_TAGENABLE" in your kernel config file, and rebuild (this is on NetBSD, anyway, but it's the common code written by Justin Gibbs). Caveats? My NetBSD box has been running a ccd for about two months striped across two drives, with this enabled (and the drives do support tagged command queuing, yes). This is on NetBSD-current (1.2), using the "common" AHC driver. No bad things have happened, yet. :-) ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-current Thu Oct 17 21:22:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA22667 for current-outgoing; Thu, 17 Oct 1996 21:22:24 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA22662; Thu, 17 Oct 1996 21:22:17 -0700 (PDT) Received: from localhost (scrappy@localhost) by quagmire.ki.net (8.7.5/8.7.5) with SMTP id AAA08522; Fri, 18 Oct 1996 00:22:12 -0400 (EDT) Date: Fri, 18 Oct 1996 00:22:11 -0400 (EDT) From: "Marc G. Fournier" To: Michael Hancock cc: Satoshi Asami , current@FreeBSD.org Subject: Re: Iozone: local vs nfs drives 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 Fri, 18 Oct 1996, Michael Hancock wrote: > On Thu, 17 Oct 1996, Satoshi Asami wrote: > > > * Did you have tagged-command queuing enabled? According to my tests, > > * that will make a BIG difference, if you have decent drives. > > > > I haven't seen tagged-queueing make much difference for reads. These > > are the kind of numbers we've seen before (off the top of my head): > > > > w/o tag with tag > > W R W R > > Quantum Atlas 6 7 6 7 > > Seagate 'Cuda 4 6 6 7 > > I guess we haven't addressed the original question though. No, it doesn't, but I think it might bring up another point... is there a way of having tagged-command queueing enabled by default? If there is the potential to see such a boost in performance as has been reported, at least in the 'write' department...is there a disadvantage to it that hasn't been brought up? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Thu Oct 17 21:26:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA22981 for current-outgoing; Thu, 17 Oct 1996 21:26:17 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA22973 for ; Thu, 17 Oct 1996 21:26:14 -0700 (PDT) Received: from localhost (scrappy@localhost) by quagmire.ki.net (8.7.5/8.7.5) with SMTP id AAA08563; Fri, 18 Oct 1996 00:24:40 -0400 (EDT) Date: Fri, 18 Oct 1996 00:24:39 -0400 (EDT) From: "Marc G. Fournier" To: "Michael L. VanLoon -- HeadCandy.com" cc: Michael Hancock , Jaye Mathisen , current@freebsd.org Subject: Re: Iozone: local vs nfs drives In-Reply-To: <199610180227.TAA14184@MindBender.serv.net> 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, 17 Oct 1996, Michael L. VanLoon -- HeadCandy.com wrote: > > >> Did you have tagged-command queuing enabled? According to my tests, > >> that will make a BIG difference, if you have decent drives. > > > I don't know...I haven't enabled it manually, so I would assume > >not. > > How do I check/enable it? Any caveats I should worry about? > > Put "options AHC_TAGENABLE" in your kernel config file, and rebuild > (this is on NetBSD, anyway, but it's the common code written by Justin > Gibbs). > > Caveats? My NetBSD box has been running a ccd for about two months > striped across two drives, with this enabled (and the drives do > support tagged command queuing, yes). This is on NetBSD-current > (1.2), using the "common" AHC driver. No bad things have happened, > yet. :-) > Okay...to me, AHC_ brings to mind the Adaptec code...I'm using one of the ASUS SC-100 PCI controllers for my drives, so just want to confirm that this will work similar here? And, you mention "the drive supporting tagged command queueing"... how does one determine that? What if some of my drives do, and some don't... will it get disabled altogether as a result, or...? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Thu Oct 17 21:32:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA23309 for current-outgoing; Thu, 17 Oct 1996 21:32:00 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA23301 for ; Thu, 17 Oct 1996 21:31:55 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id FAA29604 for ; Fri, 18 Oct 1996 05:31:50 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id GAA13443 for current@freebsd.org; Fri, 18 Oct 1996 06:30:59 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.0/keltia-uucp-2.9) id AAA22646; Fri, 18 Oct 1996 00:23:23 +0200 (MET DST) Message-Id: <199610172223.AAA22646@keltia.freenix.fr> Date: Fri, 18 Oct 1996 00:23:22 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: current@freebsd.org Subject: Re: Iozone: local vs nfs drives In-Reply-To: ; from Marc G. Fournier on Oct 17, 1996 17:00:06 -0400 References: <199610172054.NAA12845@MindBender.serv.net> X-Mailer: Mutt 0.47.13 Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-CURRENT ctm#2584 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Michael L. VanLoon: > > Did you have tagged-command queuing enabled? According to my tests, > > that will make a BIG difference, if you have decent drives. I know the current Buslogic doesn't support them but I'd like to know if it would be difficult to add... I have a decent drive (IBM DORS 32160) which should support them but I have a BT-747S and an Adaptec 1740A... Probing for devices on the EISA bus bt0: at 0x330-0x333, 0x3c00-0x3cff irq 11 bt0: on eisa0 slot 3 bt0: Bt747 / 0-(32bit) bus bt0: reading board settings, busmastering, int=11 bt0: version 3.37, fast sync, parity, 32 mbxs, 32 ccbs bt0: targ 0 sync rate=10.00MB/s(100ns), offset=15 bt0: targ 4 async bt0: targ 5 sync rate= 5.00MB/s(200ns), offset=08 bt0: Using Strict Round robin scheme (bt0:0:0): "IBM DORS-32160 WA6A" type 0 fixed SCSI 2 sd0(bt0:0:0): Direct-Access 2063MB (4226725 512 byte sectors) ... ahb0: at 0x5c00-0x5cff irq 12 on eisa0 slot 5 (ahb0:1:0): "MICROP 1624-07MZ1077801 HZ2P" type 0 fixed SCSI 2 sd11(ahb0:1:0): Direct-Access 642MB (1316751 512 byte sectors) (ahb0:2:0): "SEAGATE ST31200N 8158" type 0 fixed SCSI 2 sd12(ahb0:2:0): Direct-Access 1006MB (2061108 512 byte sectors) -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #25: Tue Oct 15 21:13:57 MET DST 1996 From owner-freebsd-current Thu Oct 17 21:41:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA23855 for current-outgoing; Thu, 17 Oct 1996 21:41:52 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA23850; Thu, 17 Oct 1996 21:41:50 -0700 (PDT) Message-Id: <199610180441.VAA23850@freefall.freebsd.org> To: "Marc G. Fournier" cc: Michael Hancock , Satoshi Asami , current@FreeBSD.org Subject: Re: Iozone: local vs nfs drives In-reply-to: Your message of "Fri, 18 Oct 1996 00:22:11 EDT." Date: Thu, 17 Oct 1996 21:41:50 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > No, it doesn't, but I think it might bring up another point... >is there a way of having tagged-command queueing enabled by default? If >there is the potential to see such a boost in performance as has been >reported, at least in the 'write' department...is there a disadvantage >to it that hasn't been brought up? It will be enabled by default as soon as we have a system in place to allow quirk entries for devices that botch tags. In the SCSI code on the 'SCSI' branch, tagged queueing is handled by the generic SCSI layer which allows for the addition of just such a quirk trivially. In short, this will happen... most likely in current before another month has passed. > >Marc G. Fournier scrappy@ki.net >Systems Administrator @ ki.net scrappy@freebsd.org > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Thu Oct 17 21:54:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA24382 for current-outgoing; Thu, 17 Oct 1996 21:54:44 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA24376 for ; Thu, 17 Oct 1996 21:54:42 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id VAA06692; Thu, 17 Oct 1996 21:54:32 -0700 (PDT) Message-Id: <199610180454.VAA06692@austin.polstra.com> To: dob@gargoyle.bazzle.com Cc: freebsd-current@freebsd.org Subject: Re: CVSUP warning on -current In-reply-to: <199610172346.TAA00312@llama.bazzle.com> References: <199610172346.TAA00312@llama.bazzle.com> Date: Thu, 17 Oct 1996 21:54:32 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I supped tonight (during dinner no less) and got the following CVSUP > warning. Is this important? > > Server warning: Cannot open "/home/ncvs/ports/security/ssh/patches/patch-ad,v": > Permission denied Somebody put that file into the repository with incorrect permissions, so the CVSup server couldn't read it. It's been fixed since you tried it. It's not a big deal. You'll get the file the next time you run CVSup. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Thu Oct 17 21:57:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA24574 for current-outgoing; Thu, 17 Oct 1996 21:57:45 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA24569 for ; Thu, 17 Oct 1996 21:57:43 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id VAA28833; Thu, 17 Oct 1996 21:57:49 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id VAA14497; Thu, 17 Oct 1996 21:57:32 -0700 (PDT) Message-Id: <199610180457.VAA14497@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Marc G. Fournier" cc: Michael Hancock , Jaye Mathisen , current@freebsd.org Subject: Re: Iozone: local vs nfs drives In-reply-to: Your message of Fri, 18 Oct 96 00:24:39 -0400. Date: Thu, 17 Oct 1996 21:57:31 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >> Did you have tagged-command queuing enabled? According to my tests, >> >> that will make a BIG difference, if you have decent drives. >> > I don't know...I haven't enabled it manually, so I would assume >> >not. >> > How do I check/enable it? Any caveats I should worry about? >> Put "options AHC_TAGENABLE" in your kernel config file, and rebuild >> (this is on NetBSD, anyway, but it's the common code written by Justin >> Gibbs). > Okay...to me, AHC_ brings to mind the Adaptec code...I'm using >one of the ASUS SC-100 PCI controllers for my drives, so just want to >confirm that this will work similar here? Ah yes. It must have been someone else that posted that he was using an Adaptec 2940. I mis-threaded... I know the NCR supports tagged-command-queuing, also, but since I don't use one (except on some NT machines at work), I don't know what you do to enable it. Joe Greco would know. > And, you mention "the drive supporting tagged command queueing"... >how does one determine that? What if some of my drives do, and some don't... >will it get disabled altogether as a result, or...? Some older SCSI drives don't support it. And some that claim they do, don't support it "correctly". I have a Quantum TrailBlazer 850MB and a Quantum LPS 540 that don't support it. My HP 1GB drives do. My Seagate Barracudas and Hawks do, also, but I run NT on those. The Adaptec driver tells you if you have a "tagged queuing device" on each SCSI device: ahc0: target 0 synchronous at 10.0MHz, offset = 0xf ahc0: target 0 Tagged Queuing Device sd0 at scsibus0 targ 0 lun 0: SCSI2 0/direct fixed sd0: 1003MB, 2982 cyl, 7 head, 98 sec, 512 bytes/sec ahc0: target 1 synchronous at 10.0MHz, offset = 0xf ahc0: target 1 Tagged Queuing Device sd1 at scsibus0 targ 1 lun 0: SCSI2 0/direct fixed sd1: 1003MB, 2982 cyl, 7 head, 98 sec, 512 bytes/sec ahc0: target 2 synchronous at 10.0MHz, offset = 0x8 sd2 at scsibus0 targ 2 lun 0: SCSI2 0/direct fixed sd2: 516MB, 2740 cyl, 4 head, 96 sec, 512 bytes/sec ahc0: target 5 synchronous at 4.0MHz, offset = 0xf cd0 at scsibus0 targ 5 lun 0: SCSI2 5/cdrom removable Once again, the NCR driver does this, as well, but you'll have to get the specifics from somewhere else. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-current Thu Oct 17 22:16:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA25339 for current-outgoing; Thu, 17 Oct 1996 22:16:57 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA25333; Thu, 17 Oct 1996 22:16:54 -0700 (PDT) Message-Id: <199610180516.WAA25333@freefall.freebsd.org> To: "Michael L. VanLoon -- HeadCandy.com" cc: "Marc G. Fournier" , Michael Hancock , Jaye Mathisen , current@freebsd.org Subject: Re: Iozone: local vs nfs drives In-reply-to: Your message of "Thu, 17 Oct 1996 21:57:31 PDT." <199610180457.VAA14497@MindBender.serv.net> Date: Thu, 17 Oct 1996 22:16:54 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >The Adaptec driver tells you if you have a "tagged queuing device" on >each SCSI device: This isn't quite true anymore - at least not if you are using the code from the 'SCSI' branch: ahc0: at 0x1c00-0x1cff irq 10 on eisa0 slot 1 ahc0: aic7770 <= Rev C, Twin Channel, A SCSI Id=7, B SCSI Id=7, 4 SCBs (ahc0:6:0): "ARCHIVE Python 28388-XXX 5.40" type 1 removable SCSI 2 st0(ahc0:6:0): Sequential-Access density code 0x13, drive empty (ahc0:0:0): "QUANTUM PD1225S 3110" type 0 fixed SCSI 2 (ahc0:0:0): Tagged Queueing Device (Queueing Enabled) sd0(ahc0:0:0): Direct-Access 1169MB (2395980 512 byte sectors) (ahc0:1:0): "QUANTUM PD1800S 3162" type 0 fixed SCSI 2 (ahc0:1:0): Tagged Queueing Device (Queueing Enabled) Those messages come from the generic SCSI layer and would say "Disabled" if my card/driver didn't supports this feature. >----------------------------------------------------------------------------- > Michael L. VanLoon michaelv@MindBender.serv.net > --< Free your mind and your machine -- NetBSD free un*x >-- > NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, > Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... > NetBSD ports in progress: PICA, others... >----------------------------------------------------------------------------- -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Fri Oct 18 03:31:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA12361 for current-outgoing; Fri, 18 Oct 1996 03:31:24 -0700 (PDT) Received: from lassie.eunet.fi (lassie.eunet.fi [192.26.119.7]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA12351 for ; Fri, 18 Oct 1996 03:31:19 -0700 (PDT) Received: from marathon.tekla.fi by lassie.eunet.fi with SMTP id AA19751 (5.67a/IDA-1.5 for ); Fri, 18 Oct 1996 13:31:14 +0300 Received: from poveri.tekla.fi by marathon.tekla.fi (5.65/20-jun-90) id AA23346; Fri, 18 Oct 1996 12:31:12 +0200 From: sja@tekla.fi (Sakari Jalovaara) Received: by poveri.tekla.fi; (5.65v3.2/1.1.8.2/20Aug96-0557PM) id AA07335; Fri, 18 Oct 1996 13:31:12 +0300 Date: Fri, 18 Oct 1996 13:31:12 +0300 Message-Id: <9610181031.AA07335@poveri.tekla.fi> To: current@freebsd.org Subject: Re: Weirdness in current Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >Stack corruption bugs are a *bugger* to find. > > Port your software to SunOS/Slolaris and run Purify on it. :) Hey, don't laugh! I've ported plenty of stuff to HP just to run under Purify. Going through all FreeBSD userland stuff with Purify would be a useful project (and a BIG one). One would need to port libraries and executables to SunOS, HP-UX and/or NT. (Purify for Losedows NT just came out; see www.pureatria.com.) >> I once made a gross hack on a Pyramid, such that checksum of the stack >> was made at every function call and record written to file at the >> return recording match/nomatch. > > This is basically what Purify does.. The mechanism is different (at least from the manual I've read); the stack checksum trick would find different kinds of errors from what Purify catches. Purify uses a memory coloring sceme and object code modification to figure out what bytes in memory shouldn't be accessed. ++sja From owner-freebsd-current Fri Oct 18 07:29:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA26118 for current-outgoing; Fri, 18 Oct 1996 07:29:35 -0700 (PDT) Received: from dfw-ix5.ix.netcom.com (dfw-ix5.ix.netcom.com [206.214.98.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA26100 for ; Fri, 18 Oct 1996 07:29:31 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca11-27.ix.netcom.com [199.35.209.187]) by dfw-ix5.ix.netcom.com (8.6.13/8.6.12) with ESMTP id HAA17736; Fri, 18 Oct 1996 07:28:58 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.6/8.6.9) id HAA18892; Fri, 18 Oct 1996 07:28:55 -0700 (PDT) Date: Fri, 18 Oct 1996 07:28:55 -0700 (PDT) Message-Id: <199610181428.HAA18892@silvia.HIP.Berkeley.EDU> To: michaelh@cet.co.jp CC: current@freebsd.org In-reply-to: (message from Michael Hancock on Fri, 18 Oct 1996 11:25:31 +0900 (JST)) Subject: Re: Iozone: local vs nfs drives From: asami@freebsd.org (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * > I haven't seen tagged-queueing make much difference for reads. These * > are the kind of numbers we've seen before (off the top of my head): * > * > w/o tag with tag * > W R W R * > Quantum Atlas 6 7 6 7 * > Seagate 'Cuda 4 6 6 7 * * I guess we haven't addressed the original question though. It's strange, You're right, I've never seen any drive that can write faster than reading. At least in my limited experience with, um, 5 drives and two controllers. Satoshi P.S. Here's another one, this is IDE (P5-133, ST32140A): ## iozone 100 65536 : 3236501 bytes/second for writing the file 3689327 bytes/second for reading the file From owner-freebsd-current Fri Oct 18 07:32:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA26442 for current-outgoing; Fri, 18 Oct 1996 07:32:35 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA26436 for ; Fri, 18 Oct 1996 07:32:31 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id JAA02841; Fri, 18 Oct 1996 09:28:28 -0500 From: Joe Greco Message-Id: <199610181428.JAA02841@brasil.moneng.mei.com> Subject: Re: Iozone: local vs nfs drives To: michaelv@MindBender.serv.net (Michael L. VanLoon -- HeadCandy.com) Date: Fri, 18 Oct 1996 09:28:28 -0500 (CDT) Cc: scrappy@ki.net, michaelh@cet.co.jp, mrcpu@cdsnet.net, current@freebsd.org In-Reply-To: <199610180457.VAA14497@MindBender.serv.net> from "Michael L. VanLoon -- HeadCandy.com" at Oct 17, 96 09:57:31 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Ah yes. It must have been someone else that posted that he was using > an Adaptec 2940. I mis-threaded... > > I know the NCR supports tagged-command-queuing, also, but since I > don't use one (except on some NT machines at work), I don't know what > you do to enable it. Joe Greco would know. I take exception to that :-) Alls I know is that they are enabled by default. Run "ncrcontrol": # ncrcontrol T:L Vendor Device Rev Speed Max Wide Tags 0:0 SEAGATE ST31055N 0318 10.0 10.0 8 4 1:0 SEAGATE ST31055N 0318 10.0 10.0 8 4 2:0 SEAGATE ST31055N 0318 10.0 10.0 8 4 3:0 SEAGATE ST31055N 0318 10.0 10.0 8 4 4:0 SEAGATE ST31055N 0318 10.0 10.0 8 4 I just a day or two ago sent a note to Stefan asking about the maximum number of tags allowable... it looks to me as though IF you are using the Adaptec stuff that it defaults to 8 tags. I really don't know anything much about the real technical details of this stuff though.. I rely on the SCSI gods for this info. ... JG From owner-freebsd-current Fri Oct 18 08:39:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA01437 for current-outgoing; Fri, 18 Oct 1996 08:39:54 -0700 (PDT) Received: from phoenix.csie.nctu.edu.tw (root@phoenix.csie.nctu.edu.tw [140.113.17.171]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA01429 for ; Fri, 18 Oct 1996 08:39:50 -0700 (PDT) Received: from FreeBSD.csie.NCTU.edu.tw (freebsd.csie.nctu.edu.tw [140.113.235.250]) by phoenix.csie.nctu.edu.tw (8.7.5/8.7.5) with ESMTP id XAA08563 for ; Fri, 18 Oct 1996 23:37:22 +0800 (CST) Received: (from jdli@localhost) by FreeBSD.csie.NCTU.edu.tw (8.7.6/8.7.3) id XAA09906 for freebsd-current@FreeBSD.ORG; Fri, 18 Oct 1996 23:38:44 +0800 (CST) From: Jian-Da Li Message-Id: <199610181538.XAA09906@FreeBSD.csie.NCTU.edu.tw> Subject: Continuously crash using 2.2-961014-SNAP To: freebsd-current@FreeBSD.ORG Date: Fri, 18 Oct 1996 23:38:44 +0800 (CST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi : Our server is running 2.2-961014-SNAP plus the NFS patch. Without this NFS patch, it will panic hourly, and now with it, it will still crash once a day. And it will always panic at "identd", which we had re-compile it on 2.2-961014-SNAP. This is a loaded NFS/BBS/News/FTP server. Fatal trap 12: page fault while in kernel mode fault virtual address = 0xefffffc0 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01af09c stack pointer = 0x10:0xefbffe34 frame pointer = 0x10:0xefbffe3c 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 = 11612 (identd) interrupt mask = panic: page fault -- 李 建 達 (Jian-Da Li) 交 大 資 工 E-Mail : http://www.csie.nctu.edu.tw/~jdli From owner-freebsd-current Fri Oct 18 09:32:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA05542 for current-outgoing; Fri, 18 Oct 1996 09:32:20 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA05537; Fri, 18 Oct 1996 09:32:16 -0700 (PDT) Message-Id: <199610181632.JAA05537@freefall.freebsd.org> To: Joe Greco cc: michaelv@MindBender.serv.net (Michael L. VanLoon -- HeadCandy.com), scrappy@ki.net, michaelh@cet.co.jp, mrcpu@cdsnet.net, current@freebsd.org Subject: Re: Iozone: local vs nfs drives In-reply-to: Your message of "Fri, 18 Oct 1996 09:28:28 CDT." <199610181428.JAA02841@brasil.moneng.mei.com> Date: Fri, 18 Oct 1996 09:32:16 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I just a day or two ago sent a note to Stefan asking about the maximum >number of tags allowable... it looks to me as though IF you are using >the Adaptec stuff that it defaults to 8 tags. I really don't know >anything much about the real technical details of this stuff though.. >I rely on the SCSI gods for this info. > >... JG Tag identifiers are in the range of 0-255. The allows each target/lun to have at most 256 tagged transactions open at a time (I'm talking SCSI-II here - SCSI III expands this a bit for upcoming bus types). So, the max number of tags depends really on a few things: 1) How many tags can your drive support? - Early Quantum drives supports up to 16 - Most modern drives support either 32 or 64 2) How many transactions your controller can support on a per target/lun basis. - For the aic7xxx cards, controller resources are shared across all target/luns, so this is your SCB count, or once I get paging to work well, 255. - For the NCR, resources are allocated separately for each target/lun and is limited by NCR_MAX_TAGS and probably the hard SCSI-II limit of 256 tags. The current 2940 driver 'guesses' at how man tags to give to each device because it does not have a good way of modulating them and communicating those changes to the generic SCSI layer. This has changed with the code on the 'SCSI' branch. On the 'SCSI' branch, the aic7xxx driver tells the generic SCSI layer that it has X openings on the controller and that each target has either a max of 2 openings if non-tag capable or X openings if tag capable with X being the number of SCBs on the controller or 255 if you are paging. The generic SCSI layer then performs round-robin among all targets to ensure resource fairness. It also looks for the QUEUE FULL or BUSY condition in order to reduce that max number of device openings if it exceeds the capacity of the device. (some early drives like the Quantum LPS series return BUSY instead of QUEUE FULL, so you have to watch for this condition recurring with the same number of transactions pending every time). -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Fri Oct 18 09:41:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA06312 for current-outgoing; Fri, 18 Oct 1996 09:41:22 -0700 (PDT) Received: from dyson.iquest.net ([198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA06304 for ; Fri, 18 Oct 1996 09:41:17 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id LAA01322; Fri, 18 Oct 1996 11:40:59 -0500 (EST) From: John Dyson Message-Id: <199610181640.LAA01322@dyson.iquest.net> Subject: Re: Continuously crash using 2.2-961014-SNAP To: jdli@FreeBSD.csie.NCTU.edu.tw (Jian-Da Li) Date: Fri, 18 Oct 1996 11:40:59 -0500 (EST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199610181538.XAA09906@FreeBSD.csie.NCTU.edu.tw> from "Jian-Da Li" at Oct 18, 96 11:38:44 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 Send me a copy of the output of nm for your kernel. John From owner-freebsd-current Fri Oct 18 12:07:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA16808 for current-outgoing; Fri, 18 Oct 1996 12:07:38 -0700 (PDT) Received: from gargoyle.bazzle.com ([206.103.246.190]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA16803 for ; Fri, 18 Oct 1996 12:07:31 -0700 (PDT) Received: from gargoyle.bazzle.com (localhost [127.0.0.1]) by gargoyle.bazzle.com (8.7.6/8.6.12) with SMTP id PAA04419; Fri, 18 Oct 1996 15:05:27 -0400 (EDT) Date: Fri, 18 Oct 1996 15:05:27 -0400 (EDT) From: "Eric J. Chet" To: "Michael L. VanLoon -- HeadCandy.com" cc: "Marc G. Fournier" , Michael Hancock , Jaye Mathisen , current@freebsd.org Subject: Re: Iozone: local vs nfs drives In-Reply-To: <199610180457.VAA14497@MindBender.serv.net> 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, 17 Oct 1996, Michael L. VanLoon -- HeadCandy.com wrote: > > I know the NCR supports tagged-command-queuing, also, but since I > don't use one (except on some NT machines at work), I don't know what > you do to enable it. Joe Greco would know. I don't think you have to do anything to enable it. ejc@gargoyle: sudo ncrcontrol -v -i -u 0 -t 0 Password: T:L Vendor Device Rev Speed Max Wide Tags 0:0 SEAGATE ST15150W 0020 10.0 10.0 16 4 [00]: disk [00]: fixed media [02]: SCSI-2 [02]: [8f]: [00]: [01]: [3e]: capabilities: wide synch link tags Peace, Eric J. Chet - ejc@bazzle.com From owner-freebsd-current Fri Oct 18 15:52:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA28511 for current-outgoing; Fri, 18 Oct 1996 15:52:35 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA28453 for ; Fri, 18 Oct 1996 15:52:15 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA08543; Sat, 19 Oct 1996 00:52:07 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA01330; Sat, 19 Oct 1996 00:52:07 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.6/8.6.9) id XAA29022; Fri, 18 Oct 1996 23:25:21 +0200 (MET DST) From: J Wunsch Message-Id: <199610182125.XAA29022@uriah.heep.sax.de> Subject: Re: Latest Current Building Boot and Fixit Floppies. To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Fri, 18 Oct 1996 23:25:21 +0200 (MET DST) Cc: rlb@mindspring.com (Ron Bolin) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <3266A4D7.2781E494@mindspring.com> from Ron Bolin at "Oct 17, 96 05:27: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 Ron Bolin wrote: > In building the floppies from the latest current I get the > following errorout of /usr/src/release/floppies > ppp.lo: Undefined symbol `_crypt' referenced from text segment > *** Error code 1 The _latest_ -current? Nope. :-) j@uriah 390% cvs log /usr/src/release/boot_crunch.conf RCS file: /home/cvs/src/release/boot_crunch.conf,v Working file: /usr/src/release/boot_crunch.conf head: 1.24 ... revision 1.24 date: 1996/10/07 04:16:36; author: jkh; state: Exp; lines: +2 -2 Add -lcrypt for new ppp changes. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Fri Oct 18 19:00:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA10120 for current-outgoing; Fri, 18 Oct 1996 19:00:18 -0700 (PDT) Received: from itchy.mindspring.com (itchy.mindspring.com [204.180.128.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA10103 for ; Fri, 18 Oct 1996 19:00:08 -0700 (PDT) Received: from rlb.users.mindspring.com (user-168-121-25-139.dialup.mindspring.com [168.121.25.139]) by itchy.mindspring.com (8.7.5/8.7.3) with SMTP id VAA15941 for ; Fri, 18 Oct 1996 21:59:56 -0400 (EDT) Message-ID: <32683637.15FB7483@mindspring.com> Date: Fri, 18 Oct 1996 22:00:23 -0400 From: Ron Bolin X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Build Fails after libc/db/hash/hash_buf.c updated Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In building the system "make" form /usr/src. I now get a build failure after doing a cvsup. I noted that the failure is new since libc/db/hash/hash_buf.c was updated. See below. cc -O -DLIBC_RCS -DSYSLIBC_RCS -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/sr c/lib/libc/locale -DYP -c /usr/src/lib/libc/db/hash/hash_buf.c -o hash_buf.o /usr/src/lib/libc/db/hash/hash_buf.c: In function `__get_buf': /usr/src/lib/libc/db/hash/hash_buf.c:131: `ptrdiff_t' undeclared (first use this function) /usr/src/lib/libc/db/hash/hash_buf.c:131: (Each undeclared identifier is reporte d only once /usr/src/lib/libc/db/hash/hash_buf.c:131: for each function it appears in.) /usr/src/lib/libc/db/hash/hash_buf.c: In function `newbuf': /usr/src/lib/libc/db/hash/hash_buf.c:221: `ptrdiff_t' undeclared (first use this function) *** Error code 1 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 Fri Oct 18 19:01:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA10194 for current-outgoing; Fri, 18 Oct 1996 19:01:32 -0700 (PDT) Received: from itchy.mindspring.com (itchy.mindspring.com [204.180.128.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA10188 for ; Fri, 18 Oct 1996 19:01:27 -0700 (PDT) Received: from rlb.users.mindspring.com (user-168-121-25-139.dialup.mindspring.com [168.121.25.139]) by itchy.mindspring.com (8.7.5/8.7.3) with SMTP id WAA16114 for ; Fri, 18 Oct 1996 22:01:22 -0400 (EDT) Message-ID: <3268368D.59E2B600@mindspring.com> Date: Fri, 18 Oct 1996 22:01:49 -0400 From: Ron Bolin X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: tcpdump fails build nfsv2.h missing Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In building the source tree, I got can't find nfsv2.h for the tcpdump build. I noted that after copying it back to the build dir that a subsequent cvsup removed it again. Is this correct?? 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 Oct 19 04:35:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA15529 for current-outgoing; Sat, 19 Oct 1996 04:35:04 -0700 (PDT) Received: from ratatosk.algonet.se (mail.algonet.se [194.213.74.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA15511 for ; Sat, 19 Oct 1996 04:34:57 -0700 (PDT) Received: from (johang@kairos.algonet.se [194.213.74.18]) by ratatosk.algonet.se (8.7.4/hdw.1.0) with SMTP id NAA10340 for ; Sat, 19 Oct 1996 13:35:31 +0200 (MET DST) Message-Id: <199610191135.NAA10340@ratatosk.algonet.se> Comments: Authenticated sender is From: "Johan Granlund" To: freebsd-current@FreeBSD.org Date: Sat, 19 Oct 1996 13:28:33 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Etherexpress Pro/100B problems, part2 Priority: normal X-mailer: Pegasus Mail for Win32 (v2.42a) Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi again I still cant get my Pro 100/b TX to work. When looking at tcpdump i can se traffic on the interface but it seems that nothing gets sent from the fxp0 interface to the client. The dosbased diagnostics says ewerything is working and the machines talkes there. I don't have a hub. 2 machines is connected with a crossed cable. Tried moving the IRQ used around (5, 7, 9, 10, 11 some where shared) but no change. Even tried to change to a MR Bios bios. Everything seems normal exept that its dead and i get the "phoenix /kernel: fxp0: device timeout " messages. Now running on the surviving 3c509 adapter in the server and that works fine, but i want my 100Mbit! I'm wondering if i'm forgetting something? >From /etc/sysconfig: network_interfaces="fxp0 ep0 lo0 tun0" ifconfig_fxp0="inet 192.168.0.1 netmask 255.255.255.0" #ifconfig_ep0="inet 192.168.0.1 netmask 255.255.255.0" ifconfig_lo0="inet localhost" The only thing i'm doing is to move the commentchar between the fxp0 and ep0 ifconfig line and rebooting. >From dmesg: Oct 17 20:13:11 phoenix /kernel: fxp0 rev 1 int a irq 7 on pci0:16 Oct 17 20:13:11 phoenix/kernel: mapreg[10] type=0 addr=fffbe000 size=1000. Oct 17 20:13:11 phoenix /kernel: mapreg[14] type=1 addr=0000ff80 size=0020. Oct 17 20:13:11 phoenix /kernel: mapreg[18] type=0 addr=ffe00000 size=100000. Oct 17 20:13:11 phoenix /kernel: reg16: virtual=0xf4879000 physical=0xfffbe000 size=0x1000 Oct 17 20:13:11 phoenix /kernel: fxp0: Ethernet address 00:a0:c9:22:e3:89 Oct 1720:13:11 phoenix /kernel: bpf: fxp0 attached My machine: Intel endevour (Advanced EV) Adaptec 2940 Diamond Stealth64 DRAM Video Vibra 16 sound (Both enabled/diabled) Intel Etherexpress Pro 100B TX 3c509 (I/0 300, IRQ 15 nonPNP) Reagards Johan ___________________________________________________________ Internet: Johang@Algonet.se I don't even speak for myself From owner-freebsd-current Sat Oct 19 06:07:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA20257 for current-outgoing; Sat, 19 Oct 1996 06:07:21 -0700 (PDT) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA20251 for ; Sat, 19 Oct 1996 06:07:15 -0700 (PDT) Received: by sovcom.kiae.su id AA28354 (5.65.kiae-1 ); Sat, 19 Oct 1996 16:05:41 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sat, 19 Oct 96 16:05:41 +0300 Received: (from ache@localhost) by nagual.ru (8.7.6/8.7.3) id RAA00689; Sat, 19 Oct 1996 17:00:32 +0400 (MSD) Message-Id: <199610191300.RAA00689@nagual.ru> Subject: Re: tcpdump fails build nfsv2.h missing In-Reply-To: <3268368D.59E2B600@mindspring.com> from "Ron Bolin" at "Oct 18, 96 10:01:49 pm" To: rlb@mindspring.com (Ron Bolin) Date: Sat, 19 Oct 1996 17:00:31 +0400 (MSD) Cc: freebsd-current@FreeBSD.org From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL28 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > In building the source tree, I got can't find nfsv2.h for the tcpdump > build. I noted that after copying it back to the build dir that a > subsequent > cvsup removed it again. Is this correct?? I found this bug too, please fix it. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Sat Oct 19 07:17:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA22783 for current-outgoing; Sat, 19 Oct 1996 07:17:12 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA22775 for ; Sat, 19 Oct 1996 07:17:07 -0700 (PDT) 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 PAA07542 for ; Sat, 19 Oct 1996 15:17:06 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id PAA09289 for freebsd-current@freefall.cdrom.com; Sat, 19 Oct 1996 15:22:20 +0100 Date: Sat, 19 Oct 1996 15:22:20 +0100 From: Christoph Kukulies Message-Id: <199610191422.PAA09289@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: device ncr0 (?)) in LINT kernel Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I believe that is a bogon and should be controller ncr0 (rather than device ncr0) in the LINT kernel. I got some 'ncr connected to non-controller'. Could someone please correct this? --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Sat Oct 19 10:27:06 1996 Return-Path: owner-current ReceiFrom owner-freebsd-current Sat Oct 19 15:00:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA11876 for current-outgoing; Sat, 19 Oct 1996 15:00:59 -0700 (PDT) Received: from ratatosk.algonet.se (mail.algonet.se [194.213.74.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA11851 for ; Sat, 19 Oct 1996 15:00:38 -0700 (PDT) Received: from (johang@sophocles.algonet.se [194.213.74.12]) by ratatosk.algonet.se (8.7.4/hdw.1.0) with SMTP id AAA20257; Sun, 20 Oct 1996 00:00:48 +0200 (MET DST) Message-Id: <199610192200.AAA20257@ratatosk.algonet.se> Comments: Authenticated sender is From: "Johan Granlund" To: dg@Root.COM, freebsd-current@FreeBSD.org Date: Sat, 19 Oct 1996 23:53:51 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Etherexpress Pro/100B problems, part2 Priority: normal X-mailer: Pegasus Mail for Win32 (v2.42a) Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > >Nope forgot to :-) I'm running -Current with a kernel of today > >(CTM patch 2327). if_fxp.c is at V1.21. That means that cbp->crscdt > >already is 1. Unlucky me. > > Try changing it to 0. :-) > reporting back (again): Sorry no change :-( > The problem really does sound like it is with interrupts and not the card > configuration or driver... > > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project > > ___________________________________________________________ Internet: Johang@Algonet.se I don't even speak for myself From owner-freebsd-current Sat Oct 19 15:49:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA16020 for current-outgoing; Sat, 19 Oct 1996 15:49:07 -0700 (PDT) Received: (from pst@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA15990; Sat, 19 Oct 1996 15:48:58 -0700 (PDT) Date: Sat, 19 Oct 1996 15:48:58 -0700 (PDT) From: Paul Traina Message-Id: <199610192248.PAA15990@freefall.freebsd.org> To: committers, current Subject: xterm termcap definition Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Some folks are complaining about the behavior of the nexw xterm definition. I've restored us to the ANCIENT X1 0 compatible xterm definition we had a week ago. until we get to ghehthe bottom of things, then I'll move us forward to the X11R6 compatible definition again. :-( From owner-freebsd-current Sat Oct 19 15:59:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA17218 for current-outgoing; Sat, 19 Oct 1996 15:59:55 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA17206; Sat, 19 Oct 1996 15:59:46 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA10099; Sat, 19 Oct 1996 16:59:39 -0600 (MDT) Date: Sat, 19 Oct 1996 16:59:39 -0600 (MDT) Message-Id: <199610192259.QAA10099@rocky.mt.sri.com> From: Nate Williams To: Paul Traina Cc: committers@freefall.freebsd.org, current@freefall.freebsd.org Subject: Re: xterm termcap definition In-Reply-To: <199610192248.PAA15990@freefall.freebsd.org> References: <199610192248.PAA15990@freefall.freebsd.org> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Some folks are complaining about the behavior of the nexw xterm definition. > I've restored us to the ANCIENT X1 0 compatible xterm definition we had > a week ago. until we get to ghehthe bottom of things, then I'll move us forward > to the X11R6 compatible definition again. :-( Thanks! Nate From owner-freebsd-current Sat Oct 19 21:09:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA03392 for current-outgoing; Sat, 19 Oct 1996 21:09:49 -0700 (PDT) Received: from crab.cie.nsysu.edu.tw ([140.117.169.94]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA03379 for ; Sat, 19 Oct 1996 21:09:41 -0700 (PDT) Received: (from root@localhost) by crab.cie.nsysu.edu.tw (8.7.5/8.7.3) id MAA03412; Sun, 20 Oct 1996 12:15:05 +0800 (CST) Date: Sun, 20 Oct 1996 12:15:05 +0800 (CST) From: Charlie ROOT To: "FreeBSD.src" Subject: subscribe current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk subscribe current subscribe cvs-all From owner-freebsd-current Sat Oct 19 22:03:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA06944 for current-outgoing; Sat, 19 Oct 1996 22:03:38 -0700 (PDT) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA06938 for ; Sat, 19 Oct 1996 22:03:32 -0700 (PDT) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.6.11/8.6.9) id PAA16647; Sun, 20 Oct 1996 15:03:23 +1000 From: David Dawes Message-Id: <199610200503.PAA16647@rf900.physics.usyd.edu.au> Subject: Re: Xterm wierdness after 'make world'... To: dmaddox@scsn.net Date: Sun, 20 Oct 1996 15:03:22 +1000 (EST) Cc: current@freebsd.org In-Reply-To: <199610191924.PAA00255@rhiannon.scsn.net> from "Donald J. Maddox" at Oct 19, 96 03:24:25 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > After doing a 'make world' last night, I now find that most >(all?) programs that use libtermcap now act strangely... When >reading mail with elm, for example, all characters are printed >in reverse video. Using 'more' to read a short file (less than >a screenful) is no longer possible, because the file is >displayed, and the screen is instantly restored before there is >any chance to see any of it. Longer files work as expected, >except for the last page, which is cleared before it can be >read. It looks like termcap has been changed to include the latest XFree86 xterm entry. The current xterm has some features not present in older versions, and this is reflected in the termcap entry. One is that 'end standout mode' (se) now only turns off standout mode rather than turning off all attributes. Old xterms don't recognise that esc sequence, so reverse video mode doesn't get turned off. The second problem is related to the ti and te termcap entries. These are switching to an alternate screen buffer while 'more' is running, then switching back afterwards. I've been setting my PAGER to 'more -e' which is OK for the last page of longer files, but still doesn't fix things for short files. The X Consortium's standard R6 termcap entry for xterm also does this. David From owner-freebsd-current Sat Oct 19 23:27:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA10413 for current-outgoing; Sat, 19 Oct 1996 23:27:54 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA10406 for ; Sat, 19 Oct 1996 23:27:51 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id XAA19430; Sat, 19 Oct 1996 23:26:29 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id XAA27419; Sat, 19 Oct 1996 23:26:11 -0700 (PDT) Message-Id: <199610200626.XAA27419@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: David Dawes cc: dmaddox@scsn.net, current@freebsd.org Subject: Re: Xterm wierdness after 'make world'... In-reply-to: Your message of Sun, 20 Oct 96 15:03:22 +1000. <199610200503.PAA16647@rf900.physics.usyd.edu.au> Date: Sat, 19 Oct 1996 23:26:10 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >The second problem is related to the ti and te termcap entries. >These are switching to an alternate screen buffer while 'more' is >running, then switching back afterwards. I've been setting my >PAGER to 'more -e' which is OK for the last page of longer files, but >still doesn't fix things for short files. The X Consortium's standard >R6 termcap entry for xterm also does this. Just for the record, I REALLY REALLY HATE this option... ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... -----------------------------------------------------------------------------