From owner-freebsd-current Sun Feb 22 00:04:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01909 for freebsd-current-outgoing; Sun, 22 Feb 1998 00:04:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01880 for ; Sun, 22 Feb 1998 00:04:12 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id CAA21731; Sun, 22 Feb 1998 02:04:02 -0600 (CST) From: Kevin Day Message-Id: <199802220804.CAA21731@home.dragondata.com> Subject: Re: panic: vm_page_unwire: invalid wire count: 0 In-Reply-To: <199802220013.TAA00419@grasshopper.cs.duke.edu> from Andrew Gallatin at "Feb 21, 98 07:13:56 pm" To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Sun, 22 Feb 1998 02:04:01 -0600 (CST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Another note: Pulling back old kernels, I've found that Feb 5th doesn't have this bug, Feb 15th does. It's somewhere in there, John. :) echo 'main() { printf ("Hello");}' > foo.c ; cc foo.c ; ./a.out ; cc foo.c works great to reproduce it. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 01:39:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08999 for freebsd-current-outgoing; Sun, 22 Feb 1998 01:39:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08994 for ; Sun, 22 Feb 1998 01:39:06 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id BAA11163; Sun, 22 Feb 1998 01:38:33 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802220938.BAA11163@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Kevin Day cc: gallatin@cs.duke.edu (Andrew Gallatin), current@FreeBSD.ORG Subject: Re: panic: vm_page_unwire: invalid wire count: 0 In-reply-to: Your message of "Sun, 22 Feb 1998 02:04:01 CST." <199802220804.CAA21731@home.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Feb 1998 01:38:33 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Another note: > > Pulling back old kernels, I've found that Feb 5th doesn't have this bug, Feb > 15th does. > > It's somewhere in there, John. :) > > echo 'main() { printf ("Hello");}' > foo.c ; cc foo.c ; ./a.out ; cc foo.c > > works great to reproduce it. > > Tried your example and it does not crash any of my systems over here. last updated the system on friday. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 01:49:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09784 for freebsd-current-outgoing; Sun, 22 Feb 1998 01:49:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley585.res.iastate.edu (friley585.res.iastate.edu [129.186.167.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09779 for ; Sun, 22 Feb 1998 01:49:21 -0800 (PST) (envelope-from ccsanady@friley585.res.iastate.edu) Received: from friley585.res.iastate.edu (loopback [127.0.0.1]) by friley585.res.iastate.edu (8.8.8/8.8.8) with ESMTP id DAA00394; Sun, 22 Feb 1998 03:49:15 -0600 (CST) (envelope-from ccsanady@friley585.res.iastate.edu) Message-Id: <199802220949.DAA00394@friley585.res.iastate.edu> To: Julian Elischer cc: "Matthew N. Dodd" , current@FreeBSD.ORG Subject: CCD Fix (Was: Re: New SoftUpdates test kit) In-reply-to: Your message of "Sat, 21 Feb 1998 22:33:56 PST." Date: Sun, 22 Feb 1998 03:49:15 -0600 From: Chris Csanady Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I don;t know yet however kirk says that the symptom is exactly matching >that he saw with bufs not being bzero'd when malloc'd. >I'm going to look at that next week. Well, this seems to be it. :) I remember seeing something like this while browsing through the OpenBSD cvs tree, but the log message did not mention that the change had such serious implications. Anyways, with the following diff, soft updates should work with CCD's. Or rather the other way around.. ;) Chris *** ccd.c Sun Feb 15 05:13:27 1998 --- /sys/dev/ccd/ccd.c Sun Feb 22 01:43:26 1998 *************** *** 885,890 **** --- 885,891 ---- * Fill in the component buf structure. */ cbp = getccdbuf(); + bzero(cbp, sizeof (struct ccdbuf)); cbp->cb_buf.b_flags = bp->b_flags | B_CALL; cbp->cb_buf.b_iodone = (void (*)(struct buf *))ccdiodone; cbp->cb_buf.b_proc = bp->b_proc; *************** *** 919,924 **** --- 920,926 ---- (cbp->cb_buf.b_flags & B_READ) == 0) { /* mirror, start one more write */ cbp = getccdbuf(); + bzero(cbp, sizeof (struct ccdbuf)); *cbp = *cb[0]; cbp->cb_buf.b_dev = ci2->ci_dev; cbp->cb_buf.b_vp = ci2->ci_vp; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 02:03:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11348 for freebsd-current-outgoing; Sun, 22 Feb 1998 02:03:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11320 for ; Sun, 22 Feb 1998 02:03:40 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id CAA25805; Sun, 22 Feb 1998 02:03:00 -0800 (PST) To: Chris Csanady cc: Julian Elischer , "Matthew N. Dodd" , current@FreeBSD.ORG Subject: Re: CCD Fix (Was: Re: New SoftUpdates test kit) In-reply-to: Your message of "Sun, 22 Feb 1998 03:49:15 CST." <199802220949.DAA00394@friley585.res.iastate.edu> Date: Sun, 22 Feb 1998 02:02:59 -0800 Message-ID: <25801.888141779@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, this seems to be it. :) I remember seeing something like this while > browsing through the OpenBSD cvs tree, but the log message did not mention > that the change had such serious implications. > > Anyways, with the following diff, soft updates should work with CCD's. > Or rather the other way around.. ;) Yowza! Thanks, committed to both branches. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 04:05:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA23098 for freebsd-current-outgoing; Sun, 22 Feb 1998 04:05:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA23091 for ; Sun, 22 Feb 1998 04:05:20 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id FAA04494; Sun, 22 Feb 1998 05:05:16 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp01.primenet.com, id smtpd004489; Sun Feb 22 05:05:15 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id FAA29448; Sun, 22 Feb 1998 05:05:08 -0700 (MST) From: Terry Lambert Message-Id: <199802221205.FAA29448@usr07.primenet.com> Subject: Re: More breakage in -current as a result of header frobbing. To: nate@mt.sri.com (Nate Williams) Date: Sun, 22 Feb 1998 12:05:08 +0000 (GMT) Cc: tlambert@primenet.com, nate@mt.sri.com, current@FreeBSD.ORG In-Reply-To: <199802220518.WAA22819@mt.sri.com> from "Nate Williams" at Feb 21, 98 10:18:01 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Sure there is. Society and human nature. Human beings simply cannot be > forced to 'Do the Right Thing'. There is no way to force 'right > behavior' automaticaly. Human behavior can only be modified if the > person desires to change, and that desire to change cannot be 'forced' > by any automatic tool. The laws of physics are an automatic tool, and "right behaviour", by definition, is "in accordance with the laws of physics". There's all sorts of nice feedback loops which enforce this, the most severe of which is "you die if you do not act in accord". You can pretend gravity does not exist on a cliff face. But you can only pretend once. > Your 'global' lock does *NOTHING* (!!!!!!!!!) to make the tree any more > buildable when in fact it is my poor coding skills/testing behavior that > breaks the tree. The commit I did was a bad commit, and locking the > tree and then unlocking the tree after I finished commit doesn't > magically make it a good commit. No. But it makes it obvious that it was *you* that did it. And if you do it consistently, you *should* lose your priviledges that allow you to do it. This is called a feedback loop. > Sometimes your absolute silliness appears to be a lack of intelligence > at times. I think you don't understand the concept of environmental enforcement of desirable behaviour. FreeBSD is free to choose whatever environment it wants, within the scope of physical laws. Including an environment that punishes tree breakage, if it's smart enough to do so. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 04:34:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA25019 for freebsd-current-outgoing; Sun, 22 Feb 1998 04:34:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA25013 for ; Sun, 22 Feb 1998 04:34:28 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.8/8.8.7) id OAA11729 for freebsd-current@freebsd.org; Sun, 22 Feb 1998 14:34:22 +0200 (SAT) From: John Hay Message-Id: <199802221234.OAA11729@zibbi.mikom.csir.co.za> Subject: clock code working properly in -current? To: freebsd-current@FreeBSD.ORG Date: Sun, 22 Feb 1998 14:34:22 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The new clock code seems to be broken (for me at least) or is there something that I must do/set/configure to make things work again? With kernels build today, both my 90MHz Pentium UP machine and my 266MHz PII SMP machine gain a lot of time. The Pentium gain about 2 seconds per minute and the SMP machine about 1 second per minute. Needless to say xntpd can't cope with a frequency error that big. Previously xntpd and ntp-4 reported a 24ppm error on the Pentium and a -297ppm error on the SMP machine. One other strange thing that I noticed is that "systat -vmstat" on the SMP machine reports the clk0 interrupt rate as 50 and the rtc0 rate as 64, while on the UP machine it is still reported as 100 and 128 like before. Is there something I can try out to fix this? At this rate it will be tomorrow a lot sooner than I anticipated. :-) John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 04:44:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA25749 for freebsd-current-outgoing; Sun, 22 Feb 1998 04:44:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA25742 for ; Sun, 22 Feb 1998 04:44:53 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id NAA11058; Sun, 22 Feb 1998 13:39:47 +0100 (CET) To: John Hay cc: freebsd-current@FreeBSD.ORG Subject: Re: clock code working properly in -current? In-reply-to: Your message of "Sat, 22 Feb 1998 14:34:22 +0200." <199802221234.OAA11729@zibbi.mikom.csir.co.za> Date: Sun, 22 Feb 1998 13:39:47 +0100 Message-ID: <11056.888151187@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199802221234.OAA11729@zibbi.mikom.csir.co.za>, John Hay writes: >Hi, > >The new clock code seems to be broken (for me at least) or is there >something that I must do/set/configure to make things work again? > >With kernels build today, both my 90MHz Pentium UP machine and my 266MHz >PII SMP machine gain a lot of time. The Pentium gain about 2 seconds per >minute and the SMP machine about 1 second per minute. Needless to say >xntpd can't cope with a frequency error that big. Previously xntpd and >ntp-4 reported a 24ppm error on the Pentium and a -297ppm error on the >SMP machine. Yes, please boot with '-v', and send me the dmesg output & the output of sysctl -a. Add CLK_USE_TSC_CALIBRATION and CLK_USE_I8254_CALIBRATION to your kernel, and repeat. >One other strange thing that I noticed is that "systat -vmstat" on the >SMP machine reports the clk0 interrupt rate as 50 and the rtc0 rate as >64, while on the UP machine it is still reported as 100 and 128 like >before. This is unrelated I belive. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 05:09:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA27235 for freebsd-current-outgoing; Sun, 22 Feb 1998 05:09:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA27227 for ; Sun, 22 Feb 1998 05:09:23 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id OAA16435; Sun, 22 Feb 1998 14:09:09 +0100 (MET) (envelope-from sos) Message-Id: <199802221309.OAA16435@sos.freebsd.dk> Subject: Re: clock code working properly in -current? In-Reply-To: <11056.888151187@critter.freebsd.dk> from Poul-Henning Kamp at "Feb 22, 98 01:39:47 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Sun, 22 Feb 1998 14:09:03 +0100 (MET) Cc: jhay@mikom.csir.co.za, freebsd-current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Poul-Henning Kamp who wrote: > In message <199802221234.OAA11729@zibbi.mikom.csir.co.za>, John Hay writes: > > >One other strange thing that I noticed is that "systat -vmstat" on the > >SMP machine reports the clk0 interrupt rate as 50 and the rtc0 rate as > >64, while on the UP machine it is still reported as 100 and 128 like > >before. > > This is unrelated I belive. Yes, but an old problem, it occurred together with Poul's first round of clock changes 'bout a month ago. It is only seen on SMP systems. I'm not sure its directly related to the clock changes, it might be some other SMP change that crept in without me noticing. I've not checked but it could look like all intr. counts are halfed, the actual interrups doues occur though. A vmstat -i shows that the rates are OK... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 05:12:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA27797 for freebsd-current-outgoing; Sun, 22 Feb 1998 05:12:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA27788; Sun, 22 Feb 1998 05:12:35 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id OAA11146; Sun, 22 Feb 1998 14:08:00 +0100 (CET) To: sos@FreeBSD.ORG cc: jhay@mikom.csir.co.za, freebsd-current@FreeBSD.ORG Subject: Re: clock code working properly in -current? In-reply-to: Your message of "Sun, 22 Feb 1998 14:09:03 +0100." <199802221309.OAA16435@sos.freebsd.dk> Date: Sun, 22 Feb 1998 14:07:59 +0100 Message-ID: <11144.888152879@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199802221309.OAA16435@sos.freebsd.dk>, Søren Schmidt writes: >Yes, but an old problem, it occurred together with Poul's first round of >clock changes 'bout a month ago. It is only seen on SMP systems. >I'm not sure its directly related to the clock changes, it might be some >other SMP change that crept in without me noticing. I've not checked but >it could look like all intr. counts are halfed, the actual interrups >doues occur though. A vmstat -i shows that the rates are OK... Yeah, I'm pretty convinced that this is not my doing and that it is harmless, or at least "mostly harmless" :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 05:29:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28731 for freebsd-current-outgoing; Sun, 22 Feb 1998 05:29:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailhost (user-38lcbbe.dialup.mindspring.com [209.86.45.110]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA28726 for ; Sun, 22 Feb 1998 05:29:20 -0800 (PST) (envelope-from rlb@mindspring.com) Received: from mindspring.com by mailhost with smtp (Smail3.1.29.1 #1) id m0y6bTK-000G5ZC; Sun, 22 Feb 98 08:29 EST Message-ID: <34F02840.2F9D3028@mindspring.com> Date: Sun, 22 Feb 1998 08:29:36 -0500 From: Ron Bolin X-Mailer: Mozilla 4.04 [en] (X11; I; SunOS 5.6 i86pc) MIME-Version: 1.0 To: FreeBSD Current Mailing List Subject: VM SYSTEM REPORT Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG About 3 weeks ago, my system (Pent 133/64MB, all SCSI) would exit X after running xscreensaver about 2 hours. I am happy to report that it is no longer a problem. The VM changes made around 2-9-98 seemed seemed to have done the trick. Thanks Ron :-) -- ------------------------------------------------------------------------------- Ron Bolin, Sr. Software Eng, NetChannel Web: http://www.netchannel.net E-mail: rbolin@netchannel.net Web: http://www.gsu.edu/~gs01rlb Ph: 770-729-2929 Ext 249 Hm: 770-992-8877 Web: http://www.mindspring.com/~rlb ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 06:16:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01853 for freebsd-current-outgoing; Sun, 22 Feb 1998 06:16:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01815 for ; Sun, 22 Feb 1998 06:15:41 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id PAA25647 for current@FreeBSD.ORG; Sun, 22 Feb 1998 15:15:23 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id PAA00441; Sun, 22 Feb 1998 15:03:21 +0100 (CET) (envelope-from roberto) Message-ID: <19980222150321.02448@keltia.freenix.fr> Date: Sun, 22 Feb 1998 15:03:21 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: New SoftUpdates test kit Mail-Followup-To: current@FreeBSD.ORG References: <34EE3060.4487EB71@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.3i In-Reply-To: <34EE3060.4487EB71@whistle.com>; from Julian Elischer on Fri, Feb 20, 1998 at 05:39:45PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4087 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Julian Elischer: > This is quite solid. Enjoy! I still get the "vm_fault on nofault entry" panic with this code, sorry. kgdb output follows. Tell me if you want more info on a specific frame or variable. I always get this when uuxqt is working at unbatching news... #0 boot (howto=260) at ../../kern/kern_shutdown.c:296 296 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=260) at ../../kern/kern_shutdown.c:296 #1 0xf01135a7 in panic (fmt=0xf01013e8 "from debugger") at ../../kern/kern_shutdown.c:436 #2 0xf0101405 in db_panic (addr=-266775763, have_addr=0, count=-1, modif=0xf4ad7a04 "") at ../../ddb/db_command.c:432 #3 0xf01012e5 in db_command (last_cmdp=0xf01c9ad4, cmd_table=0xf01c9934, aux_cmd_tablep=0xf01d89f8) at ../../ddb/db_command.c:332 #4 0xf0101472 in db_command_loop () at ../../ddb/db_command.c:454 #5 0xf0103b33 in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71 #6 0xf0195101 in kdb_trap (type=3, code=0, regs=0xf4ad7af0) at ../../i386/i386/db_interface.c:157 #7 0xf019f628 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = -266851232, tf_ebp = -189957324, tf_isp = -189957352, tf_ebx = 256, tf_edx = -266775819, tf_ecx = 0, tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -266775763, tf_cs = 8, tf_eflags = 582, tf_esp = -266775835, tf_ss = -267307716}) at ../../i386/i386/trap.c:474 #8 0xf019532d in Debugger (msg=0xf011353c "panic") at ../../i386/i386/db_interface.c:316 #9 0xf011359e in panic ( fmt=0xf0182c60 "vm_fault: fault on nofault entry, addr: %lx") at ../../kern/kern_shutdown.c:434 #10 0xf0182d94 in vm_fault (map=0xf01e3f00, vaddr=4070191104, fault_type=3 '\003', fault_flags=0) at ../../vm/vm_fault.c:225 #11 0xf019f888 in trap_pfault (frame=0xf4ad7c5c, usermode=0) at ../../i386/i386/trap.c:724 #12 0xf019f507 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -224776192, tf_esi = -219834368, tf_ebp = -189956920, tf_isp = -189956988, tf_ebx = -226566988, tf_edx = 4096, tf_ecx = 512, tf_eax = -4941824, tf_trapno = 12, tf_err = 2, tf_eip = -266739278, tf_cs = 8, tf_eflags = 66070, tf_esp = -258382464, tf_ss = -258561600}) at ../../i386/i386/trap.c:363 #13 0xf019e1b2 in generic_bcopy () #14 0xf017256f in softdep_setup_allocindir_page (ip=0xf0907000, lbn=13, bp=0xf27edcb4, ptrno=1, newblkno=171112, oldblkno=0, nbp=0xf284a53c) at ../../ufs/ffs/ffs_softdep.c:1416 #15 0xf016fafd in ffs_balloc (ap=0xf4ad7e58) at ../../ufs/ffs/ffs_balloc.c:302 #16 0xf01790ac in ffs_write (ap=0xf4ad7eac) at vnode_if.h:995 #17 0xf013ac27 in vn_write (fp=0xf0996440, uio=0xf4ad7f30, cred=0xf082f100) at vnode_if.h:331 #18 0xf011bb9f in writev (p=0xf4ac69c0, uap=0xf4ad7f84) at ../../kern/sys_generic.c:354 #19 0xf01a00ef in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 184, tf_esi = 4, tf_ebp = -272639252, tf_isp = -189956140, tf_ebx = -272638608, tf_edx = 26, tf_ecx = 5806, tf_eax = 121, tf_trapno = 7, tf_err = 7, tf_eip = 537360513, tf_cs = 31, tf_eflags = 514, tf_esp = -272639280, tf_ss = 39}) at ../../i386/i386/trap.c:994 #20 0x20077881 in ?? () #21 0x1869 in ?? () #22 0x1b34 in ?? () #23 0x1d4f in ?? () #24 0x1095 in ?? () (kgdb) info registers eax 0x0 0 ecx 0x0 0 edx 0x0 0 ebx 0x0 0 esp 0xf4ad79a0 0xf4ad79a0 ebp 0xf4ad79b4 0xf4ad79b4 esi 0xf01013e8 -267381784 edi 0x104 260 eip 0xf01132bb 0xf01132bb eflags 0x0 0 cs 0x0 0 ss 0x0 0 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 (kgdb) up #14 0xf017256f in softdep_setup_allocindir_page (ip=0xf0907000, lbn=13, bp=0xf27edcb4, ptrno=1, newblkno=171112, oldblkno=0, nbp=0xf284a53c) at ../../ufs/ffs/ffs_softdep.c:1416 1416 setup_allocindir_phase2(bp, ip, aip); (kgdb) list 1411 if ((ip->i_mode & IFMT) == IFDIR && 1412 pagedep_lookup(ip, lbn, DEPALLOC, &pagedep) == 0) 1413 WORKLIST_INSERT(&nbp->b_dep, &pagedep->pd_list); 1414 WORKLIST_INSERT(&nbp->b_dep, &aip->ai_list); 1415 FREE_LOCK(&lk); 1416 setup_allocindir_phase2(bp, ip, aip); 1417 } 1418 1419 /* 1420 * Called just before setting an indirect block pointer to a (kgdb) print *bp $3 = {b_hash = {le_next = 0xf2834cc4, le_prev = 0xf01dfa9c}, b_vnbufs = { le_next = 0x0, le_prev = 0xf284a544}, b_freelist = {tqe_next = 0xf2825d3c, tqe_prev = 0xf27ebcd4}, b_act = {tqe_next = 0x0, tqe_prev = 0xf07bad14}, b_proc = 0x0, b_flags = 536870960, b_qindex = 0, b_usecount = 7 '\a', b_error = 0, b_bufsize = 4096, b_bcount = 4096, b_resid = 0, b_dev = 4294967295, b_data = 0xf2e59000 "8\234\002", b_kvabase = 0xf2e59000 "8\234\002", b_kvasize = 4096, b_lblkno = -12, b_blkno = -12, b_iodone = 0, b_iodone_chain = 0x0, b_vp = 0xf4b5abe0, b_dirtyoff = 0, b_dirtyend = 0, b_generation = 12, b_rcred = 0x0, b_wcred = 0x0, b_validoff = 0, b_validend = 0, b_pblkno = 1964649, b_saveaddr = 0x0, b_savekva = 0x0, b_driver1 = 0x0, b_driver2 = 0x0, b_spc = 0x0, b_cluster = {cluster_head = {tqh_first = 0x0, tqh_last = 0x0}, cluster_entry = {tqe_next = 0x0, tqe_prev = 0x0}}, b_pages = {0xf04847a8, 0x0 }, b_npages = 1, b_dep = {lh_first = 0x0}} (kgdb) print ip $7 = (struct inode *) 0xf27edcb4 (kgdb) print *ip $4 = {i_lock = {lk_interlock = {lock_data = -226276156}, lk_flags = 4028496540, lk_sharecount = 0, lk_waitcount = -226187964, lk_exclusivecount = 23868, lk_prio = -3454, lk_wmesg = 0xf27ebcd4 "<]\202òh\225}ò", lk_timo = 0, lk_lockholder = -260330220}, i_hash = {le_next = 0x0, le_prev = 0x20000030}, i_vnode = 0x70000, i_devvp = 0x0, i_flag = 4096, i_dev = 4096, i_number = 0, i_effnlink = -1, inode_u = {fs = 0xf2e59000, e2fs = 0xf2e59000}, i_dquot = {0xf2e59000, 0x1000}, i_modrev = 0xfffffff4fffffff4, i_lockf = 0x0, i_count = 0, i_endoff = -189420576, i_diroff = 0, i_offset = 0, i_ino = 12, i_reclen = 0, i_spare = {0, 0, 0, 1964649, 0}, i_din = {di_mode = 0, di_nlink = 0, di_u = { oldids = {0, 0}, inumber = 0}, di_size = 0, di_atime = 0, di_atimensec = 0, di_mtime = -263698520, di_mtimensec = 0, di_ctime = 0, di_ctimensec = 0, di_db = {0 }, di_ib = {0, 0, 0}, di_flags = 0, di_blocks = 0, di_gen = 0, di_uid = 0, di_gid = 0, di_spare = {0, 0}}} (kgdb) print *aip $5 = {ai_list = {wk_list = {le_next = 0x0, le_prev = 0x0}, wk_type = 0, wk_state = 0}, ai_next = {le_next = 0x0, le_prev = 0x0}, ai_offset = 0, ai_newblkno = 0, ai_oldblkno = 0, ai_freefrag = 0x0, ai_indirdep = 0x0, ai_deps = {le_next = 0x0, le_prev = 0x0}, ai_buf = 0x0} (kgdb) print aip $6 = (struct allocindir *) 0xf2e59800 -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #3: Fri Feb 20 22:55:09 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 06:40:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03164 for freebsd-current-outgoing; Sun, 22 Feb 1998 06:40:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03159 for ; Sun, 22 Feb 1998 06:40:25 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id HAA10768; Sun, 22 Feb 1998 07:40:24 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id HAA24031; Sun, 22 Feb 1998 07:40:22 -0700 Date: Sun, 22 Feb 1998 07:40:22 -0700 Message-Id: <199802221440.HAA24031@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Terry Lambert Cc: nate@mt.sri.com (Nate Williams), current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: <199802221205.FAA29448@usr07.primenet.com> References: <199802220518.WAA22819@mt.sri.com> <199802221205.FAA29448@usr07.primenet.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Your 'global' lock does *NOTHING* (!!!!!!!!!) to make the tree any more > > buildable > > No. But it makes it obvious that it was *you* that did it. No more so than the current behavior. It is known *now* who breaks the tree, since breaking the tree is related to the commit, not the lock. > And if you do it consistently, you *should* lose your priviledges that > allow you to do it. Nobody is willing to brandish the 'lose your priviledges' stick. ;( > > Sometimes your absolute silliness appears to be a lack of intelligence > > at times. > > I think you don't understand the concept of environmental enforcement > of desirable behaviour. FreeBSD is free to choose whatever environment > it wants, within the scope of physical laws. Including an environment > that punishes tree breakage, if it's smart enough to do so. Sure I do, but a feedback loop is related to the feedback, and if you add steps in the process that are unrelated to the feedback loop, you're not doing anything to change the feedback, just adding more noise to the system. Aka. Sticking llamas in the office doesn't make the programmer want to do good commits, but telling them to do so 'or else' (with a backed up 'or else') does. FreeBSD's problem is that everyone has 'broken' the tree enough times that no-one is willing to brandish the 'big stick' to whack people for making bad commits. If you've got no negative feedback, then you've got no reason to test changes. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 07:47:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06996 for freebsd-current-outgoing; Sun, 22 Feb 1998 07:47:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06979 for ; Sun, 22 Feb 1998 07:46:36 -0800 (PST) (envelope-from archer@grape.carrier.kiev.ua) Received: from unicorn.carrier.kiev.ua (unicorn.carrier.kiev.ua [193.193.193.113]) by burka.carrier.kiev.ua (8.8.8/8.Who.Cares) with ESMTP id RAA13284 for ; Sun, 22 Feb 1998 17:35:18 +0200 (EET) Received: from kozlik.carrier.kiev.ua (kozlik.carrier.kiev.ua [193.193.193.111]) by unicorn.carrier.kiev.ua (8.8.8/8.8.7) with ESMTP id RAA18861 for ; Sun, 22 Feb 1998 17:35:16 +0200 (EET) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.8.8/8.8.8/8.Who.Cares) with UUCP id RAA27697 for current@freebsd.org; Sun, 22 Feb 1998 17:32:20 +0200 (EET) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.8.8/8.8.8) id RAA11735; Sun, 22 Feb 1998 17:24:19 +0200 (EET) (envelope-from archer) Date: Sun, 22 Feb 1998 17:24:19 +0200 (EET) From: Alexander Litvin Message-Id: <199802221524.RAA11735@grape.carrier.kiev.ua> To: current@FreeBSD.ORG Subject: Re: New SoftUpdates test kit In-Reply-To: <34EE3060.4487EB71@whistle.com> <19980222150321.02448@keltia.freenix.fr> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19980222150321.02448@keltia.freenix.fr> you wrote: > According to Julian Elischer: >> This is quite solid. Enjoy! > I still get the "vm_fault on nofault entry" panic with this code, sorry. > kgdb output follows. Tell me if you want more info on a specific frame or > variable. I always get this when uuxqt is working at unbatching news... Yep, me to. During "make buildworld", system also a bit busy with day-to-day work like mail/news unbatching. panic: vm_fault: fault on nofault entry, addr: f2585000 syncing disks... wd0: interrupt timeout: wd0: status 58 error 0 wd0: interrupt timeout: wd0: status 58 error 0 wd0: interrupt timeout: wd0: status 58 error 0 wd0: interrupt timeout: wd0: status 58 error 0 wd0: interrupt timeout: wd0: status 58 error 0 wd0: Last time I say: interrupt timeout. Probably a portable PC.: ... No crashdump, though I beleive it's repeatable. > #0 boot (howto=260) at ../../kern/kern_shutdown.c:296 > 296 dumppcb.pcb_cr3 = rcr3(); [...] > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #3: Fri Feb 20 22:55:09 CET 1998 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Litvin Alexander No SIGNATURE available at this run-level To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 09:16:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11775 for freebsd-current-outgoing; Sun, 22 Feb 1998 09:16:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11770 for ; Sun, 22 Feb 1998 09:16:42 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id JAA27163; Sun, 22 Feb 1998 09:16:00 -0800 (PST) To: John Hay cc: freebsd-current@FreeBSD.ORG Subject: Re: clock code working properly in -current? In-reply-to: Your message of "Sat, 22 Feb 1998 14:34:22 +0200." <199802221234.OAA11729@zibbi.mikom.csir.co.za> Date: Sun, 22 Feb 1998 09:16:00 -0800 Message-ID: <27159.888167760@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > With kernels build today, both my 90MHz Pentium UP machine and my 266MHz > PII SMP machine gain a lot of time. The Pentium gain about 2 seconds per > minute and the SMP machine about 1 second per minute. Needless to say > xntpd can't cope with a frequency error that big. Previously xntpd and > ntp-4 reported a 24ppm error on the Pentium and a -297ppm error on the > SMP machine. That's pretty interesting since I know of a dual PII box at a friend's place of work that's been doing *exactly* this ever since SMP entered -current; it's never worked properly. You know how hard it is to benchmark a machine who's clock runs twice as fast, too? :-) I wonder if this is a bug which has been latent since the beginning but only bites some people. We asked Steve Passe if he wanted to borrow the box in question but he was too busy. :( Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 09:25:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12774 for freebsd-current-outgoing; Sun, 22 Feb 1998 09:25:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12766 for ; Sun, 22 Feb 1998 09:25:15 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id JAA27205; Sun, 22 Feb 1998 09:24:29 -0800 (PST) To: Nate Williams cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-reply-to: Your message of "Sun, 22 Feb 1998 07:40:22 MST." <199802221440.HAA24031@mt.sri.com> Date: Sun, 22 Feb 1998 09:24:29 -0800 Message-ID: <27201.888168269@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > FreeBSD's problem is that everyone has 'broken' the tree enough times > that no-one is willing to brandish the 'big stick' to whack people for > making bad commits. If you've got no negative feedback, then you've got > no reason to test changes. More to the point, it's far more damaging to alienate and potentially lose an existing volunteer than it is to have the tree occasionally broken, as much as I might whine about that from time to time. We have to consider who we are and how we got here - this isn't commercial software development, as much as we might sometimes try to emulate it. :-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 09:52:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15958 for freebsd-current-outgoing; Sun, 22 Feb 1998 09:52:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15952 for ; Sun, 22 Feb 1998 09:52:57 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA11769; Sun, 22 Feb 1998 10:52:54 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA24429; Sun, 22 Feb 1998 10:52:52 -0700 Date: Sun, 22 Feb 1998 10:52:52 -0700 Message-Id: <199802221752.KAA24429@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: Nate Williams , Terry Lambert , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: <27201.888168269@time.cdrom.com> References: <199802221440.HAA24031@mt.sri.com> <27201.888168269@time.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > FreeBSD's problem is that everyone has 'broken' the tree enough times > > that no-one is willing to brandish the 'big stick' to whack people for > > making bad commits. If you've got no negative feedback, then you've got > > no reason to test changes. > > More to the point, it's far more damaging to alienate and potentially > lose an existing volunteer than it is to have the tree occasionally > broken, as much as I might whine about that from time to time. To a point, I agree. But, if that is indeed the case, then why isn't Terry a committer? He may damage the tree, but we're definitely alienating him. We can't have it both ways. Either we have an *enforced* policy of actually punishing offenders (which may offend them and cause them to run away), or we don't have any policy at all and so claiming to have one only alienates and makes us look foolish. The recent brokeness in -current is a *really* sad state of affairs that could have been easily avoided. However, many committers (myself included) know that in reality there is no punishment for breaking the tree, so why bother testing things more heavily when someone is going to end up doing that work for me? I think recently we have the worst of both worlds. No enforced policy and volunteers who take advantage of it. > We have to consider who we are and how we got here - this isn't We got here by people who put out quality/tested software. This appears to no longer be as important as it once was to many people, including many people in core. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 10:01:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17289 for freebsd-current-outgoing; Sun, 22 Feb 1998 10:01:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17282 for ; Sun, 22 Feb 1998 10:01:18 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id SAA11818; Sun, 22 Feb 1998 18:55:35 +0100 (CET) To: "Jordan K. Hubbard" cc: John Hay , freebsd-current@FreeBSD.ORG Subject: Re: clock code working properly in -current? In-reply-to: Your message of "Sun, 22 Feb 1998 09:16:00 PST." <27159.888167760@time.cdrom.com> Date: Sun, 22 Feb 1998 18:55:35 +0100 Message-ID: <11816.888170135@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <27159.888167760@time.cdrom.com>, "Jordan K. Hubbard" writes: >> With kernels build today, both my 90MHz Pentium UP machine and my 266MHz >> PII SMP machine gain a lot of time. The Pentium gain about 2 seconds per >> minute and the SMP machine about 1 second per minute. Needless to say >> xntpd can't cope with a frequency error that big. Previously xntpd and >> ntp-4 reported a 24ppm error on the Pentium and a -297ppm error on the >> SMP machine. > >That's pretty interesting since I know of a dual PII box at a friend's >place of work that's been doing *exactly* this ever since SMP entered >-current; it's never worked properly. You know how hard it is to >benchmark a machine who's clock runs twice as fast, too? :-) > >I wonder if this is a bug which has been latent since the beginning >but only bites some people. We asked Steve Passe if he wanted to >borrow the box in question but he was too busy. :( Please boot -v and send me the dmesg & sysctl -a outputs, then add to the kernel config CLK_USE_I8254_CALIBRATION and CLK_USE_TSC_CALIBRATION and send the dmesg & sysctl -a for those too. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 10:05:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18214 for freebsd-current-outgoing; Sun, 22 Feb 1998 10:05:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18206 for ; Sun, 22 Feb 1998 10:05:01 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA11848; Sun, 22 Feb 1998 11:04:58 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA24497; Sun, 22 Feb 1998 11:04:56 -0700 Date: Sun, 22 Feb 1998 11:04:56 -0700 Message-Id: <199802221804.LAA24497@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Alexander Litvin Cc: current@FreeBSD.ORG Subject: Re: New SoftUpdates test kit In-Reply-To: <199802221524.RAA11735@grape.carrier.kiev.ua> References: <34EE3060.4487EB71@whistle.com> <19980222150321.02448@keltia.freenix.fr> <199802221524.RAA11735@grape.carrier.kiev.ua> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yep, me to. During "make buildworld", system also a bit busy with > day-to-day work like mail/news unbatching. > > panic: vm_fault: fault on nofault entry, addr: f2585000 > > syncing disks... wd0: interrupt timeout: > wd0: status 58 error 0 Your disk is going bad. Replace it. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 10:25:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20060 for freebsd-current-outgoing; Sun, 22 Feb 1998 10:25:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20048 for ; Sun, 22 Feb 1998 10:25:04 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id TAA11872; Sun, 22 Feb 1998 19:10:05 +0100 (CET) To: Nate Williams cc: "Jordan K. Hubbard" , Terry Lambert , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-reply-to: Your message of "Sun, 22 Feb 1998 10:52:52 MST." <199802221752.KAA24429@mt.sri.com> Date: Sun, 22 Feb 1998 19:10:04 +0100 Message-ID: <11870.888171004@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199802221752.KAA24429@mt.sri.com>, Nate Williams writes: >> > FreeBSD's problem is that everyone has 'broken' the tree enough times >> > that no-one is willing to brandish the 'big stick' to whack people for >> > making bad commits. If you've got no negative feedback, then you've got >> > no reason to test changes. >> >> More to the point, it's far more damaging to alienate and potentially >> lose an existing volunteer than it is to have the tree occasionally >> broken, as much as I might whine about that from time to time. > >To a point, I agree. But, if that is indeed the case, then why isn't >Terry a committer? He may damage the tree, but we're definitely >alienating him. > >We can't have it both ways. Either we have an *enforced* policy of >actually punishing offenders (which may offend them and cause them to >run away), or we don't have any policy at all and so claiming to have >one only alienates and makes us look foolish. The reason why I for one doesn't think Terry should have a commit bit is that he is what we en Denmark calls "An ego-tripper", and on top of that, he will try to drown people in his own dialect of jabber-wocky if they happen to point out that truth and/or reality is not the same as what he preached from his soapbox. Finally you have the choice of a "Because I say so" or a long winded, obfuscated and very often entirely wrong explanation from him if you ask him for details. I short, nothing I want to spend my spare time wading through. And even shorter than that: I don't trust Terry with a commit bit. Apart from the NetBSD core team, I don't think anybody rivals Terry in number of arms the FreeBSD core team has streched out at him. The reasons that bar him from being more involved with FreeBSD than he is at present, are entirely within Terrys power to address. Of course I'm sure, some people will see this as the final clenching proof of the FreeBSD core team being an evil-spirited brotherhood, trying to keep the innocent away from the treasure etc etc etc If you think so, please create a alt.conspiracy.freebsd newsgroup, and leave us alone here to improve the OS that runs your news server. If you guys would get out of my mailbox with your noisy irrationalities, maybe I would have more time to hack code! :-( Thank you! -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 10:34:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20802 for freebsd-current-outgoing; Sun, 22 Feb 1998 10:34:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20797 for ; Sun, 22 Feb 1998 10:34:05 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id KAA27557; Sun, 22 Feb 1998 10:33:12 -0800 (PST) To: Poul-Henning Kamp cc: John Hay , freebsd-current@FreeBSD.ORG Subject: Re: clock code working properly in -current? In-reply-to: Your message of "Sun, 22 Feb 1998 18:55:35 +0100." <11816.888170135@critter.freebsd.dk> Date: Sun, 22 Feb 1998 10:33:12 -0800 Message-ID: <27554.888172392@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Please boot -v and send me the dmesg & sysctl -a outputs, then add > to the kernel config CLK_USE_I8254_CALIBRATION and CLK_USE_TSC_CALIBRATION > and send the dmesg & sysctl -a for those too. I've asked Dave (who you probably even remember from TFS - he was the Macintosh guy with long hair :) to do exactly this. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 10:39:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21465 for freebsd-current-outgoing; Sun, 22 Feb 1998 10:39:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21457 for ; Sun, 22 Feb 1998 10:39:00 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id TAA11949; Sun, 22 Feb 1998 19:34:07 +0100 (CET) To: "Jordan K. Hubbard" cc: John Hay , freebsd-current@FreeBSD.ORG Subject: Re: clock code working properly in -current? In-reply-to: Your message of "Sun, 22 Feb 1998 10:33:12 PST." <27554.888172392@time.cdrom.com> Date: Sun, 22 Feb 1998 19:34:06 +0100 Message-ID: <11947.888172446@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <27554.888172392@time.cdrom.com>, "Jordan K. Hubbard" writes: >> Please boot -v and send me the dmesg & sysctl -a outputs, then add >> to the kernel config CLK_USE_I8254_CALIBRATION and CLK_USE_TSC_CALIBRATION >> and send the dmesg & sysctl -a for those too. > >I've asked Dave (who you probably even remember from TFS - he was the >Macintosh guy with long hair :) to do exactly this. Cool, say Hi! to him from me :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 10:41:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22051 for freebsd-current-outgoing; Sun, 22 Feb 1998 10:41:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22044 for ; Sun, 22 Feb 1998 10:41:48 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id KAA27529; Sun, 22 Feb 1998 10:31:35 -0800 (PST) To: Nate Williams cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-reply-to: Your message of "Sun, 22 Feb 1998 10:52:52 MST." <199802221752.KAA24429@mt.sri.com> Date: Sun, 22 Feb 1998 10:31:35 -0800 Message-ID: <27525.888172295@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > FreeBSD's problem is that everyone has 'broken' the tree enough times > > > that no-one is willing to brandish the 'big stick' to whack people for > > > making bad commits. If you've got no negative feedback, then you've got > > > no reason to test changes. > > > > More to the point, it's far more damaging to alienate and potentially > > lose an existing volunteer than it is to have the tree occasionally > > broken, as much as I might whine about that from time to time. > > To a point, I agree. But, if that is indeed the case, then why isn't > Terry a committer? He may damage the tree, but we're definitely > alienating him. I was really careful to say *existing* volunteer above for exactly that reason. ;) And Terry isn't a committer for the simple reason that he's not *trusted* by anyone on our 17 member core team, a group which shook off its traditional apathy about such political issues to unanimously reject the proposal that he be added (which was also a first for us). I hate to single Terry out like this, but since you raised him as a specific issue... As to why we voted so unanimously on this, let's just say that Terry is a rather unique individual who can argue passionately and convincingly on either side of an argument, whether he's right or wrong. He's also wrong about 50% of the time, leading to an incredibly high overhead in trying to judge which side of the coin his current (multi-page, voluminously supported) argument falls on. This, in turn, leads to an unwillingness to trust the other 50% and hence resulted in the vote going the way it did. > We can't have it both ways. Either we have an *enforced* policy of > actually punishing offenders (which may offend them and cause them to > run away), or we don't have any policy at all and so claiming to have I'd rather not have a policy based on punishment. We're supposed to be doing this for fun and the joy of making a good OS, and hitting people with sticks is not conducive to that. I really wish Terry's specific predilection for pounding a pulpit didn't require such constant push-back since it definitely leads to the impression that we're going out of our way to hit HIM with a stick, but it's not always possible to avoid this given the extremely wide range of personalities (and personality disorders :-) we have to contend with in a project like this. > We got here by people who put out quality/tested software. This appears > to no longer be as important as it once was to many people, including > many people in core. I think you're reading rather too much into this. I'm willing to concede that there's a problem, but I don't see this as indicative of a general decline in core team quality. These things tend to be more cyclic than anything else and we'd appear to be on the down side of the cycle right now. Hope springs eternal that this will begin climbing upwards again as various folks become suitably chastened about breakage. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 10:43:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22479 for freebsd-current-outgoing; Sun, 22 Feb 1998 10:43:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hwcn.org (ac199@james.hwcn.org [199.212.94.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22470 for ; Sun, 22 Feb 1998 10:43:42 -0800 (PST) (envelope-from hoek@hwcn.org) Received: from localhost (ac199@localhost) by hwcn.org (8.8.8/8.8.8) with SMTP id NAA25258; Sun, 22 Feb 1998 13:29:59 -0500 (EST) Date: Sun, 22 Feb 1998 13:29:59 -0500 (EST) From: Tim Vanderhoek To: Nate Williams cc: "Jordan K. Hubbard" , Terry Lambert , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: <199802221752.KAA24429@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 22 Feb 1998, Nate Williams wrote: > To a point, I agree. But, if that is indeed the case, then why isn't > Terry a committer? He may damage the tree, but we're definitely > alienating him. Terry has publicly stated that he is impermeable to such unproductive emotions unreleated to actual research. As much as I am inclined to disbelieve all such silly statements, there is evidently some truth there. :) Besides, llama jokes aside, the esteemed Mr. Lambert knows what degree of respect many important (and not) people hold for him. He has been involved with FreeBSD since the Dark Ages before cvs. > We can't have it both ways. Either we have an *enforced* policy of > actually punishing offenders (which may offend them and cause them to They are volunteers. It's certainly not difficult to imagine the reaction "Okay, you don't want me to sacrifice many hours of my leisure and life; no problem; I won't". That's not a punishment! Quick! Point me to the most sensitive part of the source tree! Give me my life back! > avoided. However, many committers (myself included) know that in > reality there is no punishment for breaking the tree, so why bother > testing things more heavily when someone is going to end up doing that > work for me? For most, I imagine listening to Terry go off on another CVS global llama locking tangent is punishment enough!! Even worse, do you realize that we are getting dangerously close to being treated to an exposition elucidating the merits of weighted democracy and social engineering! Aieee!! Given the Netscape announcement, it would probably involve references to cathedrals, bazaars, and Linus Torvalds this time! > > We have to consider who we are and how we got here - this isn't > > We got here by people who put out quality/tested software. This appears > to no longer be as important as it once was to many people, including > many people in core. Speaking of Terry, his theory was that this -current instability issue comes up once every six months. I'm now expecting someone more diligint than I in tracking these things to pop-up and say that we're right on track. Addendum... These are volunteers and questioning their good will is counter-productive. The only recent idea having any merit, in my humble opinion, was having current.freebsd.org send out a message when the tree breaks. -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 11:52:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01221 for freebsd-current-outgoing; Sun, 22 Feb 1998 11:52:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01213 for ; Sun, 22 Feb 1998 11:52:19 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id OAA00804; Sun, 22 Feb 1998 14:41:45 -0500 (EST) (envelope-from toor) Message-Id: <199802221941.OAA00804@dyson.iquest.net> Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: <27525.888172295@time.cdrom.com> from "Jordan K. Hubbard" at "Feb 22, 98 10:31:35 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sun, 22 Feb 1998 14:41:45 -0500 (EST) Cc: nate@mt.sri.com, tlambert@primenet.com, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard said: > > As to why we voted so unanimously on this, let's just say that Terry > is a rather unique individual who can argue passionately and > convincingly on either side of an argument, whether he's right or > wrong. He's also wrong about 50% of the time, leading to an > incredibly high overhead in trying to judge which side of the coin his > current (multi-page, voluminously supported) argument falls on. This, > in turn, leads to an unwillingness to trust the other 50% and hence > resulted in the vote going the way it did. > BTW, I do *respect* Terry highly. I don't always agree with him, but he is a wonderful asset. Let's look at Terry like a researcher that we want to avoid having his experimental ideas in the tree. If his signal-to-noise ratio is slightly low, it doesn't mean that his contributions are faulty. I wish that we had a better support system for the likes of him, so that we can use his talents more effectively!!! -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 12:56:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09359 for freebsd-current-outgoing; Sun, 22 Feb 1998 12:56:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fang.cs.sunyit.edu (root@fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09351 for ; Sun, 22 Feb 1998 12:56:11 -0800 (PST) (envelope-from perlsta@cs.sunyit.edu) Received: from win95.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by fang.cs.sunyit.edu (8.8.5/8.7.3) with SMTP id QAA17877; Sun, 22 Feb 1998 16:56:57 GMT Message-ID: <008401bd3fd3$a1d3bee0$0600a8c0@win95.local.sunyit.edu> From: "Alfred Perlstein" To: "Nate Williams" , "Alexander Litvin" Cc: Subject: Re: New SoftUpdates test kit Date: Sun, 22 Feb 1998 15:51:20 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Yep, me to. During "make buildworld", system also a bit busy with >> day-to-day work like mail/news unbatching. >> >> panic: vm_fault: fault on nofault entry, addr: f2585000 >> >> syncing disks... wd0: interrupt timeout: >> wd0: status 58 error 0 > >Your disk is going bad. Replace it. this is not always true, this can also happen if the disk has spun down due to power managment... harderrors are usually signals of bad disks from my experiance. -alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 13:01:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10175 for freebsd-current-outgoing; Sun, 22 Feb 1998 13:01:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (dyna2-163.acadiau.ca [131.162.2.163]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10164 for ; Sun, 22 Feb 1998 13:01:40 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id RAA01094 for ; Sun, 22 Feb 1998 17:01:30 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 22 Feb 1998 17:01:30 -0400 (AST) From: The Hermit Hacker To: current@FreeBSD.ORG Subject: Joliet CDrom support... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I checked the archives, and was wondering if anyone has done anything with (or related to) the Linux patches available at: http://bmrc.berkeley.edu/people/chaffee/joliet.html Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 13:15:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13527 for freebsd-current-outgoing; Sun, 22 Feb 1998 13:15:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13496 for ; Sun, 22 Feb 1998 13:15:16 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA12855; Sun, 22 Feb 1998 14:02:44 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA24573; Sun, 22 Feb 1998 14:02:40 -0700 Date: Sun, 22 Feb 1998 14:02:40 -0700 Message-Id: <199802222102.OAA24573@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Alfred Perlstein" Cc: "Nate Williams" , "Alexander Litvin" , Subject: Re: New SoftUpdates test kit In-Reply-To: <008401bd3fd3$a1d3bee0$0600a8c0@win95.local.sunyit.edu> References: <008401bd3fd3$a1d3bee0$0600a8c0@win95.local.sunyit.edu> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> Yep, me to. During "make buildworld", system also a bit busy with > >> day-to-day work like mail/news unbatching. > >> > >> panic: vm_fault: fault on nofault entry, addr: f2585000 > >> > >> syncing disks... wd0: interrupt timeout: > >> wd0: status 58 error 0 > > > >Your disk is going bad. Replace it. > > this is not always true, this can also happen if the disk has spun down due > to power managment... True, that's why the message I deleted said 'probably a laptop'. But, I assume the user did not have a laptop since none was mentioned, and generally speaking you don't get that many errors in a row from spindowns (in my experience). > harderrors are usually signals of bad disks from my experiance. My laptop disk went dead with the above errors. :( Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 13:19:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14469 for freebsd-current-outgoing; Sun, 22 Feb 1998 13:19:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sphinx.lovett.com (root@sphinx.lovett.com [38.155.241.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA14462 for ; Sun, 22 Feb 1998 13:19:30 -0800 (PST) (envelope-from ade@demon.net) Received: from gorgon.lovett.com [38.155.241.3] (ade) by sphinx.lovett.com with esmtp (Exim 1.82 #1) id 0y6idb-0006as-00; Sun, 22 Feb 1998 15:08:39 -0600 To: Nate Williams cc: current@FreeBSD.ORG Subject: Re: New SoftUpdates test kit Organization: Demon Internet Reply-To: ade@demon.net In-reply-to: Your message of "Sun, 22 Feb 1998 11:04:56 MST." <199802221804.LAA24497@mt.sri.com> Date: Sun, 22 Feb 1998 15:08:38 -0600 From: Ade Lovett Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams writes: > >> syncing disks... wd0: interrupt timeout: >> wd0: status 58 error 0 > >Your disk is going bad. Replace it. Not necessarily true. One of my 3.0-current test boxes spits these errors out all over the place if I compile a kernel with the DMA option on the wdc* controllers (flags 0xa0ffa0ff), yet if I remove this option (flags 0x80ff80ff) it'll run fine for days under extreme disk load [various make world's, news server code testing, swap partitions almost maxed out, etc, etc..] ---------------------------------------------------------------------- cobra 1# uname -a FreeBSD cobra.lovett.com 3.0-CURRENT FreeBSD 3.0-CURRENT #14: Sat Feb 21 11:18:04 CST 1998 root@cobra.lovett.com:/usr/src/sys/compile/COBRA i386 cobra 2# dmesg ... ide_pci0: rev 0x06 on pci0.7.1 ... wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 3098MB (6346368 sectors), 6296 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): , 32-bit, multi-block-16 wd1: 3098MB (6346368 sectors), 6296 cyls, 16 heads, 63 S/T, 512 B/S ... ---------------------------------------------------------------------- -aDe -- Ade Lovett, Demon Internet, Austin, Texas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 13:20:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14888 for freebsd-current-outgoing; Sun, 22 Feb 1998 13:20:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arh0300.urh.uiuc.edu (arh0300.urh.uiuc.edu [130.126.72.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14825 for ; Sun, 22 Feb 1998 13:20:21 -0800 (PST) (envelope-from dannyman@arh0300.urh.uiuc.edu) Received: (from dannyman@localhost) by arh0300.urh.uiuc.edu (8.8.8/8.8.5) id PAA28045; Sun, 22 Feb 1998 15:20:19 -0600 (CST) Message-ID: <19980222152019.28089@urh.uiuc.edu> Date: Sun, 22 Feb 1998 15:20:19 -0600 From: dannyman Cc: current@FreeBSD.ORG Subject: Re: New SoftUpdates test kit References: <008401bd3fd3$a1d3bee0$0600a8c0@win95.local.sunyit.edu> <199802222102.OAA24573@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199802222102.OAA24573@mt.sri.com>; from Nate Williams on Sun, Feb 22, 1998 at 02:02:40PM -0700 X-Loop: djhoward@uiuc.edu X-URL: http://www.uiuc.edu/ph/www/djhoward/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 22, 1998 at 02:02:40PM -0700, Nate Williams wrote: > > >> syncing disks... wd0: interrupt timeout: > > >> wd0: status 58 error 0 > > > > > >Your disk is going bad. Replace it. > > > harderrors are usually signals of bad disks from my experiance. > > My laptop disk went dead with the above errors. :( How about just one such error that popped up once ever and you're a poor college student, and the disk itself has been employed < 1 year? :) I'm scared. Also, it's an IBM hard disk ... if it is going bad, you think they'll take it back just coz FreeBSD gave me a cryptic warning? thanks! -- //Dan -=- This message brought to you by djhoward@uiuc.edu -=- \\/yori -=- Information - http://www.uiuc.edu/ph/www/djhoward/ -=- aiokomete -=- Our Honored Symbol deserves an Honorable Retirement To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 13:23:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16012 for freebsd-current-outgoing; Sun, 22 Feb 1998 13:23:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15953 for ; Sun, 22 Feb 1998 13:23:19 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id HAA07281; Mon, 23 Feb 1998 07:52:29 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id HAA06805; Mon, 23 Feb 1998 07:52:29 +1030 (CST) (envelope-from grog) Message-ID: <19980223075229.12684@freebie.lemis.com> Date: Mon, 23 Feb 1998 07:52:29 +1030 From: Greg Lehey To: Nate Williams , Alfred Perlstein Cc: Alexander Litvin , current@FreeBSD.ORG Subject: Re: New SoftUpdates test kit References: <008401bd3fd3$a1d3bee0$0600a8c0@win95.local.sunyit.edu> <199802222102.OAA24573@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199802222102.OAA24573@mt.sri.com>; from Nate Williams on Sun, Feb 22, 1998 at 02:02:40PM -0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 22 February 1998 at 14:02:40 -0700, Nate Williams wrote: >>>> Yep, me to. During "make buildworld", system also a bit busy with >>>> day-to-day work like mail/news unbatching. >>>> >>>> panic: vm_fault: fault on nofault entry, addr: f2585000 >>>> >>>> syncing disks... wd0: interrupt timeout: >>>> wd0: status 58 error 0 >>> >>> Your disk is going bad. Replace it. >> >> this is not always true, this can also happen if the disk has spun down due >> to power managment... > > True, that's why the message I deleted said 'probably a laptop'. But, I > assume the user did not have a laptop since none was mentioned, and > generally speaking you don't get that many errors in a row from > spindowns (in my experience). I've had several incidences of this particular panic string. Julian's going to look at them when he has time. I don't get the associated interrupt timeouts, and I do get a dump. Here's a trace: #0 boot (howto=256) at ../../kern/kern_shutdown.c:296 #1 0xf011a1a7 in panic (fmt=0xf01bf960 "vm_fault: fault on nofault entry, addr: %lx") at ../../kern/kern_shutdown.c:436 #2 0xf01bfa94 in vm_fault (map=0xf0231ff8, vaddr=4088619008, fault_type=3 '\003', fault_flags=0) at ../../vm/vm_fault.c:225 #3 0xf01de208 in trap_pfault (frame=0xf6934ca8, usermode=0) at ../../i386/i386/trap.c:724 #4 0xf01dde87 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -206348288, tf_esi = -210388992, tf_ebp = -158118636, tf_isp = -158118704, tf_ebx = -218065492, tf_edx = 8192, tf_ecx = 512, tf_eax = 4040704, tf_trapno = 12, tf_err = 2, tf_eip = -266482982, tf_cs = 8, tf_eflags = 66070, tf_esp = -248082816, tf_ss = -249099424}) at ../../i386/i386/trap.c:363 #5 0xf01dcada in generic_bcopy () #6 0xf01afa3f in softdep_setup_allocindir_page (ip=0xf10ea000, lbn=1987, bp=0xf30095ac, ptrno=1975, newblkno=1681632, oldblkno=0, nbp=0xf3089e38) at ../../ufs/ffs/ffs_softdep.c:1408 #7 0xf01acfcd in ffs_balloc (ap=0xf6934ea4) at ../../ufs/ffs/ffs_balloc.c:302 #8 0xf01b657c in ffs_write (ap=0xf6934ef8) at vnode_if.h:995 #9 0xf0140fd7 in vn_write (fp=0xf123ccc0, uio=0xf6934f40, cred=0xf10e8500) at vnode_if.h:331 #10 0xf0121d8b in write (p=0xf68e2480, uap=0xf6934f94) at ../../kern/sys_generic.c:268 #11 0xf01dea6f in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 36928, tf_esi = 28672, tf_ebp = -272641928, tf_isp = -158117916, tf_ebx = 4116, tf_edx = 36928, tf_ecx = 4, tf_eax = 4, tf_trapno = 7, tf_err = 7, tf_eip = 537319009, tf_cs = 31, tf_eflags = 514, tf_esp = -272641968, tf_ss = 39}) at ../../i386/i386/trap.c:994 #12 0x2006d661 in ?? () #13 0x1099 in ?? () Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 13:39:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17590 for freebsd-current-outgoing; Sun, 22 Feb 1998 13:39:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17584 for ; Sun, 22 Feb 1998 13:39:19 -0800 (PST) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id IAA22450; Mon, 23 Feb 1998 08:38:56 +1100 (EST) Message-ID: <19980223083856.65231@rf900.physics.usyd.edu.au> Date: Mon, 23 Feb 1998 08:38:56 +1100 From: David Dawes To: dannyman Cc: current@FreeBSD.ORG Subject: Re: New SoftUpdates test kit References: <008401bd3fd3$a1d3bee0$0600a8c0@win95.local.sunyit.edu> <199802222102.OAA24573@mt.sri.com> <19980222152019.28089@urh.uiuc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <19980222152019.28089@urh.uiuc.edu>; from dannyman on Sun, Feb 22, 1998 at 03:20:19PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 22, 1998 at 03:20:19PM -0600, dannyman wrote: >On Sun, Feb 22, 1998 at 02:02:40PM -0700, Nate Williams wrote: > >> > >> syncing disks... wd0: interrupt timeout: >> > >> wd0: status 58 error 0 >> > > >> > >Your disk is going bad. Replace it. >> >> > harderrors are usually signals of bad disks from my experiance. >> >> My laptop disk went dead with the above errors. :( > >How about just one such error that popped up once ever and you're a poor >college student, and the disk itself has been employed < 1 year? :) > >I'm scared. > >Also, it's an IBM hard disk ... if it is going bad, you think they'll take it >back just coz FreeBSD gave me a cryptic warning? I've seen exactly the same message with an IBM disk (less than one year old, and not a laptop). It happens infrequently. It looks quite different from the messages I used to get from a drive that was going bad, but only time will tell for sure with this one. Looking through the logs, I found a few different ones, which might be more serious(?): wd2: interrupt timeout: wd2: status 58 error 1 wd2: interrupt timeout: wd2: status 58 error 60 David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 13:50:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20134 for freebsd-current-outgoing; Sun, 22 Feb 1998 13:50:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19286 for ; Sun, 22 Feb 1998 13:49:49 -0800 (PST) (envelope-from archer@grape.carrier.kiev.ua) Received: from unicorn.carrier.kiev.ua (unicorn.carrier.kiev.ua [193.193.193.113]) by burka.carrier.kiev.ua (8.8.8/8.Who.Cares) with ESMTP id XAA18592 for ; Sun, 22 Feb 1998 23:34:39 +0200 (EET) Received: from kozlik.carrier.kiev.ua (kozlik.carrier.kiev.ua [193.193.193.111]) by unicorn.carrier.kiev.ua (8.8.8/8.8.7) with ESMTP id XAA02140; Sun, 22 Feb 1998 23:34:38 +0200 (EET) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.8.8/8.8.8/8.Who.Cares) with UUCP id XAA13401; Sun, 22 Feb 1998 23:31:02 +0200 (EET) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.8.8/8.8.8) id XAA03356; Sun, 22 Feb 1998 23:29:23 +0200 (EET) (envelope-from archer) Message-ID: <19980222232920.29685@carrier.kiev.ua> Date: Sun, 22 Feb 1998 23:29:20 +0200 From: Alexander Litvin To: Alfred Perlstein Cc: Nate Williams , current@FreeBSD.ORG Subject: Re: New SoftUpdates test kit References: <008401bd3fd3$a1d3bee0$0600a8c0@win95.local.sunyit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <008401bd3fd3$a1d3bee0$0600a8c0@win95.local.sunyit.edu>; from Alfred Perlstein on Sun, Feb 22, 1998 at 03:51:20PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 22, 1998 at 03:51:20PM -0500, Alfred Perlstein wrote: > >> Yep, me to. During "make buildworld", system also a bit busy with > >> day-to-day work like mail/news unbatching. > >> > >> panic: vm_fault: fault on nofault entry, addr: f2585000 > >> > >> syncing disks... wd0: interrupt timeout: > >> wd0: status 58 error 0 > > > >Your disk is going bad. Replace it. > > this is not always true, this can also happen if the disk has spun down due > to power managment... > harderrors are usually signals of bad disks from my experiance. Don't quite sure, because it is a new disk. I would rather think it is my ancient VESA motherboard combined with even more ancient MIO that interferes with the disk. I'm going to replace MB first and see. Though, would you imply that the bad disk may cause that sort of panic? > -alfred --- You are only young once, but you can stay immature indefinitely. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 14:14:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25609 for freebsd-current-outgoing; Sun, 22 Feb 1998 14:14:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25604 for ; Sun, 22 Feb 1998 14:14:47 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id IAA07324; Mon, 23 Feb 1998 08:44:28 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id IAA26159; Mon, 23 Feb 1998 08:44:22 +1030 (CST) (envelope-from grog) Message-ID: <19980223084422.20994@freebie.lemis.com> Date: Mon, 23 Feb 1998 08:44:22 +1030 From: Greg Lehey To: "Jordan K. Hubbard" , Nate Williams Cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. References: <199802221752.KAA24429@mt.sri.com> <27525.888172295@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <27525.888172295@time.cdrom.com>; from Jordan K. Hubbard on Sun, Feb 22, 1998 at 10:31:35AM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 22 February 1998 at 10:31:35 -0800, Jordan K. Hubbard wrote: > Nate Williams wrote: >> We can't have it both ways. Either we have an *enforced* policy of >> actually punishing offenders (which may offend them and cause them to >> run away), or we don't have any policy at all and so claiming to have > > I'd rather not have a policy based on punishment. We're supposed to > be doing this for fun and the joy of making a good OS, and hitting > people with sticks is not conducive to that. Agreed. But a policy based on punishement isn't the same thing as a policy which includes punishment in exceptional circumstances. We've seen a lot of llamas, Terry-bashing and so on in this discussion, but we don't seem to be any closer to a clear policy on how to commit things. I made a suggestion about one possibility, expecting people to tear it apart. Instead, they turned and chased Terry, obviously a more satisfying activity. Back to the original subject, guys. I proposed the following Let's accept the fact that -CURRENT's stability fluctuates and try to influence the rhythm. One possiblity might be to say: - The first weekend in each month is the correct time for commiting big modifications that can potentially compromise stability for a while to come. - Any Sunday is the correct time for commiting smaller modifications that can potentially compromise stability for a few days. The advantage is that people can expect -CURRENT to be relatively stable on a Friday, and particularly stable at the end of a month. This is only a suggested implementation. I don't know how inconvenient it might be. Another alternative is the "heads up" approach--after a period of relative stability, somebody could say "I'm going to commit some changes to the frobulator which potentially impact stability. I'll do it tomorrow night unless I'm shouted down". None of this should replace basic testing, of course (build it and execute it, confirm it doesn't fall over immediately in every case). Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 14:45:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29289 for freebsd-current-outgoing; Sun, 22 Feb 1998 14:45:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29278 for ; Sun, 22 Feb 1998 14:44:56 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id XAA12514; Sun, 22 Feb 1998 23:26:32 +0100 (CET) To: Greg Lehey cc: "Jordan K. Hubbard" , Nate Williams , Terry Lambert , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-reply-to: Your message of "Mon, 23 Feb 1998 08:44:22 +1030." <19980223084422.20994@freebie.lemis.com> Date: Sun, 22 Feb 1998 23:26:32 +0100 Message-ID: <12512.888186392@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980223084422.20994@freebie.lemis.com>, Greg Lehey writes: >I made a suggestion about one possibility, >expecting people to tear it apart. Instead, they turned and chased >Terry, obviously a more satisfying activity. Not really... >Back to the original subject, guys. I proposed the following > > [...] I don't think it will fly, I think trying to synchronize the factors which control the time our hackers have to devote to FreeBSD would be a major mistake... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 15:02:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02092 for freebsd-current-outgoing; Sun, 22 Feb 1998 15:02:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02086 for ; Sun, 22 Feb 1998 15:02:47 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id QAA13821; Sun, 22 Feb 1998 16:02:31 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id QAA25689; Sun, 22 Feb 1998 16:02:28 -0700 Date: Sun, 22 Feb 1998 16:02:28 -0700 Message-Id: <199802222302.QAA25689@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: Nate Williams , Terry Lambert , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: <27525.888172295@time.cdrom.com> References: <199802221752.KAA24429@mt.sri.com> <27525.888172295@time.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We can't have it both ways. Either we have an *enforced* policy of > > actually punishing offenders (which may offend them and cause them to > > run away), or we don't have any policy at all and so claiming to have > > I'd rather not have a policy based on punishment. Punishment? Is it worse to 'punish' our users and developers by requiring them them to deal with broken trees all the time. IMHO, doling out the occasion 'trivial' punishment of removing someones commit privs for a time is much less punishment. > We're supposed to be doing this for fun and the joy of making a good > OS, and hitting people with sticks is not conducive to that. It's supposed to be fun, but dealing with brokeness and answering lots of questions about broken build trees is *NOT* alot of fun. > > We got here by people who put out quality/tested software. This appears > > to no longer be as important as it once was to many people, including > > many people in core. > > I think you're reading rather too much into this. I'm willing to > concede that there's a problem, but I don't see this as indicative of > a general decline in core team quality. That's not my point. My point is that the folks who are held up as 'shining examples' of dedication to the project aren't even willing to test their own code. How can we expect the users to expect things to work when core cannot even police itself. > These things tend to be more cyclic than anything else and we'd appear > to be on the down side of the cycle right now. Hope springs eternal > that this will begin climbing upwards again as various folks become > suitably chastened about breakage. I will hope with you as well, but experience has shown that things have *NOT* gotten better, but instead worse w/regards to the frequency and severity of brokeness in the tree. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 15:07:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02792 for freebsd-current-outgoing; Sun, 22 Feb 1998 15:07:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02761 for ; Sun, 22 Feb 1998 15:07:32 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id QAA13851; Sun, 22 Feb 1998 16:07:20 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id QAA25719; Sun, 22 Feb 1998 16:07:18 -0700 Date: Sun, 22 Feb 1998 16:07:18 -0700 Message-Id: <199802222307.QAA25719@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Greg Lehey Cc: "Jordan K. Hubbard" , Nate Williams , Terry Lambert , current@FreeBSD.ORG Subject: Commit schedule (was Re: Terry, llamas, More breakage in -current...) In-Reply-To: <19980223084422.20994@freebie.lemis.com> References: <199802221752.KAA24429@mt.sri.com> <27525.888172295@time.cdrom.com> <19980223084422.20994@freebie.lemis.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Back to the original subject, guys. I proposed the following > > Let's accept the fact that -CURRENT's stability fluctuates and try > to influence the rhythm. One possiblity might be to say: > > - The first weekend in each month is the correct time for commiting > big modifications that can potentially compromise stability for a > while to come. What if the developer doesn't have time that weekend to commit code? What if that committer happens to have a project due that week, but two weeks after that they have time to hack on a solution, and answer questions on it? What then? > - Any Sunday is the correct time for commiting smaller modifications > that can potentially compromise stability for a few days. Why Sunday? I tend to be on business during the week, so Friday night/Saturday morning is the best time for me, since I can answer questions and fix bugs over the weekend. > The advantage is that people can expect -CURRENT to be relatively > stable on a Friday, and particularly stable at the end of a month. IMHO, this won't work simply because you can't dictate the schedule of a volunteer. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 16:13:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08905 for freebsd-current-outgoing; Sun, 22 Feb 1998 16:13:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08896 for ; Sun, 22 Feb 1998 16:13:18 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id RAA12403; Sun, 22 Feb 1998 17:50:31 -0500 (EST) Date: Sun, 22 Feb 1998 17:50:31 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: Greg Lehey cc: "Jordan K. Hubbard" , Nate Williams , Terry Lambert , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: <19980223084422.20994@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Feb 1998, Greg Lehey wrote: > On Sun, 22 February 1998 at 10:31:35 -0800, Jordan K. Hubbard wrote: > > Nate Williams wrote: > >> We can't have it both ways. Either we have an *enforced* policy of > >> actually punishing offenders (which may offend them and cause them to > >> run away), or we don't have any policy at all and so claiming to have > > > > I'd rather not have a policy based on punishment. We're supposed to > > be doing this for fun and the joy of making a good OS, and hitting > > people with sticks is not conducive to that. > > Agreed. But a policy based on punishement isn't the same thing as a > policy which includes punishment in exceptional circumstances. I think Jordan and Greg both have points they are correct about. What about making a web page that the offender gets put on ... nothing incredibly horrible, just a rogues gallery (I broke current on 00/00/00 with a commit to " ... ". You figure that the list is pretty quickly going to get some names on it, so it won't be so embarrassing as to turn people off, but most people wouldn't want to show up on it, so they'd avoid doing things to get themselves so honored. Folks like John Dyson would show up a lot ... most of us know why that'd be, and I _wouldn't_ want to unduly embarrass John ... but if John could take it as sort of a left-handed compliment, it'd probably be a real deterrent to most of the rest of us. Think of it as minimal punishment. If it turns out to be too negative, a little editing of the web page could either soften (or harden) the impact, as needed. I don't want to be as drastic as I think Greg is proposing, but I think ignoring it isn't probably the best way to go either. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 16:28:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10732 for freebsd-current-outgoing; Sun, 22 Feb 1998 16:28:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10674 for ; Sun, 22 Feb 1998 16:27:56 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id KAA07438; Mon, 23 Feb 1998 10:46:06 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id KAA13105; Mon, 23 Feb 1998 10:46:06 +1030 (CST) (envelope-from grog) Message-ID: <19980223104605.49121@freebie.lemis.com> Date: Mon, 23 Feb 1998 10:46:05 +1030 From: Greg Lehey To: Chuck Robey Cc: "Jordan K. Hubbard" , Nate Williams , Terry Lambert , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. References: <19980223084422.20994@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Chuck Robey on Sun, Feb 22, 1998 at 05:50:31PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 22 February 1998 at 17:50:31 -0500, Chuck Robey wrote: > On Mon, 23 Feb 1998, Greg Lehey wrote: > >> On Sun, 22 February 1998 at 10:31:35 -0800, Jordan K. Hubbard wrote: >>> Nate Williams wrote: >>>> We can't have it both ways. Either we have an *enforced* policy of >>>> actually punishing offenders (which may offend them and cause them to >>>> run away), or we don't have any policy at all and so claiming to have >>> >>> I'd rather not have a policy based on punishment. We're supposed to >>> be doing this for fun and the joy of making a good OS, and hitting >>> people with sticks is not conducive to that. >> >> Agreed. But a policy based on punishement isn't the same thing as a >> policy which includes punishment in exceptional circumstances. > > I think Jordan and Greg both have points they are correct about. What > about making a web page that the offender gets put on ... nothing > incredibly horrible, just a rogues gallery (I broke current on 00/00/00 > with a commit to " ... ". You figure that the list is pretty quickly > going to get some names on it, so it won't be so embarrassing as to turn > people off, but most people wouldn't want to show up on it, so they'd > avoid doing things to get themselves so honored. > > Folks like John Dyson would show up a lot ... most of us know why that'd > be, and I _wouldn't_ want to unduly embarrass John ... but if John could > take it as sort of a left-handed compliment, it'd probably be a real > deterrent to most of the rest of us. Think of it as minimal punishment. > If it turns out to be too negative, a little editing of the web page could > either soften (or harden) the impact, as needed. Hmmm. I think this is a little drastic. I certainly wouldn't recommend anything unless the person in question is a repeat offender. And in John's case, as I said before, I don't think he has offended. There's a difference between committing a file that won't build and committing a change that causes the VM system to die in certain very specific circumstances. > I don't want to be as drastic as I think Greg is proposing, but I think > ignoring it isn't probably the best way to go either. Wait, what are you talking about? I didn't propose *any* particular punishment in my suggestion. I'm just trying to find a way to keep -CURRENT usable at least some of the time by channeling the commits. I know my suggestion isn't perfect, and the objections people have to it are valid. I just wish that somebody would come up with something better. Nate (I think) brought up the fact that people can't always commit when it would be suitable for my model. Would anybody care to think about a two-phase commit model: commit to the bleeding edge whenever you want, commit things that roughly work within a week? Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 16:43:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12726 for freebsd-current-outgoing; Sun, 22 Feb 1998 16:43:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sphinx.lovett.com (root@sphinx.lovett.com [38.155.241.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA12721 for ; Sun, 22 Feb 1998 16:43:22 -0800 (PST) (envelope-from ade@demon.net) Received: from gorgon.lovett.com [38.155.241.3] (ade) by sphinx.lovett.com with esmtp (Exim 1.82 #1) id 0y6lzB-0006nh-00; Sun, 22 Feb 1998 18:43:09 -0600 To: Greg Lehey cc: current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. Organization: Demon Internet Reply-To: ade@demon.net In-reply-to: Your message of "Mon, 23 Feb 1998 10:46:05 +1030." <19980223104605.49121@freebie.lemis.com> Date: Sun, 22 Feb 1998 18:43:08 -0600 From: Ade Lovett Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey writes: > >Nate (I think) brought up the fact that people can't always commit >when it would be suitable for my model. Would anybody care to think >about a two-phase commit model: commit to the bleeding edge whenever >you want, commit things that roughly work within a week? Surely that would require a new codeset though, ie: -bleeding -current -stable with all the extra levels of complexity that that incurs. FWIW, I think a good first step would be to have the failures (or otherwise) of Jordan's daily -current build machine made available to the community at large.. it'd certainly be useful in determining whether, for example, my -current build failures are down to the -current tree being broken, or whether local patches and/or other cruft is interfering in some way. Rather than mailing it out to hackers, committers, or wherever, how about adding the daily output of "make world" on the build box somewhere under the CVS tree, so those that are interested can cvsup a new category (say "builds"), and those that aren't don't end up with unwanted stuff in their mailboxes. -aDe -- Ade Lovett, Demon Internet, Austin, Texas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 16:51:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14162 for freebsd-current-outgoing; Sun, 22 Feb 1998 16:51:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA14157 for ; Sun, 22 Feb 1998 16:51:22 -0800 (PST) (envelope-from handy@sag.space.lockheed.com) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA14142; Sun, 22 Feb 1998 16:41:47 -0800 Date: Sun, 22 Feb 1998 16:41:47 -0800 (PST) From: Brian Handy To: Chuck Robey Cc: Greg Lehey , "Jordan K. Hubbard" , Nate Williams , Terry Lambert , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Chuck writes:] >I think Jordan and Greg both have points they are correct about. What >about making a web page that the offender gets put on ... nothing >incredibly horrible, just a rogues gallery (I broke current on 00/00/00 >with a commit to " ... ". [Followed up with John Dyson as an example] People are confusing some issues here, and Terry pointed this out to me. Chuck is wrong, because John in fact does *not* often break the tree. His stuff makes it unstable and crash, but that's not the problem here. The problem here is people committing stuff that won't even *compile*. Hello? Everyone on the same thread yet? The problem here is getting the tree to just *compile*. We'll worry about it actually *working* later! You can't jump to an unstable -current until you can compile it! Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 16:58:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15278 for freebsd-current-outgoing; Sun, 22 Feb 1998 16:58:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15251 for ; Sun, 22 Feb 1998 16:58:44 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id TAA12655; Sun, 22 Feb 1998 19:44:33 -0500 (EST) Date: Sun, 22 Feb 1998 19:44:33 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: Greg Lehey cc: "Jordan K. Hubbard" , Nate Williams , Terry Lambert , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: <19980223104605.49121@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Feb 1998, Greg Lehey wrote: > > I think Jordan and Greg both have points they are correct about. What > > about making a web page that the offender gets put on ... nothing > > incredibly horrible, just a rogues gallery (I broke current on 00/00/00 > > with a commit to " ... ". You figure that the list is pretty quickly > > going to get some names on it, so it won't be so embarrassing as to turn > > people off, but most people wouldn't want to show up on it, so they'd > > avoid doing things to get themselves so honored. > > > > Folks like John Dyson would show up a lot ... most of us know why that'd > > be, and I _wouldn't_ want to unduly embarrass John ... but if John could > > take it as sort of a left-handed compliment, it'd probably be a real > > deterrent to most of the rest of us. Think of it as minimal punishment. > > If it turns out to be too negative, a little editing of the web page could > > either soften (or harden) the impact, as needed. > > Hmmm. I think this is a little drastic. I certainly wouldn't > recommend anything unless the person in question is a repeat offender. > And in John's case, as I said before, I don't think he has offended. > There's a difference between committing a file that won't build and > committing a change that causes the VM system to die in certain very > specific circumstances. The reason why I wouldn't want the bar raised for getting on the list is because it would hurt much less if there were 20 other names there to begin with. No particular badge of honor, so folks would avoid it, but neither would one single person look like a complete idiot. I used to care about making mistakes and getting blamed for it, until a New Yorker (I was in LA at the time) started a publicly posted "awshit" list, and added names liberally. Pretty soon, I got over the onus of blame (for which I'm endlessly grateful) but I still made the attempt not to get on the list. Make it hurt less, but make it public (more public and permanent than mailing list flames). I think I'd get on that list, I've broken too many ports. > > > I don't want to be as drastic as I think Greg is proposing, but I think > > ignoring it isn't probably the best way to go either. > > Wait, what are you talking about? OK, maybe it wasn't perfect in reference. 1 awshit. I didn't propose *any* particular > punishment in my suggestion. I'm just trying to find a way to keep > -CURRENT usable at least some of the time by channeling the commits. > I know my suggestion isn't perfect, and the objections people have to > it are valid. I just wish that somebody would come up with something > better. > > Nate (I think) brought up the fact that people can't always commit > when it would be suitable for my model. Would anybody care to think > about a two-phase commit model: commit to the bleeding edge whenever > you want, commit things that roughly work within a week? > > Greg > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 17:07:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16404 for freebsd-current-outgoing; Sun, 22 Feb 1998 17:07:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (surf52.cruzers.com [205.215.232.52]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA16399 for ; Sun, 22 Feb 1998 17:07:24 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 364 invoked by uid 100); 23 Feb 1998 01:08:40 -0000 Message-ID: <19980222170834.A326@top.worldcontrol.com> Date: Sun, 22 Feb 1998 17:08:34 -0800 To: freebsd-current@FreeBSD.ORG Subject: softupdates6+soffice4 ?= freeze&reboot Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On my laptop, P5-200 w/48MB, runing FreeBSD top.worldcontrol.com 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Sun Feb 22 15:36:41 PST 1998 brian@bls2.worldcontrol.com:/uss/src/sys/compile/LAPTOP i386 with softupdates6 enabled on /usr has frozen and then reset twice while I had soffice4 sitting idle in another window. On the other hand, is has not frozen&reset while either: I have had softupdates6 disabled or I have not had soffice4 sitting in another window. This is not a panic, but a freeze and reset. I could be related to soffice4 and simply coincident with softupdates6 being enabled or disabled. -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 17:11:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17339 for freebsd-current-outgoing; Sun, 22 Feb 1998 17:11:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17333 for ; Sun, 22 Feb 1998 17:11:43 -0800 (PST) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA03253; Mon, 23 Feb 1998 11:41:34 +1030 (CST) Message-Id: <199802230111.LAA03253@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: The Hermit Hacker cc: current@FreeBSD.ORG Subject: Re: Joliet CDrom support... In-reply-to: Your message of "Sun, 22 Feb 1998 17:01:30 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Feb 1998 11:41:34 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I checked the archives, and was wondering if anyone has done anything with > (or related to) the Linux patches available at: > > http://bmrc.berkeley.edu/people/chaffee/joliet.html Well I had a look at these but they have lots of extra gunk about different code pages which I didn't really understand, so I gave up :) I tried o find 'the standard' but the MS web page on it is hopeless, and another page which supposedly has the standard is no longer up :-( I think someone with more knowledge of FS's and/or Linux would be a good candidate for this =) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 17:40:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20959 for freebsd-current-outgoing; Sun, 22 Feb 1998 17:40:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20944 for ; Sun, 22 Feb 1998 17:40:25 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA04050; Sun, 22 Feb 1998 18:40:15 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd003980; Sun Feb 22 18:40:09 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id SAA16400; Sun, 22 Feb 1998 18:40:03 -0700 (MST) From: Terry Lambert Message-Id: <199802230140.SAA16400@usr08.primenet.com> Subject: Re: More breakage in -current as a result of header frobbing. To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Mon, 23 Feb 1998 01:40:03 +0000 (GMT) Cc: grog@lemis.com, jkh@time.cdrom.com, nate@mt.sri.com, tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <12512.888186392@critter.freebsd.dk> from "Poul-Henning Kamp" at Feb 22, 98 11:26:32 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Back to the original subject, guys. I proposed the following > > > > [...] > > I don't think it will fly, I think trying to synchronize the factors > which control the time our hackers have to devote to FreeBSD would > be a major mistake... I agree. The unfortunate effect of following the suggestion, even if the time window control weren't a factor, would be to trigger all commits in a relatively short window. This is exactly the type of situation which will result in Bob and Fred committing conflicting changes that result in an unbuildable tree. Without some software-enforced procedural mechanism for avoiding this type of collision, hashing commits over "all available time" is as good a method as any. At least you get statistical protection, if nothing else. If you get a hash collision (ie: Bob and Fred's commits overlap), well, then you're potentially screwed, and if so, then it's going to require actual work to get the tree buildable. Not that this happening with an artificially bloated frequency wouldn't make my cvs locking proposal look a lot more desirable... ;-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 17:49:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22017 for freebsd-current-outgoing; Sun, 22 Feb 1998 17:49:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22008 for ; Sun, 22 Feb 1998 17:49:43 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id RAA29561; Sun, 22 Feb 1998 17:37:55 -0800 (PST) To: Chuck Robey cc: Greg Lehey , Nate Williams , Terry Lambert , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-reply-to: Your message of "Sun, 22 Feb 1998 17:50:31 EST." Date: Sun, 22 Feb 1998 17:37:54 -0800 Message-ID: <29557.888197874@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think Jordan and Greg both have points they are correct about. What > about making a web page that the offender gets put on ... nothing Gosh, why stop there? Why don't we just put the developer in the stocks and place them on display in the town square? :-) I've not yet heard a proposed cure that wasn't worse than the disease and would suggest that we all just Try A Little Harder rather than instituting unworkable policies to a problem that simply requires a bit more SELF CONTROL on the part of the developers to fix. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 17:53:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22867 for freebsd-current-outgoing; Sun, 22 Feb 1998 17:53:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22856 for ; Sun, 22 Feb 1998 17:53:20 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA06818; Sun, 22 Feb 1998 18:53:19 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd006795; Sun Feb 22 18:53:14 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id SAA17096; Sun, 22 Feb 1998 18:53:12 -0700 (MST) From: Terry Lambert Message-Id: <199802230153.SAA17096@usr08.primenet.com> Subject: Re: More breakage in -current as a result of header frobbing. To: nate@mt.sri.com (Nate Williams) Date: Mon, 23 Feb 1998 01:53:12 +0000 (GMT) Cc: tlambert@primenet.com, nate@mt.sri.com, current@FreeBSD.ORG In-Reply-To: <199802221440.HAA24031@mt.sri.com> from "Nate Williams" at Feb 22, 98 07:40:22 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > FreeBSD's problem is that everyone has 'broken' the tree enough times > that no-one is willing to brandish the 'big stick' to whack people for > making bad commits. If you've got no negative feedback, then you've got > no reason to test changes. I think that "the big stick" approach is fundamentally flawed; that's why I think the software should be doing the procedural enforcement, so that "the big stick" is unnecessary. You have my suggested method of enforcing a procedure that results in a buildable tree. Personally, I'm not hell-bent on reader/writer locks; I just know that they are one method which would tend to work, especially if the lock release required a build-step before it would release (no, not a "build world", unless the dependencies can be fixed). Feel free to suggest other alternatives for software enforcement of buildability; like I said above, I'm not necessarily wedded to the lock idea -- it's *a* soloution, not *the only* soloution. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 18:14:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27445 for freebsd-current-outgoing; Sun, 22 Feb 1998 18:14:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27412 for ; Sun, 22 Feb 1998 18:14:08 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id TAA24377; Sun, 22 Feb 1998 19:14:07 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd024332; Sun Feb 22 19:14:01 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id TAA18100; Sun, 22 Feb 1998 19:13:56 -0700 (MST) From: Terry Lambert Message-Id: <199802230213.TAA18100@usr08.primenet.com> Subject: Re: More breakage in -current as a result of header frobbing. To: hoek@hwcn.org (Tim Vanderhoek) Date: Mon, 23 Feb 1998 02:13:56 +0000 (GMT) Cc: nate@mt.sri.com, jkh@time.cdrom.com, tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: from "Tim Vanderhoek" at Feb 22, 98 01:29:59 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > avoided. However, many committers (myself included) know that in > > reality there is no punishment for breaking the tree, so why bother > > testing things more heavily when someone is going to end up doing that > > work for me? > > For most, I imagine listening to Terry go off on another CVS > global llama locking tangent is punishment enough!! Heh. "I are a component of yur quality control feedback loop". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 18:17:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28735 for freebsd-current-outgoing; Sun, 22 Feb 1998 18:17:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28702 for ; Sun, 22 Feb 1998 18:17:38 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id TAA02211; Sun, 22 Feb 1998 19:11:56 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpd002189; Sun Feb 22 19:11:52 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id TAA18013; Sun, 22 Feb 1998 19:11:50 -0700 (MST) From: Terry Lambert Message-Id: <199802230211.TAA18013@usr08.primenet.com> Subject: Re: More breakage in -current as a result of header frobbing. To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 23 Feb 1998 02:11:49 +0000 (GMT) Cc: nate@mt.sri.com, tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <27525.888172295@time.cdrom.com> from "Jordan K. Hubbard" at Feb 22, 98 10:31:35 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > More to the point, it's far more damaging to alienate and potentially > > > lose an existing volunteer than it is to have the tree occasionally > > > broken, as much as I might whine about that from time to time. > > > > To a point, I agree. But, if that is indeed the case, then why isn't > > Terry a committer? He may damage the tree, but we're definitely > > alienating him. > > I was really careful to say *existing* volunteer above for exactly > that reason. ;) > > And Terry isn't a committer for the simple reason that he's not > *trusted* by anyone on our 17 member core team, a group which shook > off its traditional apathy about such political issues to unanimously > reject the proposal that he be added (which was also a first for us). > I hate to single Terry out like this, but since you raised him as a > specific issue... Much as I love playing the human beach-ball... ;-) I have not *asked* for commit priviledges since they were first offered to me in 1994 and I turned them down on the basis of my being a USL employee at the time, and therefore a potential legal liability to the project. The core team members can vote, or not vote, or whatever, and they can be unanimous, or have unanimity with abstentions, or they can vote me in as God's Western Regional Marketing Manager. It really doesn't matter to why I'm involved, and choose to remain involved, one way or the other. But asking for code to be committed, and asking for commit priviledges are two different things. I *have* asked for code to be committed, and I certainly understand that a volunteer organization is probably not capable of the scientific rigor you would hope to find in a business or an academic research project. That's why I've been willing to scale back code changes to the point where it doesn't take a lot of rigor for them to be understood (see http://freebsd.org/~terry/). And I'm willing to continue scaling for however long it takes to get under a sufficient "I can't take the time to understand this because I'm a volunteer" threshold. > I really wish Terry's > specific predilection for pounding a pulpit didn't require such > constant push-back since it definitely leads to the impression that > we're going out of our way to hit HIM with a stick, but it's not > always possible to avoid this given the extremely wide range of > personalities (and personality disorders :-) we have to contend with > in a project like this. Hey, I'm a scientist. Passion about science is wherein lies its art. I wouldn't like me if I didn't argue passionately for rigor over expediency, correctness over fuzz, revolution over evolution, and foul-tasting medicine where foul-tasting medicine is called for. You probably wouldn't like me, either. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 18:18:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29016 for freebsd-current-outgoing; Sun, 22 Feb 1998 18:18:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28975 for ; Sun, 22 Feb 1998 18:18:28 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id TAA00256; Sun, 22 Feb 1998 19:34:23 -0500 (EST) (envelope-from toor) Message-Id: <199802230034.TAA00256@dyson.iquest.net> Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: from Chuck Robey at "Feb 22, 98 05:50:31 pm" To: chuckr@glue.umd.edu (Chuck Robey) Date: Sun, 22 Feb 1998 19:34:22 -0500 (EST) Cc: grog@lemis.com, jkh@time.cdrom.com, nate@mt.sri.com, tlambert@primenet.com, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey said: > > Folks like John Dyson would show up a lot ... most of us know why that'd > be, and I _wouldn't_ want to unduly embarrass John ... > Go ahead, embarass me :-). As if I don't embarass myself enough :-). -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 18:23:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29936 for freebsd-current-outgoing; Sun, 22 Feb 1998 18:23:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29931 for ; Sun, 22 Feb 1998 18:23:14 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id NAA07869; Mon, 23 Feb 1998 13:23:06 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199802230223.NAA07869@cimlogic.com.au> Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: <29557.888197874@time.cdrom.com> from "Jordan K. Hubbard" at "Feb 22, 98 05:37:54 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 23 Feb 1998 13:23:06 +1100 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > I've not yet heard a proposed cure that wasn't worse than the disease > and would suggest that we all just Try A Little Harder rather than > instituting unworkable policies to a problem that simply requires a > bit more SELF CONTROL on the part of the developers to fix. I'm inclined to think that this thread is all getting a little out-of-hand. I know there were a few things that triggered this discussion, but the one that caused the subject of this message existed for less than 11 hours. This discussion serves to remind everyone of how annoyed people get when others break the tree. Only if there are repeated, blatant breakages is any further action required other than a message to the committer saying "I wish you hadn't done that!". I don't see any repeated breakages, so I'd just like people to agree that "sh*t happens", and deal with it. I'd ask committers to make themselves available and respond to email at least the day after they commit something. -- John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 19:29:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06295 for freebsd-current-outgoing; Sun, 22 Feb 1998 19:29:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from taliesin.cs.ucla.edu (Taliesin.CS.UCLA.EDU [131.179.96.166]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA06276 for ; Sun, 22 Feb 1998 19:29:19 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Received: (qmail 1338 invoked from network); 23 Feb 1998 03:29:11 -0000 Received: from mordred.cs.ucla.edu (131.179.48.34) by taliesin.cs.ucla.edu with SMTP; 23 Feb 1998 03:29:11 -0000 Received: (from scottm@localhost) by mordred.cs.ucla.edu (8.8.8/8.8.8) id TAA00473; Sun, 22 Feb 1998 19:29:11 -0800 (PST) (envelope-from scottm) Date: Sun, 22 Feb 1998 19:29:11 -0800 (PST) From: Scott Michel Message-Id: <199802230329.TAA00473@mordred.cs.ucla.edu> To: freebsd-multimedia@FreeBSD.ORG Subject: kernel scheduler issues Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has there been/Is there any discussion about changing the kernel scheduler to support audio (generally multimedia) needs, where you'd like to temporarily increase a process's priority close to the end of a audio block playout to decrease the jumps/gaps? I know, I haven't done any coding for the kernel and I probably should sound like I'm bitching about this, but I'm just a little curious. -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 19:43:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08358 for freebsd-current-outgoing; Sun, 22 Feb 1998 19:43:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08353; Sun, 22 Feb 1998 19:43:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id TAA09645; Sun, 22 Feb 1998 19:41:58 -0800 (PST) Message-Id: <199802230341.TAA09645@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Scott Michel cc: freebsd-multimedia@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: kernel scheduler issues In-reply-to: Your message of "Sun, 22 Feb 1998 19:29:11 PST." <199802230329.TAA00473@mordred.cs.ucla.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Feb 1998 19:41:57 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Has there been/Is there any discussion about changing the kernel > scheduler to support audio (generally multimedia) needs, where > you'd like to temporarily increase a process's priority close to > the end of a audio block playout to decrease the jumps/gaps? > > I know, I haven't done any coding for the kernel and I probably > should sound like I'm bitching about this, but I'm just a little > curious. You probably *should* sound like you're bitching? 8) A carefully-crafted audio system will probably try to use the features documented in rtprio(2) in order to guarantee CPU availability for time-critical activities. In the crudest case, if your issue is a simple audio player application, you can use rtprio(1) to execute the entire application at realtime priority. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 19:47:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09072 for freebsd-current-outgoing; Sun, 22 Feb 1998 19:47:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09061 for ; Sun, 22 Feb 1998 19:46:49 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id UAA15571; Sun, 22 Feb 1998 20:39:43 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id UAA26400; Sun, 22 Feb 1998 20:37:11 -0700 Date: Sun, 22 Feb 1998 20:37:11 -0700 Message-Id: <199802230337.UAA26400@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: Nate Williams , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: <29557.888197874@time.cdrom.com> References: <29557.888197874@time.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've not yet heard a proposed cure that wasn't worse than the disease > and would suggest that we all just Try A Little Harder rather than > instituting unworkable policies to a problem that simply requires a > bit more SELF CONTROL on the part of the developers to fix. What happens when the developers aren't showing any self control, like now? Then we have the problems we have now. :( Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 19:54:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10660 for freebsd-current-outgoing; Sun, 22 Feb 1998 19:54:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10629 for ; Sun, 22 Feb 1998 19:54:40 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id TAA28186; Sun, 22 Feb 1998 19:54:02 -0800 (PST) To: Terry Lambert cc: nate@mt.sri.com, current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-reply-to: Your message of "Mon, 23 Feb 1998 02:11:49 GMT." <199802230211.TAA18013@usr08.primenet.com> Date: Sun, 22 Feb 1998 19:54:02 -0800 Message-ID: <28177.888206042@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have not *asked* for commit priviledges since they were first > offered to me in 1994 and I turned them down on the basis of my Sorry if I implied that you'd ever requested them - I believe we were reacting at the time to a proposal from some 3rd party that you be given commit privileges. Call it a vote to consider the idea rather than a vote to implement it. :) > I wouldn't like me if I didn't argue passionately for rigor over > expediency, correctness over fuzz, revolution over evolution, and > foul-tasting medicine where foul-tasting medicine is called for. And I don't think that anyone begrudges you that. The bigger area of concern, and the one I was specifically referring to, is your occasional predilection for recommending leeches as a cure for anemia. ;-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 19:54:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10789 for freebsd-current-outgoing; Sun, 22 Feb 1998 19:54:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10284 for ; Sun, 22 Feb 1998 19:52:35 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id UAA15670; Sun, 22 Feb 1998 20:48:05 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id UAA26504; Sun, 22 Feb 1998 20:47:57 -0700 Date: Sun, 22 Feb 1998 20:47:57 -0700 Message-Id: <199802230347.UAA26504@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Brian Handy Cc: "Jordan K. Hubbard" , Nate Williams , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: References: X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I think Jordan and Greg both have points they are correct about. What > >about making a web page that the offender gets put on ... nothing > >incredibly horrible, just a rogues gallery (I broke current on 00/00/00 > >with a commit to " ... ". [Followed up with John Dyson as an example] > > People are confusing some issues here, and Terry pointed this out to me. > Chuck is wrong, because John in fact does *not* often break the tree. His > stuff makes it unstable and crash, but that's not the problem here. Exactly! I'm not complaining about 'buggy/complex' software, but about stupid silly bugs. Things not building, include files not working in a 'build world', stuff that compiles but could never even run, etc... Basicaly, simply Q&A stuff is what I'm complaining about, not highly complex fixes to bugs that don't show up in simply Q&A testing. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 20:09:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13025 for freebsd-current-outgoing; Sun, 22 Feb 1998 20:09:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13019 for ; Sun, 22 Feb 1998 20:09:40 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id OAA07649; Mon, 23 Feb 1998 14:28:37 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id OAA08258; Mon, 23 Feb 1998 14:28:37 +1030 (CST) (envelope-from grog) Message-ID: <19980223142836.41784@freebie.lemis.com> Date: Mon, 23 Feb 1998 14:28:36 +1030 From: Greg Lehey To: Terry Lambert , Tim Vanderhoek Cc: nate@mt.sri.com, jkh@time.cdrom.com, current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. References: <199802230213.TAA18100@usr08.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199802230213.TAA18100@usr08.primenet.com>; from Terry Lambert on Mon, Feb 23, 1998 at 02:13:56AM +0000 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 February 1998 at 2:13:56 +0000, Terry Lambert wrote: >>> avoided. However, many committers (myself included) know that in >>> reality there is no punishment for breaking the tree, so why bother >>> testing things more heavily when someone is going to end up doing that >>> work for me? >> >> For most, I imagine listening to Terry go off on another CVS >> global llama locking tangent is punishment enough!! > > > Heh. "I are a component of yur quality control feedback loop". Would you be willing to bombard any future commit sinner with mail messages describing the errors of their ways? :-) Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 20:27:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA14685 for freebsd-current-outgoing; Sun, 22 Feb 1998 20:27:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ppp1707.on.bellglobal.com (ppp1707.on.bellglobal.com [206.172.249.171]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA14678 for ; Sun, 22 Feb 1998 20:27:41 -0800 (PST) (envelope-from ac199@hwcn.org) Received: from localhost (tim@localhost) by localhost.my.domain (8.8.8/8.8.8) with SMTP id XAA00576; Sun, 22 Feb 1998 23:23:53 -0500 (EST) (envelope-from ac199@hwcn.org) X-Authentication-Warning: localhost.my.domain: tim owned process doing -bs Date: Sun, 22 Feb 1998 23:23:53 -0500 (EST) From: Tim Vanderhoek X-Sender: tim@localhost Reply-To: ac199@hwcn.org To: Nate Williams cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: <199802230337.UAA26400@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 22 Feb 1998, Nate Williams wrote: > What happens when the developers aren't showing any self control, like > now? Then we have the problems we have now. :( Well, go ahead and start and pointy-hat page. Ask for volunteer submissions to get it started. Maybe even a story going with some of the better ones. The truth behind the origin of easy-import! :) Some of the greater blunders really deserve to be preserved in perpetuity. Man, I shudder to think of the embarrasment had I imported my home directory... Some of those binary files are really incriminating... ;-) $FreeBSD$ [Hmm... CVS-related blunders are usually the best, but that's no reason not to include more boring bland typos and such that break -current] -- tIM...HOEk OPTIMIZATION: the process of using many one-letter variables names hoping that the resultant code will run faster. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 20:55:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA17469 for freebsd-current-outgoing; Sun, 22 Feb 1998 20:55:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from taliesin.cs.ucla.edu (Taliesin.CS.UCLA.EDU [131.179.96.166]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA17436 for ; Sun, 22 Feb 1998 20:55:24 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Received: (qmail 1407 invoked from network); 23 Feb 1998 04:55:21 -0000 Received: from mordred.cs.ucla.edu (131.179.48.34) by taliesin.cs.ucla.edu with SMTP; 23 Feb 1998 04:55:21 -0000 Received: from mordred.cs.ucla.edu (localhost [127.0.0.1]) by mordred.cs.ucla.edu (8.8.8/8.8.8) with ESMTP id UAA00730; Sun, 22 Feb 1998 20:55:17 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Message-Id: <199802230455.UAA00730@mordred.cs.ucla.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: Mike Smith cc: Scott Michel , freebsd-multimedia@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: kernel scheduler issues In-reply-to: Your message of "Sun, 22 Feb 1998 19:41:57 PST." <199802230341.TAA09645@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Feb 1998 20:55:16 -0800 From: Scott Michel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You probably *should* sound like you're bitching? 8) Oops. That's about a size-12 foot extraction. :-) -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 21:32:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20625 for freebsd-current-outgoing; Sun, 22 Feb 1998 21:32:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20615 for ; Sun, 22 Feb 1998 21:32:21 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id AAA13371; Mon, 23 Feb 1998 00:18:55 -0500 (EST) Date: Mon, 23 Feb 1998 00:18:55 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: Nate Williams cc: Brian Handy , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: <199802230347.UAA26504@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 22 Feb 1998, Nate Williams wrote: > > >I think Jordan and Greg both have points they are correct about. What > > >about making a web page that the offender gets put on ... nothing > > >incredibly horrible, just a rogues gallery (I broke current on 00/00/00 > > >with a commit to " ... ". [Followed up with John Dyson as an example] > > > > People are confusing some issues here, and Terry pointed this out to me. > > Chuck is wrong, because John in fact does *not* often break the tree. His > > stuff makes it unstable and crash, but that's not the problem here. > I wasn't trying to complain about John, quite the opposite, I _really_ appreciate his work, and since it's so terribly touchy, I gladly accept any possible excuse for his mistakes (which are often better than the things I do correctly). I am more trying to catch the guy who carelessly sticks mistakes in the tree. and my suggestion was to position such folks for some *mild* chiding. I think that anything more would be too drastic for a volunteer effort, but a little humorous gibe (gee, who's on the top of the awshit list today?) wouldn't do any real harm. John replied himself (surprising me not at all) saying he wouldn't mind, wouldn't take such as too much ... he understood the direction I wanted to go with it, I think. I am going to drop it, tho, if Jordan's that strong against it, I'm not crusading here. > Exactly! I'm not complaining about 'buggy/complex' software, but about > stupid silly bugs. Things not building, include files not working in a > 'build world', stuff that compiles but could never even run, etc... > > Basicaly, simply Q&A stuff is what I'm complaining about, not highly > complex fixes to bugs that don't show up in simply Q&A testing. > > > Nate > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 21:39:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21618 for freebsd-current-outgoing; Sun, 22 Feb 1998 21:39:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21613 for ; Sun, 22 Feb 1998 21:39:35 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id WAA16329; Sun, 22 Feb 1998 22:38:28 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id WAA26811; Sun, 22 Feb 1998 22:37:53 -0700 Date: Sun, 22 Feb 1998 22:37:53 -0700 Message-Id: <199802230537.WAA26811@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: ac199@hwcn.org Cc: Nate Williams , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: References: <199802230337.UAA26400@mt.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tim Vanderhoek writes: > On Sun, 22 Feb 1998, Nate Williams wrote: > > > What happens when the developers aren't showing any self control, like > > now? Then we have the problems we have now. :( > > Well, go ahead and start and pointy-hat page. Public humiliation *never* does anything well. Big sticks should be waved in private instead of public, as any management book written will tell you. (Public humiliation are large parts of why we had WWII...) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 22:18:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25468 for freebsd-current-outgoing; Sun, 22 Feb 1998 22:18:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA25463 for ; Sun, 22 Feb 1998 22:18:11 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0y6rDG-0003wQ-00; Sun, 22 Feb 1998 23:18:02 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id XAA01148; Sun, 22 Feb 1998 23:17:47 -0700 (MST) Message-Id: <199802230617.XAA01148@harmony.village.org> To: "Jordan K. Hubbard" Subject: Re: More breakage in -current as a result of header frobbing. Cc: Nate Williams , Terry Lambert , current@FreeBSD.ORG In-reply-to: Your message of "Sun, 22 Feb 1998 09:24:29 PST." <27201.888168269@time.cdrom.com> References: <27201.888168269@time.cdrom.com> Date: Sun, 22 Feb 1998 23:17:47 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <27201.888168269@time.cdrom.com> "Jordan K. Hubbard" writes: : More to the point, it's far more damaging to alienate and potentially : lose an existing volunteer than it is to have the tree occasionally : broken, as much as I might whine about that from time to time. We : have to consider who we are and how we got here - this isn't : commercial software development, as much as we might sometimes try to : emulate it. :-) I hate to jump into the llama spitting that has been going on... personally, i don't have a problem with what has been going on. Ever since the make buildworld target came online, I don't care if tree is broken in -current from time to time. if people bust it and don't fix it in a timely better, then that is a problem. I've not seen that in -current at all. sure people are human and are in need of a pointy hat from time to time. if there is a person who has violated these tennants, i'd expect core to deal with it appropriately. this, after he or she has a long history of needing others to cleam up after them or not respecting the will of core. None of which is currently going on as best as I can tell (I'm not in core). I agree with jordan. I don't think there is a problem here. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 22:27:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26936 for freebsd-current-outgoing; Sun, 22 Feb 1998 22:27:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA26931 for ; Sun, 22 Feb 1998 22:27:19 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0y6rM7-0003wi-00; Sun, 22 Feb 1998 23:27:11 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id XAA01194; Sun, 22 Feb 1998 23:26:55 -0700 (MST) Message-Id: <199802230626.XAA01194@harmony.village.org> To: Nate Williams Subject: Re: More breakage in -current as a result of header frobbing. Cc: "Jordan K. Hubbard" , Terry Lambert , current@FreeBSD.ORG In-reply-to: Your message of "Sun, 22 Feb 1998 10:52:52 MST." <199802221752.KAA24429@mt.sri.com> References: <199802221752.KAA24429@mt.sri.com> <199802221440.HAA24031@mt.sri.com> <27201.888168269@time.cdrom.com> Date: Sun, 22 Feb 1998 23:26:55 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199802221752.KAA24429@mt.sri.com> Nate Williams writes: : We got here by people who put out quality/tested software. This appears : to no longer be as important as it once was to many people, including : many people in core. I find quality very important. I haven't seen the quality of -current be any worse than the -current of other BSDs that i build and use. I too am worried when people make changes they haven't tested. However, -current will be broken from time to time because of the nature of the beast. if there are those that break it too often, they should be hassled. I'm just not seeing one person who has done that. Just different people who have accidentally messed up all at the same time. what am i missing? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 22:37:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28199 for freebsd-current-outgoing; Sun, 22 Feb 1998 22:37:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA28189 for ; Sun, 22 Feb 1998 22:37:30 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0y6rVy-0003x2-00; Sun, 22 Feb 1998 23:37:22 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id XAA01242; Sun, 22 Feb 1998 23:37:07 -0700 (MST) Message-Id: <199802230637.XAA01242@harmony.village.org> To: Nate Williams Subject: Re: More breakage in -current as a result of header frobbing. Cc: ac199@hwcn.org, "Jordan K. Hubbard" , current@FreeBSD.ORG In-reply-to: Your message of "Sun, 22 Feb 1998 22:37:53 MST." <199802230537.WAA26811@mt.sri.com> References: <199802230537.WAA26811@mt.sri.com> <199802230337.UAA26400@mt.sri.com> Date: Sun, 22 Feb 1998 23:37:07 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199802230537.WAA26811@mt.sri.com> Nate Williams writes: : Public humiliation *never* does anything well. Big sticks should be : waved in private instead of public, as any management book written will : tell you. So what kind of big stick is needed, in your opinion? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 22:52:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA00308 for freebsd-current-outgoing; Sun, 22 Feb 1998 22:52:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tigger.chameleon.com (root@ts29-12.vcr.istar.ca [204.191.153.235]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA00285 for ; Sun, 22 Feb 1998 22:52:33 -0800 (PST) (envelope-from teisler@istar.ca) Received: from tigger.chameleon.com (teisler@localhost.chameleon.com [127.0.0.1]) by tigger.chameleon.com (8.8.5/8.8.5) with SMTP id XAA01152 for ; Sun, 22 Feb 1998 23:03:57 -0800 (PST) Message-ID: <34F11F5D.41C67EA6@istar.ca> Date: Sun, 22 Feb 1998 23:03:57 -0800 From: Troi Eisler Organization: Chameleon Consulting Inc. X-Mailer: Mozilla 3.0Gold (X11; U; BSD/OS 3.1 i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: unsubscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 23:43:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04159 for freebsd-current-outgoing; Sun, 22 Feb 1998 23:43:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04153 for ; Sun, 22 Feb 1998 23:43:22 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id HAA13745; Mon, 23 Feb 1998 07:43:20 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id IAA09441; Mon, 23 Feb 1998 08:43:19 +0100 (MET) Message-ID: <19980223084318.50933@follo.net> Date: Mon, 23 Feb 1998 08:43:19 +0100 From: Eivind Eklund To: Terry Lambert Cc: current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. References: <12512.888186392@critter.freebsd.dk> <199802230140.SAA16400@usr08.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199802230140.SAA16400@usr08.primenet.com>; from Terry Lambert on Mon, Feb 23, 1998 at 01:40:03AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 23, 1998 at 01:40:03AM +0000, Terry Lambert wrote: > > >Back to the original subject, guys. I proposed the following > > > > > > [...] > > > > I don't think it will fly, I think trying to synchronize the factors > > which control the time our hackers have to devote to FreeBSD would > > be a major mistake... > > I agree. The unfortunate effect of following the suggestion, even > if the time window control weren't a factor, would be to trigger > all commits in a relatively short window. > > This is exactly the type of situation which will result in Bob and > Fred committing conflicting changes that result in an unbuildable > tree. > > Without some software-enforced procedural mechanism for avoiding > this type of collision, I'd like a system where I could 'pend a commit' and have it run through a build-test and then be committed if it passed (and no one else had touched the files I've been working on in the meantime). Due to the way I work and what hardware I've got available it has been very difficult for me to do a full buildtest for each change; that has for the most part changed now (thanks Simon!), but it still would be more convenient to have a special-commit-and-it-will-built-for-you system. It couldn't be the only system (as it sometimes is necessary to have things available immediately), but it would be a valueable addition. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 23:46:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05048 for freebsd-current-outgoing; Sun, 22 Feb 1998 23:46:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA05015 for ; Sun, 22 Feb 1998 23:46:55 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id HAA13791; Mon, 23 Feb 1998 07:46:52 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id IAA09470; Mon, 23 Feb 1998 08:46:52 +0100 (MET) Message-ID: <19980223084652.46151@follo.net> Date: Mon, 23 Feb 1998 08:46:52 +0100 From: Eivind Eklund To: ade@demon.net, Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. References: <19980223104605.49121@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Ade Lovett on Sun, Feb 22, 1998 at 06:43:08PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 22, 1998 at 06:43:08PM -0600, Ade Lovett wrote: > Rather than mailing it out to hackers, committers, or wherever, > how about adding the daily output of "make world" on the build > box somewhere under the CVS tree, so those that are interested > can cvsup a new category (say "builds"), and those that aren't > don't end up with unwanted stuff in their mailboxes. I'm not certain I don't want it to the mailing list, but I think storing it in CVS would a very good idea, no matter what else is done. This will let us find differences from daily build to daily build, which could potentially be of help in tracking down strange changes. It never hurts to have more data available, at least. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 22 23:50:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06003 for freebsd-current-outgoing; Sun, 22 Feb 1998 23:50:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA05997 for ; Sun, 22 Feb 1998 23:50:35 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.4) with UUCP id HAA00761; Mon, 23 Feb 1998 07:49:23 GMT Received: from [194.32.164.2] by seagoon.gid.co.uk; Mon, 23 Feb 1998 07:48:44 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199802230537.WAA26811@mt.sri.com> References: <199802230337.UAA26400@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 23 Feb 1998 07:50:52 +0000 To: Nate Williams From: Bob Bishop Subject: Re: More breakage in -current as a result of header frobbing. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 5:37 am +0000 23/2/98, Nate Williams wrote: >(Public humiliation are large parts of why we had WWII...) No, WWII was a result of committing (to) something that didn't work: "I have on this piece of paper...". (Where's my tin hat?) -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 02:12:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA20333 for freebsd-current-outgoing; Mon, 23 Feb 1998 02:12:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20320 for ; Mon, 23 Feb 1998 02:12:15 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id DAA28396; Mon, 23 Feb 1998 03:12:13 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd028375; Mon Feb 23 03:12:06 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id DAA29929; Mon, 23 Feb 1998 03:12:03 -0700 (MST) From: Terry Lambert Message-Id: <199802231012.DAA29929@usr02.primenet.com> Subject: Re: More breakage in -current as a result of header frobbing. To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 23 Feb 1998 10:12:03 +0000 (GMT) Cc: tlambert@primenet.com, nate@mt.sri.com, current@FreeBSD.ORG In-Reply-To: <28177.888206042@time.cdrom.com> from "Jordan K. Hubbard" at Feb 22, 98 07:54:02 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I wouldn't like me if I didn't argue passionately for rigor over > > expediency, correctness over fuzz, revolution over evolution, and > > foul-tasting medicine where foul-tasting medicine is called for. > > And I don't think that anyone begrudges you that. The bigger area of > concern, and the one I was specifically referring to, is your > occasional predilection for recommending leeches as a cure for > anemia. ;-) Actually, "leeches and anemia" are a bad example. It seems that leeches work in this case ("New England Journal of Medicine", March 1989, or thereabouts, I believe... though I could be mistaken, and it might have been "Lancet"). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 04:00:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA28746 for freebsd-current-outgoing; Mon, 23 Feb 1998 04:00:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA28741 for ; Mon, 23 Feb 1998 04:00:32 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id FAA18637; Mon, 23 Feb 1998 05:00:26 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id EAA28445; Mon, 23 Feb 1998 04:56:15 -0700 Date: Mon, 23 Feb 1998 04:56:15 -0700 Message-Id: <199802231156.EAA28445@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: Nate Williams , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: <199802230637.XAA01242@harmony.village.org> References: <199802230537.WAA26811@mt.sri.com> <199802230337.UAA26400@mt.sri.com> <199802230637.XAA01242@harmony.village.org> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : Public humiliation *never* does anything well. Big sticks should be > : waved in private instead of public, as any management book written will > : tell you. > > So what kind of big stick is needed, in your opinion? Actual (temporary) removal of commit privs, and if the offender doesn't change their behavior after a couple of removals, nuke them. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 07:50:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22763 for freebsd-current-outgoing; Mon, 23 Feb 1998 07:50:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22757 for ; Mon, 23 Feb 1998 07:50:18 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.4) with UUCP id PAA06379 for freebsd.org!current; Mon, 23 Feb 1998 15:49:04 GMT Received: from [194.32.164.2] by seagoon.gid.co.uk; Mon, 23 Feb 1998 15:35:46 GMT X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 23 Feb 1998 15:37:52 +0000 To: current@FreeBSD.ORG From: Bob Bishop Subject: Build still broken Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is as of CTM src-cur 3261: cc -nostdinc -O2 -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mno-486 -DBOOTWAIT=5000 -DTIMEOUT= -DBOOTSEG=0x1000 -DBOOTSTACK=0xFFF0 -DDO_BAD144 -DVES A_SUPPORT -nostdinc -I/source/cleansrc/sys/i386/boot/biosboot/../../../../includ e -I/source/cleansrc/sys/i386/boot/biosboot/../../.. -I/usr/obj/source/cleansrc/ sys/i386/boot/biosboot -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wn ested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -I/usr/obj/source/cleansrc /tmp/usr/include -c /source/cleansrc/sys/i386/boot/biosboot/table.c In file included from /source/cleansrc/sys/i386/boot/biosboot/boot.h:35, from /source/cleansrc/sys/i386/boot/biosboot/table.c:53: /source/cleansrc/sys/i386/boot/biosboot/../../../../include/ufs/ufs/inode.h:62: field `i_lock' has incomplete type *** Error code 1 Stop. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 08:42:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28795 for freebsd-current-outgoing; Mon, 23 Feb 1998 08:42:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.hughes.net (mail.hughes.net [205.139.35.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28780 for ; Mon, 23 Feb 1998 08:42:27 -0800 (PST) (envelope-from skylord@hughes.net) Received: from hughes.net (shelby.hughes.net [205.139.43.214]) by mail.hughes.net (post.office MTA v2.0 0813 ID# 0-13727) with ESMTP id AAA14284 for ; Mon, 23 Feb 1998 08:14:27 -0800 Message-ID: <34F1A09F.F12FDC5F@hughes.net> Date: Mon, 23 Feb 1998 16:15:27 +0000 From: Skylord X-Mailer: Mozilla 4.04 [en] (X11; I; Linux 2.0.32 i586) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: IRC-Hybrid Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having a heck of a time getting IRC-Hybrid to run. It configures, makes and installs ok, but just won't run. I strongly suspect it has something to do with theses settings in config.h: #define HARD_FDLIMIT_ and #define INIT_MAXCLIENTS The problem is, I'm really not sure what to set these at and the documentation is vague on how to go about deciding what to set them at. Also, should I modify the setting CFLAGS= -g -02 -D"FD_SETSIZE=1024" in the makefile? When I run it, all I get is: Value of FD_SETSIZE is 1024 Value of NOFILE is 64 And that's it...but it never starts. Any help at this point is greatly appreciated. I've poured over the docs many times but just can't seem to find the answer. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 11:57:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29181 for freebsd-current-outgoing; Mon, 23 Feb 1998 11:57:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com ([209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29176; Mon, 23 Feb 1998 11:57:12 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id LAA01711; Mon, 23 Feb 1998 11:56:53 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802231956.LAA01711@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Mike Smith cc: Scott Michel , freebsd-multimedia@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, Jim Lowe Subject: Re: kernel scheduler issues In-reply-to: Your message of "Sun, 22 Feb 1998 19:41:57 PST." <199802230341.TAA09645@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Feb 1998 11:56:53 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I would start by ensuring that the clock is well synchronized . man ntpq and ntpq . Jim Lowe , wrote a program , xmixer , which based upon a stable clock source such as ntp attempted to equalize an audio stream when faced with an innacurate audio clock source. Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 13:44:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19079 for freebsd-current-outgoing; Mon, 23 Feb 1998 13:44:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (dyna2-156.acadiau.ca [131.162.2.156]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18706 for ; Mon, 23 Feb 1998 13:41:22 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id RAA01389 for ; Mon, 23 Feb 1998 17:40:25 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 23 Feb 1998 17:40:25 -0400 (AST) From: The Hermit Hacker To: freebsd-current@FreeBSD.ORG Subject: ATAPI related patch .. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi... I recently grabbed a patch that Luigi (freebsd-multimedia) has that is required in order to read audio tracks (using something like tosha) from a CD...with minor modifications, I've got it in my -current kernel and haven't noticed any problems. I would like to commit the patch to the -current source tree, so am asking here if there are any objections to doing this. If I hear nothing by Wednesday (long enough?), I'll assume that it is okay and commit it... Patch included below... Thanks... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org *** isa/wcd.c Mon Feb 9 02:08:43 1998 --- isa.n/wcd.c Sun Feb 22 23:33:18 1998 *************** *** 346,351 **** --- 346,352 ---- struct atapires result; struct changer *chp; int i; + int loops = 0; if (wcdnlun >= NUNIT) { printf ("wcd: too many units\n"); *************** *** 369,385 **** } /* Get drive capabilities. */ result = atapi_request_immediate (ata, unit, ATAPI_MODE_SENSE, 0, CAP_PAGE, 0, 0, 0, 0, sizeof (cdp->cap) >> 8, sizeof (cdp->cap), 0, 0, 0, 0, 0, 0, 0, (char*) &cdp->cap, sizeof (cdp->cap)); ! /* Do it twice to avoid the stale media changed state. */ ! if (result.code == RES_ERR && ! (result.error & AER_SKEY) == AER_SK_UNIT_ATTENTION) ! result = atapi_request_immediate (ata, unit, ATAPI_MODE_SENSE, ! 0, CAP_PAGE, 0, 0, 0, 0, sizeof (cdp->cap) >> 8, ! sizeof (cdp->cap), 0, 0, 0, 0, 0, 0, 0, ! (char*) &cdp->cap, sizeof (cdp->cap)); /* Some drives have shorter capabilities page. */ if (result.code == RES_UNDERRUN) --- 370,384 ---- } /* Get drive capabilities. */ + for (loops = 0 ; loops < 10 ; loops++) { + /* some drives are slow to respond at boot time... */ result = atapi_request_immediate (ata, unit, ATAPI_MODE_SENSE, 0, CAP_PAGE, 0, 0, 0, 0, sizeof (cdp->cap) >> 8, sizeof (cdp->cap), 0, 0, 0, 0, 0, 0, 0, (char*) &cdp->cap, sizeof (cdp->cap)); ! if (result.code == 0 || result.code == RES_UNDERRUN) ! break; ! } /* Some drives have shorter capabilities page. */ if (result.code == RES_UNDERRUN) *************** *** 511,516 **** --- 510,544 ---- if (t->cap.prevent) printf (", lock protected"); printf ("\n"); + + printf ("wcd%d: ", t->lun); + if (t->cap.composite) + printf(" comp. A/V,"); + if (t->cap.dport1 || t->cap.dport2) + printf(" dig.audio %s%s,", + t->cap.dport1 ? "1 ":"", t->cap.dport2 ? "2":""); + if (t->cap.mode2_form1 || t->cap.mode2_form2) + printf(" mode 2 form %s%s,", + t->cap.mode2_form1 ? "1(XA) ":"", + t->cap.mode2_form2 ? "2":""); + if (t->cap.multisession) + printf(" multisession,"); + if (t->cap.cd_da || t->cap.cd_da_stream) + printf(" CD-DA %s%s,", + t->cap.cd_da ? "read ":"", + t->cap.cd_da_stream ? "stream":""); + if (t->cap.rw) + printf(" combined rw,"); + if (t->cap.rw_corr) + printf(" rw correct.,"); + if (t->cap.c2) + printf(" C2,"); + if (t->cap.isrc) + printf(" ISRC,"); + if (t->cap.upc) + printf(" UPC"); + printf("\n"); + } static int *************** *** 738,743 **** --- 766,827 ---- *f = lba % 75; } + #if 1 + #define CDIOCATAPIREQ _IOWR('c',100,struct atapireq) + + struct atapireq { + u_char cmd[16]; + caddr_t databuf; + int datalen; + struct atapires result; + }; + + static void arstrategy(struct buf *); + static void ar_done(struct wcd *, struct buf *, int, struct atapires); + + static void + arstrategy(struct buf *bp) + { + struct wcd *t = bp->b_driver1; + struct atapireq *ar = bp->b_driver2; + + if (t == NULL || ar == NULL) { + bp->b_error = EINVAL; + bp->b_flags |= B_ERROR; + biodone(bp); + return; + } + + /* Can't ever write to a CD. */ + if (!(bp->b_flags & B_READ)) { + bp->b_error = EROFS; + bp->b_flags |= B_ERROR; + biodone(bp); + return; + } + + atapi_request_callback(t->ata, t->unit, + ar->cmd[0], ar->cmd[1], ar->cmd[2], ar->cmd[3], + ar->cmd[4], ar->cmd[5], ar->cmd[6], ar->cmd[7], + ar->cmd[8], ar->cmd[9], ar->cmd[10], ar->cmd[11], + ar->cmd[12], ar->cmd[13], ar->cmd[14], ar->cmd[15], + (u_char*) bp->b_data, bp->b_bcount, ar_done, t, bp); + } + + static void + ar_done(struct wcd *t, struct buf *bp, int resid, struct atapires result) + { + struct atapireq *ar = bp->b_driver2; + + if (result.code) + wcd_error(t, result); + bp->b_resid = 0; + ar->datalen -= resid; + ar->result = result; + biodone(bp); + } + #endif + /* * Perform special action on behalf of the user. * Knows about the internals of this device *************** *** 834,839 **** --- 918,973 ---- return (EIO); bcopy (&t->toc.hdr, addr, sizeof t->toc.hdr); break; + + #ifdef CDIOCATAPIREQ + case CDIOCATAPIREQ: { + struct atapireq *ar, *oar = (struct atapireq *)addr; + struct buf *bp; + + MALLOC(ar, struct atapireq *, sizeof *ar, M_TEMP, M_WAITOK); + MALLOC(bp, struct buf *, sizeof *bp, M_TEMP, M_WAITOK); + + bcopy(oar, ar, sizeof *ar); + bzero(bp, sizeof *bp); + + bp->b_proc = p; + bp->b_dev = dev; + bp->b_driver1 = t; + bp->b_driver2 = ar; + + if (ar->datalen) { + struct uio auio; + struct iovec aiov; + + if (ar->datalen < 0) + return (EINVAL); + + aiov.iov_base = ar->databuf; + aiov.iov_len = ar->datalen; + auio.uio_iov = &aiov; + auio.uio_iovcnt = 1; + + auio.uio_offset = 0; + auio.uio_resid = ar->datalen; + + auio.uio_rw = UIO_READ; /* CD is readonly */ + auio.uio_segflg = UIO_USERSPACE; + auio.uio_procp = p; + + bp->b_bcount = ar->datalen; + error = physio(arstrategy, bp, dev, 1, minphys, &auio); + } else { + bp->b_flags = B_READ | B_BUSY; + arstrategy(bp); + error = bp->b_error; + } + + bcopy(ar, oar, sizeof *ar); + FREE(ar, M_TEMP); + FREE(bp, M_TEMP); + break; + } + #endif case CDIOREADTOCENTRYS: { struct ioc_read_toc_entry *te = *** isa/atapi.c Mon Feb 9 02:08:24 1998 --- isa.n/atapi.c Sun Feb 22 22:44:16 1998 *************** *** 214,220 **** /* DRQ type */ switch (ap->drqtype) { ! case AT_DRQT_MPROC: ata->slow = 1; break; case AT_DRQT_INTR: printf (", intr"); ata->intrcmd = 1; break; case AT_DRQT_ACCEL: printf (", accel"); break; default: printf (", drq%d", ap->drqtype); --- 214,220 ---- /* DRQ type */ switch (ap->drqtype) { ! case AT_DRQT_MPROC: printf (", slow"); ata->slow = 1; break; case AT_DRQT_INTR: printf (", intr"); ata->intrcmd = 1; break; case AT_DRQT_ACCEL: printf (", accel"); break; default: printf (", drq%d", ap->drqtype); *************** *** 338,343 **** --- 338,344 ---- case 0x4b: return ("PAUSE"); case 0x48: return ("PLAY_TRACK"); case 0xa5: return ("PLAY_BIG"); + case 0xbe: return ("READ_CD"); /* XXX */ } sprintf (buf, "[0x%x]", cmd); return (buf); *************** *** 778,796 **** --- 779,841 ---- print (("atapi%d.%d: recv data overrun, %d bytes left\n", ata->ctrlr, ac->unit, ac->count)); ac->result.code = RES_OVERRUN; + if(ac->count != 0) insw (ata->port + AR_DATA, ac->addr, ac->count / sizeof(short)); for (i=ac->count; iport + AR_DATA); + len = ac->count; } else insw (ata->port + AR_DATA, ac->addr, len / sizeof(short)); ac->addr += len; ac->count -= len; + #if 1 + /* + * some drives appear not to assert BSY after a + * CDDA transfer, and then do not generate the intrq + * to complete the transfer. Among these: + * Sony CDU331, Goldstar GCD580 + * Obviate by testing BSY and going on anyways. + */ + for (i = 0 ; i < 2 ; i++) { + int j = inb (ata->port + AR_STATUS); + if ( (j & (ARS_DRQ | ARS_BSY)) == ARS_BSY ) + break; + } + if (i == 2 ) { + if (atapi_wait (ata->port, 0) < 0) { + ac->result.status = inb (ata->port + AR_STATUS); + ac->result.error = inb (ata->port + AR_ERROR); + ac->result.code = RES_NOTRDY; + printf ("atapi%d.%d: controller not ready, status=%b, error= %b\n", + ata->ctrlr, ac->unit, ac->result.status, ARS_BITS, + ac->result.error, AER_BITS); + return (0); + } + + ac->result.status = inb (ata->port + AR_STATUS); + ac->result.error = inb (ata->port + AR_ERROR); + len = inb (ata->port + AR_CNTLO); + len |= inb (ata->port + AR_CNTHI) << 8; + ireason = inb (ata->port + AR_IREASON); + + goto complete; + /* + * unfortunately, my Sony CDU-55E does assert BSY + * but then forgets to generate the intrq at times... + * Maybe I should check that len is a multiple of + * the CDDA size (2352) and return anyways if + * count == 0 ? + */ + } + #endif + return (1); case PHASE_ABORTED: case PHASE_COMPLETED: + complete: if (ac->result.status & (ARS_CHECK | ARS_DF)) ac->result.code = RES_ERR; else if (ac->count < 0) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 14:05:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22828 for freebsd-current-outgoing; Mon, 23 Feb 1998 14:05:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22811 for ; Mon, 23 Feb 1998 14:05:02 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA12585; Mon, 23 Feb 1998 14:03:41 -0800 (PST) Message-Id: <199802232203.OAA12585@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: The Hermit Hacker cc: freebsd-current@FreeBSD.ORG Subject: Re: ATAPI related patch .. In-reply-to: Your message of "Mon, 23 Feb 1998 17:40:25 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Feb 1998 14:03:40 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I recently grabbed a patch that Luigi (freebsd-multimedia) has > that is required in order to read audio tracks (using something like > tosha) from a CD...with minor modifications, I've got it in my -current > kernel and haven't noticed any problems. Thanks for the review! > I would like to commit the patch to the -current source tree, so > am asking here if there are any objections to doing this. If I hear > nothing by Wednesday (long enough?), I'll assume that it is okay and > commit it... Erk. This is thoroughly grostic. You shouldn't be doing I/O using an ioctl; this behaviour should belong on a new minor number and the raw device read handler. I would vote against the inclusion of this code, unless there is an overwhelming precedent for the technique. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 14:34:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28480 for freebsd-current-outgoing; Mon, 23 Feb 1998 14:34:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ppp6460.on.bellglobal.com (ppp7265.on.bellglobal.com [206.172.249.233]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28472 for ; Mon, 23 Feb 1998 14:34:27 -0800 (PST) (envelope-from ac199@hwcn.org) Received: from localhost (tim@localhost) by ppp6460.on.bellglobal.com (8.8.8/8.8.8) with SMTP id RAA00823; Mon, 23 Feb 1998 17:32:40 -0500 (EST) (envelope-from ac199@hwcn.org) X-Authentication-Warning: ppp6460.on.bellglobal.com: tim owned process doing -bs Date: Mon, 23 Feb 1998 17:32:40 -0500 (EST) From: Tim Vanderhoek X-Sender: tim@localhost Reply-To: ac199@hwcn.org To: Nate Williams cc: ac199@james.hwcn.org, "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: <199802230537.WAA26811@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 22 Feb 1998, Nate Williams wrote: > > Well, go ahead and start and pointy-hat page. > > Public humiliation *never* does anything well. Big sticks should be > waved in private instead of public, as any management book written will > tell you. This isn't about public humillamation, this is about bragging rights. "I've only broken the tree twice!! Nyah-hahaha!! I'm twice the hacker you ever were! My llama's bigger than your llama!" It's humillamation when only one person is singled out. That's why I suggested asking for volunteers to get the page off to a good start. Of course, it must be said that it is easier to just blame the core team for not brandishing their big sticks. > (Public humiliation are large parts of why we had WWII...) _Gratuitous_ public humiliation, that is. -- tIM...HOEk OPTIMIZATION: the process of using many one-letter variables names hoping that the resultant code will run faster. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 14:37:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29470 for freebsd-current-outgoing; Mon, 23 Feb 1998 14:37:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (tc-31.acadiau.ca [131.162.2.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29396 for ; Mon, 23 Feb 1998 14:37:23 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id SAA00278; Mon, 23 Feb 1998 18:36:16 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 23 Feb 1998 18:36:15 -0400 (AST) From: The Hermit Hacker To: Mike Smith cc: Amancio Hasty , freebsd-current@FreeBSD.ORG Subject: Re: ATAPI related patch .. In-Reply-To: <199802232218.OAA12635@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Feb 1998, Mike Smith wrote: > > I thought that the low level scsi i/o routines did just that io with > > ioctls... > > The low-level SCSI I/O routines need a freeform I/O approach, and > they're designed for casual poking at things in an out-of-band fashion, > sort of like a SCSI geek-port. > > Luigi's hack is for CDDA (sucking audio off the CD) acccess; this is > basically bulk data transfer. Being a read-like operation, it's better > handled as such. Actually, CDDA is one way of doing it...tosha appears to be the other way, but, as currently distributed, tosha only supports SCSI CDs...this patch, as well as one for tosha, were produced to provide those of us without SCSI subsystems on their machines the ability to 'suck audio off the CD', like those with SCSI can already do :( > With a little more work, once you support audio accesses in the driver > properly, you become able to produce a "cdrom audio FS", where tracks > on the disk appear as files when the disk is mounted. > > I appreciate that Luigi's hack is expedient, and as I said if there's a > strong precedent (ie. binary compatability issues) then sure, we should > support it. In Luigi's defence...this was not his hack, he's only kept a copy that he's provided for those of us that wish to be able to read audio tracks off of our CDs... My opinion tends to be to bring in something that does work, and then from there, improve it...else it never gets done :( This patch may not be the best way to do it, but it is one way, and, as far as I can tell, it doesn't disrupt anything in the kernel, since I'm running live with it right now... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 14:48:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01845 for freebsd-current-outgoing; Mon, 23 Feb 1998 14:48:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01839 for ; Mon, 23 Feb 1998 14:48:53 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA12635; Mon, 23 Feb 1998 14:18:42 -0800 (PST) Message-Id: <199802232218.OAA12635@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Amancio Hasty cc: Mike Smith , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: ATAPI related patch .. In-reply-to: Your message of "Mon, 23 Feb 1998 14:08:49 PST." <199802232208.OAA00599@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Feb 1998 14:18:42 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I thought that the low level scsi i/o routines did just that io with > ioctls... The low-level SCSI I/O routines need a freeform I/O approach, and they're designed for casual poking at things in an out-of-band fashion, sort of like a SCSI geek-port. Luigi's hack is for CDDA (sucking audio off the CD) acccess; this is basically bulk data transfer. Being a read-like operation, it's better handled as such. With a little more work, once you support audio accesses in the driver properly, you become able to produce a "cdrom audio FS", where tracks on the disk appear as files when the disk is mounted. I appreciate that Luigi's hack is expedient, and as I said if there's a strong precedent (ie. binary compatability issues) then sure, we should support it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 14:58:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04672 for freebsd-current-outgoing; Mon, 23 Feb 1998 14:58:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com ([209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04652 for ; Mon, 23 Feb 1998 14:58:54 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id OAA00599; Mon, 23 Feb 1998 14:08:49 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802232208.OAA00599@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Mike Smith cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: ATAPI related patch .. In-reply-to: Your message of "Mon, 23 Feb 1998 14:03:40 PST." <199802232203.OAA12585@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Feb 1998 14:08:49 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I thought that the low level scsi i/o routines did just that io with ioctls... Amancio > > > > I recently grabbed a patch that Luigi (freebsd-multimedia) has > > that is required in order to read audio tracks (using something like > > tosha) from a CD...with minor modifications, I've got it in my -current > > kernel and haven't noticed any problems. > > Thanks for the review! > > > I would like to commit the patch to the -current source tree, so > > am asking here if there are any objections to doing this. If I hear > > nothing by Wednesday (long enough?), I'll assume that it is okay and > > commit it... > > Erk. This is thoroughly grostic. You shouldn't be doing I/O using an > ioctl; this behaviour should belong on a new minor number and the raw > device read handler. > > I would vote against the inclusion of this code, unless there is an > overwhelming precedent for the technique. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 14:59:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04719 for freebsd-current-outgoing; Mon, 23 Feb 1998 14:59:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com ([209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04698 for ; Mon, 23 Feb 1998 14:59:02 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id OAA00974; Mon, 23 Feb 1998 14:58:15 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802232258.OAA00974@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Mike Smith cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: ATAPI related patch .. In-reply-to: Your message of "Mon, 23 Feb 1998 14:18:42 PST." <199802232218.OAA12635@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Feb 1998 14:58:15 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, In the past we have supported reading Video CDs as well as audio CD via the low level scsi routines. So yes I can read audio off a cd via a low level ioctl call. I am not objecting to your comment just merely wish to express that there is already a precedence for doing i/o with ioctls. Amancio > > I thought that the low level scsi i/o routines did just that io with > > ioctls... > > The low-level SCSI I/O routines need a freeform I/O approach, and > they're designed for casual poking at things in an out-of-band fashion, > sort of like a SCSI geek-port. > > Luigi's hack is for CDDA (sucking audio off the CD) acccess; this is > basically bulk data transfer. Being a read-like operation, it's better > handled as such. > > With a little more work, once you support audio accesses in the driver > properly, you become able to produce a "cdrom audio FS", where tracks > on the disk appear as files when the disk is mounted. > > I appreciate that Luigi's hack is expedient, and as I said if there's a > strong precedent (ie. binary compatability issues) then sure, we should > support it. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 16:34:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28611 for freebsd-current-outgoing; Mon, 23 Feb 1998 16:34:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28588 for ; Mon, 23 Feb 1998 16:34:05 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id LAA08839; Tue, 24 Feb 1998 11:03:49 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id LAA13436; Tue, 24 Feb 1998 11:03:48 +1030 (CST) (envelope-from grog) Message-ID: <19980224110347.29951@freebie.lemis.com> Date: Tue, 24 Feb 1998 11:03:47 +1030 From: Greg Lehey To: Terry Lambert , "Jordan K. Hubbard" Cc: nate@mt.sri.com, current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. References: <28177.888206042@time.cdrom.com> <199802231012.DAA29929@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199802231012.DAA29929@usr02.primenet.com>; from Terry Lambert on Mon, Feb 23, 1998 at 10:12:03AM +0000 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 February 1998 at 10:12:03 +0000, Terry Lambert wrote: >>> I wouldn't like me if I didn't argue passionately for rigor over >>> expediency, correctness over fuzz, revolution over evolution, and >>> foul-tasting medicine where foul-tasting medicine is called for. >> >> And I don't think that anyone begrudges you that. The bigger area of >> concern, and the one I was specifically referring to, is your >> occasional predilection for recommending leeches as a cure for >> anemia. ;-) > > Actually, "leeches and anemia" are a bad example. It seems that > leeches work in this case ("New England Journal of Medicine", March 1989, > or thereabouts, I believe... though I could be mistaken, and it might > have been "Lancet"). I think you've just made Jordan's point. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 16:49:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00843 for freebsd-current-outgoing; Mon, 23 Feb 1998 16:49:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00824 for ; Mon, 23 Feb 1998 16:49:48 -0800 (PST) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA01757; Tue, 24 Feb 1998 11:18:58 +1030 (CST) Message-Id: <199802240048.LAA01757@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: "Jordan K. Hubbard" , nate@mt.sri.com, current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Feb 1998 11:18:58 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Actually, "leeches and anemia" are a bad example. It seems that > > leeches work in this case ("New England Journal of Medicine", March 1989, > > or thereabouts, I believe... though I could be mistaken, and it might > > have been "Lancet"). No no! They use leeches for helping remove bad blood from areas of the body with poor blood flow.. Then of course there is the use of maggots for removing necrotic tissue.. I just love modern medicine :) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 16:49:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00849 for freebsd-current-outgoing; Mon, 23 Feb 1998 16:49:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00825 for ; Mon, 23 Feb 1998 16:49:49 -0800 (PST) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA01734; Tue, 24 Feb 1998 11:18:11 +1030 (CST) Message-Id: <199802240048.LAA01734@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert , "Jordan K. Hubbard" , nate@mt.sri.com, current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-reply-to: Your message of "Tue, 24 Feb 1998 11:03:47 +1030." <19980224110347.29951@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Feb 1998 11:18:10 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 23 February 1998 at 10:12:03 +0000, Terry Lambert wrote: > >>> I wouldn't like me if I didn't argue passionately for rigor over > >>> expediency, correctness over fuzz, revolution over evolution, and > >>> foul-tasting medicine where foul-tasting medicine is called for. > >> > >> And I don't think that anyone begrudges you that. The bigger area of > >> concern, and the one I was specifically referring to, is your > >> occasional predilection for recommending leeches as a cure for > >> anemia. ;-) > > > > Actually, "leeches and anemia" are a bad example. It seems that > > leeches work in this case ("New England Journal of Medicine", March 1989, > > or thereabouts, I believe... though I could be mistaken, and it might > > have been "Lancet"). > > I think you've just made Jordan's point. > > Greg > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 16:56:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02960 for freebsd-current-outgoing; Mon, 23 Feb 1998 16:56:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02949 for ; Mon, 23 Feb 1998 16:56:05 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id QAA03190; Mon, 23 Feb 1998 16:53:51 -0800 (PST) To: Greg Lehey cc: Terry Lambert , nate@mt.sri.com, current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-reply-to: Your message of "Tue, 24 Feb 1998 11:03:47 +1030." <19980224110347.29951@freebie.lemis.com> Date: Mon, 23 Feb 1998 16:53:50 -0800 Message-ID: <3186.888281630@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Actually, "leeches and anemia" are a bad example. It seems that > > leeches work in this case ("New England Journal of Medicine", March 1989, > > or thereabouts, I believe... though I could be mistaken, and it might > > have been "Lancet"). > > I think you've just made Jordan's point. Well, I was sort of inclined to give Terry the benefit of the doubt on this one since, for all I know, some berserk set of researchers somewhere *have* figured out a way of getting bone marrow to kick into high gear in response to leech-injected anti-coagulants, thus knocking conventional wisdom on its ear. The essential point I was trying to make, however, still remains even if (and, I repeat, *if* since net searches for "leech" and "anemia" in proximity having turned up nothing so far) I may have chosen a bad example. I'm all in favor of folks trying to be renaissance men in the finest tradition of Leonardo da Vinci, but sometimes a speaker's desire to be knowledgeable on all topics can turn very wearisome to the listeners when he's inclined to lecture at great length on topics where his enthusiasm has overshadowed his abilities. To also be fair, nowadays with Terry confining himself more to purely filesystem related issues rather than lengthy dissertations on the effects of QED on sparrow flight velocities in the southern hemisphere (complete with ASCII art diagrams of course) or the 4 Lost Chapters of the Kama Sutra (ASCII censored), this has been much less of a problem and I can probably put off buying that extra 4GB drive for the mail archives at least another month or two. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 17:14:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06817 for freebsd-current-outgoing; Mon, 23 Feb 1998 17:14:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06714 for ; Mon, 23 Feb 1998 17:13:54 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id UAA18281; Mon, 23 Feb 1998 20:09:38 -0500 (EST) Date: Mon, 23 Feb 1998 20:09:38 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: "Daniel O'Connor" cc: Terry Lambert , "Jordan K. Hubbard" , nate@mt.sri.com, current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: <199802240048.LAA01757@cain.gsoft.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Feb 1998, Daniel O'Connor wrote: > > > > Actually, "leeches and anemia" are a bad example. It seems that > > > leeches work in this case ("New England Journal of Medicine", March 1989, > > > or thereabouts, I believe... though I could be mistaken, and it might > > > have been "Lancet"). > No no! They use leeches for helping remove bad blood from areas of the body > with poor blood flow.. Then of course there is the use of maggots for removing > necrotic tissue.. No, Terry's right, I saw reference to that in Science News, there was some kind of chemical that a leech leaves behind that was actually beneficial to the one who'd just been sucked. They weren't suggesting moving the clock back 200 years, but they were trying to find ways to make use of that chemical in modern medicine. I think that was about a year back, if anyone wants to search www.sciencenews.org. > I just love modern medicine :) > > --------------------------------------------------------------------- > |Daniel O'Connor software and network engineer for Genesis Software | > |http://www.gsoft.com.au | > |The nice thing about standards is that there are so many of them to| > |choose from. -- Andrew Tanenbaum | > --------------------------------------------------------------------- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 18:15:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15792 for freebsd-current-outgoing; Mon, 23 Feb 1998 18:15:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA15766 for ; Mon, 23 Feb 1998 18:15:06 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 22679 invoked by uid 1000); 24 Feb 1998 02:21:31 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-021598 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 23 Feb 1998 18:21:31 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: The Hermit Hacker Subject: Re: ATAPI related patch .. Cc: freebsd-current@FreeBSD.ORG, Amancio Hasty , Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Feb-98 The Hermit Hacker wrote: ... > My opinion tends to be to bring in something that does work, and > then from there, improve it...else it never gets done :( This patch may > not be the best way to do it, but it is one way, and, as far as I can > tell, it doesn't disrupt anything in the kernel, since I'm running live > with it right now... My $0.02 worth: Last I checked IOCTL stood for I/O Control. Let's keep it this way. To turn an IOCTL system call READ to a bonfide read operation, as Dennis intended it to be, is all of 20 minutes. Testing included. Let's have the thing semantically correct, before we accept it. If desired, send me the patch and I'll add the read.write interface. Simon ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 18:16:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16054 for freebsd-current-outgoing; Mon, 23 Feb 1998 18:16:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA16002 for ; Mon, 23 Feb 1998 18:16:29 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 22707 invoked by uid 1000); 24 Feb 1998 02:23:08 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-021598 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199802232258.OAA00974@rah.star-gate.com> Date: Mon, 23 Feb 1998 18:23:08 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Amancio Hasty Subject: Re: ATAPI related patch .. Cc: freebsd-current@FreeBSD.ORG, The Hermit Hacker , Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Feb-98 Amancio Hasty wrote: > Hi, > > In the past we have supported reading Video CDs as well as audio CD via > the low level scsi routines. So yes I can read audio off a cd via a low > level ioctl call. I am not objecting to your comment just merely wish > to express that there is already a precedence for doing i/o with ioctls. > > Amancio If we actually do data I/O via IOCTL on SCSI, then this is broken as well. Especially in SCSI which has an abstraction layer already (sd, st, od, mt, etc.). Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 18:35:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18698 for freebsd-current-outgoing; Mon, 23 Feb 1998 18:35:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18692 for ; Mon, 23 Feb 1998 18:35:31 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id TAA06165; Mon, 23 Feb 1998 19:35:13 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd006130; Mon Feb 23 19:35:09 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id TAA13911; Mon, 23 Feb 1998 19:35:06 -0700 (MST) From: Terry Lambert Message-Id: <199802240235.TAA13911@usr05.primenet.com> Subject: Re: ATAPI related patch .. To: mike@smith.net.au (Mike Smith) Date: Tue, 24 Feb 1998 02:35:06 +0000 (GMT) Cc: hasty@rah.star-gate.com, mike@smith.net.au, scrappy@hub.org, freebsd-current@FreeBSD.ORG In-Reply-To: <199802232218.OAA12635@dingo.cdrom.com> from "Mike Smith" at Feb 23, 98 02:18:42 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Luigi's hack is for CDDA (sucking audio off the CD) acccess; this is > basically bulk data transfer. Being a read-like operation, it's better > handled as such. > > With a little more work, once you support audio accesses in the driver > properly, you become able to produce a "cdrom audio FS", where tracks > on the disk appear as files when the disk is mounted. Pull the other one. Audio track disk blocks are not evenly divisible into (or by) a page size. There are all *sorts* of nice coherency problems that you run into from this. Effectively, you would need the LCM of the non-factors which are not LCF, to be read at one time. Otherwise you won't get a "page not present" error when you have a page that is partially valid. This problem gets worse if you want to *write* audio tracks. Talk to Julian; we hashed this all out over a whiteboard one night when I wanted to start using the 8-bit field, take the page mapping hit, and either go with the page that was there or read partial pages from disk for the MSDOSFS case where the 1k "blocks" began at a one block offset (possible on some older geometry drives). I was being less ambitious, in that I only wanted to handle runs of blocks in 512b multiples at (possible) multiple minus 1 non-zero offsets. Just the 1k disk/2k optical media/msdosfs non-even cylinder boundry cases... Julian's soloution is more correct, but it's a lot of work to support arbitrary block sizes (*especially* if the block size happens to be prime(!)...). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 18:46:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20779 for freebsd-current-outgoing; Mon, 23 Feb 1998 18:46:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20774 for ; Mon, 23 Feb 1998 18:46:36 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id SAA13579; Mon, 23 Feb 1998 18:43:07 -0800 (PST) Message-Id: <199802240243.SAA13579@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), hasty@rah.star-gate.com, scrappy@hub.org, freebsd-current@FreeBSD.ORG Subject: Re: ATAPI related patch .. In-reply-to: Your message of "Tue, 24 Feb 1998 02:35:06 GMT." <199802240235.TAA13911@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Feb 1998 18:43:06 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Luigi's hack is for CDDA (sucking audio off the CD) acccess; this is > > basically bulk data transfer. Being a read-like operation, it's better > > handled as such. > > > > With a little more work, once you support audio accesses in the driver > > properly, you become able to produce a "cdrom audio FS", where tracks > > on the disk appear as files when the disk is mounted. > > Pull the other one. Audio track disk blocks are not evenly divisible > into (or by) a page size. I'm not pulling nothing. Put an audio CD into your Win98 machine (or Win95 OSR2 machine for that matter), and 'cd' to the drive in a penalty box. Tell me what you see *there*. > There are all *sorts* of nice coherency problems that you run into from > this. > > Effectively, you would need the LCM of the non-factors which are not > LCF, to be read at one time. Otherwise you won't get a "page not > present" error when you have a page that is partially valid. Sure, this is just a case where you need a SLICE layer that understands non-multiple non-factor block size transforms. > This problem gets worse if you want to *write* audio tracks. I don't think anyone is that stupid. Mastering an audio CD isn't a trivial operation. 8) Bear in mind that all you're actually doing is providing directory entries that someone can open. Nobody says that the files can be *mapped*, although they ought to be mappable. 8) On the other hand, if you only allow access via ioctl's, this isn't even possible. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 18:57:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22434 for freebsd-current-outgoing; Mon, 23 Feb 1998 18:57:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com ([209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22426 for ; Mon, 23 Feb 1998 18:57:17 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id SAA11687; Mon, 23 Feb 1998 18:56:36 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802240256.SAA11687@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Mike Smith cc: Terry Lambert , scrappy@hub.org, freebsd-current@FreeBSD.ORG Subject: Re: ATAPI related patch .. In-reply-to: Your message of "Mon, 23 Feb 1998 18:43:06 PST." <199802240243.SAA13579@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Feb 1998 18:56:36 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, I really don't see the point on this . We can have a low level interface as well as a high level interface. So please pave the way for the low level interface or I will. Thank you, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 19:23:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25354 for freebsd-current-outgoing; Mon, 23 Feb 1998 19:23:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25347 for ; Mon, 23 Feb 1998 19:23:56 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id TAA28838; Mon, 23 Feb 1998 19:17:32 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd028835; Mon Feb 23 19:17:25 1998 Message-ID: <34F23AD3.31DFF4F5@whistle.com> Date: Tue, 24 Feb 1998 11:13:23 +0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Terry Lambert CC: Mike Smith , hasty@rah.star-gate.com, scrappy@hub.org, freebsd-current@FreeBSD.ORG Subject: Re: ATAPI related patch .. References: <199802240235.TAA13911@usr05.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > Talk to Julian; we hashed this all out over a whiteboard one night > when I wanted to start using the 8-bit field, take the page mapping > hit, and either go with the page that was there or read partial > pages from disk for the MSDOSFS case where the 1k "blocks" began > at a one block offset (possible on some older geometry drives). I > was being less ambitious, in that I only wanted to handle runs of > blocks in 512b multiples at (possible) multiple minus 1 non-zero > offsets. Just the 1k disk/2k optical media/msdosfs non-even > cylinder boundry cases... > > Julian's soloution is more correct, but it's a lot of work to support > arbitrary block sizes (*especially* if the block size happens to be > prime(!)...). duh I remember the conversation but I'm dammed if I can rememeber my solution :-) (did it have to do with getpage/putpage or something? (or am I thinking'of the wrong conversation?)) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 19:25:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25861 for freebsd-current-outgoing; Mon, 23 Feb 1998 19:25:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25806 for ; Mon, 23 Feb 1998 19:25:40 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id UAA17268; Mon, 23 Feb 1998 20:25:37 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd017209; Mon Feb 23 20:25:31 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id UAA16750; Mon, 23 Feb 1998 20:25:26 -0700 (MST) From: Terry Lambert Message-Id: <199802240325.UAA16750@usr05.primenet.com> Subject: Re: More breakage in -current as a result of header frobbing. To: chuckr@glue.umd.edu (Chuck Robey) Date: Tue, 24 Feb 1998 03:25:25 +0000 (GMT) Cc: doconnor@gsoft.com.au, tlambert@primenet.com, jkh@time.cdrom.com, nate@mt.sri.com, current@FreeBSD.ORG In-Reply-To: from "Chuck Robey" at Feb 23, 98 08:09:38 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No, Terry's right, I saw reference to that in Science News, there was some > kind of chemical that a leech leaves behind that was actually beneficial > to the one who'd just been sucked. They weren't suggesting moving the > clock back 200 years, but they were trying to find ways to make use of > that chemical in modern medicine. I think that was about a year back, if > anyone wants to search www.sciencenews.org. Desirudin. It's a thrombin inhibitor. Apparently, it it causes elevated erythropoietin levels. I think the reference is: "Current Concepts: Erythropoietin Therapy" The New England Journal of Medicine March 27, 1997 -- Volume 336, Number 13 Lawrence T. Goodnough, Terri G. Monk, Gerald L. Andriole Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 19:33:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27959 for freebsd-current-outgoing; Mon, 23 Feb 1998 19:33:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27940 for ; Mon, 23 Feb 1998 19:33:20 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id UAA00456; Mon, 23 Feb 1998 20:33:12 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd000425; Mon Feb 23 20:33:11 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id UAA17080; Mon, 23 Feb 1998 20:33:06 -0700 (MST) From: Terry Lambert Message-Id: <199802240333.UAA17080@usr05.primenet.com> Subject: Re: ATAPI related patch .. To: mike@smith.net.au (Mike Smith) Date: Tue, 24 Feb 1998 03:33:05 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, hasty@rah.star-gate.com, scrappy@hub.org, freebsd-current@FreeBSD.ORG In-Reply-To: <199802240243.SAA13579@dingo.cdrom.com> from "Mike Smith" at Feb 23, 98 06:43:06 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Pull the other one. Audio track disk blocks are not evenly divisible > > into (or by) a page size. > > I'm not pulling nothing. Put an audio CD into your Win98 machine (or > Win95 OSR2 machine for that matter), and 'cd' to the drive in a penalty > box. > > Tell me what you see *there*. A display on a graphical exporer front-ending for an OS without a unified VM and buffer cache. > Sure, this is just a case where you need a SLICE layer that understands > non-multiple non-factor block size transforms. No. Julian's soloution was that you would need to aggregate partial real blocks underneath the page abstraction. Like many things, it requires a working VOP_{GET|PUT}PAGES. > Bear in mind that all you're actually doing is providing directory > entries that someone can open. Nobody says that the files can be > *mapped*, although they ought to be mappable. 8) If you are going to read them, then you are going to (effectively) map them, because the VM objects backed by the file are hung off the vnode. All a mapping is, is pointing a memory region at a set of pages backed by a vnode. It doesn't matter how the pages got hung off the vnode, so long as the contain completely valid or completely invalid data. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 20:02:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00602 for freebsd-current-outgoing; Mon, 23 Feb 1998 20:02:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com ([209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA00594 for ; Mon, 23 Feb 1998 20:02:44 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id UAA14922; Mon, 23 Feb 1998 20:01:18 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802240401.UAA14922@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: shimon@simon-shapiro.org cc: freebsd-current@FreeBSD.ORG, The Hermit Hacker , Mike Smith Subject: Re: ATAPI related patch .. In-reply-to: Your message of "Mon, 23 Feb 1998 18:23:08 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Feb 1998 20:01:18 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not really and I have been able to watch movies as well as extract audio tracks. Can I do it from a scsi tape drive? Nope. It appears that you are not familiar with our low level scsi interface. Cheers, Amancio > > On 23-Feb-98 Amancio Hasty wrote: > > Hi, > > > > In the past we have supported reading Video CDs as well as audio CD via > > the low level scsi routines. So yes I can read audio off a cd via a low > > level ioctl call. I am not objecting to your comment just merely wish > > to express that there is already a precedence for doing i/o with ioctls. > > > > Amancio > > If we actually do data I/O via IOCTL on SCSI, then this is broken as well. > Especially in SCSI which has an abstraction layer already (sd, st, od, mt, > etc.). > > Simon > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 22:50:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17429 for freebsd-current-outgoing; Mon, 23 Feb 1998 22:50:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17374 for ; Mon, 23 Feb 1998 22:50:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA14231; Mon, 23 Feb 1998 22:46:22 -0800 (PST) Message-Id: <199802240646.WAA14231@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), hasty@rah.star-gate.com, scrappy@hub.org, freebsd-current@FreeBSD.ORG Subject: Re: ATAPI related patch .. In-reply-to: Your message of "Tue, 24 Feb 1998 03:33:05 GMT." <199802240333.UAA17080@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Feb 1998 22:46:21 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Pull the other one. Audio track disk blocks are not evenly divisible > > > into (or by) a page size. > > > > I'm not pulling nothing. Put an audio CD into your Win98 machine (or > > Win95 OSR2 machine for that matter), and 'cd' to the drive in a penalty > > box. > > > > Tell me what you see *there*. > > A display on a graphical exporer front-ending for an OS without a > unified VM and buffer cache. OK. Perhaps I should have said "what does the user see there". Remember that at least some of us are interested in the results as seen by the user. 8) > > Sure, this is just a case where you need a SLICE layer that understands > > non-multiple non-factor block size transforms. > > No. Julian's soloution was that you would need to aggregate partial > real blocks underneath the page abstraction. I wouldn't even bother with patial blocks, but I'm probably being too primitive about it. > Like many things, it requires a working VOP_{GET|PUT}PAGES. Do you have one? Where is it in the queue of swallowable chunks? > > Bear in mind that all you're actually doing is providing directory > > entries that someone can open. Nobody says that the files can be > > *mapped*, although they ought to be mappable. 8) > > If you are going to read them, then you are going to (effectively) > map them, because the VM objects backed by the file are hung off the > vnode. All a mapping is, is pointing a memory region at a set of > pages backed by a vnode. It doesn't matter how the pages got hung > off the vnode, so long as the contain completely valid or completely > invalid data. 8-). Sure. And below the mapping (do you ever go that far down? 8) there lives a strategy handler, and that strategy handler gets passed an offset and a length, in some agreed block size. From there, all you need is the block size transform (and as mooted, a means for dealing with the write case where you logically only write part of a physical block). All pie-in-the-sky stuff, of course. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 23:30:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA20764 for freebsd-current-outgoing; Mon, 23 Feb 1998 23:30:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ache.relcom.ru (ache@ache.relcom.ru [193.125.20.108]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA20666; Mon, 23 Feb 1998 23:29:53 -0800 (PST) (envelope-from ache@ache.relcom.ru) Received: (from ache@localhost) by ache.relcom.ru (8.8.8/8.8.8) id KAA00274; Tue, 24 Feb 1998 10:24:36 +0300 (MSK) (envelope-from ache) Message-ID: <19980224102430.49385@nagual.pp.ru> Date: Tue, 24 Feb 1998 10:24:30 +0300 From: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= To: phk@FreeBSD.ORG, current@FreeBSD.ORG Subject: more about adjkerntz & calcru negative time Mail-Followup-To: phk@freebsd.org, current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 27 root 18 0 204K 20K pause ??? 0.00% 0.00% adjkerntz ^^^ time column from top What about resetting process time fields when process itself resets time backwards? -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 23 23:58:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA24649 for freebsd-current-outgoing; Mon, 23 Feb 1998 23:58:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA24631 for ; Mon, 23 Feb 1998 23:58:35 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id AAA24997; Tue, 24 Feb 1998 00:58:30 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpd024940; Tue Feb 24 00:58:21 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id AAA16091; Tue, 24 Feb 1998 00:58:17 -0700 (MST) From: Terry Lambert Message-Id: <199802240758.AAA16091@usr09.primenet.com> Subject: Re: ATAPI related patch .. To: mike@smith.net.au (Mike Smith) Date: Tue, 24 Feb 1998 07:58:16 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, hasty@rah.star-gate.com, scrappy@hub.org, freebsd-current@FreeBSD.ORG In-Reply-To: <199802240646.WAA14231@dingo.cdrom.com> from "Mike Smith" at Feb 23, 98 10:46:21 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Like many things, it requires a working VOP_{GET|PUT}PAGES. > > Do you have one? Where is it in the queue of swallowable chunks? Depends on what you are willing to swallow or not, doesn't it? I can't answer a subjective question. Would it be the same code you would have written had you taken the time to write it instead of me? I don't know. The VOP_{GET|PUT}PAGES in UFS is OK, and the recent hack for MFS is OK, too. What's left? Any local media FS (any FS where the storage is managed by the FS code, ie: none of the stacking FS's, and none of the remote FS's, like AFS, CODA, or NFS). > Sure. And below the mapping (do you ever go that far down? 8) there > lives a strategy handler, and that strategy handler gets passed an > offset and a length, in some agreed block size. That is, of course, what VOP_{GET|PUT}PAGES would be calling, in your putative audio CD FS. The one difference is that you would have to have a block cache for four blocks in front of it to deal with assembly of physical blocks into pages. > All pie-in-the-sky stuff, of course. Hardly. If I send you the code for a local media FS to implement VOP_{GET|PUT}PAGES, will you commit it? You can even test it first, by seeing if you can run FreeBSD binaries off it... This is the type of code I class as "trivial"... ie: not a challenge to write (which says nothing about the time involved). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 00:45:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28608 for freebsd-current-outgoing; Tue, 24 Feb 1998 00:45:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28597 for ; Tue, 24 Feb 1998 00:45:44 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id JAA05443 for ; Tue, 24 Feb 1998 09:48:12 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 24 Feb 1998 09:48:12 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-current@FreeBSD.ORG Subject: Proposed addition to panic() behaviour Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Many people (including me) suffered from panic while their console was in graphic mode (e.g. X Window). I don't know if this would be proper place to do this, but in case of panic (where everything is lost anyway) just add there the code to forcefully reset the video card to set it in known (and useful) mode... Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 00:46:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28898 for freebsd-current-outgoing; Tue, 24 Feb 1998 00:46:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA28879 for ; Tue, 24 Feb 1998 00:46:38 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA07901; Tue, 24 Feb 1998 08:11:39 +0100 From: Luigi Rizzo Message-Id: <199802240711.IAA07901@labinfo.iet.unipi.it> Subject: Re: ATAPI related patch .. To: mike@smith.net.au (Mike Smith) Date: Tue, 24 Feb 1998 08:11:39 +0100 (MET) Cc: hasty@rah.star-gate.com, mike@smith.net.au, scrappy@hub.org, freebsd-current@FreeBSD.ORG In-Reply-To: <199802232218.OAA12635@dingo.cdrom.com> from "Mike Smith" at Feb 23, 98 02:18:23 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The low-level SCSI I/O routines need a freeform I/O approach, and > they're designed for casual poking at things in an out-of-band fashion, ... > Luigi's hack is for CDDA (sucking audio off the CD) acccess; this is > basically bulk data transfer. Being a read-like operation, it's better > handled as such. ... > I appreciate that Luigi's hack is expedient, and as I said if there's a > strong precedent (ie. binary compatability issues) then sure, we should > support it. as a precedent, i would like to mention that access to audio/videocd and other stuff from a SCSI CD is done using the generic IO approach. Same thing is done for accessing SCSI scanners. I am the first to say that this is not nice but at least you get the job done in a simple way. This said, i _DON'T_ like to have this patch NOW in the -current tree because our atapi subsystem, as i mentioned far too many times, does not have proper timeout handling, and implementing a generic ATAPI ioctl, together with broken firmware in the atapi peripherals, opens the door to all sort of deadlocks on the corresponding IDE bus. Since many people might have another IDE disk on the same bus, they risk losing their data which is undesirable... > With a little more work, once you support audio accesses in the driver > properly, you become able to produce a "cdrom audio FS", where tracks > on the disk appear as files when the disk is mounted. I think there are priorities, and in this case making the system more robust with a proper watchdog is by far more important than implementing read access to audio, or a audio cd filesystem, etc. etc. This even for the impending release of 2.2.6. Those (forget the name(s)) who said it would be easy to add a proper read() interface to audio cd, should really consider spending this time into making the watchdog work for the atapi devices as well. >From what i have seen (but my knowledge of the wd/wcd driver is too limited) it might just require adding a reference to the IDE bus descriptor in the atapi device descriptor, and then more or less invoke the same routines which already exist for ide devices. I can't do that because at the moment i have no easy access to a crash machine. cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 00:57:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00315 for freebsd-current-outgoing; Tue, 24 Feb 1998 00:57:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00307 for ; Tue, 24 Feb 1998 00:57:20 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id JAA01421; Tue, 24 Feb 1998 09:56:29 +0100 (MET) (envelope-from sos) Message-Id: <199802240856.JAA01421@sos.freebsd.dk> Subject: Re: ATAPI related patch .. In-Reply-To: <199802240711.IAA07901@labinfo.iet.unipi.it> from Luigi Rizzo at "Feb 24, 98 08:11:39 am" To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Tue, 24 Feb 1998 09:56:29 +0100 (MET) Cc: mike@smith.net.au, hasty@rah.star-gate.com, scrappy@hub.org, freebsd-current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Luigi Rizzo who wrote: > This said, i _DON'T_ like to have this patch NOW in the -current > tree because our atapi subsystem, as i mentioned far too many times, > does not have proper timeout handling, and implementing a generic > ATAPI ioctl, together with broken firmware in the atapi peripherals, > opens the door to all sort of deadlocks on the corresponding IDE > bus. Since many people might have another IDE disk on the same bus, > they risk losing their data which is undesirable... I'm working on the atapi system right now, I have semilar problems (and new ones :) ) with the atapi tape driver. I'd like to do a rewrite, but I simply doesn't have the time for that now, so I'll try to fix what we have. I'm well aware of the potential hangs we can suffer :( -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 01:05:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01538 for freebsd-current-outgoing; Tue, 24 Feb 1998 01:05:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA01533; Tue, 24 Feb 1998 01:05:40 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA07994; Tue, 24 Feb 1998 08:31:53 +0100 From: Luigi Rizzo Message-Id: <199802240731.IAA07994@labinfo.iet.unipi.it> Subject: Re: ATAPI related patch .. To: sos@FreeBSD.ORG Date: Tue, 24 Feb 1998 08:31:53 +0100 (MET) Cc: mike@smith.net.au, hasty@rah.star-gate.com, scrappy@hub.org, freebsd-current@FreeBSD.ORG In-Reply-To: <199802240856.JAA01421@sos.freebsd.dk> from "Søren Schmidt" at Feb 24, 98 09:56:10 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm working on the atapi system right now, I have semilar problems > (and new ones :) ) with the atapi tape driver. I'd like to do a > rewrite, but I simply doesn't have the time for that now, so I'll > try to fix what we have. I'm well aware of the potential hangs i don't think a full rewrite is necessary, just add state to the atapi descriptor so that a timeout routine can be called and it can track the corresponding ide bus to reset it. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 01:13:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA02426 for freebsd-current-outgoing; Tue, 24 Feb 1998 01:13:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com ([209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA02421 for ; Tue, 24 Feb 1998 01:13:23 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id BAA22624; Tue, 24 Feb 1998 01:12:29 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802240912.BAA22624@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Luigi Rizzo cc: mike@smith.net.au (Mike Smith), scrappy@hub.org, freebsd-current@FreeBSD.ORG Subject: Re: ATAPI related patch .. In-reply-to: Your message of "Tue, 24 Feb 1998 08:11:39 +0100." <199802240711.IAA07901@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Feb 1998 01:12:29 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The low-level SCSI I/O routines need a freeform I/O approach, and > > they're designed for casual poking at things in an out-of-band fashion, > ... > > Luigi's hack is for CDDA (sucking audio off the CD) acccess; this is > > basically bulk data transfer. Being a read-like operation, it's better > > handled as such. > ... > > I appreciate that Luigi's hack is expedient, and as I said if there's a > > strong precedent (ie. binary compatability issues) then sure, we should > > support it. > > as a precedent, i would like to mention that access to audio/videocd > and other stuff from a SCSI CD is done using the generic IO approach. > Same thing is done for accessing SCSI scanners. I am the first to > say that this is not nice but at least you get the job done in a > simple way. > > This said, i _DON'T_ like to have this patch NOW in the -current > tree because our atapi subsystem, as i mentioned far too many times, > does not have proper timeout handling, and implementing a generic > ATAPI ioctl, together with broken firmware in the atapi peripherals, > opens the door to all sort of deadlocks on the corresponding IDE We forgot to mention that whomever embarks on a high level abstraction for dealing with multimedia devices including scanners has to also content with writing and supporting the underlying hardware which in many instances has not been standardized or hardware vendors are very lax . Do a net search on the linux scsi scanner project SANE and dig up the code to get a hint. If someone decides to support the new IDE standards for reading audio or video then we have the problem of backwards compatibility. For sure in scsi land , we will have a problem take a peek at the code for tosha if you you are curious -- we of course can drag all the brand/model specifics details for dealing with different scsi cdroms to the kernel. The Philips format for video cds is propieratory and over the long run it is not a good idea to have it in the kernel or the sources widely available. We can get around this obstacle by having someone with a license from Philips to write a user land program, driver, or an lkm. If memory does fail me the Philips license prohibits the distribution of source code to decode CDI or Video CDs. We can try to publish the code however we will be asking for trouble. brian@worldcontrol.com can explain further for we have discuss this issue in the past and he has had the opportunity to chat with Philips with respect to this issue. While we are in the topic of audio/video interfaces for CDs someone should take a look at what Linux is doing in this area for we can potentially benefit in this area . Quake ][ is a key program which currently we don't support reading the CD's audio track. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 01:37:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA05743 for freebsd-current-outgoing; Tue, 24 Feb 1998 01:37:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA05738 for ; Tue, 24 Feb 1998 01:37:51 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id CAA05253; Tue, 24 Feb 1998 02:37:50 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd005245; Tue Feb 24 02:37:41 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id CAA04990; Tue, 24 Feb 1998 02:37:41 -0700 (MST) From: Terry Lambert Message-Id: <199802240937.CAA04990@usr05.primenet.com> Subject: Re: Proposed addition to panic() behaviour To: abial@nask.pl (Andrzej Bialecki) Date: Tue, 24 Feb 1998 09:37:40 +0000 (GMT) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: from "Andrzej Bialecki" at Feb 24, 98 09:48:12 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Many people (including me) suffered from panic while their console was in > graphic mode (e.g. X Window). I don't know if this would be proper place > to do this, but in case of panic (where everything is lost anyway) just > add there the code to forcefully reset the video card to set it in > known (and useful) mode... See the numerous "DDX in the kernel" discussions in the -current list archives to see why "just add there the code to forcefully reset the video card" requires knowing how the video card got in the mode it's in, and specific knowledge of the card (hint: write-only hardware registers not shadoewed in RAM). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 01:45:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06958 for freebsd-current-outgoing; Tue, 24 Feb 1998 01:45:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06953 for ; Tue, 24 Feb 1998 01:45:15 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id CAA05960; Tue, 24 Feb 1998 02:45:13 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd005922; Tue Feb 24 02:45:03 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id CAA05263; Tue, 24 Feb 1998 02:44:58 -0700 (MST) From: Terry Lambert Message-Id: <199802240944.CAA05263@usr05.primenet.com> Subject: Re: ATAPI related patch .. To: tlambert@primenet.com (Terry Lambert) Date: Tue, 24 Feb 1998 09:44:58 +0000 (GMT) Cc: mike@smith.net.au, tlambert@primenet.com, hasty@rah.star-gate.com, scrappy@hub.org, freebsd-current@FreeBSD.ORG In-Reply-To: <199802240758.AAA16091@usr09.primenet.com> from "Terry Lambert" at Feb 24, 98 07:58:16 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > All pie-in-the-sky stuff, of course. > > Hardly. If I send you the code for a local media FS to implement > VOP_{GET|PUT}PAGES, will you commit it? You can even test it first, > by seeing if you can run FreeBSD binaries off it... > > This is the type of code I class as "trivial"... ie: not a challenge > to write (which says nothing about the time involved). OK, while bored waiting for Julian to send me a pointer to where he has uploaded the most recent slice code so I could hack on a BAD144 stacking layer (hint, hint, Julian)... Here is a first run at the code. It exports some generic routines that are to be wedged into local media FS's until such time as the FS specific code can be written. Clearly, the "bypass" code has to work for umapfs/unionfs/nullfs to be happy with this change; I didn't bother with them, since they are broken as they currently sit. Here is the URL: http://freebsd.org/~terry/ And here is the README: =========================================================================== These diffs implement the first stage of a VOP_{GET|PUT}PAGES pushdown for local media FS's. See ffs_putpages in /sys/ufs/ufs/ufs_readwrite.c for implementation details for generic *_{get|put}pages for local media FS's. Support is trivial to add for any FS that formerly relied on the default behaviour of the vnode_pager in in EOPNOTSUPP cases (just copy the ffs_getpages() code for the FS in question's *_{get|put}pages). Obviously, it would be better if each local media FS implemented a more optimal method, instead of calling an exported interface from the /sys/vm/vnode_pager.c, but this is a necessary first step in getting the FS's to a point where they can be supplied with better implementations on a case-by-case basis. Obviously, the cd9660_putpages() can be rather trivial (since it is a read-only FS type 8-)). EOF. =========================================================================== Like I said: trivial. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 01:57:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA07810 for freebsd-current-outgoing; Tue, 24 Feb 1998 01:57:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA07801 for ; Tue, 24 Feb 1998 01:57:00 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id KAA20821; Tue, 24 Feb 1998 10:58:56 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 24 Feb 1998 10:58:56 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Terry Lambert cc: freebsd-current@FreeBSD.ORG Subject: Re: Proposed addition to panic() behaviour In-Reply-To: <199802240937.CAA04990@usr05.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Feb 1998, Terry Lambert wrote: > > Many people (including me) suffered from panic while their console was in > > graphic mode (e.g. X Window). I don't know if this would be proper place > > to do this, but in case of panic (where everything is lost anyway) just > > add there the code to forcefully reset the video card to set it in > > known (and useful) mode... > > See the numerous "DDX in the kernel" discussions in the -current list > archives to see why "just add there the code to forcefully reset the > video card" requires knowing how the video card got in the mode it's > in, and specific knowledge of the card (hint: write-only hardware > registers not shadoewed in RAM). I see. But syscons driver _knows_ how to switch from X to text mode, doesn't it? Even if it *sometimes* fails (because some obscure registers are garbled), *most of the time* it produces useful result. This would be enough... Hmm... Or is it the X server who knows how to do it, not the syscons? But I also vaguely recall something like dump of VGA registers when booted with -v, so they are stored somewhere, right? Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 02:03:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA08609 for freebsd-current-outgoing; Tue, 24 Feb 1998 02:03:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c243.moon.jic.com [206.156.18.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA08600 for ; Tue, 24 Feb 1998 02:03:20 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id FAA00765; Tue, 24 Feb 1998 05:03:03 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Andrzej Bialecki cc: Terry Lambert , freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Proposed addition to panic() behaviour In-reply-to: Your message of "Tue, 24 Feb 1998 10:58:56 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Feb 1998 05:03:03 -0500 Message-ID: <761.888314583@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote in message ID : > I see. But syscons driver _knows_ how to switch from X to text mode, > doesn't it? Even if it *sometimes* fails (because some obscure registers > are garbled), *most of the time* it produces useful result. This would be > enough... Its X, not syscons. X has trapped keyboard events and stopped syscons from interpreting them. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 02:05:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA08930 for freebsd-current-outgoing; Tue, 24 Feb 1998 02:05:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA08916 for ; Tue, 24 Feb 1998 02:05:00 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: by outmail.utsunomiya-u.ac.jp id AA03702; Tue, 24 Feb 1998 19:03:52 +0900 Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id TAA12153; Tue, 24 Feb 1998 19:11:49 +0900 (JST) Message-Id: <199802241011.TAA12153@zodiac.mech.utsunomiya-u.ac.jp> To: Andrzej Bialecki Cc: freebsd-current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Proposed addition to panic() behaviour In-Reply-To: Your message of "Tue, 24 Feb 1998 10:58:56 +0100." References: Date: Tue, 24 Feb 1998 19:11:48 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > Many people (including me) suffered from panic while their console was in >> > graphic mode (e.g. X Window). I don't know if this would be proper place >> > to do this, but in case of panic (where everything is lost anyway) just >> > add there the code to forcefully reset the video card to set it in >> > known (and useful) mode... >> >> See the numerous "DDX in the kernel" discussions in the -current list >> archives to see why "just add there the code to forcefully reset the >> video card" requires knowing how the video card got in the mode it's >> in, and specific knowledge of the card (hint: write-only hardware >> registers not shadoewed in RAM). > >I see. But syscons driver _knows_ how to switch from X to text mode, >doesn't it? No, it doesn't. >Even if it *sometimes* fails (because some obscure registers >are garbled), *most of the time* it produces useful result. This would be >enough... > >Hmm... Or is it the X server who knows how to do it, not the syscons? Yes. This is the case. >But I also vaguely recall something like dump of VGA registers >when booted with -v, so they are stored somewhere, right? The video BIOS ROM contains the table of STANDARD register values only. We cannot know which additional registers should be set to what value. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 02:10:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10028 for freebsd-current-outgoing; Tue, 24 Feb 1998 02:10:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA09897 for ; Tue, 24 Feb 1998 02:09:51 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id JAA08096; Tue, 24 Feb 1998 09:35:38 +0100 From: Luigi Rizzo Message-Id: <199802240835.JAA08096@labinfo.iet.unipi.it> Subject: Re: ATAPI related patch .. To: hasty@rah.star-gate.com (Amancio Hasty) Date: Tue, 24 Feb 1998 09:35:38 +0100 (MET) Cc: mike@smith.net.au, scrappy@hub.org, freebsd-current@FreeBSD.ORG In-Reply-To: <199802240912.BAA22624@rah.star-gate.com> from "Amancio Hasty" at Feb 24, 98 01:12:10 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We forgot to mention that whomever embarks on a high level abstraction > for dealing with multimedia devices including scanners has to also > content with writing and supporting the underlying hardware which in > many instances has not been standardized or hardware vendors are > very lax . Do a net search on the linux scsi scanner project SANE and ... in other words: not worth the effort ? > While we are in the topic of audio/video interfaces for CDs > someone should take a look at what Linux is doing in this area i gave a very quick look a couple of months ago and I think they have some generic ioctl for atapi access. > for we can potentially benefit in this area . Quake ][ is > a key program which currently we don't support reading the > CD's audio track. what we can do is probably add the usual ioctl mapping in linux_ioctl.c cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 02:10:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10143 for freebsd-current-outgoing; Tue, 24 Feb 1998 02:10:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA10114 for ; Tue, 24 Feb 1998 02:10:49 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id LAA24300; Tue, 24 Feb 1998 11:13:16 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 24 Feb 1998 11:13:16 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Kazutaka YOKOTA cc: freebsd-current@FreeBSD.ORG Subject: Re: Proposed addition to panic() behaviour In-Reply-To: <199802241011.TAA12153@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Feb 1998, Kazutaka YOKOTA wrote: > >> > Many people (including me) suffered from panic while their console was in > >> > graphic mode (e.g. X Window). I don't know if this would be proper place > >> > to do this, but in case of panic (where everything is lost anyway) just > >> > add there the code to forcefully reset the video card to set it in > >> > known (and useful) mode... > >> > >> See the numerous "DDX in the kernel" discussions in the -current list > >> archives to see why "just add there the code to forcefully reset the > >> video card" requires knowing how the video card got in the mode it's > >> in, and specific knowledge of the card (hint: write-only hardware > >> registers not shadoewed in RAM). > > > >But I also vaguely recall something like dump of VGA registers > >when booted with -v, so they are stored somewhere, right? > > The video BIOS ROM contains the table of STANDARD register values only. > We cannot know which additional registers should be set to what value. Ok. Call me stubborn, but why can't we just write the STANDARD register values corresponding to the initial state of the card, and if the screen is still garbled, well - at least we tried... But, my point is (or maybe I'm still wrong), that *most of the time* this will restore the card to some usable state... Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 02:22:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11848 for freebsd-current-outgoing; Tue, 24 Feb 1998 02:22:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11803 for ; Tue, 24 Feb 1998 02:22:28 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id LAA01674; Tue, 24 Feb 1998 11:22:12 +0100 (MET) (envelope-from sos) Message-Id: <199802241022.LAA01674@sos.freebsd.dk> Subject: Re: Proposed addition to panic() behaviour In-Reply-To: from Andrzej Bialecki at "Feb 24, 98 11:13:16 am" To: abial@nask.pl (Andrzej Bialecki) Date: Tue, 24 Feb 1998 11:22:11 +0100 (MET) Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, freebsd-current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Andrzej Bialecki who wrote: > > >But I also vaguely recall something like dump of VGA registers > > >when booted with -v, so they are stored somewhere, right? > > > > The video BIOS ROM contains the table of STANDARD register values only. > > We cannot know which additional registers should be set to what value. > > Ok. Call me stubborn, but why can't we just write the STANDARD register > values corresponding to the initial state of the card, and if the screen > is still garbled, well - at least we tried... But, my point is (or > maybe I'm still wrong), that *most of the time* this will restore the card > to some usable state... It will only work on a std VGA card in a std mode. All moderne video cards demands specific programming (or what do you think the thousands of lines of code in Xfree86 does :) ) So your answer is it will not work most of the time, if at all. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 02:28:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13273 for freebsd-current-outgoing; Tue, 24 Feb 1998 02:28:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13114; Tue, 24 Feb 1998 02:28:07 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with ESMTP id LAA27904; Tue, 24 Feb 1998 11:30:36 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 24 Feb 1998 11:30:36 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: =?ISO-8859-2?Q?S=F8ren_Schmidt?= cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, freebsd-current@FreeBSD.ORG Subject: Re: Proposed addition to panic() behaviour In-Reply-To: <199802241022.LAA01674@sos.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-2 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Feb 1998, Søren Schmidt wrote: > In reply to Andrzej Bialecki who wrote: > > > >But I also vaguely recall something like dump of VGA registers > > > >when booted with -v, so they are stored somewhere, right? > > > > > > The video BIOS ROM contains the table of STANDARD register values only. > > > We cannot know which additional registers should be set to what value. > > > > Ok. Call me stubborn, but why can't we just write the STANDARD register > > values corresponding to the initial state of the card, and if the screen > > is still garbled, well - at least we tried... But, my point is (or > > maybe I'm still wrong), that *most of the time* this will restore the card > > to some usable state... > > It will only work on a std VGA card in a std mode. All moderne video cards > demands specific programming (or what do you think the thousands of lines > of code in Xfree86 does :) ) > > So your answer is it will not work most of the time, if at all. Now you convinced me :-) Well, if this is the case I'll try to switch to the text mode as soon as I see the crash is coming... ;-> Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 02:28:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13319 for freebsd-current-outgoing; Tue, 24 Feb 1998 02:28:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com ([209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13280 for ; Tue, 24 Feb 1998 02:28:33 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id CAA23278; Tue, 24 Feb 1998 02:27:16 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802241027.CAA23278@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Luigi Rizzo cc: mike@smith.net.au, scrappy@hub.org, freebsd-current@FreeBSD.ORG Subject: Re: ATAPI related patch .. In-reply-to: Your message of "Tue, 24 Feb 1998 09:35:38 +0100." <199802240835.JAA08096@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Feb 1998 02:27:16 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We forgot to mention that whomever embarks on a high level abstraction > > for dealing with multimedia devices including scanners has to also > > content with writing and supporting the underlying hardware which in > > many instances has not been standardized or hardware vendors are > > very lax . Do a net search on the linux scsi scanner project SANE and > ... > > in other words: not worth the effort ? It is worth the effort if we have a small team ready to tackle the project other than that is a pie in the sky idea. > > While we are in the topic of audio/video interfaces for CDs > > someone should take a look at what Linux is doing in this area > > i gave a very quick look a couple of months ago and I think they have > some generic ioctl for atapi access. Thats cool ... > > for we can potentially benefit in this area . Quake ][ is > > a key program which currently we don't support reading the > > CD's audio track. > > what we can do is probably add the usual ioctl mapping in linux_ioctl.c If we have the ioctl functionality in the kernel to map to 8) Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 02:34:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14745 for freebsd-current-outgoing; Tue, 24 Feb 1998 02:34:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com ([209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14724 for ; Tue, 24 Feb 1998 02:34:50 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id CAA23367; Tue, 24 Feb 1998 02:34:19 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802241034.CAA23367@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Andrzej Bialecki cc: Kazutaka YOKOTA , freebsd-current@FreeBSD.ORG Subject: Re: Proposed addition to panic() behaviour In-reply-to: Your message of "Tue, 24 Feb 1998 11:13:16 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Feb 1998 02:34:19 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 24 Feb 1998, Kazutaka YOKOTA wrote: > > > >> > Many people (including me) suffered from panic while their console was in > > >> > graphic mode (e.g. X Window). I don't know if this would be proper place > > >> > to do this, but in case of panic (where everything is lost anyway) just > > >> > add there the code to forcefully reset the video card to set it in > > >> > known (and useful) mode... > > >> > > >> See the numerous "DDX in the kernel" discussions in the -current list > > >> archives to see why "just add there the code to forcefully reset the > > >> video card" requires knowing how the video card got in the mode it's > > >> in, and specific knowledge of the card (hint: write-only hardware > > >> registers not shadoewed in RAM). > > > > > > >But I also vaguely recall something like dump of VGA registers > > >when booted with -v, so they are stored somewhere, right? > > > > The video BIOS ROM contains the table of STANDARD register values only. > > We cannot know which additional registers should be set to what value. > > Ok. Call me stubborn, but why can't we just write the STANDARD register > values corresponding to the initial state of the card, and if the screen > is still garbled, well - at least we tried... But, my point is (or > maybe I'm still wrong), that *most of the time* this will restore the card > to some usable state... > Look I worked on low level graphic support for S3 cards as well as other graphic cards and is not an easy thing to do at least in a clean fashion. You can however write a simple shell program that monitors the X server and restart it if you need to or use xdm which is supposed to re-start an X server if it dies -- usually it just pops you back to a login screen if the X server dies. However... if you think you can do it go ahead thats the attitute which allow me to port X to 386bsd 0.0 8) Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 03:08:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA18811 for freebsd-current-outgoing; Tue, 24 Feb 1998 03:08:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.com.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA18779 for ; Tue, 24 Feb 1998 03:07:55 -0800 (PST) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-10-09.camtech.net.au [203.28.1.137]) by goliath.camtech.com.au (8.8.5/8.8.2) with ESMTP id VAA10072; Tue, 24 Feb 1998 21:35:23 +1030 (CST) Message-ID: <34F2A9F0.E41A7227@camtech.net.au> Date: Tue, 24 Feb 1998 21:37:28 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Bob Bishop CC: current@FreeBSD.ORG Subject: Re: Build still broken - NOT! - (at CTM src-cur 3261) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have no trouble with "make world" at CTM src-cur.3261 Here's what I do when I want to make the world: chflags -R noschg /usr/obj/usr rm -rf /usr/obj/usr build a new version of config - cd /usr/src/usr.sbin/config - make - cp -p config /usr/sbin/config.new - make clean make a new kernel and boot on it. (I use "config.new -r MYKERN" to be sure) update my /etc files make world I then reboot and build a new kernel again. This may all seem like overkill but I like to be sure with -CURRENT! This built fine for me. I have "CFLAGS= -O -pipe" and "NOTCL= true" in my /etc/make.conf matte: {32} cat /usr/src/.ctm_status src-cur 3261 matte: {33} grep "make world" /usr/src/WORLD.log make world started on Tue Feb 24 01:04:58 CST 1998 make world completed on Tue Feb 24 04:38:08 CST 1998 matte: {34} Is there any other information you would like ? Bob Bishop wrote: > > This is as of CTM src-cur 3261: > > cc -nostdinc -O2 -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mno-486 > -DBOOTWAIT=5000 -DTIMEOUT= -DBOOTSEG=0x1000 -DBOOTSTACK=0xFFF0 -DDO_BAD144 > -DVES > A_SUPPORT -nostdinc > -I/source/cleansrc/sys/i386/boot/biosboot/../../../../includ > e -I/source/cleansrc/sys/i386/boot/biosboot/../../.. > -I/usr/obj/source/cleansrc/ > sys/i386/boot/biosboot -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit > -Wn > ested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline > -Wuninitialized -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 > -I/usr/obj/source/cleansrc > /tmp/usr/include -c /source/cleansrc/sys/i386/boot/biosboot/table.c > In file included from /source/cleansrc/sys/i386/boot/biosboot/boot.h:35, > from /source/cleansrc/sys/i386/boot/biosboot/table.c:53: > /source/cleansrc/sys/i386/boot/biosboot/../../../../include/ufs/ufs/inode.h:62: > field `i_lock' has incomplete type > *** Error code 1 > > Stop. > > -- > Bob Bishop (0118) 977 4017 international code +44 118 > rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 04:15:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26338 for freebsd-current-outgoing; Tue, 24 Feb 1998 04:15:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA26330 for ; Tue, 24 Feb 1998 04:15:24 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id NAA21153 for ; Tue, 24 Feb 1998 13:17:55 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 24 Feb 1998 13:17:54 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-current@FreeBSD.ORG Subject: Warning: malloc wrapped Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I'm getting this type of messages right after "Uncompressing kernel" message when booting kzip'ped -current kernel with MFS compiled in (and / on MFS). Anyway, the kernel boots and everything seems to work ok. Are these messages benign? And what are they? Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 05:21:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04575 for freebsd-current-outgoing; Tue, 24 Feb 1998 05:21:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA04529 for ; Tue, 24 Feb 1998 05:20:43 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id MAA08268; Tue, 24 Feb 1998 12:43:21 +0100 From: Luigi Rizzo Message-Id: <199802241143.MAA08268@labinfo.iet.unipi.it> Subject: Re: ATAPI related patch .. To: hasty@rah.star-gate.com (Amancio Hasty) Date: Tue, 24 Feb 1998 12:43:20 +0100 (MET) Cc: mike@smith.net.au, scrappy@hub.org, freebsd-current@FreeBSD.ORG In-Reply-To: <199802241027.CAA23278@rah.star-gate.com> from "Amancio Hasty" at Feb 24, 98 02:26:57 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > what we can do is probably add the usual ioctl mapping in linux_ioctl.c > > If we have the ioctl functionality in the kernel to map to 8) that would "my" (actually Luoqi's) ioctl which Marc proposed to bring into the tree. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 05:24:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA05279 for freebsd-current-outgoing; Tue, 24 Feb 1998 05:24:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA05267 for ; Tue, 24 Feb 1998 05:24:47 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id MAA08325; Tue, 24 Feb 1998 12:50:35 +0100 From: Luigi Rizzo Message-Id: <199802241150.MAA08325@labinfo.iet.unipi.it> Subject: Re: ATAPI related patch .. To: hasty@rah.star-gate.com (Amancio Hasty) Date: Tue, 24 Feb 1998 12:50:34 +0100 (MET) Cc: mike@smith.net.au, scrappy@hub.org, freebsd-current@FreeBSD.ORG In-Reply-To: <199802241027.CAA23278@rah.star-gate.com> from "Amancio Hasty" at Feb 24, 98 02:26:57 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It is worth the effort if we have a small team ready to tackle the > project other than that is a pie in the sky idea. now i'd really like to see a precedent in FreeBSD :) It seems to me that most recent improvements have come from one-man teams... cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 05:26:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA05815 for freebsd-current-outgoing; Tue, 24 Feb 1998 05:26:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailhost.creditanstalt.co.at ([193.83.167.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA05800 for ; Tue, 24 Feb 1998 05:26:33 -0800 (PST) (envelope-from Jacek.Strzelbicki@creditanstalt.co.at) Received: from mailhub(10.1.241.6) by localhost via smap (V1.3) id sma034652; Tue Feb 24 14:28:13 1998 Received: from vl.creditanstalt.co.at (vl [162.25.13.68]) by mailhub.cait.co.at with SMTP (8.8.8/8.7.1) id OAA00499 for ; Tue, 24 Feb 1998 14:26:38 +0100 (MET) Received: by vl.creditanstalt.co.at with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52) id <01BD4130.0FFBAE70@vl.creditanstalt.co.at>; Tue, 24 Feb 1998 14:25:31 +0100 Message-Id: From: Strzelbicki Jacek To: "'freebsd-current@FreeBSD.ORG'" Date: Tue, 24 Feb 1998 11:14:17 +0100 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-current Jacek strzelbicki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 08:55:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29819 for freebsd-current-outgoing; Tue, 24 Feb 1998 08:55:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29810 for ; Tue, 24 Feb 1998 08:55:26 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id LAA00660; Tue, 24 Feb 1998 11:55:13 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199802241655.LAA00660@dyson.iquest.net> Subject: Re: problems with XView and FreeBSD In-Reply-To: <34ECD591.41C67EA6@starbase.spd.louisville.edu> from "V Edward Gold, Jr." at "Feb 20, 98 01:00:01 am" To: vegold01@starbase.spd.louisville.edu (V Edward Gold, Jr.) Date: Tue, 24 Feb 1998 11:55:13 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG V Edward Gold, Jr. said: > I just recently started playing with an application that was written > originally on SunOS 4.1.3 and I ported it to FreeBSD 2.2.1 and > everything was fine. I upgraded to 3.0 and now I experience problems > apparently caused by using the notify_do_dispatch() call and ANY > subsequent file I/O. I went ahead and attached the sample program that > demonstrates this oddity, in case anyone wants to help me locate its > source/cure. I compile it as follows: > gcc -o main main.c -I/usr/X11R6/include -g -L/usr/X11R6/lib -lxview > \ -lX11 -lolgx > > while( 1 ) > { > char cmd_buffer[1024]; > sprintf( msg, prompt ); > write( fileno( stdout ), msg, strlen( msg ) ); > fflush( stdout ); > while( read( fileno(stdin), sizeof(cmd_buffer), cmd_buffer ) != 0 ); The order of args is wrong ^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^ > } > > free( cmd_word ); > } -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 09:22:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03472 for freebsd-current-outgoing; Tue, 24 Feb 1998 09:22:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03467 for ; Tue, 24 Feb 1998 09:22:50 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id LAA02694 for current@freebsd.org; Tue, 24 Feb 1998 11:22:50 -0600 (CST) From: Kevin Day Message-Id: <199802241722.LAA02694@home.dragondata.com> Subject: identd still not working right To: current@FreeBSD.ORG Date: Tue, 24 Feb 1998 11:22:49 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For me, identd is still complaining a lot. This started in early january. Feb 22 19:40:05 shell identd[23861]: getbuf: bad address (000018e8 not in f0100000-0xFFC00000) - ofile Feb 22 19:40:05 shell identd[23861]: getbuf: bad address (00000014 not in f0100000-0xFFC00000) - ofile Feb 22 19:40:05 shell last message repeated 3 times Feb 22 19:40:05 shell identd[23861]: k_getuid retries: 5 Feb 24 02:00:07 shell identd[6664]: getbuf: bad address (000042ee not in f0100000-0xFFC00000) - ofile Feb 24 02:00:08 shell identd[6664]: k_getuid retries: 1 Feb 24 08:47:29 shell /kernel: pid 17844 (identd), uid 0: exited on signal 11 Feb 24 08:53:15 shell /kernel: pid 18382 (identd), uid 0: exited on signal 11 I've grabbed identd again, compiled again, nothing seems to help. Anyone else seeing this? Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 09:51:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07225 for freebsd-current-outgoing; Tue, 24 Feb 1998 09:51:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07220 for ; Tue, 24 Feb 1998 09:51:45 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id JAA15553; Tue, 24 Feb 1998 09:40:11 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd015535; Tue Feb 24 09:40:06 1998 Message-ID: <34F30503.167EB0E7@whistle.com> Date: Wed, 25 Feb 1998 01:36:03 +0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Terry Lambert CC: mike@smith.net.au, hasty@rah.star-gate.com, scrappy@hub.org, freebsd-current@FreeBSD.ORG Subject: Re: ATAPI related patch .. References: <199802240944.CAA05263@usr05.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > OK, while bored waiting for Julian to send me a pointer to where > he has uploaded the most recent slice code so I could hack on a > BAD144 stacking layer (hint, hint, Julian)... sorry terry, a woman happenned. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 10:05:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09620 for freebsd-current-outgoing; Tue, 24 Feb 1998 10:05:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA09606 for ; Tue, 24 Feb 1998 10:04:59 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id MAA07090; Tue, 24 Feb 1998 12:04:47 -0600 (CST) From: Kevin Day Message-Id: <199802241804.MAA07090@home.dragondata.com> Subject: Re: identd still not working right In-Reply-To: <199802241759.KAA03340@panzer.plutotech.com> from "Kenneth D. Merry" at "Feb 24, 98 10:59:46 am" To: ken@plutotech.com (Kenneth D. Merry) Date: Tue, 24 Feb 1998 12:04:46 -0600 (CST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Kevin Day wrote... > > > > For me, identd is still complaining a lot. This started in early january. > > > > Feb 22 19:40:05 shell identd[23861]: getbuf: bad address (000018e8 not in f0100000-0xFFC00000) - ofile > > Feb 22 19:40:05 shell identd[23861]: getbuf: bad address (00000014 not in f0100000-0xFFC00000) - ofile > > Feb 22 19:40:05 shell last message repeated 3 times > > Feb 22 19:40:05 shell identd[23861]: k_getuid retries: 5 > > Feb 24 02:00:07 shell identd[6664]: getbuf: bad address (000042ee not in f0100000-0xFFC00000) - ofile > > Feb 24 02:00:08 shell identd[6664]: k_getuid retries: 1 > > Feb 24 08:47:29 shell /kernel: pid 17844 (identd), uid 0: exited on signal 11 > > Feb 24 08:53:15 shell /kernel: pid 18382 (identd), uid 0: exited on signal 11 > > > > I've grabbed identd again, compiled again, nothing seems to help. > > > > Anyone else seeing this? > > Make sure you kill the old identd process if it is still running. > I see those types of problems when there are VM system changes. > > Recompiling generally fixes it for me. I assume you've done a make > world to pick up all the library and header changes to go along with your > new kernel? > Yeah, it's not still the same old identd running. This has persisted throughout several make world's, and everything. I'm using the pidentd from the ports directory.... Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 10:43:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14197 for freebsd-current-outgoing; Tue, 24 Feb 1998 10:43:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14191 for ; Tue, 24 Feb 1998 10:43:27 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id LAA24796; Tue, 24 Feb 1998 11:43:16 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpd024753; Tue Feb 24 11:43:08 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id LAA08255; Tue, 24 Feb 1998 11:43:05 -0700 (MST) From: Terry Lambert Message-Id: <199802241843.LAA08255@usr01.primenet.com> Subject: Re: Proposed addition to panic() behaviour To: abial@nask.pl (Andrzej Bialecki) Date: Tue, 24 Feb 1998 18:43:05 +0000 (GMT) Cc: tlambert@primenet.com, freebsd-current@FreeBSD.ORG In-Reply-To: from "Andrzej Bialecki" at Feb 24, 98 10:58:56 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I see. But syscons driver _knows_ how to switch from X to text mode, > doesn't it? Even if it *sometimes* fails (because some obscure registers > are garbled), *most of the time* it produces useful result. This would be > enough... > > Hmm... Or is it the X server who knows how to do it, not the syscons? > But I also vaguely recall something like dump of VGA registers > when booted with -v, so they are stored somewhere, right? No, it does not know. It asks X to put the console back. If you panic, you can't run processes. Like X. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 10:45:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14694 for freebsd-current-outgoing; Tue, 24 Feb 1998 10:45:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14686 for ; Tue, 24 Feb 1998 10:45:09 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id LAA01023; Tue, 24 Feb 1998 11:44:54 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd000994; Tue Feb 24 11:44:50 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id LAA08323; Tue, 24 Feb 1998 11:44:33 -0700 (MST) From: Terry Lambert Message-Id: <199802241844.LAA08323@usr01.primenet.com> Subject: Re: ATAPI related patch .. To: julian@whistle.com (Julian Elischer) Date: Tue, 24 Feb 1998 18:44:33 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, hasty@rah.star-gate.com, scrappy@hub.org, freebsd-current@FreeBSD.ORG In-Reply-To: <34F30503.167EB0E7@whistle.com> from "Julian Elischer" at Feb 25, 98 01:36:03 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > OK, while bored waiting for Julian to send me a pointer to where > > he has uploaded the most recent slice code so I could hack on a > > BAD144 stacking layer (hint, hint, Julian)... > > sorry terry, a woman happenned. Sorry Julian; I guess you'll just have to put up with having a life... 8^). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 11:04:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17530 for freebsd-current-outgoing; Tue, 24 Feb 1998 11:04:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17521 for ; Tue, 24 Feb 1998 11:04:55 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id MAA28877; Tue, 24 Feb 1998 12:04:43 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp04.primenet.com, id smtpd028843; Tue Feb 24 12:04:40 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id MAA09163; Tue, 24 Feb 1998 12:04:37 -0700 (MST) From: Terry Lambert Message-Id: <199802241904.MAA09163@usr01.primenet.com> Subject: Re: Proposed addition to panic() behaviour To: abial@nask.pl (Andrzej Bialecki) Date: Tue, 24 Feb 1998 19:04:36 +0000 (GMT) Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, freebsd-current@FreeBSD.ORG In-Reply-To: from "Andrzej Bialecki" at Feb 24, 98 11:13:16 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The video BIOS ROM contains the table of STANDARD register values only. > > We cannot know which additional registers should be set to what value. > > Ok. Call me stubborn, but why can't we just write the STANDARD register > values corresponding to the initial state of the card, and if the screen > is still garbled, well - at least we tried... But, my point is (or > maybe I'm still wrong), that *most of the time* this will restore the card > to some usable state... Because video modes on any accelerator card will be a combination of standard and non-standard register values, and it is possible to actually smoke hardware by having a bad combination of settings (Diamond used to be a victim of this on occasion). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 11:13:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18642 for freebsd-current-outgoing; Tue, 24 Feb 1998 11:13:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18633 for ; Tue, 24 Feb 1998 11:13:19 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id MAA07973; Tue, 24 Feb 1998 12:13:09 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd007943; Tue Feb 24 12:13:03 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id MAA09695; Tue, 24 Feb 1998 12:12:59 -0700 (MST) From: Terry Lambert Message-Id: <199802241912.MAA09695@usr01.primenet.com> Subject: Re: ATAPI related patch .. To: hasty@rah.star-gate.com (Amancio Hasty) Date: Tue, 24 Feb 1998 19:12:58 +0000 (GMT) Cc: luigi@labinfo.iet.unipi.it, mike@smith.net.au, scrappy@hub.org, freebsd-current@FreeBSD.ORG In-Reply-To: <199802241027.CAA23278@rah.star-gate.com> from "Amancio Hasty" at Feb 24, 98 02:27:16 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > We forgot to mention that whomever embarks on a high level abstraction > > > for dealing with multimedia devices including scanners has to also > > > content with writing and supporting the underlying hardware which in > > > many instances has not been standardized or hardware vendors are > > > very lax . Do a net search on the linux scsi scanner project SANE and > > ... > > > > in other words: not worth the effort ? > > It is worth the effort if we have a small team ready to tackle the > project other than that is a pie in the sky idea. This small team would have to be: A) Highly comptetent so they can write the code B) Not so competent that they buy good hardware 8-|. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 11:35:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21490 for freebsd-current-outgoing; Tue, 24 Feb 1998 11:35:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA21475 for ; Tue, 24 Feb 1998 11:35:11 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 12117 invoked by uid 1000); 24 Feb 1998 19:41:37 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-021598 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199802240401.UAA14922@rah.star-gate.com> Date: Tue, 24 Feb 1998 11:41:36 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Amancio Hasty Subject: Re: ATAPI related patch .. Cc: Mike Smith , The Hermit Hacker , freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Feb-98 Amancio Hasty wrote: > > Not really and I have been able to watch movies as well as extract audio > tracks. Can I do it from a scsi tape drive? Nope. > > It appears that you are not familiar with our low level scsi interface. True, but I am rather familiar with Unix I/O semantics. One does data I/O via read(2) and write(2) system calls. The IOCTL system call was a hack to allow you to send control messages to the driver. The whole purpose of the Unix symetrical I/O is to abstract devices into file I/O semantics. I belive you wantch movies and play music, etc. That does not make the interface semantically correct. Does it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 11:43:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22545 for freebsd-current-outgoing; Tue, 24 Feb 1998 11:43:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA22529 for ; Tue, 24 Feb 1998 11:43:27 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 12257 invoked by uid 1000); 24 Feb 1998 19:50:09 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-021598 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199802241022.LAA01674@sos.freebsd.dk> Date: Tue, 24 Feb 1998 11:50:09 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: =?us-ascii?Q?S=F8ren?= Schmidt Subject: Re: Proposed addition to panic() behaviour Cc: freebsd-current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp, (Andrzej Bialecki) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Feb-98 Søren Schmidt wrote: ... > It will only work on a std VGA card in a std mode. All moderne video > cards > demands specific programming (or what do you think the thousands of lines > of code in Xfree86 does :) ) > > So your answer is it will not work most of the time, if at all. My ignorance shows all the time. When the system boots, something does something to the video card to make it go into a sane VGA mode. My ignorant assumption is that this something can be emulated/repeated with software in kernel mode. Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 11:57:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24395 for freebsd-current-outgoing; Tue, 24 Feb 1998 11:57:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from starbase.spd.louisville.edu (vegold01@starbase.spd.louisville.edu [136.165.99.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24389 for ; Tue, 24 Feb 1998 11:57:09 -0800 (PST) (envelope-from vegold01@starbase.spd.louisville.edu) Received: (from vegold01@localhost) by starbase.spd.louisville.edu (8.7.6/8.6.12) id OAA28243; Tue, 24 Feb 1998 14:56:55 -0500 (EST) From: Ed Gold Message-Id: <199802241956.OAA28243@starbase.spd.louisville.edu> Subject: Re: problems with XView and FreeBSD To: toor@dyson.iquest.net (John S. Dyson) Date: Tue, 24 Feb 1998 14:56:55 EST Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199802241655.LAA00660@dyson.iquest.net>; from "John S. Dyson" at Feb 24, 98 11:55 am X-Mailer: Elm [revision: 212.4] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > V Edward Gold, Jr. said: > > I just recently started playing with an application that was written > > originally on SunOS 4.1.3 and I ported it to FreeBSD 2.2.1 and > > everything was fine. I upgraded to 3.0 and now I experience problems > > apparently caused by using the notify_do_dispatch() call and ANY > > subsequent file I/O. I went ahead and attached the sample program that > > demonstrates this oddity, in case anyone wants to help me locate its > > source/cure. I compile it as follows: > > gcc -o main main.c -I/usr/X11R6/include -g -L/usr/X11R6/lib -lxview > > \ -lX11 -lolgx > > > > while( 1 ) > > { > > char cmd_buffer[1024]; > > sprintf( msg, prompt ); > > write( fileno( stdout ), msg, strlen( msg ) ); > > fflush( stdout ); > > while( read( fileno(stdin), sizeof(cmd_buffer), cmd_buffer ) != 0 ); > > The order of args is wrong ^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^ > > > } > > > > free( cmd_word ); > > } > > John, I appreciate the reply! Unfortunately, the real problem was that I was being a moron. I wrote up that example incorrectly, but to compound the problem, I was using the xview library from FreeBSD 2.2.1 instead of upgrading to the one from the ports. I recompiled from ports this morning and everything was groovy. Sorry for putting you through this pointless exercise. I also wish to apologize to everyone else for the wasted bandwidth. Thanks again, Ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 12:47:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05717 for freebsd-current-outgoing; Tue, 24 Feb 1998 12:47:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05477 for ; Tue, 24 Feb 1998 12:46:28 -0800 (PST) (envelope-from pb@fasterix.frmug.org) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id VAA29284 for freebsd-current@freebsd.org; Tue, 24 Feb 1998 21:46:07 +0100 (CET) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.8.8/8.8.5/pb-19970302) id VAA18780; Tue, 24 Feb 1998 21:44:13 +0100 (CET) Message-ID: <19980224214413.VV05778@@> Date: Tue, 24 Feb 1998 21:44:13 +0100 From: pb@fasterix.freenix.org (Pierre Beyssac) To: freebsd-current@FreeBSD.ORG Subject: broken nfsstat ? X-Mailer: Mutt 0.59.1e Mime-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It looks like there's something weird with nfsstat. Have I done something wrong? It's a -current from yesterday sources. $ nfsstat nfsstat: sysctl: No such file or directory $ modstat Type Id Off Loadaddr Size Info Rev Module Name VFS 0 2 f50a6000 00d5 f50d8890 1 nfs $ sysctl -A | grep nfs $ -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 13:29:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13847 for freebsd-current-outgoing; Tue, 24 Feb 1998 13:29:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13605; Tue, 24 Feb 1998 13:27:39 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id NAA16540; Tue, 24 Feb 1998 13:25:29 -0800 (PST) Message-Id: <199802242125.NAA16540@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: shimon@simon-shapiro.org cc: =?us-ascii?Q?S=F8ren?= Schmidt , freebsd-current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp, abial@nask.pl (Andrzej Bialecki) Subject: Re: Proposed addition to panic() behaviour In-reply-to: Your message of "Tue, 24 Feb 1998 11:50:09 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Tue, 24 Feb 1998 13:25:29 -0800 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id NAA13606 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 24-Feb-98 Søren Schmidt wrote: > > .... > > > It will only work on a std VGA card in a std mode. All moderne video > > cards > > demands specific programming (or what do you think the thousands of lines > > of code in Xfree86 does :) ) > > > > So your answer is it will not work most of the time, if at all. > > My ignorance shows all the time. When the system boots, something does > something to the video card to make it go into a sane VGA mode. My > ignorant assumption is that this something can be emulated/repeated with > software in kernel mode. That something is card-specific code in the BIOS ROM on the card. You may see it signing on if your monitor warms up quickly enough. This is real-mode 8086 code which can make all sorts of assumptions about the state of the machine at that point in the boot phase. Some of those assumptions aren't valid when the kernel is running. (Some are, but to get to a mode where you can run this code is a bit daunting.) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 15:18:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02759 for freebsd-current-outgoing; Tue, 24 Feb 1998 15:18:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02743 for ; Tue, 24 Feb 1998 15:18:11 -0800 (PST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id JAA27390; Wed, 25 Feb 1998 09:38:43 +1030 (CST) Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id FTBMCDN1; Wed, 25 Feb 1998 09:39:01 +1030 Received: from eddie.dsto.defence.gov.au (eddie.dsto.defence.gov.au [131.185.2.111]) by fang.dsto.defence.gov.au (8.8.5/8.8.5) with ESMTP id JAA04497; Wed, 25 Feb 1998 09:39:23 +1030 (CST) Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.8/8.8.5) with ESMTP id JAA05791; Wed, 25 Feb 1998 09:39:16 +1030 (CST) Message-ID: <34F3531B.BB3C830E@dsto.defence.gov.au> Date: Wed, 25 Feb 1998 09:39:15 +1030 From: Matthew Thyer Organization: Defence Science Technology Organisation X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Mike Smith CC: "Jordan K. Hubbard" , Ollivier Robert , current@FreeBSD.ORG Subject: VFAT/FAT32 References: <199802221908.LAA07867@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a newly "made world" machine at CTM src-cur.3261 I was able to mount_msdos my C: drive which is a Win95 B release installation on a newly formatted C: partition without FAT32 (without support for large drives as Micky soft calls it). It looked good through Xfm with long filenames in mixed case and filenames with spaces in them. So then I though I'd load StarOffice and try to read a Word 6 document. However when I clicked on the /dos directory (my C: drive mount point) using the "File Open" dialog box, the machine locked solid. I did not see the contents of the mount point appear in the dialog box at all and I had to press the reset switch as Ctrl-Alt-Del did nothing (Virtual console switching also had no effect). Mike Smith wrote: > > > > > Case in point: I'm still waiting for *anyone* save Mike Smith (who > > just confirmed it for me last night) to respond to my "VFAT/FAT32 > > support is in -current now, can someone test it?" and yet I've gotten > > about 6 messages about 4 stupid lines in /etc/services. Am I the only > > one here who thinks that people have their priorities rather severely > > skewed? :-) > > Can you say "Boggle"? > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe cvs-all" in the body of the message -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 15:20:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03443 for freebsd-current-outgoing; Tue, 24 Feb 1998 15:20:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA03399 for ; Tue, 24 Feb 1998 15:20:10 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 17408 invoked by uid 1000); 24 Feb 1998 23:26:54 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-021598 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199802242125.NAA16540@dingo.cdrom.com> Date: Tue, 24 Feb 1998 15:26:54 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Mike Smith Subject: Re: Proposed addition to panic() behaviour Cc: (Andrzej Bialecki) , yokota@zodiac.mech.utsunomiya-u.ac.jp, freebsd-current@FreeBSD.ORG, =?us-ascii?Q?S=F8ren?= Schmidt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Feb-98 Mike Smith wrote: >> >> On 24-Feb-98 Søren Schmidt wrote: >> >> .... >> >> > It will only work on a std VGA card in a std mode. All moderne video >> > cards >> > demands specific programming (or what do you think the thousands of >> > lines >> > of code in Xfree86 does :) ) >> > >> > So your answer is it will not work most of the time, if at all. >> >> My ignorance shows all the time. When the system boots, something does >> something to the video card to make it go into a sane VGA mode. My >> ignorant assumption is that this something can be emulated/repeated with >> software in kernel mode. > > That something is card-specific code in the BIOS ROM on the card. You > may see it signing on if your monitor warms up quickly enough. > > This is real-mode 8086 code which can make all sorts of assumptions > about the state of the machine at that point in the boot phase. Some > of those assumptions aren't valid when the kernel is running. (Some > are, but to get to a mode where you can run this code is a bit > daunting.) These entry points are known and standardized. since we are talking panic mode here, switching back to realmode, to reset the video card to standard VGA mode can be considrered and will have a very positive support impact. Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 15:29:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04988 for freebsd-current-outgoing; Tue, 24 Feb 1998 15:29:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04982 for ; Tue, 24 Feb 1998 15:29:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id PAA17023; Tue, 24 Feb 1998 15:25:47 -0800 (PST) Message-Id: <199802242325.PAA17023@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Matthew Thyer cc: Mike Smith , "Jordan K. Hubbard" , Ollivier Robert , current@FreeBSD.ORG Subject: Re: VFAT/FAT32 In-reply-to: Your message of "Wed, 25 Feb 1998 09:39:15 +1030." <34F3531B.BB3C830E@dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Feb 1998 15:25:44 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Matt; thanks for taking the time to play with this. > On a newly "made world" machine at CTM src-cur.3261 I was able to > mount_msdos my C: drive which is a Win95 B release installation > on a newly formatted C: partition without FAT32 (without support > for large drives as Micky soft calls it). OK. > It looked good through Xfm with long filenames in mixed case and > filenames with spaces in them. There appears to be an odd quirk where a ' character will truncate a name when it is being retrieved. > So then I though I'd load StarOffice and try to read a Word 6 > document. > > However when I clicked on the /dos directory (my C: drive mount > point) using the "File Open" dialog box, the machine locked solid. Ouch. Can you reproduce this reliably? Do you have a serial port you can put a serial console on and perhaps poke the system a bit there? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 15:31:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05567 for freebsd-current-outgoing; Tue, 24 Feb 1998 15:31:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05548; Tue, 24 Feb 1998 15:31:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id PAA17047; Tue, 24 Feb 1998 15:27:45 -0800 (PST) Message-Id: <199802242327.PAA17047@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: shimon@simon-shapiro.org cc: Mike Smith , abial@nask.pl (Andrzej Bialecki), yokota@zodiac.mech.utsunomiya-u.ac.jp, freebsd-current@FreeBSD.ORG, =?us-ascii?Q?S=F8ren?= Schmidt Subject: Re: Proposed addition to panic() behaviour In-reply-to: Your message of "Tue, 24 Feb 1998 15:26:54 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Tue, 24 Feb 1998 15:27:44 -0800 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id PAA05549 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > That something is card-specific code in the BIOS ROM on the card. You > > may see it signing on if your monitor warms up quickly enough. > > > > This is real-mode 8086 code which can make all sorts of assumptions > > about the state of the machine at that point in the boot phase. Some > > of those assumptions aren't valid when the kernel is running. (Some > > are, but to get to a mode where you can run this code is a bit > > daunting.) > > These entry points are known and standardized. since we are talking panic > mode here, switching back to realmode, to reset the video card to standard > VGA mode can be considrered and will have a very positive support impact. Yes, the entry points are well known and standardised. And if you want to write some simple code that switches back to real mode, hits the BIOS and then swaps back to the debugger call, then we'd be more than happy to include it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 15:37:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07006 for freebsd-current-outgoing; Tue, 24 Feb 1998 15:37:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06993 for ; Tue, 24 Feb 1998 15:37:14 -0800 (PST) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id KAA25657; Wed, 25 Feb 1998 10:05:49 +1030 (CST) Message-Id: <199802242335.KAA25657@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Amancio Hasty cc: Luigi Rizzo , mike@smith.net.au (Mike Smith), scrappy@hub.org, freebsd-current@FreeBSD.ORG Subject: Re: ATAPI related patch .. In-reply-to: Your message of "Tue, 24 Feb 1998 01:12:29 -0800." <199802240912.BAA22624@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Feb 1998 10:05:49 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > While we are in the topic of audio/video interfaces for CDs > someone should take a look at what Linux is doing in this area > for we can potentially benefit in this area . Quake ][ is > a key program which currently we don't support reading the > CD's audio track. I presume this is just because the Linux emulation layer does not have translations for the CD playing ioctls? (I've already had to port a linux program which uses the CD player, so maybe I should add these :) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 15:52:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08856 for freebsd-current-outgoing; Tue, 24 Feb 1998 15:52:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA08847 for ; Tue, 24 Feb 1998 15:52:32 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 19026 invoked by uid 1000); 24 Feb 1998 23:59:17 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-021598 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199802242327.PAA17047@dingo.cdrom.com> Date: Tue, 24 Feb 1998 15:59:17 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Mike Smith Subject: Re: Proposed addition to panic() behaviour Cc: =?us-ascii?Q?S=F8ren?= Schmidt , freebsd-current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp, (Andrzej Bialecki) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Feb-98 Mike Smith wrote: >> > That something is card-specific code in the BIOS ROM on the card. You >> > may see it signing on if your monitor warms up quickly enough. >> > >> > This is real-mode 8086 code which can make all sorts of assumptions >> > about the state of the machine at that point in the boot phase. Some >> > of those assumptions aren't valid when the kernel is running. (Some >> > are, but to get to a mode where you can run this code is a bit >> > daunting.) >> >> These entry points are known and standardized. since we are talking >> panic >> mode here, switching back to realmode, to reset the video card to >> standard >> VGA mode can be considrered and will have a very positive support >> impact. > > Yes, the entry points are well known and standardised. And if you want > to write some simple code that switches back to real mode, hits the > BIOS and then swaps back to the debugger call, then we'd be more than > happy to include it. I really hate to say this: Let's see if someone else who is more BIOS and real-mode fluent can pick this idea up. Last time I wrote something like this was a while ago, and I am sort of busy with other FreeBSD issues. Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 16:12:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12928 for freebsd-current-outgoing; Tue, 24 Feb 1998 16:12:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12913 for ; Tue, 24 Feb 1998 16:12:24 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id RAA02132; Tue, 24 Feb 1998 17:12:19 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd002108; Tue Feb 24 17:12:16 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id RAA25883; Tue, 24 Feb 1998 17:12:14 -0700 (MST) From: Terry Lambert Message-Id: <199802250012.RAA25883@usr01.primenet.com> Subject: Re: broken nfsstat ? To: pb@fasterix.freenix.org (Pierre Beyssac) Date: Wed, 25 Feb 1998 00:12:14 +0000 (GMT) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <19980224214413.VV05778@@> from "Pierre Beyssac" at Feb 24, 98 09:44:13 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It looks like there's something weird with nfsstat. Have I done > something wrong? It's a -current from yesterday sources. > > $ nfsstat > nfsstat: sysctl: No such file or directory > $ modstat > Type Id Off Loadaddr Size Info Rev Module Name > VFS 0 2 f50a6000 00d5 f50d8890 1 nfs > $ sysctl -A | grep nfs > $ The sysctl namespace is (partially, badly) autoconfigured via linker set. Linker sets do not agregate from LKM's. This is partly because of the linker interface, and partly because of the fact that FreeBSD is not ELF and partly because of the way inter-ELF linker set agregation requires a registration callback instead of taking the linker set at face value. If you want nfsstat, you need to statically link your NFS at this time, until we leave the a.out dark ages behind and fix the ELF agregation architectural issues that the gcc/gld people have so far failed to address. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 16:18:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13951 for freebsd-current-outgoing; Tue, 24 Feb 1998 16:18:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13924; Tue, 24 Feb 1998 16:17:59 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id KAA10308; Wed, 25 Feb 1998 10:47:34 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id KAA19194; Wed, 25 Feb 1998 10:47:33 +1030 (CST) (envelope-from grog) Message-ID: <19980225104733.25831@freebie.lemis.com> Date: Wed, 25 Feb 1998 10:47:33 +1030 From: Greg Lehey To: shimon@simon-shapiro.org, Mike Smith Cc: =?iso-8859-1?Q?S=F8ren_Schmidt?= , freebsd-current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp, Andrzej Bialecki Subject: Re: Proposed addition to panic() behaviour References: <199802242327.PAA17047@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Simon Shapiro on Tue, Feb 24, 1998 at 03:59:17PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 February 1998 at 15:59:17 -0800, Simon Shapiro wrote: > > On 24-Feb-98 Mike Smith wrote: >>>> That something is card-specific code in the BIOS ROM on the card. You >>>> may see it signing on if your monitor warms up quickly enough. >>>> >>>> This is real-mode 8086 code which can make all sorts of assumptions >>>> about the state of the machine at that point in the boot phase. Some >>>> of those assumptions aren't valid when the kernel is running. (Some >>>> are, but to get to a mode where you can run this code is a bit >>>> daunting.) >>> >>> These entry points are known and standardized. since we are talking >>> panic >>> mode here, switching back to realmode, to reset the video card to >>> standard >>> VGA mode can be considrered and will have a very positive support >>> impact. >> >> Yes, the entry points are well known and standardised. And if you want >> to write some simple code that switches back to real mode, hits the >> BIOS and then swaps back to the debugger call, then we'd be more than >> happy to include it. > > I really hate to say this: Let's see if someone else who is more BIOS and > real-mode fluent can pick this idea up. Last time I wrote something like > this was a while ago, and I am sort of busy with other FreeBSD > issues. Doesn't that go for all of us? That's why it's not there yet. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 16:29:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16668 for freebsd-current-outgoing; Tue, 24 Feb 1998 16:29:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kaos.atext.com (kaos.atext.com [204.62.245.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16659; Tue, 24 Feb 1998 16:29:31 -0800 (PST) (envelope-from kingson@excite.com) Received: from excite.com (batik [204.62.245.185]) by kaos.atext.com (8.8.5/8.8.5) with ESMTP id QAA01607; Tue, 24 Feb 1998 16:28:39 -0800 (PST) Message-ID: <34F365B8.8FFF939D@excite.com> Date: Tue, 24 Feb 1998 16:28:40 -0800 From: Kingson Gunawan Reply-To: kingson@excite.com Organization: Excite Inc. X-Mailer: Mozilla 4.04 [en] (X11; U; SunOS 5.6 sun4m) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG, freebsd-question@FreeBSD.ORG Subject: Help needed with DPT card + Asus M/B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anybody successfully run the DPT SmartRaid4 (PW-3334UW) with ASUS P2L97-DS? This combination keeps failing me... Detail: Asus P2L97-DS dual PII-300 512MB SDRAM Intel EtherExpress 100B SB16-Vibra Matrox Millenium 2MB/VRAM Kernel: 3.0-980211-SNAP compiles with dpt0. Error message: dpt 0: xxx Lost Interrupts Recovered or dpt timing out Thanks, Kingson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 16:46:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19346 for freebsd-current-outgoing; Tue, 24 Feb 1998 16:46:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA19336 for ; Tue, 24 Feb 1998 16:46:07 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #3) id 0y7Uz5-0006vY-00; Tue, 24 Feb 1998 16:46:03 -0800 Date: Tue, 24 Feb 1998 16:46:00 -0800 (PST) From: Tom To: Kingson Gunawan cc: freebsd-current@FreeBSD.ORG Subject: Re: Help needed with DPT card + Asus M/B In-Reply-To: <34F365B8.8FFF939D@excite.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Feb 1998, Kingson Gunawan wrote: > Does anybody successfully run the DPT SmartRaid4 (PW-3334UW) with ASUS > P2L97-DS? This combination keeps failing me... > > Detail: > Asus P2L97-DS dual PII-300 > 512MB SDRAM > Intel EtherExpress 100B > SB16-Vibra > Matrox Millenium 2MB/VRAM > > Kernel: 3.0-980211-SNAP compiles with dpt0. > > Error message: > > dpt 0: xxx Lost Interrupts Recovered Check IRQ settings. Is anything else on the same IRQ as the DPT controller? Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 17:05:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21504 for freebsd-current-outgoing; Tue, 24 Feb 1998 17:05:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axp5-fddi.physik.fu-berlin.de (axp5-fddi.physik.fu-berlin.de [160.45.34.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21488 for ; Tue, 24 Feb 1998 17:05:56 -0800 (PST) (envelope-from thimm@oberon.physik.fu-berlin.de) Received: from oberon.physik.fu-berlin.de (oberon.physik.fu-berlin.de [160.45.33.83]) by axp5-fddi.physik.fu-berlin.de (8.8.5/8.8.5) with ESMTP id CAA05484; Wed, 25 Feb 1998 02:05:48 +0100 (MET) Received: (from thimm@localhost) by oberon.physik.fu-berlin.de (8.8.5/8.7.1) id CAA23666; Wed, 25 Feb 1998 02:05:47 +0100 (MET) From: Axel Thimm Message-Id: <199802250105.CAA23666@oberon.physik.fu-berlin.de> Subject: Re: panic: vm_page_unwire: invalid wire count: 0 (was Re: getcwd, fork & vfork) In-Reply-To: <26932.887823159@time.cdrom.com> from "Jordan K. Hubbard" at "Feb 18, 98 09:32:39 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 25 Feb 1998 02:05:46 +0100 (MET) Cc: thimm@physik.fu-berlin.de, current@FreeBSD.ORG, Axel.Thimm@physik.fu-berlin.de 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-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, I will use send-pr from now on. I just thought that among other things this list was appropriate for fast feedback. (At least I had seen such request in the near past). Anyways I just send out a bug report about the vm system tormenting me the last three weeks, so I "take revenge" in Jordan's way :) I like the FreeBSD project and like to contribute in any way I can (currently this can only mean testing and reporting). Regards, Axel. Jordan K. Hubbard writes: > > Are my bug reports to current wanted? I neither was acknowledged in the > > last two mails nor did someone ask me not to post bug reports here :( > That's why send-pr is a better way of communicating these things. > Mails to -current get variable amounts of attention depending on how > busy folks are whereas a PR just sort of hangs around forever, > tormenting people. > > Jordan -- Axel Thimm Axel.Thimm@physik.fu-berlin.de Axel.Thimm@ifh.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 17:07:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22033 for freebsd-current-outgoing; Tue, 24 Feb 1998 17:07:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kaos.atext.com (kaos.atext.com [204.62.245.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22015 for ; Tue, 24 Feb 1998 17:07:31 -0800 (PST) (envelope-from kingson@excite.com) Received: from excite.com (batik [204.62.245.185]) by kaos.atext.com (8.8.5/8.8.5) with ESMTP id RAA09245; Tue, 24 Feb 1998 17:06:56 -0800 (PST) Message-ID: <34F36EB0.4839D6A0@excite.com> Date: Tue, 24 Feb 1998 17:06:56 -0800 From: Kingson Gunawan Reply-To: kingson@excite.com Organization: Excite Inc. X-Mailer: Mozilla 4.04 [en] (X11; U; SunOS 5.6 sun4m) MIME-Version: 1.0 To: Tom CC: freebsd-current@FreeBSD.ORG Subject: Re: Help needed with DPT card + Asus M/B References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom wrote: > > On Tue, 24 Feb 1998, Kingson Gunawan wrote: > > > Does anybody successfully run the DPT SmartRaid4 (PW-3334UW) with ASUS > > P2L97-DS? This combination keeps failing me... > > > > Detail: > > Asus P2L97-DS dual PII-300 > > 512MB SDRAM > > Intel EtherExpress 100B > > SB16-Vibra > > Matrox Millenium 2MB/VRAM > > > > Kernel: 3.0-980211-SNAP compiles with dpt0. > > > > Error message: > > > > dpt 0: xxx Lost Interrupts Recovered > > Check IRQ settings. Is anything else on the same IRQ as the DPT > controller? > > Tom Yes, in fact, I've manually set the irq's in the bios setup. This is just mighty wierd. Kingson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 17:15:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24220 for freebsd-current-outgoing; Tue, 24 Feb 1998 17:15:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA24188 for ; Tue, 24 Feb 1998 17:15:51 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #3) id 0y7VRs-0001rs-00; Tue, 24 Feb 1998 17:15:48 -0800 Date: Tue, 24 Feb 1998 17:15:45 -0800 (PST) From: Tom To: Kingson Gunawan cc: freebsd-current@FreeBSD.ORG Subject: Re: Help needed with DPT card + Asus M/B In-Reply-To: <34F36EB0.4839D6A0@excite.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Feb 1998, Kingson Gunawan wrote: > Tom wrote: > > > > On Tue, 24 Feb 1998, Kingson Gunawan wrote: > > > > > Does anybody successfully run the DPT SmartRaid4 (PW-3334UW) with ASUS > > > P2L97-DS? This combination keeps failing me... > > > > > > Detail: > > > Asus P2L97-DS dual PII-300 > > > 512MB SDRAM > > > Intel EtherExpress 100B > > > SB16-Vibra > > > Matrox Millenium 2MB/VRAM > > > > > > Kernel: 3.0-980211-SNAP compiles with dpt0. > > > > > > Error message: > > > > > > dpt 0: xxx Lost Interrupts Recovered > > > > Check IRQ settings. Is anything else on the same IRQ as the DPT > > controller? > > > > Tom > > Yes, in fact, I've manually set the irq's in the bios setup. This is > just mighty wierd. They could still be conflicting with ISA devices, like PS/2 mouse, sound, printer, serial, etc. Go into the BIOS and disable all unneeded functions (PS/2, printer, serial, IDE, etc), and remove your sound card. > Kingson Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 17:27:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27243 for freebsd-current-outgoing; Tue, 24 Feb 1998 17:27:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from EDISWITCH2.uninet.net.mx (EDISWITCH2.uninet.net.mx [200.33.150.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA27238 for ; Tue, 24 Feb 1998 17:27:53 -0800 (PST) (envelope-from eculp@ver1.telmex.net.mx) Received: from sunix (ver1-144.uninet.net.mx [200.38.135.144] (may be forged)) by EDISWITCH2.uninet.net.mx (8.8.8/8.8.8) with SMTP id TAA11099 for ; Tue, 24 Feb 1998 19:21:17 -0600 (CST) Message-ID: <34F37373.5FDA356B@ver1.telmex.net.mx> Date: Tue, 24 Feb 1998 19:27:15 -0600 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: ZIP 100 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just installed a Zip 100M Parallel port. It seems to work fine, but I get this from dmesg. vpo0: on ppbus 0 scbus0 at vpo0 bus 0 sd0 at scbus0 target 6 lun 0 sd0: type 0 removable SCSI 2 sd0: Direct-Access sd0: ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd0 could not mode sense (4). Using ficticious geometry I don't know where the ILLEGAL REQUEST is coming from or why, but since it works, I haven't worried too much :-) But, if someone does know it would be nice. The real problem is that I want to connect a parallel printer to the Zip and I assume that I will use nlpt0 which doesn`t have a device or a listing in MAKEDEV. I assume that it shouldn't be linked to lpt0, but I'm really not sure. thanks for your help ed P.D. Does this work or should I just install another parallel port? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 17:39:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28912 for freebsd-current-outgoing; Tue, 24 Feb 1998 17:39:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28906 for ; Tue, 24 Feb 1998 17:39:44 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id SAA01894 for ; Tue, 24 Feb 1998 18:39:35 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd001876; Tue Feb 24 18:39:26 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id SAA17032 for current@freebsd.org; Tue, 24 Feb 1998 18:39:26 -0700 (MST) From: Terry Lambert Message-Id: <199802250139.SAA17032@usr02.primenet.com> Subject: Add IPPROTO types to netinet/in.h per RFC 1700 To: current@FreeBSD.ORG Date: Wed, 25 Feb 1998 01:39:26 +0000 (GMT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here are patches to add the RFC 1700 missing manifest constants to the /sys/netinet/in.h file (IPPROTO_*)... http://www.freebsd.org/~terry/DIFF.IPPROTO.txt http://www.freebsd.org/~terry/DIFF.IPPROTO Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 18:00:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02413 for freebsd-current-outgoing; Tue, 24 Feb 1998 18:00:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02406 for ; Tue, 24 Feb 1998 18:00:23 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA03385 for ; Tue, 24 Feb 1998 17:54:38 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd003382; Tue Feb 24 17:54:34 1998 Message-ID: <34F378E8.2781E494@whistle.com> Date: Wed, 25 Feb 1998 09:50:32 +0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: DEVFS/SLICE and SOFT UPDATE patches. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The patches for both the DEVFS/SLICE integrations into FreeBSD-current can both be found from now on at: http://www.freebsd.org/~julian both sets of patches were compiled successfully today. I hope this forum will be easier for people to examine these projects and test them. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 18:08:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05143 for freebsd-current-outgoing; Tue, 24 Feb 1998 18:08:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05134 for ; Tue, 24 Feb 1998 18:08:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id SAA17550; Tue, 24 Feb 1998 18:06:01 -0800 (PST) Message-Id: <199802250206.SAA17550@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Edwin Culp cc: current@FreeBSD.ORG Subject: Re: ZIP 100 In-reply-to: Your message of "Tue, 24 Feb 1998 19:27:15 CST." <34F37373.5FDA356B@ver1.telmex.net.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Feb 1998 18:06:00 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just installed a Zip 100M Parallel port. It seems to work fine, > but I get this from dmesg. > > vpo0: on ppbus 0 > scbus0 at vpo0 bus 0 > sd0 at scbus0 target 6 lun 0 > sd0: type 0 removable SCSI 2 > sd0: Direct-Access > sd0: ILLEGAL REQUEST asc:24,0 Invalid field in CDB > sd0 could not mode sense (4). Using ficticious geometry > > I don't know where the ILLEGAL REQUEST is coming from or why, but > since it works, I haven't worried too much :-) But, if someone > does know it would be nice. The SCSI code asks the disk what its geometry is. Knowing the geometry is important if you want to make the disk bootable. The Zip refuses to give an answer, and because the command is not handled specially, you get a warning printed. It's harmless. > The real problem is that I want to connect a parallel printer to the > Zip and I assume that I will use nlpt0 which doesn`t have a device > or a listing in MAKEDEV. I assume that it shouldn't be linked to > lpt0, but I'm really not sure. No; the nlpt driver has the same major/minor numbers as lpt, so just print to /dev/lpt0 like you normally would. > P.D. Does this work or should I just install another parallel port? Yup. I even tested it before I committed it. YMMV, and I am always keen to hear feedback, especially if you have detailed problem reports. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 18:31:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08186 for freebsd-current-outgoing; Tue, 24 Feb 1998 18:31:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (root@sasami.jurai.net [207.31.78.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08173 for ; Tue, 24 Feb 1998 18:31:23 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id VAA23119; Tue, 24 Feb 1998 21:03:23 -0500 (EST) Date: Tue, 24 Feb 1998 21:03:23 -0500 (EST) From: "Matthew N. Dodd" To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: Add IPPROTO types to netinet/in.h per RFC 1700 In-Reply-To: <199802250139.SAA17032@usr02.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Woohoo! IPPROTO_GRE and IPPROTO_IPEIP Thanks! On Wed, 25 Feb 1998, Terry Lambert wrote: > Here are patches to add the RFC 1700 missing manifest constants to > the /sys/netinet/in.h file (IPPROTO_*)... > > http://www.freebsd.org/~terry/DIFF.IPPROTO.txt > http://www.freebsd.org/~terry/DIFF.IPPROTO /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 18:50:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10447 for freebsd-current-outgoing; Tue, 24 Feb 1998 18:50:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10438 for ; Tue, 24 Feb 1998 18:50:10 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id TAA16726; Tue, 24 Feb 1998 19:50:07 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd016717; Tue Feb 24 19:50:03 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id TAA10669; Tue, 24 Feb 1998 19:50:02 -0700 (MST) From: Terry Lambert Message-Id: <199802250250.TAA10669@usr04.primenet.com> Subject: Re: Add IPPROTO types to netinet/in.h per RFC 1700 To: winter@jurai.net (Matthew N. Dodd) Date: Wed, 25 Feb 1998 02:50:02 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: from "Matthew N. Dodd" at Feb 24, 98 09:03:23 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Woohoo! > > IPPROTO_GRE and IPPROTO_IPEIP Woohoo! Already committed, apparently, and added to my "kills" list... 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 18:52:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11115 for freebsd-current-outgoing; Tue, 24 Feb 1998 18:52:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11096 for ; Tue, 24 Feb 1998 18:52:38 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id TAA23771; Tue, 24 Feb 1998 19:52:28 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd023749; Tue Feb 24 19:52:23 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id TAA10749; Tue, 24 Feb 1998 19:52:23 -0700 (MST) From: Terry Lambert Message-Id: <199802250252.TAA10749@usr04.primenet.com> Subject: Re: DEVFS/SLICE and SOFT UPDATE patches. To: julian@whistle.com (Julian Elischer) Date: Wed, 25 Feb 1998 02:52:23 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <34F378E8.2781E494@whistle.com> from "Julian Elischer" at Feb 25, 98 09:50:32 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The patches for both the DEVFS/SLICE integrations into FreeBSD-current > can both be found from now on at: > > http://www.freebsd.org/~julian > > both sets of patches were compiled successfully today. > > I hope this forum will be easier for people to examine these > projects and test them. Use http://www.freebsd.org/~julian/ if you are using a brain-damaged browser. For some reason, the trailing "/" is important to the WWW server on FreeeBSD.org... This is a job for... Variant Symbolic Links! Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 19:05:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13409 for freebsd-current-outgoing; Tue, 24 Feb 1998 19:05:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13402 for ; Tue, 24 Feb 1998 19:05:38 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id VAA01031 for current@freebsd.org; Tue, 24 Feb 1998 21:05:33 -0600 (CST) From: Kevin Day Message-Id: <199802250305.VAA01031@home.dragondata.com> Subject: panic: getnewbuf: cannot get buffer, infinite recursion failure To: current@FreeBSD.ORG Date: Tue, 24 Feb 1998 21:05:32 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 2.2.5 NFS server, -current as of Feb 5th NFS client. On the client, I have /mnt/blah mounted. cp reallybigfile /mnt/blah/reallybig 74MB in to the 80MB file, the client panic's with: panic: getnewbuf: cannot get buffer, infinite recursion failure ddb locked up before I could do anything. It's somewhat reproduceable. I've gotta try it several times before it will panic. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 20:38:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA27604 for freebsd-current-outgoing; Tue, 24 Feb 1998 20:38:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mexcom.net (ver1-144.uninet.net.mx [200.38.135.144] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA26961 for ; Tue, 24 Feb 1998 20:34:12 -0800 (PST) (envelope-from eculp@ver1.telmex.net.mx) Received: from sunix (telmex@sunix.mexcom.net [206.103.64.3]) by ns.mexcom.net (8.8.8/8.8.7) with SMTP id WAA14527; Tue, 24 Feb 1998 22:31:18 -0600 (CST) Message-ID: <34F39ECB.39BC3394@ver1.telmex.net.mx> Date: Tue, 24 Feb 1998 22:32:11 -0600 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: Mike Smith CC: current@FreeBSD.ORG Subject: Re: ZIP 100 References: <199802250206.SAA17550@dingo.cdrom.com> <34F38A0D.DE69B35@ver1.telmex.net.mx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Final Report everything works great. Zip - Printer Thanks ed Edwin Culp wrote: > > Mike Smith wrote: > > > > > I just installed a Zip 100M Parallel port. It seems to work fine, > > > but I get this from dmesg. > > > > > > vpo0: on ppbus 0 > > > scbus0 at vpo0 bus 0 > > > sd0 at scbus0 target 6 lun 0 > > > sd0: type 0 removable SCSI 2 > > > sd0: Direct-Access > > > sd0: ILLEGAL REQUEST asc:24,0 Invalid field in CDB > > > sd0 could not mode sense (4). Using ficticious geometry > > > > > > I don't know where the ILLEGAL REQUEST is coming from or why, but > > > since it works, I haven't worried too much :-) But, if someone > > > does know it would be nice. > > > > The SCSI code asks the disk what its geometry is. Knowing the geometry > > is important if you want to make the disk bootable. The Zip refuses to > > give an answer, and because the command is not handled specially, you > > get a warning printed. It's harmless. > > > > > The real problem is that I want to connect a parallel printer to the > > > Zip and I assume that I will use nlpt0 which doesn`t have a device > > > or a listing in MAKEDEV. I assume that it shouldn't be linked to > > > lpt0, but I'm really not sure. > > > > No; the nlpt driver has the same major/minor numbers as lpt, so just > > print to /dev/lpt0 like you normally would. > > > > > P.D. Does this work or should I just install another parallel port? > > > > Yup. I even tested it before I committed it. YMMV, and I am always > > keen to hear feedback, especially if you have detailed problem reports. > > -- > > Thanks a lot, Mike. I'm going to give the printer a try and see what > happens. > I'm sure it'll work fine. > > ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 21:47:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08599 for freebsd-current-outgoing; Tue, 24 Feb 1998 21:47:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA08541 for ; Tue, 24 Feb 1998 21:47:06 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id VAA14967; Tue, 24 Feb 1998 21:46:40 -0800 (PST) To: Terry Lambert cc: julian@whistle.com (Julian Elischer), current@FreeBSD.ORG Subject: Re: DEVFS/SLICE and SOFT UPDATE patches. In-reply-to: Your message of "Wed, 25 Feb 1998 02:52:23 GMT." <199802250252.TAA10749@usr04.primenet.com> Date: Tue, 24 Feb 1998 21:46:36 -0800 Message-ID: <14962.888385596@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is a job for... Variant Symbolic Links! Shhhh! They're not ready for this yet, Doctor! :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 22:19:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17243 for freebsd-current-outgoing; Tue, 24 Feb 1998 22:19:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA17213 for ; Tue, 24 Feb 1998 22:19:33 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 25215 invoked by uid 1000); 25 Feb 1998 06:26:14 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-021598 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 24 Feb 1998 22:26:14 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Tom Subject: Re: Help needed with DPT card + Asus M/B Cc: freebsd-current@FreeBSD.ORG, Kingson Gunawan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Feb-98 Tom wrote: > > On Tue, 24 Feb 1998, Kingson Gunawan wrote: > >> Does anybody successfully run the DPT SmartRaid4 (PW-3334UW) with ASUS >> P2L97-DS? This combination keeps failing me... >> >> Detail: >> Asus P2L97-DS dual PII-300 >> 512MB SDRAM >> Intel EtherExpress 100B >> SB16-Vibra >> Matrox Millenium 2MB/VRAM >> >> Kernel: 3.0-980211-SNAP compiles with dpt0. >> >> Error message: >> >> dpt 0: xxx Lost Interrupts Recovered > > Check IRQ settings. Is anything else on the same IRQ as the DPT > controller? That is not it. Unless some other driver is stealing the PCI interrupt (which I do not know how to do with PCI). The message comes from the fact that I see the controller status register indicating an interrupt posted, but no interrupt delivered by the O/S for a whole second. There is a bit of race condition ther, so, once or twice a day is normal (Yes, I'll fix it ;-). What Kinkston is seeing is a total failure to boot. Wait! Try to disable caches on the board. Completely. It will run like a pig, but let's see if it is/not a cache coherency problem. > > Tom > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 22:30:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20539 for freebsd-current-outgoing; Tue, 24 Feb 1998 22:30:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20513 for ; Tue, 24 Feb 1998 22:30:21 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id XAA21743; Tue, 24 Feb 1998 23:30:14 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd021723; Tue Feb 24 23:30:09 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id XAA11219; Tue, 24 Feb 1998 23:30:06 -0700 (MST) From: Terry Lambert Message-Id: <199802250630.XAA11219@usr05.primenet.com> Subject: Re: DEVFS/SLICE and SOFT UPDATE patches. To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 25 Feb 1998 06:30:05 +0000 (GMT) Cc: tlambert@primenet.com, julian@whistle.com, current@FreeBSD.ORG In-Reply-To: <14962.888385596@time.cdrom.com> from "Jordan K. Hubbard" at Feb 24, 98 09:46:36 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This is a job for... Variant Symbolic Links! > > Shhhh! They're not ready for this yet, Doctor! :) Meanwhile, Aunt Martha lies at the edge of town, in a ditch... (And yes, I know that moving the environment to system calls off the proc structure plays hell with the POSIX mandated execve()...). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 24 22:55:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24402 for freebsd-current-outgoing; Tue, 24 Feb 1998 22:55:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA24393 for ; Tue, 24 Feb 1998 22:55:27 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #3) id 0y7akQ-0005iZ-00; Tue, 24 Feb 1998 22:55:18 -0800 Date: Tue, 24 Feb 1998 22:55:14 -0800 (PST) From: Tom To: Simon Shapiro cc: freebsd-current@FreeBSD.ORG, Kingson Gunawan Subject: Re: Help needed with DPT card + Asus M/B In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Feb 1998, Simon Shapiro wrote: > That is not it. Unless some other driver is stealing the PCI interrupt > (which I do not know how to do with PCI). Unless it is a silly ISA device... Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 02:43:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA21397 for freebsd-current-outgoing; Wed, 25 Feb 1998 02:43:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (root@dnttm.wave.ras.ru [194.85.104.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA21383 for ; Wed, 25 Feb 1998 02:42:57 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.8.5/8.8.5/IP-3) with UUCP id NAA13811; Wed, 25 Feb 1998 13:38:28 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.8.8/8.8.7) with ESMTP id NAA00464; Wed, 25 Feb 1998 13:46:32 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199802251046.NAA00464@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Mike Smith cc: Matthew Thyer , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: VFAT/FAT32 In-reply-to: Your message of "Tue, 24 Feb 1998 15:25:44 PST." <199802242325.PAA17023@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Feb 1998 13:46:31 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > So then I though I'd load StarOffice and try to read a Word 6 > > document. > > > > However when I clicked on the /dos directory (my C: drive mount > > point) using the "File Open" dialog box, the machine locked solid. It is a problem with interaction with the linux emulator. I have reproduced it here. So expect a fix soon. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 05:37:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA10216 for freebsd-current-outgoing; Wed, 25 Feb 1998 05:37:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tyree.iii.co.uk ([195.89.149.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA10211 for ; Wed, 25 Feb 1998 05:37:12 -0800 (PST) (envelope-from nik@iii.co.uk) From: nik@iii.co.uk Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.8/8.8.8) with ESMTP id KAA09965; Wed, 25 Feb 1998 10:16:36 GMT Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.7/8.8.7) id KAA03000; Wed, 25 Feb 1998 10:21:53 GMT Message-ID: <19980225102152.50924@iii.co.uk> Date: Wed, 25 Feb 1998 10:21:53 +0000 To: Terry Lambert Cc: current@FreeBSD.ORG Subject: Re: DEVFS/SLICE and SOFT UPDATE patches. References: <34F378E8.2781E494@whistle.com> <199802250252.TAA10749@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: <199802250252.TAA10749@usr04.primenet.com>; from Terry Lambert on Wed, Feb 25, 1998 at 02:52:23AM +0000 Organization: interactive investor Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 25, 1998 at 02:52:23AM +0000, Terry Lambert wrote: > Use http://www.freebsd.org/~julian/ if you are using a brain-damaged > browser. For some reason, the trailing "/" is important to the WWW > server on FreeeBSD.org... > > This is a job for... Variant Symbolic Links! Uh, no it isn't. It's a job for people to start writing URLs properly. If you're referring to a directory (as the URL above is) then you must include the trailing slash. Otherwise, the webserver thinks you're trying to retrieve a file of that name instead. When the web server realises that the file is not there, it will either a) Return the appropriate "File not found" code to the browser or b) Speculatively put a '/' on the end and try again. I don't think any web servers currently do (b), but I wouldn't stake my life on it. When a server responds with (a) the browser may or may not speculatively put a '/' on the end and resubmit the request. Most browsers do indeed do this. Some obviously don't, and I presume these are the 'brain damaged ones' referred to above. The overall effect is to contribute to the general slow down of the 'net, since your browser is submitting two requests to the server. Network traffic increases, browser logs are artificially inflated, servers that speculatively spawn multiple children to handle 'n' requests will kill those children earlier when they've done less useful work, and so on. We now return you to your "Ethernet vs. Token Ring" discussion. . . N -- --+==[ Nik Clayton is Just Another Perl Hacker at Interactive Investor ]==+-- . . . and relax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 06:13:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17332 for freebsd-current-outgoing; Wed, 25 Feb 1998 06:13:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.31.78.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17304 for ; Wed, 25 Feb 1998 06:12:58 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id JAA04667; Wed, 25 Feb 1998 09:12:43 -0500 (EST) Date: Wed, 25 Feb 1998 09:12:43 -0500 (EST) From: "Matthew N. Dodd" To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: Add IPPROTO types to netinet/in.h per RFC 1700 In-Reply-To: <199802250250.TAA10669@usr04.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Feb 1998, Terry Lambert wrote: > Woohoo! Already committed, apparently, and added to my "kills" list... > 8-). How about a patch against /etc/protocols too. :) /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 06:16:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18580 for freebsd-current-outgoing; Wed, 25 Feb 1998 06:16:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.com.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18572 for ; Wed, 25 Feb 1998 06:16:39 -0800 (PST) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-2-02.camtech.net.au [203.28.0.66]) by goliath.camtech.com.au (8.8.5/8.8.2) with ESMTP id AAA10857; Thu, 26 Feb 1998 00:43:17 +1030 (CST) Message-ID: <34F42776.71159A15@camtech.net.au> Date: Thu, 26 Feb 1998 00:45:18 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Mike Smith CC: "Jordan K. Hubbard" , Ollivier Robert , current@FreeBSD.ORG Subject: Re: VFAT/FAT32 References: <199802242325.PAA17023@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This crash happens every time I try to read /dos (my FAT16 mount point). Note that I usually have /dos umounted due to: matte: {34} grep dos /etc/fstab /dev/wd0s1 /dos msdos rw,noauto 0 0 matte: {35} So I am manually typing "mount /dos" as root before I run swriter3 to try and access the filesystem. Also note that it doesn't matter if its mounted "ro" or "rw". The system freezes solid every time. It is a total lock up requiring the reset button. I do have a dumb terminal and serial cable but have never tried remote dubugging as I am an X user with a modem and only two serial ports and a life! (read: Wife, kids, pet and hence not much time to look into these things). I suppose I could detach the modem and try this. A quick run down on what to do and what to look for would be good. (I have not used debuggers much....) Anyway, gobs of information follows: (dmesg output, kernel conf file and rc.conf) A few things to note: - I have most stuff statically compiled but do load linux LKM on startup. - My sound card is plug and pray (but properly configured I think... boot -c then "pnp 1 0 os enable irq0 5 drq0 1 drq1 5 port0 0x220 port1 0x330" followed by "quit") - Dont worry about the "Invalid field in CDB" on the old clunker IBM 305MB SCSI disks 'borrowed' from a RS6000 as I dont ever try/need to boot from them. - I do worry about "options CPU_DISABLE_5X86_LSSER". Should I ? - Dont worry about ccd0-3 (which aren't used) as I dont run softupdates - Dont laugh at my 50MB QUANTUM LP52S. Its from my Amiga 500!! - I do tend to have as many optimisations on as possible such as flags 0xa0ffa0ff on my IDE controllers so look at my kernel conf file carefully! ===================================================================== dmesg output ===================================================================== Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Tue Feb 24 22:38:33 CST 1998 matt@matte:/usr/src/sys/compile/MATTE Timecounter "i8254" frequency 1193182 Hz cost 2520 ns Timecounter "TSC" frequency 167046081 Hz cost 212 ns CPU: Pentium (167.05-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 50331648 (49152K bytes) avail memory = 46538752 (45448K bytes) Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.7.0 ide_pci0: rev 0x02 on pci0.7.1 ncr0: rev 0x02 int a irq 10 on pci0.8.0 scbus0 at ncr0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 1 sd0: Direct-Access 415MB (850451 512 byte sectors) scbus0 target 1 lun 0: 5.0 MB/s (200 ns, offset 8) sd1 at scbus0 target 1 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access sd1: ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd1 could not mode sense (4). Using ficticious geometry 305MB (625356 512 byte sectors) scbus0 target 2 lun 0: 5.0 MB/s (200 ns, offset 8) sd2 at scbus0 target 2 lun 0 sd2: type 0 fixed SCSI 2 sd2: Direct-Access sd2: ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd2 could not mode sense (4). Using ficticious geometry 305MB (625356 512 byte sectors) sd4 at scbus0 target 4 lun 0 sd4: type 0 fixed SCSI 2 sd4: Direct-Access sd4: 4.0 MB/s (250 ns, offset 8) 49MB (102171 512 byte sectors) vga0: rev 0x30 int a irq 12 on pci0.9.0 Probing for PnP devices: CSN 1 Vendor ID: CTL0024 [0x24008c0e] Serial 0x100a1ec0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <12 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 9 on isa ed0: address 00:00:e8:20:33:e8, type NE2000 (16 bit) lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 1204MB (2467584 sectors), 2448 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa wdc1: unit 0 (atapi): , removable, intr, iordy wcd0: 689Kb/sec, 128Kb cache, audio play, 255 volume levels, ejectable tray wcd0: no disc inside, unlocked fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at ? drq 5 on isa snd0: sbmidi0 at 0x330 on isa snd0: joy0 at 0x201 on isa joy0: joystick Intel Pentium F00F detected, installing workaround ccd0-3: Concatenated disk drivers WARNING: / was not properly dismounted. ===================================================================== kernel config file ===================================================================== # Machine with 32 Bit WD disks, ATAPI CD-ROM, SB16, NE2000 NIC # and ncr PCI SCSI. # NOTE: kernel at CTM 2722 is the last kernel before the Lite 2 merge! # $Id: MATTE,v 5.6 1998/02/24 00:46:00 CDT matt Exp $ # based on $Id: LINT,v 1.411 1998/02/21 10:11:41 eivind Exp $ # machine "i386" ident "MATTE.3261" maxusers 20 options INCLUDE_CONFIG_FILE # Include this file in kernel config kernel root on wd0 cpu "I586_CPU" options "CPU_DISABLE_5X86_LSSER" # should not be used if you use memory mapped I/O device(s). options "CPU_FASTER_5X86_FPU" #options "NO_F00F_HACK" # COMPATIBILITY OPTIONS options "COMPAT_43" # Compatible with BSD 4.3 [KEEP THIS!] options USER_LDT # Let processes manipulate their local descriptor table (needed for WINE) options SYSVSHM # Enable SYSV style shared memory options SYSVSEM # Enable SYSV style semaphores options SYSVMSG # Enable SYSV style message queues options "MD5" # Include a MD5 routine in the kernel options "VM86" # Allow processes to switch to vm86 mode (needed for doscmd) # DEBUGGING OPTIONS options DDB # Enable the kernel debugger options UCONSOLE # Allow users to grab the console options USERCONFIG # boot -c editor options VISUAL_USERCONFIG # visual boot -c editor # NETWORKING OPTIONS options INET # Internet communications protocols # Network interfaces: pseudo-device ether # Generic Ethernet pseudo-device loop # Network loopback device pseudo-device tun 1 # Tunnel driver(user process ppp) # FILESYSTEM OPTIONS # The ones I have commented out will autoload when required options FFS # Berkeley Fast Filesystem options NFS # Network Filesystem options "CD9660" # ISO 9660 Filesystem options MFS # Memory Filesystem options MSDOSFS # MSDOS Filesystem options PROCFS # Process Filesystem options NSWAPDEV=4 # Allow this many swap-devices controller pci0 controller ncr0 # My card set for termination and using IRQ 11 # SCSI DEVICE CONFIGURATION controller scbus0 at ncr0 # Base SCSI code disk sd0 at scbus0 target 0 disk sd1 at scbus0 target 1 disk sd2 at scbus0 target 2 disk sd3 at scbus0 target 3 disk sd4 at scbus0 target 4 disk sd5 at scbus0 target 5 disk sd6 at scbus0 target 6 # MISCELLANEOUS DEVICES AND OPTIONS pseudo-device pty 32 # Pseudo ttys - can go as high as 256 pseudo-device gzip # Exec gzipped a.out's pseudo-device vn # Vnode driver (turns a file into a device) pseudo-device ccd 4 # Concatenated disk driver # HARDWARE DEVICE CONFIGURATION controller isa0 # Options for `isa': options "AUTO_EOI_1" # Save 0.7-1.25 usec for each interrupt #options "AUTO_EOI_2" # ditto for slave 8259A controller pnp0 # Enable PnP support in the kernel options XSERVER # Include code for XFree86 device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options MAXCONS=12 # number of virtual consoles options SC_HISTORY_SIZE=200 # number of history buffer lines device npx0 at isa? port "IO_NPX" iosiz 0x0 flags 0x0 irq 13 vector npxintr options "CMD640" # Enable work around for CMD640 h/w bug controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xa0ffa0ff vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xa0ffa0ff vector wdintr disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 options ATAPI # Enable ATAPI support for IDE bus options ATAPI_STATIC # Don't do it as an LKM device wcd0 # IDE CD-ROM driver controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 tape ft0 at fdc0 drive 2 device lpt0 at isa? port? tty irq 7 vector lptintr #device lpt0 at isa? port? tty # polled mode BUT errors: /kernel: stray irq 7 ?, and is it TCP/IP capable in polled ? device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device ed0 at isa? port 0x300 net irq 9 iomem 0xd8000 vector edintr controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device joy0 at isa? port "IO_GAME" ===================================================================== /etc/rc.conf ===================================================================== #!/bin/sh # # This is rc.conf - a file full of useful variables that you can set # to change the default startup behavior of your system. # # All arguments must be in double or single quotes. # # $Id: rc.conf,v 1.39 1998/02/17 03:05:32 jseger Exp $ ############################################################## ### Important initial Boot-time options ##################### ############################################################## swapfile="NO" # Set to name of swapfile if aux swapfile desired. apm_enable="NO" # Set to YES if you want APM enabled. pccard_enable="NO" # Set to YES if you want to configure PCCARD devices. pccard_mem="DEFAULT" # If pccard_enable=YES, this is card memory address. pccard_ifconfig="NO" # Specialized pccard ethernet configuration (or NO). local_startup="/usr/local/etc/rc.d /usr/X11R6/etc/rc.d" # startup script dirs. local_periodic="/usr/local/etc/periodic /usr/X11R6/etc/periodic" # periodic script dirs ############################################################## ### Network configuration sub-section ###################### ############################################################## ### Basic network options: ### hostname="matte" # Set this! nisdomainname="NO" # Set to NIS domain if using NIS (or NO). firewall_enable="NO" # Set to YES to enable firewall functionality firewall_type="UNKNOWN" # Firewall type (see /etc/rc.firewall) firewall_quiet="NO" # Set to YES to suppress rule display tcp_extensions="YES" # Allow RFC1323 & RFC1644 extensions (or NO). network_interfaces="lo0" # List of network interfaces (lo0 is loopback). ifconfig_lo0="inet 127.0.0.1" # default loopback device configuration. #ifconfig_lo0_alias0="inet 127.0.0.254 netmask 0xffffffff" # Sample alias entry. ### Network daemon (miscellaneous) & NFS options: ### syslogd_enable="YES" # Run syslog daemon (or NO). syslogd_flags="" # Flags to syslogd (if enabled). inetd_enable="YES" # Run the network daemon dispatcher (or NO). inetd_flags="" # Optional flags to inetd. named_enable="NO" # Run named, the DNS server (or NO). named_program="/usr/sbin/named" # named program, in case we want bind8 instead. named_flags="-b /etc/namedb/named.boot" # Flags to named (if enabled). kerberos_server_enable="NO" # Run a kerberos master server (or NO). kadmind_server_enable="NO" # Run kadmind (or NO) -- do not run on # a slave kerberos server kerberos_stash="" # Is the kerberos master key stashed? rwhod_enable="NO" # Run the rwho daemon (or NO). amd_enable="NO" # Run amd service with $amd_flags (or NO). amd_flags="-a /net -c 1800 -k i386 -d my.domain -l syslog /host /etc/amd.map" nfs_client_enable="NO" # This host is an NFS client (or NO). nfs_client_flags="-n 4" # Flags to nfsiod (if enabled). nfs_server_enable="NO" # This host is an NFS server (or NO). nfs_server_flags="-u -t 4" # Flags to nfsd (if enabled). mountd_flags="-r" # Flags to mountd (if NFS server enabled). nfs_reserved_port_only="NO" # Provide NFS only on secure port (or NO). rpc_lockd_enable="NO" # Run NFS rpc.lockd (*broken!*) if nfs_server. rpc_statd_enable="YES" # Run NFS rpc.statd if nfs_server (or NO). portmap_enable="YES" # Run the portmapper service (or NO). portmap_flags="" # Flags to portmap (if enabled). xtend_enable="NO" # Run the X-10 power controller daemon. xtend_flags="" # Flags to xtend (if enabled). ### Network Time Services options: ### timed_enable="NO" # Run the time daemon (or NO). timed_flags="" # Flags to timed (if enabled). ntpdate_enable="NO" # Run the ntpdate to sync time (or NO). ntpdate_flags="" # Flags to ntpdate (if enabled). xntpd_enable="NO" # Run xntpd Network Time Protocol (or NO). xntpd_flags="" # Flags to xntpd (if enabled). tickadj_enable="NO" # Run tickadj (or NO). tickadj_flags="-Aq" # Flags to tickadj (if enabled). # Network Information Services (NIS) options: ### nis_client_enable="NO" # We're an NIS client (or NO). nis_client_flags="" # Flags to ypbind (if enabled). nis_ypset_enable="NO" # Run ypset at boot time (or NO). nis_ypset_flags="" # Flags to ypset (if enabled). nis_server_enable="NO" # We're an NIS server (or NO). nis_server_flags="" # Flags to ypserv (if enabled). nis_ypxfrd_enable="NO" # Run rpc.ypxfrd at boot time (or NO). nis_ypxfrd_flags="" # Flags to rpc.ypxfrd (if enabled). nis_yppasswdd_enable="NO" # Run rpc.yppasswdd at boot time (or NO). nis_yppasswdd_flags="" # Flags to rpc.yppasswdd (if enabled). ### Network routing options: ### defaultrouter="NO" # Set to default gateway (or NO). static_routes="" # Set to static route list (or leave empty). gateway_enable="NO" # Set to YES if this host will be a gateway. router_enable="NO" # Set to YES to enable a routing daemon. router="routed" # Name of routing daemon to use if enabled. router_flags="-q" # Flags for routing daemon. mrouted_enable="NO" # Do multicast routing (see /etc/mrouted.conf). mrouted_flags="" # Flags for multicast routing daemon. ipxgateway_enable="NO" # Set to YES to enable IPX routing. ipxrouted_enable="NO" # Set to YES to run the IPX routing daemon. ipxrouted_flags="" # Flags for IPX routing daemon. arpproxy_all="" # replaces obsolete kernel option ARP_PROXYALL. forward_sourceroute="NO" # do source routing (only if gateway_enable is set to "YES" accept_sourceroute="NO" # accept source routed packets to us ############################################################## ### System console options ################################# ############################################################## keymap="NO" # keymap in /usr/share/syscons/keymaps/* (or NO). keyrate="NO" # keyboard rate to: slow, normal, fast (or NO). keybell="NO" # bell to duration.pitch or normal or visual (or NO). keychange="NO" # function keys default values (or NO). cursor="NO" # cursor type {normal|blink|destructive} (or NO). scrnmap="NO" # screen map in /usr/share/syscons/scrnmaps/* (or NO). font8x16="NO" # font 8x16 from /usr/share/syscons/fonts/* (or NO). font8x14="NO" # font 8x14 from /usr/share/syscons/fonts/* (or NO). font8x8="NO" # font 8x8 from /usr/share/syscons/fonts/* (or NO). blanktime="NO" # blank time (in seconds) or "NO" to turn it off. saver="NO" # screen saver: blank/daemon/green/snake/star/NO. moused_type="NO" # See man page for rc.conf(5) for available settings. moused_port="/dev/cuaa0" # Set to your mouse port (required if mousetype set). moused_flags="" # Any additional flags to moused. ############################################################## ### Miscellaneous administrative options ################### ############################################################## cron_enable="YES" # Run the periodic job daemon. lpd_enable="NO" # Run the line printer daemon. lpd_flags="" # Flags to lpd (if enabled). sendmail_enable="NO" # Run the sendmail daemon (or NO). sendmail_flags="-bd -q30m" # -bd is pretty mandatory. dumpdev="NO" # Device name to crashdump to (if enabled). check_quotas="NO" # Check quotas (or NO). accounting_enable="NO" # Turn on process accounting (or NO). ibcs2_enable="NO" # Ibcs2 (SCO) emulation loaded at startup (or NO). linux_enable="YES" # Linux emulation loaded at startup (or NO). rand_irqs="NO" # Stir the entropy pool (like "5 11" or NO). clear_tmp_enable="NO" # Clear /tmp at startup. ldconfig_paths="/usr/lib/compat /usr/X11R6/lib /usr/local/lib" # shared library search paths ############################################################## ### Allow local configuration override at the very end here ## ############################################################## if [ -f /etc/rc.conf.local ]; then . /etc/rc.conf.local fi I hope this all helps! Thanks. Mike Smith wrote: > > Hi Matt; thanks for taking the time to play with this. > > > On a newly "made world" machine at CTM src-cur.3261 I was able to > > mount_msdos my C: drive which is a Win95 B release installation > > on a newly formatted C: partition without FAT32 (without support > > for large drives as Micky soft calls it). > > OK. > > > It looked good through Xfm with long filenames in mixed case and > > filenames with spaces in them. > > There appears to be an odd quirk where a ' character will truncate a > name when it is being retrieved. > > > So then I though I'd load StarOffice and try to read a Word 6 > > document. > > > > However when I clicked on the /dos directory (my C: drive mount > > point) using the "File Open" dialog box, the machine locked solid. > > Ouch. Can you reproduce this reliably? Do you have a serial port you > can put a serial console on and perhaps poke the system a bit there? > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 06:25:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19937 for freebsd-current-outgoing; Wed, 25 Feb 1998 06:25:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.31.78.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19929 for ; Wed, 25 Feb 1998 06:24:59 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id JAA04858; Wed, 25 Feb 1998 09:24:52 -0500 (EST) Date: Wed, 25 Feb 1998 09:24:52 -0500 (EST) From: "Matthew N. Dodd" To: Terry Lambert cc: "Jordan K. Hubbard" , julian@whistle.com, current@FreeBSD.ORG Subject: Re: DEVFS/SLICE and SOFT UPDATE patches. In-Reply-To: <199802250630.XAA11219@usr05.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Feb 1998, Terry Lambert wrote: > > > This is a job for... Variant Symbolic Links! > > > > Shhhh! They're not ready for this yet, Doctor! :) > > Meanwhile, Aunt Martha lies at the edge of town, in a ditch... > > (And yes, I know that moving the environment to system calls off the > proc structure plays hell with the POSIX mandated execve()...). I'd settle for having just a few kernel variables expanded... I still want remote links. :) /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 06:36:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23129 for freebsd-current-outgoing; Wed, 25 Feb 1998 06:36:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.com.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23091 for ; Wed, 25 Feb 1998 06:36:37 -0800 (PST) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-2-02.camtech.net.au [203.28.0.66]) by goliath.camtech.com.au (8.8.5/8.8.2) with ESMTP id AAA11171; Thu, 26 Feb 1998 00:47:15 +1030 (CST) Message-ID: <34F42864.EDDDD168@camtech.net.au> Date: Thu, 26 Feb 1998 00:49:16 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Dmitrij Tejblum CC: Mike Smith , "Jordan K. Hubbard" , Ollivier Robert , current@FreeBSD.ORG Subject: Re: VFAT/FAT32 References: <199802251046.NAA00464@tejblum.dnttm.rssi.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks Dima. I have just sent you all gobs of info on my system before I read this. Sorry! Dmitrij Tejblum wrote: > > > > So then I though I'd load StarOffice and try to read a Word 6 > > > document. > > > > > > However when I clicked on the /dos directory (my C: drive mount > > > point) using the "File Open" dialog box, the machine locked solid. > > It is a problem with interaction with the linux emulator. I have reproduced it > here. So expect a fix soon. > > Dima > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 06:48:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA26695 for freebsd-current-outgoing; Wed, 25 Feb 1998 06:48:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from marathon.tekla.fi (marathon.tekla.fi [192.98.7.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA26689 for ; Wed, 25 Feb 1998 06:48:11 -0800 (PST) (envelope-from sja@tekla.fi) Received: from poveri.tekla.fi (poveri.tekla.fi [192.98.7.19]) by marathon.tekla.fi (8.8.7/8.8.7) with SMTP id QAA23137 for ; Wed, 25 Feb 1998 16:47:34 +0200 From: Sakari Jalovaara Received: by poveri.tekla.fi; (5.65v3.2/1.1.8.2/20Aug96-0557PM) id AA01437; Wed, 25 Feb 1998 16:47:34 +0200 Date: Wed, 25 Feb 1998 16:47:34 +0200 Message-Id: <9802251447.AA01437@poveri.tekla.fi> To: freebsd-current@FreeBSD.ORG Subject: Re: New SoftUpdates test kit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some old mail: >>> syncing disks... wd0: interrupt timeout: >>> wd0: status 58 error 0 >> >> Your disk is going bad. Replace it. > > this is not always true, this can also happen if the disk has spun down due > to power managment... Seconded. Before rushing to get replacement IDE drives, try to check for spindown. Stop in BIOS setup (or whatever) before booting / after halt and wait and listen if the drive goes silent. Takes 15 minutes for me; YMMV. I see spindown on a second IDE drive; I guess the disk with rootfs is never idle long enough. Not a laptop or anything; a regular newish IDE drive (6G Fireball). I haven't changed any settings on the drive or anything; maybe auto-spindown is default on IDE nowadays? I haven't had crashes or anything due to spindown; spin-up just freezes FreeBSD solid for a couple of seconds (no mouse or keyboard response.) I've just sort of supposed it is mostly harmless... ++sja To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 07:08:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00736 for freebsd-current-outgoing; Wed, 25 Feb 1998 07:08:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from marathon.tekla.fi (marathon.tekla.fi [192.98.7.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00711 for ; Wed, 25 Feb 1998 07:08:43 -0800 (PST) (envelope-from sja@tekla.fi) Received: from poveri.tekla.fi (poveri.tekla.fi [192.98.7.19]) by marathon.tekla.fi (8.8.7/8.8.7) with SMTP id RAA23437 for ; Wed, 25 Feb 1998 17:08:05 +0200 From: Sakari Jalovaara Received: by poveri.tekla.fi; (5.65v3.2/1.1.8.2/20Aug96-0557PM) id AA29901; Wed, 25 Feb 1998 17:08:05 +0200 Date: Wed, 25 Feb 1998 17:08:05 +0200 Message-Id: <9802251508.AA29901@poveri.tekla.fi> To: freebsd-current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'd like a system where I could 'pend a commit' and have it run > through a build-test and then be committed if it passed (and no one > else had touched the files I've been working on in the meantime). Or, for a simpler system: run "rm -rf /usr/obj; make" in a loop on a dedicated box. If build fails, automatically send "tail -100 make.out" to everyone who has committed in the last few hours. Pro: a useful service for committers who can't (or can't be bothered to) make world always. Con: requires a fast-ish extra build box. May tempt folks to test their changes less "'cos the build box will do it anyway". ++sja To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 07:49:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09000 for freebsd-current-outgoing; Wed, 25 Feb 1998 07:49:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gateman.zeus.leitch.com (gateman.zeus.leitch.com [204.187.61.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08992 for ; Wed, 25 Feb 1998 07:49:11 -0800 (PST) (envelope-from tholmes@zeus.leitch.com) Received: from zeus.leitch.com (0@tap.zeus.leitch.com [204.187.61.10]) by gateman.zeus.leitch.com (8.8.5/8.7.3/1.0) with ESMTP id KAA19484; Wed, 25 Feb 1998 10:49:08 -0500 (EST) Received: from bitter.zeus.leitch.com (bitter.zeus.leitch.com [204.187.61.66]) by zeus.leitch.com (8.7.5/8.7.3/1.0) with ESMTP id KAA01436; Wed, 25 Feb 1998 10:49:03 -0500 (EST) From: Tony Holmes Received: (tholmes@localhost) by bitter.zeus.leitch.com (8.8.7/8.6.9) id KAA01357; Wed, 25 Feb 1998 10:49:03 -0500 (EST) Message-Id: <199802251549.KAA01357@bitter.zeus.leitch.com> Subject: Re: DEVFS/SLICE and SOFT UPDATE patches. In-Reply-To: <19980225102152.50924@iii.co.uk> from "nik@iii.co.uk" at "Feb 25, 98 10:21:53 am" To: nik@iii.co.uk Date: Wed, 25 Feb 1998 10:49:03 -0500 (EST) Cc: tlambert@primenet.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > b) Speculatively put a '/' on the end and try again. > > I don't think any web servers currently do (b), but I wouldn't stake my > life on it. Since the FreeBSD group wisely chose Apache, and if they are using a newer version (or even a slightly older one), there is a nice way to cover over the "brain-damaged" browsers ignorance and make things happily work using the rewrite module. The following two lines in the configuration file (after turning on the rewrite engine, etc.) will check to see if the request is a directory and append a trailing / if it is. You would need to check if the trailing / is missing in the first place as a precondition (this is ripped outta my config and I'm too tired to think through that part of the solution atm) RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^(.*)$ $1/ [L] Tony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 08:12:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11944 for freebsd-current-outgoing; Wed, 25 Feb 1998 08:12:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA11892 for ; Wed, 25 Feb 1998 08:11:59 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 3986 invoked by uid 1000); 25 Feb 1998 16:18:37 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-021598 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 25 Feb 1998 08:18:37 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Tom Subject: Re: Help needed with DPT card + Asus M/B Cc: Kingson Gunawan , freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Feb-98 Tom wrote: > > On Tue, 24 Feb 1998, Simon Shapiro wrote: > >> That is not it. Unless some other driver is stealing the PCI interrupt >> (which I do not know how to do with PCI). > > Unless it is a silly ISA device... True only if the MB allows interrupts to be shared between ISA and PCI, which it should not. Kingston reports that Win95 works on that MB, with the DPT and all. ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 09:00:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21703 for freebsd-current-outgoing; Wed, 25 Feb 1998 09:00:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA21467 for ; Wed, 25 Feb 1998 08:58:48 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #3) id 0y7k9n-0004lt-00; Wed, 25 Feb 1998 08:58:07 -0800 Date: Wed, 25 Feb 1998 08:58:06 -0800 (PST) From: Tom To: Simon Shapiro cc: Kingson Gunawan , freebsd-current@FreeBSD.ORG Subject: Re: Help needed with DPT card + Asus M/B In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Feb 1998, Simon Shapiro wrote: > On 25-Feb-98 Tom wrote: > > > > On Tue, 24 Feb 1998, Simon Shapiro wrote: > > > >> That is not it. Unless some other driver is stealing the PCI interrupt > >> (which I do not know how to do with PCI). > > > > Unless it is a silly ISA device... > > True only if the MB allows interrupts to be shared between ISA and PCI, > which it should not. Kingston reports that Win95 works on that MB, with > the DPT and all. Hmmm, but how does a motherboard know what interupts a ISA card might use? You certainly can't have ISA and PCI devices sharing the IRQ, but it is up to the operators to make sure it doesn't happen. Win95 often works great in that situation, up until you address the rogue ISA device. Or maybe it doesn't even have a driver installed for the rogue device. > ---------- > > > Sincerely Yours, > > Simon Shapiro > Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 > > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 09:28:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29505 for freebsd-current-outgoing; Wed, 25 Feb 1998 09:28:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from MindBender.serv.net (mindbender.serv.net [205.153.153.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29471 for ; Wed, 25 Feb 1998 09:28:08 -0800 (PST) (envelope-from michaelv@MindBender.serv.net) Received: from localhost.HeadCandy.com (localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.8.8/8.7.3) with SMTP id JAA25428; Wed, 25 Feb 1998 09:27:26 -0800 (PST) Message-Id: <199802251727.JAA25428@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Tom cc: Simon Shapiro , Kingson Gunawan , freebsd-current@FreeBSD.ORG Subject: Re: Help needed with DPT card + Asus M/B In-reply-to: Your message of Wed, 25 Feb 98 08:58:06 -0800. Date: Wed, 25 Feb 1998 09:27:24 -0800 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Wed, 25 Feb 1998, Simon Shapiro wrote: >> On 25-Feb-98 Tom wrote: >> > On Tue, 24 Feb 1998, Simon Shapiro wrote: >> >> That is not it. Unless some other driver is stealing the PCI interrupt >> >> (which I do not know how to do with PCI). >> > Unless it is a silly ISA device... >> True only if the MB allows interrupts to be shared between ISA and PCI, >> which it should not. Kingston reports that Win95 works on that MB, with >> the DPT and all. > Hmmm, but how does a motherboard know what interupts a ISA card might >use? You tell it. >You certainly can't have ISA and PCI devices sharing the IRQ, but it >is up to the operators to make sure it doesn't happen. Correct. Most BIOS' will let you go in and identify which IRQs are held by ISA devices. I've had to do this on a couple of my Asus boards, and things work just great afterwards. One further step I had to take on one board, where I had an ISA ethernet card (with a block of buffer RAM on it, of course), was to identify the block of buffer memory in the 640K-1MB hole so the BIOS wouldn't let anything else stomp on that memory range. ----------------------------------------------------------------------------- Michael L. VanLoon mvanloon@exmsft.com michaelv@MindBender.serv.net Contract software development for Windows NT, Windows 95 and Unix. Windows NT and Unix server development in C++ and C. --< 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... ----------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 09:44:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03964 for freebsd-current-outgoing; Wed, 25 Feb 1998 09:44:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03955 for ; Wed, 25 Feb 1998 09:44:54 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id MAA03075 for ; Wed, 25 Feb 1998 12:44:23 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Wed, 25 Feb 1998 12:44:23 -0500 (EST) From: "Alok K. Dhir" To: current@FreeBSD.ORG Subject: How? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey all - aside from being a member of this list and watching all the messages go by, how does one keep track of the changes to -current? For example, I happened to stumble upon the recent merging of the netbsd msdosfs driver into -current, which added support for FAT32 filesystems and Win95 VFAT extensions. This was something I have been waiting for for quite a while. It would be nice if there was a "CHANGELOG" or somesuch which would detail such additions, etc. Thanks... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 10:01:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07324 for freebsd-current-outgoing; Wed, 25 Feb 1998 10:01:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA07310 for ; Wed, 25 Feb 1998 10:00:59 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #3) id 0y7l8V-00028P-00; Wed, 25 Feb 1998 10:00:52 -0800 Date: Wed, 25 Feb 1998 10:00:50 -0800 (PST) From: Tom To: "Alok K. Dhir" cc: current@FreeBSD.ORG Subject: Re: How? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Feb 1998, Alok K. Dhir wrote: > > Hey all - aside from being a member of this list and watching all the > messages go by, how does one keep track of the changes to -current? > > For example, I happened to stumble upon the recent merging of the netbsd > msdosfs driver into -current, which added support for FAT32 filesystems > and Win95 VFAT extensions. This was something I have been waiting for for > quite a while. It would be nice if there was a "CHANGELOG" or somesuch > which would detail such additions, etc. There is. You can get on the cvs-commit lists, so you get messages whenever something changes. If you choose the type of change: sys, bin, etc You can also look at the logged cvs history on ftp.free.bsd.org Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 10:12:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10460 for freebsd-current-outgoing; Wed, 25 Feb 1998 10:12:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10449; Wed, 25 Feb 1998 10:12:02 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA23950; Wed, 25 Feb 1998 10:09:31 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd023947; Wed Feb 25 10:09:23 1998 Date: Wed, 25 Feb 1998 10:05:20 -0800 (PST) From: Julian Elischer To: Jonathan Hanna cc: current@FreeBSD.ORG, julian@FreeBSD.ORG Subject: Re:missing sliceio.h in devfs/slice patch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG oops.. I'll send it to you.. /* * $Id: sliceio.h,v 1.10 1997/02/22 09:45:37 peter Exp $ */ #ifndef _SYS_SLICEIO_H_ #define _SYS_SLICEIO_H_ #ifndef KERNEL #include #endif #include #define SLCTYPE_SIZE 16 #define SLCNAME_SIZE 32 struct sliceinfo { u_int64_t size; u_int32_t blocksize; char type[SLCTYPE_SIZE]; /* e.g. sd or raw*/ char hint[SLCTYPE_SIZE]; /* e.g. mbr or ""*/ char handler[SLCTYPE_SIZE]; /* e.g. mbr or "" */ char devicename[SLCNAME_SIZE]; /* e.g. sd0s1a */ }; struct subsliceinfo { struct sliceinfo wholesliceinfo; /* size of the whole slice */ int slicenumber; /* which subslice we are on */ u_int64_t offset; /* where that subslice starts */ struct sliceinfo subsliceinfo; /* info about that subslice */ }; #define SLCIOCRESET _IO('S', 0) /* reset and reprobe. */ #define SLCIOCINQ _IOR('S', 2, struct sliceinfo) /* info on container */ #define SLCIOCMOD _IOW('S', 3, struct sliceinfo) /* force container */ #define SLCIOCGETSUB _IOWR('S', 4, struct subsliceinfo) /* get sub info */ #define SLCIOCSETSUB _IOWR('S', 5, struct subsliceinfo) /* set sub info */ #endif /* !_SYS_SLICEIO_H_ */ On Tue, 24 Feb 1998, Jonathan Hanna wrote: > > Just applied you new devfs/slice patch. > I seem to be missing: sys/sliceio.h in mbr.c. > > Where can I find it? > > Thanks. > > Jonathan Hanna > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 11:09:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21918 for freebsd-current-outgoing; Wed, 25 Feb 1998 11:09:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kaos.atext.com (kaos.atext.com [204.62.245.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21913 for ; Wed, 25 Feb 1998 11:09:35 -0800 (PST) (envelope-from kingson@excite.com) Received: from excite.com (batik [204.62.245.185]) by kaos.atext.com (8.8.5/8.8.5) with ESMTP id LAA28494; Wed, 25 Feb 1998 11:08:28 -0800 (PST) Message-ID: <34F46C2D.92C55594@excite.com> Date: Wed, 25 Feb 1998 11:08:29 -0800 From: Kingson Gunawan Reply-To: kingson@excite.com Organization: Excite Inc. X-Mailer: Mozilla 4.04 [en] (X11; U; SunOS 5.6 sun4m) MIME-Version: 1.0 To: shimon@simon-shapiro.org CC: Tom , freebsd-current@FreeBSD.ORG Subject: Re: Help needed with DPT card + Asus M/B References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Simon Shapiro wrote: > > On 25-Feb-98 Tom wrote: > > > > On Tue, 24 Feb 1998, Kingson Gunawan wrote: > > > >> Does anybody successfully run the DPT SmartRaid4 (PW-3334UW) with ASUS > >> P2L97-DS? This combination keeps failing me... > >> > >> Detail: > >> Asus P2L97-DS dual PII-300 > >> 512MB SDRAM > >> Intel EtherExpress 100B > >> SB16-Vibra > >> Matrox Millenium 2MB/VRAM > >> > >> Kernel: 3.0-980211-SNAP compiles with dpt0. > >> > >> Error message: > >> > >> dpt 0: xxx Lost Interrupts Recovered > > > > Check IRQ settings. Is anything else on the same IRQ as the DPT > > controller? > > That is not it. Unless some other driver is stealing the PCI interrupt > (which I do not know how to do with PCI). > > The message comes from the fact that I see the controller status register > indicating an interrupt posted, but no interrupt delivered by the O/S for a > whole second. There is a bit of race condition ther, so, once or twice a > day is normal (Yes, I'll fix it ;-). > > What Kinkston is seeing is a total failure to boot. > > Wait! Try to disable caches on the board. Completely. It will run like a > pig, but let's see if it is/not a cache coherency problem. > > > > > Tom Simon, Tom, I tried the following without any success: 1. Disabling both L? caches 2. Disabling anything in the BIOS such as PS/2 mouse function, etc. 3. Assigning specific IRQ in the BIOS to my ISA card (although it is a PnP SB16 card). 4. Removing all cards other than the DPT and video card. 5. Moving DPT around to different slots. 6. Changing the m/b with another unit of the same made and model. 7. Compile the kernel with a number of DPT options on/off. DPT and Asus board simply won't cooperate. Changing the m/b to Air P6KDI makes things work instantly. I think I am about to incinerate the m/b... :-) The wierd thing is that using the DPT freebsd boot floopy from sandero, it did successfully boot up the system. Kingson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 11:28:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25183 for freebsd-current-outgoing; Wed, 25 Feb 1998 11:28:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from MindBender.serv.net (mindbender.serv.net [205.153.153.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25099 for ; Wed, 25 Feb 1998 11:27:20 -0800 (PST) (envelope-from michaelv@MindBender.serv.net) Received: from localhost.HeadCandy.com (localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.8.8/8.7.3) with SMTP id LAA26442; Wed, 25 Feb 1998 11:25:40 -0800 (PST) Message-Id: <199802251925.LAA26442@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: kingson@excite.com cc: shimon@simon-shapiro.org, Tom , freebsd-current@FreeBSD.ORG Subject: Re: Help needed with DPT card + Asus M/B In-reply-to: Your message of Wed, 25 Feb 98 11:08:29 -0800. <34F46C2D.92C55594@excite.com> Date: Wed, 25 Feb 1998 11:24:17 -0800 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Simon Shapiro wrote: >> On 25-Feb-98 Tom wrote: >> > On Tue, 24 Feb 1998, Kingson Gunawan wrote: >> >> Does anybody successfully run the DPT SmartRaid4 (PW-3334UW) with ASUS >> >> P2L97-DS? This combination keeps failing me... >> >> Asus P2L97-DS dual PII-300 >> > Check IRQ settings. Is anything else on the same IRQ as the DPT >> > controller? >> That is not it. Unless some other driver is stealing the PCI interrupt >> (which I do not know how to do with PCI). >Simon, Tom, >I tried the following without any success: > >1. Disabling both L? caches >2. Disabling anything in the BIOS such as PS/2 mouse function, etc. >3. Assigning specific IRQ in the BIOS to my ISA card (although it is a >PnP SB16 card). >4. Removing all cards other than the DPT and video card. >5. Moving DPT around to different slots. >6. Changing the m/b with another unit of the same made and model. >7. Compile the kernel with a number of DPT options on/off. > >DPT and Asus board simply won't cooperate. Changing the m/b to Air >P6KDI makes things work instantly. I think I am about to incinerate the >m/b... :-) Have you tried checking the Asus web site to see if there is a more recent BIOS with a bug fix, that you might be able to flash? Can't think of anything else to try, but I have always believed Asus motherboards to be top-notch, up 'til now. ----------------------------------------------------------------------------- Michael L. VanLoon mvanloon@exmsft.com michaelv@MindBender.serv.net Contract software development for Windows NT, Windows 95 and Unix. Windows NT and Unix server development in C++ and C. --< 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... ----------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 11:48:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28379 for freebsd-current-outgoing; Wed, 25 Feb 1998 11:48:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kaos.atext.com (kaos.atext.com [204.62.245.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28225 for ; Wed, 25 Feb 1998 11:47:07 -0800 (PST) (envelope-from kingson@excite.com) Received: from excite.com (batik [204.62.245.185]) by kaos.atext.com (8.8.5/8.8.5) with ESMTP id LAA08124; Wed, 25 Feb 1998 11:42:12 -0800 (PST) Message-ID: <34F47414.333C9D67@excite.com> Date: Wed, 25 Feb 1998 11:42:12 -0800 From: Kingson Gunawan Reply-To: kingson@excite.com Organization: Excite Inc. X-Mailer: Mozilla 4.04 [en] (X11; U; SunOS 5.6 sun4m) MIME-Version: 1.0 To: "Michael L. VanLoon -- HeadCandy.com" CC: shimon@simon-shapiro.org, Tom , freebsd-current@FreeBSD.ORG Subject: Re: Help needed with DPT card + Asus M/B References: <199802251925.LAA26442@MindBender.serv.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael L. VanLoon -- HeadCandy.com wrote: > > >Simon Shapiro wrote: > > >> On 25-Feb-98 Tom wrote: > > >> > On Tue, 24 Feb 1998, Kingson Gunawan wrote: > > >> >> Does anybody successfully run the DPT SmartRaid4 (PW-3334UW) with ASUS > >> >> P2L97-DS? This combination keeps failing me... > >> >> Asus P2L97-DS dual PII-300 > > >> > Check IRQ settings. Is anything else on the same IRQ as the DPT > >> > controller? > > >> That is not it. Unless some other driver is stealing the PCI interrupt > >> (which I do not know how to do with PCI). > > >Simon, Tom, > >I tried the following without any success: > > > >1. Disabling both L? caches > >2. Disabling anything in the BIOS such as PS/2 mouse function, etc. > >3. Assigning specific IRQ in the BIOS to my ISA card (although it is a > >PnP SB16 card). > >4. Removing all cards other than the DPT and video card. > >5. Moving DPT around to different slots. > >6. Changing the m/b with another unit of the same made and model. > >7. Compile the kernel with a number of DPT options on/off. > > > >DPT and Asus board simply won't cooperate. Changing the m/b to Air > >P6KDI makes things work instantly. I think I am about to incinerate the > >m/b... :-) > > Have you tried checking the Asus web site to see if there is a more > recent BIOS with a bug fix, that you might be able to flash? > > Can't think of anything else to try, but I have always believed Asus > motherboards to be top-notch, up 'til now. > I did that already. The m/b BIOS is the lastest greatest. Quite disappointed by this m/b. My experience with Asus m/b (with different controller cards) had been excellent up until now. Kingson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 12:20:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05625 for freebsd-current-outgoing; Wed, 25 Feb 1998 12:20:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05105 for ; Wed, 25 Feb 1998 12:19:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA20671; Wed, 25 Feb 1998 11:52:36 -0800 (PST) Message-Id: <199802251952.LAA20671@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Michael L. VanLoon -- HeadCandy.com" cc: kingson@excite.com, shimon@simon-shapiro.org, Tom , freebsd-current@FreeBSD.ORG Subject: Re: Help needed with DPT card + Asus M/B In-reply-to: Your message of "Wed, 25 Feb 1998 11:24:17 PST." <199802251925.LAA26442@MindBender.serv.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Feb 1998 11:52:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Simon, Tom, > >I tried the following without any success: > > > >1. Disabling both L? caches > >2. Disabling anything in the BIOS such as PS/2 mouse function, etc. > >3. Assigning specific IRQ in the BIOS to my ISA card (although it is a > >PnP SB16 card). > >4. Removing all cards other than the DPT and video card. > >5. Moving DPT around to different slots. > >6. Changing the m/b with another unit of the same made and model. > >7. Compile the kernel with a number of DPT options on/off. > > > >DPT and Asus board simply won't cooperate. Changing the m/b to Air > >P6KDI makes things work instantly. I think I am about to incinerate the > >m/b... :-) Have you checked to make sure that the base clock jumpers are set to 66MHz (rather than, say, 75 or 83)? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 13:55:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04097 for freebsd-current-outgoing; Wed, 25 Feb 1998 13:55:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04085 for ; Wed, 25 Feb 1998 13:55:48 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id OAA20886; Wed, 25 Feb 1998 14:55:42 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd020840; Wed Feb 25 14:55:38 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id OAA28967; Wed, 25 Feb 1998 14:55:34 -0700 (MST) From: Terry Lambert Message-Id: <199802252155.OAA28967@usr01.primenet.com> Subject: Re: DEVFS/SLICE and SOFT UPDATE patches. To: tholmes@zeus.leitch.com (Tony Holmes) Date: Wed, 25 Feb 1998 21:55:34 +0000 (GMT) Cc: nik@iii.co.uk, tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <199802251549.KAA01357@bitter.zeus.leitch.com> from "Tony Holmes" at Feb 25, 98 10:49:03 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > b) Speculatively put a '/' on the end and try again. > > > > I don't think any web servers currently do (b), but I wouldn't stake my > > life on it. > > Since the FreeBSD group wisely chose Apache, and if they are using a newer > version (or even a slightly older one), there is a nice way to cover over > the "brain-damaged" browsers ignorance and make things happily work using > the rewrite module. > > The following two lines in the configuration file (after turning on the > rewrite engine, etc.) will check to see if the request is a directory and > append a trailing / if it is. You would need to check if the trailing / is > missing in the first place as a precondition (this is ripped outta my > config and I'm too tired to think through that part of the solution atm) > > RewriteCond %{REQUEST_FILENAME} -d > RewriteRule ^(.*)$ $1/ [L] The difference is actually that the server is speculatively adding an index.html in the trailing / case, and not adding it in the non-/ case. A variant symbolic link would allow the colocation of a "username" to point to "~username/public_html/index.html". Other than a variant symbolic link (without which "username" can only point, as it does, to "~username/public_html"), the only other real option is hard links. The problem here is that (1) directory hard links are not allowed because they screw with inheritance, and (2) You have a problem relatvely rooting documentes, unless the index.html is not implied, but instead explicitly specified. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 14:50:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14902 for freebsd-current-outgoing; Wed, 25 Feb 1998 14:50:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14891 for ; Wed, 25 Feb 1998 14:50:16 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA04079 for ; Wed, 25 Feb 1998 14:42:34 -0800 (PST) Received: from UNKNOWN(), claiming to be "crab.whistle.com" via SMTP by alpo.whistle.com, id smtpd004070; Wed Feb 25 14:42:24 1998 Received: (from ambrisko@localhost) by crab.whistle.com (8.8.8/8.6.12) id OAA02224 for current@freebsd.org; Wed, 25 Feb 1998 14:39:34 -0800 (PST) From: Doug Ambrisko Message-Id: <199802252239.OAA02224@crab.whistle.com> Subject: Re: New SoftUpdates test kit In-Reply-To: <19980223083856.65231@rf900.physics.usyd.edu.au> from David Dawes at "Feb 23, 98 08:38:56 am" To: current@FreeBSD.ORG Date: Wed, 25 Feb 1998 14:39:34 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL29 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Dawes writes: | Looking through the logs, I found a few different ones, which might be | more serious(?): | | wd2: interrupt timeout: | wd2: status 58 error 1 | | wd2: interrupt timeout: | wd2: status 58 error 60 Here's some info on a related problem we've seen here. A lot of IDE disk drives do not seem to be low-level formated very well from the manufacturer. Current IDE drives are "perfect" and do sector remaping when they detect an error and are writing out new information. We discovered that many fresh IDE drives that had data just written to them would have a lot of "bit rot" on them producing various errors like above. To reduce this problem we now do a read & write pass of the entire disk before loading the drive. Then we do a checksum verification of the load. By doing this we have greatly reduced this problem. I now do this to any drive I use. Had to reload a 4G laptop drive because I skipped this step and it started to suffer "bit rot". It was not fun to re-load yet again. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 15:09:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19704 for freebsd-current-outgoing; Wed, 25 Feb 1998 15:09:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA19686 for ; Wed, 25 Feb 1998 15:09:24 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 15576 invoked by uid 1000); 25 Feb 1998 23:15:51 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-022398 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 25 Feb 1998 15:15:51 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Tom Subject: Re: Help needed with DPT card + Asus M/B Cc: freebsd-current@FreeBSD.ORG, Kingson Gunawan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Feb-98 Tom wrote: > > On Wed, 25 Feb 1998, Simon Shapiro wrote: > >> On 25-Feb-98 Tom wrote: >> > >> > On Tue, 24 Feb 1998, Simon Shapiro wrote: >> > >> >> That is not it. Unless some other driver is stealing the PCI >> >> interrupt >> >> (which I do not know how to do with PCI). >> > >> > Unless it is a silly ISA device... >> >> True only if the MB allows interrupts to be shared between ISA and PCI, >> which it should not. Kingston reports that Win95 works on that MB, with >> the DPT and all. > > Hmmm, but how does a motherboard know what interupts a ISA card might > use? You certainly can't have ISA and PCI devices sharing the IRQ, but > it > is up to the operators to make sure it doesn't happen. Most MB I am familiar with route interrupts from the ISA bus to a PCI-ISA bridge. The bridge is programmable and will not pass interrupts form ISA that it was told not to. OTOH, I amy be talking about what things should have been. I think Steve Passe (amoung others) knows the definite answer here as he has to deal with it in the APIC code. > Win95 often works great in that situation, up until you address the > rogue ISA device. Or maybe it doesn't even have a driver installed for > the rogue device. Or, the driver knows about some problem with the MB and avoids it or works around it. This is why I suggested a call to DPT. It is a free call and they know about such intractions better than I do. ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 15:12:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20327 for freebsd-current-outgoing; Wed, 25 Feb 1998 15:12:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA20295 for ; Wed, 25 Feb 1998 15:12:26 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 15730 invoked by uid 1000); 25 Feb 1998 23:18:53 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-022398 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199802251727.JAA25428@MindBender.serv.net> Date: Wed, 25 Feb 1998 15:18:53 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: "Michael L. VanLoon -- HeadCandy.com" Subject: Re: Help needed with DPT card + Asus M/B Cc: freebsd-current@FreeBSD.ORG, Kingson Gunawan , Tom Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Feb-98 Michael L. VanLoon -- HeadCandy.com wrote: ... > One further step I had to take on one board, where I had an ISA > ethernet card (with a block of buffer RAM on it, of course), was to > identify the block of buffer memory in the 640K-1MB hole so the BIOS > wouldn't let anything else stomp on that memory range. It has the added advantage of turning caching off on that area of memory, which helps too :-) ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 15:17:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21914 for freebsd-current-outgoing; Wed, 25 Feb 1998 15:17:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA21891 for ; Wed, 25 Feb 1998 15:17:30 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 15942 invoked by uid 1000); 25 Feb 1998 23:24:00 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-022398 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <34F46C2D.92C55594@excite.com> Date: Wed, 25 Feb 1998 15:24:00 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Kingson Gunawan Subject: Re: Help needed with DPT card + Asus M/B Cc: freebsd-current@FreeBSD.ORG, Tom Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Feb-98 Kingson Gunawan wrote: ... > 1. Disabling both L? caches > 2. Disabling anything in the BIOS such as PS/2 mouse function, etc. > 3. Assigning specific IRQ in the BIOS to my ISA card (although it is a > PnP SB16 card). > 4. Removing all cards other than the DPT and video card. > 5. Moving DPT around to different slots. > 6. Changing the m/b with another unit of the same made and model. > 7. Compile the kernel with a number of DPT options on/off. The only thing (and it probably will not help, is to play with shadow memory setting in the 640K-1024K no-man-land of memory. > DPT and Asus board simply won't cooperate. Changing the m/b to Air > P6KDI makes things work instantly. I think I am about to incinerate the > m/b... :-) I think you should call DPT support. The call is free, the people nice and know their stuff. > The wierd thing is that using the DPT freebsd boot floopy from sandero, > it did successfully boot up the system. Well, the quality of compilation here at Simon's Garage is world known for its exceptional quality, craftsmanship and dedication to customer service :-) [ I am considering switching to marketing - much easier than actually make things work - How am i doing with meaningless superlatives so far? ] ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 15:29:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24629 for freebsd-current-outgoing; Wed, 25 Feb 1998 15:29:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24581 for ; Wed, 25 Feb 1998 15:29:14 -0800 (PST) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id JAA14540; Thu, 26 Feb 1998 09:58:57 +1030 (CST) Message-Id: <199802252328.JAA14540@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Sakari Jalovaara cc: freebsd-current@FreeBSD.ORG Subject: Re: New SoftUpdates test kit In-reply-to: Your message of "Wed, 25 Feb 1998 16:47:34 +0200." <9802251447.AA01437@poveri.tekla.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 26 Feb 1998 09:58:56 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > this is not always true, this can also happen if the disk has spun down due > > to power managment... > Seconded. Before rushing to get replacement IDE drives, try to check > for spindown. Stop in BIOS setup (or whatever) before booting / after > halt and wait and listen if the drive goes silent. Takes 15 minutes > for me; YMMV. Hmm.. only one of my drives ever does this.. Its the damaged one =) It shuts down after about 5 minutes of idleness :-/ > I haven't had crashes or anything due to spindown; spin-up just > freezes FreeBSD solid for a couple of seconds (no mouse or keyboard > response.) I've just sort of supposed it is mostly harmless... It doesn't freeze it under current, it blocks disk access instead.. (much better IMHO :) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 15:54:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29558 for freebsd-current-outgoing; Wed, 25 Feb 1998 15:54:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29553 for ; Wed, 25 Feb 1998 15:54:30 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.4) with UUCP id XAA05831; Wed, 25 Feb 1998 23:52:58 GMT Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 25 Feb 1998 23:12:07 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <34F2A9F0.E41A7227@camtech.net.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 25 Feb 1998 23:13:51 +0000 To: current@FreeBSD.ORG From: Bob Bishop Subject: Re: Build still broken - NOT! - Oh yes it is (was) Cc: Matthew Thyer Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:07 am +0000 24/2/98, Matthew Thyer wrote: >I have no trouble with "make world" at CTM src-cur.3261 >[etc] Put it down to pilot error if you like. I eventually discovered that at some time since 15/10/97 a copy of the ufs subtree had mysteriously appeared in my /usr/src/include. The only thing odd about my system is that /usr/src and /usr/obj are symbolic links; I haven't been fiddling with the tree. Anyway, I reconstituted the tree from scratch and it builds OK now. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 16:09:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03517 for freebsd-current-outgoing; Wed, 25 Feb 1998 16:09:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kaos.atext.com (kaos.atext.com [204.62.245.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03507 for ; Wed, 25 Feb 1998 16:09:47 -0800 (PST) (envelope-from kingson@excite.com) Received: from excite.com (batik [204.62.245.185]) by kaos.atext.com (8.8.5/8.8.5) with ESMTP id QAA07184; Wed, 25 Feb 1998 16:08:11 -0800 (PST) Message-ID: <34F4B26D.1A55EFD6@excite.com> Date: Wed, 25 Feb 1998 16:08:13 -0800 From: Kingson Gunawan Reply-To: kingson@excite.com Organization: Excite Inc. X-Mailer: Mozilla 4.04 [en] (X11; U; SunOS 5.6 sun4m) MIME-Version: 1.0 To: shimon@simon-shapiro.org CC: "Michael L. VanLoon -- HeadCandy.com" , freebsd-current@FreeBSD.ORG, Tom Subject: Re: Help needed with DPT card + Asus M/B References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My vendor had just stopped by and replace the m/b with Intel's. It works like a charm... :-) Oh well, it is solved, although in a completely different way. Thanks for you time you guys put into this. Kingson Simon Shapiro wrote: > > On 25-Feb-98 Michael L. VanLoon -- HeadCandy.com wrote: > ... > > One further step I had to take on one board, where I had an ISA > > ethernet card (with a block of buffer RAM on it, of course), was to > > identify the block of buffer memory in the 640K-1MB hole so the BIOS > > wouldn't let anything else stomp on that memory range. > > It has the added advantage of turning caching off on that area of memory, > which helps too :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 16:13:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04663 for freebsd-current-outgoing; Wed, 25 Feb 1998 16:13:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04649 for ; Wed, 25 Feb 1998 16:13:54 -0800 (PST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id KAA27556; Thu, 26 Feb 1998 10:34:44 +1030 (CST) Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id FVHRA4MB; Thu, 26 Feb 1998 10:35:02 +1030 Received: from eddie.dsto.defence.gov.au (eddie.dsto.defence.gov.au [131.185.2.111]) by fang.dsto.defence.gov.au (8.8.5/8.8.5) with ESMTP id KAA26988; Thu, 26 Feb 1998 10:35:25 +1030 (CST) Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.8/8.8.5) with ESMTP id KAA01193; Thu, 26 Feb 1998 10:35:25 +1030 (CST) Message-ID: <34F4B1C5.2DAE18EA@dsto.defence.gov.au> Date: Thu, 26 Feb 1998 10:35:25 +1030 From: Matthew Thyer Organization: Defence Science Technology Organisation X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Bob Bishop , current@FreeBSD.ORG Subject: Re: Build still broken - NOT! - Oh yes it is (was) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My /usr/src and /usr/obj are also symbolic links. About the only thing I can think of is maybe you are an NFS client ?? FreeBSD-CURRENT NFS is very bad currently. I have not been able to "make world" at work with /usr/src and /usr/obj NFS mounted. I had to find enough local space to get it done and then it was fine. Bob Bishop wrote: > > At 11:07 am +0000 24/2/98, Matthew Thyer wrote: > >I have no trouble with "make world" at CTM src-cur.3261 > >[etc] > > Put it down to pilot error if you like. I eventually discovered that at > some time since 15/10/97 a copy of the ufs subtree had mysteriously > appeared in my /usr/src/include. The only thing odd about my system is that > /usr/src and /usr/obj are symbolic links; I haven't been fiddling with the > tree. > > Anyway, I reconstituted the tree from scratch and it builds OK now. > > -- > Bob Bishop (0118) 977 4017 international code +44 118 > rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 16:40:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10137 for freebsd-current-outgoing; Wed, 25 Feb 1998 16:40:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fang.cs.sunyit.edu (root@fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10017 for ; Wed, 25 Feb 1998 16:39:53 -0800 (PST) (envelope-from perlsta@cs.sunyit.edu) Received: from win95.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by fang.cs.sunyit.edu (8.8.5/8.7.3) with SMTP id UAA08620; Wed, 25 Feb 1998 20:39:34 GMT Message-ID: <036d01bd424e$3c963080$0600a8c0@win95.local.sunyit.edu> From: "Alfred Perlstein" To: "Matthew Thyer" , "Bob Bishop" , Subject: Re: Build still broken - NOT! - Oh yes it is (was) Date: Wed, 25 Feb 1998 19:34:01 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i run my 3.0 workstation as a NFS server to a 2.2-stable machine very trivial load, but i have seen no problems with using it to share my X11 dir and my jdk dirs.. are you saying the 3.0 NFS client code is broken? -Alfred -----Original Message----- From: Matthew Thyer To: Bob Bishop ; current@FreeBSD.ORG Date: Wednesday, February 25, 1998 3:21 PM Subject: Re: Build still broken - NOT! - Oh yes it is (was) >My /usr/src and /usr/obj are also symbolic links. > >About the only thing I can think of is maybe you are an NFS >client ?? > >FreeBSD-CURRENT NFS is very bad currently. > >I have not been able to "make world" at work with /usr/src and >/usr/obj NFS mounted. I had to find enough local space to get >it done and then it was fine. > > >Bob Bishop wrote: >> >> At 11:07 am +0000 24/2/98, Matthew Thyer wrote: >> >I have no trouble with "make world" at CTM src-cur.3261 >> >[etc] >> >> Put it down to pilot error if you like. I eventually discovered that at >> some time since 15/10/97 a copy of the ufs subtree had mysteriously >> appeared in my /usr/src/include. The only thing odd about my system is that >> /usr/src and /usr/obj are symbolic links; I haven't been fiddling with the >> tree. >> >> Anyway, I reconstituted the tree from scratch and it builds OK now. >> >> -- >> Bob Bishop (0118) 977 4017 international code +44 118 >> rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-current" in the body of the message > >-- > Matthew Thyer Phone: +61 8 8259 7249 > Corporate Information Systems Fax: +61 8 8259 5537 > Defence Science and Technology Organisation, Salisbury > PO Box 1500 Salisbury South Australia 5108 > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 16:40:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10384 for freebsd-current-outgoing; Wed, 25 Feb 1998 16:40:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arh0300.urh.uiuc.edu (arh0300.urh.uiuc.edu [130.126.72.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10331 for ; Wed, 25 Feb 1998 16:40:48 -0800 (PST) (envelope-from dannyman@arh0300.urh.uiuc.edu) Received: (from dannyman@localhost) by arh0300.urh.uiuc.edu (8.8.8/8.8.5) id SAA26318; Wed, 25 Feb 1998 18:40:48 -0600 (CST) Message-ID: <19980225184048.54707@urh.uiuc.edu> Date: Wed, 25 Feb 1998 18:40:48 -0600 From: dannyman To: freebsd-current@FreeBSD.ORG Subject: qcam in kernel - build died Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i X-Loop: djhoward@uiuc.edu X-URL: http://www.uiuc.edu/ph/www/djhoward/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. I noticed the QuickCam support was recently pulled. That's cool since it didn't work. When I went to compile my new kernel, it config'ed just fine, but then the compiling failed because it was trying to hit the quickcam stuff somewhere. I commented out the qcam stuff and everything worked fine. I'm just wondering if maybe config should be complaining about qcam being missing, instead of the build failing. Maybe someone overlooked something, or maybe things are s'posed to work this way, I just figured I'd call a head's up. :) dan -- //Dan -=- This message brought to you by djhoward@uiuc.edu -=- \\/yori -=- Information - http://www.uiuc.edu/ph/www/djhoward/ -=- aiokomete -=- Our Honored Symbol deserves an Honorable Retirement To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 16:56:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14762 for freebsd-current-outgoing; Wed, 25 Feb 1998 16:56:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14740 for ; Wed, 25 Feb 1998 16:56:21 -0800 (PST) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA15239; Thu, 26 Feb 1998 11:26:09 +1030 (CST) Message-Id: <199802260056.LAA15239@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: dannyman cc: freebsd-current@FreeBSD.ORG Subject: Re: qcam in kernel - build died In-reply-to: Your message of "Wed, 25 Feb 1998 18:40:48 MDT." <19980225184048.54707@urh.uiuc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 26 Feb 1998 11:26:08 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I noticed the QuickCam support was recently pulled. That's cool since it > didn't work. Arggh!! Why? Lots of things don't work and they are still in the kernel.. --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 17:18:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18560 for freebsd-current-outgoing; Wed, 25 Feb 1998 17:18:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arh0300.urh.uiuc.edu (arh0300.urh.uiuc.edu [130.126.72.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18543 for ; Wed, 25 Feb 1998 17:18:14 -0800 (PST) (envelope-from dannyman@arh0300.urh.uiuc.edu) Received: (from dannyman@localhost) by arh0300.urh.uiuc.edu (8.8.8/8.8.5) id TAA03582; Wed, 25 Feb 1998 19:18:09 -0600 (CST) Message-ID: <19980225191809.25089@urh.uiuc.edu> Date: Wed, 25 Feb 1998 19:18:09 -0600 From: dannyman To: "Daniel O'Connor" Cc: freebsd-current@FreeBSD.ORG Subject: Re: qcam in kernel - build died References: <19980225184048.54707@urh.uiuc.edu> <199802260056.LAA15239@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199802260056.LAA15239@cain.gsoft.com.au>; from Daniel O'Connor on Thu, Feb 26, 1998 at 11:26:08AM +1030 X-Loop: djhoward@uiuc.edu X-URL: http://www.uiuc.edu/ph/www/djhoward/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 26, 1998 at 11:26:08AM +1030, Daniel O'Connor wrote: > > > I noticed the QuickCam support was recently pulled. That's cool since it > > didn't work. > Arggh!! Why? Lots of things don't work and they are still in the kernel.. Maybe someone was cleaning house, or whomever was responsible fot it in hte first place gave it up. *shrug* Neat idea. I reckon if it is ever fixed and useful someone 'll put it back? -- //Dan -=- This message brought to you by djhoward@uiuc.edu -=- \\/yori -=- Information - http://www.uiuc.edu/ph/www/djhoward/ -=- aiokomete -=- Our Honored Symbol deserves an Honorable Retirement To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 17:32:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20988 for freebsd-current-outgoing; Wed, 25 Feb 1998 17:32:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20979 for ; Wed, 25 Feb 1998 17:32:30 -0800 (PST) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id MAA15522; Thu, 26 Feb 1998 12:02:14 +1030 (CST) Message-Id: <199802260132.MAA15522@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: dannyman cc: "Daniel O'Connor" , freebsd-current@FreeBSD.ORG Subject: Re: qcam in kernel - build died In-reply-to: Your message of "Wed, 25 Feb 1998 19:18:09 MDT." <19980225191809.25089@urh.uiuc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 26 Feb 1998 12:02:13 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Arggh!! Why? Lots of things don't work and they are still in the kernel.. > Maybe someone was cleaning house, or whomever was responsible fot it in hte > first place gave it up. *shrug* Yeah, but this _is_ current :) > Neat idea. I reckon if it is ever fixed and useful someone 'll put it back? The only problem is that it won't get looked at, so it won't be fixed.. Not that I have a qcam, but nonetheless =) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 17:49:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24043 for freebsd-current-outgoing; Wed, 25 Feb 1998 17:49:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24038 for ; Wed, 25 Feb 1998 17:49:01 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id RAA21108; Wed, 25 Feb 1998 17:48:28 -0800 (PST) To: "Daniel O'Connor" cc: dannyman , freebsd-current@FreeBSD.ORG Subject: Re: qcam in kernel - build died In-reply-to: Your message of "Thu, 26 Feb 1998 11:26:08 +1030." <199802260056.LAA15239@cain.gsoft.com.au> Date: Wed, 25 Feb 1998 17:48:28 -0800 Message-ID: <21104.888457708@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I noticed the QuickCam support was recently pulled. That's cool since it > > didn't work. > Arggh!! Why? Lots of things don't work and they are still in the kernel.. The original author, Paul Traina, indicated that it was badly bitrotted and he no longer wished to support it. Since nobody else seemed to be looking after it either (the QuickCam VC has been out for months and nobody has updated the driver to deal with it), Mike deemed it best to simply kill it. That said, there *was* a certain degree of outcry over the decision despite the fact that the "kill it" request came from the author himself, and I believe that the current plan is to update / enhance the usermode utilities to deal better with the QC and give the yelling folks equivalent (or better) functionality. One big advantage of putting the driver in usermode is that it doesn't drag down your interactive performance anywhere near as much while using the camera. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 18:57:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07965 for freebsd-current-outgoing; Wed, 25 Feb 1998 18:57:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (root@lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07959 for ; Wed, 25 Feb 1998 18:57:50 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (markham.southpeak.com [192.58.185.8]) by lamb.sas.com (8.8.7/8.8.7) with SMTP id VAA04499 for ; Wed, 25 Feb 1998 21:57:43 -0500 (EST) Received: from iluvatar.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA12271; Wed, 25 Feb 1998 21:57:43 -0500 From: "John W. DeBoskey" Received: by iluvatar.unx.sas.com (5.65c/SAS/Generic 9.01/3-26-93) id AA06409; Wed, 25 Feb 1998 21:57:42 -0500 Message-Id: <199802260257.AA06409@iluvatar.unx.sas.com> Subject: vfs_bio.c/vfs_page_set_valid() NFS bug (and fix) To: freebsd-current@FreeBSD.ORG Date: Wed, 25 Feb 1998 21:57:42 -0500 (EST) Cc: jwd@unx.sas.com (John W. DeBoskey) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Please commit the following patch to vfs_bio.c/vfs_page_set_valid(). * $Id: vfs_bio.c,v 1.151 1998/02/11 20:06:48 dg Exp $ # diff vfs_bio.c.orig vfs_bio.c 2127c2127 < ev = off + (bp->b_validend & ~(DEV_BSIZE - 1)); --- > ev = off + ((bp->b_validend + DEV_BSIZE - 1) & ~(DEV_BSIZE - 1)); Due to the incorrect (trunc'ing) of ev, no partial block caching is done for NFS based files. ie: A file of 16385 bytes will have the 1st 16k correctly cached, but the single byte of data will always be dumped, thus forcing a readrpc to always be executed. The above has been tested and works correctly. I also beleive that 'sv' is incorrectly calculated, and should be done as a trunc (like ev was). sv = off + ((bp->b_validoff + DEV_BSIZE - 1) & ~(DEV_BSIZE - 1)); should be: sv = off + (bp->b_validoff & ~(DEV_BSIZE - 1)); I have not tested this out though with a physical gdb -k session and an appropriate test program. Your comments are welcome. Summary: sv should be trunc'd to the next lower DEV_BSIZE boundary. ev should be rounded up to the next higher DEV_BSIZE boundary. This causes a major performance boost for nfs mounted system builds. Thanks, John ps: Now to work on the unrequired lookup & attr calls. pss: I beleive that there are some bugs in either nfsstat or the actual data collection scheme. nfsstat is supplying information that doesn't match what I'm getting with my sniffer. I trust the sniffer. Comments? -- jwd@unx.sas.com (w) John W. De Boskey (919) 677-8000 x6915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 19:09:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09391 for freebsd-current-outgoing; Wed, 25 Feb 1998 19:09:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09386 for ; Wed, 25 Feb 1998 19:09:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id TAA22064; Wed, 25 Feb 1998 19:06:20 -0800 (PST) Message-Id: <199802260306.TAA22064@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jordan K. Hubbard" cc: "Daniel O'Connor" , dannyman , freebsd-current@FreeBSD.ORG Subject: Re: qcam in kernel - build died In-reply-to: Your message of "Wed, 25 Feb 1998 17:48:28 PST." <21104.888457708@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Feb 1998 19:06:20 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > That said, there *was* a certain degree of outcry over the decision > despite the fact that the "kill it" request came from the author > himself, What I found most amusing about this was that the cry came from the anti-bloat heartland. Whoever would have thought that they would use something so inefficient and frivolous? > and I believe that the current plan is to update / enhance > the usermode utilities to deal better with the QC and give the yelling > folks equivalent (or better) functionality. One big advantage of > putting the driver in usermode is that it doesn't drag down your > interactive performance anywhere near as much while using the camera. In fact, I was already in receipt of an offer from what appears to be a completely serious volunteer who has indicated a desire to ensure that all of the QC models are supported. This will almost certainly be done in userspace, either with the ppi(4) interface or using direct port I/O. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 19:11:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09975 for freebsd-current-outgoing; Wed, 25 Feb 1998 19:11:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09914; Wed, 25 Feb 1998 19:11:01 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA06034; Thu, 26 Feb 1998 14:05:42 +1100 Date: Thu, 26 Feb 1998 14:05:42 +1100 From: Bruce Evans Message-Id: <199802260305.OAA06034@godzilla.zeta.org.au> To: ache@nagual.pp.ru, current@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Re: more about adjkerntz & calcru negative time Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 27 root 18 0 204K 20K pause ??? 0.00% 0.00% adjkerntz > ^^^ time column from top > >What about resetting process time fields when process itself resets time >backwards? The time column shows time used, so setting the time of day shouldn't affect it. The bug that caused negative time used should be fixed now (except possibly for rounding errors). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 19:15:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11350 for freebsd-current-outgoing; Wed, 25 Feb 1998 19:15:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA11325 for ; Wed, 25 Feb 1998 19:15:26 -0800 (PST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id NAA26773; Thu, 26 Feb 1998 13:44:15 +1030 (CST) Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id FVHRAXJZ; Thu, 26 Feb 1998 13:44:31 +1030 Received: from eddie.dsto.defence.gov.au (eddie.dsto.defence.gov.au [131.185.2.111]) by fang.dsto.defence.gov.au (8.8.5/8.8.5) with ESMTP id NAA30569; Thu, 26 Feb 1998 13:44:53 +1030 (CST) Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.8/8.8.5) with ESMTP id NAA01430; Thu, 26 Feb 1998 13:44:53 +1030 (CST) Message-ID: <34F4DE2C.D51E404E@dsto.defence.gov.au> Date: Thu, 26 Feb 1998 13:44:52 +1030 From: Matthew Thyer Organization: Defence Science Technology Organisation X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Alfred Perlstein CC: current@FreeBSD.ORG Subject: Re: Build still broken - NOT! - Oh yes it is (was) References: <036d01bd424e$3c963080$0600a8c0@win95.local.sunyit.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, NFS client under -CURRENT has some problems. I run a 3.0-CURRENT system which is an NFS client of a Solaris 2.5.1 system. I have /usr/ports, /usr/src, /usr/obj and /usr/CTM (where I store my CTM deltas) NFS mounted from the Solaris box. (As you can see I'm trying to run FreeBSD in less than 500MB of disk space!!). With /usr/src and /usr/obj NFS mounted I have not been able to "make world". It usually fails when my log file of the make world output gets to about 1MB (7MB is a the output of "make world" with NOTCL). The freebsd-current list has mentioned several times that there are problems with both NFS client and server. I believe that Terry recently made some changes to the NFS server code so maybe thats not so bad. I read the cvs-all and freebsd-current list and am waiting for a mega commit that fixes NFS! - I'm not holding my breath though 8-) Possibly some of the problems I have seen (corruption of files) are related to the recent VM instability which seems to be almost fixed, so maybe I should try another NFS mounted make world. Comments from others ?? Alfred Perlstein wrote: > > i run my 3.0 workstation as a NFS server to a 2.2-stable machine very > trivial load, but i have seen no problems with using it to share my X11 dir > and my jdk dirs.. > > are you saying the 3.0 NFS client code is broken? > > -Alfred > > -----Original Message----- > From: Matthew Thyer > To: Bob Bishop ; current@FreeBSD.ORG > Date: Wednesday, February 25, 1998 3:21 PM > Subject: Re: Build still broken - NOT! - Oh yes it is (was) > > >My /usr/src and /usr/obj are also symbolic links. > > > >About the only thing I can think of is maybe you are an NFS > >client ?? > > > >FreeBSD-CURRENT NFS is very bad currently. > > > >I have not been able to "make world" at work with /usr/src and > >/usr/obj NFS mounted. I had to find enough local space to get > >it done and then it was fine. > > > > > >Bob Bishop wrote: > >> > >> At 11:07 am +0000 24/2/98, Matthew Thyer wrote: > >> >I have no trouble with "make world" at CTM src-cur.3261 > >> >[etc] > >> > >> Put it down to pilot error if you like. I eventually discovered that at > >> some time since 15/10/97 a copy of the ufs subtree had mysteriously > >> appeared in my /usr/src/include. The only thing odd about my system is > that > >> /usr/src and /usr/obj are symbolic links; I haven't been fiddling with > the > >> tree. > >> > >> Anyway, I reconstituted the tree from scratch and it builds OK now. > >> > >> -- > >> Bob Bishop (0118) 977 4017 international code +44 118 > >> rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK > >> > >> To Unsubscribe: send mail to majordomo@FreeBSD.org > >> with "unsubscribe freebsd-current" in the body of the message > > > >-- > > Matthew Thyer Phone: +61 8 8259 7249 > > Corporate Information Systems Fax: +61 8 8259 5537 > > Defence Science and Technology Organisation, Salisbury > > PO Box 1500 Salisbury South Australia 5108 > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-current" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 19:17:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11821 for freebsd-current-outgoing; Wed, 25 Feb 1998 19:17:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (root@lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA11804 for ; Wed, 25 Feb 1998 19:17:03 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (markham.southpeak.com [192.58.185.8]) by lamb.sas.com (8.8.7/8.8.7) with SMTP id WAA06747 for ; Wed, 25 Feb 1998 22:16:55 -0500 (EST) Received: from iluvatar.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA13646; Wed, 25 Feb 1998 22:16:54 -0500 From: "John W. DeBoskey" Received: by iluvatar.unx.sas.com (5.65c/SAS/Generic 9.01/3-26-93) id AA06482; Wed, 25 Feb 1998 22:16:54 -0500 Message-Id: <199802260316.AA06482@iluvatar.unx.sas.com> Subject: pciconf broken? To: freebsd-current@FreeBSD.ORG Date: Wed, 25 Feb 1998 22:16:54 -0500 (EST) Cc: jwd@unx.sas.com (John W. DeBoskey) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm running FreeBSD 3.0-980223-SNAP (GENERIC). When I run pciconf, I get the following: # pciconf -l pciconf: ioctl(PCIOCGETCONF): Operation not supported by device Does anyone have any info about this? Should it work? Is it a known problem? Thanks, John -- jwd@unx.sas.com (w) John W. De Boskey (919) 677-8000 x6915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 19:34:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14641 for freebsd-current-outgoing; Wed, 25 Feb 1998 19:34:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arh0300.urh.uiuc.edu (arh0300.urh.uiuc.edu [130.126.72.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14624 for ; Wed, 25 Feb 1998 19:34:05 -0800 (PST) (envelope-from dannyman@arh0300.urh.uiuc.edu) Received: (from dannyman@localhost) by arh0300.urh.uiuc.edu (8.8.8/8.8.5) id VAA01469; Wed, 25 Feb 1998 21:33:43 -0600 (CST) Message-ID: <19980225213342.27289@urh.uiuc.edu> Date: Wed, 25 Feb 1998 21:33:42 -0600 From: dannyman To: Mike Smith , "Jordan K. Hubbard" Cc: "Daniel O'Connor" , freebsd-current@FreeBSD.ORG Subject: Re: qcam in kernel - build died References: <21104.888457708@time.cdrom.com> <199802260306.TAA22064@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199802260306.TAA22064@dingo.cdrom.com>; from Mike Smith on Wed, Feb 25, 1998 at 07:06:20PM -0800 X-Loop: djhoward@uiuc.edu X-URL: http://www.uiuc.edu/ph/www/djhoward/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 25, 1998 at 07:06:20PM -0800, Mike Smith wrote: > In fact, I was already in receipt of an offer from what appears to be a > completely serious volunteer who has indicated a desire to ensure that > all of the QC models are supported. This will almost certainly be done > in userspace, either with the ppi(4) interface or using direct port I/O. Well praise be to that volunteer. http://www.dannyland.org/~dannyman/dannycam/ is somewhat lacking. :) -- //Dan -=- This message brought to you by djhoward@uiuc.edu -=- \\/yori -=- Information - http://www.uiuc.edu/ph/www/djhoward/ -=- aiokomete -=- Our Honored Symbol deserves an Honorable Retirement To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 19:55:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA22057 for freebsd-current-outgoing; Wed, 25 Feb 1998 19:55:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mttproxy2.metro.tas.com.au ([147.109.165.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA21984 for ; Wed, 25 Feb 1998 19:54:54 -0800 (PST) (envelope-from Kerry.Morse@metro.tas.com.au) Received: (from uucp@localhost) by mttproxy2.metro.tas.com.au (8.8.7/8.8.5) id OAA01148 for ; Thu, 26 Feb 1998 14:54:41 +1100 (EST) Received: from Kerrym.metro.tas.com.au(147.109.164.253), claiming to be "metro.tas.com.au" via SMTP by MTTProxy2.metro.tas.com.au, id smtpd001129; Thu Feb 26 03:54:30 1998 Message-ID: <34F4E775.4C0F1A02@metro.tas.com.au> Date: Thu, 26 Feb 1998 14:54:30 +1100 From: Kerry Morse X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 20:30:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04555 for freebsd-current-outgoing; Wed, 25 Feb 1998 20:30:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04493 for ; Wed, 25 Feb 1998 20:30:40 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id VAA01922; Wed, 25 Feb 1998 21:30:35 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd001890; Wed Feb 25 21:30:32 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id VAA23682; Wed, 25 Feb 1998 21:30:29 -0700 (MST) From: Terry Lambert Message-Id: <199802260430.VAA23682@usr07.primenet.com> Subject: Re: qcam in kernel - build died To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 26 Feb 1998 04:30:28 +0000 (GMT) Cc: doconnor@gsoft.com.au, dannyman@sasquatch.dannyland.org, freebsd-current@FreeBSD.ORG In-Reply-To: <21104.888457708@time.cdrom.com> from "Jordan K. Hubbard" at Feb 25, 98 05:48:28 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The original author, Paul Traina, indicated that it was badly > bitrotted and he no longer wished to support it. Since nobody else > seemed to be looking after it either (the QuickCam VC has been out for > months and nobody has updated the driver to deal with it), Mike deemed > it best to simply kill it. > > That said, there *was* a certain degree of outcry over the decision > despite the fact that the "kill it" request came from the author > himself, and I believe that the current plan is to update / enhance > the usermode utilities to deal better with the QC and give the yelling > folks equivalent (or better) functionality. One big advantage of > putting the driver in usermode is that it doesn't drag down your > interactive performance anywhere near as much while using the camera. Ugh. Please don't kill the NFS ccode[1] until after I've had a chance to hack on it in a nice clean framework so that it can actually be made (1) to work, and (2) to be understandable to mortals who don't have the inclination to understand why there are all these wierd upcalls all over the place [2]. [1] The NFS code meets both criteria: it is badly bitrotted, and not very well maintained. I'd maintain it, but only under some very specific conditions, namely that the house where it lives be cleaned so I can tell the difference between real client code errors, and general rat droppings on the mounting brackets where it's screwed in (ie: it must not be a second class VFS consumer, as it currently is, with system calls taking the front seat and dictating interfaces to VFS. It is a *peer*, and should be treated as such). [2] As an exercise, build a kernel, then take all of the nfs objects and link them together (ld -r -o /tmp/nfs.o nfs*.o) and then link them against nothing, and count the number of external symbols this supposed "FS module" imports from the kernel (besides "_main"). This will be your absolute minimal DDI/DKI for the current kernel VFS interface as it now sits (to save you the trouble for FFS, FFS without soft updates, and not a network consumer like NFS, depends on ***151*** symbols. My. Isn't that *special*.). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 20:49:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11685 for freebsd-current-outgoing; Wed, 25 Feb 1998 20:49:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11616 for ; Wed, 25 Feb 1998 20:49:22 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id VAA28947; Wed, 25 Feb 1998 21:49:15 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpd028936; Wed Feb 25 21:49:10 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id VAA24670; Wed, 25 Feb 1998 21:49:07 -0700 (MST) From: Terry Lambert Message-Id: <199802260449.VAA24670@usr07.primenet.com> Subject: Re: Build still broken - NOT! - Oh yes it is (was) To: Matthew.Thyer@dsto.defence.gov.au (Matthew Thyer) Date: Thu, 26 Feb 1998 04:49:07 +0000 (GMT) Cc: perlsta@cs.sunyit.edu, current@FreeBSD.ORG In-Reply-To: <34F4DE2C.D51E404E@dsto.defence.gov.au> from "Matthew Thyer" at Feb 26, 98 01:44:52 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The freebsd-current list has mentioned several times that there are > problems with both NFS client and server. I believe that Terry > recently made some changes to the NFS server code so maybe thats > not so bad. My changes are *only* in support of NFS locking, and still require RPC client calls in the kernel for NFS clients, and rpc.statd and rpc.lockd changes in user space for NFS servers. They assert the client locks locally (in a pre-coelesced state), in case the proxy assertion by the FreeBSD NFS client to the remote server fails, so they can be backed out without destroying state. A side effect of this is reduced wire traffic on a local conflict (assuming the client RPC calls were actually being made), but the main reason is so the NFS client can reassert the locks correctly after an NFS server restarts (rpc.statd needs to tell the client about the reboot). The local assertion would have the effect of making NFS client locking work, but only intra-client, not inter-client. In any case, these changes have not been committed, despite the fact that they have been run without incident by many people for two weeks now. That means other people can't start on the rpc calling/serving code without a hacked and officially unsanctified kernel. 8-(. > I read the cvs-all and freebsd-current list and am waiting for > a mega commit that fixes NFS! - I'm not holding my breath though 8-) Other NFS fixes from me (other than trivial onces that I'm sure will be commited) will have to wait until it's even possible for me to go through the thing with a fine-tooth-comb. That's not possible right now, given the way it's organized, and I'd really hesitate to add more hack-on-a-hack type "fixes" until I can remove the quotes from "fixes". 8-(. > Possibly some of the problems I have seen (corruption of files) are > related to the recent VM instability which seems to be almost fixed, > so maybe I should try another NFS mounted make world. Some of the problems are from here. Not all of them, and not the big ones that are really biting you (IMO; others may differ, and if so, I will be happy to seem them commit their fixes). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 21:00:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15108 for freebsd-current-outgoing; Wed, 25 Feb 1998 21:00:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15067 for ; Wed, 25 Feb 1998 21:00:21 -0800 (PST) (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id AAA10932; Thu, 26 Feb 1998 00:08:47 -0500 (EST) (envelope-from mark) Message-ID: <19980226000847.50861@vmunix.com> Date: Thu, 26 Feb 1998 00:08:47 -0500 From: Mark Mayo To: Matthew Thyer , Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: Build still broken - NOT! - Oh yes it is (was) References: <036d01bd424e$3c963080$0600a8c0@win95.local.sunyit.edu> <34F4DE2C.D51E404E@dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <34F4DE2C.D51E404E@dsto.defence.gov.au>; from Matthew Thyer on Thu, Feb 26, 1998 at 01:44:52PM +1030 X-Operating-System: FreeBSD 2.2.5-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 26, 1998 at 01:44:52PM +1030, Matthew Thyer wrote: > The freebsd-current list has mentioned several times that there are > problems with both NFS client and server. I believe that Terry > recently made some changes to the NFS server code so maybe thats > not so bad. > > Comments from others ?? Well, I've personaly given Terry's patches a whirl and they seemed to fix up a lot of locking problems with my 3.0-CURRENT NFSv3 cliient. I test against an Auspex filer. I haven't tried mounting both /usr/src and /usr/obj from the NFS server, but I have successfully built the world with a /usr/src NFS mounted. I don't know if Terry's patches would help you since I belive it was mostly just to implement locking correctly (I think), but it may be worth trying out for a comparison if your latest cvsup still barfs. http://www.freebsd.org/~terry for the patches. -Mark > -- > Matthew Thyer Phone: +61 8 8259 7249 > Corporate Information Systems Fax: +61 8 8259 5537 > Defence Science and Technology Organisation, Salisbury > PO Box 1500 Salisbury South Australia 5108 -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ "The problem is how do you build tools that understand your programs at a deeper semantic level." - James Gosling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 21:14:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18419 for freebsd-current-outgoing; Wed, 25 Feb 1998 21:14:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18395 for ; Wed, 25 Feb 1998 21:14:50 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id WAA14654; Wed, 25 Feb 1998 22:14:09 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id WAA24016; Wed, 25 Feb 1998 22:14:05 -0700 Date: Wed, 25 Feb 1998 22:14:05 -0700 Message-Id: <199802260514.WAA24016@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: "Jordan K. Hubbard" , "Daniel O'Connor" , dannyman , freebsd-current@FreeBSD.ORG Subject: Re: qcam in kernel - build died In-Reply-To: <199802260306.TAA22064@dingo.cdrom.com> References: <21104.888457708@time.cdrom.com> <199802260306.TAA22064@dingo.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > That said, there *was* a certain degree of outcry over the decision > > despite the fact that the "kill it" request came from the author > > himself, > > What I found most amusing about this was that the cry came from the > anti-bloat heartland. Soren, yes. Julian, no. As a member of the 'anit-bloat heartland', I applauded this removal, and I own a qcam (both a B/W and a color). Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 21:28:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20084 for freebsd-current-outgoing; Wed, 25 Feb 1998 21:28:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20047 for ; Wed, 25 Feb 1998 21:28:00 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id VAA22665; Wed, 25 Feb 1998 21:27:45 -0800 (PST) To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG Subject: Re: pciconf broken? In-reply-to: Your message of "Wed, 25 Feb 1998 22:16:54 EST." <199802260316.AA06482@iluvatar.unx.sas.com> Date: Wed, 25 Feb 1998 21:27:45 -0800 Message-ID: <22661.888470865@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When I run pciconf, I get the following: > > # pciconf -l > pciconf: ioctl(PCIOCGETCONF): Operation not supported by device Yikes! Looks like someone broke it in 3.0: 2.2.5-stable: root@time-> pciconf -l pci0:0:0: class=0x060000 card=0x00000000 chip=0x12378086 rev=0x02 hdr=0x00 pci0:7:0: class=0x060100 card=0x00000000 chip=0x70008086 rev=0x01 hdr=0x80 pci0:7:1: class=0x010180 card=0x00000000 chip=0x70108086 rev=0x00 hdr=0x00 pci0:11:0: class=0x010000 card=0x00000000 chip=0x81789004 rev=0x00 hdr=0x00 pci0:15:0: class=0x030000 card=0x00000000 chip=0x0519102b rev=0x01 hdr=0x00 pci0:17:0: class=0x020000 card=0x00000000 chip=0x00021011 rev=0x22 hdr=0x00 3.0-current: root@whisker-> pciconf -l pciconf: ioctl(PCIOCGETCONF): Operation not supported by device I lack the cojones to fix this one myself, but I did at least notice one peculiar thing: root@whisker-> ls -l /dev/pci crw-r--r-- 1 root wheel 78, 0 Aug 1 1997 /dev/pci root@whisker-> grep 78 /sys/i386/conf/majors.i386 78 gd Geometry disk Erm. Did we recycle a major number inadvertantly somewhere? :-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 21:34:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21283 for freebsd-current-outgoing; Wed, 25 Feb 1998 21:34:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21277 for ; Wed, 25 Feb 1998 21:34:30 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id VAA22721; Wed, 25 Feb 1998 21:33:55 -0800 (PST) To: Terry Lambert cc: doconnor@gsoft.com.au, dannyman@sasquatch.dannyland.org, freebsd-current@FreeBSD.ORG Subject: Re: qcam in kernel - build died In-reply-to: Your message of "Thu, 26 Feb 1998 04:30:28 GMT." <199802260430.VAA23682@usr07.primenet.com> Date: Wed, 25 Feb 1998 21:33:55 -0800 Message-ID: <22717.888471235@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ugh. Please don't kill the NFS ccode[1] until after I've had a chance > to hack on it in a nice clean framework so that it can actually be made > (1) to work, and (2) to be understandable to mortals who don't have the > inclination to understand why there are all these wierd upcalls all over > the place [2]. You want the NFS code? It's yours! That poor code has lacked a maintainer/mentor/father/... ever since Doug Rabson was scooped up by an alien spaceship with suspiciously familiar markings and forced to work on NT. And unlike the situation with the quickcam, the Linux folks have already proven that putting NFS into user space is *not* a good idea (at least not for production work) and you are safe from competition on that quarter. :-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 21:48:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA23202 for freebsd-current-outgoing; Wed, 25 Feb 1998 21:48:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA23192 for ; Wed, 25 Feb 1998 21:48:53 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id VAA22556; Wed, 25 Feb 1998 21:45:53 -0800 (PST) Message-Id: <199802260545.VAA22556@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jordan K. Hubbard" cc: Terry Lambert , doconnor@gsoft.com.au, dannyman@sasquatch.dannyland.org, freebsd-current@FreeBSD.ORG Subject: Re: qcam in kernel - build died In-reply-to: Your message of "Wed, 25 Feb 1998 21:33:55 PST." <22717.888471235@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Feb 1998 21:45:51 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Ugh. Please don't kill the NFS ccode[1] until after I've had a chance > > to hack on it in a nice clean framework so that it can actually be made > > (1) to work, and (2) to be understandable to mortals who don't have the > > inclination to understand why there are all these wierd upcalls all over > > the place [2]. > > You want the NFS code? It's yours! That poor code has lacked a > maintainer/mentor/father/... ever since Doug Rabson was scooped up by > an alien spaceship with suspiciously familiar markings and forced to > work on NT. Are we willing to wear Terry's architectural reforms? FWIW, I have one (minor) one here ready to be committed. He appears to have worked out the sort of crouton-sized bits that us mortals can deal with. (yay!) > And unlike the situation with the quickcam, the Linux folks have > already proven that putting NFS into user space is *not* a good idea > (at least not for production work) and you are safe from competition > on that quarter. :-) No fear. Can we fund a small NetApp box for him to compete with? Gotta give the guy some incentive. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 22:02:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25483 for freebsd-current-outgoing; Wed, 25 Feb 1998 22:02:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thunderdome.plutotech.com (root@thunderdome.plutotech.com [206.168.67.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25477 for ; Wed, 25 Feb 1998 22:02:13 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by thunderdome.plutotech.com (8.8.7/8.8.5) with ESMTP id XAA00308; Wed, 25 Feb 1998 23:02:11 -0700 (MST) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id XAA11787; Wed, 25 Feb 1998 23:02:09 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199802260602.XAA11787@panzer.plutotech.com> Subject: Re: pciconf broken? In-Reply-To: <199802260316.AA06482@iluvatar.unx.sas.com> from "John W. DeBoskey" at "Feb 25, 98 10:16:54 pm" To: jwd@unx.sas.com (John W. DeBoskey) Date: Wed, 25 Feb 1998 23:02:09 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG, jwd@unx.sas.com X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John W. DeBoskey wrote... > Hi, > > I'm running FreeBSD 3.0-980223-SNAP (GENERIC). > > When I run pciconf, I get the following: > > # pciconf -l > pciconf: ioctl(PCIOCGETCONF): Operation not supported by device > > > Does anyone have any info about this? Should it work? Is it > a known problem? This is a known problem. I believe it has been broken since around April 1997. I have a fixed version of that ioctl in the CAM code. It also passes back the device name (e.g. ahc, fxp, de..) and the unit number of the device in question. Stefan and I have yet to fully work out how the new version should look, so that's why it isn't in -current or anything. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 22:24:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28343 for freebsd-current-outgoing; Wed, 25 Feb 1998 22:24:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bsdx.dyn.ml.org (root@pm157-08.dialip.mich.net [35.9.15.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28327 for ; Wed, 25 Feb 1998 22:24:43 -0800 (PST) (envelope-from mcdougall@ameritech.net) Received: from ameritech.net (user1@localhost.dyn.ml.org [127.0.0.1]) by bsdx.dyn.ml.org (8.8.8/8.8.7) with ESMTP id BAA06339; Thu, 26 Feb 1998 01:24:24 -0500 (EST) (envelope-from mcdougall@ameritech.net) Message-ID: <34F50A98.276DA27B@ameritech.net> Date: Thu, 26 Feb 1998 01:24:24 -0500 From: Adam McDougall Reply-To: mcdougall@ameritech.net X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: "Kenneth D. Merry" CC: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: pciconf broken? References: <199802260602.XAA11787@panzer.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth D. Merry wrote: > John W. DeBoskey wrote... > > Hi, > > > > I'm running FreeBSD 3.0-980223-SNAP (GENERIC). > > > > When I run pciconf, I get the following: > > > > # pciconf -l > > pciconf: ioctl(PCIOCGETCONF): Operation not supported by device > > > > > > Does anyone have any info about this? Should it work? Is it > > a known problem? > > This is a known problem. I believe it has been broken since around > April 1997. Wow, april! :P > > > I have a fixed version of that ioctl in the CAM code. It also > passes back the device name (e.g. ahc, fxp, de..) and the unit number of > the device in question. > Does someone have a website about what CAM offers and such, or a readme from it, or a url to grab CAM? Thanks.I will be going scsi soon (9.1gb atlas II and dpt) > Stefan and I have yet to fully work out how the new version should > look, so that's why it isn't in -current or anything. > > Ken > -- > Kenneth Merry > ken@plutotech.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 22:29:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29381 for freebsd-current-outgoing; Wed, 25 Feb 1998 22:29:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thunderdome.plutotech.com (root@thunderdome.plutotech.com [206.168.67.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29373 for ; Wed, 25 Feb 1998 22:29:29 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by thunderdome.plutotech.com (8.8.7/8.8.5) with ESMTP id XAA00355; Wed, 25 Feb 1998 23:29:25 -0700 (MST) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id XAA12020; Wed, 25 Feb 1998 23:29:23 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199802260629.XAA12020@panzer.plutotech.com> Subject: Re: pciconf broken? In-Reply-To: <34F50A98.276DA27B@ameritech.net> from Adam McDougall at "Feb 26, 98 01:24:24 am" To: mcdougall@ameritech.net Date: Wed, 25 Feb 1998 23:29:23 -0700 (MST) Cc: ken@plutotech.com, jwd@unx.sas.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Adam McDougall wrote... > Kenneth D. Merry wrote: > > I have a fixed version of that ioctl in the CAM code. It also > > passes back the device name (e.g. ahc, fxp, de..) and the unit number of > > the device in question. > Does someone have a website about what CAM offers and such, or a readme from > it, or a url to grab CAM? Thanks.I will be going scsi soon (9.1gb atlas II and > dpt) ftp://ftp.FreeBSD.org/pub/FreeBSD/cam or ftp://ftp.kdm.org/pub/FreeBSD/cam There are readme files in both places. We're working on a new snapshot that should be out sooner or later, but I can't promise when. The sticking point is AIC-7890 support. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 22:32:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29995 for freebsd-current-outgoing; Wed, 25 Feb 1998 22:32:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29976 for ; Wed, 25 Feb 1998 22:32:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA22718; Wed, 25 Feb 1998 22:31:28 -0800 (PST) Message-Id: <199802260631.WAA22718@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG Subject: Re: vfs_bio.c/vfs_page_set_valid() NFS bug (and fix) In-reply-to: Your message of "Wed, 25 Feb 1998 21:57:42 EST." <199802260257.AA06409@iluvatar.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Feb 1998 22:31:25 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > Please commit the following patch to vfs_bio.c/vfs_page_set_valid(). > * $Id: vfs_bio.c,v 1.151 1998/02/11 20:06:48 dg Exp $ Can someone confirm/deny this for 2.2 as well? I'll do both as soon as I have an answer. > > # diff vfs_bio.c.orig vfs_bio.c > 2127c2127 > < ev = off + (bp->b_validend & ~(DEV_BSIZE - 1)); > --- > > ev = off + ((bp->b_validend + DEV_BSIZE - 1) & ~(DEV_BSIZE - 1)); > > Due to the incorrect (trunc'ing) of ev, no partial block caching > is done for NFS based files. ie: A file of 16385 bytes will have the > 1st 16k correctly cached, but the single byte of data will always > be dumped, thus forcing a readrpc to always be executed. > > The above has been tested and works correctly. > > I also beleive that 'sv' is incorrectly calculated, and should be done > as a trunc (like ev was). > > sv = off + ((bp->b_validoff + DEV_BSIZE - 1) & ~(DEV_BSIZE - 1)); > > should be: > > sv = off + (bp->b_validoff & ~(DEV_BSIZE - 1)); > > I have not tested this out though with a physical gdb -k session and an > appropriate test program. Your comments are welcome. > > Summary: sv should be trunc'd to the next lower DEV_BSIZE boundary. > ev should be rounded up to the next higher DEV_BSIZE boundary. > > This causes a major performance boost for nfs mounted system builds. > > Thanks, > John > > ps: Now to work on the unrequired lookup & attr calls. > > pss: I beleive that there are some bugs in either nfsstat or the actual > data collection scheme. nfsstat is supplying information that > doesn't match what I'm getting with my sniffer. I trust the sniffer. > Comments? > > -- > jwd@unx.sas.com (w) John W. De Boskey (919) 677-8000 x6915 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 22:49:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02429 for freebsd-current-outgoing; Wed, 25 Feb 1998 22:49:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02424 for ; Wed, 25 Feb 1998 22:49:29 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA22787 for ; Wed, 25 Feb 1998 22:48:25 -0800 (PST) Message-Id: <199802260648.WAA22787@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: current@FreeBSD.ORG Subject: REBUILD YOUR LKMS Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Feb 1998 22:48:25 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This change alters the interface consumed by filesystem LKMs, and they should be recompiled for safety's sake. Nonstandard filesystem LKMs other than those behaving like NFS may need to be modified to obtain the correct behaviour. ------- Forwarded Message From: Michael Smith Date: Wed, 25 Feb 1998 22:40:00 -0800 (PST) Message-Id: <199802260640.WAA02687@freefall.freebsd.org> To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, cvs-sys@FreeBSD.org Subject: cvs commit: src/sys/ufs/ffs ffs_vnops.c src/sys/ufs/ufs ufs_readwrite.c src/sys/vm vnode_pager.c vnode_pager.h msmith 1998/02/25 22:40:00 PST Modified files: sys/ufs/ffs ffs_vnops.c sys/ufs/ufs ufs_readwrite.c sys/vm vnode_pager.c vnode_pager.h Log: In the author's words: These diffs implement the first stage of a VOP_{GET|PUT}PAGES pushdown for local media FS's. See ffs_putpages in /sys/ufs/ufs/ufs_readwrite.c for implementation details for generic *_{get|put}pages for local media FS's. Support is trivial to add for any FS that formerly relied on the default behaviour of the vnode_pager in in EOPNOTSUPP cases (just copy the ffs_getpages() code for the FS in question's *_{get|put}pages). Obviously, it would be better if each local media FS implemented a more optimal method, instead of calling an exported interface from the /sys/vm/vnode_pager.c, but this is a necessary first step in getting the FS's to a point where they can be supplied with better implementations on a case-by-case basis. Obviously, the cd9660_putpages() can be rather trivial (since it is a read-only FS type 8-)). A slight (temporary) modification is made to print a diagnostic message in the case where the underlying filesystem attempts to engage in the previous behaviour. Failure is likely to be ungraceful. Submitted by: terry@freebsd.org (Terry Lambert) Revision Changes Path 1.43 +3 -1 src/sys/ufs/ffs/ffs_vnops.c 1.43 +15 -1 src/sys/ufs/ufs/ufs_readwrite.c 1.87 +51 -27 src/sys/vm/vnode_pager.c 1.11 +11 -1 src/sys/vm/vnode_pager.h ------- End of Forwarded Message -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 23:26:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06499 for freebsd-current-outgoing; Wed, 25 Feb 1998 23:26:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06494 for ; Wed, 25 Feb 1998 23:26:18 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id AAA15082; Thu, 26 Feb 1998 00:26:11 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd015067; Thu Feb 26 00:26:05 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id AAA26006; Thu, 26 Feb 1998 00:26:01 -0700 (MST) From: Terry Lambert Message-Id: <199802260726.AAA26006@usr08.primenet.com> Subject: Re: Build still broken - NOT! - Oh yes it is (was) To: mark@vmunix.com (Mark Mayo) Date: Thu, 26 Feb 1998 07:26:00 +0000 (GMT) Cc: Matthew.Thyer@dsto.defence.gov.au, perlsta@cs.sunyit.edu, current@FreeBSD.ORG In-Reply-To: <19980226000847.50861@vmunix.com> from "Mark Mayo" at Feb 26, 98 00:08:47 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, I've personaly given Terry's patches a whirl and they seemed > to fix up a lot of locking problems with my 3.0-CURRENT NFSv3 > cliient. I test against an Auspex filer. This is a false sense of security you're getting here. The locks are locally asserted. As I said in another posting, inter-client locking won't work (ie: you're locks will be granted, even if another NFS client thinks it holds them) because they aren't proxied to the server. I've only got one collision domain implemented here, and then only as a preparation for rpc.statd to tell me the NFS server rebooted and I need to recreate the locks (locks held by processes on files where the lock can't be reasserted should actually get ESTALE on access attempts, I think, to be safe). In other words, they are necessary, but not sufficient for a full NFS client locking fix. > I haven't tried mounting both /usr/src and /usr/obj from the NFS > server, but I have successfully built the world with a /usr/src > NFS mounted. The majority of current NFS problems are "write"-based. You wouldn't see improvement in anything but locking tests run on one client against the server (but in that case, it would look like it's working). > I don't know if Terry's patches would help you since I belive it > was mostly just to implement locking correctly (I think), but it > may be worth trying out for a comparison if your latest cvsup > still barfs. http://www.freebsd.org/~terry for the patches. The more testers, the merrier. But I'm already confident from the people who've run it so far that I'm not leaking memory, and that the lock states are held correctly before and after the coelesce, and the lock problems and the write problems are two different animals (John Dyson hinted that he may be jumping into this arena soon, now that he has time). If you commit the patches, do it for what they do, not for what they don't do. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 25 23:33:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07442 for freebsd-current-outgoing; Wed, 25 Feb 1998 23:33:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07437 for ; Wed, 25 Feb 1998 23:33:16 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.7/8.8.7) id HAA29488 for freebsd-current@freefall.cdrom.com; Thu, 26 Feb 1998 07:38:42 GMT (envelope-from kuku) Date: Thu, 26 Feb 1998 07:38:42 GMT From: Christoph Kukulies Message-Id: <199802260738.HAA29488@gilberto.physik.RWTH-Aachen.DE> To: freebsd-current@freefall.FreeBSD.org Subject: inetd realloc junk pointer Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running a 2.2.5 system with bisdn-0.97, Xaccel, qvwm, netscape communicator (the linux version I believe), all together an explosive mixture ;-). Last night I did a several hour download of a larger piece of sw through netscape and had a 20s ping running to keep the connection alive at any rate. This morning I tried to ftp from another machine to the FreeBSD machine on the local ethernet and got on the client side : inetd in realloc(): warning: junk pointer too low to make sense. That came obviously from the FreeBSD ftpd/inetd . I looked at the swap space which had only 2MB free (of 130MB). So the machine seemed to have run out of swap during the night or at least very close to the limit and the ftpd invocation might have scraped the top. Rebooting was the only resort at that time. I'm just reporting this in case someone might have an idea which realloc might have been the cause in inetd and if a more declarative message might be issued in that case. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 03:50:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA04727 for freebsd-current-outgoing; Thu, 26 Feb 1998 03:50:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA04722 for ; Thu, 26 Feb 1998 03:50:07 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.4) with UUCP id LAA10193; Thu, 26 Feb 1998 11:48:51 GMT Received: from [194.32.164.2] by seagoon.gid.co.uk; Thu, 26 Feb 1998 11:38:48 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <34F4B1C5.2DAE18EA@dsto.defence.gov.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 26 Feb 1998 11:40:27 +0000 To: Matthew Thyer From: Bob Bishop Subject: Re: Build still broken - NOT! - Oh yes it is (was) Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:05 am +0000 26/2/98, Matthew Thyer wrote: >My /usr/src and /usr/obj are also symbolic links. > >About the only thing I can think of is maybe you are an NFS >client ?? Not using NFS. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 04:33:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11080 for freebsd-current-outgoing; Thu, 26 Feb 1998 04:33:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from serv.unibest.ru (serv.unibest.ru [194.87.33.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA11004 for ; Thu, 26 Feb 1998 04:32:55 -0800 (PST) (envelope-from hole.etrust.ru!osa) Received: (qmail 4642 invoked from network); 26 Feb 1998 12:33:25 -0000 Received: from unknown (HELO hole.etrust.ru) (200.1.6.2) by serv.unibest.ru with SMTP; 26 Feb 1998 12:33:25 -0000 Received: from localhost by hole.etrust.ru with SMTP id SAA00272; (8.8.8/vak/1.9) Thu, 26 Feb 1998 18:43:20 +0300 (MSK) Date: Thu, 26 Feb 1998 18:43:20 +0300 (MSK) From: Ozz!!! To: freebsd-current@FreeBSD.ORG Subject: new kernel says : ps: proc size mismatch ( 15936 total, 676 chunks ) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ! I have a FreeBSD-3.0-980122-SNAP. I build a new kernel & install it. After reboot: # ps ax ps : proc size mismatch ( 15936 total, 676 chunks ) What can i do ? Rgdz, Ozz, osa@unibest.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 04:43:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA12572 for freebsd-current-outgoing; Thu, 26 Feb 1998 04:43:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailhost.tue.nl (mailhost.tue.nl [131.155.2.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA12561 for ; Thu, 26 Feb 1998 04:43:13 -0800 (PST) (envelope-from J.G.E.Backus@urc.tue.nl) Received: from asterix.urc.tue.nl [131.155.5.10] by mailhost.tue.nl (8.8.8) for id NAA19500 (ESMTP). Thu, 26 Feb 1998 13:43:01 +0100 (MET) Received: from jbackus@localhost by asterix.urc.tue.nl (8.8.8) id NAA00740. Thu, 26 Feb 1998 13:42:59 +0100 (MET) Message-ID: <19980226134259.09831@asterix.urc.tue.nl> Date: Thu, 26 Feb 1998 13:42:59 +0100 From: Jos Backus To: freebsd-current@FreeBSD.ORG Subject: Re: new kernel says : ps: proc size mismatch ( 15936 total, 676 chunks ) References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Ozz!!! on Thu, Feb 26, 1998 at 06:43:20PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 26, 1998 at 06:43:20PM +0300, Ozz!!! wrote: > What can i do ? Try this: # cd /usr/src/*/libkvm # make depend && make all install clean cleandepend # cd /usr/src/*/ps # make depend && make all install clean cleandepend Ps: Your From: address is broken. Cheers, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ jbackus@urc.tue.nl _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 05:11:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15247 for freebsd-current-outgoing; Thu, 26 Feb 1998 05:11:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15241 for ; Thu, 26 Feb 1998 05:11:21 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id FAA24577; Thu, 26 Feb 1998 05:11:05 -0800 (PST) To: Ozz!!! cc: freebsd-current@FreeBSD.ORG Subject: Re: new kernel says : ps: proc size mismatch ( 15936 total, 676 chunks ) In-reply-to: Your message of "Thu, 26 Feb 1998 18:43:20 +0300." Date: Thu, 26 Feb 1998 05:11:05 -0800 Message-ID: <24574.888498665@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a FreeBSD-3.0-980122-SNAP. > I build a new kernel & install it. > After reboot: Don't build just the kernel, build the world to go with it if you're not absolutely sure that the bits poked at by libkvm haven't changed (which is often). Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 05:47:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA20301 for freebsd-current-outgoing; Thu, 26 Feb 1998 05:47:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from serv.unibest.ru (serv.unibest.ru [194.87.33.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA20288 for ; Thu, 26 Feb 1998 05:46:55 -0800 (PST) (envelope-from hole.etrust.ru!unibest.ru!osa) Received: (qmail 5079 invoked from network); 26 Feb 1998 13:47:21 -0000 Received: from unknown (HELO hole.etrust.ru) (200.1.6.2) by serv.unibest.ru with SMTP; 26 Feb 1998 13:47:21 -0000 Received: from localhost by hole.etrust.ru with SMTP id TAA00471; (8.8.8/vak/1.9) Thu, 26 Feb 1998 19:57:17 +0300 (MSK) Date: Thu, 26 Feb 1998 19:57:17 +0300 (MSK) From: Ozz!!! X-Sender: osa@hole.etrust.ru To: Jos Backus cc: freebsd-current@FreeBSD.ORG Subject: Re: new kernel says : ps: proc size mismatch ( 15936 total, 676 chunks ) In-Reply-To: <19980226134259.09831@asterix.urc.tue.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 26 Feb 1998, Jos Backus wrote: > On Thu, Feb 26, 1998 at 06:43:20PM +0300, Ozz!!! wrote: > > What can i do ? > > Try this: > > # cd /usr/src/*/libkvm > # make depend && make all install clean cleandepend > # cd /usr/src/*/ps > # make depend && make all install clean cleandepend OK! Tx! > > Ps: Your From: address is broken. Great tx! > > Cheers, > -- > Jos Backus _/ _/_/_/ "Reliability means never > _/ _/ _/ having to say you're sorry." > _/ _/_/_/ -- D. J. Bernstein > _/ _/ _/ _/ > jbackus@urc.tue.nl _/_/ _/_/_/ use Std::Disclaimer; > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Rgdz, Ozz, osa@unibest.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 08:35:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11801 for freebsd-current-outgoing; Thu, 26 Feb 1998 08:35:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ms7.accmail.com.tw (ms7.accmail.com.tw [210.68.148.43]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA11792; Thu, 26 Feb 1998 08:35:11 -0800 (PST) (envelope-from darkangel@ms7.accmail.com.tw) Message-Id: <199802261635.IAA11792@hub.freebsd.org> Received: from default ([202.145.226.10]) by AccSMTP Gateway for AccMail (v4.00.05/k3.10) [210.68.148.43]; Fri, 27 Feb 1998 00:35:14 +0800 From: "DARKANGEL" To: Cc: Subject: =?BIG5?B?vdCw3S4uLi4uLi4uLi4uLi4uLi4uLi4uLj8=?= Date: Fri, 27 Feb 1998 00:30:09 +0800 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 MIME-Version: 1.0 Content-Type: text/plain; charset=BIG5 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG œÐ°ÝŠ³ÃöFreeBSDªº«ü¥O±Ô­z±qŠó³B¥i¥Hšú±o¬ÛÃöžê®Æ p.s ŸÇ®Õ­n§Ú­ÌœĶFreeBSDªº«ü¥O€Î»yªk........ œÐ±Nµª®×(ºô¯žŠìžm)E-MAILŠÜ DARKANGEL@ACCMAIL.COM.TW ©Î JENTEH@HOTMAIL.COM ÁÂÁÂ...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 10:24:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27761 for freebsd-current-outgoing; Thu, 26 Feb 1998 10:24:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c243.moon.jic.com [206.156.18.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27735 for ; Thu, 26 Feb 1998 10:24:16 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id NAA00539; Thu, 26 Feb 1998 13:23:55 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: nik@iii.co.uk cc: Terry Lambert , current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: DEVFS/SLICE and SOFT UPDATE patches. In-reply-to: Your message of "Wed, 25 Feb 1998 10:21:53 GMT." <19980225102152.50924@iii.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 26 Feb 1998 13:23:55 -0500 Message-ID: <535.888517435@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG nik@iii.co.uk wrote in message ID <19980225102152.50924@iii.co.uk>: > On Wed, Feb 25, 1998 at 02:52:23AM +0000, Terry Lambert wrote: > b) Speculatively put a '/' on the end and try again. > > I don't think any web servers currently do (b), but I wouldn't stake my > life on it. GET /~gpalmer HTTP/1.0 HTTP/1.1 301 Moved Permanently Date: Thu, 26 Feb 1998 18:23:00 GMT Server: Apache/1.2.5 Location: http://www.freebsd.org/~gpalmer/ Connection: close Content-Type: text/html 301 Moved Permanently

Moved Permanently

The document has moved here.

Seems that the WWW server does understand what to do, maybe some browsers don't though ... Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 10:31:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29100 for freebsd-current-outgoing; Thu, 26 Feb 1998 10:31:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29085 for ; Thu, 26 Feb 1998 10:31:35 -0800 (PST) (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id NAA12740; Thu, 26 Feb 1998 13:40:35 -0500 (EST) (envelope-from mark) Message-ID: <19980226134034.12061@vmunix.com> Date: Thu, 26 Feb 1998 13:40:34 -0500 From: Mark Mayo To: "Kenneth D. Merry" , "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: Re: pciconf broken? References: <199802260316.AA06482@iluvatar.unx.sas.com> <199802260602.XAA11787@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199802260602.XAA11787@panzer.plutotech.com>; from Kenneth D. Merry on Wed, Feb 25, 1998 at 11:02:09PM -0700 X-Operating-System: FreeBSD 2.2.5-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 25, 1998 at 11:02:09PM -0700, Kenneth D. Merry wrote: > John W. DeBoskey wrote... > > Hi, > > > > I'm running FreeBSD 3.0-980223-SNAP (GENERIC). > > > > When I run pciconf, I get the following: > > > > # pciconf -l > > pciconf: ioctl(PCIOCGETCONF): Operation not supported by device > > > > > > Does anyone have any info about this? Should it work? Is it > > a known problem? > > This is a known problem. I believe it has been broken since around > April 1997. Hmm. It was working on my -CURRENT box from Dec. 8th, but I just cvsup'ed and made the world last night and now pciconf doesn't work... So I would guess it broke somewhere in between :-) -Mark > > I have a fixed version of that ioctl in the CAM code. It also > passes back the device name (e.g. ahc, fxp, de..) and the unit number of > the device in question. > > Stefan and I have yet to fully work out how the new version should > look, so that's why it isn't in -current or anything. > > > Ken > -- > Kenneth Merry > ken@plutotech.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ "The problem is how do you build tools that understand your programs at a deeper semantic level." - James Gosling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 10:45:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01233 for freebsd-current-outgoing; Thu, 26 Feb 1998 10:45:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thunderdome.plutotech.com (root@thunderdome.plutotech.com [206.168.67.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01226 for ; Thu, 26 Feb 1998 10:45:24 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by thunderdome.plutotech.com (8.8.7/8.8.5) with ESMTP id LAA01180; Thu, 26 Feb 1998 11:45:06 -0700 (MST) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id LAA14199; Thu, 26 Feb 1998 11:44:59 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199802261844.LAA14199@panzer.plutotech.com> Subject: Re: pciconf broken? In-Reply-To: <19980226134034.12061@vmunix.com> from Mark Mayo at "Feb 26, 98 01:40:34 pm" To: mark@vmunix.com (Mark Mayo) Date: Thu, 26 Feb 1998 11:44:59 -0700 (MST) Cc: ken@plutotech.com, jwd@unx.sas.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Mayo wrote... > On Wed, Feb 25, 1998 at 11:02:09PM -0700, Kenneth D. Merry wrote: > > John W. DeBoskey wrote... > > > Hi, > > > > > > I'm running FreeBSD 3.0-980223-SNAP (GENERIC). > > > > > > When I run pciconf, I get the following: > > > > > > # pciconf -l > > > pciconf: ioctl(PCIOCGETCONF): Operation not supported by device > > > > > > > > > Does anyone have any info about this? Should it work? Is it > > > a known problem? > > > > This is a known problem. I believe it has been broken since around > > April 1997. > > Hmm. It was working on my -CURRENT box from Dec. 8th, but I > just cvsup'ed and made the world last night and now pciconf > doesn't work... > > So I would guess it broke somewhere in between :-) That doesn't make any sense. The only change between December 8th and today to pci.c is: Index: pci.c =================================================================== RCS file: /usr/local/cvs/src/sys/pci/pci.c,v retrieving revision 1.80 retrieving revision 1.81 diff -r1.80 -r1.81 26c26 < * $Id: pci.c,v 1.80 1997/11/07 08:53:28 phk Exp $ --- > * $Id: pci.c,v 1.81 1998/01/24 02:54:47 eivind Exp $ 31a32,33 > > #include "opt_devfs.h" And that certainly wouldn't affect the PCIOCGETCONF ioctl. Are you sure you haven't tried CAM at all? If you have, that would probably explain why pciconf -l worked for you before. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 11:44:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07947 for freebsd-current-outgoing; Thu, 26 Feb 1998 11:44:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07899 for ; Thu, 26 Feb 1998 11:43:59 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id LAA26090; Thu, 26 Feb 1998 11:43:25 -0800 (PST) To: "Kenneth D. Merry" cc: mark@vmunix.com (Mark Mayo), jwd@unx.sas.com, freebsd-current@FreeBSD.ORG Subject: Re: pciconf broken? In-reply-to: Your message of "Thu, 26 Feb 1998 11:44:59 MST." <199802261844.LAA14199@panzer.plutotech.com> Date: Thu, 26 Feb 1998 11:43:25 -0800 Message-ID: <26086.888522205@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And I'm still wondering why /dev/pci is reusing a major number that majors.i386 claims it can't have... :) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 13:28:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28298 for freebsd-current-outgoing; Thu, 26 Feb 1998 13:28:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28276 for ; Thu, 26 Feb 1998 13:28:42 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id IAA00469; Thu, 26 Feb 1998 08:03:42 -0500 (EST) Date: Thu, 26 Feb 1998 08:03:42 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: Ozz!!! cc: freebsd-current@FreeBSD.ORG Subject: Re: new kernel says : ps: proc size mismatch ( 15936 total, 676 chunks ) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 26 Feb 1998, Ozz!!! wrote: > Hi ! > > I have a FreeBSD-3.0-980122-SNAP. > I build a new kernel & install it. > After reboot: > # ps ax > ps : proc size mismatch ( 15936 total, 676 chunks ) > > What can i do ? It means that you didn't update your userland stuff at the same time that you updated your kernel, and they are now far enough out of time-sync so that the size of various kernel things is no longer that size expected by some utilities like ps, w, netstat, etc. You can either update your userland stuff (make buildworld, make installworld) or move your old kernel back into place. > > Rgdz, > Ozz, > osa@unibest.ru > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 13:52:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04408 for freebsd-current-outgoing; Thu, 26 Feb 1998 13:52:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04328; Thu, 26 Feb 1998 13:52:25 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id OAA23716; Thu, 26 Feb 1998 14:52:22 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp04.primenet.com, id smtpd023688; Thu Feb 26 14:52:16 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id OAA01909; Thu, 26 Feb 1998 14:52:14 -0700 (MST) From: Terry Lambert Message-Id: <199802262152.OAA01909@usr09.primenet.com> Subject: LDAP 3.3: patches for FreeBSD; someone please make a port? To: owensc@enc.edu (Charles Owens) Date: Thu, 26 Feb 1998 21:52:13 +0000 (GMT) Cc: current@FreeBSD.ORG, msmith@FreeBSD.ORG In-Reply-To: from "Charles Owens" at Feb 26, 98 09:09:15 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have made the LDAP changes I needed for Whistle available at: http://www.freebsd.org/~terry/DIFF.LDAP.txt http://www.freebsd.org/~terry/DIFF.LDAP.gz Some of these changes should still be seperated out and sent to the maintainers (pretty much everything I did that Critical Angle didn't), but this is enough to make PC Netscape, PC Eudora, and the UMICH clients (WAX500, etc.) happy with an LDAP server on FreeBSD. Note: these patches contain all critical angle patches, plus the patches to make those patches work (some of them conflicted with each other -- LDAP is in its own pre-patchkit days, it seems), *EXCEPT* the SSL patches. I omitted the SSL patches because of export issues. You can obtain them from Critical Angle's site and apply them yourself, if you need them. This code presumes you are running either the latest -current or the latest -stable (which have the necessary Jeremy/Terry pthreads changes already integrated to make BSD pthreads actually work like it's supposed to -- er, like POSIX Draft 4, anyway). This should also be a nice baseline for a generic administration and management interface for FreeBSD (per the previous discussion on that topic). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 14:32:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11390 for freebsd-current-outgoing; Thu, 26 Feb 1998 14:32:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from homer.supersex.com (homer.supersex.com [209.5.1.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11385 for ; Thu, 26 Feb 1998 14:32:20 -0800 (PST) (envelope-from leo@homer.supersex.com) Received: (from leo@localhost) by homer.supersex.com (8.8.8/8.8.5) id RAA27978; Thu, 26 Feb 1998 17:32:42 -0500 (EST) Message-ID: <19980226173241.10526@homer.supersex.com> Date: Thu, 26 Feb 1998 17:32:41 -0500 From: Leo Papandreou To: current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. References: <12512.888186392@critter.freebsd.dk> <199802230140.SAA16400@usr08.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74e In-Reply-To: <199802230140.SAA16400@usr08.primenet.com>; from Terry Lambert on Mon, Feb 23, 1998 at 01:40:03AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 23, 1998 at 01:40:03AM +0000, Terry Lambert wrote: [...] > > Not that this happening with an artificially bloated frequency > wouldn't make my cvs locking proposal look a lot more desirable... ;-). > I like Terry. I think core should give him -TERRY and the chance to prove them wrong. Pedantry and code studliness arent mutually exclusive. > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 14:49:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14951 for freebsd-current-outgoing; Thu, 26 Feb 1998 14:49:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (root@lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14945 for ; Thu, 26 Feb 1998 14:49:19 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (wether.sas.com [192.35.83.31]) by lamb.sas.com (8.8.7/8.8.7) with SMTP id RAA01121; Thu, 26 Feb 1998 17:49:08 -0500 (EST) Received: from iluvatar.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA26876; Thu, 26 Feb 1998 17:49:07 -0500 From: "John W. DeBoskey" Received: by iluvatar.unx.sas.com (5.65c/SAS/Generic 9.01/3-26-93) id AA07958; Thu, 26 Feb 1998 17:49:07 -0500 Message-Id: <199802262249.AA07958@iluvatar.unx.sas.com> Subject: Re: pciconf broken? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 26 Feb 1998 17:49:06 -0500 (EST) Cc: ken@plutotech.com, mark@vmunix.com, jwd@unx.sas.com, freebsd-current@FreeBSD.ORG In-Reply-To: <26086.888522205@time.cdrom.com> from "Jordan K. Hubbard" at Feb 26, 98 11:43:25 am X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well.... What might it take to simply get the mechanism fixed in -current? Thanks, John > And I'm still wondering why /dev/pci is reusing a major number that > majors.i386 claims it can't have... :) > > Jordan -- jwd@unx.sas.com (w) John W. De Boskey (919) 677-8000 x6915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 15:12:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18836 for freebsd-current-outgoing; Thu, 26 Feb 1998 15:12:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18823 for ; Thu, 26 Feb 1998 15:12:01 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id KAA18123; Fri, 27 Feb 1998 10:03:08 +1100 Date: Fri, 27 Feb 1998 10:03:08 +1100 From: Bruce Evans Message-Id: <199802262303.KAA18123@godzilla.zeta.org.au> To: jkh@time.cdrom.com, ken@plutotech.com Subject: Re: pciconf broken? Cc: freebsd-current@FreeBSD.ORG, jwd@unx.sas.com, mark@vmunix.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >And I'm still wondering why /dev/pci is reusing a major number that >majors.i386 claims it can't have... :) pci has been using it since rev.1.57 (1996/10/22) of pci.c. It was not registered properly, and some vaporware reused the number. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 16:03:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29035 for freebsd-current-outgoing; Thu, 26 Feb 1998 16:03:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from EDISWITCH2.uninet.net.mx (EDISWITCH2.uninet.net.mx [200.33.150.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29027 for ; Thu, 26 Feb 1998 16:03:27 -0800 (PST) (envelope-from eculp@ver1.telmex.net.mx) Received: from sunix (ver1-154.uninet.net.mx [200.38.135.154] (may be forged)) by EDISWITCH2.uninet.net.mx (8.8.8/8.8.8) with SMTP id RAA10257 for ; Thu, 26 Feb 1998 17:56:52 -0600 (CST) Message-ID: <34F602B3.5DAE5B36@ver1.telmex.net.mx> Date: Thu, 26 Feb 1998 18:02:59 -0600 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: make world problem today. References: <199802262357.RAA07893@bsd3.nix.mexcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Make world from this morning didn't make it. Looks like I need a card.h that I have never had. Anyone else seen this? > cc -nostdinc -O2 -m486 -pipe -I/usr/src/usr.sbin/pccard/pccardc/../pccardd -Wall -g -static -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/pccard/pccardc/rdattr.c > /usr/src/usr.sbin/pccard/pccardc/rdattr.c:39: pccard/card.h: No such file or directory > /usr/src/usr.sbin/pccard/pccardc/rdattr.c: In function `rdattr_main\': > /usr/src/usr.sbin/pccard/pccardc/rdattr.c:56: `CARD_DEVICE\' undeclared (first use this function) > /usr/src/usr.sbin/pccard/pccardc/rdattr.c:56: (Each undeclared identifier is reported only once > /usr/src/usr.sbin/pccard/pccardc/rdattr.c:56: for each function it appears in.) > /usr/src/usr.sbin/pccard/pccardc/rdattr.c:62: `MDF_ATTR\' undeclared (first use this function) > /usr/src/usr.sbin/pccard/pccardc/rdattr.c:63: `PIOCRWFLAG\' undeclared (first use this function) > *** Error code 1 Thanks ed P.S. I cvsuped again and didn't find card.h, assuming that that is the problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 17:55:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21772 for freebsd-current-outgoing; Thu, 26 Feb 1998 17:55:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com ([209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21728 for ; Thu, 26 Feb 1998 17:54:54 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id RAA13163; Thu, 26 Feb 1998 17:54:03 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802270154.RAA13163@rah.star-gate.com> To: Edwin Culp cc: current@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: make world problem today. In-reply-to: Your message of "Thu, 26 Feb 1998 18:02:59 CST." <34F602B3.5DAE5B36@ver1.telmex.net.mx> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13160.888544442.1@rah> Date: Thu, 26 Feb 1998 17:54:02 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG /usr/include/pccard/card.h Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 18:12:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26978 for freebsd-current-outgoing; Thu, 26 Feb 1998 18:12:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from EDISWITCH2.uninet.net.mx (EDISWITCH2.uninet.net.mx [200.33.150.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26924 for ; Thu, 26 Feb 1998 18:11:59 -0800 (PST) (envelope-from eculp@ver1.telmex.net.mx) Received: from sunix (ver1-154.uninet.net.mx [200.38.135.154] (may be forged)) by EDISWITCH2.uninet.net.mx (8.8.8/8.8.8) with SMTP id UAA24341; Thu, 26 Feb 1998 20:01:57 -0600 (CST) Message-ID: <34F62005.780C0E2B@ver1.telmex.net.mx> Date: Thu, 26 Feb 1998 20:08:05 -0600 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: Amancio Hasty CC: current@FreeBSD.ORG Subject: Re: make world problem today. References: <199802270154.RAA13163@rah.star-gate.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote: > > /usr/include/pccard/card.h > > Cheers, > Amancio This one has been around since oct 30, an oldy but goody, I guess :-) Thanks ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 19:48:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10015 for freebsd-current-outgoing; Thu, 26 Feb 1998 19:48:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09974 for ; Thu, 26 Feb 1998 19:48:46 -0800 (PST) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id DAA02369 for ; Fri, 27 Feb 1998 03:48:06 GMT Date: Fri, 27 Feb 1998 12:48:06 +0900 (JST) From: Michael Hancock To: freebsd-current@FreeBSD.ORG Subject: VFS_VRELE - WILLRELE must die Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-1804928587-888551286=:2308" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---559023410-1804928587-888551286=:2308 Content-Type: TEXT/PLAIN; charset=US-ASCII Implement the complement to all vpp generating ops called in the vfs_vn layer. Some people call this making it reflexive. The 4K tar ball is attached, but I can upload this somewhere if you're mailer doesn't do MIME. Regards, Mike Hancock ------------------ The intent is to get rid of WILLRELE in vnode_if.src by making a complement to all ops that return a vpp, VFS_VRELE. This is initially only for file systems that implement the following ops that do a WILLRELE: vop_create, vop_whiteout, vop_mknod, vop_remove, vop_link, vop_rename, vop_mkdir, vop_rmdir, vop_symlink This is initial DNA that doesn't do anything yet. VFS_VRELE is implemented but not called. In the next phase vop implementations vrele and the vrele part of vput will be moved to the top layer vfs_vnops and made visible to all layers. This will only be done for vnode arguments that are released by the various fs vop implementations. Unlocking will still be done in the per fs layer but the refcount decrement will be initiated at the top because it doesn't hurt to hold a vnode reference a little longer. VFS_VRELE implementations were made for the following file systems: ffs_vfsops.c mfs_vfsops.c nfs_vfsops.c msdosfs_vfsops.c devfs_vfsops.c nullfs_vfsops.c union_vfsops.c umapfs_vfsops.c The following implementations just do ENOTSUPP because they don't implement any of the WILLRELE vops: procfs_procfs.c cd9660_vfsops.c The following code snippet from vn_open is an example of how it will be added later. vop_create releases the directory vnode, but we will change it so that it is initiated in vn_open after the VOP_CREATE returns. Now... if (error = VOP_CREATE(ndp->ni_dvp, &ndp->ni_vp, &ndp->ni_cnd, vap)) return (error); Later... error = VOP_CREATE(ndp->ni_dvp, &ndp->ni_vp, &ndp->ni_cnd, vap); VFS_VRELE(ndp->ni_dvp->vmount, ndp->ni_dvp); if (error) return (error); ---559023410-1804928587-888551286=:2308 Content-Type: APPLICATION/octet-stream; name="vfs_vrele.tgz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: H4sIAJUq9jQAA+1cbW/bOBLuV+tXELvAnZ04sd7tuLii2TbdLZAmRuNme8AC hmpJta62JEiy09xi//vNDCmJku1N0zZ2r9W0sS2KmhlyqHlmSEorP52sEm/u 9R49GDFT7VsWe8SQVPHdF9+ikNlm3zJ13dbgt6bahvWIWQ+nUknLNHMSxh4l UZT9Xb13QbgLdXZNq8L+U/fEttVjN/D9ryxDU1XbNLfaX9c1s7C/0TfA/rql mo+Y+pX12Eg/uP1fhq73cci48ScwGqI4PZ4q//pyUl4/u2J+MPeGrLdMk950 lfbSZNpLb9NekEZ+KkZcrya7u1ISL0sCbxWE71kCX2kQhUw7NgwFByc7WrKj BA/XtD46OqqXtbSTk35P03u6xnRtaKpDVW8Rr8PDw02VBz0VKveZqg/1wdCw lKdP2VHf6NrsED777OlThcGQyYIpC8Is55DehlM2mYza7TRLltOMLaIlnD3o YqUuE4XLaeK5WKiwFo58URwn0ZQddDqPN3FevfeybZyjScl7FUauxw6IzeEG NniPb+ZTZbBFDX+WRav4bxn4gSsdpdH0g+O6CRRVW5srSl0jXSA6Z2s/xFnk zyoKCE5VBfByNNnARpMN+sJkrdxQwNhPu1IBWE46xO7uKoctuduk07wb5Pqk llQQhEFGCtgWaWBbg652wnUg/wd1f/ZCGMmiIG8N3BMTN0i8aRYltxP4jhJs jkoG/Us5VA57B8ohO2DPokU89xYe9E0WMWc+Z6s4hhslWyYh3jI4lKni27dv 2RFDhQKodcuiED7gEhxRCfRV5LPfX56fvz47P6MLeiiCnb7+9erN1dlzOi7t oBzKXdJexF0Q24Geqo6GRfy4LBMGWmHZn1DMdWTts8vRxeX46s1ohLb+S4H7 ASXs2xf+iFTiv+vB74eA/7vwX7PANwv8h0DRRvzvq0aD/7sggf9k/J3B/yJI p4D/JLRXFb0V/XW7gv66XdcZwb9aJOBcA0Rnan9oaEPVbhEnxP6NdTn0a0PL HuoauXFD09CN41fuxoUbK72YcGL7dtCiReSf6165DvPku8EnP/9l9Prlxbjd /olHCD8R3LQ4E6j0WHLbao5ErHfwJaQwaPt45rFpFE69OMN2eh/jKMmwdxz2 wUtCbw69EHqJk0FQQA0DgIQ2LOPApeuvIuZG4T8zNnNCFxTHocZ/ptxuJreb ZeYRAO+eMgAQxwL/RecJ+Je6sjxZgr84XWA/Pybo3/cNfU8q/b//QN7/E/K/ vl74f8vG/F83zH7j/3dBwv+D8SfexwxuvOPZQ3v/JTh9n/8VMre7fb3q9vWq quj05YLCjasGpnuWPlTVFnFBl7+xJiCJBlnhYGgNyHGcUNgOn9xtUGja8gkq Es/bnICIVAxqUvZSXPE5uVtx8b0ytuKqe6RJ0DbeG2wVxRPgfEAcsDocQ9Au DY5dhQby4LgzJuhXB0dfr6qaD451jLeYag7N/lA1W8QlHxzbogFrqPFoYEAT AYN8IoC6vEQUX8ITX0ITX8YSv4IkfgVHfIEiXRKmqXwswne/q6tc4l8toh6P HiAEwMmEAwww/sUo0VqH633EJRSQFO3+vHRRCkJYpVUUbe3bc34fVOL/Yl/4 zyyc8xX4b6s0/2sYdoP/uyDh4hc7dvEL/ne3izfVios31aqq6OIXmxy3esJU G7w2AHuLuKCL31iT4z/81/sc/y3Cfyt38Yuv6+IXhYvft+mJpPs/daP0QXzA XfG/ppX3f1+14P43dFNv7v9dUH7/c+PvbgaIy+vV5W7PAwbVPGCwrjL5glph eZcbTLOHpjk0cPkHuJE/2Fo7D/ssm/sElXyCurb+08pZLEMe0dy5BrRxsadg sy1jwPiJcgb8RDcCtLaiAtFcbfWn5PuZyz8lg/vlFdK0FI9kDYNHsoZZRLLf 6jRapc++OHLdNH0mpOUX0+irDUaI5v9EtBCFJLQrFaDXKtIEU+edaxWrXVI1 AVxFiQAvecQhgFVaLVcogaw6FuSS/8eZr4aQSvwP9xX/a7ZWrv/YJo//LavB /12QwP9wh9gPsnrhp2C+ZVYw3zKraiLeh5vQW8T+6tA4aREXxPqNNTnOQ2Cg mtyVagT0+CUcaau1tp8hdBZrM3eATByVaU+D99GfO+/TeG1vA345YRTGdZgN P3e2sM7jXjiP/wBsqeW6SS3Xi7wnrMBHKEFHKMFGKENGWIGLsAIVYQ4TFE/x ebSTgZVHA3/SPNbGDQLfxOaH8IECAr77ARq3p/tf8v/L+fxhIODO9R/Tzv2/ puJeQM2APLDx/7ug3P+D8Xe9/M8HXK8ienv+V8UC3aypTGAgl5RoYEM8MdSM oUkrQQINNlYt1v5Nse2PpoL6VgkG69v21l05Net+mdzdiVzOdZt/37jCv0Wz rancKq4mc/4sFjghUMIYDGhRfXDSBQvIWdz1i6vJ9a9n4/aryzcX4/HlxZvz c/oJ/rJz9ARFL7DDqfHoQOPON5LuyT37ec4dMd9LkiiBpE19jGDVyg+pW1CT O/sFLsLRheevR+PL88vfz15fj9rcilsAhKTUs0psFBON4mBMrQKDwifFLhis sDJGKYMSMOd6s9HupnaCdjeNQREdcAFSgCAK8hihvAsoTJA6WTotBQvy2JQK vqGp0u+SSvxHd7YX/NdMo8j/NM2i+V/VbuZ/d0IC/7nxdx0BcKm9mvCtMYB2 UokBtJM1tTEKqJUVDwAYKlMHQxMngVvEC+OADZXzRSGobAzyCWDthM9fwteg 3MudBv/1JutTux0visMoS5cxutSfXc8PQq8QhTDVbiNmtA8698v3OuwPIVmW cFiXQDHCHSLq2SCyPlxjvaY8Dx02894yH9zxgnDlzDvStHB14rNiA5r3xB7X VUpIdTXfiNMS9UrIyQsE5EgdjJAj94Z0uoScSpukgh8Kckr/v1w48X7yPzhf +n++/qeazfr/Tkj4fzT+rr0/H3C9iujt+V91H4Cu1lRGz18pKfM/SuqMfOWP 7wTYXJU/9qVaQ4Pv9urTugp83if/48362vlfzvVL8r+cxxfkfxwGjZO1Vbx2 PQF88+p0JCU6KLueAH4rGaDctw+53keZmRD21TIz3ahlZkJACZN5gYBJaXwi TMqNl06XMFkZNVLBDwWT3y1J+B+Cp93H818Q6RX7f3TNMun5L63B/51Qjv9o /J0HACi0VxV9j+e/ajpTBFApKnBdo9RPhRBAK5//2lJXPPpdLAn2KQ3pm9UY YEMIILbSE9By1veIAD4hAOA8743/62p9PvxbHGwsvYD/fPVqr/Bd9sxDoDdG J6zQ+jRNlwsvZWHEXCdz2NSZzjyXORkfT2zu3HrJMV7QK7NnriG9I+DOzH/D 2wL+4J1v9qnz7SIcFWxLoC/ElEcFzJedVJ6UQF4aGuVxA/HfPZX4//rs9Pmr s4eQcQf+G5pRvP/F4vm/ZmvN/p+dED6GC04HnXaQbnHCUIH7zEngHwOGs3e3 bOF8AJ+ugANc8/o4i5fNwCMKV+rwtKZYCjtmbDwL8HlepYYBfpRQyMAgSMi8 hWATlAJAWT+az6MbgScKVXBBbqHsUFFa+DgbOE8n87r0aNvNLMi8aJnxo8UH aAv/mXiLaCUqzYPwQ5dfm3iQjXl5bTdIRO1F8TO9XWB9RREtydGMPb84ZUIp L8XHk1G58Daboca3XgaNLzqCeiBvHLj6d8sMcCUDTJnPPRdqvgypySFgOItn Tuqh7LI/AAKjMFV4TOCELlXmR7GT0GPVqxh43gRglXcew7a6aCWslwEnAitl xR/6A6shj4UD2IhR17u5l1uU6qW53Ygd2Qt4ulHoKWg3DqpO8n6JqgnTOYnH UB9Q3cVRQwo6SRAtU+an2Bql1hoQ8iacR1McXVxSmgn1URQORWQSewky4A3A fsPCxPOnBKSuB9anEZM3nZsn40idN/+dN3WW0KlBpuTWmi0TGsezaO7iwKVG AV8PhsQUmsfmQZZBx8yj8D3ivCIZs9oQdgPX8N7E7qkOXXmQ44CVnz2sPKVS 2ba2vuW9VX2JQb7sWxxXY9x87qG4XBlXtKq34D/gG3H8nom9WEWHQWNu+dP3 pflwlOOIw4YWjgMMTO0TM+tiiXG69uKmmiJT7PU0DOIYnJGfRAswxCSKvRDv NCeEmNZBsShuFt2A/cjOCtjZcV2w8RwsncBIKv1APgpT0q94zQ43cJfuvBtP odEynTlgW2SaRsIBZeUdjkOI3CHXx/FBEvG8vhxNngGGjs8U7vcg2FUuopvj Y/huBb5Yrcc9AUXNdujGR0/CYOJi6P2P/AhDMppoLEqmITosB8JxpbW2+q+c U3NJzn1kbGD/WGmVOxakC4+erPgOdCYVYu2iXZsU2ze2NXQ3lfEfuKM9vf9B M8v3Pxi0/q+bahP/7YTy57/w7n74Vz/Q5A8XtX3Xd3Wix7IL5egBL/67nK7R aQd3f2jh1I7Fp3bWKtm4IVw3hqbOlzEs8W4YbfPKjsi88bO7aaoHd3y12gf5 C2M6rU9+YmvrM1syS7wdt/LcOMkjXc1z+rsuz+d31hX7xH3udMk9NrtTt9s0 g2HY+VpFPj+CmHM1Ph2/uGq/GnXZ1S/wMeqAiPYBFHSOnizCDPAWUKhY2OjI NWuc/n3xjM7+fvpy3GXPsMYWVrfhtFOvWmXGl7SgxsuLS8hhRlvVooFQrVnu zJC2AY7w3FYmZPq8UlWTF7+NL69HdO7Fy+fweXH6iuR02dnbF+e/gvqvz57z LSKbeIuBcSeDQioPBUbjyxe/ta/FRULxa2S+4k+l1VpAU0id8oImCmiooYYa aqihhhpqqKGGGmqooYYaaqihhhpqqKGGGmqooYYaaqihB6f/AX3NdMQAeAAA ---559023410-1804928587-888551286=:2308-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 21:14:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19283 for freebsd-current-outgoing; Thu, 26 Feb 1998 21:14:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19257 for ; Thu, 26 Feb 1998 21:14:21 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id WAA23421; Thu, 26 Feb 1998 22:14:09 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id WAA01469; Thu, 26 Feb 1998 22:14:05 -0700 Date: Thu, 26 Feb 1998 22:14:05 -0700 Message-Id: <199802270514.WAA01469@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Edwin Culp Cc: Amancio Hasty , current@FreeBSD.ORG Subject: Re: make world problem today. In-Reply-To: <34F62005.780C0E2B@ver1.telmex.net.mx> References: <199802270154.RAA13163@rah.star-gate.com> <34F62005.780C0E2B@ver1.telmex.net.mx> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > /usr/include/pccard/card.h That was deleted from -current a *LONG* time ago. > This one has been around since oct 30, > an oldy but goody, I guess :-) Baddy in this case. I modified it to use a different include file, so if you could check to see if it compiles I would appreciate it. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 26 22:07:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28616 for freebsd-current-outgoing; Thu, 26 Feb 1998 22:07:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28584 for ; Thu, 26 Feb 1998 22:07:42 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id WAA29104; Thu, 26 Feb 1998 22:07:09 -0800 (PST) To: "John W. DeBoskey" cc: ken@plutotech.com, mark@vmunix.com, freebsd-current@FreeBSD.ORG Subject: Re: pciconf broken? In-reply-to: Your message of "Thu, 26 Feb 1998 17:49:06 EST." <199802262249.AA07958@iluvatar.unx.sas.com> Date: Thu, 26 Feb 1998 22:07:09 -0800 Message-ID: <29101.888559629@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, apparently the Plutotech people are working on it already, so I guess the answer to that question is "wait" :-) Jordan > Well.... > > What might it take to simply get the mechanism fixed in -current? > > Thanks, > John > > > And I'm still wondering why /dev/pci is reusing a major number that > > majors.i386 claims it can't have... :) > > > > Jordan > > > -- > jwd@unx.sas.com (w) John W. De Boskey (919) 677-8000 x6915 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 01:09:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21723 for freebsd-current-outgoing; Fri, 27 Feb 1998 01:09:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from firewall.ftf.dk (root@mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21714; Fri, 27 Feb 1998 01:08:58 -0800 (PST) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.2]) by firewall.ftf.dk (8.7.6/8.7.3) with ESMTP id LAA29974; Fri, 27 Feb 1998 11:57:54 +0100 Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.5/8.8.5/prosa-1.1) with ESMTP id KAA19309; Fri, 27 Feb 1998 10:16:50 +0100 (CET) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.7/8.8.5/prosa-1.1) id KAA01063; Fri, 27 Feb 1998 10:07:56 +0100 (CET) Message-ID: <19980227100756.65141@deepo.prosa.dk> Date: Fri, 27 Feb 1998 10:07:56 +0100 From: Philippe Regnauld To: Terry Lambert Cc: Charles Owens , current@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: LDAP 3.3: patches for FreeBSD; someone please make a port? References: <199802262152.OAA01909@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.88e In-Reply-To: <199802262152.OAA01909@usr09.primenet.com>; from Terry Lambert on Thu, Feb 26, 1998 at 09:52:13PM +0000 X-Operating-System: FreeBSD 2.2.5-RELEASE i386 Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert writes: > I have made the LDAP changes I needed for Whistle available at: > > http://www.freebsd.org/~terry/DIFF.LDAP.txt > http://www.freebsd.org/~terry/DIFF.LDAP.gz Thanks for the work! -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- «Pluto placed his bad dog at the entrance of Hades to keep the dead IN and the living OUT! The archetypical corporate firewall?» - S. Kelly Bootle, ("MYTHOLOGY", in Marutukku distrib) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 01:34:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23997 for freebsd-current-outgoing; Fri, 27 Feb 1998 01:34:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23986 for ; Fri, 27 Feb 1998 01:34:44 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id JAA25064; Fri, 27 Feb 1998 09:34:36 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id KAA03586; Fri, 27 Feb 1998 10:34:12 +0100 (MET) Message-ID: <19980227103412.52813@follo.net> Date: Fri, 27 Feb 1998 10:34:12 +0100 From: Eivind Eklund To: Michael Hancock , freebsd-current@FreeBSD.ORG Subject: Re: VFS_VRELE - WILLRELE must die References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Michael Hancock on Fri, Feb 27, 1998 at 12:48:06PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 27, 1998 at 12:48:06PM +0900, Michael Hancock wrote: > Implement the complement to all vpp generating ops called in the vfs_vn > layer. Some people call this making it reflexive. > > The 4K tar ball is attached, but I can upload this somewhere if you're > mailer doesn't do MIME. > > Regards, > > > Mike Hancock > ------------------ > The intent is to get rid of WILLRELE in vnode_if.src by making > a complement to all ops that return a vpp, VFS_VRELE. This is > initially only for file systems that implement the following ops > that do a WILLRELE: Uhm - what might 'RELE' stand for? My _guess_ is that it is a shortened form of 'RELEASE', but that's not certain - there are lots of other possibilities. If it is 'release', I'd like VFS_VRELE to be renamed to VFS_VRELEASE. Let's keep things easy where we can. If it actually is talking about a 'rele' (a technical name for an automated switch, at least in norwegian), then disregard the above. Then I think a rename to VFS_VSWITCH might be in order, though. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 01:58:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28266 for freebsd-current-outgoing; Fri, 27 Feb 1998 01:58:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28254 for ; Fri, 27 Feb 1998 01:58:18 -0800 (PST) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id JAA05443; Fri, 27 Feb 1998 09:57:34 GMT Date: Fri, 27 Feb 1998 18:57:34 +0900 (JST) From: Michael Hancock To: Eivind Eklund cc: freebsd-current@FreeBSD.ORG Subject: Re: VFS_VRELE - WILLRELE must die In-Reply-To: <19980227103412.52813@follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 27 Feb 1998, Eivind Eklund wrote: > Uhm - what might 'RELE' stand for? My _guess_ is that it is a > shortened form of 'RELEASE', but that's not certain - there are lots > of other possibilities. > > If it is 'release', I'd like VFS_VRELE to be renamed to VFS_VRELEASE. Have a look at vrele() and vput() in vfs_subr.c, calls to these are scattered all over the fs code. VFS_VRELE would be more familiar than VFS_VRELEASE to people working on the fs code. Most of the implementations do the same thing so I'll probably add a vfsop section with vfs_vrele(mp,vp) to phk's vfs_default.c which I stumbled onto today. This can be done anytime later though. If these are accepted then we can start working horizontally across the offending VOPs starting with vop_create. Regards, Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 04:01:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10183 for freebsd-current-outgoing; Fri, 27 Feb 1998 04:01:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10177 for ; Fri, 27 Feb 1998 04:01:25 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id MAA02667; Fri, 27 Feb 1998 12:56:27 +0100 (CET) To: Michael Hancock cc: freebsd-current@FreeBSD.ORG Subject: Re: VFS_VRELE - WILLRELE must die In-reply-to: Your message of "Fri, 27 Feb 1998 12:48:06 +0900." Date: Fri, 27 Feb 1998 12:56:27 +0100 Message-ID: <2665.888580587@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sounds like you're basically on the right track. Poul-Henning >The intent is to get rid of WILLRELE in vnode_if.src by making >a complement to all ops that return a vpp, VFS_VRELE. This is >initially only for file systems that implement the following ops >that do a WILLRELE: -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 04:29:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA13986 for freebsd-current-outgoing; Fri, 27 Feb 1998 04:29:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA13981 for ; Fri, 27 Feb 1998 04:29:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id EAA27731 for ; Fri, 27 Feb 1998 04:27:54 -0800 (PST) Message-Id: <199802271227.EAA27731@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: current@FreeBSD.ORG Subject: VFAT/FAT32 patches committed, testers please! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Feb 1998 04:27:53 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, this commit fixes the last known problems with the FAT32/VFAT code. If you're set up to track -current and you're interested in testing this, make sure you're up to date (maybe wait 6-12 hours then CVSup, check you get the right version of msdosfs_conv.c), and have at it. All test results happily received, and thanks to the testers that have got us this far! ------- Forwarded Message From: Michael Smith Date: Fri, 27 Feb 1998 04:22:24 -0800 (PST) Message-Id: <199802271222.EAA03526@freefall.freebsd.org> To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, cvs-sys@FreeBSD.org Subject: cvs commit: src/sys/msdosfs msdosfs_conv.c msmith 1998/02/27 04:22:24 PST Modified files: sys/msdosfs msdosfs_conv.c Log: Fix a problem with the conversion of Unix filenames into the VFAT namespace. Submitted by: Dmitrij Tejblum Revision Changes Path 1.25 +34 -11 src/sys/msdosfs/msdosfs_conv.c ------- End of Forwarded Message -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 05:06:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17448 for freebsd-current-outgoing; Fri, 27 Feb 1998 05:06:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from EDISWITCH2.uninet.net.mx (EDISWITCH2.uninet.net.mx [200.33.150.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA17439 for ; Fri, 27 Feb 1998 05:06:43 -0800 (PST) (envelope-from eculp@ver1.telmex.net.mx) Received: from mc.mexcom.net (ver1-183.uninet.net.mx [200.38.135.183] (may be forged)) by EDISWITCH2.uninet.net.mx (8.8.8/8.8.8) with SMTP id HAA03951; Fri, 27 Feb 1998 07:00:04 -0600 (CST) Message-ID: <34F6BBE0.2781E494@ver1.telmex.net.mx> Date: Fri, 27 Feb 1998 07:13:04 -0600 From: eculp Organization: MexCom X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-971226-SNAP i386) MIME-Version: 1.0 To: Nate Williams CC: current@FreeBSD.ORG Subject: Re: make world problem today. References: <199802270154.RAA13163@rah.star-gate.com> <34F62005.780C0E2B@ver1.telmex.net.mx> <199802270514.WAA01469@mt.sri.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams wrote: > > > > /usr/include/pccard/card.h > > That was deleted from -current a *LONG* time ago. > > > This one has been around since oct 30, > > an oldy but goody, I guess :-) > > Baddy in this case. > > I modified it to use a different include file, so if you could check to > see if it compiles I would appreciate it. > > Nate on line 39 of /usr/src/usr.sbin/pccard/pccardc/rdattr.ca #include Ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 05:29:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19344 for freebsd-current-outgoing; Fri, 27 Feb 1998 05:29:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chuggalug.clues.com (root@chuggalug.clues.com [194.159.247.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA19339 for ; Fri, 27 Feb 1998 05:29:16 -0800 (PST) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.6.12/8.6.12) id NAA01214 for freebsd-current@freebsd.org; Fri, 27 Feb 1998 13:29:14 GMT From: Geoff Buckingham Message-Id: <199802271329.NAA01214@chuggalug.clues.com> Subject: Pthreads in current To: freebsd-current@FreeBSD.ORG Date: Fri, 27 Feb 1998 13:29:14 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Playing with yesterdays current I notice the aparent absence of pthread_attr_setscope and pthread_attr_setschedparam from libc_r. The man page claims both are present :-) pthread_setschedparam is also missing but I suspect this may be non standard? (Although both Sun and SGI seem to have implimented it) Is this by intention or just that no one has implimented them yet? -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 07:51:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06154 for freebsd-current-outgoing; Fri, 27 Feb 1998 07:51:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arh0300.urh.uiuc.edu (arh0300.urh.uiuc.edu [130.126.72.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06111 for ; Fri, 27 Feb 1998 07:51:18 -0800 (PST) (envelope-from dannyman@arh0300.urh.uiuc.edu) Received: (from dannyman@localhost) by arh0300.urh.uiuc.edu (8.8.8/8.8.5) id JAA28074; Fri, 27 Feb 1998 09:51:15 -0600 (CST) Message-ID: <19980227095115.05314@urh.uiuc.edu> Date: Fri, 27 Feb 1998 09:51:15 -0600 From: dannyman To: freebsd-current@FreeBSD.ORG Subject: Curious: "Timecounter"? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i X-Loop: djhoward@uiuc.edu X-URL: http://www.uiuc.edu/ph/www/djhoward/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG arh0300 kernel log messages: > Timecounter "i8254" frequency 1193182 Hz cost 2524 ns > Timecounter "TSC" frequency 99952423 Hz cost 356 ns > wcd0: 0Kb/sec, caddy > wcd0: medium type unknown Wow, the new kernel compiling mechanism is kinda neat. I'm curious about these Timecounter lines. Can anyone explain, in terms a fairly unsophisticated guy like me could understand, what these lines mean? Just curious. Thanks, dan -- //Dan -=- This message brought to you by djhoward@uiuc.edu -=- \\/yori -=- Information - http://www.uiuc.edu/ph/www/djhoward/ -=- aiokomete -=- Our Honored Symbol deserves an Honorable Retirement To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 08:19:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12045 for freebsd-current-outgoing; Fri, 27 Feb 1998 08:19:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11980 for ; Fri, 27 Feb 1998 08:18:49 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id RAA03450; Fri, 27 Feb 1998 17:13:34 +0100 (CET) To: dannyman cc: freebsd-current@FreeBSD.ORG Subject: Re: Curious: "Timecounter"? In-reply-to: Your message of "Fri, 27 Feb 1998 09:51:15 CST." <19980227095115.05314@urh.uiuc.edu> Date: Fri, 27 Feb 1998 17:13:34 +0100 Message-ID: <3448.888596014@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980227095115.05314@urh.uiuc.edu>, dannyman writes: >arh0300 kernel log messages: >> Timecounter "i8254" frequency 1193182 Hz cost 2524 ns >> Timecounter "TSC" frequency 99952423 Hz cost 356 ns >> wcd0: 0Kb/sec, caddy >> wcd0: medium type unknown > >Wow, the new kernel compiling mechanism is kinda neat. > >I'm curious about these Timecounter lines. Can anyone explain, in terms a >fairly unsophisticated guy like me could understand, what these lines mean? It means that the machine has two pieces of hardware it can use for the construction of "time-of-day". "frequency" should be pretty obvious, "cost" is how long time it takes to read the counter, and consequently a measure of the overhead by using that timecounter. To get from the reading of the timecounters which is just a binary counter running at "frequency" to microtime() and/or nanotime() various scaled integer math is done. You can find the relevant code in sys/sys/time.h, sys/kern/kern_clock.c, sys/kern/kern_ntptime.c, sys/i386/isa/clock.c -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 08:48:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17386 for freebsd-current-outgoing; Fri, 27 Feb 1998 08:48:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17360 for ; Fri, 27 Feb 1998 08:48:21 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id KAA17330 for ; Fri, 27 Feb 1998 10:48:21 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id KAA13283; Fri, 27 Feb 1998 10:48:20 -0600 (CST) Message-ID: <19980227104820.11421@mcs.net> Date: Fri, 27 Feb 1998 10:48:20 -0600 From: Karl Denninger To: current@FreeBSD.ORG Subject: Today's "make world" explosion Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> usr.sbin/lpr ===> usr.sbin/lpr/common_source cc -nostdinc -pipe -Werror -Wall -Wnested-externs -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/lpr/common_source/common.c -o common.o cc -nostdinc -pipe -Werror -Wall -Wnested-externs -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/lpr/common_source/displayq.c -o displayq.o cc1: warnings being treated as errors /usr/obj/usr/src/tmp/usr/include/ctype.h:146: warning: `__maskrune' defined but not used /usr/obj/usr/src/tmp/usr/include/ctype.h:160: warning: `__toupper' defined but not used /usr/obj/usr/src/tmp/usr/include/ctype.h:167: warning: `__tolower' defined but not used *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Hmmmm.. why did cc1 get set to do that (treat warnings as errors)? -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 10:44:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02472 for freebsd-current-outgoing; Fri, 27 Feb 1998 10:44:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (root@burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02409 for ; Fri, 27 Feb 1998 10:44:00 -0800 (PST) (envelope-from archer@grape.carrier.kiev.ua) Received: from unicorn.carrier.kiev.ua (unicorn.carrier.kiev.ua [193.193.193.113]) by burka.carrier.kiev.ua (8.8.8/8.Who.Cares) with ESMTP id UAA08590 for ; Fri, 27 Feb 1998 20:43:29 +0200 (EET) Received: from kozlik.carrier.kiev.ua (kozlik.carrier.kiev.ua [193.193.193.111]) by unicorn.carrier.kiev.ua (8.8.8/8.8.7) with ESMTP id UAA08223 for ; Fri, 27 Feb 1998 20:43:27 +0200 (EET) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.8.8/8.8.8/8.Who.Cares) with UUCP id UAA00502 for current@freebsd.org; Fri, 27 Feb 1998 20:40:38 +0200 (EET) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.8.8/8.8.8) id UAA23246; Fri, 27 Feb 1998 20:38:13 +0200 (EET) (envelope-from archer) Message-ID: <19980227203812.20997@carrier.kiev.ua> Date: Fri, 27 Feb 1998 20:38:12 +0200 From: Alexander Litvin To: current@FreeBSD.ORG Subject: Bad DMI table checksum! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for bothering, but what does Subj. mean? (It appears during kernel booting, 3.0-CURRENT of February, 25) --- Alexander Litvin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 11:42:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13678 for freebsd-current-outgoing; Fri, 27 Feb 1998 11:42:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13668 for ; Fri, 27 Feb 1998 11:42:35 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id GAA17389; Sat, 28 Feb 1998 06:43:52 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199802271943.GAA17389@cimlogic.com.au> Subject: Re: Pthreads in current In-Reply-To: <199802271329.NAA01214@chuggalug.clues.com> from Geoff Buckingham at "Feb 27, 98 01:29:14 pm" To: geoffb@chuggalug.clues.com (Geoff Buckingham) Date: Sat, 28 Feb 1998 06:43:52 +1100 (EST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Geoff Buckingham wrote: > Playing with yesterdays current I notice the aparent absence of > pthread_attr_setscope and pthread_attr_setschedparam from libc_r. pthread_attr_setscope depends on _POSIX_THREAD_PRIORITY_SCHEDULING which is commented out in pthread.h because there is currently no way to set a scheduling policy. > The man page claims both are present :-) This needs work. > pthread_setschedparam is also missing but I suspect this may be > non standard? (Although both Sun and SGI seem to have implimented it) > > Is this by intention or just that no one has implimented them yet? Yes and yes. 8-) -- John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 13:47:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04746 for freebsd-current-outgoing; Fri, 27 Feb 1998 13:47:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ewc-nt.ewc.edu (surf4282.se.mediaone.net [24.129.49.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04693; Fri, 27 Feb 1998 13:46:22 -0800 (PST) (envelope-from root@ewc-nt.ewc.edu) Received: (from root@localhost) by ewc-nt.ewc.edu (8.8.8/8.8.8) id QAA00745; Fri, 27 Feb 1998 16:51:25 GMT (envelope-from root) Received: from eot.cs.uoregon.edu ([128.223.202.87]) by ewc-nt.ewc.edu (Netscape Mail Server v2.02) with ESMTP id AAA264 for ; Mon, 26 Jan 1998 12:40:33 -0500 Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by eot.cs.uoregon.edu (8.8.5/8.8.5) with ESMTP id JAA17458; Mon, 26 Jan 1998 09:42:25 -0800 (PST) Received: from localhost (daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA23326; Mon, 26 Jan 1998 09:42:24 -0800 (PST) (envelope-from owner-freebsd-current) Received: by hub.freebsd.org (bulk_mailer v1.6); Mon, 26 Jan 1998 09:40:26 -0800 Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22452 for current-outgoing; Mon, 26 Jan 1998 09:40:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from seera.nttlabs.com (seera.nttlabs.com [204.162.36.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22410; Mon, 26 Jan 1998 09:40:16 -0800 (PST) (envelope-from gene@nttlabs.com) Received: from nttlabs.com (localhost [127.0.0.1]) by seera.nttlabs.com (8.8.8/8.8.7) with ESMTP id JAA28495; Mon, 26 Jan 1998 09:39:41 -0800 (PST) Message-ID: <34CCCA5B.7B5AA8FD@nttlabs.com> Date: Mon, 26 Jan 1998 09:39:39 -0800 From: "Eugene M. Kim" Organization: NTT Multimedia Communications Laboratories X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Hardware FreeBSD ML CC: Current FreeBSD ML , "Eugene M. Kim" Subject: Re: ie0 and EE16 References: <199801201816.MAA24372@compound.east.sun.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Status: RO X-IMAP-Date: 26-Jan-1998 12:40:54 +0000 X-UID: 358 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, Tony Kimball wrote: > > Just FYI, the ie driver consistently fails for me after several days > of use, with an EE16 card. The mode: network activity stops (by the > hub light); no messages are logged; ping returns "sendto: no buffer > space available"; 'ifconfig ie0 down; ifconfig ie0 up' causes ping > to stop reporting errors, but no network activity occurs until reboot. > > Strangely, I've never seen this effect with NFS traffic, only with X, > and specific applications seem to trigger it: Acroread, or netscape, > for example, but not ghostview. My 3COM 3C509-TP ISA card (ep) does, too. The network activity on ep0 stops almost invariably when I use Netscape on another Win95 PC and try to download something big which imposes a load on the network continuously. It also stops when using Acroread. The symptom is exactly the same as Mr. Kimball's one, that is, some programs including ping report that there is no buffer space available, and also ifconfig ep0 shows that OACTIVE attribute is set on the interface; does this ring a bell to anyone? I CC'ed this message to FreeBSD-current mailing list because I had not seen this problem until the world was rebuilt with a recent -current source tree. This problem was first seen about a week ago. Hope this helped and thanks much, Gene -- Eugene M. Kim Software Developer NTT Multimedia Communications Laboratories mailto:gene@nttlabs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 14:38:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14696 for freebsd-current-outgoing; Fri, 27 Feb 1998 14:38:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14686 for ; Fri, 27 Feb 1998 14:38:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA29187; Fri, 27 Feb 1998 14:36:11 -0800 (PST) Message-Id: <199802272236.OAA29187@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Alexander Litvin cc: current@FreeBSD.ORG Subject: Re: Bad DMI table checksum! In-reply-to: Your message of "Fri, 27 Feb 1998 20:38:12 +0200." <19980227203812.20997@carrier.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Feb 1998 14:36:11 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Sorry for bothering, but what does Subj. mean? (It appears during > kernel booting, 3.0-CURRENT of February, 25) It means that your BIOS claims to have a DMI table, but that the checksum associated with the table is wrong. You can read more about DMI at http://www.dmtf.org/ -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 20:12:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15640 for freebsd-current-outgoing; Fri, 27 Feb 1998 20:12:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15594 for ; Fri, 27 Feb 1998 20:11:51 -0800 (PST) (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id XAA18384; Fri, 27 Feb 1998 23:21:16 -0500 (EST) (envelope-from mark) Message-ID: <19980227232116.35376@vmunix.com> Date: Fri, 27 Feb 1998 23:21:16 -0500 From: Mark Mayo To: current@FreeBSD.ORG Subject: I586_CALIBRATION ?? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i X-Operating-System: FreeBSD 2.2.5-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, just curious where CLK_USE_I586_CALIBRATION went ?? I used to use in my PPro, but not config (and LINT) tell me it's no longer an option. With the I586_CALIBRATION the boot message would correctly detect the CPU speed each and every time. Now it's off by +/- 15%, and my clock has gained over an hour in under a day.. :-( What should I be using here?? I have the CLK_USE_I8254_CALIBRATION option in the kernel right now. Maybe I should have nothing "extra" in there? TIA, -Mark Right now: FreeBSD 3.0-CURRENT #3: Thu Feb 26 10:30:37 EST 1998 root@spokane.vmunix.com:/srcs/FreeBSD/src/sys/compile/RingZero Timecounter "i8254" frequency 1193159 Hz cost 3411 ns Timecounter "TSC" frequency 193115865 Hz cost 278 ns CPU: Pentium Pro (193.12-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xf9ff It used to say 198.XX-MHz .. -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ "The problem is how do you build tools that understand your programs at a deeper semantic level." - James Gosling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 21:23:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22941 for freebsd-current-outgoing; Fri, 27 Feb 1998 21:23:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22933 for ; Fri, 27 Feb 1998 21:23:19 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id PAA05056 for ; Sat, 28 Feb 1998 15:53:09 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id PAA16962; Sat, 28 Feb 1998 15:53:09 +1030 (CST) (envelope-from grog) Message-ID: <19980228155309.44211@freebie.lemis.com> Date: Sat, 28 Feb 1998 15:53:09 +1030 From: Greg Lehey To: FreeBSD current users Subject: VM: Process hangs sleeping on vmpfw Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just discovered a process sleeping on vmpfw (in vm_fault). It's been there for several minutes already, so I don't think it's going to wake up: 1004 15301 250 0 -22 0 16872 432 vmpfw D v0 0:28.13 /opt/netscape/netscape The machine is still running, though I can take a dump if anybody (John?) wants to look at it. This is running a -CURRENT supped about a week ago. Here's the ID of vm_fault.c: * $Id: vm_fault.c,v 1.80 1998/02/09 06:11:23 eivind Exp $ If anybody wants access to the system, please let me know. Otherwise I'll take it down some time tomorrow and take a dump. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 22:10:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26843 for freebsd-current-outgoing; Fri, 27 Feb 1998 22:10:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26831 for ; Fri, 27 Feb 1998 22:10:08 -0800 (PST) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id GAA11079; Sat, 28 Feb 1998 06:09:13 GMT Date: Sat, 28 Feb 1998 15:09:13 +0900 (JST) From: Michael Hancock To: Greg Lehey cc: FreeBSD current users Subject: Re: VM: Process hangs sleeping on vmpfw In-Reply-To: <19980228155309.44211@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 28 Feb 1998, Greg Lehey wrote: > If anybody wants access to the system, please let me know. Otherwise > I'll take it down some time tomorrow and take a dump. John is a little under the weather now so just go ahead and take a dump later. There's been a lot of changes to the vm recently in current and it's going to one of those periods of instability. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 22:23:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28235 for freebsd-current-outgoing; Fri, 27 Feb 1998 22:23:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28230 for ; Fri, 27 Feb 1998 22:23:49 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id XAA13937; Fri, 27 Feb 1998 23:23:48 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd013917; Fri Feb 27 23:23:40 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id XAA21476; Fri, 27 Feb 1998 23:23:38 -0700 (MST) From: Terry Lambert Message-Id: <199802280623.XAA21476@usr05.primenet.com> Subject: Re: VM: Process hangs sleeping on vmpfw To: grog@lemis.com (Greg Lehey) Date: Sat, 28 Feb 1998 06:23:38 +0000 (GMT) Cc: FreeBSD-current@FreeBSD.ORG In-Reply-To: <19980228155309.44211@freebie.lemis.com> from "Greg Lehey" at Feb 28, 98 03:53:09 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've just discovered a process sleeping on vmpfw (in vm_fault). It's > been there for several minutes already, so I don't think it's going to > wake up: > > 1004 15301 250 0 -22 0 16872 432 vmpfw D v0 0:28.13 /opt/netscape/netscape > > The machine is still running, though I can take a dump if anybody > (John?) wants to look at it. This is running a -CURRENT supped about > a week ago. Here's the ID of vm_fault.c: > > * $Id: vm_fault.c,v 1.80 1998/02/09 06:11:23 eivind Exp $ > > If anybody wants access to the system, please let me know. Otherwise > I'll take it down some time tomorrow and take a dump. Check your dmesg/messages log for the following message: vnode_pager: *** WARNING *** stale FS code in system. If you have gotten this message, it means that you are trying to page out to an FS that has stale code (ie: a local media FS that does not support VOP_PUTPAGES). The FS needs corrected, so if you can identify which one it is, I can do a patch for you (it's pretty easy to make a VOP_{GET|PUT}PAGES to use the legacy code, but it must be explicitly used; doing this will [later] enable user space FS module developement to be stacked on top. The reason it's later is that there are still 151 imports for a non-stacking FS; the DDI/DKI for FS's needs a lot of cleanup to get it to the point that it can be proxied to user space). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 22:28:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28767 for freebsd-current-outgoing; Fri, 27 Feb 1998 22:28:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28761 for ; Fri, 27 Feb 1998 22:28:04 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.8/8.8.7) id IAA05667; Sat, 28 Feb 1998 08:27:42 +0200 (SAT) From: John Hay Message-Id: <199802280627.IAA05667@zibbi.mikom.csir.co.za> Subject: Re: I586_CALIBRATION ?? In-Reply-To: <19980227232116.35376@vmunix.com> from Mark Mayo at "Feb 27, 98 11:21:16 pm" To: mark@vmunix.com (Mark Mayo) Date: Sat, 28 Feb 1998 08:27:42 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, just curious where CLK_USE_I586_CALIBRATION went ?? > > I used to use in my PPro, but not config (and LINT) tell me > it's no longer an option. With the I586_CALIBRATION the boot > message would correctly detect the CPU speed each and every > time. Now it's off by +/- 15%, and my clock has gained over > an hour in under a day.. :-( > > What should I be using here?? I have the > CLK_USE_I8254_CALIBRATION option in the kernel right now. Maybe I > should have nothing "extra" in there? It is now called CLK_USE_TSC_CALIBRATION :-) It is being used on Pentium and better processors except SMP machines. 486 and below and SMP machines use the I8254 variation. You can define both in a kernel config file and the system will figure out which to use. Defining CLK_USE_TSC_CALIBRATION made a huge difference on my machine's clock here. Well that is my understanding... John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 22:38:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA00198 for freebsd-current-outgoing; Fri, 27 Feb 1998 22:38:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA00181 for ; Fri, 27 Feb 1998 22:38:14 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id RAA05130; Sat, 28 Feb 1998 17:08:10 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id RAA00464; Sat, 28 Feb 1998 17:08:10 +1030 (CST) (envelope-from grog) Message-ID: <19980228170809.59761@freebie.lemis.com> Date: Sat, 28 Feb 1998 17:08:09 +1030 From: Greg Lehey To: Terry Lambert Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: VM: Process hangs sleeping on vmpfw References: <19980228155309.44211@freebie.lemis.com> <199802280623.XAA21476@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199802280623.XAA21476@usr05.primenet.com>; from Terry Lambert on Sat, Feb 28, 1998 at 06:23:38AM +0000 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 28 February 1998 at 6:23:38 +0000, Terry Lambert wrote: >> I've just discovered a process sleeping on vmpfw (in vm_fault). It's >> been there for several minutes already, so I don't think it's going to >> wake up: >> >> 1004 15301 250 0 -22 0 16872 432 vmpfw D v0 0:28.13 /opt/netscape/netscape >> >> The machine is still running, though I can take a dump if anybody >> (John?) wants to look at it. This is running a -CURRENT supped about >> a week ago. Here's the ID of vm_fault.c: >> >> * $Id: vm_fault.c,v 1.80 1998/02/09 06:11:23 eivind Exp $ >> >> If anybody wants access to the system, please let me know. Otherwise >> I'll take it down some time tomorrow and take a dump. > > Check your dmesg/messages log for the following message: > > vnode_pager: *** WARNING *** stale FS code in system. Unfortunately, the machine froze about 30 minutes ago, and I wasn't able to get a dump. dmesg is also gone, of course. There was no such message in any of the /var/log/messages. If the VM code is still being modified, let's hope that the changes fix the cause of this one as well. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 22:53:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02395 for freebsd-current-outgoing; Fri, 27 Feb 1998 22:53:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02377; Fri, 27 Feb 1998 22:53:36 -0800 (PST) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id GAA11337; Sat, 28 Feb 1998 06:52:57 GMT Date: Sat, 28 Feb 1998 15:52:57 +0900 (JST) From: Michael Hancock To: freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: VFS_VRELE: a couple more that I missed ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Index: fdesc_vfsops.c =================================================================== RCS file: /usr/cvs/src/sys/miscfs/fdesc/fdesc_vfsops.c,v retrieving revision 1.13 diff -u -r1.13 fdesc_vfsops.c --- fdesc_vfsops.c 1997/10/12 20:24:39 1.13 +++ fdesc_vfsops.c 1998/02/28 05:30:37 @@ -71,6 +71,7 @@ struct ucred *cred, struct proc *p)); static int fdesc_vget __P((struct mount *mp, ino_t ino, struct vnode **vpp)); +static int fdesc_vrele __P((struct mount *mp, struct vnode *vp)); static int fdesc_vptofh __P((struct vnode *vp, struct fid *fhp)); /* @@ -253,6 +254,8 @@ size_t, struct proc *)))eopnotsupp) #define fdesc_vget ((int (*) __P((struct mount *, ino_t, struct vnode **))) \ eopnotsupp) +#define fdesc_vrele ((int (*) __P((struct mount *, struct vnode *))) \ + eopnotsupp) #define fdesc_vptofh ((int (*) __P((struct vnode *, struct fid *)))eopnotsupp) static struct vfsops fdesc_vfsops = { @@ -264,6 +267,7 @@ fdesc_statfs, fdesc_sync, fdesc_vget, + fdesc_vrele, fdesc_fhtovp, fdesc_vptofh, fdesc_init, Index: portal_vfsops.c =================================================================== RCS file: /usr/cvs/src/sys/miscfs/portal/portal_vfsops.c,v retrieving revision 1.19 diff -u -r1.19 portal_vfsops.c --- portal_vfsops.c 1998/01/01 08:28:11 1.19 +++ portal_vfsops.c 1998/02/28 05:42:03 @@ -273,6 +273,8 @@ size_t, struct proc *)))eopnotsupp) #define portal_vget ((int (*) __P((struct mount *, ino_t, struct vnode **))) \ eopnotsupp) +#define portal_vrele ((int (*) __P((struct mount *, struct vnode *))) \ + eopnotsupp) #define portal_vptofh ((int (*) __P((struct vnode *, struct fid *)))eopnotsupp) static struct vfsops portal_vfsops = { @@ -284,6 +286,7 @@ portal_statfs, portal_sync, portal_vget, + portal_vrele, portal_fhtovp, portal_vptofh, portal_init, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 23:44:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07614 for freebsd-current-outgoing; Fri, 27 Feb 1998 23:44:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07600 for ; Fri, 27 Feb 1998 23:44:38 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id AAA23523; Sat, 28 Feb 1998 00:44:37 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp01.primenet.com, id smtpd023516; Sat Feb 28 00:44:33 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id AAA00228; Sat, 28 Feb 1998 00:44:30 -0700 (MST) From: Terry Lambert Message-Id: <199802280744.AAA00228@usr09.primenet.com> Subject: Re: VM: Process hangs sleeping on vmpfw To: grog@lemis.com (Greg Lehey) Date: Sat, 28 Feb 1998 07:44:28 +0000 (GMT) Cc: tlambert@primenet.com, FreeBSD-current@FreeBSD.ORG In-Reply-To: <19980228170809.59761@freebie.lemis.com> from "Greg Lehey" at Feb 28, 98 05:08:09 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Check your dmesg/messages log for the following message: > > > > vnode_pager: *** WARNING *** stale FS code in system. > > Unfortunately, the machine froze about 30 minutes ago, and I wasn't > able to get a dump. dmesg is also gone, of course. There was no such > message in any of the /var/log/messages. > > If the VM code is still being modified, let's hope that the changes > fix the cause of this one as well. It would have been in your messages log or on your console, so this isn't your problem; sorry, it would have been an easy kill... looks like you are in for a ride on this one. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 27 23:57:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09205 for freebsd-current-outgoing; Fri, 27 Feb 1998 23:57:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09198 for ; Fri, 27 Feb 1998 23:57:22 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id XAA04789; Fri, 27 Feb 1998 23:57:15 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Date: Fri, 27 Feb 1998 23:57:14 -0800 (PST) From: Manfred Antar To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: VM: Process hangs sleeping on vmpfw In-Reply-To: <199802280754.XAA04775@mantar.slip.netcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 27 Feb 1998, Terry Lambert wrote: > > The machine is still running, though I can take a dump if anybody > > (John?) wants to look at it. This is running a -CURRENT supped about > > a week ago. Here's the ID of vm_fault.c: > > > > * $Id: vm_fault.c,v 1.80 1998/02/09 06:11:23 eivind Exp $ > > > > If anybody wants access to the system, please let me know. Otherwise > > I'll take it down some time tomorrow and take a dump. > > Check your dmesg/messages log for the following message: > > vnode_pager: *** WARNING *** stale FS code in system. > > If you have gotten this message, it means that you are trying to page > out to an FS that has stale code (ie: a local media FS that does not > support VOP_PUTPAGES). The FS needs corrected, so if you can identify > which one it is, I can do a patch for you (it's pretty easy to make > a VOP_{GET|PUT}PAGES to use the legacy code, but it must be explicitly > used; doing this will [later] enable user space FS module developement > to be stacked on top. The reason it's later is that there are still > 151 imports for a non-stacking FS; the DDI/DKI for FS's needs a lot > of cleanup to get it to the point that it can be proxied to user space). > I got that message on console last night and rebooted did fsck and have not seen it lately. do i need to do anything ? Thanks Manfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 28 00:12:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11171 for freebsd-current-outgoing; Sat, 28 Feb 1998 00:12:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11161 for ; Sat, 28 Feb 1998 00:12:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id AAA01283; Sat, 28 Feb 1998 00:09:59 -0800 (PST) Message-Id: <199802280809.AAA01283@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Manfred Antar cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: VM: Process hangs sleeping on vmpfw In-reply-to: Your message of "Fri, 27 Feb 1998 23:57:14 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Feb 1998 00:09:58 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Check your dmesg/messages log for the following message: > > > > vnode_pager: *** WARNING *** stale FS code in system. ... > I got that message on console last night and rebooted > did fsck and have not seen it lately. do i need to do anything ? It would help to know what filesystems you're running, and whether you are using any LKMs. Do you rebuild your LKMs when you update your kernel? The message indicates a potentially dangerous incompatability between one or more filesystems and other parts of the kernel. If this is due to oversight on our part, we would very much like to know so that it can be remedied ASAP. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 28 00:21:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12276 for freebsd-current-outgoing; Sat, 28 Feb 1998 00:21:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12271 for ; Sat, 28 Feb 1998 00:21:46 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id AAA05546; Sat, 28 Feb 1998 00:21:23 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Date: Sat, 28 Feb 1998 00:21:23 -0800 (PST) From: Manfred Antar To: Mike Smith cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: VM: Process hangs sleeping on vmpfw In-Reply-To: <199802280809.AAA01283@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 28 Feb 1998, Mike Smith wrote: > > > Check your dmesg/messages log for the following message: > > > > > > vnode_pager: *** WARNING *** stale FS code in system. > ... > > I got that message on console last night and rebooted > > did fsck and have not seen it lately. do i need to do anything ? > > It would help to know what filesystems you're running, and whether you > are using any LKMs. Do you rebuild your LKMs when you update your > kernel? > > The message indicates a potentially dangerous incompatability between > one or more filesystems and other parts of the kernel. If this is due > to oversight on our part, we would very much like to know so that it > can be remedied ASAP. > I've got NFS FFS MFS MSDOS CD9660 PROCFS compiled in kernel everything is mounted local on 1 4.3gig scsi drive: /dev/sd0a on / /dev/sd0s1e /var /dev/sd0s1f /usr I don't use any LKM's and did a make world today at noon with current as of then. I only saw the message once last night repeated 3 time on xterm console.I have not noticed any problems Manfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 28 02:25:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA21307 for freebsd-current-outgoing; Sat, 28 Feb 1998 02:25:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA21276 for ; Sat, 28 Feb 1998 02:25:45 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id DAA28622; Sat, 28 Feb 1998 03:25:36 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd028615; Sat Feb 28 03:25:35 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id DAA10560; Sat, 28 Feb 1998 03:25:31 -0700 (MST) From: Terry Lambert Message-Id: <199802281025.DAA10560@usr08.primenet.com> Subject: Re: VM: Process hangs sleeping on vmpfw To: root@mantar.slip.netcom.com (Manfred Antar) Date: Sat, 28 Feb 1998 10:25:31 +0000 (GMT) Cc: mike@smith.net.au, tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: from "Manfred Antar" at Feb 28, 98 00:21:23 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Check your dmesg/messages log for the following message: > > > > > > > > vnode_pager: *** WARNING *** stale FS code in system. > > ... > > > I got that message on console last night and rebooted > > > did fsck and have not seen it lately. do i need to do anything ? > > > > It would help to know what filesystems you're running, and whether you > > are using any LKMs. Do you rebuild your LKMs when you update your > > kernel? > > > > The message indicates a potentially dangerous incompatability between > > one or more filesystems and other parts of the kernel. If this is due > > to oversight on our part, we would very much like to know so that it > > can be remedied ASAP. > > I've got NFS FFS MFS MSDOS CD9660 PROCFS compiled in kernel everything is > mounted local on 1 4.3gig scsi drive: > /dev/sd0a on / > /dev/sd0s1e /var > /dev/sd0s1f /usr > > I don't use any LKM's and did a make world today at noon with current > as of then. I only saw the message once last night repeated 3 time on > xterm console.I have not noticed any problems This shows that you did not have anything other than FFS mounted. The warning can not occur with FFS. What this means is that the vnode pager was called to read in or write out pages on an FS that doesn't have a VOP_{GET|PUT}PAGES, and didn't have the legacy code referenced via stub functions. In simple terms, this means: (1) You had something other than an FFS filesystem mounted, and you aren't telling us about it. If you tell us about it, it's a simple fix (less than a minute). (2) Something is erroneously attempting a paging operation using an erroneous FS type. This is more serious, in that it means we are now catching some very bad behaviour that we didn't know about before. This is more complicated, because according to what we know about FreeBSD, you aren't supposed to need to do paging on an FS type that's not being used. It means that someone, somewhare, is probably stomping on a vnode's operations vector. We would need to change the warning to a panic, wait for you to repeat the problem, and then post-mortem the system dump to get things like a stack trace. I'm betting it's #1, though... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 28 02:30:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA21975 for freebsd-current-outgoing; Sat, 28 Feb 1998 02:30:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA21937 for ; Sat, 28 Feb 1998 02:29:57 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.8/8.8.8) id LAA04326; Sat, 28 Feb 1998 11:26:36 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199802281026.LAA04326@ocean.campus.luth.se> Subject: Re: Curious: "Timecounter"? In-Reply-To: <3448.888596014@critter.freebsd.dk> from Poul-Henning Kamp at "Feb 27, 98 05:13:34 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Sat, 28 Feb 1998 11:26:35 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Poul-Henning Kamp: > In message <19980227095115.05314@urh.uiuc.edu>, dannyman writes: > >arh0300 kernel log messages: > >> Timecounter "i8254" frequency 1193182 Hz cost 2524 ns > >> Timecounter "TSC" frequency 99952423 Hz cost 356 ns [...] > It means that the machine has two pieces of hardware it can use for > the construction of "time-of-day". > > "frequency" should be pretty obvious, "cost" is how long time it takes > to read the counter, and consequently a measure of the overhead by using > that timecounter. Does the system pick the fastest one and use that? Does it use both? (Maybe to see if one of the sources is drifting, etc?) /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 28 07:21:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17337 for freebsd-current-outgoing; Sat, 28 Feb 1998 07:21:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.scsn.net (scsn.net [206.25.246.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17332 for ; Sat, 28 Feb 1998 07:21:30 -0800 (PST) (envelope-from dmaddox@scsn.net) Received: from rhiannon.scsn.net ([208.133.153.147]) by mail.scsn.net (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-41950U6000L1100S0) with ESMTP id AAA40; Sat, 28 Feb 1998 10:17:56 -0500 Received: (from root@localhost) by rhiannon.scsn.net (8.8.8/8.8.7) id KAA00816; Sat, 28 Feb 1998 10:21:54 -0500 (EST) (envelope-from root) Message-ID: <19980228102154.10781@scsn.net> Date: Sat, 28 Feb 1998 10:21:54 -0500 From: dmaddox@scsn.net (Donald J. Maddox) To: Terry Lambert Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: VM: Process hangs sleeping on vmpfw Reply-To: dmaddox@scsn.net Mail-Followup-To: Terry Lambert , FreeBSD-current@FreeBSD.ORG References: <19980228155309.44211@freebie.lemis.com> <199802280623.XAA21476@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199802280623.XAA21476@usr05.primenet.com>; from Terry Lambert on Sat, Feb 28, 1998 at 06:23:38AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 28, 1998 at 06:23:38AM +0000, Terry Lambert wrote: > Check your dmesg/messages log for the following message: > > vnode_pager: *** WARNING *** stale FS code in system. > > If you have gotten this message, it means that you are trying to page > out to an FS that has stale code (ie: a local media FS that does not > support VOP_PUTPAGES). The FS needs corrected, so if you can identify > which one it is, I can do a patch for you (it's pretty easy to make > a VOP_{GET|PUT}PAGES to use the legacy code, but it must be explicitly > used; doing this will [later] enable user space FS module developement > to be stacked on top. The reason it's later is that there are still > 151 imports for a non-stacking FS; the DDI/DKI for FS's needs a lot > of cleanup to get it to the point that it can be proxied to user space). I'm getting this when accessing ext2fs filesystems... It looks like ext2fs is broken in more ways than one, but I thought you might like to know about this one :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 28 09:12:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26676 for freebsd-current-outgoing; Sat, 28 Feb 1998 09:12:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26653 for ; Sat, 28 Feb 1998 09:11:59 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id JAA02366; Sat, 28 Feb 1998 09:11:36 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Date: Sat, 28 Feb 1998 09:11:36 -0800 (PST) From: Manfred Antar To: Terry Lambert cc: mike@smith.net.au, current@FreeBSD.ORG Subject: Re: VM: Process hangs sleeping on vmpfw In-Reply-To: <199802281025.DAA10560@usr08.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 28 Feb 1998, Terry Lambert wrote: > > > > > Check your dmesg/messages log for the following message: > > > > > > > > > > vnode_pager: *** WARNING *** stale FS code in system. > > > ... > > > > I got that message on console last night and rebooted > > > > did fsck and have not seen it lately. do i need to do anything ? > > > > > > It would help to know what filesystems you're running, and whether you > > > are using any LKMs. Do you rebuild your LKMs when you update your > > > kernel? > > > > > > The message indicates a potentially dangerous incompatability between > > > one or more filesystems and other parts of the kernel. If this is due > > > to oversight on our part, we would very much like to know so that it > > > can be remedied ASAP. > > > > I've got NFS FFS MFS MSDOS CD9660 PROCFS compiled in kernel everything is > > mounted local on 1 4.3gig scsi drive: > > /dev/sd0a on / > > /dev/sd0s1e /var > > /dev/sd0s1f /usr > > > > I don't use any LKM's and did a make world today at noon with current > > as of then. I only saw the message once last night repeated 3 time on > > xterm console.I have not noticed any problems > > This shows that you did not have anything other than FFS mounted. The > warning can not occur with FFS. > > What this means is that the vnode pager was called to read in or write > out pages on an FS that doesn't have a VOP_{GET|PUT}PAGES, and didn't > have the legacy code referenced via stub functions. > > In simple terms, this means: > > (1) You had something other than an FFS filesystem mounted, and > you aren't telling us about it. If you tell us about it, it's > a simple fix (less than a minute). > > (2) Something is erroneously attempting a paging operation using > an erroneous FS type. This is more serious, in that it means > we are now catching some very bad behaviour that we didn't > know about before. This is more complicated, because according > to what we know about FreeBSD, you aren't supposed to need to > do paging on an FS type that's not being used. It means that > someone, somewhare, is probably stomping on a vnode's operations > vector. We would need to change the warning to a panic, wait > for you to repeat the problem, and then post-mortem the system > dump to get things like a stack trace. > > I'm betting it's #1, though... > It is very possible that I had a cdrom (FreeBSD Ports) mounted and was copying some of the distfiles.The console was in another window and i didn't see when the message happened. Manfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 28 10:09:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01240 for freebsd-current-outgoing; Sat, 28 Feb 1998 10:09:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (root@dnttm.wave.ras.ru [194.85.104.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01191 for ; Sat, 28 Feb 1998 10:09:28 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.8.5/8.8.5/IP-3) with UUCP id VAA00816; Sat, 28 Feb 1998 21:04:45 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.8.8/8.8.7) with ESMTP id VAA02290; Sat, 28 Feb 1998 21:13:10 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199802281813.VAA02290@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Terry Lambert cc: FreeBSD-current@FreeBSD.ORG Subject: Re: VM: Process hangs sleeping on vmpfw In-reply-to: Your message of "Sat, 28 Feb 1998 06:23:38 GMT." <199802280623.XAA21476@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Feb 1998 21:13:09 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > Check your dmesg/messages log for the following message: > > vnode_pager: *** WARNING *** stale FS code in system. > > If you have gotten this message, it means that you are trying to page > out to an FS that has stale code (ie: a local media FS that does not > support VOP_PUTPAGES). In fact, this mean that you are trying to _page in from_ FS that was recently broken (i.e. local media FS that does not support VOP_GETPAGES). vnode_pager_putpages does not check for EOPNOTSUPP. I thought it is job of the submitter/committer to find all places broken by the changes and fix them. Here is a (partial?) list of broken filesystems: NFS, CD9660, EXT2FS, MSDOSFS. > The FS needs corrected, so if you can identify > which one it is, I can do a patch for you (it's pretty easy to make > a VOP_{GET|PUT}PAGES to use the legacy code, but it must be explicitly > used; doing this will [later] enable user space FS module developement > to be stacked on top. Well, I don't know what do you need for user space FS module development, but I still believe that you introduced lot of unnecessary complexity. First, why default/standard/generic getpages/putpages routines does not have interface of VOP_GETPAGES/VOP_PUTPAGES vnode operations? It would be easier for a filesystem to just add some entries to their operations tables than also cut&paste implementation (even trivial) of these operations from ffs. Second, why don't put the operations to default_vnodeop_entries? It is used exactly by local media filesystems. Stacking layers use bypass routines instead (unionfs is an exception). So, filesystems even would not notice this change, until they really want their own implementation of getpages/putpages What is wrong in the above? I can send a patch for you... It is indeed pretty easy... Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 28 14:57:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29414 for freebsd-current-outgoing; Sat, 28 Feb 1998 14:57:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29405 for ; Sat, 28 Feb 1998 14:57:55 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id PAA12596; Sat, 28 Feb 1998 15:57:54 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd012552; Sat Feb 28 15:57:45 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id PAA08480; Sat, 28 Feb 1998 15:57:42 -0700 (MST) From: Terry Lambert Message-Id: <199802282257.PAA08480@usr08.primenet.com> Subject: Re: VM: Process hangs sleeping on vmpfw To: dima@tejblum.dnttm.rssi.ru (Dmitrij Tejblum) Date: Sat, 28 Feb 1998 22:57:42 +0000 (GMT) Cc: tlambert@primenet.com, FreeBSD-current@FreeBSD.ORG In-Reply-To: <199802281813.VAA02290@tejblum.dnttm.rssi.ru> from "Dmitrij Tejblum" at Feb 28, 98 09:13:09 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, the warning is emitted in the getpages. If the getpages fails, you are supposed to be trying a putpages. > In fact, this mean that you are trying to _page in from_ FS that was > recently broken (i.e. local media FS that does not support > VOP_GETPAGES). vnode_pager_putpages does not check for EOPNOTSUPP. > I thought it is job of the submitter/committer to find all places > broken by the changes and fix them. There are counter examples, but you're right, that's not good practice. The thing here is that it really wants testing by people who use the FS's. The warning was Mike's (good) addition; I personally wanted to panic when it happened. Before this gets blown out of proportion, though, there are two ways to approach a fix. I would like to use the first: (1) Fix the FS's on a case-by-case basis. (2) Hack the get/put routines to see the EOPNOTSUPP, issue a warning, and then fallback to the old behaviour. I'm against #2 because if it's not considered a serious warning, the FS's won't find themselves fixed like they should because people will blow off reporting the problem. > Here is a (partial?) list of broken filesystems: NFS, CD9660, > EXT2FS, MSDOSFS. Local media FS's for the most part, yes. The NFS case is rather problematic (find out why, below). The CD9660 needs a generic getpages, but a read-only (ie: release-only) putpages. > > The FS needs corrected, so if you can identify > > which one it is, I can do a patch for you (it's pretty easy to make > > a VOP_{GET|PUT}PAGES to use the legacy code, but it must be explicitly > > used; doing this will [later] enable user space FS module developement > > to be stacked on top. > > Well, I don't know what do you need for user space FS module > development, but I still believe that you introduced lot of unnecessary > complexity. Stacking FS's will have similar problems until they correctly implement the "bypass" mechanisms. The reson for the change is not purely for user space FS developement. The original rationale was posted when I posted the URL for the patches. > First, why default/standard/generic getpages/putpages routines does not > have interface of VOP_GETPAGES/VOP_PUTPAGES vnode operations? It would be > easier for a filesystem to just add some entries to their operations > tables than also cut&paste implementation (even trivial) of these > operations from ffs. Look at /sys/ufs/ufs/ufs_readwrite.c: ========================================================================== /* * put page routine * * XXX By default, wimp out... note that a_offset is ignored (and always * XXX has been). */ int ffs_putpages(ap) struct vop_putpages_args *ap; { return vnode_pager_generic_putpages(ap->a_vp, ap->a_m, ap->a_count, ap->a_sync, ap->a_rtvals); } ========================================================================== This is what I do in the case of a local media FS without a specific get/put implementation. This is exactly the fix that needs to go into the local media FS's (with the 'put' replaced by 'get' and the argument list adjusted). The CD9660 code should have a variant putpages (obviously). > Second, why don't put the operations to default_vnodeop_entries? It is > used exactly by local media filesystems. Stacking layers use bypass > routines instead (unionfs is an exception). So, filesystems even would > not notice this change, until they really want their own implementation > of getpages/putpages > > What is wrong in the above? Unionfs. Specifically, the point is that the unionfs implementation should fan out to the correct underlying implementation. This means it shouldn't go into the default. Secondly, you can't make FS-specific optimizations. One example here is the preterbation of the putpages by the soft updates code... an FFS-specific thing that should be reflected only in the FFS putpages. Another example would be that the generic putpage doesn't know about clustering (except what VOP_WRITE can do) for partial cluster writes, etc.. > I can send a patch for you... It is indeed pretty easy... See above for the patch. It's the identification problem and the stacking problem that I wanted to handle on a case-by-case basis. As I said, it's possible to make this change go transparent (#2, above); I would actually prefer an implementation that does *not* define the generic code as default ops, so if it has to go transparent, it should go transparent that way, not the default ops way, so at least there are warning messages emitted. Have you looked at John's comments about intended complexity in the /sys/vm/vnode_pager.c? Right now, the generic mechanism seperates (but does not yet remove) the complexity he's talking about in those comments. This is the intended direction in the VM code; I'd like to follow it through if we can, instead of crippling it. You should also follow the NFS case in vnode_pager_generic_getpages and look at all the other vp->v_mount references. Look what the change means to VOP_BMAP, specifically with regard to the assumptions comment in vnode_pager_generic_getpages and vnode_pager_input_smlfs's being called -- with the same assumptions but without the test. It's pretty obvious that the VOP_BMAP return test is equal to the NFS test. This code is at the heart of a lot of problems, and I'd like to take it slow... Any help would, of course, be appreciated. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 28 15:28:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03688 for freebsd-current-outgoing; Sat, 28 Feb 1998 15:28:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03682 for ; Sat, 28 Feb 1998 15:28:49 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id PAA09995; Sat, 28 Feb 1998 15:28:29 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802282328.PAA09995@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: dima@tejblum.dnttm.rssi.ru (Dmitrij Tejblum), FreeBSD-current@FreeBSD.ORG Subject: Re: VM: Process hangs sleeping on vmpfw In-reply-to: Your message of "Sat, 28 Feb 1998 22:57:42 GMT." <199802282257.PAA08480@usr08.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Feb 1998 15:28:29 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Terry, Try to archive in your web page the questions and responses to general issues with respect to the file and vm sub-systems . That combine with your patches, a road map, cool references to relevant material will make one of hell of a web page 8) Best Regards, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 28 15:54:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06685 for freebsd-current-outgoing; Sat, 28 Feb 1998 15:54:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06680 for ; Sat, 28 Feb 1998 15:54:07 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id QAA00595; Sat, 28 Feb 1998 16:53:58 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd000586; Sat Feb 28 16:53:52 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id QAA11825; Sat, 28 Feb 1998 16:53:45 -0700 (MST) From: Terry Lambert Message-Id: <199802282353.QAA11825@usr08.primenet.com> Subject: Re: VM: Process hangs sleeping on vmpfw To: dmaddox@scsn.net Date: Sat, 28 Feb 1998 23:53:45 +0000 (GMT) Cc: FreeBSD-current@FreeBSD.ORG In-Reply-To: <19980228102154.10781@scsn.net> from "Donald J. Maddox" at Feb 28, 98 10:21:54 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Check your dmesg/messages log for the following message: > > > > vnode_pager: *** WARNING *** stale FS code in system. > > > > If you have gotten this message, it means that you are trying to page > > out to an FS that has stale code (ie: a local media FS that does not > > support VOP_PUTPAGES). The FS needs corrected, so if you can identify > > which one it is, I can do a patch for you [ ... ] > I'm getting this when accessing ext2fs filesystems... It looks like ext2fs > is broken in more ways than one, but I thought you might like to know about > this one :-) Here is a patch that updates ext2fs. This should probably be committed. I will need to update my sources to get a patch that cleanly applies against MSDOSFS (there are some changes I havent checked out, but I have been working on a security related patch, so my tree is in a bit of disarray as I move it over). If someone wants to do *exactly* this for MSDOSFS and NFS and gets to it before I do... all the better; this is low-hanging fruit and a chance to familiarize yourself with some of the workings of the VFS without much chance of shooting your foot off. Patch follows signature (it's small and pretty obvious in light of my previous post)... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. =========================================================================== Index: gnu/ext2fs/ext2_vnops.c =================================================================== RCS file: /b/cvstree/ncvs/src/sys/gnu/ext2fs/ext2_vnops.c,v retrieving revision 1.33 diff -c -r1.33 ext2_vnops.c *** 1.33 1998/02/06 12:13:03 --- ext2_vnops.c 1998/02/28 23:47:14 *************** *** 63,68 **** --- 63,69 ---- #include #include #include + #include #include #include *************** *** 88,93 **** --- 89,96 ---- static int ext2_create __P((struct vop_create_args *)); static int ext2_mknod __P((struct vop_mknod_args *)); static int ext2_symlink __P((struct vop_symlink_args *)); + static int ext2_getpages __P((struct vop_getpages_args *)); + static int ext2_putpages __P((struct vop_putpages_args *)); /* Global vfs data structures for ufs. */ vop_t **ext2_vnodeop_p; *************** *** 109,114 **** --- 112,119 ---- { &vop_create_desc, (vop_t *) ext2_create }, { &vop_mknod_desc, (vop_t *) ext2_mknod }, { &vop_symlink_desc, (vop_t *) ext2_symlink }, + { &vop_getpages_desc, (vop_t *) ext2_getpages }, + { &vop_putpages_desc, (vop_t *) ext2_putpages }, { NULL, NULL } }; static struct vnodeopv_desc ext2fs_vnodeop_opv_desc = *************** *** 1198,1201 **** --- 1203,1234 ---- ip->i_flag |= IN_CHANGE; vput(tvp); return (error); + } + + /* + * get page routine + * + * XXX By default, wimp out... note that a_offset is ignored (and always + * XXX has been). + */ + int + ext2_getpages(ap) + struct vop_getpages_args *ap; + { + return vnode_pager_generic_getpages(ap->a_vp, ap->a_m, ap->a_count, + ap->a_reqpage); + } + + /* + * put page routine + * + * XXX By default, wimp out... note that a_offset is ignored (and always + * XXX has been). + */ + int + ext2_putpages(ap) + struct vop_putpages_args *ap; + { + return vnode_pager_generic_putpages(ap->a_vp, ap->a_m, ap->a_count, + ap->a_sync, ap->a_rtvals); } =========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 28 16:00:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07820 for freebsd-current-outgoing; Sat, 28 Feb 1998 16:00:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07811 for ; Sat, 28 Feb 1998 16:00:13 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id RAA01478; Sat, 28 Feb 1998 17:00:08 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd001441; Sat Feb 28 16:59:59 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id QAA12165; Sat, 28 Feb 1998 16:59:55 -0700 (MST) From: Terry Lambert Message-Id: <199802282359.QAA12165@usr08.primenet.com> Subject: Re: VM: Process hangs sleeping on vmpfw To: root@mantar.slip.netcom.com (Manfred Antar) Date: Sat, 28 Feb 1998 23:59:55 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, current@FreeBSD.ORG In-Reply-To: from "Manfred Antar" at Feb 28, 98 09:11:36 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It is very possible that I had a cdrom (FreeBSD Ports) mounted and was > copying some of the distfiles.The console was in another window and > i didn't see when the message happened. > Manfred Anyone having problems with the CD9660 code, let me know. You *could* use the ext2fs patch (names changed, only) but... something grates me about trying to page out to read-only media. I can't figure out what it is.. ;-). I'd like to squash the CD9660 the right way, but that's one that will take a bit more than a minute to do. Is there a call, at all, for being able to mount a CD9660 read/write? I've thought about this before, but it seems like it's not a very good idea: some poor schmuck will mount his WORM drive R/W and get access times written all over his disk 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 28 17:39:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19446 for freebsd-current-outgoing; Sat, 28 Feb 1998 17:39:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19439 for ; Sat, 28 Feb 1998 17:39:29 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id SAA05860 for ; Sat, 28 Feb 1998 18:39:24 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp03.primenet.com, id smtpd005845; Sat Feb 28 18:39:14 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id SAA02325 for current@freebsd.org; Sat, 28 Feb 1998 18:39:15 -0700 (MST) From: Terry Lambert Message-Id: <199803010139.SAA02325@usr04.primenet.com> Subject: Patches in support of security To: current@FreeBSD.ORG Date: Sun, 1 Mar 1998 01:39:15 +0000 (GMT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here are a set of patches that implement Juniper-like trusted and untrusted interfaces (the default is untrusted). They incidently bump the interface flags from 16 to 32 buts (yea!): http://www.freebsd.org/~terry/DIFF.TRUST.txt http://www.freebsd.org/~terry/DIFF.TRUST http://www.freebsd.org/~terry/DIFF.ifconfig ======================================================================= The Juniper firewall code supports the idea of trusted interfaces. These patches add the ifconfig flags "trusted" and "-trusted" in support of a "poor man's Juniper firewall". An interface may be marked trusted by root. The default is untrusted. When a interface is marked "trusted", TCP sockets may be queried to determine if they will route over trusted or untrusted interfaces. Note: this code does not take into account the possibility of asymmetric routes! The basic idea is that a daemon can determine if a connection is made via a trusted or untrusted interface, and respond accordingly. A potential use of this code is SMTP relay. If a connection is made via a trusted interface, you could allow SMTP relay, and if made via an untrusted interface, deny it. There are a lot of other possibilities, including allowing/denying VPN startup, etc., etc.. For a firewall, the interior net would be trusted and the exterior would be untrusted. This would mean (in the relay example) that trusted hosts would be permitted to relay mail through the SMTP server, and untrusted hosts would not. A server tests for "trustworthyness" of an interface by: int trusted; int trustedlen = sizeof(trusted); ... if( !getsockopt( s, IPPROTO_TCP, TCP_TRUSTED, &trusted, &trustedlen)) trusted = 0; ... if( trusted) { ... } else { ... } Note: this applies to only TCP sockets! Readers may engage in future work: (1) set the flag in the socket at connect time rather than using the route (support for asymmetric routes). (2) Allow UDP socket route queries (ie: "if I were to send a packet via this socket, where would it go?"). EOF ======================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 28 18:59:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28225 for freebsd-current-outgoing; Sat, 28 Feb 1998 18:59:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28220 for ; Sat, 28 Feb 1998 18:59:30 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id VAA00479; Sat, 28 Feb 1998 21:59:10 -0500 (EST) (envelope-from toor) Message-Id: <199803010259.VAA00479@dyson.iquest.net> Subject: Re: VM: Process hangs sleeping on vmpfw In-Reply-To: <199802282359.QAA12165@usr08.primenet.com> from Terry Lambert at "Feb 28, 98 11:59:55 pm" To: tlambert@primenet.com (Terry Lambert) Date: Sat, 28 Feb 1998 21:59:10 -0500 (EST) Cc: root@mantar.slip.netcom.com, tlambert@primenet.com, mike@smith.net.au, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert said: > > Is there a call, at all, for being able to mount a CD9660 read/write? > I've thought about this before, but it seems like it's not a very > good idea: some poor schmuck will mount his WORM drive R/W and get > access times written all over his disk 8-(. > The only way that I can think of is that permissions aren't checked correctly or a pmap bug. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 28 19:48:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02967 for freebsd-current-outgoing; Sat, 28 Feb 1998 19:48:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.31.78.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02930 for ; Sat, 28 Feb 1998 19:48:38 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id WAA23380; Sat, 28 Feb 1998 22:48:29 -0500 (EST) Date: Sat, 28 Feb 1998 22:48:29 -0500 (EST) From: "Matthew N. Dodd" To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: Patches in support of security In-Reply-To: <199803010139.SAA02325@usr04.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 1 Mar 1998, Terry Lambert wrote: > Here are a set of patches that implement Juniper-like trusted > and untrusted interfaces (the default is untrusted). > > They incidently bump the interface flags from 16 to 32 buts (yea!): > > http://www.freebsd.org/~terry/DIFF.TRUST.txt > http://www.freebsd.org/~terry/DIFF.TRUST > http://www.freebsd.org/~terry/DIFF.ifconfig This looks useful. (or at least is a useful first step) While some policies may be enforced with creative firewall rules, these patches provide a clean interface at the application level. Is it possible to have them committed? /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message