From owner-freebsd-hackers Sun Nov 8 03:20:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA26452 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 03:06:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA26422; Sun, 8 Nov 1998 03:06:11 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.59.121]) by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA2D1B; Sun, 8 Nov 1998 12:05:55 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 08 Nov 1998 12:09:55 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current , FreeBSD Hackers Subject: AWE-32 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, sorry for posting to two lists, but the problem might or might not be relevant to CURRENT. Couldn't determine yet. Problem is, I was trying to set-up my SoundBlaster AWE-32, when rebooting I got the fooling stuff at probing: Probing for PnP devices: CSN 1 Vendor ID: CTL009c [0x9c008c0e] Serial 0x10046cf4 Comp ID: PNP0600 [0x0006d041] sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at ? drq 5 on isa snd0: sbmidi0 at 0x330 on isa snd0: awe0 at 0x620 on isa AWE32: not detected Hold it! That's awkward... controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device awe0 at isa? port 0x620 Am I missing something in here? --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl Junior Network/Security Specialist *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 04:48:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA08965 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 04:48:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08960; Sun, 8 Nov 1998 04:48:19 -0800 (PST) (envelope-from matt@zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.8.8/8.8.8) with SMTP id HAA01787; Sun, 8 Nov 1998 07:52:34 -0500 (EST) (envelope-from matt@zigg.com) Date: Sun, 8 Nov 1998 07:52:34 -0500 (EST) From: Matt Behrens To: doc@FreeBSD.ORG cc: "Jordan K. Hubbard" , Chad David , hackers@FreeBSD.ORG Subject: Re: Documentation (was Re: freebsd-hackers-digest V4 #299) In-Reply-To: <19981107213933.43220@nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 7 Nov 1998, Nik Clayton wrote: > Absolutely. DocBook is designed for exactly that sort of technical > documentation. In fact, Someone on -doc recently made the suggestion > that we shift the manual pages from *roff format to DocBook. That's > possibly a touch too controversial at the moment, but might not be > beyond the bounds of possiblity for the medium term future. > > In fact, it might be worth doing that within the Doc. Project, treating > them as another translation (similar to the Japanese translation) of > the manual pages? The approach I think that could be taken for the manpages is not necessarily to treat DocBook as a translation but as the _source_ for all the other translations, including the *roff that could still be used (for efficiency's and compatibility's sake) on the actual system. I would require quite a bit of initial investment but would really pay off when our handbook would come attached to and be able to cross-reference within itself to all of our standard manpages. Matt Behrens | If only I could learn Japanese and get my Servant of Karen Behrens | hands on all 200 Sailor Moon episodes and Engineer, Nameless IRC Network | all the movies, I think my life would I eat Penguins for breakfast. | finally be complete. . . . . . . . . . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 05:02:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA10162 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 05:02:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA10121 for ; Sun, 8 Nov 1998 05:02:43 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (brian@woof.lan.Awfulhak.org [172.16.0.7]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id NAA18467 for ; Sun, 8 Nov 1998 13:02:28 GMT (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1]) by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id KAA23159 for ; Sun, 8 Nov 1998 10:14:22 GMT (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199811081014.KAA23159@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@FreeBSD.ORG Subject: bind()/listen() race Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Nov 1998 10:14:22 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, If I create a local domain socket with bind(), there's a period between that and the listen() where a connect() will fail. Is there any way to circumvent the problem ? Cheers. -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 07:09:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19016 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 07:09:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19011 for ; Sun, 8 Nov 1998 07:09:34 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:lY9bMqg8+rHX1W9SGgQbG/XYVRU6kKJl@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id AAA12416; Mon, 9 Nov 1998 00:09:15 +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 AAA16053; Mon, 9 Nov 1998 00:10:43 +0900 (JST) Message-Id: <199811081510.AAA16053@zodiac.mech.utsunomiya-u.ac.jp> To: Nik Clayton cc: hackers@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: text mode screen grabber? In-reply-to: Your message of "Sat, 07 Nov 1998 15:29:28 GMT." <19981107152928.28834@nothing-going-on.org> References: <19981107152928.28834@nothing-going-on.org> Date: Mon, 09 Nov 1998 00:10:42 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Has anyone got (or have pointers to useful code) a screen grabber for >syscons? Ideally (and given an 80x25 screen) I'm looking for something >that would write a 4000 byte file of { character code, colour } tuples. [...] Have you considered script(1), a standard command, or `screen', which is in the port collection, I expect? >If I was doing this in DOS, I'd just set a pointer to 0xb80000000 and >write the next 4000 bytes. I figure I can do this (as a root process) by >opening /dev/kmem. Yes, you can read the phyiscal screen buffer via /dev/mem and mmap(). p = (u_int16_t *)mmap(0, 0x10000, PROT_READ, MAP_FILE, open("/dev/mem", O_RDWR), 0xA0000); However, it is not usually recommended to peek around physical memory while there is a perfectly feasible way of carrying out the same task (by using regular programs such as `script' and `screen'). >virtual terminals will presumably screw this up. You can lock out syscons while you are reading from the physical screen buffer by issuing a pair of ioctl commands. ioctl(fd, KDSETMODE, KD_GRAPHICS); This will tell syscons your program want full control of the video card. Don't be alarmed by the term "KD_GRAPHICS". This ioctl will NOT put the video card in a graphics mode; it simply marks the current virtual terminal that the user-land program is controlling the video card, and syscons will not try to update the screen appearance or switch away to another virtual terminal. Your program can do anything you like to the video card now. When finished reading the screen buffer, call ioctl(fd, KDSETMODE, KD_TEXT); to release the video card. Make sure this ioctl will be issued before the program exists, otherwise you will not be able to switch between virtual terminals again. >I've had a look at the syscons code, and some of the screen savers, but >nothing's leaping out at me saying "Here, this is where the screen >buffer is. . .". No, I don't think you should directly read the internal data structure. Its format may be different between versions. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 11:07:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08737 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 11:07:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08714; Sun, 8 Nov 1998 11:07:22 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbws.vastnet.net (port17.netsvr1.cst.vastnet.net [207.252.73.17]) by etinc.com (8.8.8/8.6.9) with SMTP id OAA08632; Sun, 8 Nov 1998 14:07:03 GMT Message-Id: <3.0.32.19981108140828.006961f0@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 08 Nov 1998 14:08:30 -0500 To: hackers@FreeBSD.ORG From: Dennis Subject: Admin GUI Cc: isp@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone written a remotely excutable GUI for doing basic admin tasks like adding users? Something HTML based maybe? thanks, dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 11:16:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09685 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 11:16:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wolf.com (ns1.wolf.com [207.137.58.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA09674 for ; Sun, 8 Nov 1998 11:16:41 -0800 (PST) (envelope-from dan@wolf.com) Received: (qmail 12579 invoked by uid 100); 8 Nov 1998 19:25:10 -0000 Message-ID: <19981108112509.A12566@wolf.com> Date: Sun, 8 Nov 1998 11:25:09 -0800 From: Dan Mahoney To: Dennis , hackers@FreeBSD.ORG Cc: isp@FreeBSD.ORG Subject: Re: Admin GUI References: <3.0.32.19981108140828.006961f0@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <3.0.32.19981108140828.006961f0@etinc.com>; from Dennis on Sun, Nov 08, 1998 at 02:08:30PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Has anyone written a remotely excutable GUI for doing basic admin > tasks like adding users? Something HTML based maybe? You might want to take a look at http://www.webmin.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 11:18:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09884 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 11:18:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles209.castles.com [208.214.165.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09853; Sun, 8 Nov 1998 11:18:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA03029; Sun, 8 Nov 1998 11:17:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811081917.LAA03029@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dennis cc: hackers@FreeBSD.ORG, isp@FreeBSD.ORG Subject: Re: Admin GUI In-reply-to: Your message of "Sun, 08 Nov 1998 14:08:30 EST." <3.0.32.19981108140828.006961f0@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Nov 1998 11:17:01 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Has anyone written a remotely excutable GUI for doing basic admin > tasks like adding users? Something HTML based maybe? Try a search on freshmeat.net for 'webmin'. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 11:45:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12798 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 11:45:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alive.znep.com (207-178-54-226.go2net.com [207.178.54.226] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12793 for ; Sun, 8 Nov 1998 11:45:40 -0800 (PST) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.1/8.9.1) with ESMTP id LAA07689; Sun, 8 Nov 1998 11:37:37 -0800 (PST) (envelope-from marcs@znep.com) Date: Sun, 8 Nov 1998 11:37:37 -0800 (PST) From: Marc Slemko To: Brian Somers cc: freebsd-hackers@FreeBSD.ORG Subject: Re: bind()/listen() race In-Reply-To: <199811081014.KAA23159@woof.lan.awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Nov 1998, Brian Somers wrote: > If I create a local domain socket with bind(), there's a period > between that and the listen() where a connect() will fail. Is there > any way to circumvent the problem ? Why is it a problem to have connects fail before you listen() but not a problem to have them fail before you bind()? I'm not sure I see the race condition. Once you listen(), you can accept connections. Before you listen(), you can't. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 11:56:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13944 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 11:56:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13926; Sun, 8 Nov 1998 11:56:13 -0800 (PST) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id OAA22274; Sun, 8 Nov 1998 14:56:00 -0500 (EST) Date: Sun, 8 Nov 1998 14:55:54 -0500 (EST) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Dennis cc: hackers@FreeBSD.ORG, isp@FreeBSD.ORG Subject: Re: Admin GUI In-Reply-To: <3.0.32.19981108140828.006961f0@etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG netmax isa GREAT product if your looking at a compelte solution rather thatn JUST the GUI. http://www.netmax.com Chris -- "You both seem to be ignoring the fact that the networking market is driven by so-called 'IT professionals' these days, most of whom can't tell the difference between an ARP and a carp." --Wes Peters ===================================| Open Systems FreeBSD Consulting. FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186 -----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 13:26:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23616 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 13:26:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from trifork.gu.net (trifork.gu.net [194.93.191.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23555; Sun, 8 Nov 1998 13:26:18 -0800 (PST) (envelope-from fbsd@trifork.gu.net) Received: from localhost (localhost.gu.net [127.0.0.1]) by trifork.gu.net (8.9.1/8.9.1) with ESMTP id AAA11419; Mon, 9 Nov 1998 00:28:01 +0303 (UST) (envelope-from fbsd@trifork.gu.net) Date: Sun, 8 Nov 1998 23:25:57 +0200 (EET) From: Andrew Stesin Reply-To: fbsd@trifork.gu.net To: hackers@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Semi-realtime programming Q (RS-232, timers) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, sorry for asking probably a FAQ, this is somewhat general question. Maybe you'll drop just a word or two with a pointer to a sample code? I'm now implementing (almost close to a victory :) a protocol for communication with an external device(s) over RS-232 serial port(s). FreeBSD-3.0, of course. :) Comparatively simple protocol, character oriented, but not that dumb at all. What I need is to implement multiple timers for protocl FSM to react onto, first for inter-character timeout on input, second one for write timeout, and several more "global" ones like the "link idle" timeout etc. Modelling an approach of Harvest (or Squid) seems to be a bit of overkill (or is it the only way to go?). I tried to use select() for read/write operations, and ualarm() for "bigger" ones, but the mix won't work (SIGALRM breaks select(), sure...) Or shall I drop select() and use ualarm() and longjmp()? What I badly need is a pointer to some really well-done implementation (I'll look at userland PPP now, maybe other ones?) of a similar purpose, to use as a reference. And yes, as soon as I'll implement this successfully, I'll most probably will make this thingy available under BSD-style license, maybe someone will include this in the distribution or as a port, at least. :) -- Best regards, Andrew Stesin nic-hdl: ST73-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 14:30:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29664 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 14:30:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (tex-84.camalott.com [208.229.74.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29648 for ; Sun, 8 Nov 1998 14:30:44 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id QAA18067; Sun, 8 Nov 1998 16:29:40 -0600 (CST) (envelope-from joelh) To: fbsd@trifork.gu.net Cc: hackers@FreeBSD.ORG Subject: Re: Semi-realtime programming Q (RS-232, timers) References: From: Joel Ray Holveck Date: 08 Nov 1998 16:29:39 -0600 In-Reply-To: Andrew Stesin's message of "Sun, 8 Nov 1998 23:25:57 +0200 (EET)" Message-ID: <86iugpx1gs.fsf@detlev.UUCP> Lines: 30 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [removed from -chat, still on -hackers] > What I need is to implement multiple timers for protocl FSM > to react onto, first for inter-character timeout on input, second > one for write timeout, and several more "global" ones like > the "link idle" timeout etc. If several timers may come and go, then I would recommend just making yourself a lowest-first priority queue of the alarm time_t's coupled with the timers' handlers. Set up a global SIGALRM handler to call the handlers for the timers in the queue which have expired, and set the next SIGALRM when the next timer is due. If you only have a small set number of timers and want to save yourself writing a priority queue, then your global SIGALRM handler can check each one individually and set a SIGALRM to handle the next one instead of messing about with a queue. Either way, be sure to save the time_t when it hits, and use it to check and reset all timers. Otherwise, you end up possibly missing one if some time elapses between when several time_t checks. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 15:16:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05093 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 15:16:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05081 for ; Sun, 8 Nov 1998 15:16:43 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id SAA17589 for ; Sun, 8 Nov 1998 18:16:21 -0500 (EST) Date: Sun, 8 Nov 1998 18:16:21 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun2 To: hackers Subject: Alternative site for searching source code Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I normally search the source code via the following URL: http://minnie.cs.adfa.oz.au/FreeBSD-srctree/FreeBSD.html. But it seems to be down these two days. Are there any other sites I can use to search the source code? Thanks for your help. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 15:37:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07382 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 15:37:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07097 for ; Sun, 8 Nov 1998 15:35:09 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (root@woof.lan.Awfulhak.org [172.16.0.7]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id XAA10008; Sun, 8 Nov 1998 23:33:21 GMT (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1]) by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id XAA06518; Sun, 8 Nov 1998 23:34:35 GMT (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199811082334.XAA06518@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Marc Slemko cc: Brian Somers , freebsd-hackers@FreeBSD.ORG Subject: Re: bind()/listen() race In-reply-to: Your message of "Sun, 08 Nov 1998 11:37:37 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Nov 1998 23:34:34 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 8 Nov 1998, Brian Somers wrote: > > > If I create a local domain socket with bind(), there's a period > > between that and the listen() where a connect() will fail. Is there > > any way to circumvent the problem ? > > Why is it a problem to have connects fail before you listen() but not a > problem to have them fail before you bind()? > > I'm not sure I see the race condition. Once you listen(), you can accept > connections. Before you listen(), you can't. The code says something like: if (bind(blah) < 0) { /* we're happy to be the client */ if (connect(blah) < 0) { socket is bound without a listen ! } } else if (listen(blah) < 0) { oops ! } The sockaddrs are local domain sockets used by ppp in multilink mode. Whoever gets to be the server will survive. The other ppp will become the client, pass a file descriptor to the server and hang around holding the session 'till the other ppp kills it. However, if the two ppps get unlucky, one bind()s and the second fails then tries to connect() and fails 'cos the server hasn't listen()ed yet. This is bad news. The only way I can see around it - given that I can't sleep() in ppp without screwing up with other timing issues - is to detect the error and do a 1 second timeout, and try again then. This is a nasty thing to have to do.... I'd prefer an atomic bind()/listen() facility.... Hence the question :-) -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 17:16:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17273 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 17:16:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alive.znep.com (207-178-54-226.go2net.com [207.178.54.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17266 for ; Sun, 8 Nov 1998 17:16:21 -0800 (PST) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.1/8.9.1) with ESMTP id RAA08621; Sun, 8 Nov 1998 17:10:10 -0800 (PST) (envelope-from marcs@znep.com) Date: Sun, 8 Nov 1998 17:10:10 -0800 (PST) From: Marc Slemko To: Brian Somers cc: freebsd-hackers@FreeBSD.ORG Subject: Re: bind()/listen() race In-Reply-To: <199811082334.XAA06518@woof.lan.awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Nov 1998, Brian Somers wrote: > The code says something like: > > if (bind(blah) < 0) { > /* we're happy to be the client */ > if (connect(blah) < 0) { > socket is bound without a listen ! > } > } else if (listen(blah) < 0) { > oops ! > } > > The sockaddrs are local domain sockets used by ppp in multilink mode. > Whoever gets to be the server will survive. The other ppp will > become the client, pass a file descriptor to the server and hang > around holding the session 'till the other ppp kills it. > > However, if the two ppps get unlucky, one bind()s and the second > fails then tries to connect() and fails 'cos the server hasn't > listen()ed yet. This is bad news. > > The only way I can see around it - given that I can't sleep() in ppp > without screwing up with other timing issues - is to detect the error > and do a 1 second timeout, and try again then. This is a nasty thing > to have to do.... I'd prefer an atomic bind()/listen() facility.... No, an atomic bind/listen isn't the solution, you simply need some form of synchronization between the processes. For example, you could use a lockfile and require a write lock arouncd the bind and listen. Unfortunately, inter process synchronization is more of a pain than intra process synchronization. If you used a lock file on disk with the server pid, you could also avoid mistakenly thinking that something else listening on the port is the server. You suggestion is possible as a workaround, and is probably the easiest fix. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 17:42:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20990 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 17:42:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20908; Sun, 8 Nov 1998 17:41:59 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id MAA15085; Mon, 9 Nov 1998 12:11:38 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 09 Nov 1998 12:11:37 +1030 (CST) From: "Daniel O'Connor" To: Jeroen Ruigrok/Asmodai Subject: RE: AWE-32 Cc: FreeBSD Hackers , FreeBSD Current Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Nov-98 Jeroen Ruigrok/Asmodai wrote: > controller snd0 > device sb0 at isa? port 0x220 irq 5 drq 1 > device sbxvi0 at isa? drq 5 > device sbmidi0 at isa? port 0x330 > device awe0 at isa? port 0x620 > > Am I missing something in here? Have you typed -> pnp 1 0 enable os port0 0x220 port1 0x330 port2 0x388 irq0 5 drq0 1 drq1 5 pnp 1 1 enable os port0 0x200 pnp 1 2 enable os port0 0x620 port1 0xa20 port2 0xe20 When you boot -c? --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 17:59:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22441 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 17:59:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22433; Sun, 8 Nov 1998 17:59:42 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id MAA15381; Mon, 9 Nov 1998 12:29:09 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [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: <3.0.32.19981108140828.006961f0@etinc.com> Date: Mon, 09 Nov 1998 12:29:08 +1030 (CST) From: "Daniel O'Connor" To: Dennis Subject: RE: Admin GUI Cc: isp@FreeBSD.ORG, hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Nov-98 Dennis wrote: > Has anyone written a remotely excutable GUI for doing basic admin > tasks like adding users? Something HTML based maybe? Try webmin.. I did a port of it for FreeBSD, but it hasn't been commited yet, so if you look through the pr's you'll find it.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 18:27:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25224 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 18:27:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25216 for ; Sun, 8 Nov 1998 18:27:15 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id VAA00830 for ; Sun, 8 Nov 1998 21:26:58 -0500 (EST) Date: Sun, 8 Nov 1998 21:26:58 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun2 To: hackers Subject: option SPLIT_DEV Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am reading devfs source code. Can anyone tell me where the option SPLIT_DEV is defined and what does it mean? I can not find it under either sys/conf or sys/i386/conf. Thanks. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 18:46:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26692 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 18:46:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26675 for ; Sun, 8 Nov 1998 18:46:43 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id SAA06497; Sun, 8 Nov 1998 18:41:19 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpduz6494; Mon Nov 9 02:41:12 1998 Date: Sun, 8 Nov 1998 18:40:41 -0800 (PST) From: Julian Elischer To: zhihuizhang cc: hackers Subject: Re: option SPLIT_DEV In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The devfs has a backing tree that is only accessible to teh kernel, and then duplicates that tree once for every mounted instance. the reason is that the mounted instances may be re-arranged (using 'mv') but the 'blueprint' (the kernel's copy) must remain untouched. the option 'SPLIT_DEV' decides if the DEVICE nodes in the MOUNT trees are separate structures or simply additional links to the nodes in the blueprint. It can do this because the nodes in the blueprint are reference counted, and theoretically an occurence of /dev/wd0 and /chroot/dev/wd0 should point to the same node and through that, to the same vnode. When SPLIT_DEV is defined, node on each layer will point to different 'node' structures, and when it is not defined, they will all point to a common node for that device. The visible side-effect is that the 'link' count of /dev/wd0 will be 2 in the minimum case when you do 'ls -l /dev/wd0' because it is linked to both the hidden (kernel) mount and the one in /dev. if you mount /chroot/dev, the link count will increase to 3. Also, if you do a chown on one, since they are linked (acress devfs filesystems) the owner of the others will change at the same time. (as will modes, modification times etc.) they will ALL point to the same vnode when open too. With SPLIT_DEVS defined each tree has a different node, so the link counts are not so strange. I hope this helps. julian On Sun, 8 Nov 1998, zhihuizhang wrote: > > I am reading devfs source code. Can anyone tell me where the option > SPLIT_DEV is defined and what does it mean? I can not find it under > either sys/conf or sys/i386/conf. > > Thanks. > > -------------------------------------------------- > | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | > | Dept. of Computer Science, SUNY at Binghamton | > -------------------------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 20:22:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06439 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 20:22:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06418 for ; Sun, 8 Nov 1998 20:22:45 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id VAA24378; Sun, 8 Nov 1998 21:22:23 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp02.primenet.com, id smtpd024329; Sun Nov 8 21:22:13 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id VAA12381; Sun, 8 Nov 1998 21:22:11 -0700 (MST) From: Terry Lambert Message-Id: <199811090422.VAA12381@usr07.primenet.com> Subject: Re: Malloc in the kernel To: grog@lemis.com (Greg Lehey) Date: Mon, 9 Nov 1998 04:22:11 +0000 (GMT) Cc: tlambert@primenet.com, Reinier.Bezuidenhout@KryptoKom.DE, freebsd-hackers@FreeBSD.ORG In-Reply-To: <19981105134634.N784@freebie.lemis.com> from "Greg Lehey" at Nov 5, 98 01:46:34 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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> If I want to malloc really large space in the kernel, say from > >> 2k up to 1M or maybe more .... wat parameter should 'n > >> give to malloc ?? [ ... ] > > It depends on what you intend to use the memory for. > > > > Ideally, you would be prepared to take a page fault, and would > > allocate pageable memory backed by swap so that you didn't > > exhaust the physical memory in the system. > > > > In general, the kernel is better at deciding what memory it needs > > when it needs it than a kernel code author. You either trust > > the locality of reference model upon which VM systems are based, > > or you don't. > > Assuming that fits his needs, what's the answer? vm_pager_allocate(OBJT_SWAP, 0, OFF_TO_IDX(size), VM_PROT_DEFAULT, 0); Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 20:33:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07507 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 20:33:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07491; Sun, 8 Nov 1998 20:33:26 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id VAA05739; Sun, 8 Nov 1998 21:33:07 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpd005692; Sun Nov 8 21:33:03 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id VAA14242; Sun, 8 Nov 1998 21:33:02 -0700 (MST) From: Terry Lambert Message-Id: <199811090433.VAA14242@usr07.primenet.com> Subject: Re: "Eek" To: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=) Date: Mon, 9 Nov 1998 04:33:02 +0000 (GMT) Cc: mike@seidata.com, chat@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: from "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" at Nov 6, 98 11:26:21 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > http://dd.sh/perlfs/ > > Great... when will FreeBSD implement this? ;-P > > Never, I hope. There is a proverb about hammers and nails which has > often been invoked for Perl; it is particularly pertinent to this > situation. You mean the one that goes: "If the only tool you have is PERL, everything looks like a thumb..." ? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 20:38:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07887 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 20:38:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rufus.comms.unsw.EDU.AU (rufus.comms.unsw.EDU.AU [149.171.96.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07871; Sun, 8 Nov 1998 20:38:30 -0800 (PST) (envelope-from c.day@student.unsw.edu.au) Received: from lab_machine ([129.94.222.69]) by rufus.comms.unsw.EDU.AU (8.8.8/8.7.5.kenso-central) with SMTP id PAA10873; Mon, 9 Nov 1998 15:34:54 +1100 (EST) Message-Id: <3.0.5.32.19981109150346.00931d20@pop3.student.unsw.edu.au> X-Sender: z2172268@pop3.student.unsw.edu.au X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 09 Nov 1998 15:03:46 +1000 To: Jeroen Ruigrok/Asmodai , FreeBSD Current , FreeBSD Hackers From: chris day Subject: Re: AWE-32 In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When you boot, go into kernel config, then at the prompt type pnp 1 0 os enable port0 0x220 port1 0x330 irq0 5 drq0 1 drq1 5 pnp 1 2 os enable port0 0x620 port1 0xa20 port2 0xe20 This is the PnP strings for my PnP AWE64, the only difference with mine is that I also add 'port2 0x388' to the first line for the OPL. Anyways hopefully this should work. regards, chris >Probing for PnP devices: >CSN 1 Vendor ID: CTL009c [0x9c008c0e] Serial 0x10046cf4 Comp ID: PNP0600 >[0x0006d041] > >sb0 at 0x220 irq 5 drq 1 on isa >snd0: >sbxvi0 at ? drq 5 on isa >snd0: >sbmidi0 at 0x330 on isa >snd0: >awe0 at 0x620 on isa >AWE32: not detected To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 21:18:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11511 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 21:18:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11492 for ; Sun, 8 Nov 1998 21:18:22 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id WAA04511; Sun, 8 Nov 1998 22:18:05 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd004494; Sun Nov 8 22:18:03 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id WAA28668; Sun, 8 Nov 1998 22:18:02 -0700 (MST) From: Terry Lambert Message-Id: <199811090518.WAA28668@usr07.primenet.com> Subject: Re: text mode screen grabber? To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Mon, 9 Nov 1998 05:18:02 +0000 (GMT) Cc: nik@nothing-going-on.demon.co.uk, hackers@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp In-Reply-To: <199811081510.AAA16053@zodiac.mech.utsunomiya-u.ac.jp> from "Kazutaka YOKOTA" at Nov 9, 98 00:10:42 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Has anyone got (or have pointers to useful code) a screen grabber for > >syscons? Ideally (and given an 80x25 screen) I'm looking for something > >that would write a 4000 byte file of { character code, colour } tuples. > [...] > > Have you considered script(1), a standard command, or `screen', which > is in the port collection, I expect? Someone should implement ESC [ 2 i (Media copy); it sends the current screen contents to the host. For syscons, it would rougly resemble a mouse_paste in stuffing the input buffer. Someone should also consider IBCS2 functionality wants: http://www5.sco.com/cgi-bin/ssl_getmanpage?screen+HW+OSES30+screen Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 23:31:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21871 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 23:31:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA21862 for ; Sun, 8 Nov 1998 23:31:18 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id IAA00746; Mon, 9 Nov 1998 08:30:56 +0100 (MET) Date: Mon, 9 Nov 1998 08:30:56 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Rohit Dube cc: FreeBSD hackers mailing list Subject: Re: 3.0 on Laptops In-Reply-To: <199811062315.SAA16822@zubin.dnrc.bell-labs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Having seen several people bite the dust trying run X (on both Linux > and FreeBSD) on laptops I would especially appreciate comments on > from people who have tried this before. http://www.xig.com make laptop drivers, for FreeBSD as well as Linux. They are neat and work for example on the Vaio 505. Two ways of doing this: 1) Buy a supported one andand buy their software. 2) Buy an unsupported one, send them the laptop to make it work and get the software for free. Nick -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 23:31:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21917 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 23:31:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.wgn.net (mail.wgn.net [207.213.0.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA21912; Sun, 8 Nov 1998 23:31:48 -0800 (PST) (envelope-from almazs@wgn.net) Received: from laptop (du528-pcap-nca01.wgn.net [207.213.7.20]) by mail.wgn.net (8.9.1/8.9.0) with SMTP id XAA32223; Sun, 8 Nov 1998 23:31:31 -0800 Message-ID: <36469938.397A@wgn.net> Date: Sun, 08 Nov 1998 23:26:48 -0800 From: Co-app Network consulting Reply-To: almazs@wgn.net Organization: Network Consulting X-Mailer: Mozilla 3.0C-NSCP (Win95; U) MIME-Version: 1.0 To: isp@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: RE: APC SmartUPS Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi; Does anybody know how to setup an APC smartUPS monitoring on FreeBSD? Is there something in the port collection to interface the UPS with a FreeBSD server? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 8 23:56:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA24241 for freebsd-hackers-outgoing; Sun, 8 Nov 1998 23:56:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA24224; Sun, 8 Nov 1998 23:56:01 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id SAA24247; Mon, 9 Nov 1998 18:25:30 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [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: <36469938.397A@wgn.net> Date: Mon, 09 Nov 1998 18:25:29 +1030 (CST) From: "Daniel O'Connor" To: Co-app Network consulting Subject: RE: APC SmartUPS Cc: hackers@FreeBSD.ORG, isp@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Nov-98 Co-app Network consulting wrote: > Does anybody know how to setup an APC smartUPS monitoring on FreeBSD? > Is there something in the port collection to interface the UPS with > a FreeBSD server? No there isn't, but there is a piece of software which does it :) apcmon talks to APC UPS's and works fairly well, thought its a small pain to set up.. But given that its a collection of shell scripts, it works well :) Unfortunatley I don't know where it was found, but I put a copy on ftp://cain.gsoft.com.au/apcmon-1.28a.shar.Z --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 01:14:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA02749 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 01:14:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA02743 for ; Mon, 9 Nov 1998 01:14:16 -0800 (PST) (envelope-from xroot@root.com) Received: from implode.root.com (localhost [127.0.0.1]) by root.com (8.8.5/8.8.5) with ESMTP id BAA09637; Mon, 9 Nov 1998 01:15:16 -0800 (PST) Message-Id: <199811090915.BAA09637@root.com> To: Terry Lambert cc: grog@lemis.com (Greg Lehey), Reinier.Bezuidenhout@KryptoKom.DE, freebsd-hackers@FreeBSD.ORG Subject: Re: Malloc in the kernel In-reply-to: Your message of "Mon, 09 Nov 1998 04:22:11 GMT." <199811090422.VAA12381@usr07.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 09 Nov 1998 01:15:16 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >> If I want to malloc really large space in the kernel, say from >> >> 2k up to 1M or maybe more .... wat parameter should 'n >> >> give to malloc ?? > >[ ... ] > >> > It depends on what you intend to use the memory for. >> > >> > Ideally, you would be prepared to take a page fault, and would >> > allocate pageable memory backed by swap so that you didn't >> > exhaust the physical memory in the system. >> > >> > In general, the kernel is better at deciding what memory it needs >> > when it needs it than a kernel code author. You either trust >> > the locality of reference model upon which VM systems are based, >> > or you don't. >> >> Assuming that fits his needs, what's the answer? > >vm_pager_allocate(OBJT_SWAP, 0, OFF_TO_IDX(size), VM_PROT_DEFAULT, 0); Bzzt! Wrong! ...but you could use kmem_alloc_pageable() (or call vm_map_find() directly) to allocate demand-zero, pageable, kernel memory. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 03:44:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA18777 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 03:44:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from post.mail.demon.net (post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA18757; Mon, 9 Nov 1998 03:44:15 -0800 (PST) (envelope-from marko@uk.radan.com) Received: from [158.152.75.22] (helo=uk.radan.com) by post.mail.demon.net with smtp (Exim 2.05demon1 #1) id 0zcpjh-00007l-00; Mon, 9 Nov 1998 11:43:58 +0000 Organisation: Radan Computational Ltd., Bath, UK. Phone: +44-1225-320320 Fax: +44-1225-320311 Received: from beavis.uk.radan.com (beavis [193.114.228.122]) by uk.radan.com (8.6.10/8.6.10) with SMTP id LAA00304; Mon, 9 Nov 1998 11:40:48 GMT Received: from uk.radan.com (gppsun4) by beavis.uk.radan.com (4.1/SMI-4.1) id AA06499; Mon, 9 Nov 98 11:40:46 GMT Message-Id: <3646D4A0.2E4D402B@uk.radan.com> Date: Mon, 09 Nov 1998 11:40:16 +0000 From: Mark Ovens Organization: Radan Computational Ltd X-Mailer: Mozilla 4.03 [en] (X11; I; SunOS 4.1.3_U1 sun4m) Mime-Version: 1.0 To: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: UK User Group meeting Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If there are any UK FreeBSD users (or anyone who may be in the UK on 21/11) here who are not on the UKUG mailing list this is to inform you that the UKUG is holding a User Group meeting on Saturday 21/11 in Oxford. The venue is Jamal's Balti House, Walton Street, Oxford at 10p.m. (although some of us will probably meet up earlier in a local pub). If you are interested in joining us please e-mail me. -- Trust the computer industry to shorten Year 2000 to Y2K. It was this thinking that caused the problem in the first place. Mark Ovens, CNC Applications Engineer, Radan Computational Ltd. Bath, Avon, England. Sheet Metal CAD/CAM Solutions mailto:marko@uk.radan.com http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 03:49:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA19103 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 03:49:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA18947; Mon, 9 Nov 1998 03:47:56 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from yggdrasil.ifi.uio.no (2602@yggdrasil.ifi.uio.no [129.240.64.182]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id LAA09278; Mon, 9 Nov 1998 11:22:21 +0100 (MET) Received: (from dag-erli@localhost) by yggdrasil.ifi.uio.no ; Mon, 9 Nov 1998 11:22:20 +0100 (MET) Mime-Version: 1.0 To: Terry Lambert Cc: mike@seidata.com, chat@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: "Eek" References: <199811090433.VAA14242@usr07.primenet.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 09 Nov 1998 11:22:19 +0100 In-Reply-To: Terry Lambert's message of "Mon, 9 Nov 1998 04:33:02 +0000 (GMT)" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id DAA19096 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert writes: > > Never, I hope. There is a proverb about hammers and nails which has > > often been invoked for Perl; it is particularly pertinent to this > > situation. > You mean the one that goes: > > "If the only tool you have is PERL, everything looks like a thumb..." Uh, yeah, something like that :) DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 04:48:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA28072 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 04:48:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from emu.sourcee.com (emu.sourcee.com [199.201.159.173]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA28052; Mon, 9 Nov 1998 04:48:13 -0800 (PST) (envelope-from nrice@emu.sourcee.com) Received: (from nrice@localhost) by emu.sourcee.com (8.9.1/8.9.1) id HAA07546; Mon, 9 Nov 1998 07:47:56 -0500 (EST) Message-ID: <19981109074755.A7515@emu.sourcee.com> Date: Mon, 9 Nov 1998 07:47:55 -0500 From: "Norman C. Rice" To: almazs@wgn.net, isp@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: APC SmartUPS References: <36469938.397A@wgn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <36469938.397A@wgn.net>; from Co-app Network consulting on Sun, Nov 08, 1998 at 11:26:48PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 08, 1998 at 11:26:48PM -0800, Co-app Network consulting wrote: > Hi; > > Does anybody know how to setup an APC smartUPS monitoring on FreeBSD? > Is there something in the port collection to interface the UPS with > a FreeBSD server? Check out the `upsd-2.0' port. -- Regards, Norman C. Rice, Jr. > > Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 06:47:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA08605 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 06:47:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA08600 for ; Mon, 9 Nov 1998 06:46:59 -0800 (PST) (envelope-from lile@stdio.com) Received: from localhost (lile@localhost) by heathers.stdio.com (8.8.8/8.8.8) with SMTP id JAA28014 for ; Mon, 9 Nov 1998 09:49:36 -0500 (EST) (envelope-from lile@heathers.stdio.com) Date: Mon, 9 Nov 1998 09:49:35 -0500 (EST) From: "Larry S. Lile" To: hackers@FreeBSD.ORG Subject: mbuf question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are mbufs allocated below the 16M area? If they are, is it likely to change? Why? Because I am trying to eliminate bcopy's and mallocs in my token-ring driver to gain a little more performance. Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 07:00:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12215 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 07:00:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12152 for ; Mon, 9 Nov 1998 07:00:13 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id HAA04321; Mon, 9 Nov 1998 07:01:31 -0800 (PST) Message-Id: <199811091501.HAA04321@root.com> To: "Larry S. Lile" cc: hackers@FreeBSD.ORG Subject: Re: mbuf question In-reply-to: Your message of "Mon, 09 Nov 1998 09:49:35 EST." From: David Greenman Reply-To: dg@root.com Date: Mon, 09 Nov 1998 07:01:31 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Are mbufs allocated below the 16M area? > >If they are, is it likely to change? > >Why? Because I am trying to eliminate bcopy's and mallocs in my >token-ring driver to gain a little more performance. They're allocated throughout the machine's physical address space. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 07:00:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12338 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 07:00:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from jriver.jriver.com (jriver.jriver.com [192.146.151.161]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA12300 for ; Mon, 9 Nov 1998 07:00:42 -0800 (PST) (envelope-from nathan@jriver.jriver.com) Received: (qmail 7375 invoked by uid 0); 9 Nov 1998 09:00:12 -0600 Received: from nathan.jriver.com (HELO nathan) (192.146.151.47) by jriver.jriver.com with SMTP; 9 Nov 1998 09:00:12 -0600 Message-Id: <3.0.5.32.19981108082754.01103a10@jriver.jriver.com> X-Sender: nathan@jriver.jriver.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sun, 08 Nov 1998 08:27:54 -0600 To: hackers@FreeBSD.ORG From: "Nathan D. Gruman" Subject: The ICE.Off.Site You Downloaded (was Re: Trial Software Registration Information) In-Reply-To: <199811072326.RAA15846@rs6000.jriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:26 PM 11/7/98 -0600, you wrote: > >Prodname: ICE.Off.Site >Serial: 9807127847.99414 >Company: Teenies Productions >Person: Little Leah >City: Detroit >State: MI >Country: US >Referral: Card Deck >Phone: 313-742-9865 >Fax: >Email: hackers@freebsd.org >Date: 11/07/98 >URL: ftp://ftp.jriver.com/pub/downloads/off-demo.exe >Filename: off-demo.exe >Remote host: pool009-max2.ds19-ca-us.dialup.earthlink.net >Broswer: Mozilla/4.07 [en] (Win95; U ;Nav) >Color: >Resolution: > > > Hello- Thank you for your interest in our ICE.Off.Site package for PC to UNIX connectivity via a serial-modem. ICE.Off.Site is licensed per PC making a remote connection. ICE.Off.Site is sold two ways: 1.) OFF001, a single-user license for $125.00USD 2.) OFF001, a five pack of single-users for $495.00USD If you need technical assisstance please contact support@jriver.com . If you would like a distributor near you or if you would like to purchase the product, please feel free to drop me e-mail or give me a call. *** Please note, prices will vary from country to country. *** Sincerely, Nathan -------------------------------------------------------------- Nathan D. Gruman E-mail: nathan@jriver.com Sales Representative ftp.jriver.com J. River, Inc. http://www.jriver.com 125 North First Street Voice: (612) 677-8247 Minneapolis, MN 55401 Fax: (612) 339-7034 -------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 07:20:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15079 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 07:20:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phobos.illtel.denver.co.us (phobos.illtel.denver.co.us [207.33.75.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA15070 for ; Mon, 9 Nov 1998 07:20:47 -0800 (PST) (envelope-from abelits@phobos.illtel.denver.co.us) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.9.1a/8.6.9) with SMTP id HAA06075; Mon, 9 Nov 1998 07:23:37 -0800 Date: Mon, 9 Nov 1998 07:23:37 -0800 (PST) From: Alex Belits To: "Nathan D. Gruman" cc: hackers@FreeBSD.ORG Subject: Re: The ICE.Off.Site You Downloaded (was Re: Trial Software Registration Information) In-Reply-To: <3.0.5.32.19981108082754.01103a10@jriver.jriver.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Nov 1998, Nathan D. Gruman wrote: > Date: Sun, 08 Nov 1998 08:27:54 -0600 > From: Nathan D. Gruman > To: hackers@FreeBSD.ORG > Subject: The ICE.Off.Site You Downloaded (was Re: Trial Software Registration Information) > > At 05:26 PM 11/7/98 -0600, you wrote: > > > >Prodname: ICE.Off.Site > >Serial: 9807127847.99414 > >Company: Teenies Productions > >Person: Little Leah > >City: Detroit > >State: MI > >Country: US > >Referral: Card Deck > >Phone: 313-742-9865 > >Fax: > >Email: hackers@freebsd.org > >Date: 11/07/98 > >URL: ftp://ftp.jriver.com/pub/downloads/off-demo.exe > >Filename: off-demo.exe > >Remote host: pool009-max2.ds19-ca-us.dialup.earthlink.net > >Broswer: Mozilla/4.07 [en] (Win95; U ;Nav) > >Color: > >Resolution: > > > > > > > Hello- > > Thank you for your interest in our ICE.Off.Site package for PC to UNIX > connectivity via a serial-modem. ICE.Off.Site is licensed per PC making a Well. at least that was creative. -- Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 07:30:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15984 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 07:30:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA15967 for ; Mon, 9 Nov 1998 07:30:13 -0800 (PST) (envelope-from lile@stdio.com) Received: from localhost (lile@localhost) by heathers.stdio.com (8.8.8/8.8.8) with SMTP id KAA29753; Mon, 9 Nov 1998 10:32:48 -0500 (EST) (envelope-from lile@heathers.stdio.com) Date: Mon, 9 Nov 1998 10:32:48 -0500 (EST) From: "Larry S. Lile" To: David Greenman cc: hackers@FreeBSD.ORG Subject: Re: mbuf question In-Reply-To: <199811091501.HAA04321@root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Nov 1998, David Greenman wrote: > >Are mbufs allocated below the 16M area? > > > >If they are, is it likely to change? > > > >Why? Because I am trying to eliminate bcopy's and mallocs in my > >token-ring driver to gain a little more performance. > > They're allocated throughout the machine's physical address space. I was afraid of that, so I should just make new buffers and copy when I need DMA'able memory. Otherwise I can just use the mbuf's directly. Thanks! Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 07:45:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17492 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 07:45:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from att.com (kcgw1.att.com [192.128.133.151]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA17478; Mon, 9 Nov 1998 07:45:31 -0800 (PST) (envelope-from sbabkin@dcn.att.com) From: sbabkin@dcn.att.com Received: from kcig1.fw.att.com by kcgw1.att.com (AT&T/IPNS/UPAS-1.0) for freebsd.org!freebsd-hackers freebsd.org!advocacy sender dcn.att.com!sbabkin (dcn.att.com!sbabkin); Mon Nov 9 09:42 CST 1998 Received: from dcn71.dcn.att.com ([135.44.192.112]) by kcig1.fw.att.com (AT&T/IPNS/GW-1.0) with ESMTP id JAA25413; Mon, 9 Nov 1998 09:42:40 -0600 (CST) Received: by dcn71.dcn.att.com with Internet Mail Service (5.0.1460.8) id ; Mon, 9 Nov 1998 10:42:36 -0500 Message-ID: To: nathan@rtfm.net, hasty@netcom.com, advocacy@FreeBSD.ORG, imp@village.org Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: Ariel Faigon: The Holloween Document (fwd) Date: Mon, 9 Nov 1998 10:42:34 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1460.8) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Nathan Dorfman [SMTP:nathan@rtfm.net] > > On Tue, Nov 03, 1998 at 02:01:40PM -0800, Amancio Hasty Jr wrote: > > The e-mail made it to today's San Jose Mercury NewsPaper in the business > > section. The news article claims that the e-mail was confirmed by > > Microsoft to be authenticate --- not sure who to believe Microsoft or > > the Linux camp 8) > > http://www.microsoft.com/ntserver/highlights/editorletter.asp > I wonder, has anyone considered another possibility: that this information leak is intended. Now, when Microsoft got some pressure for monopolizing the market, it may be important for them to convince everybody that they are actually not a monopoly. -Sergey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 07:58:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18387 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 07:58:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phobos.illtel.denver.co.us (phobos.illtel.denver.co.us [207.33.75.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA18382; Mon, 9 Nov 1998 07:58:18 -0800 (PST) (envelope-from abelits@phobos.illtel.denver.co.us) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.9.1a/8.6.9) with SMTP id IAA06287; Mon, 9 Nov 1998 08:00:42 -0800 Date: Mon, 9 Nov 1998 08:00:42 -0800 (PST) From: Alex Belits To: sbabkin@dcn.att.com cc: nathan@rtfm.net, hasty@netcom.com, advocacy@FreeBSD.ORG, imp@village.org, freebsd-hackers@FreeBSD.ORG Subject: RE: Ariel Faigon: The Holloween Document (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Nov 1998 sbabkin@dcn.att.com wrote: > I wonder, has anyone considered another possibility: that > this information leak is intended. Now, when Microsoft > got some pressure for monopolizing the market, it may > be important for them to convince everybody that they > are actually not a monopoly. A lot of people did, but even taking in consideration that human stupidity is always underestimated, such tactics will backfire at Microsoft heavily -- as "You should abandon all profits from selling software to be able to compete with Microsoft". -- Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 08:11:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19716 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 08:11:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gvinpin.grad.kiev.ua (KievglavArhit-UTC-28k8.ukrtel.net [195.5.25.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19694; Mon, 9 Nov 1998 08:10:50 -0800 (PST) (envelope-from Ruslan@Shevchenko.Kiev.UA) Received: from Shevchenko.Kiev.UA (cam [10.0.0.50]) by gvinpin.grad.kiev.ua (8.8.7/8.8.7) with ESMTP id SAA30710; Mon, 9 Nov 1998 18:08:34 +0200 Message-ID: <36471364.4BE0472A@Shevchenko.Kiev.UA> Date: Mon, 09 Nov 1998 18:08:04 +0200 From: Ruslan Shevchenko Reply-To: rssh@grad.kiev.ua X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.5-STABLE i386) MIME-Version: 1.0 To: Dennis CC: hackers@FreeBSD.ORG, isp@FreeBSD.ORG Subject: Re: Admin GUI References: <3.0.32.19981108140828.006961f0@etinc.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > > > Has anyone written a remotely excutable GUI for doing basic admin > tasks like adding users? Something HTML based maybe? > > thanks, > > dennis > http://cam.grad.kiev.ua/~rssh/admin/admin.html > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- @= //RSSH mailto:Ruslan@Shevchenko.Kiev.UA CORBA in Ukraine & ex-USSR: http://www.corbadev.kiev.ua To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 08:26:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21366 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 08:26:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21356 for ; Mon, 9 Nov 1998 08:26:23 -0800 (PST) (envelope-from rivers@dignus.com) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id IAA15563 for ; Mon, 9 Nov 1998 08:26:25 -0800 (PST) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id LAA19283 for ; Mon, 9 Nov 1998 11:26:05 -0500 (EST) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id MAA21990 for ; Mon, 9 Nov 1998 12:12:52 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id LAA23614 for freebsd-hackers@freefall.cdrom.com; Mon, 9 Nov 1998 11:27:10 -0500 (EST) Date: Mon, 9 Nov 1998 11:27:10 -0500 (EST) From: Thomas David Rivers Message-Id: <199811091627.LAA23614@lakes.dignus.com> To: freebsd-hackers@freefall.cdrom.com Subject: A stdio question... does fpos_t really need to be 'long long'? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok - here's a question for the stdio internal gurus... ftell() is defined to return a 'long' (32 bits). fpos_t is defined as a 'long long' (64 bits). fgetpos() accepts an fpos_t as it's second argument, and is implemented as: { int retval; retval = (*pos = ftell(fp)) == (fpos_t) -1; return (retval); } Now - given this - how will fgetpos() ever succeed on a file position greater than 2**32 - since ftell() can't return anything larger than that... Moreover - what if you do an fsetpos() on something larger than 2**32 and then do an fgetpos() to see if it actually worked... If this is the case... then why is fpos_t a 'long long'? If, in fact, it can never be set that large? I must be missing something here... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 09:08:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24861 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 09:08:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24855 for ; Mon, 9 Nov 1998 09:08:34 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id JAA10172 for hackers@freebsd.org; Mon, 9 Nov 1998 09:12:33 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811091712.JAA10172@troutmask.apl.washington.edu> Subject: linux software installation and uname To: hackers@FreeBSD.ORG Date: Mon, 9 Nov 1998 09:12:33 -0800 (PST) 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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ladies and Gents, I've recently installed the Portland Groups's Fortran 90 for Linux on my system (it works!). However, during the installation from the cdrom, a install script is executed that contains a test involving "uname -s" to ensure the installation is on a system running Linux. Of course, "uname -s" on a FreeBSD system returns "FreeBSD" instead of the expected "Linux". Thus, I had to alter uname(1) to report "Linux" to install the software. With the expected availability of more commericial software for Linux, it seems necessary to provide uname(1) the capability to report "Linux" in place of "FreeBSD". -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html *** uname.c.orig Mon Nov 9 08:46:41 1998 --- uname.c Mon Nov 9 08:49:54 1998 *************** *** 105,116 **** prefix = ""; if (flags & SFLAG) { ! mib[0] = CTL_KERN; ! mib[1] = KERN_OSTYPE; ! len = sizeof(buf); ! if (sysctl(mib, 2, &buf, &len, NULL, 0) == -1) ! err(1, "sysctl"); ! (void)printf("%s%.*s", prefix, (int)len, buf); prefix = " "; } if (flags & NFLAG) { --- 105,119 ---- prefix = ""; if (flags & SFLAG) { ! if (!getenv("LINUX_UNAME")) { ! mib[0] = CTL_KERN; ! mib[1] = KERN_OSTYPE; ! len = sizeof(buf); ! if (sysctl(mib, 2, &buf, &len, NULL, 0) == -1) ! err(1, "sysctl"); ! (void)printf("%s%.*s", prefix, (int)len, buf); ! } else ! (void)printf("%sLinux", prefix); prefix = " "; } if (flags & NFLAG) { *** uname.1.orig Mon Nov 9 09:06:23 1998 --- uname.1 Mon Nov 9 09:08:56 1998 *************** *** 72,77 **** --- 72,82 ---- to standard output. .It Fl s Write the name of the operating system implementation to standard output. + If the environmental variable + .Em LINUX_UNAME + is set, then write + .Em Linux + to standard output. .It Fl v Write the version level of this release of the operating system to standard output. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 09:10:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25066 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 09:10:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25053 for ; Mon, 9 Nov 1998 09:10:24 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan@dan.emsphone.com [199.67.51.101]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id JAA18330 for ; Mon, 9 Nov 1998 09:10:26 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id LAA05466; Mon, 9 Nov 1998 11:09:55 -0600 (CST) Date: Mon, 9 Nov 1998 11:09:55 -0600 From: Dan Nelson To: Thomas David Rivers , freebsd-hackers@freefall.cdrom.com Subject: Re: A stdio question... does fpos_t really need to be 'long long'? Message-ID: <19981109110955.A5248@emsphone.com> References: <199811091627.LAA23614@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.3i In-Reply-To: <199811091627.LAA23614@lakes.dignus.com>; from "Thomas David Rivers" on Mon Nov 9 11:27:10 GMT 1998 X-OS: FreeBSD 2.2.7-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Nov 09), Thomas David Rivers said: > Ok - here's a question for the stdio internal gurus... > > ftell() is defined to return a 'long' (32 bits). > fpos_t is defined as a 'long long' (64 bits). > fgetpos() accepts an fpos_t as it's second argument, and is > implemented as: > > retval = (*pos = ftell(fp)) == (fpos_t) -1; > return (retval); > > If this is the case... then why is fpos_t a 'long long'? If, in > fact, it can never be set that large? I noticed this back in April and commented on it. I believe the consensus was that fsetpos()/fgetpos()/fseek()/ftell() should be wrappers for the X/Open functions fseeko() and ftello(), which take off_t arguments. Unfortunately, I never submitted patches, and neither did anyone else. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 09:12:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25219 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 09:12:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25214 for ; Mon, 9 Nov 1998 09:12:50 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id MAA14742 for ; Mon, 9 Nov 1998 12:12:30 -0500 (EST) Date: Mon, 9 Nov 1998 12:12:29 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun2 To: hackers Subject: radix argument of kvprintf() Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I try to figure out the meaning of the argument radix in the routine kvprintf() in file subr_prf.c. I find that radix can be values from 2 through 36 and is only used when you have a %n in the format. The specifier %n is supposed to save the number of characters we have printed so far. But the source code of kvprintf() does not show this. Instead, it specifies we want to print the next argument with base value of radix. This is inconsistent with what is said about printf(3). Can anyone explain this for me? Thanks a lot. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 09:13:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25308 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 09:13:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25303 for ; Mon, 9 Nov 1998 09:13:38 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA05803; Mon, 9 Nov 1998 10:13:22 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA04612; Mon, 9 Nov 1998 10:13:22 -0700 Date: Mon, 9 Nov 1998 10:13:22 -0700 Message-Id: <199811091713.KAA04612@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Steve Kargl Cc: hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <199811091712.JAA10172@troutmask.apl.washington.edu> References: <199811091712.JAA10172@troutmask.apl.washington.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I've recently installed the Portland Groups's Fortran 90 > for Linux on my system (it works!). However, during the > installation from the cdrom, a install script is executed > that contains a test involving "uname -s" to ensure the > installation is on a system running Linux. Of course, > "uname -s" on a FreeBSD system returns "FreeBSD" instead > of the expected "Linux". Thus, I had to alter uname(1) > to report "Linux" to install the software. Actually, you didn't. Stick a uname in the appropriate /compat/linux directory and it will be called (and return Linux) which doesn't bloat FreeBSD's code with Linux-centric bits. This can be done as a simple shell script or as complex as you'd like. Otherwise, modifying every OS-specific piece of code in FreeBSD with other OS's specific features (It's linux today, Solaris tomorrow, Xenix in the future... :) is fraught with bloat and peril. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 09:34:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27323 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 09:34:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27318 for ; Mon, 9 Nov 1998 09:34:16 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA05968 for ; Mon, 9 Nov 1998 10:34:01 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA04752; Mon, 9 Nov 1998 10:34:00 -0700 Date: Mon, 9 Nov 1998 10:34:00 -0700 Message-Id: <199811091734.KAA04752@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: hackers@FreeBSD.ORG Subject: Supporting more than FD_SETSIZE fd's X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I looked through the handbook and the FAQ and didn't find anything, so hopefully someone can help me out. I need to support more than the default 255 FD's in an application (the JDK for what it's worth). To be portable, the code uses fd_set as defined in . Unfortunately, unless I redefine FD_SETSIZE in every file that uses it, I still have a hard-limit on the number of FD's the application can use. Is there any 'portable' way of getting around this? I'd really like to have it use whichever open FD that the limit allows, but I know now way of having this happen? I looked through the code in Apache, and I don't see how it does this, since I never saw any re-definition of FD_SETSIZE, or use of anything other than fd_setsize. (Although, I did see mention of FD_SETSIZE quite a bit in the comments.) Any help anyone can provide would be greatly appreciated! Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 09:34:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27410 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 09:34:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27405 for ; Mon, 9 Nov 1998 09:34:56 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id MAA02660; Mon, 9 Nov 1998 12:34:38 -0500 (EST) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id NAA22180; Mon, 9 Nov 1998 13:20:48 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id MAA23943; Mon, 9 Nov 1998 12:35:05 -0500 (EST) Date: Mon, 9 Nov 1998 12:35:05 -0500 (EST) From: Thomas David Rivers Message-Id: <199811091735.MAA23943@lakes.dignus.com> To: hackers@FreeBSD.ORG, sgk@troutmask.apl.washington.edu Subject: Re: linux software installation and uname In-Reply-To: <199811091712.JAA10172@troutmask.apl.washington.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Ladies and Gents, > > I've recently installed the Portland Groups's Fortran 90 > for Linux on my system (it works!). However, during the > installation from the cdrom, a install script is executed > that contains a test involving "uname -s" to ensure the > installation is on a system running Linux. Of course, > "uname -s" on a FreeBSD system returns "FreeBSD" instead > of the expected "Linux". Thus, I had to alter uname(1) > to report "Linux" to install the software. With the > expected availability of more commericial software for Linux, > it seems necessary to provide uname(1) the capability to > report "Linux" in place of "FreeBSD". > > -- > Steve > Steve - We've been here before. The consensus - after considerable debate - was to not make such a change. The problem is that several automated processes - particularly WEB related - use uname to determine what kind of machines they are running on. If we return "Linux" - then we inflate the linux numbers at the cost of our own. In my particular instance, I was able to persuade the vendor that it was artificially limiting its customer base. And thus, the uname check was changed to accept either "FreeBSD" or "Linux". Perhaps you could do the same with the Lahey people. For the previous debate; I refer you to the mail archives. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 09:42:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA28348 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 09:42:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA28341 for ; Mon, 9 Nov 1998 09:42:57 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id JAA10366; Mon, 9 Nov 1998 09:46:42 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811091746.JAA10366@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname In-Reply-To: <199811091713.KAA04612@mt.sri.com> from Nate Williams at "Nov 9, 1998 10:13:22 am" To: nate@mt.sri.com (Nate Williams) Date: Mon, 9 Nov 1998 09:46:42 -0800 (PST) Cc: hackers@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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Nate Williams: > > > > I've recently installed the Portland Groups's Fortran 90 > > for Linux on my system (it works!). However, during the > > installation from the cdrom, a install script is executed > > that contains a test involving "uname -s" to ensure the > > installation is on a system running Linux. Of course, > > "uname -s" on a FreeBSD system returns "FreeBSD" instead > > of the expected "Linux". Thus, I had to alter uname(1) > > to report "Linux" to install the software. > > Actually, you didn't. Stick a uname in the appropriate /compat/linux > directory and it will be called (and return Linux) which doesn't bloat > FreeBSD's code with Linux-centric bits. > > This can be done as a simple shell script or as complex as you'd like. > First, I generally agree with your anti-bloat sentiments. Sure, I have the capability to write the script or C program, and stuff it into /usr/compat/linux/usr/bin, but this isn't a general solution for Jane Doe user. She wants/needs to run linux software, and she may not have the know-how to work around this problem. Neither ports/emulator/linux_lib nor ports/devel/linux_devel supply a uname(1). I am not claiming that my suggested solution is the best solution. But, we can't ignore the problem exists. At this point time, the Portland Group has no intention of supporting a native FreeBSD version of their software. I suspect other commerical vendors will have a similar attitude (particularly if they know about FreeBSD's linux emulation). -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 09:52:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29256 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 09:52:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29246 for ; Mon, 9 Nov 1998 09:52:39 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id JAA10389; Mon, 9 Nov 1998 09:56:33 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811091756.JAA10389@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname In-Reply-To: <199811091735.MAA23943@lakes.dignus.com> from Thomas David Rivers at "Nov 9, 1998 12:35: 5 pm" To: rivers@dignus.com (Thomas David Rivers) Date: Mon, 9 Nov 1998 09:56:33 -0800 (PST) Cc: hackers@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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Thomas David Rivers: > > > > to report "Linux" to install the software. With the > > expected availability of more commericial software for Linux, > > it seems necessary to provide uname(1) the capability to > > report "Linux" in place of "FreeBSD". > > We've been here before. The consensus - after considerable > debate - was to not make such a change. It was only a pro-active suggestion. I was unaware of previous debate. > The problem is that several automated processes - particularly > WEB related - use uname to determine what kind of machines > they are running on. If we return "Linux" - then we inflate > the linux numbers at the cost of our own. It's better to infate the linux numbers, than to cut-off one's only means to run certain software. For example, there are no open source Fortran 90 compilers. You must purchase a commerical F90 compiler and run it under linux emulation. > In my particular instance, I was able to persuade the vendor > that it was artificially limiting its customer base. And thus, > the uname check was changed to accept either "FreeBSD" or "Linux". > Perhaps you could do the same with the Lahey people. Been there. PGI has no intention at this time to support FreeBSD because they do not have sufficient tech. support for FreeBSD. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 09:57:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29785 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 09:57:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29772 for ; Mon, 9 Nov 1998 09:56:57 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA06185; Mon, 9 Nov 1998 10:56:42 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA04904; Mon, 9 Nov 1998 10:56:41 -0700 Date: Mon, 9 Nov 1998 10:56:41 -0700 Message-Id: <199811091756.KAA04904@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Steve Kargl Cc: nate@mt.sri.com (Nate Williams), hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <199811091746.JAA10366@troutmask.apl.washington.edu> References: <199811091713.KAA04612@mt.sri.com> <199811091746.JAA10366@troutmask.apl.washington.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I've recently installed the Portland Groups's Fortran 90 > > > for Linux on my system (it works!). However, during the > > > installation from the cdrom, a install script is executed > > > that contains a test involving "uname -s" to ensure the > > > installation is on a system running Linux. Of course, > > > "uname -s" on a FreeBSD system returns "FreeBSD" instead > > > of the expected "Linux". Thus, I had to alter uname(1) > > > to report "Linux" to install the software. > > > > Actually, you didn't. Stick a uname in the appropriate /compat/linux > > directory and it will be called (and return Linux) which doesn't bloat > > FreeBSD's code with Linux-centric bits. > > > > This can be done as a simple shell script or as complex as you'd like. > > > > First, I generally agree with your anti-bloat sentiments. > > Sure, I have the capability to write the script or C program, and stuff > it into /usr/compat/linux/usr/bin, but this isn't a general solution > for Jane Doe user. She wants/needs to run linux software, and she > may not have the know-how to work around this problem. Neither > ports/emulator/linux_lib nor ports/devel/linux_devel supply a uname(1). Ok, then provide one as part of linux_devel. It's a simple as adding a patch to the port that adds a simple script that returns linux. > I am not claiming that my suggested solution is the best solution. > But, we can't ignore the problem exists. At this point time, the > Portland Group has no intention of supporting a native FreeBSD version > of their software. I suspect other commerical vendors will have a > similar attitude (particularly if they know about FreeBSD's linux > emulation). Then they need to be informed. The easiest solution is almost always the wrong solution. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 09:59:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA00510 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 09:59:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA00505 for ; Mon, 9 Nov 1998 09:59:49 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id MAA07908; Mon, 9 Nov 1998 12:59:33 -0500 (EST) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id NAA22246; Mon, 9 Nov 1998 13:46:23 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id NAA24094; Mon, 9 Nov 1998 13:00:39 -0500 (EST) Date: Mon, 9 Nov 1998 13:00:39 -0500 (EST) From: Thomas David Rivers Message-Id: <199811091800.NAA24094@lakes.dignus.com> To: rivers@dignus.com, sgk@troutmask.apl.washington.edu Subject: Re: linux software installation and uname Cc: hackers@FreeBSD.ORG In-Reply-To: <199811091756.JAA10389@troutmask.apl.washington.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > According to Thomas David Rivers: > > > > > > to report "Linux" to install the software. With the > > > expected availability of more commericial software for Linux, > > > it seems necessary to provide uname(1) the capability to > > > report "Linux" in place of "FreeBSD". > > > > We've been here before. The consensus - after considerable > > debate - was to not make such a change. > > It was only a pro-active suggestion. I was unaware of previous debate. > > > The problem is that several automated processes - particularly > > WEB related - use uname to determine what kind of machines > > they are running on. If we return "Linux" - then we inflate > > the linux numbers at the cost of our own. > > It's better to infate the linux numbers, than to cut-off one's only > means to run certain software. For example, there are no open > source Fortran 90 compilers. You must purchase a commerical > F90 compiler and run it under linux emulation. > > > In my particular instance, I was able to persuade the vendor > > that it was artificially limiting its customer base. And thus, > > the uname check was changed to accept either "FreeBSD" or "Linux". > > Perhaps you could do the same with the Lahey people. > > Been there. PGI has no intention at this time to support FreeBSD > because they do not have sufficient tech. support for FreeBSD. > Ah then... seems like putting a uname in /compat/linux might be the way to go... You mentioned it was the install program, right; does it run the uname command? In my case, the license manager was call the uname() system function... I know how frustrating this can be - fortunately, my vendor didn't have a really good reason for checking the uname to begin with... so I was able to persuade him. Perhaps you can follow that route? i.e. ask them what they do with the uname.... point out that it may not be that useful anyway... Good luck! - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 10:02:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00927 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 10:02:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00919 for ; Mon, 9 Nov 1998 10:02:22 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id TAA06131; Mon, 9 Nov 1998 19:02:06 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id TAA15509; Mon, 9 Nov 1998 19:02:06 +0100 (MET) Message-ID: <19981109190205.46567@follo.net> Date: Mon, 9 Nov 1998 19:02:05 +0100 From: Eivind Eklund To: Steve Kargl , Nate Williams Cc: hackers@FreeBSD.ORG Subject: Re: linux software installation and uname References: <199811091713.KAA04612@mt.sri.com> <199811091746.JAA10366@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199811091746.JAA10366@troutmask.apl.washington.edu>; from Steve Kargl on Mon, Nov 09, 1998 at 09:46:42AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 09, 1998 at 09:46:42AM -0800, Steve Kargl wrote: > I am not claiming that my suggested solution is the best solution. > But, we can't ignore the problem exists. At this point time, the > Portland Group has no intention of supporting a native FreeBSD version > of their software. I suspect other commerical vendors will have a > similar attitude (particularly if they know about FreeBSD's linux > emulation). Which is why they should have the LINUX VERSION check for either FreeBSD or Linux. The other option is to create a ports category 'commercial' that is a set of ports of commercial software, to get it to install correctly. It can't be built as packages normally, of course, but it would provide a very nice way of installing and supporting commercial software. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 10:12:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01945 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 10:12:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01939 for ; Mon, 9 Nov 1998 10:12:41 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id KAA10498; Mon, 9 Nov 1998 10:16:31 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811091816.KAA10498@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname In-Reply-To: <199811091800.NAA24094@lakes.dignus.com> from Thomas David Rivers at "Nov 9, 1998 1: 0:39 pm" To: rivers@dignus.com (Thomas David Rivers) Date: Mon, 9 Nov 1998 10:16:31 -0800 (PST) Cc: rivers@dignus.com, hackers@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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Thomas David Rivers: > > > > Ah then... seems like putting a uname in /compat/linux might be > the way to go... You mentioned it was the install program, right; > does it run the uname command? In my case, the license manager was > call the uname() system function... It's uname(1) in the install script. The license manager was a whole other problem ;-) > Perhaps you can follow that route? i.e. ask them what they do with the > uname.... point out that it may not be that useful anyway... They use "uname -s" to determine if you are running i386 linux or i386 solaris. They use "uname -n" to determine the machine name for automatic registeration of their product and license management. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 10:17:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02390 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 10:17:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alive.znep.com (207-178-54-226.go2net.com [207.178.54.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02381 for ; Mon, 9 Nov 1998 10:16:58 -0800 (PST) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.1/8.9.1) with ESMTP id KAA11523; Mon, 9 Nov 1998 10:12:07 -0800 (PST) (envelope-from marcs@znep.com) Date: Mon, 9 Nov 1998 10:12:07 -0800 (PST) From: Marc Slemko To: Nate Williams cc: hackers@FreeBSD.ORG Subject: Re: Supporting more than FD_SETSIZE fd's In-Reply-To: <199811091734.KAA04752@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Nov 1998, Nate Williams wrote: > I looked through the handbook and the FAQ and didn't find anything, so > hopefully someone can help me out. > > I need to support more than the default 255 FD's in an application (the > JDK for what it's worth). To be portable, the code uses fd_set as > defined in . Unfortunately, unless I redefine FD_SETSIZE > in every file that uses it, I still have a hard-limit on the number of > FD's the application can use. > > Is there any 'portable' way of getting around this? I'd really like to > have it use whichever open FD that the limit allows, but I know now way > of having this happen? > > I looked through the code in Apache, and I don't see how it does this, > since I never saw any re-definition of FD_SETSIZE, or use of anything > other than fd_setsize. (Although, I did see mention of FD_SETSIZE quite > a bit in the comments.) Apache doesn't use select() on high numbered descriptors so it doesn't matter. It does take efforts to move things like logging descriptors up high so it can keep the first ~15 free for things that need them. FD_SETSIZE doesn't limit the number of descriptors, it just limits the highest descriptor you can pass to select(). There are various possible workarounds: - use poll(). Only on 3.0 unfortunately. - on 3.0, FD_SETSIZE defaults to 1024. - redefine FD_SETSIZE before including sys/types.h. This may seem to be a pain, but in most large projects you should have some common header files you can use for that anyway. This doesn't fix any libraries that you use though, which may use select() internally with a small FD_SETSIZE. Note that Solaris 2.6 is limited to a FD_SETSIZE of 256 (which can't be changed), so they must have some way around that. Is likely using poll() though. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 10:18:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02579 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 10:18:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02574 for ; Mon, 9 Nov 1998 10:18:50 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id MAA10332; Mon, 9 Nov 1998 12:18:15 -0600 (CST) Date: Mon, 9 Nov 1998 12:18:15 -0600 From: Dan Nelson To: Steve Kargl , Thomas David Rivers Cc: hackers@FreeBSD.ORG Subject: Re: linux software installation and uname Message-ID: <19981109121815.A6400@emsphone.com> References: <199811091735.MAA23943@lakes.dignus.com> <199811091756.JAA10389@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.3i In-Reply-To: <199811091756.JAA10389@troutmask.apl.washington.edu>; from "Steve Kargl" on Mon Nov 9 09:56:33 GMT 1998 X-OS: FreeBSD 2.2.7-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Nov 09), Steve Kargl said: > According to Thomas David Rivers: > > We've been here before. The consensus - after considerable debate > > - was to not make such a change. > > It was only a pro-active suggestion. I was unaware of previous debate. > > > The problem is that several automated processes - particularly WEB > > related - use uname to determine what kind of machines they are > > running on. If we return "Linux" - then we inflate the linux > > numbers at the cost of our own. > > It's better to infate the linux numbers, than to cut-off one's only > means to run certain software. For example, there are no open source > Fortran 90 compilers. You must purchase a commerical F90 compiler > and run it under linux emulation. On the other hand, there are no good open source COBOL compilers. We run Microfocus COBOL under SCO emulation. I vote we change FreeBSD's uname to return "SCO_SV". Wait. I'm also running the BSD/OS Quake server. I vote we change FreeBSD's uname to return "BSD/OS". Wait. See a problem here? :) > Been there. PGI has no intention at this time to support FreeBSD > because they do not have sufficient tech. support for FreeBSD. ditto MicroFocus. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 10:26:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03578 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 10:26:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03564 for ; Mon, 9 Nov 1998 10:26:36 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA06476; Mon, 9 Nov 1998 11:26:21 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA05253; Mon, 9 Nov 1998 11:26:16 -0700 Date: Mon, 9 Nov 1998 11:26:16 -0700 Message-Id: <199811091826.LAA05253@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Marc Slemko Cc: Nate Williams , hackers@FreeBSD.ORG Subject: Re: Supporting more than FD_SETSIZE fd's In-Reply-To: References: <199811091734.KAA04752@mt.sri.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I need to support more than the default 255 FD's in an application (the > > JDK for what it's worth). ... > > I looked through the code in Apache, and I don't see how it does this, > > since I never saw any re-definition of FD_SETSIZE, or use of anything > > other than fd_setsize. (Although, I did see mention of FD_SETSIZE quite > > a bit in the comments.) > > Apache doesn't use select() on high numbered descriptors so it doesn't > matter. How does it determine if there is data on those FD's w/out select? I would think that if you have more than 255 active FD's (pretty common) then you'd have a problem. > FD_SETSIZE doesn't limit the number of descriptors, it just limits the > highest descriptor you can pass to select(). Right, hence my question on how other applications deal with the problem, since select doesn't have inherent limitation. > There are various possible workarounds: > > - use poll(). Only on 3.0 unfortunately. > > - on 3.0, FD_SETSIZE defaults to 1024. I'm on 2.2.* > - redefine FD_SETSIZE before including sys/types.h. This may seem to be a > pain, but in most large projects you should have some common header files > you can use for that anyway. This doesn't fix any libraries that you use > though, which may use select() internally with a small FD_SETSIZE. No external libraries are used except for Motif. I'm not sure if it uses Select, but I doubt it. In any case, I'm still defaulting to a larger limit, which is still not a great solution. > Note that Solaris 2.6 is limited to a FD_SETSIZE of 256 (which can't be > changed), so they must have some way around that. Is likely using poll() > though. Solaris/Linux both use poll, which again doesn't exist on 2.2. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 10:29:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03877 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 10:29:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03867 for ; Mon, 9 Nov 1998 10:29:51 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id NAA13895; Mon, 9 Nov 1998 13:29:22 -0500 (EST) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id OAA22308; Mon, 9 Nov 1998 14:15:56 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id NAA24229; Mon, 9 Nov 1998 13:30:12 -0500 (EST) Date: Mon, 9 Nov 1998 13:30:12 -0500 (EST) From: Thomas David Rivers Message-Id: <199811091830.NAA24229@lakes.dignus.com> To: marcs@znep.com, nate@mt.sri.com Subject: Re: Supporting more than FD_SETSIZE fd's Cc: hackers@FreeBSD.ORG In-Reply-To: <199811091826.LAA05253@mt.sri.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > I need to support more than the default 255 FD's in an application (the > > > JDK for what it's worth). > ... > > > I looked through the code in Apache, and I don't see how it does this, > > > since I never saw any re-definition of FD_SETSIZE, or use of anything > > > other than fd_setsize. (Although, I did see mention of FD_SETSIZE quite > > > a bit in the comments.) > > > > Apache doesn't use select() on high numbered descriptors so it doesn't > > matter. > > How does it determine if there is data on those FD's w/out select? I > would think that if you have more than 255 active FD's (pretty common) > then you'd have a problem. > > > FD_SETSIZE doesn't limit the number of descriptors, it just limits the > > highest descriptor you can pass to select(). > > Right, hence my question on how other applications deal with the > problem, since select doesn't have inherent limitation. > > > There are various possible workarounds: > > > > - use poll(). Only on 3.0 unfortunately. > > > > - on 3.0, FD_SETSIZE defaults to 1024. > > I'm on 2.2.* > > > - redefine FD_SETSIZE before including sys/types.h. This may seem to be a > > pain, but in most large projects you should have some common header files > > you can use for that anyway. This doesn't fix any libraries that you use > > though, which may use select() internally with a small FD_SETSIZE. > > No external libraries are used except for Motif. I'm not sure if it > uses Select, but I doubt it. In any case, I'm still defaulting to a > larger limit, which is still not a great solution. I believe you'll find that X11 (on which Motif is based) does use select(). - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 10:33:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04283 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 10:33:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04277 for ; Mon, 9 Nov 1998 10:33:41 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id JAA07724; Mon, 9 Nov 1998 09:32:59 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Steve Kargl cc: hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-reply-to: Your message of "Mon, 09 Nov 1998 09:12:33 PST." <199811091712.JAA10172@troutmask.apl.washington.edu> Date: Mon, 09 Nov 1998 09:32:59 -0800 Message-ID: <7720.910632779@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > of the expected "Linux". Thus, I had to alter uname(1) > to report "Linux" to install the software. With the Ick. This hack seems to be insufficiently general if you're going to hack it like this. Why not make a UNAME_OS_OVERRIDE variable or something which simply contains the string to spit out?! :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 10:34:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04398 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 10:34:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04392 for ; Mon, 9 Nov 1998 10:34:07 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id KAA10627; Mon, 9 Nov 1998 10:37:58 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811091837.KAA10627@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname In-Reply-To: <19981109121815.A6400@emsphone.com> from Dan Nelson at "Nov 9, 1998 12:18:15 pm" To: dnelson@emsphone.com (Dan Nelson) Date: Mon, 9 Nov 1998 10:37:58 -0800 (PST) Cc: rivers@dignus.com, hackers@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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Dan Nelson: > In the last episode (Nov 09), Steve Kargl said: > > According to Thomas David Rivers: > > > We've been here before. The consensus - after considerable debate > > > - was to not make such a change. > > > > It was only a pro-active suggestion. I was unaware of previous debate. > > > > > The problem is that several automated processes - particularly WEB > > > related - use uname to determine what kind of machines they are > > > running on. If we return "Linux" - then we inflate the linux > > > numbers at the cost of our own. > > > > It's better to infate the linux numbers, than to cut-off one's only > > means to run certain software. For example, there are no open source > > Fortran 90 compilers. You must purchase a commerical F90 compiler > > and run it under linux emulation. > > On the other hand, there are no good open source COBOL compilers. We > run Microfocus COBOL under SCO emulation. I vote we change FreeBSD's > uname to return "SCO_SV". Wait. I'm also running the BSD/OS Quake > server. I vote we change FreeBSD's uname to return "BSD/OS". Wait. > See a problem here? :) > % setenv ALT_UNAME SCO_SV % uname -s SCO_SV % setenv ALT_UNAME Linux % uname -s Linux % setenv ALT_UNAME FooOS % uname -s FooOS % unsetenv ALT_UNAME No, I don't see a problem. I'm suggesting a useful change to uname(1) not a change to uname(3). -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html --- uname.c.orig Mon Nov 9 08:46:41 1998 +++ uname.c Mon Nov 9 10:28:06 1998 @@ -105,12 +105,15 @@ prefix = ""; if (flags & SFLAG) { - mib[0] = CTL_KERN; - mib[1] = KERN_OSTYPE; - len = sizeof(buf); - if (sysctl(mib, 2, &buf, &len, NULL, 0) == -1) - err(1, "sysctl"); - (void)printf("%s%.*s", prefix, (int)len, buf); + if (!getenv("ALT_UNAME")) { + mib[0] = CTL_KERN; + mib[1] = KERN_OSTYPE; + len = sizeof(buf); + if (sysctl(mib, 2, &buf, &len, NULL, 0) == -1) + err(1, "sysctl"); + (void)printf("%s%.*s", prefix, (int)len, buf); + } else + (void)printf("%s%s", prefix, getenv("ALT_UNAME")); prefix = " "; } if (flags & NFLAG) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 10:34:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04414 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 10:34:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04409 for ; Mon, 9 Nov 1998 10:34:10 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id JAA07737; Mon, 9 Nov 1998 09:33:21 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Nate Williams cc: Steve Kargl , hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-reply-to: Your message of "Mon, 09 Nov 1998 10:13:22 MST." <199811091713.KAA04612@mt.sri.com> Date: Mon, 09 Nov 1998 09:33:21 -0800 Message-ID: <7734.910632801@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually, you didn't. Stick a uname in the appropriate /compat/linux > directory and it will be called (and return Linux) which doesn't bloat > FreeBSD's code with Linux-centric bits. Ah, that's another good point. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 10:47:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05841 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 10:47:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alive.znep.com (207-178-54-226.go2net.com [207.178.54.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05834 for ; Mon, 9 Nov 1998 10:47:30 -0800 (PST) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.1/8.9.1) with ESMTP id KAA11645; Mon, 9 Nov 1998 10:42:59 -0800 (PST) (envelope-from marcs@znep.com) Date: Mon, 9 Nov 1998 10:42:58 -0800 (PST) From: Marc Slemko To: Nate Williams cc: hackers@FreeBSD.ORG Subject: Re: Supporting more than FD_SETSIZE fd's In-Reply-To: <199811091826.LAA05253@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Nov 1998, Nate Williams wrote: > > > I need to support more than the default 255 FD's in an application (the > > > JDK for what it's worth). > ... > > > I looked through the code in Apache, and I don't see how it does this, > > > since I never saw any re-definition of FD_SETSIZE, or use of anything > > > other than fd_setsize. (Although, I did see mention of FD_SETSIZE quite > > > a bit in the comments.) > > > > Apache doesn't use select() on high numbered descriptors so it doesn't > > matter. > > How does it determine if there is data on those FD's w/out select? I It doesn't have to. > would think that if you have more than 255 active FD's (pretty common) > then you'd have a problem. One connection per process at any given time. High descriptor use in Apache only comes in with logfiles, eg. 10000 vhosts with two logfiles for each. > > FD_SETSIZE doesn't limit the number of descriptors, it just limits the > > highest descriptor you can pass to select(). > > Right, hence my question on how other applications deal with the > problem, since select doesn't have inherent limitation. > > > There are various possible workarounds: > > > > - use poll(). Only on 3.0 unfortunately. > > > > - on 3.0, FD_SETSIZE defaults to 1024. > > I'm on 2.2.* > > > - redefine FD_SETSIZE before including sys/types.h. This may seem to be a > > pain, but in most large projects you should have some common header files > > you can use for that anyway. This doesn't fix any libraries that you use > > though, which may use select() internally with a small FD_SETSIZE. > > No external libraries are used except for Motif. I'm not sure if it > uses Select, but I doubt it. In any case, I'm still defaulting to a A lot of X11 stuff will use select(). > larger limit, which is still not a great solution. If you need a generic ability to select() on descriptors above 256, the only real choice you have is to redefine FD_SETSIZE everywhere and hope no other libraries cause problems. Or insist that anyone building or using it changes the global FD_SETSIZE on their system and does a make world. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 10:50:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06268 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 10:50:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ducky.net (gate.ducky.net [198.145.101.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06258 for ; Mon, 9 Nov 1998 10:50:11 -0800 (PST) (envelope-from mike@ducky.net) Received: from ducky.net (localhost.ducky.net [127.0.0.1]) by ducky.net (8.9.1/8.8.5) with ESMTP id KAA06440 for ; Mon, 9 Nov 1998 10:19:02 -0800 (PST) Message-Id: <199811091819.KAA06440@ducky.net> To: freebsd-hackers@FreeBSD.ORG Subject: EEPROM programmers that work with FreeBSD? Date: Mon, 09 Nov 1998 10:19:02 -0800 From: Mike Haertel Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anybody know of any EEPROM programmers that work with freebsd? All the ones I've seen come with DOS-based or windows-based software. Thanks, Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 10:51:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06405 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 10:51:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06400 for ; Mon, 9 Nov 1998 10:51:58 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id KAA10694; Mon, 9 Nov 1998 10:55:54 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811091855.KAA10694@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname In-Reply-To: <7734.910632801@time.cdrom.com> from "Jordan K. Hubbard" at "Nov 9, 1998 9:33:21 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 9 Nov 1998 10:55:54 -0800 (PST) Cc: nate@mt.sri.com, hackers@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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jordan K. Hubbard: > > Actually, you didn't. Stick a uname in the appropriate /compat/linux > > directory and it will be called (and return Linux) which doesn't bloat > > FreeBSD's code with Linux-centric bits. > > Ah, that's another good point. :-) > The install script on the cdrom had hardcoded tests for /usr/bin/uname and /bin/uname. If we every get to the emulation of Digital Unix and Solaris where we have /compat/linux, /compat/digital, /compat/solaris, etc., then we need several versions of uname. Now, we're talking about bloat. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 10:52:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06446 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 10:52:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ics.com (ics.com [140.186.40.192]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06441 for ; Mon, 9 Nov 1998 10:52:10 -0800 (PST) (envelope-from kaleb@ics.com) Received: from ics.com (sunoco.ics.com [140.186.40.142]) by ics.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id NAA28333 Mon, 9 Nov 1998 13:51:54 -0500 (EST) Message-ID: <364739CA.524190C4@ics.com> Date: Mon, 09 Nov 1998 13:51:54 -0500 From: "Kaleb S. KEITHLEY" Organization: Integrated Computer Solutions X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.5.1 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: Supporting more than FD_SETSIZE fd's References: <199811091830.NAA24229@lakes.dignus.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas David Rivers wrote: > > No external libraries are used except for Motif. I'm not sure if it > > uses Select, but I doubt it. In any case, I'm still defaulting to a > > larger limit, which is still not a great solution. > > I believe you'll find that X11 (on which Motif is based) does use > select(). Since X11R6(.0) Xlib and Xt in the Sample Implementation use poll if the system has it, otherwise they use select. It is a given, that if you're using Motif, you are also using Xt and Xlib; thus you are using either select or poll. -- Kaleb S. KEITHLEY To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 11:00:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07629 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 11:00:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07599 for ; Mon, 9 Nov 1998 11:00:30 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id OAA17711; Mon, 9 Nov 1998 14:02:59 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Mon, 9 Nov 1998 14:02:59 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Mike Haertel cc: freebsd-hackers@FreeBSD.ORG Subject: Re: EEPROM programmers that work with FreeBSD? In-Reply-To: <199811091819.KAA06440@ducky.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've seen a bunch of traffic about success stories using "doscmd" to run such software. maybe this will help you? (it's included in freebsd but doesn't seem to compile/install automagically with buildworld) Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Mon, 9 Nov 1998, Mike Haertel wrote: > Does anybody know of any EEPROM programmers that work > with freebsd? All the ones I've seen come with DOS-based > or windows-based software. > > Thanks, > > Mike > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 11:01:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07855 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 11:01:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07832 for ; Mon, 9 Nov 1998 11:01:13 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from o2.cs.rpi.edu (root@o2.cs.rpi.edu [128.113.96.156]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id OAA22651; Mon, 9 Nov 1998 14:00:57 -0500 (EST) Received: from localhost (crossd@localhost) by o2.cs.rpi.edu (8.9.1a/8.9.1) with ESMTP id NAA06183; Mon, 9 Nov 1998 13:58:49 -0500 (EST) X-Authentication-Warning: o2.cs.rpi.edu: crossd owned process doing -bs Date: Mon, 9 Nov 1998 13:58:48 -0500 From: "David E. Cross" To: Steve Kargl cc: "Jordan K. Hubbard" , nate@mt.sri.com, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <199811091855.KAA10694@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Nov 1998, Steve Kargl wrote: > ... > The install script on the cdrom had hardcoded tests for > /usr/bin/uname and /bin/uname. They should not do that; they are making the assumption that they know better than you how your machine ought to be setup. > > If we every get to the emulation of Digital Unix and Solaris > where we have /compat/linux, /compat/digital, /compat/solaris, > etc., then we need several versions of uname. Now, we're talking > about bloat. Bloat for some, or bloat for all. If you merge it into the main tree *everyone* gets that bloat, and then who is responsible for maintaining 'uname'? If you break it out into the individual directories then only those who require the mentioned functionality will suffer the bloat; and it would be easy to setup a clear maintainer for the code. Bloat is more than just code bloat, it is administrative bloat as well. -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 11:03:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08303 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 11:03:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from vader.ed.gov (vader.ed.gov [165.224.216.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08296; Mon, 9 Nov 1998 11:03:37 -0800 (PST) (envelope-from Clarence_Griffin@ed.gov) Received: from smtpgwy1.ed.gov (smtpgwy1.ed.gov [165.224.16.166]) by vader.ed.gov (8.9.1a/8.8.4) with SMTP id OAA00143; Mon, 9 Nov 1998 14:03:52 -0500 (EST) Received: from ccMail by smtpgwy1.ed.gov (IMA Internet Exchange 2.12 Enterprise) id 0029A194; Mon, 9 Nov 1998 13:52:39 -0500 Date: Mon, 9 Nov 1998 12:40:37 -0500 Message-ID: <0029A194.003144@ed.gov> From: Clarence_Griffin@ed.gov (Clarence Griffin) Subject: X display 'laps' itself. To: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As a newbie, I am uncertain about how much is enough concerning information about this problem. I've installed FreeBSD 2.2.6, on a Compaq Deskpro, with a built-in video card, which FreeBSD reveals as an "ATI Mach64 with IBM514 Ramdac". The Monitor is a Gateway2000 EV700. The install was working correctly, including X, at one time, except that the /usr directory was maxed out at 103%, so I opted to reinstall on the same machine using a larger portion the 3GB harddisk for the /usr directory. I think I did everything exactly like the first time, but now, when X gets running, the display shows that there seems to be a devideing line in the center of the display, where when the mouse is passed over it, it disappears in the center of the screen and reemerges from either the right or left. The left side of the display is stable as a rock, while the right half seems to have a little flicker in it. Frankly, I don't even know enough about UNIX, X, or FreeBSD to begin to look for the problem. Anyone have any suggestions? dg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 11:17:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09523 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 11:17:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09513 for ; Mon, 9 Nov 1998 11:16:58 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id KAA09446; Mon, 9 Nov 1998 10:10:58 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: "David E. Cross" cc: Steve Kargl , nate@mt.sri.com, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-reply-to: Your message of "Mon, 09 Nov 1998 13:58:48 EST." Date: Mon, 09 Nov 1998 10:10:58 -0800 Message-ID: <9442.910635058@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > They should not do that; they are making the assumption that they know > better than you how your machine ought to be setup. Um, no offense but I don't think that's relevant here. The essence of emulation is to make the assumptions which work on one platform work on another, nothing more, nothing less - technical correctness doesn't even enter into it. :-) I think the correct thing to do here is simply give uname(1) some truly switchable behavior, as Steve's second patch did. Sure it's a gross hack, but we have to stay focused on the fact that in the real world, people grab and abuse the output of uname(1) to request platform specific information when they should be asking for *feature* specific information and that's just life. For the addition of 4 stinking lines of code, we can gain the ability to *optionally* deal with it and I say that's a reasonable trade-off. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 11:29:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11041 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 11:29:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11030 for ; Mon, 9 Nov 1998 11:29:36 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA06998; Mon, 9 Nov 1998 12:29:18 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA05724; Mon, 9 Nov 1998 12:29:18 -0700 Date: Mon, 9 Nov 1998 12:29:18 -0700 Message-Id: <199811091929.MAA05724@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Thomas David Rivers Cc: marcs@znep.com, nate@mt.sri.com, hackers@FreeBSD.ORG Subject: Re: Supporting more than FD_SETSIZE fd's In-Reply-To: <199811091830.NAA24229@lakes.dignus.com> References: <199811091826.LAA05253@mt.sri.com> <199811091830.NAA24229@lakes.dignus.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > - redefine FD_SETSIZE before including sys/types.h. This may seem to be a > > > pain, but in most large projects you should have some common header files > > > you can use for that anyway. This doesn't fix any libraries that you use > > > though, which may use select() internally with a small FD_SETSIZE. > > > > No external libraries are used except for Motif. I'm not sure if it > > uses Select, but I doubt it. In any case, I'm still defaulting to a > > larger limit, which is still not a great solution. > > I believe you'll find that X11 (on which Motif is based) does use > select(). Maybe, but I'm not worrying about X11 not doing the right thing, since I believe that part of the code is working... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 11:31:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11269 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 11:31:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11264 for ; Mon, 9 Nov 1998 11:31:57 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA07025; Mon, 9 Nov 1998 12:31:34 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA05779; Mon, 9 Nov 1998 12:31:33 -0700 Date: Mon, 9 Nov 1998 12:31:33 -0700 Message-Id: <199811091931.MAA05779@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Steve Kargl Cc: jkh@time.cdrom.com (Jordan K. Hubbard), nate@mt.sri.com, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <199811091855.KAA10694@troutmask.apl.washington.edu> References: <7734.910632801@time.cdrom.com> <199811091855.KAA10694@troutmask.apl.washington.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Actually, you didn't. Stick a uname in the appropriate /compat/linux > > > directory and it will be called (and return Linux) which doesn't bloat > > > FreeBSD's code with Linux-centric bits. > > > > Ah, that's another good point. :-) > > > > The install script on the cdrom had hardcoded tests for > /usr/bin/uname and /bin/uname. > > If we every get to the emulation of Digital Unix and Solaris > where we have /compat/linux, /compat/digital, /compat/solaris, > etc., then we need several versions of uname. Now, we're talking > about bloat. Actually, the code would be *much* shorter than modifying uname for each platform, since uname on each platform has very different functionality and/or flags. So, bloat would be reduced, not increased. Complexity would also be limited to the code/script that is for each OS, therefore reducing maintenance on other platforms. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 11:34:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11639 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 11:34:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11634 for ; Mon, 9 Nov 1998 11:34:24 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA07055; Mon, 9 Nov 1998 12:34:00 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA05814; Mon, 9 Nov 1998 12:33:58 -0700 Date: Mon, 9 Nov 1998 12:33:58 -0700 Message-Id: <199811091933.MAA05814@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: "David E. Cross" , Steve Kargl , nate@mt.sri.com, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <9442.910635058@time.cdrom.com> References: <9442.910635058@time.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think the correct thing to do here is simply give uname(1) some > truly switchable behavior, as Steve's second patch did. The user then has to be aware of the 'LINUX_EMULATION' environment variable, which is non-intuitive. The /compat/linux script is a much better solution since it doesn't require any magic environment knowledge that must be modified if you run binaries from multiple 'emulated' OS's. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 11:37:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12224 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 11:37:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12209 for ; Mon, 9 Nov 1998 11:37:10 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id KAA00448; Mon, 9 Nov 1998 10:36:18 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Nate Williams cc: "David E. Cross" , Steve Kargl , hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-reply-to: Your message of "Mon, 09 Nov 1998 12:33:58 MST." <199811091933.MAA05814@mt.sri.com> Date: Mon, 09 Nov 1998 10:36:18 -0800 Message-ID: <444.910636578@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The user then has to be aware of the 'LINUX_EMULATION' environment I said the second patch, not the first. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 11:44:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12844 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 11:44:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12838 for ; Mon, 9 Nov 1998 11:44:12 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id LAA11148; Mon, 9 Nov 1998 11:47:56 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811091947.LAA11148@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname In-Reply-To: from "David E. Cross" at "Nov 9, 1998 1:58:48 pm" To: crossd@cs.rpi.edu (David E. Cross) Date: Mon, 9 Nov 1998 11:47:56 -0800 (PST) Cc: jkh@time.cdrom.com, nate@mt.sri.com, hackers@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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to David E. Cross: > > > On Mon, 9 Nov 1998, Steve Kargl wrote: > > ... > > The install script on the cdrom had hardcoded tests for > > /usr/bin/uname and /bin/uname. > They should not do that; they are making the assumption that they know > better than you how your machine ought to be setup. > > > > > If we every get to the emulation of Digital Unix and Solaris > > where we have /compat/linux, /compat/digital, /compat/solaris, > > etc., then we need several versions of uname. Now, we're talking > > about bloat. > Bloat for some, or bloat for all. If you merge it into the main tree > *everyone* gets that bloat, and then who is responsible for maintaining > 'uname'? If you break it out into the individual directories then only > those who require the mentioned functionality will suffer the bloat; and > it would be easy to setup a clear maintainer for the code. Bloat is more > than just code bloat, it is administrative bloat as well. > Here is the nice little uname test from the vendor's install script: # what type of target? if test -x /usr/bin/uname ; then uname=/usr/bin/uname elif test -x /bin/uname ; then uname=/bin/uname else # Never seen it anywhere but /bin or /usr/bin, so hopefully it's # in $PATH already. type uname > /dev/null 2>&1 if test $? -ne 0 ; then echo "install: uname not found in \$PATH environment variable" quit else uname=uname fi fi You'll never pick up /compat/linux/bin/uname unless you delete/rename /usr/bin/uname. I'm willing to bet that other vendors make similar assumptions. As far as the bloat argument goes: troutmask:root[228] ll uname /usr/bin/uname -r-xr-xr-x 1 root wheel - 3880 Oct 22 10:04 /usr/bin/uname* -rwxr-xr-x 1 root wheel - 3996 Nov 9 11:39 uname* Can you really write a 116 bytes /compat/linux/bin/uname? It must handle "uname", "uname -s", "uname -n", etc. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 11:44:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12893 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 11:44:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from caffeine.sundial.net (caffeine.sundial.net [204.181.150.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12885; Mon, 9 Nov 1998 11:44:41 -0800 (PST) (envelope-from gmelists@caffeine.sundial.net) Received: from coffee (coffee.caffeine.sundial.net [10.0.0.2]) by caffeine.sundial.net (8.9.1/8.9.1) with SMTP id OAA17622; Mon, 9 Nov 1998 14:42:22 -0500 (EST) (envelope-from gmelists@caffeine.sundial.net) Message-Id: <3.0.3.32.19981109144216.0095f7c0@10.0.0.1> X-Sender: gmelists@10.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Mon, 09 Nov 1998 14:42:16 -0500 To: Clarence_Griffin@ed.gov (Clarence Griffin) From: George Ellenburg Subject: Re: X display 'laps' itself. Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: <0029A194.003144@ed.gov> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Check out Compaq's website, under Technical Support. You'll need to download the boot and F10 Setup Disks for your Deskpro. I was running a Deskpro 4000. The embedded video card was a Cirrus Logic CL-GD5446 card with 2Mb RAM. Booting with the Compaq supplied boot disks and setup utilities will reveal the exact card for you, too. I should point out, that when running the SVGA X Server, I, too, would get horizontal lines in the middle of the screen - not often, but mainly when the the screen updates would be fast (like catting a long file in an xterm window). I used kde however, so refreshing the desktop was easy and since it only happened every once in a while I wasn't too concerned. There is an X server specifically for the Cirrus Logic or ATI cards, but since I had 1024x768x16bpp resolution anyway, I wasn't too concerned. Make the floppies from Compaq first, and find out exactly what you've got in there. If you need any help running XF86Setup afterwards, let me know and I'll be more than happy to walk you through it. Regards, George Ellenburg At 12:40 PM 11/9/98 -0500, Clarence Griffin wrote: > I've installed FreeBSD 2.2.6, on a Compaq Deskpro, with a built-in > video card, which FreeBSD reveals as an "ATI Mach64 with IBM514 > Ramdac". The Monitor is a Gateway2000 EV700. > I think I did everything exactly like the first time, but now, when X > gets running, the display shows that there seems to be a devideing > line in the center of the display, where when the mouse is passed over > it, it disappears in the center of the screen and reemerges from > either the right or left. The left side of the display is stable as a > rock, while the right half seems to have a little flicker in it. heck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 11:49:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13224 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 11:49:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13218 for ; Mon, 9 Nov 1998 11:48:59 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id LAA11165; Mon, 9 Nov 1998 11:52:54 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811091952.LAA11165@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname In-Reply-To: <444.910636578@time.cdrom.com> from "Jordan K. Hubbard" at "Nov 9, 1998 10:36:18 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 9 Nov 1998 11:52:54 -0800 (PST) Cc: nate@mt.sri.com, crossd@cs.rpi.edu, hackers@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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jordan K. Hubbard: > > The user then has to be aware of the 'LINUX_EMULATION' environment > > I said the second patch, not the first. > Whoops. I may have sent you a private reply. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 11:53:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13651 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 11:53:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13646 for ; Mon, 9 Nov 1998 11:52:56 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id LAA11186; Mon, 9 Nov 1998 11:56:51 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811091956.LAA11186@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname In-Reply-To: <199811091933.MAA05814@mt.sri.com> from Nate Williams at "Nov 9, 1998 12:33:58 pm" To: nate@mt.sri.com (Nate Williams) Date: Mon, 9 Nov 1998 11:56:51 -0800 (PST) Cc: jkh@time.cdrom.com, crossd@cs.rpi.edu, nate@mt.sri.com, hackers@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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Nate Williams: > > I think the correct thing to do here is simply give uname(1) some > > truly switchable behavior, as Steve's second patch did. > > The user then has to be aware of the 'LINUX_EMULATION' environment > variable, which is non-intuitive. The /compat/linux script is a much > better solution since it doesn't require any magic environment > knowledge that must be modified if you run binaries from multiple > 'emulated' OS's. > You're assuming the vendor supplied script will pick up the script in /compat/linux. That, is not the case for the Portland Group script: if test -x /usr/bin/uname ; then uname=/usr/bin/uname elif test -x /bin/uname ; then uname=/bin/uname else # Never seen it anywhere but /bin or /usr/bin, so hopefully it's # in $PATH already. type uname > /dev/null 2>&1 if test $? -ne 0 ; then echo "install: uname not found in \$PATH environment variable" quit else uname=uname fi fi -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 12:04:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14889 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 12:04:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14883 for ; Mon, 9 Nov 1998 12:04: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.8.8/8.8.8) with SMTP id NAA07292; Mon, 9 Nov 1998 13:04:08 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA06080; Mon, 9 Nov 1998 13:04:07 -0700 Date: Mon, 9 Nov 1998 13:04:07 -0700 Message-Id: <199811092004.NAA06080@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Steve Kargl Cc: nate@mt.sri.com (Nate Williams), jkh@time.cdrom.com, crossd@cs.rpi.edu, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <199811091956.LAA11186@troutmask.apl.washington.edu> References: <199811091933.MAA05814@mt.sri.com> <199811091956.LAA11186@troutmask.apl.washington.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I think the correct thing to do here is simply give uname(1) some > > > truly switchable behavior, as Steve's second patch did. > > > > The user then has to be aware of the 'LINUX_EMULATION' environment > > variable, which is non-intuitive. The /compat/linux script is a much > > better solution since it doesn't require any magic environment > > knowledge that must be modified if you run binaries from multiple > > 'emulated' OS's. > > > > You're assuming the vendor supplied script will pick up the script > in /compat/linux. That, is not the case for the Portland Group > script: You didn't answer the question. What if I have multiple binaries from different OS's on the system. The user has to be aware of the 'magic' environment variable and have it switch between them. Once we're on that path, we're no better off than we are now. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 12:08:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15388 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 12:08:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15379 for ; Mon, 9 Nov 1998 12:08:27 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id MAA28260 for ; Mon, 9 Nov 1998 12:08:30 -0800 (PST) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00487; Mon, 9 Nov 1998 12:06:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811092006.MAA00487@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dan Nelson cc: Thomas David Rivers , freebsd-hackers@freefall.cdrom.com Subject: Re: A stdio question... does fpos_t really need to be 'long long'? In-reply-to: Your message of "Mon, 09 Nov 1998 11:09:55 CST." <19981109110955.A5248@emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Nov 1998 12:06:12 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In the last episode (Nov 09), Thomas David Rivers said: > > Ok - here's a question for the stdio internal gurus... > > > > ftell() is defined to return a 'long' (32 bits). > > fpos_t is defined as a 'long long' (64 bits). > > fgetpos() accepts an fpos_t as it's second argument, and is > > implemented as: > > > > retval = (*pos = ftell(fp)) == (fpos_t) -1; > > return (retval); > > > > If this is the case... then why is fpos_t a 'long long'? If, in > > fact, it can never be set that large? > > I noticed this back in April and commented on it. I believe the > consensus was that fsetpos()/fgetpos()/fseek()/ftell() should be > wrappers for the X/Open functions fseeko() and ftello(), which take > off_t arguments. > > Unfortunately, I never submitted patches, and neither did anyone else. > > -Dan Nelson > dnelson@emsphone.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message So submit them, dammit! 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 12:10:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15778 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 12:10:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bootp.sls.usu.edu (bootp.sls.usu.edu [129.123.82.251]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15751; Mon, 9 Nov 1998 12:10:37 -0800 (PST) (envelope-from kurto@bootp.sls.usu.edu) Received: (from kurto@localhost) by bootp.sls.usu.edu (8.8.2/8.8.2) id NAA18473; Mon, 9 Nov 1998 13:10:18 -0700 (MST) Date: Mon, 9 Nov 1998 13:10:18 -0700 (MST) From: Kurt Olsen Message-Id: <199811092010.NAA18473@bootp.sls.usu.edu> To: Clarence_Griffin@ed.gov, freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: X display 'laps' itself. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It sounds like you might be trying to use too high of a refresh rate. I didn't see it in your message, but if the left and right sides are switched and there is a gap in the middle then that is probably the case. Of course unless you are running xdm or something you might not be able to tell if the sides are switched or not. You also might want to try a couple of generic video modes (640x480x8 or 640x480x16) to make sure that it is using the proper "driver" for your card. Kurt Olsen kurto@bootp.sls.usu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 12:14:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16227 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 12:14:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16217 for ; Mon, 9 Nov 1998 12:14:46 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id PAA02222 for hackers@freebsd.org; Mon, 9 Nov 1998 15:14:23 -0500 (EST) (envelope-from lee) Message-ID: <19981109151423.A2157@tidalwave.net> Date: Mon, 9 Nov 1998 15:14:23 -0500 From: Lee Cremeans To: hackers@FreeBSD.ORG Subject: Encryption coprocessor, part 2. Reply-To: lcremean@tidalwave.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All right, I've figured out what I want to do with the packets (though a zero-copy implementation would be faster, I doubt it's easy to do here). I'm going to set up a list of buffers in memory, then feed their address to the chip as needed...(actually, it'll be four rings, since there are 4 DMA channels). What I need to know now is what the best way would be to get the user buffers into the kernel (I'm assuming we'd be trying to send pointers to all four at once, then copying). -- Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | mailto:lcremean@tidalwave.net http://st-lcremean.tidalwave.net | Powered by FreeBSD 3.0-CURRENT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 12:17:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16481 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 12:17:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16475 for ; Mon, 9 Nov 1998 12:17:07 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA29423; Mon, 9 Nov 1998 12:13:39 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdw29421; Mon Nov 9 20:13:35 1998 Date: Mon, 9 Nov 1998 12:13:04 -0800 (PST) From: Julian Elischer To: Steve Kargl cc: hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <199811091712.JAA10172@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This has been a source of much contention. it should be an option of some sort.. preferably run-time but possibly compile time. julian On Mon, 9 Nov 1998, Steve Kargl wrote: > Ladies and Gents, > > I've recently installed the Portland Groups's Fortran 90 > for Linux on my system (it works!). However, during the > installation from the cdrom, a install script is executed > that contains a test involving "uname -s" to ensure the > installation is on a system running Linux. Of course, > "uname -s" on a FreeBSD system returns "FreeBSD" instead > of the expected "Linux". Thus, I had to alter uname(1) > to report "Linux" to install the software. With the > expected availability of more commericial software for Linux, > it seems necessary to provide uname(1) the capability to > report "Linux" in place of "FreeBSD". > > -- > Steve > > finger kargl@troutmask.apl.washington.edu > http://troutmask.apl.washington.edu/~clesceri/kargl.html > > > *** uname.c.orig Mon Nov 9 08:46:41 1998 > --- uname.c Mon Nov 9 08:49:54 1998 > *************** > *** 105,116 **** > prefix = ""; > > if (flags & SFLAG) { > ! mib[0] = CTL_KERN; > ! mib[1] = KERN_OSTYPE; > ! len = sizeof(buf); > ! if (sysctl(mib, 2, &buf, &len, NULL, 0) == -1) > ! err(1, "sysctl"); > ! (void)printf("%s%.*s", prefix, (int)len, buf); > prefix = " "; > } > if (flags & NFLAG) { > --- 105,119 ---- > prefix = ""; > > if (flags & SFLAG) { > ! if (!getenv("LINUX_UNAME")) { > ! mib[0] = CTL_KERN; > ! mib[1] = KERN_OSTYPE; > ! len = sizeof(buf); > ! if (sysctl(mib, 2, &buf, &len, NULL, 0) == -1) > ! err(1, "sysctl"); > ! (void)printf("%s%.*s", prefix, (int)len, buf); > ! } else > ! (void)printf("%sLinux", prefix); > prefix = " "; > } > if (flags & NFLAG) { > *** uname.1.orig Mon Nov 9 09:06:23 1998 > --- uname.1 Mon Nov 9 09:08:56 1998 > *************** > *** 72,77 **** > --- 72,82 ---- > to standard output. > .It Fl s > Write the name of the operating system implementation to standard output. > + If the environmental variable > + .Em LINUX_UNAME > + is set, then write > + .Em Linux > + to standard output. > .It Fl v > Write the version level of this release of the operating system > to standard output. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 12:18:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16607 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 12:18:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16602 for ; Mon, 9 Nov 1998 12:18:16 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA07414; Mon, 9 Nov 1998 13:16:58 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA06221; Mon, 9 Nov 1998 13:16:57 -0700 Date: Mon, 9 Nov 1998 13:16:57 -0700 Message-Id: <199811092016.NAA06221@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Steve Kargl Cc: dnelson@emsphone.com (Dan Nelson), rivers@dignus.com, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <199811091837.KAA10627@troutmask.apl.washington.edu> References: <19981109121815.A6400@emsphone.com> <199811091837.KAA10627@troutmask.apl.washington.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On the other hand, there are no good open source COBOL compilers. We > > run Microfocus COBOL under SCO emulation. I vote we change FreeBSD's > > uname to return "SCO_SV". Wait. I'm also running the BSD/OS Quake > > server. I vote we change FreeBSD's uname to return "BSD/OS". Wait. > > See a problem here? :) > > > > % setenv ALT_UNAME SCO_SV > % uname -s > SCO_SV > % setenv ALT_UNAME Linux > % uname -s > Linux > % setenv ALT_UNAME FooOS > % uname -s > FooOS > % unsetenv ALT_UNAME Ahh, but what happens when I have to run the same applications in the same shell? Do I have to modify my environment everytime I run a different application? Do I have to remember which 'emulated OS' the application runs? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 12:20:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16843 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 12:20:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16836 for ; Mon, 9 Nov 1998 12:20:58 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA07462; Mon, 9 Nov 1998 13:20:39 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA06290; Mon, 9 Nov 1998 13:20:38 -0700 Date: Mon, 9 Nov 1998 13:20:38 -0700 Message-Id: <199811092020.NAA06290@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: Nate Williams , "David E. Cross" , Steve Kargl , hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <444.910636578@time.cdrom.com> References: <199811091933.MAA05814@mt.sri.com> <444.910636578@time.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The user then has to be aware of the 'LINUX_EMULATION' environment > > I said the second patch, not the first. Which second patch? Nate > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 12:27:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17408 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 12:27:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17403 for ; Mon, 9 Nov 1998 12:27:31 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA29584; Mon, 9 Nov 1998 12:18:42 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdE29582; Mon Nov 9 20:18:39 1998 Date: Mon, 9 Nov 1998 12:18:07 -0800 (PST) From: Julian Elischer To: "Larry S. Lile" cc: David Greenman , hackers@FreeBSD.ORG Subject: Re: mbuf question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG you can allocate a pool of buffers and attach them to the mbufs using th eexternal pointer feature, and supply your own free and duplicate functions. I have done this under BSD since 1990 works like a charm.. (In my case the buffers were on the ethernet cards (2MB on each card)) julian On Mon, 9 Nov 1998, Larry S. Lile wrote: > > > On Mon, 9 Nov 1998, David Greenman wrote: > > > >Are mbufs allocated below the 16M area? > > > > > >If they are, is it likely to change? > > > > > >Why? Because I am trying to eliminate bcopy's and mallocs in my > > >token-ring driver to gain a little more performance. > > > > They're allocated throughout the machine's physical address space. > > I was afraid of that, so I should just make new buffers and copy when > I need DMA'able memory. Otherwise I can just use the mbuf's directly. > > Thanks! > > Larry Lile > lile@stdio.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 12:34:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18176 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 12:34:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18171 for ; Mon, 9 Nov 1998 12:34:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00693; Mon, 9 Nov 1998 12:33:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811092033.MAA00693@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: lcremean@tidalwave.net cc: hackers@FreeBSD.ORG Subject: Re: Encryption coprocessor, part 2. In-reply-to: Your message of "Mon, 09 Nov 1998 15:14:23 EST." <19981109151423.A2157@tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Nov 1998 12:33:57 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > All right, I've figured out what I want to do with the packets (though a > zero-copy implementation would be faster, I doubt it's easy to do here). I'm > going to set up a list of buffers in memory, then feed their address to the > chip as needed...(actually, it'll be four rings, since there are 4 DMA > channels). What I need to know now is what the best way would be to get the > user buffers into the kernel (I'm assuming we'd be trying to send pointers > to all four at once, then copying). Er, this is really list management 101. For each buffer set you have: - a free list, populated at startup - a work queue - a done queue It sounds from your previous messages as though the control buffers are actually associated with the data buffers, so you might want to unify them. In the write routine, assuming that you mandate atomic writes of single packets, you do something like this: if (uio->uio_resid != WRITE_SIZE) return(ENOSPC); bufp = getbuf_free(); if ((error = uiomove(bufp->data, WRITE_SIZE, uio)) != 0) { putbuf_free(bufp); return(error); } putbuf_work(bufp); foointr(); the interurpt handler should do something like: if (interrupt_reason & WORK_DONE) { bufp = sc->busybuf; putbuf_done(bufp); } if (device_status & CHANNEL_FREE) { bufp = getbuf_work(); if (bufp != NULL) { sc->busybuf = bufp; stuff_buffer_into_device(); } } and the read routine should look like this: if (uio->uio_resid != READ_SIZE) return(ENOSPC); bufp = getbuf_done(); if ((error = uiomove(bufp->data, READ_SIZE, uio)) != 0) { putbuf_done(bufp); /* XXX push onto head of list */ return(error); } putbuf_free(bufp); Then you just need to arrange for the getbuf_done and getbuf_free functions to sleep if there's no buffer on the head of the queue. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 12:44:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19181 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 12:44:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19174 for ; Mon, 9 Nov 1998 12:44:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00772; Mon, 9 Nov 1998 12:43:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811092043.MAA00772@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: zhihuizhang cc: hackers Subject: Re: radix argument of kvprintf() In-reply-to: Your message of "Mon, 09 Nov 1998 12:12:29 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Nov 1998 12:43:14 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I try to figure out the meaning of the argument radix in the routine > kvprintf() in file subr_prf.c. I find that radix can be values from > 2 through 36 and is only used when you have a %n in the format. > > The specifier %n is supposed to save the number of characters we have > printed so far. But the source code of kvprintf() does not show this. > Instead, it specifies we want to print the next argument with base value > of radix. This is inconsistent with what is said about printf(3). > > Can anyone explain this for me? Thanks a lot. I think that the %n behaviour is an error; it may have been meant to be implemented but never was. The correct format specifier for the radix is %r. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 12:47:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19528 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 12:47:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gamefish.pcola.gulf.net (gamefish.pcola.gulf.net [198.69.72.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19484 for ; Mon, 9 Nov 1998 12:47:15 -0800 (PST) (envelope-from psalzman@gamefish.pcola.gulf.net) Received: from localhost (psalzman@localhost) by gamefish.pcola.gulf.net (8.9.1/8.9.1) with ESMTP id UAA09908; Mon, 9 Nov 1998 20:46:56 GMT (envelope-from psalzman@gamefish.pcola.gulf.net) Date: Mon, 9 Nov 1998 20:46:56 +0000 (GMT) From: Phillip Salzman To: Steve Kargl cc: hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <199811091712.JAA10172@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Like Microsoft Internet Explorer stating it is Mozilla? No. This is not something that would be good. Even as it would make it easier for installation scripts like that - we are not Linux. Its hard enough to explain that to people... I don't think it should be there... -- Phillip Salzman "BSDFF! YOU BLASD!" On Mon, 9 Nov 1998, Steve Kargl wrote: > Ladies and Gents, > > I've recently installed the Portland Groups's Fortran 90 > for Linux on my system (it works!). However, during the > installation from the cdrom, a install script is executed > that contains a test involving "uname -s" to ensure the > installation is on a system running Linux. Of course, > "uname -s" on a FreeBSD system returns "FreeBSD" instead > of the expected "Linux". Thus, I had to alter uname(1) > to report "Linux" to install the software. With the > expected availability of more commericial software for Linux, > it seems necessary to provide uname(1) the capability to > report "Linux" in place of "FreeBSD". > > -- > Steve > > finger kargl@troutmask.apl.washington.edu > http://troutmask.apl.washington.edu/~clesceri/kargl.html > > > *** uname.c.orig Mon Nov 9 08:46:41 1998 > --- uname.c Mon Nov 9 08:49:54 1998 > *************** > *** 105,116 **** > prefix = ""; > > if (flags & SFLAG) { > ! mib[0] = CTL_KERN; > ! mib[1] = KERN_OSTYPE; > ! len = sizeof(buf); > ! if (sysctl(mib, 2, &buf, &len, NULL, 0) == -1) > ! err(1, "sysctl"); > ! (void)printf("%s%.*s", prefix, (int)len, buf); > prefix = " "; > } > if (flags & NFLAG) { > --- 105,119 ---- > prefix = ""; > > if (flags & SFLAG) { > ! if (!getenv("LINUX_UNAME")) { > ! mib[0] = CTL_KERN; > ! mib[1] = KERN_OSTYPE; > ! len = sizeof(buf); > ! if (sysctl(mib, 2, &buf, &len, NULL, 0) == -1) > ! err(1, "sysctl"); > ! (void)printf("%s%.*s", prefix, (int)len, buf); > ! } else > ! (void)printf("%sLinux", prefix); > prefix = " "; > } > if (flags & NFLAG) { > *** uname.1.orig Mon Nov 9 09:06:23 1998 > --- uname.1 Mon Nov 9 09:08:56 1998 > *************** > *** 72,77 **** > --- 72,82 ---- > to standard output. > .It Fl s > Write the name of the operating system implementation to standard output. > + If the environmental variable > + .Em LINUX_UNAME > + is set, then write > + .Em Linux > + to standard output. > .It Fl v > Write the version level of this release of the operating system > to standard output. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 13:00:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21146 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 13:00:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gate.lustig.com (gate.lustig.com [205.246.2.242]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA21139 for ; Mon, 9 Nov 1998 13:00:50 -0800 (PST) (envelope-from barry@lustig.com) Received: (qmail 23390 invoked from network); 9 Nov 1998 21:00:23 -0000 Received: from devious.lustig.com (205.246.2.244) by gate.lustig.com with SMTP; 9 Nov 1998 21:00:23 -0000 Received: (qmail 10334 invoked by uid 21); 9 Nov 1998 21:00:53 -0000 Message-ID: <19981109210052.10333.qmail@devious.lustig.com> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) X-Nextstep-Mailer: Mail 4.2mach (Enhance 2.2p1) Received: by NeXT.Mailer (1.148.RR) From: Barry Lustig Date: Mon, 9 Nov 1998 16:00:52 -0500 To: freebsd-hackers@FreeBSD.ORG Subject: UID Changing Tool for Filesystem Reply-To: barry@lustig.com X-Organizations: Barry Lustig & Associates, Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Back in the days of 4.2BSD, Chris Torek wrote a utility that would take a raw device and a map of old/new uids and old/new gids. The tool would then change the uids and gids by walking through the inodes. Does such a creature still exist anywhere? barry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 13:05:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21851 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 13:05:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21828 for ; Mon, 9 Nov 1998 13:04:52 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id UAA28957; Mon, 9 Nov 1998 20:59:20 GMT (envelope-from nik) Message-ID: <19981109205920.58410@nothing-going-on.org> Date: Mon, 9 Nov 1998 20:59:20 +0000 From: Nik Clayton To: Kazutaka YOKOTA , Nik Clayton Cc: hackers@FreeBSD.ORG Subject: Re: text mode screen grabber? References: <19981107152928.28834@nothing-going-on.org> <199811081510.AAA16053@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199811081510.AAA16053@zodiac.mech.utsunomiya-u.ac.jp>; from Kazutaka YOKOTA on Mon, Nov 09, 1998 at 12:10:42AM +0900 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 09, 1998 at 12:10:42AM +0900, Kazutaka YOKOTA wrote: > >Has anyone got (or have pointers to useful code) a screen grabber for > >syscons? Ideally (and given an 80x25 screen) I'm looking for something > >that would write a 4000 byte file of { character code, colour } tuples. > [...] > > Have you considered script(1), a standard command, or `screen', which > is in the port collection, I expect? Yes. They don't seem to capture colours. In a simple format (simple == 2 bytes per character, 1 byte = character code, 1 byte = colour code). [ ioctl() snipped ] > >I've had a look at the syscons code, and some of the screen savers, but > >nothing's leaping out at me saying "Here, this is where the screen > >buffer is. . .". > > No, I don't think you should directly read the internal data structure. > Its format may be different between versions. True enough. I hasten to point out that I'm not trying to write something for wide distribution (at the moment). This is just something to make the FreeBSD Documentation a little more user friendly. After poking a bit more through syscons.c, I think I should be able to implement something like "press 'D' to dump the current screen to /tmp/syscons.dump" or similar. Cheers, N -- C.R.F. Consulting -- we're run to make me richer. . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 13:17:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23650 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 13:17:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zappa.demon.nl (zappa.demon.nl [195.173.232.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23643 for ; Mon, 9 Nov 1998 13:17:31 -0800 (PST) (envelope-from root@zappa.demon.nl) Received: (from root@localhost) by zappa.demon.nl (8.9.1/8.8.8) id VAA04721 for freebsd-hackers@freebsd.org; Mon, 9 Nov 1998 21:18:37 +0100 (CET) (envelope-from root) Message-ID: <19981109211837.A4702@zappa.demon.nl> Date: Mon, 9 Nov 1998 21:18:37 +0100 From: Ron Klinkien To: freebsd-hackers@FreeBSD.ORG Subject: i2c projects Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone have any pointers/src code on how to use the i2c drivers with FreeBSD? I want to build a weather station / home automation project using a FreeBSD running pc, and the i2c bus on my video capture card. The i2c driver src and man pages don't give me enough info.. Furthermore I have compiled a kernel with i2c support but there are no ii* devices in /dev, and not in MAKEDEV too. Which major/minor numbers to use etc...? Regards, Ron. ---- Running Solaris/SPARC at work, enjoying FreeBSD/PII at home. Ron Klinkien System Engineer ron@zappa.demon.nl http://www.zappa.demon.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 13:32:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25209 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 13:32:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA25201 for ; Mon, 9 Nov 1998 13:32:30 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 9349 invoked by uid 1001); 9 Nov 1998 21:32:07 +0000 (GMT) To: barry@lustig.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: UID Changing Tool for Filesystem In-Reply-To: Your message of "Mon, 9 Nov 1998 16:00:52 -0500" References: <19981109210052.10333.qmail@devious.lustig.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 09 Nov 1998 22:32:07 +0100 Message-ID: <9347.910647127@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Back in the days of 4.2BSD, Chris Torek wrote a utility that would take a > raw device and a map of old/new uids and old/new gids. The tool would then > change the uids and gids by walking through the inodes. Does such a creature > still exist anywhere? For instance ftp://ftp.ntnu.no/pub/unix/security/firewalls/mjr-iwi/unify_uids.tar.gz (I know, it has nothing to do with firewalls - but that's where I picked it up from :-) Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 13:53:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26946 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 13:53:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26940 for ; Mon, 9 Nov 1998 13:53:27 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id WAA08677; Mon, 9 Nov 1998 22:53:11 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id WAA16873; Mon, 9 Nov 1998 22:53:11 +0100 (MET) Message-ID: <19981109225310.34189@follo.net> Date: Mon, 9 Nov 1998 22:53:10 +0100 From: Eivind Eklund To: Steve Kargl Cc: hackers@FreeBSD.ORG Subject: Re: linux software installation and uname References: <199811091947.LAA11148@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199811091947.LAA11148@troutmask.apl.washington.edu>; from Steve Kargl on Mon, Nov 09, 1998 at 11:47:56AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 09, 1998 at 11:47:56AM -0800, Steve Kargl wrote: > Here is the nice little uname test from the vendor's install script: > > # what type of target? > if test -x /usr/bin/uname ; then > uname=/usr/bin/uname > elif test -x /bin/uname ; then > uname=/bin/uname > else > # Never seen it anywhere but /bin or /usr/bin, so hopefully it's > # in $PATH already. > type uname > /dev/null 2>&1 > if test $? -ne 0 ; then > echo "install: uname not found in \$PATH environment variable" > quit > else > uname=uname > fi > fi > > You'll never pick up /compat/linux/bin/uname unless you delete/rename > /usr/bin/uname. Eh - I'm pretty sure /compat/linux is searched _before_ /. For all syscalls. This is hardcoded in the linux emulator in the kernel. So if /compat/linux/bin/uname exists, that will be run in preference to /bin/uname for anything Linux-emulated. We might still need a way of saying that a shell script is Linux-emulated, though - probably by running it through /compat/linux/bin/sh :-) Besides this, vendors should be pressured to test for uname in the right way to make their Linux software also work on FreeBSD. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 14:25:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29996 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 14:25:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29988 for ; Mon, 9 Nov 1998 14:25:05 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id RAA02703; Mon, 9 Nov 1998 17:24:34 -0500 (EST) (envelope-from lee) Message-ID: <19981109172434.A2380@tidalwave.net> Date: Mon, 9 Nov 1998 17:24:34 -0500 From: Lee Cremeans To: Mike Smith , hackers@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Re: Encryption coprocessor, part 2. Reply-To: lcremean@tidalwave.net References: <19981109151423.A2157@tidalwave.net> <199811092033.MAA00693@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811092033.MAA00693@dingo.cdrom.com>; from Mike Smith on Mon, Nov 09, 1998 at 12:33:57PM -0800 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 09, 1998 at 12:33:57PM -0800, Mike Smith wrote: > It sounds from your previous messages as though the control buffers are > actually associated with the data buffers, so you might want to unify > them. They can be, but the DMA channels on this chip only move 64k at a time (I'd run into trouble if I had a full IP packet and the command header together), and besides, it has a channel dedicated to writing the command buffers into the chip. So the way I see it, I'd have 4 synch'd queues, a list saying which slots are in use/dirty/free, and a way to check which buffer goes with which session (I'm thinking of keeping a list of sessions). Keeping buffers and DMA descriptors together would be interesting, tho, but I think I can figure something out. I'm thinking something like this when I build the lists: /* This is the struct for a DMA descriptor. We stick the pointer for the associated buffer directly into mybuf->buf. */ struct mybuf { unsigned short flags; #define DESC_FLAGS_VALID 0x8000 /* this descriptor is ready for use */ #define DESC_FLAGS_JUMP 0x4000 /* descriptor points to another desc */ #define DESC_FLAGS_LAST 0x2000 /* last desc in the list/ring */ #define DESC_FLAGS_MASKDONE 0x0200 /* don't interupt when this desc finishes */ unsigned short length; /* 16 bits -- 64k */ caddr_t addr; /* physical addr of buf or next desc */ } Note that this is the actual structure of a 7751 DMA descriptor (though I think I may have the byte order/alignment off). What I'd do, then, is make an array struct mybuf[NUM_SLOTS] cmd_ring and feed that address to the chip, assuming this is done in wired memory. (contigmalloc and vtophys (finally) are my friends here, I'd think). Then I'd go thorugh and allocate buffers for each slot in the list. I feel funny about allocating all that wired-down memory, though.. Does this sound right? -- Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | mailto:lcremean@tidalwave.net http://st-lcremean.tidalwave.net | Powered by FreeBSD 3.0-CURRENT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 14:39:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01442 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 14:39:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01433 for ; Mon, 9 Nov 1998 14:39:32 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan@dan.emsphone.com [199.67.51.101]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id OAA06342 for ; Mon, 9 Nov 1998 14:39:34 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id QAA20818; Mon, 9 Nov 1998 16:38:54 -0600 (CST) Date: Mon, 9 Nov 1998 16:38:53 -0600 From: Dan Nelson To: Mike Smith Cc: Thomas David Rivers , freebsd-hackers@freefall.cdrom.com Subject: Re: A stdio question... does fpos_t really need to be 'long long'? Message-ID: <19981109163853.A20712@emsphone.com> References: <19981109110955.A5248@emsphone.com> <199811092006.MAA00487@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.3i In-Reply-To: <199811092006.MAA00487@dingo.cdrom.com>; from "Mike Smith" on Mon Nov 9 12:06:12 GMT 1998 X-OS: FreeBSD 2.2.7-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Nov 09), Mike Smith said: > Dan said: > > I noticed this back in April and commented on it. I believe the > > consensus was that fsetpos()/fgetpos()/fseek()/ftell() should be > > wrappers for the X/Open functions fseeko() and ftello(), which take > > off_t arguments. > > > > Unfortunately, I never submitted patches, and neither did anyone else. > > > > -Dan Nelson > > dnelson@emsphone.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > So submit them, dammit! 8) grumble grumble.. :) Ok. Could someone go over PR bin/8637 and tell me if it looks okay? I've rebuilt libc on my machine and it seems to work; I can seek to the end of a 5gb datafile and get my position correctly. The only bad thing in my patch is the error you get if you ftell() on a FILE* that is positioned past 2 gig. errno.h doesn't have an EOVERFLOW, which is what X/Open says ftell should return. I put EFBIG in instead. Whoops. Something I realize I forgot already is manpage tweaks to document fseeko and ftello. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 15:12:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04778 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 15:12:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04772 for ; Mon, 9 Nov 1998 15:12:25 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id PAA11509; Mon, 9 Nov 1998 15:16:12 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811092316.PAA11509@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname In-Reply-To: <199811092004.NAA06080@mt.sri.com> from Nate Williams at "Nov 9, 1998 1: 4: 7 pm" To: nate@mt.sri.com (Nate Williams) Date: Mon, 9 Nov 1998 15:16:12 -0800 (PST) Cc: nate@mt.sri.com, jkh@time.cdrom.com, crossd@cs.rpi.edu, hackers@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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Nate Williams: > > > > I think the correct thing to do here is simply give uname(1) some > > > > truly switchable behavior, as Steve's second patch did. > > > > > > The user then has to be aware of the 'LINUX_EMULATION' environment > > > variable, which is non-intuitive. The /compat/linux script is a much > > > better solution since it doesn't require any magic environment > > > knowledge that must be modified if you run binaries from multiple > > > 'emulated' OS's. > > > > > > > You're assuming the vendor supplied script will pick up the script > > in /compat/linux. That, is not the case for the Portland Group > > script: > > You didn't answer the question. What if I have multiple binaries from > different OS's on the system. The user has to be aware of the 'magic' > environment variable and have it switch between them. Once we're on > that path, we're no better off than we are now. > I'm suggesting a change to uname(1) not uname(3). Binaries are unaffected by setting an ALT_UNAME environmental variable. Shell scripts are a different beast, and so you would have to protect binaries called from within a shell: #! /bin/sh setenv ALT_UNAME Linux a_linux_binary unsetenv ALT_UNAME .... setenv ALT_UNAME FooOS a_FooOS binary unsetenv ALT_UNAME Although I doubt that there are many (if any) shell scripts that mix binaries from different OS emulations, I suppose its a possibility. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 15:17:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05292 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 15:17:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05283 for ; Mon, 9 Nov 1998 15:17:49 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id QAA08850; Mon, 9 Nov 1998 16:17:29 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id QAA08648; Mon, 9 Nov 1998 16:17:28 -0700 Date: Mon, 9 Nov 1998 16:17:28 -0700 Message-Id: <199811092317.QAA08648@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Steve Kargl Cc: nate@mt.sri.com (Nate Williams), jkh@time.cdrom.com, crossd@cs.rpi.edu, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <199811092316.PAA11509@troutmask.apl.washington.edu> References: <199811092004.NAA06080@mt.sri.com> <199811092316.PAA11509@troutmask.apl.washington.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > According to Nate Williams: > > > > > I think the correct thing to do here is simply give uname(1) some > > > > > truly switchable behavior, as Steve's second patch did. > > > > > > > > The user then has to be aware of the 'LINUX_EMULATION' environment > > > > variable, which is non-intuitive. The /compat/linux script is a much > > > > better solution since it doesn't require any magic environment > > > > knowledge that must be modified if you run binaries from multiple > > > > 'emulated' OS's. > > > > > > > > > > You're assuming the vendor supplied script will pick up the script > > > in /compat/linux. That, is not the case for the Portland Group > > > script: > > > > You didn't answer the question. What if I have multiple binaries from > > different OS's on the system. The user has to be aware of the 'magic' > > environment variable and have it switch between them. Once we're on > > that path, we're no better off than we are now. > > > > I'm suggesting a change to uname(1) not uname(3). Binaries are > unaffected by setting an ALT_UNAME environmental variable. No, but in order to get the 'correct' behavior, I have to know which OS I need emulated so I can set the environment variable correctly. So, if I want to run SCO's Informix which uses uname (it does, BTW), I have to set 'ALT_UNAME' to "SCO". Then, I want to run StarOffice, so I have set 'ALT_UNAME' to "Linux", then I want to run the JDK, so I have to set 'ALT_UNAME' to "Solaris", or was it the Linux version that I was running? I don't remember if it was the Solaris version, or the Linux version? The point is that it's *NOT* transparent to the users, so the solution isn't any better than the initial problem, but it adds more bloat and more 'magic' solutions that are no better than editing shells scripts. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 16:02:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10085 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 16:02:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10080 for ; Mon, 9 Nov 1998 16:02:52 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id QAA11726; Mon, 9 Nov 1998 16:06:32 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811100006.QAA11726@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname In-Reply-To: <199811092317.QAA08648@mt.sri.com> from Nate Williams at "Nov 9, 1998 4:17:28 pm" To: nate@mt.sri.com (Nate Williams) Date: Mon, 9 Nov 1998 16:06:32 -0800 (PST) Cc: nate@mt.sri.com, jkh@time.cdrom.com, crossd@cs.rpi.edu, hackers@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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Nate Williams: > > > > I'm suggesting a change to uname(1) not uname(3). Binaries are > > unaffected by setting an ALT_UNAME environmental variable. > > No, but in order to get the 'correct' behavior, I have to know which OS > I need emulated so I can set the environment variable correctly. > > So, if I want to run SCO's Informix which uses uname (it does, BTW), I > have to set 'ALT_UNAME' to "SCO". Then, I want to run StarOffice, so I > have set 'ALT_UNAME' to "Linux", then I want to run the JDK, so I have > to set 'ALT_UNAME' to "Solaris", or was it the Linux version that I was > running? I don't remember if it was the Solaris version, or the Linux > version? I must be confused by your objection. Do Informix, StarOffice, and JDK use popen() to call uname(1) instead of uname(3)? I assume uname(3) will be resolved from the /compat/linux/usr/lib/libc.so.5 library. > > The point is that it's *NOT* transparent to the users, so the solution > isn't any better than the initial problem, but it adds more bloat and > more 'magic' solutions that are no better than editing shells scripts. It's fairly difficult to edit a shell script on a CDROM. Note, it is not a simple matter to copy the shell script to a temporary directory and change linux to FreeBSD. Some vendors expect the script to be executed from a particular directory in their CDROM hierarchy. I can change uname(1) with 4 lines, or I can fix UNIONFS. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 16:08:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12321 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 16:08:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12311 for ; Mon, 9 Nov 1998 16:07:55 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (root@woof.lan.Awfulhak.org [172.16.0.7]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id AAA22986; Tue, 10 Nov 1998 00:06:16 GMT (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1]) by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id AAA02529; Tue, 10 Nov 1998 00:07:39 GMT (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199811100007.AAA02529@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Marc Slemko cc: Brian Somers , freebsd-hackers@FreeBSD.ORG Subject: Re: bind()/listen() race In-reply-to: Your message of "Sun, 08 Nov 1998 17:10:10 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Nov 1998 00:07:38 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 8 Nov 1998, Brian Somers wrote: > > > The code says something like: > > > > if (bind(blah) < 0) { > > /* we're happy to be the client */ > > if (connect(blah) < 0) { > > socket is bound without a listen ! > > } > > } else if (listen(blah) < 0) { > > oops ! > > } > > > > The sockaddrs are local domain sockets used by ppp in multilink mode. > > Whoever gets to be the server will survive. The other ppp will > > become the client, pass a file descriptor to the server and hang > > around holding the session 'till the other ppp kills it. > > > > However, if the two ppps get unlucky, one bind()s and the second > > fails then tries to connect() and fails 'cos the server hasn't > > listen()ed yet. This is bad news. > > > > The only way I can see around it - given that I can't sleep() in ppp > > without screwing up with other timing issues - is to detect the error > > and do a 1 second timeout, and try again then. This is a nasty thing > > to have to do.... I'd prefer an atomic bind()/listen() facility.... > > No, an atomic bind/listen isn't the solution, you simply need some form of > synchronization between the processes. > > For example, you could use a lockfile and require a write lock arouncd the > bind and listen. > > Unfortunately, inter process synchronization is more of a pain than intra > process synchronization. > > If you used a lock file on disk with the server pid, you could also avoid > mistakenly thinking that something else listening on the port is the > server. This is out of the question. Ppp is only allowed block in select(). That's why it's so difficult to ``sleep''. I have to set up a timeout function that'll kick ppp into continuing where it left off, then go back and select(). Also, at this point in the communication process, there's no time to muck around. If I can't bind() and can't connect() pretty quickly, the peer's going to give up on us. At this (rather critical) point, we've told the peer that we'll do multilink and we've found that another ppp is already talking to the remote machine in multilink mode (or has crashed badly). > You suggestion is possible as a workaround, and is probably the easiest > fix. It maybe the only practical one too. Backing off for a second and trying again will give us a situation where we can fail due to a previously crashed ppp (or maybe even resurrect the socket), or we get a connection.... We'd be extremely unlikely to have had a whole second between a bind() and listen() :-) If another ppp actually came up and went down again in that second, then we're probably going to do the same thing - due to authentication or IPCP negotiation failure (misconfiguration). I appreciate that some sort of elaborate read-lock-promoted -to-write-lock on the server side would allow the client to say ``if there's a write lock, connect(), otherwise if there's no read lock the server's dead - but this may be overkill.... The simpler the better. -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 16:26:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14172 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 16:26:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14156 for ; Mon, 9 Nov 1998 16:26:19 -0800 (PST) (envelope-from dan@math.berkeley.edu) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id QAA04722; Mon, 9 Nov 1998 16:25:35 -0800 (PST) Date: Mon, 9 Nov 1998 16:25:35 -0800 (PST) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199811100025.QAA04722@math.berkeley.edu> To: nate@mt.sri.com Subject: Re: linux software installation and uname Cc: dan@math.berkeley.edu, freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No, but in order to get the 'correct' behavior, I have to know which OS > I need emulated so I can set the environment variable correctly. > > So, if I want to run SCO's Informix which uses uname (it does, BTW), I > have to set 'ALT_UNAME' to "SCO". Then, I want to run StarOffice, so I > have set 'ALT_UNAME' to "Linux", then I want to run the JDK, so I have > to set 'ALT_UNAME' to "Solaris", or was it the Linux version that I was > running? I don't remember if it was the Solaris version, or the Linux > version? > > The point is that it's *NOT* transparent to the users, so the solution > isn't any better than the initial problem, but it adds more bloat and > more 'magic' solutions that are no better than editing shells scripts. So you wrap a small shell script around certain commands that require special things in their environment. This has been an occasional necessity for years. For example, my netscape wrapper contains: ... setenv CLASSPATH "$N"/java* setenv XKEYSYMDB "$N"/XKeysymDB setenv XNLSPATH "$N"/nls setenv MOZILLA_HOME "$N" setenv MAILCAP /usr/local/misc/lib/netscape/mailcap setenv MIME_TYPES /usr/local/misc/lib/netscape/mime_types setenv NPX_PLUGIN_PATH /usr/local/misc/lib/netscape/plugins ... exec /usr/bin/nice -4 "$N/$X" $* and I have generic wrappers for several different versions of X11, each of which likes a different executable search path, manual path, library path, and I forget what else. Life is complicated. We have to live with it. (Though sometimes I consider going back in time and strangling the people who would eventually invent and implement X before they could grow up and commit such an artistic barbarism. This approach might actually be more likely to succeed.) Dan Strick dan@math.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 16:51:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16517 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 16:51:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16488 for ; Mon, 9 Nov 1998 16:51:47 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.9.1/8.9.1) id BAA08580; Tue, 10 Nov 1998 01:47:08 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199811100047.BAA08580@ocean.campus.luth.se> Subject: Re: bind()/listen() race In-Reply-To: <199811100007.AAA02529@woof.lan.awfulhak.org> from Brian Somers at "Nov 10, 98 00:07:38 am" To: brian@Awfulhak.org (Brian Somers) Date: Tue, 10 Nov 1998 01:47:08 +0100 (CET) Cc: marcs@znep.com, brian@Awfulhak.org, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Brian Somers: > > You suggestion is possible as a workaround, and is probably the easiest > > fix. > > It maybe the only practical one too. Backing off for a second and > trying again will give us a situation where we can fail due to a > previously crashed ppp (or maybe even resurrect the socket), or we > get a connection.... We'd be extremely unlikely to have had a whole > second between a bind() and listen() :-) If another ppp actually > came up and went down again in that second, then we're probably going > to do the same thing - due to authentication or IPCP negotiation > failure (misconfiguration). > > I appreciate that some sort of elaborate read-lock-promoted > -to-write-lock on the server side would allow the client to say ``if > there's a write lock, connect(), otherwise if there's no read lock > the server's dead - but this may be overkill.... The simpler the > better. Well... if you use a softlink (/var/run/mpppd.lock, or something?) which points to the PID for the holder... How about something like this? int tmp, i_am_server = 0; while ((tmp = create_softlink_to_pid()) == failure) { if (kill_pid_with_signal_0() == success) break; remove_softlink(); /* lock was old */ } if (tmp == failure) { /* we're not master */ tmp = 0; while (connect() == failed && ++tmp < 10) { sched_yield(); /* maybe add a "select(0,0,0,timeout);" with a small timeout too */ } if (tmp == 10) panic(); } else { /* we are master */ if (bind() = failed) panic(); else listen(); i_am_server = 1; } Wouldn't that maybe work? Anyway, just brainstorming... Goodnight. /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 18:38:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28445 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 18:38:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28436 for ; Mon, 9 Nov 1998 18:38:03 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from spectrum.physics.adelaide.edu.au (spectrum [129.127.36.1]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id NAA18808; Tue, 10 Nov 1998 13:07:44 +1030 (CST) Received: from localhost by spectrum.physics.adelaide.edu.au; (5.65/1.1.8.2/26Jun95-0330PM) id AA09831; Tue, 10 Nov 1998 13:07:42 +1030 Date: Tue, 10 Nov 1998 13:07:40 +1030 (CST) From: Kris Kennaway To: Nate Williams Cc: Steve Kargl , Dan Nelson , rivers@dignus.com, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <199811092016.NAA06221@mt.sri.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Nov 1998, Nate Williams wrote: > Ahh, but what happens when I have to run the same applications in the > same shell? Do I have to modify my environment everytime I run a > different application? Do I have to remember which 'emulated OS' the > application runs? That's where the proposed "commercial ports" category would come in. Someone could provide wrappers for installation, executing, etc, which handle all the messy work of setting environment variables and so forth to get the thing to run, for things which require a 'tweaked' emulation environment. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 19:02:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01229 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 19:02:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01222 for ; Mon, 9 Nov 1998 19:02:04 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id TAA08917; Mon, 9 Nov 1998 19:01:38 -0800 (PST) (envelope-from dillon) Date: Mon, 9 Nov 1998 19:01:38 -0800 (PST) From: Matthew Dillon Message-Id: <199811100301.TAA08917@apollo.backplane.com> To: Kris Kennaway Cc: Nate Williams , Steve Kargl , Dan Nelson , rivers@dignus.com, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Shell scripts in ~/bin are your friend. So, for example, when I downloaded the linux version of the realaudio player 5 and wanted to run it on my FreeBSD box, I wound up writing a little shell script to setup the proper environment, LD_LIBARRY_PATH or something like that, and then run the real linux binary. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) :On Mon, 9 Nov 1998, Nate Williams wrote: : :> Ahh, but what happens when I have to run the same applications in the :> same shell? Do I have to modify my environment everytime I run a :> different application? Do I have to remember which 'emulated OS' the :> application runs? : :That's where the proposed "commercial ports" category would come in. Someone :could provide wrappers for installation, executing, etc, which handle all the :messy work of setting environment variables and so forth to get the thing to :run, for things which require a 'tweaked' emulation environment. : :Kris : : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 19:36:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03430 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 19:36:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03424 for ; Mon, 9 Nov 1998 19:36:35 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id TAA15279 for ; Mon, 9 Nov 1998 19:28:20 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdJ15276; Tue Nov 10 03:28:16 1998 Message-ID: <3647B2AF.794BDF32@whistle.com> Date: Mon, 09 Nov 1998 19:27:43 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: libscrypt and automatic builds. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I want to have libscrypt and libdescrypt in my distribution, and have libcrypt -> libscrypt. There doesn't seen to be an easy way to get a 'make buildworld;make installworld; to be able to give that combination. It seems that if libdescrypt is available it gets pointed to. am I doing something stupid here? julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 20:31:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07797 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 20:31:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07786 for ; Mon, 9 Nov 1998 20:31:45 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id VAA11124; Mon, 9 Nov 1998 21:31:29 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id VAA09963; Mon, 9 Nov 1998 21:31:28 -0700 Date: Mon, 9 Nov 1998 21:31:28 -0700 Message-Id: <199811100431.VAA09963@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: dan@math.berkeley.edu (Dan Strick) Cc: nate@mt.sri.com, freebsd-hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <199811100025.QAA04722@math.berkeley.edu> References: <199811100025.QAA04722@math.berkeley.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > No, but in order to get the 'correct' behavior, I have to know which OS > > I need emulated so I can set the environment variable correctly. > > > > So, if I want to run SCO's Informix which uses uname (it does, BTW), I > > have to set 'ALT_UNAME' to "SCO". Then, I want to run StarOffice, so I > > have set 'ALT_UNAME' to "Linux", then I want to run the JDK, so I have > > to set 'ALT_UNAME' to "Solaris", or was it the Linux version that I was > > running? I don't remember if it was the Solaris version, or the Linux > > version? > > > > The point is that it's *NOT* transparent to the users, so the solution > > isn't any better than the initial problem, but it adds more bloat and > > more 'magic' solutions that are no better than editing shells scripts. > > So you wrap a small shell script around certain commands that require > special things in their environment. This is what I proposed, not hacking up the FreeBSD sources to have OS specific commands in them. Modifying uname when in fact the installation requires fixing is the better solution. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 20:33:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08082 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 20:33:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08077 for ; Mon, 9 Nov 1998 20:33:31 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id VAA11154; Mon, 9 Nov 1998 21:32:42 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id VAA09970; Mon, 9 Nov 1998 21:32:40 -0700 Date: Mon, 9 Nov 1998 21:32:40 -0700 Message-Id: <199811100432.VAA09970@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Kris Kennaway Cc: Nate Williams , Steve Kargl , Dan Nelson , rivers@dignus.com, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: References: <199811092016.NAA06221@mt.sri.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Ahh, but what happens when I have to run the same applications in the > > same shell? Do I have to modify my environment everytime I run a > > different application? Do I have to remember which 'emulated OS' the > > application runs? > > That's where the proposed "commercial ports" category would come in. Someone > could provide wrappers for installation, executing, etc, which handle all the > messy work of setting environment variables and so forth to get the thing to > run, for things which require a 'tweaked' emulation environment. Is there an echo in the room? Isn't this what I initially proposed as a better alternative to hacking up the uname(1) sources? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 20:35:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08250 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 20:35:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08245 for ; Mon, 9 Nov 1998 20:35:47 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from mercury (mercury [129.127.36.44]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id PAA19131; Tue, 10 Nov 1998 15:05:29 +1030 (CST) Received: from localhost by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA06569; Tue, 10 Nov 1998 15:05:29 +1030 Date: Tue, 10 Nov 1998 15:05:28 +1030 (CST) From: Kris Kennaway To: Nate Williams Cc: Steve Kargl , Dan Nelson , rivers@dignus.com, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <199811100432.VAA09970@mt.sri.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Nov 1998, Nate Williams wrote: > > > Ahh, but what happens when I have to run the same applications in the > > > same shell? Do I have to modify my environment everytime I run a > > > different application? Do I have to remember which 'emulated OS' the > > > application runs? > > > > That's where the proposed "commercial ports" category would come in. Someone > > could provide wrappers for installation, executing, etc, which handle all the > > messy work of setting environment variables and so forth to get the thing to > > run, for things which require a 'tweaked' emulation environment. > > Is there an echo in the room? Isn't this what I initially proposed as a > better alternative to hacking up the uname(1) sources? Oops :) Well, uh.."I agree" :) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 20:57:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09845 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 20:57:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09835 for ; Mon, 9 Nov 1998 20:57:01 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id XAA17449; Mon, 9 Nov 1998 23:54:46 -0500 (EST) Date: Mon, 9 Nov 1998 23:54:46 -0500 (EST) From: Chuck Robey To: Nate Williams cc: Kris Kennaway , Steve Kargl , Dan Nelson , rivers@dignus.com, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <199811100432.VAA09970@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Nov 1998, Nate Williams wrote: > > > Ahh, but what happens when I have to run the same applications in the > > > same shell? Do I have to modify my environment everytime I run a > > > different application? Do I have to remember which 'emulated OS' the > > > application runs? > > > > That's where the proposed "commercial ports" category would come in. Someone > > could provide wrappers for installation, executing, etc, which handle all the > > messy work of setting environment variables and so forth to get the thing to > > run, for things which require a 'tweaked' emulation environment. > > Is there an echo in the room? Isn't this what I initially proposed as a > better alternative to hacking up the uname(1) sources? Nate, it *seems* that what I'm hearing from him is that he wants to hack uname so that it would respond to the environmental variables that you want him to write wrappers for. I think you're right, you want wrappers, but the uname thing is something that most commercial wrappers rely on. He just wants uname to listen to some environmental variables. If there's some other way to do it, I haven't seen it yet ... am I wrong? > > > > Nate > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 22:03:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15433 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 22:03:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cs.tamu.edu (clavin.cs.tamu.edu [128.194.130.106]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15428 for ; Mon, 9 Nov 1998 22:03:53 -0800 (PST) (envelope-from gurudatt@cs.tamu.edu) Received: from dilbert.cs.tamu.edu (IDENT:2146@dilbert [128.194.133.100]) by cs.tamu.edu (8.9.1/8.9.1) with ESMTP id AAA22488 for ; Tue, 10 Nov 1998 00:02:55 -0600 (CST) Received: from localhost by dilbert.cs.tamu.edu (8.9.1/8.9.1) with SMTP id AAA03469 for ; Tue, 10 Nov 1998 00:02:43 -0600 (CST) X-Authentication-Warning: dilbert.cs.tamu.edu: gurudatt owned process doing -bs Date: Tue, 10 Nov 1998 00:02:43 -0600 (CST) From: Gurudatt Shenoy X-Sender: gurudatt@dilbert To: FreeBSD Hackers Subject: FreeBSD clock Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was wondering where I could find detailed info on how the clocks in FreeBSD 2.1.5 (the ones referred to as "main" and "kernel" clocks) work i.e. stuff like the resolution, how they decide to increment the tick count etc. Any help would be highly appreciated. Thanks, Guru (guru@cs.tamu.edu) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 22:30:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA16985 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 22:30:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA16980 for ; Mon, 9 Nov 1998 22:30:54 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id WAA12678; Mon, 9 Nov 1998 22:34:38 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811100634.WAA12678@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname In-Reply-To: <199811100432.VAA09970@mt.sri.com> from Nate Williams at "Nov 9, 1998 9:32:40 pm" To: nate@mt.sri.com (Nate Williams) Date: Mon, 9 Nov 1998 22:34:38 -0800 (PST) Cc: kkennawa@physics.adelaide.edu.au, nate@mt.sri.com, dnelson@emsphone.com, rivers@dignus.com, hackers@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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Nate Williams: > > > Ahh, but what happens when I have to run the same applications in the > > > same shell? Do I have to modify my environment everytime I run a > > > different application? Do I have to remember which 'emulated OS' the > > > application runs? > > > > That's where the proposed "commercial ports" category would come in. Someone > > could provide wrappers for installation, executing, etc, which handle all the > > messy work of setting environment variables and so forth to get the thing to > > run, for things which require a 'tweaked' emulation environment. > > Is there an echo in the room? Isn't this what I initially proposed as a > better alternative to hacking up the uname(1) sources? > There's no echo, just a bunch of deaf hackers. I happen to disagree with the viewpoint that writing custom scripts for each commerical vendor is a better solution. There may be only a handful of scripts to write this month, but next month we will have more custom scripts. If linux continues to gain in popularity among commerical vendors, then we'll have to maintain a large collection of scripts. There is a point of "diminishing returns" with respect to maintain a large collection of scripts, particularly when a 4 line change to uname(1) will accommodate the majority of the vendor supplied scripts. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 22:39:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17865 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 22:39:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles162.castles.com [208.214.165.162]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17859 for ; Mon, 9 Nov 1998 22:38:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA00637 for ; Mon, 9 Nov 1998 22:38:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811100638.WAA00637@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: [Vinum] Stupid benchmark: newfsstone Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Nov 1998 22:38:04 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just started playing with Vinum. Gawd Greg, this thing seriously needs a "smart" frontend to do the "simple" things. 4 x 4GB disks (2x Atlas, 2x Grand Prix) on an ncr 53c875, slapped together as a single volume. (you want to mention building filesystems in your manpages somewhere too - the '-v' option is not immediately obvious). 6:36 elapsed to newfs the 16GB volume in concatenated mode. 4:36 to newfs it in striped mode (64b stripes). There was an interesting symptom observed in striped mode, where the disks seemed to have a binarily-weighted access pattern. It will get more interesting when I add two more 9GB drives and four more 4GB units to the volume; especially as I haven't worked out if I can stripe the 9GB units separately and then concatenate their plex with the plex containing the 4GB units; my understanding is that all plexes in a volume contain copies of the same data. Can you nest plexes? Anyway, apart from one incident where I managed to get a pile of debugger calls out of Vinum (freeing already free memory - it occurred after many failed config attempts and I haven't been able to reproduce it) it hasn't let me down yet. Tomorrow I build the world on it. Thanks to Greg and the folks at Cybernet! -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 9 22:40:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18001 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 22:40:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17990 for ; Mon, 9 Nov 1998 22:40:31 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from spectrum.physics.adelaide.edu.au (spectrum [129.127.36.1]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id RAA20401; Tue, 10 Nov 1998 17:10:10 +1030 (CST) Received: from localhost by spectrum.physics.adelaide.edu.au; (5.65/1.1.8.2/26Jun95-0330PM) id AA10308; Tue, 10 Nov 1998 17:10:10 +1030 Date: Tue, 10 Nov 1998 17:10:09 +1030 (CST) From: Kris Kennaway To: Steve Kargl Cc: Nate Williams , dnelson@emsphone.com, rivers@dignus.com, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <199811100634.WAA12678@troutmask.apl.washington.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Nov 1998, Steve Kargl wrote: > According to Nate Williams: > > > > Ahh, but what happens when I have to run the same applications in the > > > > same shell? Do I have to modify my environment everytime I run a > > > > different application? Do I have to remember which 'emulated OS' the > > > > application runs? > > > > > > That's where the proposed "commercial ports" category would come in. Someone > > > could provide wrappers for installation, executing, etc, which handle all the > > > messy work of setting environment variables and so forth to get the thing to > > > run, for things which require a 'tweaked' emulation environment. > > > > Is there an echo in the room? Isn't this what I initially proposed as a > > better alternative to hacking up the uname(1) sources? > > > > There's no echo, just a bunch of deaf hackers. > > I happen to disagree with the viewpoint that writing custom scripts > for each commerical vendor is a better solution. There may be only > a handful of scripts to write this month, but next month we will have > more custom scripts. If linux continues to gain in popularity among > commerical vendors, then we'll have to maintain a large collection of > scripts. There is a point of "diminishing returns" with respect to > maintain a large collection of scripts, particularly when a 4 line > change to uname(1) will accommodate the majority of the vendor supplied > scripts. I'm not sure we do disagree. Your 4-line change to uname(1) was to have it respect an environment variable and return it as the result of uname(1), correct? Someone pointed out at some point in this somewhat confused discussion that that would require people to repeatedly change their environment variables before running different emulated binaries, each of which looks for uname(1) at runtime. My suggestion was for a script wrapper which performs this environment-setting automatically, and then calls the emulated binary. This is probably a 2-line script itself, so is trivial to do, but makes it transparent for users who obtain the wrappers from a skeleton port for the "Mumbulator for Linux" commercial software (or freeware, but binary-only, etc). This ties in with the "FreeBSD certification program" which was proposed on -advocacy the other week: wherein a group of "us" would have the job of working out which software works with FreeBSD under emulation, documenting any caveats, providing the vendor with an appropriate "certificate" if they wish to use it, and creating the necessary "wrapper port" which will let people trivially install and run the software they obtain or purchase, under our emulation. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 04:40:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA18131 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 04:40:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mushi.colo.neosoft.com (mushi.colo.neosoft.com [206.109.6.82]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA18122 for ; Tue, 10 Nov 1998 04:40:44 -0800 (PST) (envelope-from peter@taronga.com) Received: (qmail 4366 invoked from network); 10 Nov 1998 12:40:27 -0000 Received: from bonkers.neosoft.com (HELO bonkers.taronga.com) (root@206.109.2.48) by mushi.colo.neosoft.com with SMTP; 10 Nov 1998 12:40:27 -0000 Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id GAA08709; Tue, 10 Nov 1998 06:40:25 -0600 Date: Tue, 10 Nov 1998 06:40:25 -0600 From: peter@taronga.com (Peter da Silva) Message-Id: <199811101240.GAA08709@bonkers.taronga.com> To: hackers@FreeBSD.ORG Newsgroups: taronga.freebsd.hackers Subject: Re: linux software installation and uname References: <199811100634.WAA12678@troutmask.apl.washington.edu> Organization: none Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Someone pointed out at some point in this somewhat confused discussion that >that would require people to repeatedly change their environment variables >before running different emulated binaries, each of which looks for uname(1) >at runtime. Are there such binaries? I thought that this was an installation script. I haven't heard of any binaries barfing on uname(1) or even uname(3). Yes, I know Netscape complains about FreeBSD's uname(3), but it's nothing you need to worry about... it's really only install scripts that even have a reason to care. This is therefore more like brandelf than LD_LIBRARY_PATH, no? Or are there actually runtime requirements for magic uname(3) results after all? -- This is The Reverend Peter da Silva's Boring Sig File - there are no references to Wolves, Kibo, Discordianism, or The Church of the Subgenius in this document "The GCOS GERTS interface is so bad that a description here is inappropriate. Anyone seeking to use this interface should seek divine guidance." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 04:53:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19197 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 04:53:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zeus.dnt.md (zeus.dnt.md [193.219.215.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19161 for ; Tue, 10 Nov 1998 04:52:42 -0800 (PST) (envelope-from vr@dnt.md) Received: from localhost (vr@localhost) by zeus.dnt.md (8.8.8/8.8.8) with SMTP id OAA10155 for ; Tue, 10 Nov 1998 14:51:47 GMT (envelope-from vr@dnt.md) Date: Tue, 10 Nov 1998 14:51:47 +0000 (GMT) From: Veaceslav Revutchi To: hackers@FreeBSD.ORG Subject: kern.maxproc read-only In-Reply-To: <3647B2AF.794BDF32@whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello for god sake can anyone tell me how to increase the subject in 2.2.6. It appears to be read-only. I have a crowded news server and it's giving this "cannot fork" and "resource temporarily unavailable" messages. thank you in advance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 05:09:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA20552 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 05:09:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA20541 for ; Tue, 10 Nov 1998 05:09:53 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from gnipahellir.ifi.uio.no (2602@gnipahellir.ifi.uio.no [129.240.64.86]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id OAA21938; Tue, 10 Nov 1998 14:09:29 +0100 (MET) Received: (from dag-erli@localhost) by gnipahellir.ifi.uio.no ; Tue, 10 Nov 1998 14:09:26 +0100 (MET) Mime-Version: 1.0 To: Veaceslav Revutchi Cc: hackers@FreeBSD.ORG Subject: Re: kern.maxproc read-only References: Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 10 Nov 1998 14:09:25 +0100 In-Reply-To: Veaceslav Revutchi's message of "Tue, 10 Nov 1998 14:51:47 +0000 (GMT)" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id FAA20546 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Veaceslav Revutchi writes: > for god sake can anyone tell me how to increase the subject in 2.2.6. > It appears to be read-only. Bump maxusers in your kernel config. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 05:12:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA20951 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 05:12:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA20943 for ; Tue, 10 Nov 1998 05:12:42 -0800 (PST) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id IAA25717; Tue, 10 Nov 1998 08:11:29 -0500 (EST) Date: Tue, 10 Nov 1998 08:11:28 -0500 (EST) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Veaceslav Revutchi cc: hackers@FreeBSD.ORG Subject: Re: kern.maxproc read-only In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Nov 1998, Veaceslav Revutchi wrote: > > hello > for god sake can anyone tell me how to increase the subject in 2.2.6. > It appears to be read-only. > > I have a crowded news server and it's giving this "cannot fork" and > "resource temporarily unavailable" messages. Why don't you increase MAXUSERS in your kernel config and rebuild a new kernel. Use something alot bigger than what it's set to now. Also, READ param.c : #define NPROC (20 + 16 * MAXUSERS) #define MAXFILES (NPROC*2) int maxproc = NPROC; /* maximum # of processes */ Increasing MAXUSERS in your kernel will make your god forsaken problem go away. :-) -- "You both seem to be ignoring the fact that the networking market is driven by so-called 'IT professionals' these days, most of whom can't tell the difference between an ARP and a carp." --Wes Peters ===================================| Open Systems FreeBSD Consulting. FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186 -----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 05:35:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23105 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 05:35:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23100 for ; Tue, 10 Nov 1998 05:35:40 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id IAA18301; Tue, 10 Nov 1998 08:35:16 -0500 (EST) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id JAA24774; Tue, 10 Nov 1998 09:22:33 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id IAA27613; Tue, 10 Nov 1998 08:36:26 -0500 (EST) Date: Tue, 10 Nov 1998 08:36:26 -0500 (EST) From: Thomas David Rivers Message-Id: <199811101336.IAA27613@lakes.dignus.com> To: hackers@FreeBSD.ORG, peter@taronga.com Subject: Re: linux software installation and uname In-Reply-To: <199811101240.GAA08709@bonkers.taronga.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Someone pointed out at some point in this somewhat confused discussion that > >that would require people to repeatedly change their environment variables > >before running different emulated binaries, each of which looks for uname(1) > >at runtime. > > Are there such binaries? I thought that this was an installation script. I > haven't heard of any binaries barfing on uname(1) or even uname(3). Yes, I > know Netscape complains about FreeBSD's uname(3), but it's nothing you need > to worry about... it's really only install scripts that even have a reason > to care. Yes - there was a least one - I ran into it. (The license checker wanted to ensure it was running on Linux.) But, I successfully lobbied the vendor to check for both FreeBSD & Linux. So - that's a done deal... Just a point of information... > > This is therefore more like brandelf than LD_LIBRARY_PATH, no? Or are there > actually runtime requirements for magic uname(3) results after all? > - Dave R. - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 07:27:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05950 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 07:27:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from geek.grf.ov.com (geek.grf.ov.com [192.251.86.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05922 for ; Tue, 10 Nov 1998 07:27:02 -0800 (PST) (envelope-from ksmm@threespace.com) Received: from pebbles (pebbles.cam.veritas.com [166.98.49.16]) by geek.grf.ov.com (8.9.0/8.9.0) with SMTP id KAA12977 for ; Tue, 10 Nov 1998 10:26:33 -0500 (EST) Message-Id: <199811101526.KAA12977@geek.grf.ov.com> X-Sender: ksmm@mail.cybercom.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Tue, 10 Nov 1998 10:23:16 -0500 To: hackers@FreeBSD.ORG From: The Classiest Man Alive Subject: Re: linux software installation and uname In-Reply-To: References: <199811100432.VAA09970@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are these ideas mutually exclusive? Is there any reason that a /compat/linux/bin/uname couldn't be scripted which could set the proper environment variable and call the /usr/bin/uname of FreeBSD? In it's absence, the standard /usr/bin/uname would be called. K.S. At 11:54 PM 11/9/98 , Chuck Robey wrote: >Nate, it *seems* that what I'm hearing from him is that he wants to hack >uname so that it would respond to the environmental variables that you >want him to write wrappers for. I think you're right, you want >wrappers, but the uname thing is something that most commercial wrappers >rely on. He just wants uname to listen to some environmental variables. > >If there's some other way to do it, I haven't seen it yet ... am I >wrong? > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 07:34:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06764 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 07:34:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from stone.locallink.net (Stone.LocalLink.Net [204.71.156.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06734 for ; Tue, 10 Nov 1998 07:34:36 -0800 (PST) (envelope-from kpitcher@locallink.net) Received: from Diamond (Diamond.LocalLink.Net [204.71.156.68]) by stone.locallink.net (8.8.8/8.8.7) with SMTP id KAA09373 for ; Tue, 10 Nov 1998 10:42:14 -0500 (EST) (envelope-from kpitcher@locallink.net) From: "Keith Pitcher" To: Subject: TV out Card question Date: Tue, 10 Nov 1998 10:33:49 -0500 Message-ID: <000001be0cbf$83887e80$449c47cc@Diamond.LocalLink.Net> 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 8.5, Build 4.71.2377.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I want to setup a FreeBSD box with a TV out card, and see how well things look with Xwindows on a TV. Any suggestions/recommendations on the card to use? I've seen Trident cards with TV out for very resonable prices, but there's a number of different ones to choose from. For example, I saw the ATI all in one wonder mention that it is incompatible with non Windows OSes for TV functions. Is that part of the card or just a lack of drivers by them? If no one has ever tried this, then perhaps give some recommendations - we could always take a crack at making our own driver. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Keith Pitcher kpitcher@locallink.net LocalLink - Your Local Link to the World http://www.locallink.net 800 687-2202 616 424-4999 Fax : 616 424-4995 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 07:56:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08571 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 07:56:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08563 for ; Tue, 10 Nov 1998 07:56:13 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id HAA14049; Tue, 10 Nov 1998 07:59:49 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811101559.HAA14049@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname In-Reply-To: from Kris Kennaway at "Nov 10, 1998 5:10: 9 pm" To: kkennawa@physics.adelaide.edu.au (Kris Kennaway) Date: Tue, 10 Nov 1998 07:59:49 -0800 (PST) Cc: nate@mt.sri.com, dnelson@emsphone.com, rivers@dignus.com, hackers@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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Kris Kennaway: > On Mon, 9 Nov 1998, Steve Kargl wrote: > [large amounts of context snip] >> I happen to disagree with the viewpoint that writing custom scripts >> for each commerical vendor is a better solution. There may be only >> a handful of scripts to write this month, but next month we will have >> more custom scripts. If linux continues to gain in popularity among >> commerical vendors, then we'll have to maintain a large collection of >> scripts. There is a point of "diminishing returns" with respect to >> maintain a large collection of scripts, particularly when a 4 line >> change to uname(1) will accommodate the majority of the vendor supplied >> scripts. My disagreement is with Nate, whom I respect for his antibloat stance, because he seems to want to ignore the problem. > I'm not sure we do disagree. Your 4-line change to uname(1) was to have it > respect an environment variable and return it as the result of uname(1), > correct? Yes. > Someone pointed out at some point in this somewhat confused discussion that > that would require people to repeatedly change their environment variables > before running different emulated binaries, each of which looks for uname(1) > at runtime. *Binaries* will probably call uname(3) which is a function in libc. If you are running a linux binary, uname(3) will be picked up from /compat/linux/usr/lib/libc.so.5. I have not checked its return value, but my suggested change can have no affect on uname(3). My suggested change can have only an affect on shell scripts that call uname(1). In my case, the script was needed to install and partially configure the Portland Group Fortran compilers. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 08:17:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10906 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 08:17:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10885 for ; Tue, 10 Nov 1998 08:17:41 -0800 (PST) (envelope-from fanf@demon.net) Received: by server.noc.demon.net; id QAA28969; Tue, 10 Nov 1998 16:17:24 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xmaa28956; Tue, 10 Nov 98 16:17:12 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 0zdGhj-00037Q-00; Tue, 10 Nov 1998 16:31:43 +0000 To: freebsd-hackers@FreeBSD.ORG From: Tony Finch Subject: Re: [Vinum] Stupid benchmark: newfsstone Newsgroups: chiark.mail.freebsd.hackers In-Reply-To: <199811100638.WAA00637@dingo.cdrom.com> Organization: Deliberate Obfuscation To Amuse Tony Message-Id: Date: Tue, 10 Nov 1998 16:31:43 +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > >(you want to mention building filesystems in your manpages somewhere >too - the '-v' option is not immediately obvious). There's a "Making file systems" section in vinum(4). >Tomorrow I build the world on it. We have an experimental new "high performance" cacheing reverse web proxy running Squid 2 on FreeBSD 3 with vinum and soft updates, which we have run in service for a few days. Apart from some odd crashes on the first day that disappeared after a newfs, it is OK so far. Tony. -- f.a.n.finch.523654357374743743747333764375697569700 dot@dotat.at fanf@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 10:15:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25684 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 10:15:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25618 for ; Tue, 10 Nov 1998 10:14:23 -0800 (PST) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id MAA09462; Tue, 10 Nov 1998 12:13:23 -0600 (CST) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma009460; Tue, 10 Nov 98 12:13:21 -0600 Received: from spawn.nectar.com (localhost.nectar.com [127.0.0.1]) by spawn.nectar.com (8.9.1/8.9.1) with ESMTP id MAA11517; Tue, 10 Nov 1998 12:13:21 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Message-Id: <199811101813.MAA11517@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: <199811100634.WAA12678@troutmask.apl.washington.edu> References: <199811100634.WAA12678@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname To: Steve Kargl cc: nate@mt.sri.com (Nate Williams), kkennawa@physics.adelaide.edu.au, dnelson@emsphone.com, rivers@dignus.com, hackers@FreeBSD.ORG Date: Tue, 10 Nov 1998 12:13:21 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Why would we not put a real linux uname(1) in /compat/linux/usr/bin? This is an emulation issue. Why impact the BSD userland sources? The path of munging BSD so that it looks like some other OS leads to just throwing out our userland and using some Linux distribution... or worse yet, an attempt to become some chameleon OS such as AIX. Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org On 9 November 1998 at 22:34, Steve Kargl wrote: [snip] > There is a point of "diminishing returns" with respect to > maintain a large collection of scripts, particularly when a 4 line > change to uname(1) will accommodate the majority of the vendor supplied > scripts. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNkiCQDeRhT8JRySpAQHT+wP/Sf1JgGjOQm/Om1GZ6NF7NcmwxWMm39Sx KkgdwE05xreTVBylXIUaFoxV1UwE/Mpo0sW1RFWnZ0Q3kz0TFtEaLMKUyXjz5wSa G98HVFkKKPHd+H1bSjAUg9JwQMBKIebRScvAGrAwCqLuxU0sBk8QWgWKUBZnmshf /R/+AahLxRw= =v1DS -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 10:20:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26346 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 10:20:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elektra.ultra.net (elektra.ultra.net [199.232.56.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26327 for ; Tue, 10 Nov 1998 10:20:12 -0800 (PST) (envelope-from syang@directhit.com) Received: from moe.directhit.com ([10.4.18.2]) by elektra.ultra.net (8.8.8/ult.n14767) with ESMTP id NAA24103; Tue, 10 Nov 1998 13:16:47 -0500 (EST) Received: by MOE with Internet Mail Service (5.0.1459.74) id ; Tue, 10 Nov 1998 13:15:42 -0500 Message-ID: <839A86AB6CE4D111A52200104B938D430B066B@MOE> From: Steven Yang To: "'dg@root.com'" , Mike Smith Cc: Steven Yang , "'Open Systems Networking'" , "'freebsd-hackers@freebsd.org'" Subject: RE: FW: Can't get rid of my mbufs. Date: Tue, 10 Nov 1998 13:15:41 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1459.74) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Refresher: I started this thread two weeks ago and haven't had a time to reply until now. I'm using FreeBSD 2.2.5 (I previously stated 2.2.6, but I was wrong) with Apache 1.2.4 using FastCGI. A typical server response is about 22K of text, and under heavy load (20+ requests/second), my mbufs (as seen through netstat -m) keep increasing until the server reboots itself (when I have > ~10000 mbufs) It appears that all of the requests are getting valid replies (we check the returned web page for a string), even at loads around 100 requests/second. We do not do reverse-DNS. My original question and one of the replies is attached at the bottom of this email. The higher the load, the faster the mbufs increase. Under low load, the problem does not arise and new mbufs are not allocated. I was requested to give you guys the output of "netstat -n", as shown below. Big questions: do I have an mbuf leak? Is it possibly my fault? Could it be my version of FastCGI? Will upgrading my OS to 2.2.7 solve the problem? Will upgrading Apache solve the problem? > netstat -n Active Internet connections Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp 0 0 10.4.18.101.6010 10.4.18.101.1031 ESTABLISHED tcp 0 0 10.4.18.101.1031 10.4.18.101.6010 ESTABLISHED tcp 0 20 10.4.18.101.22 10.4.18.198.2097 ESTABLISHED tcp 0 0 10.4.18.101.22 10.4.18.199.1529 ESTABLISHED tcp 0 0 10.4.18.101.22 10.4.18.210.4307 ESTABLISHED tcp 0 0 10.4.18.101.22 10.4.18.210.4168 ESTABLISHED udp 0 0 10.4.18.101.1022 10.4.18.5.2049 udp 0 0 10.4.18.101.1023 10.4.18.5.2049 Active UNIX domain sockets Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr f48daf00 stream 0 0 f4926700 0 0 0 /tmp/OM_WS_84.21 f486d000 stream 0 0 f487a380 0 0 0 /tmp/OM_WS_83.21 f489d000 stream 0 0 f487eb00 0 0 0 /tmp/OM_WS_82.21 f4885200 stream 0 0 f47a0f80 0 0 0 /tmp/OM_WS_81.21 f4900100 stream 0 0 f4935e80 0 0 0 /tmp/OM_WS_80.21 f47b6d00 stream 0 0 f47ca980 0 0 0 /tmp/OM_WS_79.21 f48f8800 stream 0 0 f47b3e00 0 0 0 /tmp/OM_WS_78.21 f47b4500 stream 0 0 f482f380 0 0 0 /tmp/OM_WS_77.21 f4879900 stream 0 0 f47bea00 0 0 0 /tmp/OM_WS_76.21 f47ce900 stream 0 0 f4925a00 0 0 0 /tmp/OM_WS_75.21 f4791300 stream 0 0 f4934b80 0 0 0 /tmp/OM_WS_74.21 f48bf500 stream 0 0 f47a8b80 0 0 0 /tmp/OM_WS_73.21 f47b4900 stream 0 0 f4834700 0 0 0 /tmp/OM_WS_72.21 f478a200 stream 0 0 f4790180 0 0 0 /tmp/OM_WS_71.21 f4830000 dgram 0 0 0 f31a4594 0 f31f4e94 f48bf300 dgram 0 0 0 f31a4594 0 f31d9f14 f47c4000 dgram 0 0 0 f31a4594 0 f31c4b94 f4887100 dgram 0 0 0 f31a4594 0 f31d6e14 f47d0400 dgram 0 0 0 f31a4594 0 f31b5a14 f4786b00 dgram 0 0 0 f31a4594 0 0 f48d5d00 dgram 0 0 0 f31a4594 0 f31a4a14 f4742900 dgram 0 0 f4743680 0 f31c2694 0 /var/run/log > -----Original Message----- > From: David Greenman [SMTP:dg@root.com] > Sent: Wednesday, October 28, 1998 12:37 AM > To: Mike Smith > Cc: Steven Yang; 'Open Systems Networking'; > 'freebsd-hackers@freebsd.org' > Subject: Re: FW: Can't get rid of my mbufs. > > >> >If the machine is left idle for 2 hours, and presumably from this > we > >> >would expect that all open connections were closed > >> > >> That would be presuming too much. > > > >How about we ask the tester? > > I already did several messages back. I said "What does netstat -n > show?" > Note that I'm not asking for -m. I'm interested in the state of the > (apparantly still open) connections, not in the memory summaries. -n > simply > because doing reverse DNS for 6000+ connections might take a very long > time. > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project > > > -----Original Message----- > > From: Steven Yang > > Sent: Tuesday, October 20, 1998 11:04 AM > > To: 'freebsd-questions@freebsd.org' > > Subject: Can't get rid of my mbufs. > > > > Hi, we are running a test on FreeBSD 2.2.6, using Apache 1.2.4 with > > FastCGI. We are performing about 100 requests per second over a > > high-speed switch. On average, each request returns about 20,000 > > bytes, so we are transferring about 2MB/sec. The problem is, our > > machine ends up rebooting itself after a couple hours. > > Here are some sample outputs after pounding on our machine for over 1 > > hour: > > # netstat -m > > 4449 mbufs in use: > > 4437 mbufs allocated to data > > 1 mbufs allocated to packet headers > > 7 mbufs allocated to protocol control blocks > > 4 mbufs allocated to socket names and addresses > > 4263/4314 mbuf clusters in use > > 9184 Kbytes allocated to network (98% in use) > > 0 requests for memory denied > > 0 requests for memory delayed > > 0 calls to protocol drain routines > > > > #netstat -r > > Routing tables > > > > Internet: > > Destination Gateway Flags Refs Use > > Netif Expire > > default 10.4.18.1 UGSc 1 0 > > fxp0 > > 10.4.18/24 link#1 UC 0 0 > > 10.4.18.1 0:10:7b:a6:a6:e8 UHLW 2 0 > > fxp0 684 > > moe 0:10:4b:93:8d:43 UHLW 0 43 > > fxp0 1186 > > 10.4.18.198 0:10:4b:99:c5:e2 UHLW 1 9215795 > > fxp0 972 > > localhost localhost UH 0 0 > > lo0 > > > > Symptoms: I can sit around for a long time with no network activity, > > and the mbufs won't decrease. If I exceed 10,000 mbuf clusters, I'm > > in danger of hitting a server reboot. I can kill Apache, but that > > doesn't help. My memory usage increases linearly with increasing mbuf > > clusters. mbuf clusters only seem to increase under heavy load. > > Basically, once an mbuf is allocated, it's never deallocated, and we > > don't have memory leaks. > > How do I solve this problem? > > > > Thanks, > > Steven To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 10:39:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28199 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 10:39:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28181 for ; Tue, 10 Nov 1998 10:38:52 -0800 (PST) (envelope-from cmascott@world.std.com) Received: from world.std.com by europe.std.com (8.7.6/BZS-8-1.0) id NAA12369; Tue, 10 Nov 1998 13:38:18 -0500 (EST) Received: from europa.local (world-f.std.com) by world.std.com (TheWorld/Spike-2.0) id AA28102; Tue, 10 Nov 1998 13:38:16 -0500 Received: (from cmascott@localhost) by europa.local (8.8.8/8.8.8) id NAA00328 for hackers@freebsd.org; Tue, 10 Nov 1998 13:38:11 -0500 (EST) (envelope-from cmascott) Date: Tue, 10 Nov 1998 13:38:11 -0500 (EST) From: Carl Mascott Message-Id: <199811101838.NAA00328@europa.local> To: hackers@FreeBSD.ORG Subject: Request action on medium priority PR kern/8383 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I submitted a medium priority PR (kern/8383) three weeks ago. A patch was included. No one has taken any action on it yet. In a nutshell: >Category: kern >Responsible: freebsd-bugs >Synopsis: msdosfs wipes out NT VFAT lower case flags >Arrival-Date: Tue Oct 20 09:00:00 PDT 1998 Since msdosfs is destroying directory information, I think that this is serious enough that someone should have a look. Could someone please do so? It would be really nice if this could make it into -stable in time for 2.2.8-R. I have been running 2.2.7-R with the patch since 10/13/98. P.S. The good news (other than that a patch was included) is that the directory information that is being destroyed is non-critical. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 10:46:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28850 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 10:46:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28818 for ; Tue, 10 Nov 1998 10:46:54 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA186553506; Tue, 10 Nov 1998 13:45:06 -0500 Date: Tue, 10 Nov 1998 13:45:06 -0500 (EST) From: Bill Fumerola To: Carl Mascott Cc: hackers@FreeBSD.ORG Subject: Re: Request action on medium priority PR kern/8383 In-Reply-To: <199811101838.NAA00328@europa.local> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Nov 1998, Carl Mascott wrote: > >Category: kern > >Responsible: freebsd-bugs > >Synopsis: msdosfs wipes out NT VFAT lower case flags > >Arrival-Date: Tue Oct 20 09:00:00 PDT 1998 I'm not one of the src guys, but I can say with a resonable amount of certianty that msdosfs was never meant for NTFS. - 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-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 11:59:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06826 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 11:59:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06818 for ; Tue, 10 Nov 1998 11:59:01 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id LAA14084; Tue, 10 Nov 1998 11:58:19 -0800 (PST) (envelope-from dillon) Date: Tue, 10 Nov 1998 11:58:19 -0800 (PST) From: Matthew Dillon Message-Id: <199811101958.LAA14084@apollo.backplane.com> To: Steven Yang Cc: "'dg@root.com'" , Mike Smith , Steven Yang , "'Open Systems Networking'" , "'freebsd-hackers@freebsd.org'" Subject: Re: RE: FW: Can't get rid of my mbufs. References: <839A86AB6CE4D111A52200104B938D430B066B@MOE> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Refresher: I started this thread two weeks ago and haven't had a time to :reply until now. I'm using FreeBSD 2.2.5 (I previously stated 2.2.6, :but I was wrong) with Apache 1.2.4 using FastCGI. A typical server :response is about 22K of text, and under heavy load (20+ :requests/second), my mbufs (as seen through netstat -m) keep increasing :until the server reboots itself (when I have > ~10000 mbufs) It appears :that all of the requests are getting valid replies (we check the :returned web page for a string), even at loads around 100 :requests/second. We do not do reverse-DNS. My original question and :one of the replies is attached at the bottom of this email. : :The higher the load, the faster the mbufs increase. Under low load, the :problem does not arise and new mbufs are not allocated. I was requested :to give you guys the output of "netstat -n", as shown below. Big :questions: do I have an mbuf leak? Is it possibly my fault? Could it :be my version of FastCGI? Will upgrading my OS to 2.2.7 solve the :problem? Will upgrading Apache solve the problem? There are three issues that I can think of. I'm not sure 2.2.5 has the sysctl's to fix them (I think it does), but 2.2.7 certainly does. The mbuf's are almost certainly related to stale connections that aren't going away. This typically occurs because Apache has not turned on keepalives. You can fix this by turning on keepalives and reducing the keepalive idle test interval: sysctl -w net.inet.tcp.keepidle=1800 sysctl -w net.inet.tcp.keepintvl=150 sysctl -w net.inet.tcp.keepinit=150 sysctl -w net.inet.tcp.always_keepalive=1 NOTE: you must restart the web server after making these changes so it picks up the default The second issue could be that your default tcp window sizes are too large. The defaults are actually reasonable... 16K: sysctl -a | fgrep tcp (look for tcp.sendspace, tcp.recvspace) Check to make sure that Apache is not overriding the default window size to something huge. I don't understand why your netstat shows so few connections... are you sure apache was running at 20 hits/sec at the time you ran the netstat ? netstat -tn | fgrep tcp The third issue is the number of allocated protocol control blocks in the netstat below... looks like a kernel bug to me, but not one I've ever seen before. I would immediately upgrade the machine to 2.2.7. If this is your problem, I'll bet 2.2.7 will fix it. also do a 'ps ax' and look for hung CGI's, and try killing the server entirely (and anything else that was run from the server) and see if the space gets reclaimed. I'm thinking pipes, possibly, but dunno if pipes use network mbufs. :> > # netstat -m :> > 4449 mbufs in use: :> > 4437 mbufs allocated to data :> > 1 mbufs allocated to packet headers :> > 7 mbufs allocated to protocol control blocks :> > 4 mbufs allocated to socket names and addresses :> > 4263/4314 mbuf clusters in use :> > 9184 Kbytes allocated to network (98% in use) Here's one of our servers (doing around 30 hits/sec at the moment). Note that the in-use percentage is 48%, which is typical. If you regularly see in-use percentages above 80% it's almost certainly due to a stale-socket problem, which in turn is usually due to keepalive's being turned off and blown sockets building up. This box is running (roughly) 2.2.7. shell3:/home/dillon# netstat -m 3201 mbufs in use: 1470 mbufs allocated to data 1513 mbufs allocated to packet headers 211 mbufs allocated to protocol control blocks 7 mbufs allocated to socket names and addresses 1206/2684 mbuf clusters in use 5768 Kbytes allocated to network (48% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 12:12:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08525 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 12:12:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08518 for ; Tue, 10 Nov 1998 12:12:28 -0800 (PST) (envelope-from cmascott@world.std.com) Received: from world.std.com by europe.std.com (8.7.6/BZS-8-1.0) id PAA26182; Tue, 10 Nov 1998 15:05:19 -0500 (EST) Received: by world.std.com (TheWorld/Spike-2.0) id AA16804; Tue, 10 Nov 1998 15:05:19 -0500 Date: Tue, 10 Nov 1998 15:05:19 -0500 From: cmascott@world.std.com (Carl Mascott) Message-Id: <199811102005.AA16804@world.std.com> To: hackers@FreeBSD.ORG Subject: Re: Request action on medium priority PR kern/8383 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fumerola wrote: >> >Category: kern >> >Responsible: freebsd-bugs >> >Synopsis: msdosfs wipes out NT VFAT lower case flags >> >Arrival-Date: Tue Oct 20 09:00:00 PDT 1998 > > I'm not one of the src guys, but I can say with a resonable amount of > certianty that msdosfs was never meant for NTFS. PR kern/8383 has nothing to do with NTFS. You somehow misinterpreted NT VFAT as NTFS, apparently. VFAT is what FAT is called in Win 9x and Win NT. -- Carl Mascott cmascott@world.std.com uunet!world!cmascott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 12:19:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09258 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 12:19:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09249 for ; Tue, 10 Nov 1998 12:19:34 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA217739081; Tue, 10 Nov 1998 15:18:01 -0500 Date: Tue, 10 Nov 1998 15:18:01 -0500 (EST) From: Bill Fumerola To: Carl Mascott Cc: hackers@FreeBSD.ORG Subject: Re: Request action on medium priority PR kern/8383 In-Reply-To: <199811102005.AA16804@world.std.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Nov 1998, Carl Mascott wrote: > PR kern/8383 has nothing to do with NTFS. You somehow > misinterpreted NT VFAT as NTFS, apparently. VFAT is what FAT > is called in Win 9x and Win NT. Apologies. In your message I saw ``NT VFAT'' and assumed it was some NTFS deviant. I'm _not_ an NT/9x person by any means, and am not up on the terminalogy. Sorry. :> - 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-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 12:20:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09690 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 12:20:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09680 for ; Tue, 10 Nov 1998 12:20:14 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id PAA06608 for hackers@freebsd.org; Tue, 10 Nov 1998 15:19:42 -0500 (EST) (envelope-from lee) Message-ID: <19981110151942.A6604@tidalwave.net> Date: Tue, 10 Nov 1998 15:19:42 -0500 From: Lee Cremeans To: hackers@FreeBSD.ORG Subject: What is void *arg in pci_map_int used for? Reply-To: lcremean@tidalwave.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The subject says it all...(and once I understand it, I may write a man page so I won't forget any of it.) -- Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | mailto:lcremean@tidalwave.net http://st-lcremean.tidalwave.net | Powered by FreeBSD 3.0-CURRENT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 12:41:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12000 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 12:41:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA11995 for ; Tue, 10 Nov 1998 12:41:02 -0800 (PST) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id PAA06499; Tue, 10 Nov 1998 15:40:45 -0500 Date: Tue, 10 Nov 1998 15:40:44 -0500 (EST) From: "Ron G. Minnich" X-Sender: rminnich@terra To: hackers@FreeBSD.ORG Subject: PCI devices drivers as LKMs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think I asked this before, and it was not possible, but am just checking. Can a PCI driver be built as an LKM. Based on how PCI configuration happens, I am not sure it could, but thought I would check. ron Ron Minnich |"Using Windows NT, which is known to have some rminnich@sarnoff.com | failure modes, on a warship is similar to hoping (609)-734-3120 | that luck will be in our favor"- A. Digiorgio ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 12:43:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12154 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 12:43:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12139 for ; Tue, 10 Nov 1998 12:43:11 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00383; Tue, 10 Nov 1998 12:42:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811102042.MAA00383@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: lcremean@tidalwave.net cc: hackers@FreeBSD.ORG Subject: Re: What is void *arg in pci_map_int used for? In-reply-to: Your message of "Tue, 10 Nov 1998 15:19:42 EST." <19981110151942.A6604@tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Nov 1998 12:42:03 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The subject says it all...(and once I understand it, I may write a man page > so I won't forget any of it.) It's saved and passed to the interrupt handler when it's invoked. Typically it will be a pointer to the softc structure for the device, so that you can reuse one interrupt handler for multiple instances of a particular type of device. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 12:45:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12336 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 12:45:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12325 for ; Tue, 10 Nov 1998 12:45:23 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00401; Tue, 10 Nov 1998 12:43:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811102043.MAA00401@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Ron G. Minnich" cc: hackers@FreeBSD.ORG Subject: Re: PCI devices drivers as LKMs In-reply-to: Your message of "Tue, 10 Nov 1998 15:40:44 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Nov 1998 12:43:39 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think I asked this before, and it was not possible, but am just > checking. Can a PCI driver be built as an LKM. Based on how PCI > configuration happens, I am not sure it could, but thought I would check. There were some patches posted by Stefan Esser a little while back for this, but no, there's no standard way of doing it as you correctly intimate. Ideally we will be shifting to dynamic registration of PCI drivers with the new bus model, and this will make things easier. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 12:46:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12436 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 12:46:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12420 for ; Tue, 10 Nov 1998 12:46:11 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id VAA00261; Tue, 10 Nov 1998 21:44:14 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199811102044.VAA00261@freebsd.dk> Subject: Re: linux software installation and uname In-Reply-To: <199811101813.MAA11517@spawn.nectar.com> from Jacques Vidrine at "Nov 10, 1998 12:13:21 pm" To: n@nectar.com (Jacques Vidrine) Date: Tue, 10 Nov 1998 21:44:14 +0100 (CET) Cc: sgk@troutmask.apl.washington.edu, nate@mt.sri.com, kkennawa@physics.adelaide.edu.au, dnelson@emsphone.com, rivers@dignus.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Jacques Vidrine wrote: > > Why would we not put a real linux uname(1) in /compat/linux/usr/bin? > This is an emulation issue. Why impact the BSD userland sources? Hear hear!! > The path of munging BSD so that it looks like some other OS leads > to just throwing out our userland and using some Linux distribution... > or worse yet, an attempt to become some chameleon OS such as AIX. > > On 9 November 1998 Steve Kargl wrote: > [snip] > > There is a point of "diminishing returns" with respect to > > maintain a large collection of scripts, particularly when a 4 line > > change to uname(1) will accommodate the majority of the vendor supplied > > scripts. Excuse me, but this is an emulation thing, and the soultion must be put into the emulator or the compat stuff, no matter how few lines it takes. Putting it into "generic" FreeBSD is bad engineering. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 12:56:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13836 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 12:56:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13814 for ; Tue, 10 Nov 1998 12:56:13 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id MAA01681 for ; Tue, 10 Nov 1998 12:55:49 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 10 Nov 1998 12:55:48 -0800 (PST) From: Doug White To: hackers@FreeBSD.ORG Subject: splashkit current status? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello ... The topic of the splashkit came up today and I'm curious to know what it's current status is. I see a commit to syscons in early August about it but the only patches available otherwise are from February. And is the 2.2.x patch any good? Could you shed some light, Mike? :-) Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 13:04:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14773 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 13:04:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14768 for ; Tue, 10 Nov 1998 13:04:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA00544; Tue, 10 Nov 1998 13:03:02 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811102103.NAA00544@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug White cc: hackers@FreeBSD.ORG Subject: Re: splashkit current status? In-reply-to: Your message of "Tue, 10 Nov 1998 12:55:48 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Nov 1998 13:03:02 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The topic of the splashkit came up today and I'm curious to know what it's > current status is. I see a commit to syscons in early August about it but > the only patches available otherwise are from February. And is the 2.2.x > patch any good? > > Could you shed some light, Mike? :-) I played with it again a little bit the other night. The basic problems with the splashkit as it stands for 2.2.x are that it's really limited to 320x200x8bpp or 640x480x4bpp, and it requires some quite ugly hackery to the kernel and bootblocks. These are things that I've addressed in the new bootloader and kernel infrastructure, and Kazu dealt with the ugly integration with syscons by improving the screensaver code. I'm not highly motivated to work on the splashkit further for 2.2.x systems. As it stands, I would say that a moderately competent programmer with limited knowledge of the FreeBSD kernel should be able to take the patches and merge them into -stable. Of the patches supplied with the splashkit, about half of the ones to syscons have been adopted by the mainstream. The rest are still applicable, and easily adapted. Patches for the remainder of the system should still apply with little or no help. If someone wants to take over the 2.2.x splashkit, I'd be happy to help out with the odd piece of advice. I can't see myself working on it however, as I'm really just too busy. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 13:47:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20819 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 13:47:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20814 for ; Tue, 10 Nov 1998 13:47:56 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40344>; Wed, 11 Nov 1998 08:46:59 +1100 Date: Wed, 11 Nov 1998 08:46:03 +1100 From: Peter Jeremy Subject: SCSI tagged queueing and softupdates To: hackers@FreeBSD.ORG Message-Id: <98Nov11.084659est.40344@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG AFAIK, SCSI tagged queueing is the default in 3.0 (via cam or inside the ahc driver). (This was optionally enabled via AHC_TAGENABLE in 2.x and the 3.0 man page still describes this option, although the option is gone). According to the description, tagged queueing allows a SCSI device to re-order pending I/O requests in order to improve throughput. Soft updates, on the other hand, rely on the correct sequencing of physical writes to ensure that the disk metadata is consistent. Is this a real issue? If so, it would seem that tagged queueing must be disabled (at least for writes) when softupdates are enabled. It's not obvious to me that this is currently done (or even easy to do). Comments please. 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 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 13:58:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22583 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 13:58:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22573 for ; Tue, 10 Nov 1998 13:58:51 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id VAA05802; Tue, 10 Nov 1998 21:50:36 GMT Date: Tue, 10 Nov 1998 21:50:36 +0000 (GMT) From: Doug Rabson To: Sren Schmidt cc: Jacques Vidrine , sgk@troutmask.apl.washington.edu, nate@mt.sri.com, kkennawa@physics.adelaide.edu.au, dnelson@emsphone.com, rivers@dignus.com, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <199811102044.VAA00261@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Nov 1998, Sren Schmidt wrote: > It seems Jacques Vidrine wrote: > > > > Why would we not put a real linux uname(1) in /compat/linux/usr/bin? > > This is an emulation issue. Why impact the BSD userland sources? > > Hear hear!! > > > The path of munging BSD so that it looks like some other OS leads > > to just throwing out our userland and using some Linux distribution... > > or worse yet, an attempt to become some chameleon OS such as AIX. > > > > On 9 November 1998 Steve Kargl wrote: > > [snip] > > > There is a point of "diminishing returns" with respect to > > > maintain a large collection of scripts, particularly when a 4 line > > > change to uname(1) will accommodate the majority of the vendor supplied > > > scripts. > > Excuse me, but this is an emulation thing, and the soultion must be > put into the emulator or the compat stuff, no matter how few lines > it takes. Putting it into "generic" FreeBSD is bad engineering. I imagine that the install script is run by /bin/sh, not /compat/linux/bin/sh so it will get the regular /usr/bin/uname whatever is present in /compat/linux/usr/bin. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 14:48:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29238 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 14:48:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29227 for ; Tue, 10 Nov 1998 14:48:03 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id OAA16696; Tue, 10 Nov 1998 14:47:35 -0800 (PST) (envelope-from dillon) Date: Tue, 10 Nov 1998 14:47:35 -0800 (PST) From: Matthew Dillon Message-Id: <199811102247.OAA16696@apollo.backplane.com> To: Peter Jeremy Cc: hackers@FreeBSD.ORG Subject: Re: SCSI tagged queueing and softupdates References: <98Nov11.084659est.40344@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :AFAIK, SCSI tagged queueing is the default in 3.0 (via cam or inside :the ahc driver). (This was optionally enabled via AHC_TAGENABLE in 2.x :and the 3.0 man page still describes this option, although the option :is gone). : :According to the description, tagged queueing allows a SCSI device to :re-order pending I/O requests in order to improve throughput. Soft :updates, on the other hand, rely on the correct sequencing of physical :writes to ensure that the disk metadata is consistent. : :Is this a real issue? If so, it would seem that tagged queueing must :be disabled (at least for writes) when softupdates are enabled. It's :not obvious to me that this is currently done (or even easy to do). : :Comments please. : :Peter No, this is not an issue. The SCSI command set allows you to flag tags for ordered sequencing. Reads, of course, can be done out of order and that is the main advantage. Write ordering is a more complex issue and I think (?) they are all simply flagged to be ordered. Tags also mean that you avoid much of the per-transaction latencies involved with SCSI command sequencing by 'absorbing it' in parallel with the drive running the previousw N requested transactions. The advantages, especially with CAM and softupdates, are phenominal. I am running a production -current news reader box with three striped 18G drives for the spool (128 sector = 64 KByte stripe). Even with the drive LEDs solid-on most of the time, the responsiveness of the news system is incredible. da1-da3, all: da3: Fixed Direct Access SCSI2 device da3: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) The OS reports on the order of 50-60 tags per device later on, but I don't have those logs any more. nntp1:/news> iostat -oK da1 da2 da3 da4 5 tty da1 da2 da3 cpu tin tout sps tps msps sps tps msps sps tps msps us ni sy in id 0 202859 69 14.5 2529 55 18.2 2419 55 18.2 6 0 18 4 72 0 71670 73 13.7 1509 71 14.1 1563 75 13.3 7 0 37 5 51 0 72358 109 9.2 2211 102 9.8 2110 105 9.5 4 0 18 4 73 0 72262 104 9.6 1992 96 10.4 2171 102 9.8 12 0 78 7 3 0 71625 73 13.7 1491 66 15.2 1511 69 14.5 8 0 36 4 52 0 71667 77 12.9 1830 83 12.1 1779 83 12.1 6 0 28 4 61 0 71861 89 11.2 1861 84 11.9 2091 96 10.4 4 0 16 3 77 0 72088 96 10.4 2017 97 10.4 2035 103 9.7 6 0 16 4 74 The drives are still doing over a megabyte/sec each with 16KByte transfers and almost totally random seeks. This is with 366 online users and taking a full feed 'burst' at the same time. And this hasn't even reached saturation. At saturation the msps drops to a very consistant 9ms. Now watch what happens when, with 366 online users and an incoming feed burst, I also copy my history file with dd. Oops, looks like the feed burst ended about half way through my test. In anycase, *THIS* is full saturation. nntp1:/news> dd if=dhistory of=xx bs=128k 1771+1 records in 1771+1 records out 232208400 bytes transferred in 100.238914 secs (2316549 bytes/sec) iostat -oK da1 da2 da3 da4 5 tty da1 da2 da3 cpu tin tout sps tps msps sps tps msps sps tps msps us ni sy in id 0 72551 103 9.7 2560 106 9.5 2759 107 9.4 6 0 31 6 57 0 72681 100 10.0 2698 100 10.0 2738 100 10.0 11 0 59 7 22 0 72854 105 9.5 2866 110 9.1 2870 105 9.5 6 0 30 6 58 0 72954 109 9.1 2768 103 9.7 2754 97 10.4 6 0 42 4 48 0 73059 109 9.2 3004 104 9.6 3129 104 9.6 7 0 25 5 63 (feed burst into news box ends, dd still going) 0 74777 107 9.3 4709 104 9.6 4667 101 9.9 6 0 33 4 57 0 75155 123 8.1 5111 115 8.7 5151 120 8.3 5 0 31 5 59 0 74663 108 9.3 4812 115 8.7 4709 111 9.0 6 0 35 5 55 0 74818 111 9.0 5031 121 8.3 4879 114 8.8 8 0 34 6 52 0 75381 124 8.0 5393 124 8.0 5482 125 8.0 5 0 34 6 54 When the burst ends, and doing no manual copying, leaving only the online readers accessing the disk, I get (not even close to saturation now): nntp1:/news> iostat -oK da1 da2 da3 da4 5 tty da1 da2 da3 cpu tin tout sps tps msps sps tps msps sps tps msps us ni sy in id 0 20 134 17 59.8 803 50 19.9 1204 67 14.9 6 0 18 4 72 0 71345 67 15.0 1172 58 17.2 1228 63 16.0 7 0 11 3 78 0 71389 80 12.5 1369 84 11.9 1473 83 12.0 4 0 12 3 80 0 71606 94 10.6 1629 90 11.1 1551 91 11.0 6 0 11 2 80 0 71187 61 16.3 1187 58 17.2 1100 60 16.7 5 0 12 3 80 -Matt :-- :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 5247 : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 15:14:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02879 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 15:14:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02874 for ; Tue, 10 Nov 1998 15:14:05 -0800 (PST) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id RAA10080; Tue, 10 Nov 1998 17:09:12 -0600 (CST) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma010078; Tue, 10 Nov 98 17:09:05 -0600 Received: from spawn.nectar.com (localhost.nectar.com [127.0.0.1]) by spawn.nectar.com (8.9.1/8.9.1) with ESMTP id RAA21609; Tue, 10 Nov 1998 17:09:05 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Message-Id: <199811102309.RAA21609@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: References: Subject: Re: linux software installation and uname To: Doug Rabson cc: Sren Schmidt , sgk@troutmask.apl.washington.edu, nate@mt.sri.com, kkennawa@physics.adelaide.edu.au, dnelson@emsphone.com, rivers@dignus.com, hackers@FreeBSD.ORG Date: Tue, 10 Nov 1998 17:09:05 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- So take care to run the install script under /compat/linux/bin/sh, perhaps by freebsd-sh$ /compat/linux/bin/sh path_to_install_script or maybe even freebsd-sh$ /compat/linux/bin/sh linux-sh$ path_to_install_script Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org On 10 November 1998 at 21:50, Doug Rabson wrote: [snip] > I imagine that the install script is run by /bin/sh, not > /compat/linux/bin/sh so it will get the regular /usr/bin/uname whatever is > present in /compat/linux/usr/bin. [snip] -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNkjHkDeRhT8JRySpAQHc3AP/SPJCjH0ahgiNTYIT2CSzU/D7SBnKPPFE n3Nf0FkdHxThDZSjCfGbCaHdp2d/09ll8xhe9Ues7+Ewk/4Dr616kMiynvTg3WcK l+jmjKhk/3C1h44xbUoAs+AHHboxmXu+gMwtxLWfgjuWAmL9kua7PwO5fH/ec76G T6mFWsH+T3Q= =KVJe -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 16:01:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08015 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 16:01:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08009 for ; Tue, 10 Nov 1998 16:00:57 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA20120; Wed, 11 Nov 1998 10:30:34 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id KAA19873; Wed, 11 Nov 1998 10:30:29 +1030 (CST) Message-ID: <19981111103028.L18183@freebie.lemis.com> Date: Wed, 11 Nov 1998 10:30:28 +1030 From: Greg Lehey To: Mike Smith , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <199811100638.WAA00637@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811100638.WAA00637@dingo.cdrom.com>; from Mike Smith on Mon, Nov 09, 1998 at 10:38:04PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 9 November 1998 at 22:38:04 -0800, Mike Smith wrote: > > Just started playing with Vinum. Gawd Greg, this thing seriously needs > a "smart" frontend to do the "simple" things. Any suggestions? After seeing people just banging out RAID configurations with GUIs, I thought that this is probably a Bad Thing. If you don't understand what you're doing, you shouldn't be doing it. The four-layer concepts used by Veritas and Vinum have always been difficult to understand. I'm trying to work out how to explain them better, but taking the Microsoft-style "don't worry, little boy, I'll do it all for you" approach is IMO not the right way. > 4 x 4GB disks (2x Atlas, 2x Grand Prix) on an ncr 53c875, slapped > together as a single volume. (you want to mention building filesystems > in your manpages somewhere too - the '-v' option is not immediately > obvious). As Tony observed, it's in vinum(4). vinum(8) just describes the interface program. Do you still think I need to add more information? There's supposed to be a user's guide, when I get round to writing it. > 6:36 elapsed to newfs the 16GB volume in concatenated mode. 4:36 to > newfs it in striped mode (64b stripes). You shouldn't really be doing performance testing in this version. It's full to the gunwhales of debugging code. But I'd be interested to know how long it took to do a newfs on one of the disks without Vinum. > There was an interesting symptom observed in striped mode, where the > disks seemed to have a binarily-weighted access pattern. Can you describe that in more detail? Maybe I should consider relating stripe size to cylinder group size. > It will get more interesting when I add two more 9GB drives and four > more 4GB units to the volume; especially as I haven't worked out if I > can stripe the 9GB units separately and then concatenate their plex > with the plex containing the 4GB units; my understanding is that all > plexes in a volume contain copies of the same data. Correct. I need to think about how to do this, and whether it's worth the trouble. It's straightforward with concatenated plexes, of course. > Can you nest plexes? No. > Anyway, apart from one incident where I managed to get a pile of > debugger calls out of Vinum (freeing already free memory - it > occurred after many failed config attempts and I haven't been able > to reproduce it) If you do get it again, please don't hesitate. Take a dump. I'd like to find these problems. Having said that, I've been planning to rewrite the config code for a while. It's still a while off, but in the meantime please tread carefully. > it hasn't let me down yet. Tomorrow I build the world on it. Good to hear. I've built several worlds, including with degraded plexes, and so have others. I don't think you'll have any trouble there. > Thanks to Greg and the folks at Cybernet! You're welcome. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 16:02:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08711 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 16:02:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08702 for ; Tue, 10 Nov 1998 16:02:36 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA20129; Wed, 11 Nov 1998 10:32:00 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id KAA19881; Wed, 11 Nov 1998 10:31:59 +1030 (CST) Message-ID: <19981111103159.M18183@freebie.lemis.com> Date: Wed, 11 Nov 1998 10:31:59 +1030 From: Greg Lehey To: Tony Finch , freebsd-hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <199811100638.WAA00637@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Tony Finch on Tue, Nov 10, 1998 at 04:31:43PM +0000 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 10 November 1998 at 16:31:43 +0000, Tony Finch wrote: > > We have an experimental new "high performance" cacheing reverse web > proxy running Squid 2 on FreeBSD 3 with vinum and soft updates, which > we have run in service for a few days. Apart from some odd crashes on > the first day that disappeared after a newfs, it is OK so far. Good to hear. As I said to Mike, this version is not really suited to performance testing. I'll go through the code and make sure that all the debugging code is removed when you remove the DEBUG flag, and that it compiles, and you could try it with that version. Watch this space. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 16:24:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12373 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 16:24:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12362 for ; Tue, 10 Nov 1998 16:24:21 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id QAA15347; Tue, 10 Nov 1998 16:23:50 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 10 Nov 1998 16:23:49 -0800 (PST) From: Doug White To: Mike Smith cc: hackers@FreeBSD.ORG Subject: Re: splashkit current status? In-Reply-To: <199811102103.NAA00544@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Nov 1998, Mike Smith wrote: > > The topic of the splashkit came up today and I'm curious to know what it's > > current status is. I see a commit to syscons in early August about it but > > the only patches available otherwise are from February. And is the 2.2.x > > patch any good? > > > > Could you shed some light, Mike? :-) > > I played with it again a little bit the other night. > > The basic problems with the splashkit as it stands for 2.2.x are that > it's really limited to 320x200x8bpp or 640x480x4bpp, and it requires > some quite ugly hackery to the kernel and bootblocks. That's okay, 2.2.x isn't the target. I was particuarly interested in knowing if the 1998020X bundle that the Project page points to is up to date. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 16:29:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12843 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 16:29:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (tex-30.camalott.com [208.229.74.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12832 for ; Tue, 10 Nov 1998 16:29:18 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id SAA10173; Tue, 10 Nov 1998 18:28:10 -0600 (CST) (envelope-from joelh) To: Doug Rabson Cc: Sren Schmidt , Jacques Vidrine , sgk@troutmask.apl.washington.edu, nate@mt.sri.com, kkennawa@physics.adelaide.edu.au, dnelson@emsphone.com, rivers@dignus.com, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname References: From: Joel Ray Holveck Date: 10 Nov 1998 18:28:09 -0600 In-Reply-To: Doug Rabson's message of "Tue, 10 Nov 1998 21:50:36 +0000 (GMT)" Message-ID: <86k913hy3q.fsf@detlev.UUCP> Lines: 24 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> Why would we not put a real linux uname(1) in /compat/linux/usr/bin? >>> This is an emulation issue. Why impact the BSD userland sources? >> Hear hear!! > I imagine that the install script is run by /bin/sh, not > /compat/linux/bin/sh so it will get the regular /usr/bin/uname > whatever is present in /compat/linux/usr/bin. I have yet to hear of any solutions that don't require a hack to the install procedure (eg, setting an environment variable). Unless somebody comes up with an idea that would magically detect what environment a given script wants, I would recommend putting a Linux uname in /copmat/linux where it belongs, and the install procedure's PATH can have /compat/linux ahead of /. This is easy to implement, keeps the core of FreeBSD pure, and paves the way for future similarities. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 17:28:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18100 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 17:28:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18093 for ; Tue, 10 Nov 1998 17:28:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA02013; Tue, 10 Nov 1998 17:27:15 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811110127.RAA02013@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug White cc: hackers@FreeBSD.ORG Subject: Re: splashkit current status? In-reply-to: Your message of "Tue, 10 Nov 1998 16:23:49 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Nov 1998 17:27:15 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 10 Nov 1998, Mike Smith wrote: > > > > The topic of the splashkit came up today and I'm curious to know what it's > > > current status is. I see a commit to syscons in early August about it but > > > the only patches available otherwise are from February. And is the 2.2.x > > > patch any good? > > > > > > Could you shed some light, Mike? :-) > > > > I played with it again a little bit the other night. > > > > The basic problems with the splashkit as it stands for 2.2.x are that > > it's really limited to 320x200x8bpp or 640x480x4bpp, and it requires > > some quite ugly hackery to the kernel and bootblocks. > > That's okay, 2.2.x isn't the target. I was particuarly interested in > knowing if the 1998020X bundle that the Project page points to is up to > date. It's "up to date" for when it was released, sure. It's by no means "up to date" for -current. Doing splash things is easier in -current now we have the VESA infrastructure in place, but there's nothing actually happening there at the moment. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 18:34:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24506 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 18:34:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24500 for ; Tue, 10 Nov 1998 18:34:24 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from o2.cs.rpi.edu (root@o2.cs.rpi.edu [128.113.96.156]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id VAA18943 for ; Tue, 10 Nov 1998 21:33:59 -0500 (EST) Received: from localhost (crossd@localhost) by o2.cs.rpi.edu (8.9.1a/8.9.1) with ESMTP id VAA01646 for ; Tue, 10 Nov 1998 21:33:59 -0500 (EST) X-Authentication-Warning: o2.cs.rpi.edu: crossd owned process doing -bs Date: Tue, 10 Nov 1998 21:33:58 -0500 From: "David E. Cross" To: freebsd-hackers@FreeBSD.ORG Subject: Kernel Hacking stuffs (Bidirectional Parallel Port) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This in on 3.0-Current. I noticed that lpt.c is a one-way connection only. I am attempting to add support for this for bidirectional communication. I am running into a problem... I don't have any documentation for the PC parallel port (the code is great, but since it doesn't need to write data, I don't have things like the equivalent of 'LPC_STB'). -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 19:04:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27709 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 19:04:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27695 for ; Tue, 10 Nov 1998 19:04:41 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id TAA28938; Tue, 10 Nov 1998 19:57:31 -0700 (MST) Date: Tue, 10 Nov 1998 19:57:31 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199811110257.TAA28938@narnia.plutotech.com> To: Matthew Dillon cc: hackers@FreeBSD.ORG Subject: Re: SCSI tagged queueing and softupdates X-Newsgroups: pluto.freebsd.hackers In-Reply-To: <98Nov11.084659est.40344@border.alcanet.com.au> <199811102247.OAA16696@apollo.backplane.com> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199811102247.OAA16696@apollo.backplane.com> you wrote: > :According to the description, tagged queueing allows a SCSI device to > :re-order pending I/O requests in order to improve throughput. Soft > :updates, on the other hand, rely on the correct sequencing of physical > :writes to ensure that the disk metadata is consistent. > : > :Is this a real issue? If so, it would seem that tagged queueing must > :be disabled (at least for writes) when softupdates are enabled. It's > :not obvious to me that this is currently done (or even easy to do). > : > :Comments please. > : > :Peter > > No, this is not an issue. Correct. > The SCSI command set allows you to flag > tags for ordered sequencing. Yes, but softupdates does not make use of this mechanism even though, via 'bowrite' it could. Instead softupdate sends batches of writes that do not have interdependencies and waits for them to complete before sending the transactions that depend on their completion. In many workloads, due to the async and distributed nature of the writes performed by the softupdates code, there is little need to use ordered writes. In the case of certain database applications that rely on fsync or when the dependency state grows large enough to hit its high resource watermark and state needs to be flushed quickly, I believe that ordered writes could significantly improve the performance of softupdates. I haven't had a chance to talk to Kirk about this yet. > Write ordering is a more > complex issue and I think (?) they are all simply flagged to be ordered. Writes are allowed to complete out of order unless the buffer client explicitly requests an ordered write. In previous BSD implementations the client had no control over ordering and could assume that the device driver might perform elevator or other sorting on any requests. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 19:07:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27952 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 19:07:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27942 for ; Tue, 10 Nov 1998 19:07:45 -0800 (PST) (envelope-from ticso@cicely5.cicely.de) Received: from cicely.cicely.de (cicely.de [194.231.9.142]) by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id EAA27900; Wed, 11 Nov 1998 04:07:05 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [10.1.1.7]) by cicely.cicely.de (8.8.8/8.8.8) with ESMTP id EAA16549; Wed, 11 Nov 1998 04:07:12 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.9.0/8.9.0) id EAA26970; Wed, 11 Nov 1998 04:06:54 +0100 (CET) Message-ID: <19981111040654.07145@cicely.de> Date: Wed, 11 Nov 1998 04:06:54 +0100 From: Bernd Walter To: Greg Lehey , Mike Smith , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <199811100638.WAA00637@dingo.cdrom.com> <19981111103028.L18183@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19981111103028.L18183@freebie.lemis.com>; from Greg Lehey on Wed, Nov 11, 1998 at 10:30:28AM +1030 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 11, 1998 at 10:30:28AM +1030, Greg Lehey wrote: > On Monday, 9 November 1998 at 22:38:04 -0800, Mike Smith wrote: > > > > Just started playing with Vinum. Gawd Greg, this thing seriously needs > > a "smart" frontend to do the "simple" things. > > Any suggestions? After seeing people just banging out RAID > configurations with GUIs, I thought that this is probably a Bad > Thing. If you don't understand what you're doing, you shouldn't be > doing it. > > The four-layer concepts used by Veritas and Vinum have always been > difficult to understand. I'm trying to work out how to explain them > better, but taking the Microsoft-style "don't worry, little boy, I'll > do it all for you" approach is IMO not the right way. > :) [...] > > You shouldn't really be doing performance testing in this version. > It's full to the gunwhales of debugging code. But I'd be interested > to know how long it took to do a newfs on one of the disks without > Vinum. > I havn't measured the time but in my opinion it's similary to ccd. Can't say about the disks itself. Looks much like it's faster than ccd together with cam on a striped volume when having parallel access and having not to small stripes. One point is that is doesn't aggregate transactions to the lower drivers. When using stripes of one sector it's doing no more than one sector transactions to the HDDs so at least with the old scsi driver there's no linear performance increase with it. That's the same with ccd. > > There was an interesting symptom observed in striped mode, where the > > disks seemed to have a binarily-weighted access pattern. > > Can you describe that in more detail? Maybe I should consider > relating stripe size to cylinder group size. > I always saw the same and I'm shure that the cylinder groups are mostly placed on one disk each. > > It will get more interesting when I add two more 9GB drives and four > > more 4GB units to the volume; especially as I haven't worked out if I > > can stripe the 9GB units separately and then concatenate their plex > > with the plex containing the 4GB units; my understanding is that all > > plexes in a volume contain copies of the same data. > > Correct. I need to think about how to do this, and whether it's worth > the trouble. It's straightforward with concatenated plexes, of > course. > In my opinion it worth. Concatenation is the only way to increase a partition and it's realy usefull to be able to do on a stripe. I never checked if it's possible to do a stripe on differend sized disks as ccd can do. And ccd is more integrated into the rest of the system but the other things are working at least as good as with ccd. > > Can you nest plexes? > > No. > > > Anyway, apart from one incident where I managed to get a pile of > > debugger calls out of Vinum (freeing already free memory - it > > occurred after many failed config attempts and I haven't been able > > to reproduce it) > > If you do get it again, please don't hesitate. Take a dump. I'd like > to find these problems. > > Having said that, I've been planning to rewrite the config code for a > while. It's still a while off, but in the meantime please tread > carefully. > > > it hasn't let me down yet. Tomorrow I build the world on it. > > Good to hear. I've built several worlds, including with degraded > plexes, and so have others. I don't think you'll have any trouble > there. > No failure with recent versions - at least no obviously. Never observed for memory-probs. > > Thanks to Greg and the folks at Cybernet! I also have to thank all them - it's grown to a usefull software. > > You're welcome. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 19:16:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28575 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 19:16:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28569 for ; Tue, 10 Nov 1998 19:16:24 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA20832; Wed, 11 Nov 1998 13:45:47 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id NAA20447; Wed, 11 Nov 1998 13:45:46 +1030 (CST) Message-ID: <19981111134546.D20374@freebie.lemis.com> Date: Wed, 11 Nov 1998 13:45:46 +1030 From: Greg Lehey To: Bernd Walter , Mike Smith , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <199811100638.WAA00637@dingo.cdrom.com> <19981111103028.L18183@freebie.lemis.com> <19981111040654.07145@cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981111040654.07145@cicely.de>; from Bernd Walter on Wed, Nov 11, 1998 at 04:06:54AM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 11 November 1998 at 4:06:54 +0100, Bernd Walter wrote: > On Wed, Nov 11, 1998 at 10:30:28AM +1030, Greg Lehey wrote: >> On Monday, 9 November 1998 at 22:38:04 -0800, Mike Smith wrote: >>> >>> Just started playing with Vinum. Gawd Greg, this thing seriously needs >>> a "smart" frontend to do the "simple" things. >> >> Any suggestions? After seeing people just banging out RAID >> configurations with GUIs, I thought that this is probably a Bad >> Thing. If you don't understand what you're doing, you shouldn't be >> doing it. >> >> The four-layer concepts used by Veritas and Vinum have always been >> difficult to understand. I'm trying to work out how to explain them >> better, but taking the Microsoft-style "don't worry, little boy, I'll >> do it all for you" approach is IMO not the right way. >> > :) > > [...] >> >> You shouldn't really be doing performance testing in this version. >> It's full to the gunwhales of debugging code. But I'd be interested >> to know how long it took to do a newfs on one of the disks without >> Vinum. >> > I havn't measured the time but in my opinion it's similary to ccd. > Can't say about the disks itself. > Looks much like it's faster than ccd together with cam on a striped > volume when having parallel access and having not to small stripes. > > One point is that is doesn't aggregate transactions to the lower drivers. > When using stripes of one sector it's doing no more than one sector > transactions to the HDDs so at least with the old scsi driver there's no > linear performance increase with it. That's the same with ccd. Correct, at least as far as Vinum goes. The rationale for this is that, with significant extra code, Vinum could aggregate transfers *from a single user request* in this manner. But any request that gets this far (in other words, runs for more than a complete stripe) is going to convert one user request into n disk requests. There's no good reason to do this, and the significant extra code would just chop off the tip of the iceberg. The solution is in the hands of the user: don't use small stripe sizes. I recommend a stripe of between 256 and 512 kB. >>> There was an interesting symptom observed in striped mode, where the >>> disks seemed to have a binarily-weighted access pattern. >> >> Can you describe that in more detail? Maybe I should consider >> relating stripe size to cylinder group size. > > I always saw the same and I'm shure that the cylinder groups are > mostly placed on one disk each. I think you mean the superblocks. It depends on the cylinder group size. I haven't thought about this yet, but I may well do so. >>> It will get more interesting when I add two more 9GB drives and four >>> more 4GB units to the volume; especially as I haven't worked out if I >>> can stripe the 9GB units separately and then concatenate their plex >>> with the plex containing the 4GB units; my understanding is that all >>> plexes in a volume contain copies of the same data. >> >> Correct. I need to think about how to do this, and whether it's worth >> the trouble. It's straightforward with concatenated plexes, of >> course. > > In my opinion it worth. > Concatenation is the only way to increase a partition and it's realy usefull > to be able to do on a stripe. I'll think about it. > I never checked if it's possible to do a stripe on differend sized > disks as ccd can do. Do you mean 'different sized disks' or 'different sized subdisks'? Different sized disks are no problem, of course, but 'different sized subdisks' are. I don't think that ccd could do this either; it would leave a hole in the volume. > And ccd is more integrated into the rest of the system but the other > things are working at least as good as with ccd. In which way is it better integrated? It's available in exactly the same way as ccd (unless, like you, you want RAID-5 :-) Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 20:27:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03943 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 20:27:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03938 for ; Tue, 10 Nov 1998 20:27:21 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA25990; Tue, 10 Nov 1998 20:16:48 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpds25988; Wed Nov 11 04:16:40 1998 Date: Tue, 10 Nov 1998 20:16:08 -0800 (PST) From: Julian Elischer To: Peter Jeremy cc: hackers@FreeBSD.ORG Subject: Re: SCSI tagged queueing and softupdates In-Reply-To: <98Nov11.084659est.40344@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG transactions can be reorderd AS LONG AS the drive does not report a perticular transaction to be completed before it really is.. Soft updates will not schedule any IO that depends on an uncompleted IO operation. So therefore all operations that have been 'passed to the driver' are not dependent on each other (by definition) On Wed, 11 Nov 1998, Peter Jeremy wrote: > AFAIK, SCSI tagged queueing is the default in 3.0 (via cam or inside > the ahc driver). (This was optionally enabled via AHC_TAGENABLE in 2.x > and the 3.0 man page still describes this option, although the option > is gone). > > According to the description, tagged queueing allows a SCSI device to > re-order pending I/O requests in order to improve throughput. Soft > updates, on the other hand, rely on the correct sequencing of physical > writes to ensure that the disk metadata is consistent. > > Is this a real issue? If so, it would seem that tagged queueing must > be disabled (at least for writes) when softupdates are enabled. It's > not obvious to me that this is currently done (or even easy to do). > > Comments please. > > 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 5247 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 22:43:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07809 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 22:43:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from isi.co.jp (ns [202.214.62.35] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07804 for ; Tue, 10 Nov 1998 22:43:35 -0800 (PST) (envelope-from john@isi.co.jp) Received: by ns.isi.co.jp id <21907>; Wed, 11 Nov 1998 13:46:48 +0900 Date: Wed, 11 Nov 1998 13:41:00 +0900 From: john cooper To: grog@lemis.com, hackers@FreeBSD.ORG, mike@smith.net.au, ticso@cicely.de Subject: SCSI vs. DMA33.. Cc: john@isi.co.jp Message-Id: <98Nov11.134648jst.21907@ns.isi.co.jp> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Just wondering if anyone has any _objective_ opinion on the performance of say wide SCSI2 vs. DMA33 IDE drives [running on contemporary motherboards]. The theoretical throughputs of 40MBs and 33MBs don't tell me a whole lot. I know SCSI was the choice for performance in the past, however I'm curious what others are seeing in actual usage these days. Thanks, -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 22:45:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08274 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 22:45:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08260 for ; Tue, 10 Nov 1998 22:45:47 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id VAA01354; Tue, 10 Nov 1998 21:12:44 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811110512.VAA01354@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname In-Reply-To: <86k913hy3q.fsf@detlev.UUCP> from Joel Ray Holveck at "Nov 10, 1998 6:28: 9 pm" To: joelh@gnu.org (Joel Ray Holveck) Date: Tue, 10 Nov 1998 21:12:44 -0800 (PST) Cc: dfr@nlsystems.com, sos@freebsd.dk, n@nectar.com, nate@mt.sri.com, kkennawa@physics.adelaide.edu.au, dnelson@emsphone.com, rivers@dignus.com, hackers@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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Joel Ray Holveck: > >>> Why would we not put a real linux uname(1) in /compat/linux/usr/bin? > >>> This is an emulation issue. Why impact the BSD userland sources? > >> Hear hear!! > > I imagine that the install script is run by /bin/sh, not > > /compat/linux/bin/sh so it will get the regular /usr/bin/uname > > whatever is present in /compat/linux/usr/bin. > > I have yet to hear of any solutions that don't require a hack to the > install procedure (eg, setting an environment variable). Unless > somebody comes up with an idea that would magically detect what > environment a given script wants, I would recommend putting a Linux > uname in /copmat/linux where it belongs, and the install procedure's > PATH can have /compat/linux ahead of /. This is easy to implement, > keeps the core of FreeBSD pure, and paves the way for future > similarities. > What about install scripts that reside on cdroms? You can't magically edit a cdrom install script unless unionfs works. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 22:48:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08607 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 22:48:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08563 for ; Tue, 10 Nov 1998 22:47:58 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA21144; Wed, 11 Nov 1998 16:20:11 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id QAA20721; Wed, 11 Nov 1998 16:20:00 +1030 (CST) Message-ID: <19981111162000.O20374@freebie.lemis.com> Date: Wed, 11 Nov 1998 16:20:00 +1030 From: Greg Lehey To: john cooper , hackers@FreeBSD.ORG, mike@smith.net.au, ticso@cicely.de Subject: Re: SCSI vs. DMA33.. References: <98Nov11.134648jst.21907@ns.isi.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <98Nov11.134648jst.21907@ns.isi.co.jp>; from john cooper on Wed, Nov 11, 1998 at 01:41:00PM +0900 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 11 November 1998 at 13:41:00 +0900, john cooper wrote: > > Hi, > Just wondering if anyone has any _objective_ opinion on > the performance of say wide SCSI2 vs. DMA33 IDE drives [running > on contemporary motherboards]. Depends on what you mean by "objective". > The theoretical throughputs of 40MBs and 33MBs don't tell me a whole > lot. I know SCSI was the choice for performance in the past, > however I'm curious what others are seeing in actual usage these > days. SCSI is still the performance choice, but the field is closer now. I have five drives on my main machine: wd0: 1223MB (2504880 sectors), 2485 cyls, 16 heads, 63 S/T, 512 B/S wd2: 6197MB (12692736 sectors), 12592 cyls, 16 heads, 63 S/T, 512 B/S ide_pci: generic_dmainit 0170:1: warning, IDE controller timing not set wdc1: unit 1 (wd3): , DMA, 32-bit, multi-block-16 wd3: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ahc0: rev 0x03 int a irq 11 on pci0.9.0 ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 64H 32S/T 2063C) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI2 device da1: 3.300MB/s transfers, Tagged Queueing Enabled da1: 4096MB (8388608 512 byte sectors: 64H 32S/T 4096C) I'm running 3.0-CURRENT (post-RELEASE), and as you can see Ultra DMA is enabled on the IDE drives. Here's what I get transferring 32 MB from each raw device: $ dd if=/dev/rwd0c bs=32k count=1000 of=/dev/null 32768000 bytes transferred in 6.938876 secs (4722379 bytes/sec) $ dd if=/dev/rwd2c bs=32k count=1000 of=/dev/null 32768000 bytes transferred in 3.214075 secs (10195157 bytes/sec) $ dd if=/dev/rwd3c bs=32k count=1000 of=/dev/null 32768000 bytes transferred in 3.278695 secs (9994220 bytes/sec) $ dd if=/dev/rda0c bs=32k count=1000 of=/dev/null 32768000 bytes transferred in 5.734632 secs (5714055 bytes/sec) $ dd if=/dev/rsd1c bs=32k count=1000 of=/dev/null 32768000 bytes transferred in 8.893227 secs (3684602 bytes/sec) Looks good for the IDE drives, doesn't it? They say, though, that SCSI drives work better with multiple requests outstanding... $ dd if=/dev/rsd0c bs=32k count=1000 of=/dev/null & dd if=/dev/rsd1c bs=32k count=1000 of=/dev/null [3] 20705 32768000 bytes transferred in 9.940641 secs (3296367 bytes/sec) 32768000 bytes transferred in 12.121225 secs (2703357 bytes/sec) $ dd if=/dev/rsd0c bs=32k count=1000 of=/dev/null & dd if=/dev/rsd1c bs=32k count=1000 of=/dev/null 32768000 bytes transferred in 9.940080 secs (3296553 bytes/sec) 32768000 bytes transferred in 12.080951 secs (2712369 bytes/sec) Well, that doesn't look spectacular. What about the IDE drives (both on the same controller, wdc1): $ dd if=/dev/rwd2c bs=32k count=1000 of=/dev/null & dd if=/dev/rwd3c bs=32k count=1000 of=/dev/null 32768000 bytes transferred in 3.710713 secs (8830648 bytes/sec) 32768000 bytes transferred in 3.711320 secs (8829204 bytes/sec) $ dd if=/dev/rwd2c bs=32k count=1000 of=/dev/null & dd if=/dev/rwd3c bs=32k count=1000 of=/dev/null 32768000 bytes transferred in 3.737548 secs (8767245 bytes/sec) 32768000 bytes transferred in 3.729290 secs (8786659 bytes/sec) I must say, I'm surprised. This makes it look like there's more of a performance hit with concurrent requests on SCSI than on IDE. Let's look at the performance hits as a percentage (there's some guesswork which is which, of course, but only a little): alone 2 together % drop wd2 10.2 8.8 14 wd3 10.0 8.8 12 da0 5.7 3.3 42 da1 3.7 2.7 23 OK, the controller I have isn't the newest, but there's not exactly a lot of data crossing: even with the two disks transferring by themselves, they're transferring less data than a single DHEA drive. Can anybody else think of a reason for this? I have a 2940 Ultra ("ahc0: rev 0x00 int a irq 14 on pci0.17.0") in another machine. The disks aren't Ultra SCSI; is there any reason to think it will perform better? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 22:48:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08628 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 22:48:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08605 for ; Tue, 10 Nov 1998 22:48:04 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA21059; Wed, 11 Nov 1998 15:16:30 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id PAA20597; Wed, 11 Nov 1998 15:16:28 +1030 (CST) Message-ID: <19981111151628.J20374@freebie.lemis.com> Date: Wed, 11 Nov 1998 15:16:28 +1030 From: Greg Lehey To: Julian Elischer , Peter Jeremy Cc: hackers@FreeBSD.ORG Subject: Re: SCSI tagged queueing and softupdates References: <98Nov11.084659est.40344@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Julian Elischer on Tue, Nov 10, 1998 at 08:16:08PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 10 November 1998 at 20:16:08 -0800, Julian Elischer wrote: > On Wed, 11 Nov 1998, Peter Jeremy wrote: > >> AFAIK, SCSI tagged queueing is the default in 3.0 (via cam or inside >> the ahc driver). (This was optionally enabled via AHC_TAGENABLE in 2.x >> and the 3.0 man page still describes this option, although the option >> is gone). >> >> According to the description, tagged queueing allows a SCSI device to >> re-order pending I/O requests in order to improve throughput. Soft >> updates, on the other hand, rely on the correct sequencing of physical >> writes to ensure that the disk metadata is consistent. >> >> Is this a real issue? If so, it would seem that tagged queueing must >> be disabled (at least for writes) when softupdates are enabled. It's >> not obvious to me that this is currently done (or even easy to do). >> >> Comments please. > > transactions can be reorderd AS LONG AS the drive does not report a > perticular transaction to be completed before it really is.. As long as you define "transaction" correctly. SCSI-level transactions must often be completed in order. I rely on this (and the associated B_ORDERED flag in the buffer header) to ensure consistency in Vinum. > Soft updates will not schedule any IO that depends on an uncompleted IO > operation. So therefore all operations that have been 'passed to the > driver' are not dependent on each other (by definition) Doesn't this slow the whole thing down? Or is that what's behind B_ORDERED? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 22:53:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09302 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 22:53:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09290 for ; Tue, 10 Nov 1998 22:53:31 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from celeris (56k-port4004.ime.net [209.90.195.14]) by Loki.orland.u91.k12.me.us (8.9.1/8.8.8-Loki) with SMTP id BAA00768; Wed, 11 Nov 1998 01:52:33 -0500 (EST) (envelope-from netmonger@genesis.ispace.com) X-Server-ID: Loki.orland.u91.k12.me.us, OCSNet - Orland Maine USA X-Coord-Name: Drew "Droobie" Baxter, OneNetwork Exchange X-Coord-Addr: Droobie@Openlink.orland.me.us X-Coord-Pager: USA: 207-471-2719, http://pagedroo.orland.me.us Message-Id: <4.1.19981111014829.00a6eee0@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 11 Nov 1998 01:50:22 -0500 To: john cooper , grog@lemis.com, hackers@FreeBSD.ORG, mike@smith.net.au, ticso@cicely.de From: Drew Baxter Subject: Re: SCSI vs. DMA33.. Cc: john@isi.co.jp In-Reply-To: <98Nov11.134648jst.21907@ns.isi.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:41 PM 11/11/98 +0900, john cooper wrote: > >Hi, > Just wondering if anyone has any _objective_ opinion on >the performance of say wide SCSI2 vs. DMA33 IDE drives [running >on contemporary motherboards]. The theoretical throughputs of >40MBs and 33MBs don't tell me a whole lot. I know SCSI was the >choice for performance in the past, however I'm curious what >others are seeing in actual usage these days. > >Thanks, > >-john Well I'm running Windows 95 on this one, and it has 2 UDMA (6.4 and 7.0 gig Maxtor UDMA-2) drives, which run VERY fast (As a matter of fact, CEQuadrat's WinOnCD says I could use 8x+ writer from data on them), which is a better thing than my older EIDE drives. At the same time, my 4.3gig Fujitsu SCSI2 on the integrated AIC-7895 does an ok job as well for throughput. So I'd say they're relatively close in performance for my A/V requirements and all, individual results will vary. Many people say Maxtor drives are crap, but I have had no problems with mine and they've been burnt in, dropped, thrown, and various other things. --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange 207-942-0275 http://www.droo.orland.me.us My Latest Kernel: FreeBSD 3.0-CURRENT (ONEEX) #14: Mon Oct 19 22:36:58 EDT 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 22:54:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09578 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 22:54:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.whistle.com (gatekeeper.whistle.com [207.76.204.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09573 for ; Tue, 10 Nov 1998 22:54:55 -0800 (PST) (envelope-from julian@whistle.com) Received: (from smap@localhost) by gatekeeper.whistle.com (8.8.8/8.8.7) id VAA23921 for ; Tue, 10 Nov 1998 21:08:55 -0800 (PST) (envelope-from julian@whistle.com) Received: from alpo.whistle.com(unknown 207.76.204.38) by gatekeeper.whistle.com via smap (V2.0) id xma023919; Tue, 10 Nov 98 21:08:53 -0800 Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA26748; Tue, 10 Nov 1998 20:54:46 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdl26745; Wed Nov 11 04:54:38 1998 Date: Tue, 10 Nov 1998 20:54:05 -0800 (PST) From: Julian Elischer To: Greg Lehey cc: Peter Jeremy , hackers@FreeBSD.ORG Subject: Re: SCSI tagged queueing and softupdates In-Reply-To: <19981111151628.J20374@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Nov 1998, Greg Lehey wrote: > On Tuesday, 10 November 1998 at 20:16:08 -0800, Julian Elischer wrote: > > > Soft updates will not schedule any IO that depends on an uncompleted IO > > operation. So therefore all operations that have been 'passed to the > > driver' are not dependent on each other (by definition) > > Doesn't this slow the whole thing down? Or is that what's behind > B_ORDERED? Softupdates doesn't use B_ORDERED no, it can write out a directory block even if there are uncompleted inode writes it is waiting on... it fabricates a directory block with those entries, marked as invalid and writes out that copy instead. When the inode writes are completed, it will schedule a rewrite to the disk of the completed block. it's incredibally sneaky that way.. same for inodes. etc. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 22:58:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10437 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 22:58:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10431 for ; Tue, 10 Nov 1998 22:58:46 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id WAA18122; Tue, 10 Nov 1998 22:58:03 -0800 (PST) (envelope-from dillon) Date: Tue, 10 Nov 1998 22:58:03 -0800 (PST) From: Matthew Dillon Message-Id: <199811110658.WAA18122@apollo.backplane.com> To: john cooper Cc: grog@lemis.com, hackers@FreeBSD.ORG, mike@smith.net.au, ticso@cicely.de, john@isi.co.jp Subject: Re: SCSI vs. DMA33.. References: <98Nov11.134648jst.21907@ns.isi.co.jp> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The biggest issue with IDE is that it's a serialized interface. You can only run one command at a time to one device at a time and you have to wait for it to complete before you can run another command to the same device or another device. The throughput is therefore irrelevant, since most disks can't do more then 9 MBytes/sec off the platter anyway (note: the latest bleeding edge IBM drives can apparently do 20 MBytes/sec or better off the platter). IDE also isn't too hot when it comes to bad sector remapping or multiple devices, which is why most PC's come with two separate IDE busses these days. One for the CDRom, and one for the disk, nor is IDE necessarily reliable when sharing a bus in a master-slave configuration, even if both drives are the same brand. On the otherhand, a 40 MByte/sec SCSI bus with four 9 MByte/sec drives on it can actually be doing 36 MBytes/sec on the bus. Since, typically, anything approaching that kind of bandwidth is also an indication for the need for performance, it seems silly to me to even begin to compare IDE with SCSI no matter what the DMA transfer bandwidth of the IDE device is. I suppose if you never needed to seek the drive it might matter, but the moment you start needing to seek the drive the platter bandwidth goes to pot. The best a fully saturated randomly seeking disk can do is typically less then 2 MBytes/sec using 16K reads, and it doesn't get much better with larger reads. It takes truely large reads (256 KBytes or larger) between seeks to even approach the platter's bandwidth. The size of the disk in the seeking case is irrelevant, really, because voice-coil technology has not gone through the same insane technology leaps that the disk heads have gone through. IDE is still useful when you don't need performance, and I would say that 80% of the server installations these days fall into the 'don't need the performance' category. My home machines are a mix of IDE and SCSI, but all of the rack mount FreeBSD boxes in BEST's machine room are SCSI-only. If you do need performance, you go with SCSI. -Matt : :Hi, : Just wondering if anyone has any _objective_ opinion on :the performance of say wide SCSI2 vs. DMA33 IDE drives [running :on contemporary motherboards]. The theoretical throughputs of :40MBs and 33MBs don't tell me a whole lot. I know SCSI was the :choice for performance in the past, however I'm curious what :others are seeing in actual usage these days. : :Thanks, : :-john : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 23:01:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10959 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 23:01:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10941 for ; Tue, 10 Nov 1998 23:01:03 -0800 (PST) (envelope-from tony@dell.com) Received: from ant (ant.us.dell.com [143.166.12.34]) by bugs.us.dell.com (8.8.8/8.8.8) with SMTP id AAA09797; Wed, 11 Nov 1998 00:25:44 -0600 (CST) (envelope-from tony@dell.com) Message-Id: <3.0.3.32.19981111002542.00752be4@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.3 (32) Date: Wed, 11 Nov 1998 00:25:42 -0600 To: Terry Lambert From: Tony Overfield Subject: disk sector ordering (Was: Reading/writing /usr/ports is VERY slow) Cc: hackers@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Sep 1998 01:08:15 +0000 (GMT), Terry Lambert said: >Specifically, most modern disks record tracks in reverse sector >order, and as soon as you seek to the track, they start reading >(and buffering data) until they hit the sector in the track that >you were actually seeking to find. Sorry about taking the side-track with such an old message, but I've been trying to figure out what you said here and I just don't get it. Can you explain this? Is there some reason you want to avoid the concurrency you normally achieve by having the sectors in the normal order? - Tony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 23:02:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11251 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 23:02:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA11240 for ; Tue, 10 Nov 1998 23:02:19 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from celeris (56k-port4004.ime.net [209.90.195.14]) by Loki.orland.u91.k12.me.us (8.9.1/8.8.8-Loki) with SMTP id CAA00882; Wed, 11 Nov 1998 02:01:43 -0500 (EST) (envelope-from netmonger@genesis.ispace.com) X-Server-ID: Loki.orland.u91.k12.me.us, OCSNet - Orland Maine USA X-Coord-Name: Drew "Droobie" Baxter, OneNetwork Exchange X-Coord-Addr: Droobie@Openlink.orland.me.us X-Coord-Pager: USA: 207-471-2719, http://pagedroo.orland.me.us Message-Id: <4.1.19981111015237.00ab3ee0@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 11 Nov 1998 01:59:31 -0500 To: Greg Lehey , john cooper , hackers@FreeBSD.ORG, mike@smith.net.au, ticso@cicely.de From: Drew Baxter Subject: Re: SCSI vs. DMA33.. In-Reply-To: <19981111162000.O20374@freebie.lemis.com> References: <98Nov11.134648jst.21907@ns.isi.co.jp> <98Nov11.134648jst.21907@ns.isi.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:20 PM 11/11/98 +1030, Greg Lehey wrote: >On Wednesday, 11 November 1998 at 13:41:00 +0900, john cooper wrote: >> >> Hi, >> Just wondering if anyone has any _objective_ opinion on >> the performance of say wide SCSI2 vs. DMA33 IDE drives [running >> on contemporary motherboards]. > >Depends on what you mean by "objective". > >> The theoretical throughputs of 40MBs and 33MBs don't tell me a whole >> lot. I know SCSI was the choice for performance in the past, >> however I'm curious what others are seeing in actual usage these >> days. > >SCSI is still the performance choice, but the field is closer now. I >have five drives on my main machine: > >wd0: 1223MB (2504880 sectors), 2485 cyls, 16 heads, 63 S/T, 512 B/S >wd2: 6197MB (12692736 sectors), 12592 cyls, 16 heads, 63 S/T, 512 B/S >ide_pci: generic_dmainit 0170:1: warning, IDE controller timing not set >wdc1: unit 1 (wd3): , DMA, 32-bit, multi-block-16 >wd3: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S >ahc0: rev 0x03 int a irq 11 on pci0.9.0 >ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs >da0 at ahc0 bus 0 target 0 lun 0 >da0: Fixed Direct Access SCSI2 device >da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled >da0: 2063MB (4226725 512 byte sectors: 64H 32S/T 2063C) >da1 at ahc0 bus 0 target 2 lun 0 >da1: Fixed Direct Access SCSI2 device >da1: 3.300MB/s transfers, Tagged Queueing Enabled >da1: 4096MB (8388608 512 byte sectors: 64H 32S/T 4096C) > >I'm running 3.0-CURRENT (post-RELEASE), and as you can see Ultra DMA >is enabled on the IDE drives. Here's what I get transferring 32 MB >from each raw device: > >$ dd if=/dev/rwd0c bs=32k count=1000 of=/dev/null >32768000 bytes transferred in 6.938876 secs (4722379 bytes/sec) >$ dd if=/dev/rwd2c bs=32k count=1000 of=/dev/null >32768000 bytes transferred in 3.214075 secs (10195157 bytes/sec) >$ dd if=/dev/rwd3c bs=32k count=1000 of=/dev/null >32768000 bytes transferred in 3.278695 secs (9994220 bytes/sec) >$ dd if=/dev/rda0c bs=32k count=1000 of=/dev/null >32768000 bytes transferred in 5.734632 secs (5714055 bytes/sec) >$ dd if=/dev/rsd1c bs=32k count=1000 of=/dev/null >32768000 bytes transferred in 8.893227 secs (3684602 bytes/sec) > >Looks good for the IDE drives, doesn't it? They say, though, that >SCSI drives work better with multiple requests outstanding... > >$ dd if=/dev/rsd0c bs=32k count=1000 of=/dev/null & dd if=/dev/rsd1c bs=32k >count=1000 of=/dev/null >[3] 20705 >32768000 bytes transferred in 9.940641 secs (3296367 bytes/sec) >32768000 bytes transferred in 12.121225 secs (2703357 bytes/sec) >$ dd if=/dev/rsd0c bs=32k count=1000 of=/dev/null & dd if=/dev/rsd1c bs=32k >count=1000 of=/dev/null >32768000 bytes transferred in 9.940080 secs (3296553 bytes/sec) >32768000 bytes transferred in 12.080951 secs (2712369 bytes/sec) > >Well, that doesn't look spectacular. What about the IDE drives (both >on the same controller, wdc1): > >$ dd if=/dev/rwd2c bs=32k count=1000 of=/dev/null & dd if=/dev/rwd3c bs=32k >count=1000 of=/dev/null >32768000 bytes transferred in 3.710713 secs (8830648 bytes/sec) >32768000 bytes transferred in 3.711320 secs (8829204 bytes/sec) >$ dd if=/dev/rwd2c bs=32k count=1000 of=/dev/null & dd if=/dev/rwd3c bs=32k >count=1000 of=/dev/null >32768000 bytes transferred in 3.737548 secs (8767245 bytes/sec) >32768000 bytes transferred in 3.729290 secs (8786659 bytes/sec) > >I must say, I'm surprised. This makes it look like there's more of a >performance hit with concurrent requests on SCSI than on IDE. Let's >look at the performance hits as a percentage (there's some guesswork >which is which, of course, but only a little): > > alone 2 together % drop >wd2 10.2 8.8 14 >wd3 10.0 8.8 12 >da0 5.7 3.3 42 >da1 3.7 2.7 23 > >OK, the controller I have isn't the newest, but there's not exactly a >lot of data crossing: even with the two disks transferring by >themselves, they're transferring less data than a single DHEA drive. >Can anybody else think of a reason for this? I have a 2940 Ultra >("ahc0: rev 0x00 int a irq 14 on >pci0.17.0") in another machine. The disks aren't Ultra SCSI; is there >any reason to think it will perform better? > >Greg I have the 2940U card, I found the integrated AIC-7895 on my mainboard (Dual UltraSCSI Wide) performed better for throughput. Since my applications don't require much better than the UDMA drives anyway, I can't say I'm taking advantage of it. Then again, I'm not taking advantage of the 2 processors on the board (Windows 95's lack of SMP support). Eventually I'll probably throw a dual-boot in for FreeBSD, but I have a workhorse PII for that already. I find minimum grind when doing network applications across the house on either. My Fujitsu SCSI 4.3gig gets used mostly for the bootup and OS operation, the UDMA drives are used for public file sharing and caching and things like that. The UDMA 7.0gig replaced a regular EIDE Maxtor 3.5 gig. I will say that this is HANDS DOWN a faster drive. the 3.5 gig would not succeed in above a 2X CD-R write (for caching according to CEQuadrat's SpeedOMeter) and that's with an empty partition. The 7.0gig can be half full with thousands of files, and it scores to be reliable up to and past 8x CD-R speeds. I'd say all in all, UDMA33 is significantly better than the older EIDE drives. Whether it is better than SCSI or not is yet to be seen. But my Fujitsu was probably a good 400+ dollars, and my 7.0gig Maxtor was 197 (and then 30 bucks off rebate). I can't argue with a price like that, the speed is an added bonus. My FreeBSD box uses an older BIOSTAR 8500TUD that doesn't contain a UDMA chip. It performs incredibly well with a 2.7gig Maxtor (EIDE) and a 1.6gig Samsung (EIDE). The thing is running 17 Vservs on a PII-333, and experiences a peak load of probably .16, and that's rare. It all depends on how you use it I guess. I do Photoshop on the WIN95 machine, and also video editing. Runs flawless using either the 2nd partition of the 4.3, or any of the UDMA partitions.. --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange 207-942-0275 http://www.droo.orland.me.us My Latest Kernel: FreeBSD 3.0-CURRENT (ONEEX) #14: Mon Oct 19 22:36:58 EDT 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 23:22:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13522 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 23:22:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13514 for ; Tue, 10 Nov 1998 23:22:29 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id AAA19870; Wed, 11 Nov 1998 00:22:10 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd019812; Wed Nov 11 00:22:02 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id AAA04416; Wed, 11 Nov 1998 00:21:56 -0700 (MST) From: Terry Lambert Message-Id: <199811110721.AAA04416@usr01.primenet.com> Subject: Re: Malloc in the kernel To: dg@root.com Date: Wed, 11 Nov 1998 07:21:56 +0000 (GMT) Cc: tlambert@primenet.com, grog@lemis.com, Reinier.Bezuidenhout@KryptoKom.DE, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199811090915.BAA09637@root.com> from "David Greenman" at Nov 9, 98 01:15:16 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> > In general, the kernel is better at deciding what memory it needs > >> > when it needs it than a kernel code author. You either trust > >> > the locality of reference model upon which VM systems are based, > >> > or you don't. > >> > >> Assuming that fits his needs, what's the answer? > > > >vm_pager_allocate(OBJT_SWAP, 0, OFF_TO_IDX(size), VM_PROT_DEFAULT, 0); > > Bzzt! Wrong! > > ...but you could use kmem_alloc_pageable() (or call vm_map_find() directly) > to allocate demand-zero, pageable, kernel memory. Hmmm.... Better fix /sys/kern/sysv_shm.c then, since that's where I cribbed the code from... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 10 23:52:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17069 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 23:52:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA17056 for ; Tue, 10 Nov 1998 23:52:07 -0800 (PST) (envelope-from ticso@cicely5.cicely.de) Received: from cicely.cicely.de (cicely.de [194.231.9.142]) by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id IAA07919; Wed, 11 Nov 1998 08:51:45 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [10.1.1.7]) by cicely.cicely.de (8.8.8/8.8.8) with ESMTP id IAA18365; Wed, 11 Nov 1998 08:52:01 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.9.0/8.9.0) id IAA27224; Wed, 11 Nov 1998 08:51:52 +0100 (CET) Message-ID: <19981111085152.55040@cicely.de> Date: Wed, 11 Nov 1998 08:51:52 +0100 From: Bernd Walter To: Greg Lehey , Mike Smith , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <199811100638.WAA00637@dingo.cdrom.com> <19981111103028.L18183@freebie.lemis.com> <19981111040654.07145@cicely.de> <19981111134546.D20374@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19981111134546.D20374@freebie.lemis.com>; from Greg Lehey on Wed, Nov 11, 1998 at 01:45:46PM +1030 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 11, 1998 at 01:45:46PM +1030, Greg Lehey wrote: > On Wednesday, 11 November 1998 at 4:06:54 +0100, Bernd Walter wrote: > > On Wed, Nov 11, 1998 at 10:30:28AM +1030, Greg Lehey wrote: > >> On Monday, 9 November 1998 at 22:38:04 -0800, Mike Smith wrote: > > [...] > > One point is that is doesn't aggregate transactions to the lower drivers. > > When using stripes of one sector it's doing no more than one sector > > transactions to the HDDs so at least with the old scsi driver there's no > > linear performance increase with it. That's the same with ccd. > > Correct, at least as far as Vinum goes. The rationale for this is > that, with significant extra code, Vinum could aggregate transfers > *from a single user request* in this manner. But any request that > gets this far (in other words, runs for more than a complete stripe) > is going to convert one user request into n disk requests. There's no > good reason to do this, and the significant extra code would just chop > off the tip of the iceberg. The solution is in the hands of the user: > don't use small stripe sizes. I recommend a stripe of between 256 and > 512 kB. That's good for random performance increase - but for linear access a smaler stripe size is the only way to get the maximum performance of all disks together. I agree - In general bigger stripes are better for Multiitasking Systems. > > >>> There was an interesting symptom observed in striped mode, where the > >>> disks seemed to have a binarily-weighted access pattern. > >> > >> Can you describe that in more detail? Maybe I should consider > >> relating stripe size to cylinder group size. > > > > I always saw the same and I'm shure that the cylinder groups are > > mostly placed on one disk each. > > I think you mean the superblocks. It depends on the cylinder group > size. I haven't thought about this yet, but I may well do so. You are right - I mean super-blocks and inode areas of the c-groups. > [...] > > I never checked if it's possible to do a stripe on differend sized > > disks as ccd can do. > > Do you mean 'different sized disks' or 'different sized subdisks'? > Different sized disks are no problem, of course, but 'different sized > subdisks' are. I don't think that ccd could do this either; it would > leave a hole in the volume. > I mean 'different sized subdisks'. CCD has the interleave description table for doing such things. It' described in sys/ccdvar.h . Say you have 3 100M subdisks and 2 200M Subdisks then CCD make a stripe on the first 500M with all 5 disks and on the last 200M with the remaining both. > > And ccd is more integrated into the rest of the system but the other > > things are working at least as good as with ccd. > > In which way is it better integrated? It's available in exactly the > same way as ccd (unless, like you, you want RAID-5 :-) What I mean is - you edit /etc/ccd.conf and setup the partitions, ... Finaly you place an entry in /etc/fstab. You don't have to worry about loading an lkm or fsck, ... Maybe I missed anything - but the last time I wasn't able to find any point for vinum in any rc file. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 00:06:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18501 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 00:06:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18466 for ; Wed, 11 Nov 1998 00:06:29 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id SAA21733; Wed, 11 Nov 1998 18:35:47 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id SAA21087; Wed, 11 Nov 1998 18:35:46 +1030 (CST) Message-ID: <19981111183546.D20849@freebie.lemis.com> Date: Wed, 11 Nov 1998 18:35:46 +1030 From: Greg Lehey To: Bernd Walter , Mike Smith , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <199811100638.WAA00637@dingo.cdrom.com> <19981111103028.L18183@freebie.lemis.com> <19981111040654.07145@cicely.de> <19981111134546.D20374@freebie.lemis.com> <19981111085152.55040@cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981111085152.55040@cicely.de>; from Bernd Walter on Wed, Nov 11, 1998 at 08:51:52AM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 11 November 1998 at 8:51:52 +0100, Bernd Walter wrote: > On Wed, Nov 11, 1998 at 01:45:46PM +1030, Greg Lehey wrote: >> On Wednesday, 11 November 1998 at 4:06:54 +0100, Bernd Walter wrote: >>> On Wed, Nov 11, 1998 at 10:30:28AM +1030, Greg Lehey wrote: >>>> On Monday, 9 November 1998 at 22:38:04 -0800, Mike Smith wrote: >>> [...] >>> One point is that is doesn't aggregate transactions to the lower drivers. >>> When using stripes of one sector it's doing no more than one sector >>> transactions to the HDDs so at least with the old scsi driver there's no >>> linear performance increase with it. That's the same with ccd. >> >> Correct, at least as far as Vinum goes. The rationale for this is >> that, with significant extra code, Vinum could aggregate transfers >> *from a single user request* in this manner. But any request that >> gets this far (in other words, runs for more than a complete stripe) >> is going to convert one user request into n disk requests. There's no >> good reason to do this, and the significant extra code would just chop >> off the tip of the iceberg. The solution is in the hands of the user: >> don't use small stripe sizes. I recommend a stripe of between 256 and >> 512 kB. > > That's good for random performance increase - but for linear access a smaler > stripe size is the only way to get the maximum performance of all > disks together. No, the kind of stripe size you're thinking about will almost always degrade performance. If you're accessing large quantities of data in a linear fashion, you'll be reading 60 kB at a time. If each of these reads requires accessing more than one disk, you'll kill performance. Try it: I have. >>> I never checked if it's possible to do a stripe on differend sized >>> disks as ccd can do. >> >> Do you mean 'different sized disks' or 'different sized subdisks'? >> Different sized disks are no problem, of course, but 'different sized >> subdisks' are. I don't think that ccd could do this either; it would >> leave a hole in the volume. > > I mean 'different sized subdisks'. > CCD has the interleave description table for doing such things. > It' described in sys/ccdvar.h . > Say you have 3 100M subdisks and 2 200M Subdisks then CCD make a stripe > on the first 500M with all 5 disks and on the last 200M with the remaining both. Ah, *that*'s why it has an interleave table. Score one for ccd. >>> And ccd is more integrated into the rest of the system but the other >>> things are working at least as good as with ccd. >> >> In which way is it better integrated? It's available in exactly the >> same way as ccd (unless, like you, you want RAID-5 :-) > > What I mean is - you edit /etc/ccd.conf and setup the partitions, ... > Finaly you place an entry in /etc/fstab. OK, with vinum you edit /etc/vinumconf and setup the partitions, then you place an entry in /etc/fstab. Not much difference. OK, /etc/rc.conf doesn't currently know about Vinum, and that's a thing I can look at. > You don't have to worry about loading an lkm or fsck, ... Well, you either load an LKM or build a kernel. And there's no difference between ccd and Vinum as regards the necessity for fsck. > Maybe I missed anything - but the last time I wasn't able to find any > point for vinum in any rc file. Yes, as I said, that's a valid point. I'll sort it out Real Soon Now. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 00:21:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA19723 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 00:21:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA19711 for ; Wed, 11 Nov 1998 00:21:08 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id JAA01536; Wed, 11 Nov 1998 09:16:01 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199811110816.JAA01536@freebsd.dk> Subject: Re: SCSI vs. DMA33.. In-Reply-To: <98Nov11.134648jst.21907@ns.isi.co.jp> from john cooper at "Nov 11, 1998 1:41: 0 pm" To: john@isi.co.jp (john cooper) Date: Wed, 11 Nov 1998 09:16:01 +0100 (CET) Cc: grog@lemis.com, hackers@FreeBSD.ORG, mike@smith.net.au, ticso@cicely.de, john@isi.co.jp X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems john cooper wrote: > > Hi, > Just wondering if anyone has any _objective_ opinion on > the performance of say wide SCSI2 vs. DMA33 IDE drives [running > on contemporary motherboards]. The theoretical throughputs of > 40MBs and 33MBs don't tell me a whole lot. I know SCSI was the > choice for performance in the past, however I'm curious what > others are seeing in actual usage these days. Well, at my ISP we run 4 NFS servers that handels all mail/web/misc stuff for the users, needless to say they are "used" alot. Those 4 machines are P233/64M PC's with 4*4.3G UDMA IDE drives in them, configured in pairs as mirrors with ccd. They perform wonderfully. And the price cannot be beaten too :) I must say that the newer UDMA IDE drives has come a long way lately, they perform at least as good as their SCSI counterparts. The only thing that they cannot do is overlapping commands, but given EIDE's much smaller cmd overhead, I'm not sure this has any significance at all in practice. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 00:25:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA20087 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 00:25:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA20074 for ; Wed, 11 Nov 1998 00:25:54 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id BAA13324; Wed, 11 Nov 1998 01:25:37 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd013316; Wed Nov 11 01:25:37 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id BAA06296; Wed, 11 Nov 1998 01:25:31 -0700 (MST) From: Terry Lambert Message-Id: <199811110825.BAA06296@usr02.primenet.com> Subject: Re: Supporting more than FD_SETSIZE fd's To: nate@mt.sri.com (Nate Williams) Date: Wed, 11 Nov 1998 08:25:31 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199811091734.KAA04752@mt.sri.com> from "Nate Williams" at Nov 9, 98 10:34:00 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I looked through the handbook and the FAQ and didn't find anything, so > hopefully someone can help me out. > > I need to support more than the default 255 FD's in an application (the > JDK for what it's worth). To be portable, the code uses fd_set as > defined in . Unfortunately, unless I redefine FD_SETSIZE > in every file that uses it, I still have a hard-limit on the number of > FD's the application can use. > > Is there any 'portable' way of getting around this? Redefine FD_SETSIZE. If you don't wwant to do it in every file that uses it, then either do it in the header file itself, or add -DFD_SETSIZE=1024 to CFLAGS. > I'd really like to > have it use whichever open FD that the limit allows, but I know now way > of having this happen? I can't really parse this. The "the limit allows" value is based on how many contiguous bits there are in an fd_set, which is based on the value of FD_SETSIZE at the time the fd_set is declared. Basically, the first argument is how many bits into the fd_set that select is supposed to index looking for FD_ISSET bits to select fd's to select on... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 00:27:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA20235 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 00:27:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA20228 for ; Wed, 11 Nov 1998 00:27:28 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id BAA02942; Wed, 11 Nov 1998 01:27:11 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd002926; Wed Nov 11 01:27:08 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id BAA06373; Wed, 11 Nov 1998 01:27:06 -0700 (MST) From: Terry Lambert Message-Id: <199811110827.BAA06373@usr02.primenet.com> Subject: Re: linux software installation and uname To: sgk@troutmask.apl.washington.edu (Steve Kargl) Date: Wed, 11 Nov 1998 08:27:05 +0000 (GMT) Cc: rivers@dignus.com, hackers@FreeBSD.ORG In-Reply-To: <199811091756.JAA10389@troutmask.apl.washington.edu> from "Steve Kargl" at Nov 9, 98 09:56:33 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In my particular instance, I was able to persuade the vendor > > that it was artificially limiting its customer base. And thus, > > the uname check was changed to accept either "FreeBSD" or "Linux". > > Perhaps you could do the same with the Lahey people. > > Been there. PGI has no intention at this time to support FreeBSD > because they do not have sufficient tech. support for FreeBSD. This is not a "support FreeBSD" issue, it's a "don't check uname and reject a ``FreeBSD'' return value" issue. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 00:31:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA20525 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 00:31:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA20518 for ; Wed, 11 Nov 1998 00:31:21 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id BAA14128; Wed, 11 Nov 1998 01:30:59 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd014122; Wed Nov 11 01:30:57 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id BAA06529; Wed, 11 Nov 1998 01:30:57 -0700 (MST) From: Terry Lambert Message-Id: <199811110830.BAA06529@usr02.primenet.com> Subject: Re: linux software installation and uname To: sgk@troutmask.apl.washington.edu (Steve Kargl) Date: Wed, 11 Nov 1998 08:30:57 +0000 (GMT) Cc: crossd@cs.rpi.edu, jkh@time.cdrom.com, nate@mt.sri.com, hackers@FreeBSD.ORG In-Reply-To: <199811091947.LAA11148@troutmask.apl.washington.edu> from "Steve Kargl" at Nov 9, 98 11:47:56 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Here is the nice little uname test from the vendor's install script: > > # what type of target? > if test -x /usr/bin/uname ; then > uname=/usr/bin/uname > elif test -x /bin/uname ; then > uname=/bin/uname > else > # Never seen it anywhere but /bin or /usr/bin, so hopefully it's > # in $PATH already. > type uname > /dev/null 2>&1 > if test $? -ne 0 ; then > echo "install: uname not found in \$PATH environment variable" > quit > else > uname=uname > fi > fi Any you don't path this as part of the "port" you made for the compiler? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 00:37:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA21093 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 00:37:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA21088 for ; Wed, 11 Nov 1998 00:37:19 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id BAA05274; Wed, 11 Nov 1998 01:37:02 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd005261; Wed Nov 11 01:36:57 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id BAA06729; Wed, 11 Nov 1998 01:36:56 -0700 (MST) From: Terry Lambert Message-Id: <199811110836.BAA06729@usr02.primenet.com> Subject: Re: text mode screen grabber? To: nik@nothing-going-on.demon.co.uk (Nik Clayton) Date: Wed, 11 Nov 1998 08:36:56 +0000 (GMT) Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, nik@nothing-going-on.demon.co.uk, hackers@FreeBSD.ORG In-Reply-To: <19981109205920.58410@nothing-going-on.org> from "Nik Clayton" at Nov 9, 98 08:59:20 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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > True enough. I hasten to point out that I'm not trying to write something > for wide distribution (at the moment). This is just something to make > the FreeBSD Documentation a little more user friendly. > > After poking a bit more through syscons.c, I think I should be able > to implement something like "press 'D' to dump the current screen to > /tmp/syscons.dump" or similar. Or implement ESC [ 2 i processing into syscons, and when it gets the ESC [ 2 i, have it stuff the input buffer with the screen contents. Then: write( 1, "\033[2i", 4); And read the data it sends back (it will send escape sequences to represent bold, color changes from the default, etc.) until you have read "rows" worth of "\n"'s. Pretty trivial to implement both the ESC [ 2 i in syscons, and the code in the program that needs to read the screen. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 00:41:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA21421 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 00:41:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA21416 for ; Wed, 11 Nov 1998 00:41:57 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id BAA00453; Wed, 11 Nov 1998 01:41:34 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd000426; Wed Nov 11 01:41:32 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id BAA06929; Wed, 11 Nov 1998 01:41:31 -0700 (MST) From: Terry Lambert Message-Id: <199811110841.BAA06929@usr02.primenet.com> Subject: Re: linux software installation and uname To: eivind@yes.no (Eivind Eklund) Date: Wed, 11 Nov 1998 08:41:31 +0000 (GMT) Cc: sgk@troutmask.apl.washington.edu, hackers@FreeBSD.ORG In-Reply-To: <19981109225310.34189@follo.net> from "Eivind Eklund" at Nov 9, 98 10:53:10 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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You'll never pick up /compat/linux/bin/uname unless you delete/rename > > /usr/bin/uname. > > Eh - I'm pretty sure /compat/linux is searched _before_ /. For all > syscalls. This is hardcoded in the linux emulator in the kernel. Sure. /compat/linux/bin/sh was searched for on the exec of /bin/sh in order to run the shell script. Then the /bin/sh from FreeBSD was loaded. Then the /compat/linux directory was ignore as the FreeBSD binary /bin/sh exec'ed the FreeBSD /bin/uname program. > So if /compat/linux/bin/uname exists, that will be run in preference > to /bin/uname for anything Linux-emulated. We might still need a way > of saying that a shell script is Linux-emulated, though - probably by > running it through /compat/linux/bin/sh :-) > > Besides this, vendors should be pressured to test for uname in the > right way to make their Linux software also work on FreeBSD. Yes. But more to the point, the patches applied to the program in the "make install" from the ports Makefile for the thing should either install a /compat/linux/bin/uname as one of the dependencies to the install target (for the probable benefit of the license manager software) and.or modify the shell script to add "FreeBSD" as a viable install target, using the Linux binaries. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 00:51:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22124 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 00:51:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22119 for ; Wed, 11 Nov 1998 00:51:19 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id BAA17744; Wed, 11 Nov 1998 01:50:50 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd017726; Wed Nov 11 01:50:43 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id BAA07501; Wed, 11 Nov 1998 01:50:40 -0700 (MST) From: Terry Lambert Message-Id: <199811110850.BAA07501@usr02.primenet.com> Subject: Re: linux software installation and uname To: sgk@troutmask.apl.washington.edu (Steve Kargl) Date: Wed, 11 Nov 1998 08:50:40 +0000 (GMT) Cc: joelh@gnu.org, dfr@nlsystems.com, sos@freebsd.dk, n@nectar.com, nate@mt.sri.com, kkennawa@physics.adelaide.edu.au, dnelson@emsphone.com, rivers@dignus.com, hackers@FreeBSD.ORG In-Reply-To: <199811110512.VAA01354@troutmask.apl.washington.edu> from "Steve Kargl" at Nov 10, 98 09:12:44 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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What about install scripts that reside on cdroms? You can't magically > edit a cdrom install script unless unionfs works. /tmp is your friend... sed < /cdrom/install.sh "buncha commands" > /tmp/install.sh Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 00:52:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22228 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 00:52:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22219 for ; Wed, 11 Nov 1998 00:52:49 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id TAA05150; Wed, 11 Nov 1998 19:53:51 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199811110853.TAA05150@cimlogic.com.au> Subject: Re: linux software installation and uname In-Reply-To: <199811110830.BAA06529@usr02.primenet.com> from Terry Lambert at "Nov 11, 98 08:30:57 am" To: tlambert@primenet.com (Terry Lambert) Date: Wed, 11 Nov 1998 19:53:51 +1100 (EST) Cc: sgk@troutmask.apl.washington.edu, crossd@cs.rpi.edu, jkh@time.cdrom.com, nate@mt.sri.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > Here is the nice little uname test from the vendor's install script: > > > > # what type of target? > > if test -x /usr/bin/uname ; then > > uname=/usr/bin/uname > > elif test -x /bin/uname ; then > > uname=/bin/uname > > else > > # Never seen it anywhere but /bin or /usr/bin, so hopefully it's > > # in $PATH already. > > type uname > /dev/null 2>&1 > > if test $? -ne 0 ; then > > echo "install: uname not found in \$PATH environment variable" > > quit > > else > > uname=uname > > fi > > fi > > Any you don't path this as part of the "port" you made for the > compiler? What does this sentence mean? I understand each of the words, but I have no idea what the f%$# you are talking about. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 00:54:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22321 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 00:54:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22316 for ; Wed, 11 Nov 1998 00:54:31 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id BAA02812; Wed, 11 Nov 1998 01:54:15 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd002804; Wed Nov 11 01:54:08 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id BAA07678; Wed, 11 Nov 1998 01:54:07 -0700 (MST) From: Terry Lambert Message-Id: <199811110854.BAA07678@usr02.primenet.com> Subject: Re: SCSI tagged queueing and softupdates To: gibbs@narnia.plutotech.com (Justin T. Gibbs) Date: Wed, 11 Nov 1998 08:54:07 +0000 (GMT) Cc: dillon@apollo.backplane.com, hackers@FreeBSD.ORG In-Reply-To: <199811110257.TAA28938@narnia.plutotech.com> from "Justin T. Gibbs" at Nov 10, 98 07:57:31 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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The SCSI command set allows you to flag > > tags for ordered sequencing. > > Yes, but softupdates does not make use of this mechanism even though, > via 'bowrite' it could. I agree on the value of this. But this seems to infringe on the USL patent for "Delayed Ordered Writes". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 01:01:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22755 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 01:01:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22749 for ; Wed, 11 Nov 1998 01:01:14 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id BAA13927; Wed, 11 Nov 1998 01:01:34 -0800 (PST) Message-Id: <199811110901.BAA13927@root.com> To: Terry Lambert cc: grog@lemis.com, Reinier.Bezuidenhout@KryptoKom.DE, freebsd-hackers@FreeBSD.ORG Subject: Re: Malloc in the kernel In-reply-to: Your message of "Wed, 11 Nov 1998 07:21:56 GMT." <199811110721.AAA04416@usr01.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 11 Nov 1998 01:01:34 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >> > In general, the kernel is better at deciding what memory it needs >> >> > when it needs it than a kernel code author. You either trust >> >> > the locality of reference model upon which VM systems are based, >> >> > or you don't. >> >> >> >> Assuming that fits his needs, what's the answer? >> > >> >vm_pager_allocate(OBJT_SWAP, 0, OFF_TO_IDX(size), VM_PROT_DEFAULT, 0); >> >> Bzzt! Wrong! >> >> ...but you could use kmem_alloc_pageable() (or call vm_map_find() directly) >> to allocate demand-zero, pageable, kernel memory. > >Hmmm.... > > >Better fix /sys/kern/sysv_shm.c then, since that's where I cribbed the >code from... sysv_shm.c is a special beast that specifically *avoids* allocating kernel VM for the objects it manages. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 01:07:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23187 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 01:07:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23182 for ; Wed, 11 Nov 1998 01:07:19 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id CAA27014; Wed, 11 Nov 1998 02:06:57 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd026994; Wed Nov 11 02:06:47 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id CAA08497; Wed, 11 Nov 1998 02:06:47 -0700 (MST) From: Terry Lambert Message-Id: <199811110906.CAA08497@usr02.primenet.com> Subject: Re: linux software installation and uname To: jb@cimlogic.com.au (John Birrell) Date: Wed, 11 Nov 1998 09:06:47 +0000 (GMT) Cc: tlambert@primenet.com, sgk@troutmask.apl.washington.edu, crossd@cs.rpi.edu, jkh@time.cdrom.com, nate@mt.sri.com, hackers@FreeBSD.ORG In-Reply-To: <199811110853.TAA05150@cimlogic.com.au> from "John Birrell" at Nov 11, 98 07:53:51 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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Any you don't path this as part of the "port" you made for the ^^^^--- ``patch'' > > compiler? > > What does this sentence mean? I understand each of the words, but I > have no idea what the f%$# you are talking about. I was asking why you didn't just patch the install script as one of the standard patchfiles you applied to the programs from the original vendor when you made the "ports" entry for the program. In other words, when I go to install the thing from FreeBSD 3.0.1 from the sysinstall menu, it should ask me for the CDROM from the program vendor, mount it, copy the install script to /tmp, patch the install script to route around the uname dependency on Linux (preferrably by adding a FreeBSD target, so the patch can be given back to the vendor for the next time they burn CDROMs), and then the install would "just work". I'd do the job, but I don't have a copy of the CDROM. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 01:12:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23678 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 01:12:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23668 for ; Wed, 11 Nov 1998 01:12:40 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id TAA21972; Wed, 11 Nov 1998 19:42:18 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id TAA21168; Wed, 11 Nov 1998 19:42:13 +1030 (CST) Message-ID: <19981111194213.H20849@freebie.lemis.com> Date: Wed, 11 Nov 1998 19:42:13 +1030 From: Greg Lehey To: =?iso-8859-1?Q?S=F8ren_Schmidt?= , john cooper Cc: hackers@FreeBSD.ORG, mike@smith.net.au, ticso@cicely.de Subject: Re: SCSI vs. DMA33.. References: <98Nov11.134648jst.21907@ns.isi.co.jp> <199811110816.JAA01536@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.91.1i In-Reply-To: =?iso-8859-1?Q?=3C199811110816=2EJAA01536=40freebsd=2Edk=3E=3B_from_S=F8?= =?iso-8859-1?Q?ren_Schmidt_on_Wed=2C_Nov_11=2C_1998_at_09:16:01AM_+0100?= WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 11 November 1998 at 9:16:01 +0100, Søren Schmidt wrote: > It seems john cooper wrote: >> >> Hi, >> Just wondering if anyone has any _objective_ opinion on >> the performance of say wide SCSI2 vs. DMA33 IDE drives [running >> on contemporary motherboards]. The theoretical throughputs of >> 40MBs and 33MBs don't tell me a whole lot. I know SCSI was the >> choice for performance in the past, however I'm curious what >> others are seeing in actual usage these days. > > Well, at my ISP we run 4 NFS servers that handels all mail/web/misc > stuff for the users, needless to say they are "used" alot. Those 4 > machines are P233/64M PC's with 4*4.3G UDMA IDE drives in them, > configured in pairs as mirrors with ccd. They perform wonderfully. > And the price cannot be beaten too :) > > I must say that the newer UDMA IDE drives has come a long way > lately, they perform at least as good as their SCSI counterparts. > The only thing that they cannot do is overlapping commands, but > given EIDE's much smaller cmd overhead, I'm not sure this has > any significance at all in practice. This last point would appear to be borne out in my measurements earlier today. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 04:01:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA07994 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 04:01:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA07988 for ; Wed, 11 Nov 1998 04:01:44 -0800 (PST) (envelope-from fanf@demon.net) Received: by server.noc.demon.net; id MAA26717; Wed, 11 Nov 1998 12:01:25 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma026685; Wed, 11 Nov 98 12:01:10 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 0zdZBf-0003dj-00; Wed, 11 Nov 1998 12:15:51 +0000 To: hackers@FreeBSD.ORG From: Tony Finch Subject: Re: SCSI vs. DMA33.. Newsgroups: chiark.mail.freebsd.hackers In-Reply-To: <19981111162000.O20374@freebie.lemis.com> Organization: Deliberate Obfuscation To Amuse Tony References: <98Nov11.134648jst.21907@ns.isi.co.jp> <98Nov11.134648jst.21907@ns.isi.co.jp> Message-Id: Date: Wed, 11 Nov 1998 12:15:51 +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > [...] >They say, though, that SCSI drives work better with multiple requests >outstanding... > >$ dd if=/dev/rsd0c bs=32k count=1000 of=/dev/null & dd if=/dev/rsd1c bs=32k count=1000 of=/dev/null [...] >I must say, I'm surprised. This makes it look like there's more of a >performance hit with concurrent requests on SCSI than on IDE. [...] Our canonical examples of applications that benefit from SCSI is a web server or proxy cache, because they tend to exercise the disks' ability to do random seeks. Given that disks frequently lie through their teeth about their geometry and do things like transparent bad block remapping, letting the disk do its own request scheduling is probably a Good Thing. Obviously you have to have a controller that can queue up a decent number of outstanding requests so care is required when looking at the specs... Sorry, I don't have performance numbers to hand right now. Tony. -- gg yhf**f.a.n.finch dot@dotat.at fanf@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 04:22:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11391 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 04:22:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from findmail.com (m9.findmail.com [209.185.96.144]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA11386 for ; Wed, 11 Nov 1998 04:22:11 -0800 (PST) (envelope-from melvynlingham@rocketmail.com) Received: (qmail 30429 invoked by uid 505); 11 Nov 1998 12:14:19 -0000 Date: 11 Nov 1998 12:14:19 -0000 Message-ID: <19981111121419.30428.qmail@findmail.com> Received: from 204.123.2.83 (via http) from to list "freebsd-hackers" From: "Melvyn Cedric Lingham" Subject: Re: Welcome to Pornmail! Reply to confirm! In-Reply-To: <199803242230.OAA07455@pornmail.com> To: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ***** YOU MUST REPLY TO THIS EMAIL TO START PORNMAIL ****** > > This is your reply from Pornmail.com! You must now hit > REPLY on your email program to send this message back to > us, and let us know we have your correct address. Please > note that this is the ONLY way to ensure your subscription > proceeds. If you send an email to us ANY other way, it > will NOT get you subscribed to the mailing list. > > Pornmail.com! *FREE porn in your email!* > > Note: due to a software glitch, this email may have been a > few days late. We apologize for any inconvenience. > > *********************************************************** > > Note: this is not a spam email. This email was sent to you > because your email was entered in on a website requesting > to be registered for the PornMail.com adult newsletter. If > you did not request this email, please send a reply message > with the word "ban" in the subject field. This will ensure > that you will *never* receive another email from us! :) > > *********************************************************** > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ----- See the original message at http://www.egroups.com/list/freebsd-hackers/?start=23397 -- Free e-mail group hosting at http://www.eGroups.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 05:44:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16845 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 05:44:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from torrentnet.com (bacardi.torrentnet.com [198.78.51.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA16840 for ; Wed, 11 Nov 1998 05:44:22 -0800 (PST) (envelope-from bakul@torrentnet.com) Received: from chai.torrentnet.com (chai.torrentnet.com [198.78.51.73]) by torrentnet.com (8.8.5/8.8.5) with ESMTP id IAA05722; Wed, 11 Nov 1998 08:44:04 -0500 (EST) Received: from chai.torrentnet.com (localhost [127.0.0.1]) by chai.torrentnet.com (8.8.8/8.8.5) with ESMTP id IAA25228; Wed, 11 Nov 1998 08:44:03 -0500 (EST) Message-Id: <199811111344.IAA25228@chai.torrentnet.com> To: Terry Lambert Cc: nate@mt.sri.com (Nate Williams), hackers@FreeBSD.ORG Subject: Re: Supporting more than FD_SETSIZE fd's In-reply-to: Your message of "Wed, 11 Nov 1998 08:25:31 GMT." <199811110825.BAA06296@usr02.primenet.com> Date: Wed, 11 Nov 1998 08:44:03 -0500 From: Bakul Shah Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I need to support more than the default 255 FD's in an application (the > > JDK for what it's worth). To be portable, the code uses fd_set as > > defined in . Unfortunately, unless I redefine FD_SETSIZE > > in every file that uses it, I still have a hard-limit on the number of > > FD's the application can use. > > > > Is there any 'portable' way of getting around this? > Redefine FD_SETSIZE. > > If you don't wwant to do it in every file that uses it, then either > do it in the header file itself, or add -DFD_SETSIZE=1024 to CFLAGS. > > > > I'd really like to > > have it use whichever open FD that the limit allows, but I know now way > > of having this happen? > > I can't really parse this. The "the limit allows" value is based on > how many contiguous bits there are in an fd_set, which is based on > the value of FD_SETSIZE at the time the fd_set is declared. There is a way to select on all the file descriptors your program can open. The idea is to use getdtablesize() to find the number of such descriptors and just allocate an array of fd_mask. Something like: int fd_setsize = getdtablesize(); int fd_tablesize = howmany(max_fd_count, NFDBITS); fd_mask* readfds = calloc(fd_tablesize, sizeof(fd_mask)); fd_mask* tmp_readfds = calloc(fd_tablesize, sizeof(fd_mask)); ... for (;;) { memcpy(tmp_readfds, readfds, fd_tablesize*sizeof(fd_mask)); int nfds = select(maxfd_in_use+1, tmp_readfds, 0, 0, timeout); if (nfds == -1) { if (errno == EINTR) continue; perror("select"); break; } if (nfds == 0) { /* handle timeout */ } /* process ready input file descriptors */ for (int i = 0; i < nfds; i++) { if (!fd_isset(tmp_readfds, i)) continue; process_read(i); } } ... You can `portably' define macros analogous to FD_SET, FD_CLR, FD_ISSET, FD_COPY and FD_ZERO for this `flex' array type. There is really no need to use FD_SETSIZE (unless you are using functions that use select + fd_set and over which you have no control). Basically fd_set should have never been defined. The method I outlined above is portable in the sense that it can be made to work on all machines that provide BSD style select but getdtablesize() call may or may not exist on all machines so you may have to fake it on such machines. The danger is, of course, if you are using X windows library or some such other s/w that uses select and the simple minded fd_set defined in sys/types.h. In this case fds beyond FD_SETSIZE may never get selected as they will never be passed to select by such programs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 05:58:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17623 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 05:58:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (st-lcremean.tidalwave.net [208.213.203.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA17606 for ; Wed, 11 Nov 1998 05:58:00 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id IAA09684; Wed, 11 Nov 1998 08:57:44 -0500 (EST) (envelope-from lee) Message-ID: <19981111085531.A9611@tidalwave.net> Date: Wed, 11 Nov 1998 08:57:44 -0500 From: Lee Cremeans To: Drew Baxter , hackers@FreeBSD.ORG Subject: Re: SCSI vs. DMA33.. Reply-To: lcremean@tidalwave.net References: <98Nov11.134648jst.21907@ns.isi.co.jp> <4.1.19981111014829.00a6eee0@genesis.ispace.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <4.1.19981111014829.00a6eee0@genesis.ispace.com>; from Drew Baxter on Wed, Nov 11, 1998 at 01:50:22AM -0500 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 11, 1998 at 01:50:22AM -0500, Drew Baxter wrote: > So I'd say they're relatively close in performance for my A/V requirements > and all, individual results will vary. Many people say Maxtor drives are > crap, but I have had no problems with mine and they've been burnt in, > dropped, thrown, and various other things. Well, the _really_ crappy drives were the old Maxtor 7000 series, which went into prduction shortly after Maxtor bought MiniScribe (it's a MiniScribe design, technically). I've heard of people who've had scores of 7120ATs die on them! But thankfully, the CrystalMax and DiamondMax are better....completely redesigned mechanism and electronics. Also, the 7000s were much slower than, say, a Quantum LPS120AT (in the 7120's case) or a Fireball I 540MB in the 7540AV's case...the *Max drives are, as you've noticed, nice and fast, though. As for me, I have a Seagate Medalist Pro 9140, and so far, I like it. It runs REALLY HOT, but it's fast and fairly quiet, and works great even though I had to hack ide_pci.c to disable UDMA: st-lcremean:~ $ dd if=/dev/rwd0 of=/dev/null bs=1m count=20 20+0 records in 20+0 records out 20971520 bytes transferred in 2.109357 secs (9942139 bytes/sec) Woooo. -- Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | mailto:lcremean@tidalwave.net http://st-lcremean.tidalwave.net | Powered by FreeBSD 3.0-CURRENT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 06:31:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20022 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 06:31:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20014 for ; Wed, 11 Nov 1998 06:31:25 -0800 (PST) (envelope-from Reinier.Bezuidenhout@KryptoKom.DE) Received: (from mail@localhost) by Thingol.KryptoKom.DE (8.8.7/8.8.4) id PAA07393; Wed, 11 Nov 1998 15:31:02 +0100 Received: from cirdan.kryptokom.de by via smtpp (Version 1.1.1beta6) id kwa07385; Wed Nov 11 15:30:47 1998 Received: by Cirdan.KryptoKom.DE (8.8.5/8.8.5) with ESMTP id PAA26054; Wed, 11 Nov 1998 15:27:29 +0100 Received: (from bez@localhost) by borg.kryptokom.de (8.8.8/8.8.8) id PAA25157; Wed, 11 Nov 1998 15:33:42 +0100 (CET) (envelope-from bez) From: Reinier Bezuidenhout Message-Id: <199811111433.PAA25157@borg.kryptokom.de> Subject: Re: Malloc in the kernel and double panic In-Reply-To: <199811110901.BAA13927@root.com> from David Greenman at "Nov 11, 1998 1: 1:34 am" To: dg@root.com Date: Wed, 11 Nov 1998 15:33:42 +0100 (CET) Cc: tlambert@primenet.com, grog@lemis.com, Reinier.Bezuidenhout@KryptoKom.DE@Cirdan.KryptoKom.DE, freebsd-hackers@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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... After being unable to allocate a dynamic continious chunk of memory in the kernel, I decided I would not try to do it dynamically and let it grow as I need more entries. I decided to malloc one big array whose elements are pointers to structures ... so I have the following type: T_KEY *T_P_KEY; With T_KEY the structure. T_P_KEY *large_one; large_one = (T_P_KEY *)malloc(sizeof(T_P_KEY) * 10000, M_DEVBUF, M_WAITOK); And this causes a happy double panic in the kernel.... How can I allocate a 10000 * sizeof(pointer) section of memory in the kernel ? I have tried this on different hardware platforms etc. and the same thing happens. Any ideas ??? Reinier > >> to allocate demand-zero, pageable, kernel memory. > > > >Hmmm.... > > > > > >Better fix /sys/kern/sysv_shm.c then, since that's where I cribbed the > >code from... > > sysv_shm.c is a special beast that specifically *avoids* allocating kernel > VM for the objects it manages. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 06:51:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22379 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 06:51:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22373 for ; Wed, 11 Nov 1998 06:51:24 -0800 (PST) (envelope-from Reinier.Bezuidenhout@KryptoKom.DE) Received: (from mail@localhost) by Thingol.KryptoKom.DE (8.8.7/8.8.4) id PAA07695; Wed, 11 Nov 1998 15:51:08 +0100 Received: from cirdan.kryptokom.de by via smtpp (Version 1.1.1beta6) id kwa07693; Wed Nov 11 15:50:51 1998 Received: by Cirdan.KryptoKom.DE (8.8.5/8.8.5) with ESMTP id PAA26260; Wed, 11 Nov 1998 15:47:32 +0100 Received: (from bez@localhost) by borg.kryptokom.de (8.8.8/8.8.8) id PAA25265; Wed, 11 Nov 1998 15:53:45 +0100 (CET) (envelope-from bez) From: Reinier Bezuidenhout Message-Id: <199811111453.PAA25265@borg.kryptokom.de> Subject: Re: Malloc in the kernel "conical" panic In-Reply-To: <199811110901.BAA13927@root.com> from David Greenman at "Nov 11, 1998 1: 1:34 am" To: dg@root.com Date: Wed, 11 Nov 1998 15:53:45 +0100 (CET) Cc: tlambert@primenet.com, grog@lemis.com, Reinier.Bezuidenhout@KryptoKom.DE@Cirdan.KryptoKom.DE, freebsd-hackers@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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi .... Ok .. so here I am, sitting with the conical hat .... the double panic was not caused by the malloc ... :) something I did wrong .... The malloc seemed to have worked fine ... the only thing that still bothers me, is why I got data blocks of 1024 entries in the array of pointers being zero'd .... It seems that with the one big malloc I just avoid the problem as I still don't know who/what was zero'ing the entires when doing a malloc, mcopy, free using malloc and M_DEVBUF, WAIT_OK ... Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 07:43:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27569 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 07:43:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27564 for ; Wed, 11 Nov 1998 07:43:50 -0800 (PST) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id QAA29729; Wed, 11 Nov 1998 16:41:37 +0100 (MET) Message-ID: <19981111164136.A29513@cons.org> Date: Wed, 11 Nov 1998 16:41:36 +0100 From: Martin Cracauer To: john cooper , grog@lemis.com, hackers@FreeBSD.ORG, mike@smith.net.au, ticso@cicely.de Subject: Re: SCSI vs. DMA33.. References: <98Nov11.134648jst.21907@ns.isi.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <98Nov11.134648jst.21907@ns.isi.co.jp>; from john cooper on Wed, Nov 11, 1998 at 01:41:00PM +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <98Nov11.134648jst.21907@ns.isi.co.jp>, john cooper wrote: > Just wondering if anyone has any _objective_ opinion on > the performance of say wide SCSI2 vs. DMA33 IDE drives [running > on contemporary motherboards]. The theoretical throughputs of > 40MBs and 33MBs don't tell me a whole lot. I know SCSI was the > choice for performance in the past, however I'm curious what > others are seeing in actual usage these days. I'm just trying to build a CCD system with two PCI UDMA controllers by Promise and 4 IBM DDTA 8 GB drives. Given that I often stream over very large files and that I paid much less than half the money per Megabyte than for SCSI disks the IDE solution sounds good. Guess what: While I can use the two PCI cards simultaneously, I can't do so for the two channels on each card, although they are even two completely independent chips on each Promize card. Since I don't have enough PCI slots for 4 cards (and these things cost money) and my motherboard doesn't do UDMA, I'm stuck with performance like my SCSI CCD with two Atlas drives. That isn't too bad, but not what I hoped for. Maybe it's a problem with our Promise driver? I already contacted John Dyson, but no response yet. Anyone else can think of a solution? 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-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 07:47:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28036 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 07:47:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA28031 for ; Wed, 11 Nov 1998 07:47:07 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id IAA00103; Wed, 11 Nov 1998 08:38:43 -0700 (MST) Date: Wed, 11 Nov 1998 08:38:43 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199811111538.IAA00103@narnia.plutotech.com> To: Greg Lehey cc: hackers@FreeBSD.ORG Subject: Re: SCSI vs. DMA33.. X-Newsgroups: pluto.freebsd.hackers In-Reply-To: <98Nov11.134648jst.21907@ns.isi.co.jp> <199811110816.JAA01536@freebsd.dk> <19981111194213.H20849@freebie.lemis.com> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19981111194213.H20849@freebie.lemis.com> you wrote: >> I must say that the newer UDMA IDE drives has come a long way >> lately, they perform at least as good as their SCSI counterparts. >> The only thing that they cannot do is overlapping commands, but >> given EIDE's much smaller cmd overhead, I'm not sure this has >> any significance at all in practice. > > This last point would appear to be borne out in my measurements > earlier today. You had all of 1 command going to each disk. That doesn't give you any per-device overlap. If you really want to see the effect of overlapped commands, run a benchmark through the filesystem that causes lots of commands to be generated. Do it with tagged queuing and without. If your devices support a reasonable number of transactions, the effect of disabling tagged queuing on latency is quite dramatic. I once introduced a bug into CAM that effectively disabled tagged queuing. For several days I couldn't understand why my interactive performance was so lousy during large compile runs. I think that the testaments on this list and others about the dramatic improvement CAM has made to the performance of high load, random seek, workloads also shows the effectiveness of overlapped I/O. The main reason CAM performs so well is the order of magnitude increase in the number of concurrent, per-device, transactions the system supports. > Greg -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 08:11:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01946 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 08:11:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01941 for ; Wed, 11 Nov 1998 08:11:14 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id IAA18098; Wed, 11 Nov 1998 08:12:11 -0800 (PST) Message-Id: <199811111612.IAA18098@root.com> To: Reinier Bezuidenhout cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Malloc in the kernel and double panic In-reply-to: Your message of "Wed, 11 Nov 1998 15:33:42 +0100." <199811111433.PAA25157@borg.kryptokom.de> From: David Greenman Reply-To: dg@root.com Date: Wed, 11 Nov 1998 08:12:11 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >After being unable to allocate a dynamic continious chunk of memory >in the kernel, I decided I would not try to do it dynamically >and let it grow as I need more entries. I decided to malloc one >big array whose elements are pointers to structures ... so I have the >following type: > >T_KEY *T_P_KEY; With T_KEY the structure. > >T_P_KEY *large_one; > >large_one = (T_P_KEY *)malloc(sizeof(T_P_KEY) * 10000, M_DEVBUF, M_WAITOK); Just a guess: although you think that sizeof(T_P_KEY) is 4 (a pointer), it's actually much larger. There isn't any problem with allocating 40KB with malloc; many things do it in the kernel. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 09:18:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09135 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 09:18:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09073 for ; Wed, 11 Nov 1998 09:18:00 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA25715; Wed, 11 Nov 1998 10:17:42 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA17248; Wed, 11 Nov 1998 10:17:41 -0700 Date: Wed, 11 Nov 1998 10:17:41 -0700 Message-Id: <199811111717.KAA17248@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Terry Lambert Cc: nate@mt.sri.com (Nate Williams), hackers@FreeBSD.ORG Subject: Re: Supporting more than FD_SETSIZE fd's In-Reply-To: <199811110825.BAA06296@usr02.primenet.com> References: <199811091734.KAA04752@mt.sri.com> <199811110825.BAA06296@usr02.primenet.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I need to support more than the default 255 FD's in an application (the > > JDK for what it's worth). To be portable, the code uses fd_set as > > defined in . Unfortunately, unless I redefine FD_SETSIZE > > in every file that uses it, I still have a hard-limit on the number of > > FD's the application can use. > > > > Is there any 'portable' way of getting around this? > > Redefine FD_SETSIZE. This still gives me a hard-limit (instead of a dynamic limit) on the number of FD's in any compiled binary. > > I'd really like to > > have it use whichever open FD that the limit allows, but I know now way > > of having this happen? > > I can't really parse this. The "the limit allows" value is based on > how many contiguous bits there are in an fd_set, which is based on > the value of FD_SETSIZE at the time the fd_set is declared. I'd like to have it based on the 'getrlimit(RLIMIT_NOTFILE, &rlimit_t), which is how many the current 'process' can handle. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 09:18:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09302 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 09:18:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09172 for ; Wed, 11 Nov 1998 09:18:05 -0800 (PST) (envelope-from roger@cs.strath.ac.uk) Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id RAA06599 Wed, 11 Nov 1998 17:12:13 GMT Message-ID: <3649C56D.41C6@cs.strath.ac.uk> Date: Wed, 11 Nov 1998 17:12:13 +0000 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Libretto probes for 21 PCI busses Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just installed 3.0-RELEASE on my Libretto 100CT. The boot sequence works fine, but it probes for 21 PCI busses Probing PCI Bus 0 Probing PCI Bus 1 Probing PCI Bus 2 Probing PCI Bus 3 ...snip... Probing PCI Bus 21 Obviously something wrong is being passed to the PCI bus code. Does anyone want me to look into this for them. Bye Roger Hardiman BTW, The Toshiba Libretto 100CT runs 3.0-RELEASE great. I`m using the 16bit colour X server Doug White put on his web site for the NeoMagic chipset and it runs on the special wide-screen 800x480 LCD very nicely. Of course, Luigi's PCM driver works fine too for the audio. Networking is via a 3COM Etherlink III PCMCIA card. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 09:22:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09722 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 09:22:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09714 for ; Wed, 11 Nov 1998 09:22: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.8.8/8.8.8) with SMTP id KAA25763; Wed, 11 Nov 1998 10:21:49 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA17285; Wed, 11 Nov 1998 10:21:48 -0700 Date: Wed, 11 Nov 1998 10:21:48 -0700 Message-Id: <199811111721.KAA17285@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Bakul Shah Cc: Terry Lambert , nate@mt.sri.com (Nate Williams), hackers@FreeBSD.ORG Subject: Re: Supporting more than FD_SETSIZE fd's In-Reply-To: <199811111344.IAA25228@chai.torrentnet.com> References: <199811110825.BAA06296@usr02.primenet.com> <199811111344.IAA25228@chai.torrentnet.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Increasing the number of file descriptors in a program instead of having it hard-coded to FD_SETSIZE ] > > > Is there any 'portable' way of getting around this? > > > Redefine FD_SETSIZE. > > > > There is a way to select on all the file descriptors your > program can open. The idea is to use getdtablesize() to find > the number of such descriptors and just allocate an array of > fd_mask. Something like: > > int fd_setsize = getdtablesize(); > int fd_tablesize = howmany(max_fd_count, NFDBITS); Where is max_fd_count defined? > fd_mask* readfds = calloc(fd_tablesize, sizeof(fd_mask)); > fd_mask* tmp_readfds = calloc(fd_tablesize, sizeof(fd_mask)); > > ... > for (;;) { > memcpy(tmp_readfds, readfds, fd_tablesize*sizeof(fd_mask)); > int nfds = select(maxfd_in_use+1, tmp_readfds, 0, 0, timeout); > if (nfds == -1) { > if (errno == EINTR) > continue; > perror("select"); > break; > } > if (nfds == 0) { > /* handle timeout */ > } > /* process ready input file descriptors */ > for (int i = 0; i < nfds; i++) { > if (!fd_isset(tmp_readfds, i)) > continue; > process_read(i); > } > } > ... > > You can `portably' define macros analogous to FD_SET, FD_CLR, > FD_ISSET, FD_COPY and FD_ZERO for this `flex' array type. I tried doing this, but ended up with a core dump. Unfortunately, I ran out of time to work on it this week (real work calls), but I'll look into doing this this weekend. However, if someone has already done this I'm more than willing to accept example code. :) :) > The method I outlined above is portable in the sense that it > can be made to work on all machines that provide BSD style > select but getdtablesize() call may or may not exist on all > machines so you may have to fake it on such machines. For now, I'm mostly worried about all different versions of FreeBSD, so my definition of 'portable' is limited. > The > danger is, of course, if you are using X windows library or > some such other s/w that uses select and the simple minded > fd_set defined in sys/types.h. In this case fds beyond > FD_SETSIZE may never get selected as they will never be > passed to select by such programs. I understand.... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 09:25:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10059 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 09:25:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10052 for ; Wed, 11 Nov 1998 09:25:39 -0800 (PST) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id OAA09788 for ; Tue, 10 Nov 1998 14:18:01 -0600 (CST) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma009786; Tue, 10 Nov 98 14:18:00 -0600 Received: from spawn.nectar.com (localhost.nectar.com [127.0.0.1]) by spawn.nectar.com (8.9.1/8.9.1) with ESMTP id OAA20884 for ; Tue, 10 Nov 1998 14:18:00 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Message-Id: <199811102018.OAA20884@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine Subject: kernel BOOTP To: hackers@FreeBSD.ORG Date: Tue, 10 Nov 1998 14:18:00 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hi, I'm attempting to boot a machine off the floppy, and mount all filesystems over NFS. The network card is supported by the kernel xl driver, but not by the netboot code. Therefore, I created a kernel with the BOOTP and BOOTP_NFSROOT options and put it on a floppy. The reply from the BOOTP server is not being received (i.e. ``BOOTP timeout for server 0xffffffff''). The client and the BOOTP server are on the same network. Is there any documentation for use of kernel BOOTP? Is anyone using it successfully? Any advice on diagnosing the problem? Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNkifeDeRhT8JRySpAQHHGAQAyqzhTgkUA/2jY7R/FFEhiLL5jakB2ELl UZU/bT9iROplOyvkgHp1B4y85+IkHWrg3Ke8VINrEcwPgzPY0P3zgnJBxi5nn2SS FmLi45MemJ4PpiDekZcQPjSe6K7M+bKi0xfluwTyWPXegsWR7Vdnbfrq/Z4umiIa vMdotAnyohY= =XCrU -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 09:25:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10092 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 09:25:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10069 for ; Wed, 11 Nov 1998 09:25:43 -0800 (PST) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id AAA10600; Wed, 11 Nov 1998 00:40:11 -0600 (CST) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma010598; Wed, 11 Nov 98 00:40:09 -0600 Received: from spawn.nectar.com (localhost.nectar.com [127.0.0.1]) by spawn.nectar.com (8.9.1/8.9.1) with ESMTP id AAA22719; Wed, 11 Nov 1998 00:40:05 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Message-Id: <199811110640.AAA22719@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: <199811110512.VAA01354@troutmask.apl.washington.edu> References: <199811110512.VAA01354@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname To: Steve Kargl cc: joelh@gnu.org (Joel Ray Holveck), dfr@nlsystems.com, sos@freebsd.dk, nate@mt.sri.com, kkennawa@physics.adelaide.edu.au, dnelson@emsphone.com, rivers@dignus.com, hackers@FreeBSD.ORG Date: Wed, 11 Nov 1998 00:40:05 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- What about it? Copy the script to a writable filesystem. Make whatever modifications are needed. Of course, that would only be necessary if e.g. ``/compat/linux/bin/sh /cdrom/install.sh'' didn't do what is expected. Someone else (wisely) suggested wrapping this kind of thing in a port. That is what they are for. Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org On 10 November 1998 at 21:12, Steve Kargl wrote: > What about install scripts that reside on cdroms? You can't magically > edit a cdrom install script unless unionfs works. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNkkxRDeRhT8JRySpAQE46gP9GruS3LPn0YxAiLKBUTlS31Vp3SW+8qeQ 6xaCZh4gZrmuClz+1SUjn//tMEjYt7ktZ9HBLOflgV/o81gexXJ52JYkXzyjEBS0 99dNeWizEyxUIPfq/0sRcz8GGTGNK3oCfR9JjtEif6gOS35wuZDtbNl3Bis3mWA+ ZltEOEVtsEs= =vSo0 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 09:34:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11302 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 09:34:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11191 for ; Wed, 11 Nov 1998 09:34:01 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id SAA01133; Wed, 11 Nov 1998 18:30:36 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199811111730.SAA01133@freebsd.dk> Subject: Re: SCSI vs. DMA33.. In-Reply-To: <19981111164136.A29513@cons.org> from Martin Cracauer at "Nov 11, 1998 4:41:36 pm" To: cracauer@cons.org (Martin Cracauer) Date: Wed, 11 Nov 1998 18:30:36 +0100 (CET) Cc: john@isi.co.jp, grog@lemis.com, hackers@FreeBSD.ORG, mike@smith.net.au, ticso@cicely.de X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Martin Cracauer wrote: > > I'm just trying to build a CCD system with two PCI UDMA controllers by > Promise and 4 IBM DDTA 8 GB drives. Given that I often stream over > very large files and that I paid much less than half the money per > Megabyte than for SCSI disks the IDE solution sounds good. Yup, it actually works pretty well, and it sure beats everything else in cost pr MB. > Guess what: While I can use the two PCI cards simultaneously, I can't > do so for the two channels on each card, although they are even two > completely independent chips on each Promize card. Since I don't have > enough PCI slots for 4 cards (and these things cost money) and my > motherboard doesn't do UDMA, I'm stuck with performance like my SCSI > CCD with two Atlas drives. That isn't too bad, but not what I hoped > for. > > Maybe it's a problem with our Promise driver? I already contacted John > Dyson, but no response yet. Anyone else can think of a solution? Hmm, it works for me, I have this little tweak to wd.c though, without it the promise sometimes blows up... Index: wd.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/wd.c,v retrieving revision 1.178 diff -u -r1.178 wd.c --- wd.c 1998/10/22 05:58:41 1.178 +++ wd.c 1998/11/06 16:23:26 @@ -349,9 +349,11 @@ goto reset_ok; #endif DELAY(RECOVERYTIME); +/* sos if (wdreset(du) != 0) { goto nodevice; } +*/ reset_ok: /* execute a controller only command */ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 09:49:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13037 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 09:49:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles229.castles.com [208.214.165.229]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13027 for ; Wed, 11 Nov 1998 09:49:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA03980; Wed, 11 Nov 1998 09:47:56 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811111747.JAA03980@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: eivind@yes.no (Eivind Eklund), sgk@troutmask.apl.washington.edu, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-reply-to: Your message of "Wed, 11 Nov 1998 08:41:31 GMT." <199811110841.BAA06929@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Nov 1998 09:47:55 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > You'll never pick up /compat/linux/bin/uname unless you delete/rename > > > /usr/bin/uname. > > > > Eh - I'm pretty sure /compat/linux is searched _before_ /. For all > > syscalls. This is hardcoded in the linux emulator in the kernel. > > Sure. /compat/linux/bin/sh was searched for on the exec of /bin/sh > in order to run the shell script. > > Then the /bin/sh from FreeBSD was loaded. > > Then the /compat/linux directory was ignore as the FreeBSD binary > /bin/sh exec'ed the FreeBSD /bin/uname program. Actually, that's by no means correct. The linux_lib port installs the Linux 'sh' in /compat/linux/bin/{sh|bash} and the correct way to install a piece of Linux software is to start by running that shell. The real problem is that the Linux uname(1) lives in /bin, while the install script in question in this conversation checks for /usr/bin/uname first. The trivial answer is of course to put a copy there as well. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 09:49:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13068 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 09:49:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13041 for ; Wed, 11 Nov 1998 09:49:38 -0800 (PST) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.8/8.7.3) id SAA10474; Wed, 11 Nov 1998 18:45:00 +0100 (CET) Message-ID: <19981111184459.A10448@cons.org> Date: Wed, 11 Nov 1998 18:44:59 +0100 From: Martin Cracauer To: =?iso-8859-1?Q?S=F8ren_Schmidt?= , Martin Cracauer Cc: john@isi.co.jp, grog@lemis.com, hackers@FreeBSD.ORG, mike@smith.net.au, ticso@cicely.de Subject: Re: SCSI vs. DMA33.. References: <19981111164136.A29513@cons.org> <199811111730.SAA01133@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.1i In-Reply-To: =?iso-8859-1?Q?=3C199811111730=2ESAA01133=40freebsd=2Edk=3E=3B_from_S=F8?= =?iso-8859-1?Q?ren_Schmidt_on_Wed=2C_Nov_11=2C_1998_at_06:30:36PM_+0100?= Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199811111730.SAA01133@freebsd.dk>, Søren Schmidt wrote: > It seems Martin Cracauer wrote: [... about two promise cards for IDE striping] > > Guess what: While I can use the two PCI cards simultaneously, I can't > > do so for the two channels on each card, although they are even two > > completely independent chips on each Promize card. Since I don't have > > enough PCI slots for 4 cards (and these things cost money) and my > > motherboard doesn't do UDMA, I'm stuck with performance like my SCSI > > CCD with two Atlas drives. That isn't too bad, but not what I hoped > > for. > > > > Maybe it's a problem with our Promise driver? I already contacted John > > Dyson, but no response yet. Anyone else can think of a solution? > > Hmm, it works for me, I have this little tweak to wd.c though, > without it the promise sometimes blows up... What means "work"? I get a functional ccd filessystem over 4 drives/4channels/2cards, so far so good. But while the throughput is raised when striping over different cards, it isn't when striping over two channels on the same card. Or in other words, the maximum thoughput for a (2x) 4-drive, 4-channel, 2-card ccd is the same as for a (2x) 2-drive, 2-channel, 2-card array, while (1x) 2-drive, 2-channel, 1-card is excatly the same as for (1x) 1-drive, 1-channel, 1-card. Hence my impression I can't use the two channels on one card simultaneously. Is this really different for you? Do you have the promise BIOS prom installed? Thanks for the fix, BTW, does this fix the IDE timeouts I see when striping over 4 drives? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 10:09:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14729 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 10:09:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14719 for ; Wed, 11 Nov 1998 10:09:29 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from celeris (56k-port4009.ime.net [209.90.195.19]) by Loki.orland.u91.k12.me.us (8.9.1/8.8.8-Loki) with SMTP id NAA01438 for ; Wed, 11 Nov 1998 13:09:09 -0500 (EST) (envelope-from netmonger@genesis.ispace.com) X-Server-ID: Loki.orland.u91.k12.me.us, OCSNet - Orland Maine USA X-Coord-Name: Drew "Droobie" Baxter, OneNetwork Exchange X-Coord-Addr: Droobie@Openlink.orland.me.us X-Coord-Pager: USA: 207-471-2719, http://pagedroo.orland.me.us Message-Id: <4.1.19981111130503.00918c20@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 11 Nov 1998 13:06:45 -0500 To: hackers@FreeBSD.ORG From: Drew Baxter Subject: Re: UDMA33 Maxtor Diamondmax Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Welp I just figured I'd let people be forewarned to watch Maxtor drives. As soon as I said I had no problems, I woke up with a missing FAT and bad media descriptors on both partitions.. All in all I probably lost 7 of 534 mp3s on one, and a total devestation on the first partition (probably in excess of 700mb).. I guess I'm not going to use the term "Well they haven't failed for me yet" again.. I just bought this thing about a month ago. I suddenly want the 3.5 back that doesn't have UDMA. --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange 207-942-0275 http://www.droo.orland.me.us My Latest Kernel: FreeBSD 3.0-CURRENT (ONEEX) #14: Mon Oct 19 22:36:58 EDT 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 10:10:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14928 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 10:10:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles229.castles.com [208.214.165.229]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14898 for ; Wed, 11 Nov 1998 10:10:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA04141; Wed, 11 Nov 1998 10:08:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811111808.KAA04141@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Justin T. Gibbs" cc: Greg Lehey , hackers@FreeBSD.ORG Subject: Re: SCSI vs. DMA33.. In-reply-to: Your message of "Wed, 11 Nov 1998 08:38:43 MST." <199811111538.IAA00103@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Nov 1998 10:08:08 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > runs. I think that the testaments on this list and others about > the dramatic improvement CAM has made to the performance of high > load, random seek, workloads also shows the effectiveness of > overlapped I/O. The main reason CAM performs so well is the order > of magnitude increase in the number of concurrent, per-device, transactions > the system supports. Unfortunately, Simon's numbers tend to indicate that CAM doesn't provide the same order of magnitude improvement that the old SCSI subsystem did. At least it's a little more robust. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 10:35:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17875 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 10:35:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ics.com (ics.com [140.186.40.192]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17869 for ; Wed, 11 Nov 1998 10:35:33 -0800 (PST) (envelope-from kaleb@ics.com) Received: from ics.com (sunoco.ics.com [140.186.40.142]) by ics.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id NAA12532 Wed, 11 Nov 1998 13:34:56 -0500 (EST) Message-ID: <3649D8D0.61F99625@ics.com> Date: Wed, 11 Nov 1998 13:34:56 -0500 From: "Kaleb S. KEITHLEY" Organization: Integrated Computer Solutions X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.5.1 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Alpha firmware Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is this the wrong list to ask this on? I've got an Digital EB64, a.k.a. Alpha PC64 (and a.k.a. Cabriolet). It's all set up and and waiting for an OS to install; but ------- A week ago when the Alpha 3.0-RELEASE was still on the ftp server and said it needed NetBSD boot disks, I pulled over and read the NetBSD install, which said it needed the SRM firmware. I'm presuming that the FreeBSD install also needs the SRM firmware. For whatever reason the SRM firmware is not in the flash ROM on this board. Nor do I have the disk with the SRM firmware. (I bought the board, new in the box, but the box had been opened. The outfit I bought it from okay, as far as it goes, but for various reasons isn't particularly helpful about coming up with the firmware diskettes for the board.) I'm also looking for the firmware through other channels, but don't know when, if ever, they might bear fruit. Does anyone that's doing the Alpha port have firmware diskettes for this board that they'd be willing to dd off the contents and make them available somewhere for ftp? Thanks in advance. -- Kaleb S. KEITHLEY To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 10:42:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18541 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 10:42:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18535 for ; Wed, 11 Nov 1998 10:42:07 -0800 (PST) (envelope-from ticso@cicely5.cicely.de) Received: from cicely.cicely.de (cicely.de [194.231.9.142]) by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id TAA21149; Wed, 11 Nov 1998 19:41:23 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [10.1.1.7]) by cicely.cicely.de (8.8.8/8.8.8) with ESMTP id TAA21292; Wed, 11 Nov 1998 19:41:50 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.9.0/8.9.0) id TAA27689; Wed, 11 Nov 1998 19:41:58 +0100 (CET) Message-ID: <19981111194157.06719@cicely.de> Date: Wed, 11 Nov 1998 19:41:57 +0100 From: Bernd Walter To: Greg Lehey , Mike Smith , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <199811100638.WAA00637@dingo.cdrom.com> <19981111103028.L18183@freebie.lemis.com> <19981111040654.07145@cicely.de> <19981111134546.D20374@freebie.lemis.com> <19981111085152.55040@cicely.de> <19981111183546.D20849@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19981111183546.D20849@freebie.lemis.com>; from Greg Lehey on Wed, Nov 11, 1998 at 06:35:46PM +1030 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 11, 1998 at 06:35:46PM +1030, Greg Lehey wrote: > On Wednesday, 11 November 1998 at 8:51:52 +0100, Bernd Walter wrote: > > On Wed, Nov 11, 1998 at 01:45:46PM +1030, Greg Lehey wrote: > >> On Wednesday, 11 November 1998 at 4:06:54 +0100, Bernd Walter wrote: > >>> On Wed, Nov 11, 1998 at 10:30:28AM +1030, Greg Lehey wrote: > >>>> On Monday, 9 November 1998 at 22:38:04 -0800, Mike Smith wrote: > >>> [...] > >>> One point is that is doesn't aggregate transactions to the lower drivers. > >>> When using stripes of one sector it's doing no more than one sector > >>> transactions to the HDDs so at least with the old scsi driver there's no > >>> linear performance increase with it. That's the same with ccd. > >> > >> Correct, at least as far as Vinum goes. The rationale for this is > >> that, with significant extra code, Vinum could aggregate transfers > >> *from a single user request* in this manner. But any request that > >> gets this far (in other words, runs for more than a complete stripe) > >> is going to convert one user request into n disk requests. There's no > >> good reason to do this, and the significant extra code would just chop > >> off the tip of the iceberg. The solution is in the hands of the user: > >> don't use small stripe sizes. I recommend a stripe of between 256 and > >> 512 kB. > > > > That's good for random performance increase - but for linear access a smaler > > stripe size is the only way to get the maximum performance of all > > disks together. > > No, the kind of stripe size you're thinking about will almost always > degrade performance. If you're accessing large quantities of data in > a linear fashion, you'll be reading 60 kB at a time. If each of these > reads requires accessing more than one disk, you'll kill performance. > Try it: I have. With agregation? Say You read the volume linear without any other activity on the disks. If you have a stripe size of 60k and reading is at 60k chunks each read will read 60k of only one disk - expecting all transactions are stripe aligned. The only thing wich will increase performance are the readahead abilities of the fs-driver and the disks themself - at least if I havn't missed any. If You use 512byte Stripes and read 60k chunks - the current situation is that each drive gets single sector transactions which is often slower than a single disk What I expect is that an agreagation such a 60k chunk access on the volume is splited into only one transaction per drive - so you can read from all the drives at the same time and get an bandwidth increase. Write access like newfs should be different because of write behind caches. -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 11:00:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20298 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 11:00:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from torrentnet.com (bacardi.torrentnet.com [198.78.51.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20288 for ; Wed, 11 Nov 1998 11:00:18 -0800 (PST) (envelope-from bakul@torrentnet.com) Received: from chai.torrentnet.com (chai.torrentnet.com [198.78.51.73]) by torrentnet.com (8.8.5/8.8.5) with ESMTP id NAA28400; Wed, 11 Nov 1998 13:59:57 -0500 (EST) Received: from chai.torrentnet.com (localhost [127.0.0.1]) by chai.torrentnet.com (8.8.8/8.8.5) with ESMTP id NAA26093; Wed, 11 Nov 1998 13:59:57 -0500 (EST) Message-Id: <199811111859.NAA26093@chai.torrentnet.com> To: Nate Williams Cc: hackers@FreeBSD.ORG Subject: Re: Supporting more than FD_SETSIZE fd's In-reply-to: Your message of "Wed, 11 Nov 1998 10:21:48 MST." <199811111721.KAA17285@mt.sri.com> Date: Wed, 11 Nov 1998 13:59:57 -0500 From: Bakul Shah Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > int fd_setsize = getdtablesize(); > > int fd_tablesize = howmany(max_fd_count, NFDBITS); > Where is max_fd_count defined? Oops! I forgot to fix the second line above when I renamed max_fd_count to fd_setsize. BTW, getrlimit(RLIMIT_NOFILE, &fd_setsize) is a better choice than getdtablesize(). > I tried doing this, but ended up with a core dump. Unfortunately, I ran > out of time to work on it this week (real work calls), but I'll look > into doing this this weekend. However, if someone has already done this > I'm more than willing to accept example code. :) :) The code fragment I showed is approx. right as I've used something similar a couple of times before but I will try to turn it into a working example over the weekend. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 11:02:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20628 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 11:02:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20622 for ; Wed, 11 Nov 1998 11:02:35 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id MAA04591; Wed, 11 Nov 1998 12:00:41 -0700 (MST) Message-Id: <199811111900.MAA04591@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: "Justin T. Gibbs" , Greg Lehey , hackers@FreeBSD.ORG Subject: Re: SCSI vs. DMA33.. In-reply-to: Your message of "Wed, 11 Nov 1998 10:08:08 PST." <199811111808.KAA04141@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Nov 1998 11:53:55 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Unfortunately, Simon's numbers tend to indicate that CAM doesn't >provide the same order of magnitude improvement that the old SCSI >subsystem did. At least it's a little more robust. 8) I never said it was order of magnitude improvement only an order of magnitude increase in concurrency. The numbers I've seen is on the order of 50% to 100% change in performance. Simon's benchmark is hitting the O(N) constraint of bufqdisksort which I'll fix as soon as I get a chance. I never received numbers from him with a change to remove the kernel elevator sort, but I would expect to see an improvement in scalability. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 11:03:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20719 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 11:03:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20712 for ; Wed, 11 Nov 1998 11:03: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.8.8/8.8.8) with SMTP id MAA26688; Wed, 11 Nov 1998 12:03:09 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA18067; Wed, 11 Nov 1998 12:03:08 -0700 Date: Wed, 11 Nov 1998 12:03:08 -0700 Message-Id: <199811111903.MAA18067@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Bakul Shah Cc: Nate Williams , hackers@FreeBSD.ORG Subject: Re: Supporting more than FD_SETSIZE fd's In-Reply-To: <199811111859.NAA26093@chai.torrentnet.com> References: <199811111721.KAA17285@mt.sri.com> <199811111859.NAA26093@chai.torrentnet.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > int fd_setsize = getdtablesize(); > > > int fd_tablesize = howmany(max_fd_count, NFDBITS); > > > Where is max_fd_count defined? > > Oops! I forgot to fix the second line above when I renamed > max_fd_count to fd_setsize. > > BTW, getrlimit(RLIMIT_NOFILE, &fd_setsize) is a better choice > than getdtablesize(). > > > I tried doing this, but ended up with a core dump. Unfortunately, I ran > > out of time to work on it this week (real work calls), but I'll look > > into doing this this weekend. However, if someone has already done this > > I'm more than willing to accept example code. :) :) > > The code fragment I showed is approx. right as I've used > something similar a couple of times before but I will try to > turn it into a working example over the weekend. Thanks. If it included the MACROS so much the better. :) :) :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 11:04:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20793 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 11:04:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from camel14.mindspring.com (camel14.mindspring.com [207.69.200.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20758 for ; Wed, 11 Nov 1998 11:03:52 -0800 (PST) (envelope-from zenithar@mindspring.com) Received: from mindspring.com (user-38ldkk9.dialup.mindspring.com [209.86.210.137]) by camel14.mindspring.com (8.8.5/8.8.5) with ESMTP id OAA05164 for ; Wed, 11 Nov 1998 14:01:15 -0500 (EST) Message-ID: <3649DFED.FCD85FCB@mindspring.com> Date: Wed, 11 Nov 1998 13:05:17 -0600 From: Stephen Zepp Organization: Ack!Mud Home Page http://ackmud.nuc.net/ X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Gmake --using seperate directories for .c, .h, and .o files Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been trying for several days to write a simple Makefile that can handle having the .c and .h files in seperate directories, and place the .o files in a third directory. The executable is fine in the src dir. Paths: /dsmud /src : contains .c, Makefile, and executable /inc : contains .h /obj : repository for .o files. gmake is run from /dsmud/src. I've poured over the online version of the .info of gmake, and as far as I can tell we are doing what is correct, but we always get the error: gmake: *** No rule to make target `act_comm.o', needed by `darkshade'. Stop. It's my understanding that the vpath allows gmake to check the directories as set in INCDIR, SRCDIR and OBJDIR, but this doesn't seem to be happening. We've tried several dozen different forms for the rules, including removing all rules ( except darkshade and clean ) completely to force the implicits rules to take place, but nothing seems to work. We've also tried all the various variables, including $< $> and $* with no effect. System is a Pentium 90 running FreeBSD 2.2.7-STABLE Makefile is below. Anyone have any suggestions? :) TIA Stephen Zepp CC = gcc PROF = NOCRYPT = # # Source directories # SRCDIR=/usr/home2/dsmain/dsmud/src INCDIR=/usr/home2/dsmain/dsmud/inc # # Target directories # OBJDIR=/usr/home2/dsmain/dsmud/obj .CURDIR=. # Debugging flags possible: DEBUG_MEM DEBUG_MEM_CORRUPT DEBUG_MEM_DUP_FREE # DEBUG_MEM is most basic, just checks magic numbers when freeing # DEBUG_MEM_CORRUPT checks every free block to see if magic numbers ok, every # call to alloc_mem # Also makes calls to void check_free_mem(void) check for # corrupted free memory blocks. # DEBUG_MEM_DUP_FREE checks to see if freed blocks are overlapping every call # to mem_alloc. # # -DDEBUG_MEM -DDEBUG_MEM_CORRUPT -DDEBUG_MEM_DUP_FREE #-DDEBUG_MEM -DDEBUG_MEM_CORRUPT CFLAGS = -O -g3 -Wall -DACK_43 $(PROF) $(NOCRYPT) -I. -I$(SRCDIR) -I$(OBJDIR) -I$(INCDIR) #CFLAGS = -g3 -Wall ($PROF) $(NOCRYPT) L_FLAGS = -O -g $(PROF) #L_FLAGS = $(PROF) #VPATH=$(SRCDIR)/:$(INCDIR)/:$(OBJDIR)/ vpath %.c $(SRCDIR) vpath %.h $(INCDIR) vpath %.o $(OBJDIR) OBJS_darkshade = \ act_comm.o \ act_info.o \ act_move.o \ act_obj.o \ act_wiz.o \ comm.o \ const.o \ db.o \ fight.o \ handler.o \ interp.o \ magic.o \ magic2.o \ magic3.o \ magic4.o \ spell_dam.o \ mob_commands.o \ mob_prog.o \ save.o \ special.o \ update.o \ board.o \ areasave.o \ buildtab.o \ build.o \ write.o \ act_clan.o \ buildare.o \ hunt.o \ hash.o \ areachk.o \ clutch.o \ obj_fun.o \ macros.o \ trigger.o \ quest.o \ lists.o \ social-edit.o \ imc.o \ imc-mercbase.o \ imc-interp.o \ imc-version.o \ imc-mail.o \ imc-util.o \ imc-config.o \ imc-events.o \ ice.o \ icec.o \ icec-mercbase.o \ vampyre.o \ werewolf.o \ mount.o \ pdelete.o \ wizutil.o \ money.o \ ssm.o \ scheck.o \ rulers.o \ spendqp.o \ enchant.o \ sysdata.o \ strfuns.o \ mapper.o \ email.o \ overland.o \ file_io.o \ system.o \ vr_handler.o \ guilds.o \ interact.o \ craftspec.o darkshade: $(OBJS_darkshade) rm -f darkshade $(CC) $(L_FLAGS) -o darkshade $(OBJS_darkshade) -lm -lscrypt %.o: %.c $(CC) -c $(CFLAGS) $^ -o $@ # %.c: # $(CC) -c $(CFLAGS) $^ -o $@ clean: rm -f $(OBJS_darkshade) darkshade ../area/darkshade.core make To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 11:31:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23901 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 11:31:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA23837 for ; Wed, 11 Nov 1998 11:30:44 -0800 (PST) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id OAA11312; Wed, 11 Nov 1998 14:30:25 -0500 Date: Wed, 11 Nov 1998 14:30:25 -0500 (EST) From: "Ron G. Minnich" X-Sender: rminnich@terra To: hackers@FreeBSD.ORG Subject: pcibridge card (really) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a dolphin sci card that says it is a bridge. There appears to be no equivalent to: DATA_SET (pcidevice_set, scisc_device); for bridges. Other than modifying pcisupport.c is there any way to get the kernel to probe this card? It's not getting probed now as part of pci init. because pci thinks it is a bridge. Thanks ron Ron Minnich |"Using Windows NT, which is known to have some rminnich@sarnoff.com | failure modes, on a warship is similar to hoping (609)-734-3120 | that luck will be in our favor"- A. Digiorgio ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 11:35:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24718 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 11:35:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24702 for ; Wed, 11 Nov 1998 11:35:14 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id LAA22898; Wed, 11 Nov 1998 11:32:15 -0800 (PST) (envelope-from dillon) Date: Wed, 11 Nov 1998 11:32:15 -0800 (PST) From: Matthew Dillon Message-Id: <199811111932.LAA22898@apollo.backplane.com> To: Martin Cracauer Cc: =?iso-8859-1?Q?S=F8ren_Schmidt?= , Martin Cracauer , john@isi.co.jp, grog@lemis.com, hackers@FreeBSD.ORG, mike@smith.net.au, ticso@cicely.de Subject: Re: SCSI vs. DMA33.. References: <19981111164136.A29513@cons.org> <199811111730.SAA01133@freebsd.dk> <19981111184459.A10448@cons.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :What means "work"? I get a functional ccd filessystem over 4 :drives/4channels/2cards, so far so good. : :But while the throughput is raised when striping over different cards, :it isn't when striping over two channels on the same card. Or in other :words, the maximum thoughput for a :(2x) 4-drive, 4-channel, 2-card ccd is the same as for a :(2x) 2-drive, 2-channel, 2-card array, while :(1x) 2-drive, 2-channel, 1-card is excatly the same as for :(1x) 1-drive, 1-channel, 1-card. : :Hence my impression I can't use the two channels on one card :simultaneously. Is this really different for you? Do you have the :promise BIOS prom installed? : :Thanks for the fix, BTW, does this fix the IDE timeouts I see when :striping over 4 drives? : :Martin :-- You guys are all doing something wrong. First, everyone is using tiny dd's to test. Second, one SCSI channel is plenty sufficient to drive huge transfer rates through a 4-drive ccd stripe as I will demonstrate with our backup1 machine. Third, raw devices impose serialization limits and throughput depends heavily on the number of processes accessing the device. i.e. you can't pipeline to or from a raw device. Test it through the filesystem and read and write a lot of data to get around caches. Here are some tests I did with BEST's backup1 machine. It has a 36 GB 4xDisk stripe for a tape buffer. PPro 200. 4 x 9G drive (three Seagate ST19171W, 7200 RPM drives and one ST39173W 3600 rpm drive). All drives are connected to *ONE* SCSI ultra-wide controller (one 40 MBytes/sec SCSI bus). The tape units are connected to a second controller which is unused for all the tests below. CCD: 128 sector (64 KByte) interleave across four drives. And this is FreeBSD-stable, too, without CAM. Test #1: read raw device, 64K blocks, 256 MBytes total: backup1:/# dd if=/dev/rccd0d of=/dev/null bs=64k count=4096 268435456 bytes transferred in 8.617552 secs (31149851 bytes/sec) 31 MBytes/sec transfer rate. Because the disk does its own internal read-ahead. Test #2: write raw device, 64K blocks, 64 MBytes total: backup1:/# dd if=/dev/zero of=/dev/rccd0d bs=64k count=1024 67108864 bytes transferred in 12.152601 secs (5522181 bytes/sec) 5.5 MBytes/sec, because the OS/disk doesn't cache writes through the raw device. Test #3: write raw device, 64K blocks, 64 MBytes total, 4 dd's in parallel each doing 64 MBytes. foreach? dd if=/dev/zero of=/dev/rccd0d bs=64k count=1024 seek=$i & foreach? end [1] 8465 [2] 8466 [3] 8467 [4] 8468 67108864 bytes transferred in 22.503316 secs (2982177 bytes/sec) 67108864 bytes transferred in 22.510251 secs (2981258 bytes/sec) 67108864 bytes transferred in 22.529739 secs (2978679 bytes/sec) 67108864 bytes transferred in 22.542779 secs (2976956 bytes/sec) 12 MBytes/sec, again because the OS/disk doesn't cache writes through the raw device. Test #4: filesystem throughput. 1 GByte total, write 64K blocks newfs -i 32768 /dev/rccd0d backup1:/ccd# dd if=/dev/zero of=/ccd/test1 bs=64k count=16384 1073741824 bytes transferred in 41.744593 secs (25721698 bytes/sec) 25 MBytes/sec writing. <--------------- write FS throughput No chance of the OS or drive getting cache hits here, I'm writing a friggin gigabyte file! Test #5: filesystem throughput. 1 GByte total, read 64K blocks backup1:/ccd# dd if=/ccd/test1 of=/dev/null bs=64k count=16384 1073741824 bytes transferred in 34.051957 secs (31532456 bytes/sec) 31 MBytes/sec reading. <-------------- read FS throughput No chance of the OS or drive getting cache hits here, I'm reading a friggin gigabyte file! That's with *ONE* SCSI controller. An adaptec 2940UW. This is one of several reasons why you use SCSI if you need performance. You can't beat it for linear performance, and you can beat it for transactional performance either. If you have just one drive then sure, IDE will have similar linear performance. If you have two drives you may even see similar linear performance reading, but I would guess that you wouldn't see it writing. If you have several drives, SCSI beats the shit out of IDE reading and writing. For non-linear performance under load, the one-drive case will again yield similar results SCSI vs IDE. But the moment you start trying to random read two IDE devices on a single IDE controller, SCSI instantly scales to the two drives while the two IDE devices will not perform much better then one. After that, IDE goes into the shitpile for non-linear performance tests due to its command serialization. A SCSI bus with 4 drives on it will scale 4x for non-linear performance. Two IDE busses with 4 drives total will only scale 2x for non-linear performance. A SCSI bus with 8 drives on it will scale 8x for non-linear performance. I need non-linear performance on my web servers. My tape backup machine needs linear performance on the disk buffer since it is throwing multi-gigabyte files all over the place. A mail partition typically needs linear performance as well... gotta be able to copy those 20 MByte pop boxes :-). -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 13:03:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02678 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 13:03:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles249.castles.com [208.214.165.249]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02672 for ; Wed, 11 Nov 1998 13:03:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA05087; Wed, 11 Nov 1998 13:01:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811112101.NAA05087@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Ron G. Minnich" cc: hackers@FreeBSD.ORG Subject: Re: pcibridge card (really) In-reply-to: Your message of "Wed, 11 Nov 1998 14:30:25 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Nov 1998 13:00:59 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a dolphin sci card that says it is a bridge. There appears to be > no equivalent to: DATA_SET (pcidevice_set, scisc_device); > for bridges. Other than modifying pcisupport.c is there any way to get > the kernel to probe this card? It's not getting probed now as part of > pci init. because pci thinks it is a bridge. I presume 'sci' means 'scsi'? Does the card actually have a bridge on it? If so, what sort of bridge? If it's a PCI:PCI bridge, then you want to find the devices on the other side. If it's a generic bridge, then you just add a probe for the vendor/ device ID in the normal fashion (it should have a unique ID, not just the ID of the bridge chip). I've done this before with a custom board using an off-the-shelf generic bridge; if you want to look at the code, ask doconnor@gsoft.com.au, but you may need to prove that you're not obligated to disclose to Raytheon first. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 13:10:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03272 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 13:10:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gamefish.pcola.gulf.net (gamefish.pcola.gulf.net [198.69.72.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03267 for ; Wed, 11 Nov 1998 13:10:28 -0800 (PST) (envelope-from psalzman@gamefish.pcola.gulf.net) Received: from localhost (psalzman@localhost) by gamefish.pcola.gulf.net (8.9.1/8.9.1) with ESMTP id PAA20206; Wed, 11 Nov 1998 15:13:41 GMT (envelope-from psalzman@gamefish.pcola.gulf.net) Date: Wed, 11 Nov 1998 15:13:41 +0000 (GMT) From: Phillip Salzman To: "David E. Cross" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel Hacking stuffs (Bidirectional Parallel Port) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Have you looked at the Parallel Port Bus info (ie, ppbus)? I was going to use this while creating a driver for my parallel port scanner, but noticed it would require a more advanced knowledge of C than I had at the time. -- Phillip Salzman On Tue, 10 Nov 1998, David E. Cross wrote: > This in on 3.0-Current. I noticed that lpt.c is a one-way connection > only. I am attempting to add support for this for bidirectional > communication. I am running into a problem... I don't have any > documentation for the PC parallel port (the code is great, but since it > doesn't need to write data, I don't have things like the equivalent of > 'LPC_STB'). > > -- > David Cross > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 13:13:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03428 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 13:13:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA03417 for ; Wed, 11 Nov 1998 13:13:09 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 20944 invoked by uid 1001); 11 Nov 1998 21:12:49 +0000 (GMT) To: mike@smith.net.au Cc: rminnich@Sarnoff.COM, hackers@FreeBSD.ORG Subject: Re: pcibridge card (really) In-Reply-To: Your message of "Wed, 11 Nov 1998 13:00:59 -0800" References: <199811112101.NAA05087@dingo.cdrom.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 11 Nov 1998 22:12:49 +0100 Message-ID: <20942.910818769@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have a dolphin sci card that says it is a bridge. There appears to be > > no equivalent to: DATA_SET (pcidevice_set, scisc_device); > > for bridges. Other than modifying pcisupport.c is there any way to get > > the kernel to probe this card? It's not getting probed now as part of > > pci init. because pci thinks it is a bridge. > > I presume 'sci' means 'scsi'? No, SCI as in Scalable Coherent Interface. See www.dolphinics.com. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 13:35:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05815 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 13:35:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA05810 for ; Wed, 11 Nov 1998 13:35:36 -0800 (PST) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id QAA11851; Wed, 11 Nov 1998 16:34:34 -0500 Date: Wed, 11 Nov 1998 16:34:34 -0500 (EST) From: "Ron G. Minnich" X-Sender: rminnich@terra To: Mike Smith cc: hackers@FreeBSD.ORG Subject: Re: pcibridge card (really) In-Reply-To: <199811112101.NAA05087@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG SCI is scaleable coherent interface, not scsi. This is a distributed shared memory system that plugs into the PCI bus in this case. But the card is configured as a bridge, not a device. I can't figure out how to get freebsd to call my initialization code short of modifying pcisupport.c In other words, I'm not real clear on how bridges can be added to the kernel in the same modular way that pci cards are. Thanks ron Ron Minnich |"Using Windows NT, which is known to have some rminnich@sarnoff.com | failure modes, on a warship is similar to hoping (609)-734-3120 | that luck will be in our favor"- A. Digiorgio ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 13:37:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05945 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 13:37:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles249.castles.com [208.214.165.249]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05933 for ; Wed, 11 Nov 1998 13:37:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA05287; Wed, 11 Nov 1998 13:34:27 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811112134.NAA05287@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: sthaug@nethelp.no cc: mike@smith.net.au, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG Subject: Re: pcibridge card (really) In-reply-to: Your message of "Wed, 11 Nov 1998 22:12:49 +0100." <20942.910818769@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Nov 1998 13:34:26 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I have a dolphin sci card that says it is a bridge. There appears to be > > > no equivalent to: DATA_SET (pcidevice_set, scisc_device); > > > for bridges. Other than modifying pcisupport.c is there any way to get > > > the kernel to probe this card? It's not getting probed now as part of > > > pci init. because pci thinks it is a bridge. > > > > I presume 'sci' means 'scsi'? > > No, SCI as in Scalable Coherent Interface. See www.dolphinics.com. Gotcha. The picture on their web page isn't really big enough, but the device with the PCI interface doesn't look like any generic bridge part that I recognise. Without knowing much about the architecture of the card, I'm slightly surprised that they'd call it a "bridge"; it seems to be a datagram mover rather than a reflective memory interface. Still, my basic comments hold - you should be able to catch it by the device/vendor ID regardless of class. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 13:40:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06222 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 13:40:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from animaniacs.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA06214 for ; Wed, 11 Nov 1998 13:40:48 -0800 (PST) (envelope-from jamie@itribe.net) Received: from localhost (jamie@localhost) by animaniacs.itribe.net (950413.SGI.8.6.12/950213.SGI.AUTOCF) via SMTP id QAA03917; Wed, 11 Nov 1998 16:12:57 -0500 Date: Wed, 11 Nov 1998 16:12:57 -0500 (EST) From: Jamie Bowden To: Joel Ray Holveck cc: Doug Rabson , Sren Schmidt , Jacques Vidrine , sgk@troutmask.apl.washington.edu, nate@mt.sri.com, kkennawa@physics.adelaide.edu.au, dnelson@emsphone.com, rivers@dignus.com, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <86k913hy3q.fsf@detlev.UUCP> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10 Nov 1998, Joel Ray Holveck wrote: > >>> Why would we not put a real linux uname(1) in /compat/linux/usr/bin? > >>> This is an emulation issue. Why impact the BSD userland sources? > >> Hear hear!! > > I imagine that the install script is run by /bin/sh, not > > /compat/linux/bin/sh so it will get the regular /usr/bin/uname > > whatever is present in /compat/linux/usr/bin. > > I have yet to hear of any solutions that don't require a hack to the > install procedure (eg, setting an environment variable). Unless > somebody comes up with an idea that would magically detect what > environment a given script wants, I would recommend putting a Linux > uname in /copmat/linux where it belongs, and the install procedure's > PATH can have /compat/linux ahead of /. This is easy to implement, > keeps the core of FreeBSD pure, and paves the way for future > similarities. chroot /compat/linux ; install Jamie Bowden -- Systems Administrator, iTRiBE.net If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 13:46:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06723 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 13:46:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles249.castles.com [208.214.165.249]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06715 for ; Wed, 11 Nov 1998 13:46:30 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA05356; Wed, 11 Nov 1998 13:43:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811112143.NAA05356@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Ron G. Minnich" cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: pcibridge card (really) In-reply-to: Your message of "Wed, 11 Nov 1998 16:34:34 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Nov 1998 13:43:40 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > SCI is scaleable coherent interface, not scsi. This is a distributed > shared memory system that plugs into the PCI bus in this case. But the > card is configured as a bridge, not a device. I can't figure out how to > get freebsd to call my initialization code short of modifying pcisupport.c > In other words, I'm not real clear on how bridges can be added to the > kernel in the same modular way that pci cards are. Ok, belay my last comment - it does DSM after all. The PCI code *should* be passing the card's vendor/device ID to all the PCI drivers, and that should mean that your driver sees it. It sounds like the "generic chipset" code is ending up in the linker set before your driver though, so it claims it early. You can check to see if this is the case by diking out the call to generic_pci_bridge(). This is germane to Garret's comments about needing to separate 'catchall' drivers from the device-specific ones; if it'll help you at all we can implement an interim solution that will cover what seems to be your problem. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 13:47:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06816 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 13:47:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp.algonet.se (tomei.algonet.se [194.213.74.114]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA06809 for ; Wed, 11 Nov 1998 13:47:30 -0800 (PST) (envelope-from mal@algonet.se) Received: (qmail 3074 invoked from network); 11 Nov 1998 22:47:09 +0100 Received: from kairos.algonet.se (194.213.74.18) by tomei.algonet.se with SMTP; 11 Nov 1998 22:47:09 +0100 Received: (mal@localhost) by kairos.algonet.se (8.8.8+Sun/8.6.12) id WAA10051; Wed, 11 Nov 1998 22:47:09 +0100 (MET) Date: Wed, 11 Nov 1998 22:47:09 +0100 (MET) Message-Id: <199811112147.WAA10051@kairos.algonet.se> X-Authentication-Warning: kairos.algonet.se: mal set sender to mal@kairos.algonet.se using -f From: Mats Lofkvist To: hackers@FreeBSD.ORG Subject: Re: SCSI vs. DMA33.. References: <199811111842.KAA18548@hub.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I must say, I'm surprised. This makes it look like there's more of a > performance hit with concurrent requests on SCSI than on IDE. Let's > look at the performance hits as a percentage (there's some guesswork > which is which, of course, but only a little): > > alone 2 together % drop > wd2 10.2 8.8 14 > wd3 10.0 8.8 12 > da0 5.7 3.3 42 > da1 3.7 2.7 23 Don't know what conclusions to draw, but I don't see this decrease in performance with concurrent requests. Current-smp on a providence mb (7880 on board) with a quantum viking 4.5GB uw (da0) and a vikingII 4.5GB uw (da1): bash# dd if=/dev/rda0c bs=32k count=10000 of=/dev/null 10000+0 records in 10000+0 records out 327680000 bytes transferred in 30.950317 secs (10587291 bytes/sec) bash# dd if=/dev/rda1c bs=32k count=10000 of=/dev/null10000+0 records in 10000+0 records out 327680000 bytes transferred in 23.328261 secs (14046482 bytes/sec) bash# dd if=/dev/rda0c bs=32k count=10000 of=/dev/null & dd if=/dev/rda1c bs=32k count=13000 of=/dev/null [1] 375 13000+0 records in13000+0 records out 425984000 bytes transferred in 30.822861 secs (13820391 bytes/sec) bash# 10000+0 records in 10000+0 records out 327680000 bytes transferred in 31.760830 secs (10317111 bytes/sec) alone 2 together % drop da0 10.6 10.3 1.6 da1 14.0 13.8 2.6 _ Mats Lofkvist mal@algonet.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 14:24:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10567 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 14:24:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10562 for ; Wed, 11 Nov 1998 14:24:54 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from o2.cs.rpi.edu (root@o2.cs.rpi.edu [128.113.96.156]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id RAA04716; Wed, 11 Nov 1998 17:24:26 -0500 (EST) Received: from localhost (crossd@localhost) by o2.cs.rpi.edu (8.9.1a/8.9.1) with ESMTP id RAA03311; Wed, 11 Nov 1998 17:24:26 -0500 (EST) X-Authentication-Warning: o2.cs.rpi.edu: crossd owned process doing -bs Date: Wed, 11 Nov 1998 17:24:25 -0500 From: "David E. Cross" To: Phillip Salzman cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel Hacking stuffs (Bidirectional Parallel Port) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Nov 1998, Phillip Salzman wrote: > > Have you looked at the Parallel Port Bus info (ie, ppbus)? > > I was going to use this while creating a driver for my parallel > port scanner, but noticed it would require a more advanced knowledge of C > than I had at the time. > > -- > Phillip Salzman I had not looked at it until you mentioned it. It suffers the same problems that the lpt.c driver does. The way these drivers gain their bidirectional ability is by tying the status lines (ACK, BUSY, PE, ERROR, and 1 I forget) to the data lines, allowing 5 bits of data at a time, one of these bits is used as a framing signal (0x1x means high nibble is being transfered, 0x0x is the low nibble). Am I correct in thinking that 'modern' bidirectional ports and printers have 8 lines dedicated to carrying data in both directions? Or is this the only way it has ever been, and ever will be? -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 14:27:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10803 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 14:27:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles249.castles.com [208.214.165.249]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10796 for ; Wed, 11 Nov 1998 14:27:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA05644; Wed, 11 Nov 1998 14:25:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811112225.OAA05644@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Tony Overfield cc: Terry Lambert , hackers@FreeBSD.ORG Subject: Re: disk sector ordering (Was: Reading/writing /usr/ports is VERY slow) In-reply-to: Your message of "Wed, 11 Nov 1998 00:25:42 CST." <3.0.3.32.19981111002542.00752be4@bugs.us.dell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Nov 1998 14:25:04 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 3 Sep 1998 01:08:15 +0000 (GMT), Terry Lambert said: > >Specifically, most modern disks record tracks in reverse sector > >order, and as soon as you seek to the track, they start reading > >(and buffering data) until they hit the sector in the track that > >you were actually seeking to find. > > Sorry about taking the side-track with such an old message, but > I've been trying to figure out what you said here and I just don't > get it. Can you explain this? Is there some reason you want to > avoid the concurrency you normally achieve by having the sectors > in the normal order? The goal here is to minimise time-on-track while optimising the cache contents once you leave the track. The expectation is that read behaviour is generally forward sequential - that one request for a region will be followed at some stage by a request for a region immediately following the first. This request may not come immediately, however, but it will generally come soon (and this is the only case easy to optimise for). So if you have a request for blocks 4-7 on a track, and when you get to the track you're passing block 14, you read 13 down to 4 and park them in the cache. You've gotten the blocks you want as quickly as possible, and as a benefit you've also cached 8-13 without losing any time. If the read is immediately followed by a request for 8-13, you don't have to wait a whole rotation as they're already in the cache. (If the sectors were ordered forwards, by the time you'd transferred 4-7 to the host you would be out of luck for 8-11.) You can also win in this case if you simply read ahead. If the request is followed by a request for another region of the disk, you can go straight there, improving your response time. And if *that* request is then followed by the request for 8-11, you can still satisfy it from the cache. If you were only doing read-ahead, you would have aborted the read-ahead as soon as the next transaction arrived. On average, you can expect to get a free half-track readahead simply by reversing the order of sectors on the disk. What used to be dead time (waiting for the target sector to appear) is no longer wasted. I hope that helps... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 14:32:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11351 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 14:32:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles249.castles.com [208.214.165.249]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11293 for ; Wed, 11 Nov 1998 14:32:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA05676; Wed, 11 Nov 1998 14:28:15 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811112228.OAA05676@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "David E. Cross" cc: Phillip Salzman , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel Hacking stuffs (Bidirectional Parallel Port) In-reply-to: Your message of "Wed, 11 Nov 1998 17:24:25 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Nov 1998 14:28:15 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On Wed, 11 Nov 1998, Phillip Salzman wrote: > > > > > Have you looked at the Parallel Port Bus info (ie, ppbus)? > > > > I was going to use this while creating a driver for my parallel > > port scanner, but noticed it would require a more advanced knowledge of C > > than I had at the time. > > > > -- > > Phillip Salzman > > I had not looked at it until you mentioned it. It suffers the same > problems that the lpt.c driver does. The way these drivers gain their > bidirectional ability is by tying the status lines (ACK, BUSY, PE, ERROR, > and 1 I forget) to the data lines, allowing 5 bits of data at a time, one > of these bits is used as a framing signal (0x1x means high nibble is being > transfered, 0x0x is the low nibble). > > Am I correct in thinking that 'modern' bidirectional ports and printers > have 8 lines dedicated to carrying data in both directions? Or is this > the only way it has ever been, and ever will be? There are several different (incompatible) ways of shifting bidirectional data. The nibble mode you describe is the lowest common denominator. There's also "true bidirectional" mode, where the 8 data lines are open-collector outputs, so driving them high lets you listen to the other end. Then there are the EPP 1.7 and EPP 1.9 modes, and ECP to finish it all off. Ppbus either supports or will support all of these, depending on the capabilities of your hardware. You can see the nibble and "true" modes in action in the 'vpo' driver. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 14:36:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11823 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 14:36:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11817 for ; Wed, 11 Nov 1998 14:36:35 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from o2.cs.rpi.edu (root@o2.cs.rpi.edu [128.113.96.156]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id RAA04904; Wed, 11 Nov 1998 17:35:53 -0500 (EST) Received: from localhost (crossd@localhost) by o2.cs.rpi.edu (8.9.1a/8.9.1) with ESMTP id RAA03202; Wed, 11 Nov 1998 17:35:53 -0500 (EST) X-Authentication-Warning: o2.cs.rpi.edu: crossd owned process doing -bs Date: Wed, 11 Nov 1998 17:35:53 -0500 From: "David E. Cross" To: Mike Smith cc: Phillip Salzman , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel Hacking stuffs (Bidirectional Parallel Port) In-Reply-To: <199811112228.OAA05676@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Nov 1998, Mike Smith wrote: > There are several different (incompatible) ways of shifting > bidirectional data. > > The nibble mode you describe is the lowest common denominator. There's > also "true bidirectional" mode, where the 8 data lines are > open-collector outputs, so driving them high lets you listen to the > other end. Then there are the EPP 1.7 and EPP 1.9 modes, and ECP to > finish it all off. > > Ppbus either supports or will support all of these, depending on the > capabilities of your hardware. You can see the nibble and "true" modes > in action in the 'vpo' driver. Ahh, this is what I was looking for. I had looked in lpt.c and nlpt.c (from the ppbus device directory). I will check out 'vpo' now, thank you :) -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 14:39:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12031 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 14:39:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11969 for ; Wed, 11 Nov 1998 14:39:17 -0800 (PST) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.8/8.7.3) id XAA10880; Wed, 11 Nov 1998 23:34:22 +0100 (CET) Message-ID: <19981111233422.A10862@cons.org> Date: Wed, 11 Nov 1998 23:34:22 +0100 From: Martin Cracauer To: Matthew Dillon Cc: =?iso-8859-1?Q?S=F8ren_Schmidt?= , grog@lemis.com, hackers@FreeBSD.ORG Subject: Re: SCSI vs. DMA33.. References: <19981111164136.A29513@cons.org> <199811111730.SAA01133@freebsd.dk> <19981111184459.A10448@cons.org> <199811111932.LAA22898@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199811111932.LAA22898@apollo.backplane.com>; from Matthew Dillon on Wed, Nov 11, 1998 at 11:32:15AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199811111932.LAA22898@apollo.backplane.com>, Matthew Dillon wrote: > You guys are all doing something wrong. First, everyone is using > tiny dd's to test. I'm testing with bonnie inside a filesystem, using a RAM-limited kernel (i.e. 15 MB RAM for 50 MB files). Bonnie's seek test is somewhat interesting even for those multiple-process accesses. As long as you have really independent busses for your IDE drives, IDE may got quite fast. And BTW, if you use benchmarks writing to /dev/null for inter-system comarisions you'll quickly notice that this isn't the end of the story. It is not new for me that one UW SCSI channel has enough bandwidth for the task at hand. However, 4 SCSI drives and 1 UW SCSI controller and still much more expensive than 1 or 2 Promise IDE cards (depends on whether your mainboard has UIDE) and 4 IDE drives. It's bad that the Promise controllers don't work as they should and don't allow simultaneous access to both channels. But for now I am not sure that's god given and maybe there's a workaround and that's why we're discussing these things here. [benchmarks deleted] > This is one of several reasons why you use SCSI if you need performance. > You can't beat it for linear performance, and you can beat it for > transactional performance either. If you have just one drive then > sure, IDE will have similar linear performance. If you have two drives > you may even see similar linear performance reading, but I would guess > that you wouldn't see it writing. My tests so far see the IDE ccd writing as fast at it reads. The numbers aren't impressive since I can't get past the 2-channel limit for now. > If you have several drives, > SCSI beats the shit out of IDE reading and writing. As long as you have one bus per drive, I am not convinced that IDE must be worse here. > For non-linear performance under load, the one-drive case will again > yield similar results SCSI vs IDE. But the moment you start trying > to random read two IDE devices on a single IDE controller, SCSI instantly > scales to the two drives while the two IDE devices will not perform much > better then one. After that, IDE goes into the shitpile for > non-linear performance tests due to its command serialization. A SCSI > bus with 4 drives on it will scale 4x for non-linear performance. Two > IDE busses with 4 drives total will only scale 2x for non-linear > performance. A SCSI bus with 8 drives on it will scale 8x for non-linear > performance. You didn't read what I wrote. I am aware of these issue and have 4 drives, 4 channels on two cards. That it doesn't work because the two channels on each Promise card block each other is a different matter that was not foreseeable. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 15:09:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15763 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 15:09:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15757 for ; Wed, 11 Nov 1998 15:09:25 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id PAA00287; Wed, 11 Nov 1998 15:03:15 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id PAA05648; Wed, 11 Nov 1998 15:03:14 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id PAA02167; Wed, 11 Nov 1998 15:03:13 -0800 (PST) From: Don Lewis Message-Id: <199811112303.PAA02167@salsa.gv.tsc.tdk.com> Date: Wed, 11 Nov 1998 15:03:13 -0800 In-Reply-To: Bakul Shah "Re: Supporting more than FD_SETSIZE fd's" (Nov 11, 8:44am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Bakul Shah , Terry Lambert Subject: Re: Supporting more than FD_SETSIZE fd's Cc: nate@mt.sri.com (Nate Williams), hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Nov 11, 8:44am, Bakul Shah wrote: } Subject: Re: Supporting more than FD_SETSIZE fd's } There is a way to select on all the file descriptors your } program can open. The idea is to use getdtablesize() to find } the number of such descriptors and just allocate an array of } fd_mask. Something like: } } int fd_setsize = getdtablesize(); } int fd_tablesize = howmany(max_fd_count, NFDBITS); } fd_mask* readfds = calloc(fd_tablesize, sizeof(fd_mask)); } fd_mask* tmp_readfds = calloc(fd_tablesize, sizeof(fd_mask)); You may not want to do this. Some implementations return may return very large numbers from getdtablesize(), like INT_MAX. I've heard bug reports about software that wants to close all fds other than 0, 1, and 2 between a fork() and an exec(), and it does so by looping over all the numbers from 3 to the return value from getdtablesize() and executing close() on each. This is horribly slow if getdtablesize() returns an unreasonably large number. What you could do is allocate your fd_masks based on maxfd_in_use plus some slop and reallocate it to a larger size whenever maxfd_in_use increases enough to make it necessary. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 15:12:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16025 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 15:12:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16020 for ; Wed, 11 Nov 1998 15:12:29 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id PAA03393; Wed, 11 Nov 1998 15:16:17 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811112316.PAA03393@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname In-Reply-To: <199811110906.CAA08497@usr02.primenet.com> from Terry Lambert at "Nov 11, 1998 9: 6:47 am" To: tlambert@primenet.com (Terry Lambert) Date: Wed, 11 Nov 1998 15:16:17 -0800 (PST) Cc: jb@cimlogic.com.au, tlambert@primenet.com, crossd@cs.rpi.edu, jkh@time.cdrom.com, nate@mt.sri.com, hackers@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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Terry Lambert: > I was asking why you didn't just patch the install script as one of > the standard patchfiles you applied to the programs from the > original vendor when you made the "ports" entry for the program. > > In other words, when I go to install the thing from FreeBSD 3.0.1 > from the sysinstall menu, it should ask me for the CDROM from > the program vendor, mount it, copy the install script to /tmp, > patch the install script to route around the uname dependency on > Linux (preferrably by adding a FreeBSD target, so the patch can > be given back to the vendor for the next time they burn CDROMs), > and then the install would "just work". > > I'd do the job, but I don't have a copy of the CDROM. > Well, I started the thread, so here goes. It isn't that simple, the script also checks to see that it was executed from /cdrom/x86-1.7/linux. You can work around that I suppose once you find all the dependency. Next, you need to specify where the libgcc and libf2c for linux live. This can be fixed after the install. There other idiosyncracies that need to be adjusted. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 15:17:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16557 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 15:17:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16551 for ; Wed, 11 Nov 1998 15:17:56 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id PAA03416; Wed, 11 Nov 1998 15:21:52 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811112321.PAA03416@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname In-Reply-To: <199811110830.BAA06529@usr02.primenet.com> from Terry Lambert at "Nov 11, 1998 8:30:57 am" To: tlambert@primenet.com (Terry Lambert) Date: Wed, 11 Nov 1998 15:21:52 -0800 (PST) Cc: crossd@cs.rpi.edu, jkh@time.cdrom.com, nate@mt.sri.com, hackers@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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Terry Lambert: > > Here is the nice little uname test from the vendor's install script: > > > > # what type of target? uname test elided. > > Any you don't path this as part of the "port" you made for the > compiler? > I haven't made a port of the compiler. I have no itntentions of doing so, because you need to have the vendor's cdrom. Note: you can download the Portland Groups' products from the internet. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 16:28:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26857 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 16:28:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26849 for ; Wed, 11 Nov 1998 16:28:06 -0800 (PST) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id TAA09171; Wed, 11 Nov 1998 19:27:06 -0500 (EST) Received: from john.baldwinfamily.org (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id TAA04725; Wed, 11 Nov 1998 19:27:06 -0500 (EST) Message-ID: X-Mailer: XFMail 1.3 [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: <199811112321.PAA03416@troutmask.apl.washington.edu> Date: Wed, 11 Nov 1998 19:27:05 -0500 (EST) Reply-To: jobaldwi@vt.edu Organization: Virginia Tech From: John Baldwin To: Steve Kargl Subject: Re: linux software installation and uname Cc: hackers@FreeBSD.ORG, nate@mt.sri.com, jkh@time.cdrom.com, crossd@cs.rpi.edu, (Terry Lambert) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- On 11-Nov-98 Steve Kargl wrote: > According to Terry Lambert: >> > Here is the nice little uname test from the vendor's install script: >> > >> > # what type of target? > > uname test elided. >> >> Any you don't path this as part of the "port" you made for the >> compiler? >> > > I haven't made a port of the compiler. I have no itntentions of > doing so, because you need to have the vendor's cdrom. And you have to manually download the US version of Netscape Communicator 4, but there's a port for that in /usr/ports/www, so it's been done before. Some commercial skeleton ports would probably be nice. It can only help other *BSD users that use the same product, and it can't hurt anyone that I can see. > -- > Steve > > finger kargl@troutmask.apl.washington.edu > http://troutmask.apl.washington.edu/~clesceri/kargl.html - --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc Birth is the leading cause of death. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNkoqkYjYza302vYpAQGAgwL/Rd+Mi1en5ignBsT0DJCTvrW0XDrTGJnE KeB3Lu77MPmX4BxqplpstBBKgqIvGnbNQJUtw+H68ooQyePAZYPPXPpRHBmtG/z2 x6Vrz50knztf31mKTPMudv8EASUGQ6rv =OaKp -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 17:23:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA02484 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 17:23:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02479 for ; Wed, 11 Nov 1998 17:23:16 -0800 (PST) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id XAA20599; Wed, 11 Nov 1998 23:22:35 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199811120122.XAA20599@roma.coe.ufrj.br> Subject: Re: kld screensavers In-Reply-To: <199811030302.MAA01789@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Nov 3, 98 12:02:37 pm" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Wed, 11 Nov 1998 23:22:35 -0200 (EDT) Cc: karpen@ocean.campus.luth.se, hackers@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #define quoting(Kazutaka YOKOTA) // >According to Doug Rabson: // >> Thats more or less what I was suggesting. Simple screen savers wouldn't // >> even need an event handler. Maybe something like: // >[suggestion removed] // > // >While this is being discussed, I'd like to bring something up that I've // >wanted for a long time, and brought up before. Why not make to so that // >each screensaver register itself with a timeout, a priority and a flag // >that says if it's fallthrough or not? That way you can have multiple // >screensavers installed, and they get called as approriate. // > // >I haven't looked at the current code, I'm affraid, so go easy on me. // >Example: // > // >Three screensavers: (say default prio is 5) // > // >lock: prio 1, 10 minutes, fallthrough (Demands password to release screen // >) // >green: prio 4, 20 minutes (Turn screen off) // >stars: prio 5, 5 minutes (Twinkle, twinkle, little star) // [...] // // I am not sure if we want to have this kind of screen saver stack. It // will complicate things a lot: multiple saver module management, // priority management, flag checking... Is this worth the effort? I would be happy enough with the green saver included as a second timer (configurable by vidcontrol, off course) in every other saver. It must be easy to do. Say: 5 minutes -> activate the daemon saver more 5 minutes -> green power off Maybe this should be extended to deal with the different green levels: blank, snooze, power off, etc. I don't know green enough to discuss this. BTW: Talking about decoupling video driver, the screen saver drawing functions are decoupled from the video driver (assuming the last propositions I've heard in this list), but the green shutdown would be a internal function of the display device should it be a monitor, a serial port, or even a printer, although green would probably mean nothing on the laters. Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 17:25:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA02679 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 17:25:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02668 for ; Wed, 11 Nov 1998 17:24:56 -0800 (PST) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id XAA20607; Wed, 11 Nov 1998 23:24:22 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199811120124.XAA20607@roma.coe.ufrj.br> Subject: Re: Libretto probes for 21 PCI busses In-Reply-To: <3649C56D.41C6@cs.strath.ac.uk> from Roger Hardiman at "Nov 11, 98 05:12:13 pm" To: roger@cs.strath.ac.uk (Roger Hardiman) Date: Wed, 11 Nov 1998 23:24:22 -0200 (EDT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #define quoting(Roger Hardiman) // Hi, // I just installed 3.0-RELEASE on my Libretto 100CT. // // The boot sequence works fine, but it probes for 21 PCI busses // Probing PCI Bus 0 // Probing PCI Bus 1 If this helps, I'm getting this also on my Toshiba 305CDS since I upgraded to 3.0. I was intending to study this a little more before reporting, but since you started... Should this move to -mobile ? Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 19:11:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13439 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 19:11:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gershwin.tera.com ([207.224.230.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13431 for ; Wed, 11 Nov 1998 19:11:09 -0800 (PST) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (tao.tera.com [207.108.223.55]) by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id TAA01301 for ; Wed, 11 Nov 1998 19:10:50 -0800 (PST) Received: (from kline@localhost) by tao.thought.org (8.8.8/8.7.3) id TAA03072 for hackers@freebsd.org; Wed, 11 Nov 1998 19:10:38 -0800 (PST) From: Gary Kline Message-Id: <199811120310.TAA03072@tao.thought.org> Subject: bsd make to gnu make conversion, anyone?? To: hackers@FreeBSD.ORG (Hackers Mailing List) Date: Wed, 11 Nov 1998 19:10:38 -0800 (PST) Organization: <> thought.org: public access uNix in service... <> X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are there any makefile senior Wizards out there who can clue me in on the translation of this pmake LANGS= en_US.ISO_8859-1 fr_FR.ISO_8859-1 de_DE.ISO_8859-1 FILES= ${LANGS:S/$/.mv.cat/} CLEANFILES+= ${FILES} . . . for lang in ${LANGS} ${lang}.mv.cat: ${.CURDIR}/nls/${lang}/mv.msg gencat -new ${.TARGET} ${.ALLSRC} .endfor beforeinstall: .for lang in ${LANGS} ${INSTALL} ${COPY} -o ${BINOWN} -g ${BINGRP} -m ${NOBINMODE} \ ${lang}.mv.cat ${DESTDIR}${NLSDIR}/${lang}/mv.cat .endfor into gnu make style? I'd be much obliged for any tips. (I'm close--to the point where I'm using bin/sh code and $$var for most of the variables. But wondering, hoping, that there is a less contorted way.) Thanks, gary -- Gary D. Kline kline@tao.thought.org Public service uNix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 19:56:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18258 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 19:53:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from papillon.lemis.com (freebie.lemis.com [139.130.136.133] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18251 for ; Wed, 11 Nov 1998 19:53:52 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by papillon.lemis.com (8.9.1/8.6.12) with ESMTP id MAA00731; Thu, 12 Nov 1998 12:07:28 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA04011; Thu, 12 Nov 1998 12:07:54 +1030 (CST) Message-ID: <19981112120754.E463@freebie.lemis.com> Date: Thu, 12 Nov 1998 12:07:54 +1030 From: Greg Lehey To: Terry Lambert , "Justin T. Gibbs" Cc: dillon@apollo.backplane.com, hackers@FreeBSD.ORG Subject: Re: SCSI tagged queueing and softupdates References: <199811110257.TAA28938@narnia.plutotech.com> <199811110854.BAA07678@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811110854.BAA07678@usr02.primenet.com>; from Terry Lambert on Wed, Nov 11, 1998 at 08:54:07AM +0000 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 11 November 1998 at 8:54:07 +0000, Terry Lambert wrote: >>> The SCSI command set allows you to flag >>> tags for ordered sequencing. >> >> Yes, but softupdates does not make use of this mechanism even though, >> via 'bowrite' it could. > > I agree on the value of this. But this seems to infringe on the > USL patent for "Delayed Ordered Writes". Details? It's been a while since the B_ORDERED flag (and bowrite) made the system: revision 1.33 date: 1996/09/06 05:35:00; author: gibbs; state: Exp; lines: +6 -4 Add B_ORDERED buffer flag and prototype for the bowrite function. Bowrite guarantees that buffers queued after a call to bowrite will be written after the specified buffer (to a particular device). Bowrite does this either by taking advantage of hardware ordering support (e.g. tagged queueing on SCSI devices) or by resorting to a synchronous write. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 20:04:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19100 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 20:04:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19093 for ; Wed, 11 Nov 1998 20:04:51 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id UAA06570; Wed, 11 Nov 1998 20:57:37 -0700 (MST) Date: Wed, 11 Nov 1998 20:57:37 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199811120357.UAA06570@narnia.plutotech.com> To: Greg Lehey cc: hackers@FreeBSD.ORG Subject: Re: SCSI tagged queueing and softupdates X-Newsgroups: pluto.freebsd.hackers In-Reply-To: <199811110257.TAA28938@narnia.plutotech.com> <199811110854.BAA07678@usr02.primenet.com> <19981112120754.E463@freebie.lemis.com> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Bowrite guarantees that buffers queued after a call to bowrite will > be written after the specified buffer (to a particular device). > Bowrite does this either by taking advantage of hardware ordering support > (e.g. tagged queueing on SCSI devices) or by resorting to a synchronous write. bowrite never does a synchronous write. Both the kernel elevator sort and the SCSI tagged queuing code honor the B_ORDERED flag, so even devices that cannot perform concurrent I/O can safely handled an ordered write in a non-blocking fashion. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 20:34:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22638 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 20:34:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22633 for ; Wed, 11 Nov 1998 20:34:48 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id PAA14636 for ; Thu, 12 Nov 1998 15:04:27 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 12 Nov 1998 15:00:09 +1030 (CST) From: "Daniel O'Connor" To: freebsd-hackers@FreeBSD.ORG Subject: PCI interrupts Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We make a custom data acquisition PCI card, and we are experiencing some problems :) I am wondering if anyone could tell me how FreeBSD would handle having the PCI interrupt line continually asserted after calling the interrupt handler for the device in question. ie would the interrupt routine keep getting called? or would it only get called once? This probably intersects with PCI specifics as well, so I'll mail the PCI mailing list too.. Any help gratefully received.. I could probably send you some real Australian beer if you want =) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 20:48:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24074 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 20:48:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from yonge.cs.toronto.edu (yonge.cs.toronto.edu [128.100.1.8]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA24069 for ; Wed, 11 Nov 1998 20:48:26 -0800 (PST) (envelope-from dholland@cs.toronto.edu) Received: from qew.cs.toronto.edu ([128.100.2.15]) by yonge.cs.toronto.edu with SMTP id <86514-8537>; Wed, 11 Nov 1998 23:47:56 -0500 Received: by qew.cs.toronto.edu id <37814-2936>; Wed, 11 Nov 1998 23:47:27 -0500 Subject: Re: bsd make to gnu make conversion, anyone?? From: David Holland To: kline@tao.thought.org (Gary Kline) Date: Wed, 11 Nov 1998 23:47:27 -0500 Cc: hackers@FreeBSD.ORG In-Reply-To: <199811120310.TAA03072@tao.thought.org> from "Gary Kline" at Nov 11, 98 10:10:38 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <98Nov11.234727edt.37814-2936@qew.cs.toronto.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Are there any makefile senior Wizards out there who can clue me > in on the translation of this pmake gmake doesn't have an equivalent for .for, so you're stuck with making a mess. > > LANGS= en_US.ISO_8859-1 fr_FR.ISO_8859-1 de_DE.ISO_8859-1 > FILES= ${LANGS:S/$/.mv.cat/} > CLEANFILES+= ${FILES} > > . > . > . > > for lang in ${LANGS} > ${lang}.mv.cat: ${.CURDIR}/nls/${lang}/mv.msg > gencat -new ${.TARGET} ${.ALLSRC} > .endfor This you can probably do with %.mv.cat: ${.CURDIR}/nls/%/mv.msg gencat -new $@ $^ (for some suitable replacement for ${.CURDIR}) > beforeinstall: > .for lang in ${LANGS} > ${INSTALL} ${COPY} -o ${BINOWN} -g ${BINGRP} -m ${NOBINMODE} \ > ${lang}.mv.cat ${DESTDIR}${NLSDIR}/${lang}/mv.cat > .endfor try ${patsubst %, install-%, ${LANGS}}: install-%: ${INSTALL} -c -o root -m 644 ${patsubst install-%, %.mv.cat, $@} \ ${DESTDIR}${NLSDIR}/${patsubst install-%, %, $@}/mv.cat beforeinstall: ${patsubst %, install-%, ${LANGS}} but that might not work and in any event it's pretty gross. You might be better off compiling bsd make on whatever box you're using. -- - David A. Holland | (please continue to send non-list mail to dholland@cs.utoronto.ca | dholland@hcs.harvard.edu. yes, I moved.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 21:24:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26600 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 21:24:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles205.castles.com [208.214.165.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26594 for ; Wed, 11 Nov 1998 21:24:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA07759; Wed, 11 Nov 1998 21:16:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811120516.VAA07759@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PCI interrupts In-reply-to: Your message of "Thu, 12 Nov 1998 15:00:09 +1030." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Nov 1998 21:16:31 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I am wondering if anyone could tell me how FreeBSD would handle having > the PCI interrupt line continually asserted after calling the interrupt > handler for the device in question. ie would the interrupt routine keep > getting called? or would it only get called once? If the system is expecting a level-triggered interrupt, that is *extremely* bad. The interrupt handler will spin forever. The same goes for any other operating system. Your interrupt handler *must* clear the interrupt source before returning. [off topic] > Any help gratefully received.. I could probably send you some real Australian > beer if you want =) Just make sure there's some cold there in the 'fridge. I get back around the 30th or so of this month, and I've a week to kill in Adelaide. 8) Anything you think might go down well as tokens from afar? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 21:45:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29283 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 21:45:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29272 for ; Wed, 11 Nov 1998 21:45:41 -0800 (PST) (envelope-from aron@cs.rice.edu) Received: from noel.cs.rice.edu (noel.cs.rice.edu [128.42.1.136]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id XAA15170 for ; Wed, 11 Nov 1998 23:45:19 -0600 (CST) From: Mohit Aron Received: (from aron@localhost) by noel.cs.rice.edu (8.9.0/8.9.0) id XAA00292 for freebsd-hackers@freebsd.org; Wed, 11 Nov 1998 23:45:18 -0600 (CST) Date: Wed, 11 Nov 1998 23:45:18 -0600 (CST) Message-Id: <199811120545.XAA00292@noel.cs.rice.edu> To: freebsd-hackers@FreeBSD.ORG Subject: scsi disk queue Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm trying to find out how to get the number of events queued for a scsi disk at any time. Is there some way I can get this information. If not, can someone suggest the kernel variables that would give me this information - I'm willing to change the kernel and create a custom array like dk_xfer[] for reporting disk events queued at any time. Please reply by email. Thanks, - Mohit Aron aron@cs.rice.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 21:49:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29563 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 21:49:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28033 for ; Wed, 11 Nov 1998 21:34:21 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id PAA14909; Thu, 12 Nov 1998 15:57:46 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [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: <199811120516.VAA07759@dingo.cdrom.com> Date: Thu, 12 Nov 1998 15:53:29 +1030 (CST) From: "Daniel O'Connor" To: Mike Smith Subject: Re: PCI interrupts Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Nov-98 Mike Smith wrote: > > handler for the device in question. ie would the interrupt routine keep > > getting called? or would it only get called once? > If the system is expecting a level-triggered interrupt, that is > *extremely* bad. The interrupt handler will spin forever. The same > goes for any other operating system. Your interrupt handler *must* > clear the interrupt source before returning. Eww :-/ Hmm... time for some extra code methinks.. > > beer if you want =) > Just make sure there's some cold there in the 'fridge. I get back > around the 30th or so of this month, and I've a week to kill in > Adelaide. 8) Hey, lucky for you Brian had his fridge fixed.. Now the milk isn't chunky.. > Anything you think might go down well as tokens from afar? I dunno, maybe some bad American coffee and beer so we can feel superior =) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 21:51:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29900 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 21:51:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29895 for ; Wed, 11 Nov 1998 21:51:42 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id WAA21345; Wed, 11 Nov 1998 22:50:59 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811120550.WAA21345@panzer.plutotech.com> Subject: Re: scsi disk queue In-Reply-To: <199811120545.XAA00292@noel.cs.rice.edu> from Mohit Aron at "Nov 11, 98 11:45:18 pm" To: aron@cs.rice.edu (Mohit Aron) Date: Wed, 11 Nov 1998 22:50:59 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mohit Aron wrote... > Hi, > I'm trying to find out how to get the number of events queued for a > scsi disk at any time. Is there some way I can get this information. If not, > can someone suggest the kernel variables that would give me this information > - I'm willing to change the kernel and create a custom array like dk_xfer[] > for reporting disk events queued at any time. Please reply by email. Thanks, If you're running 3.0 or a CAM version of -current or -stable, you can find out the number of outstanding transactions for any device registered with the devstat(9) subsystem. Download the following program: ftp://ftp.kdm.org/pub/FreeBSD/cam/ds.c It dumps out the devstat entry for each device. The devstat entry includes a busy count, which is the number of outstanding transactions queued to the drive. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 22:01:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA00964 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 22:01:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (tex-126.camalott.com [208.229.74.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA00956 for ; Wed, 11 Nov 1998 22:01:35 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id AAA18341; Thu, 12 Nov 1998 00:01:00 -0600 (CST) (envelope-from joelh) To: Steve Kargl Cc: dfr@nlsystems.com, sos@freebsd.dk, n@nectar.com, nate@mt.sri.com, kkennawa@physics.adelaide.edu.au, dnelson@emsphone.com, rivers@dignus.com, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname References: <199811110512.VAA01354@troutmask.apl.washington.edu> From: Joel Ray Holveck Date: 12 Nov 1998 00:00:59 -0600 In-Reply-To: Steve Kargl's message of "Tue, 10 Nov 1998 21:12:44 -0800 (PST)" Message-ID: <86n25xih5w.fsf@detlev.UUCP> Lines: 23 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I have yet to hear of any solutions that don't require a hack to the >> install procedure (eg, setting an environment variable). Unless >> somebody comes up with an idea that would magically detect what >> environment a given script wants, I would recommend putting a Linux >> uname in /copmat/linux where it belongs, and the install procedure's >> PATH can have /compat/linux ahead of /. This is easy to implement, >> keeps the core of FreeBSD pure, and paves the way for future >> similarities. > What about install scripts that reside on cdroms? You can't magically > edit a cdrom install script unless unionfs works. I'm not talking about editing a script. I'm talking about: PATH=/compat/linux/bin:/compat/linux/usr/bin:${PATH} ; make install Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 22:02:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01056 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 22:02:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (tex-126.camalott.com [208.229.74.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01044 for ; Wed, 11 Nov 1998 22:02:20 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id AAA18347; Thu, 12 Nov 1998 00:01:47 -0600 (CST) (envelope-from joelh) To: Jamie Bowden Cc: Doug Rabson , Sren Schmidt , Jacques Vidrine , sgk@troutmask.apl.washington.edu, nate@mt.sri.com, kkennawa@physics.adelaide.edu.au, dnelson@emsphone.com, rivers@dignus.com, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname References: From: Joel Ray Holveck Date: 12 Nov 1998 00:01:47 -0600 In-Reply-To: Jamie Bowden's message of "Wed, 11 Nov 1998 16:12:57 -0500 (EST)" Message-ID: <86lnlhih4k.fsf@detlev.UUCP> Lines: 20 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I have yet to hear of any solutions that don't require a hack to the >> install procedure (eg, setting an environment variable). Unless >> somebody comes up with an idea that would magically detect what >> environment a given script wants, I would recommend putting a Linux >> uname in /copmat/linux where it belongs, and the install procedure's >> PATH can have /compat/linux ahead of /. This is easy to implement, >> keeps the core of FreeBSD pure, and paves the way for future >> similarities. > chroot /compat/linux ; install Not unless you have a complete minimal tree under /compat/linux. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 22:04:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01215 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 22:04:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles205.castles.com [208.214.165.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01210 for ; Wed, 11 Nov 1998 22:04:21 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA08044; Wed, 11 Nov 1998 22:00:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811120600.WAA08044@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey cc: hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone In-reply-to: Your message of "Wed, 11 Nov 1998 10:30:28 +1030." <19981111103028.L18183@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Nov 1998 22:00:40 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Monday, 9 November 1998 at 22:38:04 -0800, Mike Smith wrote: > > > > Just started playing with Vinum. Gawd Greg, this thing seriously needs > > a "smart" frontend to do the "simple" things. > > Any suggestions? After seeing people just banging out RAID > configurations with GUIs, I thought that this is probably a Bad > Thing. If you don't understand what you're doing, you shouldn't be > doing it. That's not entirely true. > The four-layer concepts used by Veritas and Vinum have always been > difficult to understand. I'm trying to work out how to explain them > better, but taking the Microsoft-style "don't worry, little boy, I'll > do it all for you" approach is IMO not the right way. I think it's a mistake to conceal all the workings, but it's also a mistake to assume that for the "common case", you need to thrust all of it into the novice's face. The "common case" for RAID applications seems to be: "I have these disk units, and I want to make them into a RAID volume". So the required functionality is: 1) Input the disks to participate in the volume. 2) Input the RAID model to be used. Step 2 should check the sizes of the disks selected in step 1, and make it clear that you can only get striped or RAID 5 volumes if the disks are all the same size. If they're within 10% or so of each other, it should probably ignore the excess on the larger drives. > > 4 x 4GB disks (2x Atlas, 2x Grand Prix) on an ncr 53c875, slapped > > together as a single volume. (you want to mention building filesystems > > in your manpages somewhere too - the '-v' option is not immediately > > obvious). > > As Tony observed, it's in vinum(4). vinum(8) just describes the > interface program. Do you still think I need to add more information? > There's supposed to be a user's guide, when I get round to writing it. I missed that, sorry. > > There was an interesting symptom observed in striped mode, where the > > disks seemed to have a binarily-weighted access pattern. > > Can you describe that in more detail? Maybe I should consider > relating stripe size to cylinder group size. I'm wondering if it was just a beat pattern related to the stripe size and cg sizes. Basically, the first disk in the group of 4 was always active. The second would go inactive for a very short period of time on a reasonably regular basis. The third for slightly longer, and the fourth for longer still, with the intervals for the third and fourth being progressively shorter. > > It will get more interesting when I add two more 9GB drives and four > > more 4GB units to the volume; especially as I haven't worked out if I > > can stripe the 9GB units separately and then concatenate their plex > > with the plex containing the 4GB units; my understanding is that all > > plexes in a volume contain copies of the same data. > > Correct. I need to think about how to do this, and whether it's worth > the trouble. It's straightforward with concatenated plexes, of > course. Yes, and it may be that activities will be sufficiently spread out over the volume that this won't be a problem. > > Can you nest plexes? > > No. That's somewhat unfortunate, but probably contributes to code simplicity. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 22:37:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA03054 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 22:37:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (79.camalott.com [208.203.140.79]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA03048 for ; Wed, 11 Nov 1998 22:37:07 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id AAA18427; Thu, 12 Nov 1998 00:31:43 -0600 (CST) (envelope-from joelh) To: Greg Lehey Cc: john cooper , hackers@FreeBSD.ORG, mike@smith.net.au, ticso@cicely.de Subject: Re: SCSI vs. DMA33.. References: <98Nov11.134648jst.21907@ns.isi.co.jp> <19981111162000.O20374@freebie.lemis.com> From: Joel Ray Holveck Date: 12 Nov 1998 00:31:42 -0600 In-Reply-To: Greg Lehey's message of "Wed, 11 Nov 1998 16:20:00 +1030" Message-ID: <86k911ifqp.fsf@detlev.UUCP> Lines: 43 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> The theoretical throughputs of 40MBs and 33MBs don't tell me a whole >> lot. I know SCSI was the choice for performance in the past, >> however I'm curious what others are seeing in actual usage these >> days. > I'm running 3.0-CURRENT (post-RELEASE), and as you can see Ultra DMA > is enabled on the IDE drives. Here's what I get transferring 32 MB > from each raw device: Were these filesystems in use at the time? About how many users/processes? dd's rarely will effectively emulate the access patterns of a real-world server. Numerous outstanding short requests scattered across the disk is more common. Several simultanious worldstones may model real-world performance better. I know that you know this, and most of the -hackers list as well, but I'd like to stress that these methodologies are all quick n' dirty. Seek times, onboard transfer buffers, and other aspects of the drives will throw these numbers off. A good methodology would be using identical drive controllers and mechanisms on the IDE and SCSI. (Naturally, ad-hoc is all we can provide right now.) > Looks good for the IDE drives, doesn't it? They say, though, that > SCSI drives work better with multiple requests outstanding... It is my understanding that the multiple request issue is primarily concerned with multiple requests on the same drive. You may want to try this again with some more dd's with skip= arguments to see how much tagged command queueing and device detachment help. Does anybody know how many drives support the SCSI device-to-device copy capability? This would probably only be useful in dd's, but I've considered implementing it. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 22:39:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA03493 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 22:39:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (79.camalott.com [208.203.140.79]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA03484 for ; Wed, 11 Nov 1998 22:39:44 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id AAA18460; Thu, 12 Nov 1998 00:39:22 -0600 (CST) (envelope-from joelh) To: Terry Lambert Cc: nik@nothing-going-on.demon.co.uk (Nik Clayton), yokota@zodiac.mech.utsunomiya-u.ac.jp, hackers@FreeBSD.ORG Subject: Re: text mode screen grabber? References: <199811110836.BAA06729@usr02.primenet.com> From: Joel Ray Holveck Date: 12 Nov 1998 00:39:22 -0600 In-Reply-To: Terry Lambert's message of "Wed, 11 Nov 1998 08:36:56 +0000 (GMT)" Message-ID: <86iuglifdx.fsf@detlev.UUCP> Lines: 29 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> True enough. I hasten to point out that I'm not trying to write something >> for wide distribution (at the moment). This is just something to make >> the FreeBSD Documentation a little more user friendly. >> After poking a bit more through syscons.c, I think I should be able >> to implement something like "press 'D' to dump the current screen to >> /tmp/syscons.dump" or similar. > Or implement ESC [ 2 i processing into syscons, and when it gets > the ESC [ 2 i, have it stuff the input buffer with the screen > contents. This doesn't capture the colors (can be modified, but with effort), and besides, is only useful if you feel like modifying the app you are capturing. It was my impression that, for this hacker's needs, this would be several apps all over FreeBSD. I would lean towards a ioctl to stuff the screen buffer into a userland buffer myself. Quick, painless, and can be used by the app or a separate program. Seeing as how it's to help our docs, if you don't feel like writing the syscons patch, send me a private email and I'll hack it out myself. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 22:42:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA03666 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 22:42:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gershwin.tera.com ([207.224.230.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA03660 for ; Wed, 11 Nov 1998 22:42:30 -0800 (PST) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (tao.tera.com [207.108.223.55]) by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id WAA03661; Wed, 11 Nov 1998 22:42:10 -0800 (PST) Received: (from kline@localhost) by tao.thought.org (8.8.8/8.7.3) id WAA04442; Wed, 11 Nov 1998 22:41:58 -0800 (PST) From: Gary Kline Message-Id: <199811120641.WAA04442@tao.thought.org> Subject: Re: bsd make to gnu make conversion, anyone?? In-Reply-To: <98Nov11.234727edt.37814-2936@qew.cs.toronto.edu> from David Holland at "Nov 11, 98 11:47:27 pm" To: dholland@cs.toronto.edu (David Holland) Date: Wed, 11 Nov 1998 22:41:58 -0800 (PST) Cc: hackers@FreeBSD.ORG Organization: <> thought.org: public access uNix in service... <> X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to David Holland: > > Are there any makefile senior Wizards out there who can clue me > > in on the translation of this pmake > > gmake doesn't have an equivalent for .for, so you're stuck with making > a mess. > As long as it works and makes some sense, that's what counts. > > > > LANGS= en_US.ISO_8859-1 fr_FR.ISO_8859-1 de_DE.ISO_8859-1 > > FILES= ${LANGS:S/$/.mv.cat/} > > CLEANFILES+= ${FILES} > > > > . > > . > > . > > > > for lang in ${LANGS} > > ${lang}.mv.cat: ${.CURDIR}/nls/${lang}/mv.msg > > gencat -new ${.TARGET} ${.ALLSRC} > > .endfor > > This you can probably do with > > %.mv.cat: ${.CURDIR}/nls/%/mv.msg > gencat -new $@ $^ > > (for some suitable replacement for ${.CURDIR}) > > > beforeinstall: > > .for lang in ${LANGS} > > ${INSTALL} ${COPY} -o ${BINOWN} -g ${BINGRP} -m ${NOBINMODE} \ > > ${lang}.mv.cat ${DESTDIR}${NLSDIR}/${lang}/mv.cat > > .endfor > > try > > ${patsubst %, install-%, ${LANGS}}: install-%: > ${INSTALL} -c -o root -m 644 ${patsubst install-%, %.mv.cat, $@} \ > ${DESTDIR}${NLSDIR}/${patsubst install-%, %, $@}/mv.cat > > beforeinstall: ${patsubst %, install-%, ${LANGS}} > > > but that might not work and in any event it's pretty gross. It's slightly worse than gross! > > You might be better off compiling bsd make on whatever box you're > using. > Can't. We're doing the entire BSD built using gmake. .... Is there a cleaner way using /bin/sh commands within gmake? Something like for $${lang} in $${LANGS} do .... done thanks for your input, gary > -- Gary D. Kline kline@tao.thought.org Public service uNix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 11 23:15:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05962 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 23:15:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (79.camalott.com [208.203.140.79]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA05957 for ; Wed, 11 Nov 1998 23:15:12 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id BAA18575; Thu, 12 Nov 1998 01:04:06 -0600 (CST) (envelope-from joelh) To: David Holland Cc: kline@tao.thought.org (Gary Kline), hackers@FreeBSD.ORG Subject: Re: bsd make to gnu make conversion, anyone?? References: <98Nov11.234727edt.37814-2936@qew.cs.toronto.edu> From: Joel Ray Holveck Date: 12 Nov 1998 01:04:05 -0600 In-Reply-To: David Holland's message of "Wed, 11 Nov 1998 23:47:27 -0500" Message-ID: <86hfw5ie8q.fsf@detlev.UUCP> Lines: 60 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> Are there any makefile senior Wizards out there who can clue me >>> in on the translation of this pmake > gmake doesn't have an equivalent for .for, so you're stuck with making > a mess. Using gmake's 'foreach' and sh's 'for' may be useful. >> for lang in ${LANGS} >> ${lang}.mv.cat: ${.CURDIR}/nls/${lang}/mv.msg >> gencat -new ${.TARGET} ${.ALLSRC} >> .endfor > %.mv.cat: ${.CURDIR}/nls/%/mv.msg > gencat -new $@ $^ This is the cleanest solution. Still, if you want alternatives, I haven't tried this, but foreach may work here, as a generalization of for: define do-lang $(lang).mv.cat: $(.CURDIR)/nls/$(lang)/mv.msg gencat -new $(.TARGET) $(.ALLSRC) endef $(foreach lang,$(LANGS),$(do-lang)) and similarly for the other one. Note that lang either should not have been defined yet, or defined with =, not :=. Again, I personally think that your % rule is by far cleaner. >> beforeinstall: >> .for lang in ${LANGS} >> ${INSTALL} ${COPY} -o ${BINOWN} -g ${BINGRP} -m ${NOBINMODE} \ >> ${lang}.mv.cat ${DESTDIR}${NLSDIR}/${lang}/mv.cat >> .endfor > ${patsubst %, install-%, ${LANGS}}: install-%: > ${INSTALL} -c -o root -m 644 ${patsubst install-%, %.mv.cat, $@} \ > ${DESTDIR}${NLSDIR}/${patsubst install-%, %, $@}/mv.cat > > beforeinstall: ${patsubst %, install-%, ${LANGS}} What's wrong with using sh like God intended? beforeinstall: for lang in ${LANGS} ; do \ ${INSTALL} ${COPY} -o ${BINOWN} -g ${BINGRP} -m ${NOBINMODE} \ $${lang}.mv.cat ${DESTDIR}${NLSDIR}/$${lang}/mv.cat ; \ done Note the $${lang}, so that sh interprets the variable instead of make. (Using foreach may also work here.) Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 00:09:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10332 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 00:09:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10327 for ; Thu, 12 Nov 1998 00:09:04 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id JAA10638 for ; Thu, 12 Nov 1998 09:08:43 +0100 (MET) Date: Thu, 12 Nov 1998 09:08:41 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: FreeBSD hackers mailing list Subject: Re: Upgrade from 2.2-STABLE to -CURRENT In-Reply-To: <3.0.32.19981111195130.0068d1d0@triton> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > cp strip maybe_stripped > strip maybe_stripped > *** Error code 1 Find the occurrence in the tree and add a '-' in front of the strip. It is unnecessary and a bug in the code, found it once, but forgot to post a bug report. Nick > ...and five more "*** Error code 1". > > I don't know what to try next, so I'd appreciate any comments or > recommendations in order to get rid of this problem! > > please email me directly at flo@ganymed.org because I'm not subscribed to > freebsd-stable nor to freebsd-current. > > Thanks to all of you in advance, > > ciao, > Flo > > ----------------------------------------------------- > F. Nigsch > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 00:43:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13168 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 00:43:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13158 for ; Thu, 12 Nov 1998 00:43:35 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id JAA00363; Thu, 12 Nov 1998 09:41:48 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199811120841.JAA00363@freebsd.dk> Subject: Re: SCSI vs. DMA33.. In-Reply-To: <19981111233422.A10862@cons.org> from Martin Cracauer at "Nov 11, 1998 11:34:22 pm" To: cracauer@cons.org (Martin Cracauer) Date: Thu, 12 Nov 1998 09:41:48 +0100 (CET) Cc: dillon@apollo.backplane.com, grog@lemis.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Martin Cracauer wrote: > > You didn't read what I wrote. I am aware of these issue and have 4 > drives, 4 channels on two cards. That it doesn't work because the two > channels on each Promise card block each other is a different matter > that was not foreseeable. I just checked here, I have no problems using both channels at once, do you have the BIOS enabled ?? If not you wont be running your drives at full specs... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 01:01:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15051 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 01:01:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from post.mail.demon.net (post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA15046 for ; Thu, 12 Nov 1998 01:01:18 -0800 (PST) (envelope-from aspltd@globalnet.co.uk) Received: from [212.228.141.241] (helo=mail.busicom.demon.co.uk) by post.mail.demon.net with smtp (Exim 2.05demon1 #1) id 0zdscc-0000Mm-00 for hackers@FreeBSD.org; Thu, 12 Nov 1998 09:00:59 +0000 Message-ID: <009501be0e1a$bbf6ba00$0500a8c0@mail.busicom.demon.co.uk> Reply-To: "Peter Pendlebury" From: "Peter Pendlebury" To: Subject: Problem with Fast Ethernet D-Link 650-TX 100Mbps PC Card Date: Thu, 12 Nov 1998 08:59:15 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by hub.freebsd.org id BAA15047 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running 2.3 and although the card is correctly detected at boot (D-Link DFE-650TX Fast Ethernet PC Card, 100Mbps), the actual driver for it only supports the DE-650 (10Mbps). I've checked the repository and there isn't a more recent driver available. I've got to hitch it up at 100Mbps, so I can't just hook it in at 10Mbps. Does anybody know of or have an updated driver for this? Thanks in advance for any help, Pete Pendlebury Email: peter@alliedsoftware.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 02:08:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA19687 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 02:08:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.fx.ro (ns.fx.ro [193.231.208.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA19652 for ; Thu, 12 Nov 1998 02:08:06 -0800 (PST) (envelope-from cpl92@fx.ro) From: cpl92@fx.ro Received: from fx.ro (ppp75.fx.ro [193.231.209.75]) by ns.fx.ro (8.9.1/8.9.1) with ESMTP id MAA31094 for ; Thu, 12 Nov 1998 12:10:32 +0200 Message-ID: <364A0A3A.EEBFB63A@fx.ro> Date: Thu, 12 Nov 1998 00:05:47 +0200 Organization: Consorzio Progetto Lazio '92 X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: sever ide hdd crash (also re:Another instance of the crash I was seeing) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I experienced yesterday a sever ide hdd crash. My computer is not operating these days, so please answer also to this address I'm using now. First I want to make a short histiry of this serious ide problem. One month ago, I was using 2.2.6-RELEASE. Someday, while I was reading the first FreeBSD CD in WALNUT CREAK distribution set, the ATA CD slow down, and was acting like having reading trouble from the CD inside (possible the CD wasn't clean). By chance, I swiched to text connsole and saw the syslog message repeating many times:(smth like) wd0 i/o error swiched to 16 bit transfer. I killed the process that was accessing the ATA CD, and than fsck my wd0 partitions: surprize! the /usr slice was damaged (I couldn't fix it due to many errors like unref inode etc.). One day ago, under the same circumstances (only that the used dist was 2.2.7-RELEASE), while I was looking far a tarball distribution in CD #3 (WALNUT CREAK 2.2.7), I heard the CD slowing down. Knowing what happened last time, I tried alt+ctrl+F1 to see the syslog mesg. Surprize again: the computer was not responding to any of the possible commands. I have waited a couple of minutes (the hdd was not running), then I have pushed the front pannel reset button. Surprize again: While reseting the computer I received the BIOS message PRIMARY HDD FAILURE. Since then, my BIOS says that I don't have a HDD inside (actually I have a Quantum Fireball UDMA 4.3 Gb). I hope that the vendor will change the damaged hdd, but I am quite sure that this is a very serious problem in FreeBSD kernel. Regards, Florin Nicolescu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 02:19:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA20626 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 02:19:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20615 for ; Thu, 12 Nov 1998 02:19:00 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1a/8.9.1) with ESMTP id CAA17890; Thu, 12 Nov 1998 02:19:37 -0800 (PST) To: cpl92@fx.ro cc: freebsd-hackers@FreeBSD.ORG Subject: Re: sever ide hdd crash (also re:Another instance of the crash I was seeing) In-reply-to: Your message of "Thu, 12 Nov 1998 00:05:47 +0200." <364A0A3A.EEBFB63A@fx.ro> Date: Thu, 12 Nov 1998 02:19:36 -0800 Message-ID: <17881.910865976@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > computer I received the BIOS message PRIMARY HDD FAILURE. Since then, my > BIOS says that I don't have a HDD inside (actually I have a Quantum > Fireball UDMA 4.3 Gb). I hope that the vendor will change the damaged > hdd, but I am quite sure that this is a very serious problem in FreeBSD > kernel. I very seriously doubt it. There are a lot of interesting things that kernel bugs can do to your data but, unless they exercise it heavily and surreptitiously in the night, there's not much they can do to cause the early retirement of your hard disk. What you have there sounds like a plain, old-fashioned, simple, hard disk failure. Not space aliens, not the ghost of Elvis trying to communicate with the living through your hard drive, but what the spanish call "el seagate muerte" Your drive is dead, Jim. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 02:30:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA21581 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 02:30:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA21576 for ; Thu, 12 Nov 1998 02:30:23 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id LAA16897; Thu, 12 Nov 1998 11:30:02 +0100 (MET) Date: Thu, 12 Nov 1998 11:30:01 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: FreeBSD hackers mailing list cc: USB BSD list Subject: update on USB stack/call for help Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The porting of the NetBSD USB stack to FreeBSD is progressing. We are at the point were actual device drivers are to be tested/implemented. The (working) beginnings of the following are there: - printer driver (not test under FreeBSD yet, but working under NetBSD) - generic driver (as in very generic, you'll know the name and serial number of your device and that's it. But the NetBSD folks are working on that one, as well as I do on the side). - mouse driver (working, cut&paste works on my laptop). (do _not_ remove the mouse while the mouse is used by any userland program, the interrupt pipe is not killed and your computer will go pop, without you being able to reset it). - keyboard driver (possibly attaches, but connection to syscons has not yet been made). - HID (human interface device driver), a general driver for any kind of human interface device. Drivers for joysticks or touchpads should not be too hard to write with this available. If you download the stack, check the README for installation instructions. Be aware of the fact that the code is alpha, so if it breaks, you can keep the pieces. Anyone wanting to get his hands dirty could have a look at the following parts: - keyboard driver: someone has to pick that up and make the driver not only work with USB keyboard but also together with syscons. NetBSD uses a completely different abstraction layer there, so that requires a bit of work. - mouse driver: someone needs to properly implement the PS/2 emulation or write the sysmouse version of it. At the moment this has been a quick&dirty job to get it working. - OHCI driver: requires compliant motherboard (non-Intel 82371 board, see your dmesg); low level driver has not been ported yet, but is high on the list of priorities. - general: testing, like installing it and telling me whether it works for you or not - video camera driver: Windows 1895 is not able to do something sensible with my camera, so I will start on that one as soon as possible One big problem that has to be solved as soon as possible: Dynamic attachment and detachment, including (manual) dynamic loading of the drivers. detachment is not implemented in the NetBSD version yet. That I am going to try and solve this weekend. The USB stack can be fetched from http://www.etla.net/~n_hibma/usb/usb.pl Mailing list for people participating in coding: http://www.egroups.com/list/usb-bsd/ Info on USB in general: http://www.usb.org (nice poll: 'Are you running Windows '98 as your OS?' 49% of 415 votes says 'No'! That is a lot for a site that is referenced by early adopters.) Cheers, Nick Hibma To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 02:38:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA22312 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 02:38:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA22305 for ; Thu, 12 Nov 1998 02:38:06 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id LAA00549; Thu, 12 Nov 1998 11:37:30 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199811121037.LAA00549@freebsd.dk> Subject: Re: sever ide hdd crash (also re:Another instance of the crash I was seeing) In-Reply-To: <364A0A3A.EEBFB63A@fx.ro> from "cpl92@fx.ro" at "Nov 12, 1998 0: 5:47 am" To: cpl92@fx.ro Date: Thu, 12 Nov 1998 11:37:30 +0100 (CET) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems cpl92@fx.ro wrote: > One day ago, under the same circumstances (only that the used dist was > 2.2.7-RELEASE), while I was looking far a tarball distribution in CD #3 > (WALNUT CREAK 2.2.7), I heard the CD slowing down. Knowing what happened > last time, I tried alt+ctrl+F1 to see the syslog mesg. Surprize again: > the computer was not responding to any of the possible commands. I have > waited a couple of minutes (the hdd was not running), then I have pushed > the front pannel reset button. Surprize again: While reseting the > computer I received the BIOS message PRIMARY HDD FAILURE. Since then, my > BIOS says that I don't have a HDD inside (actually I have a Quantum > Fireball UDMA 4.3 Gb). I hope that the vendor will change the damaged > hdd, but I am quite sure that this is a very serious problem in FreeBSD > kernel. Hmm, I'm quite sure you have a bad disk, the kernel cannot make your disk die like that. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 02:48:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23028 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 02:48:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dirac.physik.uni-bonn.de (dirac.physik.uni-bonn.de [131.220.161.119]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA23013 for ; Thu, 12 Nov 1998 02:47:57 -0800 (PST) (envelope-from conrad@dirac.physik.uni-bonn.de) Received: from merlin.physik.uni-bonn.de (merlin.physik.uni-bonn.de [131.220.161.121]) by dirac.physik.uni-bonn.de (8.8.8/8.8.8) with ESMTP id LAA14070 for ; Thu, 12 Nov 1998 11:47:32 +0100 (CET) (envelope-from conrad@merlin.physik.uni-bonn.de) Received: from localhost (conrad@localhost) by merlin.physik.uni-bonn.de (8.8.8/8.8.8) with ESMTP id LAA12391 for ; Thu, 12 Nov 1998 11:47:31 +0100 (CET) (envelope-from conrad@merlin.physik.uni-bonn.de) X-Authentication-Warning: merlin.physik.uni-bonn.de: conrad owned process doing -bs Date: Thu, 12 Nov 1998 11:47:31 +0100 (CET) From: Jan Conrad To: freebsd-hackers@FreeBSD.ORG Subject: /etc/rc: mount -v -a -t nfs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi everybody, I have a small suggestion concerning the /etc/rc script. I find it pretty annoying that the nfs mounts are done *WITHOUT* verbose mode. E.g. we have some nfs problem here on our group server which seems to appear only at boot time and cannot be repeated in multi user mode (but it has some subtle consequences then - sure :-). However mount does not show mount point information when displaying error messages! Syslog messages are not generated either! So without '-v' one does not have a chance to trace down the problem. So to say: the error messages generated by /etc/rc (when one has more than one mount point) are usesless without the 'mount -v'. This is especially true for servers which one boots only when absolutely necessary! And even more in heterogenous environments! So I suggest to change the nfs mount in /etc/rc to 'mount -v -a -t nfs'. best regards Jan Conrad -- Physikalisches Institut der Universitaet Bonn Nussallee 12 D-53115 Bonn GERMANY To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 02:50:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23501 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 02:50:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA23474 for ; Thu, 12 Nov 1998 02:50:10 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id JXGQFXWJ; Thu, 12 Nov 98 10:49:48 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981112114948.009525d0@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Thu, 12 Nov 1998 11:49:48 +0100 To: freebsd-hackers@FreeBSD.ORG From: Marius Bendiksen Subject: Maxtor Diamondmax 8.4 (UDMA33) + WD Caviar 3.2 (UDMA33) Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id CAA23484 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry if this has been posted to the wrong list. I've been running 2.2-stable, then 3.0-current for about 5 months on my WD Caviar 3.2 (UDMA33) disk, without any trouble. I used a 16x CDrom as Secondary Master. Recently, I added a Maxtor Diamondmax 8.4 (UDMA33) disk to the system as Primary Slave. This worked out for about three days, then the disk suddenly started reporting files of immense size, and after a while started reporting that it was an Oaxzor-some-or-other during the wdc0 probe. During the course of that day, the disk failed utterly, and was recognized with various geometries (sometimes not being detected at all), and yielding I/O errors upon any attempt at accessing it in any way. I got a replacement disk from the importer, and it worked fine for about 3 hours, before exhibiting the same symptoms. I then moved it to the Secondary Slave, where it was successfully detected. However, I was unable to boot it, as the BIOS could not detect it. (Booting from a floppy detected it just fine) I then replaced the 3.2 with the 8.4, and lo' and behold, it seems to work like a charm, with some exceptions. I've not tried it for more than about 12 hours, though, and the probe reports some wierd characters after the Maxtor some-or-other bit with the wdc0 probe. Also, the BIOS hangs for about 15 minutes while detecting IDE devices, and reports secondary slave failure (even though I've got none, and have reset the BIOS information). I have to use a custom boot floppy, without wd3, because wd3 always hangs the installation with maxed out tracks, heads and sectors count. I don't have any dmesg outputs or such right now, may post these later if that would help. I have used a setup w/FreeBSD on Primary Slave with Connor disks successfully earlier. (The connor disks were not UDMA) It makes no difference which flags I pass to the wdc drivers. Does anyone have any idea how I can get these two drives to co-exist? Right now, I need the data from the 3.2, and don't have any way of transferring it. Thanks. .oO[š Marius Bendiksen š]Oo. Dead girls don't say no. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 03:21:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA25319 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 03:21:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA25314 for ; Thu, 12 Nov 1998 03:21:49 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id MAA00639; Thu, 12 Nov 1998 12:21:25 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199811121121.MAA00639@freebsd.dk> Subject: Re: Maxtor Diamondmax 8.4 (UDMA33) + WD Caviar 3.2 (UDMA33) In-Reply-To: <3.0.5.32.19981112114948.009525d0@mail.scancall.no> from Marius Bendiksen at "Nov 12, 1998 11:49:48 am" To: Marius.Bendiksen@scancall.no (Marius Bendiksen) Date: Thu, 12 Nov 1998 12:21:25 +0100 (CET) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Marius Bendiksen wrote: > Sorry if this has been posted to the wrong list. > > I then replaced the 3.2 with the 8.4, and lo' and behold, it seems to work > like a charm, with some exceptions. I've not tried it for more than about > 12 hours, though, and the probe reports some wierd characters after the > Maxtor some-or-other bit with the wdc0 probe. Also, the BIOS hangs for > about 15 minutes while detecting IDE devices, and reports secondary slave > failure (even though I've got none, and have reset the BIOS information). I > have to use a custom boot floppy, without wd3, because wd3 always hangs the > installation with maxed out tracks, heads and sectors count. What kind of Motherboard are you using ?? with which chipset ?? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 03:38:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA26578 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 03:38:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from web1.rocketmail.com (web1.rocketmail.com [205.180.57.67]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA26573 for ; Thu, 12 Nov 1998 03:38:44 -0800 (PST) (envelope-from ee123@rocketmail.com) Message-ID: <19981112112445.19216.rocketmail@web1.rocketmail.com> Received: from [195.146.225.184] by web1; Thu, 12 Nov 1998 03:24:45 PST Date: Thu, 12 Nov 1998 03:24:45 -0800 (PST) From: "Eric D'HEM" Reply-To: ee123@rocketmail.com Subject: PCI-100MB ethernet card To: hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have to had a 100MB card on my system but I have lots of prolem to find one. I actually have a SN5100TX. Does anaybody know wich driver I must use with wich kernel? Does anybody know a low cost 100MB card wich work with a FreeBSD stable release? (A recent one please because many constructor have change their chipset and driver don't work any more.) Thanks. _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 03:41:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA26902 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 03:41:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA26897 for ; Thu, 12 Nov 1998 03:41:46 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id JXHDFCAJ; Thu, 12 Nov 98 11:41:26 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981112124124.00944770@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Thu, 12 Nov 1998 12:41:24 +0100 To: =?iso-8859-1?Q?S=F8ren?= Schmidt From: Marius Bendiksen Subject: Re: Maxtor Diamondmax 8.4 (UDMA33) + WD Caviar 3.2 (UDMA33) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199811121121.MAA00639@freebsd.dk> References: <3.0.5.32.19981112114948.009525d0@mail.scancall.no> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >What kind of Motherboard are you using ?? with which chipset ?? I have no idea. I'll have to talk to the dealer, because I never got that info bundled. I *do* know it's some kind of GIGA mobo, though. --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 03:50:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27472 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 03:50:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27466 for ; Thu, 12 Nov 1998 03:50:26 -0800 (PST) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id GAA10277; Thu, 12 Nov 1998 06:49:40 -0500 (EST) Received: from john.baldwinfamily.org (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id GAA28547; Thu, 12 Nov 1998 06:49:39 -0500 (EST) Message-ID: X-Mailer: XFMail 1.3 [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: <199811120641.WAA04442@tao.thought.org> Date: Thu, 12 Nov 1998 06:49:39 -0500 (EST) Reply-To: jobaldwi@vt.edu Organization: Virginia Tech From: John Baldwin To: Gary Kline Subject: Re: bsd make to gnu make conversion, anyone?? Cc: hackers@FreeBSD.ORG, (David Holland) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- On 12-Nov-98 Gary Kline wrote: > Can't. We're doing the entire BSD built using > gmake. .... > > Is there a cleaner way using /bin/sh commands > within gmake? Something like > > for $${lang} in $${LANGS} > do > .... > done > > thanks for your input, > > gary I'm using the following for loop in a makefile that works fine with both pmake and gmake: SUBDIRS = lib scripts support all clean cleanclean install: @for dir in $(SUBDIRS) ;\ do \ (cd $$dir ; echo "making $@ in $(CURRENT_DIR)/$$dir..." ; $(MAKE) $(MFLAGS) $@ ) ;\ done Hopefully that'll help. The only thing is that you need a semicolon before the do and after every statement. Also, it wants a for loop to all be on one line (?) so that you have to use \'s to make it concatenate the various lines. The ampersand on the for is to prevent the command from being echoed, btw. - --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc Lawyer (n) - one skilled in the circumvention of the law. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNkrKEYjYza302vYpAQHw1AL+Lwulc7TRmnqEFUpVuVhzl2n0c/Xt+v8b XMT0aQz3At3fG97rWz2ACHl4JFnD7Nf+fkxfZrChu9yfgiPnJxhAzwoP7EqKVngf t+MYK0FrIH/RdcdsYU5J/6RLYn4x8vLJ =jgKw -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 04:27:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA02425 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 04:27:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA02415 for ; Thu, 12 Nov 1998 04:27:02 -0800 (PST) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.8/8.7.3) id NAA16139; Thu, 12 Nov 1998 13:21:10 +0100 (CET) Message-ID: <19981112132110.B16085@cons.org> Date: Thu, 12 Nov 1998 13:21:10 +0100 From: Martin Cracauer To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: dillon@apollo.backplane.com, grog@lemis.com, hackers@FreeBSD.ORG Subject: Re: SCSI vs. DMA33.. References: <19981111233422.A10862@cons.org> <199811120841.JAA00363@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.1i In-Reply-To: =?iso-8859-1?Q?=3C199811120841=2EJAA00363=40freebsd=2Edk=3E=3B_from_S=F8?= =?iso-8859-1?Q?ren_Schmidt_on_Thu=2C_Nov_12=2C_1998_at_09:41:48AM_+0100?= Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199811120841.JAA00363@freebsd.dk>, Søren Schmidt wrote: > It seems Martin Cracauer wrote: > > > > You didn't read what I wrote. I am aware of these issue and have 4 > > drives, 4 channels on two cards. That it doesn't work because the two > > channels on each Promise card block each other is a different matter > > that was not foreseeable. > > I just checked here, I have no problems using both channels at once, > do you have the BIOS enabled ?? If not you wont be running your > drives at full specs... I don't have the BIOS installed, because I boot from a SCSI disk :-( I thought it can't be that bad because I'm much faster than the normal DMA stuff using the onboard IDE controllers and boot -v shows udma settings and anyway I can't think of a reason why the channels are synchronized without the BIOS. Next thing to try after I copied my boot parition. As I think over it, a /boot.conf entry could be sufficient. If you're right, my plan seems to work. Cheap fast space :-))) Thanks Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 04:33:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA03123 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 04:33:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA02726 for ; Thu, 12 Nov 1998 04:29:42 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id LAA09449; Thu, 12 Nov 1998 11:26:47 +0100 From: Luigi Rizzo Message-Id: <199811121026.LAA09449@labinfo.iet.unipi.it> Subject: Re: update on USB stack/call for help To: nick.hibma@jrc.it Date: Thu, 12 Nov 1998 11:26:46 +0100 (MET) Cc: hackers@FreeBSD.ORG, usb-bsd@makelist.com In-Reply-To: from "Nick Hibma" at Nov 12, 98 11:29:42 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The porting of the NetBSD USB stack to FreeBSD is progressing. We are at > the point were actual device drivers are to be tested/implemented. The > (working) beginnings of the following are there: ... > Anyone wanting to get his hands dirty could have a look at the following > parts: one thing that would really need work is SCANNER support. Currently in FreeBSD we have support for the following: + SCSI through the generic interface; + some handheld scanners through specific device drivers (gsc,asc) but the vast majority of flatbed scanners out there are parallel-port and now slowly moving to USB. For the former, there is no standard that i am aware of, and manufacturers are collaborative as usual... I just hope that USB will also bring together a standardized way to access devices so we don't have to get crazy with proprietary command sequences (I am not so optimistic, the only area where I have seen this happening is SCSI & ATAPI storage devices...) cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 04:53:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA04625 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 04:53:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA04614 for ; Thu, 12 Nov 1998 04:53:41 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id NAA00697; Thu, 12 Nov 1998 13:52:00 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199811121252.NAA00697@freebsd.dk> Subject: Re: SCSI vs. DMA33.. In-Reply-To: <19981112132110.B16085@cons.org> from Martin Cracauer at "Nov 12, 1998 1:21:10 pm" To: cracauer@cons.org (Martin Cracauer) Date: Thu, 12 Nov 1998 13:51:59 +0100 (CET) Cc: dillon@apollo.backplane.com, grog@lemis.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Martin Cracauer wrote: > > > You didn't read what I wrote. I am aware of these issue and have 4 > > > drives, 4 channels on two cards. That it doesn't work because the two > > > channels on each Promise card block each other is a different matter > > > that was not foreseeable. > > > > I just checked here, I have no problems using both channels at once, > > do you have the BIOS enabled ?? If not you wont be running your > > drives at full specs... > > I don't have the BIOS installed, because I boot from a SCSI disk :-( And? that should be a problem, I dont boot on those either (yet) > I thought it can't be that bad because I'm much faster than the normal > DMA stuff using the onboard IDE controllers and boot -v shows udma > settings and anyway I can't think of a reason why the channels are > synchronized without the BIOS. Next thing to try after I copied my > boot parition. As I think over it, a /boot.conf entry could be > sufficient. > > If you're right, my plan seems to work. Cheap fast space :-))) Yup, works for me that way... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 05:14:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA06351 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 05:14:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA06336 for ; Thu, 12 Nov 1998 05:14:39 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id OAA22406; Thu, 12 Nov 1998 14:14:08 +0100 (MET) Date: Thu, 12 Nov 1998 14:14:06 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: FreeBSD hackers mailing list cc: USB BSD list Subject: Re: MODERATE -- luigi@labinfo.iet.unipi.it wants to post a message to usb-bsd (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > one thing that would really need work is SCANNER support. > > Currently in FreeBSD we have support for the following: > + SCSI through the generic interface; > + some handheld scanners through specific device drivers (gsc,asc) > but the vast majority of flatbed scanners out there are parallel-port > and now slowly moving to USB. For the former, there is no standard that > i am aware of, and manufacturers are collaborative as usual... > > I just hope that USB will also bring together a standardized way to > access devices so we don't have to get crazy with proprietary command > sequences (I am not so optimistic, the only area where I have seen this > happening is SCSI & ATAPI storage devices...) I see a future, in which Luigi has a place, spending his time on general interfaces... One option would be, like the mouse driver, design a sysmouse/sysscan device driver and make every driver look the same. If you want to use the specific features, use a program that uses specific features. I would appreciate it if you could step in and get the folks who wrote the SCSI scanner and handheld scanner device drivers together and get something going. Cheers, Nick -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 05:15:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA06569 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 05:15:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from animaniacs.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA06563 for ; Thu, 12 Nov 1998 05:15:35 -0800 (PST) (envelope-from jamie@itribe.net) Received: from localhost (jamie@localhost) by animaniacs.itribe.net (950413.SGI.8.6.12/950213.SGI.AUTOCF) via SMTP id IAA04546; Thu, 12 Nov 1998 08:14:51 -0500 Date: Thu, 12 Nov 1998 08:14:51 -0500 (EST) From: Jamie Bowden To: Joel Ray Holveck cc: hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <86lnlhih4k.fsf@detlev.UUCP> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12 Nov 1998, Joel Ray Holveck wrote: > >> I have yet to hear of any solutions that don't require a hack to the > >> install procedure (eg, setting an environment variable). Unless > >> somebody comes up with an idea that would magically detect what > >> environment a given script wants, I would recommend putting a Linux > >> uname in /copmat/linux where it belongs, and the install procedure's > >> PATH can have /compat/linux ahead of /. This is easy to implement, > >> keeps the core of FreeBSD pure, and paves the way for future > >> similarities. > > chroot /compat/linux ; install > > Not unless you have a complete minimal tree under /compat/linux. Someone asked for a solution that didn't require corrupting the base FreeBSD installation or source tree with compatability issues. I am well aware of the technical necessities of a chrooted environment, but it does give you a clean way to handle special cases like this. Jamie Bowden -- Systems Administrator, iTRiBE.net If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 06:09:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA10372 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 06:09:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from animaniacs.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA10364 for ; Thu, 12 Nov 1998 06:09:29 -0800 (PST) (envelope-from jamie@itribe.net) Received: from localhost (jamie@localhost) by animaniacs.itribe.net (950413.SGI.8.6.12/950213.SGI.AUTOCF) via SMTP id IAA04580; Thu, 12 Nov 1998 08:56:54 -0500 Date: Thu, 12 Nov 1998 08:56:54 -0500 (EST) From: Jamie Bowden To: Luigi Rizzo cc: nick.hibma@jrc.it, hackers@FreeBSD.ORG, usb-bsd@makelist.com Subject: Re: update on USB stack/call for help In-Reply-To: <199811121026.LAA09449@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Nov 1998, Luigi Rizzo wrote: > > The porting of the NetBSD USB stack to FreeBSD is progressing. We are at > > the point were actual device drivers are to be tested/implemented. The > > (working) beginnings of the following are there: > ... > > Anyone wanting to get his hands dirty could have a look at the following > > parts: > > one thing that would really need work is SCANNER support. > > Currently in FreeBSD we have support for the following: > + SCSI through the generic interface; > + some handheld scanners through specific device drivers (gsc,asc) > but the vast majority of flatbed scanners out there are parallel-port > and now slowly moving to USB. For the former, there is no standard that > i am aware of, and manufacturers are collaborative as usual... > > I just hope that USB will also bring together a standardized way to > access devices so we don't have to get crazy with proprietary command > sequences (I am not so optimistic, the only area where I have seen this > happening is SCSI & ATAPI storage devices...) I bought an HP 6200c about 2 months ago because it was the only scanner on the shelf with a scsi interface on it. It also happens to have a USB plug as well. Does this device have two different command sets on it, or is twain riding on top of USB? Jamie Bowden -- Systems Administrator, iTRiBE.net If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 06:27:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA11627 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 06:27:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from animal.cs.chalmers.se (animal.cs.chalmers.se [129.16.225.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA11622 for ; Thu, 12 Nov 1998 06:26:59 -0800 (PST) (envelope-from augustss@cs.chalmers.se) Received: from dogbert.cs.chalmers.se (dogbert.cs.chalmers.se [129.16.225.50]) by animal.cs.chalmers.se (8.8.5/8.8.5) with ESMTP id PAA28273; Thu, 12 Nov 1998 15:20:39 +0100 (MET) Date: Thu, 12 Nov 1998 15:20:39 +0100 (MET) From: Lennart Augustsson Message-Id: <199811121420.PAA28273@animal.cs.chalmers.se> Received: by dogbert.cs.chalmers.se (8.8.8/3.14+gl) id OAA24318; Thu, 12 Nov 1998 14:22:50 GMT To: usb-bsd@egroups.com CC: luigi@labinfo.iet.unipi.it, nick.hibma@jrc.it, hackers@FreeBSD.ORG, usb-bsd@makelist.com In-reply-to: (message from Jamie Bowden on Thu, 12 Nov 1998 08:56:54 -0500 (EST)) Subject: Re: [usb-bsd] Re: update on USB stack/call for help References: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I bought an HP 6200c about 2 months ago because it was the only scanner on > the shelf with a scsi interface on it. It also happens to have a USB plug > as well. Does this device have two different command sets on it, or is > twain riding on top of USB? Who can tell? There is no standard for USB scanners yet. There is an Imaging Class in the pipeline, but it's not available to us mere mortals yet. -- Lennart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 06:37:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12565 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 06:37:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12553 for ; Thu, 12 Nov 1998 06:37:34 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id WAA16506; Thu, 12 Nov 1998 22:35:35 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199811121435.WAA16506@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Nick Hibma cc: FreeBSD hackers mailing list Subject: Re: Upgrade from 2.2-STABLE to -CURRENT In-reply-to: Your message of "Thu, 12 Nov 1998 09:08:41 +0100." Date: Thu, 12 Nov 1998 22:35:35 +0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma wrote: > > cp strip maybe_stripped > > strip maybe_stripped > > *** Error code 1 > > Find the occurrence in the tree and add a '-' in front of the strip. It > is unnecessary and a bug in the code, found it once, but forgot to post > a bug report. > > Nick This usually turns out to have been caused by somebody tempting fate by putting "." at the beginning of their $PATH.. That's rather deadly to say the least.. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 06:42:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12823 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 06:42:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12804 for ; Thu, 12 Nov 1998 06:42:02 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id PAA26605; Thu, 12 Nov 1998 15:41:16 +0100 (MET) Date: Thu, 12 Nov 1998 15:41:14 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Peter Wemm cc: FreeBSD hackers mailing list Subject: Re: Upgrade from 2.2-STABLE to -CURRENT In-Reply-To: <199811121435.WAA16506@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, if you compile your code as toor, that is true yes, and most often the case as well. But you're right that should not be. A thing is though that the strip should be preceded by a -. It is somewhere in a different Makefile ina similar situation. Nick > > Find the occurrence in the tree and add a '-' in front of the strip. It > > is unnecessary and a bug in the code, found it once, but forgot to post > > a bug report. > > > > Nick > > This usually turns out to have been caused by somebody tempting fate by > putting "." at the beginning of their $PATH.. That's rather deadly to say > the least.. > > Cheers, > -Peter > > > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 07:07:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15582 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 07:07:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA15575 for ; Thu, 12 Nov 1998 07:07:22 -0800 (PST) (envelope-from lile@stdio.com) Received: from localhost (lile@localhost) by heathers.stdio.com (8.8.8/8.8.8) with SMTP id KAA24869 for ; Thu, 12 Nov 1998 10:10:30 -0500 (EST) (envelope-from lile@heathers.stdio.com) Date: Thu, 12 Nov 1998 10:10:30 -0500 (EST) From: "Larry S. Lile" To: hackers@FreeBSD.ORG Subject: PCI device question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am working on PCI support for the Olicom token-ring driver, the ISA cards are working fine now. I need one little bit of info for the PCI devices that I do not know how to get at. >4.1.3 PCI configuration > >For PCI adapters the configuration is retrieved by the driver through PCI >BIOS calls (or their equivalents in the OS in question). The PCI ID to >look for is 108D0001 for OC-3136 and OC-3137. To set-up the complete >configuration, retrieve the 64 byte configuration space header and pass >this to TRlld: > > int TRlldPCIConfig(TRlldDriver_t * driver, > TRlldAdapterConfig_t * config, > char * PCIConfiguration) > > driver the driver definition block. > > config the configuration structure to set-up. > > PCIConfiguration pointer to the 64 byte PCI configuration space > header. What is the "64 byte PCI configuration space header" and where do I get that from (what pci_* call) I already know the io-base address, dma-level, csn, pci slot, ... from another call. Thanks Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 07:17:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16511 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 07:17:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA16506 for ; Thu, 12 Nov 1998 07:17:28 -0800 (PST) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id KAA15450; Thu, 12 Nov 1998 10:16:32 -0500 Date: Thu, 12 Nov 1998 10:16:32 -0500 (EST) From: "Ron G. Minnich" X-Sender: rminnich@terra To: "Larry S. Lile" cc: hackers@FreeBSD.ORG Subject: Re: PCI device question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Nov 1998, Larry S. Lile wrote: > What is the "64 byte PCI configuration space header" and where do I get > that from (what pci_* call) > > I already know the io-base address, dma-level, csn, pci slot, ... from > another call. That's where stuff like base address etc. are. If you have pulled out base address info via config read and friends then you already know. If you are not pulling base etc. out via config reads then you have to fix your driver :-) Functions look like this: int data = pci_conf_read(tag, PCI_CLASS_REG); Are you using these? Ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 07:29:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17639 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 07:29:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ics.com (ics.com [140.186.40.192]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17634; Thu, 12 Nov 1998 07:29:01 -0800 (PST) (envelope-from kaleb@ics.com) Received: from ics.com (sunoco.ics.com [140.186.40.142]) by ics.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id KAA29002; Thu, 12 Nov 1998 10:28:41 -0500 (EST) Message-ID: <364AFEA9.D5D78A36@ics.com> Date: Thu, 12 Nov 1998 10:28:41 -0500 From: "Kaleb S. KEITHLEY" Organization: Integrated Computer Solutions X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.5.1 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: alpha@FreeBSD.ORG CC: hackers@FreeBSD.ORG Subject: Re: Alpha firmware References: <199811112206.OAA05522@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > For an EB64 (EB as in __E__valuation __B__board 64) a.k.a. Alpha PC64... > > > > Does anyone that's doing the Alpha port have firmware diskettes for this > > board that they'd be willing to dd off the contents and make them > > available somewhere for ftp? > > ftp.digital.com/pub/DEC/Alpha/firmware/v5.2 Sigh. I suppose this is the price I pay for not having enumerated in nauseous detail that I've been there, done that. I've also searched Yahoo, Altavista, and DejaNews. Looked at every Digital Firmware CD-ROM from version 2.9 through 5.0. Looked at RedHat and NetBSD web sites. Etc., etc., etc. > > You'll need to know which DEC system(s) used the board - Yes, I know. No DEC system used the EB* boards. > hopefully > someone on this list can help out, or the NetBSD/Alpha webpages will > probably give you what you need there. > > The firmware upgrade process can be, er, entertaining. But it's > usually pretty painless. Uh, right. Okay, back to the original question: Does anyone have the firmware for this board that they'd be willing to provide by ftp -- either as dd'ed diskette images or the DOS files, or whatever? (I'm on hackers, not on alpha [yet], so if you'd be so kind as to cc: me in any reply you send, I'd be most grateful.) Thanks, -- Kaleb S. KEITHLEY To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 07:48:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20269 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 07:48:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20264 for ; Thu, 12 Nov 1998 07:48:26 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id HAA05341; Thu, 12 Nov 1998 07:49:57 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811121549.HAA05341@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname In-Reply-To: <86n25xih5w.fsf@detlev.UUCP> from Joel Ray Holveck at "Nov 12, 1998 0: 0:59 am" To: joelh@gnu.org (Joel Ray Holveck) Date: Thu, 12 Nov 1998 07:49:57 -0800 (PST) Cc: dfr@nlsystems.com, sos@freebsd.dk, n@nectar.com, nate@mt.sri.com, kkennawa@physics.adelaide.edu.au, dnelson@emsphone.com, rivers@dignus.com, hackers@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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Joel Ray Holveck: > >> I have yet to hear of any solutions that don't require a hack to the > >> install procedure (eg, setting an environment variable). Unless > >> somebody comes up with an idea that would magically detect what > >> environment a given script wants, I would recommend putting a Linux > >> uname in /copmat/linux where it belongs, and the install procedure's > >> PATH can have /compat/linux ahead of /. This is easy to implement, > >> keeps the core of FreeBSD pure, and paves the way for future > >> similarities. > > What about install scripts that reside on cdroms? You can't magically > > edit a cdrom install script unless unionfs works. > > I'm not talking about editing a script. I'm talking about: > > PATH=/compat/linux/bin:/compat/linux/usr/bin:${PATH} ; make install > Echo: What about install scripts that reside on cdroms? You can't magically edit a cdrom install script unless unionfs works. #! /bin/sh PATH=/cdrom:/foo:/bar export PATH ... rest of script -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 08:25:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24777 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 08:25:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles361.castles.com [208.214.167.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24771 for ; Thu, 12 Nov 1998 08:25:03 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA11279; Thu, 12 Nov 1998 08:22:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811121622.IAA11279@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: cpl92@fx.ro cc: freebsd-hackers@FreeBSD.ORG Subject: Re: sever ide hdd crash (also re:Another instance of the crash I was seeing) In-reply-to: Your message of "Thu, 12 Nov 1998 00:05:47 +0200." <364A0A3A.EEBFB63A@fx.ro> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Nov 1998 08:22:22 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > computer I received the BIOS message PRIMARY HDD FAILURE. Since then, my > BIOS says that I don't have a HDD inside (actually I have a Quantum > Fireball UDMA 4.3 Gb). I hope that the vendor will change the damaged > hdd, but I am quite sure that this is a very serious problem in FreeBSD > kernel. What, that it can't run with your defective hardware? I'm sure we'd all like software that didn't actually need working hardware to run on, but that's like expecting room-temperature fusion in an icebucket. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 08:48:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26880 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 08:48:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles361.castles.com [208.214.167.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26872 for ; Thu, 12 Nov 1998 08:48:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA11406; Thu, 12 Nov 1998 08:43:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811121643.IAA11406@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jamie Bowden cc: Luigi Rizzo , nick.hibma@jrc.it, hackers@FreeBSD.ORG, usb-bsd@makelist.com Subject: Re: update on USB stack/call for help In-reply-to: Your message of "Thu, 12 Nov 1998 08:56:54 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Nov 1998 08:43:08 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I bought an HP 6200c about 2 months ago because it was the only scanner on > the shelf with a scsi interface on it. It also happens to have a USB plug > as well. Does this device have two different command sets on it, or is > twain riding on top of USB? "Twain" is the software interface between the scanner-specific drivers and the user application. SCSI scanners are usually processor target devices, and their communications protocols are all proprietary. There is no indication that this will be any different for USB; there's certainly nothing that leads me to expect a standardised command set or data format(s). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 08:56:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27508 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 08:56:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27503 for ; Thu, 12 Nov 1998 08:56:31 -0800 (PST) (envelope-from lile@stdio.com) Received: from localhost (lile@localhost) by heathers.stdio.com (8.8.8/8.8.8) with SMTP id LAA29057; Thu, 12 Nov 1998 11:59:38 -0500 (EST) (envelope-from lile@heathers.stdio.com) Date: Thu, 12 Nov 1998 11:59:37 -0500 (EST) From: "Larry S. Lile" To: "Ron G. Minnich" cc: hackers@FreeBSD.ORG Subject: Re: PCI device question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Nov 1998, Ron G. Minnich wrote: > On Thu, 12 Nov 1998, Larry S. Lile wrote: > > What is the "64 byte PCI configuration space header" and where do I get > > that from (what pci_* call) > > > > I already know the io-base address, dma-level, csn, pci slot, ... from > > another call. > > That's where stuff like base address etc. are. If you have pulled out > base address info via config read and friends then you already know. If > you are not pulling base etc. out via config reads then you have to fix > your driver :-) > > Functions look like this: > int data = pci_conf_read(tag, PCI_CLASS_REG); > > Are you using these? No, there is a probe function in the driver kit that will find all of the adapters presumably through PIO, so I have not neede to delve into this yet. They then want a pointer into the right spot in memory for the config. info passed into another function. What I need is a way to get a pointer (char *) to the beginning of the config. info for a particular card (one with a PCI ID of 108D0001). Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 09:03:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA28107 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 09:03:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles361.castles.com [208.214.167.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA28101 for ; Thu, 12 Nov 1998 09:03:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA11527; Thu, 12 Nov 1998 08:59:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811121659.IAA11527@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Larry S. Lile" cc: "Ron G. Minnich" , hackers@FreeBSD.ORG Subject: Re: PCI device question In-reply-to: Your message of "Thu, 12 Nov 1998 11:59:37 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Nov 1998 08:59:43 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I already know the io-base address, dma-level, csn, pci slot, ... from > > > another call. > > > > That's where stuff like base address etc. are. If you have pulled out > > base address info via config read and friends then you already know. If > > you are not pulling base etc. out via config reads then you have to fix > > your driver :-) > > > > Functions look like this: > > int data = pci_conf_read(tag, PCI_CLASS_REG); > > > > Are you using these? > > No, there is a probe function in the driver kit that will find all > of the adapters presumably through PIO, so I have not neede to > delve into this yet. They then want a pointer into the right spot > in memory for the config. info passed into another function. Don't do this. It's Bad and Evil and if they feel the only way to find device information is to go behind the system's back then I can't wait to hear what else they think is a "good idea". > What I need is a way to get a pointer (char *) to the beginning > of the config. info for a particular card (one with a PCI ID of > 108D0001). Config data is not guaranteed to be memory-mapped. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 09:14:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29140 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 09:14:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA28839 for ; Thu, 12 Nov 1998 09:10:15 -0800 (PST) (envelope-from roger@cs.strath.ac.uk) Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id RAA08164 Thu, 12 Nov 1998 17:03:51 GMT Message-ID: <364B14F8.6201@cs.strath.ac.uk> Date: Thu, 12 Nov 1998 17:03:52 +0000 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: usb-bsd@egroups.com CC: Jamie Bowden , Luigi Rizzo , nick.hibma@jrc.it, hackers@FreeBSD.ORG, usb-bsd@makelist.com Subject: Re: [usb-bsd] Re: update on USB stack/call for help References: <199811121643.IAA11406@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Perhaps we should start by contacting the various companies and asking for information. Obviously companies whose SCSI scanners we support released information on command sets once so they should be contacted first. I think we should get the people who work on SANE (the Scanner API) involved. Bye Roger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 09:18:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29410 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 09:18:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun1.cc.binghamton.edu (bingsun1.cc.binghamton.edu [128.226.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29397 for ; Thu, 12 Nov 1998 09:18:05 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun1.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id MAA10392; Thu, 12 Nov 1998 12:17:19 -0500 (EST) Date: Thu, 12 Nov 1998 12:17:18 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun1 Reply-To: zhihuizhang To: Julian Elischer cc: hackers Subject: More questions on DEVFS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a couple of questions on DEVFS which is hard to figure out from the source code: (1) As I understand it, special files can be created only by superuser via mknod and file systems can only be mounted by superuser. I do not see any reason why the superuser will mount the device file system multiple times and possibly at different mount points. (2) Both the block and character switch table have a major number at its end (d_maj) which is often set to be -1 (see mem_cdevsw[] in file i386/mem.c for an example). This makes devfs_add_devswf() return without adding a device entry. Is this the way that is used to circuit the DEVFS code on purpose? Thanks for your help. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 09:18:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29447 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 09:18:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from scully.tamu.edu (unix.tamu.edu [128.194.103.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29442 for ; Thu, 12 Nov 1998 09:18:19 -0800 (PST) (envelope-from s0k9955@unix.tamu.edu) Received: from localhost by scully.tamu.edu (8.9.0/8.9.0) with SMTP id LAA02089; Thu, 12 Nov 1998 11:17:41 -0600 (CST) Date: Thu, 12 Nov 1998 11:17:40 -0600 (CST) From: Shafia Kausar To: Mike Smith cc: FreeBSD Hackers , shafiak@ee.tamu.edu Subject: Re: Timer Granularity In-Reply-To: <199810300504.VAA00773@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I need a kernel clock of granularity 1ms or less, for some experiments. Which version of FreeBsd supports this granularity, other than the 3.0 version? There is a mention of the resolution depending on the clock sources in use. Which source gives me the best resolution?? Thanks in advance -Shafia On Thu, 29 Oct 1998, Mike Smith wrote: > > > > I am confused, On basis of which parameters is the kernel clock > > granularity defined?? especially when multiple clocks are available. > > At which release level? 2.1.x, 2.2.x or 3.x? > > As a general rule, the best available clock is used. The techniques > used to determine which clock is best, and to ensure accurate counts > vary from release to release, with a general trend towards better. > > > > > On Thu, 29 Oct 1998, Mike Smith wrote: > > > > > > I am new to the FreeBSD OS. I have a few questions for which I could not > > > > find answers on the webpages. > > > > > > > > I am using the FreeBSD version 2.1.5 Relase #2. What is the kernel clock > > > > granularity in this version? > > > > > > 10ms, if I remember correctly. > > > > > > > > > There are a number of clocks being used in FreeBSD. Which clock is used > > > > for real time kernel processing? Is this accessible to the users? > > > > > > No clocks are "accessible to the users". User applications obtain time > > > values from the system. > > > > > > > Has the timer granularity improved in the releases following this release? > > > > > > Yes. Timer support now offers nanosecond resolution, dependant on the > > > particular clock source(s) in use. > > > > > > > In the /sys/kern/kern_clock.c file the variable time_precision has been > > > > initialised to 1microsec, but it has been stated that the resolution > > > > decreases depending on whether the external clock is working or not. > > > > What is the range of the variation in the resolutuion? > > > > > > It depends on the hardware in use. On some systems the Pentium TSC is > > > available as a time source, in which case time resolution is one CPU > > > cycle. The i8254 timecounter generally has an operating frequency > > > around 1.19MHz, giving a resolution of approximately 1us. > > > > > > -- > > > \\ Sometimes you're ahead, \\ Mike Smith > > > \\ sometimes you're behind. \\ mike@smith.net.au > > > \\ The race is long, and in the \\ msmith@freebsd.org > > > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 09:31:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA00675 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 09:31:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA00670 for ; Thu, 12 Nov 1998 09:31:57 -0800 (PST) (envelope-from lile@stdio.com) Received: from localhost (lile@localhost) by heathers.stdio.com (8.8.8/8.8.8) with SMTP id MAA00382; Thu, 12 Nov 1998 12:34:55 -0500 (EST) (envelope-from lile@heathers.stdio.com) Date: Thu, 12 Nov 1998 12:34:55 -0500 (EST) From: "Larry S. Lile" To: Mike Smith cc: "Ron G. Minnich" , hackers@FreeBSD.ORG Subject: Re: PCI device question In-Reply-To: <199811121659.IAA11527@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Nov 1998, Mike Smith wrote: > > > > I already know the io-base address, dma-level, csn, pci slot, ... from > > > > another call. > > > > > > That's where stuff like base address etc. are. If you have pulled out > > > base address info via config read and friends then you already know. If > > > you are not pulling base etc. out via config reads then you have to fix > > > your driver :-) > > > > > > Functions look like this: > > > int data = pci_conf_read(tag, PCI_CLASS_REG); > > > > > > Are you using these? > > > > No, there is a probe function in the driver kit that will find all > > of the adapters presumably through PIO, so I have not neede to > > delve into this yet. They then want a pointer into the right spot > > in memory for the config. info passed into another function. > > Don't do this. It's Bad and Evil and if they feel the only way to find > device information is to go behind the system's back then I can't wait > to hear what else they think is a "good idea". They have written the kit so that it is OS independent, don't bust an artery. They just want the config info passed to them so their half of the driver can make sure it is ok. Here is their blurb about it... [For PCI adapters the configuration is retrieved by the driver through [PCI BIOS calls (or their equivalents in the OS in question). The PCI ID [to look for is 108D0001 for OC-3136 and OC-3137. To set-up the complete [configuration, retrive the 64 byte configuration space header and pass [this to TRlld. [ [ int TRlldPCIConfig(TRlldDriver_t *driver, TRLLDAdapterConfig_t *config [ char *PCIConfiguration) The "driver" here is the FreeBSD driver, I have to get the info and pass it to them, they don't change it. If they don't like it, they tell me and I have to fix it. I could very easily copy the data into a buffer and pass it to them. Now, the question was (and still is) how do I get the 64 byte configuration header out of FreeBSD, or how do I get a pointer to it? > > > What I need is a way to get a pointer (char *) to the beginning > > of the config. info for a particular card (one with a PCI ID of > > > Config data is not guaranteed to be memory-mapped. Fine, I can copy it into a buffer and pass it to the function. How do I get the data? Could I loop through like this: char foo[64] for (i = 0; i < 64, i++) foo[i] = pci_read_conf(tag, i); And what would "tag" be? How do I relate that to a PCI ID? Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 09:50:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02596 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 09:50:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA02583 for ; Thu, 12 Nov 1998 09:50:15 -0800 (PST) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id MAA16088; Thu, 12 Nov 1998 12:49:21 -0500 Date: Thu, 12 Nov 1998 12:49:21 -0500 (EST) From: "Ron G. Minnich" X-Sender: rminnich@terra To: "Larry S. Lile" cc: hackers@FreeBSD.ORG Subject: Re: PCI device question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Nov 1998, Larry S. Lile wrote: > No, there is a probe function in the driver kit that will find all > of the adapters presumably through PIO, so I have not neede to > delve into this yet. They then want a pointer into the right spot > in memory for the config. info passed into another function. I agree with Mike. The driver kit is doing things the wrong say. Spend a little extra time and get it working the right way, it is not hard and you will not regret it. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 10:03:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03691 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 10:03:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA03488 for ; Thu, 12 Nov 1998 10:00:16 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA09782; Thu, 12 Nov 1998 17:00:13 +0100 From: Luigi Rizzo Message-Id: <199811121600.RAA09782@labinfo.iet.unipi.it> Subject: Re: Timer Granularity To: s0k9955@unix.tamu.edu (Shafia Kausar) Date: Thu, 12 Nov 1998 17:00:12 +0100 (MET) Cc: mike@smith.net.au, freebsd-hackers@FreeBSD.ORG, shafiak@ee.tamu.edu In-Reply-To: from "Shafia Kausar" at Nov 12, 98 11:17:21 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I need a kernel clock of granularity 1ms or less, for some experiments. > Which version of FreeBsd supports this granularity, other than the 3.0 > version? > > There is a mention of the resolution depending on the clock > sources in use. Which source gives me the best resolution?? settin HZ=1000 or more in the kernel config file should do the job (if you go too high you might start losing ticks...) luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 10:06:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04004 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 10:06:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03998 for ; Thu, 12 Nov 1998 10:06:13 -0800 (PST) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id TAA17528; Thu, 12 Nov 1998 19:04:51 +0100 (MET) Message-ID: <19981112190450.A17400@cons.org> Date: Thu, 12 Nov 1998 19:04:50 +0100 From: Martin Cracauer To: Mike Smith , Jamie Bowden Cc: Luigi Rizzo , nick.hibma@jrc.it, hackers@FreeBSD.ORG, usb-bsd@makelist.com Subject: Re: update on USB stack/call for help References: <199811121643.IAA11406@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199811121643.IAA11406@dingo.cdrom.com>; from Mike Smith on Thu, Nov 12, 1998 at 08:43:08AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199811121643.IAA11406@dingo.cdrom.com>, Mike Smith wrote: > > > > I bought an HP 6200c about 2 months ago because it was the only scanner on > > the shelf with a scsi interface on it. It also happens to have a USB plug > > as well. Does this device have two different command sets on it, or is > > twain riding on top of USB? > > "Twain" is the software interface between the scanner-specific drivers > and the user application. SCSI scanners are usually processor target > devices, and their communications protocols are all proprietary. That's not *that* true. Document sgc-r00.pdf on Symbios' ftp site defines "SCSI 3 graphics commands" and my Mustek implements this (more or less, didn't tangle too much with it). Maerin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 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-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 10:08:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04161 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 10:08:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04155 for ; Thu, 12 Nov 1998 10:08:31 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id NAA17224; Thu, 12 Nov 1998 13:07:59 -0500 (EST) Date: Thu, 12 Nov 1998 13:07:59 -0500 (EST) From: Daniel Eischen Message-Id: <199811121807.NAA17224@pcnet1.pcnet.com> To: luigi@labinfo.iet.unipi.it, s0k9955@unix.tamu.edu Subject: Re: Timer Granularity Cc: freebsd-hackers@FreeBSD.ORG, mike@smith.net.au, shafiak@ee.tamu.edu Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I need a kernel clock of granularity 1ms or less, for some experiments. > > Which version of FreeBsd supports this granularity, other than the 3.0 > > version? > > > > There is a mention of the resolution depending on the clock > > sources in use. Which source gives me the best resolution?? > > settin HZ=1000 or more in the kernel config file should do the job (if > you go too high you might start losing ticks...) > > luigi I set HZ to 500 just a couple of days ago on a 1-2 month old -current system without too many hiccups. There still are a few places in the kernel that need to be fixed to use hz properly, though. sysbeep is one. Grep'ing for all the timeout()s and ensuring proper use of hz is a start. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 10:14:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04790 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 10:14:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA04776 for ; Thu, 12 Nov 1998 10:14:15 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA09852; Thu, 12 Nov 1998 17:13:02 +0100 From: Luigi Rizzo Message-Id: <199811121613.RAA09852@labinfo.iet.unipi.it> Subject: Re: Timer Granularity To: eischen@vigrid.com (Daniel Eischen) Date: Thu, 12 Nov 1998 17:13:02 +0100 (MET) Cc: s0k9955@unix.tamu.edu, freebsd-hackers@FreeBSD.ORG, mike@smith.net.au, shafiak@ee.tamu.edu In-Reply-To: <199811121807.NAA17224@pcnet1.pcnet.com> from "Daniel Eischen" at Nov 12, 98 01:07:40 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > settin HZ=1000 or more in the kernel config file should do the job (if > > you go too high you might start losing ticks...) ... > I set HZ to 500 just a couple of days ago on a 1-2 month old > -current system without too many hiccups. There still are when i said "too high" i had in mind 10K or more... I routinely use HZ=1000 in the dummynet floppies... luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 10:31:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06150 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 10:31:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA06137 for ; Thu, 12 Nov 1998 10:31:09 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id JAA09255; Thu, 12 Nov 1998 09:03:12 +0100 From: Luigi Rizzo Message-Id: <199811120803.JAA09255@labinfo.iet.unipi.it> Subject: Re: kernel BOOTP To: n@nectar.com (Jacques Vidrine) Date: Thu, 12 Nov 1998 09:03:11 +0100 (MET) Cc: hackers@FreeBSD.ORG In-Reply-To: <199811102018.OAA20884@spawn.nectar.com> from "Jacques Vidrine" at Nov 10, 98 02:17:41 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > I'm attempting to boot a machine off the floppy, and mount all filesystems > over NFS. The network card is supported by the kernel xl driver, but not > by the netboot code. Therefore, I created a kernel with the BOOTP and > BOOTP_NFSROOT options and put it on a floppy. > > The reply from the BOOTP server is not being received (i.e. ``BOOTP > timeout for server 0xffffffff''). The client and the BOOTP server are > on the same network. there's a chicken and egg problem -- the bootp server is responding to the client's IP address and the latter refuses the reply because it does not know its address (some servers solve the problem by replying to the broadcast address 255.255.255.255, but not all of them and apparently not the one in FreeBSD). You need another option, BOOTP_COMPAT or so, to enable your machine to accept packets before the network card is assigned an address. Look in /sys/i386/conf/LINT. > Is there any documentation for use of kernel BOOTP? Is anyone using it > successfully? something is at http://www.iet.unipi.it/~luigi/FreeBSD.html/ cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 10:35:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06449 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 10:35:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA06168 for ; Thu, 12 Nov 1998 10:31:34 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA09943; Thu, 12 Nov 1998 17:29:43 +0100 From: Luigi Rizzo Message-Id: <199811121629.RAA09943@labinfo.iet.unipi.it> Subject: Re: update on USB stack/call for help To: cracauer@cons.org (Martin Cracauer) Date: Thu, 12 Nov 1998 17:29:43 +0100 (MET) Cc: mike@smith.net.au, jamie@itribe.net, nick.hibma@jrc.it, hackers@FreeBSD.ORG, usb-bsd@makelist.com In-Reply-To: <19981112190450.A17400@cons.org> from "Martin Cracauer" at Nov 12, 98 07:04:31 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > and the user application. SCSI scanners are usually processor target > > devices, and their communications protocols are all proprietary. > > That's not *that* true. Document sgc-r00.pdf on Symbios' ftp site > defines "SCSI 3 graphics commands" and my Mustek implements this (more > or less, didn't tangle too much with it). Yes, in fact i was referring to something like this. I think there is a lot of variance. E.g. my HP Scanjet 5p has some escape sequences to set modes and start scanning. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 10:50:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07787 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 10:50:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07775 for ; Thu, 12 Nov 1998 10:50:36 -0800 (PST) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id MAA01117; Thu, 12 Nov 1998 12:41:33 -0600 (CST) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma001115; Thu, 12 Nov 98 12:41:31 -0600 Received: from spawn.nectar.com (localhost.nectar.com [127.0.0.1]) by spawn.nectar.com (8.9.1/8.9.1) with ESMTP id MAA02453; Thu, 12 Nov 1998 12:41:31 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Message-Id: <199811121841.MAA02453@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: <199811120803.JAA09255@labinfo.iet.unipi.it> References: <199811120803.JAA09255@labinfo.iet.unipi.it> Subject: Re: kernel BOOTP To: Luigi Rizzo cc: hackers@FreeBSD.ORG Date: Thu, 12 Nov 1998 12:41:31 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- On 12 November 1998 at 9:03, Luigi Rizzo wrote: [snip] > there's a chicken and egg problem -- the bootp server is responding to > the client's IP address and the latter refuses the reply because it > does not know its address (some servers solve the problem by replying > to the broadcast address 255.255.255.255, but not all of them and > apparently not the one in FreeBSD). That doesn't work anyway. I tried overriding the reply address with the broadcast address, and the client still didn't ``hear'' it. [By the way, the FreeBSD bootpd needs to setsockopt(s, SO_BROADCAST, ...) in order to use a reply address override of this type. I'm suprised that it doesn't already -- several BOOTP examples I reviewed included ``ra=255.255.255.255'' -- which won't work with our bootpd.] > You need another option, BOOTP_COMPAT or so, to enable your machine to > accept packets before the network card is assigned an address. Look in > /sys/i386/conf/LINT. This is probably the magic I'm missing. Thanks. > something is at http://www.iet.unipi.it/~luigi/FreeBSD.html/ Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNksr2jeRhT8JRySpAQF4IAQArYqhNc5M/IDZVldiD+WH3pc5sTGNSiV1 aZLyAebal3Zrh0dxZ5TnC+cuZtdKRI5su0wvzDNsx3JWs+s26JqER+/V/QZBM935 s7nLSCVU2GfhrHF/J/c+gNxJ9oOv9B/8GqohOST4sM487FMATHs5efAJREQglj9S 4PwSVDLh+Jg= =i4OL -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 10:54:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08352 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 10:54:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail1.netsol.net (mail.netsol.net [38.216.109.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08344 for ; Thu, 12 Nov 1998 10:54:11 -0800 (PST) (envelope-from tech@scsr.com) Received: from ff.scsr.com ([38.185.32.162]) by mail1.netsol.net (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-42781U2500L250S0) with ESMTP id AAA155 for ; Thu, 12 Nov 1998 11:00:53 -0800 From: "Tech1" To: Subject: Fail-Safe cluster on Freebsd Date: Thu, 12 Nov 1998 23:00:23 -0800 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-ID: <19981112190052872.AAA155@ff.scsr.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, guys, my fail safe code is done on freebsd. It's like MS cluster server. detect remote server status-up/down. providing atomatice recovery of the crashed server by auxiliary server that reduce the down time to within a second. Wonder if any one interested to buy this. I am in some financial difficulties recently. This code can be proted to otehr unix variant liek sun or hp. Any one interested send a mail to "tech@scsr.com". matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 11:08:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09424 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 11:08:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from yonge.cs.toronto.edu (yonge.cs.toronto.edu [128.100.2.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA09381 for ; Thu, 12 Nov 1998 11:07:58 -0800 (PST) (envelope-from dholland@cs.toronto.edu) Received: from qew.cs.toronto.edu ([128.100.2.15]) by yonge.cs.toronto.edu with SMTP id <86508-8537>; Thu, 12 Nov 1998 14:07:34 -0500 Received: by qew.cs.toronto.edu id <37768-2936>; Thu, 12 Nov 1998 14:07:18 -0500 Subject: Re: bsd make to gnu make conversion, anyone?? From: David Holland To: kline@tao.thought.org (Gary Kline) Date: Thu, 12 Nov 1998 14:07:09 -0500 Cc: dholland@cs.toronto.edu, hackers@FreeBSD.ORG In-Reply-To: <199811120641.WAA04442@tao.thought.org> from "Gary Kline" at Nov 12, 98 01:41:58 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <98Nov12.140718edt.37768-2936@qew.cs.toronto.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You might be better off compiling bsd make on whatever box you're > > using. > > Can't. We're doing the entire BSD built using > gmake. .... uh, why? if you're building the entire tree it's *much* less work to port make than to change all the makefiles. Been there, done that, have the t-shirts.. > Is there a cleaner way using /bin/sh commands > within gmake? Something like > > for $${lang} in $${LANGS} > do > .... > done Yes. As this has already been posted (twice) I won't repeat it... -- - David A. Holland | (please continue to send non-list mail to dholland@cs.utoronto.ca | dholland@hcs.harvard.edu. yes, I moved.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 11:13:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09927 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 11:13:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from yonge.cs.toronto.edu (yonge.cs.toronto.edu [128.100.2.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA09902 for ; Thu, 12 Nov 1998 11:13:04 -0800 (PST) (envelope-from dholland@cs.toronto.edu) Received: from qew.cs.toronto.edu ([128.100.2.15]) by yonge.cs.toronto.edu with SMTP id <86461-8532>; Thu, 12 Nov 1998 14:12:39 -0500 Received: by qew.cs.toronto.edu id <37768-2936>; Thu, 12 Nov 1998 14:12:20 -0500 Subject: Re: bsd make to gnu make conversion, anyone?? From: David Holland To: joelh@gnu.org (Joel Ray Holveck) Date: Thu, 12 Nov 1998 14:12:14 -0500 Cc: dholland@cs.toronto.edu, kline@tao.thought.org, hackers@FreeBSD.ORG In-Reply-To: <86hfw5ie8q.fsf@detlev.UUCP> from "Joel Ray Holveck" at Nov 12, 98 02:04:05 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <98Nov12.141220edt.37768-2936@qew.cs.toronto.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is the cleanest solution. Still, if you want alternatives, I > haven't tried this, but foreach may work here, as a generalization of > for: > > define do-lang > $(lang).mv.cat: $(.CURDIR)/nls/$(lang)/mv.msg > gencat -new $(.TARGET) $(.ALLSRC) > endef > $(foreach lang,$(LANGS),$(do-lang)) eww. I didn't know this would work. I wish someone would add support for bsd make syntax to gmake. (Before you tell me to put my code where my mouth is, I looked into this at one point and concluded it would take me longer to figure out how gmake's parser worked than to write a whole new make. So I didn't. Why doesn't it use yacc?) > What's wrong with using sh like God intended? Two reasons; one that issuing complex shell commands makes make -n output less useful (for an extreme case of this, try make -n install in gnu binutils), and the other that when you do loops in the shell they don't always terminate on error like you (usually) want. For install this may not be that significant, but when you're doing recursion into subdirectories it sucketh. Hard. -- - David A. Holland | (please continue to send non-list mail to dholland@cs.utoronto.ca | dholland@hcs.harvard.edu. yes, I moved.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 11:19:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10687 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 11:19:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lwaxana.cistron.nl (lwaxana.cistron.nl [195.64.68.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10673 for ; Thu, 12 Nov 1998 11:19:02 -0800 (PST) (envelope-from wouters@cistron.nl) Received: from localhost.localdomain (cs5p22.dial.cistron.nl [62.216.0.23]) by lwaxana.cistron.nl (8.9.1a/8.9.1/Debian/GNU) with SMTP id UAA30618; Thu, 12 Nov 1998 20:17:16 +0100 Message-ID: <364B228F.6A984F58@cistron.nl> Date: Thu, 12 Nov 1998 19:01:51 +0100 From: WHS Organization: robots anonymous X-Mailer: Mozilla 3.01 (X11; I; Linux 2.0.34 i686) MIME-Version: 1.0 To: cpl92@fx.ro, freebsd-hackers@FreeBSD.ORG Subject: Re: sever ide hdd crash (also re:Another instance of the crash I was seeing) References: <199811121037.LAA00549@freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Søren Schmidt wrote: > > It seems cpl92@fx.ro wrote: > > One day ago, under the same circumstances (only that the used dist was > > 2.2.7-RELEASE), while I was looking far a tarball distribution in CD #3 > > (WALNUT CREAK 2.2.7), I heard the CD slowing down. Knowing what happened > > last time, I tried alt+ctrl+F1 to see the syslog mesg. Surprize again: > > the computer was not responding to any of the possible commands. I have > > waited a couple of minutes (the hdd was not running), then I have pushed > > the front pannel reset button. Surprize again: While reseting the > > computer I received the BIOS message PRIMARY HDD FAILURE. Since then, my > > BIOS says that I don't have a HDD inside (actually I have a Quantum > > Fireball UDMA 4.3 Gb). I hope that the vendor will change the damaged > > hdd, but I am quite sure that this is a very serious problem in FreeBSD > > kernel. > > Hmm, I'm quite sure you have a bad disk, the kernel cannot make your > disk die like that. I've had this same scenario happen (under linux) because the HDD cable got a little loose.. (by fan vibrations probably). Try pressing the cable firmly on the main board and on the HD and see if that helps. Wouter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 11:39:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12472 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 11:39:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12464 for ; Thu, 12 Nov 1998 11:39:02 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id LAA28728; Thu, 12 Nov 1998 11:38:36 -0800 (PST) (envelope-from dillon) Date: Thu, 12 Nov 1998 11:38:36 -0800 (PST) From: Matthew Dillon Message-Id: <199811121938.LAA28728@apollo.backplane.com> To: "Kenneth D. Merry" Cc: aron@cs.rice.edu (Mohit Aron), freebsd-hackers@FreeBSD.ORG Subject: Re: scsi disk queue References: <199811120550.WAA21345@panzer.plutotech.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Neat! I hope you don't mind if I modify the program some. http://www.backplane.com/FreeBSD/dds.c For ongoing reporting of read activity, write activity (avg per second), busy percentage, and request backlog. The busy percentage is especially useful. % ./dds da1 da2 da3 10 nntp1:/news> ./dds da1 da2 da3 10 da1 da2 da3 625k 142k 75%/0 644k 155k 70%/2 652k 137k 72%/1 763k 78.6k 77%/2 792k 96.9k 80%/3 840k 86.4k 80%/2 696k 153k 77%/3 693k 172k 83%/2 702k 163k 80%/4 752k 117k 80%/2 802k 144k 85%/0 839k 104k 88%/2 609k 458k 85%/0 660k 467k 87%/2 622k 449k 87%/2 601k 354k 77%/9 583k 365k 79%/2 597k 341k 79%/6 666k 240k 86%/10 665k 227k 79%/4 680k 240k 88%/7 652k 298k 82%/2 580k 326k 80%/4 619k 290k 79%/3 606k 190k 73%/15 609k 184k 70%/19 652k 188k 82%/16 664k 381k 83%/15 640k 360k 83%/18 656k 383k 76%/16 589k 365k 80%/3 655k 368k 82%/2 601k 343k 90%/1 793k 267k 86%/3 792k 268k 82%/3 818k 286k 90%/0 :If you're running 3.0 or a CAM version of -current or -stable, you can find :out the number of outstanding transactions for any device registered with :the devstat(9) subsystem. : :Download the following program: : :ftp://ftp.kdm.org/pub/FreeBSD/cam/ds.c : :It dumps out the devstat entry for each device. The devstat entry includes :a busy count, which is the number of outstanding transactions queued to the :drive. : :Ken :-- :Kenneth Merry :ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 11:42:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13057 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 11:42:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13050 for ; Thu, 12 Nov 1998 11:42:52 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id UAA05130; Thu, 12 Nov 1998 20:42:29 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA09200 (5.67b/IDA-1.5); Thu, 12 Nov 1998 20:25:30 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id UAA01157; Thu, 12 Nov 1998 20:16:48 +0100 (CET) From: Wilko Bulte Message-Id: <199811121916.UAA01157@yedi.iaf.nl> Subject: Re: sever ide hdd crash (also re:Another instance of the crash I was seeing) In-Reply-To: <364A0A3A.EEBFB63A@fx.ro> from "cpl92@fx.ro" at "Nov 12, 98 00:05:47 am" To: cpl92@fx.ro Date: Thu, 12 Nov 1998 20:16:48 +0100 (CET) Cc: freebsd-hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As cpl92@fx.ro wrote... > Hi, > > I experienced yesterday a sever ide hdd crash. My computer is not > operating these days, so please answer also to this address I'm using > now. [ stuff deleted ] > computer I received the BIOS message PRIMARY HDD FAILURE. Since then, my > BIOS says that I don't have a HDD inside (actually I have a Quantum > Fireball UDMA 4.3 Gb). I hope that the vendor will change the damaged > hdd, but I am quite sure that this is a very serious problem in FreeBSD > kernel. ?? What makes you believe FreeBSD has a 'kiss of death' bug for IDE harddisks? Harddisks die every now and then. There is nothing an OS can do about that fact of life. Although it would be amusing to see a class action against Microsoft for every harddisk that died using Windows... ;-) Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 11:44:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13235 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 11:44:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from arjun.niksun.com (gw.niksun.com [206.20.52.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13230 for ; Thu, 12 Nov 1998 11:44:40 -0800 (PST) (envelope-from ath@niksun.com) Received: from stiegl.niksun.com (stiegl.niksun.com [10.0.0.44]) by arjun.niksun.com (8.8.8/8.8.8) with ESMTP id NAA14702; Thu, 12 Nov 1998 13:47:32 -0500 (EST) Received: (from ath@localhost) by stiegl.niksun.com (8.8.8/8.8.7) id OAA24413; Thu, 12 Nov 1998 14:44:06 -0500 (EST) (envelope-from ath) To: "Ron G. Minnich" cc: hackers@FreeBSD.ORG Subject: Re: pcibridge card (really) References: From: Andrew Heybey Date: 12 Nov 1998 14:44:05 -0500 In-Reply-To: "Ron G. Minnich"'s message of "Wed, 11 Nov 1998 14:30:25 -0500 (EST)" Message-ID: <85k9103ddm.fsf@stiegl.niksun.com> Lines: 15 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Ron G. Minnich" writes: > I have a dolphin sci card that says it is a bridge. There appears to be > no equivalent to: DATA_SET (pcidevice_set, scisc_device); > for bridges. Other than modifying pcisupport.c is there any way to get > the kernel to probe this card? It's not getting probed now as part of > pci init. because pci thinks it is a bridge. I had a similar situation with a card with a PCI-ISA bridge on it. I just hacked a test for the bridge vendor's ID into sys/pci/pci_support.c:generic_pci_bridge() (to not recognize it as a bridge for that particular ID is found). This is clearly not The Right Thing, so I would be interested in finding out what is. andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 12:02:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14842 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 12:02:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from scully.tamu.edu (unix.tamu.edu [128.194.103.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14835 for ; Thu, 12 Nov 1998 12:02:42 -0800 (PST) (envelope-from s0k9955@unix.tamu.edu) Received: from localhost by scully.tamu.edu (8.9.0/8.9.0) with SMTP id OAA21080; Thu, 12 Nov 1998 14:02:10 -0600 (CST) Date: Thu, 12 Nov 1998 14:02:10 -0600 (CST) From: Shafia Kausar To: Daniel Eischen cc: luigi@labinfo.iet.unipi.it, s0k9955@unix.tamu.edu, freebsd-hackers@FreeBSD.ORG, mike@smith.net.au, shafiak@ee.tamu.edu Subject: Re: Timer Granularity In-Reply-To: <199811121807.NAA17224@pcnet1.pcnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I need a kernel clock of granularity 1ms or less, for some experiments. > > > Which version of FreeBsd supports this granularity, other than the 3.0 > > > version? > > > > > > There is a mention of the resolution depending on the clock > > > sources in use. Which source gives me the best resolution?? > > > > settin HZ=1000 or more in the kernel config file should do the job (if > > you go too high you might start losing ticks...) > > > > luigi > > I set HZ to 500 just a couple of days ago on a 1-2 month old > -current system without too many hiccups. There still are > a few places in the kernel that need to be fixed to use hz > properly, though. sysbeep is one. Grep'ing for all the > timeout()s and ensuring proper use of hz is a start. > Can I set the value of HZ in the 2.1.5 version? I believe the granularity of the clock in this version is 10ms. Does changing the value of HZ change the granularity? If yes, then why is the granularity specified as 10ms?? Thanks -Shafia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 12:08:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15480 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 12:08:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zeus.carroll.com (zeus.carroll.com [199.224.10.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15436 for ; Thu, 12 Nov 1998 12:07:49 -0800 (PST) (envelope-from jim@carroll.com) Received: from apollo.carroll.com [199.224.10.3] by zeus.carroll.com with ESMTP (8.8.5/0) id PAA06379; Thu, 12 Nov 1998 15:07:21 -0500 Received: by apollo.carroll.com (8.8.5) is PAA08366; Thu, 12 Nov 1998 15:07:21 -0500 Date: Thu, 12 Nov 1998 15:07:19 -0500 From: Jim Carroll To: freebsd-hackers@FreeBSD.ORG Subject: 10/100 ISA Support Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone know if any 10/100 ISA Cards are supported ? Specifically, the 3C515-TX ? I know it's a little pointless trying to get true 100 M performance out of an ISA bus, but it is convenient to be able to drop into a LAN that only has 100B-T support. --- Jim C., President | C A R R O L L - N E T, Inc. 201-488-1332 | New Jersey's Premier Internet Service Provider www.carroll.com | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 12:12:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16298 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 12:12:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16293 for ; Thu, 12 Nov 1998 12:12:10 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id NAA24806; Thu, 12 Nov 1998 13:11:37 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811122011.NAA24806@panzer.plutotech.com> Subject: Re: scsi disk queue In-Reply-To: <199811121938.LAA28728@apollo.backplane.com> from Matthew Dillon at "Nov 12, 98 11:38:36 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 12 Nov 1998 13:11:37 -0700 (MST) Cc: aron@cs.rice.edu, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote... > Neat! I hope you don't mind if I modify the program some. > > http://www.backplane.com/FreeBSD/dds.c No problem. Looks interesting. > For ongoing reporting of read activity, write activity (avg per second), > busy percentage, and request backlog. > > The busy percentage is especially useful. I would take the busy time stuff with a grain of salt. It is only updated when the busy count goes to zero. (to save CPU cycles, among other things) So if the disk stays busy for 10 seconds, the busy time won't get updated until the end of that 10 second period. So this can have some interesting results (using a 1 second update): da0 da1 22.4k 15.6k 2%/0 5.9k 5.76m 65%/10 31.9k 8.0k 4%/0 6.0k 4.11m 76%/21 2.0k 39.6k 0%/0 25.7k 5.75m 0%/24 14.9k 7.9k 0%/0 31.7k 5.02m 147%/18 118k 87.1k 16%/0 11.9k 4.03m 148%/10 0.0k 31.7k 0%/0 25.7k 7.12m 0%/12 0.0k 0.0k 0%/0 17.8k 7.87m 0%/18 28.7k 0.0k 3%/0 19.8k 203k 223%/10 > % ./dds da1 da2 da3 10 > nntp1:/news> ./dds da1 da2 da3 10 > da1 da2 da3 > 625k 142k 75%/0 644k 155k 70%/2 652k 137k 72%/1 > 763k 78.6k 77%/2 792k 96.9k 80%/3 840k 86.4k 80%/2 > 696k 153k 77%/3 693k 172k 83%/2 702k 163k 80%/4 [ ... ] > :If you're running 3.0 or a CAM version of -current or -stable, you can find > :out the number of outstanding transactions for any device registered with > :the devstat(9) subsystem. > : > :Download the following program: > : > :ftp://ftp.kdm.org/pub/FreeBSD/cam/ds.c > : > :It dumps out the devstat entry for each device. The devstat entry includes > :a busy count, which is the number of outstanding transactions queued to the > :drive. > : > :Ken > :-- > :Kenneth Merry > :ken@plutotech.com > Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 12:20:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17158 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 12:20:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17142 for ; Thu, 12 Nov 1998 12:20:55 -0800 (PST) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (tao.tera.com [207.108.223.55]) by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id MAA15685; Thu, 12 Nov 1998 12:20:17 -0800 (PST) Received: (from kline@localhost) by tao.thought.org (8.8.8/8.7.3) id MAA09113; Thu, 12 Nov 1998 12:20:05 -0800 (PST) Message-ID: <19981112122005.C7958@thought.org> Date: Thu, 12 Nov 1998 12:20:05 -0800 From: Gary Kline To: David Holland , Joel Ray Holveck Cc: kline@tao.thought.org, hackers@FreeBSD.ORG Subject: Re: bsd make to gnu make conversion, anyone?? References: <86hfw5ie8q.fsf@detlev.UUCP> <98Nov12.141220edt.37768-2936@qew.cs.toronto.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <98Nov12.141220edt.37768-2936@qew.cs.toronto.edu>; from David Holland on Thu, Nov 12, 1998 at 02:12:14PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 12, 1998 at 02:12:14PM -0500, David Holland wrote: > > This is the cleanest solution. Still, if you want alternatives, I > > haven't tried this, but foreach may work here, as a generalization of > > for: > > > > define do-lang > > $(lang).mv.cat: $(.CURDIR)/nls/$(lang)/mv.msg > > gencat -new $(.TARGET) $(.ALLSRC) > > endef > > $(foreach lang,$(LANGS),$(do-lang)) > > eww. > > I didn't know this would work. As written it doesn't. I carefully tried it in a test case late last night. But it may after I've played around with it; tweaked it. > > I wish someone would add support for bsd make syntax to gmake. > What? and make life simple? > (Before you tell me to put my code where my mouth is, I looked into > this at one point and concluded it would take me longer to figure out > how gmake's parser worked than to write a whole new make. So I > didn't. Why doesn't it use yacc?) I've never looked at the guts, but one of our hackers did; added some features. Not adding the BSD syntax, obviously. .... > > > What's wrong with using sh like God intended? > > Two reasons; one that issuing complex shell commands makes make -n > output less useful (for an extreme case of this, try make -n install > in gnu binutils), and the other that when you do loops in the shell > they don't always terminate on error like you (usually) want. > > For install this may not be that significant, but when you're doing > recursion into subdirectories it sucketh. Hard. > Hm. When I've figured it out, I'll share. gary -- Gary D. Kline kline@tao.thought.org Public service uNix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 12:23:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17422 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 12:23:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17414 for ; Thu, 12 Nov 1998 12:23:27 -0800 (PST) (envelope-from lile@stdio.com) Received: from localhost (lile@localhost) by heathers.stdio.com (8.8.8/8.8.8) with SMTP id PAA06795; Thu, 12 Nov 1998 15:26:32 -0500 (EST) (envelope-from lile@heathers.stdio.com) Date: Thu, 12 Nov 1998 15:26:32 -0500 (EST) From: "Larry S. Lile" To: "Ron G. Minnich" cc: hackers@FreeBSD.ORG Subject: Re: PCI device question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Nov 1998, Ron G. Minnich wrote: > On Thu, 12 Nov 1998, Larry S. Lile wrote: > > No, there is a probe function in the driver kit that will find all > > of the adapters presumably through PIO, so I have not neede to > > delve into this yet. They then want a pointer into the right spot > > in memory for the config. info passed into another function. > > I agree with Mike. The driver kit is doing things the wrong say. Spend a > little extra time and get it working the right way, it is not hard and > you will not regret it. Please read this, think about it, and then respond... 1. I want to get the entire pci config header from the card, or at least the first 64 bytes. 2. I pass this information to the lld (olicom kit), it looks at it and makes sure it is the right card, and configured in a sane way. It makes NO CHANGES, it might set its ioaddress appropriately, or set its irq - but only in its structures NOT in the card. 3. I look at its return code, 3 possibilities. 1. GOOD - do nothing 2. BAD - lld doesn't think it is an adapter, wont use it 3. SET_MASTER - For some reason the card has not been set to master mode by the bios - I must go fix this with pci_write**** (whatever) 4. That is all folks! Any io done to or from the card is redirected through calls to my FBSD driver, which get punched through to inb, outb, ... Any memory access the lld does, I have to give it the virtual and/or physical address(dma only). Any card reconfiguration that happens goes like this: I call an lld function to tell it what i want. It calls my io functions to get it done. Anything that affects the OS I have to do. Bottom line: The lld is NOT doing anything wrong! It never end runs the OS. Now I fear that no one will ever give me an answer to this question because everyone who has responded has said "Oh, GOD NO! Don't do that" because they failed to read the question and answer me. Instead FUD and assumption has been rampant, you have tried to assume what myself and the lld are going to do. Just please answer the question and give me the benefit of the doubt - if I do something wrong it will only affect me! If you are interested in what the lld does please go to: http://anarchy.stdio.com/pmw/doc/user.txt once you have read this and understood it, feel free to bring up anything you see wrong with it. If you want to look at what my driver does please go to: http://anarchy.stdio.com/oltr/if_oltr.c And then you can tell me all the things you don't like about my driver. This is not directed at any one person in general, it is just the case that often people reply to posts without reading the entire post, or making assumptions about their intent. This leads to lots of static and no signal, just plain FUD. Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 12:31:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18194 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 12:31:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA18187 for ; Thu, 12 Nov 1998 12:30:57 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA09958; Thu, 12 Nov 1998 17:37:13 +0100 From: Luigi Rizzo Message-Id: <199811121637.RAA09958@labinfo.iet.unipi.it> Subject: Re: [usb-bsd] Re: update on USB stack/call for help To: roger@cs.strath.ac.uk (Roger Hardiman) Date: Thu, 12 Nov 1998 17:37:13 +0100 (MET) Cc: usb-bsd@egroups.com, jamie@itribe.net, nick.hibma@jrc.it, hackers@FreeBSD.ORG, usb-bsd@makelist.com In-Reply-To: <364B14F8.6201@cs.strath.ac.uk> from "Roger Hardiman" at Nov 12, 98 05:03:33 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Perhaps we should start by contacting the various > companies and asking for information. it only works for very few companies. > Obviously companies whose SCSI scanners we support released > information on command sets once so they should be contacted first. > > I think we should get the people who work on SANE (the Scanner API) > involved. as a comment: the last version of SANE (0.74) dates back to July, and i think no parallel or USB scanners are supported by them. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 12:37:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18634 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 12:37:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18628 for ; Thu, 12 Nov 1998 12:37:38 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA01144; Thu, 12 Nov 1998 12:28:59 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdKL1127; Thu Nov 12 20:28:46 1998 Date: Thu, 12 Nov 1998 12:28:08 -0800 (PST) From: Julian Elischer To: Nick Hibma cc: FreeBSD hackers mailing list , USB BSD list Subject: Re: update on USB stack/call for help In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a USB on our new cyrix based board that I willneed to be investigating soon. I believe it's the non-intel standard interface.. julian On Thu, 12 Nov 1998, Nick Hibma wrote: > > > The porting of the NetBSD USB stack to FreeBSD is progressing. We are at > the point were actual device drivers are to be tested/implemented. The > (working) beginnings of the following are there: > > - printer driver (not test under FreeBSD yet, but working under > NetBSD) > > - generic driver (as in very generic, you'll know the name and > serial number of your device and that's it. But the NetBSD folks > are working on that one, as well as I do on the side). > > - mouse driver (working, cut&paste works on my laptop). > (do _not_ remove the mouse while the mouse is used by any > userland program, the interrupt pipe is not killed and your > computer will go pop, without you being able to reset > it). > > - keyboard driver (possibly attaches, but connection to syscons > has not yet been made). > > - HID (human interface device driver), a general driver for any > kind of human interface device. Drivers for joysticks or > touchpads should not be too hard to write with this available. > > > If you download the stack, check the README for installation > instructions. Be aware of the fact that the code is alpha, so if it > breaks, you can keep the pieces. > > > Anyone wanting to get his hands dirty could have a look at the following > parts: > > - keyboard driver: > someone has to pick that up and make the driver not only > work with USB keyboard but also together with syscons. > NetBSD uses a completely different abstraction layer > there, so that requires a bit of work. > > - mouse driver: > someone needs to properly implement the PS/2 emulation > or write the sysmouse version of it. At the moment this > has been a quick&dirty job to get it working. > > - OHCI driver: > requires compliant motherboard (non-Intel 82371 board, > see your dmesg); low level driver has not been ported > yet, but is high on the list of priorities. > > - general: > testing, like installing it and telling me whether it > works for you or not > > - video camera driver: > Windows 1895 is not able to do something sensible with > my camera, so I will start on that one as soon as > possible > > > One big problem that has to be solved as soon as possible: Dynamic > attachment and detachment, including (manual) dynamic loading of the > drivers. detachment is not implemented in the NetBSD version yet. > That I am going to try and solve this weekend. > > > > The USB stack can be fetched from > http://www.etla.net/~n_hibma/usb/usb.pl > > Mailing list for people participating in coding: > http://www.egroups.com/list/usb-bsd/ > > Info on USB in general: > http://www.usb.org > > (nice poll: 'Are you running Windows '98 as your OS?' > 49% of 415 votes says 'No'! That is a lot for a site that is > referenced by early adopters.) > > > Cheers, > > Nick Hibma > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 13:21:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23179 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 13:21:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uucp.intac.com (uucp.intac.com [198.6.114.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23174 for ; Thu, 12 Nov 1998 13:21:54 -0800 (PST) (envelope-from oortiz@LCSI.COM) From: oortiz@LCSI.COM Received: (uucp@localhost) by uucp.intac.com (8.9.1/8.9.1 dman) with UUCP id QAA08698 for freebsd-hackers@freebsd.org; Thu, 12 Nov 1998 16:20:27 -0500 (EST) Received: from Connect2 Message Router by lcsi.LCSI.COM via Connect2-UUCP v1.00.34; Thu, 12 Nov 98 16:12:35 -0500 Message-Id: Date: Thu, 12 Nov 98 16:03:59 -0500 Organization: LCS Industries To: freebsd-hackers@FreeBSD.ORG Subject: IP Tunneling Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7BIT X-Mailer: Connect2-UUCP v1.00.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I hope this is the right forum for this, if not, then I apologize. Can any one give me the steps in setting up IP Tunneling in FreeBSD 2.2.7. I have 5 IP's that I would like to tunnel from a FreeBSD box to a Linux box, but I can't figure out the steps on the FreeBSD box. Would anyone know or tell me where I can get documentation on this? Many Thanks... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 13:33:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24331 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 13:33:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from yonge.cs.toronto.edu (yonge.cs.toronto.edu [128.100.1.8]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA24313 for ; Thu, 12 Nov 1998 13:33:12 -0800 (PST) (envelope-from dholland@cs.toronto.edu) Received: from qew.cs.toronto.edu ([128.100.2.15]) by yonge.cs.toronto.edu with SMTP id <86508-8537>; Thu, 12 Nov 1998 16:32:43 -0500 Received: by qew.cs.toronto.edu id <37768-2936>; Thu, 12 Nov 1998 16:32:33 -0500 Subject: Re: bsd make to gnu make conversion, anyone?? From: David Holland To: kline@thought.org (Gary Kline) Date: Thu, 12 Nov 1998 16:32:30 -0500 Cc: dholland@cs.toronto.edu, joelh@gnu.org, kline@tao.thought.org, hackers@FreeBSD.ORG In-Reply-To: <19981112122005.C7958@thought.org> from "Gary Kline" at Nov 12, 98 03:20:05 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <98Nov12.163233edt.37768-2936@qew.cs.toronto.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Thu, Nov 12, 1998 at 02:12:14PM -0500, David Holland wrote: > > > This is the cleanest solution. Still, if you want alternatives, I > > > haven't tried this, but foreach may work here, as a generalization of > > > for: > > > > > > define do-lang > > > $(lang).mv.cat: $(.CURDIR)/nls/$(lang)/mv.msg > > > gencat -new $(.TARGET) $(.ALLSRC) > > > endef > > > $(foreach lang,$(LANGS),$(do-lang)) Another thing you can do is support.mk: Makefile echo $(LANGS) | awk '{ for (i=1; i<=NF; i++) print $$i;}' |\ awk '{ printf "%s.mv.cat $$(.CURDIR)/nls/%s/mv.msg\n", $$1, $$1}' |\ awk '{ printf "%s: %s\n\tgencat -new %s %s\n\n", \ $$1, $$2, $$1, $$2}' > support.mk include support.mk There are assorted possible variations on this... > > eww. > > > > I didn't know this would work. > > > As written it doesn't. I carefully tried it in a test > case late last night. But it may after I've played > around with it; tweaked it. alas. Here I'd hoped you'd found a general solution for .for in gmake. > > (Before you tell me to put my code where my mouth is, I looked into > > this at one point and concluded it would take me longer to figure out > > how gmake's parser worked than to write a whole new make. So I > > didn't. Why doesn't it use yacc?) > > I've never looked at the guts, but one of our hackers did; > added some features. Not adding the BSD syntax, obviously. > .... hm.. > > Two reasons; one that issuing complex shell commands makes make -n > > output less useful (for an extreme case of this, try make -n install > > in gnu binutils), and the other that when you do loops in the shell > > they don't always terminate on error like you (usually) want. > > > > For install this may not be that significant, but when you're doing > > recursion into subdirectories it sucketh. Hard. So yeah, here's how you do subdirectories in gmake, in case anyone's interested: SUBDIRS=a b c d TARGETS=all install depend clean TMP1:=$(foreach dir, $(SUBDIRS), $(TARGETS)) TMP2:=$(foreach dir, $(SUBDIRS), $(foreach tgt, $(TARGETS), $(dir)/)) TMP3:=$(join $(TMP2), $(TMP1)) TMP4:=$(patsubst %, %/%, $(SUBDIRS)) $(TARGETS): %: $(TMP4) $(TMP3): %: @echo $(MAKE) -C $(patsubst %/, %, $(dir $@)) $(notdir $@) -- - David A. Holland | (please continue to send non-list mail to dholland@cs.utoronto.ca | dholland@hcs.harvard.edu. yes, I moved.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 13:59:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27431 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 13:59:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (tex-95.camalott.com [208.229.74.95]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27426 for ; Thu, 12 Nov 1998 13:59:55 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id PAA21171; Thu, 12 Nov 1998 15:59:25 -0600 (CST) (envelope-from joelh) To: Steve Kargl Cc: dfr@nlsystems.com, sos@freebsd.dk, n@nectar.com, nate@mt.sri.com, kkennawa@physics.adelaide.edu.au, dnelson@emsphone.com, rivers@dignus.com, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname References: <199811121549.HAA05341@troutmask.apl.washington.edu> From: Joel Ray Holveck Date: 12 Nov 1998 15:59:24 -0600 In-Reply-To: Steve Kargl's message of "Thu, 12 Nov 1998 07:49:57 -0800 (PST)" Message-ID: <867lx0r2rn.fsf@detlev.UUCP> Lines: 33 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> What about install scripts that reside on cdroms? You can't magically >>> edit a cdrom install script unless unionfs works. >> I'm not talking about editing a script. I'm talking about: >> PATH=/compat/linux/bin:/compat/linux/usr/bin:${PATH} ; make install > Echo: What about install scripts that reside on cdroms? You can't magically > edit a cdrom install script unless unionfs works. > #! /bin/sh > PATH=/cdrom:/foo:/bar > export PATH > ... > rest of script You can copy the script to a different directory and execute it from there. If you have a full /compat/linux, you may be able to chroot to that and not worry about the path. You can set the path to include /compat/linux before executing your install scripts. I have heard no proposals that could magically look at a given install script and determine whether it is for Linux or FreeBSD, and handle uname correctly. Until I do, I will assert that any install script must be run with some changes to the environment-- although not the script. You set the path, THEN run the script from the install cd-rom. I do not see any possible way to handle all Linux install scripts out of the box, unless you want to run Linux. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 14:03:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28202 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 14:03:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28191 for ; Thu, 12 Nov 1998 14:03:40 -0800 (PST) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (tao.tera.com [207.108.223.55]) by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id OAA18458; Thu, 12 Nov 1998 14:03:17 -0800 (PST) Received: (from kline@localhost) by tao.thought.org (8.8.8/8.7.3) id OAA09722; Thu, 12 Nov 1998 14:03:06 -0800 (PST) Message-ID: <19981112140306.A9591@thought.org> Date: Thu, 12 Nov 1998 14:03:06 -0800 From: Gary Kline To: David Holland Cc: joelh@gnu.org, kline@tao.thought.org, hackers@FreeBSD.ORG Subject: Re: bsd make to gnu make conversion, anyone?? References: <19981112122005.C7958@thought.org> <98Nov12.163233edt.37768-2936@qew.cs.toronto.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <98Nov12.163233edt.37768-2936@qew.cs.toronto.edu>; from David Holland on Thu, Nov 12, 1998 at 04:32:30PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 12, 1998 at 04:32:30PM -0500, David Holland wrote: > > > Another thing you can do is > > support.mk: Makefile > echo $(LANGS) | awk '{ for (i=1; i<=NF; i++) print $$i;}' |\ > awk '{ printf "%s.mv.cat $$(.CURDIR)/nls/%s/mv.msg\n", $$1, $$1}' |\ > awk '{ printf "%s: %s\n\tgencat -new %s %s\n\n", \ > $$1, $$2, $$1, $$2}' > support.mk > include support.mk > > There are assorted possible variations on this... > Something like this crossed my mind; either in each utility makefile or in a separate file. Putting it in a ``bsd.support.mk'' would be cleaner. Good idea! > > So yeah, here's how you do subdirectories in gmake, in case anyone's > interested: > > SUBDIRS=a b c d > TARGETS=all install depend clean > > > TMP1:=$(foreach dir, $(SUBDIRS), $(TARGETS)) > TMP2:=$(foreach dir, $(SUBDIRS), $(foreach tgt, $(TARGETS), $(dir)/)) > TMP3:=$(join $(TMP2), $(TMP1)) > TMP4:=$(patsubst %, %/%, $(SUBDIRS)) > > $(TARGETS): %: $(TMP4) > > $(TMP3): %: > @echo $(MAKE) -C $(patsubst %/, %, $(dir $@)) $(notdir $@) > > Now where have I seen this syntax before! gary -- Gary D. Kline kline@tao.thought.org Public service uNix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 14:05:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28547 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 14:05:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (tex-95.camalott.com [208.229.74.95]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28502 for ; Thu, 12 Nov 1998 14:05:25 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id QAA21208; Thu, 12 Nov 1998 16:04:23 -0600 (CST) (envelope-from joelh) To: Jamie Bowden Cc: hackers@FreeBSD.ORG Subject: Re: linux software installation and uname References: From: Joel Ray Holveck Date: 12 Nov 1998 16:04:23 -0600 In-Reply-To: Jamie Bowden's message of "Thu, 12 Nov 1998 08:14:51 -0500 (EST)" Message-ID: <8667ckr2jc.fsf@detlev.UUCP> Lines: 28 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>> I would recommend putting a Linux >>>> uname in /copmat/linux where it belongs, and the install procedure's >>>> PATH can have /compat/linux ahead of /. >>> chroot /compat/linux ; install >> Not unless you have a complete minimal tree under /compat/linux. > Someone asked for a solution that didn't require corrupting the base > FreeBSD installation or source tree with compatability issues. I am well > aware of the technical necessities of a chrooted environment, but it does > give you a clean way to handle special cases like this. If we assume a complete minimal tree under /compat/linux, then it follows that there exists a /compat/linux/bin/uname. Adding it to the $PATH before running the install script is sufficient. (This would replace the chroot step, so considerations about r/o media do not create a distinction between these proposals.) Therefore, it seems that the requirements for my proposal are a subset of the requirements of yours. If you do a lot of Linux work, then having a complete /compat/linux is probably a good thing. Personally, I don't, so I would prefer to only add a uname. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 14:14:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00208 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 14:14:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00183 for ; Thu, 12 Nov 1998 14:14:12 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id RAA23313; Thu, 12 Nov 1998 17:16:47 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Thu, 12 Nov 1998 17:16:47 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Joel Ray Holveck cc: hackers@FreeBSD.ORG Subject: Re: linux software installation and uname In-Reply-To: <8667ckr2jc.fsf@detlev.UUCP> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12 Nov 1998, Joel Ray Holveck wrote: > >>>> I would recommend putting a Linux > >>>> uname in /copmat/linux where it belongs, and the install procedure's > >>>> PATH can have /compat/linux ahead of /. > >>> chroot /compat/linux ; install > >> Not unless you have a complete minimal tree under /compat/linux. > > Someone asked for a solution that didn't require corrupting the base > > FreeBSD installation or source tree with compatability issues. I am well > > aware of the technical necessities of a chrooted environment, but it does > > give you a clean way to handle special cases like this. > > If we assume a complete minimal tree under /compat/linux, then it > follows that there exists a /compat/linux/bin/uname. Adding it to the > $PATH before running the install script is sufficient. (This would > replace the chroot step, so considerations about r/o media do not > create a distinction between these proposals.) Therefore, it seems > that the requirements for my proposal are a subset of the requirements > of yours. If you do a lot of Linux work, then having a complete > /compat/linux is probably a good thing. Personally, I don't, so I > would prefer to only add a uname. simple solution: If you want linux emulation, then download a minimal linux dist and install it. Perhaps a package could be made for "large emulation" ie, many of the basic linux binaries installed into /compat/linux instead of just the libs and a few key programs. Then chroot would definetly work... Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 14:14:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00301 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 14:14:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from chunga.apana.org.au (chunga.apana.org.au [202.12.89.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00291 for ; Thu, 12 Nov 1998 14:14:47 -0800 (PST) (envelope-from davo@chunga.apana.org.au) Received: (from davo@localhost) by chunga.apana.org.au (8.9.1/8.8.8) id IAA14495 for freebsd-hackers@freebsd.org; Fri, 13 Nov 1998 08:44:15 +1030 (CST) (envelope-from davo) From: Dave Edwards Message-Id: <199811122214.IAA14495@chunga.apana.org.au> Subject: Ijppp and the -alias option To: freebsd-hackers@FreeBSD.ORG Date: Fri, 13 Nov 1998 08:44:13 +1030 (CST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I've been trying to use a few machines on rfc-1597 addresses connecting through a FreeBSD router which dials into an ISP using dynamic addressing. It seems that the ppp process ignores the -background switch and sets up demand dialing when you use the -alias option. The line will drop (and stay dropped) with entries in the logs saying "Idle time expired" when activity ceases (about 30 seconds or so). It turns out that the cost of redialling is more than keeping the link up during the day and with M$ machines on the ethernet, I don't want to risk dialing out at night for no reason. Is this normal behaviour or is there something I'm missing? I can use workarounds if I need to. Also are there any gotchas in this sort of setup that I should watch out for? I've appended the relavent section in ppp.conf and the chunk of log in question. TIA dave -- Dave Edwards davo@chunga.apana.org.au || davo@sa.apana.org.au Adelaide, South Australia ---- ppp is run using: /usr/sbin/ppp -alias -background isp Section from ppp.conf ------- isp: set log Phase Connect Carrier LCP IPCP CCP command set device /dev/cuaa0 set speed 38400 set phone 12345678 set authname foo set authkey foobar set ifaddr 10.10.10.10/0 10.10.11.11/0 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT OK ATE1Q0&D2 OK \\dATDT\\T TIMEOUT 40 CONNECT" default: set device /dev/cuaa0 set speed 57600 disable pred1 deny pred1 disable lqr deny lqr Extract from ppp.log --------- Jan 4 04:00:11 gw ppp[402]: Phase: Parent: PPP enabled. Jan 4 04:00:11 gw ppp[403]: Phase: Parent notified of success. Jan 4 04:00:11 gw ppp[403]: Command: MYADDR: delete ALL Jan 4 04:00:11 gw ppp[403]: Command: MYADDR: add 0 0 HISADDR Jan 4 04:00:11 gw ppp[403]: CCP: Received Configure Ack (2) state = Ack-Sent (8) Jan 4 04:00:11 gw ppp[403]: CCP: State change Ack-Sent --> Opened Jan 4 04:00:11 gw ppp[403]: CCP: CcpLayerUp(9). Jan 4 04:00:11 gw ppp[403]: CCP: Out = none[-1], In = none[-1] Jan 4 04:00:11 gw ppp[403]: CCP: Received Terminate Request (2) state = Opened (9) Jan 4 04:00:11 gw ppp[403]: CCP: CcpLayerDown. Jan 4 04:00:11 gw ppp[403]: CCP: CcpSendTerminateAck Jan 4 04:00:11 gw ppp[403]: CCP: State change Opened --> Stopping Jan 4 04:00:14 gw ppp[403]: CCP: State change Stopping --> Stopped Jan 4 04:00:14 gw ppp[403]: CCP: CcpLayerFinish. Jan 4 04:01:11 gw ppp[403]: Phase: HDLC errors -> FCS: 1 ADDR: 0 COMD: 0 PROTO: 0 Jan 4 11:05:17 gw ppp[403]: Phase: Idle timer expired. Jan 4 11:05:17 gw ppp[403]: Phase: NewPhase: Terminate Jan 4 11:05:17 gw ppp[403]: IPCP: OsLinkdown: 202.12.89.57 Jan 4 11:05:17 gw ppp[403]: IPCP: IpcpLayerDown. Jan 4 11:05:17 gw ppp[403]: IPCP: Connect time: 25506 secs: 4216637 octets in, 4219767 octets out ----------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 14:30:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01708 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 14:30:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01697 for ; Thu, 12 Nov 1998 14:30:08 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA02465; Thu, 12 Nov 1998 14:29:48 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma002462; Thu Nov 12 14:29:35 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id OAA20656; Thu, 12 Nov 1998 14:29:35 -0800 (PST) From: Archie Cobbs Message-Id: <199811122229.OAA20656@bubba.whistle.com> Subject: Re: IP Tunneling In-Reply-To: from "oortiz@LCSI.COM" at "Nov 12, 98 04:03:59 pm" To: oortiz@LCSI.COM Date: Thu, 12 Nov 1998 14:29:35 -0800 (PST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG oortiz@LCSI.COM writes: > > I hope this is the right forum for this, if not, then I apologize. > Can any one give me the steps in setting up IP Tunneling in FreeBSD > 2.2.7. I have 5 IP's that I would like to tunnel from a FreeBSD box to > a Linux box, but I can't figure out the steps on the FreeBSD box. > Would anyone know or tell me where I can get documentation on this? What *kind* of tunnelling? Ie, do you know what software is available on Linux? On FreeBSD you can do SKIP, for example.. and there are some other possibilities floating out there as well.. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 14:34:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02303 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 14:34:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02297 for ; Thu, 12 Nov 1998 14:34:38 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA02525; Thu, 12 Nov 1998 14:34:18 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma002521; Thu Nov 12 14:33:53 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id OAA20678; Thu, 12 Nov 1998 14:33:53 -0800 (PST) From: Archie Cobbs Message-Id: <199811122233.OAA20678@bubba.whistle.com> Subject: Re: More questions on DEVFS In-Reply-To: from zhihuizhang at "Nov 12, 98 12:17:18 pm" To: bf20761@binghamton.edu Date: Thu, 12 Nov 1998 14:33:52 -0800 (PST) Cc: julian@whistle.com, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG zhihuizhang writes: > I have a couple of questions on DEVFS which is hard to figure out from the > source code: > > (1) As I understand it, special files can be created only by superuser via > mknod and file systems can only be mounted by superuser. I do not see any > reason why the superuser will mount the device file system multiple times > and possibly at different mount points. You might want to create a chroot()'d sub-space of your filesystem, and put devices in there for example.. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 14:35:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02424 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 14:35:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (132.camalott.com [208.203.140.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02415 for ; Thu, 12 Nov 1998 14:35:43 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id QAA21363; Thu, 12 Nov 1998 16:35:15 -0600 (CST) (envelope-from joelh) To: David Holland Cc: kline@tao.thought.org, hackers@FreeBSD.ORG Subject: Re: bsd make to gnu make conversion, anyone?? References: <98Nov12.141220edt.37768-2936@qew.cs.toronto.edu> From: Joel Ray Holveck Date: 12 Nov 1998 16:35:14 -0600 In-Reply-To: David Holland's message of "Thu, 12 Nov 1998 14:12:14 -0500" Message-ID: <863e7or13x.fsf@detlev.UUCP> Lines: 38 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > eww. > I didn't know this would work. As Gary later pointed out, it doesn't. As I said, it was just a guess. The hangup is that pattern substitutions cannot introduce multiple targets. I suspect that breaking the Makefile into targets is done before variable substitution, but I don't know. >> What's wrong with using sh like God intended? > Two reasons; one that issuing complex shell commands makes make -n > output less useful (for an extreme case of this, try make -n install > in gnu binutils), I am aware of that, but in this simple case, it's perfectly fine. > and the other that when you do loops in the shell they don't always > terminate on error like you (usually) want. I guess a little extra sh code could fix that at the expense of prettiness. > For install this may not be that significant, but when you're doing > recursion into subdirectories it sucketh. Hard. Quite. Requirements for cross-compatibility across Linux, BSD, and Win32 have brought several of my compile procedures to tears. (In case you're wondering, most Win32 compilers parse #include "..." differently. It's an ambiguity about what is considered the "current directory".) Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 14:41:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03352 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 14:41:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03346 for ; Thu, 12 Nov 1998 14:41:36 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA01264; Thu, 12 Nov 1998 14:39:59 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811122239.OAA01264@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Larry S. Lile" cc: hackers@FreeBSD.ORG Subject: Re: PCI device question In-reply-to: Your message of "Thu, 12 Nov 1998 12:34:55 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Nov 1998 14:39:58 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Thu, 12 Nov 1998, Mike Smith wrote: > > > > > > I already know the io-base address, dma-level, csn, pci slot, ... from > > > > > another call. > > > > > > > > That's where stuff like base address etc. are. If you have pulled out > > > > base address info via config read and friends then you already know. If > > > > you are not pulling base etc. out via config reads then you have to fix > > > > your driver :-) > > > > > > > > Functions look like this: > > > > int data = pci_conf_read(tag, PCI_CLASS_REG); > > > > > > > > Are you using these? > > > > > > No, there is a probe function in the driver kit that will find all > > > of the adapters presumably through PIO, so I have not neede to > > > delve into this yet. They then want a pointer into the right spot > > > in memory for the config. info passed into another function. > > > > Don't do this. It's Bad and Evil and if they feel the only way to find > > device information is to go behind the system's back then I can't wait > > to hear what else they think is a "good idea". > > They have written the kit so that it is OS independent, don't bust an > artery. They just want the config info passed to them so their half > of the driver can make sure it is ok. Here is their blurb about it... You've just said "there is a probe function in the driver kit that will find all of the adapters presumably through PIO". That's bad. It should not do that. Do not do that. It has the ability to screw the PCI config right up. > Now, the question was (and still is) how do I get the 64 byte > configuration header out of FreeBSD, or how do I get a pointer to > it? Use pci_conf_read() like Ron told you three or four messages ago. Pass the tag your attach routine was given as the tag argument, and pass the longword offset you want to read in as the argument, eg. u_int32_t confspace[16]; int i; ... for (i = 0; i < 16; i++) confspace(i) = pci_conf_read(tag, i); The confspace array now contains the 64-byte configuration space contents. There are examples of this in almost every existing PCI driver. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 14:42:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03481 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 14:42:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03471 for ; Thu, 12 Nov 1998 14:42:27 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id XAA21750; Thu, 12 Nov 1998 23:41:53 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.8.5) id AAA01122; Fri, 13 Nov 1998 00:17:48 GMT Message-ID: <19981113001748.14820@breizh.prism.uvsq.fr> Date: Fri, 13 Nov 1998 00:17:48 +0000 From: Nicolas Souchu To: Ron Klinkien Cc: freebsd-hackers@FreeBSD.ORG, Marc Bouget Subject: Re: i2c projects References: <19981109211837.A4702@zappa.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <19981109211837.A4702@zappa.demon.nl>; from Ron Klinkien on Mon, Nov 09, 1998 at 09:18:37PM +0100 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 09, 1998 at 09:18:37PM +0100, Ron Klinkien wrote: > > > >Does anyone have any pointers/src code on how to use >the i2c drivers with FreeBSD? > >I want to build a weather station / home automation project using a FreeBSD running pc, >and the i2c bus on my video capture card. Cool. FreeBSD is the good choice. > >The i2c driver src and man pages don't give me enough info.. > >Furthermore I have compiled a kernel with i2c support >but there are no ii* devices in /dev, and not in MAKEDEV too. Yes, this is lacking. Waiting for a MAKEDEV update, try: mknod iic0 c 105 0 mknod smb0 c 106 0 and so on, replacing 0 by 1,2... > >Which major/minor numbers to use etc...? You would have found them in the related drivers: /sys/dev/iicbus/iic.c /sys/dev/smbus/smb.c > >Regards, >Ron. > iicbus is a powerfull framework that should bring you all what you need with only few indications about how to use it. First of all, which video card do you have? A bt848 based card? Perfect, the drivers are ready to work. As described in the bktr man page, you'll need in addition to 'device bktr0' in your /sys/i386/conf/MACHINE file: controller iicbus0 controller iicbb0 device iic0 at iicbus? controller smbus0 device smb0 at smbus? -- Now, you want to write user/kernel code? If you need kernel code which is uncertain, /sys/dev/iicbus/iic.c will be a good start. Read, copy and modify it as needed. For userland code, you'll have to add your devices in /sys/dev/iicbus/iic.c: { "iic", IICBUS_DEVICE_CLASS, "MY DEVICE IDENTIFIER", MY_DEVICE_ADDRESS}, like this (for each device on you I2C bus): /* * list of known devices */ struct iicbus_device iicbus_children[] = { { "iicsmb", IICBUS_DRIVER_CLASS, "I2C to SMB bridge" }, { "iic", IICBUS_DEVICE_CLASS, "MY DEVICE IDENTIFIER", MY_DEVICE_ADDRESS}, { "iic", IICBUS_DEVICE_CLASS, "PCF8574 I2C to 8 bits parallel i/o", 64}, { "iic", IICBUS_DEVICE_CLASS, "PCF8584 as slave", PCF_MASTER_ADDRESS }, { "ic", IICBUS_DEVICE_CLASS, "network interface", PCF_MASTER_ADDRESS }, #if 0 { "iic", IICBUS_DRIVER_CLASS, "General Call", I2C_GENERAL_CALL }, #endif { NULL, 0 } }; -- Then see /usr/include/machine/iic.h to have the ioctls on /dev/iic? They are implemented by /sys/dev/iicbus/iic.c Nicolas. -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 14:46:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04352 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 14:46:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04347 for ; Thu, 12 Nov 1998 14:46:56 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA01308; Thu, 12 Nov 1998 14:44:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811122244.OAA01308@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nicolas Souchu cc: Ron Klinkien , freebsd-hackers@FreeBSD.ORG, Marc Bouget Subject: Re: i2c projects In-reply-to: Your message of "Fri, 13 Nov 1998 00:17:48 GMT." <19981113001748.14820@breizh.prism.uvsq.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Nov 1998 14:44:54 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Now, you want to write user/kernel code? If you need kernel code which is > uncertain, /sys/dev/iicbus/iic.c will be a good start. Read, copy and > modify it as needed. > > For userland code, you'll have to add your devices in /sys/dev/iicbus/iic.c: > > { "iic", IICBUS_DEVICE_CLASS, "MY DEVICE IDENTIFIER", MY_DEVICE_ADDRESS}, > > like this (for each device on you I2C bus): > > /* > * list of known devices > */ > struct iicbus_device iicbus_children[] = { > { "iicsmb", IICBUS_DRIVER_CLASS, "I2C to SMB bridge" }, > { "iic", IICBUS_DEVICE_CLASS, "MY DEVICE IDENTIFIER", MY_DEVICE_ADDRESS}, > { "iic", IICBUS_DEVICE_CLASS, "PCF8574 I2C to 8 bits parallel i/o", 64}, > { "iic", IICBUS_DEVICE_CLASS, "PCF8584 as slave", PCF_MASTER_ADDRESS }, > { "ic", IICBUS_DEVICE_CLASS, "network interface", PCF_MASTER_ADDRESS }, > #if 0 > { "iic", IICBUS_DRIVER_CLASS, "General Call", I2C_GENERAL_CALL }, > #endif > { NULL, 0 } > }; Hmm. Is this just for devices in the kernel? You probably want to make this extensible, eg. with a (de)registration function so that other consumers can register stuff they know about. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 15:08:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07014 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 15:08:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06984 for ; Thu, 12 Nov 1998 15:07:54 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA06975; Thu, 12 Nov 1998 15:00:17 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdFI6948; Thu Nov 12 23:00:08 1998 Date: Thu, 12 Nov 1998 14:59:29 -0800 (PST) From: Julian Elischer To: zhihuizhang cc: hackers Subject: Re: More questions on DEVFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Nov 1998, zhihuizhang wrote: > > I have a couple of questions on DEVFS which is hard to figure out from the > source code: > > (1) As I understand it, special files can be created only by superuser via > mknod and file systems can only be mounted by superuser. I do not see any > reason why the superuser will mount the device file system multiple times > and possibly at different mount points. Eventually if devfs were common the ability to have devices on other filesystems would be removed. Requiring the administrator to keep in sync with dynamically assigned device major.minor numbers is impossible. (wellll... hard) In that case no-one (not even root) could make device nodes because they wouldn;t know what major number to use.. only the kernel knows that. Having multiple copies of /dev is common in chroot environments. > > (2) Both the block and character switch table have a major number at its > end (d_maj) which is often set to be -1 (see mem_cdevsw[] in file > i386/mem.c for an example). This makes devfs_add_devswf() return without > adding a device entry. Is this the way that is used to circuit the DEVFS > code on purpose? in -current there is no longer a bdevsw ond a cdevsw struct. there is only a single 'devsw' struct.. d_maj is so the driver can see what major it was assigned in th ecase where it may have been dynamically assigned.. It was also so that you could find hte mojor of the char device coresponding with a block device as there was a pointer from the blksw enty to the associated cdevsw entry, and using that you could look at d_maj to find the major of the other device. Now in -current there is on ly one struct that is pointed to by both arrays so there is a d_maj and a d_bmaj.. Eventually the whole bdevsw array will go away. block devices are not terribly useful any more. devfs_add_devsw assumes that the devsw entry has first been put into the devsw array, (pointed to rather). the routines that do this (in kern_conf.c) replace the -1 with the real number. Each driver has an init routine that is called either by the SYSINIT() entry at EARLY boot time, or when it is loaded (if it is an lkm/klm/mlk/etc.) It is the responsibility of this init routine to place the devsw entry into the table. THis usually happens well before the prob/attach routines which add the devfs entries for those specific devices they find. devsw entries are PER DRIVER devfs entries are PER FOUND DEVICE. They have different scopes. julian > > Thanks for your help. > > -------------------------------------------------- > | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | > | Dept. of Computer Science, SUNY at Binghamton | > -------------------------------------------------- > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 15:23:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09491 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 15:23:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uucp.intac.com (uucp.intac.com [198.6.114.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09484 for ; Thu, 12 Nov 1998 15:23:40 -0800 (PST) (envelope-from oortiz@LCSI.COM) From: oortiz@LCSI.COM Received: (uucp@localhost) by uucp.intac.com (8.9.1/8.9.1 dman) with UUCP id RAA10657; Thu, 12 Nov 1998 17:52:54 -0500 (EST) Received: from Connect2 Message Router by lcsi.LCSI.COM via Connect2-UUCP v1.00.34; Thu, 12 Nov 98 17:45:34 -0500 Message-Id: Date: Thu, 12 Nov 98 17:39:14 -0500 Organization: LCS Industries To: Archie Cobbs Cc: freebsd-hackers@FreeBSD.ORG Subject: Re[2]: IP Tunneling Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7BIT X-Mailer: Connect2-UUCP v1.00.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm kinda new to this. Didn't think there was different kinds. I just thought it was a matter of compiling it into the kernel and setting up some routes or something to that effect. Like I said, I'm new to this. I have the FreeBSD on a T1, and the Linux on a PPP (with static IP) and I would like to take 5 IP's that is on the Class C that the FreeBSD is on and tunnel them to the Linux box, so the Linux box can use the 5 IP's. I hope that makes sense. Thanks for the help! ______________________________ Reply Separator _________________________________ Subject: Re: IP Tunneling Author: archie@whistle.com (Archie Cobbs) at LCS-MHSLINK Date: 11/12/98 2:29 PM oortiz@LCSI.COM writes: > > I hope this is the right forum for this, if not, then I apologize. > Can any one give me the steps in setting up IP Tunneling in FreeBSD > 2.2.7. I have 5 IP's that I would like to tunnel from a FreeBSD box to > a Linux box, but I can't figure out the steps on the FreeBSD box. > Would anyone know or tell me where I can get documentation on this? What *kind* of tunnelling? Ie, do you know what software is available on Linux? On FreeBSD you can do SKIP, for example.. and there are some other possibilities floating out there as well.. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 15:29:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10376 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 15:29:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wave.campus.luth.se (wave.campus.luth.se [130.240.193.79]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10369 for ; Thu, 12 Nov 1998 15:29:44 -0800 (PST) (envelope-from pb@wave.campus.luth.se) Received: (from pb@localhost) by wave.campus.luth.se (8.8.4/8.8.4) id AAA05268 for freebsd-hackers@freebsd.org; Fri, 13 Nov 1998 00:32:21 GMT From: PB Message-Id: <199811130032.AAA05268@wave.campus.luth.se> Subject: I2C device interfacing. To: freebsd-hackers@FreeBSD.ORG Date: Fri, 13 Nov 1998 00:32:21 +0000 () X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just want annonce for the people involved in "philips i2c" interface project. I have built a application for a card named "TurboText" essentialy a ISA <-> i2c raw interface + tuner, textv, audiocontrol. So I know how to write these things. Maybe I could help ..? /Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 15:43:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12452 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 15:43:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12415 for ; Thu, 12 Nov 1998 15:43:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01630; Thu, 12 Nov 1998 15:41:24 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811122341.PAA01630@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: PB cc: freebsd-hackers@FreeBSD.ORG Subject: Re: I2C device interfacing. In-reply-to: Your message of "Fri, 13 Nov 1998 00:32:21 GMT." <199811130032.AAA05268@wave.campus.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Nov 1998 15:41:24 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I just want annonce for the people involved in "philips i2c" interface > project. I have built a application for a card named "TurboText" essentialy > a ISA <-> i2c raw interface + tuner, textv, audiocontrol. So I know how to > write these things. Maybe I could help ..? I'd say "go for it". 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 16:18:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19155 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 16:18:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pacman.redwoodsoft.com (redwoodsoft.com [207.181.199.182]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA19146 for ; Thu, 12 Nov 1998 16:18:01 -0800 (PST) (envelope-from dnelson@pacman.redwoodsoft.com) Received: (qmail 5238 invoked by uid 1000); 13 Nov 1998 00:17:41 -0000 Date: Thu, 12 Nov 1998 16:17:41 -0800 (PST) From: Dru Nelson To: freebsd-hackers@FreeBSD.ORG Subject: write syscall times for sockets Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1272362359-910916261=:4572" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1272362359-910916261=:4572 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, I wrote a simple C program to guage how many usec's system calls take or write calls take for various write lengths. I setup a socket to the discard socket on another machine. I did various writes. The times are in the attachment. The first 4 writes are 0,0,8,?. After that all the writes are in groups of 4 with a sleep(2) in between. Ahh.. :-) I'll just include the code. Basically, the first system call would take longer for some reason. Then each write would be pretty consistent. What I was looking for was that characteristic of writing to a socket with buffer available. The call should be pretty quick, and the kernel and interupt code should take over from there. If the write is small enough, the transaction could be considered done from the code's point of view. Another way of saying this is: I hand over the write, if it is smaller than the buffer, then I can use the user space to handle some other socket. Otherwise, it would block. Does this look right or what are people's experience with this??? This is pretty much for fun... a limited test case. However, I think the information would be interesting. I'm not on this list, so if you could cc: me when you reply, that would be great. Dru Nelson Redwood City, California --0-1272362359-910916261=:4572 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="testwrite.c" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: DQojaW5jbHVkZSA8c3lzL3RpbWUuaD4NCiNpbmNsdWRlIDxzdGRpby5oPg0K DQojaW5jbHVkZSA8c3lzL3R5cGVzLmg+DQojaW5jbHVkZSA8c3lzL3NvY2tl dC5oPg0KI2luY2x1ZGUgPG5ldGluZXQvaW4uaD4NCiNpbmNsdWRlIDxhcnBh L2luZXQuaD4NCg0KDQojaW5jbHVkZSA8c3RyaW5nLmg+DQojaW5jbHVkZSA8 dW5pc3RkLmg+DQoNCmNoYXIgYnVmZmVyWzgxOTIqOCo4XTsNCg0Kdm9pZCBt ZWFzdXJlZFdyaXRlKGludCBzb2NrLCBpbnQgYnl0ZXMpDQp7DQogICBzdHJ1 Y3QgdGltZXZhbCB0MTsgICANCiAgIHN0cnVjdCB0aW1ldmFsIHQyOyAgIA0K ICAgdW5zaWduZWQgaW50IHcxOw0KICAgdW5zaWduZWQgaW50IGJpYXM7DQog ICB1bnNpZ25lZCBpbnQgZGlmZjsNCiAgIHVuc2lnbmVkIGludCBhZGo7DQoN CglnZXR0aW1lb2ZkYXkoJnQxLCBOVUxMKTsNCglnZXR0aW1lb2ZkYXkoJnQy LCBOVUxMKTsNCiAgICAgICAgYmlhcyA9IHQyLnR2X3VzZWMgLSB0MS50dl91 c2VjOw0KDQoJZ2V0dGltZW9mZGF5KCZ0MSwgTlVMTCk7DQoJdzEgPSB3cml0 ZShzb2NrLCBidWZmZXIsIGJ5dGVzKTsNCglnZXR0aW1lb2ZkYXkoJnQyLCBO VUxMKTsNCg0KICAgZGlmZiA9IHQyLnR2X3VzZWMgLSB0MS50dl91c2VjOw0K ICAgYWRqICA9IGRpZmYgLSBiaWFzOw0KICAgcHJpbnRmKCJUaW1lMSA9ICVs dS4lbHVcbiIsIHQxLnR2X3NlYywgdDEudHZfdXNlYyk7DQogICBwcmludGYo IlRpbWUyID0gJWx1LiVsdVxuIiwgdDIudHZfc2VjLCB0Mi50dl91c2VjKTsN CiAgIHByaW50ZigiRGlmZmVyZW5jZSA9ICV1IHVzZWMgIiwgZGlmZik7IA0K ICAgcHJpbnRmKCJBZGp1c3RlZCA9ICV1IHVzZWMgICIsIGFkaik7DQogICBw cmludGYoIkJ5dGVzIFdyaXR0ZW4gPSAldSAgQWN0dWFsID0gJXVcbiIsIGJ5 dGVzLCB3MSk7DQoNCg0KfQ0KDQppbnQgbWFpbigpDQp7DQoNCiAgIHN0cnVj dCBzb2NrYWRkcl9pbiBzZXJ2ZXI7DQoNCiAgIGludCBzb2NrZmQ7DQogICBp bnQgZXJyb3I7DQoNCg0KLyogU2V0dXAgYSBzb2NrZXQgKi8NCiAgIHNvY2tm ZCA9IHNvY2tldChQRl9JTkVULFNPQ0tfU1RSRUFNLCAwKTsNCiANCi8qIFRl c3QgYSB3cml0ZSB0byB0aGUgcG9ydCB3aXRoIHZhcmlvdXMgd3JpdGUgc2l6 ZXMgKi8gDQogICBiemVybygmc2VydmVyLCBzaXplb2Yoc2VydmVyKSk7DQog ICBzZXJ2ZXIuc2luX2ZhbWlseSA9IEFGX0lORVQ7DQogICBzZXJ2ZXIuc2lu X3BvcnQgICA9IGh0b25zKDkpOw0KICAgc2VydmVyLnNpbl9hZGRyLnNfYWRk ciAgICAgID0gaW5ldF9hZGRyKCIxMC4xLjEuMTUxIik7DQoNCiAgIGVycm9y ID0gY29ubmVjdChzb2NrZmQsIChzdHJ1Y3Qgc29ja2FkZHIgKikmc2VydmVy LCBzaXplb2Yoc2VydmVyKSk7DQogICBpZiAoZXJyb3IgIT0gMCkgew0KCSAg IHByaW50ZigiQ2FuJ3QgY29ubmVjdCB0byBwb3J0XG4iKTsNCgkgICBleGl0 ICgxKTsNCiAgIH0NCiANCg0KICAgbWVhc3VyZWRXcml0ZShzb2NrZmQsIDAp Ow0KICAgbWVhc3VyZWRXcml0ZShzb2NrZmQsIDApOw0KICAgbWVhc3VyZWRX cml0ZShzb2NrZmQsIDgpOw0KICAgbWVhc3VyZWRXcml0ZShzb2NrZmQsIDIw NDgpOw0KCXNsZWVwKDIpOw0KDQogICBtZWFzdXJlZFdyaXRlKHNvY2tmZCwg MzIpOw0KICAgbWVhc3VyZWRXcml0ZShzb2NrZmQsIDMyKTsNCiAgIG1lYXN1 cmVkV3JpdGUoc29ja2ZkLCAzMik7DQogICBtZWFzdXJlZFdyaXRlKHNvY2tm ZCwgMzIpOw0KCXNsZWVwKDIpOw0KDQogICBtZWFzdXJlZFdyaXRlKHNvY2tm ZCwgMTAyNCk7DQogICBtZWFzdXJlZFdyaXRlKHNvY2tmZCwgMTAyNCk7DQog ICBtZWFzdXJlZFdyaXRlKHNvY2tmZCwgMTAyNCk7DQogICBtZWFzdXJlZFdy aXRlKHNvY2tmZCwgMTAyNCk7DQoJc2xlZXAoMik7DQoNCiAgIG1lYXN1cmVk V3JpdGUoc29ja2ZkLCAyMDQ4KTsNCiAgIG1lYXN1cmVkV3JpdGUoc29ja2Zk LCAyMDQ4KTsNCiAgIG1lYXN1cmVkV3JpdGUoc29ja2ZkLCAyMDQ4KTsNCiAg IG1lYXN1cmVkV3JpdGUoc29ja2ZkLCAyMDQ4KTsNCglzbGVlcCgyKTsNCg0K ICAgbWVhc3VyZWRXcml0ZShzb2NrZmQsIDQwOTYpOw0KICAgbWVhc3VyZWRX cml0ZShzb2NrZmQsIDQwOTYpOw0KICAgbWVhc3VyZWRXcml0ZShzb2NrZmQs IDQwOTYpOw0KICAgbWVhc3VyZWRXcml0ZShzb2NrZmQsIDQwOTYpOw0KCXNs ZWVwKDIpOw0KDQogICBtZWFzdXJlZFdyaXRlKHNvY2tmZCwgODE5Mik7DQog ICBtZWFzdXJlZFdyaXRlKHNvY2tmZCwgODE5Mik7DQogICBtZWFzdXJlZFdy aXRlKHNvY2tmZCwgODE5Mik7DQogICBtZWFzdXJlZFdyaXRlKHNvY2tmZCwg ODE5Mik7DQoJc2xlZXAoMik7DQoNCiAgIG1lYXN1cmVkV3JpdGUoc29ja2Zk LCAxNjM4NCk7DQogICBtZWFzdXJlZFdyaXRlKHNvY2tmZCwgMTYzODQpOw0K ICAgbWVhc3VyZWRXcml0ZShzb2NrZmQsIDE2Mzg0KTsNCiAgIG1lYXN1cmVk V3JpdGUoc29ja2ZkLCAxNjM4NCk7DQoJc2xlZXAoMik7DQoNCiAgIG1lYXN1 cmVkV3JpdGUoc29ja2ZkLCAzMjc2OCk7DQogICBtZWFzdXJlZFdyaXRlKHNv Y2tmZCwgMzI3NjgpOw0KICAgbWVhc3VyZWRXcml0ZShzb2NrZmQsIDMyNzY4 KTsNCiAgIG1lYXN1cmVkV3JpdGUoc29ja2ZkLCAzMjc2OCk7DQoJc2xlZXAo Mik7DQoNCiAgIG1lYXN1cmVkV3JpdGUoc29ja2ZkLCAoMzI3NjgqNCkpOw0K ICAgbWVhc3VyZWRXcml0ZShzb2NrZmQsICgzMjc2OCo0KSk7DQogICBtZWFz dXJlZFdyaXRlKHNvY2tmZCwgKDMyNzY4KjQpKTsNCiAgIG1lYXN1cmVkV3Jp dGUoc29ja2ZkLCAoMzI3NjgqNCkpOw0KCXNsZWVwKDIpOw0KDQoNCiAgIHJl dHVybiAwOw0KfQ0K --0-1272362359-910916261=:4572 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="socketwrite.output" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: VGltZTEgPSA5MTA5MTM1NjAuMzM2MjMyDQpUaW1lMiA9IDkxMDkxMzU2MC4z MzYyNjINCkRpZmZlcmVuY2UgPSAzMCB1c2VjIEFkanVzdGVkID0gMjYgdXNl YyAgQnl0ZXMgV3JpdHRlbiA9IDAgIEFjdHVhbCA9IDANClRpbWUxID0gOTEw OTEzNTYwLjMzNjU4NA0KVGltZTIgPSA5MTA5MTM1NjAuMzM2NTk4DQpEaWZm ZXJlbmNlID0gMTQgdXNlYyBBZGp1c3RlZCA9IDExIHVzZWMgIEJ5dGVzIFdy aXR0ZW4gPSAwICBBY3R1YWwgPSAwDQpUaW1lMSA9IDkxMDkxMzU2MC4zMzY2 MjgNClRpbWUyID0gOTEwOTEzNTYwLjMzNjY1MQ0KRGlmZmVyZW5jZSA9IDIz IHVzZWMgQWRqdXN0ZWQgPSAyMCB1c2VjICBCeXRlcyBXcml0dGVuID0gOCAg QWN0dWFsID0gOA0KVGltZTEgPSA5MTA5MTM1NjAuMzM2NjkxDQpUaW1lMiA9 IDkxMDkxMzU2MC4zMzY3MzUNCkRpZmZlcmVuY2UgPSA0NCB1c2VjIEFkanVz dGVkID0gNDEgdXNlYyAgQnl0ZXMgV3JpdHRlbiA9IDIwNDggIEFjdHVhbCA9 IDIwNDgNClRpbWUxID0gOTEwOTEzNTYyLjM0NDkwMQ0KVGltZTIgPSA5MTA5 MTM1NjIuMzQ0OTMwDQpEaWZmZXJlbmNlID0gMjkgdXNlYyBBZGp1c3RlZCA9 IDI3IHVzZWMgIEJ5dGVzIFdyaXR0ZW4gPSAzMiAgQWN0dWFsID0gMzINClRp bWUxID0gOTEwOTEzNTYyLjM0NDk3NA0KVGltZTIgPSA5MTA5MTM1NjIuMzQ0 OTg0DQpEaWZmZXJlbmNlID0gMTAgdXNlYyBBZGp1c3RlZCA9IDcgdXNlYyAg Qnl0ZXMgV3JpdHRlbiA9IDMyICBBY3R1YWwgPSAzMg0KVGltZTEgPSA5MTA5 MTM1NjIuMzQ1MDE0DQpUaW1lMiA9IDkxMDkxMzU2Mi4zNDUwMjENCkRpZmZl cmVuY2UgPSA3IHVzZWMgQWRqdXN0ZWQgPSA1IHVzZWMgIEJ5dGVzIFdyaXR0 ZW4gPSAzMiAgQWN0dWFsID0gMzINClRpbWUxID0gOTEwOTEzNTYyLjM0NTA1 MQ0KVGltZTIgPSA5MTA5MTM1NjIuMzQ1MDU4DQpEaWZmZXJlbmNlID0gNyB1 c2VjIEFkanVzdGVkID0gNCB1c2VjICBCeXRlcyBXcml0dGVuID0gMzIgIEFj dHVhbCA9IDMyDQpUaW1lMSA9IDkxMDkxMzU2NC4zNTQ1OTkNClRpbWUyID0g OTEwOTEzNTY0LjM1NDYzNg0KRGlmZmVyZW5jZSA9IDM3IHVzZWMgQWRqdXN0 ZWQgPSAzNCB1c2VjICBCeXRlcyBXcml0dGVuID0gMTAyNCAgQWN0dWFsID0g MTAyNA0KVGltZTEgPSA5MTA5MTM1NjQuMzU0NjgxDQpUaW1lMiA9IDkxMDkx MzU2NC4zNTQ2OTYNCkRpZmZlcmVuY2UgPSAxNSB1c2VjIEFkanVzdGVkID0g MTIgdXNlYyAgQnl0ZXMgV3JpdHRlbiA9IDEwMjQgIEFjdHVhbCA9IDEwMjQN ClRpbWUxID0gOTEwOTEzNTY0LjM1NDcyNw0KVGltZTIgPSA5MTA5MTM1NjQu MzU0NzQwDQpEaWZmZXJlbmNlID0gMTMgdXNlYyBBZGp1c3RlZCA9IDEwIHVz ZWMgIEJ5dGVzIFdyaXR0ZW4gPSAxMDI0ICBBY3R1YWwgPSAxMDI0DQpUaW1l MSA9IDkxMDkxMzU2NC4zNTQ3NzENClRpbWUyID0gOTEwOTEzNTY0LjM1NDc4 Mw0KRGlmZmVyZW5jZSA9IDEyIHVzZWMgQWRqdXN0ZWQgPSAxMCB1c2VjICBC eXRlcyBXcml0dGVuID0gMTAyNCAgQWN0dWFsID0gMTAyNA0KVGltZTEgPSA5 MTA5MTM1NjYuMzY0MzE2DQpUaW1lMiA9IDkxMDkxMzU2Ni4zNjQzNjENCkRp ZmZlcmVuY2UgPSA0NSB1c2VjIEFkanVzdGVkID0gNDIgdXNlYyAgQnl0ZXMg V3JpdHRlbiA9IDIwNDggIEFjdHVhbCA9IDIwNDgNClRpbWUxID0gOTEwOTEz NTY2LjM2NDQwOA0KVGltZTIgPSA5MTA5MTM1NjYuMzY0NDI5DQpEaWZmZXJl bmNlID0gMjEgdXNlYyBBZGp1c3RlZCA9IDE5IHVzZWMgIEJ5dGVzIFdyaXR0 ZW4gPSAyMDQ4ICBBY3R1YWwgPSAyMDQ4DQpUaW1lMSA9IDkxMDkxMzU2Ni4z NjQ0NjANClRpbWUyID0gOTEwOTEzNTY2LjM2NDQ3Nw0KRGlmZmVyZW5jZSA9 IDE3IHVzZWMgQWRqdXN0ZWQgPSAxNSB1c2VjICBCeXRlcyBXcml0dGVuID0g MjA0OCAgQWN0dWFsID0gMjA0OA0KVGltZTEgPSA5MTA5MTM1NjYuMzY0NTA4 DQpUaW1lMiA9IDkxMDkxMzU2Ni4zNjQ1MjUNCkRpZmZlcmVuY2UgPSAxNyB1 c2VjIEFkanVzdGVkID0gMTUgdXNlYyAgQnl0ZXMgV3JpdHRlbiA9IDIwNDgg IEFjdHVhbCA9IDIwNDgNClRpbWUxID0gOTEwOTEzNTY4LjM3NDA0Ng0KVGlt ZTIgPSA5MTA5MTM1NjguMzc0MTU2DQpEaWZmZXJlbmNlID0gMTEwIHVzZWMg QWRqdXN0ZWQgPSAxMDcgdXNlYyAgQnl0ZXMgV3JpdHRlbiA9IDQwOTYgIEFj dHVhbCA9IDQwOTYNClRpbWUxID0gOTEwOTEzNTY4LjM3NDE5NA0KVGltZTIg PSA5MTA5MTM1NjguMzc0MjIwDQpEaWZmZXJlbmNlID0gMjYgdXNlYyBBZGp1 c3RlZCA9IDIzIHVzZWMgIEJ5dGVzIFdyaXR0ZW4gPSA0MDk2ICBBY3R1YWwg PSA0MDk2DQpUaW1lMSA9IDkxMDkxMzU2OC4zNzQyNTINClRpbWUyID0gOTEw OTEzNTY4LjM3NDI4Mw0KRGlmZmVyZW5jZSA9IDMxIHVzZWMgQWRqdXN0ZWQg PSAyOCB1c2VjICBCeXRlcyBXcml0dGVuID0gNDA5NiAgQWN0dWFsID0gNDA5 Ng0KVGltZTEgPSA5MTA5MTM1NjguMzc0MzE0DQpUaW1lMiA9IDkxMDkxMzU2 OC4zNzQzNDkNCkRpZmZlcmVuY2UgPSAzNSB1c2VjIEFkanVzdGVkID0gMzIg dXNlYyAgQnl0ZXMgV3JpdHRlbiA9IDQwOTYgIEFjdHVhbCA9IDQwOTYNClRp bWUxID0gOTEwOTEzNTcwLjM4Mzc1MQ0KVGltZTIgPSA5MTA5MTM1NzAuMzgz OTA4DQpEaWZmZXJlbmNlID0gMTU3IHVzZWMgQWRqdXN0ZWQgPSAxNTQgdXNl YyAgQnl0ZXMgV3JpdHRlbiA9IDgxOTIgIEFjdHVhbCA9IDgxOTINClRpbWUx ID0gOTEwOTEzNTcwLjM4Mzk0Nw0KVGltZTIgPSA5MTA5MTM1NzAuMzg0MDA1 DQpEaWZmZXJlbmNlID0gNTggdXNlYyBBZGp1c3RlZCA9IDU2IHVzZWMgIEJ5 dGVzIFdyaXR0ZW4gPSA4MTkyICBBY3R1YWwgPSA4MTkyDQpUaW1lMSA9IDkx MDkxMzU3MC4zODQwMzgNClRpbWUyID0gOTEwOTEzNTcwLjUyOTU1OQ0KRGlm ZmVyZW5jZSA9IDE0NTUyMSB1c2VjIEFkanVzdGVkID0gMTQ1NTE4IHVzZWMg IEJ5dGVzIFdyaXR0ZW4gPSA4MTkyICBBY3R1YWwgPSA4MTkyDQpUaW1lMSA9 IDkxMDkxMzU3MC41Mjk1OTcNClRpbWUyID0gOTEwOTEzNTcwLjUzMTI5Nw0K RGlmZmVyZW5jZSA9IDE3MDAgdXNlYyBBZGp1c3RlZCA9IDE2OTggdXNlYyAg Qnl0ZXMgV3JpdHRlbiA9IDgxOTIgIEFjdHVhbCA9IDgxOTINClRpbWUxID0g OTEwOTEzNTcyLjUzMzM3OQ0KVGltZTIgPSA5MTA5MTM1NzIuNTMzNjIzDQpE aWZmZXJlbmNlID0gMjQ0IHVzZWMgQWRqdXN0ZWQgPSAyNDEgdXNlYyAgQnl0 ZXMgV3JpdHRlbiA9IDE2Mzg0ICBBY3R1YWwgPSAxNjM4NA0KVGltZTEgPSA5 MTA5MTM1NzIuNTMzNjYyDQpUaW1lMiA9IDkxMDkxMzU3Mi42ODE2NjYNCkRp ZmZlcmVuY2UgPSAxNDgwMDQgdXNlYyBBZGp1c3RlZCA9IDE0ODAwMiB1c2Vj ICBCeXRlcyBXcml0dGVuID0gMTYzODQgIEFjdHVhbCA9IDE2Mzg0DQpUaW1l MSA9IDkxMDkxMzU3Mi42ODE3MTUNClRpbWUyID0gOTEwOTEzNTcyLjY4MzU1 OQ0KRGlmZmVyZW5jZSA9IDE4NDQgdXNlYyBBZGp1c3RlZCA9IDE4NDIgdXNl YyAgQnl0ZXMgV3JpdHRlbiA9IDE2Mzg0ICBBY3R1YWwgPSAxNjM4NA0KVGlt ZTEgPSA5MTA5MTM1NzIuNjgzNjA0DQpUaW1lMiA9IDkxMDkxMzU3Mi42ODUx MTMNCkRpZmZlcmVuY2UgPSAxNTA5IHVzZWMgQWRqdXN0ZWQgPSAxNTA3IHVz ZWMgIEJ5dGVzIFdyaXR0ZW4gPSAxNjM4NCAgQWN0dWFsID0gMTYzODQNClRp bWUxID0gOTEwOTEzNTc0LjY5MzA1Mg0KVGltZTIgPSA5MTA5MTM1NzQuODQy MDAwDQpEaWZmZXJlbmNlID0gMTQ4OTQ4IHVzZWMgQWRqdXN0ZWQgPSAxNDg5 NDUgdXNlYyAgQnl0ZXMgV3JpdHRlbiA9IDMyNzY4ICBBY3R1YWwgPSAzMjc2 OA0KVGltZTEgPSA5MTA5MTM1NzQuODQyMDUyDQpUaW1lMiA9IDkxMDkxMzU3 NC44NDU1NjMNCkRpZmZlcmVuY2UgPSAzNTExIHVzZWMgQWRqdXN0ZWQgPSAz NTA4IHVzZWMgIEJ5dGVzIFdyaXR0ZW4gPSAzMjc2OCAgQWN0dWFsID0gMzI3 NjgNClRpbWUxID0gOTEwOTEzNTc0Ljg0NTYwOA0KVGltZTIgPSA5MTA5MTM1 NzQuODQ5MzE2DQpEaWZmZXJlbmNlID0gMzcwOCB1c2VjIEFkanVzdGVkID0g MzcwNiB1c2VjICBCeXRlcyBXcml0dGVuID0gMzI3NjggIEFjdHVhbCA9IDMy NzY4DQpUaW1lMSA9IDkxMDkxMzU3NC44NDkzNjINClRpbWUyID0gOTEwOTEz NTc0Ljg1MjgxNg0KRGlmZmVyZW5jZSA9IDM0NTQgdXNlYyBBZGp1c3RlZCA9 IDM0NTEgdXNlYyAgQnl0ZXMgV3JpdHRlbiA9IDMyNzY4ICBBY3R1YWwgPSAz Mjc2OA0KVGltZTEgPSA5MTA5MTM1NzYuODUyNzY3DQpUaW1lMiA9IDkxMDkx MzU3Ny4xMzYzMg0KRGlmZmVyZW5jZSA9IDQyOTQxMjgxNjEgdXNlYyBBZGp1 c3RlZCA9IDQyOTQxMjgxNTkgdXNlYyAgQnl0ZXMgV3JpdHRlbiA9IDEzMTA3 MiAgQWN0dWFsID0gMTMxMDcyDQpUaW1lMSA9IDkxMDkxMzU3Ny4xMzY5NQ0K VGltZTIgPSA5MTA5MTM1NzcuMjgwODUNCkRpZmZlcmVuY2UgPSAxNDM5MCB1 c2VjIEFkanVzdGVkID0gMTQzODggdXNlYyAgQnl0ZXMgV3JpdHRlbiA9IDEz MTA3MiAgQWN0dWFsID0gMTMxMDcyDQpUaW1lMSA9IDkxMDkxMzU3Ny4yODEz NQ0KVGltZTIgPSA5MTA5MTM1NzcuNDIxNjYNCkRpZmZlcmVuY2UgPSAxNDAz MSB1c2VjIEFkanVzdGVkID0gMTQwMjkgdXNlYyAgQnl0ZXMgV3JpdHRlbiA9 IDEzMTA3MiAgQWN0dWFsID0gMTMxMDcyDQpUaW1lMSA9IDkxMDkxMzU3Ny40 MjIxNA0KVGltZTIgPSA5MTA5MTM1NzcuNTY3MzUNCkRpZmZlcmVuY2UgPSAx NDUyMSB1c2VjIEFkanVzdGVkID0gMTQ1MTkgdXNlYyAgQnl0ZXMgV3JpdHRl biA9IDEzMTA3MiAgQWN0dWFsID0gMTMxMDcyDQo= --0-1272362359-910916261=:4572-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 16:42:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22120 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 16:42:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from papillon.lemis.com (papillon.lemis.com [192.109.197.159]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22100 for ; Thu, 12 Nov 1998 16:42:20 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by papillon.lemis.com (8.9.1/8.6.12) with ESMTP id SAA02274; Thu, 12 Nov 1998 18:22:12 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id SAA28508; Thu, 12 Nov 1998 18:22:38 +1030 (CST) Message-ID: <19981112182238.J463@freebie.lemis.com> Date: Thu, 12 Nov 1998 18:22:38 +1030 From: Greg Lehey To: "Justin T. Gibbs" Cc: hackers@FreeBSD.ORG Subject: Re: SCSI vs. DMA33.. References: <98Nov11.134648jst.21907@ns.isi.co.jp> <199811111538.IAA00103@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811111538.IAA00103@narnia.plutotech.com>; from Justin T. Gibbs on Wed, Nov 11, 1998 at 08:38:43AM -0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 11 November 1998 at 8:38:43 -0700, Justin T. Gibbs wrote: > In article <19981111194213.H20849@freebie.lemis.com> you wrote: >>> I must say that the newer UDMA IDE drives has come a long way >>> lately, they perform at least as good as their SCSI counterparts. >>> The only thing that they cannot do is overlapping commands, but >>> given EIDE's much smaller cmd overhead, I'm not sure this has >>> any significance at all in practice. >> >> This last point would appear to be borne out in my measurements >> earlier today. > > You had all of 1 command going to each disk. That doesn't give > you any per-device overlap. Sure. I was referring to the command overhead, not the effect of overlapped commands. > If you really want to see the effect of overlapped commands, run a > benchmark through the filesystem that causes lots of commands to be > generated. Do it with tagged queuing and without. If your devices > support a reasonable number of transactions, the effect of disabling > tagged queuing on latency is quite dramatic. I once introduced a > bug into CAM that effectively disabled tagged queuing. For several > days I couldn't understand why my interactive performance was so > lousy during large compile runs. I think that the testaments on > this list and others about the dramatic improvement CAM has made to > the performance of high load, random seek, workloads also shows the > effectiveness of overlapped I/O. The main reason CAM performs so > well is the order of magnitude increase in the number of concurrent, > per-device, transactions the system supports. No doubt, and that's what I intended to do next. Unfortunately, I've just fallen off the net (massive phone cable damage out in the street), so I don't can't download any benchmarks. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 16:48:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23016 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 16:48:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from papillon.lemis.com (papillon.lemis.com [192.109.197.159]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23001 for ; Thu, 12 Nov 1998 16:48:41 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by papillon.lemis.com (8.9.1/8.6.12) with ESMTP id SAA02288; Thu, 12 Nov 1998 18:44:46 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id SAA16347; Thu, 12 Nov 1998 18:45:12 +1030 (CST) Message-ID: <19981112184509.K463@freebie.lemis.com> Date: Thu, 12 Nov 1998 18:45:09 +1030 From: Greg Lehey To: Bernd Walter , Mike Smith , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <199811100638.WAA00637@dingo.cdrom.com> <19981111103028.L18183@freebie.lemis.com> <19981111040654.07145@cicely.de> <19981111134546.D20374@freebie.lemis.com> <19981111085152.55040@cicely.de> <19981111183546.D20849@freebie.lemis.com> <19981111194157.06719@cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981111194157.06719@cicely.de>; from Bernd Walter on Wed, Nov 11, 1998 at 07:41:57PM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 11 November 1998 at 19:41:57 +0100, Bernd Walter wrote: > On Wed, Nov 11, 1998 at 06:35:46PM +1030, Greg Lehey wrote: >> On Wednesday, 11 November 1998 at 8:51:52 +0100, Bernd Walter wrote: >>> On Wed, Nov 11, 1998 at 01:45:46PM +1030, Greg Lehey wrote: >>>> On Wednesday, 11 November 1998 at 4:06:54 +0100, Bernd Walter wrote: >>>>> On Wed, Nov 11, 1998 at 10:30:28AM +1030, Greg Lehey wrote: >>>>>> On Monday, 9 November 1998 at 22:38:04 -0800, Mike Smith wrote: >>>>> [...] >>>>> One point is that is doesn't aggregate transactions to the lower drivers. >>>>> When using stripes of one sector it's doing no more than one sector >>>>> transactions to the HDDs so at least with the old scsi driver there's no >>>>> linear performance increase with it. That's the same with ccd. >>>> >>>> Correct, at least as far as Vinum goes. The rationale for this is >>>> that, with significant extra code, Vinum could aggregate transfers >>>> *from a single user request* in this manner. But any request that >>>> gets this far (in other words, runs for more than a complete stripe) >>>> is going to convert one user request into n disk requests. There's no >>>> good reason to do this, and the significant extra code would just chop >>>> off the tip of the iceberg. The solution is in the hands of the user: >>>> don't use small stripe sizes. I recommend a stripe of between 256 and >>>> 512 kB. >>> >>> That's good for random performance increase - but for linear access a smaler >>> stripe size is the only way to get the maximum performance of all >>> disks together. >> >> No, the kind of stripe size you're thinking about will almost always >> degrade performance. If you're accessing large quantities of data in >> a linear fashion, you'll be reading 60 kB at a time. If each of these >> reads requires accessing more than one disk, you'll kill performance. >> Try it: I have. > > With agregation? No, with less than a full stripe transferred. > Say You read the volume linear without any other activity on the > disks. If you have a stripe size of 60k and reading is at 60k > chunks each read will read 60k of only one disk - expecting all > transactions are stripe aligned. The only thing wich will increase > performance are the readahead abilities of the fs-driver and the > disks themself - at least if I havn't missed any. Right. > If You use 512byte Stripes and read 60k chunks - the current > situation is that each drive gets single sector transactions which > is often slower than a single disk. That would definitely be slower. > What I expect is that an agreagation such a 60k chunk access on the > volume is splited into only one transaction per drive - so you can > read from all the drives at the same time and get an bandwidth > increase. OK, so you want to have 4 15 kB reads, and you expect a performance improvement because of it. Let's consider the hardware: a good modern disk has a disk transfer rate of 10 MB/s and a rotational speed of 7200 rpm. Let's look at the times involved: rotational transfer time total latency 1 disk/60 kB 4.2 ms 6 ms 10.2 ms 4 disks/15 kB 7.8 ms 1.5 ms 9.3 ms Huh? Why the difference in rotational latency? If you're reading from one disk, on average you'll have a half track latency. For two, on average one is half a track off from the other, so you'll have a latency of .75 a track. With three drives, it's .875, and with four drives, it's .9375 of a track. Still, in this case (the largest possible block size, and only 4 disks), you win--barely. Let's look at a more typical case: 16 kB rotational transfer time total latency 1 disk/16 kB 4.2 ms 1.6 ms 5.8 ms 4 disks/4 kB 7.8 ms .4 ms 8.2 ms Most transfers are 16 kB or less. What really kills you is the lack of spindle synchronization between the disks. If they were synchronized, that would be fine, but that's more complicated than it looks. You'd need identical disks with identical layout (subdisks in the same place on each disk). And it's almost impossible to find spindle synchronized disks nowadays. Finally, aggregating involves a scatter/gather approach which, unless I've missed something, is not supported at a hardware level. Each request to the driver specifies one buffer for the transfer, so the scatter gather would have to be done by allocating more memory and performing the transfer there (for a read) and then copying to the correct place. I have thought about aggregating in the manner you describe, and to a certain extent I feel it's a copout not to do so. I hope you now see that it doesn't really make sense in this context. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 18:04:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02450 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 18:04:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail1.netsol.net (mail.netsol.net [38.216.109.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02445; Thu, 12 Nov 1998 18:04:58 -0800 (PST) (envelope-from tech@scsr.com) Received: from ff.scsr.com ([38.185.32.41]) by mail1.netsol.net (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-42781U2500L250S0) with ESMTP id AAA45; Thu, 12 Nov 1998 18:11:42 -0800 From: "Tech1" To: , Cc: , Subject: Detailed info on Fail-safe cluster for Freebsd/unixes Date: Fri, 13 Nov 1998 06:11:13 -0800 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-ID: <19981113021140028.AAA45@ff.scsr.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fial-Safe Cluster: 1) It's a pair of daemon, one run on mission critical primary server, the other on auxiliary server 2) If the primary server is detected down, the auxiliary will take over all off TCP/IP communications/services for the primary while doing its own regular activity assigned. Example:When prime server down, when ftp to the downed server will end you up in the aux server. 3) The program run on freebsd 2x or 3x. 4) Highly portable to all other mordern unixes like sun,hp,dec,ibm, unixware, sco etc. 5) the down time is reduced virtually to 0, instead of hours/days. 6) Once server down is detected, a log alert message is loged and a mail sent to admin 7) a historical count of the number of down or backing up is maintained in the program and expressed in the mail message. 8) Virtual load-balancing in the crititical system event. 9) Optional Beeper notification/fax notification 10) You may setup the primary server in LA, aux server in NewYork. but i didn't test this yet. The cost of this software is $350 but open for bargin. For more than 10M $ company it's another price. If anyone working as consultant for companies. You may resell this software to them. i may stick fax code in for fax notification & beeper code optionally. If you wish to get more information or place an order, please contact tech@scsr.com Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 18:17:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03732 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 18:17:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sundance.stacken.kth.se (sundance.stacken.kth.se [130.237.234.41]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03708; Thu, 12 Nov 1998 18:17:04 -0800 (PST) (envelope-from art@stacken.kth.se) Received: from pizza.stacken.kth.se (pizza.stacken.kth.se [130.237.234.73]) by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id DAA16267; Fri, 13 Nov 1998 03:16:28 +0100 (MET) Received: (from art@localhost) by pizza.stacken.kth.se (8.8.7/8.8.7) id DAA00329; Fri, 13 Nov 1998 03:17:21 +0100 (MET) To: "Tech1" Cc: , , , Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes References: <19981113021140028.AAA45@ff.scsr.com> From: Artur Grabowski Date: 13 Nov 1998 03:17:21 +0100 In-Reply-To: "Tech1"'s message of "Fri, 13 Nov 1998 06:11:13 -0800" Message-ID: Lines: 11 X-Mailer: Gnus v5.6.44/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Tech1" writes: > The cost of this software is $350 but open for bargin. For more than 10M $ > company it's another price. If anyone working as consultant for companies. > You may resell this software to them. Or you can get almost the same thing for free from http://www.eddieware.org/ With source code. (Yes, I know it still doesn't run on *BSD, but that's a matter of weeks until that code is released). //art To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 18:22:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04687 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 18:22:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04655 for ; Thu, 12 Nov 1998 18:21:57 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA26879; Fri, 13 Nov 1998 12:51:36 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA01634; Fri, 13 Nov 1998 12:51:34 +1030 (CST) Message-ID: <19981113125134.M781@freebie.lemis.com> Date: Fri, 13 Nov 1998 12:51:34 +1030 From: Greg Lehey To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <19981111103028.L18183@freebie.lemis.com> <199811120600.WAA08044@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811120600.WAA08044@dingo.cdrom.com>; from Mike Smith on Wed, Nov 11, 1998 at 10:00:40PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 11 November 1998 at 22:00:40 -0800, Mike Smith wrote: >> On Monday, 9 November 1998 at 22:38:04 -0800, Mike Smith wrote: >>> >>> Just started playing with Vinum. Gawd Greg, this thing seriously needs >>> a "smart" frontend to do the "simple" things. >> >> Any suggestions? After seeing people just banging out RAID >> configurations with GUIs, I thought that this is probably a Bad >> Thing. If you don't understand what you're doing, you shouldn't be >> doing it. > > That's not entirely true. We'll argue that some other time. >> The four-layer concepts used by Veritas and Vinum have always been >> difficult to understand. I'm trying to work out how to explain them >> better, but taking the Microsoft-style "don't worry, little boy, I'll >> do it all for you" approach is IMO not the right way. > > I think it's a mistake to conceal all the workings, but it's also a > mistake to assume that for the "common case", you need to thrust all of > it into the novice's face. > > The "common case" for RAID applications seems to be: "I have these > disk units, and I want to make them into a RAID volume". So the > required functionality is: > > 1) Input the disks to participate in the volume. drive a device /dev/da0h drive b device /dev/da1h drive c device /dev/da2h drive d device /dev/da3h drive e device /dev/da4h > 2) Input the RAID model to be used. plex org raid5 256k > Step 2 should check the sizes of the disks selected in step 1, and make > it clear that you can only get striped or RAID 5 volumes if the disks > are all the same size. You haven't said how big you want it yet. > If they're within 10% or so of each other, it should probably ignore > the excess on the larger drives. Why? That would be a waste. Just say: sd drive a length 5g sd drive b length 5g sd drive c length 5g sd drive d length 5g sd drive e length 5g This is the way it is at the moment. Agreed, it would be nice to find a maximum size available. Currently you need to do this: $ vinum ld -v | grep Avail Available: 128985600 bytes (123 MB) Available: 172966400 bytes (164 MB) Available: 24199680 bytes (23 MB) Available: 24199680 bytes (23 MB) (don't worry about the tiny disks, you've seen these ones before :-) I'll think about how to tell the system that you want a maximum size, but in production environments these are things you think about before you start putting the hardware together. None of this requires a GUI, of course, and IMO none of it is any easier with a GUI. >>> There was an interesting symptom observed in striped mode, where the >>> disks seemed to have a binarily-weighted access pattern. >> >> Can you describe that in more detail? Maybe I should consider >> relating stripe size to cylinder group size. > > I'm wondering if it was just a beat pattern related to the stripe size > and cg sizes. Basically, the first disk in the group of 4 was always > active. The second would go inactive for a very short period of time > on a reasonably regular basis. The third for slightly longer, and the > fourth for longer still, with the intervals for the third and fourth > being progressively shorter. Right. I'm still planning to think about it. >>> It will get more interesting when I add two more 9GB drives and four >>> more 4GB units to the volume; especially as I haven't worked out if I >>> can stripe the 9GB units separately and then concatenate their plex >>> with the plex containing the 4GB units; my understanding is that all >>> plexes in a volume contain copies of the same data. >> >> Correct. I need to think about how to do this, and whether it's worth >> the trouble. It's straightforward with concatenated plexes, of >> course. > > Yes, and it may be that activities will be sufficiently spread out over > the volume that this won't be a problem. Possibly. If you're using UFS it should be. >>> Can you nest plexes? >> >> No. > > That's somewhat unfortunate, but probably contributes to code > simplicity. 8) Well, no. I can see the requirement for easy extensibility, but nesting plexes isn't the way to do it. Finding a more flexible mapping between plexes and subdisks is. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 18:31:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05532 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 18:31:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05527 for ; Thu, 12 Nov 1998 18:31:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA02465; Thu, 12 Nov 1998 18:29:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811130229.SAA02465@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone In-reply-to: Your message of "Fri, 13 Nov 1998 12:51:34 +1030." <19981113125134.M781@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Nov 1998 18:29:06 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> The four-layer concepts used by Veritas and Vinum have always been > >> difficult to understand. I'm trying to work out how to explain them > >> better, but taking the Microsoft-style "don't worry, little boy, I'll > >> do it all for you" approach is IMO not the right way. > > > > I think it's a mistake to conceal all the workings, but it's also a > > mistake to assume that for the "common case", you need to thrust all of > > it into the novice's face. > > > > The "common case" for RAID applications seems to be: "I have these > > disk units, and I want to make them into a RAID volume". So the > > required functionality is: > > > > 1) Input the disks to participate in the volume. > > drive a device /dev/da0h > drive b device /dev/da1h > drive c device /dev/da2h > drive d device /dev/da3h > drive e device /dev/da4h > > > 2) Input the RAID model to be used. > > plex org raid5 256k > > > Step 2 should check the sizes of the disks selected in step 1, and make > > it clear that you can only get striped or RAID 5 volumes if the disks > > are all the same size. > > You haven't said how big you want it yet. Yes I have. I've said I want to use all of these disks. Use them all, dammit. > > If they're within 10% or so of each other, it should probably ignore > > the excess on the larger drives. > > Why? That would be a waste. Just say: > > sd drive a length 5g > sd drive b length 5g > sd drive c length 5g > sd drive d length 5g > sd drive e length 5g If you have two drives 4.1GB and two that are 4.3GB, and you want to stripe them, you have to use a base size of 4.1GB and throw away 400MB. Either that, or you subdivide the disks into multiple partitions looking for the largest common submultiple. Yuck. > None of this requires a GUI, of course, and IMO none of it is any > easier with a GUI. I never said it needed a GUI. I said it needed a tool that eliminated the unnecessary calculations. The tool should do everything required to translate the directive "I want a RAID x volume on these disks" into a vinum configuration. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 18:34:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05976 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 18:34:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05951 for ; Thu, 12 Nov 1998 18:34:43 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA26937; Fri, 13 Nov 1998 13:04:13 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id NAA01719; Fri, 13 Nov 1998 13:03:50 +1030 (CST) Message-ID: <19981113130349.N781@freebie.lemis.com> Date: Fri, 13 Nov 1998 13:03:49 +1030 From: Greg Lehey To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <19981113125134.M781@freebie.lemis.com> <199811130229.SAA02465@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811130229.SAA02465@dingo.cdrom.com>; from Mike Smith on Thu, Nov 12, 1998 at 06:29:06PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 12 November 1998 at 18:29:06 -0800, Mike Smith wrote: >>>> The four-layer concepts used by Veritas and Vinum have always been >>>> difficult to understand. I'm trying to work out how to explain them >>>> better, but taking the Microsoft-style "don't worry, little boy, I'll >>>> do it all for you" approach is IMO not the right way. >>> >>> I think it's a mistake to conceal all the workings, but it's also a >>> mistake to assume that for the "common case", you need to thrust all of >>> it into the novice's face. >>> >>> The "common case" for RAID applications seems to be: "I have these >>> disk units, and I want to make them into a RAID volume". So the >>> required functionality is: >>> >>> 1) Input the disks to participate in the volume. >> >> drive a device /dev/da0h >> drive b device /dev/da1h >> drive c device /dev/da2h >> drive d device /dev/da3h >> drive e device /dev/da4h >> >>> 2) Input the RAID model to be used. >> >> plex org raid5 256k >> >>> Step 2 should check the sizes of the disks selected in step 1, and make >>> it clear that you can only get striped or RAID 5 volumes if the disks >>> are all the same size. >> >> You haven't said how big you want it yet. > > Yes I have. I've said I want to use all of these disks. Use them all, > dammit. Ah. OK. >>> If they're within 10% or so of each other, it should probably ignore >>> the excess on the larger drives. >> >> Why? That would be a waste. Just say: >> >> sd drive a length 5g >> sd drive b length 5g >> sd drive c length 5g >> sd drive d length 5g >> sd drive e length 5g > > If you have two drives 4.1GB and two that are 4.3GB, and you want to > stripe them, you have to use a base size of 4.1GB and throw away 400MB. > Either that, or you subdivide the disks into multiple partitions > looking for the largest common submultiple. Yuck. That's exactly what we do, except that we don't throw away the rest: it remains available for other plexes. 400 MB could come in handy somewhere. You'd write: sd drive a length 4100m sd drive b length 4100m sd drive c length 4100m sd drive d length 4100m What's the problem? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 18:43:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06923 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 18:43:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06906; Thu, 12 Nov 1998 18:43:53 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id VAA05464; Thu, 12 Nov 1998 21:41:37 -0500 (EST) Date: Thu, 12 Nov 1998 21:41:36 -0500 (EST) From: Chuck Robey To: Artur Grabowski cc: Tech1 , hackers@FreeBSD.ORG, isp@FreeBSD.ORG, tech@openbsd.org, tech-kern@netbsd.org Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13 Nov 1998, Artur Grabowski wrote: > "Tech1" writes: > > > The cost of this software is $350 but open for bargin. For more than 10M $ > > company it's another price. If anyone working as consultant for companies. > > You may resell this software to them. > > Or you can get almost the same thing for free from http://www.eddieware.org/ > With source code. (Yes, I know it still doesn't run on *BSD, but that's a > matter of weeks until that code is released). The guy's trying to make a living, and you're not. You don't know the quality of either piece of software yet, but attitudes like that are a big reason that free software isn't more highly catered to by commercial companies. If you want native versions of things like WordPerfect, then reconsider making posts like this. > > //art > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 19:07:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10005 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 19:07:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09997 for ; Thu, 12 Nov 1998 19:07:09 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40335>; Fri, 13 Nov 1998 14:06:13 +1100 Date: Fri, 13 Nov 1998 14:06:39 +1100 From: Peter Jeremy Subject: Re: [Vinum] Stupid benchmark: newfsstone To: hackers@FreeBSD.ORG Message-Id: <98Nov13.140613est.40335@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > And it's almost impossible to find >spindle synchronized disks nowadays. Seagate Barracuda's support it, I assumed that the newer Seagates did as well. The impression I got was that all you had to do was wire the `spindle sync' lines from all the disks together and then designate all except one as a sync'd slave. Admittedly, I've never tried actually using it. > Finally, aggregating involves a >scatter/gather approach which, unless I've missed something, is not >supported at a hardware level. Each request to the driver specifies >one buffer for the transfer, so the scatter gather would have to be >done by allocating more memory and performing the transfer there (for >a read) and then copying to the correct place. Since the actual data transfer occurs to physical memory, whilst the kernel buffers are in VM, this should just require some imaginative juggling of the PTE's so the physical pages (or actual scatter/gather requests) are de-interleaved (to match the data on each spindle). This does assume that the actual stripe is a multiple of the pagesize (if scatter/gather isn't supported). And I'm not saying that implementing this would be easy or clean. What would be useful is some help (from vinum or ccd) to ensure that the cylinder group blocks (superblock + inode maps etc) don't cross stripes. 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 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 19:12:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10722 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 19:12:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phobos.illtel.denver.co.us (phobos.illtel.denver.co.us [207.33.75.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10703; Thu, 12 Nov 1998 19:12:30 -0800 (PST) (envelope-from abelits@phobos.illtel.denver.co.us) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.9.1a/8.6.9) with SMTP id TAA19001; Thu, 12 Nov 1998 19:12:19 -0800 Date: Thu, 12 Nov 1998 19:12:19 -0800 (PST) From: Alex Belits To: Chuck Robey cc: Artur Grabowski , Tech1 , hackers@FreeBSD.ORG, isp@FreeBSD.ORG, tech@openbsd.org, tech-kern@netbsd.org Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Nov 1998, Chuck Robey wrote: > > "Tech1" writes: > > > > > The cost of this software is $350 but open for bargin. For more than 10M $ > > > company it's another price. If anyone working as consultant for companies. > > > You may resell this software to them. > > > > Or you can get almost the same thing for free from http://www.eddieware.org/ > > With source code. (Yes, I know it still doesn't run on *BSD, but that's a > > matter of weeks until that code is released). > > The guy's trying to make a living, and you're not. What difference does it make? > You don't know the > quality of either piece of software yet, but attitudes like that are a > big reason that free software isn't more highly catered to by commercial > companies. > > If you want native versions of things like WordPerfect, then reconsider > making posts like this. If someone wants native version of things like WordPerfect, he should encourage companies like Corel to do port that software to FreeBSD. BTW, I have a strong suspicion that Corel will rather accept ARM port of FreeBSD than any kind of ass-kissing. -- Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 19:30:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12984 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 19:30:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA12979 for ; Thu, 12 Nov 1998 19:30:18 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id WAA05576; Thu, 12 Nov 1998 22:28:17 -0500 (EST) Date: Thu, 12 Nov 1998 22:28:17 -0500 (EST) From: Chuck Robey To: Alex Belits cc: Artur Grabowski , Tech1 , hackers@FreeBSD.ORG Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Nov 1998, Alex Belits wrote: > > The guy's trying to make a living, and you're not. > > What difference does it make? > > > You don't know the > > quality of either piece of software yet, but attitudes like that are a > > big reason that free software isn't more highly catered to by commercial > > companies. > > > > If you want native versions of things like WordPerfect, then reconsider > > making posts like this. > > If someone wants native version of things like WordPerfect, he should > encourage companies like Corel to do port that software to FreeBSD. BTW, > I have a strong suspicion that Corel will rather accept ARM port of > FreeBSD than any kind of ass-kissing. It's not "ass-kissing", it's respect for someone else's work. I'm not saying you fawn on them, I'm saying that you don't slam their work on the sole reason that they're trying to make a buck from it. There were many reasons to dump on Tech1 (whoever that is) that I'd have been fine with ... like cross posting (which I largely removed, you should have) or posting commercial messages on lists not chartered for such, but jumping on commercial work *per se* is utterly destructive, shortsighted, and wrong. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 20:00:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15484 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 20:00:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15479 for ; Thu, 12 Nov 1998 19:59:59 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1a/8.9.1) with ESMTP id UAA04724; Thu, 12 Nov 1998 20:00:22 -0800 (PST) To: Chuck Robey cc: Alex Belits , Artur Grabowski , Tech1 , hackers@FreeBSD.ORG Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes In-reply-to: Your message of "Thu, 12 Nov 1998 22:28:17 EST." Date: Thu, 12 Nov 1998 20:00:22 -0800 Message-ID: <4720.910929622@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can we PLEASE get this crap off so many mailing lists? All of you know better. Thanks. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 20:00:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15707 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 20:00:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from thelab.hub.org (nat0574.mpoweredpc.net [142.177.190.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15672; Thu, 12 Nov 1998 20:00:21 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id XAA06250; Thu, 12 Nov 1998 23:58:39 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 12 Nov 1998 23:58:38 -0400 (AST) From: The Hermit Hacker To: Alex Belits cc: Chuck Robey , Artur Grabowski , Tech1 , hackers@FreeBSD.ORG, isp@FreeBSD.ORG, tech@openbsd.org, tech-kern@netbsd.org Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Nov 1998, Alex Belits wrote: > > You don't know the > > quality of either piece of software yet, but attitudes like that are a > > big reason that free software isn't more highly catered to by commercial > > companies. > > > > If you want native versions of things like WordPerfect, then reconsider > > making posts like this. > > If someone wants native version of things like WordPerfect, he should > encourage companies like Corel to do port that software to FreeBSD. BTW, > I have a strong suspicion that Corel will rather accept ARM port of > FreeBSD than any kind of ass-kissing. Actually, I have to quickly agree with Chuck on this...I don't personally want WordPerfect, mind you. But, I would be willing to pay for a copy of StarOffice 5.0 if it were native to FreeBSD, since it would effectively allow me to totally ditch any reliance I have on Winbloze... I wish there were a way of "convincing" commercial enterprises to port to us :( Here's a question for "those in the power and the know"...has anyone considered "contracting" a port of a commercial software package to FreeBSD? For instance, I'd love having a copy of Staroffice native to FreeBSD, and would be willing to pay for such...how many others are of the same position? How many would be willing to go so far as to pay FreeBSD, Inc to approach StarDivision as *one* entity and say "here is a cheque for X dollars to cover porting costs"? Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 20:14:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA17367 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 20:14:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from WEBBSD1.turnaround.com.au (webbsd1.turnaround.com.au [203.39.138.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17358 for ; Thu, 12 Nov 1998 20:14:17 -0800 (PST) (envelope-from J_Shevland@TurnAround.com.au) Received: from TurnAround.com.au (dhcp110.turnaround.com.au [192.168.1.110] (may be forged)) by WEBBSD1.turnaround.com.au (8.8.7/8.8.7) with ESMTP id PAA11827; Fri, 13 Nov 1998 15:17:03 +1100 (EST) (envelope-from J_Shevland@TurnAround.com.au) Message-ID: <364BB1C6.838816DD@TurnAround.com.au> Date: Fri, 13 Nov 1998 15:12:54 +1100 From: Joe Shevland Organization: TurnAround Solutions Pty. Ltd. X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: The Hermit Hacker CC: Tech1 , hackers@FreeBSD.ORG Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Hermit Hacker wrote: > > On Thu, 12 Nov 1998, Alex Belits wrote: > > > > You don't know the > > > quality of either piece of software yet, but attitudes like that are a > > > big reason that free software isn't more highly catered to by commercial > > > companies. > > > > > > If you want native versions of things like WordPerfect, then reconsider > > > making posts like this. > > > > If someone wants native version of things like WordPerfect, he should > > encourage companies like Corel to do port that software to FreeBSD. BTW, > > I have a strong suspicion that Corel will rather accept ARM port of > > FreeBSD than any kind of ass-kissing. I'd just like to say that I don't think anyone really 'slammed' Tech1 or his/their product, but anyway, not what I'm writing about... > Actually, I have to quickly agree with Chuck on this...I don't > personally want WordPerfect, mind you. But, I would be willing to pay for > a copy of StarOffice 5.0 if it were native to FreeBSD, since it would > effectively allow me to totally ditch any reliance I have on Winbloze... > > I wish there were a way of "convincing" commercial enterprises to > port to us :( > > Here's a question for "those in the power and the know"...has > anyone considered "contracting" a port of a commercial software package to > FreeBSD? For instance, I'd love having a copy of Staroffice native to > FreeBSD, and would be willing to pay for such...how many others are of the > same position? How many would be willing to go so far as to pay FreeBSD, > Inc to approach StarDivision as *one* entity and say "here is a cheque for > X dollars to cover porting costs"? I most certainly would be willing to pay for StarOffice 5.0, as you've stated it would mark the end of my need for Windows, at least where I'm not developing for Windoze shops/uninformed companies. I know of many other people that have expressed a similar sentiment, so I guess I'm saying... yip, I'd be willing to pay. > Marc G. Fournier > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > -- ---------------------|============================= Joe Shevland | TurnAround Solutions Senior Consultant | Hobart, Australia No unsolicited email | Voice (03) 6224 9146 | http://www.TurnAround.com.au ---------------------|============================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 20:17:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA17715 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 20:17:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17710 for ; Thu, 12 Nov 1998 20:17:38 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1a/8.9.1) with ESMTP id UAA04886; Thu, 12 Nov 1998 20:18:14 -0800 (PST) To: Joe Shevland cc: hackers@FreeBSD.ORG Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes In-reply-to: Your message of "Fri, 13 Nov 1998 15:12:54 +1100." <364BB1C6.838816DD@TurnAround.com.au> Date: Thu, 12 Nov 1998 20:18:14 -0800 Message-ID: <4882.910930694@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wonder at all of this focus on StarOffice, however. Is Applixware 4.1 just considered an evil alternative, or what? As most folks know (those who have visited www.cdrom.com at any point in the last 2 months, anyway), Walnut Creek CDROM licensed Applixware and has a project going to port it to FreeBSD. We can't get all possible ISVs to play ball, but we can at least start with one. If folks are keen to see this then by all means demonstrate your support by advance ordering a copy of Applixware from http://www.cdrom.com - you won't actually get charged for it until the product has been shipped to you. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 20:20:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18135 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 20:20:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18128 for ; Thu, 12 Nov 1998 20:20:26 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id OAA00727; Fri, 13 Nov 1998 14:49:57 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [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: <4882.910930694@zippy.cdrom.com> Date: Fri, 13 Nov 1998 14:46:11 +1030 (CST) From: "Daniel O'Connor" To: "Jordan K. Hubbard" Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes Cc: hackers@FreeBSD.ORG, Joe Shevland Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Nov-98 Jordan K. Hubbard wrote: > I wonder at all of this focus on StarOffice, however. Is Applixware > 4.1 just considered an evil alternative, or what? As most folks know > (those who have visited www.cdrom.com at any point in the last 2 > months, anyway), Walnut Creek CDROM licensed Applixware and has a > project going to port it to FreeBSD. We can't get all possible ISVs > to play ball, but we can at least start with one. If folks are keen > to see this then by all means demonstrate your support by advance > ordering a copy of Applixware from http://www.cdrom.com - you won't > actually get charged for it until the product has been shipped to you. Is there anyway I can get an Applixware demo? Kinda don't want to fork the $$ out without seeing what its like :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 20:28:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18899 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 20:28:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18894 for ; Thu, 12 Nov 1998 20:28:29 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1a/8.9.1) with ESMTP id UAA04969; Thu, 12 Nov 1998 20:29:10 -0800 (PST) To: "Daniel O'Connor" cc: hackers@FreeBSD.ORG, Joe Shevland Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes In-reply-to: Your message of "Fri, 13 Nov 1998 14:46:11 +1030." Date: Thu, 12 Nov 1998 20:29:10 -0800 Message-ID: <4963.910931350@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there anyway I can get an Applixware demo? > Kinda don't want to fork the $$ out without seeing what its like :) I don't think a demo is available - http://www.applix.com/appware/linux/index.htm is pretty much all you get for now in the way of information. :( - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 20:31:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19101 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 20:31:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from thelab.hub.org (nat0574.mpoweredpc.net [142.177.190.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19092 for ; Thu, 12 Nov 1998 20:31:12 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id AAA06630; Fri, 13 Nov 1998 00:30:41 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 13 Nov 1998 00:30:41 -0400 (AST) From: The Hermit Hacker To: Joe Shevland cc: Tech1 , hackers@FreeBSD.ORG Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes In-Reply-To: <364BB1C6.838816DD@TurnAround.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Nov 1998, Joe Shevland wrote: > I most certainly would be willing to pay for StarOffice 5.0, as you've > would mark the end of my need for Windows, at least where I'm not > developing for Windoze shops/uninformed companies. > > I know of many other people that have expressed a similar sentiment, > so I guess I'm saying... yip, I'd be willing to pay. How much is the product worth though? SO5.0 supposedly handles all the Office97 stuff...how much is Office97 worth? Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 20:32:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19262 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 20:32:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19244 for ; Thu, 12 Nov 1998 20:32:26 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id PAA01061; Fri, 13 Nov 1998 15:01:56 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [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: <4963.910931350@zippy.cdrom.com> Date: Fri, 13 Nov 1998 14:58:11 +1030 (CST) From: "Daniel O'Connor" To: "Jordan K. Hubbard" Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes Cc: Joe Shevland , hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Nov-98 Jordan K. Hubbard wrote: > > Is there anyway I can get an Applixware demo? > > Kinda don't want to fork the $$ out without seeing what its like :) > I don't think a demo is available - > http://www.applix.com/appware/linux/index.htm is pretty much all you > get for now in the way of information. :( Yeah I couldn't see any either :( Hey, I wonder if I beg wether they'll give me a copy to review =) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 20:46:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20643 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 20:46:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zeus.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20638 for ; Thu, 12 Nov 1998 20:46:28 -0800 (PST) (envelope-from akm@zeus.theinternet.com.au) Received: (from akm@localhost) by zeus.theinternet.com.au (8.8.7/8.8.7) id OAA18497 for hackers@freebsd.org; Fri, 13 Nov 1998 14:32:50 +1000 (EST) (envelope-from akm) From: Andrew Kenneth Milton Message-Id: <199811130432.OAA18497@zeus.theinternet.com.au> Subject: Applixware In-Reply-To: <4963.910931350@zippy.cdrom.com> from "Jordan K. Hubbard" at "Nov 12, 98 08:29:10 pm" To: hackers@FreeBSD.ORG Date: Fri, 13 Nov 1998 14:32:50 +1000 (EST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG +----[ Jordan K. Hubbard ]--------------------------------------------- | > Is there anyway I can get an Applixware demo? | > Kinda don't want to fork the $$ out without seeing what its like :) | | I don't think a demo is available - | http://www.applix.com/appware/linux/index.htm is pretty much all you | get for now in the way of information. :( It looks like it's linked against Motif -- goody emacs key bindings :-) Too bad FrameMaker is so expensive, otherwise it'd be worth harassing them to do a FreeBSD port (i.e. I can't afford/justify it, so I won't badger them). They've got AIX and HPUX versions so I wouldn't think there'd be too much work to get it to build for us, those being BSD(ish) systems. It's the nicest thing I've used for technical type documentation. I'd be willing to pay for Applixware if it has support for new filters the next time MS changes their word format (again). It's very hard to explain to clients to use Lowest Common Denominator (well for them) when attaching documents. -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | Milton ACN: 082 081 472 | M:+61 416 022 411 |72 Col .Sig PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au|Specialist To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 20:47:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20719 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 20:47:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20710 for ; Thu, 12 Nov 1998 20:47:24 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40323>; Fri, 13 Nov 1998 15:46:25 +1100 Date: Fri, 13 Nov 1998 15:46:51 +1100 From: Peter Jeremy Subject: dump(8) very slow To: hackers@FreeBSD.ORG Message-Id: <98Nov13.154625est.40323@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As has been mentioned recently (in the thread on the performance of striped filesystems), the throughput of a disk is strongly correlated with I/O request size - large requests are necessary to get close to the theoretical throughputs (which are the ones claimed by the vendors). The FFS design took this into account (with support for groups of adjacent blocks being read/written in one operation). Unfortunately, dump(8) is distinctly sub-optimal as far as reading the disk is concerned. Dump reads the disk in blocksize blocks (with partial blocks read as a multiple of fragsize). For a typical filesystem this means that dump never reads more than 8K at a time (and if there are lots of small files, the average read size will drop). This translates (at least for me) to dump throughputs (to /dev/null) of 500-1000KBps - slower than typical tape drives. I believe that this could be substantially improved (at the expense of increased working set size), without changing the dump tape format (ie restore(8) is not affected). The approach I'm thinking of would be to allocate a large(*) buffer (or buffers) and then sort and merge the outstanding queue of read requests to fill the buffer, whilst maximising the individual read request sizes. (Taking into account the fact that, in general, it is faster to unnecessarily read a block or two off disk, rather than issue two smaller reads for nearly adjacent sections). The tape block order can be restored by using either writev or readv to re-order the buffer. Two buffers (and associated processes) could be used to overlap disk reads and tape writes. Is this approach worth the effort? I suspect this depends on how well associated sequential blocks of inodes correlate to associated groups of data blocks on disk - I don't know the answer to this. Since this amounts to a buffer cache (albeit with a special layout and replacement policy), would dump be better off going through the buffer cache (maybe with some extra system calls to help dump tell the buffer cache management software what it's doing - ala madvise(2))? (*) where `large' is as big as possible whilst keeping dump(8) and the buffer(s) resident. 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 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 21:05:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22080 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 21:05:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22073 for ; Thu, 12 Nov 1998 21:05:45 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id XAA06134; Thu, 12 Nov 1998 23:58:58 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Thu, 12 Nov 1998 23:58:58 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Andrew Kenneth Milton cc: hackers@FreeBSD.ORG Subject: Re: Applixware In-Reply-To: <199811130432.OAA18497@zeus.theinternet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Nov 1998, Andrew Kenneth Milton wrote: > I'd be willing to pay for Applixware if it has support for new filters > the next time MS changes their word format (again). It's very hard to > explain to clients to use Lowest Common Denominator (well for them) > when attaching documents. > Just hoping to elicit a chuckle... I recently asked for several quotes on HP-UX PA-RISC boxen. I was sent word documents. I replied, "What makes you think I want/can read this format." I was then sent RTF documents. I reconsidered buying from the vendor. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 21:29:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA23949 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 21:29:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA23944 for ; Thu, 12 Nov 1998 21:29:49 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id VAA01053; Thu, 12 Nov 1998 21:29:20 -0800 (PST) (envelope-from dillon) Date: Thu, 12 Nov 1998 21:29:20 -0800 (PST) From: Matthew Dillon Message-Id: <199811130529.VAA01053@apollo.backplane.com> To: Greg Lehey Cc: "Justin T. Gibbs" , hackers@FreeBSD.ORG Subject: Re: SCSI vs. DMA33.. References: <98Nov11.134648jst.21907@ns.isi.co.jp> <199811111538.IAA00103@narnia.plutotech.com> <19981112182238.J463@freebie.lemis.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :>> earlier today. :> :> You had all of 1 command going to each disk. That doesn't give :> you any per-device overlap. : :Sure. I was referring to the command overhead, not the effect of :overlapped commands. : :> If you really want to see the effect of overlapped commands, run a :> benchmark through the filesystem that causes lots of commands to be :... : :No doubt, and that's what I intended to do next. Unfortunately, I've :just fallen off the net (massive phone cable damage out in the :street), so I don't can't download any benchmarks. : :Greg I think where overlapping commands have their greatest advantage is when a command to a drive has a certain latency associated with it that prevents you from issuing another command to the drive that might be completed more efficiently by the drive, but I've done rather extensive tests in the last few days and I don't think tags have as great an effect on performance as disconnection does (i.e. being able to run commands to several drives simultaniously). Here are some SCSI command latency / bandwidth tests. Starting out with a real small block size :-), observe both the drive transfer rate, number of transfers/sec, and the cpu used/idle time. dd if=/dev/rsd1 of=/dev/null bs=1k count=65536 67108864 bytes transferred in 8.598441 secs (7804771 bytes/sec) tty sd0 sd1 sd2 sd3 cpu tin tout sps tps msps sps tps msps sps tps msps sps tps msps us ni sy in id 0 82 0 0 0.0 153547677 0.0 0 0 0.0 0 0 0.0 4 0 29 16 50 0 82 0 0 0.0 153407670 0.0 0 0 0.0 0 0 0.0 3 0 33 12 53 0 82 0 0 0.0 152607630 0.0 0 0 0.0 0 0 0.0 3 0 27 12 58 7600 SCSI transactions/sec, 7.8 MBytes/sec. I believe this is a drive firmware transaction rate limitation. ( platter saturation is 11 MBytes/sec w/ this drive). *** But when you bump the block size up to 4K, the drive has no problem hitting the platter transfer rate of 11 Mbytes/sec, even though it is doing over 2700 SCSI transactions/sec. dd if=/dev/rsd1 of=/dev/null bs=4k count=16384 67108864 bytes transferred in 6.035871 secs (11118340 bytes/sec) 0 81 0 0 0.0 216852711 0.0 0 0 0.0 0 0 0.0 1 0 12 5 82 0 82 0 0 0.0 218372730 0.0 0 0 0.0 0 0 0.0 3 0 9 2 85 0 82 0 0 0.0 218142727 0.0 0 0 0.0 0 0 0.0 0 0 12 5 82 2700 SCSI transactions/sec, 11 MBytes/sec. The cpu is still somewhat loaded by the large number of transactions. *** More interesting things happen when you run commands to multiple SCSI drives simultaniously. dd if=/dev/rsd1 of=/dev/null bs=512 & dd if=/dev/rsd2 of=/dev/null bs=512 & dd if=/dev/rsd3 of=/dev/null bs=512 & dd if=/dev/rsd4 of=/dev/null bs=512 & backup1:/tmp/ssh-dillon# iostat sd1 sd2 sd3 sd4 1 tty sd1 sd2 sd3 sd4 cpu tin tout sps tps msps sps tps msps sps tps msps sps tps msps us ni sy in id 0 7541024081 0.0 40123993 0.0 40093988 0.0 30213001 0.0 9 0 68 19 5 0 7937913802 0.0 37823793 0.0 37623784 0.0 36523664 0.0 7 0 52 32 9 The drives are only doing 1.8 MBytes/sec each, doing 3800 transactions/sec each. The SCSI bus as a whole is doing 15200 transactions/sec. The cpu idle time is 5%, so we've obviously hit a *CPU* limitation on the motherboard here. I don't think we've hit a SCSI bus limitation here. Fortunately, this situation never occurs in real life. ** Lets try an 8K block size. dd if=/dev/rsd1 of=/dev/null bs=8k & dd if=/dev/rsd2 of=/dev/null bs=8k & dd if=/dev/rsd3 of=/dev/null bs=8k & dd if=/dev/rsd4 of=/dev/null bs=8k & backup1:/tmp/ssh-dillon# iostat sd1 sd2 sd3 sd4 1 tty sd1 sd2 sd3 sd4 cpu tin tout sps tps msps sps tps msps sps tps msps sps tps msps us ni sy in id 0 8514860 929 0.0 14876 930 0.0 14876 930 0.0 14860 929 0.0 2 0 15 12 72 0 8514908 932 0.0 14923 933 0.0 14892 931 0.0 14923 933 0.0 1 0 16 9 74 Here we are doing 7.5 MBytes/sec or so per drive (30 MBytes/sec for the whole SCSI bus). The transaction rate doing 8K reads is 930 transactions/sec per drive (3720 for the SCSI bus as a whole). ** If I use a larger block size... 16K, 32K, 64K, and so forth, the transfer rate approachs 34 MBytes/sec (9.5 MBytes/sec per drive). None of the drives are able to get all the way up to 11 Mbytes/sec/drive when all four are transfering to the SCSI bus at the same time, so obviously we are hitting a selection limitation of some sort in either the drive or the controller firmware. I've hit higher aggregate bandwidths in the past (36 MBytes/sec or higher), I'm not sure why I couldn't this time. Could be the drives. In anycase, looking at the random-seeking case, where SCSI bus bandwidth is not an issue (drives cannot get anywhere near their platter bandwidth when seeking randomly :-)), it seems pretty clear to me that a SCSI bus should be able to handle upwards of 3700 SCSI transactions/sec without any significant resource degredation other then cpu (25% utilization w/ a PPro 200). So for the sake of argument, lets say, oh, 2500 SCSI transactions/sec is the most we are willing to perform. A randomly-seeking drive as occurs in a web server or news server can handle 150 transactions/sec at best. 2500 / 150 = 16. So one should be able to put 15 SCSI drives on a SCSI bus in a web server / news reader / other situation without saturating any significant resources yet still be able to run the drives at full speed (for the randomly seeking case). For reference, my NNTP box runs between 1 and 2 MBytes/sec worth of bandwidth under normal load. 15 drives @ 2 MBytes/sec is 30 Mbytes/sec, which I've shown to be easily achievable in the tests above. So the SCSI concurrency here is very significant... you really can throw 15 drives onto a SCSI bus, though realistically you may not be able to extend an ultra-wide cable to that many. I think that IDE is fine as long as you only put in one drive per IDE controller, at least in a randomly seeking situation. In a linear reading situation the drive caching has (through previous postings made by others) been shown to scale to two drives on an IDE bus. Even saying that, I would never personally use IDE in a production commercial system unless the disk were irrelevant, like in a recursive DNS server or a radius server. But I would like to interject one last point here.... on all of our shell machines, web servers, news machines, the resource we run out of *first* are disk suds. It makes little sense to me, if you have two drives, to intentionally halve performance by putting them on one IDE bus, or if you have four drives to halve performance by putting two on each of two IDE busses. If one only has two drives, then putting one on each IDE bus should yield acceptable results, but beyond that a person is seriously limiting the platform's performance. I would go as far as to say 'gee, if we are going to put two drives on the same IDE bus we might as well throw away the 400 MHz P-II motherboard and get something cheaper'. I try to balance resources such that they all start to run out at the same time, otherwise I'm wasting money on something :-). The best example I have of a balanced machine is shell5.ba.best.com. 4 SCSI drives (3 used for web serving / home directories), 512MB ram, P-II/300. It's history has gone something like this: (root drive +) 1x9G drives 128MB ram PPro-200 2x9G drives 256MB ram PPro-200 3x9G drives 384MB ram P-II/300 (note 1) [ 4x9G drives 512MB ram P-II/300 ] FUTURE note (1): new motherboard to accomodate more memory, cpu performance is about the same. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 21:30:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24217 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 21:30:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from unix.tfs.net (as1-p16.tfs.net [139.146.210.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24199 for ; Thu, 12 Nov 1998 21:30:49 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.9.1/8.8.5) id XAA15494; Thu, 12 Nov 1998 23:30:13 -0600 (CST) From: Jim Bryant Message-Id: <199811130530.XAA15494@unix.tfs.net> Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes In-Reply-To: <19981113021140028.AAA45@ff.scsr.com> from Tech1 at "Nov 13, 98 06:11:13 am" To: tech@scsr.com (Tech1) Date: Thu, 12 Nov 1998 23:30:12 -0600 (CST) Cc: freebsd-hackers@FreeBSD.ORG Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #0: Sat Jun 20 11:57:05 CDT 1998 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > 2) If the primary server is detected down, the auxiliary will take over > all off TCP/IP > communications/services for the primary while doing its own regular > activity assigned. > Example:When prime server down, when ftp to the downed server will end > you up in the aux server. okie dokie. i assume that the same MAC's and IP's will be used on the failover machine? > 4) Highly portable to all other mordern unixes like sun,hp,dec,ibm, > unixware, sco etc. well... i won't give up Sun-HA, MC/ServiceGuard, etc.. yet. > 5) the down time is reduced virtually to 0, instead of hours/days. be very careful what you say here. since you are charging a price, i assume you will be held liable for extended downtime. > [snip] how are locks handled? what about proc sync? what about rollback? is there anything more that could actually be useful? how does your product compare to other commercial HA products? in both features and operation? what lvm do you use? jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 21:39:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24613 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 21:39:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24608 for ; Thu, 12 Nov 1998 21:39:16 -0800 (PST) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id AAA06268; Fri, 13 Nov 1998 00:38:41 -0500 (EST) Received: from john.baldwinfamily.org (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id AAA31436; Fri, 13 Nov 1998 00:38:40 -0500 (EST) Message-ID: X-Mailer: XFMail 1.3 [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: <4963.910931350@zippy.cdrom.com> Date: Fri, 13 Nov 1998 00:38:40 -0500 (EST) Reply-To: jobaldwi@vt.edu Organization: Virginia Tech From: John Baldwin To: "Jordan K. Hubbard" Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes Cc: Joe Shevland , hackers@FreeBSD.ORG, "Daniel O'Connor" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- On 13-Nov-98 Jordan K. Hubbard wrote: >> Is there anyway I can get an Applixware demo? >> Kinda don't want to fork the $$ out without seeing what its like :) > > I don't think a demo is available - > http://www.applix.com/appware/linux/index.htm is pretty much all you > get for now in the way of information. :( > > - Jordan I must say that I'm using the StarOffice port (3.1b) (only cause I can't get the 4.0 or 5.0 versions for Linux to run under emulation) and it is on the same level as Office and Corel's WordPerfect Suite (which is what I use in windows land). I would definitely be willing to pay for SO 5.0 myself. I would be a lot more open to Applixware if it had some sort of demo, even a crippled one. I *know* that SO works fine, and I'm somewhat inclined to stick with what works, if you know what I mean. - --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc There is no better road than the one that leads to heaven. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNkvDjojYza302vYpAQFr7wL8Dy8VrgaLY6Jk1AHRoHZoyc9c2FsxUSTP 5V+rzaQAj+k94AYc3YAWPUbc7UjTJmtG6lC5lZzoVctdRa+iyOvPBsS6Sxe5MU9X WS0rRZwimaD2NpQHIQ46/eglJHp5dJ2s =1ozn -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 21:51:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25926 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 21:51:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from thelab.hub.org (nat0574.mpoweredpc.net [142.177.190.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25921 for ; Thu, 12 Nov 1998 21:51:12 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id AAA06692; Fri, 13 Nov 1998 00:39:49 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 13 Nov 1998 00:39:48 -0400 (AST) From: The Hermit Hacker To: "Daniel O'Connor" cc: "Jordan K. Hubbard" , hackers@FreeBSD.ORG, Joe Shevland Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Nov 1998, Daniel O'Connor wrote: > On 13-Nov-98 Jordan K. Hubbard wrote: > > I wonder at all of this focus on StarOffice, however. Is Applixware > > 4.1 just considered an evil alternative, or what? As most folks know > > (those who have visited www.cdrom.com at any point in the last 2 > > months, anyway), Walnut Creek CDROM licensed Applixware and has a > > project going to port it to FreeBSD. We can't get all possible ISVs > > to play ball, but we can at least start with one. If folks are keen > > to see this then by all means demonstrate your support by advance > > ordering a copy of Applixware from http://www.cdrom.com - you won't > > actually get charged for it until the product has been shipped to you. > > Is there anyway I can get an Applixware demo? > Kinda don't want to fork the $$ out without seeing what its like :) SO5.0 supports up to Word97...Applixware supports up to Word6 (please don't tell me they are one in the same? *sigh*) ... ... but, since I did open my big mouth, is there any way of advance ordering without a credit card :( I tend to be kinda 'card poor' :( Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 21:56:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26418 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 21:56:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26413 for ; Thu, 12 Nov 1998 21:56:25 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id VAA01110; Thu, 12 Nov 1998 21:55:59 -0800 (PST) (envelope-from dillon) Date: Thu, 12 Nov 1998 21:55:59 -0800 (PST) From: Matthew Dillon Message-Id: <199811130555.VAA01110@apollo.backplane.com> To: Greg Lehey Cc: Bernd Walter , Mike Smith , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <199811100638.WAA00637@dingo.cdrom.com> <19981111103028.L18183@freebie.lemis.com> <19981111040654.07145@cicely.de> <19981111134546.D20374@freebie.lemis.com> <19981111085152.55040@cicely.de> <19981111183546.D20849@freebie.lemis.com> <19981111194157.06719@cicely.de> <19981112184509.K463@freebie.lemis.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :OK, so you want to have 4 15 kB reads, and you expect a performance :improvement because of it. : :Let's consider the hardware: a good modern disk has a disk transfer :rate of 10 MB/s and a rotational speed of 7200 rpm. Let's look at the :times involved: : : rotational transfer time total : latency : :1 disk/60 kB 4.2 ms 6 ms 10.2 ms :4 disks/15 kB 7.8 ms 1.5 ms 9.3 ms : :Huh? Why the difference in rotational latency? If you're reading This is only relevant in the non-parallel random-seek-read case. Is that the case you are talking about? In the linear-read case the disk's read lookahead cache absorbs the rotational latency. In the parallel random-seek-read case (i.e. a large concurrent load on the disks from different processes), it's irrelevant because although the per-request latency is higher due to lack of spindle synchronization, each disk is still individually pipelined so if disk #1 finishes it's portion of the request before disk #2, disk #1 start work on some other concurrent request, and so forth. It may seem relevant, but remember that the important resource number for striped disks is transactions/sec, not the per-transaction latency. In the large concurrent load case the transactions/sec is not compromised by the lack of a spindle sync. It should also be noted that the case where you might think that per-transaction latency is important... the database case, actually isn't, because concurrent load is typically the most important factor for a database. I'm sure there are applications where per-transaction latency is more important, but not many that also randomly seek the drives. Streaming applications can compensate simply by reading larger chunks of data (which they do anyway since seeking is a real killer for concurrent streaming applications). -Matt :Greg :-- :See complete headers for address, home page and phone numbers :finger grog@lemis.com for PGP public key : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 22:03:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA27325 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 22:03:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA27319 for ; Thu, 12 Nov 1998 22:03:08 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id WAA01141; Thu, 12 Nov 1998 22:02:45 -0800 (PST) (envelope-from dillon) Date: Thu, 12 Nov 1998 22:02:45 -0800 (PST) From: Matthew Dillon Message-Id: <199811130602.WAA01141@apollo.backplane.com> To: Peter Jeremy Cc: hackers@FreeBSD.ORG Subject: Re: dump(8) very slow References: <98Nov13.154625est.40323@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :partial blocks read as a multiple of fragsize). For a typical :filesystem this means that dump never reads more than 8K at a time :(and if there are lots of small files, the average read size will :drop). This translates (at least for me) to dump throughputs (to :/dev/null) of 500-1000KBps - slower than typical tape drives. My SCSI tests show that although the cpu overhead is greater doing small block reads, you will not gain a bandwidth advantage doing larger block reads verses two smaller reads if the small reads are 8K or larger (or even 4K or larger). Other people testing IDE have shown the same results. 1K vs 8K makes a big difference, but 8K vs 16K does not. The disk's lookahead read cache handles it just fine. This is for linear reads, of course. If dump is seeking around, then reading larger blocks might be beneficial to avoid a seek-back later on. I think it's worth messing around with the code. But beware that dump checks inodes more then once during a dump to determine if the file has changed, and does other similar junk... you may not be able to safely cache read data. :Is this approach worth the effort? I suspect this depends on how well :associated sequential blocks of inodes correlate to associated groups :of data blocks on disk - I don't know the answer to this. : :Since this amounts to a buffer cache (albeit with a special layout and :replacement policy), would dump be better off going through the buffer :cache (maybe with some extra system calls to help dump tell the buffer :cache management software what it's doing - ala madvise(2))? : :(*) where `large' is as big as possible whilst keeping dump(8) and : the buffer(s) resident. : :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 5247 : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 22:25:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29003 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 22:25:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28985 for ; Thu, 12 Nov 1998 22:24:52 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA27640; Fri, 13 Nov 1998 16:54:23 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id QAA02211; Fri, 13 Nov 1998 16:54:22 +1030 (CST) Message-ID: <19981113165422.X781@freebie.lemis.com> Date: Fri, 13 Nov 1998 16:54:22 +1030 From: Greg Lehey To: Peter Jeremy , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <98Nov13.140613est.40335@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <98Nov13.140613est.40335@border.alcanet.com.au>; from Peter Jeremy on Fri, Nov 13, 1998 at 02:06:39PM +1100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 13 November 1998 at 14:06:39 +1100, Peter Jeremy wrote: > Greg Lehey wrote: >> And it's almost impossible to find >> spindle synchronized disks nowadays. > > Seagate Barracuda's support it, I assumed that the newer Seagates did > as well. The impression I got was that all you had to do was wire the > `spindle sync' lines from all the disks together and then designate > all except one as a sync'd slave. Admittedly, I've never tried > actually using it. OK, I haven't actually tried, but there were several messages out there suggesting that spindle synchronization was on its way out. >> Finally, aggregating involves a scatter/gather approach which, >> unless I've missed something, is not supported at a hardware level. >> Each request to the driver specifies one buffer for the transfer, >> so the scatter gather would have to be done by allocating more >> memory and performing the transfer there (for a read) and then >> copying to the correct place. > > Since the actual data transfer occurs to physical memory, whilst the > kernel buffers are in VM, this should just require some imaginative > juggling of the PTE's so the physical pages (or actual scatter/gather > requests) are de-interleaved (to match the data on each spindle). Yes, I hadn't neglected that. But VM pages are 4 kB in size, and Bernd was talking about 512 byte stripe width. Bring it up to 4 kB and you're relatively unlikely to lap your stripe. > This does assume that the actual stripe is a multiple of the > pagesize (if scatter/gather isn't supported). Oops. But yes, agreed. > And I'm not saying that implementing this would be easy or clean. I've never been intimately involved in an implementation myself, but I could imagine it could be made either easy or clean. > What would be useful is some help (from vinum or ccd) to ensure that > the cylinder group blocks (superblock + inode maps etc) don't cross > stripes. It's difficult, since you can do what you like with the volume. Use whatever parameters you like for the newfs. Of course, it's obvious that if your cylinder group sizes are a multiple of a relatively large power of two, and your stripe sizes are too, then you're liable to end up with all your superblocks on the same drive. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 22:34:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29867 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 22:34:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29860 for ; Thu, 12 Nov 1998 22:34:44 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA27675; Fri, 13 Nov 1998 17:03:30 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id RAA02232; Fri, 13 Nov 1998 17:03:29 +1030 (CST) Message-ID: <19981113170329.Y781@freebie.lemis.com> Date: Fri, 13 Nov 1998 17:03:29 +1030 From: Greg Lehey To: Matthew Dillon Cc: Bernd Walter , Mike Smith , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <199811100638.WAA00637@dingo.cdrom.com> <19981111103028.L18183@freebie.lemis.com> <19981111040654.07145@cicely.de> <19981111134546.D20374@freebie.lemis.com> <19981111085152.55040@cicely.de> <19981111183546.D20849@freebie.lemis.com> <19981111194157.06719@cicely.de> <19981112184509.K463@freebie.lemis.com> <199811130555.VAA01110@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811130555.VAA01110@apollo.backplane.com>; from Matthew Dillon on Thu, Nov 12, 1998 at 09:55:59PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 12 November 1998 at 21:55:59 -0800, Matthew Dillon wrote: > : > :OK, so you want to have 4 15 kB reads, and you expect a performance > :improvement because of it. > : > :Let's consider the hardware: a good modern disk has a disk transfer > :rate of 10 MB/s and a rotational speed of 7200 rpm. Let's look at the > :times involved: > : > : rotational transfer time total > : latency > : > :1 disk/60 kB 4.2 ms 6 ms 10.2 ms > :4 disks/15 kB 7.8 ms 1.5 ms 9.3 ms > : > :Huh? Why the difference in rotational latency? If you're reading > > This is only relevant in the non-parallel random-seek-read case. Is > that the case you are talking about? Yes. Most people don't install striped volumes for sequential reads (though Justin has shown an exception). > In the linear-read case the disk's read lookahead cache absorbs > the rotational latency. > In the parallel random-seek-read case (i.e. a large concurrent > load on the disks from different processes), it's irrelevant > because although the per-request latency is higher due to lack > of spindle synchronization, each disk is still individually > pipelined so if disk #1 finishes it's portion of the request > before disk #2, disk #1 start work on some other concurrent > request, and so forth. > > It may seem relevant, but remember that the important resource number > for striped disks is transactions/sec, not the per-transaction > latency. Sure, but your argumentation views the speed from the single transaction viewpoint. The fact is that with multiple parallel transactions going on, each physical access involves a seek, rotational latency and the access itself. Let's go back and look at that again from the parallel access point of view: rotational transfer time total latency (total) (total) 1 disk/60 kB 4.2 ms 6 ms 10.2 ms 4 disks/15 kB 16.8 ms 6 ms 22.8 ms This is the (idealized) time that the disks involved are occupied with the transaction. > In the large concurrent load case the transactions/sec is not > compromised by the lack of a spindle sync. Correct. > It should also be noted that the case where you might think that > per-transaction latency is important... the database case, > actually isn't, because concurrent load is typically the most > important factor for a database. I wasn't even thinking that far, but agreed. I don't think there's much point in discussing this matter from a purely theoretical viewpoint: I intend to do some testing when I have Vinum in fit shape, and then I'll publish results. What I have done here (even for sequential access) shows a significant performance improvement for large stripes, even in the area where no "aggregation" is possible (transfer size < stripe size * number of disks). Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 23:15:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03051 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 23:15:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03043 for ; Thu, 12 Nov 1998 23:14:59 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA27813; Fri, 13 Nov 1998 17:44:38 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id RAA27762; Fri, 13 Nov 1998 17:44:37 +1030 (CST) Message-ID: <19981113174437.E781@freebie.lemis.com> Date: Fri, 13 Nov 1998 17:44:37 +1030 From: Greg Lehey To: Matthew Dillon , Peter Jeremy Cc: hackers@FreeBSD.ORG Subject: Re: dump(8) very slow References: <98Nov13.154625est.40323@border.alcanet.com.au> <199811130602.WAA01141@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i xFrom: Greg Lehey In-Reply-To: <199811130602.WAA01141@apollo.backplane.com>; from Matthew Dillon on Thu, Nov 12, 1998 at 10:02:45PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 12 November 1998 at 22:02:45 -0800, Matthew Dillon wrote: >> partial blocks read as a multiple of fragsize). For a typical >> filesystem this means that dump never reads more than 8K at a time >> (and if there are lots of small files, the average read size will >> drop). This translates (at least for me) to dump throughputs (to >> /dev/null) of 500-1000KBps - slower than typical tape drives. > > My SCSI tests show that although the cpu overhead is greater doing > small block reads, you will not gain a bandwidth advantage doing > larger block reads verses two smaller reads if the small reads are > 8K or larger (or even 4K or larger). Other people testing IDE have > shown the same results. Have you been using the raw device? > 1K vs 8K makes a big difference, but 8K vs 16K does not. The disk's > lookahead read cache handles it just fine. That depends on the disks. Here's what my test disks (admittedly, not the newest) do: # dd if=/dev/rsd1a of=/dev/null bs=8k 41943040 bytes transferred in 110.037927 secs (381169 bytes/sec) # dd if=/dev/rsd1a of=/dev/null bs=16k 41943040 bytes transferred in 67.824404 secs (618406 bytes/sec) # dd if=/dev/rsd1a of=/dev/null bs=32k 41943040 bytes transferred in 46.672556 secs (898666 bytes/sec) > This is for linear reads, of course. If dump is seeking around, then > reading larger blocks might be beneficial to avoid a seek-back later on. It doesn't have to be dump doing the seeking. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 23:35:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04424 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 23:35:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04286 for ; Thu, 12 Nov 1998 23:34:59 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m0zeDkd-000I0TC; Fri, 13 Nov 1998 02:34:39 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: pnp/booting problem with new kernel To: hackers@FreeBSD.ORG Date: Fri, 13 Nov 1998 02:34:39 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM910942479-25570-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ELM910942479-25570-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit OS = current, cvsup'd today. AWE64 support with Voxware It appears that when a new kernel is installed, the effects of the last pnp statement issued are lost. When I initially booted this kernel, I did: pnp 1 0 enable os port0 0x220 port1 0x300 port2 0x388 irq0 10 drq0 3 drq1 5 pnp 1 1 enable os port0 0x200 pnp 1 2 enable os port0 0x620 port1 0xa20 port2 0xe20 (see attachment 1 for the dmesg) This works fine for all subsequent boots, until after I install a new kernel. At that time, it appears that the effects of the LAST pnp statement issued are lost. The effects of the previously issued pnp statements are still accurately processed (see attachment 2 for the dmesg). Am I misunderstanding how this should work? Tom --ELM910942479-25570-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=pnp0 Content-Description: original dmesg Content-Transfer-Encoding: 7bit DMESG after pnp statements are entered: a fifo ncr0: single-ended, open drain IRQ driver, using on-chip SRAM found-> vendor=0x5333, dev=0x8a01, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 1, range 32, base e0000000, size 26 vga0: rev 0x01 int a irq 11 on pci0.11.0 Probing for PnP devices: Trying Read_Port at 203 Trying Read_Port at 243 PnP: CSN 1 COMP_DEVICE_ID = 0x2fb0d041 CSN 1 Vendor ID: CTL00c1 [0xc1008c0e] Serial 0x1641e094 Comp ID: PNPb02f [0x2fb0d041] PnP: override config for CSN 1 LDN 0 vend_id 0xc1008c0e port 0x0220 0x0300 0x0388 0x0000 irq 10:0 drq 3:5 en 1 PnP: override config for CSN 1 LDN 1 vend_id 0xc1008c0e port 0x0200 0x0000 0x0000 0x0000 irq 0:0 drq 4:4 en 1 PnP: override config for CSN 1 LDN 2 vend_id 0xc1008c0e port 0x0620 0x0000 0x0000 0x0000 irq 0:0 drq 4:4 en 1 Called nullpnp_probe with tag 0x00000001, type 0xc1008c0e Called nullpnp_probe with tag 0x00000001, type 0x2fb0d041 Probing for devices on the ISA bus: video: RTC equip. code:0x0f, DCC code:0x09 video: CRTC:0x3d4, video option:0x60, rows:80, cols:25, font height:16 video: param table EGA/VGA:0xf00c4644, CGA/MDA:0 video: rows_offset:1 video#0: adapter type:VGA (5), flags:0x7f, CRTC:0x3d4 video#0: init mode:24, bios mode:3, current mode:24 video#0: window:0xf00b8000 size:32k gran:32k, buf:0xf0000000 size:0k video#0: mode:0, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:1, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:2, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:3, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:19, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:20, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:21, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:22, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:23, flags:0x1 T 40x25, font:8x16, win:0xb8000 video#0: mode:25, flags:0x0 T 80x25, font:8x16, win:0xb0000 video#0: mode:24, flags:0x1 T 80x25, font:8x16, win:0xb8000 video#0: mode:7, flags:0x0 T 80x25, font:8x14, win:0xb0000 video#0: mode:112, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:113, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:33, flags:0x0 T 80x30, font:8x16, win:0xb0000 video#0: mode:32, flags:0x1 T 80x30, font:8x16, win:0xb8000 video#0: mode:31, flags:0x0 T 80x50, font:8x8, win:0xb0000 video#0: mode:30, flags:0x1 T 80x50, font:8x8, win:0xb8000 video#0: mode:35, flags:0x0 T 80x60, font:8x8, win:0xb0000 video#0: mode:34, flags:0x1 T 80x60, font:8x8, win:0xb8000 video#0: mode:4, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:5, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:6, flags:0x3 G 640x200x1, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:13, flags:0x3 G 320x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:14, flags:0x3 G 640x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:15, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:17, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:16, flags:0x3 G 640x350x2, 2 plane(s), font:8x14, win:0xa0000 video#0: mode:18, flags:0x3 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:26, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:27, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:28, flags:0x3 G 320x200x8, 1 plane(s), font:8x8, win:0xa0000 video#0: mode:37, flags:0x3 G 320x240x8, 1 plane(s), font:8x8, win:0xa0000 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 0e 0f 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: the current keyboard controller command byte 0047 kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0: keyboard device ID: ab41 sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0: irq maps: 0x401 0x411 0x401 0x401 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface bpf: lp0 attached psm0: current command byte:0047 kbdio: TEST_AUX_PORT status:0000 kbdio: RESET_AUX return code:00fa kbdio: RESET_AUX status:00aa kbdio: 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: data 08 00 00 psm: status 00 02 64 psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0, 2 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, intr, iordy wcd0: 689KB/sec, 256KB cache, audio play, 255 volume levels, ejectable tray wcd0: 120mm audio disc loaded, unlocked 1 3C5x9 board(s) on ISA found at 0x210 ep0 at 0x210-0x21f irq 5 on isa ep0: aui/bnc[*BNC*] address 00:60:8c:62:a5:65 bpf: ep0 attached sb0 at 0x220 irq 10 drq 3 on isa snd0: sbxvi0 at ? drq 5 on isa snd0: sbmidi0 at 0x300 on isa snd0: awe0 at 0x620 on isa awe0: opl0 at 0x388 on isa snd0: joy0 at 0x200 on isa joy0: joystick npx0 on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 175654312 bytes/sec bzero() bandwidth = 88409512 bytes/sec imasks: bio c008c040, tty c0031092, net c0060020 BIOS Geometries: 0:020afe3f 0..522=523 cylinders, 0..254=255 heads, 1..63=63 sectors 1:03fd893f 0..1021=1022 cylinders, 0..137=138 heads, 1..63=63 sectors 0 accounted for Device configuration finished. Intel Pentium F00F detected, installing workaround bpf: tun0 attached bpf: tun1 attached bpf: tun2 attached bpf: tun3 attached bpf: lo0 attached Waiting 15 seconds for SCSI devices to settle ncr0: restart (scsi reset). (probe5:ncr0:0:5:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe5:ncr0:0:5:0): ILLEGAL REQUEST asc:24,0 (probe5:ncr0:0:5:0): Invalid field in CDB sks:c0,1 pass0 at ncr0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI2 device pass0: Serial Number JKA5580002KB3M pass0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled pass1 at ncr0 bus 0 target 5 lun 0 pass1: Removable CD-ROM SCSI2 device pass1: 3.300MB/s transfers da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: Serial Number JKA5580002KB3M da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 3.300MB/s transfers cd0: cd present [327689 x 2048 byte records] Considering FFS root f/s. changing root device to da0s1a da0s1: type 0xa5, start 63, end = 8885267, size 8885205 : OK wd0s1: type 0xb, start 63, end = 6152894, size 6152832 : OK wd0s2: type 0x5, start 6152895, end = 8385929, size 2233035 : OK wd0s5: type 0xb, start 6152958, end = 8385929, size 2232972 : OK ffs_mountfs: superblock updated for soft updates Linux-ELF exec handler installed --ELM910942479-25570-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=pnp1 Content-Description: dmesg after installing new kernel Content-Transfer-Encoding: 7bit DMESG after new kernel installed: ebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 4, range 32, base 0000d400, size 8 map[1]: type 1, range 32, base e7000000, size 8 map[2]: type 1, range 32, base e6800000, size 12 ncr0: rev 0x03 int a irq 9 on pci0.10.0 ncr0: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo ncr0: single-ended, open drain IRQ driver, using on-chip SRAM found-> vendor=0x5333, dev=0x8a01, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 1, range 32, base e0000000, size 26 vga0: rev 0x01 int a irq 11 on pci0.11.0 Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 Trying Read_Port at 243 PnP: CSN 1 COMP_DEVICE_ID = 0x2fb0d041 CSN 1 Vendor ID: CTL00c1 [0xc1008c0e] Serial 0x1641e094 Comp ID: PNPb02f [0x2fb0d041] Called nullpnp_probe with tag 0x00000001, type 0xc1008c0e Called nullpnp_probe with tag 0x00000001, type 0x2fb0d041 Probing for devices on the ISA bus: video: RTC equip. code:0x0f, DCC code:0x09 video: CRTC:0x3d4, video option:0x60, rows:80, cols:25, font height:16 video: param table EGA/VGA:0xf00c4644, CGA/MDA:0 video: rows_offset:1 video#0: adapter type:VGA (5), flags:0x7f, CRTC:0x3d4 video#0: init mode:24, bios mode:3, current mode:24 video#0: window:0xf00b8000 size:32k gran:32k, buf:0xf0000000 size:0k video#0: mode:0, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:1, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:2, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:3, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:19, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:20, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:21, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:22, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:23, flags:0x1 T 40x25, font:8x16, win:0xb8000 video#0: mode:25, flags:0x0 T 80x25, font:8x16, win:0xb0000 video#0: mode:24, flags:0x1 T 80x25, font:8x16, win:0xb8000 video#0: mode:7, flags:0x0 T 80x25, font:8x14, win:0xb0000 video#0: mode:112, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:113, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:33, flags:0x0 T 80x30, font:8x16, win:0xb0000 video#0: mode:32, flags:0x1 T 80x30, font:8x16, win:0xb8000 video#0: mode:31, flags:0x0 T 80x50, font:8x8, win:0xb0000 video#0: mode:30, flags:0x1 T 80x50, font:8x8, win:0xb8000 video#0: mode:35, flags:0x0 T 80x60, font:8x8, win:0xb0000 video#0: mode:34, flags:0x1 T 80x60, font:8x8, win:0xb8000 video#0: mode:4, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:5, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:6, flags:0x3 G 640x200x1, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:13, flags:0x3 G 320x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:14, flags:0x3 G 640x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:15, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:17, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:16, flags:0x3 G 640x350x2, 2 plane(s), font:8x14, win:0xa0000 video#0: mode:18, flags:0x3 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:26, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:27, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:28, flags:0x3 G 320x200x8, 1 plane(s), font:8x8, win:0xa0000 video#0: mode:37, flags:0x3 G 320x240x8, 1 plane(s), font:8x8, win:0xa0000 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 0e 0f 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: the current keyboard controller command byte 0047 kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0: keyboard device ID: ab41 sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface bpf: lp0 attached psm0: current command byte:0047 kbdio: TEST_AUX_PORT status:0000 kbdio: RESET_AUX return code:00fa kbdio: RESET_AUX status:00aa kbdio: 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: data 08 00 00 psm: status 00 02 64 psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0, 2 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, intr, iordy wcd0: 689KB/sec, 256KB cache, audio play, 255 volume levels, ejectable tray wcd0: 120mm audio disc loaded, unlocked 1 3C5x9 board(s) on ISA found at 0x210 ep0 at 0x210-0x21f irq 5 on isa ep0: aui/bnc[*BNC*] address 00:60:8c:62:a5:65 bpf: ep0 attached sb0 at 0x220 irq 10 drq 3 on isa snd0: sbxvi0 at ? drq 5 on isa snd0: sbmidi0 at 0x300 on isa snd0: awe0 at 0x620 on isa AWE32: not detected opl0 at 0x388 on isa snd0: joy0 at 0x200 on isa joy0: joystick npx0 on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 175654312 bytes/sec bzero() bandwidth = 88409512 bytes/sec imasks: bio c008c040, tty c0031092, net c0060020 BIOS Geometries: 0:020afe3f 0..522=523 cylinders, 0..254=255 heads, 1..63=63 sectors 1:03fd893f 0..1021=1022 cylinders, 0..137=138 heads, 1..63=63 sectors 0 accounted for Device configuration finished. Intel Pentium F00F detected, installing workaround bpf: tun0 attached bpf: tun1 attached bpf: tun2 attached bpf: tun3 attached bpf: lo0 attached Waiting 15 seconds for SCSI devices to settle ncr0: restart (scsi reset). (probe5:ncr0:0:5:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe5:ncr0:0:5:0): ILLEGAL REQUEST asc:24,0 (probe5:ncr0:0:5:0): Invalid field in CDB sks:c0,1 pass0 at ncr0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI2 device pass0: Serial Number JKA5580002KB3M pass0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled pass1 at ncr0 bus 0 target 5 lun 0 pass1: Removable CD-ROM SCSI2 device pass1: 3.300MB/s transfers da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: Serial Number JKA5580002KB3M da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 3.300MB/s transfers cd0: cd present [327689 x 2048 byte records] Considering FFS root f/s. changing root device to da0s1a da0s1: type 0xa5, start 63, end = 8885267, size 8885205 : OK wd0s1: type 0xb, start 63, end = 6152894, size 6152832 : OK wd0s2: type 0x5, start 6152895, end = 8385929, size 2233035 : OK wd0s5: type 0xb, start 6152958, end = 8385929, size 2232972 : OK ffs_mountfs: superblock updated for soft updates Linux-ELF exec handler installed --ELM910942479-25570-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 12 23:40:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04726 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 23:40:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from unix.tfs.net (as1-p103.tfs.net [139.146.210.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04721 for ; Thu, 12 Nov 1998 23:40:19 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.9.1/8.8.5) id BAA15765; Fri, 13 Nov 1998 01:39:51 -0600 (CST) From: Jim Bryant Message-Id: <199811130739.BAA15765@unix.tfs.net> Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes In-Reply-To: <19981113062046320.AAA205@ff.scsr.com> from Tech1 at "Nov 13, 98 10:20:21 am" To: tech@scsr.com (Tech1) Date: Fri, 13 Nov 1998 01:39:50 -0600 (CST) Cc: freebsd-hackers@FreeBSD.ORG Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #0: Sat Jun 20 11:57:05 CDT 1998 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i was asking for details. you gave a minimal management overview. i'm not going to spend $350 unless i know how it operates. please give details if you are going to give details. do you have a paper on this high-availability system that would give details? if so please post it. what commercial systems are you familiar with? i was asking generically for a comparison to commercial systems as only one of my questions. what is involved in package configuration? i also find it hard to believe that if a service fails, that the lv's can be dismounted and remounted on the failover machine in a thousandth of a sec. i assume that this requires dual paths to the drives? and to add new questions: what mirroring techniques do you use? also please answer my original questions. i am interested, if it is something usable. merely saying it can fail over says nothing. In reply: > The down time will actually be between 0.001 sec to 1 sec. How's sun fail > safe features like? May be i can add more things to it. > > ---------- > > From: Jim Bryant > > To: Tech1 > > Cc: freebsd-hackers@freebsd.org > > Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes > > Date: Thursday, November 12, 1998 9:30 PM > > > > In reply: > > > 2) If the primary server is detected down, the auxiliary will take > over > > > all off TCP/IP > > > communications/services for the primary while doing its own > regular > > > activity assigned. > > > Example:When prime server down, when ftp to the downed server will > end > > > you up in the aux server. > > > > okie dokie. > > > > i assume that the same MAC's and IP's will be used on the failover > machine? > > > > > 4) Highly portable to all other mordern unixes like sun,hp,dec,ibm, > > > unixware, sco etc. > > > > well... i won't give up Sun-HA, MC/ServiceGuard, etc.. yet. > > > > > 5) the down time is reduced virtually to 0, instead of hours/days. > > > > be very careful what you say here. since you are charging a price, i > > assume you will be held liable for extended downtime. > > > > > [snip] > > > > how are locks handled? what about proc sync? what about rollback? > > > > is there anything more that could actually be useful? > > > > how does your product compare to other commercial HA products? in > > both features and operation? > > > > what lvm do you use? jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 00:03:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06356 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 00:03:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06351 for ; Fri, 13 Nov 1998 00:03:37 -0800 (PST) (envelope-from ticso@cicely5.cicely.de) Received: from cicely.cicely.de (cicely.de [194.231.9.142]) by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id JAA10573; Fri, 13 Nov 1998 09:03:01 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [10.1.1.7]) by cicely.cicely.de (8.8.8/8.8.8) with ESMTP id JAA01065; Fri, 13 Nov 1998 09:03:17 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.9.0/8.9.0) id JAA29661; Fri, 13 Nov 1998 09:03:12 +0100 (CET) Message-ID: <19981113090311.05423@cicely.de> Date: Fri, 13 Nov 1998 09:03:11 +0100 From: Bernd Walter To: Greg Lehey , Mike Smith , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <199811100638.WAA00637@dingo.cdrom.com> <19981111103028.L18183@freebie.lemis.com> <19981111040654.07145@cicely.de> <19981111134546.D20374@freebie.lemis.com> <19981111085152.55040@cicely.de> <19981111183546.D20849@freebie.lemis.com> <19981111194157.06719@cicely.de> <19981112184509.K463@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19981112184509.K463@freebie.lemis.com>; from Greg Lehey on Thu, Nov 12, 1998 at 06:45:09PM +1030 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 12, 1998 at 06:45:09PM +1030, Greg Lehey wrote: > On Wednesday, 11 November 1998 at 19:41:57 +0100, Bernd Walter wrote: > [...] > > What I expect is that an agreagation such a 60k chunk access on the > > volume is splited into only one transaction per drive - so you can > > read from all the drives at the same time and get an bandwidth > > increase. > > OK, so you want to have 4 15 kB reads, and you expect a performance > improvement because of it. > > Let's consider the hardware: a good modern disk has a disk transfer > rate of 10 MB/s and a rotational speed of 7200 rpm. Let's look at the > times involved: > > rotational transfer time total > latency > > 1 disk/60 kB 4.2 ms 6 ms 10.2 ms > 4 disks/15 kB 7.8 ms 1.5 ms 9.3 ms > > Huh? Why the difference in rotational latency? If you're reading > from one disk, on average you'll have a half track latency. For two, > on average one is half a track off from the other, so you'll have a > latency of .75 a track. With three drives, it's .875, and with four > drives, it's .9375 of a track. Still, in this case (the largest > possible block size, and only 4 disks), you win--barely. Let's look > at a more typical case: 16 kB > > rotational transfer time total > latency > > 1 disk/16 kB 4.2 ms 1.6 ms 5.8 ms > 4 disks/4 kB 7.8 ms .4 ms 8.2 ms > > Most transfers are 16 kB or less. What really kills you is the lack > of spindle synchronization between the disks. If they were OK I agree - but to get a optimal performance it was alwaysdependend of application to choice the best parameters for stripes and newfsparms > synchronized, that would be fine, but that's more complicated than it > looks. You'd need identical disks with identical layout (subdisks in > the same place on each disk). And it's almost impossible to find > spindle synchronized disks nowadays. Finally, aggregating involves a The drives I'm running vinum on ARE capable of spindle syncronisation and I know for shure that at least modern IBM server disks are to. If there's an interest I can ask Seagate for the cabeling to use it on my. > scatter/gather approach which, unless I've missed something, is not > supported at a hardware level. Each request to the driver specifies > one buffer for the transfer, so the scatter gather would have to be > done by allocating more memory and performing the transfer there (for > a read) and then copying to the correct place. That's something I don't understand - where's the difference between usual parallel access? > > I have thought about aggregating in the manner you describe, and to a > certain extent I feel it's a copout not to do so. I hope you now see > that it doesn't really make sense in this context. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 00:13:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07312 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 00:13:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sundance.stacken.kth.se (sundance.stacken.kth.se [130.237.234.41]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07307 for ; Fri, 13 Nov 1998 00:13:46 -0800 (PST) (envelope-from art@stacken.kth.se) Received: from pizza.stacken.kth.se (pizza.stacken.kth.se [130.237.234.73]) by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id JAA18035; Fri, 13 Nov 1998 09:13:15 +0100 (MET) Received: (from art@localhost) by pizza.stacken.kth.se (8.8.7/8.8.7) id JAA01278; Fri, 13 Nov 1998 09:14:08 +0100 (MET) To: Chuck Robey Cc: hackers@FreeBSD.ORG, tech@openbsd.org Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes References: From: Artur Grabowski Date: 13 Nov 1998 09:14:08 +0100 In-Reply-To: Chuck Robey's message of "Thu, 12 Nov 1998 21:41:36 -0500 (EST)" Message-ID: Lines: 44 X-Mailer: Gnus v5.6.44/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey writes: > On 13 Nov 1998, Artur Grabowski wrote: > > > "Tech1" writes: > > > > > The cost of this software is $350 but open for bargin. For more than 10M $ > > > company it's another price. If anyone working as consultant for companies. > > > You may resell this software to them. > > > > Or you can get almost the same thing for free from http://www.eddieware.org/ > > With source code. (Yes, I know it still doesn't run on *BSD, but that's a > > matter of weeks until that code is released). > > The guy's trying to make a living, and you're not. How do you know that? Is it the normal attitude "noone can make money on freeware"? I just happen to work at /// in the part that's doing Erlang. And Eddie is the way the PHBs want to check if "open sourcing" Erlang would be a good idea. _I_ know that if Erlang stays non-free it will die. So yes, I'm trying to make a living. Please. Don't judge people without knowing the facts. > You don't know the > quality of either piece of software yet, Oh, I know the quality of Eddie. And I certainly know the quality of Erlang. Erlang was _written_ for robustness and failover. And my job is to ensure the quality of Erlang. And I can promise you that I'm doing a great job. > but attitudes like that are a > big reason that free software isn't more highly catered to by commercial > companies. Oh. So Ericsson is a commercial company.. When did we start doing charity? btw. Why shouldn't I let people know that there are alternatives? Even if they are free or commercial? Since when did this market benefit from monopoly? //art To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 00:31:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA08930 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 00:31:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.wgn.net (mail.wgn.net [207.213.0.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08924 for ; Fri, 13 Nov 1998 00:31:44 -0800 (PST) (envelope-from almazs@wgn.net) Received: from laptop (du542-pcap-nca01.wgn.net [207.213.7.34]) by mail.wgn.net (8.9.1/8.9.0) with SMTP id AAA26892 for ; Fri, 13 Nov 1998 00:31:23 -0800 Message-ID: <364BED3F.41B3@wgn.net> Date: Fri, 13 Nov 1998 00:26:39 -0800 From: Co-app Network consulting Reply-To: almazs@wgn.net Organization: Network Consulting X-Mailer: Mozilla 3.0C-NSCP (Win95; U) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: RE: bus logic controller Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi; This may be a little off-topic Where can I get an uptodate info on BusLogic SCSI controllers and drivrs? bought a card that has 'BUSLOGIC FlashPoint LW' marking on it does FreeBSD has native drivers for this scard? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 01:06:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11542 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 01:06:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11537 for ; Fri, 13 Nov 1998 01:06:18 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id BAA25440; Fri, 13 Nov 1998 01:05:29 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id BAA10348; Fri, 13 Nov 1998 01:05:28 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id BAA07536; Fri, 13 Nov 1998 01:05:26 -0800 (PST) From: Don Lewis Message-Id: <199811130905.BAA07536@salsa.gv.tsc.tdk.com> Date: Fri, 13 Nov 1998 01:05:26 -0800 In-Reply-To: Greg Lehey "Re: [Vinum] Stupid benchmark: newfsstone" (Nov 12, 6:45pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Greg Lehey , Bernd Walter , Mike Smith , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Nov 12, 6:45pm, Greg Lehey wrote: } Subject: Re: [Vinum] Stupid benchmark: newfsstone } rotational transfer time total } latency } 1 disk/60 kB 4.2 ms 6 ms 10.2 ms } 4 disks/15 kB 7.8 ms 1.5 ms 9.3 ms } } Huh? Why the difference in rotational latency? If you're reading } from one disk, on average you'll have a half track latency. For two, } on average one is half a track off from the other, so you'll have a } latency of .75 a track. With three drives, it's .875, and with four } drives, it's .9375 of a track. Things should not be quite so bleak in practice, since the drives that complete their part of any given transaction the fastest don't have to wait for the slower drives and can get started on the next transaction. Assuming a 9ms seek time, if you have N independent transactions, then the total time to complete them in the small stripe parallel case will be (N-1)*4.2ms + 7.8ms + N*9ms + N*1.5ms or 238.8ms for 16 transactions. If the transactions are small enough so that the transfer time is a small part of the total, then you are better off using larger stripes so that each transaction only involves one spindle, so that you can be servicing four transactions in parallel. ceiling(N/4) * (4.2ms + 9ms + 6ms) or 76.8ms for 16 transactions. While your calculations show that using a 15kB stripe size wins slightly in terms of the latency of one 60kB transaction, it looks to me like this actually loses if you have multiple transactions and add in the seek time. For large transactions, the average transfer rate drops because of the time wasted by head switching and track to track seeks. At some point, make the transfer time will dominate, and if you don't have many transactions that can be done in parallel it makes sense to choose a stripe size so that all the drives are running in parallel on a given transaction. If you're doing 1MB transactions, then it will take more than 100ms just for the transfer time in the single drive case, but about 25ms for the case where you've got four drives processing this transaction in parallel. Since this difference is much greater than the differences in the rotational latency between these two cases, using a stripe size less than one fourth the size of the transaction is the winning strategy. I suspect it would be optimal if the stripes corresponded to disk tracks, but since modern drives have track lengths that vary between cylinders, this is pretty impractical. I suspect that most common system workloads fall into the small transaction category, so the stripe size should be chosen large enough so that it is not common for a transaction to be split across multiple drives. This maximizes the number of transactions that can be processed in parallel. The only problem with using stripe sizes that are very large is that there may be periods of time where a particular part of a filesystem gets heavy use and this would all be directed to one drive while the others sat idle. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 01:12:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11930 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 01:12:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Tandem.com (suntan.tandem.com [192.216.221.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11925; Fri, 13 Nov 1998 01:12:34 -0800 (PST) (envelope-from grefen@hrriss.hprc.tandem.com) Received: from hrriss.hprc.tandem.com (hrriss.hprc.tandem.com [168.87.28.181]) by Tandem.com (8.8.8/2.0.1) with ESMTP id BAA07903; Fri, 13 Nov 1998 01:11:55 -0800 (PST) Received: from hrriss.hprc.tandem.com (localhost [127.0.0.1]) by hrriss.hprc.tandem.com (8.8.8/8.7.3) with ESMTP id KAA02982; Fri, 13 Nov 1998 10:16:01 +0100 (CET) To: Chuck Robey Cc: Artur Grabowski , Tech1 , hackers@FreeBSD.ORG, isp@FreeBSD.ORG, tech@openbsd.org, tech-kern@netbsd.org Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes Reply-To: grefen@hprc.tandem.com In-reply-to: Chuck Robey's message of Thu, 12 Nov 98 21:41:36 EST. References: Date: Fri, 13 Nov 1998 10:16:00 +0100 Message-ID: <2980.910948560@hrriss.hprc.tandem.com> From: Stefan Grefen Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Chuck Robey wrote: > On 13 Nov 1998, Artur Grabowski wrote: > > > "Tech1" writes: > > > > > The cost of this software is $350 but open for bargin. For more than 10M $ > > > company it's another price. If anyone working as consultant for companies. > > > You may resell this software to them. > > > > Or you can get almost the same thing for free from http://www.eddieware.org/ > > With source code. (Yes, I know it still doesn't run on *BSD, but that's a > > matter of weeks until that code is released). > > The guy's trying to make a living, and you're not. You don't know the > quality of either piece of software yet, but attitudes like that are a > big reason that free software isn't more highly catered to by commercial > companies. I think for making a living its to low a price, this stuff doesn't ship like hamburgers (or gif viewers ...). In this installations the money is made from the consulting they need, and the cost of the software is marginal, even if he charges 10 times as much. So the race against eddie is open. On the other hand for personal use and playing around $350 is to much, so eddie will run on more machines. > > If you want native versions of things like WordPerfect, then reconsider > making posts like this. WordPerfect is an example where the money is made by selling the product. Ever wondered why Cygnus doesn't make spreadsheets or wordprocessors ?? Stefan > > > > > //art > > -- Stefan Grefen Tandem Computers Europe Inc. grefen@hprc.tandem.com High Performance Research Center --- Hacking's just another word for nothing left to kludge. --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 01:33:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13874 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 01:33:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA13760 for ; Fri, 13 Nov 1998 01:30:46 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id HAA11473; Fri, 13 Nov 1998 07:50:04 +0100 From: Luigi Rizzo Message-Id: <199811130650.HAA11473@labinfo.iet.unipi.it> Subject: Re: pnp/booting problem with new kernel To: tom@tomqnx.com (Tom Torrance at home) Date: Fri, 13 Nov 1998 07:50:03 +0100 (MET) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Tom Torrance at home" at Nov 13, 98 02:34:20 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It appears that when a new kernel is installed, the effects of the last > pnp statement issued are lost. correct. They are stored in the current kernel with "dset". If you want something persistent you have to put the commands below in /kernel.config and use option USERCONFIG_BOOT (the first line of /kernel.config should be "USERCONFIG" , the last one "quit" cheers luigi > When I initially booted this kernel, I did: > pnp 1 0 enable os port0 0x220 port1 0x300 port2 0x388 irq0 10 drq0 3 drq1 5 > pnp 1 1 enable os port0 0x200 > pnp 1 2 enable os port0 0x620 port1 0xa20 port2 0xe20 > (see attachment 1 for the dmesg) > > This works fine for all subsequent boots, until after I install a new kernel. > At that time, it appears that the effects of the LAST pnp statement issued > are lost. The effects of the previously issued pnp statements are still > accurately processed (see attachment 2 for the dmesg). > > Am I misunderstanding how this should work? > > Tom > > > > --ELM910942479-25570-0_ > Content-Type: text/plain; charset=ISO-8859-1 > Content-Disposition: attachment; filename=pnp0 > Content-Description: original dmesg > Content-Transfer-Encoding: 7bit > > DMESG after pnp statements are entered: > > a fifo > ncr0: single-ended, open drain IRQ driver, using on-chip SRAM > found-> vendor=0x5333, dev=0x8a01, revid=0x01 > class=03-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=11 > map[0]: type 1, range 32, base e0000000, size 26 > vga0: rev 0x01 int a irq 11 on pci0.11.0 > Probing for PnP devices: > Trying Read_Port at 203 > Trying Read_Port at 243 > PnP: CSN 1 COMP_DEVICE_ID = 0x2fb0d041 > CSN 1 Vendor ID: CTL00c1 [0xc1008c0e] Serial 0x1641e094 Comp ID: PNPb02f [0x2fb0d041] > PnP: override config for CSN 1 LDN 0 vend_id 0xc1008c0e > port 0x0220 0x0300 0x0388 0x0000 irq 10:0 drq 3:5 en 1 > PnP: override config for CSN 1 LDN 1 vend_id 0xc1008c0e > port 0x0200 0x0000 0x0000 0x0000 irq 0:0 drq 4:4 en 1 > PnP: override config for CSN 1 LDN 2 vend_id 0xc1008c0e > port 0x0620 0x0000 0x0000 0x0000 irq 0:0 drq 4:4 en 1 > Called nullpnp_probe with tag 0x00000001, type 0xc1008c0e > Called nullpnp_probe with tag 0x00000001, type 0x2fb0d041 > Probing for devices on the ISA bus: > video: RTC equip. code:0x0f, DCC code:0x09 > video: CRTC:0x3d4, video option:0x60, rows:80, cols:25, font height:16 > video: param table EGA/VGA:0xf00c4644, CGA/MDA:0 > video: rows_offset:1 > video#0: adapter type:VGA (5), flags:0x7f, CRTC:0x3d4 > video#0: init mode:24, bios mode:3, current mode:24 > video#0: window:0xf00b8000 size:32k gran:32k, buf:0xf0000000 size:0k > video#0: mode:0, flags:0x1 T 40x25, font:8x8, win:0xb8000 > video#0: mode:1, flags:0x1 T 40x25, font:8x8, win:0xb8000 > video#0: mode:2, flags:0x1 T 80x25, font:8x8, win:0xb8000 > video#0: mode:3, flags:0x1 T 80x25, font:8x8, win:0xb8000 > video#0: mode:19, flags:0x1 T 40x25, font:8x14, win:0xb8000 > video#0: mode:20, flags:0x1 T 40x25, font:8x14, win:0xb8000 > video#0: mode:21, flags:0x1 T 80x25, font:8x14, win:0xb8000 > video#0: mode:22, flags:0x1 T 80x25, font:8x14, win:0xb8000 > video#0: mode:23, flags:0x1 T 40x25, font:8x16, win:0xb8000 > video#0: mode:25, flags:0x0 T 80x25, font:8x16, win:0xb0000 > video#0: mode:24, flags:0x1 T 80x25, font:8x16, win:0xb8000 > video#0: mode:7, flags:0x0 T 80x25, font:8x14, win:0xb0000 > video#0: mode:112, flags:0x1 T 80x43, font:8x8, win:0xb8000 > video#0: mode:113, flags:0x1 T 80x43, font:8x8, win:0xb8000 > video#0: mode:33, flags:0x0 T 80x30, font:8x16, win:0xb0000 > video#0: mode:32, flags:0x1 T 80x30, font:8x16, win:0xb8000 > video#0: mode:31, flags:0x0 T 80x50, font:8x8, win:0xb0000 > video#0: mode:30, flags:0x1 T 80x50, font:8x8, win:0xb8000 > video#0: mode:35, flags:0x0 T 80x60, font:8x8, win:0xb0000 > video#0: mode:34, flags:0x1 T 80x60, font:8x8, win:0xb8000 > video#0: mode:4, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 > video#0: mode:5, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 > video#0: mode:6, flags:0x3 G 640x200x1, 1 plane(s), font:8x8, win:0xb8000 > video#0: mode:13, flags:0x3 G 320x200x4, 4 plane(s), font:8x8, win:0xa0000 > video#0: mode:14, flags:0x3 G 640x200x4, 4 plane(s), font:8x8, win:0xa0000 > video#0: mode:15, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 > video#0: mode:17, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 > video#0: mode:16, flags:0x3 G 640x350x2, 2 plane(s), font:8x14, win:0xa0000 > video#0: mode:18, flags:0x3 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 > video#0: mode:26, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 > video#0: mode:27, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 > video#0: mode:28, flags:0x3 G 320x200x8, 1 plane(s), font:8x8, win:0xa0000 > video#0: mode:37, flags:0x3 G 320x240x8, 1 plane(s), font:8x8, win:0xa0000 > 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 0e 0f 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: the current keyboard controller command byte 0047 > kbdio: DIAGNOSE status:0055 > kbdio: TEST_KBD_PORT status:0000 > kbdio: RESET_KBD return code:00fa > kbdio: RESET_KBD status:00aa > sc0: keyboard device ID: ab41 > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0> > sio0: irq maps: 0x401 0x411 0x401 0x401 > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 16550A > lpt0 at 0x378-0x37f irq 7 on isa > lpt0: Interrupt-driven port > lp0: TCP/IP capable interface > bpf: lp0 attached > psm0: current command byte:0047 > kbdio: TEST_AUX_PORT status:0000 > kbdio: RESET_AUX return code:00fa > kbdio: RESET_AUX status:00aa > kbdio: 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: data 08 00 00 > psm: status 00 02 64 > psm0 at 0x60-0x64 irq 12 on motherboard > psm0: model Generic PS/2 mouse, device ID 0, 2 buttons > psm0: config:00000000, flags:00000000, packet size:3 > psm0: syncmask:c0, syncbits:00 > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0): > wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S > wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 > wdc1 at 0x170-0x177 irq 15 on isa > wdc1: unit 0 (atapi): , removable, intr, iordy > wcd0: 689KB/sec, 256KB cache, audio play, 255 volume levels, ejectable tray > wcd0: 120mm audio disc loaded, unlocked > 1 3C5x9 board(s) on ISA found at 0x210 > ep0 at 0x210-0x21f irq 5 on isa > ep0: aui/bnc[*BNC*] address 00:60:8c:62:a5:65 > bpf: ep0 attached > sb0 at 0x220 irq 10 drq 3 on isa > snd0: > sbxvi0 at ? drq 5 on isa > snd0: > sbmidi0 at 0x300 on isa > snd0: > awe0 at 0x620 on isa > awe0: > opl0 at 0x388 on isa > snd0: > joy0 at 0x200 on isa > joy0: joystick > npx0 on motherboard > npx0: INT 16 interface > i586_bzero() bandwidth = 175654312 bytes/sec > bzero() bandwidth = 88409512 bytes/sec > imasks: bio c008c040, tty c0031092, net c0060020 > BIOS Geometries: > 0:020afe3f 0..522=523 cylinders, 0..254=255 heads, 1..63=63 sectors > 1:03fd893f 0..1021=1022 cylinders, 0..137=138 heads, 1..63=63 sectors > 0 accounted for > Device configuration finished. > Intel Pentium F00F detected, installing workaround > bpf: tun0 attached > bpf: tun1 attached > bpf: tun2 attached > bpf: tun3 attached > bpf: lo0 attached > Waiting 15 seconds for SCSI devices to settle > ncr0: restart (scsi reset). > (probe5:ncr0:0:5:0): INQUIRY. CDB: 12 1 80 0 ff 0 > (probe5:ncr0:0:5:0): ILLEGAL REQUEST asc:24,0 > (probe5:ncr0:0:5:0): Invalid field in CDB sks:c0,1 > pass0 at ncr0 bus 0 target 0 lun 0 > pass0: Fixed Direct Access SCSI2 device > pass0: Serial Number JKA5580002KB3M > pass0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled > pass1 at ncr0 bus 0 target 5 lun 0 > pass1: Removable CD-ROM SCSI2 device > pass1: 3.300MB/s transfers > da0 at ncr0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI2 device > da0: Serial Number JKA5580002KB3M > da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled > da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) > cd0 at ncr0 bus 0 target 5 lun 0 > cd0: Removable CD-ROM SCSI2 device > cd0: 3.300MB/s transfers > cd0: cd present [327689 x 2048 byte records] > Considering FFS root f/s. > changing root device to da0s1a > da0s1: type 0xa5, start 63, end = 8885267, size 8885205 : OK > wd0s1: type 0xb, start 63, end = 6152894, size 6152832 : OK > wd0s2: type 0x5, start 6152895, end = 8385929, size 2233035 : OK > wd0s5: type 0xb, start 6152958, end = 8385929, size 2232972 : OK > ffs_mountfs: superblock updated for soft updates > Linux-ELF exec handler installed > > --ELM910942479-25570-0_ > Content-Type: text/plain; charset=ISO-8859-1 > Content-Disposition: attachment; filename=pnp1 > Content-Description: dmesg after installing new kernel > Content-Transfer-Encoding: 7bit > > DMESG after new kernel installed: > > ebus=0 secondarybus=0 > intpin=a, irq=9 > map[0]: type 4, range 32, base 0000d400, size 8 > map[1]: type 1, range 32, base e7000000, size 8 > map[2]: type 1, range 32, base e6800000, size 12 > ncr0: rev 0x03 int a irq 9 on pci0.10.0 > ncr0: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo > ncr0: single-ended, open drain IRQ driver, using on-chip SRAM > found-> vendor=0x5333, dev=0x8a01, revid=0x01 > class=03-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=11 > map[0]: type 1, range 32, base e0000000, size 26 > vga0: rev 0x01 int a irq 11 on pci0.11.0 > Initializing PnP override table > Probing for PnP devices: > Trying Read_Port at 203 > Trying Read_Port at 243 > PnP: CSN 1 COMP_DEVICE_ID = 0x2fb0d041 > CSN 1 Vendor ID: CTL00c1 [0xc1008c0e] Serial 0x1641e094 Comp ID: PNPb02f [0x2fb0d041] > Called nullpnp_probe with tag 0x00000001, type 0xc1008c0e > Called nullpnp_probe with tag 0x00000001, type 0x2fb0d041 > Probing for devices on the ISA bus: > video: RTC equip. code:0x0f, DCC code:0x09 > video: CRTC:0x3d4, video option:0x60, rows:80, cols:25, font height:16 > video: param table EGA/VGA:0xf00c4644, CGA/MDA:0 > video: rows_offset:1 > video#0: adapter type:VGA (5), flags:0x7f, CRTC:0x3d4 > video#0: init mode:24, bios mode:3, current mode:24 > video#0: window:0xf00b8000 size:32k gran:32k, buf:0xf0000000 size:0k > video#0: mode:0, flags:0x1 T 40x25, font:8x8, win:0xb8000 > video#0: mode:1, flags:0x1 T 40x25, font:8x8, win:0xb8000 > video#0: mode:2, flags:0x1 T 80x25, font:8x8, win:0xb8000 > video#0: mode:3, flags:0x1 T 80x25, font:8x8, win:0xb8000 > video#0: mode:19, flags:0x1 T 40x25, font:8x14, win:0xb8000 > video#0: mode:20, flags:0x1 T 40x25, font:8x14, win:0xb8000 > video#0: mode:21, flags:0x1 T 80x25, font:8x14, win:0xb8000 > video#0: mode:22, flags:0x1 T 80x25, font:8x14, win:0xb8000 > video#0: mode:23, flags:0x1 T 40x25, font:8x16, win:0xb8000 > video#0: mode:25, flags:0x0 T 80x25, font:8x16, win:0xb0000 > video#0: mode:24, flags:0x1 T 80x25, font:8x16, win:0xb8000 > video#0: mode:7, flags:0x0 T 80x25, font:8x14, win:0xb0000 > video#0: mode:112, flags:0x1 T 80x43, font:8x8, win:0xb8000 > video#0: mode:113, flags:0x1 T 80x43, font:8x8, win:0xb8000 > video#0: mode:33, flags:0x0 T 80x30, font:8x16, win:0xb0000 > video#0: mode:32, flags:0x1 T 80x30, font:8x16, win:0xb8000 > video#0: mode:31, flags:0x0 T 80x50, font:8x8, win:0xb0000 > video#0: mode:30, flags:0x1 T 80x50, font:8x8, win:0xb8000 > video#0: mode:35, flags:0x0 T 80x60, font:8x8, win:0xb0000 > video#0: mode:34, flags:0x1 T 80x60, font:8x8, win:0xb8000 > video#0: mode:4, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 > video#0: mode:5, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 > video#0: mode:6, flags:0x3 G 640x200x1, 1 plane(s), font:8x8, win:0xb8000 > video#0: mode:13, flags:0x3 G 320x200x4, 4 plane(s), font:8x8, win:0xa0000 > video#0: mode:14, flags:0x3 G 640x200x4, 4 plane(s), font:8x8, win:0xa0000 > video#0: mode:15, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 > video#0: mode:17, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 > video#0: mode:16, flags:0x3 G 640x350x2, 2 plane(s), font:8x14, win:0xa0000 > video#0: mode:18, flags:0x3 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 > video#0: mode:26, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 > video#0: mode:27, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 > video#0: mode:28, flags:0x3 G 320x200x8, 1 plane(s), font:8x8, win:0xa0000 > video#0: mode:37, flags:0x3 G 320x240x8, 1 plane(s), font:8x8, win:0xa0000 > 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 0e 0f 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: the current keyboard controller command byte 0047 > kbdio: DIAGNOSE status:0055 > kbdio: TEST_KBD_PORT status:0000 > kbdio: RESET_KBD return code:00fa > kbdio: RESET_KBD status:00aa > sc0: keyboard device ID: ab41 > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0> > sio0: irq maps: 0x1 0x11 0x1 0x1 > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 16550A > lpt0 at 0x378-0x37f irq 7 on isa > lpt0: Interrupt-driven port > lp0: TCP/IP capable interface > bpf: lp0 attached > psm0: current command byte:0047 > kbdio: TEST_AUX_PORT status:0000 > kbdio: RESET_AUX return code:00fa > kbdio: RESET_AUX status:00aa > kbdio: 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: data 08 00 00 > psm: status 00 02 64 > psm0 at 0x60-0x64 irq 12 on motherboard > psm0: model Generic PS/2 mouse, device ID 0, 2 buttons > psm0: config:00000000, flags:00000000, packet size:3 > psm0: syncmask:c0, syncbits:00 > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0): > wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S > wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 > wdc1 at 0x170-0x177 irq 15 on isa > wdc1: unit 0 (atapi): , removable, intr, iordy > wcd0: 689KB/sec, 256KB cache, audio play, 255 volume levels, ejectable tray > wcd0: 120mm audio disc loaded, unlocked > 1 3C5x9 board(s) on ISA found at 0x210 > ep0 at 0x210-0x21f irq 5 on isa > ep0: aui/bnc[*BNC*] address 00:60:8c:62:a5:65 > bpf: ep0 attached > sb0 at 0x220 irq 10 drq 3 on isa > snd0: > sbxvi0 at ? drq 5 on isa > snd0: > sbmidi0 at 0x300 on isa > snd0: > awe0 at 0x620 on isa > AWE32: not detected > > opl0 at 0x388 on isa > snd0: > joy0 at 0x200 on isa > joy0: joystick > npx0 on motherboard > npx0: INT 16 interface > i586_bzero() bandwidth = 175654312 bytes/sec > bzero() bandwidth = 88409512 bytes/sec > imasks: bio c008c040, tty c0031092, net c0060020 > BIOS Geometries: > 0:020afe3f 0..522=523 cylinders, 0..254=255 heads, 1..63=63 sectors > 1:03fd893f 0..1021=1022 cylinders, 0..137=138 heads, 1..63=63 sectors > 0 accounted for > Device configuration finished. > Intel Pentium F00F detected, installing workaround > bpf: tun0 attached > bpf: tun1 attached > bpf: tun2 attached > bpf: tun3 attached > bpf: lo0 attached > Waiting 15 seconds for SCSI devices to settle > ncr0: restart (scsi reset). > (probe5:ncr0:0:5:0): INQUIRY. CDB: 12 1 80 0 ff 0 > (probe5:ncr0:0:5:0): ILLEGAL REQUEST asc:24,0 > (probe5:ncr0:0:5:0): Invalid field in CDB sks:c0,1 > pass0 at ncr0 bus 0 target 0 lun 0 > pass0: Fixed Direct Access SCSI2 device > pass0: Serial Number JKA5580002KB3M > pass0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled > pass1 at ncr0 bus 0 target 5 lun 0 > pass1: Removable CD-ROM SCSI2 device > pass1: 3.300MB/s transfers > da0 at ncr0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI2 device > da0: Serial Number JKA5580002KB3M > da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled > da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) > cd0 at ncr0 bus 0 target 5 lun 0 > cd0: Removable CD-ROM SCSI2 device > cd0: 3.300MB/s transfers > cd0: cd present [327689 x 2048 byte records] > Considering FFS root f/s. > changing root device to da0s1a > da0s1: type 0xa5, start 63, end = 8885267, size 8885205 : OK > wd0s1: type 0xb, start 63, end = 6152894, size 6152832 : OK > wd0s2: type 0x5, start 6152895, end = 8385929, size 2233035 : OK > wd0s5: type 0xb, start 6152958, end = 8385929, size 2232972 : OK > ffs_mountfs: superblock updated for soft updates > Linux-ELF exec handler installed > > --ELM910942479-25570-0_-- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 01:51:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15683 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 01:51:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from attach1.rocketmail.com (attach1.rocketmail.com [205.180.57.81]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA15678 for ; Fri, 13 Nov 1998 01:50:59 -0800 (PST) (envelope-from melvynlingham@rocketmail.com) Message-ID: <19981113094526.5745.rocketmail@attach1.rocketmail.com> Received: from [204.123.2.83] by attach1; Fri, 13 Nov 1998 01:45:26 PST Date: Fri, 13 Nov 1998 01:45:26 -0800 (PST) From: Melvyn Lingham Subject: Re: Welcome to Pornmail! Reply to confirm! To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ***** YOU MUST REPLY TO THIS EMAIL TO START PORNMAIL ****** > > This is your reply from Pornmail.com! You must now hit > REPLY on your email program to send this message back to > us, and let us know we have your correct address. Please > note that this is the ONLY way to ensure your subscription > proceeds. If you send an email to us ANY other way, it > will NOT get you subscribed to the mailing list. > > Pornmail.com! *FREE porn in your email!* > > Note: due to a software glitch, this email may have been a > few days late. We apologize for any inconvenience. > > *********************************************************** > > Note: this is not a spam email. This email was sent to you > because your email was entered in on a website requesting > to be registered for the PornMail.com adult newsletter. If > you did not request this email, please send a reply message > with the word "ban" in the subject field. This will ensure > that you will *never* receive another email from us! :) > > *********************************************************** > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 01:51:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15864 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 01:51:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from findmail.com (m6.findmail.com [209.185.96.140]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA15858 for ; Fri, 13 Nov 1998 01:51:17 -0800 (PST) (envelope-from melvynlingham@rocketmail.com) Received: (qmail 16594 invoked by uid 505); 13 Nov 1998 09:51:36 -0000 Date: 13 Nov 1998 09:51:36 -0000 Message-ID: <19981113095136.16593.qmail@findmail.com> Received: from 204.123.2.106 (via http) from to list "freebsd-hackers" From: "Melvyn Cedric Lingham" Subject: Re: Welcome to Pornmail! Reply to confirm! In-Reply-To: <199803242230.OAA07455@pornmail.com> To: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ***** YOU MUST REPLY TO THIS EMAIL TO START PORNMAIL ****** > > This is your reply from Pornmail.com! You must now hit > REPLY on your email program to send this message back to > us, and let us know we have your correct address. Please > note that this is the ONLY way to ensure your subscription > proceeds. If you send an email to us ANY other way, it > will NOT get you subscribed to the mailing list. > > Pornmail.com! *FREE porn in your email!* > > Note: due to a software glitch, this email may have been a > few days late. We apologize for any inconvenience. > > *********************************************************** > > Note: this is not a spam email. This email was sent to you > because your email was entered in on a website requesting > to be registered for the PornMail.com adult newsletter. If > you did not request this email, please send a reply message > with the word "ban" in the subject field. This will ensure > that you will *never* receive another email from us! :) > > *********************************************************** > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ----- See the original message at http://www.egroups.com/list/freebsd-hackers/?start=23397 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 02:17:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA18212 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 02:17:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zappa.demon.nl (zappa.demon.nl [195.173.232.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA18207 for ; Fri, 13 Nov 1998 02:17:24 -0800 (PST) (envelope-from root@zappa.demon.nl) Received: (from root@localhost) by zappa.demon.nl (8.9.1/8.8.8) id LAA02088 for freebsd-hackers@freebsd.org; Fri, 13 Nov 1998 11:18:28 +0100 (CET) (envelope-from root) Message-ID: <19981113111828.A1539@zappa.demon.nl> Date: Fri, 13 Nov 1998 11:18:28 +0100 From: Ron Klinkien To: freebsd-hackers@FreeBSD.ORG Subject: Re: i2c projects References: <19981109211837.A4702@zappa.demon.nl> <19981113001748.14820@breizh.prism.uvsq.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981113001748.14820@breizh.prism.uvsq.fr>; from Nicolas Souchu on Fri, Nov 13, 1998 at 12:17:48AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, On Fri, Nov 13, 1998 at 12:17:48AM +0000, Nicolas Souchu wrote: > >I want to build a weather station / home automation project using a FreeBSD running pc, > >and the i2c bus on my video capture card. > > Cool. FreeBSD is the good choice. Yes, it's great for almost anything ;-) > > Yes, this is lacking. Waiting for a MAKEDEV update, try: > > mknod iic0 c 105 0 > mknod smb0 c 106 0 Ah thanks, > >Which major/minor numbers to use etc...? > > You would have found them in the related drivers: I also spotted them in majors.i386 as it should. > > iicbus is a powerfull framework that should bring you all what you need with > only few indications about how to use it. Thats what i'm looking for no worries about timing etc... > Now, you want to write user/kernel code? If you need kernel code which is > uncertain, /sys/dev/iicbus/iic.c will be a good start. Read, copy and > modify it as needed. No just a normal user code program will do for starters. The drivers in the kernel seems to work: -- cut --- bktr0: rev 0x12 int a irq 10 on pci0.9.0 bti2c0: iicbb0: on bti2c0 iicbus0: on iicbb0 master-only Probing for devices on iicbus0: smbus0: on bti2c0 Miro TV, Temic PAL tuner. --- cut --- > { "iic", IICBUS_DEVICE_CLASS, "PCF8574 I2C to 8 bits parallel i/o", 64}, Hmm i happen to have this one... waiting to be soldered onto my experiment board ;-) > Nicolas. > > -- Thanks for your help so far.. Ron. -- --- Running Solaris/SPARC at work, enjoying FreeBSD/PII at home. Ron Klinkien System Engineer ron@zappa.demon.nl http://www.zappa.demon.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 06:42:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13760 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 06:42:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from send105.yahoomail.com (send105.yahoomail.com [205.180.60.128]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA13755 for ; Fri, 13 Nov 1998 06:42:43 -0800 (PST) (envelope-from sidliu@yahoo.com) Message-ID: <19981113144438.5977.rocketmail@send105.yahoomail.com> Received: from [166.55.244.226] by send105.yahoomail.com; Fri, 13 Nov 1998 06:44:38 PST Date: Fri, 13 Nov 1998 06:44:38 -0800 (PST) From: Sid Liu Subject: unsubscribe hackers To: hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe hackers _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 07:24:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19373 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 07:24:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from jekyll.piermont.com (jekyll.piermont.com [206.1.51.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19353; Fri, 13 Nov 1998 07:24:05 -0800 (PST) (envelope-from perry@jekyll.piermont.com) Received: from jekyll (localhost [[UNIX: localhost]]) by jekyll.piermont.com (8.8.8/8.6.12) with ESMTP id KAA00189; Fri, 13 Nov 1998 10:22:51 -0500 (EST) Message-Id: <199811131522.KAA00189@jekyll.piermont.com> To: Chuck Robey cc: Artur Grabowski , Tech1 , hackers@FreeBSD.ORG, isp@FreeBSD.ORG, tech@openbsd.org, tech-kern@netbsd.org Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes In-reply-to: Your message of "Thu, 12 Nov 1998 21:41:36 EST." Reply-To: perry@piermont.com X-Reposting-Policy: redistribute only with permission Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Fri, 13 Nov 1998 10:22:51 -0500 From: "Perry E. Metzger" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey writes: > > Or you can get almost the same thing for free from http://www.eddieware.org [...] > The guy's trying to make a living, and you're not. So? Why does that give you a reason to be deferential? The world doesn't *owe* him a living... .pm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 07:30:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20489 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 07:30:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA20474 for ; Fri, 13 Nov 1998 07:30:06 -0800 (PST) (envelope-from vev@michvhf.com) Received: (qmail 9199 invoked by uid 1000); 13 Nov 1998 15:30:11 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 13 Nov 1998 10:30:11 -0500 (EST) X-Face: *0^4Iw) To: The Hermit Hacker Subject: Applixware was Re: Detailed info on Fail-safe cluster for Freebsd/unixes Cc: Joe Shevland , hackers@FreeBSD.ORG, "Jordan K.Hubbard" , "Daniel O'Connor" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Nov-98 The Hermit Hacker wrote: > On Fri, 13 Nov 1998, Daniel O'Connor wrote: > >> On 13-Nov-98 Jordan K. Hubbard wrote: >> > I wonder at all of this focus on StarOffice, however. Is Applixware >> > 4.1 just considered an evil alternative, or what? As most folks know >> > (those who have visited www.cdrom.com at any point in the last 2 >> > months, anyway), Walnut Creek CDROM licensed Applixware and has a >> > project going to port it to FreeBSD. We can't get all possible ISVs >> > to play ball, but we can at least start with one. If folks are keen >> > to see this then by all means demonstrate your support by advance >> > ordering a copy of Applixware from http://www.cdrom.com - you won't >> > actually get charged for it until the product has been shipped to you. >> >> Is there anyway I can get an Applixware demo? >> Kinda don't want to fork the $$ out without seeing what its like :) > > SO5.0 supports up to Word97...Applixware supports up to Word6 > (please don't tell me they are one in the same? *sigh*) ... Looks like Marc did the same thing I did at first. I went straight for the Applixware info. After Jordan posted the linux URL (that was also in the cdrom.com blurb) I looked again and found some updated info. It imports (without a mention of an optional filter like in the other applixware info) MSWord thru 97, XL thru 97, PowerPoint, etc. It appears to handle MSOffice97 stuff without the need of optional filters. The only drawback that I see (which probably won't matter for most other folks) is the lack of IMAP support in the mail client. For me it's a minimum requirement for a mail application. But since that's just a small piece of the app, XFMail isn't giving me any trouble, and the need for a good, stable, non-emulated office suite I'll probably pre-order it. BTW, from the linux URL, there are screenshots. It doesn't look that bad, either. On the subject of lobbying ISVs, for a few months now (since the new GPIB driver appeared) I've been lobbying National Instruments to do a FreeBSD port of LabView. They already have a version for HP-UX... Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Searchable Campground Listings http://www.camping-usa.com "There is no outfit less entitled to lecture me about bloat than the federal government" -- Tony Snow ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 07:54:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22574 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 07:54:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22568 for ; Fri, 13 Nov 1998 07:54:01 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from heptifili.ifi.uio.no (2602@heptifili.ifi.uio.no [129.240.65.12]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with SMTP id QAA06715; Fri, 13 Nov 1998 16:53:36 +0100 (MET) Received: from localhost (dag-erli@localhost) by heptifili.ifi.uio.no ; Fri, 13 Nov 1998 15:53:34 GMT Mime-Version: 1.0 To: Jan Conrad Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/rc: mount -v -a -t nfs References: Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 13 Nov 1998 16:53:26 +0100 In-Reply-To: Jan Conrad's message of "Thu, 12 Nov 1998 11:47:31 +0100 (CET)" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id HAA22570 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jan Conrad writes: > I have a small suggestion concerning the /etc/rc script. I find it pretty > annoying that the nfs mounts are done *WITHOUT* verbose mode. man fstab. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 07:59:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22994 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 07:59:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22989 for ; Fri, 13 Nov 1998 07:59:35 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id HAA03306 for hackers@FreeBSD.ORG; Fri, 13 Nov 1998 07:57:08 -0800 (PST) (envelope-from dhw) Date: Fri, 13 Nov 1998 07:57:08 -0800 (PST) From: David Wolfskill Message-Id: <199811131557.HAA03306@pau-amma.whistle.com> To: hackers@FreeBSD.ORG Subject: Re: dump(8) very slow In-Reply-To: <98Nov13.154625est.40323@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Fri, 13 Nov 1998 15:46:51 +1100 >From: Peter Jeremy >... >Unfortunately, dump(8) is distinctly sub-optimal as far as reading the >disk is concerned..... >... >Is this approach worth the effort? I suspect this depends on how well >associated sequential blocks of inodes correlate to associated groups >of data blocks on disk - I don't know the answer to this. >... Well, what I do, in large part to deal with this, is have amanda run dump for me. (At work. At home, I let dump write directly to tape, but so far, I'm nowhere near the point of needing the performance gains, and I'm unwilling to use a separate tape cartridge for each day's backups.) One of the things that amanda will do (given a chance) is send dump's output to a pipeline (that may involve compressing the image and/or sending it to a different machine, which has a tape drive), and thence to a "holding disk" -- which basically acts as a largish speed-matching buffer. Thus, it allows multiple dump processes to be running at the same time; as soon as a dump image is finished, that image is queued for a separate process to write it to tape. This de-coupling of the reading that dump does, vs. the writing to tape, allows for significant speed-ups (among other things). So I'd be hard-pressed to think that the effort you describe is likely to be worth it, given that amanda is free, and the concept of the de-coupling should be somewhat easier to implement than what you describe, even if you don't want to run amanda. Maybe it would be worth it for some, though.... david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 08:01:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23306 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 08:01:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lwaxana.cistron.nl (lwaxana.cistron.nl [195.64.68.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23301 for ; Fri, 13 Nov 1998 08:01:50 -0800 (PST) (envelope-from wouters@cistron.nl) Received: from localhost.localdomain (IDENT:wouter@cs4p38.dial.cistron.nl [195.64.69.231]) by lwaxana.cistron.nl (8.9.1a/8.9.1/Debian/GNU) with SMTP id RAA32337 for ; Fri, 13 Nov 1998 17:01:18 +0100 Message-ID: <364C5851.EE9245E@cistron.nl> Date: Fri, 13 Nov 1998 17:03:29 +0100 From: WHS Organization: robots anonymous X-Mailer: Mozilla 3.01 (X11; I; Linux 2.0.34 i686) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: GGI's library is now also under X style license. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG See above. I'm going to start the port of KGI (the kernel arbitration of the video hardware) to OpenBSD soon (time permitting). None of the GGI developers are currently doing a KGI-FreeBSD port (these port efforts seemed to have evaporated as I mentioned before..), so if anyone wants to take up the challenge at this time, go ahead. Btw, if you want to subscribe to the GGI list, be prepared for 50-100 mails a day. Here's the message: +++++++++++ Hi, As all LibGGI contributors have now given their permission I am now happily announcing that LibGGI can become truly free software. The license will be changed from LGPL to the following (the same that is already used for KGI) ------------------------------- begin -------------------------------------- Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHOR(S) BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ------------------------------- end ---------------------------------------- There was a debate some time ago about whether you can relicense this under (L)GPL. I can now tell you that this is really the case. But to really clear all doubts we will also explicitly allow relicensing under GPL and LGPL. So, what does this mean? For most people - nothing. If you prefer a LGPLed library just relicense LibGGI to yourself under LGPL. For the BSD people - LibGGI is now really free, and you are welcome to use and/or help us with LibGGI. It does have some implications when it comes to sharing code with other projects which are under a GNU license. The other projects can use our code just fine, but the opposite is not true. Here we have two solutions: a) The other project appreciates LibGGI so much that they allow us to incorporate parts of their code under the above MIT-style license. b) The other project doesn't care or know about LibGGI, or are GNU fanatics. In this case we can still use use their code, but it has to be distributed separately from the MIT-style code. (Note that nothing stops anyone from merging it together and distribute the whole resulting thing under GPL or LGPL) LibGG, LibGII and the SVGAlib wrapper will also use the above license. As for LibGWT, and LibGGI2D and LibGGI3D we have some additional contributors who's position in this question is not known to me at this point, but I hope that we can make those libraries really free too. Now, there's only one small problem left - how do we change the license notices of all files with the least work? ;) Can sed handle replacing blocks of multiple lines? //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se +++++++++++ Wouter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 08:02:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23499 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 08:02:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA23483 for ; Fri, 13 Nov 1998 08:02:50 -0800 (PST) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id KAA21131; Fri, 13 Nov 1998 10:52:35 -0500 Date: Fri, 13 Nov 1998 10:52:34 -0500 (EST) From: "Ron G. Minnich" X-Sender: rminnich@terra To: Vince Vielhaber cc: The Hermit Hacker , Joe Shevland , hackers@FreeBSD.ORG, "Jordan K.Hubbard" , "Daniel O'Connor" Subject: Re: Applixware was Re: Detailed info on Fail-safe cluster for Freebsd/unixes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry to put this on -hackers, but it seems to be stuck here. You can believe the ad or you can try it. We've tried both so 5.0 and the latest applixware, and they both don't work about equally well. That is, they can read in trivial ms office files but they fail in bad ways on anything we care about. so 5.0 crashes and burns and exits and dies if it hits something it can't read. applixware just says "I can't do that" -- often. Applixware can't even handle word fast-save files, which are the most common kind out there. Note that mswordview, a freeware program, does handle fast-saved files ... This is the second time I've paid money for applixware and been burned, so I am of course somewhat less than a satisfied customer :-) Don't assume you can use either of these tools to interoperate with ms office. You can't. In terms of how luck you'll be: excel: probably works, most of the time word: works if it is text only most of the time, fails badly on anything useful powerpoint: forget it on applixware, have not tried it on so 5.0 Good luck. ron Ron Minnich |"Using Windows NT, which is known to have some rminnich@sarnoff.com | failure modes, on a warship is similar to hoping (609)-734-3120 | that luck will be in our favor"- A. Digiorgio ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 08:08:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24335 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 08:08:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24329 for ; Fri, 13 Nov 1998 08:08:06 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id RAA13520; Fri, 13 Nov 1998 17:07:34 +0100 (MET) Date: Fri, 13 Nov 1998 17:07:31 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: dag-erli@ifi.uio.no cc: Jan Conrad , freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/rc: mount -v -a -t nfs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id IAA24330 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Or rather: Change the appropriate line to mount -v -a -t nfs Nick On 13 Nov 1998 dag-erli@ifi.uio.no wrote: > Jan Conrad writes: > > I have a small suggestion concerning the /etc/rc script. I find it pretty > > annoying that the nfs mounts are done *WITHOUT* verbose mode. > > man fstab. > > DES > -- > Dag-Erling Smørgrav - dag-erli@ifi.uio.no > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 08:24:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26590 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 08:24:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dragon.ham.muohio.edu (dragon.ham.muohio.edu [134.53.147.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26517 for ; Fri, 13 Nov 1998 08:24:03 -0800 (PST) (envelope-from howardjp@dragon.ham.muohio.edu) Received: from localhost (howardjp@localhost) by dragon.ham.muohio.edu (8.8.5/8.8.5) with SMTP id LAA16214 for ; Fri, 13 Nov 1998 11:23:43 -0500 Date: Fri, 13 Nov 1998 11:23:43 -0500 (EST) From: Jamie Howard To: freebsd-hackers@FreeBSD.ORG Subject: /compat/linux Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running 3.0-RELEASE abd I found this nifty directory, /compat/linux (which I know is just a link to /usr/compat/linux). I was looking for the source to this branch of the tree but cannot find it. Can someone point me in the right direction? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 08:27:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27242 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 08:27:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tnc.com (tnc.com [139.142.36.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27237 for ; Fri, 13 Nov 1998 08:27:12 -0800 (PST) (envelope-from swheeler@tnc.com) Received: from Shannon (fort10.tnc.com [139.142.38.153]) by tnc.com (8.8.5/8.8.2) with SMTP id JAA12230; Fri, 13 Nov 1998 09:26:37 -0700 (MST) From: "Shannon Wheeler" To: "Melvyn Cedric Lingham" , Subject: Re: Welcome to Pornmail! Reply to confirm! Date: Fri, 13 Nov 1998 09:17:44 -0700 Message-ID: <01be0f21$25363700$0307070a@Shannon> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey dimwit! You have to reply to the mail, not forward it to someone else altogether. -----Original Message----- From: Melvyn Cedric Lingham >***** YOU MUST REPLY TO THIS EMAIL TO START PORNMAIL ****** >> >> This is your reply from Pornmail.com! You must now hit >> REPLY on your email program to send this message back to >> us, and let us know we have your correct address. Please >> note that this is the ONLY way to ensure your subscription >> proceeds. If you send an email to us ANY other way, it >> will NOT get you subscribed to the mailing list. >> >> Pornmail.com! *FREE porn in your email!* >> >> Note: due to a software glitch, this email may have been a >> few days late. We apologize for any inconvenience. >> >> *********************************************************** >> >> Note: this is not a spam email. This email was sent to you >> because your email was entered in on a website requesting >> to be registered for the PornMail.com adult newsletter. If >> you did not request this email, please send a reply message >> with the word "ban" in the subject field. This will ensure >> that you will *never* receive another email from us! :) >> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 08:40:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29735 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 08:40:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29730 for ; Fri, 13 Nov 1998 08:40:28 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id KAA24938; Fri, 13 Nov 1998 10:39:59 -0600 (CST) Date: Fri, 13 Nov 1998 10:39:59 -0600 From: Dan Nelson To: Jamie Howard , freebsd-hackers@FreeBSD.ORG Subject: Re: /compat/linux Message-ID: <19981113103959.A24849@emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.3i In-Reply-To: ; from "Jamie Howard" on Fri Nov 13 11:23:43 GMT 1998 X-OS: FreeBSD 2.2.7-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Nov 13), Jamie Howard said: > I am running 3.0-RELEASE abd I found this nifty directory, /compat/linux > (which I know is just a link to /usr/compat/linux). I was looking for the > source to this branch of the tree but cannot find it. Can someone point > me in the right direction? The "source" to /compat/linux is probably available at redhat.com, or debian.org :) All it is is Linux binaries and libraries. I'm not sure which flavor of Linux we're trying to emulate. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 08:42:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00349 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 08:42:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00247 for ; Fri, 13 Nov 1998 08:42:09 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id LAA22064; Fri, 13 Nov 1998 11:44:49 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Fri, 13 Nov 1998 11:44:49 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Jamie Howard cc: freebsd-hackers@FreeBSD.ORG Subject: Re: /compat/linux In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cd /usr/ports/emulation/linux_lib/ make install Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Fri, 13 Nov 1998, Jamie Howard wrote: > I am running 3.0-RELEASE abd I found this nifty directory, /compat/linux > (which I know is just a link to /usr/compat/linux). I was looking for the > source to this branch of the tree but cannot find it. Can someone point > me in the right direction? > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 08:52:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01589 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 08:52:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01568 for ; Fri, 13 Nov 1998 08:52:33 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id KAA01650; Fri, 13 Nov 1998 10:51:34 -0600 (CST) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id KAA27542; Fri, 13 Nov 1998 10:51:03 -0600 Message-ID: <19981113105102.11656@right.PCS> Date: Fri, 13 Nov 1998 10:51:02 -0600 From: Jonathan Lemon To: The Hermit Hacker Cc: "Daniel O'Connor" , "Jordan K. Hubbard" , hackers@FreeBSD.ORG, Joe Shevland Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: ; from The Hermit Hacker on Nov 11, 1998 at 12:39:48AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Nov 11, 1998 at 12:39:48AM -0400, The Hermit Hacker wrote: > On Fri, 13 Nov 1998, Daniel O'Connor wrote: > > > On 13-Nov-98 Jordan K. Hubbard wrote: > > > I wonder at all of this focus on StarOffice, however. Is Applixware > > > 4.1 just considered an evil alternative, or what? As most folks know > > > (those who have visited www.cdrom.com at any point in the last 2 > > > months, anyway), Walnut Creek CDROM licensed Applixware and has a > > > project going to port it to FreeBSD. We can't get all possible ISVs > > > to play ball, but we can at least start with one. If folks are keen > > > to see this then by all means demonstrate your support by advance > > > ordering a copy of Applixware from http://www.cdrom.com - you won't > > > actually get charged for it until the product has been shipped to you. > > > > Is there anyway I can get an Applixware demo? > > Kinda don't want to fork the $$ out without seeing what its like :) > > SO5.0 supports up to Word97...Applixware supports up to Word6 > (please don't tell me they are one in the same? *sigh*) ... > > ... but, since I did open my big mouth, is there any way of > advance ordering without a credit card :( I tend to be kinda 'card poor' Same here; I'll get corporate to buy me a copy (or two), but they like to deal with purchase orders, not credit cards. I also want them to get a FBSD subscription, ran into the same problem: no CC's. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 09:05:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02472 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 09:05:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02465 for ; Fri, 13 Nov 1998 09:05:25 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from celeris (56k-port4020.ime.net [209.90.195.30]) by Loki.orland.u91.k12.me.us (8.9.1/8.8.8-Loki) with SMTP id MAA01281; Fri, 13 Nov 1998 12:04:40 -0500 (EST) (envelope-from netmonger@genesis.ispace.com) X-Server-ID: Loki.orland.u91.k12.me.us, OCSNet - Orland Maine USA X-Coord-Name: Drew "Droobie" Baxter, OneNetwork Exchange X-Coord-Addr: Droobie@Openlink.orland.me.us X-Coord-Pager: USA: 207-471-2719, http://pagedroo.orland.me.us Message-Id: <4.1.19981113120056.00990ee0@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 13 Nov 1998 12:02:18 -0500 To: "Shannon Wheeler" , "Melvyn Cedric Lingham" , From: Drew Baxter Subject: Re: Welcome to Pornmail! Reply to confirm! In-Reply-To: <01be0f21$25363700$0307070a@Shannon> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oooh pornmail.. After this, I've seen it all, and I guess if you've seen it all, your life can be terminated, am I right? I leave 30,000 lines of code to... and I wish to be buried with my FreeBSD box. My Solaris box can burn to the ground along with the NT one.. I only ask God of one thing "Don't shame me for using Windows ever in my life". At 09:17 AM 11/13/98 -0700, Shannon Wheeler wrote: >Hey dimwit! You have to reply to the mail, not forward it to someone else >altogether. > >-----Original Message----- >From: Melvyn Cedric Lingham > > >>***** YOU MUST REPLY TO THIS EMAIL TO START PORNMAIL ****** >>> >>> This is your reply from Pornmail.com! You must now hit >>> REPLY on your email program to send this message back to >>> us, and let us know we have your correct address. Please >>> note that this is the ONLY way to ensure your subscription >>> proceeds. If you send an email to us ANY other way, it >>> will NOT get you subscribed to the mailing list. >>> >>> Pornmail.com! *FREE porn in your email!* >>> >>> Note: due to a software glitch, this email may have been a >>> few days late. We apologize for any inconvenience. >>> >>> *********************************************************** >>> >>> Note: this is not a spam email. This email was sent to you >>> because your email was entered in on a website requesting >>> to be registered for the PornMail.com adult newsletter. If >>> you did not request this email, please send a reply message >>> with the word "ban" in the subject field. This will ensure >>> that you will *never* receive another email from us! :) >>> > --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange 207-942-0275 http://www.droo.orland.me.us My Latest Kernel: FreeBSD 3.0-CURRENT (ONEEX) #14: Mon Oct 19 22:36:58 EDT 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 09:15:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03297 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 09:15:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alive.znep.com (207-178-54-226.go2net.com [207.178.54.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03280 for ; Fri, 13 Nov 1998 09:15:35 -0800 (PST) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.1/8.9.1) with ESMTP id JAA25948; Fri, 13 Nov 1998 09:11:49 -0800 (PST) (envelope-from marcs@znep.com) Date: Fri, 13 Nov 1998 09:11:49 -0800 (PST) From: Marc Slemko To: David Wolfskill cc: hackers@FreeBSD.ORG Subject: Re: dump(8) very slow In-Reply-To: <199811131557.HAA03306@pau-amma.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Nov 1998, David Wolfskill wrote: > >Date: Fri, 13 Nov 1998 15:46:51 +1100 > >From: Peter Jeremy > > >... > > >Unfortunately, dump(8) is distinctly sub-optimal as far as reading the > >disk is concerned..... > > >... > > >Is this approach worth the effort? I suspect this depends on how well > >associated sequential blocks of inodes correlate to associated groups > >of data blocks on disk - I don't know the answer to this. > > >... > > Well, what I do, in large part to deal with this, is have amanda run > dump for me. (At work. At home, I let dump write directly to tape, but > so far, I'm nowhere near the point of needing the performance gains, and > I'm unwilling to use a separate tape cartridge for each day's backups.) > > One of the things that amanda will do (given a chance) is send dump's > output to a pipeline (that may involve compressing the image and/or > sending it to a different machine, which has a tape drive), and thence > to a "holding disk" -- which basically acts as a largish speed-matching > buffer. Right, or you can just pipe dump through something like "team" which will buffer it. Really, that is the biggest problem I find with dump. On many systems, it isn't that it can't read quickly enough to fill the tape it is that there isn't enough buffering to let it do so smoothly, and when the tape isn't streaming it isn't a happy camper. You do, however, lose some things like reliable end of tape detection. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 09:18:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03655 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 09:18:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles161.castles.com [208.214.165.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03647 for ; Fri, 13 Nov 1998 09:18:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA02520; Thu, 12 Nov 1998 18:36:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811130236.SAA02520@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone In-reply-to: Your message of "Fri, 13 Nov 1998 13:03:49 +1030." <19981113130349.N781@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Nov 1998 18:36:24 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If you have two drives 4.1GB and two that are 4.3GB, and you want to > > stripe them, you have to use a base size of 4.1GB and throw away 400MB. > > Either that, or you subdivide the disks into multiple partitions > > looking for the largest common submultiple. Yuck. > > That's exactly what we do, except that we don't throw away the rest: > it remains available for other plexes. 400 MB could come in handy > somewhere. You'd write: > > sd drive a length 4100m > sd drive b length 4100m > sd drive c length 4100m > sd drive d length 4100m > > What's the problem? The problem is that it's irrelevant to the matter at hand. I've just said "I want a striped volume across all of these disks". I don't want to futz around with spillage, I just want a striped volume across these disks. Sure, your config tool would put something like the above in the config file (that's what I meant by ignoring bits of the disk), but if the lossage is < 10% I wouldn't bother even emitting a warning message. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 09:21:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04103 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 09:21:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from thelab.hub.org (nat0069.mpoweredpc.net [142.177.188.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA04097 for ; Fri, 13 Nov 1998 09:21:19 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id NAA10014; Fri, 13 Nov 1998 13:20:42 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 13 Nov 1998 13:20:41 -0400 (AST) From: The Hermit Hacker To: Vince Vielhaber cc: hackers@FreeBSD.ORG Subject: Re: Applixware was Re: Detailed info on Fail-safe cluster for Freebsd/unixes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Nov 1998, Vince Vielhaber wrote: > The only drawback that I see (which probably won't matter for most other > folks) is the lack of IMAP support in the mail client. For me it's a > minimum requirement for a mail application. But since that's just a small > piece of the app, XFMail isn't giving me any trouble, and the need for a > good, stable, non-emulated office suite I'll probably pre-order it. BTW, > from the linux URL, there are screenshots. It doesn't look that bad, > either. I was going to ask where these screenshots were, but went back and looked a little bit deeper and found them... Any chance of having a 'screenshots' link a little less buried? Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 09:25:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04584 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 09:25:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA04577 for ; Fri, 13 Nov 1998 09:25:48 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id JAA05134; Fri, 13 Nov 1998 09:25:22 -0800 (PST) (envelope-from dillon) Date: Fri, 13 Nov 1998 09:25:22 -0800 (PST) From: Matthew Dillon Message-Id: <199811131725.JAA05134@apollo.backplane.com> To: Dru Nelson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: write syscall times for sockets References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi, : : I wrote a simple C program to guage how many usec's : system calls take or write calls take for various : write lengths. : : I setup a socket to the discard socket on another machine. : I did various writes. The times are in the attachment. : The first 4 writes are 0,0,8,?. After that all the writes : are in groups of 4 with a sleep(2) in between. : Ahh.. :-) I'll just include the code. : : Basically, the first system call would take longer for some : reason. Then each write would be pretty consistent. Well, amoung other things, the system must initially fault the buffer into memory, whether it's zero-page or not. : What I was looking for was that characteristic of writing : to a socket with buffer available. The call should be pretty In order to test this properly you also need to take into account the TCP window size and kernel buffering. The combination determines how much unacked data the destination is willing to accept and how much data the source is willing to buffer in the kernel. You can control the parameter somewhat on the source with a socket option SO_SNDBUF and SO_SNDLOWAT (see 'setsockopt'), you can set system-wide defaults with sysctl (sysctl -a | fgrep tcp), and you can set per-route specifics with route (e.g. route -n get default; route -n change default -sendpipe 60000, and so on). For the tests you are making, it should be sufficient to set it just on the sender's side. You might also be interested in the new sendfile() functionality just recently added by David Greenman to FreeBSD. -Matt : This is pretty much for fun... a limited test case. However, : I think the information would be interesting. : : I'm not on this list, so if you could cc: me when you reply, : that would be great. : :Dru Nelson :Redwood City, California Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 09:47:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07533 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 09:47:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07527 for ; Fri, 13 Nov 1998 09:47:29 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id JAA05198; Fri, 13 Nov 1998 09:47:03 -0800 (PST) (envelope-from dillon) Date: Fri, 13 Nov 1998 09:47:03 -0800 (PST) From: Matthew Dillon Message-Id: <199811131747.JAA05198@apollo.backplane.com> To: Marc Slemko Cc: David Wolfskill , hackers@FreeBSD.ORG Subject: Re: dump(8) very slow References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Right, or you can just pipe dump through something like "team" which will :buffer it. Really, that is the biggest problem I find with dump. On many :systems, it isn't that it can't read quickly enough to fill the tape it is :that there isn't enough buffering to let it do so smoothly, and when the :tape isn't streaming it isn't a happy camper. : :You do, however, lose some things like reliable end of tape detection. For BEST I wrote something similar to amanda (though never having used amanda I couldn't compare them beyond that). The machine I've been running all those SCSI tests on is our backup1.ba.best.com box. It's idle during the day, active at night. The backup system is separated into two parts: The first piece runs remote dumps over ssh and writes the dump files to the disk buffer, doing up to 8 dumps in parallel, and the second piece copies the dump files from the disk buffer to the two tape units. The disk buffer consists of four 9G drives striped together into a single ccd partition, using a 64 KByte stripe. Since the backups are occuring through encrypted ssh connections, the machine tends to be cpu bound rather then I/O bound. We plan to upgrade it to a FreeBSD-current duel-pentium box soon. A PPro 200 can handle around 2.5 MBytes/sec worth of ssh encrypted data and the dump's running on the remote machines cannot generally do better then 400KB/sec due to the fact that the machines are active, plus I gzip -2 the dump output on the remote machine before it comes back through the ssh pipe. Exabyte tape drives are not very space efficient if you can't stream them, hence the 36 GB 'whole dumps' disk buffer. What I like the most about the system is that if a tape unit has an error, the dumps related to that tape are simply left in the disk buffer while dumps for other tapes run merrily on their way, allowing a human to fix the problem without interrupting the dump process or having to redump a machine. If the disk buffer fills up, my frontend simply goes into a sleep-retry-loop until the backend drains it. Since these Exabytes can do 3 MBytes/sec, the disk buffer usually does not fill up. I also like the system because I do not depend on realtime pipes at all, so I can guarentee 100% streaming to two tape units. Worst case disk I/O is 3*2 + 2.5 = 8.5 MBytes/sec, well within the 30 MByte/sec bandwidth of the ccd even assuming 2x loss in efficiency from the parallelism). And, I might add, I think for smaller backup system installations, using one or two DMA IDE drives (on their own controllers) would work very well for this sort of linear transfer problem. Not that I do... I much prefer SCSI. But it would work just fine and IBM's come out with some huge low cost, high speed IDE drives. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 10:08:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10571 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 10:08:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10564 for ; Fri, 13 Nov 1998 10:08:47 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id LAA01408; Fri, 13 Nov 1998 11:08:23 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811131808.LAA01408@panzer.plutotech.com> Subject: Re: bus logic controller In-Reply-To: <364BED3F.41B3@wgn.net> from Co-app Network consulting at "Nov 13, 98 00:26:39 am" To: almazs@wgn.net Date: Fri, 13 Nov 1998 11:08:23 -0700 (MST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Co-app Network consulting wrote... > Hi; > > This may be a little off-topic > Where can I get an uptodate info on BusLogic SCSI controllers > and drivrs? bought a card that has 'BUSLOGIC FlashPoint LW' > marking on it does FreeBSD has native drivers for this scard? Look at the FreeBSD 3.0 release notes. FreeBSD does not have support for the Buslogic Flashpoint controllers, only the BusLogic MultiMaster controllers. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 10:22:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11443 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 10:22:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11382 for ; Fri, 13 Nov 1998 10:21:27 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.8/8.8.8) id UAA15831; Fri, 13 Nov 1998 20:20:28 +0200 (EET) (envelope-from ru) Date: Fri, 13 Nov 1998 20:20:27 +0200 From: Ruslan Ermilov To: FreeBSD Hackers Subject: FreeBSD on i386 memory model Message-ID: <19981113202027.A15520@ucb.crimea.ua> Mail-Followup-To: FreeBSD Hackers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.15i X-Operating-System: FreeBSD 2.2.7-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I would like to practice in writing assembler programs under FreeBSD. Is there any doc/book/man which describes the FreeBSD memory model on i386 architecture? Thanks in advance, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 10:23:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11736 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 10:23:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from natasha.wolfram.com (natasha.wolfram.com [140.177.4.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11720; Fri, 13 Nov 1998 10:23:39 -0800 (PST) (envelope-from weingart@natasha.wolfram.com) Received: from natasha.wolfram.com (weingart@localhost [127.0.0.1]) by natasha.wolfram.com (8.8.8/8.8.8) with ESMTP id MAA00814; Fri, 13 Nov 1998 12:22:31 -0600 (CST) X-Mailer: exmh version 2.0.1 12/23/97 To: The Hermit Hacker cc: Alex Belits , Chuck Robey , Artur Grabowski , Tech1 , hackers@FreeBSD.ORG, isp@FreeBSD.ORG, tech@openbsd.org, tech-kern@netbsd.org Subject: Re: Detailed info on Fail-safe cluster for Freebsd/unixes In-Reply-To: Message from The Hermit Hacker of "Thu, 12 Nov 1998 23:58:38 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Nov 1998 12:22:30 -0600 Message-ID: <2468.910981350@natasha.wolfram.com> From: Tobias Weingartner Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, November 12, The Hermit Hacker wrote: > > Actually, I have to quickly agree with Chuck on this...I don't > personally want WordPerfect, mind you. But, I would be willing to pay for > a copy of StarOffice 5.0 if it were native to FreeBSD, since it would > effectively allow me to totally ditch any reliance I have on Winbloze... > > I wish there were a way of "convincing" commercial enterprises to > port to us :( Working in an commercial environment, where whole universities have asked for certain ports of the software, I can say the following. The companies are not just interested in getting something running, slapping it on a CD and shipping it to whoever pays some minimal amount for it. (I doubt you can afford the real cost of development. That might run several $100K for a decent sized product.) They also want to run it through their test suites, get managers to sign off on it, run it through SQA, fix critical bugs in it, etc. I doubt there are companies out there, who would release a flagship product of theirs, untested. It would have bugs in it, and would damage the reputation of the company... At least, that is they way most of them seem to think. --Toby. *----------------------------------------------------------------------------* | Tobias Weingartner | Email: weingart@Wolfram.com | Wolfram Research Inc. | | #8-1514 Grandview |-----------------------------| 100 Tradecenter Drive | | Champaign, IL | Unix Guru, Admin, Sys-Prgmr | Champaign, IL | |----------------------------------------------------------------------------| | %SYSTEM-F-ANARCHISM, The operating system has been overthrown | *----------------------------------------------------------------------------* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 10:41:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13371 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 10:41:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13366 for ; Fri, 13 Nov 1998 10:41:17 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id TAA30872; Fri, 13 Nov 1998 19:40:47 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.8.5) id UAA00544; Fri, 13 Nov 1998 20:22:52 GMT Message-ID: <19981113202252.51745@breizh.prism.uvsq.fr> Date: Fri, 13 Nov 1998 20:22:52 +0000 From: Nicolas Souchu To: PB Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: I2C device interfacing. References: <199811130032.AAA05268@wave.campus.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199811130032.AAA05268@wave.campus.luth.se>; from PB on Fri, Nov 13, 1998 at 12:32:21AM +0000 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 13, 1998 at 12:32:21AM +0000, PB wrote: > > > Hi, > >I just want annonce for the people involved in "philips i2c" interface >project. I have built a application for a card named "TurboText" essentialy >a ISA <-> i2c raw interface + tuner, textv, audiocontrol. So I know how to >write these things. Maybe I could help ..? > Cool. I'd say, do it if you need it or even anybody needs it, we're here to help you on the FreeBSD I2C framework. Is this board widespread? > /Peter > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 11:34:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19687 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 11:34:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ceia.nordier.com (m2-29-dbn.dial-up.net [196.34.155.93]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19670 for ; Fri, 13 Nov 1998 11:34:07 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id VAA12575; Fri, 13 Nov 1998 21:30:46 +0200 (SAT) From: Robert Nordier Message-Id: <199811131930.VAA12575@ceia.nordier.com> Subject: Re: FreeBSD on i386 memory model In-Reply-To: <19981113202027.A15520@ucb.crimea.ua> from Ruslan Ermilov at "Nov 13, 98 08:20:27 pm" To: ru@ucb.crimea.ua (Ruslan Ermilov) Date: Fri, 13 Nov 1998 21:30:44 +0200 (SAT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ruslan Ermilov wrote: > Hi! > > I would like to practice in writing assembler programs > under FreeBSD. > > Is there any doc/book/man which describes the FreeBSD > memory model on i386 architecture? Essentially it's just a flat protected model, and for most purposes can simply be ignored. Rather than documentation, I'd suggest looking at C startup code (src/lib/csu), i386-specific C library functions (src/lib/libc/i386), and at the output of `cc -S'. FWIW, here's a small standalone i386 assembler program: main: call .+0x5 popl %ebp subl $0x5,%ebp pushl $msg.1-msg leal msg-main(%ebp),%eax pushl %eax pushl $0x1 movl $0x4,%eax call .+0x5 lcall $0x7,$0x0 pushl $0x0 movl $0x1,%eax call .+0x5 lcall $0x7,$0x0 msg: .ascii "hello, world!\n" msg.1: -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 11:40:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20535 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 11:40:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from almach.engin.umich.edu (almach.engin.umich.edu [141.212.200.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20475 for ; Fri, 13 Nov 1998 11:40:04 -0800 (PST) (envelope-from amiu@engin.umich.edu) Received: from localhost (amiu@localhost [127.0.0.1]) by almach.engin.umich.edu (8.9.1a/8.9.1) with SMTP id OAA06784 for ; Fri, 13 Nov 1998 14:39:41 -0500 (EST) Date: Fri, 13 Nov 1998 14:39:41 -0500 (EST) From: Afonso Miu To: hackers@FreeBSD.ORG Subject: WaveLan Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have FreeBSD2.2.7+PAO installed on my laptop. I believe it is the old WaveLAN/PCMCIA, not the IEEE 802.11. I vaguely remember Craig saying something about updating the card to 802.11. Will 2.2.7+PAO work only with the new card? When I plug in the Wavelan card, it recognizes: wlp0: nwid [0:0] mac:[8:0:6a:2a:6:5c] it recognizes it as PCMCIA 915 MHz. When I use wlconfig to find out the configuration etc., I got: # wlconfig wlp0 wlconfig: get PSA: Invalid argument When I tried to set the nwid with the number Jon gave us, I got: # wlconfig wlp0 nwid A913 I got the same error message saying PSA: Invalid argument. Similarly when I try to change the irq. Maybe we have the wrong entry for the card in /etc/pccard.conf: # NCR Wavelan PCMCIA # If you want to use Japanese version, uncomment the second config # line and comment-out the first line. card "Lucent Technologies" "WaveLAN/PCMCIA" # config default "wlp0" any # US version (915MHz) config default "wlp0" 10 # US version (915MHz) # config default "wlp0" 10 0x01 # Japanese version (2.4GHz) ether wavelan insert echo WaveLAN PCMCIA inserted insert /etc/pccard_ether $device remove echo WaveLAN PCMCIA removed remove /etc/pccard_ether_remove $device I have tried the other config lines above with no improvement. The wlp0 entry in the kernel is set to irq 10. Any ideas? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 11:50:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21511 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 11:50:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21505 for ; Fri, 13 Nov 1998 11:50:07 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from o2.cs.rpi.edu (root@o2.cs.rpi.edu [128.113.96.156]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id OAA09999; Fri, 13 Nov 1998 14:49:42 -0500 (EST) Received: from localhost (crossd@localhost) by o2.cs.rpi.edu (8.9.1a/8.9.1) with ESMTP id OAA07133; Fri, 13 Nov 1998 14:49:42 -0500 (EST) X-Authentication-Warning: o2.cs.rpi.edu: crossd owned process doing -bs Date: Fri, 13 Nov 1998 14:49:42 -0500 From: "David E. Cross" To: Robert Nordier cc: Ruslan Ermilov , hackers@FreeBSD.ORG Subject: Re: FreeBSD on i386 memory model In-Reply-To: <199811131930.VAA12575@ceia.nordier.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That is great. Could you sprinkle a comment or 2 as to what it is doing? ie, I am not sure what the 'call .+0x5' and 'lcall $0x7,0x0' do. On Fri, 13 Nov 1998, Robert Nordier wrote: > FWIW, here's a small standalone i386 assembler program: > > main: call .+0x5 > popl %ebp > subl $0x5,%ebp > pushl $msg.1-msg > leal msg-main(%ebp),%eax > pushl %eax > pushl $0x1 > movl $0x4,%eax > call .+0x5 > lcall $0x7,$0x0 > pushl $0x0 > movl $0x1,%eax > call .+0x5 > lcall $0x7,$0x0 > msg: .ascii "hello, world!\n" > msg.1: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 12:16:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23757 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 12:16:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23727 for ; Fri, 13 Nov 1998 12:15:53 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id VAA10524; Fri, 13 Nov 1998 21:14:51 +0100 (MET) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Fri, 13 Nov 1998 21:14:51 +0100 (MET) Mime-Version: 1.0 To: Matthew Dillon Cc: Marc Slemko , David Wolfskill , hackers@FreeBSD.ORG Subject: Re: dump(8) very slow References: <199811131747.JAA05198@apollo.backplane.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 13 Nov 1998 21:14:50 +0100 In-Reply-To: Matthew Dillon's message of "Fri, 13 Nov 1998 09:47:03 -0800 (PST)" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id MAA23753 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > I gzip -2 the dump output on > the remote machine before it comes back through the ssh pipe. Why not turn on compression in ssh (-C) rather than add an extra stage to the pipeline? DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 12:43:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26619 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 12:43:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26607 for ; Fri, 13 Nov 1998 12:42:59 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA14292; Fri, 13 Nov 1998 12:42:06 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma014286; Fri, 13 Nov 98 12:41:42 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id MAA24629; Fri, 13 Nov 1998 12:41:42 -0800 (PST) From: Archie Cobbs Message-Id: <199811132041.MAA24629@bubba.whistle.com> Subject: Re: Re[2]: IP Tunneling In-Reply-To: from "oortiz@LCSI.COM" at "Nov 12, 98 05:39:14 pm" To: oortiz@LCSI.COM Date: Fri, 13 Nov 1998 12:41:42 -0800 (PST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG oortiz@LCSI.COM writes: > I'm kinda new to this. Didn't think there was different kinds. I just > thought it was a matter of compiling it into the kernel and setting up > some routes or something to that effect. Like I said, I'm new to this. > > I have the FreeBSD on a T1, and the Linux on a PPP (with static IP) > and I would like to take 5 IP's that is on the Class C that the > FreeBSD is on and tunnel them to the Linux box, so the Linux box can > use the 5 IP's. FreeBSD will do SKIP, and that's all I know about. You might ask if there are other options. But first, what can Linux do? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 13:16:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01378 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 13:16:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ceia.nordier.com (m2-34-dbn.dial-up.net [196.34.155.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01358 for ; Fri, 13 Nov 1998 13:16:11 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id XAA13342; Fri, 13 Nov 1998 23:09:58 +0200 (SAT) From: Robert Nordier Message-Id: <199811132109.XAA13342@ceia.nordier.com> Subject: Re: FreeBSD on i386 memory model In-Reply-To: from "David E. Cross" at "Nov 13, 98 02:49:42 pm" To: crossd@cs.rpi.edu (David E. Cross) Date: Fri, 13 Nov 1998 23:09:55 +0200 (SAT) Cc: rnordier@nordier.com, ru@ucb.crimea.ua, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David E. Cross wrote: > > That is great. Could you sprinkle a comment or 2 as to what it is doing? > > ie, I am not sure what the 'call .+0x5' and 'lcall $0x7,0x0' do. The "call .+0x5" just calls the location corresponding to the start of the next instruction (the '.' is the current location and a call is encoded as 5 bytes). The "lcall 0x7,0x0" does a system call. # Get offset of main in %ebp main: call .+0x5 popl %ebp subl $0x5,%ebp # write(STDOUT_FILENO, msg, sizeof(msg)); pushl $msg.1-msg leal msg-main(%ebp),%eax pushl %eax pushl $0x1 movl $0x4,%eax # SYS_write call .+0x5 lcall $0x7,$0x0 # exit(0); pushl $0x0 movl $0x1,%eax # SYS_exit call .+0x5 lcall $0x7,$0x0 msg: .ascii "hello, world!\n" msg.1: It is really just intended as a curiosity, and is neither very idiomatic nor very correct. :-) -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 13:17:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01439 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 13:17:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA01427 for ; Fri, 13 Nov 1998 13:17:04 -0800 (PST) (envelope-from vev@michvhf.com) Received: (qmail 9747 invoked by uid 1000); 13 Nov 1998 21:17:16 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Fri, 13 Nov 1998 16:17:16 -0500 (EST) X-Face: *0^4Iw) To: freebsd-hackers@FreeBSD.ORG Subject: FW: StarOffice 5.0 for FREE!! Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This just came from another list. With the recent conversation about SO and Applixware this fits right in (although it would be more suited for another list, the thread was *here*). ----- StarOffice 5.0 Personal Edition for OS/2 Star Division's new license model makes StarOffice 5.0 on all platforms available for free for individual non-commercial use. NOW AVAILABLE FOR DOWNLOAD ! See details: http://www.stardivision.com/os2/index.html ----- Looking there, there is a link for the Linux version from this URL (even tho it has os2 in it). Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Searchable Campground Listings http://www.camping-usa.com "There is no outfit less entitled to lecture me about bloat than the federal government" -- Tony Snow ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 13:18:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01595 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 13:18:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01588 for ; Fri, 13 Nov 1998 13:18:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA00332; Fri, 13 Nov 1998 13:16:48 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811132116.NAA00332@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Afonso Miu cc: hackers@FreeBSD.ORG Subject: Re: WaveLan In-reply-to: Your message of "Fri, 13 Nov 1998 14:39:41 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Nov 1998 13:16:48 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have FreeBSD2.2.7+PAO installed on my laptop. > I believe it is the old WaveLAN/PCMCIA, not the IEEE 802.11. > I vaguely remember Craig saying something about updating the card > to 802.11. Will 2.2.7+PAO work only with the new card? > > When I plug in the Wavelan card, it recognizes: > wlp0: nwid [0:0] mac:[8:0:6a:2a:6:5c] > it recognizes it as PCMCIA 915 MHz. > > When I use wlconfig to find out the configuration etc., I got: > > # wlconfig wlp0 > wlconfig: get PSA: Invalid argument wlconfig only works with the wl driver. You will probably have to use the DOS/Windows tools to set the NWID on your pccard. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 13:38:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04529 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 13:38:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04513 for ; Fri, 13 Nov 1998 13:38:23 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id QAA26137; Fri, 13 Nov 1998 16:37:47 -0500 (EST) Date: Fri, 13 Nov 1998 16:37:47 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun2 To: Archie Cobbs cc: julian@whistle.com, freebsd-hackers@FreeBSD.ORG Subject: Re: More questions on DEVFS In-Reply-To: <199811122233.OAA20678@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > (1) As I understand it, special files can be created only by superuser via > > mknod and file systems can only be mounted by superuser. I do not see any > > reason why the superuser will mount the device file system multiple times > > and possibly at different mount points. > > You might want to create a chroot()'d sub-space of your filesystem, > and put devices in there for example.. > After thinking for quite a while, I still have two confusions: (1) I read the source code of chroot() in file vfs_syscalls.c. It takes a path and change the fd_rdir (root directory) of the calling process. How can the superuser process change the root directory of any other process? (2) By saying "put devices in there..", I guess it means that the superuser mount the special device at some directory under the new root. If we set up root directories for several processes, then we may need to mount a certain device used by these processes several times. DEVFS can be mounted multiple times to achieve this. However, multiple mounts of a normal file system are NOT allowed. Am I right? Thanks for your response. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 13:47:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05786 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 13:47:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from thelab.hub.org (nat0069.mpoweredpc.net [142.177.188.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05773 for ; Fri, 13 Nov 1998 13:47:10 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id RAA12345; Fri, 13 Nov 1998 17:46:43 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 13 Nov 1998 17:46:42 -0400 (AST) From: The Hermit Hacker To: Vince Vielhaber cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FW: StarOffice 5.0 for FREE!! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Nov 1998, Vince Vielhaber wrote: > > > This just came from another list. With the recent conversation about > SO and Applixware this fits right in (although it would be more suited > for another list, the thread was *here*). > > ----- > StarOffice 5.0 Personal Edition for OS/2 > > Star Division's new license model makes StarOffice 5.0 on all platforms > available for free for individual non-commercial use. NOW AVAILABLE FOR > DOWNLOAD ! > > See details: http://www.stardivision.com/os2/index.html > ----- > > Looking there, there is a link for the Linux version from this URL (even > tho it has os2 in it). Its always been available free for linux though...:) Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 13:51:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06793 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 13:51:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06788 for ; Fri, 13 Nov 1998 13:51:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA00549; Fri, 13 Nov 1998 13:50:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811132150.NAA00549@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Jeremy cc: hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone In-reply-to: Your message of "Fri, 13 Nov 1998 14:06:39 +1100." <98Nov13.140613est.40335@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Nov 1998 13:50:40 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Greg Lehey wrote: > > And it's almost impossible to find > >spindle synchronized disks nowadays. > > Seagate Barracuda's support it, I assumed that the newer Seagates did > as well. The impression I got was that all you had to do was wire the > `spindle sync' lines from all the disks together and then designate > all except one as a sync'd slave. Admittedly, I've never tried > actually using it. Most modern "server class" SCSI disks support it. It's not useful unless you turn off tagged queueing, caching and most other drive performance features. > > Finally, aggregating involves a > >scatter/gather approach which, unless I've missed something, is not > >supported at a hardware level. Each request to the driver specifies > >one buffer for the transfer, so the scatter gather would have to be > >done by allocating more memory and performing the transfer there (for > >a read) and then copying to the correct place. > > Since the actual data transfer occurs to physical memory, whilst the > kernel buffers are in VM, this should just require some imaginative > juggling of the PTE's so the physical pages (or actual scatter/gather > requests) are de-interleaved (to match the data on each spindle). You'd have to cons a new map and have it present the scattered target area as a linear region. This is expensive, and the performance boost is likely to be low to nonexistent for optimal stripe sizes. Concatenation of multiple stripe reads is only a benefit if the stripe is small (so that concatenation significantly lowers overhead). > What would be useful is some help (from vinum or ccd) to ensure that > the cylinder group blocks (superblock + inode maps etc) don't cross > stripes. That's something that the user should take care of. Any power-of-2 stripe size is likely to work out OK, as CG's are currently 32MB. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 14:08:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09811 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 14:08:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from foo.eng.mindspring.net (foo.eng.mindspring.net [207.69.192.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09805 for ; Fri, 13 Nov 1998 14:08:18 -0800 (PST) (envelope-from cnh@foo.eng.mindspring.net) Received: (from cnh@localhost) by foo.eng.mindspring.net (8.9.1/8.8.8) id RAA16278 for freebsd-hackers@freebsd.org; Fri, 13 Nov 1998 17:09:16 -0500 (EST) (envelope-from cnh) Message-ID: <19981113170916.B15914@eng.mindspring.net> Date: Fri, 13 Nov 1998 17:09:16 -0500 From: "Christopher N . Harrell" To: freebsd-hackers@FreeBSD.ORG Subject: Re: corruption of large packets using skip on FreeBSD 2.2-STABLE Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christopher N . Harrell wrote: > > I'm sure we've overlooking something, but we've been mulling over this for days now > without any luck at all. Any insight would be appreciated. Here's the fix: [ttyp1 cnh@bar]% for i in *.orig; do echo ${i%%.orig}; diff $i ${i%%.orig}; done /usr/ports/security/skip/work/skip/freebsd skip_es.c 1769c1769 < m->m_flags &= ~ M_EOR; --- > m->m_flags &= ~ M_PROTO1; 2233c2233 < outbuf->m_flags |= M_EOR | M_PKTHDR; --- > outbuf->m_flags |= M_PROTO1 | M_PKTHDR; skip_if.h 107c107 < #define SKIP_DECRYPTED(m) ((m)->m_flags & M_EOR) --- > #define SKIP_DECRYPTED(m) ((m)->m_flags & M_PROTO1) We believe that skip's use of M_EOR was being misinterpreted by something else. It *looks* like M_PROTO1 is a protocol specific flag and can be used safely in this way, but this could very well break something else; Use with caution. cheers, Christopher To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 14:08:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09857 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 14:08:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lohi.clinet.fi (lohi.clinet.fi [194.100.0.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09846 for ; Fri, 13 Nov 1998 14:08:29 -0800 (PST) (envelope-from hsu@mail.clinet.fi) Received: from katiska.clinet.fi (katiska.clinet.fi [194.100.0.4]) by lohi.clinet.fi (8.9.1/8.9.0) with ESMTP id AAA14414 for ; Sat, 14 Nov 1998 00:08:16 +0200 (EET) Received: (from root@localhost) by katiska.clinet.fi (8.9.0/8.9.0) id AAA23020; Sat, 14 Nov 1998 00:08:02 +0200 (EET) Date: Sat, 14 Nov 1998 00:08:02 +0200 (EET) Message-Id: <199811132208.AAA23020@katiska.clinet.fi> From: Heikki Suonsivu To: freebsd-hackers@FreeBSD.ORG Subject: ipfw and type of service Reply-To: Heikki Suonsivu Organization: Clinet Ltd, Espoo, Finland Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just checking that I'm reading the code right; ipfw does not have any means of matching type of service (TOS) value ? -- Heikki Suonsivu / Clinet Oy / Tekniikantie 12 / FI-02150 Espoo / FINLAND, hsu@clinet.fi mobile +358-40-5519679 work +358-9-43542270 fax -4555276 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 14:21:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11152 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 14:21:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11145 for ; Fri, 13 Nov 1998 14:21:53 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1a/8.9.1) with ESMTP id OAA18371; Fri, 13 Nov 1998 14:22:35 -0800 (PST) To: Sid Liu cc: hackers@FreeBSD.ORG Subject: Re: unsubscribe hackers In-reply-to: Your message of "Fri, 13 Nov 1998 06:44:38 PST." <19981113144438.5977.rocketmail@send105.yahoomail.com> Date: Fri, 13 Nov 1998 14:22:34 -0800 Message-ID: <18368.910995754@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > unsubscribe hackers Sorry, wrong button - this is the form letter you need to read instead.. :) If you're receiving this message, it's because you recently sent an "unsubscribe" request to one of the lists, perhaps thinking that you were reaching an automated system instead of the multiple-thousands of people who are now seeing your "unsubscribe" in their mailboxes and probably somewhat annoyed with you. This message attempts to clear some of that up for you so you don't make the same mistake again. First off, just about all mailing lists on the internet support the -request naming standard, meaning that if the mailing list you wish to get off of (or make some comment to the administrators about) is named "taco-lovers" then the administrative alias will be called "taco-lovers-request". You do NOT send your messages to taco-lovers, since that's only going to get to the fans of that most tasty mexican dish, not the person (or program) who actually maintains the list and can do something about your request. Second, for those who plead ignorance of all this, let me just point out that you *were* sent a welcome message when you joined the FreeBSD mailing lists telling you to send ALL administrative requests to majordomo@freebsd.org (the *-request aliases for our lists just point to this one). Our mailing list software is fully automated, and it's up to the users to add and remove themselves as they see fit - no FreeBSD personnel are involved in this! If you just threw this welcome message away and didn't read it, you have only yourself to blame for the flames which may now be filling your mailbox. To briefly summarize what this message said again: You tell majordomo@freebsd.org when you want to unsubscribe to a list by sending it the string: unsubscribe In a mail message body. If you have tried repeatedly with majordomo to remove yourself and it's not working, you still don't want to send a message to the list since the users can't help you - send mail in such cases to postmaster@freebsd.org and the FreeBSD postmaster will manually intervene to figure out why you're having problems with majordomo (and please try majordomo FIRST! Our postmaster is very overworked!). Thank you! Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 14:38:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12974 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 14:38:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wrath.cs.utah.edu (wrath.cs.utah.edu [155.99.198.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12966 for ; Fri, 13 Nov 1998 14:38:19 -0800 (PST) (envelope-from danderse@cs.utah.edu) Received: from torrey.cs.utah.edu (torrey.cs.utah.edu [155.99.212.91]) by wrath.cs.utah.edu (8.8.8/8.8.8) with ESMTP id PAA11099; Fri, 13 Nov 1998 15:37:58 -0700 (MST) Received: (from danderse@localhost) by torrey.cs.utah.edu (8.9.1/8.9.1) id PAA01040; Fri, 13 Nov 1998 15:37:58 -0700 (MST) (envelope-from danderse@cs.utah.edu) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 13 Nov 1998 15:37:58 -0700 (MST) From: "David G. Andersen" To: freebsd-hackers@FreeBSD.ORG Cc: mike@fast.cs.utah.edu, sclawson@cs.utah.edu, danderse@cs.utah.edu Subject: amd/NFS INTR hang - more details. X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13900.45689.285484.668273@torrey.cs.utah.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On the topic of the earlier mentioned hang we've been tracking down; 3.0-CURRENT, on dual pII-350 machines. We're running an older version of amd, but the problem occurs with the new version more frequently. We can reliably hang the machine by: open a file over NFS write some data to the file (how much appears irrelevant) close the file descriptor while doing so, ctrl-C (SIGINTR) the process which is closing the file descriptor. (This likely explains the prevalence of hangs in Netscape and Xemacs, both of which use quite a few signals. We've replicated it on a machine running nothing but the bare essentials, and nfsiod) The kernel still responds to pings and such, but no userland executes after the hang. If we force the kernel to panic, and examine the crashdump, we find that it's hung in a tsleep call, in vinvalbuf (sys/kern/vfs_subr.c) while (vp->v_numoutput) { vp->v_flag |= VBWAIT; => tsleep((caddr_t)&vp->v_numoutput, slpflag | (PRIBIO + 1), "vinvlbuf", slptimeo); } Looking at it, it appears that: (Quoting shamelessly from Mike Hibler who peeked at it also) The test program is stuck in this loop in vinvalbuf because there is a SIGINTR pending. This causes tsleep to return immediately (without sleeping) with the return value EINTR or ERESTART but they aren't checking the return value! Hence, it spins forever in this loop because... Meanwhile one of the pending nfsbiod's has been awakened because its reply to the write request has arrived, but it never gets to run. The other three nfsbiods are blocked because only one biod can be in the socket receive at a time. And until the biods return, v_numoutput won't be decremented. It works with no nfsbiods because the test program does all the buffer writes itself so by the time it gets to vinvalbuf, v_numoutput is 0. Unfortunately, I don't know what the right behavior is off the top of my head. This appears to be a FreeBSDism that isn't in our code or NetBSD. Any thoughts / suggested fixes would be appreciated. Interestingly, this appears to be at least slightly orthogonal to the other person reporting NFS problems whereby processes would get locked in "D" state; with the nfsiod's disabled, we're also seeing that problem, but haven't looked into it yet. -Dave -- work: danderse@cs.utah.edu me: angio@pobox.com University of Utah http://www.angio.net/ Department of Computer Science To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 14:39:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13062 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 14:39:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13056 for ; Fri, 13 Nov 1998 14:39:02 -0800 (PST) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id QAA04845 for ; Fri, 13 Nov 1998 16:38:42 -0600 (CST) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma004843; Fri, 13 Nov 98 16:38:38 -0600 Received: from spawn.nectar.com (localhost.nectar.com [127.0.0.1]) by spawn.nectar.com (8.9.1/8.9.1) with ESMTP id QAA10370 for ; Fri, 13 Nov 1998 16:38:37 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Message-Id: <199811132238.QAA10370@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine Subject: port/8609 To: hackers@FreeBSD.ORG Date: Fri, 13 Nov 1998 16:38:37 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Can someone who knows something about terminal drivers give me a hand with port/8609? Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNky07TeRhT8JRySpAQHnUQQAm5vx3spX2LAZnPsxVR0THpN6/Ox9bYZw 9v6y02eho5IbENth5ow1x8bQ6BbN86x7TxHcoNMH7B3xIMrP7k/xQhBwinqD9ESp IMAkHVt19zpSFQjyJPPLl3daQFPkamglnFJqgPXEvedlwvnMZu43eAOn5Vdw26bh 2HeqXLM4mig= =NR+6 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 14:58:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15594 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 14:58:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15582 for ; Fri, 13 Nov 1998 14:58:30 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA15598; Fri, 13 Nov 1998 14:57:01 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdj15594; Fri Nov 13 22:56:57 1998 Date: Fri, 13 Nov 1998 14:56:19 -0800 (PST) From: Julian Elischer To: zhihuizhang cc: Archie Cobbs , freebsd-hackers@FreeBSD.ORG Subject: Re: More questions on DEVFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Nov 1998, zhihuizhang wrote: > > > > (1) As I understand it, special files can be created only by superuser via > > > mknod and file systems can only be mounted by superuser. I do not see any > > > reason why the superuser will mount the device file system multiple times > > > and possibly at different mount points. > > > > You might want to create a chroot()'d sub-space of your filesystem, > > and put devices in there for example.. > > > After thinking for quite a while, I still have two confusions: > > (1) I read the source code of chroot() in file vfs_syscalls.c. It takes a > path and change the fd_rdir (root directory) of the calling process. How > can the superuser process change the root directory of any other process? Chroot is only valid for your own process, and its descendants > > (2) By saying "put devices in there..", I guess it means that the > superuser mount the special device at some directory under the new root. > If we set up root directories for several processes, then we may need to > mount a certain device used by these processes several times. DEVFS can > be mounted multiple times to achieve this. However, multiple mounts of > a normal file system are NOT allowed. Am I right? That is correct though I think possibly multiple /proc filesystems might be ok.. > > Thanks for your response. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 15:01:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16070 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 15:01:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16064 for ; Fri, 13 Nov 1998 15:01:57 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA15266; Fri, 13 Nov 1998 14:48:12 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdK15243; Fri Nov 13 22:48:03 1998 Date: Fri, 13 Nov 1998 14:47:24 -0800 (PST) From: Julian Elischer To: Heikki Suonsivu cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ipfw and type of service In-Reply-To: <199811132208.AAA23020@katiska.clinet.fi> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe your're right... patches accepted :-) On Sat, 14 Nov 1998, Heikki Suonsivu wrote: > > Just checking that I'm reading the code right; ipfw does not have any means > of matching type of service (TOS) value ? > > -- > Heikki Suonsivu / Clinet Oy / Tekniikantie 12 / FI-02150 Espoo / FINLAND, > hsu@clinet.fi mobile +358-40-5519679 work +358-9-43542270 fax -4555276 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 15:03:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16363 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 15:03:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wrath.cs.utah.edu (wrath.cs.utah.edu [155.99.198.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16355 for ; Fri, 13 Nov 1998 15:03:48 -0800 (PST) (envelope-from danderse@cs.utah.edu) Received: from torrey.cs.utah.edu (torrey.cs.utah.edu [155.99.212.91]) by wrath.cs.utah.edu (8.8.8/8.8.8) with ESMTP id QAA12219; Fri, 13 Nov 1998 16:03:27 -0700 (MST) Received: (from danderse@localhost) by torrey.cs.utah.edu (8.9.1/8.9.1) id QAA01114; Fri, 13 Nov 1998 16:03:27 -0700 (MST) (envelope-from danderse@cs.utah.edu) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 13 Nov 1998 16:03:27 -0700 (MST) From: "David G. Andersen" To: freebsd-hackers@FreeBSD.ORG CC: sclawson@cs.utah.edu, mike@fast.cs.utah.edu, danderse@cs.utah.edu Subject: nfs intr hang and mount options X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13900.47610.325085.20936@torrey.cs.utah.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems possible that the problem is related to the handling of the 'intr' flag on NFS mounted filesystems; the filesystem where we replicate the crash is mounted with: rw, overlay, intr, bg, quotas, grpid, vers=2 (overlay is a solaris thing). If we mount the filesystem with a diffent set of options: rw, grpid, resvport, nfsv2, nosuid, nodev then we can't replicate the problem. Not too surprising, since the problem is triggered by a SIGINTR, but probably a reasonable datapoint to watch. -dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 15:26:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19628 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 15:26:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19617 for ; Fri, 13 Nov 1998 15:26:27 -0800 (PST) (envelope-from ticso@cicely5.cicely.de) Received: from cicely.cicely.de (cicely.de [194.231.9.142]) by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id AAA05542; Sat, 14 Nov 1998 00:25:27 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [10.1.1.7]) by cicely.cicely.de (8.8.8/8.8.8) with ESMTP id AAA03774; Sat, 14 Nov 1998 00:25:28 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.9.0/8.9.0) id AAA00482; Sat, 14 Nov 1998 00:25:23 +0100 (CET) Message-ID: <19981114002523.39363@cicely.de> Date: Sat, 14 Nov 1998 00:25:23 +0100 From: Bernd Walter To: Mike Smith , Peter Jeremy Cc: hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <98Nov13.140613est.40335@border.alcanet.com.au> <199811132150.NAA00549@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199811132150.NAA00549@dingo.cdrom.com>; from Mike Smith on Fri, Nov 13, 1998 at 01:50:40PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 13, 1998 at 01:50:40PM -0800, Mike Smith wrote: > > Greg Lehey wrote: > > > And it's almost impossible to find > > >spindle synchronized disks nowadays. > > > > Seagate Barracuda's support it, I assumed that the newer Seagates did > > as well. The impression I got was that all you had to do was wire the > > `spindle sync' lines from all the disks together and then designate > > all except one as a sync'd slave. Admittedly, I've never tried > > actually using it. > > Most modern "server class" SCSI disks support it. It's not useful > unless you turn off tagged queueing, caching and most other drive > performance features. Where's the problem with these options on when using Spindle Sync? > > > > Finally, aggregating involves a > > >scatter/gather approach which, unless I've missed something, is not > > >supported at a hardware level. Each request to the driver specifies > > >one buffer for the transfer, so the scatter gather would have to be > > >done by allocating more memory and performing the transfer there (for > > >a read) and then copying to the correct place. > > > > Since the actual data transfer occurs to physical memory, whilst the > > kernel buffers are in VM, this should just require some imaginative > > juggling of the PTE's so the physical pages (or actual scatter/gather > > requests) are de-interleaved (to match the data on each spindle). > > You'd have to cons a new map and have it present the scattered target > area as a linear region. This is expensive, and the performance boost > is likely to be low to nonexistent for optimal stripe sizes. > Concatenation of multiple stripe reads is only a benefit if the stripe > is small (so that concatenation significantly lowers overhead). That's right - but you can't expect a high linear performance increase when using great stripes. By the way: Is FFS limited to 64k Blocksize? At least newfs can't handle it it my case: root@cicely5# newfs -f 65536 -b 131072 rda14e Warning: 640 sector(s) in last cylinder unallocated /dev/rda14e: 2116992 sectors in 517 cylinders of 1 tracks, 4096 sectors 1033.7MB in 33 cyl groups (16 c/g, 32.00MB/g, 1024 i/g) super-block backups (for fsck -b #) at: 256, 65792, 131328, 196864, 262400, 327936, 393472, 459008, 524544, 590080, 655616, 721152, 786688, 852224, 917760, 983296, 1048832, 1114368, 1179904, 1245440, 1310976, 1376512, 1442048, 1507584, 1573120, 1638656, 1704192, 1769728, 1835264, 1900800, 1966336, 2031872, 2097408, read error: 768 newfs: rdfs: Bad address root@cicely5# newfs -f 65536 -b 65536 rda14e Warning: 640 sector(s) in last cylinder unallocated /dev/rda14e: 2116992 sectors in 517 cylinders of 1 tracks, 4096 sectors 1033.7MB in 33 cyl groups (16 c/g, 32.00MB/g, 512 i/g) super-block backups (for fsck -b #) at: 128, 65664, 131200, 196736, 262272, 327808, 393344, 458880, 524416, 589952, 655488, 721024, 786560, 852096, 917632, 983168, 1048704, 1114240, 1179776, 1245312, 1310848, 1376384, 1441920, 1507456, 1572992, 1638528, 1704064, 1769600, 1835136, 1900672, 1966208, 2031744, 2097280, > > > What would be useful is some help (from vinum or ccd) to ensure that > > the cylinder group blocks (superblock + inode maps etc) don't cross > > stripes. > > That's something that the user should take care of. Any power-of-2 > stripe size is likely to work out OK, as CG's are currently 32MB. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 15:28:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19803 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 15:28:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19797 for ; Fri, 13 Nov 1998 15:28:12 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id PAA06232; Fri, 13 Nov 1998 15:27:47 -0800 (PST) (envelope-from dillon) Date: Fri, 13 Nov 1998 15:27:47 -0800 (PST) From: Matthew Dillon Message-Id: <199811132327.PAA06232@apollo.backplane.com> To: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Cc: Marc Slemko , David Wolfskill , hackers@FreeBSD.ORG Subject: Re: dump(8) very slow References: <199811131747.JAA05198@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Matthew Dillon writes: :> I gzip -2 the dump output on :> the remote machine before it comes back through the ssh pipe. : :Why not turn on compression in ssh (-C) rather than add an extra stage :to the pipeline? I am saving gzip'd dumps to tape directly. I know, I know, it means you'd better not have a tape error in a dump. Too bad. Exabytes do duel-head verification anyway, though you definitely have to clean the drives twice a week (at the volume levels we push through the drives) to maintain optimal performance (which is 3 MBytes/sec for an exabyte Mammoth). The backup machine is already cpu-limited doing the encryption (even though the network is switched and secured, we don't trust it). If I had the backup machine do compression (ssh -C) as well, or if I had it gunzip the remotely-gzip'd dump, the 2.5 MBytes/sec would because 1.5 MBytes/sec. If I have the tape drive do the compression, I get sub-optimal capacity verses pushing gzip'd dumps to a tape drive in uncompressed mode. Sometimes I think about turning off ssh's link encryption, but then I think a little more and say 'nahh, better to leave it on'. Once we upgrade the machine we'll be able to dump 6 MBytes/sec over the network, which matches two 3 MByte/sec tape drives very well. -Matt :DES :-- :Dag-Erling Smørgrav - dag-erli@ifi.uio.no : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 15:38:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20706 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 15:38:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20701 for ; Fri, 13 Nov 1998 15:38:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01117; Fri, 13 Nov 1998 15:36:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811132336.PAA01117@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bernd Walter cc: Mike Smith , Peter Jeremy , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone In-reply-to: Your message of "Sat, 14 Nov 1998 00:25:23 +0100." <19981114002523.39363@cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Nov 1998 15:36:14 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Nov 13, 1998 at 01:50:40PM -0800, Mike Smith wrote: > > > Greg Lehey wrote: > > > > And it's almost impossible to find > > > >spindle synchronized disks nowadays. > > > > > > Seagate Barracuda's support it, I assumed that the newer Seagates did > > > as well. The impression I got was that all you had to do was wire the > > > `spindle sync' lines from all the disks together and then designate > > > all except one as a sync'd slave. Admittedly, I've never tried > > > actually using it. > > > > Most modern "server class" SCSI disks support it. It's not useful > > unless you turn off tagged queueing, caching and most other drive > > performance features. > Where's the problem with these options on when using Spindle Sync? The whole point of spindle sync is to exactly lock all the drives together to coordinate read/write activity. These features in conjunction with sector sparing and quantum differences between disks means that synchronising spindles is a complete waste of time, as the disks won't be mimicking each other anyway. > > > > Finally, aggregating involves a > > > >scatter/gather approach which, unless I've missed something, is not > > > >supported at a hardware level. Each request to the driver specifies > > > >one buffer for the transfer, so the scatter gather would have to be > > > >done by allocating more memory and performing the transfer there (for > > > >a read) and then copying to the correct place. > > > > > > Since the actual data transfer occurs to physical memory, whilst the > > > kernel buffers are in VM, this should just require some imaginative > > > juggling of the PTE's so the physical pages (or actual scatter/gather > > > requests) are de-interleaved (to match the data on each spindle). > > > > You'd have to cons a new map and have it present the scattered target > > area as a linear region. This is expensive, and the performance boost > > is likely to be low to nonexistent for optimal stripe sizes. > > Concatenation of multiple stripe reads is only a benefit if the stripe > > is small (so that concatenation significantly lowers overhead). > That's right - but you can't expect a high linear performance increase > when using great stripes. That depends on the application's read behaviour. If reads are larger than the stripe size, you still win. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 16:11:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26267 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 16:11:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26260 for ; Fri, 13 Nov 1998 16:11:37 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA02774; Sat, 14 Nov 1998 10:41:07 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id KAA26312; Sat, 14 Nov 1998 10:41:05 +1030 (CST) Message-ID: <19981114104105.S781@freebie.lemis.com> Date: Sat, 14 Nov 1998 10:41:05 +1030 From: Greg Lehey To: Mike Smith , Bernd Walter Cc: Peter Jeremy , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <19981114002523.39363@cicely.de> <199811132336.PAA01117@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811132336.PAA01117@dingo.cdrom.com>; from Mike Smith on Fri, Nov 13, 1998 at 03:36:14PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 13 November 1998 at 15:36:14 -0800, Mike Smith wrote: >> On Fri, Nov 13, 1998 at 01:50:40PM -0800, Mike Smith wrote: >>>> Greg Lehey wrote: >>>>> And it's almost impossible to find >>>>> spindle synchronized disks nowadays. >>>> >>>> Seagate Barracuda's support it, I assumed that the newer Seagates did >>>> as well. The impression I got was that all you had to do was wire the >>>> `spindle sync' lines from all the disks together and then designate >>>> all except one as a sync'd slave. Admittedly, I've never tried >>>> actually using it. >>> >>> Most modern "server class" SCSI disks support it. It's not useful >>> unless you turn off tagged queueing, caching and most other drive >>> performance features. >> Where's the problem with these options on when using Spindle Sync? > > The whole point of spindle sync is to exactly lock all the drives > together to coordinate read/write activity. These features in > conjunction with sector sparing and quantum differences between disks > means that synchronising spindles is a complete waste of time, as the > disks won't be mimicking each other anyway. Apart from this, in a multiuser environment you won't just be reading a single file. Any form of write to a block device or multiple reads will cause the block device subsystem to issue requests at different times, so having the spindles synched, no spare sectors and identical disks still wouldn't help. >>>>> Finally, aggregating involves a >>>>> scatter/gather approach which, unless I've missed something, is not >>>>> supported at a hardware level. Each request to the driver specifies >>>>> one buffer for the transfer, so the scatter gather would have to be >>>>> done by allocating more memory and performing the transfer there (for >>>>> a read) and then copying to the correct place. >>>> >>>> Since the actual data transfer occurs to physical memory, whilst the >>>> kernel buffers are in VM, this should just require some imaginative >>>> juggling of the PTE's so the physical pages (or actual scatter/gather >>>> requests) are de-interleaved (to match the data on each spindle). >>> >>> You'd have to cons a new map and have it present the scattered target >>> area as a linear region. This is expensive, and the performance boost >>> is likely to be low to nonexistent for optimal stripe sizes. >>> Concatenation of multiple stripe reads is only a benefit if the stripe >>> is small (so that concatenation significantly lowers overhead). >> That's right - but you can't expect a high linear performance increase >> when using great stripes. > > That depends on the application's read behaviour. If reads are larger > than the stripe size, you still win. We're talking about stripes larger than the maximum physical I/O length here. I'll tell you what: anybody who wants, go and look at the request building code in /usr/src/lkm/vinum/request.c and rebuild it to perform the "aggregation" optimizations that Bernd wants, and I'll put it into the code. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 17:12:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01381 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 17:12:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01361 for ; Fri, 13 Nov 1998 17:12:10 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id CAA13389 for hackers@FreeBSD.ORG; Sat, 14 Nov 1998 02:11:40 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 150E814FA; Sat, 14 Nov 1998 01:50:12 +0100 (CET) Date: Sat, 14 Nov 1998 01:50:11 +0100 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: FreeBSD on i386 memory model Message-ID: <19981114015011.A7966@keltia.freenix.fr> Mail-Followup-To: hackers@FreeBSD.ORG References: <199811132109.XAA13342@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i In-Reply-To: <199811132109.XAA13342@ceia.nordier.com>; from Robert Nordier on Fri, Nov 13, 1998 at 11:09:55PM +0200 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4805 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Robert Nordier: > It is really just intended as a curiosity, and is neither very > idiomatic nor very correct. :-) I found a few years back a complete manual for the AT&T assembler syntax somewhere on the 'Net. I must have deleted it and am now unable to find it again. Anyone with a pointer to it ? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 18:21:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06095 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 18:21:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ceia.nordier.com (m2-17-dbn.dial-up.net [196.34.155.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06039 for ; Fri, 13 Nov 1998 18:21:18 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id EAA15033 for hackers@FreeBSD.org; Sat, 14 Nov 1998 04:20:20 +0200 (SAT) From: Robert Nordier Message-Id: <199811140220.EAA15033@ceia.nordier.com> Subject: Re: FreeBSD on i386 memory model In-Reply-To: <19981114015011.A7966@keltia.freenix.fr> from Ollivier Robert at "Nov 14, 98 01:50:11 am" To: hackers@FreeBSD.ORG Date: Sat, 14 Nov 1998 04:20:18 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ollivier Robert wrote: > According to Robert Nordier: > > It is really just intended as a curiosity, and is neither very > > idiomatic nor very correct. :-) > > I found a few years back a complete manual for the AT&T assembler syntax > somewhere on the 'Net. I must have deleted it and am now unable to find it > again. > > Anyone with a pointer to it ? Hope I didn't imply "not very correct" in any mundane syntactic sense. :) The transformations between Intel and AT&T syntax can really be expressed in about a dozen rules, and there are sed and awk scripts around that do a fairly reasonable job of automatic translation. The Intel 80386 manual is available from various places (except Intel) in text format, so it shouldn't be too difficult to do an AT&T-flavored manual, if anyone thought this worth the bother. I've never found GNU assembler syntax to correspond terribly closely to that of the AT&T assemblers I've used, though. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 20:43:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13415 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 20:43:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from acrserv-1.acrny.com (internet.acrny.com [207.252.53.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13410; Fri, 13 Nov 1998 20:43:34 -0800 (PST) (envelope-from adam.furman@usi.net) Received: by ACRSERV-1 with Internet Mail Service (5.5.2232.9) id ; Fri, 13 Nov 1998 23:42:44 -0500 Message-ID: <41156768DA32D211A97600C0F0313F01393E@ACRSERV-1> From: Adam Furman To: "'freebsd-hackers@freebsd.org'" , "'freebsd-fs@freebsd.org'" Cc: Adam Furman Subject: Server going into Kernel Debug mode Date: Fri, 13 Nov 1998 23:42:35 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running FreeBSD 2.2.5 on an Pentium 133 with 128megs of Memory. My server seems to be crashing now every couple of hours and goes into Kernel Debug mode. The server was running for 184 days before it started to encore any problems. It gave me trouble for about 3 days and it all of sudden stop giving me trouble and ran for another month. The server again is giving me problems. The error message that is comming up on the console is as follows. Any help in this problem would be great. I need to know what could be wrong so I can fix that problem so this doesn't keep happening. Thanks Adam Furman (error message) calcrv: negative time: -6131984 vsec fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xf0153ed9 stack pointer = 0x10:0xefbfff74 frame pointer = 0x10:0xefbfff84 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, Pres 1, det32 1, gran 1 processor eflags = interrupt enabled, resume, IUPL=0 current process = 177(SSHD1) interrupt mask = kernel: type 12 trap, code =0 stoped at _ip_slowtimot0x49: mov1 0x4(%ebx),%eax db> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 20:46:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13813 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 20:46:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13797; Fri, 13 Nov 1998 20:46:50 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from celeris (56k-port4020.ime.net [209.90.195.30]) by Loki.orland.u91.k12.me.us (8.9.1/8.8.8-Loki) with SMTP id XAA00527; Fri, 13 Nov 1998 23:46:10 -0500 (EST) (envelope-from netmonger@genesis.ispace.com) X-Server-ID: Loki.orland.u91.k12.me.us, OCSNet - Orland Maine USA X-Coord-Name: Drew "Droobie" Baxter, OneNetwork Exchange X-Coord-Addr: Droobie@Openlink.orland.me.us X-Coord-Pager: USA: 207-471-2719, http://pagedroo.orland.me.us Message-Id: <4.1.19981113234248.00ae9ca0@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 13 Nov 1998 23:43:58 -0500 To: Adam Furman , "'freebsd-hackers@freebsd.org'" , "'freebsd-fs@freebsd.org'" From: Drew Baxter Subject: Re: Server going into Kernel Debug mode Cc: Adam Furman In-Reply-To: <41156768DA32D211A97600C0F0313F01393E@ACRSERV-1> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:42 PM 11/13/98 -0500, Adam Furman wrote: >I'm running FreeBSD 2.2.5 on an Pentium 133 with 128megs of Memory. My >server seems to be crashing now every couple of hours and goes into Kernel >Debug mode. The server was running for 184 days before it started to encore >any problems. It gave me trouble for about 3 days and it all of sudden stop >giving me trouble and ran for another month. The server again is giving me >problems. The error message that is comming up on the console is as >follows. Any help in this problem would be great. I need to know what >could be wrong so I can fix that problem so this doesn't keep happening. >Thanks >Adam Furman > >(error message) >calcrv: negative time: -6131984 vsec >fatal trap 12: page fault while in kernel mode >fault virtual address = 0x4 >fault code = supervisor read, page not present >instruction pointer = 0x8:0xf0153ed9 >stack pointer = 0x10:0xefbfff74 >frame pointer = 0x10:0xefbfff84 > >code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, Pres 1, det32 1, gran 1 >processor eflags = interrupt enabled, resume, IUPL=0 >current process = 177(SSHD1) >interrupt mask = >kernel: type 12 trap, code =0 >stoped at _ip_slowtimot0x49: mov1 0x4(%ebx),%eax >db> You wouldn't by any chance have kernel-level debugging on do you? (option DDB?). I had it in my kernel for a while, but the thing would do exactly that, and then it would go and beep eradically.. That doesn't work very well when the machine is over 30 miles away. --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange 207-942-0275 http://www.droo.orland.me.us My Latest Kernel: FreeBSD 3.0-CURRENT (ONEEX) #14: Mon Oct 19 22:36:58 EDT 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 22:11:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19187 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 22:11:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (105.camalott.com [208.203.140.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19182 for ; Fri, 13 Nov 1998 22:11:10 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id AAA03081; Sat, 14 Nov 1998 00:10:22 -0600 (CST) (envelope-from joelh) To: Robert Nordier Cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD on i386 memory model References: <199811140220.EAA15033@ceia.nordier.com> From: Joel Ray Holveck Date: 14 Nov 1998 00:10:21 -0600 In-Reply-To: Robert Nordier's message of "Sat, 14 Nov 1998 04:20:18 +0200 (SAT)" Message-ID: <86ogqaerea.fsf@detlev.UUCP> Lines: 17 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The transformations between Intel and AT&T syntax can really be > expressed in about a dozen rules, and there are sed and awk scripts > around that do a fairly reasonable job of automatic translation. I posted an article on this here a while back if someone cares to check the archives. (It's the only discussion on assembler I recall being involved in on -hackers.) There's also a decent overview of the differences between AT&T and Intel syntax in the gas info file. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 13 23:46:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA22465 for freebsd-hackers-outgoing; Fri, 13 Nov 1998 23:46:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA22460 for ; Fri, 13 Nov 1998 23:46:51 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id SAA03765; Sat, 14 Nov 1998 18:16:18 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id SAA26989; Sat, 14 Nov 1998 18:16:15 +1030 (CST) Message-ID: <19981114181615.G781@freebie.lemis.com> Date: Sat, 14 Nov 1998 18:16:15 +1030 From: Greg Lehey To: Adam Furman , freebsd-hackers@FreeBSD.ORG Subject: Re: Server going into Kernel Debug mode References: <41156768DA32D211A97600C0F0313F01393E@ACRSERV-1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <41156768DA32D211A97600C0F0313F01393E@ACRSERV-1>; from Adam Furman on Fri, Nov 13, 1998 at 11:42:35PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [removing -fs; I don't see the reason for this] On Friday, 13 November 1998 at 23:42:35 -0500, Adam Furman wrote: > I'm running FreeBSD 2.2.5 on an Pentium 133 with 128megs of Memory. My > server seems to be crashing now every couple of hours and goes into Kernel > Debug mode. The server was running for 184 days before it started to encore > any problems. It gave me trouble for about 3 days and it all of sudden stop > giving me trouble and ran for another month. The server again is giving me > problems. The error message that is comming up on the console is as > follows. Any help in this problem would be great. I need to know what > could be wrong so I can fix that problem so this doesn't keep happening. > Thanks > Adam Furman > > (error message) > calcrv: negative time: -6131984 vsec > fatal trap 12: page fault while in kernel mode > fault virtual address = 0x4 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xf0153ed9 > stack pointer = 0x10:0xefbfff74 > frame pointer = 0x10:0xefbfff84 > > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, Pres 1, det32 1, gran 1 > processor eflags = interrupt enabled, resume, IUPL=0 > current process = 177(SSHD1) > interrupt mask = > kernel: type 12 trap, code =0 > stoped at _ip_slowtimot0x49: mov1 0x4(%ebx),%eax > db> Well, yes, you've gone into the kernel debugger because it's configured. If it hadn't been, you would just have had a panic. Small choice in rotten apples. I suppose the first question is: do you know how to use the kernel debugger? If not, disable it. If you do, check the handbook, which tells you what to do with the debugger. I strongly recommend a debug kernel, which will enable you to find out what is happening. You might also like to look at http://www.lemis.com/vinum_debugging.html, which, though not general purpose, contains some ideas which aren't available elsewhere. In this case, you've obviously died in ip_slowtimo (not ip_slowtimot, as you wrote), and I'd guess it's related with the calcru time offset you mention. I don't have 2.2.5 online, but you might find it an interesting effort to find out what went wrong there. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 00:50:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25556 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 00:50:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25549 for ; Sat, 14 Nov 1998 00:50:26 -0800 (PST) (envelope-from ticso@cicely5.cicely.de) Received: from cicely.cicely.de (cicely.de [194.231.9.142]) by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id JAA24251; Sat, 14 Nov 1998 09:49:32 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [10.1.1.7]) by cicely.cicely.de (8.8.8/8.8.8) with ESMTP id JAA08943; Sat, 14 Nov 1998 09:49:56 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.9.0/8.9.0) id JAA04069; Sat, 14 Nov 1998 09:49:38 +0100 (CET) Message-ID: <19981114094937.10858@cicely.de> Date: Sat, 14 Nov 1998 09:49:37 +0100 From: Bernd Walter To: Greg Lehey , Mike Smith Cc: Peter Jeremy , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <19981114002523.39363@cicely.de> <199811132336.PAA01117@dingo.cdrom.com> <19981114104105.S781@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19981114104105.S781@freebie.lemis.com>; from Greg Lehey on Sat, Nov 14, 1998 at 10:41:05AM +1030 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 14, 1998 at 10:41:05AM +1030, Greg Lehey wrote: > I'll tell you what: anybody who wants, go and look at the request > building code in /usr/src/lkm/vinum/request.c and rebuild it to > perform the "aggregation" optimizations that Bernd wants, and I'll > put it into the code. I don't "want" it - I'm just expecting a perdormance icnrease in a special and unusal case. There are some thing that should be more usefull to implement at this moment than some performance things: - fsck -p can't find the rvol - I couldn't find any way to dump a vinum volume - maybe the same reason. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 02:30:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA00777 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 02:30:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA00772 for ; Sat, 14 Nov 1998 02:30:07 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id UAA04012; Sat, 14 Nov 1998 20:59:40 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id UAA27169; Sat, 14 Nov 1998 20:59:39 +1030 (CST) Message-ID: <19981114205938.J781@freebie.lemis.com> Date: Sat, 14 Nov 1998 20:59:38 +1030 From: Greg Lehey To: Bernd Walter , Mike Smith Cc: Peter Jeremy , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <19981114002523.39363@cicely.de> <199811132336.PAA01117@dingo.cdrom.com> <19981114104105.S781@freebie.lemis.com> <19981114094937.10858@cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981114094937.10858@cicely.de>; from Bernd Walter on Sat, Nov 14, 1998 at 09:49:37AM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 14 November 1998 at 9:49:37 +0100, Bernd Walter wrote: > On Sat, Nov 14, 1998 at 10:41:05AM +1030, Greg Lehey wrote: >> I'll tell you what: anybody who wants, go and look at the request >> building code in /usr/src/lkm/vinum/request.c and rebuild it to >> perform the "aggregation" optimizations that Bernd wants, and I'll >> put it into the code. > > I don't "want" it - I'm just expecting a perdormance icnrease in a special > and unusal case. > There are some thing that should be more usefull to implement at this moment > than some performance things: > - fsck -p can't find the rvol Somewhere round here we're running into Vinum testing. But OK. What problems did you have? # fsck -p /dev/vinum/rsrc /dev/vinum/rsrc: clean, 365642 free (874 frags, 45596 blocks, 0.2% fragmentation) # fsck -p /dev/vinum/robj /dev/vinum/robj: clean, 152758 free (6814 frags, 18243 blocks, 1.7% fragmentation) > - I couldn't find any way to dump a vinum volume - maybe the same reason. I don't use dump. I'd like to hear the problems you had. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 03:41:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA04871 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 03:41:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA04865 for ; Sat, 14 Nov 1998 03:41:43 -0800 (PST) (envelope-from ticso@cicely5.cicely.de) Received: from cicely.cicely.de (cicely.de [194.231.9.142]) by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id MAA20087; Sat, 14 Nov 1998 12:40:52 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [10.1.1.7]) by cicely.cicely.de (8.8.8/8.8.8) with ESMTP id MAA09393; Sat, 14 Nov 1998 12:41:20 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.9.0/8.9.0) id MAA00553; Sat, 14 Nov 1998 12:41:13 +0100 (CET) Message-ID: <19981114124113.38442@cicely.de> Date: Sat, 14 Nov 1998 12:41:13 +0100 From: Bernd Walter To: Greg Lehey , Mike Smith Cc: Peter Jeremy , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <19981114002523.39363@cicely.de> <199811132336.PAA01117@dingo.cdrom.com> <19981114104105.S781@freebie.lemis.com> <19981114094937.10858@cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19981114094937.10858@cicely.de>; from Bernd Walter on Sat, Nov 14, 1998 at 09:49:37AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 14, 1998 at 09:49:37AM +0100, Bernd Walter wrote: > On Sat, Nov 14, 1998 at 10:41:05AM +1030, Greg Lehey wrote: > > I'll tell you what: anybody who wants, go and look at the request > > building code in /usr/src/lkm/vinum/request.c and rebuild it to > > perform the "aggregation" optimizations that Bernd wants, and I'll > > put it into the code. > I don't "want" it - I'm just expecting a perdormance icnrease in a special > and unusal case. > There are some thing that should be more usefull to implement at this moment > than some performance things: > - fsck -p can't find the rvol > - I couldn't find any way to dump a vinum volume - maybe the same reason. > Sorry it works when using /dev/vinum/volname /dev/vinum/rvolname I was trying with /dev/vinum/vol/volname /dev/vinum/rvol/volname > > > > Greg > > -- > > See complete headers for address, home page and phone numbers > > finger grog@lemis.com for PGP public key > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > -- > B.Walter > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 03:52:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA07003 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 03:52:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA06996 for ; Sat, 14 Nov 1998 03:52:18 -0800 (PST) (envelope-from ticso@cicely5.cicely.de) Received: from cicely.cicely.de (cicely.de [194.231.9.142]) by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id MAA21638; Sat, 14 Nov 1998 12:51:27 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [10.1.1.7]) by cicely.cicely.de (8.8.8/8.8.8) with ESMTP id MAA09405; Sat, 14 Nov 1998 12:51:47 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.9.0/8.9.0) id MAA00575; Sat, 14 Nov 1998 12:51:43 +0100 (CET) Message-ID: <19981114125143.03016@cicely.de> Date: Sat, 14 Nov 1998 12:51:43 +0100 From: Bernd Walter To: Greg Lehey , Mike Smith Cc: Peter Jeremy , hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <19981114002523.39363@cicely.de> <199811132336.PAA01117@dingo.cdrom.com> <19981114104105.S781@freebie.lemis.com> <19981114094937.10858@cicely.de> <19981114205938.J781@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19981114205938.J781@freebie.lemis.com>; from Greg Lehey on Sat, Nov 14, 1998 at 08:59:38PM +1030 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 14, 1998 at 08:59:38PM +1030, Greg Lehey wrote: > On Saturday, 14 November 1998 at 9:49:37 +0100, Bernd Walter wrote: > > On Sat, Nov 14, 1998 at 10:41:05AM +1030, Greg Lehey wrote: > >> I'll tell you what: anybody who wants, go and look at the request > >> building code in /usr/src/lkm/vinum/request.c and rebuild it to > >> perform the "aggregation" optimizations that Bernd wants, and I'll > >> put it into the code. > > > > I don't "want" it - I'm just expecting a perdormance icnrease in a special > > and unusal case. > > There are some thing that should be more usefull to implement at this moment > > than some performance things: > > - fsck -p can't find the rvol > > Somewhere round here we're running into Vinum testing. But OK. What > problems did you have? > > # fsck -p /dev/vinum/rsrc > /dev/vinum/rsrc: clean, 365642 free (874 frags, 45596 blocks, 0.2% fragmentation) > # fsck -p /dev/vinum/robj > /dev/vinum/robj: clean, 152758 free (6814 frags, 18243 blocks, 1.7% fragmentation) > > > - I couldn't find any way to dump a vinum volume - maybe the same reason. > > I don't use dump. I'd like to hear the problems you had. Mmmm - as I can see even /dev/vinum/rvol/volname works now. Don't know exactly what happened last time. Only dumping with an fstabentry pointing to /dev/vinum/vol/volname won't work when dumping with a mount-point given. Guess that's why solaris has an entry for character and block device in /etc/vfstab. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 04:45:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA12688 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 04:45:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.linkdesign.com (relay.linkdesign.com [194.42.128.250] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA12682 for ; Sat, 14 Nov 1998 04:45:07 -0800 (PST) (envelope-from michael@linkdesign.com) Received: (from michael@localhost) by relay.linkdesign.com (8.8.8/8.8.6) id NAA02528 for hackers@freebsd.org; Sat, 14 Nov 1998 13:59:20 +0200 (EET) Message-ID: <19981114135920.A2119@linkdesign.com> Date: Sat, 14 Nov 1998 13:59:20 +0200 From: "Michael.Bielicki" To: hackers@FreeBSD.ORG Subject: Re: Applixware was Re: Detailed info on Fail-safe cluster for Freebsd/unixes References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: ; from Vince Vielhaber on Fri, Nov 13, 1998 at 10:30:11AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A applixware demo is available on ftp.suse.com in /pub/suse_apdate/applixware or something similar :) The missing IMAP support is a drawback but the data builder with connections to MySQL, Postgresql, oracle, ingres and informix is a incredible plus. And the speed compared to SO5.0 is incredible and runs even perfectly fine on a\486DX 100 with 32 MB RAM. Just my two cents .... Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 06:59:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19049 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 06:59:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19033 for ; Sat, 14 Nov 1998 06:59:52 -0800 (PST) (envelope-from roger@cs.strath.ac.uk) Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id OAA24429 Sat, 14 Nov 1998 14:59:26 GMT Message-ID: <364D9AD1.2781@cs.strath.ac.uk> Date: Sat, 14 Nov 1998 14:59:29 +0000 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: pccard.conf - the Insert Echo is not working Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, in 3.0-RELEASE, the messages pccard.conf is supposed to echo to the screen just do not appear. eg, in pccard.conf is "insert echo 3Com Etherlink III insterted" Any ideas? Bye Roger -- Roger Hardiman | Telepresence Research Group roger@cs.strath.ac.uk | DMEM, University of Strathclyde tel: 0141 548 2897 | Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557 | http://telepresence.dmem.strath.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 09:22:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29706 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 09:22:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29297 for ; Sat, 14 Nov 1998 09:20:22 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.8/8.8.8) id TAA25899; Sat, 14 Nov 1998 19:15:57 +0200 (EET) (envelope-from ru) Date: Sat, 14 Nov 1998 19:15:56 +0200 From: Ruslan Ermilov To: Robert Nordier Cc: FreeBSD Hackers Subject: Re: FreeBSD on i386 memory model Message-ID: <19981114191556.A17660@ucb.crimea.ua> Mail-Followup-To: Robert Nordier , FreeBSD Hackers References: <19981113202027.A15520@ucb.crimea.ua> <199811131930.VAA12575@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.15i In-Reply-To: <199811131930.VAA12575@ceia.nordier.com>; from Robert Nordier on Fri, Nov 13, 1998 at 09:30:44PM +0200 X-Operating-System: FreeBSD 2.2.7-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 13, 1998 at 09:30:44PM +0200, Robert Nordier wrote: > Ruslan Ermilov wrote: > > Hi! > > > > I would like to practice in writing assembler programs > > under FreeBSD. > > > > Is there any doc/book/man which describes the FreeBSD > > memory model on i386 architecture? > > Essentially it's just a flat protected model, and for most purposes > can simply be ignored. Rather than documentation, I'd suggest What documentation do you mean? > looking at C startup code (src/lib/csu), i386-specific C library > functions (src/lib/libc/i386), and at the output of `cc -S'. > > FWIW, here's a small standalone i386 assembler program: > > main: call .+0x5 > popl %ebp > subl $0x5,%ebp > pushl $msg.1-msg > leal msg-main(%ebp),%eax > pushl %eax > pushl $0x1 > movl $0x4,%eax > call .+0x5 <-- why this one? > lcall $0x7,$0x0 > pushl $0x0 > movl $0x1,%eax > call .+0x5 <-- and this one? > lcall $0x7,$0x0 > msg: .ascii "hello, world!\n" > msg.1: Unfortunately, I can't compile it, as(1) gives the following: {standard input}: Assembler messages: {standard input}:5: Error: Unimplemented segment type 0 in parse_operand {standard input}:10: Error: operands given don't match any known 386 instruction {standard input}:14: Error: operands given don't match any known 386 instruction It seems that as(1) doesn't understand ``lcall $SECTION, $OFFSET''. At least on my 2.2.1, 2.2.5 and 2.2.7+ machines: FreeBSD relay.ucb.crimea.ua 2.2.7-STABLE FreeBSD 2.2.7-STABLE #0: Sun Oct 4 18:08:06 EEST 1998 root@:/usr/src/sys/compile/CHYRO i386 GNU assembler version 1.92.3, FreeBSD $Revision: 1.4 $ Any ideas? -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 09:54:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02133 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 09:54:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from torrentnet.com (bacardi.torrentnet.com [198.78.51.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02126 for ; Sat, 14 Nov 1998 09:54:11 -0800 (PST) (envelope-from bakul@torrentnet.com) Received: from chai.torrentnet.com (chai.torrentnet.com [198.78.51.73]) by torrentnet.com (8.8.5/8.8.5) with ESMTP id MAA25261; Sat, 14 Nov 1998 12:53:44 -0500 (EST) Received: from chai.torrentnet.com (localhost [127.0.0.1]) by chai.torrentnet.com (8.8.8/8.8.5) with ESMTP id MAA25077; Sat, 14 Nov 1998 12:53:43 -0500 (EST) Message-Id: <199811141753.MAA25077@chai.torrentnet.com> To: Nate Williams Cc: hackers@FreeBSD.ORG Subject: Re: Supporting more than FD_SETSIZE fd's In-reply-to: Your message of "Wed, 11 Nov 1998 12:03:08 MST." <199811111903.MAA18067@mt.sri.com> Date: Sat, 14 Nov 1998 12:53:43 -0500 From: Bakul Shah Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The code fragment I showed is approx. right as I've used > > something similar a couple of times before but I will try to > > turn it into a working example over the weekend. > Thanks. If it included the MACROS so much the better. :) :) :) Check out http://www.bitblocks.com/src/select-test.c It even includes code to create and manipulate an FD set object! Note that when used on a kernel that has fixed FD_SETSIZE select() implementation, you must allocate exactly FD_SETSIZE elements (and certainly no less) in an FD set. BTW, instead of my FD_xxx functions you can use bitstring macros from /usr/include/bitstring.h. Sample use: In window 1: 1307% cc select-test.c 1308% ./a.out 1234 accepting on 1234, fd_setsize = 1024 3: accept from 127.0.0.1:28681 4: open 3: accept from 127.0.0.1:28937 5: open 4: Sat Nov 14 12:14:45 EST 1998 4: close 5: Sat Nov 14 12:14:46 EST 1998 5: close ^C 1309% In Window 2: 852% (sleep 3 ; date)| telnet 1234& 853% (sleep 3 ; date)| telnet 1234& 854% This is a sample program and hence it is missing a few obvious optimizations, error checking, as well as code to deal with timeouts, write and exception FD_sets etc. In a program for real use, you would likely put all fds in nonblocking mode; you would have multiple accept fds (one per interface); in do_accept() you would accept all outstanding connections; in do_read() you would read everything the other side sends (or not, depending on any fairness criterion); you would likely keep an array of functions, indexed by a fd, for a quick dispatch; and so on. For any moderately complex processing you may be better off using pthreads than a select loop (unless you want to squeeze out the very last drop of performance without descending to assembly language code). -- bakul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 10:00:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02786 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 10:00:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02779 for ; Sat, 14 Nov 1998 10:00:44 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA26712; Sat, 14 Nov 1998 11:00:22 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA08322; Sat, 14 Nov 1998 11:00:21 -0700 Date: Sat, 14 Nov 1998 11:00:21 -0700 Message-Id: <199811141800.LAA08322@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Bakul Shah Cc: Nate Williams , hackers@FreeBSD.ORG Subject: Re: Supporting more than FD_SETSIZE fd's In-Reply-To: <199811141753.MAA25077@chai.torrentnet.com> References: <199811111903.MAA18067@mt.sri.com> <199811141753.MAA25077@chai.torrentnet.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > The code fragment I showed is approx. right as I've used > > > something similar a couple of times before but I will try to > > > turn it into a working example over the weekend. > > > Thanks. If it included the MACROS so much the better. :) :) :) > > Check out > http://www.bitblocks.com/src/select-test.c > It even includes code to create and manipulate an FD set > object! Note that when used on a kernel that has fixed > FD_SETSIZE select() implementation, you must allocate exactly > FD_SETSIZE elements (and certainly no less) in an FD set. Thanks, I may not use the code directly, but by looking at it I certainly have a good idea how to make the JDK work, and why my attempts at this failed. :( Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 10:06:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03518 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 10:06:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03512 for ; Sat, 14 Nov 1998 10:06:40 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id NAA19048 for ; Sat, 14 Nov 1998 13:06:39 GMT Message-Id: <199811141306.NAA19048@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 14 Nov 1998 13:03:06 -0500 To: hackers@FreeBSD.ORG From: Dennis Subject: problem with netstat Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG when i run "netstat -rn" on one machine, I consistantly get Netstat: kvm_read: Bad Address streaming endlessly down the screen. what could be the cause of this? thanks, dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 10:09:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03750 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 10:09:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03745 for ; Sat, 14 Nov 1998 10:09:33 -0800 (PST) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id NAA18730; Sat, 14 Nov 1998 13:09:09 -0500 (EST) Date: Sat, 14 Nov 1998 13:09:09 -0500 (EST) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Dennis cc: hackers@FreeBSD.ORG Subject: Re: problem with netstat In-Reply-To: <199811141306.NAA19048@etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 14 Nov 1998, Dennis wrote: > > when i run "netstat -rn" on one machine, I consistantly get > > Netstat: kvm_read: Bad Address > > streaming endlessly down the screen. > > what could be the cause of this? Any change this is a -current box with a kernel built around 7 days to present? Chris -- "You both seem to be ignoring the fact that the networking market is driven by so-called 'IT professionals' these days, most of whom can't tell the difference between an ARP and a carp." --Wes Peters ===================================| Open Systems FreeBSD Consulting. FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186 -----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 10:48:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06108 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 10:48:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ceia.nordier.com (m1-55-dbn.dial-up.net [196.34.155.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06103 for ; Sat, 14 Nov 1998 10:48:48 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id UAA21102; Sat, 14 Nov 1998 20:46:32 +0200 (SAT) From: Robert Nordier Message-Id: <199811141846.UAA21102@ceia.nordier.com> Subject: Re: FreeBSD on i386 memory model In-Reply-To: <19981114191556.A17660@ucb.crimea.ua> from Ruslan Ermilov at "Nov 14, 98 07:15:56 pm" To: ru@ucb.crimea.ua (Ruslan Ermilov) Date: Sat, 14 Nov 1998 20:46:29 +0200 (SAT) Cc: rnordier@nordier.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ruslan Ermilov wrote: > On Fri, Nov 13, 1998 at 09:30:44PM +0200, Robert Nordier wrote: > > Ruslan Ermilov wrote: > > > Hi! > > > > > > I would like to practice in writing assembler programs > > > under FreeBSD. > > > > > > Is there any doc/book/man which describes the FreeBSD > > > memory model on i386 architecture? > > > > Essentially it's just a flat protected model, and for most purposes > > can simply be ignored. Rather than documentation, I'd suggest > > What documentation do you mean? I just meant: Don't rely on documentation, it's easier to use examples from the source tree. > > looking at C startup code (src/lib/csu), i386-specific C library > > functions (src/lib/libc/i386), and at the output of `cc -S'. > > > > FWIW, here's a small standalone i386 assembler program: > > > > main: call .+0x5 > > popl %ebp > > subl $0x5,%ebp > > pushl $msg.1-msg > > leal msg-main(%ebp),%eax > > pushl %eax > > pushl $0x1 > > movl $0x4,%eax > > call .+0x5 <-- why this one? > > lcall $0x7,$0x0 > > pushl $0x0 > > movl $0x1,%eax > > call .+0x5 <-- and this one? > > lcall $0x7,$0x0 > > msg: .ascii "hello, world!\n" > > msg.1: Typically, syscall() is implemented as a separate function, and what is pushed is the return address from that function: syscall: popl %ecx # Return address popl %eax # Syscall number pushl %ecx # Return address lcall $0x7,$0x0 # Do syscall pushl %ecx # Return address ret # To caller > Unfortunately, I can't compile it, as(1) gives the following: > > {standard input}: Assembler messages: > {standard input}:5: Error: Unimplemented segment type 0 in parse_operand > {standard input}:10: Error: operands given don't match any known 386 instruction > {standard input}:14: Error: operands given don't match any known 386 instruction > > It seems that as(1) doesn't understand ``lcall $SECTION, $OFFSET''. > At least on my 2.2.1, 2.2.5 and 2.2.7+ machines: > > FreeBSD relay.ucb.crimea.ua 2.2.7-STABLE FreeBSD 2.2.7-STABLE #0: Sun Oct 4 18:08:06 EEST 1998 root@:/usr/src/sys/compile/CHYRO i386 > > GNU assembler version 1.92.3, FreeBSD $Revision: 1.4 $ > > Any ideas? It assembles OK using the ELF assembler (2.9.1) on -current. I'd suggest using this, or installing a recent copy of GNU binutils. Older copies of gas weren't very usable for hand-written assembly language. Here's a better version, which assembles using either version of gas: main: pushl $0xe # sizeof(msg) pushl $msg # msg pushl $0x1 # FILENO_STDOUT movl $0x4,%eax # SYS_write pushl $main.1 # Do int $0x80 # syscall main.1: pushl $0x0 # Return values movl $0x1,%eax # SYS_exit pushl $main.2 # Do int $0x80 # syscall main.2: msg: .ascii "hello, world!\n" msg.1: -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 11:00:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07255 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 11:00:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles134.castles.com [208.214.165.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07241 for ; Sat, 14 Nov 1998 11:00:53 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA06641; Sat, 14 Nov 1998 10:59:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811141859.KAA06641@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dennis cc: hackers@FreeBSD.ORG Subject: Re: problem with netstat In-reply-to: Your message of "Sat, 14 Nov 1998 13:03:06 EST." <199811141306.NAA19048@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Nov 1998 10:59:33 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > when i run "netstat -rn" on one machine, I consistantly get > > Netstat: kvm_read: Bad Address > > streaming endlessly down the screen. > > what could be the cause of this? Looks like a mismatch between the kernel and libkvm. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 11:06:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07558 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 11:06:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles134.castles.com [208.214.165.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07553 for ; Sat, 14 Nov 1998 11:06:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA06709; Sat, 14 Nov 1998 11:04:28 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811141904.LAA06709@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ruslan Ermilov cc: Robert Nordier , FreeBSD Hackers Subject: Re: FreeBSD on i386 memory model In-reply-to: Your message of "Sat, 14 Nov 1998 19:15:56 +0200." <19981114191556.A17660@ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Nov 1998 11:04:28 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > FWIW, here's a small standalone i386 assembler program: > > > > main: call .+0x5 > > popl %ebp > > subl $0x5,%ebp > > pushl $msg.1-msg > > leal msg-main(%ebp),%eax > > pushl %eax > > pushl $0x1 > > movl $0x4,%eax > > call .+0x5 <-- why this one? > > lcall $0x7,$0x0 > > pushl $0x0 > > movl $0x1,%eax > > call .+0x5 <-- and this one? > > lcall $0x7,$0x0 > > msg: .ascii "hello, world!\n" > > msg.1: > > Unfortunately, I can't compile it, as(1) gives the following: > > {standard input}: Assembler messages: > {standard input}:5: Error: Unimplemented segment type 0 in parse_operand > {standard input}:10: Error: operands given don't match any known 386 instruction > {standard input}:14: Error: operands given don't match any known 386 instruction > > It seems that as(1) doesn't understand ``lcall $SECTION, $OFFSET''. > At least on my 2.2.1, 2.2.5 and 2.2.7+ machines: No, it doesn't. You can either upgrade to a newer assembler, or do it the "old" way: #define LCALL(x,y) .byte 0x9a ; .long y; .word x Note that on 3.0 systems we use int 0x80 for kernel entry, as it's faster. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 11:32:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09445 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 11:32:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ceia.nordier.com (m1-35-dbn.dial-up.net [196.34.155.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09282 for ; Sat, 14 Nov 1998 11:32:31 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id VAA21677; Sat, 14 Nov 1998 21:29:08 +0200 (SAT) From: Robert Nordier Message-Id: <199811141929.VAA21677@ceia.nordier.com> Subject: Re: FreeBSD on i386 memory model In-Reply-To: <199811141904.LAA06709@dingo.cdrom.com> from Mike Smith at "Nov 14, 98 11:04:28 am" To: mike@smith.net.au (Mike Smith) Date: Sat, 14 Nov 1998 21:29:04 +0200 (SAT) Cc: ru@ucb.crimea.ua, rnordier@nordier.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > No, it doesn't. You can either upgrade to a newer assembler, or > do it the "old" way: > > #define LCALL(x,y) .byte 0x9a ; .long y; .word x > > Note that on 3.0 systems we use int 0x80 for kernel entry, as it's > faster. Though int 0x80 is also valid for older releases of FreeBSD, including 2.2.x. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 13:19:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17002 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 13:19:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16990 for ; Sat, 14 Nov 1998 13:19:25 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id QAA19399; Sat, 14 Nov 1998 16:19:21 GMT Message-Id: <199811141619.QAA19399@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 14 Nov 1998 16:15:46 -0500 To: Mike Smith From: Dennis Subject: Re: problem with netstat Cc: hackers@FreeBSD.ORG In-Reply-To: <199811141859.KAA06641@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:59 AM 11/14/98 -0800, you wrote: >> >> when i run "netstat -rn" on one machine, I consistantly get >> >> Netstat: kvm_read: Bad Address >> >> streaming endlessly down the screen. >> >> what could be the cause of this? > >Looks like a mismatch between the kernel and libkvm. scrubbed and rebuilt the kernel and its ok now. Thanks. db To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 14:41:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22158 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 14:41:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22146 for ; Sat, 14 Nov 1998 14:41:10 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1a/8.9.1) with ESMTP id OAA04667 for ; Sat, 14 Nov 1998 14:41:47 -0800 (PST) To: hackers@FreeBSD.ORG Subject: Mike Smith and I will be at COMDEX in Las Vegas, Nov 16-20 Date: Sat, 14 Nov 1998 14:41:46 -0800 Message-ID: <4662.911083306@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just FYI, Mike and I will be at the Walnut Creek CDROM/FreeBSD/Slackware booth (each of us groups gets our own piece of it :) at the Sands Convention Center, booth S-7533. If anyone in Las Vegas would like to stop by and say "Hi!", please do! If anyone would like to give me dialup access so that I can check my mail (I should really set this up as a standing arrangement for every year :-), that would be really great also. If so, please just drop me an email with the dialup/account details. Much obliged. Thanks! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 15:04:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24107 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 15:04:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24102 for ; Sat, 14 Nov 1998 15:04:27 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id QAA13910; Sat, 14 Nov 1998 16:04:00 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd013887; Sat Nov 14 16:03:53 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA25590; Sat, 14 Nov 1998 16:03:53 -0700 (MST) From: Terry Lambert Message-Id: <199811142303.QAA25590@usr02.primenet.com> Subject: Re: linux software installation and uname To: sgk@troutmask.apl.washington.edu (Steve Kargl) Date: Sat, 14 Nov 1998 23:03:52 +0000 (GMT) Cc: tlambert@primenet.com, jb@cimlogic.com.au, crossd@cs.rpi.edu, jkh@time.cdrom.com, nate@mt.sri.com, hackers@FreeBSD.ORG In-Reply-To: <199811112316.PAA03393@troutmask.apl.washington.edu> from "Steve Kargl" at Nov 11, 98 03:16:17 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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, I started the thread, so here goes. It isn't that simple, > the script also checks to see that it was executed from /cdrom/x86-1.7/linux. > You can work around that I suppose once you find all the dependency. Or even ignoring the dependency as being irrelevent to the issue: #!/bin/sh # assume failure... PRESTATUS="FAIL" preinstall() { echo "PREINSTALL started" if [ -d /cdrom ] then echo "renaming /cdrom; we need a work directory named /cdrom" mv /cdrom /cdrom-linux-was-here fi mkdir /cdrom mount /dev/cd0a /mnt cd /mnt echo "copying install image to writeable hierarchy for patching" tar cf - . | (cd /cdrom ; tar xvf -) unount /mnt echo "patching the bejesus out of things..." # Oh, look, a patch that, if sent to the vendor, would make # the next CDROM install on FreeBSD as well as Linux, without # all the hoopla... patch < Next, you need to specify where the libgcc and libf2c for linux live. /compat/linux/usr/lib > This can be fixed after the install. There other idiosyncracies that > need to be adjusted. Yeah, so? That's why there are software engineers. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 15:19:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25272 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 15:19:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25267 for ; Sat, 14 Nov 1998 15:19:39 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id QAA25287; Sat, 14 Nov 1998 16:19:13 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd025276; Sat Nov 14 16:19:12 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA26572; Sat, 14 Nov 1998 16:19:06 -0700 (MST) From: Terry Lambert Message-Id: <199811142319.QAA26572@usr02.primenet.com> Subject: Re: SCSI vs. DMA33.. To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sat, 14 Nov 1998 23:19:05 +0000 (GMT) Cc: grog@lemis.com, gibbs@narnia.plutotech.com, hackers@FreeBSD.ORG In-Reply-To: <199811130529.VAA01053@apollo.backplane.com> from "Matthew Dillon" at Nov 12, 98 09:29:20 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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think where overlapping commands have their greatest > advantage is when a command to a drive has a certain > latency associated with it that prevents you from issuing > another command to the drive that might be completed more > efficiently by the drive You mean like "write" or "read"? 8-). PS: I think your Promise two channel concurrent access problems may be because of the way you compiled your kernel; make sure you are not using the CMD640B workaround (where we intentionally do not access the second channel while the first is active, and vice-versa because the IDE controller chip will silently interrupt transfers in progress). Also make sure that the workaround is not being triggered by onboard Intel or other IDE chips known to have the same problem (this may occur silently because we can detect buggy Intel chips, but we can't detect CMD640B's relaibly). Probably you want to put in a printf. See the relevent CMD640B code. PS: Your SCSI drives appear to suck; it is not fair for you to blame this on SCSI instead of on the drive manufacturer. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 15:41:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27295 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 15:41:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27290 for ; Sat, 14 Nov 1998 15:41:29 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id QAA00690; Sat, 14 Nov 1998 16:41:03 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd000668; Sat Nov 14 16:40:58 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA27778; Sat, 14 Nov 1998 16:40:53 -0700 (MST) From: Terry Lambert Message-Id: <199811142340.QAA27778@usr02.primenet.com> Subject: Re: [Vinum] Stupid benchmark: newfsstone To: mike@smith.net.au (Mike Smith) Date: Sat, 14 Nov 1998 23:40:53 +0000 (GMT) Cc: peter.jeremy@auss2.alcatel.com.au, hackers@FreeBSD.ORG In-Reply-To: <199811132150.NAA00549@dingo.cdrom.com> from "Mike Smith" at Nov 13, 98 01:50:40 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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ ... disk-to-disk copies over the SCSI bus not involving the host ... ] > > > And it's almost impossible to find > > >spindle synchronized disks nowadays. > > > > Seagate Barracuda's support it, I assumed that the newer Seagates did > > as well. The impression I got was that all you had to do was wire the > > `spindle sync' lines from all the disks together and then designate > > all except one as a sync'd slave. Admittedly, I've never tried > > actually using it. > > Most modern "server class" SCSI disks support it. It's not useful > unless you turn off tagged queueing, caching and most other drive > performance features. Actually, I could see it being *very* useful for copying data between plexes on different volumes for the purpose of replication. Bringing a new disk online in a RAID 5 array could also use this to advantage. I don't think either of these applications actually requires that you turn off drive performance features -- though you would have to reserve tag space to not starve the sending drive. Finally, if a disk could be made to talk to itself (unlikely, but some vendor probably neglected to prevent it by checking for the same source/target ID, I hope 8-)), it would be useful for various intra-disk transfers of data, as well. > You'd have to cons a new map and have it present the scattered target > area as a linear region. This is expensive, and the performance boost > is likely to be low to nonexistent for optimal stripe sizes. > Concatenation of multiple stripe reads is only a benefit if the stripe > is small (so that concatenation significantly lowers overhead). Compared to the normal recalculation time on a new hot-swap on a large array, I would think that even though it's expensive, it would be less expensive than the alternative of having to do the same thing anyway, *and* transfer the SCSI data in an out of host memory over, best case, a PCI bus. > > What would be useful is some help (from vinum or ccd) to ensure that > > the cylinder group blocks (superblock + inode maps etc) don't cross > > stripes. > > That's something that the user should take care of. Any power-of-2 > stripe size is likely to work out OK, as CG's are currently 32MB. Hm. Maybe the tools should limit this, or at least "bitch", in the same sense that disklabel puts up little asterisks... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 15:42:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27562 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 15:42:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27518 for ; Sat, 14 Nov 1998 15:41:55 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (root@woof.lan.Awfulhak.org [172.16.0.7]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id WAA16859; Sat, 14 Nov 1998 22:44:12 GMT (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1]) by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id WAA20413; Sat, 14 Nov 1998 22:46:00 GMT (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199811142246.WAA20413@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Dave Edwards cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Ijppp and the -alias option In-reply-to: Your message of "Fri, 13 Nov 1998 08:44:13 +1030." <199811122214.IAA14495@chunga.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Nov 1998 22:45:57 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems that the ppp process ignores the -background switch and > sets up demand dialing when you use the -alias option. > > The line will drop (and stay dropped) with entries in the logs > saying "Idle time expired" when activity ceases (about 30 seconds > or so). Using -background doesn't alter the idle timer. Use ``set timeout 0'' if you don't want to time out. [.....] -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 15:48:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27911 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 15:48:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27897 for ; Sat, 14 Nov 1998 15:48:06 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id QAA04768; Sat, 14 Nov 1998 16:47:34 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd004754; Sat Nov 14 16:47:30 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA28187; Sat, 14 Nov 1998 16:47:24 -0700 (MST) From: Terry Lambert Message-Id: <199811142347.QAA28187@usr02.primenet.com> Subject: Re: [Vinum] Stupid benchmark: newfsstone To: mike@smith.net.au (Mike Smith) Date: Sat, 14 Nov 1998 23:47:24 +0000 (GMT) Cc: ticso@cicely.de, mike@smith.net.au, peter.jeremy@auss2.alcatel.com.au, hackers@FreeBSD.ORG In-Reply-To: <199811132336.PAA01117@dingo.cdrom.com> from "Mike Smith" at Nov 13, 98 03:36:14 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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Most modern "server class" SCSI disks support it. It's not useful > > > unless you turn off tagged queueing, caching and most other drive > > > performance features. > > > > Where's the problem with these options on when using Spindle Sync? > > The whole point of spindle sync is to exactly lock all the drives > together to coordinate read/write activity. These features in > conjunction with sector sparing and quantum differences between disks > means that synchronising spindles is a complete waste of time, as the > disks won't be mimicking each other anyway. My personal take on this was to allow the choice of disk from which to read a stripe to be "late bound" to optimize the load distribution between spindles. This assumes each plex or stripe has at least one replicate on a different spindle. Give three read operations against three disks, this would allow you to choose your disks so as to schedule the reads from seperate disks for each of the reads on average 66% of the time. Even so, sync is much less useful inreverse sector ordered devices for which the geometry is not known, even for this use. Actually, you should drag Rod Grimes into any spindle-sync discussion; I know that he built a spindle-syned system, and had, at one time, put up patches for CCD to deal with it. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 15:50:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28092 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 15:50:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28085 for ; Sat, 14 Nov 1998 15:50:17 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id QAA05193; Sat, 14 Nov 1998 16:49:54 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd005180; Sat Nov 14 16:49:46 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA28317; Sat, 14 Nov 1998 16:49:45 -0700 (MST) From: Terry Lambert Message-Id: <199811142349.QAA28317@usr02.primenet.com> Subject: Re: [Vinum] Stupid benchmark: newfsstone To: grog@lemis.com (Greg Lehey) Date: Sat, 14 Nov 1998 23:49:45 +0000 (GMT) Cc: mike@smith.net.au, ticso@cicely.de, peter.jeremy@auss2.alcatel.com.au, hackers@FreeBSD.ORG In-Reply-To: <19981114104105.S781@freebie.lemis.com> from "Greg Lehey" at Nov 14, 98 10:41:05 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'll tell you what: anybody who wants, go and look at the request > building code in /usr/src/lkm/vinum/request.c and rebuild it to > perform the "aggregation" optimizations that Bernd wants, and I'll > put it into the code. RAIDFrame was built as a research tool to allow people to test out just such theories, with the minimum amount of code, and no modification required to the framework in which the code runs. It's acutally the right tool for the job of testing these ideas out. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 16:06:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01193 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 16:06:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01188 for ; Sat, 14 Nov 1998 16:06:39 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA06039; Sun, 15 Nov 1998 10:35:54 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id KAA28619; Sun, 15 Nov 1998 10:35:47 +1030 (CST) Message-ID: <19981115103547.F28481@freebie.lemis.com> Date: Sun, 15 Nov 1998 10:35:47 +1030 From: Greg Lehey To: Terry Lambert Cc: mike@smith.net.au, ticso@cicely.de, peter.jeremy@auss2.alcatel.com.au, hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone References: <19981114104105.S781@freebie.lemis.com> <199811142349.QAA28317@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811142349.QAA28317@usr02.primenet.com>; from Terry Lambert on Sat, Nov 14, 1998 at 11:49:45PM +0000 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 14 November 1998 at 23:49:45 +0000, Terry Lambert wrote: >> I'll tell you what: anybody who wants, go and look at the request >> building code in /usr/src/lkm/vinum/request.c and rebuild it to >> perform the "aggregation" optimizations that Bernd wants, and I'll >> put it into the code. > > RAIDFrame was built as a research tool to allow people to test > out just such theories, with the minimum amount of code, and no > modification required to the framework in which the code runs. > > It's acutally the right tool for the job of testing these ideas > out. I'm not sure. One of the problems is timing. I'm sure RAIDFrame would behave differently from Vinum, especially regarding the sequence in which the requests are issued. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 17:16:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05970 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 17:16:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05964 for ; Sat, 14 Nov 1998 17:16:29 -0800 (PST) (envelope-from aron@cs.rice.edu) Received: from elf.cs.rice.edu (elf.cs.rice.edu [128.42.1.134]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id TAA06551 for ; Sat, 14 Nov 1998 19:16:06 -0600 (CST) From: Mohit Aron Received: (from aron@localhost) by elf.cs.rice.edu (8.9.0/8.9.0) id TAA01047 for freebsd-hackers@freebsd.org; Sat, 14 Nov 1998 19:16:06 -0600 (CST) Message-Id: <199811150116.TAA01047@elf.cs.rice.edu> Subject: NFS over tcp To: freebsd-hackers@FreeBSD.ORG Date: Sat, 14 Nov 1998 19:16:05 -0600 (CST) 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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm using NFS over TCP between two FreeBSD-2.2.6 machines. Despite TCP being a reliable protocol, it seems the NFS implementation still tries to retransmit requests. Can someone please confirm my observation and suggest a fix to turn off this feature ? Please reply directly to me by email. Thanks, - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 20:05:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA17545 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 20:05:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bachue.usc.unal.edu.co (bachue.usc.unal.edu.co [168.176.3.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17538 for ; Sat, 14 Nov 1998 20:05:28 -0800 (PST) (envelope-from pfgiffun@bachue.usc.unal.edu.co) Received: from bachue.usc.unal.edu.co ([168.176.3.20]) by bachue.usc.unal.edu.co (Netscape Messaging Server 3.0) with SMTP id AAA21214 for ; Sat, 14 Nov 1998 23:08:11 +0500 Date: Sat, 14 Nov 1998 23:07:58 +0500 (GMT) From: "Pedro Fernando Giffuni" Reply-To: Pedro Fernando Giffuni To: hackers@FreeBSD.ORG Subject: Interesting: the globus project Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a parallel computing list ? http://www.mcs.anl.gov/nexus/ BTW, FreeBSD is a supported platform for the Globus toolkit ! enjoy, Pedro. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 21:08:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21929 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 21:08:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pchost.com (pchost.com [203.24.253.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21918 for ; Sat, 14 Nov 1998 21:08:44 -0800 (PST) (envelope-from kyle@pchost.com) Received: from pchost.com (bob.pchost.com [203.24.253.107]) by pchost.com (8.8.8/8.8.8) with ESMTP id QAA01888 for ; Sun, 15 Nov 1998 16:18:07 +1100 (EST) (envelope-from kyle@pchost.com) Message-ID: <364E618A.FE7BDC5F@pchost.com> Date: Sun, 15 Nov 1998 16:07:23 +1100 From: kyle X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 2.2.7-STABLE i386) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Star Office 5 install Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am having some probles installing Star Office 5 and was wondering if any one else has sucessfully sompleted the install. At the moment I think I have install the glibc2 files ok. But when I try to run the setup program I get a segmentation fault (core dump) any ideas. Kyle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 22:52:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26934 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 22:52:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles231.castles.com [208.214.165.231]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26927 for ; Sat, 14 Nov 1998 22:52:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA10105; Sat, 14 Nov 1998 22:51:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811150651.WAA10105@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), peter.jeremy@auss2.alcatel.com.au, hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone In-reply-to: Your message of "Sat, 14 Nov 1998 23:40:53 GMT." <199811142340.QAA27778@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Nov 1998 22:51:17 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [ ... disk-to-disk copies over the SCSI bus not involving the host ... ] > > > > > And it's almost impossible to find > > > >spindle synchronized disks nowadays. > > > > > > Seagate Barracuda's support it, I assumed that the newer Seagates did > > > as well. The impression I got was that all you had to do was wire the > > > `spindle sync' lines from all the disks together and then designate > > > all except one as a sync'd slave. Admittedly, I've never tried > > > actually using it. > > > > Most modern "server class" SCSI disks support it. It's not useful > > unless you turn off tagged queueing, caching and most other drive > > performance features. > > Actually, I could see it being *very* useful for copying data between > plexes on different volumes for the purpose of replication. How? Please note the quantum effects I've mentioned previously, and note that the only useful way to overcome them is to enable buffering at both ends of the queue. Please also study the internal architecture of most SCSI disks and note the almost total decoupling between the head/spindle location and the availability of a request for presentation to the bus. Spindle sync was useful back when data off the drive was basically the output of the head preamp or the data separator. It's not noticeably useful as soon as you allow the drive to do things for it's own reasons. > Bringing a new disk online in a RAID 5 array could also use this > to advantage. What you want is the SCSI COPY command. > Finally, if a disk could be made to talk to itself (unlikely, but > some vendor probably neglected to prevent it by checking for the > same source/target ID, I hope 8-)), it would be useful for various > intra-disk transfers of data, as well. This is beyond far-fetched. > > You'd have to cons a new map and have it present the scattered target > > area as a linear region. This is expensive, and the performance boost > > is likely to be low to nonexistent for optimal stripe sizes. > > Concatenation of multiple stripe reads is only a benefit if the stripe > > is small (so that concatenation significantly lowers overhead). > > Compared to the normal recalculation time on a new hot-swap on a > large array, I would think that even though it's expensive, it > would be less expensive than the alternative of having to do the > same thing anyway, *and* transfer the SCSI data in an out of host > memory over, best case, a PCI bus. This has nothing to do with array reconstruction. Having just watched Event Horizon, I can imagine how your brain got here, but you're completely crossed up. Go back. > > > What would be useful is some help (from vinum or ccd) to ensure that > > > the cylinder group blocks (superblock + inode maps etc) don't cross > > > stripes. > > > > That's something that the user should take care of. Any power-of-2 > > stripe size is likely to work out OK, as CG's are currently 32MB. > > Hm. Maybe the tools should limit this, or at least "bitch", in the > same sense that disklabel puts up little asterisks... Disklabel should stop putting them up. They're not meaningful anymore. It's arguable as to whether it actually matters whether CG's fragment across stripe boundaries either. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 22:58:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA27582 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 22:58:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles231.castles.com [208.214.165.231]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA27577 for ; Sat, 14 Nov 1998 22:58:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA10149; Sat, 14 Nov 1998 22:56:21 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811150656.WAA10149@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: grog@lemis.com (Greg Lehey), mike@smith.net.au, ticso@cicely.de, peter.jeremy@auss2.alcatel.com.au, hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone In-reply-to: Your message of "Sat, 14 Nov 1998 23:49:45 GMT." <199811142349.QAA28317@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Nov 1998 22:56:20 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'll tell you what: anybody who wants, go and look at the request > > building code in /usr/src/lkm/vinum/request.c and rebuild it to > > perform the "aggregation" optimizations that Bernd wants, and I'll > > put it into the code. > > RAIDFrame was built as a research tool to allow people to test > out just such theories, with the minimum amount of code, and no > modification required to the framework in which the code runs. > > It's acutally the right tool for the job of testing these ideas > out. ... it was also imported into NetBSD on the 12th. What's most irritating is that the vast majority of the diffs between the original RAIDframe code and the version imported into the NetBSD tree are noise - formatting, prototypes, etc. The actual meat is pretty trivial, but it makes me wonder who actually reviewed the code, and what their criteria were... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 23:08:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28294 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 23:08:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles231.castles.com [208.214.165.231]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28279 for ; Sat, 14 Nov 1998 23:08:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA10241; Sat, 14 Nov 1998 23:06:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811150706.XAA10241@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: kyle cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Star Office 5 install In-reply-to: Your message of "Sun, 15 Nov 1998 16:07:23 +1100." <364E618A.FE7BDC5F@pchost.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Nov 1998 23:06:31 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Don't bother, unless you're working on the Linux threading emulation; It doesn't run at this point in time. > I am having some probles installing Star Office 5 and was wondering if > any one else has sucessfully sompleted the install. > > At the moment I think I have install the glibc2 files ok. > > But when I try to run the setup program I get a segmentation fault (core > dump) > > any ideas. > > Kyle > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 14 23:47:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01424 for freebsd-hackers-outgoing; Sat, 14 Nov 1998 23:47:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01419 for ; Sat, 14 Nov 1998 23:47:56 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id CAA05210; Sun, 15 Nov 1998 02:40:19 -0500 (EST) Date: Sun, 15 Nov 1998 02:40:19 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: "Ron G. Minnich" cc: Vince Vielhaber , The Hermit Hacker , Joe Shevland , hackers@FreeBSD.ORG, "Jordan K.Hubbard" , "Daniel O'Connor" Subject: Re: Applixware was Re: Detailed info on Fail-safe cluster for Freebsd/unixes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Nov 1998, Ron G. Minnich wrote: > Sorry to put this on -hackers, but it seems to be stuck here. ditto. > Don't assume you can use either of these tools to interoperate with ms > office. You can't. In terms of how luck you'll be: > excel: probably works, most of the time > word: works if it is text only most of the time, fails badly on anything > useful Hey, that's OK. We have an NT machine in the office that we share for those "killer apps" from Redmond. Someone has screwed Word7 to the point that it just displays a bunch of binary garbage where images should be and occasionaly puts a word or two in different fonts... I'd try to fix it, but since a reinstall of Word didn't help... Who really has a day to waste? Lesson: Office sucks. Office emulators suck when emulating it. Just be thankful you have a suite you can run in 'native' mode on your OS of choice... Charles > Good luck. > > ron > > Ron Minnich |"Using Windows NT, which is known to have some > rminnich@sarnoff.com | failure modes, on a warship is similar to hoping > (609)-734-3120 | that luck will be in our favor"- A. Digiorgio > ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message