From owner-freebsd-current Sun Dec 12 2:16:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id E6AC514F83; Sun, 12 Dec 1999 02:16:38 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11x637-000DrV-00; Sun, 12 Dec 1999 10:16:17 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id LAA17078; Sun, 12 Dec 1999 11:16:29 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <385375FD.4DC0EFF7@scc.nl> Date: Sun, 12 Dec 1999 11:16:29 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Takahashi Yoshihiro Cc: msmith@freebsd.org, current@freebsd.org Subject: Re: make world is failed on pc98 References: <19991211230552P.nyan@dd.catv.ne.jp> <38526700.70C5CBF@scc.nl> <199912120121.RAA00570@mass.cdrom.com> <19991212131847U.nyan@dd.catv.ne.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Takahashi Yoshihiro wrote: > > > BTW: Is there a special reason to have boot2 in aout? > > Because nobody transplant from the i386 boot2 :-). > FreeBSD(98) porting team is always suffering from a shortage of > workers. > > In article <199912120121.RAA00570@mass.cdrom.com> > Mike Smith writes: > > > Only in the longer term, I think. How hard would it be to port the 'new' > > i386 boot2? > > There are few people who are knowledgeable about pc98 boot sequence. > And that we all have our regular work. So, it is very difficult to > port the i386 boot2 to pc98. Please correct me if I'm wrong while I'm drawing the picture: Since pc98 only has a specialized boot2 and thus shares boot0 and boot1 with other architectures, it can be assumed that an ELF boot2 doesn't need any special hacking in boot0 and/or boot1, right? boot2 is already capable of loading ELF, right? Isn't it therefore enough to just compile boot2 as ELF? In other words, what are the problems? -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 2:17:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.hanarotel.net (mail.hananet.net [210.180.98.70]) by hub.freebsd.org (Postfix) with ESMTP id 634BC1508E; Sun, 12 Dec 1999 02:16:59 -0800 (PST) (envelope-from cjh@kr.FreeBSD.ORG) Received: from gradius.myhome ([210.205.33.54]) by mail.hanarotel.net (Post.Office MTA v3.5.3 release 223 ID# 200-56547U100000L100000S0V35) with ESMTP id net; Sun, 12 Dec 1999 19:23:21 +0900 Received: (from cjh@localhost) by gradius.myhome (8.9.3/8.9.3) id TAA02970; Sun, 12 Dec 1999 19:16:52 +0900 (KST) (envelope-from cjh) To: Jon Hamilton Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: ppp over pty: trying to detect CD References: <19991212032201.5BF1150@woodstock.monkey.net> From: "CHOI, Junho" Date: 12 Dec 1999 19:16:52 +0900 In-Reply-To: Jon Hamilton's message of "Sat, 11 Dec 1999 21:22:01 -0600" Message-ID: <86bt7wlazv.fsf@gradius.myhome> Lines: 32 X-Mailer: Gnus v5.7/Emacs 20.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "JH" == Jon Hamilton writes: JH> Running -current from this afternoon, I am having a strange JH> symptom with ppp over a pty; ppp does not detect that the pty JH> does not support carrier, and will cycle once per second JH> waiting for CD to appear. Putting ``set cd off'' in my JH> ppp.conf for that target fixed the problem, but I thought I'd JH> mention it nonetheless, since that didn't used to be JH> required. Certainly not all that big a deal, but I thought it JH> was worth a mention. JH> FreeBSD 4.0-CURRENT #13: Sat Dec 11 20:31:42 CST 1999 I am using 3-STABLE but I have the same problem with you. I think it comes after adding pppoe support in pppd(after 3.3-RELEASE). I am -STABLE user but I had to back to 3.3-RELEASE's ppp... I am using ADSL service with pptpclient. JH> and the syslog with debugging turned on, with no "set cd" in the config: JH> Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: deflink: Using tty_Timeout [0x8072d44] JH> Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: Waiting for carrier JH> Dec 11 20:48:21 woodstock ppp[3106]: tun1: Debug: deflink: Using tty_Timeout [0x8072d44] JH> Dec 11 20:48:21 woodstock ppp[3106]: tun1: Debug: Waiting for carrier JH> [ and on and on and on ] -- +++ Any opinions in this posting are my own and not those of my employers +++ CHOI, Junho - Korea FreeBSD Users Group - Public Service, Youido Post Office - Web Data Bank To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 2:24:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 05A5514BE2 for ; Sun, 12 Dec 1999 02:24:22 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id LAA16583; Sun, 12 Dec 1999 11:23:59 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Julian Elischer Cc: "Jordan K. Hubbard" , John Robert LoVerso , freebsd-current@FreeBSD.ORG Subject: Re: Modules and sysctl tree In-reply-to: Your message of "Sat, 11 Dec 1999 22:42:25 PST." Date: Sun, 12 Dec 1999 11:23:58 +0100 Message-ID: <16581.944994238@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Jul ian Elischer writes: [sysctlfs] >Linux have basically done this in their procfs. And have recently started to wonder if that wasn't a mistake I've heard. I would regard sysctlfs as a grave mistake. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 2:51:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 82EC614DF0 for ; Sun, 12 Dec 1999 02:51:49 -0800 (PST) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id QAA52964; Sun, 12 Dec 1999 16:50:29 +0600 (NOVT) (envelope-from nnd) Date: Sun, 12 Dec 1999 16:50:29 +0600 (NOVT) Message-Id: <199912121050.QAA52964@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: Kenneth Wayne Culver Cc: current@freebsd.org Subject: Re: Audio support [was Re: HEADSUP: wd driver will be retired!] In-Reply-To: User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Kenneth Wayne Culver wrote: > Just a question which I'm not sure is soundcard related. My xmms no longer > starts up anymore, it just hangs in Poll before it actually puts anything > on the display, is that because /dev/dsp isn't working? Thw 'xmms' problem is not soundcard related. It is uthreads related. Daniel Eischen already have the patches to solve this problem. In the meantime you can try to make the following: Manually unpack your default Skin (now it is 'zip'-ped - is it ?). After that your 'xmms' will start to make noises (somebody calla them music ;-). N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 2:55:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 8404514F0A for ; Sun, 12 Dec 1999 02:55:12 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id AAA06211; Sun, 12 Dec 1999 00:03:49 GMT (envelope-from nik) Date: Sun, 12 Dec 1999 00:03:49 +0000 From: Nik Clayton To: Poul-Henning Kamp Cc: Nate Williams , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991212000349.A4242@catkin.nothing-going-on.org> References: <199912101752.KAA19725@mt.sri.com> <6120.944848909@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <6120.944848909@critter.freebsd.dk>; from Poul-Henning Kamp on Fri, Dec 10, 1999 at 07:01:49PM +0100 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 10, 1999 at 07:01:49PM +0100, Poul-Henning Kamp wrote: > The ata driver has been available for you and other to test for a long > time. That may be the case, but the vast majority of our users don't run -current, for good reason, and so are in no position to test it. 4.0 will be their first exposure to ata, and you should definitely expect it to have problems that have been shaken out of the wd driver. Poul, I'd like to know what's wrong with (1) Putting ata in GENERIC (2) Keeping wd in LINT, commented out (3) A big notice in UPDATING, saying that ata is the replacement for wd. Make wd require "options I_WANT_WD" or something similar, so that people can't simply re-config their existing configuration file. That gives you the best of all possible worlds. Most people can move to ata immediately. Those people that can't can still run 4.0 with wd, and will know that it's going away for 4.1, and can take part in reporting the problems they're having with ata. N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 2:57: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 7C6BB15073 for ; Sun, 12 Dec 1999 02:57:06 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id LAA16927; Sun, 12 Dec 1999 11:56:08 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Wilko Bulte Cc: Bob Vaughan , nate@mt.sri.com, current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Sat, 11 Dec 1999 19:29:25 +0100." <19991211192925.C77444@yedi.iaf.nl> Date: Sun, 12 Dec 1999 11:56:08 +0100 Message-ID: <16925.944996168@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991211192925.C77444@yedi.iaf.nl>, Wilko Bulte writes: >On Sat, Dec 11, 1999 at 09:00:52AM -0800, Bob Vaughan wrote: >> > Subject: Re: HEADSUP: wd driver will be retired! >> > Date: Fri, 10 Dec 1999 19:19:43 +0100 >> > From: Poul-Henning Kamp >> > >> > >> > Maybe we should put a special marker in -currents sendmail and >> > reject all email to the current list if they don't originate >> > from such a system. >> > >> > >Seriously: I don't expect to be meant seriously. Right? Right. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 2:58: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 6571415195 for ; Sun, 12 Dec 1999 02:57:56 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id LAA80707 for current@FreeBSD.org; Sun, 12 Dec 1999 11:47:15 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Sun, 12 Dec 1999 11:47:09 +0100 From: Marcel Moolenaar Message-ID: <38537D2D.CA2C3DB3@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <199912112149.NAA71033@bubba.whistle.com>, <91986.944949603@zippy.cdrom.com> Subject: Re: Modules and sysctl tree Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > > In other words, it's not a problem specific to KLD's .. but > > it's still a problem :-) > > Which raises an important issue - other than walking the sysctl tree > regularly looking for changes, how does such an application become > aware that the sysctl space has changed? The same holds true for a > dynamic /dev, of course, though one assumes one can at least hack a > solution with devfs where you stat the directory and compare its > current mod time with a saved one, only walking the directory if you > see a change. I don't see any kind of mechanism for doing this > with sysctl, even as a gross hack. It crossed my mind when implementing Linuxulator sysctl variables. IIRC, I though that it might be a good idea to have a `kern.modules' tree that holds which modules are loaded (either dynamicly or staticly). Since each sysctl variable belongs to a module (be it the kernel core), walking the `kern.modules' tree is sufficient to detect changes in the rest of the sysctl tree. It can also used as an alternative to find out if module foobar is loaded, for example. An alternative to this is to only add modules to kern.modules if it changes the sysctl tree. The number of variables would be limited to only one or two (maybe three :-). -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 2:59:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id BB32714C0E for ; Sun, 12 Dec 1999 02:59:15 -0800 (PST) (envelope-from vallo@solaris.matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id F14452CE4E; Sun, 12 Dec 1999 12:58:59 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id F05DC10B; Sun, 12 Dec 1999 12:59:01 +0200 (EET) Date: Sun, 12 Dec 1999 12:59:01 +0200 From: Vallo Kallaste To: Doug White Cc: Soren Schmidt , Jean Louis Ntakpe , current@FreeBSD.ORG Subject: Re: ata: lost disk contact errors [was: Re: HEADSUP: wd driver will be retired!] Message-ID: <19991212125901.A38377@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <19991211181115.A36357@myhakas.matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Doug White on Sat, Dec 11, 1999 at 12:57:04PM -0800 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 11, 1999 at 12:57:04PM -0800, Doug White wrote: > > I'm getting the "lost disk contact" messages every now and then, but > > only on our mp3 machine with PIIX3 controller and IBM UDMA/66 disk. It's > > an PPro machine with Intel mobo. Can it be related to newer IBM disks? > > Depends on what 'now and then' is. The Deskstar series of drives was not > intended to run 24/7, and therefore shut themselves down every week to > clean the heads. Mhm, now I remember the discussion in -current list some time ago. It can be, yes, but I need to follow the logs to say for sure. About month ago the messages appeared several times per day, not per week. Thank you refreshing my memory :-) -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 2:59:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id A95C3150B7; Sun, 12 Dec 1999 02:59:43 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id LAA16970; Sun, 12 Dec 1999 11:59:39 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Nik Clayton Cc: Nate Williams , current@freebsd.org Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Sun, 12 Dec 1999 00:03:49 GMT." <19991212000349.A4242@catkin.nothing-going-on.org> Date: Sun, 12 Dec 1999 11:59:38 +0100 Message-ID: <16968.944996378@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991212000349.A4242@catkin.nothing-going-on.org>, Nik Clayton writ es: >On Fri, Dec 10, 1999 at 07:01:49PM +0100, Poul-Henning Kamp wrote: >> The ata driver has been available for you and other to test for a long >> time. > >That may be the case, but the vast majority of our users don't run >-current, for good reason, and so are in no position to test it. 4.0 >will be their first exposure to ata, and you should definitely expect >it to have problems that have been shaken out of the wd driver. > >Poul, I'd like to know what's wrong with > > (1) Putting ata in GENERIC > > (2) Keeping wd in LINT, commented out This will not force CURRENT users to change their configs, a config with wd in it will still work unchanged. Peter just added code for issuing warnings, but I'd prefer for the build to actually break until people fix it. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 4:34:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 7E1B414F83 for ; Sun, 12 Dec 1999 04:33:59 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from tecra.nlsystems.com (tecra.nlsystems.com [10.0.0.5]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id MAA34831; Sun, 12 Dec 1999 12:42:47 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 12 Dec 1999 12:42:47 +0000 (GMT) From: Doug Rabson To: Marcel Moolenaar Cc: current@freebsd.org Subject: Re: Audio support [was Re: HEADSUP: wd driver will be retired!] In-Reply-To: <385257BE.761B4F92@scc.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 Sat, 11 Dec 1999, Marcel Moolenaar wrote: > "Jordan K. Hubbard" wrote: > > > Actually, I'm sad to say that our shiny new sound system does *not* > > work for some of the most popular audio chipsets on the market today > > (where the older "luigi" sound system did support them) and this is a > > matter of significant concern to some folks, myself included. > > The recent commits made existing support even worse. Yes, I'm talking > about the ESS1888. It's more dead than before. I'll have to make the > noise myself these days, and I can tell you it's no opera :-) > > In short: Gimme patches! I'll be happy to test and, in a spare hour, can > even do some trial and error on my own. I'm not going to beg... Which commits broke the ESS1888? I haven't tested it for a couple of weeks but I have an ESS1888 in one of my alpha boxes which worked a while ago after I fixed a few bits and pieces in the driver. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 5: 8: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 98C9B14DFC; Sun, 12 Dec 1999 05:07:57 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id MAA97196; Sun, 12 Dec 1999 12:25:20 GMT (envelope-from nik) Date: Sun, 12 Dec 1999 12:25:20 +0000 From: Nik Clayton To: Poul-Henning Kamp Cc: Nik Clayton , Nate Williams , current@freebsd.org Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991212122519.A95550@catkin.nothing-going-on.org> References: <19991212000349.A4242@catkin.nothing-going-on.org> <16968.944996378@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <16968.944996378@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Dec 12, 1999 at 11:59:38AM +0100 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 12, 1999 at 11:59:38AM +0100, Poul-Henning Kamp wrote: > >Poul, I'd like to know what's wrong with > > > > (1) Putting ata in GENERIC > > > > (2) Keeping wd in LINT, commented out > > This will not force CURRENT users to change their configs, a config > with wd in it will still work unchanged. Peter just added code > for issuing warnings, but I'd prefer for the build to actually > break until people fix it. wd.c #ifndef I_WANT_WD #error "You must really, really, really want to use this driver." #error "See UPDATING for details." #else ... #endif If someone takes their existing config file and tries to build a kernel from it, it will break. That meets every definition of "force CURRENT users to change their configs" that I can think of. N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 5:10:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id DC7F114F86 for ; Sun, 12 Dec 1999 05:10:31 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11x8lR-000FX3-00; Sun, 12 Dec 1999 13:10:13 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id OAA40807; Sun, 12 Dec 1999 14:10:26 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <38539EC2.7894323A@scc.nl> Date: Sun, 12 Dec 1999 14:10:26 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Doug Rabson Cc: current@freebsd.org Subject: Re: Audio support [was Re: HEADSUP: wd driver will be retired!] References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > > > The recent commits made existing support even worse. Yes, I'm talking > > about the ESS1888. It's more dead than before. I'll have to make the > > noise myself these days, and I can tell you it's no opera :-) > > > > In short: Gimme patches! I'll be happy to test and, in a spare hour, can > > even do some trial and error on my own. I'm not going to beg... > > Which commits broke the ESS1888? I haven't tested it for a couple of weeks > but I have an ESS1888 in one of my alpha boxes which worked a while ago > after I fixed a few bits and pieces in the driver. The first breakage was with the introduction of newmidi IIRC. The mixer worked, but any dsp related functions were broken. See: sys/dev/sound/isa/es1888.c rev 1.3  In recent kernel even the mixer is dead and the soundcard is left in a state where all volumes are zeroed, preventing audio CD playing as well. See: sys/dev/sound/isa/es1888.c rev 1.4 Relevant kernel config options: options PNPBIOS controller isa0 controller eisa0 controller pci0 controller pnp0 device pcm0 I have to re-enable sbc0 to see if any changes therein apply to ESS as well. Should I have sbc0 in the first place? -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 5:11:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs0.catv.ne.jp (cs0.catv.ne.jp [202.232.171.20]) by hub.freebsd.org (Postfix) with ESMTP id B313514D6A; Sun, 12 Dec 1999 05:11:22 -0800 (PST) (envelope-from nyan@dd.catv.ne.jp) Received: from localhost by cs0.catv.ne.jp (8.9.1/3.7W) id WAA23655; Sun, 12 Dec 1999 22:10:16 +0900 (JST) To: marcel@scc.nl Cc: msmith@freebsd.org, current@freebsd.org Subject: Re: make world is failed on pc98 In-Reply-To: <385375FD.4DC0EFF7@scc.nl> References: <199912120121.RAA00570@mass.cdrom.com> <19991212131847U.nyan@dd.catv.ne.jp> <385375FD.4DC0EFF7@scc.nl> From: Takahashi Yoshihiro X-Mailer: Mew version 1.94 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991212221111Q.nyan@dd.catv.ne.jp> Date: Sun, 12 Dec 1999 22:11:11 +0900 (JST) X-Dispatcher: imput version 990905(IM130) Lines: 30 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <385375FD.4DC0EFF7@scc.nl> Marcel Moolenaar writes: > Since pc98 only has a specialized boot2 and thus shares boot0 and boot1 > with other architectures, it can be assumed that an ELF boot2 doesn't > need any special hacking in boot0 and/or boot1, right? No, if HDD is formated with the format command in MS-DOS for pc98, it is installed 'HDD booting menu' in the HDD. Since the menu is substituting for boot0, boot0 is not always necessary to pc98. The 'loader' program is only transplanted for pc98. The boot2 (sys/boot/pc98/boot2) is the mostly same as the old biosboot (sys/pc98/boot/biosboot) . > boot2 is already capable of loading ELF, right? No. > Isn't it therefore enough to just compile boot2 as ELF? No. > In other words, what are the problems? We need to transplant the new boot2 (sys/boot/i386/boot2) to pc98 to compile as ELF. --- Takahashi Yoshihiro / nyan@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 5:19:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 0AFE214EA0; Sun, 12 Dec 1999 05:19:32 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id OAA24504; Sun, 12 Dec 1999 14:19:21 +0100 (CET) (envelope-from leifn@neland.dk) Date: Sun, 12 Dec 1999 14:19:20 +0100 (CET) From: Leif Neland To: Nik Clayton Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <19991212000349.A4242@catkin.nothing-going-on.org> 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, 12 Dec 1999, Nik Clayton wrote: > (3) A big notice in UPDATING, saying that ata is the replacement for > wd. Make wd require "options I_WANT_WD" or something similar, > so that people can't simply re-config their existing configuration > file. > To be nasty: Change to to I_WANT_WD first. Next week: I_REALLY_WANT_WD Next week: I_REALLY_REALLY_WANT_WD and so on... This should force all to concider changing to ata... Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 5:38:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 5DCB714E52 for ; Sun, 12 Dec 1999 05:38:33 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from tecra.nlsystems.com (tecra.nlsystems.com [10.0.0.5]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id NAA56462; Sun, 12 Dec 1999 13:47:29 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 12 Dec 1999 13:47:29 +0000 (GMT) From: Doug Rabson To: Marcel Moolenaar Cc: current@freebsd.org Subject: Re: Audio support [was Re: HEADSUP: wd driver will be retired!] In-Reply-To: <38539EC2.7894323A@scc.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 Sun, 12 Dec 1999, Marcel Moolenaar wrote: > Doug Rabson wrote: > > > > > The recent commits made existing support even worse. Yes, I'm talking > > > about the ESS1888. It's more dead than before. I'll have to make the > > > noise myself these days, and I can tell you it's no opera :-) > > > > > > In short: Gimme patches! I'll be happy to test and, in a spare hour, can > > > even do some trial and error on my own. I'm not going to beg... > > > > Which commits broke the ESS1888? I haven't tested it for a couple of weeks > > but I have an ESS1888 in one of my alpha boxes which worked a while ago > > after I fixed a few bits and pieces in the driver. > > The first breakage was with the introduction of newmidi IIRC. The mixer > worked, but any dsp related functions were broken. > > See: sys/dev/sound/isa/es1888.c rev 1.3 >  > In recent kernel even the mixer is dead and the soundcard is left in a > state where all volumes are zeroed, preventing audio CD playing as well. > > See: sys/dev/sound/isa/es1888.c rev 1.4 I'll look into this. It won't be today though since I have an Aikido grading to go to this afternoon. > > Relevant kernel config options: > > options PNPBIOS > controller isa0 > controller eisa0 > controller pci0 > controller pnp0 > device pcm0 > > I have to re-enable sbc0 to see if any changes therein apply to ESS as > well. Should I have sbc0 in the first place? I think so. I'll make sure when I get a chance to hack on this. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 6:11:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw0.boostworks.com (gw0.boostworks.com [194.167.81.213]) by hub.freebsd.org (Postfix) with ESMTP id 4D40C14DED for ; Sun, 12 Dec 1999 06:11:20 -0800 (PST) (envelope-from root@synx.com) Received: from synx.com (root@rn.synx.com [192.1.1.241]) by gw0.boostworks.com (8.9.1/8.9.1) with ESMTP id PAA39511 for ; Sun, 12 Dec 1999 15:11:11 +0100 (CET) Message-Id: <199912121411.PAA39511@gw0.boostworks.com> Date: Sun, 12 Dec 1999 15:11:08 +0100 (CET) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: Fwd: Idle loop in SMP. To: current@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Forwarded to -current, due to lack of audience in -smp. Sorry for bothering you). ------ Forwarded message ------ From: Remy Nonnenmacher Subject: Idle loop in SMP. Date: Wed, 1 Dec 1999 18:43:40 +0100 (CET) To: smp@freebsd.org Reply-To: remy@synx.com While investigating a temperature problem, I seen that the default_halt entry called for an idle processor do not really halt the processor. I found the reason on the CVS logs and it is intended to react to changes made on the run queue by the other processor. (i386/i386/swtch.s, 1.61). Since this is dated Sept 97, can we expect a better solution regarding the progress made in the SMP area ? Thanks to all. RN. IaM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 6:35:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 2AF3B14F4E for ; Sun, 12 Dec 1999 06:35:46 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id PAA17867 for freebsd-current@FreeBSD.ORG; Sun, 12 Dec 1999 15:35:44 +0100 (CET) (envelope-from olli) Date: Sun, 12 Dec 1999 15:35:44 +0100 (CET) From: Oliver Fromme Message-Id: <199912121435.PAA17867@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: syscons extension: "propellers" Organization: Administration TU Clausthal Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have (long time ago) written some extensions to syscons, and finally decided to clean them up, document and submit them. (Being tired of updating and merging them every time a new FreeBSD release comes out...) The patches can be found in kern/15436, and it would be really great if they could be committed to -current before the feature freeze. There is no risk, because they completely depend on a single kernel option (SC_PROPELLERS) -- without this option, none of the new code gets compiled into the kernel. The attached patches implement an extension to syscons called "propellers" (activity indicators), along with a status line. It is very useful and convenient if you have to work without X for some reason. So far, everybody who has used these patches for an hour or two didn't want to miss them anymore. :-) Details can be found in the PR. Regards Oliver PS: If someone wants to contact me privately, please use the address . The host in the "From:" line is not set up to receive email. Sorry for the inconvenience. -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 6:55:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from gatekeeper.radio-do.de (gatekeeper.Radio-do.de [193.101.164.1]) by hub.freebsd.org (Postfix) with ESMTP id 0D12214F65 for ; Sun, 12 Dec 1999 06:55:36 -0800 (PST) (envelope-from fn@gatekeeper.radio-do.de) Received: from trinity.radio-do.de (trinity.Radio-do.de [193.101.164.3]) by gatekeeper.radio-do.de (Postfix) with ESMTP id 9749CA9D9; Sun, 12 Dec 1999 15:55:33 +0100 (MET) Received: (from fn@localhost) by trinity.radio-do.de (8.9.3/8.9.3) id PAA13711; Sun, 12 Dec 1999 15:55:33 +0100 (CET) (envelope-from fn@gatekeeper.radio-do.de) Date: Sun, 12 Dec 1999 15:55:33 +0100 From: Frank Nobis To: Maxim Sobolev , current@FreeBSD.ORG Subject: Re: Vibra 16 doesn't recognised anymore Message-ID: <19991212155533.A13426@radio-do.de> References: <385219FB.AFC3C7B8@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <385219FB.AFC3C7B8@altavista.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 11, 1999 at 11:31:39AM +0200, Maxim Sobolev wrote: > Some time ago my soundcard (Vibra 16C), which worked just fine > previously, stopped being recognised/attached. Following is relevant > pieces of dmesg and pnpinfo: > > [...] > isa_probe_children: probing PnP devices > unknown0: at port > 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 > unknown1: at port 0x200-0x207 on isa0 > Looks like the same problem I had here. Try this path: *** sbc.c.orig Mon Dec 6 19:26:31 1999 --- sbc.c Thu Dec 9 11:37:22 1999 *************** *** 107,113 **** /* Check pnp ids */ error = ISA_PNP_PROBE(device_get_parent(dev), dev, sbc_ids); ! if (error) return error; else return -100; --- 107,113 ---- /* Check pnp ids */ error = ISA_PNP_PROBE(device_get_parent(dev), dev, sbc_ids); ! if (error >= 0) return error; else return -100; Regards, Frank -- ~/.signature not found: wellknown error 42 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 7:29:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id B566014D0F; Sun, 12 Dec 1999 07:29:11 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 747BC1CA0; Sun, 12 Dec 1999 23:29:08 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Leif Neland Cc: Nik Clayton , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: Message from Leif Neland of "Sun, 12 Dec 1999 14:19:20 +0100." Date: Sun, 12 Dec 1999 23:29:08 +0800 From: Peter Wemm Message-Id: <19991212152908.747BC1CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leif Neland wrote: > > > On Sun, 12 Dec 1999, Nik Clayton wrote: > > > (3) A big notice in UPDATING, saying that ata is the replacement for > > wd. Make wd require "options I_WANT_WD" or something similar, > > so that people can't simply re-config their existing configuration > > file. > > > To be nasty: Change to to I_WANT_WD first. > Next week: I_REALLY_WANT_WD > Next week: I_REALLY_REALLY_WANT_WD > and so on... > > This should force all to concider changing to ata... > > Leif Well, I've added (which was fairly easy) a warning mechanism to config(8) and have added warnings if the drivers are used. It's pretty loud but it shouldn't be able to be missed. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 7:34:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc2.on.home.com (ha1.rdc2.on.home.com [24.9.0.15]) by hub.freebsd.org (Postfix) with ESMTP id F076F14CE1 for ; Sun, 12 Dec 1999 07:34:15 -0800 (PST) (envelope-from street@iname.com) Received: from mired.eh.local ([24.64.136.188]) by mail.rdc2.on.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991212153415.SYIZ9271.mail.rdc2.on.home.com@mired.eh.local>; Sun, 12 Dec 1999 07:34:15 -0800 Received: (from kws@localhost) by mired.eh.local (8.9.3/8.9.3) id KAA34145; Sun, 12 Dec 1999 10:34:15 -0500 (EST) (envelope-from kws) To: "Jordan K. Hubbard" Cc: FUJISHIMA Satsuki , Greg Lehey , current@FreeBSD.ORG Subject: Re: vinum start needs block device References: <6104.944978331@zippy.cdrom.com> From: Kevin Street Date: 12 Dec 1999 10:34:14 -0500 In-Reply-To: "Jordan K. Hubbard"'s message of "Sat, 11 Dec 1999 21:58:51 -0800" Message-ID: <879030896x.fsf@mired.eh.local> Lines: 18 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Biscayne" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > > Since the recent block device vanishment, MAKEDEV all and my vinum > > volumes have failed to start. > > Please read /usr/src/UPDATING if you're going to track -current > these days. The reason for this is clearly documented at the > top of that file and won't be a problem in -release since the > correct device nodes will be created initially. Jordan, I don't understand your answer. Using the new MAKEDEV is what causes vinum to fail. Won't -release be using the new MAKEDEV? Greg, is there a mechanism to transition an existing vinum installation to the new device nodes? -- Kevin Street street@iname.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 7:38: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id B318314E48 for ; Sun, 12 Dec 1999 07:37:57 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id QAA17570; Sun, 12 Dec 1999 16:37:30 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Kevin Street Cc: "Jordan K. Hubbard" , FUJISHIMA Satsuki , Greg Lehey , current@FreeBSD.ORG Subject: Re: vinum start needs block device In-reply-to: Your message of "12 Dec 1999 10:34:14 EST." <879030896x.fsf@mired.eh.local> Date: Sun, 12 Dec 1999 16:37:29 +0100 Message-ID: <17568.945013049@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <879030896x.fsf@mired.eh.local>, Kevin Street writes: >Jordan, I don't understand your answer. Using the new MAKEDEV is what >causes vinum to fail. Won't -release be using the new MAKEDEV? > >Greg, is there a mechanism to transition an existing vinum >installation to the new device nodes? I think that between the two of us, Greg and I have lost a oneline patch on the floor, try this: Index: vinumio.c =================================================================== RCS file: /home/ncvs/src/sys/dev/vinum/vinumio.c,v retrieving revision 1.45 diff -u -r1.45 vinumio.c --- vinumio.c 1999/10/13 03:17:59 1.45 +++ vinumio.c 1999/12/12 11:00:12 @@ -76,7 +76,7 @@ drive->devicename, drive->vp->v_usecount); } - if (drive->vp->v_type != VBLK) { /* only consider block devices */ + if (!vn_isdisk(drive->vp)) { /* only consider block devices */ VOP_UNLOCK(drive->vp, 0, drive->p); close_drive(drive); drive->lasterror = ENOTBLK; -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 7:39:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from dmaddox.conterra.com (dmaddox.conterra.com [209.12.169.48]) by hub.freebsd.org (Postfix) with ESMTP id 4B71714CD4 for ; Sun, 12 Dec 1999 07:39:27 -0800 (PST) (envelope-from myself@dmaddox.conterra.com) Received: (from myself@localhost) by dmaddox.conterra.com (8.9.3/8.9.3) id KAA55093 for current@FreeBSD.ORG; Sun, 12 Dec 1999 10:37:01 -0500 (EST) (envelope-from myself) Date: Sun, 12 Dec 1999 10:37:01 -0500 From: "Donald J . Maddox" To: current@FreeBSD.ORG Subject: What happened to netstat? Message-ID: <19991212103701.A55038@dmaddox.conterra.com> Reply-To: dmaddox@conterra.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After rebuilding World and kernel last night, I find that the behavior of 'netstat -a' has changed... Only UNIX domain sockets are shown in the output, no inet stuff at all, e.g.: # netstat -a Active UNIX domain sockets Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr cbf67c40 stream 0 0 0 cbf67c00 0 0 /tmp/.X11-unix/X0 cbf67c00 stream 0 0 0 cbf67c40 0 0 cbf67e00 stream 0 0 0 cbf67b40 0 0 /tmp/.X11-unix/X0 cbf67b40 stream 0 0 0 cbf67e00 0 0 cbf67d80 stream 0 0 0 cbf67a40 0 0 /tmp/.X11-unix/X0 cbf67a40 stream 0 0 0 cbf67d80 0 0 cbf67a80 stream 0 0 0 cbf67c80 0 0 /tmp/.X11-unix/X0 cbf67c80 stream 0 0 0 cbf67a80 0 0 cbf67cc0 stream 0 0 0 cbf67dc0 0 0 fs7100 cbf67dc0 stream 0 0 0 cbf67cc0 0 0 cbf67d40 stream 0 0 0 cbf67e80 0 0 /tmp/.X11-unix/X0 cbf67e80 stream 0 0 0 cbf67d40 0 0 cbf67e40 stream 0 0 cc22bd20 0 0 0 /tmp/.X11-unix/X0 cbf67d00 stream 0 0 0 0 0 0 fs7100 cbf67ec0 stream 0 0 cbf80660 0 0 0 fs7100 cbf67f40 stream 0 0 cbf5ac60 0 0 0 /var/run/printer cbf67ac0 dgram 0 0 0 cbf60fc0 0 cbf67f00 cbf67f00 dgram 0 0 0 cbf60fc0 0 cbf67f80 cbf67f80 dgram 0 0 0 cbf60fc0 0 cbf67fc0 cbf67fc0 dgram 0 0 0 cbf60fc0 0 0 cbf60fc0 dgram 0 0 cbf5ca60 0 cbf67ac0 0 /var/run/log Anybody have an idea what's going on here? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 7:47:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 870E014D7A for ; Sun, 12 Dec 1999 07:47:39 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 8295D1CA0; Sun, 12 Dec 1999 23:47:36 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Poul-Henning Kamp Cc: Kevin Street , "Jordan K. Hubbard" , FUJISHIMA Satsuki , Greg Lehey , current@FreeBSD.ORG Subject: Re: vinum start needs block device In-Reply-To: Message from Poul-Henning Kamp of "Sun, 12 Dec 1999 16:37:29 +0100." <17568.945013049@critter.freebsd.dk> Date: Sun, 12 Dec 1999 23:47:36 +0800 From: Peter Wemm Message-Id: <19991212154736.8295D1CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > In message <879030896x.fsf@mired.eh.local>, Kevin Street writes: > > >Jordan, I don't understand your answer. Using the new MAKEDEV is what > >causes vinum to fail. Won't -release be using the new MAKEDEV? > > > >Greg, is there a mechanism to transition an existing vinum > >installation to the new device nodes? > > I think that between the two of us, Greg and I have lost a oneline > patch on the floor, try this: I tried a patch exactly like this last night, it works fine. I also changed the error message below to say "not a _disk_ device" rather than refer to block devices. > Index: vinumio.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/vinum/vinumio.c,v > retrieving revision 1.45 > diff -u -r1.45 vinumio.c > --- vinumio.c 1999/10/13 03:17:59 1.45 > +++ vinumio.c 1999/12/12 11:00:12 > @@ -76,7 +76,7 @@ > drive->devicename, > drive->vp->v_usecount); > } > - if (drive->vp->v_type != VBLK) { /* only consider bl ock devices */ > + if (!vn_isdisk(drive->vp)) { /* only consider bl ock devices */ > VOP_UNLOCK(drive->vp, 0, drive->p); > close_drive(drive); > drive->lasterror = ENOTBLK; > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 9:22:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id CF06D14E51; Sun, 12 Dec 1999 09:22:43 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id DAA77474; Mon, 13 Dec 1999 03:52:41 +1030 (CST) Date: Mon, 13 Dec 1999 03:52:41 +1030 From: Greg Lehey To: current@FreeBSD.org Cc: Poul-Henning Kamp Subject: vinum start needs block device Message-ID: <19991213035240.A77464@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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'm on the road now, and writing mail is like pulling teeth. phk supplied the correct patch. phk, could you commit it, please? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 9:45: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id BD72115134 for ; Sun, 12 Dec 1999 09:45:00 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA17957; Sun, 12 Dec 1999 18:44:48 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: vinum start needs block device In-reply-to: Your message of "Mon, 13 Dec 1999 03:52:41 +1030." <19991213035240.A77464@freebie.lemis.com> Date: Sun, 12 Dec 1999 18:44:47 +0100 Message-ID: <17955.945020687@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991213035240.A77464@freebie.lemis.com>, Greg Lehey writes: >I'm on the road now, and writing mail is like pulling teeth. phk >supplied the correct patch. phk, could you commit it, please? Done. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 10: 7:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from m08.alpha-net.ne.jp (m08.alpha-net.ne.jp [210.229.64.38]) by hub.freebsd.org (Postfix) with ESMTP id 5FFFC14D9F for ; Sun, 12 Dec 1999 10:07:17 -0800 (PST) (envelope-from k5@cheerful.com) Received: from kyoto-p29.alpha-net.ne.jp (kyoto-p29.alpha-net.ne.jp [210.237.118.29]) by m08.alpha-net.ne.jp (8.9.3/3.7W) with ESMTP id DAA10823 for ; Mon, 13 Dec 1999 03:07:12 +0900 (JST) Received: from souffle.bogus-local.net (souffle.bogus-local.net [192.168.1.1]) by kyoto-p29.alpha-net.ne.jp (Postfix) with ESMTP id 706EB3D4B; Mon, 13 Dec 1999 03:07:09 +0900 (JST) Date: Mon, 13 Dec 1999 03:07:07 +0900 Message-ID: <14419.58443.318824.72159A@cheerful.com> From: FUJISHIMA Satsuki To: phk@critter.freebsd.dk Cc: street@iname.com, jkh@zippy.cdrom.com, k5@cheerful.com, grog@lemis.com, current@FreeBSD.ORG Subject: Re: vinum start needs block device In-Reply-To: In your message of "Sun, 12 Dec 1999 16:37:29 +0100" <17568.945013049@critter.freebsd.dk> References: <879030896x.fsf@mired.eh.local> <17568.945013049@critter.freebsd.dk> User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) Emacs/20.4 (i386--freebsd) MULE/4.0 (HANANOEN) MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Sun, 12 Dec 1999 16:37:29 +0100, Poul-Henning Kamp wrote: > I think that between the two of us, Greg and I have lost a oneline > patch on the floor, try this: > > Index: vinumio.c This patch solved my problem, and I found it has already been committed to the tree. :) thanks! -- FUJISHIMA Satsuki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 10:29: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 5D82814C80 for ; Sun, 12 Dec 1999 10:29:00 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id TAA04947 for freebsd-current@FreeBSD.ORG; Sun, 12 Dec 1999 19:28:55 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id A60CD8863; Sun, 12 Dec 1999 18:40:33 +0100 (CET) Date: Sun, 12 Dec 1999 18:40:33 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: Modules and sysctl tree Message-ID: <19991212184033.A10383@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199912112149.NAA71033@bubba.whistle.com> <91986.944949603@zippy.cdrom.com> <199912112333.SAA78252@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <199912112333.SAA78252@khavrinen.lcs.mit.edu> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Garrett Wollman: > It's listening on a kernel notification socket. (Implementation is an > exercise left for the reader, but there are already a few examples.) Like the routing socket I guess ? Or we could implement POLLSYSCTL ? :-) /me hides and runs -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 13:11: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 0995D14E11 for ; Sun, 12 Dec 1999 13:11:08 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA08343; Sun, 12 Dec 1999 13:11:14 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kevin Street Cc: FUJISHIMA Satsuki , Greg Lehey , current@FreeBSD.ORG Subject: Re: vinum start needs block device In-reply-to: Your message of "12 Dec 1999 10:34:14 EST." <879030896x.fsf@mired.eh.local> Date: Sun, 12 Dec 1999 13:11:14 -0800 Message-ID: <8340.945033074@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Jordan, I don't understand your answer. Using the new MAKEDEV is what > causes vinum to fail. Won't -release be using the new MAKEDEV? Sorry, I evidently didn't read the message the same way. If the problem is indeed as you say then vinum has been broken; I thought he was talking about using the old MAKEDEV. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 16: 6:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id E418A14C82 for ; Sun, 12 Dec 1999 16:06:34 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40329>; Mon, 13 Dec 1999 10:58:14 +1100 Content-return: prohibited Date: Mon, 13 Dec 1999 11:06:19 +1100 From: Peter Jeremy Subject: make world broken building fortunes To: current@FreeBSD.ORG Message-Id: <99Dec13.105814est.40329@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm still running a -CURRENT from just before the signal changes and for the past 4 days, my nightly buildworld has been dying at follows: ===> games/fortune/datfiles PATH=$PATH:/usr/games:/usr/obj/3.0/cvs/src/games/fortune/datfiles/../strfile st rfile -Crs /3.0/cvs/src/games/fortune/datfiles/fortunes fortunes.dat strfile: illegal option -- C strfile [-iorsx] [-c char] sourcefile [datafile] *** Error code 1 ... Looking at the command in question, I believe the fix is as follows, but it'll be a couple of hours to confirm. Index: Makefile =================================================================== RCS file: /home/CVSROOT/src/games/fortune/datfiles/Makefile,v retrieving revision 1.23 diff -u -r1.23 Makefile --- Makefile 1999/11/05 08:17:53 1.23 +++ Makefile 1999/12/13 00:04:00 @@ -33,16 +33,16 @@ .for f in fortunes fortunes2 fortunes2-o limerick startrek zippy $f.dat: $f - PATH=$$PATH:/usr/games:${.OBJDIR}/../strfile \ + PATH=/usr/games:${.OBJDIR}/../strfile:$$PATH \ strfile -Crs ${.ALLSRC} ${.TARGET} .endfor fortunes-o.dat: fortunes-o - PATH=$$PATH:/usr/games:${.OBJDIR}/../strfile \ + PATH=/usr/games:${.OBJDIR}/../strfile:$$PATH \ strfile -Crsx ${.ALLSRC} ${.TARGET} fortunes-o: fortunes-o.${TYPE} - PATH=$$PATH:/usr/games:${.OBJDIR}/../../caesar \ + PATH=/usr/games:${.OBJDIR}/../../caesar:$$PATH \ caesar 13 < ${.ALLSRC} > ${.TARGET} .include Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 16:58:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from holonet.net (ifmxoak.informix.com [192.147.88.2]) by hub.freebsd.org (Postfix) with ESMTP id B07AF14F32 for ; Sun, 12 Dec 1999 16:58:34 -0800 (PST) (envelope-from adamw@holonet.net) Received: by holonet.net (Postfix, from userid 667) id 5191726B6; Sun, 12 Dec 1999 16:59:01 +0000 (GMT) Date: Sun, 12 Dec 1999 16:59:00 +0000 From: Adam Wight To: current@freebsd.org Subject: Among the ATA casualties... Message-ID: <19991212165900.A482@holonet.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="ZGiS0Q5IWpPtfppv" X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Against my better judgment, I've been running -current on, among other machines, a Dell Latitude XP 475C... The wd driver manages to deal with the inevitable cruft quite nicely, but the ata driver refuses to mount the root partition. To the best of my knowledge the chipset is the Western Digital 8110. I can supply any other information required, of course. -Adam Wight boot -v output using the wd driver follows: --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="wd.v" Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Sun Dec 12 12:04:07 GMT 1999 root@:/usr2/src/sys/compile/PROBOSCIS Calibrating clock(s) ... i8254 clock: 1193395 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CPU: i486 DX4 (486-class CPU) Origin = "GenuineIntel" Id = 0x480 Stepping = 0 Features=0x3 real memory = 37748736 (36864K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x0029a000 - 0x023fdfff, 35012608 bytes (8548 pages) avail memory = 34107392 (33308K bytes) Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel" at 0xc0281000. md0: Malloc disk Creating DISK md0 npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.1, connected at v1.0 isa0: on motherboard Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 401MB (822016 sectors), 988 cyls, 16 heads, 52 S/T, 512 B/S wd0: ATA INQUIRE valid = 0003, dmamword = 0107, apio = 0003, udma = 0000 wdc0: unit 1 (atapi): <\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*/\M-*\M-*\M-*\M-*\M-*\M-*\M-*\M-*>, removable, cmd2, intr, ovlap, idma, iordy wdc0: unit 1: unknown ATAPI type=10 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0065 kbdc: TEST_AUX_PORT status:0001 psm0: strange result for test aux port (1). kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: status 10 00 64 psm: data 08 00 00 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k vga0: vga: WARNING: video mode switching is not fully supported on this adapter VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 52 10 11 00 00 07 80 9c 8e da 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 52 10 11 00 00 07 80 9c 8e da 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0 kbd0 pcic: polling, can't alloc 0 pcic: polling, can't alloc 0 pcic0: on isa0 pccard0: on pcic0 pccard1: on pcic0 sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: irq maps: 0x41 0x41 0x41 0x41 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio2: not probed (disabled) ppc: parallel port found at 0x378 ppc: chipset forced to generic ppc0: SPP ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip: irq 7 plip0: on ppbus 0 isa_probe_children: probing PnP devices BIOS Geometries: 0:03da0f34 0..986=987 cylinders, 0..15=16 heads, 1..52=52 sectors 1:01300311 0..304=305 cylinders, 0..3=4 heads, 1..17=17 sectors 0 accounted for Device configuration finished. new masks: bio 40084040, tty 40031092, net 40071092 Mounting root from ufs:/dev/wd0s1a wd0: wdcontrol: recal failed reading fsbn 0 (status 51 error 4) pccard: card inserted, slot 1 wd0s1: type 0xa5, start 52, end = 822015, size 821964 : OK start_init: trying /sbin/init devclass_alloc_unit: sio2 already exists, using next available unit number sio3 at port 0x2e8-0x2ef irq 5 slot 1 on pccard1 sio3: type 16550A splash: image decoder found: daemon_saver --ZGiS0Q5IWpPtfppv-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 17:40: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles516.castles.com [208.214.165.80]) by hub.freebsd.org (Postfix) with ESMTP id 1EC0F14EE1 for ; Sun, 12 Dec 1999 17:40:01 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA04671; Sun, 12 Dec 1999 17:42:37 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912130142.RAA04671@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Adam Wight Cc: current@freebsd.org Subject: Re: Among the ATA casualties... In-reply-to: Your message of "Sun, 12 Dec 1999 16:59:00 GMT." <19991212165900.A482@holonet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 12 Dec 1999 17:42:37 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Against my better judgment, I've been running -current on, among other > machines, a Dell Latitude XP 475C... The wd driver manages to deal with > the inevitable cruft quite nicely, but the ata driver refuses to mount > the root partition. > > To the best of my knowledge the chipset is the Western Digital 8110. > I can supply any other information required, of course. > > -Adam Wight > > boot -v output using the wd driver follows: That's not very helpful; we know it works. How about some information on the problem? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Dec 12 18:29:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.netaxs.com (mail.netaxs.com [207.8.186.26]) by hub.freebsd.org (Postfix) with ESMTP id B63E114CA0 for ; Sun, 12 Dec 1999 18:29:25 -0800 (PST) (envelope-from bleez@netaxs.com) Received: from dyn-2.blackbox-2.netaxs.com (dyn-2.blackbox-2.netaxs.com [207.106.60.2]) by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id VAA08194 for ; Sun, 12 Dec 1999 21:29:22 -0500 (EST) Date: Sun, 12 Dec 1999 21:29:21 -0500 (EST) From: Bryan Liesner X-Sender: root@gravy.kishka.net Reply-To: Bryan Liesner To: freebsd-current@freebsd.org Subject: Broken sound on an Avance Asound 110 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 In a kernel built from sources current as of 21:00 EST, I no longer have sound. dmesg from yesterday: pcm0: at port 0x220-0x22f irq 5 drq 1,0 on isa0 unknown0: at port 0x388-0x38f on isa0 joy0: at port 0x200-0x207 on isa0 unknown1: at port 0x330-0x331 irq 9 on isa0 The above worked without using sbc0 in my kernel conf, only pcm0 dmesg now: unknown0: at port 0x220-0x22f irq 5 drq 1,0 on isa0 sbc0: at port 0x388-0x38f on isa0 device_probe_and_attach: sbc0 attach returned 6 joy0: at port 0x200-0x207 on isa0 unknown1: at port 0x330-0x331 irq 9 on isa0 The above is using both sbc0 and pcm0 I know this probably isn't enough info, what can I do to help? -Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 18:31:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 3072514CA3 for ; Sun, 12 Dec 1999 18:31:56 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40338>; Mon, 13 Dec 1999 13:23:33 +1100 Content-return: prohibited Date: Mon, 13 Dec 1999 13:31:40 +1100 From: Peter Jeremy Subject: Re: make world broken building fortunes In-reply-to: <99Dec13.105814est.40329@border.alcanet.com.au>; from peter.jeremy@alcatel.com.au on Mon, Dec 13, 1999 at 11:06:19AM +1100 To: current@FreeBSD.ORG Message-Id: <99Dec13.132333est.40338@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <99Dec13.105814est.40329@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Dec-13 11:06:19 +1100, I wrote: >I'm still running a -CURRENT from just before the signal changes and >for the past 4 days, my nightly buildworld has been dying at follows: > >===> games/fortune/datfiles >PATH=$PATH:/usr/games:/usr/obj/3.0/cvs/src/games/fortune/datfiles/../strfile strfile -Crs /3.0/cvs/src/games/fortune/datfiles/fortunes fortunes.dat >strfile: illegal option -- C >strfile [-iorsx] [-c char] sourcefile [datafile] >*** Error code 1 >... I tried using PATH=${.OBJDIR}/../strfile:$PATH:/usr/games (which is slightly different and more correct than the patch I posted). This changed the problem to: /usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found Which isn't a good sign. Running the command manually with LD_LIBRARY_PATH pointing to the new libc.so works for me (which means that strfile isn't using signals), but I'm not sure how far back this will work. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 20:27:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from everyhost.com (everyhost.com [63.71.213.201]) by hub.freebsd.org (Postfix) with SMTP id C3DF815450 for ; Sun, 12 Dec 1999 20:27:46 -0800 (PST) (envelope-from mah@everyhost.com) Received: (qmail 35701 invoked by uid 1000); 13 Dec 1999 04:26:36 -0000 Date: 13 Dec 1999 04:26:36 -0000 Message-ID: <19991213042636.35700.qmail@everyhost.com> From: mah@everyhost.com To: perlbug@perl.com Subject: Segfault on $f->print for IO::File Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a bug report for perl from mah@everybody.org, generated with the help of perlbug 1.26 running under perl 5.00503. ----------------------------------------------------------------- [Please enter your report here] The following segfaults on the "setpos" line. It only does this with the "print" statement included. --- cut --- #!/usr/bin/perl -w use strict; use IO::File; my $f = IO::File->new(">new.txt"); $f->print; $f->setpos(0); --- cut --- [Please do not change anything below this line] ----------------------------------------------------------------- --- Site configuration information for perl 5.00503: Configured by markm at $Date: 1999/05/05 19:42:40 $. Summary of my perl5 (5.0 patchlevel 5 subversion 3) configuration: Platform: osname=freebsd, osvers=4.0-current, archname=i386-freebsd uname='freebsd freefall.freebsd.org 4.0-current freebsd 4.0-current #0: $Date: 1999/05/05 19:42:40 $' hint=recommended, useposix=true, d_sigaction=define usethreads=undef useperlio=undef d_sfio=undef Compiler: cc='cc', optimize='undef', gccversion=egcs-2.91.66 19990314 (egcs-1.1.2 release) cppflags='' ccflags ='' stdchar='char', d_stdstdio=undef, usevfork=true intsize=4, longsize=4, ptrsize=4, doublesize=8 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 alignbytes=4, usemymalloc=n, prototype=define Linker and Libraries: ld='cc', ldflags ='-Wl,-E' libpth=/usr/lib libs=-lm -lc -lcrypt libc=/usr/lib/libc.so, so=so, useshrplib=true, libperl=libperl.so.3 Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' ' cccdlflags='-DPIC -fpic', lddlflags='-shared' Locally applied patches: --- @INC for perl 5.00503: /usr/libdata/perl/5.00503/mach /usr/libdata/perl/5.00503 /usr/local/lib/perl5/site_perl/5.005/i386-freebsd /usr/local/lib/perl5/site_perl/5.005 . --- Environment for perl 5.00503: HOME=/home/mah LANG (unset) LANGUAGE (unset) LD_LIBRARY_PATH (unset) LOGDIR (unset) PATH=/bin:/usr/bin:/usr/local/bin:/usr/games:/usr/sbin:/sbin:/usr/X11R6/bin:/usr/local/pgsql/bin:/etc:/usr/etc:/usr/freeware/bin PERL_BADLANG (unset) SHELL=/usr/local/bin/bash To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 20:28:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from tmtowtdi.perl.org (tmtowtdi.perl.org [209.85.3.25]) by hub.freebsd.org (Postfix) with SMTP id 967AF14ED4 for ; Sun, 12 Dec 1999 20:28:18 -0800 (PST) (envelope-from richard@tmtowtdi.perl.org) Received: (qmail 21215 invoked by uid 511); 13 Dec 1999 04:28:17 -0000 Subject: [ID 19991212.003] Segfault on $f->print for IO::File To: perl5-porters@perl.org From: mah@everyhost.com Delivered-To: perlmail-perlbugtron@perl.org Cc: current@freebsd.org Date: 13 Dec 1999 04:26:36 -0000 Message-Id: <19991213042636.35700.qmail@everyhost.com> Received: (qmail 21206 invoked by uid 508); 13 Dec 1999 04:28:16 -0000 X-loop: perlbug@perl.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a bug report for perl from mah@everybody.org, generated with the help of perlbug 1.26 running under perl 5.00503. ----------------------------------------------------------------- [Please enter your report here] The following segfaults on the "setpos" line. It only does this with the "print" statement included. --- cut --- #!/usr/bin/perl -w use strict; use IO::File; my $f = IO::File->new(">new.txt"); $f->print; $f->setpos(0); --- cut --- [Please do not change anything below this line] ----------------------------------------------------------------- --- Site configuration information for perl 5.00503: Configured by markm at $Date: 1999/05/05 19:42:40 $. Summary of my perl5 (5.0 patchlevel 5 subversion 3) configuration: Platform: osname=freebsd, osvers=4.0-current, archname=i386-freebsd uname='freebsd freefall.freebsd.org 4.0-current freebsd 4.0-current #0: $Date: 1999/05/05 19:42:40 $' hint=recommended, useposix=true, d_sigaction=define usethreads=undef useperlio=undef d_sfio=undef Compiler: cc='cc', optimize='undef', gccversion=egcs-2.91.66 19990314 (egcs-1.1.2 release) cppflags='' ccflags ='' stdchar='char', d_stdstdio=undef, usevfork=true intsize=4, longsize=4, ptrsize=4, doublesize=8 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 alignbytes=4, usemymalloc=n, prototype=define Linker and Libraries: ld='cc', ldflags ='-Wl,-E' libpth=/usr/lib libs=-lm -lc -lcrypt libc=/usr/lib/libc.so, so=so, useshrplib=true, libperl=libperl.so.3 Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' ' cccdlflags='-DPIC -fpic', lddlflags='-shared' Locally applied patches: --- @INC for perl 5.00503: /usr/libdata/perl/5.00503/mach /usr/libdata/perl/5.00503 /usr/local/lib/perl5/site_perl/5.005/i386-freebsd /usr/local/lib/perl5/site_perl/5.005 . --- Environment for perl 5.00503: HOME=/home/mah LANG (unset) LANGUAGE (unset) LD_LIBRARY_PATH (unset) LOGDIR (unset) PATH=/bin:/usr/bin:/usr/local/bin:/usr/games:/usr/sbin:/sbin:/usr/X11R6/bin:/usr/local/pgsql/bin:/etc:/usr/etc:/usr/freeware/bin PERL_BADLANG (unset) SHELL=/usr/local/bin/bash To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 20:40:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from holonet.net (ifmxoak.informix.com [192.147.88.2]) by hub.freebsd.org (Postfix) with ESMTP id 0820714DC9; Sun, 12 Dec 1999 20:40:26 -0800 (PST) (envelope-from adamw@holonet.net) Received: by holonet.net (Postfix, from userid 667) id ACA0726B6; Sun, 12 Dec 1999 20:40:53 +0000 (GMT) Date: Sun, 12 Dec 1999 20:40:53 +0000 From: Adam Wight To: Mike Smith Cc: current@freebsd.org Subject: Re: Among the ATA casualties... Message-ID: <19991212204053.A734@holonet.net> References: <19991212165900.A482@holonet.net> <199912130142.RAA04671@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912130142.RAA04671@mass.cdrom.com>; from msmith@freebsd.org on Sun, Dec 12, 1999 at 05:42:37PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > boot -v output using the wd driver follows: > > That's not very helpful; we know it works. How about some information on > the problem? Well... I'd sure like to send a boot -v for a kernel using ata... I don't have the right hardware here to use a serial console, however. Here are the relevant lines from the boot sequence (paraphrased, of course): .... ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at port 0x1f0 irq 14 on isa0 .... BIOS Geometries: 0:03da0f34 0..986=987 cylinders, 0..15=16 heads, 1..52=52 sectors 1:01300311 0..304=305 cylinders, 0..3=4 heads, 1..17=17 sectors 0 accounted for Device configuration finished. new masks: bio 40084040, tty 40031092, net 40071092 ad0: piomode=4 dmamode=2 udmamode=-1 cblid=0 ad0: ATA-? disk at ata0 as master ad0: 401MB (822016 sectors), 988 cyls, 16 heads, 52 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, PIO Creating DISK ad0 Creating DISK wd0 Mounting root from ufs:/dev/wd0s1a wd0: invalid primary partition table: no magic Root mount failed: 6 Mounting root from ufs:wd0s1a wd0: invalid primary partition table: no magic Root mount failed: 6 Mounting root from ufs:wd0a wd0: invalid primary partition table: no magic Root mount failed: 22 Manual root filesystem specification.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 20:51: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from mtiwmhc01.worldnet.att.net (mtiwmhc01.worldnet.att.net [204.127.131.36]) by hub.freebsd.org (Postfix) with ESMTP id AB49214F0D; Sun, 12 Dec 1999 20:50:49 -0800 (PST) (envelope-from Thrumbar@Worldnet.att.net) Received: from 11.neworleans-01-02rs16rt.la.dial-access.att.net ([12.73.238.11]) by mtiwmhc01.worldnet.att.net (InterMail v03.02.07.07 118-134) with SMTP id <19991213045047.GYLL5516@11.neworleans-01-02rs16rt.la.dial-access.att.net>; Mon, 13 Dec 1999 04:50:47 +0000 From: Thrumbar Pathfinder To: freebsd-current@freebsd.org Cc: doc@freebsd.org Subject: Developer's Interface Guide for IA-64 Servers (DIG64) Adopter Date: Sun, 12 Dec 1999 22:47:45 -0600 Organization: OmniCorp Interstellar Message-ID: X-Mailer: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Attention, all FreeBSD, OpenBSD and NetBSD developers.. This is a chance we cannot ignore.. Please form up a development team with a central tram leader and get signed up for this offer. The Documentation personnel should sign up for the Contributors link to add BSD's voice in setting the guidelines for future BSD development for all three forms... Please read below.. (also, team leaders, send me a e-mail when you sign-up to keep me informed as to the process and to get an idea on how many teams there is involved) About the DIG64 Leading hardware and software vendors have formed an industry group to develop the DIG64 guidelines. These guidelines establish basic system building blocks, interfaces, and programming conventions for upcoming IA-64 based servers and their system-level software in order to define hardware and software compatibility and interoperability.=20 DIG64 is...=20 an industry-driven set of technical guidelines that define hardware, firmware and operating system's compatibility for IA-64 servers providing IT with systems built on common, stabilized interfaces that improve reliability and interoperability, lower qualification and support costs developed and backed by the key IA-64 OEMs, OSVs, and BIOS vendors who are contributing to its development and are building compliant products allowing the industry to accelerate the pace of IA-64 technology adoption=20 By defining common building blocks and interfaces and proactively addressing legacy issues, the DIG64 provides an array of benefits for both developers and IT organizations.=20 =46or developers, the DIG64: =20 Increases the efficiency of the design process, freeing developers to focus design resources of features that add unique value and differentiate their products in the marketplace. =20 Gives firmware and OS vendors a known set of interfaces to build to, enabling them to confidentially develop their products concurrently with the hardware and shrink time to markets. =20 Provides a technology migration roadmap that extends the planning horizon for developers and allows them to create designs with increased longevity.=20 =46or business users and Information Technology (IT) departments: =20 Standard interfaces and interoperable layers enhance the reliability and robustness of the resulting servers as well as lowering qualification costs. Since developers find it easier to build components that work together, customers can enjoy a greater choice of robust, innovative server solutions. Because the DIG64 addresses the migration of support-intensive, obsolete technologies to newer, more robust choices, IT departments can control or reduce the cost of server support.=20 DIG64 Defined =20 The DIG64 specification defines basic system building blocks, interfaces and programming conventions between IA-64 based servers and system-level software such as the operating system and device drivers. The specification covers:=20 Core system components such as the processor, chipset, memory, I/O bus, and server management hardware.=20 =20 Interfaces to peripheral devices for networking, communications and storage.=20 =20 Low-level firmware interfaces to the operating system for system configuration, boot and runtime services.=20 The guide does not create new standards and interfaces, but selects components and interfaces from already existing technologies. To ensure interoperability, the DIG64 also specifies implementation requirements for each specification or standard.=20 The DIG64 spells out a roadmap for eliminating obsolete technologies. Release 1.0, which is currently available , pertains to servers=20 based on the Intel=AE Itanium=99 processor. Subsequent versions will address future processors as they are developed. A three-level hierarchy of required, recommended and optional features enables vendors to choose how quickly they want to remove older technologies.=20 The DIG64 is operating-system independent, promoting cross-platform interoperability among servers running Windows 2000*, Linux and other UNIX* operating systems.=20 Join Other Industry Leaders Already Building Compatible IA-64 Server Solutions! =20 =20 There is still time to get involved by becoming a DIG64 Adopter member. To find out more about the advantages of becoming a DIG64 Adopter, take look at the DIG64 www site.... http://www.dig64.org/ To sign up as a Developer's Interface Guide for IA-64 Servers (DIG64) Adopter, complete all of the information at the link listed below and hit the submit button. You will then be able to download a "DIG64 Adopters Agreement". http://www.dig64.org/signup.htm By becoming a DIG64 Contributor, you will be able to provide technical input into the development of the DIG64 guidelines in addition to gaining access to the latest published draft. All input will be reviewed by the DIG64 Working Group for possible inclusion in the guideline. http://www.dig64.org/contributor.htm When you have formed your group please e-mail me so that I will know how many groups there are.. Please include a list of the individuals on the team and their position on said team as well as any contact information you are willing to provide... Thrumbar@Worldnet.att.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 20:55: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id CF6FC14F8B for ; Sun, 12 Dec 1999 20:54:58 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40324>; Mon, 13 Dec 1999 15:46:31 +1100 Content-return: prohibited Date: Mon, 13 Dec 1999 15:54:35 +1100 From: Peter Jeremy Subject: Re: make world broken building fortunes In-reply-to: <99Dec13.132333est.40338@border.alcanet.com.au>; from peter.jeremy@alcatel.com.au on Mon, Dec 13, 1999 at 01:31:40PM +1100 To: current@FreeBSD.ORG Message-Id: <99Dec13.154631est.40324@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <99Dec13.105814est.40329@border.alcanet.com.au> <99Dec13.132333est.40338@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On 1999-Dec-13 11:06:19 +1100, I wrote: >I'm still running a -CURRENT from just before the signal changes and >for the past 4 days, my nightly buildworld has been dying at follows: > >===> games/fortune/datfiles >PATH=$PATH:/usr/games:/usr/obj/3.0/cvs/src/games/fortune/datfiles/../strfile strfile -Crs /3.0/cvs/src/games/fortune/datfiles/fortunes fortunes.dat >strfile: illegal option -- C >strfile [-iorsx] [-c char] sourcefile [datafile] >*** Error code 1 >... Well, the following fixes that problem for me: Index: datfiles/Makefile =================================================================== RCS file: /home/CVSROOT/src/games/fortune/datfiles/Makefile,v retrieving revision 1.23 diff -u -r1.23 Makefile --- Makefile 1999/11/05 08:17:53 1.23 +++ Makefile 1999/12/13 02:27:16 @@ -33,16 +33,19 @@ .for f in fortunes fortunes2 fortunes2-o limerick startrek zippy $f.dat: $f - PATH=$$PATH:/usr/games:${.OBJDIR}/../strfile \ + LD_LIBRARY_PATH=${LIBRARY_PATH} \ + PATH=${.OBJDIR}/../strfile:$$PATH:/usr/games \ strfile -Crs ${.ALLSRC} ${.TARGET} .endfor fortunes-o.dat: fortunes-o - PATH=$$PATH:/usr/games:${.OBJDIR}/../strfile \ + LD_LIBRARY_PATH=${LIBRARY_PATH} \ + PATH=${.OBJDIR}/../strfile:$$PATH:/usr/games \ strfile -Crsx ${.ALLSRC} ${.TARGET} fortunes-o: fortunes-o.${TYPE} - PATH=$$PATH:/usr/games:${.OBJDIR}/../../caesar \ + LD_LIBRARY_PATH=${LIBRARY_PATH} \ + PATH=${.OBJDIR}/../../caesar:$$PATH:/usr/games \ caesar 13 < ${.ALLSRC} > ${.TARGET} .include And buildworld then dies at: colldef -I /3.0/cvs/src/share/colldef -o ru_SU.ISO_8859-5.out /3.0/cvs/src/share/colldef/ru_SU.ISO_8859-5.src colldef: syntax error near line 1 *** Error code 69 This looks like it is solved by Marcel's commit: 1.106 +3 -3 src/Makefile.inc1 Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 22: 5: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from host.cer.ntnu.edu.tw (cer.ntnu.edu.tw [140.122.119.9]) by hub.freebsd.org (Postfix) with ESMTP id E230D14DA5 for ; Sun, 12 Dec 1999 22:05:01 -0800 (PST) (envelope-from clive@host.cer.ntnu.edu.tw) Received: (from clive@localhost) by host.cer.ntnu.edu.tw (8.9.3/8.9.3) id OAA71276 for current@FreeBSD.ORG; Mon, 13 Dec 1999 14:08:08 +0800 (CST) (envelope-from clive) Date: Mon, 13 Dec 1999 14:08:07 +0800 From: Clive Lin To: current@FreeBSD.ORG Subject: Re: What happened to netstat? Message-ID: <19991213140807.A71230@host.cer.ntnu.edu.tw> Reply-To: Clive Lin References: <19991212103701.A55038@dmaddox.conterra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991212103701.A55038@dmaddox.conterra.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 12, 1999 at 10:37:01AM -0500, Donald J . Maddox wrote: > After rebuilding World and kernel last night, I find that the behavior of > 'netstat -a' has changed... Only UNIX domain sockets are shown in the Errr... may I complain ? I got the same problem :( current last night. -- CirX Clive Lin FreeBSD - The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 23: 5:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles516.castles.com [208.214.165.80]) by hub.freebsd.org (Postfix) with ESMTP id 93B7214D01 for ; Sun, 12 Dec 1999 23:05:42 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA05626; Sun, 12 Dec 1999 23:08:24 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912130708.XAA05626@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Adam Wight Cc: current@freebsd.org Subject: Re: Among the ATA casualties... In-reply-to: Your message of "Sun, 12 Dec 1999 20:40:53 GMT." <19991212204053.A734@holonet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 12 Dec 1999 23:08:24 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > boot -v output using the wd driver follows: > > > > That's not very helpful; we know it works. How about some information on > > the problem? > > Well... I'd sure like to send a boot -v for a kernel using ata... I don't > have the right hardware here to use a serial console, however. That's more your problem than ours though. > Here are the relevant lines from the boot sequence (paraphrased, of course): > ad0: piomode=4 dmamode=2 udmamode=-1 cblid=0 > ad0: ATA-? disk at ata0 as master Eek. An old laptop drive. > ad0: 401MB (822016 sectors), 988 cyls, 16 heads, 52 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, PIO > Creating DISK ad0 > Creating DISK wd0 > Mounting root from ufs:/dev/wd0s1a Ultimately you'll want to update /etc/fstab (obviously not yet!) > wd0: invalid primary partition table: no magic Ok. It looks like we need more verbose output from the 'ad' driver, since it believes that it's read the primary partition table, but obviously hasn't. This syncs to some degree with the 'wd' driver's complaining about the recal failing. > Root mount failed: 6 > Mounting root from ufs:wd0s1a > wd0: invalid primary partition table: no magic This destroys my original hypothesis (that the first command was being ignored). You'll need to take this up with Soren; I suspect though that the simplest answer for you is going to be to stick with 'wd' until you get yourself a less-broken disk, or manage to analyse the problem in greater depth. The latter would be greatly assisted if you were able to dig into the 'ad' code a little and see what, if anything, is actually failing. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Dec 12 23:14:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 30D8C14F8F for ; Sun, 12 Dec 1999 23:14:41 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA22321; Mon, 13 Dec 1999 08:14:34 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912130714.IAA22321@freebsd.dk> Subject: Re: Among the ATA casualties... In-Reply-To: <19991212165900.A482@holonet.net> from Adam Wight at "Dec 12, 1999 04:59:00 pm" To: adamw@holonet.net (Adam Wight) Date: Mon, 13 Dec 1999 08:14:34 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Adam Wight wrote: > Against my better judgment, I've been running -current on, among other > machines, a Dell Latitude XP 475C... The wd driver manages to deal with > the inevitable cruft quite nicely, but the ata driver refuses to mount > the root partition. > > To the best of my knowledge the chipset is the Western Digital 8110. > I can supply any other information required, of course. Have you update your /dev with MAKEDEV from usr/src/etc recently? -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 23:33:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id D988C14FEF for ; Sun, 12 Dec 1999 23:33:55 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA26820; Mon, 13 Dec 1999 08:33:43 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912130733.IAA26820@freebsd.dk> Subject: Re: ATA weird message? In-Reply-To: <19991211091053B.haro@tk.kubota.co.jp> from Munehiro Matsuda at "Dec 11, 1999 09:10:53 am" To: haro@tk.kubota.co.jp (Munehiro Matsuda) Date: Mon, 13 Dec 1999 08:33:43 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Munehiro Matsuda wrote: > Hi all, > > I am using -current as of December 9 (CTM:src-cur.4130.gz), and > got following weird ATA related messages while 'make -j4 buildworld'. > I never had this kind of message when using wd drivers. > > ata0-master: ad_timeout: lost disk contact - resetting > ata0: resetting devices .. done Hmm, maybe the timeout in ata-disk.c is too short, try increasing the 5*hz to say 10*hz in line 436, and see if that changes anything.. -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 23:36:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7F21A14D50 for ; Sun, 12 Dec 1999 23:36:14 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA27323; Mon, 13 Dec 1999 08:35:53 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912130735.IAA27323@freebsd.dk> Subject: Re: ATA problem In-Reply-To: <14418.33865.945738.983367@grasshopper.cs.duke.edu> from Andrew Gallatin at "Dec 11, 1999 12:15:59 pm" To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Mon, 13 Dec 1999 08:35:53 +0100 (CET) Cc: gchil0@pop.uky.edu (Greg Childers), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Andrew Gallatin wrote: > > Greg Childers writes: > > Hello, > > > > Seems now is the time to raise problems with ATA, so here goes. I have used the ATA driver > > since its introduction into -current without problem until recently. A kernel from October > > 5 worked fine. Now, it no longer works using ATA, but works fine using the old WD drivers. > > The console freezes after the dmesg and the keyboard is unresponsive. The ata info in > > I'm having similar problems, however mine are spurrious. They happen > maybe 1 in 15 or so reboots. I'm seeing them on two kinds of > machines, both alpha & i386. All the machines I'm seeing this on > have serial consoles, but since about 95% of the machines I take care > of do, they might not mean anything. I haven't seen it on a SCSI > machine, but I'm not sure if that means anything either, since nearly > all our machines boot from IDE disks. > > When they happen, the machine is unresponsive. It will ignore > attempts to break into ddb. I'd have tried to debug it already, but > its pretty damned hard to catch. Usually it only seems to happen when > I reboot a machine from home & cannot walk up & hit the reset button. > :-( Hmm, damn that I can reproduce that error here, I have a machine on constant reboot now, and hope to eventually catch this... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 23:37:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8D5C014C91 for ; Sun, 12 Dec 1999 23:37:53 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA27680; Mon, 13 Dec 1999 08:37:24 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912130737.IAA27680@freebsd.dk> Subject: Re: ata: lost disk contact errors [was: Re: HEADSUP: wd driver will be retired!] In-Reply-To: <19991212125901.A38377@myhakas.matti.ee> from Vallo Kallaste at "Dec 12, 1999 12:59:01 pm" To: vallo@solaris.matti.ee Date: Mon, 13 Dec 1999 08:37:24 +0100 (CET) Cc: dwhite@resnet.uoregon.edu (Doug White), ntakpe@ffab.tide.ti.com (Jean Louis Ntakpe), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Vallo Kallaste wrote: > On Sat, Dec 11, 1999 at 12:57:04PM -0800, Doug White wrote: > > > > I'm getting the "lost disk contact" messages every now and then, but > > > only on our mp3 machine with PIIX3 controller and IBM UDMA/66 disk. It's > > > an PPro machine with Intel mobo. Can it be related to newer IBM disks? > > > > Depends on what 'now and then' is. The Deskstar series of drives was not > > intended to run 24/7, and therefore shut themselves down every week to > > clean the heads. > > Mhm, now I remember the discussion in -current list some time ago. It > can be, yes, but I need to follow the logs to say for sure. About month > ago the messages appeared several times per day, not per week. > Thank you refreshing my memory :-) Well, I use alot of IBM's and I've newer seen them do this... Have you tried upping the timeout in ata-disk.c about line 426 to say 10s and see if it changes behavior ?? -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 12 23:38: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles516.castles.com [208.214.165.80]) by hub.freebsd.org (Postfix) with ESMTP id 3EC9614C8D for ; Sun, 12 Dec 1999 23:38:05 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA05787; Sun, 12 Dec 1999 23:39:59 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912130739.XAA05787@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Soren Schmidt Cc: haro@tk.kubota.co.jp (Munehiro Matsuda), freebsd-current@FreeBSD.ORG Subject: Re: ATA weird message? In-reply-to: Your message of "Mon, 13 Dec 1999 08:33:43 +0100." <199912130733.IAA26820@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Sun, 12 Dec 1999 23:39:59 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems Munehiro Matsuda wrote: > > Hi all, > > = > > I am using -current as of December 9 (CTM:src-cur.4130.gz), and > > got following weird ATA related messages while 'make -j4 buildworld'.= > > I never had this kind of message when using wd drivers. > > = > > ata0-master: ad_timeout: lost disk contact - resetting > > ata0: resetting devices .. done > = > Hmm, maybe the timeout in ata-disk.c is too short, try increasing > the 5*hz to say 10*hz in line 436, and see if that changes anything.. Ugh. Are we still using these short timeouts for I/O transaction = completion? Much pain some time back established that we need at least = 30 seconds for some drives doing internal error recovery, and as long as = the drive is returning something sensible (ie. still busy), we should = give it at least that long. -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Dec 13 0: 1:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4E5E314D16 for ; Mon, 13 Dec 1999 00:01:53 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA33383; Mon, 13 Dec 1999 09:01:37 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912130801.JAA33383@freebsd.dk> Subject: Re: Errors from the ata disk driver In-Reply-To: <14418.39524.290684.380673@grasshopper.cs.duke.edu> from Andrew Gallatin at "Dec 11, 1999 01:43:13 pm" To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Mon, 13 Dec 1999 09:01:37 +0100 (CET) Cc: joeo@nks.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Andrew Gallatin wrote: > > These are UDMA CRC errors, if you upgrade to the latest current, ata > > knows to retry these, only if they persist, something is wrong. > > However it could indicate cable problems, ie bad connectors or maybe > > too long cables.. > > > > He said the disk was attached to a Promise Ultra/33. Does the > backdown to PIO on Promise Ultra controllers work now? I've been > watching the commits to the ata driver, and haven't seen anything that > makes me think that it would.. but I haven't tried it since last week. I've fixed it here (I hope), and it will be in the next batch of fixes. I hope to get through my mailbox today :) -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 0: 3:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id D7C5914FAC for ; Mon, 13 Dec 1999 00:03:22 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA33772; Mon, 13 Dec 1999 09:03:16 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912130803.JAA33772@freebsd.dk> Subject: Re: Errors from the ata disk driver In-Reply-To: from "joeo@nks.net" at "Dec 11, 1999 03:35:24 pm" To: joeo@nks.net Date: Mon, 13 Dec 1999 09:03:16 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems joeo@nks.net wrote: > Will the backdown to PIO mode be permanent till the next reboot of the > machine, or will the driver be able to attempt to return to DMA mode after > a timeout period. I'm only seeing these errors under really heavy disk > activity (mutlitple nfs readers and writers plus rsync/mirror jobs to the > vinum volume in question). The fallback is permanent, but it only occurs after 3 retries on the failed request. If it fails 3 times in a row, there is something really wrong on that channel, ie bad cableing etc etc... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 0:17:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 5794814D07; Mon, 13 Dec 1999 00:17:36 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA37135; Mon, 13 Dec 1999 09:17:35 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912130817.JAA37135@freebsd.dk> Subject: Re: ATA weird message? In-Reply-To: <199912130739.XAA05787@mass.cdrom.com> from Mike Smith at "Dec 12, 1999 11:39:59 pm" To: msmith@FreeBSD.ORG (Mike Smith) Date: Mon, 13 Dec 1999 09:17:35 +0100 (CET) Cc: haro@tk.kubota.co.jp (Munehiro Matsuda), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Mike Smith wrote: > > It seems Munehiro Matsuda wrote: > > > Hi all, > > > > > > I am using -current as of December 9 (CTM:src-cur.4130.gz), and > > > got following weird ATA related messages while 'make -j4 buildworld'. > > > I never had this kind of message when using wd drivers. > > > > > > ata0-master: ad_timeout: lost disk contact - resetting > > > ata0: resetting devices .. done > > > > Hmm, maybe the timeout in ata-disk.c is too short, try increasing > > the 5*hz to say 10*hz in line 436, and see if that changes anything.. > > Ugh. Are we still using these short timeouts for I/O transaction > completion? Much pain some time back established that we need at least > 30 seconds for some drives doing internal error recovery, and as long as > the drive is returning something sensible (ie. still busy), we should > give it at least that long. Not really, the timeout for completing a request on a drive that said it is ready, _should_ complete in much less than 5 secs, but a reset of a hung drive should be waited for 31 secs, which we do allready in ata_reset()... I'm afraid that the sporious timeouts that some are seeing is an artifact of another problem... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 0:33:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles516.castles.com [208.214.165.80]) by hub.freebsd.org (Postfix) with ESMTP id 9688114D76 for ; Mon, 13 Dec 1999 00:33:14 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA06152; Mon, 13 Dec 1999 00:35:51 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912130835.AAA06152@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: rtc0 In-reply-to: Your message of "Sat, 11 Dec 1999 20:17:01 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Dec 1999 00:35:51 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG statclock_disable is set to 1 if you have the 0x20 flag set on your APM device. This should probably no longer be the default. > Oops, try this patch instead, again, it's done wrong, but I couldn't > figure out why statclock_disable was getting a value, and I don't have > time to figure it out. > > --- clock.c.orig Sat Dec 11 19:58:15 1999 > +++ clock.c Sat Dec 11 20:15:01 1999 > @@ -962,7 +962,7 @@ > int apic_8254_trial; > struct intrec *clkdesc; > #endif /* APIC_IO */ > - > + statclock_disable = 0; > if (statclock_disable) { > /* > * The stat interrupt mask is different without the > > > ================================================================= > | Kenneth Culver | FreeBSD: The best OS around. | > | Unix Systems Administrator | ICQ #: 24767726 | > | and student at The | AIM: AgRSkaterq | > | The University of Maryland, | Website: (Under Construction) | > | College Park. | http://www.wam.umd.edu/~culverk/| > ================================================================= > > On Sat, 11 Dec 1999, Kenneth Wayne Culver wrote: > > > I don't know if anyone else was having this problem, and I don't know that > > this is a proper fix, but here goes: > > > > For some reason rtc0 was not working, and I think it's because this > > variable was not initialized, here is the patch: > > > > --- clock.c.orig Sat Dec 11 19:58:15 1999 > > +++ clock.c Sat Dec 11 19:58:30 1999 > > @@ -132,7 +132,7 @@ > > int clkintr_pending; > > int disable_rtc_set; /* disable resettodr() if != 0 */ > > volatile u_int idelayed; > > -int statclock_disable; > > +int statclock_disable = 0; > > u_int stat_imask = SWI_CLOCK_MASK; > > #ifndef TIMER_FREQ > > #define TIMER_FREQ 1193182 > > > > > > the patch should go in /usr/src/sys/i386/isa > > > > ================================================================= > > | Kenneth Culver | FreeBSD: The best OS around. | > > | Unix Systems Administrator | ICQ #: 24767726 | > > | and student at The | AIM: AgRSkaterq | > > | The University of Maryland, | Website: (Under Construction) | > > | College Park. | http://www.wam.umd.edu/~culverk/| > > ================================================================= > > > > > > > > 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 > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Dec 13 0:37: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (Postfix) with ESMTP id C9F0B14ECA for ; Mon, 13 Dec 1999 00:37:01 -0800 (PST) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id 8E6D3A84A; Mon, 13 Dec 1999 09:37:00 +0100 (CET) Date: Mon, 13 Dec 1999 09:37:00 +0100 From: Guido van Rooij To: current@freebsd.org Subject: netstat to show listen queues Message-ID: <19991213093700.A21787@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd like to have a review on the following patch: http://www.freebsd.org/~guido/netstat.diff It adds support to netstat to show listen queue lengths. Manual page diffs are in the working. -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 1:57:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 9B1B015027 for ; Mon, 13 Dec 1999 01:57:51 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id KAA35871 for current@FreeBSD.org; Mon, 13 Dec 1999 10:42:40 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Mon, 13 Dec 1999 10:42:36 +0100 From: Marcel Moolenaar Message-ID: <3854BF8C.ED803CBD@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <99Dec13.132333est.40338@border.alcanet.com.au>, <99Dec13.154631est.40324@border.alcanet.com.au> Subject: Re: make world broken building fortunes Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy wrote: > > >===> games/fortune/datfiles > >PATH=$PATH:/usr/games:/usr/obj/3.0/cvs/src/games/fortune/datfiles/../strfile strfile -Crs /3.0/cvs/src/games/fortune/datfiles/fortunes fortunes.dat > >strfile: illegal option -- C > >strfile [-iorsx] [-c char] sourcefile [datafile] > >*** Error code 1 This is exactly why strfile is built as a tool. > Well, the following fixes that problem for me: > .for f in fortunes fortunes2 fortunes2-o limerick startrek zippy > $f.dat: $f > - PATH=$$PATH:/usr/games:${.OBJDIR}/../strfile \ > + LD_LIBRARY_PATH=${LIBRARY_PATH} \ > + PATH=${.OBJDIR}/../strfile:$$PATH:/usr/games \ > strfile -Crs ${.ALLSRC} ${.TARGET} > .endfor The problem basicly is that the strfile tool is installed in /usr/obj/.../usr/games, which isn't in the path. I think the easiest solution would be (instead of your patches of course): Index: Makefile.inc1 =================================================================== RCS file: /home/ncvs/src/Makefile.inc1,v retrieving revision 1.106 diff -u -r1.106 Makefile.inc1 --- Makefile.inc1 1999/12/12 22:24:08 1.106 +++ Makefile.inc1 1999/12/13 09:40:16 @@ -113,7 +113,7 @@ OBJTREE= ${MAKEOBJDIRPREFIX}/${MACHINE_ARCH} .endif WORLDTMP= ${OBJTREE}${.CURDIR}/${BUILD_ARCH} -STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin +STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games TMPPATH= ${STRICTTMPPATH}:${PATH} # bootstrap/tools make Can you try it and tell me if that works? > And buildworld then dies at: > > colldef -I /3.0/cvs/src/share/colldef -o ru_SU.ISO_8859-5.out /3.0/cvs/src/share/colldef/ru_SU.ISO_8859-5.src > colldef: syntax error near line 1 > *** Error code 69 Yes. I had it built as a tool in my tests, but got lost somehow in the final commit. Thanks, -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 2:19:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id D7FF815083 for ; Mon, 13 Dec 1999 02:19:36 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11xSZj-0007aY-00; Mon, 13 Dec 1999 12:19:27 +0200 From: Sheldon Hearn To: Marcel Moolenaar Cc: current@FreeBSD.ORG Subject: Re: make world broken building fortunes In-reply-to: Your message of "Mon, 13 Dec 1999 10:42:36 +0100." <3854BF8C.ED803CBD@scc.nl> Date: Mon, 13 Dec 1999 12:19:27 +0200 Message-ID: <29173.945080367@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 13 Dec 1999 10:42:36 +0100, Marcel Moolenaar wrote: > I think the easiest solution would be (instead of your patches of > course): > -STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin > +STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games Only if you preceded the line with a comment explaining that the games part of the path is needed exclusively for strfile, which is needed exclusivelty for fortune. I've been bitten once already by undocumented dependencies. :-( Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 2:21:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 393C2150A1 for ; Mon, 13 Dec 1999 02:21:17 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id LAA66098 for current@freebsd.org; Mon, 13 Dec 1999 11:21:16 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912131021.LAA66098@freebsd.dk> Subject: HEADS UP ata driver update! To: current@freebsd.org Date: Mon, 13 Dec 1999 11:21:15 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL54 (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 I've just committed a bunch of fixes and enhancements to the ATA driver, so before submitting new bug reports, PLEASE upgrade to the newest sources, thanks! -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 5:42: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 944561504F for ; Mon, 13 Dec 1999 05:42:05 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 117801CCE; Mon, 13 Dec 1999 21:42:03 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Sheldon Hearn Cc: Marcel Moolenaar , current@FreeBSD.ORG Subject: Re: make world broken building fortunes In-Reply-To: Message from Sheldon Hearn of "Mon, 13 Dec 1999 12:19:27 +0200." <29173.945080367@axl.noc.iafrica.com> Date: Mon, 13 Dec 1999 21:42:03 +0800 From: Peter Wemm Message-Id: <19991213134203.117801CCE@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > > On Mon, 13 Dec 1999 10:42:36 +0100, Marcel Moolenaar wrote: > > > I think the easiest solution would be (instead of your patches of > > course): > > > -STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin > > +STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games > > Only if you preceded the line with a comment explaining that the games > part of the path is needed exclusively for strfile, which is needed > exclusivelty for fortune. > > I've been bitten once already by undocumented dependencies. :-( I wonder if we should move fortune to usr.bin? It's hardly a game and I'm way beyond tired of it being left out of standard paths... (ie: "/bin:/usr/bin[:/usr/local/bin]") Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 6: 3:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with SMTP id 23B3B14F6E for ; Mon, 13 Dec 1999 06:03:51 -0800 (PST) (envelope-from matt@camtech.net.au) Received: from dialup-ad-14-32.camtech.net.au ([203.55.242.160]) by camtech.net.au ; Tue, 14 Dec 1999 00:33:48 +1030 Date: Tue, 14 Dec 1999 00:34:28 +1030 (CST) From: Matthew Thyer X-Sender: matt@localhost Reply-To: thyerm@camtech.net.au To: current@freebsd.org Subject: RELEASE timelines 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 What is the big rush to 4.0-RELEASE ? With all the new functionality and recent changes there are some things that need to be bedded in (I'm thinking newpcm and ATA). Maybe I'm saying this because my SB16 PnP has only just been fixed and my CD-ROM drive doesn't work under the ATA driver (I'm about to try the most recent fixes so dont yell at me yet) but maybe I'm saying this because things seem a bit rushed. Consider the 2.2 stream that went through many more releases (counting 2.2.1 -> 2.2.8). Using that yardstick you'd expect 4.0 to stay in development until 3.7 is released. I know 7 releases of the 2.2 stream was considerred a few too many but surely we can hold 4.0 back a bit longer considerring the age of some of the code. -- /=======================================================================\ | 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 Mon Dec 13 6:26: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 1D54714D7C for ; Mon, 13 Dec 1999 06:25:51 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11xWPr-0008FC-00; Mon, 13 Dec 1999 16:25:31 +0200 From: Sheldon Hearn To: thyerm@camtech.net.au Cc: current@FreeBSD.ORG Subject: Re: RELEASE timelines In-reply-to: Your message of "Tue, 14 Dec 1999 00:34:28 +1030." Date: Mon, 13 Dec 1999 16:25:31 +0200 Message-ID: <31693.945095131@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 14 Dec 1999 00:34:28 +1030, Matthew Thyer wrote: > What is the big rush to 4.0-RELEASE ? We are relying on public awareness of the fact that .0 releases (in just about any project) are _going_ to have issues. We need the 4 branch out out there in the hands of the masses. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 6:34:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id CC0A214D50 for ; Mon, 13 Dec 1999 06:34:12 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id OAA38467; Mon, 13 Dec 1999 14:34:29 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <31693.945095131@axl.noc.iafrica.com> Date: Mon, 13 Dec 1999 14:34:29 -0000 (GMT) From: "Steve O'Hara-Smith" To: Sheldon Hearn Subject: Re: RELEASE timelines Cc: current@FreeBSD.ORG, thyerm@camtech.net.au Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Dec-99 Sheldon Hearn wrote: > > > On Tue, 14 Dec 1999 00:34:28 +1030, Matthew Thyer wrote: > >> What is the big rush to 4.0-RELEASE ? > > We are relying on public awareness of the fact that .0 releases (in just > about any project) are _going_ to have issues. We need the 4 branch out > out there in the hands of the masses. Presumably then like 3.0, 4.0 will not be -stable for a while. ------------------------------------------------------- Tell a computer to WIN and ... ... You lose ------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 6:49:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with ESMTP id BB95214EB0 for ; Mon, 13 Dec 1999 06:49:43 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: from lcb13.cvzoom.net (lcb13.cvzoom.net [63.65.159.13]) by ns.cvzoom.net (8.9.3/8.9.3) with ESMTP id JAA00796; Mon, 13 Dec 1999 09:26:53 -0500 (EST) Date: Mon, 13 Dec 1999 00:45:24 -0500 (EST) From: Donn Miller To: "Steve O'Hara-Smith" Cc: Sheldon Hearn , current@FreeBSD.ORG, thyerm@camtech.net.au Subject: Re: RELEASE timelines 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 Mon, 13 Dec 1999, Steve O'Hara-Smith wrote: > Tell a computer to WIN and ... > ... You lose Actually, I always thought there was something subliminal about typing "WIN". Funny how they didn't choose "WIND". It's like, you're typing "WIN", so you in your subconcious, you're thinking winner. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 6:51:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 3BF5C14E60 for ; Mon, 13 Dec 1999 06:51:38 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m2.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX9911-Fujitsu Gateway) id XAA22872; Mon, 13 Dec 1999 23:51:10 +0900 (JST) Received: from incapgw.fujitsu.co.jp by m2.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id XAA18150; Mon, 13 Dec 1999 23:51:09 +0900 (JST) Received: from localhost ([192.168.245.155]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id XAA21295; Mon, 13 Dec 1999 23:51:08 +0900 (JST) To: clive@GnatS.CirX.ORG Cc: current@FreeBSD.ORG Subject: Re: What happened to netstat? In-Reply-To: <19991213140807.A71230@host.cer.ntnu.edu.tw> References: <19991212103701.A55038@dmaddox.conterra.com> <19991213140807.A71230@host.cer.ntnu.edu.tw> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991213235133S.shin@nd.net.fujitsu.co.jp> Date: Mon, 13 Dec 1999 23:51:33 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 17 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Dec 12, 1999 at 10:37:01AM -0500, Donald J . Maddox wrote: > > After rebuilding World and kernel last night, I find that the behavior of > > 'netstat -a' has changed... Only UNIX domain sockets are shown in the > > Errr... may I complain ? > I got the same problem :( > > current last night. I'm sorry, that is due to my commit at 1999/12/07 09:39:17 PST. It should be fixed by my another commit at 1999/12/12 16:39:21 PST. Please update sys/netinet/udp_usrreq.c and sys/netinet/tcp_usrreq.c and rebuild new kernel to fix the problem. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 8:11: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id E833E15199 for ; Mon, 13 Dec 1999 08:10:58 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA91358; Mon, 13 Dec 1999 11:10:36 -0500 (EST) (envelope-from wollman) Date: Mon, 13 Dec 1999 11:10:36 -0500 (EST) From: Garrett Wollman Message-Id: <199912131610.LAA91358@khavrinen.lcs.mit.edu> To: Guido van Rooij Cc: current@FreeBSD.ORG Subject: netstat to show listen queues In-Reply-To: <19991213093700.A21787@gvr.gvr.org> References: <19991213093700.A21787@gvr.gvr.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I'd like to have a review on the following patch: > http://www.freebsd.org/~guido/netstat.diff > It adds support to netstat to show listen queue lengths. > Manual page diffs are in the working. Looks good to me. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 8:47:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from blackdawn.com (deepspace9.dcds.edu [207.231.151.2]) by hub.freebsd.org (Postfix) with ESMTP id 1E0BF15170 for ; Mon, 13 Dec 1999 08:47:38 -0800 (PST) (envelope-from will@blackdawn.com) Received: (from will@localhost) by blackdawn.com (8.9.3/8.9.3) id LAA00472; Mon, 13 Dec 1999 11:47:25 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 13 Dec 1999 11:47:10 -0500 (EST) From: will andrews To: thyerm@camtech.net.au Subject: FW: RE: RELEASE timelines Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Dec-99 Matthew Thyer wrote: > Consider the 2.2 stream that went through many more releases (counting > 2.2.1 -> 2.2.8). Using that yardstick you'd expect 4.0 to stay in > development until 3.7 is released. I know 7 releases of the 2.2 stream > was considerred a few too many but surely we can hold 4.0 back a bit > longer considerring the age of some of the code. You may view this as inconsistent, but the fact is that 3.x's development cycle took far too long (I believe around 2 years). They are trying to shorten this for 4.0. I could name many significant differences between 3.x and 4.x (bdev, signals, cardbus, ata, camified aic, and so on), but my favorite would be the up-to-date compiler. Makes porting certain C++-based programs + libraries a helluva lot easier. Kudos to David O'Brien. ;-) I'm running 4.0-CURRENT on this machine. I would not mind seeing "official" support for 4.0-RELEASE, since I would not be under as much pressure to get novel programs working with an obsolete compiler.. Great way to kick off 2000... release 4.0-RELEASE on my 18th birthday (March 13, 2000). I'd say they'll be pretty close. :-) Besides, in the 2 months I've been subscribed to cvs-all, I've seen >7500 commits (~125/day), 95% of which were against -CURRENT. I'd say it's had plenty of testing. -STABLE is obsolete. You Will Be Assimilated. Resistence is Futile. =|-) -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 10:23:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.freebsd.org.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id E7B0E151D1 for ; Mon, 13 Dec 1999 10:23:47 -0800 (PST) (envelope-from osa@freebsd.org.ru) Received: from localhost (localhost.freebsd.org.ru [127.0.0.1]) by ozz.freebsd.org.ru (8.9.3/8.9.3) with ESMTP id VAA07001 for ; Mon, 13 Dec 1999 21:23:44 +0300 (MSK) (envelope-from osa@freebsd.org.ru) Date: Mon, 13 Dec 1999 21:23:44 +0300 (MSK) From: Sergey Osokin To: current@FreeBSD.org Subject: boot failed with "options ata0" & etc. at kernel... 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 Hello! I rebuild all ad* devices at /dev with new MAKEDEV from /usr/src/etc at my -current, but still have following problem... ........... ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ........... ad0: ATA-3 disk at ata0 as master ad0: 2503MB (5126688 sectors), 5086 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, DMA acd0: CDROM drive at ata1 as master acd0: read 171KB/s (8250KB/s), 128KB buffer, UDMA33 acd0: supported read types: CD-R, CD-RW, CD-DA stream, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked afd0: rewriteable drive at ata1 as slave afd0: 120MB (246528 sectors), 963 cyls, 8 heads, 32 S/T, 512 B/S afd0: 533KB/s, PIO afd0: Medium: Unknown media (0x0) Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted WARNING: R/W mount of / denied. Filesystem is not clean - run fsck # mount /dev/ad0s1a on / (ufs, local, read-only, writes: sync 2 async 0, reads: sync 149 async 1) /dev/ad0s1f on /usr (ufs, local, nodev, soft-updates, writes: sync 2 async 0, reads: sync 76 async 0) /dev/ad0s1e on /var (ufs, local, nodev, noexec, nosuid, soft-updates, writes: sync 2 async 0, reads: sync 1 async 0) procfs on /proc (procfs, local) # fsck / ** /dev/ad0s1a ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 1271 files, 24082 used, 39421 free (152 frags, 4909 blocks, 0.2% fragmentation) then i simply type Ctrl-D & system gone up correct... Whats may wrong? Rgdz, Sergey A. Osokin, osa@etrust.ru osa@freebsd.org.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 10:25: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 873881548F for ; Mon, 13 Dec 1999 10:24:58 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id KAA14747; Mon, 13 Dec 1999 10:24:28 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912131824.KAA14747@gndrsh.dnsmgr.net> Subject: Re: make world broken building fortunes In-Reply-To: <29173.945080367@axl.noc.iafrica.com> from Sheldon Hearn at "Dec 13, 1999 12:19:27 pm" To: sheldonh@uunet.co.za (Sheldon Hearn) Date: Mon, 13 Dec 1999 10:24:27 -0800 (PST) Cc: marcel@scc.nl (Marcel Moolenaar), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 > > > On Mon, 13 Dec 1999 10:42:36 +0100, Marcel Moolenaar wrote: > > > I think the easiest solution would be (instead of your patches of > > course): > > > -STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin > > +STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games > > Only if you preceded the line with a comment explaining that the games > part of the path is needed exclusively for strfile, which is needed > exclusivelty for fortune. And protect it all by !defined(NOGAMES) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 10:59:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-25.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.153]) by hub.freebsd.org (Postfix) with ESMTP id B0DA11517A; Mon, 13 Dec 1999 10:59:10 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id SAA00803; Mon, 13 Dec 1999 18:59:08 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id RAA00338; Mon, 13 Dec 1999 17:59:24 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912131759.RAA00338@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: "CHOI, Junho" Cc: Jon Hamilton , current@FreeBSD.ORG, stable@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: ppp over pty: trying to detect CD In-Reply-To: Message from "CHOI, Junho" of "12 Dec 1999 19:16:52 +0900." <86bt7wlazv.fsf@gradius.myhome> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Dec 1999 17:59:24 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ah, I see the problem. I have a fix - I'm about to apply it to -current and ask jkh for permission to MFC. I've attached the -stable patch for your viewing enjoyment.... > >>>>> "JH" == Jon Hamilton writes: > > JH> Running -current from this afternoon, I am having a strange > JH> symptom with ppp over a pty; ppp does not detect that the pty > JH> does not support carrier, and will cycle once per second > JH> waiting for CD to appear. Putting ``set cd off'' in my > JH> ppp.conf for that target fixed the problem, but I thought I'd > JH> mention it nonetheless, since that didn't used to be > JH> required. Certainly not all that big a deal, but I thought it > JH> was worth a mention. > > JH> FreeBSD 4.0-CURRENT #13: Sat Dec 11 20:31:42 CST 1999 > > I am using 3-STABLE but I have the same problem with you. I think it > comes after adding pppoe support in pppd(after 3.3-RELEASE). I am > -STABLE user but I had to back to 3.3-RELEASE's ppp... I am using ADSL > service with pptpclient. > > JH> and the syslog with debugging turned on, with no "set cd" in the config: > > JH> Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: deflink: Using tty_Timeout [0x8072d44] > JH> Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: Waiting for carrier > JH> Dec 11 20:48:21 woodstock ppp[3106]: tun1: Debug: deflink: Using tty_Timeout [0x8072d44] > JH> Dec 11 20:48:21 woodstock ppp[3106]: tun1: Debug: Waiting for carrier > > JH> [ and on and on and on ] > > -- > +++ Any opinions in this posting are my own and not those of my employers +++ > CHOI, Junho > - Korea FreeBSD Users Group > - Public Service, Youido Post Office - Web Data Bank -- Brian Don't _EVER_ lose your sense of humour ! Index: tty.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/ppp/tty.c,v retrieving revision 1.12.2.3 diff -u -r1.12.2.3 tty.c --- tty.c 1999/11/19 23:48:04 1.12.2.3 +++ tty.c 1999/12/13 07:30:44 @@ -112,6 +112,7 @@ log_Printf(LogDEBUG, "%s: ioctl error (%s)!\n", p->link.name, strerror(errno)); timer_Stop(&dev->Timer); + dev->mbits = TIOCM_CD; return; } } else @@ -187,8 +188,7 @@ return CARRIER_PENDING; /* Not yet ! */ } - return Online(dev) || !p->cfg.cd.necessity == CD_REQUIRED ? - CARRIER_OK : CARRIER_LOST; + return Online(dev) ? CARRIER_OK : CARRIER_LOST; } static int To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 11: 5:55 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id ECE5014C9F; Mon, 13 Dec 1999 11:05:53 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E0B681CD73E; Mon, 13 Dec 1999 11:05:53 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 13 Dec 1999 11:05:53 -0800 (PST) From: Kris Kennaway To: Peter Wemm Cc: Sheldon Hearn , Marcel Moolenaar , current@FreeBSD.ORG Subject: Speaking of moving files (Re: make world broken building fortunes ) In-Reply-To: <19991213134203.117801CCE@overcee.netplex.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 Mon, 13 Dec 1999, Peter Wemm wrote: > I wonder if we should move fortune to usr.bin? It's hardly a game and I'm > way beyond tired of it being left out of standard paths... > (ie: "/bin:/usr/bin[:/usr/local/bin]") I have no opinion about fortune, but I do think that md5 should be moved from /sbin to /bin - it's hardly a "system program or administration utility" but is a quite general-purpose tool. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 11: 9: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from host.cer.ntnu.edu.tw (cer.ntnu.edu.tw [140.122.119.9]) by hub.freebsd.org (Postfix) with ESMTP id 9021414CA4 for ; Mon, 13 Dec 1999 11:08:49 -0800 (PST) (envelope-from clive@host.cer.ntnu.edu.tw) Received: (from clive@localhost) by host.cer.ntnu.edu.tw (8.9.3/8.9.3) id DAA74251; Tue, 14 Dec 1999 03:11:27 +0800 (CST) (envelope-from clive) Date: Tue, 14 Dec 1999 03:11:27 +0800 From: Clive Lin To: Guido van Rooij Cc: current@FreeBSD.ORG Subject: Re: netstat to show listen queues Message-ID: <19991214031127.A74211@host.cer.ntnu.edu.tw> Reply-To: Clive Lin References: <19991213093700.A21787@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991213093700.A21787@gvr.gvr.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, it looks GREAT ! X clive@cartier ~> netstat -a -f inet -L Current listen queue sizes (qlen/incqlen/maxqlen) Listen Local Address 0/0/5 *.1029 0/0/5 *.1028 0/0/5 *.1027 0/0/5 *.1026 0/0/5 *.1025 0/0/128 *.6001 0/0/64 *.ppasswd 0/0/64 *.ptelnet 0/0/64 *.telnet 0/0/64 *.ftp 0/0/5 *.ssh 0/0/5 *.netbios-ssn 0/0/128 *.5432 0/0/10 *.innbbsd 0/0/3 *.finger 0/0/3 *.bbs 0/0/3 *.3838 0/0/128 *.http 0/0/128 *.https 0/0/3 *.auth 0/0/10 *.smtp X clive@cartier ~> On Mon, Dec 13, 1999 at 09:37:00AM +0100, Guido van Rooij wrote: > I'd like to have a review on the following patch: > http://www.freebsd.org/~guido/netstat.diff > > It adds support to netstat to show listen queue lengths. > Manual page diffs are in the working. > > -Guido -- CirX Clive Lin FreeBSD - The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 11:19:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130]) by hub.freebsd.org (Postfix) with ESMTP id 10E0C15159; Mon, 13 Dec 1999 11:19:10 -0800 (PST) (envelope-from lyndon@orthanc.ab.ca) Received: from orthanc.ab.ca (localhost.orthanc.ab.ca [127.0.0.1]) by orthanc.ab.ca (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id dBDJJ8Q19201; Mon, 13 Dec 1999 12:19:08 -0700 (MST) Message-Id: <199912131919.dBDJJ8Q19201@orthanc.ab.ca> To: Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Sat, 11 Dec 1999 17:41:25 PST." <199912120141.RAA00880@mass.cdrom.com> Date: Mon, 13 Dec 1999 12:19:07 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Mike" == Mike Smith writes: Mike> The "right" solution is and has always been to name your Mike> disks and mount them by name. Once devfs is a reality, Mike> we'll be able to do just this. Until then, the problem's Mike> not really as bad as you make it out to be. I like the assigned-name solution. I still don't like dynamic disk names. It's not a show-stopper by any stretch, but if you move disks around, (not uncommon on development machines) it's a pain. And while you're correct about the boot/fsck issues, adding a renumbering in /etc/fstab to my restart sequence isn't doing anything to get the machine back up quickly (or reliably). Anyway, enough of this -- I have config files to go hardwire :-) --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 11:23:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 5C03E1528A for ; Mon, 13 Dec 1999 11:23:40 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id OAA02505; Mon, 13 Dec 1999 14:23:31 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA05581; Mon, 13 Dec 1999 14:23:00 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 13 Dec 1999 14:23:00 -0500 (EST) To: Soren Schmidt Cc: joeo@nks.net, freebsd-current@FreeBSD.ORG Subject: Re: Errors from the ata disk driver In-Reply-To: <199912130801.JAA33383@freebsd.dk> References: <14418.39524.290684.380673@grasshopper.cs.duke.edu> <199912130801.JAA33383@freebsd.dk> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14421.18254.748286.640261@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt writes: > It seems Andrew Gallatin wrote: > > > These are UDMA CRC errors, if you upgrade to the latest current, ata > > > knows to retry these, only if they persist, something is wrong. > > > However it could indicate cable problems, ie bad connectors or maybe > > > too long cables.. > > > > > > > He said the disk was attached to a Promise Ultra/33. Does the > > backdown to PIO on Promise Ultra controllers work now? I've been > > watching the commits to the ata driver, and haven't seen anything that > > makes me think that it would.. but I haven't tried it since last week. > > I've fixed it here (I hope), and it will be in the next batch of fixes. > I hope to get through my mailbox today :) Thanks. I'm running a kernel built with them now. If/when we see CRC errors, I'll let you know what happens. We don't see them frequently (a few times a month), so it might be a while. Thanks again, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 13:45:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (ferg5200-2-100.cpinternet.com [208.149.16.100]) by hub.freebsd.org (Postfix) with ESMTP id 8FC2014D76 for ; Mon, 13 Dec 1999 13:45:38 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id PAA04938; Mon, 13 Dec 1999 15:45:15 -0600 (CST) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 13 Dec 1999 15:45:15 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: ken@kdm.org Cc: current@freebsd.org Subject: Re: HEADSUP: wd driver will be retired! X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14421.26625.277025.414924@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What I didn't like about CAM was that I lost my tape drive. Since I had all my backups and archives on DAT, it felt like a bad thing. Which reminds me -- can anyone spare a 2.1 CD? Please send me private mail, if so: I foolishly neglected to convert to CD, and now I can't find 2.1 on the web anywhere. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 13:51:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id EFBAE14C40 for ; Mon, 13 Dec 1999 13:51:34 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA32767; Mon, 13 Dec 1999 14:51:14 -0700 (MST) (envelope-from ken) Date: Mon, 13 Dec 1999 14:51:14 -0700 From: "Kenneth D. Merry" To: Anthony Kimball Cc: current@freebsd.org Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991213145114.A32722@panzer.kdm.org> References: <14421.26625.277025.414924@avalon.east> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <14421.26625.277025.414924@avalon.east>; from alk@pobox.com on Mon, Dec 13, 1999 at 03:45:15PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 13, 1999 at 15:45:15 -0600, Anthony Kimball wrote: > > What I didn't like about CAM was that I lost my tape drive. Since I > had all my backups and archives on DAT, it felt like a bad thing. What do you mean you "lost" your tape drive? CAM has included a tape driver almost from day one, and it certainly went into the tree with a tape driver. It certainly works with *my* DAT drive... > Which reminds me -- can anyone spare a 2.1 CD? Please send me private > mail, if so: I foolishly neglected to convert to CD, and now I can't > find 2.1 on the web anywhere. Do you mean straight 2.1, or a release in the 2.1 series? If you want 2.1.7.1, check here: ftp://ftp.kdm.org/pub/FreeBSD Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 15: 2: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext04.compaq.com (mailext04.compaq.com [207.18.199.42]) by hub.freebsd.org (Postfix) with ESMTP id 350691515B for ; Mon, 13 Dec 1999 15:02:02 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: by mailext04.compaq.com (Postfix, from userid 12345) id 9D7D1104B8C; Mon, 13 Dec 1999 17:02:01 -0600 (CST) Received: from mailint01.im.hou.compaq.com (mailint01.compaq.com [207.18.199.34]) by mailext04.compaq.com (Postfix) with ESMTP id 8E7F6FB101; Mon, 13 Dec 1999 17:02:01 -0600 (CST) Received: by mailint01.im.hou.compaq.com (Postfix, from userid 12345) id 63AF4825D3; Mon, 13 Dec 1999 17:01:54 -0600 (CST) Received: from mojave.worldwide.lemis.com (unknown [155.186.83.42]) by mailint01.im.hou.compaq.com (Postfix) with ESMTP id CD89578B42; Mon, 13 Dec 1999 17:01:53 -0600 (CST) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id PAA00394; Sat, 11 Dec 1999 15:44:00 -0600 (CST) (envelope-from grog) Date: Sat, 11 Dec 1999 15:44:00 -0600 From: Greg Lehey To: Poul-Henning Kamp Cc: Warner Losh , Kris Kennaway , Luoqi Chen , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991211154400.A359@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <199912110132.SAA26623@harmony.village.org> <12376.944898748@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <12376.944898748@critter.freebsd.dk>; from phk@critter.freebsd.dk on Sat, Dec 11, 1999 at 08:52:28AM +0100 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Saturday, 11 December 1999 at 8:52:28 +0100, Poul-Henning Kamp wrote: > In message <199912110132.SAA26623@harmony.village.org>, Warner Losh writes: >> In message <7881.944870115@critter.freebsd.dk> Poul-Henning Kamp writes: >> : You overlook one simple thing here: If we want the ata driver tested, >> : we need to make existing kernel configs break, otherwise people >> : will not change them to use ata. We know this from bitter experience. >> >> If all you are talking about is something like: >> >> Index: files.i386 >> =================================================================== >> RCS file: /home/imp/FreeBSD/CVS/src/sys/i386/conf/files.i386,v >> retrieving revision 1.282 >> diff -u -r1.282 files.i386 >> --- files.i386 1999/11/28 17:51:06 1.282 >> +++ files.i386 1999/12/11 01:31:00 >> @@ -318,6 +318,7 @@ >> i386/isa/stallion.c optional stl >> i386/isa/tw.c optional tw >> i386/isa/vesa.c optional vga >> +i386/isa/SirNotAppaeringInThisKerenl.c optional wd >> i386/isa/wd.c optional wd >> i386/isa/wd.c optional wdc >> i386/isa/wfd.c optional wfd >> >> >> I could go along with that. I've been trying to figure out exactly what you mean with this change. I've decided you mean this is a line you need to remove in order to build a kernel with wd. Correct? That might work, but I think it's a bit of a kludge. Why not just change the name of the driver to owd? That way people will have to make a conscious effort to stay with that driver, and we can issue them with the dire warnings about the effects of doing so. > And probably an > #error "Don't use this driver, use ata-disk instead" > in wd.d Remember this fix is supposed to be for non-CURRENT users, people who are traumatized enough already. A warning from config(8) would serve a similar purpose. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 15: 2:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext03.compaq.com (mailext03.compaq.com [207.18.199.41]) by hub.freebsd.org (Postfix) with ESMTP id C365D153A9 for ; Mon, 13 Dec 1999 15:02:09 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: by mailext03.compaq.com (Postfix, from userid 12345) id C1AE3151FB8; Mon, 13 Dec 1999 17:02:08 -0600 (CST) Received: from mailint01.im.hou.compaq.com (mailint01.compaq.com [207.18.199.34]) by mailext03.compaq.com (Postfix) with ESMTP id BAAB214850C; Mon, 13 Dec 1999 17:02:08 -0600 (CST) Received: by mailint01.im.hou.compaq.com (Postfix, from userid 12345) id 5DD0C825C3; Mon, 13 Dec 1999 17:02:01 -0600 (CST) Received: from mojave.worldwide.lemis.com (unknown [155.186.83.42]) by mailint01.im.hou.compaq.com (Postfix) with ESMTP id CFB3578B42; Mon, 13 Dec 1999 17:02:00 -0600 (CST) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id MAA01017; Sat, 11 Dec 1999 12:54:12 -0600 (CST) (envelope-from grog) Date: Sat, 11 Dec 1999 12:54:12 -0600 From: Greg Lehey To: Poul-Henning Kamp Cc: Nate Williams , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991211125412.K760@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <199912101752.KAA19725@mt.sri.com> <6120.944848909@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <6120.944848909@critter.freebsd.dk>; from phk@critter.freebsd.dk on Fri, Dec 10, 1999 at 07:01:49PM +0100 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Friday, 10 December 1999 at 19:01:49 +0100, Poul-Henning Kamp wrote: > In message <199912101752.KAA19725@mt.sri.com>, Nate Williams writes: >>> In a few days time the wd driver will be retired from FreeBSDs >>> i386 architecture. >> >> Given that the ATA driver just went active a few minutes ago, I think a >> period of shakeout time would be called for. I think that time should >> be longer than a few days, and should be in 4.0, and then retired in >> 4.1. > > The ata driver has been available for you and other to test for a long > time. Oh. Somehow I missed this. Sure, I saw commits, but I can't recall a "HEADS UP: ata is good enough for general testing now". If I had done so, I might have changed months ago, and a lot of this principle discussion would be deferred to the next night of the long axes. > 4.0-REL is still some time away, so if you are quick you can still > give it a good shakeout and have any bugs you find fixed before > 4.0-RELEASE. Again, it's not the bugs I'm worried about. Anyway, the 'else' part must read: and if not, it will go into -RELEASE buggy. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 15: 2:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext12.compaq.com (mailext12.compaq.com [207.18.199.188]) by hub.freebsd.org (Postfix) with ESMTP id 9D4EC15375 for ; Mon, 13 Dec 1999 15:02:08 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: by mailext12.compaq.com (Postfix, from userid 12345) id A86985790E; Mon, 13 Dec 1999 17:02:07 -0600 (CST) Received: from mailint01.im.hou.compaq.com (mailint01.compaq.com [207.18.199.34]) by mailext12.compaq.com (Postfix) with ESMTP id A116854602; Mon, 13 Dec 1999 17:02:07 -0600 (CST) Received: by mailint01.im.hou.compaq.com (Postfix, from userid 12345) id 98553825EB; Mon, 13 Dec 1999 17:02:00 -0600 (CST) Received: from mojave.worldwide.lemis.com (unknown [155.186.83.42]) by mailint01.im.hou.compaq.com (Postfix) with ESMTP id 11BD578B42; Mon, 13 Dec 1999 17:02:00 -0600 (CST) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id OAA00391; Sat, 11 Dec 1999 14:25:54 -0600 (CST) (envelope-from grog) Date: Sat, 11 Dec 1999 14:25:54 -0600 From: Greg Lehey To: Peter Wemm Cc: Dieter Rothacker , Michael Kennett , freebsd-current@FreeBSD.ORG Subject: Wiring drive IDs (was: HEADSUP: wd driver will be retired!) Message-ID: <19991211142553.A359@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <19991211102842.C18331CA0@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991211102842.C18331CA0@overcee.netplex.com.au>; from peter@netplex.com.au on Sat, Dec 11, 1999 at 06:28:42PM +0800 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 p On Saturday, 11 December 1999 at 18:28:42 +0800, Peter Wemm wrote: > Dieter Rothacker wrote: >> On Sat, 11 Dec 1999 14:21:25 +0800 (WST), Michael Kennett wrote: >> >>> Note that wd1 is not present. This caused a mild hickup when rebooting the >>> new kernel, since the new ata controller assigned the labels ad0 and ad1 to >>> the drives. It was not possible to boot into multiuser mode without changin > g >>> the /etc/fstab file to rename the /dev/wd2* entries to /dev/ad1*. That was >>> easy to fix, however for a newbie it might cause problems. I mention it now > , >>> since the upgrade from 3.x might need special handling of this case (?). >> >> You should use the kernel option >> "options ATA_STATIC_ID" >> for such cases. At least it works for me :-) > > I think this should only apply to the /dev/wd* compatability devices. ie: > use the correct numbering for new installs onto ad*, but still support the old > spread-out naming for wd*. This used to be more important as it required > fiddling with $root_disk_unit, but the new mountroot code has relieved the > pressure there. We've been through this before (and no, it has nothing to do with Danish axes :-) As long as we refer to them in /etc/fstab, we should have consistent ways of referring to specific drives. I think the *correct* way to refer to drives is by an ID field on the drive itself, the way Vinum does it. That way you could swap drives around anyway you want and the system can handle, and you would still be able to locate your partitions. But in the meantime, it's nice to know that you can add a primary slave without your fstab falling apart. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 15: 2:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext02.compaq.com (mailext02.compaq.com [207.18.199.33]) by hub.freebsd.org (Postfix) with ESMTP id ABE7415425 for ; Mon, 13 Dec 1999 15:02:10 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: by mailext02.compaq.com (Postfix, from userid 12345) id 4F9479A82F; Mon, 13 Dec 1999 17:02:09 -0600 (CST) Received: from mailint01.im.hou.compaq.com (mailint01.compaq.com [207.18.199.34]) by mailext02.compaq.com (Postfix) with ESMTP id 3DB1C90D82; Mon, 13 Dec 1999 17:02:09 -0600 (CST) Received: by mailint01.im.hou.compaq.com (Postfix, from userid 12345) id 37A31825C3; Mon, 13 Dec 1999 17:02:02 -0600 (CST) Received: from mojave.worldwide.lemis.com (unknown [155.186.83.42]) by mailint01.im.hou.compaq.com (Postfix) with ESMTP id 8AD9178B42; Mon, 13 Dec 1999 17:02:01 -0600 (CST) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id MAA01045; Sat, 11 Dec 1999 12:58:31 -0600 (CST) (envelope-from grog) Date: Sat, 11 Dec 1999 12:58:31 -0600 From: Greg Lehey To: Poul-Henning Kamp Cc: Nate Williams , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991211125831.M760@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <199912101815.LAA20053@mt.sri.com> <6332.944849983@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <6332.944849983@critter.freebsd.dk>; from phk@critter.freebsd.dk on Fri, Dec 10, 1999 at 07:19:43PM +0100 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Friday, 10 December 1999 at 19:19:43 +0100, Poul-Henning Kamp wrote: > In message <199912101815.LAA20053@mt.sri.com>, Nate Williams writes: > >>>> And your point is? I'm a user, not a developer. If I wanted to be a >>>> developer, I'd have written my own device driver. I want to *USE* >>>> FreeBSD, not develop it. >>> >>> Then don't run -current. >> >> I don't, but I will be running 4.0, which won't have a WD driver. > > > Maybe we should put a special marker in -currents sendmail and > reject all email to the current list if they don't originate > from such a system. > > > So, if you're not running -current, please stop whining on the > -current list will you ? > > 4.0 will have a perfectly good diskdriver, we probably have two > entire months to find and nail any remaning bugs, so what the > proton do you think you're acheiving by whining here ? Two months? I thought the date was 15 January. Anyway, it's fairly evident what Nate's "whining" about. What part of "FUNCTIONALITY LOSS" don't you understand? > I'll tell you in case you can't figure out the answer to that rather > simple question: You're annoying people and wasting developer time. > That's what. OK, why don't you save time and leave wd in the tree. Comment it out of GENERIC, leave a comment explaining what it's for and that it will go away as soon as ata has the complete functionality. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 15: 2:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext04.compaq.com (mailext04.compaq.com [207.18.199.42]) by hub.freebsd.org (Postfix) with ESMTP id 08AF01542D; Mon, 13 Dec 1999 15:02:12 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: by mailext04.compaq.com (Postfix, from userid 12345) id 7FF97104BDF; Mon, 13 Dec 1999 17:02:11 -0600 (CST) Received: from mailint01.im.hou.compaq.com (mailint01.compaq.com [207.18.199.34]) by mailext04.compaq.com (Postfix) with ESMTP id 6EBADFB101; Mon, 13 Dec 1999 17:02:11 -0600 (CST) Received: by mailint01.im.hou.compaq.com (Postfix, from userid 12345) id 4B478825EA; Mon, 13 Dec 1999 17:02:04 -0600 (CST) Received: from mojave.worldwide.lemis.com (unknown [155.186.83.42]) by mailint01.im.hou.compaq.com (Postfix) with ESMTP id CA48D78B42; Mon, 13 Dec 1999 17:02:02 -0600 (CST) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id MAA01003; Sat, 11 Dec 1999 12:51:21 -0600 (CST) (envelope-from grog) Date: Sat, 11 Dec 1999 12:51:21 -0600 From: Greg Lehey To: Stephen McKay , Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991211125121.J760@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <199912110503.PAA01950@nymph.detir.qld.gov.au> <199912110557.VAA00518@mass.cdrom.com> <199912110158.RAA04944@mass.cdrom.com> <199912110503.PAA01950@nymph.detir.qld.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912110503.PAA01950@nymph.detir.qld.gov.au>; from syssgm@detir.qld.gov.au on Sat, Dec 11, 1999 at 03:03:19PM +1000 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Saturday, 11 December 1999 at 15:03:19 +1000, Stephen McKay wrote: > On Friday, 10th December 1999, Mike Smith wrote: > >> The same mentality that made the CAM cutover a "debacle" is making the >> ata cutover a "debacle". > > This "mentality" might be an unavoidable part of human nature. I found > my first reaction was "How dare they take away something I have now?!" > and it took some careful thinking to see that my loss was actually very > small against future benefits. It might be that these things have to be > predicted by -core and handled "touchy feely" like: > > core: What if we do this ? > public: Um, sounds scary. When will you do it? Will I lose anything? > core: We think a month from now, and you will lose support for and . > public: We don't use and any more, so fine. > > instead of the current (caricatured for emphasis): > > core: We will do soon. Probably today. > public: Oh my God! > core: It's for your own good. You always complain and make it difficult! > public: We don't want to change anything, ever! It's so hard! You must > support all my hardware for ever and ever! You obviously haven't seen it from this viewpoint (s/core/committers/): committers: We will do soon. Probably today. public: What does this mean for me? committers: It's all new, all better, much better code. public: Will it do everything the old driver did? committers: Well, no, but that's coming. public: And what do I do in the meantime? committers: Stop whining. On Friday, 10 December 1999 at 21:57:17 -0800, Mike Smith wrote: >> On Friday, 10th December 1999, Mike Smith wrote: >> >>> Fortunately, the CAM folks persisted despite the criticism, and I'm glad >>> to see that Soren is taking the same stance. >> >> Not everything improved with CAM. Personally I'm only receiving the >> benifits of CAM now, about a year after it replaced the old system. >> On the balance it has been good for FreeBSD, but you have to remember >> that there will be small pockets of users that will get the short end >> of the stick. How the project deals with the losers in these deals is >> important for its long term health. > > It's more how the losers deal with the project, to be honest. There has > to be a way to make them realise that it's not reasonable to expect > everyone else to live in pain just because they (think they) are still > comfortable. OK, now explain how that statement relates to the matter at hand. Who is going to be in pain if the "losers" get their way? Who if not? Your whole attitude shows a surprisingly one-sided view of things. There are people out there who are going to suffer because of short-term decisions which aren't really necessary right now. Amongst others, they're the people who are paying your salary. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 15: 2:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext03.compaq.com (mailext03.compaq.com [207.18.199.41]) by hub.freebsd.org (Postfix) with ESMTP id 7833315440 for ; Mon, 13 Dec 1999 15:02:17 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: by mailext03.compaq.com (Postfix, from userid 12345) id 24D7C151FB5; Mon, 13 Dec 1999 17:02:17 -0600 (CST) Received: from mailint01.im.hou.compaq.com (mailint01.compaq.com [207.18.199.34]) by mailext03.compaq.com (Postfix) with ESMTP id 1BAD914850C; Mon, 13 Dec 1999 17:02:17 -0600 (CST) Received: by mailint01.im.hou.compaq.com (Postfix, from userid 12345) id B20A3825C3; Mon, 13 Dec 1999 17:02:09 -0600 (CST) Received: from mojave.worldwide.lemis.com (unknown [155.186.83.42]) by mailint01.im.hou.compaq.com (Postfix) with ESMTP id 321CB78B42; Mon, 13 Dec 1999 17:02:09 -0600 (CST) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id MAA00974; Sat, 11 Dec 1999 12:43:44 -0600 (CST) (envelope-from grog) Date: Sat, 11 Dec 1999 12:43:44 -0600 From: Greg Lehey To: Stephen McKay Cc: "Kenneth D. Merry" , freebsd-current@FreeBSD.ORG, Brad Knowles Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991211124343.I760@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <199912102344.QAA53269@panzer.kdm.org> <199912110239.MAA01680@nymph.detir.qld.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912110239.MAA01680@nymph.detir.qld.gov.au>; from syssgm@detir.qld.gov.au on Sat, Dec 11, 1999 at 12:39:15PM +1000 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Saturday, 11 December 1999 at 12:39:15 +1000, Stephen McKay wrote: > > But that shouldn't stop us from moving forward with the ata driver. I > think that a small slowing of the pace, and a bit more understanding toward > those with unusual hardware will help. And I support PHK's hard line > stance (except for the rushed pace) toward making the kernel break for > users of wd. It has to be so, or no one will move. The wd code will > still be in the CVS tree for desperate people to revive to use, and to > port the missing bits into the ata driver. The kind of people I'm talking about are end users. They wouldn't know how to extract the driver from the CVS tree and build it. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 15: 2:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext03.compaq.com (mailext03.compaq.com [207.18.199.41]) by hub.freebsd.org (Postfix) with ESMTP id 0D2FD15226 for ; Mon, 13 Dec 1999 15:02:14 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: by mailext03.compaq.com (Postfix, from userid 12345) id C0F7D151FB0; Mon, 13 Dec 1999 17:02:13 -0600 (CST) Received: from mailint01.im.hou.compaq.com (mailint01.compaq.com [207.18.199.34]) by mailext03.compaq.com (Postfix) with ESMTP id B885514850C; Mon, 13 Dec 1999 17:02:13 -0600 (CST) Received: by mailint01.im.hou.compaq.com (Postfix, from userid 12345) id 56EAF825EA; Mon, 13 Dec 1999 17:02:06 -0600 (CST) Received: from mojave.worldwide.lemis.com (unknown [155.186.83.42]) by mailint01.im.hou.compaq.com (Postfix) with ESMTP id C86A678B42; Mon, 13 Dec 1999 17:02:05 -0600 (CST) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id MAA01030; Sat, 11 Dec 1999 12:55:37 -0600 (CST) (envelope-from grog) Date: Sat, 11 Dec 1999 12:55:36 -0600 From: Greg Lehey To: Peter Wemm Cc: Poul-Henning Kamp , Nate Williams , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991211125536.L760@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <19991210180948.7359C1CA0@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991210180948.7359C1CA0@overcee.netplex.com.au>; from peter@netplex.com.au on Sat, Dec 11, 1999 at 02:09:48AM +0800 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Saturday, 11 December 1999 at 2:09:48 +0800, Peter Wemm wrote: > Poul-Henning Kamp wrote: >> In message <199912101752.KAA19725@mt.sri.com>, Nate Williams writes: >>>> In a few days time the wd driver will be retired from FreeBSDs >>>> i386 architecture. >>> >>> Given that the ATA driver just went active a few minutes ago, I think a >>> period of shakeout time would be called for. I think that time should >>> be longer than a few days, and should be in 4.0, and then retired in >>> 4.1. >> >> The ata driver has been available for you and other to test for a long >> time. 4.0-REL is still some time away, so if you are quick you can >> still give it a good shakeout and have any bugs you find fixed before >> 4.0-RELEASE. > > Also, I'd like to reiterate something again.. Not running as fast as > possible is *not* a showstopper. If a device runs in generic PIO or WDMA > mode instead of udma mode, it's *not* the end of the earth. People in that > scenario won't be stranded. I think a 90% performance hit is a bug in most people's books. From what I've seen, that's a conservative estimate. > What is a killer is if a large number of people on popular hardware > can't even boot, *at all*, in no, way, shape or form. Only that. > The only way to find that out for sure before 4.0 is to push the > issue *now*. Agreed. I'm not saying "don't make it the default", I'm saying "leave an escape path". Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 15: 2:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext02.compaq.com (mailext02.compaq.com [207.18.199.33]) by hub.freebsd.org (Postfix) with ESMTP id B957A1515B for ; Mon, 13 Dec 1999 15:02:14 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: by mailext02.compaq.com (Postfix, from userid 12345) id 367819A82F; Mon, 13 Dec 1999 17:02:14 -0600 (CST) Received: from mailint01.im.hou.compaq.com (mailint01.compaq.com [207.18.199.34]) by mailext02.compaq.com (Postfix) with ESMTP id 1DE3890D82; Mon, 13 Dec 1999 17:02:14 -0600 (CST) Received: by mailint01.im.hou.compaq.com (Postfix, from userid 12345) id 0A596825EA; Mon, 13 Dec 1999 17:02:07 -0600 (CST) Received: from mojave.worldwide.lemis.com (unknown [155.186.83.42]) by mailint01.im.hou.compaq.com (Postfix) with ESMTP id 8BF5178B44; Mon, 13 Dec 1999 17:02:06 -0600 (CST) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id NAA01079; Sat, 11 Dec 1999 13:06:56 -0600 (CST) (envelope-from grog) Date: Sat, 11 Dec 1999 13:06:56 -0600 From: Greg Lehey To: Poul-Henning Kamp Cc: Kris Kennaway , Luoqi Chen , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991211130656.O760@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <7881.944870115@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <7881.944870115@critter.freebsd.dk>; from phk@critter.freebsd.dk on Sat, Dec 11, 1999 at 12:55:15AM +0100 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Saturday, 11 December 1999 at 0:55:15 +0100, Poul-Henning Kamp wrote: > In message , Kris Ken > naway writes: > >> No-one (as far as I can see) is objecting to making ata the default (which >> it already is), and to kill wd in some number of weeks. Why can't you just >> do that, and put and end to this discussion happily? Will a few weeks >> really harm the development process? > > You overlook one simple thing here: If we want the ata driver > tested, we need to make existing kernel configs break, otherwise > people will not change them to use ata. We know this from bitter > experience. OK, so rename the wd driver to owd. Make it necessary to change the config in any way. Print out dire warnings on every boot and every config(8). > The removal of wd has many discrete steps, but the first one is to > make it clear to people that it is going away, this has been done > by now I belive. I think it has settled in, yes. > The next thing is to break all the kernel configs, this has yet to > happen, but it will happen real soon. This means that you have to > really insist badly to make the wd driver work for you. OK, as long as we have an alternative, such as I suggest above. > Once we have established that the new driver doesn't leave a large > number of people stranded it will be killed for good. The new driver? That's counterproductive :-) I'd like to see a definition of "large number". > What we need right NOW is for people to test the ata driver, and if > it doesn't work, to debug as well as they can and report in > excrutiating detail to sos so that he has a chance to analyze the > problems. Just saying "It doesn't work for me" will simply not do. > The more senior the person reporting, the more detail and quality > information should be able to expect. You're talking about different people here. Understand that the users of -CURRENT are numbered in the hundreds; the users of -RELEASE are numbered in the hundreds of thousands. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 15: 2:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext12.compaq.com (mailext12.compaq.com [207.18.199.188]) by hub.freebsd.org (Postfix) with ESMTP id 6E92715350; Mon, 13 Dec 1999 15:02:16 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: by mailext12.compaq.com (Postfix, from userid 12345) id D93D85795D; Mon, 13 Dec 1999 17:02:15 -0600 (CST) Received: from mailint01.im.hou.compaq.com (mailint01.compaq.com [207.18.199.34]) by mailext12.compaq.com (Postfix) with ESMTP id D45B854602; Mon, 13 Dec 1999 17:02:15 -0600 (CST) Received: by mailint01.im.hou.compaq.com (Postfix, from userid 12345) id CAFDD825EA; Mon, 13 Dec 1999 17:02:08 -0600 (CST) Received: from mojave.worldwide.lemis.com (unknown [155.186.83.42]) by mailint01.im.hou.compaq.com (Postfix) with ESMTP id 6C1E778B43; Mon, 13 Dec 1999 17:02:08 -0600 (CST) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id MAA00926; Sat, 11 Dec 1999 12:34:52 -0600 (CST) (envelope-from grog) Date: Sat, 11 Dec 1999 12:34:52 -0600 From: Greg Lehey To: Mike Smith Cc: Nate Williams , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991211123452.F760@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <199912102123.OAA21691@mt.sri.com> <199912110154.RAA04860@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912110154.RAA04860@mass.cdrom.com>; from msmith@FreeBSD.ORG on Fri, Dec 10, 1999 at 05:54:14PM -0800 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Friday, 10 December 1999 at 17:54:14 -0800, Mike Smith wrote: >>> If half as much energy was spent adding the missing bits of functionality >>> to the new systems as people have been spending complaining it then we'd be >>> there ages ago. >> >> Not true. It doesn't take a disk expert to complain about a policy, but >> it takes one to fix bugs/add features to the existing driver. :) :) :) > > That's ignoring the fact that it takes less energy to become enough of a > "disk expert" to do something useful than it takes to engage in the sort > of protracted whining that we're seeing. Using derogatory terminology doesn't alter the facts, it just alters people's view of you. We're not talking "whining" here, we're talking policy. And the policy has good, solid reasoning behind it, something we've seen precious little of in favour of immediately axing the wd driver. > It does take more foresight and commitment to actually doing > something though, and given the popularity of graffiti and mindless > vandalism these days perhaps that's just par for the course. By "graffiti and vandalism", are you referring to the Danish Axes? I wouldn't call that graffiti, and the Vandals are only distantly related to the Danes :-) Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 15: 3: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext12.compaq.com (mailext12.compaq.com [207.18.199.188]) by hub.freebsd.org (Postfix) with ESMTP id AEE2315514 for ; Mon, 13 Dec 1999 15:02:27 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: by mailext12.compaq.com (Postfix, from userid 12345) id A117057953; Mon, 13 Dec 1999 17:02:26 -0600 (CST) Received: from mailint01.im.hou.compaq.com (mailint01.compaq.com [207.18.199.34]) by mailext12.compaq.com (Postfix) with ESMTP id 99C3854602; Mon, 13 Dec 1999 17:02:26 -0600 (CST) Received: by mailint01.im.hou.compaq.com (Postfix, from userid 12345) id 91407825EB; Mon, 13 Dec 1999 17:02:19 -0600 (CST) Received: from mojave.worldwide.lemis.com (unknown [155.186.83.42]) by mailint01.im.hou.compaq.com (Postfix) with ESMTP id EB22A78B42; Mon, 13 Dec 1999 17:02:18 -0600 (CST) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id MAA00939; Sat, 11 Dec 1999 12:36:34 -0600 (CST) (envelope-from grog) Date: Sat, 11 Dec 1999 12:36:33 -0600 From: Greg Lehey To: Poul-Henning Kamp Cc: Soren Schmidt , Blaz Zupan , Christopher Masto , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991211123633.G760@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <19991209225405.E866@mojave.sitaranetworks.com> <5386.944842313@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <5386.944842313@critter.freebsd.dk>; from phk@critter.freebsd.dk on Fri, Dec 10, 1999 at 05:11:53PM +0100 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Friday, 10 December 1999 at 17:11:53 +0100, Poul-Henning Kamp wrote: > In message <19991209225405.E866@mojave.sitaranetworks.com>, Greg Lehey writes: > >> We're getting off track again: the real issue is that you shouldn't >> completely replace old drivers with new, better written, less buggy >> drivers which have significantly less than the full functionality of >> the old driver. > > And while that attitude might work for an organization where some > PHB type can dictate what people should or shouldn't do, experience > has taught us that at some point you draw a line in the sand and > force people to concentrate on the path forward. Experience has also taught us that people draw the lines in different places. I haven't seen enough consideration of the end user in all this discussion. > Look at the sound code to see why your proposal doesn't work in our > reality. You're going to have to help me here. I hadn't used the sound code up to a couple of months ago. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 15: 3: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext12.compaq.com (mailext12.compaq.com [207.18.199.188]) by hub.freebsd.org (Postfix) with ESMTP id 305BC1539B; Mon, 13 Dec 1999 15:02:13 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: by mailext12.compaq.com (Postfix, from userid 12345) id AD4B757838; Mon, 13 Dec 1999 17:02:12 -0600 (CST) Received: from mailint01.im.hou.compaq.com (mailint01.compaq.com [207.18.199.34]) by mailext12.compaq.com (Postfix) with ESMTP id A5F8854602; Mon, 13 Dec 1999 17:02:12 -0600 (CST) Received: by mailint01.im.hou.compaq.com (Postfix, from userid 12345) id 9E88E825C3; Mon, 13 Dec 1999 17:02:05 -0600 (CST) Received: from mojave.worldwide.lemis.com (unknown [155.186.83.42]) by mailint01.im.hou.compaq.com (Postfix) with ESMTP id 0F96E78B42; Mon, 13 Dec 1999 17:02:05 -0600 (CST) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id NAA01066; Sat, 11 Dec 1999 13:03:39 -0600 (CST) (envelope-from grog) Date: Sat, 11 Dec 1999 13:03:39 -0600 From: Greg Lehey To: Mike Smith Cc: Greg Childers , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991211130339.N760@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <4.2.0.58.19991210180808.00945190@pop.uky.edu> <199912110732.XAA01032@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912110732.XAA01032@mass.cdrom.com>; from msmith@FreeBSD.ORG on Fri, Dec 10, 1999 at 11:32:27PM -0800 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Friday, 10 December 1999 at 23:32:27 -0800, Mike Smith wrote: > [missing attribution to Greg Childers ] >> Except that ATA currently does not work on my system. So I assume I'm not >> the only one. > > Actually, to quote from your original message: > >> According to technical product summary, the primary IDE interface, on >> which both my drives reside, is a PCTech RZ1000 on the PCI local bus. > > Nobody in their right mind uses the RZ1000 chipset for IDE. It's one of > the classic "broken" parts (along with several of the CMD64x family) that > you just don't use. > > You're probably not the only one out there with one of these controllers, > but there aren't anywhere near that many of them still circulating after > the massive problems that were encountered with that part _many_ years > ago. OK, and I think I can agree that we don't need to carry support for this chip over into ata. But what does Greg do? He has this hardware. He can do one of four things: 1. Throw it away and get something better. 2. Carry on running 3.X forever. 3. Get pissed off with FreeBSD and go elsewhere. 4. Use the wd driver which has been left in 4.x for exactly this kind of problem. Why make life difficult for him? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 15: 4:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext03.compaq.com (mailext03.compaq.com [207.18.199.41]) by hub.freebsd.org (Postfix) with ESMTP id 0282D1536A; Mon, 13 Dec 1999 15:04:16 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: by mailext03.compaq.com (Postfix, from userid 12345) id DE322152075; Mon, 13 Dec 1999 17:04:15 -0600 (CST) Received: from mailint01.im.hou.compaq.com (mailint01.compaq.com [207.18.199.34]) by mailext03.compaq.com (Postfix) with ESMTP id D378214850C; Mon, 13 Dec 1999 17:04:15 -0600 (CST) Received: by mailint01.im.hou.compaq.com (Postfix, from userid 12345) id D8A6B825C3; Mon, 13 Dec 1999 17:04:08 -0600 (CST) Received: from mojave.worldwide.lemis.com (unknown [155.186.83.42]) by mailint01.im.hou.compaq.com (Postfix) with ESMTP id 151BF78B42; Mon, 13 Dec 1999 17:04:08 -0600 (CST) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id MAA00953; Sat, 11 Dec 1999 12:39:35 -0600 (CST) (envelope-from grog) Date: Sat, 11 Dec 1999 12:39:35 -0600 From: Greg Lehey To: Poul-Henning Kamp Cc: Nate Williams , Mike Smith , Christopher Masto , Julian Elischer , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991211123935.H760@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <199912101757.KAA19772@mt.sri.com> <6152.944849073@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <6152.944849073@critter.freebsd.dk>; from phk@critter.freebsd.dk on Fri, Dec 10, 1999 at 07:04:33PM +0100 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Friday, 10 December 1999 at 19:04:33 +0100, Poul-Henning Kamp wrote: > In message <199912101757.KAA19772@mt.sri.com>, Nate Williams writes: >>> What we need here is a commitment to these new initiatives, not a lot of >>> fence-sitting and clutching our knitting to our chests. >> >> If all our users were developers I would agree. But *most* of our users >> are not developers. > > -CURRENT should have very few users who are not developers in some > capacity. Agreed. As I said earlier in the thread, the problem is that we're 5 weeks from releasing this code as 4.0-RELEASE. I think we might be able to compromise here: issue 4.0 with a disclaimer saying "AFAWK Cyrix DMA support is broken. If you have a Cyrix [IDE] chip, use 3.[45]-RELEASE instead.". >> Good question. What are we trying to achieve here? I thought it was to >> provide the best OS that is usable to the largest number of users? > > And this requires us to move away the old cruft so we force the > people on the bleeding edge to test the new stuff. > > All in all, it sounds to me like a lot of people are presenting > a stance which can be summarized as: > > "why should *I* have to be guinea-pig for the ata driver > in -current make somebody else test it first." I haven't noticed anybody doing that. It's certainly not my concern; as soon as I get home I'm going to try out the 5591 code and make sure it works correctly. > To which the answer is: If you decide to run -current you have > tacitly agreed to be a guinea-pig for FreeBSD developers, so > shut up and test. To which the answer is what I said above: today's -CURRENT is next month's -RELEASE. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 15: 4:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext02.compaq.com (mailext02.compaq.com [207.18.199.33]) by hub.freebsd.org (Postfix) with ESMTP id 4004815407; Mon, 13 Dec 1999 15:04:18 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: by mailext02.compaq.com (Postfix, from userid 12345) id 8157C9A82F; Mon, 13 Dec 1999 17:04:17 -0600 (CST) Received: from mailint01.im.hou.compaq.com (mailint01.compaq.com [207.18.199.34]) by mailext02.compaq.com (Postfix) with ESMTP id 71A6590D82; Mon, 13 Dec 1999 17:04:17 -0600 (CST) Received: by mailint01.im.hou.compaq.com (Postfix, from userid 12345) id 69145825CA; Mon, 13 Dec 1999 17:04:10 -0600 (CST) Received: from mojave.worldwide.lemis.com (unknown [155.186.83.42]) by mailint01.im.hou.compaq.com (Postfix) with ESMTP id D8F5E78B42; Mon, 13 Dec 1999 17:04:09 -0600 (CST) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id MAA00899; Sat, 11 Dec 1999 12:29:29 -0600 (CST) (envelope-from grog) Date: Sat, 11 Dec 1999 12:29:29 -0600 From: Greg Lehey To: Peter Wemm Cc: Jeroen Ruigrok/Asmodai , Brad Knowles , Mike Smith , Julian Elischer , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991211122928.D760@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <19991210160247.DF62D1CA0@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991210160247.DF62D1CA0@overcee.netplex.com.au>; from peter@netplex.com.au on Sat, Dec 11, 1999 at 12:02:47AM +0800 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Saturday, 11 December 1999 at 0:02:47 +0800, Peter Wemm wrote: > Jeroen Ruigrok/Asmodai wrote: >> -On [19991209 16:03], Greg Lehey (grog@mojave.sitaranetworks.com) wrote: >>> On Wednesday, 8 December 1999 at 20:23:24 +0100, Brad Knowles wrote: >>>> >>>> This is -CURRENT. It pains me to say it, but anyone trying to >>>> run anything "useful" on -CURRENT gets what they deserve. This is >>>> the only place where we can make clean breaks with the past, and as >>>> painful as that can be, we simply have to do that occasionally. >>> >>> Next month it'll be -RELEASE. This isn't the time to remove such >>> significant functionality. If it weren't for that, I'd agree with >>> you. >> >> Think about that some more. >> >> After that it will be 4.1. Nice to give people a driver and then rip it >> out when 4.1 comes when Soren fixes the last of the things people >> needed to have into the ata driver. >> >> I was already testing the ata driver and even procured some more info >> for Soren than he already had. Same goes for a bunch of other people. >> But the opposite goes for a lot of people. >> >> People running CURRENT to be cutting edge as in being elite with the >> latest FreeBSD thus get bitten. >> >> I'd say, cut loose the wd driver. (VoxWare removed would be cool too.) > > If half as much energy was spent adding the missing bits of functionality > to the new systems as people have been spending complaining it then we'd be > there ages ago. Trying desperately to prolong the agony by keeping the old > stuff on life support is counter productive. There's more than energy involved. We need the hardware. > Damn it people! If you want cyrix busmaster support, then the code > is there, it's not all that hard to extract and adapt the cyrix code > to ata. If you have got cyrix hardware and can test your work, then > even better. Who are you talking to? The relatively non-technical people who buy the CDs because they know that FreeBSD is a reliable, no-problems operating system. Then they discover that functionality they had is gone again. Send that to /. and smoke it. Like it or not, we have a reputation to maintain. We have to live up to expectations. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 15: 4:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext04.compaq.com (mailext04.compaq.com [207.18.199.42]) by hub.freebsd.org (Postfix) with ESMTP id 87BAF158A2; Mon, 13 Dec 1999 15:04:30 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: by mailext04.compaq.com (Postfix, from userid 12345) id 3B954104B8C; Mon, 13 Dec 1999 17:04:27 -0600 (CST) Received: from mailint01.im.hou.compaq.com (mailint01.compaq.com [207.18.199.34]) by mailext04.compaq.com (Postfix) with ESMTP id 21F42FB101; Mon, 13 Dec 1999 17:04:27 -0600 (CST) Received: by mailint01.im.hou.compaq.com (Postfix, from userid 12345) id 165A5825CC; Mon, 13 Dec 1999 17:04:20 -0600 (CST) Received: from mojave.worldwide.lemis.com (unknown [155.186.83.42]) by mailint01.im.hou.compaq.com (Postfix) with ESMTP id 61E5F78B42; Mon, 13 Dec 1999 17:04:19 -0600 (CST) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id MAA00916; Sat, 11 Dec 1999 12:32:09 -0600 (CST) (envelope-from grog) Date: Sat, 11 Dec 1999 12:32:09 -0600 From: Greg Lehey To: Soren Schmidt Cc: Nate Williams , Peter Wemm , Jeroen Ruigrok/Asmodai , Brad Knowles , Mike Smith , Julian Elischer , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991211123208.E760@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <199912102123.OAA21691@mt.sri.com> <199912102144.WAA27469@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912102144.WAA27469@freebsd.dk>; from sos@freebsd.dk on Fri, Dec 10, 1999 at 10:44:36PM +0100 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Friday, 10 December 1999 at 22:44:36 +0100, Soren Schmidt wrote: > It seems Nate Williams wrote: >>> If half as much energy was spent adding the missing bits of functionality >>> to the new systems as people have been spending complaining it then we'd be >>> there ages ago. >> >> Not true. It doesn't take a disk expert to complain about a policy, but >> it takes one to fix bugs/add features to the existing driver. :) :) :) > > Yeah, and some of them is spending valueable time going thru all this > garbage in their mailbox instead of doing something usefull. > > Excuse me for not taking part in this, but I _really_ think I can use > my time for better things... Sure, this thread has gone on far too long. Let's agree to the principle of leaving drivers in the system, disabled, until their replacements can do everything that they can. It looks like ata is nearly there, but what about those Cyrix users? Who has a Cyrix chip? Until we find somebody with hardware, inclination and ability, it's going to be difficult to replace the wd driver. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 15:18:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 10226153F2 for ; Mon, 13 Dec 1999 15:18:28 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 370881C4A; Mon, 13 Dec 1999 18:18:14 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 33855381B; Mon, 13 Dec 1999 18:18:14 -0500 (EST) Date: Mon, 13 Dec 1999 18:18:14 -0500 (EST) From: Bill Fumerola Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: vinum start needs block device In-Reply-To: <19991212154736.8295D1CA0@overcee.netplex.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 Sun, 12 Dec 1999, Peter Wemm wrote: > > - if (drive->vp->v_type != VBLK) { /* only consider bl > ock devices */ > > + if (!vn_isdisk(drive->vp)) { /* only consider bl Note: this fixes some recent problems (Hi Greg!) that I've been having. I'm now a happy puppy once again. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 15:32:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from kbtfw.kubota.co.jp (kbtfw.kubota.co.jp [133.253.102.202]) by hub.freebsd.org (Postfix) with ESMTP id 22B5E14A24 for ; Mon, 13 Dec 1999 15:32:10 -0800 (PST) (envelope-from haro@tk.kubota.co.jp) Received: by kbtfw.kubota.co.jp; id IAA19849; Tue, 14 Dec 1999 08:32:01 +0900 (JST) Received: from unknown(133.253.31.1) by kbtfw.kubota.co.jp via smap (V4.2) id xma019755; Tue, 14 Dec 99 08:31:36 +0900 Received: (from uucp@localhost) by lemond.gkn.kubota.co.jp (8.9.3+3.2W/3.7W99070916) with UUCP id IAA11949; Tue, 14 Dec 1999 08:31:34 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by jkpc15.tk.kubota.co.jp (8.9.3/3.7W-uucp) with ESMTP id IAA00478; Tue, 14 Dec 1999 08:26:13 +0900 (JST) To: sos@freebsd.dk Cc: freebsd-current@FreeBSD.ORG Subject: Re: ATA weird message? In-Reply-To: Your message of "Mon, 13 Dec 1999 08:33:43 +0100 (CET)" <199912130733.IAA26820@freebsd.dk> References: <199912130733.IAA26820@freebsd.dk> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-Id: <19991214082613G.haro@tk.kubota.co.jp> Date: Tue, 14 Dec 1999 08:26:13 +0900 From: haro@tk.kubota.co.jp (Munehiro Matsuda) X-Dispatcher: imput version 980905(IM100) Lines: 56 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Soren Schmidt Date: Mon, 13 Dec 1999 08:33:43 +0100 (CET) ::It seems Munehiro Matsuda wrote: ::> Hi all, ::> = ::> I am using -current as of December 9 (CTM:src-cur.4130.gz), and ::> got following weird ATA related messages while 'make -j4 buildworld'= .= ::> I never had this kind of message when using wd drivers. ::> = ::> ata0-master: ad_timeout: lost disk contact - resetting ::> ata0: resetting devices .. done :: ::Hmm, maybe the timeout in ata-disk.c is too short, try increasing ::the 5*hz to say 10*hz in line 436, and see if that changes anything.. :: ::-S=F8ren :: I tried that, but didn't seem to help much. I run 'make -j4 buildworld' twice, just in case, and got the same warning the first round, but didn't on the second. One thing I noticed is that, the first warning occurs on a idle disk, not the one running 'buildworld'! = FYI, my system configuration: ata0 -- master: ad0s1 (Win95), ad0s2* (-STABLE) slave: none ata1 -- master: ad2s1 (DOS), ad2s2* (-CURRENT) slave: none I was running 'buidworld' on -CURRENT (ad2s2), at that time -STABLE and Win95 partitions where mounted, but basically idle. = IIRC, buildworld was working on lib/libc when the warning occurred. = So, it may be that, system was too busy talking to that running disk with loads of small-file transfers, and timed its-self out on the other?= Thank you, Haro =3D---------------------------------------------------------------------= --------- _ _ Munehiro (haro) Matsuda -|- /_\ |_|_| Office of Business Planning & Developement, Kubota Cor= p. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103, Japan Tel: +81-3-3245-3318 Fax: +81-3-32454-3315 Email: haro@kubota.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 15:40:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 50C681515B; Mon, 13 Dec 1999 15:40:41 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 36B341CA0; Tue, 14 Dec 1999 07:40:37 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Greg Lehey Cc: Mike Smith , Greg Childers , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: Message from Greg Lehey of "Sat, 11 Dec 1999 13:03:39 CST." <19991211130339.N760@mojave.worldwide.lemis.com> Date: Tue, 14 Dec 1999 07:40:37 +0800 From: Peter Wemm Message-Id: <19991213234037.36B341CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > On Friday, 10 December 1999 at 23:32:27 -0800, Mike Smith wrote: > > [missing attribution to Greg Childers ] > >> Except that ATA currently does not work on my system. So I assume I'm not > >> the only one. > > > > Actually, to quote from your original message: > > > >> According to technical product summary, the primary IDE interface, on > >> which both my drives reside, is a PCTech RZ1000 on the PCI local bus. > > > > Nobody in their right mind uses the RZ1000 chipset for IDE. It's one of > > the classic "broken" parts (along with several of the CMD64x family) that > > you just don't use. > > > > You're probably not the only one out there with one of these controllers, > > but there aren't anywhere near that many of them still circulating after > > the massive problems that were encountered with that part _many_ years > > ago. > > OK, and I think I can agree that we don't need to carry support for > this chip over into ata. > > But what does Greg do? He has this hardware. He can do one of four > things: > > 1. Throw it away and get something better. > 2. Carry on running 3.X forever. > 3. Get pissed off with FreeBSD and go elsewhere. > 4. Use the wd driver which has been left in 4.x for exactly this kind > of problem. > > Why make life difficult for him? The RZ1000 is *dangerous*! We are doing no favours by making it run.. :-/ IMHO It is better to loose the user by not playing ball than to corrupt their data or run unreliably and make them hate us for it. http://www.faqs.org/faqs/pc-hardware-faq/enhanced-IDE/part1/ ==== 3.3. Are those rumors about buggy interfaces true? Very true, unfortunately. This FAQ doesn't really deal with specific interfaces, but two very popular interface chips have been shown to contain bugs too serious to ignore: o the CMD640x, a dual-channel PCI to EIDE interface used on many mainboards (Intel!) and interface boards, has a number of dangerous bugs you need to be aware of. o The PC-Tech RZ-1000, used on AT&T, Dell, Gateway and Intel boards, also has two data-corrupting bugs. See also . In both cases, the corruption occurs only in specific software environments and is very subtle; you can go on working for months without suspecting anything more than buggy software. The damage can be immense. For all the details, look at Roedy Green's (roedy@bix.com) "PCI EIDE controller flaws" FAQ included with his EIDE test program which will test your system for the bugs. BE WARNED that you're playing Russian roulette with your data if you continue working on an affected machine without taking notice of this problem. ==== Have a look at the intel information. It explains about having to mask interrupts during a data transfer, and how dangerous mixing floppy and IDE access is with that chip. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 15:47:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 6347915153 for ; Mon, 13 Dec 1999 15:47:11 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40325>; Tue, 14 Dec 1999 10:38:43 +1100 Content-return: prohibited Date: Tue, 14 Dec 1999 10:46:52 +1100 From: Peter Jeremy Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: <19991211125412.K760@mojave.worldwide.lemis.com>; from grog@lemis.com on Sun, Dec 12, 1999 at 05:54:12AM +1100 To: current@FreeBSD.ORG Message-Id: <99Dec14.103843est.40325@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <199912101752.KAA19725@mt.sri.com> <6120.944848909@critter.freebsd.dk> <19991211125412.K760@mojave.worldwide.lemis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Dec-12 05:54:12 +1100, Greg Lehey wrote: >On Friday, 10 December 1999 at 19:01:49 +0100, Poul-Henning Kamp wrote: >> The ata driver has been available for you and other to test for a long >> time. > >Oh. Somehow I missed this. Sure, I saw commits, but I can't recall a >"HEADS UP: ata is good enough for general testing now". If I had done >so, I might have changed months ago, and a lot of this principle >discussion would be deferred to the next night of the long axes. I don't recall anything like this either. I _do_ remember all the commit messages stating 'this driver can hose your disk real bad' which tended to disuade me from experimenting in the early days. (None of my systems are `scratch boxes' to the extent that I can afford for the disk contents to be scrambled regularly). Checking back though the commit logs, the last commit that explicitly included the 'As usual USE AT YOUR OWN RISK!!, this is still alpha level code' comment was on 21st September. There's nothing in the logs explicitly stating that the code is now `beta', `pre-production' or `production' quality. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 16:53:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.49]) by hub.freebsd.org (Postfix) with ESMTP id 9AE5A14BC2 for ; Mon, 13 Dec 1999 16:53:02 -0800 (PST) (envelope-from niels@bakker.net) Received: from liquid.tpb.net (arctic.xs4all.nl [194.109.37.82]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id BAA06032 for ; Tue, 14 Dec 1999 01:52:58 +0100 (CET) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.3/8.9.3/Debian/GNU) with ESMTP id BAA30498 for ; Tue, 14 Dec 1999 01:52:58 +0100 Date: Tue, 14 Dec 1999 01:52:57 +0100 (CET) From: N X-Sender: niels@liquid.tpb.net To: current@FreeBSD.ORG Subject: Re: Anybody actually using gigabit ethernet? In-Reply-To: <199905111712.NAA25750@khavrinen.lcs.mit.edu> Message-ID: <9912140149130.30300-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Garrett Wollman wrote on 11 May 1999: [Netgear GigE PCI interface] > I'm buying one of these cards today ($319.99 from NECX) and will stick > it into a machine here on our new Gigabit backbone. I'm particularly > interested to test out the VLAN support, since my Secret Plan is to > have this one machine serve as the DHCP server for the whole Lab (17 > subnets). Did this work out? I'm secretly planning something similar :-) and noted this afternoon that a kernel with `pseudo-device vlan 4' in its config file doesn't compile: cc -c -O -m486 -pipe -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf ../../net/if_vlan.c ../../net/if_vlan.c: In function `vlan_ioctl': ../../net/if_vlan.c:517: structure has no member named `if_flags' *** Error code 1 (This is RELENG_3, f'ups to freebsd-stable@freebsd.org are more appropriate I guess... please feel free; since the original thread happened on -current I'm posting it there.) TIA, -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 17: 1:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D0D5615252 for ; Mon, 13 Dec 1999 17:01:37 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id UAA09905; Mon, 13 Dec 1999 20:01:30 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id UAA06129; Mon, 13 Dec 1999 20:00:59 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 13 Dec 1999 20:00:58 -0500 (EST) To: Soren Schmidt Cc: joeo@nks.net, freebsd-current@FreeBSD.ORG Subject: Re: Errors from the ata disk driver In-Reply-To: <14421.18254.748286.640261@grasshopper.cs.duke.edu> References: <14418.39524.290684.380673@grasshopper.cs.duke.edu> <199912130801.JAA33383@freebsd.dk> <14421.18254.748286.640261@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14421.37871.442695.788714@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Gallatin writes: > > Soren Schmidt writes: > > I've fixed it here (I hope), and it will be in the next batch of fixes. > > I hope to get through my mailbox today :) > > Thanks. I'm running a kernel built with them now. If/when we see CRC > errors, I'll let you know what happens. We don't see them frequently > (a few times a month), so it might be a while. Looks like the world is safe for Promise Ultra users: Dec 13 18:42:37 waffle /kernel.test: ad2: UDMA CRC READ ERROR blk #22057647 retrying Dec 13 18:49:21 waffle xntpd[122]: time reset (step) 0.389151 s Dec 13 19:11:45 waffle xntpd[122]: time reset (step) 0.381460 s Dec 13 19:35:13 waffle xntpd[122]: time reset (step) 0.459194 s Dec 13 19:40:47 waffle /kernel.test: ad4: UDMA CRC READ ERROR blk #16658928 retrying Thanks! Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 17: 9:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from daemon.best.ca (cr262311-a.lngly1.bc.wave.home.com [24.113.173.186]) by hub.freebsd.org (Postfix) with ESMTP id DF885151C6; Mon, 13 Dec 1999 17:09:11 -0800 (PST) (envelope-from riso@best.ca) Received: by daemon.best.ca (Postfix, from userid 1000) id E386AD7211; Mon, 13 Dec 1999 17:09:08 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by daemon.best.ca (Postfix) with ESMTP id C9DE1C989F; Mon, 13 Dec 1999 17:09:08 -0800 (PST) Date: Mon, 13 Dec 1999 17:09:08 -0800 (PST) From: Richard Furda To: FreeBSD-stable@freebsd.org Cc: FreeBSD-current@freebsd.org Subject: QIC 40/80 floppy tape drive controller 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 Hello, I have a QIC 40/80 clone floppy tape drive controller (running 3.3-stable) and wondering if anyone is working/thinking about porting the ft driver to 3.X/4.X branch. I understand the driver was "removed" in 2.2.8 due to incompatibility issues. I'd like to help out, thus give access to a machine with the QIC 40/80 floppy tape controller. Thanks, Rich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 17:27:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from web2101.mail.yahoo.com (web2101.mail.yahoo.com [128.11.68.245]) by hub.freebsd.org (Postfix) with SMTP id 3DB9D1502C for ; Mon, 13 Dec 1999 17:27:52 -0800 (PST) (envelope-from valsho@yahoo.com) Received: (qmail 16574 invoked by uid 60001); 14 Dec 1999 01:27:49 -0000 Message-ID: <19991214012749.16573.qmail@web2101.mail.yahoo.com> Received: from [147.226.112.101] by web2101.mail.yahoo.com; Mon, 13 Dec 1999 17:27:49 PST Date: Mon, 13 Dec 1999 17:27:49 -0800 (PST) From: "Valentin S. Chopov" Subject: 4.0-CURRENT boot kernel, ATA_16BIT_ONLY , etc. To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The latest 4.0-CURRENT boot floppies are not working on old ISA boards with 16-bit data transfer only, and the installation of FreeBSD becomes impossible:( . It seems that in this case ATA_16BIT_ONLY is not enough - may be flags to ata0 controller or auto-detection as Soren promised will be O.K.?! Thanks, Val __________________________________________________ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one place. Yahoo! Shopping: http://shopping.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 18: 6: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 0CCBC152D9 for ; Mon, 13 Dec 1999 18:05:55 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id DAA11873 for freebsd-current@freebsd.org; Tue, 14 Dec 1999 03:05:51 +0100 (CET) (envelope-from olli) Date: Tue, 14 Dec 1999 03:05:51 +0100 (CET) From: Oliver Fromme Message-Id: <199912140205.DAA11873@dorifer.heim3.tu-clausthal.de> To: freebsd-current@freebsd.org Subject: 2.1 (was: wd driver will be retired) Organization: Administration TU Clausthal Reply-To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anthony Kimball wrote in list.freebsd-current: > What I didn't like about CAM was that I lost my tape drive. Since I > had all my backups and archives on DAT, it felt like a bad thing. I don't think that's related to CAM. At least my crappy HP 1533A drive (DDS2) still works with CAM. > Which reminds me -- can anyone spare a 2.1 CD? Please send me private > mail, if so: I foolishly neglected to convert to CD, and now I can't > find 2.1 on the web anywhere. For example, you can find 2.0.5-Release and 2.1.7.1-Release at ftp7.de.freebsd.org, for example. See the "FreeBSD snap finder" at http://www.itworks.com.au/~gavin/FBSDsites.php3 Well, or check it out from the CVS repository. :) Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 18:30:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-4.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.132]) by hub.freebsd.org (Postfix) with ESMTP id 5729B1537B; Mon, 13 Dec 1999 18:30:35 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA01373; Mon, 13 Dec 1999 23:03:36 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA02922; Mon, 13 Dec 1999 23:05:14 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912132305.XAA02922@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Brian Somers Cc: "CHOI, Junho" , Jon Hamilton , current@FreeBSD.org, stable@FreeBSD.org, brian@hak.lan.Awfulhak.org, brian@hak.lan.Awfulhak.org Subject: Re: ppp over pty: trying to detect CD In-Reply-To: Message from Brian Somers of "Mon, 13 Dec 1999 17:59:24 GMT." <199912131759.RAA00338@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Dec 1999 23:05:14 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is now fixed in -stable (and -current). > > >>>>> "JH" == Jon Hamilton writes: > > > > JH> Running -current from this afternoon, I am having a strange > > JH> symptom with ppp over a pty; ppp does not detect that the pty > > JH> does not support carrier, and will cycle once per second > > JH> waiting for CD to appear. Putting ``set cd off'' in my > > JH> ppp.conf for that target fixed the problem, but I thought I'd > > JH> mention it nonetheless, since that didn't used to be > > JH> required. Certainly not all that big a deal, but I thought it > > JH> was worth a mention. > > > > JH> FreeBSD 4.0-CURRENT #13: Sat Dec 11 20:31:42 CST 1999 > > > > I am using 3-STABLE but I have the same problem with you. I think it > > comes after adding pppoe support in pppd(after 3.3-RELEASE). I am > > -STABLE user but I had to back to 3.3-RELEASE's ppp... I am using ADSL > > service with pptpclient. > > > > JH> and the syslog with debugging turned on, with no "set cd" in the config: > > > > JH> Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: deflink: Using tty_Timeout [0x8072d44] > > JH> Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: Waiting for carrier > > JH> Dec 11 20:48:21 woodstock ppp[3106]: tun1: Debug: deflink: Using tty_Timeout [0x8072d44] > > JH> Dec 11 20:48:21 woodstock ppp[3106]: tun1: Debug: Waiting for carrier > > > > JH> [ and on and on and on ] > > > > -- > > +++ Any opinions in this posting are my own and not those of my employers +++ > > CHOI, Junho > > - Korea FreeBSD Users Group > > - Public Service, Youido Post Office - Web Data Bank -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 18:52:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id A909415412; Mon, 13 Dec 1999 18:52:13 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id SAA91993; Mon, 13 Dec 1999 18:52:07 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 13 Dec 1999 18:52:07 -0800 (PST) From: Doug White To: Kris Kennaway Cc: Peter Wemm , Sheldon Hearn , Marcel Moolenaar , current@FreeBSD.ORG Subject: Re: Speaking of moving files (Re: make world broken building fortunes ) 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 Mon, 13 Dec 1999, Kris Kennaway wrote: > On Mon, 13 Dec 1999, Peter Wemm wrote: > > > I wonder if we should move fortune to usr.bin? It's hardly a game and I'm > > way beyond tired of it being left out of standard paths... > > (ie: "/bin:/usr/bin[:/usr/local/bin]") > > I have no opinion about fortune, but I do think that md5 should be moved > from /sbin to /bin - it's hardly a "system program or administration > utility" but is a quite general-purpose tool. /me 's gratuitous-change alarm goes off Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 19: 2:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 2DB04151DF; Mon, 13 Dec 1999 19:02:20 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id WAA26643; Mon, 13 Dec 1999 22:02:56 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199912140302.WAA26643@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Doug White Cc: Kris Kennaway , Peter Wemm , Sheldon Hearn , Marcel Moolenaar , current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Speaking of moving files (Re: make world broken building fortunes ) References: In-reply-to: Your message of "Mon, 13 Dec 1999 18:52:07 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Dec 1999 22:02:56 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 13 Dec 1999, Kris Kennaway wrote: > > > On Mon, 13 Dec 1999, Peter Wemm wrote: > > > > > I wonder if we should move fortune to usr.bin? It's hardly a game and I'm > > > way beyond tired of it being left out of standard paths... > > > (ie: "/bin:/usr/bin[:/usr/local/bin]") > > > > I have no opinion about fortune, but I do think that md5 should be moved > > from /sbin to /bin - it's hardly a "system program or administration > > utility" but is a quite general-purpose tool. > > /me 's gratuitous-change alarm goes off So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with just the root file system mounted? louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 19: 5:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id C6930154CB for ; Mon, 13 Dec 1999 19:05:16 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 85A6A1C2B; Mon, 13 Dec 1999 22:05:00 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 822D5381B; Mon, 13 Dec 1999 22:05:00 -0500 (EST) Date: Mon, 13 Dec 1999 22:05:00 -0500 (EST) From: Bill Fumerola To: "Louis A. Mamakos" Cc: current@FreeBSD.ORG Subject: Re: Speaking of moving files (Re: make world broken building fortunes ) In-Reply-To: <199912140302.WAA26643@whizzo.transsys.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, 13 Dec 1999, Louis A. Mamakos wrote: > So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with > just the root file system mounted? As one who just got his ass bitten by this, I would vote yes. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 19:31:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from nautilus.shore.net (nautilus.shore.net [207.244.124.104]) by hub.freebsd.org (Postfix) with ESMTP id 8148E15059 for ; Mon, 13 Dec 1999 19:31:16 -0800 (PST) (envelope-from ejon@colltech.com) Received: from pm4-2-128.port.shore.net (colltech.com) [207.244.111.128] by nautilus.shore.net with esmtp (Exim) for current@freebsd.org id 11xigE-00056S-00; Mon, 13 Dec 1999 22:31:15 -0500 Message-ID: <3855BCBB.578EA6A1@colltech.com> Date: Mon, 13 Dec 1999 22:42:51 -0500 From: Eric Jones X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: sysinstall: is it really at the end of its lifecycle? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, In looking through the sysinstall source, I noticed that the man page states that "This product is currently at the end of its life cycle and will eventually be replaced." Is there any truth to this? Apparently this verbiage was introduced in rev 1.20 because the previous text claimed that it would be replaced in 3.1-Release, "hopefully by setup(1)" (?????). Amusingly, the man page author (Jordan?) says, "This utility is a prototype which lasted approximately 3 years past its expiration date and is greatly in need of death." Which may or may not be true, but I've been reading current for quite a while and don't recall any discussion of a sysinstall replacement. I'm thinking of doing some work on automating installs and I'd hate to invest too much effort in a "prototype." Eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 20:16:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.lgishk.com (server.lgishk.com [210.184.22.225]) by hub.freebsd.org (Postfix) with ESMTP id 13B51151E2 for ; Mon, 13 Dec 1999 20:16:44 -0800 (PST) (envelope-from thomasc@lgishk.com) Received: from francis (francis.lgishk.com [210.184.22.235]) by server.lgishk.com (8.9.3/8.9.3) with SMTP id MAA01639 for ; Tue, 14 Dec 1999 12:22:32 +0800 (CST) Message-ID: <001b01bf45e9$d47076e0$eb16b8d2@francis.lgishk.com> From: "Leung Wa, Thomas Chow" To: Subject: join the mailing-list Date: Tue, 14 Dec 1999 12:15:17 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0018_01BF462C.E1DB1540" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0018_01BF462C.E1DB1540 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_000_0018_01BF462C.E1DB1540 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
------=_NextPart_000_0018_01BF462C.E1DB1540-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 22: 1:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from darkstar.qx.net (darkstar.qx.net [208.235.88.101]) by hub.freebsd.org (Postfix) with ESMTP id 3976614ED0; Mon, 13 Dec 1999 22:01:15 -0800 (PST) (envelope-from gchil0@pop.uky.edu) Received: from mail.qx.net (mail.qx.net [208.235.88.10]) by darkstar.qx.net (8.8.7/8.8.7) with ESMTP id BAA04367; Tue, 14 Dec 1999 01:01:08 -0500 Received: from k7 ([208.200.110.198]) by mail.qx.net (Netscape Messaging Server 3.6) with ESMTP id AAA61A4; Tue, 14 Dec 1999 01:03:58 -0500 Message-Id: <4.2.0.58.19991214005153.00953590@pop.uky.edu> X-Sender: gchil0@pop.uky.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Tue, 14 Dec 1999 01:01:21 -0500 To: Peter Wemm , Greg Lehey From: Greg Childers Subject: Re: HEADSUP: wd driver will be retired! Cc: Mike Smith , Poul-Henning Kamp , current@FreeBSD.ORG In-Reply-To: <19991213234037.36B341CA0@overcee.netplex.com.au> References: <19991211130339.N760@mojave.worldwide.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 07:40 AM 12/14/99 +0800, Peter Wemm wrote: >Greg Lehey wrote: > > On Friday, 10 December 1999 at 23:32:27 -0800, Mike Smith wrote: > > > [missing attribution to Greg Childers ] > > >> Except that ATA currently does not work on my system. So I assume I'm not > > >> the only one. > > > > > > Actually, to quote from your original message: > > > > > >> According to technical product summary, the primary IDE interface, on > > >> which both my drives reside, is a PCTech RZ1000 on the PCI local bus. > > > >The RZ1000 is *dangerous*! We are doing no favours by making it run.. :-/ >IMHO It is better to loose the user by not playing ball than to corrupt >their data or run unreliably and make them hate us for it. > >http://www.faqs.org/faqs/pc-hardware-faq/enhanced-IDE/part1/ > o The PC-Tech RZ-1000, used on AT&T, Dell, Gateway and Intel boards, > also has two data-corrupting bugs. See also > . > > In both cases, the corruption occurs only in specific software > environments and is very subtle; you can go on working for months > without suspecting anything more than buggy software. The damage can > be immense. For all the details, look at Roedy Green's (roedy@bix.com) > "PCI EIDE controller flaws" FAQ included with his EIDE test > program which will > test your system for the bugs. Thanks for the info! I wasn't aware of this problem. Fortunately, the fix was easy. From eideflaw.txt in the above mentioned utility (actually it's eidete20.zip now): Some BIOSes have a feature disable the EIDE prefetch buffer. This will bypass both RZ-1000 flaws... I haven't tried ATA after today's update. I'll do that tomorrow. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 22:31:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 442C7152CF for ; Mon, 13 Dec 1999 22:31:38 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id WAA04345; Mon, 13 Dec 1999 22:30:05 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912140630.WAA04345@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Sat, 11 Dec 1999 13:03:39 CST." <19991211130339.N760@mojave.worldwide.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Dec 1999 22:30:05 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 3. Get pissed off with FreeBSD and go elsewhere. don't worry I am sure that quite a few user have left already. This kind of situation reminds of when I accidently broke the gus max backwards compatibility. An old friend of mine sent me a quiet note stating that he switch OSes cause he couldn't use his soundcard with FreeBSD . The mail didn't surprise me what really surprise is that he just switch OSes without warning me. So we have quiet types and "loud" types of users. The users which complaint don't bother me at least I know what they are thinking . The users / developers ratio initially bother me in the multimedia mailing list;however, I came to the conclusion that we do need a large user base to maximize test coverage and feasibility . -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 22:41: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from host.cer.ntnu.edu.tw (cer.ntnu.edu.tw [140.122.119.9]) by hub.freebsd.org (Postfix) with ESMTP id 724E314D03 for ; Mon, 13 Dec 1999 22:41:06 -0800 (PST) (envelope-from clive@host.cer.ntnu.edu.tw) Received: (from clive@localhost) by host.cer.ntnu.edu.tw (8.9.3/8.9.3) id OAA76562 for current@FreeBSD.ORG; Tue, 14 Dec 1999 14:44:12 +0800 (CST) (envelope-from clive) Date: Tue, 14 Dec 1999 14:44:12 +0800 From: Clive Lin To: current@FreeBSD.ORG Subject: pcm playback becomes weird. Message-ID: <19991214144412.A76534@host.cer.ntnu.edu.tw> Reply-To: Clive Lin Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cvsup last night, after rebuild world and kernel, things become weird. part of my dmesg: sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 pcm0: on sbc0 whenever I wany to play anyting via esd, the EsounD report ---- unsupported sound format: 33 Audio device open for 44.1Khz, stereo, 16bit failed Trying 44.1Khz, 8bit stereo. ---- mpg123 plays .mp3 2 times faster then normal play. Even cat a .au file directly to /dev/dsp, RMS sings faster then normal. (Err, the free-software-song.au found on www.gnu.org) x11amp (the aout version installed from ports) freezes when plays anything :-( With several fix, I still cant' fix this problem... since I'm not familiar with bsdcode :( May somebody help this ... ? -- CirX Clive Lin FreeBSD - The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 22:56:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2692315252; Mon, 13 Dec 1999 22:56:30 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA70819; Mon, 13 Dec 1999 23:56:23 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA50727; Mon, 13 Dec 1999 23:56:23 -0700 (MST) Message-Id: <199912140656.XAA50727@harmony.village.org> To: Richard Furda Subject: Re: QIC 40/80 floppy tape drive controller Cc: FreeBSD-stable@FreeBSD.ORG, FreeBSD-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 13 Dec 1999 17:09:08 PST." References: Date: Mon, 13 Dec 1999 23:56:22 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Richard Furda writes: : I have a QIC 40/80 clone floppy tape drive controller (running : 3.3-stable) and wondering if anyone is working/thinking about porting the : ft driver to 3.X/4.X branch. I understand the driver was "removed" : in 2.2.8 due to incompatibility issues. I'd like to help out, thus give : access to a machine with the QIC 40/80 floppy tape controller. At this point, if you aren't writing it, it ain't happening. There are plentty of people who have the hardware, but none have made them work. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 23: 3: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from holonet.net (ifmxoak.informix.com [192.147.88.2]) by hub.freebsd.org (Postfix) with ESMTP id 93F6D1523A; Mon, 13 Dec 1999 23:02:59 -0800 (PST) (envelope-from adamw@holonet.net) Received: by holonet.net (Postfix, from userid 667) id 347842431; Mon, 13 Dec 1999 23:03:55 -0800 (PST) Date: Tue, 14 Dec 1999 07:03:55 +0000 From: Adam Wight To: Mike Smith , Soren Schmidt Cc: current@freebsd.org Subject: Re: Among the ATA casualties... Message-ID: <19991214070355.A207@holonet.net> References: <19991212165900.A482@holonet.net> <199912130714.IAA22321@freebsd.dk> <19991212204053.A734@holonet.net> <199912130708.XAA05626@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912130708.XAA05626@mass.cdrom.com>; from msmith@freebsd.org on Sun, Dec 12, 1999 at 11:08:24PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 12, 1999 at 11:08:24PM -0800, Mike Smith wrote: > You'll need to take this up with Soren; I suspect though that the simplest > answer for you is going to be to stick with 'wd' until you get yourself a > less-broken disk, or manage to analyse the problem in greater depth. Ideally I (we?) would fix the problem in code. Even with the odd error messages emitted by wd everything is quite solid, so I know there's a "better" solution than buying another drive for no reason... I'll wallow around the code tomorrow night and post the results. On Mon, Dec 13, 1999 at 08:14:34AM +0100, Soren Schmidt wrote: > Have you update your /dev with MAKEDEV from usr/src/etc recently? I rebuilt and fresh MAKEDEVved at about 11AM PST with exactly the same results... -Adam Wight To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 23:18:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id A7D761520C for ; Mon, 13 Dec 1999 23:18:39 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA02181; Mon, 13 Dec 1999 23:19:05 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Eric Jones Cc: current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: Your message of "Mon, 13 Dec 1999 22:42:51 EST." <3855BCBB.578EA6A1@colltech.com> Date: Mon, 13 Dec 1999 23:19:05 -0800 Message-ID: <2177.945155945@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > that "This product is currently at the end of its life cycle and will > eventually > be replaced." The handy thing about "eventually" is that it can be a long time. :) > Amusingly, the man page author (Jordan?) says, "This utility is a > prototype which lasted approximately 3 years past its expiration > date and is greatly in need of death." All true, I'm afraid. All I can say is that efforts to revive the effort to replace sysinstall are underway and we're even trying to throw some money-shaped darts at the problem in hopes that we'll hit something. I'm cautiously pessimistic, so we'll see. :) In any case, nothing I'm currently trying to bootstrap here will see the light of day before 5.0 at this point, so hacking sysinstall is probably not such a bad prospect for the 3.x and 4.x releases to come. I've even (*shudder*) been putting some work into cleaning the code up a bit these past couple of days. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 23:29:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id E2E0414C05 for ; Mon, 13 Dec 1999 23:29:05 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA66642; Tue, 14 Dec 1999 08:28:56 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912140728.IAA66642@freebsd.dk> Subject: Re: 4.0-CURRENT boot kernel, ATA_16BIT_ONLY , etc. In-Reply-To: <19991214012749.16573.qmail@web2101.mail.yahoo.com> from "Valentin S. Chopov" at "Dec 13, 1999 05:27:49 pm" To: valsho@yahoo.com (Valentin S. Chopov) Date: Tue, 14 Dec 1999 08:28:56 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Valentin S. Chopov wrote: > Hi, > > The latest 4.0-CURRENT boot floppies are not working > on old ISA boards with 16-bit data transfer only, and > the installation of FreeBSD becomes impossible:( . It > seems that in this case ATA_16BIT_ONLY is not enough - > may be flags to ata0 controller or auto-detection as > Soren promised will be O.K.?! If ATA_16BIT_ONLY doesn't do it, autodetection wont either. What is the exact problem, there is absolutely no info in your statement above?? Have you tried a verbose boot ?? How far does it get?? Hardware config?? -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 23:37:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with ESMTP id 8FEF7152D6 for ; Mon, 13 Dec 1999 23:37:15 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: from cvzoom.net (lcb13.cvzoom.net [63.65.159.13]) by ns.cvzoom.net (8.9.3/8.9.3) with ESMTP id CAA21611; Tue, 14 Dec 1999 02:17:30 -0500 (EST) Message-ID: <3855F364.E66EC87B@cvzoom.net> Date: Tue, 14 Dec 1999 02:36:04 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: Eric Jones , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? References: <2177.945155945@zippy.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 "Jordan K. Hubbard" wrote: > All true, I'm afraid. All I can say is that efforts to revive the > effort to replace sysinstall are underway and we're even trying to > throw some money-shaped darts at the problem in hopes that we'll hit > something. I'm cautiously pessimistic, so we'll see. :) As far as the successor to sysinstall goes, I think it would be nice to have both a console version and an X version, with some X tookit such as Lesstif or Qt, or Tcl/Tk. It could be a lot like RedHat's "linuxconf", where you can use it as both an installer or system administration tool. Not that I'm in love with RedHat's method of doing things, but I think it would be nice to keep sysinstall (or whatever it'd be called) as an all-in-one tool for adding packages or for first-time installs. Maybe we could call it "sysconfig", in honor of the old /etc/sysconfig file that was superceded bt /etc/rc.conf. I saw in CUBFM (the newsgroup) where a couple of people wanted to do a GUI menu-based interfaced to the kernel configuration (as opposed to editing a file by hand). I don't think this would be too hard at all, but I wondered what the experienced FreeBSD users thought of this idea? I was fiddling around with NetBSD-current i386 on this same machine, and it looks really raw compared to FreeBSD. No offense, but they don't even have anything as nice as sysinstall yet. On top of that, there's no utility like we have (userconfig) to edit device parameters before the boot procedes. As a result, if more than one ISA device is attached to the same IRQ, you'll get a kernel panic on boot-up. Of course, I realize NetBSD is more focused on being multi-platform than we, but there's no reason they can't "borrow" some ideas from us, such as userconfig boot editor or sysinstall. In return, we could borrow some of their code for our SPARC port. I think we should keep the lines open between us and NetBSD/OpenBSD, so that we can exchange some ideas more freely. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 13 23:40:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C45C315333 for ; Mon, 13 Dec 1999 23:40:49 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA70158; Tue, 14 Dec 1999 08:40:39 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912140740.IAA70158@freebsd.dk> Subject: Re: Errors from the ata disk driver In-Reply-To: <14421.37871.442695.788714@grasshopper.cs.duke.edu> from Andrew Gallatin at "Dec 13, 1999 08:00:58 pm" To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Tue, 14 Dec 1999 08:40:39 +0100 (CET) Cc: joeo@nks.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Andrew Gallatin wrote: > > Looks like the world is safe for Promise Ultra users: > > Dec 13 18:42:37 waffle /kernel.test: ad2: UDMA CRC READ ERROR blk #22057647 retrying > Dec 13 18:49:21 waffle xntpd[122]: time reset (step) 0.389151 s > Dec 13 19:11:45 waffle xntpd[122]: time reset (step) 0.381460 s > Dec 13 19:35:13 waffle xntpd[122]: time reset (step) 0.459194 s > Dec 13 19:40:47 waffle /kernel.test: ad4: UDMA CRC READ ERROR blk #16658928 retrying > > Thanks! You're welcome :) -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 1: 6: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 59A8014D9F for ; Tue, 14 Dec 1999 01:06:04 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id KAA23219; Tue, 14 Dec 1999 10:05:54 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <3855F364.E66EC87B@cvzoom.net> References: <2177.945155945@zippy.cdrom.com> <3855F364.E66EC87B@cvzoom.net> Date: Tue, 14 Dec 1999 09:54:33 +0100 To: Donn Miller , "Jordan K. Hubbard" From: Brad Knowles Subject: Re: sysinstall: is it really at the end of its lifecycle? Cc: Eric Jones , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:36 AM -0500 1999/12/14, Donn Miller wrote: > I saw in CUBFM (the newsgroup) where a couple of people wanted to > do a GUI menu-based interfaced to the kernel configuration (as > opposed to editing a file by hand). I don't think this would be > too hard at all, but I wondered what the experienced FreeBSD > users thought of this idea? I saw that too. I'm not sure I qualify as an "experienced FreeBSD user", but although I almost certainly would not use the tool myself (I like to have some inkling of what programs are doing and why), I can see why others might want something like this. Myself, I'd like to see an improved installation tool to replace sysinstall, before we worry too much about a GUI kernel configuration tool, although if someone has a real bee in their bonnet to do the latter, I certainly wouldn't be inclined to stand in their way. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 1:49: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 90400150BD for ; Tue, 14 Dec 1999 01:49:03 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA02687; Tue, 14 Dec 1999 01:49:25 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Donn Miller Cc: Eric Jones , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: Your message of "Tue, 14 Dec 1999 02:36:04 EST." <3855F364.E66EC87B@cvzoom.net> Date: Tue, 14 Dec 1999 01:49:25 -0800 Message-ID: <2683.945164965@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As far as the successor to sysinstall goes, I think it would be > nice to have both a console version and an X version, with some X > tookit such as Lesstif or Qt, or Tcl/Tk. It could be a lot like > RedHat's "linuxconf", where you can use it as both an installer > or system administration tool. Which is about correct, though there's a volume of details behind your conceptualization of the system in outline form there. :-) To really understand where we're trying to go, however, it's somewhat helpful to take a good look at where we are now, e.g. stuck with our dear friends sysinstall and the pkg_install suite. The sysinstall program is basically nothing more than a monolithic C program which knows how to do the following "special" things: o Run as init, if so invoked, and do the special inity-things that must be done for an interactive program to subsequently function properly (see system.c:systemInitialize). o How to stomp on disks directly for the purposes of partitioning, writing MBRs, etc. Most of this is already abstracted by libdisk(3) (see also disks.c and label.c). o How to newfs and/or mount filesystems of many different types (UFS, DOS, NFS, CD, floppy, etc) and how to use them as installation media (see media.c and friends). o How to configure network interfaces (with or without DHCP) and how to use FTP servers as media devices, much of the latter being abstracted by ftpio(3) (see tcpip.c and network.c). o How to read FreeBSD "distributions" (gzippied, split tarballs with external property (.inf) files, essentially) and extract them to a mounted hierarchy of UFS partitions (see dist.c). o How to read /usr/ports/INDEX files and enough about the internals of packages to get the pkg_install suite to jump through many hoops you'd rather just not know about (see index.c and package.c). o How to spit out hosts, resolv.conf and rc.conf files from internal variable state, allowing dialogs to be constructed which front-end much of the contents of these files (see config.c and variable.c). o How to use the dialog(3) library in ways that should not be discussed within earshot of small children (see dmenu.c). All of these capabilities adding up to a composite picture with a number of deep and irredeemable flaws. Let's take the UI, for example. Even in a system as simple as sysinstall, we have 2 screens open: the primary interaction screen on VTY1 and the debugging information screen on VTY2 (not counting the possible child holoshell on VTY4 or a child ppp session on VTY3). We put them on separate VTYs because there is no clever multithreaded UI here which allows such output to scroll along in one window while doing other things in another, it's basically a single thread of control per VTY. Anyway, this works great for most things but causes problems the minute you want to install a package which is interactive. Most packages just cause pkg_add to spew various bits of diagnostic output which you'd otherwise be perfectly happy to go onto VTY2, but if a package suddenly takes it into its head to bring up a menu, that's also going to go on VTY2 since sysinstall has no idea in advance that this package might have something meaningful to say and it's going to route its stdin and stdout to VTY2 as always. Unfortunately, that causes consernation on the part of the user who's staring at VTY1 meanwhile and wondering why the package is taking so damn *long* to install. I've seen novices wait so long that medical intervention was necessary in order to save them, leaving us unlikely to win any Tog Awards for interface design in such cases. Sure, I can hear you yelling at those novices from here: "JUST SWITCH TO THE OTHER VTY AND *LOOK*, YOU CHEESEHEADS!", but it's never that simple. Users will be users and even our own annoying common-sense tells us that both pkg_add and sysinstall should really be "rendevousing" on the user, wherever the user's eyeballs might happen to be at the moment, and bringing up the menu in question. It shouldn't be over on the debugging screen and if pkg_add were somehow a library linked into sysinstall and using the same common UI API, initialized by sysinstall to point to VTY1 at startup time, well then by golly that would Just Work(tm) and life would be good again. That's one of the design precepts of the New System, in fact. There is one common UI abstraction which sysinstall II (hereafter referred to as Setup) and the new package system both use. The generic UI front-end API is "bound" at runtime to a back-end implementation class, the two currently supported ones being Qt and Turbovision (the references implementation for the common UI stuff is all written in C++), and everything pops up in the appropriate UI environment from that point forward. Our test code checks for $DISPLAY and does the appropriate Qt magic in that case, otherwise it binds in Turbovision. In theory, one could even write a back-end class which talked to a browser. Scary. :) Having a proper UI also means a lot more than just being able to see your packages when they try and interact with you at install time, it means that many things which were previously limited by the actual dialog(3) UI itself are possible. Ever wonder why there's no "Back" button in many of sysinstall's dialogs, for example? Because the dialog code only supports 2 buttons in menu dialogs and would have required radical reworking of the thing to support an arbitrary number of buttons. :) That is only one of the many limitations of the dialog library and all of them have hampered sysinstall's progress to some extent, a properly designed callback-driven UI making it possible, for example, to do extraction of packages in a separate thread and allow the user to continue to do other things in the UI while extraction is taking place. I won't even get into the possibilities of actually being able to use the mouse, or going towards something closer to a tiled multi-panel interface which makes it more obvious at a glance just where you're going and where you've been in the installation. Another place where sysinstall went wrong, sadly of necessity, is in drawing the dividing line between what a package is supposed to do and sysinstall itself is supposed to do. Because the FreeBSD distribution format is kind of brain-dead in being a split gzipped tar file, a format which does not lend itself to being randomly accessed or selectively decompressed, sysinstall assumes that there's no decent information about distributions available from outside and takes all responsibility for getting the right bits to the right places, doing so by consulting a fair bit of in-built knowledge of what a FreeBSD distributions look like and which ones should go into what directories. This naturally causes divergence problems as FreeBSD distributions evolve and it means that sysinstall has to be cognizant of a lot more special details than it really should about FreeBSD's distribution format. Changing distributions into packages doesn't really help us either since packages are also gzipped tarballs and, what's worse, the pkg_install system attempts to unpack a package into a temporary directory before moving it to its final location given that many packages only install a certain subset of themselves. This is fine if you're installing a 300K package like bash, but a 70MB package like bin might run your /var/tmp directory a bit low. :) Clearly, neither format was really designed properly for the idea of potentially massive packages which also had certain "smarts" about what to do before, during and after their installation. Starting over, we clearly see that the zip file offer quite a bit more in terms of compression, random access and even in-place updating or deletion of contents (not offered with tar). Furthermore, zip files offer "comment fields" on a per-file and per-entry basis, leaving us with room to store MD5/pgp signatures, extended attribution information, etc. That is why the new package system is based on the zip archive format and uses a library (well, currently two, one in C and one in C++) to abstract away the details of zipfile innards. A given zip file need also not be extracted in its entirety now, making the concept of "fat packages" (multiple architecture support) and such possible. In order to ensure that the package's installation routines call the common UI routines for all their interaction needs (remember the VTY2 scenario), a package's installation script is also now assumed to be a secure TCL script rather than being the arbitrary executable it is now. This has a number of implications even more important than simple interface unification, of course, most of them in the realm of security. As previously mentioned, a package is currently installed by unpacking it to a temporary location and then running a number of optional (e.g. if found) scripts before finally going through the packages's "packing list" file for guidance on what to do with the rest of it. A packing list can also contain (and cause to run) in-line shell commands and such during pkg_add's parsing of it, so for the purpose of simplification we'll refer to the packing list as another "script." Now every one of these scripts runs as the user running pkg_add and, in most cases, that's root. That means that a package's install routine can turn right around and "rm -rf /" and you probably won't even notice it happening until stuff starts disappearing out from under your feet. Sure, you can pgp sign trusted packages, but what happens when somebody in a trusted position makes a mistake? Maybe an install script wants to "rm -rf /${TMPJUNKDIR}" in order to be a good citizen after it's done but its not-so-good programmer forgot what happens when you don't spell TEMPJUNKDIR correctly and the variable expands to nothing (another bad reason to prepend the /, but I digress :). Clearly, it should be possible to prevent an installation script from doing *anything* it pleases, even if the system grants the privilege, and that's where the idea for using secure TCL comes in. The language is comparatively small and easy to embed, meaning the results will actually still fit on an mfsroot floppy (sorry PERL addicts), and it's not a dialect of lisp or forth, forstalling the usual religious flame-wars which occur when either of those two languages are mentioned. Somewhat more importantly, the evolution that secure TCL went through in order to run TCL inside of a web browser plug-in (TCLets) gives us the ability to provide a very selective set of operations for packages, any of which can be disabled, overridden or made more picky based on how much we trust the specific package or all packages in general. A file::create routine, for example, could be set to create files in any directory, to create them only in directories found in ${file_create_authorized_dirs}, to create them based on the opinion of an external hook function, etc etc. Because any interpreter can create more (but not less) restricted versions of itself, a package can even elect to override certain system functions with even more anal versions in order to "firewall" some suspect piece of 3rd-party installation code which a port maintainer found along with the original bits. The possibilities are pretty endless and the name of the game is basically to know for certain what a package is doing every step of the way. Along the same lines, you can even write your various primitives to push "undo information" for themselves before committing whatever actions they're designed to commit, allowing arbitrary roll-back of an installation procedure in case of error or even somewhat later in the package's lifetime ("damn, this is broken, give me the previous version!"). Making packages this much more "intelligent" and endowed with a more powerful UI abstraction for getting information from the user would also allow us to finally solve the problem of where to put configuration dialogs and important setup checklists. It's always been clear that they belong in the packages themselves, not the installers of the packages, but since we've always taken a very non-interactive approach to packaging we wound up instead with a situation where sysinstall, for example, used to ask setup questions for Apache. It required constant updating to remain in sync with the apache server's configuration directory location and such and it sucked so much, in fact, that I eventually took that setup screen back out of sysinstall again. Other similar ones remain, however, too useful to remove from sysinstall but not actually belonging *in* sysinstall, they belong in the bindist or the XFree86 distribution or wherever, those distribution formats simply being too stupid to manage this on their own. I could go on and on about how braindead the current packaging system is, how updates and version-specific dependences and occlusion and garbage collection and roll-back and all that good stuff just isn't implemented at all, but that'd be like kicking the bleached and dried skeleton of a dead horse. :-) Suffice it to say, we're certainly hoping to address all of those problems in whatever we eventually come up with as "the new package system." I've described some of the existing parts already and outlined many others which exist only loosly in my mind and the minds of a few others. I've also only touched on some of it, some other (future) topics being the concept of "media maps" which tell where all the various little packages are and what they depend on, the problems constituted in probing for installation media devices and device discovery in general in the installer, etc. We also need to discuss the ways and means of creating not so much an installer but an installation "nucleus" around which we also have a general script execution and menu-generation framework which makes it easy for other people to write "configurators" in secure TCL which take on the job of configuring some utility like, say, Samba. When you pkg_add samba.zip in such a system, it runs its configurator to generate the initial smb.conf file but also drops a copy of the configuration script into some special config directory under the Networking category. Now the next time the user fires up the system configuration tool and goes to the Networking section, they see Samba there as a new item and clicking on it will bring up the configuration tool again (perhaps in the same form, perhaps not). If Samba is deleted from the system, the correspnding item goes away along with the configuration script and I'm sure you all get the idea at this point. No more monolithic prototypes! Framework! Frame-work! Frame-work! [jkh jumps up on a chair and begins waving his hands enthusiastically before losing his balance and toppling over with an abrupt scream]. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 2:31:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 8025715038 for ; Tue, 14 Dec 1999 02:31:29 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id LAA29864 for freebsd-current@FreeBSD.ORG; Tue, 14 Dec 1999 11:31:28 +0100 (CET) (envelope-from olli) Date: Tue, 14 Dec 1999 11:31:28 +0100 (CET) From: Oliver Fromme Message-Id: <199912141031.LAA29864@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" Organization: Administration TU Clausthal Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote in list.freebsd-current: > I have (long time ago) written some extensions to syscons, and > finally decided to clean them up, document and submit them. Just in case somebody is curious, here's a screenshot: http://www.fromme.com/propellers/ Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 2:38:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 9B59D14C05 for ; Tue, 14 Dec 1999 02:38:31 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id CAA03048 for ; Tue, 14 Dec 1999 02:39:00 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" In-reply-to: Your message of "Tue, 14 Dec 1999 11:31:28 +0100." <199912141031.LAA29864@dorifer.heim3.tu-clausthal.de> Date: Tue, 14 Dec 1999 02:38:59 -0800 Message-ID: <3044.945167939@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just in case somebody is curious, here's a screenshot: > http://www.fromme.com/propellers/ That looks very interesting... It's just screaming for some kind of mechanism which allows you to kldload the propeller code in as an extention rather than linking it into the kernel. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 2:49:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with SMTP id 62D8914FB2 for ; Tue, 14 Dec 1999 02:49:39 -0800 (PST) (envelope-from matt@camtech.net.au) Received: from dialup-ad-10-6.camtech.net.au ([203.28.1.134]) by camtech.net.au ; Tue, 14 Dec 1999 21:19:36 +1030 Date: Tue, 14 Dec 1999 21:20:17 +1030 (CST) From: Matthew Thyer X-Sender: matt@localhost Reply-To: thyerm@camtech.net.au To: Mark Newton Cc: current@freebsd.org Subject: Re: RELEASE timelines In-Reply-To: <19991214164003.B1587@internode.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 Yes 2.x went on for too long but I was counting 2.2.x as the equivalent of 3.x due to the change in the release schedule (mainly just a change in the numberring). The thing that worries me is the bad reputation that comes from releasing not quite ready releases. Basically the real way to run FreeBSD is from source ala -STABLE as we dont have a binary patching system established like the commercial vendors. Its argueable that the real FreeBSD is -CURRENT considering there is no automated method for tracking what hasn't yet been committed to -STABLE. It seems there is always a mad rush to MFC when -STABLE is about to pop out another release and this often leads to less than perfect releases and sometimes downright embarrasing mistakes. I'm not calling for a years worth of beta testing ala IRIX 6.5 but there are probably some improvements that can be made to the release system. After all we dont have to have the latest set of gcc, binutils, etc whenever a release appears since we have a good ports system. My first thought would be for cvs to be modified to require tagging of each commit to -CURRENT with a flag to indicate whether it should be merged into -STABLE before the next release (maybe it would indicate which release this change should be in). This will make it easier to process the backlog and allow a longer testing period for -STABLE before each release. I hope this doesn't start too big a thread as I'm rather behind on my cvs-all mail as it is (methinks those people who read all of current and cvs-all must have a job that lets them do this during work time or no wife and kids like myself). On Tue, 14 Dec 1999, Mark Newton wrote: > On Tue, Dec 14, 1999 at 12:34:28AM +1030, Matthew Thyer wrote: > > > Consider the 2.2 stream that went through many more releases (counting > > 2.2.1 -> 2.2.8). Using that yardstick you'd expect 4.0 to stay in > > development until 3.7 is released. I know 7 releases of the 2.2 stream > > was considerred a few too many but surely we can hold 4.0 back a bit > > longer considerring the age of some of the code. > > The fact that the 2.2 stream went on for so long was one of the things > which prompted the change to the way FreeBSD release engineering occurs. > Continuing to bang on 2.x for, what, 16 minor revisions? was a problem, > because it held the many improvements in 3.x back from the release > stream for ages: So long, in fact, that some of the developers who had > been working on them decided to leave for greener pastures where their > code would actually see the light of day. > > Bear in mind the difference between 4.0-RELEASE and 4.1-STABLE too: > 4.0-RELEASE will be for "early adopters" anyway. > > - mark > > -- /=======================================================================\ | 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 Dec 14 2:52: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id E453914CC3 for ; Tue, 14 Dec 1999 02:52:01 -0800 (PST) (envelope-from brad@shub-internet.org) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id LAA28241; Tue, 14 Dec 1999 11:51:49 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <2683.945164965@zippy.cdrom.com> References: <2683.945164965@zippy.cdrom.com> Date: Tue, 14 Dec 1999 11:50:20 +0100 To: "Jordan K. Hubbard" , Donn Miller From: Brad Knowles Subject: Re: sysinstall: is it really at the end of its lifecycle? Cc: Eric Jones , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:49 AM -0800 1999/12/14, Jordan K. Hubbard wrote: > Sure, I can hear you yelling at those > novices from here: "JUST SWITCH TO THE OTHER VTY AND *LOOK*, YOU > CHEESEHEADS!", but it's never that simple. Yup, this is me. Been there, done that many times. This is why I don't use sysinstall to actually install any packages anymore -- I never know which ones are going to want to be interactive. > No more monolithic prototypes! Framework! Frame-work! > Frame-work! [jkh jumps up on a chair and begins waving his hands > enthusiastically before losing his balance and toppling over with an > abrupt scream]. [{()}] [{()}] "Brain hurt." [ THUD ] "I sit down now." -- Brad Knowles Your mouse has moved. Windows NT must be restarted for the change to take effect. Reboot now? [ OK ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 2:57:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id F24B314CA4 for ; Tue, 14 Dec 1999 02:57:51 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11xpe3-000LbO-00; Tue, 14 Dec 1999 10:57:27 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id LAA61654; Tue, 14 Dec 1999 11:57:41 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <385622A5.4FF281D6@scc.nl> Date: Tue, 14 Dec 1999 11:57:41 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: Sheldon Hearn , current@FreeBSD.ORG Subject: Re: make world broken building fortunes References: <19991213134203.117801CCE@overcee.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > > I wonder if we should move fortune to usr.bin? It's hardly a game and I'm > way beyond tired of it being left out of standard paths... > (ie: "/bin:/usr/bin[:/usr/local/bin]") After letting this go through my head for a day (it probably isn't important anymore :-), I think it's better to add /usr/games to the standard search path. Fortune is not a tool you use for anything other than fun and does not really belong in a "serious" directory as /usr/bin. On the other hand it's too frequently used to not have it somewhere in a search path. Also, having games as part of FreeBSD without a proper search path to them is also a bit odd. Anyway, my 2c... -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 3:34:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with SMTP id 9F61614E3A for ; Tue, 14 Dec 1999 03:34:22 -0800 (PST) (envelope-from matt@camtech.net.au) Received: from dialup-ad-10-6.camtech.net.au ([203.28.1.134]) by camtech.net.au ; Tue, 14 Dec 1999 22:04:19 +1030 Date: Tue, 14 Dec 1999 22:05:00 +1030 (CST) From: Matthew Thyer X-Sender: matt@localhost Reply-To: thyerm@camtech.net.au To: "Leung Wa, Thomas Chow" Cc: freebsd-current@FreeBSD.org Subject: Re: join the mailing-list In-Reply-To: <001b01bf45e9$d47076e0$eb16b8d2@francis.lgishk.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 Not this way. Send email to "majordomo@FreeBSD.org" with the following two lines in the body of the message: subscribe freebsd-current subscribe cvs-all You should consider this action very carefully as you will start receiving approximately 200 messages each day. I would suggest that you only subscribe to freebsd-current to start with. On Tue, 14 Dec 1999, Leung Wa, Thomas Chow wrote: > > -- /=======================================================================\ | 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 Dec 14 3:40:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 04E44151D3 for ; Tue, 14 Dec 1999 03:40:45 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id MAA02742 for freebsd-current@FreeBSD.ORG; Tue, 14 Dec 1999 12:40:34 +0100 (CET) (envelope-from olli) Date: Tue, 14 Dec 1999 12:40:34 +0100 (CET) From: Oliver Fromme Message-Id: <199912141140.MAA02742@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" Organization: Administration TU Clausthal Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote in list.freebsd-current: > > Just in case somebody is curious, here's a screenshot: > > http://www.fromme.com/propellers/ > > That looks very interesting... It's just screaming for some kind of > mechanism which allows you to kldload the propeller code in as an > extention rather than linking it into the kernel. :) Actually, I was thinking about that myself. But the problem is that the code is very closely integrated into the existing syscons code (with a lot of #ifdef's, of course). I have never programmed a KLD before (though I will have a look into this when I have some spare time left), but it is my understanding that KLDs are appropriate for parts of the kernel which can be reasonably easy separated from the rest of the kernel. This is not the case for the propellers code. Well, it could possibly be done, but it would require some major design changes to syscons. On the other hand, the propeller code adds about 5 Kbyte to /kernel, which isn't that much. And of course, I'm not voting for putting it into GENERIC. By the way, is there interest in giving the "Print Screen" key an appropriate meaning, i.e. capturing a screenshot? I have a few patches for this to implement that, I'd just have to clean the code up and write a bit of documentation. The GIF on the above webpage was created that way (along with a small userland tool and netpbm). I'm just asking. If nobody cares, I will not bother putting more time and effort into this. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 3:50:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id B733F14D9F for ; Tue, 14 Dec 1999 03:50:04 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id NAA04869; Tue, 14 Dec 1999 13:51:03 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <199912141251.NAA04869@info.iet.unipi.it> Subject: Re: syscons extension: "propellers" In-Reply-To: <199912141140.MAA02742@dorifer.heim3.tu-clausthal.de> from Oliver Fromme at "Dec 14, 1999 12:40:34 pm" To: freebsd-current@FreeBSD.ORG Date: Tue, 14 Dec 1999 13:51:02 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL61 (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 > By the way, is there interest in giving the "Print Screen" > key an appropriate meaning, i.e. capturing a screenshot? > I have a few patches for this to implement that, I'd just > have to clean the code up and write a bit of documentation. > The GIF on the above webpage was created that way (along i was about to ask how did you generate 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 Dec 14 3:56:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id D168114E1A for ; Tue, 14 Dec 1999 03:56:16 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id DAA12449 for ; Tue, 14 Dec 1999 03:56:44 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" In-reply-to: Your message of "Tue, 14 Dec 1999 12:40:34 +0100." <199912141140.MAA02742@dorifer.heim3.tu-clausthal.de> Date: Tue, 14 Dec 1999 03:56:44 -0800 Message-ID: <12445.945172604@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have never programmed a KLD before (though I will have a > look into this when I have some spare time left), but it is > my understanding that KLDs are appropriate for parts of the > kernel which can be reasonably easy separated from the rest > of the kernel. This is not the case for the propellers code. > Well, it could possibly be done, but it would require some > major design changes to syscons. Indeed, so I'd also suspected and more the reason to do so, right? It would make possible many other types of "dashboard" controls as well. Skins for syscons! I can see it now! Haha! [he laughs hysterically as several burly guys in white medical gowns leap out of a panel van, wielding hypodermic needles and various restraints]. > By the way, is there interest in giving the "Print Screen" > key an appropriate meaning, i.e. capturing a screenshot? Sure, that sounds kind of interesting too. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 3:57:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 6A52214F14 for ; Tue, 14 Dec 1999 03:57:06 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11xqZR-000Agf-00; Tue, 14 Dec 1999 13:56:45 +0200 From: Sheldon Hearn To: oliver.fromme@heim3.tu-clausthal.de Cc: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" In-reply-to: Your message of "Tue, 14 Dec 1999 12:40:34 +0100." <199912141140.MAA02742@dorifer.heim3.tu-clausthal.de> Date: Tue, 14 Dec 1999 13:56:45 +0200 Message-ID: <41084.945172605@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 14 Dec 1999 12:40:34 +0100, Oliver Fromme wrote: > By the way, is there interest in giving the "Print Screen" > key an appropriate meaning, i.e. capturing a screenshot? YES! This comes up at least once a month on the -questions mailing list. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 4:34:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with ESMTP id 6FE071512F for ; Tue, 14 Dec 1999 04:34:56 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: from cvzoom.net (lcb13.cvzoom.net [63.65.159.13]) by ns.cvzoom.net (8.9.3/8.9.3) with ESMTP id HAA02955 for ; Tue, 14 Dec 1999 07:15:24 -0500 (EST) Message-ID: <38563935.3FCD4711@cvzoom.net> Date: Tue, 14 Dec 1999 07:33:57 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" References: <199912141140.MAA02742@dorifer.heim3.tu-clausthal.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fromme wrote: > Actually, I was thinking about that myself. But the problem > is that the code is very closely integrated into the existing > syscons code (with a lot of #ifdef's, of course). I think another way (instead of ifdefs) would be to provide some hooks into syscons, so that the "propellers" code can be loaded or unloaded via kldload/unload. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 4:43:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 045C41512F for ; Tue, 14 Dec 1999 04:43:09 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11xrI4-000BPj-00; Tue, 14 Dec 1999 14:42:52 +0200 From: Sheldon Hearn To: oliver.fromme@heim3.tu-clausthal.de Cc: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" In-reply-to: Your message of "Tue, 14 Dec 1999 13:56:45 +0200." <41084.945172605@axl.noc.iafrica.com> Date: Tue, 14 Dec 1999 14:42:52 +0200 Message-ID: <43878.945175372@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 14 Dec 1999 13:56:45 +0200, Sheldon Hearn wrote: > YES! This comes up at least once a month on the -questions mailing > list. :-) I should have been more specific. People are dead keen on these two features: 1) dump an ascii capture of the screen to a file. 2) dump the entire scrollback buffer to a file. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 4:54: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with SMTP id 8028B14D98 for ; Tue, 14 Dec 1999 04:53:55 -0800 (PST) (envelope-from matt@camtech.net.au) Received: from dialup-ad-14-14.camtech.net.au ([203.55.242.142]) by camtech.net.au ; Tue, 14 Dec 1999 23:23:52 +1030 Date: Tue, 14 Dec 1999 23:24:34 +1030 (CST) From: Matthew Thyer X-Sender: matt@localhost Reply-To: thyerm@camtech.net.au To: "Louis A. Mamakos" Cc: Doug White , Kris Kennaway , Peter Wemm , Sheldon Hearn , Marcel Moolenaar , current@FreeBSD.ORG Subject: Re: Speaking of moving files (Re: make world broken building fortunes ) In-Reply-To: <199912140302.WAA26643@whizzo.transsys.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, 13 Dec 1999, Louis A. Mamakos wrote: > So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with > just the root file system mounted? How about removing awk from MAKEDEV so life isn't so hard to recover when you use a 3.3 fixit floppy after removing /dev and not making enough of it again. -- /=======================================================================\ | 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 Dec 14 4:55: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with ESMTP id 3A9F3151FA for ; Tue, 14 Dec 1999 04:55:01 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: from cvzoom.net (lcb13.cvzoom.net [63.65.159.13]) by ns.cvzoom.net (8.9.3/8.9.3) with ESMTP id HAA04020; Tue, 14 Dec 1999 07:35:27 -0500 (EST) Message-ID: <38563DE8.3494309F@cvzoom.net> Date: Tue, 14 Dec 1999 07:54:00 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" References: <12445.945172604@zippy.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 "Jordan K. Hubbard" wrote: > Indeed, so I'd also suspected and more the reason to do so, > right? It would make possible many other types of "dashboard" > controls as well. Skins for syscons! I can see it now! Haha! > [he laughs hysterically as several burly guys in white medical > gowns leap out of a panel van, wielding hypodermic needles > and various restraints]. Actually, that's not a bad idea. One idea I had was combining syscons with XFree86 server code, so you always have a crippled X server running without the bloat of a full-blown X server running. That way, you could just type "xclock", and an xclock would pop up right on your syscons screen (without formally starting X ;-). Well, the idea would be to somehow integrate the driver portion of XFree86 into a new console driver package. You would have your video card type entered in /etc/rc.conf (or some other place, such as /etc/syscons.conf). Then, you could have the option of loading this "enhanced" version of syscons at boot time. Each video driver would be loaded as a KLD. Then, we could do something like run X apps at the virtual console without X running. For example, you want to run netscape without firing up X. You would just type "netscape", and netscape would display right on your syscons virtual console without having to start X proper. What this would give us is a way to run X11 apps as console graphics applications. You would lose window management, however, because the idea is to run the apps as if they were console graphics (e.g. svgalib) apps. One potential drawback is that it would probably bloat the syscons code slightly. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 5: 4: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id BE13214E27 for ; Tue, 14 Dec 1999 05:04:03 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 08DB12DC07; Tue, 14 Dec 1999 14:04:40 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id A31907811; Tue, 14 Dec 1999 14:03:22 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id A0FB110E10; Tue, 14 Dec 1999 14:03:22 +0100 (CET) Date: Tue, 14 Dec 1999 14:03:22 +0100 (CET) From: Andrzej Bialecki To: Donn Miller Cc: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" In-Reply-To: <38563935.3FCD4711@cvzoom.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 Tue, 14 Dec 1999, Donn Miller wrote: > Oliver Fromme wrote: > > > Actually, I was thinking about that myself. But the problem > > is that the code is very closely integrated into the existing > > syscons code (with a lot of #ifdef's, of course). > > I think another way (instead of ifdefs) would be to provide some > hooks into syscons, so that the "propellers" code can be loaded > or unloaded via kldload/unload. Another way to customize various strings, colors and variables could be via sysctl. It's easy e.g. to set up the "propeller" string via sysctl. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 5:29: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 3227614D00 for ; Tue, 14 Dec 1999 05:29:05 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id IAA26167; Tue, 14 Dec 1999 08:29:01 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id IAA13882; Tue, 14 Dec 1999 08:28:59 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id IAA24002; Tue, 14 Dec 1999 08:28:58 -0500 (EST) Date: Tue, 14 Dec 1999 08:28:58 -0500 (EST) From: Thomas David Rivers Message-Id: <199912141328.IAA24002@lakes.dignus.com> To: dmmiller@cvzoom.net, jkh@zippy.cdrom.com Subject: Re: syscons extension: "propellers" Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <38563DE8.3494309F@cvzoom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > One potential drawback is that it would probably bloat the > syscons code slightly. > > - Donn > Uhh... "slightly"? - Dave R. - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 5:53: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id BBB651512F for ; Tue, 14 Dec 1999 05:53:00 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id OAA26224 for current@FreeBSD.org; Tue, 14 Dec 1999 14:48:56 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Tue, 14 Dec 1999 14:48:51 +0100 From: Marcel Moolenaar Message-ID: <38564AC3.B7ADD3AE@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Broken sh(1): A more specific example Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just try: #!/bin/sh PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\ /usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:\ /usr/games:/usr/local/bin:/usr/X11R6/bin:/home/marcel/bin ls ls I get: scones% ./y.sh COPYRIGHT etc share CVS games sys Makefile gnu tools Makefile.inc0 include update.out Makefile.inc1 kerberosIV usr.bin Makefile.upgrade lib usr.sbin README libexec x.out UPDATING make.out x.sh bin mkrelease y.sh contrib release y.sh~ crypto sbin diff.out secure ./y.sh: ls: not found I somehow think it has something to do with the size of the new PATH variable... -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 5:53: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id C02251518D for ; Tue, 14 Dec 1999 05:53:02 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id OAA21878 for current@FreeBSD.org; Tue, 14 Dec 1999 14:31:01 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Tue, 14 Dec 1999 14:30:59 +0100 From: Marcel Moolenaar Message-ID: <38564693.EE9DB4EC@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Broken sh(1)? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Try the following shell script (taken from a buildworld): #!/bin/sh -ev cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/i386 \ PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\ /usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:\ /usr/games:/usr/local/bin:/usr/X11R6/bin:/home/marcel/bin \ INSTALL="sh /usr/src/tools/install.sh" \ DESTDIR=/usr/obj/usr/src/i386 TARGET_ARCH=i386 \ MACHINE_ARCH=i386 make -f Makefile.inc1 -DNOMAN -DNOINFO \ -DNO_FORTRAN -DNO_GDB tools cd /usr/src; make -f Makefile.inc1 par-obj I always get the following: ===> c++filt sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 555 \ c++filt /usr/obj/usr/src/i386/usr/libexec/elf ===> doc ===> cc1obj sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 555 \ cc1obj /usr/obj/usr/src/i386/usr/libexec cd /usr/src; make -f Makefile.inc1 par-obj ./x.sh: make: not found ^^^^^^^^^^^^^^^ At this point PATH contains /usr/bin, so I don't think it's PATH related. context: FreeBSD scones.sup.scc.nl 4.0-CURRENT FreeBSD 4.0-CURRENT #21: Sun Dec 12 19:15:04 CET 1999 marcel@scones.sup.scc.nl:/usr/src/sys/compile/SCONES i386 -r-xr-xr-x 1 root wheel 430152 Dec 11 13:05 /bin/sh -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 6: 0:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 6CA8915106 for ; Tue, 14 Dec 1999 06:00:42 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11xsUn-000C4i-00; Tue, 14 Dec 1999 16:00:05 +0200 From: Sheldon Hearn To: Marcel Moolenaar Cc: current@FreeBSD.ORG Subject: Re: Broken sh(1): A more specific example In-reply-to: Your message of "Tue, 14 Dec 1999 14:48:51 +0100." <38564AC3.B7ADD3AE@scc.nl> Date: Tue, 14 Dec 1999 16:00:05 +0200 Message-ID: <46419.945180005@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 14 Dec 1999 14:48:51 +0100, Marcel Moolenaar wrote: > #!/bin/sh > PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\ > /usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:\ > /usr/games:/usr/local/bin:/usr/X11R6/bin:/home/marcel/bin ls > ls What do you think the shell should be doing with this malformed path? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 6:10:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 4DB7614F36 for ; Tue, 14 Dec 1999 06:10:18 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11xseN-000C7i-00; Tue, 14 Dec 1999 16:09:59 +0200 From: Sheldon Hearn To: Marcel Moolenaar Cc: current@FreeBSD.ORG Subject: Re: Broken sh(1)? In-reply-to: Your message of "Tue, 14 Dec 1999 14:30:59 +0100." <38564693.EE9DB4EC@scc.nl> Date: Tue, 14 Dec 1999 16:09:58 +0200 Message-ID: <46605.945180598@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 14 Dec 1999 14:30:59 +0100, Marcel Moolenaar wrote: > #!/bin/sh -ev > cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/i386 \ > PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\ > /usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:\ > /usr/games:/usr/local/bin:/usr/X11R6/bin:/home/marcel/bin \ > INSTALL="sh /usr/src/tools/install.sh" \ > DESTDIR=/usr/obj/usr/src/i386 TARGET_ARCH=i386 \ > MACHINE_ARCH=i386 make -f Makefile.inc1 -DNOMAN -DNOINFO \ > -DNO_FORTRAN -DNO_GDB tools > cd /usr/src; make -f Makefile.inc1 par-obj You set all those variables for the first make command, but not for the second. What did you expect to happen? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 6:39:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 2B4A014BE6 for ; Tue, 14 Dec 1999 06:39:31 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 11xt6v-0007d5-00; Tue, 14 Dec 1999 14:39:29 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id PAA08756; Tue, 14 Dec 1999 15:39:26 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <3856569E.B665230D@scc.nl> Date: Tue, 14 Dec 1999 15:39:26 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: Broken sh(1): A more specific example References: <46419.945180005@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > On Tue, 14 Dec 1999 14:48:51 +0100, Marcel Moolenaar wrote: > > > #!/bin/sh > > PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\ > > /usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:\ > > /usr/games:/usr/local/bin:/usr/X11R6/bin:/home/marcel/bin ls > > ls > > What do you think the shell should be doing with this malformed path? I assume you all understand that this was a simple invocation of PATH=something ls. You all heard of line-continuation didn't you? Anyway, try this: scones% sh % PATH=/foobar:$PATH ls % ls ls: not found -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 6:52:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id B118C14D72 for ; Tue, 14 Dec 1999 06:52:51 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id PAA38975 for current@FreeBSD.org; Tue, 14 Dec 1999 15:42:16 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Tue, 14 Dec 1999 15:42:11 +0100 From: Marcel Moolenaar Message-ID: <38565743.F27BE03D@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <38564693.EE9DB4EC@scc.nl>, <46605.945180598@axl.noc.iafrica.com> Subject: Re: Broken sh(1)? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > On Tue, 14 Dec 1999 14:30:59 +0100, Marcel Moolenaar wrote: > > > #!/bin/sh -ev > > cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/i386 \ > > PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\ > > /usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:\ > > /usr/games:/usr/local/bin:/usr/X11R6/bin:/home/marcel/bin \ > > INSTALL="sh /usr/src/tools/install.sh" \ > > DESTDIR=/usr/obj/usr/src/i386 TARGET_ARCH=i386 \ > > MACHINE_ARCH=i386 make -f Makefile.inc1 -DNOMAN -DNOINFO \ > > -DNO_FORTRAN -DNO_GDB tools > > cd /usr/src; make -f Makefile.inc1 par-obj > > You set all those variables for the first make command, but not for the > second. What did you expect to happen? That make(1) would execute. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 7:10:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 50FAD14D72 for ; Tue, 14 Dec 1999 07:10:38 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11xtaj-00003J-00; Tue, 14 Dec 1999 15:10:17 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id QAA63059; Tue, 14 Dec 1999 16:10:34 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <38565DEA.4487DF53@scc.nl> Date: Tue, 14 Dec 1999 16:10:34 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn , current@freebsd.org Subject: sh(1) broken caching [was: Re: Broken sh(1)?] References: <712.945183175@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > On Tue, 14 Dec 1999 15:42:11 +0100, Marcel Moolenaar wrote: > > > > You set all those variables for the first make command, but not for the > > > second. What did you expect to happen? > > > > That make(1) would execute. > > But what was the PATH set to _before_ you set it for the first execution > of make? That's what's important, surely? It is. Try this: scones% sh % echo $PATH /sbin:/bin:/usr/sbin:/usr/bin:.... % hash -v builtin hash builtin echo % which ls /bin/ls % hash -v builtin hash builtin echo /usr/bin/which % PATH=/foo:/bar:/bin ls % hash -v builtin hash builtin echo /usr/bin/which /usr/sbin/ls ^^^^^^^^^^^^ Caching index based on temp. path!!!! % ls ls: not found QED :-) -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 8: 0:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id D109D150BD for ; Tue, 14 Dec 1999 08:00:15 -0800 (PST) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id D78511FBA; Tue, 14 Dec 1999 17:00:14 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by shadowmere.student.utwente.nl (Postfix) with ESMTP id D4DB3DE for ; Tue, 14 Dec 1999 17:00:14 +0100 (CET) Date: Tue, 14 Dec 1999 17:00:14 +0100 (CET) From: Pascal Hofstee To: freebsd-current@freebsd.org Subject: configure problems 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 noticed some weird problems lately when running configure-scripts. E.g. when trying to build the gtk12-port configure just hangs waiting for "conftest" to finish (which never seems to do so). I have noticed similair problems with other configure checks (e.g. SDL). Is this a known issue and/or is there any way to solve this problem ? This is on a FreeBSD-current system as of last night. (Noticed the problem occuring for several days now) -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 8:24:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id A2F3E1525F for ; Tue, 14 Dec 1999 08:24:07 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA13786; Tue, 14 Dec 1999 08:24:06 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA86036; Tue, 14 Dec 1999 08:24:06 -0800 (PST) (envelope-from obrien) Date: Tue, 14 Dec 1999 08:24:06 -0800 From: "David O'Brien" To: Pascal Hofstee Cc: freebsd-current@freebsd.org Subject: Re: configure problems Message-ID: <19991214082406.A86003@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from daeron@shadowmere.student.utwente.nl on Tue, Dec 14, 1999 at 05:00:14PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 14, 1999 at 05:00:14PM +0100, Pascal Hofstee wrote: > I have noticed some weird problems lately when running configure-scripts. > E.g. when trying to build the gtk12-port configure just hangs waiting for Please repost this in ports@freebsd.org as that is the proper list for ports-related questions (which this is). freebsd-current@freebsd.org is for issues surounding the bleading edge development in the base system. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 8:26: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from maulwurf.franken.de (maulwurf.franken.de [193.141.110.9]) by hub.freebsd.org (Postfix) with ESMTP id ADAB415159 for ; Tue, 14 Dec 1999 08:26:05 -0800 (PST) (envelope-from gaspode.franken.de!tanis@maulwurf.franken.de) Received: by maulwurf.franken.de via rmail with stdio id for freebsd-current@freebsd.org; Tue, 14 Dec 1999 17:25:53 +0100 (MET) (Smail-3.2 1996-Jul-4 #1 built DST-May-30) Received: (from tanis@localhost) by gaspode.franken.de (8.9.3/8.9.3) id RAA02103 for freebsd-current@freebsd.org; Tue, 14 Dec 1999 17:24:22 +0100 (CET) (envelope-from tanis) Date: Tue, 14 Dec 1999 17:24:22 +0100 From: German Tischler To: freebsd-current@freebsd.org Subject: PCM/AD1816 Message-ID: <19991214172422.A2091@gaspode.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. Would someone please fix recording for the Ad1816 chip in the newpcm code ? (the problem is, that the dma is started on the wrong channel, because the channel number is not initialized during setup.) I've already sent a patch to the maintainer but it seems he didn't like it. -- German Tischler, tanis@gaspode.franken.de "There are two major products that come out of Berkeley: LSD and Unix. We don't believe this to be a coincidence." -- Jeremy S. Anderson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 8:35:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 8A5C115209 for ; Tue, 14 Dec 1999 08:35:10 -0800 (PST) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id LAA77224; Tue, 14 Dec 1999 11:44:26 -0500 (EST) Date: Tue, 14 Dec 1999 11:44:26 -0500 (EST) From: Ben Rosengart To: Bill Fumerola Cc: "Louis A. Mamakos" , current@FreeBSD.ORG Subject: Re: Speaking of moving files (Re: make world broken building fortunes ) 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 Mon, 13 Dec 1999, Bill Fumerola wrote: > On Mon, 13 Dec 1999, Louis A. Mamakos wrote: > > > So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with > > just the root file system mounted? > > As one who just got his ass bitten by this, I would vote yes. As one who's missed chown at times when only root's mounted, I'm with Bill. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 8:53:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 2EFD21526B for ; Tue, 14 Dec 1999 08:53:26 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id PAA74565 for freebsd-current@FreeBSD.ORG; Tue, 14 Dec 1999 15:02:02 GMT (envelope-from nik) Date: Tue, 14 Dec 1999 15:02:02 +0000 From: Nik Clayton To: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" Message-ID: <19991214150202.A73952@catkin.nothing-going-on.org> References: <199912141140.MAA02742@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199912141140.MAA02742@dorifer.heim3.tu-clausthal.de>; from Oliver Fromme on Tue, Dec 14, 1999 at 12:40:34PM +0100 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 14, 1999 at 12:40:34PM +0100, Oliver Fromme wrote: > By the way, is there interest in giving the "Print Screen" > key an appropriate meaning, i.e. capturing a screenshot? > I have a few patches for this to implement that, I'd just > have to clean the code up and write a bit of documentation. > The GIF on the above webpage was created that way (along > with a small userland tool and netpbm). I'm just asking. > If nobody cares, I will not bother putting more time and > effort into this. Yes. I've got some patches somewhere for 2.2x syscons that implemented an ioctl for this, the idea being that these screenshots can then be used in the FAQ and Handbook as necessary. I didn't get around to sorting this out, which is why I never re-integrated them after the big syscons change that happened when -current became 3.0. N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 8:54:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 695A815353 for ; Tue, 14 Dec 1999 08:54:38 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id PAA75975; Tue, 14 Dec 1999 15:13:18 GMT (envelope-from nik) Date: Tue, 14 Dec 1999 15:13:17 +0000 From: Nik Clayton To: Sheldon Hearn Cc: oliver.fromme@heim3.tu-clausthal.de, freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" Message-ID: <19991214151317.B73952@catkin.nothing-going-on.org> References: <41084.945172605@axl.noc.iafrica.com> <43878.945175372@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <43878.945175372@axl.noc.iafrica.com>; from Sheldon Hearn on Tue, Dec 14, 1999 at 02:42:52PM +0200 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 14, 1999 at 02:42:52PM +0200, Sheldon Hearn wrote: > On Tue, 14 Dec 1999 13:56:45 +0200, Sheldon Hearn wrote: > > > YES! This comes up at least once a month on the -questions mailing > > list. :-) > > I should have been more specific. People are dead keen on these two > features: > > 1) dump an ascii capture of the screen to a file. > 2) dump the entire scrollback buffer to a file. We need more than just an ASCII capture. Grabbing the colour information is also very useful. This lets you make full colour pictures of things like sysinstall. If anyone's interested, I've still got the old patches to syscons (which were mostly the work of a third party -- I'm damned if I can find out who sent them to me in my mail archive though) and a little utility that converts from the PC text mode screen format (each char described by 2 bytes, 1st byte is ASCII value, second byte is colour, where top nybble is background colour, bottom nybble is foreground colour). It also reads and decodes the same font files that syscons uses, so the GIF it outputs is as near as damn it identical to what was on the screen originally. Source code available free to a good home :-) N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 10: 1:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from karon.dynas.se (karon.dynas.se [192.71.43.4]) by hub.freebsd.org (Postfix) with SMTP id 9AA2615172 for ; Tue, 14 Dec 1999 10:00:04 -0800 (PST) (envelope-from micke@dynas.se) Received: (qmail 8768 invoked from network); 14 Dec 1999 17:59:56 -0000 Received: from spirit.sto.dynas.se (HELO spirit.dynas.se) (172.16.1.10) by karon.sto.dynas.se with SMTP; 14 Dec 1999 17:59:56 -0000 Received: (qmail 29213 invoked by uid 1101); 14 Dec 1999 17:59:55 -0000 Date: Tue, 14 Dec 1999 18:59:55 +0100 (MET) From: Mikael Hybsch To: freebsd-current@freebsd.org Subject: Last ATA checkin broke the IDE drive on my Toshiba Portege Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Got myself a Toshiba Port=E9g=E9 3110CT last week. The IDE controller isn't recognized by the ata driver. It's an Intel(0x8086) with the device ID 0x7199. Until the last DMA related checkins by S=F8ren, the drive was working in PIO mode. Now it says it's using DMA and after the "Mounting root from ..." message, I get =09ad0: ad_timeout: lost disk contact - resetting =09ata0: resetting devices ..=20 and then it hangs with the disk activity led on. Todays ata checkin said "Try to enable DMA on generic controllers ...", but it still doesn't work. Now it also says "ata0: master: success setting up WDMA2 mode on generic chip". The wdc driver seems to work ok with the 0xa0ffa0ff flags. I have tried looking around on developer.intel.com, but couldn't find any reference to the device ID 0x7199. Where can I find which chipset this is? boot -v from last working PIO mode below Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 =09The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Sun Dec 12 23:52:16 GMT 1999 root@h:/usr/src/sys/compile/H Calibrating clock(s) ... TSC clock: 299933222 Hz, i8254 clock: 1193150 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II/Celeron (299.94-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x66a Stepping =3D 10 Features=3D0x183f9ff real memory =3D 134086656 (130944K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x0030d000 - 0x07fd7fff, 130854912 bytes (31947 pages) avail memory =3D 126955520 (123980K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f0220 bios32: Entry =3D 0xfc455 (c00fc455) Rev =3D 0 Len =3D 1 pcibios: PCI BIOS entry at 0xedcd pnpbios: Found PnP BIOS data at 0xc00f8ed0 pnpbios: Entry =3D f0000:9344 Rev =3D 1.0 pnpbios: Event flag at 510 pnpbios: OEM ID 1934f351 Other BIOS signatures found: ACPI: 000f0170 Preloaded elf kernel "kernel" at 0xc02f4000. Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 pci_open(1):=09mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a):=09mode1res=3D0x80000000 (0x80000000) pci_cfgcheck:=09device 0 [class=3D060000] [hdr=3D00] is there (id=3D7194808= 6) npx0: on motherboard npx0: INT 16 interface pci_open(1):=09mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a):=09mode1res=3D0x80000000 (0x80000000) pci_cfgcheck:=09device 0 [class=3D060000] [hdr=3D00] is there (id=3D7194808= 6) pcib0: on motherboard found->=09vendor=3D0x8086, dev=3D0x7194, revid=3D0x01 =09class=3D06-00-00, hdrtype=3D0x00, mfdev=3D0 =09subordinatebus=3D0 =09secondarybus=3D0 found->=09vendor=3D0x1023, dev=3D0x9525, revid=3D0x49 =09class=3D03-00-00, hdrtype=3D0x00, mfdev=3D0 =09subordinatebus=3D0 =09secondarybus=3D0 =09intpin=3Da, irq=3D11 =09map[10]: type 1, range 32, base ff400000, size 22 =09map[14]: type 1, range 32, base ff3e0000, size 17 =09map[18]: type 1, range 32, base fec00000, size 22 found->=09vendor=3D0x8086, dev=3D0x7198, revid=3D0x01 =09class=3D06-80-00, hdrtype=3D0x00, mfdev=3D1 =09subordinatebus=3D0 =09secondarybus=3D0 found->=09vendor=3D0x8086, dev=3D0x7199, revid=3D0x00 =09class=3D01-01-80, hdrtype=3D0x00, mfdev=3D0 =09subordinatebus=3D0 =09secondarybus=3D0 =09map[20]: type 1, range 32, base 0000fff0, size 4 found->=09vendor=3D0x8086, dev=3D0x719a, revid=3D0x00 =09class=3D0c-03-00, hdrtype=3D0x00, mfdev=3D0 =09subordinatebus=3D0 =09secondarybus=3D0 =09intpin=3Dd, irq=3D11 =09map[20]: type 1, range 32, base 0000ff80, size 5 found->=09vendor=3D0x8086, dev=3D0x719b, revid=3D0x00 =09class=3D06-80-00, hdrtype=3D0x00, mfdev=3D0 =09subordinatebus=3D0 =09secondarybus=3D0 found->=09vendor=3D0x1179, dev=3D0x0d01, revid=3D0x00 =09class=3D0d-00-00, hdrtype=3D0x00, mfdev=3D0 =09subordinatebus=3D0 =09secondarybus=3D0 =09intpin=3Da, irq=3D11 =09map[10]: type 1, range 32, base 0000ff60, size 5 found->=09vendor=3D0x1179, dev=3D0x0617, revid=3D0x20 =09class=3D06-07-00, hdrtype=3D0x02, mfdev=3D1 =09subordinatebus=3D14 =09secondarybus=3D14 =09intpin=3Da, irq=3D255 found->=09vendor=3D0x125d, dev=3D0x1978, revid=3D0x10 =09class=3D04-01-00, hdrtype=3D0x00, mfdev=3D0 =09subordinatebus=3D0 =09secondarybus=3D0 =09intpin=3Da, irq=3D11 =09map[10]: type 1, range 32, base 0000fc00, size 8 found->=09vendor=3D0x11c1, dev=3D0x0441, revid=3D0x01 =09class=3D07-80-00, hdrtype=3D0x00, mfdev=3D0 =09subordinatebus=3D0 =09secondarybus=3D0 =09intpin=3Da, irq=3D3 =09map[10]: type 1, range 32, base ffefff00, size 8 =09map[14]: type 3, range 32, base 000002f8, size 3 =09map[18]: type 1, range 32, base 00001c00, size 8 found->=09vendor=3D0x8086, dev=3D0x1229, revid=3D0x08 =09class=3D02-00-00, hdrtype=3D0x00, mfdev=3D0 =09subordinatebus=3D0 =09secondarybus=3D0 =09intpin=3Da, irq=3D11 =09map[10]: type 1, range 32, base febff000, size 12 =09map[14]: type 1, range 32, base 0000fb40, size 6 =09map[18]: type 1, range 32, base fea00000, size 20 pci0: on pcib0 vga-pci0: irq 11 at devi= ce 4.0 on pci0 chip1: at device 7.0 on= pci0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0: iobase=3D0x01f0 altiobase=3D0x03f6 ata0: mask=3D03 status0=3D50 status1=3D00 ata0: mask=3D03 status0=3D50 status1=3D00 ata0: devices =3D 0x1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=3D0x0170 altiobase=3D0x0376 ata1: mask=3D00 status0=3Dff status1=3Dff uhci0: irq 11 at device 7.2 on pci0 uhci0: (New UHCI DeviceId=3D0x719a8086) usb0: on uhci0 usb0: USB revision 1.0 uhub0: (0x719a8086) UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chip2: at device 7.3 on= pci0 pci0: unknown card (vendor=3D0x1179, dev=3D0x0d01) at 9.0 irq 11 chip3: at device 11.0= on pci0 pci0: unknown card (vendor=3D0x125d, dev=3D0x1978) at 12.0 irq 11 pci0: unknown card (vendor=3D0x11c1, dev=3D0x0441) at 13.0 irq 3 fxp0: irq 11 at device 14.0 on pc= i0 =09using shared irq11. fxp0: Ethernet address 00:00:39:21:b0:1a bpf: fxp0 attached eisa0: on motherboard eisa0: unknown card @@@0000 (0x00000000) at slot 1 isa0: on motherboard Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 ata-isa0: already registered as ata0 ata1: iobase=3D0x0170 altiobase=3D0x0376 ata1: mask=3D00 status0=3Dff status1=3Dff atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: status 10 00 64 psm: data 08 00 00 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81=20 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c=20 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81=20 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c=20 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81=20 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c=20 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=3D0x200> sc0: fb0 kbd0 pcic: polling, can't alloc 0 pcic0: on isa0 pccard0: on pcic0 sio0: irq maps: 0x41 0x51 0x51 0x51 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: irq maps: 0x41 0x41 0x41 0x41 sio1: probe failed test(s): 0 1 2 4 ppc: parallel port found at 0x378 ppc: chipset forced to generic ppc0: ECP SPP SPP ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip: irq 7 plip0: on ppbus 0 bpf: lp0 attached lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 isa_probe_children: probing PnP devices BIOS Geometries: 0:0313fe3f 0..787=3D788 cylinders, 0..254=3D255 heads, 1..63=3D63 sectors 0 accounted for Device configuration finished. bpf: sl0 attached bpf: ppp0 attached new masks: bio 40084840, tty 40031092, net 40071892 bpf: lo0 attached ad0: piomode=3D4 dmamode=3D2 udmamode=3D2 cblid=3D0 ad0: ATA-4 disk at ata0 as master ad0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, PIO Creating DISK ad0 Creating DISK wd0 Mounting root from ufs:/dev/ad0s2a ad0s1: type 0x6, start 63, end =3D 2056319, size 2056257 : OK ad0s2: type 0xa5, start 2056320, end =3D 7293509, size 5237190 : OK start_init: trying /sbin/init --=20 Mikael Hybsch Email: mhybsch@rsasecurity.com RSA Security AB Phone: +46-8-7250900 Box 10704=09=09=09 Fax: +46-8-6494970 S-121 29 STOCKHOLM, SWEDEN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 10:32:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id CA88615172 for ; Tue, 14 Dec 1999 10:32:29 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA22638; Tue, 14 Dec 1999 10:32:23 -0800 (PST) (envelope-from dillon) Date: Tue, 14 Dec 1999 10:32:23 -0800 (PST) From: Matthew Dillon Message-Id: <199912141832.KAA22638@apollo.backplane.com> To: Ben Rosengart Cc: Bill Fumerola , "Louis A. Mamakos" , current@FreeBSD.ORG Subject: Re: Speaking of moving files (Re: make world broken building fortunes ) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> > So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with :> > just the root file system mounted? :> :> As one who just got his ass bitten by this, I would vote yes. : :As one who's missed chown at times when only root's mounted, I'm with Bill. : :-- : Ben Rosengart : :UNIX Systems Engineer, Skunk Group :StarMedia Network, Inc. I think at one time or another all of us have missed *something* in /usr that wasn't in /. For example, disklabel -e doesn't work without vi -- which is in /usr. But if we go down that path we are going to wind up with *every* binary in /usr being moved to /, which is clearly wrong. Moving a well known, long-existing system binary is not something that should be undertaken lightly. I will remind everyone that when sendmail was moved from /usr/libexec to /usr/sbin, it created ramifications that didn't clear up for a year. Sendmail's move could be justified, but I don't think chown's move can be -- certainly not on the basis of something as flimsy as MAKEDEV needing it! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 10:36:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 4A1C615279 for ; Tue, 14 Dec 1999 10:36:01 -0800 (PST) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id NAA78044; Tue, 14 Dec 1999 13:44:25 -0500 (EST) Date: Tue, 14 Dec 1999 13:44:25 -0500 (EST) From: Ben Rosengart To: Matthew Dillon Cc: Bill Fumerola , "Louis A. Mamakos" , current@FreeBSD.ORG Subject: Re: Speaking of moving files (Re: make world broken building fortunes ) In-Reply-To: <199912141832.KAA22638@apollo.backplane.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, 14 Dec 1999, Matthew Dillon wrote: > I think at one time or another all of us have missed *something* in > /usr that wasn't in /. For example, disklabel -e doesn't work without > vi -- which is in /usr. Good example of something else that would be great to have in /bin. *ducking* -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 10:39:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 9584415141 for ; Tue, 14 Dec 1999 10:39:12 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA05917; Tue, 14 Dec 1999 19:38:32 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Ben Rosengart , Bill Fumerola , "Louis A. Mamakos" , current@FreeBSD.ORG Subject: Re: Speaking of moving files (Re: make world broken building fortunes ) In-reply-to: Your message of "Tue, 14 Dec 1999 10:32:23 PST." <199912141832.KAA22638@apollo.backplane.com> Date: Tue, 14 Dec 1999 19:38:32 +0100 Message-ID: <5915.945196712@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912141832.KAA22638@apollo.backplane.com>, Matthew Dillon writes: > > I think at one time or another all of us have missed *something* in > /usr that wasn't in /. For example, disklabel -e doesn't work without > vi -- which is in /usr. EDITOR=/bin/ed export EDITOR disklabel -e > But if we go down that path we are going to wind up with *every* binary > in /usr being moved to /, which is clearly wrong. Dogmatically, yes. Sensibly: I'm not so sure. It would make more sense, considering the way FreeBSD is distributed for /usr/local to be a mountpoint than for /usr to be a mountpoint. /var is traditionally a mountpoint to keep the logs out of harms way (and vice versa), but /usr never had that level of justification. It is getting even less justifiable as time progress. The last sensible argument we had for it was the "load the filesystem from the first 1024 cylinders or bust" problem. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 10:50:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id EF868152E5 for ; Tue, 14 Dec 1999 10:50:42 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA72760; Tue, 14 Dec 1999 11:50:27 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA54339; Tue, 14 Dec 1999 11:50:26 -0700 (MST) Message-Id: <199912141850.LAA54339@harmony.village.org> To: Marcel Moolenaar Subject: Re: Broken sh(1): A more specific example Cc: current@FreeBSD.ORG In-reply-to: Your message of "Tue, 14 Dec 1999 14:48:51 +0100." <38564AC3.B7ADD3AE@scc.nl> References: <38564AC3.B7ADD3AE@scc.nl> Date: Tue, 14 Dec 1999 11:50:26 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38564AC3.B7ADD3AE@scc.nl> Marcel Moolenaar writes: : #!/bin/sh : PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\ : /usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:\ : /usr/games:/usr/local/bin:/usr/X11R6/bin:/home/marcel/bin ls : ls Isn't path not exported, so it is in effect for the first ls, but not the second? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 11: 4:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id D850C1527D for ; Tue, 14 Dec 1999 11:04:36 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id LAA81392 for current@FreeBSD.ORG; Tue, 14 Dec 1999 11:04:32 -0800 (PST) Date: Tue, 14 Dec 1999 11:04:32 -0800 (PST) From: David Wolfskill Message-Id: <199912141904.LAA81392@pau-amma.whistle.com> To: current@FreeBSD.ORG Subject: Re: Speaking of moving files (Re: make world broken building fortunes ) In-Reply-To: <5915.945196712@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Recipient list trimmed down to just the list. dhw] >Date: Tue, 14 Dec 1999 19:38:32 +0100 >From: Poul-Henning Kamp >.... >It would make more sense, considering the way FreeBSD is distributed for >/usr/local to be a mountpoint than for /usr to be a mountpoint. It's hardly impossible for both to be mountpoints. :-} >/var is traditionally a mountpoint to keep the logs out of harms >way (and vice versa), but /usr never had that level of justification. >It is getting even less justifiable as time progress. The last >sensible argument we had for it was the "load the filesystem from >the first 1024 cylinders or bust" problem. Somehow, I'm getting a feeling of deja vu [sorry about the loss of diacritical marks], reflecting on SunOS (both 4.x & 5.x), where /bin is a symlink to /usr/bin, and /lib is a symlink to /usr/lib. All of which reminds me of a singularly memorable time when I came in to (then-)work, where I had my (personal) Sun 3/60 in use as my workstation, and found that it had re-booted, but failed to switch to multi-user mode. Shortening this story, it turns out that /etc/fstab was no longer present. And it had been so long since I had paid any attention to the filesystems, I didn't know what the name of the partition for /usr was. And this was the only SunOS 4.x box in the shop. So... I didn't have access to such user-level programs as "ls", for example. Shell built-ins, especially "echo", along with redirection (to fabricate a skeleton /etc/fstab enough to get boot-strapped) saved the day... and I learned a little. :-} Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 11: 8:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id C1D5F14F9E; Tue, 14 Dec 1999 11:08:42 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id OAA02885; Tue, 14 Dec 1999 14:08:40 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA13677; Tue, 14 Dec 1999 14:08:10 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 14 Dec 1999 14:08:09 -0500 (EST) To: freebsd-current@freebsd.org Cc: tanimura@freebsd.org Subject: ESS1688 newpcm support, soundblaster panics at boot X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14422.37057.798245.620736@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an old, wheezing Dell Lattitude LM with an ESS1688 sound chip. (specs at http://support.dell.com/docs/systems/pespmmx/specs.htm) I have managed to get newpcm to find the 1688 via 'options PNPBIOS' and the following patch: Index: sys/dev/sound/isa/sbc.c =================================================================== RCS file: /home/ncvs/src/sys/dev/sound/isa/sbc.c,v retrieving revision 1.7 diff -u -r1.7 sbc.c --- sbc.c 1999/12/12 02:30:19 1.7 +++ sbc.c 1999/12/14 04:47:41 @@ -187,6 +187,7 @@ {0x01100001, "Avance Asound 110"}, {0x01200001, "Avance Logic ALS120"}, + {0x02017316, "ESS ES1688"}, /* ESS1688 */ {0x68187316, "ESS ES1868"}, /* ESS1868 */ {0x69187316, "ESS ES1869"}, /* ESS1869 */ {0xacb0110e, "ESS ES1869 (Compaq OEM)"}, However, the machine now panics on boot in sbchan_init(), at line 821 of sb.c with a page fault on access to virtual address 0x14: 810 static void * 811 sbchan_init(void *devinfo, snd_dbuf *b, pcm_channel *c, int dir) 812 { 813 struct sb_info *sb = devinfo; 814 struct sb_chinfo *ch = (dir == PCMDIR_PLAY)? &sb->pch : &sb->rch; 815 816 ch->parent = sb; 817 ch->channel = c; 818 ch->buffer = b; 819 ch->buffer->bufsize = DSP_BUFFSIZE; 820 if (chn_allocbuf(ch->buffer, sb->parent_dmat) == -1) return NULL; 821 ch->buffer->chan = (dir == PCMDIR_PLAY)? rman_get_start(sb->drq2) 822 : rman_get_start(sb->drq1); 823 return ch; 824 } I strongly suspect that this is due to the fact that this card has only 1 dma channel. I suspect the panic is caused by rman_get_start(sb->drq2) when sb->drq2 is null. Does newpcm even support simplex operations on soundblaster chips? I ask because I simply could not get simplex operations to work on my wss cards, so I suspect that simplex operation is simply not well tested. Can anybody who is more familiar with newpcm please point me in the right direction? Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 11:10:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 54B7814DE8 for ; Tue, 14 Dec 1999 11:10:46 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11xxL6-0003Mm-00; Tue, 14 Dec 1999 19:10:24 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id UAA64309; Tue, 14 Dec 1999 20:10:41 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <38569631.18F7ECA5@scc.nl> Date: Tue, 14 Dec 1999 20:10:41 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: Broken sh(1): A more specific example References: <38564AC3.B7ADD3AE@scc.nl> <199912141850.LAA54339@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <38564AC3.B7ADD3AE@scc.nl> Marcel Moolenaar writes: > : #!/bin/sh > : PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\ > : /usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:\ > : /usr/games:/usr/local/bin:/usr/X11R6/bin:/home/marcel/bin ls > : ls > > Isn't path not exported, so it is in effect for the first ls, but not > the second? Yes. The normal system default PATH applies to the second ls and it does contain /bin. See my mail about sh's broken caching. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 11:22:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 3E62615281 for ; Tue, 14 Dec 1999 11:22:08 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40325>; Wed, 15 Dec 1999 06:13:31 +1100 Content-return: prohibited Date: Wed, 15 Dec 1999 06:21:48 +1100 From: Peter Jeremy Subject: Re: make world broken building fortunes In-reply-to: <3854BF8C.ED803CBD@scc.nl>; from marcel@scc.nl on Mon, Dec 13, 1999 at 08:42:36PM +1100 To: Marcel Moolenaar Cc: freebsd-current@FreeBSD.ORG Message-Id: <99Dec15.061331est.40325@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <99Dec13.132333est.40338@border.alcanet.com.au> <99Dec13.154631est.40324@border.alcanet.com.au> <3854BF8C.ED803CBD@scc.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Dec-13 20:42:36 +1100, Marcel Moolenaar wrote: >Index: Makefile.inc1 >=================================================================== >RCS file: /home/ncvs/src/Makefile.inc1,v >retrieving revision 1.106 >diff -u -r1.106 Makefile.inc1 >--- Makefile.inc1 1999/12/12 22:24:08 1.106 >+++ Makefile.inc1 1999/12/13 09:40:16 >@@ -113,7 +113,7 @@ > OBJTREE= ${MAKEOBJDIRPREFIX}/${MACHINE_ARCH} > .endif > WORLDTMP= ${OBJTREE}${.CURDIR}/${BUILD_ARCH} >-STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin >+STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games > TMPPATH= ${STRICTTMPPATH}:${PATH} Taking into account Sheldon and Rodney's comments, together with another few glitches (casear is also needed to build the ROT-13 fortune database and my existing makeinfo wasn't up to building the gawk info files), I came up with the following: Index: src/Makefile.inc1 =================================================================== RCS file: /home/CVSROOT/src/Makefile.inc1,v retrieving revision 1.106 diff -u -r1.106 Makefile.inc1 --- Makefile.inc1 1999/12/12 22:24:08 1.106 +++ Makefile.inc1 1999/12/13 23:07:53 @@ -113,7 +113,14 @@ OBJTREE= ${MAKEOBJDIRPREFIX}/${MACHINE_ARCH} .endif WORLDTMP= ${OBJTREE}${.CURDIR}/${BUILD_ARCH} +.if exists(${.CURDIR}/games) && !defined(NOGAMES) +# /usr/games is needed for strfile and caesar, both of which are +# required for building the fortune databases. +STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games +.else STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin +.endif + TMPPATH= ${STRICTTMPPATH}:${PATH} # bootstrap/tools make @@ -334,7 +341,8 @@ # tools - Build tools needed to run the actual build. # .if exists(${.CURDIR}/games) && !defined(NOGAMES) -_strfile= games/fortune/strfile +# strfile and caesar are needed to build the fortune database +_strfile= games/fortune/strfile games/caesar .endif .if ${MACHINE_ARCH} == "i386" && ${MACHINE} == "pc98" @@ -344,7 +352,7 @@ tools:: .for _tool in ${_strfile} ${_aout_tools} usr.bin/gensetdefs \ gnu/usr.bin/binutils usr.bin/objformat usr.bin/yacc usr.bin/colldef \ - gnu/usr.bin/bison gnu/usr.bin/cc + gnu/usr.bin/bison gnu/usr.bin/cc gnu/usr.bin/texinfo cd ${.CURDIR}/${_tool}; \ ${MAKE} obj; \ ${MAKE} depend; \ Index: src/games/fortune/datfiles/Makefile =================================================================== RCS file: /home/CVSROOT/src/games/fortune/datfiles/Makefile,v retrieving revision 1.23 diff -u -r1.23 Makefile --- Makefile 1999/11/05 08:17:53 1.23 +++ Makefile 1999/12/13 20:00:49 @@ -33,16 +33,13 @@ .for f in fortunes fortunes2 fortunes2-o limerick startrek zippy $f.dat: $f - PATH=$$PATH:/usr/games:${.OBJDIR}/../strfile \ strfile -Crs ${.ALLSRC} ${.TARGET} .endfor fortunes-o.dat: fortunes-o - PATH=$$PATH:/usr/games:${.OBJDIR}/../strfile \ strfile -Crsx ${.ALLSRC} ${.TARGET} fortunes-o: fortunes-o.${TYPE} - PATH=$$PATH:/usr/games:${.OBJDIR}/../../caesar \ caesar 13 < ${.ALLSRC} > ${.TARGET} .include I can now successfully do a -CURRENT buildworld on a system running -CURRENT before the signal changes. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 11:46:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 1F8711516B for ; Tue, 14 Dec 1999 11:46:35 -0800 (PST) (envelope-from dagill@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id OAA21282 for ; Tue, 14 Dec 1999 14:46:34 -0500 (EST) Received: from frink.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA03473; Tue, 14 Dec 1999 14:46:03 -0500 Received: (from dagill@localhost) by frink.unx.sas.com (8.9.3/8.9.1) id OAA63744 for freebsd-current@freebsd.org; Tue, 14 Dec 1999 14:46:03 -0500 (EST) (envelope-from dagill) From: David Gillham Message-Id: <199912141946.OAA63744@frink.unx.sas.com> Subject: FTP and PAM syslog question To: freebsd-current@freebsd.org Date: Tue, 14 Dec 1999 14:46:03 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL61 (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 I've been working with ftp and PAM lately and I noticed that when there is no entry for ftp in pam.conf the following messages are generated in the system logs: Dec 14 11:04:11 frink ftpd[61865]: no modules loaded for `ftpd' service Dec 14 11:04:11 frink ftpd[61865]: auth_pam: Permission denied My question is, is "Permission denied" the correct error message to use here? The first message seems fine, but the second part seems to imply that the user was denied access. Looking through pam_strerror.c there doesn't seem to be a good error code for "no module entry in pam.conf" (PAM_SERVICE_ERR perhaps?). Just trying to avoid confusion down the line. Thanks, Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 11:52:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 9BCA914CC3 for ; Tue, 14 Dec 1999 11:52:53 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA14281; Tue, 14 Dec 1999 19:55:19 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01180; Tue, 14 Dec 1999 20:07:44 +0100 (CET) (envelope-from wilko) Date: Tue, 14 Dec 1999 20:07:44 +0100 From: Wilko Bulte To: Matthew Dillon Cc: Ben Rosengart , Bill Fumerola , "Louis A. Mamakos" , current@FreeBSD.ORG Subject: Re: Speaking of moving files (Re: make world broken building fortunes ) Message-ID: <19991214200744.D1003@yedi.iaf.nl> References: <199912141832.KAA22638@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912141832.KAA22638@apollo.backplane.com>; from dillon@apollo.backplane.com on Tue, Dec 14, 1999 at 10:32:23AM -0800 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 14, 1999 at 10:32:23AM -0800, Matthew Dillon wrote: > :> > :> > So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with > :> > just the root file system mounted? > :> > :> As one who just got his ass bitten by this, I would vote yes. > : > :As one who's missed chown at times when only root's mounted, I'm with Bill. > : > :-- > : Ben Rosengart > : > :UNIX Systems Engineer, Skunk Group > :StarMedia Network, Inc. > > I think at one time or another all of us have missed *something* in > /usr that wasn't in /. For example, disklabel -e doesn't work without > vi -- which is in /usr. Bad example: yedi#EDITOR=ed disklabel -re da0 831 1,$p # /dev/rda0c: type: SCSI disk: da0s2 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 [etc] yedi#type ed ed is /bin/ed yedi# 8) -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 11:53:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 6FD5E15370 for ; Tue, 14 Dec 1999 11:53:12 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA14282; Tue, 14 Dec 1999 19:55:20 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01191; Tue, 14 Dec 1999 20:09:14 +0100 (CET) (envelope-from wilko) Date: Tue, 14 Dec 1999 20:09:14 +0100 From: Wilko Bulte To: Poul-Henning Kamp Cc: Matthew Dillon , Ben Rosengart , Bill Fumerola , "Louis A. Mamakos" , current@FreeBSD.ORG Subject: Re: Speaking of moving files (Re: make world broken building fortunes ) Message-ID: <19991214200914.E1003@yedi.iaf.nl> References: <199912141832.KAA22638@apollo.backplane.com> <5915.945196712@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <5915.945196712@critter.freebsd.dk>; from phk@critter.freebsd.dk on Tue, Dec 14, 1999 at 07:38:32PM +0100 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 14, 1999 at 07:38:32PM +0100, Poul-Henning Kamp wrote: > In message <199912141832.KAA22638@apollo.backplane.com>, Matthew Dillon writes: > > > > I think at one time or another all of us have missed *something* in > > /usr that wasn't in /. For example, disklabel -e doesn't work without > > vi -- which is in /usr. > > EDITOR=/bin/ed > export EDITOR > disklabel -e > > > But if we go down that path we are going to wind up with *every* binary > > in /usr being moved to /, which is clearly wrong. > > Dogmatically, yes. Sensibly: I'm not so sure. > > It would make more sense, considering the way FreeBSD is distributed for > /usr/local to be a mountpoint than for /usr to be a mountpoint. > > /var is traditionally a mountpoint to keep the logs out of harms > way (and vice versa), but /usr never had that level of justification. It just has an historical justification. When /usr was another RK05 pack/drive. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 12:10: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 37A3614CA4 for ; Tue, 14 Dec 1999 12:09:58 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id VAA29270 for freebsd-current@FreeBSD.ORG; Tue, 14 Dec 1999 21:09:56 +0100 (CET) (envelope-from olli) Date: Tue, 14 Dec 1999 21:09:56 +0100 (CET) From: Oliver Fromme Message-Id: <199912142009.VAA29270@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: Speaking of moving files Organization: Administration TU Clausthal Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Rosengart wrote in list.freebsd-current: > On Tue, 14 Dec 1999, Matthew Dillon wrote: > > > I think at one time or another all of us have missed *something* in > > /usr that wasn't in /. For example, disklabel -e doesn't work without > > vi -- which is in /usr. > > Good example of something else that would be great to have in /bin. No, really bad example. # export EDITOR=ed # disklabel -e da0s1 759 _ Works perfectly well. But for chown, there is no functional equivalent in /bin or /sbin that I'm aware of. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 12:26:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 32F66151F1 for ; Tue, 14 Dec 1999 12:26:05 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id VAA29478 for freebsd-current@FreeBSD.ORG; Tue, 14 Dec 1999 21:26:04 +0100 (CET) (envelope-from olli) Date: Tue, 14 Dec 1999 21:26:04 +0100 (CET) From: Oliver Fromme Message-Id: <199912142026.VAA29478@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" Organization: Administration TU Clausthal Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote in list.freebsd-current: > On Tue, 14 Dec 1999, Donn Miller wrote: > > I think another way (instead of ifdefs) would be to provide some > > hooks into syscons, so that the "propellers" code can be loaded > > or unloaded via kldload/unload. I'm not yet 100% convinced that it would make sense to separate the propellers code into a module. Is 5 Kbyte of kernel code really that much of a problem? Please note that 1. without the kernel option SC_PROPELLERS, none of the code gets compiled into the kernel. So someone who doesn't need the propellers and doesn't want the 5 Kbyte "bloat" simply doesn't include that option in his kernel. 2. the option should probably not be in GENERIC. 3. once you have the code in your kernel, you can arbitrarily enable and disable (hide) the propellers. When they're disabled, you get the full screen resolution back (25 rows or whatever). You can even enable them on some VTYs and disable them on others, if you want. So the only drawback is 5 Kbyte of kernel growth, once someone has included the option SC_PROPELLERS. Does this justify a rewrite of syscons to divide it into KLDs? Frankly, I don't think so. > Another way to customize various strings, colors and variables could be > via sysctl. It's easy e.g. to set up the "propeller" string via sysctl. Currently it uses ioctls, which is more appropriate for these things, IMO. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 12:47:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 5CCC214F9C for ; Tue, 14 Dec 1999 12:47:23 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40325>; Wed, 15 Dec 1999 07:38:43 +1100 Content-return: prohibited Date: Wed, 15 Dec 1999 07:47:00 +1100 From: Peter Jeremy Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: <3855F364.E66EC87B@cvzoom.net>; from dmmiller@cvzoom.net on Tue, Dec 14, 1999 at 06:36:04PM +1100 To: Donn Miller Cc: current@FreeBSD.ORG Message-Id: <99Dec15.073843est.40325@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <2177.945155945@zippy.cdrom.com> <3855F364.E66EC87B@cvzoom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Dec-14 18:36:04 +1100, Donn Miller wrote: >As far as the successor to sysinstall goes, I think it would be >nice to have both a console version and an X version, with some X >tookit such as Lesstif or Qt, or Tcl/Tk. I know Jordan mentioned Qt before his over-enthusiastic hand-waving made him over-balance, but Lesstif and Qt (or anything else related to X11) have a number of serious problems. Firstly, size: One of sysinstall's requirements is that it fit (along with a variety of other related commands) onto a floppy disk. Last time I checked, the /stand bundle (sysinstall + friends) was ~640K. The smallest X-server (XF86_VGA16) is 1.7MB (plus libraries). I don't have either Qt or Lesstif installed, but from previous dealings with Motif, it's several times the size of the Xserver. Unless we want to mandate the use of ZIP drives (or similar) as FreeBSD install floppies, we're limited to a syscons (or VTxxx) sysinstall. The second problem is that X11 needs a fair amount of configuration before it will work. Whilst the VGA16 server forms a convenient lowest-common-denominator position, it offers no real advantages over a character-mode installation (same screen resolution and number of colours) and significantly poorer performance. Given the primary mission of sysinstall is to load FreeBSD, I'd go so far as to say that developing an X version would be wasting valuable developer resources (IMHO, of course). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 12:52:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from gold.amis.net (gold.amis.net [212.18.37.254]) by hub.freebsd.org (Postfix) with ESMTP id 39D3A151FA for ; Tue, 14 Dec 1999 12:52:06 -0800 (PST) (envelope-from blaz@gold.amis.net) Received: from localhost (blaz@localhost) by gold.amis.net (8.9.3/8.9.3) with ESMTP id VAA03835 for ; Tue, 14 Dec 1999 21:51:59 +0100 (CET) (envelope-from blaz@gold.amis.net) Date: Tue, 14 Dec 1999 21:51:58 +0100 (CET) From: Blaz Zupan To: current@freebsd.org Subject: Re: Speaking of moving files (Re: make world broken building fortunes ) 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 > How about removing awk from MAKEDEV so life isn't so hard to recover > when you use a 3.3 fixit floppy after removing /dev and not making > enough of it again. How about finally starting to work on devfs and forget about all the MAKEDEV junk and leave it as it is for now? Blaz Zupan, blaz@amis.net, http://home.amis.net/blaz/ Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 13: 5:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id EF1BB152E5 for ; Tue, 14 Dec 1999 13:05:08 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA01437; Tue, 14 Dec 1999 13:08:09 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912142108.NAA01437@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: Your message of "Wed, 15 Dec 1999 07:47:00 +1100." <99Dec15.073843est.40325@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Dec 1999 13:08:09 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Firstly, size: One of sysinstall's requirements is that it fit (along > with a variety of other related commands) onto a floppy disk. Last > time I checked, the /stand bundle (sysinstall + friends) was ~640K. > The smallest X-server (XF86_VGA16) is 1.7MB (plus libraries). I don't > have either Qt or Lesstif installed, but from previous dealings with > Motif, it's several times the size of the Xserver. Unless we want to > mandate the use of ZIP drives (or similar) as FreeBSD install > floppies, we're limited to a syscons (or VTxxx) sysinstall. This manages to overlook the fact that the installer has to have a feed to a much larger source of data in order to actually perform the installation. > The second problem is that X11 needs a fair amount of configuration > before it will work. Whilst the VGA16 server forms a convenient > lowest-common-denominator position, it offers no real advantages over > a character-mode installation (same screen resolution and number of > colours) and significantly poorer performance. You're welcome to look at the technology demonstrators currently in use by RedHat and Caldera if you think that this is impossible. > Given the primary mission of sysinstall is to load FreeBSD, I'd > go so far as to say that developing an X version would be wasting > valuable developer resources (IMHO, of course). It's a painful tradeoff between functionality and flash. The latter is an unfortunate necessity if we are to avoid looking hopelessly outdated. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Dec 14 13:15:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from pulsar.dead-end.net (pulsar.high-performance.com [216.15.153.82]) by hub.freebsd.org (Postfix) with ESMTP id 626CB14EDC for ; Tue, 14 Dec 1999 13:15:43 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.153.82] (may be forged)) by pulsar.dead-end.net (8.9.3/8.9.3/DEAD-END/1999020900) with ESMTP id WAA42485 for ; Tue, 14 Dec 1999 22:15:37 +0100 (CET) (envelope-from rock@dead-end.net) Received: from server.rock.net (p3E9D1A88.dip.t-dialin.net [62.157.26.136]) by mailto.dead-end.net (8.9.3/DEAD-END/1999102400-Customer) with ESMTP id WAA42477 for ; Tue, 14 Dec 1999 22:15:36 +0100 (CET) (envelope-from rock@dead-end.net) Received: from dead-end.net (solaris.rock.net [172.23.7.10]) by server.rock.net (8.9.3/8.9.3) with ESMTP id WAA44049 for ; Tue, 14 Dec 1999 22:15:40 +0100 (CET) (envelope-from rock@dead-end.net) Message-ID: <3856B361.9BF2C9D9@dead-end.net> Date: Tue, 14 Dec 1999 22:15:13 +0100 From: "D. Rock" X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.7 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: current@freebsd.org Subject: Re: pcm driver breakage References: <38519601.75B59555@dead-end.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Followup to myself] With the latest changes to the pcm driver, a downgrade of channel.c to 1.8 doesn't help any more: I cannot hear anything while playing something (in my case with mpg123). A verbose output of mpg123 shows me that the application seems to hang after a few write()'s to the sound device (with no sound output). There also doesn't seem to be any interrupt activity on the pcm interrupt. Two days before (but with rev 1.8 of channel.c) I could play any pcm file I have with only some noise at the end if I interrupt mpg123 with ^C. Here the latest configuration information (I can post full output if requested). Kernel config: [...] device pcm0 device sbc0 options PNPBIOS [also without PNPBIOS but with device sbc0 at isa? port 0x220 irq 5 drq 1 flags 0x10 no difference] dmesg output from a verbose boot: sbc0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 pcm0: on sbc0 pcm: setmap 30000, ff00; 0xcd4b5000 -> 30000 pcm: setmap 40000, ff00; 0xcd4c5000 -> 40000 Daniel "D. Rock" wrote: > > Hi, > > something broke between rev 1.8 and 1.9 of /sys/dev/sound/pcm/channel.c > > The driver probes as a: > pcm0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 > > The relevant kernel config entries are > device pcm0 > options PNPBIOS > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 13:26:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 0357214A05 for ; Tue, 14 Dec 1999 13:26:14 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA49481 for ; Tue, 14 Dec 1999 13:26:11 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" In-reply-to: Your message of "Tue, 14 Dec 1999 21:26:04 +0100." <199912142026.VAA29478@dorifer.heim3.tu-clausthal.de> Date: Tue, 14 Dec 1999 13:26:11 -0800 Message-ID: <49477.945206771@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm not yet 100% convinced that it would make sense to separate > the propellers code into a module. Is 5 Kbyte of kernel code > really that much of a problem? Please note that I certainly wouldn't argue this based on size, no. To understand the point I was arguing, consider what would have been the case if the very first screen saver had been hacked straight into syscons rather than making it an optional component. We'd probably have 2 or 3 screensavers at most now, each one being even more of a pain to write than they are now since there was no standardized interface for writing or loading screensavers (in fact, I'd have to say that our existing interface is still pretty weak and should be something more in AfterDark's class of abstraction if we're really seeking to do things right, but I digress :). So I see it with "propellers" - they're an optional feature component and there should be a way of bolting such optional features into syscons without having to recompile the kernel. It's not a question of size, it's a question of design and flexibility and I can argue from such a purist's perspective because I'm not doing any of the work involved and it's thus really easy to do so. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 13:34:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 6254A15119 for ; Tue, 14 Dec 1999 13:34:39 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id WAA02809 for freebsd-current@FreeBSD.ORG; Tue, 14 Dec 1999 22:34:37 +0100 (CET) (envelope-from olli) Date: Tue, 14 Dec 1999 22:34:37 +0100 (CET) From: Oliver Fromme Message-Id: <199912142134.WAA02809@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" Organization: Administration TU Clausthal Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Donn Miller wrote in list.freebsd-current: > Actually, that's not a bad idea. One idea I had was combining > syscons with XFree86 server code, so you always have a crippled X > server running without the bloat of a full-blown X server > running. I'm afraid that wouldn't work. In order to run non-trivial X11 apps, you _will_ need a full-blown X server, including X libs. You'll also need at least a very simple window manager (while xclock would probably work without, Netscape would certainly be pretty unusable). Although, the window manager would be the smallest problem of your approach... > One potential drawback is that it would probably bloat the > syscons code slightly. *ROTFL* :-)) Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 14: 4:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 22A99150B9 for ; Tue, 14 Dec 1999 14:04:33 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id IAA05376; Wed, 15 Dec 1999 08:33:52 +1030 (CST) (envelope-from newton) Date: Wed, 15 Dec 1999 08:33:52 +1030 From: Mark Newton To: Peter Jeremy Cc: Donn Miller , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991215083352.B3500@internode.com.au> References: <2177.945155945@zippy.cdrom.com> <3855F364.E66EC87B@cvzoom.net> <99Dec15.073843est.40325@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <99Dec15.073843est.40325@border.alcanet.com.au> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 07:47:00AM +1100, Peter Jeremy wrote: > On 1999-Dec-14 18:36:04 +1100, Donn Miller wrote: > >As far as the successor to sysinstall goes, I think it would be > >nice to have both a console version and an X version, with some X > >tookit such as Lesstif or Qt, or Tcl/Tk. > > I know Jordan mentioned Qt before his over-enthusiastic hand-waving > made him over-balance, but Lesstif and Qt (or anything else related to > X11) have a number of serious problems. That's ok; He also said it could be back-ended by TurboVision, with the decision of which GUI to use based on whether you had a $DISPLAY environment variable set. > Given the primary mission of sysinstall is to load FreeBSD, I'd > go so far as to say that developing an X version would be wasting > valuable developer resources (IMHO, of course). Long-term, do we want the installer to be a program whose primary mission is to load FreeBSD, or would we prefer a generic framework which provides the situation where loading FreeBSD doesn't differ markedly from loading (and configuring!) any particular package or subsystem after the initial installation event? I think I'll pick the latter. - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 14: 4:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id D65C0150E2 for ; Tue, 14 Dec 1999 14:04:45 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p10-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.139]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id HAA14550; Wed, 15 Dec 1999 07:04:20 +0900 (JST) Message-ID: <3856BD33.5DE1AB48@newsguy.com> Date: Wed, 15 Dec 1999 06:57:07 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Peter Jeremy Cc: Donn Miller , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? References: <2177.945155945@zippy.cdrom.com> <3855F364.E66EC87B@cvzoom.net> <99Dec15.073843est.40325@border.alcanet.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy wrote: > > Firstly, size: One of sysinstall's requirements is that it fit (along > with a variety of other related commands) onto a floppy disk. Last > time I checked, the /stand bundle (sysinstall + friends) was ~640K. > The smallest X-server (XF86_VGA16) is 1.7MB (plus libraries). I don't > have either Qt or Lesstif installed, but from previous dealings with > Motif, it's several times the size of the Xserver. Unless we want to > mandate the use of ZIP drives (or similar) as FreeBSD install > floppies, we're limited to a syscons (or VTxxx) sysinstall. There is a device called cd-rom which more or less qualifies for the "or similar" category you mention. It happens to be the most popular installation media nowadays (though it probably comes second as far as FreeBSD is concerned). > Given the primary mission of sysinstall is to load FreeBSD, I'd > go so far as to say that developing an X version would be wasting > valuable developer resources (IMHO, of course). X install => "user-friendly" install (perceived as) => more market share => more resources -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 14:28:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 3C83C15353 for ; Tue, 14 Dec 1999 14:28:26 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id RAA22682; Tue, 14 Dec 1999 17:28:16 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <199912142228.RAA22682@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <99Dec15.073843est.40325@border.alcanet.com.au> Date: Tue, 14 Dec 1999 17:28:16 -0500 (EST) From: John Baldwin To: Peter Jeremy Subject: Re: sysinstall: is it really at the end of its lifecycle? Cc: current@FreeBSD.org, Donn Miller Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Dec-99 Peter Jeremy wrote: > On 1999-Dec-14 18:36:04 +1100, Donn Miller wrote: >>As far as the successor to sysinstall goes, I think it would be >>nice to have both a console version and an X version, with some X >>tookit such as Lesstif or Qt, or Tcl/Tk. > > I know Jordan mentioned Qt before his over-enthusiastic hand-waving > made him over-balance, but Lesstif and Qt (or anything else related to > X11) have a number of serious problems. [ snip ] > Given the primary mission of sysinstall is to load FreeBSD, I'd > go so far as to say that developing an X version would be wasting > valuable developer resources (IMHO, of course). Many people use sysinstall to do post-install configuration of their system, and the seperate X interface (probably a seperate program) would be targeted at this task. > Peter -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 14:45:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 7148814F7B for ; Tue, 14 Dec 1999 14:45:52 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA49721; Tue, 14 Dec 1999 14:44:52 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Mark Newton Cc: Peter Jeremy , Donn Miller , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: Your message of "Wed, 15 Dec 1999 08:33:52 +1030." <19991215083352.B3500@internode.com.au> Date: Tue, 14 Dec 1999 14:44:52 -0800 Message-ID: <49717.945211492@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I know Jordan mentioned Qt before his over-enthusiastic hand-waving > > made him over-balance, but Lesstif and Qt (or anything else related to > > X11) have a number of serious problems. > > That's ok; He also said it could be back-ended by TurboVision, with > the decision of which GUI to use based on whether you had a $DISPLAY > environment variable set. Indeed, in fact using dlopen() directly from the front-end in order to instantiate the back-end interface component gives you the option of doing it at runtime, making the nucleus of sysinstall very small indeed. Of course, it would probably be linked statically with turbovision in the single-floppy boot case, but that wouldn't stop you from getting more clever with other installation media. > Long-term, do we want the installer to be a program whose primary mission > is to load FreeBSD, or would we prefer a generic framework which provides > the situation where loading FreeBSD doesn't differ markedly from loading > (and configuring!) any particular package or subsystem after the initial > installation event? The latter is, of course, not even a difficult choice to make. We've had the former already, been there and done that. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 14:48:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id F338714F89 for ; Tue, 14 Dec 1999 14:48:40 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.10.0.Beta10/8.10.0.Beta10) with ESMTP id dBEMlnG40376; Tue, 14 Dec 1999 17:47:49 -0500 (EST) Date: Tue, 14 Dec 1999 17:47:49 -0500 (EST) From: jack To: Oliver Fromme Cc: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" In-Reply-To: <199912142134.WAA02809@dorifer.heim3.tu-clausthal.de> 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 Today Oliver Fromme wrote: > I'm afraid that wouldn't work. In order to run non-trivial X11 > apps, you _will_ need a full-blown X server, including X libs. > You'll also need at least a very simple window manager (while > xclock would probably work without, Netscape would certainly be > pretty unusable). I just tried only netscape in my .xinitrc and it worked fine. As well as "ddd ${WINDOW_MANAGER}" or "xterm" run from .xinitrc has for me in the past. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 14:56:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id 3B28414F30; Tue, 14 Dec 1999 14:56:22 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.10.0.Beta10/8.10.0.Beta10) with ESMTP id dBEMuIo41197; Tue, 14 Dec 1999 17:56:18 -0500 (EST) Date: Tue, 14 Dec 1999 17:56:18 -0500 (EST) From: jack To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-Reply-To: <199912142108.NAA01437@mass.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 Today Mike Smith wrote: > > Given the primary mission of sysinstall is to load FreeBSD, I'd > > go so far as to say that developing an X version would be wasting > > valuable developer resources (IMHO, of course). > > It's a painful tradeoff between functionality and flash. The latter is > an unfortunate necessity if we are to avoid looking hopelessly outdated. Not arguing the point in reguard to the "unwashed masses", but when an NT[hates it]/Novell admin watched me install FreeBSD last week his opinion of sysinstall was that it was about the cleanest and most straight forward install program he's seen. Guess he, like I, is more concerned with functionality than flash. :) -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 15: 7:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id 898A414EDC; Tue, 14 Dec 1999 15:07:06 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id 2080C11F; Tue, 14 Dec 1999 15:06:59 -0800 (PST) Date: Tue, 14 Dec 1999 15:06:58 -0800 From: Chris Piazza To: David O'Brien Cc: Pascal Hofstee , freebsd-current@FreeBSD.ORG Subject: Re: configure problems Message-ID: <19991214150658.A722@norn.ca.eu.org> References: <19991214082406.A86003@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991214082406.A86003@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Tue, Dec 14, 1999 at 08:24:06AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 14, 1999 at 08:24:06AM -0800, David O'Brien wrote: > On Tue, Dec 14, 1999 at 05:00:14PM +0100, Pascal Hofstee wrote: > > I have noticed some weird problems lately when running configure-scripts. > > E.g. when trying to build the gtk12-port configure just hangs waiting for > > Please repost this in ports@freebsd.org as that is the proper list for > ports-related questions (which this is). > > freebsd-current@freebsd.org is for issues surounding the bleading edge > development in the base system. It *is* a problem with freebsd-current, though. See PR bin/15328. -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 15: 9:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1C4A515103 for ; Tue, 14 Dec 1999 15:09:21 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA73591; Tue, 14 Dec 1999 16:09:15 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA56037; Tue, 14 Dec 1999 16:09:15 -0700 (MST) Message-Id: <199912142309.QAA56037@harmony.village.org> To: jack Subject: Re: syscons extension: "propellers" Cc: Oliver Fromme , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 14 Dec 1999 17:47:49 EST." References: Date: Tue, 14 Dec 1999 16:09:15 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message jack writes: : I just tried only netscape in my .xinitrc and it worked fine. As : well as "ddd ${WINDOW_MANAGER}" or "xterm" run from .xinitrc has : for me in the past. Nearly all applications "work" without a window manager for some reduced expection of "work." Generally, the problems are restricted to window placement and cursor differeces due to inherited cursors from the decoration windows of X Windows. It is certainly possible to made these minor issues disappear with minimal effort. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 15:11:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A1C5215383; Tue, 14 Dec 1999 15:11:05 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA73607; Tue, 14 Dec 1999 16:10:58 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA56067; Tue, 14 Dec 1999 16:10:58 -0700 (MST) Message-Id: <199912142310.QAA56067@harmony.village.org> To: jack Subject: Re: sysinstall: is it really at the end of its lifecycle? Cc: Mike Smith , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 14 Dec 1999 17:56:18 EST." References: Date: Tue, 14 Dec 1999 16:10:58 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Personally, I like the speed of the current installation and wouldn't want to wait for X to start. It will triple my install setup time since right now I'm hardware speed limited (nearly) with sysinstall. It is much faster to draw the dialog boxes with libdialog than to start X. But I'm a mutant... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 15:14:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 0980715273; Tue, 14 Dec 1999 15:14:29 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA49878; Tue, 14 Dec 1999 15:14:15 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Warner Losh Cc: jack , Mike Smith , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: Your message of "Tue, 14 Dec 1999 16:10:58 MST." <199912142310.QAA56067@harmony.village.org> Date: Tue, 14 Dec 1999 15:14:14 -0800 Message-ID: <49874.945213254@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Personally, I like the speed of the current installation and wouldn't > want to wait for X to start. It will triple my install setup time > since right now I'm hardware speed limited (nearly) with sysinstall. > It is much faster to draw the dialog boxes with libdialog than to > start X. It will always be an option, don't worry. We're not talking about becoming Red Hat, simply offering people more *options*. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 15:17: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 044AA15273; Tue, 14 Dec 1999 15:16:56 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id PAA02317; Tue, 14 Dec 1999 15:16:21 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Tue, 14 Dec 1999 15:16:21 -0800 Date: Tue, 14 Dec 1999 15:16:21 -0800 (PST) From: Kip Macy To: jack Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: jack@germanium.xtalwind.net,msmith@FreeBSD.ORG,current@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Most people I have shown the FreeBSD installer are much more impressed with it than Redhat's snazzy GUI. -Kip On Tue, 14 Dec 1999, jack wrote: > Today Mike Smith wrote: > > > > Given the primary mission of sysinstall is to load FreeBSD, I'd > > > go so far as to say that developing an X version would be wasting > > > valuable developer resources (IMHO, of course). > > > > It's a painful tradeoff between functionality and flash. The latter is > > an unfortunate necessity if we are to avoid looking hopelessly outdated. > > Not arguing the point in reguard to the "unwashed masses", but > when an NT[hates it]/Novell admin watched me install FreeBSD last > week his opinion of sysinstall was that it was about the cleanest > and most straight forward install program he's seen. Guess he, > like I, is more concerned with functionality than flash. :) > > -------------------------------------------------------------------------- > Jack O'Neill Systems Administrator / Systems Analyst > jack@germanium.xtalwind.net Crystal Wind Communications, Inc. > Finger jack@germanium.xtalwind.net for my PGP key. > PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD > enriched, vcard, HTML messages > /dev/null > -------------------------------------------------------------------------- > > > > > 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 Tue Dec 14 15:21:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id CC29014FF9 for ; Tue, 14 Dec 1999 15:21:50 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA26445; Tue, 14 Dec 1999 23:31:30 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA02494; Wed, 15 Dec 1999 00:06:04 +0100 (CET) (envelope-from wilko) Date: Wed, 15 Dec 1999 00:06:04 +0100 From: Wilko Bulte To: Mark Newton Cc: Peter Jeremy , Donn Miller , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991215000600.C77327@yedi.iaf.nl> References: <2177.945155945@zippy.cdrom.com> <3855F364.E66EC87B@cvzoom.net> <99Dec15.073843est.40325@border.alcanet.com.au> <19991215083352.B3500@internode.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991215083352.B3500@internode.com.au>; from newton@internode.com.au on Wed, Dec 15, 1999 at 08:33:52AM +1030 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 08:33:52AM +1030, Mark Newton wrote: > On Wed, Dec 15, 1999 at 07:47:00AM +1100, Peter Jeremy wrote: > > Given the primary mission of sysinstall is to load FreeBSD, I'd > > go so far as to say that developing an X version would be wasting > > valuable developer resources (IMHO, of course). > > Long-term, do we want the installer to be a program whose primary mission > is to load FreeBSD, or would we prefer a generic framework which provides > the situation where loading FreeBSD doesn't differ markedly from loading > (and configuring!) any particular package or subsystem after the initial > installation event? > > I think I'll pick the latter. This does, however, have all the risks of building yet another SMIT or SAM. :-( Neither attempt at making Unix sysadm 'user-friendly' makes me want to cheer. And: how many people would volunteer for such a job? Or is it assumed that since this appears suspiciously like Real Work it will be a paid-for job? -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 15:26:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id 40B1D14FF9 for ; Tue, 14 Dec 1999 15:26:20 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FMR001VJ7RJMJ@mta4.rcsntx.swbell.net> for current@FreeBSD.ORG; Tue, 14 Dec 1999 17:26:08 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id RAA07868; Tue, 14 Dec 1999 17:28:33 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Tue, 14 Dec 1999 17:28:32 -0600 From: Chris Costello Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: <3855F364.E66EC87B@cvzoom.net> To: Donn Miller Cc: "Jordan K. Hubbard" , Eric Jones , current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991214172832.V868@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <2177.945155945@zippy.cdrom.com> <3855F364.E66EC87B@cvzoom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 14, 1999, Donn Miller wrote: > Maybe we could call it "sysconfig", in honor of the old > /etc/sysconfig file that was superceded bt /etc/rc.conf. That's not very creative! I had "Trident" in mind. Only problem is that the name is used by a company that makes video card chips and another company that makes chewing gum. > I saw in CUBFM (the newsgroup) where a couple of people wanted to > do a GUI menu-based interfaced to the kernel configuration (as > opposed to editing a file by hand). I don't think this would be > too hard at all, but I wondered what the experienced FreeBSD > users thought of this idea? Just me. I'm not working with anyone on this. -- |Chris Costello |No program done by a hacker will work unless he is on the system. `----------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 15:33:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 0269E14FC5 for ; Tue, 14 Dec 1999 15:33:10 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA49978; Tue, 14 Dec 1999 15:32:09 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Wilko Bulte Cc: Mark Newton , Peter Jeremy , Donn Miller , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: Your message of "Wed, 15 Dec 1999 00:06:04 +0100." <19991215000600.C77327@yedi.iaf.nl> Date: Tue, 14 Dec 1999 15:32:09 -0800 Message-ID: <49974.945214329@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And: how many people would volunteer for such a job? > Or is it assumed that since this appears suspiciously like Real Work > it will be a paid-for job? It will be a paid-for job, naturally. Something we also have to stay aware of in this discussion is the fact that even if most hackers could give a fig for graphical installers and consider them to be an unneeded bit of hand-holding, it would still be nice to have a framework which stuff could drop into and be accessed via a command line or turbovision type of interface. We're not talking about writing multiple installers for each type of UI, after all, since that would be an unreasonable duplication of labor. We're talking about one installation/configuration code base which can use either X or text mode interfaces at the user's discretion, so both "camps" get what they want. It's also a sad fact that journalists tend to rate products based on different criteria than engineers do, and even where we're getting kudos in the engineering community, magazines are kicking us in the nuts over not having something which competes head-to-head with Caldera or Red Hat. Sad, but true. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 15:36:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta3.rcsntx.swbell.net (mta3.rcsntx.swbell.net [151.164.30.27]) by hub.freebsd.org (Postfix) with ESMTP id A9AD915353 for ; Tue, 14 Dec 1999 15:36:09 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta3.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FMR008ZQ861C8@mta3.rcsntx.swbell.net> for current@FreeBSD.ORG; Tue, 14 Dec 1999 17:34:49 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id RAA07906; Tue, 14 Dec 1999 17:37:15 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Tue, 14 Dec 1999 17:37:14 -0600 From: Chris Costello Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: <2683.945164965@zippy.cdrom.com> To: "Jordan K. Hubbard" Cc: Donn Miller , Eric Jones , current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991214173714.W868@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <3855F364.E66EC87B@cvzoom.net> <2683.945164965@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 14, 1999, Jordan K. Hubbard wrote: > That's one of the design precepts of the New System, in fact. There > is one common UI abstraction which sysinstall II (hereafter referred > to as Setup) and the new package system both use. The generic UI > front-end API is "bound" at runtime to a back-end implementation > class, the two currently supported ones being Qt and Turbovision (the > references implementation for the common UI stuff is all written in > C++), and everything pops up in the appropriate UI environment from > that point forward. Our test code checks for $DISPLAY and does the > appropriate Qt magic in that case, otherwise it binds in Turbovision. > In theory, one could even write a back-end class which talked to a > browser. Scary. :) Is Qt going to be put into the base system in this case? If I can wrestle along with figuring out a few little problems with Qt (ones that I could even somehow more easily solve with Motif!), then I'll continue to develop my system administration tool(s) with it. Another possible solution I was thinking about (but will probably really regret) is keeping a binary distribution and enabling source builds only if a Motif or Lesstif port is installed. Yes, this implies that I would write it in Motif. And yes, I'm also sure that it will meet with much disagreement. > In order to ensure that the package's installation routines call the > common UI routines for all their interaction needs (remember the VTY2 > scenario), a package's installation script is also now assumed to be a > secure TCL script rather than being the arbitrary executable it is > now. This has a number of implications even more important than > simple interface unification, of course, most of them in the realm of > security. So is all of this (TCL, Qt, et. al.) going into the base system to facilitate this work? -- |Chris Costello |A computer scientist is someone who fixes things that aren't broken. `-------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 15:37:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasknow.com (h139-142-245-96.ss.fiberone.net [139.142.245.96]) by hub.freebsd.org (Postfix) with ESMTP id 6B4611536B for ; Tue, 14 Dec 1999 15:37:14 -0800 (PST) (envelope-from freebsd@sasknow.com) Received: from localhost (freebsd@localhost) by sasknow.com (8.9.3/8.9.3) with ESMTP id RAA77193; Tue, 14 Dec 1999 17:37:09 -0600 (CST) (envelope-from freebsd@sasknow.com) Date: Tue, 14 Dec 1999 17:37:09 -0600 (CST) From: Ryan Thompson To: "Daniel C. Sobral" Cc: Peter Jeremy , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-Reply-To: <3856BD33.5DE1AB48@newsguy.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, 15 Dec 1999, Daniel C. Sobral wrote: > Peter Jeremy wrote: > > > > [...] > > Motif, it's several times the size of the Xserver. Unless we want to > > mandate the use of ZIP drives (or similar) as FreeBSD install > > floppies, we're limited to a syscons (or VTxxx) sysinstall. > > There is a device called cd-rom which more or less qualifies for the "or > similar" category you mention. It happens to be the most popular > installation media nowadays (though it probably comes second as far as > FreeBSD is concerned). If memory serves, I first joined FreeBSD in 2.2.3, and I've at one point or another ran just about every release in between, (and many more source builds in between THOSE) up to 3.4-RC, which I'm running today on some development/test machines. I have made dozens of installs of FreeBSD, and have logged a great deal of time in sysinstall on running systems. I have often wondered if FreeBSD would benefit from a graphical installer. As an experienced administrator of FreeBSD on a variety of systems, new and old, I am satisfied with the current text-based offering. As someone who was once an inexperienced administrator of FreeBSD, I was satisfied with the then-text-based offering. (Which, for those of you that don't remember, was remarkably similar to the current text-based offering :-) Daniel, here, sees the X install as being "user-friendly". Is the text based install not? Granted, it's not the point and click interface that windows users are accustomed to, but, clearly, if users can't navigate the menus and manage to find their way to a help menu (and don't know how to read install documentation)... It could be reasonably argued that they are going to experience a rude awakening when presented with the good old root prompt. From a techical standpoint, yes, an X based install would be far too large for a single floppy, even at the simplest level. AND, again, as someone who has installed FreeBSD dozens of times on various systems, I think I should also stress that I have NEVER installed FreeBSD from CD :-) For the average newbie "wanna try it" user, buying the CDs, books and everything neat in a box, is more often than not the safest and simplest route to take. In that case, putting a graphical installer on the CD would be a viable option. To take this a step further, why not keep (or keep something similar to) the current sysinstall, but have an option to fetch, install, configure and run X and another GUI installer distribution, then start the X server and continue the installation process from there? The first portion of the install (selecting media type, allocating space, and labeling) could remain text-based, whereas the user could then be presented with a "Get X and continue installation graphically?" option, which would then download/copy/read a (possibly minimal) X binary distribution, small window manager--TWM would probably suffice :-), as well as the graphical installer. No additional floppy storage space required. The rest of the install, including distribution download, package install, startup config, and all the other wonderful goodies, plus (possibly) a graphical disk partition/labeling utility for post-install changes, would all be done within the comfort of X, after a relatively small download/copy/read is done from their chosen media. Or... To take this ANOTHER small step further... For systems with enough memory (this certainly wouldn't justify increasing the requirements), the text installer could mount a large MFS partition to hold minimal X, window manager and installer... Fetch automatically, do a VERY simple configure from selected media, and continue with the install, INCLUDING a graphical disk partitioner/labeller, after that. Of course, with any of these options, development time and relative cost would be an issue, but, all things being equal, it may result in a flexible install option that a) still runs on virtually any supported platform, and b) gives systems with graphical support the option of a very good looking installer :-) > > Given the primary mission of sysinstall is to load FreeBSD, I'd > > go so far as to say that developing an X version would be wasting > > valuable developer resources (IMHO, of course). > > X install => "user-friendly" install (perceived as) => more market share > => more resources > > -- > Daniel C. Sobral (8-DCS) > who is as social as a wampas > > dcs@newsguy.com > dcs@freebsd.org > --- Ryan Thompson 50% Owner, Technical and Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 15:39:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta2.rcsntx.swbell.net (mta2.rcsntx.swbell.net [151.164.30.26]) by hub.freebsd.org (Postfix) with ESMTP id 66FFB15347 for ; Tue, 14 Dec 1999 15:39:40 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta2.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FMR000HY8BTI0@mta2.rcsntx.swbell.net> for current@FreeBSD.ORG; Tue, 14 Dec 1999 17:38:21 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id RAA07933; Tue, 14 Dec 1999 17:40:43 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Tue, 14 Dec 1999 17:40:43 -0600 From: Chris Costello Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: <99Dec15.073843est.40325@border.alcanet.com.au> To: Peter Jeremy Cc: Donn Miller , current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991214174043.X868@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <2177.945155945@zippy.cdrom.com> <3855F364.E66EC87B@cvzoom.net> <99Dec15.073843est.40325@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999, Peter Jeremy wrote: > Firstly, size: One of sysinstall's requirements is that it fit (along > with a variety of other related commands) onto a floppy disk. Last > time I checked, the /stand bundle (sysinstall + friends) was ~640K. > The smallest X-server (XF86_VGA16) is 1.7MB (plus libraries). I don't > have either Qt or Lesstif installed, but from previous dealings with > Motif, it's several times the size of the Xserver. Unless we want to > mandate the use of ZIP drives (or similar) as FreeBSD install > floppies, we're limited to a syscons (or VTxxx) sysinstall. If it comes down to it, and Jordan's idea for the pkg installation really does/can apply to the actual OS installer, what we could do is have a statically linked, stripped, gzipped X server (though I haven't seen how small VGA16 can be at that point), and a small Xt frontend linked with the installer somehow (depending on what Jordan has in mind), for those with size concerns. Hopefully this won't be the default for things like CDs, however. :) -- |Chris Costello |Eunuchs, the non-gender-specific OS `------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 15:43:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta1.rcsntx.swbell.net (mta1.rcsntx.swbell.net [151.164.30.25]) by hub.freebsd.org (Postfix) with ESMTP id 54F8915103 for ; Tue, 14 Dec 1999 15:43:12 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta1.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FMR00KAX8I64V@mta1.rcsntx.swbell.net> for current@FreeBSD.ORG; Tue, 14 Dec 1999 17:42:07 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id RAA07973; Tue, 14 Dec 1999 17:44:32 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Tue, 14 Dec 1999 17:44:32 -0600 From: Chris Costello Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: <19991215000600.C77327@yedi.iaf.nl> To: Wilko Bulte Cc: Mark Newton , Peter Jeremy , Donn Miller , current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991214174432.Y868@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <2177.945155945@zippy.cdrom.com> <3855F364.E66EC87B@cvzoom.net> <99Dec15.073843est.40325@border.alcanet.com.au> <19991215083352.B3500@internode.com.au> <19991215000600.C77327@yedi.iaf.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999, Wilko Bulte wrote: > This does, however, have all the risks of building yet another SMIT or > SAM. :-( Neither attempt at making Unix sysadm 'user-friendly' makes > me want to cheer. What do you want in making Unix quick to administer? Seems to me that's the real goal of those things. Click click click done, you know. > And: how many people would volunteer for such a job? > Or is it assumed that since this appears suspiciously like Real Work > it will be a paid-for job? Maybe I'll get a free T-shirt for writing Trident (or whatever name I decide on), the 'SAM Done The FreeBSD Way' project. -- |Chris Costello |Managing programmers is like herding cats. `------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 15:45:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from postfix1.free.fr (postfix1.free.fr [212.27.32.21]) by hub.freebsd.org (Postfix) with ESMTP id E0D5815125 for ; Tue, 14 Dec 1999 15:45:29 -0800 (PST) (envelope-from usebsd@free.fr) Received: from safi (paris11-nas2-42-160.dial.proxad.net [212.27.42.160]) by postfix1.free.fr (Postfix) with SMTP id BFA0C28B3C; Wed, 15 Dec 1999 00:43:04 +0100 (MET) From: "BSDman" To: "Poul-Henning Kamp" , "Matthew Dillon" Cc: "Ben Rosengart" , "Bill Fumerola" , "Louis A. Mamakos" , Subject: RE: Speaking of moving files (Re: make world broken building fortunes ) Date: Wed, 15 Dec 1999 00:50:10 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <5915.945196712@critter.freebsd.dk> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote > It would make more sense, considering the way FreeBSD is distributed for > /usr/local to be a mountpoint than for /usr to be a mountpoint. > > /var is traditionally a mountpoint to keep the logs out of harms > way (and vice versa), but /usr never had that level of justification. > one idea about /usr is to allow the admin to mount it read-only. I didn't tried it but this would give some level of security against modifications of the files there in. > It is getting even less justifiable as time progress. The last > sensible argument we had for it was the "load the filesystem from > the first 1024 cylinders or bust" problem. I think the "cylinder" limitation is still of concern. If all OSes come with large root paritions, installing many of them on the same host would be a nightmare. Regards, mouss Free your Net with BSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 15:50:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from drama.navinet.net (drama.navinet.net [216.67.14.8]) by hub.freebsd.org (Postfix) with ESMTP id 685CB15419 for ; Tue, 14 Dec 1999 15:50:10 -0800 (PST) (envelope-from forrie@drama.navinet.net) Received: (from forrie@localhost) by drama.navinet.net (8.9.3/8.9.3) id SAA11512 for freebsd-current@freebsd.org; Tue, 14 Dec 1999 18:50:05 -0500 (EST) Date: Tue, 14 Dec 1999 18:50:02 -0500 From: Forrest Aldrich To: freebsd-current@freebsd.org Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991214185002.A10531@drama.navinet.net> References: <3856BD33.5DE1AB48@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from freebsd@sasknow.com on Tue, Dec 14, 1999 at 05:37:09PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have one request for whatever becomes of sysinstall. And that is to make it technically consistent with the command line utilities capabilities. For example, I ran into (on several different occasions) problems where i would label a disk, allocate paritions, change parition types, etc., and it didn't really get done. Doing it manually would generally resolve the problem. However, it's a Good Thing(tm) to have a gui of one form or another to cater to less-experienced users. That's just very sensible. Thanks. _F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 15:56:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id 0ABB1152F9 for ; Tue, 14 Dec 1999 15:55:57 -0800 (PST) (envelope-from ggm@dstc.edu.au) Received: from dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155]) by piglet.dstc.edu.au (8.9.3/8.9.3) with ESMTP id JAA09713 for ; Wed, 15 Dec 1999 09:55:39 +1000 (EST) X-Mailer: exmh version 2.1.0 09/18/1999 To: current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-Reply-To: Message from Chris Costello of "Tue, 14 Dec 1999 17:40:43 CST." <19991214174043.X868@holly.calldei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Dec 1999 09:55:39 +1000 Message-ID: <15433.945215739@dstc.edu.au> From: George Michaelson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Argh!!! SMIT! Hack! Puke! Why do we have to make FreeBSD more like HP-UX? the most sucky UNIX ever invented apart from AIX? Those of us old enough to remember the SunView install tool with graphical disk icons and the amazing 'free disk hog' barchart partition manager, while finding it vaguely entertaining, could not in all concience say its a 'better' way to install a machine. After the first 10, you generally prefer to do something else anyway. And those icons of 5and1/4 in hard disk boxes become so dated, I mean who is going to draw the littley bittley disk icons each year, and are we going to wind up with skins, and will it make /. (like I care) sysinstall is perfectly good enough as an engine. If you want to emulate the new Anaconda Python/tk interface for Linux why not just run it instead of re-inventing it? Not all apps need a GUI. cat -v as a term of abuse seems to be a concept vanishing from the language... cheers -George -- George Michaelson | DSTC Pty Ltd Email: ggm@dstc.edu.au | University of Qld 4072 Phone: +61 7 3365 4310 | Australia Fax: +61 7 3365 4311 | http://www.dstc.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 16:11:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130]) by hub.freebsd.org (Postfix) with ESMTP id 22DF915313 for ; Tue, 14 Dec 1999 16:11:28 -0800 (PST) (envelope-from lyndon@orthanc.ab.ca) Received: from orthanc.ab.ca (localhost.orthanc.ab.ca [127.0.0.1]) by orthanc.ab.ca (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id dBF0BJQ22600 for ; Tue, 14 Dec 1999 17:11:19 -0700 (MST) Message-Id: <199912150011.dBF0BJQ22600@orthanc.ab.ca> To: current@freebsd.org Subject: Re: Speaking of moving files (Re: make world broken building fortunes ) In-reply-to: Your message of "Wed, 15 Dec 1999 00:50:10 +0100." Date: Tue, 14 Dec 1999 17:11:18 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "BSDman" == BSDman writes: BSDman> one idea about /usr is to allow the admin to mount it BSDman> read-only. I didn't tried it but this would give some BSDman> level of security against modifications of the files there BSDman> in. This is particulary useful in a lab environment where you have xx workstations with local root, var, and swap NFS mounting an RO /usr. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 16:19:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 42D6A151F9 for ; Tue, 14 Dec 1999 16:19:02 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 0B8C12DC09; Wed, 15 Dec 1999 01:19:40 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id 52AEE7811; Wed, 15 Dec 1999 01:15:31 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 509DE10E10; Wed, 15 Dec 1999 01:15:31 +0100 (CET) Date: Wed, 15 Dec 1999 01:15:31 +0100 (CET) From: Andrzej Bialecki To: Bill Fumerola Cc: "Louis A. Mamakos" , current@FreeBSD.ORG Subject: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) 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 Mon, 13 Dec 1999, Bill Fumerola wrote: > On Mon, 13 Dec 1999, Louis A. Mamakos wrote: > > > So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with > > just the root file system mounted? > > As one who just got his ass bitten by this, I would vote yes. On a related subject: don't you think it's high time to end up this madness with MAKEDEV being a shell script, and reimplement it in C? Today, MAKEDEV uses about 10 external programs, it's inflexible and complicated, but the task it's doing could be relatively easily ported to C plus config file. Have you ever tried to use it in nonstandad location, or on a minimal system? The end result is usually an unpleasant surprise... Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 16:29: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 4021114E8C for ; Tue, 14 Dec 1999 16:28:55 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id KAA00545; Wed, 15 Dec 1999 10:57:36 +1030 (CST) (envelope-from newton) Date: Wed, 15 Dec 1999 10:57:36 +1030 From: Mark Newton To: Ryan Thompson Cc: "Daniel C. Sobral" , Peter Jeremy , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991215105736.A467@internode.com.au> References: <3856BD33.5DE1AB48@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 14, 1999 at 05:37:09PM -0600, Ryan Thompson wrote: > Daniel, here, sees the X install as being "user-friendly". Is the text > based install not? Let's not get too fixated on the visual aspect of installing the OS: That's just a sideline (an important one, but a sideline nonetheless). There's a whole swag of structural details which the current sysinstall fails miserably in. For example, has anyone noticed how virtually every OS on the market except the *BSD's build up their distributions in the same file format and with the same package database machinations as their third-party add-on packages? If I'm on a Solaris box, or an IRIX box, or a SCO box, or a Redhat box, or essentially anything else except BSD I install the base operating system using the same tools I'd use for any other software. This provides enormous benefits. Worried about bloat? Define what you mean by "Base system install" at the actual time that you're installing the system. Don't need a nameserver? Don't install it. Don't need lpd? Don't install it. Do you need Fortran? Fine, install it, even though it isn't part of the default installation set (ooooh, I'm gonna get flamed for that :-) Upgrades are another issue: At the moment, patching parts of the base system is utterly hopeless. Consider what happens whenever there's a security advisory: We release a source-code patch to CERT, and say to everyone, "Install the patch if you have the sources installed, but if you don't have the sources you're going to have to upgrade the entire god-damned operating system!" And once someone has upgraded by patching the source code, they suddenly have a "base distribution" which is subtly different from what would have been described as the "base distribution" the day before they patched it, so future bug reports become a shot-in-the-dark type of problem. Wouldn't it be easier to say, "pkgpatch named-8.8.2p2857" (or something - I've pulled that example out of my butt) and have it md5 the files it's about to replace to make sure that you have the faulty version it's attempting to upgrade, back up the old files, install a new binary, and patch the sources if they happen to be installed, AND RECORD THE FACT THAT THIS HAS BEEN DONE IN THE PACKAGE DATABASE? And if you don't like the patch? Back it out. This is something other OS's find trivial: To continue the example of patching named, every other UNIX I can think of has named in a stand-alone package as part of the base install. If you want to upgrade it, you install a more recent version of the package, and the fact that you've done it gets recorded in a "this has been patched" section of the package database. Note that I haven't mentioned user-interfaces once in the discussion above: The problems with sysinstall have very little to do with user interfaces. > To take this a step further, why not keep (or keep something similar to) > the current sysinstall, but have an option to fetch, install, configure > and run X and another GUI installer distribution, then start the X server > and continue the installation process from there? This discussion is orthogonal to the one we're actually happening, which is about the structural problems in sysinstall which has lead Jordan to place the "this has a limited lifespan" comment in the sources. You can do what you're proposing whether we end up with a new installer or not. Anyway, don't think about user-interfaces -- They're the easy bit. Re-read Jordan's (very lucid) message on the topic from a few hours ago and think about the problems described therein and the solutions that have been proposed; you can slot your favourite user interface (even one that looks the same as the one we're using now!) into that picture later once the background issues have been dealt with. - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 16:29:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id E0E1715281 for ; Tue, 14 Dec 1999 16:29:23 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id QAA20326 for freebsd-current@FreeBSD.ORG; Tue, 14 Dec 1999 16:29:19 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912150029.QAA20326@gndrsh.dnsmgr.net> Subject: Re: Speaking of moving files In-Reply-To: <199912142009.VAA29270@dorifer.heim3.tu-clausthal.de> from Oliver Fromme at "Dec 14, 1999 09:09:56 pm" To: freebsd-current@FreeBSD.ORG Date: Tue, 14 Dec 1999 16:29:18 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL54 (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 [Charset ISO-8859-1 unsupported, filtering to ASCII...] > Ben Rosengart wrote in list.freebsd-current: > > On Tue, 14 Dec 1999, Matthew Dillon wrote: > > > > > I think at one time or another all of us have missed *something* in > > > /usr that wasn't in /. For example, disklabel -e doesn't work without > > > vi -- which is in /usr. > > > > Good example of something else that would be great to have in /bin. > > No, really bad example. > > # export EDITOR=ed > # disklabel -e da0s1 > 759 > _ > > Works perfectly well. But for chown, there is no functional > equivalent in /bin or /sbin that I'm aware of. A person who really knew fsdb could do it /bin/fsdb, infact it's not really that hard... as fsdb has chown, chgrp, chmod, chtype chname and all the others built in as native commands ;-) :-) :-) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 16:34: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 814B715206 for ; Tue, 14 Dec 1999 16:34:01 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id DFDE22DC0A; Wed, 15 Dec 1999 01:34:39 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id 3EC4C7811; Wed, 15 Dec 1999 01:30:52 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 3C55E10E10; Wed, 15 Dec 1999 01:30:52 +0100 (CET) Date: Wed, 15 Dec 1999 01:30:52 +0100 (CET) From: Andrzej Bialecki To: "Jordan K. Hubbard" Cc: Wilko Bulte , Mark Newton , Peter Jeremy , Donn Miller , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-Reply-To: <49974.945214329@zippy.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 Tue, 14 Dec 1999, Jordan K. Hubbard wrote: > Something we also have to stay aware of in this discussion is the fact > that even if most hackers could give a fig for graphical installers > and consider them to be an unneeded bit of hand-holding, it would > still be nice to have a framework which stuff could drop into and be > accessed via a command line or turbovision type of interface. We're > not talking about writing multiple installers for each type of UI, > after all, since that would be an unreasonable duplication of labor. > We're talking about one installation/configuration code base which can > use either X or text mode interfaces at the user's discretion, so > both "camps" get what they want. I should perhaps mention here that there are windowing GUIs out there which are not X11. I know of two: W (almost dead, but quite sufficient), and Microwindows (very new, still quite limited, but under active development). Both use either VGA or VESA graphics. Both are very small (around 100kB). Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 17:41: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-12.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.140]) by hub.freebsd.org (Postfix) with ESMTP id E0B7B152D5 for ; Tue, 14 Dec 1999 17:41:03 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA47382; Wed, 15 Dec 1999 01:37:44 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA01185; Wed, 15 Dec 1999 01:39:28 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912150139.BAA01185@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Andrzej Bialecki Cc: Bill Fumerola , "Louis A. Mamakos" , current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) In-Reply-To: Message from Andrzej Bialecki of "Wed, 15 Dec 1999 01:15:31 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Dec 1999 01:39:28 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > On a related subject: don't you think it's high time to end up this > madness with MAKEDEV being a shell script, and reimplement it in C? Today, [.....] *cough*DEVFS*cough* -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 17:45:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta1.rcsntx.swbell.net (mta1.rcsntx.swbell.net [151.164.30.25]) by hub.freebsd.org (Postfix) with ESMTP id 5FE48150BB for ; Tue, 14 Dec 1999 17:45:32 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta1.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FMR008BRE40JF@mta1.rcsntx.swbell.net> for current@FreeBSD.ORG; Tue, 14 Dec 1999 19:43:13 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id TAA08233; Tue, 14 Dec 1999 19:45:38 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Tue, 14 Dec 1999 19:45:37 -0600 From: Chris Costello Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: <15433.945215739@dstc.edu.au> To: George Michaelson Cc: current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991214194537.A868@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <15433.945215739@dstc.edu.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999, George Michaelson wrote: > Why do we have to make FreeBSD more like HP-UX? the most sucky UNIX ever > invented apart from AIX? Is this a fact? I always sort of liked HP-UX. Not as fun as FreeBSD for obvious reasons, but... > sysinstall is perfectly good enough as an engine. No it's not. Ask its author, for one. You can read what he's had to say about it throughout this whole thread. > If you want to emulate the new Anaconda Python/tk interface for Linux why > not just run it instead of re-inventing it? Why do everything just to be like Linux? Who says we can't be inventive on our own? -- |Chris Costello |Drive defensively -- buy a tank. `---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 17:50: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 177D0152A4 for ; Tue, 14 Dec 1999 17:49:59 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id RAA18213; Tue, 14 Dec 1999 17:51:31 -0800 Date: Tue, 14 Dec 1999 17:51:31 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: George Michaelson Cc: current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-Reply-To: <19991214194537.A868@holly.calldei.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, Dec 15, 1999, George Michaelson wrote: > > Why do we have to make FreeBSD more like HP-UX? the most sucky UNIX ever > > invented apart from AIX? Hmmph. When FreeBSD has a fully SMP-ized kernel, including filesystem and network stacks and device drivers, and when it has something that allows dynamic paged kernel objects and when it has a device/system configuration manager that successfully balances persistent device names with dynamic reconfiguration, *then* do the comparison. Until then, umm, your underwear is showing, jack.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 17:52:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 6C35714E7C for ; Tue, 14 Dec 1999 17:52:07 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id RAA20796; Tue, 14 Dec 1999 17:51:25 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912150151.RAA20796@gndrsh.dnsmgr.net> Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) In-Reply-To: <199912150139.BAA01185@hak.lan.Awfulhak.org> from Brian Somers at "Dec 15, 1999 01:39:28 am" To: brian@Awfulhak.org (Brian Somers) Date: Tue, 14 Dec 1999 17:51:25 -0800 (PST) Cc: abial@webgiro.com (Andrzej Bialecki), billf@chc-chimes.com (Bill Fumerola), louie@TransSys.COM (Louis A. Mamakos), current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org X-Mailer: ELM [version 2.4ME+ PL54 (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 > [.....] > > On a related subject: don't you think it's high time to end up this > > madness with MAKEDEV being a shell script, and reimplement it in C? Today, > [.....] > *cough*DEVFS*cough* Yea... been hearing that for 4 years... one of it's big short comings is that it needs a persistent backing store for this. Sounds like this C program could fullfill one of the missing parts of devfs :-) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 17:54:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id BC7D0152DD for ; Tue, 14 Dec 1999 17:54:16 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id MAA01007; Wed, 15 Dec 1999 12:22:42 +1030 (CST) (envelope-from newton) Date: Wed, 15 Dec 1999 12:22:41 +1030 From: Mark Newton To: Brian Somers Cc: Andrzej Bialecki , Bill Fumerola , "Louis A. Mamakos" , current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) Message-ID: <19991215122241.A982@internode.com.au> References: <199912150139.BAA01185@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199912150139.BAA01185@hak.lan.Awfulhak.org> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 01:39:28AM +0000, Brian Somers wrote: > [.....] > > On a related subject: don't you think it's high time to end up this > > madness with MAKEDEV being a shell script, and reimplement it in C? Today, > [.....] > *cough*DEVFS*cough* Gesunteit. - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 18: 1:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from swan.en-bio.com.au (swan.en-bio.com.au [203.35.254.3]) by hub.freebsd.org (Postfix) with ESMTP id 76EE214A1D for ; Tue, 14 Dec 1999 18:01:17 -0800 (PST) (envelope-from Tony.Maher@eBioinformatics.com) Received: from shad.internal.en-bio (www-cache.en-bio.com.au [203.35.254.2]) by swan.en-bio.com.au (8.9.1a/8.9.1) with ESMTP id NAA29712 for ; Wed, 15 Dec 1999 13:01:13 +1100 Received: (from tonym@localhost) by shad.internal.en-bio (8.9.1b+Sun/8.9.1) id NAA00195 for freebsd-current@FreeBSD.ORG; Wed, 15 Dec 1999 13:00:46 +1100 (EST) Date: Wed, 15 Dec 1999 13:00:46 +1100 (EST) From: Tony Maher Message-Id: <199912150200.NAA00195@shad.internal.en-bio> To: freebsd-current@FreeBSD.ORG Subject: Re: Speaking of moving files Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A person who really knew fsdb could do it /bin/fsdb, infact it's And for everyone else ;-) WARNING Use this tool with extreme caution--you can damage an FFS file system beyond what fsck(8) can repair. tonym To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 18: 9: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7ABB814C9C for ; Tue, 14 Dec 1999 18:09:00 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id SAA18635; Tue, 14 Dec 1999 18:08:59 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA99754; Tue, 14 Dec 1999 18:08:59 -0800 (PST) (envelope-from obrien) Date: Tue, 14 Dec 1999 18:08:59 -0800 From: "David O'Brien" To: Chris Piazza Cc: Pascal Hofstee , freebsd-current@FreeBSD.ORG Subject: Re: configure problems Message-ID: <19991214180859.A99730@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <19991214082406.A86003@dragon.nuxi.com> <19991214150658.A722@norn.ca.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991214150658.A722@norn.ca.eu.org>; from cpiazza@jaxon.net on Tue, Dec 14, 1999 at 03:06:58PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 14, 1999 at 03:06:58PM -0800, Chris Piazza wrote: > > freebsd-current@freebsd.org is for issues surounding the bleading edge > > development in the base system. > > It *is* a problem with freebsd-current, though. See PR bin/15328. That was not obvious from the email. It still should have *started* in ports@freebsd.org. There are probably many more on -ports@ that would know about this problem than people on -current. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 18:45:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 0AE4314F77 for ; Tue, 14 Dec 1999 18:45:25 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id SAA20895; Tue, 14 Dec 1999 18:44:26 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912150244.SAA20895@gndrsh.dnsmgr.net> Subject: Re: Speaking of moving files In-Reply-To: <199912150200.NAA00195@shad.internal.en-bio> from Tony Maher at "Dec 15, 1999 01:00:46 pm" To: Tony.Maher@eBioinformatics.com (Tony Maher) Date: Tue, 14 Dec 1999 18:44:25 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 > > A person who really knew fsdb could do it /bin/fsdb, infact it's > > And for everyone else ;-) > > WARNING > Use this tool with extreme caution--you can damage an FFS file system > beyond what fsck(8) can repair. Yea.. well... fsdb /dev/rda0s1a cd /dev/ cd da0s1g chown root chgrp wheel chmod 640 q There... easy enough??? fsdb is not that big of a deal as long as you stay with the basic commands of cd, ls, chown, chmod, chgrp, rm and ln. It's the ones like uplink downlink chgen that can hose you up but good. If it looks like a shell command, smells like a shell command and the man page description reads like a command it behaves pretty much like the command. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 18:50:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from polaris.shore.net (polaris.shore.net [207.244.124.105]) by hub.freebsd.org (Postfix) with ESMTP id 105CA14E32 for ; Tue, 14 Dec 1999 18:50:32 -0800 (PST) (envelope-from ejon@colltech.com) Received: from pm4-155.port.shore.net (colltech.com) [207.244.108.155] by polaris.shore.net with esmtp (Exim) id 11y4W3-00027S-00; Tue, 14 Dec 1999 21:50:12 -0500 Message-ID: <385704A2.76A6E27A@colltech.com> Date: Tue, 14 Dec 1999 22:01:54 -0500 From: Eric Jones X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? References: <2683.945164965@zippy.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 "Jordan K. Hubbard" wrote: > > > As far as the successor to sysinstall goes, I think it would be > > nice to have both a console version and an X version, with some X > > tookit such as Lesstif or Qt, or Tcl/Tk. It could be a lot like > > RedHat's "linuxconf", where you can use it as both an installer > > or system administration tool. > > Which is about correct, though there's a volume of details behind your > conceptualization of the system in outline form there. :-) Hear hear! > > To really understand where we're trying to go, however, it's somewhat > helpful to take a good look at where we are now, e.g. stuck with our > dear friends sysinstall and the pkg_install suite. > [...] > > We also need to discuss the ways and means of creating not so much an > installer but an installation "nucleus" around which we also have a > general script execution and menu-generation framework which makes it > easy for other people to write "configurators" in secure TCL which > take on the job of configuring some utility like, say, Samba. When > you pkg_add samba.zip in such a system, it runs its configurator to > generate the initial smb.conf file but also drops a copy of the > configuration script into some special config directory under the > Networking category. Now the next time the user fires up the system > configuration tool and goes to the Networking section, they see Samba > there as a new item and clicking on it will bring up the configuration > tool again (perhaps in the same form, perhaps not). If Samba is > deleted from the system, the correspnding item goes away along with > the configuration script and I'm sure you all get the idea at this > point. No more monolithic prototypes! Framework! Frame-work! > Frame-work! [jkh jumps up on a chair and begins waving his hands > enthusiastically before losing his balance and toppling over with an > abrupt scream]. > > - Jordan A worthy manifesto if ever I've seen one. I have to add that I've been pretty well amused by the discussions of pretty GUI interfaces and how they'll attract users. My interest lies in exactly the opposite direction: I want to stick a floppy in and have a box find an install server and follow a pre-defined recipe for building itself, ala Jumpstart or Kickstart. If I'm a Systems Administrator rolling out dozens of web servers or hundreds of desktops (and I frequently am), the last thing I want to look at is a GUI, unless it helps me to build the configuration that'll be installed across a large base. If anything will drive the commercialization of FreeBSD it's manageability enhancements. So, when the framework, Frame-work! Frame-work! is being considered, please keep in mind the pre-configured one disk network install. In the meantime, I'm off to learn what sysinstall can do for me. Please keep me in mind if looking for reviewers, commentators, or (*shudder*) coders and documentors for pushing this project forward. Cheers, Eric Jones Collective Technologies is a pretty GUI. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 19: 2:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 75A1114F62 for ; Tue, 14 Dec 1999 19:02:26 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA50968; Tue, 14 Dec 1999 19:02:14 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Eric Jones Cc: current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: Your message of "Tue, 14 Dec 1999 22:01:54 EST." <385704A2.76A6E27A@colltech.com> Date: Tue, 14 Dec 1999 19:02:14 -0800 Message-ID: <50964.945226934@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My interest lies in exactly the opposite direction: I want to stick > a floppy in and have a box find an install server and follow a > pre-defined recipe for building itself, ala Jumpstart or Kickstart. And you're far from alone in wanting this, another reason I've been wanting to go to a script-based installation for some time. It's not at all difficult to imagine an installer which comes in two-part form: /stand/setup /stand/setup.tcl The latter actually containing just about *all* the user interaction and "installer behavior" that the user experiences during an installation of FreeBSD. That means that if you want to modify the installer to put "Case Western University Special Custom Installation" at the top of the first menu and add lots of distributions of purely academic (haha) interest to the appropriate submenus, it's a simple matter of mounting a floppy and editing a text file. Needless to say, this would also make translation efforts a lot easier. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 19:25:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 9C57315094 for ; Tue, 14 Dec 1999 19:25:13 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:25pWk0ErqcmhCP/QPI6ttpyOKETxyZs+@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id MAA05695 for ; Wed, 15 Dec 1999 12:25:11 +0900 (JST) 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 MAA06313; Wed, 15 Dec 1999 12:30:12 +0900 (JST) Message-Id: <199912150330.MAA06313@zodiac.mech.utsunomiya-u.ac.jp> To: freebsd-current@freebsd.org Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: syscons extension: "propellers" In-reply-to: Your message of "Tue, 14 Dec 1999 13:26:11 PST." <49477.945206771@zippy.cdrom.com> References: <49477.945206771@zippy.cdrom.com> Date: Wed, 15 Dec 1999 12:30:11 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I'm not yet 100% convinced that it would make sense to separate >> the propellers code into a module. Is 5 Kbyte of kernel code >> really that much of a problem? Please note that > >I certainly wouldn't argue this based on size, no. To understand the >point I was arguing, consider what would have been the case if the >very first screen saver had been hacked straight into syscons rather >than making it an optional component. We'd probably have 2 or 3 [...] >So I see it with "propellers" - they're an optional feature component >and there should be a way of bolting such optional features into >syscons without having to recompile the kernel. It's not a question >of size, it's a question of design and flexibility and I can argue >from such a purist's perspective because I'm not doing any of the work >involved and it's thus really easy to do so. :-) I am looking at Oliver Fromme's code. It is interesting. I am currently preparing the final stage of syscons clean-up (which was outlined a year ago), and will think about reasonably generalized way of adding extentions to syscons. Kazu PS: As for screen savers, there have been a plan to move screen savers out of the kernel to userland. A part of the necessary infrastructure is there, but it's not fininished... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 20:24: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 11BB414C46 for ; Tue, 14 Dec 1999 20:24:00 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p23-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.120]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id NAA21637; Wed, 15 Dec 1999 13:23:26 +0900 (JST) Message-ID: <38571717.F25976F7@newsguy.com> Date: Wed, 15 Dec 1999 13:20:39 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Ryan Thompson Cc: Peter Jeremy , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just to to correct a misunderstanding... Ryan Thompson wrote: > > Daniel, here, sees the X install as being "user-friendly". Is the text > based install not? Granted, it's not the point and click interface that > windows users are accustomed to, but, clearly, if users can't navigate the > menus and manage to find their way to a help menu (and don't know how to > read install documentation)... It could be reasonably argued that they are > going to experience a rude awakening when presented with the good old root > prompt. Hey, I like CUI. I'd rather install with a CUI than a GUI, all other things being equal. And besides some quirks here and there, I really like sysinstall. So what? I'm a Forth programmer. I'm the guy who wrote /boot/support.4th, and find it easy to read and understand, even long after writting it. I'm the guy who wrote the builtin wrapper code in src/sys/boot/common/interp_forth.c, though I'd prefer not to disclose that information in public. :-) But the fact is that when we get featured in a magazine article, user-friendly install == GUI. No GUI, it's not an user-friendly install. End of review. You can kick and scream all you want, that's the way it is. Either we live by these rules, or we loose. > >From a techical standpoint, yes, an X based install would be far too large > for a single floppy, even at the simplest level. AND, again, as someone > who has installed FreeBSD dozens of times on various systems, I think I > should also stress that I have NEVER installed FreeBSD from CD :-) Me neither, but CD is still the most popular installation media these days, though we, Open Source OS, probably get more network installs than CD installs. -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 20:35:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from megadodo.segNET.COM (megadodo.segNET.COM [206.34.181.3]) by hub.freebsd.org (Postfix) with ESMTP id 9144D15396 for ; Tue, 14 Dec 1999 20:35:39 -0800 (PST) (envelope-from adams@digitalspark.net) Received: from nightfall.digitalspark.net (arc6a42.bf.sover.net [209.198.85.43]) by megadodo.segNET.COM (8.9.1a/8.8.5) with ESMTP id XAA13008; Tue, 14 Dec 1999 23:35:11 -0500 (EST) Date: Tue, 14 Dec 1999 23:35:56 -0500 (EST) From: Adam Strohl To: "Daniel C. Sobral" Cc: Ryan Thompson , Peter Jeremy , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-Reply-To: <38571717.F25976F7@newsguy.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, 15 Dec 1999, Daniel C. Sobral wrote: > Hey, I like CUI. I'd rather install with a CUI than a GUI, all other > things being equal. And besides some quirks here and there, I really > like sysinstall. Its nice, but its not where it should be. > But the fact is that when we get featured in a magazine article, > user-friendly install == GUI. No GUI, it's not an user-friendly install. > End of review. You can kick and scream all you want, that's the way it > is. Either we live by these rules, or we loose. A VESA GUI based sysinstall replacement would probably be small enough to fit on a floppy, yet still have the friendlyness that a new user/reviewer would look for. If we follow jkh's outline, making another "front end target" for the script shouldn't be that hard. You have X, VESA Syscons, and Text Syscons. The script says "ok, prompt user for ", under X it opens a window, under Text some ASCII dialog, and under VESA a little window. - ----( Adam Strohl )------------------------------------------------ - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - - ----------------------------------------( DigitalSpark.NET )------- - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 21: 5:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from bs.duckland.org (apocalypse.starkreality.com [208.24.48.237]) by hub.freebsd.org (Postfix) with ESMTP id 182AE15436 for ; Tue, 14 Dec 1999 21:05:18 -0800 (PST) (envelope-from duck@duckland.org) Received: from localhost (duck@localhost) by bs.duckland.org (8.9.3/8.9.3) with ESMTP id XAA60282; Tue, 14 Dec 1999 23:04:21 -0600 (CST) (envelope-from duck@duckland.org) Date: Tue, 14 Dec 1999 23:04:21 -0600 (CST) From: "Don 'Duck' Harper" Reply-To: duck@duckland.org To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-Reply-To: <38571717.F25976F7@newsguy.com> Message-ID: X-No-Archive: yes X-WARNING: Pursuant to US Code. Title 47. Chapter 5. Subchapter X-WARNING: II. Sec. 227. any and all nonsolicited commercial E-mail X-WARNING: sent to this address is subject to a download and archival X-WARNING: fee in the amount of $500 US. E-mailing denotes acceptance X-WARNING: of these terms. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sometime Tomorrow, Daniel C. Sobral said something like this: :-)But the fact is that when we get featured in a magazine article, :-)user-friendly install == GUI. No GUI, it's not an user-friendly install. :-)End of review. You can kick and scream all you want, that's the way it :-)is. Either we live by these rules, or we loose. :-) :-)> >From a techical standpoint, yes, an X based install would be far too large :-)> for a single floppy, even at the simplest level. AND, again, as someone :-)> who has installed FreeBSD dozens of times on various systems, I think I :-)> should also stress that I have NEVER installed FreeBSD from CD :-) :-) :-)Me neither, but CD is still the most popular installation media these :-)days, though we, Open Source OS, probably get more network installs than :-)CD installs. From the linux world ( I know, bad word :), there are two distrubutions which use a GUI based install. Caldera's & Red Hat. The Red Hat is based on python, and auto-detects if the graphics card is capable of X. Then it fires up XFree86's VGA server. And it fits all this on one floppy. They do have two floppies, one for local CD/disk installs, and another for NFS/FTP/HTTP/SMB installs. So, I know it can be done. Is it worth the effort? I donno. Just a view from a FreeBSD newbie, long time Linux guy. Don -- Don Harper, RHCE, MCSE | work: duck@colltech.com cell: (512) 751-9888 Team Austin | Pager: (800) Sky-Page, pin 303-7055 Collective Technologies | http://www.colltech.com http://www.duckland.org A Pencom Company | home: duck@duckland.org | finger duck@duckland.org for PGP key He Who Dies with the Most Toys Still Dies. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 21: 7:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3BFEE1508C for ; Tue, 14 Dec 1999 21:07:34 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA26239; Tue, 14 Dec 1999 21:07:31 -0800 (PST) (envelope-from dillon) Date: Tue, 14 Dec 1999 21:07:31 -0800 (PST) From: Matthew Dillon Message-Id: <199912150507.VAA26239@apollo.backplane.com> To: "BSDman" Cc: "Poul-Henning Kamp" , "Ben Rosengart" , "Bill Fumerola" , "Louis A. Mamakos" , Subject: Re: RE: Speaking of moving files (Re: make world broken building fortunes ) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Poul-Henning Kamp wrote :> It would make more sense, considering the way FreeBSD is distributed for :> /usr/local to be a mountpoint than for /usr to be a mountpoint. :> :> /var is traditionally a mountpoint to keep the logs out of harms :> way (and vice versa), but /usr never had that level of justification. :> : :one idea about /usr is to allow the admin to mount it read-only. I tend to make /usr a separate mount point for one reason and one reason only: So root (/) can be made a small partition (64-128M) and thus be less likely to get corrupted beyond repair in a crash. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 21:11:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 558BF14C9C for ; Tue, 14 Dec 1999 21:11:15 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA51312; Tue, 14 Dec 1999 21:10:48 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Adam Strohl Cc: "Daniel C. Sobral" , Ryan Thompson , Peter Jeremy , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: Your message of "Tue, 14 Dec 1999 23:35:56 EST." Date: Tue, 14 Dec 1999 21:10:48 -0800 Message-ID: <51308.945234648@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If we follow jkh's outline, making another "front end target" for the > script shouldn't be that hard. You have X, VESA Syscons, and Text > Syscons. > > The script says "ok, prompt user for ", under X it opens a window, > under Text some ASCII dialog, and under VESA a little window. VESA syscons, either using libvgl and an array of crude widgets or something like MGR and its widget set, has long been on the wish-list but I didn't even include it in my summary since it's still very much a pipe-dream. :-) There's actually one mode you forgot, which is what I call "text mode", and that's straight ascii prompts, no CUI-style dialog boxes or anything. Think about text-to-speach devices for the blind or serial consoles attached to really *dumb* terminals. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 21:14:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id B5E2C15449 for ; Tue, 14 Dec 1999 21:14:14 -0800 (PST) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id XAA20764 for current@FreeBSD.ORG; Tue, 14 Dec 1999 23:13:36 -0600 (CST) Date: Tue, 14 Dec 1999 23:13:35 -0600 From: Tim Tsai To: current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991214231335.A20661@futuresouth.com> References: <51308.945234648@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <51308.945234648@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There's actually one mode you forgot, which is > what I call "text mode", and that's straight ascii prompts, no CUI-style > dialog boxes or anything. You can reprogram the character table and draw fairly nice looking menus in text mode. The last generations of MS-DOS based programs used them to good effect. Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 22:25:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 57B091506C for ; Tue, 14 Dec 1999 22:25:42 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA75057; Tue, 14 Dec 1999 23:25:40 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA58573; Tue, 14 Dec 1999 23:25:40 -0700 (MST) Message-Id: <199912150625.XAA58573@harmony.village.org> To: Brian Somers Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 15 Dec 1999 01:39:28 GMT." <199912150139.BAA01185@hak.lan.Awfulhak.org> References: <199912150139.BAA01185@hak.lan.Awfulhak.org> Date: Tue, 14 Dec 1999 23:25:40 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912150139.BAA01185@hak.lan.Awfulhak.org> Brian Somers writes: : *cough*DEVFS*cough* devfs*D* Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 23:10:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.worldwide.lemis.com (mojave.lemis.com [192.109.197.162]) by hub.freebsd.org (Postfix) with ESMTP id 1FD061546C for ; Tue, 14 Dec 1999 23:10:34 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id GAA00480; Wed, 15 Dec 1999 06:52:32 +1100 (EST) (envelope-from grog) Date: Wed, 15 Dec 1999 06:52:32 +1100 From: Greg Lehey To: Soren Schmidt Cc: joeo@nks.net, freebsd-current@FreeBSD.ORG Subject: Fallback to PIO (was: Errors from the ata disk driver) Message-ID: <19991215065232.A456@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <199912130803.JAA33772@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912130803.JAA33772@freebsd.dk>; from sos@freebsd.dk on Mon, Dec 13, 1999 at 09:03:16AM +0100 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Monday, 13 December 1999 at 9:03:16 +0100, Soren Schmidt wrote: > It seems joeo@nks.net wrote: >> Will the backdown to PIO mode be permanent till the next reboot of the >> machine, or will the driver be able to attempt to return to DMA mode after >> a timeout period. I'm only seeing these errors under really heavy disk >> activity (mutlitple nfs readers and writers plus rsync/mirror jobs to the >> vinum volume in question). > > The fallback is permanent, but it only occurs after 3 retries on the > failed request. If it fails 3 times in a row, there is something > really wrong on that channel, ie bad cableing etc etc... Wouldn't it be possible to find some way to manually reenable DMA? Having to reboot seems rather hard. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 23:10:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.worldwide.lemis.com (mojave.lemis.com [192.109.197.162]) by hub.freebsd.org (Postfix) with ESMTP id A53161548E for ; Tue, 14 Dec 1999 23:10:37 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id VAA00618; Mon, 13 Dec 1999 21:03:24 -0800 (PST) (envelope-from grog) Date: Mon, 13 Dec 1999 21:03:24 -0800 From: Greg Lehey To: Soren Schmidt Cc: Dieter Rothacker , current@FreeBSD.ORG Subject: Re: FYI: Benchmarked ATA driver Message-ID: <19991213210324.A580@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <199912111755.SAA04647@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912111755.SAA04647@freebsd.dk>; from sos@freebsd.dk on Sat, Dec 11, 1999 at 06:55:27PM +0100 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Saturday, 11 December 1999 at 18:55:27 +0100, Soren Schmidt wrote: > It seems Dieter Rothacker wrote: >> Hi, >> >> here I have my Bonnie++ 0.99d output: >> machine is a P233MMX, 128MB, Hotrod66 with IBM DJNA-352500. >> (One slice, one partition UFS) >> -- >> Version 0.99d ------Sequential Output------ --Sequential Input- --Random- >> -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- >> Machine MB K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP >> Unknown 256 6578 91 13484 71 3976 27 6539 92 13550 50 297.4 8 >> ------Sequential Create------ --------Random Create-------- >> -Create-- --Stat--- -Delete-- -Create-- --Stat--- -Delete-- >> files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP >> 30 121 83 7781 67 1079 92 135 91 184 99 80 25 >> -- >> This really rocks, and the driver is perfectly stable. Very good work. > > Thanks, very much appreciated!! It would be nice to see the results with a benchmark which bypasses buffer cache, such as rawio. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 23:11:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.worldwide.lemis.com (mojave.lemis.com [192.109.197.162]) by hub.freebsd.org (Postfix) with ESMTP id 49DB215515 for ; Tue, 14 Dec 1999 23:11:33 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id SAA00880; Mon, 13 Dec 1999 18:46:34 -0800 (PST) (envelope-from grog) Date: Mon, 13 Dec 1999 18:46:34 -0800 From: Greg Lehey To: Bill Fumerola Cc: current@FreeBSD.ORG Subject: Re: vinum start needs block device Message-ID: <19991213184634.S333@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <19991212154736.8295D1CA0@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from billf@chc-chimes.com on Mon, Dec 13, 1999 at 06:18:14PM -0500 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Monday, 13 December 1999 at 18:18:14 -0500, Bill Fumerola wrote: > On Sun, 12 Dec 1999, Peter Wemm wrote: > >>> - if (drive->vp->v_type != VBLK) { /* only consider bl >> ock devices */ >>> + if (!vn_isdisk(drive->vp)) { /* only consider bl > > Note: this fixes some recent problems (Hi Greg!) that I've been > having. Really? I thought they were more serious. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 23:11:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id D304215541 for ; Tue, 14 Dec 1999 23:11:39 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA08425; Wed, 15 Dec 1999 08:11:18 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912150711.IAA08425@freebsd.dk> Subject: Re: Fallback to PIO (was: Errors from the ata disk driver) In-Reply-To: <19991215065232.A456@mojave.worldwide.lemis.com> from Greg Lehey at "Dec 15, 1999 06:52:32 am" To: grog@lemis.com (Greg Lehey) Date: Wed, 15 Dec 1999 08:11:18 +0100 (CET) Cc: joeo@nks.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Greg Lehey wrote: > On Monday, 13 December 1999 at 9:03:16 +0100, Soren Schmidt wrote: > > It seems joeo@nks.net wrote: > >> Will the backdown to PIO mode be permanent till the next reboot of the > >> machine, or will the driver be able to attempt to return to DMA mode after > >> a timeout period. I'm only seeing these errors under really heavy disk > >> activity (mutlitple nfs readers and writers plus rsync/mirror jobs to the > >> vinum volume in question). > > > > The fallback is permanent, but it only occurs after 3 retries on the > > failed request. If it fails 3 times in a row, there is something > > really wrong on that channel, ie bad cableing etc etc... > > Wouldn't it be possible to find some way to manually reenable DMA? > Having to reboot seems rather hard. The retry count is pr request, and if the same request fails 3 times in a row, belive me you dont want to run DMA on that drive :) -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 14 23:24:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.zuhause.org (c2-178.xtlab.com [205.215.217.178]) by hub.freebsd.org (Postfix) with ESMTP id 014BF1545A for ; Tue, 14 Dec 1999 23:24:43 -0800 (PST) (envelope-from bruce@zuhause.mn.org) Received: by mail.zuhause.org (Postfix, from userid 1001) id BE6397C34; Wed, 15 Dec 1999 01:24:40 -0600 (CST) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14423.16952.518144.298755@celery.zuhause.org> Date: Wed, 15 Dec 1999 01:24:40 -0600 (CST) To: freebsd-current@freebsd.org Subject: Upgrading from a not-very-current current X-Mailer: VM 6.72 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you want to complain that I shouldn't be running -current in the first place, don't bother. I upgraded because -stable doesn't support SMP + fork with shared memory. I want to upgrade from a pre-signal changes -current to -current (I'm having problems with a pnic card getting corrupted mbufs and I want to see if Bill Paul's new driver works better), and I have a simple question: I know that I need to build the tools for config, and build a new kernel, and reboot it before doing a make world. My question is, after booting the new kernel, do I run MAKEDEV immediately, or do I run make world before runnning MAKEDEV? Would it be prudent to disable softupdates until after I'm done upgrading? Would it be simpler to install from the latest -current snap? Thanks, Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 0: 3:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 12B0C153C9; Wed, 15 Dec 1999 00:03:04 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11y9Oj-0001bC-00; Wed, 15 Dec 1999 10:02:57 +0200 From: Sheldon Hearn To: Nik Clayton Cc: oliver.fromme@heim3.tu-clausthal.de, freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" In-reply-to: Your message of "Tue, 14 Dec 1999 15:13:17 GMT." <19991214151317.B73952@catkin.nothing-going-on.org> Date: Wed, 15 Dec 1999 10:02:57 +0200 Message-ID: <6149.945244977@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 14 Dec 1999 15:13:17 GMT, Nik Clayton wrote: > We need more than just an ASCII capture. Grabbing the colour information > is also very useful. This lets you make full colour pictures of things > like sysinstall. Sure, I was just explaining what lots of users have asked for. I'm not saying that's _all_ we could possibly want. :-) later, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 0:16: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 85CCE154A1 for ; Wed, 15 Dec 1999 00:15:59 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA51851; Wed, 15 Dec 1999 00:15:46 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: chris@calldei.com Cc: Donn Miller , Eric Jones , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: Your message of "Tue, 14 Dec 1999 17:37:14 CST." <19991214173714.W868@holly.calldei.com> Date: Wed, 15 Dec 1999 00:15:46 -0800 Message-ID: <51847.945245746@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is Qt going to be put into the base system in this case? If > I can wrestle along with figuring out a few little problems with > Qt (ones that I could even somehow more easily solve with > Motif!), then I'll continue to develop my system administration > tool(s) with it. No, I don't envision that Qt would go into the system at any point, in fact. I figure that the minimal infrastructure support to make setup and new package_install work will be part of FreeBSD (e.g. tcl and turbovision would probably replace at least libdialog) and then Qt will be an optional component. As previously mentioned, I'd intend the default setup to be dynamically linked and just dlopen() the Qt library if a suitable DISPLAY and the Qt libraries could be found. Otherwise, it would fall back to Turbovison. Since the floppy version needs to be linked static, that would support only the CUI interface. That said, one of the installer options will be to chain to a more capable installer if the media for same (and all of its dependencies) can be found. So you could use the CUI version only long enough to select "Desktop install" and then the whole VGA16 X server dance would begin, culminating in the execution of a Qt-capable version of setup. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 0:41:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from circe.tops.net (circe.tops.net [194.162.222.100]) by hub.freebsd.org (Postfix) with ESMTP id BBA8414C9C for ; Wed, 15 Dec 1999 00:41:35 -0800 (PST) (envelope-from lederer@bonn-online.com) Received: from bonn-online.com (ppp148.dialin.bonn-online.com [194.162.223.148]) by circe.tops.net (8.9.3/8.9.3) with ESMTP id JAA17169 for ; Wed, 15 Dec 1999 09:41:31 +0100 Message-ID: <3857545A.201ED3CC@bonn-online.com> Date: Wed, 15 Dec 1999 09:42:02 +0100 From: Sebastian Lederer X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: sysinstall: is it really at the end of its lifecycle? References: <2177.945155945@zippy.cdrom.com> <3855F364.E66EC87B@cvzoom.net> <99Dec15.073843est.40325@border.alcanet.com.au> <3856BD33.5DE1AB48@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > > Peter Jeremy wrote: > > > > Firstly, size: One of sysinstall's requirements is that it fit (along > > with a variety of other related commands) onto a floppy disk. Last > > time I checked, the /stand bundle (sysinstall + friends) was ~640K. > > The smallest X-server (XF86_VGA16) is 1.7MB (plus libraries). I don't > > have either Qt or Lesstif installed, but from previous dealings with > > Motif, it's several times the size of the Xserver. Unless we want to > > mandate the use of ZIP drives (or similar) as FreeBSD install > > floppies, we're limited to a syscons (or VTxxx) sysinstall. > > There is a device called cd-rom which more or less qualifies for the "or > similar" category you mention. It happens to be the most popular > installation media nowadays (though it probably comes second as far as > FreeBSD is concerned). > [...] Actually I started to write an X11-based installer some time ago. It was designed to boot off a CD, auto-detect mouse and graphics card and then start the appropriate X-Server in 640x480 mode. Then a series of dialogs popped up, asking the most important system parameters like which disk to install on, internet parameters and so on. Unto that point, it actually worked. You can see how it looked like at http://www.stud.fh-rhein-sieg.de/~sleder2s/totali.html . I ran out of spare time (and out of CD-Rs), however, when debugging the shell script that was supposed to do the actual install. Regards, Sebastian Lederer -- Sebastian Lederer lederer@bonn-online.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 0:50:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 05B1F152C9 for ; Wed, 15 Dec 1999 00:49:56 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11yA84-0001tn-00 for freebsd-current@FreeBSD.ORG; Wed, 15 Dec 1999 10:49:48 +0200 From: Sheldon Hearn To: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" In-reply-to: Your message of "Tue, 14 Dec 1999 21:26:04 +0100." <199912142026.VAA29478@dorifer.heim3.tu-clausthal.de> Date: Wed, 15 Dec 1999 10:49:48 +0200 Message-ID: <7302.945247788@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 14 Dec 1999 21:26:04 +0100, Oliver Fromme wrote: > I'm not yet 100% convinced that it would make sense to separate > the propellers code into a module. Is 5 Kbyte of kernel code > really that much of a problem? No, but think ahead, into a future where we use a teeny tiny kernel into which we plug lots of modules. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 0:58:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 0BE291539C for ; Wed, 15 Dec 1999 00:58:26 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11yAFp-0001xQ-00; Wed, 15 Dec 1999 10:57:49 +0200 From: Sheldon Hearn To: Peter Jeremy Cc: Marcel Moolenaar , freebsd-current@FreeBSD.ORG Subject: Re: make world broken building fortunes In-reply-to: Your message of "Wed, 15 Dec 1999 06:21:48 +1100." <99Dec15.061331est.40325@border.alcanet.com.au> Date: Wed, 15 Dec 1999 10:57:49 +0200 Message-ID: <7527.945248269@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 15 Dec 1999 06:21:48 +1100, Peter Jeremy wrote: > @@ -344,7 +352,7 @@ > tools:: > .for _tool in ${_strfile} ${_aout_tools} usr.bin/gensetdefs \ > gnu/usr.bin/binutils usr.bin/objformat usr.bin/yacc usr.bin/colldef \ > - gnu/usr.bin/bison gnu/usr.bin/cc > + gnu/usr.bin/bison gnu/usr.bin/cc gnu/usr.bin/texinfo > cd ${.CURDIR}/${_tool}; \ > ${MAKE} obj; \ > ${MAKE} depend; \ Presumably this hunk is a stray fix for something other than the fortune database? :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 1: 9:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 08E4F151B4 for ; Wed, 15 Dec 1999 01:09:40 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11yAPQ-00021m-00; Wed, 15 Dec 1999 11:07:44 +0200 From: Sheldon Hearn To: Bruce Albrecht Cc: freebsd-current@FreeBSD.ORG Subject: Re: Upgrading from a not-very-current current In-reply-to: Your message of "Wed, 15 Dec 1999 01:24:40 CST." <14423.16952.518144.298755@celery.zuhause.org> Date: Wed, 15 Dec 1999 11:07:43 +0200 Message-ID: <7797.945248863@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 15 Dec 1999 01:24:40 CST, Bruce Albrecht wrote: > Would it be simpler to install from the latest -current snap? Wait a few days. We're almost at the point where current CURRENT can be built on pre-sigset_t-changes CURRENT. Watch your cvs-all mail. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 1:10:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from nic-31-c23-178.mn.mediaone.net (nic-31-c23-178.mn.mediaone.net [24.31.23.178]) by hub.freebsd.org (Postfix) with ESMTP id 0E703151B4 for ; Wed, 15 Dec 1999 01:10:01 -0800 (PST) (envelope-from jstock@winterzone.com) Received: from localhost (localhost [127.0.0.1]) by nic-31-c23-178.mn.mediaone.net (8.9.3/8.9.3) with ESMTP id DAA00326 for ; Wed, 15 Dec 1999 03:09:10 -0600 (CST) (envelope-from jstock@winterzone.com) Date: Wed, 15 Dec 1999 03:09:10 -0600 (CST) From: "Jeremy L. Stock" X-Sender: jstock@nic-31-c23-178.mn.mediaone.net To: current@FreeBSD.ORG Subject: Problem with sbc driver and/or newpcm 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 The sbc driver seems to correctly detect my soundcard for the first time since the introduction of newpcm but I don't actually get sound out of it. I think the IRQ it's detecting might be wrong. Both Windows 98 and the old pcm driver always used IRQ 10. Unfortunately my BIOS is too brain-damaged to report IRQ's for ISA devices at boot so I can't be sure. I have tried options PNPBIOS as well as trying to specify irq 10 to sbc to no avail. I'd appreciate any assistance. Here's output from dsmesg and pnpinfo: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-19991214-CURRENT #0: Wed Dec 15 02:44:58 CST 1999 root@nic-31-c23-178.mn.mediaone.net:/usr/src/sys/compile/NIC Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 350796172 Hz CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 134217728 (131072K bytes) avail memory = 127004672 (124028K bytes) Preloaded elf kernel "kernel" at 0xc02ac000. md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 chip1: at device 3.0 on pci0 isab0: at device 7.0 on pci0 isa0: on isab0 xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 9 at device 9.0 on pci0 xl0: Ethernet address: 00:50:da:24:3a:c5 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc0: irq 9 at device 10.0 on pci0 ahc0: aic7850 Single Channel A, SCSI Id=7, 3/255 SCBs vga-pci0: irq 11 at device 11.0 on pci0 ata-pci0: irq 0 at device 15.0 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata-isa0: already registered as ata0 ata-isa1: already registered as ata1 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/7 bytes threshold plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,3 on isa0 pcm0: on sbc0 unknown0: at port 0x201 on isa0 ad0: ATA-4 disk at ata0 as master ad0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad1: ATA-4 disk at ata0 as slave ad1: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 acd0: CDROM drive at ata1 as master acd0: read 6890KB/s (6890KB/s), 120KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad1s1a cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID CTL00f0 (0xf0008c0e), Serial Number 0xffffffff PnP Version 1.0, Vendor Version 16 Device Description: Creative ViBRA16X PnP Logical Device ID: CTL0043 0x43008c0e #0 Device Description: Audio TAG Start DF Good Configuration IRQ: 5 - only one type (true/edge) DMA: channel(s) 1 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x220, alignment 0x1, len 0x10 [16-bit addr] I/O Range 0x330 .. 0x330, alignment 0x1, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] TAG Start DF Sub-optimal Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x10, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x394, alignment 0x4, len 0x4 [16-bit addr] TAG Start DF Sub-optimal Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] TAG End DF Logical Device ID: CTL7005 0x05708c0e #1 Compatible Device ID: PNPb02f (2fb0d041) Device Description: Game TAG Start DF Good Configuration I/O Range 0x201 .. 0x201, alignment 0x1, len 0x1 [16-bit addr] TAG Start DF Acceptable Configuration I/O Range 0x200 .. 0x20f, alignment 0x1, len 0x1 [16-bit addr] TAG End DF End Tag Successfully got 48 resources, 2 logical fdevs -- card select # 0x0001 CSN CTL00f0 (0xf0008c0e), Serial Number 0xffffffff Logical device #0 IO: 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 IRQ 5 0 DMA 1 3 IO range check 0x00 activate 0x01 Logical device #1 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 -- Jeremy L. Stock ICQ 46329337 Fax # 612-629-6540 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 1:30:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.194]) by hub.freebsd.org (Postfix) with ESMTP id 60943153B8 for ; Wed, 15 Dec 1999 01:30:54 -0800 (PST) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.9.3/8.7.3) id KAA60599; Wed, 15 Dec 1999 10:30:49 +0100 (MET) Date: Wed, 15 Dec 1999 10:30:49 +0100 From: Martin Cracauer To: Marcel Moolenaar Cc: current@FreeBSD.ORG Subject: Re: Broken sh(1)? Message-ID: <19991215103049.A60044@cons.org> References: <38564693.EE9DB4EC@scc.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <38564693.EE9DB4EC@scc.nl>; from Marcel Moolenaar on Tue, Dec 14, 1999 at 02:30:59PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <38564693.EE9DB4EC@scc.nl>, Marcel Moolenaar wrote: > Hi, > > Try the following shell script (taken from a buildworld): > > #!/bin/sh -ev > cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/i386 \ > PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\ > /usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:\ > /usr/games:/usr/local/bin:/usr/X11R6/bin:/home/marcel/bin \ > INSTALL="sh /usr/src/tools/install.sh" \ > DESTDIR=/usr/obj/usr/src/i386 TARGET_ARCH=i386 \ > MACHINE_ARCH=i386 make -f Makefile.inc1 -DNOMAN -DNOINFO \ > -DNO_FORTRAN -DNO_GDB tools > cd /usr/src; make -f Makefile.inc1 par-obj You mix up variable settings for just one command vs. permanent ones; export VAR=foo VAR=bar sh -c 'echo $VAR' echo $VAR ==> bar foo This is correct, the second line's variable settings only affect the command behind it. The next command will have the original value restored. > I always get the following: > > ===> c++filt > sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 555 \ > c++filt /usr/obj/usr/src/i386/usr/libexec/elf > ===> doc > ===> cc1obj > sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 555 \ > cc1obj /usr/obj/usr/src/i386/usr/libexec > > cd /usr/src; make -f Makefile.inc1 par-obj > ./x.sh: make: not found > > ^^^^^^^^^^^^^^^ > At this point PATH contains /usr/bin, so I don't think it's PATH > related. No, $PATH is restored to what is was before the first make command. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 1:35:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.194]) by hub.freebsd.org (Postfix) with ESMTP id A05DC153ED for ; Wed, 15 Dec 1999 01:35:09 -0800 (PST) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.9.3/8.7.3) id KAA60631; Wed, 15 Dec 1999 10:34:44 +0100 (MET) Date: Wed, 15 Dec 1999 10:34:44 +0100 From: Martin Cracauer To: Marcel Moolenaar Cc: Sheldon Hearn , current@FreeBSD.ORG Subject: Re: sh(1) broken caching [was: Re: Broken sh(1)?] Message-ID: <19991215103444.B60044@cons.org> References: <712.945183175@axl.noc.iafrica.com> <38565DEA.4487DF53@scc.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <38565DEA.4487DF53@scc.nl>; from Marcel Moolenaar on Tue, Dec 14, 1999 at 04:10:34PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <38565DEA.4487DF53@scc.nl>, Marcel Moolenaar wrote: > Sheldon Hearn wrote: > > > > On Tue, 14 Dec 1999 15:42:11 +0100, Marcel Moolenaar wrote: > > > > > > You set all those variables for the first make command, but not for the > > > > second. What did you expect to happen? > > > > > > That make(1) would execute. > > > > But what was the PATH set to _before_ you set it for the first execution > > of make? That's what's important, surely? > > It is. Try this: > > scones% sh > % echo $PATH > /sbin:/bin:/usr/sbin:/usr/bin:.... > % hash -v > builtin hash > builtin echo > % which ls > /bin/ls > % hash -v > builtin hash > builtin echo > /usr/bin/which > % PATH=/foo:/bar:/bin ls This line does *not* change $PATH for the next lines. > > % hash -v > builtin hash > builtin echo > /usr/bin/which > /usr/sbin/ls > ^^^^^^^^^^^^ Caching index based on temp. path!!!! > % ls > ls: not found $PATH is still /sbin:/bin:/usr/sbin:/usr/bin:.... Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 1:41:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 9B3211548E for ; Wed, 15 Dec 1999 01:41:40 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id KAA02986; Wed, 15 Dec 1999 10:41:05 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199912150244.SAA20895@gndrsh.dnsmgr.net> References: <199912150244.SAA20895@gndrsh.dnsmgr.net> Date: Wed, 15 Dec 1999 09:56:35 +0100 To: "Rodney W. Grimes" , Tony.Maher@eBioinformatics.com (Tony Maher) From: Brad Knowles Subject: Re: Speaking of moving files Cc: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 6:44 PM -0800 1999/12/14, Rodney W. Grimes wrote: > There... easy enough??? fsdb is not that big of a deal as long as you > stay with the basic commands of cd, ls, chown, chmod, chgrp, rm and ln. > It's the ones like uplink downlink chgen that can hose you up but good. > > If it looks like a shell command, smells like a shell command and the > man page description reads like a command it behaves pretty much like > the command. I had always been terrified to even look at the man page for fsdb, fearing that even that amount of arrogance could permanently hose up the filesystem. ;-) Seriously, thanks for the enlightenment! Next time I'm on a seriously hosed system, perhaps this information can be used to help me save my butt. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 1:46:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id A51B0153CE for ; Wed, 15 Dec 1999 01:46:51 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11yB0v-000Bk1-00; Wed, 15 Dec 1999 09:46:29 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id KAA09729; Wed, 15 Dec 1999 10:46:49 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <38576389.567EEE47@scc.nl> Date: Wed, 15 Dec 1999 10:46:49 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Martin Cracauer Cc: current@FreeBSD.ORG Subject: Re: Broken sh(1)? References: <38564693.EE9DB4EC@scc.nl> <19991215103049.A60044@cons.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Martin Cracauer wrote: > You mix up variable settings for just one command vs. permanent ones; > export VAR=foo > VAR=bar sh -c 'echo $VAR' > echo $VAR > ==> > bar > foo > > This is correct, the second line's variable settings only affect the > command behind it. The next command will have the original value > restored. I know this is correct and I'm even depending on it. The problem is that sh's caching has been poluted in such a way it can't recover. > > cd /usr/src; make -f Makefile.inc1 par-obj > > ./x.sh: make: not found > > > > ^^^^^^^^^^^^^^^ > > At this point PATH contains /usr/bin, so I don't think it's PATH > > related. > > No, $PATH is restored to what is was before the first make command. Yes, I know and as I said it contains /usr/bin. See other mail. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 1:47:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from kiew.egd.igd.fhg.de (kiew.egd.igd.fhg.de [192.102.170.32]) by hub.freebsd.org (Postfix) with ESMTP id AA66C14C01 for ; Wed, 15 Dec 1999 01:47:36 -0800 (PST) (envelope-from runge@rostock.zgdv.de) Received: from rostock.zgdv.de (kingfisher.egd.igd.fhg.de [153.96.43.107]) by kiew.egd.igd.fhg.de (Netscape Messaging Server 3.6) with ESMTP id AAA4059 for ; Wed, 15 Dec 1999 10:46:13 +0100 Message-ID: <38576264.7D33C327@rostock.zgdv.de> Date: Wed, 15 Dec 1999 10:41:56 +0100 From: "Thomas Runge" Organization: http://www.rostock.zgdv.de X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 Cc: current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? References: <3856BD33.5DE1AB48@newsguy.com> <19991215105736.A467@internode.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This all sounds like a decision, whether we want to be a desktop or a server-only system. For mainly server-oriented, the "install source to update" or console-based setups are quite enough, because the system will most probably administraded by people, that know, what they are doing. But if we want to compete with Linux (and the development of the Linuxulator makes that impression) and if we want to get some market share, we have to be more "user friendly", which means, installs must be easy and *smile* eye-catching. Sorry, but thats the way it is. Thats why Suse is more used than Debian. Thats why some people still prefer Windows over Unix even for servers. So, we have a very good server OS, let's focus a little bit more on the desktop. -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 1:51:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id E94F115244; Wed, 15 Dec 1999 01:51:03 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id dBF9oqo12058; Wed, 15 Dec 1999 11:50:52 +0200 (SAST) Message-Id: <199912150950.dBF9oqo12058@gratis.grondar.za> To: sos@freebsd.org Cc: current@freebsd.org Subject: YA Non-DMA IDE controller... Date: Wed, 15 Dec 1999 11:50:51 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi My Toshiba Libretto has dogslow disk; here is the probe message. Any chances of getting this one to work in DMA mode? ad0: ATA-4 disk at ata0 as master ad0: 4126MB (8452080 sectors), 8944 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, PIO M To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 1:53: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 9B98314C01 for ; Wed, 15 Dec 1999 01:52:57 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id KAA18299 for current@FreeBSD.org; Wed, 15 Dec 1999 10:49:53 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Wed, 15 Dec 1999 10:49:48 +0100 From: Marcel Moolenaar Message-ID: <3857643C.D1349A70@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <712.945183175@axl.noc.iafrica.com>, <19991215103444.B60044@cons.org> Subject: Re: sh(1) broken caching [was: Re: Broken sh(1)?] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Martin Cracauer wrote: > > In <38565DEA.4487DF53@scc.nl>, Marcel Moolenaar wrote: > > Sheldon Hearn wrote: > > > > > > On Tue, 14 Dec 1999 15:42:11 +0100, Marcel Moolenaar wrote: > > > > > > > > You set all those variables for the first make command, but not for the > > > > > second. What did you expect to happen? > > > > > > > > That make(1) would execute. > > > > > > But what was the PATH set to _before_ you set it for the first execution > > > of make? That's what's important, surely? > > > > It is. Try this: > > > > scones% sh > > % echo $PATH > > /sbin:/bin:/usr/sbin:/usr/bin:.... > > % hash -v > > builtin hash > > builtin echo > > % which ls > > /bin/ls > > % hash -v > > builtin hash > > builtin echo > > /usr/bin/which > > % PATH=/foo:/bar:/bin ls > > This line does *not* change $PATH for the next lines. *I KNOW* geez... > > > > % hash -v > > builtin hash > > builtin echo > > /usr/bin/which > > /usr/sbin/ls > > ^^^^^^^^^^^^ Caching index based on temp. path!!!! > > % ls > > ls: not found > > $PATH is still /sbin:/bin:/usr/sbin:/usr/bin:.... Exactly, so why can't it find ls then? -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 1:55:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id E088114DE8; Wed, 15 Dec 1999 01:55:42 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA46772; Wed, 15 Dec 1999 10:55:15 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912150955.KAA46772@freebsd.dk> Subject: Re: YA Non-DMA IDE controller... In-Reply-To: <199912150950.dBF9oqo12058@gratis.grondar.za> from Mark Murray at "Dec 15, 1999 11:50:51 am" To: mark@grondar.za (Mark Murray) Date: Wed, 15 Dec 1999 10:55:15 +0100 (CET) Cc: sos@freebsd.org, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Mark Murray wrote: > Hi > > My Toshiba Libretto has dogslow disk; here is the probe message. Any > chances of getting this one to work in DMA mode? > > ad0: ATA-4 disk at ata0 as master > ad0: 4126MB (8452080 sectors), 8944 cyls, 15 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, PIO Could you send me a verbose boot from it, and I'll take a look... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 1:57:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.194]) by hub.freebsd.org (Postfix) with ESMTP id A2713153C9 for ; Wed, 15 Dec 1999 01:57:51 -0800 (PST) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.9.3/8.7.3) id KAA61476; Wed, 15 Dec 1999 10:57:28 +0100 (MET) Date: Wed, 15 Dec 1999 10:57:28 +0100 From: Martin Cracauer To: Marcel Moolenaar Cc: Sheldon Hearn , current@FreeBSD.ORG Subject: Re: sh(1) broken caching [was: Re: Broken sh(1)?] Message-ID: <19991215105728.A61202@cons.org> References: <712.945183175@axl.noc.iafrica.com> <38565DEA.4487DF53@scc.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <38565DEA.4487DF53@scc.nl>; from Marcel Moolenaar on Tue, Dec 14, 1999 at 04:10:34PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, the problem is real. BTW, its worse: #! /bin/sh hash -v PATH=/sbin:/bin PATH=/foo:/bar:/bin ls hash -v ls => coredump Working on it. -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 2: 3: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 6AE95153C1; Wed, 15 Dec 1999 02:02:41 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id dBFA2Ro12236; Wed, 15 Dec 1999 12:02:27 +0200 (SAST) Message-Id: <199912151002.dBFA2Ro12236@gratis.grondar.za> To: Brian Fundakowski Feldman Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: OpenSSL update Date: Wed, 15 Dec 1999 12:02:27 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Sounds great. I hope this means I get to import OpenSSH! Hell, yes! I reckon it may be better to let me do it; that way I can get Internat and Freefall synchronised. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 2: 3:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 9E02315371; Wed, 15 Dec 1999 02:01:43 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id dBFA1Mo12224; Wed, 15 Dec 1999 12:01:22 +0200 (SAST) Message-Id: <199912151001.dBFA1Mo12224@gratis.grondar.za> To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: OpenSSL update Date: Wed, 15 Dec 1999 12:01:20 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Sound okay to everyone? Fine by me! :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 2: 8:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 857991539C; Wed, 15 Dec 1999 02:08:45 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA45980; Wed, 15 Dec 1999 10:18:14 GMT (envelope-from dfr@nlsystems.com) Date: Wed, 15 Dec 1999 10:18:13 +0000 (GMT) From: Doug Rabson To: Andrew Gallatin Cc: freebsd-current@freebsd.org, tanimura@freebsd.org Subject: Re: ESS1688 newpcm support, soundblaster panics at boot In-Reply-To: <14422.37057.798245.620736@grasshopper.cs.duke.edu> 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, 14 Dec 1999, Andrew Gallatin wrote: > > I have an old, wheezing Dell Lattitude LM with an ESS1688 sound chip. > (specs at http://support.dell.com/docs/systems/pespmmx/specs.htm) > > I have managed to get newpcm to find the 1688 via 'options PNPBIOS' > and the following patch: I've added this to my sources. I'll commit it after I get the rest working. > > However, the machine now panics on boot in sbchan_init(), at line 821 > of sb.c with a page fault on access to virtual address 0x14: > > I strongly suspect that this is due to the fact that this card has > only 1 dma channel. I suspect the panic is caused by > rman_get_start(sb->drq2) when sb->drq2 is null. > > Does newpcm even support simplex operations on soundblaster chips? I > ask because I simply could not get simplex operations to work on my > wss cards, so I suspect that simplex operation is simply not well > tested. It is supposed to support simplex but that support has changed recently so perhaps it broke. I already have a report that the ESS1888 is broken at the moment and I will be fixing it as soon as I find a spare couple of hours to tackle it (I have an ESS1888 in my miata). > > Can anybody who is more familiar with newpcm please point me in the > right direction? Not sure where to look yet. Something is probably passing a NULL channel. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 2:11:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 49263153B0 for ; Wed, 15 Dec 1999 02:11:17 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA46184; Wed, 15 Dec 1999 10:20:36 GMT (envelope-from dfr@nlsystems.com) Date: Wed, 15 Dec 1999 10:20:36 +0000 (GMT) From: Doug Rabson To: "Jeremy L. Stock" Cc: current@freebsd.org Subject: Re: Problem with sbc driver and/or newpcm 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, 15 Dec 1999, Jeremy L. Stock wrote: > The sbc driver seems to correctly detect my soundcard for the first time > since the introduction of newpcm but I don't actually get sound out of it. > I think the IRQ it's detecting might be wrong. Both Windows 98 and the old > pcm driver always used IRQ 10. > > Unfortunately my BIOS is too brain-damaged to report IRQ's for ISA devices > at boot so I can't be sure. I have tried options PNPBIOS as well as trying > to specify irq 10 to sbc to no avail. I'd appreciate any assistance. It is perfectly reasonable for the kernel to choose irq 5 for this card since its free and the soundcard supports it. There is a known problem with the vibra16x at the moment. Last I heard, Cameron was part way through fixing it. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 2:22:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 7519514F7B for ; Wed, 15 Dec 1999 02:22:14 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11yBZA-000CKG-00; Wed, 15 Dec 1999 10:21:52 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id LAA11006; Wed, 15 Dec 1999 11:22:10 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <38576BD2.21701740@scc.nl> Date: Wed, 15 Dec 1999 11:22:10 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Martin Cracauer Cc: current@FreeBSD.ORG Subject: Re: sh(1) broken caching [was: Re: Broken sh(1)?] References: <712.945183175@axl.noc.iafrica.com> <38565DEA.4487DF53@scc.nl> <19991215105728.A61202@cons.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Martin Cracauer wrote: > > OK, the problem is real. > > BTW, its worse: > > #! /bin/sh > hash -v > PATH=/sbin:/bin > PATH=/foo:/bar:/bin ls > hash -v > ls > > => coredump It seems to me that when there's a PATH= assignment you don't want to add anything to the cache or alternatively, clear the cache after execution of the command having a PATH= assignment. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 2:28:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id C2397153C1 for ; Wed, 15 Dec 1999 02:28:14 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1774 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Wed, 15 Dec 1999 11:28:12 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id A35D338E6; Wed, 15 Dec 1999 11:28:11 +0100 (MET) Subject: tagged openings now 31 To: freebsd-current@freebsd.org (FreeBSD Current) Date: Wed, 15 Dec 1999 11:28:11 +0100 (MET) Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1068 Message-Id: <19991215102811.A35D338E6@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, from time to time (i have no idea how to reproduce it or what causes it) i get the following message on the console of one of my current systems: (da1:ncr0:0:1:0): tagged openings now 31 The drive causing this is a da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: Serial Number DX91RXG da1: 20.000MB/s transfers (10.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4096MB (8388608 512 byte sectors: 255H 63S/T 522C) on a Tekram: ncr0: irq 15 at device 8.0 on pci0 ncr0: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo ncr0: single-ended, open drain IRQ driver, using on-chip SRAM Should i be concerned about this ? hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 2:59: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 73A2915244 for ; Wed, 15 Dec 1999 02:58:43 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id dBFAw1o12522; Wed, 15 Dec 1999 12:58:01 +0200 (SAST) Message-Id: <199912151058.dBFAw1o12522@gratis.grondar.za> To: Soren Schmidt Cc: current@freebsd.org Subject: Re: YA Non-DMA IDE controller... Date: Wed, 15 Dec 1999 12:58:00 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems Mark Murray wrote: > > Hi > > > > My Toshiba Libretto has dogslow disk; here is the probe message. Any > > chances of getting this one to work in DMA mode? > > > > ad0: ATA-4 disk at ata0 as master > > ad0: 4126MB (8452080 sectors), 8944 cyls, 15 heads, 63 S/T, 512 B/S > > ad0: 16 secs/int, 1 depth queue, PIO > > Could you send me a verbose boot from it, and I'll take a look... Sure. (It got chopped off at the top; if that is a problem, I'll see if I can fix it). M K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002ca000 - 0x0400dfff, 64241664 bytes (15684 pages) avail memory = 62287872 (60828K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f8e20 bios32: Entry = 0xfe95a (c00fe95a) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xc5d9 pnpbios: Found PnP BIOS data at 0xc00f8e30 pnpbios: Entry = f0000:90a8 Rev = 1.0 pnpbios: Event flag at 510 pnpbios: OEM ID c932f351 Other BIOS signatures found: ACPI: 000f4660 Preloaded elf kernel "kernel.debug" at 0xc02b1000. Intel Pentium detected, installing workaround for F00F bug VESA: information block 56 45 53 41 00 02 1f 01 00 01 00 00 00 00 22 00 00 01 1f 00 01 01 00 01 00 01 09 01 00 01 1a 01 00 01 00 01 01 01 02 01 03 01 04 01 05 01 0d 01 0e 01 10 01 11 01 12 01 13 01 14 01 15 01 16 01 VESA: 21 mode(s) found VESA: v2.0, 1984k memory, flags:0x0, mode table:0xc0263b62 (1000022) VESA: MagicGraph 128XD 40K SVGA BIOS VESA: NeoMagic MagicGraph 128XV 01.0 pci_open(1): mode 1 addr port (0x0cf8) is 0x8000a050 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=06011179) npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 126710593 bytes/sec bzero() bandwidth = 178794922 bytes/sec apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=06011179) pcib0: on motherboard found-> vendor=0x1179, dev=0x0601, revid=0x2e class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x10c8, dev=0x0004, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=255 map[10]: type 1, range 32, base fd000000, size 24 map[14]: type 1, range 32, base ffc00000, size 21 map[18]: type 1, range 32, base ffb00000, size 20 found-> vendor=0x1179, dev=0x0701, revid=0x22 class=07-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=255 found-> vendor=0x1179, dev=0x060f, revid=0x20 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=14 secondarybus=14 intpin=a, irq=255 found-> vendor=0x1179, dev=0x060f, revid=0x20 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=15 secondarybus=15 intpin=b, irq=255 pci0: on pcib0 vga-pci0: at device 4.0 on pci0 pci0: unknown card (vendor=0x1179, dev=0x0701) at 17.0 pcic-pci0: at device 19.0 on pci0 PCI Config space: 00: 060f1179 04800007 06070020 00820000 10: 00000000 04800000 00141400 00000000 20: 00000000 00000000 00000000 00000000 30: 00000000 00000000 00000000 000001ff 40: 00011179 000003e1 00000000 00000000 50: 00000000 00000000 00000000 00000000 60: 00000000 00000000 00000000 00000000 70: 00000000 00000000 00000000 00000000 80: 00000000 00000000 00000000 01000000 90: 00000000 00000000 00000000 00000000 Cardbus Socket registers: 00: f000ef6f: f000ef6f: f000e2c3: f000ef6f: 10: f000ef6f: c0002bdd: f000e140: f000ef6f: ExCa registers: 00: fb 77 c5 86 c4 c0 c8 02 08 e8 40 91 88 fe 28 e0 10: 8a 66 03 38 e0 72 02 88 e0 bf 05 00 c4 5e 04 50 20: b4 02 cd 13 5b 73 0a 4f 74 1c 30 e4 cd 13 93 eb 30: eb 0f b6 c3 01 46 08 73 03 ff 46 0a d0 e3 00 5e pcic-pci1: at device 19.1 on pci0 PCI Config space: 00: 060f1179 04800007 06070020 00820000 10: 00000000 04800000 00151500 00000000 20: 00000000 00000000 00000000 00000000 30: 00000000 00000000 00000000 000002ff 40: 00011179 000003e1 00000000 00000000 50: 00000000 00000000 00000000 00000000 60: 00000000 00000000 00000000 00000000 70: 00000000 00000000 00000000 00000000 80: 00000000 00000000 00000000 01000000 90: 00000000 00000000 00000000 00000000 Cardbus Socket registers: 00: f000ef6f: f000ef6f: f000e2c3: f000ef6f: 10: f000ef6f: c0002bdd: f000e140: f000ef6f: ExCa registers: 00: fb 77 c5 86 c4 c0 c8 02 08 e8 40 91 88 fe 28 e0 10: 8a 66 03 38 e0 72 02 88 e0 bf 05 00 c4 5e 04 50 20: b4 02 cd 13 5b 73 0a 4f 74 1c 30 e4 cd 13 93 eb 30: eb 0f b6 c3 01 46 08 73 03 ff 46 0a d0 e3 00 5e isa0: on motherboard Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: direction bit not set fdc0: cmd 3 failed at out byte 1 of 3 ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at port 0x1f0 irq 14 on isa0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: status 10 00 64 psm: data 08 00 00 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0 kbd0 sio0: irq maps: 0x1 0x11 0x11 0x11 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A pcic: polling, can't alloc 0 pcic: polling, can't alloc 0 pcic0: on isa0 pccard0: on pcic0 pccard1: on pcic0 isa_probe_children: probing PnP devices BIOS Geometries: 0:0203fe3f 0..515=516 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: lo0 attached IPsec: Initialized Security Association Processing. ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 ad0: ATA-4 disk at ata0 as master ad0: 4126MB (8452080 sectors), 8944 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, PIO Creating DISK ad0 Creating DISK wd0 Mounting root from ufs:/dev/wd0s2a wd0s1: type 0xc, start 63, end = 2056319, size 2056257 : OK wd0s2: type 0xa5, start 2056320, end = 8161019, size 6104700 : OK start_init: trying /sbin/init pccard: card inserted, slot 0 pccard: card inserted, slot 1 sio2 at port 0x2e8-0x2ef irq 9 slot 0 on pccard0 sio2: type 16550A splash: image decoder found: star_saver ep0: <3Com Etherlink III 3C589> at port 0x240-0x24f irq 10 slot 1 on pccard1 ep0: Ethernet address 00:10:5a:2d:39:c6 ep0: supplying EUI64: 00:10:5a:ff:fe:2d:39:c6 bpf: ep0 attached ep0: starting DAD for fe80:0002::0210:5aff:fe2d:39c6 ep0: DAD complete for fe80:0002::0210:5aff:fe2d:39c6 - no duplicates found -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 3:25:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.195]) by hub.freebsd.org (Postfix) with ESMTP id 968EE1534E for ; Wed, 15 Dec 1999 03:25:53 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id MAA24042; Wed, 15 Dec 1999 12:25:47 +0100 (CET) Date: Wed, 15 Dec 1999 12:25:46 +0100 From: Martin Cracauer To: Marcel Moolenaar Cc: Martin Cracauer , current@FreeBSD.ORG Subject: Re: sh(1) broken caching [was: Re: Broken sh(1)?] Message-ID: <19991215122546.A24027@cons.org> References: <712.945183175@axl.noc.iafrica.com> <38565DEA.4487DF53@scc.nl> <19991215105728.A61202@cons.org> <38576BD2.21701740@scc.nl> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=6TrnltStXW4iwmi0 X-Mailer: Mutt 0.95.1i In-Reply-To: <38576BD2.21701740@scc.nl>; from Marcel Moolenaar on Wed, Dec 15, 1999 at 11:22:10AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii In <38576BD2.21701740@scc.nl>, Marcel Moolenaar wrote: > It seems to me that when there's a PATH= assignment you don't want to > add anything to the cache or alternatively, clear the cache after > execution of the command having a PATH= assignment. The first solution is better, but the source messes with the hashtable too directly in too many places. Appended diff does the second route. Does it fix your problems? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=diff ? test2 ? l ? test1 ? sh.core ? builtins.c ? builtins.h ? mknodes ? nodes.h ? nodes.c ? mksyntax ? syntax.c ? syntax.h ? token.h ? y.tab.h ? y.tab.c ? arith.c ? arith_lex.c ? sh ? mkinit ? init.c ? sh.1.gz Index: Makefile =================================================================== RCS file: /home/CVS-FreeBSD/src/bin/sh/Makefile,v retrieving revision 1.30 diff -c -r1.30 Makefile *** Makefile 1999/09/08 15:40:43 1.30 --- Makefile 1999/12/15 11:24:05 *************** *** 18,24 **** LDADD+= -ll -ledit -ltermcap LFLAGS= -8 # 8-bit lex scanner for arithmetic ! CFLAGS+=-DSHELL -I. -I${.CURDIR} # for debug: # CFLAGS+= -g -DDEBUG=2 --- 18,24 ---- LDADD+= -ll -ledit -ltermcap LFLAGS= -8 # 8-bit lex scanner for arithmetic ! CFLAGS+=-DSHELL -I. -I${.CURDIR} -g -Werror # for debug: # CFLAGS+= -g -DDEBUG=2 Index: eval.c =================================================================== RCS file: /home/CVS-FreeBSD/src/bin/sh/eval.c,v retrieving revision 1.26 diff -c -r1.26 eval.c *** eval.c 1999/11/29 19:10:59 1.26 --- eval.c 1999/12/15 11:24:05 *************** *** 612,623 **** --- 612,625 ---- volatile int e; char *lastarg; int realstatus; + int do_clearcmdentry; #if __GNUC__ /* Avoid longjmp clobbering */ (void) &argv; (void) &argc; (void) &lastarg; (void) &flags; + (void) &do_clearcmdentry; #endif /* First expand the arguments. */ *************** *** 626,631 **** --- 628,634 ---- arglist.lastp = &arglist.list; varlist.lastp = &varlist.list; varflag = 1; + do_clearcmdentry = 0; oexitstatus = exitstatus; exitstatus = 0; for (argp = cmd->ncmd.args ; argp ; argp = argp->narg.next) { *************** *** 688,695 **** * is present */ for (sp = varlist.list ; sp ; sp = sp->next) ! if (strncmp(sp->text, PATH, sizeof(PATH) - 1) == 0) path = sp->text + sizeof(PATH) - 1; find_command(argv[0], &cmdentry, 1, path); if (cmdentry.cmdtype == CMDUNKNOWN) { /* command not found */ --- 691,700 ---- * is present */ for (sp = varlist.list ; sp ; sp = sp->next) ! if (strncmp(sp->text, PATH, sizeof(PATH) - 1) == 0) { path = sp->text + sizeof(PATH) - 1; + do_clearcmdentry = 1; + } find_command(argv[0], &cmdentry, 1, path); if (cmdentry.cmdtype == CMDUNKNOWN) { /* command not found */ *************** *** 887,892 **** --- 892,899 ---- out: if (lastarg) setvar("_", lastarg, 0); + if (do_clearcmdentry) + clearcmdentry(0); popstackmark(&smark); } Index: exec.c =================================================================== RCS file: /home/CVS-FreeBSD/src/bin/sh/exec.c,v retrieving revision 1.13 diff -c -r1.13 exec.c *** exec.c 1999/08/27 23:15:11 1.13 --- exec.c 1999/12/15 11:24:05 *************** *** 104,110 **** STATIC void execinterp __P((char **, char **)); #endif STATIC void printentry __P((struct tblentry *, int)); - STATIC void clearcmdentry __P((int)); STATIC struct tblentry *cmdlookup __P((char *, int)); STATIC void delete_cmd_entry __P((void)); --- 104,109 ---- *************** *** 640,646 **** * PATH which has changed. */ ! STATIC void clearcmdentry(firstchange) int firstchange; { --- 639,645 ---- * PATH which has changed. */ ! void clearcmdentry(firstchange) int firstchange; { Index: exec.h =================================================================== RCS file: /home/CVS-FreeBSD/src/bin/sh/exec.h,v retrieving revision 1.8 diff -c -r1.8 exec.h *** exec.h 1999/08/27 23:15:12 1.8 --- exec.h 1999/12/15 11:24:05 *************** *** 69,71 **** --- 69,72 ---- void defun __P((char *, union node *)); int unsetfunc __P((char *)); int typecmd __P((int, char **)); + void clearcmdentry __P((int)); --6TrnltStXW4iwmi0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 3:51:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 82DAA154DA for ; Wed, 15 Dec 1999 03:51:54 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id MAA73981; Wed, 15 Dec 1999 12:51:38 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912151151.MAA73981@freebsd.dk> Subject: Re: YA Non-DMA IDE controller... In-Reply-To: <199912151058.dBFAw1o12522@gratis.grondar.za> from Mark Murray at "Dec 15, 1999 12:58:00 pm" To: mark@grondar.za (Mark Murray) Date: Wed, 15 Dec 1999 12:51:38 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Mark Murray wrote: > > It seems Mark Murray wrote: > > > Hi > > > > > > My Toshiba Libretto has dogslow disk; here is the probe message. Any > > > chances of getting this one to work in DMA mode? > > > > > > ad0: ATA-4 disk at ata0 as master > > > ad0: 4126MB (8452080 sectors), 8944 cyls, 15 heads, 63 S/T, 512 B/S > > > ad0: 16 secs/int, 1 depth queue, PIO > > > > Could you send me a verbose boot from it, and I'll take a look... > > Sure. (It got chopped off at the top; if that is a problem, I'll see if > I can fix it). It is, sort of, I also wanted to see the pci probes of the ATA chip they are missing here. options MSGBUF_SIZE=50000 or so is your friend... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 4:16:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id EC01A15097 for ; Wed, 15 Dec 1999 04:16:27 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 11yDM2-0005fm-00; Wed, 15 Dec 1999 12:16:26 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id NAA88888; Wed, 15 Dec 1999 13:16:21 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <38578695.D41619A9@scc.nl> Date: Wed, 15 Dec 1999 13:16:21 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Martin Cracauer Cc: current@FreeBSD.ORG Subject: Re: sh(1) broken caching [was: Re: Broken sh(1)?] References: <712.945183175@axl.noc.iafrica.com> <38565DEA.4487DF53@scc.nl> <19991215105728.A61202@cons.org> <38576BD2.21701740@scc.nl> <19991215122546.A24027@cons.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Martin Cracauer wrote: > > In <38576BD2.21701740@scc.nl>, Marcel Moolenaar wrote: > > It seems to me that when there's a PATH= assignment you don't want to > > add anything to the cache or alternatively, clear the cache after > > execution of the command having a PATH= assignment. > > The first solution is better, but the source messes with the hashtable > too directly in too many places. > > Appended diff does the second route. Does it fix your problems? It fixes the examples and thus my problems :-) I already created a work-around in `make buildworld' so it works on older shells without the need to build sh(1) in the bootstrap stage, because the bug only pops up when doing a parallel make (ie make -jN) because each command will be executed by the same shell instance in that case. BTW: Don't forget to remove '-g' from CFLAGS when you commit the patch :-) -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 4:29:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 7B1A715157 for ; Wed, 15 Dec 1999 04:29:05 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id NAA04727 for freebsd-current@freebsd.org; Wed, 15 Dec 1999 13:29:03 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id B09B78863; Wed, 15 Dec 1999 13:19:30 +0100 (CET) Date: Wed, 15 Dec 1999 13:19:30 +0100 From: Ollivier Robert To: FreeBSD Current Subject: Re: tagged openings now 31 Message-ID: <19991215131930.A36296@keltia.freenix.fr> Mail-Followup-To: FreeBSD Current References: <19991215102811.A35D338E6@hcswork.hcs.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <19991215102811.A35D338E6@hcswork.hcs.de> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Hellmuth Michaelis: > Should i be concerned about this ? No. You have booted with "-v" haven't you ? It is just a message saying that the # of tagged commands is down from the default of 64 to 31. Nothing to worry about. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 4:34:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id EC6A01526C for ; Wed, 15 Dec 1999 04:34:23 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id HAA08550; Wed, 15 Dec 1999 07:34:17 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id HAA15893; Wed, 15 Dec 1999 07:34:16 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id HAA51317; Wed, 15 Dec 1999 07:34:16 -0500 (EST) Date: Wed, 15 Dec 1999 07:34:16 -0500 (EST) From: Thomas David Rivers Message-Id: <199912151234.HAA51317@lakes.dignus.com> To: adams@digitalspark.net, dcs@newsguy.com Subject: Re: sysinstall: is it really at the end of its lifecycle? Cc: current@FreeBSD.ORG, freebsd@sasknow.com, peter.jeremy@alcatel.com.au In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Adam Strohl wrote: > On Wed, 15 Dec 1999, Daniel C. Sobral wrote: > > > Hey, I like CUI. I'd rather install with a CUI than a GUI, all other > > things being equal. And besides some quirks here and there, I really > > like sysinstall. > > Its nice, but its not where it should be. > > > But the fact is that when we get featured in a magazine article, > > user-friendly install == GUI. No GUI, it's not an user-friendly install. > > End of review. You can kick and scream all you want, that's the way it > > is. Either we live by these rules, or we loose. > > A VESA GUI based sysinstall replacement would probably be small enough to > fit on a floppy, yet still have the friendlyness that a new user/reviewer > would look for. > > If we follow jkh's outline, making another "front end target" for the > script shouldn't be that hard. You have X, VESA Syscons, and Text > Syscons. > > The script says "ok, prompt user for ", under X it opens a window, > under Text some ASCII dialog, and under VESA a little window. > This is important to note... 25% of all the installs I do are on MGA (remember monochrome graphics adapter - a hercules card.) So, I would not be in favor of any replacement that required a VESA or VGA platform... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 4:47:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from megadodo.segNET.COM (megadodo.segNET.COM [206.34.181.3]) by hub.freebsd.org (Postfix) with ESMTP id 31E8615082 for ; Wed, 15 Dec 1999 04:47:08 -0800 (PST) (envelope-from adams@digitalspark.net) Received: from nightfall.digitalspark.net (arc6a203.bf.sover.net [209.198.85.204]) by megadodo.segNET.COM (8.9.1a/8.8.5) with ESMTP id HAA26990; Wed, 15 Dec 1999 07:46:59 -0500 (EST) Date: Wed, 15 Dec 1999 07:47:43 -0500 (EST) From: Adam Strohl To: Thomas David Rivers Cc: dcs@newsguy.com, current@FreeBSD.ORG, freebsd@sasknow.com, peter.jeremy@alcatel.com.au Subject: Re: sysinstall: is it really at the end of its lifecycle? In-Reply-To: <199912151234.HAA51317@lakes.dignus.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, 15 Dec 1999, Thomas David Rivers wrote: > This is important to note... 25% of all the installs I do are > on MGA (remember monochrome graphics adapter - a hercules card.) True, hence there would be other display targets, ie; CUI, and I like Jordan's text-only non GUI idea, too. It doesn't really matter. The new sysinstall architecture should be such that it is completely indepentent of the UI (or lack there of). > So, I would not be in favor of any replacement that required a VESA > or VGA platform... I agree, this would not be a requirement, just another option. - ----( Adam Strohl )------------------------------------------------ - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - - ----------------------------------------( DigitalSpark.NET )------- - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 4:50:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id CC24D14CB5 for ; Wed, 15 Dec 1999 04:50:28 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 14482 invoked from network); 15 Dec 1999 12:50:28 -0000 Received: from lcb13.cvzoom.net (HELO cvzoom.net) (63.65.159.13) by ns.cvzoom.net with SMTP; 15 Dec 1999 12:50:28 -0000 Message-ID: <38578E57.BE6F50E1@cvzoom.net> Date: Wed, 15 Dec 1999 07:49:27 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Kernel config utility Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So, would having a kernel config utility help us get better reviews? I was thinking about something like an explorer-type thing that was divided into two panes. On the left would be LINT. Here, we would have icons representing the various devices. For example, we could ahve an icon representing an ethernet card, another icon representing a serial port, etc. On the right hand side we would have the custom kernel config file. You could just drag the icons over to the right hand side to add devices to your kernel config. And, of course, you could always just delete the icons you don't need. By clicking on the icons, a properties pane would show the properties for this device. Of course, there should be some way to represent options, such as DEVFS or SOFTUPDATES. Of course, I like using vi better, but I've heard some people complaining about "how hard it is to configure a FreeBSD kernel." I know I didn't fully convey the principles, but you probably get the general idea. Of course, when you're down to using teddy bears and talking parrots, then you know you've made it too simple. :-] - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 4:55: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.195]) by hub.freebsd.org (Postfix) with ESMTP id 9EFE015563 for ; Wed, 15 Dec 1999 04:54:52 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id NAA24616; Wed, 15 Dec 1999 13:54:47 +0100 (CET) Date: Wed, 15 Dec 1999 13:54:47 +0100 From: Martin Cracauer To: Marcel Moolenaar Cc: Martin Cracauer , current@FreeBSD.ORG Subject: Re: sh(1) broken caching [was: Re: Broken sh(1)?] Message-ID: <19991215135447.B24584@cons.org> References: <712.945183175@axl.noc.iafrica.com> <38565DEA.4487DF53@scc.nl> <19991215105728.A61202@cons.org> <38576BD2.21701740@scc.nl> <19991215122546.A24027@cons.org> <38578695.D41619A9@scc.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <38578695.D41619A9@scc.nl>; from Marcel Moolenaar on Wed, Dec 15, 1999 at 01:16:21PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <38578695.D41619A9@scc.nl>, Marcel Moolenaar wrote: > Martin Cracauer wrote: > > > > In <38576BD2.21701740@scc.nl>, Marcel Moolenaar wrote: > > > It seems to me that when there's a PATH= assignment you don't want to > > > add anything to the cache or alternatively, clear the cache after > > > execution of the command having a PATH= assignment. > > > > The first solution is better, but the source messes with the hashtable > > too directly in too many places. > > > > Appended diff does the second route. Does it fix your problems? > > It fixes the examples and thus my problems :-) > > I already created a work-around in `make buildworld' so it works on > older shells without the need to build sh(1) in the bootstrap stage, > because the bug only pops up when doing a parallel make (ie make -jN) > because each command will be executed by the same shell instance in that > case. I would like you to do so, since I'd like to give the better solution a shot over the weekend. > BTW: Don't forget to remove '-g' from CFLAGS when you commit the patch > :-) Ops :-) Now working with a seperate Makefile (for bumping Warning levels). Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 4:57:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 3AD9B152CB for ; Wed, 15 Dec 1999 04:57:16 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11yDyw-0002Va-00; Wed, 15 Dec 1999 14:56:38 +0200 From: Sheldon Hearn To: "Thomas Runge" Cc: current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: Your message of "Wed, 15 Dec 1999 10:41:56 +0100." <38576264.7D33C327@rostock.zgdv.de> Date: Wed, 15 Dec 1999 14:56:38 +0200 Message-ID: <9645.945262598@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 15 Dec 1999 10:41:56 +0100, "Thomas Runge" wrote: > So, we have a very good server OS, let's focus a little bit > more on the desktop. Most developers are more concerned with improving the operating system itself than providing an inviting desktop experience. The problem is that it's very seldom that the people who call for an inviting desktop experience actually follow through with effort. When invited to do so, they usually cite a lack of various combinations of time, inclination and ability. None of the FreeBSD developers are against an improved "look'n'feel". They just happen to be more inclined to focus elsewhere. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 4:58:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from megadodo.segNET.COM (megadodo.segNET.COM [206.34.181.3]) by hub.freebsd.org (Postfix) with ESMTP id 2FE0B1526C for ; Wed, 15 Dec 1999 04:58:32 -0800 (PST) (envelope-from adams@digitalspark.net) Received: from nightfall.digitalspark.net (arc6a203.bf.sover.net [209.198.85.204]) by megadodo.segNET.COM (8.9.1a/8.8.5) with ESMTP id HAA28706; Wed, 15 Dec 1999 07:58:19 -0500 (EST) Date: Wed, 15 Dec 1999 07:59:03 -0500 (EST) From: Adam Strohl To: "Jordan K. Hubbard" Cc: "Daniel C. Sobral" , Ryan Thompson , Peter Jeremy , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-Reply-To: <51308.945234648@zippy.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 Tue, 14 Dec 1999, Jordan K. Hubbard wrote: > VESA syscons, either using libvgl and an array of crude widgets or > something like MGR and its widget set, has long been on the wish-list > but I didn't even include it in my summary since it's still very much > a pipe-dream. :-) Hmm, this has been a fantasy of mine, as well. I was hoping to assist with the syscons code enough so that we could get a simple primative API down for drawing graphics on the screen, but my job seems to be taking up any time I'd have to do that now, hopefully that will change :P However, the syscons cleanup is proceeding anyway from what I've seen on the list. As long as we have basic graphics drawing, we'd be able to impliment our own widgets, if need be. I don't know how big the requirements for libvgl are, or how much spare space on that second floppy we have, though. > There's actually one mode you forgot, which is > what I call "text mode", and that's straight ascii prompts, no CUI-style > dialog boxes or anything. Think about text-to-speach devices for > the blind or serial consoles attached to really *dumb* terminals. :-) This is a cool idea, also good for script based installs where you want it to go fast and dirty. - ----( Adam Strohl )------------------------------------------------ - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - - ----------------------------------------( DigitalSpark.NET )------- - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 5: 0:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 98D1814CB5 for ; Wed, 15 Dec 1999 05:00:23 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id XAA01323; Wed, 15 Dec 1999 23:29:48 +1030 (CST) (envelope-from newton) Date: Wed, 15 Dec 1999 23:29:48 +1030 From: Mark Newton To: "Jeremy L. Stock" Cc: current@FreeBSD.ORG Subject: Re: Problem with sbc driver and/or newpcm Message-ID: <19991215232948.A1263@internode.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 03:09:10AM -0600, Jeremy L. Stock wrote: > The sbc driver seems to correctly detect my soundcard for the first time > since the introduction of newpcm but I don't actually get sound out of it. Just a quick check: Can you type "mixer" at a shell prompt and check whether the reason you're getting no sound is because the master volume level defaults to 0? - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 5: 3:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 25A7414E59 for ; Wed, 15 Dec 1999 05:03:38 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id XAA01353; Wed, 15 Dec 1999 23:33:19 +1030 (CST) (envelope-from newton) Date: Wed, 15 Dec 1999 23:33:19 +1030 From: Mark Newton To: Thomas Runge Cc: current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991215233319.B1263@internode.com.au> References: <3856BD33.5DE1AB48@newsguy.com> <19991215105736.A467@internode.com.au> <38576264.7D33C327@rostock.zgdv.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <38576264.7D33C327@rostock.zgdv.de> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 10:41:56AM +0100, Thomas Runge wrote: > This all sounds like a decision, whether we want to be a desktop > or a server-only system. I don't agree at all -- I think that's another divsion which is orthogonal to the current discussion. Why can't we be a server OS with a decent installation tool? > For mainly server-oriented, the "install source to update" or > console-based setups are quite enough, because the system will > most probably administraded by people, that know, what they are > doing. But is it reasonable to say, "You can't play at all if you don't fit that description"? (Especially since the NT server camp seems to think you can administer a system with zero knowledge of anything; The requirement that they suddenly need to become familiar with how to deal with large archives of source code isn't going to help us get a foot in those doors). - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 5:32:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from chai.torrentnet.com (chai.torrentnet.com [198.78.51.73]) by hub.freebsd.org (Postfix) with ESMTP id AA7B614F7B for ; Wed, 15 Dec 1999 05:32:45 -0800 (PST) (envelope-from bakul@torrentnet.com) Received: from chai.torrentnet.com (localhost [127.0.0.1]) by chai.torrentnet.com (8.8.8/8.8.5) with ESMTP id IAA02990; Wed, 15 Dec 1999 08:32:43 -0500 (EST) Message-Id: <199912151332.IAA02990@chai.torrentnet.com> To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: Kernel config utility In-reply-to: Your message of "Wed, 15 Dec 1999 07:49:27 EST." <38578E57.BE6F50E1@cvzoom.net> Date: Wed, 15 Dec 1999 08:32:43 -0500 From: Bakul Shah Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So, would having a kernel config utility help us get better > reviews? I was thinking about something like an explorer-type > thing that was divided into two panes. On the left would be > LINT. Here, we would have icons representing the various > devices. For example, we could ahve an icon representing an > ethernet card, another icon representing a serial port, etc. On > the right hand side we would have the custom kernel config file. > You could just drag the icons over to the right hand side to add > devices to your kernel config. And, of course, you could always > just delete the icons you don't need. You have just described some file system operations! left pane: ls LINT right pane: ls KERNEL drag an icon: cp LINT/device/ethernet KERNEL/device > By clicking on the icons, a properties pane would show the > properties for this device. Of course, there should be some way > to represent options, such as DEVFS or SOFTUPDATES. property pane: vi KERNEL/ethernet options: touch KERNEL/options/DEVFS echo 2048 > KERNEL/options/NMBCLUSTERS > Of course, I like using vi better, but I've heard some people > complaining about "how hard it is to configure a FreeBSD > kernel." Most of us like the convenience of editing one file but I think what these `some people' are asking for is explicit structure. In a config represented by a plain file the structure is implicit and the flat structure makes it hard to group related things so you have to read comments (if any and hopefully uptodate) to understand what option applies to what object. A directory would provide that structure (and allow for extensions that you wouldn't even try with a flat file). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 5:43:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 16AAE14C32 for ; Wed, 15 Dec 1999 05:43:31 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id OAA12846; Wed, 15 Dec 1999 14:43:15 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199912151234.HAA51317@lakes.dignus.com> References: <199912151234.HAA51317@lakes.dignus.com> Date: Wed, 15 Dec 1999 14:33:40 +0100 To: Thomas David Rivers , adams@digitalspark.net, dcs@newsguy.com From: Brad Knowles Subject: Re: sysinstall: is it really at the end of its lifecycle? Cc: current@FreeBSD.ORG, freebsd@sasknow.com, peter.jeremy@alcatel.com.au Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 7:34 AM -0500 1999/12/15, Thomas David Rivers wrote: > This is important to note... 25% of all the installs I do are > on MGA (remember monochrome graphics adapter - a hercules card.) > So, I would not be in favor of any replacement that required a VESA > or VGA platform... Agreed. Think "RealWeasel" (see ). -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 7: 1:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22]) by hub.freebsd.org (Postfix) with ESMTP id A16B4153D8 for ; Wed, 15 Dec 1999 07:01:07 -0800 (PST) (envelope-from veldy@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id 97C96379E; Wed, 15 Dec 1999 09:01:06 -0600 (CST) Received: from localhost (veldy@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id JAA11222; Wed, 15 Dec 1999 09:01:06 -0600 (CST) X-Authentication-Warning: isis.visi.com: veldy owned process doing -bs Date: Wed, 15 Dec 1999 09:01:06 -0600 (CST) From: Thomas Veldhouse To: "Don 'Duck' Harper" Cc: "Daniel C. Sobral" , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? 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 There a more Linux distros with grahical installs. Correl 1.0 - based upon debian. Also, I believe that SUSE 6.3 has one also. Tom Veldhouse veldy@visi.com On Tue, 14 Dec 1999, Don 'Duck' Harper wrote: > Sometime Tomorrow, Daniel C. Sobral said something like this: > :-)But the fact is that when we get featured in a magazine article, > :-)user-friendly install == GUI. No GUI, it's not an user-friendly install. > :-)End of review. You can kick and scream all you want, that's the way it > :-)is. Either we live by these rules, or we loose. > :-) > :-)> >From a techical standpoint, yes, an X based install would be far too large > :-)> for a single floppy, even at the simplest level. AND, again, as someone > :-)> who has installed FreeBSD dozens of times on various systems, I think I > :-)> should also stress that I have NEVER installed FreeBSD from CD :-) > :-) > :-)Me neither, but CD is still the most popular installation media these > :-)days, though we, Open Source OS, probably get more network installs than > :-)CD installs. > > >From the linux world ( I know, bad word :), there are two distrubutions > which use a GUI based install. Caldera's & Red Hat. The Red Hat is based > on python, and auto-detects if the graphics card is capable of X. Then it > fires up XFree86's VGA server. And it fits all this on one floppy. They > do have two floppies, one for local CD/disk installs, and another for > NFS/FTP/HTTP/SMB installs. > > So, I know it can be done. Is it worth the effort? I donno. > > Just a view from a FreeBSD newbie, long time Linux guy. > > Don > > -- > Don Harper, RHCE, MCSE | work: duck@colltech.com cell: (512) 751-9888 > Team Austin | Pager: (800) Sky-Page, pin 303-7055 > Collective Technologies | http://www.colltech.com http://www.duckland.org > A Pencom Company | home: duck@duckland.org > | finger duck@duckland.org for PGP key > > He Who Dies with the Most Toys Still Dies. > > > > > 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 Dec 15 7: 9:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from chain.freebsd.os.org.za (chain.freebsd.os.org.za [196.7.162.242]) by hub.freebsd.org (Postfix) with ESMTP id 0C60215220 for ; Wed, 15 Dec 1999 07:09:34 -0800 (PST) (envelope-from khetan@chain.freebsd.os.org.za) Received: by chain.freebsd.os.org.za (Postfix, from userid 1000) id 5F79E35627; Wed, 15 Dec 1999 17:09:15 +0200 (SAST) Received: from localhost (localhost [127.0.0.1]) by chain.freebsd.os.org.za (Postfix) with ESMTP id 553EF31915 for ; Wed, 15 Dec 1999 17:09:15 +0200 (SAST) Date: Wed, 15 Dec 1999 17:09:15 +0200 (SAST) From: Khetan Gajjar Reply-To: Khetan Gajjar To: current@freebsd.org Subject: microuptime problem/error ? Message-ID: X-Mobile: +27 82 9907663 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've started seeing "microuptime() went backwards" errors, followed by calcru errors. I think it's related to phk's commit of kern_resource.c (1.53) and kern_synch.c (1.84). What I don't understand is how is this possible if I'm using xntpd to keep time, and my machine is reporting itself as a stratum 3 server ? I have included three examples of the microuptime and calcru error, and the output of ntptrace. I'm running a -current with source from Dec 5th. Dec 15 16:07:53 chain /kernel: microuptime() went backwards (101123.4765911 -> 101123,992013) Dec 15 16:07:53 chain /kernel: microuptime() went backwards (101123.4765911 -> 101123,992013) Dec 15 16:07:53 chain /kernel: microuptime() went backwards (101123.4765911 -> 101123,993154) Dec 15 17:00:01 chain /kernel: calcru: negative time of 653353 usec for pid 126 (syslogd) Dec 15 17:00:01 chain /kernel: calcru: negative time of 653353 usec for pid 126 (syslogd) Dec 15 17:00:01 chain /kernel: calcru: negative time of 653353 usec for pid 126 (syslogd) localhost.freebsd.os.org.za: stratum 3, offset 0.000043, synch distance 0.17436 lo0.cr1.cpt.iafrica.net: stratum 2, offset 0.002962, synch distance 0.06694 Time1.wasp.co.za: stratum 1, offset -0.005048, synch distance 0.00087, refid 'GPS' TIA. --- Khetan Gajjar (!kg1779) * khetan@os.org.za http://khetan.os.org.za/ * Talk/Finger khetan@khetan.os.org.za FreeBSD enthusiast * http://www2.za.freebsd.org/ /dev/random output : A naked man fears no pickpocket To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 7:19:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 1CCB4153D8 for ; Wed, 15 Dec 1999 07:19:51 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id QAA28467 for freebsd-current@FreeBSD.ORG; Wed, 15 Dec 1999 16:19:49 +0100 (CET) (envelope-from olli) Date: Wed, 15 Dec 1999 16:19:49 +0100 (CET) From: Oliver Fromme Message-Id: <199912151519.QAA28467@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" Organization: Administration TU Clausthal Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jack wrote in list.freebsd-current: > Today Oliver Fromme wrote: > > I'm afraid that wouldn't work. In order to run non-trivial X11 > > apps, you _will_ need a full-blown X server, including X libs. > > You'll also need at least a very simple window manager (while > > xclock would probably work without, Netscape would certainly be > > pretty unusable). > > I just tried only netscape in my .xinitrc and it worked fine. That's because X itself contains a very simple "windowmanager" functionality, which focuses the window beneath the mouse pointer. But when you have to access something which is behind another window, you lose. And as I wrote, the window manager is the smallest problem of his proposal. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 7:24: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 6246715292 for ; Wed, 15 Dec 1999 07:23:59 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id F28BA2DC0A; Wed, 15 Dec 1999 16:24:39 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id D91A67811; Wed, 15 Dec 1999 16:21:56 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id D41AB10E10; Wed, 15 Dec 1999 16:21:56 +0100 (CET) Date: Wed, 15 Dec 1999 16:21:56 +0100 (CET) From: Andrzej Bialecki To: Adam Strohl Cc: "Jordan K. Hubbard" , "Daniel C. Sobral" , Ryan Thompson , Peter Jeremy , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? 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, 15 Dec 1999, Adam Strohl wrote: > On Tue, 14 Dec 1999, Jordan K. Hubbard wrote: > > > VESA syscons, either using libvgl and an array of crude widgets or > > something like MGR and its widget set, has long been on the wish-list > > but I didn't even include it in my summary since it's still very much > > a pipe-dream. :-) > > Hmm, this has been a fantasy of mine, as well. I was hoping to assist > with the syscons code enough so that we could get a simple primative API > down for drawing graphics on the screen, but my job seems to be taking up > any time I'd have to do that now, hopefully that will change :P > > However, the syscons cleanup is proceeding anyway from what I've seen on > the list. > > As long as we have basic graphics drawing, we'd be able to impliment our > own widgets, if need be. I don't know how big the requirements for libvgl > are, or how much spare space on that second floppy we have, though. As I said, I know of two examples of more or less complete GUIs, which are either ported to libvgl or can be fairly easily ported. Both of them take about 100kB. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 7:26:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 5137D153DD for ; Wed, 15 Dec 1999 07:26:33 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id QAA28624 for freebsd-current@FreeBSD.ORG; Wed, 15 Dec 1999 16:26:29 +0100 (CET) (envelope-from olli) Date: Wed, 15 Dec 1999 16:26:29 +0100 (CET) From: Oliver Fromme Message-Id: <199912151526.QAA28624@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" Organization: Administration TU Clausthal Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote in list.freebsd-current: > On Tue, 14 Dec 1999 21:26:04 +0100, Oliver Fromme wrote: > > > I'm not yet 100% convinced that it would make sense to separate > > the propellers code into a module. Is 5 Kbyte of kernel code > > really that much of a problem? > > No, but think ahead, into a future where we use a teeny tiny kernel into > which we plug lots of modules. Sure, in that case, syscons itself should be a module, shouldn't it? Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 7:29: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 5881F15220 for ; Wed, 15 Dec 1999 07:29:01 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p13-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.142]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id AAA19709; Thu, 16 Dec 1999 00:27:44 +0900 (JST) Message-ID: <3857B2C4.3CA62441@newsguy.com> Date: Thu, 16 Dec 1999 00:24:52 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: Adam Strohl , Ryan Thompson , Peter Jeremy , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? References: <51308.945234648@zippy.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 "Jordan K. Hubbard" wrote: > > VESA syscons, either using libvgl and an array of crude widgets or > something like MGR and its widget set, has long been on the wish-list > but I didn't even include it in my summary since it's still very much > a pipe-dream. :-) There's actually one mode you forgot, which is Since no one seems to have spoken of it yet... GGI! GGI! I bet their X server is far smaller than XFree's, and we don't even _have_ to usa an X server. > what I call "text mode", and that's straight ascii prompts, no CUI-style > dialog boxes or anything. Think about text-to-speach devices for > the blind or serial consoles attached to really *dumb* terminals. :-) Sounds like CLI. :-) -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 7:30:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (dialfwn01.fwn.rug.nl [129.125.32.151]) by hub.freebsd.org (Postfix) with ESMTP id 4213414C34 for ; Wed, 15 Dec 1999 07:30:13 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id OAA00609; Wed, 15 Dec 1999 14:43:51 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Wed, 15 Dec 1999 14:43:51 +0100 (CET) From: Nick Hibma Reply-To: Nick Hibma To: Warner Losh Cc: FreeBSD CURRENT Mailing List Subject: Re: ed driver, resources not released (was: Re: PCCARD eject freeze) In-Reply-To: <199912071622.JAA41964@harmony.village.org> 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 Better news. I've recompiled the kernel just now and that did not make a difference. Then I recompiled pccardd and pccardc and I can now suspend/resume my machine at will (as in I've suspended the machine during the writing of this message). Thanks. Nick On Tue, 7 Dec 1999, Warner Losh wrote: > In message Nick Hibma writes: > : Hm, The machine is not crashing at the moment when unplugging the > : device. But plugging it back in gives me a 'No free configuration for > : card Ethernet' ('Ethernet' being the quite splendid name of the card in > : the CIS). > : > : A quick browse reveals the following difference between ep and ed. It > : doesn't have any effect however. > : > : Let me know if I can test anything. I'd like to get that working, but > : don't have the time to dig into this (utun driver is more important :) > > Quick question. If you kill and restart pccardd does the problem go > away? > > Warner > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 7:35:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as15-031.rp-plus.de [149.221.237.31]) by hub.freebsd.org (Postfix) with ESMTP id 4EB7B1529F for ; Wed, 15 Dec 1999 07:35:30 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id B4B0AAB7F; Wed, 15 Dec 1999 16:36:20 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id QAA04447; Wed, 15 Dec 1999 16:36:08 +0100 (CET) (envelope-from alex) Date: Wed, 15 Dec 1999 16:36:08 +0100 From: Alexander Langer To: "Don 'Duck' Harper" Cc: "Daniel C. Sobral" , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991215163608.A4358@cichlids.cichlids.com> Mail-Followup-To: Don 'Duck' Harper , "Daniel C. Sobral" , current@FreeBSD.ORG References: <38571717.F25976F7@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from duck@duckland.org on Tue, Dec 14, 1999 at 11:04:21PM -0600 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Don 'Duck' Harper (duck@duckland.org): > fires up XFree86's VGA server. And it fits all this on one floppy. They > do have two floppies, one for local CD/disk installs, and another for > NFS/FTP/HTTP/SMB installs. > So, I know it can be done. Is it worth the effort? I donno. Maybe they gzip the binaries and gunzip them into MFS before using them. gunzip has approx 106 kb, but you save about 50% per executeable. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 7:44:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id D7DC314A1B for ; Wed, 15 Dec 1999 07:44:39 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id QAA10387; Wed, 15 Dec 1999 16:44:19 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Khetan Gajjar Cc: current@FreeBSD.ORG Subject: Re: microuptime problem/error ? In-reply-to: Your message of "Wed, 15 Dec 1999 17:09:15 +0200." Date: Wed, 15 Dec 1999 16:44:19 +0100 Message-ID: <10385.945272659@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please send me the output of the following: xntpdc -c loopinfo xntpdc -c kerninfo xntpdc -c peer Poul-Henning In message , Khetan Gajjar writes: >Hi. > >I've started seeing "microuptime() went backwards" errors, followed >by calcru errors. I think it's related to phk's commit of >kern_resource.c (1.53) and kern_synch.c (1.84). > >What I don't understand is how is this possible if I'm using >xntpd to keep time, and my machine is reporting itself as a >stratum 3 server ? I have included three examples of the >microuptime and calcru error, and the output of ntptrace. > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 7:49:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from jasper.heartland.ab.ca (jasper.heartland.ab.ca [207.107.228.1]) by hub.freebsd.org (Postfix) with ESMTP id 00D87150D8 for ; Wed, 15 Dec 1999 07:48:57 -0800 (PST) (envelope-from dkwiebe@heartland.ab.ca) Received: from heartland.ab.ca (dyn109.heartland.ab.ca [207.107.228.109]) by jasper.heartland.ab.ca (8.9.0/8.9.0) with ESMTP id IAA18949; Wed, 15 Dec 1999 08:35:22 -0700 (MST) Message-ID: <3857AC6D.9DDA410B@heartland.ab.ca> Date: Wed, 15 Dec 1999 07:57:49 -0700 From: Darren Wiebe Reply-To: dkwiebe@hagenhomes.com Organization: Hagen Homes Ltd. X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: Kernel config utility References: <38578E57.BE6F50E1@cvzoom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Donn Miller wrote: > > So, would having a kernel config utility help us get better > reviews? I was thinking about something like an explorer-type > thing that was divided into two panes. On the left would be > LINT. Here, we would have icons representing the various > devices. For example, we could ahve an icon representing an > ethernet card, another icon representing a serial port, etc. On > the right hand side we would have the custom kernel config file. > You could just drag the icons over to the right hand side to add > devices to your kernel config. And, of course, you could always > just delete the icons you don't need. > I can definitely see advanatages, not that I would use it myself. :-) I also think that if it was written properly, which I'm sure that it would be, it could also be used to setup ppp etc.. > By clicking on the icons, a properties pane would show the > properties for this device. Of course, there should be some way > to represent options, such as DEVFS or SOFTUPDATES. Rather like MS registry editor. :-) > > Of course, I like using vi better, but I've heard some people > complaining about "how hard it is to configure a FreeBSD > kernel." I know I didn't fully convey the principles, but you > probably get the general idea. Of course, when you're down to > using teddy bears and talking parrots, then you know you've made > it too simple. :-] > > - Donn > Darren Wiebe dkwiebe@hagenhomes.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 7:54:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 815C215475 for ; Wed, 15 Dec 1999 07:54:41 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 753F21C4A; Wed, 15 Dec 1999 10:54:24 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 720AF381B; Wed, 15 Dec 1999 10:54:24 -0500 (EST) Date: Wed, 15 Dec 1999 10:54:24 -0500 (EST) From: Bill Fumerola To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: vinum start needs block device In-Reply-To: <19991213184634.S333@mojave.worldwide.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, 13 Dec 1999, Greg Lehey wrote: > > Note: this fixes some recent problems (Hi Greg!) that I've been > > having. > > Really? I thought they were more serious. So did I. Although, I did a 'make world' after I saw the change go in, so the fix could have come from a different commit. In any event 'vinum stripe /dev/da1e /dev/da2e' doesn't pagefault that machine anymore. PNPBIOS is a different story... -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 7:58:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 6E278154A5 for ; Wed, 15 Dec 1999 07:58:06 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11yGoW-0003Px-00 for freebsd-current@FreeBSD.ORG; Wed, 15 Dec 1999 17:58:04 +0200 From: Sheldon Hearn To: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" In-reply-to: Your message of "Wed, 15 Dec 1999 16:26:29 +0100." <199912151526.QAA28624@dorifer.heim3.tu-clausthal.de> Date: Wed, 15 Dec 1999 17:58:04 +0200 Message-ID: <13140.945273484@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 15 Dec 1999 16:26:29 +0100, Oliver Fromme wrote: > Sure, in that case, syscons itself should be a module, > shouldn't it? I would have thought so, yes. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 8: 8: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 89BAC15033; Wed, 15 Dec 1999 08:08:05 -0800 (PST) From: "Jonathan M. Bresler" To: dkwiebe@hagenhomes.com Cc: dmmiller@cvzoom.net, current@FreeBSD.ORG In-reply-to: <3857AC6D.9DDA410B@heartland.ab.ca> (message from Darren Wiebe on Wed, 15 Dec 1999 07:57:49 -0700) Subject: Re: Kernel config utility Message-Id: <19991215160805.89BAC15033@hub.freebsd.org> Date: Wed, 15 Dec 1999 08:08:05 -0800 (PST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > I can definitely see advanatages, not that I would use it myself. :-) I > also think that if it was written properly, which I'm sure that it would > be, it could also be used to setup ppp etc.. > > > By clicking on the icons, a properties pane would show the > > properties for this device. Of course, there should be some way > > to represent options, such as DEVFS or SOFTUPDATES. > > Rather like MS registry editor. :-) uh...NO! must be an ascii file that may be processed into a database format for use. we need something that cal be read, diff'ed, grep'ped, comm'ed, that can be backed up without problmes, that can be moved from host to host, .... jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 8:29:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id D46B51503B for ; Wed, 15 Dec 1999 08:29:24 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id RAA01525 for freebsd-current@FreeBSD.ORG; Wed, 15 Dec 1999 17:24:24 +0100 (CET) (envelope-from olli) Date: Wed, 15 Dec 1999 17:24:24 +0100 (CET) From: Oliver Fromme Message-Id: <199912151624.RAA01525@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? Organization: Administration TU Clausthal Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Langer wrote in list.freebsd-current: > Thus spake Don 'Duck' Harper (duck@duckland.org): > > fires up XFree86's VGA server. And it fits all this on one floppy. They > > do have two floppies, one for local CD/disk installs, and another for > > NFS/FTP/HTTP/SMB installs. > > So, I know it can be done. Is it worth the effort? I donno. > > Maybe they gzip the binaries and gunzip them into MFS before using > them. > > gunzip has approx 106 kb, but you save about 50% per executeable. -r-xr-xr-x 1 root wheel 4648 Jan 28 1999 /usr/bin/minigzip Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 8:31:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (dialfwn01.fwn.rug.nl [129.125.32.151]) by hub.freebsd.org (Postfix) with ESMTP id 566CE15495 for ; Wed, 15 Dec 1999 08:31:15 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id RAA00598; Wed, 15 Dec 1999 17:30:03 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Wed, 15 Dec 1999 17:30:03 +0100 (CET) From: Nick Hibma Reply-To: Nick Hibma To: Mark Newton Cc: "Jeremy L. Stock" , current@FreeBSD.ORG Subject: Re: Problem with sbc driver and/or newpcm In-Reply-To: <19991215232948.A1263@internode.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 Same here: henny:n_hibma# mixer Mixer vol is currently set to 75:75 Mixer synth is currently set to 0:0 Mixer pcm is currently set to 75:75 Mixer line is currently set to 75:75 Mixer mic is currently set to 0:0 Mixer cd is currently set to 75:75 sbc0: at port 0x220-0x22f,0x388-0x38b irq 5 drq 1,5 on isa0 pcm0: on sbc0 Nick On Wed, 15 Dec 1999, Mark Newton wrote: > On Wed, Dec 15, 1999 at 03:09:10AM -0600, Jeremy L. Stock wrote: > > > The sbc driver seems to correctly detect my soundcard for the first time > > since the introduction of newpcm but I don't actually get sound out of it. > > Just a quick check: Can you type "mixer" at a shell prompt and check > whether the reason you're getting no sound is because the master volume > level defaults to 0? > > - mark > > -- > Mark Newton Email: newton@internode.com.au (W) > Network Engineer Email: newton@atdot.dotat.org (H) > Internode Systems Pty Ltd Desk: +61-8-82232999 > "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 8:43:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 103F015241 for ; Wed, 15 Dec 1999 08:43:19 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id LAA27528; Wed, 15 Dec 1999 11:43:15 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id LAA18799; Wed, 15 Dec 1999 11:42:44 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 15 Dec 1999 11:42:44 -0500 (EST) To: freebsd-current@freebsd.org Cc: dillon@apollo.backplane.com Subject: Serious server-side NFS problem X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14423.46117.353932.473968@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a few "scratch" servers which are running -current from early July. They serve large, fast scratch filesystems striped over 4 large IDE drives. With the recent improvements to the NFS code & the ATA code, I was hoping to get them running a more recent -current. However, I'm seeing a showstopping problem when running newer kernels: When writing a large file via TCP, a Solaris 2.7 client pauses when closing the file, and appears to become stuck in an infinate loop. Eg: dd if=/dev/zero of=zot bs=64k count=8192 8192+0 records in 8192+0 records out ^C <------------- wedge The process does not exit, and there is a flurry of activity between the client & server: solaris -> freebsd ETHER Type=0800 (IP), size = 1514 bytes solaris -> freebsd IP D=152.3.X.Z S=152.3.X.Y LEN=1500, ID=16922 solaris -> freebsd TCP D=2049 S=843 Ack=94978376 Seq=1906025252 Len=1460 Win=8760 solaris -> freebsd RPC C XID=299504169 PROG=100003 (NFS) VERS=3 PROC=7 solaris -> freebsd NFS C WRITE3 FH=F5CB at 369655808 for 32768 (ASYNC) ________________________________ <....> freebsd -> solaris ETHER Type=0800 (IP), size = 218 bytes freebsd -> solaris IP D=152.3.X.Y S=152.3.X.Z LEN=204, ID=34565 freebsd -> solaris TCP D=843 S=2049 Ack=1906313520 Seq=94979688 Len=164 Win=33176 freebsd -> solaris RPC R (#5146) XID=299504169 Success freebsd -> solaris NFS R WRITE3 OK 32768 (ASYNC) ________________________________ <....> solaris -> freebsd ETHER Type=0800 (IP), size = 1514 bytes solaris -> freebsd IP D=152.3.X.Z S=152.3.X.Y LEN=1500, ID=49895 solaris -> freebsd TCP D=2049 S=843 Ack=96156528 Seq=2140928624 Len=1460 Win=8760 solaris -> freebsd RPC C XID=299511401 PROG=100003 (NFS) VERS=3 PROC=7 solaris -> freebsd NFS C WRITE3 FH=F5CB at 369655808 for 32768 (ASYNC) <...> ________________________________ freebsd -> solaris ETHER Type=0800 (IP), size = 218 bytes freebsd -> solaris IP D=152.3.X.Y S=152.3.X.Z LEN=204, ID=51011 freebsd -> solaris TCP D=843 S=2049 Ack=2140968864 Seq=96156856 Len=164 Win=33176 freebsd -> solaris RPC R (#18995) XID=299511401 Success freebsd -> solaris NFS R WRITE3 OK 32768 (A As you can see, the client seems to write the same block multiple times. I would think that this is not our fault, except things work just dandy with a kernel from July. In fact, the only way out of this situation is to reboot the FreeBSD NFS server into an older kernel. In the trace (about 30 seconds or so of the activity after dd finished, but before it exited) there are ~21,000 packets. There is a grand total of: NFS C WRITE3: 11024 NFS R WRITE3 OK: 10499 NFS C COMMIT3: 1 NFS R COMMIT3 OK: 1 In case more details are needed, I've left the complete trace in ~gallatin/nfs-trace.gz on freefall. Also, while read performance has improved by 44%, write performance has degraded by between 50 - 70% (FreeBSD clients)! Here are some quick benchmarks. Note that the file size of 512MB is larger than memory on both the server and client. Also note that the disk array on the server will read at 50MB/sec and write at 40MB/sec, so we are not disk bound ;-) - UDP NFS write performance from a FreeBSD client: July's kernel: % dd if=/dev/zero of=zot bs=1024k count=512 512+0 records in 512+0 records out 536870912 bytes transferred in 52.780773 secs (10171714 bytes/sec) Today's kernel:: % dd if=/dev/zero of=zot bs=1024k count=512 512+0 records in 512+0 records out 536870912 bytes transferred in 141.593458 secs (3791636 bytes/sec) -- TCP NFS write performnace from a FreeBSD client: July's kernel: % dd if=/dev/zero of=zot bs=1024k count=512 512+0 records in 512+0 records out 536870912 bytes transferred in 69.935044 secs (7676708 bytes/sec) Today's kernel: % dd if=/dev/zero of=zot bs=1024k count=512 512+0 records in 512+0 records out 536870912 bytes transferred in 162.074402 secs (3312497 bytes/sec) UDP NFS Read performance has gotten better: July's kernel: % dd if=zot of=/dev/null bs=64k 8192+0 records in 8192+0 records out 536870912 bytes transferred in 84.621477 secs (6344381 bytes/sec) Today's kernel: dd if=zot of=/dev/null bs=64k 8192+0 records in 8192+0 records out 536870912 bytes transferred in 58.544409 secs (9170319 bytes/sec) Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 8:45:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22]) by hub.freebsd.org (Postfix) with ESMTP id 606CB150E4 for ; Wed, 15 Dec 1999 08:45:41 -0800 (PST) (envelope-from veldy@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id A598E3904 for ; Wed, 15 Dec 1999 10:45:39 -0600 (CST) Received: from localhost (veldy@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id KAA18075 for ; Wed, 15 Dec 1999 10:45:39 -0600 (CST) X-Authentication-Warning: isis.visi.com: veldy owned process doing -bs Date: Wed, 15 Dec 1999 10:45:39 -0600 (CST) From: Thomas Veldhouse To: freebsd-current@freebsd.org Subject: Sound Blaster 128 PCI (ESS1371) support in current? 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 Does the newpcm system support the Sound Blaster 128 PCI card (ESS1371 chipset)? I am aware of a pcm dirver for it in STABLE, but I have not tried it. Tom Veldhouse veldy@visi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 8:52: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 2B0D8155F2; Wed, 15 Dec 1999 08:51:56 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id LAA21798; Wed, 15 Dec 1999 11:49:56 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Wed, 15 Dec 1999 11:49:56 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Peter Wemm Cc: Greg Lehey , Mike Smith , Greg Childers , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <19991213234037.36B341CA0@overcee.netplex.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, 14 Dec 1999, Peter Wemm wrote: > The RZ1000 is *dangerous*! We are doing no favours by making it run.. :-/ > IMHO It is better to loose the user by not playing ball than to corrupt > their data or run unreliably and make them hate us for it. > > http://www.faqs.org/faqs/pc-hardware-faq/enhanced-IDE/part1/ ... > > In both cases, the corruption occurs only in specific software > environments and is very subtle; you can go on working for months > without suspecting anything more than buggy software. The damage can > be immense. For all the details, look at Roedy Green's (roedy@bix.com) > "PCI EIDE controller flaws" FAQ included with his EIDE test > program which will > test your system for the bugs. > > BE WARNED that you're playing Russian roulette with your data if you > continue working on an affected machine without taking notice of this > problem. Since someone has code to detect these, how about putting this code in the ata driver probe so it can say something appropriately obscene and we start getting feedback about how widely deployed they are, and so that users can evaluate their risk in using the new driver? There's also mention of being able to disable features in the bios to fix this--is this a workaround that can be initiated from user software in a useful way? I.e., if the ata driver detects bad hardware, it pulls in a loadable kernel module that would somehow address the problem, or avoids the issues which cause corruption, if identifiable? Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 8:58: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 15B59150E4 for ; Wed, 15 Dec 1999 08:58:02 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA76804; Wed, 15 Dec 1999 09:58:00 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA61335; Wed, 15 Dec 1999 09:58:00 -0700 (MST) Message-Id: <199912151658.JAA61335@harmony.village.org> To: Bruce Albrecht Subject: Re: Upgrading from a not-very-current current Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 15 Dec 1999 01:24:40 CST." <14423.16952.518144.298755@celery.zuhause.org> References: <14423.16952.518144.298755@celery.zuhause.org> Date: Wed, 15 Dec 1999 09:58:00 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14423.16952.518144.298755@celery.zuhause.org> Bruce Albrecht writes: : I know that I need to build the tools for config, and build a new : kernel, and reboot it before doing a make world. My question is, : after booting the new kernel, do I run MAKEDEV immediately, or do I run : make world before runnning MAKEDEV? Would it be prudent to disable : softupdates until after I'm done upgrading? I'd do the MAKEDEV stuff, as described in UPDATING, before you did the reboot for the make world. It likely doesn't matter much, but you are better off safe than sorry. : Would it be simpler to install from the latest -current snap? Maybe. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 9: 1:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from modemcable156.106-200-24.mtl.mc.videotron.net (modemcable126.102-200-24.mtl.mc.videotron.net [24.200.102.126]) by hub.freebsd.org (Postfix) with SMTP id 93EBC14BD6 for ; Wed, 15 Dec 1999 09:01:54 -0800 (PST) (envelope-from patrick@mindstep.com) Received: (qmail 30267 invoked from network); 15 Dec 1999 17:01:53 -0000 Received: from patrak.local.mindstep.com (HELO patrak) (192.168.10.4) by jacuzzi.local.mindstep.com with SMTP; 15 Dec 1999 17:01:53 -0000 Message-ID: <003a01bf471e$16185e70$040aa8c0@local.mindstep.com> From: "Patrick Bihan-Faou" To: References: <3857AC6D.9DDA410B@heartland.ab.ca> <19991215160805.89BAC15033@hub.freebsd.org> Subject: Re: Kernel config utility Date: Wed, 15 Dec 1999 12:01:53 -0500 Organization: MindStep Corporation 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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Rather than going in horror shows like a registry editor look alike for the kernel config, I think that there is a somewhat better approach to the kernel configuration task. Has anybody taken a look at the configuration script on RedHat-Linux distributions ? I don't know if it is RedHat specific or generic to all Linux distribution, but it is really nice. You just have to type "make menuconfig" and here you go with a fairly well structure presentation of the options you have to configure the kernel. The thingy also manages basic dependencies between kernel options etc. It is really easy to understand even for the non-expert, and for purists/gurus you still have the text file to play around... > must be an ascii file that may be processed into a database > format for use. we need something that cal be read, diff'ed, > grep'ped, comm'ed, that can be backed up without problmes, that can be > moved from host to host, .... I agree with that part. And I would also add that we need something that can be used even if you don't have X11 installed... Just my 2 cents. Patrick. -- www.mindstep.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 9: 3:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext03.compaq.com (mailext03.compaq.com [207.18.199.41]) by hub.freebsd.org (Postfix) with ESMTP id 624F61503D for ; Wed, 15 Dec 1999 09:03:25 -0800 (PST) (envelope-from bruceb@txn.cpqcorp.net) Received: by mailext03.compaq.com (Postfix, from userid 12345) id 3B611152184; Wed, 15 Dec 1999 11:03:24 -0600 (CST) Received: from mailint02.im.hou.compaq.com (mailint02.compaq.com [207.18.199.35]) by mailext03.compaq.com (Postfix) with ESMTP id 377FC148506 for ; Wed, 15 Dec 1999 11:03:24 -0600 (CST) Received: by mailint02.im.hou.compaq.com (Postfix, from userid 12345) id 22058BC4D4; Wed, 15 Dec 1999 11:03:17 -0600 (CST) Received: from fedex-s1.txn.cpqcorp.net (fedex-s1.txn.cpqcorp.net [16.74.4.108]) by mailint02.im.hou.compaq.com (Postfix) with ESMTP id 8667CB2A43 for ; Wed, 15 Dec 1999 11:03:16 -0600 (CST) From: Bruce Burden Posted-Date: Wed, 15 Dec 1999 11:03:22 -0600 (CST) Received: (from bruceb@localhost) by panther.txn.cpqcorp.net (8.9.3/8.9.3) id KAA22301 for freebsd-current@freebsd.org; Wed, 15 Dec 1999 10:59:35 -0600 (CST) Message-Id: <199912151659.KAA22301@panther.txn.cpqcorp.net> Subject: libcc_drv.a fails to compile on 12/14 sup To: freebsd-current@freebsd.org Date: Wed, 15 Dec 1999 10:59:35 -0600 (CST) Reply-To: bruceb@devnull.mpd.tandem.com 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 Hi, I am attempting to build the source, and am getting the following error: cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc/../../../../contrib/gcc/config -I/usr/obj/usr/src/i386/usr/include -o cc gcc.o gccspec.o /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a(choose-temp.o): In function `make_temp_file': choose-temp.o(.text+0x264): undefined reference to `mkstemps' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. # And, yes, I did build the config source, I did build the -current kernel, yes, I did boot on the -current kernel, yes I did copy the /src/etc/MAKEDEV and run that, and yes, when the build failed at this spot on the 12/13 cvsup, I reran sup and tried again. With the same results on the 12/14 sup. Yet I see people are getting their builds to work. Okay, what did I miss? Thank you, Bruce -- ------------------------------------------------------------------------------- Bruce Burden bruceb@isd.tandem.com Tandem Computers Inc. 512-432-8944 Network Verification 14231 Tandem Blvd. Auto answer(4 rings) Austin, TX 78726 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 9: 8:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7B508154CF for ; Wed, 15 Dec 1999 09:08:12 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA76846 for ; Wed, 15 Dec 1999 10:08:11 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA61414 for ; Wed, 15 Dec 1999 10:08:11 -0700 (MST) Message-Id: <199912151708.KAA61414@harmony.village.org> To: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" In-reply-to: Your message of "Wed, 15 Dec 1999 16:19:49 +0100." <199912151519.QAA28467@dorifer.heim3.tu-clausthal.de> References: <199912151519.QAA28467@dorifer.heim3.tu-clausthal.de> Date: Wed, 15 Dec 1999 10:08:11 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912151519.QAA28467@dorifer.heim3.tu-clausthal.de> Oliver Fromme writes: : That's because X itself contains a very simple "windowmanager" : functionality, which focuses the window beneath the mouse : pointer. But when you have to access something which is behind : another window, you lose. That's not entirely true. The X server does not contain a window manager at all. It doesn't implement any of the ICCCM required for window managers. All it does is have a default focus polcy of focus on root. This ensures that focus follows pointer works until one of the applications does a XSetFocus to take the focus (which normally it would only do if it was poorly written since it is only supposed to do that in response to ICCCM messages). There is no placement management, no redirection of windows, no visibility management or anything of the sort in the X server. It just has mechanisms which allow one to do these things. "Tools, not rules," being the motto from long ago... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 9:11: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9B1AB154DB for ; Wed, 15 Dec 1999 09:11:03 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA32205; Wed, 15 Dec 1999 09:11:01 -0800 (PST) (envelope-from dillon) Date: Wed, 15 Dec 1999 09:11:01 -0800 (PST) From: Matthew Dillon Message-Id: <199912151711.JAA32205@apollo.backplane.com> To: Andrew Gallatin Cc: freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem References: <14423.46117.353932.473968@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :However, I'm seeing a showstopping problem when running newer kernels: :When writing a large file via TCP, a Solaris 2.7 client pauses when :closing the file, and appears to become stuck in an infinate loop. :Eg: : :dd if=/dev/zero of=zot bs=64k count=8192 :8192+0 records in :8192+0 records out :^C <------------- wedge : :The process does not exit, and there is a flurry of activity between :the client & server: : :solaris -> freebsd NFS C WRITE3 FH=F5CB at 369655808 for 32768 (ASYNC) :________________________________ :freebsd -> solaris TCP D=843 S=2049 Ack=1906313520 Seq=94979688 Len=164 Win=33176 :freebsd -> solaris RPC R (#5146) XID=299504169 Success :freebsd -> solaris NFS R WRITE3 OK 32768 (ASYNC) :________________________________ This is very odd. Does it lockup with UDP or only with TCP? And only with a solaris client? It's possible that the problem may be related to changes in the TCP stack rather then related to NFS. Looking at your trace output I don't see anything wrong beyond the solaris client apparently repeating write requests. Another possibility is that we somehow nixed the commit rpc. All the repeated writes occur after the commit rpc. In the protocol trace, though, the commit rpc succeeds. Very odd! :I would think that this is not our fault, except things work just dandy :with a kernel from July. In fact, the only way out of this situation :is to reboot the FreeBSD NFS server into an older kernel. : :In the trace (about 30 seconds or so of the activity after dd :finished, but before it exited) there are ~21,000 packets. There is a :grand total of: : :NFS C WRITE3: 11024 :NFS R WRITE3 OK: 10499 :NFS C COMMIT3: 1 :NFS R COMMIT3 OK: 1 : :In case more details are needed, I've left the complete trace in :~gallatin/nfs-trace.gz on freefall. I've looked at it -- it looks normal except for the repeated writes. :Also, while read performance has improved by 44%, write performance :has degraded by between 50 - 70% (FreeBSD clients)! Here are some :quick benchmarks. Note that the file size of 512MB is larger than :memory on both the server and client. Also note that the disk array :on the server will read at 50MB/sec and write at 40MB/sec, so we are :not disk bound ;-) : :- UDP NFS write performance from a FreeBSD client: Ok, I'll take a look at it. I get 9 MBytes/sec writing over UDP links but only with fast (400MHz class) clients. With a 200 MHz class client I am only getting 4-5 MBytes/sec. Frankly, I should be getting 9 MB/sec even with the slower client! :UDP NFS Read performance has gotten better: : :July's kernel: :% dd if=zot of=/dev/null bs=64k :8192+0 records in :8192+0 records out :536870912 bytes transferred in 84.621477 secs (6344381 bytes/sec) : :Today's kernel: :dd if=zot of=/dev/null bs=64k :8192+0 records in :8192+0 records out :536870912 bytes transferred in 58.544409 secs (9170319 bytes/sec) : :Cheers, : :Drew Yes, read performance has been improved in just the last few days simply by adding a read heuristic to the server side for transfers off the physical media. -Matt Matthew Dillon :------------------------------------------------------------------------------ :Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin :Duke University Email: gallatin@cs.duke.edu :Department of Computer Science Phone: (919) 660-6590 : : : :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 Dec 15 9:13:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A417B15338 for ; Wed, 15 Dec 1999 09:13:06 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA76873; Wed, 15 Dec 1999 10:13:04 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA61491; Wed, 15 Dec 1999 10:13:03 -0700 (MST) Message-Id: <199912151713.KAA61491@harmony.village.org> To: Thomas Veldhouse Subject: Re: Sound Blaster 128 PCI (ESS1371) support in current? Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 15 Dec 1999 10:45:39 CST." References: Date: Wed, 15 Dec 1999 10:13:03 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Thomas Veldhouse writes: : Does the newpcm system support the Sound Blaster 128 PCI card (ESS1371 : chipset)? I am aware of a pcm dirver for it in STABLE, but I have not : tried it. Looking at src/sys/dev/sound/pci/es137x.c, we find the comment: * Support the ENSONIQ AudioPCI board and Creative Labs SoundBlaster PCI * boards based on the ES1370, ES1371 and ES1373 chips. and it probes my es1370 board properly. Haven't tried to play my mp3s on it yet. pcm0: irq 5 at device 17.0 on pci0 Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 9:14: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D829C150E4 for ; Wed, 15 Dec 1999 09:14:05 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA76878; Wed, 15 Dec 1999 10:14:03 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA61510; Wed, 15 Dec 1999 10:14:03 -0700 (MST) Message-Id: <199912151714.KAA61510@harmony.village.org> To: bruceb@devnull.mpd.tandem.com Subject: Re: libcc_drv.a fails to compile on 12/14 sup Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 15 Dec 1999 10:59:35 CST." <199912151659.KAA22301@panther.txn.cpqcorp.net> References: <199912151659.KAA22301@panther.txn.cpqcorp.net> Date: Wed, 15 Dec 1999 10:14:03 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912151659.KAA22301@panther.txn.cpqcorp.net> Bruce Burden writes: : Yet I see people are getting their builds to work. Okay, what : did I miss? Looks like a bug to me... What is the date/version of the system you are updating? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 9:21:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id D3999154DE for ; Wed, 15 Dec 1999 09:21:15 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 16334 invoked from network); 15 Dec 1999 17:21:14 -0000 Received: from lcb13.cvzoom.net (63.65.159.13) by ns.cvzoom.net with SMTP; 15 Dec 1999 17:21:14 -0000 Date: Wed, 15 Dec 1999 12:20:13 -0500 (EST) From: Donn Miller To: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" In-Reply-To: <199912151708.KAA61414@harmony.village.org> 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, 15 Dec 1999, Warner Losh wrote: > In message <199912151519.QAA28467@dorifer.heim3.tu-clausthal.de> Oliver Fromme writes: > : That's because X itself contains a very simple "windowmanager" > : functionality, which focuses the window beneath the mouse > : pointer. But when you have to access something which is behind > : another window, you lose. > > That's not entirely true. The X server does not contain a window > There is no placement management, no redirection of windows, no > visibility management or anything of the sort in the X server. It But, if there's only one app running, then that app gets the focus. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 9:23:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22]) by hub.freebsd.org (Postfix) with ESMTP id 42AEB1539C for ; Wed, 15 Dec 1999 09:23:52 -0800 (PST) (envelope-from veldy@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id 54D3C3806; Wed, 15 Dec 1999 11:23:51 -0600 (CST) Received: from localhost (veldy@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id LAA20539; Wed, 15 Dec 1999 11:23:51 -0600 (CST) X-Authentication-Warning: isis.visi.com: veldy owned process doing -bs Date: Wed, 15 Dec 1999 11:23:50 -0600 (CST) From: Thomas Veldhouse To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: Sound Blaster 128 PCI (ESS1371) support in current? In-Reply-To: <199912151713.KAA61491@harmony.village.org> 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 Thanks, I will CVSUP tonight and try out the new sound and ATA at the same time. I am runing on an AMD board (Compaq style 751 chipset) with a 200MHz FSB. Promises to be interesting with ATA and sound. Everthing always takes work with this board, because I can't disable PNP. Tom Veldhouse veldy@visi.com On Wed, 15 Dec 1999, Warner Losh wrote: > In message Thomas Veldhouse writes: > : Does the newpcm system support the Sound Blaster 128 PCI card (ESS1371 > : chipset)? I am aware of a pcm dirver for it in STABLE, but I have not > : tried it. > > Looking at src/sys/dev/sound/pci/es137x.c, we find the comment: > > * Support the ENSONIQ AudioPCI board and Creative Labs SoundBlaster PCI > * boards based on the ES1370, ES1371 and ES1373 chips. > > and it probes my es1370 board properly. Haven't tried to play my mp3s > on it yet. > > pcm0: irq 5 at device 17.0 on pci0 > > Warner > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 9:24:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from barracuda.aquarium.rtci.com (barracuda.aquarium.rtci.com [208.11.247.5]) by hub.freebsd.org (Postfix) with ESMTP id E45E51552F for ; Wed, 15 Dec 1999 09:24:19 -0800 (PST) (envelope-from tstromberg@rtci.com) Received: from rtci.com (localhost [127.0.0.1]) by barracuda.aquarium.rtci.com (8.9.3+Sun/8.9.3) with SMTP id MAA00818 for freebsd-current@freebsd.org; Wed, 15 Dec 1999 12:24:22 -0500 (EST) Date: Wed, 15 Dec 1999 12:24:22 -0500 (EST) Message-Id: <199912151724.MAA00818@barracuda.aquarium.rtci.com> To: freebsd-current@freebsd.org Subject: kernel crash via /usr/bin/ktrace From: X-Mailer: TWIG 2.0.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While testing ktrace today for the FreeBSD-Audit project with smashwidgets, I left the room and came back to my bios booting up. Unfortunatly smashwidgets wasn't in full logging mode for speed, so I don't know what arguments or environment variablesm were executed to trigger the crash. What annoys me the most is that I can't seem to reproduce it, even though I reran the tests 3 times. But, it still represents some kind of bug.. environment: ============ PIII-500, 96M RAM, 786M swap Running X & smashwidgets (both running as nornmal users, not root) Load of ~2.0 kernel: ======= FreeBSD karma.afterthought.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Dec 13 16:31:04 EST 1999 chenresig@karma.afterthought.org:/usr/src/sys/compile/KARMA i386 backtrace: ========== IdlePTD 3084288 initial pcb at 27bb60 panicstr: vrele: negative ref cnt panic messages: --- panic: vrele: negative ref cnt syncing disks... 11 2 done Uptime: 1d0h12m5s dumping to dev #wd/0x20001, offset 1413889 dump ata0: resetting devices .. done 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:303 303 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:303 #1 0xc0133d01 in panic (fmt=0xc023a662 "vrele: negative ref cnt") at ./../kern/kern_shutdown.c:553 #2 0xc015c8c2 in vrele (vp=0xcce4d8e0) at ../../kern/vfs_subr.c:1426 #3 0xc012ed6d in ktrops (curp=0xccfd0180, p=0xccfd1c80, ops=1, facs=254, vp=0x0) at ../../kern/kern_ktrace.c:422 #4 0xc012edaa in ktrsetchildren (curp=0xccfd0180, top=0xcc5e7e00, ops=1, facs=254, vp=0x0) at ../../kern/kern_ktrace.c:442 #5 0xc012ebda in ktrace (curp=0xccfd0180, uap=0xcd06ef80) at ./../kern/kern_ktrace.c:343 #6 0xc0222972 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077969896, tf_esi = 1, tf_ebp = -1077969988, tf_isp = -855183404, tf_ebx = 1, tf_edx = 672046132, tf_ecx = 11, tf_eax = 45, tf_trapno = 12, tf_err = 2, tf_eip = 671715924, tf_cs = 31, tf_eflags = 582, tf_esp = -1077970160, tf_ss = 47}) at ../../i386/i386/trap.c:1057 #7 0xc0217376 in Xint0x80_syscall () #8 0x8048751 in ?? () To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 9:30:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.tn.home.com (ha1.rdc1.tn.home.com [24.2.7.66]) by hub.freebsd.org (Postfix) with ESMTP id D74A7154ED for ; Wed, 15 Dec 1999 09:30:34 -0800 (PST) (envelope-from dakuntz@home.com) Received: from windows ([24.2.16.41]) by mail.rdc1.tn.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <19991215173029.POSJ17996.mail.rdc1.tn.home.com@windows>; Wed, 15 Dec 1999 09:30:29 -0800 Message-ID: <00ab01bf4722$58108100$29100218@micronetinfo.com> From: "Douglas Kuntz" To: "Patrick Bihan-Faou" , References: <3857AC6D.9DDA410B@heartland.ab.ca> <19991215160805.89BAC15033@hub.freebsd.org> <003a01bf471e$16185e70$040aa8c0@local.mindstep.com> Subject: Re: Kernel config utility Date: Wed, 15 Dec 1999 12:32:21 -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 5.50.3825.400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.3825.400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That script(scripts) is part of the Kernel, and not Redhat specific. It has 3 options, too.. make config which is text only (ie: do you want xyz? (yes/no)), make menuconfig (uses python I think), and make xconfig, so it works with most peoples preferences. It worked pretty well most of the time...except I now like being able to my editor of choices "find" command to find something, instead of searching through lots of menus and submenus. Doug ----- Original Message ----- From: "Patrick Bihan-Faou" To: Sent: Wednesday, December 15, 1999 12:01 PM Subject: Re: Kernel config utility > Hi, > > > Rather than going in horror shows like a registry editor look alike for the > kernel config, I think that there is a somewhat better approach to the > kernel configuration task. Has anybody taken a look at the configuration > script on RedHat-Linux distributions ? I don't know if it is RedHat specific > or generic to all Linux distribution, but it is really nice. > > You just have to type "make menuconfig" and here you go with a fairly well > structure presentation of the options you have to configure the kernel. The > thingy also manages basic dependencies between kernel options etc. > > It is really easy to understand even for the non-expert, and for > purists/gurus you still have the text file to play around... > > > > must be an ascii file that may be processed into a database > > format for use. we need something that cal be read, diff'ed, > > grep'ped, comm'ed, that can be backed up without problmes, that can be > > moved from host to host, .... > > > I agree with that part. And I would also add that we need something that can > be used even if you don't have X11 installed... > > > Just my 2 cents. > > Patrick. > > -- > www.mindstep.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 Dec 15 9:35:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 65F641552E for ; Wed, 15 Dec 1999 09:35:17 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id MAA28819; Wed, 15 Dec 1999 12:35:15 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id MAA18905; Wed, 15 Dec 1999 12:34:45 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 15 Dec 1999 12:34:45 -0500 (EST) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-Reply-To: <199912151711.JAA32205@apollo.backplane.com> References: <14423.46117.353932.473968@grasshopper.cs.duke.edu> <199912151711.JAA32205@apollo.backplane.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14423.52876.91488.48428@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > This is very odd. Does it lockup with UDP or only with TCP? And only > with a solaris client? This appears to be solaris only. I just tried a UDP mount & I see the same problem. Is there anything else I can do? <...> > : > :- UDP NFS write performance from a FreeBSD client: > > Ok, I'll take a look at it. I get 9 MBytes/sec writing over UDP links > but only with fast (400MHz class) clients. With a 200 MHz class client > I am only getting 4-5 MBytes/sec. Frankly, I should be getting 9 MB/sec > even with the slower client! The client and server here are both 450MHz machines. The server and client are identical (450MHz PII (or PIII), etherexpress pro nics) except that the server has 384MB of ram and the client has 64MB. The client was running a kernel from last week. My desktop (196 MB 300MHZ PII) shows similar behaviour -- a drop from 7MB/s to 3MB/s. It is running a kernel from Monday. <...> > Yes, read performance has been improved in just the last few days > simply by adding a read heuristic to the server side for transfers off > the physical media. Nice! Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 9:38:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id C54D9154EF for ; Wed, 15 Dec 1999 09:38:45 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 18917 invoked from network); 15 Dec 1999 17:38:44 -0000 Received: from lcb13.cvzoom.net (63.65.159.13) by ns.cvzoom.net with SMTP; 15 Dec 1999 17:38:44 -0000 Date: Wed, 15 Dec 1999 12:37:43 -0500 (EST) From: Donn Miller To: Thomas Veldhouse Cc: Warner Losh , freebsd-current@FreeBSD.ORG Subject: Re: Sound Blaster 128 PCI (ESS1371) support in current? 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, 15 Dec 1999, Thomas Veldhouse wrote: > I will CVSUP tonight and try out the new sound and ATA at the same > time. I am runing on an AMD board (Compaq style 751 chipset) with a > 200MHz FSB. Promises to be interesting with ATA and sound. Everthing > always takes work with this board, because I can't disable PNP. I've got the ESS 1868 chipset, and all I get is static. In fact, when I press the "play" button in RealPlayer, the sound clip never starts but hangs in the beginning. Then, RealPlayer itself hangs. I end up killing RealPlayer with killall -15 rvplayer. I too just made world, and remade my audio devices. Just to be sure, which command is it? Is it both ./MAKEDEV pcaudio ./MAKEDEV snd0 or just one of those? - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 9:39:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id BE6C3154F9 for ; Wed, 15 Dec 1999 09:39:12 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA32687; Wed, 15 Dec 1999 09:39:07 -0800 (PST) (envelope-from dillon) Date: Wed, 15 Dec 1999 09:39:07 -0800 (PST) From: Matthew Dillon Message-Id: <199912151739.JAA32687@apollo.backplane.com> To: Andrew Gallatin Cc: freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem References: <14423.46117.353932.473968@grasshopper.cs.duke.edu> <199912151711.JAA32205@apollo.backplane.com> <14423.52876.91488.48428@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : :Matthew Dillon writes: : > This is very odd. Does it lockup with UDP or only with TCP? And only : > with a solaris client? : :This appears to be solaris only. I just tried a UDP mount & I see the :same problem. Is there anything else I can do? Yes, see if you can repeat the problem with a shorter dd count -- see how small a count you can achieve and still produce the problem, then do a nice long protocol trace. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 9:41:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id B24BC15477 for ; Wed, 15 Dec 1999 09:41:49 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id MAA08347; Wed, 15 Dec 1999 12:41:39 -0500 (EST) (envelope-from wollman) Date: Wed, 15 Dec 1999 12:41:39 -0500 (EST) From: Garrett Wollman Message-Id: <199912151741.MAA08347@khavrinen.lcs.mit.edu> To: Donn Miller Cc: current@FreeBSD.ORG Subject: Kernel config utility In-Reply-To: <38578E57.BE6F50E1@cvzoom.net> References: <38578E57.BE6F50E1@cvzoom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > thing that was divided into two panes. On the left would be > LINT. Here, we would have icons representing the various > devices. This is actually a really cool idea, although it needs a bit of refinement, and we would need to start providing and maintaining a database which describes the drivers in more detail. You don't want to start with LINT, though; you want to start with GENERIC plus a few of the more common options. (Then provide a menu selection of the form ``Show all available devices and options''.) Icons are probably not the right user interface. I'd suggest something like Windows's ``hardware manager'' (in the System control panel). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 9:52:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 8EB1215154 for ; Wed, 15 Dec 1999 09:52:10 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 20398 invoked from network); 15 Dec 1999 17:52:09 -0000 Received: from lcb13.cvzoom.net (63.65.159.13) by ns.cvzoom.net with SMTP; 15 Dec 1999 17:52:09 -0000 Date: Wed, 15 Dec 1999 12:51:08 -0500 (EST) From: Donn Miller To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: Kernel config utility In-Reply-To: <199912151741.MAA08347@khavrinen.lcs.mit.edu> 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, 15 Dec 1999, Garrett Wollman wrote: > Icons are probably not the right user interface. I'd suggest > something like Windows's ``hardware manager'' (in the System control > panel). Some people were afraid that it would end up like the Windows registry. Well, even if it did, I'd argue that it still wouldn't be too bad. The Windows registry has so many classes and entries, and I think the kernel config would be smaller with not as many classes. You'd have the device class, and options class. Then, you'd break devices down into scsi, ide, etc. Or, we could break them down into network, disk controllers, sound, that way. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 9:58: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id B651015298 for ; Wed, 15 Dec 1999 09:57:57 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id SAA64385; Wed, 15 Dec 1999 18:57:38 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912151757.SAA64385@freebsd.dk> Subject: Re: Sound Blaster 128 PCI (ESS1371) support in current? In-Reply-To: from Thomas Veldhouse at "Dec 15, 1999 11:23:50 am" To: veldy@visi.com (Thomas Veldhouse) Date: Wed, 15 Dec 1999 18:57:38 +0100 (CET) Cc: imp@village.org (Warner Losh), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Thomas Veldhouse wrote: > Thanks, > > I will CVSUP tonight and try out the new sound and ATA at the same > time. I am runing on an AMD board (Compaq style 751 chipset) with a > 200MHz FSB. Promises to be interesting with ATA and sound. Everthing > always takes work with this board, because I can't disable PNP. Works like a charm, or at least my K7M +SB PCI128 does... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 9:58:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2DC4415530 for ; Wed, 15 Dec 1999 09:58:13 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA77091; Wed, 15 Dec 1999 10:58:10 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA61919; Wed, 15 Dec 1999 10:58:09 -0700 (MST) Message-Id: <199912151758.KAA61919@harmony.village.org> To: Donn Miller Subject: Re: Sound Blaster 128 PCI (ESS1371) support in current? Cc: Thomas Veldhouse , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 15 Dec 1999 12:37:43 EST." References: Date: Wed, 15 Dec 1999 10:58:09 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Donn Miller writes: : I've got the ESS 1868 chipset, and all I get is static. In fact, when I : press the "play" button in RealPlayer, the sound clip never starts but : hangs in the beginning. Then, RealPlayer itself hangs. I end up killing : RealPlayer with killall -15 rvplayer. I too just made world, and remade : my audio devices. Don't know about the 1868. Just know that my ess1370 probes on boot. : Just to be sure, which command is it? Is it both : ./MAKEDEV pcaudio : ./MAKEDEV snd0 : or just one of those? No clue. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 9:58:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.infolibria.com (mail.infolibria.com [199.103.137.198]) by hub.freebsd.org (Postfix) with ESMTP id 1C0EA15637 for ; Wed, 15 Dec 1999 09:58:52 -0800 (PST) (envelope-from loverso@infolibria.com) Received: from infolibria.com (border [199.103.137.193]) by mail.infolibria.com (Postfix) with ESMTP id E536BDDB82 for ; Wed, 15 Dec 1999 12:58:48 -0500 (EST) Message-ID: <3857D6FB.A95BFE4@infolibria.com> Date: Wed, 15 Dec 1999 12:59:23 -0500 From: John LoVerso X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Kernel config utility References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Some people were afraid that it would end up like the Windows registry. But it wouldn't, because that isn't the right thing. A kernel config utility should end up functioning like XF86Setup. When was the last time most people made an XF86Config file since that program came around? > and we would need to start providing and maintaining a > database which describes the drivers in more detail. Exactly! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 10: 3: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 21A8C150E4; Wed, 15 Dec 1999 10:03:03 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id TAA65973; Wed, 15 Dec 1999 19:01:59 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912151801.TAA65973@freebsd.dk> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: from Robert Watson at "Dec 15, 1999 11:49:56 am" To: robert+freebsd@cyrus.watson.org (Robert Watson) Date: Wed, 15 Dec 1999 19:01:59 +0100 (CET) Cc: peter@netplex.com.au (Peter Wemm), grog@lemis.com (Greg Lehey), msmith@FreeBSD.ORG (Mike Smith), gchil0@pop.uky.edu (Greg Childers), phk@critter.freebsd.dk (Poul-Henning Kamp), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Robert Watson wrote: > On Tue, 14 Dec 1999, Peter Wemm wrote: > > > The RZ1000 is *dangerous*! We are doing no favours by making it run.. :-/ > > IMHO It is better to loose the user by not playing ball than to corrupt > > their data or run unreliably and make them hate us for it. > > > > http://www.faqs.org/faqs/pc-hardware-faq/enhanced-IDE/part1/ Amen! > Since someone has code to detect these, how about putting this code in the > ata driver probe so it can say something appropriately obscene and we > start getting feedback about how widely deployed they are, and so that > users can evaluate their risk in using the new driver? There's also > mention of being able to disable features in the bios to fix this--is this > a workaround that can be initiated from user software in a useful way? > I.e., if the ata driver detects bad hardware, it pulls in a loadable > kernel module that would somehow address the problem, or avoids the issues > which cause corruption, if identifiable? That particular chip is so broken in so obscure ways, that most of the "fixes" floating around doesn't. Its just plain broken, and should be avoided totally and at all cost... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 10:14:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id E5C5415503 for ; Wed, 15 Dec 1999 10:14:47 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p13-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.142]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id DAA19080; Thu, 16 Dec 1999 03:14:28 +0900 (JST) Message-ID: <3857D2A3.5F0DCCE0@newsguy.com> Date: Thu, 16 Dec 1999 02:40:51 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: chris@calldei.com Cc: "Jordan K. Hubbard" , Donn Miller , Eric Jones , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? References: <3855F364.E66EC87B@cvzoom.net> <2683.945164965@zippy.cdrom.com> <19991214173714.W868@holly.calldei.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Costello wrote: > > So is all of this (TCL, Qt, et. al.) going into the base > system to facilitate this work? NOT AGAIN! Please! In particular TCL. -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 10:15: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 720C01549A for ; Wed, 15 Dec 1999 10:14:48 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p13-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.142]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id DAA19073; Thu, 16 Dec 1999 03:14:23 +0900 (JST) Message-ID: <3857D1B0.66C930F9@newsguy.com> Date: Thu, 16 Dec 1999 02:36:48 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: chris@calldei.com Cc: Wilko Bulte , Mark Newton , Peter Jeremy , Donn Miller , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? References: <2177.945155945@zippy.cdrom.com> <3855F364.E66EC87B@cvzoom.net> <99Dec15.073843est.40325@border.alcanet.com.au> <19991215083352.B3500@internode.com.au> <19991215000600.C77327@yedi.iaf.nl> <19991214174432.Y868@holly.calldei.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Costello wrote: > > What do you want in making Unix quick to administer? Seems to > me that's the real goal of those things. Click click click done, > you know. /me clear the throat GUI's are *NEVER* the faster way to administer. They can make faster a very limited set of tasks. When I worked with AIX, even though I was very comfortable with SMIT, at any time when I wanted to do something fast, it was CLI all the way. Perhaps you mean "easy" instead of "quick"? Or maybe "quick" as in "flat learning curve"? -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 10:15:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id F39F0154DE for ; Wed, 15 Dec 1999 10:15:41 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p13-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.142]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id DAA19084; Thu, 16 Dec 1999 03:14:32 +0900 (JST) Message-ID: <3857D64E.ABE978FE@newsguy.com> Date: Thu, 16 Dec 1999 02:56:30 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: "Rodney W. Grimes" Cc: Brian Somers , Andrzej Bialecki , Bill Fumerola , "Louis A. Mamakos" , current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) References: <199912150151.RAA20796@gndrsh.dnsmgr.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rodney W. Grimes" wrote: > > Yea... been hearing that for 4 years... one of it's big short comings is > that it needs a persistent backing store for this. Sounds like this C > program could fullfill one of the missing parts of devfs :-) F persistent backing store. The daemon solution is perfectly fine. -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 10:16: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id BA54515154 for ; Wed, 15 Dec 1999 10:15:55 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p13-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.142]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id DAA19057; Thu, 16 Dec 1999 03:14:19 +0900 (JST) Message-ID: <3857D101.2AF01952@newsguy.com> Date: Thu, 16 Dec 1999 02:33:53 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Wilko Bulte Cc: Mark Newton , Peter Jeremy , Donn Miller , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? References: <2177.945155945@zippy.cdrom.com> <3855F364.E66EC87B@cvzoom.net> <99Dec15.073843est.40325@border.alcanet.com.au> <19991215083352.B3500@internode.com.au> <19991215000600.C77327@yedi.iaf.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote: > > This does, however, have all the risks of building yet another SMIT or > SAM. :-( Neither attempt at making Unix sysadm 'user-friendly' makes > me want to cheer. Actually, I very much like both SMIT (in it's 4.x incarnation) and SAM. Sure, I'll complain loudly if that was the _only_ way of doing it, but neither of these tools precludes you from cli and file-editing, nor would we have to. -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 10:21:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 41A4E1552E for ; Wed, 15 Dec 1999 10:21:08 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id TAA21945 for freebsd-current@FreeBSD.ORG; Wed, 15 Dec 1999 19:21:03 +0100 (CET) (envelope-from olli) Date: Wed, 15 Dec 1999 19:21:03 +0100 (CET) From: Oliver Fromme Message-Id: <199912151821.TAA21945@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" Organization: Administration TU Clausthal Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote in list.freebsd-current: > In message <199912151519.QAA28467@dorifer.heim3.tu-clausthal.de> Oliver Fromme writes: > : That's because X itself contains a very simple "windowmanager" > : functionality, which focuses the window beneath the mouse > : pointer. But when you have to access something which is behind > : another window, you lose. > > That's not entirely true. The X server does not contain a window > manager at all. It doesn't implement any of the ICCCM required for > window managers. Right, that's why I wrote it in "quotes". > There is no placement management, no redirection of windows, no > visibility management or anything of the sort in the X server. It > just has mechanisms which allow one to do these things. "Tools, not > rules," being the motto from long ago... Exactly. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 10:23: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id C49FE15503 for ; Wed, 15 Dec 1999 10:22:59 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id SAA35914 for current@FreeBSD.org; Wed, 15 Dec 1999 18:55:23 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Wed, 15 Dec 1999 18:55:19 +0100 From: Marcel Moolenaar Message-ID: <3857D607.242291F5@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <199912151659.KAA22301@panther.txn.cpqcorp.net> Subject: Re: libcc_drv.a fails to compile on 12/14 sup Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Burden wrote: > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a(choose-temp.o): In function `make_temp_file': > choose-temp.o(.text+0x264): undefined reference to `mkstemps' > *** Error code 1 > Yet I see people are getting their builds to work. Okay, what > did I miss? Your -current must be at least 6 if not 9 months old, right? gcc doesn't have a mkstemps implementation anymore. This means that you must has a -stable or -current that has the function in libc. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 10:23:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id E1C63155C3 for ; Wed, 15 Dec 1999 10:23:21 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id TAA22513 for freebsd-current@FreeBSD.ORG; Wed, 15 Dec 1999 19:23:20 +0100 (CET) (envelope-from olli) Date: Wed, 15 Dec 1999 19:23:20 +0100 (CET) From: Oliver Fromme Message-Id: <199912151823.TAA22513@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: syscons extension: "propellers" Organization: Administration TU Clausthal Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Donn Miller wrote in list.freebsd-current: > On Wed, 15 Dec 1999, Warner Losh wrote: > [...] > > There is no placement management, no redirection of windows, no > > visibility management or anything of the sort in the X server. It > > But, if there's only one app running, then that app gets the focus. Only if that application has only one window (which is not the case for Netscape). The focus is a property that works on windows, not on applications. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 10:26:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 3272A14D51 for ; Wed, 15 Dec 1999 10:26:14 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA11262; Wed, 15 Dec 1999 19:25:26 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Daniel C. Sobral" Cc: "Rodney W. Grimes" , Brian Somers , Andrzej Bialecki , Bill Fumerola , "Louis A. Mamakos" , current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) In-reply-to: Your message of "Thu, 16 Dec 1999 02:56:30 +0900." <3857D64E.ABE978FE@newsguy.com> Date: Wed, 15 Dec 1999 19:25:26 +0100 Message-ID: <11260.945282326@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3857D64E.ABE978FE@newsguy.com>, "Daniel C. Sobral" writes: >"Rodney W. Grimes" wrote: >> >> Yea... been hearing that for 4 years... one of it's big short comings is >> that it needs a persistent backing store for this. Sounds like this C >> program could fullfill one of the missing parts of devfs :-) A "devd" program would solve 98% of what devfs could solve. It cannot solve the homebrew-a-vnode-for-the-root-fs problem. FreeBSD needs a "devd" program *anyway* because what good is dynamic devices if you can't do something intelligent with them when they appear (mount/ifconfig etc etc etc). -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 10:37:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from jasper.heartland.ab.ca (jasper.heartland.ab.ca [207.107.228.1]) by hub.freebsd.org (Postfix) with ESMTP id 0A61A14D85 for ; Wed, 15 Dec 1999 10:37:43 -0800 (PST) (envelope-from dkwiebe@heartland.ab.ca) Received: from heartland.ab.ca (dyn115.heartland.ab.ca [207.107.228.115]) by jasper.heartland.ab.ca (8.9.0/8.9.0) with ESMTP id LAA21079; Wed, 15 Dec 1999 11:24:32 -0700 (MST) Message-ID: <3857D414.AD75A44C@heartland.ab.ca> Date: Wed, 15 Dec 1999 10:47:00 -0700 From: Darren Wiebe Reply-To: dkwiebe@hagenhomes.com Organization: Hagen Homes Ltd. X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Donn Miller Cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: Kernel config utility References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Donn Miller wrote: > > On Wed, 15 Dec 1999, Garrett Wollman wrote: > > > Icons are probably not the right user interface. I'd suggest > > something like Windows's ``hardware manager'' (in the System control > > panel). > > Some people were afraid that it would end up like the Windows > registry. Well, even if it did, I'd argue that it still wouldn't be too > bad. The Windows registry has so many classes and entries, and I think Sorry Ladies & Gentlemen... I was thinking REGISTRY EDITOR not registry, if you get the difference. I know that I did not draw a very fine example. I think that the editor idea is great though.... Darren Wiebe dkwiebe@hagenhomes.com > the kernel config would be smaller with not as many classes. You'd have > the device class, and options class. Then, you'd break devices down into > scsi, ide, etc. Or, we could break them down into network, disk > controllers, sound, that way. > > - Donn > > 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 Dec 15 10:45:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from kiew.egd.igd.fhg.de (kiew.egd.igd.fhg.de [192.102.170.32]) by hub.freebsd.org (Postfix) with ESMTP id E210715521 for ; Wed, 15 Dec 1999 10:45:18 -0800 (PST) (envelope-from runge@rostock.zgdv.de) Received: from rostock.zgdv.de (kingfisher.egd.igd.fhg.de [153.96.43.107]) by kiew.egd.igd.fhg.de (Netscape Messaging Server 3.6) with ESMTP id AAA592B for ; Wed, 15 Dec 1999 19:42:43 +0100 Message-ID: <3857E01E.1937D700@rostock.zgdv.de> Date: Wed, 15 Dec 1999 19:38:22 +0100 From: "Thomas Runge" Organization: http://www.rostock.zgdv.de/ X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 Cc: current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? References: <2177.945155945@zippy.cdrom.com> <3855F364.E66EC87B@cvzoom.net> <99Dec15.073843est.40325@border.alcanet.com.au> <19991215083352.B3500@internode.com.au> <19991215000600.C77327@yedi.iaf.nl> <19991214174432.Y868@holly.calldei.com> <3857D1B0.66C930F9@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > Perhaps you mean "easy" instead of "quick"? Or maybe "quick" as in "flat > learning curve"? Thats it. We have to provide some tools to easily administrate the system for the *avarage* user (but without breaking the "old fashioned way") It would be nice, if we really could become secretary-, boss- or even mom-ready (1) ;-) (1) http://insidedenver.com/seebach/0418seeba.shtml -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 10:49:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 9C5B715521 for ; Wed, 15 Dec 1999 10:49:41 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 34DE7137FBF for ; Wed, 15 Dec 1999 13:49:36 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id NAA69284; Wed, 15 Dec 1999 13:49:34 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14423.58046.169405.384150@trooper.velocet.net> Date: Wed, 15 Dec 1999 13:49:34 -0500 (EST) To: freebsd-current@freebsd.org Subject: AMI MEGARAID problems. X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having trouble convincing -CURRENT to disklabel or newfs an AMI MEGARAID adapter. amr0: irq 10 at device 11.1 on pci0 amr0: firmware GH89 bios 1.41 16MB memory amrd0: on amr0 amrd0: 122647MB (251181056 sectors) RAID 5 (optimal) [1:22:322]root@raid1:~> fdisk amrd0 ******* Working on device /dev/ramrd0 ******* parameters extracted from in-core disklabel are: cylinders=15635 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=15635 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 251176212 (122644 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 274/ sector 63/ head 254 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: [1:29:329]root@raid1:~> disklabel -w -r amrd0s1 auto disklabel: ioctl DIOCGDINFO: Invalid argument disklabel: auto: unknown disk type Dav.e -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 10:56:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B53831553B for ; Wed, 15 Dec 1999 10:56:55 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA21447; Wed, 15 Dec 1999 10:57:59 -0800 Date: Wed, 15 Dec 1999 10:57:59 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: "Daniel C. Sobral" , "Rodney W. Grimes" , Brian Somers , Andrzej Bialecki , Bill Fumerola , "Louis A. Mamakos" , current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) In-Reply-To: <11260.945282326@critter.freebsd.dk> 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, 15 Dec 1999, Poul-Henning Kamp wrote: > In message <3857D64E.ABE978FE@newsguy.com>, "Daniel C. Sobral" writes: > >"Rodney W. Grimes" wrote: > >> > >> Yea... been hearing that for 4 years... one of it's big short comings is > >> that it needs a persistent backing store for this. Sounds like this C > >> program could fullfill one of the missing parts of devfs :-) > > A "devd" program would solve 98% of what devfs could solve. It cannot > solve the homebrew-a-vnode-for-the-root-fs problem. FreeBSD needs a > "devd" program *anyway* because what good is dynamic devices if you > can't do something intelligent with them when they appear (mount/ifconfig > etc etc etc). I mostly agree with you. I tend to also not worry terribly much about root-fs type issues, except that I keep being told by *my* customers that this is what they want, particularly for large SANs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 10:58:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from lodge.guild.ab.ca (lodge.guild.ab.ca [209.91.118.66]) by hub.freebsd.org (Postfix) with ESMTP id B3EBF155B5 for ; Wed, 15 Dec 1999 10:58:29 -0800 (PST) (envelope-from davidc@lodge.guild.ab.ca) Received: from localhost (davidc@localhost) by lodge.guild.ab.ca (8.9.3/8.9.1) with ESMTP id LAA20517 for ; Wed, 15 Dec 1999 11:58:25 -0700 (MST) Date: Wed, 15 Dec 1999 11:58:25 -0700 (MST) From: Chad David To: current@freebsd.org Subject: INET6 userland tools 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 may be missing the obvious, but what is everybody using for userland tools (ping6 etc) on current? I haven't tried, but will the kame-snap tools for 3 work? Thanks Chad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 10:59: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from host.cer.ntnu.edu.tw (cer.ntnu.edu.tw [140.122.119.9]) by hub.freebsd.org (Postfix) with ESMTP id C1B1415033 for ; Wed, 15 Dec 1999 10:58:56 -0800 (PST) (envelope-from clive@host.cer.ntnu.edu.tw) Received: (from clive@localhost) by host.cer.ntnu.edu.tw (8.9.3/8.9.3) id DAA84041; Thu, 16 Dec 1999 03:01:39 +0800 (CST) (envelope-from clive) Date: Thu, 16 Dec 1999 03:01:39 +0800 From: Clive Lin To: Donn Miller Cc: freebsd-current@FreeBSD.ORG Subject: Re: Sound Blaster 128 PCI (ESS1371) support in current? Message-ID: <19991216030139.A83911@host.cer.ntnu.edu.tw> Reply-To: Clive Lin References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 12:37:43PM -0500, Donn Miller wrote: > > I've got the ESS 1868 chipset, and all I get is static. In fact, when I > press the "play" button in RealPlayer, the sound clip never starts but > hangs in the beginning. Then, RealPlayer itself hangs. I end up killing > RealPlayer with killall -15 rvplayer. I too just made world, and remade > my audio devices. Alas. It seems not only ISA SoundBlaster like me got this problem. Well, I believe there must something missed in rescent commits about src/sys/dev/sound. May be in pcm/ or isa/, dunno. At least there's one thing wrong... the ioctl(fdofdevdsp, SNDCTL_DSP_GETFMTS, &test); success before will fail now. Various players may hang when some ioctl like above occured. > Just to be sure, which command is it? Is it both > > ./MAKEDEV pcaudio > ./MAKEDEV snd0 > > or just one of those? may be not all of them ;-) -- CirX Clive Lin FreeBSD - The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 10:59:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 8AD161560C for ; Wed, 15 Dec 1999 10:59:10 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id KAA11182 for freebsd-current@freebsd.org; Wed, 15 Dec 1999 10:58:17 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199912151858.KAA11182@troutmask.apl.washington.edu> Subject: make world breakage To: freebsd-current@freebsd.org (FreeBSD Current) Date: Wed, 15 Dec 1999 10:58:17 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL54 (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 FreeBSD-current source cvsup'd at 1034pst on 991215. -------------------------------------------------------------- >>> Building libraries -------------------------------------------------------------- cd /usr/src; COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.00503 MAKEOBJDIRPREFIX=/usr/obj DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:/root/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/bin:/usr/local/libexec:/root/Office40/bin make -f Makefile.inc1 -DNOINFO -DNOMAN libraries cd /usr/src/lib/csu/i386-elf; make depend; make all; make install rm -f .depend mkdep -f .depend -a -I/usr/obj/usr/src/i386/usr/include /usr/src/lib/csu/i386-elf/crti.S /usr/src/lib/csu/i386-elf/crtn.S cpp: }: No such file or directory cpp: }: No such file or directory mkdep: compile failed *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 11:10:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id 827C3153DD for ; Wed, 15 Dec 1999 11:10:38 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (boomer.navinet.net [216.67.12.90]) by forrie.net (8.9.3/8.9.3) with ESMTP id OAA20051 for ; Wed, 15 Dec 1999 14:10:37 -0500 (EST) Message-Id: <4.2.2.19991215141013.00abed80@216.67.12.69> X-Sender: forrie@216.67.12.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 15 Dec 1999 14:10:43 -0500 To: freebsd-current@freebsd.org From: Forrest Aldrich Subject: Today's make world breakage Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI.... just CVSup'd and got this: X-UIDL: 495287ccf607850cc65e4c59c7b49751 cd /usr/src/lib/librpcsvc; make beforeinstall cd /usr/src/lib/libskey; make beforeinstall sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libskey/skey.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libstand; make beforeinstall sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libstand/stand.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libtacplus; make beforeinstall sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 /usr/src/lib/libtacplus/taclib.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libcom_err; make beforeinstall sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libcom_err/../../contrib/com_err/com_err.h /usr/src/lib/libcom_err/../../contrib/com_err/com_right.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libss; make -B hdrs beforeinstall test -e ss_err.et || ln -s /usr/src/lib/libss/ss_err.et . compile_et ss_err.et test -h ss_err.et && rm -f ss_err.et sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libss/ss.h ss_err.h /usr/obj/usr/src/i386/usr/include/ss sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libss/copyright.h /usr/obj/usr/src/i386/usr/include/ss/mit-sipb-copyright.h cd /usr/src/lib/libutil; make beforeinstall sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libutil/libutil.h /usr/obj/usr/src/i386/usr/include sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libutil/login_cap.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libvgl; make beforeinstall sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libvgl/vgl.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libwrap; make beforeinstall sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libwrap/../../contrib/tcp_wrappers/tcpd.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libz; make beforeinstall sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libz/zconf.h /usr/obj/usr/src/i386/usr/include sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libz/zlib.h /usr/obj/usr/src/i386/usr/include cd /usr/src/usr.bin/lex; make beforeinstall sh /usr/src/tools/install.sh -C -o root -g wheel -m 644 /usr/src/usr.bin/lex/FlexLexer.h /usr/obj/usr/src/i386/usr/include/g++ -------------------------------------------------------------- >>> Building libraries -------------------------------------------------------------- cd /usr/src; COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.00503 MAKEOBJDIRPREFIX=/usr/obj DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/ssl/bin:/usr/X11R6/bin:/usr/local/samba/bin:/usr/local/home/forrie/bin make -f Makefile.inc1 -DNOINFO -DNOMAN libraries cd /usr/src/lib/csu/i386-elf; make depend; make all; make install rm -f .depend mkdep -f .depend -a -I/usr/obj/usr/src/i386/usr/include /usr/src/lib/csu/i386-elf/crti.S /usr/src/lib/csu/i386-elf/crtn.S cpp: }: No such file or directory cpp: }: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/lib/csu/i386-elf. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 11:12:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9796914DEB for ; Wed, 15 Dec 1999 11:12:06 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA40369; Wed, 15 Dec 1999 11:12:00 -0800 (PST) (envelope-from dillon) Date: Wed, 15 Dec 1999 11:12:00 -0800 (PST) From: Matthew Dillon Message-Id: <199912151912.LAA40369@apollo.backplane.com> To: Andrew Gallatin Cc: freebsd-current@freebsd.org Subject: Re: Serious server-side NFS problem References: <14423.46117.353932.473968@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Also, while read performance has improved by 44%, write performance :has degraded by between 50 - 70% (FreeBSD clients)! Here are some :quick benchmarks. Note that the file size of 512MB is larger than :memory on both the server and client. Also note that the disk array :on the server will read at 50MB/sec and write at 40MB/sec, so we are :not disk bound ;-) : :- UDP NFS write performance from a FreeBSD client: : :July's kernel: :% dd if=/dev/zero of=zot bs=1024k count=512 :512+0 records in :512+0 records out :536870912 bytes transferred in 52.780773 secs (10171714 bytes/sec) : :Today's kernel:: :% dd if=/dev/zero of=zot bs=1024k count=512 :512+0 records in :512+0 records out :536870912 bytes transferred in 141.593458 secs (3791636 bytes/sec) Question on these: Is it the client you are running the old and new kernels on or the server? Also, make sure you are running the same number of nfsiod's on each (and also try running a different number of nfsiod's). At the moment I am assuming you ran these tests with the client running the old and new kernel. I have some ideas there in regards to inefficient context switching when the nfsiod's are saturated that I am testing. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 11:20:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 26047153A3 for ; Wed, 15 Dec 1999 11:20:48 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA26092; Wed, 15 Dec 1999 19:20:15 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA01042; Wed, 15 Dec 1999 19:49:22 +0100 (CET) (envelope-from wilko) Date: Wed, 15 Dec 1999 19:49:22 +0100 From: Wilko Bulte To: Mark Newton Cc: Thomas Runge , current@freebsd.org Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991215194922.E447@yedi.iaf.nl> References: <3856BD33.5DE1AB48@newsguy.com> <19991215105736.A467@internode.com.au> <38576264.7D33C327@rostock.zgdv.de> <19991215233319.B1263@internode.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991215233319.B1263@internode.com.au>; from newton@internode.com.au on Wed, Dec 15, 1999 at 11:33:19PM +1030 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 11:33:19PM +1030, Mark Newton wrote: > On Wed, Dec 15, 1999 at 10:41:56AM +0100, Thomas Runge wrote: > > For mainly server-oriented, the "install source to update" or > > console-based setups are quite enough, because the system will > > most probably administraded by people, that know, what they are > > doing. > > But is it reasonable to say, "You can't play at all if you don't > fit that description"? > > (Especially since the NT server camp seems to think you can administer > a system with zero knowledge of anything; The requirement that they > suddenly need to become familiar with how to deal with large archives of > source code isn't going to help us get a foot in those doors). Whatever [CG]UI you throw at the problem at hand: there is *NO* programmer- fixable way out from cluelessnes. What good would be a system that is a snap to install but once it is installed it says # to you? -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 11:21:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id EBE5115585 for ; Wed, 15 Dec 1999 11:21:23 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA26089; Wed, 15 Dec 1999 19:20:12 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA00839; Wed, 15 Dec 1999 19:29:27 +0100 (CET) (envelope-from wilko) Date: Wed, 15 Dec 1999 19:29:27 +0100 From: Wilko Bulte To: Chris Costello Cc: Donn Miller , "Jordan K. Hubbard" , Eric Jones , current@freebsd.org Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991215192927.B447@yedi.iaf.nl> References: <2177.945155945@zippy.cdrom.com> <3855F364.E66EC87B@cvzoom.net> <19991214172832.V868@holly.calldei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991214172832.V868@holly.calldei.com>; from chris@calldei.com on Tue, Dec 14, 1999 at 05:28:32PM -0600 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 14, 1999 at 05:28:32PM -0600, Chris Costello wrote: > On Tue, Dec 14, 1999, Donn Miller wrote: > > Maybe we could call it "sysconfig", in honor of the old > > /etc/sysconfig file that was superceded bt /etc/rc.conf. > > That's not very creative! I had "Trident" in mind. Only > problem is that the name is used by a company that makes video > card chips and another company that makes chewing gum. Call it Inuit. (rationale: Inuit feed on pinguins (right?)) :) Wilko -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 11:21:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 1D8DC1559A for ; Wed, 15 Dec 1999 11:21:39 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA26090; Wed, 15 Dec 1999 19:20:13 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA00890; Wed, 15 Dec 1999 19:34:24 +0100 (CET) (envelope-from wilko) Date: Wed, 15 Dec 1999 19:34:24 +0100 From: Wilko Bulte To: Chris Costello Cc: Mark Newton , Peter Jeremy , Donn Miller , current@freebsd.org Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991215193424.C447@yedi.iaf.nl> References: <2177.945155945@zippy.cdrom.com> <3855F364.E66EC87B@cvzoom.net> <99Dec15.073843est.40325@border.alcanet.com.au> <19991215083352.B3500@internode.com.au> <19991215000600.C77327@yedi.iaf.nl> <19991214174432.Y868@holly.calldei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991214174432.Y868@holly.calldei.com>; from chris@calldei.com on Tue, Dec 14, 1999 at 05:44:32PM -0600 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 14, 1999 at 05:44:32PM -0600, Chris Costello wrote: > On Wed, Dec 15, 1999, Wilko Bulte wrote: > > This does, however, have all the risks of building yet another SMIT or > > SAM. :-( Neither attempt at making Unix sysadm 'user-friendly' makes > > me want to cheer. > > What do you want in making Unix quick to administer? Seems to > me that's the real goal of those things. Click click click done, > you know. Click-click, hosed up beyond repair. What I mean to say is that GUI != easy to administer. M$ has plenty of examples available. The really hard part is to design something that really appeals to the (general) sense of what is a logic. Assuming there is an universal logic to sysadmin-ing. I happen to really like the current installer. OK, it has some rough edges maybe and as I understand the inner workings are labeled 'There be dragons here' but from the outside it is not too bad. What's more, total newbies to FreeBSD can learn to work with it pretty easily. W/ -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 11:22: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 8CFB6153A3 for ; Wed, 15 Dec 1999 11:21:59 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA26091; Wed, 15 Dec 1999 19:20:14 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA00988; Wed, 15 Dec 1999 19:42:44 +0100 (CET) (envelope-from wilko) Date: Wed, 15 Dec 1999 19:42:44 +0100 From: Wilko Bulte To: "Jordan K. Hubbard" Cc: Mark Newton , Peter Jeremy , Donn Miller , current@freebsd.org Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991215194244.D447@yedi.iaf.nl> References: <19991215000600.C77327@yedi.iaf.nl> <49974.945214329@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <49974.945214329@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Tue, Dec 14, 1999 at 03:32:09PM -0800 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 14, 1999 at 03:32:09PM -0800, Jordan K. Hubbard wrote: > > And: how many people would volunteer for such a job? > > Or is it assumed that since this appears suspiciously like Real Work > > it will be a paid-for job? > > It will be a paid-for job, naturally. :) > Something we also have to stay aware of in this discussion is the fact > that even if most hackers could give a fig for graphical installers > and consider them to be an unneeded bit of hand-holding, it would > still be nice to have a framework which stuff could drop into and be > accessed via a command line or turbovision type of interface. We're Fundamental to the discussion is whether there is a desire for a installer+admintool-in-one. Or that these functions are seperated out in different tools. > not talking about writing multiple installers for each type of UI, > after all, since that would be an unreasonable duplication of labor. > We're talking about one installation/configuration code base which can > use either X or text mode interfaces at the user's discretion, so > both "camps" get what they want. Let's please not forget the blind users of FreeBSD.. > It's also a sad fact that journalists tend to rate products based on > different criteria than engineers do, and even where we're getting kudos > in the engineering community, magazines are kicking us in the nuts over > not having something which competes head-to-head with Caldera or Red Hat. > Sad, but true. Very true. I know. Whatever happens, the criterium should not be a 'me too' kind of tool, but rather something better. I happen to dislike tools that ask a bazillion questions. Assuming ease of use is related to a more abstract selection ("What do you want to install? Typical workstation? Web server? Firewall?" along that line) of a installation type. I for example like the Solaris/SPARC installation procedure. At least on a X-display. The character cell variant works, but that is about it. But it works on your 1970s dumb terminal. > - Jordan -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 11:22:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 23275155E1 for ; Wed, 15 Dec 1999 11:22:36 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id OAA02120; Wed, 15 Dec 1999 14:22:34 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA19135; Wed, 15 Dec 1999 14:22:03 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 15 Dec 1999 14:22:03 -0500 (EST) To: Matthew Dillon Cc: freebsd-current@freebsd.org Subject: Re: Serious server-side NFS problem In-Reply-To: <199912151912.LAA40369@apollo.backplane.com> References: <14423.46117.353932.473968@grasshopper.cs.duke.edu> <199912151912.LAA40369@apollo.backplane.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14423.59494.219984.475675@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > > :Also, while read performance has improved by 44%, write performance > :has degraded by between 50 - 70% (FreeBSD clients)! Here are some > :quick benchmarks. Note that the file size of 512MB is larger than > :memory on both the server and client. Also note that the disk array > :on the server will read at 50MB/sec and write at 40MB/sec, so we are > :not disk bound ;-) > : > :- UDP NFS write performance from a FreeBSD client: > : > :July's kernel: > :% dd if=/dev/zero of=zot bs=1024k count=512 > :512+0 records in > :512+0 records out > :536870912 bytes transferred in 52.780773 secs (10171714 bytes/sec) > : > :Today's kernel:: > :% dd if=/dev/zero of=zot bs=1024k count=512 > :512+0 records in > :512+0 records out > :536870912 bytes transferred in 141.593458 secs (3791636 bytes/sec) > > Question on these: Is it the client you are running the old and new > kernels on or the server? Also, make sure you are running the same > number of nfsiod's on each (and also try running a different number > of nfsiod's). > > At the moment I am assuming you ran these tests with the client running > the old and new kernel. I have some ideas there in regards to inefficient > context switching when the nfsiod's are saturated that I am testing. > > -Matt Sorry I wasn't clear. The variable was the server's kernel version. The client's kernel remained constant. It was from sources built late week. When you are measuring server write performance, are you looking at the numbers from the client's perspective, or are you looking at the numbers from the point of view of the server's disks. I ask because if I watch the server via systat, I see a steady 10-11MB/sec hitting the disk. However, if I time the process, or look at the output from dd, I see the poor (< 4MB/sec) numbers I reported. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 11:30:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 91A0915591 for ; Wed, 15 Dec 1999 11:30:17 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (2408 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Wed, 15 Dec 1999 20:30:15 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id B006D38E5; Wed, 15 Dec 1999 20:30:13 +0100 (MET) Subject: tagged openings now 31, 25, 2; ncr0: queue empty. In-Reply-To: <19991215102811.A35D338E6@hcswork.hcs.de> from Hellmuth Michaelis at "Dec 15, 99 11:28:11 am" To: freebsd-current@freebsd.org (FreeBSD Current) Date: Wed, 15 Dec 1999 20:30:13 +0100 (MET) Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1568 Message-Id: <19991215193013.B006D38E5@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From the keyboard of Hellmuth Michaelis: > > from time to time (i have no idea how to reproduce it or what causes it) i get > the following message on the console of one of my current systems: > > (da1:ncr0:0:1:0): tagged openings now 31 > > The drive causing this is a > > da1 at ncr0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: Serial Number DX91RXG > da1: 20.000MB/s transfers (10.000MHz, offset 15, 16bit), Tagged Queueing Enabled > da1: 4096MB (8388608 512 byte sectors: 255H 63S/T 522C) > > on a Tekram: > > ncr0: irq 15 at device 8.0 on pci0 > ncr0: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo > ncr0: single-ended, open drain IRQ driver, using on-chip SRAM > > Should i be concerned about this ? Just to follow up on this, i just saw on that device: (da1:ncr0:0:1:0): tagged openings now 31 (da1:ncr0:0:1:0): tagged openings now 25 (da1:ncr0:0:1:0): tagged openings now 2 and then scrolling: ncr0: queue empty. ncr0: queue empty. ncr0: queue empty. .... over and over the console screen. The only way to get out of this was to reboot. Now i am concerned :-) What is happening there ? Is the drive going bad ? hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 11:37:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (Postfix) with ESMTP id 6CAA2154B2 for ; Wed, 15 Dec 1999 11:37:44 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with ESMTP id LAA17472; Wed, 15 Dec 1999 11:36:48 -0800 (PST) Date: Wed, 15 Dec 1999 11:36:48 -0800 (PST) From: Tom Bartol To: Forrest Aldrich Cc: freebsd-current@FreeBSD.ORG Subject: Re: Today's make world breakage In-Reply-To: <4.2.2.19991215141013.00abed80@216.67.12.69> 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 Ditto here. Tom On Wed, 15 Dec 1999, Forrest Aldrich wrote: > FYI.... just CVSup'd and got this: > > > > X-UIDL: 495287ccf607850cc65e4c59c7b49751 > > cd /usr/src/lib/librpcsvc; make beforeinstall > cd /usr/src/lib/libskey; make beforeinstall > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libskey/skey.h /usr/obj/usr/src/i386/usr/include > cd /usr/src/lib/libstand; make beforeinstall > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libstand/stand.h /usr/obj/usr/src/i386/usr/include > cd /usr/src/lib/libtacplus; make beforeinstall > sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 /usr/src/lib/libtacplus/taclib.h /usr/obj/usr/src/i386/usr/include > cd /usr/src/lib/libcom_err; make beforeinstall > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libcom_err/../../contrib/com_err/com_err.h /usr/src/lib/libcom_err/../../contrib/com_err/com_right.h /usr/obj/usr/src/i386/usr/include > cd /usr/src/lib/libss; make -B hdrs beforeinstall > test -e ss_err.et || ln -s /usr/src/lib/libss/ss_err.et . > compile_et ss_err.et > test -h ss_err.et && rm -f ss_err.et > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libss/ss.h ss_err.h /usr/obj/usr/src/i386/usr/include/ss > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libss/copyright.h /usr/obj/usr/src/i386/usr/include/ss/mit-sipb-copyright.h > cd /usr/src/lib/libutil; make beforeinstall > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libutil/libutil.h /usr/obj/usr/src/i386/usr/include > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libutil/login_cap.h /usr/obj/usr/src/i386/usr/include > cd /usr/src/lib/libvgl; make beforeinstall > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libvgl/vgl.h /usr/obj/usr/src/i386/usr/include > cd /usr/src/lib/libwrap; make beforeinstall > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libwrap/../../contrib/tcp_wrappers/tcpd.h /usr/obj/usr/src/i386/usr/include > cd /usr/src/lib/libz; make beforeinstall > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libz/zconf.h /usr/obj/usr/src/i386/usr/include > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libz/zlib.h /usr/obj/usr/src/i386/usr/include > cd /usr/src/usr.bin/lex; make beforeinstall > sh /usr/src/tools/install.sh -C -o root -g wheel -m 644 /usr/src/usr.bin/lex/FlexLexer.h /usr/obj/usr/src/i386/usr/include/g++ > > -------------------------------------------------------------- > >>> Building libraries > -------------------------------------------------------------- > cd /usr/src; COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.00503 MAKEOBJDIRPREFIX=/usr/obj DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/ssl/bin:/usr/X11R6/bin:/usr/local/samba/bin:/usr/local/home/forrie/bin make -f Makefile.inc1 -DNOINFO -DNOMAN libraries > cd /usr/src/lib/csu/i386-elf; make depend; make all; make install > rm -f .depend > mkdep -f .depend -a -I/usr/obj/usr/src/i386/usr/include /usr/src/lib/csu/i386-elf/crti.S /usr/src/lib/csu/i386-elf/crtn.S > cpp: }: No such file or directory > cpp: }: No such file or directory > mkdep: compile failed > *** Error code 1 > > Stop in /usr/src/lib/csu/i386-elf. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > > > > 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 Dec 15 11:42:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 158B015387 for ; Wed, 15 Dec 1999 11:42:39 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA40673; Wed, 15 Dec 1999 11:42:35 -0800 (PST) (envelope-from dillon) Date: Wed, 15 Dec 1999 11:42:35 -0800 (PST) From: Matthew Dillon Message-Id: <199912151942.LAA40673@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: kernel build breakage if COMPAT_43 not defined Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The compile dies with prototype-missing errors on osig*() routines in kern/kern_sig.c and i386/i386/machdep.c if COMPAT_43 is not defined. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 11:44:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3980A14D32 for ; Wed, 15 Dec 1999 11:44:55 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA56101; Wed, 15 Dec 1999 11:44:17 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Wilko Bulte Cc: Chris Costello , Donn Miller , Eric Jones , current@freebsd.org Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: Your message of "Wed, 15 Dec 1999 19:29:27 +0100." <19991215192927.B447@yedi.iaf.nl> Date: Wed, 15 Dec 1999 11:44:17 -0800 Message-ID: <56097.945287057@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Call it Inuit. (rationale: Inuit feed on pinguins (right?)) How about PolarBear in that case? :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 11:49:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from jasper.heartland.ab.ca (jasper.heartland.ab.ca [207.107.228.1]) by hub.freebsd.org (Postfix) with ESMTP id A1CAA154E5 for ; Wed, 15 Dec 1999 11:49:42 -0800 (PST) (envelope-from dkwiebe@heartland.ab.ca) Received: from heartland.ab.ca (dyn104.heartland.ab.ca [207.107.228.104]) by jasper.heartland.ab.ca (8.9.0/8.9.0) with ESMTP id MAA21795; Wed, 15 Dec 1999 12:36:31 -0700 (MST) Message-ID: <3857E4F6.86B7247C@heartland.ab.ca> Date: Wed, 15 Dec 1999 11:59:02 -0700 From: Darren Wiebe Reply-To: dkwiebe@hagenhomes.com Organization: Hagen Homes Ltd. X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Wilko Bulte Cc: Chris Costello , Donn Miller , "Jordan K. Hubbard" , Eric Jones , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? References: <2177.945155945@zippy.cdrom.com> <3855F364.E66EC87B@cvzoom.net> <19991214172832.V868@holly.calldei.com> <19991215192927.B447@yedi.iaf.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote: > > On Tue, Dec 14, 1999 at 05:28:32PM -0600, Chris Costello wrote: > > On Tue, Dec 14, 1999, Donn Miller wrote: > > > Maybe we could call it "sysconfig", in honor of the old > > > /etc/sysconfig file that was superceded bt /etc/rc.conf. > > > > That's not very creative! I had "Trident" in mind. Only > > problem is that the name is used by a company that makes video > > card chips and another company that makes chewing gum. > > Call it Inuit. (rationale: Inuit feed on pinguins (right?)) The Inuit are my neighbors, just a ways north.. And no, they DON'T have penguins up there. The name would work though.. I will spare the geography, etc. lesson. :-) Darren Wiebe dkwiebe@hagenhomes.com > > :) > > Wilko > -- > Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project > WWW : http://www.tcja.nl http://www.freebsd.org > > 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 Dec 15 11:50:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from timbuk.cray.com (timbuk-fddi.cray.com [128.162.8.102]) by hub.freebsd.org (Postfix) with ESMTP id 400BF1553D for ; Wed, 15 Dec 1999 11:50:32 -0800 (PST) (envelope-from cattelan@thebarn.com) Received: from ledzep.cray.com (mailhost.cray.com [137.38.226.97]) by timbuk.cray.com (8.8.8/CRI-gate-news-1.3) with ESMTP id NAA26758; Wed, 15 Dec 1999 13:50:28 -0600 (CST) Received: from ironwood-e185.americas.sgi.com (ironwood.cray.com [128.162.185.212]) by ledzep.cray.com (8.9.3/craymail-smart-nospam1.0) with ESMTP id NAA2864092; Wed, 15 Dec 1999 13:50:26 -0600 (CST) Received: from nt8.americas.sgi.com (nt8.americas.sgi.com [128.162.195.8]) by ironwood-e185.americas.sgi.com (8.8.4/SGI-ironwood-e1.3a) with ESMTP id NAA21611; Wed, 15 Dec 1999 13:50:25 -0600 (CST) Received: from thebarn.com by nt8.americas.sgi.com (SGI-8.9.3/SGI-client.1.6) via ESMTP id NAA35650; Wed, 15 Dec 1999 13:50:24 -0600 (CST) Message-ID: <3857F0FF.5AC674AE@thebarn.com> Date: Wed, 15 Dec 1999 13:50:23 -0600 From: Russell Cattelan X-Mailer: Mozilla 4.7C-SGI [en] (X11; I; IRIX 6.5-ALPHA-1286074720 IP32) X-Accept-Language: en MIME-Version: 1.0 To: Thomas Veldhouse Cc: freebsd-current@FreeBSD.ORG Subject: Re: Sound Blaster 128 PCI (ESS1371) support in current? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Veldhouse wrote: > Does the newpcm system support the Sound Blaster 128 PCI card (ESS1371 > chipset)? I am aware of a pcm dirver for it in STABLE, but I have not > tried it. The only major problems have been with certain ASUS motherboards and some of the newer PCI128's. (the card freezes) I don't have any specific info at this point. It's been on my list of things to do. The other reports of problems have been with the 1370's and playing short wav clips. I haven't been able to reproduce the problems on the 1371. > > > > Tom Veldhouse > veldy@visi.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 Dec 15 11:53:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id D06C01534E for ; Wed, 15 Dec 1999 11:53:49 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p22-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.151]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id EAA28377; Thu, 16 Dec 1999 04:53:33 +0900 (JST) Message-ID: <3857EE34.5DF0D4C7@newsguy.com> Date: Thu, 16 Dec 1999 04:38:28 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Wilko Bulte Cc: Mark Newton , Thomas Runge , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? References: <3856BD33.5DE1AB48@newsguy.com> <19991215105736.A467@internode.com.au> <38576264.7D33C327@rostock.zgdv.de> <19991215233319.B1263@internode.com.au> <19991215194922.E447@yedi.iaf.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote: > > Whatever [CG]UI you throw at the problem at hand: there is *NO* programmer- > fixable way out from cluelessnes. What good would be a system that is > a snap to install but once it is installed it says # to you? It says /etc/motd to you, actually. :-) -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 11:56:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from filer3.isc.rit.edu (filer3.isc.rit.edu [129.21.3.117]) by hub.freebsd.org (Postfix) with ESMTP id 764D615503 for ; Wed, 15 Dec 1999 11:56:40 -0800 (PST) (envelope-from jcptch@osfmail.isc.rit.edu) Received: from grace.isc.rit.edu ("port 1328"@[129.21.3.102]) by osfmail.isc.rit.edu (PMDF V5.2-32 #21576) with ESMTP id <0FMS00MDVSOUR6@osfmail.isc.rit.edu> for current@freebsd.org; Wed, 15 Dec 1999 14:55:42 -0500 (EST) Received: by grace.isc.rit.edu (8.8.8/1.1.19.2/21Sep98-0910AM) id OAA0000006704; Wed, 15 Dec 1999 14:55:17 -0500 (EST) Date: Wed, 15 Dec 1999 14:55:17 -0500 From: Jon Parise Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: <56097.945287057@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Wed, Dec 15, 1999 at 11:44:17AM -0800 To: current@freebsd.org Mail-followup-to: current@freebsd.org Message-id: <19991215145517.B4788@osfmail.isc.rit.edu> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i X-Operating-System: OSF1 V4.0 (alpha) References: <19991215192927.B447@yedi.iaf.nl> <56097.945287057@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 11:44:17AM -0800, Jordan K. Hubbard wrote: > > Call it Inuit. (rationale: Inuit feed on pinguins (right?)) > > How about PolarBear in that case? :) I was under the impression that Polar Bears are native to the North Pole and penguins are from the South Pole. Promoting a zoologically correct operating system ... -- Jon Parise (parise@pobox.com) . Rochester Inst. of Technology http://www.pobox.com/~parise/ : Computer Science House Member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 11:56:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 16D0615590 for ; Wed, 15 Dec 1999 11:56:45 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id OAA03966; Wed, 15 Dec 1999 14:56:44 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA19203; Wed, 15 Dec 1999 14:56:13 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 15 Dec 1999 14:56:13 -0500 (EST) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-Reply-To: <199912151739.JAA32687@apollo.backplane.com> References: <14423.46117.353932.473968@grasshopper.cs.duke.edu> <199912151711.JAA32205@apollo.backplane.com> <14423.52876.91488.48428@grasshopper.cs.duke.edu> <199912151739.JAA32687@apollo.backplane.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14423.60766.907301.965548@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > > : > : > :Matthew Dillon writes: > : > This is very odd. Does it lockup with UDP or only with TCP? And only > : > with a solaris client? > : > :This appears to be solaris only. I just tried a UDP mount & I see the > :same problem. Is there anything else I can do? > > Yes, see if you can repeat the problem with a shorter dd count -- see > how small a count you can achieve and still produce the problem, then > do a nice long protocol trace. > > -Matt I've tried. I can get the file to take a hell of a long time to close with a count as short as 512 64k chunks. But it eventually completes. Perhaps the large files would eventually complete too, if I were patient enough.. I've left you a full trace on freefall in ~gallatin of a 384MB test (client has 320MB, server has 384MB). large.gz : trace from file creation to server reboot Server is running kernel from today. large_reboot.gz: trace after server is rebooted into ~July kernel and the writes complete. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12: 0:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from patrick.whetstonelogic.com (patrick.whetstonelogic.com [205.252.46.171]) by hub.freebsd.org (Postfix) with ESMTP id A995014A06 for ; Wed, 15 Dec 1999 12:00:24 -0800 (PST) (envelope-from patrick@patrick.whetstonelogic.com) Received: (from patrick@localhost) by patrick.whetstonelogic.com (8.9.3/8.9.3) id OAA62775; Wed, 15 Dec 1999 14:53:52 -0500 (EST) (envelope-from patrick) Message-Id: <199912151953.OAA62775@patrick.whetstonelogic.com> Date: Wed, 15 Dec 1999 14:53:52 -0500 (EST) From: patrick@whetstonelogic.com Subject: Re: sysinstall: is it really at the end of its lifecycle? To: jkh@zippy.cdrom.com Cc: wilko@yedi.iaf.nl, chris@calldei.com, dmmiller@cvzoom.net, ejon@colltech.com, current@FreeBSD.ORG In-Reply-To: <56097.945287057@zippy.cdrom.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15 Dec, Jordan K. Hubbard wrote: >> Call it Inuit. (rationale: Inuit feed on pinguins (right?)) > > How about PolarBear in that case? :) Ok....picky time here. Polar bears and Inuits are found near the North Pole (Alaska, Greenland, etc). Penguins are typically only found in Antarctica. Their only natural enemies are killer whales and leopard seals. Back to lurking... Patrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12: 2:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 6E8DA14CB5 for ; Wed, 15 Dec 1999 12:02:17 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40321>; Thu, 16 Dec 1999 06:53:36 +1100 Content-return: prohibited Date: Thu, 16 Dec 1999 07:01:54 +1100 From: Peter Jeremy Subject: Re: make world broken building fortunes In-reply-to: <7527.945248269@axl.noc.iafrica.com>; from sheldonh@uunet.co.za on Wed, Dec 15, 1999 at 07:57:49PM +1100 To: Sheldon Hearn Cc: freebsd-current@FreeBSD.ORG Message-Id: <99Dec16.065336est.40321@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <99Dec15.061331est.40325@border.alcanet.com.au> <7527.945248269@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Dec-15 19:57:49 +1100, Sheldon Hearn wrote: >> - gnu/usr.bin/bison gnu/usr.bin/cc >> + gnu/usr.bin/bison gnu/usr.bin/cc gnu/usr.bin/texinfo > >Presumably this hunk is a stray fix for something other than the fortune >database? :-) Yes it is. I was having problems with buildworld dying in makeinfo. I've since done some more checking and found a stray (and ancient) makeinfo lying around - it appears to have been installed by an old teTeX port. Ignore that hunk. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12: 2:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from jasper.heartland.ab.ca (jasper.heartland.ab.ca [207.107.228.1]) by hub.freebsd.org (Postfix) with ESMTP id 4598515565 for ; Wed, 15 Dec 1999 12:02:36 -0800 (PST) (envelope-from dkwiebe@heartland.ab.ca) Received: from heartland.ab.ca (dyn107.heartland.ab.ca [207.107.228.107]) by jasper.heartland.ab.ca (8.9.0/8.9.0) with ESMTP id MAA21977; Wed, 15 Dec 1999 12:49:44 -0700 (MST) Message-ID: <3857E80E.5A21040B@heartland.ab.ca> Date: Wed, 15 Dec 1999 12:12:14 -0700 From: Darren Wiebe Reply-To: dkwiebe@hagenhomes.com Organization: Hagen Homes Ltd. X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Jon Parise Cc: current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? References: <19991215192927.B447@yedi.iaf.nl> <56097.945287057@zippy.cdrom.com> <19991215145517.B4788@osfmail.isc.rit.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jon Parise wrote: > > On Wed, Dec 15, 1999 at 11:44:17AM -0800, Jordan K. Hubbard wrote: > > > > Call it Inuit. (rationale: Inuit feed on pinguins (right?)) > > > > How about PolarBear in that case? :) > > I was under the impression that Polar Bears are native to the > North Pole and penguins are from the South Pole. Very GOOD!! I don't know if I can imagin penguins 750 miles north of were I am. :-) Darren Wiebe dkwiebe@hagenhomes.com > > Promoting a zoologically correct operating system ... > > -- > Jon Parise (parise@pobox.com) . Rochester Inst. of Technology > http://www.pobox.com/~parise/ : Computer Science House Member > > 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 Dec 15 12: 3:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3F3CC1526D for ; Wed, 15 Dec 1999 12:03:19 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA56285; Wed, 15 Dec 1999 12:03:01 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Jon Parise Cc: current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: Your message of "Wed, 15 Dec 1999 14:55:17 EST." <19991215145517.B4788@osfmail.isc.rit.edu> Date: Wed, 15 Dec 1999 12:03:01 -0800 Message-ID: <56282.945288181@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was under the impression that Polar Bears are native to the > North Pole and penguins are from the South Pole. Really? What eats penguins then? Maybe walrus? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12: 9:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id A758214A21 for ; Wed, 15 Dec 1999 12:05:33 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA56303; Wed, 15 Dec 1999 12:04:15 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: patrick@whetstonelogic.com Cc: wilko@yedi.iaf.nl, chris@calldei.com, dmmiller@cvzoom.net, ejon@colltech.com, current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: Your message of "Wed, 15 Dec 1999 14:53:52 EST." <199912151953.OAA62775@patrick.whetstonelogic.com> Date: Wed, 15 Dec 1999 12:04:15 -0800 Message-ID: <56300.945288255@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Polar bears and Inuits are found near the North Pole (Alaska, > Greenland, etc). > > Penguins are typically only found in Antarctica. Their only natural > enemies are killer whales and leopard seals. I knew we'd get to the bottom of this eventually. We're hackers, not naturalists! :-) OK, I hereby vote for "orca" as the code name. It's shorter than "leopard seal" :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12: 9:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from pasteur.EECS.Berkeley.EDU (pasteur.EECS.Berkeley.EDU [128.32.138.75]) by hub.freebsd.org (Postfix) with ESMTP id 803B1155F7 for ; Wed, 15 Dec 1999 12:09:30 -0800 (PST) (envelope-from sowings@pasteur.EECS.Berkeley.EDU) Received: from mamba.CS.Berkeley.EDU (mamba.CS.Berkeley.EDU [128.32.43.159]) by pasteur.EECS.Berkeley.EDU (8.9.3+Sun/8.9.1) with ESMTP id MAA09394; Wed, 15 Dec 1999 12:09:29 -0800 (PST) Received: from mamba.CS.Berkeley.EDU (localhost [127.0.0.1]) by mamba.CS.Berkeley.EDU (8.9.3+Sun/8.9.1) with ESMTP id MAA12605; Wed, 15 Dec 1999 12:09:28 -0800 (PST) Message-Id: <199912152009.MAA12605@mamba.CS.Berkeley.EDU> To: patrick@whetstonelogic.com Cc: freebsd-current@freebsd.org Subject: Re: sysinstall: is it really at the end of its lifecycle? In-Reply-To: Your message of "Wed, 15 Dec 1999 14:53:52 EST." <199912151953.OAA62775@patrick.whetstonelogic.com> Date: Wed, 15 Dec 1999 12:09:28 -0800 From: Sanford Owings Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok....picky time here. > > Polar bears and Inuits are found near the North Pole (Alaska, > Greenland, etc). > > Penguins are typically only found in Antarctica. Their only natural > enemies are killer whales and leopard seals. So then ... "Orca"! -- Sanford Owings EECS Instructional Group Staff University of California at Berkeley To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12:12:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from patrick.whetstonelogic.com (patrick.whetstonelogic.com [205.252.46.171]) by hub.freebsd.org (Postfix) with ESMTP id 7098514FE2 for ; Wed, 15 Dec 1999 12:12:21 -0800 (PST) (envelope-from patrick@patrick.whetstonelogic.com) Received: (from patrick@localhost) by patrick.whetstonelogic.com (8.9.3/8.9.3) id PAA62839; Wed, 15 Dec 1999 15:05:57 -0500 (EST) (envelope-from patrick) Message-Id: <199912152005.PAA62839@patrick.whetstonelogic.com> Date: Wed, 15 Dec 1999 15:05:57 -0500 (EST) From: patrick@whetstonelogic.com Subject: Re: sysinstall: is it really at the end of its lifecycle? To: jkh@zippy.cdrom.com Cc: wilko@yedi.iaf.nl, chris@calldei.com, dmmiller@cvzoom.net, ejon@colltech.com, current@FreeBSD.ORG In-Reply-To: <56300.945288255@zippy.cdrom.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15 Dec, Jordan K. Hubbard wrote: >> Polar bears and Inuits are found near the North Pole (Alaska, >> Greenland, etc). >> >> Penguins are typically only found in Antarctica. Their only natural >> enemies are killer whales and leopard seals. > > I knew we'd get to the bottom of this eventually. We're hackers, > not naturalists! :-) > > OK, I hereby vote for "orca" as the code name. It's shorter than > "leopard seal" :) Seconded! Patrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12:21:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id F134115220 for ; Wed, 15 Dec 1999 12:21:29 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40329>; Thu, 16 Dec 1999 07:12:53 +1100 Content-return: prohibited Date: Thu, 16 Dec 1999 07:21:16 +1100 From: Peter Jeremy Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: <199912151953.OAA62775@patrick.whetstonelogic.com>; from patrick@whetstonelogic.com on Thu, Dec 16, 1999 at 06:53:52AM +1100 To: patrick@whetstonelogic.com Cc: current@FreeBSD.ORG Message-Id: <99Dec16.071253est.40329@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <56097.945287057@zippy.cdrom.com> <199912151953.OAA62775@patrick.whetstonelogic.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Dec-16 06:53:52 +1100, patrick@whetstonelogic.com wrote: >Penguins are typically only found in Antarctica. And southern Australia (there are penguin colonies in both Sydney and Melbourne), New Zealand, the southern bits of South America, South Georgia Island, probably South Africa. Hemispherically, I don't believe wild penguins are found north of the equator. > Their only natural enemies are killer whales How about `Orca' as a name then? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12:22:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 0A6E714A01 for ; Wed, 15 Dec 1999 12:22:23 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 8498 invoked from network); 15 Dec 1999 20:22:18 -0000 Received: from lcb13.cvzoom.net (HELO cvzoom.net) (63.65.159.13) by ns.cvzoom.net with SMTP; 15 Dec 1999 20:22:18 -0000 Message-ID: <3857F83C.DC60CC1F@cvzoom.net> Date: Wed, 15 Dec 1999 15:21:16 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: Jon Parise , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? References: <56282.945288181@zippy.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 "Jordan K. Hubbard" wrote: > > > I was under the impression that Polar Bears are native to the > > North Pole and penguins are from the South Pole. > > Really? What eats penguins then? Maybe walrus? Arctic Foxes. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12:23: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id CFA43155A8 for ; Wed, 15 Dec 1999 12:22:56 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id VAA69304 for current@FreeBSD.org; Wed, 15 Dec 1999 21:12:11 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Wed, 15 Dec 1999 21:12:06 +0100 From: Marcel Moolenaar Message-ID: <3857F616.6D818906@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <199912151942.LAA40673@apollo.backplane.com> Subject: Re: kernel build breakage if COMPAT_43 not defined Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > The compile dies with prototype-missing errors on osig*() routines > in kern/kern_sig.c and i386/i386/machdep.c if COMPAT_43 is not defined. This is a known problem. We need to introduce something like COMPAT_FBSD3 and make the code conditional on that. It's now conditional on COMPAT_43 which is wrong, because the osig* code is not 4.3BSD specific. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12:23:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id DAEE014FE2 for ; Wed, 15 Dec 1999 12:23:33 -0800 (PST) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.9.3/8.9.3) with ESMTP id VAA81018; Wed, 15 Dec 1999 21:23:32 +0100 (CET) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.9.3/8.9.3) with UUCP id VAA27478; Wed, 15 Dec 1999 21:23:32 +0100 (MET) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id VAA12897; Wed, 15 Dec 1999 21:22:46 +0100 (CET) (envelope-from root@nihil.plaut.de) Date: Wed, 15 Dec 1999 21:22:44 +0100 (CET) From: Michael Reifenberger To: Hellmuth Michaelis Cc: FreeBSD Current Subject: Re: tagged openings now 31, 25, 2; ncr0: queue empty. In-Reply-To: <19991215193013.B006D38E5@hcswork.hcs.de> 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, 15 Dec 1999, Hellmuth Michaelis wrote: ... > (da1:ncr0:0:1:0): tagged openings now 31 > (da1:ncr0:0:1:0): tagged openings now 25 > (da1:ncr0:0:1:0): tagged openings now 2 > > and then scrolling: > > ncr0: queue empty. ... > What is happening there ? Is the drive going bad ? Probably if you see this for the first time. Ususlly you see some degration from 64 to 32 for not optimal designed Drives (Which propagate to operate with more tagged commands than they actually can) see /sys/cam/cam_xpt.c for such drives. If it's a new drive maybe it can't hande tagged commands at all. This could be solved by adding an entry in cam_xpt.c Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12:24: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext02.compaq.com (mailext02.compaq.com [207.18.199.33]) by hub.freebsd.org (Postfix) with ESMTP id 2E9DF15271 for ; Wed, 15 Dec 1999 12:24:02 -0800 (PST) (envelope-from bruceb@txn.cpqcorp.net) Received: by mailext02.compaq.com (Postfix, from userid 12345) id ED75A9A8B7; Wed, 15 Dec 1999 14:24:00 -0600 (CST) Received: from mailint02.im.hou.compaq.com (mailint02.compaq.com [207.18.199.35]) by mailext02.compaq.com (Postfix) with ESMTP id E683190D87 for ; Wed, 15 Dec 1999 14:24:00 -0600 (CST) Received: by mailint02.im.hou.compaq.com (Postfix, from userid 12345) id BB46ABC4C8; Wed, 15 Dec 1999 14:23:53 -0600 (CST) Received: from fedex-s1.txn.cpqcorp.net (fedex-s1.txn.cpqcorp.net [16.74.4.108]) by mailint02.im.hou.compaq.com (Postfix) with ESMTP id 48761B2A43 for ; Wed, 15 Dec 1999 14:23:53 -0600 (CST) From: Bruce Burden Posted-Date: Wed, 15 Dec 1999 14:24:04 -0600 (CST) Received: (from bruceb@localhost) by panther.txn.cpqcorp.net (8.9.3/8.9.3) id OAA22569 for freebsd-current@freebsd.org; Wed, 15 Dec 1999 14:20:19 -0600 (CST) Message-Id: <199912152020.OAA22569@panther.txn.cpqcorp.net> Subject: Re: sysinstall: is it really at the end of its lifecycle? To: freebsd-current@freebsd.org Date: Wed, 15 Dec 1999 14:20:18 -0600 (CST) Reply-To: bruceb@devnull.mpd.tandem.com In-Reply-To: <19991215192927.B447@yedi.iaf.nl> from "Wilko Bulte" at Dec 15, 99 07:29:27 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 > > Call it Inuit. (rationale: Inuit feed on pinguins (right?)) > The northern hemisphere penguin type birds are called Auks. Close cousin to penguins. I don't know whether the Inuit hunt them or not. Bruce -- ------------------------------------------------------------------------------- Bruce Burden bruceb@isd.tandem.com Tandem Computers Inc. 512-432-8944 Network Verification 14231 Tandem Blvd. Auto answer(4 rings) Austin, TX 78726 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12:26: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (Postfix) with ESMTP id A8F6B14FE2 for ; Wed, 15 Dec 1999 12:26:02 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with ESMTP id MAA18372; Wed, 15 Dec 1999 12:25:43 -0800 (PST) Date: Wed, 15 Dec 1999 12:25:44 -0800 (PST) From: Tom Bartol To: Donn Miller Cc: "Jordan K. Hubbard" , Jon Parise , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-Reply-To: <3857F83C.DC60CC1F@cvzoom.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 Wed, 15 Dec 1999, Donn Miller wrote: > "Jordan K. Hubbard" wrote: > > > > > I was under the impression that Polar Bears are native to the > > > North Pole and penguins are from the South Pole. > > > > Really? What eats penguins then? Maybe walrus? > > Arctic Foxes. > > > - Donn I doubt it. No peguins in the arctic. But Sea Lions definitely do. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12:33:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 6104915503 for ; Wed, 15 Dec 1999 12:33:03 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id VAA05973; Wed, 15 Dec 1999 21:31:21 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <56300.945288255@zippy.cdrom.com> References: <56300.945288255@zippy.cdrom.com> Date: Wed, 15 Dec 1999 21:23:40 +0100 To: "Jordan K. Hubbard" , patrick@whetstonelogic.com From: Brad Knowles Subject: Re: sysinstall: is it really at the end of its lifecycle? Cc: wilko@yedi.iaf.nl, chris@calldei.com, dmmiller@cvzoom.net, ejon@colltech.com, current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:04 PM -0800 1999/12/15, Jordan K. Hubbard wrote: > OK, I hereby vote for "orca" as the code name. It's shorter than > "leopard seal" :) Except that there is already a well-known tool by that name. See . -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12:36: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 0EF1E1553B for ; Wed, 15 Dec 1999 12:36:03 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id OAA17052; Wed, 15 Dec 1999 14:35:15 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Wed, 15 Dec 1999 14:35:15 -0600 (CST) From: David Scheidt To: Brad Knowles Cc: "Jordan K. Hubbard" , patrick@whetstonelogic.com, wilko@yedi.iaf.nl, chris@calldei.com, dmmiller@cvzoom.net, ejon@colltech.com, current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? 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, 15 Dec 1999, Brad Knowles wrote: > At 12:04 PM -0800 1999/12/15, Jordan K. Hubbard wrote: > > > OK, I hereby vote for "orca" as the code name. It's shorter than > > "leopard seal" :) > > Except that there is already a well-known tool by that name. See > . > > -- Stoat then? http://home.capu.net/~kwelch/pp/predators/mammals.html David scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12:40: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 7094015516 for ; Wed, 15 Dec 1999 12:40:01 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA11993; Wed, 15 Dec 1999 21:24:05 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Jordan K. Hubbard" Cc: patrick@whetstonelogic.com, wilko@yedi.iaf.nl, chris@calldei.com, dmmiller@cvzoom.net, ejon@colltech.com, current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: Your message of "Wed, 15 Dec 1999 12:04:15 PST." <56300.945288255@zippy.cdrom.com> Date: Wed, 15 Dec 1999 21:24:04 +0100 Message-ID: <11991.945289444@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <56300.945288255@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >> Polar bears and Inuits are found near the North Pole (Alaska, >> Greenland, etc). >> >> Penguins are typically only found in Antarctica. Their only natural >> enemies are killer whales and leopard seals. > >I knew we'd get to the bottom of this eventually. We're hackers, >not naturalists! :-) > >OK, I hereby vote for "orca" as the code name. It's shorter than >"leopard seal" :) With due attention paid to realities I offer the following two code names for your consideration: "freon" and/or: "flourocarbons" -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12:43:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from megadodo.segNET.COM (megadodo.segNET.COM [206.34.181.3]) by hub.freebsd.org (Postfix) with ESMTP id 1613D15363 for ; Wed, 15 Dec 1999 12:43:49 -0800 (PST) (envelope-from adams@digitalspark.net) Received: from nightfall.digitalspark.net (arc6a203.bf.sover.net [209.198.85.204]) by megadodo.segNET.COM (8.9.1a/8.8.5) with ESMTP id PAA09413; Wed, 15 Dec 1999 15:43:10 -0500 (EST) Date: Wed, 15 Dec 1999 15:43:54 -0500 (EST) From: Adam Strohl To: Poul-Henning Kamp Cc: "Jordan K. Hubbard" , patrick@whetstonelogic.com, wilko@yedi.iaf.nl, chris@calldei.com, dmmiller@cvzoom.net, ejon@colltech.com, current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-Reply-To: <11991.945289444@critter.freebsd.dk> 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, 15 Dec 1999, Poul-Henning Kamp wrote: > With due attention paid to realities I offer the following two code > names for your consideration: > > "freon" YES! This has my vote - ----( Adam Strohl )------------------------------------------------ - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - - ----------------------------------------( DigitalSpark.NET )------- - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12:44:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 946CE15573 for ; Wed, 15 Dec 1999 12:44:51 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA77822; Wed, 15 Dec 1999 13:44:44 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA63531; Wed, 15 Dec 1999 13:44:44 -0700 (MST) Message-Id: <199912152044.NAA63531@harmony.village.org> To: Poul-Henning Kamp Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 15 Dec 1999 19:25:26 +0100." <11260.945282326@critter.freebsd.dk> References: <11260.945282326@critter.freebsd.dk> Date: Wed, 15 Dec 1999 13:44:44 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <11260.945282326@critter.freebsd.dk> Poul-Henning Kamp writes: : A "devd" program would solve 98% of what devfs could solve. It cannot : solve the homebrew-a-vnode-for-the-root-fs problem. FreeBSD needs a : "devd" program *anyway* because what good is dynamic devices if you : can't do something intelligent with them when they appear (mount/ifconfig : etc etc etc). Yes. I'd like to see this in the future. There is no reason to have pccardd after the cut over to the new code. I don't think there is a reason to have both devd and usbd. They all just do things when devices come and go. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12:48:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E661F155C6 for ; Wed, 15 Dec 1999 12:48:22 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA77834; Wed, 15 Dec 1999 13:47:59 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA63557; Wed, 15 Dec 1999 13:47:59 -0700 (MST) Message-Id: <199912152047.NAA63557@harmony.village.org> To: Donn Miller Subject: Re: sysinstall: is it really at the end of its lifecycle? Cc: "Jordan K. Hubbard" , Jon Parise , current@FreeBSD.ORG In-reply-to: Your message of "Wed, 15 Dec 1999 15:21:16 EST." <3857F83C.DC60CC1F@cvzoom.net> References: <3857F83C.DC60CC1F@cvzoom.net> <56282.945288181@zippy.cdrom.com> Date: Wed, 15 Dec 1999 13:47:59 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : > Really? What eats penguins then? Maybe walrus? The penguin's natural preditors include the "killer whale", man and a few other preditors in the southern hemisphere. orca? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12:49: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 480D9155B0 for ; Wed, 15 Dec 1999 12:48:55 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA12190; Wed, 15 Dec 1999 21:48:48 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) In-reply-to: Your message of "Wed, 15 Dec 1999 13:44:44 MST." <199912152044.NAA63531@harmony.village.org> Date: Wed, 15 Dec 1999 21:48:48 +0100 Message-ID: <12188.945290928@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912152044.NAA63531@harmony.village.org>, Warner Losh writes: >In message <11260.945282326@critter.freebsd.dk> Poul-Henning Kamp writes: >: A "devd" program would solve 98% of what devfs could solve. It cannot >: solve the homebrew-a-vnode-for-the-root-fs problem. FreeBSD needs a >: "devd" program *anyway* because what good is dynamic devices if you >: can't do something intelligent with them when they appear (mount/ifconfig >: etc etc etc). > >Yes. I'd like to see this in the future. There is no reason to have >pccardd after the cut over to the new code. I don't think there is a >reason to have both devd and usbd. They all just do things when >devices come and go. And we don't really need YAD when we have init hanging around doing nothing for its keep anyway... I would really like to see the devd functionality to live in init and at the same time I wouldn't mind if init were taught to keep important programs running, things like sshd, inetd, syslogd and similar should be restarted if they die. No, I don't want sysV runlevels or the weird shit AIX has. I'm sure a clean and sensible way can be found, if some mental energies are poured into the problem. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12:52:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 51A801523D for ; Wed, 15 Dec 1999 12:52:08 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id MAA22092; Wed, 15 Dec 1999 12:53:42 -0800 Date: Wed, 15 Dec 1999 12:53:42 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) In-Reply-To: <12188.945290928@critter.freebsd.dk> 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 would really like to see the devd functionality to live in init > and at the same time I wouldn't mind if init were taught to keep > important programs running, things like sshd, inetd, syslogd and > similar should be restarted if they die. > > No, I don't want sysV runlevels or the weird shit AIX has. I'm sure > a clean and sensible way can be found, if some mental energies are > poured into the problem. > Isn't this throwing an awful lot onto init? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12:53:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 3C69F155AF for ; Wed, 15 Dec 1999 12:53:16 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA06595; Wed, 15 Dec 1999 13:53:05 -0700 (MST) (envelope-from ken) Date: Wed, 15 Dec 1999 13:53:05 -0700 From: "Kenneth D. Merry" To: Hellmuth Michaelis Cc: FreeBSD Current Subject: Re: tagged openings now 31, 25, 2; ncr0: queue empty. Message-ID: <19991215135305.A6498@panzer.kdm.org> References: <19991215102811.A35D338E6@hcswork.hcs.de> <19991215193013.B006D38E5@hcswork.hcs.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991215193013.B006D38E5@hcswork.hcs.de>; from hm@hcs.de on Wed, Dec 15, 1999 at 08:30:13PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 20:30:13 +0100, Hellmuth Michaelis wrote: > >From the keyboard of Hellmuth Michaelis: > > > > from time to time (i have no idea how to reproduce it or what causes it) i get > > the following message on the console of one of my current systems: > > > > (da1:ncr0:0:1:0): tagged openings now 31 The reason you're getting these messages is because you're either using a pre-3.2 version of FreeBSD, or you're booting with -v. From the dmesg output below, it appears you're booting with -v. It is nothing to worry about for the most part, just an indication that your drive has returned queue full and CAM has reduced the number of outstanding transactions for that drive. > > The drive causing this is a > > > > da1 at ncr0 bus 0 target 1 lun 0 > > da1: Fixed Direct Access SCSI-2 device > > da1: Serial Number DX91RXG > > da1: 20.000MB/s transfers (10.000MHz, offset 15, 16bit), Tagged Queueing Enabled > > da1: 4096MB (8388608 512 byte sectors: 255H 63S/T 522C) > > > > on a Tekram: > > > > ncr0: irq 15 at device 8.0 on pci0 > > ncr0: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo > > ncr0: single-ended, open drain IRQ driver, using on-chip SRAM > > > > Should i be concerned about this ? > > Just to follow up on this, i just saw on that device: > > (da1:ncr0:0:1:0): tagged openings now 31 > (da1:ncr0:0:1:0): tagged openings now 25 > (da1:ncr0:0:1:0): tagged openings now 2 That's not a good sign. This means that the drive kept returning queue full, until we reduced the number of transactions to the minimum. > and then scrolling: > > ncr0: queue empty. > ncr0: queue empty. > ncr0: queue empty. > .... And neither is that. You may want to try Gerard Roudier's sym driver instead of the stock ncr driver. At least if you have problems with the sym driver, Gerard will fix them. > over and over the console screen. The only way to get out of this was to > reboot. > > Now i am concerned :-) > > What is happening there ? Is the drive going bad ? My guess is that your drive is broken for tagged queueing. The Conner CFP2107 is quirked in the transport layer to disable tagged queueing, and my guess is that your drive may also have the same sort of problem. Since we've already established that your drive will return queue full indefinitely, there are several things for you to try: - use 'camcontrol negotiate' to disable tagged queueing temporarily on the drive. See if that helps any. - Put a quirk entry in the transport layer (sys/cam/cam_xpt.c) and try putting in lower limit of say 8 tags for your drive. If that doesn't work, and disabling tags in camcontrol did, just quirk it to disable tagged queueing. Anyway, let me know what happens. My guess is that the 4207 is just the 4G version of the 2107, so they probably have the same sorts of problems. I would like to see what happens if you use Gerard's sym driver (with tagged queueing enabled for the drive) as well. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 12:55: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 2201B14C24 for ; Wed, 15 Dec 1999 12:55:00 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA12237; Wed, 15 Dec 1999 21:54:49 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) In-reply-to: Your message of "Wed, 15 Dec 1999 12:53:42 PST." Date: Wed, 15 Dec 1999 21:54:49 +0100 Message-ID: <12235.945291289@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: >> > >> I would really like to see the devd functionality to live in init >> and at the same time I wouldn't mind if init were taught to keep >> important programs running, things like sshd, inetd, syslogd and >> similar should be restarted if they die. >> >> No, I don't want sysV runlevels or the weird shit AIX has. I'm sure >> a clean and sensible way can be found, if some mental energies are >> poured into the problem. >> > >Isn't this throwing an awful lot onto init? Not really... The meta-daemon part is no different from keeping gettys in the air... The devd thing consists of selecting on some magic fd and running a program when something happens. This could be done with a getty like daemon too of course. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 13: 1:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1222B155B3 for ; Wed, 15 Dec 1999 13:01:11 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id NAA22145; Wed, 15 Dec 1999 13:02:32 -0800 Date: Wed, 15 Dec 1999 13:02:32 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) In-Reply-To: <12235.945291289@critter.freebsd.dk> 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 > >Isn't this throwing an awful lot onto init? > > Not really... > > The meta-daemon part is no different from keeping gettys in the air... > > The devd thing consists of selecting on some magic fd and running a > program when something happens. This could be done with a getty > like daemon too of course. I was just thinking it could get tricky and have subtle ordering bugs of new tty devices, changes to ttys and signals all about the same time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 13: 4:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 533701553D for ; Wed, 15 Dec 1999 13:04:00 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA12293; Wed, 15 Dec 1999 22:03:48 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) In-reply-to: Your message of "Wed, 15 Dec 1999 13:02:32 PST." Date: Wed, 15 Dec 1999 22:03:48 +0100 Message-ID: <12291.945291828@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: >> >Isn't this throwing an awful lot onto init? >> >> Not really... >> >> The meta-daemon part is no different from keeping gettys in the air... >> >> The devd thing consists of selecting on some magic fd and running a >> program when something happens. This could be done with a getty >> like daemon too of course. > >I was just thinking it could get tricky and have subtle ordering bugs of >new tty devices, changes to ttys and signals all about the same time. Well, they are no less subtle by having them in different processes... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 13: 4:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 3A1EA1553B for ; Wed, 15 Dec 1999 13:04:40 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id PAA22713; Wed, 15 Dec 1999 15:04:26 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Wed, 15 Dec 1999 15:04:25 -0600 (CST) From: David Scheidt To: Poul-Henning Kamp Cc: Warner Losh , current@FreeBSD.ORG Subject: Init Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) ) In-Reply-To: <12188.945290928@critter.freebsd.dk> 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, 15 Dec 1999, Poul-Henning Kamp wrote: > In message <199912152044.NAA63531@harmony.village.org>, Warner Losh writes: > > I would really like to see the devd functionality to live in init > and at the same time I wouldn't mind if init were taught to keep > important programs running, things like sshd, inetd, syslogd and > similar should be restarted if they die. > > No, I don't want sysV runlevels or the weird shit AIX has. I'm sure > a clean and sensible way can be found, if some mental energies are > poured into the problem. What's wrong with run with system V runlevels? Other than it's system V and everything AT^HUSL did is evil, of course. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 13: 6: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4B3A514D0B for ; Wed, 15 Dec 1999 13:05:57 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id NAA22171; Wed, 15 Dec 1999 13:07:30 -0800 Date: Wed, 15 Dec 1999 13:07:30 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) In-Reply-To: <12291.945291828@critter.freebsd.dk> 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 was just thinking it could get tricky and have subtle ordering bugs of > >new tty devices, changes to ttys and signals all about the same time. > > Well, they are no less subtle by having them in different processes... No, but possibly easier to track and debug. Just a minor nit. N'mind... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 13:13:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 86FE414DD6 for ; Wed, 15 Dec 1999 13:13:27 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA12346; Wed, 15 Dec 1999 22:13:09 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: David Scheidt Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: Init Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) ) In-reply-to: Your message of "Wed, 15 Dec 1999 15:04:25 CST." Date: Wed, 15 Dec 1999 22:13:09 +0100 Message-ID: <12344.945292389@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Dav id Scheidt writes: >On Wed, 15 Dec 1999, Poul-Henning Kamp wrote: > >> In message <199912152044.NAA63531@harmony.village.org>, Warner Losh writes: >> >> I would really like to see the devd functionality to live in init >> and at the same time I wouldn't mind if init were taught to keep >> important programs running, things like sshd, inetd, syslogd and >> similar should be restarted if they die. >> >> No, I don't want sysV runlevels or the weird shit AIX has. I'm sure >> a clean and sensible way can be found, if some mental energies are >> poured into the problem. > >What's wrong with run with system V runlevels? Other than it's system V and >everything AT^HUSL did is evil, of course. runlevels are a very oldfashioned way to think about things, I don't want to have one big button which is called "NETWORKING ON/OFF". We need to be able to dynamically say "keep this puppy alive" and later "ok, forget about that one from now on". -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 13:14:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 600D714DB0 for ; Wed, 15 Dec 1999 13:14:46 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA12361; Wed, 15 Dec 1999 22:13:49 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) In-reply-to: Your message of "Wed, 15 Dec 1999 13:07:30 PST." Date: Wed, 15 Dec 1999 22:13:49 +0100 Message-ID: <12359.945292429@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: >> > >> >I was just thinking it could get tricky and have subtle ordering bugs of >> >new tty devices, changes to ttys and signals all about the same time. >> >> Well, they are no less subtle by having them in different processes... > >No, but possibly easier to track and debug. Just a minor nit. N'mind... But lets say you add a pccard on which you want a getty, so devd will have to tell init to run a getty on that port wouldn't it ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 13:26:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from lorien.odc.net (lorien.odc.net [207.137.42.14]) by hub.freebsd.org (Postfix) with ESMTP id B95FB14E66 for ; Wed, 15 Dec 1999 13:26:31 -0800 (PST) (envelope-from nwestfal@lorien.odc.net) Received: from localhost (nwestfal@localhost) by lorien.odc.net (8.9.3/8.9.3) with ESMTP id NAA20410; Wed, 15 Dec 1999 13:26:03 -0800 Date: Wed, 15 Dec 1999 13:26:03 -0800 (PST) From: Neal Westfall To: Russell Cattelan Cc: Thomas Veldhouse , freebsd-current@FreeBSD.ORG Subject: Re: Sound Blaster 128 PCI (ESS1371) support in current? In-Reply-To: <3857F0FF.5AC674AE@thebarn.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, 15 Dec 1999, Russell Cattelan wrote: > Thomas Veldhouse wrote: > > > Does the newpcm system support the Sound Blaster 128 PCI card (ESS1371 > > chipset)? I am aware of a pcm dirver for it in STABLE, but I have not > > tried it. > > The only major problems have been with certain ASUS motherboards and > some of the newer PCI128's. (the card freezes) > I don't have any specific info at this point. > It's been on my list of things to do. > > The other reports of problems have been with the 1370's and playing > short wav clips. I haven't been able to reproduce the problems on the > 1371. I've been having problems with a Creative/Ensoniq AudioPCI which is also 1371. It probes fine, and the fist sound clip you play sounds fine, but after that any sounds you try to play you only get fragmented pieces of it or no sound at all. I am using an Asus P6NP5 motherboard on this machine (Pentium Pro 200). -- Neal Westfall | mailto:nwestfal@odc.net | http://www.odc.net/~nwestfal "What is today a matter of academic speculation begins tomorrow to move armies and pull down empires. In that second stage, it has gone too far to be combatted; the time to stop it was when it was still a matter of impassionate debate." -- J. Gresham Machen, "Christianity and Culture" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 13:35:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CA44B155BD for ; Wed, 15 Dec 1999 13:35:45 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id NAA22275; Wed, 15 Dec 1999 13:37:20 -0800 Date: Wed, 15 Dec 1999 13:37:20 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) In-Reply-To: <12359.945292429@critter.freebsd.dk> 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 > But lets say you add a pccard on which you want a getty, so devd will > have to tell init to run a getty on that port wouldn't it ? Of course- but this lays out very clearly where breakage could occur and leads to be better flexibility. Let's assume this is devd and leave to the side whether devfs would or would not be better. a. insert card b. card recognized (8 new tty ports) c. devd awakened d. (re)makes /dev nodes e. updates /etc/ttys [ this is a debatable step ] f. notifies init (kill(1,1)) g. init awakens h. rescans /etc/ttys i. spawns new gettys, kills dead ones (the old rmut hat dance) Groups a-b, c-f, g-i, are separable steps with pretty clear audit trail stops as to how things could go. Let's take another more complicated example: a. SAN Fabric SCN (change notify) is received by Qlogic FC-AL driver. b. Fabric Nameserver rescanned- 32 new disks arrived, 8 disks left. c. ASYNC notification upcall to CAM is made [ this is as yet an undesigned area, but assume that does like what a camcontrol rescan now does (or is supposed to)- new disks get assigned new instance numbers, dead disks are either safely removed of pack invalidation occurs if they were still open ] d. devd awakened e. (re)makes /dev nodes f. [ VARIABLE HOOK HERE- POLICY LEFT OPEN ] g1. vinum awakened, yatta yatta yatta g2. VxVM (Veritas Volume Manager) awakened, yatta yatta yatta g3. Specified perl script activated, (auto disklabel, newfs, mount) ... Again, Groups a-b and d-f are separable steps with pretty clear audit trail stops. It's not quite clear what step G should be, or whether it should be left to 3rd party hooks, but it's pretty clear to me that putting volume management in init makes no sense whatsoever. For things like what init itself manages (tty lines), sure it does. Otherwise, no. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 13:36:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 5E3FB14DD6 for ; Wed, 15 Dec 1999 13:36:46 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA00946; Wed, 15 Dec 1999 21:37:54 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA03591; Wed, 15 Dec 1999 22:25:42 +0100 (CET) (envelope-from wilko) Date: Wed, 15 Dec 1999 22:25:42 +0100 From: Wilko Bulte To: "Jordan K. Hubbard" Cc: Jon Parise , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991215222542.D3264@yedi.iaf.nl> References: <19991215145517.B4788@osfmail.isc.rit.edu> <56282.945288181@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <56282.945288181@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Wed, Dec 15, 1999 at 12:03:01PM -0800 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 12:03:01PM -0800, Jordan K. Hubbard wrote: > > I was under the impression that Polar Bears are native to the > > North Pole and penguins are from the South Pole. > > Really? What eats penguins then? Maybe walrus? > > - Jordan Which leads us to the inevitable conclusion: with jkh and your's truly as guides you cannot get *more* lost. In order to break the record just set mankind will need to leave this blueish planet to explore the final frontier. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 13:37: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 8B5F215608 for ; Wed, 15 Dec 1999 13:37:02 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA00943; Wed, 15 Dec 1999 21:37:51 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA03462; Wed, 15 Dec 1999 22:18:24 +0100 (CET) (envelope-from wilko) Date: Wed, 15 Dec 1999 22:18:24 +0100 From: Wilko Bulte To: Warner Losh Cc: Donn Miller , "Jordan K. Hubbard" , Jon Parise , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991215221824.B3264@yedi.iaf.nl> References: <3857F83C.DC60CC1F@cvzoom.net> <56282.945288181@zippy.cdrom.com> <3857F83C.DC60CC1F@cvzoom.net> <199912152047.NAA63557@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912152047.NAA63557@harmony.village.org>; from imp@village.org on Wed, Dec 15, 1999 at 01:47:59PM -0700 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 01:47:59PM -0700, Warner Losh wrote: > : > Really? What eats penguins then? Maybe walrus? > > The penguin's natural preditors include the "killer whale", man and a > few other preditors in the southern hemisphere. orca? Hm, if correct, Orca would make a good codename for a sysadm tool: Ordinary Ramblers Can [now] Admin [FreeBSD] Wilko [shuts up and heads back to the Bokbier :] -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 13:37:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 14FFD1553B for ; Wed, 15 Dec 1999 13:37:20 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA00942; Wed, 15 Dec 1999 21:37:50 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA03404; Wed, 15 Dec 1999 22:12:12 +0100 (CET) (envelope-from wilko) Date: Wed, 15 Dec 1999 22:12:12 +0100 From: Wilko Bulte To: patrick@whetstonelogic.com Cc: jkh@zippy.cdrom.com, chris@calldei.com, dmmiller@cvzoom.net, ejon@colltech.com, current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991215221212.A3264@yedi.iaf.nl> Reply-To: freebsd-chat@FreeBSD.ORG References: <56097.945287057@zippy.cdrom.com> <199912151953.OAA62775@patrick.whetstonelogic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912151953.OAA62775@patrick.whetstonelogic.com>; from patrick@whetstonelogic.com on Wed, Dec 15, 1999 at 02:53:52PM -0500 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 02:53:52PM -0500, patrick@whetstonelogic.com wrote: > On 15 Dec, Jordan K. Hubbard wrote: > >> Call it Inuit. (rationale: Inuit feed on pinguins (right?)) > > > > How about PolarBear in that case? :) > > Ok....picky time here. > > Polar bears and Inuits are found near the North Pole (Alaska, > Greenland, etc). OK, minor detail. Only half a planet wrong :-) > Penguins are typically only found in Antarctica. Their only natural But they are making their ways into the warmer parts of the Earth ;) > enemies are killer whales and leopard seals. Hm. Neither of which makes a good name for a sysadm tool unfortunately Follow-ups to -chat. Wilko -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 13:37:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 89CD714A13 for ; Wed, 15 Dec 1999 13:37:46 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA00945; Wed, 15 Dec 1999 21:37:54 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA03537; Wed, 15 Dec 1999 22:21:40 +0100 (CET) (envelope-from wilko) Date: Wed, 15 Dec 1999 22:21:40 +0100 From: Wilko Bulte To: Poul-Henning Kamp Cc: "Jordan K. Hubbard" , patrick@whetstonelogic.com, chris@calldei.com, dmmiller@cvzoom.net, ejon@colltech.com, current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991215222140.C3264@yedi.iaf.nl> References: <56300.945288255@zippy.cdrom.com> <11991.945289444@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <11991.945289444@critter.freebsd.dk>; from phk@critter.freebsd.dk on Wed, Dec 15, 1999 at 09:24:04PM +0100 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 09:24:04PM +0100, Poul-Henning Kamp wrote: > In message <56300.945288255@zippy.cdrom.com>, "Jordan K. Hubbard" writes: > >> Polar bears and Inuits are found near the North Pole (Alaska, > >> Greenland, etc). > >> > >> Penguins are typically only found in Antarctica. Their only natural > >> enemies are killer whales and leopard seals. > > > >I knew we'd get to the bottom of this eventually. We're hackers, > >not naturalists! :-) > > > >OK, I hereby vote for "orca" as the code name. It's shorter than > >"leopard seal" :) > > With due attention paid to realities I offer the following two code > names for your consideration: > > "freon" Is a TM of Dupont (although I doubt they will be proud enough of it to sue ;-) > and/or: > "flourocarbons" fluorocarbons aka CFK. There is a relation with computing: Seymour used them to keep his machines thermally sound. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 13:57:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 34FA2152EE for ; Wed, 15 Dec 1999 13:57:19 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id PAA32818; Wed, 15 Dec 1999 15:57:05 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Wed, 15 Dec 1999 15:57:05 -0600 (CST) From: David Scheidt To: Poul-Henning Kamp Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: Init Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) ) In-Reply-To: <12344.945292389@critter.freebsd.dk> 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, 15 Dec 1999, Poul-Henning Kamp wrote: > In message , Dav > id Scheidt writes: > >What's wrong with run with system V runlevels? Other than it's system V and > >everything AT^HUSL did is evil, of course. > > runlevels are a very oldfashioned way to think about things, I don't > want to have one big button which is called "NETWORKING ON/OFF". runlevels let you do more than just run gettys, control networking, and run /sbin/rc?.d scripts. We do. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 13:59:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id C3450152A7; Wed, 15 Dec 1999 13:59:15 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id NAA92202; Wed, 15 Dec 1999 13:59:14 -0800 (PST) Date: Wed, 15 Dec 1999 13:59:12 -0800 (PST) From: Julian Elischer To: current@freebsd.org Cc: sef@freebsd.org Subject: linux /proc and vmware. 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 for various reasons it looks more an dmore like we will need to do this simply for practical reasons. In particular for vmware, but also for other packages. the hack at http://www.enst.fr/~beyssac/freebsd/ seems a good one to me. (as a starting point. might I suggest that we make a decision to allow procfs to be mounted with a -linux flag and act more like the linux programs expect.? (particularly we could mount it at /compat/linux/proc with the -linux flag). julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 14: 8:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 3A78B1529A for ; Wed, 15 Dec 1999 14:08:25 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA01251; Wed, 15 Dec 1999 14:09:44 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912152209.OAA01251@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Martin Cracauer Cc: Marcel Moolenaar , Sheldon Hearn , current@FreeBSD.ORG Subject: Re: sh(1) broken caching [was: Re: Broken sh(1)?] In-reply-to: Your message of "Wed, 15 Dec 1999 10:34:44 +0100." <19991215103444.B60044@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Dec 1999 14:09:44 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In <38565DEA.4487DF53@scc.nl>, Marcel Moolenaar wrote: > > Sheldon Hearn wrote: > > > > > > On Tue, 14 Dec 1999 15:42:11 +0100, Marcel Moolenaar wrote: > > > > > > > > You set all those variables for the first make command, but not for the > > > > > second. What did you expect to happen? > > > > > > > > That make(1) would execute. > > > > > > But what was the PATH set to _before_ you set it for the first execution > > > of make? That's what's important, surely? > > > > It is. Try this: > > > > scones% sh > > % echo $PATH > > /sbin:/bin:/usr/sbin:/usr/bin:.... > > % hash -v > > builtin hash > > builtin echo > > % which ls > > /bin/ls > > % hash -v > > builtin hash > > builtin echo > > /usr/bin/which > > % PATH=/foo:/bar:/bin ls > > This line does *not* change $PATH for the next lines. > > > > > % hash -v > > builtin hash > > builtin echo > > /usr/bin/which > > /usr/sbin/ls > > ^^^^^^^^^^^^ Caching index based on temp. path!!!! > > % ls > > ls: not found > > $PATH is still /sbin:/bin:/usr/sbin:/usr/bin:.... You don't get it, do you? So the path is /sbin:/bin:... ... where is ls, again? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Dec 15 14: 9:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from pasteur.EECS.Berkeley.EDU (pasteur.EECS.Berkeley.EDU [128.32.138.75]) by hub.freebsd.org (Postfix) with ESMTP id 35E911529A for ; Wed, 15 Dec 1999 14:09:33 -0800 (PST) (envelope-from sowings@pasteur.EECS.Berkeley.EDU) Received: from mamba.CS.Berkeley.EDU (mamba.CS.Berkeley.EDU [128.32.43.159]) by pasteur.EECS.Berkeley.EDU (8.9.3+Sun/8.9.1) with ESMTP id OAA18353; Wed, 15 Dec 1999 14:09:32 -0800 (PST) Received: from mamba.CS.Berkeley.EDU (localhost [127.0.0.1]) by mamba.CS.Berkeley.EDU (8.9.3+Sun/8.9.1) with ESMTP id OAA13108; Wed, 15 Dec 1999 14:09:32 -0800 (PST) Message-Id: <199912152209.OAA13108@mamba.CS.Berkeley.EDU> To: Wilko Bulte Cc: freebsd-current@freebsd.org Subject: Re: sysinstall: is it really at the end of its lifecycle? In-Reply-To: Your message of "Wed, 15 Dec 1999 22:18:24 +0100." <19991215221824.B3264@yedi.iaf.nl> Date: Wed, 15 Dec 1999 14:09:32 -0800 From: Sanford Owings Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hm, if correct, Orca would make a good codename for a sysadm tool: > > Ordinary Ramblers Can [now] Admin [FreeBSD] Someone pointed out that Orca was already taken.... The question NOW is: Can you come up with a good acronym for "SHAMU"? -- Sanford Owings EECS Instructional Group Staff University of California at Berkeley To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 14:12:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id 7167E155D8 for ; Wed, 15 Dec 1999 14:12:20 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FMS006OXYZSEM@mta4.rcsntx.swbell.net> for freebsd-current@FreeBSD.ORG; Wed, 15 Dec 1999 16:11:53 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id QAA16145; Wed, 15 Dec 1999 16:14:13 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Wed, 15 Dec 1999 16:14:08 -0600 From: Chris Costello Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: <199912152209.OAA13108@mamba.CS.Berkeley.EDU> To: Sanford Owings Cc: Wilko Bulte , freebsd-current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991215161408.J868@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <19991215221824.B3264@yedi.iaf.nl> <199912152209.OAA13108@mamba.CS.Berkeley.EDU> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999, Sanford Owings wrote: > Someone pointed out that Orca was already taken.... The question NOW > is: Can you come up with a good acronym for "SHAMU"? Systems Have an Administration Monstrosity Underfoot. Sounds a bit derogatory if I want people to _use_ the thing. -- |Chris Costello |It's 10 o'clock. Do you know where your child processes are? `------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 14:16:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from dead-end.net (dead-end.net [216.15.131.2]) by hub.freebsd.org (Postfix) with ESMTP id 4DF4E155DE for ; Wed, 15 Dec 1999 14:16:15 -0800 (PST) (envelope-from rock@dead-end.net) Received: from dead-end.net (p3E9C3609.dip.t-dialin.net [62.156.54.9]) by dead-end.net (8.9.3/DEAD-END/1999102300-Deliver) with ESMTP id XAA18533 for ; Wed, 15 Dec 1999 23:16:13 +0100 (CET) (envelope-from rock@dead-end.net) Message-ID: <3858051B.4A21331E@dead-end.net> Date: Wed, 15 Dec 1999 22:16:11 +0100 From: "D. Rock" X-Mailer: Mozilla 4.7 [de] (Win98; U) X-Accept-Language: de MIME-Version: 1.0 To: current@freebsd.org Subject: problems with new pnp code 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 noticed a bug in the new pnp code. The resource allocator seems to ignore the align flag for port addresses. dmesg output: [...] AZT5001: start dependant AZT5001: adding io range 0x100-0x3ff, size=0x1, align=0x1 AZT5001: end dependant [...] SAG0001: start dependant SAG0001: adding io range 0x100-0x3f7, size=0x8, align=0x8 SAG0001: adding irq mask 0xbcb8 SAG0001: start dependant SAG0001: adding io range 0x100-0x3f7, size=0x8, align=0x8 SAG0001: adding irq mask 0x20 SAG0001: start dependant SAG0001: adding io range 0x100-0x3f7, size=0x8, align=0x8 SAG0001: adding irq mask 0x80 SAG0001: end dependant [...] unknown11: at port 0x100 on isa0 isic0: at port 0x101-0x108 irq 10 on isa0 isic0: HSCX VSTR test failed for SWS PnP isic0: HSC0: VSTR: 0xee isic0: HSC1: VSTR: 0xee device_probe_and_attach: isic0 attach returned 6 [...] Shouldn't the port for isic0 be chosen as 0x108-10f? This used to be the assignment by the BIOS with the old code. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 14:16:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from dead-end.net (dead-end.net [216.15.131.2]) by hub.freebsd.org (Postfix) with ESMTP id 2FD5715063 for ; Wed, 15 Dec 1999 14:16:32 -0800 (PST) (envelope-from rock@dead-end.net) Received: from dead-end.net (p3E9C3609.dip.t-dialin.net [62.156.54.9]) by dead-end.net (8.9.3/DEAD-END/1999102300-Deliver) with ESMTP id XAA18544 for ; Wed, 15 Dec 1999 23:16:30 +0100 (CET) (envelope-from rock@dead-end.net) Message-ID: <3858052D.A1298D60@dead-end.net> Date: Wed, 15 Dec 1999 22:16:29 +0100 From: "D. Rock" X-Mailer: Mozilla 4.7 [de] (Win98; U) X-Accept-Language: de MIME-Version: 1.0 To: current@freebsd.org Subject: ATA problem 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 ata driver tries to enable UDMA for my controller, but fails (this is no disk problem. The disks can do UDMA, as tested in another machine). Perhaps UDMA should be disabled for all VIA 82C586 chips: dmesg output: [...] found-> vendor=0x1106, dev=0x0571, revid=0x02 class=01-01-8a, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 00006000, size 4 map[24]: type 1, range 32, base e1100000, size 13 [...] ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=50 status1=50 ata0: mask=03 status0=50 status1=50 ata0: devices = 0x3 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 ata1: mask=03 status0=50 status1=00 ata1: mask=03 status0=50 status1=00 ata1: devices = 0x1 ata1 at 0x0170 irq 15 on ata-pci0 [...] ata0: master: success setting up WDMA2 mode on VIA chip ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 ad0: ATA-4 disk at ata0 as master ad0: 4103MB (8404830 sectors), 8894 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, DMA Creating DISK ad0 Creating DISK wd0 ata0: slave: success setting up WDMA2 mode on VIA chip ad1: piomode=4 dmamode=2 udmamode=-1 cblid=0 ad1: ATA-2 disk at ata0 as slave ad1: 1221MB (2501856 sectors), 2482 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, DMA Creating DISK ad1 Creating DISK wd1 ata1: master: success setting up WDMA2 mode on VIA chip ad2: piomode=4 dmamode=2 udmamode=2 cblid=0 ad2: ATA-4 disk at ata1 as master ad2: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 32 depth queue, DMA This already with a small patch with only uses WDMA modes, otherwise I will get "lost disk contact" messages. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 14:22:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id D8E61155D4 for ; Wed, 15 Dec 1999 14:22:39 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA01511; Wed, 15 Dec 1999 14:25:47 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912152225.OAA01511@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: David Gilbert Cc: freebsd-current@freebsd.org Subject: Re: AMI MEGARAID problems. In-reply-to: Your message of "Wed, 15 Dec 1999 13:49:34 EST." <14423.58046.169405.384150@trooper.velocet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Dec 1999 14:25:47 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dd if=/dev/zero of=/dev/amrd0 count=16 disklabel -rw amrd0 auto newfs amrd0c Don't bother slicing the array in this case; it's not worth the effort. (The probable cause of your trouble is garbage at the beginning of the slice you've created). > I'm having trouble convincing -CURRENT to disklabel or newfs an AMI > MEGARAID adapter. > > amr0: irq 10 at device 11.1 on pci0 > amr0: firmware GH89 bios 1.41 16MB memory > amrd0: on amr0 > amrd0: 122647MB (251181056 sectors) RAID 5 (optimal) > > [1:22:322]root@raid1:~> fdisk amrd0 > ******* Working on device /dev/ramrd0 ******* > parameters extracted from in-core disklabel are: > cylinders=15635 heads=255 sectors/track=63 (16065 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=15635 heads=255 sectors/track=63 (16065 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > start 63, size 251176212 (122644 Meg), flag 80 (active) > beg: cyl 0/ sector 1/ head 1; > end: cyl 274/ sector 63/ head 254 > The data for partition 2 is: > > The data for partition 3 is: > > The data for partition 4 is: > > > [1:29:329]root@raid1:~> disklabel -w -r amrd0s1 auto > disklabel: ioctl DIOCGDINFO: Invalid argument > disklabel: auto: unknown disk type > > Dav.e > > -- > ============================================================================ > |David Gilbert, Velocet Communications. | Two things can only be | > |Mail: dgilbert@velocet.net | equal if and only if they | > |http://www.velocet.net/~dgilbert | are precisely opposite. | > =========================================================GLO================ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Dec 15 14:33:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id AD14F14BE3 for ; Wed, 15 Dec 1999 14:33:12 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA01651; Wed, 15 Dec 1999 14:34:08 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912152234.OAA01651@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: patrick@whetstonelogic.com Cc: jkh@zippy.cdrom.com, wilko@yedi.iaf.nl, chris@calldei.com, dmmiller@cvzoom.net, ejon@colltech.com, current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: Your message of "Wed, 15 Dec 1999 14:53:52 EST." <199912151953.OAA62775@patrick.whetstonelogic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Dec 1999 14:34:08 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok....picky time here. > > Polar bears and Inuits are found near the North Pole (Alaska, > Greenland, etc). > > Penguins are typically only found in Antarctica. Their only natural > enemies are killer whales and leopard seals. > > Back to lurking... Actually, Penguins are found all the way into the tropics, and their list of incidental predators include sharks and feral cats. However, I think "orca" has a lot of promise as a name to be held in reserve for when we finally have a decent installer to threaten people with. Let's not take the Apple route (announce, tshirts, then code). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Dec 15 14:33:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 8BB2614DFF for ; Wed, 15 Dec 1999 14:33:44 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA01700; Wed, 15 Dec 1999 14:36:54 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912152236.OAA01700@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: Your message of "Wed, 15 Dec 1999 21:24:04 +0100." <11991.945289444@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Dec 1999 14:36:54 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <56300.945288255@zippy.cdrom.com>, "Jordan K. Hubbard" writes: > >> Polar bears and Inuits are found near the North Pole (Alaska, > >> Greenland, etc). > >> > >> Penguins are typically only found in Antarctica. Their only natural > >> enemies are killer whales and leopard seals. > > > >I knew we'd get to the bottom of this eventually. We're hackers, > >not naturalists! :-) > > > >OK, I hereby vote for "orca" as the code name. It's shorter than > >"leopard seal" :) > > With due attention paid to realities I offer the following two code > names for your consideration: > > "freon" > and/or: > "flourocarbons" "Plastic Bag" "Driftnet" "TWA800" (Ok, it was a bit far north), "EXXON Valdez" (ditto)... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Dec 15 14:43:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id A47FE15280 for ; Wed, 15 Dec 1999 14:43:29 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id OAA24578; Wed, 15 Dec 1999 14:43:17 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912152243.OAA24578@gndrsh.dnsmgr.net> Subject: Re: sysinstall: is it really at the end of its lifecycle? In-Reply-To: <199912152209.OAA13108@mamba.CS.Berkeley.EDU> from Sanford Owings at "Dec 15, 1999 02:09:32 pm" To: sowings@pasteur.EECS.Berkeley.EDU (Sanford Owings) Date: Wed, 15 Dec 1999 14:43:16 -0800 (PST) Cc: wilko@yedi.iaf.nl (Wilko Bulte), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 > > > Hm, if correct, Orca would make a good codename for a sysadm tool: > > > > Ordinary Ramblers Can [now] Admin [FreeBSD] > > Someone pointed out that Orca was already taken.... The question NOW > is: Can you come up with a good acronym for "SHAMU"? Easy... Some Help for Another Misguided User -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 14:50:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from lorien.odc.net (lorien.odc.net [207.137.42.14]) by hub.freebsd.org (Postfix) with ESMTP id ADD05155F5 for ; Wed, 15 Dec 1999 14:50:09 -0800 (PST) (envelope-from nwestfal@lorien.odc.net) Received: from localhost (nwestfal@localhost) by lorien.odc.net (8.9.3/8.9.3) with ESMTP id OAA22553; Wed, 15 Dec 1999 14:49:45 -0800 Date: Wed, 15 Dec 1999 14:49:45 -0800 (PST) From: Neal Westfall To: "Rodney W. Grimes" Cc: Sanford Owings , Wilko Bulte , freebsd-current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-Reply-To: <199912152243.OAA24578@gndrsh.dnsmgr.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 Wed, 15 Dec 1999, Rodney W. Grimes wrote: > > > > > Hm, if correct, Orca would make a good codename for a sysadm tool: > > > > > > Ordinary Ramblers Can [now] Admin [FreeBSD] > > > > Someone pointed out that Orca was already taken.... The question NOW > > is: Can you come up with a good acronym for "SHAMU"? > > Easy... > > Some Help for Another Misguided User > "System Hoser and Mangling Utility" (ducking) -- Neal Westfall | mailto:nwestfal@odc.net | http://www.odc.net/~nwestfal "What is today a matter of academic speculation begins tomorrow to move armies and pull down empires. In that second stage, it has gone too far to be combatted; the time to stop it was when it was still a matter of impassionate debate." -- J. Gresham Machen, "Christianity and Culture" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 14:53:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B396715446 for ; Wed, 15 Dec 1999 14:53:26 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA78392; Wed, 15 Dec 1999 15:53:23 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA64569; Wed, 15 Dec 1999 15:53:23 -0700 (MST) Message-Id: <199912152253.PAA64569@harmony.village.org> To: Neal Westfall Subject: Re: sysinstall: is it really at the end of its lifecycle? Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 15 Dec 1999 14:49:45 PST." References: Date: Wed, 15 Dec 1999 15:53:23 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Neal Westfall writes: : "System Hoser and Mangling Utility" Shamu Helps Any Moronic User Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 14:55:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 3DF48153F3 for ; Wed, 15 Dec 1999 14:55:25 -0800 (PST) (envelope-from jedgar@fxp.org) Received: from earth.fxp (oca-c1s2-19.mfi.net [209.26.94.66]) by pawn.primelocation.net (Postfix) with ESMTP id D9C059B4A for ; Wed, 15 Dec 1999 17:55:21 -0500 (EST) Date: Wed, 15 Dec 1999 17:55:21 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.fxp To: current@freebsd.org Subject: Re: sysinstall: is it really at the end of its lifecycle? In-Reply-To: <19991215192927.B447@yedi.iaf.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 Wed, 15 Dec 1999, Wilko Bulte wrote: > On Tue, Dec 14, 1999 at 05:28:32PM -0600, Chris Costello wrote: > > On Tue, Dec 14, 1999, Donn Miller wrote: > > > Maybe we could call it "sysconfig", in honor of the old > > > /etc/sysconfig file that was superceded bt /etc/rc.conf. > > > > That's not very creative! I had "Trident" in mind. Only > > problem is that the name is used by a company that makes video > > card chips and another company that makes chewing gum. > > Call it Inuit. (rationale: Inuit feed on pinguins (right?)) > When I first saw 'Inuit', I thought it was 'Tuit'...therefore we, when distributing on CD's, can claim that we are providing a 'round-tuit'. /me ducks ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@freebsd.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 15: 0:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id B1CF01541C for ; Wed, 15 Dec 1999 15:00:36 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id PAA94844 for ; Wed, 15 Dec 1999 15:00:35 -0800 (PST) Date: Wed, 15 Dec 1999 15:00:34 -0800 (PST) From: Julian Elischer To: current@freebsd.org Subject: pnp, sound and LINT in -current 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 Somethifn I have not bee tracking has happened with config, and "controller pnp" as it no longer likes it. however LINT doesn't help because it still has comments refering to 'enable pnp'. Are these old? and if not, how do I now do this? Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 15: 3:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id BE55E15602 for ; Wed, 15 Dec 1999 15:02:57 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40348>; Thu, 16 Dec 1999 09:54:20 +1100 Content-return: prohibited Date: Thu, 16 Dec 1999 10:02:38 +1100 From: Peter Jeremy Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) In-reply-to: <12188.945290928@critter.freebsd.dk>; from phk@critter.freebsd.dk on Thu, Dec 16, 1999 at 07:48:48AM +1100 To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Message-Id: <99Dec16.095420est.40348@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <199912152044.NAA63531@harmony.village.org> <12188.945290928@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Dec-16 07:48:48 +1100, Poul-Henning Kamp wrote: >And we don't really need YAD when we have init hanging around doing >nothing for its keep anyway... I beg to differ. To quote init(8): The role of init is so critical that if it dies, the system will reboot itself automatically. If, at bootstrap time, the init process cannot be located, the system will panic with the message ``panic: init died (signal %d, exit %d)''. This suggests that init needs to be very robust - which generally translates to `small and well audited'. Non-core functionality (which IMHO includes devd) really belongs in another process. Looking at the development side, it's also painful to debug init - another reason for leaving it alone. >and at the same time I wouldn't mind if init were taught to keep >important programs running, things like sshd, inetd, syslogd and >similar should be restarted if they die. It can do that now. Add the following lines to /etc/ttys: sshd "/usr/local/sbin/sshd" none on inetd "/usr/sbin/inetd -Ww" none on syslogd "/usr/sbin/syslogd" none on (This ability has always been present, but is now documented). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 15: 4: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 81AE714A13 for ; Wed, 15 Dec 1999 15:03:58 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 2F5051C59; Wed, 15 Dec 1999 18:03:39 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 2BDFD3836; Wed, 15 Dec 1999 18:03:39 -0500 (EST) Date: Wed, 15 Dec 1999 18:03:39 -0500 (EST) From: Bill Fumerola To: Julian Elischer Cc: current@freebsd.org Subject: Re: pnp, sound and LINT in -current 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, 15 Dec 1999, Julian Elischer wrote: > Somethifn I have not bee tracking has happened with config, and > "controller pnp" as it no longer likes it. > however LINT doesn't help because it still has comments refering > to 'enable pnp'. Are these old? and if not, how do I now do this? [hawk-billf] /home/billf > grep pnp.c /sys/conf/files isa/pnp.c optional isa if you have isa, you now have pnp, as I understand it. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 15: 9: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 2A65114CED for ; Wed, 15 Dec 1999 15:09:03 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id AAA12875; Thu, 16 Dec 1999 00:07:49 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) In-reply-to: Your message of "Thu, 16 Dec 1999 10:02:38 +1100." <99Dec16.095420est.40348@border.alcanet.com.au> Date: Thu, 16 Dec 1999 00:07:49 +0100 Message-ID: <12873.945299269@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <99Dec16.095420est.40348@border.alcanet.com.au>, Peter Jeremy writes : >On 1999-Dec-16 07:48:48 +1100, Poul-Henning Kamp wrote: >>And we don't really need YAD when we have init hanging around doing >>nothing for its keep anyway... > >I beg to differ. To quote init(8): > The role of init is so critical that if it dies, the system will reboot > itself automatically. If, at bootstrap time, the init process cannot be > located, the system will panic with the message ``panic: init died > (signal %d, exit %d)''. > >This suggests that init needs to be very robust - which generally >translates to `small and well audited'. Non-core functionality >(which IMHO includes devd) really belongs in another process. Well, there are a lot of chicken & eggs issues with devd, which may skew that a bit, but lets examine that when we get there. >>and at the same time I wouldn't mind if init were taught to keep >>important programs running, things like sshd, inetd, syslogd and >>similar should be restarted if they die. > >It can do that now. Add the following lines to /etc/ttys: > >sshd "/usr/local/sbin/sshd" none on >inetd "/usr/sbin/inetd -Ww" none on >syslogd "/usr/sbin/syslogd" none on > >(This ability has always been present, but is now documented). Yes, but apart from the highly unintuitive name "/etc/ttys" any process which involves edititing a file and signalling a process has a big potential for races. I would prefer if the lines could be added to /etc/ttys somewhat like: sshd "/usr/local/sbin/sshd" none ondemand And then we could telinit -on sshd telinit -off sshd or similar. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 15:16:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 8946814CB5 for ; Wed, 15 Dec 1999 15:16:20 -0800 (PST) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id AAA78014; Thu, 16 Dec 1999 00:15:49 +0100 (CET) (envelope-from leifn@neland.dk) Message-ID: <01b201bf4752$8bd2c680$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: , "FreeBSD Current" References: <19991215193013.B006D38E5@hcswork.hcs.de> Subject: Sv: tagged openings now 31, 25, 2; ncr0: queue empty. Date: Thu, 16 Dec 1999 00:11:10 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message -----=20 From: Hellmuth Michaelis To: FreeBSD Current Sent: Wednesday, December 15, 1999 8:30 PM Subject: tagged openings now 31, 25, 2; ncr0: queue empty. > and then scrolling: >=20 > ncr0: queue empty. > ncr0: queue empty. > ncr0: queue empty. > .... >=20 > over and over the console screen. The only way to get out of this was = to=20 > reboot. >=20 > Now i am concerned :-) >=20 > What is happening there ? Is the drive going bad ? I've had the same thing happening here. I've since that removed (well, = just not mounting) a drive, which gave some reading errors, and have = installed a newer current, and I haven't seen it happening since. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 15:20:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id A95BD15616 for ; Wed, 15 Dec 1999 15:20:26 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA06699; Wed, 15 Dec 1999 23:27:39 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA31489; Thu, 16 Dec 1999 00:06:35 +0100 (CET) (envelope-from wilko) Date: Thu, 16 Dec 1999 00:06:34 +0100 From: Wilko Bulte To: Sanford Owings Cc: freebsd-current@freebsd.org Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991216000632.A8960@yedi.iaf.nl> References: <19991215221824.B3264@yedi.iaf.nl> <199912152209.OAA13108@mamba.CS.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912152209.OAA13108@mamba.CS.Berkeley.EDU>; from sowings@pasteur.EECS.Berkeley.EDU on Wed, Dec 15, 1999 at 02:09:32PM -0800 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 02:09:32PM -0800, Sanford Owings wrote: > > > Hm, if correct, Orca would make a good codename for a sysadm tool: > > > > Ordinary Ramblers Can [now] Admin [FreeBSD] > > Someone pointed out that Orca was already taken.... The question NOW > is: Can you come up with a good acronym for "SHAMU"? System Hackers Administration Mindnumbing Utility nah.. System Housekeeping Advanced Management Utility ? [ can we loose the H please? Sounds like a broom to me ] -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 15:20:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id EB6B1155EF for ; Wed, 15 Dec 1999 15:20:35 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA06700; Wed, 15 Dec 1999 23:27:40 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA45451; Thu, 16 Dec 1999 00:10:33 +0100 (CET) (envelope-from wilko) Date: Thu, 16 Dec 1999 00:10:33 +0100 From: Wilko Bulte To: Sanford Owings Cc: freebsd-current@freebsd.org Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991216001033.A37061@yedi.iaf.nl> Reply-To: freebsd-chat@freebsd.org References: <19991215221824.B3264@yedi.iaf.nl> <199912152209.OAA13108@mamba.CS.Berkeley.EDU> <19991216000632.A8960@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991216000632.A8960@yedi.iaf.nl>; from wilko@yedi.iaf.nl on Thu, Dec 16, 1999 at 12:06:33AM +0100 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 12:06:33AM +0100, Wilko Bulte wrote: > On Wed, Dec 15, 1999 at 02:09:32PM -0800, Sanford Owings wrote: > > > > > Hm, if correct, Orca would make a good codename for a sysadm tool: > > > > > > Ordinary Ramblers Can [now] Admin [FreeBSD] > > > > Someone pointed out that Orca was already taken.... The question NOW > > is: Can you come up with a good acronym for "SHAMU"? MeMEmHoRoS [Mere Mortals Emergency Holographic Root Substitute] -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 15:29:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta1.rcsntx.swbell.net (mta1.rcsntx.swbell.net [151.164.30.25]) by hub.freebsd.org (Postfix) with ESMTP id 2C5BD15257 for ; Wed, 15 Dec 1999 15:29:23 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta1.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FMT0059E2K56S@mta1.rcsntx.swbell.net> for current@FreeBSD.ORG; Wed, 15 Dec 1999 17:28:54 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id RAA16612; Wed, 15 Dec 1999 17:31:14 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Wed, 15 Dec 1999 17:31:13 -0600 From: Chris Costello Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: <19991215193424.C447@yedi.iaf.nl> To: Wilko Bulte Cc: Mark Newton , Peter Jeremy , Donn Miller , current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991215173113.M868@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <2177.945155945@zippy.cdrom.com> <3855F364.E66EC87B@cvzoom.net> <99Dec15.073843est.40325@border.alcanet.com.au> <19991215083352.B3500@internode.com.au> <19991215000600.C77327@yedi.iaf.nl> <19991214174432.Y868@holly.calldei.com> <19991215193424.C447@yedi.iaf.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999, Wilko Bulte wrote: > Click-click, hosed up beyond repair. What I mean to say is that > GUI != easy to administer. M$ has plenty of examples available. There's a difference between useful GUI design and backwards braindead inconsistant GUI design. Guess which Microsoft is using. -- |Chris Costello |A journey of a thousand miles begins with a cash advance. `--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 15:30:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta1.rcsntx.swbell.net (mta1.rcsntx.swbell.net [151.164.30.25]) by hub.freebsd.org (Postfix) with ESMTP id BD101155EF for ; Wed, 15 Dec 1999 15:30:15 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta1.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FMT006VQ2LYWY@mta1.rcsntx.swbell.net> for current@FreeBSD.ORG; Wed, 15 Dec 1999 17:29:59 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id RAA16629; Wed, 15 Dec 1999 17:32:19 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Wed, 15 Dec 1999 17:32:19 -0600 From: Chris Costello Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: <3857D1B0.66C930F9@newsguy.com> To: "Daniel C. Sobral" Cc: Wilko Bulte , Mark Newton , Peter Jeremy , Donn Miller , current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991215173219.N868@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <2177.945155945@zippy.cdrom.com> <3855F364.E66EC87B@cvzoom.net> <99Dec15.073843est.40325@border.alcanet.com.au> <19991215083352.B3500@internode.com.au> <19991215000600.C77327@yedi.iaf.nl> <19991214174432.Y868@holly.calldei.com> <3857D1B0.66C930F9@newsguy.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999, Daniel C. Sobral wrote: > GUI's are *NEVER* the faster way to administer. They can make faster a > very limited set of tasks. When I worked with AIX, even though I was > very comfortable with SMIT, at any time when I wanted to do something > fast, it was CLI all the way. > > Perhaps you mean "easy" instead of "quick"? Or maybe "quick" as in "flat > learning curve"? I'm not going out of my way to make it so that you'll see "Click this thing here to make it so that hackers cannot send floods to port XXX" I'll do my best to make it as featureful as what we have in our commands here. -- |Chris Costello |Never trust a computer you can't lift. - Stan Masor `---------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 15:36:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 9F65E153F3 for ; Wed, 15 Dec 1999 15:36:47 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40329>; Thu, 16 Dec 1999 10:28:04 +1100 Content-return: prohibited Date: Thu, 16 Dec 1999 10:36:27 +1100 From: Peter Jeremy Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) In-reply-to: <12873.945299269@critter.freebsd.dk>; from phk@critter.freebsd.dk on Thu, Dec 16, 1999 at 10:07:49AM +1100 To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Message-Id: <99Dec16.102804est.40329@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <99Dec16.095420est.40348@border.alcanet.com.au> <12873.945299269@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Dec-16 10:07:49 +1100, Poul-Henning Kamp wrote: >In message <99Dec16.095420est.40348@border.alcanet.com.au>, Peter Jeremy writes >: >>It can do that now. Add the following lines to /etc/ttys: >> >>sshd "/usr/local/sbin/sshd" none on >>inetd "/usr/sbin/inetd -Ww" none on >>syslogd "/usr/sbin/syslogd" none on >> >>(This ability has always been present, but is now documented). > >Yes, but apart from the highly unintuitive name "/etc/ttys" I agree that it's non-intuitive, but I doubt that any attempt to change the name would survive very long. >I would prefer if the lines could be added to /etc/ttys somewhat >like: > sshd "/usr/local/sbin/sshd" none ondemand > >And then we could > telinit -on sshd > telinit -off sshd This looks nice. The major problem I see is coming up with a secure mechanism for passing the daemon name from telinit to init. (And the issue of whether the state should be persistent over reboots - which is regularly hashed to death whenever DEVFS comes up). And, whilst it's even less intuitive than /etc/ttys, we already have equivalent functionality now (assuming you have an entry in /dev for a non-existent device). The state in /etc/ttys always is `on'. Using sshd as an example: To enable: rm -f /dev/sshd kill -HUP 1 To disable: ln -s /dev/some_device_that_isnt_configured /dev/sshd kill -HUP 1 (This works because init will always try to open /dev/sshd. If the open returns ENXIO, it will skip that line. If the open succeeds, or fails with any other error (ie ENOENT) the line is accepted). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 15:55:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130]) by hub.freebsd.org (Postfix) with ESMTP id BF2ED15403 for ; Wed, 15 Dec 1999 15:55:48 -0800 (PST) (envelope-from lyndon@orthanc.ab.ca) Received: from orthanc.ab.ca (localhost.orthanc.ab.ca [127.0.0.1]) by orthanc.ab.ca (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id dBFNtlQ25471 for ; Wed, 15 Dec 1999 16:55:47 -0700 (MST) Message-Id: <199912152355.dBFNtlQ25471@orthanc.ab.ca> To: current@FreeBSD.ORG Subject: Re: Init (was MAKEDEV et al) In-reply-to: Your message of "Thu, 16 Dec 1999 10:36:27 +1100." <99Dec16.102804est.40329@border.alcanet.com.au> Date: Wed, 15 Dec 1999 16:55:46 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Peter" == Peter Jeremy writes: >> And then we could telinit -on sshd telinit -off sshd Peter> This looks nice. The major problem I see is coming up with Peter> a secure mechanism for passing the daemon name from telinit Peter> to init. Named sockets work well for this sort of control channel. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 16:43:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 7A83F14D35 for ; Wed, 15 Dec 1999 16:43:07 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id LAA03852; Thu, 16 Dec 1999 11:10:09 +1030 (CST) (envelope-from newton) Date: Thu, 16 Dec 1999 11:10:09 +1030 From: Mark Newton To: Wilko Bulte Cc: Poul-Henning Kamp , "Jordan K. Hubbard" , patrick@whetstonelogic.com, chris@calldei.com, dmmiller@cvzoom.net, ejon@colltech.com, current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991216111009.D3456@internode.com.au> References: <56300.945288255@zippy.cdrom.com> <11991.945289444@critter.freebsd.dk> <19991215222140.C3264@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <19991215222140.C3264@yedi.iaf.nl> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 10:21:40PM +0100, Wilko Bulte wrote: > > "flourocarbons" > > fluorocarbons aka CFK. There is a relation with computing: Seymour used > them to keep his machines thermally sound. Call it "cfc" -- "The tool you want to use when you want to keep FreeBSD cool." :-) - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 18:13:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 33B6A14C01 for ; Wed, 15 Dec 1999 18:13:13 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id SAA25162; Wed, 15 Dec 1999 18:13:08 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA43374; Wed, 15 Dec 1999 18:13:08 -0800 (PST) (envelope-from obrien) Date: Wed, 15 Dec 1999 18:13:08 -0800 From: "David O'Brien" To: Forrest Aldrich Cc: freebsd-current@freebsd.org Subject: Re: Today's make world breakage Message-ID: <19991215181308.A43354@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <4.2.2.19991215141013.00abed80@216.67.12.69> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <4.2.2.19991215141013.00abed80@216.67.12.69>; from forrie@forrie.com on Wed, Dec 15, 1999 at 02:10:43PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 02:10:43PM -0500, Forrest Aldrich wrote: > cpp: }: No such file or directory > cpp: }: No such file or directory > mkdep: compile failed > *** Error code 1 Fixed. Thanks for the report. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 18:22:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from mppsystems.com (dslmpp.pro-ns.net [208.210.148.205]) by hub.freebsd.org (Postfix) with ESMTP id A14FF15220 for ; Wed, 15 Dec 1999 18:22:01 -0800 (PST) (envelope-from mpp@mppsystems.com) Received: (from mpp@localhost) by mppsystems.com (8.9.3/8.9.3) id TAA00949; Wed, 15 Dec 1999 19:46:04 -0600 (CST) (envelope-from mpp) Date: Wed, 15 Dec 1999 19:46:04 -0600 From: Mike Pritchard To: "D. Rock" Cc: current@FreeBSD.ORG Subject: Re: ATA problem Message-ID: <19991215194604.A887@mppsystems.com> References: <3858052D.A1298D60@dead-end.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <3858052D.A1298D60@dead-end.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 10:16:29PM +0100, D. Rock wrote: > Hi, > > The ata driver tries to enable UDMA for my controller, but fails > (this is no disk problem. The disks can do UDMA, as tested in > another machine). Perhaps UDMA should be disabled for all > VIA 82C586 chips: I have two machines with VIA 82C586 chips and they both seem to do UDMA just fine. Several days ago, one machine didn't work right with UDMA (it detected the disk as UDMA/66, but it is only a UDMA/33 disk), but today after a fresh cvsup and kernel build it seems to be working fine. See the dmesg output below. -Mike ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ad0: ATA-5 disk at ata0 as master ad0: 13029MB (26684784 sectors), 26473 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 Mounting root from ufs:/dev/ad0s2a -- Mike Pritchard mpp@FreeBSD.org or mpp@mppsystems.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 18:45:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 9E75214FE3 for ; Wed, 15 Dec 1999 18:45:54 -0800 (PST) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id DAA14424; Thu, 16 Dec 1999 03:46:02 +0100 (CET) (envelope-from assar) To: Cc: freebsd-current@FreeBSD.ORG Subject: Re: kernel crash via /usr/bin/ktrace References: <199912151724.MAA00818@barracuda.aquarium.rtci.com> From: Assar Westerlund Date: 16 Dec 1999 03:46:01 +0100 In-Reply-To: 's message of "Wed, 15 Dec 1999 12:24:22 -0500 (EST)" Message-ID: <5l3dt38uxi.fsf@assaris.sics.se> Lines: 10 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG writes: > While testing ktrace today for the FreeBSD-Audit project with smashwidgets, I > left the room and came back to my bios booting up. Unfortunatly smashwidgets > wasn't in full logging mode for speed, so I don't know what arguments or > environment variablesm were executed to trigger the crash. This might be related to kern/15204. But I don't have any fix, sorry :-( /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 19:12:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id BD64B15241 for ; Wed, 15 Dec 1999 19:12:23 -0800 (PST) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id WAA25429; Wed, 15 Dec 1999 22:12:19 -0500 (EST) (envelope-from mike@sentex.net) Received: from ospf-mdt.sentex.net (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id WAA14876; Wed, 15 Dec 1999 22:12:18 -0500 (EST) From: mike@sentex.net (Mike Tancsa) To: dgilbert@velocet.ca (David Gilbert) Cc: freebsd-current@freebsd.org Subject: Re: AMI MEGARAID problems. Date: Thu, 16 Dec 1999 03:12:17 GMT Message-ID: <385857ea.1734265521@mail.sentex.net> References: In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15 Dec 1999 13:50:33 -0500, in sentex.lists.freebsd.current you wrote: >I'm having trouble convincing -CURRENT to disklabel or newfs an AMI >MEGARAID adapter. > >amr0: irq 10 at device 11.1 on pci0 >amr0: firmware GH89 bios 1.41 16MB memory >amrd0: on amr0 >amrd0: 122647MB (251181056 sectors) RAID 5 (optimal) Try dd if=/dev/zero of=/dev/ramrd0 count=16 disklabel -rw amrd0 auto newfs amrd0c ---Mike Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 19:54:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from orange.kame.net (orange.kame.net [203.178.141.194]) by hub.freebsd.org (Postfix) with ESMTP id 34C951514C for ; Wed, 15 Dec 1999 19:54:07 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from localhost (kame209.kame.net [203.178.141.209]) by orange.kame.net (8.9.1+3.1W/3.7W) with ESMTP id MAA12353; Thu, 16 Dec 1999 12:54:00 +0900 (JST) To: davidc@lodge.guild.ab.ca Cc: current@FreeBSD.ORG Subject: Re: INET6 userland tools In-Reply-To: References: X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991216125426X.shin@nd.net.fujitsu.co.jp> Date: Thu, 16 Dec 1999 12:54:26 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 23 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I may be missing the obvious, but what is > everybody using for userland tools (ping6 etc) > on current? I haven't tried, but will the > kame-snap tools for 3 work? > > Thanks Now only ifconfig, route, and netstat support INET6 on the current. To support other tools, INET6 related library functions are need to be added into libc.(which was provided as independent static link library in KAME) Very INET6 specific patches are already prepared and under the review. getaddrinfo() and getaddrname() is not yet, but I'll also prepare them. And after those libraries are prepared, porting KAME tools onto current won't be difficult. Yoshinobu Inoue > Chad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 20:14:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from phnxpop1.phnx.uswest.net (phnxpop1.phnx.uswest.net [206.80.192.1]) by hub.freebsd.org (Postfix) with SMTP id 8CE1815392 for ; Wed, 15 Dec 1999 20:14:40 -0800 (PST) (envelope-from abed@uswest.net) Received: (qmail 28701 invoked by alias); 16 Dec 1999 04:13:52 -0000 Delivered-To: fixup-current@FreeBSD.ORG@fixme Received: (qmail 27094 invoked by uid 0); 16 Dec 1999 04:12:58 -0000 Received: from vdslg129.phnx.uswest.net (HELO uswest.net) (216.161.188.129) by phnxpop1.phnx.uswest.net with SMTP; 16 Dec 1999 04:12:58 -0000 Message-ID: <385868DB.84722BB2@uswest.net> Date: Wed, 15 Dec 1999 21:21:47 -0700 From: Alex Bedworth X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Daniel C. Sobral" Cc: Wilko Bulte , Mark Newton , Peter Jeremy , Donn Miller , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? References: <2177.945155945@zippy.cdrom.com> <3855F364.E66EC87B@cvzoom.net> <99Dec15.073843est.40325@border.alcanet.com.au> <19991215083352.B3500@internode.com.au> <19991215000600.C77327@yedi.iaf.nl> <3857D101.2AF01952@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel brings up a good point about SMIT (I don't know about SAM, not being a HP geek :) One helpful feature of SMIT/smitty is that it allows you to display the command that you are about to run. It also saves a history of its session in $HOME/smit.log, which can be used later to repeat actions taken, just a little better than script(1) ;-) For administration, this capability is VERY nice. I don't administer systems, but, occasionally, I have to install packages on a number of systems. Being able to see what 'goes on under the covers' is very helpful - especially if you're doing it for the first time, or are a 'casual' user, sometimes administrator. Having used LINUX since around '92, I am in love with FreeBSD's use of /usr/ports/*. Simply being able to type 'make install' in a port directory, and having everything magically installed is wonderful. If the point of this thread is for the basic 'sysinstall', leave the thing as it is. It works great. If [collective] we want to create an administrative tool, then I, as a user, would want for whatever tool that is to provide me with the information I need to create an action via script, or whatever. Let me see what command is being run, or at least give me the ability to view it. I also want to be able to copy/paste the command in its entirety to a script for use later. Just .02 from a user. Keep up the good work! "Daniel C. Sobral" wrote: > > Wilko Bulte wrote: > > > > This does, however, have all the risks of building yet another SMIT or > > SAM. :-( Neither attempt at making Unix sysadm 'user-friendly' makes > > me want to cheer. > > Actually, I very much like both SMIT (in it's 4.x incarnation) and SAM. > Sure, I'll complain loudly if that was the _only_ way of doing it, but > neither of these tools precludes you from cli and file-editing, nor > would we have to. > > -- > Daniel C. Sobral (8-DCS) > who is as social as a wampas > > dcs@newsguy.com > dcs@freebsd.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- The only thing to do with good advice is pass it on. It is never any use to oneself. -- Oscar Wilde To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 20:59:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 5185015511 for ; Wed, 15 Dec 1999 20:59:36 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id FAA19654 for freebsd-current@FreeBSD.ORG; Thu, 16 Dec 1999 05:59:35 +0100 (CET) (envelope-from olli) Date: Thu, 16 Dec 1999 05:59:35 +0100 (CET) From: Oliver Fromme Message-Id: <199912160459.FAA19654@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: syscons screenshot tool Organization: Administration TU Clausthal Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, As I mentioned in the "propellers" thread, I have a small tool that can be used to make screenshots of syscons VTYs. Here it is: http://www.fromme.com/syscons-screenshot/ There is a README with instructions, _please_ read it! Actually this is a quick hack, and the ioctl approach is a bit clumsy, so I haven't submitted it with send-pr yet. I will change the ioctl, clean the code up, write docs and submit the thing, unless someone else comes up with something better. I'm also under the impression that Mr. Syscons (Yokota?) is currently doing some design changes to syscons, so maybe I should wait until this is done, before submitting any further code. Regards Oliver PS: There is no need to Cc me, I'm on this list. However, if someone wants to mail me privately, please use the address olli@fromme.com -- the host from which I'm sending this is not prepared to receive email, and tin doesn't enable me to change the From line. Sorry for the inconvenience. -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 21:57:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from host.cer.ntnu.edu.tw (cer.ntnu.edu.tw [140.122.119.9]) by hub.freebsd.org (Postfix) with ESMTP id 3281615488 for ; Wed, 15 Dec 1999 21:57:51 -0800 (PST) (envelope-from clive@host.cer.ntnu.edu.tw) Received: (from clive@localhost) by host.cer.ntnu.edu.tw (8.9.3/8.9.3) id OAA86677 for freebsd-current@FreeBSD.ORG; Thu, 16 Dec 1999 14:00:39 +0800 (CST) (envelope-from clive) Date: Thu, 16 Dec 1999 14:00:39 +0800 From: Clive Lin To: FreeBSD Current Subject: make world breakage Message-ID: <19991216140039.A86641@host.cer.ntnu.edu.tw> Reply-To: Clive Lin Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD current source cvsuped about 2 hrs ago: ===> gnu/usr.bin/binutils/ld cc -Os -pipe -mpentiumpro -march=pentiumpro -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/ld/i386 -I/usr/src/gnu/usr.bin/binutils/ld -I/usr/src/gnu/usr.bin/binutils/ld/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/include -DDEFAULT_EMULATION=\"elf_i386\" -DTARGET=\"i386-unknown-freebsdelf\" -DSCRIPTDIR=\"/usr/obj/usr/src/i386/usr/libdata\" -I/usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld -I/usr/obj/usr/src/i386/usr/include -c eelf_i386.c eelf_i386.c:133: warning: initialization makes integer from pointer without a cast eelf_i386.c:133: initializer element is not constant eelf_i386.c:133: warning: data definition has no type or storage class eelf_i386.c:134: syntax error before `if' cpp: output pipe has been closed *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils/ld. *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. # root@cartier /usr/src> -- CirX Clive Lin FreeBSD - The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 22: 0:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7E28815511 for ; Wed, 15 Dec 1999 22:00:42 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA47882; Wed, 15 Dec 1999 22:00:20 -0800 (PST) (envelope-from dillon) Date: Wed, 15 Dec 1999 22:00:20 -0800 (PST) From: Matthew Dillon Message-Id: <199912160600.WAA47882@apollo.backplane.com> To: Andrew Gallatin Cc: freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem References: <14423.46117.353932.473968@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's a general update on this bug report to -current. It took all day but I was finally able to reproduce Andrew's bug. You guys are going to *love* this. NFS uses the kernel 'boottime' structure to generate its version id. Now normally you might believe that this structure, once set, will never change. The authors of NFS certainly make that assumption! No such luck. If you happen to be running, oh, xntpd for example, the kernel adjusts the boottime structure to take into account time changes, including PLL changes so, in fact, the boottime structure can change quite often - once each tick, in fact. Now, the effect of boottime changing on NFS is rather drastic. You see, the version id controls whether NFS clients must reset their state machines for NFS data writes. If a client has done a stage 1 write and is ready to do the stage 2 commit, and the version id changes, the client must revert back to stage 1. And so Andrews bug report comes into the light! His poor client (and mine once I reproduced the bug) got into a state, due to the server returning a different version id for virtually every packet, where it resent the same write data over the network over and over and over and over and over again. I think recent changes to the way the kernel clocks work in -current brought the bug out into the open, but it's definitely a problem in both -stable and -current. Doh! I gotta say that if I hadn't happened to have been running xntpd on my test box I would have *never* figured it out. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 22:17:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from wireless.net (wireless.net [207.137.156.159]) by hub.freebsd.org (Postfix) with ESMTP id 495FA15608 for ; Wed, 15 Dec 1999 22:17:27 -0800 (PST) (envelope-from dbutter@wireless.net) Received: from db.wireless.net (db.wireless.net [209.75.70.101]) by wireless.net (8.9.3/8.9.3) with ESMTP id WAA00324 for ; Wed, 15 Dec 1999 22:22:05 -0800 (PST) Received: from wireless.net (dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with ESMTP id WAA99889 for ; Wed, 15 Dec 1999 22:16:26 -0800 (PST) (envelope-from dbutter@wireless.net) Message-ID: <38588452.3383809C@wireless.net> Date: Wed, 15 Dec 1999 22:18:58 -0800 From: Devin Butterfield X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: ATA driver problem?? (lost disk contact) 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 just recently compiled a kernel with the new ATA driver and have discovered a problem: if I run sysinstall, right when it says "probing devices, please wait (this can be a while)" error messages saying... Dec 15 21:20:05 dbm /kernel: ata0-slave: ad_timeout: lost disk contact - resetting Dec 15 21:20:05 dbm /kernel: ata0: resetting devices .. done Dec 15 21:20:15 dbm /kernel: ata0-slave: ad_timeout: lost disk contact - resetting Dec 15 21:20:15 dbm /kernel: ata0: resetting devices .. done Dec 15 21:20:25 dbm /kernel: ata0-slave: ad_timeout: lost disk contact - resetting Dec 15 21:20:25 dbm /kernel: ata0: resetting devices .. done Dec 15 21:20:35 dbm /kernel: ata0-slave: ad_timeout: lost disk contact - resetting Dec 15 21:20:35 dbm /kernel: ata0-slave: ad_timeout: trying fallback to PIO mode Dec 15 21:20:35 dbm /kernel: ata0: resetting devices .. done and after printing these messages a number of times, sysinstall will finally come up. If I quit sysinstall and then run it again, probing goes well and there are no timeouts. The interesting thing is that I can reproduce this problem by rebooting and running sysinstall. So, this only happens when running sysinstall for the first time after a boot. :-/ I've read through all the previous messages regarding these timeout problems and have even increased the timeout in ata-disk.c to 10 secs but no luck. Anybody have any ideas?? Below is the usual info... -- Regards, Devin. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-19991214-CURRENT #1: Wed Dec 15 21:05:38 PST 1999 root@dbm.wireless.net:/usr/src/sys/compile/DBM Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (501.14-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 134152192 (131008K bytes) avail memory = 126500864 (123536K bytes) Preloaded elf kernel "kernel" at 0xc0378000. md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 15.0 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 dc0: <82c169 PNIC 10/100BaseTX> irq 10 at device 16.0 on pci0 dc0: Ethernet address: 00:a0:cc:27:48:ec miibus0: on dc0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ad0: ATA-5 disk at ata0 as master ad0: 8297MB (16992864 sectors), 16858 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad1: ATA-4 disk at ata0 as slave ad1: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 acd0: CDROM drive at ata1 as master acd0: read 1377KB/s (1377KB/s), 128KB buffer, PIO acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad0s2a cd0 at adv0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 22:21:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 1F9CF14CAB for ; Wed, 15 Dec 1999 22:21:44 -0800 (PST) (envelope-from vallo@solaris.matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id E5C632CE49; Thu, 16 Dec 1999 08:21:40 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 5F30DEC; Thu, 16 Dec 1999 08:21:37 +0200 (EET) Date: Thu, 16 Dec 1999 08:21:37 +0200 From: Vallo Kallaste To: Soren Schmidt Cc: Robert Watson , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991216082137.A49409@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <199912151801.TAA65973@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199912151801.TAA65973@freebsd.dk>; from Soren Schmidt on Wed, Dec 15, 1999 at 07:01:59PM +0100 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 07:01:59PM +0100, Soren Schmidt wrote: > That particular chip is so broken in so obscure ways, that most of the > "fixes" floating around doesn't. Its just plain broken, and should be > avoided totally and at all cost... It will be nice to let the user know about very broken hardware. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 22:23:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id A39EE14CED for ; Wed, 15 Dec 1999 22:23:48 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 8163 invoked from network); 16 Dec 1999 06:23:47 -0000 Received: from lcb13.cvzoom.net (HELO cvzoom.net) (63.65.159.13) by ns.cvzoom.net with SMTP; 16 Dec 1999 06:23:47 -0000 Message-ID: <38588536.8A0818CB@cvzoom.net> Date: Thu, 16 Dec 1999 01:22:46 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: David Scheidt Cc: Poul-Henning Kamp , Warner Losh , current@FreeBSD.ORG Subject: Re: Init Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) ) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Scheidt wrote: > What's wrong with run with system V runlevels? Other than it's system V and > everything AT^HUSL did is evil, of course. Well, the one danger is that we'd be slowly drifting away from the classic BSD way of doing thigs. Of course, the official BSD is dead (right?). But OTOH, we want to carry FreeBSD forward, so if that means we have to incorporate some SysVisms, then so be it. After all, SysV borrowed some things from BSD. The second question I have is, do we try to stay on par with what Open/NetBSD are doing? Should we stick together, synchronise our efforts, and try to define what comprises "BSD"? Or, do we let the 3 BSDs diverge completely? Well, if the 3 diverge too far (ex: FreeBSD implements SysV runlevels, OpenBSD does not or goes with an entirely different system), them would it be fair to consider FreeBSD "BSD"? The advantage here is that FreeBSD would mature into it's own type of UNIX with a BSD heritage. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 22:55:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 54967153D4 for ; Wed, 15 Dec 1999 22:55:09 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id RAA01356; Thu, 16 Dec 1999 17:23:42 +1030 (CST) (envelope-from newton) Date: Thu, 16 Dec 1999 17:23:42 +1030 From: Mark Newton To: Donn Miller Cc: David Scheidt , Poul-Henning Kamp , Warner Losh , current@FreeBSD.ORG Subject: Re: Init Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) ) Message-ID: <19991216172342.B1082@internode.com.au> References: <38588536.8A0818CB@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <38588536.8A0818CB@cvzoom.net> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 01:22:46AM -0500, Donn Miller wrote: > runlevels, OpenBSD does not or goes with an entirely different > system), them would it be fair to consider FreeBSD "BSD"? The > advantage here is that FreeBSD would mature into it's own type of > UNIX with a BSD heritage. Can we please not have this thread again? Anyone who is interested in following up on anything whatsoever to do with SysV runlevels should first familiarize themselves with the numerous problems they have which have been hashed out on the lists several times over the last 12 months (hint: to to the mail archive search engine at www.freebsd.org and search for "runlevel"). - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 23:24:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 486AE14D28 for ; Wed, 15 Dec 1999 23:24:18 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id IAA14378; Thu, 16 Dec 1999 08:24:01 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Andrew Gallatin , freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-reply-to: Your message of "Wed, 15 Dec 1999 22:00:20 PST." <199912160600.WAA47882@apollo.backplane.com> Date: Thu, 16 Dec 1999 08:24:01 +0100 Message-ID: <14376.945329041@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912160600.WAA47882@apollo.backplane.com>, Matthew Dillon writes: > Here's a general update on this bug report to -current. It took all day > but I was finally able to reproduce Andrew's bug. > > You guys are going to *love* this. > > NFS uses the kernel 'boottime' structure to generate its version id. > Now normally you might believe that this structure, once set, will > never change. The authors of NFS certainly make that assumption! Is this another case of "lets assume the time of day is a random number" or is there any underlying assumption about time in this ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 23:26:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.uninet.ee (ns.uninet.ee [194.204.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 486171557D for ; Wed, 15 Dec 1999 23:26:49 -0800 (PST) (envelope-from taavi@uninet.ee) Received: by ns.uninet.ee (Postfix, from userid 1001) id 39EAD2590F; Thu, 16 Dec 1999 09:26:43 +0200 (EET) Received: from localhost (localhost [127.0.0.1]) by ns.uninet.ee (Postfix) with SMTP id 33E9614A12 for ; Thu, 16 Dec 1999 09:26:43 +0200 (EET) Date: Thu, 16 Dec 1999 09:26:43 +0200 (EET) From: Taavi Talvik To: freebsd-current@freebsd.org Subject: amandad still freezes current 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 Hello ! running amanda over network still freezes current (1-2 days old). Script started on Thu Dec 16 09:20:23 1999 tt# gdb -k kernel.6 vmcore.6 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... (no debugging symbols found)... IdlePTD 3125248 initial pcb at 27aea0 panicstr: from debugger panic messages: --- panic: from debugger syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up on 1 buffers Uptime: 15h14m57s dumping to dev #ad/0x30001, offset 151232 dump ata0: resetting devices .. done 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 0xc013ec4c in boot () (kgdb) bt #0 0xc013ec4c in boot () #1 0xc013efe9 in panic () #2 0xc011dfa9 in db_panic () #3 0xc011df49 in db_command () #4 0xc011e00e in db_command_loop () #5 0xc012009f in db_trap () #6 0xc02079db in kdb_trap () #7 0xc0215c38 in trap () #8 0xc0207c37 in Debugger () #9 0xc02032d2 in scgetc () #10 0xc01fea19 in sckbdevent () #11 0xc01f350b in atkbd_intr () #12 0xc02235c4 in atkbd_isa_intr () #13 0xc02097c2 in vec1 () #14 0xc0147a1d in diskopen () #15 0xc0171b11 in spec_open () #16 0xc0171a0d in spec_vnoperate () #17 0xc01bf281 in ufs_vnoperatespec () #18 0xc016c0bc in vn_open () #19 0xc016851d in open () #20 0xc0216506 in syscall () #21 0xc02082e6 in Xint0x80_syscall () #22 0x804b91a in ?? () #23 0x804b6b3 in ?? () ---Type to continue, or q to quit--- #24 0x80491c0 in ?? () #25 0x80480f9 in ?? () (kgdb) q Script done on Thu Dec 16 09:20:55 1999 best regards, taavi ----------------------------------------------------------- Taavi Talvik | Internet: taavi@uninet.ee Unineti Andmeside AS | phone: +372 6405150 Ravala pst. 10 | fax: +372 6405151 Tallinn 10143, Estonia | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 23:27:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (ferg5200-1-30.cpinternet.com [208.149.16.30]) by hub.freebsd.org (Postfix) with ESMTP id 1D75A14D08 for ; Wed, 15 Dec 1999 23:27:15 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id BAA02277; Thu, 16 Dec 1999 01:26:35 -0600 (CST) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 16 Dec 1999 01:26:33 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: wilko@yedi.iaf.nl Cc: current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14424.37823.671739.167701@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > System Housekeeping Advanced Management Utility ? > > [ can we loose the H please? Sounds like a broom to me ] SHyshtem advanshed managedment utilititily? (hic) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 23:29:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 84EC0153B0 for ; Wed, 15 Dec 1999 23:29:25 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA58142; Thu, 16 Dec 1999 08:29:14 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912160729.IAA58142@freebsd.dk> Subject: Re: ATA driver problem?? (lost disk contact) In-Reply-To: <38588452.3383809C@wireless.net> from Devin Butterfield at "Dec 15, 1999 10:18:58 pm" To: dbutter@wireless.net (Devin Butterfield) Date: Thu, 16 Dec 1999 08:29:14 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Devin Butterfield wrote: > Hi, > > I just recently compiled a kernel with the new ATA driver and have > discovered a problem: if I run sysinstall, right when it says "probing > devices, please wait (this can be a while)" error messages saying... [snip] > and after printing these messages a number of times, sysinstall will > finally come up. If I quit sysinstall and then run it again, probing > goes well and there are no timeouts. The interesting thing is that I can > reproduce this problem by rebooting and running sysinstall. So, this > only happens when running sysinstall for the first time after a boot. > :-/ > > I've read through all the previous messages regarding these timeout > problems and have even increased the timeout in ata-disk.c to 10 secs > but no luck. Hmm, I'd put my disks on different channels, but thats just for performance sake. I'm currently trying every wierd setup I can imagine with the HW I have for testing, but I havn't been able to get any of my test setups to exhibit this behavior... But I'm working on it... -Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 23:43:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id D40C514FF5 for ; Wed, 15 Dec 1999 23:43:10 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA49890; Wed, 15 Dec 1999 23:43:06 -0800 (PST) (envelope-from dillon) Date: Wed, 15 Dec 1999 23:43:06 -0800 (PST) From: Matthew Dillon Message-Id: <199912160743.XAA49890@apollo.backplane.com> To: Poul-Henning Kamp Cc: Andrew Gallatin , freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem References: <14376.945329041@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> NFS uses the kernel 'boottime' structure to generate its version id. :> Now normally you might believe that this structure, once set, will :> never change. The authors of NFS certainly make that assumption! : :Is this another case of "lets assume the time of day is a random number" or :is there any underlying assumption about time in this ? : :-- :Poul-Henning Kamp FreeBSD coreteam member :phk@FreeBSD.ORG "Real hackers run -current on their laptop." It basically needs to be a unique for each server reboot in order to allow clients to resynchronize. The time has historically been used for this purpose since NFS networks tend to require ntp synchronization anyway. The time was used even before systems had realtime clocks -- the kernel would load it's initial time from the last access time stamp in the root filesystem (or superblock, I forget which it was). Under NFSv2 it wasn't as critical. Under NFSv3 the protocol will break badly if the number stays the same across a reboot - there would be a massive loss of data. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 23:51: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 834FA1557D for ; Wed, 15 Dec 1999 23:51:06 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id IAA14569; Thu, 16 Dec 1999 08:50:59 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Andrew Gallatin , freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-reply-to: Your message of "Wed, 15 Dec 1999 23:43:06 PST." <199912160743.XAA49890@apollo.backplane.com> Date: Thu, 16 Dec 1999 08:50:59 +0100 Message-ID: <14567.945330659@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912160743.XAA49890@apollo.backplane.com>, Matthew Dillon writes: > >:> NFS uses the kernel 'boottime' structure to generate its version id. >:> Now normally you might believe that this structure, once set, will >:> never change. The authors of NFS certainly make that assumption! >: >:Is this another case of "lets assume the time of day is a random number" or >:is there any underlying assumption about time in this ? >: >:-- >:Poul-Henning Kamp FreeBSD coreteam member >:phk@FreeBSD.ORG "Real hackers run -current on their laptop." > > It basically needs to be a unique for each server reboot in order > to allow clients to resynchronize. Ok, then I suggest that you cache a copy of the boottime in the NFS code for this purpose. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 15 23:58:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id C96CC14FF5 for ; Wed, 15 Dec 1999 23:58:42 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id BAA87332; Thu, 16 Dec 1999 01:58:52 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <199912160758.BAA87332@celery.dragondata.com> Subject: Re: Serious server-side NFS problem To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Thu, 16 Dec 1999 01:58:52 -0600 (CST) Cc: dillon@apollo.backplane.com (Matthew Dillon), gallatin@cs.duke.edu (Andrew Gallatin), freebsd-current@FreeBSD.ORG In-Reply-To: <14567.945330659@critter.freebsd.dk> from "Poul-Henning Kamp" at Dec 16, 1999 08:50:59 AM X-Mailer: ELM [version 2.5 PL1] 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 > > In message <199912160743.XAA49890@apollo.backplane.com>, Matthew Dillon writes: > > > >:> NFS uses the kernel 'boottime' structure to generate its version id. > >:> Now normally you might believe that this structure, once set, will > >:> never change. The authors of NFS certainly make that assumption! > >: > >:Is this another case of "lets assume the time of day is a random number" or > >:is there any underlying assumption about time in this ? > >: > >:-- > >:Poul-Henning Kamp FreeBSD coreteam member > >:phk@FreeBSD.ORG "Real hackers run -current on their laptop." > > > > It basically needs to be a unique for each server reboot in order > > to allow clients to resynchronize. > > Ok, then I suggest that you cache a copy of the boottime in the NFS > code for this purpose. > Ack, I was using this very same thing for several devices in an isolated peer-to-peer network to decide who the 'master' was. (Whoever had been up longest knew more about the state of the network) Having this change could cause weirdness for me too... I assumed (without checking *thwap*) that boottime was a constant. Perhaps a 'real_boottime' or 'unadjusted_boottime' that gets copied after 'boottime' gets initialized so that others can use it, not just NFS? :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 0: 2:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 13C3614E50 for ; Thu, 16 Dec 1999 00:02:12 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA50074; Thu, 16 Dec 1999 00:01:54 -0800 (PST) (envelope-from dillon) Date: Thu, 16 Dec 1999 00:01:54 -0800 (PST) From: Matthew Dillon Message-Id: <199912160801.AAA50074@apollo.backplane.com> To: Kevin Day Cc: phk@critter.freebsd.dk (Poul-Henning Kamp), gallatin@cs.duke.edu (Andrew Gallatin), freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem References: <199912160758.BAA87332@celery.dragondata.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> :> In message <199912160743.XAA49890@apollo.backplane.com>, Matthew Dillon writes: :> > :> >:> NFS uses the kernel 'boottime' structure to generate its version id. :> >:> Now normally you might believe that this structure, once set, will :> >:> never change. The authors of NFS certainly make that assumption! :> >: :> >:Is this another case of "lets assume the time of day is a random number" or :> >:is there any underlying assumption about time in this ? :> >: :> >:-- :> >:Poul-Henning Kamp FreeBSD coreteam member :> >:phk@FreeBSD.ORG "Real hackers run -current on their laptop." :> > :> > It basically needs to be a unique for each server reboot in order :> > to allow clients to resynchronize. :> :> Ok, then I suggest that you cache a copy of the boottime in the NFS :> code for this purpose. :> : :Ack, I was using this very same thing for several devices in an isolated :peer-to-peer network to decide who the 'master' was. (Whoever had been up :longest knew more about the state of the network) Having this change could :cause weirdness for me too... I assumed (without checking *thwap*) that :boottime was a constant. : :Perhaps a 'real_boottime' or 'unadjusted_boottime' that gets copied after :'boottime' gets initialized so that others can use it, not just NFS? :) : : :Kevin We're already testing a patch. For the moment it is going to be NFS specific, because there's no time right now to do it right. Hopefully I can get this in tomorrow and be done with NFS for the release. Then I can spend a little time figuring out what's wrong with VN (which doesn't work in current at the moment). Again. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 0:19:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 3A29F14F23 for ; Thu, 16 Dec 1999 00:19:43 -0800 (PST) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 741A61DEA; Thu, 16 Dec 1999 09:19:50 +0100 (CET) Date: Thu, 16 Dec 1999 09:19:50 +0100 From: "Dave J. Boers" To: freebsd-current@freebsd.org Cc: sos@freebsd.dk Subject: Re: ATA driver problem?? (lost disk contact) Message-ID: <19991216091950.B8469@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <38588452.3383809C@wireless.net> <199912160729.IAA58142@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199912160729.IAA58142@freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 08:29:14AM +0100, Soren Schmidt wrote: > It seems Devin Butterfield wrote: > > I just recently compiled a kernel with the new ATA driver and have > > discovered a problem: if I run sysinstall, right when it says "probing > > devices, please wait (this can be a while)" error messages saying... > [snip] > > and after printing these messages a number of times, sysinstall will > > finally come up. If I quit sysinstall and then run it again, probing > > goes well and there are no timeouts. The interesting thing is that I can > > reproduce this problem by rebooting and running sysinstall. So, this > > only happens when running sysinstall for the first time after a boot. > > > Hmm, I'd put my disks on different channels, but thats just for > performance sake. I'm currently trying every wierd setup I can > imagine with the HW I have for testing, but I havn't been able > to get any of my test setups to exhibit this behavior... > > But I'm working on it... I am still having "disc contact lost messages" regularly too. I've been posting about them on several occasions some time ago. I haven't been able to pinn it down, however. IF they occur, they occur somewhere between 9:15 and 9:20 a.m. OR p.m. But they don't always. This used to be 10:15, but that changed _some weeks after_ the change of daylight saving time. I can't seem to relate it to anything. It is unlikely that it's a power glitch, because the system has been displaying the problem with two different UPS's. The machine is running current current's which are regularly updated. It's an ABIT BP6 and the disk causing problems is a WD 7200 RPM 18,2 Gb disk running UDMA33. It's the only IDE disk in the system; the other disks are all SCSI. The system is running 24/7. Other details were posted earlier. There are two important aspects of the problem: 1. The problem does not always occur: it's unpredictable 2. When it occurs, I can actually hear the disk spinning down and then up again. I haven't been able to find any relevant information at www.wdc.com. I am also not sure if it is a hardware problem, however since I never noticed the problem with the wd0 driver (which I used some months ago). Regards, Dave Boers. -- God, root, what's the difference? djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 0:25:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 61DA215516 for ; Thu, 16 Dec 1999 00:25:15 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA71207; Thu, 16 Dec 1999 09:25:11 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912160825.JAA71207@freebsd.dk> Subject: Re: ATA driver problem?? (lost disk contact) In-Reply-To: <19991216091950.B8469@relativity.student.utwente.nl> from "Dave J. Boers" at "Dec 16, 1999 09:19:50 am" To: djb@Wit389306.student.utwente.nl Date: Thu, 16 Dec 1999 09:25:11 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Dave J. Boers wrote: > > I am still having "disc contact lost messages" regularly too. I've been > posting about them on several occasions some time ago. I haven't been able > to pinn it down, however. IF they occur, they occur somewhere between 9:15 > and 9:20 a.m. OR p.m. But they don't always. This used to be 10:15, but > that changed _some weeks after_ the change of daylight saving time. I can't > seem to relate it to anything. It is unlikely that it's a power glitch, > because the system has been displaying the problem with two different > UPS's. > > The machine is running current current's which are regularly updated. It's > an ABIT BP6 and the disk causing problems is a WD 7200 RPM 18,2 Gb disk > running UDMA33. It's the only IDE disk in the system; the other disks are > all SCSI. The system is running 24/7. Other details were posted earlier. There is this thing with the IBM's doing some headcleaning stuff once a day/week, but I've never seen any of my IBM's do that (I got plenty of them). I'll try to get more info on that from IBM... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 0:36:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4F0C015669 for ; Thu, 16 Dec 1999 00:36:46 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA73900; Thu, 16 Dec 1999 09:36:42 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912160836.JAA73900@freebsd.dk> Subject: Re: ATA driver problem?? (lost disk contact) In-Reply-To: <199912160825.JAA71207@freebsd.dk> from Soren Schmidt at "Dec 16, 1999 09:25:11 am" To: sos@freebsd.dk (Soren Schmidt) Date: Thu, 16 Dec 1999 09:36:42 +0100 (CET) Cc: djb@Wit389306.student.utwente.nl, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Soren Schmidt wrote: > It seems Dave J. Boers wrote: > > > > I am still having "disc contact lost messages" regularly too. I've been > > posting about them on several occasions some time ago. I haven't been able > > to pinn it down, however. IF they occur, they occur somewhere between 9:15 > > and 9:20 a.m. OR p.m. But they don't always. This used to be 10:15, but > > that changed _some weeks after_ the change of daylight saving time. I can't > > seem to relate it to anything. It is unlikely that it's a power glitch, > > because the system has been displaying the problem with two different > > UPS's. > > > > The machine is running current current's which are regularly updated. It's > > an ABIT BP6 and the disk causing problems is a WD 7200 RPM 18,2 Gb disk > > running UDMA33. It's the only IDE disk in the system; the other disks are > > all SCSI. The system is running 24/7. Other details were posted earlier. > > There is this thing with the IBM's doing some headcleaning stuff once > a day/week, but I've never seen any of my IBM's do that (I got plenty > of them). I'll try to get more info on that from IBM... One more thing, do you have SMART enabled in your BIOS ??, if so turn it off, and see if that changes anything... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 0:49:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 17EF715516 for ; Thu, 16 Dec 1999 00:49:30 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA14781; Thu, 16 Dec 1999 09:49:07 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Kevin Day Cc: dillon@apollo.backplane.com (Matthew Dillon), gallatin@cs.duke.edu (Andrew Gallatin), freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-reply-to: Your message of "Thu, 16 Dec 1999 01:58:52 CST." <199912160758.BAA87332@celery.dragondata.com> Date: Thu, 16 Dec 1999 09:49:07 +0100 Message-ID: <14779.945334147@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912160758.BAA87332@celery.dragondata.com>, Kevin Day writes: >Ack, I was using this very same thing for several devices in an isolated >peer-to-peer network to decide who the 'master' was. (Whoever had been up >longest knew more about the state of the network) Having this change could >cause weirdness for me too... I assumed (without checking *thwap*) that >boottime was a constant. > >Perhaps a 'real_boottime' or 'unadjusted_boottime' that gets copied after >'boottime' gets initialized so that others can use it, not just NFS? :) no, I think that is a bad idea. In your case you want to use the "uptime" which *is* a measure of how long the system has been running. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 0:54:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id C0A8D14F0C for ; Thu, 16 Dec 1999 00:54:35 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id IAA00488 for freebsd-current@FreeBSD.ORG; Thu, 16 Dec 1999 08:55:35 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199912151624.RAA01525@dorifer.heim3.tu-clausthal.de> Date: Thu, 16 Dec 1999 08:55:35 -0000 (GMT) From: "Steve O'Hara-Smith" To: freebsd-current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15-Dec-99 Oliver Fromme wrote: > Alexander Langer wrote in list.freebsd-current: > > gunzip has approx 106 kb, but you save about 50% per executeable. > > -r-xr-xr-x 1 root wheel 4648 Jan 28 1999 /usr/bin/minigzip It requires the 50Kb libz.so.2 though and some of libc. ------------------------------------------------------- Tell a computer to WIN and ... ... You lose ------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 1: 2: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id BD33A14F5D for ; Thu, 16 Dec 1999 01:01:59 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id BAA25491; Thu, 16 Dec 1999 01:01:25 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912160901.BAA25491@gndrsh.dnsmgr.net> Subject: Re: Init Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) ) In-Reply-To: <19991216172342.B1082@internode.com.au> from Mark Newton at "Dec 16, 1999 05:23:42 pm" To: newton@internode.com.au (Mark Newton) Date: Thu, 16 Dec 1999 01:01:25 -0800 (PST) Cc: dmmiller@cvzoom.net (Donn Miller), dscheidt@enteract.com (David Scheidt), phk@critter.freebsd.dk (Poul-Henning Kamp), imp@village.org (Warner Losh), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 > On Thu, Dec 16, 1999 at 01:22:46AM -0500, Donn Miller wrote: > > > runlevels, OpenBSD does not or goes with an entirely different > > system), them would it be fair to consider FreeBSD "BSD"? The > > advantage here is that FreeBSD would mature into it's own type of > > UNIX with a BSD heritage. > > Can we please not have this thread again? Anyone who is interested > in following up on anything whatsoever to do with SysV runlevels > should first familiarize themselves with the numerous problems they > have which have been hashed out on the lists several times over the > last 12 months (hint: to to the mail archive search engine at > www.freebsd.org and search for "runlevel"). Only correction here is ``over the last 7 years'' not ``12 months''. This will be atleast the 4th time we have been over this... -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 1: 6:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from wireless.net (wireless.net [207.137.156.159]) by hub.freebsd.org (Postfix) with ESMTP id 8BF2815587 for ; Thu, 16 Dec 1999 01:06:46 -0800 (PST) (envelope-from dbutter@wireless.net) Received: from db.wireless.net (db.wireless.net [209.75.70.101]) by wireless.net (8.9.3/8.9.3) with ESMTP id BAA00643; Thu, 16 Dec 1999 01:11:29 -0800 (PST) Received: from wireless.net (dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with ESMTP id BAA00282; Thu, 16 Dec 1999 01:05:48 -0800 (PST) (envelope-from dbutter@wireless.net) Message-ID: <3858AC04.1ACEB813@wireless.net> Date: Thu, 16 Dec 1999 01:08:20 -0800 From: Devin Butterfield X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: djb@Wit389306.student.utwente.nl Cc: freebsd-current@FreeBSD.ORG Subject: Re: ATA driver problem?? (lost disk contact) References: <38588452.3383809C@wireless.net> <199912160729.IAA58142@freebsd.dk> <19991216091950.B8469@relativity.student.utwente.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, "Dave J. Boers" wrote: > > On Thu, Dec 16, 1999 at 08:29:14AM +0100, Soren Schmidt wrote: > > It seems Devin Butterfield wrote: > > > I just recently compiled a kernel with the new ATA driver and have > > > discovered a problem: if I run sysinstall, right when it says "probing > > > devices, please wait (this can be a while)" error messages saying... > > [snip] > > > and after printing these messages a number of times, sysinstall will > > > finally come up. If I quit sysinstall and then run it again, probing > > > goes well and there are no timeouts. The interesting thing is that I can > > > reproduce this problem by rebooting and running sysinstall. So, this > > > only happens when running sysinstall for the first time after a boot. > > > > > > Hmm, I'd put my disks on different channels, but thats just for > > performance sake. I'm currently trying every wierd setup I can > > imagine with the HW I have for testing, but I havn't been able > > to get any of my test setups to exhibit this behavior... > > > > But I'm working on it... > > I am still having "disc contact lost messages" regularly too. I've been > posting about them on several occasions some time ago. [SNIP] > There are two important aspects of the problem: > > 1. The problem does not always occur: it's unpredictable > 2. When it occurs, I can actually hear the disk spinning down and then up > again. > [SNIP] That's interesting...In my case it is quite easily reproduced (very predictable). All I have to do is reboot and then run sysinstall and when it probes the devices the disks time out. So far I have not been able to get this behavior at any other time. I should also note that it repeatedly try's "resetting devices...done." many times (number of times it does this varies). Soren, since the problem is reproducible in my case, can you think of anything else I can try to help shed some light on what might be causing these time-outs we are having? Thanks again! -- Regards, Devin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 1:14:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 6C70715575 for ; Thu, 16 Dec 1999 01:14:31 -0800 (PST) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 27C501DEA; Thu, 16 Dec 1999 10:14:39 +0100 (CET) Date: Thu, 16 Dec 1999 10:14:39 +0100 From: "Dave J. Boers" To: Soren Schmidt Cc: freebsd-current@freebsd.org Subject: Re: ATA driver problem?? (lost disk contact) Message-ID: <19991216101439.A8685@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <199912160825.JAA71207@freebsd.dk> <199912160836.JAA73900@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199912160836.JAA73900@freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 09:36:42AM +0100, Soren Schmidt wrote: > One more thing, do you have SMART enabled in your BIOS ??, if so > turn it off, and see if that changes anything... I don't recall having it enabled; but I will check to make sure as soon as I get home from work (which is still some 10 hours away ). Regards, Dave Boers. -- God, root, what's the difference? djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 1:41:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 464EC14FE2 for ; Thu, 16 Dec 1999 01:41:42 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA89041; Thu, 16 Dec 1999 10:41:35 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912160941.KAA89041@freebsd.dk> Subject: Re: ATA driver problem?? (lost disk contact) In-Reply-To: <3858AC04.1ACEB813@wireless.net> from Devin Butterfield at "Dec 16, 1999 01:08:20 am" To: dbutter@wireless.net (Devin Butterfield) Date: Thu, 16 Dec 1999 10:41:35 +0100 (CET) Cc: djb@Wit389306.student.utwente.nl, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Devin Butterfield wrote: > That's interesting...In my case it is quite easily reproduced (very > predictable). All I have to do is reboot and then run sysinstall and > when it probes the devices the disks time out. So far I have not been > able to get this behavior at any other time. > > I should also note that it repeatedly try's "resetting devices...done." > many times (number of times it does this varies). > > Soren, since the problem is reproducible in my case, can you think of > anything else I can try to help shed some light on what might be causing > these time-outs we are having? Hmm, does the problem persist if you increase the timeout in ata-disk.c to some too big value, like 100 secs or so?? If so, there is something causing the timeout function to be called without a real timeout. This could be the problem, I just dont see how that would be possible... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 1:44:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id D51CC155BB for ; Thu, 16 Dec 1999 01:44:40 -0800 (PST) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 5D43D1DEA; Thu, 16 Dec 1999 10:44:47 +0100 (CET) Date: Thu, 16 Dec 1999 10:44:47 +0100 From: "Dave J. Boers" To: Max Khon Cc: freebsd-current@freebsd.org Subject: Re: ATA driver problem?? (lost disk contact) Message-ID: <19991216104447.A8757@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <19991216091950.B8469@relativity.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 03:29:30PM +0600, Max Khon wrote: > hi, there! > same here, dmesg output: > > ata_command: timeout waiting for interrupt > Mounting root from ufs:/dev/ad0s2a > ata0-master: ad_timeout: lost disk contact - resetting > ata0: resetting devices .. done > ata0-master: ad_timeout: lost disk contact - resetting > ata0: resetting devices .. done > ata0-master: ad_timeout: lost disk contact - resetting > ata0: resetting devices .. done > ata0-master: ad_timeout: lost disk contact - resetting > ata0: resetting devices .. done > ata0-master: ad_timeout: lost disk contact - resetting > ata0: resetting devices .. done > ata0-master: ad_timeout: lost disk contact - resetting > ata0: resetting devices .. done > ata0-master: ad_timeout: lost disk contact - resetting > ata0: resetting devices .. done Could you tell met the exact time on which these messages occurred? Anywhere near 10:15 or 9:15 ? Regards, Dave Boers. -- God, root, what's the difference? [djb,bofh,coredump,root]@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 2: 0:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from wireless.net (wireless.net [207.137.156.159]) by hub.freebsd.org (Postfix) with ESMTP id B62AE15602 for ; Thu, 16 Dec 1999 02:00:45 -0800 (PST) (envelope-from dbutter@wireless.net) Received: from db.wireless.net (db.wireless.net [209.75.70.101]) by wireless.net (8.9.3/8.9.3) with ESMTP id CAA00802; Thu, 16 Dec 1999 02:05:28 -0800 (PST) Received: from wireless.net (dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with ESMTP id BAA00356; Thu, 16 Dec 1999 01:59:47 -0800 (PST) (envelope-from dbutter@wireless.net) Message-ID: <3858B8AA.53468C2@wireless.net> Date: Thu, 16 Dec 1999 02:02:18 -0800 From: Devin Butterfield X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: ATA driver problem?? Solution (in my case)! References: <199912160825.JAA71207@freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Soren/group, After spending a little time sniffing around in my BIOS I realized that my BIOS (Award BIOS) defaults to disabling UDMA for both master and slave and for some reason I never thought to check this....duh. Anyway after setting this to "auto" for both master and slave the problem seems to be fixed! This is curious because I was running the wd driver with the BIOS set wrong all along and never had any errors or problems (AFAIK). So why does the wd driver seem to ignore this incorrect configuration while the ata driver trips over it? Does this help anyone? Thanks again for your help Soren/everyone else. -- Regards, Devin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 2: 6: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 60BC8155C9 for ; Thu, 16 Dec 1999 02:05:54 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id QAA67394; Thu, 16 Dec 1999 16:05:29 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Thu, 16 Dec 1999 16:05:28 +0600 (NS) From: Max Khon To: "Dave J. Boers" Cc: freebsd-current@FreeBSD.ORG Subject: Re: ATA driver problem?? (lost disk contact) In-Reply-To: <19991216104447.A8757@relativity.student.utwente.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 hi, there! On Thu, 16 Dec 1999, Dave J. Boers wrote: > Could you tell met the exact time on which these messages occurred? > Anywhere near 10:15 or 9:15 ? nope. the time is unpredictable. sometimes it can work more than a day without spilling out those messages /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 2:12:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 99612155CC for ; Thu, 16 Dec 1999 02:11:43 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id PAA64008; Thu, 16 Dec 1999 15:29:30 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Thu, 16 Dec 1999 15:29:30 +0600 (NS) From: Max Khon To: "Dave J. Boers" Cc: freebsd-current@FreeBSD.ORG, sos@freebsd.dk Subject: Re: ATA driver problem?? (lost disk contact) In-Reply-To: <19991216091950.B8469@relativity.student.utwente.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 hi, there! On Thu, 16 Dec 1999, Dave J. Boers wrote: > I am still having "disc contact lost messages" regularly too. [...] > There are two important aspects of the problem: > > 1. The problem does not always occur: it's unpredictable > 2. When it occurs, I can actually hear the disk spinning down and then up > again. > > I haven't been able to find any relevant information at www.wdc.com. I am > also not sure if it is a hardware problem, however since I never noticed > the problem with the wd0 driver (which I used some months ago). same here, dmesg output: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Mon Nov 29 20:58:28 NOVT 1999 root@:/usr/src/sys/compile/lark Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (349.41-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 134217728 (131072K bytes) avail memory = 126251008 (123292K bytes) Preloaded elf kernel "kernel" at 0xc037b000. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 11 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pci0: UHCI USB controller (vendor=0x8086, dev=0x7112) at 7.2 chip1: at device 7.3 on pci0 pci0: unknown card (vendor=0x1274, dev=0x1371) at 12.0 irq 10 xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 10 at device 15.0 on pci0 xl0: Ethernet address: 00:50:04:03:31:b7 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model NetMouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 ad0: ATA-4 disk at ata0 as master ad0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 32 depth queue, UDMA33 acd0: CDROM drive at ata1 as master acd0: read 5512KB/s (5512KB/s), 256KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked ata_command: timeout waiting for interrupt Mounting root from ufs:/dev/ad0s2a ata0-master: ad_timeout: lost disk contact - resetting ata0: resetting devices .. done ata0-master: ad_timeout: lost disk contact - resetting ata0: resetting devices .. done ata0-master: ad_timeout: lost disk contact - resetting ata0: resetting devices .. done ata0-master: ad_timeout: lost disk contact - resetting ata0: resetting devices .. done ata0-master: ad_timeout: lost disk contact - resetting ata0: resetting devices .. done ata0-master: ad_timeout: lost disk contact - resetting ata0: resetting devices .. done ata0-master: ad_timeout: lost disk contact - resetting ata0: resetting devices .. done /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 2:45:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id AC81A14D8E for ; Thu, 16 Dec 1999 02:45:45 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id LAA04163; Thu, 16 Dec 1999 11:45:40 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912161045.LAA04163@freebsd.dk> Subject: Re: ATA driver problem?? Solution (in my case)! In-Reply-To: <3858B8AA.53468C2@wireless.net> from Devin Butterfield at "Dec 16, 1999 02:02:18 am" To: dbutter@wireless.net (Devin Butterfield) Date: Thu, 16 Dec 1999 11:45:40 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Devin Butterfield wrote: > Hi Soren/group, > > After spending a little time sniffing around in my BIOS I realized that > my BIOS (Award BIOS) defaults to disabling UDMA for both master and > slave and for some reason I never thought to check this....duh. Anyway > after setting this to "auto" for both master and slave the problem seems > to be fixed! > > This is curious because I was running the wd driver with the BIOS set > wrong all along and never had any errors or problems (AFAIK). So why > does the wd driver seem to ignore this incorrect configuration while the > ata driver trips over it? > > Does this help anyone? Hmm, maybe. Try the below patch, but with the BIOS again in the disabled position, and see if it still fails. Index: ata-dma.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-dma.c,v retrieving revision 1.23 diff -u -r1.23 ata-dma.c --- ata-dma.c 1999/12/14 10:25:25 1.23 +++ ata-dma.c 1999/12/16 10:44:51 @@ -227,6 +227,12 @@ pci_write_config(scp->dev, 0x53, pci_read_config(scp->dev, 0x53, 1) | 0x03, 1); scp->flags |= ATA_ATAPI_DMA_RO; + if (device == ATA_MASTER) + outb(scp->bmaddr + ATA_BMSTAT_PORT, + inb(scp->bmaddr + ATA_BMSTAT_PORT) | ATA_BMSTAT_DMA_MASTER); + else + outb(scp->bmaddr + ATA_BMSTAT_PORT, + inb(scp->bmaddr + ATA_BMSTAT_PORT) | ATA_BMSTAT_DMA_SLAVE); scp->mode[(device == ATA_MASTER) ? 0 : 1] = ATA_MODE_UDMA2; return 0; } @@ -242,6 +248,12 @@ pci_write_config(scp->dev, 0x53, pci_read_config(scp->dev, 0x53, 1) | 0x03, 1); scp->flags |= ATA_ATAPI_DMA_RO; + if (device == ATA_MASTER) + outb(scp->bmaddr + ATA_BMSTAT_PORT, + inb(scp->bmaddr + ATA_BMSTAT_PORT) | ATA_BMSTAT_DMA_MASTER); + else + outb(scp->bmaddr + ATA_BMSTAT_PORT, + inb(scp->bmaddr + ATA_BMSTAT_PORT) | ATA_BMSTAT_DMA_SLAVE); scp->mode[(device == ATA_MASTER) ? 0 : 1] = ATA_MODE_WDMA2; return 0; } -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 2:58:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl4.philips.com (gw-nl4.philips.com [192.68.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 1FD8B14DAA for ; Thu, 16 Dec 1999 02:58:53 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl4.philips.com with ESMTP id LAA22444 for ; Thu, 16 Dec 1999 11:58:49 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl4.philips.com via mwrap (4.0a) id xma022439; Thu, 16 Dec 99 11:58:49 +0100 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with SMTP id LAA05966 for ; Thu, 16 Dec 1999 11:58:48 +0100 (MET) Received: (qmail 28965 invoked by uid 666); 16 Dec 1999 11:12:14 -0000 Date: Thu, 16 Dec 1999 12:12:14 +0100 From: Jos Backus To: current@FreeBSD.ORG Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) Message-ID: <19991216121214.B34062@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <99Dec16.095420est.40348@border.alcanet.com.au> <12873.945299269@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <12873.945299269@critter.freebsd.dk>; from phk@critter.freebsd.dk on Thu, Dec 16, 1999 at 12:07:49AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 12:07:49AM +0100, Poul-Henning Kamp wrote: > I would prefer if the lines could be added to /etc/ttys somewhat > like: > sshd "/usr/local/sbin/sshd" none ondemand > > And then we could > telinit -on sshd > telinit -off sshd hal:/service# ls -l telnetd total 2 -rwxr-xr-x 1 root wheel 64 Sep 20 11:34 run drwx------ 2 root wheel 512 Dec 14 16:09 supervise hal:/service# cat telnetd/run #!/bin/sh exec \ tcpserver -RH -D 0 telnet /usr/libexec/telnetd hal:/service# svstat telnetd telnetd: up (pid 224) hal:/service# svc -d telnetd hal:/service# svstat telnetd telnetd: down, normally up hal:/service# svc -u telnetd hal:/service# svstat telnetd telnetd: up (pid 40965) init's role is assumed by a program named svscan. Of course, svscan not being init, it cannot control daemons that background themselves. http://cr.yp.to/daemontools.html -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ 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 Dec 16 4:22:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from wireless.net (wireless.net [207.137.156.159]) by hub.freebsd.org (Postfix) with ESMTP id 059BA14F98 for ; Thu, 16 Dec 1999 04:22:56 -0800 (PST) (envelope-from dbutter@wireless.net) Received: from db.wireless.net (db.wireless.net [209.75.70.101]) by wireless.net (8.9.3/8.9.3) with ESMTP id EAA00968; Thu, 16 Dec 1999 04:27:40 -0800 (PST) Received: from wireless.net (dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with ESMTP id EAA00686; Thu, 16 Dec 1999 04:21:59 -0800 (PST) (envelope-from dbutter@wireless.net) Message-ID: <3858D9FD.2EA50F5A@wireless.net> Date: Thu, 16 Dec 1999 04:24:29 -0800 From: Devin Butterfield X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: freebsd-current@FreeBSD.org Subject: Re: ATA driver problem?? Solution (in my case)! References: <199912161045.LAA04163@freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Soren, No unfortunately it still fails with the patch and the UDMA disabled in the BIOS. I'd be happy to try anything else you can think of. :) Thanks. -- Regards, Devin. Soren Schmidt wrote: > > It seems Devin Butterfield wrote: > > Hi Soren/group, > > > > After spending a little time sniffing around in my BIOS I realized that > > my BIOS (Award BIOS) defaults to disabling UDMA for both master and > > slave and for some reason I never thought to check this....duh. Anyway > > after setting this to "auto" for both master and slave the problem seems > > to be fixed! > > > > This is curious because I was running the wd driver with the BIOS set > > wrong all along and never had any errors or problems (AFAIK). So why > > does the wd driver seem to ignore this incorrect configuration while the > > ata driver trips over it? > > > > Does this help anyone? > > Hmm, maybe. > > Try the below patch, but with the BIOS again in the disabled position, > and see if it still fails. > > Index: ata-dma.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/ata/ata-dma.c,v > retrieving revision 1.23 > diff -u -r1.23 ata-dma.c > --- ata-dma.c 1999/12/14 10:25:25 1.23 > +++ ata-dma.c 1999/12/16 10:44:51 > @@ -227,6 +227,12 @@ > pci_write_config(scp->dev, 0x53, > pci_read_config(scp->dev, 0x53, 1) | 0x03, 1); > scp->flags |= ATA_ATAPI_DMA_RO; > + if (device == ATA_MASTER) > + outb(scp->bmaddr + ATA_BMSTAT_PORT, > + inb(scp->bmaddr + ATA_BMSTAT_PORT) | ATA_BMSTAT_DMA_MASTER); > + else > + outb(scp->bmaddr + ATA_BMSTAT_PORT, > + inb(scp->bmaddr + ATA_BMSTAT_PORT) | ATA_BMSTAT_DMA_SLAVE); > scp->mode[(device == ATA_MASTER) ? 0 : 1] = ATA_MODE_UDMA2; > return 0; > } > @@ -242,6 +248,12 @@ > pci_write_config(scp->dev, 0x53, > pci_read_config(scp->dev, 0x53, 1) | 0x03, 1); > scp->flags |= ATA_ATAPI_DMA_RO; > + if (device == ATA_MASTER) > + outb(scp->bmaddr + ATA_BMSTAT_PORT, > + inb(scp->bmaddr + ATA_BMSTAT_PORT) | ATA_BMSTAT_DMA_MASTER); > + else > + outb(scp->bmaddr + ATA_BMSTAT_PORT, > + inb(scp->bmaddr + ATA_BMSTAT_PORT) | ATA_BMSTAT_DMA_SLAVE); > scp->mode[(device == ATA_MASTER) ? 0 : 1] = ATA_MODE_WDMA2; > return 0; > } > > -Sĝren > > 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 Thu Dec 16 4:31: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id C8A47155E0 for ; Thu, 16 Dec 1999 04:30:52 -0800 (PST) (envelope-from roberto@eurocontrol.fr) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.43.2]) by matrix.eurocontrol.fr (Postfix) with ESMTP id 63E7D2BB1 for ; Thu, 16 Dec 1999 13:30:48 +0100 (CET) (envelope-from roberto@caerdonn.eurocontrol.fr) Received: by caerdonn.eurocontrol.fr (Postfix, from userid 1193) id E71924E32; Thu, 16 Dec 1999 13:30:47 +0100 (CET) Date: Thu, 16 Dec 1999 13:30:47 +0100 From: Ollivier Robert To: FreeBSD Current Users' list Subject: HEADSUP: ntp4 to replace xntpd Message-ID: <19991216133047.A79776@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a HEADSUP message to warn all current users that tha following is being done: - disable xntpd build - enable ntp build - removal of old xntpd/xntpdc binaries as they've been renamed - modifications in /etc/defaults/rc.conf to take the new daemon into account. xntpd will be "cvs removed" in one week approx. -- Ollivier ROBERT -=- Eurocontrol EEC/TEC -=- Ollivier.Robert@eurocontrol.fr The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 5:11: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id C500A14E92 for ; Thu, 16 Dec 1999 05:11:01 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id HAA27498; Thu, 16 Dec 1999 07:10:46 -0600 (CST) (envelope-from dick) Date: Thu, 16 Dec 1999 07:10:46 -0600 From: "Richard Seaman, Jr." To: Soren Schmidt Cc: djb@Wit389306.student.utwente.nl, freebsd-current@FreeBSD.ORG Subject: Re: ATA driver problem?? (lost disk contact) Message-ID: <19991216071046.A91400@tar.com> References: <19991216091950.B8469@relativity.student.utwente.nl> <199912160825.JAA71207@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912160825.JAA71207@freebsd.dk>; from sos@freebsd.dk on Thu, Dec 16, 1999 at 09:25:11AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 09:25:11AM +0100, Soren Schmidt wrote: > It seems Dave J. Boers wrote: > > > > I am still having "disc contact lost messages" regularly too. I've been > > posting about them on several occasions some time ago. I haven't been able > > to pinn it down, however. IF they occur, they occur somewhere between 9:15 > > and 9:20 a.m. OR p.m. But they don't always. This used to be 10:15, but > > that changed _some weeks after_ the change of daylight saving time. I can't > > seem to relate it to anything. It is unlikely that it's a power glitch, > > because the system has been displaying the problem with two different > > UPS's. > > > > The machine is running current current's which are regularly updated. It's > > an ABIT BP6 and the disk causing problems is a WD 7200 RPM 18,2 Gb disk > > running UDMA33. It's the only IDE disk in the system; the other disks are > > all SCSI. The system is running 24/7. Other details were posted earlier. > > There is this thing with the IBM's doing some headcleaning stuff once > a day/week, but I've never seen any of my IBM's do that (I got plenty > of them). I'll try to get more info on that from IBM... I've been running the ata driver for about a week now. Yesterday, for the first time, I got the messages posted below, and now again this morning. Note the fallback to PIO. Also note that Dec 15 is exactly 1 week from the first time I ran with the ATA drivers, thought there have been several reboots in the interim. The times are CST (-600). The machine's time is synched using ntp. Dec 15 07:00:44 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting Dec 15 07:00:45 test /kernel: ata0: resetting devices .. done [snip] Dec 15 19:01:02 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting Dec 15 19:01:02 test /kernel: ata0: resetting devices .. done Dec 15 19:01:07 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting Dec 15 19:01:07 test /kernel: ata0: resetting devices .. done Dec 15 19:01:07 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting Dec 15 19:01:07 test /kernel: ata0: resetting devices .. done Dec 15 19:01:12 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting Dec 15 19:01:12 test /kernel: ata0: resetting devices .. done Dec 15 19:01:12 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting Dec 15 19:01:12 test /kernel: ata0: resetting devices .. done Dec 15 19:01:17 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting Dec 15 19:01:17 test /kernel: ata0-master: ad_timeout: trying fallback to PIO mode Dec 15 19:01:17 test /kernel: ata0: resetting devices .. done Dec 15 19:01:17 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting Dec 15 19:01:17 test /kernel: ata0: resetting devices .. done Dec 15 19:01:22 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting Dec 15 19:01:22 test /kernel: ata0: resetting devices .. done [snip] Dec 16 07:01:24 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting Dec 16 07:01:24 test /kernel: ata0: resetting devices .. done Dec 16 07:01:29 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting Dec 16 07:01:29 test /kernel: ata0: resetting devices .. done Dec 16 07:01:34 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting Dec 16 07:01:34 test /kernel: ata0: resetting devices .. done Dec 16 07:01:39 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting Dec 16 07:01:39 test /kernel: ata0: resetting devices .. done Setup: Dec 11 11:31:02 test /kernel: ata-pci0: irq 14 at device 0.1 on pci0 Dec 11 11:31:02 test /kernel: ata-pci0: Busmastering DMA supported Dec 11 11:31:02 test /kernel: ata0 at 0x01f0 irq 14 on ata-pci0 Dec 11 11:31:02 test /kernel: ata1 at 0x0170 irq 15 on ata-pci0 [snip] Dec 11 11:31:02 test /kernel: ata-isa0: already registered as ata0 Dec 11 11:31:02 test /kernel: ata-isa1: already registered as ata1 [snip] Dec 11 11:31:02 test /kernel: ad0: ATA-4 disk at ata0 as master Dec 11 11:31:02 test /kernel: ad0: 17206MB (35239680 sectors), 34960 cyls, 16 heads, 63 S/T, 512 B/S Dec 11 11:31:02 test /kernel: ad0: 16 secs/int, 32 depth queue, UDMA33 Dec 11 11:31:02 test /kernel: ad1: ATA-3 disk at ata0 as slave Dec 11 11:31:02 test /kernel: ad1: 4884MB (10003392 sectors), 9924 cyls, 16 heads, 63 S/T, 512 B/S Dec 11 11:31:02 test /kernel: ad1: 16 secs/int, 1 depth queue, DMA Dec 11 11:31:02 test /kernel: ad2: ATA-4 disk at ata1 as master Dec 11 11:31:02 test /kernel: ad2: 10991MB (22510656 sectors), 22332 cyls, 16 heads, 63 S/T, 512 B/S Dec 11 11:31:02 test /kernel: ad2: 16 secs/int, 1 depth queue, UDMA33 -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 5:53:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 3FB9914F28 for ; Thu, 16 Dec 1999 05:53:47 -0800 (PST) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 73FA51DEA; Thu, 16 Dec 1999 14:53:55 +0100 (CET) Date: Thu, 16 Dec 1999 14:53:55 +0100 From: "Dave J. Boers" To: "Richard Seaman, Jr." Cc: sos@freebsd.dk, freebsd-current@freebsd.org Subject: Re: ATA driver problem?? (lost disk contact) Message-ID: <19991216145355.A9566@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <19991216091950.B8469@relativity.student.utwente.nl> <199912160825.JAA71207@freebsd.dk> <19991216071046.A91400@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991216071046.A91400@tar.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 07:10:46AM -0600, Richard Seaman, Jr. wrote: > Dec 15 19:01:02 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting > Dec 15 19:01:02 test /kernel: ata0: resetting devices .. done > Dec 16 07:01:24 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting > Dec 16 07:01:24 test /kernel: ata0: resetting devices .. done ...and again there is almost precisely 12 hours in between... That's the same as I find time and again. I noticed that you are using IBM disks, whil my disk is a WD. The only common denominator seems to be the fact that we are both using -current with ATA drivers and that we are both running UDMA33. Regards, Dave Boers -- God, root, what's the difference? djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 6: 2:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8AC7714DD1 for ; Thu, 16 Dec 1999 06:02:32 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id PAA50199; Thu, 16 Dec 1999 15:02:24 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912161402.PAA50199@freebsd.dk> Subject: Re: ATA driver problem?? (lost disk contact) In-Reply-To: <19991216145355.A9566@relativity.student.utwente.nl> from "Dave J. Boers" at "Dec 16, 1999 02:53:55 pm" To: djb@Wit389306.student.utwente.nl Date: Thu, 16 Dec 1999 15:02:24 +0100 (CET) Cc: dick@tar.com (Richard Seaman Jr.), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Dave J. Boers wrote: > On Thu, Dec 16, 1999 at 07:10:46AM -0600, Richard Seaman, Jr. wrote: > > > Dec 15 19:01:02 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting > > Dec 15 19:01:02 test /kernel: ata0: resetting devices .. done > > > Dec 16 07:01:24 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting > > Dec 16 07:01:24 test /kernel: ata0: resetting devices .. done > > ...and again there is almost precisely 12 hours in between... > That's the same as I find time and again. > I noticed that you are using IBM disks, whil my disk is a WD. The only > common denominator seems to be the fact that we are both using -current > with ATA drivers and that we are both running UDMA33. Uhm, that wont be new WD drives, as they are exactly the same as IBM drives give or take the label :) -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 6:10:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 4581715451 for ; Thu, 16 Dec 1999 06:10:13 -0800 (PST) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 9B0DF1DEA; Thu, 16 Dec 1999 15:10:21 +0100 (CET) Date: Thu, 16 Dec 1999 15:10:21 +0100 From: "Dave J. Boers" To: Soren Schmidt Cc: freebsd-current@freebsd.org Subject: Re: ATA driver problem?? (lost disk contact) Message-ID: <19991216151021.A9649@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <19991216145355.A9566@relativity.student.utwente.nl> <199912161402.PAA50199@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199912161402.PAA50199@freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 03:02:24PM +0100, Soren Schmidt wrote: > Uhm, that wont be new WD drives, as they are exactly the same as > IBM drives give or take the label :) Huh? That I didn't know. So you're saying that WD and IBM 18 Gb disks are the same hardware? My disk: ad0: ATA-4 disk at ata0 as master ad0: 17206MB (35239680 sectors), 34960 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 32 depth queue, UDMA33 I would *love* to hear more about that. Can you point me to some info? Regards, Dave Boers. -- God, root, what's the difference? djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 6:16:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4709E14F04 for ; Thu, 16 Dec 1999 06:16:49 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id PAA53443; Thu, 16 Dec 1999 15:16:15 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912161416.PAA53443@freebsd.dk> Subject: Re: ATA driver problem?? (lost disk contact) In-Reply-To: <19991216151021.A9649@relativity.student.utwente.nl> from "Dave J. Boers" at "Dec 16, 1999 03:10:21 pm" To: djb@Wit389306.student.utwente.nl Date: Thu, 16 Dec 1999 15:16:15 +0100 (CET) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Dave J. Boers wrote: > On Thu, Dec 16, 1999 at 03:02:24PM +0100, Soren Schmidt wrote: > > Uhm, that wont be new WD drives, as they are exactly the same as > > IBM drives give or take the label :) > > Huh? That I didn't know. So you're saying that WD and IBM 18 Gb disks are > the same hardware? > > My disk: > > ad0: ATA-4 disk at ata0 as master > ad0: 17206MB (35239680 sectors), 34960 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 32 depth queue, UDMA33 > > I would *love* to hear more about that. Can you point me to some info? I read it somewhere that IBM & WD has joined forces on their newer disks, funny enough WD disks now looks exactly like IBM disks :) I think this only applies to WD's expert series, but that I'm not sure of. At least the 9G AC29100D I've got is physically identical to the IBM drives I've got. -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 6:40:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.194]) by hub.freebsd.org (Postfix) with ESMTP id E3DB315511 for ; Thu, 16 Dec 1999 06:40:34 -0800 (PST) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.9.3/8.7.3) id PAA41199; Thu, 16 Dec 1999 15:40:20 +0100 (MET) Date: Thu, 16 Dec 1999 15:40:20 +0100 From: Martin Cracauer To: Marcel Moolenaar Cc: Sheldon Hearn , current@FreeBSD.ORG Subject: Re: sh(1) broken caching [was: Re: Broken sh(1)?] Message-ID: <19991216154020.A41154@cons.org> References: <712.945183175@axl.noc.iafrica.com> <38565DEA.4487DF53@scc.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <38565DEA.4487DF53@scc.nl>; from Marcel Moolenaar on Tue, Dec 14, 1999 at 04:10:34PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You can also fool sh into running the *wrong* binary if if you have two in showdowed paths: #! /bin/sh test -d foo1 || mkdir foo1 test -d foo2 || mkdir foo2 test -d foo2 || mkdir foo3 echo 'echo :one' > foo1/run echo 'echo :two' > foo2/run echo 'echo :three' > foo2/run3 chmod a+x */run* hash -r echo echo Expect one: PATH=./foo3:./foo1:./foo2:./foo5 echo Expect two: PATH=./foo3:./foo3:./foo1 run echo run should be in in foo1: hash -v echo $PATH echo Should give one: run ==> runs foo2/run, not foo1/run. This is still covered by the quick fix I sent. Looking for cases that aren't... Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 7:33:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9EAE714D7F for ; Thu, 16 Dec 1999 07:33:11 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id KAA25355; Thu, 16 Dec 1999 10:33:10 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id KAA00557; Thu, 16 Dec 1999 10:32:39 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 16 Dec 1999 10:32:38 -0500 (EST) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-Reply-To: <199912160600.WAA47882@apollo.backplane.com> References: <14423.46117.353932.473968@grasshopper.cs.duke.edu> <199912160600.WAA47882@apollo.backplane.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14425.1514.261894.79461@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > > And so Andrews bug report comes into the light! His poor client > (and mine once I reproduced the bug) got into a state, due to the > server returning a different version id for virtually every packet, > where it resent the same write data over the network over and over > and over and over and over again. Very nice catch! Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 7:53: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 3C51114E08 for ; Thu, 16 Dec 1999 07:53:04 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 91300137F83 for ; Thu, 16 Dec 1999 10:52:59 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id KAA03946; Thu, 16 Dec 1999 10:52:59 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14425.2778.943367.365945@trooper.velocet.net> Date: Thu, 16 Dec 1999 10:52:58 -0500 (EST) To: freebsd-current@freebsd.org Subject: AMI MegaRAID datapoint. X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have the Enterprise 1400 Megaraid adapter with (currently 16M) on it. I have tested the various modes of operation (different raid levels and striping) and find it to be working well. My LVD array consists of 8 18G Quamtum IV's. Now... using vinum and either the 2940U2W (Adaptec LVD) or the TekRAM (NCR) LVD (using the sym0 device) gives 30 to 35 M/s under RAID-5. This is impressive and subject to the bug that I mentioned in -STABLE which still hasn't been found. The AMI MegaRAID 1400 delivers between 16.5 and 19 M/s (the 19M/s value is somewhat contrived --- using 8 bonnies in parrallel and then summing their results --- which is not 100% valid)... but the MegaRAID appears to be stable. I would like to know, however, if there are any planned or in-the-works utility programs for the amr device. In particular, a program to print the state of the array would be useful. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 8:37: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 8464114CC9 for ; Thu, 16 Dec 1999 08:36:54 -0800 (PST) (envelope-from brad@shub-internet.org) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id RAA27216; Thu, 16 Dec 1999 17:36:45 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <14425.2778.943367.365945@trooper.velocet.net> References: <14425.2778.943367.365945@trooper.velocet.net> Date: Thu, 16 Dec 1999 17:35:28 +0100 To: David Gilbert , freebsd-current@FreeBSD.ORG From: Brad Knowles Subject: Re: AMI MegaRAID datapoint. Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:52 AM -0500 1999/12/16, David Gilbert wrote: > Now... using vinum and either the 2940U2W (Adaptec LVD) or the TekRAM > (NCR) LVD (using the sym0 device) gives 30 to 35 M/s under RAID-5. That's really interesting, because there are at least two or three outstanding bugs in the vinum RAID-5 implementation that have prevented me from successfully benchmarking it (see ). Have you been using rawio? Have you made any attempt to try duplicating some of the sorts of benchmarks I've done, available at ? > This is impressive and subject to the bug that I mentioned in -STABLE > which still hasn't been found. Which one is this? > The AMI MegaRAID 1400 delivers between 16.5 and 19 M/s (the 19M/s > value is somewhat contrived --- using 8 bonnies in parrallel and then > summing their results --- which is not 100% valid)... but the MegaRAID > appears to be stable. If you look at the page I mentioned, you'll see that my best sustained speed with a vinum 4-way stripe on IBM 10kRPM 9LZX drives attached to an Adaptec 2940UW controller was about 19MB/s sequential read (anywhere from four to 128 processes), 16.5MB/s random read (64-256 processes), 14MB/s sequential write (16 processes), and 15MB/s random write (64-256 processes). My best performance with a DPT SmartRAID IV in a 4-way stripe with the same disks was 16.5MB/s sequential read (4 processes), 7.5MB/s random read (pretty much regardless of how many processes), 17MB/s sequential write (256 processes), and 6MB/s (independent of the number of processes). I did not attempt to benchmark DPT SmartRAID IV performance under RAID-5. I'd be very interested to see more extensive benchmarking of this configuration. In addition to my page above, I'd recommend you look at and , and see which of these you can throw at your system. With luck, in about a month or so, I should be getting a new server in with 1GB RAM, 450Mhz Pentium III w/ 1MB L2 cache, a DPT SmartRAID V controller with 256MB ECC cache, and eight Fujitsu MAE3182LC 7200RPM 18GB drives for RAID-5 configuration on a single SCSI bus, for our new anonymous ftp server. I know this isn't an ideal configuration (I shouldn't have more than four devices on a SCSI bus, and I should be using faster drives with lower latency), but it will be very interesting to test out this configuration with 3.4-RELEASE and what should hopefully be stable DPT SmartRAID V/VI drivers by then. I plan on beating the crap out of this machine before it goes online. ;-) -- Brad Knowles Your mouse has moved. Windows NT must be restarted for the change to take effect. Reboot now? [ OK ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 8:48:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 6651E14FE2 for ; Thu, 16 Dec 1999 08:48:44 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 3BF84137FB9; Thu, 16 Dec 1999 11:48:39 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id LAA05572; Thu, 16 Dec 1999 11:48:39 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14425.6118.899093.621159@trooper.velocet.net> Date: Thu, 16 Dec 1999 11:48:38 -0500 (EST) To: Brad Knowles Cc: David Gilbert , freebsd-current@FreeBSD.ORG Subject: Re: AMI MegaRAID datapoint. In-Reply-To: References: <14425.2778.943367.365945@trooper.velocet.net> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Brad" == Brad Knowles writes: >> This is impressive and subject to the bug that I mentioned in >> -STABLE which still hasn't been found. Brad> Which one is this? It's a really long thread. I'm not going to repeat it here. Basically, under "enough" load, vinum trashes the kernel stack in such a way that debugging is very tough. I have been talking to a number of people about it in -STABLE. I will continue to debug this on the new news server I'm building (before it gets commissioned), but work on this particular server had to halt with the instalation of the MegaRAID. Brad> With luck, in about a month or so, I should be getting a new Brad> server in with 1GB RAM, 450Mhz Pentium III w/ 1MB L2 cache, a Brad> DPT SmartRAID V controller with 256MB ECC cache, and eight Brad> Fujitsu MAE3182LC 7200RPM 18GB drives for RAID-5 configuration Brad> on a single SCSI bus, for our new anonymous ftp server. I got the MegaRAID 1400 because the DPT V drivers weren't available. The MegaRAID should be roughly equivlanet to the DPT V. Do go with LVD if you can. I have done benchmarking with bonnie instead of rawIO. The output is as follows: 1 process, for vinum: -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU raid-1 512 4554 20.0 4583 6.3 4495 8.3 18596 80.1 30001 25.9 446.0 5.3 1 process, for MegaRAID: -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU mega 512 7419 32.4 7529 10.2 4653 9.6 14616 63.4 14942 18.8 345.4 5.0 ... now the MegaRAID was at 16.5M/s block read with a different stripe size, but I don't have that output in front of me. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 9:18:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0CF5D14DDC for ; Thu, 16 Dec 1999 09:18:34 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id JAA29076 for ; Thu, 16 Dec 1999 09:18:33 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id JAA74195 for current@FreeBSD.ORG; Thu, 16 Dec 1999 09:18:33 -0800 (PST) (envelope-from obrien) Date: Thu, 16 Dec 1999 09:18:33 -0800 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: sh(1) broken caching [was: Re: Broken sh(1)?] Message-ID: <19991216091832.A74110@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <712.945183175@axl.noc.iafrica.com> <38565DEA.4487DF53@scc.nl> <19991216154020.A41154@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991216154020.A41154@cons.org>; from cracauer@cons.org on Thu, Dec 16, 1999 at 03:40:20PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 03:40:20PM +0100, Martin Cracauer wrote: > You can also fool sh into running the *wrong* binary if if you have > two in showdowed paths: pdksh does not suffer from either this problem or the problem that started this thread (and does not coredump). We've shown in the past that pdksh is actually smaller (when linked statically) than ash. I still think we should *seriously* consider switching to pdksh. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 9:19:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 69B6914DC2 for ; Thu, 16 Dec 1999 09:19:08 -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.9.3/8.9.3) with SMTP id KAA06289; Thu, 16 Dec 1999 10:18:50 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA19547; Thu, 16 Dec 1999 10:18:48 -0700 Date: Thu, 16 Dec 1999 10:18:48 -0700 Message-Id: <199912161718.KAA19547@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Poul-Henning Kamp Cc: Kevin Day , dillon@apollo.backplane.com (Matthew Dillon), gallatin@cs.duke.edu (Andrew Gallatin), freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-Reply-To: <14779.945334147@critter.freebsd.dk> References: <199912160758.BAA87332@celery.dragondata.com> <14779.945334147@critter.freebsd.dk> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199912160758.BAA87332@celery.dragondata.com>, Kevin Day writes: > > >Ack, I was using this very same thing for several devices in an isolated > >peer-to-peer network to decide who the 'master' was. (Whoever had been up > >longest knew more about the state of the network) Having this change could > >cause weirdness for me too... I assumed (without checking *thwap*) that > >boottime was a constant. > > > >Perhaps a 'real_boottime' or 'unadjusted_boottime' that gets copied after > >'boottime' gets initialized so that others can use it, not just NFS? :) > > no, I think that is a bad idea. In your case you want to use the > "uptime" which *is* a measure of how long the system has been > running. Uptime is also a constantly changing number. Forgive me for my ignorance, but why does bootime constantly change? I would have thought it would be a constant? I've got software that also uses this to determine when a new copy of it exists (although I do keep a local cache of the value in case my software crashes, since it can recover from a crash, but not a reboot). I would think that boottime would be constant, since you didn't keep booting at a different time... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 9:30:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from dead-end.net (dead-end.net [216.15.131.2]) by hub.freebsd.org (Postfix) with ESMTP id 396C7150D2 for ; Thu, 16 Dec 1999 09:30:38 -0800 (PST) (envelope-from rock@dead-end.net) Received: (from nopriv@localhost) by dead-end.net (8.9.3/DEAD-END/1999102300-Deliver) id SAA42830; Thu, 16 Dec 1999 18:30:35 +0100 (CET) (envelope-from rock@dead-end.net) Date: Thu, 16 Dec 1999 18:30:35 +0100 (CET) From: "D. Rock" Message-Id: <199912161730.SAA42830@dead-end.net> X-Authentication-Warning: dead-end.net: nopriv set sender to rock@dead-end.net using -f To: current@FreeBSD.org Reply-To: rock@dead-end.net MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="-MOQ94536543503c0bde80a2899ef775e4a06f9ea0ab1" User-Agent: IMP/PHP3 Imap webMail Program 2.0.11 Subject: More on problems with new pnp code Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. ---MOQ94536543503c0bde80a2899ef775e4a06f9ea0ab1 Content-Type: text/plain Content-Transfer-Encoding: 8bit Hi, yesterday I reported a bug in the resource allocator for PnP ISA devices: The align-field is ignored for IO port resources, e.g. device A wants io range 0x100-0x3ff, size=0x1, align=0x1 device B wants io range 0x100-0x3f7, size=0x8, align=0x8 device A gets assigned first and will receive at port 0x100 on isa0 device B will then receive at port 0x101-0x108 I have somewhat debug the code and found out that the loop in isa_find_port() [/sys/isa/isa_common.c] is totally useless. The first call to bus_alloc_resource() there will succeed, because the major work of resource allocation (including searching for an alternate region) will be done in rman_reserve_resource() [/sys/kern/subr_rman.c], which doesn\'t know of any alignment constraints. I haven\'t tested it, but shouldn\'t the code in isa_find_port() be something like below? I will test it tonight, though. Daniel ---MOQ94536543503c0bde80a2899ef775e4a06f9ea0ab1 Content-Type: text/plain; name="isa.diff" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="isa.diff" --- isa_common.c.orig Thu Dec 16 18:27:23 1999 +++ isa_common.c Thu Dec 16 18:27:25 1999 @@ -205,7 +205,8 @@ start, size); res[i] = bus_alloc_resource(child, SYS_RES_IOPORT, &i, - 0, ~0, 1, RF_ACTIVE); + start, start + size - 1, + 1, RF_ACTIVE); if (res[i]) { result->ic_port[i].ir_start = start; result->ic_port[i].ir_end = start + size - 1; ---MOQ94536543503c0bde80a2899ef775e4a06f9ea0ab1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 9:32: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 5034E14F5F for ; Thu, 16 Dec 1999 09:31:56 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id C526E1CC6; Fri, 17 Dec 1999 01:31:53 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: nate@mt.sri.com (Nate Williams) Cc: Poul-Henning Kamp , Kevin Day , dillon@apollo.backplane.com (Matthew Dillon), gallatin@cs.duke.edu (Andrew Gallatin), freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-Reply-To: Message from Nate Williams of "Thu, 16 Dec 1999 10:18:48 MST." <199912161718.KAA19547@mt.sri.com> Date: Fri, 17 Dec 1999 01:31:53 +0800 From: Peter Wemm Message-Id: <19991216173153.C526E1CC6@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams wrote: > > In message <199912160758.BAA87332@celery.dragondata.com>, Kevin Day writes: > > > > >Ack, I was using this very same thing for several devices in an isolated > > >peer-to-peer network to decide who the 'master' was. (Whoever had been up > > >longest knew more about the state of the network) Having this change could > > >cause weirdness for me too... I assumed (without checking *thwap*) that > > >boottime was a constant. > > > > > >Perhaps a 'real_boottime' or 'unadjusted_boottime' that gets copied after > > >'boottime' gets initialized so that others can use it, not just NFS? :) > > > > no, I think that is a bad idea. In your case you want to use the > > "uptime" which *is* a measure of how long the system has been > > running. > > Uptime is also a constantly changing number. Forgive me for my > ignorance, but why does bootime constantly change? I would have thought > it would be a constant? I've got software that also uses this to > determine when a new copy of it exists (although I do keep a local cache > of the value in case my software crashes, since it can recover from a > crash, but not a reboot). > > I would think that boottime would be constant, since you didn't keep > booting at a different time... Uptime is a monotonically increasing time starting at zero. Whenever the time-of-day adjusts to add or remove time, rather than changing the "uptime", we change the "origin" of timeofday and boottime. This means that we don't have to walk the entire process list and intercept all the timers and adjust them for the changing number of ticks in uptime etc. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 9:33:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 87A2E14ECB for ; Thu, 16 Dec 1999 09:33:17 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id JAA26368; Thu, 16 Dec 1999 09:34:50 -0800 Date: Thu, 16 Dec 1999 09:34:50 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Ollivier Robert Cc: "FreeBSD Current Users' list" Subject: Re: HEADSUP: ntp4 to replace xntpd In-Reply-To: <19991216133047.A79776@caerdonn.eurocontrol.fr> 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 Huh? What about the impact on all ntp.conf files? Or is this seamless? On Thu, 16 Dec 1999, Ollivier Robert wrote: > This is a HEADSUP message to warn all current users that tha following is > being done: > > - disable xntpd build > - enable ntp build > - removal of old xntpd/xntpdc binaries as they've been renamed > - modifications in /etc/defaults/rc.conf to take the new daemon into > account. > > xntpd will be "cvs removed" in one week approx. > -- > Ollivier ROBERT -=- Eurocontrol EEC/TEC -=- Ollivier.Robert@eurocontrol.fr > The Postman hits! The Postman hits! You have new mail. > > > 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 Thu Dec 16 9:33:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 7475514DC7 for ; Thu, 16 Dec 1999 09:33:13 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA16724; Thu, 16 Dec 1999 18:32:44 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: nate@mt.sri.com (Nate Williams) Cc: Kevin Day , dillon@apollo.backplane.com (Matthew Dillon), gallatin@cs.duke.edu (Andrew Gallatin), freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-reply-to: Your message of "Thu, 16 Dec 1999 10:18:48 MST." <199912161718.KAA19547@mt.sri.com> Date: Thu, 16 Dec 1999 18:32:44 +0100 Message-ID: <16722.945365564@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912161718.KAA19547@mt.sri.com>, Nate Williams writes: >> In message <199912160758.BAA87332@celery.dragondata.com>, Kevin Day writes: >> >> >Ack, I was using this very same thing for several devices in an isolated >> >peer-to-peer network to decide who the 'master' was. (Whoever had been up >> >longest knew more about the state of the network) Having this change could >> >cause weirdness for me too... I assumed (without checking *thwap*) that >> >boottime was a constant. >> > >> >Perhaps a 'real_boottime' or 'unadjusted_boottime' that gets copied after >> >'boottime' gets initialized so that others can use it, not just NFS? :) >> >> no, I think that is a bad idea. In your case you want to use the >> "uptime" which *is* a measure of how long the system has been >> running. > >Uptime is also a constantly changing number. Forgive me for my >ignorance, but why does bootime constantly change? I would have thought >it would be a constant? I've got software that also uses this to >determine when a new copy of it exists (although I do keep a local cache >of the value in case my software crashes, since it can recover from a >crash, but not a reboot). > >I would think that boottime would be constant, since you didn't keep >booting at a different time... Well, our timekeeping is done my having two estimates: The amount of time on the UTC timescale since we booted and the time we did so in UTC. If people do a "settimeofday" we change the boot time since the amount of time we've been up *IS* known for sure, whereas the boottime is only an estimate. The ntp pll adjusts the frequency of our clock, since that is a frequency adjustment. The sticky but is the gross "adjtime" call. Since the primary user of this is the timed daemon, which issues phase adjustments, not frequency adjustments, it fiddles boottime, but still using the "slowly converge" method so we don't step the clock more than we need to. The reason why xntpd used tickadj was that enabling the kernel pll for xntpd was rather obscure and people never did. This problem is now gone with NTPv4 (Thanks Roberto!) So after today, the problem is gone, unless you use timed/tickadj or other broken clock synchronizers. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 9:36: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from modemcable156.106-200-24.mtl.mc.videotron.net (modemcable126.102-200-24.mtl.mc.videotron.net [24.200.102.126]) by hub.freebsd.org (Postfix) with SMTP id CFC4415645 for ; Thu, 16 Dec 1999 09:36:00 -0800 (PST) (envelope-from patrick@mindstep.com) Received: (qmail 52776 invoked from network); 16 Dec 1999 17:35:56 -0000 Received: from patrak.local.mindstep.com (HELO patrak) (192.168.10.4) by jacuzzi.local.mindstep.com with SMTP; 16 Dec 1999 17:35:56 -0000 Message-ID: <00c501bf47ec$01fee840$040aa8c0@local.mindstep.com> From: "Patrick Bihan-Faou" To: Cc: Subject: Status of the netatalk stack Date: Thu, 16 Dec 1999 12:35:55 -0500 Organization: MindStep Corporation 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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was looking at the netatalk package and the appletalk support in the kernel source code and I realized that they are based on the same code originally (the code from netatalk). The kernel code however is quite out of date from what can be found in the netatalk-asun package. I was wondering if anybody is planning on integrating the latest changes ? If not is it something that I should undertake ? Are there any major reasons why the code in freebsd should be left alone ? PS. I cross-posted in current and stable because it affects both stream in the same way, however I guess the discussion should be kept in "current", so please try to reply to the correct address. Thanks. Patrick. -- www.mindstep.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 9:36:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A1E4C14E55 for ; Thu, 16 Dec 1999 09:36:14 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id JAA26402 for ; Thu, 16 Dec 1999 09:37:59 -0800 Date: Thu, 16 Dec 1999 09:37:59 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: Re: Linux vs. OpenBSD vs. FreeBSD vs. NetBSD (fwd) 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 fyi ---------- Forwarded message ---------- Date: Thu, 16 Dec 1999 12:15:48 -0500 (EST) From: Paul B. Brown Reply-To: axp-list@redhat.com To: axp-list@redhat.com Subject: Re: Linux vs. OpenBSD vs. FreeBSD vs. NetBSD Resent-Date: 16 Dec 1999 17:15:54 -0000 Resent-From: axp-list@redhat.com Resent-cc: recipient list not shown: ; > Is there a handy collection of arguments over which OS is better? Hummmm . . . . this is a much debated topic. In a nutshell: Linux: 1. More prevalent 2. More support 3. More software ported 4. Multi-platform: Intel, Alpha, Sparc, Mac, PowerPC, etc. 5. GPLed Even though I think Linux needs further tweaking to become as high stress as FreeBSD, I still believe it is the best bang for the buck. There is more interest in this OS than any of the other "free" OSes. This is a plus and a minus. The plus is that it will continue to advance as an OS and a production platform. The minus is that now business needs may begin to drive Linux and that will skew the original intent of Linux and it's reason for being as good as it is. I've been talking to some Systems Operations boys at NASA HQ in Washington, DC who have done (and continue to do) testing on the "free" OSes as stable platforms for research and production at NASA. They found that even now, FreeBSD or OpenBSD are their choice either because of stability or speed. I found that interesting given some of the claims I've seem on this list, and others, that Linux is now as stable and high performance as FreeBSD on Intel. The NASA boys don't think so. FreeBSD: 1. Higher performance especially in the network stack. 2. Can run any Linux application using emulator. 3. BSDL 4. Intel Only: This means the OS is tweaked for max performance. This is a very stable, very robust, high stress-capable OS for Intel platforms only. If you want to get the max out of your production Intel platform, use FreeBSD. Yahoo does. The choice at NASA HQ. NetBSD: 1. Runs on a lot of old hardware: PDP, VAX, 3B2, etc. 2. Very stable. 3. BSDL. This one is used if you have some old hardware lying around and want to get it functional again. This is great for older companies, Universities, and research facilities. OpenBSD: 1. Runs on a lot of old hardware: PDP, VAX, 3B2, etc. 2. More secure out of the box than any other xBSD. 3. Offshoot of NetBSD. 4. Very stable. 5. BSDL. The same as NetBSD except it's security features are it's main selling point. There is my $0.02 worth. :-) Paul --------------------------------------------------------------------------- Paul B. Brown pbrown@btechnet.com President Brown Technologies Network, Inc. http://www.btechnet.com/ Systems and Applications Design, Development, Deployment, and Maintenance --------------------------------------------------------------------------- -- To unsubscribe: send e-mail to axp-list-request@redhat.com with 'unsubscribe' as the subject. Do not send it to axp-list@redhat.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 9:51:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 4427515451 for ; Thu, 16 Dec 1999 09:51:40 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA16820; Thu, 16 Dec 1999 18:51:27 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: Ollivier Robert , "FreeBSD Current Users' list" Subject: Re: HEADSUP: ntp4 to replace xntpd In-reply-to: Your message of "Thu, 16 Dec 1999 09:34:50 PST." Date: Thu, 16 Dec 1999 18:51:27 +0100 Message-ID: <16818.945366687@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: > >Huh? What about the impact on all ntp.conf files? Or is this seamless? I was just about to start to compose an email with some info on this one when you email arrived. /etc/ntp.conf is the same unless you have a refclock. If you have a refclock you need to revisit your setup. About NTPv4 in general I can say that a lot of things have changed under the hood. Between the two of us Dave Mills and I have managed to get the "nanokernel" to act sensibly in the domain inside +/- 1usec which the old one didn't. (See http://gps.freebsd.dk for what kind of performance this can result in, given appropriate hardware). A lot of changes in the "control" code in ntpd has also changed, and as far as I can tell for the better all around. There is support for *very* long poll intervals (18hours I belive a lot cheaper if you sync by dialup) and burst mode which is more suitable for dial-on-demand kind of lines. There is a new API for PPS kind of signals (I'm also partly guilty here, but I must admit that I think the result is far too rococco for my taste). One thing which is new, is the initial synchronization: it can look broken, but it isn't. You will likely see something like this: 1. Ntpd starts 2. Home in on some server, steps the clock to zero offset. in the process we loose sync again. 3. Catch sync again. Very light and slow adaptation of frequency the clock slowly drifts off to +/- 128msec. 4. Clock is steped again and frequency set to slope of the drift from step 3. 5. Business as usual. Depending on your clock step three can take hours to complete, the better your clock the longer it takes. Dave Mills old rule of thumb applies even more than before: Only tweak your ntp.conf right before lunch. That gives it 24hours to settle before you fiddle it again. You can find much more about NTPv4 on www.ntp.org -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 9:53:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E9EC114E7B for ; Thu, 16 Dec 1999 09:53:26 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id JAA26507; Thu, 16 Dec 1999 09:55:02 -0800 Date: Thu, 16 Dec 1999 09:55:02 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: Ollivier Robert , "FreeBSD Current Users' list" Subject: Re: HEADSUP: ntp4 to replace xntpd In-Reply-To: <16818.945366687@critter.freebsd.dk> 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 Thanks for the very clear writeup of what we can expect. I'm happy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 9:53:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from boromir.vpop.net (dns1.vpop.net [206.117.147.2]) by hub.freebsd.org (Postfix) with ESMTP id 64DDC14EEB for ; Thu, 16 Dec 1999 09:53:27 -0800 (PST) (envelope-from mreimer@vpop.net) Received: from vpop.net (bilbo.vpop.net [216.160.82.65]) by boromir.vpop.net (8.9.1/8.9.1) with ESMTP id JAA07176; Thu, 16 Dec 1999 09:53:25 -0800 (PST) Message-ID: <38592725.34AAE2E3@vpop.net> Date: Thu, 16 Dec 1999 09:53:41 -0800 From: Matthew Reimer Organization: VPOP Technologies, Inc. X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon , freebsd-current@freebsd.org Subject: Re: Serious server-side NFS problem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt, you are a tenacious, fearsome bug hunter! Matt Matthew Dillon wrote: > > Here's a general update on this bug report to -current. It took all day > but I was finally able to reproduce Andrew's bug. > > You guys are going to *love* this. > > NFS uses the kernel 'boottime' structure to generate its version id. > Now normally you might believe that this structure, once set, will > never change. The authors of NFS certainly make that assumption! > > No such luck. If you happen to be running, oh, xntpd for example, > the kernel adjusts the boottime structure to take into account time > changes, including PLL changes so, in fact, the boottime structure > can change quite often - once each tick, in fact. > > Now, the effect of boottime changing on NFS is rather drastic. You > see, the version id controls whether NFS clients must reset their > state machines for NFS data writes. If a client has done a stage 1 > write and is ready to do the stage 2 commit, and the version id > changes, the client must revert back to stage 1. > > And so Andrews bug report comes into the light! His poor client > (and mine once I reproduced the bug) got into a state, due to the > server returning a different version id for virtually every packet, > where it resent the same write data over the network over and over > and over and over and over again. > > I think recent changes to the way the kernel clocks work in -current > brought the bug out into the open, but it's definitely a problem in > both -stable and -current. > > Doh! I gotta say that if I hadn't happened to have been running xntpd > on my test box I would have *never* figured it out. > > -Matt > > 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 Thu Dec 16 10: 1:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtprch1.nortel.com (smtprch1.nortelnetworks.com [192.135.215.14]) by hub.freebsd.org (Postfix) with ESMTP id 880F215657 for ; Thu, 16 Dec 1999 10:01:06 -0800 (PST) (envelope-from atrens@nortelnetworks.com) Received: from zmers013 by smtprch1.nortel.com; Thu, 16 Dec 1999 10:45:23 -0600 Received: from hcarp00g.ca.nortel.com by zmers013; Thu, 16 Dec 1999 11:45:07 -0500 Received: from hcarp00g.ca.nortel.com (hcarp00g.ca.nortel.com [47.196.31.114]) by hcarp00g.ca.nortel.com (8.9.3/8.7.3) with ESMTP id LAA08502 for ; Thu, 16 Dec 1999 11:52:43 -0500 (EST) Date: Thu, 16 Dec 1999 11:52:43 -0500 (EST) From: "Andrew Atrens" X-Sender: atrens@hcarp00g.ca.nortel.com Reply-To: "Andrew Atrens" To: current@freebsd.org Subject: framemaker for linux 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 All, This might be a linux ABI question, or it might be an `ld.so' question, so arguably I could have sent this to emulation, questions or since I run -current, current, or perhaps hackers, at any rate here goes - I've got `framemaker for linux' and am getting - # maker5X.exe maker5X.exe: error in loading shared libraries : undefined symbol: __register_frame_info # nm -A *.exe *.so | grep __register_frame_info maker5X.exe: U __register_frame_info libjpeg.so:0001fb50 T __register_frame_info libjpeg.so:0001fbd0 T __register_frame_info_table libpbm.so:00004d40 T __register_frame_info libpbm.so:00004dc0 T __register_frame_info_table libpgm.so:00001b40 T __register_frame_info libpgm.so:00001bc0 T __register_frame_info_table libpng.so:00018f40 T __register_frame_info libpng.so:00018fc0 T __register_frame_info_table libpnm.so:00003b30 T __register_frame_info libpnm.so:00003bb0 T __register_frame_info_table libppm.so:00005290 T __register_frame_info libppm.so:00005310 T __register_frame_info_table libz.so:0000c140 T __register_frame_info libz.so:0000c1c0 T __register_frame_info_table I've done the brandelf thing, and the LD_LIBRARY_PATH thing, and even tried LD_IGNORE_MISSING_OBJECTS to no avail. Here's what truss says - # truss ./maker5X.exe syscall linux_brk(0x0) returns 141787136 (0x8738000) syscall linux_open("/etc/ld.so.preload",0,05033211710) returns 3 (0x3) syscall linux_newfstat(3,0xbfbff2e4) returns 0 (0x0) syscall linux_mmap(0xbfbff320) returns 678195200 (0x286c7000) syscall close(3) returns 0 (0x0) syscall munmap(0x286c7000,0x0) returns 0 (0x0) syscall linux_open("./libm.so.6",0,015133027456) errno -2 'No such file or directory' syscall linux_open("/etc/ld.so.cache",0,05033211710) returns 3 (0x3) syscall linux_newfstat(3,0xbfbff1e4) returns 0 (0x0) syscall linux_mmap(0xbfbff220) returns 678240256 (0x286d2000) syscall close(3) returns 0 (0x0) syscall linux_open("/lib/libm.so.6",0,05033211710) returns 3 (0x3) syscall linux_mmap(0xbfbff22c) returns 678252544 (0x286d5000) syscall munmap(0x286d5000,0x1000) returns 0 (0x0) syscall linux_mmap(0xbfbff1d8) returns 678252544 (0x286d5000) syscall mprotect(0x286ed000,0x6e0,0x0) returns 0 (0x0) syscall linux_mmap(0xbfbff1d8) returns 678350848 (0x286ed000) syscall close(3) returns 0 (0x0) syscall linux_open("./libc.so.6",0,015133027456) errno -2 'No such file or directory' syscall linux_open("/lib/libc.so.6",0,05033211710) returns 3 (0x3) syscall linux_mmap(0xbfbff21c) returns 678354944 (0x286ee000) syscall munmap(0x286ee000,0x1000) returns 0 (0x0) syscall linux_mmap(0xbfbff1c8) returns 678354944 (0x286ee000) syscall mprotect(0x2877f000,0x133c8,0x0) returns 0 (0x0) syscall linux_mmap(0xbfbff1c8) returns 678948864 (0x2877f000) syscall linux_mmap(0xbfbff1c8) returns 678981632 (0x28787000) syscall close(3) returns 0 (0x0) syscall linux_open("./libdl.so.2",0,015133027456) errno -2 'No such file or directory' syscall linux_open("/lib/libdl.so.2",0,05033211710) returns 3 (0x3) syscall linux_mmap(0xbfbff20c) returns 679030784 (0x28793000) syscall munmap(0x28793000,0x1000) returns 0 (0x0) syscall linux_mmap(0xbfbff1b8) returns 679030784 (0x28793000) syscall mprotect(0x28795000,0x428,0x0) returns 0 (0x0) syscall linux_mmap(0xbfbff1b8) returns 679038976 (0x28795000) syscall close(3) returns 0 (0x0) syscall munmap(0x286d2000,0x235b) returns 0 (0x0) syscall linux_personality(0x0) returns 0 (0x0) syscall getpid() returns 8490 (0x212a) ./maker5X.exesyscall write(2,0xbfbff71c,13) returns 13 (0xd) : error in loading shared libraries syscall write(2,0x286cf1c8,36) returns 36 (0x24) syscall write(2,0x286ce9d4,0) returns 0 (0x0) : syscall write(2,0x286cf1c2,2) returns 2 (0x2) undefined symbol: __register_frame_infosyscall write(2,0xbfbff518,39) returns 39 (0x27) syscall write(2,0x286cf1c7,0) returns 0 (0x0) syscall write(2,0x286cf1c7,0) returns 0 (0x0) syscall write(2,0x286cf1c5,1) returns 1 (0x1) syscall exit(0x7f) process exit, rval = 32512 I'm probably missing something obvious. Any help y'all can provide would be greatly appreciated! Cheers, Andrew. -- +-- | Andrew Atrens Nortel Networks, Ottawa, Canada. | | All opinions expressed are my own, not those of any employer. | --+ Heller's Law: The first myth of management is that it exists. Johnson's Corollary: Nobody really knows what is going on anywhere within the organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 10:11: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 3FCC515110 for ; Thu, 16 Dec 1999 10:11:06 -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.9.3/8.9.3) with SMTP id LAA06817; Thu, 16 Dec 1999 11:10:46 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA19919; Thu, 16 Dec 1999 11:10:45 -0700 Date: Thu, 16 Dec 1999 11:10:45 -0700 Message-Id: <199912161810.LAA19919@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Poul-Henning Kamp Cc: mjacob@feral.com, Ollivier Robert , "FreeBSD Current Users' list" Subject: Re: HEADSUP: ntp4 to replace xntpd In-Reply-To: <16818.945366687@critter.freebsd.dk> References: <16818.945366687@critter.freebsd.dk> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Between the two of us Dave Mills and I have managed to get the > "nanokernel" to act sensibly in the domain inside +/- 1usec which > the old one didn't. (See http://gps.freebsd.dk for what kind of > performance this can result in, given appropriate hardware). You may not know the answer to this, but it's worth a shot. Wht kind of accuracy can we expect using 'cheap' off-the-shelf GPS receivers? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 10:12:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id 9614914D2A for ; Thu, 16 Dec 1999 10:12:42 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id MAA33594; Thu, 16 Dec 1999 12:14:54 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <199912161814.MAA33594@celery.dragondata.com> Subject: Re: Serious server-side NFS problem To: nate@mt.sri.com Date: Thu, 16 Dec 1999 12:14:54 -0600 (CST) Cc: phk@critter.freebsd.dk (Poul-Henning Kamp), toasty@dragondata.com (Kevin Day), dillon@apollo.backplane.com (Matthew Dillon), gallatin@cs.duke.edu (Andrew Gallatin), freebsd-current@FreeBSD.ORG In-Reply-To: <199912161718.KAA19547@mt.sri.com> from "Nate Williams" at Dec 16, 1999 10:18:48 AM X-Mailer: ELM [version 2.5 PL1] 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 > > > In message <199912160758.BAA87332@celery.dragondata.com>, Kevin Day writes: > > > > >Ack, I was using this very same thing for several devices in an isolated > > >peer-to-peer network to decide who the 'master' was. (Whoever had been up > > >longest knew more about the state of the network) Having this change could > > >cause weirdness for me too... I assumed (without checking *thwap*) that > > >boottime was a constant. > > > > > >Perhaps a 'real_boottime' or 'unadjusted_boottime' that gets copied after > > >'boottime' gets initialized so that others can use it, not just NFS? :) > > > > no, I think that is a bad idea. In your case you want to use the > > "uptime" which *is* a measure of how long the system has been > > running. > > Uptime is also a constantly changing number. Forgive me for my > ignorance, but why does bootime constantly change? I would have thought > it would be a constant? I've got software that also uses this to > determine when a new copy of it exists (although I do keep a local cache > of the value in case my software crashes, since it can recover from a > crash, but not a reboot). > > I would think that boottime would be constant, since you didn't keep > booting at a different time... > Yeah, uptime is moving which makes it difficult for me too. When new machines enter the network, they need to announce a number which is used to decice who will become the master if the current master disappears. I could just announce currenttime-uptime, but that's got a slightly different meaning that I'll have to consider. Anyway, enough of my proprietary mess, but... I do see a few uses for a non-moving boottime, but won't argue here or now. :) This behaviour is documented in time(9) though, so I really can't complain. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 10:32:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 0F92F14F76 for ; Thu, 16 Dec 1999 10:32:27 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA17007; Thu, 16 Dec 1999 19:31:58 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Kevin Day Cc: nate@mt.sri.com, dillon@apollo.backplane.com (Matthew Dillon), gallatin@cs.duke.edu (Andrew Gallatin), freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-reply-to: Your message of "Thu, 16 Dec 1999 12:14:54 CST." <199912161814.MAA33594@celery.dragondata.com> Date: Thu, 16 Dec 1999 19:31:58 +0100 Message-ID: <17005.945369118@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Yeah, uptime is moving which makes it difficult for me too. When new >machines enter the network, they need to announce a number which is used to >decice who will become the master if the current master disappears. I could >just announce currenttime-uptime, but that's got a slightly different >meaning that I'll have to consider. just announce uptime, the one with the largest number wins. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 10:57:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22]) by hub.freebsd.org (Postfix) with ESMTP id B57221513C for ; Thu, 16 Dec 1999 10:57:29 -0800 (PST) (envelope-from veldy@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id A2AEB3839; Thu, 16 Dec 1999 12:57:24 -0600 (CST) Received: from localhost (veldy@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id MAA16983; Thu, 16 Dec 1999 12:57:24 -0600 (CST) X-Authentication-Warning: isis.visi.com: veldy owned process doing -bs Date: Thu, 16 Dec 1999 12:57:24 -0600 (CST) From: Thomas Veldhouse To: Matthew Jacob Cc: current@FreeBSD.ORG Subject: Re: Linux vs. OpenBSD vs. FreeBSD vs. NetBSD (fwd) 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 The only point I would like to argue is that this is not a comparison of Apples to Apples. Linux is just a kernel. There are Linux only utilities however (i.e. util-linux). Each of the BSDs that you mentioned are full operating systems. The closest comparison you can get is to compare a Linux Distribution to the BSDs. I will not go there - there is plenty of information on the web for that. Tom Veldhouse veldy@visi.com On Thu, 16 Dec 1999, Matthew Jacob wrote: > > fyi > > > ---------- Forwarded message ---------- > Date: Thu, 16 Dec 1999 12:15:48 -0500 (EST) > From: Paul B. Brown > Reply-To: axp-list@redhat.com > To: axp-list@redhat.com > Subject: Re: Linux vs. OpenBSD vs. FreeBSD vs. NetBSD > Resent-Date: 16 Dec 1999 17:15:54 -0000 > Resent-From: axp-list@redhat.com > Resent-cc: recipient list not shown: ; > > > > Is there a handy collection of arguments over which OS is better? > > Hummmm . . . . this is a much debated topic. In a nutshell: > > Linux: > > 1. More prevalent > 2. More support > 3. More software ported > 4. Multi-platform: Intel, Alpha, Sparc, Mac, PowerPC, etc. > 5. GPLed > > Even though I think Linux needs further tweaking to become as high > stress as FreeBSD, I still believe it is the best bang for the buck. > There is more interest in this OS than any of the other "free" OSes. > This is a plus and a minus. The plus is that it will continue to > advance as an OS and a production platform. The minus is that now > business needs may begin to drive Linux and that will skew the > original intent of Linux and it's reason for being as good as it is. > > I've been talking to some Systems Operations boys at NASA HQ in > Washington, DC who have done (and continue to do) testing on the > "free" OSes as stable platforms for research and production at NASA. > They found that even now, FreeBSD or OpenBSD are their choice either > because of stability or speed. I found that interesting given some > of the claims I've seem on this list, and others, that Linux is now as > stable and high performance as FreeBSD on Intel. The NASA boys don't > think so. > > FreeBSD: > > 1. Higher performance especially in the network stack. > 2. Can run any Linux application using emulator. > 3. BSDL > 4. Intel Only: This means the OS is tweaked for max performance. > > This is a very stable, very robust, high stress-capable OS for Intel > platforms only. If you want to get the max out of your production > Intel platform, use FreeBSD. Yahoo does. The choice at NASA HQ. > > NetBSD: > > 1. Runs on a lot of old hardware: PDP, VAX, 3B2, etc. > 2. Very stable. > 3. BSDL. > > This one is used if you have some old hardware lying around and want > to get it functional again. This is great for older companies, > Universities, and research facilities. > > OpenBSD: > > 1. Runs on a lot of old hardware: PDP, VAX, 3B2, etc. > 2. More secure out of the box than any other xBSD. > 3. Offshoot of NetBSD. > 4. Very stable. > 5. BSDL. > > The same as NetBSD except it's security features are it's main selling > point. > > There is my $0.02 worth. :-) > > Paul > > --------------------------------------------------------------------------- > Paul B. Brown pbrown@btechnet.com > President > Brown Technologies Network, Inc. http://www.btechnet.com/ > > Systems and Applications Design, Development, Deployment, and Maintenance > --------------------------------------------------------------------------- > > -- > To unsubscribe: send e-mail to axp-list-request@redhat.com with > 'unsubscribe' as the subject. Do not send it to axp-list@redhat.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 Thu Dec 16 10:58: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 6327E14DFD for ; Thu, 16 Dec 1999 10:57:47 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id TAA04724; Thu, 16 Dec 1999 19:57:22 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <14425.6118.899093.621159@trooper.velocet.net> References: <14425.2778.943367.365945@trooper.velocet.net> <14425.6118.899093.621159@trooper.velocet.net> Date: Thu, 16 Dec 1999 19:43:09 +0100 To: David Gilbert , Brad Knowles From: Brad Knowles Subject: Re: AMI MegaRAID datapoint. Cc: David Gilbert , freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:48 AM -0500 1999/12/16, David Gilbert wrote: > It's a really long thread. I'm not going to repeat it here. > Basically, under "enough" load, vinum trashes the kernel stack in such > a way that debugging is very tough. It sounds like the second RAID-5 bug listed on the page I mentioned: >> 28 September 1999: We have seen hangs when perform heavy I/O to >> RAID-5 plexes. The symptoms are that processes hang waiting on >> vrlock and flswai. Use ps lax to display this information. >> >> Technical explanation: A deadlock arose between code locking stripes >> on a RAID-5 plex (vrlock) and code waiting for buffers to be freed >> (flswai). >> >> Status: Being fixed. I believe that I have seen this bug myself, but in my only serious attempt to replicate it, I managed to create what appears to be a new third bug which he had never seen before. Yes, I've already given all debugging information to Greg. > I got the MegaRAID 1400 because the DPT V drivers weren't available. Understandable. I didn't know that the AMI MegaRAID controller was even an option, otherwise I would have looked at it. > The MegaRAID should be roughly equivlanet to the DPT V. I'd really like to see these two benchmarked head-to-head, or at least under sufficiently similar circumstances that we can be reasonably comfortable with how well one performs relative to the other. > Do go with > LVD if you can. The drives are using SCA attachment mechanisms, but I believe that electronically they are LVD. > I have done benchmarking with bonnie instead of rawIO. The output is > as follows: I have never been impressed with the benchmarking that bonnie is capable of. In my experience, rawio is a much better tool, because it handles coordinating large numbers of child processes, doesn't lose information in communications between the parent and the child processes, by-passes all the filesystem overhead, etc.... If you want to do filesystem level benchmarking, I've been more impressed by what I've seen out of Postmark. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 11: 8:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id D504D15653 for ; Thu, 16 Dec 1999 11:08:20 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 9F6DC137FCE; Thu, 16 Dec 1999 14:08:17 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id OAA03554; Thu, 16 Dec 1999 14:08:17 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14425.14497.356453.187331@trooper.velocet.net> Date: Thu, 16 Dec 1999 14:08:17 -0500 (EST) To: Brad Knowles Cc: David Gilbert , Brad Knowles , freebsd-current@FreeBSD.ORG Subject: Re: AMI MegaRAID datapoint. In-Reply-To: References: <14425.2778.943367.365945@trooper.velocet.net> <14425.6118.899093.621159@trooper.velocet.net> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Brad" == Brad Knowles writes: Brad> It sounds like the second RAID-5 bug listed on the page I Brad> mentioned: >>> 28 September 1999: We have seen hangs when perform heavy I/O to >>> RAID-5 plexes. The symptoms are that processes hang waiting on >>> vrlock and flswai. Use ps lax to display this information. >>> >>> Technical explanation: A deadlock arose between code locking >>> stripes on a RAID-5 plex (vrlock) and code waiting for buffers to >>> be freed (flswai). >>> >>> Status: Being fixed. Maybe, maybe not. My crashes have a different signature than your according to Greg. Brad> I believe that I have seen this bug myself, but in my only Brad> I have never been impressed with the benchmarking that bonnie Brad> is capable of. In my experience, rawio is a much better tool, Brad> because it handles coordinating large numbers of child Brad> processes, doesn't lose information in communications between Brad> the parent and the child processes, by-passes all the filesystem Brad> overhead, etc.... Brad> If you want to do filesystem level benchmarking, I've been Brad> more impressed by what I've seen out of Postmark. ... well... one of the pros that I have heard for bonnie is that you get a number that is close to what you can expect with applications... vs. something like rawio that is isolating one system for intensive testing. I often use bonnie as a good weathervane of how fast a "whole system" is with it's disk. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 11:39:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id CF09915653 for ; Thu, 16 Dec 1999 11:39:54 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA55533; Thu, 16 Dec 1999 11:39:48 -0800 (PST) (envelope-from dillon) Date: Thu, 16 Dec 1999 11:39:48 -0800 (PST) From: Matthew Dillon Message-Id: <199912161939.LAA55533@apollo.backplane.com> To: Poul-Henning Kamp Cc: Kevin Day , nate@mt.sri.com, gallatin@cs.duke.edu (Andrew Gallatin), freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem References: <17005.945369118@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : :>Yeah, uptime is moving which makes it difficult for me too. When new :>machines enter the network, they need to announce a number which is used to :>decice who will become the master if the current master disappears. I could :>just announce currenttime-uptime, but that's got a slightly different :>meaning that I'll have to consider. : :just announce uptime, the one with the largest number wins. : :-- :Poul-Henning Kamp FreeBSD coreteam member :phk@FreeBSD.ORG "Real hackers run -current on their laptop." :FreeBSD -- It will take a long time before progress goes too far! Go outside, kill the circuit breaker, then turn it back on. It's easier just to use the IP address. Highest number wins. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:14:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id AC3E915047 for ; Thu, 16 Dec 1999 12:14:16 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p23-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.152]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id FAA11119; Fri, 17 Dec 1999 05:14:03 +0900 (JST) Message-ID: <38594766.D340BCDE@newsguy.com> Date: Fri, 17 Dec 1999 05:11:18 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Warner Losh Cc: Neal Westfall , freebsd-current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? References: <199912152253.PAA64569@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message Neal Westfall writes: > : "System Hoser and Mangling Utility" > > Shamu Helps Any Moronic User I need not hear a single more suggestion... brilliant! :-) -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:22:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from tantivy.stanford.edu (tantivy.Stanford.EDU [171.64.234.70]) by hub.freebsd.org (Postfix) with ESMTP id 4429414FDA for ; Thu, 16 Dec 1999 12:22:20 -0800 (PST) (envelope-from techie@tantivy.stanford.edu) Received: (from techie@localhost) by tantivy.stanford.edu (8.9.3/8.9.1) id MAA11118; Thu, 16 Dec 1999 12:19:26 -0800 (PST) Date: Thu, 16 Dec 1999 12:19:26 -0800 (PST) From: Bob Vaughan Message-Id: <199912162019.MAA11118@tantivy.stanford.edu> To: sowings@pasteur.EECS.Berkeley.EDU, wilko@yedi.iaf.nl Subject: Re: sysinstall: is it really at the end of its lifecycle? Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199912152209.OAA13108@mamba.CS.Berkeley.EDU> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Wed, 15 Dec 1999 14:09:32 -0800 > From: Sanford Owings > > > > Hm, if correct, Orca would make a good codename for a sysadm tool: > > > > Ordinary Ramblers Can [now] Admin [FreeBSD] > > Someone pointed out that Orca was already taken.... The question NOW > is: Can you come up with a good acronym for "SHAMU"? > Sysadmin Handholding And Modification Utility Sysadmin Helper And Maintainance Utility Sysadmin Helpful Automatic Maintainance Utility -- Welcome My Son, Welcome To The Machine -- Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | kc6sxc@w6yx.ampr.org | P.O. Box 9792, Stanford, Ca 94309-9792 -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:22:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 50C1215667 for ; Thu, 16 Dec 1999 12:22:43 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA90429; Thu, 16 Dec 1999 13:22:41 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA73678; Thu, 16 Dec 1999 13:22:41 -0700 (MST) Message-Id: <199912162022.NAA73678@harmony.village.org> To: mjacob@feral.com Subject: Re: HEADSUP: ntp4 to replace xntpd Cc: Ollivier Robert , "FreeBSD Current Users' list" In-reply-to: Your message of "Thu, 16 Dec 1999 09:34:50 PST." References: Date: Thu, 16 Dec 1999 13:22:40 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Matthew Jacob writes: : Huh? What about the impact on all ntp.conf files? Or is this seamless? Except for additional clocks, I've had no problems using old ntp.conf files with the new ntpd. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:24:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1663E15047 for ; Thu, 16 Dec 1999 12:24:39 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA90822; Thu, 16 Dec 1999 13:24:37 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA73705; Thu, 16 Dec 1999 13:24:37 -0700 (MST) Message-Id: <199912162024.NAA73705@harmony.village.org> To: Poul-Henning Kamp Subject: Re: Serious server-side NFS problem Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 16 Dec 1999 18:32:44 +0100." <16722.945365564@critter.freebsd.dk> References: <16722.945365564@critter.freebsd.dk> Date: Thu, 16 Dec 1999 13:24:37 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <16722.945365564@critter.freebsd.dk> Poul-Henning Kamp writes: : If people do a "settimeofday" we change the boot time since the : amount of time we've been up *IS* known for sure, whereas the boottime : is only an estimate. There is one problem with this. The amount of uptime isn't the same as the amount of time since the machine booted. How can this happen? When a laptop suspends, it doesn't update the update while it is asleep, nor does it update the uptime by the amount of time that has been slept. IS this a bug in the apm code? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:32:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 70A7015017 for ; Thu, 16 Dec 1999 12:32:54 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA92548; Thu, 16 Dec 1999 13:32:53 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA73759; Thu, 16 Dec 1999 13:32:52 -0700 (MST) Message-Id: <199912162032.NAA73759@harmony.village.org> To: nate@mt.sri.com (Nate Williams) Subject: Re: HEADSUP: ntp4 to replace xntpd Cc: "FreeBSD Current Users' list" In-reply-to: Your message of "Thu, 16 Dec 1999 11:10:45 MST." <199912161810.LAA19919@mt.sri.com> References: <199912161810.LAA19919@mt.sri.com> <16818.945366687@critter.freebsd.dk> Date: Thu, 16 Dec 1999 13:32:52 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912161810.LAA19919@mt.sri.com> Nate Williams writes: : You may not know the answer to this, but it's worth a shot. Wht kind of : accuracy can we expect using 'cheap' off-the-shelf GPS receivers? We're getting, with ntp4 on a 3.x kernel, about +- 4uSec with a cheap gps receiver + atomic clock on a i486 class machine. The clock doesn't want to sync more closely than that, likely due to the large jitter in the 8254 timing device, so the atomic clock is a bit of a waste for this part of our application (there are others it is needed for). With a pentium class machine and w/o the atomic clock "backing", I'd say you could easily get into the sub-micro second range. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:33:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 29B9F14FBB for ; Thu, 16 Dec 1999 12:33:49 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA17548; Thu, 16 Dec 1999 21:33:32 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-reply-to: Your message of "Thu, 16 Dec 1999 13:24:37 MST." <199912162024.NAA73705@harmony.village.org> Date: Thu, 16 Dec 1999 21:33:32 +0100 Message-ID: <17546.945376412@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912162024.NAA73705@harmony.village.org>, Warner Losh writes: >In message <16722.945365564@critter.freebsd.dk> Poul-Henning Kamp writes: >: If people do a "settimeofday" we change the boot time since the >: amount of time we've been up *IS* known for sure, whereas the boottime >: is only an estimate. > >There is one problem with this. The amount of uptime isn't the same >as the amount of time since the machine booted. How can this happen? >When a laptop suspends, it doesn't update the update while it is >asleep, nor does it update the uptime by the amount of time that has >been slept. IS this a bug in the apm code? Well, I don't think anybody has seriously thought about what the right semantics for APM is, and consequently the code we have is rather evil. What to do is a definition question more than anything, and I guess the answer to the question: if I call timeout(bla bla bla, 3600*hz) and suspend the machine for half an hour, how long time after it resumes will I be called ? will point the direction. In other words: Do routes expire while suspended ? Do TCP timers tick ? I would say "they sure should do, because they relates to external events" (if we accept that as the answer we need to to call softclock a LOT of times when we come out of suspend). In reality we have not clear definition of "suspend" for a unix system, and the kernel may need to learn about "timeouts on the kernel consious timescale" vs. "timeouts on the wallclock timescale" and similar hair. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:34:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 6D4F91567F for ; Thu, 16 Dec 1999 12:34:40 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id VAA00817 for freebsd-current@FreeBSD.ORG; Thu, 16 Dec 1999 21:34:39 +0100 (CET) (envelope-from olli) Date: Thu, 16 Dec 1999 21:34:39 +0100 (CET) From: Oliver Fromme Message-Id: <199912162034.VAA00817@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? Organization: Administration TU Clausthal Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve O'Hara-Smith wrote in list.freebsd-current: > On 15-Dec-99 Oliver Fromme wrote: > > Alexander Langer wrote in list.freebsd-current: > > > gunzip has approx 106 kb, but you save about 50% per executeable. > > > > -r-xr-xr-x 1 root wheel 4648 Jan 28 1999 /usr/bin/minigzip > > It requires the 50Kb libz.so.2 though and some of libc. Only very few of those libs, though. I once had a (self- contained) gunzip.com for DOS that was about 5 Kbyte. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:35:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 04C5C14D08 for ; Thu, 16 Dec 1999 12:35:27 -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.9.3/8.9.3) with SMTP id NAA08201; Thu, 16 Dec 1999 13:35:24 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA20788; Thu, 16 Dec 1999 13:35:23 -0700 Date: Thu, 16 Dec 1999 13:35:23 -0700 Message-Id: <199912162035.NAA20788@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@mt.sri.com (Nate Williams), "FreeBSD Current Users' list" Subject: Re: HEADSUP: ntp4 to replace xntpd In-Reply-To: <199912162032.NAA73759@harmony.village.org> References: <199912161810.LAA19919@mt.sri.com> <16818.945366687@critter.freebsd.dk> <199912162032.NAA73759@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : You may not know the answer to this, but it's worth a shot. Wht kind of > : accuracy can we expect using 'cheap' off-the-shelf GPS receivers? > > We're getting, with ntp4 on a 3.x kernel, about +- 4uSec with a cheap > gps receiver + atomic clock on a i486 class machine. I've got the cheap gps receiver (Garmin 12XL), but what do you mean by an 'atomic clock'? Should the GPS receiver's NMEA messages be adequate enough to do the job? However, all I need is ms accuracy, so anything below 500us is good enough for me. > The clock > doesn't want to sync more closely than that, likely due to the large > jitter in the 8254 timing device, so the atomic clock is a bit of a > waste for this part of our application (there are others it is needed > for). With a pentium class machine and w/o the atomic clock > "backing", I'd say you could easily get into the sub-micro second > range. I've got a 486, although running the antenna to an outside window might get exciting. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:37:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (Postfix) with ESMTP id E143414FBB for ; Thu, 16 Dec 1999 12:37:11 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with ESMTP id MAA07676; Thu, 16 Dec 1999 12:37:02 -0800 (PST) Date: Thu, 16 Dec 1999 12:37:02 -0800 (PST) From: Tom Bartol To: Warner Losh Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-Reply-To: <199912162024.NAA73705@harmony.village.org> 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, 16 Dec 1999, Warner Losh wrote: > In message <16722.945365564@critter.freebsd.dk> Poul-Henning Kamp writes: > : If people do a "settimeofday" we change the boot time since the > : amount of time we've been up *IS* known for sure, whereas the boottime > : is only an estimate. > > There is one problem with this. The amount of uptime isn't the same > as the amount of time since the machine booted. How can this happen? > When a laptop suspends, it doesn't update the update while it is > asleep, nor does it update the uptime by the amount of time that has > been slept. IS this a bug in the apm code? > > Warner > IIRC it does update uptime properly after a suspend in 2.2.8 but does not do so in 3.X and -current on my ThinkPad 770. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:39:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 79D9314F6B for ; Thu, 16 Dec 1999 12:39:26 -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.9.3/8.9.3) with SMTP id NAA08255; Thu, 16 Dec 1999 13:39:19 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA20890; Thu, 16 Dec 1999 13:39:18 -0700 Date: Thu, 16 Dec 1999 13:39:18 -0700 Message-Id: <199912162039.NAA20890@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: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-Reply-To: <199912162024.NAA73705@harmony.village.org> References: <16722.945365564@critter.freebsd.dk> <199912162024.NAA73705@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : If people do a "settimeofday" we change the boot time since the > : amount of time we've been up *IS* known for sure, whereas the boottime > : is only an estimate. > > There is one problem with this. The amount of uptime isn't the same > as the amount of time since the machine booted. How can this happen? > When a laptop suspends, it doesn't update the update while it is > asleep, nor does it update the uptime by the amount of time that has > been slept. FWIW, we had code in the tree (just before the timeout_ch changes) that did update all of the timeouts to 'fire' when the laptop was resumed. This caused a 'thundering herd' problem at resume, but I don't see any way around it... However, it was lost when we changed to the different timeout code. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:39:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 35A3A14C39 for ; Thu, 16 Dec 1999 12:39:42 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA92594; Thu, 16 Dec 1999 13:39:40 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA73855; Thu, 16 Dec 1999 13:39:39 -0700 (MST) Message-Id: <199912162039.NAA73855@harmony.village.org> To: Poul-Henning Kamp Subject: Re: Serious server-side NFS problem Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 16 Dec 1999 21:33:32 +0100." <17546.945376412@critter.freebsd.dk> References: <17546.945376412@critter.freebsd.dk> Date: Thu, 16 Dec 1999 13:39:39 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <17546.945376412@critter.freebsd.dk> Poul-Henning Kamp writes: : Well, I don't think anybody has seriously thought about what the right : semantics for APM is, and consequently the code we have is rather evil. Don't know if I'd go so far as to say evil, but there are some pola issues. : What to do is a definition question more than anything, and I guess the : answer to the question: : : if I call timeout(bla bla bla, 3600*hz) and suspend the machine : for half an hour, how long time after it resumes will I be : called ? : : will point the direction. It will be called 3600*hz softclock ticks after the original timeout was called, which could be >> a wall time of 1 hour. I'd guess that it would be after 1 hour and 30 minutes. : In other words: : Do routes expire while suspended ? : Do TCP timers tick ? : : I would say "they sure should do, because they relates to external : events" (if we accept that as the answer we need to to call softclock : a LOT of times when we come out of suspend). Uggg. That's right. The current approach is to step the current time by the amount of time we slept, based on rtc measurements (high precision time keeping at its absolute worst). : In reality we have not clear definition of "suspend" for a unix system, : and the kernel may need to learn about "timeouts on the kernel consious : timescale" vs. "timeouts on the wallclock timescale" and similar hair. Yes. Some timeouts don't matter over a suspend (eg make sure that this card isn't wedged) while some should take the suspend into account (need to expire routes, arp entries, etc) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:42: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5A07E15662 for ; Thu, 16 Dec 1999 12:41:55 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA92614; Thu, 16 Dec 1999 13:41:54 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA73896; Thu, 16 Dec 1999 13:41:53 -0700 (MST) Message-Id: <199912162041.NAA73896@harmony.village.org> To: nate@mt.sri.com (Nate Williams) Subject: Re: HEADSUP: ntp4 to replace xntpd Cc: "FreeBSD Current Users' list" In-reply-to: Your message of "Thu, 16 Dec 1999 13:35:23 MST." <199912162035.NAA20788@mt.sri.com> References: <199912162035.NAA20788@mt.sri.com> <199912161810.LAA19919@mt.sri.com> <16818.945366687@critter.freebsd.dk> <199912162032.NAA73759@harmony.village.org> Date: Thu, 16 Dec 1999 13:41:53 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912162035.NAA20788@mt.sri.com> Nate Williams writes: : > : You may not know the answer to this, but it's worth a shot. Wht kind of : > : accuracy can we expect using 'cheap' off-the-shelf GPS receivers? : > : > We're getting, with ntp4 on a 3.x kernel, about +- 4uSec with a cheap : > gps receiver + atomic clock on a i486 class machine. : : I've got the cheap gps receiver (Garmin 12XL), but what do you mean by : an 'atomic clock'? Should the GPS receiver's NMEA messages be adequate : enough to do the job? However, all I need is ms accuracy, so anything : below 500us is good enough for me. We have a cesium clock, which is generally called atomic clock, that we use for various things in our system. If the GPS gives out a PPS signal for the NMEA, then you can likely hit 1mS w/o any problems at all. Don't know a thing about the Garmin 12XL to know for sure about how it operates. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:42:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 81F3D15683 for ; Thu, 16 Dec 1999 12:42:27 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA92619; Thu, 16 Dec 1999 13:42:25 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA73909; Thu, 16 Dec 1999 13:42:25 -0700 (MST) Message-Id: <199912162042.NAA73909@harmony.village.org> To: Tom Bartol Subject: Re: Serious server-side NFS problem Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 16 Dec 1999 12:37:02 PST." References: Date: Thu, 16 Dec 1999 13:42:25 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Tom Bartol writes: : IIRC it does update uptime properly after a suspend in 2.2.8 but does not : do so in 3.X and -current on my ThinkPad 770. define correctly. Eg, if I suspend for an hour it adds an hour? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:44:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as7-034.rp-plus.de [149.221.239.34]) by hub.freebsd.org (Postfix) with ESMTP id 2A08A15047 for ; Thu, 16 Dec 1999 12:44:08 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 34751AB7F; Thu, 16 Dec 1999 21:44:49 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id VAA49400; Thu, 16 Dec 1999 21:44:34 +0100 (CET) (envelope-from alex) Date: Thu, 16 Dec 1999 21:44:34 +0100 From: Alexander Langer To: Oliver Fromme Cc: freebsd-current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991216214434.A49330@cichlids.cichlids.com> Mail-Followup-To: Oliver Fromme , freebsd-current@FreeBSD.ORG References: <199912151624.RAA01525@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912151624.RAA01525@dorifer.heim3.tu-clausthal.de>; from olli@dorifer.heim3.tu-clausthal.de on Wed, Dec 15, 1999 at 05:24:24PM +0100 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Also sprach Oliver Fromme (olli@dorifer.heim3.tu-clausthal.de): > > gunzip has approx 106 kb, but you save about 50% per executeable. > -r-xr-xr-x 1 root wheel 4648 Jan 28 1999 /usr/bin/minigzip ok, even better :-) Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:44:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id A6CB115742 for ; Thu, 16 Dec 1999 12:44:10 -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.9.3/8.9.3) with SMTP id NAA08310; Thu, 16 Dec 1999 13:44:00 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA20958; Thu, 16 Dec 1999 13:43:46 -0700 Date: Thu, 16 Dec 1999 13:43:46 -0700 Message-Id: <199912162043.NAA20958@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@mt.sri.com (Nate Williams), "FreeBSD Current Users' list" Subject: Re: HEADSUP: ntp4 to replace xntpd In-Reply-To: <199912162041.NAA73896@harmony.village.org> References: <199912162035.NAA20788@mt.sri.com> <199912161810.LAA19919@mt.sri.com> <16818.945366687@critter.freebsd.dk> <199912162032.NAA73759@harmony.village.org> <199912162041.NAA73896@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : > : You may not know the answer to this, but it's worth a shot. Wht kind of > : > : accuracy can we expect using 'cheap' off-the-shelf GPS receivers? > : > > : > We're getting, with ntp4 on a 3.x kernel, about +- 4uSec with a cheap > : > gps receiver + atomic clock on a i486 class machine. > : > : I've got the cheap gps receiver (Garmin 12XL), but what do you mean by > : an 'atomic clock'? Should the GPS receiver's NMEA messages be adequate > : enough to do the job? However, all I need is ms accuracy, so anything > : below 500us is good enough for me. > > We have a cesium clock, which is generally called atomic clock, that > we use for various things in our system. If the GPS gives out a PPS > signal for the NMEA, then you can likely hit 1mS w/o any problems at > all. Cool. I was under the impression that the cheap NMEA signals only gave 2-5sec accuracy given the 2400 baud speed issues. > Don't know a thing about the Garmin 12XL to know for sure about > how it operates. It just a standard 'cheap' GPS. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:46:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id B9DED14D08 for ; Thu, 16 Dec 1999 12:46:23 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA17664; Thu, 16 Dec 1999 21:45:57 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: nate@mt.sri.com (Nate Williams) Cc: mjacob@feral.com, Ollivier Robert , "FreeBSD Current Users' list" Subject: Re: HEADSUP: ntp4 to replace xntpd In-reply-to: Your message of "Thu, 16 Dec 1999 11:10:45 MST." <199912161810.LAA19919@mt.sri.com> Date: Thu, 16 Dec 1999 21:45:57 +0100 Message-ID: <17662.945377157@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912161810.LAA19919@mt.sri.com>, Nate Williams writes: >> Between the two of us Dave Mills and I have managed to get the >> "nanokernel" to act sensibly in the domain inside +/- 1usec which >> the old one didn't. (See http://gps.freebsd.dk for what kind of >> performance this can result in, given appropriate hardware). > >You may not know the answer to this, but it's worth a shot. Wht kind of >accuracy can we expect using 'cheap' off-the-shelf GPS receivers? I think there are several classes of GPS receivers: "What is a PPS signal ?" Typically handheld/boat naviation stuff. The NMEA or other serial timecodes are at best in the 1msec class. "VP Marketing to VP engineering: Everybody else has a PPS signal make sure our product has one too at no extra cost or schedule changes." You don't want to know. As bad as 1msec have been seen, jitter as bad as 200nsec. "Straight PPS" Derived from the internal clock, typically in the "a few usec" class. "Position hold PPS" State of the art 1 band GPS does a stddev of about 35nsec. The Motorola Oncore UT+ is considered the leader of the pack I think, other vendors have similar devices. "Postion hold PPS + OCXO" OEM products doing basically what the HP 58503A does. We're into cesium like (or better!) quality here. I have *not* heard some rumours about carrier phase tracking low cost receivers, and I was *not* told that they can practically uwiggle the S/A when in position hold mode and I was *not* told to expect them on the market in 1H2000 :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:46:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 162B5156E9 for ; Thu, 16 Dec 1999 12:46:36 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA92652; Thu, 16 Dec 1999 13:46:34 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA74003; Thu, 16 Dec 1999 13:46:34 -0700 (MST) Message-Id: <199912162046.NAA74003@harmony.village.org> To: nate@mt.sri.com (Nate Williams) Subject: Re: HEADSUP: ntp4 to replace xntpd Cc: "FreeBSD Current Users' list" In-reply-to: Your message of "Thu, 16 Dec 1999 13:43:46 MST." <199912162043.NAA20958@mt.sri.com> References: <199912162043.NAA20958@mt.sri.com> <199912162035.NAA20788@mt.sri.com> <199912161810.LAA19919@mt.sri.com> <16818.945366687@critter.freebsd.dk> <199912162032.NAA73759@harmony.village.org> <199912162041.NAA73896@harmony.village.org> Date: Thu, 16 Dec 1999 13:46:34 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912162043.NAA20958@mt.sri.com> Nate Williams writes: : Cool. I was under the impression that the cheap NMEA signals only gave : 2-5sec accuracy given the 2400 baud speed issues. If you have a PPS signal, then you can get fairly close even if the inforation about the PPS signal comes in at 2400 baud. If you have no PPS signal (eg a DTR or DSR that pulses once a second), then you are SOL for anything better than a few seconds. : > Don't know a thing about the Garmin 12XL to know for sure about : > how it operates. : : It just a standard 'cheap' GPS. My only GPS experience is with Motorola OnCore receivers. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:48:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id F0B2415770 for ; Thu, 16 Dec 1999 12:48:13 -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.9.3/8.9.3) with SMTP id NAA08370; Thu, 16 Dec 1999 13:48:09 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA21039; Thu, 16 Dec 1999 13:48:08 -0700 Date: Thu, 16 Dec 1999 13:48:08 -0700 Message-Id: <199912162048.NAA21039@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@mt.sri.com (Nate Williams), "FreeBSD Current Users' list" Subject: Re: HEADSUP: ntp4 to replace xntpd In-Reply-To: <199912162046.NAA74003@harmony.village.org> References: <199912162043.NAA20958@mt.sri.com> <199912162035.NAA20788@mt.sri.com> <199912161810.LAA19919@mt.sri.com> <16818.945366687@critter.freebsd.dk> <199912162032.NAA73759@harmony.village.org> <199912162041.NAA73896@harmony.village.org> <199912162046.NAA74003@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : Cool. I was under the impression that the cheap NMEA signals only gave > : 2-5sec accuracy given the 2400 baud speed issues. > > If you have a PPS signal, then you can get fairly close even if the > inforation about the PPS signal comes in at 2400 baud. Hmm, how do I find out how good it is? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:49:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (Postfix) with ESMTP id AAA1B15707 for ; Thu, 16 Dec 1999 12:49:37 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with ESMTP id MAA07935; Thu, 16 Dec 1999 12:49:26 -0800 (PST) Date: Thu, 16 Dec 1999 12:49:27 -0800 (PST) From: Tom Bartol To: Warner Losh Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-Reply-To: <199912162042.NAA73909@harmony.village.org> 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, 16 Dec 1999, Warner Losh wrote: > In message Tom Bartol writes: > : IIRC it does update uptime properly after a suspend in 2.2.8 but does not > : do so in 3.X and -current on my ThinkPad 770. > > define correctly. Eg, if I suspend for an hour it adds an hour? > > Warner > Yeah, that's what I meant by "correctly". I don't recall seeing a "thundering herd" effect afterwards. Hmmm... which reminds me, I believe this was not stock 2.2.8 but rather 2.2.8-PAO. I had thought that the lion's share of PAO code got merged into 3.0-current at some point. When I tried 3.0-current after this merge, suspend and resume worked fine on my 770 with the exception of uptime. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:50:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id CD42514E50 for ; Thu, 16 Dec 1999 12:50: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.9.3/8.9.3) with SMTP id NAA08384; Thu, 16 Dec 1999 13:50:13 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA21068; Thu, 16 Dec 1999 13:50:12 -0700 Date: Thu, 16 Dec 1999 13:50:12 -0700 Message-Id: <199912162050.NAA21068@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Poul-Henning Kamp Cc: nate@mt.sri.com (Nate Williams), mjacob@feral.com, Ollivier Robert , "FreeBSD Current Users' list" Subject: Re: HEADSUP: ntp4 to replace xntpd In-Reply-To: <17662.945377157@critter.freebsd.dk> References: <199912161810.LAA19919@mt.sri.com> <17662.945377157@critter.freebsd.dk> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> Between the two of us Dave Mills and I have managed to get the > >> "nanokernel" to act sensibly in the domain inside +/- 1usec which > >> the old one didn't. (See http://gps.freebsd.dk for what kind of > >> performance this can result in, given appropriate hardware). > > > >You may not know the answer to this, but it's worth a shot. Wht kind of > >accuracy can we expect using 'cheap' off-the-shelf GPS receivers? > > I think there are several classes of GPS receivers: > > "What is a PPS signal ?" > > Typically handheld/boat naviation stuff. The NMEA or other > serial timecodes are at best in the 1msec class. Again, for me this is acceptable. It would be nice to have it better than this, but the kernel's of all the OS's I'm using have at best 1ms precision for all of the applications being used (FS timestamps, application program timestamps, etc...). > "VP Marketing to VP engineering: Everybody else has a PPS signal > make sure our product has one too at no extra cost or schedule changes." > > You don't want to know. As bad as 1msec have been seen, > jitter as bad as 200nsec. > > "Straight PPS" > > Derived from the internal clock, typically in the "a few usec" > class. > > "Position hold PPS" > > State of the art 1 band GPS does a stddev of about 35nsec. The > Motorola Oncore UT+ is considered the leader of the pack I think, > other vendors have similar devices. > > "Postion hold PPS + OCXO" > > OEM products doing basically what the HP 58503A does. > We're into cesium like (or better!) quality here. > > I have *not* heard some rumours about carrier phase tracking low cost > receivers, and I was *not* told that they can practically uwiggle > the S/A when in position hold mode and I was *not* told to expect them > on the market in 1H2000 :-) As I mentioned to Warner, is there any way to know how good a particular model of a GPS receiver is? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:53:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0CCF315782 for ; Thu, 16 Dec 1999 12:53:13 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA92692; Thu, 16 Dec 1999 13:53:11 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA74078; Thu, 16 Dec 1999 13:53:11 -0700 (MST) Message-Id: <199912162053.NAA74078@harmony.village.org> To: nate@mt.sri.com (Nate Williams) Subject: Re: HEADSUP: ntp4 to replace xntpd Cc: "FreeBSD Current Users' list" In-reply-to: Your message of "Thu, 16 Dec 1999 13:48:08 MST." <199912162048.NAA21039@mt.sri.com> References: <199912162048.NAA21039@mt.sri.com> <199912162043.NAA20958@mt.sri.com> <199912162035.NAA20788@mt.sri.com> <199912161810.LAA19919@mt.sri.com> <16818.945366687@critter.freebsd.dk> <199912162032.NAA73759@harmony.village.org> <199912162041.NAA73896@harmony.village.org> <199912162046.NAA74003@harmony.village.org> Date: Thu, 16 Dec 1999 13:53:11 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912162048.NAA21039@mt.sri.com> Nate Williams writes: : > : Cool. I was under the impression that the cheap NMEA signals only gave : > : 2-5sec accuracy given the 2400 baud speed issues. : > : > If you have a PPS signal, then you can get fairly close even if the : > inforation about the PPS signal comes in at 2400 baud. : : Hmm, how do I find out how good it is? By looking at the docs to see if it supports PPS or not. PPS is Pulse Per Second and is a dedicated signal that pulses (typ 10mS) once per second. For serial devices, this is typically done by one of the extra RS-232 signals, DSR comes to mind. I suppose you could hook a scope up to the unit and see if any of the signals are acting like PPS. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:54:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D97FC15726 for ; Thu, 16 Dec 1999 12:54:34 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA92701; Thu, 16 Dec 1999 13:54:32 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA74098; Thu, 16 Dec 1999 13:54:31 -0700 (MST) Message-Id: <199912162054.NAA74098@harmony.village.org> To: Tom Bartol Subject: Re: Serious server-side NFS problem Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 16 Dec 1999 12:49:27 PST." References: Date: Thu, 16 Dec 1999 13:54:31 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Tom Bartol writes: : I tried 3.0-current after this merge, suspend and resume worked fine on my : 770 with the exception of uptime. I can confirm that uptime, at least as reported by uptime(1), isn't increased in the latest -current. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 12:55:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 9F6BB1569D for ; Thu, 16 Dec 1999 12:55:09 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA17731; Thu, 16 Dec 1999 21:54:47 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: nate@mt.sri.com (Nate Williams) Cc: Warner Losh , "FreeBSD Current Users' list" Subject: Re: HEADSUP: ntp4 to replace xntpd In-reply-to: Your message of "Thu, 16 Dec 1999 13:35:23 MST." <199912162035.NAA20788@mt.sri.com> Date: Thu, 16 Dec 1999 21:54:47 +0100 Message-ID: <17729.945377687@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912162035.NAA20788@mt.sri.com>, Nate Williams writes: >> : You may not know the answer to this, but it's worth a shot. Wht kind of >> : accuracy can we expect using 'cheap' off-the-shelf GPS receivers? >> >> We're getting, with ntp4 on a 3.x kernel, about +- 4uSec with a cheap >> gps receiver + atomic clock on a i486 class machine. > >I've got the cheap gps receiver (Garmin 12XL), but what do you mean by >an 'atomic clock'? Should the GPS receiver's NMEA messages be adequate >enough to do the job? However, all I need is ms accuracy, so anything >below 500us is good enough for me. If you only have NMEA you will have a hard time. At 1200 baud you get 50 usec jitter just from the rxclock in the uart (16 * 1200), not to mention how exact the NMEA is transmitted in the first place. There is a pretty vanilla NMEA refclock, so the easist way to find out is to try it out next to (in a network sense) a stratum 1 NTP. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 13: 2:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 2E64D14E16 for ; Thu, 16 Dec 1999 13:02:30 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA17771; Thu, 16 Dec 1999 22:01:43 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: nate@mt.sri.com (Nate Williams) Cc: mjacob@feral.com, Ollivier Robert , "FreeBSD Current Users' list" Subject: Re: HEADSUP: ntp4 to replace xntpd In-reply-to: Your message of "Thu, 16 Dec 1999 13:50:12 MST." <199912162050.NAA21068@mt.sri.com> Date: Thu, 16 Dec 1999 22:01:43 +0100 Message-ID: <17769.945378103@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912162050.NAA21068@mt.sri.com>, Nate Williams writes: >> >> "What is a PPS signal ?" >> >> Typically handheld/boat naviation stuff. The NMEA or other >> serial timecodes are at best in the 1msec class. > >Again, for me this is acceptable. It would be nice to have it better >than this, but the kernel's of all the OS's I'm using have at best 1ms >precision for all of the applications being used (FS timestamps, >application program timestamps, etc...). Well, when I say "at best" I mean it. One NMEA boat-navigation unit I had access to over last winter had +/- 400msec performance. >As I mentioned to Warner, is there any way to know how good a particular >model of a GPS receiver is? measure it. It's not that hard actually, because you can trust the FreeBSD clock to be allright over short time intervals, so you timestamp the events (NEMA / PPS / Whatever) and analyse the pairwise difference between them: for instance: xxxxx2.100000 xxxxx3.140000 xxxxx4.120000 gives you *two* datapoints: +.040000 second and -.020000 second. Find the stddev of a couple of thousand samples and you have a good number which is correct to within a factor sqrt(two) or so of the real jitter. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 13: 5:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 0641115697; Thu, 16 Dec 1999 13:05:47 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id NAA27445; Thu, 16 Dec 1999 13:05:37 -0800 (PST) Date: Thu, 16 Dec 1999 13:05:36 -0800 (PST) From: Julian Elischer To: Patrick Bihan-Faou Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Status of the netatalk stack In-Reply-To: <00c501bf47ec$01fee840$040aa8c0@local.mindstep.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 the kernel code for appletalk is 'out of date' but it is also somewhat modified.. If you want to work with it, let me know and I can help as I did the original integration into our tree, Julian On Thu, 16 Dec 1999, Patrick Bihan-Faou wrote: > Hi, > > > I was looking at the netatalk package and the appletalk support in the > kernel source code and I realized that they are based on the same code > originally (the code from netatalk). > > The kernel code however is quite out of date from what can be found in the > netatalk-asun package. I was wondering if anybody is planning on integrating > the latest changes ? If not is it something that I should undertake ? Are > there any major reasons why the code in freebsd should be left alone ? > > > PS. I cross-posted in current and stable because it affects both stream in > the same way, however I guess the discussion should be kept in "current", so > please try to reply to the correct address. Thanks. > > > > Patrick. > > -- > www.mindstep.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 Thu Dec 16 13: 5:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (Postfix) with ESMTP id 75D011581D for ; Thu, 16 Dec 1999 13:05:53 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with ESMTP id NAA08234; Thu, 16 Dec 1999 13:05:45 -0800 (PST) Date: Thu, 16 Dec 1999 13:05:45 -0800 (PST) From: Tom Bartol To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-Reply-To: <199912162054.NAA74098@harmony.village.org> 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, 16 Dec 1999, Warner Losh wrote: > In message Tom Bartol writes: > : I tried 3.0-current after this merge, suspend and resume worked fine on my > : 770 with the exception of uptime. > > I can confirm that uptime, at least as reported by uptime(1), isn't > increased in the latest -current. > > Warner > I confirm this as well. Perhaps after suspend we need: Allow ntp to update time and adjust boottime as necessary. Then set uptime = time-boottime Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 13:11:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id E8EA015832 for ; Thu, 16 Dec 1999 13:11:04 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40335>; Fri, 17 Dec 1999 08:02:27 +1100 Content-return: prohibited Date: Fri, 17 Dec 1999 08:10:54 +1100 From: Peter Jeremy Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: ; from steve@pooh.elsevier.nl on Thu, Dec 16, 1999 at 07:55:35PM +1100 To: freebsd-current@FreeBSD.ORG Message-Id: <99Dec17.080227est.40335@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <199912151624.RAA01525@dorifer.heim3.tu-clausthal.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Dec-16 19:55:35 +1100, Steve O'Hara-Smith wrote: >On 15-Dec-99 Oliver Fromme wrote: >> Alexander Langer wrote in list.freebsd-current: >> > gunzip has approx 106 kb, but you save about 50% per executeable. >> >> -r-xr-xr-x 1 root wheel 4648 Jan 28 1999 /usr/bin/minigzip > > It requires the 50Kb libz.so.2 though and some of libc. % cc -static -O -o minigzip minigzip.c -lz % size minigzip text data bss dec hex filename 75299 8524 2004 85827 14f43 minigzip % ls -l minigzip -rwxr-xr-x 1 jeremyp inplat 96509 Dec 17 08:08 minigzip % Or, ignoring the libc code (which is indicative of the effect of building it into a crunched executable): % cc -O -o minigzip minigzip.c /usr/lib/libz.a % ls -l minigzip -rwxr-xr-x 1 jeremyp inplat 48523 Dec 17 08:08 minigzip % size minigzip text data bss dec hex filename 37756 4848 272 42876 a77c minigzip % Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 13:22:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from modemcable156.106-200-24.mtl.mc.videotron.net (modemcable126.102-200-24.mtl.mc.videotron.net [24.200.102.126]) by hub.freebsd.org (Postfix) with SMTP id 40CEE156B4 for ; Thu, 16 Dec 1999 13:22:47 -0800 (PST) (envelope-from patrick@mindstep.com) Received: (qmail 53458 invoked from network); 16 Dec 1999 21:22:41 -0000 Received: from patrak.local.mindstep.com (HELO patrak) (192.168.10.4) by jacuzzi.local.mindstep.com with SMTP; 16 Dec 1999 21:22:41 -0000 Message-ID: <013a01bf480b$af2b64c0$040aa8c0@local.mindstep.com> From: "Patrick Bihan-Faou" To: "Julian Elischer" Cc: References: Subject: Re: Status of the netatalk stack Date: Thu, 16 Dec 1999 16:22:40 -0500 Organization: MindStep Corporation 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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Julian, > the kernel code for appletalk is 'out of date' but it is also > somewhat modified.. > > If you want to work with it, let me know and I can help as I did the > original integration into our tree, > Well I would definitelly appreciate a quick summary of the changes that you did to integrate the netatalk code. A couple of pointers on what to look for would be really good to! Anyway, I will try to get working on this during the hollidays or maybe early in january. a+ Patrick. -- www.mindstep.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 13:55:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-122.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.250]) by hub.freebsd.org (Postfix) with ESMTP id 5F6DF15B24 for ; Thu, 16 Dec 1999 13:55:33 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id VAA02631 for ; Thu, 16 Dec 1999 21:50:57 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id HAA00841 for ; Thu, 16 Dec 1999 07:37:12 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912160737.HAA00841@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: FreeBSD-current@FreeBSD.org Subject: make world [bsd.info.mk] - patch ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Dec 1999 07:37:12 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I can only assume that I'm doing something strange locally, but I've now got two machines that do this, and my third -current machine hasn't been installworld'd in a while.... The problem is that I can't ``make install'' any info files... I get something like: $ make clean && make depend && make && sudo make install .....[make looks fine]..... ===> doc sflag=`grep -q ^INFO-DIR-SECTION com_err.info || echo 1`; eflag=`grep -q ^START-INFO-DIR-ENTRY com_err.info || echo 1`; install-info ${sflag:+--section="Programming & development tools."} ${eflag:+--entry="* libcom_err: (com_err). A Common Error Description Library for UNIX."} com_err.info /usr/share/info/dir install-info: Undefined error: 0 for /usr/share/info/dir *** Error code 1 Stop in /usr/src/lib/libcom_err/doc. *** Error code 1 Stop in /usr/src/lib/libcom_err. From what I can tell, this shouldn't work anyway.... but the attached patch fixes things. Am I missing something ? Cheers. cvs diff: Diffing . Index: bsd.info.mk =================================================================== RCS file: /home/ncvs/src/share/mk/bsd.info.mk,v retrieving revision 1.56 diff -u -r1.56 bsd.info.mk --- bsd.info.mk 1999/08/28 00:21:46 1.56 +++ bsd.info.mk 1999/12/16 07:27:58 @@ -32,7 +32,7 @@ # INFODIR Base path for GNU's hypertext system # called Info (see info(1)). [${SHAREDIR}/info] # -# INFODIRFILE Top level node/index for info files. [dir] +# INFODIRFILE Top level node/index for info files. [$INFO.info.gz] # # INFOGRP Info group. [${SHAREGRP}] # @@ -86,7 +86,7 @@ MAKEINFO?= makeinfo MAKEINFOFLAGS+= --no-split # simplify some things, e.g., compression SRCDIR?= ${.CURDIR} -INFODIRFILE?= dir +INFODIRFILE?= ${INFO:S/$/.info.gz/} INFOTMPL?= ${INFODIR}/dir-tmpl INSTALLINFO?= install-info INFOSECTION?= Miscellaneous -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 13:59:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl4.philips.com (gw-nl4.philips.com [192.68.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 3A4EE156BE for ; Thu, 16 Dec 1999 13:59:27 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl4.philips.com with ESMTP id WAA20473 for ; Thu, 16 Dec 1999 22:59:24 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl4.philips.com via mwrap (4.0a) id xma020471; Thu, 16 Dec 99 22:59:24 +0100 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with SMTP id WAA25345 for ; Thu, 16 Dec 1999 22:59:24 +0100 (MET) Received: (qmail 46434 invoked by uid 666); 16 Dec 1999 22:16:09 -0000 Date: Thu, 16 Dec 1999 23:16:09 +0100 From: Jos Backus To: freebsd-current@freebsd.org Subject: make world broken Message-ID: <19991216231609.A90209@hal.mpn.cp.philips.com> Reply-To: Jos Backus Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cd /usr/src/gnu/usr.bin/cc/f771; make build-tools cc -O -pipe -march=pentium -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_T ARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/us r/src/gnu/usr.bin/cc/f771/../cc_tools -I/usr/src/gnu/usr.bin/cc/f771/../cc_tools -I/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/c c/f771/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/f771/../../../.. /contrib/gcc/f -I. -c /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/f ini.c In file included from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/pro j.h:28, from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/fin i.c:24: /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/hconfig.j:25: hconfig.h: No such file or directory In file included from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/sys tem.j:25, from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/pro j.h:32, from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/fin i.c:24: /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/system.h:348: conflicting t ypes for `sys_errlist' /usr/include/stdio.h:225: previous declaration of `sys_errlist' /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/system.h:394: syntax error before `PVPROTO' *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/f771. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ 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 Dec 16 14:23:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 26454155EF for ; Thu, 16 Dec 1999 14:23:56 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p23-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.152]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id HAA07982; Fri, 17 Dec 1999 07:23:43 +0900 (JST) Message-ID: <38595274.C3E61DEE@newsguy.com> Date: Fri, 17 Dec 1999 05:58:28 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: David Scheidt Cc: Poul-Henning Kamp , Warner Losh , current@FreeBSD.ORG Subject: Re: Init Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) ) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Scheidt wrote: > > What's wrong with run with system V runlevels? Other than it's system V and > everything AT^HUSL did is evil, of course. They try to map graphs into a line. -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 14:51:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 8DCEC1507E for ; Thu, 16 Dec 1999 14:51:07 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id QAA00962; Thu, 16 Dec 1999 16:50:56 -0600 (CST) (envelope-from dick) Date: Thu, 16 Dec 1999 16:50:55 -0600 From: "Richard Seaman, Jr." To: Soren Schmidt Cc: djb@Wit389306.student.utwente.nl, freebsd-current@FreeBSD.ORG Subject: Re: ATA driver problem?? (lost disk contact) Message-ID: <19991216165055.A320@tar.com> References: <19991216091950.B8469@relativity.student.utwente.nl> <199912160825.JAA71207@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912160825.JAA71207@freebsd.dk>; from sos@freebsd.dk on Thu, Dec 16, 1999 at 09:25:11AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 09:25:11AM +0100, Soren Schmidt wrote: > There is this thing with the IBM's doing some headcleaning stuff once > a day/week, but I've never seen any of my IBM's do that (I got plenty > of them). I'll try to get more info on that from IBM... Check http://www.storage.ibm.com/techsup/hddtech/prodspec/djna_spw.pdf On page 99 it says: 10.12 Automatic Drive Maintenance (ADM) ADM function is equipped to maintain the reliability even in continuous usage. ADM function is to go into Standby mode automatically after detecting idle mode at intervals of 6 days. This function is always enabled regardless of Standby Timer value. The detail of Standby Timer is described in 12.6, "Idle (E3h/97h)" on page 122, and 12.32, "Standby (E2h/96h)" on page 171. The 6 days counter is reset at the following. Power on Ready Entering Standby mode by Standby Command Entering Standby mode by Standby Timer Both Soft Reset and Hard Reset do not disturb the spin down of ADM. If a command is received during spin down of ADM, the drive quits the spin down and tries to complete the command as soon as possible. In case the spin down of ADM is disturbed by a command, it is retried 12 hours later. For timeout concern, refer to 13.0, "Timeout Values" on page 185. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 15: 3:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 0919E14FC4 for ; Thu, 16 Dec 1999 15:03:06 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id PAA68845; Thu, 16 Dec 1999 15:01:59 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199912162301.PAA68845@troutmask.apl.washington.edu> Subject: Re: Status of the netatalk stack In-Reply-To: <013a01bf480b$af2b64c0$040aa8c0@local.mindstep.com> from Patrick Bihan-Faou at "Dec 16, 1999 04:22:40 pm" To: patrick@mindstep.com (Patrick Bihan-Faou) Date: Thu, 16 Dec 1999 15:01:59 -0800 (PST) Cc: julian@whistle.com (Julian Elischer), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Patrick Bihan-Faou wrote: [Charset iso-8859-1 unsupported, filtering to ASCII...] > Hi Julian, > > > the kernel code for appletalk is 'out of date' but it is also > > somewhat modified.. > > > > If you want to work with it, let me know and I can help as I did the > > original integration into our tree, > > > > Well I would definitelly appreciate a quick summary of the changes that you > did to integrate the netatalk code. A couple of pointers on what to look for > would be really good to! > The cvs repository of the netatalk kernel code can be reviewed by looking at http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netatalk Julian and others have also modified at least netstat to understand atalk. There my be other utilities that need to be scrutinized. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 15:23:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 28B1814A07 for ; Thu, 16 Dec 1999 15:23:23 -0800 (PST) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 6F1171E26; Fri, 17 Dec 1999 00:23:32 +0100 (CET) Date: Fri, 17 Dec 1999 00:23:32 +0100 From: "Dave J. Boers" To: "Richard Seaman, Jr." Cc: Soren Schmidt , freebsd-current@FreeBSD.ORG Subject: Re: ATA driver problem?? (lost disk contact) Message-ID: <19991217002332.A10820@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <19991216091950.B8469@relativity.student.utwente.nl> <199912160825.JAA71207@freebsd.dk> <19991216165055.A320@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991216165055.A320@tar.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 04:50:55PM -0600, Richard Seaman, Jr. wrote: > Check http://www.storage.ibm.com/techsup/hddtech/prodspec/djna_spw.pdf > If a command is received during spin down of ADM, the drive quits the spin down > and tries to complete the command as soon as possible. > In case the spin down of ADM is disturbed by a command, it is retried 12 hours > later. That sure sounds like my 12 hours. I guess this more or solves the mystery. There is still one thing which keeps me wondering, though. How exactly does the ata driver react to the drive doing ADM? Whenever I hear it spinning down, I immediately hear it spinning up again. Does this mean that the ATA driver won't allow the drive to do _any_ ADM at all? Is that a bad thing? Regards, Dave Boers -- God, root, what's the difference? djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 15:31:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from jasper.heartland.ab.ca (jasper.heartland.ab.ca [207.107.228.1]) by hub.freebsd.org (Postfix) with ESMTP id 5717114F2C for ; Thu, 16 Dec 1999 15:31:19 -0800 (PST) (envelope-from dkwiebe@heartland.ab.ca) Received: from heartland.ab.ca (dyn102.heartland.ab.ca [207.107.228.102]) by jasper.heartland.ab.ca (8.9.0/8.9.0) with ESMTP id QAA13228; Thu, 16 Dec 1999 16:18:25 -0700 (MST) Message-ID: <385AC788.56641747@heartland.ab.ca> Date: Fri, 17 Dec 1999 16:30:16 -0700 From: Darren Wiebe Reply-To: dkwiebe@hagenhomes.com Organization: Hagen Homes Ltd. X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Jos Backus Cc: freebsd-current@FreeBSD.ORG Subject: Re: make world broken References: <19991216231609.A90209@hal.mpn.cp.philips.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jos Backus wrote: I just built the world from sources about 3-4 hours ago. It was all great. Darren Wiebe dkwiebe@hagenhomes.com > > cd /usr/src/gnu/usr.bin/cc/f771; make build-tools > cc -O -pipe -march=pentium -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_T > ARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/us > r/src/gnu/usr.bin/cc/f771/../cc_tools -I/usr/src/gnu/usr.bin/cc/f771/../cc_tools > -I/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/c > c/f771/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/f771/../../../.. > /contrib/gcc/f -I. -c /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/f > ini.c > In file included from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/pro > j.h:28, > from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/fin > i.c:24: > /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/hconfig.j:25: hconfig.h: > No such file or directory > In file included from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/sys > tem.j:25, > from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/pro > j.h:32, > from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/fin > i.c:24: > /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/system.h:348: conflicting t > ypes for `sys_errlist' > /usr/include/stdio.h:225: previous declaration of `sys_errlist' > /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/system.h:394: syntax error > before `PVPROTO' > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/cc/f771. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > -- > Jos Backus _/ _/_/_/ "Reliability means never > _/ _/ _/ having to say you're sorry." > _/ _/_/_/ -- D. J. Bernstein > _/ _/ _/ _/ > Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; > > 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 Thu Dec 16 15:48:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by hub.freebsd.org (Postfix) with ESMTP id BD8B515663 for ; Thu, 16 Dec 1999 15:47:45 -0800 (PST) (envelope-from akm@mail.theinternet.com.au) Received: (from akm@localhost) by mail.theinternet.com.au (8.9.3/8.9.3) id JAA67579; Fri, 17 Dec 1999 09:59:58 +1000 (EST) (envelope-from akm) From: Andrew Kenneth Milton Message-Id: <199912162359.JAA67579@mail.theinternet.com.au> Subject: Re: Serious server-side NFS problem In-Reply-To: <199912162024.NAA73705@harmony.village.org> from Warner Losh at "Dec 16, 1999 1:24:37 pm" To: imp@village.org (Warner Losh) Date: Fri, 17 Dec 1999 09:59:58 +1000 (EST) Cc: phk@critter.freebsd.dk, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 +----[ Warner Losh ]--------------------------------------------- | | There is one problem with this. The amount of uptime isn't the same | as the amount of time since the machine booted. How can this happen? | When a laptop suspends, it doesn't update the update while it is | asleep, nor does it update the uptime by the amount of time that has | been slept. IS this a bug in the apm code? The machine is neither up or down until you collapse the even horizon and unsuspend it to observe its state d8) -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | ACN: 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 15:51:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 09AC614E30 for ; Thu, 16 Dec 1999 15:51:20 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA02071; Thu, 16 Dec 1999 15:54:42 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912162354.PAA02071@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: David Gilbert Cc: freebsd-current@freebsd.org Subject: Re: AMI MegaRAID datapoint. In-reply-to: Your message of "Thu, 16 Dec 1999 10:52:58 EST." <14425.2778.943367.365945@trooper.velocet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Dec 1999 15:54:42 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have the Enterprise 1400 Megaraid adapter with (currently 16M) on > it. I have tested the various modes of operation (different raid > levels and striping) and find it to be working well. My LVD array > consists of 8 18G Quamtum IV's. > > Now... using vinum and either the 2940U2W (Adaptec LVD) or the TekRAM > (NCR) LVD (using the sym0 device) gives 30 to 35 M/s under RAID-5. > This is impressive and subject to the bug that I mentioned in -STABLE > which still hasn't been found. It's pretty good, that's for sure. 8) > The AMI MegaRAID 1400 delivers between 16.5 and 19 M/s (the 19M/s > value is somewhat contrived --- using 8 bonnies in parrallel and then > summing their results --- which is not 100% valid)... but the MegaRAID > appears to be stable. Hmm. Those numbers aren't so great though. I'd be interested to know how busy the controller is during your test (use systat -vmstat 1 and look at the amrd0 device), as well as how you've configured it. AMI's default configurations for those controllers is wildly inconsistent between one BIOS version and the next. > I would like to know, however, if there are any planned or > in-the-works utility programs for the amr device. In particular, a > program to print the state of the array would be useful. I'm currently waiting on AMI for more documentation, at which point there will indeed be more monitoring and control facilities added. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Thu Dec 16 16: 8:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id E5FB315121 for ; Thu, 16 Dec 1999 16:07:53 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA02326; Thu, 16 Dec 1999 16:10:40 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912170010.QAA02326@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tom Bartol Cc: freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-reply-to: Your message of "Thu, 16 Dec 1999 12:37:02 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Dec 1999 16:10:40 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On Thu, 16 Dec 1999, Warner Losh wrote: > > > In message <16722.945365564@critter.freebsd.dk> Poul-Henning Kamp writes: > > : If people do a "settimeofday" we change the boot time since the > > : amount of time we've been up *IS* known for sure, whereas the boottime > > : is only an estimate. > > > > There is one problem with this. The amount of uptime isn't the same > > as the amount of time since the machine booted. How can this happen? > > When a laptop suspends, it doesn't update the update while it is > > asleep, nor does it update the uptime by the amount of time that has > > been slept. IS this a bug in the apm code? > > IIRC it does update uptime properly after a suspend in 2.2.8 but does not > do so in 3.X and -current on my ThinkPad 770. Not updating uptime to account for time slept is the "correct" behaviour given the way the kernel currently thinks about things, where "correct" is defined as "most survivable". -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Thu Dec 16 16:21:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id C949315667 for ; Thu, 16 Dec 1999 16:21:55 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id TAA10464; Thu, 16 Dec 1999 19:21:37 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id TAA01416; Thu, 16 Dec 1999 19:21:07 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 16 Dec 1999 19:21:07 -0500 (EST) To: Matthew Dillon Cc: Kevin Day , phk@critter.freebsd.dk (Poul-Henning Kamp), freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-Reply-To: <199912160801.AAA50074@apollo.backplane.com> References: <199912160758.BAA87332@celery.dragondata.com> <199912160801.AAA50074@apollo.backplane.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14425.33053.359447.429215@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > We're already testing a patch. Thanks again Matt! The latest rev of nfs_serv.c has fixed it. I'm now seeing FreeBSD UDP client read bandwidth of 9.2MB/sec & write bandwidth of 10.9MB/sec. Solaris clients are writing over TCP at 10.1MB/sec (and that is across a router!) and are reading at 7MB/sec. Awesome! Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 17:16:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from bsd1.gccs.com.au (gw-telstra.gccs.com.au [203.17.152.1]) by hub.freebsd.org (Postfix) with ESMTP id 4B9D914FA3 for ; Thu, 16 Dec 1999 17:16:43 -0800 (PST) (envelope-from starr3@gccs.com.au) Received: from LB50X (LB50X.gccs.com.au [203.17.152.10]) by bsd1.gccs.com.au (8.9.1/8.9.1) with SMTP id LAA18365; Fri, 17 Dec 1999 11:16:06 +1000 (EST) Message-ID: <00d701bf482c$4c64f970$0a9811cb@gccs.com.au> From: "Harry Starr" To: "Leif Neland" , , "FreeBSD Current" References: <19991215193013.B006D38E5@hcswork.hcs.de> <01b201bf4752$8bd2c680$0e00a8c0@neland.dk> Subject: Re: tagged openings now 31, 25, 2; ncr0: queue empty. Date: Fri, 17 Dec 1999 11:16:06 +1000 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 5.00.2919.5600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had similar problems with Conner drives -- they have bugs in their microcode. You need to disable tagged queueing for these drives by adding a QUIRK to cam_xpt.c Harry. ----- Original Message ----- From: "Leif Neland" To: ; "FreeBSD Current" Sent: Thursday, December 16, 1999 9:11 AM Subject: Sv: tagged openings now 31, 25, 2; ncr0: queue empty. > > ----- Original Message ----- > From: Hellmuth Michaelis > To: FreeBSD Current > Sent: Wednesday, December 15, 1999 8:30 PM > Subject: tagged openings now 31, 25, 2; ncr0: queue empty. > > > and then scrolling: > > > > ncr0: queue empty. > > ncr0: queue empty. > > ncr0: queue empty. > > .... > > > > over and over the console screen. The only way to get out of this was to > > reboot. > > > > Now i am concerned :-) > > > > What is happening there ? Is the drive going bad ? > > I've had the same thing happening here. I've since that removed (well, just not mounting) a drive, which gave some reading errors, and have installed a newer current, and I haven't seen it happening since. > > Leif > > > > > 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 Thu Dec 16 18:28: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id CBA3E15043 for ; Thu, 16 Dec 1999 18:28:06 -0800 (PST) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-r-0.1-19990829) with ESMTP id LAA92172; Fri, 17 Dec 1999 11:28:00 +0900 (JST) Date: Fri, 17 Dec 1999 11:28:00 +0900 Message-ID: <14425.40880.275206.81928B@rina.r.dl.itc.u-tokyo.ac.jp> From: Seigo Tanimura To: julian@whistle.com Cc: current@freebsd.org Subject: Re: pnp, sound and LINT in -current In-Reply-To: In your message of "Wed, 15 Dec 1999 15:00:34 -0800 (PST)" References: Cc: Seigo Tanimura User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 15 Dec 1999 15:00:34 -0800 (PST), Julian Elischer said: Julian> however LINT doesn't help because it still has comments refering Julian> to 'enable pnp'. Are these old? and if not, how do I now do this? Yes. Also, pcm(4) no longer needs to mention pnp(4). Could anyone handle pcm(4) while I fix LINT and go out in half an hour? -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 18:56:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 7F2E615011; Thu, 16 Dec 1999 18:56:43 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id VAA12645; Thu, 16 Dec 1999 21:56:41 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id VAA01692; Thu, 16 Dec 1999 21:56:10 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 16 Dec 1999 21:56:10 -0500 (EST) To: Julian Elischer Cc: current@freebsd.org, sef@freebsd.org Subject: Re: linux /proc and vmware. In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14425.42251.714289.32020@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > > might I suggest that we make a decision to allow procfs to be mounted with > a -linux flag and act more like the linux programs expect.? > (particularly we could mount it at /compat/linux/proc with the -linux > flag). > That would be wonderful. I'd also like to see us have enough information in /proc to be able to divorce ps & friends from libkvm. It would be nice to be able to have most tools continue to work if you have mismatched kernels & userlands. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 19:11: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 350B71568D; Thu, 16 Dec 1999 19:11:02 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id WAA15269; Thu, 16 Dec 1999 22:09:03 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Thu, 16 Dec 1999 22:09:02 -0500 (EST) From: Chuck Robey To: Andrew Gallatin Cc: Julian Elischer , current@FreeBSD.ORG, sef@FreeBSD.ORG Subject: Re: linux /proc and vmware. In-Reply-To: <14425.42251.714289.32020@grasshopper.cs.duke.edu> 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, 16 Dec 1999, Andrew Gallatin wrote: > > Julian Elischer writes: > > > > might I suggest that we make a decision to allow procfs to be mounted with > > a -linux flag and act more like the linux programs expect.? > > (particularly we could mount it at /compat/linux/proc with the -linux > > flag). > > > > That would be wonderful. > > I'd also like to see us have enough information in /proc to be able to > divorce ps & friends from libkvm. It would be nice to be able to have > most tools continue to work if you have mismatched kernels & > userlands. I thought the work was going in precisely the opposite way, so that jail could work without any visibility to /proc. ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 19:28:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4972C152FD for ; Thu, 16 Dec 1999 19:28:36 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA57721; Thu, 16 Dec 1999 19:28:34 -0800 (PST) (envelope-from dillon) Date: Thu, 16 Dec 1999 19:28:34 -0800 (PST) From: Matthew Dillon Message-Id: <199912170328.TAA57721@apollo.backplane.com> To: Andrew Gallatin Cc: Kevin Day , phk@critter.freebsd.dk (Poul-Henning Kamp), freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem References: <199912160758.BAA87332@celery.dragondata.com> <199912160801.AAA50074@apollo.backplane.com> <14425.33053.359447.429215@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Matthew Dillon writes: : : > We're already testing a patch. : :Thanks again Matt! : :The latest rev of nfs_serv.c has fixed it. : :I'm now seeing FreeBSD UDP client read bandwidth of 9.2MB/sec & write :bandwidth of 10.9MB/sec. Solaris clients are writing over TCP at :10.1MB/sec (and that is across a router!) and are reading at 7MB/sec. : :Awesome! : :Thanks, : :Drew : :------------------------------------------------------------------------------ :Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin :Duke University Email: gallatin@cs.duke.edu Those are really quite excellent results! Linux eat your heart out! I get 9.5 to 10.5 MBytes/sec on my half-duplex network between two fast machines. I tend to get between 7.5 and 9 MBytes/sec when using slower (200-300 MHz) clients. That's *with* packet loss (for some reason when my fxp ethernets pump data out that quickly they tend to cause packet loss in other parts of my HUBed network, which I find quite annoying). We've solved most of the performance issues, but NFS is still eating a little too much cpu for my tastes. Unfortunately it is getting to the point where a significant portion of the performance loss is occuring in the network driver itself. Some of my cards eat 25% of the cpu just in 'interrupt' (at 10 MBytes/sec half duplex), not even counting the TCP or UDP stacks. This is mainly due to the MTU being too small (i.e. packet fragmentation takes it toll on the interrupt subsystem). SCSI cards are way ahead of NIC cards in regards to reducing interrupt overhead (though gigabit NICs have caught up some). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 19:56:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 2E6871504D for ; Thu, 16 Dec 1999 19:56:33 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id UAA20500; Thu, 16 Dec 1999 20:55:54 -0700 (MST) (envelope-from ken) Date: Thu, 16 Dec 1999 20:55:54 -0700 From: "Kenneth D. Merry" To: Matthew Dillon Cc: Andrew Gallatin , Kevin Day , Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem Message-ID: <19991216205554.A20410@panzer.kdm.org> References: <199912160758.BAA87332@celery.dragondata.com> <199912160801.AAA50074@apollo.backplane.com> <14425.33053.359447.429215@grasshopper.cs.duke.edu> <199912170328.TAA57721@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912170328.TAA57721@apollo.backplane.com>; from dillon@apollo.backplane.com on Thu, Dec 16, 1999 at 07:28:34PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 19:28:34 -0800, Matthew Dillon wrote: > :Matthew Dillon writes: > : > : > We're already testing a patch. > : > :Thanks again Matt! > : > :The latest rev of nfs_serv.c has fixed it. > : > :I'm now seeing FreeBSD UDP client read bandwidth of 9.2MB/sec & write > :bandwidth of 10.9MB/sec. Solaris clients are writing over TCP at > :10.1MB/sec (and that is across a router!) and are reading at 7MB/sec. [ ... ] > :Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > :Duke University Email: gallatin@cs.duke.edu > > Those are really quite excellent results! Linux eat your heart out! I > get 9.5 to 10.5 MBytes/sec on my half-duplex network between two fast > machines. I tend to get between 7.5 and 9 MBytes/sec when using slower > (200-300 MHz) clients. That's *with* packet loss (for some reason when > my fxp ethernets pump data out that quickly they tend to cause packet > loss in other parts of my HUBed network, which I find quite annoying). > > We've solved most of the performance issues, but NFS is still > eating a little too much cpu for my tastes. Unfortunately it is getting to > the point where a significant portion of the performance loss is occuring > in the network driver itself. Some of my cards eat 25% of the cpu just > in 'interrupt' (at 10 MBytes/sec half duplex), not even counting the > TCP or UDP stacks. This is mainly due to the MTU being too small (i.e. > packet fragmentation takes it toll on the interrupt subsystem). SCSI > cards are way ahead of NIC cards in regards to reducing interrupt > overhead (though gigabit NICs have caught up some). Another advantage with gigabit ethernet is that if you can do jumbo frames, you can fit an entire 8K NFS packet in one frame. I'd like to see NFS numbers from two 21264 Alphas with GigE cards, zero copy, checksum offloading and a big striped array on one end at least. I bet you could get pretty good performance with a setup like that. (Now don't anybody go out and do it unless you really want to spend the time.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 20:59:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.netaxs.com (mail.netaxs.com [207.8.186.26]) by hub.freebsd.org (Postfix) with ESMTP id 106C715216 for ; Thu, 16 Dec 1999 20:59:49 -0800 (PST) (envelope-from bleez@netaxs.com) Received: from dyn-11.blackbox-2.netaxs.com (dyn-11.blackbox-2.netaxs.com [207.106.60.11]) by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id XAA11186 for ; Thu, 16 Dec 1999 23:59:45 -0500 (EST) Date: Thu, 16 Dec 1999 23:59:44 -0500 (EST) From: Bryan Liesner X-Sender: root@gravy.kishka.net Reply-To: Bryan Liesner To: freebsd-current@freebsd.org Subject: Avance Asound 110 patch for sbc.c 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 A few days back my Avance Asound stopped working. The probe would fail (sorry, this is from memory): sbc0: probe_and_attach returned 6 I found a slight error in sbc.c and here's a working patch: --- /sys/dev/sound/isa/sbc.c Sat Dec 11 21:30:19 1999 +++ sbc.c Thu Dec 16 23:42:43 1999 @@ -184,7 +184,7 @@ {0x45008c0e, "Creative SB AWE64"}, /* CTL0045 */ {0x01000000, "Avance Asound 100"}, - {0x01100001, "Avance Asound 110"}, + {0x01100000, "Avance Asound 110"}, {0x01200001, "Avance Logic ALS120"}, {0x68187316, "ESS ES1868"}, /* ESS1868 */ I was happy to hear that nice "pop" when I rebooted. -Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 22:32: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id DC24414FA2 for ; Thu, 16 Dec 1999 22:31:59 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id WAA69960; Thu, 16 Dec 1999 22:30:45 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199912170630.WAA69960@troutmask.apl.washington.edu> Subject: Re: pnp, sound and LINT in -current In-Reply-To: <14425.40880.275206.81928B@rina.r.dl.itc.u-tokyo.ac.jp> from Seigo Tanimura at "Dec 17, 1999 11:28:00 am" To: tanimura@r.dl.itc.u-tokyo.ac.jp (Seigo Tanimura) Date: Thu, 16 Dec 1999 22:30:45 -0800 (PST) Cc: julian@whistle.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Seigo Tanimura wrote: > On Wed, 15 Dec 1999 15:00:34 -0800 (PST), > Julian Elischer said: > > Julian> however LINT doesn't help because it still has comments refering > Julian> to 'enable pnp'. Are these old? and if not, how do I now do this? > > Yes. Also, pcm(4) no longer needs to mention pnp(4). Could anyone > handle pcm(4) while I fix LINT and go out in half an hour? > pcm(4) describes Luigi's old pcm driver. Tne newpcm driver is different and the info pcm(4) does not necessarily apply. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 23:22:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 5569314F50 for ; Thu, 16 Dec 1999 23:22:10 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA04753; Fri, 17 Dec 1999 08:22:03 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912170722.IAA04753@freebsd.dk> Subject: Re: ATA driver problem?? (lost disk contact) In-Reply-To: <19991216165055.A320@tar.com> from "Richard Seaman, Jr." at "Dec 16, 1999 04:50:55 pm" To: dick@tar.com (Richard Seaman, Jr.) Date: Fri, 17 Dec 1999 08:22:03 +0100 (CET) Cc: djb@Wit389306.student.utwente.nl, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Richard Seaman, Jr. wrote: Yup, sounds like the problem some are seing, now I wonder why I havn't seen it on any of the IBM disks I've access to, hmm... It apparantly can't be disabled, but I'll try to figure out if I can detect when the drive is in this mode, or put it in standby mode and back again when there is nothing else to do, that should reset the timer... > On Thu, Dec 16, 1999 at 09:25:11AM +0100, Soren Schmidt wrote: > > > There is this thing with the IBM's doing some headcleaning stuff once > > a day/week, but I've never seen any of my IBM's do that (I got plenty > > of them). I'll try to get more info on that from IBM... > > Check http://www.storage.ibm.com/techsup/hddtech/prodspec/djna_spw.pdf > > On page 99 it says: > > 10.12 Automatic Drive Maintenance (ADM) > > ADM function is equipped to maintain the reliability even in continuous usage. > ADM function is to go into Standby mode automatically after detecting idle mode > at intervals of 6 days. > > This function is always enabled regardless of Standby Timer value. The detail > of Standby Timer is described in 12.6, "Idle (E3h/97h)" on page 122, and 12.32, > "Standby (E2h/96h)" on page 171. > > The 6 days counter is reset at the following. > Power on Ready > Entering Standby mode by Standby Command > Entering Standby mode by Standby Timer > > Both Soft Reset and Hard Reset do not disturb the spin down of ADM. > > If a command is received during spin down of ADM, the drive quits the spin down > and tries to complete the command as soon as possible. > In case the spin down of ADM is disturbed by a command, it is retried 12 hours > later. For timeout concern, refer to 13.0, "Timeout Values" on page 185. -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 16 23:25:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id DD78915697 for ; Thu, 16 Dec 1999 23:25:41 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id GAA02611; Fri, 17 Dec 1999 06:52:21 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id HAA46224; Fri, 17 Dec 1999 07:43:06 +0100 (CET) (envelope-from wilko) Date: Fri, 17 Dec 1999 07:43:06 +0100 From: Wilko Bulte To: Chris Costello Cc: Mark Newton , Peter Jeremy , Donn Miller , current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991217074306.A46207@yedi.iaf.nl> References: <2177.945155945@zippy.cdrom.com> <3855F364.E66EC87B@cvzoom.net> <99Dec15.073843est.40325@border.alcanet.com.au> <19991215083352.B3500@internode.com.au> <19991215000600.C77327@yedi.iaf.nl> <19991214174432.Y868@holly.calldei.com> <19991215193424.C447@yedi.iaf.nl> <19991215173113.M868@holly.calldei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991215173113.M868@holly.calldei.com>; from chris@calldei.com on Wed, Dec 15, 1999 at 05:31:13PM -0600 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 05:31:13PM -0600, Chris Costello wrote: > On Wed, Dec 15, 1999, Wilko Bulte wrote: > > Click-click, hosed up beyond repair. What I mean to say is that > > GUI != easy to administer. M$ has plenty of examples available. > > There's a difference between useful GUI design and backwards > braindead inconsistant GUI design. Guess which Microsoft is > using. Definitely. But as the Unix has yet to come up with something better... [GUI wars etc, no real standards, etc] -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 0:48: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id BEAB614F7E for ; Fri, 17 Dec 1999 00:48:00 -0800 (PST) (envelope-from vallo@solaris.matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id EAB352CE53 for ; Fri, 17 Dec 1999 10:47:56 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 1A97BF7; Fri, 17 Dec 1999 10:47:59 +0200 (EET) Date: Fri, 17 Dec 1999 10:47:59 +0200 From: Vallo Kallaste To: freebsd-current@freebsd.org Subject: Weird story with dump | restore Message-ID: <19991217104758.A53242@myhakas.matti.ee> Reply-To: vallo@matti.ee Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello ! Something is weird with standard dump/restore procedure which I've always used to relocate my filesystems. I'm using 4.0-19991208-CURRENT on two machines, one is my home machine with SiS 5591 ATA controller and the other one has Intel PIIX. Home machine has disk pair Seagate 6.4GB and IBM 37.5GB, the other one Quantum Fireball 1GB and Fujitsu 3.2GB. First pair is in standard WDMA2 mode, the other one in PIO as per ata driver boot messages. Both setups have disks on separate channels, disks are masters. Problem: I'm trying to use dump/restore pair piped together to relocate / and /usr filesystems to the secondary master disk. In the first case from Seagate to IBM and second case from Quantum to Fujitsu. Target disks have innocent filesystems just created. On the home machine with SiS controller the overall dump/restore process runs smoothly until phase IV when it will do regular file dumping. Now the process stops regularly for about 10 seconds, then runs for 4 seconds or so. The process just runs, stops, runs, stops and so forth. Intervals aren't always same, but the stopped period is always longer. I dropped to in-kernel debugger and used ps to view process states. The dump wmesg column showed pipdwt and sbwait, for restore it's nbufkv. There's five lines for dump overall, the not mentioned were in wait or pause state. After viewing ps in debugger I continued the usual run and launced top. Everything stops while the restore process enters into nbuf?? state, top can't refresh screen etc, but everything continues after stopped period so I can see the restore process state changing. For the record, at last I used pax to relocate the data on the /usr filesystem and pax showed exactly same behavior. Difference was in reversed stop/run sequence, runs lasted lot longer than stopped states, pax even run for ten minutes, then stopped for about 13 seconds. The wd driver has same behavior, kernel with wd driver has same configuration as ata one. This claim is only true for SiS 5591 case as I've not tried yet with other machine. For other machine everything is same except machine stops completely. I've tried to disable softupdates on both source and target filesystems but no difference. All procedures were done in single user mode. It's very annoying, I have only fair experiences with dump/restore back to the 2.2.2 days until now. machine i386 ident Vokk maxusers 32 makeoptions CONF_CFLAGS=-fno-builtin #Don't allow use of memcmp, etc. makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options PQ_NORMALCACHE # color for 256k/16k cache cpu I586_CPU # aka Pentium Pro(tm) options COMPAT_43 options SYSVSHM options SYSVSEM options SYSVMSG options MD5 options DDB options DDB_UNATTENDED options INET #Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device loop #Network loopback device pseudo-device bpf #Berkeley packet filter options ICMP_BANDLIM options FFS #Fast filesystem options NFS #Network File System options CD9660 #ISO 9660 filesystem options PROCFS #Process filesystem options FFS_ROOT #FFS usable as root device options SOFTUPDATES options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L pseudo-device pty #Pseudo ttys pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. options MSGBUF_SIZE=40960 controller isa0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device vga0 at isa? port ? conflicts pseudo-device splash device sc0 at isa? options MAXCONS=8 # number of virtual consoles options SC_HISTORY_SIZE=800 # number of history buffer lines device npx0 at nexus? port IO_NPX flags 0x0 irq 13 controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives options ATA_ENABLE_ATAPI_DMA controller fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 controller miibus0 controller pci0 device vr0 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? device ppc0 at isa? port? irq 7 options CLK_CALIBRATION_LOOP options CLK_USE_I8254_CALIBRATION options CLK_USE_TSC_CALIBRATION -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 0:52: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles504.castles.com [208.214.165.68]) by hub.freebsd.org (Postfix) with ESMTP id F30B714F2F for ; Fri, 17 Dec 1999 00:52:01 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA00646; Fri, 17 Dec 1999 00:55:26 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912170855.AAA00646@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-reply-to: Your message of "Thu, 16 Dec 1999 19:28:34 PST." <199912170328.TAA57721@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Dec 1999 00:55:26 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We've solved most of the performance issues, but NFS is still > eating a little too much cpu for my tastes. Unfortunately it is getting to > the point where a significant portion of the performance loss is occuring > in the network driver itself. Some of my cards eat 25% of the cpu just > in 'interrupt' (at 10 MBytes/sec half duplex), not even counting the > TCP or UDP stacks. This is mainly due to the MTU being too small (i.e. > packet fragmentation takes it toll on the interrupt subsystem). SCSI > cards are way ahead of NIC cards in regards to reducing interrupt > overhead (though gigabit NICs have caught up some). Actually, I'm not sure I buy this at all. Both the EtherExpress and 3C905 families give less than one interrupt per datagram, and the other overheads on them are comparably small. I think you'll want to do some profiling before getting too concerned about the network drivers themselves; gigabit hardware isn't really any lighter on the CPU than good 100Mbps hardware, and we can handle better than 400MBps UDP inbound on a reasonable (400MHz) system right now. (Lots better with jumbo frames.) My guesses (based on some of the profiling that Bill Paul did) would be the IP and UDP checksum guessing, but more that I think you'll find that a considerable amount of the inbound NFS traffic handling is actually performed in the interrupt context (ie. I don't think that stuff is being handed off to a softnet handler), blowing out the numbers a bit. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Dec 17 1:21:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id F2D9D14EB1; Fri, 17 Dec 1999 01:21:13 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id KAA20169; Fri, 17 Dec 1999 10:20:38 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Chuck Robey Cc: Andrew Gallatin , Julian Elischer , current@FreeBSD.ORG, sef@FreeBSD.ORG Subject: Re: linux /proc and vmware. In-reply-to: Your message of "Thu, 16 Dec 1999 22:09:02 EST." Date: Fri, 17 Dec 1999 10:20:38 +0100 Message-ID: <20167.945422438@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Chuck Rob ey writes: >> I'd also like to see us have enough information in /proc to be able to >> divorce ps & friends from libkvm. It would be nice to be able to have >> most tools continue to work if you have mismatched kernels & >> userlands. Such transparancy can be made with with either /proc or sysctl. >I thought the work was going in precisely the opposite way, so that jail >could work without any visibility to /proc. Well, if you want to run linux binaries which insist on peeking into /proc you will need to mount a procfs there. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 1:27:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 0A66C1510F for ; Fri, 17 Dec 1999 01:27:08 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id KAA20282; Fri, 17 Dec 1999 10:26:51 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Soren Schmidt Cc: dick@tar.com (Richard Seaman, Jr.), djb@Wit389306.student.utwente.nl, freebsd-current@FreeBSD.ORG Subject: Re: ATA driver problem?? (lost disk contact) In-reply-to: Your message of "Fri, 17 Dec 1999 08:22:03 +0100." <199912170722.IAA04753@freebsd.dk> Date: Fri, 17 Dec 1999 10:26:50 +0100 Message-ID: <20280.945422810@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912170722.IAA04753@freebsd.dk>, Soren Schmidt writes: >It seems Richard Seaman, Jr. wrote: > >Yup, sounds like the problem some are seing, now I wonder why I >havn't seen it on any of the IBM disks I've access to, hmm... > >It apparantly can't be disabled, but I'll try to figure out if >I can detect when the drive is in this mode, or put it in >standby mode and back again when there is nothing else to do, >that should reset the timer... Probably the best thing to do would be to write a "atamaint" program and schedule a cronjob to run it at 05:00 every morning or something. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 1:42:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 58D6C14FA6 for ; Fri, 17 Dec 1999 01:42:24 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA46687; Fri, 17 Dec 1999 09:52:20 GMT (envelope-from dfr@nlsystems.com) Date: Fri, 17 Dec 1999 09:52:20 +0000 (GMT) From: Doug Rabson To: Matthew Dillon Cc: Andrew Gallatin , freebsd-current@freebsd.org Subject: Re: Serious server-side NFS problem In-Reply-To: <199912160600.WAA47882@apollo.backplane.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, 15 Dec 1999, Matthew Dillon wrote: > Here's a general update on this bug report to -current. It took all day > but I was finally able to reproduce Andrew's bug. > > You guys are going to *love* this. > > NFS uses the kernel 'boottime' structure to generate its version id. > Now normally you might believe that this structure, once set, will > never change. The authors of NFS certainly make that assumption! > > No such luck. If you happen to be running, oh, xntpd for example, > the kernel adjusts the boottime structure to take into account time > changes, including PLL changes so, in fact, the boottime structure > can change quite often - once each tick, in fact. Nice catch, Matt. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 2:37:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 77D5B14FD1 for ; Fri, 17 Dec 1999 02:37:44 -0800 (PST) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 7E5632CE49 for ; Fri, 17 Dec 1999 12:37:39 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 2FAFE10C; Fri, 17 Dec 1999 12:37:42 +0200 (EET) Date: Fri, 17 Dec 1999 12:37:42 +0200 From: Vallo Kallaste To: freebsd-current@freebsd.org Subject: Re: Weird story with dump | restore Message-ID: <19991217123742.A70473@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <19991217104758.A53242@myhakas.matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <19991217104758.A53242@myhakas.matti.ee>; from Vallo Kallaste on Fri, Dec 17, 1999 at 10:47:59AM +0200 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 17, 1999 at 10:47:59AM +0200, Vallo Kallaste wrote: [snip] > It's very annoying, I have only fair experiences with dump/restore back > to the 2.2.2 days until now. Sorry for the long post and partially? false alert. Something in my mind waked up and I checked what type of bsize and fsize the other machines have. Now I remember a little discussion in the cvs-all list, at that time phk committed something about default flags for newfs or so and there was rgrimes involved into discussion. He was suggesting following flags for filesystem creation for newer, bigger disks: newfs -b16384 -f2048 -u2048 -c128 -i4096 I've used them since with no problems whatsoever. Now I got the dump done on the machine with default filesystem, the bugger is unusual filesystem I guess. Is it expected behavior? Does anybody know why it can't be done? -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 2:52:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl4.philips.com (gw-nl4.philips.com [192.68.44.36]) by hub.freebsd.org (Postfix) with ESMTP id A175E15045 for ; Fri, 17 Dec 1999 02:52:43 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl4.philips.com with ESMTP id LAA20739 for ; Fri, 17 Dec 1999 11:52:41 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl4.philips.com via mwrap (4.0a) id xma020721; Fri, 17 Dec 99 11:52:42 +0100 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with SMTP id LAA11750 for ; Fri, 17 Dec 1999 11:52:38 +0100 (MET) Received: (qmail 76210 invoked by uid 666); 17 Dec 1999 10:53:34 -0000 Date: Fri, 17 Dec 1999 11:53:34 +0100 From: Jos Backus To: freebsd-current@FreeBSD.ORG Subject: Re: make world broken Message-ID: <19991217115334.B11849@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19991216231609.A90209@hal.mpn.cp.philips.com> <385AC788.56641747@heartland.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <385AC788.56641747@heartland.ab.ca>; from dkwiebe@heartland.ab.ca on Fri, Dec 17, 1999 at 04:30:16PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 17, 1999 at 04:30:16PM -0700, Darren Wiebe wrote: > I just built the world from sources about 3-4 hours ago. It was all > great. Fwiw, I just got the same error on another system, cvsupped this morning. -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ 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 Fri Dec 17 3:33:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.195]) by hub.freebsd.org (Postfix) with ESMTP id 719FE14E98; Fri, 17 Dec 1999 03:33:10 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id MAA03192; Fri, 17 Dec 1999 12:33:07 +0100 (CET) Date: Fri, 17 Dec 1999 12:33:07 +0100 From: Martin Cracauer To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: sh(1) broken caching [was: Re: Broken sh(1)?] Message-ID: <19991217123306.A3177@cons.org> References: <712.945183175@axl.noc.iafrica.com> <38565DEA.4487DF53@scc.nl> <19991216154020.A41154@cons.org> <19991216091832.A74110@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19991216091832.A74110@dragon.nuxi.com>; from David O'Brien on Thu, Dec 16, 1999 at 09:18:33AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <19991216091832.A74110@dragon.nuxi.com>, David O'Brien wrote: > On Thu, Dec 16, 1999 at 03:40:20PM +0100, Martin Cracauer wrote: > > You can also fool sh into running the *wrong* binary if if you have > > two in showdowed paths: > > pdksh does not suffer from either this problem or the problem that > started this thread (and does not coredump). We've shown in the past > that pdksh is actually smaller (when linked statically) than ash. > > I still think we should *seriously* consider switching to pdksh. As I said before, pdksh has other bugs. Try this in pdksh: #! /bin/sh emacs -nw /tmp/bla mv /tmp/bla /tmp/bla2 Two times: - first run, do not hit C-g in emacs - second run, use C-g in emacs In the second run, the `mv` will not be executed, while in the first it will. This is not a bug, but a design decision in pdksh (see also my homepage - sigint.html). It's poor man's workaround about programs that don't exit with a proper signal status when they exit on a signal. Also we would loose all the PRs we received in the past. This testing effort by our user base is a valuable resource. From the tests I ran on all available shells, only bash2 is considerably better than the other shells, pdksh has other bugs than our ash, not less. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 3:58:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as12-077.rp-plus.de [149.221.242.77]) by hub.freebsd.org (Postfix) with ESMTP id CA55A15727 for ; Fri, 17 Dec 1999 03:58:43 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 3300CAB7F for ; Fri, 17 Dec 1999 12:37:10 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id MAA01437 for freebsd-current@FreeBSD.ORG; Fri, 17 Dec 1999 12:36:52 +0100 (CET) (envelope-from alex) Date: Fri, 17 Dec 1999 12:36:52 +0100 From: Alexander Langer To: freebsd-current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? Message-ID: <19991217123652.A684@cichlids.cichlids.com> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199912151624.RAA01525@dorifer.heim3.tu-clausthal.de> <99Dec17.080227est.40335@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s" X-Mailer: Mutt 1.0i In-Reply-To: <99Dec17.080227est.40335@border.alcanet.com.au>; from peter.jeremy@alcatel.com.au on Fri, Dec 17, 1999 at 08:10:54AM +1100 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Thus spake Peter Jeremy (peter.jeremy@alcatel.com.au): > -rwxr-xr-x 1 jeremyp inplat 96509 Dec 17 08:08 minigzip > % cc -O -o minigzip minigzip.c /usr/lib/libz.a What about stripping? root:/usr/src/usr.bin/minigzip $ ls -l minigzip -rwxr-xr-x 1 root bin 96921 17 Dez 12:35 minigzip root:/usr/src/usr.bin/minigzip $ strip minigzip root:/usr/src/usr.bin/minigzip $ ls -l minigzip -rwxr-xr-x 1 root bin 90044 17 Dez 12:35 minigzip root:/usr/src/usr.bin/minigzip $ cc -O -o minigzip minigzip.o /usr/lib/libz.a root:/usr/src/usr.bin/minigzip $ ls -l minigzip -rwxr-xr-x 1 root bin 48699 17 Dez 12:36 minigzip root:/usr/src/usr.bin/minigzip $ strip minigzip root:/usr/src/usr.bin/minigzip $ ls -l minigzip -rwxr-xr-x 1 root bin 45240 17 Dez 12:36 minigzip Alex --=20 I doubt, therefore I might be.=20 --SLDf9lqlvOQaIe6s Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (FreeBSD) Comment: For info see http://www.gnupg.org iQEVAwUBOFogUrRIIUSeqRcRAQFxrQf+JdWsx8dneKzUzg5Y7SZw2k3XNZykviih eUpFp9PCtnrrpZCvSdk2+UKIsNjfCe4gm2dUdBk+3uo5lvbiRE/YgGKVAHfRhvfA nmEpzK/X5biz0aWU/Vrbdahs72KxAB3I5w2je7PbQYczGN8ZQDSCCi4BulzAPQWX 6XnpggIBRicZWuMSNPiWhDmbSRL0PNxhN8iUoNSQdAswUOaUnRKF6gsZKgrO0ovZ 3flr8IekFY7XpTfIrKs/OrONhlzEYRh00Ycn+2LuAUVeAgWNEA8MnQcXpCx6DOdd yEFMA5vDR5LhLfbee6ARV0HnVigcqdf18RosdWnD7EhFupXI39uzdg== =2qvx -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 5:11:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from chmls11.mediaone.net (chmls11.mediaone.net [24.128.1.112]) by hub.freebsd.org (Postfix) with ESMTP id DA27915045 for ; Fri, 17 Dec 1999 05:11:52 -0800 (PST) (envelope-from veldy@visi.com) Received: from barley (h-181-234.mn.mediaone.net [209.32.181.234]) by chmls11.mediaone.net (8.8.7/8.8.7) with SMTP id IAA18476 for ; Fri, 17 Dec 1999 08:11:49 -0500 (EST) Message-ID: <001001bf4890$a45fde60$0100a8c0@veldy.org> From: "Thomas T. Veldhouse" To: "FreeBSD-Current" Subject: ATA Problem? Fallback to PIO Date: Fri, 17 Dec 1999 07:14:24 -0600 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 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to be having a problem with the my Western Digital Caviar 6.4GB UDMA33 (5400RPM?) Hard Drive. I get the following error: ad0: ATA-4 disk at ata0 as master ad0: 19092MB (39102336 sectors), 38792 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad1: ATA-4 disk at ata0 as slave ad1: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 . . . Mounting root from ufs:/dev/ad1s2a ad1: UDMA CRC WRITE ERROR blk# 1999 retrying ad1: UDMA CRC WRITE ERROR blk# 1999 retrying ad1: UDMA CRC WRITE ERROR blk# 1999 retrying ad1: UDMA CRC WRITE ERROR blk# 1999 falling back to PIO mode I do not have any problems with this drive under Windows98, WindowsNT, FreeBSD3.x or Linux. Never an error reported before. What does this mean? I am using the GENERIC kernel from the FreeBSD 4.0-19991215-CURRENT #0: Wed Dec 15 16:26:48 GMT 1999 snapshot. I have not had time to recompile as of yet. I do know that this drive is partitioned funny with ad1s1 as a 2000MB FAT16 partition and the rest as UFS. I saw a warning once that x number of sectors are not being used because of the off-size of the partitions. Perhaps I should repartition? As a side question - why are the CD-ROM (see DMESG below) drives using PIO? Thanks in advance, Tom Veldhouse veldy@visi.com DMESG output follows: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-19991215-CURRENT #0: Wed Dec 15 16:26:48 GMT 1999 root@usw2.freebsd.org:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K7(tm) Processor (598.84-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x612 Stepping = 2 Features=0x81f9ff AMD Features=0xc0400000 real memory = 134152192 (131008K bytes) config> di lnc0 config> di le0 config> di ie0 config> di fe0 config> di ex0 config> di ed0 config> di cs0 config> di wt0 config> di scd0 config> di mcd0 config> di matcd0 config> di bt0 config> di aic0 config> di aha0 config> di adv0 config> q avail memory = 126492672 (123528K bytes) Preloaded elf kernel "kernel" at 0xc0378000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc037809c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 10 at device 5.0 on pci1 pci0: unknown card (vendor=0x1274, dev=0x1371) at 3.0 irq 11 dc0: irq 5 at device 6.0 on pci0 dc0: Ethernet address: 00:a0:cc:37:ad:85 miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pci0: VIA 83C572 USB controller (vendor=0x1106, dev=0x3038) at 7.2 irq 11 pci0: VIA 83C572 USB controller (vendor=0x1106, dev=0x3038) at 7.3 irq 11 isab1: at device 7.4 on pci0 pci0: unknown card (vendor=0x127a, dev=0x1003) at 9.0 irq 10 pci0: unknown card (vendor=0x104c, dev=0x8019) at 12.0 irq 3 fe0: not probed (disabled) fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata-isa0: already registered as ata0 ata-isa1: already registered as ata1 adv0: not probed (disabled) bt0: not probed (disabled) aha0: not probed (disabled) aic0: not probed (disabled) wt0: not probed (disabled) mcd0: not probed (disabled) matcd0: not probed (disabled) scd0: not probed (disabled) atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppb0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: ppbus0: LEXWPS plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 ed0: not probed (disabled) ex0: not probed (disabled) ie0: not probed (disabled) le0: not probed (disabled) lnc0: not probed (disabled) cs0: not probed (disabled) ad0: ATA-4 disk at ata0 as master ad0: 19092MB (39102336 sectors), 38792 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad1: ATA-4 disk at ata0 as slave ad1: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 acd0: CDROM drive at ata1 as master , 512KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA stream, DVD-ROM, DVD-R acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked acd1: CDROM drive at ata1 as slave acd1: read 4134KB/s (4134KB/s) write 689KB/s, 2048KB buffer, PIO acd1: supported read types: CD-R, CD-RW, CD-DA stream, packet acd1: supported write types: CD-R, CD-RW, test write acd1: Audio: play, 255 volume levels acd1: Mechanism: ejectable tray acd1: Medium: no/blank disc inside, unlocked Mounting root from ufs:/dev/ad1s2a ad1: UDMA CRC WRITE ERROR blk# 1999 retrying ad1: UDMA CRC WRITE ERROR blk# 1999 retrying ad1: UDMA CRC WRITE ERROR blk# 1999 retrying ad1: UDMA CRC WRITE ERROR blk# 1999 falling back to PIO mode To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 5:25:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id C010C14BDE for ; Fri, 17 Dec 1999 05:25:43 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id HAA04225; Fri, 17 Dec 1999 07:25:24 -0600 (CST) (envelope-from dick) Date: Fri, 17 Dec 1999 07:25:24 -0600 From: "Richard Seaman, Jr." To: Soren Schmidt Cc: "Richard Seaman, Jr." , djb@Wit389306.student.utwente.nl, freebsd-current@FreeBSD.ORG Subject: Re: ATA driver problem?? (lost disk contact) Message-ID: <19991217072524.B320@tar.com> References: <19991216165055.A320@tar.com> <199912170722.IAA04753@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912170722.IAA04753@freebsd.dk>; from sos@freebsd.dk on Fri, Dec 17, 1999 at 08:22:03AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 17, 1999 at 08:22:03AM +0100, Soren Schmidt wrote: > Yup, sounds like the problem some are seing, now I wonder why I > havn't seen it on any of the IBM disks I've access to, hmm... > > It apparantly can't be disabled, but I'll try to figure out if > I can detect when the drive is in this mode, or put it in > standby mode and back again when there is nothing else to do, > that should reset the timer... Note that the wd driver doesn't "report" any problems. Don't know if that is because the wd driver handles this differently, or because the reporting is different. The machine that reports these problems runs 7/24, and has for over a year and a half. The IBM disk has been in for quite a while (maybe 6 months or more). Only ata "reports" the problem. Note that the IBM specs say that spinup from standby to idle is 13 secs "typical" and 31 secs max for this drive. I'm assuming that what we're seeing is that the ata driver "lost contact" because the timeout is less that the time it takes to spinup from standby to idle (or to spinup from an interrupted switch from idle to standby)? -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 5:26: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 53BE915007 for ; Fri, 17 Dec 1999 05:26:02 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA89819; Fri, 17 Dec 1999 14:25:57 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912171325.OAA89819@freebsd.dk> Subject: Re: ATA Problem? Fallback to PIO In-Reply-To: <001001bf4890$a45fde60$0100a8c0@veldy.org> from "Thomas T. Veldhouse" at "Dec 17, 1999 07:14:24 am" To: veldy@visi.com (Thomas T. Veldhouse) Date: Fri, 17 Dec 1999 14:25:57 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG (FreeBSD-Current) X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Thomas T. Veldhouse wrote: > I seem to be having a problem with the my Western Digital Caviar 6.4GB > UDMA33 > > ad0: ATA-4 disk at ata0 as master > ad0: 19092MB (39102336 sectors), 38792 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, UDMA33 > ad1: ATA-4 disk at ata0 as slave > ad1: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S > ad1: 16 secs/int, 1 depth queue, UDMA33 > . > . > . > Mounting root from ufs:/dev/ad1s2a > ad1: UDMA CRC WRITE ERROR blk# 1999 retrying > ad1: UDMA CRC WRITE ERROR blk# 1999 retrying > ad1: UDMA CRC WRITE ERROR blk# 1999 retrying > ad1: UDMA CRC WRITE ERROR blk# 1999 falling back to PIO mode > > I do not have any problems with this drive under Windows98, WindowsNT, > FreeBSD3.x or Linux. Never an error reported before. Hmm, the WDC WD200BA disk does UDMA66 doesn't it ?? The VIA 82C686 has support for this, but its very "generous" in setting it. Form the above I'd guess you dont have a 80lead cable on those disks ?? What does the BIOS say about the disk modes on boot ?? A dmesg from a verbose boot would be nice... Also what mobo is this ? I guess the VIA has decided to run UDMA66 which wont work without the right cable... > As a side question - why are the CD-ROM (see DMESG below) drives using PIO? Because ATAPI DMA is disabled as default (the old driver didn't even have DMA support for ATAPI devices), see lint how to enable it. -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 5:28:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id E071A15736 for ; Fri, 17 Dec 1999 05:28:36 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA90417; Fri, 17 Dec 1999 14:28:29 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912171328.OAA90417@freebsd.dk> Subject: Re: ATA driver problem?? (lost disk contact) In-Reply-To: <19991217072524.B320@tar.com> from "Richard Seaman, Jr." at "Dec 17, 1999 07:25:24 am" To: dick@tar.com (Richard Seaman, Jr.) Date: Fri, 17 Dec 1999 14:28:29 +0100 (CET) Cc: djb@Wit389306.student.utwente.nl, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Richard Seaman, Jr. wrote: > > > Yup, sounds like the problem some are seing, now I wonder why I > > havn't seen it on any of the IBM disks I've access to, hmm... > > > > It apparantly can't be disabled, but I'll try to figure out if > > I can detect when the drive is in this mode, or put it in > > standby mode and back again when there is nothing else to do, > > that should reset the timer... > > Note that the wd driver doesn't "report" any problems. Don't > know if that is because the wd driver handles this differently, > or because the reporting is different. Because the wd driver has a 10 secs timeout, and ata has 5 secs. I think the easiest way to "solve" this is to increase the timeout to 10-15 secs, as little as I want to do that... > The machine that reports these problems runs 7/24, and has for > over a year and a half. The IBM disk has been in for quite a > while (maybe 6 months or more). Only ata "reports" the problem. Se above.. -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 5:45: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from jfh00.fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by hub.freebsd.org (Postfix) with ESMTP id C20E414FEB for ; Fri, 17 Dec 1999 05:44:58 -0800 (PST) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Received: (from jfh@localhost) by jfh00.fernuni-hagen.de (8.9.3/8.9.3) id OAA03550; Fri, 17 Dec 1999 14:44:56 +0100 (CET) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) X-Authentication-Warning: jfh00.fernuni-hagen.de: jfh set sender to fritz.heinrichmeyer@fernuni-hagen.de using -f To: Soren Schmidt , freebsd-current@freebsd.org Subject: ATA driver, ZIP-Disk and mtools now OK References: <199912171328.OAA90417@freebsd.dk> From: Fritz Heinrichmeyer Date: 17 Dec 1999 14:44:56 +0100 In-Reply-To: Soren Schmidt's message of "Fri, 17 Dec 1999 14:28:29 +0100 (CET)" Message-ID: Lines: 21 User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/21.2 (Yoko) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG today i tried again a windows formatted ZIP disk with mtools. First with a line in /usr/local/etc/mtools.conf drive z: file="/dev/afd0s4" <--- this does not work!!!!!!!!!!!!!! i had a message like init Z: sector size too big Cannot initialize 'Z:' this message i have never seen before, so i gave poking around with mtools.conf another try. Looking at solaris examples, i edited drive z: file="/dev/afd0s4" partition=4 # this works!!!! and now it works! -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 5:52: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id E877214EB1 for ; Fri, 17 Dec 1999 05:51:59 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA95853; Fri, 17 Dec 1999 14:51:40 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912171351.OAA95853@freebsd.dk> Subject: Re: ATA driver, ZIP-Disk and mtools now OK In-Reply-To: from Fritz Heinrichmeyer at "Dec 17, 1999 02:44:56 pm" To: fritz.heinrichmeyer@fernuni-hagen.de (Fritz Heinrichmeyer) Date: Fri, 17 Dec 1999 14:51:40 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Fritz Heinrichmeyer wrote: > today i tried again a windows formatted ZIP disk with mtools. First > with a line in /usr/local/etc/mtools.conf > > drive z: file="/dev/afd0s4" <--- this does not work!!!!!!!!!!!!!! > > i had a message like > > init Z: sector size too big > Cannot initialize 'Z:' > > this message i have never seen before, so i gave poking around with > mtools.conf another try. Looking at solaris examples, i edited > > drive z: file="/dev/afd0s4" partition=4 # this works!!!! > > and now it works! Hmm, so my gut feeling that the atapi-fd driver did what it should was not that far off :) Thanks for reporting, I was about to spend time on this problem in the weekend, now I can tick that on off.... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 5:57:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from jfh00.fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by hub.freebsd.org (Postfix) with ESMTP id 3519315024 for ; Fri, 17 Dec 1999 05:57:20 -0800 (PST) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Received: (from jfh@localhost) by jfh00.fernuni-hagen.de (8.9.3/8.9.3) id OAA03574; Fri, 17 Dec 1999 14:57:18 +0100 (CET) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) X-Authentication-Warning: jfh00.fernuni-hagen.de: jfh set sender to fritz.heinrichmeyer@fernuni-hagen.de using -f To: Soren Schmidt , freebsd-current@freebsd.org Cc: fritz.heinrichmeyer@fernuni-hagen.de (Fritz Heinrichmeyer), freebsd-current@freebsd.org Subject: Re: ATA driver, ZIP-Disk and mtools now OK, but mount_msdos ... References: <199912171351.OAA95853@freebsd.dk> From: Fritz Heinrichmeyer Date: 17 Dec 1999 14:57:18 +0100 In-Reply-To: Soren Schmidt's message of "Fri, 17 Dec 1999 14:51:40 +0100 (CET)" Message-ID: Lines: 12 User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/21.2 (Yoko) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of course i wish you a nice weekend ... but only mtools work. Mount_msdos still fails: mount_msdos /dev/afd0s4 /mnt mount_msdos: /dev/afd0s4: Invalid argument -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 6:11:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 91C68156D4 for ; Fri, 17 Dec 1999 06:11:32 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id PAA00405; Fri, 17 Dec 1999 15:10:36 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912171410.PAA00405@freebsd.dk> Subject: Re: ATA driver, ZIP-Disk and mtools now OK, but mount_msdos ... In-Reply-To: from Fritz Heinrichmeyer at "Dec 17, 1999 02:57:18 pm" To: fritz.heinrichmeyer@fernuni-hagen.de (Fritz Heinrichmeyer) Date: Fri, 17 Dec 1999 15:10:36 +0100 (CET) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Fritz Heinrichmeyer wrote: > > Of course i wish you a nice weekend ... but only mtools work. > > Mount_msdos still fails: > > mount_msdos /dev/afd0s4 /mnt > mount_msdos: /dev/afd0s4: Invalid argument Hmm, strange, are you sure the dospartition is on slice 4 ?? -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 6:20:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 6774715740 for ; Fri, 17 Dec 1999 06:20:51 -0800 (PST) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id 042AE1FBA; Fri, 17 Dec 1999 15:20:49 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by shadowmere.student.utwente.nl (Postfix) with ESMTP id F0232C6 for ; Fri, 17 Dec 1999 15:20:48 +0100 (CET) Date: Fri, 17 Dec 1999 15:20:48 +0100 (CET) From: Pascal Hofstee To: freebsd-current@freebsd.org Subject: minor gcc-issue ? 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, While tracing a bug with my Mozilla Tinderbox-builds continuously rasing SIGFPE's I starting searching for the gcc-option -mieee-fp as suggested by people from the Mozilla-team. I couldn't find that option in the gcc-man-pages so I started searching for it in the gcc source-tree. I eventually came across the following oditity in /usr/src/contrib/gcc/config/i386 freebsd-aout.h: #define TARGET_DEFAULT \ (MASK_80387 | MASK_IEEE_FP | MASK_FLOAT_RETURNS | MASK_NO_FANCY_MATH_387) freebsd.h: #define TARGET_DEFAULT (MASK_NO_FANCY_MATH_387 | 0301) apparently the defines for MASK_80387 | MASK_IEEE_FP | MASK_FLOAT_RETURNS got combined into one single octal value. If have doubts that this is actually intended. -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 6:30:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22]) by hub.freebsd.org (Postfix) with ESMTP id 8203515286 for ; Fri, 17 Dec 1999 06:30:23 -0800 (PST) (envelope-from veldy@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id A0E8E3851; Fri, 17 Dec 1999 08:30:22 -0600 (CST) Received: from localhost (veldy@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id IAA01332; Fri, 17 Dec 1999 08:30:22 -0600 (CST) X-Authentication-Warning: isis.visi.com: veldy owned process doing -bs Date: Fri, 17 Dec 1999 08:30:22 -0600 (CST) From: Thomas Veldhouse To: Soren Schmidt Cc: FreeBSD-Current Subject: Re: ATA Problem? Fallback to PIO In-Reply-To: <199912171325.OAA89819@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 17 Dec 1999, Soren Schmidt wrote: >=20 > Hmm, the WDC WD200BA disk does UDMA66 doesn't it ?? > The VIA 82C686 has support for this, but its very "generous" in setting > it. Form the above I'd guess you dont have a 80lead cable on those > disks ?? What does the BIOS say about the disk modes on boot ?? > A dmesg from a verbose boot would be nice... Also what mobo is this ? > I guess the VIA has decided to run UDMA66 which wont work without > the right cable... > This is a compaq special motherboard (5868 series). If I would have known what I as getting, I wouldn't have bought the computer. The BIOS offers nearly nothing in the way of options. I do know it uses a VIA chipset and the AMD 751 chipset. I don't really have more specifics other than what you see in the dmesg. I will get you a verbose dmesg tonight. I will also see what BIOS settings are available. I do believe all of them are set to auto for the IDE interfaces.=20 I do believe the drive is UDMA66 capable - but I never looked into it. Perhaps I should get a different cable. Ironically, Linux drops that drive to PIO. > Because ATAPI DMA is disabled as default (the old driver didn't even have > DMA support for ATAPI devices), see lint how to enable it. >=20 > -S=F8ren >=20 Cool. Real CD performance. Thanks, Tom Veldhouse veldy@visi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 7: 3: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 0736C14DA3; Fri, 17 Dec 1999 07:02:59 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 1CFE8137FCB; Fri, 17 Dec 1999 10:02:58 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id KAA21926; Fri, 17 Dec 1999 10:02:57 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14426.20641.329657.464545@trooper.velocet.net> Date: Fri, 17 Dec 1999 10:02:57 -0500 (EST) To: Mike Smith Cc: David Gilbert , freebsd-current@freebsd.org Subject: Re: AMI MegaRAID datapoint. In-Reply-To: <199912162354.PAA02071@mass.cdrom.com> References: <14425.2778.943367.365945@trooper.velocet.net> <199912162354.PAA02071@mass.cdrom.com> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Mike" == Mike Smith writes: >> The AMI MegaRAID 1400 delivers between 16.5 and 19 M/s (the 19M/s >> value is somewhat contrived --- using 8 bonnies in parrallel and >> then summing their results --- which is not 100% valid)... but the >> MegaRAID appears to be stable. Mike> Hmm. Those numbers aren't so great though. I'd be interested Mike> to know how busy the controller is during your test (use systat Mike> -vmstat 1 and look at the amrd0 device), as well as how you've Mike> configured it. AMI's default configurations for those Mike> controllers is wildly inconsistent between one BIOS version and Mike> the next. Well... it's RAID-5 across the same 8 drives with all 8 drives on one LVD chain (same configuration as the other test). I have tried the 128k stripe, but it was slower than the default 64k stripe. >> I would like to know, however, if there are any planned or >> in-the-works utility programs for the amr device. In particular, a >> program to print the state of the array would be useful. Mike> I'm currently waiting on AMI for more documentation, at which Mike> point there will indeed be more monitoring and control Mike> facilities added. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 7:14:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from web2106.mail.yahoo.com (web2106.mail.yahoo.com [128.11.68.250]) by hub.freebsd.org (Postfix) with SMTP id 091C714E0A for ; Fri, 17 Dec 1999 07:14:29 -0800 (PST) (envelope-from valsho@yahoo.com) Received: (qmail 17425 invoked by uid 60001); 17 Dec 1999 15:14:28 -0000 Message-ID: <19991217151428.17424.qmail@web2106.mail.yahoo.com> Received: from [147.226.112.101] by web2106.mail.yahoo.com; Fri, 17 Dec 1999 07:14:28 PST Date: Fri, 17 Dec 1999 07:14:28 -0800 (PST) From: "Valentin S. Chopov" Subject: ata-all.c & ata_find_dev() To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, There is are error in compilling of ata-all.c on a non-PCI macine, so I think, in ata-all.c the ata_find_dev() has to be moved into #if NPCI > 0 ... #endif Val __________________________________________________ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one place. Yahoo! Shopping: http://shopping.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 7:43:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id F0CC515736 for ; Fri, 17 Dec 1999 07:43:31 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id CAA18738; Sat, 18 Dec 1999 02:43:20 +1100 Date: Sat, 18 Dec 1999 02:43:03 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Pascal Hofstee Cc: freebsd-current@FreeBSD.ORG Subject: Re: minor gcc-issue ? 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 Fri, 17 Dec 1999, Pascal Hofstee wrote: > freebsd-aout.h: > #define TARGET_DEFAULT \ > (MASK_80387 | MASK_IEEE_FP | MASK_FLOAT_RETURNS | > MASK_NO_FANCY_MATH_387) > > > freebsd.h: > #define TARGET_DEFAULT (MASK_NO_FANCY_MATH_387 | 0301) > > > apparently the defines for MASK_80387 | MASK_IEEE_FP | MASK_FLOAT_RETURNS > got combined into one single octal value. > > If have doubts that this is actually intended. 0301 is an old (bad) way of spelling MASK_80387 | MASK_IEEE_FP | MASK_FLOAT_RETURNS. Cygnus finally fixed it in in gcc/config/i386/freebsd.h on 1999/03/23 (see the ChangeLog), but FreeBSD hasn't merged the change. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 7:49: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id 860F114F81 for ; Fri, 17 Dec 1999 07:49:05 -0800 (PST) (envelope-from netchild@Leidinger.net) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id QAA16087363; Fri, 17 Dec 1999 16:48:57 +0100 (CET) Received: from Magelan.Leidinger.net (maxtnt-239.telip.uni-sb.de [134.96.71.110]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id QAA21164; Fri, 17 Dec 1999 16:48:52 +0100 (CET) Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id QAA01063; Fri, 17 Dec 1999 16:21:51 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <199912171521.QAA01063@Magelan.Leidinger.net> Date: Fri, 17 Dec 1999 16:21:50 +0100 (CET) From: Alexander Leidinger Subject: Re: ATA driver, ZIP-Disk and mtools now OK, but mount_msdos ... To: sos@freebsd.dk Cc: current@freebsd.org, ritz.heinrichmeyer@fernuni-hagen.de In-Reply-To: <199912171410.PAA00405@freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17 Dec, Soren Schmidt wrote: >> Of course i wish you a nice weekend ... but only mtools work. >> >> Mount_msdos still fails: >> >> mount_msdos /dev/afd0s4 /mnt >> mount_msdos: /dev/afd0s4: Invalid argument > > Hmm, strange, are you sure the dospartition is on slice 4 ?? Yes (mounting /dev/wfd0s4 works). Bye, Alexander. -- Dead men tell no tales, unless you're in forensics. http://netchild.home.pages.de Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 7:49:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 6CC3314CC5 for ; Fri, 17 Dec 1999 07:49:32 -0800 (PST) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id B453B1FC9; Fri, 17 Dec 1999 16:49:30 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by shadowmere.student.utwente.nl (Postfix) with ESMTP id 85FEAC6; Fri, 17 Dec 1999 16:49:30 +0100 (CET) Date: Fri, 17 Dec 1999 16:49:30 +0100 (CET) From: Pascal Hofstee To: Bruce Evans Cc: Pascal Hofstee , freebsd-current@FreeBSD.ORG Subject: Re: minor gcc-issue ? 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 Sat, 18 Dec 1999, Bruce Evans wrote: > 0301 is an old (bad) way of spelling > MASK_80387 | MASK_IEEE_FP | MASK_FLOAT_RETURNS. Cygnus finally fixed it in > in gcc/config/i386/freebsd.h on 1999/03/23 (see the ChangeLog), but FreeBSD > hasn't merged the change. Thanks ... I do have on eother question though ... does this mean that FreeBSD by default compiles with the -mieee-fp compile switch. As that is the solution (for SIGFPE issues) suggested by some Mozilla people on Bugzilla. If FreeBSD indeed already compiles with the -mieee-flag on default the fix obviously should be looked for elsewhere. If you could clarify this issue for me it would be hightly appreciated. -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 7:49:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id BBFD915758 for ; Fri, 17 Dec 1999 07:49:35 -0800 (PST) (envelope-from netchild@Leidinger.net) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id QAA15484183; Fri, 17 Dec 1999 16:48:59 +0100 (CET) Received: from Magelan.Leidinger.net (maxtnt-239.telip.uni-sb.de [134.96.71.110]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id QAA21180; Fri, 17 Dec 1999 16:48:57 +0100 (CET) Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id QAA00530; Fri, 17 Dec 1999 16:48:35 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <199912171548.QAA00530@Magelan.Leidinger.net> Date: Fri, 17 Dec 1999 16:48:34 +0100 (CET) From: Alexander Leidinger Subject: Re: ATA driver, ZIP-Disk and mtools now OK To: fritz.heinrichmeyer@fernuni-hagen.de Cc: sos@freebsd.dk, freebsd-current@FreeBSD.ORG In-Reply-To: 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 On 17 Dec, Fritz Heinrichmeyer wrote: > drive z: file="/dev/afd0s4" partition=4 # this works!!!! > > and now it works! Confirmed, mtools works (mount remains). I think this gives Sĝren a start to look at. If I remember correctly one of the first versions of ata didn´t had this problem (it stopped perhaps at the 3. or 4. "Heads-Up"). Bye, Alexander. -- If Bill Gates had a dime for every time a Windows box crashed... ...Oh, wait a minute, he already does. http://netchild.home.pages.de Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 7:57:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 9F67F14FC4; Fri, 17 Dec 1999 07:57:17 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA46338; Fri, 17 Dec 1999 10:57:16 -0500 (EST) (envelope-from wollman) Date: Fri, 17 Dec 1999 10:57:16 -0500 (EST) From: Garrett Wollman Message-Id: <199912171557.KAA46338@khavrinen.lcs.mit.edu> To: Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-Reply-To: <199912170855.AAA00646@mass.cdrom.com> References: <199912170328.TAA57721@apollo.backplane.com> <199912170855.AAA00646@mass.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > the IP and UDP checksum guessing, but more that I think you'll find that > a considerable amount of the inbound NFS traffic handling is actually > performed in the interrupt context If it is, then there is a serious bug. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 8:26:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 4D79914DCB for ; Fri, 17 Dec 1999 08:26:40 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id IAA29545; Fri, 17 Dec 1999 08:25:55 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912171625.IAA29545@gndrsh.dnsmgr.net> Subject: Re: Serious server-side NFS problem In-Reply-To: <199912170328.TAA57721@apollo.backplane.com> from Matthew Dillon at "Dec 16, 1999 07:28:34 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Fri, 17 Dec 1999 08:25:55 -0800 (PST) Cc: gallatin@cs.duke.edu (Andrew Gallatin), toasty@dragondata.com (Kevin Day), phk@critter.freebsd.dk (Poul-Henning Kamp), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 ... > (200-300 MHz) clients. That's *with* packet loss (for some reason when > my fxp ethernets pump data out that quickly they tend to cause packet > loss in other parts of my HUBed network, which I find quite annoying). Interesting you should say that.... I've been playing with some broadcom based ASIC 100BaseTX full duplex switches and I actually loose more packets due to overrunning the buffers in the switch than I do if I used a half duplex standard hub. :-( Performance for most things overall on the network is better with the switch, but direct high bandwidth traffic between 2 machines has suffered due to the conversion to a fully switched network. Seems FreeBSD (using dc21143 based cards) can pump data around so damn fast that the switch can't keep up :-(. I need to do some more testing to find out if this occurs between ports on the same ASIC or only when packets have to go out to the ASIC to ASIC bridge bus. Also how do the fxp and dc based cards respond to flow control? Do we obey it? Do the cards even understand it? -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 8:38:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 556ED15752; Fri, 17 Dec 1999 08:38:50 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id RAA24448; Fri, 17 Dec 1999 17:38:29 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <14426.20641.329657.464545@trooper.velocet.net> References: <14425.2778.943367.365945@trooper.velocet.net> <199912162354.PAA02071@mass.cdrom.com> <14426.20641.329657.464545@trooper.velocet.net> Date: Fri, 17 Dec 1999 17:34:08 +0100 To: David Gilbert , Mike Smith From: Brad Knowles Subject: Re: AMI MegaRAID datapoint. Cc: David Gilbert , freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:02 AM -0500 1999/12/17, David Gilbert wrote: > Well... it's RAID-5 across the same 8 drives with all 8 drives on one > LVD chain (same configuration as the other test). I have tried the > 128k stripe, but it was slower than the default 64k stripe. One of the lessons I learned from Greg was that, when dealing with RAID implementations in hardware, you should usually take their "native" stripe size, since that's the one that will usually perform best. It's only when you do software RAID (e.g., vinum) that you can choose larger or smaller stripe sizes with a reasonable expectation that you will get the particular performance enhancement that you're hoping for. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 8:48:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 3F82115703 for ; Fri, 17 Dec 1999 08:48:44 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id IAA29595; Fri, 17 Dec 1999 08:48:30 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912171648.IAA29595@gndrsh.dnsmgr.net> Subject: Re: Weird story with dump | restore In-Reply-To: <19991217123742.A70473@myhakas.matti.ee> from Vallo Kallaste at "Dec 17, 1999 12:37:42 pm" To: vallo@solaris.matti.ee Date: Fri, 17 Dec 1999 08:48:30 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 > On Fri, Dec 17, 1999 at 10:47:59AM +0200, Vallo Kallaste wrote: > > [snip] > > > It's very annoying, I have only fair experiences with dump/restore back > > to the 2.2.2 days until now. > > Sorry for the long post and partially? false alert. > > Something in my mind waked up and I checked what type of bsize and fsize > the other machines have. Now I remember a little discussion in the > cvs-all list, at that time phk committed something about default flags > for newfs or so and there was rgrimes involved into discussion. He was > suggesting following flags for filesystem creation for newer, bigger > disks: > > newfs -b16384 -f2048 -u2048 -c128 -i4096 > > I've used them since with no problems whatsoever. Now I got the dump > done on the machine with default filesystem, the bugger is unusual > filesystem I guess. Is it expected behavior? Does anybody know why it > can't be done? A few more details please. Are you having problems when you are dumping from a file system formatted as above, or is it a restore going to this type of file system, or are both the source and destination file system formatted as above? EXACTLY what dump/restore pipeline command did you run? I'll try to duplicate this here... I suspect a blocking/unblocking operation is highly un optimized to deal with these large block size file systems and/or your exasting a kernel resource during this operation. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 8:54:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 9E9AC15742; Fri, 17 Dec 1999 08:54:44 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 3FD9D137FD0; Fri, 17 Dec 1999 11:54:43 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id LAA23838; Fri, 17 Dec 1999 11:54:42 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14426.27346.393029.804411@trooper.velocet.net> Date: Fri, 17 Dec 1999 11:54:42 -0500 (EST) To: Brad Knowles Cc: David Gilbert , Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: AMI MegaRAID datapoint. In-Reply-To: References: <14425.2778.943367.365945@trooper.velocet.net> <199912162354.PAA02071@mass.cdrom.com> <14426.20641.329657.464545@trooper.velocet.net> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Brad" == Brad Knowles writes: Brad> At 10:02 AM -0500 1999/12/17, David Gilbert wrote: >> Well... it's RAID-5 across the same 8 drives with all 8 drives on >> one LVD chain (same configuration as the other test). I have tried >> the 128k stripe, but it was slower than the default 64k stripe. Brad> One of the lessons I learned from Greg was that, when dealing Brad> with RAID implementations in hardware, you should usually take Brad> their "native" stripe size, since that's the one that will Brad> usually perform best. Brad> It's only when you do software RAID (e.g., vinum) that you can Brad> choose larger or smaller stripe sizes with a reasonable Brad> expectation that you will get the particular performance Brad> enhancement that you're hoping for. Another thing that I find very different betweent he vinum software RAID-5 and the hardware I've tried (I've used both the DPT and the MegaRAID controllers) that the latency of a command can be incredible on the hardware raid. If you type (for instance) 'du -ks foo' where foo is a big directory on the hardware raid, and then press CTRL-C, it can take 10 to 15 seconds to come back (I'm assuming that this is queued I/O requests). Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 9: 8: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A905A156E6; Fri, 17 Dec 1999 09:07:58 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA63193; Fri, 17 Dec 1999 09:07:56 -0800 (PST) (envelope-from dillon) Date: Fri, 17 Dec 1999 09:07:56 -0800 (PST) From: Matthew Dillon Message-Id: <199912171707.JAA63193@apollo.backplane.com> To: Garrett Wollman Cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem References: <199912170328.TAA57721@apollo.backplane.com> <199912170855.AAA00646@mass.cdrom.com> <199912171557.KAA46338@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :< said: : :> the IP and UDP checksum guessing, but more that I think you'll find that :> a considerable amount of the inbound NFS traffic handling is actually :> performed in the interrupt context : :If it is, then there is a serious bug. : :-GAWollman : :-- :Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same No serious NFS traffic handling is done in the interrupt context. The packets are essentially just queued up for nfsd to deal with. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 9:11:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as15-036.rp-plus.de [149.221.237.36]) by hub.freebsd.org (Postfix) with ESMTP id 625041571B for ; Fri, 17 Dec 1999 09:11:26 -0800 (PST) (envelope-from alex@cichlids.com) Received: by cichlids.com (Postfix, from userid 1001) id B4A15AB89; Fri, 17 Dec 1999 18:12:26 +0100 (CET) Message-ID: <19991217181226.A83674@cichlids.com> Date: Fri, 17 Dec 1999 18:12:26 +0100 From: Alexander Langer To: freebsd-current@freebsd.org Subject: ata: Mount root failure: 6 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! today I upgraded my current with the new ata drivers. I followed the instructions in src/UPDATING. When I boot my new kernel, I get root mount failure: 6 Also, it automatically tries to mount wd0s1a, but this fails, too. When I boot an old kernel, I can mount rwd0s1a I shall give it the device, but I really only get this 6 - error. What can I do now? (I have a working kernel, as said) Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 9:17:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id CEA0114F84 for ; Fri, 17 Dec 1999 09:17:35 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA96179; Fri, 17 Dec 1999 10:17:34 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA81278; Fri, 17 Dec 1999 10:17:33 -0700 (MST) Message-Id: <199912171717.KAA81278@harmony.village.org> To: Alexander Langer Subject: Re: ata: Mount root failure: 6 Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 17 Dec 1999 18:12:26 +0100." <19991217181226.A83674@cichlids.com> References: <19991217181226.A83674@cichlids.com> Date: Fri, 17 Dec 1999 10:17:33 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991217181226.A83674@cichlids.com> Alexander Langer writes: : When I boot my new kernel, I get : root mount failure: 6 This is ENXIO, Device Not Configured. What is the name of the device that it is trying to mount? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 9:18:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id BD75A14E2D for ; Fri, 17 Dec 1999 09:18:33 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id MAA26667; Fri, 17 Dec 1999 12:18:22 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id MAA02944; Fri, 17 Dec 1999 12:17:52 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 17 Dec 1999 12:17:51 -0500 (EST) To: "Kenneth D. Merry" Cc: Matthew Dillon , anderson@cs.duke.edu, Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-Reply-To: <19991216205554.A20410@panzer.kdm.org> References: <199912160758.BAA87332@celery.dragondata.com> <199912160801.AAA50074@apollo.backplane.com> <14425.33053.359447.429215@grasshopper.cs.duke.edu> <199912170328.TAA57721@apollo.backplane.com> <19991216205554.A20410@panzer.kdm.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14426.25577.295630.812426@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth D. Merry writes: > > > Another advantage with gigabit ethernet is that if you can do jumbo frames, > you can fit an entire 8K NFS packet in one frame. > > I'd like to see NFS numbers from two 21264 Alphas with GigE cards, zero > copy, checksum offloading and a big striped array on one end at least. I Well.. maybe this will work for you ;-) 2 21264 alphas (500MHz XP1000S), 640MB RAM, Myrinet/Trapeze using 64-bit Myrinet cards, 8K cluster mbufs, UDP checksums disabled (we can do checksum offloading at the receiver only). We have a 56K MTU. Using this setup, *without* zero copy, we get roughly 140MB/sec out of TCP: % netperf -Hbroil-my TCP STREAM TEST to broil-my : histogram Recv Send Send Socket Socket Message Elapsed Size Size Size Time Throughput bytes bytes bytes secs. 10^6bits/sec 524288 524288 524288 10.01 1135.20 And about 900Mb/sec (112MB/sec) out of UDP using an 8k message size: % netperf -Hbroil-my -tUDP_STREAM -- -m 8192 UDP UNIDIRECTIONAL SEND TEST to broil-my : histogram Socket Message Elapsed Messages Size Size Time Okay Errors Throughput bytes bytes secs # # 10^6bits/sec 57344 8192 10.00 165619 0 1084.94 65535 10.00 137338 899.68 I have exported a local disk on broil-my and created a 512MB file (zot). Both machines have 640MB of ram and the test file is fully cached on the server. When reading the file from the client, I have found the best I can do is roughly 57MB/sec: # mount_nfs -a 3 -r 16384 boil-my:/var/tmp /mnt # dd if=/mnt/zot of=/dev/null bs=64k 8192+0 records in 8192+0 records out 536870912 bytes transferred in 9.658521 secs (55585209 bytes/sec) # umount /mnt # mount_nfs -a 3 -r 32768 boil-my:/var/tmp /mnt # if=/mnt/zot of=/dev/null bs=64k 8192+0 records in 8192+0 records out 536870912 bytes transferred in 9.513517 secs (56432433 bytes/sec) Emperically, it seems that -a 3 performs better than -a 2 or -a 4. Also, the bandwidth seems to max out with a 16k read size. Increasing much beyond that doesn't seem to help. Varying the number if nfsiods across between 2,4 & 20 doesn't seem to matter much. Running iprobe on the client (http://www.cs.duke.edu/ari/iprobe.html) shows us that we are spending: - 29.4% in bcopy -- this doesn't change a lot if I enable/disable vfs_ioopt. I suspect that this is from bcopy'ing data out of mbufs, not crossing the user/kernel boundary. In either case, there's not much that can be done to reduce this in a generic manner. - 5.5% tsleep (contention between nfsiods?) The "top" functions/components are: Name Count Pct Pct -- ----- --- --- kernel 4128 90.0 -------- bcopy_samealign_lp 1347 32.6 29.4 procrunnable 279 6.8 6.1 tsleep 256 6.2 5.6 Lidle2 195 4.7 4.3 m_freem 89 2.2 1.9 soreceive 73 1.8 1.6 lockmgr 63 1.5 1.4 brelse 60 1.5 1.3 vm_page_free_toq 55 1.3 1.2 ovbcopy 51 1.2 1.1 wakeup 43 1.0 0.9 acquire 42 1.0 0.9 bcopy_da_lp 42 1.0 0.9 nfs_request 41 1.0 0.9 ip_input 40 1.0 0.9 biodone 39 0.9 0.9 nfs_readrpc 38 0.9 0.8 vm_page_alloc 36 0.9 0.8 <...> ---------- /modules/tpz.ko 435 9.5 tpz.ko is the myrinet device driver. This is saying that the system spent 90% of its time in the static kernel, 9.5% in the device driver, and 0.5% in userland. The server is also close to maxed-out. I can provide an iprobe breakdown for it as well, and/or complete breakdowns for the client and server. Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 9:21:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as15-036.rp-plus.de [149.221.237.36]) by hub.freebsd.org (Postfix) with ESMTP id 73FA914DED for ; Fri, 17 Dec 1999 09:21:45 -0800 (PST) (envelope-from alex@cichlids.com) Received: by cichlids.com (Postfix, from userid 1001) id 590ABAB89; Fri, 17 Dec 1999 18:22:46 +0100 (CET) Message-ID: <19991217182246.A83740@cichlids.com> Date: Fri, 17 Dec 1999 18:22:46 +0100 From: Alexander Langer To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: ata: Mount root failure: 6 References: <19991217181226.A83674@cichlids.com> <199912171717.KAA81278@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199912171717.KAA81278@harmony.village.org>; from Warner Losh on Fri, Dec 17, 1999 at 10:17:33AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 17, 1999 at 10:17:33AM -0700, Warner Losh wrote: > : When I boot my new kernel, I get > : root mount failure: 6 > This is ENXIO, Device Not Configured. What is the name of the device > that it is trying to mount? ad0s1a an IDE drive with the new ata-drivers. Also, the same for wd0s1a and rwd0s1a Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 9:24:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3B2B71578E for ; Fri, 17 Dec 1999 09:24:21 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA96215; Fri, 17 Dec 1999 10:24:19 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA81424; Fri, 17 Dec 1999 10:24:19 -0700 (MST) Message-Id: <199912171724.KAA81424@harmony.village.org> To: Alexander Langer Subject: Re: ata: Mount root failure: 6 Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 17 Dec 1999 18:22:46 +0100." <19991217182246.A83740@cichlids.com> References: <19991217182246.A83740@cichlids.com> <19991217181226.A83674@cichlids.com> <199912171717.KAA81278@harmony.village.org> Date: Fri, 17 Dec 1999 10:24:19 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991217182246.A83740@cichlids.com> Alexander Langer writes: : ad0s1a : an IDE drive with the new ata-drivers. : Also, the same for wd0s1a and rwd0s1a That looks good. Can you send the config file and the boot messages, at least those related to ata/ad? And a ls -l /dev/ad0* might not hurt either. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 9:32: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C9FBE15703 for ; Fri, 17 Dec 1999 09:32:07 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA63489; Fri, 17 Dec 1999 09:32:04 -0800 (PST) (envelope-from dillon) Date: Fri, 17 Dec 1999 09:32:04 -0800 (PST) From: Matthew Dillon Message-Id: <199912171732.JAA63489@apollo.backplane.com> To: "Rodney W. Grimes" Cc: vallo@solaris.matti.ee, freebsd-current@FreeBSD.ORG Subject: Re: Weird story with dump | restore References: <199912171648.IAA29595@gndrsh.dnsmgr.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> suggesting following flags for filesystem creation for newer, bigger :> disks: :> :> newfs -b16384 -f2048 -u2048 -c128 -i4096 :> :> I've used them since with no problems whatsoever. Now I got the dump :> done on the machine with default filesystem, the bugger is unusual :> filesystem I guess. Is it expected behavior? Does anybody know why it :> can't be done? : :A few more details please. Are you having problems when you are :dumping from a file system formatted as above, or is it a restore :going to this type of file system, or are both the source and destination :file system formatted as above? : :EXACTLY what dump/restore pipeline command did you run? : :I'll try to duplicate this here... I suspect a blocking/unblocking :operation is highly un optimized to deal with these large block size :file systems and/or your exasting a kernel resource during this :operation. : :-- :Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net Hmm. With a block size of 16384 and restore getting stuck in 'nbufkv', it sounds like a problem with the buffer cache. The buffer cache can get into this state if there are too many dirty buffers eating up available KVM. Try changing the vfs.lodirtybuffers and vfs.hidirtybuffers sysctl variables. Try halving the values for both and tell me if that solves the problem. sysctl -a | fgrep dirty sysctl -w vfs.lodirtybuffers=X sysctl -w vfs.hidirtybuffers=Y Where X and Y are appropriate numbers. The delay you are seeing is due to the fact that getnewbuf() no longer synchronously flushes buffers out. I'll look into fixing the code to better handle this situation. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 9:39: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as15-036.rp-plus.de [149.221.237.36]) by hub.freebsd.org (Postfix) with ESMTP id 8656D1571F for ; Fri, 17 Dec 1999 09:38:15 -0800 (PST) (envelope-from alex@cichlids.com) Received: by cichlids.com (Postfix, from userid 1001) id 83836AB89; Fri, 17 Dec 1999 18:39:16 +0100 (CET) Message-ID: <19991217183916.A83806@cichlids.com> Date: Fri, 17 Dec 1999 18:39:16 +0100 From: Alexander Langer To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: ata: Mount root failure: 6 References: <19991217182246.A83740@cichlids.com> <19991217181226.A83674@cichlids.com> <199912171717.KAA81278@harmony.village.org> <19991217182246.A83740@cichlids.com> <199912171724.KAA81424@harmony.village.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=cNdxnHkX5QqsyA0e X-Mailer: Mutt 0.91.1i In-Reply-To: <199912171724.KAA81424@harmony.village.org>; from Warner Losh on Fri, Dec 17, 1999 at 10:24:19AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --cNdxnHkX5QqsyA0e Content-Type: text/plain; charset=us-ascii On Fri, Dec 17, 1999 at 10:24:19AM -0700, Warner Losh wrote: > That looks good. Can you send the config file and the boot messages, > at least those related to ata/ad? And a ls -l /dev/ad0* might not > hurt either. Unfortunately, I cant send the boot-messages, because they aren`t logged and I have no serial console. But there seems to be no error. The disk is detected correctly with UDMA33 and no errors appear. But I can send the other stuff. crw-r----- 1 root operator 116, 0x00010002 Dec 17 18:56 /dev/ad0 crw-r----- 1 root operator 116, 0 Dec 17 18:56 /dev/ad0a crw-r----- 1 root operator 116, 1 Dec 17 18:56 /dev/ad0b crw-r----- 1 root operator 116, 2 Dec 17 18:56 /dev/ad0c crw-r----- 1 root operator 116, 3 Dec 17 18:56 /dev/ad0d crw-r----- 1 root operator 116, 4 Dec 17 18:56 /dev/ad0e crw-r----- 1 root operator 116, 5 Dec 17 18:56 /dev/ad0f crw-r----- 1 root operator 116, 6 Dec 17 18:56 /dev/ad0g crw-r----- 1 root operator 116, 7 Dec 17 18:56 /dev/ad0h crw-r----- 1 root operator 116, 0x00020002 Dec 17 18:56 /dev/ad0s1 crw-r----- 1 root operator 116, 0x00020000 Dec 17 18:56 /dev/ad0s1a crw-r----- 1 root operator 116, 0x00020001 Dec 17 18:56 /dev/ad0s1b crw-r----- 1 root operator 116, 0x00020002 Dec 17 18:56 /dev/ad0s1c crw-r----- 1 root operator 116, 0x00020003 Dec 17 18:56 /dev/ad0s1d crw-r----- 1 root operator 116, 0x00020004 Dec 17 18:56 /dev/ad0s1e crw-r----- 1 root operator 116, 0x00020005 Dec 17 18:56 /dev/ad0s1f crw-r----- 1 root operator 116, 0x00020006 Dec 17 18:56 /dev/ad0s1g crw-r----- 1 root operator 116, 0x00020007 Dec 17 18:56 /dev/ad0s1h crw-r----- 1 root operator 116, 0x00030002 Dec 17 18:56 /dev/ad0s2 crw-r----- 1 root operator 116, 0x00040002 Dec 17 18:56 /dev/ad0s3 crw-r----- 1 root operator 116, 0x00050002 Dec 17 18:56 /dev/ad0s4 crw-r----- 1 root operator 116, 0x0001000a Dec 17 18:56 /dev/ad1 crw-r----- 1 root operator 116, 8 Dec 17 18:56 /dev/ad1a crw-r----- 1 root operator 116, 9 Dec 17 18:56 /dev/ad1b crw-r----- 1 root operator 116, 10 Dec 17 18:56 /dev/ad1c crw-r----- 1 root operator 116, 11 Dec 17 18:56 /dev/ad1d crw-r----- 1 root operator 116, 12 Dec 17 18:56 /dev/ad1e crw-r----- 1 root operator 116, 13 Dec 17 18:56 /dev/ad1f crw-r----- 1 root operator 116, 14 Dec 17 18:56 /dev/ad1g crw-r----- 1 root operator 116, 15 Dec 17 18:56 /dev/ad1h crw-r----- 1 root operator 116, 0x0002000a Dec 17 18:56 /dev/ad1s1 crw-r----- 1 root operator 116, 0x0003000a Dec 17 18:56 /dev/ad1s2 crw-r----- 1 root operator 116, 0x00030008 Dec 17 17:24 /dev/ad1s2a crw-r----- 1 root operator 116, 0x00030009 Dec 17 17:24 /dev/ad1s2b crw-r----- 1 root operator 116, 0x0003000a Dec 17 17:24 /dev/ad1s2c crw-r----- 1 root operator 116, 0x0003000b Dec 17 17:24 /dev/ad1s2d crw-r----- 1 root operator 116, 0x0003000c Dec 17 17:24 /dev/ad1s2e crw-r----- 1 root operator 116, 0x0003000d Dec 17 17:24 /dev/ad1s2f crw-r----- 1 root operator 116, 0x0003000e Dec 17 17:24 /dev/ad1s2g crw-r----- 1 root operator 116, 0x0003000f Dec 17 17:24 /dev/ad1s2h crw-r----- 1 root operator 116, 0x0004000a Dec 17 18:56 /dev/ad1s3 crw-r----- 1 root operator 116, 0x0005000a Dec 17 18:56 /dev/ad1s4 crw-r----- 1 root operator 116, 0x00010012 Dec 17 18:56 /dev/ad2 crw-r----- 1 root operator 116, 16 Dec 17 18:56 /dev/ad2a crw-r----- 1 root operator 116, 17 Dec 17 18:56 /dev/ad2b crw-r----- 1 root operator 116, 18 Dec 17 18:56 /dev/ad2c crw-r----- 1 root operator 116, 19 Dec 17 18:56 /dev/ad2d crw-r----- 1 root operator 116, 20 Dec 17 18:56 /dev/ad2e crw-r----- 1 root operator 116, 21 Dec 17 18:56 /dev/ad2f crw-r----- 1 root operator 116, 22 Dec 17 18:56 /dev/ad2g crw-r----- 1 root operator 116, 23 Dec 17 18:56 /dev/ad2h crw-r----- 1 root operator 116, 0x00020012 Dec 17 18:56 /dev/ad2s1 crw-r----- 1 root operator 116, 0x00030012 Dec 17 18:56 /dev/ad2s2 crw-r----- 1 root operator 116, 0x00040012 Dec 17 18:56 /dev/ad2s3 crw-r----- 1 root operator 116, 0x00050012 Dec 17 18:56 /dev/ad2s4 crw-r----- 1 root operator 116, 0x0001001a Dec 17 18:56 /dev/ad3 crw-r----- 1 root operator 116, 24 Dec 17 18:56 /dev/ad3a crw-r----- 1 root operator 116, 25 Dec 17 18:56 /dev/ad3b crw-r----- 1 root operator 116, 26 Dec 17 18:56 /dev/ad3c crw-r----- 1 root operator 116, 27 Dec 17 18:56 /dev/ad3d crw-r----- 1 root operator 116, 28 Dec 17 18:56 /dev/ad3e crw-r----- 1 root operator 116, 29 Dec 17 18:56 /dev/ad3f crw-r----- 1 root operator 116, 30 Dec 17 18:56 /dev/ad3g crw-r----- 1 root operator 116, 31 Dec 17 18:56 /dev/ad3h crw-r----- 1 root operator 116, 0x0002001a Dec 17 18:56 /dev/ad3s1 crw-r----- 1 root operator 116, 0x0003001a Dec 17 18:56 /dev/ad3s2 crw-r----- 1 root operator 116, 0x0004001a Dec 17 18:56 /dev/ad3s3 crw-r----- 1 root operator 116, 0x0005001a Dec 17 18:56 /dev/ad3s4 Attached is the config-file. Thanks Alex --cNdxnHkX5QqsyA0e Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=cichlids # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.freebsd.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.ORG/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.199 1999/11/01 04:02:56 peter Exp $ machine i386 cpu I386_CPU cpu I486_CPU cpu I586_CPU cpu I686_CPU ident cichlids maxusers 255 options NMBCLUSTERS=32768 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs controller isa0 #controller pnp0 # PnP support for ISA controller eisa0 controller pci0 # Floppy drives controller fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 # IDE controller and disks #controller wdc0 at isa? port IO_WD1 irq 14 flags 0xb0ffb0ff #device wd0 at wdc0 drive 0 #device wd1 at wdc0 drive 1 # #controller wdc1 at isa? port IO_WD2 irq 15 flags 0xb0ffb0ff #device wd2 at wdc1 drive 0 #device wd3 at wdc1 drive 1 # ## ATAPI devices on wdc? #device wcd0 #IDE CD-ROM #device wfd0 #IDE Floppy (e.g. LS-120) #device wst0 #IDE Tape (e.g. Travan) controller ata0 device atadisk0 device atapicd0 # SCSI Controllers # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. controller ncr0 # NCR/Symbios Logic controller ahb0 # EISA AHA1742 family controller ahc0 # AHA2940 and onboard AIC7xxx devices controller amd0 # AMD 53C974 (Teckram DC-390(T)) controller isp0 # Qlogic family controller dpt0 # DPT Smartcache - See LINT for options! controller adv0 at isa? port ? irq ? controller adw0 controller bt0 at isa? port ? irq ? controller aha0 at isa? port ? irq ? # SCSI peripherals # Only one of each of these is needed, they are dynamically allocated. controller scbus0 # SCSI bus (required) device da0 # Direct Access (disks) device sa0 # Sequential Access (tape etc) device cd0 # CD device pass0 # Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0 at nexus? disable flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support #controller card0 #device pcic0 at isa? #device pcic1 at isa? # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? port? flags 0x40 irq 7 controller ppbus0 # Parallel port bus (required) device lpt0 # Printer device plip0 # TCP/IP over parallel device ppi0 # Parallel port interface device #controller vpo0 # Requires scbus and da0 # PCI Ethernet NICs. device de0 # DEC/Intel DC21x4x (``Tulip'') device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) device tx0 # SMC 9432TX (83c170 ``EPIC'') device vx0 # 3Com 3c590, 3c595 (``Vortex'') # PCI Ethernet NICs that use the common MII bus controller code. controller miibus0 # MII bus support device rl0 # RealTek 8129/8139 device sf0 # Adaptec AIC-6915 (``Starfire'') device sis0 # Silicon Integrated Systems SiS 900/SiS 7016 device ste0 # Sundance ST201 (D-Link DFE-550TX) device tl0 # Texas Instruments ThunderLAN device vr0 # VIA Rhine, Rhine II device wb0 # Winbond W89C840F device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 device ex0 at isa? port? irq? device ep0 # The probe order of these is presently determined by i386/isa/isa_compat.c. device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 device fe0 at isa? port 0x300 irq ? device le0 at isa? port 0x300 irq 5 iomem 0xd0000 device lnc0 at isa? port 0x280 irq 10 drq 0 device cs0 at isa? port 0x300 irq ? # requires PCCARD (PCMCIA) support to be activated #device xe0 at isa? port? irq ? # PCCARD NIC drivers. # ze and zp take over the pcic and cannot coexist with generic pccard # support, nor the ed and ep drivers they replace. #device ze0 at isa? port 0x300 irq 10 iomem 0xd8000 #device zp0 at isa? port 0x300 irq 10 iomem 0xd8000 # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device sl 1 # Kernel SLIP pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device gzip # Exec gzipped a.out's # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter # USB support #controller uhci0 # UHCI PCI->USB interface #controller ohci0 # OHCI PCI->USB interface #controller usb0 # USB Bus (required) #device ugen0 # Generic #device uhid0 # "Human Interface Devices" #device ukbd0 # Keyboard #device ulpt0 # Printer #controller umass0 # Disks/Mass storage - Requires scbus and da0 #device ums0 # Mouse device pcm0 at isa? port ? irq 10 drq 1 flags 0x0 device sbc0 options VESA options SOFTUPDATES options USER_LDT --cNdxnHkX5QqsyA0e-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 9:53: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 60D4714A10 for ; Fri, 17 Dec 1999 09:53:03 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA96283; Fri, 17 Dec 1999 10:53:01 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA81703; Fri, 17 Dec 1999 10:53:01 -0700 (MST) Message-Id: <199912171753.KAA81703@harmony.village.org> To: Alexander Langer Subject: Re: ata: Mount root failure: 6 Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 17 Dec 1999 18:39:16 +0100." <19991217183916.A83806@cichlids.com> References: <19991217183916.A83806@cichlids.com> <19991217182246.A83740@cichlids.com> <19991217181226.A83674@cichlids.com> <199912171717.KAA81278@harmony.village.org> <19991217182246.A83740@cichlids.com> <199912171724.KAA81424@harmony.village.org> Date: Fri, 17 Dec 1999 10:53:01 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991217183916.A83806@cichlids.com> Alexander Langer writes: : crw-r----- 1 root operator 116, 0x00010002 Dec 17 18:56 /dev/ad0 You didn't copy MAKEDEV from a current source tree before making these devices. The major number of ad is 30, not 116. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 10: 7:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 752D614FCB for ; Fri, 17 Dec 1999 10:07:40 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA96340; Fri, 17 Dec 1999 11:07:38 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA81833; Fri, 17 Dec 1999 11:07:38 -0700 (MST) Message-Id: <199912171807.LAA81833@harmony.village.org> Subject: Re: ata: Mount root failure: 6 To: Alexander Langer , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 17 Dec 1999 10:53:01 MST." <199912171753.KAA81703@harmony.village.org> References: <199912171753.KAA81703@harmony.village.org> <19991217183916.A83806@cichlids.com> <19991217182246.A83740@cichlids.com> <19991217181226.A83674@cichlids.com> <199912171717.KAA81278@harmony.village.org> <19991217182246.A83740@cichlids.com> <199912171724.KAA81424@harmony.village.org> Date: Fri, 17 Dec 1999 11:07:38 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912171753.KAA81703@harmony.village.org> Warner Losh writes: : You didn't copy MAKEDEV from a current source tree before making these : devices. The major number of ad is 30, not 116. Actually, this is wrong. I didn't update MY MAKEDEV before looking. 30 is the old major bdev number... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 10: 8:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from vulture.dmem.strath.ac.uk (vulture.dmem.strath.ac.uk [130.159.232.158]) by hub.freebsd.org (Postfix) with ESMTP id 995DF157B3 for ; Fri, 17 Dec 1999 10:08:14 -0800 (PST) (envelope-from roger@vulture.dmem.strath.ac.uk) Received: (from roger@localhost) by vulture.dmem.strath.ac.uk (8.9.3/8.9.3) id SAA02594 for current@freebsd.org; Fri, 17 Dec 1999 18:08:12 GMT (envelope-from roger) Date: Fri, 17 Dec 1999 18:08:12 GMT From: Roger Hardiman Message-Id: <199912171808.SAA02594@vulture.dmem.strath.ac.uk> To: current@freebsd.org Subject: fcnt, ecvt, gcvt and XFree86 2.9.16f build errors Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The latest XFree86 snapshot, 3.9.16f (which is about to become the public 3.9.17 snapshot) does not build on FreeBSD -current. It compains about fcvt, ecvt and gcvt. The exact error log from building XFree86 3.9.16f follows. It compiles ok on my 3.4 box (just CVSuped) The next public snapshot of XFree86 3.9.x is due very soon, so a quick fix would be great. Cheers Roger -- Roger Hardiman roger@cs.strath.ac.uk roger@freebsd.org fcvt, ecvt and gcvt are used in ./xc/lib/misc/snprintf.c The important part of my make log follows making all in ./programs... making all in programs/appres... <..snip..> cc -o bitmap -O -L../../exports/lib BitEdit.o CutPaste.o Graphics.o ReqMach.o Bitmap.o Dialog.o Handlers.o -lXaw -lXmu -lXt -lSM -lICE -lXpm -lXext -lX11 -L/usr/X11R6/lib -lm ../../exports/lib/libXaw.a(MultiSrc.o): In function `InitStringOrFile': MultiSrc.o(.text+0xf7c): warning: tmpnam() possibly used unsafely; consider using mkstemp() ../../exports/lib/libXmu.a(Lower.o): In function `conv_fp': Lower.o(.text+0x4b): undefined reference to `fcvt' Lower.o(.text+0x6a): undefined reference to `ecvt' ../../exports/lib/libXmu.a(Lower.o): In function `vsnprintf': Lower.o(.text+0x85b): undefined reference to `gcvt' *** Error code 1 (continuing) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 10:15: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as15-036.rp-plus.de [149.221.237.36]) by hub.freebsd.org (Postfix) with ESMTP id 02AE114DF7 for ; Fri, 17 Dec 1999 10:15:04 -0800 (PST) (envelope-from alex@cichlids.com) Received: by cichlids.com (Postfix, from userid 1001) id 46CB7AB89; Fri, 17 Dec 1999 19:16:04 +0100 (CET) Message-ID: <19991217191603.A83939@cichlids.com> Date: Fri, 17 Dec 1999 19:16:04 +0100 From: Alexander Langer To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: ata: Mount root failure: 6 References: <19991217183916.A83806@cichlids.com> <19991217182246.A83740@cichlids.com> <19991217181226.A83674@cichlids.com> <199912171717.KAA81278@harmony.village.org> <19991217182246.A83740@cichlids.com> <199912171724.KAA81424@harmony.village.org> <19991217183916.A83806@cichlids.com> <199912171753.KAA81703@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199912171753.KAA81703@harmony.village.org>; from Warner Losh on Fri, Dec 17, 1999 at 10:53:01AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 17, 1999 at 10:53:01AM -0700, Warner Losh wrote: > In message <19991217183916.A83806@cichlids.com> Alexander Langer writes: > : crw-r----- 1 root operator 116, 0x00010002 Dec 17 18:56 /dev/ad0 > You didn't copy MAKEDEV from a current source tree before making these > devices. The major number of ad is 30, not 116. My latest -current tree has the following MAKEDEV and MAKEDEV.local: /usr/src/etc/MAKEDEV:# $FreeBSD: src/etc/MAKEDEV,v 1.226 1999/12/14 22:36:03 joerg Exp $ /usr/src/etc/MAKEDEV.local:# $FreeBSD: src/etc/MAKEDEV.local,v 1.3 1999/08/27 23:23:40 peter Exp $ That are the ones I used. Are these the right ones? If so, why does it fail for me (incorrect major number) but not for you? Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 10:18: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9EEB6151B8 for ; Fri, 17 Dec 1999 10:18:07 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA96384; Fri, 17 Dec 1999 11:18:06 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA81922; Fri, 17 Dec 1999 11:18:06 -0700 (MST) Message-Id: <199912171818.LAA81922@harmony.village.org> To: Alexander Langer Subject: Re: ata: Mount root failure: 6 Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 17 Dec 1999 19:16:04 +0100." <19991217191603.A83939@cichlids.com> References: <19991217191603.A83939@cichlids.com> <19991217183916.A83806@cichlids.com> <19991217182246.A83740@cichlids.com> <19991217181226.A83674@cichlids.com> <199912171717.KAA81278@harmony.village.org> <19991217182246.A83740@cichlids.com> <199912171724.KAA81424@harmony.village.org> <19991217183916.A83806@cichlids.com> <199912171753.KAA81703@harmony.village.org> Date: Fri, 17 Dec 1999 11:18:05 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991217191603.A83939@cichlids.com> Alexander Langer writes: : That are the ones I used. Are these the right ones? Turns out those are the right ones. : If so, why does it fail for me (incorrect major number) but not for you? Don't know. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 10:27:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as6-009.rp-plus.de [149.221.238.137]) by hub.freebsd.org (Postfix) with ESMTP id 2DCB615010 for ; Fri, 17 Dec 1999 10:27:49 -0800 (PST) (envelope-from alex@cichlids.com) Received: by cichlids.com (Postfix, from userid 1001) id CC9F0AB89; Fri, 17 Dec 1999 19:28:49 +0100 (CET) Message-ID: <19991217192849.A84075@cichlids.com> Date: Fri, 17 Dec 1999 19:28:49 +0100 From: Alexander Langer To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: ata: Mount root failure: 6 References: <19991217183916.A83806@cichlids.com> <19991217182246.A83740@cichlids.com> <19991217181226.A83674@cichlids.com> <199912171717.KAA81278@harmony.village.org> <19991217182246.A83740@cichlids.com> <199912171724.KAA81424@harmony.village.org> <19991217183916.A83806@cichlids.com> <199912171753.KAA81703@harmony.village.org> <19991217191603.A83939@cichlids.com> <199912171818.LAA81922@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199912171818.LAA81922@harmony.village.org>; from Warner Losh on Fri, Dec 17, 1999 at 11:18:05AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 17, 1999 at 11:18:05AM -0700, Warner Losh wrote: > In message <19991217191603.A83939@cichlids.com> Alexander Langer writes: > : That are the ones I used. Are these the right ones? > Turns out those are the right ones. > : If so, why does it fail for me (incorrect major number) but not for you? > Don't know. Still doesn't work, btw, also with major num of 30. BTW: The MAKEDEV _really_ does include 116 as major num. If this an error - could one _please_ correct this? Thank you. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 10:31:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id C2B2B14DA0 for ; Fri, 17 Dec 1999 10:31:03 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA96427; Fri, 17 Dec 1999 11:31:01 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA82016; Fri, 17 Dec 1999 11:31:01 -0700 (MST) Message-Id: <199912171831.LAA82016@harmony.village.org> To: Alexander Langer Subject: Re: ata: Mount root failure: 6 Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 17 Dec 1999 19:28:49 +0100." <19991217192849.A84075@cichlids.com> References: <19991217192849.A84075@cichlids.com> <19991217183916.A83806@cichlids.com> <19991217182246.A83740@cichlids.com> <19991217181226.A83674@cichlids.com> <199912171717.KAA81278@harmony.village.org> <19991217182246.A83740@cichlids.com> <199912171724.KAA81424@harmony.village.org> <19991217183916.A83806@cichlids.com> <199912171753.KAA81703@harmony.village.org> <19991217191603.A83939@cichlids.com> <199912171818.LAA81922@harmony.village.org> Date: Fri, 17 Dec 1999 11:31:01 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991217192849.A84075@cichlids.com> Alexander Langer writes: : BTW: The MAKEDEV _really_ does include 116 as major num. If this an error - could one _please_ correct this? No. MAKEDEV is right. BTW, what does your /etc/fstab look like? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 11: 2:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 313571577D for ; Fri, 17 Dec 1999 11:02:29 -0800 (PST) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id C0E372CE6B; Fri, 17 Dec 1999 21:02:22 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 79D63B9; Fri, 17 Dec 1999 21:02:27 +0200 (EET) Date: Fri, 17 Dec 1999 21:02:27 +0200 From: Vallo Kallaste To: "Rodney W. Grimes" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Weird story with dump | restore Message-ID: <19991217210227.A945@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <19991217123742.A70473@myhakas.matti.ee> <199912171648.IAA29595@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199912171648.IAA29595@gndrsh.dnsmgr.net>; from Rodney W. Grimes on Fri, Dec 17, 1999 at 08:48:30AM -0800 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 17, 1999 at 08:48:30AM -0800, "Rodney W. Grimes" wrote: > A few more details please. Are you having problems when you are > dumping from a file system formatted as above, or is it a restore > going to this type of file system, or are both the source and destination > file system formatted as above? > > EXACTLY what dump/restore pipeline command did you run? > > I'll try to duplicate this here... I suspect a blocking/unblocking > operation is highly un optimized to deal with these large block size > file systems and/or your exasting a kernel resource during this > operation. The source filesystems were both standard with bsize 8192 and fsize 1024. Target filesystems were nonstandard. I umounted the source filesystem, in the exact case /usr (/dev/ad0s1e), then mounted target filesystem to /mnt, cd to /mnt and dump -0a -f - /dev/ad0s1e | restore rf - -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 11:15: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 90D8714DA8 for ; Fri, 17 Dec 1999 11:15:02 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA74875; Fri, 17 Dec 1999 20:14:56 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912171914.UAA74875@freebsd.dk> Subject: Re: ATA Problem? Fallback to PIO In-Reply-To: from Thomas Veldhouse at "Dec 17, 1999 08:30:22 am" To: veldy@visi.com (Thomas Veldhouse) Date: Fri, 17 Dec 1999 20:14:56 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG (FreeBSD-Current) X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Thomas Veldhouse wrote: >> Hmm, the WDC WD200BA disk does UDMA66 doesn't it ?? >> The VIA 82C686 has support for this, but its very "generous" in setting >> it. Form the above I'd guess you dont have a 80lead cable on those >> disks ?? What does the BIOS say about the disk modes on boot ?? >> A dmesg from a verbose boot would be nice... Also what mobo is this ? >> I guess the VIA has decided to run UDMA66 which wont work without >> the right cable... >> >This is a compaq special motherboard (5868 series). If I would have known >what I as getting, I wouldn't have bought the computer. The BIOS offers >nearly nothing in the way of options. I do know it uses a VIA chipset and >the AMD 751 chipset. I don't really have more specifics other than what >you see in the dmesg. I will get you a verbose dmesg tonight. I will also >see what BIOS settings are available. I do believe all of them are set to >auto for the IDE interfaces. Hmm, never buy "brand name" PC's, better get two clones for the same price :), however the chipset combo are the same as on m K7M, the secret ASUS board... >I do believe the drive is UDMA66 capable - but I never looked into it. >Perhaps I should get a different cable. Ironically, Linux drops that >drive to PIO. Well, last I looked Linux didn't have any real support for the VIA 82c686, maybe its because VIA doesn't have a spec sheet for it online. I've done some experimentation, and have some sparse docs, but its not perfect (neither are the VIA chips I might add).... >> Because ATAPI DMA is disabled as default (the old driver didn't even have >> DMA support for ATAPI devices), see lint how to enable it. >Cool. Real CD performance. Yup, I get around 4M/sec of my drive with no CPU load, real nice... But be carefull, alot of ATAPI devices dont take DMA that well, and some chipsets are real crappy in that respect too.... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 11:18:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0017C15738 for ; Fri, 17 Dec 1999 11:18:20 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA64133; Fri, 17 Dec 1999 11:18:18 -0800 (PST) (envelope-from dillon) Date: Fri, 17 Dec 1999 11:18:18 -0800 (PST) From: Matthew Dillon Message-Id: <199912171918.LAA64133@apollo.backplane.com> To: Vallo Kallaste Cc: "Rodney W. Grimes" , freebsd-current@FreeBSD.ORG Subject: Re: Weird story with dump | restore References: <19991217123742.A70473@myhakas.matti.ee> <199912171648.IAA29595@gndrsh.dnsmgr.net> <19991217210227.A945@myhakas.matti.ee> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :The source filesystems were both standard with bsize 8192 and fsize :1024. Target filesystems were nonstandard. : :I umounted the source filesystem, in the exact case /usr (/dev/ad0s1e), :then mounted target filesystem to /mnt, cd to /mnt and : :dump -0a -f - /dev/ad0s1e | restore rf - :-- : :Vallo Kallaste :vallo@matti.ee Try this patch to -current, it should solve the problem. I've been meaning to fixup the buf_daemon for a while. This solves the buf_daemon problem. We still will not be entirely optimal due to kvm reshuffling but that's a different problem. -Matt Index: vfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.237 diff -u -r1.237 vfs_bio.c --- vfs_bio.c 1999/12/01 02:09:29 1.237 +++ vfs_bio.c 1999/12/17 18:44:40 @@ -88,7 +88,7 @@ bufmallocspace, maxbufmallocspace, hibufspace; static int maxbdrun; static int needsbuffer; -static int numdirtybuffers, lodirtybuffers, hidirtybuffers; +static int numdirtybuffers, hidirtybuffers; static int numfreebuffers, lofreebuffers, hifreebuffers; static int getnewbufcalls; static int getnewbufrestarts; @@ -96,8 +96,6 @@ SYSCTL_INT(_vfs, OID_AUTO, numdirtybuffers, CTLFLAG_RD, &numdirtybuffers, 0, ""); -SYSCTL_INT(_vfs, OID_AUTO, lodirtybuffers, CTLFLAG_RW, - &lodirtybuffers, 0, ""); SYSCTL_INT(_vfs, OID_AUTO, hidirtybuffers, CTLFLAG_RW, &hidirtybuffers, 0, ""); SYSCTL_INT(_vfs, OID_AUTO, numfreebuffers, CTLFLAG_RD, @@ -275,6 +273,16 @@ } } +/* + * bd_speedup - speedup the buffer cache flushing code + */ + +static __inline__ +void +bd_speedup(void) +{ + bd_wakeup(1); +} /* * Initialize buffer headers and related structures. @@ -353,7 +361,6 @@ * Reduce the chance of a deadlock occuring by limiting the number * of delayed-write dirty buffers we allow to stack up. */ - lodirtybuffers = nbuf / 7 + 10; hidirtybuffers = nbuf / 4 + 20; numdirtybuffers = 0; /* @@ -365,14 +372,9 @@ * the buffer cache. */ while (hidirtybuffers * BKVASIZE > 3 * hibufspace / 4) { - lodirtybuffers >>= 1; hidirtybuffers >>= 1; buf_maxio >>= 1; } - if (lodirtybuffers < 2) { - lodirtybuffers = 2; - hidirtybuffers = 4; - } /* * Temporary, BKVASIZE may be manipulated soon, make sure we don't @@ -799,9 +801,9 @@ void bwillwrite(void) { - int twenty = (hidirtybuffers - lodirtybuffers) / 5; + int slop = hidirtybuffers / 10; - if (numdirtybuffers > hidirtybuffers + twenty) { + if (numdirtybuffers > hidirtybuffers + slop) { int s; s = splbio(); @@ -1571,9 +1573,8 @@ flags = VFS_BIO_NEED_ANY; } - /* XXX */ + bd_speedup(); /* heeeelp */ - (void) speedup_syncer(); needsbuffer |= flags; while (needsbuffer & flags) { if (tsleep(&needsbuffer, (PRIBIO + 4) | slpflag, @@ -1652,6 +1653,7 @@ static struct proc *bufdaemonproc; static int bd_interval; static int bd_flushto; +static int bd_flushinc; static struct kproc_desc buf_kp = { "bufdaemon", @@ -1672,6 +1674,7 @@ bd_interval = 5 * hz; /* dynamically adjusted */ bd_flushto = hidirtybuffers; /* dynamically adjusted */ + bd_flushinc = 1; while (TRUE) { bd_request = 0; @@ -1694,44 +1697,38 @@ } } - /* - * If nobody is requesting anything we sleep - */ - if (bd_request == 0) - tsleep(&bd_request, PVM, "psleep", bd_interval); + if (bd_request || + tsleep(&bd_request, PVM, "psleep", bd_interval) == 0) { + /* + * Another request is pending or we were woken up + * without timing out. Flush more. + */ + --bd_flushto; + if (bd_flushto >= numdirtybuffers - 5) { + bd_flushto = numdirtybuffers - 10; + bd_flushinc = 1; + } + if (bd_flushto < 2) + bd_flushto = 2; + } else { + /* + * We slept and timed out, we can slow down. + */ + bd_flushto += bd_flushinc; + if (bd_flushto > hidirtybuffers) + bd_flushto = hidirtybuffers; + ++bd_flushinc; + if (bd_flushinc > hidirtybuffers / 20 + 1) + bd_flushinc = hidirtybuffers / 20 + 1; + } /* - * We calculate how much to add or subtract from bd_flushto - * and bd_interval based on how far off we are from the - * optimal number of dirty buffers, which is 20% below the - * hidirtybuffers mark. We cannot use hidirtybuffers straight - * because being right on the mark will cause getnewbuf() - * to oscillate our wakeup. - * - * The larger the error in either direction, the more we adjust - * bd_flushto and bd_interval. The time interval is adjusted - * by 2 seconds per whole-buffer-range of error. This is an - * exponential convergence algorithm, with large errors - * producing large changes and small errors producing small - * changes. + * Set the interval on a linear scale based on hidirtybuffers + * with a maximum frequency of 1/10 second. */ - - { - int brange = hidirtybuffers - lodirtybuffers; - int middb = hidirtybuffers - brange / 5; - int deltabuf = middb - numdirtybuffers; - - bd_flushto += deltabuf / 20; - bd_interval += deltabuf * (2 * hz) / (brange * 1); - } - if (bd_flushto < lodirtybuffers) - bd_flushto = lodirtybuffers; - if (bd_flushto > hidirtybuffers) - bd_flushto = hidirtybuffers; + bd_interval = bd_flushto * 5 * hz / hidirtybuffers; if (bd_interval < hz / 10) bd_interval = hz / 10; - if (bd_interval > 5 * hz) - bd_interval = 5 * hz; } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 11:59:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 3CB2614F81 for ; Fri, 17 Dec 1999 11:59:30 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA00660; Fri, 17 Dec 1999 12:02:54 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912172002.MAA00660@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: David Gilbert Cc: freebsd-current@freebsd.org Subject: Re: AMI MegaRAID datapoint. In-reply-to: Your message of "Fri, 17 Dec 1999 10:02:57 EST." <14426.20641.329657.464545@trooper.velocet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Dec 1999 12:02:54 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >>>>> "Mike" == Mike Smith writes: > > >> The AMI MegaRAID 1400 delivers between 16.5 and 19 M/s (the 19M/s > >> value is somewhat contrived --- using 8 bonnies in parrallel and > >> then summing their results --- which is not 100% valid)... but the > >> MegaRAID appears to be stable. > > Mike> Hmm. Those numbers aren't so great though. I'd be interested > Mike> to know how busy the controller is during your test (use systat > Mike> -vmstat 1 and look at the amrd0 device), as well as how you've > Mike> configured it. AMI's default configurations for those > Mike> controllers is wildly inconsistent between one BIOS version and > Mike> the next. > > Well... it's RAID-5 across the same 8 drives with all 8 drives on one > LVD chain (same configuration as the other test). I have tried the > 128k stripe, but it was slower than the default 64k stripe. Try enabling DirectIO and WriteBack if you haven't already. AMI's RAID5 implementation seems to suffer from rewriting the entire stripe when you do sub-stripe-sized writes, but I'm not sure about that yet. The Mylex controllers seem to have a small edge in performance, which may be due to them doing cache-line-sized I/Os (usually only 8k) in that case. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Dec 17 12: 6:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 5B5FD157A1 for ; Fri, 17 Dec 1999 12:06:40 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA00768; Fri, 17 Dec 1999 12:09:41 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912172009.MAA00768@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-reply-to: Your message of "Fri, 17 Dec 1999 09:07:56 PST." <199912171707.JAA63193@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Dec 1999 12:09:41 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > :< said: > : > :> the IP and UDP checksum guessing, but more that I think you'll find that > :> a considerable amount of the inbound NFS traffic handling is actually > :> performed in the interrupt context > : > :If it is, then there is a serious bug. > > No serious NFS traffic handling is done in the interrupt context. The > packets are essentially just queued up for nfsd to deal with. That's interesting then, since your results are somewhat at odds with what I've seen so far regarding interrupt load for network traffic. Do you have any profiling results that point the finger more directly at anything? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Dec 17 12:13:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 1E12B157E5; Fri, 17 Dec 1999 12:13:41 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id D8E12137FCB; Fri, 17 Dec 1999 15:13:21 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id PAA27440; Fri, 17 Dec 1999 15:13:21 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14426.39265.260916.742812@trooper.velocet.net> Date: Fri, 17 Dec 1999 15:13:21 -0500 (EST) To: Mike Smith Cc: David Gilbert , freebsd-current@freebsd.org Subject: Re: AMI MegaRAID datapoint. In-Reply-To: <199912172002.MAA00660@mass.cdrom.com> References: <14426.20641.329657.464545@trooper.velocet.net> <199912172002.MAA00660@mass.cdrom.com> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Mike" == Mike Smith writes: Mike> Try enabling DirectIO and WriteBack if you haven't already. Mike> AMI's RAID5 implementation seems to suffer from rewriting the Mike> entire stripe when you do sub-stripe-sized writes, but I'm not Mike> sure about that yet. Already done. This would explain why 128K stripes are bad. Mike> The Mylex controllers seem to have a small edge in performance, Mike> which may be due to them doing cache-line-sized I/Os (usually Mike> only 8k) in that case. Maybe so, but they also don't seem to support the LVD-enabled versions of the Mylex cards. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 12:14:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from sjgw.ipo.att.com (gate.ipo.att.com [135.197.57.2]) by hub.freebsd.org (Postfix) with ESMTP id 0223614F81 for ; Fri, 17 Dec 1999 12:14:46 -0800 (PST) (envelope-from davet@sjgw.ipo.att.com) Received: from localhost. (nomad.ipo.att.com [135.197.41.30]) by sjgw.ipo.att.com (8.8.5/8.8.8) with ESMTP id MAA25478 for ; Fri, 17 Dec 1999 12:14:45 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by localhost. (8.9.3/8.9.3) with ESMTP id MAA01172 for ; Fri, 17 Dec 1999 12:14:45 -0800 (PST) (envelope-from davet@localhost) X-Mailer: exmh version 2.1.0 04/14/1999 From: "Dave Truesdell" To: freebsd-current@FreeBSD.ORG Reply-To: dtruesdell@att.com Subject: Re: ata: Mount root failure: 6 In-reply-to: Your message of "Fri, 17 Dec 1999 18:39:16 +0100." <19991217183916.A83806@cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Dec 1999 12:14:44 -0800 Message-ID: <1160.945461684@localhost> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try this: running an old/working kernel, run disklabel on all your disks/slices and make sure the "badsect" flag is NOT set. I ran into this a couple of nights ago, updating a machine (my laptop) to a current "-current". -- T.T.F.N., Dave Truesdell / dtruesdell@att.com/davet@ttfn.com / UNIX system administrator To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 12:19:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id AD4681578A for ; Fri, 17 Dec 1999 12:19:11 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA01030; Fri, 17 Dec 1999 12:22:37 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912172022.MAA01030@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: David Gilbert Cc: freebsd-current@freebsd.org Subject: Re: AMI MegaRAID datapoint. In-reply-to: Your message of "Fri, 17 Dec 1999 15:13:21 EST." <14426.39265.260916.742812@trooper.velocet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Dec 1999 12:22:37 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike> The Mylex controllers seem to have a small edge in performance, > Mike> which may be due to them doing cache-line-sized I/Os (usually > Mike> only 8k) in that case. > > Maybe so, but they also don't seem to support the LVD-enabled versions > of the Mylex cards. Who is "they" here? We currently support the AcceleRAID 250 (single channel LVD card), and I just committed code to -current that adds support for the AcceleRAID 352 (Ultra160) and eXtremeRAID 1164P (three channel LVD). As I said earlier, we support all of Mylex' currently-shipping RAID controllers (and I expect we'll support the 2000 and 3000 when they finally arrive). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Dec 17 12:33:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 2483C14D5A; Fri, 17 Dec 1999 12:33:30 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id D6FC9137FCC; Fri, 17 Dec 1999 15:33:22 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id PAA27841; Fri, 17 Dec 1999 15:33:22 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14426.40466.484723.608496@trooper.velocet.net> Date: Fri, 17 Dec 1999 15:33:22 -0500 (EST) To: Mike Smith Cc: David Gilbert , freebsd-current@freebsd.org Subject: Re: AMI MegaRAID datapoint... or is it NFS In-Reply-To: <199912172022.MAA01030@mass.cdrom.com> References: <14426.39265.260916.742812@trooper.velocet.net> <199912172022.MAA01030@mass.cdrom.com> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Another thing I've found with the MegaRAID (or maybe this is an nfs thing?) is that large scale (100Mb, full duplex) hits on the NFS server tend to lock up the nfs server (which has the megaraid in it). Typically, this includes not being able to access the non-raid root var and usr partitions. Any ideas? I can reproduce the problem, but it doesn't cause a panic. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 12:41:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9AC3814CB4; Fri, 17 Dec 1999 12:41:16 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA64739; Fri, 17 Dec 1999 12:41:07 -0800 (PST) (envelope-from dillon) Date: Fri, 17 Dec 1999 12:41:07 -0800 (PST) From: Matthew Dillon Message-Id: <199912172041.MAA64739@apollo.backplane.com> To: David Gilbert Cc: Mike Smith , David Gilbert , freebsd-current@FreeBSD.ORG Subject: Re: AMI MegaRAID datapoint... or is it NFS References: <14426.39265.260916.742812@trooper.velocet.net> <199912172022.MAA01030@mass.cdrom.com> <14426.40466.484723.608496@trooper.velocet.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Another thing I've found with the MegaRAID (or maybe this is an nfs :thing?) is that large scale (100Mb, full duplex) hits on the NFS :server tend to lock up the nfs server (which has the megaraid in it). :Typically, this includes not being able to access the non-raid root :var and usr partitions. : :Any ideas? I can reproduce the problem, but it doesn't cause a panic. : :Dave. :|David Gilbert, Velocet Communications. | Two things can only be | You need to figure out what the processes are locked up in. If 'ps axl' doesn't work then you need to ctl-alt-esc into DDB (assuming the kernel is configured for DDB) and do a 'ps' there. It should be possible to narrow the problem down from that output. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 13:23:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 6CE4714D5D for ; Fri, 17 Dec 1999 13:23:22 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id PAA06724; Fri, 17 Dec 1999 15:23:00 -0600 (CST) (envelope-from dick) Date: Fri, 17 Dec 1999 15:23:00 -0600 From: "Richard Seaman, Jr." To: Soren Schmidt Cc: djb@Wit389306.student.utwente.nl, freebsd-current@FreeBSD.ORG Subject: Re: ATA driver problem?? (lost disk contact) Message-ID: <19991217152300.C320@tar.com> References: <19991217072524.B320@tar.com> <199912171328.OAA90417@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912171328.OAA90417@freebsd.dk>; from sos@freebsd.dk on Fri, Dec 17, 1999 at 02:28:29PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 17, 1999 at 02:28:29PM +0100, Soren Schmidt wrote: > Because the wd driver has a 10 secs timeout, and ata has 5 secs. > I think the easiest way to "solve" this is to increase the > timeout to 10-15 secs, as little as I want to do that... I don't really understand disk drivers, so if I'm off base, I apologize. I'm under the impression that you can query the disk to see if its in idle mode, or if not, if its in standby mode. If you leave the timeout at 5 secs, and you actually timeout, perhaps you can check the disk to see if its in standby mode, or in the process of spinning up. If so, for just this case, perhaps you can adjust the timeout to a greater value before retrying the command? Also, perhaps you want to skip printing the diagnostic if the timeout was due to standby/spinup, unless it also fails on retry? -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 14: 4:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail3.teleport.com (mail3.teleport.com [192.108.254.31]) by hub.freebsd.org (Postfix) with SMTP id 8F3EC14C29 for ; Fri, 17 Dec 1999 14:04:39 -0800 (PST) (envelope-from anholt@teleport.com) Received: (qmail 29105 invoked from network); 17 Dec 1999 22:03:36 -0000 Received: from i48-17-41.pdx.du.teleport.com (HELO ?10.1.1.2?) (216.26.6.41) by mail3.teleport.com with SMTP; 17 Dec 1999 22:03:36 -0000 X-Sender: anholt@mail.teleport.com Message-Id: In-Reply-To: <199912171808.SAA02594@vulture.dmem.strath.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 17 Dec 1999 14:08:50 -0800 To: current@freebsd.org From: Eric Anholt Subject: Re: fcnt, ecvt, gcvt and XFree86 2.9.16f build errors Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hi, >The latest XFree86 snapshot, 3.9.16f (which is about to become >the public 3.9.17 snapshot) does not build on FreeBSD -current. > >It compains about fcvt, ecvt and gcvt. >The exact error log from building XFree86 3.9.16f follows. > >It compiles ok on my 3.4 box (just CVSuped) > The problem is that gcc 2.95.2 in -current does not include #define __FreeBSD__ any more. XF can't tell the OS, so it assumes you lack snprintf(), and tries a different way of putting strings into numbers (fcvt, ecvt, gcvt). Check the top of a log from make World to see the OS detection. If you drop a #define __FreeBSD__ in config/cf/Imake.cf, it'll detect and get at least farther along. (still having troubles compiling from their cvs, going to submit a report rsn). Hopefully we can find a bit nicer way of doing things soon. -- Eric Anholt anholt@teleport.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 14:14:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from crystal.advantis.ca (crystal.on.ca.prserv.net [129.37.152.50]) by hub.freebsd.org (Postfix) with ESMTP id 9FBFF15506 for ; Fri, 17 Dec 1999 14:14:16 -0800 (PST) (envelope-from jkendall@Celestica.com) Received: from hivermuet.advantis.ca ([198.74.66.3]) by crystal.advantis.ca (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id RAA50098 for ; Fri, 17 Dec 1999 17:09:09 -0600 From: jkendall@Celestica.com Received: from Celestica.com ([32.69.41.45]) by hivermuet.advantis.ca (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id RAA83948 for ; Fri, 17 Dec 1999 17:06:19 -0600 Received: from tormta3.tor.cel.com (tormta3.tor.cel.com [32.69.41.171]) by Celestica.com (AIX4.2/UCB 8.7/8.7) with SMTP id RAA30966 for ; Fri, 17 Dec 1999 17:12:16 -0500 (EST) Received: by tormta3.tor.cel.com(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 8525684A.0079B1AA ; Fri, 17 Dec 1999 17:09:13 -0500 X-Lotus-FromDomain: CELESTICA To: freebsd-current@FreeBSD.org Message-ID: <8525684A.0079B18A.00@tormta3.tor.cel.com> Date: Fri, 17 Dec 1999 17:12:08 -0500 Subject: 3COM 574BT 10/100 PCMCIA Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I see a few days ago that some one mentioned the 3COM 574BT 10/100 PCMICA card was still not supported. Is this true ??? -------------------------------------------------------------------------------- Jerry T. Kendall, CISSP Celestica International Inc. Manager, Worldwide Information Security 12 Concorde Place, 7th Floor Corporate Information Security Toronto, Ontario, M3C 3R8, CANADA http://www.celestica.com Tel: +1.416.386.7739 jkendall@celestica.com Fax: +1.416.386.7707 -------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 14:21:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id ECFDC14CC2 for ; Fri, 17 Dec 1999 14:21:11 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id OAA02707 for ; Fri, 17 Dec 1999 14:21:10 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id OAA36050 for current@freebsd.org; Fri, 17 Dec 1999 14:21:09 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <199912172221.OAA36050@realtime.exit.com> Subject: Re: 3COM 574BT 10/100 PCMCIA In-Reply-To: <8525684A.0079B18A.00@tormta3.tor.cel.com> from "jkendall@Celestica.com" at "Dec 17, 1999 05:12:08 pm" To: jkendall@Celestica.com Date: Fri, 17 Dec 1999 14:20:51 -0800 (PST) Reply-To: frank@exit.com X-Mailer: ELM [version 2.4ME+ PL54 (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 jkendall@Celestica.com wrote: > I see a few days ago that some one mentioned the 3COM 574BT 10/100 PCMICA card > was still not supported. > Is this true ??? Yes, it's still broken in -current. (I have one, I know.) Matt Dodd has the specs and the NIC (complements of Terry Murphy at 3Com), so it should be fixed Real Soon Now (meaning, when Matt gets to it). -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 15:24:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id 966D314E42 for ; Fri, 17 Dec 1999 15:24:13 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 27227 invoked by uid 1001); 17 Dec 1999 23:23:08 -0000 Date: Fri, 17 Dec 1999 15:23:08 -0800 From: Jason Evans To: freebsd-current@freebsd.org Cc: Alfred Perlstein Subject: Proposed end-all fix for (Re: Make world broken in libc_r) Message-ID: <19991217152308.C26743@sturm.canonware.com> References: <199911271216.OAA01797@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from bright@wintelcom.net on Sat, Nov 27, 1999 at 11:40:08AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 27, 1999 at 11:40:08AM -0800, Alfred Perlstein wrote: > On Sat, 27 Nov 1999, Mark Murray wrote: > > > Hi > > > > "make world" is broken in libc_r. Simple fix is to replace all > > "socklen_t" with "int". > > libc_r likes to pull data from /usr/include instead of the > source tree, "make includes" fixes this. I'm not sure if > that's the correct way to fix it though. I've got a change in the pipeline that will cause world breakage again, unless we do something about this. Is there anything wrong with simply adding: CFLAGS+=-I${.CURDIR}/../../include to lib/libc_r/Makefile? It fixes such build problems. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 15:35: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 8D17A14DC1 for ; Fri, 17 Dec 1999 15:34:59 -0800 (PST) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id A91162CE62; Sat, 18 Dec 1999 01:34:52 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 47C94B6; Sat, 18 Dec 1999 01:34:58 +0200 (EET) Date: Sat, 18 Dec 1999 01:31:34 +0200 From: Vallo Kallaste To: Matthew Dillon Subject: Re: Weird story with dump | restore Message-ID: <19991218013134.A1458@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <19991217123742.A70473@myhakas.matti.ee> <199912171648.IAA29595@gndrsh.dnsmgr.net> <19991217210227.A945@myhakas.matti.ee> <199912171918.LAA64133@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199912171918.LAA64133@apollo.backplane.com>; from Matthew Dillon on Fri, Dec 17, 1999 at 11:18:18AM -0800 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 17, 1999 at 11:18:18AM -0800, Matthew Dillon wrote: > Try this patch to -current, it should solve the problem. I've been > meaning to fixup the buf_daemon for a while. This solves the > buf_daemon problem. We still will not be entirely optimal due to kvm > reshuffling but that's a different problem. Thank you for your clear explanation and patch, I will try it out. Your previous suggestion to lower the dirtybuffers marks was successful. The initial values were 222 for hi and 125 for lowmark. Lowering them by half let the restore run as usual. Now I'm running off from an IBM 35GB disk :-) that's because my response was abit delayed. Thanks -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 17:17:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id E9BAD14A23 for ; Fri, 17 Dec 1999 17:17:32 -0800 (PST) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 0BD091E26; Sat, 18 Dec 1999 02:17:27 +0100 (CET) Date: Sat, 18 Dec 1999 02:17:26 +0100 From: "Dave J. Boers" To: freebsd-current@freebsd.org Subject: Success with ATA drivers and UDMA66 Message-ID: <19991218021726.A931@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I just wanted to let you know that I enabled UDMA66 (by plugging in an 80 conductor cable) on my WDC AC418000D today. The mainboard is an ABit BP6 with builtin Highpoint HPT366 ATA controller. The system works very nicely. I did some heavy testing in single user mode by moving several 300 Mb files around between the IDE disk and my other SCSI disk (which got me a sustained transfer rate of over 10 Mb/sec). Then I made world. Everything works great (softupdates enabled on all filesystems except "/"). If someone wants me to do some specific testing, let me know. Regards, Dave Boers. -- God, root, what's the difference? djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 19: 4:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from pluto.psn.net (pluto.psn.net [207.211.58.12]) by hub.freebsd.org (Postfix) with ESMTP id 68D7714CA6 for ; Fri, 17 Dec 1999 19:04:37 -0800 (PST) (envelope-from will@shadow.blackdawn.com) Received: from 17-031.008.popsite.net ([209.69.196.31] helo=shadow.blackdawn.com) by pluto.psn.net with esmtp (PSN Internet Service 3.12 #1) id 11zAAV-0006X0-00; Fri, 17 Dec 1999 20:04:35 -0700 Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id WAA49525; Fri, 17 Dec 1999 22:04:23 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.3.1 [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: <19991218021726.A931@relativity.student.utwente.nl> Date: Fri, 17 Dec 1999 22:04:22 -0500 (EST) Reply-To: Will Andrews From: Will Andrews To: "Dave J. Boers" Subject: RE: Success with ATA drivers and UDMA66 Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Dec-99 Dave J. Boers wrote: > The system works very nicely. I did some heavy testing in single user mode > by moving several 300 Mb files around between the IDE disk and my other > SCSI disk (which got me a sustained transfer rate of over 10 Mb/sec). Then > I made world. Everything works great (softupdates enabled on all > filesystems except "/"). /proc too? (although technically, /proc isn't a filesystem. ;-) -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 19:18:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 69EBD14D43 for ; Fri, 17 Dec 1999 19:18:44 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA38129; Fri, 17 Dec 1999 19:18:44 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id TAA29762; Fri, 17 Dec 1999 19:18:43 -0800 (PST) (envelope-from obrien) Date: Fri, 17 Dec 1999 19:18:43 -0800 From: "David O'Brien" To: Eric Anholt Cc: current@freebsd.org Subject: Re: fcnt, ecvt, gcvt and XFree86 2.9.16f build errors Message-ID: <19991217191843.A29739@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <199912171808.SAA02594@vulture.dmem.strath.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from anholt@teleport.com on Fri, Dec 17, 1999 at 02:08:50PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 17, 1999 at 02:08:50PM -0800, Eric Anholt wrote: > The problem is that gcc 2.95.2 in -current does not include #define The problem is that /usr/libexec/cpp ... > __FreeBSD__ any more. XF can't tell the OS, so it assumes you lack A fix is on the way RSN. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 20: 8:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from p.wl.vg (209-9-69-194.sdsl.cais.net [209.9.69.194]) by hub.freebsd.org (Postfix) with ESMTP id 9399515222; Fri, 17 Dec 1999 20:08:25 -0800 (PST) (envelope-from patrick@p.wl.vg) Received: (from patrick@localhost) by p.wl.vg (8.9.3/8.9.3) id XAA24609; Fri, 17 Dec 1999 23:08:00 -0500 (EST) (envelope-from patrick) Message-Id: <199912180408.XAA24609@p.wl.vg> Date: Fri, 17 Dec 1999 23:08:00 -0500 (EST) From: patrick@whetstonelogic.com Subject: Sun4c as Xterminal - Problems To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is a question that will test your memories! I'm trying to use a Sun ELC (sun4c) as an Xterminal on my FreeBSD system using Xkernel 2.0. I've used the old howto's from 1996 (Philippe Regnauld) as well as NetBSD diskless howto's to set this up. I've got it working up to a point: It finds it IP address via rarp loads the boot loader via tftp mounts it's root via nfs and boots the kernel. But then it freezes with the message: le0 at SBus slot 0 0xc00000 pri 5 bwtwo0 at SBus slot 3 0x0 pri 7 No bootparam server responding; still trying whoami: pmap_rmtcall status 0x5 Looking at a tcpdump, I see: 22:45:09.936573 sun.wl.vg.1023 > 209.9.69.0.sunrpc: udp 100 repeated frequently. From what I've seen in the mail archives, it's probably a networking issue, and several people asked about it in 1996. But I never found a solution in the archives, only questions. So, does anyone have a fix for this? Back in '96-97, Luigi Rizzo and Mike Smith (among others) seemed to be doing this, so I'm hoping someone still does. Patrick Gardella My setup: 4.0-CURRENT #2: Sun Dec 12 20:35:48 EST 1999 fxp0: flags=8943 mtu 1500 inet 209.9.69.194 netmask 0xffffffe0 broadcast 209.9.69.223 ether 00:90:27:cb:0f:32 media: autoselect (10baseT/UTP) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 20:45:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 8BF5F14D8C for ; Fri, 17 Dec 1999 20:45:44 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id UAA72080; Fri, 17 Dec 1999 20:45:41 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 17 Dec 1999 20:45:40 -0800 (PST) From: Doug White To: Andrew Atrens Cc: current@FreeBSD.ORG Subject: Re: framemaker for linux 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, 16 Dec 1999, Andrew Atrens wrote: > > All, > > This might be a linux ABI question, or it might be an `ld.so' question, > so arguably I could have sent this to emulation, questions or since I run > -current, current, or perhaps hackers, at any rate here goes - > > > I've got `framemaker for linux' and am getting - > > # maker5X.exe > maker5X.exe: error in loading shared libraries > : undefined symbol: __register_frame_info > I believe this is a libc issue. I remember running into this before, although on the FreeBSD ABI (I _think_). Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 21:43: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 3E69914C4A for ; Fri, 17 Dec 1999 21:43:03 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id QAA16413; Sat, 18 Dec 1999 16:42:54 +1100 Date: Sat, 18 Dec 1999 16:42:37 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Pascal Hofstee Cc: freebsd-current@FreeBSD.ORG Subject: Re: minor gcc-issue ? 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 Fri, 17 Dec 1999, Pascal Hofstee wrote: > On Sat, 18 Dec 1999, Bruce Evans wrote: > > > 0301 is an old (bad) way of spelling > > MASK_80387 | MASK_IEEE_FP | MASK_FLOAT_RETURNS. Cygnus finally fixed it in > > in gcc/config/i386/freebsd.h on 1999/03/23 (see the ChangeLog), but FreeBSD > > hasn't merged the change. > > Thanks ... I do have on eother question though ... does this mean that > FreeBSD by default compiles with the -mieee-fp compile switch. As that is Yes. > the solution (for SIGFPE issues) suggested by some Mozilla people on > Bugzilla. Very unlikely. -mieee-fp just fixes comparisons of Quiet NaNs with 0, at a small cost in efficiency. As a side effect, this prevents SIGFPEs for comparisons of Quiet NaNs with 0 when the invalid-operand exception is not masked, but if you have a Quiet NaN, then you are probably running with invalid-operand exceptions masked and wouldn't be worried about SIGFPEs. Quiet NaNs are normally generated by invalid operations, e.g., 0.0/0.0 when the invalid-operand exception is masked. If this exception is unmasked, then 0.0/0.0 generates a SIGFPE and leaves the operands on the FPU stack. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 21:55:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtprch1.nortel.com (smtprch1.nortelnetworks.com [192.135.215.14]) by hub.freebsd.org (Postfix) with ESMTP id 04F8614D9B for ; Fri, 17 Dec 1999 21:55:41 -0800 (PST) (envelope-from atrens@nortelnetworks.com) Received: from zmers013 by smtprch1.nortel.com; Fri, 17 Dec 1999 23:54:16 -0600 Received: from hcarp00g.ca.nortel.com by zmers013; Sat, 18 Dec 1999 00:54:01 -0500 Received: from hcarp00g.ca.nortel.com (hcarp00g.ca.nortel.com [47.196.31.114]) by hcarp00g.ca.nortel.com (8.9.3/8.7.3) with ESMTP id BAA08484; Sat, 18 Dec 1999 01:01:36 -0500 (EST) Date: Sat, 18 Dec 1999 01:01:36 -0500 (EST) From: "Andrew Atrens" X-Sender: atrens@hcarp00g.ca.nortel.com Reply-To: "Andrew Atrens" To: Doug White Cc: current@FreeBSD.ORG Subject: Re: framemaker for linux 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 Fri, 17 Dec 1999, Doug White wrote: > Date: Fri, 17 Dec 1999 20:45:40 -0800 (PST) > From: Doug White > To: "Atrens, Andrew (A.B.) [EXCHANGE:SKY:1U33]" > > Cc: current@FreeBSD.ORG > Subject: Re: framemaker for linux > > On Thu, 16 Dec 1999, Andrew Atrens wrote: > > > > > All, > > > > This might be a linux ABI question, or it might be an `ld.so' question, > > so arguably I could have sent this to emulation, questions or since I run > > -current, current, or perhaps hackers, at any rate here goes - > > > > > > I've got `framemaker for linux' and am getting - > > > > # maker5X.exe > > maker5X.exe: error in loading shared libraries > > : undefined symbol: __register_frame_info > > > > I believe this is a libc issue. I remember running into this before, > although on the FreeBSD ABI (I _think_). Quite possibly since at the root of it, it's a gcc/egcs incompatibility. The problem is described quite nicely in the glibc FAQ - | 2.8. When I run an executable on one system which I compiled on | another, I get dynamic linker errors. Both systems have the same | version of glibc installed. What's wrong? | | {ZW} Glibc on one of these systems was compiled with gcc 2.7 or 2.8, the | other with egcs (any version). Egcs has functions in its internal | `libgcc.a' to support exception handling with C++. They are linked into | any program or dynamic library compiled with egcs, whether it needs them | or | not. Dynamic libraries then turn around and export those functions again | unless special steps are taken to prevent them. | | When you link your program, it resolves its references to the exception | functions to the ones exported accidentally by libc.so. That works fine | as | long as libc has those functions. On the other system, libc doesn't have | those functions because it was compiled by gcc 2.8, and you get undefined | symbol errors. The symbols in question are named things like | `__register_frame_info'. The best thing to do is get the glibc-2.1.2-11.i386.rpm from redhat and install it with - rpm --ignoreos --root=/usr/compat/linux --nodeps -i glibc-2.1.2-11.i386.rpm This version apparently has stubs for __register_frame_info and friends and so will work irregardless of which gcc it was built with. Andrew. -- +-- | Andrew Atrens Nortel Networks, Ottawa, Canada. | | All opinions expressed are my own, not those of any employer. | --+ Heller's Law: The first myth of management is that it exists. Johnson's Corollary: Nobody really knows what is going on anywhere within the organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 17 22:26:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id EC5AE14ED4 for ; Fri, 17 Dec 1999 22:26:54 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 10235985 invoked from network); 18 Dec 1999 06:27:01 -0000 Received: from d027.paris-6.cybercable.fr (HELO cybercable.fr) ([212.198.6.27]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 18 Dec 1999 06:27:01 -0000 Message-ID: <385B2944.6ABE249E@cybercable.fr> Date: Sat, 18 Dec 1999 07:27:16 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: djb@relativity.student.utwente.nl Cc: freebsd-current@freebsd.org Subject: Re: Success with ATA drivers and UDMA66 References: <19991218021726.A931@relativity.student.utwente.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Dave J. Boers" wrote: > > Hi all, > > I just wanted to let you know that I enabled UDMA66 (by plugging in an 80 > conductor cable) on my WDC AC418000D today. The mainboard is an ABit BP6 > with builtin Highpoint HPT366 ATA controller. > > The system works very nicely. I did some heavy testing in single user mode > by moving several 300 Mb files around between the IDE disk and my other > SCSI disk (which got me a sustained transfer rate of over 10 Mb/sec). Then > I made world. Everything works great (softupdates enabled on all > filesystems except "/"). > > If someone wants me to do some specific testing, let me know. > Do you boot from the UDMA66 drive ? What is your BIOS revision ? How many SDARM DIMMs do you use ? What is the rating of your Power supply ? Do you use an AGP graphics board ? (I also have a BP6 and I'm mildly satisfied by its stability up to now, I'm looking for ways to upgrade it and hints to increase the reliability) TfH > Regards, > > Dave Boers. > > -- > God, root, what's the difference? > djb@relativity.student.utwente.nl > > 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 Sat Dec 18 0:32:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id D2C9E14CC5 for ; Sat, 18 Dec 1999 00:32:02 -0800 (PST) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: (from uucp@localhost) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-r-0.1-19990829) with UUCP id RAA79001; Sat, 18 Dec 1999 17:31:48 +0900 (JST) Received: from silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (8.9.3/3.7W) with ESMTP id RAA09390; Sat, 18 Dec 1999 17:12:58 +0900 (JST) Date: Sat, 18 Dec 1999 17:12:57 +0900 Message-ID: <14427.16905.273219.44789W@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> From: Seigo Tanimura To: sgk@troutmask.apl.washington.edu, "Cameron Grant" Cc: tanimura@r.dl.itc.u-tokyo.ac.jp, julian@whistle.com, current@FreeBSD.ORG Subject: Re: pnp, sound and LINT in -current In-Reply-To: In your message of "Thu, 16 Dec 1999 22:30:45 -0800 (PST)" <199912170630.WAA69960@troutmask.apl.washington.edu> References: <14425.40880.275206.81928B@rina.r.dl.itc.u-tokyo.ac.jp> <199912170630.WAA69960@troutmask.apl.washington.edu> Cc: Seigo Tanimura User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Carrots MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Dec 1999 22:30:45 -0800 (PST), Steve Kargl said: Steve> pcm(4) describes Luigi's old pcm driver. Tne newpcm driver is Steve> different and the info pcm(4) does not necessarily apply. Ouch! Cameron, could you write pcm(4) while I do sbc(4), gusc(4) and csa(4)? -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 0:56:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as15-130.rp-plus.de [149.221.237.130]) by hub.freebsd.org (Postfix) with ESMTP id 106AD14EF1 for ; Sat, 18 Dec 1999 00:56:42 -0800 (PST) (envelope-from alex@cichlids.com) Received: by cichlids.com (Postfix, from userid 1001) id 64D6EAB89; Sat, 18 Dec 1999 09:57:09 +0100 (CET) Message-ID: <19991218095709.A88087@cichlids.com> Date: Sat, 18 Dec 1999 09:57:09 +0100 From: Alexander Langer To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: ata: Mount root failure: 6 References: <19991217181226.A83674@cichlids.com> <199912171717.KAA81278@harmony.village.org> <19991217182246.A83740@cichlids.com> <199912171724.KAA81424@harmony.village.org> <19991217183916.A83806@cichlids.com> <199912171753.KAA81703@harmony.village.org> <19991217191603.A83939@cichlids.com> <199912171818.LAA81922@harmony.village.org> <19991217192849.A84075@cichlids.com> <199912171831.LAA82016@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199912171831.LAA82016@harmony.village.org>; from Warner Losh on Fri, Dec 17, 1999 at 11:31:01AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 17, 1999 at 11:31:01AM -0700, Warner Losh wrote: > BTW, what does your /etc/fstab look like? # Device Mountpoint FStype Options Dump Pass# /dev/ad0s1b none swap sw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1e /usr ufs rw 2 2 proc /proc procfs rw 0 0 Is the kernel-config ok? Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 1:21:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as15-185.rp-plus.de [149.221.237.185]) by hub.freebsd.org (Postfix) with ESMTP id 762DA14CB3 for ; Sat, 18 Dec 1999 01:21:34 -0800 (PST) (envelope-from alex@cichlids.com) Received: by cichlids.com (Postfix, from userid 1001) id 0A722AB89; Sat, 18 Dec 1999 10:22:37 +0100 (CET) Message-ID: <19991218102237.A88542@cichlids.com> Date: Sat, 18 Dec 1999 10:22:37 +0100 From: Alexander Langer To: dtruesdell@att.com, freebsd-current@FreeBSD.ORG Subject: Re: ata: Mount root failure: 6 References: <19991217183916.A83806@cichlids.com> <1160.945461684@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <1160.945461684@localhost>; from Dave Truesdell on Fri, Dec 17, 1999 at 12:14:44PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 17, 1999 at 12:14:44PM -0800, Dave Truesdell wrote: > Try this: running an old/working kernel, run disklabel on all your > disks/slices and make sure the "badsect" flag is NOT set. > I ran into this a couple of nights ago, updating a machine (my laptop) to a > current "-current". Hmm. NO. There is no flag set for any slice/disk. What were your problems? Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 1:57:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as15-079.rp-plus.de [149.221.237.79]) by hub.freebsd.org (Postfix) with ESMTP id 3830E14D6A for ; Sat, 18 Dec 1999 01:57:54 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 8EC5DAB7F; Sat, 18 Dec 1999 10:58:56 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id KAA01498; Sat, 18 Dec 1999 10:58:35 +0100 (CET) (envelope-from alex) Date: Sat, 18 Dec 1999 10:58:35 +0100 From: Alexander Langer To: Dave Truesdell Cc: freebsd-current@FreeBSD.ORG Subject: Re: ata: Mount root failure: 6 Message-ID: <19991218105835.A1144@cichlids.cichlids.com> Mail-Followup-To: Dave Truesdell , freebsd-current@FreeBSD.ORG References: <19991217183916.A83806@cichlids.com> <1663.945454803@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <1663.945454803@localhost>; from dtruesdell@att.com on Fri, Dec 17, 1999 at 10:20:03AM -0800 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Dave Truesdell (dtruesdell@att.com): > Try this: running an old/working kernel, run disklabel on all your > disks/slices and make sure the "badsect" flag is NOT set. > I ran into this a couple of nights ago, updating a machine (my laptop) to a > current "-current". I now just build a kernel with the old wd drivers and everything works fine... Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 3:51:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 516E314CAA for ; Sat, 18 Dec 1999 03:51:09 -0800 (PST) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id BD34E1E2A; Sat, 18 Dec 1999 12:51:01 +0100 (CET) Date: Sat, 18 Dec 1999 12:51:01 +0100 From: "Dave J. Boers" To: Thierry Herbelot Cc: freebsd-current@freebsd.org Subject: Re: Success with ATA drivers and UDMA66 Message-ID: <19991218125101.A367@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <19991218021726.A931@relativity.student.utwente.nl> <385B2944.6ABE249E@cybercable.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <385B2944.6ABE249E@cybercable.fr>; from herbelot@cybercable.fr on Sat, Dec 18, 1999 at 07:27:16AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 18, 1999 at 07:27:16AM +0100, Thierry Herbelot wrote: > Do you boot from the UDMA66 drive ? Yes. Bios boot sequence is EXT,C,A; where EXT is set to UDMA66, not SCSI. The SCSI disk is a 4.3 Gb WD Enterprise on an Adaptec 2940AU board. > What is your BIOS revision ? Award Bios v. 4.51PG Revision line (bottom of screen) sais: 06/08/1999-i440BX-W83977-2A69KA1SC-LP Highpoint Bios: HPT 366 v. 1.07 > How many SDRAM DIMMs do you use ? Currently there is one 128 Mb DIMM in the first slot. In a few weeks I will add a 256 Mb DIMM in the second slot, if I can get my hands on one (memory prices are going down again). > What is the rating of your Power supply ? Not quite high enough :-( It's a 300 Watt power supply. > Do you use an AGP graphics board ? Yes. It's a diamond Viper 550 with 8 Mb RAM. > (I also have a BP6 and I'm mildly satisfied by its stability up to now, > I'm looking for ways to upgrade it and hints to increase the > reliability) I haven't got any complaints about the BP6, actually. It runs quite nicely here. Exactly what are your complaints about it (i.e. why do you say "mildly" instead of "wildly")? Regards, Dave Boers. -- God, root, what's the difference? djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 3:53: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 0CCBD14E9A for ; Sat, 18 Dec 1999 03:53:07 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id MAA99496 for current@FreeBSD.org; Sat, 18 Dec 1999 12:49:58 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Sat, 18 Dec 1999 12:49:54 +0100 From: Marcel Moolenaar Message-ID: <385B74E2.66516542@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <199911271216.OAA01797@gratis.grondar.za>, <19991217152308.C26743@sturm.canonware.com> Subject: Re: Proposed end-all fix for (Re: Make world broken in libc_r) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Evans wrote: > > I've got a change in the pipeline that will cause world breakage again, > unless we do something about this. Is there anything wrong with simply > adding: > > CFLAGS+=-I${.CURDIR}/../../include > > to lib/libc_r/Makefile? It fixes such build problems. Yes, anything is wrong. ${DESTDIR}/usr/include is already present in CFLAGS and points to the proper include files. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 5: 6:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id D5ED414BD3; Sat, 18 Dec 1999 05:06:14 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id AAA28764; Sun, 19 Dec 1999 00:05:46 +1100 Date: Sun, 19 Dec 1999 00:05:28 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Takahashi Yoshihiro Cc: marcel@scc.nl, msmith@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: make world is failed on pc98 In-Reply-To: <19991212221111Q.nyan@dd.catv.ne.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 Sun, 12 Dec 1999, Takahashi Yoshihiro wrote: > The 'loader' program is only transplanted for pc98. The boot2 > (sys/boot/pc98/boot2) is the mostly same as the old biosboot > (sys/pc98/boot/biosboot) . > > > boot2 is already capable of loading ELF, right? > > No. I use a modified version of biosboot which is capable of loading ELF. biosboot has many improvements on i386/boot2. E.g., its C source files actually have comments apart from copyrights. > > Isn't it therefore enough to just compile boot2 as ELF? > > No. > > > In other words, what are the problems? > > We need to transplant the new boot2 (sys/boot/i386/boot2) to pc98 to > compile as ELF. I think you only need to compile it to ELF and maybe use btxld instead of dd to strip the headers. It can then load `loader'. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 5:18:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from zappa.demon.nl (zappa.demon.nl [195.173.232.30]) by hub.freebsd.org (Postfix) with ESMTP id ECBA414EE1 for ; Sat, 18 Dec 1999 05:18:50 -0800 (PST) (envelope-from ron@zappa.demon.nl) Received: from win98 (win98.demon.nl [192.168.1.3]) by zappa.demon.nl (Postfix) with SMTP id 43BCA5BBF for ; Sat, 18 Dec 1999 14:20:57 +0100 (CET) Message-ID: <000e01bf495a$58b367a0$0301a8c0@demon.nl> From: "Ron Klinkien" To: Subject: No disks found msg in /stand/sysinstall, how come? Date: Sat, 18 Dec 1999 14:18:17 +0100 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 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is is not possible to configure and add a second disk via the /stand/sysinstall Label and Fdisk menu's? I want to configure a second scsi disk to my system, but I get this message while choosing post-install/fdisk or label: | |[----------------------------- Message -----------------------------]| | | ||No disks found! Please verify that your disk controller is being || | | ||properly probed at boot time. See the Hardware Guide on the || | | ||Documentation menu for clues on diagnosing this type of problem. || | | |}-----------------------------------------------------------(100%)--{| | | || [ OK ] || | | |[--------------------[ Press enter to continue ]--------------------]| | zappa# dmesg|grep da Mounting root from ufs:/dev/da0s1a da1 at ncr0 bus 0 target 6 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da1: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4094MB (8385121 512 byte sectors: 255H 63S/T 521C) zappa# df -k Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 99183 23517 67732 26% / /dev/da0s1h 1205119 704100 404610 64% /d1 /dev/da0s1e 1016303 858091 76908 92% /usr /dev/da0s1f 744175 278633 406008 41% /usr/src /dev/da0s1g 744175 8138 676503 1% /var procfs 4 4 0 100% /proc zappa# uname -a FreeBSD zappa.demon.nl 4.0-CURRENT FreeBSD 4.0-CURRENT #62: Fri Dec 17 20:56:18 CET 1999 ron@zappa.demon.nl:/usr/src/sys/compile/MOON i386 Did I miss something here? Regards, Ron. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 6:21:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id E6E5814F4D for ; Sat, 18 Dec 1999 06:21:20 -0800 (PST) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 8A8772CE64; Sat, 18 Dec 1999 16:21:15 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 42897F7; Sat, 18 Dec 1999 16:21:19 +0200 (EET) Date: Sat, 18 Dec 1999 16:21:19 +0200 From: Vallo Kallaste To: Ron Klinkien Cc: freebsd-current@freebsd.org Subject: Re: No disks found msg in /stand/sysinstall, how come? Message-ID: <19991218162119.A4964@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <000e01bf495a$58b367a0$0301a8c0@demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <000e01bf495a$58b367a0$0301a8c0@demon.nl>; from Ron Klinkien on Sat, Dec 18, 1999 at 02:18:17PM +0100 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 18, 1999 at 02:18:17PM +0100, Ron Klinkien wrote: > Is is not possible to configure and add a second disk via the > /stand/sysinstall > Label and Fdisk menu's? Hmm, yes I got it too. Me thinks it's related to change from block devices to char and to the MAKEDEV. Anybody out there please correct me if I'm wrong. I had to do standard disklabel -rw ad1 auto and after that edit the disklabel by hand. It's certainly not an option if you need more than FreeBSD on your disk. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 8:27:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from zappa.demon.nl (zappa.demon.nl [195.173.232.30]) by hub.freebsd.org (Postfix) with ESMTP id D983D15030 for ; Sat, 18 Dec 1999 08:27:13 -0800 (PST) (envelope-from ron@zappa.demon.nl) Received: from win98 (win98.demon.nl [192.168.1.3]) by zappa.demon.nl (Postfix) with SMTP id 695D35BBF for ; Sat, 18 Dec 1999 17:28:46 +0100 (CET) Message-ID: <000a01bf4974$950797c0$0301a8c0@demon.nl> From: "Ron Klinkien" To: Subject: bootparamd_enable support in rc.conf, anyone? Date: Sat, 18 Dec 1999 17:26:05 +0100 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 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe an idea to implement: bootparamd_enable="NO" # Run bootparamd (or NO). bootparamd_flags="" # Flags to bootparamd. in /etc/rc.conf For the diskless client users among us... Regards, Ron. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 8:50:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id DE17715070 for ; Sat, 18 Dec 1999 08:50:10 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id RAA15668 for freebsd-current@freebsd.org; Sat, 18 Dec 1999 17:50:09 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.9.3/8.9.1) id RAA04225; Sat, 18 Dec 1999 17:31:49 +0100 (MET) (envelope-from j) Date: Sat, 18 Dec 1999 17:31:49 +0100 (MET) Message-Id: <199912181631.RAA04225@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Last ATA checkin broke the IDE drive on my Toshiba Portege X-Original-Newsgroups: local.freebsd.current To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikael Hybsch wrote: > Now it says it's using DMA and after the "Mounting root from ..." message, > I get > ad0: ad_timeout: lost disk contact - resetting > ata0: resetting devices .. > and then it hangs with the disk activity led on. me too Happens on an IBM Thinkpad 755 (older model, 486/75), at the moment sysinstall accesses the disk the first time. Eventually it will then panic for `going to nowhere without my init'. No idea which controller, it's not a PCI machine so nothing known about it. When making ata the default driver, i'd vote for keeping one instance of a wdc driver (disabled by default) so the bottleneck of not being able to install in such a case could be circumvented. If space goes scarce, we could always throw out matcdc, scd, mcd and wt from the installation floppies... I guess their user base has been rapidly fading during the last years. scd is only confusing people anyway since more than one luser so far assumed this stands for `SCSI CD'. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 8:55:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 98154154BC; Sat, 18 Dec 1999 08:54:36 -0800 (PST) (envelope-from mb@imp.ch) Received: from mephisto.imp.ch (mb@mephisto.imp.ch [157.161.1.22]) by mail.imp.ch (8.9.3/8.9.3) with ESMTP id RAA29233; Sat, 18 Dec 1999 17:54:33 +0100 (MET) Received: from localhost (mb@localhost) by mephisto.imp.ch (8.9.3/8.9.3) with ESMTP id RAA10740; Sat, 18 Dec 1999 17:54:31 +0100 (MEZ) Date: Sat, 18 Dec 1999 17:54:31 +0100 From: Martin Blapp To: sos@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: ATA driver problem?? (lost disk contact) 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've bought two new 16GB ATA disks and am not able to boot anymore since wd0 has been retired: Fresh current from today: [...] ad0: ad_timeout: lost disk contact ata0: resetting devices and after it hangs forever. I tried IDE_DELAY=10000 and 15000 but it did not change anything. Break into DDB is not possible. This happens with/without ATA DMA support in the kernel. fuchur# pciconf -l chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x70061022 rev=0x23 hdr=0x00 pcib1@pci0:1:0: class=0x060400 card=0x00000000 chip=0x70071022 rev=0x01 hdr=0x01 isab0@pci0:7:0: class=0x060100 card=0x00000000 chip=0x74081022 rev=0x01 hdr=0x00 ide_pci0@pci0:7:1: class=0x01018a card=0x00000000 chip=0x74091022 rev=0x03 hdr=0x00 chip1@pci0:7:3: class=0x068000 card=0x00000000 chip=0x740b1022 rev=0x03 hdr=0x00 none0@pci0:7:4: class=0x0c0310 card=0x00000000 chip=0x740c1022 rev=0x06 hdr=0x00 de0@pci0:10:0: class=0x020000 card=0x00000000 chip=0x00091011 rev=0x20 hdr=0x00 none1@pci0:11:0: class=0x010000 card=0x10001000 chip=0x000f1000 rev=0x26 hdr=0x00 vga-pci0@pci1:5:0: class=0x030000 card=0x2179102b chip=0x0525102b rev=0x04 hdr=0x00 and the output from the old wd driver: wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 14664MB (30033360 sectors), 29795 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, accel, ovlap, dma, iordis Device wcd0a: name slot allocation failed (Errno=17) Device wcd0c: name slot allocation failed (Errno=17) wcd0: drive speed 5512KB/sec, 256KB cache wcd0: supported read types: CD-R, CD-RW, CD-DA wcd0: Audio: play, 255 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked wdc1 at port 0x170-0x177 irq 15 on isa0 wdc1: unit 0 (wd2): wd2: 14664MB (30033360 sectors), 29795 cyls, 16 heads, 63 S/T, 512 B/S wdc1: unit 1 (atapi): , removable, intr, iordis wfd0: medium type unknown (no disk) wfd0: buggy Zip drive, 64-block transfer limit set Martin PS: I can give you access to the machine if you like. Martin Blapp, mb@imp.ch ------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 10:47:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 43BD514E5E for ; Sat, 18 Dec 1999 10:47:42 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA01876 for ; Sat, 18 Dec 1999 10:49:32 -0800 Date: Sat, 18 Dec 1999 10:49:32 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: general multiarchitectural build question.... 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 my i386 build fell over this morning because it found a .depend that depended on stdio.h for alpha, or: -DKEYCAP_PATH="/usr/share/misc/keycap.pcvt" -I/usr/obj/usr/src/alpha/usr/include keycap.c keycap.o keycap.po keycap.So: keycap.c /usr/obj/usr/src/alpha/usr/include/stdio.h \ /usr/obj/usr/src/alpha/usr/include/sys/cdefs.h \ /usr/obj/usr/src/alpha/usr/include/machine/ansi.h \ /usr/obj/usr/src/alpha/usr/include/ctype.h \ /usr/obj/usr/src/alpha/usr/include/runetype.h keycap.h Now, I share basic source (NFS mounted) for i386 && alpha (hey, it's one spot to CVS update...)... Is a shared read-only source tree supported, or am I abusing my luck here? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 10:52:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id B68BB14EF6 for ; Sat, 18 Dec 1999 10:52:36 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA74512; Sat, 18 Dec 1999 10:52:34 -0800 (PST) (envelope-from dillon) Date: Sat, 18 Dec 1999 10:52:34 -0800 (PST) From: Matthew Dillon Message-Id: <199912181852.KAA74512@apollo.backplane.com> To: Matthew Jacob Cc: current@FreeBSD.ORG Subject: Re: general multiarchitectural build question.... References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :my i386 build fell over this morning because it found a .depend that :depended on stdio.h for alpha, or: : : -DKEYCAP_PATH="/usr/share/misc/keycap.pcvt" -I/usr/obj/usr/src/alpha/usr/include keycap.c :keycap.o keycap.po keycap.So: keycap.c /usr/obj/usr/src/alpha/usr/include/stdio.h \ : /usr/obj/usr/src/alpha/usr/include/sys/cdefs.h \ : /usr/obj/usr/src/alpha/usr/include/machine/ansi.h \ : /usr/obj/usr/src/alpha/usr/include/ctype.h \ : /usr/obj/usr/src/alpha/usr/include/runetype.h keycap.h : : :Now, I share basic source (NFS mounted) for i386 && alpha (hey, it's one :spot to CVS update...)... Is a shared read-only source tree supported, or :am I abusing my luck here? I haven't done any alpha compiles but I use a shared read-only source tree (/usr/src) almost exclusively. The only problem I've ever encountered is that sometimes I accidently build something in the source tree on the server and it leaves garbage files lying around which confuse builds done over the read-only mount (because they can't remove the files). But that's it. One of my favorite tests is to run a -j 8 or -j 12 build world on four or five machines at once from a single NFS mounted /usr/src mounted from the server, with /usr/obj on each machine being a mix of local partitions, R+W NFS mounts, and VN mounts. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 11:43:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id BECF015107; Sat, 18 Dec 1999 11:42:48 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA27487; Sat, 18 Dec 1999 20:42:39 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912181942.UAA27487@freebsd.dk> Subject: Re: ATA driver problem?? (lost disk contact) In-Reply-To: from Martin Blapp at "Dec 18, 1999 05:54:31 pm" To: mb@imp.ch (Martin Blapp) Date: Sat, 18 Dec 1999 20:42:39 +0100 (CET) Cc: sos@freebsd.org, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Martin Blapp wrote: > I've bought two new 16GB ATA disks and am not able to boot > anymore since wd0 has been retired: > > Fresh current from today: > > [...] > ad0: ad_timeout: lost disk contact > ata0: resetting devices > > and after it hangs forever. > > I tried IDE_DELAY=10000 and 15000 but it did not change anything. Hmm, IDE_DELAY is an option for the old wd driver, so thats expected :) > Break into DDB is not possible. This happens with/without > ATA DMA support in the kernel. > > fuchur# pciconf -l > chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x70061022 rev=0x23 hdr=0x00 > pcib1@pci0:1:0: class=0x060400 card=0x00000000 chip=0x70071022 rev=0x01 hdr=0x01 > isab0@pci0:7:0: class=0x060100 card=0x00000000 chip=0x74081022 rev=0x01 hdr=0x00 > ide_pci0@pci0:7:1: class=0x01018a card=0x00000000 chip=0x74091022 rev=0x03 hdr=0x00 > chip1@pci0:7:3: class=0x068000 card=0x00000000 chip=0x740b1022 rev=0x03 hdr=0x00 > none0@pci0:7:4: class=0x0c0310 card=0x00000000 chip=0x740c1022 rev=0x06 hdr=0x00 > de0@pci0:10:0: class=0x020000 card=0x00000000 chip=0x00091011 rev=0x20 hdr=0x00 > none1@pci0:11:0: class=0x010000 card=0x10001000 chip=0x000f1000 rev=0x26 hdr=0x00 > vga-pci0@pci1:5:0: class=0x030000 card=0x2179102b chip=0x0525102b rev=0x04 hdr=0x00 This is an AMD K7 board rigth?, we have no support for AMD's own southbridge... > and the output from the old wd driver: > wdc0: unit 0 (wd0): > wd0: 14664MB (30033360 sectors), 29795 cyls, 16 heads, 63 S/T, 512 B/S So it didn't use multisector nor DMA, what does the ata driver say in the probe ?? > PS: I can give you access to the machine if you like. Well, if the ata driver just hangs the system, there is not much I can do remotely, mayhaps on a serial console, if I can reset it somehow... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 11:45: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 31A8D14FAC for ; Sat, 18 Dec 1999 11:44:59 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA27989; Sat, 18 Dec 1999 20:44:42 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912181944.UAA27989@freebsd.dk> Subject: Re: ATA driver problem?? (lost disk contact) In-Reply-To: <19991217152300.C320@tar.com> from "Richard Seaman, Jr." at "Dec 17, 1999 03:23:00 pm" To: dick@tar.com (Richard Seaman, Jr.) Date: Sat, 18 Dec 1999 20:44:42 +0100 (CET) Cc: djb@Wit389306.student.utwente.nl, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Richard Seaman, Jr. wrote: > On Fri, Dec 17, 1999 at 02:28:29PM +0100, Soren Schmidt wrote: > > > Because the wd driver has a 10 secs timeout, and ata has 5 secs. > > I think the easiest way to "solve" this is to increase the > > timeout to 10-15 secs, as little as I want to do that... > > I don't really understand disk drivers, so if I'm off base, > I apologize. I'm under the impression that you can query the > disk to see if its in idle mode, or if not, if its in standby > mode. If you leave the timeout at 5 secs, and you actually > timeout, perhaps you can check the disk to see if its in > standby mode, or in the process of spinning up. If so, for > just this case, perhaps you can adjust the timeout to a greater > value before retrying the command? Also, perhaps you want to > skip printing the diagnostic if the timeout was due to > standby/spinup, unless it also fails on retry? There is no way to see if the disk was in suspend mode, you can give it a command and se how long it takes before it comes back :) The problem here is that it takes the command and OK's it, but it takes the spinuptime + overhead before the answer comes, and then the driver already timed out. -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 11:46:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 79BC314FC2 for ; Sat, 18 Dec 1999 11:46:12 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA28240; Sat, 18 Dec 1999 20:45:44 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912181945.UAA28240@freebsd.dk> Subject: Re: ata: Mount root failure: 6 In-Reply-To: <19991218105835.A1144@cichlids.cichlids.com> from Alexander Langer at "Dec 18, 1999 10:58:35 am" To: alex@big.endian.de (Alexander Langer) Date: Sat, 18 Dec 1999 20:45:44 +0100 (CET) Cc: dtruesdell@att.com (Dave Truesdell), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Alexander Langer wrote: > Thus spake Dave Truesdell (dtruesdell@att.com): > > > Try this: running an old/working kernel, run disklabel on all your > > disks/slices and make sure the "badsect" flag is NOT set. > > I ran into this a couple of nights ago, updating a machine (my laptop) to a > > current "-current". > > I now just build a kernel with the old wd drivers and everything works > fine... Have you checked the badsect flags then ?? -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 11:53:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 53E7314C11 for ; Sat, 18 Dec 1999 11:53:14 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id UAA25695 for current@FreeBSD.org; Sat, 18 Dec 1999 20:46:00 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Sat, 18 Dec 1999 20:45:55 +0100 From: Marcel Moolenaar Message-ID: <385BE473.ECD2BBED@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: Subject: Re: general multiarchitectural build question.... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > > my i386 build fell over this morning because it found a .depend that > depended on stdio.h for alpha, or: > > -DKEYCAP_PATH="/usr/share/misc/keycap.pcvt" -I/usr/obj/usr/src/alpha/usr/include keycap.c > keycap.o keycap.po keycap.So: keycap.c /usr/obj/usr/src/alpha/usr/include/stdio.h \ > /usr/obj/usr/src/alpha/usr/include/sys/cdefs.h \ > /usr/obj/usr/src/alpha/usr/include/machine/ansi.h \ > /usr/obj/usr/src/alpha/usr/include/ctype.h \ > /usr/obj/usr/src/alpha/usr/include/runetype.h keycap.h > > Now, I share basic source (NFS mounted) for i386 && alpha (hey, it's one > spot to CVS update...)... Is a shared read-only source tree supported, or > am I abusing my luck here? The problem is probably caused by the (former) bug that usr.sbin/pcvt/keycap was built on an Alpha by the libraries target, while pcvt is not built on an Alpha. The bottomline is that libkeycap was built in the source tree. The bug has been fix recently by simply expluding usr/sbin/pcvt/keycap from the libraries target on Alpha. You may want to check the source tree for leftover Alpha files. I had hoped to be able to share the object tree as well, but this requires /usr/obj/${MACHINE_ARCH} as the prefix for all builds, not just the cross-builds. That way you can build an Alpha system on i386 and install it on an Alpha from an NFS mounted object dir. Fortunately, it only a symlink away :-) HTH, -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 12: 6:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 722FC14D81 for ; Sat, 18 Dec 1999 12:06:14 -0800 (PST) (envelope-from mantar@pacbell.net) Received: from dual (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id MAA00318 for ; Sat, 18 Dec 1999 12:06:13 -0800 (PST) (envelope-from mantar@pacbell.net) Message-Id: <4.2.2.19991218120318.00a9a100@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sat, 18 Dec 1999 12:06:13 -0800 To: current@FreeBSD.ORG From: Manfred Antar Subject: Current kernel compile fails Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think this happened when mbuf.h was changed : linking kernel.debug uipc_mbuf.o: In function `m_mballoc_wait': /sys/compile/pro2/../../kern/uipc_mbuf.c(.text+0x2cb): undefined reference to `m_mballoc_wakeup' uipc_mbuf.o: In function `m_clalloc_wait': /sys/compile/pro2/../../kern/uipc_mbuf.c:349: undefined reference to `m_clalloc_wakeup' *** Error code 1 Manfred ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 12:17:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 6AB2515027 for ; Sat, 18 Dec 1999 12:17:54 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id PAA29393; Sat, 18 Dec 1999 15:17:44 -0500 (EST) Date: Sat, 18 Dec 1999 15:17:43 -0500 (EST) From: Bosko Milekic To: Manfred Antar Cc: current@FreeBSD.ORG Subject: Re: Current kernel compile fails In-Reply-To: <4.2.2.19991218120318.00a9a100@pozo.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, 18 Dec 1999, Manfred Antar wrote: !>I think this happened when mbuf.h was changed : !> !>linking kernel.debug !>uipc_mbuf.o: In function `m_mballoc_wait': !>/sys/compile/pro2/../../kern/uipc_mbuf.c(.text+0x2cb): undefined reference !>to `m_mballoc_wakeup' !>uipc_mbuf.o: In function `m_clalloc_wait': !>/sys/compile/pro2/../../kern/uipc_mbuf.c:349: undefined reference to !>`m_clalloc_wakeup' !>*** Error code 1 !> !>Manfred !>===================== !>|| mantar@pacbell.net || !>|| Ph. (415) 681-6235 || !>===================== Yeah, you just caught some bad timing. Re-cvsup, all should be fixed now. :-) ...... . . . . . . . . . . . . . Bosko Milekic -- bmilekic@dsuper.net . . . . . . . . . . . ...... . . WWW: http://pages.infinit.net/bmilekic/ . ................................................ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 13: 3: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 66A0D1506A for ; Sat, 18 Dec 1999 13:02:59 -0800 (PST) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 81EAC1E2A; Sat, 18 Dec 1999 22:02:58 +0100 (CET) Date: Sat, 18 Dec 1999 22:02:58 +0100 From: "Dave J. Boers" To: Soren Schmidt Cc: "Richard Seaman, Jr." , freebsd-current@FreeBSD.ORG Subject: Re: ATA driver problem?? (lost disk contact) Message-ID: <19991218220258.B35095@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <19991217152300.C320@tar.com> <199912181944.UAA27989@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912181944.UAA27989@freebsd.dk>; from sos@freebsd.dk on Sat, Dec 18, 1999 at 08:44:42PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 18, 1999 at 08:44:42PM +0100, Soren Schmidt wrote: > There is no way to see if the disk was in suspend mode, you can > give it a command and se how long it takes before it comes back :) > > The problem here is that it takes the command and OK's it, but it > takes the spinuptime + overhead before the answer comes, and then > the driver already timed out. I am under the impression that the drive does not need to do ADM if it is shutdown once every six days. So can't we go with phk's solution: make a cron job that shuts down and powers up the drive once every six days? Regards, Dave. -- God, root, what's the difference? djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 13:13:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id E7E9B14BDE for ; Sat, 18 Dec 1999 13:13:26 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA49245; Sat, 18 Dec 1999 22:13:20 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912182113.WAA49245@freebsd.dk> Subject: Re: ATA driver problem?? (lost disk contact) In-Reply-To: <19991218220258.B35095@relativity.student.utwente.nl> from "Dave J. Boers" at "Dec 18, 1999 10:02:58 pm" To: djb@Wit389306.student.utwente.nl Date: Sat, 18 Dec 1999 22:13:20 +0100 (CET) Cc: dick@tar.com (Richard Seaman Jr.), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Dave J. Boers wrote: > On Sat, Dec 18, 1999 at 08:44:42PM +0100, Soren Schmidt wrote: > > There is no way to see if the disk was in suspend mode, you can > > give it a command and se how long it takes before it comes back :) > > > > The problem here is that it takes the command and OK's it, but it > > takes the spinuptime + overhead before the answer comes, and then > > the driver already timed out. > > I am under the impression that the drive does not need to do ADM if it is > shutdown once every six days. So can't we go with phk's solution: make a > cron job that shuts down and powers up the drive once every six days? I'd rather just up the timeout to 10s like the old wd driver, that way it apparently isn't a problem anymore, we just wait for the sucker to spin up if needed. -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 14:17:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 6553C14CCB for ; Sat, 18 Dec 1999 14:17:28 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA46080; Sat, 18 Dec 1999 14:17:28 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA09209; Sat, 18 Dec 1999 14:17:28 -0800 (PST) (envelope-from obrien) Date: Sat, 18 Dec 1999 14:17:28 -0800 From: "David O'Brien" To: Ron Klinkien Cc: freebsd-current@freebsd.org Subject: Re: bootparamd_enable support in rc.conf, anyone? Message-ID: <19991218141728.D56211@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <000a01bf4974$950797c0$0301a8c0@demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <000a01bf4974$950797c0$0301a8c0@demon.nl>; from ron@zappa.demon.nl on Sat, Dec 18, 1999 at 05:26:05PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Maybe an idea to implement: > bootparamd_enable="NO" # Run bootparamd (or NO). > bootparamd_flags="" # Flags to bootparamd. I'm more of the opinion to move bootparamd to a port and remove it from the base system. It is evil. Using an ISC-DHCP server to cover DHCP, BOOTP, and booparamd type things is much cleaner. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 14:20:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 1498314EAF for ; Sat, 18 Dec 1999 14:20:56 -0800 (PST) (envelope-from mb@imp.ch) Received: from mephisto.imp.ch (mb@mephisto.imp.ch [157.161.1.22]) by mail.imp.ch (8.9.3/8.9.3) with ESMTP id XAA02480; Sat, 18 Dec 1999 23:20:53 +0100 (MET) Received: from localhost (mb@localhost) by mephisto.imp.ch (8.9.3/8.9.3) with ESMTP id XAA28130; Sat, 18 Dec 1999 23:20:51 +0100 (MEZ) Date: Sat, 18 Dec 1999 23:20:51 +0100 From: Martin Blapp To: Soren Schmidt Cc: current@freebsd.org Subject: Re: ATA driver problem?? (lost disk contact) In-Reply-To: <199912182002.VAA32495@freebsd.dk> 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 Sorry, I found a rather easy workaround. Disable DMA for the disks in the BIOS ... But I still wonder why enable/disable ATA DMA in kernel has no effect for this crash. Why does only the BIOS disable help ? ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 chip1: at device 7.3 on pci0 Strange thing is that the the two disks report themselves different (The disks are identical) and the settings in the BIOS for ata0 and ata1 too ... ad0: ATA-4 disk at ata0 as master ad0: 14664MB (30033360 sectors), 29795 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 32 depth queue, DMA ^^^ why that ? ad2: ATA-4 disk at ata1 as master ad2: 14664MB (30033360 sectors), 29795 cyls, 16 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 32 depth queue, PIO Anyway, so DMA on K7 boards is not supported. Is someone working on this ? Martin Martin Blapp, mb@imp.ch ------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 15:17:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 545BC14EBC for ; Sat, 18 Dec 1999 15:17:34 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id AAA78692; Sun, 19 Dec 1999 00:17:18 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912182317.AAA78692@freebsd.dk> Subject: Re: ATA driver problem?? (lost disk contact) In-Reply-To: from Martin Blapp at "Dec 18, 1999 11:20:51 pm" To: mb@imp.ch (Martin Blapp) Date: Sun, 19 Dec 1999 00:17:18 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Martin Blapp wrote: > > Sorry, > > I found a rather easy workaround. Disable DMA for > the disks in the BIOS ... But I still wonder why > enable/disable ATA DMA in kernel has no effect for > this crash. Why does only the BIOS disable help ? No idea, I have to study AMD's southbridge first.. > ata-pci0: at device 7.1 on pci0 > ata-pci0: Busmastering DMA supported > ata0 at 0x01f0 irq 14 on ata-pci0 > ata1 at 0x0170 irq 15 on ata-pci0 > chip1: at device 7.3 on pci0 > > Strange thing is that the the two disks report themselves > different (The disks are identical) and the settings in the > BIOS for ata0 and ata1 too ... > > ad0: ATA-4 disk at ata0 as master > ad0: 14664MB (30033360 sectors), 29795 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 32 depth queue, DMA > > ^^^ > why that ? > > ad2: ATA-4 disk at ata1 as master > ad2: 14664MB (30033360 sectors), 29795 cyls, 16 heads, 63 S/T, 512 B/S > ad2: 16 secs/int, 32 depth queue, PIO > > Anyway, so DMA on K7 boards is not supported. Is someone working on this ? Its not all K7 boards, those that has the VIA southbridge are supported ie most K7 boards. Its just that nobody has written support for the AMD southbridge yet. It should work in generic mode as the above suggest in PIO or DMA mode, just no UDMA. BTW I need full dmesg's from verbose boots, these snippets are not enough. I'll try to get docs on the AMD southbridge, if so, it should be pretty easy to add support for it... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 15:51: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl4.philips.com (gw-nl4.philips.com [192.68.44.36]) by hub.freebsd.org (Postfix) with ESMTP id A403714EE1 for ; Sat, 18 Dec 1999 15:50:59 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl4.philips.com with ESMTP id AAA19742 for ; Sun, 19 Dec 1999 00:50:58 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl4.philips.com via mwrap (4.0a) id xma019740; Sun, 19 Dec 99 00:50:58 +0100 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with SMTP id AAA14904 for ; Sun, 19 Dec 1999 00:50:58 +0100 (MET) Received: (qmail 31170 invoked by uid 666); 19 Dec 1999 00:03:05 -0000 Date: Sun, 19 Dec 1999 01:03:05 +0100 From: Jos Backus To: freebsd-current@FreeBSD.ORG Subject: Re: make world broken Message-ID: <19991219010305.B53473@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19991216231609.A90209@hal.mpn.cp.philips.com> <385AC788.56641747@heartland.ab.ca> <19991217115334.B11849@hal.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991217115334.B11849@hal.mpn.cp.philips.com>; from Jos.Backus@nl.origin-it.com on Fri, Dec 17, 1999 at 11:53:34AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG More precisely, three things seem to be wrong: - hconfig.h is missing/not being generated. - /usr/include/stdio.h says: extern __const char *__const sys_errlist[]; but /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/system.h says: extern char *sys_errlist[]; possibly because HAVE_STRERROR is not defined at that point. - The PVPROTO macro is not defined at that point; it is defined in /usr/src/contrib/gcc/gansidecl.h as #define PVPROTO(ARGS) PARAMS(ARGS) Is anyone else seeing this? jos:/usr/src# make -f Makefile.inc1 build-tools cd /usr/src/bin/sh; make build-tools cd /usr/src/games/adventure; make build-tools cd /usr/src/games/hack; make build-tools cd /usr/src/games/phantasia; make build-tools cd /usr/src/gnu/usr.bin/cc/cc_tools; make build-tools cd /usr/src/gnu/usr.bin/cc/f771; make build-tools cc -O -pipe -march=pentium -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/src/gnu/usr.bin/cc/f771/../cc_tools -I/usr/src/gnu/usr.bin/cc/f771/../cc_tools -I/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f -I. -c /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/fini.c In file included from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/proj.h:28, from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/fini.c:24: /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/hconfig.j:25: hconfig.h: No such file or directory In file included from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/system.j:25, from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/proj.h:32, from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/fini.c:24: /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/system.h:348: conflicting types for `sys_errlist' /usr/include/stdio.h:225: previous declaration of `sys_errlist' /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/system.h:394: syntax error before `PVPROTO' *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/f771. *** Error code 1 Stop in /usr/src. jos:/usr/src# Thanks, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ 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 Sat Dec 18 15:58:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 4BC5B14CC5 for ; Sat, 18 Dec 1999 15:58:38 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id RAA01430; Sat, 18 Dec 1999 17:58:28 -0600 (CST) (envelope-from dick) Date: Sat, 18 Dec 1999 17:58:28 -0600 From: "Richard Seaman, Jr." To: Martin Blapp Cc: Soren Schmidt , current@FreeBSD.ORG Subject: Re: ATA driver problem?? (lost disk contact) Message-ID: <19991218175828.C317@tar.com> References: <199912182002.VAA32495@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from mb@imp.ch on Sat, Dec 18, 1999 at 11:20:51PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 18, 1999 at 11:20:51PM +0100, Martin Blapp wrote: > > Sorry, > > I found a rather easy workaround. Disable DMA for > the disks in the BIOS ... But I still wonder why > enable/disable ATA DMA in kernel has no effect for > this crash. Why does only the BIOS disable help ? Purely a wild guess on my part: If the BIOS is set to enable UDMA, then the bios sets both the controller and the disk for UDMA. But, the ata driver tries to set the disk to WDMA2 mode for "generic drivers". If the controller is set for UDMA and the disk for WDMA2, they might have problems communicating (the "generic driver" doesn't try to mess with the controller settings, I don't think). However, if the BIOS sets the disk and the controller to PIO, then when the ata drivers uses the "generic" treatment to set the disk to WDMA2, this works since PIO and WDMA2 have similar timings. As I said, this is purely a wild guess from someone who understands all this poorly. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 16:11:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id 427BF14CF3 for ; Sat, 18 Dec 1999 16:11:45 -0800 (PST) (envelope-from pulsifer@mediaone.net) Received: from ahp3 (ahp.ne.mediaone.net [24.128.184.250]) by chmls06.mediaone.net (8.8.7/8.8.7) with SMTP id TAA05180; Sat, 18 Dec 1999 19:11:34 -0500 (EST) From: "Allen Pulsifer" To: Cc: "Soren Schmidt" Subject: RE: ATA driver problem?? (lost disk contact) Date: Sat, 18 Dec 1999 19:11:34 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <199912182113.WAA49245@freebsd.dk> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to the DPTA-3xxxxx spec from IBM, if the drive has fully entered Standby mode, it can take up to 31 seconds for it to spin back up. (See sections 3.3.6.1 and 13.0). Other drive models may take even longer, and even after the drive is back up, it may take a few seconds to respond to the command. You might have to set the timeout value as high as 45-60 seconds in order to get reliable operation. One possibility: the Check Power Mode command (sections 10.5.2 and 12.1) allows you to determine if the drive is in Standby mode. You might be able to timeout after 5-10 seconds, abort the read/write command, do a Check Power Mode command, and if the drive is in the process of spinning back up, then wait patiently for it to come to life before retrying the original read/write command. It looks to me like you would have to do a soft reset (sections 11.0, 9.6 and 10.1) in order to abort the read/write command. A soft reset would also cause the drive to come back to life if it were in Sleep mode (sections 3.3.6, 10.5.1 and 12.31). Note that section 13.0 (page 190) is explicit about this procedure: "We recommend that the host system executes Soft reset and then retry to issue the command if the host system would occur timeout for the device." Hope this helps. Allen > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Soren Schmidt > Sent: Saturday, December 18, 1999 4:13 PM > To: djb@Wit389306.student.utwente.nl > Cc: Richard Seaman Jr.; freebsd-current@FreeBSD.ORG > Subject: Re: ATA driver problem?? (lost disk contact) > > > It seems Dave J. Boers wrote: > > On Sat, Dec 18, 1999 at 08:44:42PM +0100, Soren Schmidt wrote: > > > There is no way to see if the disk was in suspend mode, you can > > > give it a command and se how long it takes before it comes back :) > > > > > > The problem here is that it takes the command and OK's it, but it > > > takes the spinuptime + overhead before the answer comes, and then > > > the driver already timed out. > > > > I am under the impression that the drive does not need to do ADM if it is > > shutdown once every six days. So can't we go with phk's solution: make a > > cron job that shuts down and powers up the drive once every six days? > > I'd rather just up the timeout to 10s like the old wd driver, that way > it apparently isn't a problem anymore, we just wait for the sucker to > spin up if needed. > > -Sĝren > > > 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 Sat Dec 18 16:31:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles522.castles.com [208.214.165.86]) by hub.freebsd.org (Postfix) with ESMTP id B99D414C8A for ; Sat, 18 Dec 1999 16:31:56 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA01419; Sat, 18 Dec 1999 16:35:35 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912190035.QAA01419@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-reply-to: Your message of "Fri, 17 Dec 1999 21:35:12 PST." <199912180535.VAA67191@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Dec 1999 16:35:35 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :That's interesting then, since your results are somewhat at odds with > :what I've seen so far regarding interrupt load for network traffic. Do > :you have any profiling results that point the finger more directly at > :anything? > : > :-- > > Ok, here is the kernel gprof output for one of my -current test > boxes. This one is a duel 450 MHz P-III but running a UP kernel, > and a built-in intel ethernet. ... > I've included the entire gprof output below, but the pertainant section > is #8 and #9 indicating that 19.8% of the cpu is being eaten in the > fxp interrupt code. > > The lion's share appears to be fxp_add_rfabuf(), which takes 10% of > the cpu all by itself (see #11), and most of that appears to be in > the splx() code, which seems bogus but that is what it says. I > presume the splimp()/splx() calls it is making are coming from the > MBUF macros. Hmm, interesting. Do you have a 3C905B kicking around there somewhere that you could repeat the profiling run with? I must admit I hadn't had a chance to look at a profile dump using fxp, and this comes as a bit of a surprise. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Dec 18 16:44:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A010915152; Sat, 18 Dec 1999 16:44:35 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA76031; Sat, 18 Dec 1999 16:44:34 -0800 (PST) (envelope-from dillon) Date: Sat, 18 Dec 1999 16:44:34 -0800 (PST) From: Matthew Dillon Message-Id: <199912190044.QAA76031@apollo.backplane.com> To: Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem References: <199912190035.QAA01419@mass.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hmm, interesting. Do you have a 3C905B kicking around there somewhere :that you could repeat the profiling run with? I must admit I hadn't had :a chance to look at a profile dump using fxp, and this comes as a bit of :a surprise. I have two but they are both on slow machines (read: can't saturate the network) with old (pre signal changes) kernels and I don't have time to upgrade them, so no profiling is possible for now. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 16:56:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id EDE3B14CB7 for ; Sat, 18 Dec 1999 16:56:47 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id TAA22644; Sat, 18 Dec 1999 19:56:46 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id TAA10284; Sat, 18 Dec 1999 19:56:16 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Sat, 18 Dec 1999 19:56:15 -0500 (EST) To: Soren Schmidt Cc: freebsd-current@freebsd.org Subject: ATA: more Promise Ultra wedges X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14428.10180.553556.127603@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG S=F8ren, It looks like I spoke to soon when I said the world was safe for Promise Ultra users: ad3: ad_timeout: lost disk contact - resetting ata4: resetting devices .. ad3: HARD WRITE ERROR blk# 6594768ad3: DMA p= roblem en countered, fallback to PIO mode ad3: DMA problem encountered, fallback to PIO mode done ad1: UDMA CRC READ ERROR blk# 10522095 retrying ad3: ad_timeout: lost disk contact - resetting ata4: resetting devices .. done At this point the machine is unpingable & will not respond to a break on the console. This is with a ccd stripe set, striped across 4 Maxtor "Diamondmax" drives attached one per channel to 2 Promise Ultra cards. `The kernel sources are dated slightly before the build time in= the below boot messages. (I'd have given you verbose messages, but this is a transcript from the serial console logs & the machine is wedged solid right now). I'm running with a timeout of 30 seconds as I was hoping to avoid a 'lost contact - resetting' situation as all hell breaks loose when those appear. BTW, I'd really like a tunable or some way to prevent a permanent fallback to PIO. I'm more than willing to tolerate one hard error per week or so on a disk which sees 10s of gigabytes of data read & written between errors. =20 The driver was much more stable back in July when (I guess) you just ignored errors. Using a July kernel, this machine will stay up for months with nothing but the occasional: ad3: status=3D51 error=3D84 ad_interrupt: hard error It never looses contact, never wedges. Oh for the good old days.. Cheers, Drew -----------------------------------------------------------------------= ------- Andrew Gallatin, Sr Systems Programmer=09http://www.cs.duke.edu/~gallat= in Duke University=09=09=09=09Email: gallatin@cs.duke.edu Department of Computer Science=09=09Phone: (919) 660-6590 Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserve= d. FreeBSD 4.0-CURRENT #2: Wed Dec 15 20:59:01 EST 1999 gallatin@grasshopper.cs.duke.edu:/a/muffin/export/ari_scratch2/gall= atin/src/ sys/compile/SLICEX86 Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 451024869 Hz CPU: Pentium II/Xeon/Celeron (451.02-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x653 Stepping =3D 3 Features=3D0x183fbff real memory =3D 536870912 (524288K bytes) avail memory =3D 517353472 (505228K bytes) Preloaded elf kernel "kernel" at 0xc0305000. ccd0-3: Concatenated disk drivers Pentium Pro MTRR support enabled devclass_alloc_unit: pcib0 already exists, using next available unit nu= mber npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on p= ci0 pci1: on pcib2 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=3D0x8086, dev=3D0= x7112) at 7.2 intpm0: at device 7.3 on pc= i0 intpm0: I/O mapped 440 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 400=20 ata-pci1: irq 10 at device 15.0 on pc= i0 ata-pci1: Busmastering DMA supported ata2 at 0xeff0 irq 10 on ata-pci1 ata3 at 0xefa8 irq 10 on ata-pci1 ata-pci2: irq 11 at device 18.0 on pc= i0 ata-pci2: Busmastering DMA supported ata4 at 0xefa0 irq 11 on ata-pci2 ata5 at 0xef68 irq 11 on ata-pci2 fxp0: irq 10 at device 19.0 o= n pci0 fxp0: Ethernet address 00:a0:c9:e7:9d:f6 devclass_alloc_unit: pci1 already exists, using next available unit num= ber pcib1: on motherboard pci2: on pcib1 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A RTC BIOS diagnostic error 20 ad0: ATA-4 disk at ata0 as master ad0: 4892MB (10018890 sectors), 10602 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad1: ATA-4 disk at ata2 as master ad1: 16479MB (33750864 sectors), 33483 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 ad2: ATA-4 disk at ata3 as master ad2: 16479MB (33750864 sectors), 33483 cyls, 16 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, UDMA33 ad3: ATA-4 disk at ata4 as master ad3: 16479MB (33750864 sectors), 33483 cyls, 16 heads, 63 S/T, 512 B/S ad3: 16 secs/int, 1 depth queue, UDMA33 ad4: ATA-4 disk at ata5 as master ad4: 16479MB (33750864 sectors), 33483 cyls, 16 heads, 63 S/T, 512 B/S ad4: 16 secs/int, 1 depth queue, UDMA33 Mounting root from ufs:/dev/ad0s1a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 17:11:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from cage.tse-online.de (cage.tse-online.de [194.97.69.170]) by hub.freebsd.org (Postfix) with SMTP id 7A63D14A0D for ; Sat, 18 Dec 1999 17:11:34 -0800 (PST) (envelope-from ab@cage.tse-online.de) Received: (qmail 16235 invoked by uid 1000); 19 Dec 1999 01:12:22 -0000 Date: Sun, 19 Dec 1999 02:12:22 +0100 From: Andreas Braukmann To: freebsd-current@FreeBSD.ORG Subject: Re: No disks found msg in /stand/sysinstall, how come? Message-ID: <19991219021222.B15806@cage.tse-online.de> References: <000e01bf495a$58b367a0$0301a8c0@demon.nl> <19991218162119.A4964@myhakas.matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991218162119.A4964@myhakas.matti.ee>; from vallo@matti.ee on Sat, Dec 18, 1999 at 04:21:19PM +0200 Organization: TSE GmbH - Neue Medien Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 18, 1999 at 04:21:19PM +0200, Vallo Kallaste wrote: > On Sat, Dec 18, 1999 at 02:18:17PM +0100, Ron Klinkien > wrote: > > > Is is not possible to configure and add a second disk via the > > /stand/sysinstall Label and Fdisk menu's? ... I got this, too, ... but > > Hmm, yes I got it too. Me thinks it's related to change from block > devices to char and to the MAKEDEV. Anybody out there please > correct me if I'm wrong. I had to do standard disklabel -rw ad1 > auto and after that edit the disklabel by hand. It's certainly not ... just after having the standard disklabel -rw ad0 auto (my boot disk is da0) complained about 'no space left on device'. Yes, ... I did the disklabel -W ad0 ... > an option if you need more than FreeBSD on your disk. -- Eventually I booted from one of my FreeBSD-CDs and got it right ... -Andreas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 17:15: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id C603414D4C for ; Sat, 18 Dec 1999 17:15:03 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id RAA09317; Sat, 18 Dec 1999 17:13:39 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199912190113.RAA09317@troutmask.apl.washington.edu> Subject: Re: make world broken In-Reply-To: <19991219010305.B53473@hal.mpn.cp.philips.com> from Jos Backus at "Dec 19, 1999 01:03:05 am" To: Jos.Backus@nl.origin-it.com (Jos Backus) Date: Sat, 18 Dec 1999 17:13:39 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Jos Backus wrote: > More precisely, three things seem to be wrong: > > - hconfig.h is missing/not being generated. > > - /usr/include/stdio.h says: > > extern __const char *__const sys_errlist[]; > > but /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/system.h says: > > extern char *sys_errlist[]; > > possibly because HAVE_STRERROR is not defined at that point. > > - The PVPROTO macro is not defined at that point; it is defined in > /usr/src/contrib/gcc/gansidecl.h as > > #define PVPROTO(ARGS) PARAMS(ARGS) > > Is anyone else seeing this? > I did a "make -j 4 buildworld" every day last week. I did not see this error. Did you by any chance run configure in the contrib/gcc (or whatever the current gcc contrib source tree is called)? If your build tree ends up in /usr/obj, then you might try rm -rf /usr/obj chflags -r noschg /usr/obj rm -rf /usr/obj cd /usr/src make clean make buildworld -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 17:57:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles522.castles.com [208.214.165.86]) by hub.freebsd.org (Postfix) with ESMTP id 47DF914E72 for ; Sat, 18 Dec 1999 17:57:47 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA01698; Sat, 18 Dec 1999 18:01:21 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912190201.SAA01698@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andreas Braukmann Cc: freebsd-current@FreeBSD.ORG Subject: Re: No disks found msg in /stand/sysinstall, how come? In-reply-to: Your message of "Sun, 19 Dec 1999 02:12:22 +0100." <19991219021222.B15806@cage.tse-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Dec 1999 18:01:21 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, Dec 18, 1999 at 04:21:19PM +0200, Vallo Kallaste wrote: > > > On Sat, Dec 18, 1999 at 02:18:17PM +0100, Ron Klinkien > > wrote: > > > > > Is is not possible to configure and add a second disk via the > > > /stand/sysinstall Label and Fdisk menu's? > ... I got this, too, ... but > > > > Hmm, yes I got it too. Me thinks it's related to change from block > > devices to char and to the MAKEDEV. Anybody out there please > > correct me if I'm wrong. I had to do standard disklabel -rw ad1 > > auto and after that edit the disklabel by hand. It's certainly not Sysinstall is not build with 'make world', and should not be used on a system that's been updated that way. > ... just after having the standard disklabel -rw ad0 auto (my boot disk is > da0) complained about 'no space left on device'. Yes, ... I did the > disklabel -W ad0 ... You forgot to overwrite the beginning of the disk. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Dec 18 17:59:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from beach.silcom.com (beach.silcom.com [199.201.128.19]) by hub.freebsd.org (Postfix) with ESMTP id 6353C15135 for ; Sat, 18 Dec 1999 17:59:19 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Received: from smarter.than.nu (pm0-25.vpop1.avtel.net [207.71.237.25]) by beach.silcom.com (Postfix) with ESMTP id A8ACA14579B for ; Sat, 18 Dec 1999 17:59:15 -0800 (PST) Date: Sat, 18 Dec 1999 17:59:14 -0800 (PST) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: freebsd-current@freebsd.org Subject: New sound driver and Linux games 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 The new sound driver (I'm using pcm0 and sbc0) seems to break a lot of Linux-centric games. Quake2, Q3Test, and snes9x (built from ports) all have choppy, looping sound, and sometimes die with SIGSEGV or SIGBUS soon after starting up. Other programs that use sound, like mpg123, work fine. Everything worked just dandy with the old Voxware driver, but after my latest kernel compile no amount of playing with PNP BIOS settings or driver settings could get it to work. :( Is the new driver perhaps missing some calls that Linux programs expect? -- Brian Buchanan brian@CSUA.Berkeley.EDU -------------------------------------------------------------------------- FreeBSD - The Power to Serve! http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 19:15: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 2587A151AC for ; Sat, 18 Dec 1999 19:15:05 -0800 (PST) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id WAA39972 for ; Sat, 18 Dec 1999 22:15:02 -0500 (EST) (envelope-from culverk@culverk.student.umd.edu) Date: Sat, 18 Dec 1999 22:15:02 -0500 (EST) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: pcm and Vibra16X 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 Alright!! Sound works!! hat's off to the people responsible. One thing though, I noticed that the spectrum analyzer in xmms gets lagged, and I've tried rebuilding libc_r, and xmms to fix it, and neither works, so I'm kinda thinking it may have something to do with the pcm driver. I tried finding what the problem could be, but I'm not too familiar with soundcard programming, so I couldn't find it. This is just to let someone know that sound works, but there are a few little glitches here and there. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 19:50: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id B5F9C14FDC for ; Sat, 18 Dec 1999 19:50:02 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA00904; Sat, 18 Dec 1999 19:50:01 -0800 (PST) (envelope-from dillon) Date: Sat, 18 Dec 1999 19:50:01 -0800 (PST) From: Matthew Dillon Message-Id: <199912190350.TAA00904@apollo.backplane.com> To: freebsd-current@freebsd.org Subject: Correction to /usr/src/sys/i386/conf/LINT for D-Link DFE-530TX+ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The D-Link DFE-530TX+ uses the 'rl' driver, not the 'vr' driver. I don't know if there's a DFE-530TX (without the '+') so I'm leaving the entry for that in the 'vr' driver notes intact. I'll be committing this fixup on sunday. If anyone knows definitively whether the DFE-530TX (without the '+') is even real and, if so, which driver it uses, pleaes emai me. -Matt Matthew Dillon Index: LINT =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/LINT,v retrieving revision 1.702 diff -u -r1.702 LINT --- LINT 1999/12/18 06:27:31 1.702 +++ LINT 1999/12/19 03:35:58 @@ -1665,7 +1665,8 @@ # mode seems to cause severe lockups on SMP hardware. This driver also # supports the Accton EN1207D `Cheetah' adapter, which uses a chip called # the MPX 5030/5038, which is either a RealTek in disguise or a RealTek -# workalike. +# workalike. Note that the D-Link DFE-530TX+ uses the RealTek chipset +# and is supported by this driver, not the 'vr' driver. # # The 'sf' device provides support for Adaptec Duralink PCI fast # ethernet adapters based on the Adaptec AIC-6915 "starfire" controller. @@ -1705,8 +1706,8 @@ # # The `vr' device provides support for various fast ethernet adapters # based on the VIA Technologies VT3043 `Rhine I' and VT86C100A `Rhine II' -# chips, including the D-Link DFE530TX, the Hawking Technologies PN102TX, -# and the AOpen/Acer ALN-320. +# chips, including the D-Link DFE530TX (see 'rl' for DFE530TX+), the Hawking +# Technologies PN102TX, and the AOpen/Acer ALN-320. # # The `vx' device provides support for the 3Com 3C590 and 3C595 # early support To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 19:56: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 54F8614D86 for ; Sat, 18 Dec 1999 19:55:57 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 24916 invoked from network); 19 Dec 1999 03:55:56 -0000 Received: from lcb13.cvzoom.net (63.65.159.13) by ns.cvzoom.net with SMTP; 19 Dec 1999 03:55:56 -0000 Date: Sat, 18 Dec 1999 22:54:45 -0500 (EST) From: Donn Miller To: current@freebsd.org Subject: Question about device ed0 in GENERIC 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 noticed that the ed0 driver is under the categorie of "ISA Ethernet NICs", and that its entry in GENERIC is device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 Well, I've got the Kye Genius 2500III, which uses the ed0 driver, and it's a PCI device. So, I end up using: device ed0 Maybe this should be commented out and entered under the category of # PCI Ethernet NICs Because, I think there are PCI versions of ethernet cards using the ed0 driver. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 19:59:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id CE0EB150DA for ; Sat, 18 Dec 1999 19:59:15 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 25296 invoked from network); 19 Dec 1999 03:59:15 -0000 Received: from lcb13.cvzoom.net (63.65.159.13) by ns.cvzoom.net with SMTP; 19 Dec 1999 03:59:15 -0000 Date: Sat, 18 Dec 1999 22:58:07 -0500 (EST) From: Donn Miller To: current@freebsd.org Subject: Re: Question about device ed0 in GENERIC 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 Sat, 18 Dec 1999, Donn Miller wrote: > Maybe this should be commented out and entered under the category of > > # PCI Ethernet NICs > > Because, I think there are PCI versions of ethernet cards using the ed0 > driver. I can confirm this with dmesg | grep ed0: ed0: irq 10 at device 10.0 on pci0 ed0: address 00:c0:df:ed:0b:17, type NE2000 (16 bit) See? See? It's a PCI card using ed0. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 20: 0:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id 00FDE15166 for ; Sat, 18 Dec 1999 20:00:32 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id 7D61916F; Sat, 18 Dec 1999 20:00:31 -0800 (PST) Date: Sat, 18 Dec 1999 20:00:31 -0800 From: Chris Piazza To: "Brian W. Buchanan" Cc: freebsd-current@FreeBSD.ORG Subject: Re: New sound driver and Linux games Message-ID: <19991218200031.A723@norn.ca.eu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from brian@CSUA.Berkeley.EDU on Sat, Dec 18, 1999 at 05:59:14PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 18, 1999 at 05:59:14PM -0800, Brian W. Buchanan wrote: > The new sound driver (I'm using pcm0 and sbc0) seems to break a lot of > Linux-centric games. Quake2, Q3Test, and snes9x (built from ports) all ^^^^^^^^ not a linux binary. I noticed snes9x's sound acting really weird too earlier today. -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 20: 4:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id B5B771515B for ; Sat, 18 Dec 1999 20:04:36 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id XAA02125; Sat, 18 Dec 1999 23:08:35 -0500 From: Bill Paul Message-Id: <199912190408.XAA02125@skynet.ctr.columbia.edu> Subject: Re: Correction to /usr/src/sys/i386/conf/LINT for D-Link DFE-530TX+ To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sat, 18 Dec 1999 23:08:33 -0500 (EST) Cc: current@freebsd.org In-Reply-To: <199912190350.TAA00904@apollo.backplane.com> from "Matthew Dillon" at Dec 18, 99 07:50:01 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1427 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Matthew Dillon had to walk into mine and say: > The D-Link DFE-530TX+ uses the 'rl' driver, not the 'vr' driver. I > don't know if there's a DFE-530TX (without the '+') so I'm leaving the > entry for that in the 'vr' driver notes intact. Both exist. The DFE-530TX is most definitely a VIA Rhine card and needs the vr driver. I have one. I only recently learned of the existence of the DFE-530TX+, which uses the RealTek 8139 and needs the rl driver. Yes, it's dumb to change the whole card design and do nothing to update the model number except stick a "+" on the end, but that's how it goes. D-Link also has a habit of selling certain cards only some markets. For example, there apparently also exists a DFE-540TX card that uses a Macronix chip, however it was never sold in the U.S., only in Asia. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 20: 7:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 4E83F14D3A for ; Sat, 18 Dec 1999 20:07:53 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id OAA00713 for FreeBSD-current@FreeBSD.ORG; Sun, 19 Dec 1999 14:38:00 +1030 (CST) Date: Sun, 19 Dec 1999 14:38:00 +1030 From: Greg Lehey To: FreeBSD current users Subject: Recent current hangs frequently for 1 to 2 seconds. Message-ID: <19991219143759.C465@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 upgraded to -CURRENT as of yesterday, and I'm noticing a number of occasions where all activity ceases for a second or two at a time; it seems to be related to IDE disk activity with the new ATA driver, but I don't have much evidence. I'm running a SiS 5591 chipset. Has anybody else seen something like this? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 20:12:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 1DAFF150DB for ; Sat, 18 Dec 1999 20:12:29 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 26867 invoked from network); 19 Dec 1999 04:12:19 -0000 Received: from lcb13.cvzoom.net (HELO cvzoom.net) (63.65.159.13) by ns.cvzoom.net with SMTP; 19 Dec 1999 04:12:19 -0000 Message-ID: <385C5ADF.B04A8C74@cvzoom.net> Date: Sat, 18 Dec 1999 23:11:11 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: ESS 1868, newpcm, and Linux RealPlayer 5.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 just rebuilt my kernel from a recent cvsup. Of course, I have device pcm0 device sbc0 in my kernel config file. When I try to play a realaudio clip with Linux rvplayer (RealPlayer 5.0), rvplayer downloads the clip, and instead of playing the clip, rvplayer just hangs until I kill it. Is the ESS 1868 isa card working with sbc0 and pcm0? Anyone else have this problem with rvplayer? I tried the OSS driver modules, and the same rvplayer works OK there. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 20:17: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id F03211503C for ; Sat, 18 Dec 1999 20:17:01 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA01125; Sat, 18 Dec 1999 20:16:53 -0800 (PST) (envelope-from dillon) Date: Sat, 18 Dec 1999 20:16:53 -0800 (PST) From: Matthew Dillon Message-Id: <199912190416.UAA01125@apollo.backplane.com> To: Greg Lehey Cc: FreeBSD current users Subject: Re: Recent current hangs frequently for 1 to 2 seconds. References: <19991219143759.C465@freebie.lemis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I've just upgraded to -CURRENT as of yesterday, and I'm noticing a :number of occasions where all activity ceases for a second or two at a :time; it seems to be related to IDE disk activity with the new ATA :driver, but I don't have much evidence. I'm running a SiS 5591 :chipset. Has anybody else seen something like this? : :Greg It's possible that the blockages you are seeing are due to the ATA driver, but it's also possible that they are due to a bug in the buffer cache flushing code which the following patch fixes. So try the patch and see if that fixes your problem. If it doesn't then we can at least rule it out as being the cause of the problem you are seeing. (This patch is currently slated for commit on Sunday). -Matt Matthew Dillon Index: vfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.237 diff -u -r1.237 vfs_bio.c --- vfs_bio.c 1999/12/01 02:09:29 1.237 +++ vfs_bio.c 1999/12/17 18:44:40 @@ -88,7 +88,7 @@ bufmallocspace, maxbufmallocspace, hibufspace; static int maxbdrun; static int needsbuffer; -static int numdirtybuffers, lodirtybuffers, hidirtybuffers; +static int numdirtybuffers, hidirtybuffers; static int numfreebuffers, lofreebuffers, hifreebuffers; static int getnewbufcalls; static int getnewbufrestarts; @@ -96,8 +96,6 @@ SYSCTL_INT(_vfs, OID_AUTO, numdirtybuffers, CTLFLAG_RD, &numdirtybuffers, 0, ""); -SYSCTL_INT(_vfs, OID_AUTO, lodirtybuffers, CTLFLAG_RW, - &lodirtybuffers, 0, ""); SYSCTL_INT(_vfs, OID_AUTO, hidirtybuffers, CTLFLAG_RW, &hidirtybuffers, 0, ""); SYSCTL_INT(_vfs, OID_AUTO, numfreebuffers, CTLFLAG_RD, @@ -275,6 +273,16 @@ } } +/* + * bd_speedup - speedup the buffer cache flushing code + */ + +static __inline__ +void +bd_speedup(void) +{ + bd_wakeup(1); +} /* * Initialize buffer headers and related structures. @@ -353,7 +361,6 @@ * Reduce the chance of a deadlock occuring by limiting the number * of delayed-write dirty buffers we allow to stack up. */ - lodirtybuffers = nbuf / 7 + 10; hidirtybuffers = nbuf / 4 + 20; numdirtybuffers = 0; /* @@ -365,14 +372,9 @@ * the buffer cache. */ while (hidirtybuffers * BKVASIZE > 3 * hibufspace / 4) { - lodirtybuffers >>= 1; hidirtybuffers >>= 1; buf_maxio >>= 1; } - if (lodirtybuffers < 2) { - lodirtybuffers = 2; - hidirtybuffers = 4; - } /* * Temporary, BKVASIZE may be manipulated soon, make sure we don't @@ -799,9 +801,9 @@ void bwillwrite(void) { - int twenty = (hidirtybuffers - lodirtybuffers) / 5; + int slop = hidirtybuffers / 10; - if (numdirtybuffers > hidirtybuffers + twenty) { + if (numdirtybuffers > hidirtybuffers + slop) { int s; s = splbio(); @@ -1571,9 +1573,8 @@ flags = VFS_BIO_NEED_ANY; } - /* XXX */ + bd_speedup(); /* heeeelp */ - (void) speedup_syncer(); needsbuffer |= flags; while (needsbuffer & flags) { if (tsleep(&needsbuffer, (PRIBIO + 4) | slpflag, @@ -1652,6 +1653,7 @@ static struct proc *bufdaemonproc; static int bd_interval; static int bd_flushto; +static int bd_flushinc; static struct kproc_desc buf_kp = { "bufdaemon", @@ -1672,6 +1674,7 @@ bd_interval = 5 * hz; /* dynamically adjusted */ bd_flushto = hidirtybuffers; /* dynamically adjusted */ + bd_flushinc = 1; while (TRUE) { bd_request = 0; @@ -1694,44 +1697,38 @@ } } - /* - * If nobody is requesting anything we sleep - */ - if (bd_request == 0) - tsleep(&bd_request, PVM, "psleep", bd_interval); + if (bd_request || + tsleep(&bd_request, PVM, "psleep", bd_interval) == 0) { + /* + * Another request is pending or we were woken up + * without timing out. Flush more. + */ + --bd_flushto; + if (bd_flushto >= numdirtybuffers - 5) { + bd_flushto = numdirtybuffers - 10; + bd_flushinc = 1; + } + if (bd_flushto < 2) + bd_flushto = 2; + } else { + /* + * We slept and timed out, we can slow down. + */ + bd_flushto += bd_flushinc; + if (bd_flushto > hidirtybuffers) + bd_flushto = hidirtybuffers; + ++bd_flushinc; + if (bd_flushinc > hidirtybuffers / 20 + 1) + bd_flushinc = hidirtybuffers / 20 + 1; + } /* - * We calculate how much to add or subtract from bd_flushto - * and bd_interval based on how far off we are from the - * optimal number of dirty buffers, which is 20% below the - * hidirtybuffers mark. We cannot use hidirtybuffers straight - * because being right on the mark will cause getnewbuf() - * to oscillate our wakeup. - * - * The larger the error in either direction, the more we adjust - * bd_flushto and bd_interval. The time interval is adjusted - * by 2 seconds per whole-buffer-range of error. This is an - * exponential convergence algorithm, with large errors - * producing large changes and small errors producing small - * changes. + * Set the interval on a linear scale based on hidirtybuffers + * with a maximum frequency of 1/10 second. */ - - { - int brange = hidirtybuffers - lodirtybuffers; - int middb = hidirtybuffers - brange / 5; - int deltabuf = middb - numdirtybuffers; - - bd_flushto += deltabuf / 20; - bd_interval += deltabuf * (2 * hz) / (brange * 1); - } - if (bd_flushto < lodirtybuffers) - bd_flushto = lodirtybuffers; - if (bd_flushto > hidirtybuffers) - bd_flushto = hidirtybuffers; + bd_interval = bd_flushto * 5 * hz / hidirtybuffers; if (bd_interval < hz / 10) bd_interval = hz / 10; - if (bd_interval > 5 * hz) - bd_interval = 5 * hz; } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 20:25:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 426B3151C5 for ; Sat, 18 Dec 1999 20:25:54 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id OAA02141; Sun, 19 Dec 1999 14:55:51 +1030 (CST) Date: Sun, 19 Dec 1999 14:55:51 +1030 From: Greg Lehey To: Matthew Dillon Cc: FreeBSD current users Subject: Re: Recent current hangs frequently for 1 to 2 seconds. Message-ID: <19991219145550.D465@freebie.lemis.com> References: <19991219143759.C465@freebie.lemis.com> <199912190416.UAA01125@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199912190416.UAA01125@apollo.backplane.com> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Saturday, 18 December 1999 at 20:16:53 -0800, Matthew Dillon wrote: > :I've just upgraded to -CURRENT as of yesterday, and I'm noticing a > :number of occasions where all activity ceases for a second or two at a > :time; it seems to be related to IDE disk activity with the new ATA > :driver, but I don't have much evidence. I'm running a SiS 5591 > :chipset. Has anybody else seen something like this? > : > :Greg > > It's possible that the blockages you are seeing are due to the ATA > driver, but it's also possible that they are due to a bug in the > buffer cache flushing code which the following patch fixes. So try > the patch and see if that fixes your problem. If it doesn't then > we can at least rule it out as being the cause of the problem you > are seeing. Thanks. I'll do that Real Soon Now. BTW, it looks as if the disk activity was on SCSI disks, so the ATA driver is probably a red herring. > (This patch is currently slated for commit on Sunday). It *is* Sunday :-) Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 20:41:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B067914BDE for ; Sat, 18 Dec 1999 20:41:42 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA06336; Sat, 18 Dec 1999 21:41:41 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA00896; Sat, 18 Dec 1999 21:41:41 -0700 (MST) Message-Id: <199912190441.VAA00896@harmony.village.org> To: Alexander Langer Subject: Re: ata: Mount root failure: 6 Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 18 Dec 1999 09:57:09 +0100." <19991218095709.A88087@cichlids.com> References: <19991218095709.A88087@cichlids.com> <19991217181226.A83674@cichlids.com> <199912171717.KAA81278@harmony.village.org> <19991217182246.A83740@cichlids.com> <199912171724.KAA81424@harmony.village.org> <19991217183916.A83806@cichlids.com> <199912171753.KAA81703@harmony.village.org> <19991217191603.A83939@cichlids.com> <199912171818.LAA81922@harmony.village.org> <19991217192849.A84075@cichlids.com> <199912171831.LAA82016@harmony.village.org> Date: Sat, 18 Dec 1999 21:41:41 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The fstab looks good : Is the kernel-config ok? I didn't see anything wrong with it, but maybe soren should take a close look. This stuff definitely works for me on my laptop. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 20:43:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7FCF314C82 for ; Sat, 18 Dec 1999 20:43:53 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA06345; Sat, 18 Dec 1999 21:43:52 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA00923; Sat, 18 Dec 1999 21:43:52 -0700 (MST) Message-Id: <199912190443.VAA00923@harmony.village.org> Subject: Re: ata: Mount root failure: 6 Cc: Alexander Langer , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 18 Dec 1999 21:41:41 MST." Date: Sat, 18 Dec 1999 21:43:51 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -------- Warner Losh writes: : : The fstab looks good : : : Is the kernel-config ok? : : I didn't see anything wrong with it, but maybe soren should take a : close look. This stuff definitely works for me on my laptop. Hate to follow up myself, but what boot blocks are you using? Really old ones use the disk label to determine what root device to pass to the kernel, and maybe that's where the problem lies? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 20:47:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from beach.silcom.com (beach.silcom.com [199.201.128.19]) by hub.freebsd.org (Postfix) with ESMTP id 32B0A151CA for ; Sat, 18 Dec 1999 20:47:12 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Received: from smarter.than.nu (pm0-37.vpop1.avtel.net [207.71.237.37]) by beach.silcom.com (Postfix) with ESMTP id 9350E14589B; Sat, 18 Dec 1999 20:47:01 -0800 (PST) Date: Sat, 18 Dec 1999 20:47:00 -0800 (PST) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: Chris Piazza Cc: freebsd-current@FreeBSD.ORG Subject: Re: New sound driver and Linux games In-Reply-To: <19991218200031.A723@norn.ca.eu.org> 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, 18 Dec 1999, Chris Piazza wrote: > On Sat, Dec 18, 1999 at 05:59:14PM -0800, Brian W. Buchanan wrote: > > The new sound driver (I'm using pcm0 and sbc0) seems to break a lot of > > Linux-centric games. Quake2, Q3Test, and snes9x (built from ports) all > ^^^^^^^^ > not a linux binary. > > I noticed snes9x's sound acting really weird too earlier today. Yeah, I know snes9x isn't a linux binary, but it was written with Linux (and hence its sound system) in mind, not portability. snes9x plays about a half second of audio for me, then loops it a few times before dying with either SIGBUS or SIGSEGV. I've tried rebuilding it in case it had something to do with include file changes, but no dice. -- Brian Buchanan brian@CSUA.Berkeley.EDU -------------------------------------------------------------------------- FreeBSD - The Power to Serve! http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 21:13:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from fepa.mail.ozemail.net (fepa.mail.ozemail.net [203.2.192.101]) by hub.freebsd.org (Postfix) with ESMTP id 2998D14D43 for ; Sat, 18 Dec 1999 21:13:39 -0800 (PST) (envelope-from c9710216@atlas.newcastle.edu.au) Received: from atlas.newcastle.edu.au (slnew54p31.ozemail.com.au [203.108.151.47]) by fepa.mail.ozemail.net (8.9.0/8.6.12) with ESMTP id QAA15410; Sun, 19 Dec 1999 16:13:08 +1100 (EST) Message-ID: <385C76C2.4026575@atlas.newcastle.edu.au> Date: Sun, 19 Dec 1999 17:10:10 +1100 From: "Jacob A. Hart" X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Brian W. Buchanan" Cc: Chris Piazza , freebsd-current@FreeBSD.ORG Subject: Re: New sound driver and Linux games Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 18 Dec 1999, Chris Piazza wrote: > > > On Sat, Dec 18, 1999 at 05:59:14PM -0800, Brian W. Buchanan wrote: > > > The new sound driver (I'm using pcm0 and sbc0) seems to break a lot of > > > Linux-centric games. Quake2, Q3Test, and snes9x (built from ports) all > > ^^^^^^^^ > > not a linux binary. > > > > I noticed snes9x's sound acting really weird too earlier today. > > Yeah, I know snes9x isn't a linux binary, but it was written with Linux > (and hence its sound system) in mind, not portability. snes9x plays about > a half second of audio for me, then loops it a few times before dying with > either SIGBUS or SIGSEGV. I've tried rebuilding it in case it had > something to do with include file changes, but no dice. > I don't think the looping/flangy audio in Q3Test is entirely the FreeBSD sound driver's problem. I have a friend who runs Linux and uses the ALSA (Advanced Linux Sound Architecture) driver. According to him, the ALSA driver suffers from the same symtoms our sbc/pcm combo does when playing Q3Test. I don't know if he's tried running Q2 or snes9x using ALSA drivers though. It could be that the OSS Voxware driver does something "unintentional" that some programmers are relying on. Unreal Tournament and XMAME audio works fine under newpcm, for instance. Strange. -jake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 21:48:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id DB75214CB7 for ; Sat, 18 Dec 1999 21:48:39 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id VAA60338; Sat, 18 Dec 1999 21:45:32 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912190545.VAA60338@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jacob A. Hart" Cc: "Brian W. Buchanan" , Chris Piazza , freebsd-current@FreeBSD.ORG Subject: Re: New sound driver and Linux games In-reply-to: Your message of "Sun, 19 Dec 1999 17:10:10 +1100." <385C76C2.4026575@atlas.newcastle.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Dec 1999 21:45:32 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It could be that the OSS Voxware driver does something "unintentional" > that some programmers are relying on. Unreal Tournament and XMAME audio > works fine under newpcm, for instance. > > Strange. Not really . Just go to http://www.opensound.com and look at their api in addition you have the old voxware sound driver in the kernel to look at . I made Quake and Quake 2 work with the voxware sound driver and it was not that hard . -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 18 23:38:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id A180015203 for ; Sat, 18 Dec 1999 23:38:50 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id XAA47598; Sat, 18 Dec 1999 23:38:49 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id XAA16267; Sat, 18 Dec 1999 23:38:49 -0800 (PST) (envelope-from obrien) Date: Sat, 18 Dec 1999 23:38:49 -0800 From: "David O'Brien" To: Bruce Evans Cc: freebsd-current@FreeBSD.ORG Subject: Re: minor gcc-issue ? Message-ID: <19991218233849.A15754@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from bde@zeta.org.au on Sat, Dec 18, 1999 at 02:43:03AM +1100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 18, 1999 at 02:43:03AM +1100, Bruce Evans wrote: > 0301 is an old (bad) way of spelling > MASK_80387 | MASK_IEEE_FP | MASK_FLOAT_RETURNS. Cygnus finally fixed it in > in gcc/config/i386/freebsd.h on 1999/03/23 (see the ChangeLog), but FreeBSD > hasn't merged the change. Actually Cygnus hasn't merged it. Cygnus's gcc/config/i386/freebsd.h is our gcc/config/i386/freebsd-aout.h. Their gcc/config/i386/freebsd-elf.h is our gcc/config/i386/freebsd.h. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message